
From jiangsheng@huawei.com  Tue Jul  5 00:28:40 2011
Return-Path: <jiangsheng@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE87A21F876C for <renum@ietfa.amsl.com>; Tue,  5 Jul 2011 00:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pOF9IYxc83ty for <renum@ietfa.amsl.com>; Tue,  5 Jul 2011 00:28:39 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 36ED721F875A for <renum@ietf.org>; Tue,  5 Jul 2011 00:28:16 -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 <0LNU00KDENEYLV@szxga03-in.huawei.com> for renum@ietf.org; Tue, 05 Jul 2011 15:28:10 +0800 (CST)
Received: from szxrg02-dlp.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 <0LNU00822NESYY@szxga03-in.huawei.com> for renum@ietf.org; Tue, 05 Jul 2011 15:28:10 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml207-edg.china.huawei.com) ([172.24.2.119])	by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ABT33633; Tue, 05 Jul 2011 15:28:09 +0800 (CST)
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 05 Jul 2011 15:28:06 +0800
Received: from SZXEML504-MBX.china.huawei.com ([169.254.8.3]) by szxeml411-hub.china.huawei.com ([10.82.67.138]) with mapi id 14.01.0270.001; Tue, 05 Jul 2011 15:28:09 +0800
Date: Tue, 05 Jul 2011 07:27:37 +0000
From: Jiangsheng <jiangsheng@huawei.com>
X-Originating-IP: [10.110.98.101]
To: "renum@ietf.org" <renum@ietf.org>
Message-id: <5D36713D8A4E7348A7E10DF7437A4B9286B056@SZXEML504-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: en-GB, zh-CN, en-US
Thread-topic: New Version Notification for draft-jiang-6renum-enterprise-00.txt
Thread-index: AQHMOiQc7Sw4YhA7hUmGORgkTKbQ9JTc99TQ
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
Subject: [renum] FW: New Version Notification for draft-jiang-6renum-enterprise-00.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 07:28:41 -0000

Hi, all,

A new draft draft-jiang-6renum-enterprise-00 has been submitted to 6renum WG. This document analyzes the enterprise renumbering events and gives the recommendations among the existing renumbering mechanisms. This document has replaced earlier draft-jiang-ipv6-site-renum-guideline.

Any comments are welcome!

Best regards,

Sheng

> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Monday, July 04, 2011 4:26 PM
> To: Jiangsheng
> Cc: brian.e.carpenter@gmail.com; Leo Liu(bing); Jiangsheng
> Subject: New Version Notification for draft-jiang-6renum-enterprise-
> 00.txt
> 
> A new version of I-D, draft-jiang-6renum-enterprise-00.txt has been
> successfully submitted by Sheng Jiang and posted to the IETF repository.
> 
> Filename:	 draft-jiang-6renum-enterprise
> Revision:	 00
> Title:		 IPv6 Enterprise Network Renumbering Scenarios and
> Guidelines
> Creation date:	 2011-07-01
> WG ID:		 Individual Submission
> Number of pages: 15
> 
> Abstract:
>    This document analyzes the enterprise renumbering events and gives
>    the recommendations among the existing renumbering mechanisms.
>    According to the different stages of renumbering events,
>    considerations and best current recommendations are described in
>    three categories: during network design, for preparation of
>    renumbering, and during renumbering operation. A gap inventory is
>    listed at the end of this document.
> 
> 
> 
> 
> The IETF Secretariat

From leo.liubing@huawei.com  Tue Jul  5 01:03:17 2011
Return-Path: <leo.liubing@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24FBF21F8747 for <renum@ietfa.amsl.com>; Tue,  5 Jul 2011 01:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.095
X-Spam-Level: 
X-Spam-Status: No, score=0.095 tagged_above=-999 required=5 tests=[AWL=2.694,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nW2SK6l3J0vn for <renum@ietfa.amsl.com>; Tue,  5 Jul 2011 01:03:16 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 0674F21F8742 for <renum@ietf.org>; Tue,  5 Jul 2011 01:03:16 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNU0065WP0MMF@szxga05-in.huawei.com> for renum@ietf.org; Tue, 05 Jul 2011 16:02:47 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNU00265P0FDA@szxga05-in.huawei.com> for renum@ietf.org; Tue, 05 Jul 2011 16:02:46 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml203-edg.china.huawei.com) ([172.24.2.119])	by szxrg01-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACG92777; Tue, 05 Jul 2011 16:02:46 +0800 (CST)
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 05 Jul 2011 16:02:42 +0800
Received: from SZXEML502-MBS.china.huawei.com ([169.254.2.87]) by szxeml412-hub.china.huawei.com ([169.254.226.192]) with mapi id 14.01.0270.001; Tue, 05 Jul 2011 16:02:45 +0800
Date: Tue, 05 Jul 2011 08:02:42 +0000
From: "Leo Liu(bing)" <leo.liubing@huawei.com>
X-Originating-IP: [10.110.98.62]
To: "renum@ietf.org" <renum@ietf.org>
Message-id: <8AE0F17B87264D4CAC7DE0AA6C406F45017F5BB6@SZXEML502-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: zh-CN, en-US
Thread-topic: New draft:  draft-liu-6renum-gap-analysis-00.txt
Thread-index: AQHMOjVaZPW4KXC9t0Gxoi9f9XOmhpTdSDlA
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
Subject: [renum] New draft:  draft-liu-6renum-gap-analysis-00.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 08:03:17 -0000

Hi, all

The renumbering gap analysis draft has been posted:
http://tools.ietf.org/html/draft-liu-6renum-gap-analysis-00

The 00 version intends to provide a clue for analysis and some open questions to provoke discussions rather than a decided gap list. 
So please don't stint your comments and ideas, :)
We'll continue work on it to produce a 01 version, your comments would be very useful for it.


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, July 04, 2011 6:30 PM
To: Jiangsheng
Cc: Leo Liu(bing); Jiangsheng
Subject: New Version Notification for draft-liu-6renum-gap-analysis-00.txt

A new version of I-D, draft-liu-6renum-gap-analysis-00.txt has been successfully submitted by Sheng Jiang and posted to the IETF repository.

Filename:	 draft-liu-6renum-gap-analysis
Revision:	 00
Title:		 IPv6 Site Renumbering Gap Analysis
Creation date:	 2011-07-04
WG ID:		 Individual Submission
Number of pages: 14

Abstract:
   This document briefly introduces the existing mechanisms could be
   utilized by IPv6 site renumbering and envisions the effort could be
   done under the 6renum working group. This document tries to cover the
   most explicit issues and requirements of IPv6 renumbering. Through
   the gap analysis, the document provides a basis for future work to
   identify and develop solutions or to stimulate such development as
   appropriate. The gap analysis is presented following a renumbering
   event procedure clue.



                                                                                  


The IETF Secretariat

From leo.liubing@huawei.com  Tue Jul  5 01:07:07 2011
Return-Path: <leo.liubing@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95BD621F878B for <renum@ietfa.amsl.com>; Tue,  5 Jul 2011 01:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.952
X-Spam-Level: 
X-Spam-Status: No, score=-2.952 tagged_above=-999 required=5 tests=[AWL=3.047,  BAYES_00=-2.599, J_CHICKENPOX_82=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cINN8ois-SdW for <renum@ietfa.amsl.com>; Tue,  5 Jul 2011 01:07:07 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 6986D21F8789 for <renum@ietf.org>; Tue,  5 Jul 2011 01:07:06 -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 <0LNU005UKP6J0R@szxga03-in.huawei.com> for renum@ietf.org; Tue, 05 Jul 2011 16:06:20 +0800 (CST)
Received: from szxrg02-dlp.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 <0LNU008Z2P4WYY@szxga03-in.huawei.com> for renum@ietf.org; Tue, 05 Jul 2011 16:06:19 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml202-edg.china.huawei.com) ([172.24.2.119])	by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ABT36919; Tue, 05 Jul 2011 16:06:17 +0800 (CST)
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 05 Jul 2011 16:06:12 +0800
Received: from SZXEML502-MBS.china.huawei.com ([169.254.2.87]) by szxeml401-hub.china.huawei.com ([10.82.67.31]) with mapi id 14.01.0270.001; Tue, 05 Jul 2011 16:06:16 +0800
Date: Tue, 05 Jul 2011 08:06:15 +0000
From: "Leo Liu(bing)" <leo.liubing@huawei.com>
X-Originating-IP: [10.110.98.62]
To: "renum@ietf.org" <renum@ietf.org>
Message-id: <8AE0F17B87264D4CAC7DE0AA6C406F45017F5BD3@SZXEML502-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: summary of the gap analysis draft--//FW: New draft: draft-liu-6renum-gap-analysis-00.txt
Thread-index: AQHMOuppro06IhX9/0SWcFSE/uqw+Q==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
Subject: [renum] summary of the gap analysis draft--//FW: New draft: draft-liu-6renum-gap-analysis-00.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2011 08:07:07 -0000

SWYgeW91IGRvbuKAmXQnIGhhdmUgZW5vdWdoIHRpbWUgdG8gcmVhZCB0aGUgd2hvbGUgZHJhZnQs
IGZvbGxvd2luZyBpcyBhIHN1bW1hcnkgb2YgdGhlIGRyYWZ0Og0KDQpBYnN0cmFjdDogVGhpcyBk
b2N1bWVudCBicmllZmx5IGludHJvZHVjZXMgdGhlIGV4aXN0aW5nIG1lY2hhbmlzbXMgY291bGQg
YmUgdXRpbGl6ZWQgYnkgSVB2NiBzaXRlIHJlbnVtYmVyaW5nIGFuZCBlbnZpc2lvbnMgdGhlIGVm
Zm9ydCBjb3VsZCBiZSBkb25lIHVuZGVyIHRoZSA2cmVudW0gd29ya2luZyBncm91cC4gVGhpcyBk
b2N1bWVudCB0cmllcyB0byBjb3ZlciB0aGUgbW9zdCBleHBsaWNpdCBpc3N1ZXMgYW5kIHJlcXVp
cmVtZW50cyBvZiBJUHY2IHJlbnVtYmVyaW5nLiBUaHJvdWdoIHRoZSBnYXAgYW5hbHlzaXMsIHRo
ZSBkb2N1bWVudCBwcm92aWRlcyBhIGJhc2lzIGZvciBmdXR1cmUgd29yayB0byBpZGVudGlmeSBh
bmQgZGV2ZWxvcCBzb2x1dGlvbnMgb3IgdG8gc3RpbXVsYXRlIHN1Y2ggZGV2ZWxvcG1lbnQgYXMg
YXBwcm9wcmlhdGUuIFRoZSBnYXAgYW5hbHlzaXMgaXMgcHJlc2VudGVkIGZvbGxvd2luZyBhIHJl
bnVtYmVyaW5nIGV2ZW50IHByb2NlZHVyZSBjbHVlLg0KDQpPdmVyYWxsIHJlcXVpcmVtZW50cyBm
b3IgcmVudW1iZXJpbmcgKGVudmlzaW9ucyB0aGUgZWZmb3J0IHBvdGVudGlhbGx5IGJlIGFjaGll
dmVkIGluIHRoZSBmdXR1cmUpDQpvCVByZWZpeCBkZWxlZ2F0aW9uIGFuZCBkZWxpdmVyeSBzaG91
bGQgYmUgYXV0b21hdGljIGFuZCBhY2N1cmF0ZSBpbiBhZ2dyZWdhdGlvbiBhbmQgY29vcmRpbmF0
aW9uLg0KbwlBZGRyZXNzIHJlY29uZmlndXJhdGlvbiBzaG91bGQgYmUgYXV0b21hdGljYWxseSBh
Y2hpZXZlZCB0aHJvdWdoIHN0YW5kYXJkIHByb3RvY29scyB3aXRoIG1pbmltdW0gaHVtYW4gaW50
ZXJ2ZW5lLiBbb3BlbiBxdWVzdGlvbl0gIndpdGggbm8gaHVtYW4gaW50ZXJ2ZW5lIiBwb3NzaWJs
ZT8NCm8JQWRkcmVzcyByZWxldmFudCBlbnRyaWVzIChETlMgcmVjb3JkcywgQUNMcywgZXRjLikg
dXBkYXRlIHNob3VsZCBiZSBwcm9jZXNzZWQgaW50ZWdyYWxseSBhbmQgZXJyb3ItcHJldmVudGVk
LiBbb3BlbiBxdWVzdGlvbl1JcyBpdCBuZWNlc3NhcnkgdG8gZGV2ZWxvcCBhdXRvbWF0aWMgZW50
cmllcyB1cGRhdGUgbWVjaGFuaXNtcz8gSWYgbmVjZXNzYXJ5LCBkbyB3ZSBuZWVkIHN0YW5kYXJk
IHByb3RvY29scy9pbnRlcmZhY2UgZm9yIGl0Pw0Kbwlbb3BlbiBxdWVzdGlvbl1JcyBpdCBuZWNl
c3NhcnkvcG9zc2libGUgdG8gZGV2ZWxvcCBhIOKAnE9uZS1DbGlja+KAnSBmdWxseSBhdXRvbWF0
aWMgcmVudW1iZXJpbmcgdGVjaG5vbG9neT8gV2hhdCBzY2VuYXJpb3MgaGF2ZSB0aGUgcG90ZW50
aWFsIHBvc3NpYmlsaXR5Pw0Kbwlbb3BlbiBxdWVzdGlvbl1JcyBzZXNzaW9uIHN1cnZpdmFiaWxp
dHkgd2l0aGluIG91ciBzY29wZT8NCg0KRXhpc3RpbmcgY29tcG9uZW50cyBmb3IgSVB2NiByZW51
bWJlcmluZyAoImNvbXBvbmVudHMiIGluIGN1cnJlbnQgcHJvdG9jb2xzL3Rvb2xzIGNvdWxkIGJl
IHV0aWxpemVkIGZvciByZW51bWJlcmluZykNCi0gUHJvdG9jb2xzOiBORCwgREhDUCwgREhDUC1Q
RCwgcmZjMjg5NChyb3V0ZXIgcmVudW1iZXJpbmcpLCBldGMuDQotIE1hbmFnZW1lbnQgVG9vbHM6
IFNvbWUgb3BlcmF0aW9ucyBvZiByZW51bWJlcmluZyBjb3VsZCBiZSBhdXRvbWF0aWNhbGx5IHBy
b2Nlc3NlZCBieSBtYW5hZ2VtZW50IHRvb2xzIHRvIG1ha2UgdGhlIHJlbnVtYmVyaW5nIHByb2Nl
c3MgbW9yZSBlZmZpY2llbnQgYW5kIGFjY3VyYXRlLg0KLSBQcm9jZWR1cmVzL1BvbGljaWVzOiBz
b21ldGhpbmcgbGlrZSBSRkM0MTkyLCB3aGljaCBwcm9wb3NlZCBhIHByb2NlZHVyZSBmb3IgcmVu
dW1iZXJpbmcgYSBJUHY2IG5ldHdvcmsgd2l0aG91dCBhIGZsYWcgZGF5Lg0KDQpHYXAgYW5hbHlz
aXMNClRoZSBnYXAgYW5hbHlzaXMgaXMgb3JnYW5pemVkIGJ5IHRoZSBtYWluIHN0ZXBzIG9mIHJl
bnVtYmVyaW5nIHByb2Nlc3M6DQoNCjEpIE1hbmFnaW5nIHByZWZpeCAoYSBzaG9ydCBwcmVmaXgg
bWF5IGJlIGRpdmlkZWQgaW50byBsb25nZXIgcHJlZml4ZXMgZm9yIHN1Ym5ldHMpDQogIC0gUHJl
Zml4IGRlbGVnYXRpb24NCiAgLSBQcmVmaXggYXNzaWdubWVudA0KMikgQWRkcmVzcyBDb25maWd1
cmF0aW9uDQogIC0gSG9zdCBBZGRyZXNzIENvbmZpZ3VyYXRpb24NCiAgLSBSb3V0ZXIgQWRkcmVz
cyBDb25maWd1cmF0aW9uDQogIC0gU3RhdGljIEFkZHJlc3MgQ29uZmlndXJhdGlvbg0KMykgQWRk
cmVzcyBSZWxldmFudCBFbnRyaWVzIFVwZGF0ZQ0KICAtIEROUyBSZWNvcmRzIFVwZGF0ZQ0KICAt
IEZpbHRlcnMNCjQpIFJlbnVtYmVyaW5nIEV2ZW50IE1hbmFnZW1lbnQNCnJlbnVtYmVyaW5nIGlz
IGEga2luZCBvZiBldmVudCB3aGljaCBtYXkgbmVlZCBhZGRpdGlvbmFsIHByb2Nlc3MgdG8gbWFr
ZSB0aGUgcHJvY2VzcyBtb3JlIGVhc3kgYW5kIG1hbmFnZWFibGUuDQo1KSBNaXNjZWxsYW5lb3Vz
DQogIC0gTXVsdGljYXN0DQogIC0gTW9iaWxpdHkNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCkZyb206IExlbyBMaXUoYmluZykgDQpTZW50OiBUdWVzZGF5LCBKdWx5IDA1LCAyMDExIDQ6
MDMgUE0NClRvOiByZW51bUBpZXRmLm9yZw0KU3ViamVjdDogTmV3IGRyYWZ0OiBkcmFmdC1saXUt
NnJlbnVtLWdhcC1hbmFseXNpcy0wMC50eHQNCg0KSGksIGFsbA0KDQpUaGUgcmVudW1iZXJpbmcg
Z2FwIGFuYWx5c2lzIGRyYWZ0IGhhcyBiZWVuIHBvc3RlZDoNCmh0dHA6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LWxpdS02cmVudW0tZ2FwLWFuYWx5c2lzLTAwDQoNClRoZSAwMCB2ZXJzaW9u
IGludGVuZHMgdG8gcHJvdmlkZSBhIGNsdWUgZm9yIGFuYWx5c2lzIGFuZCBzb21lIG9wZW4gcXVl
c3Rpb25zIHRvIHByb3Zva2UgZGlzY3Vzc2lvbnMgcmF0aGVyIHRoYW4gYSBkZWNpZGVkIGdhcCBs
aXN0LiANClNvIHBsZWFzZSBkb24ndCBzdGludCB5b3VyIGNvbW1lbnRzIGFuZCBpZGVhcywgOikN
CldlJ2xsIGNvbnRpbnVlIHdvcmsgb24gaXQgdG8gcHJvZHVjZSBhIDAxIHZlcnNpb24sIHlvdXIg
Y29tbWVudHMgd291bGQgYmUgdmVyeSB1c2VmdWwgZm9yIGl0Lg0KDQoNCi0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRl
cm5ldC1kcmFmdHNAaWV0Zi5vcmddIA0KU2VudDogTW9uZGF5LCBKdWx5IDA0LCAyMDExIDY6MzAg
UE0NClRvOiBKaWFuZ3NoZW5nDQpDYzogTGVvIExpdShiaW5nKTsgSmlhbmdzaGVuZw0KU3ViamVj
dDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1saXUtNnJlbnVtLWdhcC1hbmFs
eXNpcy0wMC50eHQNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWxpdS02cmVudW0tZ2Fw
LWFuYWx5c2lzLTAwLnR4dCBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFNoZW5n
IEppYW5nIGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5hbWU6CSBk
cmFmdC1saXUtNnJlbnVtLWdhcC1hbmFseXNpcw0KUmV2aXNpb246CSAwMA0KVGl0bGU6CQkgSVB2
NiBTaXRlIFJlbnVtYmVyaW5nIEdhcCBBbmFseXNpcw0KQ3JlYXRpb24gZGF0ZToJIDIwMTEtMDct
MDQNCldHIElEOgkJIEluZGl2aWR1YWwgU3VibWlzc2lvbg0KTnVtYmVyIG9mIHBhZ2VzOiAxNA0K
DQpBYnN0cmFjdDoNCiAgIFRoaXMgZG9jdW1lbnQgYnJpZWZseSBpbnRyb2R1Y2VzIHRoZSBleGlz
dGluZyBtZWNoYW5pc21zIGNvdWxkIGJlDQogICB1dGlsaXplZCBieSBJUHY2IHNpdGUgcmVudW1i
ZXJpbmcgYW5kIGVudmlzaW9ucyB0aGUgZWZmb3J0IGNvdWxkIGJlDQogICBkb25lIHVuZGVyIHRo
ZSA2cmVudW0gd29ya2luZyBncm91cC4gVGhpcyBkb2N1bWVudCB0cmllcyB0byBjb3ZlciB0aGUN
CiAgIG1vc3QgZXhwbGljaXQgaXNzdWVzIGFuZCByZXF1aXJlbWVudHMgb2YgSVB2NiByZW51bWJl
cmluZy4gVGhyb3VnaA0KICAgdGhlIGdhcCBhbmFseXNpcywgdGhlIGRvY3VtZW50IHByb3ZpZGVz
IGEgYmFzaXMgZm9yIGZ1dHVyZSB3b3JrIHRvDQogICBpZGVudGlmeSBhbmQgZGV2ZWxvcCBzb2x1
dGlvbnMgb3IgdG8gc3RpbXVsYXRlIHN1Y2ggZGV2ZWxvcG1lbnQgYXMNCiAgIGFwcHJvcHJpYXRl
LiBUaGUgZ2FwIGFuYWx5c2lzIGlzIHByZXNlbnRlZCBmb2xsb3dpbmcgYSByZW51bWJlcmluZw0K
ICAgZXZlbnQgcHJvY2VkdXJlIGNsdWUuDQoNCg0KDQogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
DQoNCg0KVGhlIElFVEYgU2VjcmV0YXJpYXQNCg==

