1

The University Of Auckland

Efficiency of IPv4 - IPv6
Translators
Se-Young Yu
Prof Brian Carpenter
Assoc-Prof Nevil Brownlee
November 2010
2
What Do We Want to Find Out
Efficiency of translators for
Siultaneous connections
!ifferent pac"et si#es
Copare $ scenarios for %TTP access&
'(native IPv4
)(native IPv6
*(NAT64
4(NAT-PT
$(+ual stac" %TTP pro,y
3
How NAT64 works
Clients sen+ an IPv6 re-uest pac"et to t.e
a++ress wit.in NAT64 prefi,(
NAT64 recor+s session state an+ $ tuple
inforation for t.e session(
NAT64 translates source an+ +estination a++ress
accor+ing to t.e translation ec.anis
NAT64 sen+s translate+ IPv4 pac"et to t.e
+estination(
/or rest of t.e session0 translation is perfore+
accor+ing to t.e recor+e+ state(
4
E!eri"ent #lan
A client sen+s '1111 pac"ets for a connection
A client esta2lis.es '-'11 siultaneous
connections(
A client sen+s siple or large pac"et si#e %TTP
re-uests(
A 3inu, router is ipleente+ wit. NAT-PT0
NAT64 45iagenie6 an+ %TTP Pro,y 4apac.e
we2 server60 as well as forwar+ing native IPv4
an+ IPv6(
Siple apac.e we2server is +eploye+ to 2e
teste+ as t.e target(
5
E!eri"ent environ"ent
All t.e 2o,es are
coo+ity PCs
running 3inu,(
6
E!eri"ent $esults% &i"!lest case
7e+ian 8TT
Native IPv4 &
6*' 9sec
Native IPv6&
:4$ 9sec
NAT64&
'1): 9sec
NAT-PT&
'164 9sec
%TTP Pro,y&
'*$$ 9sec
7
E!eri"ent $esults
IPv6-IPv4 NAT64-IPv6 NATPT-IPv6 P8;<Y-IPv6 NATPT-NAT64
-*$1
-*11
-)$1
-)11
-'$1
-'11
-$1
1
$1
'11
'$1
)11
)$1
*11
*$1
411
4$1
$11
$$1
611
6$1
:11
:$1
=11
=$1
>11
>$1
'111
'1$1
$TT co"!ared 'etween different translators for a sin(le connection
sall re-uest? sall response
sall re-uest?2ig response
Big re-uest?sall response
Translators copare+
8
T
T

+
i
f
f
e
r
e
n
c
e

i
n

i
c
r
o
s
e
c
8
)onclusion
NAT64 is clearly a reasona2le c.oice for a sall
si#e pac"et counication(
/or large out2oun+ pac"et NAT64 sees to
perfor 2a+ly 4NAT64 co+e aut.ors can@t
e,plain yet6(
NAT-PT is also reasona2le c.oice 4fro t.e
perforance view6(
%TTP Pro,y ig.t not 2e too 2a+(
Please remember we are comparing
implementations, not protocols!