Subject: [Geopriv] RE: [Ecrit] Circuit ID

From: "Winterbottom, James" <[email-masked]>
Date: Mon, 7 May 2007 19:11:12 -0500

DSL Forum document TR-101 describes this in detail I think.

Cheers
James

> -----Original Message-----
> From: Stark, Barbara [mailto:[email-masked]]
> Sent: Friday, 27 April 2007 1:20 AM
> To: Stark, Barbara; Clive D.W. Feather; Henning Schulzrinne
> Cc: GEOPRIV; ECRIT
> Subject: RE: [Ecrit] Circuit ID
> 
> It turns out I was wrong about the Circuit ID and RADIUS. I just can't
> seem to keep up with the architecture changes going on.
> Yes, in newer equipment, the Access Node (DSLAM) adds the Circuit ID
to
> both DHCP and PPP protocols. This is copied into the message sent to
> RADIUS.
> Barbara
> 
> -----Original Message-----
> From: Stark, Barbara
> Sent: Wednesday, April 25, 2007 11:28 AM
> To: Clive D.W. Feather; Henning Schulzrinne
> Cc: GEOPRIV; ECRIT
> Subject: RE: [Ecrit] Circuit ID
> 
> Circuit IDs have nothing to do with RADIUS, that I'm aware of.
> "Circuit ID" format is defined by whatever system an access company
uses
> to manage its inventory of circuits. The most common such system in
the
> US is TIRKS(R), which is now developed by Telcordia. It was initially
> developed by AT&T Bell Labs in the late 1970's. Fortunately, it has
> managed to evolve a bit since then. Most of the baby Bells continue to
> use it, I think.
> There's a really short Wikipedia description of TIRKS at
> http://en.wikipedia.org/wiki/TIRKS
> In short, a Circuit ID uniquely identifies a circuit within an access
> provider's operations systems. Many different types of circuits exist
> (POTS, T1, DS3, SONET, etc.). Different types use different formats.
> Barbara
> 
> -----Original Message-----
> From: Clive D.W. Feather [mailto:[email-masked]]
> Sent: Wednesday, April 25, 2007 4:37 AM
> To: Henning Schulzrinne
> Cc: Stark, Barbara; GEOPRIV; ECRIT
> Subject: Re: [Ecrit] Circuit ID
> 
> Henning Schulzrinne said:
> > Just out of curiosity, what does a circuit ID look like? Is that the
> > NAS identifier used in RADIUS or where is it visible?
> 
> In the UK it's not currently standardised, though we're looking at it.
I
> would *expect* it to end up something like BT-EA12345678 or
> 001-EA12345678 where the first part identifies the circuit owner
(either
> a short name or a
> CUPID) and the second half is decided by the provider; BT appear to
use
> a two letter region code followed by an 8 digit number).
> 
> >> Actually, given requirements for "naked" DSL, without an underlying
> >> POTS phone number, we're moving to "Circuit ID".
> 
> That's not the only scenario - the UK is looking at an arrangement
> whereby one telco (Openreach, part of BT) provides the circuit and
> another telco provides the call server and thus the number; Openreach
> and BT will have no visibility of the number - if any - allocated to
the
> line.
> 
> --
> Clive D.W. Feather  | Work:  <[email-masked]>   | Tel:    +44 20 8495
> 6138
> Internet Expert     | Home:  <[email-masked]>  | Fax:    +44 870 051
> 9937
> Demon Internet      | WWW: http://www.davros.org | Mobile: +44 7973
> 377646
> THUS plc            |                            |
> 
> *****
> 
> The information transmitted is intended only for the person or entity
to
> which it is addressed and may contain confidential, proprietary,
and/or
> privileged material. Any review, retransmission, dissemination or
other
> use of, or taking of any action in reliance upon this information by
> persons or entities other than the intended recipient is prohibited.
If
> you received this in error, please contact the sender and delete the
> material from all computers. GA623
> 
> 
> 
> _______________________________________________
> Ecrit mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/ecrit
> 
> _______________________________________________
> Ecrit mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/ecrit

------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]

_______________________________________________
Geopriv mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/geopriv