
From Wesley.E.George@sprint.com  Sun Apr  3 17:09:42 2011
Return-Path: <Wesley.E.George@sprint.com>
X-Original-To: renum@core3.amsl.com
Delivered-To: renum@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDF853A68DE for <renum@core3.amsl.com>; Sun,  3 Apr 2011 17:09:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.466
X-Spam-Level: 
X-Spam-Status: No, score=-5.466 tagged_above=-999 required=5 tests=[AWL=1.133,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lHr+ankguUro for <renum@core3.amsl.com>; Sun,  3 Apr 2011 17:09:37 -0700 (PDT)
Received: from VA3EHSOBE007.bigfish.com (va3ehsobe006.messaging.microsoft.com [216.32.180.16]) by core3.amsl.com (Postfix) with ESMTP id 7880028B56A for <renum@ietf.org>; Sun,  3 Apr 2011 17:09:37 -0700 (PDT)
Received: from mail173-va3-R.bigfish.com (10.7.14.254) by VA3EHSOBE007.bigfish.com (10.7.40.11) with Microsoft SMTP Server id 14.1.225.8; Mon, 4 Apr 2011 00:11:19 +0000
Received: from mail173-va3 (localhost.localdomain [127.0.0.1])	by mail173-va3-R.bigfish.com (Postfix) with ESMTP id 3D0291708092; Mon,  4 Apr 2011 00:11:19 +0000 (UTC)
X-SpamScore: -47
X-BigFish: VS-47(zf7Iz936eK9371P542N1418M4015Lzz1202hzz1033IL8275dhz2fh2a8h668h839h34h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: KIP:(null); UIP:(null); IPVD:NLI; H:plsasdm2.corp.sprint.com; RD:smtpls2.sprint.com; EFVD:NLI
Received: from mail173-va3 (localhost.localdomain [127.0.0.1]) by mail173-va3 (MessageSwitch) id 130187587844033_31387; Mon,  4 Apr 2011 00:11:18 +0000 (UTC)
Received: from VA3EHSMHS022.bigfish.com (unknown [10.7.14.235])	by mail173-va3.bigfish.com (Postfix) with ESMTP id F14D71A2004F; Mon,  4 Apr 2011 00:11:17 +0000 (UTC)
Received: from plsasdm2.corp.sprint.com (144.230.168.26) by VA3EHSMHS022.bigfish.com (10.7.99.32) with Microsoft SMTP Server (TLS) id 14.1.225.8; Mon, 4 Apr 2011 00:11:17 +0000
Received: from PDAWEH01.ad.sprint.com (PDAWEH01.corp.sprint.com [144.226.110.69])	by plsasdm2.corp.sprint.com (Sentrion-MTA-4.0.5/Sentrion-MTA-4.0.5) with ESMTP id p340BET0018708 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 3 Apr 2011 19:11:14 -0500
Received: from PLSWEH04.ad.sprint.com (144.226.251.22) by PDAWEH01.ad.sprint.com (144.226.110.69) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sun, 3 Apr 2011 19:11:14 -0500
Received: from PLSWM12A.ad.sprint.com ([fe80::dd81:e8a1:cd6b:78f]) by PLSWEH04.ad.sprint.com ([2002:90e2:fb16::90e2:fb16]) with mapi id 14.01.0270.001; Sun, 3 Apr 2011 19:11:14 -0500
From: "George, Wes E [NTK]" <Wesley.E.George@sprint.com>
To: Sheng Jiang <shengjiang@huawei.com>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00
Thread-Index: AQHLvT13deLdjBNuyUy7p0vAJHcYwZRLKeAA
Date: Mon, 4 Apr 2011 00:11:13 +0000
Message-ID: <54E900DC635DAB4DB7A6D799B3C4CD8E10C6AD2E@PLSWM12A.ad.sprint.com>
References: <4D3FECA9.6060109@huawei.com>
In-Reply-To: <4D3FECA9.6060109@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.214.116.75]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_025E_01CBF13C.671F2FE0"
MIME-Version: 1.0
X-OriginatorOrg: sprint.com
Subject: Re: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 04 Apr 2011 00:09:42 -0000

------=_NextPart_000_025E_01CBF13C.671F2FE0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Wanted to get some of my comments from the mic out to the list-

I think that there are a number of places where we need to break up the problem space in order to make it more manageable, both in
terms of work that this group might take on vs work that is already partially done/belongs in existing groups, etc. Please add to
the list and provide comments...

Questions:
Do we care about supporting hitless renumbering (that is, some form of make-before-break that allows end hosts to migrate their
active sessions)?
 - I say nice to have, if at all, definitely not a primary goal
Should we be considering an encapsulation (like IRON) or Locator ID split implementation within scope to solve the renumbering
problem?
 - I say that we should be concentrating on renumbering problems that we can solve independent of any improved support in the
network infrastructure for mobility and route scaling, but others may disagree.

Different problem spaces:
- BCP on how to limit the impact of renumbering when it is required - especially important as IPv6 rolls out and people are doing
their once-in-a-blue-moon numbering plans, plus code work to support it
- Device config:
*on-box CLI and the places where it supports/requires IP address literals - places we can recommend that vendors support
parameterization either through FQDNs or external files that allow you to change an address in multiple places in the config at once
*a centralized management infrastructure that abstracts local config  from addressing
*Dynamically numbered devices/networks vs static

Thanks, 
Wes George

-----Original Message-----
From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of Sheng Jiang
Sent: Wednesday, January 26, 2011 4:43 AM
To: renum@ietf.org
Subject: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00


A new version of I-D, draft-jiang-ipv6-site-renum-guideline-00.txt has been successfully submitted by Sheng Jiang and posted to the
IETF repository.

Filename:	 draft-jiang-ipv6-site-renum-guideline
Revision:	 00
Title:		 IPv6 Site Renumbering Guidelines and Further Works
Creation_date:	 2011-01-26
WG ID:		 Independent Submission
Number_of_pages: 13

Abstract:
This document analyzes the existing issues for IPv6 site renumbering.
It also analyzes the possible directions to solve these issues and gives recommendations. This document only takes the perspective
of network and network protocols. Renumbering in IPv4 networks, in the dual-stack network or in the IPv4/IPv6 transition networks
are out of scope.

This document only takes the perspective of network and network protocols. According to the different stages, these issues are
described in three categories: considerations during network design, considerations for routine network management, and
considerations during renumbering operation. Recommended solutions or strategies are also described. Issues that still remain
unsolvable are listed as the fourth category.

Although we list a few non-network issues in this document, we consider them as issues that ISPs or network providers cannot affect.
So, these issues are considered to be unsolvable and not explore further in these document, though they may be solved by OS
implementations or application implementations.

We summary the requests that need to extend current protocols as further works at the end of this document.
 



The IETF Secretariat.



_______________________________________________
renum mailing list
renum@ietf.org
https://www.ietf.org/mailman/listinfo/renum


------=_NextPart_000_025E_01CBF13C.671F2FE0
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIXHjCCBPYw
ggPeoAMCAQICChTCbVgAAAAAAAUwDQYJKoZIhvcNAQEFBQAwcTEbMBkGA1UECxMSQ29weXJpZ2h0
IChjKSAyMDA3MRYwFAYDVQQLEw1TcHJpbnQgTmV4dGVsMTowOAYDVQQDEzFTcHJpbnQgTmV4dGVs
IEVudGVycHJpc2UgSW50ZXJtZWRpYXRlIDEgQXV0aG9yaXR5MB4XDTA3MDcxNzE5NDIxNloXDTE1
MDcxNzE5NTIxNloweDETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBnNwcmlu
dDESMBAGCgmSJomT8ixkARkWAmFkMTUwMwYDVQQDEyxTcHJpbnQgTmV4dGVsIEVudGVycHJpc2Ug
SXNzdWluZyAxIEF1dGhvcml0eTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL95aoB4
LLMFIOaq8WTtWyNCb7m5xoKdM6oJKXsCx8k8GATPtiX7VPXKMjRNv+jMZXKF9U6RA4wjSKiKMOYg
48ioSpanTxp+7p6+00Nr/eEtjsY+21rDQbANaqFGfkRFv4m59jM53j+mEXIDybTttcQN/CdSvI0d
XOD3KxQTPaG+h9uqZmkrdlk/rwvGbKhqmsl2BApItCDlUWt4rbv0GYQR4GP0w6c7e5prJBh89PEq
y+NDtv14YqYl5zOBST4IoHX77uS9gZXqglhtpYKDfESgrgcMldsfKyjrOwiRlT7o8ez1iOyCULkp
RcGLSe3wxZxx82bPEYjSWJf56V21FV0CAwEAAaOCAYcwggGDMA8GA1UdEwEB/wQFMAMBAf8wHQYD
VR0OBBYEFAGPJVAshjSbwX6QH9mINbU/rwuJMAsGA1UdDwQEAwIBhjAQBgkrBgEEAYI3FQEEAwIB
ADAZBgkrBgEEAYI3FAIEDB4KAFMAdQBiAEMAQTAfBgNVHSMEGDAWgBRRAcgiA5nZbiss2II5eNyr
GXZEcTBuBgNVHR8EZzBlMGOgYaBfhjBodHRwOi8vY3JsLmNvcnAuc3ByaW50LmNvbS9QUEtJV0Iw
MS9QUEtJV0IwMS5jcmyGK2h0dHA6Ly9jcmwuc3ByaW50LmNvbS9QUEtJV0IwMS9QUEtJV0IwMS5j
cmwwgYUGCCsGAQUFBwEBBHkwdzA8BggrBgEFBQcwAoYwaHR0cDovL2NybC5jb3JwLnNwcmludC5j
b20vUFBLSVdCMDEvUFBLSVdCMDEuY3J0MDcGCCsGAQUFBzAChitodHRwOi8vY3JsLnNwcmludC5j
b20vUFBLSVdCMDEvUFBLSVdCMDEuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCpeKWuin6cpun45r8E
cmaxzwvYsNiZhC3iTS6sMIbUaSZZM7N0+UavCDZX04/9xlFUQNchlMezJDDlrM2EZyEZ2gDZDN65
22gWd8sJHyi5M8yruC42PHGePBdV8sY0EEB2dxuMsV+jQ1uBThyv1Oo8F38FjEuodYIlYuOWVxPY
sDiWNAJ0K0wq+EzxHgxuYO3Afg6pc4TlmHH9ZkWhNC6Lb1MzQjlp+a0FUWAljzZe/QeYbZEINsHx
swoQIO0/Uyg9ZUTK3K3mGWmWVdrPjYk3UJCfjOU3qLqIM5J17St7wd1o9Q9UDDJowUKgIZVXH6oY
obBGb7rBuyi/SEG5pNHGMIIFkzCCA3ugAwIBAgIQRmQhybpKpLtIEeJdHD7ivzANBgkqhkiG9w0B
AQUFADBcMRswGQYDVQQLExJDb3B5cmlnaHQgKGMpIDIwMDcxFjAUBgNVBAsTDVNwcmludCBOZXh0
ZWwxJTAjBgNVBAMTHFNwcmludCBOZXh0ZWwgUm9vdCBBdXRob3JpdHkwHhcNMDcwNTIyMTYyODI1
WhcNMjcwNTIyMTYzNTUyWjBcMRswGQYDVQQLExJDb3B5cmlnaHQgKGMpIDIwMDcxFjAUBgNVBAsT
DVNwcmludCBOZXh0ZWwxJTAjBgNVBAMTHFNwcmludCBOZXh0ZWwgUm9vdCBBdXRob3JpdHkwggIi
MA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQCXnrAnWxH9Pnu51vYiwtYe6Q6hcRrIZr84JcW+
9ze9zfu5pE3+PcsMzk6q5roX7LnwU/omHSUlKCMpnu2D78I5+VsA+U3in/2T0qN3VEdo2jvO8WZH
7KPwVGqYsbJBPk1cNYiRSKG2CRxsdWTDFpn2ri5/rsfWd7U8ZrNPMlFG17kVKJpb5E3e4d4PP7E9
/snxYnG0PCgT8kTe6SVTLIR0nlWZ6J+MvqGiWu21yd5BNFNFzfTitSgDkGtQZ17HbjmXCBkv3ULr
7jM19TAt5ZFjVewmvJPIKZT9/9+7KT6QaQVe/Ao7Xc9tFKgaEBwMCxLRPLHsxEi4oCgr/0N7wyIe
CoZropYeM3fxkFIRqa7hGSNQ0HLC51o/LpljxhrNjkoILnyL48mgevqdsER8jz7hlITqy3rHcyCM
HLmlt0YlKEYTTr9REXNnoUXNBkvJQPJgyl44xdaUzm3n8ydPtO4Cl0grRouQ4CJ3fQ2Hfi90zYhc
vs3hPI4YgccdUv9l2X++lRnazRME7FSGPd9RQh5eerR3bSWBukYo5KwgMGxyIU/hpraYHI38bbiA
PZmmpZ8vFk6iP2zVXHTkH+PqatzYGNdSkHLYQG5NM3GZlrE3khygDpfBuNo/VFtzIXAqNfWPJq7y
QM7AkGwbN5Y9uOalzh74O+Ej+nQUhVCuaZ46NQIDAQABo1EwTzALBgNVHQ8EBAMCAYYwDwYDVR0T
AQH/BAUwAwEB/zAdBgNVHQ4EFgQU6o073JNr96Z42jmfdFu4WxRjgs0wEAYJKwYBBAGCNxUBBAMC
AQAwDQYJKoZIhvcNAQEFBQADggIBAHIdGEzkUTJjPn1vyv/vL944OZ8hoVd6anmS1OMR+vRn9L5i
fdfmos332+Y+TGGB74lLeMp6lsP1tRd9TgMhB2DvcShCoEpyX8lNdiVczo4cKkZ5zSbaQzlK8Cfr
necuMFiFEk2Hi+T790l7DKSz4NbKfZGokZIx15grgrKlGK5ZQuTjfudKfguAXqFasFuxsLX4tcT1
2W2dcBjHdQxJy9LbwDJK39cgOuJlHj+VhwR07ZwS8by5JCm5JbOOrv40uyEWc1mnY6E8Jptq6iyf
wpItMr1gAJ1bVkaKjHXfyEqb0OPgu5sbne9mSIJQlwxiiHYHIB4OJXY5bczKpb2OAyyb9jmF/jC6
LMBhl7SmM81ftBiD1HQctqirilaUTlKNtIaZN7dZBFltnQyqSZE6GtQ+xOgojNGyceE/MI9asIFJ
jGVXYgUUX15Ri7OajEF+0E3DliTN2VZ2ECmdsuvGyz4AC+pWl8jZLPWUNsGfTgSR1S1+5iIRb6ia
yAkpKanTWNTPOPbTGbcetg5oXuKaPywcr6znRysmh1e+spAviXR/o5wv5NyApPix5sxV4urovGJ5
cVu07fw8UPMI0/25cJ4P+owxoRMRMWuEO7K1AF0GuCPr84v0d+CZLb3FqoK3DNJBLTvqGPA8VnAZ
ukt2co0Mcw8raOlCypTSGnYoWz0JMIIF2jCCA8KgAwIBAgIKYSGdxgAAAAAAAzANBgkqhkiG9w0B
AQUFADBcMRswGQYDVQQLExJDb3B5cmlnaHQgKGMpIDIwMDcxFjAUBgNVBAsTDVNwcmludCBOZXh0
ZWwxJTAjBgNVBAMTHFNwcmludCBOZXh0ZWwgUm9vdCBBdXRob3JpdHkwHhcNMDcwNTIyMTk1MjQw
WhcNMjAwNTIyMjAwMjQwWjBxMRswGQYDVQQLExJDb3B5cmlnaHQgKGMpIDIwMDcxFjAUBgNVBAsT
DVNwcmludCBOZXh0ZWwxOjA4BgNVBAMTMVNwcmludCBOZXh0ZWwgRW50ZXJwcmlzZSBJbnRlcm1l
ZGlhdGUgMSBBdXRob3JpdHkwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCp5IX+RYNn
IeUe+BkJ5VfMppHbxZlrSzd831LTblSkdTXQyi8+5A1p1ZObUSzm5mIW352SxStOtGvfSRTKcLg4
HBiZyArS+pQ8QvnXxdY70kzqfrN4+urXrHCol1y9LuUxfSShM0ZsFkC3DEtFj4zC0wi9I71Cb+8V
0rhVx6iTFCHo/KrDJJm/7twjmN39ZxaXZJFV+ofLEd+7wZijHuVlsKy6597etMor3CkeuwcMdp+1
lm/YAWZqmUY98LKKxKIet59OSDJPXP7L2nBJfwkkt6z4ibWQU1j4OJ1cZE5e/STDOXOR9by9FMh9
kDIAKyG/tGaHsxfrMY5miX8MywPlAgMBAAGjggGHMIIBgzAPBgNVHRMBAf8EBTADAQH/MB0GA1Ud
DgQWBBRRAcgiA5nZbiss2II5eNyrGXZEcTALBgNVHQ8EBAMCAYYwEAYJKwYBBAGCNxUBBAMCAQAw
GQYJKwYBBAGCNxQCBAweCgBTAHUAYgBDAEEwHwYDVR0jBBgwFoAU6o073JNr96Z42jmfdFu4WxRj
gs0wbgYDVR0fBGcwZTBjoGGgX4YwaHR0cDovL2NybC5jb3JwLnNwcmludC5jb20vUFBLSVdBMDEv
UFBLSVdBMDEuY3JshitodHRwOi8vY3JsLnNwcmludC5jb20vUFBLSVdBMDEvUFBLSVdBMDEuY3Js
MIGFBggrBgEFBQcBAQR5MHcwPAYIKwYBBQUHMAKGMGh0dHA6Ly9jcmwuY29ycC5zcHJpbnQuY29t
L1BQS0lXQTAxL1BQS0lXQTAxLmNydDA3BggrBgEFBQcwAoYraHR0cDovL2NybC5zcHJpbnQuY29t
L1BQS0lXQTAxL1BQS0lXQTAxLmNydDANBgkqhkiG9w0BAQUFAAOCAgEAPnhPbwWBkx8lJuBkvFQZ
+ndd5xT2WonpdzuqC1B7br4auN7RzovHVmC40RUrZfxf0mkNX9awG4naZaVjQzoMG0ijE8YEz/+X
JxOadLsXiatSjljJWSuRp4w6cc9yH2Vc3wkCjSYYhawD6kBVV/j10CWLJVfQ5gLw2OXa/k8jSxoZ
7eyPinEM4bkJOJTNkwPW99MiKwua/qFWeoshPy0w1KlT6mgEQM65mZfIwZ16/AiWcAg1QKgr6YYY
kzFu1M7cNEUhhohonAm/XPpsadSBIHKiQrW2rgWW56d5iDoUtoYXPaRZ7b/LaxqtuDrChaCYtYHA
iD8LwynwNqNG1L541S/nfAoyQcSmYgx2mo2b23ZsYI6LIEDeAOFtlLOZN/cUeSYACO60y75j1aj1
j9mbfSTA9VfOyayfgVOadeNHdse6zM8pRQ4AJt1yC7mNPkmkON9k+16IqOMXgwa+M4derUwRy+tt
QUOZe7iMtI7dgf8hsFteMSrXKkjNth0x2mEdGU8777WRCd4hFEKkGkJ2xTYGXDf8S6tmZM+OQ+Xt
gBvxZWMnehlUiycJtDdNazacLowHaRND8C7L6zcFlyeAkCOHoYxcUK7hm5FMfYrr2KZDFcakrjIy
AxYyTa/LlKv+spIBjxA+QOKJUYfrM8b+csCvy8vGhihP1EaxSv2J0xEwggarMIIFk6ADAgECAgo8
FVeJAAAAAZIPMA0GCSqGSIb3DQEBBQUAMHgxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJ
k/IsZAEZFgZzcHJpbnQxEjAQBgoJkiaJk/IsZAEZFgJhZDE1MDMGA1UEAxMsU3ByaW50IE5leHRl
bCBFbnRlcnByaXNlIElzc3VpbmcgMSBBdXRob3JpdHkwHhcNMDgwNTAxMTczNzE0WhcNMTEwNTAx
MTczNzE0WjCBzzETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBnNwcmludDES
MBAGCgmSJomT8ixkARkWAmFkMRUwEwYDVQQLEwxEb21haW4gVXNlcnMxEDAOBgNVBAsTB01hbmFn
ZWQxGzAZBgNVBAsTElN0YW5kYXJkLVRlY2huaWNhbDEbMBkGA1UEAxMSV2VzbGV5IEUgR2Vvcmdl
IElWMSkwJwYJKoZIhvcNAQkBFhpXZXNsZXkuRS5HZW9yZ2VAc3ByaW50LmNvbTCBnzANBgkqhkiG
9w0BAQEFAAOBjQAwgYkCgYEArxfUh9TugEcsXY4OefFQTrGuaTRenLcZg0KCxZlTY7P9wMRCYd8p
GJljwH1x4qn0Ejjyz+uX5UL8Biia13BSWRgiq7QYLKTZNKwEpBbeOf9lK/LrPsbFOgat/Zh/lPmx
YzxeikU42X3KhyVSCmWdQhmWRu5kfUzsejaGWH9AyuUCAwEAAaOCA2EwggNdMAsGA1UdDwQEAwIF
oDA2BgkqhkiG9w0BCQ8EKTAnMA0GCCqGSIb3DQMCAgE4MA0GCCqGSIb3DQMEAgE4MAcGBSsOAwIH
MB0GA1UdDgQWBBTFSbrzJuajBSX9B63Y9r2TlgbU5DA8BgkrBgEEAYI3FQcELzAtBiUrBgEEAYI3
FQiBkugshNficv2LB4Xs/liCno8icYbjvkqEsfZAAgFkAgECMB8GA1UdIwQYMBaAFAGPJVAshjSb
wX6QH9mINbU/rwuJMIIBXgYDVR0fBIIBVTCCAVEwggFNoIIBSaCCAUWGgeNsZGFwOi8vL0NOPVNw
cmludCUyME5leHRlbCUyMEVudGVycHJpc2UlMjBJc3N1aW5nJTIwMSUyMEF1dGhvcml0eSxDTj1Q
UEtJV0MwMSxDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049
Q29uZmlndXJhdGlvbixEQz1hZCxEQz1zcHJpbnQsREM9Y29tP2NlcnRpZmljYXRlUmV2b2NhdGlv
bkxpc3Q/YmFzZT9vYmplY3RDbGFzcz1jUkxEaXN0cmlidXRpb25Qb2ludIYraHR0cDovL2NybC5z
cHJpbnQuY29tL1BQS0lXQzAxL1BQS0lXQzAxLmNybIYwaHR0cDovL2NybC5jb3JwLnNwcmludC5j
b20vUFBLSVdDMDEvUFBLSVdDMDEuY3JsMIGFBggrBgEFBQcBAQR5MHcwNwYIKwYBBQUHMAKGK2h0
dHA6Ly9jcmwuc3ByaW50LmNvbS9QUEtJV0MwMS9QUEtJV0MwMS5jcnQwPAYIKwYBBQUHMAKGMGh0
dHA6Ly9jcmwuY29ycC5zcHJpbnQuY29tL1BQS0lXQzAxL1BQS0lXQzAxLmNydDApBgNVHSUEIjAg
BggrBgEFBQcDAgYIKwYBBQUHAwQGCisGAQQBgjcKAwQwNQYJKwYBBAGCNxUKBCgwJjAKBggrBgEF
BQcDAjAKBggrBgEFBQcDBDAMBgorBgEEAYI3CgMEMEwGA1UdEQRFMEOgJQYKKwYBBAGCNxQCA6AX
DBV3ZWcwMjIxQGFkLnNwcmludC5jb22BGldlc2xleS5FLkdlb3JnZUBzcHJpbnQuY29tMA0GCSqG
SIb3DQEBBQUAA4IBAQBYdUj2FTmOVS0X2fF+OYWXu9QoS6JWB8exD8kBPWVh28UilosoFwpVs2Ux
K+V9NE1SC4QXDfwcjyMMV6WfXfy1foT6YAOcLt1z91ALCbTPlr1mazbAnOL6AzoTnq5V+TjvJvdN
IYROS6PJC/YU5+w/NannnhC1zNFOtmxZZcrz50uRU8Q4mgITpxcnJXKUtKNaFTEhhtnP+hMVXYW0
eUyG7xjDTCyqsO5jcyI0IKJkNW1NXaKjHfmlAAiL5HVNl7cYL5uce6orHQQPMTSGRmTKCNjx7Yaz
EHAorZUGmCTuihdhPDq+tOhGrIDE4XuiDxj+OVU6JXM5nsiKTjU968o4MYIDITCCAx0CAQEwgYYw
eDETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBnNwcmludDESMBAGCgmSJomT
8ixkARkWAmFkMTUwMwYDVQQDEyxTcHJpbnQgTmV4dGVsIEVudGVycHJpc2UgSXNzdWluZyAxIEF1
dGhvcml0eQIKPBVXiQAAAAGSDzAJBgUrDgMCGgUAoIIB8DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN
AQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA0MDIxNzQ2NDRaMCMGCSqGSIb3DQEJBDEWBBQfA9uHZuF0
FjNi1CZL8s77wd4xvDBbBgkqhkiG9w0BCQ8xTjBMMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCGjCBlwYJKwYB
BAGCNxAEMYGJMIGGMHgxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZzcHJp
bnQxEjAQBgoJkiaJk/IsZAEZFgJhZDE1MDMGA1UEAxMsU3ByaW50IE5leHRlbCBFbnRlcnByaXNl
IElzc3VpbmcgMSBBdXRob3JpdHkCCjwVV4kAAAABkg8wgZkGCyqGSIb3DQEJEAILMYGJoIGGMHgx
EzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZzcHJpbnQxEjAQBgoJkiaJk/Is
ZAEZFgJhZDE1MDMGA1UEAxMsU3ByaW50IE5leHRlbCBFbnRlcnByaXNlIElzc3VpbmcgMSBBdXRo
b3JpdHkCCjwVV4kAAAABkg8wDQYJKoZIhvcNAQEBBQAEgYAe6L6mE3/sO5FK+TQUl4qXFQ/tCbLR
7t8ZMvxbCgL92oL+dAse015cPgN/OVgolZxqpH5qql65aP56c/PVDDgrBN0OqAnKFOBP2WRN/ITb
T6LJfqQIkw1KyB/akRSEBWPo6cif1p4KEdSCT6X338zP2krNFjj/74p3RgxpTFFjGgAAAAAAAA==

------=_NextPart_000_025E_01CBF13C.671F2FE0--

From brian.e.carpenter@gmail.com  Mon Apr  4 00:40:59 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@core3.amsl.com
Delivered-To: renum@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E3483A6931 for <renum@core3.amsl.com>; Mon,  4 Apr 2011 00:40:59 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boklekEG5jXm for <renum@core3.amsl.com>; Mon,  4 Apr 2011 00:40:53 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 09EBE3A6922 for <renum@ietf.org>; Mon,  4 Apr 2011 00:40:52 -0700 (PDT)
Received: by wyb29 with SMTP id 29so4985459wyb.31 for <renum@ietf.org>; Mon, 04 Apr 2011 00:42:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=aG7B3dWV+hq4zmJpP/lxLa37zQkvhS7qwagvYvxzs8I=; b=JvERjBNiCquIMXhj7MskZVYd+S0mrRGtwL0nzXHxiej5HeUU8I5VsX/1O+ZzGPVEKp r3VeiHXrXuoSDSYqhXL3e1CAS55iJTtxpW3jhcEqbtgvcUoM9VISOMIFWn7aCqtp12Io ic8XP4zve3ASksnUkVkbjTSVPPmfwNPK+asbc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=jGmhQFABRqCy+OEXjInky7kUlbxr7ExnJg5Tx7fCEnaR1494lWw3oCw90Rp0RxxblQ 7dezbo1dHCNOdN9zN0uVEU2x7S58SZRr//wSJddeCR2kEP8nAScqz+gJqZd7AaUkuRvS IylRVMlGqHGVVEYK2pWOUPLyeo6EqlzS4Jq90=
Received: by 10.216.46.135 with SMTP id r7mr3610994web.21.1301902954818; Mon, 04 Apr 2011 00:42:34 -0700 (PDT)
Received: from [192.168.1.65] (host86-162-222-107.range86-162.btcentralplus.com [86.162.222.107]) by mx.google.com with ESMTPS id p5sm2747741wbg.62.2011.04.04.00.42.33 (version=SSLv3 cipher=OTHER); Mon, 04 Apr 2011 00:42:33 -0700 (PDT)
Message-ID: <4D997663.2060505@gmail.com>
Date: Mon, 04 Apr 2011 19:42:27 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "George, Wes E [NTK]" <Wesley.E.George@sprint.com>
References: <4D3FECA9.6060109@huawei.com> <54E900DC635DAB4DB7A6D799B3C4CD8E10C6AD2E@PLSWM12A.ad.sprint.com>
In-Reply-To: <54E900DC635DAB4DB7A6D799B3C4CD8E10C6AD2E@PLSWM12A.ad.sprint.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Sheng Jiang <shengjiang@huawei.com>, "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 04 Apr 2011 07:40:59 -0000

Thanks Wes. Yes, we clearly need a 'divide and conquer' approach.

We definitely need to separate renumbering avoidance (both the goal
and potential solutions) from the problem of how to renumber when
it's unavoidable.

Also we need to separate the target networks into major classes
such as managed vs unmanaged.

Regards
   Brian

On 2011-04-04 12:11, George, Wes E [NTK] wrote:
> Wanted to get some of my comments from the mic out to the list-
> 
> I think that there are a number of places where we need to break up the problem space in order to make it more manageable, both in
> terms of work that this group might take on vs work that is already partially done/belongs in existing groups, etc. Please add to
> the list and provide comments...
> 
> Questions:
> Do we care about supporting hitless renumbering (that is, some form of make-before-break that allows end hosts to migrate their
> active sessions)?
>  - I say nice to have, if at all, definitely not a primary goal
> Should we be considering an encapsulation (like IRON) or Locator ID split implementation within scope to solve the renumbering
> problem?
>  - I say that we should be concentrating on renumbering problems that we can solve independent of any improved support in the
> network infrastructure for mobility and route scaling, but others may disagree.
> 
> Different problem spaces:
> - BCP on how to limit the impact of renumbering when it is required - especially important as IPv6 rolls out and people are doing
> their once-in-a-blue-moon numbering plans, plus code work to support it
> - Device config:
> *on-box CLI and the places where it supports/requires IP address literals - places we can recommend that vendors support
> parameterization either through FQDNs or external files that allow you to change an address in multiple places in the config at once
> *a centralized management infrastructure that abstracts local config  from addressing
> *Dynamically numbered devices/networks vs static
> 
> Thanks, 
> Wes George
> 
> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of Sheng Jiang
> Sent: Wednesday, January 26, 2011 4:43 AM
> To: renum@ietf.org
> Subject: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00
> 
> 
> A new version of I-D, draft-jiang-ipv6-site-renum-guideline-00.txt has been successfully submitted by Sheng Jiang and posted to the
> IETF repository.
> 
> Filename:	 draft-jiang-ipv6-site-renum-guideline
> Revision:	 00
> Title:		 IPv6 Site Renumbering Guidelines and Further Works
> Creation_date:	 2011-01-26
> WG ID:		 Independent Submission
> Number_of_pages: 13
> 
> Abstract:
> This document analyzes the existing issues for IPv6 site renumbering.
> It also analyzes the possible directions to solve these issues and gives recommendations. This document only takes the perspective
> of network and network protocols. Renumbering in IPv4 networks, in the dual-stack network or in the IPv4/IPv6 transition networks
> are out of scope.
> 
> This document only takes the perspective of network and network protocols. According to the different stages, these issues are
> described in three categories: considerations during network design, considerations for routine network management, and
> considerations during renumbering operation. Recommended solutions or strategies are also described. Issues that still remain
> unsolvable are listed as the fourth category.
> 
> Although we list a few non-network issues in this document, we consider them as issues that ISPs or network providers cannot affect.
> So, these issues are considered to be unsolvable and not explore further in these document, though they may be solved by OS
> implementations or application implementations.
> 
> We summary the requests that need to extend current protocols as further works at the end of this document.
>  
> 
> 
> 
> The IETF Secretariat.
> 
> 
> 
> _______________________________________________
> 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 Wesley.E.George@sprint.com  Mon Apr  4 07:22:26 2011
Return-Path: <Wesley.E.George@sprint.com>
X-Original-To: renum@core3.amsl.com
Delivered-To: renum@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D156D28C126 for <renum@core3.amsl.com>; Mon,  4 Apr 2011 07:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.123
X-Spam-Level: 
X-Spam-Status: No, score=-4.123 tagged_above=-999 required=5 tests=[AWL=-0.524, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FK97W6CgRcq0 for <renum@core3.amsl.com>; Mon,  4 Apr 2011 07:22:24 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1outboundpool.messaging.microsoft.com [216.32.181.186]) by core3.amsl.com (Postfix) with ESMTP id F22893A69F0 for <renum@ietf.org>; Mon,  4 Apr 2011 07:22:23 -0700 (PDT)
Received: from mail80-ch1-R.bigfish.com (216.32.181.170) by CH1EHSOBE015.bigfish.com (10.43.70.65) with Microsoft SMTP Server id 14.1.225.8; Mon, 4 Apr 2011 14:24:05 +0000
Received: from mail80-ch1 (localhost.localdomain [127.0.0.1])	by mail80-ch1-R.bigfish.com (Postfix) with ESMTP id B96191A181F1; Mon,  4 Apr 2011 14:24:04 +0000 (UTC)
X-SpamScore: -47
X-BigFish: VS-47(zf7Iz936eK9371P542N1418M4015Lzz1202hzz1033IL8275dhz2fh2a8h668h839h34h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: KIP:(null); UIP:(null); IPVD:NLI; H:plsasdm1.corp.sprint.com; RD:smtpls1.sprint.com; EFVD:NLI
Received: from mail80-ch1 (localhost.localdomain [127.0.0.1]) by mail80-ch1 (MessageSwitch) id 1301927044177995_31466; Mon,  4 Apr 2011 14:24:04 +0000 (UTC)
Received: from CH1EHSMHS015.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.244])	by mail80-ch1.bigfish.com (Postfix) with ESMTP id 27D7C23004F;	Mon,  4 Apr 2011 14:24:04 +0000 (UTC)
Received: from plsasdm1.corp.sprint.com (144.230.168.25) by CH1EHSMHS015.bigfish.com (10.43.70.15) with Microsoft SMTP Server (TLS) id 14.1.225.8; Mon, 4 Apr 2011 14:24:01 +0000
Received: from PDAWEH01.ad.sprint.com (PDAWEH01.corp.sprint.com [144.226.110.69])	by plsasdm1.corp.sprint.com (Sentrion-MTA-4.0.5/Sentrion-MTA-4.0.5) with ESMTP id p34ENghY025177 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 4 Apr 2011 09:24:00 -0500
Received: from PLSWM12A.ad.sprint.com ([fe80::dd81:e8a1:cd6b:78f]) by PDAWEH01.ad.sprint.com ([2002:90e2:6e45::90e2:6e45]) with mapi id 14.01.0270.001; Mon, 4 Apr 2011 09:23:50 -0500
From: "George, Wes E [NTK]" <Wesley.E.George@sprint.com>
To: Sheng Jiang <shengjiang@huawei.com>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00
Thread-Index: AQHLvT13deLdjBNuyUy7p0vAJHcYwZRLKeAAgAMCkUA=
Date: Mon, 4 Apr 2011 14:23:49 +0000
Message-ID: <54E900DC635DAB4DB7A6D799B3C4CD8E10C6B190@PLSWM12A.ad.sprint.com>
References: <4D3FECA9.6060109@huawei.com> <54E900DC635DAB4DB7A6D799B3C4CD8E10C6AD2E@PLSWM12A.ad.sprint.com>
In-Reply-To: <54E900DC635DAB4DB7A6D799B3C4CD8E10C6AD2E@PLSWM12A.ad.sprint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.229.76.112]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0076_01CBF2B2.6744BE50"
MIME-Version: 1.0
X-OriginatorOrg: sprint.com
Subject: Re: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 04 Apr 2011 14:22:26 -0000

