Survey
* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project
Download IPv6 Naming
Document related concepts
no text concepts found
Transcript
KOM15032: Arsitektur Jaringan Terkini #03 – Addressing: 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, PaQerns in Network Architecture: A Return to Fundamentals. Pearson. 2007. Slide 2 KOM15032: Course Purposes • memahami berbagai kelebihan dan kekurangan arsitektur jaringan komputer saat ini. • mengerW 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% • AkWfitas/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 and Naming" Slide 6 IP Addressing • How many IP address? – IPv4: 2^32 = 4.3 * 109 (Billion) – IPv6: 2^128 = 3.4 * 1038 (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 • IETF iniWated the standard in 1994 • why not IPv5? Slide 7 What were the major goals of IPv6? • • • • • • • • • Support billions of hosts Reduce the size of the rouWng tables Simplify the protocol Provide beQer security (authenWcaWon & privacy) Pay more aQenWon to QoS Aid mulWcasWng by allowing scoped to be specified Allowing a host to roam without changing its address Allow the protocol to evolve in future Permit the old and new protocols to coexist for years Slide 8 Do we really need larger IP address space? World’s Total PopulaFon (est.) = 7 Billion World‘s Total Internet users = 2.4 Billion Slide 9 How about in Indonesia? • From CIA’ factbook: – mobile phone users: 249.8 million in 2011 – Internet users: 20 million in 2009 – Internet hosts: 1.344 million in 2012 – PopulaWon: 248,6 million (est. 2012, no. 4 in the world) – Total IP addresses: (source: maxmind.com) • 18,901,572 • compared to – US: 1,561,999,807 – CN: 330,426,276 – JP: 205,213,640 Slide 10 What is the problem with IPv4? • Problems – rapid increase of the size of rouWng tables • 450,000+ entries in the Internet now – was predicted that IPv4 will exhaust by 2008. • TheoreWcal limit: 4 billion devices • PracWcal limit: 250 million devices (RFC 3194) Slide 11 To reduce/slowdown IPv4 address depleWon • Classless Inter Domain RouWng (CIDR) • Network Address TranslaWon (NAT) Slide 12 Can NAT solve the problems ? • NAT : Network Address TranslaWon – Assign private addresses to the internal systems – Router translate the addresses 175.45.188.1 175.45.190.1 Global IP address Space 192.0.0.1 Private Address Space NAT NAT 175.45.188.1 Private Address Space 192.0.0.2 192.0.0.1 192.0.0.2 Slide 13 One soluWon – NAT • NAT(Network Address Translator) – Popular on Dial-‐ups, SOHO and VPN networks – will save IPv4 address – lost of the end-‐to-‐end model – Asymmetric idenWfier/communicaWon model Slide 14 Why not NAT ? • NAT breaks “end-‐to-‐end communicaWon” – Routers monitors the communicaWon – Routers changes the data • NAT breaks “Bi-‐direcWonal communicaWon” – Hosts with global address can not iniWate the communicaWon to the hosts with private address. Slide 15 What is the problem with IPv4? • IPv4 address exhausWon is the depleWon of the pool of unallocated IPv4 addresses • IANA’s Unallocated Address Pool ExhausWon: – 03-‐Feb-‐2011 • Projected RIR Address Pool ExhausWon Dates: – APNIC: 19-‐Apr-‐2011 (actual) 0.8857 – RIPE NCC: 14-‐Sep-‐2012 (actual) 0.9264 – LACNIC: 04-‐Jul-‐2014 2.5137 – ARIN: 05-‐Jul-‐2014 2.9267 – AFRINIC: 07-‐Oct-‐2020 3.7892 *source: ipv4.potaroo.net Slide 16 Why 128 bits then? • Room for many levels of structured hierarchy and rouWng aggregaWon • Easier address management and delegaWon than IPv4 • Easy address auto-‐configuraWon • Ability to deploy end-‐to-‐end IPsec (NATs removed as unnecessary) Slide 17 IPv6 started in 1994 What’s good about IPv6 • Larger Address space – 128 bit: 3.4 * 1038 • Re-‐design to solve the current problems such as; – Efficient and hierarchical addressing and rouWng infrastructure – Security – Auto-‐configuraWon – Plug & Play – BeQer support for QoS – Extensibility Slide 19 Is IPv6 really good ? • IPv6 cannot easily solve (same as IPv4); – Security – MulWcast – Mobile – QoS Slide 20 IPv6 Addressing 00101010000100100011010001011100 00000000000000000000000000000000 00000000011110000000100110101011 00001100000011011110000011110000 A 128 bit value RepresenWng an interface on the network Slide 21 IPv6 Address NotaWon 2A12:3456:0:0:78:9AB:C0D:E0F0 Slide 22 IPv6 Address NotaWon Eight blocks of 16 bits in hexadecimal separated by colons (::) 2A12:3456:0:0:78:9AB:C0D:E0F0 00101010000100100011010001011100 00000000000000000000000000000000 00000000011110000000100110101011 00001100000011011110000011110000 Slide 23 IPv6 Address NotaWon Eight blocks of 16 bits in hexadecimal separated by colons (::) 2A12:3456:0:0:78:9AB:C0D:E0F0 00101010000100100011010001011100 00000000000000000000000000000000 00000000011110000000100110101011 00001100000011011110000011110000 Slide 24 IPv6 Address NotaWon Eight blocks of 16 bits in hexadecimal separated by colons (::) 2A12:3456:0:0:78:9AB:C0D:E0F0 00101010000100100011010001011100 00000000000000000000000000000000 00000000011110000000100110101011 00001100000011011110000011110000 Slide 25 IPv6 Address NotaWon Eight blocks of 16 bits in hexadecimal separated by colons (::) 2A12:3456:0:0:78:9AB:C0D:E0F0 00101010000100100011010001011100 00000000000000000000000000000000 00000000011110000000100110101011 00001100000011011110000011110000 Slide 26 IPv6 Address NotaWon • Blocks of 0 may be shortened with double colon (::) ; but only one :: is allowed 1234:5678:90AB::5678:0:CDEF 1234:5678:90AB:0:0:5678::CDEF 1234:5678:90AB::5678::CDEF Slide 27 IPv6 Address Space NotaWon <prefix>/<prefix-length> 1234:5678::/48 1234:5678:9ABC:DEF::/64 Slide 28 IPv6 Address Types • Unicast – Single interface • MulWcast – Set of interfaces – Packets delivered to all interfaces • Anycast – Set of interfaces – Packets delivered to one (the nearest) interface Slide 29 Address Type IdenWficaWon 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) Slide 30 Global Aggregatable Unicast Address Format Prefix TLA ID RES NLA ID SLA ID 001 Interface ID 3 bits 13 bits 8 bits 24 bits 16 bits 64 bits TLA ID Top-‐level aggregaWon idenWfier RES Reserved for future use NLA ID Next-‐level aggregaWon idenWfier SLA ID Site-‐level aggregaWon idenWfier Interface ID Interface idenWfier Slide 31 An Interface’s Unicast Address Network Prefix Interface ID 64 bits 64 bits A link’s prefix length is always 64 bit Slide 32 AllocaWng IPv6 Address Space 2001:df0:ba::/48 • 16 bits for link’s network prefixes = 65k Slide 33 Interface IdenWfier • Interface ID: manual or automaWc • AutomaWc: Modified EUI-‐64 of MAC address – Complement 2nd LSB of 1st byte – Insert 0xfffe between 3rd and 4th bytes • MAC: 00-12-34-56-78-9a • Interface ID: 212:34ff:fe56:789a Slide 34 Link-‐local Address Format fe80::<Interface-ID> KAME style fe80:<Interface-ID>%<ifname> fe80::212:34ff:fe56:789a%fxp0 Slide 35 MulWcast Address Format Prefix 1111 1111 8 bits FLAGS SCOPE 4 bits 4 bits Flags: LSB = 0 well-‐known mcast address LSB = 1 temporary/transient mcast address Group Identifier 112 bits Scope: 1 interface-‐link scope 2 link-‐local scope 5 site-‐local scope 8 organizaWon-‐local scope E global scope Slide 36 MulWcast Address Example ff02::2 • Well-‐known address, link-‐local scope ff18::100 • Temporary address, organizaWon-‐local scope Slide 37 A Node’s Address • • • • • • Loopback Address Link-‐local Address for each interface AddiWonal Unicast and Anycast Addresses All-‐Nodes MulWcast Addresses (ff02::1) Solicited-‐Node MulWcast Addresses MulWcast Addresses of groups it joined Slide 38 A Router’s Address • • • • A node’s address Subnet-‐Router Anycast Addresses All other Anycast Addresses All-‐Router MulWcast Addresses (ff02::2) Slide 39 IPv4 vs IPv6 Header 32 bits Ver. 4 HL TOS Datagram-ID TTL Protocol 32 bits Datagram Length Flags Flag Offset Ver. Traffic class 6 8 bits Payload Length 16 bits Flow label 20 bits Next Hdr. 8 bits Hop Limit 8 bits Header Checksum Source IP Address Source Address 128 bits Destination IP Address IP Options (with padding if necessary) IPv4 header Destination Address 128 bits IPv6 header Slide 40 What are missing from IPv4 in IPv6? • FragmentaWon/Reassembly – IPv6 do not allow for fragmentaWon/reassembly • Header checksum – Because Transport layer and data link-‐layer have handle it • OpWons – fixed-‐length 40-‐byte IP header – no longer a part of standard IP header – but, there is next header Slide 41 What about the transiWon from IPv4 to IPv6? Slide 42 End of Today’s Lecture THANK YOU ... Any QuesWon? Slide 43
Related documents