Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : LAST MILE TECHNOLOGIES - Let's Discuss Them Here -- Ignore unavailable to you. Want to Upgrade?

To: Frank A. Coluccio who wrote (6164)	12/11/1999 12:13:00 PM
From: SDR-SI	Respond to of 12823

Assistance With Current Regulatory/Practice Questions Frank or anyone, Could I impose on you to say a few words to help me clarify my necessarily simplified understanding of both regulatory and practice considerations with the application of DSL to lines serviced by CLEC's that are colo'd through an ILEC facility, especially in view of the fact that the actual DSL provider is generally not the CLEC itself or an ILEC itself, but often is a separate DSL provider organization. If the user is a POTS customer of the ILEC, it is my understanding that the DSL is applied to the outgoing lines at the CO, downstream from the switch and that the DSLAM/DSLAR cross-connects to the lines essentially at the point at which the lines frame up as they leave/enter the CO for the cable plant. I think I am also correct in understanding that it is not unusual for various outside DSL providers have their own DSALM/DSLAR's colo'd at the ILEC CO, and that such results in the ability for the DSL providers to either provide their services name-branded to the ILEC or with their own name-brand or a name-brand of some other organization who basically just resells the DSL services the DSL provider provides. As one brings a CLEC into the picture, I'm not really sure that I understand the structure and data flow correctly. If one orders both POTS and DSL through a CLEC, are the POTS and DSL information streams combined at the CLEC switch, fibered to the colo at the ILEC and then appropriately separated in the colo'd equipment for application to the outgoing customer line at the ILEC? OR do they come over as two wholly separate and unrelated communications streams and then are combined at the point at which the colo equipment connects to the cable plant, meaning that the colo must contain at least some mini-DSLAM functionality? I suspect its the latter. I suspect also that there are situations in which the DSL provider for the CLEC just happens to also have an independently existing DSLAM/DSLAR at the ILEC and that a separate DSL capability might not be necessary in the CLEC's colo at the ILEC. This brings me to two questions of interest to me from both a regulatory and practice point of view: First, is it regulatorily possible, and is it done in common practice, to obtain POTS service from a CLEC whose feed into the cable plant is through a specific ILEC, and on the same copper pair obtain DSL service from either that ILEC itself or from some other DSL provider who has DSLAM/DSLAR facilities only at the ILEC and basically does not have a working relationship with the CLEC itself? In other words, is it possble for a provider to add DSL onto a customer line, other than through arrangement with the ultimate POTS provider, or does the pots provider own the right to control everything outgoing from the ILEC CO onto the copper to the CLEC's customer? Second, is my assumption about mini-DSLAm/DSLAR functionality in the usual colo equipment belonging to a CLEC and colo'd at an ILEC CO correct? Or does the availability of DSL through a CLEC depend upon the existence of a independent DSLAM/DSLAR belonging to the actual DSL provider at the ILEC CO facility? TIA and apologies for the fact that this post suffers from "over-abbreviationness", an unfortunately common, but necessary disease. Steve

To: Frank A. Coluccio who wrote (6164)	12/16/1999 1:07:00 PM
From: joarel	Read Replies (1) \| Respond to of 12823

Frank & All, A glorious holiday to everyone. I open this question to all who may have some knowledge regarding T carrier. I've been researching Cisco router requirements for T carrier. I've been able to locate the format, code, number of channels, line rate, but need some assistance on clock source(internal or external) and LBO(as it relates to DB gain or loss). Can you help? Any direction or information will be very helpful. ~joarel