------=_NextPart_000_0076_01CBF2B2.6744BE50
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Got some offlist comments that I should clarify what I mean by hitless renumbering in the first question below.

This isn't referring to what we have today, where we can take a node and provide one or more additional IPv6 addresses to it so that
you can use this as a way to make renumbering less painful. Ultimately, you still have some point where traffic has to stop flowing
from the old address and start flowing from the new one, even if it's pretty short.
What I'm specifically referring to is yet-to-be implemented machinery to let a host take that new address and signal to the other
side that it's going to be moving to a new address so that active traffic flows can be migrated without being reset. Since this is a
lot more complicated, that's what I'm referring to as nice-to-have. 

Thanks, 
Wes George

-----Original Message-----
From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of George, Wes E [NTK]
Sent: Sunday, April 03, 2011 8:11 PM
To: Sheng Jiang; renum@ietf.org
Subject: Re: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00

Wanted to get some of my comments from the mic out to the list-

I think that there are a number of places where we need to break up the problem space in order to make it more manageable, both in
terms of work that this group might take on vs work that is already partially done/belongs in existing groups, etc. Please add to
the list and provide comments...

Questions:
Do we care about supporting hitless renumbering (that is, some form of make-before-break that allows end hosts to migrate their
active sessions)?
 - I say nice to have, if at all, definitely not a primary goal Should we be considering an encapsulation (like IRON) or Locator ID
split implementation within scope to solve the renumbering problem?
 - I say that we should be concentrating on renumbering problems that we can solve independent of any improved support in the
network infrastructure for mobility and route scaling, but others may disagree.

Different problem spaces:
- BCP on how to limit the impact of renumbering when it is required - especially important as IPv6 rolls out and people are doing
their once-in-a-blue-moon numbering plans, plus code work to support it
- Device config:
*on-box CLI and the places where it supports/requires IP address literals - places we can recommend that vendors support
parameterization either through FQDNs or external files that allow you to change an address in multiple places in the config at once
*a centralized management infrastructure that abstracts local config  from addressing *Dynamically numbered devices/networks vs
static

Thanks,
Wes George

-----Original Message-----
From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of Sheng Jiang
Sent: Wednesday, January 26, 2011 4:43 AM
To: renum@ietf.org
Subject: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00


A new version of I-D, draft-jiang-ipv6-site-renum-guideline-00.txt has been successfully submitted by Sheng Jiang and posted to the
IETF repository.

Filename:	 draft-jiang-ipv6-site-renum-guideline
Revision:	 00
Title:		 IPv6 Site Renumbering Guidelines and Further Works
Creation_date:	 2011-01-26
WG ID:		 Independent Submission
Number_of_pages: 13

Abstract:
This document analyzes the existing issues for IPv6 site renumbering.
It also analyzes the possible directions to solve these issues and gives recommendations. This document only takes the perspective
of network and network protocols. Renumbering in IPv4 networks, in the dual-stack network or in the IPv4/IPv6 transition networks
are out of scope.

This document only takes the perspective of network and network protocols. According to the different stages, these issues are
described in three categories: considerations during network design, considerations for routine network management, and
considerations during renumbering operation. Recommended solutions or strategies are also described. Issues that still remain
unsolvable are listed as the fourth category.

