Re: [GROW] Choice of Large vs. Extended Community for Route Leaks Solution

2021-04-02 Thread Sriram, Kotikalapudi (Fed)
Jakob, Thanks. I was expecting this question. We will work on a recursive path analysis to answer it. Brian's suggestion also will be considered. The data crunching may take a week or so. My hunch was that when the AS path length is 5 or 6 or more, the ASes at the far end (most recently added)

Re: [GROW] Choice of Large vs. Extended Community for Route Leaks Solution

2021-04-01 Thread Jakob Heitz (jheitz)
When the collector sees a route with AS-PATH length 5 with a community on it, that does not imply that the community traveled through 5 AS hops. The community could have been added at any of the ASes in the path. Where does the data show that any communities transited any AS boundaries? Regards

Re: [GROW] Choice of Large vs. Extended Community for Route Leaks Solution

2021-04-01 Thread Brian Dickson
On Thu, Apr 1, 2021 at 2:06 PM Sriram, Kotikalapudi (Fed) < kotikalapudi.sri...@nist.gov> wrote: > There may be a knob that AS operators have for permitting transitivity, > but we need to look at measurements to understand whether or not operators > actually allow transitivity to EC and LC. > > NI

Re: [GROW] Choice of Large vs. Extended Community for Route Leaks Solution

2021-04-01 Thread Sriram, Kotikalapudi (Fed)
There may be a knob that AS operators have for permitting transitivity, but we need to look at measurements to understand whether or not operators actually allow transitivity to EC and LC. NIST BGP measurements (thanks to my colleague Lilia Hannachi) were shared on the GROW list in May 2020: ht

Re: [GROW] Choice of Large vs. Extended Community for Route Leaks Solution

2021-04-01 Thread Brian Dickson
On Thu, Apr 1, 2021 at 6:11 AM Jeffrey Haas wrote: > [Note, commenting as an individual contributor...] > > On Wed, Mar 31, 2021 at 03:10:08PM -0700, Brian Dickson wrote: > > On Wed, Mar 31, 2021 at 7:57 AM Sriram, Kotikalapudi (Fed) < > > kotikalapudi.sri...@nist.gov> wrote: > > > We (authors of

Re: [GROW] Choice of Large vs. Extended Community for Route Leaks Solution

2021-04-01 Thread Sriram, Kotikalapudi (Fed)
Brian, >We would like to continue proceeding with use of a LC range for >implementation, using a single (or small number) of Global Administrator >values. I should have clarified. I am not opposed to staying on course with a WKLC based solution. I only thought transitivity readily came with Tr

Re: [GROW] Choice of Large vs. Extended Community for Route Leaks Solution

2021-04-01 Thread Jeffrey Haas
[Note, commenting as an individual contributor...] On Wed, Mar 31, 2021 at 03:10:08PM -0700, Brian Dickson wrote: > On Wed, Mar 31, 2021 at 7:57 AM Sriram, Kotikalapudi (Fed) < > kotikalapudi.sri...@nist.gov> wrote: > > We (authors of the WKLC draft) can continue working on creating an IANA > > WK

Re: [GROW] Choice of Large vs. Extended Community for Route Leaks Solution

2021-03-31 Thread Brian Dickson
On Wed, Mar 31, 2021 at 7:57 AM Sriram, Kotikalapudi (Fed) < kotikalapudi.sri...@nist.gov> wrote: > Hi Sue, > > Thanks for the detailed thoughts you have shared on the IDR list about the > WKLC draft and route leaks solution draft (while also responding to Brian’s > post). > > At one point in the

[GROW] Choice of Large vs. Extended Community for Route Leaks Solution

2021-03-31 Thread Sriram, Kotikalapudi (Fed)
Hi Sue, Thanks for the detailed thoughts you have shared on the IDR list about the WKLC draft and route leaks solution draft (while also responding to Brian’s post). At one point in the past, the route leaks solution needed 8 bytes of user data space to accommodate two ASNs but then there was a