Guidelines for Writing an IANA Considerations Section in RFCs
RFC 8126 also known as BCP 26

Received changes through RFC Editor sync (changed abstract to 'Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).

To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.

This is the third edition of this document; it obsoletes RFC 5226.')

Received changes through RFC Editor sync (created alias RFC 8126, changed abstract to 'Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).', changed pages to 47, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2017-06-20, changed IESG state to RFC Published, created obsoletes relation between draft-leiba-cotton-iana-5226bis and RFC 5226)