From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Reply-To: iesg@ietf.org
Subject: WG Review: Update to IANA Considerations (ianabis)
A new IETF WG has been proposed in the General Area. The IESG has not made
any determination yet. The following draft charter was submitted, and is
provided for informational purposes only. Please send your comments to the
IESG mailing list (iesg@ietf.org) by 2024-10-28.
Update to IANA Considerations (ianabis)
-----------------------------------------------------------------------
Current status: Proposed WG
Chairs:
TBD
Assigned Area Director:
Murray Kucherawy <superuser@gmail.com>
General Area Directors:
Roman Danyliw <rdd@cert.org>
Mailing list:
TBD
Group page: https://datatracker.ietf.org/group/ianabis/
Charter: https://datatracker.ietf.org/doc/charter-ietf-ianabis/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:
* Additional stipulations around what constitutes valid references for
“Specification Required” registries;
* 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 specifications around 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:
Feb 2025 - Adopt an RFC 8126bis document.
Nov 2025 - Submit RFC 8126bis to the IESG as a BCP.
WG action announcement
WG Action Announcement
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>,
ianabis-chairs@ietf.org
Subject: WG Action: Formed Update to IANA Considerations (ianabis)
A new IETF WG has been formed in the General Area. For additional
information, please contact the Area Directors or the WG Chairs.
Update to IANA Considerations (ianabis)
-----------------------------------------------------------------------
Current status: Proposed WG
Chairs:
TBD
Assigned Area Director:
Murray Kucherawy <superuser@gmail.com>
General Area Directors:
Roman Danyliw <rdd@cert.org>
Mailing list:
TBD
Group page: https://datatracker.ietf.org/group/ianabis/
Charter: https://datatracker.ietf.org/doc/charter-ietf-ianabis/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:
* Additional stipulations around what constitutes valid references for
“Specification Required” registries;
* Stronger requirements around advice to Designated Experts;
* Requirements for the use of Expert Review mailing lists;
* Standardizing terms like “registry group,” “registry,” “subregistry”;
* Specifying process and restrictions around early allocations;
* Adjustments based on IANA’s experience with registries over the past seven
years;
* Amend and update registry terminology;
* 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 FCFS and “Specification Required”, and
* A process for using the Internet-Drafts system to create permanent
references.
Milestones:
Feb 2025 - Adopt an RFC 8126bis document.
Jul 2025 - Submit RFC 8126bis to the IESG as a BCP.