RFC 6555
Happy Eyeballs: Success with Dual-Stack Hosts, April 2012
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 8305
- Authors:
- D. Wing
A. Yourtchenko - Stream:
- IETF
- Source:
- v6ops (ops)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6555
Discuss this RFC: Send questions or comments to the mailing list v6ops@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6555
Abstract
When a server's IPv4 path and protocol are working, but the server's IPv6 path and protocol are not working, a dual-stack client application experiences significant connection delay compared to an IPv4-only client. This is undesirable because it causes the dual- stack client to have a worse user experience. This document specifies requirements for algorithms that reduce this user-visible delay and provides an algorithm. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.