]> APNIC

6 Cordelia St South Brisbane QLD 4101 Australia gih@apnic.net

Google, Inc.

warren@kumari.net

Internet WG Working Group IPv6 Loopback Documentation This document updates the IP Version 6 Address Architecture to define the IPv6 address prefix ::/32 as the Loopback address prefix. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Source for this draft and an issue tracker can be found at .

Introduction In the IP address architecture, a loopback address is a special IP address used by hosts to send data to itself. Packets directed to a loopback address are automatically routed back to the sending host’s network software stack without ever reaching the physical network interface. This has use in some forms of testing and is used to support a non-network method to facilitate local inter-process communication within a host. This document updates the IP Version 6 Address Architecture to define the IPv6 address prefix ::/32 as the Loopback address prefix.

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Loopback addresses The IPv4 network 127.0.0.0/8 was reserved by the IANA in where tha class-based address architecture was described. It is understood that it was the IANA's policy at the time to reserve the first and last network of each class, and the address prefixes 0.0.0.0/8 and 127.0.0.0/8 from the Class A space were reserved in accordance with this practice. listed the 127.0.0.0/8 address prefix as being used by the loopback function, and this function was listed as a requirement for all Internet hosts in . The "loopback" function is defined such that an outbound packet that triggers this loopback function should loop back to the packet ingress queue for processing by the same host. No packet that is addresses to a network 127 address should ever to passed to any network. , the original IPv6 Addressing Architecture document, allocates a single local loopback address, ::1. This single address allocation has been preserved in all subsequent revision to the IPv6 addressing specification (, , ) These addresses enable localhost communication, network diagnostics, and inter-process connections, making them essential for developers and IT professionals. Multiple loopback addresses can increase the number of distinct sockets that can be used for inter-process communication within a host. A larger local loopback address in IPv6 can permit large numbers of distinct concurrent loopback TCP connections within a single host, which is comparable the the functionality supported in the IPv4 loopback address prefix.

The IPv6 Loopback Prefix The IANA IPv6 Address registry denotes the address prefix ::/8 as being reserved by the IETF in . This range has been partially allocated with the prefix ::FFFF:0:0/32 being used in the context of an IPv6 transition technology to map IPv4 addresses into IPv6 addresses. The document expands the set of IPv6 loopback addresses to span the address prefix range ::0 through to ::FFFFFFFF (or ::/32 in prefix notation). This RFC replaces section 2.5.2 and 2.5.3 of as follows:

• The Loopback prefix The unicast address prefix ::/32 is called the loopback address prefix. The first address of this address prefix block, 0:0:0:0:0:0:0:0, is also termed the "unspecified address". This address MUST NOT be assigned to any node, as it indicates the absence of an address. One example of the use of this address is in the Source Address field of any IPv6 packets sent by an initializing host before it has learned its own address. All other loopback addresses drawn from this prefix may be used by a node as a destination address to send an IPv6 packet to itself. These addresses MUST NOT be assigned to any physical interface. These addresses are treated as having Link-Local scope, and may be thought of as the Link-Local unicast address prefix of a virtual interface (typically called the "loopback interface") to an imaginary link that goes nowhere. All loopback addresses other than the unspecified address MUST NOT be used as the source address in IPv6 packets that are sent outside of a single node. An IPv6 packet with a destination address of loopback address MUST NOT be sent outside of a single node and must never be forwarded by an IPv6 router. A packet received on an interface with a destination loopback address MUST be dropped.

((Geoff: I have gone for a simple prefix that sits below the IPv4-mapped address block of 0:0:0:0:0:FFFF::/32 - the complication is that the prefix then includes the "unspecified address" as well.)) ((Geoff: this last sentence of the paragraph on the unspecified address, lifted from RFC4291, strikes me as incorrect! If a packet is sent out an interface with a source address of all zeros then nobody can respond and the packet has no purpose. I'm inclined to drop this sentence from the proposed update, but as I don't think I was paying attention to IPv6 when this text was originally incorporated into the IPv6 Address Architecture so I have no idea what scenario was being referenced in this case.))

Security Considerations IPv6 addressing documents do not have any direct impact on Internet infrastructure security. ((WK: I don't think that we need to add anything about the "Unspecified Address", nor the behavior of "packets with source address of ::" since this is already covered in RFC 4291, but figured I'd mention it here for completeness.))

IANA Considerations The IANA is requested to amend the IPv6 Address registry and the IPv6 Special Purpose Address registry to record the designation of the IPv6 address prefix ::/32 as denoting the IPV6 Loopback function.

References Normative References This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. This document obsoletes RFC 3513, "IP Version 6 Addressing Architecture". [STANDARDS-TRACK] In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Informative References This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-997. Obsoletes RFC-960, 943, 923 and 900. This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK] This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. [STANDARDS-TRACK] This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. [STANDARDS-TRACK] This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. [STANDARDS-TRACK]

Acknowledgments TODO acknowledge.