Seamless converging system for IPv4/IPv6 transition
4
Citation
6
Reference
10
Related Paper
Citation Trend
Abstract:
The IPv4 address pool of ICANN has been depleted. Internet service providers are accelerating the research and deployment of IPv6 transition solution. Dual stack and tunneling technologies can only allow IPv4 and IPv6 to coexist, but can't make IPv4 and IPv6 network interact with each other. For alleviating the shortage of IPv4 address, accelerating the deployment of IPv6 and promoting the seamless converging of IPv4 and IPv6 network, this paper illustrate the design and implementation of an IPv4/IPv6 seamless converging system. The system is mainly composed by stateful and stateless protocol translation modules and can make hosts with shared IPv4 address or global IPv6 address access IPv4 Internet across IPv6 backbone.Keywords:
IPv4
As each global IPv4 address will be shared among more and more
customers, and as more and more NATs will be deployed in ISP
infrastructures, the lack of end-to-end transparency and the limited
scalability of some NATs are likely to cause increasing difficulties
to customers and to ISPs. This document introduces IPv4-IPv6
coexistence scenarios where IPv4 addresses are shared with good
scalability and, in favorable configurations, with full IPv4 end-to-
end transparency. For this, the key tool is the Stateless Address
Mapping (SAM) of draft-despres-SAM-00, with in particular its extended
IPv4 addressing (IPv4E) in which port prefixes are used as IPv4
address extensions. For each considered scenario, Static Address
Mappers (SAMs) are deployed at scenario specific places.
IPv4
IPv6 address
Cite
Citations (0)
Due to specific problems, Network Address Translation - Protocol
Translation (NAT-PT) was deprecated by the IETF as a mechanism to
perform IPv6-IPv4 translation. Since then, new efforts have been
undertaken within IETF to standardize alternative mechanisms to
perform IPv6-IPv4 translation. This document analyzes to what extent
the new stateful translation mechanisms avoid the problems that caused
the IETF to deprecate NAT-PT.
IPv4
NAT traversal
Nat
Network address
Cite
Citations (2)
Cite
Citations (0)
Invocation
Cite
Citations (4)
This paper investigates the message complexity of stateless and stateful methods that are used in every mobile ad-hoc networks (MANETs) address auto-configuration protocol (AAP). It is important to understand the performance difference between stateless and stateful methods in AAPs since stateless and stateful methods have been installed in every AAPs as the basic module. The purpose of this paper is giving a clear guidance in selecting AAP methods. It is investigated that that due to the term of O(tN) in the stateful method, the overall message complexity of stateful method is 13.2% a nd 3 4.8% higher than that of stateless method with conflict probabilities(p) 0.1 and 0.3.
Cite
Citations (0)
This document describes stateful NAT64 translation, which allows IPv6-only clients to contact IPv4 servers using unicast UDP, TCP, or ICMP. One or more public IPv4 addresses assigned to a NAT64 translator are shared among several IPv6-only clients. When stateful NAT64 is used in conjunction with DNS64, no changes are usually required in the IPv6 client or the IPv4 server.
IPv4
Unicast
Cite
Citations (35)
This document describes stateful NAT64 translation, which allows IPv6-only clients to contact IPv4 servers using unicast UDP, TCP, or ICMP.One or more public IPv4 addresses assigned to a NAT64 translator are shared among several IPv6-only clients.When stateful NAT64 is used in conjunction with DNS64, no changes are usually required in the IPv6 client or the IPv4 server.
IPv4
Cite
Citations (191)
It is well known that, in the near future, the lifetime of the IPv4 address space will be limited and available 32-bit IP network addresses will not be left any more. In order to solve such IPv4 address space problem in an effective way, the transition to the new version using IPv6 architecture is inevitably required. At present, it is impossible to convert IPv4 into IPv6 at a time, since the coverage and the size of today's Internet is too huge. Therefore, the coexistence of both IPv4 and IPv6 must be arranged in a special and practical fashion for rapid conversion on the whole. IP protocol translation has been proposed to ease the translation of the Internet from IPv4 to IPv6. This paper presents the design and implementation of a transparent transition service that translates packet header as they cross between IPv4 and IPv6 networks. IPv4/IPv6 Translation Protocol is written in c source code and is tested by the local test recommended by ISO, which has the most excellent error detection function. The test was processed with a test scenario and it was found that the results were successful.
IPv4
Header
NAT traversal
Address space
Cite
Citations (0)
A computer network that would cover the entire planet and connect billions of devices was beyond imagination when the Internet was first conceived. Consequently, over the last 20 years, the Internet has become a crowded place. This is because the IP protocol that makes the Internet possible was
an experimental protocol that “escaped from the lab”. The Internet address exhaustion problem was identified less than a decade later, when the first proposal solutions also began to emerge. Switching to the Classless Inter-Domain Routing (CIDR) scheme was crucial for continued Internet growth, but insufficient to resolve the resulting problematic. Being able to address only $2^{32}$ Internet nodes started becoming a serious concern that was subsequently temporarily dismissed due to the aggressive use of Network Address Translation (NAT). As collateral damage, NAT heavily endangered one of the core principles of the Internet--end-to-end connectivity. The only possible long-term solution to the IPv4 address exhaustion and end-to-end connectivity problem appears to be transitioning the
Internet from the “old” IPv4 protocol to the “new” IPv6 protocol. This must be done because IPv4 and IPv6 are incompatible. However, transitioning such a large and complex system is not an easy task, particularly if applying
“hacks” continues to solve the most difficult problems and if motivation appears to be far off and misty. Many transition mechanisms have been proposed in order to solve this task and make the transition less painful for users. A scientific approach to the development, analysis and evaluation of these mechanisms is crucial in order to avoid as much hassle as possible during the transition as well as during the coexistence period of the IPv4 and IPv6 protocols.
In this thesis, we thoroughly address the IPv6 transition problem. Even
though the IPv6 protocol was standardized more than a decade and a half ago,
we show that the transition has not yet gained its momentum. We examine how
the transition to the IPv6 was approached and executed through time and what
are the major drawbacks and drivers in this ongoing process. We identify two
major groups of transition mechanisms: IPv6 deployment mechanisms, which are
used to introduce IPv6 connectivity into IPv4-only networks, and IPv4 address
sharing mechanisms, which are used to assure the long-term co-existence of
the IPv4 and IPv6 protocols on the Internet by enabling ISPs to allocate a
single IPv4 address to multiple subscribers. We analyse the current state of
the transition and systematically review a large number of the IPv6
transition mechanisms that have been proposed thus far.
We then go one step further in approaching IPv4 address sharing mechanisms.
In recognition that it is difficult to scientifically examine the actual
proposals of various mechanisms, we develop a classification system by
defining five dimensions. We classify existing IPv4 address sharing
mechanisms into nine distinct classes and analyse mechanism properties by
systematically analysing possible values along the dimensions. To enable
practitioners to understand the tradeoffs between different mechanism
classes, we asses the key advantages and disadvantages of individual classes
in the tradeoff analysis.
By defining the dimensions for the classification, we construct a
5-dimensional space of all possible IPv4 address sharing mechanisms. We
identify a combination of properties that result in another useful IPv4
address sharing mechanism - AP64. We define the architecture and function of
this mechanism and provide all the technical details for its implementation.
Finally, we propose a theoretical performance analysis framework for IPv4
address sharing mechanisms. While conducting this research, it has become
apparent that it is indeed challenging to generally evaluate the performance
of different mechanisms because they are complex and difficult to implement.
Also, the implementations of whole mechanisms are difficult to obtain. To
alleviate this problem, we decompose the mechanism classes into basic packet
operations and experimentally evaluate their performance. We tackle space and
time requirements for the mechanisms and establish a resulting framework that
may be used as a tool to evaluate the performance of future mechanisms by
classifying them using the proposed classification system and identifying
their basic packet operations.
IPv4
Internet layer
IPv6 address
Reserved IP addresses
Cite
Citations (1)
IPv6 Neighbor Discovery (IPv6ND) specifies a control message set for
nodes to discover neighbors, routers, prefixes and other services on
the link. It also supports a manner of StateLess Address
AutoConfiguration (SLAAC), while the Dynamic Host Configuration
Protocol for IPv6 (DHCPv6) specifies a separate stateful service. This
document presents IPv6ND extensions for providing a unified
stateful/stateless configuration service.
Cite
Citations (0)