Network Working Group X. Xiao Internet-Draft Huawei Technologies Dusseldorf Intended status: Informational 15 November 2026 Expires: 19 May 2027 Enhanced Dual Stack: Connection-Informed IPv6/IPv4 Selection draft-xiao-v6ops-eds-03 Abstract This document describes Enhanced Dual Stack (EDS), a framework intended to reduce the operational risk and upfront workload of introducing IPv6 into existing IPv4 networks. EDS provides a connection-informed method for implementing RFC 6724 Rule 1, "Avoid unusable destinations", by remembering recent TCP/QUIC connection- establishment failures and avoiding repeated selection of affected IPv6 destinations. It also provides operational diagnostics so administrators can identify and correct IPv6 problems. EDS is complementary to Happy Eyeballs and does not require connection racing. By starting with selected EDS-capable pioneer hosts, performing practical validation, and expanding IPv6 gradually, EDS can be deployed incrementally without requiring all hosts to support EDS. With EDS, enterprises' IPv6 introduction can change from a heavy upfront validation process toward an incremental improvement process. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 19 May 2027. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. Xiao Expires 19 May 2027 [Page 1] Internet-Draft Enhanced Dual Stack November 2026 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Enhanced Dual Stack Framework . . . . . . . . . . . . . . . . 4 3.1. Connection-informed Destination Selection . . . . . . . . 4 3.1.1. Relationship to Happy Eyeballs . . . . . . . . . . . 7 3.2. Operational Diagnostics . . . . . . . . . . . . . . . . . 8 4. Incremental EDS Deployment . . . . . . . . . . . . . . . . . 9 5. Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 10 6. Standardization Considerations . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 9.1. Normative References . . . . . . . . . . . . . . . . . . 11 9.2. Informative References . . . . . . . . . . . . . . . . . 11 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13 1. Introduction [RFC6724], which replaced [RFC3484], defines destination-address selection between IPv6 and IPv4. Rule 1, "Avoid unusable destinations", does not specify a method for identifying unusable destinations from previous connection attempts. Rule 6, "Prefer higher precedence", normally prefers IPv6 over IPv4, even when IPv6 connectivity has recently failed, exposing users repeatedly to service degradation. To minimize user-visible disruption, IPv6 deployers must prevent IPv6 connection-establishment failures as much as possible. This requires heavy upfront validation before switching on IPv6. The needed work is described in [RFC7381] and is substantial. Consequently, the organizations that have deployed IPv6 are usually big ISPs and enterprises that need a large number of IP addresses. For other enterprises, especially those with limited IPv6 expertise and little need for additional address space, the benefits may not justify the migration effort. Unless an effort is made to simplify IPv6 introduction, these enterprises may remain in IPv4 for a long period of time. Xiao Expires 19 May 2027 [Page 2] Internet-Draft Enhanced Dual Stack November 2026 EDS is intended to simplify IPv6 introduction. It provides a connection-informed method of applying RFC 6724 Rule 1: remember recent TCP/QUIC connection-establishment failures and avoid repeatedly selecting affected IPv6 destinations. EDS also provides operational diagnostics so that administrators can identify and fix IPv6 problems over time. This changes the deployment model. Instead of requiring exhaustive validation before IPv6 can be enabled, administrators can perform upfront validation as much as practical, enable IPv6 for suitable hosts or environments, observe remaining problems, and improve IPv6 progressively. The objective is to change IPv6 deployment from a heavily front-loaded and somewhat risky process into a gradual operational improvement process. In other words, EDS intends to mimic the effect of "Duolingo for language learning" for IPv6. Before Duolingo, language learners had to find a language class, enroll, pay, and then go to classes several times a week. This big upfront effort works for people who need to master a language quickly, but not for many casual learners. By making the start very easy and spreading the learning effort over time, Duolingo has brought millions more people to learn foreign languages. EDS intends to bring many more enterprises to use IPv6 by making the start easy and spreading the learning and improvement effort over time. In addition, just like Duolingo has not prevented people from going to language class, EDS will not prevent people from introducing IPv6 with existing approaches. EDS and existing IPv6 deployment approaches can be used by different types of organizations. Happy Eyeballs (HE) [RFC8305] [HEv3] and EDS are different, complementary ways of addressing Rule 1's goal of avoiding unusable destinations. HE races IPv6/IPv4 connections; EDS remembers recent failures for subsequent destination selection. Section 3 compares them. The Transport Services (TAPS) architecture [RFC9621] and its abstract API [RFC9622] provide an asynchronous connection-establishment architecture that can select among multiple endpoints, paths, and transport protocols. TAPS can provide a long-term architectural basis for advanced connection establishment but TAPS does not help existing applications that do not support it. For EDS, TAPS is similar to HE. EDS is complementary to TAPS, as it is to HE, and does not require either TAPS or HE. Xiao Expires 19 May 2027 [Page 3] Internet-Draft Enhanced Dual Stack November 2026 1.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 2. Terminology Enhanced Dual Stack (EDS): A framework that combines connection- informed IPv6/IPv4 destination selection with operational diagnostics to reduce the risk and upfront workload of introducing IPv6. Connection-informed destination selection: Destination selection that applies RFC 6724 Rule 1 using applicable recent connection- establishment failures. Recent-failure state: Short-lived local state indicating that an IPv6 connection establishment attempt recently failed for an applicable network context, destination address, source prefix or address, and transport protocol and port. Operational Diagnostics: Local information that helps an authorized network administrator determine why IPv6 was not used or why it failed, and identify problems that can be corrected over time. EDS-capable host: A host that supports connection-informed destination selection and can expose the corresponding operational diagnostic information. 3. Enhanced Dual Stack Framework EDS consists of two complementary parts: connection-informed destination selection and operational diagnostics. 3.1. Connection-informed Destination Selection EDS provides a specific method for implementing RFC 6724 Rule 1, "Avoid unusable destinations", using recent TCP/QUIC connection- establishment failures. The corresponding record and selection behavior is intended to be specified in [ADDR-SELECT]. When there is no applicable recent-failure state, destination selection continues to follow the normal RFC 6724 precedence behavior, and suitable IPv6 destinations normally retain their preference over IPv4. Xiao Expires 19 May 2027 [Page 4] Internet-Draft Enhanced Dual Stack November 2026 When enabled, an EDS State Manager maintains a Recent IPv6 Failure Table, or equivalent host-local state, using applicable failures reported by TCP and QUIC connection-establishment implementations. A typical record contains: +===============================+===========================+ | Field | Example | +===============================+===========================+ | Network context | Corp-WiFi-A | +-------------------------------+---------------------------+ | IPv6 destination address | 2001:db8:1234:5678::42 | +-------------------------------+---------------------------+ | IPv6 source prefix or address | 2001:db8:1111:1200::/64 | +-------------------------------+---------------------------+ | Transport protocol and port | TCP/443 | +-------------------------------+---------------------------+ | Failure type | timeout | +-------------------------------+---------------------------+ | Timestamp | 2026-09-17T14:32:18+02:00 | +-------------------------------+---------------------------+ Table 1 The following logical components cooperate to populate and use the table: Xiao Expires 19 May 2027 [Page 5] Internet-Draft Enhanced Dual Stack November 2026 +================+========================+========================+ | Component | Existing or new? | EDS responsibility | +================+========================+========================+ | TCP stack / | Existing, enhanced | Report connection | | QUIC | (TCP connect() or QUIC | outcomes, destination, | | implementation | connection- | transport/port, and | | | establishment | available source/path | | | mechanism) | information. | +----------------+------------------------+------------------------+ | OS network | Existing, reused | Supply IPv6 source | | configuration | (interface-address and | address/prefix and | | | routing facilities) | network context. | +----------------+------------------------+------------------------+ | EDS State | New EDS logical | Combine information, | | Manager | function; may be | timestamp, maintain | | | integrated into the OS | and expire failure | | | | records. | +----------------+------------------------+------------------------+ | Destination- | Existing, enhanced | Consult applicable | | selection | (getaddrinfo() or | records when applying | | mechanism | equivalent) | RFC 6724 Rule 1. | +----------------+------------------------+------------------------+ Table 2 TCP/QUIC implementations report outcomes to the EDS State Manager through a local interface. The manager obtains missing network information from the OS and shares applicable failure state with destination selection. These logical functions need not be separate processes, and EDS does not define an internal API. The network context field identifies the network environment in which the failure occurred (e.g., a Wi-Fi network or VPN), so that failure state is not applied to unrelated networks. The IPv6 destination field contains the IPv6 destination address selected for the failed attempt. The IPv6 source field SHOULD contain the locally known prefix associated with the IPv6 source address selected for that attempt. The associated prefix length can be obtained from the host's interface-address configuration for the selected source address. If no applicable source prefix is known, the complete IPv6 source address SHOULD be used instead. An implementation MUST NOT infer a prefix length solely from the IPv6 address value. Xiao Expires 19 May 2027 [Page 6] Internet-Draft Enhanced Dual Stack November 2026 The asymmetry is intentional. A failure may be specific to an individual destination, so the destination is recorded as an address. On the source side, multiple source addresses, including temporary addresses, can belong to the same locally known prefix. Recording the source prefix when available keeps the failure state applicable across such source-address changes without unnecessarily creating separate state for each source address. The first four fields identify the scope to which the observation applies. Applicable failure types include timeout, unreachable, refusal, or reset. The recent-failure state is short-lived. [ADDR-SELECT] recommends expiration after 10 minutes, following the stateful Happy Eyeballs guidance in [RFC6555]. A subsequent successful establishment in the same applicable IPv6 context can clear the state, and a relevant network-context change can make it irrelevant. While applicable recent-failure state exists, Rule 1 can treat the affected IPv6 destination as unusable, allowing IPv4 to be preferred. When the state expires, normal selection gives IPv6 another opportunity after the problem may have been corrected. EDS does not require active probing, RTT measurement, packet-loss measurement, throughput measurement, or other performance ranking. It uses observed connection-establishment outcomes, such as those from TCP connect() or a QUIC connection-establishment mechanism. The first encounter with a previously unknown IPv6 problem can still be user-visible. The purpose of connection-informed selection is to learn from that failure and avoid repeatedly exposing later selections to the same recently failing IPv6 connectivity. This choice keeps EDS simple while avoiding repeated failures. 3.1.1. Relationship to Happy Eyeballs HE and EDS are complementary approaches to avoiding unusable destinations: Xiao Expires 19 May 2027 [Page 7] Internet-Draft Enhanced Dual Stack November 2026 +===============+=================+========================+ | Aspect | Happy Eyeballs | EDS | | | (HE) | | +===============+=================+========================+ | Approach | Race IPv6/IPv4 | Remember recent | | | connections; | failures; avoid | | | use the winner. | affected destinations. | +---------------+-----------------+------------------------+ | Beneficiaries | Applications | Applications using | | | implementing | EDS-enabled platform | | | HE. | destination selection. | +---------------+-----------------+------------------------+ | First IPv6 | Minimizes delay | May time out, as with | | failure | through racing. | current RFC 6724 | | | | behavior. | +---------------+-----------------+------------------------+ | Complexity | Requires | Requires shared | | | connection | failure state; no | | | racing. | racing. | +---------------+-----------------+------------------------+ Table 3 EDS does not depend on HE, and the two mechanisms can coexist. 3.2. Operational Diagnostics Avoiding repeated failures is only part of the EDS objective. Network administrators also need information about IPv6 connection- establishment failures so that the underlying problems can be corrected. The recent-failure records defined in [ADDR-SELECT] provide the primary diagnostic information used by EDS. An EDS-capable implementation SHOULD make these records available to authorized local administrators or management systems, subject to local policy and privacy controls. The records identify the applicable network context, IPv6 destination, IPv6 source prefix or address, transport protocol and port, failure type, and time of the observation. Recent-failure records can be emitted to a local logging or telemetry facility, such as syslog, and retained independently of the short- lived state used by destination selection. Expiration or clearing of the selection state does not require deletion of corresponding diagnostic records. Xiao Expires 19 May 2027 [Page 8] Internet-Draft Enhanced Dual Stack November 2026 EDS does not require a particular log format, storage model, aggregation method, or remote reporting protocol. Retention, filtering, aggregation, and export are matters of local policy. It is worth noting that, with the normal RFC 6724 policy, when both usable IPv6 and IPv4 destinations are available for selection, IPv6 is normally preferred. Therefore, when IPv4 is preferred, a recent- failure state record should normally exist to explain the reason. When IPv4 is used without such a record, the reason lies outside [ADDR-SELECT]. Network administrators should therefore investigate whether a usable IPv6 candidate was available to the destination- selection mechanism and, in particular, whether DNS resolution, host IPv6 configuration, or local address-selection policy prevented IPv6 from being preferred. The diagnostic information is intended to support a gradual improvement loop: observe IPv6 connection-establishment failures or cases where usable IPv6 candidates are unavailable, determine the cause, correct the underlying problem, and verify that IPv6 use increases over time. 4. Incremental EDS Deployment EDS enables IPv6 introduction to start with practical upfront validation and expand as operational confidence grows. A suggested approach is: 1. Start small: Divide hosts into IPv6-pioneer hosts and regular hosts. Pioneer hosts are EDS-capable; regular hosts can initially remain IPv4-only or unchanged. 2. Validate practically: Perform as much upfront IPv6 validation as practical, using [RFC7381] as guidance. 3. Enable IPv6: Enable IPv6 on pioneer hosts and the supporting network infrastructure. 4. Diagnose and fix: Use EDS failure records and diagnostics from pioneer hosts to identify and correct IPv6 problems. 5. Expand gradually: Enable IPv6, and EDS where appropriate, on more hosts, applications, services, and network environments as confidence grows; eventually progress toward IPv6-mostly or IPv6-only operation. Xiao Expires 19 May 2027 [Page 9] Internet-Draft Enhanced Dual Stack November 2026 Regular hosts need not all become EDS-capable before IPv6 is expanded. Operators can retain EDS-capable pioneer hosts in newly enabled environments to continue the observe, fix, and expand process. EDS reduces upfront deployment risk; it does not eliminate IPv6 validation or the need to repair underlying problems. 5. Limitations EDS reduces repeated user-visible disruption but does not guarantee that the first encounter with a previously unknown IPv6 problem will be invisible. With no applicable recent-failure state, RFC 6724 behaves normally and IPv6 can be preferred. If that first attempt fails, later selections can use the resulting state to avoid repeatedly preferring the same recently failing IPv6 context. EDS also does not repair the underlying IPv6 problem. Connection- informed selection protects users from repeated exposure, while operational diagnostics provide the information needed for administrators to locate and correct the problem. Recent-failure information can become stale. It therefore needs bounded lifetime and appropriate scoping, as specified in [ADDR-SELECT]. 6. Standardization Considerations EDS is an operational framework. The corresponding implementation method for RFC 6724 Rule 1 is intended to be specified in [ADDR-SELECT]. Operational diagnostic information can be exposed through existing local logging or telemetry facilities. Additional standardization can be developed where common reporting semantics or mechanisms are useful, but EDS does not depend on a particular reporting transport or management protocol. This document does not define a new application-facing API. Its purpose is to describe how connection-informed destination selection and operational diagnostics work together to support lower-risk, incremental IPv6 deployment. 7. Security Considerations The security considerations of [RFC6724] and [ADDR-SELECT] apply. Xiao Expires 19 May 2027 [Page 10] Internet-Draft Enhanced Dual Stack November 2026 Recent-failure state influences whether IPv6 or IPv4 is preferred. Incorrect or malicious creation of such state could therefore cause temporary preference for IPv4. Failure information used for selection SHOULD be derived from locally observed connection- establishment outcomes, and its lifetime SHOULD be bounded. Operational diagnostic information can contain sensitive information about network context, destination addresses, source addresses or prefixes, transport protocol and port, failure patterns, and timestamp. Access to this information MUST be controlled. Retention, export, and aggregation SHOULD follow local security and privacy policy and SHOULD expose no more information than is needed for the intended operational purpose. 8. IANA Considerations This document makes no request of IANA. 9. References 9.1. Normative References [ADDR-SELECT] Martin, F., Xiao, X., and B. E. Carpenter, "Updates to IPv6 Default Address Selection", Work in Progress, Internet-Draft, draft-martin-ipv6-addr-selection-updates- 00, 15 September 2026, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC6724] Thaler, D., Ed., Draves, R., Matsumoto, A., and T. Chown, "Default Address Selection for Internet Protocol Version 6 (IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . 9.2. Informative References Xiao Expires 19 May 2027 [Page 11] Internet-Draft Enhanced Dual Stack November 2026 [HE-REPORT] Martinez, J. P. and P. S. Tiesel, "Considerations for Happy Eyeballs Error Reporting", Work in Progress, Internet-Draft, draft-palet-happy-reporting- considerations-02, 15 November 2026, . [HEv3] Pauly, T., Schinazi, D., Jaju, N., and K. Ishibashi, "Happy Eyeballs Version 3: Better Connectivity Using Concurrency", Work in Progress, Internet-Draft, draft- ietf-happy-happyeyeballs-v3-05, 2 November 2026, . [RFC3484] Draves, R., "Default Address Selection for Internet Protocol version 6 (IPv6)", RFC 3484, DOI 10.17487/RFC3484, March 2003, . [RFC6555] Wing, D. and A. Yourtchenko, "Happy Eyeballs: Success with Dual-Stack Hosts", RFC 6555, DOI 10.17487/RFC6555, April 2012, . [RFC7381] Chittimaneni, K., Chown, T., Howard, L., Kuarsingh, V., Pouffary, Y., and E. Vyncke, "Enterprise IPv6 Deployment Guidelines", RFC 7381, DOI 10.17487/RFC7381, October 2014, . [RFC8305] Schinazi, D. and T. Pauly, "Happy Eyeballs Version 2: Better Connectivity Using Concurrency", RFC 8305, DOI 10.17487/RFC8305, December 2017, . [RFC9621] Pauly, T., Ed., Trammell, B., Ed., Brunstrom, A., Fairhurst, G., and C. S. Perkins, "Architecture and Requirements for Transport Services", RFC 9621, DOI 10.17487/RFC9621, January 2025, . [RFC9622] Trammell, B., Ed., Welzl, M., Ed., Enghardt, R., Fairhurst, G., Kühlewind, M., Perkins, C. S., Tiesel, P.S., and T. Pauly, "An Abstract Application Programming Interface (API) for Transport Services", RFC 9622, DOI 10.17487/RFC9622, January 2025, . Xiao Expires 19 May 2027 [Page 12] Internet-Draft Enhanced Dual Stack November 2026 Acknowledgements Brian Carpenter and Franck Martin contributed to the development of the connection-informed approach to RFC 6724 destination selection and helped refine the relationship between EDS and default IPv6/IPv4 selection. Comments from David Schinazi, Tim Chown, Philipp Tiesel, Tom Hill, Warren Kumari, Jen Linkova, Nick Buraglio, Mike Ackermann, and Gert Doering led to revisions and improvements of this draft. Author's Address Xipeng Xiao Huawei Technologies Dusseldorf Email: xipengxiao@gmail.com Xiao Expires 19 May 2027 [Page 13]