Subject: [Softwires] 4 Japanese ISPs intending to adopt 4rd - IETF spec needed

From: Rémi Després <[email-masked]>
Date: Thu, 4 Nov 2010 13:58:45 +0100

Hi, all,

FWI, here are extracts from mails exchanged on the v4tov6transition list.

The proposed 4rd specification is tools.ietf.org/id/draft-despres-softwire-4rd-00.

As 4rd is likely to have only a very short presentation time on Monday morning (if any at all in view of the posted agenda), these extracts are IMHO worth looking at, to understand the importance of getting an 4rd specification in IETF.

Good reading, and best regards,
RD

1.  From Satoru Matsushima, on September 2, 2010:
> ...
> FYI,
> SPs in Japan, BBIX, Internet Multifeed, JPIX and IIJ-II unveil the intention of 
> adopting SAM/4rd as a solution for their IPv4 service over IPv6 native network.
> 
> We then support including Remi's helpful comment for section 4.3 in the draft.
> 
> Please take look at these joint press release.
> 
> BBIX:
> http://www.bbix.net/press/file/press_20100831.pdf
> 
> Internet Multifeed:
> http://www.mfeed.co.jp/press/2010/pdf/20100831.pdf
> 
> JPIX:
> http://www.jpix.ad.jp/jp/pdf/20100831_001.pdf
> 
> IIJ-II:
> http://www.iij.ad.jp/news/pressrelease/2010/0831.html
> 
> 
> Since these documents are written in Japanese originally, English page does not 
> available by now.
> ... 

2.  From Satoru Matsushima, on September 20, 2010: 
> ...
> Here is the summary of press release contents from Japanese ISPs. 
> ...
> o They had co-worked to find what most efficient solution for IPv4 service over native IPv6 network.
> o The background is that they are going to provide IPv6 service from 2011, but they also need to 
>   provide IPv4 service as well.
> o Significant requirements for the solution are:
> 
>  1. Sharing a IPv4 address among many of customers with highest cost efficiency
>     -> The analogy of SAM/4rd is as same as 6rd, it could be expected that high cost efficiency with 
>        stateless operation. NAT state only exist on the CPE side.
> 
>  2. As much as simple provisioning and configuration
>     -> CPE can automatically configure its IPv4 address from delegated IPv6 prefix.
> 
>  3. Optimized routing path for IPv4 service on the native IPv6 network (need mesh capability)
>     -> SAM/4rd allow CPE to CPE packet flow on optimized routing path in the IPv6 network.
> 
> Since 4rd (IPv4 residual deployment), which is a part of IPv4 over IPv6 scenario of SAM
> (draft-despres-softwire-sam) satisfy these requirements, the ISPs intent to adopt SAM/4rd 
> for their IPv4 solution.