Le 1 août 2011 à 18:34, Wojciech Dec a écrit : ... > Note that with stateless mappings + encapsulation, "stateless NAT" is an > inappropriate wording, because there is no translation: > > All of the current Stateless46 variants TRANSLATE Layer 4 (TCP/UDP) + layer > 3 (IPv4) info into Layer 3 (IPv6). Would be happy to use another term if... > > - This ensures e2e transparency,
Right, if IPv4 packets are encapsulated, they cannot be said to be "translated". "Stateless NAT" isn't therefore an adequate generic term for all the stateless solutions being discussed or IPv4 via IPv6. "Stateless IPv4-via-IPv6", as in your draft, is AFAIK much better. 4V6 variants could then be named, for example: - Stateless 4V6 Translation - Stateless 4V6 Encapsulation - Stateful 4V6 without CGN (RFC 6145, but no NAPT64) - Stateful 4V6 with CGN (NAPT64) If acronyms are needed (and they tend to be), they could be something like: - 4V6T, 4V6E, 4V6N , 4V6C - or 4V6-T, 4V6-E, 4V-6N , 4V6-C - whatever expresses both what is common and what is different Thoughts? Cheers, RD
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
