Skip to main content

IPv4 Residual Deployment via IPv6 - a Stateless Solution (4rd)
draft-ietf-softwire-4rd-04

The information below is for an old version of the document.
Document Type Expired Internet-Draft (softwire WG)
Authors Sheng Jiang , Remi Despres , Reinaldo Penno , Yiu Lee , Gang Chen , Maoke Chen
Last updated 2013-04-25 (Latest revision 2012-10-22)
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
plain text htmlized pdfized bibtex
Reviews
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 can be found at:
https://www.ietf.org/archive/id/draft-ietf-softwire-4rd-04.txt

Abstract

The 4rd automatic tunneling mechanism makes IPv4 Residual Deployment possible via IPv6 networks without maintaining for this per-customer states in 4rd-capable nodes (reverse of the IPv6 Rapid Deployment of 6rd). To cope with the IPv4 address shortage, customer sites can be assigned shared public IPv4 addresses with restricted port sets.

Authors

Sheng Jiang
Remi Despres
Reinaldo Penno
Yiu Lee
Gang Chen
Maoke Chen

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