Hi Mike, I would like to join you guys to work on this. I work for HPE Networking. Please let me know next actions, meetings, etc.
Thanks, Hongwei Li > On Jul 26, 2020, at 6:38 PM, Michael McBride <michael.mcbr...@futurewei.com> > wrote: > > Thank you all for the helpful comments. We will update the draft over the > next few weeks and send to you for further review. If anyone cares to join us > as an author please let us know. > > And yes Robert, perhaps we can eventually conclude that if you do prepending > then do X but that we discourage prepending by instead doing Y. > > mike > > -----Original Message----- > From: Nick Hilliard <n...@foobar.org> > Sent: Sunday, July 26, 2020 1:59 PM > To: Michael McBride <michael.mcbr...@futurewei.com> > Cc: grow@ietf.org > Subject: Re: [GROW] AS_Path prepend BCP > > Michael McBride wrote on 26/07/2020 19:42: >> We have submitted >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata >> tracker.ietf.org%2Fdoc%2Fdraft-mcbride-grow-as-path-prepend%2F&dat >> a=02%7C01%7Cmichael.mcbride%40futurewei.com%7C23a5d643a0804b71ff1908d8 >> 31a6c523%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C6373139396290344 >> 10&sdata=IpTVh2AVylhnMb94MROGNtVMxuguov16bpXBHwdvT%2Fs%3D&rese >> rved=0 which is intended to be a bcp in the use of AS_Path prepend >> based on work of Doug Madory. As we state in the intro: AS_Path >> prepending is discussed in Use of BGP Large Communities [RFC8195] and >> this document provides additional, and specific, guidance to operators >> on how to be a good internet citizen with the proper use of AS_Path >> prepend. >> >> We would encourage feedback on this document. > > Good start - but needs work! > > some suggestions: > > - it would be useful to have a histogram or table of the frequency of > unique-aspath lengths (i.e. with all prepending flattened). This would help > contextualise the best practice recommendation. > > - +1 on randy's comments about de-nationalising and providing examples of why > recommended good practice is good practice. > > - a BCP should be as relevant and fresh in 10 years time as it is today, so > imagine it's 2030 and you're reading the draft: plenty of things in it need > to be made insensitive to time context. E.g. 95.47.142.0/23 might be held by > a Guatamalan company in 10 years time, AS174 might be assigned to > NTTCogentCentury and AS6939 might be Hurricane Equinix. You never know. > > - it would be useful to give advice on how to measure the effectiveness of > prepending in terms of remote global visibility. > > Nick > > _______________________________________________ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow _______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
