NAT444 or ?
simon.perreault at viagenie.ca
Wed Sep 7 16:29:16 CDT 2011
David Israel wrote, on 09/07/2011 04:21 PM:
> In theory, this
> particular performance problem should only arise when the NAT gear insists on a
> unique port per session (which is common, but unnecessary)
What you're describing is known as "endpoint-independent mapping" behaviour. It
is good for not breaking applications, not so good for scalability. RFC 4787
section 4.1 makes it a MUST.
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server --> http://numb.viagenie.ca
More information about the NANOG