From owner-urn-ietf@LISTS.NETSOL.COM Thu Jun 13 12:13:30 2002 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19955 for ; Thu, 13 Jun 2002 12:13:30 -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 MAA06621; Thu, 13 Jun 2002 12:08:40 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 50028 for URN-IETF@LISTS.NETSOL.COM; Thu, 13 Jun 2002 12:07:49 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from ietf.org (odin.ietf.org [132.151.1.176]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id KAA06331 for ; Thu, 13 Jun 2002 10:55:36 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15786; Thu, 13 Jun 2002 10:48:32 -0400 (EDT) Message-ID: <200206131448.KAA15786@ietf.org> Date: Thu, 13 Jun 2002 10:48:32 -0400 Reply-To: The IESG Comments: RFC822 error: Incorrect or incomplete address field found and ignored. From: The IESG Subject: Protocol Action: Dynamic Delegation Discovery System (DDDS) to Proposed Standard To: URN-IETF@LISTS.NETSOL.COM The IESG has approved the following Internet-Drafts for publication as Proposed Standards o Dynamic Delegation Discovery System (DDDS) o A DDDS Database Using The Domain Name System o URI Resolution using the Dynamic Delegation Discovery System The IESG aslo approved publication of Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS Standard as an Informational RFC. Publication of these documents obsoletes RFC2915 and RFC2168. These documents are the product of the Uniform Resource Names Working Group. The IESG contact persons are Ned Freed and Patrik Faltstrom. Technical Summary The DDDS defines an abstract algorithm for applying dynamically retrieved string transformation rules to an application-unique string. This means in reality that given some specific input string, one can fetch transformation rules from a DDDS database, and by applying them get the desired result. The key is that the DDDS algorithm is abstract, and not dependent on any specific database or protocol technology. The second document specifies how DDDS can be implemented using the domain name system, and the third how one DDDS database (for example one using DNS) can be used for resolution of URI schemes. Working Group Summary The URN working group have been using NAPTR resource records according to specifications in RFC 2915 and 2168. Experience from the last couple of years have shown that the description needed to be split and abstracted in the three parts we see here. The wg had consensus for this solution. Protocol Quality The protocol was reviewed by Patrik Faltstrom. From owner-urn-ietf@LISTS.NETSOL.COM Thu Jun 13 12:46:34 2002 Received: from lists.netsol.com (lists.netsol.com [216.168.224.214]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21432 for ; Thu, 13 Jun 2002 12:46:34 -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 MAA07274; Thu, 13 Jun 2002 12:42:20 -0400 (EDT) Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 50123 for URN-IETF@LISTS.NETSOL.COM; Thu, 13 Jun 2002 12:42:13 -0400 Approved-By: michael@BAILEY.DSCGA.COM Received: from bailey.dscga.com (bailey.neonym.net [198.78.11.130]) by lists.netsol.com (8.9.3/8.9.3) with ESMTP id MAA06829 for ; Thu, 13 Jun 2002 12:17:41 -0400 (EDT) Received: from bailey.dscga.com (localhost [127.0.0.1]) by bailey.dscga.com (8.12.1/8.12.1) with ESMTP id g5DG9rRP004514 for ; Thu, 13 Jun 2002 12:09:53 -0400 (EDT) Received: (from michael@localhost) by bailey.dscga.com (8.12.1/8.12.1/Submit) id g5DG9rqv004513 for URN-IETF@LISTS.NETSOL.COM; Thu, 13 Jun 2002 12:09:53 -0400 (EDT) References: <200206131448.KAA15786@ietf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.22.1i Message-ID: <20020613120952.I1751@bailey.dscga.com> Date: Thu, 13 Jun 2002 12:09:52 -0400 Reply-To: Michael Mealling From: Michael Mealling Subject: Re: Protocol Action: Dynamic Delegation Discovery System (DDDS) to Proposed Standard To: URN-IETF@LISTS.NETSOL.COM In-Reply-To: <200206131448.KAA15786@ietf.org> Yes! Thanks to everyone who helped with getting these documents finished. The final reviews we had were very detailed and thorough. Being able to get those kinds of comments with these documents showed dedication, stamina and possibly insomnia. Thanks! -MM On Thu, Jun 13, 2002 at 10:48:32AM -0400, The IESG wrote: > The IESG has approved the following Internet-Drafts for publication as > Proposed Standards > > o Dynamic Delegation Discovery System (DDDS) > > > o A DDDS Database Using The Domain Name System > > > o URI Resolution using the Dynamic Delegation Discovery System > > > The IESG aslo approved publication of Dynamic Delegation Discovery > System (DDDS) Part One: The Comprehensive DDDS Standard > as an Informational RFC. > > Publication of these documents obsoletes RFC2915 and RFC2168. > > > These documents are the product of the Uniform Resource Names Working > Group. The IESG contact persons are Ned Freed and Patrik Faltstrom. > > > Technical Summary > > The DDDS defines an abstract algorithm for applying dynamically > retrieved string transformation rules to an application-unique > string. This means in reality that given some specific input string, > one can fetch transformation rules from a DDDS database, and by > applying them get the desired result. The key is that the DDDS > algorithm is abstract, and not dependent on any specific database or > protocol technology. > > The second document specifies how DDDS can be implemented using the > domain name system, and the third how one DDDS database (for example > one using DNS) can be used for resolution of URI schemes. > > Working Group Summary > > The URN working group have been using NAPTR resource records > according to specifications in RFC 2915 and 2168. Experience from the > last couple of years have shown that the description needed to be > split and abstracted in the three parts we see here. The wg had > consensus for this solution. > > Protocol Quality > > The protocol was reviewed by Patrik Faltstrom. -- -------------------------------------------------------------------------------- Michael Mealling | Vote Libertarian! | urn:pin:1 michael@neonym.net | | http://www.neonym.net