Embedding Port Information in IPv4-Translatable IPv6 Prefixes and IPv4- Embedded IPv6 Addresses
draft-boucadair-softwire-stateless-rfc6052-update-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Nejc Skoberne , Xing Li , Congxiao Bao | ||
Last updated | 2011-09-08 (Latest revision 2011-09-07) | ||
Replaced by | draft-boucadair-softwire-stateless-requirements | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-boucadair-softwire-stateless-requirements | |
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
RFC6052 specifies the algorithmic translation of an IPv6 address to a corresponding IPv4 address, and vice versa. In particular, RFC6052 specifies the address format to build IPv4-converted and IPv4- translatable IPv6 addresses. In order to be deployed in the context of stateless 4/6 solutions, RFC6052 should be updated so that IPv4- embedded IPv6 addresses convey the port information. This document identifies a set of requirements to be taken into account when updating RFC6052 for that purpose. A companion effort, document at [I-D.bsd-softwire-stateless-port-index-analysis], is required to converge on one or a set of algorithms to be used by all stateless solutions.
Authors
Nejc Skoberne
Xing Li
Congxiao Bao
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)