RFC 2732: Format for Literal IPv6 Addresses in URL's
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 the format for literal IPv6 Addresses in URL's for implementation in World Wide Web browsers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2732
- Published
- December 1999
- Authors
- R. Hinden; B. Carpenter; L. Masinter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 5
- 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
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 5092IMAP URL SchemeUpdated
November 2007
- RFC 3041Privacy Extensions for Stateless Address Autoconfiguration in IPv6Obsoleted
January 2001
- RFC 3087Control of Service Context using SIP Request-URICurrent
April 2001
- RFC 2192IMAP URL SchemeObsoleted
September 1997
- RFC 2187Application of Internet Cache Protocol (ICP), version 2Current
September 1997
- RFC 2648A URN Namespace for IETF DocumentsUpdated
August 1999
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
- RFC 2017Definition of the URL MIME External-Body Access-TypeCurrent
October 1996
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?