Update to IANA Considerations (ianabis) Internet Drafts

      
 Guidelines for Writing an IANA Considerations Section in RFCs
 
 draft-baber-ianabis-rfc8126bis-01.txt
 Date: 07/07/2025
 Authors: Amanda Baber, Sabrina Tanamal
 Working Group: Update to IANA Considerations (ianabis)
 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.
 Early IANA Code Point Allocation for IETF Stream Internet-Drafts
 
 draft-baber-ianabis-rfc7120bis-00.txt
 Date: 25/03/2025
 Authors: Amanda Baber, Sabrina Tanamal
 Working Group: Update to IANA Considerations (ianabis)
 This memo describes the requirements for securing IANA code point assignments before RFC publication. In particular, it describes the "early allocation" process that allows for temporary but renewable allocations from registries that would ordinarily require an IESG- approved Internet-Draft: namely, registries maintained in accordance with the "Standards Action," "IETF Review," "RFC Required," and, in some cases, "Specification Required" policies. This process can be used when code point allocation is needed to facilitate desired or required implementation and deployment experience prior to publication. The procedures in this document are intended to apply only to IETF Stream documents. This document obsoletes RFC 7120.

data-group-menu-data-url="/group/groupmenu.json">

Update to IANA Considerations (ianabis)

WG Name Update to IANA Considerations
Acronym ianabis
Area General Area (gen)
State Active
Charter charter-ietf-ianabis-01-02 External Review (Message to Community, Selected by Secretariat)
Document dependencies
Personnel Chairs Murray Kucherawy, Ted Hardie
Area Director Roman Danyliw
Mailing list Address ianabis@ietf.org
To subscribe https://mailman3.ietf.org/mailman3/lists/ianabis.ietf.org/
Archive https://mailarchive.ietf.org/arch/browse/ianabis/
Chat Room address https://zulip.ietf.org/#narrow/stream/ianabis

Charter for Working Group

RFC 8126/BCP 26, "Guidelines for Writing an IANA Considerations Section in RFCs", defines a framework to ensure that the IANA Considerations section in a document is clear and addresses the various issues that are likely in the operation of a registry.

This is a critical function in many protocol frameworks. The current version of BCP 26 was published in 2017 and is the third generation of this document. Given the evolving needs of the IETF community, it is due for an update.

The IANABIS working group will consider proposed revisions to BCP 26, given experience gained since the publication of RFC 8126, and ultimately produce a revision for that document. This is the only expected output for the working group.

Issues it will consider include:

  • Stronger requirements around advice to Designated Experts;

  • Requirements for the use of Expert Review mailing lists;

  • Standardizing terms like “registry group,” “registry,” “subregistry”, or updating existing definitions;

  • Process and restrictions regarding early allocations;

  • Adjustments based on IANA’s experience with registries over the past seven years;

  • Additional registration policies that can allow more flexibility for encouraging and accepting registrations;

  • Combinations of registration policies with choices by WGs or registrants for specific cases;

  • A registration policy between "First Come First Served" and “Specification Required”, and

  • A process for using the Internet-Drafts system to create permanent references.

The primary goal of the IANABIS Working Group is to produce a revised Best Current Practice (BCP 26) that:

  • Reflects the current needs and practices of the IETF community;

  • Incorporates lessons learned and operational experiences since the publication of RFC 8126;

  • Provides clear, comprehensive guidance for authors and Working Groups in crafting IANA Considerations sections; and

  • Enhances the efficiency, clarity, and consistency of IANA registry management processes.

The working group will collaborate closely with IANA staff, designated experts, and of course the community at large.

By updating BCP 26, the IANABIS Working Group aims to strengthen the foundational guidelines that support the IETF's protocol development and registry management, ensuring they remain robust, clear, and aligned with the evolving landscape of Internet standards.

Milestones

Date Milestone Associated documents
Nov 2025 Submit RFC 8126bis to the IESG as a BCP.
Mar 2025 Adopt an RFC 8126bis document.