[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NAPTR record for urn:fdc
- To: Dave Tessman <dtessman at zelestra.com>, "urn-nid at ietf.org" <urn-nid at ietf.org>
- To: Dave Tessman <dtessman at zelestra.com>, "urn-nid at ietf.org" <urn-nid at ietf.org>
- Subject: Re: NAPTR record for urn:fdc
- From: Ted Hardie <hardie at qualcomm.com>
- From: Ted Hardie <hardie at qualcomm.com>
- Date: Mon, 8 Dec 2008 08:45:36 -0800
- Date: Mon, 8 Dec 2008 08:45:36 -0800
- Cc: Leslie Daigle <leslie at thinkingcat.com>
- Cc: Leslie Daigle <leslie at thinkingcat.com>
- Delivered-to: ietfarch-urn-nid-web-archive at core3.amsl.com
- Delivered-to: urn-nid at core3.amsl.com
- Delivered-to: ietfarch-urn-nid-archive at core3.amsl.com
- Delivered-to: urn-nid at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=hardie at qualcomm.com; q=dns/txt; s=qcdkim; t=1228754744; x=1260290744; h=mime-version:message-id:in-reply-to:references:date:to: from:subject:cc:content-type:x-ironport-av; z=MIME-Version:=201.0|Message-ID:=20<p06240601c562fee1f1b0 @[67.174.198.19]>|In-Reply-To:=20<000301c94e8f$a56be010$6 501a8c0 at 886kv31>|References:=20<000301c94e8f$a56be010$650 1a8c0 at 886kv31>|Date:=20Mon,=208=20Dec=202008=2008:45:36 =20-0800|To:=20Dave=20Tessman=20<dtessman at zelestra.com>, =0D=0A=20=20=20=20=20=20=20=20"urn-nid at ietf.org"=0D=0A=09 <urn-nid at ietf.org>|From:=20Ted=20Hardie=20<hardie at qualcom m.com>|Subject:=20Re:=20NAPTR=20record=20for=20urn:fdc |CC:=20Leslie=20Daigle=20<leslie at thinkingcat.com> |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5100,188,5457"=3B=20a =3D"13745419"; bh=5zYLa8B6iUoZcHkpbEW4iouBbz6jwzV7eGpkRaDbsMw=; b=KyulLha6oqQik9htDWhZp8SEervgd4e0QRSeDDZYZNv3U7vMiRhGDDVq 4Vq58OlpgfA2g6373eq426FaSmaa85IBuNM71r0sD//RWcggfsJ249iLF sbRBJ/t499GMcArGb+n3dmsviwVBOeDObeRl9zYKANYN0nWd5oBbL/E44 Y=;
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=hardie at qualcomm.com; q=dns/txt; s=qcdkim; t=1228754744; x=1260290744; h=mime-version:message-id:in-reply-to:references:date:to: from:subject:cc:content-type:x-ironport-av; z=MIME-Version:=201.0|Message-ID:=20<p06240601c562fee1f1b0 @[67.174.198.19]>|In-Reply-To:=20<000301c94e8f$a56be010$6 501a8c0 at 886kv31>|References:=20<000301c94e8f$a56be010$650 1a8c0 at 886kv31>|Date:=20Mon,=208=20Dec=202008=2008:45:36 =20-0800|To:=20Dave=20Tessman=20<dtessman at zelestra.com>, =0D=0A=20=20=20=20=20=20=20=20"urn-nid at ietf.org"=0D=0A=09 <urn-nid at ietf.org>|From:=20Ted=20Hardie=20<hardie at qualcom m.com>|Subject:=20Re:=20NAPTR=20record=20for=20urn:fdc |CC:=20Leslie=20Daigle=20<leslie at thinkingcat.com> |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5100,188,5457"=3B=20a =3D"13745419"; bh=5zYLa8B6iUoZcHkpbEW4iouBbz6jwzV7eGpkRaDbsMw=; b=KyulLha6oqQik9htDWhZp8SEervgd4e0QRSeDDZYZNv3U7vMiRhGDDVq 4Vq58OlpgfA2g6373eq426FaSmaa85IBuNM71r0sD//RWcggfsJ249iLF sbRBJ/t499GMcArGb+n3dmsviwVBOeDObeRl9zYKANYN0nWd5oBbL/E44 Y=;
- In-reply-to: <000301c94e8f$a56be010$6501a8c0 at 886kv31>
- In-reply-to: <000301c94e8f$a56be010$6501a8c0 at 886kv31>
- List-archive: <https://www.ietf.org/mailman/private/urn-nid>
- List-help: <mailto:urn-nid-request@ietf.org?subject=help>
- List-id: discussion of new namespace identifFrom urn-nid-bounces at ietf.org Mon Dec 8 08:46:28 2008
- List-id: discussion of new namespace identifiers foriers for URNs <urn-nid.ietf.org>
- List-post: <mailto:urn-nid@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
- References: <000301c94e8f$a56be010$6501a8c0 at 886kv31>
- References: <000301c94e8f$a56be010$6501a8c0 at 886kv31>
- Sender: urn-nid-bounces at ietf.org
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 at zelestra.com
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 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 at zelestra.com