RE: Comments on draft-adid-urn-00

Jarrett Wold <> Mon, 18 April 2016 20:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7DD6512E7A5 for <>; Mon, 18 Apr 2016 13:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id T6wTYq8ROt1h for <>; Mon, 18 Apr 2016 13:50:46 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 63D7F12E7A3 for <>; Mon, 18 Apr 2016 13:50:46 -0700 (PDT)
Received: by with SMTP id er2so53829922pad.3 for <>; Mon, 18 Apr 2016 13:50:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc; bh=roc4SjSOyKzIvyEg9m7fBrjpJ6aNMggr0Zo66zpbMUg=; b=hbTAlxpf3RswcLGRIEReclJdvlHG7gsafgSnnxy+ZtDUrcZ0tuax/MVFinhNvnHd0v 14TotU91eMR0LnNUN2cyjBDTGiKspj8L9l4O+6CwKACcmSRbDHe7kH8BgACAWDWsscWf wQ+7EJAM2J0h1zyzK2roSab/s3twJVl7vMMh0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc; bh=roc4SjSOyKzIvyEg9m7fBrjpJ6aNMggr0Zo66zpbMUg=; b=h9uazvlkz/ZSghdvYLwRY8kNgkj+w8C6NxKQpXmm6PSu4kpJv1th4jZH4tSCn5Ee3I 6GOx1U1h5RHntm2ExybwahWq/BXofyhl5fCqe5FumBcsAZnBuTHSMkDqJbya5Xf4pvxs oBn7asX8JNv+15RgCN1FIhuUmIgVIMxWt0ow2yjPmGRuJvoD6kVeRCaTcxEQ8duiEyBo IF+dVbYSh18EddZ7JCDzmkS2hMhQ2vT0zjHUO17vvVIMkm2Q440AidtS9LIWsEI7N3va Fw2XoZ9fqaZUVsqClNg8KS6EGyeeR9SPz+w6QDEcCXV4EdzoKH9DFTKDXR1vdrs6Qqfl XsbA==
X-Gm-Message-State: AOPr4FUdo3AbbkD3G8wITJjnRfenLNCC7WCJ/ThCp98YLJmuHA2EKZQx7GgxAoNSTpaeB3YmSEh7muWKB5j0Rwb3
X-Received: by with SMTP id ic10mr51022927pad.127.1461012645816; Mon, 18 Apr 2016 13:50:45 -0700 (PDT)
From: Jarrett Wold <>
References: <> ( <>
In-Reply-To: <>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQIU03LmXC9BSPOt12kmeabPy8STEZ8JwTGw
Date: Mon, 18 Apr 2016 16:51:53 -0400
Message-ID: <>
Subject: RE: Comments on draft-adid-urn-00
To: "Dale R. Worley" <>
Content-Type: text/plain; charset=UTF-8
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 18 Apr 2016 20:50:48 -0000

Hi Dale -
It looks like this was submitted ok now.

From: []
Sent: Thursday, April 14, 2016 3:08 PM
To:; Jarrett Wold <>
Subject: New Version Notification for draft-adid-urn-00.txt

A new version of I-D, draft-adid-urn-00.txt has been successfully
submitted by Jarrett Wold and posted to the IETF repository.

Name:		draft-adid-urn
Revision:	00
Title:		Advertising Digital Identification (Ad-ID) URN Namespace
Document date:	2016-04-12
Group:		Individual Submission
Pages:		6

   Advertising Digital Identification (Ad-ID) Identifiers are used
   identifying Advertising Assets across all media platforms (over the
   air, on-line, over the top, mobile, place based). This document
   defines the formal Uniform Resource Name (URN) Namespace Identifier
   (NID) for Ad-ID Identifiers.

Please note that it may take a couple of minutes from the time of
submission until the htmlized version and diff are available at

-----Original Message-----
From: Dale R. Worley []
Sent: Tuesday, April 12, 2016 11:35 AM
To: Jarrett Wold <>
Subject: Re: Comments on draft-adid-urn-00

Jarrett Wold <> writes:
> I hope you are well.  I just wanted to give you a heads up I submitted
> as and Internet Draft.
> e4a2
> 25c5d7f/

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

  -- The document has an IETF Trust Provisions (28 Dec 2009) Section
     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.