RFC 6556: Testing Eyeball Happiness
In plain English — editorial summary, not part of the RFC
The amount of time it takes to establish a session using common transport APIs in dual-stack networks and networks with filtering such as proposed in BCP 38 is a barrier to IPv6 deployment. This note describes a test that can be used to determine whether an application can reliably establish sessions quickly in a complex environment such as dual-stack (IPv4+IPv6) deployment or IPv6 deployment with multiple prefixes and upstream ingress filtering. This test is not a test of a specific algorithm, but of the external behavior of the system as a black box. Any algorithm that has the intended external behavior will be accepted by it. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6556
- Published
- April 2012
- Authors
- F. Baker
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 2012
- RFC 6619Scalable Operation of Address Translators with Per-Interface BindingsCurrent
June 2012
- RFC 6145IP/ICMP Translation AlgorithmObsoleted
April 2011
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 7484Finding the Authoritative Registration Data (RDAP) ServiceObsoleted
March 2015
- RFC 5549Advertising IPv4 Network Layer Reachability Information with an IPv6 Next HopObsoleted
May 2009
- RFC 7600IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)Current
July 2015
- RFC 7915IP/ICMP Translation AlgorithmCurrent
June 2016
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?