From leo.liubing@huawei.com  Mon Jul 11 19:00:59 2011
Return-Path: <leo.liubing@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC37011E8407 for <renum@ietfa.amsl.com>; Mon, 11 Jul 2011 19:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.118
X-Spam-Level: 
X-Spam-Status: No, score=-3.118 tagged_above=-999 required=5 tests=[AWL=1.181,  BAYES_00=-2.599, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDawdhp8lwAz for <renum@ietfa.amsl.com>; Mon, 11 Jul 2011 19:00:59 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 9597211E83FE for <renum@ietf.org>; Mon, 11 Jul 2011 19:00:58 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LO7005FT6WW9O@szxga04-in.huawei.com> for renum@ietf.org; Tue, 12 Jul 2011 10:00:32 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LO7006ZL6WWC7@szxga04-in.huawei.com> for renum@ietf.org; Tue, 12 Jul 2011 10:00:32 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml203-edg.china.huawei.com) ([172.24.2.119])	by szxrg01-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACO79410; Tue, 12 Jul 2011 10:00:31 +0800 (CST)
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 12 Jul 2011 10:00:27 +0800
Received: from SZXEML509-MBX.china.huawei.com ([169.254.1.68]) by szxeml405-hub.china.huawei.com ([169.254.211.222]) with mapi id 14.01.0270.001; Tue, 12 Jul 2011 10:00:29 +0800
Date: Tue, 12 Jul 2011 02:00:28 +0000
From: "Leo Liu(bing)" <leo.liubing@huawei.com>
X-Originating-IP: [10.110.98.62]
To: "renum@ietf.org" <renum@ietf.org>
Message-id: <8AE0F17B87264D4CAC7DE0AA6C406F4502193737@szxeml509-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: zh-CN, en-US
Thread-topic: New Version of draft-liu-6renum-gap-analysis-01.txt
Thread-index: AQHMQDd4EC95Nh8hG0SrC9M4Xhej8w==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
Subject: [renum] New Version of draft-liu-6renum-gap-analysis-01.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2011 02:00:59 -0000

Hi, all

The gap analysis has been updated to 01 version:
http://tools.ietf.org/html/draft-liu-6renum-gap-analysis-01

main changes:
1. In section 5 "Address Configuration gap analysis", section 5.1 "host address configuration" was reorganized, some gap analysis was added
2. In section 6 "Address relevant entries update gap analysis", inserted a new section 6.2 "In-host server address update", to introduce the update of server addresses stored in hosts. 
3. reorganized section 7 "Renumbering event management" into 3 sub-clauses as "Renumbering notification", "Synchronization Management", and "Renumbering monitoring"

Your comments are expected eagerly.

B.R.
Bing

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, July 11, 2011 9:00 PM
To: Leo Liu(bing)
Cc: Leo Liu(bing); Jiangsheng
Subject: New Version Notification for draft-liu-6renum-gap-analysis-01.txt

A new version of I-D, draft-liu-6renum-gap-analysis-01.txt has been successfully submitted by Bing Liu and posted to the IETF repository.

Filename:	 draft-liu-6renum-gap-analysis
Revision:	 01
Title:		 IPv6 Site Renumbering Gap Analysis
Creation date:	 2011-07-11
WG ID:		 Individual Submission
Number of pages: 18

Abstract:
   This document briefly introduces the existing mechanisms could be
   utilized by IPv6 site renumbering and envisions the effort could be
   done. This document tries to cover the most explicit issues and
   requirements of IPv6 renumbering. Through the gap analysis, the
   document provides a basis for future work to identify and develop
   solutions or to stimulate such development as appropriate. The gap
   analysis is presented following a renumbering event procedure clue.



                                                                                  


The IETF Secretariat

From tjc@ecs.soton.ac.uk  Wed Jul 13 08:30:08 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 105CA11E80F8 for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 08:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gIDlnm2oPfNB for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 08:30:04 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 962CC11E811E for <renum@ietf.org>; Wed, 13 Jul 2011 08:30:03 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6DFU0rA028626 for <renum@ietf.org>; Wed, 13 Jul 2011 16:30:00 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p6DFU0rA028626
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1310571000; bh=XdVgtZkxZeIx1G3AWQHu4qIr1dU=; h=Subject:From:Date:To:Mime-Version:References; b=HwkrmMxnUeXAUEUZyU6h5b2VZHGcJvfmM3gx/jBpAGRr1hUGjaWIngFsrruGH2TH+ U88DbrnIIixDj4b8nguDL13Zoa7nfXv05k2ygRslIXjnjP5aO03SB6gwA77qpL12Wk h3BqeO/NZgkNaSK2hHgx+hfq4tRXdN4rf6AYFZwo=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n6CGU003661256115M ret-id none; Wed, 13 Jul 2011 16:30:00 +0100
Received: from [IPv6:2001:630:d0:f111:216:cbff:fe8b:752e] ([IPv6:2001:630:d0:f111:216:cbff:fe8b:752e]) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6DFTtwa006144 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Wed, 13 Jul 2011 16:29:55 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
Message-ID: <EMEW3|ac351c5a85f720bfc99745f81f8d9cb0n6CGU003tjc|ecs.soton.ac.uk|455CEC4F-6425-4D4D-A7D9-2B7E75C48980@ecs.soton.ac.uk>
Date: Wed, 13 Jul 2011 16:29:55 +0100
To: renum@ietf.org
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n6CGU0036612561100; tid=n6CGU003661256115M; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
References: <455CEC4F-6425-4D4D-A7D9-2B7E75C48980@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p6DFU0rA028626
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: [renum] IETF81 agenda uploaded
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 15:30:08 -0000

The agenda for Quebec is now posted at

http://www.ietf.org/proceedings/81/agenda/6renum.html

If there are any alterations or anyone who wishes to present something =
(brief) that's in line with our two chartered documents, please let me =
know.

We will keep presentation time to a minimum to allow for discussion.

Tim=

From tjc@ecs.soton.ac.uk  Wed Jul 13 08:55:00 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 396AC21F8906 for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 08:55:00 -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=-1.150, BAYES_00=-2.599, MANGLED_TOOL=2.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDsMcy55X+HE for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 08:54:56 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id B9D3911E8146 for <renum@ietf.org>; Wed, 13 Jul 2011 08:54:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6DFslYg003162 for <renum@ietf.org>; Wed, 13 Jul 2011 16:54:47 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p6DFslYg003162
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1310572487; bh=txWTe1JMKS4rFm0zX/ZsKF8cG7I=; h=References:In-Reply-To:Mime-Version:From:Subject:Date:To; b=Gx740Zju1CFj/wxFfCO5HuCMjQ/QeKscMBZxRf8aUA4fvn1Jl3Y4TAcLhefWOiXFV gV7SArBIyltDDuFer+j/qOXC/Q9GhBKo2EeBlyW57HX3lA3prTeyOOO7zNy1//l1Ls eaMwdOjgTmF7jxP4ChWbIYn7l3jLKqfHFa3pMis8=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n6CGsl0366125801HF ret-id none; Wed, 13 Jul 2011 16:54:47 +0100
Received: from [IPv6:2001:630:d0:f111:216:cbff:fe8b:752e] ([IPv6:2001:630:d0:f111:216:cbff:fe8b:752e]) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6DFsiCk012549 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Wed, 13 Jul 2011 16:54:45 +0100
References: <8AE0F17B87264D4CAC7DE0AA6C406F4502193737@szxeml509-mbx.china.huawei.com> <394FD5BE-3CB3-4E36-AE9C-5BD746AC90D7@ecs.soton.ac.uk>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F4502193737@szxeml509-mbx.china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
Message-ID: <EMEW3|9b671b4665ef4701830605afe0cf8c26n6CGsl03tjc|ecs.soton.ac.uk|394FD5BE-3CB3-4E36-AE9C-5BD746AC90D7@ecs.soton.ac.uk>
Content-Transfer-Encoding: quoted-printable
From: Tim Chown <tjc@ecs.soton.ac.uk>
Date: Wed, 13 Jul 2011 16:54:44 +0100
To: renum@ietf.org
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n6CGsl036612580100; tid=n6CGsl0366125801HF; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p6DFslYg003162
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [renum] New Version of draft-liu-6renum-gap-analysis-01.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 15:55:00 -0000

Many thanks for this update Bing,

I would encourage comments and questions prior to the session at Quebec. =
  Any open issues can then be discussed there.

In general, are the two documents heading in the right direction for WG =
adoption?  If not, why not?

Tim

On 12 Jul 2011, at 03:00, Leo Liu(bing) wrote:

> Hi, all
>=20
> The gap analysis has been updated to 01 version:
> http://tools.ietf.org/html/draft-liu-6renum-gap-analysis-01
>=20
> main changes:
> 1. In section 5 "Address Configuration gap analysis", section 5.1 =
"host address configuration" was reorganized, some gap analysis was =
added
> 2. In section 6 "Address relevant entries update gap analysis", =
inserted a new section 6.2 "In-host server address update", to introduce =
the update of server addresses stored in hosts.=20
> 3. reorganized section 7 "Renumbering event management" into 3 =
sub-clauses as "Renumbering notification", "Synchronization Management", =
and "Renumbering monitoring"
>=20
> Your comments are expected eagerly.
>=20
> B.R.
> Bing
>=20
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
> Sent: Monday, July 11, 2011 9:00 PM
> To: Leo Liu(bing)
> Cc: Leo Liu(bing); Jiangsheng
> Subject: New Version Notification for =
draft-liu-6renum-gap-analysis-01.txt
>=20
> A new version of I-D, draft-liu-6renum-gap-analysis-01.txt has been =
successfully submitted by Bing Liu and posted to the IETF repository.
>=20
> Filename:	 draft-liu-6renum-gap-analysis
> Revision:	 01
> Title:		 IPv6 Site Renumbering Gap Analysis
> Creation date:	 2011-07-11
> WG ID:		 Individual Submission
> Number of pages: 18
>=20
> Abstract:
>   This document briefly introduces the existing mechanisms could be
>   utilized by IPv6 site renumbering and envisions the effort could be
>   done. This document tries to cover the most explicit issues and
>   requirements of IPv6 renumbering. Through the gap analysis, the
>   document provides a basis for future work to identify and develop
>   solutions or to stimulate such development as appropriate. The gap
>   analysis is presented following a renumbering event procedure clue.
>=20
>=20
>=20
>=20
>=20
>=20
> The IETF Secretariat
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum


From Fred.L.Templin@boeing.com  Wed Jul 13 11:03:26 2011
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3778221F8BD8 for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 11:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.239
X-Spam-Level: 
X-Spam-Status: No, score=-6.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9FeyI8dG5aA for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 11:03:25 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by ietfa.amsl.com (Postfix) with ESMTP id 9B80821F8BC8 for <renum@ietf.org>; Wed, 13 Jul 2011 11:03:22 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p6DI3FXN000092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 13 Jul 2011 11:03:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with SMTP id p6DI3FrO024357; Wed, 13 Jul 2011 11:03:15 -0700 (PDT)
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p6DI39XS023802 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 13 Jul 2011 11:03:10 -0700 (PDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Wed, 13 Jul 2011 11:03:09 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "renum@ietf.org" <renum@ietf.org>
Date: Wed, 13 Jul 2011 11:03:08 -0700
Thread-Topic: An observation on 'draft-jiang-6renum-enterprise-00.txt'
Thread-Index: AcxBdXERdFTyM40XSrSml9Cw9XU+jgAEEysw
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F0C3@XCH-NW-01V.nw.nos.boeing.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F4502193737@szxeml509-mbx.china.huawei.com> <394FD5BE-3CB3-4E36-AE9C-5BD746AC90D7@ecs.soton.ac.uk> <EMEW3|9b671b4665ef4701830605afe0cf8c26n6CGsl03tjc|ecs.soton.ac.uk|394FD5BE-3CB3-4E36-AE9C-5BD746AC90D7@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|9b671b4665ef4701830605afe0cf8c26n6CGsl03tjc|ecs.soton.ac.uk|394FD5BE-3CB3-4E36-AE9C-5BD746AC90D7@ecs.soton.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [renum] An observation on 'draft-jiang-6renum-enterprise-00.txt'
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 18:03:26 -0000

Authors,

In Section 1 of this document, we see:

  "This document focuses on IPv6 only, by leaving IPv4
   out of scope. Dual-stack network or IPv4/IPv6
   transition scenarios are out of scope, too."

Also, in Section 2:

  "The complicated IPv4/IPv6 co-existing scenarios are
   out of scope."

These statements seem to me to be dodging a very
important phase in the transition of existing IPv4
enterprise networks into IPv6 supporting enterprises.
Indeed, the document fails to cite the two v6ops
publications on Enterprise network IPv6 consideraitons,
namely "IPv6 Enterprise Network Scenarios" [RFC4057]
and "



From Fred.L.Templin@boeing.com  Wed Jul 13 11:14:17 2011
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDBA621F8BF4 for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 11:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.199
X-Spam-Level: 
X-Spam-Status: No, score=-6.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pPtcg0Uh2KgI for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 11:14:17 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by ietfa.amsl.com (Postfix) with ESMTP id 5B66621F8BED for <renum@ietf.org>; Wed, 13 Jul 2011 11:14:17 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p6DIDahN018300 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 13 Jul 2011 13:13:37 -0500 (CDT)
Received: from localhost (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with SMTP id p6DIDa90009296; Wed, 13 Jul 2011 11:13:36 -0700 (PDT)
Received: from XCH-NWHT-01.nw.nos.boeing.com (xch-nwht-01.nw.nos.boeing.com [130.247.70.222]) by slb-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p6DIDUcF009145 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 13 Jul 2011 11:13:30 -0700 (PDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-01.nw.nos.boeing.com ([130.247.70.222]) with mapi; Wed, 13 Jul 2011 11:13:29 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "renum@ietf.org" <renum@ietf.org>
Date: Wed, 13 Jul 2011 11:13:28 -0700
Thread-Topic: An observation on 'draft-jiang-6renum-enterprise-00.txt'
Thread-Index: AcxBdXERdFTyM40XSrSml9Cw9XU+jgAEEyswAABfxxA=
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F0D7@XCH-NW-01V.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [renum] An observation on 'draft-jiang-6renum-enterprise-00.txt'
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 18:14:18 -0000

=20
[[ Re-sending - previous attempt was truncated ]]

Authors,

In Section 1 of this document, we see:

  "This document focuses on IPv6 only, by leaving IPv4
   out of scope. Dual-stack network or IPv4/IPv6
   transition scenarios are out of scope, too."

This statement seem to me to be dodging a very
important phase in the transition of existing IPv4
enterprise networks into IPv6 supporting enterprises.
Indeed, the document fails to cite the two v6ops
publications on Enterprise network IPv6 considerations,
namely "IPv6 Enterprise Network Scenarios" [RFC4057]
and "IPv6 Enterprise Network Analysis - IP Layer 3
Focus" [RFC4852]". These documents clearly show a
need to account for a mixed IPv4/IPv6 environment
for some time to come.

Also, in Section 2 of your document:

  "The complicated IPv4/IPv6 co-existing scenarios are
   out of scope."

In the case of ISATAP [RFC5214] at least, I disagree
with the characterization of "complicated". Indeed,
using ISATAP, an entire enterprise network can be
automatically renumbered by touching only the site
bordering ISATAP routers when their ISP delegated
prefixes from the ISP change. As far as I can tell,
such would represent possibly the simplest of all
renumbering scenarios. Note also that operational
guidance for IPv6 deployment in IPv4 sites using
is now beind documented in 'draft-templin-v6ops-isops',
which could also be cited by your document.

Please check these works, and consider citing the
appropriate documents. Please also note that ISATAP
provides a ready-made simple solution for enterprise
network renumbering, which could also be mentioned
in your document.

Thanks - Fred
fred.l.templin@boeing.com


From brian.e.carpenter@gmail.com  Wed Jul 13 14:39:10 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49CB111E8120 for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 14:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.339
X-Spam-Level: 
X-Spam-Status: No, score=-103.339 tagged_above=-999 required=5 tests=[AWL=-0.340, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BE42nkTvA2Z7 for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 14:39:09 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id A751011E8102 for <renum@ietf.org>; Wed, 13 Jul 2011 14:39:09 -0700 (PDT)
Received: by qyk9 with SMTP id 9so621104qyk.10 for <renum@ietf.org>; Wed, 13 Jul 2011 14:39:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Rg1hBugSmcVSOQx3AJ2Rdzc0JUbu1WD9t2iHGK2AMDI=; b=S/boNsRjgQMmuZyLFHmt7TdRtku+VbdqRiAFA3/RF9PnlBKwyutHCY4mxG/0g+2qtN QyiY1g7hhOJ03MydL99RzipnJaJPIgMjax3mJRJwNF00YAPsAzySEQndmrF69sWjiFxO 3SbZp7RxBcPdaZhwZZ5/BnpSEve76aPXpNZdQ=
Received: by 10.224.71.12 with SMTP id f12mr1441621qaj.306.1310593148926; Wed, 13 Jul 2011 14:39:08 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id r33sm12230235qcs.18.2011.07.13.14.39.06 (version=SSLv3 cipher=OTHER); Wed, 13 Jul 2011 14:39:08 -0700 (PDT)
Message-ID: <4E1E1076.6060703@gmail.com>
Date: Thu, 14 Jul 2011 09:39:02 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F0D7@XCH-NW-01V.nw.nos.boeing.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F0D7@XCH-NW-01V.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] An observation on 'draft-jiang-6renum-enterprise-00.txt'
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 21:39:10 -0000

Fred,

It's mentioned in RFC 5887 that one trigger for IPv6 renumbering could
be migrating from a transitional IPv6 solution to true native IPv6.
In that sense, coexistence mechanisms are (IMHO) in the scope of the
6renum charter, but I think it's limited to that; IPv4 is out of scope
unless "analysis leads to conclusions that are also applicable to IPv4."
Of course, this applies to all coexistence mechanisms, not just ISATAP.

I agree that mentioning renumbering from a coexistence solution to
a native solution is reasonable, as it may lead to specific items in
the gap analysis.

Regards
   Brian

On 2011-07-14 06:13, Templin, Fred L wrote:
>  
> [[ Re-sending - previous attempt was truncated ]]
> 
> Authors,
> 
> In Section 1 of this document, we see:
> 
>   "This document focuses on IPv6 only, by leaving IPv4
>    out of scope. Dual-stack network or IPv4/IPv6
>    transition scenarios are out of scope, too."
> 
> This statement seem to me to be dodging a very
> important phase in the transition of existing IPv4
> enterprise networks into IPv6 supporting enterprises.
> Indeed, the document fails to cite the two v6ops
> publications on Enterprise network IPv6 considerations,
> namely "IPv6 Enterprise Network Scenarios" [RFC4057]
> and "IPv6 Enterprise Network Analysis - IP Layer 3
> Focus" [RFC4852]". These documents clearly show a
> need to account for a mixed IPv4/IPv6 environment
> for some time to come.
> 
> Also, in Section 2 of your document:
> 
>   "The complicated IPv4/IPv6 co-existing scenarios are
>    out of scope."
> 
> In the case of ISATAP [RFC5214] at least, I disagree
> with the characterization of "complicated". Indeed,
> using ISATAP, an entire enterprise network can be
> automatically renumbered by touching only the site
> bordering ISATAP routers when their ISP delegated
> prefixes from the ISP change. As far as I can tell,
> such would represent possibly the simplest of all
> renumbering scenarios. Note also that operational
> guidance for IPv6 deployment in IPv4 sites using
> is now beind documented in 'draft-templin-v6ops-isops',
> which could also be cited by your document.
> 
> Please check these works, and consider citing the
> appropriate documents. Please also note that ISATAP
> provides a ready-made simple solution for enterprise
> network renumbering, which could also be mentioned
> in your document.
> 
> Thanks - Fred
> fred.l.templin@boeing.com
> 
> 

From Fred.L.Templin@boeing.com  Wed Jul 13 15:41:26 2011
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5192011E8075 for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 15:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.17
X-Spam-Level: 
X-Spam-Status: No, score=-6.17 tagged_above=-999 required=5 tests=[AWL=-0.171,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fLrGoIUlWBRd for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 15:41:25 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by ietfa.amsl.com (Postfix) with ESMTP id ACB0E21F8B4F for <renum@ietf.org>; Wed, 13 Jul 2011 15:41:25 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p6DMfItX029368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 13 Jul 2011 15:41:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with SMTP id p6DMfHIA025350; Wed, 13 Jul 2011 15:41:17 -0700 (PDT)
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by slb-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p6DMfDqI025225 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 13 Jul 2011 15:41:13 -0700 (PDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Wed, 13 Jul 2011 15:41:13 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Wed, 13 Jul 2011 15:41:12 -0700
Thread-Topic: An observation on 'draft-jiang-6renum-enterprise-00.txt'
Thread-Index: AcxBpU1cPoo8Ul5VRXy/tLJrngApYAAB50xQ
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F268@XCH-NW-01V.nw.nos.boeing.com>
References: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F0D7@XCH-NW-01V.nw.nos.boeing.com> <4E1E1076.6060703@gmail.com>
In-Reply-To: <4E1E1076.6060703@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] An observation on 'draft-jiang-6renum-enterprise-00.txt'
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 22:41:26 -0000

Hi Brian,=20

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]=20
> Sent: Wednesday, July 13, 2011 2:39 PM
> To: Templin, Fred L
> Cc: renum@ietf.org; jiangsheng@huawei.com; leo.liubing@huawei.com
> Subject: Re: An observation on 'draft-jiang-6renum-enterprise-00.txt'
>=20
> Fred,
>=20
> It's mentioned in RFC 5887 that one trigger for IPv6 renumbering could
> be migrating from a transitional IPv6 solution to true native IPv6.

OK. But, renumbering could also include changing from an
IPv6 prefix 'A' assigned to a coexistence mechanism to a
different IPv6 prefix 'B' assigned to that same coexistence
mechanism (i.e., it does not need to entail a migration
from coexistence to native).

> In that sense, coexistence mechanisms are (IMHO) in the scope of the
> 6renum charter, but I think it's limited to that; IPv4 is out of scope
> unless "analysis leads to conclusions that are also=20
> applicable to IPv4."

If by that, you mean that IPv4 renumbering is out of
scope unless ..., then I am fine with that. My concern
is for IPv6 renumbering.

> Of course, this applies to all coexistence mechanisms, not=20
> just ISATAP.

I mention ISATAP only within the context of enterprise
networks, which is the domain of analysis of the document
in question.
=20
> I agree that mentioning renumbering from a coexistence solution to
> a native solution is reasonable, as it may lead to specific items in
> the gap analysis.

Should also include changing from IPv6 prefix 'A' to
IPv6 prefix 'B' while not changing from coexistence
to native.

Thanks - Fred
fred.l.templin@boeing.com

> Regards
>    Brian
>=20
> On 2011-07-14 06:13, Templin, Fred L wrote:
> > =20
> > [[ Re-sending - previous attempt was truncated ]]
> >=20
> > Authors,
> >=20
> > In Section 1 of this document, we see:
> >=20
> >   "This document focuses on IPv6 only, by leaving IPv4
> >    out of scope. Dual-stack network or IPv4/IPv6
> >    transition scenarios are out of scope, too."
> >=20
> > This statement seem to me to be dodging a very
> > important phase in the transition of existing IPv4
> > enterprise networks into IPv6 supporting enterprises.
> > Indeed, the document fails to cite the two v6ops
> > publications on Enterprise network IPv6 considerations,
> > namely "IPv6 Enterprise Network Scenarios" [RFC4057]
> > and "IPv6 Enterprise Network Analysis - IP Layer 3
> > Focus" [RFC4852]". These documents clearly show a
> > need to account for a mixed IPv4/IPv6 environment
> > for some time to come.
> >=20
> > Also, in Section 2 of your document:
> >=20
> >   "The complicated IPv4/IPv6 co-existing scenarios are
> >    out of scope."
> >=20
> > In the case of ISATAP [RFC5214] at least, I disagree
> > with the characterization of "complicated". Indeed,
> > using ISATAP, an entire enterprise network can be
> > automatically renumbered by touching only the site
> > bordering ISATAP routers when their ISP delegated
> > prefixes from the ISP change. As far as I can tell,
> > such would represent possibly the simplest of all
> > renumbering scenarios. Note also that operational
> > guidance for IPv6 deployment in IPv4 sites using
> > is now beind documented in 'draft-templin-v6ops-isops',
> > which could also be cited by your document.
> >=20
> > Please check these works, and consider citing the
> > appropriate documents. Please also note that ISATAP
> > provides a ready-made simple solution for enterprise
> > network renumbering, which could also be mentioned
> > in your document.
> >=20
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >=20
> >=20
> =


From jiangsheng@huawei.com  Wed Jul 13 19:23:06 2011
Return-Path: <jiangsheng@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5FC311E80B4 for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 19:23:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.41
X-Spam-Level: 
X-Spam-Status: No, score=-3.41 tagged_above=-999 required=5 tests=[AWL=-1.411,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bMVIPQ6ct9EB for <renum@ietfa.amsl.com>; Wed, 13 Jul 2011 19:23:06 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id CEC1611E8089 for <renum@ietf.org>; Wed, 13 Jul 2011 19:23:05 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOA00EFJX7LGX@szxga05-in.huawei.com> for renum@ietf.org; Thu, 14 Jul 2011 10:21:21 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOA00GE0X7C4V@szxga05-in.huawei.com> for renum@ietf.org; Thu, 14 Jul 2011 10:21:21 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml203-edg.china.huawei.com) ([172.24.2.119])	by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACE89740; Thu, 14 Jul 2011 10:21:19 +0800 (CST)
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 14 Jul 2011 10:21:14 +0800
Received: from SZXEML506-MBX.china.huawei.com ([169.254.4.221]) by szxeml412-hub.china.huawei.com ([169.254.226.192]) with mapi id 14.01.0270.001; Thu, 14 Jul 2011 10:21:17 +0800
Date: Thu, 14 Jul 2011 02:21:14 +0000
From: Jiangsheng <jiangsheng@huawei.com>
In-reply-to: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F268@XCH-NW-01V.nw.nos.boeing.com>
X-Originating-IP: [10.110.98.101]
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-id: <5D36713D8A4E7348A7E10DF7437A4B920121587C@SZXEML506-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: en-GB, zh-CN, en-US
Thread-topic: An observation on 'draft-jiang-6renum-enterprise-00.txt'
Thread-index: AcxBdXERdFTyM40XSrSml9Cw9XU+jgAEEyswAABfxxD//7X5AIAAEV8A//9AxoA=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <E1829B60731D1740BB7A0626B4FAF0A65C6B37F0D7@XCH-NW-01V.nw.nos.boeing.com> <4E1E1076.6060703@gmail.com> <E1829B60731D1740BB7A0626B4FAF0A65C6B37F268@XCH-NW-01V.nw.nos.boeing.com>
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] An observation on 'draft-jiang-6renum-enterprise-00.txt'
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2011 02:23:06 -0000

Hi, Templin,

So far, in this version of our drafts, we do not distinguish the different reasons of changing prefix. So, your mentioned "changing from an IPv6 prefix 'A' assigned to a coexistence mechanism to a different IPv6 prefix 'B' assigned to that same coexistence mechanism" is already included. But we sort it in different dimension.

Regards,

Sheng

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> Sent: Thursday, July 14, 2011 6:41 AM
> To: Brian E Carpenter
> Cc: renum@ietf.org; Jiangsheng; Leo Liu(bing)
> Subject: RE: An observation on 'draft-jiang-6renum-enterprise-00.txt'
> 
> Hi Brian,
> 
> > -----Original Message-----
> > From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> > Sent: Wednesday, July 13, 2011 2:39 PM
> > To: Templin, Fred L
> > Cc: renum@ietf.org; jiangsheng@huawei.com; leo.liubing@huawei.com
> > Subject: Re: An observation on 'draft-jiang-6renum-enterprise-00.txt'
> >
> > Fred,
> >
> > It's mentioned in RFC 5887 that one trigger for IPv6 renumbering
> could
> > be migrating from a transitional IPv6 solution to true native IPv6.
> 
> OK. But, renumbering could also include changing from an
> IPv6 prefix 'A' assigned to a coexistence mechanism to a
> different IPv6 prefix 'B' assigned to that same coexistence
> mechanism (i.e., it does not need to entail a migration
> from coexistence to native).
> 
> > In that sense, coexistence mechanisms are (IMHO) in the scope of the
> > 6renum charter, but I think it's limited to that; IPv4 is out of
> scope
> > unless "analysis leads to conclusions that are also
> > applicable to IPv4."
> 
> If by that, you mean that IPv4 renumbering is out of
> scope unless ..., then I am fine with that. My concern
> is for IPv6 renumbering.
> 
> > Of course, this applies to all coexistence mechanisms, not
> > just ISATAP.
> 
> I mention ISATAP only within the context of enterprise
> networks, which is the domain of analysis of the document
> in question.
> 
> > I agree that mentioning renumbering from a coexistence solution to
> > a native solution is reasonable, as it may lead to specific items in
> > the gap analysis.
> 
> Should also include changing from IPv6 prefix 'A' to
> IPv6 prefix 'B' while not changing from coexistence
> to native.
> 
> Thanks - Fred
> fred.l.templin@boeing.com
> 
> > Regards
> >    Brian
> >
> > On 2011-07-14 06:13, Templin, Fred L wrote:
> > >
> > > [[ Re-sending - previous attempt was truncated ]]
> > >
> > > Authors,
> > >
> > > In Section 1 of this document, we see:
> > >
> > >   "This document focuses on IPv6 only, by leaving IPv4
> > >    out of scope. Dual-stack network or IPv4/IPv6
> > >    transition scenarios are out of scope, too."
> > >
> > > This statement seem to me to be dodging a very
> > > important phase in the transition of existing IPv4
> > > enterprise networks into IPv6 supporting enterprises.
> > > Indeed, the document fails to cite the two v6ops
> > > publications on Enterprise network IPv6 considerations,
> > > namely "IPv6 Enterprise Network Scenarios" [RFC4057]
> > > and "IPv6 Enterprise Network Analysis - IP Layer 3
> > > Focus" [RFC4852]". These documents clearly show a
> > > need to account for a mixed IPv4/IPv6 environment
> > > for some time to come.
> > >
> > > Also, in Section 2 of your document:
> > >
> > >   "The complicated IPv4/IPv6 co-existing scenarios are
> > >    out of scope."
> > >
> > > In the case of ISATAP [RFC5214] at least, I disagree
> > > with the characterization of "complicated". Indeed,
> > > using ISATAP, an entire enterprise network can be
> > > automatically renumbered by touching only the site
> > > bordering ISATAP routers when their ISP delegated
> > > prefixes from the ISP change. As far as I can tell,
> > > such would represent possibly the simplest of all
> > > renumbering scenarios. Note also that operational
> > > guidance for IPv6 deployment in IPv4 sites using
> > > is now beind documented in 'draft-templin-v6ops-isops',
> > > which could also be cited by your document.
> > >
> > > Please check these works, and consider citing the
> > > appropriate documents. Please also note that ISATAP
> > > provides a ready-made simple solution for enterprise
> > > network renumbering, which could also be mentioned
> > > in your document.
> > >
> > > Thanks - Fred
> > > fred.l.templin@boeing.com
> > >
> > >
> >

From tjc@ecs.soton.ac.uk  Mon Jul 18 04:18:39 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4C621F87D3 for <renum@ietfa.amsl.com>; Mon, 18 Jul 2011 04:18:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.024
X-Spam-Level: 
X-Spam-Status: No, score=-2.024 tagged_above=-999 required=5 tests=[AWL=0.575,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fxHZ0Hl+LWfk for <renum@ietfa.amsl.com>; Mon, 18 Jul 2011 04:18:39 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 80F9421F87BC for <renum@ietf.org>; Mon, 18 Jul 2011 04:18:38 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6IBIakw026773 for <renum@ietf.org>; Mon, 18 Jul 2011 12:18:36 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p6IBIakw026773
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1310987916; bh=K8w2dMkckN9J3wK0YU8zmyAI79Y=; h=From:Subject:Date:To:Mime-Version:References; b=aVmSKmt+9dIc8oFTZkrZ1jsGIoDLCTDLGRVqDESgsmh/43G0CZ9mf+kIrKZOf1ery gMS9Ffo1DXsvwfBhfoiWWodaNtBI/ETskzEaIlk81vdbh+Br7dbQ31EeBQxokZguAd iAlyG/c0OBlyhN4zNVzyILq6EbjgcXxx8N8bphLE=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n6HCIa0366150927pa ret-id none; Mon, 18 Jul 2011 12:18:36 +0100
Received: from [IPv6:2001:630:d0:f105:226:8ff:fee4:215b] ([IPv6:2001:630:d0:f105:226:8ff:fee4:215b]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6IBIU9o028148 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Mon, 18 Jul 2011 12:18:30 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 18 Jul 2011 12:18:30 +0100
Message-ID: <EMEW3|825df330a710f1f3c7354d0267c38683n6HCIa03tjc|ecs.soton.ac.uk|6E2FDD55-36C8-4924-9FAA-DD8CC00698F1@ecs.soton.ac.uk>
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n6HCIa036615092700; tid=n6HCIa0366150927pa; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
References: <6E2FDD55-36C8-4924-9FAA-DD8CC00698F1@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p6IBIakw026773
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: [renum] 6renum @ Quebec
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 11:18:39 -0000

Hi,

Wes George has kindly agreed to be the co-chair for 6renum, and we'll =
both be at Quebec.=20

We will need presentations to go online in advance of the meeting, so =
please mail those to me as soon as possible.  At present we are only =
expecting brief presentations from Sheng and Bing for their two drafts.  =
I would like to see the presentations asking questions of the WG so we =
can have a good discussion of the structure and contents of the two =
drafts.

Tim=

From wesley.george@twcable.com  Tue Jul 19 12:43:40 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBA745E8009 for <renum@ietfa.amsl.com>; Tue, 19 Jul 2011 12:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.145
X-Spam-Level: 
X-Spam-Status: No, score=-0.145 tagged_above=-999 required=5 tests=[AWL=0.317,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QQO2Nvgv58gf for <renum@ietfa.amsl.com>; Tue, 19 Jul 2011 12:43:38 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 294FC5E8004 for <renum@ietf.org>; Tue, 19 Jul 2011 12:43:38 -0700 (PDT)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,229,1309752000";  d="scan'208,217";a="251504064"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 19 Jul 2011 15:41:55 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.29]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Tue, 19 Jul 2011 15:43:37 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: "renum@ietf.org" <renum@ietf.org>
Date: Tue, 19 Jul 2011 15:43:36 -0400
Thread-Topic: comments on draft-jiang-6renum-enterprise-00
Thread-Index: AcxGTCbF/pU0ChUVQXa10ceAEcTaeQ==
Message-ID: <34E4F50CAFA10349A41E0756550084FB0B61DE3B@PRVPEXVS04.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_34E4F50CAFA10349A41E0756550084FB0B61DE3BPRVPEXVS04corpt_"
MIME-Version: 1.0
Subject: [renum] comments on draft-jiang-6renum-enterprise-00
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 19:43:41 -0000

--_000_34E4F50CAFA10349A41E0756550084FB0B61DE3BPRVPEXVS04corpt_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

2 - I don't think that it's necessary to assume that the *network* is IPv6-=
only, or to call dual-stack a complicated IPv4/IPv6 coexisting scenario. Yo=
ur current language makes this work irrelevant for 99.9% of the networks ou=
t there today (because they are either dual-stack or IPv4-only), which I th=
ink is probably not what we're going for when we say that IPv4 is not in sc=
ope.
I understand what you're trying to say with the comment "logical IPv6 plane=
 is independent from IPv4" but I think there's probably a clearer way to sa=
y it.
In other words, it's perfectly acceptable to have a dual-stack network and =
leverage these recommendations. You just simply need to say that IPv4 renum=
bering is not directly covered by this work and if a network is dual-stack,=
 IPv4 renumbering will have to be treated separately. Consider the fact tha=
t IPv4 and IPv6 allocations are often different, and while a topology chang=
e may trigger renumbering for both address-families, it is also possible th=
at a dual-stack network has other events that trigger a renumbering event o=
n just one of  multiple address-families. You could possibly identify which=
 of these techniques are IP version-agnostic and therefore applicable to IP=
v4, but note that the further gap analysis will not focus on improving IPv4=
 renumbering where it diverges from IPv6.

3- I would recommend reviewing and categorizing the renumbering reasons in =
RFC2071 specifically in a subsequent revision, rather than your current gen=
eralization that some are out of date/not suitable. For that matter, should=
 this document formally update RFC2071?

3.1/3.2 - Right now you have this somewhat limited to PA space -  you don't=
 actually say that, but your use cases/examples are all making that assumpt=
ion, and I doubt that was your intent.
Depending on how successful RIRs have been at doing sparse allocations, it'=
s quite possible that if a network needs to request a larger block (assumin=
g that they have a PI allocation) from their RIR, they may receive an entir=
ely new block rather than simply having their existing block's bit-length c=
hanged. This will trigger a renumber similar to a switch to a new ISP.

4.1 Address types -
Does this draft need to discuss the common reasons for using statically-def=
ined addresses, and perhaps identify some ways to reduce? You mention FQDN =
and DNS updates elsewhere in the document, but it may be useful to explicit=
ly note that here. Also, I know you have a  placeholder entry for that in 5=
.3 of the gap analysis draft, but I would think that it would start here wi=
th things that can be done (BCP) today...

while this isn't necessarily a current use of ULA, http://tools.ietf.org/ht=
ml/draft-herbst-v6ops-cpeenhancements-00 is specifying use of ULA in the Sm=
art Grid

5 - I don't understand what that first item "manual or script-driven proced=
ures..." means/refers to - can you attempt to clarify in the next revision?
Also, doesn't most of this section belong in the gap-analysis draft?

Thanks,

Wes George
speaking as individual contributor


________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

--_000_34E4F50CAFA10349A41E0756550084FB0B61DE3BPRVPEXVS04corpt_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">2 &#8211; I don&#8217;t think that it&#8217;s necess=
ary to assume that the *<b>network</b>* is IPv6-only, or to call dual-stack=
 a complicated IPv4/IPv6 coexisting scenario. Your current language makes t=
his work irrelevant for 99.9% of the networks out there
 today (because they are either dual-stack or IPv4-only), which I think is =
probably not what we&#8217;re going for when we say that IPv4 is not in sco=
pe.
<o:p></o:p></p>
<p class=3D"MsoNormal">I understand what you&#8217;re trying to say with th=
e comment &#8220;logical IPv6 plane is independent from IPv4&#8221; but I t=
hink there&#8217;s probably a clearer way to say it.
<o:p></o:p></p>
<p class=3D"MsoNormal">In other words, it&#8217;s perfectly acceptable to h=
ave a dual-stack network and leverage these recommendations. You just simpl=
y need to say that IPv4 renumbering is not directly covered by this work an=
d if a network is dual-stack, IPv4 renumbering
 will have to be treated separately. Consider the fact that IPv4 and IPv6 a=
llocations are often different, and while a topology change may trigger ren=
umbering for both address-families, it is also possible that a dual-stack n=
etwork has other events that trigger
 a renumbering event on just one of&nbsp; multiple address-families. You co=
uld possibly identify which of these techniques are IP version-agnostic and=
 therefore applicable to IPv4, but note that the further gap analysis will =
not focus on improving IPv4 renumbering
 where it diverges from IPv6. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">3- I would recommend reviewing and categorizing the =
renumbering reasons in RFC2071 specifically in a subsequent revision, rathe=
r than your current generalization that some are out of date/not suitable. =
For that matter, should this document
 formally update RFC2071?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">3.1/3.2 &#8211; Right now you have this somewhat lim=
ited to PA space -&nbsp; you don&#8217;t actually say that, but your use ca=
ses/examples are all making that assumption, and I doubt that was your inte=
nt.<o:p></o:p></p>
<p class=3D"MsoNormal">Depending on how successful RIRs have been at doing =
sparse allocations, it&#8217;s quite possible that if a network needs to re=
quest a larger block (assuming that they have a PI allocation) from their R=
IR, they may receive an entirely new block
 rather than simply having their existing block&#8217;s bit-length changed.=
 This will trigger a renumber similar to a switch to a new ISP.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">4.1 Address types &#8211; <o:p></o:p></p>
<p class=3D"MsoNormal">Does this draft need to discuss the common reasons f=
or using statically-defined addresses, and perhaps identify some ways to re=
duce? You mention FQDN and DNS updates elsewhere in the document, but it ma=
y be useful to explicitly note that
 here. Also, I know you have a&nbsp; placeholder entry for that in 5.3 of t=
he gap analysis draft, but I would think that it would start here with thin=
gs that can be done (BCP) today&#8230;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">while this isn&#8217;t necessarily a current use of =
ULA, <a href=3D"http://tools.ietf.org/html/draft-herbst-v6ops-cpeenhancemen=
ts-00">
http://tools.ietf.org/html/draft-herbst-v6ops-cpeenhancements-00</a> is spe=
cifying use of ULA in the Smart Grid<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">5 &#8211; I don&#8217;t understand what that first i=
tem &#8220;manual or script-driven procedures&#8230;&#8221; means/refers to=
 &#8211; can you attempt to clarify in the next revision?<o:p></o:p></p>
<p class=3D"MsoNormal">Also, doesn&#8217;t most of this section belong in t=
he gap-analysis draft?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Wes George<o:p></o:p></p>
<p class=3D"MsoNormal">speaking as individual contributor<span style=3D"col=
or:#7F7F7F"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>

--_000_34E4F50CAFA10349A41E0756550084FB0B61DE3BPRVPEXVS04corpt_--

From wesley.george@twcable.com  Tue Jul 19 12:52:06 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A8E5E800A for <renum@ietfa.amsl.com>; Tue, 19 Jul 2011 12:52:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.167
X-Spam-Level: 
X-Spam-Status: No, score=-0.167 tagged_above=-999 required=5 tests=[AWL=0.295,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sGi8nxxXCTrg for <renum@ietfa.amsl.com>; Tue, 19 Jul 2011 12:52:04 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 9CAC221F8564 for <renum@ietf.org>; Tue, 19 Jul 2011 12:52:03 -0700 (PDT)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,230,1309752000";  d="scan'208,217";a="237360857"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 19 Jul 2011 15:50:14 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.29]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Tue, 19 Jul 2011 15:52:00 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: "renum@ietf.org" <renum@ietf.org>
Date: Tue, 19 Jul 2011 15:52:00 -0400
Thread-Topic: scoping question - how to define Enterprise in the context of 6renum?
Thread-Index: AcxGTVKvr00AFcI7ThS19/pWOhg7bQ==
Message-ID: <34E4F50CAFA10349A41E0756550084FB0B61DE55@PRVPEXVS04.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_34E4F50CAFA10349A41E0756550084FB0B61DE55PRVPEXVS04corpt_"
MIME-Version: 1.0
Subject: [renum] scoping question - how to define Enterprise in the context of 6renum?
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2011 19:52:06 -0000

--_000_34E4F50CAFA10349A41E0756550084FB0B61DE55PRVPEXVS04corpt_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

In both the charter and in the enterprise draft, we make a point to specify=
 Enterprise renumbering as being in scope but ISP and SOHO/MANET out of sco=
pe. Right now, neither the drafts nor the charter does a particularly good =
job defining what is considered Enterprise and therefore in-scope, and diff=
erentiating how and why the renumbering work we're undertaking is applicabl=
e there while it is not in the other cases.

For example, what about renumbering enterprise networking infrastructure (a=
s compared to end hosts)? I would think that this is somewhat of a small-sc=
ale version of an ISP network renumber (which was previously identified as =
out of scope), but it is quite possible that all or part of an enterprise's=
 internal network infra might be subject to a renumbering event (depending =
on how they numbered things like routers and WAN/LAN links). If this is in =
scope, how do we make the distinction between SP renumbering and Enterprise=
 renumbering? Is it just scale/amount of renumbering? If it's out of scope,=
 what's our rationale?

I've been on the list mostly since the BOF days, but I don't remember there=
 being a lot of discussion on this specific scoping question, so I'd like s=
ome background, either from the draft charter authors or otherwise. The onl=
y thing that I could see was some comments on the draft charter from Scott =
Brim specifically recommending that we remove enterprise/soho/manet in favo=
r of something like managed or unmanaged.

I think there are probably a couple of characterization points - one is sca=
le, the other is management/administrative domain (typically enterprises ar=
e more centrally managed), but I think there may be more that aren't occurr=
ing to me at the moment, and I'd like to get some discussion going on how w=
e make this clearer so that we can say focused on the right scope (or redef=
ine it if it's currently too narrow).  I think it's better to get some clar=
ity on this now before we get too far along on the drafts and have to revis=
it them later.

Thanks,

Wes George
Speaking as chair


________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

--_000_34E4F50CAFA10349A41E0756550084FB0B61DE55PRVPEXVS04corpt_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">In both the charter and in the enterprise draft, we =
make a point to specify Enterprise renumbering as being in scope but ISP an=
d SOHO/MANET out of scope. Right now, neither the drafts nor the charter do=
es a particularly good job defining
 what is considered Enterprise and therefore in-scope, and differentiating =
how and why the renumbering work we&#8217;re undertaking is applicable ther=
e while it is not in the other cases.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For example, what about renumbering enterprise netwo=
rking infrastructure (as compared to end hosts)? I would think that this is=
 somewhat of a small-scale version of an ISP network renumber (which was pr=
eviously identified as out of scope),
 but it is quite possible that all or part of an enterprise&#8217;s interna=
l network infra might be subject to a renumbering event (depending on how t=
hey numbered things like routers and WAN/LAN links). If this is in scope, h=
ow do we make the distinction between
 SP renumbering and Enterprise renumbering? Is it just scale/amount of renu=
mbering? If it&#8217;s out of scope, what&#8217;s our rationale?
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I&#8217;ve been on the list mostly since the BOF day=
s, but I don&#8217;t remember there being a lot of discussion on this speci=
fic scoping question, so I&#8217;d like some background, either from the dr=
aft charter authors or otherwise. The only thing that
 I could see was some comments on the draft charter from Scott Brim specifi=
cally recommending that we remove enterprise/soho/manet in favor of somethi=
ng like managed or unmanaged.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I think there are probably a couple of characterizat=
ion points &#8211; one is scale, the other is management/administrative dom=
ain (typically enterprises are more centrally managed), but I think there m=
ay be more that aren&#8217;t occurring to me at
 the moment, and I&#8217;d like to get some discussion going on how we make=
 this clearer so that we can say focused on the right scope (or redefine it=
 if it&#8217;s currently too narrow).&nbsp; I think it&#8217;s better to ge=
t some clarity on this now before we get too far along
 on the drafts and have to revisit them later. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Wes George<o:p></o:p></p>
<p class=3D"MsoNormal">Speaking as chair<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>

--_000_34E4F50CAFA10349A41E0756550084FB0B61DE55PRVPEXVS04corpt_--

From jiangsheng@huawei.com  Wed Jul 20 00:01:56 2011
Return-Path: <jiangsheng@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1762D21F88E5 for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 00:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.48
X-Spam-Level: 
X-Spam-Status: No, score=-3.48 tagged_above=-999 required=5 tests=[AWL=-0.882,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GD20vjG3Qb1K for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 00:01:52 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 2379021F88A6 for <renum@ietf.org>; Wed, 20 Jul 2011 00:01:52 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOM00HVUDQDMY@szxga05-in.huawei.com> for renum@ietf.org; Wed, 20 Jul 2011 14:51:50 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOM00G4SDQCGQ@szxga05-in.huawei.com> for renum@ietf.org; Wed, 20 Jul 2011 14:51:49 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml205-edg.china.huawei.com) ([172.24.2.119])	by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACJ94831; Wed, 20 Jul 2011 14:51:48 +0800 (CST)
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 20 Jul 2011 14:51:45 +0800
Received: from SZXEML506-MBX.china.huawei.com ([169.254.4.221]) by szxeml405-hub.china.huawei.com ([169.254.211.222]) with mapi id 14.01.0270.001; Wed, 20 Jul 2011 14:51:32 +0800
Date: Wed, 20 Jul 2011 06:51:31 +0000
From: Jiangsheng <jiangsheng@huawei.com>
In-reply-to: <34E4F50CAFA10349A41E0756550084FB0B61DE3B@PRVPEXVS04.corp.twcable.com>
X-Originating-IP: [10.110.98.101]
To: "George, Wesley" <wesley.george@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Message-id: <5D36713D8A4E7348A7E10DF7437A4B92012182EA@SZXEML506-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_RQGdFJY0uZVblFgg59XN9g)"
Content-language: zh-CN
Accept-Language: en-GB, zh-CN, en-US
Thread-topic: comments on draft-jiang-6renum-enterprise-00
Thread-index: AcxGTCbF/pU0ChUVQXa10ceAEcTaeQAPYnLw
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <34E4F50CAFA10349A41E0756550084FB0B61DE3B@PRVPEXVS04.corp.twcable.com>
Subject: Re: [renum] comments on draft-jiang-6renum-enterprise-00
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 07:01:56 -0000

--Boundary_(ID_RQGdFJY0uZVblFgg59XN9g)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi, George,

Thanks for your valuable comments. See my reply in lines.

Sheng

From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of George, Wesley
Sent: Wednesday, July 20, 2011 3:44 AM
To: renum@ietf.org
Subject: [renum] comments on draft-jiang-6renum-enterprise-00

2 - I don't think that it's necessary to assume that the *network* is IPv6-only, or to call dual-stack a complicated IPv4/IPv6 coexisting scenario. Your current language makes this work irrelevant for 99.9% of the networks out there today (because they are either dual-stack or IPv4-only), which I think is probably not what we're going for when we say that IPv4 is not in scope.

<Sheng> My understanding is that focusing on IPv6 is the scope of this WG. It was decided during BoF and WG creating period. Dual-stack network is included, I think, but we only focus on IPv6 part of it.

I understand what you're trying to say with the comment "logical IPv6 plane is independent from IPv4" but I think there's probably a clearer way to say it.

<Sheng> It looks like the word "coexisting scenario" is misleading. We actually means IPv4/IPv6 transition scenarios. Dual-stack network is in the scope. Will make clearer description in next version. :)

In other words, it's perfectly acceptable to have a dual-stack network and leverage these recommendations. You just simply need to say that IPv4 renumbering is not directly covered by this work and if a network is dual-stack, IPv4 renumbering will have to be treated separately. Consider the fact that IPv4 and IPv6 allocations are often different, and while a topology change may trigger renumbering for both address-families, it is also possible that a dual-stack network has other events that trigger a renumbering event on just one of  multiple address-families. You could possibly identify which of these techniques are IP version-agnostic and therefore applicable to IPv4, but note that the further gap analysis will not focus on improving IPv4 renumbering where it diverges from IPv6.

3- I would recommend reviewing and categorizing the renumbering reasons in RFC2071 specifically in a subsequent revision, rather than your current generalization that some are out of date/not suitable. For that matter, should this document formally update RFC2071?

<Sheng> We could adopt the style of RFC2071, but many of their reasons are out of date. Could you point out what our current generalization are not suitable so that we can change it in next version? Thanks.

3.1/3.2 - Right now you have this somewhat limited to PA space -  you don't actually say that, but your use cases/examples are all making that assumption, and I doubt that was your intent.
Depending on how successful RIRs have been at doing sparse allocations, it's quite possible that if a network needs to request a larger block (assuming that they have a PI allocation) from their RIR, they may receive an entirely new block rather than simply having their existing block's bit-length changed. This will trigger a renumber similar to a switch to a new ISP.

<Sheng> OK, we can add this as one sub-scenario of caused by Internal Network Factors.

4.1 Address types -
Does this draft need to discuss the common reasons for using statically-defined addresses, and perhaps identify some ways to reduce? You mention FQDN and DNS updates elsewhere in the document, but it may be useful to explicitly note that here. Also, I know you have a  placeholder entry for that in 5.3 of the gap analysis draft, but I would think that it would start here with things that can be done (BCP) today...

<sheng> I guess it is fair in the draft to say the BCP is to reduce/avoid the usage of static addresses. Will do so in the next version.

while this isn't necessarily a current use of ULA, http://tools.ietf.org/html/draft-herbst-v6ops-cpeenhancements-00 is specifying use of ULA in the Smart Grid

5 - I don't understand what that first item "manual or script-driven procedures..." means/refers to - can you attempt to clarify in the next revision?

<Sheng> This is a mistake quote from RFC 5887. It should be "manual or script-driven host address configuration procedures...". Will be fixed in the next version.

Also, doesn't most of this section belong in the gap-analysis draft?

<Sheng> This was added by suggestion from Tim. He thought a brief list in this draft can be considered as a good input or start point of gap-analysis draft.

Thanks,

Wes George
speaking as individual contributor


________________________________
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.

--Boundary_(ID_RQGdFJY0uZVblFgg59XN9g)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi, George,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for your valuab=
le comments. See my reply in lines.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Sheng<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> renum-bo=
unces@ietf.org [mailto:renum-bounces@ietf.org]
<b>On Behalf Of </b>George, Wesley<br>
<b>Sent:</b> Wednesday, July 20, 2011 3:44 AM<br>
<b>To:</b> renum@ietf.org<br>
<b>Subject:</b> [renum] comments on draft-jiang-6renum-enterprise-00<o:p></=
o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">2 &#8211; I don&#8217;t think t=
hat it&#8217;s necessary to assume that the *<b>network</b>* is IPv6-only, =
or to call dual-stack a complicated IPv4/IPv6 coexisting scenario. Your cur=
rent language makes this work irrelevant for 99.9% of
 the networks out there today (because they are either dual-stack or IPv4-o=
nly), which I think is probably not what we&#8217;re going for when we say =
that IPv4 is not in scope.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&lt;She=
ng&gt; My understanding is that focusing on IPv6 is the scope of this WG. I=
t was decided during BoF and WG creating period. Dual-stack network is incl=
uded, I think, but we only focus on IPv6 part
 of it.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I understand what you&#8217;re =
trying to say with the comment &#8220;logical IPv6 plane is independent fro=
m IPv4&#8221; but I think there&#8217;s probably a clearer way to say it.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&lt;She=
ng&gt; It looks like the word &#8220;coexisting scenario&#8221; is misleadi=
ng. We actually means IPv4/IPv6 transition scenarios. Dual-stack network is=
 in the scope. Will make clearer description in next version.
</span><span lang=3D"EN-US" style=3D"font-family:Wingdings;color:#1F497D">J=
</span><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In other words, it&#8217;s perf=
ectly acceptable to have a dual-stack network and leverage these recommenda=
tions. You just simply need to say that IPv4 renumbering is not directly co=
vered by this work and if a network is dual-stack,
 IPv4 renumbering will have to be treated separately. Consider the fact tha=
t IPv4 and IPv6 allocations are often different, and while a topology chang=
e may trigger renumbering for both address-families, it is also possible th=
at a dual-stack network has other
 events that trigger a renumbering event on just one of&nbsp; multiple addr=
ess-families. You could possibly identify which of these techniques are IP =
version-agnostic and therefore applicable to IPv4, but note that the furthe=
r gap analysis will not focus on improving
 IPv4 renumbering where it diverges from IPv6. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">3- I would recommend reviewing =
and categorizing the renumbering reasons in RFC2071 specifically in a subse=
quent revision, rather than your current generalization that some are out o=
f date/not suitable. For that matter,
 should this document formally update RFC2071?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&lt;She=
ng&gt; We could adopt the style of RFC2071, but many of their reasons are o=
ut of date. Could you point out what our current generalization are not sui=
table so that we can change it in next version?
 Thanks.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">3.1/3.2 &#8211; Right now you h=
ave this somewhat limited to PA space -&nbsp; you don&#8217;t actually say =
that, but your use cases/examples are all making that assumption, and I dou=
bt that was your intent.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Depending on how successful RIR=
s have been at doing sparse allocations, it&#8217;s quite possible that if =
a network needs to request a larger block (assuming that they have a PI all=
ocation) from their RIR, they may receive
 an entirely new block rather than simply having their existing block&#8217=
;s bit-length changed. This will trigger a renumber similar to a switch to =
a new ISP.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&lt;She=
ng&gt; OK, we can add this as one sub-scenario of caused by Internal Networ=
k Factors.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">4.1 Address types &#8211; <o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Does this draft need to discuss=
 the common reasons for using statically-defined addresses, and perhaps ide=
ntify some ways to reduce? You mention FQDN and DNS updates elsewhere in th=
e document, but it may be useful to
 explicitly note that here. Also, I know you have a&nbsp; placeholder entry=
 for that in 5.3 of the gap analysis draft, but I would think that it would=
 start here with things that can be done (BCP) today&#8230;<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&lt;she=
ng&gt; I guess it is fair in the draft to say the BCP is to reduce/avoid th=
e usage of static addresses. Will do so in the next version.<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">while this isn&#8217;t necessar=
ily a current use of ULA,
<a href=3D"http://tools.ietf.org/html/draft-herbst-v6ops-cpeenhancements-00=
">http://tools.ietf.org/html/draft-herbst-v6ops-cpeenhancements-00</a> is s=
pecifying use of ULA in the Smart Grid<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">5 &#8211; I don&#8217;t underst=
and what that first item &#8220;manual or script-driven procedures&#8230;&#=
8221; means/refers to &#8211; can you attempt to clarify in the next revisi=
on?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&lt;She=
ng&gt; This is a mistake quote from RFC 5887. It should be &#8220;manual or=
 script-driven host address configuration procedures&#8230;&#8221;. Will be=
 fixed in the next version.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Also, doesn&#8217;t most of thi=
s section belong in the gap-analysis draft?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&lt;She=
ng&gt; This was added by suggestion from Tim. He thought a brief list in th=
is draft can be considered as a good input or start point of gap-analysis d=
raft.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Wes George<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">speaking as individual contribu=
tor<span style=3D"color:#7F7F7F"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-=
family:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman=
&quot;,&quot;serif&quot;">
<hr size=3D"3" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:7.5pt;font-f=
amily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:gray">This E-mail and =
any of its attachments may contain Time Warner Cable proprietary informatio=
n, which is privileged, confidential, or subject to copyright
 belonging to Time Warner Cable. This E-mail is intended solely for the use=
 of the individual or entity to which it is addressed. If you are not the i=
ntended recipient of this E-mail, you are hereby notified that any dissemin=
ation, distribution, copying, or
 action taken in relation to the contents of and attachments to this E-mail=
 is strictly prohibited and may be unlawful. If you have received this E-ma=
il in error, please notify the sender immediately and permanently delete th=
e original and any copy of this
 E-mail and any printout.</span><span lang=3D"EN-US" style=3D"font-size:12.=
0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p><=
/span></p>
</div>
</div>
</body>
</html>

--Boundary_(ID_RQGdFJY0uZVblFgg59XN9g)--

From jiangsheng@huawei.com  Wed Jul 20 01:09:12 2011
Return-Path: <jiangsheng@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 496DB21F8782 for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 01:09:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.407
X-Spam-Level: 
X-Spam-Status: No, score=-3.407 tagged_above=-999 required=5 tests=[AWL=-0.809, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B808xDxei-EO for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 01:09:09 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 4856E21F8770 for <renum@ietf.org>; Wed, 20 Jul 2011 01:09:09 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOM00L8IH893I@szxga05-in.huawei.com> for renum@ietf.org; Wed, 20 Jul 2011 16:07:21 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOM00DJHH7T7Q@szxga05-in.huawei.com> for renum@ietf.org; Wed, 20 Jul 2011 16:07:21 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml202-edg.china.huawei.com) ([172.24.2.119])	by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACK05176; Wed, 20 Jul 2011 16:07:19 +0800 (CST)
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 20 Jul 2011 16:07:12 +0800
Received: from SZXEML506-MBX.china.huawei.com ([169.254.4.221]) by szxeml402-hub.china.huawei.com ([10.82.67.32]) with mapi id 14.01.0270.001; Wed, 20 Jul 2011 16:07:18 +0800
Date: Wed, 20 Jul 2011 08:07:17 +0000
From: Jiangsheng <jiangsheng@huawei.com>
In-reply-to: <34E4F50CAFA10349A41E0756550084FB0B61DE55@PRVPEXVS04.corp.twcable.com>
X-Originating-IP: [10.110.98.101]
To: "George, Wesley" <wesley.george@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Message-id: <5D36713D8A4E7348A7E10DF7437A4B920121835D@SZXEML506-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_ax+BrYBF1alUe+zHFLAXNA)"
Content-language: zh-CN
Accept-Language: en-GB, zh-CN, en-US
Thread-topic: [renum] scoping question - how to define Enterprise in the context of 6renum?
Thread-index: AcxGTVKvr00AFcI7ThS19/pWOhg7bQAXFWNQ
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <34E4F50CAFA10349A41E0756550084FB0B61DE55@PRVPEXVS04.corp.twcable.com>
Subject: Re: [renum] scoping question - how to define Enterprise in the context of 6renum?
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 08:09:12 -0000

--Boundary_(ID_ax+BrYBF1alUe+zHFLAXNA)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi, George,

Good catch, here. I agree ISP renumbering is very similar and should be in the scope.

Actually, there was some private discussion between IESG member and BoF/WG proponents during the WG forming. The main argument and agreement later was SOHO/MANET should be out of scope. Also the WG should avoid overlap work with HOMENET WG, which was announced yesterday.

Regards,

Sheng

From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of George, Wesley
Sent: Wednesday, July 20, 2011 3:52 AM
To: renum@ietf.org
Subject: [renum] scoping question - how to define Enterprise in the context of 6renum?

In both the charter and in the enterprise draft, we make a point to specify Enterprise renumbering as being in scope but ISP and SOHO/MANET out of scope. Right now, neither the drafts nor the charter does a particularly good job defining what is considered Enterprise and therefore in-scope, and differentiating how and why the renumbering work we're undertaking is applicable there while it is not in the other cases.

For example, what about renumbering enterprise networking infrastructure (as compared to end hosts)? I would think that this is somewhat of a small-scale version of an ISP network renumber (which was previously identified as out of scope), but it is quite possible that all or part of an enterprise's internal network infra might be subject to a renumbering event (depending on how they numbered things like routers and WAN/LAN links). If this is in scope, how do we make the distinction between SP renumbering and Enterprise renumbering? Is it just scale/amount of renumbering? If it's out of scope, what's our rationale?

I've been on the list mostly since the BOF days, but I don't remember there being a lot of discussion on this specific scoping question, so I'd like some background, either from the draft charter authors or otherwise. The only thing that I could see was some comments on the draft charter from Scott Brim specifically recommending that we remove enterprise/soho/manet in favor of something like managed or unmanaged.

I think there are probably a couple of characterization points - one is scale, the other is management/administrative domain (typically enterprises are more centrally managed), but I think there may be more that aren't occurring to me at the moment, and I'd like to get some discussion going on how we make this clearer so that we can say focused on the right scope (or redefine it if it's currently too narrow).  I think it's better to get some clarity on this now before we get too far along on the drafts and have to revisit them later.

Thanks,

Wes George
Speaking as chair


________________________________
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.

--Boundary_(ID_ax+BrYBF1alUe+zHFLAXNA)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.underline1
	{mso-style-name:underline1;
	text-decoration:underline;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi, George,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Good catch, here. I ag=
ree ISP renumbering is very similar and should be in the scope.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Actually, there was so=
me private discussion between IESG member and BoF/WG proponents during the =
WG forming. The main argument and agreement later was SOHO/MANET should be =
out of scope. Also the WG should avoid
 overlap work with HOMENET WG, which was announced yesterday.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Sheng<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> renum-bo=
unces@ietf.org [mailto:renum-bounces@ietf.org]
<b>On Behalf Of </b>George, Wesley<br>
<b>Sent:</b> Wednesday, July 20, 2011 3:52 AM<br>
<b>To:</b> renum@ietf.org<br>
<b>Subject:</b> [renum] scoping question - how to define Enterprise in the =
context of 6renum?<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In both the charter and in the =
enterprise draft, we make a point to specify Enterprise renumbering as bein=
g in scope but ISP and SOHO/MANET out of scope. Right now, neither the draf=
ts nor the charter does a particularly
 good job defining what is considered Enterprise and therefore in-scope, an=
d differentiating how and why the renumbering work we&#8217;re undertaking =
is applicable there while it is not in the other cases.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">For example, what about renumbe=
ring enterprise networking infrastructure (as compared to end hosts)? I wou=
ld think that this is somewhat of a small-scale version of an ISP network r=
enumber (which was previously identified
 as out of scope), but it is quite possible that all or part of an enterpri=
se&#8217;s internal network infra might be subject to a renumbering event (=
depending on how they numbered things like routers and WAN/LAN links). If t=
his is in scope, how do we make the distinction
 between SP renumbering and Enterprise renumbering? Is it just scale/amount=
 of renumbering? If it&#8217;s out of scope, what&#8217;s our rationale?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I&#8217;ve been on the list mos=
tly since the BOF days, but I don&#8217;t remember there being a lot of dis=
cussion on this specific scoping question, so I&#8217;d like some backgroun=
d, either from the draft charter authors or otherwise.
 The only thing that I could see was some comments on the draft charter fro=
m Scott Brim specifically recommending that we remove enterprise/soho/manet=
 in favor of something like managed or unmanaged.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I think there are probably a co=
uple of characterization points &#8211; one is scale, the other is manageme=
nt/administrative domain (typically enterprises are more centrally managed)=
, but I think there may be more that aren&#8217;t
 occurring to me at the moment, and I&#8217;d like to get some discussion g=
oing on how we make this clearer so that we can say focused on the right sc=
ope (or redefine it if it&#8217;s currently too narrow).&nbsp; I think it&#=
8217;s better to get some clarity on this now before we
 get too far along on the drafts and have to revisit them later. <o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Wes George<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Speaking as chair<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-=
family:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman=
&quot;,&quot;serif&quot;">
<hr size=3D"3" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:7.5pt;font-f=
amily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:gray">This E-mail and =
any of its attachments may contain Time Warner Cable proprietary informatio=
n, which is privileged, confidential, or subject to copyright
 belonging to Time Warner Cable. This E-mail is intended solely for the use=
 of the individual or entity to which it is addressed. If you are not the i=
ntended recipient of this E-mail, you are hereby notified that any dissemin=
ation, distribution, copying, or
 action taken in relation to the contents of and attachments to this E-mail=
 is strictly prohibited and may be unlawful. If you have received this E-ma=
il in error, please notify the sender immediately and permanently delete th=
e original and any copy of this
 E-mail and any printout.</span><span lang=3D"EN-US" style=3D"font-size:12.=
0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p><=
/span></p>
</div>
</div>
</body>
</html>

--Boundary_(ID_ax+BrYBF1alUe+zHFLAXNA)--

From wesley.george@twcable.com  Wed Jul 20 05:35:39 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9733921F8747 for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 05:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.187
X-Spam-Level: 
X-Spam-Status: No, score=-0.187 tagged_above=-999 required=5 tests=[AWL=0.275,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v9MKMVpbNewY for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 05:35:35 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 3ECF921F8661 for <renum@ietf.org>; Wed, 20 Jul 2011 05:35:35 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,235,1309752000";  d="scan'208,217";a="237601575"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 20 Jul 2011 08:33:45 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.29]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Wed, 20 Jul 2011 08:35:34 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: Jiangsheng <jiangsheng@huawei.com>, "renum@ietf.org" <renum@ietf.org>
Date: Wed, 20 Jul 2011 08:35:32 -0400
Thread-Topic: comments on draft-jiang-6renum-enterprise-00
Thread-Index: AcxGTCbF/pU0ChUVQXa10ceAEcTaeQAPYnLwABOcZRA=
Message-ID: <34E4F50CAFA10349A41E0756550084FB0B61DFE7@PRVPEXVS04.corp.twcable.com>
References: <34E4F50CAFA10349A41E0756550084FB0B61DE3B@PRVPEXVS04.corp.twcable.com> <5D36713D8A4E7348A7E10DF7437A4B92012182EA@SZXEML506-MBX.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B92012182EA@SZXEML506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_34E4F50CAFA10349A41E0756550084FB0B61DFE7PRVPEXVS04corpt_"
MIME-Version: 1.0
Subject: Re: [renum] comments on draft-jiang-6renum-enterprise-00
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 12:35:39 -0000

--_000_34E4F50CAFA10349A41E0756550084FB0B61DFE7PRVPEXVS04corpt_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Inline below

Thanks
Wes
Still as individual contributor

From: Jiangsheng [mailto:jiangsheng@huawei.com]
Sent: Wednesday, July 20, 2011 2:52 AM
To: George, Wesley; renum@ietf.org
Subject: RE: comments on draft-jiang-6renum-enterprise-00

Hi, George,

Thanks for your valuable comments. See my reply in lines.

Sheng

From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of G=
eorge, Wesley
Sent: Wednesday, July 20, 2011 3:44 AM
To: renum@ietf.org
Subject: [renum] comments on draft-jiang-6renum-enterprise-00

2 - I don't think that it's necessary to assume that the *network* is IPv6-=
only, or to call dual-stack a complicated IPv4/IPv6 coexisting scenario. Yo=
ur current language makes this work irrelevant for 99.9% of the networks ou=
t there today (because they are either dual-stack or IPv4-only), which I th=
ink is probably not what we're going for when we say that IPv4 is not in sc=
ope.

<Sheng> My understanding is that focusing on IPv6 is the scope of this WG. =
It was decided during BoF and WG creating period. Dual-stack network is inc=
luded, I think, but we only focus on IPv6 part of it.

WEG> I understand, and we're in agreement on the scope. I'm simply saying t=
hat right now I think the text goes out of its way to exclude IPv4 even whe=
n it would be able to take advantage of the work because it is IP version-a=
gnostic. I think that your suggested update will help to clarify.


3- I would recommend reviewing and categorizing the renumbering reasons in =
RFC2071 specifically in a subsequent revision, rather than your current gen=
eralization that some are out of date/not suitable. For that matter, should=
 this document formally update RFC2071?

<Sheng> We could adopt the style of RFC2071, but many of their reasons are =
out of date. Could you point out what our current generalization are not su=
itable so that we can change it in next version? Thanks.


WEG> My problem is with "Some of renumbering reasons
   described in [RFC2071<http://tools.ietf.org/html/rfc2071>] has out of da=
te, or not suitable in IPv6, or
   not suitable for enterprise networks."

Specifically, I have issue with the reference to 2071 and then the general =
statement "some ... out of date/not suitable" without specifying which are =
still acceptable, which are out of date/not suitable. "Some" is unclear/ove=
rly general by itself. If they are all unsuitable, make it clear that this =
is meant to replace those definitions as they are all unsuitable, and there=
fore list 2071 as being formally updated by this draft.

________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

--_000_34E4F50CAFA10349A41E0756550084FB0B61DFE7PRVPEXVS04corpt_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Inline below<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Wes<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Still as individual co=
ntributor</span><span style=3D"font-size:9.0pt;color:#7F7F7F"><o:p></o:p></=
span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jiangshe=
ng [mailto:jiangsheng@huawei.com]
<br>
<b>Sent:</b> Wednesday, July 20, 2011 2:52 AM<br>
<b>To:</b> George, Wesley; renum@ietf.org<br>
<b>Subject:</b> RE: comments on draft-jiang-6renum-enterprise-00<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Hi, Geo=
rge,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Thanks =
for your valuable comments. See my reply in lines.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Sheng<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"EN-GB" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> renum-bounces@ietf.org [mailto:renum-bounces@ietf.org=
]
<b>On Behalf Of </b>George, Wesley<br>
<b>Sent:</b> Wednesday, July 20, 2011 3:44 AM<br>
<b>To:</b> renum@ietf.org<br>
<b>Subject:</b> [renum] comments on draft-jiang-6renum-enterprise-00<o:p></=
o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">2 &#8211; I don&#8217;t think that it&#8217;s necess=
ary to assume that the *<b>network</b>* is IPv6-only, or to call dual-stack=
 a complicated IPv4/IPv6 coexisting scenario. Your current language makes t=
his work irrelevant for 99.9% of the networks out there
 today (because they are either dual-stack or IPv4-only), which I think is =
probably not what we&#8217;re going for when we say that IPv4 is not in sco=
pe.<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&lt;Sheng&gt; My under=
standing is that focusing on IPv6 is the scope of this WG. It was decided d=
uring BoF and WG creating period. Dual-stack network is included, I think, =
but we only focus on IPv6 part of it.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#0F243E">WEG&gt; I understand, =
and we&#8217;re in agreement on the scope. I&#8217;m simply saying that rig=
ht now I think the text goes out of its way to exclude IPv4 even when it wo=
uld be able to take advantage of the work because it
 is IP version-agnostic. I think that your suggested update will help to cl=
arify.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">3- I would recommend reviewing and categorizing the =
renumbering reasons in RFC2071 specifically in a subsequent revision, rathe=
r than your current generalization that some are out of date/not suitable. =
For that matter, should this document
 formally update RFC2071?<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&lt;Sheng&gt; We could=
 adopt the style of RFC2071, but many of their reasons are out of date. Cou=
ld you point out what our current generalization are not suitable so that w=
e can change it in next version? Thanks.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:11.0pt;fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#0F243E">WEG&gt; =
My problem is with</span><span style=3D"font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1F497D"> &#8220;</span><span style=3D"font-size:=
12.0pt;color:black">Some of renumbering reasons<o:p></o:p></span></pre>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; described in [<a href=3D"http://tools.ietf.org/html/rfc2071" title=3D"&qu=
ot;Network Renumbering Overview: Why would I want it and what is it anyway?=
&quot;">RFC2071</a>]
 has out of date, or not suitable in IPv6, or<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; not suitable for enterprise networks.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#0F243E">Specifically, I have i=
ssue with the reference to 2071 and then the general statement &#8220;some =
&#8230; out of date/not suitable&#8221; without specifying which are still =
acceptable, which are out of date/not suitable. &#8220;Some&#8221;
 is unclear/overly general by itself. If they are all unsuitable, make it c=
lear that this is meant to replace those definitions as they are all unsuit=
able, and therefore list 2071 as being formally updated by this draft.
<o:p></o:p></span></p>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>

--_000_34E4F50CAFA10349A41E0756550084FB0B61DFE7PRVPEXVS04corpt_--

From wesley.george@twcable.com  Wed Jul 20 05:50:41 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AC3C21F8892 for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 05:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.204
X-Spam-Level: 
X-Spam-Status: No, score=-0.204 tagged_above=-999 required=5 tests=[AWL=0.258,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hw2CobO96v84 for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 05:50:38 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 1548321F8888 for <renum@ietf.org>; Wed, 20 Jul 2011 05:50:37 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,235,1309752000";  d="scan'208,217";a="237606336"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 20 Jul 2011 08:48:48 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.29]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Wed, 20 Jul 2011 08:50:37 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: Jiangsheng <jiangsheng@huawei.com>, "renum@ietf.org" <renum@ietf.org>
Date: Wed, 20 Jul 2011 08:50:36 -0400
Thread-Topic: [renum] scoping question - how to define Enterprise in the context of 6renum?
Thread-Index: AcxGTVKvr00AFcI7ThS19/pWOhg7bQAXFWNQAAv6UpA=
Message-ID: <34E4F50CAFA10349A41E0756550084FB0B61DFFB@PRVPEXVS04.corp.twcable.com>
References: <34E4F50CAFA10349A41E0756550084FB0B61DE55@PRVPEXVS04.corp.twcable.com> <5D36713D8A4E7348A7E10DF7437A4B920121835D@SZXEML506-MBX.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B920121835D@SZXEML506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_34E4F50CAFA10349A41E0756550084FB0B61DFFBPRVPEXVS04corpt_"
MIME-Version: 1.0
Subject: Re: [renum] scoping question - how to define Enterprise in the context of 6renum?
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 12:50:41 -0000

--_000_34E4F50CAFA10349A41E0756550084FB0B61DFFBPRVPEXVS04corpt_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The problem is that http://datatracker.ietf.org/wg/6renum/charter/ item #3 =
of the "out of scope" section specifically says "ISP renumbering." If the g=
roup agrees that this needs to be changed, we can request a charter update,=
 but mainly I'm looking for clarity on how we define the scope, especially =
what is specifically considered "enterprise" so that we can keep focus on t=
he right things.

Regarding ISP renumbering, my view is that we should focus on Enterprise, i=
ncluding network infra, and that will provide a framework that can be exten=
ded to ISP renumbering (with the appropriate charter update) at a later poi=
nt.

I'll respond to your comment about HOMENET in a separate thread.

Thanks
Wes
Speaking as chair

From: Jiangsheng [mailto:jiangsheng@huawei.com]
Sent: Wednesday, July 20, 2011 4:07 AM
To: George, Wesley; renum@ietf.org
Subject: RE: [renum] scoping question - how to define Enterprise in the con=
text of 6renum?

Hi, George,

Good catch, here. I agree ISP renumbering is very similar and should be in =
the scope.

Actually, there was some private discussion between IESG member and BoF/WG =
proponents during the WG forming. The main argument and agreement later was=
 SOHO/MANET should be out of scope. Also the WG should avoid overlap work w=
ith HOMENET WG, which was announced yesterday.

Regards,

Sheng

From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of G=
eorge, Wesley
Sent: Wednesday, July 20, 2011 3:52 AM
To: renum@ietf.org
Subject: [renum] scoping question - how to define Enterprise in the context=
 of 6renum?

In both the charter and in the enterprise draft, we make a point to specify=
 Enterprise renumbering as being in scope but ISP and SOHO/MANET out of sco=
pe. Right now, neither the drafts nor the charter does a particularly good =
job defining what is considered Enterprise and therefore in-scope, and diff=
erentiating how and why the renumbering work we're undertaking is applicabl=
e there while it is not in the other cases.

For example, what about renumbering enterprise networking infrastructure (a=
s compared to end hosts)? I would think that this is somewhat of a small-sc=
ale version of an ISP network renumber (which was previously identified as =
out of scope), but it is quite possible that all or part of an enterprise's=
 internal network infra might be subject to a renumbering event (depending =
on how they numbered things like routers and WAN/LAN links). If this is in =
scope, how do we make the distinction between SP renumbering and Enterprise=
 renumbering? Is it just scale/amount of renumbering? If it's out of scope,=
 what's our rationale?

I've been on the list mostly since the BOF days, but I don't remember there=
 being a lot of discussion on this specific scoping question, so I'd like s=
ome background, either from the draft charter authors or otherwise. The onl=
y thing that I could see was some comments on the draft charter from Scott =
Brim specifically recommending that we remove enterprise/soho/manet in favo=
r of something like managed or unmanaged.

I think there are probably a couple of characterization points - one is sca=
le, the other is management/administrative domain (typically enterprises ar=
e more centrally managed), but I think there may be more that aren't occurr=
ing to me at the moment, and I'd like to get some discussion going on how w=
e make this clearer so that we can say focused on the right scope (or redef=
ine it if it's currently too narrow).  I think it's better to get some clar=
ity on this now before we get too far along on the drafts and have to revis=
it them later.

Thanks,

Wes George
Speaking as chair


________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

--_000_34E4F50CAFA10349A41E0756550084FB0B61DFFBPRVPEXVS04corpt_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator content=3D"Microsoft Word 12 (filtered medium)"><!--[if !mso]><style=
>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.underline1
	{mso-style-name:underline1;
	text-decoration:underline;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><div><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>The problem is that </span><a href=3D"http://datatracker=
.ietf.org/wg/6renum/charter/">http://datatracker.ietf.org/wg/6renum/charter=
/</a> <span style=3D'color:#1F497D'>item #3 of the &#8220;out of scope&#822=
1; section specifically says &#8220;ISP renumbering.&#8221; If the group ag=
rees that this needs to be changed, we can request a charter update, but ma=
inly I&#8217;m looking for clarity on how we define the scope, especially w=
hat is specifically considered &#8220;enterprise&#8221; so that we can keep=
 focus on the right things. <o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal>=
<span style=3D'color:#1F497D'>Regarding ISP renumbering, my view is that we=
 should focus on Enterprise, including network infra, and that will provide=
 a framework that can be extended to ISP renumbering (with the appropriate =
charter update) at a later point. </span><span style=3D'font-size:9.0pt;col=
or:#7F7F7F'><o:p></o:p></span></p></div><p class=3DMsoNormal><span style=3D=
'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'color:#1F497D'>I&#8217;ll respond to your comment about HOMENET in a s=
eparate thread.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'co=
lor:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>Thanks<o:p></o:p></span></p><p class=3DMsoNormal><span s=
tyle=3D'color:#1F497D'>Wes<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Speaking as chair<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><di=
v style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in=
 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"=
Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-=
family:"Tahoma","sans-serif"'> Jiangsheng [mailto:jiangsheng@huawei.com] <b=
r><b>Sent:</b> Wednesday, July 20, 2011 4:07 AM<br><b>To:</b> George, Wesle=
y; renum@ietf.org<br><b>Subject:</b> RE: [renum] scoping question - how to =
define Enterprise in the context of 6renum?<o:p></o:p></span></p></div></di=
v><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span lang=
=3DEN-GB style=3D'color:#1F497D'>Hi, George,<o:p></o:p></span></p><p class=
=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'><o:p>&nbsp;</o:p></=
span></p><p class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>Go=
od catch, here. I agree ISP renumbering is very similar and should be in th=
e scope.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB style=
=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span l=
ang=3DEN-GB style=3D'color:#1F497D'>Actually, there was some private discus=
sion between IESG member and BoF/WG proponents during the WG forming. The m=
ain argument and agreement later was SOHO/MANET should be out of scope. Als=
o the WG should avoid overlap work with HOMENET WG, which was announced yes=
terday.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB style=
=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span l=
ang=3DEN-GB style=3D'color:#1F497D'>Regards,<o:p></o:p></span></p><p class=
=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'><o:p>&nbsp;</o:p></=
span></p><p class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>Sh=
eng<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB style=3D'c=
olor:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-=
left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'border:=
none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DM=
soNormal><b><span lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif"'>From:</span></b><span lang=3DEN-GB style=3D'font-size:10.0=
pt;font-family:"Tahoma","sans-serif"'> renum-bounces@ietf.org [mailto:renum=
-bounces@ietf.org] <b>On Behalf Of </b>George, Wesley<br><b>Sent:</b> Wedne=
sday, July 20, 2011 3:52 AM<br><b>To:</b> renum@ietf.org<br><b>Subject:</b>=
 [renum] scoping question - how to define Enterprise in the context of 6ren=
um?<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span lang=3DEN-G=
B><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal>In both the charter and =
in the enterprise draft, we make a point to specify Enterprise renumbering =
as being in scope but ISP and SOHO/MANET out of scope. Right now, neither t=
he drafts nor the charter does a particularly good job defining what is con=
sidered Enterprise and therefore in-scope, and differentiating how and why =
the renumbering work we&#8217;re undertaking is applicable there while it i=
s not in the other cases. <o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</=
o:p></p><p class=3DMsoNormal>For example, what about renumbering enterprise=
 networking infrastructure (as compared to end hosts)? I would think that t=
his is somewhat of a small-scale version of an ISP network renumber (which =
was previously identified as out of scope), but it is quite possible that a=
ll or part of an enterprise&#8217;s internal network infra might be subject=
 to a renumbering event (depending on how they numbered things like routers=
 and WAN/LAN links). If this is in scope, how do we make the distinction be=
tween SP renumbering and Enterprise renumbering? Is it just scale/amount of=
 renumbering? If it&#8217;s out of scope, what&#8217;s our rationale? <o:p>=
</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I&=
#8217;ve been on the list mostly since the BOF days, but I don&#8217;t reme=
mber there being a lot of discussion on this specific scoping question, so =
I&#8217;d like some background, either from the draft charter authors or ot=
herwise. The only thing that I could see was some comments on the draft cha=
rter from Scott Brim specifically recommending that we remove enterprise/so=
ho/manet in favor of something like managed or unmanaged.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I think there a=
re probably a couple of characterization points &#8211; one is scale, the o=
ther is management/administrative domain (typically enterprises are more ce=
ntrally managed), but I think there may be more that aren&#8217;t occurring=
 to me at the moment, and I&#8217;d like to get some discussion going on ho=
w we make this clearer so that we can say focused on the right scope (or re=
define it if it&#8217;s currently too narrow).&nbsp; I think it&#8217;s bet=
ter to get some clarity on this now before we get too far along on the draf=
ts and have to revisit them later. <o:p></o:p></p><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p><p class=3DMsoNormal>Thanks,<o:p></o:p></p><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Wes George<o:p></o:p></p><p=
 class=3DMsoNormal>Speaking as chair<o:p></o:p></p><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font=
-family:"Times New Roman","serif"'><o:p>&nbsp;</o:p></span></p><div class=
=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span style=3D'font=
-size:12.0pt;font-family:"Times New Roman","serif"'><hr size=3D3 width=3D"1=
00%" align=3Dcenter></span></div><p class=3DMsoNormal><span style=3D'font-s=
ize:7.5pt;font-family:"Arial","sans-serif";color:gray'>This E-mail and any =
of its attachments may contain Time Warner Cable proprietary information, w=
hich is privileged, confidential, or subject to copyright belonging to Time=
 Warner Cable. This E-mail is intended solely for the use of the individual=
 or entity to which it is addressed. If you are not the intended recipient =
of this E-mail, you are hereby notified that any dissemination, distributio=
n, copying, or action taken in relation to the contents of and attachments =
to this E-mail is strictly prohibited and may be unlawful. If you have rece=
ived this E-mail in error, please notify the sender immediately and permane=
ntly delete the original and any copy of this E-mail and any printout.</spa=
n><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o=
:p></o:p></span></p></div></div></body></html>=

--_000_34E4F50CAFA10349A41E0756550084FB0B61DFFBPRVPEXVS04corpt_--

From wesley.george@twcable.com  Wed Jul 20 06:11:13 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8774621F86C3 for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 06:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.219
X-Spam-Level: 
X-Spam-Status: No, score=-0.219 tagged_above=-999 required=5 tests=[AWL=0.243,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id panVCKxI70Cr for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 06:11:10 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 0515A21F869D for <renum@ietf.org>; Wed, 20 Jul 2011 06:11:09 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,235,1309752000";  d="scan'208,217";a="237616282"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 20 Jul 2011 09:09:20 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.29]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Wed, 20 Jul 2011 09:11:09 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: Jiangsheng <jiangsheng@huawei.com>, "renum@ietf.org" <renum@ietf.org>
Date: Wed, 20 Jul 2011 09:11:08 -0400
Thread-Topic: Overlap/interaction with other WGs (was RE: [renum] scoping question - how to define Enterprise in the context of 6renum?)
Thread-Index: AcxGTVKvr00AFcI7ThS19/pWOhg7bQAXFWNQAAxtslA=
Message-ID: <34E4F50CAFA10349A41E0756550084FB0B61E019@PRVPEXVS04.corp.twcable.com>
References: <34E4F50CAFA10349A41E0756550084FB0B61DE55@PRVPEXVS04.corp.twcable.com> <5D36713D8A4E7348A7E10DF7437A4B920121835D@SZXEML506-MBX.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B920121835D@SZXEML506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_34E4F50CAFA10349A41E0756550084FB0B61E019PRVPEXVS04corpt_"
MIME-Version: 1.0
Subject: [renum] Overlap/interaction with other WGs (was RE: scoping question - how to define Enterprise in the context of 6renum?)
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 13:11:13 -0000

--_000_34E4F50CAFA10349A41E0756550084FB0B61E019PRVPEXVS04corpt_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

New subject for this part of the thread

Regarding HOMENET overlap (and other WGs in general) - since we are an OpsA=
rea WG, we're not going to do much (if any) protocol work. We're going to d=
ocument BCP and identify gaps + possibly requirements for any solutions to =
those gaps. Any protocol work necessary would have to be offloaded to other=
 groups, such as DHC. HOMENET might also be one of those offload groups, bu=
t I don't expect there to be an overlap problem. That said, one of my colle=
agues is going to be watching HOMENET carefully, so I expect he'll keep me =
in the loop on what's happening in that group.
And while we've explicitly excluded MANET and SOHO networks (HOMENET) from =
our scope, it may be useful for MANET and or HOMENET to generate companion =
drafts to cover some of the same issues, use cases, and gaps within their s=
pace with a draft that we can reference in our own. If there are folks on t=
his list who are also planning to participate in either of those groups, yo=
u might mention it on the lists.
It is probably also a good idea for folks to keep an eye on the discussion =
happening in OpsAWG regarding VM migration in the datacenter, since there m=
ay be some use cases that could trigger renumbering events, or would be loo=
king to specifically avoid renumbering events for a number of reasons.

Thanks,

Wes
Speaking as chair


From: Jiangsheng [mailto:jiangsheng@huawei.com]
Sent: Wednesday, July 20, 2011 4:07 AM
To: George, Wesley; renum@ietf.org
Subject: RE: [renum] scoping question - how to define Enterprise in the con=
text of 6renum?

Hi, George,

Good catch, here. I agree ISP renumbering is very similar and should be in =
the scope.

Actually, there was some private discussion between IESG member and BoF/WG =
proponents during the WG forming. The main argument and agreement later was=
 SOHO/MANET should be out of scope. Also the WG should avoid overlap work w=
ith HOMENET WG, which was announced yesterday.

Regards,

Sheng

From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of G=
eorge, Wesley
Sent: Wednesday, July 20, 2011 3:52 AM
To: renum@ietf.org
Subject: [renum] scoping question - how to define Enterprise in the context=
 of 6renum?

In both the charter and in the enterprise draft, we make a point to specify=
 Enterprise renumbering as being in scope but ISP and SOHO/MANET out of sco=
pe. Right now, neither the drafts nor the charter does a particularly good =
job defining what is considered Enterprise and therefore in-scope, and diff=
erentiating how and why the renumbering work we're undertaking is applicabl=
e there while it is not in the other cases.

For example, what about renumbering enterprise networking infrastructure (a=
s compared to end hosts)? I would think that this is somewhat of a small-sc=
ale version of an ISP network renumber (which was previously identified as =
out of scope), but it is quite possible that all or part of an enterprise's=
 internal network infra might be subject to a renumbering event (depending =
on how they numbered things like routers and WAN/LAN links). If this is in =
scope, how do we make the distinction between SP renumbering and Enterprise=
 renumbering? Is it just scale/amount of renumbering? If it's out of scope,=
 what's our rationale?

I've been on the list mostly since the BOF days, but I don't remember there=
 being a lot of discussion on this specific scoping question, so I'd like s=
ome background, either from the draft charter authors or otherwise. The onl=
y thing that I could see was some comments on the draft charter from Scott =
Brim specifically recommending that we remove enterprise/soho/manet in favo=
r of something like managed or unmanaged.

I think there are probably a couple of characterization points - one is sca=
le, the other is management/administrative domain (typically enterprises ar=
e more centrally managed), but I think there may be more that aren't occurr=
ing to me at the moment, and I'd like to get some discussion going on how w=
e make this clearer so that we can say focused on the right scope (or redef=
ine it if it's currently too narrow).  I think it's better to get some clar=
ity on this now before we get too far along on the drafts and have to revis=
it them later.

Thanks,

Wes George
Speaking as chair


________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

--_000_34E4F50CAFA10349A41E0756550084FB0B61E019PRVPEXVS04corpt_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator content=3D"Microsoft Word 12 (filtered medium)"><!--[if !mso]><style=
>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.underline1
	{mso-style-name:underline1;
	text-decoration:underline;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
olor:#1F497D'>New subject for this part of the thread<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoNormal><span style=3D'color:#1F497D'>Regarding HOMENET ov=
erlap (and other WGs in general) &#8211; since we are an OpsArea WG, we&#82=
17;re not going to do much (if any) protocol work. We&#8217;re going to doc=
ument BCP and identify gaps + possibly requirements for any solutions to th=
ose gaps. Any protocol work necessary would have to be offloaded to other g=
roups, such as DHC. HOMENET might also be one of those offload groups, but =
I don&#8217;t expect there to be an overlap problem. That said, one of my c=
olleagues is going to be watching HOMENET carefully, so I expect he&#8217;l=
l keep me in the loop on what&#8217;s happening in that group. <o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>And while we&#=
8217;ve explicitly excluded MANET and SOHO networks (HOMENET) from our scop=
e, it may be useful for MANET and or HOMENET to generate companion drafts t=
o cover some of the same issues, use cases, and gaps within their space wit=
h a draft that we can reference in our own. If there are folks on this list=
 who are also planning to participate in either of those groups, you might =
mention it on the lists.<o:p></o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'color:#1F497D'>It is probably also a good idea for folks to keep an =
eye on the discussion happening in OpsAWG regarding VM migration in the dat=
acenter, since there may be some use cases that could trigger renumbering e=
vents, or would be looking to specifically avoid renumbering events for a n=
umber of reasons. <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span=
 style=3D'font-size:10.0pt;color:#1F497D'>Thanks,<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'font-size:10.0pt;color:#1F497D'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;color=
:#1F497D'>Wes<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;color:#1F497D'>Speaking as chair<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;color:#1F497D'><o:p>&nbsp;</o:=
p></span></p></div><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>=
&nbsp;</o:p></span></p><div><div style=3D'border:none;border-top:solid #B5C=
4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D=
'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Jiangsheng [m=
ailto:jiangsheng@huawei.com] <br><b>Sent:</b> Wednesday, July 20, 2011 4:07=
 AM<br><b>To:</b> George, Wesley; renum@ietf.org<br><b>Subject:</b> RE: [re=
num] scoping question - how to define Enterprise in the context of 6renum?<=
o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p>=
<p class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>Hi, George,=
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB style=3D'colo=
r:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN=
-GB style=3D'color:#1F497D'>Good catch, here. I agree ISP renumbering is ve=
ry similar and should be in the scope.<o:p></o:p></span></p><p class=3DMsoN=
ormal><span lang=3DEN-GB style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></=
p><p class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>Actually,=
 there was some private discussion between IESG member and BoF/WG proponent=
s during the WG forming. The main argument and agreement later was SOHO/MAN=
ET should be out of scope. Also the WG should avoid overlap work with HOMEN=
ET WG, which was announced yesterday.<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span lang=3DEN-GB style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>Regards,<o=
:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB style=3D'color:=
#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-G=
B style=3D'color:#1F497D'>Sheng<o:p></o:p></span></p><p class=3DMsoNormal><=
span lang=3DEN-GB style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt=
'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0=
pt 0in 0in 0in'><p class=3DMsoNormal><b><span lang=3DEN-GB style=3D'font-si=
ze:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=3DE=
N-GB style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> renum-bo=
unces@ietf.org [mailto:renum-bounces@ietf.org] <b>On Behalf Of </b>George, =
Wesley<br><b>Sent:</b> Wednesday, July 20, 2011 3:52 AM<br><b>To:</b> renum=
@ietf.org<br><b>Subject:</b> [renum] scoping question - how to define Enter=
prise in the context of 6renum?<o:p></o:p></span></p></div></div><p class=
=3DMsoNormal><span lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal>In both the charter and in the enterprise draft, we make a point to s=
pecify Enterprise renumbering as being in scope but ISP and SOHO/MANET out =
of scope. Right now, neither the drafts nor the charter does a particularly=
 good job defining what is considered Enterprise and therefore in-scope, an=
d differentiating how and why the renumbering work we&#8217;re undertaking =
is applicable there while it is not in the other cases. <o:p></o:p></p><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>For example, wha=
t about renumbering enterprise networking infrastructure (as compared to en=
d hosts)? I would think that this is somewhat of a small-scale version of a=
n ISP network renumber (which was previously identified as out of scope), b=
ut it is quite possible that all or part of an enterprise&#8217;s internal =
network infra might be subject to a renumbering event (depending on how the=
y numbered things like routers and WAN/LAN links). If this is in scope, how=
 do we make the distinction between SP renumbering and Enterprise renumberi=
ng? Is it just scale/amount of renumbering? If it&#8217;s out of scope, wha=
t&#8217;s our rationale? <o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o=
:p></p><p class=3DMsoNormal>I&#8217;ve been on the list mostly since the BO=
F days, but I don&#8217;t remember there being a lot of discussion on this =
specific scoping question, so I&#8217;d like some background, either from t=
he draft charter authors or otherwise. The only thing that I could see was =
some comments on the draft charter from Scott Brim specifically recommendin=
g that we remove enterprise/soho/manet in favor of something like managed o=
r unmanaged.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cla=
ss=3DMsoNormal>I think there are probably a couple of characterization poin=
ts &#8211; one is scale, the other is management/administrative domain (typ=
ically enterprises are more centrally managed), but I think there may be mo=
re that aren&#8217;t occurring to me at the moment, and I&#8217;d like to g=
et some discussion going on how we make this clearer so that we can say foc=
used on the right scope (or redefine it if it&#8217;s currently too narrow)=
.&nbsp; I think it&#8217;s better to get some clarity on this now before we=
 get too far along on the drafts and have to revisit them later. <o:p></o:p=
></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thanks,=
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorm=
al>Wes George<o:p></o:p></p><p class=3DMsoNormal>Speaking as chair<o:p></o:=
p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p>&nbsp=
;</o:p></span></p><div class=3DMsoNormal align=3Dcenter style=3D'text-align=
:center'><span style=3D'font-size:12.0pt;font-family:"Times New Roman","ser=
if"'><hr size=3D3 width=3D"100%" align=3Dcenter></span></div><p class=3DMso=
Normal><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";colo=
r:gray'>This E-mail and any of its attachments may contain Time Warner Cabl=
e proprietary information, which is privileged, confidential, or subject to=
 copyright belonging to Time Warner Cable. This E-mail is intended solely f=
or the use of the individual or entity to which it is addressed. If you are=
 not the intended recipient of this E-mail, you are hereby notified that an=
y dissemination, distribution, copying, or action taken in relation to the =
contents of and attachments to this E-mail is strictly prohibited and may b=
e unlawful. If you have received this E-mail in error, please notify the se=
nder immediately and permanently delete the original and any copy of this E=
-mail and any printout.</span><span style=3D'font-size:12.0pt;font-family:"=
Times New Roman","serif"'><o:p></o:p></span></p></div></div></body></html>=

--_000_34E4F50CAFA10349A41E0756550084FB0B61E019PRVPEXVS04corpt_--

From brian.e.carpenter@gmail.com  Wed Jul 20 14:25:37 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83A3921F89BE for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 14:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.615
X-Spam-Level: 
X-Spam-Status: No, score=-103.615 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id akrWPhJ1sHrd for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 14:25:37 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id D7BEC21F89C1 for <renum@ietf.org>; Wed, 20 Jul 2011 14:25:36 -0700 (PDT)
Received: by qyk9 with SMTP id 9so3797187qyk.10 for <renum@ietf.org>; Wed, 20 Jul 2011 14:25:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=L7GmbVMkWS03gmn/eKHsOI753hhBXcFYEeN9Rob4m04=; b=j9q204LiJWcIYtgKu8rrYpOEmgwMosR0k3C6NXQzWyVYPvQHlMYOGODgILQr/206Z4 EEtSdtCms+5oR8HX3DXQYf0yDUcUOtwkVw9J7joOEBbwELYKtjpALGXtqZwH5sy/7i/x 7yGljMERT/Zu6uhVqh5BWkj8mMMZGZK4+3DXA=
Received: by 10.229.136.81 with SMTP id q17mr7398137qct.170.1311197136324; Wed, 20 Jul 2011 14:25:36 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id s14sm401614qct.6.2011.07.20.14.25.33 (version=SSLv3 cipher=OTHER); Wed, 20 Jul 2011 14:25:35 -0700 (PDT)
Message-ID: <4E2747C8.7070600@gmail.com>
Date: Thu, 21 Jul 2011 09:25:28 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "George, Wesley" <wesley.george@twcable.com>
References: <34E4F50CAFA10349A41E0756550084FB0B61DE55@PRVPEXVS04.corp.twcable.com>	<5D36713D8A4E7348A7E10DF7437A4B920121835D@SZXEML506-MBX.china.huawei.com> <34E4F50CAFA10349A41E0756550084FB0B61DFFB@PRVPEXVS04.corp.twcable.com>
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB0B61DFFB@PRVPEXVS04.corp.twcable.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] scoping question - how to define Enterprise in the context of 6renum?
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 21:25:37 -0000

On 2011-07-21 00:50, George, Wesley wrote:
> The problem is that http://datatracker.ietf.org/wg/6renum/charter/ item #3 of the "out of scope" section specifically says "ISP renumbering." If the group agrees that this needs to be changed, we can request a charter update, but mainly I'm looking for clarity on how we define the scope, especially what is specifically considered "enterprise" so that we can keep focus on the right things.
> 
> Regarding ISP renumbering, my view is that we should focus on Enterprise, including network infra, and that will provide a framework that can be extended to ISP renumbering (with the appropriate charter update) at a later point.

Maybe we should interpret the charter for now to mean that we will not work to
identify ISP-specific requirements, beyond what applies to any enterprise
including ISPs. It's obvious that many things will apply both to end-user
enterprise networks and to ISP networks, but (for example) renumbering
mass-market access devices would be ISP-specific. In the other direction,
mechanisms for relating individual host MAC addresses to wiring topology
and to address assignment mainly apply to campus-style enterprise
networks.

Anyway - I agree that there is certainly a need to define crisply what
"enterprise network" means to us. We could look at RFC 4057:

  "Enterprise Network - A network that has multiple internal links, one
                        or more router connections to one or more
                        Providers, and is actively managed by a network
                        operations entity.

   Provider           - An entity that provides services and
                        connectivity to the Internet or other private
                        external networks for the enterprise network."

and at the section "2. Brief Description of a Generic ISP Network" in RFC 4029.

(I'm not sure this was a correct chartering decision, and it could certainly
be reviewed before IETF 82.)

   Brian

From rogerj@gmail.com  Wed Jul 20 23:49:48 2011
Return-Path: <rogerj@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE53521F8606 for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 23:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.199
X-Spam-Level: 
X-Spam-Status: No, score=-3.199 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l58a4utRT8+w for <renum@ietfa.amsl.com>; Wed, 20 Jul 2011 23:49:44 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 425C221F85F2 for <renum@ietf.org>; Wed, 20 Jul 2011 23:49:44 -0700 (PDT)
Received: by wyj26 with SMTP id 26so725570wyj.31 for <renum@ietf.org>; Wed, 20 Jul 2011 23:49:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=CWJRaV/J9UO+inxl3Tfpw+vn8lkdVd8oFKuUYEXkpiw=; b=gbwuOd4FHn8gjJv7+bkcgiLXALw26pftmZODZKa+OY+5wsVUA9xWx26EOg2TtoqlUk z1Viq2bquDQKq2aZxQBbLQ2P6QFnlL2+9FDiQIs95A4YIq5wsQQisox+MoZpYH3ob4xy erIuun5S+UGl8ECaylwbRRV6NbLEkcSPPe8S4=
MIME-Version: 1.0
Received: by 10.227.198.142 with SMTP id eo14mr8270484wbb.113.1311230981342; Wed, 20 Jul 2011 23:49:41 -0700 (PDT)
Received: by 10.227.155.197 with HTTP; Wed, 20 Jul 2011 23:49:41 -0700 (PDT)
In-Reply-To: <4E2747C8.7070600@gmail.com>
References: <34E4F50CAFA10349A41E0756550084FB0B61DE55@PRVPEXVS04.corp.twcable.com> <5D36713D8A4E7348A7E10DF7437A4B920121835D@SZXEML506-MBX.china.huawei.com> <34E4F50CAFA10349A41E0756550084FB0B61DFFB@PRVPEXVS04.corp.twcable.com> <4E2747C8.7070600@gmail.com>
Date: Thu, 21 Jul 2011 08:49:41 +0200
Message-ID: <CAKFn1SGeaz2zEw1_2NXrGEHBfwv0L8TVOLa42pspsiBMSgXqTg@mail.gmail.com>
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] scoping question - how to define Enterprise in the context of 6renum?
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 06:49:48 -0000

On Wed, Jul 20, 2011 at 11:25 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
<snip>
> Anyway - I agree that there is certainly a need to define crisply what
> "enterprise network" means to us. We could look at RFC 4057:
>
> =A0"Enterprise Network - A network that has multiple internal links, one
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0or more router connections=
 to one or more
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Providers, and is actively=
 managed by a network
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0operations entity.
>
> =A0 Provider =A0 =A0 =A0 =A0 =A0 - An entity that provides services and
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0connectivity to the Intern=
et or other private
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0external networks for the =
enterprise network."

atleast in my head an ISP is a network build for transporting data
between several edges and toward many uplinks (peers/IXs). Very few
rules on what is allowed or not.
An enterprise network on the other hand is "closer" to the end user
(client). Enterprise networks have many clients on many LANs that they
interconnected, and then they have few uplinks out of their network.
And also enterprise can be considered a semi-closed network protected
by firewall that only allow some traffic outbound and little incoming.

LAN centric vs transport centric?


--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From jiangsheng@huawei.com  Thu Jul 21 01:01:31 2011
Return-Path: <jiangsheng@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D928421F8563 for <renum@ietfa.amsl.com>; Thu, 21 Jul 2011 01:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.345
X-Spam-Level: 
X-Spam-Status: No, score=-5.345 tagged_above=-999 required=5 tests=[AWL=1.253,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dvDdl8Mo4egv for <renum@ietfa.amsl.com>; Thu, 21 Jul 2011 01:01:30 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id B347221F856A for <renum@ietf.org>; Thu, 21 Jul 2011 01:01:29 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOO002D7BJD23@szxga04-in.huawei.com> for renum@ietf.org; Thu, 21 Jul 2011 15:59:37 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LOO00MXPBJD8J@szxga04-in.huawei.com> for renum@ietf.org; Thu, 21 Jul 2011 15:59:37 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml208-edg.china.huawei.com) ([172.24.2.119])	by szxrg01-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ACT30367; Thu, 21 Jul 2011 15:59:36 +0800 (CST)
Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 21 Jul 2011 15:59:30 +0800
Received: from SZXEML506-MBX.china.huawei.com ([169.254.4.221]) by szxeml408-hub.china.huawei.com ([169.254.27.188]) with mapi id 14.01.0270.001; Thu, 21 Jul 2011 15:59:35 +0800
Date: Thu, 21 Jul 2011 07:59:34 +0000
From: Jiangsheng <jiangsheng@huawei.com>
In-reply-to: <34E4F50CAFA10349A41E0756550084FB0B61DFE7@PRVPEXVS04.corp.twcable.com>
X-Originating-IP: [10.110.98.101]
To: "George, Wesley" <wesley.george@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Message-id: <5D36713D8A4E7348A7E10DF7437A4B9201218A2A@SZXEML506-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_+qxEDQbyxuCNs0Wn2GogCQ)"
Content-language: zh-CN
Accept-Language: en-GB, zh-CN, en-US
Thread-topic: comments on draft-jiang-6renum-enterprise-00
Thread-index: AcxGTCbF/pU0ChUVQXa10ceAEcTaeQAPYnLwABOcZRAAJsbv0A==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <34E4F50CAFA10349A41E0756550084FB0B61DE3B@PRVPEXVS04.corp.twcable.com> <5D36713D8A4E7348A7E10DF7437A4B92012182EA@SZXEML506-MBX.china.huawei.com> <34E4F50CAFA10349A41E0756550084FB0B61DFE7@PRVPEXVS04.corp.twcable.com>
Subject: Re: [renum] comments on draft-jiang-6renum-enterprise-00
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2011 08:01:32 -0000

--Boundary_(ID_+qxEDQbyxuCNs0Wn2GogCQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

3- I would recommend reviewing and categorizing the renumbering reasons in RFC2071 specifically in a subsequent revision, rather than your current generalization that some are out of date/not suitable. For that matter, should this document formally update RFC2071?

<Sheng> We could adopt the style of RFC2071, but many of their reasons are out of date. Could you point out what our current generalization are not suitable so that we can change it in next version? Thanks.


WEG> My problem is with "Some of renumbering reasons
   described in [RFC2071<http://tools.ietf.org/html/rfc2071>] has out of date, or not suitable in IPv6, or
   not suitable for enterprise networks."

Specifically, I have issue with the reference to 2071 and then the general statement "some ... out of date/not suitable" without specifying which are still acceptable, which are out of date/not suitable. "Some" is unclear/overly general by itself. If they are all unsuitable, make it clear that this is meant to replace those definitions as they are all unsuitable, and therefore list 2071 as being formally updated by this draft.

<Sheng> Oops... Misunderstood earlier. We can analyze current available renumbering reasons more in details. But we are hesitating to mention these out of date reasons, which may not help. I guess the best we can do, is to state: we input renumbering reasons from RFC2071 if they are not out of data and still suitable in IPv6. On other side, we are not sure this could be update of 2071 because some reasons may be still suitable in IPv4, We only rule them out by our scope.

________________________________
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.

--Boundary_(ID_+qxEDQbyxuCNs0Wn2GogCQ)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLChar
	{mso-style-name:"HTML \9884\8BBE\683C\5F0F Char";
	mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<p class=3D"MsoNormal"><span lang=3D"EN-US">3- I would recommend reviewing =
and categorizing the renumbering reasons in RFC2071 specifically in a subse=
quent revision, rather than your current generalization that some are out o=
f date/not suitable. For that matter,
 should this document formally update RFC2071?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&lt;She=
ng&gt; We could adopt the style of RFC2071, but many of their reasons are o=
ut of date. Could you point out what our current generalization are not sui=
table so that we can change it in next version?
 Thanks.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<pre style=3D"page-break-before:always"><span lang=3D"EN-US" style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#0=
F243E">WEG&gt; My problem is with</span><span lang=3D"EN-US" style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"> &#8220;</=
span><span lang=3D"EN-US" style=3D"font-size:12.0pt;color:black">Some of re=
numbering reasons<o:p></o:p></span></pre>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN-=
US" style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;;color:bla=
ck">&nbsp;&nbsp; described in [<a href=3D"http://tools.ietf.org/html/rfc207=
1" title=3D"&quot;Network Renumbering Overview: Why would I want it and wha=
t is it anyway?&quot;">RFC2071</a>]
 has out of date, or not suitable in IPv6, or<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span lang=3D"EN-=
US" style=3D"font-size:12.0pt;font-family:&quot;Courier New&quot;;color:bla=
ck">&nbsp;&nbsp; not suitable for enterprise networks.&#8221;<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#0F243E">Specifi=
cally, I have issue with the reference to 2071 and then the general stateme=
nt &#8220;some &#8230; out of date/not suitable&#8221; without specifying w=
hich are still acceptable, which are out of date/not suitable.
 &#8220;Some&#8221; is unclear/overly general by itself. If they are all un=
suitable, make it clear that this is meant to replace those definitions as =
they are all unsuitable, and therefore list 2071 as being formally updated =
by this draft.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&lt;She=
ng&gt; Oops&#8230; Misunderstood earlier. We can analyze current available =
renumbering reasons more in details. But we are hesitating to mention these=
 out of date reasons, which may not help. I guess
 the best we can do, is to state: we input renumbering reasons from RFC2071=
 if they are not out of data and still suitable in IPv6. On other side, we =
are not sure this could be update of 2071 because some reasons may be still=
 suitable in IPv4, We only rule
 them out by our scope.<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-=
family:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman=
&quot;,&quot;serif&quot;">
<hr size=3D"3" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:7.5pt;font-f=
amily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:gray">This E-mail and =
any of its attachments may contain Time Warner Cable proprietary informatio=
n, which is privileged, confidential, or subject to copyright
 belonging to Time Warner Cable. This E-mail is intended solely for the use=
 of the individual or entity to which it is addressed. If you are not the i=
ntended recipient of this E-mail, you are hereby notified that any dissemin=
ation, distribution, copying, or
 action taken in relation to the contents of and attachments to this E-mail=
 is strictly prohibited and may be unlawful. If you have received this E-ma=
il in error, please notify the sender immediately and permanently delete th=
e original and any copy of this
 E-mail and any printout.</span><span lang=3D"EN-US" style=3D"font-size:12.=
0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p><=
/span></p>
</div>
</div>
</body>
</html>

--Boundary_(ID_+qxEDQbyxuCNs0Wn2GogCQ)--

From wesley.george@twcable.com  Sun Jul 24 11:27:10 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5507121F8AD3 for <renum@ietfa.amsl.com>; Sun, 24 Jul 2011 11:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.063
X-Spam-Level: *
X-Spam-Status: No, score=1.063 tagged_above=-999 required=5 tests=[AWL=-1.075,  BAYES_50=0.001, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yq5+L+pmyWVc for <renum@ietfa.amsl.com>; Sun, 24 Jul 2011 11:27:10 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id CB7DD21F85FF for <renum@ietf.org>; Sun, 24 Jul 2011 11:27:09 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,257,1309752000";  d="scan'208,217";a="253292420"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 24 Jul 2011 14:25:17 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.29]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Sun, 24 Jul 2011 14:27:09 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: "renum@ietf.org" <renum@ietf.org>
Date: Sun, 24 Jul 2011 14:27:08 -0400
Thread-Topic: Minute taker and  Jabber scribe
Thread-Index: AcxKGvhGvDoBcIpKTSurULdDPSVfHw==
Message-ID: <34E4F50CAFA10349A41E0756550084FB0BBE73AD@PRVPEXVS04.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_34E4F50CAFA10349A41E0756550084FB0BBE73ADPRVPEXVS04corpt_"
MIME-Version: 1.0
Subject: [renum] Minute taker and  Jabber scribe
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jul 2011 18:27:10 -0000

--_000_34E4F50CAFA10349A41E0756550084FB0BBE73ADPRVPEXVS04corpt_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Need volunteers for both for the meeting

Thanks,

Wes and Tim



________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

--_000_34E4F50CAFA10349A41E0756550084FB0BBE73ADPRVPEXVS04corpt_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Need volunteers for both for the meeting<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Wes and Tim<span style=3D"color:#7F7F7F"><o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#7F7F7F"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>

--_000_34E4F50CAFA10349A41E0756550084FB0BBE73ADPRVPEXVS04corpt_--

From tjc@ecs.soton.ac.uk  Tue Jul 26 05:52:37 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE2DB21F8C66 for <renum@ietfa.amsl.com>; Tue, 26 Jul 2011 05:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8nOgAZLrsKsz for <renum@ietfa.amsl.com>; Tue, 26 Jul 2011 05:52:36 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 1910A21F8C52 for <renum@ietf.org>; Tue, 26 Jul 2011 05:52:35 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6QCqSLe021402 for <renum@ietf.org>; Tue, 26 Jul 2011 13:52:28 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p6QCqSLe021402
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1311684748; bh=If0jFAvtJMqWinjfqBgnOjo9OhA=; h=From:Subject:Date:To:Mime-Version:References; b=llyFYEfxMvBEBNsgYsAkYzaOzjb/eP/9ouPubtTF1uMbYsBVf+fyQCjgkj2NCXvRj /uKzmvwH3Oh/iIdVPciQWgMeNFBHa0yOkAO+GLfF+mmvWKUj4Or3Yegb9GKhn/RHbx ethgenW+Gon1sqbgIJQYNhtLGcd6yeYXB4Sy68gQ=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n6PDqS036613586163 ret-id none; Tue, 26 Jul 2011 13:52:28 +0100
Received: from [IPv6:2001:df8::112:95b0:87b5:ade3:c250] ([IPv6:2001:df8:0:112:95b0:87b5:ade3:c250]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p6QCqD67006464 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Tue, 26 Jul 2011 13:52:18 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 26 Jul 2011 13:52:13 +0100
Message-ID: <EMEW3|0547444d749d961d2c052ff40248d934n6PDqS03tjc|ecs.soton.ac.uk|0A782D18-2D46-4818-8476-5558CDC1CECF@ecs.soton.ac.uk>
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1244.3)
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n6PDqS036613586100; tid=n6PDqS036613586163; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
References: <0A782D18-2D46-4818-8476-5558CDC1CECF@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p6QCqSLe021402
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: [renum] IETF81 session information
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 12:52:37 -0000

Hi,

The tools-style page has all the Quebec meeting information available: =
drafts, slides, audio and jabber, see:

http://tools.ietf.org/wg/6renum/agenda?item=3Dagenda81.html

The session is 15:10 on Wednesday.

Tim=
