Re: [v4tov6transition] [v6ops] Charter clarification discussion
Tina TSOU <tena@huawei.com> Wed, 22 September 2010 05:57 UTC
Return-Path: <tena@huawei.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 B7DEF3A68DB; Tue, 21 Sep 2010 22:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.22
X-Spam-Level:
X-Spam-Status: No, score=-100.22 tagged_above=-999 required=5 tests=[AWL=-0.326, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 6rbOY0zJHHtk; Tue, 21 Sep 2010 22:57:13 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 729743A6AEE; Tue, 21 Sep 2010 22:56:26 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L94001LAWG424@szxga03-in.huawei.com>; Wed, 22 Sep 2010 13:55:17 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9400MIMWG4HP@szxga03-in.huawei.com>; Wed, 22 Sep 2010 13:55:16 +0800 (CST)
Received: from [192.168.1.4] ([113.116.43.122]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L94009CXWG4YY@szxml01-in.huawei.com>; Wed, 22 Sep 2010 13:55:16 +0800 (CST)
Date: Wed, 22 Sep 2010 13:55:14 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <72E93F80-B792-4062-950C-0F56D1B2CCAF@cisco.com>
To: Fred Baker <fred@cisco.com>
Message-id: <ED693C76-387A-4C9F-918F-E5DDFBFCCA30@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: multipart/alternative; boundary="Boundary_(ID_wYQcdXLGAApOrzB7xtOkUA)"
References: <9267FA37-A97B-4794-BB93-E1A7D86B7BAB@cisco.com> <C8BE4364.EF87%victor.kuarsingh@gmail.com> <m2eicn3yyt.wl%randy@psg.com> <AANLkTi=gGdTPMsNbGCdXjCqSFz7rEkJJ0DpMCk_h9DUf@mail.gmail.com> <82239B09-87B2-435B-8554-54F5F213C030@cisco.com> <m21v8n3ru5.wl%randy@psg.com> <72E93F80-B792-4062-950C-0F56D1B2CCAF@cisco.com>
Cc: Randy Bush <randy@psg.com>, v6ops@ietf.org, v4tov6transition@ietf.org
Subject: Re: [v4tov6transition] [v6ops] Charter clarification discussion
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: Wed, 22 Sep 2010 05:57:19 -0000
Hi all, In the end of the v4v6tran Webex meeting, we doubled checked with the v6ops chair and the AD, "if the network is not v6 only, not DS, it is the v4 network in the process transitioning to v6 (e.g. using NAT44(4), tunneling etc), is it in the (being updated) charter of v6ops?" The answer from the v6ops chair and the AD is yes. V4 network in the process transitioning to v6, DS, v6 only are in a package. That means, the content of draft-yang-v4v6tran-ipv6-transition- guide-00 et al (the use cases, transition guide for cable, broadband, mobile for large scale operators) except the addressing scheme is in the (being updated) charter of v6ops. B. R. Tina http://tinatsou.weebly.com On Sep 22, 2010, at 2:01 AM, Fred Baker wrote: > > On Sep 21, 2010, at 10:54 AM, Randy Bush wrote: > >>>> I thought Fred make this clear on the call last night v6ops will >>>> take >>>> into consideration all architectures that involve IPv6, including >>>> the >>>> IPv4 side of an IPv6 transition network (DS-lite, 6RD, DS >>>> +NAT44). It >>>> will not take into consideration IPv4-only network (NAT444 with no >>>> IPv6). >>> >>> That is literally what I said. >>> >>> Randy, I'm kind of scratching my head here. If I read you correctly, >>> you are of the opinion that only IPv6 issues need apply; >> >> no. that is not what i said. i said ipv4-only issues need not >> apply, >> e.g. nat4* when ipv6 is not used as an assist >> >> as camron said, i suspect that we are in agreement. > > ack > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops