<?xml version="1.0" encoding="UTF-8"?>
<?rfc toc="yes"?>
<?rfc compact="yes"?>
<?rfc tocdepth="6"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc autobreaks="no"?>
<?rfc subcompact="no"?>

<rfc category="std" submissionType="IETF" consensus="yes" ipr="trust200902" docName="draft-palet-v6ops-eam-std-01">
  <front>
  <title abbrev="Reclassifying EAM (RFC7757) to STD">Reclassifying EAM (RFC7757) to Internet Standard</title>

    <author fullname="Jordi Palet Martinez" initials="J" surname="Palet Martinez">
      <organization>The IPv6 Company</organization>

      <address>
        <postal>
          <street>Molino de la Navata, 75</street>

          <city>La Navata - Galapagar</city>

          <region>Madrid</region>

          <code>28420</code>

          <country>Spain</country>
        </postal>

        <email>jordi.palet@theipv6company.com</email>

        <uri>http://www.theipv6company.com/</uri>
      </address>
    </author>

    <date year="2025"/>

		<workgroup>v6ops</workgroup>


		<abstract>
			<t>This document reclassifies Explicit Address Mappings for Stateless IP/ICMP Translation (<xref target="RFC7757"/>) to Internet Standard.</t>
		</abstract>
	</front>

	<middle>
		<section title="Introduction">
			<t>This document proposes that Explicit Address Mappings for Stateless IP/ICMP Translation (<xref target="RFC7757"/>) 
			is advanced Internet Standard, following RFC6410 (<xref target="RFC6410"/>).</t>

			<t>(1) There are at least two independent interoperating implementations with widespread 
			deployment and successful operational experience.</t>

			<t>Explicit Address Mappings for Stateless IP/ICMP Translation (<xref target="RFC7757"/>) has been widely implemented by 
			at least a dozen of vendors and its being used in commercial deployments by hundreds of millions of devices.</t>

			<t>(2) There are no errata against the specification that would cause a new implementation to fail 
			to interoperate with deployed ones.</t>

			<t>Explicit Address Mappings for Stateless IP/ICMP Translation (<xref target="RFC7757"/>) has no errata filed.</t>

			<t>(3) There are no unused features in the specification that greatly increase implementation complexity.</t>

			<t>There are no unused features.</t>

			<t>(4) If the technology required to implement the specification requires patented or otherwise 
			controlled technology, then the set of implementations must demonstrate at least two independent, 
			separate and successful uses of the licensing process.</t>

			<t>None.</t>

		</section>

        <section title="Implementation Status">
            <t>Note to RFC Editor: If this document needs to be published, please remove this section before publication, as it is only intended for the IESG evaluation.</t>
            
            <t>This section summarized the known status of existing and interoperable implementations of the protocol subject of this document, as well as closely related protocols. This is following (<xref target="RFC7942"/>) and intended to assist the relevant WGs, IESG and IETF as a whole, in the evaluation of the document for the document progress through the standardization process.</t>
            
            <t>The description of the implementations does not imply any IETF endorsement and is solely based on public available information, which has not been formally confirmed by specific interoperatbility testing for this document publication; however, it is known to be confirmed by existing commercial working deployments worldwide and without knows interoperability issues.</t>
            
            <t>Explicit Address Mappings for Stateless IP/ICMP Translation (<xref target="RFC7757"/>) was originally published in February 2016.</t>
            
            <t>(<xref target="RFC7757"/>) is implemented together with other related protocols (just to name a few of the most relevant ones) such as:</t>
            <t><list style="symbols">
                <t>IPv6 Addressing of IPv4/IPv6 Translators (<xref target="RFC6052"/>).</t>
                <t>IP/ICMP Translation Algorithm (<xref target="RFC7915"/>).</t>
            </list></t>
            
            <t>Follows a list of known implementations by different products/vendors, known to be mature and in production products/networks/services worlwide:</t>
            <t><list style="symbols">
                <t>A10. Implemented in multiple products. https://www.a10networks.com/products/thunder-cgn/.</t>
                <t>Arista. Implemented in multiple products. https://www.arista.com/en/support/toi/eos-4-24-0f/14495-map-t-border-relay.</t>
                <t>Broadcom. Implemented in Brocade products. https://techdocs.broadcom.com/us/en/vmware-cis/nsx/nsxt-dc/3-1/administration-guide/network-address-translation/configure-an-nsx-nat64.html.</t>
                <t>Cisco. Implemented in multiple series of products. https://www.cisco.com/c/en/us/td/docs/routers/ios/config/17-x/ip-addressing/b-ip-addressing/m_iadnat-stateless-nat64.html.</t>
                <t>CLATD. Implemented in Linux. https://github.com/toreanderson/clatd.</t>
                <t>F5. Implemented in multiple products. https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/cgn-implementations-11-6-0/2.html.</t>
                <t>Fortinet. Implemented in multiple products. https://docs.fortinet.com/document/fortigate/7.4.6/fortinet-carrier-grade-nat-field-reference-architecture-guide/891965/nat64.</t>
                <t>Huawei. Implemented in multiple series of products. https://support.huawei.com/enterprise/en/doc/EDOC1100279002/a8672300/appendix-gx-interface.</t>
                <t>Jool. Implmemented since 2014. https://nicmx.github.io/Jool/en/index.html.</t>
                <t>Juniper. Implemented in multiple series of products. https://www.juniper.net/documentation/us/en/software/junos/nat/topics/topic-map/security-persistent-nat-and-nat64.html.</t>
                <t>Nokia. Implemented in multiple products as part of the NAT64 support. https://documentation.nokia.com/acg/23-7-2/books/classic-cli-part-iii/c128-nat-stateless-dh.html.</t>
                <t>OpenWRT. https://github.com/openwrt.</t>
                <t>Palo Alto. Implemented in muliple products. https://docs.paloaltonetworks.com/ngfw/networking/nat64.</t>
                <t>Tayga. https://github.com/openthread/tayga.</t>
                <t>VPP. https://wiki.fd.io/view/VPP/Configure_an_LW46_(MAP-E)_Terminator#SIIT-DC.</t>
            </list></t>
            
            <t>Note that even an effort has been done to compile an extensive list (including a relevant URL), there may be many more implementations not publicly known, so this list doesn't pretent to be exclusive, just an indication of a sufficient number of implementations, as required for the evaluation of the current implementation status.</t>
        </section>
        
	</middle>

  <back>

    <references title="Normative References">
		<?rfc include="reference.RFC.7757" ?>
		<?rfc include="reference.RFC.6410" ?>
    </references>

    <references title="Informative References">
        <?rfc include="reference.RFC.6052" ?>
        <?rfc include="reference.RFC.6147" ?>
        <?rfc include="reference.RFC.7599" ?>
        <?rfc include="reference.RFC.7755" ?>
        <?rfc include="reference.RFC.7756" ?>
        <?rfc include="reference.RFC.6877" ?>
        <?rfc include="reference.RFC.7915" ?>
        <?rfc include="reference.RFC.7942" ?>
    </references>

  </back>


</rfc>
