> > >> 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 information and heavily rely on "set community" == 'delete'.
> But... at the same time those same carriers are interested in honoring
> GRACEFUL_SHUTDOWN.
>
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" policy, but it did.
Clearly "set community foo" is not appropriate for use on many classes
of connections -- e.g. on connections to one's customers -- but where
it is used it should not cause surprises.
Jay B.
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
