IPv4 Residual Deployment via IPv6 - a Stateless Solution (4rd)

The information below is for an old version of the document
Document Type Expired Internet-Draft (softwire WG)
Last updated 2013-04-25 (latest revision 2012-10-22)
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state Expired
Consensus Boilerplate Unknown
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


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.


Sheng Jiang (jiangsheng@huawei.com)
Remi Despres (despres.remi@laposte.net)
Reinaldo Penno (repenno@cisco.com)
Yiu Lee (yiu_lee@cable.comcast.com)
Gang Chen (phdgang@gmail.com)
Maoke Chen (fibrib@gmail.com)

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