EI IPv4-6

IPv4 TO IPv6
INFORMATION TECHNOLOGY
rM AlSz
Engineering Instructions for
GENERAL DESCRIPTION OF IPv4 TO IPv6
msZ xZr Document No.
EI/ IPv4 TO IPv6/11-12/22
mxZr No of Pages.
e AU M xSp GR reference
:
:
23
-
xv|kl qM (rS
(rS MD) Amendment
No. (If any)
m xv|ki Page Nos. Amended
eUMi Issued By
NIL
:
:
NIL
Telecom Quality Assurance circle, Bangalore
AlqSi Approved by
The CGM, TQA circle, Bangalore
eU MUl M SlM Date of Issue
11-11-2011
Written by
RAMESH CHANDRA YADAV (QA Circle)
Expert Comments
MAMATHA N K & LAKSHMIRAMANATHAN (QA Circle)
Restricted use by BSNL Employees only
All efforts have been made to incorporate all relevant up to date information available, any discrepancies
or need for addition or deletion is felt necessarily may please be intimated to this office for further
improvement,on E-Mail Id cgmtqa_ei@ bsnl.co.in (or) cgmtqa.ei@gmail.com
qZr qW mokM M Mrsr

SxcU ah Azuxl mUqhQs
SxU qes, xcU MqmsYx,
Qosr Lq Lx MqmhQ 41 u x,
9 u qZr Uxi, 5 u osM, erlaU
oasU 560 041
Office of Chief General Manager

Telecom Quality Assurance circle
II Floor, Sanchar Complex,
BSNL-WMS Compound, 9th Main,
Jayanagar 5th Block, Bangalore - 560 041
Tel: 91 80 26533100 Fax: 91 80
26530681
Visit us at www.qa.bsnl.co.in
DISCLAIMER: FOR INTERNAL CIRCULATION AMONG BSNL EMPLOYEES AS A GUIDELINE FOR

INSTRUCTIONAL PURPOSE.
IPv4 TO IPv6
CONTENTS
Sl. No.
1.
Description
Scope
Page No.
3
2.
Introduction
3.
Present System of Internet addressing
4.
IPv4: Short Comings and Limitations
5.
Requirements of IPv6
6.
Advantages of IPv6
7.
To Transition To IPv6 Or Not
8.
Key Differences Between IPv4 and IPpv6
9.
How To Switch From IPv4 to IPv6
10.
Migration From IPv4 to IPv6
11.
Deployment Strategy / Recommendations
15
12.
Migration Plan
18
13.
List Of Abbreviations
21
14.
References
23
IPv4 TO IPv6
1.0 SCOPE:
This book gives a general guideline and need for transition from IPv4 to IPv6.
2.0 INTRODUCTION:
IPv4 stands for Internet Protocol version 4. It is the underlying technology that makes it
possible for us to connect our devices to the network and also the web. Whenever a device
accesses the Internet (whether its a PC, Mac, Smartphone or other device), it is assigned a
unique numerical IP address such as 99.48.227.227. to send or receive data from one
computer to another in the network.
IP address is essential to the infrastructure of the web as computers will not be able to
communicate with each other without IP addresses. With growing number of computers and
handheld devices, it has become essential to enhance the limited addresses to an advance
system to meet the future requirements.
3.0 PRESENT SYSTEM OF INTERNET ADDRESSING:

At present, we are using IPv4 system for addressing of internet sites. It has 4 bytes of
address. It is used in four groups of one byte each. It can be anything between
000:000:000:000 to 255:255:255:255. Thus we can generate an IP pool of up to 28.28.28.28
=232 addresses. Thus technically, we can have a maximum of 232 = 4,294,967,296 addresses.
These addresses are divided into pools or categories such as A B C & D. Much of the address
space available is reserved by different organizations for their use. Address open for use by
everybody is very limited. Hence, the need arises to develop an addressing system which can
cater our growing demand.
4.0 IPv4 :SHORTCOMINGS AND LIMITATIONS:

Major weakness of IPv4 is its limited addressing space, as in this, an address consists of
just 32 bits thereby limiting the total number of addresses to about 2 billion only. The rapid
growth of Internet, leading to accelerated consumption of IP addresses, has led to the anxiety
about shortage of IP addresses in coming years specially in Asia Pacific region. Already, the
limits of IPv4's addressing system have started pushing the usage of processes such as
Network Address Translation (NAT) and the Classless Interdomain Routing (CIDR) diagram
to aggregate IP addresses, which are supposed to have their associated problems.
IPv4 TO IPv6
5.0
REQUIREMENTS OF IPv6:
THE NEED FOR IPv6
IPv4 ADDRESS EXHAUSTION
The exhaustion of IPv4 addresses was already foreseen before Internet became a
worldwide phenomenon. As early as 1990, the Internet Engineering Task Force started
looking for a successor for IPv4. However, at the same time, other mechanisms, such as the
use of Private Addresses, were introduced to stave off an immediate crisis. This caused some
people to hope that perhaps the transition to IPv6 could be postponed indefinitely. A careful
analysis of available data, however, shows that IPv4 address exhaustion is progressing
unrelentingly and the most recent predictions are that in less than 5 years, it will become
impossible to receive new address blocks from official registries.
1. The IPv4 Address Report presents a thorough analysis of the expected depletion of
IPv4 addresses. It analyzes three stages of IP address usage:
2. Address blocks allocated by Internet Assigned Number Authority (IANA) to the
Regional Internet Registries (RIRs) Address blocks allocated by the RIRs to Internet
Service Providers and other local entities.
3. Addresses that appear in Internet routing tables.
Extrapolating from existing data, the report anticipates that IANA will run out of
addresses by the end of 2012. The RIRs will run out of addresses in mid of 2013. Based on
its analysis of actual usage of IPv4 addresses, the IPv4 Address Report has found that not
only do IANA and the RIRs allocate address blocks at an increasing pace, but the percentage
of allocated addresses that are actually being used in the Internet is increasing as well. When
IANA and the RIRs run out of IPv4 addresses, many service providers will still have
unallocated address blocks. However, to stave off total exhaustion as long as possible,
service providers would have to fragment address pools in increasingly smaller sets and at
times may have to reallocate addresses. Alternatively, service providers and enterprises could
start trading unallocated address blocks. In either case, address management becomes an
increasingly cumbersome and expensive procedure.
6.0
ADVANTAGES OF IPv6:
IPv6, developed by the IETF in the mid Nineties, is the Next Generation (version 6) of
the Internet Protocol (IP). IPv6 improves on the addressing capacities of IPv4 by using 128
bits for addressing instead of 32, thereby making available an almost infinite pool of IP
addresses. Also IPv6 is supposed to be providing various enhancements with respect to
security, routing, address auto configuration, mobility & QOS etc.
IPv4 TO IPv6
The following are the important features of IPv6 protocol, which may play an important
role in the growth of Internet in the country due to its advance capabilities.
(i) New Header Format:
The IPv6 header has a new format that is designed to keep header overhead to a minimum.
The streamlined IPv6 header is more efficiently processed at intermediate routers with lower
processing costs.
(ii) Large Address Space:
IPv6 has 128 bits (16 bytes) source and destination IP addresses. This will enable to
128
accommodate 2
= 3.4028236692093846346337460743177X10+38hosts. Even though only
a small number of IPv6 addresses are currently allocated for use by hosts, there are plenty of
addresses available for future use. With a much larger number of available addresses, address
conservation techniques, such as deployments of NAT will no longer be necessary.
(iii) Efficient and Hierarchical Addressing and Routing Infrastructure:
IPv6 global addresses used on the IPv6 portion of the Internet are designed to create an
efficient, hierarchical, and summarisable routing infrastructure that is based on the common
occurrence of levels of Internet service providers.
(iv) Stateless and stateful address configuration
IPv6 supports both stateful address configuration, such as address configuration in the
presence of a DHCP server, and stateless address configuration (address configuration in the
absence of a DHCP server). With stateless address configuration, hosts on a link
automatically configure themselves with IPv6 addresses for the link (called link-local
addresses) and with addresses derived from prefixes advertised by local routers. Even in the
absence of a router, hosts on the same link can automatically configure themselves with linklocal addresses and communicate without manual configuration.
(v) Built-in Security
Support for IPSec is an IPv6 protocol suite requirement. This requirement provides a
standards-based solution for network security needs and promotes interoperability between
different IPv6 implementations.
(vi) Support for QoS
New fields in the IPv6 header define how traffic is handled and identified. Traffic
identification using a Flow Label field in the IPv6 header allows IPv6 routers to identify and
provide special handling for packets belonging to particular packet flow between source and
5
IPv4 TO IPv6
destination. Support for QOS can be achieved even when the packet payload is encrypted
through IPSec.
(vii) Extensibility:
IPv6 can easily be extended for new features by adding extension headers after the IPv6
header.
In addition, IPv6 can make available almost unlimited address space thereby enabling static/
global address allocation which can have following advantages: a. As per Clause 1.10.3 of the ISP license agreement ISP are required to log all user
activity and archive it. Such an archive is required by law enforcement agencies
when the need arises. The lack of end user addressability with static IP address
may not serve the purpose of logging information fully. In cases where a static
private address is used, it is possible to trace the end user, but in cases where
DHCP is used for private addresses, there may be absolutely no clue about the
end user. So, for true accountability, there is a need to have a static IP address
allocated.
b. By having IP addresses delegated directly to the ISPs, the ISPs can provide a
better user experience with fault tolerant topologies, fault tolerant service access
and so on. The ISP can allocate static IP addresses to each of its customers and
therefore enable the users to use the newer services that may work or may not
work efficiency with NAT. Allocating static IP addresses to the subscriber end
point provides a specific identity to that user. Therefore, that user can easily be
monitored for acceptable use (as well as accounting) in an unambiguous manner.
7.0
TO TRANSITION TO IPv6 OR NOT?

A critical question for many service providers is when to transition to IPv6. As pointed
out above, IPv6 has several benefits which will result in a simpler, more powerful and more
efficient network. The sooner a service provider achieves these benefits, the better it will be
at a competitive advantage compared to service providers who delay transition. The risks of
delaying the transition are the following:
Managing a dwindling IPv4 address space will become increasingly expensive.

Address allocation requires careful planning; previously assigned address blocks
may need to be recovered, which is a complex process; and the management of
additional devices such as Network Address Translation (NAT) devices add to the
cost.
The service provider that delays transition to IPv6 may not be able to deliver the
same services as service providers that have made the transition to IPv6. The ability
to support always-on and peer-to-peer services is impaired when traffic has to
traverse NAT devices. For example, always-on services require that a user is always
reachable and therefore cannot share a pool of public addresses with other devices.
6
IPv4 TO IPv6
This can be mitigated through address and port translation, but also that has its
limitations.
At some point, a service provider who has not made the transition to IPv6 may
become unattractive as a roaming partner to service providers who have made the
transition. The same may be true in retail/wholesale relationships.
On the other hand, transitioning to IPv6 at an early stage also has certain risks. The
transitioning process is complex. It requires a significant investment in planning and training.
During the transition period, the service provider must run both IPv4 and IPv6 systems
concurrently, which leads to an increase in operational expenses. Furthermore, there is a risk
of service interruption, customer dissatisfaction and penalties. All service providers will need
to go through this, but an early adopter may run into problems which later adopters could
avoid.
In the end, we believe that service providers dont have the option to delay IPv6
introduction. The exhaustion of IPv4 addresses will force a transition to IPv6, and as pointed
out in section 1.1, address exhaustion may become a reality within the next few years. From
that point on, service providers will face an increase in operations cost, if not because of
introduction of IPv6, then due to the complexity of running an IPv4-only network with a
diminishing pool of addresses.
With careful planning, the risk of early adoption can be mitigated significantly. Later
sections in this paper provide suggestions for making the process as smooth as possible.
8.0 KEY DIFFERENCES BETWEEN IPv4 AND IPv6:

S.No.
IPv4
IPv6
(i)
Source and destination addresses are

32 bits (4 bytes) in length.
Source and destination addresses are

128 bits (16 bytes) in length.
(ii)
IPSec support is optional.
IPSec support is required.
(iii)
No identification of packet flow for

QoS handling by routers is present
within the IPv4 header.
Packet flow identification for QoS

handling by routers is included in the
IPv6 header using the Flow Label field.
(iv)
Fragmentation is done by both

routers and the sending host.
Fragmentation is not done by routers,

only by the sending host.
(v)
Header includes a checksum.
Header does not include a checksum.
(vi)
Header includes options.
All optional data is moved to IPv6

extension headers.
(vii)
Address Resolution Protocol (ARP)

uses broadcast ARP Request frames
to resolve an IPv4 address to a link
layer address.
ARP Request frames are replaced with

multicast Neighbour Solicitation
messages.
IPv4 TO IPv6
(viii)
Internet Group Management Protocol

(IGMP) is used to manage local
subnet group membership.
IGMP is replaced with Multicast

Listener Discovery (MLD) messages.
(ix)
ICMP Router Discovery is used to

determine the IPv4 address of the
best default gateway and is optional.
ICMP Router Discovery is replaced

with ICMPv6 Router Solicitation and
Router Advertisement messages and is
required.
(x)
Broadcast addresses are used to send

traffic to all nodes on a subnet.
There are no IPv6 broadcast addresses.

Instead, a link-local scope all-nodes
multicast address is used.
(xi)
Must be configured either manually

or through DHCP.
Does not require manual configuration

or DHCP.
(xii)
Uses host address (A) resource

records in the Domain Name System
(DNS) to map host names to IPv4
addresses.
Uses host address (AAAA) resource

records in the Domain Name System
(DNS) to map host names to IPv6
addresses.
(xiii)
Uses pointer (PTR) resource records

Uses pointer (PTR) resource records in
in the IN-ADDR.ARPA DNS domain the IP6.ARPA DNS domain to map
to map IPv4 addresses to host names. IPv6 addresses to host names.
9.0
HOW TO SWITCH FROM IPv4 TO IPv6:

TRANSITION MECHANISMS
9.1
OVERVIEW
The transition to IPv6 is expected to be gradual and occur over several years. With this
in mind, the Internet Engineering Task Force (IETF) has defined a wide range of transition
mechanisms to allow smooth co-existence between IPv6 networks and legacy IPv4 networks.
Such mechanisms fall into three broad categories:
1.Dual-stack (enables IPv4 and IPv6 to coexist in the same devices / networks).
2.Tunneling (includes configured and automatic tunnels; encapsulating IPv6 packets in
IPv4 packets and vice versa).
3.Protocol Translation (enables an IPv6-only device to communicate with an IPv4-only
device).
IPv4 TO IPv6
9.2
IPv6-TO-IPv4 HTTP PROXY
One option an operator may consider is the use of an IPv6 Proxy Gateway for general
web browsing. This dual stack Proxy Gateway would act as an intermediary between an IPv6
host or UE and a native IPv4 server accessed through the IPv4 Internet. This type of proxy
may be limited to HTTP port 80 and long term may offer other functionality including
caching, user authentication and content acceleration. This concept allows the operator to
provide IPv4 Internet content while transitioning to IPv6 on the mobile user plane. There are
considerations the operator must factor when deploying this type of service. The proxy must
comply with the operator's security policies and provide proper levels of secure access when
opening HTTP communication paths to Internet content. Performance and scalability will
also need to be examined since IPv6 to IPv4 Gateways will likely be processor intensive
since capabilities may initially be limited to software based solutions.
10.0
MIGRATION FROM IPv4 TO IPv6:
10.1 THE FUNDAMENTAL REASON

The fundamental reason to transition from IPv4 to IPv6 is to extend the address space
to keep the universal connectivity.
10.2 CNGI-CERNET2
CNGI-CERNET2 is an IPv6 single stack network. The original promotion concept to
migrate from IPv4 to IPv6 was:
It is free and it is light loaded.
The users need to export their applications into IPv6.
But this concept did not work well.
The connectivity is the most important issue.
So IVI Concept was developed.
10.3 IVI CONCEPT:
IV means 4
VI means 6
IVI means 4|6 coexistence and transition.
IVI is symmetric and both IPv6 and IPv4 initiated communication are supported.
10.4 THE KEY CONCEPTS OF IVI
Prefix Specific Addressing and Routing:
o Maintain a clean Internet addressing and routing architecture and globally
deliverable.
Bi-directional and Explicit Mapping:
o Restore the end-to-end address transparency.
o Maintain the minimum state.
9
IPv4 TO IPv6
Extended Address Transparency:

o Support the both, IPv6 initiated and IPv4 initiated communications for every IPv6
host (not every IPv6 address).
o Effectively use the global IPv4 addresses.
o Meet different requirements of server, client and P2P.
Protocol translation:
o SIIT.
o ICMP extension.
o Multicast extension.
10.5 TERMS AND ABBREVIATIONS OF IVI
General
o IVI.
o ISP(i)
IPv4
o IPG4: An address set containing all IPv4 addresses, the addresses in this
set are mainly used by IPv4 hosts at the current stage.
o IPS4(i): A subset of IPG4 allocated to ISP(i).
o IVI4(i): A subset of IPS4(i), the addresses in this set will be mapped to
IPv6 via IVI rule and physically used by IPv6 hosts of ISP(i).
IPv6
o IPG6: An address set containing all IPv6 addresses.
o IPS6(i): A subset of IPG6 allocated to ISP(i).
o IVIG46(i): A subset of IPS6(i), an image of IPG4 in IPv6 address family
via IVI mapping rule.
o IVI6(i): A subset of IVIG46(i), an image of IVI4(i) in IPv6 address family
via IVI mapping rule.
Components
o IVI gateway
o IVI DNS
10
IPv4 TO IPv6
10.6 IVI ADDRESS MAPPING
Single ISP deployed IVI
Multiple ISPs deployed IVI
11
IPv4 TO IPv6
10.7 ROUTING AND FORWARDING
IVI REACHABILITY MATRIX
10.8 IVI COMMUNICATION SCENARIO
IVI COMMUNICATION: SCENARIOS (1)
A (B&A)
B
12
IPv4 TO IPv6
10.9 IVI DNS CONFIGURATION
For providing primary DNS service for IVI4(i)

and IVI6(i), each host will have both A and
AAAA records
IPv4
AUTHORITATIVE DNS SERVER

Example
o www.ivi2.org A 202.38.108.2
o www.ivi2.org AAAA
2001:250:ffca:266c:200::
For resolving IVIG46(i) for IVI6(i), use

IVI DNS to do the dynamic mapping based on
the IVI rule.
CACHING DNS SERVER

Example
o www.mit.edu A 18.7.22.83
o www.mit.edu AAAA
2001:250:ff12:0716:5300::
IV
I
IPv6
IVI
DNS
IVI6 ADDRESS
o
o
o
13
Implementation scope
Host
DNS server provided via DHCPv6
ISP
IPv4 TO IPv6
10.10 MULTIPLEXING OF THE IPv4 ADDRESSES
TEMPORAL MULTIPLEXING
Dynamic assignment of IVI6(i)
PORT MULTIPLEXING
Combine address with the port number
SPATIAL MULTIPLEXING
SERVER 1:1 MAPPING
Home server 1: M mapping (via IPv4 initiated communication)
Client 1: N mapping (via IPv6 initiated communication)
MULTIPLEXING USING IPv4 NAT-PT
Cascade IPv4 NAT-PT and IVI (1:1 mapping)
10.11 EXTENDED ADDRESS TRANSPARENCY
End-to-end address transparency: the source and destination addresses of the

packets could be used as unique labels for the end systems (RFC2755).
Port multiplexing extends the address transparency
Basic NAT 232
Extended NAT 248
10.12 PORT EMBEDDING
IPv6 client initiates the communication to the IPv4 servers

o Method 1: port collision avoidance
202.38.108.5#100 2001:250:ffca:266c:0500::81#100
202.38.108.5#101 2001:250:ffca:266c:0500::82#100
202.38.108.5#102 2001:250:ffca:266c:0500::83#100
202.38.108.5#103 2001:250:ffca:266c:0500::84#100
o Method 2: embed port range into the IVI6 addresses
2001:250:ffca:266c:0500:ratio:bias:pseudo-well-know-port
IPv4 client initiates the communication to the IPv6 servers

o Method: provide pseudo-well-know-port via SRV DNS record (i.e. the remote
IPv4 host can reach different IVI6s via different port number)
202.38.108.2#81 2001:250:ffca:266c:0200:3:0:81#81
202.38.108.2#82 2001:250:ffca:266c:0200:3:1:82#82
202.38.108.2#83 2001:250:ffca:266c:0200:3:2:83#83
202.38.108.2#84 2001:250:ffca:266c:0200:3:3:84#84
14
IPv4 TO IPv6
10.13 IVI DEPLOYMENT SCENARIO
IVI DEPLOYMENT SCENARIOS (1)
11.0 DEPLOYMENT STRATEGY / RECOMMENDATIONS:

11.1 DEVELOP A TRANSITIONING PLAN
The moment that service providers will not be able to acquire new IPv4 address blocks
is rapidly approaching. As discussed in section 1.1, it could be as soon as 2012. The
transition to IPv6 is inevitable. The transition to IPv6 will take several years, but the planning
to transition to IPv6 should begin as soon as possible. Therefore, if service providers have
not already started transitioning plans, it is strongly recommended to start soon.
15
IPv4 TO IPv6
The "IPv6 Transition Guidance report, issued by Federal CIO Council Architecture
and Infrastructure Committee ([9]) provides a useful blueprint. Among the recommended
actions are:
Identifying an IPv6 Transitioning lead within the organization
Developing a transitioning plan
Taking a complete inventory of IPv6-capable network elements, applications and
enduser devices
Transition plans may vary widely from network to network; however, the transition
plans should include the following sequence of activities - Assessment, Planning, and
Deployment. Depending on the scale and complexity of the existing network infrastructure,
a number of different detailed plans may be required. Some examples include: equipment
inventory and upgrade capabilities and schedules, trials and testing vs. operational
deployment, infrastructure vs. application rollout, and staff training and support.
Large wireless service providers will likely need to begin transition sooner than smaller
service providers due to the sheer number of subscribers they must support. This places an
additional burden of being early adopters to technologies and standards that are still
maturing. One advantage that large service providers have as IPv6 pioneers is the ability to
shape the industry to their benefit by being able to provide IPv6 development requirements to
key suppliers and vendors.
11.2 USE A PHASED APPROACH

As illustrated by the given use cases, wireless service providers have the option to start
deploying IPv6-enabled devices while still running IPv4 on most network elements. In
addition to the user devices, GGSN, P-CSCF and application servers should support IPv6
interfaces. Many other network elements need to be IPv6-aware but do not need to run IPv6
themselves. This latter point should not be underestimated. A large percentage of ancillary
systems may need to be IPv6-aware, including DNS servers, DHCP servers, network
management systems, billing systems, Lawful Intercept systems, etc.
The document does not mean to suggest that the only sensible transition scenario is one
in which a service provider starts IPv6 transition with the deployment of IPv6-capable UEs,
while upgrading the IP core infrastructure later. In fact, upgrading the core may be an easier
task as many core routers already support IPv6. Therefore, upgrading the core before
upgrading user devices and edge equipment is a valid transitioning plan.
It should be noted, though, that upgrading the IP core does not mitigate the IPv4
exhaustion problem, since new end-user devices and applications will still require IPv4
addresses. Also, in the absence of IPv6 hosts, the core may be able to route IPv6, but there
will be no IPv6 traffic.
16
IPv4 TO IPv6
11.3 INTERWORKING MECHANISMS
The biggest problem that a service provider will need to solve is the interworking
between IPv6 devices and IPv4-only devices. As discussed in sections 2 and 3, a dual-stack
approach is preferred because it maintains transparency between the two end-points. In the
dual-stack approach, an IPv6 device will use IPv4 when interfacing with a device or
application server that supports IPv4 only. However, as pointed out in the Video Share use
case, the dual stack approach may not work well for mobile devices. In the case of IMSbased applications, the dual stack approach may require four simultaneous PDP Contexts. On
the other hand, for non-IMS based applications such as gaming, the dual-stack approach may
be feasible.
A service provider will need to develop a clear plan with respect to support of multiple
PDP Contexts. This plan should take the following into account:
Services the service provider is planning to support.
QoS levels planned to be offered to subscribers.
The ability of the existing RAN infrastructure to support multiple PDP Contexts and
RABs.
Based on these, the service provider will be able to assess to what extent a dual-stack
approach is feasible. The service provider should give careful consideration to an APN
strategy in order to avoid overly complex RAB requirements. In the case a dual-stack
approach is not feasible, translation is the recommended alternative.
11.4 SECURITY CONSIDERATIONS
The transition to IPv6 requires special attention to security considerations. The security
policies of individual companies typically address exposures and security mitigation
techniques in the IPv4 environment. To this end, firewalls and intrusion detection systems
have been implemented to protect an enterprises network, host computer and data assets.
However, with the introduction of dual-stack and IPv6, enterprises will need to assess
security during and after the transition. As mentioned in section 2.3, automatic tunneling can
bypass IPv4 safeguards. Therefore, transitional dual-stack security policies should be
developed to address the many networking aspects that IPv6 introduces:
Any cast addresses.
Scoped addresses.
New extension headers.
Tunneling protocols.
Transport headers and deep packet inspection.
Privacy addresses.
ICMP options.
17
IPv4 TO IPv6
12.0
MIGRATION PLAN: BSNL
12.1 STEPS TO BE TAKEN:

To enable IPv6 services, the following steps need to be followed:
1. Study the existing NIB network and verify that the all the equipment installed supports IPv6.
2. Recommend upgradation of the equipment which does not support IPv6. The upgradation
could be in terms of Software upgrade or Hardware upgradation/replacement.
3. Plan IPv6 addressing for the entire network.
4. Enable IPv6 routing in the entire network. This will be done in phased manner.
5. Enable IPv6 peering with other ISPs.
6. Setup Name Servers to support IPv6 address resolution.
7. Setup Network Monitoring and Management for IPv6.
8. Enable IPv6 in Access Equipment.
9. Test IPv6 applications.
12.2 CHECK IPv6 COMPLIANCE OF THE HARDWARE:
Compatibility of hardware to IPv6 can be ascertained from list of hardware available in
BSNL supporting IPv6 from the link http://bsnl.co.in/ipv6/ipv6.htm by downloading
migration plan for BSNL network.
ACTIONS REQUIRED:
1.The Backbone is IPv6 compliant, so no upgradation is required.
2.The IOS of PE Router needs to be upgraded to 12.4. Cisco should be consulted before
the IOS is finalized.
3.The Broadband equipment needs to be upgraded/replaced with IPv6 compliant
equipment. BSNL needs to plan a policy on this.
4.The Multiplay equipment needs to be upgraded/replaced with IPv6 compliant
equipment. BSNL needs to plan a policy on this.
12.3 IPv6 ADDRESSING PLAN
The IPv6 address range allocated to BSNL by APNIC is 2001:4490::/30. However since
BSNL is entitled for /24 address space and a larger address space will be future safe, the
same should be requested to APNIC.
Following would require IPv6 addressing
BSNL servers, backbone and access equipment.
Leased Line Customers
Enterprise customer with multiple location (connected through leased lines or over
MPLS)
Broadband (ADSL) Customers
Mobile Wireless (GSM, CDMA, 3G) customers
Multiplay Customers
18
IPv4 TO IPv6
WiMAX Customers
ISPs who are taking bandwidth from BSNL
IPv6 services will not be offered to Narrow-band Dial-up customers.

Following Hierarchical Address Allocation Policy may be used:
Allocate address range to various PoPs as follows:

o /34 for A1 & A2 PoPs
o /36 for A3 & A4 PoPs
o /38 for B1 & B2 PoPs
Within each PoP, allocate address range as follows:
o In all A1 & A2 PoPs, use /38 for various services like Broadband, Mobile, Multiplay,
WiMAX, leased line customers (including ISPs) and BSNL service networks.
o In all A3 & A4 PoPs, use /40 for various services like Broadband, Mobile, Multiplay,
o In all B1 & B2 PoPs, use /42 for various services like Broadband, Mobile, Multiplay,
Allocate address range to customers as follows:
o Allocate /64 IP address to broadband, mobile wireless, WiMAX and multiplay
customers.
o Allocate /56 to large Leased Line customers & /60 for small leased line customers and
BSNL service networks.
o Allocate multiple /56 or /60 to multi-location leased line customer.
o Allocate multiple /56 to ISPs.
Allocate 1 /40 address range for all the routers and other network devices. All the IPv6
related routing and IPv6 SNMP management should be done using these IPs.
RFCs 3531, RFC 4007, RFC 4291, RFC 5375 related to IPv6 address assignment may be
referred to for details.
ACTIONS REQUIRED:
o BSNL should use the address allocation policy to allocate addresses to various PoPs.
The website http://www.ipv6book.ca/allocation.html may be used for IPv6 prefix
calculation.
o Various network equipments should be configured with allotted IPv6 addresses.
12.4 IPv6 ROUTING

The complete NIB network needs to be configured for routing IPv6 traffic. Since the core
backbone is MPLS, it is recommended that the IPv6 traffic should be routed through VPN
tunnels over the MPLS cloud.
So no configuration change is required in Core Routers. The PE routers should be configured
as 6PE routers so that the IPv6 traffic can routed over MPLS core backbone.
19
IPv4 TO IPv6
This feature has already been tested on the PE routers at Noida and Banglore NOC.
Annexure II details how PE routers at Noida and Banglore NOC have been configured as
6PE routers to route IPv6 traffic over the NIB MPLS backbone. Similar configuration can be
replicated in all the PE routers.
The routing of IPv6 traffic from customer premises to the PE Routers will be native IPv6
routing. So the Customer Edge equipment, Central Office Access equipment and PE Routers
should be configured to support dual stack IPv4 and IPv6 routing.
ACTIONS REQUIRED:
1.Plan IPv6 routing in the Backbone and Customer Edge.
2.Configure PE Routers as 6PE Routers.
3.Configure all Central Office Access equipment for Dual Stack IPv4/IPv6.
12.5 IPv6 PEERING:

To enable all the BSNL customers to be able to access Internet over IPv6 and run IP based
applications (e.g. VoIP) over IPv6, the peering with upstream provider(s) and other peering
ISP(s) needs to be enabled for routing IPv6 traffic.
ACTIONS REQUIRED:
1.Request upstream provider(s) to announce BSNLs Ipv6 addresses and enable Ipv6
routing between BSNL NIB network and their network.
2.Study the existing peering arrangements and enable Ipv6 peering with other peering
partners.
12.6 IPv6 APPLICATION SERVERS:

In order to support IPv6 services for BSNL customers, the application servers need to be
enabled for supporting IPv6. Initially at-least DNS and Web Server(s) should be configured
to support IPv6. The steps required to setup an IPv6 DNS and Web server are given in
Annexure III of ref.7.
ACTIONS REQUIRED:
Upgrade some of the existing Internet Name Servers and Web Servers being run by BSNL
for its customers to support IPv6.
12.7 IPv6 NETWORK MONITORING AND MANAGEMENT:

In order to monitor and manage the IPv6 network, the SNMP management stations should be
upgraded to support IPv6. Necessary configurations should be done so that the monitoring
and management can be done over IPv6.
20
IPv4 TO IPv6
ACTIONS REQUIRED:
The existing SNMP management tool(s) should be upgraded and configured to monitor and
manage the network over IPv6 in addition to the existing IPv4 based management.
12.8 IPv6 SUPPORT IN ACCESS EQUIPMENT:

In order for the BSNL customers using various access technologies like ADSL Broadband,
WiMAX, Multiplay etc., to be able to run native IPv6 applications, the access network needs
to be enabled to support and route IPv6 traffic. So the Central Office Access equipment
needs to be upgraded and configured to support IPv6.
ACTIONS REQUIRED:
Enable and configure IPv6 support in Access Equipment.
12.9 TEST IPv6 APPLICATIONS AND SERVICES

Test plans should be made to test various features of IPv6.
ACTIONS REQUIRED:
1. Make comprehensive Test Plans to test IPv6 Routing and Application Services.
2. Suggest modifications and improvements based on the test results.
13.0 LIST OF ABBREVIATIONS:

1. AAA: Authentication, Authorization and Accounting
2. ALG: Application-Level Gateway
3. APN: Access Point Name
4. CDR: Call Detail Record
5. CIDR: Classless Interdomain Routing
6.
7.
8.
9.
10.
DAD: Duplicate Address Detection

DHCP: Dynamic Host Configuration Protocol
DNS: Domain Name Server
EMS: Element Management System
GGSN: Gateway GPRS Support Node
11. GPRS: General Packet Radio Service

12. GTP: GPRS Tunneling Protocol
21
IPv4 TO IPv6
13. GTP: GPRS Tunneling Protocol
14. HSS: Home Subscriber Server
15. HTTP: HyperText Transfer Protocol
16.
17.
18.
19.
IANA: Internet Assigned Number Authority

IANA: Internet Assigned Number Authority.
ICE: Interactive Connectivity Establishment
ICID: IMS Charging Identity
20.
21.
22.
23.
ICMP: Internet Control Message Protocol

IMS: IP Multimedia Subsystem
IPv4: internet protocol version 4
IPv6: internet protocol version 6
24. ISP: Internet Service Provider

25. IVI: IV to VI translation
26. NAT: Network Address Translation
27. NOC: Network Operation Center
28.
29.
30.
31.
PCRF: Policy and Charging Rules Function

P-CSCF: Proxy Call Session Control Function
PDP: Packet Data Protocol
QoS: Quality-of-Service
32.
33.
34.
35.
RAB: Radio Access Bearer

RAN: Radio Access Network
RIM: Research in Motion
RIR: Regional Internet Registry
36. RNC: Radio Network Controller

37. RTCP: Real-Time Control Protocol
38. RTP: Real-Time Protocol
39. S-CSCF: Serving Call Session Control Function
40. SDP: Session Description Protocol
41.
42.
43.
44.
45.
SGSN: Serving GPRS Support Node

SIIT: Stateless IP/ICMP Translation Algorithm
SIP: Session Initiation Protocol
SLAAC: Stateless Address Auto-Configuration
UE: User Equipment
46. UMTS: Universal Mobile Telecommunications System

47. URI: Universal Resource Identifier
48. VPN: Virtual Private Network
22
IPv4 TO IPv6
14.0
REFERENCES:
http://trai.gov.in
http://www.ietf.org/internet-drafts/draft-xli-behave-ivi-00.txt
http://www.ietf.org/rfc/rfc2765.txt
http://www.subnetonline.com/pages/subnet-calculators/ipv4-to-ipv6-converter.php
(An online convertor from IPv4 to IPv6 and vice-versa)
5. http://www.ipv6book.ca/allocation.html
6. http://bsnl.co.in/ipv6/national_plan%20final%20book.pdf
7. http://bsnl.co.in/ipv6/ipv6.htm
1.
2.
3.
4.
******End of Document******
23

EI IPv4-6

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EI IPv4-6

Uploaded by

Copyright:

Available Formats

IPv4 TO IPv6

EI/ IPv4 TO IPv6/11-12/22

The CGM, TQA circle, Bangalore

eU MUl M SlM Date of Issue

RAMESH CHANDRA YADAV (QA Circle)

MAMATHA N K & LAKSHMIRAMANATHAN (QA Circle)

Restricted use by BSNL Employees only

qZr qW mokM M Mrsr

Office of Chief General Manager

DISCLAIMER: FOR INTERNAL CIRCULATION AMONG BSNL EMPLOYEES AS A GUIDELINE FOR

Present System of Internet addressing

IPv4: Short Comings and Limitations

To Transition To IPv6 Or Not

Key Differences Between IPv4 and IPpv6

How To Switch From IPv4 to IPv6

Migration From IPv4 to IPv6

Deployment Strategy / Recommendations

3.0 PRESENT SYSTEM OF INTERNET ADDRESSING:

4.0 IPv4 :SHORTCOMINGS AND LIMITATIONS:

TO TRANSITION TO IPv6 OR NOT?

Managing a dwindling IPv4 address space will become increasingly expensive.

8.0 KEY DIFFERENCES BETWEEN IPv4 AND IPv6:

Source and destination addresses are

Source and destination addresses are

IPSec support is optional.

IPSec support is required.

No identification of packet flow for

Packet flow identification for QoS

Fragmentation is done by both

Fragmentation is not done by routers,

Header includes a checksum.

Header does not include a checksum.

Header includes options.

All optional data is moved to IPv6

Address Resolution Protocol (ARP)

ARP Request frames are replaced with

Internet Group Management Protocol

IGMP is replaced with Multicast

ICMP Router Discovery is used to

ICMP Router Discovery is replaced

Broadcast addresses are used to send

There are no IPv6 broadcast addresses.

Must be configured either manually

Does not require manual configuration

Uses host address (A) resource

Uses host address (AAAA) resource

Uses pointer (PTR) resource records

HOW TO SWITCH FROM IPv4 TO IPv6:

IPv6-TO-IPv4 HTTP PROXY

MIGRATION FROM IPv4 TO IPv6:

10.1 THE FUNDAMENTAL REASON

Extended Address Transparency:

Single ISP deployed IVI

Multiple ISPs deployed IVI

IVI REACHABILITY MATRIX

10.8 IVI COMMUNICATION SCENARIO

IVI COMMUNICATION: SCENARIOS (1)

IVI COMMUNICATION: SCENARIOS (2)

10.9 IVI DNS CONFIGURATION

For providing primary DNS service for IVI4(i)

AUTHORITATIVE DNS SERVER

For resolving IVIG46(i) for IVI6(i), use

CACHING DNS SERVER

10.11 EXTENDED ADDRESS TRANSPARENCY