Sometimes registries are needed to track a new set of code points for a new protocol or an extension to an existing protocol.
In general, documents on the Independent Stream cannot request the creation of a new IANA registry.
The only exception to this rule is when a document to be published in the Independent Submission Stream requests the allocation of a code point from an existing registry with the allocation policy Specification Required, Expert Review, RFC Required, or First Come First Served. Then the document to be published may also need to create a registry that is tied to that specific code point and is used for interpreting a sub-code.
Consider, for example, the "Uniform Resource Identifier (URI) Schemes" registry [URL-URIschemes
]. From time to time, a URI scheme may need a registry of associated parameters; for example, consider the tel URI scheme that has a register of parameters called the "tel URI Parameters" [URL-telURI
Such examples are rare and only exist to support the allocation from the base registry. In such cases, where there is an appointed DE for the existing base registry, the assignment of the individual code point from the existing base registry and the creation of the new registry can only happen if the DE approves both actions.
There are several further constraints on the new registry:
The allocation policy for the new registry may only be First Come First Served, RFC Required, Experimental, or Private Use. In particular, no registry may be created that would require IETF action to achieve a future code point allocation. See Section 5 for an explanation of why the application of Specification Required and Expert Review are not acceptable policies for any registry created from a document in the Independent Stream.
If the allocation policy for the new registry is First Come First Served, the document must contain a brief statement and explanation of the expected arrival rate of new registrations over time.
The new registry must contain a clear statement of the escalation process for any issues that arise with the registry. A model for this statement is as follows:
This registry was created by [RFCXXXX], which was published on the Independent Submission Stream. Any issues that arise with the management of this registry will be resolved by IANA in consultation with the Independent Submissions Editor.
The IESG will be invited to provide its opinions about the advisability of the creation of any new registries during its conflict review of the document [RFC 5742], and the ISE will give full consideration to such opinions.
Authors of Independent Submission Stream documents should consider the most appropriate venue to host such registries, taking into account where the expertise for managing and reviewing registry assignments may be found. In some cases, this may mean that registries are hosted by organizations other than IANA.