Hi James,

I didn't read this before posting my previous message... Would "Algorithmic NAT66" address your concern? Because I do think that is the main way in which this is different form regular old NAPT44, or an IPv6 equivalent.

What do you think?

Margaret

On Oct 29, 2010, at 7:24 PM, james woodyatt wrote:

margaret--

I went through my archives of the list. We've discussed the naming confusion issue before, but I don't think a consensus emerged. Here's what I proposed:

Begin forwarded message:

From: james woodyatt <[email protected]>
Date: April 1, 2009 08:56:07 PDT
To: [email protected]
Subject: Re: [nat66] The case for the name SAT66 to mean stateless NAT66

On Apr 1, 2009, at 08:41 , Fred Baker wrote:

That said, I think Remi has made a good suggestion here. Calling it Stateless Address Translation makes sense, I think.

I could accept either of the following as improvements to the existing order:

+ Stateless IPv6-to-IPv6 Address Translation (SAT66)
+ IPv6 Network Prefix Translation (6NPT)

I prefer the latter term, but the former is fine too.

I'd prefer either of these over NAT66 on the grounds that I expect it to be easier to teach people that this new and different thing they've never heard of before still breaks some applications, than to try to teach people that conventional NAT44 means dynamic per- host state, NAT64 means dynamic per-host state, but NAT66 means no dynamic state.

On Apr 1, 2009, at 08:49 , Rémi Denis-Courmont wrote:

"NAT" does not mean that it's stateful or stateless. It means it's doing translation. Using a separate word for stateless IPv6-IPv6 NAT will just add to the confusion at this point.

Another reason I prefer IPv6 Network Prefix Translation (6NPT). It still says translation, but it explicitly constrains the translation to network prefixes only.

When the latest revision of I-D.mrw-nat66 appeared and the name had not changed, I assumed that we were still using NAT66 to refer specifically to the proposal in the draft we have, and that we do not yet have a good way to refer to the sort of IPv6 network address/ port translation that Mr. Engel and Mr. Marquis have been so vigorously advocating on the list recently.


--
james woodyatt <[email protected]>
member of technical staff, communications engineering



_______________________________________________
nat66 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nat66

Reply via email to