KOM15032:

 Arsitektur  Jaringan  
Terkini  
#04  –  Transi;oning  to  IPv6  
Achmad  Basuki,  ST.,  MMG.,  Ph.D  
 KOM15032:  Class  Overview  
•  Mata  Kuliah  :  Arsitektur  Jaringan  Terkini  
•  Beban  Studi  :  3  SKS  
•  Sifat        :  Pilihan  
•  Prasyarat    :  Jaringan  Komputer  
•  Pustaka      :    
–  Materi-­‐materi  online  di  Internet:  
–  John  Day,  PaSerns  in  Network  Architecture:  A  Return  
to  Fundamentals.  Pearson.  2007.    

Slide  2  
 KOM15032:  Course  Purposes    
•  memahami  berbagai  kelebihan  dan  kekurangan  
arsitektur  jaringan  komputer  saat  ini.  
•  menger;  akan  kebutuhan  arsitektur  jaringan  
komputer  masa  depan.  

Slide  3  
 KOM15032:  Grading  
•  Tugas  terstruktur    :  30%  
–  nilai  rata-­‐rata  dari  Tugas/Quiz  
•  UTS/MidTerm      :  30%  
•  UAS/Tugas  Akhir    :  35%  
•  Ak;fitas/Kehadiran  :      5%  

Slide  4  
 Pokok  Bahasan  
Paruh  Semester  Pertama   Paruh  Semester  Kedua  

•  Dasar  Arsitektur  Jaringan   •  Content-­‐centric  Networking  

