RE: [v6ops] draft-liu-v6ops-ula-usage-analysis-02

"Liubing (Leo)" <leo.liubing@huawei.com> Fri, 23 March 2012 05:34 UTC

Return-Path: <leo.liubing@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B6BE21F8469; Thu, 22 Mar 2012 22:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.246
X-Spam-Level:
X-Spam-Status: No, score=-0.246 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OfIR8Qw9lA09; Thu, 22 Mar 2012 22:34:01 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id B9DA521F8468; Thu, 22 Mar 2012 22:34:01 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AEP96741; Fri, 23 Mar 2012 01:34:01 -0400 (EDT)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 22 Mar 2012 22:31:02 -0700
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 22 Mar 2012 22:31:09 -0700
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml404-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Fri, 23 Mar 2012 13:31:03 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IPv6 Operations <v6ops@ietf.org>
Subject: RE: [v6ops] draft-liu-v6ops-ula-usage-analysis-02
Thread-Topic: [v6ops] draft-liu-v6ops-ula-usage-analysis-02
Thread-Index: AQHNCKO8Z4KSGk/lHk+mkdEjskALJpZ3UmnA
Date: Fri, 23 Mar 2012 05:31:02 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F4524A26650@szxeml509-mbs>
References: <4F6BEB95.60608@gmail.com>
In-Reply-To: <4F6BEB95.60608@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.4.84]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Fri, 23 Mar 2012 00:46:43 -0700
Cc: "homenet@ietf.org" <homenet@ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 05:34:02 -0000

Hi, Brian

There comes comments finally :-) Thanks for your concern about the draft.  

I've noticed the discussion in 6man and homenet, which is more in-depth technical issue while the ULA usage draft is more general use cases. But I think it is exactly valuable input and consideration to the ULA draft for the further step.  

I am also confused about the relationship between the discussion in various WGs and the ULA draft.
We should cover all the specific issues in the draft, or just limit the discussion within each WG while the draft only focus on general use cases?


> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> Sent: Friday, March 23, 2012 11:19 AM
> To: IPv6 Operations
> Subject: [v6ops] draft-liu-v6ops-ula-usage-analysis-02
> 
> Hi,
> 
> I think this draft is a considerable improvement on the -00 version.
> It still needs some work on the English, but I think the main points
> are covered now and the work should continue.
> 
> However, there is clearly a complication, which is that this document
> needs to be aligned with whatever consensus appears in homenet about
> ULAs, and with whatever consensus appears in 6man about RFC3484bis.
> 
> In particular, homenet is hitting the problem of what happens when
> multiple ULA prefixes show up automatically in the same network. That
> may not be recommended practice, but it seems very likely to happen,
> and raises routing and address-selection questions.
> 
> I think the various WG Chairs need to agree how the discussion should
> be managed, because it might get complicated with three WGs involved
> (or four, if you count 6renum).
> 
> Regards
>    Brian
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops