[ippm] Review request for draft-ietf-v6ops-ipv6-app-testing
Philipp Tiesel <[email protected]> Mon, 22 Jun 2026 15:06:21 +0200
| Newsgroups | gmane.ietf.ippm,gmane.ietf.bmwg,gmane.ietf.v6ops |
|---|---|
| Message-ID | <[email protected]> |
--===============7973733194311973109==
Content-Type: multipart/alternative;
boundary="Apple-Mail=_4D6701F7-BCE9-45BA-929D-9CB711A63367"
--Apple-Mail=_4D6701F7-BCE9-45BA-929D-9CB711A63367
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=us-ascii
Hi,
We are currently working on a new BCP about IPv6 application testing.
The document got adopted by v6ops last year and, based on the WGs feedback,
seams mature for WGLC soon.
The document in its current state is focused on providing framework for
testing functional aspects, while mostly ignoring performance aspects.
As suggested by Mohamed Boucadair, I would like to ask members of
the IPPM and BMWG to have a look and provide feedback whether
they see performance aspects that should be added to an IPv6 testing BCP.
Document details:
Title: Testing Applications' IPv6 Support
Authors: Philipp S. Tiesel
Jen Linkova
Kyle Ouellette
Ben Patton
Name: draft-ietf-v6ops-ipv6-app-testing-01.txt
Pages: 22
Dates: 2026-05-26
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 "IPv6-
only-strict" scenarios without any connectivity towards any relevant
IPv4 endpoint. 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.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-app-testing/
There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-v6ops-ipv6-app-testing-01.html
AVE!
Philipp S. Tiesel
--
Philipp S. Tiesel
https://philipp.tiesel.net/
--Apple-Mail=_4D6701F7-BCE9-45BA-929D-9CB711A63367
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" =
content=3D"text/html; charset=3Dus-ascii"></head><body =
style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;"><font face=3D"Menlo">Hi,<br><br>We are =
currently working on a new BCP about IPv6 application testing.<br>The =
document got adopted by v6ops last year and, based on </font><span =
style=3D"font-family: Menlo;">the WGs feedback,</span><div><span =
style=3D"font-family: Menlo;">seams mature for WGLC =
soon.</span><div><font face=3D"Menlo"><br>The document in its current =
state is focused on providing framework for</font></div><div><font =
face=3D"Menlo">testing functional aspects, while mostly ignoring =
performance aspects.</font></div><div><font face=3D"Menlo">As suggested =
by Mohamed Boucadair, I would like to ask members =
of</font></div><div><font face=3D"Menlo">the IPPM and BMWG to have a =
look and provide feedback whether</font></div><div><font =
face=3D"Menlo">they see performance aspects that should be added to =
an IPv6 testing BCP.<br><br>Document details:<br><br> Title: =
Testing Applications' IPv6 Support<br> Authors: =
Philipp S. =
Tiesel<br> &nbs=
p;Jen =
Linkova<br> &nb=
sp;Kyle =
Ouellette<br> &=
nbsp;Ben Patton<br> Name: =
draft-ietf-v6ops-ipv6-app-testing-01.txt<br> =
Pages: 22<br> Dates: =
2026-05-26<br><br>Abstract:<br><br> This document =
provides guidance for application developers and<br> software =
as a service providers on how to approach IPv6 testing =
in<br> Dual-stack (IPv4+IPv6), and IPv6-only scenarios, =
including "IPv6-<br> only-strict" scenarios without any =
connectivity towards any relevant<br> IPv4 endpoint. It =
discusses common misconceptions about the degree<br> to which =
operating systems and libraries can abstract IPv6 =
issues<br> away and explains common regressions to avoid when =
deploying IPv6<br> support.<br><br>The IETF datatracker =
status page for this Internet-Draft =
is:<br>https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-app-testing/=
<br><br>There is also an HTML version available =
at:<br>https://www.ietf.org/archive/id/draft-ietf-v6ops-ipv6-app-testing-0=
1.html<br><br></font><div>
<font face=3D"Menlo">AVE!<br> Philipp S. =
Tiesel<br><br>-- <br>Philipp S. =
Tiesel <br>https://philipp.tiesel.net/</font><br>
</div></div></div></body></html>=
--Apple-Mail=_4D6701F7-BCE9-45BA-929D-9CB711A63367--
--===============7973733194311973109==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaXBwbSBtYWls
aW5nIGxpc3QgLS0gaXBwbUBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv
IGlwcG0tbGVhdmVAaWV0Zi5vcmcK
--===============7973733194311973109==--