Re: [RPSEC] BGP Security Requirements v08

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

In a separate email, and with my WG chair hat _off_....

> Maybe it's useful to break this into two questions?
> 
> 1. Is information about the authorization of an originator to advertise
> reachability useful to AS' on the "other side" of a non-supporting AS?
> 
> 2. Is information about the validity of an AS path useful to AS' on the
> "other side" of a non-supporting AS?

IMHO, as an individual, I believe both of these pieces of information
are useful. I believe the origin authorization information is really
useful, along with the first hop (or second hop, depending on your point
of view) of the AS Path. The subsequent hops of the AS path are less
interesting than these two to the receiver on the "other side" of a
non-supporting AS.

Why? Because if you can validate the originator and the first (second)
hop (the second entry in the AS Path), then you have a good bit more
assurance the destination is valid/etc, than if you just drop this
information out.

:-)

Russ

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGlN0PER27sUhU9OQRAuiZAJ4v/z6YbmRkrZrtOoyCdkmgTAfYWgCgkbFu
ViW1S1+MF8ykjh3AhBYjPJk=
=/e4u
-----END PGP SIGNATURE-----

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