draft-ietf-idr-as-pathlimit-00.txt

Tony Li, et al,

	1) Do I implicitly read that this new will also
	   limit looping paths to AS_PATHLIMIT?

	2) 5.1 Operations
   If the
   AS_PATHLIMIT value exceeds the number of ASes found in the AS_PATH,
   then the route should not be sent.

	I must be dsylexic, I would think that you want the number of
	ASs found to be less or equal to the AS_PATH_LIMIT,

	Thus...

	If the number of ASs found in the AS_PATH exceeds the
        AS_PATHLIMIT value, then the route should not be forwarded.

	As this also seems backward..

	If the attribute value exceeds the number of ASes in the
   AS_PATH, then the route MUST be ignored without further processing.

	3a) Stupid question.

	  Why isn't this AS_PATHLIMIT decremented at each BGP speaker
	  who would examine the route, and when it reaches 0, then
	  the route would be dropped?

	3b) Another stupid question

	   What prevents a BGP speaker from changing this value? Why
	   would a speaker want to change the value or why shouldn't
	   a speaker change this value?

	  Mitchell Erblich
	

Tony Li wrote:
> 
> Hi all,
> 
> Surprisingly, my mailbox wasn't full this morning.  For those that
> didn't notice, the next revision of the AS_HOPCOUNT draft (now
> AS_PATHLIMIT) has been released.  Here's the link:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-idr-as-pathlimit-00.txt
> 
> Please comment now...  Given our previous discussions, I can't believe
> that there are no further comments.  
> 
> Regards,
> Tony
> 
> _______________________________________________
> Idr mailing list
> Idr <at> ietf.org
> https://www1.ietf.org/mailman/listinfo/idr

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www1.ietf.org/mailman/listinfo/idr