RFC 8305: Happy Eyeballs Version 2: Better Connectivity Using Concurrency
In plain English — editorial summary, not part of the RFC
Many communication protocols operating over the modern Internet use hostnames. These often resolve to multiple IP addresses, each of which may have different performance and connectivity characteristics. Since specific addresses or address families (IPv4 or IPv6) may be blocked, broken, or sub-optimal on a network, clients that attempt multiple connections in parallel have a chance of establishing a connection more quickly. This document specifies requirements for algorithms that reduce this user-visible delay and provides an example algorithm, referred to as "Happy Eyeballs". This document obsoletes the original algorithm description in RFC 6555.
Document record
- Document ID
- RFC8305
- Published
- December 2017
- Authors
- D. Schinazi; T. Pauly
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 15
- Also known as
- —
- Obsoletes:
- RFC 6555
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 9224Finding the Authoritative Registration Data Access Protocol (RDAP) ServiceCurrent
March 2022
- RFC 7984Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP NetworkCurrent
September 2016
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 2012
- RFC 8683Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise NetworksCurrent
November 2019
- RFC 9210DNS Transport over TCP - Operational RequirementsCurrent
March 2022
- RFC 9872Recommendations for Discovering IPv6 Prefix Used for IPv6 Address SynthesisCurrent
September 2025
- RFC 10001Operational Guidelines for DNS Transport in Mixed IPv4/IPv6 EnvironmentsCurrent
August 2026
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?