RFC 8305: Happy Eyeballs Version 2: Better Connectivity Using Concurrency

Many communication protocols operating over the modern Internet use hostnames. These often resolve to multiple IP addresses, each of which may have different…

Read RFC 8305 on the RFC Editor

Outgoing relationships (14 related RFCs)

Obsoletes — RFC 6555: Happy Eyeballs: Success with Dual-Stack Hosts
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 4821: Packetization Layer Path MTU Discovery
Normative reference — RFC 6146: Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
Normative reference — RFC 6724: Default Address Selection for Internet Protocol Version 6 (IPv6)
Normative reference — RFC 6052: IPv6 Addressing of IPv4/IPv6 Translators
Normative reference — RFC 6147: DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
Normative reference — RFC 6298: Computing TCP's Retransmission Timer
Normative reference — RFC 7050: Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis
Normative reference — RFC 6535: Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)
Informative reference — RFC 8200: Internet Protocol, Version 6 (IPv6) Specification
Informative reference — RFC 7413: TCP Fast Open
Informative reference — RFC 6877: 464XLAT: Combination of Stateful and Stateless Translation

Incoming relationships (16 related RFCs)

Normatively referenced by — RFC 9460: Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Normatively referenced by — RFC 9132: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Normatively referenced by — RFC 8489: Session Traversal Utilities for NAT (STUN)
Normatively referenced by — RFC 8656: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
Normatively referenced by — RFC 8683: Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise Networks
Normatively referenced by — RFC 9623: Implementing Interfaces to Transport Services
Informatively referenced by — RFC 8803: 0-RTT TCP Convert Protocol
Informatively referenced by — RFC 9131: Gratuitous Neighbor Discovery: Creating Neighbor Cache Entries on First-Hop Routers
Informatively referenced by — RFC 9484: Proxying IP in HTTP
Informatively referenced by — RFC 9621: Architecture and Requirements for Transport Services
Informatively referenced by — RFC 8883: ICMPv6 Errors for Discarding Packets Due to Processing Limits
Informatively referenced by — RFC 9149: TLS Ticket Requests
Informatively referenced by — RFC 9386: IPv6 Deployment Status
Informatively referenced by — RFC 9872: Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis
Informatively referenced by — RFC 9079: Source-Specific Routing in the Babel Routing Protocol
Informatively referenced by — RFC 9824: Compact Denial of Existence in DNSSEC