Re: Comments on draft-adid-urn-00

worley@ariadne.com (Dale R. Worley) Tue, 12 April 2016 15:35 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAA3C12DB87 for <urn-nid@ietfa.amsl.com>; Tue, 12 Apr 2016 08:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ivac0ADGyCKo for <urn-nid@ietfa.amsl.com>; Tue, 12 Apr 2016 08:34:59 -0700 (PDT)
Received: from resqmta-po-06v.sys.comcast.net (resqmta-po-06v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E13612D627 for <urn-nid@apps.ietf.org>; Tue, 12 Apr 2016 08:34:56 -0700 (PDT)
Received: from resomta-po-16v.sys.comcast.net ([96.114.154.240]) by comcast with SMTP id q0KoaAJX39sFTq0LAaNkOh; Tue, 12 Apr 2016 15:34:56 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1460475296; bh=DD65K2R3pviafIesLnQw1hfjRLJADn9I4SSKMZAYSY4=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=shIPHlaaTxd4geraL7e+g/no1N0NFp6THUji/3tbZMzMed9Lj8h79baVGPsCinaNB b4yDR4vQDZK8Byw4UqF4IvIAoA47SS9pcx5l4M8unAb6rumdvI/zr6s+l1+WGFjmHr Gr0/4qvO7ficLDr5v3N/Ar9N8vX7IaZFbTm8AJr24tzDfNBR4Zs1AU8on0gEi71QK7 8OWg0lVETOjMTgXigNchw82JC6PP578h5Bgnjodm/DmF4vlA9wo4zcwMUtCF2S2aza XcHqjkKOa5tcX6+AuW2riAbs00Fp3gbsgXYWJS0oLsjLPaOPUcUxFolIi13MwnalYQ 2rQpgn+UTmqAQ==
Received: from hobgoblin.ariadne.com ([73.143.237.82]) by resomta-po-16v.sys.comcast.net with comcast id hTau1s00H1nMCLR01Tavd8; Tue, 12 Apr 2016 15:34:56 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id u3CFYsvv002584; Tue, 12 Apr 2016 11:34:54 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u3CFYr5W002581; Tue, 12 Apr 2016 11:34:53 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Jarrett Wold <jwold@ad-id.org>
Subject: Re: Comments on draft-adid-urn-00
In-Reply-To: <8733ebf3a2b0717cde5d5b7fbcd63c6d@mail.gmail.com> (jwold@ad-id.org)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 12 Apr 2016 11:34:53 -0400
Message-ID: <87lh4ig7s2.fsf@hobgoblin.ariadne.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/VlghdKN___BQyTY_h9fFUAzLO4g>
Cc: urn-nid@apps.ietf.org
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Apr 2016 15:35:00 -0000

Jarrett Wold <jwold@ad-id.org>; writes:
> I hope you are well.  I just wanted to give you a heads up I submitted as
> and Internet Draft.
>
> https://datatracker.ietf.org/submit/status/77574/2ec89a71732528ff6b323e4a2
> 25c5d7f/

When I look at that URL, I see "Submission status: Awaiting Manual
Post".  Clicking on the "idnits" button shows a bunch of stuff
including:

  -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(ii)
     Publication Limitation clause.  If this document is intended for
     submission to the IESG for publication, this constitutes an error.

Looking at the prodcedures document (RFC 3406 section 4.3), it looks
like URN namespaces have to be approved by the IESG, so you'll probably
have to change the IETF Trust Provisions before you can get the
namespaced approved.  You shouldn't have to change that, though, to get
the draft into the database.  But I suspect you've got to go into the
tool somehow and tell it that you're OK with this.  If you can't make it
work, you should probably get in touch with the chair of the URN working
group, who would be the person in charge.

Dale