Subject: [Softwires] FW: New Version Notification for draft-ietf-softwire-4rd-06.txt

From: Sheng Jiang <[email-masked]>
Date: Thu, 11 Jul 2013 07:42:38 +0000

Hi, Softwires,

The 4rd authors have just updated the draft. This update is mainly solve the incomplete modification regarding to NAT64+ in last update, in which we adapted to 6man conclusion - no IID-range reservations. This issue was raised by Remi (below email). The authors think it is now fulled addressed.

http://www.ietf.org/mail-archive/web/softwires/current/msg05444.html

Best regards,

Sheng

>-----Original Message-----
>From: [email-masked] [mailto:[email-masked]]
>Sent: Thursday, July 11, 2013 3:39 PM
>To: Remi Despres; Reinaldo Penno; Gang Chen; Sheng Jiang; Yiu Lee; Maoke
>Chen
>Subject: New Version Notification for draft-ietf-softwire-4rd-06.txt
>
>
>A new version of I-D, draft-ietf-softwire-4rd-06.txt
>has been successfully submitted by Remi Despres and posted to the
>IETF repository.
>
>Filename:	 draft-ietf-softwire-4rd
>Revision:	 06
>Title:		 IPv4 Residual Deployment via IPv6 - a Stateless Solution (4rd)
>Creation date:	 2013-07-11
>Group:		 softwire
>Number of pages: 38
>URL:
>http://www.ietf.org/internet-drafts/draft-ietf-softwire-4rd-06.txt
>Status:          http://datatracker.ietf.org/doc/draft-ietf-softwire-4rd
>Htmlized:        http://tools.ietf.org/html/draft-ietf-softwire-4rd-06
>Diff:
>http://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-4rd-06
>
>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. 4rd
>   can also support the scenarios that customer sites are assigned full
>   public IPv4 addresses or a set of public IPv4 addresses.
>
>
>
>
>The IETF Secretariat