Although we list a few non-network issues in this document, we consider them as issues that ISPs or network providers cannot affect.
So, these issues are considered to be unsolvable and not explore further in these document, though they may be solved by OS
implementations or application implementations.

We summary the requests that need to extend current protocols as further works at the end of this document.
 



The IETF Secretariat.



_______________________________________________
renum mailing list
renum@ietf.org
https://www.ietf.org/mailman/listinfo/renum


------=_NextPart_000_0076_01CBF2B2.6744BE50
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIXHjCCBPYw
ggPeoAMCAQICChTCbVgAAAAAAAUwDQYJKoZIhvcNAQEFBQAwcTEbMBkGA1UECxMSQ29weXJpZ2h0
IChjKSAyMDA3MRYwFAYDVQQLEw1TcHJpbnQgTmV4dGVsMTowOAYDVQQDEzFTcHJpbnQgTmV4dGVs
IEVudGVycHJpc2UgSW50ZXJtZWRpYXRlIDEgQXV0aG9yaXR5MB4XDTA3MDcxNzE5NDIxNloXDTE1
MDcxNzE5NTIxNloweDETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBnNwcmlu
dDESMBAGCgmSJomT8ixkARkWAmFkMTUwMwYDVQQDEyxTcHJpbnQgTmV4dGVsIEVudGVycHJpc2Ug
SXNzdWluZyAxIEF1dGhvcml0eTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL95aoB4
LLMFIOaq8WTtWyNCb7m5xoKdM6oJKXsCx8k8GATPtiX7VPXKMjRNv+jMZXKF9U6RA4wjSKiKMOYg
48ioSpanTxp+7p6+00Nr/eEtjsY+21rDQbANaqFGfkRFv4m59jM53j+mEXIDybTttcQN/CdSvI0d
XOD3KxQTPaG+h9uqZmkrdlk/rwvGbKhqmsl2BApItCDlUWt4rbv0GYQR4GP0w6c7e5prJBh89PEq
y+NDtv14YqYl5zOBST4IoHX77uS9gZXqglhtpYKDfESgrgcMldsfKyjrOwiRlT7o8ez1iOyCULkp
RcGLSe3wxZxx82bPEYjSWJf56V21FV0CAwEAAaOCAYcwggGDMA8GA1UdEwEB/wQFMAMBAf8wHQYD
VR0OBBYEFAGPJVAshjSbwX6QH9mINbU/rwuJMAsGA1UdDwQEAwIBhjAQBgkrBgEEAYI3FQEEAwIB
ADAZBgkrBgEEAYI3FAIEDB4KAFMAdQBiAEMAQTAfBgNVHSMEGDAWgBRRAcgiA5nZbiss2II5eNyr
GXZEcTBuBgNVHR8EZzBlMGOgYaBfhjBodHRwOi8vY3JsLmNvcnAuc3ByaW50LmNvbS9QUEtJV0Iw
MS9QUEtJV0IwMS5jcmyGK2h0dHA6Ly9jcmwuc3ByaW50LmNvbS9QUEtJV0IwMS9QUEtJV0IwMS5j
cmwwgYUGCCsGAQUFBwEBBHkwdzA8BggrBgEFBQcwAoYwaHR0cDovL2NybC5jb3JwLnNwcmludC5j
b20vUFBLSVdCMDEvUFBLSVdCMDEuY3J0MDcGCCsGAQUFBzAChitodHRwOi8vY3JsLnNwcmludC5j
b20vUFBLSVdCMDEvUFBLSVdCMDEuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCpeKWuin6cpun45r8E
cmaxzwvYsNiZhC3iTS6sMIbUaSZZM7N0+UavCDZX04/9xlFUQNchlMezJDDlrM2EZyEZ2gDZDN65
22gWd8sJHyi5M8yruC42PHGePBdV8sY0EEB2dxuMsV+jQ1uBThyv1Oo8F38FjEuodYIlYuOWVxPY
sDiWNAJ0K0wq+EzxHgxuYO3Afg6pc4TlmHH9ZkWhNC6Lb1MzQjlp+a0FUWAljzZe/QeYbZEINsHx
swoQIO0/Uyg9ZUTK3K3mGWmWVdrPjYk3UJCfjOU3qLqIM5J17St7wd1o9Q9UDDJowUKgIZVXH6oY
obBGb7rBuyi/SEG5pNHGMIIFkzCCA3ugAwIBAgIQRmQhybpKpLtIEeJdHD7ivzANBgkqhkiG9w0B
AQUFADBcMRswGQYDVQQLExJDb3B5cmlnaHQgKGMpIDIwMDcxFjAUBgNVBAsTDVNwcmludCBOZXh0
ZWwxJTAjBgNVBAMTHFNwcmludCBOZXh0ZWwgUm9vdCBBdXRob3JpdHkwHhcNMDcwNTIyMTYyODI1
WhcNMjcwNTIyMTYzNTUyWjBcMRswGQYDVQQLExJDb3B5cmlnaHQgKGMpIDIwMDcxFjAUBgNVBAsT
DVNwcmludCBOZXh0ZWwxJTAjBgNVBAMTHFNwcmludCBOZXh0ZWwgUm9vdCBBdXRob3JpdHkwggIi
MA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQCXnrAnWxH9Pnu51vYiwtYe6Q6hcRrIZr84JcW+
9ze9zfu5pE3+PcsMzk6q5roX7LnwU/omHSUlKCMpnu2D78I5+VsA+U3in/2T0qN3VEdo2jvO8WZH
7KPwVGqYsbJBPk1cNYiRSKG2CRxsdWTDFpn2ri5/rsfWd7U8ZrNPMlFG17kVKJpb5E3e4d4PP7E9
/snxYnG0PCgT8kTe6SVTLIR0nlWZ6J+MvqGiWu21yd5BNFNFzfTitSgDkGtQZ17HbjmXCBkv3ULr
7jM19TAt5ZFjVewmvJPIKZT9/9+7KT6QaQVe/Ao7Xc9tFKgaEBwMCxLRPLHsxEi4oCgr/0N7wyIe
CoZropYeM3fxkFIRqa7hGSNQ0HLC51o/LpljxhrNjkoILnyL48mgevqdsER8jz7hlITqy3rHcyCM
HLmlt0YlKEYTTr9REXNnoUXNBkvJQPJgyl44xdaUzm3n8ydPtO4Cl0grRouQ4CJ3fQ2Hfi90zYhc
vs3hPI4YgccdUv9l2X++lRnazRME7FSGPd9RQh5eerR3bSWBukYo5KwgMGxyIU/hpraYHI38bbiA
PZmmpZ8vFk6iP2zVXHTkH+PqatzYGNdSkHLYQG5NM3GZlrE3khygDpfBuNo/VFtzIXAqNfWPJq7y
QM7AkGwbN5Y9uOalzh74O+Ej+nQUhVCuaZ46NQIDAQABo1EwTzALBgNVHQ8EBAMCAYYwDwYDVR0T
AQH/BAUwAwEB/zAdBgNVHQ4EFgQU6o073JNr96Z42jmfdFu4WxRjgs0wEAYJKwYBBAGCNxUBBAMC
AQAwDQYJKoZIhvcNAQEFBQADggIBAHIdGEzkUTJjPn1vyv/vL944OZ8hoVd6anmS1OMR+vRn9L5i
fdfmos332+Y+TGGB74lLeMp6lsP1tRd9TgMhB2DvcShCoEpyX8lNdiVczo4cKkZ5zSbaQzlK8Cfr
necuMFiFEk2Hi+T790l7DKSz4NbKfZGokZIx15grgrKlGK5ZQuTjfudKfguAXqFasFuxsLX4tcT1
2W2dcBjHdQxJy9LbwDJK39cgOuJlHj+VhwR07ZwS8by5JCm5JbOOrv40uyEWc1mnY6E8Jptq6iyf
wpItMr1gAJ1bVkaKjHXfyEqb0OPgu5sbne9mSIJQlwxiiHYHIB4OJXY5bczKpb2OAyyb9jmF/jC6
LMBhl7SmM81ftBiD1HQctqirilaUTlKNtIaZN7dZBFltnQyqSZE6GtQ+xOgojNGyceE/MI9asIFJ
jGVXYgUUX15Ri7OajEF+0E3DliTN2VZ2ECmdsuvGyz4AC+pWl8jZLPWUNsGfTgSR1S1+5iIRb6ia
yAkpKanTWNTPOPbTGbcetg5oXuKaPywcr6znRysmh1e+spAviXR/o5wv5NyApPix5sxV4urovGJ5
cVu07fw8UPMI0/25cJ4P+owxoRMRMWuEO7K1AF0GuCPr84v0d+CZLb3FqoK3DNJBLTvqGPA8VnAZ
ukt2co0Mcw8raOlCypTSGnYoWz0JMIIF2jCCA8KgAwIBAgIKYSGdxgAAAAAAAzANBgkqhkiG9w0B
AQUFADBcMRswGQYDVQQLExJDb3B5cmlnaHQgKGMpIDIwMDcxFjAUBgNVBAsTDVNwcmludCBOZXh0
ZWwxJTAjBgNVBAMTHFNwcmludCBOZXh0ZWwgUm9vdCBBdXRob3JpdHkwHhcNMDcwNTIyMTk1MjQw
WhcNMjAwNTIyMjAwMjQwWjBxMRswGQYDVQQLExJDb3B5cmlnaHQgKGMpIDIwMDcxFjAUBgNVBAsT
DVNwcmludCBOZXh0ZWwxOjA4BgNVBAMTMVNwcmludCBOZXh0ZWwgRW50ZXJwcmlzZSBJbnRlcm1l
ZGlhdGUgMSBBdXRob3JpdHkwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCp5IX+RYNn
IeUe+BkJ5VfMppHbxZlrSzd831LTblSkdTXQyi8+5A1p1ZObUSzm5mIW352SxStOtGvfSRTKcLg4
HBiZyArS+pQ8QvnXxdY70kzqfrN4+urXrHCol1y9LuUxfSShM0ZsFkC3DEtFj4zC0wi9I71Cb+8V
0rhVx6iTFCHo/KrDJJm/7twjmN39ZxaXZJFV+ofLEd+7wZijHuVlsKy6597etMor3CkeuwcMdp+1
lm/YAWZqmUY98LKKxKIet59OSDJPXP7L2nBJfwkkt6z4ibWQU1j4OJ1cZE5e/STDOXOR9by9FMh9
kDIAKyG/tGaHsxfrMY5miX8MywPlAgMBAAGjggGHMIIBgzAPBgNVHRMBAf8EBTADAQH/MB0GA1Ud
DgQWBBRRAcgiA5nZbiss2II5eNyrGXZEcTALBgNVHQ8EBAMCAYYwEAYJKwYBBAGCNxUBBAMCAQAw
GQYJKwYBBAGCNxQCBAweCgBTAHUAYgBDAEEwHwYDVR0jBBgwFoAU6o073JNr96Z42jmfdFu4WxRj
gs0wbgYDVR0fBGcwZTBjoGGgX4YwaHR0cDovL2NybC5jb3JwLnNwcmludC5jb20vUFBLSVdBMDEv
UFBLSVdBMDEuY3JshitodHRwOi8vY3JsLnNwcmludC5jb20vUFBLSVdBMDEvUFBLSVdBMDEuY3Js
MIGFBggrBgEFBQcBAQR5MHcwPAYIKwYBBQUHMAKGMGh0dHA6Ly9jcmwuY29ycC5zcHJpbnQuY29t
L1BQS0lXQTAxL1BQS0lXQTAxLmNydDA3BggrBgEFBQcwAoYraHR0cDovL2NybC5zcHJpbnQuY29t
L1BQS0lXQTAxL1BQS0lXQTAxLmNydDANBgkqhkiG9w0BAQUFAAOCAgEAPnhPbwWBkx8lJuBkvFQZ
+ndd5xT2WonpdzuqC1B7br4auN7RzovHVmC40RUrZfxf0mkNX9awG4naZaVjQzoMG0ijE8YEz/+X
JxOadLsXiatSjljJWSuRp4w6cc9yH2Vc3wkCjSYYhawD6kBVV/j10CWLJVfQ5gLw2OXa/k8jSxoZ
7eyPinEM4bkJOJTNkwPW99MiKwua/qFWeoshPy0w1KlT6mgEQM65mZfIwZ16/AiWcAg1QKgr6YYY
kzFu1M7cNEUhhohonAm/XPpsadSBIHKiQrW2rgWW56d5iDoUtoYXPaRZ7b/LaxqtuDrChaCYtYHA
iD8LwynwNqNG1L541S/nfAoyQcSmYgx2mo2b23ZsYI6LIEDeAOFtlLOZN/cUeSYACO60y75j1aj1
j9mbfSTA9VfOyayfgVOadeNHdse6zM8pRQ4AJt1yC7mNPkmkON9k+16IqOMXgwa+M4derUwRy+tt
QUOZe7iMtI7dgf8hsFteMSrXKkjNth0x2mEdGU8777WRCd4hFEKkGkJ2xTYGXDf8S6tmZM+OQ+Xt
gBvxZWMnehlUiycJtDdNazacLowHaRND8C7L6zcFlyeAkCOHoYxcUK7hm5FMfYrr2KZDFcakrjIy
AxYyTa/LlKv+spIBjxA+QOKJUYfrM8b+csCvy8vGhihP1EaxSv2J0xEwggarMIIFk6ADAgECAgo8
FVeJAAAAAZIPMA0GCSqGSIb3DQEBBQUAMHgxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJ
k/IsZAEZFgZzcHJpbnQxEjAQBgoJkiaJk/IsZAEZFgJhZDE1MDMGA1UEAxMsU3ByaW50IE5leHRl
bCBFbnRlcnByaXNlIElzc3VpbmcgMSBBdXRob3JpdHkwHhcNMDgwNTAxMTczNzE0WhcNMTEwNTAx
MTczNzE0WjCBzzETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBnNwcmludDES
MBAGCgmSJomT8ixkARkWAmFkMRUwEwYDVQQLEwxEb21haW4gVXNlcnMxEDAOBgNVBAsTB01hbmFn
ZWQxGzAZBgNVBAsTElN0YW5kYXJkLVRlY2huaWNhbDEbMBkGA1UEAxMSV2VzbGV5IEUgR2Vvcmdl
IElWMSkwJwYJKoZIhvcNAQkBFhpXZXNsZXkuRS5HZW9yZ2VAc3ByaW50LmNvbTCBnzANBgkqhkiG
9w0BAQEFAAOBjQAwgYkCgYEArxfUh9TugEcsXY4OefFQTrGuaTRenLcZg0KCxZlTY7P9wMRCYd8p
GJljwH1x4qn0Ejjyz+uX5UL8Biia13BSWRgiq7QYLKTZNKwEpBbeOf9lK/LrPsbFOgat/Zh/lPmx
YzxeikU42X3KhyVSCmWdQhmWRu5kfUzsejaGWH9AyuUCAwEAAaOCA2EwggNdMAsGA1UdDwQEAwIF
oDA2BgkqhkiG9w0BCQ8EKTAnMA0GCCqGSIb3DQMCAgE4MA0GCCqGSIb3DQMEAgE4MAcGBSsOAwIH
MB0GA1UdDgQWBBTFSbrzJuajBSX9B63Y9r2TlgbU5DA8BgkrBgEEAYI3FQcELzAtBiUrBgEEAYI3
FQiBkugshNficv2LB4Xs/liCno8icYbjvkqEsfZAAgFkAgECMB8GA1UdIwQYMBaAFAGPJVAshjSb
wX6QH9mINbU/rwuJMIIBXgYDVR0fBIIBVTCCAVEwggFNoIIBSaCCAUWGgeNsZGFwOi8vL0NOPVNw
cmludCUyME5leHRlbCUyMEVudGVycHJpc2UlMjBJc3N1aW5nJTIwMSUyMEF1dGhvcml0eSxDTj1Q
UEtJV0MwMSxDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049
Q29uZmlndXJhdGlvbixEQz1hZCxEQz1zcHJpbnQsREM9Y29tP2NlcnRpZmljYXRlUmV2b2NhdGlv
bkxpc3Q/YmFzZT9vYmplY3RDbGFzcz1jUkxEaXN0cmlidXRpb25Qb2ludIYraHR0cDovL2NybC5z
cHJpbnQuY29tL1BQS0lXQzAxL1BQS0lXQzAxLmNybIYwaHR0cDovL2NybC5jb3JwLnNwcmludC5j
b20vUFBLSVdDMDEvUFBLSVdDMDEuY3JsMIGFBggrBgEFBQcBAQR5MHcwNwYIKwYBBQUHMAKGK2h0
dHA6Ly9jcmwuc3ByaW50LmNvbS9QUEtJV0MwMS9QUEtJV0MwMS5jcnQwPAYIKwYBBQUHMAKGMGh0
dHA6Ly9jcmwuY29ycC5zcHJpbnQuY29tL1BQS0lXQzAxL1BQS0lXQzAxLmNydDApBgNVHSUEIjAg
BggrBgEFBQcDAgYIKwYBBQUHAwQGCisGAQQBgjcKAwQwNQYJKwYBBAGCNxUKBCgwJjAKBggrBgEF
BQcDAjAKBggrBgEFBQcDBDAMBgorBgEEAYI3CgMEMEwGA1UdEQRFMEOgJQYKKwYBBAGCNxQCA6AX
DBV3ZWcwMjIxQGFkLnNwcmludC5jb22BGldlc2xleS5FLkdlb3JnZUBzcHJpbnQuY29tMA0GCSqG
SIb3DQEBBQUAA4IBAQBYdUj2FTmOVS0X2fF+OYWXu9QoS6JWB8exD8kBPWVh28UilosoFwpVs2Ux
K+V9NE1SC4QXDfwcjyMMV6WfXfy1foT6YAOcLt1z91ALCbTPlr1mazbAnOL6AzoTnq5V+TjvJvdN
IYROS6PJC/YU5+w/NannnhC1zNFOtmxZZcrz50uRU8Q4mgITpxcnJXKUtKNaFTEhhtnP+hMVXYW0
eUyG7xjDTCyqsO5jcyI0IKJkNW1NXaKjHfmlAAiL5HVNl7cYL5uce6orHQQPMTSGRmTKCNjx7Yaz
EHAorZUGmCTuihdhPDq+tOhGrIDE4XuiDxj+OVU6JXM5nsiKTjU968o4MYIDITCCAx0CAQEwgYYw
eDETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBnNwcmludDESMBAGCgmSJomT
8ixkARkWAmFkMTUwMwYDVQQDEyxTcHJpbnQgTmV4dGVsIEVudGVycHJpc2UgSXNzdWluZyAxIEF1
dGhvcml0eQIKPBVXiQAAAAGSDzAJBgUrDgMCGgUAoIIB8DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN
AQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA0MDQxNDIzNTZaMCMGCSqGSIb3DQEJBDEWBBQMfEypcWGd
GpjfQ+7CHhb6aRWdCDBbBgkqhkiG9w0BCQ8xTjBMMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCGjCBlwYJKwYB
BAGCNxAEMYGJMIGGMHgxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZzcHJp
bnQxEjAQBgoJkiaJk/IsZAEZFgJhZDE1MDMGA1UEAxMsU3ByaW50IE5leHRlbCBFbnRlcnByaXNl
IElzc3VpbmcgMSBBdXRob3JpdHkCCjwVV4kAAAABkg8wgZkGCyqGSIb3DQEJEAILMYGJoIGGMHgx
EzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZzcHJpbnQxEjAQBgoJkiaJk/Is
ZAEZFgJhZDE1MDMGA1UEAxMsU3ByaW50IE5leHRlbCBFbnRlcnByaXNlIElzc3VpbmcgMSBBdXRo
b3JpdHkCCjwVV4kAAAABkg8wDQYJKoZIhvcNAQEBBQAEgYCDMvi/A5ncXrLXTX2YSfRsJgDmDERq
tTqV6A+qzijkfrwW0SkJOBVVLyivCnVE75piDwlfYhzjdbpqv0QHRKThDtISs0QcAkipxPmh7eCh
EsN8n1hEwr3LiGSHYt5Dz4Fa929VJ880ZIWujyUT5wjOXEhG8NuQ90Sr4j3r+Oo7mgAAAAAAAA==

