<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.12) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-v6ops-ipv6-app-testing-10" category="bcp" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.35.0 -->
  <front>
    <title abbrev="ipv6-app-testing">Recommendations for IPv6 Testing of Applications</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-v6ops-ipv6-app-testing-10"/>
    <author fullname="Philipp S. Tiesel">
      <organization>SAP SE</organization>
      <address>
        <email>philipp@tiesel.net</email>
        <email>philipp.tiesel@sap.com</email>
      </address>
    </author>
    <author fullname="Kyle Ouellette">
      <organization abbrev="UNH-IOL">University of New Hampshire Interoperability Labs</organization>
      <address>
        <email>kouellette@iol.unh.edu</email>
      </address>
    </author>
    <author fullname="Ben Patton">
      <organization abbrev="UNH-IOL">University of New Hampshire Interoperability Labs</organization>
      <address>
        <email>bpatton@iol.unh.edu</email>
      </address>
    </author>
    <date year="2026" month="November" day="16"/>
    <area>Operations and Management</area>
    <workgroup>v6ops</workgroup>
    <keyword>Interoperability</keyword>
    <keyword>Deployment</keyword>
    <keyword>Operation</keyword>
    <keyword>IPv6 Failure</keyword>
    <keyword>IPv6 service</keyword>
    <keyword>Validation</keyword>
    <keyword>Application developer</keyword>
    <abstract>
      <?line 103?>

<t>This document provides guidance for application developers and Software-as-a-Service (SaaS) 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.</t>
      <t>The document also 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>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-app-testing/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/ietf-wg-v6ops/draft-itef-v6ops-ipv6-app-testing"/>.</t>
    </note>
  </front>
  <middle>
    <?line 111?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>For the last 20 years, enabling applications for IPv6 has focused on coexistence with IPv4 and allowing traffic to shift towards IPv6 without breaking IPv4 operation.
This target has changed in part due to a series of national regulations mandating state entities to proceed in the transition to IPv6, e.g., in
China <xref target="CN-CAC-2023"/>, the United States of America <xref target="US-OMB-M-21-07"/>, Germany <xref target="DE-BIT-2020-14"/>, and the Czech Republic <xref target="CZ-ENDv4"/>.
IPv6 support thus means being fully functional in the absence of IPv4 and transition technologies providing connectivity to the IPv4 Internet.
Therefore, applications are expected to function regardless of whether they are used in an IPv4-only environment, a Dual-stack environment, or an IPv6-only environment, with or without connectivity to the IPv4 Internet. To achieve this, applications need to be verified against all these scenarios.</t>
      <t>The availability of IPv6 support in applications, from small command-line tools to huge cloud-based distributed applications like Enterprise Resource Planning (ERP) systems, has a considerable impact on the success of IPv6 deployment.
While the IETF does not define compliance tests, best current practices exist for the behavior of general IPv6 nodes <xref target="RFC8504"/> and Customer Edge (CE) routers <xref target="RFC7084bis"/>, as well as for test SIP-based applications <xref target="RFC5118"/>.
However, at the time of writing this document, there exists no documented best current practices on how to test whether applications are ready for Dual-stack and IPv6-only environments.</t>
      <t>To fill that gap, this document provides guidance for application developers and cloud application providers on how to approach IPv6 testing.
It describes the parts of an application lifecycle to include, which communication scenarios they should consider validating against, and which common regressions to avoid when adding IPv6 support.
While many application developers assume that the network abstractions of an OS, communication libraries, application frameworks, or embedded platforms will handle the transition towards IPv6 transparently, leaky abstractions within these frameworks will make it difficult for an application developer to write address family-independent code for features such as allow/deny lists, tracing, and logging.</t>
      <t>Testing cloud applications poses an additional challenge, as these are typically composed of hundreds to thousands of micro and macroservices, forming a complex distributed system that requires intricate communication and orchestration infrastructure to operate.
Enabling these applications to communicate over IPv6 requires careful analysis of data flows towards services, between components, and towards external services as well as analysis where IPv6 addresses may occur as metadata.</t>
      <t>As the scope of applications to be guided by this document ranges from small command-line tools to huge cloud-based systems,
not all details discussed here are relevant for all applications.
However, the underlying idea of how to approach IPv6 application testing is the same for all of these:
Don't invent new tests for IPv6, but instead test whether the functional correctness is given irrespective of the address family used for communication. In cases where IP addresses are processed as data, make sure to update the tests to support IPv4 and IPv6 addressees.</t>
      <t>The remainder of this document is organized as follows:
<xref target="definitions"/> contains the base definitions and scenarios used throughout the document.
<xref target="objectives"/> provides guidance on testing objectives and dimensions that should be considered in an IPv6 testing campaign.
<xref target="strategies"/> presents practical testing strategies for setting up the scenarios defined in <xref target="objectives"/> without building all scenarios within a lab environment.
<xref target="failures"/> describes common sources of IPv6-related failures and misbehavior that application developers and testers should be aware of.
Finally, <xref target="ops"/> describes operational considerations to keep in mind while designing end-to-end tests.</t>
    </section>
    <section anchor="definitions">
      <name>Conventions and Definitions</name>
      <section anchor="requirements-language">
        <name>Requirements Language</name>
        <t>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 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.
<?line -6?>
        </t>
      </section>
      <section anchor="base-connectivity-scenarios">
        <name>Base Connectivity Scenarios</name>
        <t>This document defines the following four "base connectivity scenarios"
in which applications ought to be verified for availability and functional correctness:</t>
        <t><cref anchor="_1"><strong>Note to the RFC-Editor:</strong> The capitalization of the following terms should be consistent with <xref target="IPv6-ONLY"/>.</cref></t>
        <dl>
          <dt>IPv4-only:</dt>
          <dd>
            <t>A node or application that has native connectivity towards all endpoints relevant for the test scenario using IPv4 and no connectivity towards any relevant IPv6 endpoints.</t>
          </dd>
          <dt/>
          <dd>
            <t>While this definition is narrower than the one from <xref target="IPv6-ONLY"/>, and mirrors the <em>IPv6-only-strict</em> scenario, it refrains from calling it <em>IPv4-only-strict</em> for the sake of simplicity as transition technologies allowing IPv4-only endpoints to talk to arbitrary IPv6-only endpoints are not widely deployed and encapsulation cases mentioned in <xref target="IPv6-ONLY"/> are covered by the either the <em>Dual-stack</em> or <em>IPv6-only with NAT64</em> case.</t>
          </dd>
          <dt>Dual-stack:</dt>
          <dd>
            <t>A node or application that has native connectivity towards all endpoints relevant for the test scenario using IPv4 as well as using IPv6.</t>
          </dd>
          <dt/>
          <dd>
            <t>This case covers the <em>Dual-Stack</em> and <em>IPv6-Mostly (for clients not supporting Option 108 <xref target="RFC8925"/>)</em> cases in <xref target="IPv6-ONLY"/> and
narrows it down by defining the scope to test-relevant endpoints.</t>
          </dd>
          <dt>IPv6-only with NAT64:</dt>
          <dd>
            <t>A node or application that has native connectivity towards all endpoints relevant for the test scenario using IPv6 and connectivity towards IPv4 endpoints using a transition technology like NAT64, e.g., NAT64 in combination with CLAT <xref target="RFC6877"/>, DNS64 <xref target="RFC6147"/>, or local address synthesis. This document does not differentiate between stateful <xref target="RFC6146-bis"/> and stateless <xref target="RFC7915"/> NAT64 variants.</t>
          </dd>
          <dt/>
          <dd>
            <t>This case covers the <em>IPv6-Only</em> as well as <em>IPv6-Mostly (for clients supporting Option 108 <xref target="RFC8925"/>)</em> cases in <xref target="IPv6-ONLY"/> and
narrows them down by defining the scope to test-relevant endpoints.</t>
          </dd>
          <dt>IPv6-only-strict:</dt>
          <dd>
            <t>A node or application that has native IPv6 connectivity towards all endpoints relevant for the test scenario and no connectivity towards any relevant IPv4 endpoints, neither encapsulated nor translated.</t>
          </dd>
          <dt/>
          <dd>
            <t>This definition narrows down the <em>IPv6-Only-Strict</em> definition from <xref target="IPv6-ONLY"/> by defining the scope to test-relevant endpoints.</t>
          </dd>
        </dl>
      </section>
      <section anchor="lifecycle-functions">
        <name>Lifecycle Functions</name>
        <t>Orthogonal to the base scenarios, this document defines lifecycle functions (i.e., the phases in which an application is approached during a simplified lifecycle of the application) in accordance to <xref target="US-NIST.SP.500-267Ar1"/> as follows:</t>
        <ul spacing="normal">
          <li>
            <t>Installation: The installation of the application including any initial configuration required for
getting the application in a state where remote services are operational.</t>
          </li>
          <li>
            <t>User Interface: All forms of interactive access to the application (e.g., Web User Interface (UI) or API).</t>
          </li>
          <li>
            <t>Management: All forms of remote management and monitoring functions.</t>
          </li>
          <li>
            <t>Update: All forms of update functions, including both automatic and manual update mechanisms.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="objectives">
      <name>Testing Objectives</name>
      <t>As a basic principle, IPv6 application testing should always be derived from functional and integration testing.
Therefore, the goal is to verify that the expected behavior is consistent across all connectivity scenarios,
i.e., the application functions correctly in IPv4-only, Dual-stack, IPv6-only with NAT64, and IPv6-only-strict settings.</t>
      <t>This section provides guidance on which connectivity scenarios and parts of the lifecycle of an application to include in a testing campaign
for an ideal application that is supposed to run anywhere.
It is RECOMMENDED to apply these scenarios to all existing functional, integration, and end-to-end test cases that the application's communication pattern may influence.
The document also explains how to approach testing of complex cloud applications and how to exclude connectivity scenarios based on the deployment environment.
Testing for application-specific or protocol-specific issues is out of scope.
While this section assumes that the communication scenarios are under full control of the tester,
<xref target="strategies"/> explains how to conduct tests in cases where control over the test environment is limited.</t>
      <section anchor="scenarios">
        <name>Connectivity Scenarios</name>
        <t><xref target="scn_combinations"/> lists the combinations of connectivity scenarios that should be considered when testing the application for IPv6 issues.
Not testing some of these cases may lead to failures in operations.
Note, while the involved parties are listed here as "client" and "server" to reflect the most common case, the combinations can be used the same way when considering Peer-to-Peer (P2P) applications -- with "client" representing the initiating or first acting party.</t>
        <t>The first five scenarios marked as <em>base</em> should cover all major code paths and fallback conditions and MUST be validated to work as expected unless the application's architecture or deployment makes them irrelevant (see <xref target="complex-apps"/> for further discussion).
These include Dual-stack clients combined with IPv4-only and IPv6-only-strict servers, to test whether the additional address family confused the client.
The document also includes the cases with Dual-stack server and both IPv4-only and IPv6-only clients, to test whether a single address family at client side works as anticipated and look at the transition case using NAT64.</t>
        <t>This document does not include any special scenarios for 464XLAT <xref target="RFC6877"/> and IPv6-Mostly <xref target="V6MOPS"/>, as these architectures are from the client side indistinguishable from the Dual-stack or IPv6-only with NAT64 (IPv6-Mostly without CLAT).</t>
        <t>MTU issues, as described in <xref section="7.4.5" sectionFormat="of" target="V6MOPS"/>, that may arise form these scenarios are covered in <xref target="partially-broken"/>.</t>
        <t>This document also do not separate IPv4-only cases with and without NAT, despite that applications exist that assume NAT for IPv4 and do not work without, as these issues are also revealed by the IPv6 scenarios.</t>
        <t>For the IPv6-only data center case, where servers may be exposed to the IPv4-only Internet using NAT46, the case marked as IPv6-only-DC in <xref target="scn_combinations"/> SHOULD also be considered. This case MAY be omitted for deployments targeting IPv6-only clients.</t>
        <t>The other combinations are unlikely to exhibit additional problems for 'client/server'-based applications and, therefore, are marked as extended in <xref target="scn_combinations"/>.</t>
        <t>For P2P applications and applications with complex connection handling like using Session Traversal Utilities for NAT (STUN) <xref target="RFC8489"/> or Traversal Using Relays around NAT (TURN) <xref target="RFC8656"/>, skipping these scenarios is strongly discouraged.</t>
        <table anchor="scn_combinations">
          <name>Connectivity scenario combinations to consider</name>
          <thead>
            <tr>
              <th align="left">Client</th>
              <th align="left">Server</th>
              <th align="center">Classification</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Dual-stack</td>
              <td align="left">IPv4-only</td>
              <td align="center">base</td>
            </tr>
            <tr>
              <td align="left">Dual-stack</td>
              <td align="left">IPv6-only-strict</td>
              <td align="center">base</td>
            </tr>
            <tr>
              <td align="left">IPv4-only</td>
              <td align="left">Dual-stack</td>
              <td align="center">base</td>
            </tr>
            <tr>
              <td align="left">IPv6-only with NAT64</td>
              <td align="left">IPv4-only</td>
              <td align="center">base</td>
            </tr>
            <tr>
              <td align="left">IPv6-only-strict</td>
              <td align="left">Dual-stack</td>
              <td align="center">base</td>
            </tr>
            <tr>
              <td align="left">IPv4-only</td>
              <td align="left">IPv6-only with NAT64</td>
              <td align="center">IPv6-only-DC</td>
            </tr>
            <tr>
              <td align="left">Dual-stack</td>
              <td align="left">Dual-stack</td>
              <td align="center">extended</td>
            </tr>
            <tr>
              <td align="left">IPv4-only</td>
              <td align="left">IPv4-only</td>
              <td align="center">extended</td>
            </tr>
            <tr>
              <td align="left">IPv6-only with NAT64</td>
              <td align="left">IPv6-only-strict</td>
              <td align="center">extended</td>
            </tr>
            <tr>
              <td align="left">IPv6-only-strict</td>
              <td align="left">IPv6-only-strict</td>
              <td align="center">extended</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="intermediaries">
        <name>Testing with Intermediaries (e.g., Proxies)</name>
        <t>Many application protocols support communicating across intermediates, most commonly HTTP Connect <xref target="RFC7230"/>,  SOCKS <xref target="RFC1928"/>, or MASQUE <xref target="MASQUE"/> proxies.
P2P applications often support TURN <xref target="RFC8656"/> as an intermediary to traverse NAT and provide connectivity between IPv4-only and IPv6-only hosts.
When testing connectivity scenarios for such an application, the additional test cases including a proxy MUST also be validated.</t>
        <t>As a proxy can convert between address families, all combinations shown in <xref target="scn_proxy"/>,
consisting of base scenarios towards the proxy and (assuming the same scenarios on both sides of the proxy) the respective base scenarios from the proxy to the server, should be considered for testing.</t>
        <table anchor="scn_proxy">
          <name>Base scenario combinations including a proxy to consider for IPv6 testing</name>
          <thead>
            <tr>
              <th align="left">Client</th>
              <th align="left">Proxy</th>
              <th align="left">Server</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">Dual-stack</td>
              <td align="left">IPv4-only</td>
              <td align="left">Dual-stack</td>
            </tr>
            <tr>
              <td align="left">Dual-stack</td>
              <td align="left">IPv6-only-strict</td>
              <td align="left">Dual-stack</td>
            </tr>
            <tr>
              <td align="left">IPv4-only</td>
              <td align="left">Dual-stack</td>
              <td align="left">IPv4-only</td>
            </tr>
            <tr>
              <td align="left">IPv4-only</td>
              <td align="left">Dual-stack</td>
              <td align="left">IPv6-only-strict</td>
            </tr>
            <tr>
              <td align="left">IPv6-only with NAT64</td>
              <td align="left">IPv4-only</td>
              <td align="left">Dual-stack</td>
            </tr>
            <tr>
              <td align="left">IPv6-only-strict</td>
              <td align="left">Dual-stack</td>
              <td align="left">IPv4-only</td>
            </tr>
            <tr>
              <td align="left">IPv6-only-strict</td>
              <td align="left">Dual-stack</td>
              <td align="left">IPv6-only-strict</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="testing-name-resolution-issues">
        <name>Testing Name Resolution Issues</name>
        <t>As most applications use name resolution to bootstrap their connectivity,
it is necessary to consider name resolution aspects when testing IPv6 readiness.
While some name resolution issues only manifest in certain connectivity scenarios or can be mitigated by using Happy Eyeballs <xref target="RFC8305"/>,
others will just map to different connectivity scenarios.</t>
        <t>This section lists name resolution issues to consider for testing.</t>
        <section anchor="missing-dns-records">
          <name>Missing DNS Records</name>
          <t>While a server endpoint is intended to support Dual-stack connectivity,
A or AAAA DNS resource records for the endpoint may be missing (e.g., due to misconfiguration or broken tooling)
or does not reach the client endpoint (e.g., because it got filtered out by a middlebox or local resolver).
The same can happen for names discovered and resolved through mDNS <xref target="RFC6762"/>, for example.</t>
          <t>While deployment and integration testing should try to test for this kind of broken connectivity,
this scenario is usually indistinguishable from an IPv4-only or an IPv6-only server endpoint,
and, therefore, already addressed by testing the base scenarios above.</t>
        </section>
        <section anchor="incorrect-dns-resource-records">
          <name>Incorrect DNS Resource Records</name>
          <t>Independent of the deployed server endpoint,
there may be an A and AAAA resource record pointing somewhere else,
e.g., to an old or planned deployment.</t>
          <t>For either IPv4-only or IPv6-only-strict clients, this scenario should always fail.</t>
          <t>For Dual-stack clients, it MUST be tested whether they can use the working IPv4-only or IPv6-only connectivity scenario, either by using Happy Eyeballs <xref target="RFC8305"/> or trying the next resolved address candidate after timeout.
Especially for the latter, it is advisable to verify whether the connection delay is acceptable for the desired use case.</t>
          <t>IPv6-only clients with NAT64 are only expected to work with broken AAAA records when deployed with
CLAT (should behave like Dual-stack as discussed in <xref target="scenarios"/>) or
local NAT64 address (e.g., as when implementing Happy Eyeballs v2 <xref target="RFC8305"/>).
IPv6-only clients with NAT64 that rely on DNS64 only are expected to fail as the presence of AAAA records prevents synthesis of DNS64 records.</t>
          <t>Testing with IPv4-Mapped IPv6 addresses <xref target="RFC4291"/> in AAAA resource records is also RECOMMENDED.
While this makes zero sense, it has been seen in the wild and should not confuse the client.</t>
        </section>
        <section anchor="dns-delegation-issues">
          <name>DNS Delegation Issues</name>
          <t>Integration testing for cloud applications MUST verify that the necessary domain names are resolvable from IPv4-only or IPv6-only-strict DNS resolvers.
<xref target="RFC10001"/> describes common misconfigurations breaking IPv4-only or IPv6-only-strict in detail and provides guidance how to avoid these.
Applications providing endpoints SHOULD test against these misconfigurations.</t>
        </section>
        <section anchor="testing-with-ip-literals">
          <name>Testing with IP Literals</name>
          <t>Most name resolution libraries support IP literals, i.e., textual representations of IP addresses.
Applications SHOULD be tested to determine whether they work as expected with IPv4 literals and all IPv6 address representations described in <xref target="RFC4291"/>. Some applications (client or server) may not allow for IPv4 literals.</t>
          <t>If there is a use case for link-local communication using IP literals, it MUST be tested whether the zone identifier can be entered as described in <xref target="RFC9844"/> and work as expected.</t>
        </section>
        <section anchor="testing-reverse-dns-lookups">
          <name>Testing Reverse DNS Lookups</name>
          <t>Applications SHOULD be tested whether they correctly resolve and display reverse DNS lookups for all address families and deal correctly with missing DNS records if reverse DNS is used anywhere in the code or runtime environment.</t>
        </section>
        <section anchor="testing-with-link-local-names">
          <name>Testing with Link-local Names</name>
          <t>A name such as <tt>example.local</tt> can resolve, e.g., through DNS-Based Service Discovery <xref target="RFC6763"/>,
to one or both of a link-local IPv4 address <xref target="RFC3927"/> and a link-local IPv6 address.
The latter is incomplete and possibly ambiguous unless associated with the relevant zone identifier or zone index <xref target="RFC4007"/>.
Applications SHOULD be tested to determine whether they work as expected with link-local names, particularly on a host with multiple network interfaces.</t>
        </section>
      </section>
      <section anchor="testing-with-different-transports">
        <name>Testing with Different Transports</name>
        <t>Some applications can employ different transports or protocol variants for their communication flows.
Typical examples include HTTP-based applications running over TCP or QUIC <xref target="RFC9114"/> (over UDP) and SIP-based applications that can do signaling over UDP, TCP, and SCTP.
While Transport Layer Security (TLS) or similar security layers are used for most application flows today, they may be optional from an application protocol's point of view.
IPv6-related issues that only arise with certain transports or protocol variants are usually hard to identify and debug in production. Because TCP transport is usually implemented in the OS, while UDP/QUIC transport is usually implemented in the application or a library shipped with it, diverging behaviors and failures in IP-family-specific corner cases are more likely.
Therefore, an IP connectivity testing strategy MUST also exercise all transport and protocol variants supported by the application and that might be available at the endpoints.
Testers have to assess whether these test cases use the expected transport protocol (or variant) or fall back to a less preferable transport under specific forwarding conditions.</t>
      </section>
      <section anchor="partially-broken">
        <name>Testing with Partially Broken Connectivity, MTU, and Fragmentation Issues</name>
        <t>When multiple address families are available, IP packets may traverse different forwarding paths depending on the address family.
