
From brian.e.carpenter@gmail.com  Wed Jan  5 13:31:44 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 14E033A6DCE for <renum@core3.amsl.com>; Wed,  5 Jan 2011 13:31:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.38
X-Spam-Level: 
X-Spam-Status: No, score=-103.38 tagged_above=-999 required=5 tests=[AWL=0.219, 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 uYMc-QHOH63T for <renum@core3.amsl.com>; Wed,  5 Jan 2011 13:31:43 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 042233A6D28 for <renum@ietf.org>; Wed,  5 Jan 2011 13:31:42 -0800 (PST)
Received: by wyf23 with SMTP id 23so16477852wyf.31 for <renum@ietf.org>; Wed, 05 Jan 2011 13:33:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=W8yM1OaBSkUxGIM7vr4K1RhWe4H+StqhZA8jxeVJ0l4=; b=XiIBNqPIxZSlEnwqAnT5wFCH/z7qckUMqXzxGPQRjrSYKRpBK//ogkY+ssCfJMGrDr jb0cZC4fIW91i6ojG1zaJhchjd+0lF/SIRe3iPeNwiH6RhjrQ0ZKAS5e47WgndvybpiH IbxFSNwwdoJ+PXZP3qhzMDLXYHotpo8qmkPzg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; b=JkitDJEBeu2W99LHxPA1O0VYSQJZ5bbH+6kP8ZDd9l3UiksjQ0HS41Gzg6I2kKeVgI PPDVT8CSRzP6rq86nmzUJm0RhhWGMJlYpT3kFZMfSpsOLzRAnBJFV3Tx+bRVocSs6GDV p9cBPe+bihvo4sN9r0FdL59VikQpHFwrKYg2g=
Received: by 10.227.169.196 with SMTP id a4mr13548901wbz.185.1294263199132; Wed, 05 Jan 2011 13:33:19 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id q18sm16272059wbe.5.2011.01.05.13.33.16 (version=SSLv3 cipher=RC4-MD5); Wed, 05 Jan 2011 13:33:18 -0800 (PST)
Message-ID: <4D24E399.8000101@gmail.com>
Date: Thu, 06 Jan 2011 10:33:13 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: renum@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [renum] Renumbering BOF?
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: Wed, 05 Jan 2011 21:31:44 -0000

Hi,

Back to work...

Does anyone have the feeling that we have enough to chew on to justify
a renumbering BOF in Prague? I'd need at least one significant topic
to discuss, and a volunteer to produce a draft in the near future -
the ADs are unlikely to approve a BOF without any sign of a draft.

So far, our discussions have been a bit discursive, apart from
Fred's proposal to develop a management model for site renumbering:
http://www.ietf.org/mail-archive/web/renum/current/msg00035.html

Are we interested in developing such an approach? If so, there isn't
much time to do so:

2011-01-31 (Monday): Cutoff date for BOF proposal requests to Area Directors at 17:00 PT

-- 
Regards
   Brian Carpenter



From shengjiang@huawei.com  Wed Jan  5 16:57:21 2011
Return-Path: <shengjiang@huawei.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 D97293A6DD3 for <renum@core3.amsl.com>; Wed,  5 Jan 2011 16:57:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.643
X-Spam-Level: 
X-Spam-Status: No, score=-3.643 tagged_above=-999 required=5 tests=[AWL=0.852,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.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 JHyfFpQBK3iW for <renum@core3.amsl.com>; Wed,  5 Jan 2011 16:57:21 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id DC4143A6D79 for <renum@ietf.org>; Wed,  5 Jan 2011 16:57:20 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEK000GOTETEM@szxga04-in.huawei.com> for renum@ietf.org; Thu, 06 Jan 2011 08:59:17 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEK00FJVTETUX@szxga04-in.huawei.com> for renum@ietf.org; Thu, 06 Jan 2011 08:59:17 +0800 (CST)
Received: from j66104a ([10.110.98.58]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LEK000IUTESQQ@szxml06-in.huawei.com> for renum@ietf.org; Thu, 06 Jan 2011 08:59:17 +0800 (CST)
Date: Thu, 06 Jan 2011 08:59:18 +0800
From: Sheng Jiang <shengjiang@huawei.com>
In-reply-to: <4D24E399.8000101@gmail.com>
To: 'Brian E Carpenter' <brian.e.carpenter@gmail.com>, renum@ietf.org, 'Fred Baker' <fred@cisco.com>
Message-id: <003401cbad3c$f2d501c0$3a626e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcutIEDsQwip5m3OTRSqrL9EW+uRNwAG3+gg
Subject: Re: [renum] Renumbering BOF?
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: Thu, 06 Jan 2011 00:57:21 -0000

Hi, Brian,

We are already starting to work on a problem statement draft. It should be possible to submit a
primary version by the end of this month. Of course, we would like to work with you and anybody
interested.

Now, the first important question is what kind of direction we want to choice, or we just list all
of possibilities in the draft? Are we going to fix the current minor issues one by one (we have
located several minor issues that need to modify or extend current protocols) or propose a big new
model to solve most issues together? Personally, I am hesitating to choose the latter since it
would be difficult to deploy such new and big mechanism in the current mature networks.

Regards,

Sheng

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] 
> On Behalf Of Brian E Carpenter
> Sent: Thursday, January 06, 2011 5:33 AM
> To: renum@ietf.org
> Subject: [renum] Renumbering BOF?
> 
> Hi,
> 
> Back to work...
> 
> Does anyone have the feeling that we have enough to chew on 
> to justify a renumbering BOF in Prague? I'd need at least one 
> significant topic to discuss, and a volunteer to produce a 
> draft in the near future - the ADs are unlikely to approve a 
> BOF without any sign of a draft.
> 
> So far, our discussions have been a bit discursive, apart 
> from Fred's proposal to develop a management model for site 
> renumbering:
> http://www.ietf.org/mail-archive/web/renum/current/msg00035.html
> 
> Are we interested in developing such an approach? If so, 
> there isn't much time to do so:
> 
> 2011-01-31 (Monday): Cutoff date for BOF proposal requests to 
> Area Directors at 17:00 PT
> 
> --
> Regards
>    Brian Carpenter
> 
> 
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum


From fred@cisco.com  Wed Jan  5 17:34:04 2011
Return-Path: <fred@cisco.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 BD04F3A6BB4 for <renum@core3.amsl.com>; Wed,  5 Jan 2011 17:34:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.446
X-Spam-Level: 
X-Spam-Status: No, score=-110.446 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 BtWKeY-53Gzh for <renum@core3.amsl.com>; Wed,  5 Jan 2011 17:34:03 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 61AB23A67D4 for <renum@ietf.org>; Wed,  5 Jan 2011 17:34:03 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAE+rJE2rR7H+/2dsb2JhbACkHHOmQJg4hUwEhGiGIoMf
X-IronPort-AV: E=Sophos;i="4.60,280,1291593600"; d="scan'208";a="310892408"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-5.cisco.com with ESMTP; 06 Jan 2011 01:35:36 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p061ZV8b007759; Thu, 6 Jan 2011 01:35:35 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Wed, 05 Jan 2011 17:35:36 -0800
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Wed, 05 Jan 2011 17:35:36 -0800
Mime-Version: 1.0 (Apple Message framework v1082)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <003401cbad3c$f2d501c0$3a626e0a@china.huawei.com>
Date: Wed, 5 Jan 2011 17:35:21 -0800
Message-Id: <A77D5E45-907F-48AE-958E-6FB697A0347E@cisco.com>
References: <003401cbad3c$f2d501c0$3a626e0a@china.huawei.com>
To: Sheng Jiang <shengjiang@huawei.com>
X-Mailer: Apple Mail (2.1082)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: renum@ietf.org
Subject: Re: [renum] Renumbering BOF?
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: Thu, 06 Jan 2011 01:34:04 -0000

I'm up for a BOF.

On Jan 5, 2011, at 4:59 PM, Sheng Jiang wrote:

> Hi, Brian,
>=20
> We are already starting to work on a problem statement draft. It =
should be possible to submit a
> primary version by the end of this month. Of course, we would like to =
work with you and anybody
> interested.
>=20
> Now, the first important question is what kind of direction we want to =
choice, or we just list all
> of possibilities in the draft? Are we going to fix the current minor =
issues one by one (we have
> located several minor issues that need to modify or extend current =
protocols) or propose a big new
> model to solve most issues together? Personally, I am hesitating to =
choose the latter since it
> would be difficult to deploy such new and big mechanism in the current =
mature networks.
>=20
> Regards,
>=20
> Sheng
>=20
>> -----Original Message-----
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org]=20
>> On Behalf Of Brian E Carpenter
>> Sent: Thursday, January 06, 2011 5:33 AM
>> To: renum@ietf.org
>> Subject: [renum] Renumbering BOF?
>>=20
>> Hi,
>>=20
>> Back to work...
>>=20
>> Does anyone have the feeling that we have enough to chew on=20
>> to justify a renumbering BOF in Prague? I'd need at least one=20
>> significant topic to discuss, and a volunteer to produce a=20
>> draft in the near future - the ADs are unlikely to approve a=20
>> BOF without any sign of a draft.
>>=20
>> So far, our discussions have been a bit discursive, apart=20
>> from Fred's proposal to develop a management model for site=20
>> renumbering:
>> http://www.ietf.org/mail-archive/web/renum/current/msg00035.html
>>=20
>> Are we interested in developing such an approach? If so,=20
>> there isn't much time to do so:
>>=20
>> 2011-01-31 (Monday): Cutoff date for BOF proposal requests to=20
>> Area Directors at 17:00 PT
>>=20
>> --
>> Regards
>>   Brian Carpenter
>>=20
>>=20
>> _______________________________________________
>> renum mailing list
>> renum@ietf.org
>> https://www.ietf.org/mailman/listinfo/renum
>=20


From tvest@eyeconomics.com  Wed Jan  5 18:30:03 2011
Return-Path: <tvest@eyeconomics.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 F0ACF3A6BB4 for <renum@core3.amsl.com>; Wed,  5 Jan 2011 18:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 YMYjedbxufzZ for <renum@core3.amsl.com>; Wed,  5 Jan 2011 18:30:01 -0800 (PST)
Received: from host.isweb.net (host.isweb.net [69.167.133.234]) by core3.amsl.com (Postfix) with ESMTP id 485573A67B4 for <renum@ietf.org>; Wed,  5 Jan 2011 18:30:01 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=eyeconomics.com;  h=Received:Date:Subject:Message-ID:From:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ZGJBol7MVblHwPsAgA5Gefbl0HZO660vLX6KsEgfXviPVnq2s1AJD3yQklygD2Dh4/i65fh9Rjsw65TODAmwSxoyOwS4VwsMJ3IUHBql7ZiQ2NxDx8/pMuz/ZNHDSv8/;
Received: from m272336d0.tmodns.net ([208.54.35.39]:12357 helo=localhost) by host.isweb.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <tvest@eyeconomics.com>) id 1Pafdz-0001Kn-12; Wed, 05 Jan 2011 18:32:03 -0800
Date: Wed, 05 Jan 2011 21:31:56 -0500
Message-ID: <xv3otgl9hlu48aq96y2kvur0.1294281115574@email.android.com>
From: " " <tvest@eyeconomics.com>
To: Fred Baker <fred@cisco.com>, Sheng Jiang <shengjiang@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.isweb.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - eyeconomics.com
Cc: renum@ietf.org
Subject: Re: [renum] Renumbering BOF?
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: Thu, 06 Jan 2011 02:30:03 -0000

