RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3986.
Current document in this lineage: RFC 3986 — Uniform Resource Identifier (URI): Generic Syntax
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2396
- Published
- August 1998
- Authors
- T. Berners-Lee; R. Fielding; L. Masinter
- Status
- DRAFT STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 40
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 1808 (1995)
- RFC 2396 (1998)
- RFC 2732 (1999)
- RFC 3986 (2005) ✓
Read the full history of Uniform Resource Identifier (URI): Generic Syntax →
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2384POP URL SchemeCurrent
August 1998
- RFC 2482Language Tagging in Unicode Plain TextObsoleted
January 1999
- RFC 2254The String Representation of LDAP Search FiltersObsoleted
December 1997
- RFC 2253Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished NamesObsoleted
December 1997
- RFC 3490Internationalizing Domain Names in Applications (IDNA)Obsoleted
March 2003
- RFC 4514Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished NamesCurrent
June 2006
- RFC 5890Internationalized Domain Names for Applications (IDNA): Definitions and Document FrameworkCurrent
August 2010
- RFC 5891Internationalized Domain Names in Applications (IDNA): ProtocolCurrent
August 2010
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?