Even when the same forwarding path is traversed, the path can exhibit distinct forwarding behaviors, especially in the presence of middleboxes, including:</t>
        <ul spacing="normal">
          <li>
            <t>Dropping all packets</t>
          </li>
          <li>
            <t>Dropping particular packets, e.g., TCP vs. UDP packets, packets destined to different port numbers</t>
          </li>
          <li>
            <t>Preventing the use of QUIC, specific port numbers, or encapsulation schemes</t>
          </li>
          <li>
            <t>Behaving differently for the same values of ECN or DSCP fields</t>
          </li>
          <li>
            <t>Exhibiting a different Path Maximum Transmission Unit (PMTU)</t>
          </li>
          <li>
            <t>Dropping some ICMP messages and breaking PMTU discovery</t>
          </li>
          <li>
            <t>Dropping fragmented packets</t>
          </li>
          <li>
            <t>Blocking certain protocol features, e.g., certain extensions or ciphers in TLS handshake</t>
          </li>
        </ul>
        <t>In such scenarios, clients restricted to a single address family -- such as IPv6-only-strict clients -- may experience complete loss of connectivity,
while dual-stack clients often mask such failures by automatically falling back to another address family.
Disabling either address family may therefore break a scenario that seems to function correctly at first glance.
Testing applications against these scenarios can become a key enabler for users' acceptance of IPv6,
especially during a transition phase where partially broken connectivity is expected more frequently.</t>
        <t>While this document provides no comprehensive guide on how to test for these network issues,
it is  REQUIRED to check applications with dual-stack servers for partial blackholing and MTU issues by testing with IPv4-only and IPv6-only-strict clients during deployment and integration testing.
Note that in some cases, connectivity issues may only become apparent late in the communication process, for example, after a successful TCP handshake / QUIC initial packet, but before a TLS handshake succeeds.
Because these issues can occur outside the testers' control, it is advisable to simulate them and ensure the application's behavior supports detecting and analyzing these errors.</t>
      </section>
      <section anchor="testing-without-ipv4-loopback-addresses-1270008">
        <name>Testing without IPv4 Loopback Addresses (127.0.0.0/8)</name>
        <t>Some applications and services may assume the existence and reachability of the IPv4 loopback addresses (127.0.0.0/8) when binding to a socket or for communicating with other services on the same host.
For example, a web server may explicitly listen on a 127.0.0.0/8 by default.
For IPv6-only-strict scenarios, system administrators may choose to disable IPv4, including loopback.
In such cases, applications may fail to operate correctly. Applications expecting to bind to an IPv4 loopback address may fail to start when these addresses are unavailable due to a bind failure.
Applications expecting these addresses to be available for inter-service communication will result in these services being unable to communicate properly.</t>
        <t>Because of this, when testing applications for the IPv6-only-strict scenario, it is RECOMMENDED to test the application in an environment without IPv4 on the loopback interface.</t>
      </section>
      <section anchor="lifecycle-considerations">
        <name>Testing Lifecycle Function Considerations</name>
        <t>To cover the whole lifecycle of an application including installation, user interface,
management, and update, it is recommended to test that the lifecycle functions defined in <xref target="lifecycle-functions"/> are operational within the connectivity scenarios defined in <xref target="scn_combinations"/>.
Testing the normal operations of the application is encompassed by the user interface lifecycle function.</t>
        <t>In particular, the following MUST be considered:</t>
        <ul spacing="normal">
          <li>
            <t>Installation: Installation may require communications with remote first-party services (e.g., activation/license server)
or remote third-party services (e.g., package repositories). In these scenarios, the installer acts as
the client, and the remote service acts as the server. In cases of remote third-party services, testing
all server scenarios in <xref target="scn_combinations"/> may not be feasible, and impact the client scenarios that
can be supported. For example, if a third-party service is IPv4-only, testing an IPv6-only-strict scenario will fail.</t>
          </li>
          <li>
            <t>User Interface: User interfaces can be incredibly complex with numerous contexts, views, API endpoints,
CLI commands, etc. When testing an application's user interface(s), the normal operations of the application should be verified.
Additionally, when testing non-web-based user interfaces, it is recommended to test components
of the interface that involve communications with remote services, and those that handle network configuration parameters.
For example, a network configuration interface may only accept IPv4 address literals for certain parameters.
For testing web-based user interfaces, see <xref target="web-app-considerations"/>.</t>
          </li>
          <li>
            <t>Management: Depending on the application, management functions may be provided via the user interface.
However, the application may have additional management functions (Network Configuration Protocol (NETCONF) <xref target="RFC6124"/>, RESTCONF <xref target="RFC8040"/>, SNMP <xref target="STD62"/>, Open Telemetry <xref target="RFC9232"/>, syslog <xref target="RFC5424"/>, etc.) that should be tested.
As the source triggering application behavior is crucial for logging and auditing functionality,
addresses recorded need to be verified to be represented correctly. See <xref target="addr-as-data"/> about representation of addresses.</t>
          </li>
          <li>
            <t>Update: Depending on the application, update functions may be exercised during installation. However, the application
may have additional update functions (e.g., automatic updates or manual update mechanisms) that should be tested.</t>
          </li>
        </ul>
      </section>
      <section anchor="complex-apps">
        <name>Testing Complex Cloud Applications and Applying Test Cases</name>
        <t>Complex applications and especially cloud applications typically involve many data flows into the application, across components, and towards external services.
In such a system, an application or component may be considered as a server for some communication flows,
while being a client in others.
Therefore, test cases need to cover each data flow in all relevant scenarios.</t>
        <t>As functional and integration tests are often defined as end-to-end test cases,
