Article View: digex.general
Article #86SLCs, Digex and BA (Was: Re: DIGEX Customer Newsletter)
From: Jim Jagielski
Date: Thu, 14 Dec 1995 00:00
Date: Thu, 14 Dec 1995 00:00
28 lines
2527 bytes
2527 bytes
This is all my opinion... take it or leave it. I think it's unfair to blame Digex for the fact that the SLCs can't carry the full bandwidth of a 28.8k modem. The specifications and particulars of those circuits are beyond Digex's control and instead fall into the grand monopoly of Bell Atlantic. However, you could blame Digex for using this technique to handle remote calling areas. As I understand it, the actual carrier is being shipped down these SLCs to Digex's main POP. However, this isn't the only way to handle remote numbers. A "more reasonable" solution, and one which puts control of the circuit at least more in their control, is a true POP, which is linked via leased-line to their main POP. At each remote POP, there would be a modem pool, terminal servers, router and CSU/DSU. Thus, they wouldn't be shipping analog carrier down the SLCs but instead would be shipping digital data in which bandwidth can be controlled and somewhat guaranteed. So the limitations of the SLCs are beyond Digex's control, and you can't blame them for that. You can, if you like, blame them for using a method that makes the limitations of the SLCs _their_ limitation as well. You could also reasonable blame them for not investigating different options as well. -- Jim Jagielski << jim@jaguNET.com >> | "Wind the frog!" ** jaguNET Access Services ** | - Woody (from Toy Story) ++ Email: info@jaguNET.com +++ Voice: 410-931-3157 ++ ++ http://www.jaguNET.com/ +++ Data: 410-931-7060 ++
Technical Details
Message-ID:
<4aq3m1$9jb@shado.jaguNET.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<4a6a30$2n2@ss2.digex.net> <4afp2j$7sc@access1.digex.net> <4ahmuo$sr2@access4.digex.net> <4ai9j9$c2n@access4.digex.net> <4aidu4$5br@access5.digex.net> <ACF4CA5B966843BEA@ehrice.his.com> <4apsfr$rr8@news4.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: 15ff9f,d1501dbbe4ab84f7 X-Google-Attributes: gid15ff9f,public X-Google-Thread: 101049,d1501dbbe4ab84f7 X-Google-Attributes: gid101049,public X-Google-Thread: 109e7a,d1501dbbe4ab84f7 X-Google-Attributes: gid109e7a,public From: jim@jaguNET.com (Jim Jagielski) Subject: SLCs, Digex and BA (Was: Re: DIGEX Customer Newsletter) Date: 1995/12/14 Message-ID: <4aq3m1$9jb@shado.jaguNET.com> X-Deja-AN: 121817093 references: <4a6a30$2n2@ss2.digex.net> <4afp2j$7sc@access1.digex.net> <4ahmuo$sr2@access4.digex.net> <4ai9j9$c2n@access4.digex.net> <4aidu4$5br@access5.digex.net> <ACF4CA5B966843BEA@ehrice.his.com> <4apsfr$rr8@news4.digex.net> organization: jaguNET Access Services - MD ISP, 410-931-3157 reply-to: jim@jaguNET.com newsgroups: digex.general,digex.slip,balt.general,dc.general