RFC 2276: Architectural Principles of Uniform Resource Name Resolution
In plain English — editorial summary, not part of the RFC
This document addresses the issues of the discovery of URN (Uniform Resource Name) resolver services that in turn will directly translate URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource Characteristics). This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2276
- Published
- January 1998
- Authors
- K. Sollins
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 24
- Also known as
- —
- Updated by:
- RFC 3401
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
- RFC 2483URI Resolution Services Necessary for URN ResolutionCurrent
January 1999
- RFC 2017Definition of the URL MIME External-Body Access-TypeCurrent
October 1996
- RFC 2141URN SyntaxObsoleted
May 1997
- RFC 2079Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs)Current
January 1997
- RFC 1959An LDAP URL FormatObsoleted
June 1996
- RFC 2611URN Namespace Definition MechanismsObsoleted
June 1999
- RFC 2648A URN Namespace for IETF DocumentsUpdated
August 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?