From urn-nid-bounces@ietf.org Mon Dec 8 08:02:17 2008 Return-Path: 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 ; 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 ; 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 ; 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" To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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::: Becomes http:///uri-res/N2R? 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 From urn-nid-bounces@ietf.org Mon Dec 8 08:46:28 2008 Return-Path: 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 B65C13A69DF; Mon, 8 Dec 2008 08:46:28 -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 8AEF73A6A94 for ; Mon, 8 Dec 2008 08:46:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.287 X-Spam-Level: X-Spam-Status: No, score=-102.287 tagged_above=-999 required=5 tests=[AWL=-0.888, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, J_CHICKENPOX_34=0.6, USER_IN_WHITELIST=-100] 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 m6QkPtrUXcA2 for ; Mon, 8 Dec 2008 08:46:26 -0800 (PST) Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id A9FDD3A686C for ; Mon, 8 Dec 2008 08:45:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=hardie@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|In-Reply-To:=20<000301c94e8f$a56be010$6 501a8c0@886kv31>|References:=20<000301c94e8f$a56be010$650 1a8c0@886kv31>|Date:=20Mon,=208=20Dec=202008=2008:45:36 =20-0800|To:=20Dave=20Tessman=20, =0D=0A=20=20=20=20=20=20=20=20"urn-nid@ietf.org"=0D=0A=09 |From:=20Ted=20Hardie=20|Subject:=20Re:=20NAPTR=20record=20for=20urn:fdc |CC:=20Leslie=20Daigle=20 |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=; X-IronPort-AV: E=McAfee;i="5100,188,5457"; a="13745419" Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Dec 2008 08:45:44 -0800 Received: from msgtransport01.qualcomm.com (msgtransport01.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id mB8GjiIQ007059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 8 Dec 2008 08:45:44 -0800 Received: from nasanexhub04.na.qualcomm.com (nasanexhub04.qualcomm.com [129.46.134.222]) by msgtransport01.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id mB8Gjd88017659 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 8 Dec 2008 08:45:39 -0800 Received: from nasanexmsp02.na.qualcomm.com (10.45.56.203) by nasanexhub04.na.qualcomm.com (129.46.134.222) with Microsoft SMTP Server (TLS) id 8.1.311.2; Mon, 8 Dec 2008 08:45:39 -0800 Received: from [67.174.198.19] (10.46.82.6) by qcmail1.qualcomm.com (10.45.56.203) with Microsoft SMTP Server (TLS) id 8.1.311.2; Mon, 8 Dec 2008 08:45:38 -0800 MIME-Version: 1.0 Message-ID: In-Reply-To: <000301c94e8f$a56be010$6501a8c0@886kv31> References: <000301c94e8f$a56be010$6501a8c0@886kv31> Date: Mon, 8 Dec 2008 08:45:36 -0800 To: Dave Tessman , "urn-nid@ietf.org" From: Ted Hardie Subject: Re: NAPTR record for urn:fdc Content-Type: text/plain; charset="us-ascii" Cc: Leslie Daigle X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: urn-nid-bounces@ietf.org Errors-To: urn-nid-bounces@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::: > >Becomes > >http:///uri-res/N2R? > >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 From urn-nid-bounces@ietf.org Mon Dec 8 12:25:51 2008 Return-Path: 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 6D9343A67D6; Mon, 8 Dec 2008 12:25:51 -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 4339C3A67F1 for ; 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 ; 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 ; 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@thinkingcat.com> Date: Mon, 08 Dec 2008 15:25:32 -0500 From: Leslie Daigle User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914) MIME-Version: 1.0 To: Dave Tessman Subject: Re: NAPTR record for urn:fdc References: <000301c94e8f$a56be010$6501a8c0@886kv31> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: urn-nid-bounces@ietf.org Errors-To: urn-nid-bounces@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::: >> >> Becomes >> >> http:///uri-res/N2R? >> >> 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 ------------------------------------------------------------------- From urn-nid-bounces@ietf.org Thu Dec 18 10:34:07 2008 Return-Path: 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 ; 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 ; 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 ; 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" To: "'Leslie Daigle'" References: <000301c94e8f$a56be010$6501a8c0@886kv31> <493D82BC.5050609@thinkingcat.com> Subject: RE: NAPTR record for urn:fdc Date: Mon, 8 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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::: >> >> Becomes >> >> http:///uri-res/N2R? >> >> 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 -------------------------------------------------------------------