In a message written on Thu, Sep 29, 2011 at 09:27:57AM -0400, Danny McPherson wrote: > I never said "does not require any pre-knowledge". As a matter of fact, > what I said, and what the draft says, is that with unique origins the > services operator _could publish in a well-known location a list of origin > ASNs for a given prefix and the feasible adjacent upstreams for each ASN. > With that information network operators can make informed decisions about > the legitimacy of a new path in the routing system for a critical Internet > services prefix.
Ok, fair enough. So let's ask the direct question: Would it not be even better then for them to have a unique origin ASN, and publish the list of paths that originate the route, achieving the same result without needing to have an inconsistent origin? Seems like that would be a quick change to the draft... And couldn't the entire draft thus be greatly simplifed to a single paragraph? Anycast operators SHOULD publish a list of all valid AS-Paths to reach their Anycast service to aid in the detection of routing leaks. I suppose bonus points if we could agree on a method for publishing (RPSL?). -- Leo Bicknell; E-mail: [email protected], Phone: +1 650 423 1358 INOC*DBA *3357*592; Internet Systems Consortium, Inc. www.isc.org _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
