E1-E2 - Text - Chapter 4. IPV6
E1-E2 - Text - Chapter 4. IPV6
E1-E2 - Text - Chapter 4. IPV6
4 IPV6
4.1 LEARNING OBJECTIVES
Limitations Of IPv4
IPv6 Address Presentation
Features Of IPv6
IPv6 Header Format
IPv6 Prefixes & Types
The IPv6 Interface Id And Eui-64 Format
The IPv6 Address Hierarchy
Multicast Ipv6 Address
4.1 INTRODUCTION
Internet Protocol version 6 (IPv6) is the sixth revision in the development of the
Internet Protocol (IP) and the second version of the protocol to be widely deployed.
Together with IPv4, it is at the core of standards-based internetworking methods of the
Internet.
The current version of IP - IPv4 has not changed substantially since RFC 791,
which was published in 1981. IPv4 has proven to be robust, easily implemented, and
interoperable. It has stood up to the test of scaling an internetwork to a global utility the
size of today‘s Internet. This is a tribute to its initial design.
However, the initial design of IPv4 did not anticipate the areas like growth of
internet, need for simpler configuration, security consideration, support for prioritized
and real-time delivery of data etc.
4.2 IPV4
Limitations of IPv4
Features of IPv6
Uses of IPv6
hundred million. As a result, public IPv4 addresses have become relatively scarce,
forcing many users and some organizations to use a NAT (Network Address
Translation) to map a single public IPv4 address to multiple private IPv4 addresses.
4.3.4 Security
Private communication over a public medium such as the Internet requires
cryptographic services that protect the data being sent from being viewed or modified in
transit. Although a standard now exists for providing security for IPv4 packets (known
as Internet Protocol security, or IPsec), this standard is optional for IPv4 and additional
security solutions, some of which are proprietary, are prevalent.
4.3.5 Mobility
The problem of mobility for IPv4 was first addressed in a standards track specification,
RFC 2002, ―IP Mobility Support,‖ in 1996. But this mobility is limited in true sense.
for configuring services like NAT which is mainly because of scarcity of IPv4
resources.
0000001010101010000000001111111111111110001010001001110001011010
can be represented as :
An Address having more than one zeros can be represented as double colon ::
( Double Colon )
can be written as
Even with all of the addresses currently assigned for use by hosts, plenty of addresses
are available for future use. With a much larger number of available addresses, address-
conservation techniques, such as the deployment of NATs, are no longer necessary.
With IPv6, NATs are no longer necessary to conserve public address space, and the
problems associated with mapping addresses and ports disappear for developers of
applications and gateways. More importantly, end-to-end communication is restored
between hosts on the Internet by using addresses in packets that do not change in
transit. This functional restoration has immense value when one considers the
emergence of peer-to-peer telephony, video, and other real-time collaboration
technologies for personal communications etc.
By restoring global addressing and end-to-end connectivity, IPv6 has no barrier to new
applications that are based on ad hoc connectivity and peer-based communication.
There are different types of IPv6 addresses with different scopes. When multiple IPv6
addresses are returned in a DNS name query, the sending node must be able to
distinguish their types and, when initiating communication, use a pair (source address
and destination address) that is matched in scope and that is the most appropriate pair to
use. For example, for a source and a destination that have been assigned both global
(public) and link-local addresses, a sending IPv6 host would never use a global
destination with a link-local source. IPv6 sending hosts include the address selection
logic that is needed to decide which pair of addresses to use in communication.
Moreover, the address selection rules are configurable.
The benefit of scoped addresses is that by using the set of addresses of the smallest
scope, your traffic does not travel beyond the scope for the address, exposing your
network traffic to fewer possible malicious hosts.
IPv4 headers and IPv6 headers are not interoperable. IPv6 is not a superset of
functionality that is backward compatible with IPv4.
Implementation of both IPv4 and IPv6 to recognize and process both header formats.
The new default IPv6 header is only twice the size of the default IPv4 header, even
though the number of bits in IPv6 addresses is four times larger than IPv4 addresses.
4.5.9 Extensibility
IPv6 can easily be extended for new features by adding extension headers after the IPv6
header. Unlike options in the IPv4 header, which can support only 40 bytes of options,
the size of IPv6 extension headers is constrained only by the size of the IPv6 packet.
The business benefit of requiring support for IPsec and using a single, global address
space is that IPv6 can protect packets from end to end across the entire IPv6 Internet.
Unlike IPsec on the IPv4 Internet, which must be modified and has limited functionality
when the endpoints are behind NATs, IPsec on the IPv6 Internet is fully functional
between any two endpoints.
The IPv4 header has two 4-byte addresses preceded by 12 bytes of control
information and possibly followed by option data. The reduction of the control
information and the elimination of options in the header for most IP packets
optimizes the processing time per packet in a router. The infrequently used fields
removed from the header are moved to optional extension headers when they are
required.
The IPv6 header has 8 fields and is 320 bits long. It has been considerably
streamlined compared to its IPv4 counterpart, which has 12 fields and is 160 bits
long.
Several such extension headers exist, and are usually processed in the following order:
Routing Header – specifies each router the packet must traverse to reach the
destination (source routing)
Fragment Header – used when a packet is larger than the MTU for the path
Authentication Header – used to integrate IPSEC Authentication Header (AH) into the
IPv6 packet
ESP Header – used to integrate IPSEC Encapsulating Security Payload (ESP) into the
IPv6 packet
Prefixes for IPv6 subnet identifiers, routes, and address ranges are expressed in the
same way as Classless Inter-Domain Routing (CIDR) notation for IPv4.
Examples:
The /64 indicates that the first 64 bits of this address identify the prefix.
IPv6 unicasts generally allocate the first 64 bits of the address to identify the network
(prefix), and the last 64 bits to identify the host (referred to as the interface ID). The
interface ID is based on the interface‘s hardware address.
This interface ID adheres to the IEEE 64-bit Extended Unique Identifier (EUI-64)
format. Since most interfaces still use the 48-bit MAC address, the MAC must be
converted into the EUI-64 format.
Consider the following MAC address: 1111.2222.3333. The first 24 bits, the
Organizationally Unique Identifier (OUI), identify the manufacturer. The last 24 bits
uniquely identify the host. To convert this to EUI-64 format:
1. The first 24 bits of the MAC (the OUI), become the first 24
bits of the EUI-64 formatted interface ID.
2. The seventh bit of the OUI is changed from a ―0‖ to a ―1‖.
3. The next 16 bits of the interface ID are FFFE.
4. The last 24 bits of the MAC (the host ID), become the last 24
bits of the interface ID.
Thus, the MAC address 1111.2222.3333 in EUI-64 format would become
The address space that has been allocated is organized into several types, determined by
the high-order bits of the first field:
There are no broadcast addresses in IPv6. Thus, any IPv6 address that is not a
multicast is a unicast address.
Practical applications of anycast addressing are a bit murky. One possible application
would be a server farm providing an identical service or function, in which case anycast
addressing would allow clients to connect to the nearest server.
Reserved addresses represent 1/256th of the available IPv6 address space. Various
reserved addresses exist, including:
Two types of addresses can be used for IPv4 embedding, IPv4-compatible IPv6
addresses, and IPv4-mapped IPv6 addresses.
::192.168.1.1/96
The first field of a link-local IPv6 address will always begin FE8x (1111 1110 10).
Link-local addresses are unicasts, and represent 1/1024th of the available IPv6 address
space. A prefix of /10 is used for link-local addresses.
FE80::1311:22FF:FE22:3333/10
The first 10 bits are fixed (FE8), known as the Format Prefix (FP).
The first field of a site-local IPv6 address will always begin FECx (1111 1110 11).
Site-local addresses are unicasts, and represent 1/1024th of the available IPv6 address
space.
FEC0::2731:E2FF:FE96:C283/64
Currently, the first field of an aggregate global IPv6 address will always begin 2xxx
(001). Aggregate global addresses are unicasts, and represent 1/8th of the available IPv6
address space.
2001::2731:E2FF:FE96:C283/64
The next 24 bits are the next-level aggregation identifier (NLA ID).
The next 16 bits are the site-level aggregation identifier (SLA ID).
The final 64 bits are used as the interface ID.
By have multiple levels, a consistent, organized, and scalable hierarchy is maintained.
High level registries are assigned ranges of TLA IDs. These can then be subdivided in
the NLA ID field, and passed on to lower-tiered ISPs.
Such ISPs allocate these prefixes to their customers, which can further subdivide the
prefix using the SLA ID field, to create whatever local hierarchy they wish. The 16-bit
SLA field provides up to 65535 networks for an organization.
Note: Do not confuse the SLA ID field of a global address field, with a site- local
address. Site-local addresses cannot be routed publicly, where as SLA ID‘s are just a
subset of the publicly routable aggregate global address.
The first field of a multicast IPv6 address will always begin FFxx (1111 1111). The
full multicast range is FF00 through FFFF. Multicasts represent 1/256th of the
available IPv6 address space.
FF01:0:0:0:0:0:0:1
FEC0::1111:2731:E2FF:FE96:C283
FF02::1:FF96:C283
Solicited-node multicast addresses are most often used for neighbor discovery (covered
in an upcoming section in this guide).
4.18 CONCLUSION
There are many reasons for IPv6 supports and there is also need to migrate from
current version of Internet IPv4 to IPv6 for availing additional benefits of Internet.
However, for quite some time, things will move in parallel and smooth transition will
be in benefit for the Internet world. Therefore, we will see IPv4 and IPv6
simultaneously being used by the Internet users, and the service provider. Also the
application that will be developed during this phase will also keep in mind the
requirement of IPv4 and IPv6.