NAPTR record for urn:fdc
"Dave Tessman" <dtessman@zelestra.com> Mon, 08 December 2008 16:02 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 B91DD3A6888; Mon, 8 Dec 2008 08:02:17 -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 0E8D33A6A96 for <urn-nid@core3.amsl.com>; Mon, 24 Nov 2008 15:52:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.201
X-Spam-Level: *
X-Spam-Status: No, score=1.201 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 cQb-uh5WaKgC for <urn-nid@core3.amsl.com>; Mon, 24 Nov 2008 15:52:05 -0800 (PST)
Received: from smtpout06.prod.mesa1.secureserver.net (smtpout06-04.prod.mesa1.secureserver.net [64.202.165.227]) by core3.amsl.com (Postfix) with SMTP id 0C56F3A6B90 for <urn-nid@ietf.org>; Mon, 24 Nov 2008 15:52:04 -0800 (PST)
Received: (qmail 17837 invoked from network); 24 Nov 2008 23:52:02 -0000
Received: from unknown (71.130.197.125) by smtpout06-04.prod.mesa1.secureserver.net (64.202.165.227) with ESMTP; 24 Nov 2008 23:52:02 -0000
From: Dave Tessman <dtessman@zelestra.com>
To: urn-nid@ietf.org
Subject: NAPTR record for urn:fdc
Date: Mon, 24 Nov 2008 15:52:01 -0800
Organization: Zelestra
Message-ID: <000301c94e8f$a56be010$6501a8c0@886kv31>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AclOj6MmGwNBX9GZS822WRI1yyhRFg==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailman-Approved-At: Mon, 08 Dec 2008 08:02:15 -0800
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
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
- 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