Re: [v4tov6transition] Comment on draft-despres-softwire-6a44-01.txt

Rémi Després <remi.despres@free.fr> Thu, 21 October 2010 10:31 UTC

Return-Path: <remi.despres@free.fr>
X-Original-To: v4tov6transition@core3.amsl.com
Delivered-To: v4tov6transition@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A50323A6934; Thu, 21 Oct 2010 03:31:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level:
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5 tests=[AWL=0.500, 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 Bo+WRy7FZVrN; Thu, 21 Oct 2010 03:31:56 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by core3.amsl.com (Postfix) with ESMTP id 661013A689F; Thu, 21 Oct 2010 03:31:53 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id 59B567000085; Thu, 21 Oct 2010 12:33:26 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id 111A67000084; Thu, 21 Oct 2010 12:33:25 +0200 (CEST)
X-SFR-UUID: 20101021103326710.111A67000084@msfrf2404.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="iso-8859-1"
From: Rémi Després <remi.despres@free.fr>
In-Reply-To: <201010211642401795469@huaweisymantec.com>
Date: Thu, 21 Oct 2010 12:33:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <335DA979-0D23-4198-9B3F-A70906AF2692@free.fr>
References: <201010151714195590072@huaweisymantec.com> <9A7A1A70-1BA0-472D-9220-9556450AE777@free.fr> <201010161015343743018@huaweisymantec.com> <4CB91E95.9000509@gmail.com> <201010211642401795469@huaweisymantec.com>
To: Dong Zhang <zhangdong_rh@huaweisymantec.com>
X-Mailer: Apple Mail (2.1081)
Cc: softwires <softwires@ietf.org>, v4tov6transition <v4tov6transition@ietf.org>
Subject: Re: [v4tov6transition] Comment on draft-despres-softwire-6a44-01.txt
X-BeenThere: v4tov6transition@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <v4tov6transition.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v4tov6transition>
List-Post: <mailto:v4tov6transition@ietf.org>
List-Help: <mailto:v4tov6transition-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 10:31:57 -0000

Le 21 oct. 2010 à 10:42, Dong Zhang a écrit :

>> ...
>> Why? When I have to restart my IPv4-only ADSL box, I lose all
>> sessions, and for all I know I get a different IPv4 address.
>> So why do I care if 6a44 loses state too?
>> 
>> Certainly the IPv6 client host must be forced to restart
>> the 6a44 process when this happens. We do need a method of
>> forcing that.
> Maybe after the CPE box restarts, it could send an announcement message to arise the 6a44 hosts restart the IPv6 address application process.


Not that the host, with the current specification, will remain at most 29 s without getting its new IPv6 address after a CPE reset:
- It refreshes its CPE port mapping at least every 29 s.
- The 6a44-S, if it notices an inconsistency between the IPv6 source address and IPv4 A+P, returns a updated address indication to the right A+P.

Regards,
RD