The Update to IANA Considerations (ianabis) WG in the General Area of the IETF is undergoing rechartering. 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 ([email protected]) by 2025-05-02.
Update to IANA Considerations (ianabis) ----------------------------------------------------------------------- Current status: Active WG Chairs: Ted Hardie <[email protected]> Murray Kucherawy <[email protected]> Assigned Area Director: Roman Danyliw <[email protected]> General Area Directors: Roman Danyliw <[email protected]> Mailing list: Address: [email protected] To subscribe: https://mailman3.ietf.org/mailman3/lists/ianabis.ietf.org/ Archive: https://mailarchive.ietf.org/arch/browse/ianabis/ 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. RFC 7120/BCP 100, “Early IANA Allocation of Standards Track Code Points”, describes the process for early allocation of code points by IANA from registries with a certain set of registration policies. These BCPs form a critical function in many protocol frameworks. The latest version of BCP 26 was published in 2017 and is the third generation of this document. BCP 100 was published in 2014. Given the evolving needs of the IETF community, they are due for an update. The IANABIS Working Group will consider proposed revisions to both BCPs, given experience gained since the publication of each, and ultimately produce revisions for those documents. These are the only expected output for the working group. Issues to be considered 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”; * A process for using the Internet-Drafts system to create permanent references; and * Integrating or referencing the IANA-related guidance in draft-ietf-netmod-rfc8407bis in the specifications of the WG. The primary goal of the IANABIS Working Group is to produce a revised BCP 26 and BCP 100 that: * Reflects the current needs and practices of the IETF community; * Incorporates lessons learned and operational experiences since the publication of RFC 8126; * For BCP 26 specifically, 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. Lastly, the working group may consider combining the two documents into BCP 26. The working group will collaborate closely with IANA staff, designated experts, and of course the community at large. By updating these documents, 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: Mar 2025 - Adopt an RFC 8126bis document. Nov 2025 - Submit RFC 8126bis to the IESG as a BCP. _______________________________________________ IETF-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected]
