AN 02 - IPv6 - 2013

KOM15007:
Jaringan Komputer Lanjut

Topik: IPv6
Semester Ganjil
PTIIK Universitas Brawijaya
http://elearning.ptiik.ub.ac.id
Materi Perkuliahan
Review Jaringan Komputer

IPv6
Algoritma Rou@ng
Intra-domain Rou@ng
Inter-domain Rou@ng
Policy Rou@ng
Overlay Network
Data Center Networking
Content Delivery Network
MK: Jaringan Komputer Lanjut
Slide 2
Evaluasi & Nilai
Mata Kuliah ini

-
3 SKS
Evaluasi
Keaktifan dalam perkuliahan

Tugas Praktik/Diskusi/Presentasi
UTS
UAS
5%
50%
20%
25%
Slide 3
Kuliah Hari ini

IPv6:
Addressing
Notation
Transition to IPv6
Slide 4
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) rened in 1998 (RFC 2460)

As early as 1990, IETF started to work on IPng, solving IPv4
address shortage issue
IETF ini@ated the standard in 1994
why not IPv5?
Slide 5
What were the major goals of

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 specied
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 6
Do we really need larger IP address space?
Worlds Total Popula5on (est.) = 7 Billion

Worlds Total Internet users = 2.4 Billion
Slide 7
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
Popula@on: 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 8
What is the problem with IPv4?

Problems
rapid increase of the size of rou@ng tables
450,000+ entries in the Internet now
was predicted that IPv4 will exhaust by 2008.

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
Remaining = 220,922 /8 = about 3.7 billion addresses
Slide 9
What is the problem with IPv4?

IPv4 address exhaus@on is the deple@on of the pool
of unallocated IPv4 addresses
IANAs Unallocated Address Pool Exhaus@on:
03-Feb-2011
Projected RIR Address Pool Exhaus@on 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 10
To reduce/slowdown
IPv4 address deple@on
Classless Inter Domain Rou@ng (CIDR)
Network Address Transla@on (NAT)
Slide 11
Can NAT solve the problems ?

NAT : Network Address Transla@on
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
Private
Address Space
175.45.188.1
192.0.0.2
192.0.0.1
192.0.0.2
Slide 12
One solu@on 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 iden@er/communica@on model
Slide 13
Why not NAT ?

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.
Slide 14
Why 128 bits then?

Room for many levels of structured hierarchy and
rou@ng aggrega@on
Easier address management and delega@on than
IPv4
Easy address auto-congura@on
Ability to deploy end-to-end IPsec
(NATs removed as unnecessary)
Slide 15
IPv6
started in 1994
Whats good about IPv6

Larger Address space
128 bit: 3.4 * 1038
Re-design to solve the current problems such as;

Ecient and hierarchical addressing and rou@ng
infrastructure
Security
Auto-congura@on
Plug & Play
Beeer support for QoS
Extensibility
Slide 17
Is IPv6 really good ?

IPv6 cannot easily solve (same as IPv4);
Security
Mul@cast
Mobile
QoS
Slide 18
IPv6 Addressing
00101010000100100011010001011100
00000000000000000000000000000000
00000000011110000000100110101011
00001100000011011110000011110000
A 128 bit value
Represen@ng an interface on the network
Slide 19
IPv6 Address Nota@on
2A12:3456:0:0:78:9AB:C0D:E0F0
Slide 20

Eight blocks of 16 bits in hexadecimal
separated by colons (::)
2A12:3456:0:0:78:9AB:C0D:E0F0
00101010000100100011010001011100
00000000000000000000000000000000
00000000011110000000100110101011
00001100000011011110000011110000
Slide 21

2A12:3456:0:0:78:9AB:C0D:E0F0
00101010000100100011010001011100
00000000000000000000000000000000
00000000011110000000100110101011
00001100000011011110000011110000
Slide 22

2A12:3456:0:0:78:9AB:C0D:E0F0
00101010000100100011010001011100
00000000000000000000000000000000
00000000011110000000100110101011
00001100000011011110000011110000
Slide 23

2A12:3456:0:0:78:9AB:C0D:E0F0
00101010000100100011010001011100
00000000000000000000000000000000
00000000011110000000100110101011
00001100000011011110000011110000
Slide 24

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 25
IPv6 Address Space Nota@on

<prefix>/<prefix-length>
1234:5678::/48
1234:5678:9ABC:DEF::/64
Slide 26
IPv6 Address Types

Unicast
Single interface
Mul@cast
Set of interfaces
Packets delivered to all interfaces
Anycast
Set of interfaces
Packets delivered to one (the nearest) interface
Slide 27
Address Type Iden@ca@on

Type
Binary Value/Prefix
IPv6 Notation
Unspecified
0000 (128bits)
::/128
Loopback
0001 (128bits)
::1/128
Multicast
11111111
FF00::/8
Link-local unicast
1111111010
FE80::/10
Global unicast
(everything else)
Slide 28
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 aggrega@on iden@er

