From owner-urn-ietf@LISTS.NETSOL.COM  Tue Feb  5 13:05:47 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 NAA11256
	for <urn-archive@IETF.ORG>; Tue, 5 Feb 2002 13:05:45 -0500 (EST)
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 NAA02478;
	Tue, 5 Feb 2002 13:02:24 -0500 (EST)
Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 19388 for URN-IETF@LISTS.NETSOL.COM; Tue, 5 Feb
          2002 13:01:35 -0500
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 MAA02399 for <urn-ietf@lists.netsol.com>;
          Tue, 5 Feb 2002 12:45:00 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org
          (8.9.1a/8.9.1a) with ESMTP id MAA10240; Tue, 5 Feb 2002 12:38:48
          -0500 (EST)
Message-ID:  <200202051738.MAA10240@ietf.org>
Date:         Tue, 5 Feb 2002 12:38:48 -0500
Reply-To: The IESG <iesg-secretary@ietf.org>
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
From: The IESG <iesg-secretary@ietf.org>
Subject:      Protocol Action: URN Namespace Definition Mechanisms to BCP
To: URN-IETF@LISTS.NETSOL.COM

The IESG has approved the Internet-Draft 'URN Namespace Definition
Mechanisms' <draft-ietf-urn-rfc2611bis-04.txt> as a BCP.  This document
is the product of the Uniform Resource Names Working Group.  The IESG
contact persons are Ned Freed and Patrik Faltstrom.

This document obsoletes RFC 2611.

Technical Summary

The document specifies the registration process for URN namespace
identifiers. It focuses on the ability to inherit existing namespaces and
identifiers as URN's.


Working Group Summary

This documents obsoletes RFC 2611, partially on request from the IESG which
according to both RFC 2611 and this new document is the authority which
approves formal namespaces via the RFC publication process. RFC 2611 was
updated by the URN wg, and discussed on the appropriate mailing lists.


Protocol Quality

The spec was reviewed by Patrik Faltstrom.

Note to RFC Editor:

Please replace ftp://ftp.isi.edu/in-notes/iana/assignments/URN-namespaces/
with http://www.iana.org/assignments/urn-namespaces


From owner-urn-ietf@LISTS.NETSOL.COM  Mon Feb 18 15:43:11 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 PAA17562
	for <urn-archive@IETF.ORG>; Mon, 18 Feb 2002 15:43:11 -0500 (EST)
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 PAA05530;
	Mon, 18 Feb 2002 15:44:15 -0500 (EST)
Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 22009 for URN-IETF@LISTS.NETSOL.COM; Mon, 18 Feb
          2002 15:43:17 -0500
Received: from plexus.cst.ca (plexus.CST.CA [207.139.176.42]) by
          lists.netsol.com (8.9.3/8.9.3) with ESMTP id PAA05513 for
          <urn-ietf@lists.netsol.com>; Mon, 18 Feb 2002 15:43:16 -0500 (EST)
Received: from earth.in.steltor.com (earth.in.steltor.com [101.1.1.100]) by
          plexus.cst.ca (8.9.3/1.0.1) with ESMTP id PAA21601; Mon, 18 Feb 2002
          15:36:40 -0500
Received: from steltor.com (c-1782.in.steltor.com [101.1.42.13]) by
          earth.in.steltor.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id
          g1IKadQ23727; Mon, 18 Feb 2002 15:36:39 -0500 (EST)
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr-CA,pdf
MIME-Version: 1.0
References: <OF98191EB7.84B833FE-ON85256B61.00695232@incentivesystems.com>
            <3C6D919A.1C84D7C4@steltor.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Approved-By:  Bernard Desruisseaux <bernard@STELTOR.COM>
Message-ID:  <3C716653.F03814BA@steltor.com>
Date:         Mon, 18 Feb 2002 15:38:43 -0500
Reply-To: Bernard Desruisseaux <bernard@steltor.com>
From: Bernard Desruisseaux <bernard@steltor.com>
Organization: Steltor <http://www.steltor.com>
Subject:      CAP URL definition
To: URN-IETF@LISTS.NETSOL.COM
Content-Transfer-Encoding: 7bit

[ I'm cross posting this message to ietf-urn in the hope that people
  from this working group might help us with our CAP URL definition. ]

