![Cara Membuat Buku Digital [PDF]](https://pdfs.asia/img/200x200/cara-membuat-buku-digital.jpg)
9 0 759 KB
KOM15032: Arsitektur Jaringan Terkini #04 – Transi;oning to IPv6 Achmad Basuki, ST., MMG., Ph.D
KOM15032: Class Overview • • • • •
Mata Kuliah Beban Studi Sifat Prasyarat Pustaka
: Arsitektur Jaringan Terkini : 3 SKS : Pilihan : Jaringan Komputer :
– 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 • Dasar Arsitektur Jaringan • Internet and End2End Argument • Pengalamatan & Penamaan • Pembagian Layer • UTS
Paruh Semester Kedua Content-‐centric Networking Data Center Networking So`ware Defined Networking Challenged Networks Environments • 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-‐Stack ApproachApproach Dual Dual StackStack Approach IPv6-enabled IPv6-enabled Application Application
Application Application
TCP
TCP UDP
UDP
TCP
TCP UDP
IPv4
IPv4 IPv6
IPv6
IPv4
IPv4 IPv6
Pre Pre fer f A red e p r Ap r p e l plic d m ica met UDPatio eth tion’ hod n’s od o s se on ser n rve ver rs s IPv6
Frame Frame 0x0800 0x86dd 0x0800 0x86dd ID Protocol Protocol ID
x0800 0x0800 0x86dd 0x86dd Data Link (Ethernet) Data Link (Ethernet)
Data Link (Ethernet) Data Link (Ethernet)
Dual stack node means: • Dual stack node means: Dual stack node means:
BothIPv6 IPv4stacks and IPv6 stacksIPv4 enabled – Both and IPv6 stacks enabled Both IPv4 and enabled Applications to both Applications can talk to can both – talkApplica;ons can talk to both Choice of the is IPbased versiononisname basedlookup on name lookup and application preference Choice of the IP version application preference – Choice of the IP vand ersion is based on
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 =*?
DNS Server
2001:db8::1 10.1.1.1
IPv4
IPv6 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:
the DNS (AAAA for an record) IPv6 address (AAAA record) Ask the DNS – for Ask an IPv6 address If that exists, – IPv6 will be Iused If transport that exists, Pv6 transport will be used
If it does not exist, then n ask DNS ifor address record) – If itit will does ot the exist, t wanill IPv4 then ask (A the DNS and for an use IPv4 transport instead NANOG 42
IPv4 address (A record) and use IPv4 transport instead
© 2008 Cisco Systems, Inc. All rights reserved.
Slide 10
73
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
– Manual Tunnel (RFC 4213) strongly engaged IETF, ICANN, and RIR – GRE (RFC in2473)
Preparations for Transition
Established networks that are processes appear to be taking appropriate measures in anticipation of the IPv6 transition. However, lessons from past transitions indicate that there may be some businesses that are not as aware or prepared. 90 Unprepared businesses could begin to experience connectivity and service issues, – Tunnel b roker 91 and difficulty acquiring additional IPv4 addresses. A business that delays transition could find it costly to achieved on a compressed schedule. 92
• Semi-‐automated • Automa;c
6to4 (RFC 3056) – been 6rd IP address blocks have historically 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 RIR address policy. If an address block was not – TEREDO (RFC 4380) – IPv4 Allocations and Transfers
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 NAT-PT Interface
IPv6 Interface
ipv6 nat prefix
IPv4 Host
IPv6 Host
2001:db8:1987:0:2E0:B0FF:FE6A:412C
172.16.1.1
• 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 NANOG 42
82
• combined with DNS64
© 2008 Cisco Systems, Inc. All rights reserved.
Slide 12
End of Today’s Lecture
THANK YOU ... Any Ques;on?
Slide 13