------=_NextPart_000_0076_01CBF2B2.6744BE50--

From teco@inf-net.nl  Mon Apr  4 22:16:03 2011
Return-Path: <teco@inf-net.nl>
X-Original-To: renum@core3.amsl.com
Delivered-To: renum@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49E9E3A68A7 for <renum@core3.amsl.com>; Mon,  4 Apr 2011 22:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.028
X-Spam-Level: 
X-Spam-Status: No, score=-3.028 tagged_above=-999 required=5 tests=[AWL=-0.421, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eA6EFunFSfRJ for <renum@core3.amsl.com>; Mon,  4 Apr 2011 22:16:02 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id D5D353A688A for <renum@ietf.org>; Mon,  4 Apr 2011 22:16:01 -0700 (PDT)
Received: by eye13 with SMTP id 13so6890eye.31 for <renum@ietf.org>; Mon, 04 Apr 2011 22:17:44 -0700 (PDT)
Received: by 10.213.3.80 with SMTP id 16mr27058ebm.47.1301980662100; Mon, 04 Apr 2011 22:17:42 -0700 (PDT)
Received: from [192.168.2.187] (ip56530916.direct-adsl.nl [86.83.9.22]) by mx.google.com with ESMTPS id q53sm3740165eeh.11.2011.04.04.22.17.39 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Apr 2011 22:17:40 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <54E900DC635DAB4DB7A6D799B3C4CD8E10C6B190@PLSWM12A.ad.sprint.com>
Date: Mon, 4 Apr 2011 16:50:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <01D88F72-77FE-49F0-86A5-46945059B96A@inf-net.nl>
References: <4D3FECA9.6060109@huawei.com> <54E900DC635DAB4DB7A6D799B3C4CD8E10C6AD2E@PLSWM12A.ad.sprint.com> <54E900DC635DAB4DB7A6D799B3C4CD8E10C6B190@PLSWM12A.ad.sprint.com>
To: "George, Wes E [NTK]" <Wesley.E.George@sprint.com>
X-Mailer: Apple Mail (2.1082)
Cc: Sheng Jiang <shengjiang@huawei.com>, "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2011 05:16:03 -0000

Wes,

I think there are lots of pieces of the puzzle for smooth, hitless =
renumbering. We can have the ambition combine those and complete the =
picture. I think this is more than a nice-to-have for unmanaged sites, =
although it may not work from day one, with basic IPv6 nodes.=20

Teco=20

Op 4 apr 2011, om 16:23 heeft George, Wes E [NTK] het volgende =
geschreven:

> Got some offlist comments that I should clarify what I mean by hitless =
renumbering in the first question below.
>=20
> This isn't referring to what we have today, where we can take a node =
and provide one or more additional IPv6 addresses to it so that
> you can use this as a way to make renumbering less painful. =
Ultimately, you still have some point where traffic has to stop flowing
> from the old address and start flowing from the new one, even if it's =
pretty short.
> What I'm specifically referring to is yet-to-be implemented machinery =
to let a host take that new address and signal to the other
> side that it's going to be moving to a new address so that active =
traffic flows can be migrated without being reset. Since this is a
> lot more complicated, that's what I'm referring to as nice-to-have.=20
>=20
> Thanks,=20
> Wes George
>=20
> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf =
Of George, Wes E [NTK]
> Sent: Sunday, April 03, 2011 8:11 PM
> To: Sheng Jiang; renum@ietf.org
> Subject: Re: [renum] Fwd: New Version Notification for =
draft-jiang-ipv6-site-renum-guideline-00
>=20
> Wanted to get some of my comments from the mic out to the list-
>=20
> I think that there are a number of places where we need to break up =
the problem space in order to make it more manageable, both in
> terms of work that this group might take on vs work that is already =
partially done/belongs in existing groups, etc. Please add to
> the list and provide comments...
>=20
> Questions:
> Do we care about supporting hitless renumbering (that is, some form of =
make-before-break that allows end hosts to migrate their
> active sessions)?
> - I say nice to have, if at all, definitely not a primary goal Should =
we be considering an encapsulation (like IRON) or Locator ID
> split implementation within scope to solve the renumbering problem?
> - I say that we should be concentrating on renumbering problems that =
we can solve independent of any improved support in the
> network infrastructure for mobility and route scaling, but others may =
disagree.
>=20
> Different problem spaces:
> - BCP on how to limit the impact of renumbering when it is required - =
especially important as IPv6 rolls out and people are doing
> their once-in-a-blue-moon numbering plans, plus code work to support =
it
> - Device config:
> *on-box CLI and the places where it supports/requires IP address =
literals - places we can recommend that vendors support
> parameterization either through FQDNs or external files that allow you =
to change an address in multiple places in the config at once
> *a centralized management infrastructure that abstracts local config  =
from addressing *Dynamically numbered devices/networks vs
> static
>=20
> Thanks,
> Wes George
>=20
> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf =
Of Sheng Jiang
> Sent: Wednesday, January 26, 2011 4:43 AM
> To: renum@ietf.org
> Subject: [renum] Fwd: New Version Notification for =
draft-jiang-ipv6-site-renum-guideline-00
>=20
>=20
> A new version of I-D, draft-jiang-ipv6-site-renum-guideline-00.txt has =
been successfully submitted by Sheng Jiang and posted to the
> IETF repository.
>=20
> Filename:	 draft-jiang-ipv6-site-renum-guideline
> Revision:	 00
> Title:		 IPv6 Site Renumbering Guidelines and Further =
Works
> Creation_date:	 2011-01-26
> WG ID:		 Independent Submission
> Number_of_pages: 13
>=20
> Abstract:
> This document analyzes the existing issues for IPv6 site renumbering.
> It also analyzes the possible directions to solve these issues and =
gives recommendations. This document only takes the perspective
> of network and network protocols. Renumbering in IPv4 networks, in the =
dual-stack network or in the IPv4/IPv6 transition networks
> are out of scope.
>=20
> This document only takes the perspective of network and network =
protocols. According to the different stages, these issues are
> described in three categories: considerations during network design, =
considerations for routine network management, and
> considerations during renumbering operation. Recommended solutions or =
strategies are also described. Issues that still remain
> unsolvable are listed as the fourth category.
>=20
> Although we list a few non-network issues in this document, we =
consider them as issues that ISPs or network providers cannot affect.
> So, these issues are considered to be unsolvable and not explore =
further in these document, though they may be solved by OS
> implementations or application implementations.
>=20
> We summary the requests that need to extend current protocols as =
further works at the end of this document.
>=20
>=20
>=20
>=20
> The IETF Secretariat.
>=20
>=20
>=20
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
>=20
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum


From brian.e.carpenter@gmail.com  Tue Apr  5 00:46:18 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@core3.amsl.com
Delivered-To: renum@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D5243A68D4 for <renum@core3.amsl.com>; Tue,  5 Apr 2011 00:46:18 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LmCoLI4Z0aaG for <renum@core3.amsl.com>; Tue,  5 Apr 2011 00:46:11 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 5B6AA3A67EF for <renum@ietf.org>; Tue,  5 Apr 2011 00:46:10 -0700 (PDT)
Received: by wyb29 with SMTP id 29so95887wyb.31 for <renum@ietf.org>; Tue, 05 Apr 2011 00:47:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=40L7BxVRj122Ui+EYgyAm+PhGbod79TkCULjyVLLYzo=; b=QsKkLzHbruy+67te9CwBfnRB2ZD4LFBtvfXawYH1uH5PSSpTbgNqqmqfGckwrkRKJN X31524/SbbKidBjkEM6sXM1Qz3ioORL/qzceWvtKcJd1sfjymX0ySs7VzbFrvTBZD1bj wVgAQWFc+/j7ZRJjQaT8j8UThk5/HS0TLcLjg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Nk8PUnDrEcHL7X6V/rTmtefhwoUIJKjwn0Syex5e5zH/lwnJhApdkWFphMXhoQj8LA TheoL9ozOfb1fH/ko6OlCFzF8Gr5GgLtkUIJOLfedbSdbPzQSXdzl8f4llVXEYn6Wq4R TNMeDWHLjcGmUnFcCE8+LEIzXciH/buZzn1gI=
Received: by 10.216.65.16 with SMTP id e16mr4711192wed.93.1301989672746; Tue, 05 Apr 2011 00:47:52 -0700 (PDT)
Received: from [192.168.1.65] (host86-162-222-107.range86-162.btcentralplus.com [86.162.222.107]) by mx.google.com with ESMTPS id j49sm2604572wer.38.2011.04.05.00.47.51 (version=SSLv3 cipher=OTHER); Tue, 05 Apr 2011 00:47:51 -0700 (PDT)
Message-ID: <4D9AC925.1030801@gmail.com>
Date: Tue, 05 Apr 2011 19:47:49 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Teco Boot <teco@inf-net.nl>
References: <4D3FECA9.6060109@huawei.com>	<54E900DC635DAB4DB7A6D799B3C4CD8E10C6AD2E@PLSWM12A.ad.sprint.com>	<54E900DC635DAB4DB7A6D799B3C4CD8E10C6B190@PLSWM12A.ad.sprint.com> <01D88F72-77FE-49F0-86A5-46945059B96A@inf-net.nl>
In-Reply-To: <01D88F72-77FE-49F0-86A5-46945059B96A@inf-net.nl>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Sheng Jiang <shengjiang@huawei.com>, "George, Wes E \[NTK\]" <Wesley.E.George@sprint.com>, "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Fwd: New Version Notification for	draft-jiang-ipv6-site-renum-guideline-00
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2011 07:46:18 -0000

This is more or less the use case for shim6, which is standardised
and has running code. Shim6 was designed to maintain sessions
across multihoming events, and planned renumbering is a multihoming
event.

Regards
   Brian

On 2011-04-05 02:50, Teco Boot wrote:
> Wes,
> 
> I think there are lots of pieces of the puzzle for smooth, hitless renumbering. We can have the ambition combine those and complete the picture. I think this is more than a nice-to-have for unmanaged sites, although it may not work from day one, with basic IPv6 nodes. 
> 
> Teco 
> 
> Op 4 apr 2011, om 16:23 heeft George, Wes E [NTK] het volgende geschreven:
> 
>> Got some offlist comments that I should clarify what I mean by hitless renumbering in the first question below.
>>
>> This isn't referring to what we have today, where we can take a node and provide one or more additional IPv6 addresses to it so that
>> you can use this as a way to make renumbering less painful. Ultimately, you still have some point where traffic has to stop flowing
>> from the old address and start flowing from the new one, even if it's pretty short.
>> What I'm specifically referring to is yet-to-be implemented machinery to let a host take that new address and signal to the other
>> side that it's going to be moving to a new address so that active traffic flows can be migrated without being reset. Since this is a
>> lot more complicated, that's what I'm referring to as nice-to-have. 
>>
>> Thanks, 
>> Wes George
>>
>> -----Original Message-----
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of George, Wes E [NTK]
>> Sent: Sunday, April 03, 2011 8:11 PM
>> To: Sheng Jiang; renum@ietf.org
>> Subject: Re: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00
>>
>> Wanted to get some of my comments from the mic out to the list-
>>
>> I think that there are a number of places where we need to break up the problem space in order to make it more manageable, both in
>> terms of work that this group might take on vs work that is already partially done/belongs in existing groups, etc. Please add to
>> the list and provide comments...
>>
>> Questions:
>> Do we care about supporting hitless renumbering (that is, some form of make-before-break that allows end hosts to migrate their
>> active sessions)?
>> - I say nice to have, if at all, definitely not a primary goal Should we be considering an encapsulation (like IRON) or Locator ID
>> split implementation within scope to solve the renumbering problem?
>> - I say that we should be concentrating on renumbering problems that we can solve independent of any improved support in the
>> network infrastructure for mobility and route scaling, but others may disagree.
>>
>> Different problem spaces:
>> - BCP on how to limit the impact of renumbering when it is required - especially important as IPv6 rolls out and people are doing
>> their once-in-a-blue-moon numbering plans, plus code work to support it
>> - Device config:
>> *on-box CLI and the places where it supports/requires IP address literals - places we can recommend that vendors support
>> parameterization either through FQDNs or external files that allow you to change an address in multiple places in the config at once
>> *a centralized management infrastructure that abstracts local config  from addressing *Dynamically numbered devices/networks vs
>> static
>>
>> Thanks,
>> Wes George
>>
>> -----Original Message-----
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of Sheng Jiang
>> Sent: Wednesday, January 26, 2011 4:43 AM
>> To: renum@ietf.org
>> Subject: [renum] Fwd: New Version Notification for draft-jiang-ipv6-site-renum-guideline-00
>>
>>
>> A new version of I-D, draft-jiang-ipv6-site-renum-guideline-00.txt has been successfully submitted by Sheng Jiang and posted to the
>> IETF repository.
>>
>> Filename:	 draft-jiang-ipv6-site-renum-guideline
>> Revision:	 00
>> Title:		 IPv6 Site Renumbering Guidelines and Further Works
>> Creation_date:	 2011-01-26
>> WG ID:		 Independent Submission
>> Number_of_pages: 13
>>
>> Abstract:
>> This document analyzes the existing issues for IPv6 site renumbering.
>> It also analyzes the possible directions to solve these issues and gives recommendations. This document only takes the perspective
>> of network and network protocols. Renumbering in IPv4 networks, in the dual-stack network or in the IPv4/IPv6 transition networks
>> are out of scope.
>>
>> This document only takes the perspective of network and network protocols. According to the different stages, these issues are
>> described in three categories: considerations during network design, considerations for routine network management, and
>> considerations during renumbering operation. Recommended solutions or strategies are also described. Issues that still remain
>> unsolvable are listed as the fourth category.
>>
>> Although we list a few non-network issues in this document, we consider them as issues that ISPs or network providers cannot affect.
>> So, these issues are considered to be unsolvable and not explore further in these document, though they may be solved by OS
>> implementations or application implementations.
>>
>> We summary the requests that need to extend current protocols as further works at the end of this document.
>>
>>
>>
>>
>> The IETF Secretariat.
>>
>>
>>
>> _______________________________________________
>> 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 tjc@ecs.soton.ac.uk  Tue Apr  5 06:13:31 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@core3.amsl.com
Delivered-To: renum@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2EDD28C0E4 for <renum@core3.amsl.com>; Tue,  5 Apr 2011 06:13:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brKnCtehAcWt for <renum@core3.amsl.com>; Tue,  5 Apr 2011 06:13:21 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by core3.amsl.com (Postfix) with ESMTP id 5FA8328C0F5 for <renum@ietf.org>; Tue,  5 Apr 2011 06:13:19 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p35DEvgM007933;  Tue, 5 Apr 2011 14:14:57 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p35DEvgM007933
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1302009297; bh=+XM1P9qTyGYqiXjIyz9Ot5Lo8h4=; h=From:Subject:Date:Cc:To:Mime-Version:References; b=Q+Ia5QT9J8wAawdX7jJFOUkGiEIsBb1fgR3fRLUiOCq4GG0iQjtEKMAJmpTMrnk3U kT/wLwwdSTa7kjCuZ1VgbJjGti/DYQSNqk2FevXxipdlVpkCZuCTuP/wUReVU1a9x6 K6iWYhpHtEnpsTkP6eDDWryfelUR2vFSuT8Ug7QE=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n34EEv003565367821 ret-id none; Tue, 05 Apr 2011 14:14:57 +0100
Received: from dhcp-152-78-95-103.ecs.soton.ac.uk (dhcp-152-78-95-103.ecs.soton.ac.uk [152.78.95.103]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p35DEngU014482 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 5 Apr 2011 14:14:50 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/mixed; boundary=Apple-Mail-86--567941500
Date: Tue, 5 Apr 2011 14:14:49 +0100
Message-ID: <EMEW3|c62a65a4ec77804c4ba46603047a770bn34EEv03tjc|ecs.soton.ac.uk|DFC431D1-50DD-449E-943C-B8B337E5DD73@ecs.soton.ac.uk>
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n34EEv003565367800; tid=n34EEv003565367821; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
References: <DFC431D1-50DD-449E-943C-B8B337E5DD73@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p35DEvgM007933
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: Ron Bonica <rbonica@juniper.net>
Subject: [renum] Draft BoF minutes from IETF80
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2011 13:13:31 -0000

--Apple-Mail-86--567941500
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

Thanks again to Fred Templin for taking minutes; I've edited these up a =
little to be checked before we post them as final.

Comments/corrections by this Friday please.

Thanks,
Tim



--Apple-Mail-86--567941500
Content-Disposition: attachment;
	filename=renum80-draft.txt
Content-Type: text/plain;
	name="renum80-draft.txt"
Content-Transfer-Encoding: quoted-printable

****************************************************************
Site Renumbering (renum) BOF - IETF80 - March 31, 2011
****************************************************************

-----------------------------------------------------------------
0) Agenda bash
   http://www.ietf.org/proceedings/80/agenda/renum.txt
-----------------------------------------------------------------
- Brian Carpenter, Tim Chown co-chairs
- Same Note Well disclosure rules apply here as for WGs
- Need to stay focused on-topic
- BOF sponsored by Ron Bonica - not able to attend but present on=20
  Webex, Jabber and audio feed
- Brian presented a summary of the draft description/charter for the=20
  proposed renum WG
- Renumbering sometimes unavoidable
- Three documents as starting points (RFC4192, RFC5887,=20
  draft-jiang-ipv6-site-renum-guideline-00); plus an older draft from=20
  Tim Chown (draft-chown-v6ops-renumber-thinkabout-05) which was drawn=20=

  upon to create RFC5887

-----------------------------------------------------------------
1) Renumbering still needs work (RFC5887)
   http://tools.ietf.org/html/rfc5887
   http://www.ietf.org/proceedings/80/slides/renum-1.pdf
