[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
NAT444 or ?
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.
Simon
--
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
- References:
- NAT444 or ?
- From: Jean-Francois.TremblayING at videotron.com (Jean-Francois.TremblayING at videotron.com)
- NAT444 or ?
- From: seth.mos at dds.nl (Seth Mos)
- NAT444 or ?
- From: davei at otd.com (David Israel)