As requested by members of ietf-calendar I've changed my proposal
(see http://www.imc.org/ietf-calendar/mail-archive/msg04439.html)
to forbid CAP URLs of the following forms:

   cap:///abcd1234QWER
   cap:/abcd1234QWER

Comments anyone?

--------------------------------------------------------------------

2.x CAP URL

   The CAP URL scheme is used to designate calendar stores,
   and calendars accessible using the CAP protocol.

   The CAP URL scheme conform to the generic URL syntax,
   defined in RFC 2396, and follows the Guidelines for URL
   Schemes, set forth in RFC 2718.

   A CAP URL begins with the protocol prefix "cap" and is
   defined by the following grammar.

      capurl   = scheme ":" [ "//" csid ] [ "/" relcalid ]
      scheme   = "cap"
      csid     = hostport   ; As defined in Section 3.2.2 of RFC 2396
      relcalid = *uric      ; As defined in Section 2 of RFC 2396

   'relcalid' is an identifier that uniquely identifies a calendar
   on a particular calendar store. There is no implied structure in
   a Relative CALID. It may refer to the calendar of a user or of a
   resource such as a conference room. It MUST be unique within the
   calendar store.

   Examples:

      cap://cal.example.com
      cap://cal.example.com/abcd1234QWER

   Relative CAP URLs are permitted and are resolved according
   to the rules defined in Section 5 of RFC 2396.

   Example of a relative CAP URL:

      abcd1234QWER


2.x Calendar Addresses

   Calendar addresses can be described as absolute or relative
   CAP URLs.

   Examples:

      cap://cal.example.com/abcd1234QWER
      abcd1234QWER

   For a user currently authenticated to the CAP server on
   cal.example.com, all four addresses refer to the same
   calendar.

--------------------------------------------------------------------

Regards,
Bernard
--
Bernard Desruisseaux                    mailto:bernard@steltor.com
Research & Development                  Tel.  : +1 514 733-8500 x4213
Steltor                                 Fax   : +1 514 733-8878


From owner-urn-ietf@LISTS.NETSOL.COM  Tue Feb 19 13:48:20 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 NAA01124
	for <urn-archive@IETF.ORG>; Tue, 19 Feb 2002 13:48:19 -0500 (EST)
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 NAA10570;
	Tue, 19 Feb 2002 13:46:09 -0500 (EST)
Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 22343 for URN-IETF@LISTS.NETSOL.COM; Tue, 19 Feb
          2002 13:45:35 -0500
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 NAA10512 for
          <urn-ietf@lists.netsol.com>; Tue, 19 Feb 2002 13:34:18 -0500 (EST)
Received: from bailey.dscga.com (localhost [127.0.0.1]) by bailey.dscga.com
          (8.12.1/8.12.1) with ESMTP id g1JIO3I2000390; Tue, 19 Feb 2002
          13:24:03 -0500 (EST)
Received: (from michael@localhost) by bailey.dscga.com (8.12.1/8.12.1/Submit)
          id g1JIO1Tj000389; Tue, 19 Feb 2002 13:24:01 -0500 (EST)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.22.1i
Message-ID:  <20020219132401.J26811@bailey.dscga.com>
Date:         Tue, 19 Feb 2002 13:24:01 -0500
Reply-To: Michael Mealling <michael@neonym.net>
From: Michael Mealling <michael@neonym.net>
Subject:      updated DDDS drafts....
To: URN-IETF@LISTS.NETSOL.COM

Hi all,
  You should see a new set of DDDS updates come by soon. The significant
changes were due to IESG comments concerning a screw up in discussing
the Preference and Priority fields. Apparently one of the documents
discussed the Priority field in terms of weighted random selection in
one section which is in exact opposition to the stated purpose of
signifying preference in the other documents. This apparently tripped up one
document author already.
  There were some other subsequence clarifications brought on by comments
from the ENUM group (thanks guys!). I also changed the use of the term 'URL'
to 'URI' where appropriate.

-MM

--
--------------------------------------------------------------------------------
Michael Mealling        |      Vote Libertarian!       | urn:pin:1
michael@neonym.net      |                              | http://www.neonym.net


From owner-urn-ietf@LISTS.NETSOL.COM  Tue Feb 19 15:56:58 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 PAA05293
	for <urn-archive@IETF.ORG>; Tue, 19 Feb 2002 15:56:58 -0500 (EST)
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 PAA11553;
	Tue, 19 Feb 2002 15:55:01 -0500 (EST)
Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 22514 for URN-IETF@LISTS.NETSOL.COM; Tue, 19 Feb
          2002 15:54:33 -0500
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 PAA11490 for
          <urn-ietf@lists.netsol.com>; Tue, 19 Feb 2002 15:42:51 -0500 (EST)
Received: from bailey.dscga.com (localhost [127.0.0.1]) by bailey.dscga.com
          (8.12.1/8.12.1) with ESMTP id g1JKWaI2000887; Tue, 19 Feb 2002
          15:32:37 -0500 (EST)
Received: (from michael@localhost) by bailey.dscga.com (8.12.1/8.12.1/Submit)
          id g1JKWa5l000886; Tue, 19 Feb 2002 15:32:36 -0500 (EST)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.22.1i
Message-ID:  <20020219153236.P26811@bailey.dscga.com>
Date:         Tue, 19 Feb 2002 15:32:36 -0500
Reply-To: Michael Mealling <michael@neonym.net>
From: Michael Mealling <michael@neonym.net>
Subject:      frequently asked DDDS questions?
To: URN-IETF@LISTS.NETSOL.COM

Hi everyone,
  I'm in the process of collecting questions for a DDDS FAQ. If you've
found one or there some particular part of the DDDS you keep tripping up
on I'd appreciate a short note letting me know what it is and what
the answer is so I can put it in the list. You can see the beginnings
at http://uri.net/ddds-faq.html.

Thanks!

-MM

--
--------------------------------------------------------------------------------
Michael Mealling        |      Vote Libertarian!       | urn:pin:1
michael@neonym.net      |                              | http://www.neonym.net


From owner-urn-ietf@LISTS.NETSOL.COM  Wed Feb 20 08:01:22 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 IAA29129
	for <urn-archive@IETF.ORG>; Wed, 20 Feb 2002 08:01:22 -0500 (EST)
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 HAA15862;
	Wed, 20 Feb 2002 07:59:34 -0500 (EST)
Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 22914 for URN-IETF@LISTS.NETSOL.COM; Wed, 20 Feb
          2002 07:59:14 -0500
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 HAA15657 for <urn-ietf@lists.netsol.com>;
          Wed, 20 Feb 2002 07:14:19 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org
          (8.9.1a/8.9.1a) with ESMTP id HAA27934; Wed, 20 Feb 2002 07:08:12
          -0500 (EST)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Message-ID:  <200202201208.HAA27934@ietf.org>
Date:         Wed, 20 Feb 2002 07:08:12 -0500
Reply-To: Internet-Drafts@ietf.org
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
From: Internet-Drafts@ietf.org
Subject:      I-D ACTION:draft-ietf-urn-uri-res-ddds-06.txt
To: URN-IETF@LISTS.NETSOL.COM

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Uniform Resource Names Working Group of the IETF.

        Title           : Dynamic Delegation Discovery System (DDDS) Part Four:
                          The URI Resolution Application
        Author(s)       : M. Mealling
        Filename        : draft-ietf-urn-uri-res-ddds-06.txt
        Pages           : 25
        Date            : 19-Feb-02

A specification for taking a 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
Standard' (RFC WWWW).  It is very important to note that it is
impossible to read and understand any document in this series without
reading the others.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-urn-uri-res-ddds-06.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
        "get draft-ietf-urn-uri-res-ddds-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ietf-urn-uri-res-ddds-06.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
        access-type="mail-server";
        server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:     <20020219135541.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-urn-uri-res-ddds-06.txt

--OtherAccess
Content-Type: Message/External-body;
        name="draft-ietf-urn-uri-res-ddds-06.txt";
        site="ftp.ietf.org";
        access-type="anon-ftp";
        directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <20020219135541.I-D@ietf.org>

--OtherAccess--

--NextPart--


From owner-urn-ietf@LISTS.NETSOL.COM  Wed Feb 20 08:01:33 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 IAA29147
	for <urn-archive@IETF.ORG>; Wed, 20 Feb 2002 08:01:32 -0500 (EST)
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 IAA15901;
	Wed, 20 Feb 2002 08:00:36 -0500 (EST)
Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 22918 for URN-IETF@LISTS.NETSOL.COM; Wed, 20 Feb
          2002 08:00:33 -0500
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 HAA15645 for <urn-ietf@lists.netsol.com>;
          Wed, 20 Feb 2002 07:14:14 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org
          (8.9.1a/8.9.1a) with ESMTP id HAA27913; Wed, 20 Feb 2002 07:08:07
          -0500 (EST)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Message-ID:  <200202201208.HAA27913@ietf.org>
Date:         Wed, 20 Feb 2002 07:08:07 -0500
Reply-To: Internet-Drafts@ietf.org
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
From: Internet-Drafts@ietf.org
Subject:      I-D ACTION:draft-ietf-urn-ddds-06.txt
To: URN-IETF@LISTS.NETSOL.COM

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Uniform Resource Names Working Group of the IETF.

        Title           : Dynamic Delegation Discovery System (DDDS)Part Two:
                          The Algorithm
        Author(s)       : M. Mealling
        Filename        : draft-ietf-urn-ddds-06.txt
        Pages           : 23
        Date            : 19-Feb-02

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 Standard'
(RFC WWWW).  It is very important to note that it is impossible to
read and understand any document in this series without reading the
others.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-urn-ddds-06.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
        "get draft-ietf-urn-ddds-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ietf-urn-ddds-06.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
        access-type="mail-server";
        server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:     <20020219135528.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-urn-ddds-06.txt

--OtherAccess
Content-Type: Message/External-body;
        name="draft-ietf-urn-ddds-06.txt";
        site="ftp.ietf.org";
        access-type="anon-ftp";
        directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <20020219135528.I-D@ietf.org>

--OtherAccess--

--NextPart--


From owner-urn-ietf@LISTS.NETSOL.COM  Wed Feb 20 08:01:44 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 IAA29171
	for <urn-archive@IETF.ORG>; Wed, 20 Feb 2002 08:01:44 -0500 (EST)
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 IAA15923;
	Wed, 20 Feb 2002 08:00:48 -0500 (EST)
Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 22922 for URN-IETF@LISTS.NETSOL.COM; Wed, 20 Feb
          2002 08:00:44 -0500
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 HAA15633 for <urn-ietf@lists.netsol.com>;
          Wed, 20 Feb 2002 07:14:09 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org
          (8.9.1a/8.9.1a) with ESMTP id HAA27892; Wed, 20 Feb 2002 07:08:02
          -0500 (EST)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Message-ID:  <200202201208.HAA27892@ietf.org>
Date:         Wed, 20 Feb 2002 07:08:02 -0500
Reply-To: Internet-Drafts@ietf.org
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
From: Internet-Drafts@ietf.org
Subject:      I-D ACTION:draft-ietf-urn-ddds-toc-02.txt
To: URN-IETF@LISTS.NETSOL.COM

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Uniform Resource Names Working Group of the IETF.

        Title           : Dynamic Delegation Discovery System (DDDS) Part One:
                          The Comprehensive DDDS Standard
        Author(s)       : M. Mealling
        Filename        : draft-ietf-urn-ddds-toc-02.txt
        Pages           : 10
        Date            : 19-Feb-02

This document specifies the exact documents that make up the complete
Dynamic Delegation Discovery System (DDDS) standard.  The DDDS is an
abstract algorithm for applying dynamically retrieved string
transformation rules to an application-unique string.
This document along with RFC XXXX, RFC YYYY and RFC ZZZZ obsolete RFC
2168 [8] and RFC 2915 [6] as well as update RFC 2276 [5].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-urn-ddds-toc-02.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
        "get draft-ietf-urn-ddds-toc-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ietf-urn-ddds-toc-02.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
        access-type="mail-server";
        server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:     <20020219135516.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-urn-ddds-toc-02.txt

--OtherAccess
Content-Type: Message/External-body;
        name="draft-ietf-urn-ddds-toc-02.txt";
        site="ftp.ietf.org";
        access-type="anon-ftp";
        directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <20020219135516.I-D@ietf.org>

--OtherAccess--

--NextPart--


From owner-urn-ietf@LISTS.NETSOL.COM  Wed Feb 20 08:02:20 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 IAA29189
	for <urn-archive@IETF.ORG>; Wed, 20 Feb 2002 08:02:20 -0500 (EST)
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 IAA15996;
	Wed, 20 Feb 2002 08:01:18 -0500 (EST)
Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 22930 for URN-IETF@LISTS.NETSOL.COM; Wed, 20 Feb
          2002 08:01:13 -0500
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 HAA15609 for <urn-ietf@lists.netsol.com>;
          Wed, 20 Feb 2002 07:13:59 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org
          (8.9.1a/8.9.1a) with ESMTP id HAA27850; Wed, 20 Feb 2002 07:07:52
          -0500 (EST)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Message-ID:  <200202201207.HAA27850@ietf.org>
Date:         Wed, 20 Feb 2002 07:07:52 -0500
Reply-To: Internet-Drafts@ietf.org
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
From: Internet-Drafts@ietf.org
Subject:      I-D ACTION:draft-ietf-urn-dns-ddds-database-08.txt
To: URN-IETF@LISTS.NETSOL.COM

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Uniform Resource Names Working Group of the IETF.

        Title           : Dynamic Delegation Discovery System  (DDDS) Part
                          Three: The DNS Database
        Author(s)       : M. Mealling
        Filename        : draft-ietf-urn-dns-ddds-database-08.txt
        Pages           : 20
        Date            : 19-Feb-02

This document describes a Dynamic Delegation Discovery System
Database using the Domain Name System as a distributed database of
Rules. The Keys are domain-names and the Rules are encoded using the
NAPTR Resource Record.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-urn-dns-ddds-database-08.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
        "get draft-ietf-urn-dns-ddds-database-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ietf-urn-dns-ddds-database-08.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
        access-type="mail-server";
        server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:     <20020219135452.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-urn-dns-ddds-database-08.txt

--OtherAccess
Content-Type: Message/External-body;
        name="draft-ietf-urn-dns-ddds-database-08.txt";
        site="ftp.ietf.org";
        access-type="anon-ftp";
        directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <20020219135452.I-D@ietf.org>

--OtherAccess--

--NextPart--


From owner-urn-ietf@LISTS.NETSOL.COM  Wed Feb 20 08:02:21 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 IAA29201
	for <urn-archive@IETF.ORG>; Wed, 20 Feb 2002 08:02:21 -0500 (EST)
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 IAA15951;
	Wed, 20 Feb 2002 08:01:03 -0500 (EST)
Received: from LISTS.NETSOL.COM by LISTS.NETSOL.COM (LISTSERV-TCP/IP release
          1.8d) with spool id 22926 for URN-IETF@LISTS.NETSOL.COM; Wed, 20 Feb
          2002 08:00:59 -0500
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 HAA15621 for <urn-ietf@lists.netsol.com>;
          Wed, 20 Feb 2002 07:14:04 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org
          (8.9.1a/8.9.1a) with ESMTP id HAA27871; Wed, 20 Feb 2002 07:07:57
          -0500 (EST)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Message-ID:  <200202201207.HAA27871@ietf.org>
Date:         Wed, 20 Feb 2002 07:07:57 -0500
Reply-To: Internet-Drafts@ietf.org
Comments:     RFC822 error: <W> Incorrect or incomplete address field found and
              ignored.
From: Internet-Drafts@ietf.org
Subject:      I-D ACTION:draft-ietf-urn-net-procedures-10.txt
To: URN-IETF@LISTS.NETSOL.COM

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Uniform Resource Names Working Group of the IETF.

        Title           : Dynamic Delegation Discovery System (DDDS) Part Five:
                          URI.ARPA Assignment Procedures
        Author(s)       : M. Mealling
        Filename        : draft-ietf-urn-net-procedures-10.txt
        Pages           : 10
        Date            : 19-Feb-02

RFCYYYY defines a how DNS is used as a DDDS database that contains
URI delegation rules (sometimes called resolution hints).  That
document specifies that the first step in that algorithm is to append
'URI.ARPA' to the URI scheme and retrieve the NAPTR record for that
domain-name.  I.e., the first step in resolving 'http://foo.com/'
would be to look up a NAPTR record for the domain 'http.URI.ARPA'.
URN resolution also follows a similar procedure but uses the
'URN.ARPA' zone as its root.  This document describes the procedures
for inserting a new rule into the 'URI.ARPA' and 'URN.ARPA' zones.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-urn-net-procedures-10.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
        "get draft-ietf-urn-net-procedures-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ietf-urn-net-procedures-10.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
        access-type="mail-server";
        server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:     <20020219135504.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-urn-net-procedures-10.txt

--OtherAccess
Content-Type: Message/External-body;
        name="draft-ietf-urn-net-procedures-10.txt";
        site="ftp.ietf.org";
        access-type="anon-ftp";
        directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <20020219135504.I-D@ietf.org>

--OtherAccess--

--NextPart--


