Hi Jeffrey & Havard
Thank you for the comments.
The goal of 3.1 was to graphically depict the how excess as-path prepending
and how that could yield or exacerbate prefix hijacking impact downstream
consumers of pretending as you stated with ripple effect where a desirable
source origin AS becomes
I support Hávard's observations.
I'd also like to comment that the notation of "prepends 5" meaning "5 + 1" is a
bit confusing for all of the examples. Consider instead just saying what the
announced as-path length is. Operators prepend 5 because their intent is
"announce 6". :-)
Rather tha
Hi,
here are a few comments about section 3.1 in the draft:
Other than the missing comma in the list of routers/ASes, near
the end there is talk about a route leak. However, I don't think
what's stated here as a route leak is what's commonly understood
to be a route leak.
I think a route leak i
To: i-d-annou...@ietf.org
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-as-path-prepending-06.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Global Routing Operations WG of the IETF.
Title : AS
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Global Routing Operations WG of the IETF.
Title : AS Path Prepending
Authors : Mike McBride
Doug Madory
