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

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



Remi,

By not changing the encoding rules of sub-TLVs within a given TE LSA that rule has to be relaxed in the sense "The node attribute TLV must appear in exactly one TE LSA originated by a --TE-- router.". 

Thanks,
-dimitri.
________________________________

	From: Remi Theillaud [mailto:remi.theillaud@marben-products.com] 
	Sent: Tuesday, April 14, 2009 4:37 PM
	To: PAPADIMITRIOU Dimitri
	Cc: ccamp@ops.ietf.org
	Subject: Re: One question about draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt
	
	
	   Dimitri,
	
	   I understand the sentence "The node attribute TLV must appear in exactly one TE LSA originated by a router." as meaning that a router is not allowed to originate multiple LSAs specifying a node attribute TLV.
	
	   Thanks for your quick answers,
	   Rémi
	
	
	-------- Original Message --------
	Subject: Re: One question about draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt
	From: PAPADIMITRIOU Dimitri <Dimitri.Papadimitriou@alcatel-lucent.be> <mailto:Dimitri.Papadimitriou@alcatel-lucent.be> 
	To: Remi Theillaud <remi.theillaud@marben-products.com> <mailto:remi.theillaud@marben-products.com> 
	CC: ccamp@ops.ietf.org
	Date: 14/04/2009 16:28
	

		Don't we say the same thing ? Quoting this doc.:
		 
		 " The node attribute TLV must appear in exactly one TE LSA originated
		   by a router. Further only one node attribute TLV must be advertised
		   in such a LSA. A node attribute TLV must carry at most one Node IPv4
		   Local Address sub-TLV and at most one Node IPv6 Local Address sub-
		   TLV."
		 
		Hence, to your question:
		
		  

			Should a Local TE Router-ID sub-TLV be encoded 
			*before* each Node IPv4/IPv6 Local Prefix Sub-TLV? 
			    

		
		it is a one to one correspondance in each of these LSAs.
		-d.
		
		
		  

			-----Original Message-----
			From: Remi Theillaud [mailto:remi.theillaud@marben-products.com] 
			Sent: Tuesday, April 14, 2009 4:23 PM
			To: PAPADIMITRIOU Dimitri
			Cc: ccamp@ops.ietf.org
			Subject: Re: One question about 
			draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt
			
			
			   Hi Dimitri,
			
			   I thought about it, but 
			draft-ietf-ospf-te-node-addr-05.txt section 
			4.2 states "The node attribute TLV must appear in exactly one TE LSA 
			originated by a router. Further only one node attribute TLV must be 
			advertised in such a LSA." So it does seem possible for a router to 
			advertise multiple LSAs specifying a node attribute TLV.
			
			   Thanks,
			   Rémi
			
			
			-------- Original Message --------
			Subject: Re: One question about 
			draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt
			From: PAPADIMITRIOU Dimitri <Dimitri.Papadimitriou@alcatel-lucent.be> <mailto:Dimitri.Papadimitriou@alcatel-lucent.be> 
			To: Remi Theillaud <remi.theillaud@marben-products.com> <mailto:remi.theillaud@marben-products.com> , 
			ccamp@ops.ietf.org
			Date: 14/04/2009 16:06
			    

				hi remi: the encoding follows 
				      

			http://www.ietf.org/internet-drafts/draft-ietf-ospf-te-node-ad
			dr-05.txt 
			<http://www.ietf.org/internet-drafts/draft-ietf-ospf-te-node-a
			ddr-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 
					
				
				
				  
				      

			-- 
			
			------------------------------------------
			
			Rémi Theillaud
			Senior Consultant
			
			Marben Products
			176 rue Jean Jaures
			92800 Puteaux
			France
			
			Tel : +33 (0)1 7962 1022
			Fax : +33 (0)1 7962 1001
			remi.theillaud@marben-products.com
			www.marben-products.com  
			
			
			    

		
		  


	-- 
	
	------------------------------------------
	
	Rémi Theillaud
	Senior Consultant
	
	Marben Products
	176 rue Jean Jaures
	92800 Puteaux
	France
	
	Tel : +33 (0)1 7962 1022
	Fax : +33 (0)1 7962 1001
	remi.theillaud@marben-products.com
	www.marben-products.com