I think we do need to be a little careful about what the AS path
"always" meant, and what we are going to end up with it meaning if we
follow the path and discussion.
For example, there is long practice of adding not just ones own AS, but
sometimes other AS numbers to a path for policy reasons. In that usage,
it does not represent "the AS that propagated the update."
It may well be that it is acceptable to eliminate that usage.
An AS Set does not mean that the advertisement went through all of those
AS. (Admittedly, we are probably just going to ban sets.)
Folks tell all sorts of lies if they implement various kinds of
multi-pathing.
It is reasonable to say that we are going to give up some of the
flexibility the tool has had in order to get better verifiability of
certain specific properties.
But we should understand that we are indeed changing the semantics when
we do so.
Yours,
Joel
On 2/21/2011 3:13 PM, Sandra Murphy wrote:
...
The AS_PATH has always been intended to represent the ASs that
propagated the update.
The AS_PATH can be used to detect loops ONLY because it does represent
the ASs that propagated the update.
--Sandy
:-)
Russ
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
