[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: spc connections



Title: [전체회신] Re: [ AuA¼E¸½A ] spc connections
Hi John,
 
I apologize for being an uninformed reader :o)  As such I can only rely on the text in
3473, which is very specific and does not discuss SPC labels.
 
It probably seems intuitively very obvious to you because you have had this in mind
for a while.  It is not necessarily obvious from all points of view.  I see a reasonable
case to be made that an SPC label, being passed down from the management system,
should be in a separate object from the ERO, which may typically be calculated by the
source endpoint rather than passed down from the management system.
 
Cheers,
 
Lyndon
-----Original Message-----
From: John Drake [mailto:jdrake@calient.net]
Sent: Friday, November 14, 2003 12:48 PM
To: Ong, Lyndon; 'yhwkim@etri.re.kr'; jonathan.sadler@tellabs.com
Cc: adrian@olddog.co.uk; kireeti@juniper.net; ccamp@ops.ietf.org
Subject: RE: spc connections

Lyndon,
 
This will be my last post on this topic.
 
I helped write RFC3471 and RFC3473, and SPC support was always an integral part of them, as Adrian's note informed  you.
 
If you are referring to your original question on this topic, I think the proper response is that it should be blindingly obvious to the informed reader that the egress node doesn't have to put the explicit label for the next hop into a Label Set in the outgoing Path message, because there is no outgoing Path message. 
 
Thanks,
 
John