nanog mailing list archives
Re: Production-scale NAT64
From: Mark Tinka <mark.tinka () seacom mu>
Date: Thu, 27 Aug 2015 15:17:47 +0200
On 27/Aug/15 14:59, Bjoern A. Zeeb wrote:
The question I have not seen the answer yet to is “why?” Is this really because of the network, e.g., separate pipes in some places still, with forwarding devices handling a lot less pps? Is it because of people having done a newer cleaner-cut network stack implementation and lately cared about its performance? Is it about middle nodes? Has anyone done the research on this?.
The life of an IPv4 packet on the Internet is very likely to undergo some NAT at some point in its travels. I haven't yet heard of many doing NAT66, hence IPv6 not undergoing NAT means any slow-downs caused by NAT44 are missed (gladly) on IPv6. This might not necessarily be immediately visible on regular networks, but the large content players could count this quite easily due to the significant volumes of traffic their networks are having to aggregate and process. Mark.
Current thread:
- Re: Production-scale NAT64, (continued)
- Re: Production-scale NAT64 Mark Tinka (Aug 26)
- Re: Production-scale NAT64 Tore Anderson (Aug 26)
- Re: Production-scale NAT64 Mark Tinka (Aug 27)
- Re: Production-scale NAT64 Brandon Ross (Aug 27)
- Re: Production-scale NAT64 Mark Tinka (Aug 27)
- Re: Production-scale NAT64 Randy Bush (Aug 29)
- Re: Production-scale NAT64 Mark Tinka (Aug 26)
- Re: Production-scale NAT64 Valdis . Kletnieks (Aug 26)
- Re: Production-scale NAT64 Ca By (Aug 26)
- Re: Production-scale NAT64 Bjoern A. Zeeb (Aug 27)
- Re: Production-scale NAT64 Mark Tinka (Aug 27)
- Re: Production-scale NAT64 Ca By (Aug 27)
- Re: Production-scale NAT64 Mark Tinka (Aug 26)
- Re: Production-scale NAT64 Valdis . Kletnieks (Aug 26)
- Re: Production-scale NAT64 Mark Tinka (Aug 26)