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

Dong Zhang <zhangdong_rh@huaweisymantec.com> Tue, 19 October 2010 02:36 UTC

Return-Path: <zhangdong_rh@huaweisymantec.com>
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 D0A9F3A6AE9; Mon, 18 Oct 2010 19:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.352
X-Spam-Level:
X-Spam-Status: No, score=0.352 tagged_above=-999 required=5 tests=[AWL=0.847, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 VSuCCcCglZRq; Mon, 18 Oct 2010 19:36:04 -0700 (PDT)
Received: from mta1.huaweisymantec.com (unknown [218.17.155.14]) by core3.amsl.com (Postfix) with ESMTP id 4EA983A6A84; Mon, 18 Oct 2010 19:35:13 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=gb2312
Received: from hstml01-in.huaweisymantec.com ([172.26.3.41]) by hstga01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0LAI006HAN7P0T40@hstga01-in.huaweisymantec.com>; Tue, 19 Oct 2010 10:35:49 +0800 (CST)
Received: from z90001956 ([10.27.154.169]) by hstml01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTPA id <0LAI008FQN7QU210@hstml01-in.huaweisymantec.com>; Tue, 19 Oct 2010 10:35:50 +0800 (CST)
Date: Tue, 19 Oct 2010 10:35:37 +0800
From: Dong Zhang <zhangdong_rh@huaweisymantec.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <201010151714195590072@huaweisymantec.com> <9A7A1A70-1BA0-472D-9220-9556450AE777@free.fr> <201010161015343743018@huaweisymantec.com> <4CB91E95.9000509@gmail.com>
Message-id: <201010191035366100991@huaweisymantec.com>
X-Mailer: Foxmail 6, 10, 201, 20 [cn]
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: Tue, 19 Oct 2010 02:36:07 -0000

Hi Brain,

Brian E Carpenter 2010-10-16 Wrote:
>On 2010-10-16 15:15, Dong Zhang wrote:
>> Hi Remi,
>> Please see inline.
>
>...
>>>> Is the A:W<->N:Z mapping created staticly? Or dynimicly?
>>> Dynamically when the 6a44-C starts operation.
>>> It then remains static until the 6a44 client or the NAT is reset. 
>> That is say it is similar to a kind of permanent state once the mapping is created, supposing that there no NAT reboot and power off. Right? If so, the interruption issue of CPE should be considered. 6a44 still needs to guarantee the state recovery, right?
>
>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.
Yes, this is what I mean. If the client still uses the old 6a44 address after ADSL restart, 6a44 will not work. So the host should realize the restart of ADSL box.

Thanks.

>
>   Brian


------------------				 
Dong Zhang
2010-10-19