KOM15007: Jaringan Komputer Lanjut

  

KOM15007:    

Jaringan  Komputer  Lanjut  

Topik:  IPv6  

  Semester Ganjil PTIIK – Universitas Brawijaya http://elearning.ptiik.ub.ac.id Review  Jaringan  Komputer    

       IPv6

• Algoritma  Rou@ng  
• Intra-­‐domain  Rou@ng  
• Inter-­‐domain  Rou@ng  
• Policy  Rou@ng  
• Overlay  Network  

  

Evaluasi  &  Nilai  

 

  Mata Kuliah ini

• 3 SKS _

  Evaluasi _ Keaktifan dalam perkuliahan 5% _ Tugas Praktik/Diskusi/Presentasi 50% _ UTS

  20% _ UAS

  25%

  

Kuliah  Hari  ini  

• IPv6:
• –  Addressing –  Notation –  Transition to IPv6
• How  many  IP  address?  

• –  IPv4:  2^32  =  4.3  *  10
⁹

 (Billion)  

• –  IPv6:  2^128  =  3.4  *  10
³⁸  (Undecillion) &
• When  was  IP  address  standardized?  
• –  IPv4  in  1981  (RFC  791)  
• Developed  in  1970s  
• –  IPv6  in  1995  (RFC  1883)  refined  in  1998  (RFC  2460)  
• As  early  as  1990,  IETF  started  to  work  on  IPng,  solving  IPv4   _{address  shortage  issue}  

IPv6?  

• Support  billions  of  hosts  
• Reduce  the  size  of  the  rou@ng  tables  
• Simplify  the  protocol  
• Provide  beeer  security  (authen@ca@on  &  privacy)  
• Pay  more  aeen@on  to  QoS  
• Aid  mul@cas@ng  by  allowing  scoped  to  be  specified  

• •  Allowing  a  host  to  roam  without  changing  its  address  

  Do  we  really  need  larger  IP  address  space?   _{World‘s  Total  Internet  users  =  2.4  Billion}   World’s  Total  Popula5on  (est.)  =  7  Billion  

• From  CIA’  factbook:  
• –  mobile  phone  users:  249.8  million  in  2011  
• –  Internet  users:  20  million  in  2009  
• –  Internet  hosts:  1.344  million  in  2012  
• –  Popula@on:  248,6  million  (est.  2012,  no.  4  in  the  world)  
• –  Total  IP  addresses:  (source:  maxmind.com)  

    18,901,572    

• compared  to  
• Problems  

• –   rapid  increase   of  the  size  of  rou@ng  tables  
• 450,000+  entries  in  the  Internet  now  

  exhaust  by  2008.  

• –  was  predicted  that  IPv4  will  
• Theore@cal  limit:      4.29  billion  addresses  
• Prac@cal  limit:    250  million  devices     ^{(RFC  3194)}  
>–  256  “/8”  =  2^24  =  16.78  millions  
• –  Reserved  by  IETF  (RFC  5735)  =  35,078  “/8”  

• •  IPv4  address  exhaus@on  is  the  deple@on  of  the  pool  

  of  unallocated  IPv4  addresses  
• IANA’s  Unallocated  Address  Pool  Exhaus@on:        

  03-­‐Feb-­‐2011    

• – •  Projected  RIR  Address  Pool  Exhaus@on  Dates:  

  

19-­‐Apr-­‐2011  (actual)              0.8857  

• –  APNIC:  

  14-­‐Sep-­‐2012  (actual)  0.9264  

• –  RIPE  NCC:  
• –  LACNIC:  04-­‐Jul-­‐2014  2.5137  
• –  ARIN:  05-­‐Jul-­‐2014  2.9267  

IPv4  address  deple@on  

• Classless  Inter  Domain    Rou@ng  (CIDR)  
• Network  Address  Transla@on  (NAT)  

• NAT  :  Network  Address  Transla@on  
• –  Assign  private  addresses  to  the  internal  systems    
• –  Router  translate  the  addresses   _{192.0.0.1   175.45.190.1}  

  175.45.188.1   _{Address  Space   Private     192.0.0.2   IP  address  Space   Global}     NAT     _192.0.0.1  

• NAT(Network  Address  Translator)  
• –  Popular  on  Dial-­‐ups,  SOHO  and  VPN  networks  
• –  will  save  IPv4  address  
• –   Asymmetric  iden@fier/communica@on    model  

    lost  of  the  end-­‐to-­‐end  model  

• –
• NAT  breaks  “end-­‐to-­‐end  communica@on”  

• –  Routers  monitors  the  communica@on  
• –  Routers  changes  the  data  
• NAT  breaks  “Bi-­‐direc@onal  communica@on”  
• –  Hosts  with  global  address  can  not  ini@ate  the   communica@on  to  the  hosts  with  private  address.  
• Room  for  many  levels  of  structured  hierarchy  and   rou@ng  aggrega@on  
• Easier  address  management  and  delega@on  than  

  IPv4  

• Easy  address  auto-­‐configura@on  
• Ability  to  deploy  end-­‐to-­‐end  IPsec  

  (NATs  removed  as  unnecessary)  

  

IPv6  

started  in  1994  

• Larger  Address  space   ₃₈  
• –  128  bit:  3.4  *  10
• Re-­‐design  to  solve  the  current  problems  such  as;  
• –  Efficient  and  hierarchical  addressing  and  rou@ng   infrastructure  
• –  Security  
• –  Plug  &  Play  
• –  Beeer  support  for  QoS  

• IPv6  cannot  easily  solve  (same  as  IPv4);  
• –  Security  
• –  Mul@cast  
• –  Mobile  
• –  QoS  

  00101010 00010010 00110100 01011100 00000000 00000000 00000000 00000000 00000000 01111000 00001001 10101011 00001100 00001101 11100000 11110000

  A  128  bit  value  

  2A12:3456:0:0:78:9AB:C0D:E0F0

  00000000 00000000 00000000 00000000 00000000 01111000 00001001 10101011

  2A12:3456:0:0:78:9AB:C0D:E0F0 Eight  blocks  of  16  bits  in  hexadecimal   separated  by  colons  (::)  

  Eight  blocks  of  16  bits  in  hexadecimal   separated  by  colons  (::)  

  2A 12 : 3456:0:0:78:9AB:C0D:E0F0 00000000000000000000000000000000 00000000011110000000100110101011

  Eight  blocks  of  16  bits  in  hexadecimal   separated  by  colons  (::)  

  2A12:3456:0 :0: 78:9AB:C0D:E0F0 0000000000000000 00000000 00000000 00000000011110000000100110101011

  Eight  blocks  of  16  bits  in  hexadecimal   separated  by  colons  (::)  

  2A12:3456:0:0:78:9AB:C0D : E0 F0 00000000000000000000000000000000 00000000011110000000100110101011

• Blocks  of  0  may  be  shortened  with  double  colon  

  only  one  ::  

  (::)  ;  but   is    allowed     1234:5678:90AB::5678:0:CDEF 1234:5678:90AB:0:0:5678::CDEF 1234:5678:90AB::5678::CDEF  

  <prefix>/<prefix-length> 1234:5678::/48 1234:5678:9ABC:DEF::/64

• Unicast  
• –  Single  interface  
• Mul@cast  
• –  Set  of  interfaces  
• –  Packets  delivered  to  all  interfaces  
• Anycast  
• –  Set  of  interfaces  
• –  Packets  delivered  to  one  (the  nearest)  interface  

Address  Type  Iden@fica@on  

  Type Binary Value/Prefix IPv6 Notation Unspecified 000…0 (128bits) ::/128 Loopback 000…1 (128bits) ::1/128 Multicast 11111111 FF00::/8 Link-local unicast 1111111010 FE80::/10 Global unicast (everything else)

  Format   Prefix _{001 TLA ID RES NLA ID SLA ID Interface ID}

  3 bits 13 bits 8 bits 24 bits 16 bits 64 bits _{NLA  ID  Next-­‐level  aggrega@on  iden@fier   RES    Reserved  for  future  use}   TLA  ID  Top-­‐level  aggrega@on  iden@fier   SLA  ID  Site-­‐level  aggrega@on  iden@fier  

  Network Prefix Interface ID 64 bits 64 bits

  A  link ’

s  prefix  length  is  always  64  bit   Alloca@ng  IPv6  Address  Space   2001:df0:ba::/48

