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

Barry Leiba <> Wed, 17 April 2013 15:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0F43121F8E36 for <>; Wed, 17 Apr 2013 08:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.935
X-Spam-Status: No, score=-102.935 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 83QFtCZAZlM6 for <>; Wed, 17 Apr 2013 08:31:26 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 7111C21F8E2C for <>; Wed, 17 Apr 2013 08:31:26 -0700 (PDT)
Received: by with SMTP id jz10so1523488veb.19 for <>; Wed, 17 Apr 2013 08:31:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=qlzPVddHLghtKwz795YBpkZEOuyaCpg6vNwDwQXrIzg=; b=eorrlLkm5s6bQy0oQV/qi5smonxJ57jz76JnXIrZWtART7/DTh+6D1MissrLtNc77P wJANgjymTjVBXHM4KuDb6www6gWRe2AxZXPSgRvsRIdqWw3ad0UeiWwDlwXPlg0DMKos 4xoncL0VTzY8Jx7YzQUcax3+m0P850Kk6cF70K9CL8qMlpWBEHpWgPKVAusPQ55xP17X Gsu0tOHUGeDWBJcQUBtCE51pfnuREJ1DyrKQPMaxDQ5Gp0AJuZm8Y2lj8HCilFGLnmO+ 4oR3jvKxUnm+lF29t34QxkXTBD/eNYn36jYOeJC6EecLZJVDsz6MDl747wXlMUv7/Bfc xDAQ==
MIME-Version: 1.0
X-Received: by with SMTP id ds10mr4503168vdb.3.1366212685887; Wed, 17 Apr 2013 08:31:25 -0700 (PDT)
Received: by with HTTP; Wed, 17 Apr 2013 08:31:25 -0700 (PDT)
In-Reply-To: <>
References: <> <>
Date: Wed, 17 Apr 2013 11:31:25 -0400
X-Google-Sender-Auth: rLZHrMbzyMaAJ5yr9DGi3Niq46s
Message-ID: <>
From: Barry Leiba <>
To: "Murray S. Kucherawy" <>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Apps Discuss <>
Subject: Re: [apps-discuss] FW: New Version Notification for draft-lanthaler-profile-registry-01.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 17 Apr 2013 15:31:27 -0000

>> 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.