Just to clarify one subtle point. In wide communities types are either operator assigned or IANA driven - no new code from vendor is required in contrast to extended community. That along with variable length is what makes wide communities universal.
Sure that some vendors or individuals are scared about policy aspect of wide communities processing - but implementing policy handling any arbitrary types (irrespective of IANA or local assignment) is optional. - - - To the topic of using Large Communities - I do recommend whichever encoding is chosen to always be able to insert and carry originator's ASN. All zeros are meaningless read: anonymous. Thx, R. On Wed, Feb 5, 2020 at 2:45 AM Brian Dickson <[email protected]> wrote: > Disagree, we want something deployed (large) and deployable (requiring > only IANA action, no vendor activity) immediately. > IMHO, any special handling or new code points or upgrades are non-starters. > This particularly applies to wide and extended > Brian > > On Tue, Feb 4, 2020 at 5:41 PM Dongjie (Jimmy) <[email protected]> > wrote: > >> Agree that for this case it may be more convenient to just use extended >> community with a new type, this could avoid any possible collision with >> existing deployments, and save the effort of assigning a set of ASNs. Wide >> community may be too powerful for this:) >> >> >> >> Best regards, >> >> Jie >> >
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
