<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.leiba-cotton-iana-5226bis" target="https://datatracker.ietf.org/doc/html/draft-leiba-cotton-iana-5226bis-19">
   <front>
      <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
      <author initials="M." surname="Cotton" fullname="Michelle Cotton">
         </author>
      <author initials="B." surname="Leiba" fullname="Barry Leiba">
         </author>
      <author initials="T." surname="Narten" fullname="Dr. Thomas Narten">
         </author>
      <date month="January" day="10" year="2017" />
      <abstract>
	 <t>   Many protocols make use of points of extensibility that use constants
   to identify various protocol parameters.  To ensure that the values
   used in these fields do not have conflicting uses, and to promote
   interoperability, their allocation is often coordinated by a central
   record keeper.  For IETF protocols, that role is filled by the
   Internet Assigned Numbers Authority (IANA) Services.

   To make assignments in a given registry prudently, guidance is needed
   for describing the conditions under which new values should be
   assigned, as well as when and how modifications to existing values
   can be made.  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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-leiba-cotton-iana-5226bis-19" />
   
</reference>
