IPv6 transition techniques for legacy application

  • Authors:
  • A. Dutta;J. Alberi;A. Cheng;B. Horgan;T. McAuley;D. Chee;B. Lyles

  • Affiliations:
  • Telcordia Technologies, Piscataway, New Jersey;Telcordia Technologies, Piscataway, New Jersey;Telcordia Technologies, Piscataway, New Jersey;Telcordia Technologies, Piscataway, New Jersey;Telcordia Technologies, Piscataway, New Jersey;Telcordia Technologies, Piscataway, New Jersey;Telcordia Technologies, Piscataway, New Jersey

  • Venue:
  • MILCOM'06 Proceedings of the 2006 IEEE conference on Military communications
  • Year:
  • 2006

Quantified Score

Hi-index 0.00

Visualization

Abstract

As part of Army's IPv6 transition initiative there are several deployment issues that need to be solved. These include transition at several layers of the protocol stack. Army has a suite of legacy applications that currently work on IPv4 systems. Before Army moves to an all IPv6 network, it will need to go through a period of transition where both IPv4 and IPv6 networks, applications will need to co-exist and interoperate. While the IETF has proposed several ways the transition can take place, we have focused our discussion on application transition. As part of this effort we choose the Army's heavily used legacy application MCS-L (Maneuver Control System-Lite) and applied several transition technologies. We took advantage of Telcordia's Dynamic Slicing Tool to study the MCS-L code and made appropriate changes to make MCS-L IPv6 compatible. We tested several transition technologies such as dual stacking, Application Layer Gateway (ALG), Tunnel Broker and NAT-PT with MCS-L application. Both multicast and unicast mode of communication associated with MCS-L were also tested.