RE: URN registration - Email found in subject - Email found in subject

"DTG Registration" <registration@dtg.org.uk> Thu, 31 March 2011 11:16 UTC

Return-Path: <registration@dtg.org.uk>
X-Original-To: urn-nid@core3.amsl.com
Delivered-To: urn-nid@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B20243A6930 for <urn-nid@core3.amsl.com>; Thu, 31 Mar 2011 04:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.736
X-Spam-Level:
X-Spam-Status: No, score=-0.736 tagged_above=-999 required=5 tests=[AWL=0.467, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MRyhXph8YfA0 for <urn-nid@core3.amsl.com>; Thu, 31 Mar 2011 04:16:51 -0700 (PDT)
Received: from dtg.org.uk (mail1.dtg.org.uk [217.20.28.2]) by core3.amsl.com (Postfix) with ESMTP id 983143A68B1 for <urn-nid@apps.ietf.org>; Thu, 31 Mar 2011 04:16:51 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: URN registration - Email found in subject - Email found in subject
Date: Thu, 31 Mar 2011 12:18:29 +0100
Message-ID: <A81C894800C709429D1973719CF7D3360243074D@sbs.dtg.org.uk>
In-Reply-To: <AANLkTin53VMG9VF0DXfcH4FeudWCbxVP4ofycopntNmY@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: URN registration - Email found in subject - Email found in subject
Thread-Index: AcvvlVyxPbhZRFDWR7iihQgGPY1Dvg==
References: <AANLkTi=wsemN2=NcFZ9Rgki5kuPg2Ykd-z81d7SdK+CR@mail.gmail.com> <AANLkTin53VMG9VF0DXfcH4FeudWCbxVP4ofycopntNmY@mail.gmail.com>
From: DTG Registration <registration@dtg.org.uk>
To: Benja Fallenstein <benja.fallenstein@gmail.com>, Ted Hardie <ted.ietf@gmail.com>
Cc: urn-nid@apps.ietf.org, DTG Registration <registration@dtg.org.uk>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 31 Mar 2011 11:16:52 -0000

Benja,

Thank you for your response.

Yes, the text was copied from the example application in RFC 3406.

Is it possible to speak to somebody to assist the application process?

Best regards,

Will





-----Original Message-----
From: Benja Fallenstein [mailto:benja.fallenstein@gmail.com] 
Sent: 31 March 2011 11:58
To: Ted Hardie
Cc: DTG Registration; urn-nid@apps.ietf.org
Subject: Re: URN registration - Email found in subject - Email found in subject

Hi Ted,

On Mon, Mar 7, 2011 at 11:39 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
>> Does our urn require an assigned number? Does this come from ietf? I don't think we require a number, apologies for the confusion.
>>
> Your registration form currently implies your organization assigns a
> unique number.  If you are guaranteeing uniqueness in some other way,
> how need to be made clear.  The IETF would not assign these resources
> numbers.

I think you're misreading. Most of the text in this application seems
to be copied from the example application in RFC 3406, including the

> URN:<assigned number>:<FQDN>:<assigned string>

that you cite. In this context, the <assigned number> is the URN
namespace name. IIUC, the example is of an application for an informal
URN namespace, where the namespace name is assigned by IANA. That's
also why the first line reads "Namespace ID: to be assigned".

All the best,
- Benja


The information in this email and any attachments is confidential, may be subject to copyright and is intended solely for the addressee (s). Access to this email by anyone else is unauthorised. If you are not the intended recipient, please notify the sender and delete this e-mail.  In this case, please note that copying, disseminating or taking any action in relation to the contents of this e-mail is strictly prohibited. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Digital TV Group. Digital TV Group cannot ensure that emails are virus-free and therefore accepts no liability for viruses that might be transferred by this email or any attachment.