On Mar 15, 2011, at 5:04 PM, Brian E Carpenter wrote: > 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)?
I don't think so, at least not in any general sense, because it's a matter of routing, traffic loads, probability of failure, and so on - it's is all about specific cases. If a network has two upstreams and one DMZ to each, it will apply to every TCP session open at the time of the failure. If it has two DMZs to each, does re-routing take it to the other DMZ to the same ISP (0% loss) or a DMZ to a different ISP (100% loss), or some middle ground? If failures happen every 100 days, and the network typically opens and closes 3100 TCP sessions/second (assumes that every session consumes 50 KBPS on a 155 MBPS link and that is exactly what's happening), 3100/(100*24*3600*3100) is 0.00003733572282%, or so says /Applications/Calculator.app. If you don't like my numbers, insert your own. For the record, we had a power failure this morning at the house and every TCP session I had outstanding did a belly flop. I think that was exactly zero. _______________________________________________ nat66 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nat66
