Dual Stack deployment using DSTM and 6to4
draft-ietf-ngtrans-6to4-dstm-00
| Document | Type |
Expired Internet-Draft
(ngtrans WG)
Expired & archived
|
|
|---|---|---|---|
| Author | George K. Tsirtsis | ||
| Last updated | 2001-01-24 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
It is desirable that most of IPv6 deployment is based on Dual Stack IPv4 and IPv6 nodes so that interoperability with the current IPv4 based Internet be seamless. The 6to4 transition mechanism offers a automated mechanisms for addressing an IPv6 site as well as interconnectivity with other IPv6 sites when no native IPv6 connectivity is available.[DSTM] provides a mechanism for dynamic IPv4 address allocation to Dual Stack nodes and a mechanism to send packets over a network that only supports IPv6 routing. By combining the two mechanisms we show how Dual Stack Intranets may be deployed with minimum need for IPv4 address space and no native IPv6 connectivity.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)