Updates to the Allocation Policy for the Border Gateway Protocol - Link State (BGP-LS) Parameters Registries
obsoleted by
- rfc-9552 — Distribution of Link-State and Traffic Engineering Information Using BGP
updates
- rfc-7752 — North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Extracted elements (10)
The allocation policy was changed from 'Specification Required' to 'Expert Review' to remove the requirement that values be documented in a permanent, publicly available formal specification. Under Expert Review, code points may be allocated based on technical documentation that need not take the form of a finalized RFC, lowering the barrier for extensions while retaining expert oversight.
Applications for code point allocation MUST be accompanied by technical documentation explaining the use of the code point. Such documentation SHOULD be presented as an Internet-Draft but MAY arrive in any reviewable form.
Designated experts MUST review assignment requests on their technical merit and MAY raise issues with authors or on the IDR mailing list before assignments are made.
Designated experts SHOULD only consider requests arising from Internet-Drafts already accepted as working group documents or planned for progression as AD-Sponsored documents in the absence of a suitably chartered working group.
For working group documents, designated experts MUST verify with WG chairs that there is working group consensus to make the allocation. For AD-Sponsored documents, experts MUST obtain approval from the responsible AD before making the allocation.
If a working group or AD-Sponsored document fails to progress to RFC publication, the WG chairs or AD SHOULD contact IANA to mark the allocated code points as deprecated. Deprecated code points are not available for new allocation but may be fully deallocated by WG chairs if a shortage of unallocated code points exists.
If the document is not adopted by the IDR Working Group, the designated expert MUST notify the IDR mailing list of the request, MUST provide access to the document, and MUST allow two weeks for any response before proceeding. All comments received MUST be considered.
The designated expert MUST ensure that any request for a code point does not conflict with work that is active or already published within the IETF.
IANA's 'Border Gateway Protocol - Link State (BGP-LS) Parameters' registry and its four subregistries — BGP-LS NLRI-Types, BGP-LS Protocol-IDs, BGP-LS Well-Known Instance-IDs, and BGP-LS Node Descriptor/Link Descriptor/Prefix Descriptor/Attribute TLVs — have had their allocation policy changed from 'Specification Required' to 'Expert Review'.
Relaxing the allocation policy to Expert Review makes the registry and designated experts slightly more vulnerable to denial-of-service attacks via excessive or bogus code point requests. Designated experts are expected to report suspected attacks to IDR WG chairs and the responsible AD and should immediately halt all allocation requests until mitigations are in place, which may temporarily block legitimate requests.