•  Internet  and  End2End   •  Data  Center  Networking  
Argument   •  So`ware  Defined  Networking  
•  Pengalamatan  &  Penamaan   •  Challenged  Networks  
•  Pembagian  Layer   Environments  
•  UTS   •  UAS  

Slide  5  
 Outline  of  Today’s  Lecture  
•  Addressing: Transitioning to IPv6"
–  Dual Stack"
–  Tunneling"
–  Translation"

Slide  6  
 History  
•  1982:  NCP  to  IPv4  
–  There  was  a  “flag  day”  

Slide  7  
 Transi;oning  to  IPv6  
•  There  are  many  techniques,  but  basically  fall  into  
three  approaches:  
1.  Dual-­‐stack:  running  both  IPv4  and  IPv6  on  the  same  
device  
•  to  allow  IPv4  and  IPv6  to  co-­‐exist  in  the  same  devices  and  
networks  
2.  Tunneling:  Transpor;ng  IPv6  traffic  through  an  IPv4  
network  transparently  
•  to  avoid  dependencies  when  upgrading  hosts,  routers,  or  
regions  
3.  TranslaDon:  Conver;ng  IPv6traffic  to  IPv4  traffic  for  
transport  and  vice  versa  
•  to  allow  IPv6-­‐only  devices  to  communicate  with  IPv4-­‐only  devices  

Slide  8  
Dual Dual Dual-­‐Stack  
StackStack ApproachApproach  
Approach
IPv6-enabled
IPv6-enabled
Application
Application Application
Application
Pre Pre
f A fer
Ap er r p p red
e
plic d m ica met l
TCP UDP TCP UDPatio eth tion’ hod
TCP UDP TCP UDP n’s od o s se on
ser n rve
ver rs
s
IPv4 IPv4
IPv6 IPv6 IPv4 IPv4
IPv6 IPv6

Frame Frame
x0800 0x0800
0x86dd 0x86dd 0x0800 0x0800
0x86dd 0x86dd
Protocol Protocol
ID ID
Data Link (Ethernet) Data Link (Ethernet)
Data Link (Ethernet) Data Link (Ethernet)

 Dual
Dual stack stack
node •  Dual  
node
means: means: stack  node  means:  
BothIPv6
Both IPv4 and IPv4stacks
and IPv6
–  Both  
enabledstacksIPv4  
enabled and  IPv6  stacks  enabled  
Applications
can talk to can
Applications both– talkApplica;ons  
to both
can  talk  to  both  
Choice of the is
IPbased
versiononisname
basedlookup
on name lookup and application preference
Choice of the IP version –  Choice   of  the  IP  vand
ersion   is  based  
application on  
preference
name  lookup  and  applica;on  preference  
NANOG 42  
© 2008 Cisco Systems, Inc. All rights reserved.
© 2008 Cisco Systems, Inc. All rights reserved. Slide  9  
72
72
 Dual Stack & DNS
Dual-­‐Stack  Approach  
www.a.com
=*? IPv4

2001:db8::1
DNS 10.1.1.1 IPv6
Server
2001:db8:1::1
•  a  system  running  dual  stack,  an  applica;on  
 On a system running dual stack, an application that is both IPv4 and IPv6
enabled will: with  IPv4  and  IPv6  enabled  will:  
for Ask  
Ask the DNS –  an IPv6 the   DNS  (AAAA
address for  an  record)
IPv6  address  (AAAA  record)    
If that exists, –  If  transport
IPv6 that  exists,  
will be Iused
Pv6  transport  will  be  used  
–  If  itit  will
If it does not exist, does  
then n ot  the
ask exist,  
DNS ifort  wanill  IPv4
then   ask  (A
address the   DNS  and
record) for  an  
use IPv4 transport instead
IPv4  address  (A  record)  and  use  IPv4  transport  
NANOG 42
instead  
© 2008 Cisco Systems, Inc. All rights reserved. 73

Slide  10  
across an IPv4 network to the other side where the IPv4 packet is removed and the IPv6 packets
continue on their way. 88 Conversely, IPv4 packets can also be tunneled across IPv6 networks.

Tunneling  Approaches  
Figure 7: Example of Tunneling IPv6 Traffic Inside an IPv4-Only Internet 89

•  Manually  configured  
Preparations for Transition –  Manual  Tunnel  (RFC  4213)  
Established networks that are –  GRE  
strongly (RFC  in2473)  
engaged IETF,  ICANN, and RIRprocesses
appear to be taking appropriate measures in anticipation of the IPv6 transition. However, lessons
•  Semi-­‐automated  
from past transitions indicate that there may be some businesses that are not as aware or
prepared. 90 Unprepared businesses could –  Tunnel  
begin b roker  
to experience connectivity and service issues,
91
and difficulty acquiring additional IPv4 addresses. A business that delays transition could find
•  Automa;c  
it costly to achieved on a compressed schedule. 92
– 
IPv4 Allocations and Transfers 6to4  (RFC  3056)  
IP address blocks have historically 6rd  
– been allocated based on need. 93 The costs involved in
receiving an allocation are nominal and are not generally a factor in considering whether to apply
–  ISATAP  (RFC  4214)    
for an allocation. 94 The principle requirement has been the ability to demonstrate need for the IP
addresses, pursuant to community developed–  TEREDO   (RFC  
RIR address 4380)  
policy. If an address block was not
needed, it would (in theory) be returned; it could not be traded.
Slide  11  
IPv4 conservation has dampened the pace of IPv4 exhaustion. In the early days of the
 NAT-PT Concept
Transla;on  Approaches  
IPv4 IPv6
Interface
NAT-PT Interface

IPv4 Host ipv6 nat prefix IPv6 Host

172.16.1.1 2001:db8:1987:0:2E0:B0FF:FE6A:412C

•  Techniques:  
 prefix is a 96-bit field that allows routing back to the
–  NAT-­‐PT  
NAT-PT device
•  require  Applica;on  Layer  Gateway  (ALG)  func;onality  that  
converts  Domain  Name  System  (DNS)  mappings  between  
protocols.  (not  really  in  use,  since  NAT64  came)  
–  NAT64  
82
•  combined  with  DNS64  
NANOG 42 © 2008 Cisco Systems, Inc. All rights reserved.

Slide  12  
End  of  Today’s  Lecture  

THANK  YOU  ...  

Any  Ques;on?  

Slide  13