Summary

  • The 26 October IANABIS draft adds a proposal to rename and repurpose an IANA list of standards organizations first built for media-type registration.
  • IANA would check the list when another procedure needs IESG recognition, and send an unlisted organization to the IESG for a decision.

Some standards bodies need a code point before they can publish the specification that explains it. The new IETF working-group draft describes that circular wait and a proposed early-allocation route requiring expert judgment and IESG recognition of the organization. The current IANA page has a wonderfully narrow title: organizations that registered Media Types in the Standards Tree. It is a record of who came through one door. The draft would give that list a second career at several doors.

Published in the 27 October UTC announcement, revision -04 of Guidelines for Writing an IANA Considerations Section in RFCs adds an IANA action absent from July’s -03 text. It proposes renaming the list “IESG-Recognized Standards-Related Organizations” and retaining its existing entries. That shift sounds like filing-cabinet maintenance. In practice, it moves a list built around one kind of media-type registration toward a reusable answer to a governance question: which outside standards body has the IESG already recognized?

The proposed sequence is unusually crisp. When a registration procedure demands that recognition, IANA checks the list. If the organization is missing, IANA asks the IESG to decide. Once the IESG formally recognizes it, IANA adds its name. The draft keeps “IESG Approval” as the list’s registration procedure. At publication, the listed bodies would be eligible for procedures that require this sort of recognition; the text leaves room for later restrictions by particular registry or procedure.

One side effect deserves daylight. A record initially populated by media-type activity could become a shortcut for other procedures. Anyone reading a future entry should be able to tell when and on what basis recognition was granted, and whether its reach was later narrowed. The draft also asks IANA to add “Change Controller” fields to certain new registries, then backfill blank fields in older ones. That is another custody question: a code-point list needs an owner for subsequent changes.

The live IANA register still carries its media-type title and cites RFC 6838. The expanded title and workflow are in the draft, where the decision belongs today.

The Datatracker record identifies -04 as an IANABIS working-group document.