Browse Prior Art Database

Guidelines for Writing an IANA Considerations Section in RFCs (RFC8126)

IP.com Disclosure Number: IPCOM000250270D
Original Publication Date: 2017-Jun-01
Included in the Prior Art Database: 2017-Jun-21

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Cotton: AUTHOR [+3]

Abstract

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. The Protocol field in the IP header [RFC791] and MIME media types [RFC6838] are two examples of such coordinations.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Internet Engineering Task Force (IETF)                         M. Cotton Request for Comments: 8126                                           PTI BCP: 26                                                         B. Leiba Obsoletes: 5226                                      Huawei Technologies Category: Best Current Practice                                T. Narten ISSN: 2070-1721                                          IBM Corporation                                                                June 2017

      Guidelines for Writing an IANA Considerations Section in RFCs

Abstract

   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.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    BCPs is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8126.

Cotton, et al.            Best Current Practice                 [Page 1]
 RFC 8126           IANA Considerations Section in RFCs         June 2017

 Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on...