IPP> [Fwd: I-D ACTION:draft-ietf-urn-naptr-03.txt]

IPP> [Fwd: I-D ACTION:draft-ietf-urn-naptr-03.txt]

IPP> [Fwd: I-D ACTION:draft-ietf-urn-naptr-03.txt]

Randy Turner rturner at sharplabs.com
Wed Mar 5 17:17:59 EST 1997


This is a multi-part message in MIME format.


--------------222213185FF6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


FYI,


Information on resolving URNs through the DNS.....




Randy








Internet-Drafts at ietf.org wrote:
> 
>  A Revised 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     : Resolution of Uniform Resource Identifiers using the
>                    Domain Name System
>        Author(s) : R. Daniel, M. Mealling
>        Filename  : draft-ietf-urn-naptr-03.txt
>        Pages     : 14
>        Date      : 02/27/1997
> 
> Uniform Resource Locators (URLs) are the foundation of the World Wide Web,
> and are a vital Internet technology. However, they have proven to be
> brittle in practice. The basic problem is that URLs typically identify a
> particular path to a file on a particular host. There is no graceful way of
> changing the path or host once the URL has been assigned. Neither is there
> a graceful way of replicating the resource located by the URL to achieve
> better network utilization and/or fault tolerance. Uniform Resource Names
> (URNs) have been hypothesized as a adjunct to URLs that would overcome such
> problems. URNs and URLs are both instances of a broader class of
> identifiers known as Uniform Resource Identifiers (URIs).
> 
> This document describes a new DNS Resource Record, NAPTR (Naming Authority
> PoinTeR), that provides rules for mapping parts of URIs to domain names.
> By changing the mapping rules, we can change the host that is contacted to
> resolve a URI.  This will allow a more graceful handling of URLs over
> long time periods, and forms the foundation for a new proposal for
> Uniform Resource Names.
> 
> Internet-Drafts are 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-naptr-03.txt".
> A URL for the Internet-Draft is:
> ftp://ds.internic.net/internet-drafts/draft-ietf-urn-naptr-03.txt
> 
> Internet-Drafts directories are located at:
> 
>      o  Africa:  ftp.is.co.za
> 
>      o  Europe:  ftp.nordu.net
>                  ftp.nis.garr.it
> 
>      o  Pacific Rim: munnari.oz.au
> 
>      o  US East Coast: ds.internic.net
> 
>      o  US West Coast: ftp.isi.edu
> 
> Internet-Drafts are also available by mail.
> 
> Send a message to:  mailserv at ds.internic.net. In the body type:
>      "FILE /internet-drafts/draft-ietf-urn-naptr-03.txt".
> 
> NOTE: The mail server at ds.internic.net 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.
> 
>     ---------------------------------------------------------------
> 
>                          Access-Type: anon-ftp
>                                 Site: ds.internic.net
>        Link to Document    Directory: internet-drafts
>                                 Name: draft-ietf-urn-naptr-03.txt
>                                 Type: text/plain


--------------222213185FF6
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


Received: from slafw.sharplabs.com (gatekeeper.sharplabs.com [204.203.96.101])
          by sla5c.enet.sharplabs.com (8.8.4/8.8.4) with ESMTP
	  id HAA06667 for <rturner at sheltie.sharplabs.com>; Mon, 3 Mar 1997 07:59:56 -0800 (PST)
Received: from ietf.org (ietf.org [132.151.1.19]) by slafw.sharplabs.com (8.8.4/8.7.3) with SMTP id IAA05788 for <rturner at sharplabs.com>; Mon, 3 Mar 1997 08:06:54 -0800 (PST)
Received: from ietf.org by ietf.org id aa05376; 3 Mar 97 9:38 EST
Received: from ietf.ietf.org by ietf.org id aa03780; 3 Mar 97 9:24 EST
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
cc: urn-ietf at bunyip.com
Sender: ietf-announce-request at ietf.org
From: Internet-Drafts at ietf.org
Reply-to: Internet-Drafts at ietf.org
Subject: I-D ACTION:draft-ietf-urn-naptr-03.txt
Date: Mon, 03 Mar 1997 09:24:11 -0500
X-Orig-Sender: cclark at ietf.org
Message-ID:  <9703030924.aa03780 at ietf.org>


--NextPart


 A Revised 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     : Resolution of Uniform Resource Identifiers using the 
                   Domain Name System                                      
       Author(s) : R. Daniel, M. Mealling
       Filename  : draft-ietf-urn-naptr-03.txt
       Pages     : 14
       Date      : 02/27/1997


Uniform Resource Locators (URLs) are the foundation of the World Wide Web, 
and are a vital Internet technology. However, they have proven to be 
brittle in practice. The basic problem is that URLs typically identify a 
particular path to a file on a particular host. There is no graceful way of
changing the path or host once the URL has been assigned. Neither is there 
a graceful way of replicating the resource located by the URL to achieve 
better network utilization and/or fault tolerance. Uniform Resource Names 
(URNs) have been hypothesized as a adjunct to URLs that would overcome such
problems. URNs and URLs are both instances of a broader class of 
identifiers known as Uniform Resource Identifiers (URIs). 


This document describes a new DNS Resource Record, NAPTR (Naming Authority 
PoinTeR), that provides rules for mapping parts of URIs to domain names. 
By changing the mapping rules, we can change the host that is contacted to 
resolve a URI.  This will allow a more graceful handling of URLs over 
long time periods, and forms the foundation for a new proposal for 
Uniform Resource Names.    


Internet-Drafts are 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-naptr-03.txt".
A URL for the Internet-Draft is:
ftp://ds.internic.net/internet-drafts/draft-ietf-urn-naptr-03.txt
 
Internet-Drafts directories are located at:	
	                                                
     o  Africa:  ftp.is.co.za                    
	                                                
     o  Europe:  ftp.nordu.net            	
                 ftp.nis.garr.it                 
	                                                
     o  Pacific Rim: munnari.oz.au               
	                                                
     o  US East Coast: ds.internic.net           
	                                                
     o  US West Coast: ftp.isi.edu               
	                                                
Internet-Drafts are also available by mail.	
	                                                
Send a message to:  mailserv at ds.internic.net. In the body type: 
     "FILE /internet-drafts/draft-ietf-urn-naptr-03.txt".
							
NOTE: The mail server at ds.internic.net 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 at ds.internic.net"


Content-Type: text/plain
Content-ID: <19970227135257.I-D at ietf.org>


ENCODING mime
FILE /internet-drafts/draft-ietf-urn-naptr-03.txt


--OtherAccess
Content-Type:   Message/External-body;
        name="draft-ietf-urn-naptr-03.txt";
        site="ds.internic.net";
        access-type="anon-ftp";
        directory="internet-drafts"


Content-Type: text/plain
Content-ID: <19970227135257.I-D at ietf.org>


--OtherAccess--


--NextPart--






--------------222213185FF6--



More information about the Ipp mailing list