<?xml version='1.0' encoding='UTF-8'?>

<reference anchor='RFC2483'>

<front>
<title abbrev='URI Resolution Services'>URI Resolution Services Necessary for URN Resolution</title>
<author initials='M.' surname='Mealling' fullname='Michael Mealling'>
<organization>Network Solutions</organization>
<address>
<postal>
<street>505 Huntmar Park Drive</street>
<city>Herndon</city>
<region>VA</region>
<code>22070</code>
<country>USA</country></postal>
<phone>+1 703 742 0400</phone>
<facsimile>+1 703 742 9552</facsimile>
<email>michaelm@rwhois.net</email></address></author>
<author initials='R.' surname='Daniel' fullname='Ron Daniel'>
<organization>Los Alamos National Laboratory, ,Advanced Computing Lab</organization>
<address>
<postal>
<street>MS B287</street>
<city>Los Alamos</city>
<region>NM</region>
<code>87545</code>
<country>USA</country></postal>
<phone>+1 505 665 0597</phone>
<facsimile>+1 505 665 4939</facsimile>
<email>rdaniel@lanl.gov</email></address></author>
<date year='1999' month='January' />
<area>Applications</area>
<keyword>uniform resource identifier</keyword>
<keyword>URI</keyword>
<abstract>
<t>
   Retrieving the resource identified by a Uniform Resource Identifier
   (URI)  is only one of the operations that can be performed on a
   URI.  One might also ask for and get a list of other identifiers that
   are aliases for the original URI or a bibliographic description of
   the resource the URI denotes, for example. This applies to both
   Uniform Resource Names (URNs) and Uniform Resource Locators (URLs).
   Uniform Resource Characteristics (URCs) are discussed in this
   document but only as descriptions of resources rather than
   identifiers.
</t>
<t>
   A service in the network providing access to a resource may provide
   one or some of these options, but it need not provide all of them.
   This memo specifies an initial set of these operations that can be
   used to describe the interactions provided by a given access service.
   It also suggests guidelines that should be adhered to when those
   operations are encoded in a protocol.
</t></abstract></front>

<seriesInfo name='RFC' value='2483' />
<format type='TXT' octets='30518' target='http://www.rfc-editor.org/rfc/rfc2483.txt' />
<format type='HTML' octets='55191' target='http://xml.resource.org/public/rfc/html/rfc2483.html' />
<format type='XML' octets='43991' target='http://xml.resource.org/public/rfc/xml/rfc2483.xml' />
</reference>
