RFC 8136: Additional Transition Functionality for IPv6

This document proposes an additional mechanism intended to both facilitate transition from IPv4 to IPv6 and improve the latter's security and privacy.

Read RFC 8136 on the RFC Editor

Outgoing relationships (12 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 3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Normative reference — RFC 1122: Requirements for Internet Hosts - Communication Layers
Normative reference — RFC 4862: IPv6 Stateless Address Autoconfiguration
Normative reference — RFC 7217: A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)
Normative reference — RFC 6555: Happy Eyeballs: Success with Dual-Stack Hosts
Normative reference — RFC 7136: Significance of IPv6 Interface Identifiers
Normative reference — RFC 6164: Using 127-Bit IPv6 Prefixes on Inter-Router Links
Informative reference — RFC 7721: Security and Privacy Considerations for IPv6 Address Generation Mechanisms
Informative reference — RFC 3514: The Security Flag in the IPv4 Header
Informative reference — RFC 7421: Analysis of the 64-bit Boundary in IPv6 Addressing