Compatibility between the new and the current ipv6 packet headers

International Journal of Electronics and Communication Engineering & Technology (IJECET),
ISSN 0976 – 6464(Print), ISSN 0976 – 6472(Online) Volume 4, Issue 3, May – June (2013), © IAEME
211
COMPATIBILITY BETWEEN THE NEW AND THE CURRENT IPV6
PACKET HEADERS
Fahim A. Ahmed Ghanem1
, Vilas M. Thakare2
1
Research Student, School of Computational Sciences,
Swami Ramanand Teerth Marathwada University, Nanded, India.
2
Professor and Head of Computer Science, Faculty of Engineering &Technology
Post Graduate Department of Computer Science, SGB, Amravati University, Amravati.
ABSTRACT
This paper aims to compatible between the new approach of IPv6 Packets’ header and
transmission with the existing one. This compatibility will give us the ability to combine and
execute both approaches in one network environment and give us the flexibility to gradual
migration from the existing to new approach without affecting the current network
environment.
KEYWORDS: TCP/IP, UDP, IPv6, Ethernet Frame.
1. INTRODUCTION
The new “IPv6 Packet’s header and transmission”approach which was proposed by us
previously [1] has reduced the headers of the packet and reduced the header processing time
which was worthy to be implemented in network environment.
Network environment has billions of devices work on current IPv6 packet scheme which
makes the implementationof new approach practically not possible at all. The practical way
for implementing the new approach is to find compatibility way between the new and the
existing approach and start implementing the new approach gradually.
2. OBJECTIVE OF THIS STUDY
The objective of this paper is the compatibility between the new approachof
“IPv6Packetheaders and transmission” which was proposed by us in the previous paper [2]
with existing OSImodule. This compatibility willgive us the ability to gradually migratefrom
INTERNATIONAL JOURNAL OF ELECTRONICS AND
COMMUNICATION ENGINEERING & TECHNOLOGY (IJECET)
ISSN 0976 – 6464(Print)
ISSN 0976 – 6472(Online)
Volume 4, Issue 3, May – June, 2013, pp. 211-219
© IAEME: www.iaeme.com/ijecet.asp
Journal Impact Factor (2013): 5.8896 (Calculated by GISI)
www.jifactor.com
IJECET
© I A E M E

ISSN 0976 – 6464(Print), ISSN 0976
the exiting IPv6 approach to the new
devices which are working on current
by reducing the cost of replacement the existing
without extra investment. This will help organization to migrate the devices which have an
expired support licenses or reach the default work years.
3. EXISTING AND NEW IPV6 PACKET’S APPROACH
Before we start with compatibility, it
existing and the packet header’s approaches.
3.1 CurrentIPv6 Packet’s Approach (
As we have gone through existing approach in the previous paper
section we will have a quick look
deeply in the functionality of theheader
a. Variable Fields: fields that it is information from
in each packet.
b. Invariable Fields (Tagged with Inv.):
to other and doesn’t have to be repeated in each packet
Open Systems Interconnection (OSI) model
Systems Interconnection effort at the
prescription of characterizing and standardizing the functions of a
terms of abstraction. Similar communication functions are grouped into logical layers. A
layer serves the layer above it and is served by the layer below it.
There are seven interconnection layers start from up to down (layer 7 to layer 1
prospectively:
Application forwards user data to Presentation layer which forwards it to
Session layer forwards data user to Transportation layer.
sent the segment to Network layer which adds header and forward the packet to
layer. Data link adds the header and forward the frame to
Fig.
3.1.1 TCP Packet’s Headers
The Transmission Control Protocol (TCP) is one of the core
Protocol Suiteprovides reliable, ordered
computer to another program on another computer. TCP is the protocol that major Internet
applications such as the World Wide
on.
ISSN 0976 – 6472(Online) Volume 4, Issue 3, May – June (2013), © IAEME
212
to the new approach without needing to remove all the existing
devices which are working on currentIPv6 approach. This approach will be useful financially
by reducing the cost of replacement the existing IPv6 devices to the new proposed
will help organization to migrate the devices which have an
expired support licenses or reach the default work years.
EXISTING AND NEW IPV6 PACKET’S APPROACH
Before we start with compatibility, it will be helpful to have a quick review of the
existing and the packet header’s approaches.
Packet’s Approach (OSI Model Layers)
As we have gone through existing approach in the previous paper [3
look through OSI model packet construction without digging
deeply in the functionality of theheader files.There are two types of header fields:
it is information from packet to packet and has to be repeated
(Tagged with Inv.): fieldthat it is information doesn’t vary
have to be repeated in each packet.
Open Systems Interconnection (OSI) model (ISO/IEC 7498-1) is a product of the
effort at the International organization for Standardization
prescription of characterizing and standardizing the functions of a communications system
layer serves the layer above it and is served by the layer below it.
There are seven interconnection layers start from up to down (layer 7 to layer 1
forwards user data to Presentation layer which forwards it to Session
Session layer forwards data user to Transportation layer. Transport layer adds the header and
layer which adds header and forward the packet to
link adds the header and forward the frame to Physical layer.
Fig.1 OSI 7 layers’ hierarchy
The Transmission Control Protocol (TCP) is one of the core protocols of the
provides reliable, ordered delivery of a stream of bytes from a program on one
World Wide Web, email, remote administration and file transfer
June (2013), © IAEME
ach without needing to remove all the existing
This approach will be useful financially
devices to the new proposed IPv6
will help organization to migrate the devices which have an
will be helpful to have a quick review of the
3], so in this
packet construction without digging
of header fields:
to be repeated
it is information doesn’t vary from packet
1) is a product of the Open
rganization for Standardization. It is a
cations system in
There are seven interconnection layers start from up to down (layer 7 to layer 1)
Session layer.
adds the header and
layer which adds header and forward the packet to Data link
of the Internet
delivery of a stream of bytes from a program on one
file transfer rely

ISSN 0976 – 6464(Print), ISSN 0976
3.1.1 UDP Packet’s Header
UDP is a connectionless protocol that provides an unreliable data services [
applications must generally be willing to accept some loss, errors or duplication. Some
applications such as TFTP may add rudimentary reliability mechanisms into the application
layer as needed [5]. UDP provides application
verification (via checksum) of the header and payload [
where error checking and correction is either not necessary or performed in the application,
avoiding the overhead of such processing at the network interface level [
Fig. 2 OSI TCP frame
3.2 New IPv6 Packet’s Approach
New IPv6 approachconsists of two
1- TCP/UDP HeadersOptimization:
It contains creationof master
2- TCP/UDP Packet Transmission:
Packet’s processingdivided into two steps
a. Processing of Master packet.
b. Processing of Slave packet.
3.2.1 TCP/UDP Header Optimization
TCP/UDP headers optimization divides the packet into two groups; master and slave packets
213
UDP is a connectionless protocol that provides an unreliable data services [
may add rudimentary reliability mechanisms into the application
]. UDP provides application multiplexing (via port numbers) and integrity
the header and payload [6]. UDP is suitable for purposes
avoiding the overhead of such processing at the network interface level [7].
frame Fig. 3 OSI UDP frame
Packet’s Approach
consists of two stages:
Optimization:
aster and slave packet.
Transmission:
divided into two steps
Master packet.
Processing of Slave packet.
Header Optimization
TCP/UDP headers optimization divides the packet into two groups; master and slave packets
UDP is a connectionless protocol that provides an unreliable data services [4]. UDP
may add rudimentary reliability mechanisms into the application
) and integrity
UDP is suitable for purposes
TCP/UDP headers optimization divides the packet into two groups; master and slave packets.

ISSN 0976 – 6464(Print), ISSN 0976
3.2.1.1 TCP/UDP Master Packet
The proposed Master packet contains all header fields (Variables, Invar
ID and Tag Fields) but without user data field.
same contents of OSI TCP/UDP
a. ID: 1 bit indicates the type of the packet, as value 1 indicates Master segment and value 0
indicate slave packet.
b. Tag: 31 bits, is a unique ID for each session, th
session.
Fig. 4
Fig. 5
214
TCP/UDP Master Packet
Master packet contains all header fields (Variables, Invariable, along with
ID and Tag Fields) but without user data field.The contents of Master TCP/UDPPacket
header with extra two fields:
ID: 1 bit indicates the type of the packet, as value 1 indicates Master segment and value 0
Tag: 31 bits, is a unique ID for each session, thisvaluewill be maintained till
Fig. 4 Proposed TCP master frame
Fig. 5 Proposed UDP master frame
iable, along with
/UDPPacket are
ID: 1 bit indicates the type of the packet, as value 1 indicates Master segment and value 0
aluewill be maintained till end of the

ISSN 0976 – 6464(Print), ISSN 0976
3.2.1.2 TCP/UDP Slave Packet
Slave packet contains only i
along with user data.
Fig. 6
Fig.
215
TCP/UDP Slave Packet
only invariable header fields in addition to ID and
Fig. 6 Proposed TCP slave frame
Fig. 7 Proposed UDP slave frame
and Tag fields

216
3.2.2 Packet Transmission
Packet transmission includes the process of transmission of master and slave packets from
source to destination.
3.2.2.1 Master PacketTransmission
3.2.2.1.1 Master TCP Packet Transmission
a. Application layer of the source stationforwardsuser data to Presentation which forwards it
to Session which also forwards it to transport layer.
b. Transport layer buffers the received user data, creates one master TCP segment and
forward it to network layer.
c. Network layeradds Network layer master header to the received segmentand send the
packet to Ethernet layer.
d. Ethernet layer adds Ethernet master header and tailor and sends the frame to physical
layer.
e. Physical layeradds it is header sends it to another station or middle devices towards
destination.
f. Ethernet layer in layer 2 devicechecks the packet ID and identify whether it is Master
packet or Slave packet by value of ID (1= master and 0 = slave).
g. If the value ID is 1, Ethernet layerprocesses Master packet asthe processing of OSI model
packet based on source, destination and content etc. anddecide the next hop MAC.
h. Ethernet layercashes the frame processing result, save it in the forwarding table along
with frame’s Tag and send the frametowards the destination.
i. If the next hop is layer 2, steps f,g, and h will be repeated.
j. If the next hop is layer 3device,layer 3 checks the packet ID and identify whether it is
Master Packet or Slave Packet by value of ID (1= master and 0 = slave).
k. If value ID is 1, layer 3, layer 3 processes master packet as OSI model processing based
on source, destination and content etc. anddecide the next hop IP.
l. Layers 3 cashes the processing result, save it in the forwarding table along with packet’s
Tag and forwards the packet towards the destination.
m. If the next hop is layer 3, steps j, k, and l will be repeated.
n. If the next hop is layer 4, layer 4processes the segment as per layer 2 and layer 3 and
forwards it to next hop or layer.
o. Steps f – n will be repeated till packet reaches the destination.
p. Once Transport layer of source station receives the acknowledgement about receiving
Master packet from the destination, it startscreating and sending slave segments.
Note: master TCP packet was sent only one time per each session.
3.2.2.1.2 MasterUDPPacket Transmission
Transmission of master UDP packet takes steps from a - n of TCP packetbut not step
o, because UDP packet doesn’t rely on acknowledgment.
Note: master UDP packet being transmitted every 5 seconds in order to insure continuously
delivering of packets in case there is any transmission or processing issue in the middle
devices.

217
3.2.2.2 Slave Packet’s Transmission
3.2.2.2.1 Slave TCP Packet Transmission
a. Source transport layer creates either TCP or UDP slave header and sends the segment to
Network layer.
b. Network layeradds it is slave header and sendsthe packet to Ethernet layer.
c. Ethernet layeradds it is slave header and tailor and sends it to physical layer.
d. Physical layer adds it isheader and forwards it towards the destination.
e. Ethernet layer of the destination stationor middle devices checks the packet ID and
identify whether it is Master Frame or Slave Frame by value ID (1= master and 0 =
slave).
f. If the value ID is 0, layer 2matches the Tag with forwarding table information and
forwardsitto the next hope without any extra processing.
g. If there is no information about the Tag in the forwarding table, layer 2simply drops the
packet.
h. If the next hope is layer 2, step e and f will be repeated.
i. If the next hope is layer 3deviceof the destination station, layer 3 will check the packet ID
and identify whether it is Master Frame or Slave Frame by value ID (1= master and 0 =
slave).
j. If the value ID is 0, layer 3matchespacketTag with forwarding table information and
forwards it to the next hope without any extra processing.
k. If there is no information about the Tag in the forwarding table, layer 3 simply drops the
packet.
l. If the next hope is layer 3, step iand j will be repeated.
m. If the next hop is layer 4, layer 4processes the segment like layer 2 and layer 3 and
forwards it to next layer.
n. Steps etomwas repeated till packet reaches the destination.
o. Packet acknowledgment wassent as OSI model.
3.2.2.2.2 Slave UDPPacket Transmission:
Transmission of slave UDP segment, packet and frame takes is same as steps from a -
n of TCP packet but not step o, because UDP packet doesn’t rely on acknowledgment.
Note: master UDP packet is sent every 5 seconds in order to insure continuously delivering of
the packets in case there is any transmission or processing issue in the middle devices. [8]
4. Compatibility approach
New approach headers construction and packet transmission differs than the existing header
construction and transmission. In any network environment there will benew approach based
devices and existing approach based devices. Transmission of data between those devices
basically will not be doable unless there is compatibility between those devices. There are
four scenarios for this compatibility as the following:
1- New IPv6 approach device hands over TCP data to current IPv6 approach device.
2- Current IPv6 approach device hands over TCP data to new IPv6device.
3- New IPv6 approach device hands over UDP data to current IPv6 approach device.
4- Current IPv6 approach device hands over UDP data to new IPv6 device.
In the first scenario; new IPv6approach device will send master TCP packet to current
approach device and wait for acknowledgment. If it doesn’t receive the acknowledgement
within widow time, it will assume the neighbor doesn’t support new approach and will send

ISSN 0976 – 6464(Print), ISSN 0976
the packets based on the current approach.
In the second scenario; new IPv6
data for first packet, create master TCP packet and send it to its neighbor. If its neighbor
supports IPv6 new approach, this device will change the header
approach packet and send it to the neighbor. If its neighbor doesn’t support new
approach packet, the device will bypass the current
modification.
For third scenario and as per UDP
this scenario, the new device will send test
order to check the ability of its neighbor whether it sup
neighbor supports new IPv6 approach, the device will send new
doesn’t support new IPv6 approach, the device will send current
In the fourth scenario; newIPv6
data for first packet, create test master TCP
neighbor supports IPv6 new approach,
received packet to new IPv6 appr
doesn’t support new IPv6 approach packet,
packet to its neighbor without any modification.
Fig. 8 compatibility scenario 1 and 3
Fig. 9 compatibility
5. CONCLUSION
Compatibility between new
ability to gradually migrate from the current
devices without needing to retire the existing devices or to invest more for th
This compatibility helps financially as we don’t have to create 100% new network
environment, the migration will be don’t for
devices which have expired support. Compatibility also
enterprise companies to move forward the new
218
based on the current approach.
IPv6approach device will receive current IPv6 packet, cash the
new approach, this device will change the headers of thepackets to new
send it to the neighbor. If its neighbor doesn’t support new
will bypass the current IPv6packet to its neighbor without
For third scenario and as per UDP nature, there is no acknowledgment for UDP packet. In
this scenario, the new device will send test master TCP not UDP packet to it is neighbor in
order to check the ability of its neighbor whether it supports current or new IPv6
approach, the device will send new IPv6 packet approach
approach, the device will send current IPv6 approach.
IPv6 approach device will receive current IPv6 packet, cash the
master TCP not UDP packet and send it to its neighbor. If its
new approach, then the device will change the header of each
approach packet and send it to the neighbor. If its neighbor
approach packet, then the device will bypass the current
packet to its neighbor without any modification.
between new IPv6 approach and current IPv6 approach gives us the
ability to gradually migrate from the current IPv6 approach devices to the new IPv6
devices without needing to retire the existing devices or to invest more for this migration.
environment, the migration will be don’t for the devices which reach theend-of-
devices which have expired support. Compatibility also encourages the vendors and
enterprise companies to move forward the new IPv6 approach without extra investments
packet, cash the
thepackets to new IPv6
send it to the neighbor. If its neighbor doesn’t support new IPv6
to its neighbor without any
there is no acknowledgment for UDP packet. In
TCP not UDP packet to it is neighbor in
IPv6 approach. If
approach. If it
packet, cash the
packet and send it to its neighbor. If its
device will change the header of each
and send it to the neighbor. If its neighbor
bypass the current IPv6
approach gives us the
IPv6 approach
migration.
-life or for the
the vendors and
investments.

ISSN 0976 – 6464(Print), ISSN 0976
6. REFERENCES
[1][2][3][8] Fahim A. Ahmed Ghanem, Vilas M. Thakare
Headers”, IJCSI International Journal of Computer Science Issues, Vol. 10. Issue 1, No 2,
January 2013, IJCSI-10-1-2-294-
[4] Michael A. Gallo, William M. Hancock, “Computer Communications and Networking
Technologies”, New Delhi, India, Cengage Learning India Private Limited
[5]Forouzan, B.A. “TCP/IP: Protocol Suite, 1st edition”, New Delhi, India, Tata McGraw
Hill Publishing Company Ltd.
[6] Clark, M.P., “Data Networks IP and the Internet, 1st edition”, West Sussex, England,
John Wiley & Sons Ltd.
[7]Andrew S. Tanenbaum, “Computer Networks 4th Edition”
Prentice Hall PTR.
[9] Mustafa Alaa Qasim and Dipak Pawar
Address”, International Journal of Computer Engineering & Technology (IJCET),
Volume 4, Issue 2, 2013, pp.
0976 – 6375.
[10] Fahim A. Ahmed Ghanem and Vilas M. Thakare, “Optimization of Ipv6 Packet’s
Headers Over Ethernet Frame”, International Journal of Electronics and Communication
Engineering & Technology (IJECET), Volume 4, Issue 1, 2013, pp. 99
0976- 6464, ISSN Online: 0976
AUTHORS
Mr. Fahim A. Ahmed Ghanem
Computational Sciences,
MARATHWADA UNIVERSITY, Nanded,
in field of IP Network Optimization. He received MSC
SMU, India 2005
Senior Network
(Supervisor)
M.E. degree in field of
in field of Applied Electronics, Diploma in Computer Management
was obtained his PhD in field of Computer Science.
219
Fahim A. Ahmed Ghanem, Vilas M. Thakare, “Optimization OfIPv6
IJCSI International Journal of Computer Science Issues, Vol. 10. Issue 1, No 2,
-302.
Michael A. Gallo, William M. Hancock, “Computer Communications and Networking
Technologies”, New Delhi, India, Cengage Learning India Private Limited.
Forouzan, B.A. “TCP/IP: Protocol Suite, 1st edition”, New Delhi, India, Tata McGraw
ompany Ltd.
Clark, M.P., “Data Networks IP and the Internet, 1st edition”, West Sussex, England,
Computer Networks 4th Edition”, Amsterdam, the Netherland,
Dipak Pawar, “Encryption & Steganography in Ipv6 Sou
ournal of Computer Engineering & Technology (IJCET),
, pp. 315 - 324, ISSN Print: 0976 – 6367, ISSN Online:
Fahim A. Ahmed Ghanem and Vilas M. Thakare, “Optimization of Ipv6 Packet’s
Technology (IJECET), Volume 4, Issue 1, 2013, pp. 99 - 111, ISSN Print:
ISSN Online: 0976 –6472.
Mr. Fahim A. Ahmed Ghanem is a Ph.D. student at
Computational Sciences, SWAMI RAMANAND TEERTH
MARATHWADA UNIVERSITY, Nanded, India. He is doing research
in field of IP Network Optimization. He received MSC-IT degree from
SMU, India 2005 – 2007. He is a dual CCIE R&S and SP.He
Network Engineer in mobily SPK.S.A.
(Supervisor) Mr. Vilas Mahadeorao Thakare, has received his
degree in field of Advance Electronics, received his
Applied Electronics, Diploma in Computer Management
was obtained his PhD in field of Computer Science.
IPv6 Packet’s
IJCSI International Journal of Computer Science Issues, Vol. 10. Issue 1, No 2,
Michael A. Gallo, William M. Hancock, “Computer Communications and Networking
Forouzan, B.A. “TCP/IP: Protocol Suite, 1st edition”, New Delhi, India, Tata McGraw-
Clark, M.P., “Data Networks IP and the Internet, 1st edition”, West Sussex, England,
, Amsterdam, the Netherland,
n Ipv6 Source
ournal of Computer Engineering & Technology (IJCET),
6367, ISSN Online:
Fahim A. Ahmed Ghanem and Vilas M. Thakare, “Optimization of Ipv6 Packet’s
111, ISSN Print:
is a Ph.D. student at School of
SWAMI RAMANAND TEERTH
India. He is doing research
IT degree from
He works as a
, has received his
, received his M.Sc. degree
Applied Electronics, Diploma in Computer Management. He

Compatibility between the new and the current ipv6 packet headers

More Related Content

What's hot (20)

Viewers also liked (8)

Similar to Compatibility between the new and the current ipv6 packet headers (20)

More from IAEME Publication (20)

Recently uploaded (20)

Compatibility between the new and the current ipv6 packet headers