Translation Spot Negotiation in IPv4/IPv6-Coexist Mesh
draft-cui-softwire-pet-03

Document Type Expired Internet-Draft (individual)
Last updated 2010-10-25
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-cui-softwire-pet-03.txt

Abstract

IPv4 and IPv6 are expected to coexist for a long period. Currently, there are many IPv4/IPv6 transition/coexistence techniques, roughly divided into the categories of tunneling and translation. Tunneling and translation have respective application scopes, and translation has some technical limitations, including scalability issue, application layer translation, operation complexity, etc. To improve the availability of translation, this draft proposes the method of selecting appropriate translation spot to execute translation. When the translation spot is not on IPv4-IPv6 border, tunnel is used to achieve the traversing between translation spot and IP border. This method applies well in mesh scenario where both IPv4 and IPv6 client network exists, and BGP can be extended to achieve a translation spot signaling.

Authors

Yong Cui (cy@csnet1.cs.tsinghua.edu.cn)
Mingwei Xu (xmw@csnet1.cs.tsinghua.edu.cn)
Peng Wu (weapon@csnet1.cs.tsinghua.edu.cn)
Shengling Wang (slwang@csnet1.cs.tsinghua.edu.cn)
Jianping Wu (jianping@cernet.edu.cn)
Xing Li (xing@cernet.edu.cn)
Chris Metz (chmetz@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)