<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-v6ops-ipv6-app-testing" target="https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-ipv6-app-testing-00">
   <front>
      <title>Testing Applications&#x27; IPv6 Support</title>
      <author initials="P. S." surname="Tiesel" fullname="Philipp S. Tiesel">
         <organization>SAP SE</organization>
      </author>
      <author initials="J." surname="Linkova" fullname="Jen Linkova">
         <organization>Google</organization>
      </author>
      <author initials="K." surname="Ouellette" fullname="Kyle Ouellette">
         <organization>University of New Hampshire Interoperability Labs</organization>
      </author>
      <author initials="B." surname="Patton" fullname="Ben Patton">
         <organization>University of New Hampshire Interoperability Labs</organization>
      </author>
      <date month="December" day="16" year="2025" />
      <abstract>
	 <t>   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 &quot;true
   IPv6-only&quot; 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-v6ops-ipv6-app-testing-00" />
   
</reference>
