The IESG has received a request from the IPv6 Operations WG (v6ops) to
consider the following document: - '464XLAT Customer-side Translator (CLAT):
Node Behavior and
   Recommendations'
  <draft-ietf-v6ops-claton-12.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
[email protected] mailing lists by 2025-11-21. Exceptionally, comments may
be sent to [email protected] instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   464XLAT defines an architecture for providing IPv4 connectivity
   across an IPv6-only network.  The solution involves two functional
   elements: provider-side translator (PLAT) and 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 the
   node developers on enabling and disabling CLAT.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-v6ops-claton/



No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc6877: 464XLAT: Combination of Stateful and Stateless Translation 
(Informational - Internet Engineering Task Force (IETF) stream)
    rfc8585: Requirements for IPv6 Customer Edge Routers to Support 
IPv4-as-a-Service (Informational - Internet Engineering Task Force (IETF) 
stream)
    rfc9872: Recommendations for Discovering IPv6 Prefix Used for IPv6 Address 
Synthesis (Informational - Internet Engineering Task Force (IETF) stream)




_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to