[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Creating a Circuit ID Format
- Subject: Creating a Circuit ID Format
- From: achatz at forthnet.gr (Tassos Chatzithomaoglou)
- Date: Tue, 22 Aug 2017 19:01:56 +0300
- In-reply-to: <CAMDdSzPotYBiYgXH=eTtPGJ1hLcQ8wkpEpFbdskR-zTsNL6fOA@mail.gmail.com>
- References: <CAMDdSzPotYBiYgXH=eTtPGJ1hLcQ8wkpEpFbdskR-zTsNL6fOA@mail.gmail.com>
I don't know if it has any relation to your issue, but we use Circuit-ID to uniquely identify the access node plus the customer's access loop logical port on the access node.
Access node can be either a DSLAM, a switch, an OLT, etc.
You may have a look at BBF's TR-101 (section 3.9.3) or TR-156 (section 5.7) for syntax guide .
--
Tassos
Colton Conor wrote on 21/8/17 23:26:
> We are building a new fiber network, and need help creating a circuit ID
> format to for new fiber circuits. Is there a guide or standard for fiber
> circuit formats? Does the circuit ID change when say a customer upgrades
> for 100Mbps to 1Gbps port?
>
> What do the larger carriers do? Any advice on creating a circuit ID format
> for a brand new fiber network?
>
>
> Originally we ran a CLEC using a LECs copper, and our circuit ID was
> historically a telephone number for DSL circuits. The ILEC had a complex
> method for assigning circuit IDs.
>
> I am sure anything will work as long as you keep track of it, but any
> advice would be great!
>