Testing Applications' IPv6 Support
draft-tiesel-v6ops-ipv6-app-testing-01
| Document | Type |
Replaced Internet-Draft
(v6ops WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Philipp S. Tiesel , Jen Linkova , Kyle Ouellette , Ben Patton | ||
| Last updated | 2025-12-05 (Latest revision 2025-10-17) | ||
| Replaced by | draft-ietf-v6ops-ipv6-app-testing | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-v6ops-ipv6-app-testing | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document provides guidance for application developers and software as a service providers on how to approach IPv6 testing in Dual-Stack (IPv4+IPv6), and IPv6-only scenarios, including "true IPv6-only" scenarios. It discusses common misconceptions about the degree to which operating systems and libraries can abstract IPv6 issues away and explains common regressions to avoid when deploying IPv6 support.
Authors
Philipp S. Tiesel
Jen Linkova
Kyle Ouellette
Ben Patton
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)