they often involve several components, e.g., micro-services, load-balancers, application gateways, logging, authentication, and authorization services, which use IP-based protocols between the components.
Therefore, an end-to-end test case breaks down to a series of flows between components, and for each of these flows,
it MUST be determine whether it is necessary to apply the connectivity scenarios from <xref target="scn_combinations"/> to it,
or whether the connectivity scenarios are only controlled by the deployment of the application.</t>
        <t>For external flows (i.e., flows outside the application developers' control), all base scenarios from <xref target="scenarios"/> MUST be accounted for.</t>
        <t>If one side of the flow is under administrative control, the number of scenario combinations can still be limited:
For example, a cloud software provider choosing to deploy Dual-stack endpoints can skip all non-Dual-stack cases on the respective side of the communication.
For internal flows, the relevant scenarios only depend on the applications' architecture, and only scenarios planned in the deployment need to be considered.
From a networking perspective, flows between components are typically independent, as long as endpoints are not signaled inside of the protocol.
There is no need to run the Cartesian product of scenarios x communications as long as all relevant scenarios for a given flow are tested.</t>
        <t>In addition to the data flows, an implementation may include metadata about the data flow when communicating with backend systems, e.g., for logging or authorization purposes.
While the flows towards these backend systems themselves may be safe to ignore as outlined above,
the functional correctness of the backend systems for all kinds of IP address MUST be verified as part of the test series.
Ignoring IP addresses as data in the testing may result in malfunctions, like always denying access over IPv6, or security issues, like not logging access from IPv6 clients.</t>
      </section>
      <section anchor="web-app-considerations">
        <name>Special Considerations for Web-based Applications</name>
        <t>Web-based applications usually load resources from multiple parties, including Content Delivery Networks (CDNs) and analytic tools, involving data flows to all these parties.
When facing the requirement to support IPv6-only-strict users, being unable to load some resources due to missing/defective IPv6 support at the respective parties can have effects from missing analytics insights or ad revenue to severe functional defects rendering the application unusable.</t>
        <t>When testing such applications, it is not sufficient to only focus on the initial/main interactions,
but it is REQUIRED to consider all resources and parties providing them.
As Web browsers load these resources dynamically and third-party resources may themselves may request resources from more parties, this kind of testing usually requires an instrumented Web browser,
e.g., using <xref target="Selenium"/>.</t>
      </section>
      <section anchor="addr-as-data">
        <name>Considerations for Addresses as Data</name>
        <t>When applications process IP addresses as data (e.g., as part of logging or management functionality),
this functionality MUST work for all possible address families and representations.</t>
        <t>One challenge to consider is that the textual representation of IPv4 and IPv6 addresses are not canonical. Although <xref target="RFC5952"/> recommends a canonical format, all implementations MUST accept and be able to handle any legitimate <xref target="RFC4291"/> address format.
It allows several valid textual representations for the same address, which makes direct string comparison and arithmetic operations on addresses error-prone and slow.
For example, the IPv6 address <tt>2001:db8::1</tt> can be written as <tt>2001:db8:0:0:0:0:0:1</tt>, <tt>2001:0db8::0.0.0.1</tt>, or in several other forms.</t>
        <t>While custom logic to check, parse and process addresses is often error-prone and should be validated thoroughly,
modern environments and frameworks usually provide data structures that encapsulate the canonical binary representation and include methods for parsing the various textual representations, comparing addresses, performing subnet operations, and rendering addresses in a consistent format.</t>
        <t>For situations where textual representation of IPv6 addresses is needed -- such as in user interfaces, logging output, and text-based data formats like JSON, YAML, TOML, and XML -- <xref target="RFC5952"/> provides recommendations on which of the valid textual representations should be used.
Applications MUST be tested whether they follow <xref target="RFC5952"/> when rendering IPv6 addresses in textual form,
as required by national regulations like <xref target="US-NIST.SP.500-267Ar1"/>,
while accepting all valid representations defined in <xref target="RFC4291"/>.</t>
      </section>
    </section>
    <section anchor="strategies">
      <name>Testing Strategies</name>
      <t>Naive IPv6 testing, based on end-to-end functional tests as outlined in <xref target="objectives"/>, would require running a set of functional tests in various connectivity scenarios.
In certain environments, setting up test cases for all scenarios can become forbiddingly expensive,
especially for complex cloud applications, application platforms, or when dealing with corporate IT environments.</t>
      <t>This section gives recommendations how to set up scenarios defined in <xref target="scenarios"/> and
present strategies to meet the relevant testing objective by modifying Dual-stack clients and servers to conclude the results for other scenario combinations (e.g., by tracing whether the right address family is used).</t>
      <section anchor="ipv6-only-strict-clients">
        <name>IPv6-only-strict Clients</name>
        <t>This is the most natural way to test whether IPv6-only-strict clients behave correctly.</t>
        <t>The client device is either placed in a network without IPv4 connectivity or the IPv4 stack is disabled on the device while it is in a Dual-stack network.
While most desktop OSes allow disabling IPv4, mobile OSes, such as Android and iOS, do not.
For mobiles OSes, an IPv6-only-strict environment is needed.</t>
        <t>In both cases, it has to be ensured that there is no way to access IPv4-only resources.
In particular, fallback to NAT64 must be prevented by disabling CLAT <xref target="CLAT"/>,
making sure DNS resolution does not perform DNS64 address synthesis <xref target="RFC6147"/>
and blocking the Well-known Prefix (WKP) <xref target="RFC6052"/> for these clients.
In addition, VPN services including privacy services like <xref target="iCloud-Private-Relay"/> need to be disabled as they can provide connectivity towards the IPv4 Internet.</t>
        <t>A note on the applicability of disabling IPv4:
Before disabling IPv4 make sure the environment supports IPv6-only operation.
Many desktop virtualization environments become unusable because IPv4 is needed to access and manage the virtual machines.
Some corporate environments may render the machines unusable as they require IPv4 connectivity for sign-on.</t>
      </section>
      <section anchor="ipv6-only-servers">
        <name>IPv6-only Servers</name>
        <t>IPv6-only servers are a good option when setting up an IPv6-only-strict client environment is infeasible and
it is clear that clients only contact a single server or a small number of servers under the testers' control.
Even if setting up an IPv6-only-strict server environment is infeasible,
most testing is also achievable by setting up a dedicated DNS name only containing an AAAA resource record pointing to the IPv6 addresses of an otherwise Dual-stack server.</t>
      </section>
      <section anchor="client-based-tracing">
        <name>Client-based Tracing</name>
        <t>If the tester can't limit the available address families, the tester can still trace and verify whether the address family desired for the scenario is used.</t>
        <t>Client-based tracing is especially useful when Dual-stack servers and clients are available and a conclusion for the IPv6-only-strict case is desired.
By using the clients' logging/tracing/debugging functionality, the tester can verify that the actual data flows happen over IPv6, which is preferred by most network abstractions. If the client allows changing the preference between IPv6 and IPv4, IPv4-only testing is also possible.</t>
        <t>The most relevant case for this strategy is testing Web applications.
By examining the Web browser performance log or using a plugin like <xref target="IPvFoo"/> that visualizes connectivity information, the tester can determine whether all resources are available using IPv6.</t>
      </section>
      <section anchor="server-based-tracing">
        <name>Server-based Tracing</name>
        <t>Analogue to tracing on the client side, it is also possible to look at the protocols used on the server side.</t>
        <t>While this is functionally equivalent for protocols where clients only communicate to a single server,
this approach is not feasible for Web-based applications where a client usually needs flows towards many servers, where client or network based tracing are the only feasible alternatives to testing with an IPv6-only-strict client.</t>
      </section>
      <section anchor="network-based-tracing">
        <name>Network-based Tracing</name>
        <t>If the communication pattern of an application is known well enough, a packet tracer such as <xref target="Wireshark"/> can verify that an application in a Dual-stack environment uses IPv6 for all of its flows.
If this can be verified, failures in IPv6-only-strict environments are unlikely.</t>
        <t>While this is the least invasive method of testing IPv6-only-strict scenarios in a Dual-stack setup,
it is the most error-prone as it requires the tester to fully understand the network flows of the application
and cross-check these expected flows with the flows shown in the packet trace.</t>
      </section>
    </section>
    <section anchor="failures">
      <name>Common Sources of IPv6 Related Failures and Misbehavior</name>
      <t>This section discusses special failure modes that can cause unexpected application behavior that is hard to debug.</t>
      <t>Some of these cases can be automatically mitigated, especially by using Happy Eyeballs <xref target="RFC8305"/> or similar techniques.
In cases where this is not possible or where developers choose not to implement mitigation strategies, users and operators should be supported in manual resolution by providing detailed error or debug messages.</t>
      <section anchor="enable-ipv6-feature-gates">
        <name>Enable IPv6 Feature Gates</name>
        <t>Some applications completely ignore IPv6 unless explicitly configured to enable IPv6.
This adds another class of user or configuration errors, like deploying an application without enabled IPv6 support in an IPv6-only environment.
As these feature gates are often buried deeply in the documentation and are often vendor, product, or component specific, every component needs to be checked to determine whether IPv6 support needs extra configuration.</t>
      </section>
      <section anchor="ignoring-to-test-management-and-control-interfaces">
        <name>Ignoring to Test Management and Control Interfaces</name>
        <t>Ignoring management and control interfaces when enabling and testing applications for IPv6-only operation turns out to be a common pattern.
As already discussed in <xref target="lifecycle-considerations"/>, special care should be taken to cover all of these flows and avoid setups that require Dual-stack deployment.</t>
      </section>
      <section anchor="destination-address-selection-preference-and-address-filtering">
        <name>Destination Address Selection Preference and Address Filtering</name>
        <t>The destination address selection algorithm in <xref target="RFC6724"/> filters unavailable address families (Rule 1),
de-prioritizes non-matching address families (Rule 2), and clearly prioritizes IPv6 GUA addresses over IPv4 addresses.
Some OSes and alternative resolver libraries, such as <xref target="C-ARES"/>, implement <xref target="RFC6724"/> correctly. However, at the time of writing this document, major operating systems are still implementing the old behavior from <xref target="RFC3484"/> -- if an application relies on behavior updated through <xref target="RFC6724"/> or <xref target="RFC6724-update"/>, especially preference of ULA, integration testing against this behavior SHOULD be performed.</t>
        <t>Beyond that, there are several notable and widely used implementations that implement an address selection algorithm different from <xref target="RFC6724"/> or its predecessor <xref target="RFC3484"/>, causing unexpected behavior and other hard-to-debug errors:</t>
        <ul spacing="normal">
          <li>
            <t>Most JAVA runtimes do the opposite and prefer IPv4 destinations over IPv6.
To prefer IPv6 addresses over IPv4, one needs to set the system property <tt>java.net.preferIPv6Addresses=true</tt>.</t>
          </li>
          <li>
            <t>Some applications only use the first address candidate from the <tt>getaddrinfo()</tt> and fail if the connection attempt to that one fails.</t>
          </li>
          <li>
            <t>Applications composed of services built on different programming languages or runtimes may behave inconsistently with regard to choosing destination addresses.</t>
          </li>
          <li>
            <t>NGINX (at the time of writing, since at least version 1.6 and unchanged in 1.31) has its own user DNS resolver without address filtering; thus, adding a <em>AAAA</em> resource record to a backend can render that backend unusable.
After having resolved a <em>AAAA</em> resource record, it is trying to open an IPv6 socket, even when the IPv6 stack is disabled.
As socket creation failure is not expected, an internal server error is sent back to the client. <xref target="NGINX.trac-552"/></t>
          </li>
          <li>
            <t>Some resolvers ignore address families for which no default route exists or where the default-route is pointing to an unsupported/ignored device.
This becomes cumbersome especially in split-VPN use cases (e.g. when trying to contact IPv6-only endpoints via the VPN while having IPv4-only Internet connectivity).</t>
          </li>
        </ul>
      </section>
      <section anchor="listening-on-ipv4-only">
        <name>Listening on IPv4 Only</name>
        <t>Many tutorials and programmer facing documentations have still not been updated to cover listening on multiple address families to accept connections from both IPv6 and IPv4.
Listening code should be checked whether it supports distinct listening sockets for IPv6 and IPv4, or configures IPv6 sockets to also bind to IPv4.
Listening code should also be able to deal with cases where IPv6 or IPv4 have been disabled in the OS.</t>
        <t>In deployments, it is recommended to always use tools like <tt>netstat</tt> or <tt>lsof</tt> (if available) to verify all relevant address families are listened on.</t>
      </section>
      <section anchor="input-validation-and-output-rendering">
        <name>Input Validation and Output Rendering</name>
        <t>While most libraries and application frameworks have decent IPv6 support,
there often is still application logic that prevents taking advantage of the IPv6 support by the underlying components.
Checking whether user input is a valid IPv4 address or rendering output under the assumption that an address is always an IPv4 address are typical examples for this class of limitations.</t>
        <t>Even applications that have been adapted to IPv6 may have based their input validation on wrong assumptions,
e.g., checking an IPv6 address is in <tt>2000::/3</tt>.
Therefore, test cases should include IPv6 addresses from GUA (<tt>2000::/3</tt>), ULA (<tt>fc00::/7</tt>), and NAT64 WKP (<tt>64:ff9b::/96</tt>), as well as link-local (<tt>fe80::/10</tt>) range.</t>
        <t>The link-local range needs special attention as addresses are incomplete and possibly ambiguous unless associated with the relevant zone identifier or zone index <xref target="RFC4007"/>.
Testing should verify that the zone identifier or zone index are correctly displayed and can be passed if endpoints may be link-local addresses.</t>
      </section>
      <section anchor="connectivity-checks">
        <name>Connectivity Checks</name>
        <t>Some applications perform connectivity checks to determine whether Internet access is available by trying to connect to one or more well-known endpoints.
If the connectivity check endpoints differ from the actual endpoints used by the application, this approach can lead to incorrect conclusions -
especially in IPv6-only environments when connectivity checks are IPv4-only or in environments with strict network polices or split-tunnel VPNs.
Applications should prefer implementing appropriate error handling for connectivity issues than relying on connectivity pre-checks.</t>
      </section>
      <section anchor="address-bindings-in-server-backends">
        <name>Address Bindings in Server Backends</name>
        <t>Some backend services use the remote IP address of previous requests as an additional security mechanism and prevent subsequent requests from different addresses.
Address changes, e.g., through Happy Eyeballs implementations trying switching address family or carrier grade NAT64 implementations mapping subsequent request to a different source, may therefore break within a session on these events.</t>
      </section>
      <section anchor="misbehaving-middleboxes">
        <name>Misbehaving Middleboxes</name>
        <t>In practice, many IPv6-related regressions uncovered during testing turn out to be caused by hidden components outside of the application developers' control.
Middleboxes (e.g., firewalls, virus scanners, and intrusion detection systems) can break end-to-end tests in surprising ways, like terminating TLS sessions over IPv6 with certain extensions in the <em>TLS client hello</em> while correctly passing the same flow over IPv4.</t>
      </section>
    </section>
    <section anchor="ops">
      <name>Operational Considerations</name>
      <t>Lab testing of applications for IPv6 compliance should always have the next step in mind: Deploying the application and providing the users with decent IPv6 support.
Therefore, end-to-end tests, especially of cloud applications, should also keep deployment steps, prerequisites, and risks in mind.</t>
      <t>This section discusses some issues to keep in mind when planning and executing IPv6 testing.</t>
      <section anchor="operational-scope-software-lifecycle">
        <name>Operational Scope &amp; Software Lifecycle</name>
        <t>Depending on the application and deployment model, the timing of deploying IPv6 support may be in control of the users' organization, the developers' organization, or neither of them.</t>
        <t>Based on this setup, certain combinations of IPv6-enabled clients, servers, and infrastructure in between may or may not be excluded from consideration.
Therefore, it may be necessary to add test cases for old software versions with known and already fixed bugs against newly IPv6-enabled servers.
If regressions and service disruptions cannot be ruled out by the tests, a per-user or per-customer tenant opt-in/opt-out/roll-back scheme for the IPv6 enablement SHOULD be considered.</t>
      </section>
      <section anchor="allow-deny-lists">
        <name>Allow &amp; Deny Lists</name>
        <t>Application-level IP allow and deny lists pose a special challenge for deploying IPv6 in a cloud application.
As users may already have IPv6 connectivity, adding IPv6 support to the server may cause clients to use IPv6 immediately.
Having no allow list entry for the users' IPv6 addresses results in service disruptions.
Happy Eyeballs as defined in <xref target="RFC8305"/> does not solve the problem as allow list checks usually take place after the transport connection has already been established.</t>
        <t>To prevent unintended exposure of services and mitigate allow or deny lists causing service disruptions when enabling IPv6,
it is RECOMMENDED to enable including IPv6 addresses in allow and deny lists way before rolling out IPv6 on the transport and communicated towards the users.
To further limit the probability of service disruptions, generalizing Happy Eyeballs to re-try using IPv4 after certain error conditions should be evaluated.</t>
      </section>
      <section anchor="component-and-service-reuse">
        <name>Component and Service Reuse</name>
        <t>If components or cloud services can be reused in other products, special care needs to be taken when planning IPv6 deployment.
The interaction contracts between the reusing parties and the service need to be checked
whether IPv6 enablement of the services also affects the flows of these.
Additional end-to-end tests, including the reusing parties, are recommended.
This is often a recursive process.</t>
      </section>
      <section anchor="ownership-of-software-components">
        <name>Ownership of Software Components</name>
        <t>Sometimes enabling IPv6 requires touching components that are not actively maintained anymore.
Operators have to be prepared for this and plan extra time or budget for updating or replacing these components.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The testing procedures described in this document do not create any new security implications.
Some security-related issues that should be considered and ruled out by appropriate testing are discussed in <xref target="failures"/>.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="IPv6-ONLY">
          <front>
            <title>IPv6 Terminology Definitions</title>
            <author fullname="Jordi Palet Martinez" initials="J. P." surname="Martinez">
              <organization>The IPv6 Company</organization>
            </author>
            <date day="16" month="November" year="2026"/>
            <abstract>
              <t>   This document defines the terminology regarding the usage of
   expressions such as "IPv6-Only" and "IPv6-Mostly", in order to avoid
   confusions when using them in IETF and other documents.  In
   particular, a goal is to provide a reference that describes the
   actual "IPv6-Only" functionality being used in a given scope, not the
   installed protocol stack support.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-v6ops-ipv6-only-08"/>
        </reference>
        <reference anchor="CLAT">
          <front>
            <title>464XLAT Customer-side Translator (CLAT): Node Behavior and Recommendations</title>
            <author fullname="Lorenzo Colitti" initials="L." surname="Colitti">
              <organization>Google</organization>
            </author>
            <author fullname="Jen Linkova" initials="J." surname="Linkova">
              <organization>Google</organization>
            </author>
            <author fullname="Tommy Jensen" initials="T." surname="Jensen">
              <organization>Cloudflare</organization>
            </author>
            <date day="5" month="March" year="2026"/>
            <abstract>
              <t>   464XLAT defines an architecture for providing IPv4 connectivity
   across an IPv6-only network.  The solution involves two functional
   elements: a provider-side translator (PLAT) and a customer-side
   translator (CLAT).  This document updates the 464XLAT specification
   (RFC6877) and Requirements for IPv6 Customer Edge Routers (RFC8585)
   by further defining CLAT node behavior and IPv6 Customer Edge Routers
   to support IPv4-as-a-Service by providing recommendations for node
   developers on enabling and disabling CLAT.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-v6ops-claton-16"/>
        </reference>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC6147">
          <front>
            <title>DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers</title>
            <author fullname="M. Bagnulo" initials="M." surname="Bagnulo"/>
            <author fullname="A. Sullivan" initials="A." surname="Sullivan"/>
            <author fullname="P. Matthews" initials="P." surname="Matthews"/>
            <author fullname="I. van Beijnum" initials="I." surname="van Beijnum"/>
            <date month="April" year="2011"/>
            <abstract>
              <t>DNS64 is a mechanism for synthesizing AAAA records from A records. DNS64 is used with an IPv6/IPv4 translator to enable client-server communication between an IPv6-only client and an IPv4-only server, without requiring any changes to either the IPv6 or the IPv4 node, for the class of applications that work through NATs. This document specifies DNS64, and provides suggestions on how it should be deployed in conjunction with IPv6/IPv4 translators. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6147"/>
          <seriesInfo name="DOI" value="10.17487/RFC6147"/>
        </reference>
        <reference anchor="RFC8305">
          <front>
            <title>Happy Eyeballs Version 2: Better Connectivity Using Concurrency</title>
            <author fullname="D. Schinazi" initials="D." surname="Schinazi"/>
            <author fullname="T. Pauly" initials="T." surname="Pauly"/>
            <date month="December" year="2017"/>
            <abstract>
              <t>Many communication protocols operating over the modern Internet use hostnames. These often resolve to multiple IP addresses, each of which may have different performance and connectivity characteristics. Since specific addresses or address families (IPv4 or IPv6) may be blocked, broken, or sub-optimal on a network, clients that attempt multiple connections in parallel have a chance of establishing a connection more quickly. This document specifies requirements for algorithms that reduce this user-visible delay and provides an example algorithm, referred to as "Happy Eyeballs". This document obsoletes the original algorithm description in RFC 6555.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8305"/>
          <seriesInfo name="DOI" value="10.17487/RFC8305"/>
        </reference>
        <reference anchor="RFC4291">
          <front>
            <title>IP Version 6 Addressing Architecture</title>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <author fullname="S. Deering" initials="S." surname="Deering"/>
            <date month="February" year="2006"/>
            <abstract>
              <t>This specification defines the addressing architecture of the IP Version 6 (IPv6) protocol. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses.</t>
              <t>This document obsoletes RFC 3513, "IP Version 6 Addressing Architecture". [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4291"/>
          <seriesInfo name="DOI" value="10.17487/RFC4291"/>
        </reference>
        <reference anchor="RFC9844">
          <front>
            <title>Entering IPv6 Zone Identifiers in User Interfaces</title>
            <author fullname="B. Carpenter" initials="B." surname="Carpenter"/>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <date month="August" year="2025"/>
            <abstract>
              <t>This document describes how the zone identifier of an IPv6 scoped address, defined in the IPv6 Scoped Address Architecture specification (RFC 4007), should be entered into a user interface. This document obsoletes RFC 6874 and updates RFCs 4007, 7622, and 8089.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9844"/>
          <seriesInfo name="DOI" value="10.17487/RFC9844"/>
        </reference>
        <reference anchor="RFC4007">
          <front>
            <title>IPv6 Scoped Address Architecture</title>
            <author fullname="S. Deering" initials="S." surname="Deering"/>
            <author fullname="B. Haberman" initials="B." surname="Haberman"/>
            <author fullname="T. Jinmei" initials="T." surname="Jinmei"/>
            <author fullname="E. Nordmark" initials="E." surname="Nordmark"/>
            <author fullname="B. Zill" initials="B." surname="Zill"/>
            <date month="March" year="2005"/>
            <abstract>
              <t>This document specifies the architectural characteristics, expected behavior, textual representation, and usage of IPv6 addresses of different scopes. According to a decision in the IPv6 working group, this document intentionally avoids the syntax and usage of unicast site-local addresses. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4007"/>
          <seriesInfo name="DOI" value="10.17487/RFC4007"/>
        </reference>
        <reference anchor="RFC5952">
          <front>
            <title>A Recommendation for IPv6 Address Text Representation</title>
            <author fullname="S. Kawamura" initials="S." surname="Kawamura"/>
            <author fullname="M. Kawashima" initials="M." surname="Kawashima"/>
            <date month="August" year="2010"/>
            <abstract>
              <t>As IPv6 deployment increases, there will be a dramatic increase in the need to use IPv6 addresses in text. While the IPv6 address architecture in Section 2.2 of RFC 4291 describes a flexible model for text representation of an IPv6 address, this flexibility has been causing problems for operators, system engineers, and users. This document defines a canonical textual representation format. It does not define a format for internal storage, such as within an application or database. It is expected that the canonical format will be followed by humans and systems when representing IPv6 addresses as text, but all implementations must accept and be able to handle any legitimate RFC 4291 format. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5952"/>
          <seriesInfo name="DOI" value="10.17487/RFC5952"/>
        </reference>
        <reference anchor="RFC6052">
          <front>
            <title>IPv6 Addressing of IPv4/IPv6 Translators</title>
            <author fullname="C. Bao" initials="C." surname="Bao"/>
            <author fullname="C. Huitema" initials="C." surname="Huitema"/>
            <author fullname="M. Bagnulo" initials="M." surname="Bagnulo"/>
            <author fullname="M. Boucadair" initials="M." surname="Boucadair"/>
            <author fullname="X. Li" initials="X." surname="Li"/>
            <date month="October" year="2010"/>
            <abstract>
              <t>This document discusses the algorithmic translation of an IPv6 address to a corresponding IPv4 address, and vice versa, using only statically configured information. It defines a well-known prefix for use in algorithmic translations, while allowing organizations to also use network-specific prefixes when appropriate. Algorithmic translation is used in IPv4/IPv6 translators, as well as other types of proxies and gateways (e.g., for DNS) used in IPv4/IPv6 scenarios. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6052"/>
          <seriesInfo name="DOI" value="10.17487/RFC6052"/>
        </reference>
        <reference anchor="RFC6724">
          <front>
            <title>Default Address Selection for Internet Protocol Version 6 (IPv6)</title>
            <author fullname="D. Thaler" initials="D." role="editor" surname="Thaler"/>
            <author fullname="R. Draves" initials="R." surname="Draves"/>
            <author fullname="A. Matsumoto" initials="A." surname="Matsumoto"/>
            <author fullname="T. Chown" initials="T." surname="Chown"/>
            <date month="September" year="2012"/>
            <abstract>
              <t>This document describes two algorithms, one for source address selection and one for destination address selection. The algorithms specify default behavior for all Internet Protocol version 6 (IPv6) implementations. They do not override choices made by applications or upper-layer protocols, nor do they preclude the development of more advanced mechanisms for address selection. The two algorithms share a common context, including an optional mechanism for allowing administrators to provide policy that can override the default behavior. In dual-stack implementations, the destination address selection algorithm can consider both IPv4 and IPv6 addresses -- depending on the available source addresses, the algorithm might prefer IPv6 addresses over IPv4 addresses, or vice versa.</t>
              <t>Default address selection as defined in this specification applies to all IPv6 nodes, including both hosts and routers. This document obsoletes RFC 3484. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6724"/>
          <seriesInfo name="DOI" value="10.17487/RFC6724"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="RFC7084bis">
          <front>
            <title>Basic Requirements for IPv6 Customer Edge Routers</title>
            <author fullname="Gábor Lencse" initials="G." surname="Lencse">
              <organization>Széchenyi István University</organization>
            </author>
            <author fullname="Jordi Palet Martinez" initials="J. P." surname="Martinez">
              <organization>The IPv6 Company</organization>
            </author>
            <author fullname="Ben Patton" initials="B." surname="Patton">
              <organization>University of New Hampshire, Interoperability Lab (UNH-IOL)</organization>
            </author>
            <author fullname="Timothy Winters" initials="T." surname="Winters">
              <organization>QA Cafe</organization>
            </author>
            <date day="1" month="November" year="2026"/>
            <abstract>
              <t>   This document specifies requirements for an IPv6 Customer Edge (CE)
   router.  Specifically, the current version of this document focuses
   on the basic provisioning of an IPv6 CE router and the provisioning
   of IPv6 hosts attached to it.  The document obsoletes RFC 7084.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-v6ops-rfc7084bis-08"/>
        </reference>
        <reference anchor="V6MOPS">
          <front>
            <title>IPv6-mostly Networks: Deployment and Operations Considerations</title>
            <author fullname="Nick Buraglio" initials="N." surname="Buraglio">
              <organization>Energy Sciences Network</organization>
            </author>
            <author fullname="Ondřej Caletka" initials="O." surname="Caletka">
              <organization>RIPE NCC</organization>
            </author>
            <author fullname="Jen Linkova" initials="J." surname="Linkova">
              <organization>Google</organization>
            </author>
            <date day="29" month="October" year="2026"/>
            <abstract>
              <t>   This document discusses a deployment scenario called "an IPv6-mostly
   network", when IPv6-only and IPv4-enabled endpoints coexist on the
   same network (e.g. local area network (LAN)).  This approach enables
   incremental transition from dual-stack to IPv6-only networks by
   allowing IPv6-capable devices to remain IPv6-only while the network
   is seamlessly supplying IPv4 addresses to those devices that require
   them.  This document discusses the requirements, recommendations, and
   challenges associated with deploying IPv6-mostly networks in
   enterprise and public Wi-Fi environments.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-v6ops-6mops-12"/>
        </reference>
        <reference anchor="RFC6146-bis">
          <front>
            <title>Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers</title>
            <author fullname="Marcelo Bagnulo" initials="M." surname="Bagnulo">
              <organization>UC3M</organization>
            </author>
            <author fullname="Philip Matthews" initials="P." surname="Matthews">
         </author>
            <author fullname="Jordi Palet Martinez" initials="J. P." surname="Martinez">
              <organization>The IPv6 Company</organization>
            </author>
            <date day="4" month="September" year="2026"/>
            <abstract>
              <t>   This document specifies a stateful NAT64 translation, which allows
   IPv6-Only clients to contact IPv4 servers using unicast UDP, TCP, or
   ICMP.  One or more public IPv4 addresses assigned to a stateful NAT64
   translator are shared among several IPv6-Only clients.  Stateful
   NAT64 translation also supports IPv4-initiated communications to a
   subset of the IPv6 hosts through configured bindings in the stateful
   NAT64 translator.  When the stateful NAT64 translation is used in
   conjunction with DNS64, no changes are required in either the IPv6
   client or the IPv4 server.

   This document obsoletes RFC 6146.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-v6ops-rfc6146-bis-16"/>
        </reference>
        <reference anchor="RFC6724-update">
          <front>
            <title>Prioritizing known-local IPv6 ULAs through address selection policy</title>
            <author fullname="Nick Buraglio" initials="N." surname="Buraglio">
              <organization>Energy Sciences Network</organization>
            </author>
            <author fullname="Tim Chown" initials="T." surname="Chown">
              <organization>Jisc</organization>
            </author>
            <author fullname="Jeremy Duncan" initials="J." surname="Duncan">
              <organization>Tachyon Dynamics</organization>
            </author>
            <date day="11" month="August" year="2025"/>
            <abstract>
              <t>   This document updates the default address selection algorithm for
   Internet Protocol Version 6 (IPv6), originally specified in RFC 6724,
   based on accumulated operational experience.  It introduces the
   concept of "known-local" Unique Local Address (ULA) prefixes within
   the fd00::/8 block and specifies that ULA-to-ULA communications using
   such prefixes should be preferred over both IPv4-to-IPv4 and GUA-to-
   GUA (Global Unicast Address) communications in local use scenarios.
   The document defines mechanisms for nodes to identify and incorporate
   known-local prefixes into their address selection policy tables.  It
   introduces a requirement to implement Rule 5.5 of RFC 6724 and
   reduces the default precedence for 6to4 addresses.  These updates
   enhance the supportability of typical deployment environments,
   including automatic and unmanaged configurations, and promote
   consistent IPv6-over-IPv4 precedence behavior for both ULA and GUA
   within local networks.  The document acknowledges that certain
   atypical deployment models may require explicit configuration to
   achieve intended operational outcomes.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-6man-rfc6724-update-25"/>
        </reference>
        <reference anchor="MASQUE">
          <front>
            <title>The MASQUE Architecture</title>
            <author fullname="David Schinazi" initials="D." surname="Schinazi">
              <organization>Google LLC</organization>
            </author>
            <date day="27" month="August" year="2026"/>
            <abstract>
              <t>   MASQUE (Multiplexed Application Substrate over QUIC Encryption) is a
   set of protocols and extensions to HTTP that allow proxying all kinds
   of Internet traffic over HTTP.  This document describes the
   architectural principles behind MASQUE, and the properties that
   MASQUE can provide.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-schinazi-masque-proxy-09"/>
        </reference>
        <reference anchor="CN-CAC-2023" target="http://www.cac.gov.cn/2023-04/27/c_1684239012351367.htm">
          <front>
            <title>2023 Work Arrangement for Further Promoting Large-scale IPv6 Deployment and Application</title>
            <author>
              <organization/>
            </author>
            <date year="2023" month="April" day="27"/>
          </front>
        </reference>
        <reference anchor="US-OMB-M-21-07" target="https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf">
          <front>
            <title>M-21-07 - Completing the Transition to Internet Protocol Version 6 (IPv6)</title>
            <author>
              <organization/>
            </author>
            <date year="2020" month="November" day="19"/>
          </front>
          <seriesInfo name="United States of America Office of Management and Budget" value="Memorandum for Heads of Executive Departments and Agencies"/>
        </reference>
        <reference anchor="DE-BIT-2020-14" target="https://www.cio.bund.de/SharedDocs/downloads/Webs/CIO/DE/cio-bund/steuerung-it-bund/beschluesse_cio-board_KoITB/2020_14_Beschluss_Konferenz_IT_Beauftragte.pdf">
          <front>
            <title>Beschluss Nr. 2020/14 - Zukunftsfaehige Netzinfrastrukturen auf Basis von funktionsfiaehigem IPv6</title>
            <author>
              <organization/>
            </author>
            <date year="2020" month="November" day="11"/>
          </front>
          <seriesInfo name="Konferenz der IT-Beauftragten der Ressorts" value=""/>
          <annotation>Original link is broken - cached copy available at https://raw.githubusercontent.com/ietf-wg-v6ops/draft-itef-v6ops-ipv6-app-testing/refs/tags/draft-ietf-v6ops-ipv6-app-testing-05/references/DE-BIT-2020-14.pdf</annotation>
        </reference>
        <reference anchor="CZ-ENDv4" target="https://konecipv4.cz/">
          <front>
            <title>Czech Republic sets IPv4 end date</title>
            <author>
              <organization/>
            </author>
            <date year="2024" month="January" day="17"/>
          </front>
        </reference>
        <reference anchor="US-NIST.SP.500-267Ar1" target="https://nvlpubs.nist.gov/nistpubs/specialpublications/NIST.SP.500-267Ar1.pdf">
          <front>
            <title>NIST Special Publication 500-267 Revision 1 - NIST IPv6 Profile</title>
            <author>
              <organization/>
            </author>
            <date year="2020" month="November" day="23"/>
          </front>
        </reference>
        <reference anchor="iCloud-Private-Relay" target="https://developer.apple.com/videos/play/wwdc2021/10096/">
          <front>
            <title>Apple iCLoud Private Relay (WWDC2021)</title>
            <author>
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="IPvFoo" target="https://pmarks.net/ipvfoo">
          <front>
            <title>IPvFoo - a Chrome/Firefox extension that adds an icon to indicate whether the current page was fetched using IPv4 or IPv6.</title>
            <author initials="P." surname="Marks" fullname="Paul Marks">
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="Wireshark" target="https://www.wireshark.org/">
          <front>
            <title>Wireshark packet tracer</title>
            <author>
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="C-ARES" target="https://c-ares.org/">
          <front>
            <title>C-ARES - a modern DNS (stub) resolver library, written in C</title>
            <author>
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="Selenium" target="https://www.selenium.dev/">
          <front>
            <title>Selenium WebDriver</title>
            <author>
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="NGINX.trac-552" target="https://trac.nginx.org/nginx/ticket/552">
          <front>
            <title>Nginx doesn't honor net.ipv6.conf.all.disable_ipv6</title>
            <author>
              <organization/>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="RFC8504">
          <front>
            <title>IPv6 Node Requirements</title>
            <author fullname="T. Chown" initials="T." surname="Chown"/>
            <author fullname="J. Loughney" initials="J." surname="Loughney"/>
            <author fullname="T. Winters" initials="T." surname="Winters"/>
            <date month="January" year="2019"/>
            <abstract>
              <t>This document defines requirements for IPv6 nodes. It is expected that IPv6 will be deployed in a wide range of devices and situations. Specifying the requirements for IPv6 nodes allows IPv6 to function well and interoperate in a large number of situations and deployments.</t>
              <t>This document obsoletes RFC 6434, and in turn RFC 4294.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="220"/>
          <seriesInfo name="RFC" value="8504"/>
          <seriesInfo name="DOI" value="10.17487/RFC8504"/>
        </reference>
        <reference anchor="RFC5118">
          <front>
            <title>Session Initiation Protocol (SIP) Torture Test Messages for Internet Protocol Version 6 (IPv6)</title>
            <author fullname="V. Gurbani" initials="V." surname="Gurbani"/>
            <author fullname="C. Boulton" initials="C." surname="Boulton"/>
            <author fullname="R. Sparks" initials="R." surname="Sparks"/>
            <date month="February" year="2008"/>
            <abstract>
              <t>This document provides examples of Session Initiation Protocol (SIP) test messages designed to exercise and "torture" the code of an IPv6-enabled SIP implementation. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5118"/>
          <seriesInfo name="DOI" value="10.17487/RFC5118"/>
        </reference>
        <reference anchor="RFC8925">
          <front>
            <title>IPv6-Only Preferred Option for DHCPv4</title>
            <author fullname="L. Colitti" initials="L." surname="Colitti"/>
            <author fullname="J. Linkova" initials="J." surname="Linkova"/>
            <author fullname="M. Richardson" initials="M." surname="Richardson"/>
            <author fullname="T. Mrugalski" initials="T." surname="Mrugalski"/>
            <date month="October" year="2020"/>
            <abstract>
              <t>This document specifies a DHCPv4 option to indicate that a host supports an IPv6-only mode and is willing to forgo obtaining an IPv4 address if the network provides IPv6 connectivity. It also updates RFC 2563 to specify DHCPv4 server behavior when the server receives a DHCPDISCOVER not containing the Auto-Configure option but containing the new option defined in this document.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8925"/>
          <seriesInfo name="DOI" value="10.17487/RFC8925"/>
        </reference>
        <reference anchor="RFC6877">
          <front>
            <title>464XLAT: Combination of Stateful and Stateless Translation</title>
            <author fullname="M. Mawatari" initials="M." surname="Mawatari"/>
            <author fullname="M. Kawashima" initials="M." surname="Kawashima"/>
            <author fullname="C. Byrne" initials="C." surname="Byrne"/>
            <date month="April" year="2013"/>
            <abstract>
              <t>This document describes an architecture (464XLAT) for providing limited IPv4 connectivity across an IPv6-only network by combining existing and well-known stateful protocol translation (as described in RFC 6146) in the core and stateless protocol translation (as described in RFC 6145) at the edge. 464XLAT is a simple and scalable technique to quickly deploy limited IPv4 access service to IPv6-only edge networks without encapsulation.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6877"/>
          <seriesInfo name="DOI" value="10.17487/RFC6877"/>
        </reference>
        <reference anchor="RFC7915">
          <front>
            <title>IP/ICMP Translation Algorithm</title>
            <author fullname="C. Bao" initials="C." surname="Bao"/>
            <author fullname="X. Li" initials="X." surname="Li"/>
            <author fullname="F. Baker" initials="F." surname="Baker"/>
            <author fullname="T. Anderson" initials="T." surname="Anderson"/>
            <author fullname="F. Gont" initials="F." surname="Gont"/>
            <date month="June" year="2016"/>
            <abstract>
              <t>This document describes the Stateless IP/ICMP Translation Algorithm (SIIT), which translates between IPv4 and IPv6 packet headers (including ICMP headers). This document obsoletes RFC 6145.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7915"/>
          <seriesInfo name="DOI" value="10.17487/RFC7915"/>
        </reference>
        <reference anchor="RFC8489">
          <front>
            <title>Session Traversal Utilities for NAT (STUN)</title>
            <author fullname="M. Petit-Huguenin" initials="M." surname="Petit-Huguenin"/>
            <author fullname="G. Salgueiro" initials="G." surname="Salgueiro"/>
            <author fullname="J. Rosenberg" initials="J." surname="Rosenberg"/>
            <author fullname="D. Wing" initials="D." surname="Wing"/>
            <author fullname="R. Mahy" initials="R." surname="Mahy"/>
            <author fullname="P. Matthews" initials="P." surname="Matthews"/>
            <date month="February" year="2020"/>
            <abstract>
              <t>Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other protocols in dealing with NAT traversal. It can be used by an endpoint to determine the IP address and port allocated to it by a NAT. It can also be used to check connectivity between two endpoints and as a keep-alive protocol to maintain NAT bindings. STUN works with many existing NATs and does not require any special behavior from them.</t>
              <t>STUN is not a NAT traversal solution by itself. Rather, it is a tool to be used in the context of a NAT traversal solution.</t>
              <t>This document obsoletes RFC 5389.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8489"/>
          <seriesInfo name="DOI" value="10.17487/RFC8489"/>
        </reference>
        <reference anchor="RFC8656">
          <front>
            <title>Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)</title>
            <author fullname="T. Reddy" initials="T." role="editor" surname="Reddy"/>
            <author fullname="A. Johnston" initials="A." role="editor" surname="Johnston"/>
            <author fullname="P. Matthews" initials="P." surname="Matthews"/>
            <author fullname="J. Rosenberg" initials="J." surname="Rosenberg"/>
            <date month="February" year="2020"/>
            <abstract>
              <t>If a host is located behind a NAT, it can be impossible for that host to communicate directly with other hosts (peers) in certain situations. In these situations, it is necessary for the host to use the services of an intermediate node that acts as a communication relay. This specification defines a protocol, called "Traversal Using Relays around NAT" (TURN), that allows the host to control the operation of the relay and to exchange packets with its peers using the relay. TURN differs from other relay control protocols in that it allows a client to communicate with multiple peers using a single relay address.</t>
              <t>The TURN protocol was designed to be used as part of the Interactive Connectivity Establishment (ICE) approach to NAT traversal, though it can also be used without ICE.</t>
              <t>This document obsoletes RFCs 5766 and 6156.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8656"/>
          <seriesInfo name="DOI" value="10.17487/RFC8656"/>
        </reference>
        <reference anchor="RFC7230">
          <front>
            <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2014"/>
            <abstract>
              <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document provides an overview of HTTP architecture and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements, and describes related security concerns for implementations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7230"/>
          <seriesInfo name="DOI" value="10.17487/RFC7230"/>
        </reference>
        <reference anchor="RFC1928">
          <front>
            <title>SOCKS Protocol Version 5</title>
            <author fullname="M. Leech" initials="M." surname="Leech"/>
            <author fullname="M. Ganis" initials="M." surname="Ganis"/>
            <author fullname="Y. Lee" initials="Y." surname="Lee"/>
            <author fullname="R. Kuris" initials="R." surname="Kuris"/>
            <author fullname="D. Koblas" initials="D." surname="Koblas"/>
            <author fullname="L. Jones" initials="L." surname="Jones"/>
            <date month="March" year="1996"/>
            <abstract>
              <t>This memo describes a protocol that is an evolution of the previous version of the protocol, version 4 [1]. This new protocol stems from active discussions and prototype implementations. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1928"/>
          <seriesInfo name="DOI" value="10.17487/RFC1928"/>
        </reference>
        <reference anchor="RFC6762">
          <front>
            <title>Multicast DNS</title>
            <author fullname="S. Cheshire" initials="S." surname="Cheshire"/>
            <author fullname="M. Krochmal" initials="M." surname="Krochmal"/>
            <date month="February" year="2013"/>
            <abstract>
              <t>As networked devices become smaller, more portable, and more ubiquitous, the ability to operate with less configured infrastructure is increasingly important. In particular, the ability to look up DNS resource record data types (including, but not limited to, host names) in the absence of a conventional managed DNS server is useful.</t>
              <t>Multicast DNS (mDNS) provides the ability to perform DNS-like operations on the local link in the absence of any conventional Unicast DNS server. In addition, Multicast DNS designates a portion of the DNS namespace to be free for local use, without the need to pay any annual fee, and without the need to set up delegations or otherwise configure a conventional DNS server to answer for those names.</t>
              <t>The primary benefits of Multicast DNS names are that (i) they require little or no administration or configuration to set them up, (ii) they work when no infrastructure is present, and (iii) they work during infrastructure failures.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6762"/>
          <seriesInfo name="DOI" value="10.17487/RFC6762"/>
        </reference>
        <reference anchor="RFC10001">
          <front>
            <title>Operational Guidelines for DNS Transport in Mixed IPv4/IPv6 Environments</title>
            <author fullname="Momoka" surname="Momoka"/>
            <author fullname="T. Fiebig" initials="T." surname="Fiebig"/>
            <date month="August" year="2026"/>
            <abstract>
              <t>This document provides guidelines and documents best current practice for operating authoritative DNS servers, recursive resolvers, and stub resolvers in a mixed IPv4/IPv6 environment. This document recommends that both authoritative DNS servers and recursive resolvers support IPv4 and IPv6. It also provides guidance on how recursive DNS resolvers should select upstream DNS servers, including when IPv4-embedded IPv6 addresses are available.</t>
              <t>This document obsoletes RFC 3901.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="91"/>
          <seriesInfo name="RFC" value="10001"/>
          <seriesInfo name="DOI" value="10.17487/RFC10001"/>
        </reference>
        <reference anchor="RFC6763">
          <front>
            <title>DNS-Based Service Discovery</title>
            <author fullname="S. Cheshire" initials="S." surname="Cheshire"/>
            <author fullname="M. Krochmal" initials="M." surname="Krochmal"/>
            <date month="February" year="2013"/>
            <abstract>
              <t>This document specifies how DNS resource records are named and structured to facilitate service discovery. Given a type of service that a client is looking for, and a domain in which the client is looking for that service, this mechanism allows clients to discover a list of named instances of that desired service, using standard DNS queries. This mechanism is referred to as DNS-based Service Discovery, or DNS-SD.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6763"/>
          <seriesInfo name="DOI" value="10.17487/RFC6763"/>
        </reference>
        <reference anchor="RFC3927">
          <front>
            <title>Dynamic Configuration of IPv4 Link-Local Addresses</title>
            <author fullname="S. Cheshire" initials="S." surname="Cheshire"/>
            <author fullname="B. Aboba" initials="B." surname="Aboba"/>
            <author fullname="E. Guttman" initials="E." surname="Guttman"/>
            <date month="May" year="2005"/>
            <abstract>
              <t>To participate in wide-area IP networking, a host needs to be configured with IP addresses for its interfaces, either manually by the user or automatically from a source on the network such as a Dynamic Host Configuration Protocol (DHCP) server. Unfortunately, such address configuration information may not always be available. It is therefore beneficial for a host to be able to depend on a useful subset of IP networking functions even when no address configuration is available. This document describes how a host may automatically configure an interface with an IPv4 address within the 169.254/16 prefix that is valid for communication with other devices connected to the same physical (or logical) link.</t>
              <t>IPv4 Link-Local addresses are not suitable for communication with devices not directly connected to the same physical (or logical) link, and are only used where stable, routable addresses are not available (such as on ad hoc or isolated networks). This document does not recommend that IPv4 Link-Local addresses and routable addresses be configured simultaneously on the same interface. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3927"/>
          <seriesInfo name="DOI" value="10.17487/RFC3927"/>
        </reference>
        <reference anchor="RFC9114">
          <front>
            <title>HTTP/3</title>
            <author fullname="M. Bishop" initials="M." role="editor" surname="Bishop"/>
            <date month="June" year="2022"/>
            <abstract>
              <t>The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP semantics over QUIC. This document also identifies HTTP/2 features that are subsumed by QUIC and describes how HTTP/2 extensions can be ported to HTTP/3.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9114"/>
          <seriesInfo name="DOI" value="10.17487/RFC9114"/>
        </reference>
        <reference anchor="RFC6124">
          <front>
            <title>An EAP Authentication Method Based on the Encrypted Key Exchange (EKE) Protocol</title>
            <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/>
            <author fullname="G. Zorn" initials="G." surname="Zorn"/>
            <author fullname="H. Tschofenig" initials="H." surname="Tschofenig"/>
            <author fullname="S. Fluhrer" initials="S." surname="Fluhrer"/>
            <date month="February" year="2011"/>
            <abstract>
              <t>The Extensible Authentication Protocol (EAP) describes a framework that allows the use of multiple authentication mechanisms. This document defines an authentication mechanism for EAP called EAP-EKE, based on the Encrypted Key Exchange (EKE) protocol. This method provides mutual authentication through the use of a short, easy to remember password. Compared with other common authentication methods, EAP-EKE is not susceptible to dictionary attacks. Neither does it require the availability of public-key certificates. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6124"/>
          <seriesInfo name="DOI" value="10.17487/RFC6124"/>
        </reference>
        <reference anchor="RFC8040">
          <front>
            <title>RESTCONF Protocol</title>
            <author fullname="A. Bierman" initials="A." surname="Bierman"/>
            <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <date month="January" year="2017"/>
            <abstract>
              <t>This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8040"/>
          <seriesInfo name="DOI" value="10.17487/RFC8040"/>
        </reference>
        <referencegroup anchor="STD62" target="https://www.rfc-editor.org/info/std62">
          <reference anchor="RFC3411" target="https://www.rfc-editor.org/info/rfc3411">
            <front>
              <title>An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks</title>
              <author fullname="D. Harrington" initials="D." surname="Harrington"/>
              <author fullname="R. Presuhn" initials="R." surname="Presuhn"/>
              <author fullname="B. Wijnen" initials="B." surname="Wijnen"/>
              <date month="December" year="2002"/>
              <abstract>
                <t>This document describes an architecture for describing Simple Network Management Protocol (SNMP) Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. The major portions of the architecture are an SNMP engine containing a Message Processing Subsystem, a Security Subsystem and an Access Control Subsystem, and possibly multiple SNMP applications which provide specific functional processing of management data. This document obsoletes RFC 2571. [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="62"/>
            <seriesInfo name="RFC" value="3411"/>
            <seriesInfo name="DOI" value="10.17487/RFC3411"/>
          </reference>
          <reference anchor="RFC3412" target="https://www.rfc-editor.org/info/rfc3412">
            <front>
              <title>Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)</title>
              <author fullname="J. Case" initials="J." surname="Case"/>
              <author fullname="D. Harrington" initials="D." surname="Harrington"/>
              <author fullname="R. Presuhn" initials="R." surname="Presuhn"/>
              <author fullname="B. Wijnen" initials="B." surname="Wijnen"/>
              <date month="December" year="2002"/>
              <abstract>
                <t>This document describes the Message Processing and Dispatching for Simple Network Management Protocol (SNMP) messages within the SNMP architecture. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. This document obsoletes RFC 2572. [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="62"/>
            <seriesInfo name="RFC" value="3412"/>
            <seriesInfo name="DOI" value="10.17487/RFC3412"/>
          </reference>
          <reference anchor="RFC3413" target="https://www.rfc-editor.org/info/rfc3413">
            <front>
              <title>Simple Network Management Protocol (SNMP) Applications</title>
              <author fullname="D. Levi" initials="D." surname="Levi"/>
              <author fullname="P. Meyer" initials="P." surname="Meyer"/>
              <author fullname="B. Stewart" initials="B." surname="Stewart"/>
              <date month="December" year="2002"/>
              <abstract>
                <t>This document describes five types of Simple Network Management Protocol (SNMP) applications which make use of an SNMP engine as described in STD 62, RFC 3411. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This document also defines Management Information Base (MIB) modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. This document obsoletes RFC 2573. [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="62"/>
            <seriesInfo name="RFC" value="3413"/>
            <seriesInfo name="DOI" value="10.17487/RFC3413"/>
          </reference>
          <reference anchor="RFC3414" target="https://www.rfc-editor.org/info/rfc3414">
            <front>
              <title>User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)</title>
              <author fullname="U. Blumenthal" initials="U." surname="Blumenthal"/>
              <author fullname="B. Wijnen" initials="B." surname="Wijnen"/>
              <date month="December" year="2002"/>
              <abstract>
                <t>This document describes the User-based Security Model (USM) for Simple Network Management Protocol (SNMP) version 3 for use in the SNMP architecture. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a Management Information Base (MIB) for remotely monitoring/managing the configuration parameters for this Security Model. This document obsoletes RFC 2574. [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="62"/>
            <seriesInfo name="RFC" value="3414"/>
            <seriesInfo name="DOI" value="10.17487/RFC3414"/>
          </reference>
          <reference anchor="RFC3415" target="https://www.rfc-editor.org/info/rfc3415">
            <front>
              <title>View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)</title>
              <author fullname="B. Wijnen" initials="B." surname="Wijnen"/>
              <author fullname="R. Presuhn" initials="R." surname="Presuhn"/>
              <author fullname="K. McCloghrie" initials="K." surname="McCloghrie"/>
              <date month="December" year="2002"/>
              <abstract>
                <t>This document describes the View-based Access Control Model (VACM) for use in the Simple Network Management Protocol (SNMP) architecture. It defines the Elements of Procedure for controlling access to management information. This document also includes a Management Information Base (MIB) for remotely managing the configuration parameters for the View- based Access Control Model. This document obsoletes RFC 2575. [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="62"/>
            <seriesInfo name="RFC" value="3415"/>
            <seriesInfo name="DOI" value="10.17487/RFC3415"/>
          </reference>
          <reference anchor="RFC3416" target="https://www.rfc-editor.org/info/rfc3416">
            <front>
              <title>Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)</title>
              <author fullname="R. Presuhn" initials="R." role="editor" surname="Presuhn"/>
              <date month="December" year="2002"/>
              <abstract>
                <t>This document defines version 2 of the protocol operations for the Simple Network Management Protocol (SNMP). It defines the syntax and elements of procedure for sending, receiving, and processing SNMP PDUs. This document obsoletes RFC 1905. [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="62"/>
            <seriesInfo name="RFC" value="3416"/>
            <seriesInfo name="DOI" value="10.17487/RFC3416"/>
          </reference>
          <reference anchor="RFC3417" target="https://www.rfc-editor.org/info/rfc3417">
            <front>
              <title>Transport Mappings for the Simple Network Management Protocol (SNMP)</title>
              <author fullname="R. Presuhn" initials="R." role="editor" surname="Presuhn"/>
              <date month="December" year="2002"/>
              <abstract>
                <t>This document defines the transport of Simple Network Management Protocol (SNMP) messages over various protocols. This document obsoletes RFC 1906. [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="62"/>
            <seriesInfo name="RFC" value="3417"/>
            <seriesInfo name="DOI" value="10.17487/RFC3417"/>
          </reference>
          <reference anchor="RFC3418" target="https://www.rfc-editor.org/info/rfc3418">
            <front>
              <title>Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)</title>
              <author fullname="R. Presuhn" initials="R." role="editor" surname="Presuhn"/>
              <date month="December" year="2002"/>
              <abstract>
                <t>This document defines managed objects which describe the behavior of a Simple Network Management Protocol (SNMP) entity. This document obsoletes RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2). [STANDARDS-TRACK]</t>
              </abstract>
            </front>
            <seriesInfo name="STD" value="62"/>
            <seriesInfo name="RFC" value="3418"/>
            <seriesInfo name="DOI" value="10.17487/RFC3418"/>
          </reference>
        </referencegroup>
        <reference anchor="RFC9232">
          <front>
            <title>Network Telemetry Framework</title>
            <author fullname="H. Song" initials="H." surname="Song"/>
            <author fullname="F. Qin" initials="F." surname="Qin"/>
            <author fullname="P. Martinez-Julia" initials="P." surname="Martinez-Julia"/>
            <author fullname="L. Ciavaglia" initials="L." surname="Ciavaglia"/>
            <author fullname="A. Wang" initials="A." surname="Wang"/>
            <date month="May" year="2022"/>
            <abstract>
              <t>Network telemetry is a technology for gaining network insight and facilitating efficient and automated network management. It encompasses various techniques for remote data generation, collection, correlation, and consumption. This document describes an architectural framework for network telemetry, motivated by challenges that are encountered as part of the operation of networks and by the requirements that ensue. This document clarifies the terminology and classifies the modules and components of a network telemetry system from different perspectives. The framework and taxonomy help to set a common ground for the collection of related work and provide guidance for related technique and standard developments.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9232"/>
          <seriesInfo name="DOI" value="10.17487/RFC9232"/>
        </reference>
        <reference anchor="RFC5424">
          <front>
            <title>The Syslog Protocol</title>
            <author fullname="R. Gerhards" initials="R." surname="Gerhards"/>
            <date month="March" year="2009"/>
            <abstract>
              <t>This document describes the syslog protocol, which is used to convey event notification messages. This protocol utilizes a layered architecture, which allows the use of any number of transport protocols for transmission of syslog messages. It also provides a message format that allows vendor-specific extensions to be provided in a structured way.</t>
              <t>This document has been written with the original design goals for traditional syslog in mind. The need for a new layered specification has arisen because standardization efforts for reliable and secure syslog extensions suffer from the lack of a Standards-Track and transport-independent RFC. Without this document, each other standard needs to define its own syslog packet format and transport mechanism, which over time will introduce subtle compatibility issues. This document tries to provide a foundation that syslog extensions can build on. This layered architecture approach also provides a solid basis that allows code to be written once for each syslog feature rather than once for each transport. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5424"/>
          <seriesInfo name="DOI" value="10.17487/RFC5424"/>
        </reference>
        <reference anchor="RFC3484">
          <front>
            <title>Default Address Selection for Internet Protocol version 6 (IPv6)</title>
            <author fullname="R. Draves" initials="R." surname="Draves"/>
            <date month="March" year="2003"/>
            <abstract>
              <t>This document describes two algorithms, for source address selection and for destination address selection. The algorithms specify default behavior for all Internet Protocol version 6 (IPv6) implementations. They do not override choices made by applications or upper-layer protocols, nor do they preclude the development of more advanced mechanisms for address selection. The two algorithms share a common context, including an optional mechanism for allowing administrators to provide policy that can override the default behavior. In dual stack implementations, the destination address selection algorithm can consider both IPv4 and IPv6 addresses - depending on the available source addresses, the algorithm might prefer IPv6 addresses over IPv4 addresses, or vice-versa. All IPv6 nodes, including both hosts and routers, must implement default address selection as defined in this specification. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3484"/>
          <seriesInfo name="DOI" value="10.17487/RFC3484"/>
        </reference>
        <reference anchor="RFC7239">
          <front>
            <title>Forwarded HTTP Extension</title>
            <author fullname="A. Petersson" initials="A." surname="Petersson"/>
            <author fullname="M. Nilsson" initials="M." surname="Nilsson"/>
            <date month="June" year="2014"/>
            <abstract>
              <t>This document defines an HTTP extension header field that allows proxy components to disclose information lost in the proxying process, for example, the originating IP address of a request or IP address of the proxy on the user-agent-facing interface. In a path of proxying components, this makes it possible to arrange it so that each subsequent component will have access to, for example, all IP addresses used in the chain of proxied HTTP requests.</t>
              <t>This document also specifies guidelines for a proxy administrator to anonymize the origin of a request.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7239"/>
          <seriesInfo name="DOI" value="10.17487/RFC7239"/>
        </reference>
      </references>
    </references>
    <?line 646?>

<section anchor="example">
      <name>Example: Deriving IPv6 Test Cases for a Web Application</name>
      <t>This appendix illustrates how the methodology of this document can be applied to a concrete application.
It starts from the application's existing end-to-end tests and its system architecture,
crosses the two to identify the relevant data flows between components as described in <xref target="complex-apps"/>,
and finally derives the IPv6 test cases by applying the connectivity scenarios from <xref target="scn_combinations"/> to each flow.</t>
      <t>The example is deliberately kept small; a real application will have many more components, flows, and tests.
The intent is to demonstrate the method, not to provide a complete test plan.
This appendix is informative.</t>
      <section anchor="example-app">
        <name>The Application and its End-to-End Tests</name>
        <t>The example application is the online shop of a bookshop.
Customers use a browser-based frontend to browse the catalog, check availability, and place orders.</t>
        <t>The bookshop already maintains a suite of functional end-to-end tests.
These tests predate any IPv6 testing effort and verify the functional correctness of the application; they form the basis from which the IPv6 test cases are derived.
<xref target="example-e2e-tests"/> provides a non-exhaustive list of such tests.</t>
        <table anchor="example-e2e-tests">
          <name>Existing end-to-end tests</name>
          <thead>
            <tr>
              <th align="left">Test</th>
              <th align="left">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">E2E-1</td>
              <td align="left">Load the shop front page and browse the catalog.</td>
            </tr>
            <tr>
              <td align="left">E2E-2</td>
              <td align="left">Search the catalog and open a book's detail page.</td>
            </tr>
            <tr>
              <td align="left">E2E-3</td>
              <td align="left">Open a book detail page showing live stock availability.</td>
            </tr>
            <tr>
              <td align="left">E2E-4</td>
              <td align="left">Register a new customer account and sign in.</td>
            </tr>
            <tr>
              <td align="left">E2E-5</td>
              <td align="left">Add books to the cart and place an order, issuing a shipment.</td>
            </tr>
            <tr>
              <td align="left">E2E-6</td>
              <td align="left">Open the order history and track the shipment status of an existing order.</td>
            </tr>
            <tr>
              <td align="left">E2E-7</td>
              <td align="left">Load a page and confirm the third-party analytics resource loads and events are sent.</td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="example-architecture">
        <name>Architecture</name>
        <t>While the frontend runs in a Web browser in the user's side, it is delivered and served from a cloud-based backend operated by the bookshop, and it additionally loads a third-party analytics solution directly into the customer's browser.
The backend is composed of the following components:</t>
        <ul spacing="normal">
          <li>
            <t>a Load Balancer (LB) that terminates TLS, serves the static content, and reverse-proxies API requests to the business logic;</t>
          </li>
          <li>
            <t>a Business Microservice (BMS) that implements the shop's business logic;</t>
          </li>
          <li>
            <t>a Database (DB) that keeps the business state (catalog, customer accounts, carts, and orders);</t>
          </li>
          <li>
            <t>an Audit Log Service (ALS), internal to the backend, to which the BMS writes audit records of security-relevant business operations; each record includes the originating client's IP address and other request metadata; and</t>
          </li>
          <li>
            <t>an external Logistics Partner API (LPA), operated by a third party, that the BMS queries for stock levels and uses to issue shipping orders.</t>
          </li>
        </ul>
        <t><xref target="example-arch"/> shows these components and the connections between them.
The data flows are labeled F1 to F6 for reference; which of them are relevant for IPv6 testing is determined in <xref target="example-flows-sec"/>.
The direction on the edges points from client to the server of the flow.</t>
        <figure anchor="example-arch">
          <name>Components and data flows of the example bookshop application</name>
          <artset>
            <artwork type="svg"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="416" width="552" viewBox="0 0 552 416" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
                <path d="M 8,80 L 8,144" fill="none" stroke="black"/>
                <path d="M 16,224 L 16,272" fill="none" stroke="black"/>
                <path d="M 80,144 L 80,216" fill="none" stroke="black"/>
                <path d="M 144,224 L 144,272" fill="none" stroke="black"/>
                <path d="M 152,80 L 152,144" fill="none" stroke="black"/>
                <path d="M 224,48 L 224,120" fill="none" stroke="black"/>
                <path d="M 224,136 L 224,304" fill="none" stroke="black"/>
                <path d="M 256,80 L 256,160" fill="none" stroke="black"/>
                <path d="M 288,192 L 288,224" fill="none" stroke="black"/>
                <path d="M 288,256 L 288,288" fill="none" stroke="black"/>
                <path d="M 360,80 L 360,160" fill="none" stroke="black"/>
                <path d="M 384,192 L 384,224" fill="none" stroke="black"/>
                <path d="M 384,256 L 384,288" fill="none" stroke="black"/>
                <path d="M 400,352 L 400,400" fill="none" stroke="black"/>
                <path d="M 440,96 L 440,160" fill="none" stroke="black"/>
                <path d="M 456,160 L 456,208" fill="none" stroke="black"/>
                <path d="M 480,160 L 480,272" fill="none" stroke="black"/>
                <path d="M 504,160 L 504,344" fill="none" stroke="black"/>
                <path d="M 520,96 L 520,160" fill="none" stroke="black"/>
                <path d="M 536,48 L 536,304" fill="none" stroke="black"/>
                <path d="M 544,352 L 544,400" fill="none" stroke="black"/>
                <path d="M 224,48 L 536,48" fill="none" stroke="black"/>
                <path d="M 8,80 L 152,80" fill="none" stroke="black"/>
                <path d="M 256,80 L 360,80" fill="none" stroke="black"/>
                <path d="M 440,96 L 520,96" fill="none" stroke="black"/>
                <path d="M 368,112 L 392,112" fill="none" stroke="black"/>
                <path d="M 416,112 L 432,112" fill="none" stroke="black"/>
                <path d="M 160,128 L 248,128" fill="none" stroke="black"/>
                <path d="M 8,144 L 152,144" fill="none" stroke="black"/>
                <path d="M 256,160 L 360,160" fill="none" stroke="black"/>
                <path d="M 440,160 L 520,160" fill="none" stroke="black"/>
                <path d="M 288,192 L 384,192" fill="none" stroke="black"/>
                <path d="M 392,208 L 416,208" fill="none" stroke="black"/>
                <path d="M 440,208 L 456,208" fill="none" stroke="black"/>
                <path d="M 16,224 L 144,224" fill="none" stroke="black"/>
                <path d="M 288,224 L 384,224" fill="none" stroke="black"/>
                <path d="M 288,256 L 384,256" fill="none" stroke="black"/>
                <path d="M 16,272 L 144,272" fill="none" stroke="black"/>
                <path d="M 392,272 L 416,272" fill="none" stroke="black"/>
                <path d="M 440,272 L 480,272" fill="none" stroke="black"/>
                <path d="M 288,288 L 384,288" fill="none" stroke="black"/>
                <path d="M 224,304 L 496,304" fill="none" stroke="black"/>
                <path d="M 512,304 L 536,304" fill="none" stroke="black"/>
                <path d="M 400,352 L 544,352" fill="none" stroke="black"/>
                <path d="M 400,400 L 544,400" fill="none" stroke="black"/>
                <polygon class="arrowhead" points="512,344 500,338.4 500,349.6" fill="black" transform="rotate(90,504,344)"/>
                <polygon class="arrowhead" points="440,112 428,106.4 428,117.6" fill="black" transform="rotate(0,432,112)"/>
                <polygon class="arrowhead" points="400,272 388,266.4 388,277.6" fill="black" transform="rotate(180,392,272)"/>
                <polygon class="arrowhead" points="400,208 388,202.4 388,213.6" fill="black" transform="rotate(180,392,208)"/>
                <polygon class="arrowhead" points="256,128 244,122.4 244,133.6" fill="black" transform="rotate(0,248,128)"/>
                <polygon class="arrowhead" points="88,216 76,210.4 76,221.6" fill="black" transform="rotate(90,80,216)"/>
                <g class="text">
                  <text x="316" y="36">Operator's</text>
                  <text x="384" y="36">cloud</text>
                  <text x="440" y="36">backend</text>
                  <text x="72" y="100">Browser</text>
                  <text x="308" y="100">Load</text>
                  <text x="72" y="116">based</text>
                  <text x="188" y="116">F1</text>
                  <text x="308" y="116">Balancer</text>
                  <text x="404" y="116">F3</text>
                  <text x="484" y="116">Business</text>
                  <text x="76" y="132">frontend</text>
                  <text x="280" y="132">+</text>
                  <text x="316" y="132">static</text>
                  <text x="484" y="132">Micro-</text>
                  <text x="320" y="148">content</text>
                  <text x="480" y="148">service</text>
                  <text x="100" y="196">F2</text>
                  <text x="332" y="212">Database</text>
                  <text x="428" y="212">F4</text>
                  <text x="80" y="244">3rd-party</text>
                  <text x="80" y="260">analytics</text>
                  <text x="320" y="276">Audit</text>
                  <text x="360" y="276">Log</text>
                  <text x="428" y="276">F6</text>
                  <text x="524" y="324">F5</text>
                  <text x="472" y="372">Logistics</text>
                  <text x="456" y="388">Partner</text>
                  <text x="504" y="388">API</text>
                </g>
              </svg>
            </artwork>
            <artwork type="ascii-art"><![CDATA[
                                  Operator's cloud backend
                           .--------------------------------------.
                           |                                      |
.-----------------.        |   .------------.                     |
|    Browser      |        |   |    Load    |         .---------. |
|     based       |   F1   |   |  Balancer  |----F3-->| Business| |
|    frontend     |----------->|  + static  |         |  Micro- | |
'--------+--------'        |   |    content |         | service | |
         |                 |   '------------'         '-+--+--+-' |
         |                 |                            |  |  |   |
         | F2              |       .-----------.        |  |  |   |
         V                 |       | Database  |<---F4--+  |  |   |
 .---------------.         |       '-----------'           |  |   |
 |   3rd-party   |         |                               |  |   |
 |   analytics   |         |       .-----------.           |  |   |
 '---------------'         |       | Audit Log |<---F6-----+  |   |
                           |       '-----------'              |   |
                           '----------------------------------|---'
                                                              | F5
                                                              V
                                                 +-----------------+
                                                 |    Logistics    |
                                                 |   Partner API   |
                                                 +-----------------+
]]></artwork>
          </artset>
        </figure>
      </section>
      <section anchor="example-flows-sec">
        <name>Identifying the Relevant Flows</name>
        <t>Tracing each end-to-end test through the architecture shows which component-to-component connections it exercises.
<xref target="example-flows"/> summarizes the resulting flows.
Crossing the tests of <xref target="example-e2e-tests"/> with the architecture of <xref target="example-arch"/> yields the matrix in <xref target="example-matrix"/>; its populated columns are the data flows relevant for IPv6 testing.</t>
        <table anchor="example-flows">
          <name>Data flows of the example bookshop application</name>
          <thead>
            <tr>
              <th align="left">Flow</th>
              <th align="left">From</th>
              <th align="left">To</th>
              <th align="left">Scope</th>
              <th align="left">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">F1</td>
              <td align="left">Browser</td>
              <td align="left">LB</td>
              <td align="left">external</td>
              <td align="left">Static content (SPA bundle, style sheets, images) and API requests, reverse-proxied to the business microservice (HTTPS).</td>
            </tr>
            <tr>
              <td align="left">F2</td>
              <td align="left">Browser</td>
              <td align="left">3rd-party analytics</td>
              <td align="left">external</td>
              <td align="left">Analytics events sent from the customer's browser.</td>
            </tr>
            <tr>
              <td align="left">F3</td>
              <td align="left">LB</td>
              <td align="left">BMS</td>
              <td align="left">internal</td>
              <td align="left">Reverse-proxied API requests inside the backend.</td>
            </tr>
            <tr>
              <td align="left">F4</td>
              <td align="left">BMS</td>
              <td align="left">Database</td>
              <td align="left">internal</td>
              <td align="left">Reads and writes of business state.</td>
            </tr>
            <tr>
              <td align="left">F5</td>
              <td align="left">BMS</td>
              <td align="left">Logistics Partner API</td>
              <td align="left">external</td>
              <td align="left">Stock queries and shipping orders towards the logistics partner.</td>
            </tr>
            <tr>
              <td align="left">F6</td>
              <td align="left">BMS</td>
              <td align="left">Audit Log Service</td>
              <td align="left">internal</td>
              <td align="left">Audit records of business operations, carrying the originating client IP address as data.</td>
            </tr>
          </tbody>
        </table>
        <table anchor="example-matrix">
          <name>End-to-end tests crossed with the architecture: the flows each test exercises</name>
          <thead>
            <tr>
              <th align="left">Test</th>
              <th align="center">F1</th>
              <th align="center">F2</th>
              <th align="center">F3</th>
              <th align="center">F4</th>
              <th align="center">F5</th>
              <th align="center">F6</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">E2E-1</td>
              <td align="center">X</td>
              <td align="center"> </td>
              <td align="center">X</td>
              <td align="center">X</td>
              <td align="center"> </td>
              <td align="center"> </td>
            </tr>
            <tr>
              <td align="left">E2E-2</td>
              <td align="center">X</td>
              <td align="center"> </td>
              <td align="center">X</td>
              <td align="center">X</td>
              <td align="center"> </td>
              <td align="center"> </td>
            </tr>
            <tr>
              <td align="left">E2E-3</td>
              <td align="center">X</td>
              <td align="center"> </td>
              <td align="center">X</td>
              <td align="center">X</td>
              <td align="center">X</td>
              <td align="center"> </td>
            </tr>
            <tr>
              <td align="left">E2E-4</td>
              <td align="center">X</td>
              <td align="center"> </td>
              <td align="center">X</td>
              <td align="center">X</td>
              <td align="center"> </td>
              <td align="center">X</td>
            </tr>
            <tr>
              <td align="left">E2E-5</td>
              <td align="center">X</td>
              <td align="center"> </td>
              <td align="center">X</td>
              <td align="center">X</td>
              <td align="center">X</td>
              <td align="center">X</td>
            </tr>
            <tr>
              <td align="left">E2E-6</td>
              <td align="center">X</td>
              <td align="center"> </td>
              <td align="center">X</td>
              <td align="center">X</td>
              <td align="center">X</td>
              <td align="center"> </td>
            </tr>
            <tr>
              <td align="left">E2E-7</td>
              <td align="center">X</td>
              <td align="center">X</td>
              <td align="center">X</td>
              <td align="center"> </td>
              <td align="center"> </td>
              <td align="center"> </td>
            </tr>
          </tbody>
        </table>
        <t>For the purpose of this example, the scope of each flow is classified following <xref target="complex-apps"/>:</t>
        <ul spacing="normal">
          <li>
            <t>F1 and F5 are external flows for which one side is under the operator's administrative control (the LB for F1, the BMS for F5) and the other side is not (the customer's browser, the LPA).</t>
          </li>
          <li>
            <t>F2 is an external flow where neither side is under the operator's control; the bookshop controls neither the browser nor the third-party analytics provider.</t>
          </li>
          <li>
            <t>F3, F4, and F6 are internal flows, fully under the operator's administrative control, and thus only need to be considered in the connectivity scenarios actually planned for the deployment.</t>
          </li>
        </ul>
        <t>Note that, even though F3 and F6 are internal flows whose transport only needs to be tested against the deployed scenario, they carry the originating client's IP address as data and need to be tested to work correctly for all relevant address families as discussed in <xref target="addr-as-data"/>.
For example, the ALS's handling of that address value (storage, comparison, and rendering) must therefore be verified for all address families and representations, independent of the connectivity scenario used for the flow itself.</t>
      </section>
      <section anchor="example-derivation">
        <name>Deriving the IPv6 Test Cases</name>
        <t>The flows identified in <xref target="example-flows-sec"/> and their classification are used to derive the IPv6 test cases:
for each flow, all connectivity scenarios from <xref target="scn_combinations"/> that can occur based on the deployment assumptions described in <xref target="complex-apps"/> are applied.</t>
        <t>For the bookshop example, a Dual-stack public edge (i.e., the LB endpoint) is used while internally IPv6-only with NAT64 for outbound IPv4 connectivity is used.</t>
        <t>The internal flows F3, F4, and F6 are fully under the operator's administrative control.
Following <xref target="complex-apps"/>, their connectivity only needs to be validated in the single configuration that is actually deployed; they are not multiplied across connectivity scenarios.</t>
        <t>Two of these flows, however, carry an IP address as data and must be tested with all connectivity scenarios that might occur on F1 in the data.</t>
        <ul spacing="normal">
          <li>
            <t>F3 carries the originating client's address in the <tt>Forwarded</tt> <xref target="RFC7239"/> header the LB adds when proxying to the BMS.</t>
          </li>
          <li>
            <t>F6 carries that same address where the BMS writes it to the audit log.</t>
          </li>
        </ul>
        <t>This leaves F1, F2, and F5 for connectivity-scenario testing, plus data tests on F3 and F6.
Each of these flows can be exercised either through the full end-to-end test or in isolation between its two endpoints.
Running everything end-to-end stays closest to production and reuses the existing tests unchanged, but it couples the flows:
one run fixes the browser scenario (F1, F2) and the logistics scenario (F5) at the same time.
Testing each flow individually avoids the Cartesian blow-up warned against in <xref target="complex-apps"/> but may be difficult to build as a test case.</t>
        <t>This example keeps the end-to-end tests for the browser edge (F1, F2), where the browser genuinely drives the flow, as well as for the F3/F6 data handling.
The server-initiated flow F5 is tested individually, as it is largely independent of the browser scenario.</t>
      </section>
      <section anchor="example-remaining">
        <name>Scenarios and Data Tests for the Remaining Flows</name>
        <t>The connectivity scenarios to cover for F1, F2, and F5 follow directly from <xref target="scenarios"/> once the controlled side of each flow is fixed to the deployment above:</t>
        <dl>
          <dt>F1:</dt>
          <dd>
            <t>The server (edge) is Dual-stack, so vary the client/browser side: IPv4-only and IPv6-only-strict (base cases).</t>
          </dd>
          <dt>F2:</dt>
          <dd>
            <t>Follows the F1 browser scenario; even in the case of an IPv6-only-strict browser with a IPv4-only analytics provider, the shop must still render (see <xref target="web-app-considerations"/>).</t>
          </dd>
          <dt/>
          <dd>
            <t>Whether the loss of analytics capabilities is critical is a business decision.</t>
          </dd>
          <dt>F5:</dt>
          <dd>
            <t>The BMS is an IPv6-only-with-NAT64 client, so present the server as IPv4-only (exercising NAT64), Dual-stack, and IPv6-only-strict.</t>
          </dd>
        </dl>
        <t>The data tests for F3 and F6 do not need their own connectivity setup; they are driven by the client addresses that the F1 scenarios above produce.
The IPv4-only browser scenario yields an IPv4 client address and the IPv6 browser scenarios yield an IPv6 GUA, and each must be carried unchanged into the <tt>Forwarded</tt> header on F3 and into the audit record on F6.
For every input, verify that the BMS parses the header correctly (F3) and that the ALS stores it.</t>
        <t>In case the Logistics backend (F5) is dual stack, a trick from <xref target="strategies"/> can be applied to avoid testing against a mocked endpoint:
Point the BMS at a controlled DNS recursor that can filter A or AAAA resource records to simulate IPv4-only and IPv6-only servers.</t>
      </section>
    </section>
    <section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>Thanks to
Andrew Yourtchenko,
Axel Schemberg,
Brian E Carpenter,
Holger Fuessler,
Jeremy Duncan,
Jordi Palet,
Michael Perscheid,
Michael Richardson,
Nathan Sherrard,
Sulabh Soneji,
and
Tommy Jensen
for the discussions, the input, and all contribution.</t>
      <t>Special thanks to Jen Linkova and Timothy Winters for advise on how to shape the document and finding the right set of authors
as well as Mohamed Boucadair for numerous fruitful discussions and suggestions.</t>
      <t><xref target="example"/> has been written withe the help of Anthropic Opus 4.8.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA8V96XbbWHbufzwFYq8VS9UkNViWbVVyE1mWutRtS4olV3Un
K7cKJA9JtECAjUEyS3ae5T7LfbK7xzMAoMruzl1RD5ZI4Iz77PHb+wyHw+ju
KH4eVXWST39OsiI3R/HaVFG1TMr65782RW2qozgvolV6FP9HXUwGcVWUdWlm
Ffy2XuIv/xnVaZ3Bi08+mEmxXJp8mtRpkVfxrCjj86u7w/jGVHWaz+NiFh+v
Vlk64QeeRMl4XBoYwpN0dXc4TFarYc2PPommxSRPltDstExm9TA19Wx4d1is
qmH72eHeblQ142VaVdBqvV7BS+enN2cRdGPmRbk+iseTVZSuyqO4Lpuq3t/d
fb27HyWlSaDry5UpZcCwCvH7JE/mBmZRP4nu50cx9RndmvV9UU6Pojgexud5
bcoCXxunWVqv6cO3ZpUVa3yP/rSt8hu4CmdJmjWlcR9UprxLJ/zBj0mWTt0L
3jLFU3NnMuwuiu5M3hgcxDytF834KKZluZ/zyuzIUtVm01Lhm2XRrGDaNAI3
9ydRlDT1oiih9SE8FsezJst4B64WMM3VKr4exTepqUxG3xflPMnTX+n1o/j6
+Cq+PqUvzBImekS/4lRW/Pa/1vTqKDd1+6sRf/WvVbIaAQV1B/DHdWbiy8Zk
malr09P7xzy9M2UFe4E0dmHu4x+S5apapKXp7Fb8LhlX1IZS38eLH4bnl++8
wce3hfb2r2mRjZp8MTLTpjuyNyaPr5K6pm37/z6q8Yq6CoYU5UW5hA7viC5w
V4eXF+/+DEdg+HbUPjVFniG1nrw7vuk8MMkSnEaU5jO/xQ9nJy93Xx2M06rz
RjmbyFfw3I+H7y+vrjvPHC7x+FAzh3sHh8MN7eh38uTL/YNhs4LzYLyHD5dJ
Ts+6b+Hx98fX//bxlB9j+q8mizRPfk2Hy6T6a2OGq7L4RLO+GJ4cnwz3d/ef
M3XWSTk39VG8qOvV0c7O/f39aJJMRvPibjTJd/C54e7Bzv7LncnPe4evDvaf
v97d23/+Yu/54cvRol5yG8z78OH4p6K8jY/LMsmZgRADPGvKemHK+KoslgVx
wXfYLYwyAaKmU+hYB3Eg7+xTF7wMMpzh/kv48OP18PL9m+H74f7ecPdldzaV
TOd+AcxgUTSVwVnt3K+GE+CQ0NFOA10m0wpnubuzt7cjTY1W05k/L/kYzupJ
sVzBgcAJwHziG5glUDbyp7pgaoaTjbMEKVFk8Y9I+PDlYbyFc9ymRoHhwUlH
AlP2AEekNtP4uoY5ViQflvDMJIkvZzNgjfiJY8i0Om+aKU3zvVkWMIZps6Rl
/sHAbPDx009m0iDx4rKCFMMXmbMfz00+gf7DRd0d7u0N917Dh29Ph2/Ob4b8
2cGRvwxvDBBV1lRVfFGOYl6zA1iUf29um3xWV7PELNK5gTNe/wrTK5MKBM1t
Ddw+j5NmFr9JqrSK72A9Zk1+Swx3lvI7S6KBjTs4SYvRuMmno6nZuV6AyJq+
LSbA6Yv7nDfwJzOudk7OL3fenu7Aw0N8eKeqTWPKBmRjWvMnY56BqSrzMz1W
JOX05z8W5zdviAZ+3jv42c4SPs9nBgb/68/nN/AxTKEuk3ltLHl0d9K+AvIK
xP7N0Hstp88+QOegPAiXy/OiFj55WaZzOLFZnKX5bQwLNS6LW3hpGMNxXAB5
TIrVOk7ugAcmYzg0SW2XqEzuRywLgcZLIW4UIjvfKBl3UJXZqZO5ffYRhWP3
BT6Os52YaiekG7tELQrbQw7078PTi7d3B/0H9hbUrwn0dTCa/LrjU9/Jr2ay
gOVbNWNgDLD2QNBANAcxqFqxsEGvv4PhLvQnbOLi/PpmdH01erG7O9w/fHlc
7vV3nt9l0Hw1ytOqJl6Bv+AnO9UKRpVk3DkrCzvdVtuMA5+Ir/nV+Mq9G8sr
MJ27lDjEHuwzPU28EBjILM1MzwruP4cP05OsaKbDqzK9gy+HH0yWrPsnZLWm
EexcZogm7tKpKaqdFbwEh2s6gab3dvZAGzwM1hsZsIGu3kFXsXQVU1fx1k8/
vT3B17ZZ2J4VRX/3K9CgbyvUdnZgS2dF4XfAL8K8k/hkAXLB7JyBTjArPsXm
ExAwLUu9ADJPplPkXXE6YT6b5lNcRxPfLwxJFWTFk6YskTuugE3G9wno3aam
Y9NUyK2JUkQTH/HZU0WP1TD5FxY3B9l8NQKOC0O3n4oOmDSZ/eInGG0FzOj2
Ecmjj4xAJwpW174MA57cgswAHjEB5RaOx/D4w+l1f5uTIfC+qtMYv0IruSyA
yeTx24vreKuqm/F2DC8UGWhgwFfGZVKuB/F9mdbIjtI8PoFmrk1m8rRZbp5G
JU8A+70LOtZXY+C/b0vU8+Dbi9+fX/xphPMZvnix398qfjvKgd99osnQbzt1
iiuxAy8FZwi/i6eFqfJnwPIK0PRiIKgR8iOg53w2SrJsNE0r5Io/46dRNBzC
Wowr7KWOopsFcFOwpBoSn6AI4Qmo4nkDtgbwLpKcSZ+pwRLzupjV97Duw6Qa
JsNrNlfireskud7W1uBReHFR3CN9QltlATybz7KwS1ztt02SDcHMnNySPnDw
O1IKBtQL6ayomcbVxORJmRZgXKb5JGum+PYT+z00ALpB/cQ9F98D7y8a1AzW
ICVyYKAg+lGdrgsYOB2eNdBBZu4SWABlmqsiBSmBy2Pc6iRZVcSwmBMQgLBG
aMrCxMCqhHYnZiUW4hh7w1M3NfPSGJw0KFkwYzGlYMDXaxC/S15BprwU24Nj
rBvDywP2KsjjOLlP1hE+az4BY4IzqF2X2APZtBWt7V2RTvHg4zahwiiHG+zI
ZrUCwQoTou1fptMpcNDoKaplZTFtJqRKRmcF84sMtBPgqmDoJyWsNCwlcGdo
yyMEz3ZfIEOBNaqAocCgJoX5BJIBJR8tPq8pDh9osbgn9RDkJyhvOGawdWa1
3QtqT3cMjJzk1vEnNURHTLN8aqjzyQL16SlSEepz8bShVU9EB0GdL6dXQdDA
kjWZzACshSlvSIXaJcwTjhW+AC8DlU4Mt4krUofKLAwTlmU0HyEZRidoTcQP
D5758OXLgN7bqL0+PIQaOr7wewNWFVDjw0OoMOB3uH7YYEvSQ6eiMXz5Mor8
vYanG5iigXHHY4OTRJt0jerlRNZC5gY0R5sFo7Nb5c8XOsyLrJjjyvCRxtZa
Z4laotdV08d9MiizSjMIKQf4BZIyvA1LA6/qkHBzgAwyIGkcjCfB1vQOURgM
Gs4J9sQcweR3aVnkeEChG5+NBN8gG8s9RhJ8SWQKTyjl/fbc4hugL7AigRvC
t2nVmmFueGZjEwPfT2cp/JnM8egiF8mwwco4JiWMRvRXtvZ5N9x24ry9Lgbx
DNSCuFpic8gOYNeGcEiR8ouMSHjRgLSfkDY0TnDpgHUBexw3uOzBcLP01sSn
OLdVmVaoyVRFUwJJXGWgheNub51+uNqOK+ZbAzp1CS5ThfydVO50uUK+VTBN
Vc1kIttIs5haA3YU/bQA9Y3X9PTmjKRXDKo+PDPD8U/QjExJ+KB4gN7AMqmd
DoPsEYRMFRObITaEbY3NIrlL4Q/oEsw4GFXGXecFCrSHh3/5cHby6sUuHBSi
8JOmqkGvKuNTsBbjrZNT0AZg71FaPTw4lwadPZAiBpY5YaaHo4qvz69kVYOV
5G5e7O29wvP4Q3EPBFIO0B4hLpIu6ZihksFmsid8iWHQyYBp4YrYb6CTDUvg
5CoNSk9M57QBJ52uafDe+Qglq3cgiB7hWKZEqTD2ebIahIP9dk2BCDF44KvV
A2BsSB3VBIgXuTOsJPJ5oq4kOBZAyTMzWU8yw7owagjAfVj+4ilpcn3SaQjE
Xyo4+NnUknR8J95WlHp8cJkHu6Yelb+glneFLxM+sfhNCwUCf2l40XGawGru
0WWkagH1xLO+vB60ZmQ1iYAZAZ8A9RxbqYgLmuXYTKdAUqBK1OjHQxUJNhpk
6FSOZSDsPMFMn8PKw/5noCpnIJ7X4dCQgbJUAS7iOuYelglwmRR2MkXh32R8
dlsbaBeD9CY4JwbXElc5niXLFFQ8sHDMClQ0pMIJnG1qZWYS9KVUyHgWeFBJ
1wATD9Y6S4mL4ChhT3gbQZzNibIijTx06BOEXYFqXsK7KTITdI0M9Pq5IbbA
E8UTVq9X8B4KWORfBelCM2DBOYx9WrEQKZoK+qYNXKaTsqCRLBP4Tfz8yNVh
R4jomA+aTwHXZgbM9FGavzZoKAGZo9KLCkxID9h6UYKdhxtEn1jH0wQXCwfF
WpUZRaeq48mU/HWA51zLwMDQYCKCsEOYwBKAegFdJtkaHVkwRTg9STyDXags
FblpjoGwjcl5sXLkOaLiyJNo5Za43vqKz4RtL/fEMGkoQiQGtToQnhPglfjo
0tQJDgQ2+pg5ByjrK2LC7SmCrEZehsx23WJ25K+t/gaJqwIzQvmG701hPCk8
rFbENKYpMI8WG4ROBc7UG6AnS3ASQFamzEi/hxEnRGp9DNQ/WdbWknWAw2m7
gvdp34+itwVakml+h/POzT3LYKvsw841+DVMK5mGQgcb9ZTLSQHCalLneHKh
yzkYwECA8Bl6i8j7yp22jjcredhdQMwjUL2AynB/ddO9LcflI4WdVhS2Hbd8
wAynEkrncADzN5oSGh+iW1m1NyAlo3pZicEVXHEesk8ZSOoc0eGOZwXyneoo
enggdYbYBigRKFhqMt1IV4GJxN731LcTSLQE9QLUkfnCGpPS4whaLsZ/4SXE
hruC2Ntr9yR1MQX9IxdxhSxEhN7YWLnnK9jOPJ8koNyl8xw7J2Zi0BigzoFo
0HsuKgnsu77jnqPdrExNHzcrOYU6Wdb6qNvWzKwd2KQZSVOk1NCwx7GCtTr2
tRcc5IwDqdiK0xtEaLNqa1XTIZy7BHmrvsNcOa2sQsl+ts2aDc4Yf3ermaBL
BDoYRWfotUZhCXNbhcOxBi0dFtGkLTe6NWaFawLCgJSODAmmgj3AhQDpN6yL
oZHOkU6fxicFHVpLT289+np46lMjPP0UdHzi3Rz8eAcMrknmhun9FvQhjGVX
8ZP3H69vngz43/jikn7/cPpvH88/nL7F369/OH73zv4SyRPXP1x+fPfW/ebe
PLl8/x7MVX4ZPo2Dj6In74///IQlwZPLq5vzy4vjd0/YTvVPXcJHGlY6ZaPF
kElTRbq6RE5vTq7+7//ZO4Cl/wfQyff39l7D+vMfr/Zeoh2Aqhr3Riow/4nq
YATbbZKSzgJy+2SV1klWkcyHbb7PiW2Pon/6FxIAw8N/+V8RreobPNknvvl4
rQTb9rUx4TNDYLZBRjpQZ/yEGERghVq6fxLBoFgLDSQYMou6bXMSf/etSpxr
P5M+iqL/+N97/8n/fxR/991FURs1fmHJhqegAxXl0XffxUgjsiQSyVZe7uYB
27Ks2gwGvUI1W9sPDzYQjZZSZA36o+goPiajLW4ZFHQO0fLMKfS8wZsH26X+
uyqUqcr67Vr67m9cmLz4Og/hoethBKNVezatPJ6OkgE6KUFqEwdhsxhUHdYi
gukPhOXA0yXTw3dtj+Z3dtADVKFB2ypJmlBjqHeSZK/pxYPwRZ16hdIQ9qlK
0b6eEDVUGx091lfne1p0WZEqkuyW9I1ynNboOg9MSX0QDyqqPvfA3OAL9gLg
UUVnZg40VIkzTmT7khmYigNvjaipCaqeqqCBpZxaxeM7Z9d+h3TjFpDJ7eL4
5vDgO+oFiM09/D9FbU6ZtZ8eIi0Ri5jw6UdkiDe5a54cLh3P7n1RgR0Wb5Gy
lKXEyHGxRavBZi/JKR3v7b5SB8jr/Rdfvmx/J+vdXeV8GjHZVmSqIasbr4Wu
JbDPGrT4HIZ20t6ZiPpW/39kqQ/Z99DXYODq131Ieg/Emj1kNA31+9IfuICg
VoxT9i/zbBE7I8t9+OoleXbfXlwfHuhnewf0GQw8K1BjUgW4WueohKfVKG5J
CushA8sZY8p1iqqs2lDkvEbri/xWipMRNxd9SR5V7v3l6z0gABn9HSxWIlys
n/KYNmAjv/NpdjP9/XfRHnS+/PupT3jg11MeUczfT37fIkw8GhyAwcUszfFG
gy2VTJX0p90rT9boqtGChfsGbIPFgPd4VwL9LasM2s476207E50CVU3rgxuq
poEq52UJ2vyctA5RKkjJ8QJ6da965Dx6trV4Kx2ZEVvCq4USk+hEoTsJWlSL
GB3gTcmHnGUgqUiufbVH3evbpABOQEtiywoGTnGbLrgBydez/iKEgMLRyzIB
sKDKlHqf9HTmBTSRRmiz2DSYpfNGPDjicSHNDqGaYlV1m8JJ1oIDIOfCEtU5
501B+8QZICMc8ccK/TqoUM+SCYIcgOTZQQiDJUU7YcM9Yd++bKPf7xbzxp/M
uNVavPXxfBtP3/HV+Tb15kBbrZ5kqMsQ1AWWG6qfHMcSOuBRCwgwaEOMffuk
Hy0eF8Cjk6YuEME4ER9cDhJW31oaDCim1ZLtKnUQXjpb+uGpZ6iSZylBaobW
VjDCSbrKzGCzA0aU4iS7T9YYm0PoE7Q05XPpaec4NFz3eRk0EATWcAfmBQbz
aENI8187B7INs1lrFrm808XJ+cjcrd/cGETurAVeZXsYxYbIkGSdtjjwIg2D
uE8faIX2hVero4B9Lyn6DCd+tCD0c6g3vm/k1LyNE1BY2z/qLUbhwgV8eNqu
j0h81ehuy7oyJBXRV3Hcr2zQibK+ZyvxnL73LF1x1GXrdiCQvkBJgzEgn9aT
bOCTwkA06MANIHLV7r03yGdVyzeMMGHEwqCzNM1nWYMR4FEP3MFCDtr+Reti
mllPdY8LHYcpb5pPvLwbdosdphI+dOHC0LOjZ7EVaxoSAg0RBfD5SgCm7kOB
UaCvrqnJBELp5gKRHpVxAMZbxE1BI4pHk08Qw+rk3isLdaSKS2jQdpe1FxPe
QuyFOCTT0MNpm7wzno7hLQdOKEuXKSkFKI77/Q7AreywgVnBkCb5z57SigOj
EInO137Be9u7W5vdhxT+UuLocA3FjPCWjKKLonZ8sVga64lWgxDoMyNXc+Ec
dLBQVnZxGxzjk/BVmt8hqIsPfyrCDmdove1V/IQV1ifsakKxaMondHLNLDMT
3vtlgYeKvYY4nEF3hRCzMzbqsRWvOvB1XgZdFpzdlTElnlb8N9662r/aDk/K
cMi80Y6sNOJd1YVkjYAPHZBdWiKYYEJ/40zX4q3mL2YoqN1+IdaQPdTf4UH7
zsU7kboSis79hZzuUwyu1gs+ujP4ZoyxYqRUz1dN7kB0NHGUlJkeRyorJ3Oa
nAyPLi9KygnCzjkKBb16xx199qL+Y7BA9M6tyhhQvYTRINIWqZYCfwKel4AK
Km3Exipj+bkX8lYzhfcQqVUBSiydNkgkpA5UUItuxMMLDbYCGai4WbrgjvsY
rIxSTh+ffxyUN2oeAA2OlJcN49XZdQeKCm8+zzqxFjjD/E6MZBpzrJYCbKAZ
pSvaWI6WFrcWw+DsY7IW2W4miT7quDjVcNWtQMVW0MIeceI+Hhwe/KltN7vp
ian58MA5JALK0OirIyY+66RHuVXnySEwlvhMk1YLQqzYx7ylFv7U1lU4RUGH
oYEJNPRRmX1/81EYGg0rcEI/PFyLaHk5Ohi9QP7m5kBcFFlcQrAbVF87GoHv
96L2iKthUGHIIHhyn4brzkDFgr1BmOOAaq2jGo/KCNIg04GZDnDwq7Q2naCH
wm34c4YpwAvK0dmBKl0SI5BWvY1SNCNyYBxgae5Al3LuPAZLeJgohSO6HaGY
8gQhMaVwZJaVckRpLcek9aomptAtft9moViqPTgc2JPncUnHBN6e8LL3SE0J
btBkAiE48rwp74//jF8WS8QVs0fesTuFMaq3KjjHws8LOsKB1GHlA31S2ZpV
q0U6TmufGYEWBDS+5MP1jFvc4WV61gdcgu0TAJIA9kp/OQh0PlUK7C6FbBZI
ta76F3xARGf1RdEtEP6D6BNcBXK08e5cM7QGE4lwc2FSH2uMYmhIEclv6/rm
48W2OpgOXmGIB77yXqGmCJqP61aAzsYv3nz84F48fHGI57G6TVcrB4JwhxA1
RFDGgIeuSdIUYI/PSe36HJ8wkwl/PsfXzLTbH59kcHhQK2WF6DM0cISQ3PbP
ox8feR9AAx7/8p90ZB98TG6Xr20glIQbG9jQ1YZ2+xvoMt1vmcKGsX7TCPq6
2jwwxx8eXcQNH9sT9TUj6Pu4v4HHxxoszWMNhE9+bQMPR/HTNm/gTIV/fnLS
Z0eEXI0NImKhTzhGreYea2nIu5dmmjJaXlxNV2XxCf7cjsHMSYMnoIn3baid
2obWUe3bd+h4Y3eIa6hGme7ZAbC2P9zcXKmppU71/ee7yD/i68uTP17Lh3uv
91+Jn58zUOFz/oVRGzjsUdRhmcUM0090eMilAibF6pk3wpIRyszwWCaT44Pd
JaH9phGDTQrkoiAwwU++CbfBACRMR9NxuA7aSrHnmPD8mzT/NZsRKj6tLTES
jxo/gxbWBKENsBo6/kCNZcAjY7IcMXGU3ooragt2IxLfl3guQhe09dGTY5l6
x/XZInXHesbRwnOvAFGRTl6Rb0rMf3p3m3718E6tzqz6yT2JrsIietBvWyv6
mJGLG0XPFTXY+bgjkf424RN+9M3ip/P0twug3ia+TQR1nv6bmggH9+1ybNNE
vkGSbZrItzXRnohyciFNZuFvfPoNT1v3aHvM3Hl9tHTHlyhg7xd4pDDnIGuI
S5+ToUBcgFhvwB/BpKaEQ87da9R5Oy6KGn1tBC9Ly4BtDaKUnGXwAXAN4Zh2
dO3GEjqwVejIErhrMsWYVKWuQ/JYtd8XM4f2ZJnk6Qw5IPr2gIMlFC/uZajo
fGFnElgK6Zxs7/FaVOEfYAnW8enajIHRVQpier77AlkaGQiCsf5LU6FFucIZ
2mjxhi7bHnZ2Am6YTns/HRt6Cjv5HiurwDgxtRJrvAATjWSNEnVfaOwQdwLF
F6kOHgjTd9MEm3dMcSP4oeZLzU0puR8bgrXtixG4lDGJoiBJYZyt50XU4G1J
JkcYL7ywHaGJpp4L2HN0djtngu1G2h2bSYI0CSQ2L9DvltXEqwm5uMasU0q2
GxefXMRf007ZVcUiBTd/gbAz9pLiNjBMWGx/lETyngWHxktcEXGZvDzcR3UD
XzafErSwRroH07B8RE9MSeVNLeqEsZk1sFu3iEFEacnrFO4Ou8+VK6R4QBvC
wW9wuATJW+2srBapDKKOWZpxKotidNl54HmbW0I2GcPyCZGe5xKqEjIVOrL0
eu4lFoggt4ClzsA4V0dIDeZwzAUkkEpbFBrTG+rgZn+FySoziJiAMKgCZJhN
KXiBCVcYqfbypci0FmBAsHQdxu0cgMGmhAFHdKNLo13PKKHL1LtLUYxpmIeH
ZIrkjquDfp4QIha4z3q5zkBn8jW8LSbkw1r3NgeLw50BVQJhRFNSHONkhn4h
TLKCwzeKTsXTmK0tj8go7EWTRGTA9I4zo73IaZA27/wTU8rtx3cmmOnL5CyN
Ii63pGR6owCzji/HVwco9k44OS8H0vrM9JQJKTGP83J6xWkdEcpoy6qJC9D/
2XniZ3j5iQaiC2sk6AuG4yPmRzIuWVBhbIl0i1AJisP3bNbdPoOOeLu2R49P
XNJWkE5ygUSxEdLOBwUKFbehIMw5OzVYkhW6DwlypLApfIRblWe87B7n53+P
PLaF9JeUv4P91wjkSPPec0xeIDJWvEhuEETk2MWvpoQjZ3L0TqaMLhoTTMtw
WQE6OWnGHF32DyWNxAuCcAHxLeRWb01m5kmgHZ33cHGGYnWisHSg29AApw1N
C8xvEJHDqSh4xhzPfpzrqFRGiVYh+p6s393d3b0++H1bAFdhnvfmbtJcsmd8
+9aDA2iAmpLwyIE3ivxacl7usgNyiQuX5J0m6LLzrzNO2Y0WRcXvUgTGZLAh
GB3oqE8uvd8lm8CH/A4QCIMrgLE1pBdIyM/FX/08l9Z8ZOyOUaPOZ9AvgJj0
gGt3QnMuMV/Hohn6wcnojKgV2/gHe2pG8TUqwwHZbYnKROkfKD+3SWBKLhRs
lw0e6CCQdc5Y3tNpszyVHsXiP0PmWGFYXuGe/sI+JsbiXxGInaKkRxCY1bwp
sCAZRN2Jvn51oMnD7fVs0cYHw84YPBnviuK2WaE18+jehULWQmrkXEn2ToV1
aShuoq1n3LrLGWt5RvhF46D+apkuPY3d8rdZ0HYqmUgKZFHmNREgZdnklNAc
IDS6Z+Sd2zU09HAl+JRoquYvqq7SQ7/QZsi8FWyr+i4Ma/iGghdaauStaMhr
pwZj8YUIcxtzGia5ZxDw49MPh6xksfjN56/3NebYftSeB9bXWYtgO4ZjGTXv
0KqARR2jRAPbeN4UTaUx8KSqikma2KPHriGJbrepEQbNH4Eu+klP2S7WiPjv
5gDeNIn7DxgzMWmypGQxnZBTUGimyWrEttm05FThfYIHDfb9rTU/qRLcigp7
RV0ugdttlqjaeBZrbV/xIT0WsKy6V9pKE+R8U9glzsZVQ6iyAWh03vaFv4CW
CftKcIibkyvs9d8+np8Ibbzewyoc8RZ9/fEtYjew+E1/DQCSsDirKegB6TxP
MtsyvDrA5hm/dX1yc6UKhF2j+F2yhievzaQpUXHeunl3TcjJKoUjnSArlW8y
fLBylTFwTdr+EpuAO03WnNqkNkuxEg+tWmV9fvJnFVsveH7uUnMvCp6mzKlv
ACcsmhzGsTnIJ+6O39pJHj6bjIukJBqWs7AW7jVuqELQylaqGcVvxOrGrbI9
BNanaq2uhgtmzDNKCLZhh3b3a1/11wY5rdaLwvI1pE7SlNN6ACQM+zwnnKkg
LhVJ48BLQDaSy24hasCAc4lp85Isi5L1+WwdFlLB11vI8jDj0nerm0+mnOCW
UNERO1lRoFo7IQqKC8j7s+b6MwhXSDHPbGzCanu+A6ZinB7SJlklqJSh+lL5
HKkyfmhA9V5nBdix2nFuFaWOlc4DYpNiAidRrR9isysquscmnW2BYXp2qWEd
0csvsQ1BNfXwryvFWcRv2CLzQ1iD+P3NRz7FZ2UyX6qGJNp5/PC0A9OIOK5i
mWhXVJfeoiJmVsqfMazBRngck/RmwpAt9l8Qt8k1EOPhfcAkxiRsdmx6KeB+
I4Qjlq6mArHHj4lLC8yA/TqTYACW2kFkO7tbjo9vxFl3mPFR2UdRhBWSy4Lj
77i1Mvngcyed9GvVEJAR3FUjPNruK12/Ke2ryEe7fEQcebMcw1yxlyu2KNXb
gDQJ40U+MXDU47/E9TSCNLZqsjCo40Bzb2hFoDHbo+eIoKW/S7KGg0anJxfY
1ttrmAWoANmUWjjl9Wa3uhv3Fe7H++RTumyWLDeksDVVm4q3roA0t4NlIz/1
+cn7q3iJJt9c9EJreOEb1te4Dl6dCXUTnNJuyBvQGehN5fL2lGohDt0XfcCW
LWRPd7oinzV8AeKN0B/VAqxntGpZL/TyQtSTUBq2BHkfN2HahkOrWG7yj+Ez
eKSQ24BphoRp1bisqDq410EkCdhdICFHa5dJdcu9WjaPrl/NMWAXlCRpWo6V
M7CnfUTfkkuKrNS05wHmBSoPeAtxLdTXx8Bcg8gfv7KW0/6TWhCi8yxhzLcw
vRC4E9jCzp/KhtKElDjKE6facBITwAKr1TN1kbmSYoeDyOMJNgnHQxJSFo9g
uSzj7PM3I3uyQoJk5AxTYuhwWXf3hkpFlJG1BF60QEq8k3If7RpKckIrT8tl
aJ8EkWJNf6eQyMKgm62DcJq2wZusscrU4nEG3ywKrqmHcFoLIPTd2V+DTVU6
lEX9bUc/w6UlaSFnzkAyeNBeZxoOFVPB3nXTV1z/B20gzyAMUgu4EEcQiRiI
bzbRwmCYrogs2578eIf1bU17YmbD5UbGTOtJyCu4KYNuPtUGA5whkirXgSma
miCgDpkPVCrw+l5fMKjalHvHOGROteA6Ih0os82rEe2pIgOMUdlkSmKtml8d
psxQkndX3cBwERml74piRTzi2Dont/b2X4528T87r7b7TCjyJGpqF+FJtY6U
lBMjHscRpGSy8ErMKTwSHQncbdLfLWsN45TVC+a/BRVnLcp2uRalXWZwdmCF
p3WgUTniwIalkPjejDXQIuyZ8tQzLuEE3ZM96o1K0hYTUKm4sS5224kRqZ2U
TME4TklXLgQxOlkURWVYOWAawCXxc8Z0dUZWPsmZCbYB2yLftSus5BjvKLjY
QpiYrCUuq8SBejcjaBnYSllbJa4yrTo4Te4Uc1sIkzoQ2dTyIXgDabXGtSRc
a7jLZPEPZUtbB58C0PAuVvayRcDs7nMNyibXM+ZXlFrRPQfEwfUoS6WdQRiG
7xQgDeDB7U3Xs93KvCI235cxmQfZNcGpFNq1G2M9H+FJ7ibEotXgl3bx02PD
qi9fqOjexKb73IOAeDxnzdGnn1o6IDnsRjiIXColWyyc56irU+qdLAKYNory
DlPmXMJfULGnL9n3Szu91KsLtwn+EDTaBzC+8YK8dKFF5iUB9abTVqibg8BP
bJyYtXpvbXrmNyId1BkabAO5wibqVXawrJ50X/8vOryStxueGFEWJOGVtLIh
ZfK4U6OxOFwwemcH5oexJfWoRzG5YrkJWORyuqEJFKhY/rs0q6KiVFpTbVNZ
rZaON5BkI5oBymwEwyRY1NtFplw92jCxWB/2oGxe5S6X3Ns30IGecuiJKj2x
JPBA2Btg+BpTgE0B6wMdsIbHJyVJ/UyQIIENOhLHv3V9jOJAJqXoNu4ZLBKX
l+pq2VO+mRkxe5TgezfZ+mNAlzaxDI44UBj5lBU1TzQDFqgp0b9MFxp8QmMX
/XPwz/HVuVdRgK5yOddydWiV1ZNRHAA8Q6byrGodka1qe/D1h87BFrUGERaU
P7Z4UFytgKPnRT4EuS9+1LDr6jEW5SoH4hGYCdHquRb9lhIBHzt0jviYoEkP
4KIQVA5TbYAQM4QZNUv0s1c4u5YW0/+KG5pVqdlOCkMRNhpHKpUa153urImw
eeU4Yw4fwHspWqLmSycF/23HdeSDer1kfCcHxJEs9tUUCDDpYbE45KB2oU8u
2AT5CD3EcG9fWxeyqifBqtrLZLYuTm9OLi/ONKPjcG+fymZ/OL2mzxVDvXtA
QO3ri/dX+NH1zVtGTV0i7urGoN+3trGk1/vP6UvQHLNirrV9D7hlPEjbcSsP
lsMwRPLCAxlBAKxgPuc8UH/6QVJ+2VBaHAU6uTopGxDNNG2lgpNLIvY0NQ7g
YamQnrrT/KcN5NJlKVYnvSYqwZawgj+mV6H0phL2YeiX1A8XiPYKLzxOOe1K
DC5Fiz3TtiiHr8KMNlIMTLuPZjq9qNy0ZR74CXI+bar2sHE3fQ3vRLgw3TIS
qvR6MxPhlfD5+ITE3sPTIG81irSNjg3neUl6UByuxKwyNiol7NVZhUPXqckx
0KSGry616oycRIymQVvzZHuPm9Md9XDqVB1c5DclCpCXoRuoU8ca2waJSmnM
7yZMa1jpwoULlMxZWSaEpl0Frdlno6s+3hVO5W/U15DSKDO+koh1Ugyb9pVa
IBTgWh7WPamQbhmhYJebiZFq/g6dxMHbmYB7kxuubBVtRvwvovUGyguIlhfo
nrbbSswB72nRInyuaa6LgXaUDVG61BfNohDXjYyyHWXqmzG7G7XOUHjDAlPg
prq+5AvCfbL5/UIAHk6jG7nugW3bshkbE1O4uFGPnoiBxXqA6N4+kF+7eIiC
9MRP5OWpek62rgakcE09VLwsUrCI//DdUf1lRa13apszW/oyRwIsn11DLFbU
5JJoymgaRBJQf1qjkQ5JJWExzx0ipdfYK0YaH4U5uGBGH+ofdVTgijhAo5Uo
jtpOHWZkldwTY4u+s9NF/B+8ouHdDYrQok5u0xUtBGqLPmiVzYq8nWnjTzcs
I0yjI93Ebs4gBGP4qT1cstDk0x7Rho5uL/PcKyPqWlA0b9qpauIJai9tODqj
WLyqkBTxAnKQaQ02nrFWBXKvQjrBOLMCuWvVU5eR4Qk0Qn/NlFcIT6BDWNgx
Y3EbfOoELCJTpYmNzPuUUsWf2nq3N5J+Bs0oJikVTWRK81IpfO4KsWu2lJN9
xLNs5N5plwr80ELg/v08VmRIsY6OAxNdPbj79t4LZuS+ioYjDpjwqimpbrx/
z0VYBZ35X6ttcjVXJrszVkWqkhlfYzDPC65aAiPPWCIhrJ3Ez6aS27KT7V4U
J4aQ/ha+0BX1sDeWVHyfjlfURhg+qAg4KEHdeQ5ILr1tb80RpYk9IOoYBCvS
K8xFmGWBpmO5fk7D5MtDtND8gCGEgnvRUgv0JlKxVZf5NYWsHnqJ9KDB6VVz
LYccrshP1owKFLqHpxvMpyhyb7SSkxhCgqLd4odlRDbwL2VpfP/yCV9LiDDf
lMBsYu6A5Dh5e1Ftu1BCTdcmFQRxJI2Dwj5+qX3vghnpSTI6Z3T/gXA7W/y5
VQc9dF5QRG/Q8d3S9Eipc3N0+TXI1XdAdxJmHNxiI25Fj1drkR7Of4EPzGxG
+Ve8aAJT1LlXxKnmC0YT0SLTjcc0C9S8ggPBg0D7KJcqPG2Z2+QNefxHUZj1
yupvcN+OKCNUYBUvsEhl8Yjn0/1XKiUkhrVDqGpbOA8biah6vjilvTCiZlYx
X9Ql1QJm4cVLyChGqMlilb0x1n3E8CJtCe+6tyfrPFmKUGD/hvNkuackouxz
H4qpVnWHhIvSI98gN0gXTk+AvRqCkpXxzglBEXij1gwYhu9ipRS+MY/cE1zP
qn1Sj31W8xbJ/uFpYL3KPob3eHBEsp9VuWwH5XUea+/xRZD5vS15T8GHzEDJ
S6FsVgChfWAfCsYF4GqY9CXef6Q3jASUkXo1yfrh4sH9Xa30BpX3cMgKFHHZ
KD7OMLwxXwi+9MXrF/ugR1pPG93vpE/HfN8zK6OhkBWxIb4sQpXgjWLMJ8SJ
hlZqZuZwKJZocfuwcbcw1APVyiNseGUNKcoL3wiRDwA10pjaP5yPMU0p5ws5
GkG+litEKQqkDX6tF6AbYOk4z7GZe2tHEVu8IjrnEGoFo2uFLjUKZWfzy/7u
7t7RdPzq6GjvF/Xl6tWSif/9rv3P3i8D+XyXXqQY5wg/JZXVrgdHVanUpUU8
TOgyK6RcvlWPcAkE5q2Mov3oCLhppQpe6czPuXBddS9QcJBYsvUgkls0/fui
2MRz1/0oE9AiBHTQ7L0zQslejVtW1C21oYVRrtvkzda61eYWxdSCKipl7YgP
RK/4BmoZ6PajRNGVGKCOrdfuVM0YywM5WhjISVUB4i1grlegcSlNpWAijSqF
/sXdTCr0o2f2MNwXVLRh0T0kU5p3HbyWTTX1qtGIDPSil72RTkBjkgve/nB9
eTGI/3z8/t0gvrnE/8dX/vT+HfYUcAELmbHswB0MPlqiEj5+Nh0lIT65FXd+
LMmQo23hmEhHd/vQXrXcjgLnPIiSytXKBbu99/5HWpWNBX3VOcWsTVGJPONu
WowXvfSSYvz6sdfuQpSHp15ZyCi6SKyeJGJ04Mphen4YT7MRV5VnEnTuTwEu
SMuvoUeFuKPThuRcpzloQg/Qpozxc5fH7jOAQXC/i3PUqRzsBZDBl+OU7kmT
XEhCZQVYMQGWbKguGrrM7H1mxDAlY5Kx91J1CgwzroR207ntzs+Dn1ON3zbp
C0YM1w7muDFw7VwyWM5cqMS/DAd1ZGNUDRYTuHNfD9IsMNp0RvZQTwVDhfxQ
pXbSE5gzinYNtgavvmBwev03msG+1rvRAsdYSUDvFvpQcoK2WUHr2AtckESv
OpGbppacFwesH5EAiUsw1942otokrdXFK7gimriJp0ZDsYKUBAqYyAVGNgoX
oDgCqnbokYOY1zatFADkFaKlPpgTpFK7ILxmVHqy1/vhbIF33tbFKr681qs0
pGVNc8SiQmN8HJ8YWD5/nE9LTF8kWYf5ClxRj9UNfqOSV/piza3isCxH2HNC
WVACWpKsVHY/MbJtarVL6+6RnRKj2uEQrU0wagMlbLVQeI0zfpdYjoJihASt
Zl7sVkJuSsB/kN8uGY1MSDubVMpplLYeg8hqSfTtXJ0g7JfvWKA7k8cKVcbt
/Mlk2fA2R/f1VQkH91O89dMfr7b1rV2SNA4Bav0HnutpEP94deHQFc6GX+E1
8BMPeCHipe9CeujF8wBaokvkMspJYutd918iYAnXXbaLWXUY0Q49lQ7pF9Lf
UfSGQZXhx/6VaYsgs8/hG12Kt3clM1XaUqqHl1ASq0cs0BSF96vdbctnUO9O
93GEJ/XZEbpCGge3jdcmLrAWy4jhkI65B72xLUuObuJE8pLrXldchWSXTVD8
Kp3nQ/Lt+0xPCipVfrq/smTK5YjnRTGVRCsWSJ6U7Du/tsRIcIzTXGEtJFOY
C00yvJ+KU80Ui67hCgS9WHi8hOHIs8p3F3pufRltY1eoDY+VlJF09ltDtwUy
Ngwd7YbKCTpNpec7lJkS1kEfQE1TQgdOiRdQxqibId9UkfRn6ruKG64AqK8s
MpKOJOM9Jkd1Su2K+4HWVdTpG5aQmp8sC4Un9VnNsQ8+di4pqlOjLHxNIico
ednu6ilA0RK+WmjC2rxB1RXi9MGYVaqjhHQ6FTyJ6Guix87M9a7e1IYVvBlR
ZixrGpRushGASbFCuqKEBjyK3mixD4fFAhoTC2ZHxrlDmX7zLtahvXLtSgZA
78gSPC+oFNLxHMhstqSaIiZmAasmPZfsjmLZZzmS4pOgm+Z1HtwSQau9wnqH
6n85GHhCs0336hgSjYbGYbVBm/DOZVw0rQ/VKWkGnWjh9aBv1uSOcDe4eH42
FZqUkoFIFsrVYFtglTUwIZVVMOCzosBYKa7tXVoRGzctewBONdmVqdb78/am
G8Rt+TQDkvIvvyIfPRFh+8gdAx0Uc3byKk2LmPMqPFskv7++7K121atdFLzx
rhtQqCG0EiaRBC4+tFJASoAFKOa+15qU7A85sQM4+/lKUuGPHYj2OgVxLVtO
H4YlwgwTLmKvc1dnC0rOqhVqIoCIrV/uDxJpQAk/5BaJCH/2a1vJk1HMlO8/
EQXemlabZRlvq0QzNrDS/pspeuDOVcyqG11DZXJ0SGGEmVNFmJOWVpV+ePgJ
/c+LpLzF61dbbKODpA51el+MNSgy6GB7t+WmdaW55udyJ6x4+TR6Nmil/G5W
1cN6zh0CJBg2bAPhGRNKXGL3l+9235z40JkbCNlmpdlM1j4LvIAV3zEoHnzv
hFNKGQkR1BigPUEBKyUJwKGDiiBNnGBIQ06ZYv3aZnLxe7YyAv9pS3jSwfU2
eRTxfadUT+Y6vM6VSj1jk2f+da7vvetcH57a22Fbhr/WSqpsjXp5Ek1x4yX2
s8ra5Hb8vaA+vRhGs9pJvI0kf6d1z4UQT5gyaAsBBjm1mwtn/UtQOEvrBdAt
dulfGzHY/CtGlMTIsFKOyc6T0vjX3EqGDD6HAWmNAOgICXxkXRycgMALzyZC
EdyO6/LMKRicN1oRj0298doLdnHFH3iU6JPvisByAJrHyvzlNNesncP4jBNQ
498j3K+33oSkeqI3gyPr9J4U6vCSjhTAy+aIcX2MmGxAO6tsGucE63rT1VMV
a9sh/JfTviRmzTiQLvbaOiu4r2kYOnX3Mustm17ZlWOFFUj+LQHIfCzbuClT
qitnVi4vW3MknYPdvQBq/7QAo16wHYMQ86f50ECZFK9237AYEmgLnvVNZUmC
yfFb5hMQUbhyYnMp2gBaImTl+/B2sBO5K8cC6tEo03daN4npvToe2J50YVp0
Rd1uTDjqsX5jWPCc7xaSlCmtdSWyjLZHKxe2CrJtzAb6MrBcaIK74sFSE65W
6V3eEqLqeCepDhYxe+FcauN6siAoM4ilxmjaPCsJtcYYlZ0I2toqvIR1lQfO
qOQlSfQbLodn27D+GdtGks0Lirk5X/nhS0RUS+XMKkhg64RNtz408PHe9iCa
GpBWKbZFCioiw4Bzon0/3/Ta/vZAzBtD5W3894kaf//x2DcTxXo48IHPxE/Y
rUf1sqxWZEuguZJfA08ZORkefzilSz8c9+T7Onn2HibbYp813JuyvMD4IWv3
XnrzQC7uEWpE95lAfYhoyMYMKviRapd5F8IJmpBKIB28wrEMh5T4EvImsE5S
BtvZNxlB7aqR+vNBQat/DvlBQs07OeaZTzC5j++OgxvO3Am0meipl23rKh+J
bUPW7xuzLqROiVQN5VWQyCmwamvIyo3EZAW0I9osuO02JY/TsVePg1cyWARU
FGGmU8Kw0qK4hR6QIsHQmu5FfSQ+iVOiAoExIBZ9LEoo6Ywqzv3h+MdjrcWF
dME7vKIsLw3+4kozKXun0wNYYcbCTeE9eNh3DgaEJbUMvpIohiTWchInmIe/
/PLLX+AIj9AtyS1igxa58c912Rh4hpIIuuKZeKvWg5FLrjqVPm3tdGhnjsi+
aYlG6dY2/G3L7SAR+whf3DXgx8tVzX4hKlpk6FHOaDhuqwl0iYz4yTiJtQEm
FZOqaKuIlAWQ7JKix1mSzxsqr+HKoymcjyIZWC9MA8Zaia00c1EQLSS2h4VK
0sXF788v/hRv9XOGAZqYE6rHwwYDmn3Yxt6IvRJgyqIDg2XP3uj53jYFApBG
UdUm1cWv5mgVEstQldV/D/03GIWYStXvn9ER93PHE8fZxwJC5MJu4muEQern
DoQVx8dUJ0Aqp7harxvaV5tfi8RS3rXVkyRDnXQUr+wNf9WO+EjSjiS1T0BY
c56CWACiJesxHdhLGDRzAp2fpKOSQZHXttCHc1OM4PTTBo7QjBm+wGiDPQS2
gqbFe7aF2Iw0c3Rj5YWmvcfAeWtJ8q+c6s6hK3piyE+kVeAVxSq+uVXEd7jL
qYS7iBswu0VnPZwFrneDwwyL+1RwYOohBkQaa8pQVFFW226LuqV99VXByJo3
hs1woE22v+feJt8Pta2XEONxEp8Q8Ti891gu/6gbzHTV8pZ6VhE/w86OQAOW
elUsNDmjFCZhpZwqXJnf4eZyThLCWNUeAxIcnd7i5nyFo8hNg+orevc/iBLt
JUW4WhNaicmNiQnYKaueO9KzSlTj0acJNlq5SgSPjUkv7FCUF5WX5BC7Z1tS
81rfk9aVVtPGumxRNo5Pendibcj6FIwwiQYEwLItBQwf6AKvOkbWD/3BPzC+
Gf61hVqM6pLbXpHnAH7eW4eL15M8hGKB5Cvggz8yIkqtpUuC3sQfFJUS+TFg
V/m1dQuWj5SihUHlgC8DtwaRFhiX3KJKiNJvRcBeyEhtLeSaI6jJFGeGITNX
4sPZWpoJj4PmZDU/C+gEyc3HAgjwCCdKJVkZARNkrVIGuiJzGI/kxZSoGAkH
wazvTV4kdy1tq5a+0G+8jAZXxdH6xK21TZEXC5+kWFW3FqOjvmSarOQs05LY
XEJxgVJFSZ7rndtqtMxLzlzQmVSKXZ3ocqnM8aYGJI6Avt2jo53nv2zKZZND
pci2lu5F7ALNki3XElgxoC3DJ7MJffLyF7FrOOb+0x+v4LvDg6PZ7PUYvn59
SN9X7DbFJAxX9BPaMK+wjb3dX7bjEnUDiUh4D9HHovapSYqKVM7nwAcVJqX5
H6iJqggrWcp2eOjxpvh+Ra2OJTV25b4F8cpJBQngJk5oSY6Gt0y+ota+jJcO
Va83SvEMQYCFiKra4DZRUSjxcTxC1l4mKI8nc+mOKlcKl/Db9w4D4VVsPA91
ZTcMb86s9DrlW+Ju7oHGK7TRuhTKj3Xgsuqlvqm9lMEFFqt4GIV6Rq/Xq7KX
7HZWLin9Wx8ZPxu+iQQnrnJ1Xq+KjOsUlaLX1A20nKFe0i69LZQm9lJgX9Ms
V2VKWARSCO3dhoxm6xbZAkol+3otOkXwDPTBPnOhK/W6vOFSTMRl5GanN6xP
K53Z3B+1XtSqktoHXuoPcFKUIQT9E+y/XATrZ1nbDBybM63m5R0jRMYV12Jz
bRCtOGPJL2WuRh1ZJFW70nPLud0x0ZnKK9jHHpfPmm/TKUs87qDxTY3wxnYz
y0QKJHaGzpaLGzmbHYPe8ntS3QaBlVyHsdCiKiyWeeNsDAKLyLgimFxuhuLO
3D5orUGRXbAPS24XOadeByNZ8/bqkwZDZtYDSQEKOooL6CnMFdT0057qHT0Z
qKPIG6siBsEsN/e4L1h1pGzwqhFMdCwFLQ28oGSEgNRCw/AAe6W2mafSsrUy
jImSq6aEs0NGsKQ/o5LHPJDdW1gDrtL1sA6MsOawV2xS1Myf8TWJfC6AARY/
i6nhWD9yeXWQcWVUhO1Z5wdheS+9mkadwk4FJfe/S8YOzjnrdyBzDCKleHx4
OQsXzF3IXSewZCsKksBZp0ILEjZo75u7EEG/5QgM1yLsapeBLtLehsBJh5Uw
e3C3viVwa2CQXmorDhpB9aUhhzN6oRRFn1a3lc6njbr1gm/IvNy1U9S+vMQc
n9Jq1VNvPgFXcnd0+fdSBdt1PQHCjv8RjG3JRLa1uqLosRIWUoPaXVAOlpDk
R9fpUnbZRXQCTVuUBL70i4IOcuikUmZRzoGN/uohKfwTGH5L8XrGuXIjS3R4
JhbFQEuJkV3vojEP6yvh0aGGlux9PxYdwCcXbBObqIEDV2QLVa0p/VpL5hNp
rFPm8UH0IqCv1K5DmMg/nbaR4uiWtoni4rsSImZ9hV3uHEeZpZ+QwzVzV6w0
N/fZOpymzI70G5+RehUTkfLKZmVT2mV6ZUMw4MbaS3I4ElTZhhrlw985+QaN
HegVkRWrepjmO/gPvL6DxQOG5Azi4sABbEpCfURZzqftp4STzCcE8T8CBwDh
gEZ5eJ3EMEOqIXlODzLF5mu50Q3dmCicNJpk88vcXdSWcjmppX3iKYDFLIWq
S8oWELMSfuaXxhanYHAUgustueoiBdEVMgPfCwwUBrGUu1cRDfEDS8y8kMnh
nPCijtIVU5bT1DKdFAWf5n07jQ0HGkbSgvJ7wXQLPua7OARHhNsmuew6LNE+
FZGDgToGpevVVAu/Lnlw/bULEJKhCrSG0chqQSTArnlSsprc3p1Ht5w35CRw
Oh7BZQU3IEOjXbbUoCGHPuoP46Bcube3hKIEwx34uZuO00uK98QISHXCYyHu
AvEV5a314WCtBVG5ijV2z0e4MrOmJK7oQJi4OR7yuWemg3hucowJpb/2ICmw
xoEZIoVZfNqB7KDVMEizd/XjPX+dwbLeiS0cdGIj43Tlg4zlg4EJEALK18z0
8ia7m2KAlqaRgDEHhCQmX7VCxH7onYPEobikZfZDvjdaMy3RKtE5ISDDGjHY
OwHcJRVZQT+6rn4tC/ZVRkGM32NxIv4ctRIGWBK+HfJHw9lkJaj10dVTHPn1
DHMgN1lZH+LIJqWwUy3BL5uSAFWSHilawz2qsot0heOw6sKJqzdH5hXHdoLD
4kGmiobNEm932fclibhU0NFQOe+U4Mx8zw4a6KPo0oJm9P4ETqHA0stT5wQj
rS+juvwIm+BgUAkicTo3jE8k17WkMsPrmS0AUIWVf1C1tReOhHote4NUoaV1
mpL7OLggKay4zUkrHEPh7F+QzF79hqUPXCVTVb/rvVmk9ypk0id9Ee3b3TZ2
zAkOPt7CYr84Oe/8+OK4Z8b+bJA3g/ShJxUdDCuGNyGjVMdWTtlBiSp6md5Z
cvBqgHFlE8TkenIbbAZxbSoSjWDL0/RTnGZZw4gqyTxbKOqvyIr5WsvjulEq
gAxb1wL56FEpyQ/ni/LzmksIezdQh/UfKZiEk+gYaKQi0pV7XErZr38TEbxP
4YL3RXCPS+Da83DafaVsOndvBdXTvtCdoKD9MSAXfc53pnL6lKdSMlFk1mL6
WwpGUc2qGWV800GQ/WJwewZjLElNASNlVXN6xffEWJKsBezKMj7MZN+TH84v
kWVL2MhKO9bMeRTkCVwWOZOERw0DxeRpulDirjKgpUAGMWoTV+Ug3HdawRia
PG5ZPbjVp0wD8A+Rc+VoFvfjS7gqLbSuoIjRewlneMWXcI2L4hb/GkUnojez
YypRtLqghGFbSNEh9kff8CYC8cAJGGjpfXZ9ppwnIBwRESXllPQDGp52aVUs
ZbpUpq5BmESYDtsmfNoOubGG4RzK2HybEyuXqN5ifdC/VaDHWzKMqVPyc8mn
EtYhFfLksG8fkROLo0MwxasXdW/MPigwOFo/mzshlJT5tAAVkCBLpLSihoQw
JZlp9Jn5Ft4XTueQIzd/74+7a37D5fJ/R7un+6fDPWj3ndRAYWojAgJtYG7k
spM2DY2+pt19aPfaIKfzX1Vsay4E/azSuymxv8ca1nafQ7uXrgH/dQI+E5yE
apnVRYvOe5vXdvG2+Q9mnlZ83QIKXmufSnE4Nn7TOQIYHl0Dv90X0C4oY3yW
LKwh0cuk2MjJ+dwNSHxLrjnoUaRsbmj3UNeBmAW+HQOvAuVHKtaUCaPFbUMo
vOpGk7isrKJXR67dl0oPiSMBCn7L4fJL4bjiQhZeguV0pCbnnYXoVzSPz9HD
Ufy0c9BA/6oz889PTjdJT7z1Hm15T2j6zNT7+Evk1w5TPlg2uYD5/dQe8W+i
OQRE6OfBTLmWlOhKZHiLr0YsfGG0GiaQGwtsAEe5pniGai8SIBWuqlZxbLeO
Lm83Fe+qLU2q1Ih3Z/AcWNjpMNIQekVLYIuvO5lJ+LeEt/iN1NCMt969kSKu
6jEGrnfz7lq8XFKSt6aCsBMuuaX1PejCK8x/+IQmDhbRtjEMGfgYzQuq0YyB
9++p+zf62Xus7akG0dab99fbLRRhZRkTTrynKSxmRHUet97qJNDzWYV94+Dh
EScFW2cbS5ygbiflCEkKblMHeXyMlYRhxebWCt06fne9PXA4Jp0pbwVdTe4k
D0yKgGYoSKglvTaUTGynv7OSZ0fsSql8z9qUIMMk4C1aQpnO1cHPHqFnfrkm
Dwup4Rmt5/c95cQOmRfINGCKeAaBDvEON7xXD/dz693VMUzWJ3MhXzIZKc1Q
IsY4VeimVNQV82DysvFYGrkfg8wUvgTQMiGUoU4Q47kGGYwsXSH6vrIrprSP
EPJM7yUfDU9hJmxKMjZo+Jzt4RDOOC/Jgmm/Dyq0LMUKll2xAQgvH9GGmEXd
1pFTh0PYWQqx4zDoLLv4VmymCHWU2C97gTOtiuY5+7y6o7A0//Vf/xUnSXWH
Zf5/60cN4WeVOEaEMh97dTT8qp/RY218/u2hsQzrdmbl3Of2WPpFLcor+Hkj
7Dzs/rP+QWwuGNjIa1faEBCLexUIxLZheWT8GV86ez4c/q/Pln991jastKE2
vNHDw/HvlHd644DfiPcNY2zjmT7+O/3lWWcuwniDNpRzYht+0+3Fgv898wbl
WoePfzfk/z777TY2/nzW/4ZtnO33t+Hv7+jRNn7cOI7PjvPHn/8Jt+YAZuG3
0SayUaeNZ71L4reB/zy3grq1gY/+hG04Ed/XRu96BG08a83lWaeNz56c4vU4
ZIrqrGnvWB9dj/gr2miPsOcHz8Wzr2Bfj/0AUb34O5v48dvf/11nLr/79kaE
I6mMjX9jQTc34kvnv6mRvumAfAkUdDbdWDc/CSWvJ1dFRqkjw3kMnHku+vu5
+LTUq/RBZesZNeQ0eic/o0hSnlkBaldWV8gLuQN864CVBhbnVmnAV122na84
pLW9VaHyfQE0ENRBmuUyKSnbif1xGB8jXBInMp+gA0+nxTYNLEu/T8EC9oIB
B4+L5rOm60zZZZXUJbqffC2DP/vy5XvOlClWDTuAJ2BBLPPKZqN7e7VRmyHn
BW4Dni5UR4TSbop+CmRIQPzf4eqw7g3fu7HJ0+F9/vc7Q7BnEfROiQDb903v
w05JhukHhlC8dX11DGo7VuwEe6leY6mChaF7dNMlJrVwFWLfNBq0DKdpx1Za
BnYR3r5+vc0KC8nUcMzPeyzJ1piP7Rdil1c28WqDcdmzWs9bK/SZFP6+1bKW
ETpVwpkGJqKUT/eMp462Rz0ftHrzhf8jPasvQswvOGahQfi4F4d6ftHpud9K
alEI2j1qCXFx0MDUCUKymW1wxQ2OqOfDTs9dQ7Qz5+O2hdljT5KpW1pG3LUh
AwuSy/223TdSLoPFw9tvlgfOV3q2x3oikRftNC06zT/0fR5t/j/Pl/knkbPy
m/szDn2TX/Pc8w3P/an13MFj7f0p9AVubM977vAr+33Z/603D3/LRIqou60d
o+Iw1LRfQh15QWaSxSSArdTELT0TUInU8beRtqDYb0WSA76y8aFYsxK4dL5z
WbXjV+S4Amqhq+NfkHxrXRbi8rzs1R2pX6OrcFZx/+0d8RY+BvwNWzrbG1if
Bv39Ytu6HaQ4pPSAkaStfi7KTaADZYSj3yfUeR4OXPJ+FKT26LhloN8Hjkb9
tLJt0LciIHLZl36Ho14rQsN7PoDzxx4wOH2ckxDe+OEVMfm6JdX74RpJUO29
v8Pdh9x/pQzB5RFpKteCKH4pyMK31zNL2qJU6QausnE+eFVo5SNn7BAtGoSL
7Hq3ekunCJGzt6XWXHuwLNdf55STCuo4Lm89pC/0HfI1eAqw1fI5j2ReVe1w
fXgzWU/Z7eN3188qB7Gn05q4phGLA4oHBhRAhbH1nyu9QMmmLW1zrUoP2u1d
hKEj/5oq7gP/+hV3CU0PRXC6hBIBM5G6MtlMazEIlsCG/YI7xZQdUvCPupZg
rFwFpvkum716ygbS0nIuDf6WXLKZ484YXOyLPR5F9lYnbJWrw397kF2L6vBd
3ePEq8vlX2fuUq8exwdwhTGGQYwcO7dMxruayCuEsWrGINfJo6mXNQkP1eyW
ba2yp8Vg5Qgq4pTOHAkdTjUgQGtTj4tG8i/bqR9ass+CsNx57uFg38yx8Kxs
kkED3fagHm6babjy78LXpIBZWNlGqxxZ7qaMRcLZiniSRFm6V0YvpOuvMR3d
3Bfte8IQBMNFMZg/UbZdLyfSkrNaV5zqk20mTBr+kkody2XxOUpnLZCDKiMJ
7OeST/JIvMJm/vG7vwDpoXJspr8InPTl/vPXQKAL0OdlF4G+qIoQ4/TAstDc
LZHYJM4Ova4RDuXddOCle3vhmdR64DlQg7FuARhlJsE4GCoFZ/sDVULaiUlD
y6JsPfJV1sgii2cgdyJpFJ12r3ZTRJK76NEKdefuQKru+EM4XQt4dKYFtTgg
gg4CBBZ5WWsfpKY5FSGqF62wKxztNUUOKknoEdyk4lsIVlmJoi9RW56dLZQw
iOXGlknRUAqq1R+PItTO8C4sRKJXga5il2+LF9ppXM5G8p5BjUxKaeDeIpDP
JTV6GmY+hd2Z8imj8j7cq7uHawyPDZtVDGSXe+K+j0vitASWj0lOWMKZk4ea
NJMLHC2nV+JRa8jFJTsIMZVmuhLMUGUVBh656gNzkzdg2CHfcEguEScuZVWb
PXu+A8eByFBFPsemONQ05Jt3tKIckrYUzSQm5pZvIDXu8EQk5dyEl6bZy7Na
2yk1Kp1CB9Mmm/EmmPsHs5T6tG2XYKnfiKjexJO00oDq78FRlWriqlR17wIs
8olRrUOvLtSMr8Be4RQKvUrNk7V4uxjYKWd7R9FR7JY33sLtJEHoROcgrgq8
NkAuZSRmuGNXDro98jIx9WqaoFThFvk/SKXAkg5n+9grCy8mB+DH7a34npVj
VbgTNtT66lDqmywIgrG0jYeBAw+RFOGce6lYsvX4hcow8iO8V9vaLVlRCUhF
u5kkK0bwpHzNxwSrtmDmMKXVWwfH1AC75MpnZy90A5C7p1U4QZzRkJUNvZW9
okQB8ol5AdjEL9++JQwZ6ZNehmPp72bfFomW4rF/okxrkgjgl40A0iwwWyek
bsxN8lQCOu25Yk20yq5NILCheNh7z4JCwhQubvjgu4l1mK94nrWyQNiH5cik
1Lbfrfhlm9T/+4/HvDJ0flTFYLEcltWR0+QLf5H3TmK6a3o9Lxd9fygWDtXU
ozoEg046O5ICXezDh0Nad2bW1tlzlTfyxjGmTIKuSKoBl9ugE0MaiBVICsAh
eYS4AMztVqLAG6xBTVZu424v+dKHPKbSc+0CXkm8LKiQicrvo+gK/7GTQrPN
51lciQgh+lpME7viEkTxMaoJfcW/uTRVuuSLhTawHpcXFj2NjyeYXQY9zgmo
Ez0cgVZBFW/MlBh1khPkLcLbGcx9/Gforp6AxnZbDKLjTwZzCxcGn58Pojcl
CuJTFMorvPGgHEQ/FNkcRnzWANll+MEfoOUlXneaw4TgTxh1Gl8lmakH0fsU
aAmavILRQavp1H30Af+FCYLtGl0klDR+DdymhM8G0TXMd7yIr0Ep+UtKGOno
plhCL38wOfCDyPoa2L5mS7Um08PeHiRqMmz1uJHai3ppYq2LgO3F71KY+x3r
2zfpsqgX6/gnsmEE6T69w7rqmNgkt6YskpXEcRSwLihul75BOrhcTcNXalaR
pwK8LxagHE3jN0UzSaZJytIR9smUmLU+K5u0xrrm3gTZY93M50iJDNu3hjDq
4UnFyVZ6MRcyVCOHKiO48nGO2uoKLMPLFXRyMHo1iv4f+ot+OBTrAAA=

-->

</rfc>
