> On Feb 18, 2022, at 12:30 PM, Randy Bush <ra...@psg.com> wrote: > >> >> * 32-bit ASNs don't fit in 16-bit fields. Consider using a set of >> Extended Communities? > > next you're gonna want ipv6; sheesh! :) > > i think the draft tried to finesse and not get into wire format. but it > probably should. > > extended or wide?
If your semantics will happily fit into 6 bytes, extended would work okay for you. Implementations that support extended communities often let you configure such things even if they're not "well known". https://www.rfc-editor.org/rfc/rfc5668.html <https://www.rfc-editor.org/rfc/rfc5668.html> You'd probably just want to ask for a new sub-type for this using the transitive version of the type, and then put the semantics in the local-admin. Most of the range is defined first come, first served so it's trivial to get an assignment without a lot of work. https://www.iana.org/assignments/bgp-extended-communities/bgp-extended-communities.xhtml#trans-four-octet-as -- Jeff
_______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
