Re: [Softwires] WG Review: Recharter of Softwires (softwire) - 4rd updated ref

Rémi Després <remi.despres@free.fr> Thu, 24 March 2011 15:32 UTC

Return-Path: <remi.despres@free.fr>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76BFE28C0F5; Thu, 24 Mar 2011 08:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.291
X-Spam-Level:
X-Spam-Status: No, score=-1.291 tagged_above=-999 required=5 tests=[AWL=0.658, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QB-mSe4bqHOz; Thu, 24 Mar 2011 08:32:17 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.4]) by core3.amsl.com (Postfix) with ESMTP id 760F43A68EA; Thu, 24 Mar 2011 08:32:17 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2101.sfr.fr (SMTP Server) with ESMTP id 64D6370000C6; Thu, 24 Mar 2011 16:33:51 +0100 (CET)
Received: from [192.168.0.14] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2101.sfr.fr (SMTP Server) with ESMTP id 301E270000CD; Thu, 24 Mar 2011 16:33:50 +0100 (CET)
X-SFR-UUID: 20110324153351197.301E270000CD@msfrf2101.sfr.fr
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1082)
From: Rémi Després <remi.despres@free.fr>
In-Reply-To: <20110321212944.80DA33A68DD@core3.amsl.com>
Date: Thu, 24 Mar 2011 16:33:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC7701D4-D11E-4B57-B096-ED6D5956DA7B@free.fr>
References: <20110321212944.80DA33A68DD@core3.amsl.com>
To: Softwires-wg <softwires@ietf.org>, IESG <iesg@ietf.org>
X-Mailer: Apple Mail (2.1082)
Subject: Re: [Softwires] WG Review: Recharter of Softwires (softwire) - 4rd updated ref
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2011 15:32:18 -0000

Hello all,

I just noted that he reference to a 4rd draft in the Softwire page "datatracker.ietf.org/wg/softwire" is obsolete.

For IETF 80, the right reference is:
 datatracker.ietf.org/doc/draft-despres-intarea-4rd/
(the ref to intarea is just historical)

Regards,
RD



<<<
Internet Engineering Task Force                          R. Despres, Ed.
Internet-Draft                                                 RD-IPtech
Intended status: Standards Track                           S. Matsushima
Expires: September 15, 2011                                     SoftBank
                                                             T. Murakami
                                                             IP Infusion
                                                                O. Troan
                                                                   Cisco
                                                          March 14, 2011


      IPv4 Residual Deployment across IPv6-Service networks (4rd)
                        ISP-NAT's made optional
                      draft-despres-intarea-4rd-01

Abstract

   This document specifies an automatic tunneling mechanism for
   providing IPv4 connectivity service to end users over a service
   provider's IPv6 network.  During the long transition period from IPv4
   to IPv6-only, a service provider's network will have to support IPv6,
   but will also have to maintain some IPv4 connectivity for a number of
   customers, for both outgoing and incoming connections, and for both
   exclusive and shared IPv4 addresses.  The 4rd solution (IPv4 Residual
   Deployment) is designed as a lightweight solution for this.

   In some scenarios, 4rd can dispense ISPs from supporting any NAT in
   their networks.  In some others it can be used in parallel with NAT-
   based solutions such as DS-lite and/or NAT64/DNS4.
>>>