
From internet-drafts@ietf.org  Mon Sep  3 19:16:12 2012
Return-Path: <internet-drafts@ietf.org>
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 2D84621F8648; Mon,  3 Sep 2012 19:16:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.867
X-Spam-Level: 
X-Spam-Status: No, score=-99.867 tagged_above=-999 required=5 tests=[AWL=0.133, 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 Monl04YhxU4p; Mon,  3 Sep 2012 19:16:11 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B484521F8629; Mon,  3 Sep 2012 19:16:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120904021611.3518.72892.idtracker@ietfa.amsl.com>
Date: Mon, 03 Sep 2012 19:16:11 -0700
Cc: renum@ietf.org
Subject: [renum] I-D Action: draft-ietf-6renum-enterprise-02.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, 04 Sep 2012 02:16:12 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Site Renumbering Working Group of th=
e IETF.

	Title           : IPv6 Enterprise Network Renumbering Scenarios and Guidel=
ines
	Author(s)       : Sheng Jiang
                          Bing Liu
                          Brian Carpenter
	Filename        : draft-ietf-6renum-enterprise-02.txt
	Pages           : 16
	Date            : 2012-09-03

Abstract:
   This document analyzes enterprise renumbering events and describes
   the best current practice among the existing renumbering mechanisms.
   According to the different stages of renumbering events,
   considerations and best current practices are described in three
   categories: during network design, for preparation of renumbering,
   and during a renumbering operation.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6renum-enterprise-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-enterprise-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From internet-drafts@ietf.org  Mon Sep  3 20:37:58 2012
Return-Path: <internet-drafts@ietf.org>
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 B67FC21F8645; Mon,  3 Sep 2012 20:37:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.2
X-Spam-Level: 
X-Spam-Status: No, score=-101.2 tagged_above=-999 required=5 tests=[AWL=1.399,  BAYES_00=-2.599, 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 ofLmdp4kBsE8; Mon,  3 Sep 2012 20:37:58 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5828421F8499; Mon,  3 Sep 2012 20:37:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120904033758.18836.26105.idtracker@ietfa.amsl.com>
Date: Mon, 03 Sep 2012 20:37:58 -0700
Cc: renum@ietf.org
Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.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, 04 Sep 2012 03:37:58 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Site Renumbering Working Group of th=
e IETF.

	Title           : IPv6 Site Renumbering Gap Analysis
	Author(s)       : Bing Liu
                          Sheng Jiang
                          Brian Carpenter
                          Stig Venaas
	Filename        : draft-ietf-6renum-gap-analysis-03.txt
	Pages           : 20
	Date            : 2012-09-03

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




The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-03


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From jiangsheng@huawei.com  Mon Sep  3 20:44:22 2012
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 AA4BE21F84D3; Mon,  3 Sep 2012 20:44:22 -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 B8Imz+dGvxIC; Mon,  3 Sep 2012 20:44:22 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 631BB21F84C2; Mon,  3 Sep 2012 20:44:21 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AJH98787; Tue, 04 Sep 2012 03:44:18 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 4 Sep 2012 04:43:35 +0100
Received: from SZXEML415-HUB.china.huawei.com (10.82.67.154) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 4 Sep 2012 04:44:17 +0100
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.98]) by szxeml415-hub.china.huawei.com ([10.82.67.154]) with mapi id 14.01.0323.003; Tue, 4 Sep 2012 11:44:12 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "internet-drafts@ietf.org" <internet-drafts@ietf.org>, "i-d-announce@ietf.org" <i-d-announce@ietf.org>
Thread-Topic: [renum] I-D Action: draft-ietf-6renum-enterprise-02.txt
Thread-Index: AQHNikNV7fB46Bd+10acMJUwfliwEJd5igUA
Date: Tue, 4 Sep 2012 03:44:11 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B9239F3938C@szxeml545-mbx.china.huawei.com>
References: <20120904021611.3518.72892.idtracker@ietfa.amsl.com>
In-Reply-To: <20120904021611.3518.72892.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.31]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-02.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, 04 Sep 2012 03:44:22 -0000

QSBuZXcgdmVyc2lvbiB3aXRoIG1pbm9yIGVkaXRvcmlhbCBtb2RpZmljYXRpb25zIGFyZSBzdWJt
aXR0ZWQuIFlvdXIgcmV2aWV3IGFuZCBjb21tZW50cyBhcmUgYXBwcmVjaWF0ZWQuDQoNCkJlc3Qg
cmVnYXJkcywNCg0KU2hlbmcNCg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTog
cmVudW0tYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnJlbnVtLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZg0KPk9mIGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZw0KPlNlbnQ6IFR1ZXNkYXksIFNl
cHRlbWJlciAwNCwgMjAxMiAxMDoxNiBBTQ0KPlRvOiBpLWQtYW5ub3VuY2VAaWV0Zi5vcmcNCj5D
YzogcmVudW1AaWV0Zi5vcmcNCj5TdWJqZWN0OiBbcmVudW1dIEktRCBBY3Rpb246IGRyYWZ0LWll
dGYtNnJlbnVtLWVudGVycHJpc2UtMDIudHh0DQo+DQo+DQo+QSBOZXcgSW50ZXJuZXQtRHJhZnQg
aXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50ZXJuZXQtRHJhZnRzIGRpcmVjdG9yaWVz
Lg0KPiBUaGlzIGRyYWZ0IGlzIGEgd29yayBpdGVtIG9mIHRoZSBJUHY2IFNpdGUgUmVudW1iZXJp
bmcgV29ya2luZyBHcm91cCBvZiB0aGUNCj5JRVRGLg0KPg0KPglUaXRsZSAgICAgICAgICAgOiBJ
UHY2IEVudGVycHJpc2UgTmV0d29yayBSZW51bWJlcmluZyBTY2VuYXJpb3MgYW5kDQo+R3VpZGVs
aW5lcw0KPglBdXRob3IocykgICAgICAgOiBTaGVuZyBKaWFuZw0KPiAgICAgICAgICAgICAgICAg
ICAgICAgICAgQmluZyBMaXUNCj4gICAgICAgICAgICAgICAgICAgICAgICAgIEJyaWFuIENhcnBl
bnRlcg0KPglGaWxlbmFtZSAgICAgICAgOiBkcmFmdC1pZXRmLTZyZW51bS1lbnRlcnByaXNlLTAy
LnR4dA0KPglQYWdlcyAgICAgICAgICAgOiAxNg0KPglEYXRlICAgICAgICAgICAgOiAyMDEyLTA5
LTAzDQo+DQo+QWJzdHJhY3Q6DQo+ICAgVGhpcyBkb2N1bWVudCBhbmFseXplcyBlbnRlcnByaXNl
IHJlbnVtYmVyaW5nIGV2ZW50cyBhbmQgZGVzY3JpYmVzDQo+ICAgdGhlIGJlc3QgY3VycmVudCBw
cmFjdGljZSBhbW9uZyB0aGUgZXhpc3RpbmcgcmVudW1iZXJpbmcgbWVjaGFuaXNtcy4NCj4gICBB
Y2NvcmRpbmcgdG8gdGhlIGRpZmZlcmVudCBzdGFnZXMgb2YgcmVudW1iZXJpbmcgZXZlbnRzLA0K
PiAgIGNvbnNpZGVyYXRpb25zIGFuZCBiZXN0IGN1cnJlbnQgcHJhY3RpY2VzIGFyZSBkZXNjcmli
ZWQgaW4gdGhyZWUNCj4gICBjYXRlZ29yaWVzOiBkdXJpbmcgbmV0d29yayBkZXNpZ24sIGZvciBw
cmVwYXJhdGlvbiBvZiByZW51bWJlcmluZywNCj4gICBhbmQgZHVyaW5nIGEgcmVudW1iZXJpbmcg
b3BlcmF0aW9uLg0KPg0KPg0KPlRoZSBJRVRGIGRhdGF0cmFja2VyIHN0YXR1cyBwYWdlIGZvciB0
aGlzIGRyYWZ0IGlzOg0KPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWll
dGYtNnJlbnVtLWVudGVycHJpc2UNCj4NCj5UaGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9u
IGF2YWlsYWJsZSBhdDoNCj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLTZy
ZW51bS1lbnRlcnByaXNlLTAyDQo+DQo+QSBkaWZmIGZyb20gdGhlIHByZXZpb3VzIHZlcnNpb24g
aXMgYXZhaWxhYmxlIGF0Og0KPmh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0
LWlldGYtNnJlbnVtLWVudGVycHJpc2UtMDINCj4NCj4NCj5JbnRlcm5ldC1EcmFmdHMgYXJlIGFs
c28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQo+ZnRwOi8vZnRwLmlldGYub3JnL2lu
dGVybmV0LWRyYWZ0cy8NCj4NCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPnJlbnVtIG1haWxpbmcgbGlzdA0KPnJlbnVtQGlldGYub3JnDQo+aHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yZW51bQ0K

From jiangsheng@huawei.com  Mon Sep  3 20:44:41 2012
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 DB86521F863B; Mon,  3 Sep 2012 20:44:41 -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 LjqfJGg9g59X; Mon,  3 Sep 2012 20:44:41 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9F23B21F84C2; Mon,  3 Sep 2012 20:44:40 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AJH98819; Tue, 04 Sep 2012 03:44:39 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 4 Sep 2012 04:43:37 +0100
Received: from SZXEML424-HUB.china.huawei.com (10.82.67.163) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 4 Sep 2012 04:44:23 +0100
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.98]) by szxeml424-hub.china.huawei.com ([10.82.67.163]) with mapi id 14.01.0323.003; Tue, 4 Sep 2012 11:44:19 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "internet-drafts@ietf.org" <internet-drafts@ietf.org>, "i-d-announce@ietf.org" <i-d-announce@ietf.org>
Thread-Topic: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: AQHNik7MXZLBrDRvQ0yub4oo6oOK/Jd5inrA
Date: Tue, 4 Sep 2012 03:44:18 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B9239F3A393@szxeml545-mbx.china.huawei.com>
References: <20120904033758.18836.26105.idtracker@ietfa.amsl.com>
In-Reply-To: <20120904033758.18836.26105.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.31]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.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, 04 Sep 2012 03:44:42 -0000

QSBuZXcgdmVyc2lvbiB3aXRoIG1pbm9yIGVkaXRvcmlhbCBtb2RpZmljYXRpb25zIGFyZSBzdWJt
aXR0ZWQuIFlvdXIgcmV2aWV3IGFuZCBjb21tZW50cyBhcmUgYXBwcmVjaWF0ZWQuDQoNCkJlc3Qg
cmVnYXJkcywNCg0KU2hlbmcNCg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTog
cmVudW0tYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnJlbnVtLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZg0KPk9mIGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZw0KPlNlbnQ6IFR1ZXNkYXksIFNl
cHRlbWJlciAwNCwgMjAxMiAxMTozOCBBTQ0KPlRvOiBpLWQtYW5ub3VuY2VAaWV0Zi5vcmcNCj5D
YzogcmVudW1AaWV0Zi5vcmcNCj5TdWJqZWN0OiBbcmVudW1dIEktRCBBY3Rpb246IGRyYWZ0LWll
dGYtNnJlbnVtLWdhcC1hbmFseXNpcy0wMy50eHQNCj4NCj4NCj5BIE5ldyBJbnRlcm5ldC1EcmFm
dCBpcyBhdmFpbGFibGUgZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMgZGlyZWN0b3Jp
ZXMuDQo+IFRoaXMgZHJhZnQgaXMgYSB3b3JrIGl0ZW0gb2YgdGhlIElQdjYgU2l0ZSBSZW51bWJl
cmluZyBXb3JraW5nIEdyb3VwIG9mIHRoZQ0KPklFVEYuDQo+DQo+CVRpdGxlICAgICAgICAgICA6
IElQdjYgU2l0ZSBSZW51bWJlcmluZyBHYXAgQW5hbHlzaXMNCj4JQXV0aG9yKHMpICAgICAgIDog
QmluZyBMaXUNCj4gICAgICAgICAgICAgICAgICAgICAgICAgIFNoZW5nIEppYW5nDQo+ICAgICAg
ICAgICAgICAgICAgICAgICAgICBCcmlhbiBDYXJwZW50ZXINCj4gICAgICAgICAgICAgICAgICAg
ICAgICAgIFN0aWcgVmVuYWFzDQo+CUZpbGVuYW1lICAgICAgICA6IGRyYWZ0LWlldGYtNnJlbnVt
LWdhcC1hbmFseXNpcy0wMy50eHQNCj4JUGFnZXMgICAgICAgICAgIDogMjANCj4JRGF0ZSAgICAg
ICAgICAgIDogMjAxMi0wOS0wMw0KPg0KPkFic3RyYWN0Og0KPiAgIFRoaXMgZG9jdW1lbnQgYnJp
ZWZseSBpbnRyb2R1Y2VzIHRoZSBleGlzdGluZyBtZWNoYW5pc21zIGNvdWxkIGJlDQo+ICAgdXRp
bGl6ZWQgYnkgSVB2NiBzaXRlIHJlbnVtYmVyaW5nIGFuZCB0cmllcyB0byBjb3ZlciBtb3N0IG9m
IHRoZQ0KPiAgIGV4cGxpY2l0IGlzc3VlcyBhbmQgcmVxdWlyZW1lbnRzIG9mIElQdjYgcmVudW1i
ZXJpbmcuIFRocm91Z2ggdGhlIGdhcA0KPiAgIGFuYWx5c2lzLCB0aGUgZG9jdW1lbnQgcHJvdmlk
ZXMgYSBiYXNpcyBmb3IgZnV0dXJlIHdvcmtzIHRoYXQNCj4gICBpZGVudGlmeSBhbmQgZGV2ZWxv
cCBzb2x1dGlvbnMgb3IgdG8gc3RpbXVsYXRlIHN1Y2ggZGV2ZWxvcG1lbnQgYXMNCj4gICBhcHBy
b3ByaWF0ZS4gVGhlIGdhcCBhbmFseXNpcyBpcyBwcmVzZW50ZWQgZm9sbG93aW5nIGEgcmVudW1i
ZXJpbmcNCj4gICBldmVudCBwcm9jZWR1cmUgY2x1ZS4NCj4NCj4NCj4NCj4NCj5UaGUgSUVURiBk
YXRhdHJhY2tlciBzdGF0dXMgcGFnZSBmb3IgdGhpcyBkcmFmdCBpczoNCj5odHRwczovL2RhdGF0
cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLTZyZW51bS1nYXAtYW5hbHlzaXMNCj4NCj5U
aGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBhdDoNCj5odHRwOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLTZyZW51bS1nYXAtYW5hbHlzaXMtMDMNCj4NCj5B
IGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUgYXQ6DQo+aHR0cDov
L3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaWV0Zi02cmVudW0tZ2FwLWFuYWx5c2lz
LTAzDQo+DQo+DQo+SW50ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1v
dXMgRlRQIGF0Og0KPmZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvDQo+DQo+X19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5yZW51bSBtYWls
aW5nIGxpc3QNCj5yZW51bUBpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vcmVudW0NCg==

From lee.howard@twcable.com  Thu Sep  6 09:19:29 2012
Return-Path: <lee.howard@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 AF50821F866D for <renum@ietfa.amsl.com>; Thu,  6 Sep 2012 09:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 8abCyAQVacGO for <renum@ietfa.amsl.com>; Thu,  6 Sep 2012 09:19:28 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 9E69E21F8674 for <renum@ietf.org>; Thu,  6 Sep 2012 09:19:28 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,380,1344225600"; d="scan'208";a="416762633"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 06 Sep 2012 12:18:51 -0400
Received: from PRVPEXVS17.corp.twcable.com ([10.136.163.95]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Thu, 6 Sep 2012 12:19:26 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: "renum@ietf.org" <renum@ietf.org>
Date: Thu, 6 Sep 2012 12:19:25 -0400
Thread-Topic: Working Group Last Call: draft-ietf-6renum-enterprise-02.txt
Thread-Index: Ac2MS1AyGfCtBCmORjqQzps1UhuJbg==
Message-ID: <99B887114EDB1449941CFBC8EC279FA12CB43E15@PRVPEXVS17.corp.twcable.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] Working Group Last Call: draft-ietf-6renum-enterprise-02.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, 06 Sep 2012 16:19:29 -0000

We are requesting a Working Group Last Call on this document.  Please revie=
w and provide comments before September 19, since this may be the final rev=
iew of this document.

Thanks,

Lee


> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of
Sheng Jiang
> Sent: Monday, September 03, 2012 11:44 PM
> To: internet-drafts@ietf.org; i-d-announce@ietf.org
> Cc: renum@ietf.org
> Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-02.txt
>
> A new version with minor editorial modifications are submitted. Your
review and comments
> are appreciated.
>
> Best regards,
>
> Sheng
>
> >-----Original Message-----
> >From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On
> >Behalf Of internet-drafts@ietf.org
> >Sent: Tuesday, September 04, 2012 10:16 AM
> >To: i-d-announce@ietf.org
> >Cc: renum@ietf.org
> >Subject: [renum] I-D Action: draft-ietf-6renum-enterprise-02.txt
> >
> >
> >A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> > This draft is a work item of the IPv6 Site Renumbering Working Group
> >of the IETF.
> >
> >     Title           : IPv6 Enterprise Network Renumbering Scenarios and
> >Guidelines
> >     Author(s)       : Sheng Jiang
> >                          Bing Liu
> >                          Brian Carpenter
> >     Filename        : draft-ietf-6renum-enterprise-02.txt
> >     Pages           : 16
> >     Date            : 2012-09-03
> >
> >Abstract:
> >   This document analyzes enterprise renumbering events and describes
> >   the best current practice among the existing renumbering mechanisms.
> >   According to the different stages of renumbering events,
> >   considerations and best current practices are described in three
> >   categories: during network design, for preparation of renumbering,
> >   and during a renumbering operation.
> >
> >
> >The IETF datatracker status page for this draft is:
> >https://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise
> >
> >There's also a htmlized version available at:
> >http://tools.ietf.org/html/draft-ietf-6renum-enterprise-02
> >
> >A diff from the previous version is available at:
> >http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-enterprise-02
> >
> >
> >Internet-Drafts are also available by anonymous FTP at:
> >ftp://ftp.ietf.org/internet-drafts/
> >
> >_______________________________________________
> >renum mailing list
> >renum@ietf.org
> >https://www.ietf.org/mailman/listinfo/renum
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum


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.

From lee.howard@twcable.com  Thu Sep  6 09:22:12 2012
Return-Path: <lee.howard@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 E2BCB21F86C4 for <renum@ietfa.amsl.com>; Thu,  6 Sep 2012 09:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.963
X-Spam-Level: 
X-Spam-Status: No, score=-0.963 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 UdrkcK5Hl4rP for <renum@ietfa.amsl.com>; Thu,  6 Sep 2012 09:22:12 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 4E64121F86B0 for <renum@ietf.org>; Thu,  6 Sep 2012 09:22:12 -0700 (PDT)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,380,1344225600"; d="scan'208";a="434771169"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 06 Sep 2012 12:17:20 -0400
Received: from PRVPEXVS17.corp.twcable.com ([10.136.163.95]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Thu, 6 Sep 2012 12:17:44 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: "renum@ietf.org" <renum@ietf.org>
Date: Thu, 6 Sep 2012 12:17:43 -0400
Thread-Topic: Working Group Last Call: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: Ac2MSv8ivRG0vUeJSx+uTzY+jOkLiw==
Message-ID: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.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] Working Group Last Call: draft-ietf-6renum-gap-analysis-03.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, 06 Sep 2012 16:22:13 -0000

We are requesting a Working Group Last Call on this document.  Please revie=
w and provide comments before September 19, since this may be the final rev=
iew of this document.

Thanks,

Lee


> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of internet- drafts@ietf.org
> Sent: Monday, September 03, 2012 11:38 PM
> To: i-d-announce@ietf.org
> Cc: renum@ietf.org
> Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the IPv6 Site Renumbering Working Group of =
the IETF.
>
>       Title           : IPv6 Site Renumbering Gap Analysis
>       Author(s)       : Bing Liu
>                           Sheng Jiang
>                           Brian Carpenter
>                           Stig Venaas
>       Filename        : draft-ietf-6renum-gap-analysis-03.txt
>       Pages           : 20
>       Date            : 2012-09-03
>
> Abstract:
>    This document briefly introduces the existing mechanisms could be
>    utilized by IPv6 site renumbering and tries to cover most of the
>    explicit issues and requirements of IPv6 renumbering. Through the gap
>    analysis, the document provides a basis for future works that
>    identify and develop solutions or to stimulate such development as
>    appropriate. The gap analysis is presented following a renumbering
>    event procedure clue.
>
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-03
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

Lee Howard
Director, Network Technology
Time Warner Cable
(703) 345-3513
13820 Sunrise Valley Drive, Herndon VA 20171



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.

From eleven.fuyu@huawei.com  Tue Sep 11 19:01:31 2012
Return-Path: <eleven.fuyu@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 9EC0321F8550 for <renum@ietfa.amsl.com>; Tue, 11 Sep 2012 19:01:31 -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 rjS2v1Ib12AS for <renum@ietfa.amsl.com>; Tue, 11 Sep 2012 19:01:31 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id B296D21F8582 for <renum@ietf.org>; Tue, 11 Sep 2012 19:01:27 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AJO70279; Wed, 12 Sep 2012 02:01:25 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 12 Sep 2012 03:01:13 +0100
Received: from SZXEML425-HUB.china.huawei.com (10.72.61.33) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 12 Sep 2012 03:01:22 +0100
Received: from SZXEML512-MBX.china.huawei.com ([169.254.5.187]) by szxeml425-hub.china.huawei.com ([10.72.61.33]) with mapi id 14.01.0323.003; Wed, 12 Sep 2012 10:01:19 +0800
From: "Fuyu (Eleven)" <eleven.fuyu@huawei.com>
To: "Howard, Lee" <lee.howard@twcable.com>
Thread-Topic: [renum] Working Group Last Call: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: Ac2MSv8ivRG0vUeJSx+uTzY+jOkLiwDtjl6Q
Date: Wed, 12 Sep 2012 02:01:18 +0000
Message-ID: <EF6A204047BD994A860EE26D5F23BF582B8E1494@SZXEML512-MBX.china.huawei.com>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com>
In-Reply-To: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Working Group Last Call:	draft-ietf-6renum-gap-analysis-03.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, 12 Sep 2012 02:01:31 -0000

I am in favor of moving forward this work.

Cheers
Yu

-----Original Message-----
From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of H=
oward, Lee
Sent: Friday, September 07, 2012 12:18 AM
To: renum@ietf.org
Subject: [renum] Working Group Last Call: draft-ietf-6renum-gap-analysis-03=
.txt

We are requesting a Working Group Last Call on this document.  Please revie=
w and provide comments before September 19, since this may be the final rev=
iew of this document.

Thanks,

Lee


> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of internet- drafts@ietf.org
> Sent: Monday, September 03, 2012 11:38 PM
> To: i-d-announce@ietf.org
> Cc: renum@ietf.org
> Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the IPv6 Site Renumbering Working Group of =
the IETF.
>
>       Title           : IPv6 Site Renumbering Gap Analysis
>       Author(s)       : Bing Liu
>                           Sheng Jiang
>                           Brian Carpenter
>                           Stig Venaas
>       Filename        : draft-ietf-6renum-gap-analysis-03.txt
>       Pages           : 20
>       Date            : 2012-09-03
>
> Abstract:
>    This document briefly introduces the existing mechanisms could be
>    utilized by IPv6 site renumbering and tries to cover most of the
>    explicit issues and requirements of IPv6 renumbering. Through the gap
>    analysis, the document provides a basis for future works that
>    identify and develop solutions or to stimulate such development as
>    appropriate. The gap analysis is presented following a renumbering
>    event procedure clue.
>
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-03
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

Lee Howard
Director, Network Technology
Time Warner Cable
(703) 345-3513
13820 Sunrise Valley Drive, Herndon VA 20171



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.
_______________________________________________
renum mailing list
renum@ietf.org
https://www.ietf.org/mailman/listinfo/renum

From madi@cnnic.cn  Thu Sep 13 20:00:21 2012
Return-Path: <madi@cnnic.cn>
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 88B1721F863C for <renum@ietfa.amsl.com>; Thu, 13 Sep 2012 20:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.545
X-Spam-Level: 
X-Spam-Status: No, score=-0.545 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753]
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 SUPFJrSlG9OM for <renum@ietfa.amsl.com>; Thu, 13 Sep 2012 20:00:20 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id CA92221F8639 for <renum@ietf.org>; Thu, 13 Sep 2012 20:00:11 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: madi@cnnic.cn
Received: from unknown127.0.0.1 (HELO user-think) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 14 Sep 2012 11:00:07 +0800
Date: Fri, 14 Sep 2012 11:00:04 +0800
From: "Di Ma" <madi@cnnic.cn>
To: =?gb2312?B?va/KpA==?= <jiangsheng@huawei.com>
References: <20120904033758.18836.26105.idtracker@ietfa.amsl.com>,  <5D36713D8A4E7348A7E10DF7437A4B9239F3A393@szxeml545-mbx.china.huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.90[cn]
Mime-Version: 1.0
Message-ID: <201209141100044525538@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart172282378841_=----"
Cc: 6renum <renum@ietf.org>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: madi <madi@cnnic.cn>
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: Fri, 14 Sep 2012 03:00:21 -0000

This is a multi-part message in MIME format.

------=_001_NextPart172282378841_=----
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SSBhbSBpbiBmYXZvciBvZiBtb3ZpbmcgZm9yd2FyZCB0aGlzIHdvcmsuIA0KIA0KWWV0IGFzIGEg
ZG9jdW1lbnQgcHJvdmlkaW5nIGEgYmFzaXMgZm9yIGZ1dHVyZSB3b3JrcyB0aGF0IGlkZW50aWZ5
IGFuZCBkZXZlbG9wIHNvbHV0aW9ucyBvciB0byBzdGltdWxhdGUgc3VjaCBkZXZlbG9wbWVudCBh
cyBhcHByb3ByaWF0ZSwgdGhpcyBkcmFmdCBtaWdodCBtYWtlIElQU2VjIFNlY3VyaXR5IEFzc29j
aWF0aW9uIChTQSkgbWFuYWdlbWVudCBpbmNsdWRlZCwgY29uc2lkZXJpbmcgSVBTZWMgU0EgaXMg
YSBraW5kIG9mIElQIGFkZHJlc3Mgb3JpZW50ZWQgobBjb25uZWN0aW9uobEgdGhhdCBjYW5ub3Qg
ZnVuY3Rpb24gYWZ0ZXIgdGhlIGNoYW5nZSBvZiB0aGUgaW52b2x2ZWQgSVAgYWRkcmVzc2VzLCB3
aGljaCBtZWFucyBleHRyYSBjb25maWd1cmF0aW9uIG9mIFNBIHBhcmFtZXRlcnMgaXMgaW5ldml0
YWJsZSBhZnRlciBuZXR3b3JrIHJlbnVtYmVyaW5nLiANCiANClNvLCBJIHByb3Bvc2UgYWRkaW5n
IHNvbWUgd29yZHMgaW50byB0aGlzIGRyYWZ0IGFzIFNlY3Rpb24gOC4zIChJUFNlYyBTQSBNYW5h
Z2VtZW50KSwgYSBzZWN0b3Igb2YgU2VjdGlvbiA4IChNaXNjZWxsYW5lb3VzKSwgd2hpY2ggaXMg
ZGVzY3JpYmVkIGFzIGZvbGxvd3M6DQogDQpOZXR3b3JrIHJlbnVtYmVyaW5nIGV2ZW50cyBnZXQg
bmV0d29ya2luZyBtZWNoYW5pc21zIHRoYXQgYXJlIGJvdW5kIHRvIElQIGFkZHJlc3Nlcywgb3Ig
YXBwbGljYXRpb25zIHVzaW5nIHNwZWNpZmljIElQIGFkZHJlc3NlcywgaW52b2x2ZWQuIEFzIGRl
ZmluZWQgaW4gW1JGQzQzMDFdLCBJUFNlYyBTZWN1cml0eSBBc3NvY2lhdGlvbiAoU0EpLCBhcyBh
IGtpbmQgb2YgSVAgYWRkcmVzcyBvcmllbnRlZCChsGNvbm5lY3Rpb26hsSwgY2Fubm90IGZ1bmN0
aW9uIGFmdGVyIHRoZSBjaGFuZ2Ugb2YgdGhlIGludm9sdmVkIElQIGFkZHJlc3Nlcywgd2hpY2gg
bWVhbnMgZXh0cmEgY29uZmlndXJhdGlvbiBvZiBTQSBwYXJhbWV0ZXJzIGlzIGluZXZpdGFibGUg
YWZ0ZXIgbmV0d29yayByZW51bWJlcmluZy4gDQogDQpTQSBpcyBhIKGwY29ubmVjdGlvbqGxIHRo
YXQgcHJvdmlkZXMgc2VjdXJpdHkgc2VydmljZXMgdG8gdGhlIHRyYWZmaWMgY2FycmllZCBieSBp
dCBhbmQgZGV0YWlscyB0aGUga2V5IGFuZCBhbGdvcml0aG0gdGhhdCB0aGUgSVBTZWMgY29ubmVj
dGlvbiByZWxpZXMgb24uIFNBIGNhbiBiZSBlc3RhYmxpc2hlZCB3aXRoIG1hbnVhbCBjb25maWd1
cmF0aW9uIGJ5IHRoZSBhZG1pbmlzdHJhdG9yLiBJS0V2MiBbUkZDNTk5Nl0gZWxpbWluYXRlcyBt
YW51YWwgcmVjb25maWd1cmF0aW9uLiBJdCBlbXBsb3lzIHR3byByb3VuZHMgb2YgbWVzc2FnZSBl
eGNoYW5nZXMuIFRoZSBmaXJzdCBleGNoYW5nZSBvZiBtZXNzYWdlcyBlc3RhYmxpc2hlcyBhIHRy
dXN0IHJlbGF0aW9uc2hpcCBiZXR3ZWVuIHRoZSB0d28gSUtFdjIgcGFydGljaXBhbnRzLiBUaGlz
IGV4Y2hhbmdlIHVzZXMgdHdvIGF1dGhlbnRpY2F0aW9uIG1ldGhvZHMsIGRpZ2l0YWwgc2lnbmF0
dXJlIGFuZCBwcmUtc2hhcmVkIGtleS4gVGhlIGRpZ2l0YWwgc2lnbmF0dXJlIG1ldGhvZCBuZWVk
cyBjZXJ0aWZpY2F0ZSBtYW5hZ2VtZW50LiBJZiB0aGUgcGFydGljaXBhbnRzIGFyZSBub3QgY29u
ZmlndXJlZCB3aXRoIHRoZSBzYW1lIHRydXN0IGFuY2hvciwgY2VydGlmaWNhdGUtYmFzZWQgSUtF
djIgY2Fubm90IGJlIHJlYWxpemVkLiBXaGlsZSB0aGUgcHJlLXNoYXJlZCBrZXkgbWV0aG9kIGlz
IHRoZSBzaW1wbGVyIG9mIHRoZSBhdXRoZW50aWNhdGlvbiBtZXRob2RzIGZvciBJS0V2MiBhbmQg
cHJlLXNoYXJlZCBrZXlzIGFyZSB0aWVkIHRvIHBhcnRpY3VsYXIgSVAgYWRkcmVzc2VzLCB1bmxp
a2UgcHVibGljIGtleSBjZXJ0aWZpY2F0ZXMgdXNlZCBieSBkaWdpdGFsIHNpZ25hdHVyZSBtZXRo
b2QuIFByZS1zaGFyZWQga2V5IG1ldGhvZCBjYW5ub3QgYmUgdXNlZCB3aXRoIG1vYmlsZSBzeXN0
ZW1zIG9yIHN5c3RlbXMgdGhhdCBtYXkgYmUgcmVudW1iZXJlZCwgdW5sZXNzIHRoZSByZW51bWJl
cmluZyBpcyB3aXRoaW4gdGhlIHByZXZpb3VzbHkgZGV0ZXJtaW5lZCByYW5nZSBvZiBJUCBhZGRy
ZXNzZXMuIEFsc28sIHdoZW4gcHJlLXNoYXJlZCBrZXkgaXMgZW1wbG95ZWQsIElLRXYyIGNvbXB1
dGF0aW9ucyBjYW5ub3QgYmUgb2ZmbG9hZGVkIHRvIHRoZSBhdHRhY2hlZCBoYXJkd2FyZS4gVGhl
cmVmb3JlLCBwcmUtc2hhcmVkIGtleSBtZXRob2QgZmFpbHMgdG8gYmUgYSBwdXJlIGF1dG9tYXRp
YyBvbmUgYW5kIGRvZXMgbm90IGdvIHdlbGwgd2l0aCBuZXR3b3JrIHJlbnVtYmVyaW5nLiBBIG1l
Y2hhbmlzbSB0aGF0IGlzIGFibGUgdG8gaW50ZWdyYXRlIFNBIG1hbmFnZW1lbnQgaW50byBJUCBh
ZGRyZXNzIGFzc2lnbm1lbnQgaW4gYW4gYXV0b21hdGljIGFuZCBhbiBhZGFwdGl2ZSBtYW5uZXIg
aXMgZGVzaXJlZCB0byBnbyB3aXRoIG5ldHdvcmsgcmVudW1iZXJpbmcuDQoNCg0KDQoNCg0KRGkg
TWEgDQpDTk5JQyBBZHZhbmNlZCBSZXNlYXJjaCBEZXBhcnRtZW50DQpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkNoaW5hIEludGVybmV0IE5ldHdv
cmsgSW5mb3JtYXRpb24gQ2VudGVyDQpUZWw6ICg4NjEwKS01ODgxMzIxNg0KSHR0cHM6Ly93d3cu
Y25uaWMuY24NCkFkZDogNCwgU291dGggNHRoIFN0cmVldCwgWmhvbmdndWFuY3VuDQpIYWlkaWFu
IERpc3RyaWN0LCBCZWlqaW5nDQpQLlIuQ2hpbmEgMTAwMTkwDQpQT0I6IEJlaWppbmcgMzQ5LCBC
cmFuY2ggNg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KDQpGcm9tOiBTaGVuZyBKaWFuZw0KRGF0ZTogMjAxMi0wOS0wNCAxMTo0NA0KVG86IGlu
dGVybmV0LWRyYWZ0c0BpZXRmLm9yZzsgaS1kLWFubm91bmNlQGlldGYub3JnDQpDQzogcmVudW1A
aWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbcmVudW1dIEktRCBBY3Rpb246IGRyYWZ0LWlldGYtNnJl
bnVtLWdhcC1hbmFseXNpcy0wMy50eHQNCkEgbmV3IHZlcnNpb24gd2l0aCBtaW5vciBlZGl0b3Jp
YWwgbW9kaWZpY2F0aW9ucyBhcmUgc3VibWl0dGVkLiBZb3VyIHJldmlldyBhbmQgY29tbWVudHMg
YXJlIGFwcHJlY2lhdGVkLg0KDQpCZXN0IHJlZ2FyZHMsDQoNClNoZW5nDQoNCj4tLS0tLU9yaWdp
bmFsIE1lc3NhZ2UtLS0tLQ0KPkZyb206IHJlbnVtLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpy
ZW51bS1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYNCj5PZiBpbnRlcm5ldC1kcmFmdHNAaWV0
Zi5vcmcNCj5TZW50OiBUdWVzZGF5LCBTZXB0ZW1iZXIgMDQsIDIwMTIgMTE6MzggQU0NCj5Ubzog
aS1kLWFubm91bmNlQGlldGYub3JnDQo+Q2M6IHJlbnVtQGlldGYub3JnDQo+U3ViamVjdDogW3Jl
bnVtXSBJLUQgQWN0aW9uOiBkcmFmdC1pZXRmLTZyZW51bS1nYXAtYW5hbHlzaXMtMDMudHh0DQo+
DQo+DQo+QSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUg
SW50ZXJuZXQtRHJhZnRzIGRpcmVjdG9yaWVzLg0KPiBUaGlzIGRyYWZ0IGlzIGEgd29yayBpdGVt
IG9mIHRoZSBJUHY2IFNpdGUgUmVudW1iZXJpbmcgV29ya2luZyBHcm91cCBvZiB0aGUNCj5JRVRG
Lg0KPg0KPiBUaXRsZSAgICAgICAgICAgOiBJUHY2IFNpdGUgUmVudW1iZXJpbmcgR2FwIEFuYWx5
c2lzDQo+IEF1dGhvcihzKSAgICAgICA6IEJpbmcgTGl1DQo+ICAgICAgICAgICAgICAgICAgICAg
ICAgICBTaGVuZyBKaWFuZw0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgQnJpYW4gQ2FycGVu
dGVyDQo+ICAgICAgICAgICAgICAgICAgICAgICAgICBTdGlnIFZlbmFhcw0KPiBGaWxlbmFtZSAg
ICAgICAgOiBkcmFmdC1pZXRmLTZyZW51bS1nYXAtYW5hbHlzaXMtMDMudHh0DQo+IFBhZ2VzICAg
ICAgICAgICA6IDIwDQo+IERhdGUgICAgICAgICAgICA6IDIwMTItMDktMDMNCj4NCj5BYnN0cmFj
dDoNCj4gICBUaGlzIGRvY3VtZW50IGJyaWVmbHkgaW50cm9kdWNlcyB0aGUgZXhpc3RpbmcgbWVj
aGFuaXNtcyBjb3VsZCBiZQ0KPiAgIHV0aWxpemVkIGJ5IElQdjYgc2l0ZSByZW51bWJlcmluZyBh
bmQgdHJpZXMgdG8gY292ZXIgbW9zdCBvZiB0aGUNCj4gICBleHBsaWNpdCBpc3N1ZXMgYW5kIHJl
cXVpcmVtZW50cyBvZiBJUHY2IHJlbnVtYmVyaW5nLiBUaHJvdWdoIHRoZSBnYXANCj4gICBhbmFs
eXNpcywgdGhlIGRvY3VtZW50IHByb3ZpZGVzIGEgYmFzaXMgZm9yIGZ1dHVyZSB3b3JrcyB0aGF0
DQo+ICAgaWRlbnRpZnkgYW5kIGRldmVsb3Agc29sdXRpb25zIG9yIHRvIHN0aW11bGF0ZSBzdWNo
IGRldmVsb3BtZW50IGFzDQo+ICAgYXBwcm9wcmlhdGUuIFRoZSBnYXAgYW5hbHlzaXMgaXMgcHJl
c2VudGVkIGZvbGxvd2luZyBhIHJlbnVtYmVyaW5nDQo+ICAgZXZlbnQgcHJvY2VkdXJlIGNsdWUu
DQo+DQo+DQo+DQo+DQo+VGhlIElFVEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMg
ZHJhZnQgaXM6DQo+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi02
cmVudW0tZ2FwLWFuYWx5c2lzDQo+DQo+VGhlcmUncyBhbHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBh
dmFpbGFibGUgYXQ6DQo+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi02cmVu
dW0tZ2FwLWFuYWx5c2lzLTAzDQo+DQo+QSBkaWZmIGZyb20gdGhlIHByZXZpb3VzIHZlcnNpb24g
aXMgYXZhaWxhYmxlIGF0Og0KPmh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0
LWlldGYtNnJlbnVtLWdhcC1hbmFseXNpcy0wMw0KPg0KPg0KPkludGVybmV0LURyYWZ0cyBhcmUg
YWxzbyBhdmFpbGFibGUgYnkgYW5vbnltb3VzIEZUUCBhdDoNCj5mdHA6Ly9mdHAuaWV0Zi5vcmcv
aW50ZXJuZXQtZHJhZnRzLw0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQo+cmVudW0gbWFpbGluZyBsaXN0DQo+cmVudW1AaWV0Zi5vcmcNCj5odHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JlbnVtDQpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KcmVudW0gbWFpbGluZyBsaXN0DQpyZW51
bUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yZW51bQ==