CgpGcmVkIEJha2VyIDxmcmVkQGNpc2NvLmNvbT4gd3JvdGU6Cgo+SSdtIHVwIGZvciBhIEJPRi4K
Pgo+T24gSmFuIDUsIDIwMTEsIGF0IDQ6NTkgUE0sIFNoZW5nIEppYW5nIHdyb3RlOgo+Cj4+IEhp
LCBCcmlhbiwKPj4gCj4+IFdlIGFyZSBhbHJlYWR5IHN0YXJ0aW5nIHRvIHdvcmsgb24gYSBwcm9i
bGVtIHN0YXRlbWVudCBkcmFmdC4gSXQgc2hvdWxkIGJlIHBvc3NpYmxlIHRvIHN1Ym1pdCBhCj4+
IHByaW1hcnkgdmVyc2lvbiBieSB0aGUgZW5kIG9mIHRoaXMgbW9udGguIE9mIGNvdXJzZSwgd2Ug
d291bGQgbGlrZSB0byB3b3JrIHdpdGggeW91IGFuZCBhbnlib2R5Cj4+IGludGVyZXN0ZWQuCj4+
IAo+PiBOb3csIHRoZSBmaXJzdCBpbXBvcnRhbnQgcXVlc3Rpb24gaXMgd2hhdCBraW5kIG9mIGRp
cmVjdGlvbiB3ZSB3YW50IHRvIGNob2ljZSwgb3Igd2UganVzdCBsaXN0IGFsbAo+PiBvZiBwb3Nz
aWJpbGl0aWVzIGluIHRoZSBkcmFmdD8gQXJlIHdlIGdvaW5nIHRvIGZpeCB0aGUgY3VycmVudCBt
aW5vciBpc3N1ZXMgb25lIGJ5IG9uZSAod2UgaGF2ZQo+PiBsb2NhdGVkIHNldmVyYWwgbWlub3Ig
aXNzdWVzIHRoYXQgbmVlZCB0byBtb2RpZnkgb3IgZXh0ZW5kIGN1cnJlbnQgcHJvdG9jb2xzKSBv
ciBwcm9wb3NlIGEgYmlnIG5ldwo+PiBtb2RlbCB0byBzb2x2ZSBtb3N0IGlzc3VlcyB0b2dldGhl
cj8gUGVyc29uYWxseSwgSSBhbSBoZXNpdGF0aW5nIHRvIGNob29zZSB0aGUgbGF0dGVyIHNpbmNl
IGl0Cj4+IHdvdWxkIGJlIGRpZmZpY3VsdCB0byBkZXBsb3kgc3VjaCBuZXcgYW5kIGJpZyBtZWNo
YW5pc20gaW4gdGhlIGN1cnJlbnQgbWF0dXJlIG5ldHdvcmtzLgo+PiAKPj4gUmVnYXJkcywKPj4g
Cj4+IFNoZW5nCj4+IAo+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0KPj4+IEZyb206IHJl
bnVtLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpyZW51bS1ib3VuY2VzQGlldGYub3JnXSAKPj4+
IE9uIEJlaGFsZiBPZiBCcmlhbiBFIENhcnBlbnRlcgo+Pj4gU2VudDogVGh1cnNkYXksIEphbnVh
cnkgMDYsIDIwMTEgNTozMyBBTQo+Pj4gVG86IHJlbnVtQGlldGYub3JnCj4+PiBTdWJqZWN0OiBb
cmVudW1dIFJlbnVtYmVyaW5nIEJPRj8KPj4+IAo+Pj4gSGksCj4+PiAKPj4+IEJhY2sgdG8gd29y
ay4uLgo+Pj4gCj4+PiBEb2VzIGFueW9uZSBoYXZlIHRoZSBmZWVsaW5nIHRoYXQgd2UgaGF2ZSBl
bm91Z2ggdG8gY2hldyBvbiAKPj4+IHRvIGp1c3RpZnkgYSByZW51bWJlcmluZyBCT0YgaW4gUHJh
Z3VlPyBJJ2QgbmVlZCBhdCBsZWFzdCBvbmUgCj4+PiBzaWduaWZpY2FudCB0b3BpYyB0byBkaXNj
dXNzLCBhbmQgYSB2b2x1bnRlZXIgdG8gcHJvZHVjZSBhIAo+Pj4gZHJhZnQgaW4gdGhlIG5lYXIg
ZnV0dXJlIC0gdGhlIEFEcyBhcmUgdW5saWtlbHkgdG8gYXBwcm92ZSBhIAo+Pj4gQk9GIHdpdGhv
dXQgYW55IHNpZ24gb2YgYSBkcmFmdC4KPj4+IAo+Pj4gU28gZmFyLCBvdXIgZGlzY3Vzc2lvbnMg
aGF2ZSBiZWVuIGEgYml0IGRpc2N1cnNpdmUsIGFwYXJ0IAo+Pj4gZnJvbSBGcmVkJ3MgcHJvcG9z
YWwgdG8gZGV2ZWxvcCBhIG1hbmFnZW1lbnQgbW9kZWwgZm9yIHNpdGUgCj4+PiByZW51bWJlcmlu
ZzoKPj4+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9yZW51bS9jdXJyZW50
L21zZzAwMDM1Lmh0bWwKPj4+IAo+Pj4gQXJlIHdlIGludGVyZXN0ZWQgaW4gZGV2ZWxvcGluZyBz
dWNoIGFuIGFwcHJvYWNoPyBJZiBzbywgCj4+PiB0aGVyZSBpc24ndCBtdWNoIHRpbWUgdG8gZG8g
c286Cj4+PiAKPj4+IDIwMTEtMDEtMzEgKE1vbmRheSk6IEN1dG9mZiBkYXRlIGZvciBCT0YgcHJv
cG9zYWwgcmVxdWVzdHMgdG8gCj4+PiBBcmVhIERpcmVjdG9ycyBhdCAxNzowMCBQVAo+Pj4gCj4+
PiAtLQo+Pj4gUmVnYXJkcwo+Pj4gICBCcmlhbiBDYXJwZW50ZXIKPj4+IAo+Pj4gCj4+PiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+Pj4gcmVudW0gbWFp
bGluZyBsaXN0Cj4+PiByZW51bUBpZXRmLm9yZwo+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9yZW51bQo+PiAKPgo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18KPnJlbnVtIG1haWxpbmcgbGlzdAo+cmVudW1AaWV0Zi5vcmcKPmh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcmVudW0K


From brian.e.carpenter@gmail.com  Wed Jan  5 19:35:41 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 5E65E3A6DD5 for <renum@core3.amsl.com>; Wed,  5 Jan 2011 19:35:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.393
X-Spam-Level: 
X-Spam-Status: No, score=-103.393 tagged_above=-999 required=5 tests=[AWL=0.206, 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 D2db-KEReitm for <renum@core3.amsl.com>; Wed,  5 Jan 2011 19:35:40 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id D15303A67E2 for <renum@ietf.org>; Wed,  5 Jan 2011 19:35:39 -0800 (PST)
Received: by qyk34 with SMTP id 34so18160678qyk.10 for <renum@ietf.org>; Wed, 05 Jan 2011 19:37:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=3+yDiB81uAQwhGnTE6AkSwl5z/NjUa64rVkqQiLvuWw=; b=FQe2LpztRLX1qcoaXn2NYG4sJ5Tvj+PZh6GZKfcD1aMxN69dbdG0oYLUn4YFkEMa0C 19HuJkSLM3mi9VDgw/AYCAPatlG3ASRcZy8aghshDTiWywydTjn3DzRvIQQIpx9rKB5m NW8wtRIOKB4cku2+zrEY04Uj476O61bVNwXf0=
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=FNDEnCp7aYDwnz7xGh2Nm4T/Z/WqTgfAPUF4ophMCHKa/DzMqUFZkoyyR1b/OUmprr op4JZcIJypWF9SKNod6IuKZZFP3bv5i93hsRvg2X9PxvUjMADfWBo3kXaOPHR2Bdj43A mm/eZEobY+5QlxU05KZO2euizv19kfr8Hztyk=
Received: by 10.229.233.18 with SMTP id jw18mr20589615qcb.122.1294285066503; Wed, 05 Jan 2011 19:37:46 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id s10sm12594211qco.23.2011.01.05.19.37.43 (version=SSLv3 cipher=RC4-MD5); Wed, 05 Jan 2011 19:37:45 -0800 (PST)
Message-ID: <4D2538F6.7020406@gmail.com>
Date: Thu, 06 Jan 2011 16:37:26 +1300
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: Fred Baker <fred@cisco.com>
References: <003401cbad3c$f2d501c0$3a626e0a@china.huawei.com> <A77D5E45-907F-48AE-958E-6FB697A0347E@cisco.com>
In-Reply-To: <A77D5E45-907F-48AE-958E-6FB697A0347E@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: renum@ietf.org
Subject: Re: [renum] Renumbering BOF?
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: Thu, 06 Jan 2011 03:35:41 -0000

Fred, are you up for a draft on your approach, too?

With two drafts in prospect I could make a BOF proposal,
but it will not be a WG-forming BOF, in all probability.

Regards
   Brian

On 2011-01-06 14:35, Fred Baker wrote:
> I'm up for a BOF.
> 
> On Jan 5, 2011, at 4:59 PM, Sheng Jiang wrote:
> 
>> Hi, Brian,
>>
>> We are already starting to work on a problem statement draft. It should be possible to submit a
>> primary version by the end of this month. Of course, we would like to work with you and anybody
>> interested.
>>
>> Now, the first important question is what kind of direction we want to choice, or we just list all
>> of possibilities in the draft? Are we going to fix the current minor issues one by one (we have
>> located several minor issues that need to modify or extend current protocols) or propose a big new
>> model to solve most issues together? Personally, I am hesitating to choose the latter since it
>> would be difficult to deploy such new and big mechanism in the current mature networks.
>>
>> Regards,
>>
>> Sheng
>>
>>> -----Original Message-----
>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] 
>>> On Behalf Of Brian E Carpenter
>>> Sent: Thursday, January 06, 2011 5:33 AM
>>> To: renum@ietf.org
>>> Subject: [renum] Renumbering BOF?
>>>
>>> Hi,
>>>
>>> Back to work...
>>>
>>> Does anyone have the feeling that we have enough to chew on 
>>> to justify a renumbering BOF in Prague? I'd need at least one 
>>> significant topic to discuss, and a volunteer to produce a 
>>> draft in the near future - the ADs are unlikely to approve a 
>>> BOF without any sign of a draft.
>>>
>>> So far, our discussions have been a bit discursive, apart 
>>> from Fred's proposal to develop a management model for site 
>>> renumbering:
>>> http://www.ietf.org/mail-archive/web/renum/current/msg00035.html
>>>
>>> Are we interested in developing such an approach? If so, 
>>> there isn't much time to do so:
>>>
>>> 2011-01-31 (Monday): Cutoff date for BOF proposal requests to 
>>> Area Directors at 17:00 PT
>>>
>>> --
>>> Regards
>>>   Brian Carpenter
>>>
>>>
>>> _______________________________________________
>>> renum mailing list
>>> renum@ietf.org
>>> https://www.ietf.org/mailman/listinfo/renum
> 
> 

