One suggestion I would make came out of a private discussion on the
politics of the discussion. "Network Address Translation" is a pretty
good description of the behavior of IPv4 NATs and their attendant
issues detailed in RFC 4864. This is in fact a "Network Prefix
Translation" draft; changing the name of the functionality might help
have a more illuminating and less heated discussion.
On Mar 9, 2009, at 3:08 PM, Margaret Wasserman wrote:
Hi All,
I just submitted a new NAT66 draft. I had to submit it for manual
posting, because of an internal meta-data error that I don't
understand. Anyway, it may take a couple of days to post, so here
it is for your review and comments.
It still has the behave name, because I forgot about the name change
until after the -00 submission deadline. If we continue this work
after SF, I will change the name.
Thanks,
Margaret
<draft-mrw-behave-nat66-02.txt>
_______________________________________________
nat66 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nat66
_______________________________________________
nat66 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nat66
