The current text states:
This specification introduces some new namespaces that will be
registered with IANA. In all cases, new entries are assigned only
for values that have been documented in a published RFC that has IETF
Consensus, per [IANA-CONSIDERATIONS].
This precludes RFCs that are submitted directly to the RFC Editor for
individual submission. Is there a particular reason for this? There
are likely to be authentication specs in the future that will not go
through the IETF process (such as VBR from the Domain Assurance
Council) that should be in the IANA registry but cannot with this
rule even though those specs will be stable and open RFCs.
--Paul Hoffman, Director
--Domain Assurance Council
_______________________________________________
NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html