From lear@cisco.com  Thu Jan  6 06:06:04 2011
Return-Path: <lear@cisco.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 16D533A6F02 for <renum@core3.amsl.com>; Thu,  6 Jan 2011 06:06:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.18
X-Spam-Level: 
X-Spam-Status: No, score=-110.18 tagged_above=-999 required=5 tests=[AWL=0.419, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 jtUI5ic4F8e6 for <renum@core3.amsl.com>; Thu,  6 Jan 2011 06:06:03 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 057983A6E28 for <renum@ietf.org>; Thu,  6 Jan 2011 06:06:02 -0800 (PST)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AswEAFNbJU2Q/khNgWdsb2JhbACDd6AiFQEBFiIkpSuKU40wgSGEKwSLCQ
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 06 Jan 2011 14:00:18 +0000
Received: from ams3-vpn-dhcp4836.cisco.com (ams3-vpn-dhcp4836.cisco.com [10.61.82.227]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p06E0IVt019074; Thu, 6 Jan 2011 14:00:18 GMT
Message-ID: <4D25CAFB.9010405@cisco.com>
Date: Thu, 06 Jan 2011 15:00:27 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4D24E399.8000101@gmail.com>
In-Reply-To: <4D24E399.8000101@gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: renum@ietf.org
Subject: Re: [renum] Renumbering BOF?
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: Thu, 06 Jan 2011 14:06:04 -0000

Brian,

I like the idea of having a concrete proposal that we can discuss as to
whether useful work can proceed.  I'm not sure a BoF is needed for such
a proposal, but it might be a nice forcing function to see how this
group can focus.

Eliot


On 1/5/11 10:33 PM, Brian E Carpenter wrote:
> Hi,
>
> Back to work...
>
> Does anyone have the feeling that we have enough to chew on to justify
> a renumbering BOF in Prague? I'd need at least one significant topic
> to discuss, and a volunteer to produce a draft in the near future -
> the ADs are unlikely to approve a BOF without any sign of a draft.
>
> So far, our discussions have been a bit discursive, apart from
> Fred's proposal to develop a management model for site renumbering:
> http://www.ietf.org/mail-archive/web/renum/current/msg00035.html
>
> Are we interested in developing such an approach? If so, there isn't
> much time to do so:
>
> 2011-01-31 (Monday): Cutoff date for BOF proposal requests to Area Directors at 17:00 PT
>

From tjc@ecs.soton.ac.uk  Thu Jan  6 06:16:34 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 87C1F3A6E1E for <renum@core3.amsl.com>; Thu,  6 Jan 2011 06:16:34 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599]
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 AdQGYMqmHvbT for <renum@core3.amsl.com>; Thu,  6 Jan 2011 06:16:33 -0800 (PST)
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 3CF913A6DF3 for <renum@ietf.org>; Thu,  6 Jan 2011 06:16:32 -0800 (PST)
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 p06EIVJF006808 for <renum@ietf.org>; Thu, 6 Jan 2011 14:18:31 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p06EIVJF006808
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1294323512; bh=sPv4ur3F/GDaSMCOe2Tn7gW09II=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=QWrjPvviNDC2PtgDTRTZxJ257eMgeWV0ITK7Bdbmt/D3KxcPMtTa9KI9S7iI1HGS2 cOSX+02vxprZt5SsT3fkXo+5ziNxyHaTiv4h5bBOQT7zNwEjNH0azsytxrb0mgZiuK JwjXK8K3EwB5dfTKfNNS98QaaYPR0B2NYPbCCzSQ=
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 n05EIV2308260918QG ret-id none; Thu, 06 Jan 2011 14:18:32 +0000
Received: from dhcp-152-78-94-255.ecs.soton.ac.uk (dhcp-152-78-94-255.ecs.soton.ac.uk [152.78.94.255]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p06EITPX016212 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Thu, 6 Jan 2011 14:18:29 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <4D2538F6.7020406@gmail.com>
Date: Thu, 6 Jan 2011 14:18:29 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|e31afb273ebc6fe09cc18b517a5c91b1n05EIV03tjc|ecs.soton.ac.uk|1575BF72-8EC9-43B8-9DF9-953A6100B1EB@ecs.soton.ac.uk>
References: <003401cbad3c$f2d501c0$3a626e0a@china.huawei.com> <A77D5E45-907F-48AE-958E-6FB697A0347E@cisco.com> <4D2538F6.7020406@gmail.com> <1575BF72-8EC9-43B8-9DF9-953A6100B1EB@ecs.soton.ac.uk>
To: renum@ietf.org
X-Mailer: Apple Mail (2.1082)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n05EIV230826091800; tid=n05EIV2308260918QG; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p06EIVJF006808
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [renum] Renumbering BOF?
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: Thu, 06 Jan 2011 14:16:34 -0000

I recall we tried proposing a renumbering BoF some 3 or 4 years ago, but =
there wasn't interest then.   At that time we'd had some results from =
applying Fred's RFC4192 methodology, and we had a bunch of thoughts and =
issues captured in =
http://tools.ietf.org/html/draft-chown-v6ops-renumber-thinkabout-05.   =
Since then of course we have more recent work by Brian and others.   But =
as at least part of a BoF it's definitely worth reviewing the past work, =
which of the concerns and issues are still valid, and what could/should =
be done about that.    Maybe there's piecemeal work to be done along the =
lines Sheng suggests.

I think Fred's recent post/suggestion is also certainly interesting in =
that it takes a more strategic approach; to me it's not just about =
renumbering a network, it's about numbering/provisioning its IP =
configuration in general.   A model should then allow coexistence of and =
transition between states, and support validation that processes being =
applied are producing the correct states.   Or maybe that's too broad a =
problem to consider here?

Tim

On 6 Jan 2011, at 03:37, Brian E Carpenter wrote:

> Fred, are you up for a draft on your approach, too?
>=20
> With two drafts in prospect I could make a BOF proposal,
> but it will not be a WG-forming BOF, in all probability.
>=20
> Regards
>   Brian
>=20
> On 2011-01-06 14:35, Fred Baker wrote:
>> I'm up for a BOF.
>>=20
>> On Jan 5, 2011, at 4:59 PM, Sheng Jiang wrote:
>>=20
>>> Hi, Brian,
>>>=20
>>> We are already starting to work on a problem statement draft. It =
should be possible to submit a
>>> primary version by the end of this month. Of course, we would like =
to work with you and anybody
>>> interested.
>>>=20
>>> Now, the first important question is what kind of direction we want =
to choice, or we just list all
>>> of possibilities in the draft? Are we going to fix the current minor =
issues one by one (we have
>>> located several minor issues that need to modify or extend current =
protocols) or propose a big new
>>> model to solve most issues together? Personally, I am hesitating to =
choose the latter since it
>>> would be difficult to deploy such new and big mechanism in the =
current mature networks.
>>>=20
>>> Regards,
>>>=20
>>> Sheng
>>>=20
>>>> -----Original Message-----
>>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org]=20
>>>> On Behalf Of Brian E Carpenter
>>>> Sent: Thursday, January 06, 2011 5:33 AM
>>>> To: renum@ietf.org
>>>> Subject: [renum] Renumbering BOF?
>>>>=20
>>>> Hi,
>>>>=20
>>>> Back to work...
>>>>=20
>>>> Does anyone have the feeling that we have enough to chew on=20
>>>> to justify a renumbering BOF in Prague? I'd need at least one=20
>>>> significant topic to discuss, and a volunteer to produce a=20
>>>> draft in the near future - the ADs are unlikely to approve a=20
>>>> BOF without any sign of a draft.
>>>>=20
>>>> So far, our discussions have been a bit discursive, apart=20
>>>> from Fred's proposal to develop a management model for site=20
>>>> renumbering:
>>>> http://www.ietf.org/mail-archive/web/renum/current/msg00035.html
>>>>=20
>>>> Are we interested in developing such an approach? If so,=20
>>>> there isn't much time to do so:
>>>>=20
>>>> 2011-01-31 (Monday): Cutoff date for BOF proposal requests to=20
>>>> Area Directors at 17:00 PT
>>>>=20
>>>> --
>>>> Regards
>>>>  Brian Carpenter
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> renum mailing list
>>>> renum@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/renum
>>=20
>>=20
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum


From scott.brim@gmail.com  Thu Jan  6 08:12:36 2011
Return-Path: <scott.brim@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 039193A6EFF for <renum@core3.amsl.com>; Thu,  6 Jan 2011 08:12:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.155
X-Spam-Level: 
X-Spam-Status: No, score=-103.155 tagged_above=-999 required=5 tests=[AWL=0.444, 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 I9IRcSxH1ZNI for <renum@core3.amsl.com>; Thu,  6 Jan 2011 08:12:35 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 330D73A6E25 for <renum@ietf.org>; Thu,  6 Jan 2011 08:12:35 -0800 (PST)
Received: by qwi2 with SMTP id 2so1076536qwi.31 for <renum@ietf.org>; Thu, 06 Jan 2011 08:14:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Zm5QPkmqYk7NwPIEvCjkcGWmmXBLYI4yNFzAljAurnc=; b=f8cGDgnDp5YLPgEW65pM62QUljXDt2HUFcrj5vaOLaamohl8qgWsSzhtp/L97qKH9c w1sKz8m9ZE2Zn50Bs2MJSkustcSNhXlv362bfonl3WMQw1pkCf2SuXjVdXb5ddD2OR8H Lxwau9o75T9CHJMXx2vcMLpcoCkyL8iBwvRu0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Sxd3E5IXli7WFR7MpqUludBRWmze7lz5iDfLVRCv2r9kFLdaRHFRvBhxvDgYHQzYUQ PGDosLjn6YnQte2P7z66oTSunzgsOV1Pvt22/H2QD6pp8FzYDLATuxwQsDAJHJ9DmUF8 fEXf8Uzqfvw57cqA5gxwXeC5Vc6j4oxix0pA0=
Received: by 10.224.60.211 with SMTP id q19mr23571424qah.69.1294330481583; Thu, 06 Jan 2011 08:14:41 -0800 (PST)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id e29sm14460563qck.39.2011.01.06.08.14.39 (version=SSLv3 cipher=RC4-MD5); Thu, 06 Jan 2011 08:14:40 -0800 (PST)
Message-ID: <4D25EA6E.4010603@gmail.com>
Date: Thu, 06 Jan 2011 11:14:38 -0500
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4D24E399.8000101@gmail.com>
In-Reply-To: <4D24E399.8000101@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: renum@ietf.org
Subject: Re: [renum] Renumbering BOF?
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: Thu, 06 Jan 2011 16:12:36 -0000

I'd say the only way to know if it's worth doing is to try to make it
happen.

On 01/05/2011 16:33 EST, Brian E Carpenter wrote:
> Hi,
> 
> Back to work...
> 
> Does anyone have the feeling that we have enough to chew on to justify
> a renumbering BOF in Prague? I'd need at least one significant topic
> to discuss, and a volunteer to produce a draft in the near future -
> the ADs are unlikely to approve a BOF without any sign of a draft.
> 
> So far, our discussions have been a bit discursive, apart from
> Fred's proposal to develop a management model for site renumbering:
> http://www.ietf.org/mail-archive/web/renum/current/msg00035.html
> 
> Are we interested in developing such an approach? If so, there isn't
> much time to do so:
> 
> 2011-01-31 (Monday): Cutoff date for BOF proposal requests to Area Directors at 17:00 PT
> 

From fred@cisco.com  Thu Jan  6 16:43:51 2011
Return-Path: <fred@cisco.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 3EF0E3A6F6B for <renum@core3.amsl.com>; Thu,  6 Jan 2011 16:43:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.449
X-Spam-Level: 
X-Spam-Status: No, score=-110.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 PivhrtHec+Be for <renum@core3.amsl.com>; Thu,  6 Jan 2011 16:43:50 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 732A83A6F63 for <renum@ietf.org>; Thu,  6 Jan 2011 16:43:50 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACHxJU2rR7Hu/2dsb2JhbACkH3OkfZgyhUwEhGeGIoMdiBA
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-6.cisco.com with ESMTP; 07 Jan 2011 00:45:57 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p070jp2O019577; Fri, 7 Jan 2011 00:45:56 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Thu, 06 Jan 2011 16:45:56 -0800
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Thu, 06 Jan 2011 16:45:56 -0800
Mime-Version: 1.0 (Apple Message framework v1082)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <EMEW3|e31afb273ebc6fe09cc18b517a5c91b1n05EIV03tjc|ecs.soton.ac.uk|1575BF72-8EC9-43B8-9DF9-953A6100B1EB@ecs.soton.ac.uk>
Date: Thu, 6 Jan 2011 16:45:42 -0800
Message-Id: <472D17CD-B0FC-46A0-9469-BCF8950CCE7D@cisco.com>
References: <003401cbad3c$f2d501c0$3a626e0a@china.huawei.com> <A77D5E45-907F-48AE-958E-6FB697A0347E@cisco.com> <4D2538F6.7020406@gmail.com> <1575BF72-8EC9-43B8-9DF9-953A6100B1EB@ecs.soton.ac.uk> <EMEW3|e31afb273ebc6fe09cc18b517a5c91b1n05EIV03tjc|ecs.soton.ac.uk|1575BF72-8EC9-43B8-9DF9-953A6100B1EB@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1082)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: renum@ietf.org
Subject: Re: [renum] Renumbering BOF?
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: Fri, 07 Jan 2011 00:43:51 -0000

On Jan 6, 2011, at 6:18 AM, Tim Chown wrote:

> I think Fred's recent post/suggestion is also certainly interesting in =
that it takes a more strategic approach; to me it's not just about =
renumbering a network, it's about numbering/provisioning its IP =
configuration in general.   A model should then allow coexistence of and =
transition between states, and support validation that processes being =
applied are producing the correct states.   Or maybe that's too broad a =
problem to consider here?

That's more or less what I was getting at, and I'll argue that =
provisioning addresses is part of "provisioning". I'm quite happy to =
design some sort of schema that allows for address management. Care to =
collaborate?=

From shengjiang@huawei.com  Thu Jan  6 19:13:50 2011
Return-Path: <shengjiang@huawei.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 82C323A6E28 for <renum@core3.amsl.com>; Thu,  6 Jan 2011 19:13:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.684
X-Spam-Level: 
X-Spam-Status: No, score=-3.684 tagged_above=-999 required=5 tests=[AWL=0.811,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.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 edx+A1iLcXtz for <renum@core3.amsl.com>; Thu,  6 Jan 2011 19:13:49 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 220BD3A6DF7 for <renum@ietf.org>; Thu,  6 Jan 2011 19:13:49 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEM00HKAUDXCV@szxga04-in.huawei.com> for renum@ietf.org; Fri, 07 Jan 2011 11:15:34 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEM00B7KUDXZO@szxga04-in.huawei.com> for renum@ietf.org; Fri, 07 Jan 2011 11:15:33 +0800 (CST)
Received: from j66104a ([10.110.98.58]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LEM005D7UDXGU@szxml04-in.huawei.com> for renum@ietf.org; Fri, 07 Jan 2011 11:15:33 +0800 (CST)
Date: Fri, 07 Jan 2011 11:15:31 +0800
From: Sheng Jiang <shengjiang@huawei.com>
In-reply-to: <EMEW3|e31afb273ebc6fe09cc18b517a5c91b1n05EIV03tjc|ecs.soton.ac.uk|1575BF72-8EC9-43B8-9DF9-953A6100B1EB@ecs.soton.ac.uk>
To: 'Tim Chown' <tjc@ecs.soton.ac.uk>, renum@ietf.org
Message-id: <002801cbae19$244ecab0$3a626e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcutrKLys6oEq0EVRcunrRXQREC6uAAawfIg
Subject: Re: [renum] Renumbering BOF?
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: Fri, 07 Jan 2011 03:13:50 -0000

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] 
> On Behalf Of Tim Chown
> Sent: Thursday, January 06, 2011 10:18 PM
> To: renum@ietf.org
> Subject: Re: [renum] Renumbering BOF?
> 
> I recall we tried proposing a renumbering BoF some 3 or 4 
> years ago, but there wasn't interest then.   At that time 
> we'd had some results from applying Fred's RFC4192 
> methodology, and we had a bunch of thoughts and issues 
> captured in 
> http://tools.ietf.org/html/draft-chown-v6ops-renumber-thinkabo
> ut-05.   Since then of course we have more recent work by 
> Brian and others.   But as at least part of a BoF it's 
> definitely worth reviewing the past work, which of the 
> concerns and issues are still valid, and what could/should be 
> done about that.    Maybe there's piecemeal work to be done 
> along the lines Sheng suggests.

Hi, Tim,

Thanks for your information. I just had a quick review for your draft. It contains many valuable
information. Many issues may still exist. We will re-examine these issues carefully and summary
them into our PS draft. Are you interesting to work with us on the PS draft? My plan is to produce
a very first draft by Jan 20 for a small range reviewing so that we can have a primary version
submitted this month.

Regards,

Sheng
 
> I think Fred's recent post/suggestion is also certainly 
> interesting in that it takes a more strategic approach; to me 
> it's not just about renumbering a network, it's about 
> numbering/provisioning its IP configuration in general.   A 
> model should then allow coexistence of and transition between 
> states, and support validation that processes being applied 
> are producing the correct states.   Or maybe that's too broad 
> a problem to consider here?
> 
> Tim
> 
> On 6 Jan 2011, at 03:37, Brian E Carpenter wrote:
> 
> > Fred, are you up for a draft on your approach, too?
> > 
> > With two drafts in prospect I could make a BOF proposal, 
> but it will 
> > not be a WG-forming BOF, in all probability.
> > 
> > Regards
> >   Brian
> > 
> > On 2011-01-06 14:35, Fred Baker wrote:
> >> I'm up for a BOF.
> >> 
> >> On Jan 5, 2011, at 4:59 PM, Sheng Jiang wrote:
> >> 
> >>> Hi, Brian,
> >>> 
> >>> We are already starting to work on a problem statement draft. It 
> >>> should be possible to submit a primary version by the end of this 
> >>> month. Of course, we would like to work with you and 
> anybody interested.
> >>> 
> >>> Now, the first important question is what kind of 
> direction we want 
> >>> to choice, or we just list all of possibilities in the 
> draft? Are we 
> >>> going to fix the current minor issues one by one (we have located 
> >>> several minor issues that need to modify or extend current 
> >>> protocols) or propose a big new model to solve most 
> issues together? Personally, I am hesitating to choose the 
> latter since it would be difficult to deploy such new and big 
> mechanism in the current mature networks.
> >>> 
> >>> Regards,
> >>> 
> >>> Sheng
> >>> 
> >>>> -----Original Message-----
> >>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On 
> >>>> Behalf Of Brian E Carpenter
> >>>> Sent: Thursday, January 06, 2011 5:33 AM
> >>>> To: renum@ietf.org
> >>>> Subject: [renum] Renumbering BOF?
> >>>> 
> >>>> Hi,
> >>>> 
> >>>> Back to work...
> >>>> 
> >>>> Does anyone have the feeling that we have enough to chew on to 
> >>>> justify a renumbering BOF in Prague? I'd need at least one 
> >>>> significant topic to discuss, and a volunteer to produce 
> a draft in 
> >>>> the near future - the ADs are unlikely to approve a BOF 
> without any 
> >>>> sign of a draft.
> >>>> 
> >>>> So far, our discussions have been a bit discursive, apart from 
> >>>> Fred's proposal to develop a management model for site
> >>>> renumbering:
> >>>> http://www.ietf.org/mail-archive/web/renum/current/msg00035.html
> >>>> 
> >>>> Are we interested in developing such an approach? If so, there 
> >>>> isn't much time to do so:
> >>>> 
> >>>> 2011-01-31 (Monday): Cutoff date for BOF proposal 
> requests to Area 
> >>>> Directors at 17:00 PT
> >>>> 
> >>>> --
> >>>> Regards
> >>>>  Brian Carpenter
> >>>> 
> >>>> 
> >>>> _______________________________________________
> >>>> 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 brian.e.carpenter@gmail.com  Sun Jan 23 11:44:49 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 280C03A6967 for <renum@core3.amsl.com>; Sun, 23 Jan 2011 11:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.448
X-Spam-Level: 
X-Spam-Status: No, score=-103.448 tagged_above=-999 required=5 tests=[AWL=0.151, 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 7Y+sdyGg-JbL for <renum@core3.amsl.com>; Sun, 23 Jan 2011 11:44:48 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id BEB713A6969 for <renum@ietf.org>; Sun, 23 Jan 2011 11:44:47 -0800 (PST)
Received: by qwi2 with SMTP id 2so3549806qwi.31 for <renum@ietf.org>; Sun, 23 Jan 2011 11:47:40 -0800 (PST)
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=1FJZSQ2QZZT2sBh9kJY8YnP2wPUyugd3a0a3vNsq8l0=; b=S+K2C495duJEgsuP7lzyeNd3I852Gm6r8NDh3MvCSohfINFSv24RxoufK32BJ3pUEK dBKgpFgudsU42hcEgARAk3SPQ9fDDNmdEWaxsvP0ywT1U53LQt53BNB8ish3jX0U/Zyn m5NaxK2fckDSUjzVUwLA5Ny2rE6rzy5NdWINw=
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=F6OnFTvugR91c6VbRj5nYkTjM3837lKJ8M4JapzN7RdxImqVtPc6yPDtx6u+JETfkT 9UV2Tr0HXgwRov/6u9427pH0MPZv77mc+6pVY09mvB1mEJT2tliGTbyLKINFdPGpHHWf wND/D2tbBn32rTu5Cb14z4MLMGA0hfyqzx22M=
Received: by 10.229.193.204 with SMTP id dv12mr3018579qcb.274.1295812058392; Sun, 23 Jan 2011 11:47:38 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id nb15sm8588845qcb.2.2011.01.23.11.47.34 (version=SSLv3 cipher=RC4-MD5); Sun, 23 Jan 2011 11:47:37 -0800 (PST)
Message-ID: <4D3C85DB.3010304@gmail.com>
Date: Mon, 24 Jan 2011 08:47:39 +1300
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: Sheng Jiang <shengjiang@huawei.com>
References: <002801cbae19$244ecab0$3a626e0a@china.huawei.com>
In-Reply-To: <002801cbae19$244ecab0$3a626e0a@china.huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: renum@ietf.org
Subject: Re: [renum] Renumbering BOF?
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: Sun, 23 Jan 2011 19:44:49 -0000

Hi everybody,

FYI, to get AD support for a BOF we really, really need the two
proposed I-Ds within one week at the most.

> 1. Problem statement (Sheng Jiang, Liu Bing) - this would be more focussed
> that RFC 5887, and I expect will concentrate on IPv6.
...
 > 2. A management model for systematic renumbering (Fred Baker).


Regards
   Brian Carpenter




On 2011-01-07 16:15, Sheng Jiang wrote:
>> -----Original Message-----
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] 
>> On Behalf Of Tim Chown
>> Sent: Thursday, January 06, 2011 10:18 PM
>> To: renum@ietf.org
>> Subject: Re: [renum] Renumbering BOF?
>>
>> I recall we tried proposing a renumbering BoF some 3 or 4 
>> years ago, but there wasn't interest then.   At that time 
>> we'd had some results from applying Fred's RFC4192 
>> methodology, and we had a bunch of thoughts and issues 
>> captured in 
>> http://tools.ietf.org/html/draft-chown-v6ops-renumber-thinkabo
>> ut-05.   Since then of course we have more recent work by 
>> Brian and others.   But as at least part of a BoF it's 
>> definitely worth reviewing the past work, which of the 
>> concerns and issues are still valid, and what could/should be 
>> done about that.    Maybe there's piecemeal work to be done 
>> along the lines Sheng suggests.
> 
> Hi, Tim,
> 
> Thanks for your information. I just had a quick review for your draft. It contains many valuable
> information. Many issues may still exist. We will re-examine these issues carefully and summary
> them into our PS draft. Are you interesting to work with us on the PS draft? My plan is to produce
> a very first draft by Jan 20 for a small range reviewing so that we can have a primary version
> submitted this month.
> 
> Regards,
> 
> Sheng
>  
>> I think Fred's recent post/suggestion is also certainly 
>> interesting in that it takes a more strategic approach; to me 
>> it's not just about renumbering a network, it's about 
>> numbering/provisioning its IP configuration in general.   A 
>> model should then allow coexistence of and transition between 
>> states, and support validation that processes being applied 
>> are producing the correct states.   Or maybe that's too broad 
>> a problem to consider here?
>>
>> Tim
>>
>> On 6 Jan 2011, at 03:37, Brian E Carpenter wrote:
>>
>>> Fred, are you up for a draft on your approach, too?
>>>
>>> With two drafts in prospect I could make a BOF proposal, 
>> but it will 
>>> not be a WG-forming BOF, in all probability.
>>>
>>> Regards
>>>   Brian
>>>
>>> On 2011-01-06 14:35, Fred Baker wrote:
>>>> I'm up for a BOF.
>>>>
>>>> On Jan 5, 2011, at 4:59 PM, Sheng Jiang wrote:
>>>>
>>>>> Hi, Brian,
>>>>>
>>>>> We are already starting to work on a problem statement draft. It 
>>>>> should be possible to submit a primary version by the end of this 
>>>>> month. Of course, we would like to work with you and 
>> anybody interested.
>>>>> Now, the first important question is what kind of 
>> direction we want 
>>>>> to choice, or we just list all of possibilities in the 
>> draft? Are we 
>>>>> going to fix the current minor issues one by one (we have located 
>>>>> several minor issues that need to modify or extend current 
>>>>> protocols) or propose a big new model to solve most 
>> issues together? Personally, I am hesitating to choose the 
>> latter since it would be difficult to deploy such new and big 
>> mechanism in the current mature networks.
>>>>> Regards,
>>>>>
>>>>> Sheng
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On 
>>>>>> Behalf Of Brian E Carpenter
>>>>>> Sent: Thursday, January 06, 2011 5:33 AM
>>>>>> To: renum@ietf.org
>>>>>> Subject: [renum] Renumbering BOF?
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Back to work...
>>>>>>
>>>>>> Does anyone have the feeling that we have enough to chew on to 
>>>>>> justify a renumbering BOF in Prague? I'd need at least one 
>>>>>> significant topic to discuss, and a volunteer to produce 
>> a draft in 
>>>>>> the near future - the ADs are unlikely to approve a BOF 
>> without any 
>>>>>> sign of a draft.
>>>>>>
>>>>>> So far, our discussions have been a bit discursive, apart from 
>>>>>> Fred's proposal to develop a management model for site
>>>>>> renumbering:
>>>>>> http://www.ietf.org/mail-archive/web/renum/current/msg00035.html
>>>>>>
>>>>>> Are we interested in developing such an approach? If so, there 
>>>>>> isn't much time to do so:
>>>>>>
>>>>>> 2011-01-31 (Monday): Cutoff date for BOF proposal 
>> requests to Area 
>>>>>> Directors at 17:00 PT
>>>>>>
>>>>>> --
>>>>>> Regards
>>>>>>  Brian Carpenter
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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 shengjiang@huawei.com  Sun Jan 23 11:59:23 2011
Return-Path: <shengjiang@huawei.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 A95FE3A6968 for <renum@core3.amsl.com>; Sun, 23 Jan 2011 11:59:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fo0-lrJPpCQ7 for <renum@core3.amsl.com>; Sun, 23 Jan 2011 11:59:22 -0800 (PST)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by core3.amsl.com (Postfix) with ESMTP id 10EF33A6973 for <renum@ietf.org>; Sun, 23 Jan 2011 11:59:21 -0800 (PST)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LFH00KNZRNPJY@usaga03-in.huawei.com> for renum@ietf.org; Sun, 23 Jan 2011 14:02:13 -0600 (CST)
Received: from [192.168.1.90] (vdsl678-dia1.ce.ip-plus.net [217.193.114.170]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LFH00GTRRNKJB@usaga03-in.huawei.com> for renum@ietf.org; Sun, 23 Jan 2011 14:02:13 -0600 (CST)
Date: Mon, 24 Jan 2011 04:02:04 +0800
From: Sheng Jiang <shengjiang@huawei.com>
In-reply-to: <4D3C85DB.3010304@gmail.com>
To: renum@ietf.org
Message-id: <4D3C893C.7090604@huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; zh-CN; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
References: <002801cbae19$244ecab0$3a626e0a@china.huawei.com> <4D3C85DB.3010304@gmail.com>
Subject: Re: [renum] Renumbering BOF?
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: Sun, 23 Jan 2011 19:59:23 -0000

>> 1. Problem statement (Sheng Jiang, Liu Bing) - this would be more focussed
>> that RFC 5887, and I expect will concentrate on IPv6.

The very first version has been finished and in private reviewing. It 
would be ready for submission soon.

Sheng

> Regards
>     Brian Carpenter
>
>
>
>
> On 2011-01-07 16:15, Sheng Jiang wrote:
>>> -----Original Message-----
>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org]
>>> On Behalf Of Tim Chown
>>> Sent: Thursday, January 06, 2011 10:18 PM
>>> To: renum@ietf.org
>>> Subject: Re: [renum] Renumbering BOF?
>>>
>>> I recall we tried proposing a renumbering BoF some 3 or 4
>>> years ago, but there wasn't interest then.   At that time
>>> we'd had some results from applying Fred's RFC4192
>>> methodology, and we had a bunch of thoughts and issues
>>> captured in
>>> http://tools.ietf.org/html/draft-chown-v6ops-renumber-thinkabo
>>> ut-05.   Since then of course we have more recent work by
>>> Brian and others.   But as at least part of a BoF it's
>>> definitely worth reviewing the past work, which of the
>>> concerns and issues are still valid, and what could/should be
>>> done about that.    Maybe there's piecemeal work to be done
>>> along the lines Sheng suggests.
>>
>> Hi, Tim,
>>
>> Thanks for your information. I just had a quick review for your draft. It contains many valuable
>> information. Many issues may still exist. We will re-examine these issues carefully and summary
>> them into our PS draft. Are you interesting to work with us on the PS draft? My plan is to produce
>> a very first draft by Jan 20 for a small range reviewing so that we can have a primary version
>> submitted this month.
>>
>> Regards,
>>
>> Sheng
>>
>>> I think Fred's recent post/suggestion is also certainly
>>> interesting in that it takes a more strategic approach; to me
>>> it's not just about renumbering a network, it's about
>>> numbering/provisioning its IP configuration in general.   A
>>> model should then allow coexistence of and transition between
>>> states, and support validation that processes being applied
>>> are producing the correct states.   Or maybe that's too broad
>>> a problem to consider here?
>>>
>>> Tim
>>>
>>> On 6 Jan 2011, at 03:37, Brian E Carpenter wrote:
>>>
>>>> Fred, are you up for a draft on your approach, too?
>>>>
>>>> With two drafts in prospect I could make a BOF proposal,
>>> but it will
>>>> not be a WG-forming BOF, in all probability.
>>>>
>>>> Regards
>>>>    Brian
>>>>
>>>> On 2011-01-06 14:35, Fred Baker wrote:
>>>>> I'm up for a BOF.
>>>>>
>>>>> On Jan 5, 2011, at 4:59 PM, Sheng Jiang wrote:
>>>>>
>>>>>> Hi, Brian,
>>>>>>
>>>>>> We are already starting to work on a problem statement draft. It
>>>>>> should be possible to submit a primary version by the end of this
>>>>>> month. Of course, we would like to work with you and
>>> anybody interested.
>>>>>> Now, the first important question is what kind of
>>> direction we want
>>>>>> to choice, or we just list all of possibilities in the
>>> draft? Are we
>>>>>> going to fix the current minor issues one by one (we have located
>>>>>> several minor issues that need to modify or extend current
>>>>>> protocols) or propose a big new model to solve most
>>> issues together? Personally, I am hesitating to choose the
>>> latter since it would be difficult to deploy such new and big
>>> mechanism in the current mature networks.
>>>>>> Regards,
>>>>>>
>>>>>> Sheng
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On
>>>>>>> Behalf Of Brian E Carpenter
>>>>>>> Sent: Thursday, January 06, 2011 5:33 AM
>>>>>>> To: renum@ietf.org
>>>>>>> Subject: [renum] Renumbering BOF?
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Back to work...
>>>>>>>
>>>>>>> Does anyone have the feeling that we have enough to chew on to
>>>>>>> justify a renumbering BOF in Prague? I'd need at least one
>>>>>>> significant topic to discuss, and a volunteer to produce
>>> a draft in
>>>>>>> the near future - the ADs are unlikely to approve a BOF
>>> without any
>>>>>>> sign of a draft.
>>>>>>>
>>>>>>> So far, our discussions have been a bit discursive, apart from
>>>>>>> Fred's proposal to develop a management model for site
>>>>>>> renumbering:
>>>>>>> http://www.ietf.org/mail-archive/web/renum/current/msg00035.html
>>>>>>>
>>>>>>> Are we interested in developing such an approach? If so, there
>>>>>>> isn't much time to do so:
>>>>>>>
>>>>>>> 2011-01-31 (Monday): Cutoff date for BOF proposal
>>> requests to Area
>>>>>>> Directors at 17:00 PT
>>>>>>>
>>>>>>> --
>>>>>>> Regards
>>>>>>>   Brian Carpenter
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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 rdroms.ietf@gmail.com  Wed Jan 26 01:08:04 2011
Return-Path: <rdroms.ietf@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 E0F693A6958 for <renum@core3.amsl.com>; Wed, 26 Jan 2011 01:08:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.379
X-Spam-Level: 
X-Spam-Status: No, score=-103.379 tagged_above=-999 required=5 tests=[AWL=0.220, 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 tPLXGDNPwW0U for <renum@core3.amsl.com>; Wed, 26 Jan 2011 01:08:03 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 8C4ED3A63D2 for <renum@ietf.org>; Wed, 26 Jan 2011 01:08:03 -0800 (PST)
Received: by iwn40 with SMTP id 40so729225iwn.31 for <renum@ietf.org>; Wed, 26 Jan 2011 01:11:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=zwK3Yue07IdaeVjd+5Y5iVCrH+WxSF14aw0uOvpOOyc=; b=qiLcvAA9DzEqhVazZtOTT0okH/au/C2uYq1l2Jh5lCvUTUFSA9+TwVH8yC9VguSy/o R6Bl89PwfuajdE0D/kwdSuSKT0ZND5RkJB2y9QfHloWUgsetWK2VydhWCr4xeIyr3kdK pBsnG8g+7RqlGURpgTglM6U7q9q8OLAzvXl6c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=ttQNcoEq+WfguMPzg3Xh6Iitg8VYYjMj1L6aecQYocduV3/ag7oieHzYGi5skpXCVb /PDa/oF8U2baeeLLDtCsThVy7koRRgslHwnbVzQ7rXCO8pQmxEXod9PmHBbCjUg3xd8A VAvE4zIJtf18e8/fj0Qv5e8IWaddd2qT6GwuE=
Received: by 10.42.222.66 with SMTP id if2mr75571icb.487.1296033062021; Wed, 26 Jan 2011 01:11:02 -0800 (PST)
Received: from sjc-vpnasa-303.cisco.com (128-107-239-233.cisco.com [128.107.239.233]) by mx.google.com with ESMTPS id jv9sm11452882icb.13.2011.01.26.01.10.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 26 Jan 2011 01:11:00 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <4D3C893C.7090604@huawei.com>
Date: Wed, 26 Jan 2011 10:10:46 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4DBD7F89-0113-4479-9886-2F35D3BAD431@gmail.com>
References: <002801cbae19$244ecab0$3a626e0a@china.huawei.com> <4D3C85DB.3010304@gmail.com> <4D3C893C.7090604@huawei.com>
To: Sheng Jiang <shengjiang@huawei.com>
X-Mailer: Apple Mail (2.1082)
Cc: renum@ietf.org
Subject: Re: [renum] Renumbering BOF?
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: Wed, 26 Jan 2011 09:08:05 -0000

FYI, please see http://trac.tools.ietf.org/bof/trac/ and =
http://www.rfc-editor.org/rfc/rfc5434.txt for more info on proposing a =
BoF.  Note that the BoF request deadline for IETF 80 is 1/31/2011.

Seems to me there are opportunities for a WG with deliverables ranging =
from Fred's thoughts about renumbering in the abstract to addressing =
specific problems raised in docs like RFC 4192, RFC 5887, =
draft-chown-v6ops-renumber-thinkabout, =
draft-jiang-ipv6-site-renum-guideline, etc.  The problem statement might =
be borrowed almost verbatim from the introduction to RFC 5887.  The =
biggest issue I see is focusing the WG in a target-rich environment, =
balancing system design against solutions for specific renumbering =
problems.

Here is a draft of a problem statement, with acknowledgments to the =
authors of RFC 5887 for reuse of their well-drafted text:

   Renumbering, especially for medium to large sites and networks, is
   widely viewed as an expensive, painful, and error-prone process,
   and is therefore avoided by network managers as much as possible.
   Some would argue that the very design of IP addressing and routing
   makes automatic renumbering intrinsically impossible.  In fact,
   managers have an economic incentive to avoid having to renumber,
   and many have resorted to private addressing and Network Address
   Translation (NAT) as a result.  This has the highly unfortunate
   consequence that any mechanisms for managing the scaling problems
   of wide-area (BGP4) routing that require occasional or frequent
   site renumbering have been consistently dismissed as unacceptable.
   However, renumbering is sometimes unavoidable.  The <renumbering>
   working group is identifying specific renumbering problems in the
   context of system-wide renumbering and developing point solutions
   and system solutions to address those problems.

   It is certainly to be expected that as the pressure on IPv4 address
   space intensifies in the next few years, there will be many
   attempts to consolidate usage of addresses so as to avoid wastage,
   as part of the "end game" for IPv4, which necessarily requires
   renumbering of the sites involved.  However, strategically, it is
   more important to implement and deploy techniques for IPv6
   renumbering, so that as IPv6 becomes universally deployed,
   renumbering becomes viewed as a relatively routine event.  In
   particular, some mechanisms being considered to allow indefinite
   scaling of the wide-area routing system might assume site
   renumbering to be a straightforward matter.

- Ralph


On Jan 23, 2011, at 9:02 PM 1/23/11, Sheng Jiang wrote:

>>> 1. Problem statement (Sheng Jiang, Liu Bing) - this would be more =
focussed
>>> that RFC 5887, and I expect will concentrate on IPv6.
>=20
> The very first version has been finished and in private reviewing. It =
would be ready for submission soon.
>=20
> Sheng
>=20
>> Regards
>>    Brian Carpenter
>>=20
>>=20
>>=20
>>=20
>> On 2011-01-07 16:15, Sheng Jiang wrote:
>>>> -----Original Message-----
>>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org]
>>>> On Behalf Of Tim Chown
>>>> Sent: Thursday, January 06, 2011 10:18 PM
>>>> To: renum@ietf.org
>>>> Subject: Re: [renum] Renumbering BOF?
>>>>=20
>>>> I recall we tried proposing a renumbering BoF some 3 or 4
>>>> years ago, but there wasn't interest then.   At that time
>>>> we'd had some results from applying Fred's RFC4192
>>>> methodology, and we had a bunch of thoughts and issues
>>>> captured in
>>>> http://tools.ietf.org/html/draft-chown-v6ops-renumber-thinkabo
>>>> ut-05.   Since then of course we have more recent work by
>>>> Brian and others.   But as at least part of a BoF it's
>>>> definitely worth reviewing the past work, which of the
>>>> concerns and issues are still valid, and what could/should be
>>>> done about that.    Maybe there's piecemeal work to be done
>>>> along the lines Sheng suggests.
>>>=20
>>> Hi, Tim,
>>>=20
>>> Thanks for your information. I just had a quick review for your =
draft. It contains many valuable
>>> information. Many issues may still exist. We will re-examine these =
issues carefully and summary
>>> them into our PS draft. Are you interesting to work with us on the =
PS draft? My plan is to produce
>>> a very first draft by Jan 20 for a small range reviewing so that we =
can have a primary version
>>> submitted this month.
>>>=20
>>> Regards,
>>>=20
>>> Sheng
>>>=20
>>>> I think Fred's recent post/suggestion is also certainly
>>>> interesting in that it takes a more strategic approach; to me
>>>> it's not just about renumbering a network, it's about
>>>> numbering/provisioning its IP configuration in general.   A
>>>> model should then allow coexistence of and transition between
>>>> states, and support validation that processes being applied
>>>> are producing the correct states.   Or maybe that's too broad
>>>> a problem to consider here?
>>>>=20
>>>> Tim
>>>>=20
>>>> On 6 Jan 2011, at 03:37, Brian E Carpenter wrote:
>>>>=20
>>>>> Fred, are you up for a draft on your approach, too?
>>>>>=20
>>>>> With two drafts in prospect I could make a BOF proposal,
>>>> but it will
>>>>> not be a WG-forming BOF, in all probability.
>>>>>=20
>>>>> Regards
>>>>>   Brian
>>>>>=20
>>>>> On 2011-01-06 14:35, Fred Baker wrote:
>>>>>> I'm up for a BOF.
>>>>>>=20
>>>>>> On Jan 5, 2011, at 4:59 PM, Sheng Jiang wrote:
>>>>>>=20
>>>>>>> Hi, Brian,
>>>>>>>=20
>>>>>>> We are already starting to work on a problem statement draft. It
>>>>>>> should be possible to submit a primary version by the end of =
this
>>>>>>> month. Of course, we would like to work with you and
>>>> anybody interested.
>>>>>>> Now, the first important question is what kind of
>>>> direction we want
>>>>>>> to choice, or we just list all of possibilities in the
>>>> draft? Are we
>>>>>>> going to fix the current minor issues one by one (we have =
located
>>>>>>> several minor issues that need to modify or extend current
>>>>>>> protocols) or propose a big new model to solve most
>>>> issues together? Personally, I am hesitating to choose the
>>>> latter since it would be difficult to deploy such new and big
>>>> mechanism in the current mature networks.
>>>>>>> Regards,
>>>>>>>=20
>>>>>>> Sheng
>>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On
>>>>>>>> Behalf Of Brian E Carpenter
>>>>>>>> Sent: Thursday, January 06, 2011 5:33 AM
>>>>>>>> To: renum@ietf.org
>>>>>>>> Subject: [renum] Renumbering BOF?
>>>>>>>>=20
>>>>>>>> Hi,
>>>>>>>>=20
>>>>>>>> Back to work...
>>>>>>>>=20
>>>>>>>> Does anyone have the feeling that we have enough to chew on to
>>>>>>>> justify a renumbering BOF in Prague? I'd need at least one
>>>>>>>> significant topic to discuss, and a volunteer to produce
>>>> a draft in
>>>>>>>> the near future - the ADs are unlikely to approve a BOF
>>>> without any
>>>>>>>> sign of a draft.
>>>>>>>>=20
>>>>>>>> So far, our discussions have been a bit discursive, apart from
>>>>>>>> Fred's proposal to develop a management model for site
>>>>>>>> renumbering:
>>>>>>>> =
http://www.ietf.org/mail-archive/web/renum/current/msg00035.html
>>>>>>>>=20
>>>>>>>> Are we interested in developing such an approach? If so, there
>>>>>>>> isn't much time to do so:
>>>>>>>>=20
>>>>>>>> 2011-01-31 (Monday): Cutoff date for BOF proposal
>>>> requests to Area
>>>>>>>> Directors at 17:00 PT
>>>>>>>>=20
>>>>>>>> --
>>>>>>>> Regards
>>>>>>>>  Brian Carpenter
>>>>>>>>=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
>>>> _______________________________________________
>>>> renum mailing list
>>>> renum@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/renum
>>>=20
>>>=20
>>=20
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum


From shengjiang@huawei.com  Wed Jan 26 01:40:11 2011
Return-Path: <shengjiang@huawei.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 CE5263A6962 for <renum@core3.amsl.com>; Wed, 26 Jan 2011 01:40:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QSaYY+CA4O3j for <renum@core3.amsl.com>; Wed, 26 Jan 2011 01:40:11 -0800 (PST)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by core3.amsl.com (Postfix) with ESMTP id CF8253A6825 for <renum@ietf.org>; Wed, 26 Jan 2011 01:40:10 -0800 (PST)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LFM000B5IZYHF@usaga03-in.huawei.com> for renum@ietf.org; Wed, 26 Jan 2011 03:43:10 -0600 (CST)
Received: from [192.168.1.234] (vdsl678-dia1.ce.ip-plus.net [217.193.114.170]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LFM00A5PIZX9D@usaga03-in.huawei.com> for renum@ietf.org; Wed, 26 Jan 2011 03:43:10 -0600 (CST)
Date: Wed, 26 Jan 2011 17:43:05 +0800
From: Sheng Jiang <shengjiang@huawei.com>
To: renum@ietf.org
Message-id: <4D3FECA9.6060109@huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; zh-CN; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
Subject: [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: Wed, 26 Jan 2011 09:40:11 -0000

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.




From shengjiang@huawei.com  Thu Jan 27 20:18:40 2011
Return-Path: <shengjiang@huawei.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 DDDB73A6BD2 for <renum@core3.amsl.com>; Thu, 27 Jan 2011 20:18:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2QG5moo3hdMF for <renum@core3.amsl.com>; Thu, 27 Jan 2011 20:18:39 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 843CC3A6BCB for <renum@ietf.org>; Thu, 27 Jan 2011 20:18:39 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LFP000ZITG7MP@usaga01-in.huawei.com> for renum@ietf.org; Thu, 27 Jan 2011 20:21:43 -0800 (PST)
Received: from [192.168.1.200] ([221.223.116.93]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LFP007A7TG5X2@usaga01-in.huawei.com> for renum@ietf.org; Thu, 27 Jan 2011 20:21:43 -0800 (PST)
Date: Fri, 28 Jan 2011 12:21:36 +0800
From: Sheng Jiang <shengjiang@huawei.com>
In-reply-to: <4DBD7F89-0113-4479-9886-2F35D3BAD431@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Message-id: <4D424450.2000305@huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 8BIT
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; zh-CN; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
References: <002801cbae19$244ecab0$3a626e0a@china.huawei.com> <4D3C85DB.3010304@gmail.com> <4D3C893C.7090604@huawei.com> <4DBD7F89-0113-4479-9886-2F35D3BAD431@gmail.com>
Cc: renum@ietf.org
Subject: Re: [renum] Renumbering BOF?
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: Fri, 28 Jan 2011 04:18:41 -0000

Hi, Ralph,

Thanks for your email. It is really encourage. :) We are working on the 
BoF request. It will meet the deadline for sure.

Cheers,

Sheng

于 2011/1/26 17:10, Ralph Droms 写道:
> FYI, please see http://trac.tools.ietf.org/bof/trac/ and http://www.rfc-editor.org/rfc/rfc5434.txt for more info on proposing a BoF.  Note that the BoF request deadline for IETF 80 is 1/31/2011.
>
> Seems to me there are opportunities for a WG with deliverables ranging from Fred's thoughts about renumbering in the abstract to addressing specific problems raised in docs like RFC 4192, RFC 5887, draft-chown-v6ops-renumber-thinkabout, draft-jiang-ipv6-site-renum-guideline, etc.  The problem statement might be borrowed almost verbatim from the introduction to RFC 5887.  The biggest issue I see is focusing the WG in a target-rich environment, balancing system design against solutions for specific renumbering problems.
>
> Here is a draft of a problem statement, with acknowledgments to the authors of RFC 5887 for reuse of their well-drafted text:
>
>     Renumbering, especially for medium to large sites and networks, is
>     widely viewed as an expensive, painful, and error-prone process,
>     and is therefore avoided by network managers as much as possible.
>     Some would argue that the very design of IP addressing and routing
>     makes automatic renumbering intrinsically impossible.  In fact,
>     managers have an economic incentive to avoid having to renumber,
>     and many have resorted to private addressing and Network Address
>     Translation (NAT) as a result.  This has the highly unfortunate
>     consequence that any mechanisms for managing the scaling problems
>     of wide-area (BGP4) routing that require occasional or frequent
>     site renumbering have been consistently dismissed as unacceptable.
>     However, renumbering is sometimes unavoidable.  The<renumbering>
>     working group is identifying specific renumbering problems in the
>     context of system-wide renumbering and developing point solutions
>     and system solutions to address those problems.
>
>     It is certainly to be expected that as the pressure on IPv4 address
>     space intensifies in the next few years, there will be many
>     attempts to consolidate usage of addresses so as to avoid wastage,
>     as part of the "end game" for IPv4, which necessarily requires
>     renumbering of the sites involved.  However, strategically, it is
>     more important to implement and deploy techniques for IPv6
>     renumbering, so that as IPv6 becomes universally deployed,
>     renumbering becomes viewed as a relatively routine event.  In
>     particular, some mechanisms being considered to allow indefinite
>     scaling of the wide-area routing system might assume site
>     renumbering to be a straightforward matter.
>
> - Ralph
>
>
> On Jan 23, 2011, at 9:02 PM 1/23/11, Sheng Jiang wrote:
>
>>>> 1. Problem statement (Sheng Jiang, Liu Bing) - this would be more focussed
>>>> that RFC 5887, and I expect will concentrate on IPv6.
>>
>> The very first version has been finished and in private reviewing. It would be ready for submission soon.
>>
>> Sheng
>>
>>> Regards
>>>     Brian Carpenter
>>>
>>>
>>>
>>>
>>> On 2011-01-07 16:15, Sheng Jiang wrote:
>>>>> -----Original Message-----
>>>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org]
>>>>> On Behalf Of Tim Chown
>>>>> Sent: Thursday, January 06, 2011 10:18 PM
>>>>> To: renum@ietf.org
>>>>> Subject: Re: [renum] Renumbering BOF?
>>>>>
>>>>> I recall we tried proposing a renumbering BoF some 3 or 4
>>>>> years ago, but there wasn't interest then.   At that time
>>>>> we'd had some results from applying Fred's RFC4192
>>>>> methodology, and we had a bunch of thoughts and issues
>>>>> captured in
>>>>> http://tools.ietf.org/html/draft-chown-v6ops-renumber-thinkabo
>>>>> ut-05.   Since then of course we have more recent work by
>>>>> Brian and others.   But as at least part of a BoF it's
>>>>> definitely worth reviewing the past work, which of the
>>>>> concerns and issues are still valid, and what could/should be
>>>>> done about that.    Maybe there's piecemeal work to be done
>>>>> along the lines Sheng suggests.
>>>>
>>>> Hi, Tim,
>>>>
>>>> Thanks for your information. I just had a quick review for your draft. It contains many valuable
>>>> information. Many issues may still exist. We will re-examine these issues carefully and summary
>>>> them into our PS draft. Are you interesting to work with us on the PS draft? My plan is to produce
>>>> a very first draft by Jan 20 for a small range reviewing so that we can have a primary version
>>>> submitted this month.
>>>>
>>>> Regards,
>>>>
>>>> Sheng
>>>>
>>>>> I think Fred's recent post/suggestion is also certainly
>>>>> interesting in that it takes a more strategic approach; to me
>>>>> it's not just about renumbering a network, it's about
>>>>> numbering/provisioning its IP configuration in general.   A
>>>>> model should then allow coexistence of and transition between
>>>>> states, and support validation that processes being applied
>>>>> are producing the correct states.   Or maybe that's too broad
>>>>> a problem to consider here?
>>>>>
>>>>> Tim
>>>>>
>>>>> On 6 Jan 2011, at 03:37, Brian E Carpenter wrote:
>>>>>
>>>>>> Fred, are you up for a draft on your approach, too?
>>>>>>
>>>>>> With two drafts in prospect I could make a BOF proposal,
>>>>> but it will
>>>>>> not be a WG-forming BOF, in all probability.
>>>>>>
>>>>>> Regards
>>>>>>    Brian
>>>>>>
>>>>>> On 2011-01-06 14:35, Fred Baker wrote:
>>>>>>> I'm up for a BOF.
>>>>>>>
>>>>>>> On Jan 5, 2011, at 4:59 PM, Sheng Jiang wrote:
>>>>>>>
>>>>>>>> Hi, Brian,
>>>>>>>>
>>>>>>>> We are already starting to work on a problem statement draft. It
>>>>>>>> should be possible to submit a primary version by the end of this
>>>>>>>> month. Of course, we would like to work with you and
>>>>> anybody interested.
>>>>>>>> Now, the first important question is what kind of
>>>>> direction we want
>>>>>>>> to choice, or we just list all of possibilities in the
>>>>> draft? Are we
>>>>>>>> going to fix the current minor issues one by one (we have located
>>>>>>>> several minor issues that need to modify or extend current
>>>>>>>> protocols) or propose a big new model to solve most
>>>>> issues together? Personally, I am hesitating to choose the
>>>>> latter since it would be difficult to deploy such new and big
>>>>> mechanism in the current mature networks.
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Sheng
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On
>>>>>>>>> Behalf Of Brian E Carpenter
>>>>>>>>> Sent: Thursday, January 06, 2011 5:33 AM
>>>>>>>>> To: renum@ietf.org
>>>>>>>>> Subject: [renum] Renumbering BOF?
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> Back to work...
>>>>>>>>>
>>>>>>>>> Does anyone have the feeling that we have enough to chew on to
>>>>>>>>> justify a renumbering BOF in Prague? I'd need at least one
>>>>>>>>> significant topic to discuss, and a volunteer to produce
>>>>> a draft in
>>>>>>>>> the near future - the ADs are unlikely to approve a BOF
>>>>> without any
>>>>>>>>> sign of a draft.
>>>>>>>>>
>>>>>>>>> So far, our discussions have been a bit discursive, apart from
>>>>>>>>> Fred's proposal to develop a management model for site
>>>>>>>>> renumbering:
>>>>>>>>> http://www.ietf.org/mail-archive/web/renum/current/msg00035.html
>>>>>>>>>
>>>>>>>>> Are we interested in developing such an approach? If so, there
>>>>>>>>> isn't much time to do so:
>>>>>>>>>
>>>>>>>>> 2011-01-31 (Monday): Cutoff date for BOF proposal
>>>>> requests to Area
>>>>>>>>> Directors at 17:00 PT
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Regards
>>>>>>>>>   Brian Carpenter
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>
>>>>
>>>
>> _______________________________________________
>> renum mailing list
>> renum@ietf.org
>> https://www.ietf.org/mailman/listinfo/renum
>
>

From brian.e.carpenter@gmail.com  Sun Jan 30 11:42:14 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 239083A6814 for <renum@core3.amsl.com>; Sun, 30 Jan 2011 11:42:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.474
X-Spam-Level: 
X-Spam-Status: No, score=-103.474 tagged_above=-999 required=5 tests=[AWL=0.125, 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 Ej9Tf13pFK3R for <renum@core3.amsl.com>; Sun, 30 Jan 2011 11:42:12 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 9FF013A67DA for <renum@ietf.org>; Sun, 30 Jan 2011 11:42:12 -0800 (PST)
Received: by ywk9 with SMTP id 9so1978401ywk.31 for <renum@ietf.org>; Sun, 30 Jan 2011 11:45:24 -0800 (PST)
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:subject:content-type; bh=Kw9LITBX9lClRGQ6mh/9sxbEKpMWWnrBTt6TMFr07Ls=; b=HBx7YB3vo0QiTQ0qzL2LsY3flbJ7jf2A84PHB3vz7RqACQdSfEKFb6ztuFBmLeal1e t7WZdJzu7eGNTIYOwOpjP+lyGp76dO18OwnA+f9++lqBB3KnxQuc0o99Gl3rd9QF+lDi ZVttQvrVY9WLQmzP9dGig73bp5wETck++rCg0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; b=j33lNHdxwHSX/5sbhmNHgsaVM/2dQybpzORnDNKewJpTbseg/QLV+uiEv7LvW1cURd kV2eBCYDCtrgEBtAF0xLbKhS09+IZAuiMvCpCcx7MTSzGhjBRjkobaznrU3b7+qTQDF+ i1iJSBbjxRBbqzzi0TCXuPaVMCNY22+u7Jzvs=
Received: by 10.91.146.17 with SMTP id y17mr3983092agn.198.1296416722854; Sun, 30 Jan 2011 11:45:22 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id e24sm24855258ana.22.2011.01.30.11.45.20 (version=SSLv3 cipher=RC4-MD5); Sun, 30 Jan 2011 11:45:22 -0800 (PST)
Message-ID: <4D45BFCC.9010702@gmail.com>
Date: Mon, 31 Jan 2011 08:45:16 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: renum@ietf.org
Content-Type: multipart/mixed; boundary="------------040800020509060702090802"
Subject: [renum] Proposed RENUM BOF in Prague
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: Sun, 30 Jan 2011 19:42:14 -0000

This is a multi-part message in MIME format.
--------------040800020509060702090802
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi,

The deadline for BOF requests arrived rather suddenly...

The request we've submitted is attached. Apologies that we didn't
send a draft to the list - if the BOF is approved, we can tune
it, of course.

Regards
   Brian



--------------040800020509060702090802
Content-Type: text/plain;
 name="renumBOF.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="renumBOF.txt"

Qk9GIHByb3Bvc2FsIGZvciBJRVRGIDgwOiBSRU5VTSAoU2l0ZSBSZW51bWJlcmluZykNCg0K
UHJvcG9zZWQgY2hhaXJzOiBCcmlhbiBDYXJwZW50ZXIsIFNoZW5nIEppYW5nDQoNClByb3Bv
c2VkIGFyZWE6IE9wcywgYnV0IEludGVybmV0IGFsc28gcG9zc2libGUuIFRoZSByZXF1aXJl
bWVudA0KYmVsb25ncyBpbiBPcHMgYnV0IHRoZSBzb2x1dGlvbnMgbWF5IGJlbG9uZyBpbiBJ
bnRlcm5ldC4NCg0KUHJvcG9zZWQgZHVyYXRpb246IDIgaG91cnMuDQoNCkV4cGVjdGVkIGF0
ZW5kYW5jZTogMTAwDQoNCk1haWxpbmcgbGlzdDogcmVudW1AaWV0Zi5vcmcNClN1YnNjcmli
ZTogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yZW51bQ0KDQpGb2xs
b3dpbmcgYnJpZWYgZGlzY3NzaW9ucyBpbiB0aGUgT3BzIGFuZCBJbnRlcm5ldCBhcmVhIG1l
ZXRpbmdzIGluIEJlaWppbmcsDQp3ZSBoYXZlIGFib3V0IDc1IHBlb3BsZSBvbiB0aGUgcmVu
dW0gbGlzdCwgYW5kIHRoZXJlIGhhcyBiZWVuIGEgcmVhc29uYWJsZQ0KYW1vdW50IG9mIGRp
c2N1c3Npb24sIGluZGljYXRpbmcgZGVmaW5pdGUgY29tbXVuaXR5IGludGVyZXN0Lg0KDQpE
ZXNjcmlwdGlvbg0KLS0tLS0tLS0tLS0NCg0KQXMgb3V0bGluZWQgaW4gUkZDIDU4ODcsIHJl
bnVtYmVyaW5nLCBlc3BlY2lhbGx5IGZvciBtZWRpdW0gdG8gbGFyZ2UgDQpzaXRlcyBhbmQg
bmV0d29ya3MsIGlzIHZpZXdlZCBhcyBhbiBleHBlbnNpdmUsIHBhaW5mdWwsIGFuZCBlcnJv
ci1wcm9uZQ0KcHJvY2VzcywgYXZvaWRlZCBieSBuZXR3b3JrIG1hbmFnZXJzIGFzIG11Y2gg
YXMgcG9zc2libGUuIFNvbWUgd291bGQNCmFyZ3VlIHRoYXQgdGhlIHZlcnkgZGVzaWduIG9m
IElQIGFkZHJlc3NpbmcgYW5kIHJvdXRpbmcgbWFrZXMgYXV0b21hdGVkDQpyZW51bWJlcmlu
ZyBpbnRyaW5zaWNhbGx5IGltcG9zc2libGUuICBJbiBmYWN0LCBtYW5hZ2VycyBoYXZlIGFu
IGVjb25vbWljDQppbmNlbnRpdmUgdG8gYXZvaWQgaGF2aW5nIHRvIHJlbnVtYmVyLCBhbmQg
bWFueSBoYXZlIHJlc29ydGVkIHRvIHByaXZhdGUNCmFkZHJlc3NpbmcgYW5kIE5ldHdvcmsg
QWRkcmVzcyBUcmFuc2xhdGlvbiAoTkFUKSBhcyBhIHJlc3VsdC4gIFRoaXMgaGFzDQp0aGUg
Y29uc2VxdWVuY2UgdGhhdCBhbnkgbWVjaGFuaXNtcyBmb3IgbWFuYWdpbmcgdGhlIHNjYWxp
bmcgcHJvYmxlbXMNCm9mIHdpZGUtYXJlYSAoQkdQNCkgcm91dGluZyB0aGF0IHJlcXVpcmUg
c2l0ZSByZW51bWJlcmluZyBoYXZlIGJlZW4NCmRpc21pc3NlZCBhcyB1bmFjY2VwdGFibGUu
IEV2ZW4gc28sIHJlbnVtYmVyaW5nIGlzIHNvbWV0aW1lcyB1bmF2b2lkYWJsZS4gIA0KDQpJ
dCBpcyBleHBlY3RlZCB0aGF0IGFzIHRoZSBwcmVzc3VyZSBvbiBJUHY0IGFkZHJlc3Mgc3Bh
Y2UgaW50ZW5zaWZpZXMNCmluIHRoZSBuZXh0IGZldyB5ZWFycywgdGhlcmUgd2lsbCBiZSBt
YW55IGF0dGVtcHRzIHRvIGNvbnNvbGlkYXRlIHVzYWdlDQpvZiBJUHY0IGFkZHJlc3NlcyBz
byBhcyB0byBhdm9pZCB3YXN0YWdlLCB3aGljaCBuZWNlc3NhcmlseSByZXF1aXJlcw0KcmVu
dW1iZXJpbmcgb2YgdGhlIHNpdGVzIGludm9sdmVkLiAgVW5mb3J0dW5hdGVseSwgY3VycmVu
dCBJUHY0IGRlcGxveW1lbnQNCnByYWN0aWNlcyBtZWFuIHRoYXQgYXV0b21hdGluZyB0aGlz
IHByb2Nlc3MgYXBwZWFycyBleHRyZW1lbHkgZGlmZmljdWx0Lg0KSG93ZXZlciwgc3RyYXRl
Z2ljYWxseSwgaXQgaXMgbW9yZSBpbXBvcnRhbnQgdG8gaW1wbGVtZW50IGFuZCBkZXBsb3kg
DQp0ZWNobmlxdWVzIGZvciBJUHY2IHNpdGUgcmVudW1iZXJpbmcsIHNvIHRoYXQgYXMgSVB2
NiBiZWNvbWVzIHVuaXZlcnNhbGx5DQpkZXBsb3llZCwgcmVudW1iZXJpbmcgY2FuIGJlIHZp
ZXdlZCBhcyBhIHJlbGF0aXZlbHkgcm91dGluZSBldmVudC4NCg0KRm9yIHJlbnVtYmVyaW5n
IHRvIGJlY29tZSByb3V0aW5lLCBhIHN5c3RlbWF0aWMgYWRkcmVzcyBtYW5hZ2VtZW50IGFw
cHJvYWNoDQp3aWxsIGJlIGVzc2VudGlhbC4gQSBsYXJnZSBzaXRlIHdpdGggYSBzaG9ydCBw
cmVmaXggd2lsbCBiZSBkaXZpZGVkIGludG8NCnN1Ym5ldHMgd2l0aCBsb25nZXIgcHJlZml4
ZXMuIEluIHRoaXMgc2NlbmFyaW8sIHJlbnVtYmVyaW5nIG9yIHBhcnRpYWwNCnJlbnVtYmVy
aW5nIGNhbiBiZSBjb21wbGljYXRlZC4gQWdncmVnYXRpb24sIHN5bmNocm9uaXNhdGlvbiwg
Y29vcmRpbmF0aW9uLCANCmV0Yy4sIG5lZWQgdG8gYmUgY2FyZWZ1bGx5IG1hbmFnZWQuDQoN
ClRoZSB0YXNrIG9mIHRoZSBSRU5VTSB3b3JraW5nIGdyb3VwIGlzIHRvIGlkZW50aWZ5IHNw
ZWNpZmljIHJlbnVtYmVyaW5nDQpwcm9ibGVtcyBpbiB0aGUgY29udGV4dCBvZiBzaXRlLXdp
ZGUgcmVudW1iZXJpbmcsIGFuZCB0byBkZXZlbG9wIHBvaW50IHNvbHV0aW9ucw0KYW5kIHN5
c3RlbSBzb2x1dGlvbnMgdG8gYWRkcmVzcyB0aG9zZSBwcm9ibGVtcywgb3IgdG8gc3RpbXVs
YXRlIHN1Y2ggZGV2ZWxvcG1lbnQNCmluIG90aGVyIHdvcmtpbmcgZ3JvdXBzIGlmIGFwcHJv
cHJpYXRlLiBUaGUgcHJpbmNpcGFsIHRhcmdldCB3aWxsIGJlIHNvbHV0aW9ucw0KZm9yIElQ
djYsIGJ1dCBzb2x1dGlvbnMgdGhhdCBhcHBseSBlcXVhbGx5IHRvIElQdjQgbWF5IGJlIGNv
bnNpZGVyZWQuDQoNClJGQyA1ODg3IGFuZCBkcmFmdC1qaWFuZy1pcHY2LXNpdGUtcmVudW0t
Z3VpZGVsaW5lIGFyZSBzdGFydGluZyBwb2ludHMNCmZvciB0aGlzIHdvcmsuDQoNCkdvYWxz
L2RlbGl2ZXJhYmxlcw0KLS0tLS0tLS0tLS0tLS0tLS0tDQoNCkRldmVsb3AgZHJhZnQtamlh
bmctaXB2Ni1zaXRlLXJlbnVtLWd1aWRlbGluZSBhcyBhIHJvYWRtYXAgZm9yIHRoZSBXRw0K
YW5kIGZvciBpdGVtcyB0aGF0IHNob3VsZCBiZSBzcGVjaWZpZWQgYnkgb3RoZXIgV0dzLg0K
DQogLSBUaGUgcmVzdWx0IG9mIHRoaXMgd29yayB3aWxsIGJlIGEgbW9yZSBzcGVjaWZpYyBs
aXN0IG9mIGdvYWxzIGFuZCBkZWxpdmVyYWJsZXMNCg0KRGV2ZWxvcCBhIG1hbmFnZW1lbnQg
bW9kZWwgZm9yIHNpdGUgcmVudW1iZXJpbmcuDQoNCk1pbGVzdG9uZXMNCi0tLS0tLS0tLS0N
Cg0KSnVsIDIwMTEgICAgZHJhZnQtamlhbmctaXB2Ni1zaXRlLXJlbnVtLWd1aWRlbGluZSBy
ZWFkeSBmb3IgV0dMQw0KU2VwIDIwMTEgICAgZHJhZnQtamlhbmctaXB2Ni1zaXRlLXJlbnVt
LWd1aWRlbGluZSByZWFkeSBmb3IgSUVTRw0KT2N0IDIwMTEgICAgbWFuYWdlbWVudCBtb2Rl
bCByZWFkeSBmb3IgV0dMQw0KTm92IDIwMTEgICAgcmVjaGFydGVyIHdpdGggc3BlY2lmaWMg
Z29hbHMgYW5kIGRlbGl2ZXJhYmxlcw0KRGVjIDIwMTEgICAgbWFuYWdlbWVudCBtb2RlbCBy
ZWFkeSBmb3IgSUVTRw0KDQpCT0YgYWdlbmRhDQotLS0tLS0tLS0tDQoNCjAuIEFnZW5kYSBC
YXNoLCBJbnRyby4gKDUgbWluKQ0KDQoxLiBCcmllZiByZXZpZXcgb2YgUkZDIDU4ODcuICgx
MCBtaW4pDQoNCjIuIFJldmlldyBvZiBkcmFmdC1qaWFuZy1pcHY2LXNpdGUtcmVudW0tZ3Vp
ZGVsaW5lLiAoMTUgbWluKQ0KDQozLiBCcmllZiBhbm5vdW5jZW1lbnRzIG9mICJzb2x1dGlv
biBzcGFjZSIgZHJhZnRzLCBpZiBwb3N0ZWQgaW4gdGltZSAoMTAgbWluKToNCg0KMy4xLiBB
IG1hbmFnZW1lbnQgbW9kZWwgZm9yIHN5c3RlbWF0aWMgcmVudW1iZXJpbmcgKEZyZWQgQmFr
ZXIpDQozLjIuIGRyYWZ0LWJvb3QtYnJkcC1mcmFtZXdvcmsgKFRlY28gQm9vdCkNCjMuMy4g
RGlhZ25vc3RpYyBmdW5jdGlvbiBmb3IgU0xBQUMvREhDUHY2IGNvbmZsaWN0cyAoU2hlbmcg
SmlhbmcpDQoNCjQuIERpc2N1c3Npb24gb2YgZ29hbHMgYW5kIG1pbGVzdG9uZXMuICgzMCBt
aW4pDQoNCjUuIERpc2N1c3Npb24gb2YgY29uY2x1c2lvbnMgKGZ1cnRoZXIgd29yayBqdXN0
aWZpZWQ/IFdHPyBXaGljaCBhcmVhPykuICgxMCBtaW4pDQoNCg0KDQoNCg==
--------------040800020509060702090802--

From teco@inf-net.nl  Mon Jan 31 07:11:27 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 2AAB63A6BFD for <renum@core3.amsl.com>; Mon, 31 Jan 2011 07:11:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6frltjDDSJyQ for <renum@core3.amsl.com>; Mon, 31 Jan 2011 07:11:21 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id DF8333A6C12 for <renum@ietf.org>; Mon, 31 Jan 2011 07:11:19 -0800 (PST)
Received: by eyd10 with SMTP id 10so2810908eyd.31 for <renum@ietf.org>; Mon, 31 Jan 2011 07:14:33 -0800 (PST)
Received: by 10.213.21.206 with SMTP id k14mr8528589ebb.42.1296486872995; Mon, 31 Jan 2011 07:14:32 -0800 (PST)
Received: from [172.16.4.93] ([188.205.88.52]) by mx.google.com with ESMTPS id x54sm16469658eeh.23.2011.01.31.07.14.31 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 31 Jan 2011 07:14:31 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
From: Teco Boot <teco@inf-net.nl>
Date: Mon, 31 Jan 2011 16:14:30 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <093FE270-72FE-4014-AA61-E253386C0963@inf-net.nl>
References: <20110131121852.17B2D3A6BEC@core3.amsl.com>
To: renum@ietf.org
X-Mailer: Apple Mail (2.1082)
Subject: [renum] Fwd: New Version Notification for draft-boot-brdp-framework-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, 31 Jan 2011 15:11:28 -0000

Here a pointer to BRDP Framework, a Site Renumbering solution 
space proposal. This work is also related to Autoconf, 6man, 
Routing Area or others. Comments are welcome. We planned to 
subnet a -01 before Prague.

Teco & Arjen.

http://tools.ietf.org/id/draft-boot-brdp-framework

> Abstract:
> This document describes the Border Router Discovery Protocol (BRDP)
> framework.  This framework enables multi-homing for small to medium
> sites, using Provider Aggregatable IPv6 addresses.  It describes a
> mechanism for automated IP address configuration and renumbering, a
> mechanism for optimized source address selection and a new paradigm
> for packet forwarding.  The BRDP framework prevents ingress filtering
> problems with multi-homed sites and supports load-balancing for
> multi-path transport protocols.  This work also prevents routing
> scalability problems in the provider network and Internet Default
> Free Zone because small to medium multi-homed size sites would not
> need to request Provider Independent address blocks.
