Re: [RPSEC] Basis of Requirements?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>Well, the _intent_ of the document is that the AS_PATH contain _all_
>>of the ASes.  This is obviously necessary for loop avoidance.

> Yes, as Russ White et all say in draft-white-pathconsiderations-05.txt:

>>path vector
>>protocols, such as [BGP], prove a path is loop free by carrying a
>>list of nodes the advertisement itself has traversed.

Note it doesn't say, anyplace that I can find, that the AS Path 
constitutes an "authorization chain," and such thing. Yes, it does prove 
loop freeness, as I've said many times before. Receiving a route with 
NLRI X doesn't prove that every AS given in the AS Path has authorized 
the transiting of traffic to every destination within the address block, 
as the draft mentioned also shows.

:-)

Russ

- -- 
riw@cisco.com CCIE <>< Grace Alone

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.0.2 (Build 2424)

iQA/AwUBQzqRIBEdu7FIVPTkEQI4bACg6niAKJ7vzTHtS5zmBGeZoUtSu8UAnizk
77kN2XBkTs/jFozg+4/kEH9y
=whho
-----END PGP SIGNATURE-----

_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www1.ietf.org/mailman/listinfo/rpsec