Progressing Explicit Address Mappings for Stateless IP/ICMP Translation (RFC7757) to Internet Standard
status-change-eam-to-internet-standard-01

Explicit Address Mappings for Stateless IP/ICMP Translation (EAM, RFC7757) was
published as PS in 2016. Since then, the specification was widely implemented
and used in deployment. Operational experience supports reclassification of
RFC7757 to Internet Standard.

Consistent with its Charter [1], V6OPS requests this reclassification to
acknowledge a higher maturity level. See below for more information:

(1) There are at least two independent interoperating implementations
    with widespread deployment and successful operational experience.

EAM has been widely implemented and it is being used in deployments.

A non-exhaustive list of implementations is provided below:

* TAYGA [2]

* CLATD [3]

* JOOL [4]

See more at [5].

(2) There are no errata against the specification that would cause a
    new implementation to fail to interoperate with deployed ones.

There are no errata against RFC 7757.

(3) There are no unused features in the specification that greatly
    increase implementation complexity.

There are no unused features.

(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.

None.

[1] https://datatracker.ietf.org/wg/v6ops/about/

[2]
https://github.com/apalrd/tayga/blob/e78f04a29ad7d5d81677aa36b441cc84548e8d8f/docs/rfc.md?plain=1#L13

[3] https://www.systutorials.com/docs/linux/man/8-clatd/

[4] https://nicmx.github.io/Jool/en/index.html

[5] https://datatracker.ietf.org/doc/draft-palet-v6ops-eam-std/