-----------------------------------------------------------------
- Renumbering is a non-issue for many users (e.g. renumbering a CPE =
every=20
  time you boot, for a simple single subnet home network)
- Planned renumbering of larger sites sometimes needed:
  - when change ISP
  - when add a second ISP
  - when ISP has to renumber
  - etc.
- Note: PI, ULA, NAT don't get you completely away from renumbering
- A hard target - but we need a solution for renumbering
- The RFC includes a survey of existing mechanisms/tools (DHC, SLAAC, =
etc.)
- IPv6 gives multi-addressing, allows the RFC4192 'no flag day' approach
- It surveys operational issues - hard ones are application-layer issues=20=

  and management issues
- Problem - finding all of the configuration files that have addresses
- Possible mechanisms - shim6, MANET work, etc
- Gap analysis - address lifetimes in socket API, etc. Lots of little=20
  things that don't work well
- How to tell peers that your address has changed - e.g. what if MIPv6=20=

  HA renumbers?
- No questions

-----------------------------------------------------------------
2) UNH-IOL Testing Event - Tim Winters
   http://www.ietf.org/proceedings/80/slides/renum-7.pdf
-----------------------------------------------------------------
- RFC6204 testing run by UNH for DOCSIS and Ethernet CE routers
- DHCPv6 Prefix delegation for renumbering
- DHCPv6 reconfigure is preferred method
- DHCPv6 renew is another method
- DHCPv6 reconfigure not included in all CEs
- DHCPv6 renew/reply - servers were sending two IA_PDs, but routers were=20=

  only servicing the first - caused loss of connectivity
- Recommendations - renumbering through renew/reply was the most =
successful=20
  approach
Brian Carpenter - Tim, you did an IPv6 renumber in 6NET, have things =
gotten=20
  better since?