------=_001_NextPart172282378841_=----
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3DGB2312" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: =CE=A2=C8=ED=D1=C5=BA=DA; COLOR: #000080; =
FONT-SIZE: 10.5pt
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 9.00.8112.16448"></HEAD>
<BODY style=3D"MARGIN: 10px">
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 11pt" lang=3DE=
N-US><FONT=20
color=3D#000000>I am in favor of moving forward this work. <?xml:namespace=
 prefix=20
=3D o ns =3D "urn:schemas-microsoft-com:office:office"=20
/><o:p></o:p></FONT></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 11pt"=20
lang=3DEN-US><o:p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 11pt"=20
lang=3DEN-US><o:p></o:p></SPAN><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 11pt" lang=3DE=
N-US><FONT=20
color=3D#000000>Yet as a document providing a basis for future works that =
identify=20
and develop solutions or to stimulate such development as appropriate, thi=
s=20
draft might make IPSec Security Association (SA) management included,=20
considering IPSec SA is a kind of IP address oriented =A1=B0connection=A1=
=B1 that cannot=20
function after the change of the involved IP addresses, which means extra=20
configuration of SA parameters is inevitable after network renumbering.=20
<o:p></o:p></FONT></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 11pt"=20
lang=3DEN-US><o:p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 11pt" lang=3DE=
N-US><FONT=20
color=3D#000000>So, I propose adding some words into this draft as Section=
 8.3=20
(IPSec SA Management), a sector of Section 8 (Miscellaneous), which is des=
cribed=20
as follows:<o:p></o:p></FONT></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 9pt" lang=3DEN-US><o:p><FONT c=
olor=3D#000000=20
face=3DCalibri>&nbsp;</FONT></o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><I style=3D"mso-bidi-font-style: normal"><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 11pt" lang=3DE=
N-US><FONT=20
color=3D#000000>Network renumbering events get networking mechanisms that =
are=20
bound to IP addresses, or applications using specific IP addresses, involv=
ed. As=20
defined in [RFC4301], IPSec Security Association (SA), as a kind of IP add=
ress=20
oriented =A1=B0connection=A1=B1, cannot function after the change of the i=
nvolved IP=20
addresses, which means extra configuration of SA parameters is inevitable =
after=20
network renumbering. <o:p></o:p></FONT></SPAN></I></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><I style=3D"mso-bidi-font-style: normal"><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 11pt"=20
lang=3DEN-US><o:p><FONT color=3D#000000>&nbsp;</FONT></o:p></SPAN></I></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><I style=3D"mso-bidi-font-style: normal"><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 11pt" lang=3DE=
N-US><FONT=20
color=3D#000000>SA is a =A1=B0connection=A1=B1 that provides security serv=
ices to the=20
traffic carried by it and details the key and algorithm that the IPSec=20
connection relies on. SA can be established with manual configuration by t=
he=20
administrator. IKEv2 [RFC5996] eliminates manual reconfiguration. It emplo=
ys two=20
rounds of message exchanges. The first exchange of messages establishes a =
trust=20
relationship between the two IKEv2 participants. This exchange uses two=20
authentication methods, digital signature and pre-shared key. The digital=20
signature method needs certificate management. If the participants are not=
=20
configured with the same trust anchor, certificate-based IKEv2 cannot be=20
realized. While the pre-shared key method is the simpler of the authentica=
tion=20
methods for IKEv2 and pre-shared keys are tied to particular IP addresses,=
=20
unlike public key certificates used by digital signature method. Pre-share=
d key=20
method cannot be used with mobile systems or systems that may be renumbere=
d,=20
unless the renumbering is within the previously determined range of IP=20
addresses. Also, when pre-shared key is employed, IKEv2 computations canno=
t be=20
offloaded to the attached hardware. Therefore, pre-shared key method fails=
 to be=20
a pure automatic one and does not go well with network renumbering. A mech=
anism=20
that is able to integrate SA management into IP address assignment in an=20
automatic and an adaptive manner is desired to go with network=20
renumbering.<o:p></o:p></FONT></SPAN></I></P><!--EndFragment-->
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>
</DIV>
<DIV><SPAN>
<DIV><SPAN style=3D"FONT-FAMILY: =CB=CE=CC=E5; COLOR: #000000; FONT-SIZE: =
10.5pt">
<DIV><FONT face=3D"Courier New"><FONT color=3D#0000ff>Di Ma</FONT> </FONT>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"></P>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff face=3D"Courier New">CNNIC Advanced Research=20
Department<BR>___________________________________________________</FONT></=
P>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff face=3D"Courier New">China Internet Network Information=20
Center<BR>Tel: (8610)-58813216<BR></FONT><FONT color=3D#0000ff=20
face=3D"Courier New">Https://www.cnnic.cn</FONT></P>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff face=3D"Courier New">Add: 4, South 4th Street,=20
Zhongguancun<BR>Haidian District, Beijing<BR>P.R.China 100190</FONT></P>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff><SPAN style=3D"FONT-FAMILY: Arial"><FONT size=3D2=20
face=3D"Courier New">POB: Beijing 349, Branch 6</FONT></SPAN><BR><FONT=20
face=3D"Courier New">____________________________________________________<=
/FONT></P></FONT></DIV></SPAN></DIV></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:jiangsheng@huawei.com">Sheng=20
Jiang</A></DIV>
<DIV><B>Date:</B>&nbsp;2012-09-04&nbsp;11:44</DIV>
<DIV><B>To:</B>&nbsp;<A=20
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</A>; <A=20
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A></DIV>
<DIV><B>CC:</B>&nbsp;<A href=3D"mailto:renum@ietf.org">renum@ietf.org</A><=
/DIV>
<DIV><B>Subject:</B>&nbsp;Re: [renum] I-D Action:=20
draft-ietf-6renum-gap-analysis-03.txt</DIV></DIV></DIV>
<DIV>
<DIV>A&nbsp;new&nbsp;version&nbsp;with&nbsp;minor&nbsp;editorial&nbsp;modi=
fications&nbsp;are&nbsp;submitted.&nbsp;Your&nbsp;review&nbsp;and&nbsp;com=
ments&nbsp;are&nbsp;appreciated.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Best&nbsp;regards,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Sheng</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;-----Original&nbsp;Message-----</DIV>
<DIV>&gt;From:&nbsp;renum-bounces@ietf.org&nbsp;[mailto:renum-bounces@ietf=
.org]&nbsp;On&nbsp;Behalf</DIV>
<DIV>&gt;Of&nbsp;internet-drafts@ietf.org</DIV>
<DIV>&gt;Sent:&nbsp;Tuesday,&nbsp;September&nbsp;04,&nbsp;2012&nbsp;11:38&=
nbsp;AM</DIV>
<DIV>&gt;To:&nbsp;i-d-announce@ietf.org</DIV>
<DIV>&gt;Cc:&nbsp;renum@ietf.org</DIV>
<DIV>&gt;Subject:&nbsp;[renum]&nbsp;I-D&nbsp;Action:&nbsp;draft-ietf-6renu=
m-gap-analysis-03.txt</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;A&nbsp;New&nbsp;Internet-Draft&nbsp;is&nbsp;available&nbsp;from&n=
bsp;the&nbsp;on-line&nbsp;Internet-Drafts&nbsp;directories.</DIV>
<DIV>&gt;&nbsp;This&nbsp;draft&nbsp;is&nbsp;a&nbsp;work&nbsp;item&nbsp;of&=
nbsp;the&nbsp;IPv6&nbsp;Site&nbsp;Renumbering&nbsp;Working&nbsp;Group&nbsp=
;of&nbsp;the</DIV>
<DIV>&gt;IETF.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;=20
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&n=
bsp;IPv6&nbsp;Site&nbsp;Renumbering&nbsp;Gap&nbsp;Analysis</DIV>
<DIV>&gt;=20
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;Bing&nbsp;Liu</D=
IV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;Sheng&nbsp;Jiang</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;Brian&nbsp;Carpenter</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;Stig&nbsp;Venaas</DIV>
<DIV>&gt;=20
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;draft-ietf-=
6renum-gap-analysis-03.txt</DIV>
<DIV>&gt;=20
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&n=
bsp;20</DIV>
<DIV>&gt;=20
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;:&nbsp;2012-09-03</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;Abstract:</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;This&nbsp;document&nbsp;briefly&nbsp;introduces=
&nbsp;the&nbsp;existing&nbsp;mechanisms&nbsp;could&nbsp;be</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;utilized&nbsp;by&nbsp;IPv6&nbsp;site&nbsp;renum=
bering&nbsp;and&nbsp;tries&nbsp;to&nbsp;cover&nbsp;most&nbsp;of&nbsp;the</=
DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;explicit&nbsp;issues&nbsp;and&nbsp;requirements=
&nbsp;of&nbsp;IPv6&nbsp;renumbering.&nbsp;Through&nbsp;the&nbsp;gap</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;analysis,&nbsp;the&nbsp;document&nbsp;provides&=
nbsp;a&nbsp;basis&nbsp;for&nbsp;future&nbsp;works&nbsp;that</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;identify&nbsp;and&nbsp;develop&nbsp;solutions&n=
bsp;or&nbsp;to&nbsp;stimulate&nbsp;such&nbsp;development&nbsp;as</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;appropriate.&nbsp;The&nbsp;gap&nbsp;analysis&nb=
sp;is&nbsp;presented&nbsp;following&nbsp;a&nbsp;renumbering</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;event&nbsp;procedure&nbsp;clue.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;The&nbsp;IETF&nbsp;datatracker&nbsp;status&nbsp;page&nbsp;for&nbs=
p;this&nbsp;draft&nbsp;is:</DIV>
<DIV>&gt;https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis</=
DIV>
<DIV>&gt;</DIV>
<DIV>&gt;There's&nbsp;also&nbsp;a&nbsp;htmlized&nbsp;version&nbsp;availabl=
e&nbsp;at:</DIV>
<DIV>&gt;http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03</DIV=
>
<DIV>&gt;</DIV>
<DIV>&gt;A&nbsp;diff&nbsp;from&nbsp;the&nbsp;previous&nbsp;version&nbsp;is=
&nbsp;available&nbsp;at:</DIV>
<DIV>&gt;http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis=
-03</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;Internet-Drafts&nbsp;are&nbsp;also&nbsp;available&nbsp;by&nbsp;an=
onymous&nbsp;FTP&nbsp;at:</DIV>
<DIV>&gt;ftp://ftp.ietf.org/internet-drafts/</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;_______________________________________________</DIV>
<DIV>&gt;renum&nbsp;mailing&nbsp;list</DIV>
<DIV>&gt;renum@ietf.org</DIV>
<DIV>&gt;https://www.ietf.org/mailman/listinfo/renum</DIV>
<DIV>_______________________________________________</DIV>
<DIV>renum&nbsp;mailing&nbsp;list</DIV>
<DIV>renum@ietf.org</DIV>
<DIV>https://www.ietf.org/mailman/listinfo/renum</DIV></DIV></BODY></HTML>

------=_001_NextPart172282378841_=------


From madi@cnnic.cn  Thu Sep 13 20:01:47 2012
Return-Path: <madi@cnnic.cn>
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 2F89021F865F for <renum@ietfa.amsl.com>; Thu, 13 Sep 2012 20:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.545
X-Spam-Level: 
X-Spam-Status: No, score=-0.545 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753]
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 ACcGkZqpQK87 for <renum@ietfa.amsl.com>; Thu, 13 Sep 2012 20:01:46 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id C311621F8639 for <renum@ietf.org>; Thu, 13 Sep 2012 20:01:45 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: madi@cnnic.cn
Received: from unknown127.0.0.1 (HELO user-think) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 14 Sep 2012 11:01:32 +0800
Date: Fri, 14 Sep 2012 11:01:30 +0800
From: "Di Ma" <madi@cnnic.cn>
To: =?gb2312?B?va/KpA==?= <jiangsheng@huawei.com>
References: <20120904021611.3518.72892.idtracker@ietfa.amsl.com>,  <5D36713D8A4E7348A7E10DF7437A4B9239F3938C@szxeml545-mbx.china.huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.90[cn]
Mime-Version: 1.0
Message-ID: <201209141101298192409@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart401662784747_=----"
Cc: 6renum <renum@ietf.org>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-02.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: madi <madi@cnnic.cn>
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: Fri, 14 Sep 2012 03:01:47 -0000

This is a multi-part message in MIME format.

------=_001_NextPart401662784747_=----
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

VGhpcyBkb2N1bWVudCBzaGVkcyBsaWdodCBvbiB3aGF0IHdlIGFyZSBnb2luZyB0byBoYW5kbGUg
d2l0aCB0aGUgbmV0d29yayByZW51bWJlcmluZy4gSSBhbSBpbiBmYXZvciBvZiBtb3ZpbmcgZm9y
d2FyZCB0aGlzIHdvcmsuIA0KDQoNCg0KDQpEaSBNYSANCkNOTklDIEFkdmFuY2VkIFJlc2VhcmNo
IERlcGFydG1lbnQNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KQ2hpbmEgSW50ZXJuZXQgTmV0d29yayBJbmZvcm1hdGlvbiBDZW50ZXINClRlbDog
KDg2MTApLTU4ODEzMjE2DQpIdHRwczovL3d3dy5jbm5pYy5jbg0KQWRkOiA0LCBTb3V0aCA0dGgg
U3RyZWV0LCBaaG9uZ2d1YW5jdW4NCkhhaWRpYW4gRGlzdHJpY3QsIEJlaWppbmcNClAuUi5DaGlu
YSAxMDAxOTANClBPQjogQmVpamluZyAzNDksIEJyYW5jaCA2DQpfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCkZyb206IFNoZW5nIEppYW5nDQpE
YXRlOiAyMDEyLTA5LTA0IDExOjQ0DQpUbzogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnOyBpLWQt
YW5ub3VuY2VAaWV0Zi5vcmcNCkNDOiByZW51bUBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtyZW51
bV0gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi02cmVudW0tZW50ZXJwcmlzZS0wMi50eHQNCkEgbmV3
IHZlcnNpb24gd2l0aCBtaW5vciBlZGl0b3JpYWwgbW9kaWZpY2F0aW9ucyBhcmUgc3VibWl0dGVk
LiBZb3VyIHJldmlldyBhbmQgY29tbWVudHMgYXJlIGFwcHJlY2lhdGVkLg0KDQpCZXN0IHJlZ2Fy
ZHMsDQoNClNoZW5nDQoNCj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPkZyb206IHJlbnVt
LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpyZW51bS1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh
bGYNCj5PZiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcNCj5TZW50OiBUdWVzZGF5LCBTZXB0ZW1i
ZXIgMDQsIDIwMTIgMTA6MTYgQU0NCj5UbzogaS1kLWFubm91bmNlQGlldGYub3JnDQo+Q2M6IHJl
bnVtQGlldGYub3JnDQo+U3ViamVjdDogW3JlbnVtXSBJLUQgQWN0aW9uOiBkcmFmdC1pZXRmLTZy
ZW51bS1lbnRlcnByaXNlLTAyLnR4dA0KPg0KPg0KPkEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2
YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy4NCj4g
VGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRlbSBvZiB0aGUgSVB2NiBTaXRlIFJlbnVtYmVyaW5nIFdv
cmtpbmcgR3JvdXAgb2YgdGhlDQo+SUVURi4NCj4NCj4gVGl0bGUgICAgICAgICAgIDogSVB2NiBF
bnRlcnByaXNlIE5ldHdvcmsgUmVudW1iZXJpbmcgU2NlbmFyaW9zIGFuZA0KPkd1aWRlbGluZXMN
Cj4gQXV0aG9yKHMpICAgICAgIDogU2hlbmcgSmlhbmcNCj4gICAgICAgICAgICAgICAgICAgICAg
ICAgIEJpbmcgTGl1DQo+ICAgICAgICAgICAgICAgICAgICAgICAgICBCcmlhbiBDYXJwZW50ZXIN
Cj4gRmlsZW5hbWUgICAgICAgIDogZHJhZnQtaWV0Zi02cmVudW0tZW50ZXJwcmlzZS0wMi50eHQN
Cj4gUGFnZXMgICAgICAgICAgIDogMTYNCj4gRGF0ZSAgICAgICAgICAgIDogMjAxMi0wOS0wMw0K
Pg0KPkFic3RyYWN0Og0KPiAgIFRoaXMgZG9jdW1lbnQgYW5hbHl6ZXMgZW50ZXJwcmlzZSByZW51
bWJlcmluZyBldmVudHMgYW5kIGRlc2NyaWJlcw0KPiAgIHRoZSBiZXN0IGN1cnJlbnQgcHJhY3Rp
Y2UgYW1vbmcgdGhlIGV4aXN0aW5nIHJlbnVtYmVyaW5nIG1lY2hhbmlzbXMuDQo+ICAgQWNjb3Jk
aW5nIHRvIHRoZSBkaWZmZXJlbnQgc3RhZ2VzIG9mIHJlbnVtYmVyaW5nIGV2ZW50cywNCj4gICBj
b25zaWRlcmF0aW9ucyBhbmQgYmVzdCBjdXJyZW50IHByYWN0aWNlcyBhcmUgZGVzY3JpYmVkIGlu
IHRocmVlDQo+ICAgY2F0ZWdvcmllczogZHVyaW5nIG5ldHdvcmsgZGVzaWduLCBmb3IgcHJlcGFy
YXRpb24gb2YgcmVudW1iZXJpbmcsDQo+ICAgYW5kIGR1cmluZyBhIHJlbnVtYmVyaW5nIG9wZXJh
dGlvbi4NCj4NCj4NCj5UaGUgSUVURiBkYXRhdHJhY2tlciBzdGF0dXMgcGFnZSBmb3IgdGhpcyBk
cmFmdCBpczoNCj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLTZy
ZW51bS1lbnRlcnByaXNlDQo+DQo+VGhlcmUncyBhbHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBhdmFp
bGFibGUgYXQ6DQo+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi02cmVudW0t
ZW50ZXJwcmlzZS0wMg0KPg0KPkEgZGlmZiBmcm9tIHRoZSBwcmV2aW91cyB2ZXJzaW9uIGlzIGF2
YWlsYWJsZSBhdDoNCj5odHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRm
LTZyZW51bS1lbnRlcnByaXNlLTAyDQo+DQo+DQo+SW50ZXJuZXQtRHJhZnRzIGFyZSBhbHNvIGF2
YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQIGF0Og0KPmZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5l
dC1kcmFmdHMvDQo+DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj5yZW51bSBtYWlsaW5nIGxpc3QNCj5yZW51bUBpZXRmLm9yZw0KPmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcmVudW0NCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQpyZW51bSBtYWlsaW5nIGxpc3QNCnJlbnVtQGlldGYu
b3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JlbnVt

------=_001_NextPart401662784747_=----
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3DGB2312" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: =CE=A2=C8=ED=D1=C5=BA=DA; COLOR: #000080; =
FONT-SIZE: 10.5pt
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 9.00.8112.16448"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 11pt" lang=3DE=
N-US><FONT=20
color=3D#000000>This document sheds light on what we are going to handle w=
ith the=20
network renumbering. I am in favor of moving forward this work. <?xml:name=
space=20
prefix =3D o ns =3D "urn:schemas-microsoft-com:office:office"=20
/><o:p></o:p></FONT></SPAN></P><!--EndFragment--></DIV>
<DIV>&nbsp;</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV><SPAN>
<DIV><SPAN style=3D"FONT-FAMILY: =CB=CE=CC=E5; COLOR: #000000; FONT-SIZE: =
10.5pt">
<DIV><FONT face=3D"Courier New"><FONT color=3D#0000ff>Di Ma</FONT> </FONT>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"></P>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff face=3D"Courier New">CNNIC Advanced Research=20
Department<BR>___________________________________________________</FONT></=
P>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff face=3D"Courier New">China Internet Network Information=20
Center<BR>Tel: (8610)-58813216<BR></FONT><FONT color=3D#0000ff=20
face=3D"Courier New">Https://www.cnnic.cn</FONT></P>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff face=3D"Courier New">Add: 4, South 4th Street,=20
Zhongguancun<BR>Haidian District, Beijing<BR>P.R.China 100190</FONT></P>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff><SPAN style=3D"FONT-FAMILY: Arial"><FONT size=3D2=20
face=3D"Courier New">POB: Beijing 349, Branch 6</FONT></SPAN><BR><FONT=20
face=3D"Courier New">____________________________________________________<=
/FONT></P></FONT></DIV></SPAN></DIV></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:jiangsheng@huawei.com">Sheng=20
Jiang</A></DIV>
<DIV><B>Date:</B>&nbsp;2012-09-04&nbsp;11:44</DIV>
<DIV><B>To:</B>&nbsp;<A=20
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</A>; <A=20
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A></DIV>
<DIV><B>CC:</B>&nbsp;<A href=3D"mailto:renum@ietf.org">renum@ietf.org</A><=
/DIV>
<DIV><B>Subject:</B>&nbsp;Re: [renum] I-D Action:=20
draft-ietf-6renum-enterprise-02.txt</DIV></DIV></DIV>
<DIV>
<DIV>A&nbsp;new&nbsp;version&nbsp;with&nbsp;minor&nbsp;editorial&nbsp;modi=
fications&nbsp;are&nbsp;submitted.&nbsp;Your&nbsp;review&nbsp;and&nbsp;com=
ments&nbsp;are&nbsp;appreciated.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Best&nbsp;regards,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Sheng</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;-----Original&nbsp;Message-----</DIV>
<DIV>&gt;From:&nbsp;renum-bounces@ietf.org&nbsp;[mailto:renum-bounces@ietf=
.org]&nbsp;On&nbsp;Behalf</DIV>
<DIV>&gt;Of&nbsp;internet-drafts@ietf.org</DIV>
<DIV>&gt;Sent:&nbsp;Tuesday,&nbsp;September&nbsp;04,&nbsp;2012&nbsp;10:16&=
nbsp;AM</DIV>
<DIV>&gt;To:&nbsp;i-d-announce@ietf.org</DIV>
<DIV>&gt;Cc:&nbsp;renum@ietf.org</DIV>
<DIV>&gt;Subject:&nbsp;[renum]&nbsp;I-D&nbsp;Action:&nbsp;draft-ietf-6renu=
m-enterprise-02.txt</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;A&nbsp;New&nbsp;Internet-Draft&nbsp;is&nbsp;available&nbsp;from&n=
bsp;the&nbsp;on-line&nbsp;Internet-Drafts&nbsp;directories.</DIV>
<DIV>&gt;&nbsp;This&nbsp;draft&nbsp;is&nbsp;a&nbsp;work&nbsp;item&nbsp;of&=
nbsp;the&nbsp;IPv6&nbsp;Site&nbsp;Renumbering&nbsp;Working&nbsp;Group&nbsp=
;of&nbsp;the</DIV>
<DIV>&gt;IETF.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;=20
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&n=
bsp;IPv6&nbsp;Enterprise&nbsp;Network&nbsp;Renumbering&nbsp;Scenarios&nbsp=
;and</DIV>
<DIV>&gt;Guidelines</DIV>
<DIV>&gt;=20
Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;Sheng&nbsp;Jiang=
</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;Bing&nbsp;Liu</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;Brian&nbsp;Carpenter</DIV>
<DIV>&gt;=20
Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;draft-ietf-=
6renum-enterprise-02.txt</DIV>
<DIV>&gt;=20
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&n=
bsp;16</DIV>
<DIV>&gt;=20
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;:&nbsp;2012-09-03</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;Abstract:</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;This&nbsp;document&nbsp;analyzes&nbsp;enterpris=
e&nbsp;renumbering&nbsp;events&nbsp;and&nbsp;describes</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;the&nbsp;best&nbsp;current&nbsp;practice&nbsp;a=
mong&nbsp;the&nbsp;existing&nbsp;renumbering&nbsp;mechanisms.</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;According&nbsp;to&nbsp;the&nbsp;different&nbsp;=
stages&nbsp;of&nbsp;renumbering&nbsp;events,</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;considerations&nbsp;and&nbsp;best&nbsp;current&=
nbsp;practices&nbsp;are&nbsp;described&nbsp;in&nbsp;three</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;categories:&nbsp;during&nbsp;network&nbsp;desig=
n,&nbsp;for&nbsp;preparation&nbsp;of&nbsp;renumbering,</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;and&nbsp;during&nbsp;a&nbsp;renumbering&nbsp;op=
eration.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;The&nbsp;IETF&nbsp;datatracker&nbsp;status&nbsp;page&nbsp;for&nbs=
p;this&nbsp;draft&nbsp;is:</DIV>
<DIV>&gt;https://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise</DI=
V>
<DIV>&gt;</DIV>
<DIV>&gt;There's&nbsp;also&nbsp;a&nbsp;htmlized&nbsp;version&nbsp;availabl=
e&nbsp;at:</DIV>
<DIV>&gt;http://tools.ietf.org/html/draft-ietf-6renum-enterprise-02</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;A&nbsp;diff&nbsp;from&nbsp;the&nbsp;previous&nbsp;version&nbsp;is=
&nbsp;available&nbsp;at:</DIV>
<DIV>&gt;http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-enterprise-0=
2</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;Internet-Drafts&nbsp;are&nbsp;also&nbsp;available&nbsp;by&nbsp;an=
onymous&nbsp;FTP&nbsp;at:</DIV>
<DIV>&gt;ftp://ftp.ietf.org/internet-drafts/</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;_______________________________________________</DIV>
<DIV>&gt;renum&nbsp;mailing&nbsp;list</DIV>
<DIV>&gt;renum@ietf.org</DIV>
<DIV>&gt;https://www.ietf.org/mailman/listinfo/renum</DIV>
<DIV>_______________________________________________</DIV>
<DIV>renum&nbsp;mailing&nbsp;list</DIV>
<DIV>renum@ietf.org</DIV>
<DIV>https://www.ietf.org/mailman/listinfo/renum</DIV></DIV></BODY></HTML>

------=_001_NextPart401662784747_=------


From eleven.fuyu@huawei.com  Fri Sep 14 02:08:43 2012
Return-Path: <eleven.fuyu@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 88D1621F8578 for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 02:08:43 -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 nygrIbQOukIJ for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 02:08:42 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9C73D21F8581 for <renum@ietf.org>; Fri, 14 Sep 2012 02:08:41 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AJQ90540; Fri, 14 Sep 2012 09:08:40 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 14 Sep 2012 10:08:03 +0100
Received: from SZXEML417-HUB.china.huawei.com (10.82.67.156) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 14 Sep 2012 10:08:18 +0100
Received: from SZXEML512-MBX.china.huawei.com ([169.254.5.187]) by szxeml417-hub.china.huawei.com ([10.82.67.156]) with mapi id 14.01.0323.003; Fri, 14 Sep 2012 17:08:13 +0800
From: "Fuyu (Eleven)" <eleven.fuyu@huawei.com>
To: "Howard, Lee" <lee.howard@twcable.com>
Thread-Topic: Working Group Last Call: draft-ietf-6renum-enterprise-02.txt
Thread-Index: Ac2MS1AyGfCtBCmORjqQzps1UhuJbgGBOT3Q
Date: Fri, 14 Sep 2012 09:08:13 +0000
Message-ID: <EF6A204047BD994A860EE26D5F23BF582B8E1C22@SZXEML512-MBX.china.huawei.com>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E15@PRVPEXVS17.corp.twcable.com>
In-Reply-To: <99B887114EDB1449941CFBC8EC279FA12CB43E15@PRVPEXVS17.corp.twcable.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Working Group Last Call: draft-ietf-6renum-enterprise-02.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: Fri, 14 Sep 2012 09:08:43 -0000

This draft analyze the enterprise renumbering events for different scenario=
 and give suggestions to reduce the influence to the network.=20
I think it is useful and well- organized. So I support to move forward this=
 draft.

Cheers=20
Yu

-----Original Message-----
From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of H=
oward, Lee
Sent: Friday, September 07, 2012 12:19 AM
To: renum@ietf.org
Subject: [renum] Working Group Last Call: draft-ietf-6renum-enterprise-02.t=
xt

We are requesting a Working Group Last Call on this document.  Please revie=
w and provide comments before September 19, since this may be the final rev=
iew of this document.

Thanks,

Lee


> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of
Sheng Jiang
> Sent: Monday, September 03, 2012 11:44 PM
> To: internet-drafts@ietf.org; i-d-announce@ietf.org
> Cc: renum@ietf.org
> Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-02.txt
>
> A new version with minor editorial modifications are submitted. Your
review and comments
> are appreciated.
>
> Best regards,
>
> Sheng
>
> >-----Original Message-----
> >From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On
> >Behalf Of internet-drafts@ietf.org
> >Sent: Tuesday, September 04, 2012 10:16 AM
> >To: i-d-announce@ietf.org
> >Cc: renum@ietf.org
> >Subject: [renum] I-D Action: draft-ietf-6renum-enterprise-02.txt
> >
> >
> >A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> > This draft is a work item of the IPv6 Site Renumbering Working Group
> >of the IETF.
> >
> >     Title           : IPv6 Enterprise Network Renumbering Scenarios and
> >Guidelines
> >     Author(s)       : Sheng Jiang
> >                          Bing Liu
> >                          Brian Carpenter
> >     Filename        : draft-ietf-6renum-enterprise-02.txt
> >     Pages           : 16
> >     Date            : 2012-09-03
> >
> >Abstract:
> >   This document analyzes enterprise renumbering events and describes
> >   the best current practice among the existing renumbering mechanisms.
> >   According to the different stages of renumbering events,
> >   considerations and best current practices are described in three
> >   categories: during network design, for preparation of renumbering,
> >   and during a renumbering operation.
> >
> >
> >The IETF datatracker status page for this draft is:
> >https://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise
> >
> >There's also a htmlized version available at:
> >http://tools.ietf.org/html/draft-ietf-6renum-enterprise-02
> >
> >A diff from the previous version is available at:
> >http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-enterprise-02
> >
> >
> >Internet-Drafts are also available by anonymous FTP at:
> >ftp://ftp.ietf.org/internet-drafts/
> >
> >_______________________________________________
> >renum mailing list
> >renum@ietf.org
> >https://www.ietf.org/mailman/listinfo/renum
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum


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.
_______________________________________________
renum mailing list
renum@ietf.org
https://www.ietf.org/mailman/listinfo/renum

From leo.liubing@huawei.com  Fri Sep 14 02:20:33 2012
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 CED4B21F85E6 for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 02:20:32 -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=[AWL=-0.001, 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 ELzsR3HgokJJ for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 02:20:29 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 07C5221F85F0 for <renum@ietf.org>; Fri, 14 Sep 2012 02:20:27 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AJQ91549; Fri, 14 Sep 2012 09:20:27 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 14 Sep 2012 10:19:43 +0100
Received: from SZXEML407-HUB.china.huawei.com (10.82.67.94) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 14 Sep 2012 10:19:58 +0100
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml407-hub.china.huawei.com ([10.82.67.94]) with mapi id 14.01.0323.003; Fri, 14 Sep 2012 17:19:47 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: madi <madi@cnnic.cn>, Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: AQHNik7MInfcpaeCJk6BA/ZG3LCMd5eJNZQogABjNgA=
Date: Fri, 14 Sep 2012 09:19:45 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F452935456B@szxeml509-mbs>
References: <20120904033758.18836.26105.idtracker@ietfa.amsl.com>, <5D36713D8A4E7348A7E10DF7437A4B9239F3A393@szxeml545-mbx.china.huawei.com> <201209141100044525538@cnnic.cn>
In-Reply-To: <201209141100044525538@cnnic.cn>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.42]
Content-Type: multipart/alternative; boundary="_000_8AE0F17B87264D4CAC7DE0AA6C406F452935456Bszxeml509mbs_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: 6renum <renum@ietf.org>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.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: Fri, 14 Sep 2012 09:20:33 -0000

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

