The MPLS WG Archive

[Fong Liaw <FLiaw@zaffire.com>]

Hi, Diego

The official name for ligthpath ID is now "Connection_ID".
We are still discussing (among authors) how this
object should be used and therefore where it should
show up in the messages.  Right now, we don't have
a clear definition of these from the requirement
but this will hopefully be resolved between the
carrier group in OIF and the signaling group authors soon.

Right now our proposal is the following:

"The Connection_ID object will be an optional
object in all RSVP messages. However, once a 
Connection_ID is assigned by the network, 
a user node MUST carry the object in every 
subsequent RSVP message it generates."
 
This phrase gives network the freedom of generating
or not generating a Connection_ID, and if they do 
generate one, a user node will play it back to 
the network.  A connection is still identified by
RSVP Session object, at the UNI. 

-Fong

>  -----Original Message-----
>  From: Diego Caviglia [mailto:Diego.Caviglia@marconi.com]
>  Sent: Thursday, November 30, 2000 5:54 AM
>  To: mpls@UU.NET
>  Subject: draft-yu-mpls-rsvp-oif-uni-00
>  
>  
>  
>  
>  Fong,
>                 I've seen that w.r.t. the OIF version of this 
>  draft a Lightpath
>  ID object is introduced but in the message definition I 
>  can't find it.
>  
>  If it is not a mistake, could someone explain in wich 
>  message Lightpath ID must
>  be inserted?
>  
>  Regards Diego.
>  
>