<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.baber-ianabis-rfc8126bis" target="https://datatracker.ietf.org/doc/html/draft-baber-ianabis-rfc8126bis-01">
   <front>
      <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
      <author initials="A." surname="Baber" fullname="Amanda Baber">
         <organization>Internet Assigned Numbers Authority</organization>
      </author>
      <author initials="S." surname="Tanamal" fullname="Sabrina Tanamal">
         <organization>Internet Assigned Numbers Authority</organization>
      </author>
      <date month="July" day="7" year="2025" />
      <abstract>
	 <t>   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 fourth edition of this document; it obsoletes RFC 8126.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-baber-ianabis-rfc8126bis-01" />
   
</reference>
