Re: [apps-discuss] FW: New Version Notification for draft-lanthaler-profile-registry-01.txt

[Barry Leiba <[e-mail]>]

>> Since this is my first I-D I'm not familiar with the processes yet. If my understanding
>> of RFC2026 & RFC4846 is correct, the next step would be to send a publication
>> request to the RFC editor. Or do I have to contact the Area Directors because the
>> document requires IANA allocations?
>
> This document creates a registry, so I'm fairly certain it needs to go
> through the IETF Stream, which means an Area Director has to sponsor it or a
> working group has to adopt it.  On the other hand, although Independent
> Submission stream drafts can't create registry entries when the registry has
> certain constraints, I couldn't find anything constraining registry
> creation.  Someone should check my math here.

There's nothing that says you can't create a new registry through the
Independent Stream, as long as the IESG doesn't think it conflicts
with IETF work, so that's not the issue here.

The reason this can't go through the Independent Stream (that is,
directly to the RFC Editor) is that it's requesting an IETF-namespace
URN sub-namespace in the second bullet of Section 4.  RFC 3553 says
this about that:

   Process of identifier assignment:

      Identifiers are assigned only after a particular protocol element
      or number has been registered with the IANA using standard
      policies and procedures, or documented in an RFC describing a
      standards track protocol.  This means that the 'gating' function
      for assignment is the "IETF Consensus" process documented in RFC
      2434 [4].

I suggest that the appsawg might process this document.

Barry