RE: NAPTR record for urn:fdc
"Dave Tessman" <dtessman@zelestra.com> Thu, 18 December 2008 18:34 UTC
Return-Path: <urn-nid-bounces@ietf.org>
X-Original-To: urn-nid-archive@optimus.ietf.org
Delivered-To: ietfarch-urn-nid-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0D9528C0EA; Thu, 18 Dec 2008 10:34:07 -0800 (PST)
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 87BAF3A6A7B for <urn-nid@core3.amsl.com>; Mon, 8 Dec 2008 14:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.809
X-Spam-Level:
X-Spam-Status: No, score=-0.809 tagged_above=-999 required=5 tests=[AWL=0.591, 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 7LH+lMPD3kHQ for <urn-nid@core3.amsl.com>; Mon, 8 Dec 2008 14:40:50 -0800 (PST)
Received: from smtpauth22.prod.mesa1.secureserver.net (smtpauth22.prod.mesa1.secureserver.net [64.202.165.44]) by core3.amsl.com (Postfix) with SMTP id 701963A6A19 for <urn-nid@ietf.org>; Mon, 8 Dec 2008 14:40:50 -0800 (PST)
Received: (qmail 5508 invoked from network); 8 Dec 2008 22:40:44 -0000
Received: from unknown (71.130.193.218) by smtpauth22.prod.mesa1.secureserver.net (64.202.165.44) with ESMTP; 08 Dec 2008 22:40:44 -0000
From: Dave Tessman <dtessman@zelestra.com>
To: 'Leslie Daigle' <leslie@thinkingcat.com>
References: <000301c94e8f$a56be010$6501a8c0@886kv31> <p06240601c562fee1f1b0@[67.174.198.19]> <493D82BC.5050609@thinkingcat.com>
Subject: RE: NAPTR record for urn:fdc
Date: Mon, 08 Dec 2008 14:40:41 -0800
Organization: Zelestra
Message-ID: <10725C23BD6741309BA781F053364C30@886kv31>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-reply-to: <493D82BC.5050609@thinkingcat.com>
thread-index: AclZcycqXfCfueq/QSSD0qdZdfqa2wAEo2Eg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailman-Approved-At: Thu, 18 Dec 2008 10:34:07 -0800
Cc: urn-nid@ietf.org
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: <https://www.ietf.org/mailman/private/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>
Sender: urn-nid-bounces@ietf.org
Errors-To: urn-nid-bounces@ietf.org
Hi Leslie, Yup! It has been quite a while. Hope all is well with you and yours. >...formulating the NAPTR record... Yes, any help would be appreciated. Thanks, --Dave -----Original Message----- From: Leslie Daigle [mailto:leslie@thinkingcat.com] Sent: Monday, December 08, 2008 12:26 PM To: Dave Tessman Cc: Ted Hardie; urn-nid@ietf.org Subject: 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 would my process be to start that rolling? >> >> Thanks, >> >> Dave Tessman >> dtessman@zelestra.com > -- ------------------------------------------------------------------- "Reality: Yours to discover." -- ThinkingCat Leslie Daigle leslie@thinkingcat.com -------------------------------------------------------------------
- NAPTR record for urn:fdc Dave Tessman
- Re: NAPTR record for urn:fdc Ted Hardie
- Re: NAPTR record for urn:fdc Leslie Daigle
- RE: NAPTR record for urn:fdc Dave Tessman
- RE: NAPTR record for urn:fdc Dave Tessman