IETF - Uniform Resource Identifiers (URI) Working GroupIETFUniform Resource Identifiers (URI) Working GroupAbout the Internet Engineering Task ForceOther active IETF Working GroupsInternet Notes at ISIInternet RFCs at InnosoftThis WG has concludedAt the Stockholm IETF, theIESG decided that the URI WG had "completed" its original goals, andthat its current work was too broad of scope for a single WG to everattain consensus. New working groups will be formed to deal with thespecific items of remaining work, to be announced on theURI mailing list. See also the URNworking group.RFC Revisions-in-progress and Internet-DraftsDiscussion of these and related topics takes place on the URI workinggroup mailing list <uri@w3.org>. A hypertextarchive of the mailing list is available.URL BOF Agenda for December IETFMinutes from Stockholm IETFMinutes from Danvers IETFMinutes from San Jose IETF "An '.ipv6' Top Level Pseudo-Domain", L. Masinter, J. Gettys, B. Carpenter, 16 Apr 1999. <draft-masinter-url-ipv6-02.txt> AbstractThe normal textual representation for IPv6 addresses as a setof colon-separated hexadecimal numbers does not work well withmost deployed URL-parsing software. This document describes analternate format which will pass unharmed through most URL-parsingsoftware. "Internationalized Uniform Resource Identifiers (IURI)", L. Masinter, M. Duerst, 28 Jun 1999. <draft-masinter-url-i18n-04.txt> AbstractURIs [RFC 2396] are defined as sequences of characters chosenfrom a limited subset of the repertoire of ASCII characters bothfor transmission in network protocols and representation in spokenand written human communication. This document defines IURIs (Internationalized URIs) as a sequenceof characters from the repertorie of the UCS (Universal CharacterSet). A mapping of IURIs to URIs and guidelines for the use anddeployment of IURIs in various elements of software that dealwith URIs are given. "Handling Internationalized Query Components in URLs", M. Duerst, 30 Jul 1997. <draft-duerst-query-i18n-00.txt> AbstractHTTP and HTML provide the facility to query the user and return theresults. This is usually done in the query component of an URL. Thismechanisms works with full satisfaction for characters of the us-ascii repertoire. Due to the lack of an agreed encoding for othercharacters, the situation is much less satisfactory for charactersoutside the us-ascii repertoire. "Requirements for Human Friendly Identifiers", M. Mealling, 02 Oct 1998. <draft-mealling-human-friendly-identifier-req-00.txt> AbstractThis document includes a set of requirements for an identifier thatis engineered for human consumption. While the identifier is stillmachine consumable, the services and capabilities of the underlyingsystem are designed with humans in mind. This includes concepts ofgeographic and context specific constraints, non-uniqueness, andnatural language match semantics.New URL Scheme Proposals "A FTP URL Format", J. Casey, 09 Jan 1997. <draft-casey-url-ftp-00.txt>AbstractThis document defines the format of Uniform Resource Locators (URL) for the File Transfer Protocol (FTP) using the general URL syntax defined in RFC xxxx, "Uniform Resource Locators (URL)". It is a one of a suite of documents which replace RFC 1738, "Uniform Resource Locators", and RFC 1808, "Relative Uniform Resource Locators". "A Gopher URL Format", M. Krishnan, J. Casey, 04 Dec 1996. <draft-murali-url-gopher.txt>Abstract This document defines the format of Uniform Resource Locators (URL) for the Gopher and Gopher+ protocols using the general URL syntax defined in RFC xxxx, "Uniform Resource Locators (URL)". It is a one of a suite of documents which replace RFC 1738, "Uniform Resource Locators", and RFC 1808, "Relative Uniform Resource Locators". "The 'news' URL scheme", A. Gilman, 05 Mar 1998. <draft-gilman-news-url-01.txt>AbstractThis document defines the format of Uniform Resource Locators(URLs) identifying news messages and groups. The syntax of'news' URLs from RFC 1738 is extended to allow specification ofthe site from which the message is to be sought and toincorporate protections via 'snews' URLs. This combines into the'news' scheme enough capability so that the previously-proposed'nntp' scheme can be retired and URL usage simplified. "The hnews URL scheme", T. Stockwell, 17 Jun 1998. <draft-stockwell-hnews-url-00.txt>AbstractHNEWS [1] is an HTTP-tunneling variant of the NNTP news protocol.This document defines the format of Uniform Resource Locators(URLs)identifying news messages and groups provided by HNEWS servers.The syntax of 'hnews' URLs is designed to be compatible with thecurrent common usage of the 'news' URL scheme. Specifically, the'hnews' URL scheme is designed according to recommendations made in[NEWS_URL_SCHEME]. [NEWS_URL_SCHEME] is based on the generalspecification of all URL schemes in 'Uniform Resource Locators (URL):Generic Syntax and Semantics' [RFC URI SYNTAX]. "The RWhois Uniform Resource Locator", S. Williamson, M. Mealling, 02 Aug 1997. <draft-mealling-rwhoisurl-01.txt>AbstractRWhois is an Internet directory access protocol, defined in RFC1714 [1] and RFC2167 [3]. This document describes a format for an RWhois Uniform Resource Locator (URL) that will allow Internet clients to have direct access to the RWhois protocol. An RWhois URL will represent a single query to an RWhois server. "WHOIS++ URL Specification", M. Hamilton, 13 Mar 1998. <draft-ietf-asid-whois-url-02.txt>AbstractThis document defines a new Uniform Resource Locator (URL) scheme "whois++", which provides a convention within the URL framework for referring to WHOIS++ servers and the data held within them. "SDP URL Scheme", K. Fujikawa, 07 Aug 1998. <draft-fujikawa-sdp-url-01.txt>Abstract This document describes a format for an Session Description Protocol Uniform Resource Locator (SDP URL) which will allow Internet clients to have direct access to multimedia sessions. "The service: URL Scheme", E. Guttman, 22 Nov 1996. <draft-ietf-svrloc-service-scheme-00.txt>Abstract The service: URL scheme is used to provide service access information for arbitrary network services. These URLs provide an extensible framework for client based network software to obtain configuration information required to make use of network services. A service: URL may be accompanied by a set of well defined attributes which define the characteristics of the service. These attributes may convey protocol configuration information to client software or service characteristics meaningful to end users. This document describes how to define and standardize new service types and attributes for use with the service: scheme and provides examples. "irc: URL scheme", M. Mirashi, 26 Aug 1996. <draft-mirashi-url-irc-01.txt>AbstractA new URL scheme "irc:" is defined. The irc URL scheme is used to refer to either IRC (Internet Relay Chat) servers or individual entities (channels or people) on IRC servers. "Videotex URL Specification", D. Mavrakis, H. Layec, K. Kartmann, 20 May 1997. <draft-mavrakis-videotex-url-spec-01.txt>AbstractA new URL scheme, "videotex" is defined. It allows videotex client softwareor terminals to connect to videotex services compliant to the ITU-T and ETSI videotex standards. "Requirements TV Broadcast URI Schemes", W. ten Kate, G. Thomas, C. Finseth, 18 Nov 1998. <draft-tenkate-tvweb-uri-reqs-00.txt>AbstractThis document lists the requirements posed to URI schemes for usein TV Broadcast environments. The document summarizes the outcomeof discussions on this subject by the W3C TV-Web Interest Group [1]. "Uniform Resource Identifiers for Television Broadcasts", D. Zigmond, M. Vickers, 07 Jan 2000. <draft-zigmond-tv-url-03.txt>AbstractWorld-Wide Web browsers are starting to appear on a variety ofconsumer electronic devices, such as television sets and televisionset-top boxes, which are capable of receiving television programmingfrom either terrestrial broadcast, satellite broadcast, or cable. Inthis context there is a need to reference television broadcastsusing the URI format described in [RFC 2396]. This documentdescribes a widely-implemented URI scheme to refer to suchbroadcasts. "URLs for GSM Short Message Service", A. Vaha-Sipila, 19 May 1999. <draft-antti-gsm-sms-url-04.txt>AbstractThis document specifies a URL (Uniform Resource Locator) scheme'gsm-sms' for specifying a recipient for an alphanumeric message(Short Message) in a GSM-based mobile phone system. Short Messagesare two-way paging messages that can be sent from a suitableequipped computer or a phone. "URLs for Telephone Calls", A. Vaha-Sipila, 29 Dec 1999. <draft-antti-telephony-url-12.txt>AbstractThis document specifies URL (Uniform Resource Locator) schemes'tel', 'fax' and 'modem' for specifying the location of aterminal in the phone network and the connection types (modes ofoperation) that can be used to connect to that entity. Thisspecification covers voice calls (normal phone calls, answeringmachines and voice messaging systems), facsimile (telefax) calls anddata calls, both for POTS and digital/mobile subscribers. "Conversational Multimedia URLs", P. Cordell, 23 Dec 1997. <draft-cordell-sg16-conv-url-00.txt>AbstractThe evolving technologies for real-time conversation over the Internetrequire URLs to provide user contact information. As there are manyprotocols (including some that are not Internet based) that can be usedfor inter-user conversation, this document describes a two stagetransaction process for obtaining a URL that can be used to initiateconversation. The first stage involves retrieving a list of protocolspecific URLs in a MIME encoded file. The MIME type enables anappropriate application to be launched which will analyse the presentedURLs and select the most appropriate one. The second stage involvesinterpreting the protocol specific URL and initiating the conversation.The protocol specific URLs are encoded in a URL form so that they can beembedded directly into HTML pages. This allows the first stage to beomitted. The document describes the format of the MIME encoded list ofURLs, and the format of a number of protocol specific URLs. "Stream URI Scheme", F. Kenji, K. Shinobu, T. Tsuyoshi, 03 Jan 2000. <draft-fujikawa-stream-uri-00.txt>AbstractThis document describes the Stream Uniform Resource Identifier whichallows Internet clients to have direct access to multimedia streams. "An SMTP URL Interface", R. Earhart, 29 Dec 1997. <draft-earhart-url-smtp-00.txt>Abstract It is occasionally useful to be able to reference a generic server to be used for message submission. URLs provide a good mechanism for refering to arbitrary network resources. The SMTP URL scheme allows a URL to specify an SMTP server, thus allowing other protocols to use a general ''URL to be used for message delivery'' in place of an explicit reference to SMTP. "The 'eid' URL Scheme", C. Finseth, 02 Apr 1999. <draft-finseth-url-00.txt>AbstractThis document defines a new URL scheme, 'eid'. This scheme providesa mechanism by which the local application can reference data thathas been obtained by other, non-URL scheme means. The scheme isintended to provide a general escape mechanism to allow access toinformation for applications that are too specialized to justifytheir own schemes.See also Historical Documents.Requests for CommentFunctional Recommendations for Internet Resource Locators (RFC 1736) (22415 bytes), J. Kunze, February 1995. This document specifies a minimum set of requirements for Internet resource locators, which convey location and access information for resources. Typical examples of resources include network accessible documents, WAIS databases, FTP servers, and Telnet destinations.Functional Requirements for Uniform Resource Names (RFC 1737) (16337 bytes), K. Sollins, L. Masinter, December 1994. This document specifies a minimum set of requirements for a kind of Internet resource identifier known as Uniform Resource Names (URNs). URNs fit within a larger Internet information architecture, which in turn is composed of, additionally, Uniform Resource Characteristics (URCs), and Uniform Resource Locators (URLs). URNs are used for identification, URCs for including meta-information, and URLs for locating or finding resources. It is provided as a basis for evaluating standards for URNs. The discussions of this work have occurred on the mailing list uri@bunyip.com and at the URI Working Group sessions of the IETF.Uniform Resource Locators (URL) (RFC 1738) (51348 bytes), T. Berners-Lee, L. Masinter, M. McCahill, December 1994. Updated by RFC 2396. This document specifies a Uniform Resource Locator (URL), the syntax and semantics of formalized information for location and access of resources via the Internet.Relative Uniform Resource Locators (RFC 1808) (34950 bytes), R. Fielding, June 1995, Updated by RFC 2396. A Uniform Resource Locator (URL) is a compact representation of the location and access method for a resource available via the Internet. When embedded within a base document, a URL in its absolute form may contain a great deal of information which is already known from the context of that base document's retrieval, including the scheme, network location, and parts of the url-path. In situations where the base URL is well-defined and known to the parser (human or machine), it is useful to be able to embed URL references which inherit that context rather than re-specifying it in every instance. This document defines the syntax and semantics for such Relative Uniform Resource Locators.The LDAP URL Format (RFC 2255) (20685 bytes) LDAP-WG, T. Howes, M. Smith, December 1997.LDAP is the Lightweight Directory Access Protocol, defined in [1], [2]and [3]. This document describes a format for an LDAP UniformResource Locator. The format describes an LDAP search operation toperform to retrieve information from an LDAP directory. This documentreplaces RFC 1959. It updates the LDAP URL format for version 3 ofLDAP and clarifies how LDAP URLs are resolved. This document alsodefines an extension mechanism for LDAP URLs, so that future documentscan extend their functionality, for example, to provide access to newLDAPv3 extensions as they are defined.Uniform Resource Locators for Z39.50 (RFC 2056) (14204 bytes), R. Denenberg, J. Kunze, D. Lynch, November 1996.Z39.50 is an information retrieval protocol that does not fit neatlyinto a retrieval model designed primarily around the stateless fetchof data. Instead, it models a general user inquiry as asession-oriented, multi-step task, any step of which may be suspendedtemporarily while the server requests additional parameters from theclient before continuing. Content-ID and Message-ID Uniform Resource Locators (RFC 2111) (9113 bytes), E. Levinson, March 1997. Obsoleted by RFC 2392.The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allowreferences to messages and the body parts of messages. For example,within a single multipart message, one HTML body part might includeembedded references to other parts of the same message. This documentis a product of the MIME Encapsulation of Aggregate HTML DocumentsWorking Group of the IETF. VEMMI URL Specification (RFC 2122), (25043 bytes), D. Mavrakis, H. Layec, K. Kartmann, March 1997.A new URL scheme, "vemmi" is defined. It allows VEMMI client software and VEMMI terminals to connect to multimedia interactive services compliant to the VEMMI standard (Enhanced Man-Machine Interface for Videotex and Multimedia/Hypermedia Information Retrieval Services), sometimes abbreviated as "VErsatile MultiMedia Interface". IMAP URL Scheme (RFC 2192), (31426 bytes), C. Newman, September 1997.IMAP [IMAP4] is a rich protocol for accessing remote message stores.It provides an ideal mechanism for accessing public mailing listarchives as well as private and shared message stores. Thisdocument defines a URL scheme for referencing objects on an IMAP server. NFS URL Scheme (RFC 2224), (22726 bytes), B. Callaghan, October 1997.A new URL scheme, 'nfs' is defined. It is used to referto files and directories on NFS servers using the generalURL syntax defined in RFC 1738, "Uniform Resource Locators (URL)". The mailto URL scheme (RFC 2368), (16502 bytes), P. Hoffman, L. Masinter, J. Zawinski, July 1998.This document defines the format of Uniform Resource Locators (URL)for designating electronic mail addresses. It is one of a suite ofdocuments which replace RFC 1738, 'Uniform Resource Locators', andRFC 1808, 'Relative Uniform Resource Locators'. The syntax of'mailto' URLs from RFC 1738 is extended to allow creation of more RFC822 messages by allowing the URL to express additional header and bodyfields. The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields (RFC 2369), (30853 bytes), G. Neufeld, J. Baer, July 1998.This is a proposal for additional header fields to be added to emailmessages sent by email distribution lists. The content of each newfield is typically a URL - usually mailto [RFC2368] - which locatesthe relevant information or performs the command directly. MTAsgenerating the header fields SHOULD usually include a mailto basedcommand, in addition to any other protocols used, in order to supportusers who do not have access to non-mail-based protocols. POP URL Scheme (RFC 2384), (13649 bytes), R. Gellens, August 1998.This memo defines a URL scheme for referencing a POP mailbox. Content-ID and Message-ID Uniform Resource Locators (RFC 2392) (11141 bytes), E. Levinson, August 1998.The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allowreferences to messages and the body parts of messages. For example,within a single multipart message, one HTML body part might includeembedded references to other parts of the same message. Uniform Resource Identifiers (URI): Generic Syntax (RFC 2396), (84503 bytes), T. Berners-Lee, R. Fielding, L. Masinter, August 1998. Additional information is available at Roy's test site. A Uniform Resource Identifier (URI) is a compact string of characters for identifying an abstract or physical resource. This document defines the generic syntax of URI, including both absolute and relative forms, and guidelines for their use; it revises and replaces the generic definitions in RFC 1738 and RFC 1808. This document defines a grammar that is a superset of all valid URI, such that an implementation can parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier type. This document does not define a generative grammar for URI; that task will be performed by the individual specifications of each URI scheme. The "data" URL scheme (RFC 2397), (9514 bytes), L. Masinter, August 1998. A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally. URI Resolution Services Necessary for URN Resolution (RFC 2483), (30518 bytes), M. Mealling, R. Daniel, Jr., January 1999. Retrieving the resource identified by a Uniform Resource Identifier(URI) [1] is only one of the operations that can be performed on aURI. One might also ask for and get a list of other identifiers thatare aliases for the original URI or a bibliographic description of theresource the URI denotes, for example. This applies to both UniformResource Names (URNs) and Uniform Resource Locators (URLs). UniformResource Characteristics (URCs) are discussed in this document butonly as descriptions of resources rather than identifiers. Registration Procedures for URL Scheme Names (RFC 2717), (19780 bytes), R. Petke, I. King, November 1999.This document defines the process by which new URL scheme names areregistered. Guidelines for new URL Schemes (RFC 2718), (19208 bytes), L. Masinter, H. Alvestrand, D. Zigmond, R. Petke, November 1999.A Uniform Resource Locator (URL) is a compact string representationof the location for a resource that is available via the Internet.This document provides guidelines for the definition of new URLschemes. Preferred Format for Literal IPv6 Addresses in URL's (RFC 2732), (7984 bytes), R. Hinden, B. Carpenter, L. Masinter, December 1999.This document defines the format for literal IPv6 Addresses in URL'sfor implementation in World Wide Web browsers. This format has beenimplemented in the IPv6 versions of several widely deployed browsersincluding Microsoft Internet Explorer, Mozilla, and Lynx. It is alsointended to be used in the IPv6 version of the service locationprotocol.This document includes an update to the generic syntax for UniformResource Identifiers defined in RFC 2396 [URL]. It defines a syntaxfor IPv6 addresses and allows the use of "[" and "]" within a URIexplicitly for this reserved purpose.Related WorkGeneral Discussion and ArchivesURI-WG Mailing List ArchivesW3C's collected info on WWW Names and Addresses, URIs, URLs, URNsRFC 1630 -- "Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web." T. Berners-Lee. June 1994.Ron Daniel's collected info on Uniform Resource IdentifiersUniform Resource Names (and other resource naming issues)Daniel LaLiberte's HyperNews info on URNsGordon Irlam's collected links on naming and distribution issues.LIFN work by Moore, Green, and Wade.Uniform Resource Characteristics and MetadataDaniel LaLiberte's HyperNews info on and URCsStu Weibel's list of library background material. Partial Redundant Distributed Meta-language (PRDM)OCLC/NCSA Metadata WorkshopThe Scientific and Technical Attribute Set (STAS)Network Information Retrieval and IIIRMichael Mealling's collected IIIR papers and URC, URN, whois++ software archive.RFC 1727 -- "A Vision of an Integrated Internet Information Service", C. Weider, P. Deutsch, 12/16/1994.RFC 1728 -- "Resource Transponders", C. Weider, 12/16/1994. RFC 1729 -- "Using the Z39.50 Information Retrieval Protocol in the Internet Environment", C. Lynch, 12/16/1994.Related Standards and DraftsIETF URNWorking GroupIETF HTTP Working GroupIETF HTML Working GroupDefinition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs) (RFC 2079)Roy FieldingDepartment of Information and Computer ScienceUniversity of California, Irvine, CA 92697-3425Last modified: 06 Oct 2000 |
|
