[Speaking as an individual contributor.] Prepending has been around for ages and it's well understood at this point in how it behaves.
An older version of the grow prepending document was nicely clear as to why excess prepending was problematic. From that perspective, the document was useful. More recent versions of the document have muddied its clarity. I don't find it needful that BGP protocol documents reference this document in particular. -- Jeff > On Feb 10, 2022, at 4:53 PM, Keyur Patel <ke...@arrcus.com> wrote: > > [Sending it to IDR & GROW] > > Hi Folks, > > IDR is requesting input on the use of AS prepend in BGP policy. This begins a > 2 week call for requested input on the beneficial use of AS Prepend. > draft-ietf-grow-as-path-prepending-05.txt indicates there is a risk in > excessive prepending. In section 5, this draft suggests there is no need to > prepend more than 5 ASN in an AS Pathway by a single AS. Is this > recommendation firm or likely to change? Should a comment be added to the > draft-ietf-rpd-15.txt security section to point to the > draft-ietf-grow-as-path-prepending-05.txt draft? > > The RPD draft can be found at: > https://datatracker.ietf.org/doc/html/draft-ietf-idr-rpd > <https://datatracker.ietf.org/doc/html/draft-ietf-idr-rpd>. The AS Path > Prepending draft can be found > at:https://datatracker.ietf.org/doc/html/draft-ietf-grow-as-path-prepending > <https://datatracker.ietf.org/doc/html/draft-ietf-grow-as-path-prepending>. > This call will end on Feb 24th 2022. > > Best Regards, > Keyur > > _______________________________________________ > GROW mailing list > GROW@ietf.org <mailto:GROW@ietf.org> > https://www.ietf.org/mailman/listinfo/grow > <https://www.ietf.org/mailman/listinfo/grow>
_______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