Hi, Di
Thanks for your review and the new contribution.
Personally, I think the issue you pointed out is worth to be documented. If=
 the IP addresses are renumbered, the SA would be definitely broken. But I =
would like to hear the  co-authors' and the WG's opinions about it, since i=
t is been under WGLC.
For the texts, I think it may need to be simplified, especially the IKEv2 r=
elevant details may confuse people that it is talking about a IKEv2 gap, bu=
t in fact it is about SA.

B.R.
Bing

From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of D=
i Ma
Sent: Friday, September 14, 2012 11:00 AM
To: Sheng Jiang
Cc: 6renum
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt

I am in favor of moving forward this work.

Yet as a document providing a basis for future works that identify and deve=
lop solutions or to stimulate such development as appropriate, this draft m=
ight make IPSec Security Association (SA) management included, considering =
IPSec SA is a kind of IP address oriented "connection" that cannot function=
 after the change of the involved IP addresses, which means extra configura=
tion of SA parameters is inevitable after network renumbering.

So, I propose adding some words into this draft as Section 8.3 (IPSec SA Ma=
nagement), a sector of Section 8 (Miscellaneous), which is described as fol=
lows:

Network renumbering events get networking mechanisms that are bound to IP a=
ddresses, or applications using specific IP addresses, involved. As defined=
 in [RFC4301], IPSec Security Association (SA), as a kind of IP address ori=
ented "connection", cannot function after the change of the involved IP add=
resses, which means extra configuration of SA parameters is inevitable afte=
r network renumbering.

SA is a "connection" that provides security services to the traffic carried=
 by it and details the key and algorithm that the IPSec connection relies o=
n. SA can be established with manual configuration by the administrator. IK=
Ev2 [RFC5996] eliminates manual reconfiguration. It employs two rounds of m=
essage exchanges. The first exchange of messages establishes a trust relati=
onship between the two IKEv2 participants. This exchange uses two authentic=
ation methods, digital signature and pre-shared key. The digital signature =
method needs certificate management. If the participants are not configured=
 with the same trust anchor, certificate-based IKEv2 cannot be realized. Wh=
ile the pre-shared key method is the simpler of the authentication methods =
for IKEv2 and pre-shared keys are tied to particular IP addresses, unlike p=
ublic key certificates used by digital signature method. Pre-shared key met=
hod cannot be used with mobile systems or systems that may be renumbered, u=
nless the renumbering is within the previously determined range of IP addre=
sses. Also, when pre-shared key is employed, IKEv2 computations cannot be o=
ffloaded to the attached hardware. Therefore, pre-shared key method fails t=
o be a pure automatic one and does not go well with network renumbering. A =
mechanism that is able to integrate SA management into IP address assignmen=
t in an automatic and an adaptive manner is desired to go with network renu=
mbering.


________________________________
Di Ma
CNNIC Advanced Research Department
___________________________________________________
China Internet Network Information Center
Tel: (8610)-58813216
Https://www.cnnic.cn
Add: 4, South 4th Street, Zhongguancun
Haidian District, Beijing
P.R.China 100190
POB: Beijing 349, Branch 6
____________________________________________________

From: Sheng Jiang<mailto:jiangsheng@huawei.com>
Date: 2012-09-04 11:44
To: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>; i-d-announce=
@ietf.org<mailto:i-d-announce@ietf.org>
CC: renum@ietf.org<mailto:renum@ietf.org>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
A new version with minor editorial modifications are submitted. Your review=
 and comments are appreciated.

Best regards,

Sheng

>-----Original Message-----
>From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
>Of internet-drafts@ietf.org
>Sent: Tuesday, September 04, 2012 11:38 AM
>To: i-d-announce@ietf.org
>Cc: renum@ietf.org
>Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
>
>
>A New Internet-Draft is available from the on-line Internet-Drafts directo=
ries.
> This draft is a work item of the IPv6 Site Renumbering Working Group of t=
he
>IETF.
>
> Title           : IPv6 Site Renumbering Gap Analysis
> Author(s)       : Bing Liu
>                          Sheng Jiang
>                          Brian Carpenter
>                          Stig Venaas
> Filename        : draft-ietf-6renum-gap-analysis-03.txt
> Pages           : 20
> Date            : 2012-09-03
>
>Abstract:
>   This document briefly introduces the existing mechanisms could be
>   utilized by IPv6 site renumbering and tries to cover most of the
>   explicit issues and requirements of IPv6 renumbering. Through the gap
>   analysis, the document provides a basis for future works that
>   identify and develop solutions or to stimulate such development as
>   appropriate. The gap analysis is presented following a renumbering
>   event procedure clue.
>
>
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-03
>
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>renum mailing list
>renum@ietf.org
>https://www.ietf.org/mailman/listinfo/renum
_______________________________________________
renum mailing list
renum@ietf.org
https://www.ietf.org/mailman/listinfo/renum

--_000_8AE0F17B87264D4CAC7DE0AA6C406F452935456Bszxeml509mbs_
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)">
<!--[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:"Microsoft YaHei";
	panose-1:2 11 5 3 2 2 4 2 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;}
