> IOS XR: "set community X" removes _all_ except WKC, and sets X
^ some
randy
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow
On 01-03-18 13:50, Job Snijders wrote:
> On Wed, Feb 28, 2018 at 09:52:50PM -0500, Jay Borkenhagen wrote:
>> For what it's worth, I first noticed the special treatment of some
>> well-known communities after Job announced his GRACEFUL_SHUTDOWN
>> beacon prefix. I expected that it would not have pa
On Wed, Feb 28, 2018 at 09:52:50PM -0500, Jay Borkenhagen wrote:
> For what it's worth, I first noticed the special treatment of some
> well-known communities after Job announced his GRACEFUL_SHUTDOWN
> beacon prefix. I expected that it would not have passed intact
> through a "set community foo"
>> did you even know this was happening, that "set community" might
>> not replace ALL well known communities?"
>
> No, as in, "I assumed that 'set community' would stamp the communities
> listed onto the prefix, and replace everything already there".
jay was shocked when he discovered it, and i
Hi,
On Thu, Mar 01, 2018 at 09:52:37AM +0900, Randy Bush wrote:
> question for ops:
>
> did you even know this was happening, that "set community" might not
> replace ALL well known communities?"
No, as in, "I assumed that 'set community' would stamp the communities
listed onto the prefix, a
> Trouble with WKC is that some you want to remove, some you want to
> honor, and some you just want to pass-through without taking any
> action.
and, if i was of that mind, i would want to decide which, not have the
vendors do so.
> "set community" isn't a great fit for cherry-picking.
nor is
> > >> i did not realize this was going on. jay, who discovered it, was
> > >> surprised.
> > >
> > > NTT noticed this type of inconsistency between some vendors somewhere
> > > in July 2016. [...]
[...]
> I know of other carriers who are not interested in preserving any
> community inf
On Thu, Mar 01, 2018 at 10:54:08AM +0900, Randy Bush wrote:
> >> question for ops:
> >>
> >> did you even know this was happening, that "set community" might not
> >> replace ALL well known communities?"
> >>
> >> the reasom i ask is, as you see in the draft, we are hesitant to
> >> propose chang
>> question for ops:
>>
>> did you even know this was happening, that "set community" might not
>> replace ALL well known communities?"
>>
>> the reasom i ask is, as you see in the draft, we are hesitant to
>> propose changing behavior for existing wks as it might impact ops.
>> but if we were no
On Thu, Mar 01, 2018 at 09:52:37AM +0900, Randy Bush wrote:
> question for ops:
>
> did you even know this was happening, that "set community" might not
> replace ALL well known communities?"
>
> the reasom i ask is, as you see in the draft, we are hesitant to
> propose changing behavior for exis
question for ops:
did you even know this was happening, that "set community" might not
replace ALL well known communities?"
the reasom i ask is, as you see in the draft, we are hesitant to propose
changing behavior for existing wks as it might impact ops. but if we
were not aware of this beh
Hi authors,
This is an excellent initiative.
Kind regards,
Job
On Tue, Feb 27, 2018 at 09:13:31AM -0800, internet-dra...@ietf.org wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> Title : Well-Known Community Policy Behavior
12 matches
Mail list logo