Tim Chown - we didn't have DHCPv6 PD then, but the network element=20
  renumbering/multi-addressing worked fine (results on 6NET web site)
Tim Winters - thought Reconfigure would work, but it didn't. Lots of =
moving=20
  parts - DHCP PD, SLAAC, M&O bits, etc.

-----------------------------------------------------------------
3) IPv6 site renumbering guidelines - Sheng Jiang
   http://tools.ietf.org/html/draft-jiang-ipv6-site-renum-guideline-00
   http://www.ietf.org/proceedings/80/slides/renum-8.ppt
-----------------------------------------------------------------
- Renumbering is not new - standing on shoulders of giants
- Dates back to at least RFC1900 - "Renumbering needs work"
- Long list of additional RFCs and credits
- Focusing here on IPv6 renumbering
- Three perspectives on issues: network design, network operation,=20
  renumbering operation
- Summarised requests to extend current protocols
- Recommends network choosing only one of SLAAC or DHCP
- DNS record updates
- Security mechanisms needed, e.g. SEND
- Misc: addresses should not be used to configure network utilities
- Management: stable records and long lifetimes means less flexibility
- Transition period - ideally needs to be longer than all address =
lifetimes
- Many unsolved remaining issues=20
- But some of the unsolved issues are harmless and/or minimal impacts
- Routers might need to be restarted due to renumbering - RFC2072
- Further analysis needed
- Many non-network issues
- Requests to extend protocols - diagnostic function to detect =
conflicts,=20
  combine forward and reverse DNS updates, etc.
Brian - note this is a very early draft; there is much more development=20=

  to come
Sheng - the draft was drawn up from from material in RFC5887
Lee Howard - concerned about recommendation to choose either SLAAC or =
DHCP,
  need to figure out how to reconcile them
Sheng - coexistence is possible; working on the issues, but we're trying=20=

  to make coexistence better
Brian - managed networks can take that approach but not unmanaged
Bob Hinden - different IPv6 deployments will do different things on=20
  different subnets
Teco Boot - problems with both SLAAC and DHCPv6 - need to take away the=20=

  problems
Tim C. - have different address configuration mechanisms in a campus; =
manual=20
  servers, DHCPv6 for managed and SLAAC for unmanaged systems.=20
Brian - we need clarity for both managed and unmanaged scenarios

-----------------------------------------------------------------
4) Renumbering Networks (RFC4192) - Fred Baker
   http://www.ietf.org/proceedings/80/slides/renum-2.ppt
-----------------------------------------------------------------
- Fred told a story - thought renumbering wasn't hard and thought he was=20=

  missing something, so he wrote an Internet draft. Went to operators to=20=

  ask what was hard. After discussion, Fred, Ralph Droms and Eliot Lear=20=

  got together and wrote a first draft
- Turned out is was hard.  The reason: almost any configuration tool can=20=

  change the network configuration
- The problem is stupidity - places where people write down numbers=20
  instead of names
- Thing #1 that makes renumbering hard - human stupidity
- Fred went on to describe how Cisco outsources much of its =
manufacturing=20
  and shipping, but in one case as units were shipped scanners noted =
down=20
  addresses of equipment, and sent data back to the company, but by IP=20=

  address!
- The fix: DNS!
- Thing #2 - numeric router configurations
- Examples of configuration paradigm - not as simple as adding things to =
ACLs=20
  and removing things
  Fred continued part two of his talk - My View of Network Renumbering
- Q: how did the network box get a number in the first place?
- There is some kind of configuration language, program, etc. in place
- A simple approach might be to build a configuration management tool
- Need it to be able to add or delete prefixes/addresses
- It would handle both the initial numbering of the network and =
subsequent=20
  renumbering of the network
Brian - what if the site manager doesn't have tools?
Fred - they might want to get tools
Cathy Aronson - IPv6 addresses are hard to remember - need to use a =
name.=20
  Addresses dynamically assigned - need to deal with customer networks=20=

  as well as your own
Fred - just added this to the list
Mark Rample(?) - point on human stupidity - firewall rules with IP=20
  addresses
Fred - suggests a network management tool to deal with a database of
  ACL settings. Need it to be ONE manager that changes by add/drop
Mark - 2nd observation - hasn't IPv6 introduced a problem? In IPv4,
  renumbered and only had to change the firewall (NAT). Took 10-15mins.
  In IPv6, addresses are back in the customer network.
Joel Jaeggli - firewalls need configuration management policy tool.=20
  Need the problem to be made tractable.
Wes George - need to decide on goals.

-----------------------------------------------------------------
5) Solution Space proposals
-----------------------------------------------------------------

The chairs explained these talks were only included as 1-slide lightning
talks to show there is interest in solutions in the renumbering space;
solutions are not in scope for the discussion today though.

5a) Teco Boot - BRDP
  http://www.ietf.org/proceedings/80/slides/renum-3.pdf
- edge networks have multiple uplinks to multiple ISPs
- single edge network
- source-address based forwarding (packets from ISP1 source address=20
  go through ISP1)
- advertise prefixes downlink in multihop fashion
- work came from MANET space

5b) Fred Templin - IRON
  http://www.ietf.org/proceedings/80/slides/renum-4.ppt
- Fred described his overlay network approach (see RFC6179)
- falls in the category of renumbering avoidance

5c) Remi Despres - approach; not a solution
  http://www.ietf.org/proceedings/80/slides/renum-5.pdf
- renumber hosts, but avoid renumbering routers
- hosts must cooperate
- encapsulation of one family in a second family
- using ULA local IPv6 addressing
- when site changes providers, send DHCPv6 update and hosts do the =
updates

5d) Bing Liu - SLAAC/DHCPv6 conflict diagnostics during site renumbering
  http://www.ietf.org/proceedings/80/slides/renum-6.pdf
- prefix announced
- if host detects conflict, reports mistakes to network
- admins can identify mistakes during renumbering
- human stupidity is a key issue

-----------------------------------------------------------------
6) Discussion of goals and milestones
-----------------------------------------------------------------

Brian - if we assume for a moment that there will be a WG formed, let's
  look at the goals and milestones
Fred Baker - WG description - build a mechanism/tool/procedure/etc.
  to provide for site-wide renumbering?
Brian - yes
Fred - thinks renumbering is a special-case of numbering; if we are=20
  going to charter a WG to look at small aspect of numbering, probably=20=

  should do a WG to look at configuring and managing a *network*
Brian - Are we trying to build a single tool, or a methodology?
Fred - bigger problem has to solve it anyway
Bob Hinden - lots of thought about this earlier, IPv6 was designed
  to make this easier. Supports the work. Making renumbering routine
  is too high of a goal - should be happy if we could get to 90%.
  Should be a non-goal to renumber every day.
Tim Chown - we should discuss how realistic things are
Brian - RRG looked into frequent renumbering, but unrealistic (Bob
  is right)
Erik Kline - things often managed by completely different organizations.=20=

  Application problem - need configuration updates from different=20
  systems, e.g. netconf WG.  Could lead there dangerously.
Tim C. - the issue is not dissimilar to scenarios where a site has =
policy
  in place on data protection, but information leaks due to republishing
  by others - it's similar with renumbering, the numbers may be used by
  users or non-network teams at the site in unexpected ways
Brian - after renumbering, CERN program library had a statistics module=20=

  with hard-coded numberings
Tim Shepard - thinks IPv6 deployment incredibly important. Solving this=20=

  problem is necessary for the viability of IPv6. Huge problem and =
scary.=20
  Problem isn't solved by an IETF WG - problem is in the heads of =
network=20
  admins who think they know how to deploy IPv6.
Tim C. - just reinforcing Fred B.'s point
Tim S. - act of typing an IPv6 address is creating a future problem
Tim C. - may be protocol gaps or ambiguities in protocols; we should =
seek
  to identify and remedy both where possible
Tim S. - wants a WG, but it may not be enough
Brian C. - what admins will do for IPv6 is close to the same practice
  that is used for IPv4
Shane Amanti - supports taking the work on, but wants more specificity.
  Put difficult parts later in the process. Have to do this, because PI=20=

  is not sustainable.
Lee Howard - after hearing Fred's presentation and the 1-slide talks, at=20=

  least 7 major problems. Making one single point of reference scary due=20=

  to single point of failure, human errors. There are a number of =
problems=20
  - not just one problem. We should only solve this for IPv6
Brian - IPv4 problem is overtaken by events
Lee - IETF cannot resolve human stupidity. We are creating a single
  point of attack if we're not careful. Doesn't think it is tractable
  with the charter as written.
Chris Morrow - thinks that could be addressed by abstractions, but not =
in=20
  actual device. Goal of IRTF wasn't renumbering. Making renumbering for=20=

  a single organization may be tractable. When IPv6 was finished 10 yrs=20=

  ago ... problem now is configuration management; not address =
management
Mark Townsley - problem space centered around large / medium-sized =
sites,
  also actively-managed networks. Will this work also include small
  networks and unmanaged networks?
Tim Chown - need to consider low power subnets/PANs in SOHOs - what =
happens=20
  when the ISP renumbers?  Users just want remote light switches to work
  when controlled via their multi-subnet home network
Mark T. - flash-cut renumbering of residential networks necessary
Tim C. - ULAs could be in-scope. Will be discussed in v6ops later today
Brian - is our scope managed networks, unmanaged, or both?
Thomas Narten - extremely pessimistic that we can do anything in this
  space. Reality of gap between what we have today and where we need to
  get to is tremendous. E.g. site with 100 routers - how can we help =
them?
  Lots we have to do, but not sure we can help them. Gap is astonishing,
  people who do this stuff don't attend this meeting.  Need to peel off=20=

  specific problems before we jump into this work.
Brian - should we do piece-parts?
Thomas - look at architecture
Greg Lebowicz - have to do this in order to prevent IPv4-like NATs.
  Rather have great minds fail while trying rather than give up now
  because it looks too difficult.

-----------------------------------------------------------------
7) Proposed WG charter targets
-----------------------------------------------------------------

Brian Carpenter - shows list of initial goals/deliverable/milestones
Wes George - list of milestones looks vague - do we want to talk about
  solutions, and will they solve the problems? Do we want to farm off
  application issues to application area?  Need to have not as many IP=20=

  addresses in CLI in routers anymore. Need to have these things in=20
  initial set of goals.
Brian - can this be integrated into charter?
Wes - yes, some work needed though.
Ralph Droms - Thomas' remarks - tension between tool development, and =
big
  problem with a number of steps along the way. May not be able to get
  to a complete automation from beginning to end. Keep in mind that
  these things will be deployed but human beings. Need to coordinate
  human operations.
Brian  - milestone dates unrealistic. Won't have this done by IPv6 day.
Dan Romascanu - question on 2nd deliverable - are there people =
interested=20
  in working on a management model for site renumbering?
Brian - wants to ask Fred B. work work on managed side. Need to find=20
  someone for unmanaged side.
Remi Despres - can we present solutions here, or is it just renumbering
  guidelines
Brian - need to be clear on problem statement and guidelines before
  looking at solutions
Brian - solutions identified here might belong in different WGs
Ralph Droms - pieces being coordinated - one piece shouldn't break the=20=

  other pieces. Understand problem here before charging off into =
solutions
Tim Chown - make the items clearer
Bob Hinden - router renumbering RFC - will you look at this?
Brian - wasn't much information available
Bob - might want to look at this
Brian - we could ask volunteers to look into this and read it
Ralph - document doesn't have sufficient controls, synchronization,
  etc. Talks about prefix substitutions, but not much more.
Bob - maybe fix the router renumbering document?
Wes George - possibly have fixing the document as top of the list
Thomas Narten - router renumbering was an academic exercise, but
  disconnected from reality

-----------------------------------------------------------------
8) Conclusion discussion
-----------------------------------------------------------------

Brian - should further work be done (draft charter needs to change)?
Thomas - how can anyone be opposed to working on this, but what can
  we do to make a difference?
Dan Wing - doesn't think we can be successful
Thomas - work on the tractable problems
Tim C. - it's an 80/20 thing - need to identify and prioritise work =
items
Scott Brim - thinks we should go forward on this
David Kessens - topic has been discussed so many times, but nothing in
  charter to do something complete. Unless we can come up with something=20=

  that we can complete, shouldn't do a working group
Brian - a number of goals in the draft charter - not just handwaving
Glenn Kowak - problem needs to be solved - need to pay attention
  to the cost. One possible outcome is to identify some other group that=20=

  can get this done.  A moment of Zen; it's a little like Y2K.
Remi Despres - likes the idea of identifying problems that are tractable=20=

  and those that are not.
Tim Shepard - pessimistic, but we should still try. More urgent things=20=

  are not writing drafts. Need to get people to think about places where=20=

  IPv6 addresses are typed in. Maybe we need to set up a wiki? Get =
people=20
  to share all of these places where renumbering is needed. Need to get=20=

  the word out.
Cathy Aronson - RIR issues - infinite number of addresses in IPv6, so=20
  policies are that people get PI blocks because renumbering is hard. =
Has=20
  implications on the routing table. May may/not be doing this in an=20
  efficient way.
Lorezno Colletti - look at access networks, enterprise networks, mobile=20=

  networks. People say this is too hard, and he kind of agrees. No =
