IETF Logo Mail Archive

Re: URN registration - Email found in subject

Benja Fallenstein <benja.fallenstein@gmail.com> Thu, 31 March 2011 10:56 UTC

Return-Path: <benja.fallenstein@gmail.com>
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 6C9CC3A6B31 for <urn-nid@core3.amsl.com>; Thu, 31 Mar 2011 03:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 k4zKmUeDm7wl for <urn-nid@core3.amsl.com>; Thu, 31 Mar 2011 03:55:59 -0700 (PDT)
Received: from mail-qy0-f177.google.com (mail-qy0-f177.google.com [209.85.216.177]) by core3.amsl.com (Postfix) with ESMTP id 8DDFA3A6B2E for <urn-nid@apps.ietf.org>; Thu, 31 Mar 2011 03:55:59 -0700 (PDT)
Received: by qyl38 with SMTP id 38so2544505qyl.1 for <urn-nid@apps.ietf.org>; Thu, 31 Mar 2011 03:57:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=XBS9AX9qx/KhVH4yDrwyMhSwLb75xaadX+TORtEyAxg=; b=ri5CMDJK5ZrDAiN/nQprAwNR9uM5GB/e7zX7JG1vZzQ8gXTJ/Rje+5OEVNe2oXgGR+ vPumJ8LTJYLbW9j9ZSW/v02+Ki6Hs6/MzjOc0XkF/GsFNV8zkbz43lAhem/2+4hbV4p0 y4hAjxXeW9LxH+Eh0MiYtKvzvPG8RY/iIePKQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=czxjlA+MB5qbTbYpYzekb1ZyuD8wgWGlqO5P/O828xnGYxhdnnUZ2ZRww/skZQjSyc Jse8vlqQyatTe1vCGVmYUShvbo42G1OM8t1LSZ46qSkDIH/3myK0oPQEPnsyE+DaF5DL YBJWBKZM5wBWFoyY104g9sUPEEePlZsoSpUPg=
MIME-Version: 1.0
Received: by 10.229.127.104 with SMTP id f40mr1216672qcs.48.1301569058805; Thu, 31 Mar 2011 03:57:38 -0700 (PDT)
Received: by 10.229.73.137 with HTTP; Thu, 31 Mar 2011 03:57:38 -0700 (PDT)
In-Reply-To: <AANLkTi=wsemN2=NcFZ9Rgki5kuPg2Ykd-z81d7SdK+CR@mail.gmail.com>
References: <A81C894800C709429D1973719CF7D33602326549@sbs.dtg.org.uk> <AANLkTi=-qRnOeiETrvHxfMgDQMh7NWJ74=32o-8fw=Wk@mail.gmail.com> <A81C894800C709429D1973719CF7D3360232659C@sbs.dtg.org.uk> <AANLkTin66+e7hTqt=rghOFFBtcAZBykfgrk7D+DBXvdr@mail.gmail.com> <A81C894800C709429D1973719CF7D33602326945@sbs.dtg.org.uk> <AANLkTi=wsemN2=NcFZ9Rgki5kuPg2Ykd-z81d7SdK+CR@mail.gmail.com>
Date: Thu, 31 Mar 2011 12:57:38 +0200
Message-ID: <AANLkTin53VMG9VF0DXfcH4FeudWCbxVP4ofycopntNmY@mail.gmail.com>
Subject: Re: URN registration - Email found in subject
From: Benja Fallenstein <benja.fallenstein@gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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 10:56:00 -0000

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

v2.23.0 | Report a Bug | By Email