RES
Reserved for future use
NLA ID Next-level aggrega@on iden@er
SLA ID Site-level aggrega@on iden@er
Interface ID Interface iden@er
Slide 29
An Interfaces Unicast Address
Network Prefix
Interface ID
64 bits
64 bits
A links prex length is always 64 bit
Slide 30
Alloca@ng IPv6 Address Space
2001:df0:ba::/48
16 bits for links network prexes = 65k
Slide 31
Interface Iden@er
Interface ID: manual or automa@c
Automa@c: Modied EUI-64 of MAC address
Complement 2nd LSB of 1st byte
Insert 0xfe between 3rd and 4th bytes
MAC: 00-12-34-56-78-9a
Interface ID: 212:34ff:fe56:789a
Slide 32
Link-local Address Format

fe80::<Interface-ID>

KAME style
fe80:<Interface-ID>%<ifname>
fe80::212:34ff:fe56:789a%fxp0
Slide 33
Mul@cast 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 organiza@on-local scope
E global scope
Slide 34
Mul@cast Address Example

ff02::2
Well-known address, link-local scope
ff18::100
Temporary address, organiza@on-local scope
Slide 35
A Nodes Address
Loopback Address
Link-local Address for each interface
Addi@onal Unicast and Anycast Addresses
All-Nodes Mul@cast Addresses (02::1)
Solicited-Node Mul@cast Addresses
Mul@cast Addresses of groups it joined
Slide 36
A Routers Address
A nodes address
Subnet-Router Anycast Addresses
All other Anycast Addresses
All-Router Mul@cast Addresses (02::2)
Slide 37
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 Address
128 bits
Source IP Address
Destination IP Address
IP Options (with padding if necessary)
IPv4 header
Destination Address
128 bits
IPv6 header
Slide 38
What are missing from IPv4 in IPv6?

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
xed-length 40-byte IP header
no longer a part of standard IP header
but, there is next header

Slide 39
What about the transi@on

from IPv4 to IPv6?
Slide 40
Transi@oning 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 trac through an IPv4

network transparently
to avoid dependencies when upgrading hosts, routers, or

regions
3. Transla5on: Conver@ng IPv6trac to IPv4 trac for

transport and vice versa
to allow IPv6-only devices to communicate with IPv4-only devices

Slide 41
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
ns 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)

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.
S72lide 42
72
Dual Stack & DNS
Dual-Stack Approach
www.a.com
=*?
DNS
Server
IPv4
2001:db8::1
10.1.1.1
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
Slide 43
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 congured
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 44
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
Slide 45
Bertanyalah, sebelum anda ditanya!

Ada pertanyaan?
END OF LECTURE #2
46

AN 02 - IPv6 - 2013

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

AN 02 - IPv6 - 2013

Enviado por

Direitos autorais:

Formatos disponíveis

KOM15007:

Jaringan Komputer Lanjut

Review Jaringan Komputer

Evaluasi & Nilai

Mata Kuliah ini

Keaktifan dalam perkuliahan

MK: Jaringan Komputer Lanjut

Kuliah Hari ini

MK: Jaringan Komputer Lanjut

When was IP address standardized?

IPv6 in 1995 (RFC 1883) rened in 1998 (RFC 2460)

What were the major goals of

Support billions of hosts

Do we really need larger IP address space?

Worlds Total Popula5on (est.) = 7 Billion

MK: Jaringan Komputer Lanjut

How about in Indonesia?

What is the problem with IPv4?

was predicted that IPv4 will exhaust by 2008.

MK: Jaringan Komputer Lanjut

What is the problem with IPv4?

Projected RIR Address Pool Exhaus@on Dates:

MK: Jaringan Komputer Lanjut

Can NAT solve the problems ?

One solu@on NAT

MK: Jaringan Komputer Lanjut

Why not NAT ?

NAT breaks Bi-direc@onal communica@on

MK: Jaringan Komputer Lanjut

Why 128 bits then?

MK: Jaringan Komputer Lanjut

Whats good about IPv6

Re-design to solve the current problems such as;

Is IPv6 really good ?

MK: Jaringan Komputer Lanjut

IPv6 Address Nota@on

MK: Jaringan Komputer Lanjut

IPv6 Address Nota@on

IPv6 Address Nota@on

IPv6 Address Nota@on

IPv6 Address Nota@on

IPv6 Address Nota@on

MK: Jaringan Komputer Lanjut

IPv6 Address Space Nota@on

MK: Jaringan Komputer Lanjut

IPv6 Address Types

MK: Jaringan Komputer Lanjut

Address Type Iden@ca@on

MK: Jaringan Komputer Lanjut

Global Aggregatable Unicast Address

3 bits 13 bits 8 bits 24 bits 16 bits

TLA ID Top-level aggrega@on iden@er

MK: Jaringan Komputer Lanjut

An Interfaces Unicast Address

A links prex length is always 64 bit

MK: Jaringan Komputer Lanjut

Alloca@ng IPv6 Address Space

MK: Jaringan Komputer Lanjut

MK: Jaringan Komputer Lanjut

Link-local Address Format

MK: Jaringan Komputer Lanjut

Mul@cast Address Format

MK: Jaringan Komputer Lanjut

Mul@cast Address Example