URI Resolution Services Necessary for URN Resolution
Voir toute la rfc dans une seule page
Page : 11 / 16
Télécharger le PDF
Auteur(s) : R. Daniel
, M. Mealling
Classé sous : Names
RFC 2483 URI Resolution Services January 1999
5. The text/uri-list Internet Media Type
Several of the resolution service requests, such as I2Ls, I2Ns,
result in a list of URIs being returned to the client. The text/uri-
list Internet Media Type is defined to provide a simple format for
the automatic processing of such lists of URIs.
This is a copy of the IANA registration of the text/uri-list Media
Date: Fri, 18 Apr 97 08:36:07 PDT
From: Ron Daniel Jr. <firstname.lastname@example.org>
To: email@example.com, firstname.lastname@example.org
Subject: Request for MIME media type Text/IETF Tree - uri-list
Name : Ron Daniel Jr.
E-mail : email@example.com
MIME media type name : Text
MIME subtype name : IETF Tree -uri-list
Required parameters : none
Optional parameters : charset
Currently, URIs can be represented using US-ASCII. However, there
are many non-standard URIs which use special character sets.
Discussion of how to best achieve internationalization of URIs is
underway. This registration will be updated with a discussion of the
URI charsets once that discussion has concluded.
Encoding considerations : Some transfer protocols, such as SMTP,
place limits on the length of lines. Very long URIs might exceed
those limits. Systems must therefore be prepared to use a suitable
content transfer encoding. This is anticipated to be a rare
Security considerations : Client software should be aware of the
security considerations of URIs. For example, accessing some URIs
can result in sending a death threat to a head of state, frequently
prompting a visit from the relevant protective service. Accessing
other URIs may result in financial obligations, or access to
resources considered inappropriate by one's employer.
Mealling & Daniel Experimental [Page 11]