Thus wrote Brian E Carpenter ([email protected]):
> On 2011-03-16 11:51, Fred Baker wrote:
> ...
> > people don't spend a lot of cycles thinking about NAPT44 route flap
> > effects.
>
> The interesting thing is that people don't spend cycles thinking about
> any of the NAT-induced glitches which cause end users to lose sessions;
> some of these will apply to NPTv6 of course. I wonder if it's possible
> to quantify this (rough % of sessions lost by NAPT44 glitches, and
> how many of these would *not* occur with NPTv6)?
You get NAPT44 glitches under two circumstances, in my experience:
- your NAT gateway is buggy or overwhelmed and loses NAT state ->
single sessions fail randomly
- your NAT gateway reboots, all sessions that were going previously are
toast
Both are due to the statefulness of NAPT44. Since NPTv6 is stateless,
I do not expect either to apply. (Modulo "it's buggy as an ant farm", but
that's not a protocol failure, especially not of the protocol algorithm
is fairly simple).
If an outside link fails, I would say it was unfair to blame the NPTv6 for
the sessions across it failing; it's not the cause, the sessions would
have died without translation just the same.
regards,
spz
--
[email protected] (S.P.Zeidler)
_______________________________________________
nat66 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nat66
