RE: One question about draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt

["PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>]

hi remi: the encoding follows http://www.ietf.org/internet-drafts/draft-ietf-ospf-te-node-addr-05.txt <http://www.ietf.org/internet-drafts/draft-ietf-ospf-te-node-addr-05.txt>; hence, you will find only one TE Router ID sub-TLV (together with one Node IPv4 / IPv6 Local Prefix sub-TLV) per top level node attribute TLV per opaque LSA and have multiple TE LSAs.
 
thanks,
-dimitri.


________________________________

	From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org] On Behalf Of Remi Theillaud
	Sent: Tuesday, April 14, 2009 3:43 PM
	To: ccamp@ops.ietf.org
	Subject: One question about draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt
	
	

	  Hi CCAMP, 
	
	  One question about draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt. 
	  This draft defines a new Node-Attribute sub-TLV (Local TE Router-ID sub-TLV) as "optional sub-TLV for scoping reachability per TE Router-ID". 
	  How does this scoping occur when a router advertises reachability information on behalf of multiple TE Router IDs? 
	  Should a Local TE Router-ID sub-TLV be encoded *before* each Node IPv4/IPv6 Local Prefix Sub-TLV? 
	  
	  Regards, 
	  Rémi