RFC 4193: Unique Local IPv6 Unicast Addresses

This document defines an IPv6 unicast address format that is globally unique and is intended for local communications, usually inside of a site. These…

Read RFC 4193 on the RFC Editor

Outgoing relationships (10 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
Normative reference — RFC 1305: Network Time Protocol (Version 3) Specification, Implementation and Analysis
Normative reference — RFC 3513: Internet Protocol Version 6 (IPv6) Addressing Architecture
Normative reference — RFC 3174: US Secure Hash Algorithm 1 (SHA1)
Normative reference — RFC 2463: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
Normative reference — RFC 3587: IPv6 Global Unicast Address Format
Informative reference — RFC 3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Informative reference — RFC 2462: IPv6 Stateless Address Autoconfiguration
Informative reference — RFC 3484: Default Address Selection for Internet Protocol version 6 (IPv6)

Incoming relationships (48 related RFCs)

Normatively referenced by — RFC 6275: Mobility Support in IPv6
Normatively referenced by — RFC 6724: Default Address Selection for Internet Protocol Version 6 (IPv6)
Normatively referenced by — RFC 6887: Port Control Protocol (PCP)
Normatively referenced by — RFC 6775: Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)
Normatively referenced by — RFC 7217: A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)
Normatively referenced by — RFC 6296: IPv6-to-IPv6 Network Prefix Translation
Normatively referenced by — RFC 7084: Basic Requirements for IPv6 Customer Edge Routers
Normatively referenced by — RFC 6092: Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service
Normatively referenced by — RFC 7871: Client Subnet in DNS Queries
Normatively referenced by — RFC 7239: Forwarded HTTP Extension
Normatively referenced by — RFC 7788: Home Networking Control Protocol
Normatively referenced by — RFC 9462: Discovery of Designated Resolvers
Normatively referenced by — RFC 8368: Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance (OAM)
Normatively referenced by — RFC 6204: Basic Requirements for IPv6 Customer Edge Routers
Normatively referenced by — RFC 7428: Transmission of IPv6 Packets over ITU-T G.9959 Networks
Normatively referenced by — RFC 8994: An Autonomic Control Plane (ACP)
Normatively referenced by — RFC 7269: NAT64 Deployment Options and Experience
Normatively referenced by — RFC 8105: Transmission of IPv6 Packets over Digital Enhanced Cordless Telecommunications (DECT) Ultra Low Energy (ULE)
Normatively referenced by — RFC 8678: Enterprise Multihoming using Provider-Assigned IPv6 Addresses without Network Prefix Translation: Requirements and Solutions
Normatively referenced by — RFC 9818: DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANs
Informatively referenced by — RFC 4941: Privacy Extensions for Stateless Address Autoconfiguration in IPv6
Informatively referenced by — RFC 6890: Special-Purpose IP Address Registries
Informatively referenced by — RFC 5533: Shim6: Level 3 Multihoming Shim Protocol for IPv6
Informatively referenced by — RFC 6177: IPv6 Address Assignment to End Sites
Informatively referenced by — RFC 6740: Identifier-Locator Network Protocol (ILNP) Architectural Description
Informatively referenced by — RFC 6281: Understanding Apple's Back to My Mac (BTMM) Service
Informatively referenced by — RFC 6731: Improved Recursive DNS Server Selection for Multi-Interfaced Nodes
Informatively referenced by — RFC 7668: IPv6 over BLUETOOTH(R) Low Energy
Informatively referenced by — RFC 9099: Operational Security Considerations for IPv6 Networks
Informatively referenced by — RFC 5739: IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2)
Informatively referenced by — RFC 8244: Special-Use Domain Names Problem Statement
Informatively referenced by — RFC 8799: Limited Domains and Internet Protocols
Informatively referenced by — RFC 7969: Customizing DHCP Configuration on the Basis of Network Topology
Informatively referenced by — RFC 9915: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Informatively referenced by — RFC 4621: Design of the IKEv2 Mobility and Multihoming (MOBIKE) Protocol
Informatively referenced by — RFC 6866: Problem Statement for Renumbering IPv6 Hosts with Static Addresses in Enterprise Networks
Informatively referenced by — RFC 6981: A Framework for IP and MPLS Fast Reroute Using Not-Via Addresses
Informatively referenced by — RFC 6751: Native IPv6 behind IPv4-to-IPv4 NAT Customer Premises Equipment (6a44)
Informatively referenced by — RFC 7574: Peer-to-Peer Streaming Peer Protocol (PPSPP)
Informatively referenced by — RFC 8190: Updates to the Special-Purpose IP Address Registries
Informatively referenced by — RFC 8416: Simplified Local Internet Number Resource Management with the RPKI (SLURM)
Informatively referenced by — RFC 8766: Discovery Proxy for Multicast DNS-Based Service Discovery
Informatively referenced by — RFC 9526: Simple Provisioning of Public Names for Residential Networks
Informatively referenced by — RFC 9365: IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases
Informatively referenced by — RFC 9762: Using Router Advertisements to Signal the Availability of DHCPv6 Prefix Delegation to Clients
Informatively referenced by — RFC 9837: The IPv6 VPN Service Destination Option
Informatively referenced by — RFC 9898: Neighbor Discovery Considerations in IPv6 Deployments
Informatively referenced by — RFC 10001: Operational Guidelines for DNS Transport in Mixed IPv4/IPv6 Environments