>>> "Operators are recommened not to use "set community" or "community
>>> set" and just explicitly remove/add what needs to be done.
>>
>> do all vendors support wildcards?
>
> Yes, I think so. Of the top of my head you can wilcard on Junos, Cisco
> Classic/XE/XR, OpenBGPD, BIRD, Brocade
On Mon, Jun 11, 2018 at 04:59:49PM -0700, Randy Bush wrote:
> > "Operators are recommened not to use "set community" or "community
> > set" and just explicitly remove/add what needs to be done.
>
> do all vendors support wildcards?
Yes, I think so. Of the top of my head you can wilcard on Junos,
> "Operators are recommened not to use "set community" or "community
> set" and just explicitly remove/add what needs to be done.
do all vendors support wildcards?
randy
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow
Hi all,
On Mon, Jun 11, 2018 at 08:59:39PM +, Job Snijders wrote:
> The authors of draft-ymbk-grow-wkc-behavior [1] requested the chairs to
> consider issuing a call for working group adoption. Here is the
> abstract:
>
> "Well-Known BGP Communities are manipulated inconsistently by
>
Dear working group,
The authors of draft-ymbk-grow-wkc-behavior [1] requested the chairs to
consider issuing a call for working group adoption. Here is the
abstract:
"Well-Known BGP Communities are manipulated inconsistently by
current implementations. This results in difficulties for
Hi Folks!
GROW is planning to meet in Canada at IETF 102, iff we have agenda
items. People who would like time on the agenda please send a request
so that a time slot and agenda can be prepared!
Presentation proposals with drafts will have priority over talks
without an uploaded draft.
Kind
