Computer

Networks
L. Budi Handoko, M.Kom. (handoko@dsn.dinus.ac.id)
Dian Nuswantoro University
Introduction to Computer Networks
(IPv4 Compare To IPv6)
Introduction to Computer Networks
(IPv6)
Introduction to Computer Networks
(IPv6 - Features)

• Larger Address Space

• Aggregation-based address hierarchy
– Efficient backbone routing
• Efficient and Extensible IP datagram
• Stateless Address Autoconfiguration
• Security (IPsec mandatory)
• Mobility
Introduction to Computer Networks
(IPv6 - Deployment)
• Dual-stack backbone
Both version is used on the network and the application will select the correct address based on
the type of IP traffic and particular requirements of the communication.
• IPv6 over IPv4 tunneling
Encapsulating IPv6 traffic within IPv4 packets, to be sent over an IPv4 backbone.
• NAT-PT (Network Address Translation and Protocol Translation)
Deprecated due to numerous problems.
Introduction to Computer Networks
(IPv6 – Stateless Autoconfiguration)

• Assign IP Address automaticaly without need of DHCP Server present

• Get the address from ICMPv6 and Neighbor Discovery Protocol
• Use MAC Address as the basis of IPv6 addressing
• Using Modified EUI-64 (Convert EUI-48 from MAC into EUI-64 for IPv6)
Introduction to Computer Networks
(IPv6 – Convert EUI-48 to EUI-64)

• Reference from IEEE (RFC 2373)

• Conver 48-bit MAC into 64-bit MAC by

inserting FF FE in the middle of MAC
Address

• Invert the universal/local (U/L) flag (bit

7) in the OUI portion of the address
Introduction to Computer Networks
(IPv6 – Modified EUI-64)
Introduction to Computer Networks
(IPv6 – Address Space)

IP IP
Allocation Reference Allocation Reference
Prefix Prefix
0000::/8 Reserved by IETF RFC 4291 A000::/3 Reserved by IETF RFC 4291

0100::/8 Reserved by IETF RFC 4291 C000::/3 Reserved by IETF RFC 4291

0200::/7 Reserved by IETF RFC 4048 E000::/4 Reserved by IETF RFC 4291

0400::/6 Reserved by IETF RFC 4291 F000::/5 Reserved by IETF RFC 4291

0800::/5 Reserved by IETF RFC 4291 F800::/6 Reserved by IETF RFC 4291

1000::/4 Reserved by IETF RFC 4291 FC00::/7 Unique Local Unicast RFC 4193

2000::/3 Global Unicast RFC 4291 FE00::/9 Reserved by IETF RFC 4291

4000::/3 Reserved by IETF RFC 4291 FE80::/10 Link Local Unicast RFC 4291

6000::/3 Reserved by IETF RFC 4291 FEC0::/10 Reserved by IETF RFC 3879

8000::/3 Reserved by IETF RFC 4291 FF00::/8 Multicast RFC 4291

Introduction to Computer Networks
(IPv6 – Allocation)
• 2000::/3 — Only one eighth of the total address space is currently allocated for use on the Internet.
• ::/128 — The address with all zero bits is called the unspecified address (corresponding to 0.0.0.0/32 in
IPv4)
• ::/0 — The default unicast route (default route) address (corresponding to 0.0.0.0/0 in IPv4)
• ::1/128 — The loopback address is a unicast localhost address. If an application in a host sends packets
to this address, the IPv6 stack will loop these packets back on the same virtual interface (corresponding
to 127.0.0.0/8 in IPv4)
• fe80::/10 — Addresses in the link-local prefix are only valid and unique on a single link. Within this
prefix only one subnet is allocated (54 zero bits), yielding an effective format of fe80::/64. The least
significant 64 bits are usually chosen as the interface hardware address constructed in modified EUI-64
format. A link-local address is required on every IPv6-enabled interface, in other words, applications
may rely on the existence of a link-local address even when there is no IPv6 routing. These addresses
are comparable to the auto-configuration addresses 169.254.0.0/16 of IPv4.
Introduction to Computer Networks
(IPv6 – Allocation Continues)

• fc00::/7 — Unique local addresses (ULAs) are intended for local communication. They are routable only
within a set of cooperating sites (analogous to the private address ranges 10.0.0.0/8, 172.16.0.0/12, and
192.168.0.0/16 of IPv4)
• Transition from IPv4
• ::ffff:0:0/96 — This prefix designated an IPv4-mapped IPv6 address. With a few exceptions, this address type
allows the transparent use of the Transport Layer protocols over IPv4 through the IPv6 networking application
programming interface
• ::ffff:0:0:0/96 — A prefix used for IPv4-translated addresses which are used by the Stateless IP/ICMP Translation
(SIIT) protocol
• 64:ff9b::/96 — The "Well-Known" Prefix. Addresses with this prefix are used for automatic IPv4/IPv6 translation
• 2002::/16 — This prefix is used for 6to4 addressing. Here, an address from the IPv4 network 192.88.99.0/24 is
also used
Introduction to Computer Networks
(IPv6 – Allocation Continues)
• Special-purpose addresses
• 2001::/32 — Used for Teredo tunneling (which also falls into the category of IPv6 transition mechanisms)
• 2001:2::/48 — Assigned to the Benchmarking Methodology Working Group (BMWG) for benchmarking IPv6
(corresponding to 198.18.0.0/15 for benchmarking IPv4)
• 2001:10::/28 — ORCHID (Overlay Routable Cryptographic Hash Identifiers)
• 2001:db8::/32 — This prefix is used in documentation. The addresses should be used anywhere an
example IPv6 address is given or model networking scenarios are described (corresponding to
192.0.2.0/24, 198.51.100.0/24, and 203.0.113.0/24 in IPv4)
 Any Question ?

Anything to discuss ?