[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NAPTR record for urn:fdc
Hi,
Yep, it's been a while.
The process for getting NAPTR material into urn.arpa is outlined in this
RFC:
http://www.ietf.org/rfc/rfc3405.txt
It would probably be good to cc the IAB and/or IANA on any
correspondence, as it's been a while since there was any action there.
I wasn't quite clear from the message below whether help is sought for
formulating the NAPTR record that will be registered?
Leslie.
Ted Hardie wrote:
Hi Dave,
Yes, it is possible. The IAB is responsible for the
.ARPA domain, and they need to approve delegations under
it. If you want fdc.urn.arpa delegated, I believe they would
be the ones to instruct IANA on it. I've cc'ed Leslie Daigle
on this message; though she's not currently on the IAB, I
believe she was chair the last time it was done and probably
has better info on how to request it of the IAB.
regards,
Ted Hardie
At 3:52 PM -0800 11/24/08, Dave Tessman wrote:
Is it even possible to create a NAPTR DNS record (on URN.ARPA?) for the
"fdc" NID (RFC 4198) that would map the ProviderId portion of the NSS to the
URN resolution path using the http scheme and the ProviderId as the domain
name as specified in RFC 4198?
urn:fdc:<ProviderId>:<CCYY>:<Path>
Becomes
http://<ProviderId>/uri-res/N2R?<Path>
The result being that folks could type the URN into their browsers and the
appropriate resource would be returned.
If this is doable, what From urn-nid-bounces at ietf.org Mon Dec 8 12:25:51 2008
Return-Path: <urn-nid-bounces at ietf.org>
X-Original-To: urn-nid-archive at optimus.ietf.org
Delivered-To: ietfarch-urn-nid-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 6D9343A67D6;
Mon, 8 Dec 2008 12:25:51 -0800 (PST)
X-Original-To: urn-nid at core3.amsl.com
Delivered-To: urn-nid at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 4339C3A67F1
for <urn-nid at core3.amsl.com>; Mon, 8 Dec 2008 12:25:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
tests=[AWL=-0.600, BAYES_00=-2.599, J_CHICKENPOX_33=0.6,
J_CHICKENPOX_34=0.6]
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 pawjcN7VGoHI for <urn-nid at core3.amsl.com>;
Mon, 8 Dec 2008 12:25:49 -0800 (PST)
Received: from zeke.ecotroph.net (zeke.ecotroph.net [70.164.19.155])
by core3.amsl.com (Postfix) with ESMTP id 237993A67D6
for <urn-nid at ietf.org>; Mon, 8 Dec 2008 12:25:49 -0800 (PST)
Received: from beethoven.local ([::ffff:209.183.196.229])
(AUTH: PLAIN leslie, SSL: TLSv1/SSLv3,256bits,AES256-SHA)
by zeke.ecotroph.net with esmtp; Mon, 08 Dec 2008 15:25:41 -0500
id 015880FC.493D82C5.00001C33
Message-ID: <493D82BC.5050609 at thinkingcat.com>
Date: Mon, 08 Dec 2008 15:25:32 -0500
From: Leslie Daigle <leslie at thinkingcat.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Dave Tessman <dtessman at zelestra.com>
Subject: Re: NAPTR record for urn:fdc
References: <000301c94e8f$a56be010$6501a8c0 at 886kv31>
<p06240601c562fee1f1b0 at [67.174.198.19]>
In-Reply-To: <p06240601c562fee1f1b0 at [67.174.198.19]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "urn-nid at ietf.org" <urn-nid at ietf.org>
X-BeenThere: urn-nid at 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 at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/urn-nid>
List-Post: <mailto:urn-nid at ietf.org>
List-Help: <mailto:urn-nid-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>,
<mailto:urn-nid-request at ietf.org?subject=subscribe>
Sender: urn-nid-bounces at ietf.org
Errors-To: urn-nid-bounces at ietf.org
Hi,
Yep, it's been a while.
The process for getting NAPTR material into urn.arpa is outlined in this
RFC:
http://www.ietf.org/rfc/rfc3405.txt
It would probably be good to cc the IAB and/or IANA on any
correspondence, as it's been a while since there was any action there.
I wasn't quite clear from the message below whether help is sought for
formulating the NAPTR record that will be registered?
Leslie.
Ted Hardie wrote:
Hi Dave,
Yes, it is possible. The IAB is responsible for the
.ARPA domain, and they need to approve delegations under
it. If you want fdc.urn.arpa delegated, I believe they would
be the ones to instruct IANA on it. I've cc'ed Leslie Daigle
on this message; though she's not currently on the IAB, I
believe she was chair the last time it was done and probably
has better info on how to request it of the IAB.
regards,
Ted Hardie
At 3:52 PM -0800 11/24/08, Dave Tessman wrote:
Is it even possible to create a NAPTR DNS record (on URN.ARPA?) for the
"fdc" NID (RFC 4198) that would map the ProviderId portion of the NSS to the
URN resolution path using the http scheme and the ProviderId as the domain
name as specified in RFC 4198?
urn:fdc:<ProviderId>:<CCYY>:<Path>
Becomes
http://<ProviderId>/uri-res/N2R?<Path>
The result being that folks could type the URN into their browsers and the
appropriate resource would be returned.
If this is doable, what would mywould my process be to start that rolling?
Thanks,
Dave Tessman
dtessman at zelestra.com
--
-------------------------------------------------------------------
"Reality:
Yours to discover."
-- ThinkingCat
Leslie Daigle
leslie at thinkingcat.com
-------------------------------------------------------------------
process be to start that rolling?
Thanks,
Dave Tessman
dtessman at zelestra.com
--
-------------------------------------------------------------------
"Reality:
Yours to discover."
-- ThinkingCat
Leslie Daigle
leslie at thinkingcat.com
-------------------------------------------------------------------