• 16  bits  for  link’s  network  prefixes  =  65k  
• Interface  ID:  manual  or  automa@c  
• Automa@c:  Modified  EUI-­‐64  of  MAC  address   _{nd st}

   LSB  of  1  byte    

• –  Complement  2 _{rd th}

   and  4  bytes    

• –  Insert  0xfffe  between  3
• MAC:    00-12-34-56-78-9a

  2 12:34 ff : fe 56:789a

• Interface  ID:  

fe80::<Interface-ID>     KAME  style   fe80:<Interface-ID>%<ifname> fe80::212:34ff:fe56:789a%fxp0

Prefix _{1111 1111 FLAGS SCOPE Group Identifier Flags:}     8 bits _{4 bits 4 bits Scope:}   ^{112 bits} _{LSB  =  1  temporary/transient  mcast  address   2  link-­‐local  scope}   LSB  =  0  well-­‐known  mcast  address   1  interface-­‐link  scope   _{5  site-­‐local  scope}  

ff02::2

• Well-­‐known  address,  link-­‐local  scope  

  ff18::100

• Temporary  address,  organiza@on-­‐local  scope  

  ’s  Address  

• Loopback  Address  
• Link-­‐local  Address  for  each  interface  
• Addi@onal  Unicast  and  Anycast  Addresses  
• All-­‐Nodes  Mul@cast  Addresses  (ff02::1)  
• Solicited-­‐Node  Mul@cast  Addresses  
• Mul@cast  Addresses  of  groups  it  joined  

  ’s  Address  

• A  node’s  address  
• Subnet-­‐Router  Anycast  Addresses  
• All  other  Anycast  Addresses  
• All-­‐Router  Mul@cast  Addresses  (ff02::2)  

IPv4  vs  IPv6  Header  

  Ver. _{4 HL}

  TOS Datagram Length _{Datagram-ID Flags Flag Offset} TTL Protocol Header Checksum _{Source IP Address} Destination IP Address

  IP Options (with padding if necessary) ^{32 bits Ver. 6 Traffic class 8 bits Flow label 20 bits Payload Length 16 bits Next Hdr. 8 bits Hop Limit 8 bits Source Address 128 bits} _{Destination Address} ^{32 bits}

• Fragmenta@on/Reassembly  
• –  IPv6  do  not  allow  for  fragmenta@on/reassembly  
• Header  checksum  
• –  Because  Transport  layer  and  data  link-­‐layer  have   handle  it  
• Op@ons  
• –  fixed-­‐length  40-­‐byte  IP  header  

  What  about  the  transi@on     from  IPv4  to  IPv6?  

• Many  techniques,  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.

  

  Transla5on:  Conver@ng  IPv6traffic  to  IPv4  traffic  for  

  _Application ach _{IPv6-enabled Application TCP UDP Application} Preferred method on TCP UDP ’s servers _{0x0800 0x86dd}

  IPv4 ^IPv6

_{0x0800 0x86dd}

_{IPv4 IPv6 Frame Data Link (Ethernet)}

_{Data Link (Ethernet)}

Protocol ID

• Dual  stack  node  means:  
• –  Both  IPv4  and  IPv6  stacks  enabled  

  www.a.com _{= * ? IPv4 Server DNS} 2001:db8::1 _{10.1.1.1 IPv6} 2001:db8:1::1

• a  system  running  dual  stack,  an  applica@on   with  IPv4  and  IPv6  enabled  will:  
• –  Ask  the  DNS  for  an  IPv6  address  (AAAA  record)    
• Manually  configured  

• –  Manual  Tunnel  (RFC  4213)  
• –  GRE  (RFC  2473)    
• Semi-­‐automated  
• –  Tunnel  broker  
• Automa@c  
• –  6to4  (RFC  3056)  

  IPv4 Interface ipv6 nat prefix _{IPv4 Host IPv6 Host}

  

NAT-PT

  IPv6 Interface 172.16.1.1 ^{2001:db8:1987:0:2E0:B0FF:FE6A:412C}

• Techniques:  
• –  NAT-­‐PT  
• require  Applica@on  Layer  Gateway  (ALG)  func@onality  that   _{converts  Domain  Name  System  (DNS)  mappings  between   protocols.  (not  really  in  use,  since  NAT64  came)}  

Bertanyalah,  sebelum  anda  ditanya!   Ada  pertanyaan?  

  END  OF  LECTURE  #2