At 11:35 AM -0500 2/18/11, Russ White wrote:
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enigEEE752FC731D9F82CF768B1F"
* Is an Autonomous System (AS) authorized to originate an IP prefix
> * Is the AS-Path represented in the route the same as the path
through which the route update traveled
As we've been discussing on the list --I don't think this is a good
goal. The first goal should be to determine what it is we want to show
about the AS Path in relation to other things, and then work on filling
that goal.
Starting with the assumption that proving an update travels a specific
path seems, to me, to be going about things the wrong way.
:-)
Russ
Some folks have observed that ASes may make decisions about accepting updates
based on AS path info. That, by itself, motivates securing the AS
path info in an update, irrespective of any other motivations.
Steve
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr