IEICE TRANSACTIONS on Communications
Evaluating IPv6 Application Transition
Summary :
Even though various kinds of IPv6 transition mechanisms have been developed for the transition to an IPv6 network, these transition mechanisms take no stance on whether applications support IPv6 or not. This paper describes why the transition period between IPv4 and IPv6 applications may not be straightforward and applications should be ported to support both IPv4 and IPv6; such applications are called "IP version-independent applications." Also, this paper examines and empirically evaluates overhead of the IP version-independent applications, since the performance implication is not well known. The overhead might be very dependent on data sizes and network performance, but it was relatively minimized for general Internet traffic with larger data sizes and lower network latency.
- Publication
- IEICE TRANSACTIONS on Communications Vol.E89-B No.3 pp.982-984
- Publication Date
- 2006/03/01
- Publicized
- Online ISSN
- 1745-1345
- DOI
- 10.1093/ietcom/e89-b.3.982
- Type of Manuscript
- LETTER
- Category
- Internet
Authors
Keyword
Latest Issue
Copyrights notice of machine-translated contents
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Cite this
Copy
Myung-Ki SHIN, "Evaluating IPv6 Application Transition" in IEICE TRANSACTIONS on Communications,
vol. E89-B, no. 3, pp. 982-984, March 2006, doi: 10.1093/ietcom/e89-b.3.982.
Abstract: Even though various kinds of IPv6 transition mechanisms have been developed for the transition to an IPv6 network, these transition mechanisms take no stance on whether applications support IPv6 or not. This paper describes why the transition period between IPv4 and IPv6 applications may not be straightforward and applications should be ported to support both IPv4 and IPv6; such applications are called "IP version-independent applications." Also, this paper examines and empirically evaluates overhead of the IP version-independent applications, since the performance implication is not well known. The overhead might be very dependent on data sizes and network performance, but it was relatively minimized for general Internet traffic with larger data sizes and lower network latency.
URL: https://global.ieice.org/en_transactions/communications/10.1093/ietcom/e89-b.3.982/_p
Copy
@ARTICLE{e89-b_3_982,
author={Myung-Ki SHIN, },
journal={IEICE TRANSACTIONS on Communications},
title={Evaluating IPv6 Application Transition},
year={2006},
volume={E89-B},
number={3},
pages={982-984},
abstract={Even though various kinds of IPv6 transition mechanisms have been developed for the transition to an IPv6 network, these transition mechanisms take no stance on whether applications support IPv6 or not. This paper describes why the transition period between IPv4 and IPv6 applications may not be straightforward and applications should be ported to support both IPv4 and IPv6; such applications are called "IP version-independent applications." Also, this paper examines and empirically evaluates overhead of the IP version-independent applications, since the performance implication is not well known. The overhead might be very dependent on data sizes and network performance, but it was relatively minimized for general Internet traffic with larger data sizes and lower network latency.},
keywords={},
doi={10.1093/ietcom/e89-b.3.982},
ISSN={1745-1345},
month={March},}
Copy
TY - JOUR
TI - Evaluating IPv6 Application Transition
T2 - IEICE TRANSACTIONS on Communications
SP - 982
EP - 984
AU - Myung-Ki SHIN
PY - 2006
DO - 10.1093/ietcom/e89-b.3.982
JO - IEICE TRANSACTIONS on Communications
SN - 1745-1345
VL - E89-B
IS - 3
JA - IEICE TRANSACTIONS on Communications
Y1 - March 2006
AB - Even though various kinds of IPv6 transition mechanisms have been developed for the transition to an IPv6 network, these transition mechanisms take no stance on whether applications support IPv6 or not. This paper describes why the transition period between IPv4 and IPv6 applications may not be straightforward and applications should be ported to support both IPv4 and IPv6; such applications are called "IP version-independent applications." Also, this paper examines and empirically evaluates overhead of the IP version-independent applications, since the performance implication is not well known. The overhead might be very dependent on data sizes and network performance, but it was relatively minimized for general Internet traffic with larger data sizes and lower network latency.
ER -
English
