From owner-urn-ietf@LISTS.NETSOL.COM Thu Oct 17 20:56:10 2002 Received: from lists.netsol.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01401 for ; Thu, 17 Oct 2002 20:56:10 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id UAA15329; Thu, 17 Oct 2002 20:54:46 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 10556 for URN-IETF@LISTS.NETSOL.COM; Thu, 17 Oct 2002 20:51:31 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id UAA15117 for ; Thu, 17 Oct 2002 20:20:33 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9I07pD01040; Thu, 17 Oct 2002 17:07:51 -0700 (PDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Message-ID: <200210180007.g9I07pD01040@gamma.isi.edu> Date: Thu, 17 Oct 2002 17:07:51 -0700 Reply-To: rfc-editor@RFC-EDITOR.ORG Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: rfc-editor@RFC-EDITOR.ORG Subject: BCP 66, RFC 3406 on Uniform Resource Names (URN) Namespace Definition Mechanisms To: URN-IETF@LISTS.NETSOL.COM --NextPart A new Request for Comments is now available in online RFC libraries. BCP 66 RFC 3406 Title: Uniform Resource Names (URN) Namespace Definition Mechanisms Author(s): L. Daigle, D. van Gulik, R. Iannella, P. Faltstrom Status: Best Current Practice Date: October 2002 Mailbox: leslie@thinkingcat.com, Dirkx@webweaving.org, renato@iprsystems.com, paf@cisco.com Pages: 22 Characters: 43707 Obsoletes: 2611 SeeAlso: BCP 66 I-D Tag: draft-ietf-urn-rfc2611bis-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3406.txt This document lays out general definitions of and mechanisms for establishing Uniform Resource Names (URN) "namespaces". The URN WG has defined a syntax for URNs in RFC 2141, as well as some proposed mechanisms for their resolution and use in Internet applications in RFC 3401 and RFC 3405. The whole rests on the concept of individual "namespaces" within the URN structure. Apart from proof-of-concept namespaces, the use of existing identifiers in URNs has been discussed in RFC 2288. This document is a product of the Uniform Resource Names Working Group of the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021017170513.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3406 --OtherAccess Content-Type: Message/External-body; name="rfc3406.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021017170513.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-urn-ietf@LISTS.NETSOL.COM Thu Oct 17 20:56:54 2002 Received: from lists.netsol.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01427 for ; Thu, 17 Oct 2002 20:56:53 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id UAA15400; Thu, 17 Oct 2002 20:59:36 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 10560 for URN-IETF@LISTS.NETSOL.COM; Thu, 17 Oct 2002 20:56:44 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id UAA15056 for ; Thu, 17 Oct 2002 20:13:09 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9I00RD28385; Thu, 17 Oct 2002 17:00:27 -0700 (PDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Message-ID: <200210180000.g9I00RD28385@gamma.isi.edu> Date: Thu, 17 Oct 2002 17:00:27 -0700 Reply-To: rfc-editor@RFC-EDITOR.ORG Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: rfc-editor@RFC-EDITOR.ORG Subject: RFC 3404 on Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) Resolution Application To: URN-IETF@LISTS.NETSOL.COM --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3404 Title: Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) Resolution Application Author(s): M. Mealling Status: Standards Track Date: October 2002 Mailbox: michael@neonym.net Pages: 18 Characters: 40124 Obsoletes: 2915, 2168 I-D Tag: draft-ietf-urn-uri-res-ddds-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3404.txt This document describes a specification for taking Uniform Resource Identifiers (URI) and locating an authoritative server for information about that URI. The method used to locate that authoritative server is the Dynamic Delegation Discovery System. This document is part of a series that is specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible to read and understand any document in this series without reading the others. This document is a product of the Uniform Resource Names Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021017165807.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3404 --OtherAccess Content-Type: Message/External-body; name="rfc3404.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021017165807.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-urn-ietf@LISTS.NETSOL.COM Thu Oct 17 20:59:39 2002 Received: from lists.netsol.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01519 for ; Thu, 17 Oct 2002 20:59:39 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id VAA15499; Thu, 17 Oct 2002 21:02:41 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 10564 for URN-IETF@LISTS.NETSOL.COM; Thu, 17 Oct 2002 20:59:48 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id UAA15040 for ; Thu, 17 Oct 2002 20:10:36 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNvsD27042; Thu, 17 Oct 2002 16:57:54 -0700 (PDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Message-ID: <200210172357.g9HNvsD27042@gamma.isi.edu> Date: Thu, 17 Oct 2002 16:57:54 -0700 Reply-To: rfc-editor@RFC-EDITOR.ORG Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: rfc-editor@RFC-EDITOR.ORG Subject: RFC 3403 on Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database To: URN-IETF@LISTS.NETSOL.COM --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3403 Title: Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database Author(s): M. Mealling Status: Standards Track Date: October 2002 Mailbox: michael@neonym.net Pages: 14 Characters: 31058 Obsoletes: 2915, 2168 I-D Tag: draft-ietf-urn-dns-ddds-database-09.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3403.txt This document describes a Dynamic Delegation Discovery System (DDDS) Database using the Domain Name System (DNS) as a distributed database of Rules. The Keys are domain-names and the Rules are encoded using the Naming Authority Pointer (NAPTR) Resource Record (RR). Since this document obsoletes RFC 2915, it is the official specification for the NAPTR DNS Resource Record. It is also part of a series that is completely specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible to read and understand any document in this series without reading the others. This document is a product of the Uniform Resource Names Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021017165555.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3403 --OtherAccess Content-Type: Message/External-body; name="rfc3403.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021017165555.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-urn-ietf@LISTS.NETSOL.COM Thu Oct 17 21:02:47 2002 Received: from lists.netsol.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01591 for ; Thu, 17 Oct 2002 21:02:46 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id VAA15625; Thu, 17 Oct 2002 21:05:40 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 10568 for URN-IETF@LISTS.NETSOL.COM; Thu, 17 Oct 2002 21:02:53 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id UAA15011 for ; Thu, 17 Oct 2002 20:08:05 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNtND26365; Thu, 17 Oct 2002 16:55:23 -0700 (PDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Message-ID: <200210172355.g9HNtND26365@gamma.isi.edu> Date: Thu, 17 Oct 2002 16:55:23 -0700 Reply-To: rfc-editor@RFC-EDITOR.ORG Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: rfc-editor@RFC-EDITOR.ORG Subject: RFC 3402 on Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm To: URN-IETF@LISTS.NETSOL.COM --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3402 Title: Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm Author(s): M. Mealling Status: Standards Track Date: October 2002 Mailbox: michael@neonym.net Pages: 17 Characters: 38925 Obsoletes: 2915, 2168 I-D Tag: draft-ietf-urn-ddds-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3402.txt This document describes the Dynamic Delegation Discovery System (DDDS) algorithm for applying dynamically retrieved string transformation rules to an application-unique string. Well-formed transformation rules will reflect the delegation of management of information associated with the string. This document is also part of a series that is completely specified in "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS" (RFC 3401). It is very important to note that it is impossible to read and understand any document in this series without reading the others. This document is a product of the Uniform Resource Names Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021017165329.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3402 --OtherAccess Content-Type: Message/External-body; name="rfc3402.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021017165329.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-urn-ietf@LISTS.NETSOL.COM Thu Oct 17 21:05:41 2002 Received: from lists.netsol.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01702 for ; Thu, 17 Oct 2002 21:05:40 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id VAA15716; Thu, 17 Oct 2002 21:08:41 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 10572 for URN-IETF@LISTS.NETSOL.COM; Thu, 17 Oct 2002 21:05:54 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id UAA14999 for ; Thu, 17 Oct 2002 20:05:46 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g9HNr4D25201; Thu, 17 Oct 2002 16:53:04 -0700 (PDT) Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Message-ID: <200210172353.g9HNr4D25201@gamma.isi.edu> Date: Thu, 17 Oct 2002 16:53:04 -0700 Reply-To: rfc-editor@RFC-EDITOR.ORG Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: rfc-editor@RFC-EDITOR.ORG Subject: RFC 3401 on Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS To: URN-IETF@LISTS.NETSOL.COM --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3401 Title: Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS Author(s): M. Mealling Status: Informational Date: October 2002 Mailbox: michael@neonym.net Pages: 6 Characters: 10172 Updates: 2276 Obsoletes: 2915, 2168 I-D Tag: draft-ietf-urn-ddds-toc-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3401.txt This document specifies the exact documents that make up the complete Dynamic Delegation Discovery System (DDDS). DDDS is an abstract algorithm for applying dynamically retrieved string transformation rules to an application-unique string. This document along with RFC 3402, RFC 3403 and RFC 3404 obsolete RFC 2168 and RFC 2915, as well as updates RFC 2276. This document is a product of the Uniform Resource Names Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <021017165023.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3401 --OtherAccess Content-Type: Message/External-body; name="rfc3401.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <021017165023.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-urn-ietf@LISTS.NETSOL.COM Tue Oct 22 17:15:29 2002 Received: from lists.netsol.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04868 for ; Tue, 22 Oct 2002 17:15:28 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id RAA21112; Tue, 22 Oct 2002 17:23:51 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 12549 for URN-IETF@LISTS.NETSOL.COM; Tue, 22 Oct 2002 17:20:35 -0400 Received: from cliffie.verisignlabs.com (bulkregister-ldap.verisignlabs.com [65.201.175.62] (may be forged)) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id RAA21105 for ; Tue, 22 Oct 2002 17:20:33 -0400 (EDT) Received: from thinkingcat.com (h140.s251.netsol.com [216.168.251.140]) (AUTH: PLAIN leslie, TLS: TLSv1/SSLv3,128bits,RC4-MD5) by cliffie.verisignlabs.com with esmtp; Tue, 22 Oct 2002 17:07:19 -0400 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Approved-By: Leslie Daigle Message-ID: <3DB5BE28.2020200@thinkingcat.com> Date: Tue, 22 Oct 2002 17:07:52 -0400 Reply-To: Leslie Daigle From: Leslie Daigle Subject: So long, and thanks for all the... [Fwd: WG Action: Uniform Resource Names (URN) to conclude] To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit Hello all, Six years in the making (let alone a few years of earlier discussion :-) but we have done it: successfully concluded the work on our URN WG charter and gotten all the relevant documents published. Thanks and congratulations! Leslie. (Happily picking the blue dot from her IETF badge... ;-) -------- Original Message -------- Subject: WG Action: Uniform Resource Names (URN) to conclude Date: Tue, 22 Oct 2002 16:08:36 -0400 From: The IESG To: IETF-Announce: ; The Uniform Resource Names (URN) Working Group in the Applications Area of the IETF has concluded. The IESG contact persons are Patrik Faltstrom and Ned Freed. -- ------------------------------------------------------------------- "An essential element of a successful journey is recognizing when you have arrived." -- ThinkingCat (c.1983 - 2002) Leslie Daigle leslie@thinkingcat.com ------------------------------------------------------------------- From owner-urn-ietf@LISTS.NETSOL.COM Tue Oct 22 18:16:15 2002 Received: from lists.netsol.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06211 for ; Tue, 22 Oct 2002 18:16:14 -0400 (EDT) Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id SAA21954; Tue, 22 Oct 2002 18:24:43 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 12683 for URN-IETF@LISTS.NETSOL.COM; Tue, 22 Oct 2002 18:21:53 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from bab5.dscga.com (IDENT:root@bab5.dscga.com [207.120.28.7]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id SAA21769 for ; Tue, 22 Oct 2002 18:09:59 -0400 (EDT) Received: from mmealling (usrpppma.dscga.com [207.120.28.232]) by bab5.dscga.com (8.11.0/8.11.0) with SMTP id g9MLtdN29002 for ; Tue, 22 Oct 2002 17:55:40 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: <028801c27a15$d5dede50$e71c78cf@netsol.com> Date: Tue, 22 Oct 2002 17:56:10 -0400 Reply-To: Michael Mealling From: Michael Mealling Subject: all of our documents have been published! To: URN-IETF@LISTS.NETSOL.COM Content-Transfer-Encoding: 7bit In case anyone missed the announcements, all of the documents that the URN working group had on its plate have been published: RFC 3401 Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS RFC 3402 Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm RFC 3403 Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database RFC 3404 Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) Resolution Application RFC 3405 (BCP 65) Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedure RFC 3406 (BCP 66) Uniform Resource Names (URN) Namespace Definition Mechanisms Also note the fact that since they have been published, the IANA has also setup and is currently running the uri.arpa and urn.arpa zones. Information on how to subscribe to the register@ur*.arpa lists will be forthcoming....