nanog mailing list archives
Re: Creating a Circuit ID Format
From: Jared Mauch <jared () puck nether net>
Date: Tue, 22 Aug 2017 12:37:08 -0400
On Aug 22, 2017, at 12:01 PM, Tassos Chatzithomaoglou <achatz () forthnet gr> wrote: 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 .
My favorite circuit-ids were those from MFS where it had the service type (2 chars i think) + a pop-code + z pop-code + service count number. We could then tell what pop/facility everything was handed off at easily enough. I think my house even got a MFS pop code at one time due to the T1 which was there. - Jared
Current thread:
- Re: Creating a Circuit ID Format, (continued)
- Re: Creating a Circuit ID Format Nick Hilliard (Aug 21)
- Re: Creating a Circuit ID Format Jared Mauch (Aug 21)
- Re: Creating a Circuit ID Format William Herrin (Aug 21)
- Re: Creating a Circuit ID Format Tim Pozar (Aug 21)
- Re: Creating a Circuit ID Format Nick W (Aug 24)
- Re: Creating a Circuit ID Format James Bensley (Aug 22)
- Re: Creating a Circuit ID Format Justin M. Streiner (Aug 22)
- Re: Creating a Circuit ID Format Nick Hilliard (Aug 22)
- RE: Creating a Circuit ID Format Timothy Creswick (Aug 23)
- Re: Creating a Circuit ID Format Tassos Chatzithomaoglou (Aug 22)
- Re: Creating a Circuit ID Format Jared Mauch (Aug 22)
- Re: Creating a Circuit ID Format Allan Eising (Aug 24)
- Re: Creating a Circuit ID Format William Herrin (Aug 24)
- RE: Creating a Circuit ID Format Jameson, Daniel (Aug 24)