@font-face
	{font-family:"Microsoft YaHei";
	panose-1:2 11 5 3 2 2 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:SimSun;
	mso-believe-normal-left:yes;}
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;}
p
	{mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
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 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><![if mso 9]><style>p.MsoNormal
	{margin-left:7.5pt;}
</style><![endif]><!--[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"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"margin-left:7.=
5pt;margin-top:7.5pt;margin-right:7.5pt;margin-bottom:7.5pt">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi, Di<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks for=
 your review and the new contribution.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Personally=
, I think the issue you pointed out is worth to be documented. If the IP ad=
dresses are renumbered, the SA would be definitely broken.
 But I would like to hear the &nbsp;co-authors&#8217; and the WG&#8217;s op=
inions about it, since it is been under WGLC.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">For the te=
xts, I think it may need to be simplified, especially the IKEv2 relevant de=
tails may confuse people that it is talking about a IKEv2
 gap, but in fact it is about SA. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">B.R.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bing<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></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" style=3D"margin:0cm;margin-bottom:.0001pt"><b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;">From:</span></b><span lang=3D"EN-US" style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> renum-boun=
ces@ietf.org
 [mailto:renum-bounces@ietf.org] <b>On Behalf Of </b>Di Ma<br>
<b>Sent:</b> Friday, September 14, 2012 11:00 AM<br>
<b>To:</b> Sheng Jiang<br>
<b>Cc:</b> 6renum<br>
<b>Subject:</b> Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.t=
xt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;;color:black">I am in favor of moving forward this work=
.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;;color:navy"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;;color:black">Yet as a document providing a basis for f=
uture works that identify and develop solutions or to stimulate
 such development as appropriate, this draft might make IPSec Security Asso=
ciation (SA) management included, considering IPSec SA is a kind of IP addr=
ess oriented &#8220;connection&#8221; that cannot function after the change=
 of the involved IP addresses, which means extra
 configuration of SA parameters is inevitable after network renumbering. </=
span><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Times=
 New Roman&quot;,&quot;serif&quot;;color:navy"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;;color:navy"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;;color:black">So, I propose adding some words into this=
 draft as Section 8.3 (IPSec SA Management), a sector of Section
 8 (Miscellaneous), which is described as follows:<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:9.0pt;color:navy"><o:p>&nbsp;</o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><i><span =
lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Times New Roman&=
quot;,&quot;serif&quot;;color:black">Network renumbering events get network=
ing mechanisms that are bound to IP addresses, or applications
 using specific IP addresses, involved. As defined in [RFC4301], IPSec Secu=
rity Association (SA), as a kind of IP address oriented &#8220;connection&#=
8221;, cannot function after the change of the involved IP addresses, which=
 means extra configuration of SA parameters
 is inevitable after network renumbering. <o:p></o:p></span></i></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><i><span =
lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Times New Roman&=
quot;,&quot;serif&quot;;color:navy"><o:p>&nbsp;</o:p></span></i></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><i><span =
lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Times New Roman&=
quot;,&quot;serif&quot;;color:black">SA is a &#8220;connection&#8221; that =
provides security services to the traffic carried by it and details the
 key and algorithm that the IPSec connection relies on. SA can be establish=
ed with manual configuration by the administrator. IKEv2 [RFC5996] eliminat=
es manual reconfiguration. It employs two rounds of message exchanges. The =
first exchange of messages establishes
 a trust relationship between the two IKEv2 participants. This exchange use=
s two authentication methods, digital signature and pre-shared key. The dig=
ital signature method needs certificate management. If the participants are=
 not configured with the same trust
 anchor, certificate-based IKEv2 cannot be realized. While the pre-shared k=
ey method is the simpler of the authentication methods for IKEv2 and pre-sh=
ared keys are tied to particular IP addresses, unlike public key certificat=
es used by digital signature method.
 Pre-shared key method cannot be used with mobile systems or systems that m=
ay be renumbered, unless the renumbering is within the previously determine=
d range of IP addresses. Also, when pre-shared key is employed, IKEv2 compu=
tations cannot be offloaded to the
 attached hardware. Therefore, pre-shared key method fails to be a pure aut=
omatic one and does not go well with network renumbering. A mechanism that =
is able to integrate SA management into IP address assignment in an automat=
ic and an adaptive manner is desired
 to go with network renumbering.<o:p></o:p></span></i></p>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&nbsp;<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&nbsp;<o:p></o:p></s=
pan></p>
</div>
<div>
<div class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span l=
ang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&=
#38597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">
<hr size=3D"1" width=3D"210" style=3D"width:157.5pt" noshade=3D"" style=3D"=
color:#B5C4DF" align=3D"left">
</span></div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;c=
olor:blue">Di Ma</span><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Courier New&quot;;color:black">
</span><span lang=3D"EN-US" style=3D"font-size:10.5pt;color:black"><o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-family:&quot;Courier New&quot;;color:blue">CNNIC =
Advanced Research Department<br>
___________________________________________________</span><span lang=3D"EN-=
US" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-family:&quot;Courier New&quot;;color:blue">China =
Internet Network Information Center<br>
Tel: (8610)-58813216<br>
Https://www.cnnic.cn</span><span lang=3D"EN-US" style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-family:&quot;Courier New&quot;;color:blue">Add: 4=
, South 4th Street, Zhongguancun<br>
Haidian District, Beijing<br>
P.R.China 100190</span><span lang=3D"EN-US" style=3D"color:black"><o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;c=
olor:blue">POB: Beijing 349, Branch 6</span><span lang=3D"EN-US" style=3D"c=
olor:blue"><br>
</span><span lang=3D"EN-US" style=3D"font-family:&quot;Courier New&quot;;co=
lor:blue">____________________________________________________</span><span =
lang=3D"EN-US" style=3D"color:blue"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&nbsp;<o:p></o:p></s=
pan></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt;background=
:#EFEFEF">
<b><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;&#24494;=
&#36719;&#38597;&#40657;&quot;,&quot;sans-serif&quot;;color:black">From:</s=
pan></b><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;&#2=
4494;&#36719;&#38597;&#40657;&quot;,&quot;sans-serif&quot;;color:black">&nb=
sp;<a href=3D"mailto:jiangsheng@huawei.com">Sheng Jiang</a><o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt;background=
:#EFEFEF">
<b><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;&#24494;=
&#36719;&#38597;&#40657;&quot;,&quot;sans-serif&quot;;color:black">Date:</s=
pan></b><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;&#2=
4494;&#36719;&#38597;&#40657;&quot;,&quot;sans-serif&quot;;color:black">&nb=
sp;2012-09-04&nbsp;11:44<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt;background=
:#EFEFEF">
<b><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;&#24494;=
&#36719;&#38597;&#40657;&quot;,&quot;sans-serif&quot;;color:black">To:</spa=
n></b><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;&#244=
94;&#36719;&#38597;&#40657;&quot;,&quot;sans-serif&quot;;color:black">&nbsp=
;<a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>;
<a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt;background=
:#EFEFEF">
<b><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;&#24494;=
&#36719;&#38597;&#40657;&quot;,&quot;sans-serif&quot;;color:black">CC:</spa=
n></b><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;&#244=
94;&#36719;&#38597;&#40657;&quot;,&quot;sans-serif&quot;;color:black">&nbsp=
;<a href=3D"mailto:renum@ietf.org">renum@ietf.org</a><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt;background=
:#EFEFEF">
<b><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;&#24494;=
&#36719;&#38597;&#40657;&quot;,&quot;sans-serif&quot;;color:black">Subject:=
</span></b><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;=
&#24494;&#36719;&#38597;&#40657;&quot;,&quot;sans-serif&quot;;color:black">=
&nbsp;Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt<o:p></o=
:p></span></p>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">A&nbsp;new&nbsp;vers=
ion&nbsp;with&nbsp;minor&nbsp;editorial&nbsp;modifications&nbsp;are&nbsp;su=
bmitted.&nbsp;Your&nbsp;review&nbsp;and&nbsp;comments&nbsp;are&nbsp;appreci=
ated.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&nbsp;<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">Best&nbsp;regards,<o=
:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&nbsp;<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">Sheng<o:p></o:p></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&nbsp;<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;-----Original&nb=
sp;Message-----<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;From:&nbsp;renum=
-bounces@ietf.org&nbsp;[mailto:renum-bounces@ietf.org]&nbsp;On&nbsp;Behalf<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;Of&nbsp;internet=
-drafts@ietf.org<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;Sent:&nbsp;Tuesd=
ay,&nbsp;September&nbsp;04,&nbsp;2012&nbsp;11:38&nbsp;AM<o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;To:&nbsp;i-d-ann=
ounce@ietf.org<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;Cc:&nbsp;renum@i=
etf.org<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;Subject:&nbsp;[r=
enum]&nbsp;I-D&nbsp;Action:&nbsp;draft-ietf-6renum-gap-analysis-03.txt<o:p>=
</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;A&nbsp;New&nbsp;=
Internet-Draft&nbsp;is&nbsp;available&nbsp;from&nbsp;the&nbsp;on-line&nbsp;=
Internet-Drafts&nbsp;directories.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;&nbsp;This&nbsp;=
draft&nbsp;is&nbsp;a&nbsp;work&nbsp;item&nbsp;of&nbsp;the&nbsp;IPv6&nbsp;Si=
te&nbsp;Renumbering&nbsp;Working&nbsp;Group&nbsp;of&nbsp;the<o:p></o:p></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;IETF.<o:p></o:p>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt; Title&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;IPv6&nbsp;Si=
te&nbsp;Renumbering&nbsp;Gap&nbsp;Analysis<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt; Author(s)&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;Bing&nbsp;Liu<o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Sheng&nbsp=
;Jiang<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Brian&nbsp=
;Carpenter<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Stig&nbsp;=
Venaas<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt; Filename&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;draft-ietf-6renum-gap-analy=
sis-03.txt<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt; Pages&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;20<o:p></o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt; Date&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:&nbsp;2012-09=
-03<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;Abstract:<o:p></=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;&nbsp;&nbsp;&nbs=
p;This&nbsp;document&nbsp;briefly&nbsp;introduces&nbsp;the&nbsp;existing&nb=
sp;mechanisms&nbsp;could&nbsp;be<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;&nbsp;&nbsp;&nbs=
p;utilized&nbsp;by&nbsp;IPv6&nbsp;site&nbsp;renumbering&nbsp;and&nbsp;tries=
&nbsp;to&nbsp;cover&nbsp;most&nbsp;of&nbsp;the<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;&nbsp;&nbsp;&nbs=
p;explicit&nbsp;issues&nbsp;and&nbsp;requirements&nbsp;of&nbsp;IPv6&nbsp;re=
numbering.&nbsp;Through&nbsp;the&nbsp;gap<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;&nbsp;&nbsp;&nbs=
p;analysis,&nbsp;the&nbsp;document&nbsp;provides&nbsp;a&nbsp;basis&nbsp;for=
&nbsp;future&nbsp;works&nbsp;that<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;&nbsp;&nbsp;&nbs=
p;identify&nbsp;and&nbsp;develop&nbsp;solutions&nbsp;or&nbsp;to&nbsp;stimul=
ate&nbsp;such&nbsp;development&nbsp;as<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;&nbsp;&nbsp;&nbs=
p;appropriate.&nbsp;The&nbsp;gap&nbsp;analysis&nbsp;is&nbsp;presented&nbsp;=
following&nbsp;a&nbsp;renumbering<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;&nbsp;&nbsp;&nbs=
p;event&nbsp;procedure&nbsp;clue.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;The&nbsp;IETF&nb=
sp;datatracker&nbsp;status&nbsp;page&nbsp;for&nbsp;this&nbsp;draft&nbsp;is:=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;https://datatrac=
ker.ietf.org/doc/draft-ietf-6renum-gap-analysis<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;There's&nbsp;als=
o&nbsp;a&nbsp;htmlized&nbsp;version&nbsp;available&nbsp;at:<o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;http://tools.iet=
f.org/html/draft-ietf-6renum-gap-analysis-03<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;A&nbsp;diff&nbsp=
;from&nbsp;the&nbsp;previous&nbsp;version&nbsp;is&nbsp;available&nbsp;at:<o=
:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;http://www.ietf.=
org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-03<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;Internet-Drafts&=
nbsp;are&nbsp;also&nbsp;available&nbsp;by&nbsp;anonymous&nbsp;FTP&nbsp;at:<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;ftp://ftp.ietf.o=
rg/internet-drafts/<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;<o:p>&nbsp;</o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;________________=
_______________________________<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;renum&nbsp;maili=
ng&nbsp;list<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;renum@ietf.org<o=
:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">&gt;https://www.ietf=
.org/mailman/listinfo/renum<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">____________________=
___________________________<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">renum&nbsp;mailing&n=
bsp;list<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">renum@ietf.org<o:p><=
/o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0cm;margin-bottom:.0001pt"><span lan=
g=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;&#24494;&#36719;&#3=
8597;&#40657;&quot;,&quot;sans-serif&quot;;color:navy">https://www.ietf.org=
/mailman/listinfo/renum<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_8AE0F17B87264D4CAC7DE0AA6C406F452935456Bszxeml509mbs_--

From brian.e.carpenter@gmail.com  Fri Sep 14 06:09:00 2012
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 9F32621F8503 for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 06:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[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 I8-37c6YKTYr for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 06:08:59 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7F2A821F84FD for <renum@ietf.org>; Fri, 14 Sep 2012 06:08:59 -0700 (PDT)
Received: by ieak13 with SMTP id k13so7512338iea.31 for <renum@ietf.org>; Fri, 14 Sep 2012 06:08:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=03siIiAXEFGkXAYd4vwdh3U9hKIAZy3I+R8DrFXmHaY=; b=B7P06lJmbU4tU39jbFPELX77STIKdYc2hBg7USvNKIv0RMQIxH4KW2Lvr2oJKB1RVM J097+KkCwWYSpw/TBxZvqe9+h6ZT06nWfZQIUlVVXM3bgvA2HRJOTuCSEkcrlk1LxSaC YEmt+N+DwoS05c5DEh39lAzxqvsaAK1KgCuuL+yziqaiffTRzXcvVG/1BZa8G2UDQHqz cg9aCESXaWL53MatTGc1Aq87UingDrOdxI4Td1kwDPwrMWjZESRzYMpKQXQPMpkj+L5g w/XJyP/OMFQFnlFk8j3l3slgmMqQeWS4IItinwTSsc3bq6Hd56oK/m/7Gv2remI5FwlX +PgA==
Received: by 10.50.95.231 with SMTP id dn7mr3101364igb.37.1347628138839; Fri, 14 Sep 2012 06:08:58 -0700 (PDT)
Received: from [10.255.25.102] (50-76-68-140-static.hfc.comcastbusiness.net. [50.76.68.140]) by mx.google.com with ESMTPS id cu10sm3316545igc.9.2012.09.14.06.08.56 (version=SSLv3 cipher=OTHER); Fri, 14 Sep 2012 06:08:58 -0700 (PDT)
Message-ID: <50532C74.8080803@gmail.com>
Date: Fri, 14 Sep 2012 14:09:08 +0100
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: "Liubing (Leo)" <leo.liubing@huawei.com>
References: <20120904033758.18836.26105.idtracker@ietfa.amsl.com>, <5D36713D8A4E7348A7E10DF7437A4B9239F3A393@szxeml545-mbx.china.huawei.com>	<201209141100044525538@cnnic.cn> <8AE0F17B87264D4CAC7DE0AA6C406F452935456B@szxeml509-mbs>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F452935456B@szxeml509-mbs>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6renum <renum@ietf.org>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.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: Fri, 14 Sep 2012 13:09:00 -0000

It is a good point to mention. As far as I can tell, there is no solution;
sessions using address-based SAs will need to renegotiate (just like
a TCP or TLS session, in fact).

See RFC 5887, however, which gives the solution for the VPN application
of IPsec (use FQDN-based SA).

I noticed that RFC 4192 doesn't mention IPsec!

Regards
   Brian


On 14/09/2012 10:19, Liubing (Leo) wrote:
> Hi, Di
> Thanks for your review and the new contribution.
> Personally, I think the issue you pointed out is worth to be documented. If the IP addresses are renumbered, the SA would be definitely broken. But I would like to hear the  co-authors' and the WG's opinions about it, since it is been under WGLC.
> For the texts, I think it may need to be simplified, especially the IKEv2 relevant details may confuse people that it is talking about a IKEv2 gap, but in fact it is about SA.
> 
> B.R.
> Bing
> 
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of Di Ma
> Sent: Friday, September 14, 2012 11:00 AM
> To: Sheng Jiang
> Cc: 6renum
> Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
> 
> I am in favor of moving forward this work.
> 
> Yet as a document providing a basis for future works that identify and develop solutions or to stimulate such development as appropriate, this draft might make IPSec Security Association (SA) management included, considering IPSec SA is a kind of IP address oriented "connection" that cannot function after the change of the involved IP addresses, which means extra configuration of SA parameters is inevitable after network renumbering.
> 
> So, I propose adding some words into this draft as Section 8.3 (IPSec SA Management), a sector of Section 8 (Miscellaneous), which is described as follows:
> 
> Network renumbering events get networking mechanisms that are bound to IP addresses, or applications using specific IP addresses, involved. As defined in [RFC4301], IPSec Security Association (SA), as a kind of IP address oriented "connection", cannot function after the change of the involved IP addresses, which means extra configuration of SA parameters is inevitable after network renumbering.
> 
> SA is a "connection" that provides security services to the traffic carried by it and details the key and algorithm that the IPSec connection relies on. SA can be established with manual configuration by the administrator. IKEv2 [RFC5996] eliminates manual reconfiguration. It employs two rounds of message exchanges. The first exchange of messages establishes a trust relationship between the two IKEv2 participants. This exchange uses two authentication methods, digital signature and pre-shared key. The digital signature method needs certificate management. If the participants are not configured with the same trust anchor, certificate-based IKEv2 cannot be realized. While the pre-shared key method is the simpler of the authentication methods for IKEv2 and pre-shared keys are tied to particular IP addresses, unlike public key certificates used by digital signature method. Pre-shared key method cannot be used with mobile systems or systems that may be renumbered, unless the re
numbering is within the previously determined range of IP addresses. Also, when pre-shared key is employed, IKEv2 computations cannot be offloaded to the attached hardware. Therefore, pre-shared key method fails to be a pure automatic one and does not go well with network renumbering. A mechanism that is able to integrate SA management into IP address assignment in an automatic and an adaptive manner is desired to go with network renumbering.
> 
> 
> ________________________________
> Di Ma
> CNNIC Advanced Research Department
> ___________________________________________________
> China Internet Network Information Center
> Tel: (8610)-58813216
> Https://www.cnnic.cn
> Add: 4, South 4th Street, Zhongguancun
> Haidian District, Beijing
> P.R.China 100190
> POB: Beijing 349, Branch 6
> ____________________________________________________
> 
> From: Sheng Jiang<mailto:jiangsheng@huawei.com>
> Date: 2012-09-04 11:44
> To: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>; i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
> CC: renum@ietf.org<mailto:renum@ietf.org>
> Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
> A new version with minor editorial modifications are submitted. Your review and comments are appreciated.
> 
> Best regards,
> 
> Sheng
> 
>> -----Original Message-----
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
>> Of internet-drafts@ietf.org
>> Sent: Tuesday, September 04, 2012 11:38 AM
>> To: i-d-announce@ietf.org
>> Cc: renum@ietf.org
>> Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the IPv6 Site Renumbering Working Group of the
>> IETF.
>>
>> Title           : IPv6 Site Renumbering Gap Analysis
>> Author(s)       : Bing Liu
>>                          Sheng Jiang
>>                          Brian Carpenter
>>                          Stig Venaas
>> Filename        : draft-ietf-6renum-gap-analysis-03.txt
>> Pages           : 20
>> Date            : 2012-09-03
>>
>> Abstract:
>>   This document briefly introduces the existing mechanisms could be
>>   utilized by IPv6 site renumbering and tries to cover most of the
>>   explicit issues and requirements of IPv6 renumbering. Through the gap
>>   analysis, the document provides a basis for future works that
>>   identify and develop solutions or to stimulate such development as
>>   appropriate. The gap analysis is presented following a renumbering
>>   event procedure clue.
>>
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-6renum-gap-analysis-03
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> renum mailing list
>> renum@ietf.org
>> https://www.ietf.org/mailman/listinfo/renum
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

From lee.howard@twcable.com  Fri Sep 14 10:01:41 2012
Return-Path: <lee.howard@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 E5BDE21F851E for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 10:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.213
X-Spam-Level: 
X-Spam-Status: No, score=-1.213 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 vsWqH4AAf8zD for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 10:01:41 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 5144021F851C for <renum@ietf.org>; Fri, 14 Sep 2012 10:01:41 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,423,1344225600"; d="scan'208";a="438771286"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 14 Sep 2012 13:01:11 -0400
Received: from PRVPEXVS17.corp.twcable.com ([10.136.163.95]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Fri, 14 Sep 2012 13:01:25 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: "renum@ietf.org" <renum@ietf.org>
Date: Fri, 14 Sep 2012 13:01:24 -0400
Thread-Topic: Working Group Last Call: draft-ietf-6renum-static-problem-01.txt
Thread-Index: Ac2SmleJUG5z5HTMQcKalR8udC2pCg==
Message-ID: <99B887114EDB1449941CFBC8EC279FA12D016997@PRVPEXVS17.corp.twcable.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] Working Group Last Call: draft-ietf-6renum-static-problem-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: Fri, 14 Sep 2012 17:01:42 -0000

We are requesting a Working Group Last Call on this document.  Please revie=
w and provide comments before September 28, since this may be the final rev=
iew of this document.

Thanks,

Lee

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of=
 internet-
> drafts@ietf.org
> Sent: Friday, August 31, 2012 3:00 AM
> To: i-d-announce@ietf.org
> Cc: renum@ietf.org
> Subject: [renum] I-D Action: draft-ietf-6renum-static-problem-01.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the IPv6 Site Renumbering Working Group of =
the IETF.
>
>       Title           : Problem Statement for Renumbering IPv6 Hosts with=
 Static Addresses
>       Author(s)       : Brian Carpenter
>                           Sheng Jiang
>       Filename        : draft-ietf-6renum-static-problem-01.txt
>       Pages           : 12
>       Date            : 2012-08-30
>
> Abstract:
>    This document analyses the problems of updating the IPv6 addresses of
>    hosts in enterprise networks that for operational reasons require
>    static addresses.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6renum-static-problem-01
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-static-problem-01
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

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.

From wesley.george@twcable.com  Fri Sep 14 11:03:04 2012
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 D401C21F8487 for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 11:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.661
X-Spam-Level: 
X-Spam-Status: No, score=-0.661 tagged_above=-999 required=5 tests=[AWL=0.802,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 lg1AN-nK9dqd for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 11:03:04 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 07C3921F847B for <renum@ietf.org>; Fri, 14 Sep 2012 11:03:03 -0700 (PDT)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,423,1344225600"; d="scan'208";a="438813951"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 14 Sep 2012 14:02:01 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Fri, 14 Sep 2012 14:02:16 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "Howard, Lee" <lee.howard@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Date: Fri, 14 Sep 2012 14:02:14 -0400
Thread-Topic: Working Group Last Call: draft-ietf-6renum-enterprise-02.txt
Thread-Index: Ac2MS1AyGfCtBCmORjqQzps1UhuJbgGVvRsQ
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59235DB47277@PRVPEXVS15.corp.twcable.com>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E15@PRVPEXVS17.corp.twcable.com>
In-Reply-To: <99B887114EDB1449941CFBC8EC279FA12CB43E15@PRVPEXVS17.corp.twcable.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: Re: [renum] Working Group Last Call: draft-ietf-6renum-enterprise-02.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: Fri, 14 Sep 2012 18:03:05 -0000

Support publication. Good work on this.


Thanks,

Wes


> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of Howard, Lee
> Sent: Thursday, September 06, 2012 12:19 PM
> To: renum@ietf.org
> Subject: [renum] Working Group Last Call: draft-ietf-6renum-enterprise-
> 02.txt
>
> We are requesting a Working Group Last Call on this document.  Please
> review and provide comments before September 19, since this may be the
> final review of this document.
>
> Thanks,
>
> Lee
>
>
> > -----Original Message-----
> > From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> > Of
> Sheng Jiang
> > Sent: Monday, September 03, 2012 11:44 PM
> > To: internet-drafts@ietf.org; i-d-announce@ietf.org
> > Cc: renum@ietf.org
> > Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-02.txt
> >
> > A new version with minor editorial modifications are submitted. Your
> review and comments
> > are appreciated.
> >
> > Best regards,
> >
> > Sheng
> >
> > >-----Original Message-----
> > >From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On
> > >Behalf Of internet-drafts@ietf.org
> > >Sent: Tuesday, September 04, 2012 10:16 AM
> > >To: i-d-announce@ietf.org
> > >Cc: renum@ietf.org
> > >Subject: [renum] I-D Action: draft-ietf-6renum-enterprise-02.txt
> > >
> > >
> > >A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > > This draft is a work item of the IPv6 Site Renumbering Working Group
> > >of the IETF.
> > >
> > >     Title           : IPv6 Enterprise Network Renumbering Scenarios
> and
> > >Guidelines
> > >     Author(s)       : Sheng Jiang
> > >                          Bing Liu
> > >                          Brian Carpenter
> > >     Filename        : draft-ietf-6renum-enterprise-02.txt
> > >     Pages           : 16
> > >     Date            : 2012-09-03
> > >
> > >Abstract:
> > >   This document analyzes enterprise renumbering events and describes
> > >   the best current practice among the existing renumbering
> mechanisms.
> > >   According to the different stages of renumbering events,
> > >   considerations and best current practices are described in three
> > >   categories: during network design, for preparation of renumbering,
> > >   and during a renumbering operation.
> > >
> > >
> > >The IETF datatracker status page for this draft is:
> > >https://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise
> > >
> > >There's also a htmlized version available at:
> > >http://tools.ietf.org/html/draft-ietf-6renum-enterprise-02
> > >
> > >A diff from the previous version is available at:
> > >http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-enterprise-02
> > >
> > >
> > >Internet-Drafts are also available by anonymous FTP at:
> > >ftp://ftp.ietf.org/internet-drafts/
> > >
> > >_______________________________________________
> > >renum mailing list
> > >renum@ietf.org
> > >https://www.ietf.org/mailman/listinfo/renum
> > _______________________________________________
> > renum mailing list
> > renum@ietf.org
> > https://www.ietf.org/mailman/listinfo/renum
>
>
> 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.
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

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.

From wesley.george@twcable.com  Fri Sep 14 12:39:59 2012
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 AC61C21F8540 for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 12:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.295
X-Spam-Level: 
X-Spam-Status: No, score=-0.295 tagged_above=-999 required=5 tests=[AWL=0.168,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 Gzj+Po-NMB4n for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 12:39:59 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id B8F4521F853E for <renum@ietf.org>; Fri, 14 Sep 2012 12:39:58 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,424,1344225600"; d="scan'208";a="420716357"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 14 Sep 2012 15:39:33 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Fri, 14 Sep 2012 15:39:57 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "Howard, Lee" <lee.howard@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Date: Fri, 14 Sep 2012 15:39:56 -0400
Thread-Topic: [renum] Working Group Last Call: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: Ac2MSv8ivRG0vUeJSx+uTzY+jOkLiwGYvSjA
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59235E0DA40F@PRVPEXVS15.corp.twcable.com>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com>
In-Reply-To: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.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: Re: [renum] Working Group Last Call:	draft-ietf-6renum-gap-analysis-03.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: Fri, 14 Sep 2012 19:39:59 -0000

Generally I think this is good, and it's probably ready to go after a revis=
ion to address WGLC comments.

I do see one area where I've made previous comments that never really made =
it into this gap analysis, which is as it relates to the need for a layer o=
f abstraction for IP-specific configuration within routers/switches and hos=
ts (servers, etc). While you discuss filtering updates in section 7, the nu=
mber of places where a bare IP is configured in your average router is quit=
e a lot more than just there, sometimes even including things like derived =
values (using the unique portion of the loopback address to generate an ISI=
S net ID is common, for example).

Some of this can be solved because IPv6 allows multiple addresses and can d=
o make before break renumbering (changing the addresses on interfaces, BGP =
sessions, etc) but I've said more than once that this is still a fairly man=
ual and resource-intensive process, prone to mistakes. Likewise, use of FQD=
N everywhere that it's supported helps, but it's not supported everywhere y=
ou'd use an IP, nor is it always appropriate on a box that might need the I=
P address in order to keep working even if DNS is dead. We could see a lot =
of benefit from implementations of configuration management tools/CLI that =
allow you to use inheritance so that there is only one place in the config =
where the IP address is defined, whether statically or via dynamic means, a=
nd the rest of the config simply references and inherits it. There are a lo=
t of "devil in the details" problems here about how you automatically updat=
e the inherited or parent/child config without causing disruption or non-de=
terministic behavior, but that's worth discussing as a problem to be solved=
. A well-parameterized configuration management system also has the net ben=
efit of solving some of the filtering problems you discuss. Some of this wo=
uld be implementation-specific, but I think we can articulate clear gaps th=
ere to give good guidance to implementers to make this easier.
With the advent of SDN and Openflow, I'm thinking that it's perhaps less of=
 an intractable problem than it might have been in the past, so for complet=
eness, we do need to discuss it in this gap analysis. It may be appropriate=
 to have this in the static draft, but I wanted to raise it here and let th=
e authors and WG decide how best to address it.

Thanks,

Wes

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of Howard, Lee
> Sent: Thursday, September 06, 2012 12:18 PM
> To: renum@ietf.org
> Subject: [renum] Working Group Last Call: draft-ietf-6renum-gap-
> analysis-03.txt
>
> We are requesting a Working Group Last Call on this document.  Please
> review and provide comments before September 19, since this may be the
> final review of this document.
>
> Thanks,
>
> Lee
>
>
> > -----Original Message-----
> > From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> > Of internet- drafts@ietf.org
> > Sent: Monday, September 03, 2012 11:38 PM
> > To: i-d-announce@ietf.org
> > Cc: renum@ietf.org
> > Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >  This draft is a work item of the IPv6 Site Renumbering Working Group
> of the IETF.
> >
> >       Title           : IPv6 Site Renumbering Gap Analysis
> >       Author(s)       : Bing Liu
> >                           Sheng Jiang
> >                           Brian Carpenter
> >                           Stig Venaas
> >       Filename        : draft-ietf-6renum-gap-analysis-03.txt
> >       Pages           : 20
> >       Date            : 2012-09-03
> >
> > Abstract:
> >    This document briefly introduces the existing mechanisms could be
> >    utilized by IPv6 site renumbering and tries to cover most of the
> >    explicit issues and requirements of IPv6 renumbering. Through the
> gap
> >    analysis, the document provides a basis for future works that
> >    identify and develop solutions or to stimulate such development as
> >    appropriate. The gap analysis is presented following a renumbering
> >    event procedure clue.
> >
> >
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-03
> >
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > renum mailing list
> > renum@ietf.org
> > https://www.ietf.org/mailman/listinfo/renum
>
> Lee Howard
> Director, Network Technology
> Time Warner Cable
> (703) 345-3513
> 13820 Sunrise Valley Drive, Herndon VA 20171
>
>
>
> 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.
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

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.

From wesley.george@twcable.com  Fri Sep 14 12:43:47 2012
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 70A4321F8527 for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 12:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.819
X-Spam-Level: 
X-Spam-Status: No, score=-0.819 tagged_above=-999 required=5 tests=[AWL=0.644,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 IYrUCFh+2Tis for <renum@ietfa.amsl.com>; Fri, 14 Sep 2012 12:43:46 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id B5DC821F84D3 for <renum@ietf.org>; Fri, 14 Sep 2012 12:43:46 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,424,1344225600"; d="scan'208";a="438875432"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 14 Sep 2012 15:43:26 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Fri, 14 Sep 2012 15:43:40 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "Howard, Lee" <lee.howard@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Date: Fri, 14 Sep 2012 15:43:39 -0400
Thread-Topic: [renum] Working Group Last Call: draft-ietf-6renum-static-problem-01.txt
Thread-Index: Ac2SmleJUG5z5HTMQcKalR8udC2pCgAFqppQ
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59235E0DA41B@PRVPEXVS15.corp.twcable.com>
References: <99B887114EDB1449941CFBC8EC279FA12D016997@PRVPEXVS17.corp.twcable.com>
In-Reply-To: <99B887114EDB1449941CFBC8EC279FA12D016997@PRVPEXVS17.corp.twcable.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: Re: [renum] Working Group Last Call:	draft-ietf-6renum-static-problem-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: Fri, 14 Sep 2012 19:43:47 -0000

My comments on the gap-analysis draft may be more appropriately applied to =
section 2.7 of this document. Otherwise I'm happy with this document.

Thanks,

Wes



> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of Howard, Lee
> Sent: Friday, September 14, 2012 1:01 PM
> To: renum@ietf.org
> Subject: [renum] Working Group Last Call: draft-ietf-6renum-static-
> problem-01.txt
>
> We are requesting a Working Group Last Call on this document.  Please
> review and provide comments before September 28, since this may be the
> final review of this document.
>
> Thanks,
>
> Lee
>
> > -----Original Message-----
> > From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> > Of internet- drafts@ietf.org
> > Sent: Friday, August 31, 2012 3:00 AM
> > To: i-d-announce@ietf.org
> > Cc: renum@ietf.org
> > Subject: [renum] I-D Action: draft-ietf-6renum-static-problem-01.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >  This draft is a work item of the IPv6 Site Renumbering Working Group
> of the IETF.
> >
> >       Title           : Problem Statement for Renumbering IPv6 Hosts
> with Static Addresses
> >       Author(s)       : Brian Carpenter
> >                           Sheng Jiang
> >       Filename        : draft-ietf-6renum-static-problem-01.txt
> >       Pages           : 12
> >       Date            : 2012-08-30
> >
> > Abstract:
> >    This document analyses the problems of updating the IPv6 addresses
> of
> >    hosts in enterprise networks that for operational reasons require
> >    static addresses.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-ietf-6renum-static-problem-01
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-static-problem-01
> >
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > renum mailing list
> > renum@ietf.org
> > https://www.ietf.org/mailman/listinfo/renum
>
> 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.
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

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.

From brian.e.carpenter@gmail.com  Sat Sep 15 13:19:02 2012
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 42B0921E803C for <renum@ietfa.amsl.com>; Sat, 15 Sep 2012 13:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[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 a+YxTKLbzc0U for <renum@ietfa.amsl.com>; Sat, 15 Sep 2012 13:19:01 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3C22621F84AF for <renum@ietf.org>; Sat, 15 Sep 2012 13:19:01 -0700 (PDT)
Received: by ieak13 with SMTP id k13so8813609iea.31 for <renum@ietf.org>; Sat, 15 Sep 2012 13:19:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EZ7yJ3H3zXcIU8k5V+IIYJiYyUxUMD37n8D6Tcsme2w=; b=qfqPa2DzY+NFto28TrK52jt7NIr12xoKbrcx7BeezdcZ2UusY0g5MfVK+fjVxgQJcp LLgUP8xF5rJCYF0bWfmcvh6Z81BycKw/bHmJzIbps6IgN6wj2qdNY5jtsLQIQT9K3jUY j1ChOSfOKM5ClvKBKHNt4nxX5mf4srf1db1V5XagsziD52pgxC8kOMv0dEXj/t0pBRS9 lU2Lnh0ZJ0BQmlMmbp0zI2KdmbQ/XioT6NQ3C3zbAtj+5T6cbYleIkRX5B2w/6H5T+cj VRgDtI/X60Jkkh6XPrMH6Ro2HxlRhOslUMCgq5bwxWnZppmIztk/wt27zPbEOtuPaYHk RIkw==
Received: by 10.42.23.207 with SMTP id t15mr5659358icb.3.1347740340456; Sat, 15 Sep 2012 13:19:00 -0700 (PDT)
Received: from [10.255.25.102] (50-76-68-140-static.hfc.comcastbusiness.net. [50.76.68.140]) by mx.google.com with ESMTPS id fu4sm2058989igc.4.2012.09.15.13.18.58 (version=SSLv3 cipher=OTHER); Sat, 15 Sep 2012 13:18:59 -0700 (PDT)
Message-ID: <5054E2C3.80008@gmail.com>
Date: Sat, 15 Sep 2012 21:19:15 +0100
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, Wes" <wesley.george@twcable.com>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com> <2671C6CDFBB59E47B64C10B3E0BD59235E0DA40F@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59235E0DA40F@PRVPEXVS15.corp.twcable.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Working Group Last	Call:	draft-ietf-6renum-gap-analysis-03.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: Sat, 15 Sep 2012 20:19:02 -0000

Wes,

Simply put, I think you're saying that "A well-parameterized configuration management system"
is an essential tool, and I completely agree. Actually defining all the details of
that is a product design issue, but do you think we should aim at a requirements
document for such a tool?

As for whether this should be added as a specific gap in this draft or in
draft-ietf-6renum-static-problem, I'll await guidance from the WG chairs.

Regards
   Brian

On 14/09/2012 20:39, George, Wes wrote:
> Generally I think this is good, and it's probably ready to go after a revision to address WGLC comments.
> 
> I do see one area where I've made previous comments that never really made it into this gap analysis, which is as it relates to the need for a layer of abstraction for IP-specific configuration within routers/switches and hosts (servers, etc). While you discuss filtering updates in section 7, the number of places where a bare IP is configured in your average router is quite a lot more than just there, sometimes even including things like derived values (using the unique portion of the loopback address to generate an ISIS net ID is common, for example).
> 
> Some of this can be solved because IPv6 allows multiple addresses and can do make before break renumbering (changing the addresses on interfaces, BGP sessions, etc) but I've said more than once that this is still a fairly manual and resource-intensive process, prone to mistakes. Likewise, use of FQDN everywhere that it's supported helps, but it's not supported everywhere you'd use an IP, nor is it always appropriate on a box that might need the IP address in order to keep working even if DNS is dead. We could see a lot of benefit from implementations of configuration management tools/CLI that allow you to use inheritance so that there is only one place in the config where the IP address is defined, whether statically or via dynamic means, and the rest of the config simply references and inherits it. There are a lot of "devil in the details" problems here about how you automatically update the inherited or parent/child config without causing disruption or non-deterministic 
beh
>  avior, but that's worth discussing as a problem to be solved. A well-parameterized configuration management system also has the net benefit of solving some of the filtering problems you discuss. Some of this would be implementation-specific, but I think we can articulate clear gaps there to give good guidance to implementers to make this easier.
> With the advent of SDN and Openflow, I'm thinking that it's perhaps less of an intractable problem than it might have been in the past, so for completeness, we do need to discuss it in this gap analysis. It may be appropriate to have this in the static draft, but I wanted to raise it here and let the authors and WG decide how best to address it.
> 
> Thanks,
> 
> Wes
> 
>> -----Original Message-----
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
>> Of Howard, Lee
>> Sent: Thursday, September 06, 2012 12:18 PM
>> To: renum@ietf.org
>> Subject: [renum] Working Group Last Call: draft-ietf-6renum-gap-
>> analysis-03.txt
>>
>> We are requesting a Working Group Last Call on this document.  Please
>> review and provide comments before September 19, since this may be the
>> final review of this document.
>>
>> Thanks,
>>
>> Lee
>>
>>
>>> -----Original Message-----
>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
>>> Of internet- drafts@ietf.org
>>> Sent: Monday, September 03, 2012 11:38 PM
>>> To: i-d-announce@ietf.org
>>> Cc: renum@ietf.org
>>> Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
>>>
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>>  This draft is a work item of the IPv6 Site Renumbering Working Group
>> of the IETF.
>>>       Title           : IPv6 Site Renumbering Gap Analysis
>>>       Author(s)       : Bing Liu
>>>                           Sheng Jiang
>>>                           Brian Carpenter
>>>                           Stig Venaas
>>>       Filename        : draft-ietf-6renum-gap-analysis-03.txt
>>>       Pages           : 20
>>>       Date            : 2012-09-03
>>>
>>> Abstract:
>>>    This document briefly introduces the existing mechanisms could be
>>>    utilized by IPv6 site renumbering and tries to cover most of the
>>>    explicit issues and requirements of IPv6 renumbering. Through the
>> gap
>>>    analysis, the document provides a basis for future works that
>>>    identify and develop solutions or to stimulate such development as
>>>    appropriate. The gap analysis is presented following a renumbering
>>>    event procedure clue.
>>>
>>>
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
>>>
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03
>>>
>>> A diff from the previous version is available at:
>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-6renum-gap-analysis-03
>>>
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> _______________________________________________
>>> renum mailing list
>>> renum@ietf.org
>>> https://www.ietf.org/mailman/listinfo/renum
>> Lee Howard
>> Director, Network Technology
>> Time Warner Cable
>> (703) 345-3513
>> 13820 Sunrise Valley Drive, Herndon VA 20171
>>
>>
>>
>> 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.
>> _______________________________________________
>> renum mailing list
>> renum@ietf.org
>> https://www.ietf.org/mailman/listinfo/renum
> 
> 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.
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
> 

From leo.liubing@huawei.com  Sun Sep 16 23:20:39 2012
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 D9AFD21E8034 for <renum@ietfa.amsl.com>; Sun, 16 Sep 2012 23:20:39 -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=[AWL=0.000,  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 YCdfN4gw2h9Z for <renum@ietfa.amsl.com>; Sun, 16 Sep 2012 23:20:39 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 933DE21F84CE for <renum@ietf.org>; Sun, 16 Sep 2012 23:20:37 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AJS73872; Mon, 17 Sep 2012 06:20:36 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 17 Sep 2012 07:20:17 +0100
Received: from SZXEML436-HUB.china.huawei.com (10.72.61.64) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 17 Sep 2012 07:20:34 +0100
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml436-hub.china.huawei.com ([10.72.61.64]) with mapi id 14.01.0323.003; Mon, 17 Sep 2012 14:20:27 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "George, Wes" <wesley.george@twcable.com>, "Howard, Lee" <lee.howard@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: [renum] Working Group Last	Call: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: AQHNkrDAQnB3tCw8W0a8DxHnNs4ki5eOE54g
Date: Mon, 17 Sep 2012 06:20:26 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F4529354B16@szxeml509-mbs>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com> <2671C6CDFBB59E47B64C10B3E0BD59235E0DA40F@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59235E0DA40F@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.42]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [renum] Working Group Last	Call:	draft-ietf-6renum-gap-analysis-03.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: Mon, 17 Sep 2012 06:20:40 -0000

Hi, Wes

Thanks for your review and comments. I think the issue you pointed out is i=
mportant and need to be discussed.=20
But I'm a little confused about some issues, please see inline.

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of
> George, Wes
> Sent: Saturday, September 15, 2012 3:40 AM
> To: Howard, Lee; renum@ietf.org
> Subject: Re: [renum] Working Group Last Call:
> draft-ietf-6renum-gap-analysis-03.txt
>=20
> Generally I think this is good, and it's probably ready to go after a rev=
ision to
> address WGLC comments.
>=20
> I do see one area where I've made previous comments that never really mad=
e
> it into this gap analysis, which is as it relates to the need for a layer=
 of
> abstraction for IP-specific configuration within routers/switches and hos=
ts
> (servers, etc). While you discuss filtering updates in section 7, the num=
ber of
> places where a bare IP is configured in your average router is quite a lo=
t more
> than just there, sometimes even including things like derived values (usi=
ng the
> unique portion of the loopback address to generate an ISIS net ID is comm=
on,
> for example).

[Bing] In fact, when we used the word "filter", we did intend to treat it a=
s a common concept rather than some specific instances such as ACL. Besides=
 the DNS records and the in-host server addresses, we treated all the entri=
es containing IP_addresses-as-IDs as "filter", I think it is align with you=
r "a layer of abstraction for IP-specific configuration"(however, we didn't=
 cover the consideration of the derived values, thanks for pointing it out)=
. Did I understand your "abstraction" correctly? If I did, then the problem=
 is just maybe the word "filter" and the relevant description are not suffi=
cient enough to represent the abstraction, then we can modify them.

> Some of this can be solved because IPv6 allows multiple addresses and can=
 do
> make before break renumbering (changing the addresses on interfaces, BGP
> sessions, etc) but I've said more than once that this is still a fairly m=
anual and
> resource-intensive process, prone to mistakes. Likewise, use of FQDN
> everywhere that it's supported helps, but it's not supported everywhere y=
ou'd
> use an IP, nor is it always appropriate on a box that might need the IP a=
ddress
> in order to keep working even if DNS is dead. We could see a lot of benef=
it from
> implementations of configuration management tools/CLI that allow you to u=
se
> inheritance so that there is only one place in the config where the IP ad=
dress is
> defined, whether statically or via dynamic means, and the rest of the con=
fig
> simply references and inherits it. There are a lot of "devil in the detai=
ls"
> problems here about how you automatically update the inherited or
> parent/child config without causing disruption or non-deterministic beh
>  avior, but that's worth discussing as a problem to be solved. A
> well-parameterized configuration management system also has the net benef=
it
> of solving some of the filtering problems you discuss. Some of this would=
 be
> implementation-specific, but I think we can articulate clear gaps there t=
o give
> good guidance to implementers to make this easier.
> With the advent of SDN and Openflow, I'm thinking that it's perhaps less =
of an
> intractable problem than it might have been in the past, so for completen=
ess,
> we do need to discuss it in this gap analysis. It may be appropriate to h=
ave this
> in the static draft, but I wanted to raise it here and let the authors an=
d WG
> decide how best to address it.

[Bing] The inheritance configuration can make the parameters instead of the=
 specific IP addresses, which provides similar ability of the FQDN, and ind=
eed it doesn't need to rely on DNS systems. But then it will rely on the ma=
nagement system, which may face the problems of compatibility and also avai=
lability. So I'm afraid this may be the same assurance level comparing to t=
he DNS.=20
And, if we consider how to implement parameterized configuration management=
 system as gaps, it has an implicit assumption that parameterized managemen=
t is an already chosen solution for the "abstraction for IP-specific config=
uration" gap. So I'm not sure currently we should only treat the parameteri=
zed management as a candidate solution, or we need to do further gap analys=
is of it in the draft.

> Thanks,
>=20
> Wes
>=20
> > -----Original Message-----
> > From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> > Of Howard, Lee
> > Sent: Thursday, September 06, 2012 12:18 PM
> > To: renum@ietf.org
> > Subject: [renum] Working Group Last Call: draft-ietf-6renum-gap-
> > analysis-03.txt
> >
> > We are requesting a Working Group Last Call on this document.  Please
> > review and provide comments before September 19, since this may be the
> > final review of this document.
> >
> > Thanks,
> >
> > Lee
> >
> >
> > > -----Original Message-----
> > > From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behal=
f
> > > Of internet- drafts@ietf.org
> > > Sent: Monday, September 03, 2012 11:38 PM
> > > To: i-d-announce@ietf.org
> > > Cc: renum@ietf.org
> > > Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
> > >
> > >
> > > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > >  This draft is a work item of the IPv6 Site Renumbering Working Group
> > of the IETF.
> > >
> > >       Title           : IPv6 Site Renumbering Gap Analysis
> > >       Author(s)       : Bing Liu
> > >                           Sheng Jiang
> > >                           Brian Carpenter
> > >                           Stig Venaas
> > >       Filename        : draft-ietf-6renum-gap-analysis-03.txt
> > >       Pages           : 20
> > >       Date            : 2012-09-03
> > >
> > > Abstract:
> > >    This document briefly introduces the existing mechanisms could be
> > >    utilized by IPv6 site renumbering and tries to cover most of the
> > >    explicit issues and requirements of IPv6 renumbering. Through the
> > gap
> > >    analysis, the document provides a basis for future works that
> > >    identify and develop solutions or to stimulate such development as
> > >    appropriate. The gap analysis is presented following a renumbering
> > >    event procedure clue.
> > >
> > >
> > >
> > >
> > > The IETF datatracker status page for this draft is:
> > > https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
> > >
> > > There's also a htmlized version available at:
> > > http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03
> > >
> > > A diff from the previous version is available at:
> > > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-03
> > >
> > >
> > > Internet-Drafts are also available by anonymous FTP at:
> > > ftp://ftp.ietf.org/internet-drafts/
> > >
> > > _______________________________________________
> > > renum mailing list
> > > renum@ietf.org
> > > https://www.ietf.org/mailman/listinfo/renum
> >
> > Lee Howard
> > Director, Network Technology
> > Time Warner Cable
> > (703) 345-3513
> > 13820 Sunrise Valley Drive, Herndon VA 20171
> >
> >
> >
> > 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.
> > _______________________________________________
> > renum mailing list
> > renum@ietf.org
> > https://www.ietf.org/mailman/listinfo/renum
>=20
> 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 disse=
mination,
> 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 print=
out.
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

From leo.liubing@huawei.com  Sun Sep 16 23:49:31 2012
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 5EC6421E8034 for <renum@ietfa.amsl.com>; Sun, 16 Sep 2012 23:49:31 -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=[AWL=0.000,  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 Duqf7iSpU9wX for <renum@ietfa.amsl.com>; Sun, 16 Sep 2012 23:49:29 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D259D21E8039 for <renum@ietf.org>; Sun, 16 Sep 2012 23:49:28 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AJS76201; Mon, 17 Sep 2012 06:49:28 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 17 Sep 2012 07:49:10 +0100
Received: from SZXEML430-HUB.china.huawei.com (10.72.61.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 17 Sep 2012 14:49:27 +0800
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml430-hub.china.huawei.com ([10.72.61.38]) with mapi id 14.01.0323.003; Mon, 17 Sep 2012 14:49:16 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: AQHNik7MInfcpaeCJk6BA/ZG3LCMd5eJNZQogABjNgD//8C7AIAE0WmQ
Date: Mon, 17 Sep 2012 06:49:15 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F4529354B42@szxeml509-mbs>
References: <20120904033758.18836.26105.idtracker@ietfa.amsl.com>, <5D36713D8A4E7348A7E10DF7437A4B9239F3A393@szxeml545-mbx.china.huawei.com> <201209141100044525538@cnnic.cn> <8AE0F17B87264D4CAC7DE0AA6C406F452935456B@szxeml509-mbs> <50532C74.8080803@gmail.com>
In-Reply-To: <50532C74.8080803@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.42]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: 6renum <renum@ietf.org>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.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: Mon, 17 Sep 2012 06:49:31 -0000

SGksIEJyaWFuDQoNClRoYW5rcyBmb3IgeW91ciBjb21tZW50LiANCkkgYWxzbyBub3RpY2VkIHRo
ZSBGUUROLWJhc2VkIHNvbHV0aW9uIGluIFJGQzU4ODcsIGl0IGlzIGEgZ29vZCBjYW5kaWRhdGUg
c29sdXRpb24uDQoNCkJ1dCB0aGUgcHJvYmxlbSBpdHNlbGYgaXMgaW5kZWVkIGEgZ2FwIG5lZWQg
dG8gYmUgbWVudGlvbmVkIGluIHRoZSBkcmFmdC4gSWYgdGhlcmUncyBubyBvYmplY3Rpb24sIEkn
bGwgaW5jbHVkZSBpdCBpbiB0aGUgcmV2aXNpb24uDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCj4gRnJvbTogQnJpYW4gRSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRl
ckBnbWFpbC5jb21dDQo+IFNlbnQ6IEZyaWRheSwgU2VwdGVtYmVyIDE0LCAyMDEyIDk6MDkgUE0N
Cj4gVG86IExpdWJpbmcgKExlbykNCj4gQ2M6IG1hZGk7IFNoZW5nIEppYW5nOyA2cmVudW0NCj4g
U3ViamVjdDogUmU6IFtyZW51bV0gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi02cmVudW0tZ2FwLWFu
YWx5c2lzLTAzLnR4dA0KPiANCj4gSXQgaXMgYSBnb29kIHBvaW50IHRvIG1lbnRpb24uIEFzIGZh
ciBhcyBJIGNhbiB0ZWxsLCB0aGVyZSBpcyBubyBzb2x1dGlvbjsNCj4gc2Vzc2lvbnMgdXNpbmcg
YWRkcmVzcy1iYXNlZCBTQXMgd2lsbCBuZWVkIHRvIHJlbmVnb3RpYXRlIChqdXN0IGxpa2UNCj4g
YSBUQ1Agb3IgVExTIHNlc3Npb24sIGluIGZhY3QpLg0KPiANCj4gU2VlIFJGQyA1ODg3LCBob3dl
dmVyLCB3aGljaCBnaXZlcyB0aGUgc29sdXRpb24gZm9yIHRoZSBWUE4gYXBwbGljYXRpb24NCj4g
b2YgSVBzZWMgKHVzZSBGUUROLWJhc2VkIFNBKS4NCj4gDQo+IEkgbm90aWNlZCB0aGF0IFJGQyA0
MTkyIGRvZXNuJ3QgbWVudGlvbiBJUHNlYyENCj4gDQo+IFJlZ2FyZHMNCj4gICAgQnJpYW4NCj4g
DQo+IA0KPiBPbiAxNC8wOS8yMDEyIDEwOjE5LCBMaXViaW5nIChMZW8pIHdyb3RlOg0KPiA+IEhp
LCBEaQ0KPiA+IFRoYW5rcyBmb3IgeW91ciByZXZpZXcgYW5kIHRoZSBuZXcgY29udHJpYnV0aW9u
Lg0KPiA+IFBlcnNvbmFsbHksIEkgdGhpbmsgdGhlIGlzc3VlIHlvdSBwb2ludGVkIG91dCBpcyB3
b3J0aCB0byBiZSBkb2N1bWVudGVkLiBJZiB0aGUNCj4gSVAgYWRkcmVzc2VzIGFyZSByZW51bWJl
cmVkLCB0aGUgU0Egd291bGQgYmUgZGVmaW5pdGVseSBicm9rZW4uIEJ1dCBJIHdvdWxkDQo+IGxp
a2UgdG8gaGVhciB0aGUgIGNvLWF1dGhvcnMnIGFuZCB0aGUgV0cncyBvcGluaW9ucyBhYm91dCBp
dCwgc2luY2UgaXQgaXMgYmVlbg0KPiB1bmRlciBXR0xDLg0KPiA+IEZvciB0aGUgdGV4dHMsIEkg
dGhpbmsgaXQgbWF5IG5lZWQgdG8gYmUgc2ltcGxpZmllZCwgZXNwZWNpYWxseSB0aGUgSUtFdjIN
Cj4gcmVsZXZhbnQgZGV0YWlscyBtYXkgY29uZnVzZSBwZW9wbGUgdGhhdCBpdCBpcyB0YWxraW5n
IGFib3V0IGEgSUtFdjIgZ2FwLCBidXQgaW4NCj4gZmFjdCBpdCBpcyBhYm91dCBTQS4NCj4gPg0K
PiA+IEIuUi4NCj4gPiBCaW5nDQo+ID4NCj4gPiBGcm9tOiByZW51bS1ib3VuY2VzQGlldGYub3Jn
IFttYWlsdG86cmVudW0tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmDQo+IE9mIERpIE1hDQo+
ID4gU2VudDogRnJpZGF5LCBTZXB0ZW1iZXIgMTQsIDIwMTIgMTE6MDAgQU0NCj4gPiBUbzogU2hl
bmcgSmlhbmcNCj4gPiBDYzogNnJlbnVtDQo+ID4gU3ViamVjdDogUmU6IFtyZW51bV0gSS1EIEFj
dGlvbjogZHJhZnQtaWV0Zi02cmVudW0tZ2FwLWFuYWx5c2lzLTAzLnR4dA0KPiA+DQo+ID4gSSBh
bSBpbiBmYXZvciBvZiBtb3ZpbmcgZm9yd2FyZCB0aGlzIHdvcmsuDQo+ID4NCj4gPiBZZXQgYXMg
YSBkb2N1bWVudCBwcm92aWRpbmcgYSBiYXNpcyBmb3IgZnV0dXJlIHdvcmtzIHRoYXQgaWRlbnRp
ZnkgYW5kIGRldmVsb3ANCj4gc29sdXRpb25zIG9yIHRvIHN0aW11bGF0ZSBzdWNoIGRldmVsb3Bt
ZW50IGFzIGFwcHJvcHJpYXRlLCB0aGlzIGRyYWZ0IG1pZ2h0DQo+IG1ha2UgSVBTZWMgU2VjdXJp
dHkgQXNzb2NpYXRpb24gKFNBKSBtYW5hZ2VtZW50IGluY2x1ZGVkLCBjb25zaWRlcmluZyBJUFNl
Yw0KPiBTQSBpcyBhIGtpbmQgb2YgSVAgYWRkcmVzcyBvcmllbnRlZCAiY29ubmVjdGlvbiIgdGhh
dCBjYW5ub3QgZnVuY3Rpb24gYWZ0ZXIgdGhlDQo+IGNoYW5nZSBvZiB0aGUgaW52b2x2ZWQgSVAg
YWRkcmVzc2VzLCB3aGljaCBtZWFucyBleHRyYSBjb25maWd1cmF0aW9uIG9mIFNBDQo+IHBhcmFt
ZXRlcnMgaXMgaW5ldml0YWJsZSBhZnRlciBuZXR3b3JrIHJlbnVtYmVyaW5nLg0KPiA+DQo+ID4g
U28sIEkgcHJvcG9zZSBhZGRpbmcgc29tZSB3b3JkcyBpbnRvIHRoaXMgZHJhZnQgYXMgU2VjdGlv
biA4LjMgKElQU2VjIFNBDQo+IE1hbmFnZW1lbnQpLCBhIHNlY3RvciBvZiBTZWN0aW9uIDggKE1p
c2NlbGxhbmVvdXMpLCB3aGljaCBpcyBkZXNjcmliZWQgYXMNCj4gZm9sbG93czoNCj4gPg0KPiA+
IE5ldHdvcmsgcmVudW1iZXJpbmcgZXZlbnRzIGdldCBuZXR3b3JraW5nIG1lY2hhbmlzbXMgdGhh
dCBhcmUgYm91bmQgdG8NCj4gSVAgYWRkcmVzc2VzLCBvciBhcHBsaWNhdGlvbnMgdXNpbmcgc3Bl
Y2lmaWMgSVAgYWRkcmVzc2VzLCBpbnZvbHZlZC4gQXMgZGVmaW5lZCBpbg0KPiBbUkZDNDMwMV0s
IElQU2VjIFNlY3VyaXR5IEFzc29jaWF0aW9uIChTQSksIGFzIGEga2luZCBvZiBJUCBhZGRyZXNz
IG9yaWVudGVkDQo+ICJjb25uZWN0aW9uIiwgY2Fubm90IGZ1bmN0aW9uIGFmdGVyIHRoZSBjaGFu
Z2Ugb2YgdGhlIGludm9sdmVkIElQIGFkZHJlc3NlcywNCj4gd2hpY2ggbWVhbnMgZXh0cmEgY29u
ZmlndXJhdGlvbiBvZiBTQSBwYXJhbWV0ZXJzIGlzIGluZXZpdGFibGUgYWZ0ZXIgbmV0d29yaw0K
PiByZW51bWJlcmluZy4NCj4gPg0KPiA+IFNBIGlzIGEgImNvbm5lY3Rpb24iIHRoYXQgcHJvdmlk
ZXMgc2VjdXJpdHkgc2VydmljZXMgdG8gdGhlIHRyYWZmaWMgY2FycmllZCBieSBpdA0KPiBhbmQg
ZGV0YWlscyB0aGUga2V5IGFuZCBhbGdvcml0aG0gdGhhdCB0aGUgSVBTZWMgY29ubmVjdGlvbiBy
ZWxpZXMgb24uIFNBIGNhbiBiZQ0KPiBlc3RhYmxpc2hlZCB3aXRoIG1hbnVhbCBjb25maWd1cmF0
aW9uIGJ5IHRoZSBhZG1pbmlzdHJhdG9yLiBJS0V2MiBbUkZDNTk5Nl0NCj4gZWxpbWluYXRlcyBt
YW51YWwgcmVjb25maWd1cmF0aW9uLiBJdCBlbXBsb3lzIHR3byByb3VuZHMgb2YgbWVzc2FnZQ0K
PiBleGNoYW5nZXMuIFRoZSBmaXJzdCBleGNoYW5nZSBvZiBtZXNzYWdlcyBlc3RhYmxpc2hlcyBh
IHRydXN0IHJlbGF0aW9uc2hpcA0KPiBiZXR3ZWVuIHRoZSB0d28gSUtFdjIgcGFydGljaXBhbnRz
LiBUaGlzIGV4Y2hhbmdlIHVzZXMgdHdvIGF1dGhlbnRpY2F0aW9uDQo+IG1ldGhvZHMsIGRpZ2l0
YWwgc2lnbmF0dXJlIGFuZCBwcmUtc2hhcmVkIGtleS4gVGhlIGRpZ2l0YWwgc2lnbmF0dXJlIG1l
dGhvZA0KPiBuZWVkcyBjZXJ0aWZpY2F0ZSBtYW5hZ2VtZW50LiBJZiB0aGUgcGFydGljaXBhbnRz
IGFyZSBub3QgY29uZmlndXJlZCB3aXRoIHRoZQ0KPiBzYW1lIHRydXN0IGFuY2hvciwgY2VydGlm
aWNhdGUtYmFzZWQgSUtFdjIgY2Fubm90IGJlIHJlYWxpemVkLiBXaGlsZSB0aGUNCj4gcHJlLXNo
YXJlZCBrZXkgbWV0aG9kIGlzIHRoZSBzaW1wbGVyIG9mIHRoZSBhdXRoZW50aWNhdGlvbiBtZXRo
b2RzIGZvciBJS0V2Mg0KPiBhbmQgcHJlLXNoYXJlZCBrZXlzIGFyZSB0aWVkIHRvIHBhcnRpY3Vs
YXIgSVAgYWRkcmVzc2VzLCB1bmxpa2UgcHVibGljIGtleQ0KPiBjZXJ0aWZpY2F0ZXMgdXNlZCBi
eSBkaWdpdGFsIHNpZ25hdHVyZSBtZXRob2QuIFByZS1zaGFyZWQga2V5IG1ldGhvZCBjYW5ub3Qg
YmUNCj4gdXNlZCB3aXRoIG1vYmlsZSBzeXN0ZW1zIG9yIHN5c3RlbXMgdGhhdCBtYXkgYmUgcmVu
dW1iZXJlZCwgdW5sZXNzIHRoZSByZQ0KPiBudW1iZXJpbmcgaXMgd2l0aGluIHRoZSBwcmV2aW91
c2x5IGRldGVybWluZWQgcmFuZ2Ugb2YgSVAgYWRkcmVzc2VzLiBBbHNvLA0KPiB3aGVuIHByZS1z
aGFyZWQga2V5IGlzIGVtcGxveWVkLCBJS0V2MiBjb21wdXRhdGlvbnMgY2Fubm90IGJlIG9mZmxv
YWRlZCB0bw0KPiB0aGUgYXR0YWNoZWQgaGFyZHdhcmUuIFRoZXJlZm9yZSwgcHJlLXNoYXJlZCBr
ZXkgbWV0aG9kIGZhaWxzIHRvIGJlIGEgcHVyZQ0KPiBhdXRvbWF0aWMgb25lIGFuZCBkb2VzIG5v
dCBnbyB3ZWxsIHdpdGggbmV0d29yayByZW51bWJlcmluZy4gQSBtZWNoYW5pc20NCj4gdGhhdCBp
cyBhYmxlIHRvIGludGVncmF0ZSBTQSBtYW5hZ2VtZW50IGludG8gSVAgYWRkcmVzcyBhc3NpZ25t
ZW50IGluIGFuDQo+IGF1dG9tYXRpYyBhbmQgYW4gYWRhcHRpdmUgbWFubmVyIGlzIGRlc2lyZWQg
dG8gZ28gd2l0aCBuZXR3b3JrIHJlbnVtYmVyaW5nLg0KPiA+DQo+ID4NCj4gPiBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPiA+IERpIE1hDQo+ID4gQ05OSUMgQWR2YW5jZWQgUmVz
ZWFyY2ggRGVwYXJ0bWVudA0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KPiA+IENoaW5hIEludGVybmV0IE5ldHdvcmsgSW5mb3JtYXRpb24g
Q2VudGVyDQo+ID4gVGVsOiAoODYxMCktNTg4MTMyMTYNCj4gPiBIdHRwczovL3d3dy5jbm5pYy5j
bg0KPiA+IEFkZDogNCwgU291dGggNHRoIFN0cmVldCwgWmhvbmdndWFuY3VuDQo+ID4gSGFpZGlh
biBEaXN0cmljdCwgQmVpamluZw0KPiA+IFAuUi5DaGluYSAxMDAxOTANCj4gPiBQT0I6IEJlaWpp
bmcgMzQ5LCBCcmFuY2ggNg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4gPg0KPiA+IEZyb206IFNoZW5nIEppYW5nPG1haWx0bzpqaWFu
Z3NoZW5nQGh1YXdlaS5jb20+DQo+ID4gRGF0ZTogMjAxMi0wOS0wNCAxMTo0NA0KPiA+IFRvOiBp
bnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc8bWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZz47
DQo+IGktZC1hbm5vdW5jZUBpZXRmLm9yZzxtYWlsdG86aS1kLWFubm91bmNlQGlldGYub3JnPg0K
PiA+IENDOiByZW51bUBpZXRmLm9yZzxtYWlsdG86cmVudW1AaWV0Zi5vcmc+DQo+ID4gU3ViamVj
dDogUmU6IFtyZW51bV0gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi02cmVudW0tZ2FwLWFuYWx5c2lz
LTAzLnR4dA0KPiA+IEEgbmV3IHZlcnNpb24gd2l0aCBtaW5vciBlZGl0b3JpYWwgbW9kaWZpY2F0
aW9ucyBhcmUgc3VibWl0dGVkLiBZb3VyIHJldmlldw0KPiBhbmQgY29tbWVudHMgYXJlIGFwcHJl
Y2lhdGVkLg0KPiA+DQo+ID4gQmVzdCByZWdhcmRzLA0KPiA+DQo+ID4gU2hlbmcNCj4gPg0KPiA+
PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+PiBGcm9tOiByZW51bS1ib3VuY2VzQGll
dGYub3JnIFttYWlsdG86cmVudW0tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmDQo+ID4+IE9m
IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZw0KPiA+PiBTZW50OiBUdWVzZGF5LCBTZXB0ZW1iZXIg
MDQsIDIwMTIgMTE6MzggQU0NCj4gPj4gVG86IGktZC1hbm5vdW5jZUBpZXRmLm9yZw0KPiA+PiBD
YzogcmVudW1AaWV0Zi5vcmcNCj4gPj4gU3ViamVjdDogW3JlbnVtXSBJLUQgQWN0aW9uOiBkcmFm
dC1pZXRmLTZyZW51bS1nYXAtYW5hbHlzaXMtMDMudHh0DQo+ID4+DQo+ID4+DQo+ID4+IEEgTmV3
IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURy
YWZ0cw0KPiBkaXJlY3Rvcmllcy4NCj4gPj4gVGhpcyBkcmFmdCBpcyBhIHdvcmsgaXRlbSBvZiB0
aGUgSVB2NiBTaXRlIFJlbnVtYmVyaW5nIFdvcmtpbmcgR3JvdXAgb2YgdGhlDQo+ID4+IElFVEYu
DQo+ID4+DQo+ID4+IFRpdGxlICAgICAgICAgICA6IElQdjYgU2l0ZSBSZW51bWJlcmluZyBHYXAg
QW5hbHlzaXMNCj4gPj4gQXV0aG9yKHMpICAgICAgIDogQmluZyBMaXUNCj4gPj4gICAgICAgICAg
ICAgICAgICAgICAgICAgIFNoZW5nIEppYW5nDQo+ID4+ICAgICAgICAgICAgICAgICAgICAgICAg
ICBCcmlhbiBDYXJwZW50ZXINCj4gPj4gICAgICAgICAgICAgICAgICAgICAgICAgIFN0aWcgVmVu
YWFzDQo+ID4+IEZpbGVuYW1lICAgICAgICA6IGRyYWZ0LWlldGYtNnJlbnVtLWdhcC1hbmFseXNp
cy0wMy50eHQNCj4gPj4gUGFnZXMgICAgICAgICAgIDogMjANCj4gPj4gRGF0ZSAgICAgICAgICAg
IDogMjAxMi0wOS0wMw0KPiA+Pg0KPiA+PiBBYnN0cmFjdDoNCj4gPj4gICBUaGlzIGRvY3VtZW50
IGJyaWVmbHkgaW50cm9kdWNlcyB0aGUgZXhpc3RpbmcgbWVjaGFuaXNtcyBjb3VsZCBiZQ0KPiA+
PiAgIHV0aWxpemVkIGJ5IElQdjYgc2l0ZSByZW51bWJlcmluZyBhbmQgdHJpZXMgdG8gY292ZXIg
bW9zdCBvZiB0aGUNCj4gPj4gICBleHBsaWNpdCBpc3N1ZXMgYW5kIHJlcXVpcmVtZW50cyBvZiBJ
UHY2IHJlbnVtYmVyaW5nLiBUaHJvdWdoIHRoZSBnYXANCj4gPj4gICBhbmFseXNpcywgdGhlIGRv
Y3VtZW50IHByb3ZpZGVzIGEgYmFzaXMgZm9yIGZ1dHVyZSB3b3JrcyB0aGF0DQo+ID4+ICAgaWRl
bnRpZnkgYW5kIGRldmVsb3Agc29sdXRpb25zIG9yIHRvIHN0aW11bGF0ZSBzdWNoIGRldmVsb3Bt
ZW50IGFzDQo+ID4+ICAgYXBwcm9wcmlhdGUuIFRoZSBnYXAgYW5hbHlzaXMgaXMgcHJlc2VudGVk
IGZvbGxvd2luZyBhIHJlbnVtYmVyaW5nDQo+ID4+ICAgZXZlbnQgcHJvY2VkdXJlIGNsdWUuDQo+
ID4+DQo+ID4+DQo+ID4+DQo+ID4+DQo+ID4+IFRoZSBJRVRGIGRhdGF0cmFja2VyIHN0YXR1cyBw
YWdlIGZvciB0aGlzIGRyYWZ0IGlzOg0KPiA+PiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1pZXRmLTZyZW51bS1nYXAtYW5hbHlzaXMNCj4gPj4NCj4gPj4gVGhlcmUncyBh
bHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6DQo+ID4+IGh0dHA6Ly90b29scy5p
ZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtNnJlbnVtLWdhcC1hbmFseXNpcy0wMw0KPiA+Pg0KPiA+
PiBBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUgYXQ6DQo+ID4+
IGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWlldGYtNnJlbnVtLWdhcC1h
bmFseXNpcy0wMw0KPiA+Pg0KPiA+Pg0KPiA+PiBJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZh
aWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQo+ID4+IGZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRl
cm5ldC1kcmFmdHMvDQo+ID4+DQo+ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fDQo+ID4+IHJlbnVtIG1haWxpbmcgbGlzdA0KPiA+PiByZW51bUBpZXRm
Lm9yZw0KPiA+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JlbnVtDQo+
ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiBy
ZW51bSBtYWlsaW5nIGxpc3QNCj4gPiByZW51bUBpZXRmLm9yZw0KPiA+IGh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vcmVudW0NCj4gPg0KPiA+DQo+ID4NCj4gPiAtLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0NCj4gPg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+ID4gcmVudW0gbWFpbGluZyBsaXN0DQo+ID4gcmVudW1AaWV0Zi5vcmcNCj4g
PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JlbnVtDQo=

From wesley.george@twcable.com  Mon Sep 17 07:52:19 2012
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 D2DC121F869D for <renum@ietfa.amsl.com>; Mon, 17 Sep 2012 07:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.4
X-Spam-Level: 
X-Spam-Status: No, score=-0.4 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 D5zJkyuA6FV1 for <renum@ietfa.amsl.com>; Mon, 17 Sep 2012 07:52:15 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 432CF21F86DF for <renum@ietf.org>; Mon, 17 Sep 2012 07:52:14 -0700 (PDT)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,435,1344225600"; d="scan'208";a="421476607"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 17 Sep 2012 10:51:36 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Mon, 17 Sep 2012 10:52:09 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Mon, 17 Sep 2012 10:52:09 -0400
Thread-Topic: [renum] Working Group Last	Call: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: Ac2Tf1l4SkYEqMzUReaKVTZRnV3hCwBZAZAw
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59235E935B7E@PRVPEXVS15.corp.twcable.com>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com> <2671C6CDFBB59E47B64C10B3E0BD59235E0DA40F@PRVPEXVS15.corp.twcable.com> <5054E2C3.80008@gmail.com>
In-Reply-To: <5054E2C3.80008@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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Working Group Last	Call:	draft-ietf-6renum-gap-analysis-03.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: Mon, 17 Sep 2012 14:52:20 -0000

PiBGcm9tOiBCcmlhbiBFIENhcnBlbnRlciBbbWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWls
LmNvbV0NCg0KPiBTaW1wbHkgcHV0LCBJIHRoaW5rIHlvdSdyZSBzYXlpbmcgdGhhdCAiQSB3ZWxs
LXBhcmFtZXRlcml6ZWQNCj4gY29uZmlndXJhdGlvbiBtYW5hZ2VtZW50IHN5c3RlbSINCj4gaXMg
YW4gZXNzZW50aWFsIHRvb2wsIGFuZCBJIGNvbXBsZXRlbHkgYWdyZWUuIEFjdHVhbGx5IGRlZmlu
aW5nIGFsbCB0aGUNCj4gZGV0YWlscyBvZiB0aGF0IGlzIGEgcHJvZHVjdCBkZXNpZ24gaXNzdWUs
IGJ1dCBkbyB5b3UgdGhpbmsgd2Ugc2hvdWxkDQo+IGFpbSBhdCBhIHJlcXVpcmVtZW50cyBkb2N1
bWVudCBmb3Igc3VjaCBhIHRvb2w/DQo+DQoNCltXRUddIHdlbGwsIGRlZmluaW5nIHN1Y2ggYSB0
aGluZyBtaWdodCBiZSB1c2VmdWwsIGJ1dCBJIHRoaW5rIHRoYXQgaXQncyBub3Qgc29tZXRoaW5n
IHNwZWNpZmljIHRvIHJlbnVtYmVyaW5nLiBUaGVyZSBhcmUgYSBsb3Qgb2YgYWRkaXRpb25hbCBy
ZXF1aXJlbWVudHMgYmV5b25kIHJlbnVtYmVyaW5nIHRoYXQgd291bGQgbmVlZCB0byBiZSBjb25z
aWRlcmVkLiBJdCBtaWdodCBiZSBhcHByb3ByaWF0ZSB0byBkaXNjdXNzIHRoZSByZW51bWJlcmlu
Zy1zcGVjaWZpYyBjb25zaWRlcmF0aW9ucy9yZXF1aXJlbWVudHMgaW4gYSBnYXAgYW5hbHlzaXMs
IGJ1dCB0byBub3RlIHRoYXQgZGVmaW5pbmcgYSBjb21wbGV0ZSBsaXN0IG9mIHJlcXVpcmVtZW50
cyBmb3IgYSBwYXJhbWV0ZXJpemVkIGNvbmZpZ3VyYXRpb24gbWFuYWdlbWVudCBzeXN0ZW0gaXMg
YSBnb29kIGdvYWwgYnV0IG91dCBvZiBzY29wZSBmb3IgdGhpcyBkb2N1bWVudC4NCg0KVGhhbmtz
DQpXZXMgR2VvcmdlDQoNClRoaXMgRS1tYWlsIGFuZCBhbnkgb2YgaXRzIGF0dGFjaG1lbnRzIG1h
eSBjb250YWluIFRpbWUgV2FybmVyIENhYmxlIHByb3ByaWV0YXJ5IGluZm9ybWF0aW9uLCB3aGlj
aCBpcyBwcml2aWxlZ2VkLCBjb25maWRlbnRpYWwsIG9yIHN1YmplY3QgdG8gY29weXJpZ2h0IGJl
bG9uZ2luZyB0byBUaW1lIFdhcm5lciBDYWJsZS4gVGhpcyBFLW1haWwgaXMgaW50ZW5kZWQgc29s
ZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9yIGVudGl0eSB0byB3aGljaCBpdCBp
cyBhZGRyZXNzZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQgb2YgdGhp
cyBFLW1haWwsIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVkIHRoYXQgYW55IGRpc3NlbWluYXRpb24s
IGRpc3RyaWJ1dGlvbiwgY29weWluZywgb3IgYWN0aW9uIHRha2VuIGluIHJlbGF0aW9uIHRvIHRo
ZSBjb250ZW50cyBvZiBhbmQgYXR0YWNobWVudHMgdG8gdGhpcyBFLW1haWwgaXMgc3RyaWN0bHkg
cHJvaGliaXRlZCBhbmQgbWF5IGJlIHVubGF3ZnVsLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlz
IEUtbWFpbCBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGltbWVkaWF0ZWx5IGFu
ZCBwZXJtYW5lbnRseSBkZWxldGUgdGhlIG9yaWdpbmFsIGFuZCBhbnkgY29weSBvZiB0aGlzIEUt
bWFpbCBhbmQgYW55IHByaW50b3V0Lg0K

From wesley.george@twcable.com  Mon Sep 17 08:16:39 2012
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 1BFB121F8714 for <renum@ietfa.amsl.com>; Mon, 17 Sep 2012 08:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.907
X-Spam-Level: 
X-Spam-Status: No, score=-0.907 tagged_above=-999 required=5 tests=[AWL=0.556,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 33JVCpw+bZVD for <renum@ietfa.amsl.com>; Mon, 17 Sep 2012 08:16:38 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id EE9BE21F8713 for <renum@ietf.org>; Mon, 17 Sep 2012 08:16:37 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,437,1344225600"; d="scan'208";a="439676859"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 17 Sep 2012 11:15:53 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Mon, 17 Sep 2012 11:16:12 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "Liubing (Leo)" <leo.liubing@huawei.com>, "Howard, Lee" <lee.howard@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Date: Mon, 17 Sep 2012 11:16:11 -0400
Thread-Topic: [renum] Working Group Last	Call: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: AQHNkrDAQnB3tCw8W0a8DxHnNs4ki5eOE54ggACDDWA=
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59235E935BE1@PRVPEXVS15.corp.twcable.com>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com> <2671C6CDFBB59E47B64C10B3E0BD59235E0DA40F@PRVPEXVS15.corp.twcable.com> <8AE0F17B87264D4CAC7DE0AA6C406F4529354B16@szxeml509-mbs>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F4529354B16@szxeml509-mbs>
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: Re: [renum] Working Group Last	Call:	draft-ietf-6renum-gap-analysis-03.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: Mon, 17 Sep 2012 15:16:39 -0000

> From: Liubing (Leo) [mailto:leo.liubing@huawei.com]

> But I'm a little confused about some issues, please see inline.
> >
> [Bing] In fact, when we used the word "filter", we did intend to treat
> it as a common concept rather than some specific instances such as ACL.
> Besides the DNS records and the in-host server addresses, we treated all
> the entries containing IP_addresses-as-IDs as "filter", I think it is
> align with your "a layer of abstraction for IP-specific
> configuration"(however, we didn't cover the consideration of the derived
> values, thanks for pointing it out). Did I understand your "abstraction"
> correctly? If I did, then the problem is just maybe the word "filter"
> and the relevant description are not sufficient enough to represent the
> abstraction, then we can modify them.

[WEG] the word "filter" is at least part of the problem, because it has one=
 or more common definitions within IETF and router implementations in gener=
al, specifically that it is a method to allow some information to pass and =
other info to be dropped, whether traffic, route updates, even things like =
classification. However, I'm not sure that a reader will make the leap to t=
he generic level that you're trying to use here. Yes, it follows that any s=
ort of configuration that is using a filter as I defined above would benefi=
t from this, but that doesn't cover other uses such as using the interface =
IP block to build the remote BGP neighbor session, using the interface IP a=
s the source for a certain type of traffic, etc.
>
> [Bing] The inheritance configuration can make the parameters instead of
> the specific IP addresses, which provides similar ability of the FQDN,
> and indeed it doesn't need to rely on DNS systems. But then it will rely
> on the management system, which may face the problems of compatibility
> and also availability. So I'm afraid this may be the same assurance
> level comparing to the DNS.

[WEG] I realized I was a bit unclear in my previous comments - there are tw=
o types of parameterized configuration, and both are important. The first i=
s one that is self-contained to the individual device - this is where you c=
an define a value once, and then use either keywords or variables to call t=
hat value in the other places where it can be defined in the configuration,=
 a sort of internal inheritance in CLI or other local configuration. This m=
akes it easier to manage a renumbering event by reducing the number of plac=
es in a device's configuration that must be updated. Still means that you h=
ave to touch every device, but you only have to touch it once, instead of h=
aving to scrub the config to ensure that you didn't miss any of the 8 separ=
ate places that a given IP occurs. The second is the more formalized off-bo=
x configuration management system, where you make the changes in the system=
 and it manages how to push the changes to the individual devices. Since we=
're talking about enterprise renumbering, it's not necessarily valid to ass=
ume that there is going to be a formalized configuration management system =
to leverage, so making this easier on a device-by-device basis is an import=
ant goal to highlight.

> And, if we consider how to implement parameterized configuration
> management system as gaps, it has an implicit assumption that
> parameterized management is an already chosen solution for the
> "abstraction for IP-specific configuration" gap. So I'm not sure
> currently we should only treat the parameterized management as a
> candidate solution, or we need to do further gap analysis of it in the
> draft.
>
[WEG] I wouldn't say that it's an already chosen solution, and I don't thin=
k that discussing it leads to that assumption. Most of what we discuss is a=
lternatives that make this easier or help to eliminate the need for some re=
numbering. This is just one additional alternative that may work in some ca=
ses, may not work in others. There is some value in at least a high-level g=
ap analysis of the places where parameterized configuration already exists =
vs the areas where it isn't common and really should be implemented because=
 it's fairly straightforward, vs the areas where perhaps it doesn't help/is=
n't practical.

Thanks,

Wes George

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.

From leo.liubing@huawei.com  Mon Sep 17 21:00:21 2012
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 A343921E809E for <renum@ietfa.amsl.com>; Mon, 17 Sep 2012 21:00:21 -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=[AWL=0.000,  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 wU0BqlLaR1+z for <renum@ietfa.amsl.com>; Mon, 17 Sep 2012 21:00:21 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C4AC621F84C4 for <renum@ietf.org>; Mon, 17 Sep 2012 21:00:19 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKT58099; Tue, 18 Sep 2012 04:00:18 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 18 Sep 2012 04:59:51 +0100
Received: from SZXEML424-HUB.china.huawei.com (10.82.67.163) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 18 Sep 2012 05:00:17 +0100
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml424-hub.china.huawei.com ([10.82.67.163]) with mapi id 14.01.0323.003; Tue, 18 Sep 2012 12:00:11 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "Howard, Lee" <lee.howard@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: [renum] Working Group Last Call: draft-ietf-6renum-static-problem-01.txt
Thread-Index: Ac2SmleJUG5z5HTMQcKalR8udC2pCgCtItBA
Date: Tue, 18 Sep 2012 04:00:10 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F4529355D82@szxeml509-mbs>
References: <99B887114EDB1449941CFBC8EC279FA12D016997@PRVPEXVS17.corp.twcable.com>
In-Reply-To: <99B887114EDB1449941CFBC8EC279FA12D016997@PRVPEXVS17.corp.twcable.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.42]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [renum] Working Group Last Call:	draft-ietf-6renum-static-problem-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, 18 Sep 2012 04:00:21 -0000

Support forwarding this document.

Some minor comments:
1. Several reference need to be updated. draft-liu, draft-jiang, draft-nart=
en, they've already been draft-ietf versions.
2. In the end of Section 3, "Remaining poteintial gaps" seems like some ope=
n questions, probably need to be removed?

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of
> Howard, Lee
> Sent: Saturday, September 15, 2012 1:01 AM
> To: renum@ietf.org
> Subject: [renum] Working Group Last Call:
> draft-ietf-6renum-static-problem-01.txt
>=20
> We are requesting a Working Group Last Call on this document.  Please rev=
iew
> and provide comments before September 28, since this may be the final rev=
iew
> of this document.
>=20
> Thanks,
>=20
> Lee
>=20
> > -----Original Message-----
> > From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of internet-
> > drafts@ietf.org
> > Sent: Friday, August 31, 2012 3:00 AM
> > To: i-d-announce@ietf.org
> > Cc: renum@ietf.org
> > Subject: [renum] I-D Action: draft-ietf-6renum-static-problem-01.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts dire=
ctories.
> >  This draft is a work item of the IPv6 Site Renumbering Working Group o=
f the
> IETF.
> >
> >       Title           : Problem Statement for Renumbering IPv6 Hosts
> with Static Addresses
> >       Author(s)       : Brian Carpenter
> >                           Sheng Jiang
> >       Filename        : draft-ietf-6renum-static-problem-01.txt
> >       Pages           : 12
> >       Date            : 2012-08-30
> >
> > Abstract:
> >    This document analyses the problems of updating the IPv6 addresses o=
f
> >    hosts in enterprise networks that for operational reasons require
> >    static addresses.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-ietf-6renum-static-problem-01
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-static-problem-01
> >
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > renum mailing list
> > renum@ietf.org
> > https://www.ietf.org/mailman/listinfo/renum
>=20
> 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 disse=
mination,
> 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 print=
out.
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

From marc.lampo.ietf@gmail.com  Tue Sep 18 00:54:36 2012
Return-Path: <marc.lampo.ietf@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 9245521F847A for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 00:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 Huh1r6y+Jb8b for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 00:54:35 -0700 (PDT)
Received: from mail-qc0-f194.google.com (mail-qc0-f194.google.com [209.85.216.194]) by ietfa.amsl.com (Postfix) with ESMTP id B330221F8476 for <renum@ietf.org>; Tue, 18 Sep 2012 00:54:35 -0700 (PDT)
Received: by qcbb18 with SMTP id b18so2309922qcb.1 for <renum@ietf.org>; Tue, 18 Sep 2012 00:54:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=uMv46bcojMTzokYJN2dKFxtIiXF6ovimVKKuCFxMkZ0=; b=Ymps9KYnhrxuWVWt3OksBUG3v/iGw9KcKKqVnjSn57kVO5ITUzzusSzzFBd753nwD9 FlSoyoQ0KXkZJv2qK7Gf2/8GV1osVaDx5DejoeM5MyXmvQDqfzkS3BQVgrJ8nSDLsgkf A33okR7zMU6Jb51m4xANqAh45zD7BF2mmKgVkoEKAF+hTt0ZhTkQogfPsdFVbZxAI1rC fy5JhKBi91wdnRv5ULISml8j99xXH1KZnADHKl0/4p+leK3jE7QdDSJMrZdiZblTd/4F v43INBrDjlhnaDxkK8IvVY3tOY2sgIsnAikGhE8oEqvek8qO/8FgZyHyKM2gNlSvuuoj 5gYA==
MIME-Version: 1.0
Received: by 10.229.137.18 with SMTP id u18mr9108557qct.20.1347954875046; Tue, 18 Sep 2012 00:54:35 -0700 (PDT)
Received: by 10.49.133.195 with HTTP; Tue, 18 Sep 2012 00:54:34 -0700 (PDT)
In-Reply-To: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com>
Date: Tue, 18 Sep 2012 09:54:34 +0200
Message-ID: <CAB0C4xOdmHpTN2hVY6R4MAeGZU4kKruMuL0u1wPFgqCkXAsbzg@mail.gmail.com>
From: Marc Lampo <marc.lampo.ietf@gmail.com>
To: "Howard, Lee" <lee.howard@twcable.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Working Group Last Call: draft-ietf-6renum-gap-analysis-03.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, 18 Sep 2012 07:54:36 -0000

Hello (and sorry to jump in so late, but as I just changed employer ...),

my remark is about impact of renumbering on IPSEC VPN definitions.
In my opinion this area is not addressed (enough).

I understand that, via a reference to RFC5887 these is a suggestion to
define addresses on either side of an IPSEC VPN via DNS.
One element is that in practice, not all devices "out there" (some
very widely used) are not capable of defining the valid addresses on
an IPSEC endpoint via DNS.

The second element is about the DNS aspect itself.
Suppose there is a site-to-site VPN between organisations A and B.
Suppose organisation A is capable of defining "valid addresses behind
VPN endpoint" via DNS.
Problem is that device at organisation A needs access to a NS that
"knows" about internal addresses at organisation B.
But if organisation B renumbers its internal network !
How can DNS server accessible/used by VPN endpoint at organisation A
know about new addresses in an automatic way ?


Because there is so little about this subject, in the present version,
I think it is not addressed enough.
Either explicitly, in a paragraph firmly stating recommendations and proced=
ures;
or in section 9, Gaps considered unresolvable, where it can be added
why this is a problem and what admins will have to do manually, if
they renumber.


Kind regards,

Marc Lampo

On Thu, Sep 6, 2012 at 6:17 PM, Howard, Lee <lee.howard@twcable.com> wrote:
> We are requesting a Working Group Last Call on this document.  Please rev=
iew and provide comments before September 19, since this may be the final r=
eview of this document.
>
> Thanks,
>
> Lee
>
>
>> -----Original Message-----
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
>> Of internet- drafts@ietf.org
>> Sent: Monday, September 03, 2012 11:38 PM
>> To: i-d-announce@ietf.org
>> Cc: renum@ietf.org
>> Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories.
>>  This draft is a work item of the IPv6 Site Renumbering Working Group of=
 the IETF.
>>
>>       Title           : IPv6 Site Renumbering Gap Analysis
>>       Author(s)       : Bing Liu
>>                           Sheng Jiang
>>                           Brian Carpenter
>>                           Stig Venaas
>>       Filename        : draft-ietf-6renum-gap-analysis-03.txt
>>       Pages           : 20
>>       Date            : 2012-09-03
>>
>> Abstract:
>>    This document briefly introduces the existing mechanisms could be
>>    utilized by IPv6 site renumbering and tries to cover most of the
>>    explicit issues and requirements of IPv6 renumbering. Through the gap
>>    analysis, the document provides a basis for future works that
>>    identify and develop solutions or to stimulate such development as
>>    appropriate. The gap analysis is presented following a renumbering
>>    event procedure clue.
>>
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-03
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> renum mailing list
>> renum@ietf.org
>> https://www.ietf.org/mailman/listinfo/renum
>
> Lee Howard
> Director, Network Technology
> Time Warner Cable
> (703) 345-3513
> 13820 Sunrise Valley Drive, Herndon VA 20171
>
>
>
> This E-mail and any of its attachments may contain Time Warner Cable prop=
rietary information, which is privileged, confidential, or subject to copyr=
ight 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 t=
he intended recipient of this E-mail, you are hereby notified that any diss=
emination, distribution, copying, or action taken in relation to the conten=
ts of and attachments to this E-mail is strictly prohibited and may be unla=
wful. If you have received this E-mail in error, please notify the sender i=
mmediately and permanently delete the original and any copy of this E-mail =
and any printout.
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

From brian.e.carpenter@gmail.com  Tue Sep 18 05:53:23 2012
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 7E32021E80CA for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 05:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.524
X-Spam-Level: 
X-Spam-Status: No, score=-103.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 GGWPvvTnKjvO for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 05:53:22 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8E48A21E80CC for <renum@ietf.org>; Tue, 18 Sep 2012 05:53:22 -0700 (PDT)
Received: by iec9 with SMTP id 9so3277564iec.31 for <renum@ietf.org>; Tue, 18 Sep 2012 05:53:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=AqPoyjKQTeeWWnjFZEeqVjgA+XHmqLm85EY7WWsynAw=; b=cAj05RAhv5QASh5ZcvdK14/OZ5tJVimWxSZVzRth5FB7JM2H38DZMRbwj66n83gbg6 A560VYpER2amHSpddlUCqCIL1xbbF4z4Dq0jPs+5ftC7qETYAO6SYwtmtF0jCD9/UMZS 07RCP/zAnYkPqwZn8klvRHRgxz9G1Lnyuug9t4tXkM5d9zBS4F9PH6b50ME/gBp2Kv3p IhSDzdx2n+CNQq1IcvCCcvFuHQDb6JhIzbuMSsqKY7ksXLxAmuPeCGmOMwq4PQ1Ytx1R ZNH1SlQZ2Nai8ah7ri/8IbH0N3lE4+eqcri58VB7IeXhfrrdjcLgi9NfizWlC9J6h0+c Gkgw==
Received: by 10.50.187.170 with SMTP id ft10mr10656085igc.36.1347972801988; Tue, 18 Sep 2012 05:53:21 -0700 (PDT)
Received: from [10.255.25.102] (50-76-68-140-static.hfc.comcastbusiness.net. [50.76.68.140]) by mx.google.com with ESMTPS id d19sm10515398igp.6.2012.09.18.05.53.20 (version=SSLv3 cipher=OTHER); Tue, 18 Sep 2012 05:53:21 -0700 (PDT)
Message-ID: <50586EBB.5090206@gmail.com>
Date: Tue, 18 Sep 2012 13:53:15 +0100
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: "Liubing (Leo)" <leo.liubing@huawei.com>
References: <99B887114EDB1449941CFBC8EC279FA12D016997@PRVPEXVS17.corp.twcable.com> <8AE0F17B87264D4CAC7DE0AA6C406F4529355D82@szxeml509-mbs>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F4529355D82@szxeml509-mbs>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Working Group Last	Call:	draft-ietf-6renum-static-problem-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, 18 Sep 2012 12:53:23 -0000

On 18/09/2012 05:00, Liubing (Leo) wrote:
> Support forwarding this document.
> 
> Some minor comments:
> 1. Several reference need to be updated. draft-liu, draft-jiang, draft-narten, they've already been draft-ietf versions.

Thanks, I can do that at the end of WGLC.

> 2. In the end of Section 3, "Remaining poteintial gaps" seems like some open questions, probably need to be removed?

Not so sure I agree - this document is in the charter as part of the gap analysis.
What do other people think?

   Brian

> 
>> -----Original Message-----
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of
>> Howard, Lee
>> Sent: Saturday, September 15, 2012 1:01 AM
>> To: renum@ietf.org
>> Subject: [renum] Working Group Last Call:
>> draft-ietf-6renum-static-problem-01.txt
>>
>> We are requesting a Working Group Last Call on this document.  Please review
>> and provide comments before September 28, since this may be the final review
>> of this document.
>>
>> Thanks,
>>
>> Lee
>>
>>> -----Original Message-----
>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
>> Of internet-
>>> drafts@ietf.org
>>> Sent: Friday, August 31, 2012 3:00 AM
>>> To: i-d-announce@ietf.org
>>> Cc: renum@ietf.org
>>> Subject: [renum] I-D Action: draft-ietf-6renum-static-problem-01.txt
>>>
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>  This draft is a work item of the IPv6 Site Renumbering Working Group of the
>> IETF.
>>>       Title           : Problem Statement for Renumbering IPv6 Hosts
>> with Static Addresses
>>>       Author(s)       : Brian Carpenter
>>>                           Sheng Jiang
>>>       Filename        : draft-ietf-6renum-static-problem-01.txt
>>>       Pages           : 12
>>>       Date            : 2012-08-30
>>>
>>> Abstract:
>>>    This document analyses the problems of updating the IPv6 addresses of
>>>    hosts in enterprise networks that for operational reasons require
>>>    static addresses.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem
>>>
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-ietf-6renum-static-problem-01
>>>
>>> A diff from the previous version is available at:
>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-6renum-static-problem-01
>>>
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> _______________________________________________
>>> renum mailing list
>>> renum@ietf.org
>>> https://www.ietf.org/mailman/listinfo/renum
>> 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.
>> _______________________________________________
>> renum mailing list
>> renum@ietf.org
>> https://www.ietf.org/mailman/listinfo/renum
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
> 

From brian.e.carpenter@gmail.com  Tue Sep 18 06:07:18 2012
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 0C78F21F8783 for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 06:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.539
X-Spam-Level: 
X-Spam-Status: No, score=-103.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 nsECodRcmrGK for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 06:07:17 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 08F9C21F876D for <renum@ietf.org>; Tue, 18 Sep 2012 06:07:16 -0700 (PDT)
Received: by iabz21 with SMTP id z21so6805366iab.31 for <renum@ietf.org>; Tue, 18 Sep 2012 06:07:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=RaAIIDqbnGdk92FYpNyKC5/9Nb+4/uXfgfFD5EfZUlY=; b=MqezDC1+4UJvjqq4KjIpaWdjYrOe2jfjf0XD4cI7hJOD8VgNgdsAsyzFRc4W2CH4Rn 0MFz09ZEckgnUbY2POXb2yAfv+Xl4OkR8U7q0wuoJKr9UJviHeFYC2/5j+0aOeuWBbCG T2+EkeaMmyQ3P4LuLDDARLpHDpOgtl9exDubVU0JERB2zWoHBV8W0AMKuspYa7ZqDUaw E7K2GXBH+ynVAuzUa4YAwEOZPlAQiJt1R8V35+0vRiX4puaVNWHhcVbmjUOVCdSAnvbF ABpVKQc2aIpicAe/S5a3zTLhIpG7sbFOmBNPar7J0TkHnrOacxx3YXCoRxI1wjcFFcmu ei+g==
Received: by 10.50.94.201 with SMTP id de9mr37543igb.61.1347973636273; Tue, 18 Sep 2012 06:07:16 -0700 (PDT)
Received: from [10.255.25.102] (50-76-68-140-static.hfc.comcastbusiness.net. [50.76.68.140]) by mx.google.com with ESMTPS id nh1sm10539873igc.11.2012.09.18.06.07.13 (version=SSLv3 cipher=OTHER); Tue, 18 Sep 2012 06:07:15 -0700 (PDT)
Message-ID: <50587202.9080808@gmail.com>
Date: Tue, 18 Sep 2012 14:07:14 +0100
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: Marc Lampo <marc.lampo.ietf@gmail.com>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com> <CAB0C4xOdmHpTN2hVY6R4MAeGZU4kKruMuL0u1wPFgqCkXAsbzg@mail.gmail.com>
In-Reply-To: <CAB0C4xOdmHpTN2hVY6R4MAeGZU4kKruMuL0u1wPFgqCkXAsbzg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Working Group Last Call:	draft-ietf-6renum-gap-analysis-03.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, 18 Sep 2012 13:07:18 -0000

Marc,

On 18/09/2012 08:54, Marc Lampo wrote:
> Hello (and sorry to jump in so late, but as I just changed employer ...),
> 
> my remark is about impact of renumbering on IPSEC VPN definitions.
> In my opinion this area is not addressed (enough).
> 
> I understand that, via a reference to RFC5887 these is a suggestion to
> define addresses on either side of an IPSEC VPN via DNS.
> One element is that in practice, not all devices "out there" (some
> very widely used) are not capable of defining the valid addresses on
> an IPSEC endpoint via DNS.

True, that's an implementation and deployment gap, not a protocol gap.
All we can do in the IETF is document this kind of gap, since we don't
control implementations.

> 
> The second element is about the DNS aspect itself.
> Suppose there is a site-to-site VPN between organisations A and B.
> Suppose organisation A is capable of defining "valid addresses behind
> VPN endpoint" via DNS.
> Problem is that device at organisation A needs access to a NS that
> "knows" about internal addresses at organisation B.
> But if organisation B renumbers its internal network !
> How can DNS server accessible/used by VPN endpoint at organisation A
> know about new addresses in an automatic way ?

Only if B publishes the appropriate AAAA records in global DNS. Of course
B must also use appropriate DNS TTLs and follow the RFC 4192 overlap
procedure. Then when the IPsec SA breaks, the VPN software will retry
and find the new AAAA record.

Nothing works if people don't use the global DNS correctly, due to misguided
belief in security by obscurity.

> Because there is so little about this subject, in the present version,
> I think it is not addressed enough.
> Either explicitly, in a paragraph firmly stating recommendations and procedures;
> or in section 9, Gaps considered unresolvable, where it can be added
> why this is a problem and what admins will have to do manually, if
> they renumber.

I think we need to separate out implementation and deployment recommendations,
which are in scope for an Ops Area WG, even if we need to add a goal to
the WG Charter.

Regards
    Brian

> Kind regards,
> 
> Marc Lampo
> 
> On Thu, Sep 6, 2012 at 6:17 PM, Howard, Lee <lee.howard@twcable.com> wrote:
>> We are requesting a Working Group Last Call on this document.  Please review and provide comments before September 19, since this may be the final review of this document.
>>
>> Thanks,
>>
>> Lee
>>
>>
>>> -----Original Message-----
>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
>>> Of internet- drafts@ietf.org
>>> Sent: Monday, September 03, 2012 11:38 PM
>>> To: i-d-announce@ietf.org
>>> Cc: renum@ietf.org
>>> Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
>>>
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>  This draft is a work item of the IPv6 Site Renumbering Working Group of the IETF.
>>>
>>>       Title           : IPv6 Site Renumbering Gap Analysis
>>>       Author(s)       : Bing Liu
>>>                           Sheng Jiang
>>>                           Brian Carpenter
>>>                           Stig Venaas
>>>       Filename        : draft-ietf-6renum-gap-analysis-03.txt
>>>       Pages           : 20
>>>       Date            : 2012-09-03
>>>
>>> Abstract:
>>>    This document briefly introduces the existing mechanisms could be
>>>    utilized by IPv6 site renumbering and tries to cover most of the
>>>    explicit issues and requirements of IPv6 renumbering. Through the gap
>>>    analysis, the document provides a basis for future works that
>>>    identify and develop solutions or to stimulate such development as
>>>    appropriate. The gap analysis is presented following a renumbering
>>>    event procedure clue.
>>>
>>>
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
>>>
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03
>>>
>>> A diff from the previous version is available at:
>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-6renum-gap-analysis-03
>>>
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> _______________________________________________
>>> renum mailing list
>>> renum@ietf.org
>>> https://www.ietf.org/mailman/listinfo/renum
>> Lee Howard
>> Director, Network Technology
>> Time Warner Cable
>> (703) 345-3513
>> 13820 Sunrise Valley Drive, Herndon VA 20171
>>
>>
>>
>> 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.
>> _______________________________________________
>> renum mailing list
>> renum@ietf.org
>> https://www.ietf.org/mailman/listinfo/renum
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
> 

From leo.liubing@huawei.com  Tue Sep 18 19:07:05 2012
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 9332C21E8037 for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 19:07:05 -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=[AWL=0.000,  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 BkenHsC3Er3m for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 19:07:04 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 834D121E8055 for <renum@ietf.org>; Tue, 18 Sep 2012 19:07:03 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AJU53748; Wed, 19 Sep 2012 02:07:00 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 19 Sep 2012 03:05:08 +0100
Received: from SZXEML438-HUB.china.huawei.com (10.72.61.73) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 19 Sep 2012 03:05:37 +0100
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml438-hub.china.huawei.com ([10.72.61.73]) with mapi id 14.01.0323.003; Wed, 19 Sep 2012 10:05:31 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "George, Wes" <wesley.george@twcable.com>, "Howard, Lee" <lee.howard@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: [renum] Working Group Last	Call: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: AQHNkrDAQnB3tCw8W0a8DxHnNs4ki5eOE54ggACDDWCAAlSAwA==
Date: Wed, 19 Sep 2012 02:05:30 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F4529355FD2@szxeml509-mbs>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com> <2671C6CDFBB59E47B64C10B3E0BD59235E0DA40F@PRVPEXVS15.corp.twcable.com> <8AE0F17B87264D4CAC7DE0AA6C406F4529354B16@szxeml509-mbs> <2671C6CDFBB59E47B64C10B3E0BD59235E935BE1@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59235E935BE1@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.42]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [renum] Working Group Last	Call:	draft-ietf-6renum-gap-analysis-03.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, 19 Sep 2012 02:07:05 -0000

Hi, Wes

Thanks for your reply. Please see inline.

> -----Original Message-----
> From: George, Wes [mailto:wesley.george@twcable.com]
> Sent: Monday, September 17, 2012 11:16 PM
> To: Liubing (Leo); Howard, Lee; renum@ietf.org
> Subject: RE: [renum] Working Group Last Call:
> draft-ietf-6renum-gap-analysis-03.txt
>=20
> > From: Liubing (Leo) [mailto:leo.liubing@huawei.com]
>=20
> > But I'm a little confused about some issues, please see inline.
> > >
> > [Bing] In fact, when we used the word "filter", we did intend to treat
> > it as a common concept rather than some specific instances such as ACL.
> > Besides the DNS records and the in-host server addresses, we treated al=
l
> > the entries containing IP_addresses-as-IDs as "filter", I think it is
> > align with your "a layer of abstraction for IP-specific
> > configuration"(however, we didn't cover the consideration of the derive=
d
> > values, thanks for pointing it out). Did I understand your "abstraction=
"
> > correctly? If I did, then the problem is just maybe the word "filter"
> > and the relevant description are not sufficient enough to represent the
> > abstraction, then we can modify them.
>=20
> [WEG] the word "filter" is at least part of the problem, because it has o=
ne or
> more common definitions within IETF and router implementations in general=
,
> specifically that it is a method to allow some information to pass and ot=
her info
> to be dropped, whether traffic, route updates, even things like classific=
ation.
> However, I'm not sure that a reader will make the leap to the generic lev=
el that
> you're trying to use here. Yes, it follows that any sort of configuration=
 that is
> using a filter as I defined above would benefit from this, but that doesn=
't cover
> other uses such as using the interface IP block to build the remote BGP
> neighbor session, using the interface IP as the source for a certain type=
 of
> traffic, etc.

[Bing] OK, we can modify the relevant description accordingly. Thanks for c=
larifying the concept.

> >
> > [Bing] The inheritance configuration can make the parameters instead of
> > the specific IP addresses, which provides similar ability of the FQDN,
> > and indeed it doesn't need to rely on DNS systems. But then it will rel=
y
> > on the management system, which may face the problems of compatibility
> > and also availability. So I'm afraid this may be the same assurance
> > level comparing to the DNS.
>=20
> [WEG] I realized I was a bit unclear in my previous comments - there are =
two
> types of parameterized configuration, and both are important. The first i=
s one
> that is self-contained to the individual device - this is where you can d=
efine a
> value once, and then use either keywords or variables to call that value =
in the
> other places where it can be defined in the configuration, a sort of inte=
rnal
> inheritance in CLI or other local configuration. This makes it easier to =
manage a
> renumbering event by reducing the number of places in a device's configur=
ation
> that must be updated. Still means that you have to touch every device, bu=
t you
> only have to touch it once, instead of having to scrub the config to ensu=
re that
> you didn't miss any of the 8 separate places that a given IP occurs. The =
second
> is the more formalized off-box configuration management system, where you
> make the changes in the system and it manages how to push the changes to
> the individual devices. Since we're talking about enterprise renumbering,=
 it's
> not necessarily valid to assume that there is going to be a formalized
> configuration management system to leverage, so making this easier on a
> device-by-device basis is an important goal to highlight.
>=20
[Bing] I like the classification of the two types of parameterized configur=
ation, I think it makes the issue much clearer than before.
When we wrote the draft, we were in fact thinking about the second type of =
configuration. And it is true as you said, probably there is not going to b=
e a formalized configuration management system to leverage. But we consider=
ed this as a gap. There might not be a full solution for the gap, but parti=
ally solution can also benefit renumbering.=20
For the first type, the device-by-device parameterized configuration, actua=
lly we didn't touch it in the draft, we can add some description in the rev=
ision, thanks for pointing it out.

> > And, if we consider how to implement parameterized configuration
> > management system as gaps, it has an implicit assumption that
> > parameterized management is an already chosen solution for the
> > "abstraction for IP-specific configuration" gap. So I'm not sure
> > currently we should only treat the parameterized management as a
> > candidate solution, or we need to do further gap analysis of it in the
> > draft.
> >
> [WEG] I wouldn't say that it's an already chosen solution, and I don't th=
ink that
> discussing it leads to that assumption. Most of what we discuss is altern=
atives
> that make this easier or help to eliminate the need for some renumbering.=
 This
> is just one additional alternative that may work in some cases, may not w=
ork in
> others. There is some value in at least a high-level gap analysis of the =
places
> where parameterized configuration already exists vs the areas where it is=
n't
> common and really should be implemented because it's fairly straightforwa=
rd,
> vs the areas where perhaps it doesn't help/isn't practical.
>=20

> Thanks,
>=20
> Wes George
>=20
> 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 disse=
mination,
> 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 print=
out.

From leo.liubing@huawei.com  Tue Sep 18 19:59:15 2012
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 3338B11E80DE for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 19:59:15 -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=[AWL=0.000,  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 dQiogt-HcWv1 for <renum@ietfa.amsl.com>; Tue, 18 Sep 2012 19:59:14 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A544011E80D2 for <renum@ietf.org>; Tue, 18 Sep 2012 19:59:13 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKU51675; Wed, 19 Sep 2012 02:59:12 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 19 Sep 2012 03:58:19 +0100
Received: from SZXEML421-HUB.china.huawei.com (10.82.67.160) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 19 Sep 2012 10:58:40 +0800
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml421-hub.china.huawei.com ([10.82.67.160]) with mapi id 14.01.0323.003; Wed, 19 Sep 2012 10:58:37 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Marc Lampo <marc.lampo.ietf@gmail.com>
Thread-Topic: [renum] Working Group Last	Call: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: AQHNlZ6LRHT5YMbiOECBYU4Cz/+Is5eQ9x7g
Date: Wed, 19 Sep 2012 02:58:36 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F4529355FF5@szxeml509-mbs>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E09@PRVPEXVS17.corp.twcable.com> <CAB0C4xOdmHpTN2hVY6R4MAeGZU4kKruMuL0u1wPFgqCkXAsbzg@mail.gmail.com> <50587202.9080808@gmail.com>
In-Reply-To: <50587202.9080808@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.42]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Working Group Last	Call:	draft-ietf-6renum-gap-analysis-03.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, 19 Sep 2012 02:59:15 -0000

Hi, Marc & Brian

Thanks for your comments. Please see inline.

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> Sent: Tuesday, September 18, 2012 9:07 PM
> To: Marc Lampo
> Cc: renum@ietf.org
> Subject: Re: [renum] Working Group Last Call:
> draft-ietf-6renum-gap-analysis-03.txt
>=20
> Marc,
>=20
> On 18/09/2012 08:54, Marc Lampo wrote:
> > Hello (and sorry to jump in so late, but as I just changed employer ...=
),
> >
> > my remark is about impact of renumbering on IPSEC VPN definitions.
> > In my opinion this area is not addressed (enough).
> >
[Bing] In previous mails, Di Ma also pointed out this issue, and proposed s=
ome texts. Thank you for pointing it out again, then it is obvious that the=
 IPsec renumbering issue would be probably cared by many people. We'll add =
some more description accordingly.

> > I understand that, via a reference to RFC5887 these is a suggestion to
> > define addresses on either side of an IPSEC VPN via DNS.
> > One element is that in practice, not all devices "out there" (some
> > very widely used) are not capable of defining the valid addresses on
> > an IPSEC endpoint via DNS.
>=20
> True, that's an implementation and deployment gap, not a protocol gap.
> All we can do in the IETF is document this kind of gap, since we don't
> control implementations.
>=20
> >
> > The second element is about the DNS aspect itself.
> > Suppose there is a site-to-site VPN between organisations A and B.
> > Suppose organisation A is capable of defining "valid addresses behind
> > VPN endpoint" via DNS.
> > Problem is that device at organisation A needs access to a NS that
> > "knows" about internal addresses at organisation B.
> > But if organisation B renumbers its internal network !
> > How can DNS server accessible/used by VPN endpoint at organisation A
> > know about new addresses in an automatic way ?
>=20
> Only if B publishes the appropriate AAAA records in global DNS. Of course
> B must also use appropriate DNS TTLs and follow the RFC 4192 overlap
> procedure. Then when the IPsec SA breaks, the VPN software will retry
> and find the new AAAA record.
>=20
> Nothing works if people don't use the global DNS correctly, due to misgui=
ded
> belief in security by obscurity.
>=20
> > Because there is so little about this subject, in the present version,
> > I think it is not addressed enough.
> > Either explicitly, in a paragraph firmly stating recommendations and
> procedures;
> > or in section 9, Gaps considered unresolvable, where it can be added
> > why this is a problem and what admins will have to do manually, if
> > they renumber.
>=20
> I think we need to separate out implementation and deployment
> recommendations,
> which are in scope for an Ops Area WG, even if we need to add a goal to
> the WG Charter.
>=20
[Bing] For the detailed gap analysis you proposed above, I generally agree =
with Brian, we need to distinguish the protocol gaps and implementation gap=
s.
For the recommendations, I think we can consider to add some description in=
 draft-ietf-6renum-enterprise-scenarios, which contains BCPs for renumberin=
g as an important part of the draft.


> Regards
>     Brian
>=20
> > Kind regards,
> >
> > Marc Lampo
> >
> > On Thu, Sep 6, 2012 at 6:17 PM, Howard, Lee <lee.howard@twcable.com>
> wrote:
> >> We are requesting a Working Group Last Call on this document.  Please
> review and provide comments before September 19, since this may be the fi=
nal
> review of this document.
> >>
> >> Thanks,
> >>
> >> Lee
> >>
> >>
> >>> -----Original Message-----
> >>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On
> Behalf
> >>> Of internet- drafts@ietf.org
> >>> Sent: Monday, September 03, 2012 11:38 PM
> >>> To: i-d-announce@ietf.org
> >>> Cc: renum@ietf.org
> >>> Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
> >>>
> >>>
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >>>  This draft is a work item of the IPv6 Site Renumbering Working Group=
 of
> the IETF.
> >>>
> >>>       Title           : IPv6 Site Renumbering Gap Analysis
> >>>       Author(s)       : Bing Liu
> >>>                           Sheng Jiang
> >>>                           Brian Carpenter
> >>>                           Stig Venaas
> >>>       Filename        : draft-ietf-6renum-gap-analysis-03.txt
> >>>       Pages           : 20
> >>>       Date            : 2012-09-03
> >>>
> >>> Abstract:
> >>>    This document briefly introduces the existing mechanisms could be
> >>>    utilized by IPv6 site renumbering and tries to cover most of the
> >>>    explicit issues and requirements of IPv6 renumbering. Through the =
gap
> >>>    analysis, the document provides a basis for future works that
> >>>    identify and develop solutions or to stimulate such development as
> >>>    appropriate. The gap analysis is presented following a renumbering
> >>>    event procedure clue.
> >>>
> >>>
> >>>
> >>>
> >>> The IETF datatracker status page for this draft is:
> >>> https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
> >>>
> >>> There's also a htmlized version available at:
> >>> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-03
> >>>
> >>> A diff from the previous version is available at:
> >>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-03
> >>>
> >>>
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>>
> >>> _______________________________________________
> >>> renum mailing list
> >>> renum@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/renum
> >> Lee Howard
> >> Director, Network Technology
> >> Time Warner Cable
> >> (703) 345-3513
> >> 13820 Sunrise Valley Drive, Herndon VA 20171
> >>
> >>
> >>
> >> 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 disse=
mination,
> 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 print=
out.
> >> _______________________________________________
> >> renum mailing list
> >> renum@ietf.org
> >> https://www.ietf.org/mailman/listinfo/renum
> > _______________________________________________
> > renum mailing list
> > renum@ietf.org
> > https://www.ietf.org/mailman/listinfo/renum
> >
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

From rja.lists@gmail.com  Wed Sep 19 05:43:46 2012
Return-Path: <rja.lists@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 2733521F8620 for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 05:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 JTQSq-qAwr3F for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 05:43:45 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 865F221F867C for <renum@ietf.org>; Wed, 19 Sep 2012 05:43:45 -0700 (PDT)
Received: by qcac10 with SMTP id c10so870632qca.31 for <renum@ietf.org>; Wed, 19 Sep 2012 05:43:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=fixprU0gXyBbScQ7waU0PH4Ms14CfB7Xb319Mbn7VoM=; b=iJVXbWuEMvQdxqigaXZeBN43sUsbHDfHIohUTWVzASGfj5Npar/ryNyvnvHwB/iXJP SyMw/AbIt4P1vX8+B5PoSeoc2+1Yp17cgh9+vC+aBVPCMAghCy/BSOTkXkh4e3CRoArv 8/EHF2em8jLRdkYnfLI12YBfroWdirdFKXJySVMoUgPnbclBkP4j3+6iiiGTmVf9IGqX wnanKVpURCHUNDH2SadMUQvf85CdrLcCMCJnQ8V12TnwLlvJLNk1j5tEOIemJQXFr/fO oFdqxvDNv7NrQyERh5GB9WHkbNfnIJQAxZaRZqHsf5cUPRESOIkg9NX3fATMyMLBQsWW xgPg==
Received: by 10.224.180.7 with SMTP id bs7mr6884969qab.37.1348058617325; Wed, 19 Sep 2012 05:43:37 -0700 (PDT)
Received: from [10.30.20.13] (pool-74-110-100-136.nrflva.fios.verizon.net. [74.110.100.136]) by mx.google.com with ESMTPS id y18sm3861646qaa.15.2012.09.19.05.43.35 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Sep 2012 05:43:36 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 19 Sep 2012 08:43:34 -0400
Message-Id: <D1800D0A-95CA-4EFE-8841-391156232607@gmail.com>
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: Re: [renum] Working Group Last Call: draft-ietf-6renum-static-problem-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, 19 Sep 2012 12:43:46 -0000

Hi,

	While I am not a subscriber to this WG list,
I have a few comments on draft-ietf-6renum-static-problem-01.
I have tried to organise the comments by Section.


Section 2.2, 1st Paragraph:
	For about a decade now, most network-capable printers 
	have silently and automatically enabled SLP without 
	requiring any user interaction.  Such printers often
	use a factory-default algorithm to generate a printer
	name, unless a user has explicitly configured a 
	printer name.
	
	Hosts that are SLP-aware, automatically discover such 
	printers and can use them, without requiring the printer 
	to have a preconfigured fixed IP address.  Many deployed 
	hosts have supported SLP for the past decade.

	So, the statement that "It is also unusual to enable 
	the Service Location Protocol for the same purpose..."
	is not correct in the deployed world.  It was correct
	in the 1990s.  It has not been correct for about a
	decade, however.


Section 2.2, Last Paragraph:
	The DNS Service Discovery (DNS-SD) technology
	described in draft-cheshire-dnsext-dns-sd-11.txt
	is directly relevant and should be both mentioned
	and referenced in this paragraph.  mDNS is great,
	but for the problems of Section 2.2, mDNS really
	works much more effectively in combination with
	DNS-SD.  The RFC Editor web site indicates that
	both DNS-SD and mDNS are IN-QUEUE for publication
	on the IETF standards track.

	Also, since around 2005/2006, many printers have
	shipped with mDNS/DNS-SD silently and automatically
	enabled (in addition to SLP).  Further, many Windows
	PCs, all Apple Macs, and many UNIX systems have
	silently enabled mDNS/DNS-SD support for printing.
	(NOTE: I'm told that when one installs "iTunes" onto 
	MS Windows, the installer silently installs mDNS/DNS-SD 
	support also, since mDNS/DNS-SD is how iTunes finds 
        "shared libraries" of digital content.)  So the last 
        paragraph also needs to be edited to clarify that the 
	mDNS/DNS-SD combination is now widely supported and 
	widely deployed for a range of services, including 
	location of network printers.

Otherwise the I-D seems fine to me.

Yours,

Ran





From brian.e.carpenter@gmail.com  Wed Sep 19 06:41:40 2012
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 96CE321F86FC for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 06:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.562
X-Spam-Level: 
X-Spam-Status: No, score=-103.562 tagged_above=-999 required=5 tests=[AWL=0.038, 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 VuQSAY76nDDz for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 06:41:40 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id D7C5C21F864A for <renum@ietf.org>; Wed, 19 Sep 2012 06:41:39 -0700 (PDT)
Received: by ghbg10 with SMTP id g10so258434ghb.31 for <renum@ietf.org>; Wed, 19 Sep 2012 06:41:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=2ouNdf/SUnmSGia9hd8BWWY3jL4hbCZS4trpLFRRdqM=; b=v+IaD7MOxlwCaA9sxwNReOvGK84S+a0P20Sigtznx02DPmx7ouSVumwKxCkeavYE1U Os7hEqwVoy9rGvMMiws2FEy+xgu+SYH1KuuLg1eNB5VMjbwQ8k58HBe0SNCtGd9+SWmi CWbb9lkavZCj8abPl9HJxhszODOnt4hjW0WvZ3LVckEqJrew8tI2f7jHUTCcjtkkCbKh iM0XnRXUgWJWJmMaPJiyTwZ0t66/eNk6Fu1teDV4M1FJddc6Xy5K7PAtqXH1+y+9yfqG RZL7dj1h18rKnL5zdrLeKWZ9kbhCZWZdRSJX+CfqVKddkcNr3/2NCo3LrevD6j6eoigv QLug==
Received: by 10.236.153.164 with SMTP id f24mr3343692yhk.83.1348062099324; Wed, 19 Sep 2012 06:41:39 -0700 (PDT)
Received: from [10.255.25.102] (50-76-68-140-static.hfc.comcastbusiness.net. [50.76.68.140]) by mx.google.com with ESMTPS id o5sm2691296anm.17.2012.09.19.06.41.34 (version=SSLv3 cipher=OTHER); Wed, 19 Sep 2012 06:41:38 -0700 (PDT)
Message-ID: <5059CB93.6020500@gmail.com>
Date: Wed, 19 Sep 2012 14:41:39 +0100
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: RJ Atkinson <rja.lists@gmail.com>
References: <D1800D0A-95CA-4EFE-8841-391156232607@gmail.com>
In-Reply-To: <D1800D0A-95CA-4EFE-8841-391156232607@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: renum@ietf.org
Subject: Re: [renum] Working Group Last Call: draft-ietf-6renum-static-problem-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, 19 Sep 2012 13:41:40 -0000

Hi Ran,

Thanks for the comments. We are in WG Last Call until Sept. 28 so
we will roll all the comments up at that time.

See my small comments in line below.

Regards
   Brian

On 19/09/2012 13:43, RJ Atkinson wrote:
> Hi,
> 
> 	While I am not a subscriber to this WG list,
> I have a few comments on draft-ietf-6renum-static-problem-01.
> I have tried to organise the comments by Section.
> 
> 
> Section 2.2, 1st Paragraph:
> 	For about a decade now, most network-capable printers 
> 	have silently and automatically enabled SLP without 
> 	requiring any user interaction.  Such printers often
> 	use a factory-default algorithm to generate a printer
> 	name, unless a user has explicitly configured a 
> 	printer name.
> 	
> 	Hosts that are SLP-aware, automatically discover such 
> 	printers and can use them, without requiring the printer 
> 	to have a preconfigured fixed IP address.  Many deployed 
> 	hosts have supported SLP for the past decade.
> 
> 	So, the statement that "It is also unusual to enable 
> 	the Service Location Protocol for the same purpose..."
> 	is not correct in the deployed world.  It was correct
> 	in the 1990s.  It has not been correct for about a
> 	decade, however.

Opinions on the extent of deployment seem to differ, judging by
some recent comments on the homenet WG list. I recently had occasion
to install an HP printer and it was necessary to install some proprietary
discovery software on the (Windows) hosts as well; so at least in that case
there was no SLP by default. But we can certainly remove "unusual"
and say something like "It is not universal to enable...".

> 
> Section 2.2, Last Paragraph:
> 	The DNS Service Discovery (DNS-SD) technology
> 	described in draft-cheshire-dnsext-dns-sd-11.txt
> 	is directly relevant and should be both mentioned
> 	and referenced in this paragraph.  mDNS is great,
> 	but for the problems of Section 2.2, mDNS really
> 	works much more effectively in combination with
> 	DNS-SD.  The RFC Editor web site indicates that
> 	both DNS-SD and mDNS are IN-QUEUE for publication
> 	on the IETF standards track.
> 
> 	Also, since around 2005/2006, many printers have
> 	shipped with mDNS/DNS-SD silently and automatically
> 	enabled (in addition to SLP).  Further, many Windows
> 	PCs, all Apple Macs, and many UNIX systems have
> 	silently enabled mDNS/DNS-SD support for printing.
> 	(NOTE: I'm told that when one installs "iTunes" onto 
> 	MS Windows, the installer silently installs mDNS/DNS-SD 
> 	support also, since mDNS/DNS-SD is how iTunes finds 
>         "shared libraries" of digital content.)  So the last 
>         paragraph also needs to be edited to clarify that the 
> 	mDNS/DNS-SD combination is now widely supported and 
> 	widely deployed for a range of services, including 
> 	location of network printers.

Again, this has come up recently in homenet, and whether mDNS
or "genuine" DNS is the way to go is a hot topic. The issue with
mDNS is that it only works on a bridged network, as I understand
it, which is an issue in many enterprise networks (our scope
for 6renum).

> 
> Otherwise the I-D seems fine to me.
> 
> Yours,
> 
> Ran
> 
> 
> 
> 
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
> 

From rja.lists@gmail.com  Wed Sep 19 08:18:53 2012
Return-Path: <rja.lists@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 F3A3B21F86AD for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 08:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 SyOPrmxeDQyG for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 08:18:52 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id C747221F8643 for <renum@ietf.org>; Wed, 19 Sep 2012 08:18:48 -0700 (PDT)
Received: by qadz3 with SMTP id z3so1124708qad.10 for <renum@ietf.org>; Wed, 19 Sep 2012 08:18:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=M8goUEg5D95OOgTFRKfl4iPVRwXHlbuVlh9+SO5wiZQ=; b=dvjh3TtQsDuIA2F5jVp2e0myM1SQxmbQxLSizX4pz2su3G319nj1LXNnbLa/K7v7WT 4Wyr7W6ddGaT6f/gMySdKZbyTjUrtEyipR8Xwn+MZHXdJ6CY/F+6Ja03mS+wvRXGVI7G iq96lCFMSNxGoa3XLPyFBMZV5SDeVzIirXGtVaAZgeGzfHmIdnjB66QoSktcTk+AO84v xFzXjTHnAPpQEaKnmsD3VEwq+Rs2AB3g1QfCG7gL0vm4QGRaaJLJPma4xZe+oyk4mcZO KR2RmABhfpkUdj2w1+46OXFgqm+/se22NiiKZXR5DUvxi5qZAkDMfiSzf/tbpwk26xRo ZwBw==
Received: by 10.224.71.74 with SMTP id g10mr715941qaj.34.1348067928257; Wed, 19 Sep 2012 08:18:48 -0700 (PDT)
Received: from [10.30.20.13] (pool-74-110-100-136.nrflva.fios.verizon.net. [74.110.100.136]) by mx.google.com with ESMTPS id dp3sm4285862qab.21.2012.09.19.08.18.46 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Sep 2012 08:18:47 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Sep 2012 11:18:45 -0400
Message-Id: <2709B191-EA6F-44E7-9537-19175DC8AD01@gmail.com>
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: Re: [renum] Working Group Last Call: draft-ietf-6renum-enterprise-02.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, 19 Sep 2012 15:18:53 -0000

  I am not a member of the Renum mailing list, but I have
a few comments on this draft.

General:
	It would be helpful to use "might" when one means
	"possibility" and only use "may" when one means
	"permission".  In several places the meaning is
	a bit unclear, because "may" gets used in different
	ways in different parts of the document.  A
	little editing would help readability.


Section 4.1, "Usage of FQDN", 2nd paragraph:
	Please cite the mDNS and DNS-SD specifications,
	which are in the RFC Editor's publication queue,
        and add them to the REFERENCES section.


Section 4.2, page 10, "Reduce the DNS configuration lifetime":
	The section should note that it is practical and reasonable=20
	for A, AAAA, and PTR records to be configured with very=20
	short DNS TTL values (e.g. 0 seconds, 1 second), not
	only during renumbering events, but also for longer-term
	operation.

	Recent experimental work done at U. St Andrews [BA2011]=20
        has verified much earlier trace-driven simulation=20
        research done at MIT which noted that DNS caching is
	not really very effective. [JSBM2002]

        [BA2011] S. Bhatti, R. Atkinson, "Reducing DNS Caching",=20
        Proc. 14th IEEE Global Internet Symposium (GI2011),=20
        Shanghai, China. 15 April 2011.
       =20
	[JSBM2002] J. Jung, E. Sit, H. Balakrishnan, & R. Morris,
        "DNS Performance and the Effectiveness of Caching",=20
        IEEE/ACM Trans. Netw., 10(5):589=96603, 2002.


Section 4.3, page 12, "DNS record update and DNS configuration":
	See previous comment above about running DNS
	with very short TTLs.


Section 4.3, page 12, "Tunnel concentrator renumbering":

	It is NOT correct that IPsec necessarily will fail
	when a tunnel concentrator is renumbered.  As noted
	in RFC-5887, Section 5.2, IPsec works fine and adapts=20
        to renumbering provided that any non IP-address name=20
        is used for identity in one's IPsec key management system
	(e.g. with IKEv1, IKEv2; conceptually also Kerberos).
	RFC-4306, Section 3.5 lists several non-IP-address
	name types (ID_FQDN, ID_RFC822_ADDR, ID_DER_ASN1_DN,
	ID_DER_ASN1_GN, ID_KEY_ID), each of which would be
	sufficient to provide IPsec resilience in the event
	of an IP address renumbering event.  A similar set
	of non-IP-address identities was earlier defined
	for IKEv1, so this is NOT something new with IKEv2.

	Separately, RFC-2230 defines the KX record, which
	could be used to help locate the domain-name for
	a IPsec VPN concentrator associated with a site's
	domain name.

       =20
Thanks,

Ran




From rja.lists@gmail.com  Wed Sep 19 11:39:56 2012
Return-Path: <rja.lists@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 64E4621F84C5 for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 11:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 WAh7GH550whb for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 11:39:55 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id B1ABF21F843A for <renum@ietf.org>; Wed, 19 Sep 2012 11:39:55 -0700 (PDT)
Received: by qcac10 with SMTP id c10so1229662qca.31 for <renum@ietf.org>; Wed, 19 Sep 2012 11:39:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=DygS/PUjTZuaEucTwlPz5yjjuoIwcmPV9/avpavWwPc=; b=XZVFWq6rLBpuf5haAr+9FsXpQhfzbzbUILq5YHaJRZJaO0lLLzxdPXfZ235LxY0jVa Gtd0F60vUy/BD11vkp5db8M8Sg3M7M74oxg2qcD4r6XeAY6/vq/AFPEXuHxWJ7ZcdXmC OSn+7v2fuNGZErrdwyrKxGtZEYSKg4Dnuzo9roZEA7f/tn3jfF1BrzHJeRTtRw7z8dWG FvicZOzN1mxQmRzDVRu7rh4+VJkxjPo8Wc+38sOC4QAs/ppcAFU4It54UVZeSSekfT9a 8uO9EsfCdtZKZto184/TWT8wY19ubljUwmUs6snffRpBAzJWbHY2mB/ASWh8xTh+xHVc O34A==
Received: by 10.229.137.132 with SMTP id w4mr2528176qct.155.1348079995091; Wed, 19 Sep 2012 11:39:55 -0700 (PDT)
Received: from [10.30.20.13] (pool-74-110-100-136.nrflva.fios.verizon.net. [74.110.100.136]) by mx.google.com with ESMTPS id e5sm4888496qao.11.2012.09.19.11.39.52 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Sep 2012 11:39:53 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 19 Sep 2012 14:39:51 -0400
Message-Id: <C89AB8B8-78B6-4482-9E34-5DE04B6C537D@gmail.com>
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: Re: [renum] Working Group Last Call:	draft-ietf-6renum-gap-analysis-03.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, 19 Sep 2012 18:39:56 -0000

>> Earlier, Marc Lampo wrote:
>> One element is that in practice, not all devices "out there"
>> (some very widely used) are not capable of defining the
>> valid addresses on an IPSEC endpoint via DNS.

(With a confused look on my face)

I'm aware of numerous IPsec devices that do support
the use of FQDNs, in addition to IP addresses, as
IPsec SA endpoint identifiers.  Multiple products 
(e.g. from Cisco, from Juniper [both JunOS and also
ex-Netscreen products running ScreenOS], and 
other products from many suppliers) support this
-- and have done for many many years now.

In fact, I'm not aware of any IKEv1 or IKEv2 
implementations that lack this, since it was 
in the very very early specifications for ISAKMP/IKE.

However, in many cases, users don't seem to realise that 
the capability exists, which is partly why the capability
was noted in RFC-5887 and is repeated here.  

An example of a "very widely used" IPsec implementation
that can't do this would be informative, to me at least, 
if not on-list, then perhaps in a quick unicast email.

Later, Brian Carpenter wrote:
> True, that's an implementation and deployment gap,
> not a protocol gap.  All we can do in the IETF is document
> this kind of gap, since we don't control implementations.

Agreed.  To the extent that some IPsec implementation(s)
d(oes)n't comply with long-standing (well over a decade old)
IETF specs, that issue is outside the scope of an IETF WG.

However, the best information I have, and I've done some
online checks today (without figuring out which item
Marc is referring to), is that this capability is widely
implemented and available -- albeit not so widely deployed.

> Nothing works if people don't use the global DNS correctly, ...


Agreed.


Yours,

Ran


From shane@castlepoint.net  Wed Sep 19 12:11:18 2012
Return-Path: <shane@castlepoint.net>
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 0B60A21E80A5 for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 12:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.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 ymusyUoUL6eB for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 12:11:17 -0700 (PDT)
Received: from mail.tcb.net (unknown [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id 1F2BE11E8091 for <renum@ietf.org>; Wed, 19 Sep 2012 12:11:17 -0700 (PDT)
Received: from mbpw.castlepoint.net (216-160-173-224.hlrn.qwest.net [216.160.173.224]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.tcb.net (Postfix) with ESMTPSA id AD1835DA; Wed, 19 Sep 2012 13:11:15 -0600 (MDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <C89AB8B8-78B6-4482-9E34-5DE04B6C537D@gmail.com>
Date: Wed, 19 Sep 2012 13:11:17 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0BA0A91-4334-49FF-B6DB-AB63FA90A508@castlepoint.net>
References: <C89AB8B8-78B6-4482-9E34-5DE04B6C537D@gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
X-Mailer: Apple Mail (2.1486)
Cc: renum@ietf.org
Subject: Re: [renum] Working Group Last Call:	draft-ietf-6renum-gap-analysis-03.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, 19 Sep 2012 19:11:18 -0000

Ran, Brian,

On Sep 19, 2012, at 12:39 PM, RJ Atkinson <rja.lists@gmail.com> wrote:
>>> Earlier, Marc Lampo wrote:
>>> One element is that in practice, not all devices "out there"
>>> (some very widely used) are not capable of defining the
>>> valid addresses on an IPSEC endpoint via DNS.
>=20
> (With a confused look on my face)
>=20
> I'm aware of numerous IPsec devices that do support
> the use of FQDNs, in addition to IP addresses, as
> IPsec SA endpoint identifiers.  Multiple products=20
> (e.g. from Cisco, from Juniper [both JunOS and also
> ex-Netscreen products running ScreenOS], and=20
> other products from many suppliers) support this
> -- and have done for many many years now.

I agree.  In fact, I remember configuring FQDN's, as IPsec SA endpoint =
ID's, in Netscreen devices (ScreenOS) as far back as the 2000-2001 =
timeframe.  I seem to recall Checkpoint FW-1 supporting a similar =
capability in that timeframe, as well.  Anyway, just more data points =
from my past experience to substantiate what Ran said above.

I'll echo what Ran said below:
> An example of a "very widely used" IPsec implementation
> that can't do this would be informative, to me at least,=20
> if not on-list, then perhaps in a quick unicast email.


-shane


> In fact, I'm not aware of any IKEv1 or IKEv2=20
> implementations that lack this, since it was=20
> in the very very early specifications for ISAKMP/IKE.
>=20
> However, in many cases, users don't seem to realise that=20
> the capability exists, which is partly why the capability
> was noted in RFC-5887 and is repeated here. =20
>=20
>=20
> Later, Brian Carpenter wrote:
>> True, that's an implementation and deployment gap,
>> not a protocol gap.  All we can do in the IETF is document
>> this kind of gap, since we don't control implementations.
>=20
> Agreed.  To the extent that some IPsec implementation(s)
> d(oes)n't comply with long-standing (well over a decade old)
> IETF specs, that issue is outside the scope of an IETF WG.
>=20
> However, the best information I have, and I've done some
> online checks today (without figuring out which item
> Marc is referring to), is that this capability is widely
> implemented and available -- albeit not so widely deployed.
>=20
>> Nothing works if people don't use the global DNS correctly, ...
>=20
>=20
> Agreed.
>=20
>=20
> Yours,
>=20
> Ran
>=20
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
>=20


From rja.lists@gmail.com  Wed Sep 19 12:12:19 2012
Return-Path: <rja.lists@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 187BA21F85B8 for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 12:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 RXxHH2o7StBh for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 12:12:18 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 616D521F8551 for <renum@ietf.org>; Wed, 19 Sep 2012 12:12:18 -0700 (PDT)
Received: by qcac10 with SMTP id c10so1259067qca.31 for <renum@ietf.org>; Wed, 19 Sep 2012 12:12:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=wVpefZPXS+mxvKLyzwhLLq2qh/rElDKFGSAKaXELM1s=; b=T5oj0VcKbiSn9VImZkuQZB0PsZyqq+ybddulvQo02BIPG3LsDe149hM0qCieKCJAXC ETaBvuuGQ5WWKZXf8ntoXhtw8mNv/tYIjn/YL3gt5xkXYuZ8x5u578af9ACduKfpv4+o lHKLHekUv9E+6+LtXXymgeOMOJuLlxc//YKaDLT6bsfjSwTz/LXbuc1W35hG/dMwness 8LQ638qdjb8gE9+21M3d8vy9XAPLpHfR9d2DWW1Csj5S2r/y4hm/AtenN5ZDgZqcEHg8 Euuk+tPZnSMZFLCnNEOkCSbVsCPDssmIXjMvqogpDNmp18jNhEYx3ufkMM1zIzZmW0Ms RvWQ==
Received: by 10.224.177.15 with SMTP id bg15mr9151470qab.85.1348081937696; Wed, 19 Sep 2012 12:12:17 -0700 (PDT)
Received: from [10.30.20.13] (pool-74-110-100-136.nrflva.fios.verizon.net. [74.110.100.136]) by mx.google.com with ESMTPS id ca8sm4982885qab.20.2012.09.19.12.12.16 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Sep 2012 12:12:17 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Sep 2012 15:12:15 -0400
Message-Id: <07A9B495-21EA-4DFD-84BC-AF5BB6B62BE2@gmail.com>
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.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, 19 Sep 2012 19:12:19 -0000

Earlier Di Ma wrote:
> Yet as a document providing a basis for future works that identify
> and develop solutions or to stimulate such development as appropriate,
> this draft might make IPSec Security Association (SA) management
> included, considering IPSec SA is a kind of IP address oriented
> =93connection=94 that cannot function after the change of the involved
> IP addresses, which means extra configuration of SA parameters
> is inevitable after network renumbering.

In general, the above is NOT correct with regard to IPsec.

I wrote the IPsec specs (e.g. RFC-1825 et seq) and was,
for a time, IPsec WG Co-Chair.  I'm also the person who=20
insisted upon having non-IP-address identities defined=20
in the specs, not because of renumbering, but because of
the more general issue of different users wanting to use
different identity types.

IF AND ONLY IF, one configures IKE (either v1 or v2)=20
to use the IP Address based identifiers (e.g. ID_IPV4_ADDR,
ID_IPV6_ADDR), then Di Ma's text is correct.

HOWEVER, if one configures IKE (either version) to use
non-address identifiers (e.g. ID_FQDN, ID_USER_FQDN) [1],=20
then Di Ma's description above is NOT correct.  In that case,=20
what happens is that when any IP address changes, the=20
IPsec endpoints recover automatically, thereby making=20
IPsec use resilient in the presence of renumbering.

I have personally relied upon this capability for many years,
dating back at least to 2001.  Circa 2001, the ID_USER_FQDN
and ID_FQDN identity types were being used with IKEv1 between=20
a very small Netscreen box connected to the DOCSIS cable modem=20
in my house and a larger VPN box at my (then) employer across=20
the country.  The Cable-ISP regularly renumbered the IPv4=20
address for my CPE, using DHCPv4, which changed the IPv4=20
address of the public-side of the Netscreen box, yet the=20
IPsec VPN tunnel was resilient, requiring no intervention=20
from me to remain alive/available.

> Pre-shared key method cannot be used with mobile systems=20
> or systems that may be renumbered, unless the renumbering=20
> is within the previously determined range of IP addresses.

I also have used pre-shared keys with ID_USER_FQDN between
a mobile laptop (home, coffee shop, office) and an employer's=20
VPN box.  So that also works just fine -- and has done=20
for a decade or longer. =20

One can find a renumbered "employer VPN box" simply by=20
using DNS KX records from RFC-2230.  A simplified example=20
of how the DNS records might look is provided below=20
(caveat: I might have mistyped the DNS syntax):

	example.com         IN KX 5  vpn-box.example.com
	vpn-box.example.com IN A     <IP address here>

Of course, use of KX records ought to be authenticated
via DNS Security, but that (separately) is widely
available today (and has rapidly growing deployment).

> Also, when pre-shared key is employed, IKEv2 computations=20
> cannot be offloaded to the attached hardware.

The above might be true for a particular implementation,
but it is not true in general for all implementations.
Better quality implementations simply do not have this
property. =20


Accordingly, I object to the inclusion of the text that
Di Ma has proposed, on grounds that it is not correct.

Yours,

Ran

[1]  I've used RFC-4306 terminology above.  The same
     capability exists in IKEv1, but uses slightly
     different terminology (e.g. ID_USER_FQDN rather
     than ID_RFC822_ADDR).  See RFC-2407, Section 4.6.2.1,
     which dates back to 1998, and was widely supported
     in commercially available products by 2000.




From jiangsheng@huawei.com  Wed Sep 19 18:03:02 2012
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 A7CD821E8044 for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 18:03:02 -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 ux9TsPjh2E8E for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 18:02:58 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C0EC121F849A for <renum@ietf.org>; Wed, 19 Sep 2012 18:02:57 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AJV45032; Thu, 20 Sep 2012 01:02:56 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 20 Sep 2012 02:02:00 +0100
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 20 Sep 2012 02:02:31 +0100
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.98]) by szxeml403-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Thu, 20 Sep 2012 09:01:45 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: RJ Atkinson <rja.lists@gmail.com>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: [renum] Working Group Last Call: draft-ietf-6renum-enterprise-02.txt
Thread-Index: AQHNlnol7M6QVHRFsU6w32J53Ghb/peSaMaQ
Date: Thu, 20 Sep 2012 01:01:45 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B9239F49690@szxeml545-mbx.china.huawei.com>
References: <2709B191-EA6F-44E7-9537-19175DC8AD01@gmail.com>
In-Reply-To: <2709B191-EA6F-44E7-9537-19175DC8AD01@gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.31]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [renum] Working Group Last Call:	draft-ietf-6renum-enterprise-02.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, 20 Sep 2012 01:03:02 -0000

SGksIFJhbiwNCg0KVGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzLiBUaGV5IGFyZSBoZWxwZnVsIGFu
ZCB3aWxsIGJlIGludGVncmF0ZWQgaW4gbmV4dCB2ZXJzaW9uIGFtb25nIHdpdGggb3RoZXIgY29t
bWVudHMgcmVjZWl2ZWQgZHVyaW5nIFdHTEMuDQoNCkJlc3QgcmVnYXJkcywNCg0KU2hlbmcNCg0K
PiAgSSBhbSBub3QgYSBtZW1iZXIgb2YgdGhlIFJlbnVtIG1haWxpbmcgbGlzdCwgYnV0IEkgaGF2
ZQ0KPmEgZmV3IGNvbW1lbnRzIG9uIHRoaXMgZHJhZnQuDQo+DQo+R2VuZXJhbDoNCj4JSXQgd291
bGQgYmUgaGVscGZ1bCB0byB1c2UgIm1pZ2h0IiB3aGVuIG9uZSBtZWFucw0KPgkicG9zc2liaWxp
dHkiIGFuZCBvbmx5IHVzZSAibWF5IiB3aGVuIG9uZSBtZWFucw0KPgkicGVybWlzc2lvbiIuICBJ
biBzZXZlcmFsIHBsYWNlcyB0aGUgbWVhbmluZyBpcw0KPglhIGJpdCB1bmNsZWFyLCBiZWNhdXNl
ICJtYXkiIGdldHMgdXNlZCBpbiBkaWZmZXJlbnQNCj4Jd2F5cyBpbiBkaWZmZXJlbnQgcGFydHMg
b2YgdGhlIGRvY3VtZW50LiAgQQ0KPglsaXR0bGUgZWRpdGluZyB3b3VsZCBoZWxwIHJlYWRhYmls
aXR5Lg0KPg0KPg0KPlNlY3Rpb24gNC4xLCAiVXNhZ2Ugb2YgRlFETiIsIDJuZCBwYXJhZ3JhcGg6
DQo+CVBsZWFzZSBjaXRlIHRoZSBtRE5TIGFuZCBETlMtU0Qgc3BlY2lmaWNhdGlvbnMsDQo+CXdo
aWNoIGFyZSBpbiB0aGUgUkZDIEVkaXRvcidzIHB1YmxpY2F0aW9uIHF1ZXVlLA0KPiAgICAgICAg
YW5kIGFkZCB0aGVtIHRvIHRoZSBSRUZFUkVOQ0VTIHNlY3Rpb24uDQo+DQo+DQo+U2VjdGlvbiA0
LjIsIHBhZ2UgMTAsICJSZWR1Y2UgdGhlIEROUyBjb25maWd1cmF0aW9uIGxpZmV0aW1lIjoNCj4J
VGhlIHNlY3Rpb24gc2hvdWxkIG5vdGUgdGhhdCBpdCBpcyBwcmFjdGljYWwgYW5kIHJlYXNvbmFi
bGUNCj4JZm9yIEEsIEFBQUEsIGFuZCBQVFIgcmVjb3JkcyB0byBiZSBjb25maWd1cmVkIHdpdGgg
dmVyeQ0KPglzaG9ydCBETlMgVFRMIHZhbHVlcyAoZS5nLiAwIHNlY29uZHMsIDEgc2Vjb25kKSwg
bm90DQo+CW9ubHkgZHVyaW5nIHJlbnVtYmVyaW5nIGV2ZW50cywgYnV0IGFsc28gZm9yIGxvbmdl
ci10ZXJtDQo+CW9wZXJhdGlvbi4NCj4NCj4JUmVjZW50IGV4cGVyaW1lbnRhbCB3b3JrIGRvbmUg
YXQgVS4gU3QgQW5kcmV3cyBbQkEyMDExXQ0KPiAgICAgICAgaGFzIHZlcmlmaWVkIG11Y2ggZWFy
bGllciB0cmFjZS1kcml2ZW4gc2ltdWxhdGlvbg0KPiAgICAgICAgcmVzZWFyY2ggZG9uZSBhdCBN
SVQgd2hpY2ggbm90ZWQgdGhhdCBETlMgY2FjaGluZyBpcw0KPglub3QgcmVhbGx5IHZlcnkgZWZm
ZWN0aXZlLiBbSlNCTTIwMDJdDQo+DQo+ICAgICAgICBbQkEyMDExXSBTLiBCaGF0dGksIFIuIEF0
a2luc29uLCAiUmVkdWNpbmcgRE5TIENhY2hpbmciLA0KPiAgICAgICAgUHJvYy4gMTR0aCBJRUVF
IEdsb2JhbCBJbnRlcm5ldCBTeW1wb3NpdW0gKEdJMjAxMSksDQo+ICAgICAgICBTaGFuZ2hhaSwg
Q2hpbmEuIDE1IEFwcmlsIDIwMTEuDQo+DQo+CVtKU0JNMjAwMl0gSi4gSnVuZywgRS4gU2l0LCBI
LiBCYWxha3Jpc2huYW4sICYgUi4gTW9ycmlzLA0KPiAgICAgICAgIkROUyBQZXJmb3JtYW5jZSBh
bmQgdGhlIEVmZmVjdGl2ZW5lc3Mgb2YgQ2FjaGluZyIsDQo+ICAgICAgICBJRUVFL0FDTSBUcmFu
cy4gTmV0dy4sIDEwKDUpOjU4OeKAkzYwMywgMjAwMi4NCj4NCj4NCj5TZWN0aW9uIDQuMywgcGFn
ZSAxMiwgIkROUyByZWNvcmQgdXBkYXRlIGFuZCBETlMgY29uZmlndXJhdGlvbiI6DQo+CVNlZSBw
cmV2aW91cyBjb21tZW50IGFib3ZlIGFib3V0IHJ1bm5pbmcgRE5TDQo+CXdpdGggdmVyeSBzaG9y
dCBUVExzLg0KPg0KPg0KPlNlY3Rpb24gNC4zLCBwYWdlIDEyLCAiVHVubmVsIGNvbmNlbnRyYXRv
ciByZW51bWJlcmluZyI6DQo+DQo+CUl0IGlzIE5PVCBjb3JyZWN0IHRoYXQgSVBzZWMgbmVjZXNz
YXJpbHkgd2lsbCBmYWlsDQo+CXdoZW4gYSB0dW5uZWwgY29uY2VudHJhdG9yIGlzIHJlbnVtYmVy
ZWQuICBBcyBub3RlZA0KPglpbiBSRkMtNTg4NywgU2VjdGlvbiA1LjIsIElQc2VjIHdvcmtzIGZp
bmUgYW5kIGFkYXB0cw0KPiAgICAgICAgdG8gcmVudW1iZXJpbmcgcHJvdmlkZWQgdGhhdCBhbnkg
bm9uIElQLWFkZHJlc3MgbmFtZQ0KPiAgICAgICAgaXMgdXNlZCBmb3IgaWRlbnRpdHkgaW4gb25l
J3MgSVBzZWMga2V5IG1hbmFnZW1lbnQgc3lzdGVtDQo+CShlLmcuIHdpdGggSUtFdjEsIElLRXYy
OyBjb25jZXB0dWFsbHkgYWxzbyBLZXJiZXJvcykuDQo+CVJGQy00MzA2LCBTZWN0aW9uIDMuNSBs
aXN0cyBzZXZlcmFsIG5vbi1JUC1hZGRyZXNzDQo+CW5hbWUgdHlwZXMgKElEX0ZRRE4sIElEX1JG
QzgyMl9BRERSLCBJRF9ERVJfQVNOMV9ETiwNCj4JSURfREVSX0FTTjFfR04sIElEX0tFWV9JRCks
IGVhY2ggb2Ygd2hpY2ggd291bGQgYmUNCj4Jc3VmZmljaWVudCB0byBwcm92aWRlIElQc2VjIHJl
c2lsaWVuY2UgaW4gdGhlIGV2ZW50DQo+CW9mIGFuIElQIGFkZHJlc3MgcmVudW1iZXJpbmcgZXZl
bnQuICBBIHNpbWlsYXIgc2V0DQo+CW9mIG5vbi1JUC1hZGRyZXNzIGlkZW50aXRpZXMgd2FzIGVh
cmxpZXIgZGVmaW5lZA0KPglmb3IgSUtFdjEsIHNvIHRoaXMgaXMgTk9UIHNvbWV0aGluZyBuZXcg
d2l0aCBJS0V2Mi4NCj4NCj4JU2VwYXJhdGVseSwgUkZDLTIyMzAgZGVmaW5lcyB0aGUgS1ggcmVj
b3JkLCB3aGljaA0KPgljb3VsZCBiZSB1c2VkIHRvIGhlbHAgbG9jYXRlIHRoZSBkb21haW4tbmFt
ZSBmb3INCj4JYSBJUHNlYyBWUE4gY29uY2VudHJhdG9yIGFzc29jaWF0ZWQgd2l0aCBhIHNpdGUn
cw0KPglkb21haW4gbmFtZS4NCj4NCj4NCj5UaGFua3MsDQo+DQo+UmFuDQo+DQo+DQo+DQo+X19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5yZW51bSBtYWls
aW5nIGxpc3QNCj5yZW51bUBpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vcmVudW0NCg==

From leo.liubing@huawei.com  Wed Sep 19 19:23:16 2012
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 1C4F611E80A2 for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 19:23:16 -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=[AWL=0.000,  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 V7Z5tm+lL+Eg for <renum@ietfa.amsl.com>; Wed, 19 Sep 2012 19:23:15 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id AFE5D11E808E for <renum@ietf.org>; Wed, 19 Sep 2012 19:23:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKW13019; Thu, 20 Sep 2012 02:23:13 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 20 Sep 2012 03:21:40 +0100
Received: from SZXEML437-HUB.china.huawei.com (10.72.61.72) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 20 Sep 2012 03:22:12 +0100
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml437-hub.china.huawei.com ([10.72.61.72]) with mapi id 14.01.0323.003; Thu, 20 Sep 2012 10:22:06 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: RJ Atkinson <rja.lists@gmail.com>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
Thread-Index: AQHNlpqtInfcpaeCJk6BA/ZG3LCMd5eSdojw
Date: Thu, 20 Sep 2012 02:22:05 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F452935720A@szxeml509-mbs>
References: <07A9B495-21EA-4DFD-84BC-AF5BB6B62BE2@gmail.com>
In-Reply-To: <07A9B495-21EA-4DFD-84BC-AF5BB6B62BE2@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.42]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.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, 20 Sep 2012 02:23:16 -0000

Hi, Ran

Thanks a lot for the detailed clarification of the IPSEC renumbering issue.=
 I think it is fully clear now.

But I think what Di and Marc argued is that, they might found in their case=
s, the FQDN ability was not easy to enable, which may caused by various dep=
loyment/implementation issues. Especially in the Not-well-managed networks,=
 the issue may be common.
If I understood them correctly. I think we need to emphasize the IPSEC FQDN=
 as a BCP in the draft-ietf-6renum-enterprise-scenarios, we can add some mo=
re description according to your detailed comments below.

So, may I ask Di and Marc's opinions about it?

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of
> RJ Atkinson
> Sent: Thursday, September 20, 2012 3:12 AM
> To: renum@ietf.org
> Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
>=20
>=20
> Earlier Di Ma wrote:
> > Yet as a document providing a basis for future works that identify
> > and develop solutions or to stimulate such development as appropriate,
> > this draft might make IPSec Security Association (SA) management
> > included, considering IPSec SA is a kind of IP address oriented
> > "connection" that cannot function after the change of the involved
> > IP addresses, which means extra configuration of SA parameters
> > is inevitable after network renumbering.
>=20
> In general, the above is NOT correct with regard to IPsec.
>=20
> I wrote the IPsec specs (e.g. RFC-1825 et seq) and was,
> for a time, IPsec WG Co-Chair.  I'm also the person who
> insisted upon having non-IP-address identities defined
> in the specs, not because of renumbering, but because of
> the more general issue of different users wanting to use
> different identity types.
......


From rja.lists@gmail.com  Thu Sep 20 04:30:18 2012
Return-Path: <rja.lists@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 2821A21F8793 for <renum@ietfa.amsl.com>; Thu, 20 Sep 2012 04:30:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 GxNFRuRJMSuP for <renum@ietfa.amsl.com>; Thu, 20 Sep 2012 04:30:17 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2A6B921F8694 for <renum@ietf.org>; Thu, 20 Sep 2012 04:30:17 -0700 (PDT)
Received: by qaec10 with SMTP id c10so287406qae.10 for <renum@ietf.org>; Thu, 20 Sep 2012 04:30:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=URnYZ60qjFqj0cpcAAbjtdmv3adjs4YQwIbQYjy6MMA=; b=TdV4Mxo1dqHXvqM/+U0ygBL9jTphz4nT61lgjhPGxHXnq/QB2OXq2Lmg1aJWF6Np18 n127ZkZmkffjRIU5+rOFRnXxLWwMG6j25OHz8FceC6ANxc4RgHjvb5zH125lrVgQMg/w tjVDIVxHSlg37O8s1dRiGHriw4FvERgNt8v2kjDj9AUr7Jm0eE0Suz/nGrKPu1Ihl36q 0U2l33rMw6ULmEnDXpDw8LxL9yEl0Bzfdv2VUlInyWZbF+oVQku41vAipsr85lKI/a1D 5E7At79FuFUIoggbPrwIBD2XFsLqO+X85WpsgFLkLtx2++dz3UIoaAgym8zW+AfWukg8 si+g==
Received: by 10.224.184.197 with SMTP id cl5mr4066675qab.28.1348140616562; Thu, 20 Sep 2012 04:30:16 -0700 (PDT)
Received: from [10.30.20.13] (pool-74-110-100-136.nrflva.fios.verizon.net. [74.110.100.136]) by mx.google.com with ESMTPS id m4sm7851913qak.6.2012.09.20.04.30.14 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 20 Sep 2012 04:30:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F452935720A@szxeml509-mbs>
Date: Thu, 20 Sep 2012 07:30:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2FEB233-3206-4E6C-B54D-BA832B545009@gmail.com>
References: <07A9B495-21EA-4DFD-84BC-AF5BB6B62BE2@gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F452935720A@szxeml509-mbs>
To: renum@ietf.org
X-Mailer: Apple Mail (2.1278)
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.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, 20 Sep 2012 11:30:18 -0000

On 19  Sep 2012, at 22:22 , Liubing (Leo) wrote:
> But I think what Di and Marc argued is that,
> they might found in their cases, the FQDN ability
> was not easy to enable, which may caused by various =
deployment/implementation issues.

It really is very easy to enable in products from
multiple vendors (e.g. Netscreen, Cisco, Juniper).

In any case, both "ease of use" and "user interface"
are outside the usual scope of the IETF.

The big issue appears to be that folks don't realise
why using FQDN is better than IP addresses -- which
is why RFC 5887 talked about this.

Yours,

Ran



From ghalwasi@cisco.com  Thu Sep 20 06:03:58 2012
Return-Path: <ghalwasi@cisco.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 7295F21F87D6 for <renum@ietfa.amsl.com>; Thu, 20 Sep 2012 06:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.095
X-Spam-Level: 
X-Spam-Status: No, score=-10.095 tagged_above=-999 required=5 tests=[AWL=0.504, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 044ImR0EgI2P for <renum@ietfa.amsl.com>; Thu, 20 Sep 2012 06:03:57 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 03ABC21F87D5 for <renum@ietf.org>; Thu, 20 Sep 2012 06:03:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3925; q=dns/txt; s=iport; t=1348146237; x=1349355837; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=er0ylyJ0Ict874BRRQ0yIR3TiE/JEFpBOVZbshKgFqs=; b=FglK7cqk5hQ+O/DANLZROAod5VApuGQUQBDkChprjCPI719lym6py6bh Hn3r2N6SXzjv+lKTy85T91EpHhLMMSM0ZvwpKhMxugvrbzdtogcxunmEB 6SLlvv3aoOSLQjeWyCW19fM2QQbV5WnXMntf6R9sON8og+lde2Z5iuX1u o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAM8TW1CtJV2a/2dsb2JhbABFvRWBCIIgAQEBBAEBAQ8BJzQEAhEEAgEIEQQBAQsUCQcnCxQJCAEBBAESCAEZh2ELmWWgEoscGoVHYAOWeI0kgWmCZoFjNA
X-IronPort-AV: E=Sophos;i="4.80,453,1344211200"; d="scan'208";a="123592861"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP; 20 Sep 2012 13:03:54 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q8KD3sBF029519 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 20 Sep 2012 13:03:54 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.33]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.02.0298.004; Thu, 20 Sep 2012 08:03:54 -0500
From: "Gaurav Halwasia (ghalwasi)" <ghalwasi@cisco.com>
To: "Howard, Lee" <lee.howard@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: Working Group Last Call: draft-ietf-6renum-enterprise-02.txt
Thread-Index: Ac2MS1AyGfCtBCmORjqQzps1UhuJbgK5O7hQ
Date: Thu, 20 Sep 2012 13:03:53 +0000
Message-ID: <90903C21C73202418A48BFBE80AEE5EB1925E620@xmb-aln-x06.cisco.com>
References: <99B887114EDB1449941CFBC8EC279FA12CB43E15@PRVPEXVS17.corp.twcable.com>
In-Reply-To: <99B887114EDB1449941CFBC8EC279FA12CB43E15@PRVPEXVS17.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.142.105.209]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19194.004
x-tm-as-result: No--49.769700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [renum] Working Group Last Call: draft-ietf-6renum-enterprise-02.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, 20 Sep 2012 13:03:58 -0000

I am in favor of advancing with this draft. It's a useful work.

Thanks,
Gaurav

-----Original Message-----
From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of H=
oward, Lee
Sent: Thursday, September 06, 2012 9:49 PM
To: renum@ietf.org
Subject: [renum] Working Group Last Call: draft-ietf-6renum-enterprise-02.t=
xt

We are requesting a Working Group Last Call on this document.  Please revie=
w and provide comments before September 19, since this may be the final rev=
iew of this document.

Thanks,

Lee


> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf=20
> Of
Sheng Jiang
> Sent: Monday, September 03, 2012 11:44 PM
> To: internet-drafts@ietf.org; i-d-announce@ietf.org
> Cc: renum@ietf.org
> Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-02.txt
>
> A new version with minor editorial modifications are submitted. Your
review and comments
> are appreciated.
>
> Best regards,
>
> Sheng
>
> >-----Original Message-----
> >From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On=20
> >Behalf Of internet-drafts@ietf.org
> >Sent: Tuesday, September 04, 2012 10:16 AM
> >To: i-d-announce@ietf.org
> >Cc: renum@ietf.org
> >Subject: [renum] I-D Action: draft-ietf-6renum-enterprise-02.txt
> >
> >
> >A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> > This draft is a work item of the IPv6 Site Renumbering Working Group=20
> >of the IETF.
> >
> >     Title           : IPv6 Enterprise Network Renumbering Scenarios and
> >Guidelines
> >     Author(s)       : Sheng Jiang
> >                          Bing Liu
> >                          Brian Carpenter
> >     Filename        : draft-ietf-6renum-enterprise-02.txt
> >     Pages           : 16
> >     Date            : 2012-09-03
> >
> >Abstract:
> >   This document analyzes enterprise renumbering events and describes
> >   the best current practice among the existing renumbering mechanisms.
> >   According to the different stages of renumbering events,
> >   considerations and best current practices are described in three
> >   categories: during network design, for preparation of renumbering,
> >   and during a renumbering operation.
> >
> >
> >The IETF datatracker status page for this draft is:
> >https://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise
> >
> >There's also a htmlized version available at:
> >http://tools.ietf.org/html/draft-ietf-6renum-enterprise-02
> >
> >A diff from the previous version is available at:
> >http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-enterprise-02
> >
> >
> >Internet-Drafts are also available by anonymous FTP at:
> >ftp://ftp.ietf.org/internet-drafts/
> >
> >_______________________________________________
> >renum mailing list
> >renum@ietf.org
> >https://www.ietf.org/mailman/listinfo/renum
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum


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.
_______________________________________________
renum mailing list
renum@ietf.org
https://www.ietf.org/mailman/listinfo/renum

From madi@cnnic.cn  Thu Sep 20 12:57:14 2012
Return-Path: <madi@cnnic.cn>
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 2F50321E805F for <renum@ietfa.amsl.com>; Thu, 20 Sep 2012 12:57:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level: 
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[AWL=-0.595,  BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753]
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 8-OWpv37cds4 for <renum@ietfa.amsl.com>; Thu, 20 Sep 2012 12:57:13 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id 379C421F8682 for <renum@ietf.org>; Thu, 20 Sep 2012 12:57:10 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: madi@cnnic.cn
Received: from unknown127.0.0.1 (HELO user-think) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 21 Sep 2012 03:57:00 +0800
Date: Fri, 21 Sep 2012 03:56:58 +0800
From: "Di Ma" <madi@cnnic.cn>
To: "RJ Atkinson" <rja.lists@gmail.com>
References: <07A9B495-21EA-4DFD-84BC-AF5BB6B62BE2@gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F452935720A@szxeml509-mbs>,  <E2FEB233-3206-4E6C-B54D-BA832B545009@gmail.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.90[cn]
Mime-Version: 1.0
Message-ID: <201209210356573495357@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart487888456634_=----"
Cc: 6renum <renum@ietf.org>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: madi <madi@cnnic.cn>
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, 20 Sep 2012 19:57:14 -0000

This is a multi-part message in MIME format.

------=_001_NextPart487888456634_=----
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SGksIFJhbiwNCiANClRoYW5rIHlvdSB2ZXJ5IG11Y2ggaW5kZWVkIGZvciB5b3VyIGRldGFpbGVk
IGNvbW1lbnRzLiBZb3UgaGF2ZSBwcm92aWRlZCBwbGVudHkgb2YgdmFsdWFibGUgaW5mb3JtYXRp
b24uIFlldCBpbiBteSBwcmV2aW91cyBtYWlsLCB3aGF0IEkgd2FzIHRyeWluZyB0byBzYXkgaXMg
dGhhdCBJUFNlYyBpdHNlbGYgaXMgYW4gYWRkcmVzcy1iYXNlZCBjb25uZWN0aW9uLCB3aGljaCwg
YnkgdGhlIHdheSwgaGFzIG5vdGhpbmcgdG8gZG8gd2l0aCB0aGUgbWV0aG9kcyBJS0UgZW1wbG95
cyB0byBpZGVudGlmeSB0aGUgcGVlcnMgbmVnb3RpYXRpbmcgU0EgcGFyYW1ldGVycy4gDQogDQpD
b25zcGljdW91c2x5LCBub24tSVAtYWRkcmVzcyBpZGVudGlmaWVycyBzdWNoIGFzIEZRRE4gY2Fu
IGhlbHAgSVBTZWMgcGFydGljaXBhbnRzIHRvIGV4Y2hhbmdlIG5vdGVzLCBhbmQgd2l0aCBJS0Ug
SVBTZWMgZW5kcG9pbnRzIGNhbiByZWNvdmVyIGF1dG9tYXRpY2FsbHkgYXMgeW91IG1lbnRpb25l
ZC4gVGhlIHJlYXNvbiB3aHkgSSB0aHJldyB0aGUgSVBTZWMgaXNzdWUgaW4gdGhlIGNhdGVnb3J5
IG9mIG5ldHdvcmsgcmVudW1iZXJpbmcgaXMgdGhhdCBhdCBzb21lIHNwZWNpZmljIGNpcmN1bXN0
YW5jZXMgSVBTZWMgU0EgcGFyYW1ldGVycywgYXMgSVAgYWRkcmVzcyBvcmllbnRlZCwgY2FuIGJl
IGNvbmZpZ3VyZWQgaW4gYSBiZXR0ZXIgd2F5IG90aGVyIHRoYW4gSUtFICh2MikgdG8gZ28gd2l0
aCByZW51bWJlcmluZyBldmVudHMuDQogDQpCeSB0aGUgdmlydHVlIG9mIHNwZWNpZmljIG5ldHdv
cmsgb3BlcmF0aW9ucywgU0EgY29uZmlndXJhdGlvbiBtYW5hZ2VtZW50IGNvdWxkIGJlIGZhbmNp
ZWQgaW4gYW4gb3B0aW1pemVkIHdheS4gQ3VzdG9tZXIgUHJlbWlzZXMgTmV0d29yayAoQ1BOKSBv
ZmZlcnMgYSBzY2VuYXJpbyB3aGVyZSB0aGUgY29uZmlndXJhdGlvbiBvZiBTQSBwYXJhbWV0ZXJz
IGZvciBzcGVjaWZpYyBJUFNlYyBwYXJ0aWNpcGFudHMgY2FuIGJlIGludGVncmF0ZWQgaW50byBJ
UCBhZGRyZXNzIGFzc2lnbm1lbnQuIEFzIHdpZGVseSBvYnNlcnZlZCwgc29tZSBDUE4gc2Vydmlj
ZXMgc3VjaCBhcyBETlMgcmVjdXJzaXZlIHJlc29sdXRpb24gc2VydmljZSwgU0lQIHByb3h5IHNl
cnZpY2UsIGFyZSBleHBlY3RlZCB0byBoYXZlIGludGVncml0eSBhbmQgY29uZmlkZW50aWFsaXR5
IHByb3RlY3Rpb24uIFRoYXQgaXMsIGZyb20gdGhlIHBvaW50IG9mIHZpZXcgb2YgYSB1c2VyIGhv
c3QsIFNBIHBhcmFtZXRlcnMgYm91bmQgdG8gRE5TIHJlY3Vyc2l2ZSBuYW1lIHNlcnZlciBvciBT
SVAgc2VydmVyLCBjYW4gYmUgY29uc2lkZXJlZCB1bmRpZmZlcmVudGlhdGVkIHdpdGggb3RoZXIg
bmV0d29yayBwYXJhbWV0ZXJzLCBzdWNoIGFzIElQIGFkZHJlc3Mgb2YgdGhlIHVzZXIgaG9zdCwg
ZGVmYXVsdCBnYXRld2F5IGFkZHJlc3MsIHRoYXQgYXJlIGNvbW1vbmx5IGNvbmZpZ3VyZWQgdmlh
IERIQ1AuDQogDQpTaW5jZSB0aGUgSVBTZWMgaXMgYWRkcmVzcy1vcmllbnRlZCBhbmQgdGhlIERI
Q1Agc2VydmVyIGlzIHJlc3BvbnNpYmxlIGZvciBJUCBhZGRyZXNzIGNvbmZpZ3VyYXRpb24sIHdl
IG1pZ2h0IGFzIHdlbGwgaW50ZWdyYXRlIElQU2VjIFNBIHBhcmFtZXRlcnMgY29uZmlndXJhdGlv
biBpbnRvIElQIGFkZHJlc3MgYXNzaWdubWVudCBieSBleHRlbmRpbmcgREhDUCB3aGVyZSB0aGUg
SVAgYWRkcmVzcyBjb25maWd1cmF0aW9uIG5vZGUgKERIQ1Agc2VydmVyKSBwbGF5cyBsaWtlIGFu
IKGwYWRtaW5pc3RyYXRvcqGxIHVzaW5nIERIQ1AgdG8gY29uZmlndXJlIElQU2VjIFNBIHBhcmFt
ZXRlcnMgaW4gYSBob3N0LCBhZnRlciBpdCwgaW4gZGVwdXR5IG9mIHRoZSBob3N0LCBoYXMgbmVn
b3RpYXRlZCB3aXRoIGEgQ1BOIHNlcnZlciB0aGUgdmVyeSBob3N0IHdhbnRzIHRvIGVzdGFibGlz
aCBJUFNlYyB3aXRoLiAgQ29uc2VxdWVudGx5LCBhZnRlciB0aGUgcmVudW1iZXJpbmcgZXZlbnQs
IHRoZSB1c2VyIGhvc3QgY2FuIGdldCBhIG5ldyBJUCBhZGRyZXNzIGFuZCBuZXcgU0EgcGFyYW1l
dGVycyBwaWdneWJhY2tlZCB2aWEgREhDUCBtZXNzYWdlcy4NCiANClRvIGJlIGV4YWN0LCBpbiB0
aGlzIHNjZW5hcmlvLCB0aGUgdXNlciBob3N0IHdpbGwgYmUgYSBTQSBlc3RhYmxpc2htZW50IGlu
aXRpYXRvciBhbmQgdGhlIERIQ1Agc2VydmVyIHdpbGwgc2VydmUgYXMgdGhlIGRlcHV0eSBmb3Ig
dGhlIHVzZXIgaG9zdCB0byBuZWdvdGlhdGUgU0EgcGFyYW1ldGVycyB3aXRoIHRoZSBDUE4gc2Vy
dmVyIHN1Y2ggYXMgRE5TIHJlY3Vyc2l2ZSBuYW1lIHNlcnZlciwgU0lQIHNlcnZlciwgZXRjLiBU
aGUgc3VwZXJpb3JpdHkgb2YgZ3JhbnRpbmcgU0EgbWFuYWdlbWVudCB0byBESENQIHNlcnZlciBp
cyB0aGF0IHRoZSBTQSBuZWdvdGlhdGlvbiB3aWxsIGJlIHNpbXBsaWZpZWQgYmFzZWQgb24gdGhl
IHByZWNvbmZpZ3VyZWQgdHJ1c3QgcmVsYXRpb25zaGlwIGJldHdlZW4gdGhlIERIQ1Agc2VydmVy
IGFuZCBvdGhlciBDUE4gc2VydmVycywgc2luY2UgaW4gcmVndWxhciBDUE4gc2NlbmFyaW9zLCB0
aGUgREhDUCBzZXJ2ZXIgYW5kIENQTiBzZXJ2ZXJzIGFyZSB1c3VhbGx5IGF0IHRoZSBzYW1lIGFk
bWluaXN0cmF0aW9uIGRvbWFpbiwgc29tZXRpbWVzIGV2ZW4gaW50ZWdyYXRlZCBpbiB0aGUgc2Ft
ZSBkZXZpY2UsIHdoaWNoIG1ha2VzIHRoZSBJS0V2MiBhdXRoZW50aWNhdGlvbiBleGNoYW5nZXMg
dW5uZWNlc3NhcnkuICBTZWN1cmUgdHVubmVscywgc3VjaCBhcyBIVFRQUyBvciBvdGhlciBzZWN1
cmUgcHJvdG9jb2xzIHdpdGggbGVzcyByb3VuZHMgY291bGQgYmUgZWFzaWx5IGFwcGxpZWQgdG8g
cHJvdGVjdCB0aGUgY29tbXVuaWNhdGlvbiBiZXR3ZWVuIHRoZSBESENQIHNlcnZlciBhbmQgQ1BO
IHNlcnZlciB3aGVuIG5lZWRlZC4gIA0KIA0KT25jZSB0aGUgdmVyeSBtZXRob2QgaXMgcmVhbGl6
ZWQsIHRoZSBJUFNlYyBTQSBuZWdvdGlhdGlvbiBpcyB0cmFuc3BhcmVudCB0byB1c2VyIGhvc3Rz
IGVzcGVjaWFsbHkgdGhlIGhhbmRoZWxkIGRldmljZXMgdGhhdCBhcmUgY29uc2lkZXJlZCBhcyCh
sHRoaW4gY2xpZW50c6GxLiBUaGUgdXNlciBob3N0IHRlbGxzIHRoZSBjb25maWd1cmF0aW9uIGVu
dGl0eSwgREhDUCBzZXJ2ZXIgZm9yIGluc3RhbmNlLCBpdCB3YW50cyB0byBrbm93IHRoZSBJUCBh
ZGRyZXNzIG9mIEROUyByZWN1cnNpdmUgbmFtZSBzZXJ2ZXIgYW5kIGl0IHdhbnRzIHRvIGVtcGxv
eSBJUFNlYyB0byBzZWN1cmUgdGhlIKGwRE5TIGxhc3QgbWlsZaGxLCB0aGVuIHZpYSBzb21lIHBy
b2Nlc3NlcyBhdCB0aGUgc2lkZSBvZiB0aGUgYWNjZXNzIG5ldHdvcmssIGl0IGdldHMgdGhlIElQ
IGFkZHJlc3MgKGVzKSBvZiB0aGUgRE5TIHNlcnZlciBhbmQgdGhlIFNBIHBhcmFtZXRlcnMgaXQg
bmVlZHMgdG8gY29uZmlndXJlIHRvIGVzdGFibGlzaCBJUFNlYyB3aXRoIHRoZSB2ZXJ5IEROUyBz
ZXJ2ZXIuIA0KIA0KUmVjZW50bHkgd2UgYXJlIHdvcmtpbmcgb24gdGhlIGRlc2lnbiBhbmQgYSBk
cmFmdCBpcyBnb2luZyB0byBiZSBzdWJtaXR0ZWQgc29vbi4gDQoNCllvdXJzLA0KRGkgTWENCg0K
Q2hpbmEgSW50ZXJuZXQgTmV0d29yayBJbmZvcm1hdGlvbiBDZW50ZXIgo6hDTk5JQ6OpDQpUZWw6
ICg4NjEwKS01ODgxMzIxNg0KTW9iaWxlOig4NiktMTg2MTE3MTgzMDENCkh0dHBzOi8vd3d3LmNu
bmljLmNuDQpBZGQ6IDQsIFNvdXRoIDR0aCBTdHJlZXQsIFpob25nZ3VhbmN1bg0KSGFpZGlhbiBE
aXN0cmljdCwgQmVpamluZw0KUC5SLkNoaW5hIDEwMDE5MA0KUE9COiBCZWlqaW5nIDM0OSwgQnJh
bmNoIDYNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCg0KRnJvbTogUkogQXRraW5zb24NCkRhdGU6IDIwMTItMDktMjAgMTk6MzANClRvOiByZW51
bQ0KU3ViamVjdDogUmU6IFtyZW51bV0gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi02cmVudW0tZ2Fw
LWFuYWx5c2lzLTAzLnR4dA0KDQpPbiAxOSAgU2VwIDIwMTIsIGF0IDIyOjIyICwgTGl1YmluZyAo
TGVvKSB3cm90ZToNCj4gQnV0IEkgdGhpbmsgd2hhdCBEaSBhbmQgTWFyYyBhcmd1ZWQgaXMgdGhh
dCwNCj4gdGhleSBtaWdodCBmb3VuZCBpbiB0aGVpciBjYXNlcywgdGhlIEZRRE4gYWJpbGl0eQ0K
PiB3YXMgbm90IGVhc3kgdG8gZW5hYmxlLCB3aGljaCBtYXkgY2F1c2VkIGJ5IHZhcmlvdXMgZGVw
bG95bWVudC9pbXBsZW1lbnRhdGlvbiBpc3N1ZXMuDQoNCkl0IHJlYWxseSBpcyB2ZXJ5IGVhc3kg
dG8gZW5hYmxlIGluIHByb2R1Y3RzIGZyb20NCm11bHRpcGxlIHZlbmRvcnMgKGUuZy4gTmV0c2Ny
ZWVuLCBDaXNjbywgSnVuaXBlcikuDQoNCkluIGFueSBjYXNlLCBib3RoICJlYXNlIG9mIHVzZSIg
YW5kICJ1c2VyIGludGVyZmFjZSINCmFyZSBvdXRzaWRlIHRoZSB1c3VhbCBzY29wZSBvZiB0aGUg
SUVURi4NCg0KVGhlIGJpZyBpc3N1ZSBhcHBlYXJzIHRvIGJlIHRoYXQgZm9sa3MgZG9uJ3QgcmVh
bGlzZQ0Kd2h5IHVzaW5nIEZRRE4gaXMgYmV0dGVyIHRoYW4gSVAgYWRkcmVzc2VzIC0tIHdoaWNo
DQppcyB3aHkgUkZDIDU4ODcgdGFsa2VkIGFib3V0IHRoaXMuDQoNCllvdXJzLA0KDQpSYW4NCg0K
DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KcmVudW0g
bWFpbGluZyBsaXN0DQpyZW51bUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9yZW51bQ==

------=_001_NextPart487888456634_=----
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3DGB2312" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: =CE=A2=C8=ED=D1=C5=BA=DA; COLOR: #000080; =
FONT-SIZE: 10.5pt
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 9.00.8112.16448"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US><FONT color=3D#000000>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US>Hi, Ran,<?xml:namespace prefix =3D o ns =3D=20
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US><o:p>&nbsp;</o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US>Thank you very much indeed for your detailed comments. You ha=
ve=20
provided plenty of valuable information. Yet in my previous mail, what I w=
as=20
trying to say is that IPSec itself is an address-based connection, which, =
by the=20
way, has nothing to do with the methods IKE employs to identify the peers=20
negotiating SA parameters. <o:p></o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US><o:p>&nbsp;</o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US>Conspicuously, non-IP-address identifiers such as FQDN can he=
lp IPSec=20
participants to exchange notes, and with IKE IPSec endpoints can recover=20
automatically as you mentioned. The reason why I threw the IPSec issue in =
the=20
category of network renumbering is that at some specific circumstances IPS=
ec SA=20
parameters, as IP address oriented, can be configured in a better way othe=
r than=20
IKE (v2) to go with renumbering events.<o:p></o:p></SPAN></P>
<P style=3D"TEXT-ALIGN: left; MARGIN: 0cm 0cm 0pt; mso-pagination: widow-o=
rphan"=20
class=3DMsoNormal align=3Dleft><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US><o:p>&nbsp;</o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US>By the virtue of specific network operations, SA configuratio=
n=20
management could be fancied in an optimized way. Customer Premises Network=
 (CPN)=20
offers a scenario where the configuration of SA parameters for specific IP=
Sec=20
participants can be integrated into IP address assignment. As widely obser=
ved,=20
some CPN services such as DNS recursive resolution service, SIP proxy serv=
ice,=20
are expected to have integrity and confidentiality protection. That is, fr=
om the=20
point of view of a user host, SA parameters bound to DNS recursive name se=
rver=20
or SIP server, can be considered <A href=3D"app:ds:undifferentiated"=20
target=3D_self><SPAN=20
style=3D"COLOR: windowtext; TEXT-DECORATION: none; text-underline: none">u=
ndifferentiated</SPAN></A>=20
with other network parameters, such as IP address of the user host, defaul=
t=20
gateway address, that are commonly configured via DHCP.</SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US></SPAN><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US><SPAN style=3D"mso-spacerun: yes">&nbsp;</SPAN><o:p></o:p></S=
PAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US>Since the IPSec is address-oriented and the DHCP server is=20
responsible for IP address configuration, we might as well integrate IPSec=
 SA=20
parameters configuration into IP address assignment by extending DHCP wher=
e the=20
IP address configuration node (DHCP server) plays like an =A1=B0administra=
tor=A1=B1 using=20
DHCP to configure IPSec SA parameters in a host, after it, in deputy of th=
e=20
host, has negotiated with a CPN server the very host wants to establish IP=
Sec=20
with.&nbsp; Consequently, after the renumbering event, the user host can g=
et a=20
new IP address and new SA parameters piggybacked via DHCP=20
messages.<o:p></o:p><o:p></o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US><o:p>&nbsp;</o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US>To be exact, in this scenario, the user host will be a SA=20
establishment initiator and the DHCP server will serve as the deputy for t=
he=20
user host to negotiate SA parameters with the CPN server such as DNS recur=
sive=20
name server, SIP server, etc. The superiority of granting SA management to=
 DHCP=20
server is that the SA negotiation will be simplified based on the preconfi=
gured=20
trust relationship between the DHCP server and other CPN servers, since in=
=20
regular CPN scenarios, the DHCP server and CPN servers are usually at the =
same=20
administration domain, sometimes even integrated in the same device, which=
 makes=20
the IKEv2 authentication exchanges unnecessary.<SPAN=20
style=3D"mso-spacerun: yes">&nbsp; </SPAN>Secure tunnels, such as HTTPS or=
 other=20
secure protocols with less rounds could be easily applied to protect the=20
communication between the DHCP server and CPN server when needed.&nbsp;=20
<o:p></o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US><o:p>&nbsp;</o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US>Once the very method is realized, the IPSec SA negotiation is=
=20
transparent to user hosts especially the handheld devices that are conside=
red as=20
=A1=B0thin clients=A1=B1. The user host tells the configuration entity, DH=
CP server for=20
instance, it wants to know the IP address of DNS recursive name server and=
 it=20
wants to employ IPSec to secure the =A1=B0DNS last mile=A1=B1, then via so=
me processes at=20
the side of the access network, it gets the IP address (es) of the DNS ser=
ver=20
and the SA parameters it needs to configure to establish IPSec with the ve=
ry DNS=20
server. <o:p></o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US><o:p>&nbsp;</o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal><SPAN=20
style=3D"FONT-FAMILY: 'Cambria Math','serif'; FONT-SIZE: 11pt; mso-bidi-fo=
nt-family: 'Times New Roman'"=20
lang=3DEN-US>Recently we are working on the design and a draft is going to=
 be=20
submitted soon. <o:p></o:p></SPAN></P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal>&nbsp;</P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal>Yours,</P>
<P style=3D"MARGIN: 0cm 0cm 0pt; TEXT-AUTOSPACE: ; mso-layout-grid-align: =
none"=20
class=3DMsoNormal>Di Ma</FONT></SPAN></P></DIV>
<DIV><SPAN>
<DIV><SPAN style=3D"FONT-FAMILY: =CB=CE=CC=E5; COLOR: #000000; FONT-SIZE: =
10.5pt">
<DIV>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff face=3D"Courier New"><FONT color=3D#0000ff=20
face=3D"Courier New"><BR></FONT></FONT><FONT color=3D#0000ff=20
face=3D"Courier New">China Internet Network Information Center =A3=A8CNNIC=
=A3=A9<BR>Tel:=20
(8610)-58813216</FONT></P>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff face=3D"Courier New">Mobile:(86)-18611718301<BR></FONT><FO=
NT=20
color=3D#0000ff face=3D"Courier New">Https://www.cnnic.cn</FONT></P>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff face=3D"Courier New">Add: 4, South 4th Street,=20
Zhongguancun<BR>Haidian District, Beijing<BR>P.R.China 100190</FONT></P>
<P style=3D"MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px" class=3DMsoNormal><FONT=20
color=3D#0000ff><SPAN style=3D"FONT-FAMILY: Arial"><FONT size=3D2=20
face=3D"Courier New">POB: Beijing 349, Branch 6</FONT></SPAN><BR><FONT=20
face=3D"Courier New">____________________________________________________<=
/FONT></P></FONT></DIV></SPAN></DIV></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:rja.lists@gmail.com">RJ=20
Atkinson</A></DIV>
<DIV><B>Date:</B>&nbsp;2012-09-20&nbsp;19:30</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:renum@ietf.org">renum</A></DIV>
<DIV><B>Subject:</B>&nbsp;Re: [renum] I-D Action:=20
draft-ietf-6renum-gap-analysis-03.txt</DIV></DIV></DIV>
<DIV>
<DIV>&nbsp;</DIV>
<DIV>On&nbsp;19&nbsp;&nbsp;Sep&nbsp;2012,&nbsp;at&nbsp;22:22&nbsp;,&nbsp;L=
iubing&nbsp;(Leo)&nbsp;wrote:</DIV>
<DIV>&gt;&nbsp;But&nbsp;I&nbsp;think&nbsp;what&nbsp;Di&nbsp;and&nbsp;Marc&=
nbsp;argued&nbsp;is&nbsp;that,</DIV>
<DIV>&gt;&nbsp;they&nbsp;might&nbsp;found&nbsp;in&nbsp;their&nbsp;cases,&n=
bsp;the&nbsp;FQDN&nbsp;ability</DIV>
<DIV>&gt;&nbsp;was&nbsp;not&nbsp;easy&nbsp;to&nbsp;enable,&nbsp;which&nbsp=
;may&nbsp;caused&nbsp;by&nbsp;various&nbsp;deployment/implementation&nbsp;=
issues.</DIV>
<DIV>&nbsp;</DIV>
<DIV>It&nbsp;really&nbsp;is&nbsp;very&nbsp;easy&nbsp;to&nbsp;enable&nbsp;i=
n&nbsp;products&nbsp;from</DIV>
<DIV>multiple&nbsp;vendors&nbsp;(e.g.&nbsp;Netscreen,&nbsp;Cisco,&nbsp;Jun=
iper).</DIV>
<DIV>&nbsp;</DIV>
<DIV>In&nbsp;any&nbsp;case,&nbsp;both&nbsp;"ease&nbsp;of&nbsp;use"&nbsp;an=
d&nbsp;"user&nbsp;interface"</DIV>
<DIV>are&nbsp;outside&nbsp;the&nbsp;usual&nbsp;scope&nbsp;of&nbsp;the&nbsp=
;IETF.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The&nbsp;big&nbsp;issue&nbsp;appears&nbsp;to&nbsp;be&nbsp;that&nbsp;f=
olks&nbsp;don't&nbsp;realise</DIV>
<DIV>why&nbsp;using&nbsp;FQDN&nbsp;is&nbsp;better&nbsp;than&nbsp;IP&nbsp;a=
ddresses&nbsp;--&nbsp;which</DIV>
<DIV>is&nbsp;why&nbsp;RFC&nbsp;5887&nbsp;talked&nbsp;about&nbsp;this.</DIV=
>
<DIV>&nbsp;</DIV>
<DIV>Yours,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Ran</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>_______________________________________________</DIV>
<DIV>renum&nbsp;mailing&nbsp;list</DIV>
<DIV>renum@ietf.org</DIV>
<DIV>https://www.ietf.org/mailman/listinfo/renum</DIV></DIV></BODY></HTML>

------=_001_NextPart487888456634_=------


From rja.lists@gmail.com  Fri Sep 21 04:11:27 2012
Return-Path: <rja.lists@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 3E39121F8786 for <renum@ietfa.amsl.com>; Fri, 21 Sep 2012 04:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 5wRWbAwj3I-b for <renum@ietfa.amsl.com>; Fri, 21 Sep 2012 04:11:26 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id A0B6F21F8687 for <renum@ietf.org>; Fri, 21 Sep 2012 04:11:26 -0700 (PDT)
Received: by qcac10 with SMTP id c10so2885419qca.31 for <renum@ietf.org>; Fri, 21 Sep 2012 04:11:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:x-priority:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=TfOly4gs3zbrnh3WUsqrJn5nklujdzftEMknTh0TWIs=; b=MjClEIwNNocmRizK9cYXGVYgI1Mu/gZWBHAnyqrZsjz5VkGb+wx13c7qoW6aPWpEie k+QGcaay0TC8tIVTeb0d4t6f6/3oBTvzMpXGpD8QYa2PUPs3DvhbDaH+97oE36M269Ut VWzCcxFH9MvGgBlyjJjyUW4ccWt5zwZWccS+B3QyxhMuJlQluWBJVQhtEMIZPxTVHBqS bsFSTygrUtGxT4QSzyoVJh+EtsiTNY6TkVhacZhzRvDlmUE12UJmVN9QmOlnRrRCdqe2 gwX/7UxvM0lnW9SoXQp1nZ7JHfHQljnZTVLNwuJtY15fiTMk7Dgmofx6x9HJuswaTR0k Wy1g==
Received: by 10.224.39.147 with SMTP id g19mr11511491qae.46.1348225886147; Fri, 21 Sep 2012 04:11:26 -0700 (PDT)
Received: from [10.30.20.13] (pool-74-110-100-136.nrflva.fios.verizon.net. [74.110.100.136]) by mx.google.com with ESMTPS id o9sm12080146qao.7.2012.09.21.04.11.24 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 21 Sep 2012 04:11:25 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: RJ Atkinson <rja.lists@gmail.com>
X-Priority: 3
In-Reply-To: <201209210356573495357@cnnic.cn>
Date: Fri, 21 Sep 2012 07:11:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <27FE2BC1-E089-4FED-9197-002AE3ABD1FF@gmail.com>
References: <07A9B495-21EA-4DFD-84BC-AF5BB6B62BE2@gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F452935720A@szxeml509-mbs>, <E2FEB233-3206-4E6C-B54D-BA832B545009@gmail.com> <201209210356573495357@cnnic.cn>
To: renum@ietf.org
X-Mailer: Apple Mail (2.1278)
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.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: Fri, 21 Sep 2012 11:11:27 -0000

On 20  Sep 2012, at 15:56 , Di Ma wrote:
> Since the IPSec is address-oriented...

We continue to disagree about this.

> ...and the DHCP server is responsible for IP address configuration,
> we might as well integrate IPSec SA parameters configuration into
> IP address assignment by extending DHCP where the IP address
> configuration node (DHCP server) plays like an =93administrator=94
> using DHCP to configure IPSec SA parameters in a host, after it,
> in deputy of the host, has negotiated with a CPN server the
> very host wants to establish IPSec with. =20

This seems very unwise for any IETF standards work,
from multiple perspectives.  A quick subset of examples,
each by itself sufficient to illustrate why this would
be unwise, follow:


* A very basic one is that one would not want to standardise=20
  the trust model issues that such an approach would create.

  EXAMPLE:
  While I might trust the DHCP server at the coffee shop
  for the limited function of assigning an IP address and
  conveying minimally essential IP-layer information to my
  laptop, I definitely DO NOT trust the coffee shop network
  or its infrastructure components (e.g. DHCP server).  So
  when I would begin work, I would always want to directly
  secure the communications channel between my laptop and
  my workplace -- without ANY intermediaries.


* Related to that, user security and privacy would be=20
  compromised by such centralisation and the delegation=20
  implied by "in deputy of the host". =20

  EXAMPLE:
  Basically, the proposal would be to standardise use of any
  DHCP server as an attacker for an automated "man in the middle"=20
  attack.  I see zero chance of the IETF Security Area
  approving this.


* DHCP is not suitable for key management, while the above
  proposes using DHCP to manage keys (IPsec SAs).


Given these issues, and previous notes in this thread explaining
how IPsec-related renumbering works today, it is not obvious that=20
the contents of your note are appropriate for this gap analysis=20
document. =20

Yours,

Ran



From brian.e.carpenter@gmail.com  Fri Sep 21 05:27:15 2012
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 7848E21F8815 for <renum@ietfa.amsl.com>; Fri, 21 Sep 2012 05:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.566
X-Spam-Level: 
X-Spam-Status: No, score=-103.566 tagged_above=-999 required=5 tests=[AWL=0.033, 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 3KHUCY7zb8uS for <renum@ietfa.amsl.com>; Fri, 21 Sep 2012 05:27:14 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id C40B321F8810 for <renum@ietf.org>; Fri, 21 Sep 2012 05:27:14 -0700 (PDT)
Received: by iec9 with SMTP id 9so6008857iec.31 for <renum@ietf.org>; Fri, 21 Sep 2012 05:27:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=a02lfJuwEymEPt56F9a6Uo+THJBg+zrPiyBaxYA5Kaw=; b=NYv6dkE1MgKkk4wnA9L6zmbcBmNXN7CCMwy1nX4WMoNGaglPGfEn3cMOmC2nLydFw3 0R9XPmPfUr/otVeu0frOr6DuEGfR6/u26ITRJGaxlhZ2Rl07GUYVr6t2weM/Rvd4EGrd m2Yp/GgUA1VTwzR2i0NfdxLzQshm3byFH9NuK9y6ib63u0qH6tWNM5u/W2x8YvtGGdX9 yaETnmN/TpxrITwbVu2ro6lZkNDeRtWCGxtVBlycPGguD8Kko5kTSVwkq/T/zEuOKl/S R/7QxMwC+Lbuy/kFYttsK67wU/XaaA0OyPg7f/trAhbaX1KqtQrSHERV5hvo3Sa+YM47 xjCw==
Received: by 10.50.7.177 with SMTP id k17mr1495716iga.27.1348230434164; Fri, 21 Sep 2012 05:27:14 -0700 (PDT)
Received: from [10.255.25.102] (50-76-68-140-static.hfc.comcastbusiness.net. [50.76.68.140]) by mx.google.com with ESMTPS id a10sm12468913igd.1.2012.09.21.05.27.12 (version=SSLv3 cipher=OTHER); Fri, 21 Sep 2012 05:27:13 -0700 (PDT)
Message-ID: <505C5D28.5080409@gmail.com>
Date: Fri, 21 Sep 2012 13:27:20 +0100
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: RJ Atkinson <rja.lists@gmail.com>
References: <07A9B495-21EA-4DFD-84BC-AF5BB6B62BE2@gmail.com>	<8AE0F17B87264D4CAC7DE0AA6C406F452935720A@szxeml509-mbs>, <E2FEB233-3206-4E6C-B54D-BA832B545009@gmail.com>	<201209210356573495357@cnnic.cn> <27FE2BC1-E089-4FED-9197-002AE3ABD1FF@gmail.com>
In-Reply-To: <27FE2BC1-E089-4FED-9197-002AE3ABD1FF@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: renum@ietf.org
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.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: Fri, 21 Sep 2012 12:27:15 -0000

On 21/09/2012 12:11, RJ Atkinson wrote:
> On 20  Sep 2012, at 15:56 , Di Ma wrote:
>> Since the IPSec is address-oriented...
>=20
> We continue to disagree about this.

Put it this way. The community needs to change its bad habit of using IPS=
ec
in an address-oriented way, and renumbering is one of the main reasons
for that. So it is 6renum's job to strongly recommend the change.

It remains true, of course, that even if an SA survives renumbering,
the transport session running over that SA will also have to be renumbere=
d,
but that's a separate problem.

   Brian

>=20
>> ...and the DHCP server is responsible for IP address configuration,
>> we might as well integrate IPSec SA parameters configuration into
>> IP address assignment by extending DHCP where the IP address
>> configuration node (DHCP server) plays like an =E2=80=9Cadministrator=E2=
=80=9D
>> using DHCP to configure IPSec SA parameters in a host, after it,
>> in deputy of the host, has negotiated with a CPN server the
>> very host wants to establish IPSec with. =20
>=20
> This seems very unwise for any IETF standards work,
> from multiple perspectives.  A quick subset of examples,
> each by itself sufficient to illustrate why this would
> be unwise, follow:
>=20
>=20
> * A very basic one is that one would not want to standardise=20
>   the trust model issues that such an approach would create.
>=20
>   EXAMPLE:
>   While I might trust the DHCP server at the coffee shop
>   for the limited function of assigning an IP address and
>   conveying minimally essential IP-layer information to my
>   laptop, I definitely DO NOT trust the coffee shop network
>   or its infrastructure components (e.g. DHCP server).  So
>   when I would begin work, I would always want to directly
>   secure the communications channel between my laptop and
>   my workplace -- without ANY intermediaries.
>=20
>=20
> * Related to that, user security and privacy would be=20
>   compromised by such centralisation and the delegation=20
>   implied by "in deputy of the host". =20
>=20
>   EXAMPLE:
>   Basically, the proposal would be to standardise use of any
>   DHCP server as an attacker for an automated "man in the middle"=20
>   attack.  I see zero chance of the IETF Security Area
>   approving this.
>=20
>=20
> * DHCP is not suitable for key management, while the above
>   proposes using DHCP to manage keys (IPsec SAs).
>=20
>=20
> Given these issues, and previous notes in this thread explaining
> how IPsec-related renumbering works today, it is not obvious that=20
> the contents of your note are appropriate for this gap analysis=20
> document. =20
>=20
> Yours,
>=20
> Ran
>=20
>=20
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
>=20


From rja.lists@gmail.com  Fri Sep 21 06:16:23 2012
Return-Path: <rja.lists@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 C674621F87FB for <renum@ietfa.amsl.com>; Fri, 21 Sep 2012 06:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 3hA-Vwi4zCad for <renum@ietfa.amsl.com>; Fri, 21 Sep 2012 06:16:23 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC7621F87E5 for <renum@ietf.org>; Fri, 21 Sep 2012 06:16:23 -0700 (PDT)
Received: by qcac10 with SMTP id c10so2987552qca.31 for <renum@ietf.org>; Fri, 21 Sep 2012 06:16:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=1LPzo2whI+Xa8+6PjLQ2ZFIDN1Cs7yWnIVCaivIrj1k=; b=XbRHoF36LN48iWJHbAI0cTOyFw+j5sQz1aMxoYcsTvG+cmIoeJVqyp/zT9fhIrTRbX Kf0uzMTCW2QwjxJdL4WbxYVLj8XrtIZ2RzMPOh9FHsSQK7cLJp98HE6xzG7THiZac4oe UUc+LEXQMaGOBNL4qbwWRSpasXa9IyRwI1ZcDfhVYLYg+/iSUZIbZOonSVNF48rw7T5b b7YbrjcjMOkxKEza/ZnvILktEePkxF9MV0Y3E+DVKHlLxuSKV/KZ6gHtw64PW5lqkPsl APg3fe75vmfaggq1gylzrzZtfLjUDTTMwVmJ3ir050kcdJA3c+pl2p2s8iHlLBJpah1E wsvA==
Received: by 10.224.209.7 with SMTP id ge7mr10926472qab.30.1348233382766; Fri, 21 Sep 2012 06:16:22 -0700 (PDT)
Received: from [10.30.20.13] (pool-74-110-100-136.nrflva.fios.verizon.net. [74.110.100.136]) by mx.google.com with ESMTPS id gx8sm928428qab.12.2012.09.21.06.16.21 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 21 Sep 2012 06:16:22 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <505C5D28.5080409@gmail.com>
Date: Fri, 21 Sep 2012 09:16:20 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <1B851043-52E6-4CEB-9620-5A6613D444A6@gmail.com>
References: <07A9B495-21EA-4DFD-84BC-AF5BB6B62BE2@gmail.com>	<8AE0F17B87264D4CAC7DE0AA6C406F452935720A@szxeml509-mbs>, <E2FEB233-3206-4E6C-B54D-BA832B545009@gmail.com>	<201209210356573495357@cnnic.cn> <27FE2BC1-E089-4FED-9197-002AE3ABD1FF@gmail.com> <505C5D28.5080409@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: renum@ietf.org
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-03.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: Fri, 21 Sep 2012 13:16:23 -0000

On 21  Sep 2012, at 08:27 , Brian E Carpenter wrote:
> Put it this way. The community needs to change its bad habit
> of using IPSec in an address-oriented way, and renumbering
> is one of the main reasons for that. So it is 6renum's job
> to strongly recommend the change.

I fully agree.

Ran


From eleven.fuyu@huawei.com  Thu Sep 27 03:33:04 2012
Return-Path: <eleven.fuyu@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 DDBC721F86DE for <renum@ietfa.amsl.com>; Thu, 27 Sep 2012 03:33:04 -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 CEcexkpNd8zk for <renum@ietfa.amsl.com>; Thu, 27 Sep 2012 03:33:04 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE8B21F86E1 for <renum@ietf.org>; Thu, 27 Sep 2012 03:33:03 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ALC25188; Thu, 27 Sep 2012 10:33:02 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 27 Sep 2012 11:32:07 +0100
Received: from SZXEML436-HUB.china.huawei.com (10.72.61.64) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 27 Sep 2012 11:33:00 +0100
Received: from SZXEML512-MBX.china.huawei.com ([169.254.5.187]) by szxeml436-hub.china.huawei.com ([10.72.61.64]) with mapi id 14.01.0323.003; Thu, 27 Sep 2012 18:32:55 +0800
From: "Fuyu (Eleven)" <eleven.fuyu@huawei.com>
To: "Howard, Lee" <lee.howard@twcable.com>
Thread-Topic: [renum] Working Group Last Call: draft-ietf-6renum-static-problem-01.txt
Thread-Index: Ac2SmleJUG5z5HTMQcKalR8udC2pCgJwQDuQ
Date: Thu, 27 Sep 2012 10:32:54 +0000
Message-ID: <EF6A204047BD994A860EE26D5F23BF582B8E354C@SZXEML512-MBX.china.huawei.com>
References: <99B887114EDB1449941CFBC8EC279FA12D016997@PRVPEXVS17.corp.twcable.com>
In-Reply-To: <99B887114EDB1449941CFBC8EC279FA12D016997@PRVPEXVS17.corp.twcable.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Working Group Last Call:	draft-ietf-6renum-static-problem-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: Thu, 27 Sep 2012 10:33:05 -0000

	This document analyzes several problems of why the hosts need to update th=
eir IPv6 addresses but for some reasons they require static address.=20
    Some methods of how to avoid this scenarios and potential gaps also hav=
e been analyzed in the document.
    I think it is useful and meaningful and I am in favor of advancing this=
 document.

    BR
    Yu

-----Original Message-----
From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of H=
oward, Lee
Sent: Saturday, September 15, 2012 1:01 AM
To: renum@ietf.org
Subject: [renum] Working Group Last Call: draft-ietf-6renum-static-problem-=
01.txt

We are requesting a Working Group Last Call on this document.  Please revie=
w and provide comments before September 28, since this may be the final rev=
iew of this document.

Thanks,

Lee

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of=
 internet-
> drafts@ietf.org
> Sent: Friday, August 31, 2012 3:00 AM
> To: i-d-announce@ietf.org
> Cc: renum@ietf.org
> Subject: [renum] I-D Action: draft-ietf-6renum-static-problem-01.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the IPv6 Site Renumbering Working Group of =
the IETF.
>
>       Title           : Problem Statement for Renumbering IPv6 Hosts with=
 Static Addresses
>       Author(s)       : Brian Carpenter
>                           Sheng Jiang
>       Filename        : draft-ietf-6renum-static-problem-01.txt
>       Pages           : 12
>       Date            : 2012-08-30
>
> Abstract:
>    This document analyses the problems of updating the IPv6 addresses of
>    hosts in enterprise networks that for operational reasons require
>    static addresses.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6renum-static-problem-01
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-static-problem-01
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

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.
_______________________________________________
renum mailing list
renum@ietf.org
https://www.ietf.org/mailman/listinfo/renum

From internet-drafts@ietf.org  Sun Sep 30 06:56:01 2012
Return-Path: <internet-drafts@ietf.org>
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 5C8C421F8530; Sun, 30 Sep 2012 06:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.509
X-Spam-Level: 
X-Spam-Status: No, score=-102.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, 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 WaxOm7eLs1Co; Sun, 30 Sep 2012 06:56:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C151B21F8516; Sun, 30 Sep 2012 06:55:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120930135545.21049.14776.idtracker@ietfa.amsl.com>
Date: Sun, 30 Sep 2012 06:55:45 -0700
Cc: renum@ietf.org
Subject: [renum] I-D Action: draft-ietf-6renum-static-problem-02.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: Sun, 30 Sep 2012 13:56:01 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Site Renumbering Working Group of th=
e IETF.

	Title           : Problem Statement for Renumbering IPv6 Hosts with Static=
 Addresses
	Author(s)       : Brian Carpenter
                          Sheng Jiang
	Filename        : draft-ietf-6renum-static-problem-02.txt
	Pages           : 12
	Date            : 2012-09-30

Abstract:
   This document analyses the problems of updating the IPv6 addresses of
   hosts in enterprise networks that for operational reasons require
   static addresses.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6renum-static-problem-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-static-problem-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From brian.e.carpenter@gmail.com  Sun Sep 30 06:59:38 2012
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 DE24021F856C for <renum@ietfa.amsl.com>; Sun, 30 Sep 2012 06:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.554
X-Spam-Level: 
X-Spam-Status: No, score=-103.554 tagged_above=-999 required=5 tests=[AWL=0.045, 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 KxTdK3DVj1Ul for <renum@ietfa.amsl.com>; Sun, 30 Sep 2012 06:59:38 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 60D4121F855D for <renum@ietf.org>; Sun, 30 Sep 2012 06:59:38 -0700 (PDT)
Received: by iec9 with SMTP id 9so12006099iec.31 for <renum@ietf.org>; Sun, 30 Sep 2012 06:59:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=RnruweL6lQRMPr0Km6S/olYBIzL6f+hWIHRvf7RYdcw=; b=S3hNW0x61Px2vDzJ494cQBiXVVOQD7j8x+OsYHQr0dza6q+WwXUcUuHuLN31ZnRzBT jaMLPCK+Sqlg6Eo/95jm9/GfWWZ4D4eh3YU7p3qXUqwipDm2LFiPlclBJ0bkzzVuheue 39R24MU3Ou2sBAgcIv/z9O872vmAVLhnceO7f623sat8rWdV3bio/XvvsjwCrtT1TvLC 0mEbDRSSNB228S0fS7u0kHRnBJ3AkgJNwCD89WWArrSyPDOMkAXvlq+zo4W83DylsT3N sOgxeExzczFdk3FHHhJM8lQNJlqfww+BecD8jrKqw+7RSJARrrIULWppYrjFJQcjxsWd wGOA==
Received: by 10.50.149.228 with SMTP id ud4mr3297221igb.16.1349013577977; Sun, 30 Sep 2012 06:59:37 -0700 (PDT)
Received: from [10.255.25.102] (50-76-68-140-static.hfc.comcastbusiness.net. [50.76.68.140]) by mx.google.com with ESMTPS id us4sm4355708igc.9.2012.09.30.06.59.37 (version=SSLv3 cipher=OTHER); Sun, 30 Sep 2012 06:59:37 -0700 (PDT)
Message-ID: <50685048.2020205@gmail.com>
Date: Sun, 30 Sep 2012 14:59:36 +0100
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: renum@ietf.org
References: <20120930135545.21049.14776.idtracker@ietfa.amsl.com>
In-Reply-To: <20120930135545.21049.14776.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [renum] I-D Action: draft-ietf-6renum-static-problem-02.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: Sun, 30 Sep 2012 13:59:39 -0000

This version deals with the comments received during WGLC:
 clarified discussion of SLP and mDNS
 expanded discussion of configuration tool

Regards
   Brian

On 30/09/2012 14:55, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the IPv6 Site Renumbering Working Group of the IETF.
> 
> 	Title           : Problem Statement for Renumbering IPv6 Hosts with Static Addresses
> 	Author(s)       : Brian Carpenter
>                           Sheng Jiang
> 	Filename        : draft-ietf-6renum-static-problem-02.txt
> 	Pages           : 12
> 	Date            : 2012-09-30
> 
> Abstract:
>    This document analyses the problems of updating the IPv6 addresses of
>    hosts in enterprise networks that for operational reasons require
>    static addresses.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6renum-static-problem-02
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6renum-static-problem-02
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
> 
