Indeed carving out some chunks of ASN space is a hack. But why not simply request a new attribute value and do not reserve anything ? This time do it properly and encode the structure in it.
Thx, Robert On Sat, Jun 8, 2024 at 6:41 PM Jeffrey Haas <[email protected]> wrote: > > > > On Jun 8, 2024, at 11:54 AM, Sriram, Kotikalapudi (Fed) < > [email protected]> wrote: > > > > Some of us may remember this (including Sue and Jeff). Jakob Heitz, I, > and others have proposed/presented (in the IDR WG) the idea of a range of > IANA-registered 4-octet ASN values for the Global Admin field to classify > BGP Well Known Large Communities (WKLC). > > See: https://datatracker.ietf.org/doc/draft-heitz-idr-wklc/ [1] > > > > The above draft was motivated in part by the following GROW WG draft's > request plus possible other use cases for WKLC: > > > https://datatracker.ietf.org/doc/draft-ietf-grow-route-leak-detection-mitigation/ > [2] > > > > Our idea was critiqued for requesting 64M 4-octet ASN values to be set > aside by IANA for WKLC. That is only 64 million out of the 4 Billion (a > fraction 0.015) 4-octet ASNs. This can be reduced easily to 256K out of the > 4 Billion (a fraction 0.00006) if that is acceptable. There would be 9 > octets available in the WKLC for the data part. The 256K number can be > further reduced to 1K if desired (with 8 octets available in the WKLC for > the data part). > > > > Details can be found in the above cited draft [1]. We can discuss > further the possibilities if this approach gets some traction. Thanks. > > Please let the proposal stay dead. Carving up the globally visible BGP AS > space with too many "this is special" numbers is a bad idea. > > > > -- Jeff > > _______________________________________________ > GROW mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