"magic=20
  wand" to renumber an entire AS - too ambitious. However, operational=20=

  community doesn't know how to renumber at even a small scale. So, for=20=

  the smaller tasks we have a lot of the pieces but still don't know how=20=

  to put them together. Can ssh into routers and do what he wants.
  Maybe we can focus on individual parts like renumbering a CPE,=20
  renumbering a mobile network, etc.
Sheng Jiang - agrees issue is difficult. Does not mean that every small=20=

  step is not useful. Start with small steps, may still have problems,=20=

  but our work will make things better.
Greg Lebowicz - hears Lorenzo saying we want well-defined and useful=20
  use cases.
Ruediger Volk - getting depressed. What idea did the RRG chairs have =
when=20
  they put renumbering avoidance as an architectural goal?  Probably we=20=

  should do something like the avoidance. In general, probably picking=20=

  things where names/numbers need to be matched is an area where fixed=20=

  identification is relevant. But, this needs to be separated out.=20
  Big jump in architecture - especially for host stacks. Restrict renum =
to=20
  domains where it can be managed (e.g., provider networks).
Brian - how many people willing to work on documents? 10-12
Brian - how many think we should have a WG? 20-25
Brian - how many think we should NOT have a WG? 5-6
Brian - how many unsure? 12
Thomas Narten - is it premature to form a WG? BOF might be appropriate,=20=

  but what would be appropriate for WG?
Brian - WG gives a point of focus
Scott Brim - should it be a research group? Brian and Wes - No!
Greg Lebowicz - problem is immediate - not a research group issue.
Dan Romascanu - Ron on audio stream but couldn't jabber. Dan's opinion=20=

  is there is a certain level of interest, but problem statement needs=20=

  to be developed.
Ron Bonica - at the moment, I am torn.
Ralph Droms - keep folks who run networks in the loop. Is there some way=20=

  we could adopt a model like the IETF tools development group? Can we=20=

  move forward incrementally?
Brian - not just ISP operators, but also enterprise operators
Ralph - Zigbee alliance, 802.15.4 analogy. How to do this for completely=20=

  unmanaged networks?
Ron Bonica - give me a day or two to think about it.
Ralph - research group on renumbering avoidance is a good topic
Cathy - renumbering avoidance is what we do NOW!

-----------------------------------------------------------------
[ end of BOF ]=20
-----------------------------------------------------------------

--Apple-Mail-86--567941500--

From tjc@ecs.soton.ac.uk  Wed Apr 13 03:48:55 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfc.amsl.com
Delivered-To: renum@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 85A22E06C1 for <renum@ietfc.amsl.com>; Wed, 13 Apr 2011 03:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U1bI8IucZKck for <renum@ietfc.amsl.com>; Wed, 13 Apr 2011 03:48:47 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfc.amsl.com (Postfix) with ESMTP id 0DA55E0678 for <renum@ietf.org>; Wed, 13 Apr 2011 03:48:46 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p3DAmjoA015122 for <renum@ietf.org>; Wed, 13 Apr 2011 11:48:45 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p3DAmjoA015122
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1302691725; bh=69x4/xVtblKvUNBp4kSGe5WVCq8=; h=From:Subject:Date:To:Mime-Version:References; b=Ic+tIttBRekP4NcNb6fp1C3qnOO/TbjzcAqcOTU6DpdzSEzFPpEYqOajJqE9pln+7 djGouHIQZwJIYS+70YvNDwiMzflSwcAfilj9gYpU+EqZG0IqxeegUWmtgozSc1W8DI wDKimTmmJ+RFEhm5ZfQGsAl17YUQ5S9m0vk8OvSA=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n3CBmj00356398959Y ret-id none; Wed, 13 Apr 2011 11:48:45 +0100
Received: from ip-036-012.vpn.soton.ac.uk (ip-036-012.vpn.soton.ac.uk [152.78.36.12]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p3DAmSCv020866 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Wed, 13 Apr 2011 11:48:42 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 13 Apr 2011 11:47:49 +0100
Message-ID: <EMEW3|fc608b57db2bdd70bffd38f24b60740bn3CBmj03tjc|ecs.soton.ac.uk|286ECFB2-5F1E-436A-9DF5-9CF11E422DE0@ecs.soton.ac.uk>
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n3CBmj003563989500; tid=n3CBmj00356398959Y; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
References: <286ECFB2-5F1E-436A-9DF5-9CF11E422DE0@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p3DAmjoA015122
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: [renum] IETF 80 BoF minutes uploaded
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2011 10:48:55 -0000

Hi,

The finalised minutes are now uploaded.

You can read these and check the presentations at the meeting materials =
page under RENUM.

https://datatracker.ietf.org/meeting/80/materials.html

Tim=

From tjc@ecs.soton.ac.uk  Wed Apr 13 03:48:55 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfc.amsl.com
Delivered-To: renum@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8C6D4E0678 for <renum@ietfc.amsl.com>; Wed, 13 Apr 2011 03:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JCAAdprw2E0d for <renum@ietfc.amsl.com>; Wed, 13 Apr 2011 03:48:52 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfc.amsl.com (Postfix) with ESMTP id 675B1E06D4 for <renum@ietf.org>; Wed, 13 Apr 2011 03:48:52 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p3DAmlKC015160 for <renum@ietf.org>; Wed, 13 Apr 2011 11:48:47 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p3DAmlKC015160
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1302691727; bh=69x4/xVtblKvUNBp4kSGe5WVCq8=; h=From:Subject:Date:To:Mime-Version:References; b=hS1NZ8eZ+smgd5s5v1i9Q67Ml8sKHim0kRxHWqkmaPiFc7AqSJMPhda+9L8G7q2Hk 3WqLt5Zo+3GFHdym99rNwqEhTYD+Y/URgb6zUuBY84kAcabwveHnGdDThk6v4VIrTH pYMXcgyRkzg4DplIfVseEwNmDgOmtyCC7Y0jZatM=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n3CBml00356398969F ret-id none; Wed, 13 Apr 2011 11:48:47 +0100
Received: from ip-036-012.vpn.soton.ac.uk (ip-036-012.vpn.soton.ac.uk [152.78.36.12]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p3DAmSCt020866 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Wed, 13 Apr 2011 11:48:41 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 13 Apr 2011 11:36:58 +0100
Message-ID: <EMEW3|05de15f4fa509cc129d9ac6711c563dfn3CBml03tjc|ecs.soton.ac.uk|F1D9E31B-85F4-46E6-90D6-43DC12BD5B53@ecs.soton.ac.uk>
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n3CBml003563989600; tid=n3CBml00356398969F; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
References: <F1D9E31B-85F4-46E6-90D6-43DC12BD5B53@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p3DAmlKC015160
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: [renum] IETF 80 BoF minutes uploaded
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2011 10:48:55 -0000

Hi,

The finalised minutes are now uploaded.

You can read these and check the presentations at the meeting materials =
page under RENUM.

https://datatracker.ietf.org/meeting/80/materials.html

Tim=

From Fred.L.Templin@boeing.com  Thu Apr 14 13:44:39 2011
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: renum@ietfc.amsl.com
Delivered-To: renum@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id D8591E0836; Thu, 14 Apr 2011 13:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.49
X-Spam-Level: 
X-Spam-Status: No, score=-6.49 tagged_above=-999 required=5 tests=[AWL=0.109,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bNfIIRU0uGtE; Thu, 14 Apr 2011 13:44:38 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by ietfc.amsl.com (Postfix) with ESMTP id A0262E07AB; Thu, 14 Apr 2011 13:44:32 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p3EKiVHO016027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 14 Apr 2011 13:44:32 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p3EKiVKC009122; Thu, 14 Apr 2011 15:44:31 -0500 (CDT)
Received: from XCH-NWHT-07.nw.nos.boeing.com (xch-nwht-07.nw.nos.boeing.com [130.247.25.111]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p3EKiTRT009074 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 14 Apr 2011 15:44:30 -0500 (CDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-07.nw.nos.boeing.com ([130.247.25.111]) with mapi; Thu, 14 Apr 2011 13:44:29 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>, "renum@ietf.org" <renum@ietf.org>
Date: Thu, 14 Apr 2011 13:44:28 -0700
Thread-Topic: Simplified Automatic IPv6 Renumbering within ISATAP Sites (non-draft)
Thread-Index: Acv4RPaAwKW3FKbCS76FU3Oxx/og4QAGIvjAAJ/PblA=
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C699E7DD1@XCH-NW-01V.nw.nos.boeing.com>
References: <7B64C6B4-23DB-44AE-8941-ACE9964A3578@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A65C699E721E@XCH-NW-01V.nw.nos.boeing.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65C699E721E@XCH-NW-01V.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [renum] Simplified Automatic IPv6 Renumbering within ISATAP Sites (non-draft)
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2011 20:44:40 -0000

The following is not a draft, but rather just a set
of ideas. Any comments or suggestions?

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

--- cut here ---

Introduction
************
Countless end user sites in the Internet today still have
predominantly IPv4 infrastructures. These sites range in
size from small home/office networks to large corporate
enterprise networks, but share the commonality that IPv4
continues to provide satisfactory internal routing and
addressing services. As more and more IPv6-only services
are deployed in the Internet, however, hosts within the
site will increasingly require IPv6 functionality for
external access.

Such IPv4 sites can use ISATAP [RFC5214] to provide IPv6
services to hosts within the site. Advertising ISATAP
routers distribute IPv6 prefixes obtained from an ISP
to hosts within the site via DHCPv6 or SLAAC for address
autoconfiguration purposes. If the site subsequently
reconnects to a different ISP, however, the site must
renumber to use addresses derived from the new IPv6
prefixes [RFC1900][RFC4192][RFC5887]. This non-draft
provides operational guidance for accommodating
simplified automatic renumbering within ISATAP sites.

Characteristics of Existing IPv4 Sites
**************************************
Existing end user sites use IPv4 routing and addressing
internally for normal IT operations such as filesharing,
network printing, e-mail, conferencing and numerous other
critical site-internal networking services. Such sites
typically have an abundance of public or private IPv4
addresses for internal networking, and are separated from
the public Internet by firewalls, packet filtering gateways,
proxies, address translators and other site border securing
devices. To date, such sites have had little incentive to
enable IPv6 services internally [RFC1687].

With the emergence of IPv6-only services within the public
Internet, however, existing IPv4 sites will increasingly
require a means for enabling IPv6 services so that hosts
within the site can communicate with IPv6 correspondents
in the Internet. Such services must be deployable with
minimal configuration and in a fashion that will not cause
disruptions to existing IPv4 services within the site. The
Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
[RFC5214] provides a simple-to-use service that sites can
deploy in the near term to meet these reqirements.

Enabling Client-Side IPv6 Services with ISATAP
**********************************************
Small sites typically arrange to obtain public IPv6 prefixes
from an Internet Service Provider (ISP) in the same fashion
as for home network users. When the ISP does not yet provide
native IPv6 services, it can instead offer a transitional
service with native-equivalent capabilities using 6RD
[RFC5569][RFC5969]. Large sites typically obtain provider
independent IPv6 prefixes from an Internet registry and
advertise the prefixes into the IPv6 routing system on their
own behalf, i.e., they act as an ISP unto themselves. (Such
large sites need never incur a site-wide IPv6 renumbering.)

After obtaining IPv6 prefixes, the site can automatically
enable ISATAP based IPv6 services by configuring one or more
site border routers as advertising ISATAP routers. Each such
ISATAP router is added to the Potential Router List (PRL) for
the site so that hosts can discover them for default route
and address auto-configuration purposes.

ISATAP hosts will automatically discover ISATAP site border
routers and configure ISATAP addresses using either Stateless
Address AutoConfiguration (SLAAC) or the Dynamic Host
Configuration Protocol for IPv6 (DHCPv6). In order to provide
a simple service that does not interact poorly with existing
site topological arrangements, the site should limit IPv6
operation for external access only so that hosts only use
the ISATAP service for communicating with IPv6 correspondents
on the public Internet, while continuing to use IPv4 services
for intra-site communications.

In order to maintain an external-only service, the site
should not publish any IPv6 addresses provided by ISATAP
within the site name service. The site should further not
write down any IPv6 literal addresses within configuration
files, documentation, packet filter rules, etc. An exception
to this rule is that literal addresses may be used within
packet filtering rules as long as they can be automatically
rewritten during a site renumbering event. In this way,
intra-site communications will continue to use existing
IPv4 networking services instead of ISATAP served IPv6
services.

Simplified Automatic Renumbering within ISATAP Sites
****************************************************
When the site is configured in the manner described above,
site renumbering in the event of a change in an ISP-served
IPv6 prefix entails only the renumbering of IPv6 addresses
and/or prefixes that are assigned to the ISATAP interfaces
of hosts within the site. In some cases, filtering rules
(e.g., within site border firewall filtering tables) may
also require renumbering, but this operation can be automated
and limited to only one or a few "touch points" at the site
border.

In order to renumber the ISATAP interfaces of hosts within
the site, however, the ISATAP routers need only schedule
the services offered by the old ISP for deprecation while
beginning to advertise the IPv6 prefixes provided by the
new ISP. ISATAP host interface address lifetimes will
eventually expire, and the host will renumber its interfaces
with addresses derived from the new prefixes.

If the site has published the IPv6 addresses of any site-
internal nodes within the public Internet DNS system, then
the corresponding resource records will need to be updated
during the renumbering operation. This can be accomplished
via secure dynamic updates to the DNS. =
