ietf-corpus

rfc-2732

Format for Literal IPv6 Addresses in URL's

R. Hinden, B. Carpenter, L. Masinter
date1999-12 streamIETF areaint wgipngwg statusPROPOSED STANDARD pages5 canonicalhttps://www.rfc-editor.org/rfc/rfc2732 doi10.17487/RFC2732 errataview
This document defines the format for literal IPv6 Addresses in URL's for implementation in World Wide Web browsers. [STANDARDS-TRACK]

obsoleted by

updates

Extracted elements (7)

design-rationale §1

The textual representation of IPv6 addresses (RFC 2373) uses ':' and '.' as delimiters, which conflict with URL syntax. Enclosing the address in brackets was chosen to allow easy cut-and-paste with minimal editing while avoiding delimiter ambiguity.

ip

interoperability-note §3

The IPv4address definition is updated to that of RFC 2373, which correctly constrains each segment to at most three decimal digits; this supersedes the RFC 2396 definition.

ip

normative-requirement §1.1 SHOULD

World Wide Web browsers SHOULD implement the format of IPv6 literals in URLs defined in this document. Other types of applications and protocols that use URLs MAY use this format.

ip, http

protocol-element §2

A literal IPv6 address in a URL must be enclosed in '[' and ']' characters, forming an 'ipv6reference' production: ipv6reference = '[' IPv6address ']', where IPv6address is defined in RFC 2373.

ip

protocol-element §3

The characters '[' and ']' are added to the RFC 2396 'reserved' set and removed from the 'unwise' set, making them legal within a URI exclusively for IPv6 literal address delimiters.

ip, http

security-consideration §4

The use of bracket-enclosed literal IPv6 addresses in URLs does not introduce any known new security concerns.

security, ip

wire-format §3

The URI host non-terminal is extended to three alternatives: host = hostname | IPv4address | IPv6reference. IPv6reference wraps the address in square brackets, e.g., http://[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:80/index.html.

ip, http