Article View: digex.general
Article #106Re: DIGEX Customer Newsletter
From: Sean Connery
Date: Mon, 11 Dec 1995 00:00
Date: Mon, 11 Dec 1995 00:00
41 lines
2722 bytes
2722 bytes
In article <4ahmuo$sr2@access4.digex.net>, Moo's Access Point <moobox@access4.digex.net> wrote: >Spec what out? > >Bell Atlantic installs and owns the equipment, lines, and so forth. They >have a regulated monopoly, which is bound by various tariffs as to what >they must provide. Anything beyond that is gravy. > >They are under no obligation beyond what the tariffs state. > >Just what did would one expect DIGEX to "spec" out? > >People seem to have this very bizarre notion that: > > A) Bell Atlantic can be told what to do > > B) There is significant competition for BA dial-tone > services in the areas we serve. > >B is conditionally true; there is competition for dial-tone and other >services, via MFS and other carriers, but I doubt MFS or Teleport is >going to unconditionally promise to deliver 28.8K analog dial up because >if a call crosses from BA to MFS or Telport and there's a SLC in the >middle... <slice> Oh geez. OK, here is my humble opinion...and I gather as I am a customer..most people here will agree. Yes, I understand that BA this and BA that and they're fone weasels and regulated monopoly blah blah blah. BUT...if BA told DIGEX...or DIGEX had bothered to investigate..into the issued of the SLC96s don't generally provide connections paat 24k... Then it is DIGEX's position to say hey...this is subpar performance...we should either get better equipment...or "worse" equipment...because what the customer wants is 28.8k, not what is going to be most cost effective for DIGEX. Now the damage is done. And I understand the technical aspects. But if someone was really paying attention...then maybe the SLC96 route would not have been taken. And certainly after the fact...your whole rhetoric with uncondtionally blaming BA is not going to sit well with customers. The comment someone made about the "court of public opinion" was a very good one indeed.
Technical Details
Message-ID:
<4ai9j9$c2n@access4.digex.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<4a6a30$2n2@ss2.digex.net> <4a77go$184@access4.digex.net> <4afp2j$7sc@access1.digex.net> <4ahmuo$sr2@access4.digex.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10a9ce,d1501dbbe4ab84f7 X-Google-Attributes: gid10a9ce,public X-Google-Thread: 101049,d1501dbbe4ab84f7 X-Google-Attributes: gid101049,public X-Google-Thread: 15ff9f,d1501dbbe4ab84f7 X-Google-Attributes: gid15ff9f,public X-Google-Thread: 109e7a,d1501dbbe4ab84f7 X-Google-Attributes: gid109e7a,public From: bond@access4.digex.net (Sean Connery) Subject: Re: DIGEX Customer Newsletter Date: 1995/12/11 Message-ID: <4ai9j9$c2n@access4.digex.net> X-Deja-AN: 121548132 references: <4a6a30$2n2@ss2.digex.net> <4a77go$184@access4.digex.net> <4afp2j$7sc@access1.digex.net> <4ahmuo$sr2@access4.digex.net> organization: Universal Export newsgroups: digex.general,digex.slip,balt.general,dc.general