
From tjc@ecs.soton.ac.uk  Wed Jun  1 04:02:59 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8940E0703 for <renum@ietfa.amsl.com>; Wed,  1 Jun 2011 04:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1UNQHxGejj1P for <renum@ietfa.amsl.com>; Wed,  1 Jun 2011 04:02:58 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id DF29AE06DE for <renum@ietf.org>; Wed,  1 Jun 2011 04:02:55 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p51B2mSS031830 for <renum@ietf.org>; Wed, 1 Jun 2011 12:02:48 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p51B2mSS031830
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1306926169; bh=5srYRHAC8I+J6dJibsTmUpxxvvg=; h=From:Subject:Date:References:To:Mime-Version; b=IEL0lQGgvW39XgmcjZDx+u3r7exllYXWRqlH/qGcqRjsGLZTB+8jFrbrDAOyoKtp1 KJbJ7jw8S+szJxhuepuniTQd3Aupv3mKJyGYRxrlULiU2LUwyeH0mR5ASi/SVYgj8+ ZARsp6AbLyROTott3AoNWHyl/mQ0s4sRtPGBAOiA=
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 n50C2m0035609355hz ret-id none; Wed, 01 Jun 2011 12:02:48 +0100
Received: from dhcp-152-78-94-254.ecs.soton.ac.uk (dhcp-152-78-94-254.ecs.soton.ac.uk [152.78.94.254]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p51B2kYU015053 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Wed, 1 Jun 2011 12:02:46 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/mixed; boundary=Apple-Mail-18-53968266
Date: Wed, 1 Jun 2011 12:02:46 +0100
References: <3BA56133-1567-4EFE-A28D-0D581A659B7D@cisco.com> <60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk>
To: renum@ietf.org
Message-ID: <EMEW3|b61efb0457d7ba5695c7b32f90e233d6n50C2m03tjc|ecs.soton.ac.uk|60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n50C2m003560935500; tid=n50C2m0035609355hz; 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: p51B2mSS031830
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: [renum] Revised 6RENUM WG proposed charter
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 11:02:59 -0000

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

Hi,

We have updated the proposed 6RENUM WG description in response to =
various comments.

Feedback on this version welcomed, particularly by those who commented =
on the previous version.

The main changes are:
- emphasis on enterprise; future solutions that apply to soho or adhoc =
may arise but are not the target of the work
- focus on two deliverables: enterprise description and gap analysis
- removal of specific work on systematic address management approach pre =
future rechartering
- pushback on milestone dates

Tim


--Apple-Mail-18-53968266
Content-Disposition: attachment;
	filename=6renum-proposal-revised.txt
Content-Type: text/plain;
	name="6renum-proposal-revised.txt"
Content-Transfer-Encoding: quoted-printable

IPv6 Enterprise Site Renumbering (6RENUM) WG
Chairs: TBD
Area Director: Ron Bonica

Mailing list Address: renum@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/renum=20
Archive: http://www.ietf.org/mail-archive/web/renum/

Description
-----------

As outlined in RFC 5887, renumbering, especially for medium to large =
sites and networks, is currently viewed as an expensive, painful, and =
error-prone process, avoided by network managers as much as possible.

As that RFC describes, there are triggers that mean some cases of =
renumbering are unavoidable, so it should be considered a given that a =
site may need partial or complete renumbering at some stage. It is thus =
important to implement and deploy techniques that facilitate simpler =
IPv6 site renumbering, so that as IPv6 becomes universally deployed, =
renumbering can be viewed as a more routine event. This includes =
consideration of how the initial assignment and subsequent management of =
address information is performed, as this will affect future renumbering =
operations.

If IPv6 site renumbering continues to be considered difficult, network =
managers will turn to PI addressing for IPv6 to attempt to minimise the =
need for future renumbering. However, widespread use of PI may create =
very serious BGP4 scaling problems. It is thus desirable to develop =
tools and practices that may make renumbering a simpler process to =
reduce demand for IPv6 PI space.

Renumbering, or partial renumbering, can be complicated in an enterprise =
site where a short prefix is divided into subnets with longer prefixes.  =
Aggregation, synchronisation, coordination, etc., need to be carefully =
managed, and the use of manually inserted address literals minimised.

Other factors such as applications binding long-term to low level IP =
addresses may add constraints to what can be realistically achieved, but =
identifying and documenting such factors is a useful objective.  In some =
scenarios, consideration may also need to be made for 'flag day' =
renumbering (in contrast to the procedure described in RFC4192).=20

The task of the 6RENUM working group is to document existing renumbering =
practices for enterprise site networks, to identify specific renumbering =
problems in the context of partial or site-wide renumbering, and to then =
recharter with a view to develop point solutions and system solutions to =
address those problems or to stimulate such development in other working =
groups as appropriate.=20

6RENUM is chartered to develop solutions for IPv6 renumbering. If the =
solutions developed are also applicable to IPv4 that will be an =
advantage, but it is not an objective of the WG to make its solutions =
more widely available than IPv6. Similarly the WG is targeting =
enterprise networks, but solutions may also be applicable to SOHO or =
other (e.g. ad-hoc) scenarios.

It may be that for site renumbering to become more routine, a systematic =
address management approach will be required. By documenting current =
practices and undertaking a gap analysis, we should become better =
informed of the requirements of such an approach. Post-analysis =
rechartering may lead to further work in this area. RFC 4192, RFC 5887, =
and draft-jiang-ipv6-site-renum-guideline are starting points for this =
work.

Goals/deliverables
------------------

The goals of the 6RENUM working group are:

1. To undertake scenario descriptions, including documentation of =
current capability inventories and existing BCPs, for enterprise =
networks, including managed and unmanaged elements. These texts should =
contribute towards a gap analysis and provide an agreed basis for =
subsequent WG rechartering towards development of solutions (which may =
be more appropriate for other WGs to undertake) and improved practices. =
Operator input will be of high value for this text.

2. To perform a gap analysis for renumbering practices, to identify =
generic issues for network design, network management, address =
management and renumbering operations. The methodology for the WG will =
be to begin building the enterprise scenario description while in =
parallel constructing an initial gap analysis drawing on existing work =
in (at least) RFC4192 and RFC5877. As the scenario text hardens, its =
contributions will be incorporated into the more detailed gap analysis, =
which can be published once the scenario text is completed. The =
deliverables are thus the scenario and gap analysis texts.

The following topics are out of scope for the working group:

1. Renumbering avoidance; this can perhaps be considered by appropriate =
IRTF groups. As documented in RFC5887, renumbering cannot be completely =
avoided. The WG is limited to dealing with how to renumber when it is =
unavoidable.

2. IPv4 renumbering. While many sites are likely to run dual-stack, IPv6 =
is the future and, especially given concerns over extensive use of IPv6 =
PI, the most appropriate place to focus effort.

3. ISP renumbering; this is potentially the most complex renumbering =
case. However, more benefit can be achieved by focusing effort on site =
renumbering. The enterprise site analysis should include the ISP's role =
in the site's renumbering events.

4. Neither SOHO nor manet networks are targeted by the WG. However, if =
solutions from the WG are applicable to those scenarios, that would be =
an advantage.

A recharter of the WG will be possible once the gap analysis and =
scenario description are completed and published. The rechartering will =
identify more specific work items within the 6RENUM WG or appropriate =
protocol WGs, and may include a proposal for work on a systematic =
address management approach.

Milestones
----------

Oct 2011 IPv6 enterprise site scenario draft ready for WG adoption
Nov 2011 Gap analysis document ready for WG adoption=20
Jun 2012 IPv6 enterprise site scenario draft ready for WGLC=20
Jul 2012 Gap analysis document ready for WGLC=20
Aug 2012 Recharter 6RENUM WG towards solution space

--Apple-Mail-18-53968266--

From rdroms.ietf@gmail.com  Wed Jun  1 11:30:15 2011
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82C3613003F for <renum@ietfa.amsl.com>; Wed,  1 Jun 2011 11:30:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.606
X-Spam-Level: 
X-Spam-Status: No, score=-103.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vs1VMo-ZByXo for <renum@ietfa.amsl.com>; Wed,  1 Jun 2011 11:30:15 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id E852313002A for <renum@ietf.org>; Wed,  1 Jun 2011 11:30:14 -0700 (PDT)
Received: by qwc23 with SMTP id 23so49133qwc.31 for <renum@ietf.org>; Wed, 01 Jun 2011 11:30:14 -0700 (PDT)
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=izOhyCnuwp7yp4r2KWX4G3IJJhPdVeMP78Co/24fR0E=; b=rtYhEvfedhItfzUBai1BPijPAyBPq1VkwdBXJBGS01hX9no5jD/gOU9ULP5T/E3ulu eTn2g+ScYK5GUDu6aJwIZHF9efW92QAjKG1BZ4ODycWWhXXeykCdFlam++eGwx201XLX ChUD2sN3jovBFizXfSM4pGeeO+SwQ5UtX9amM=
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=dJSI54TQwY7uV5Mm6F+hyDG7f4uVmtfHqlOXlYPIyTVxah6HLtZgnjjgq8NbfyvHFU cp3da2/hT3cVAzcRIrUNiO8r52oIAFKL2nTh/3UMLqDBu+igt8wMPKBODA3qCcAT3iqX 8WmvL0yrV4QgGDA7GmFsxEogS8Py94XicnFus=
Received: by 10.229.95.144 with SMTP id d16mr5518123qcn.37.1306953013293; Wed, 01 Jun 2011 11:30:13 -0700 (PDT)
Received: from [161.44.65.177] ([161.44.65.177]) by mx.google.com with ESMTPS id i34sm835716qck.7.2011.06.01.11.30.11 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 01 Jun 2011 11:30:12 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <EMEW3|b61efb0457d7ba5695c7b32f90e233d6n50C2m03tjc|ecs.soton.ac.uk|60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk>
Date: Wed, 1 Jun 2011 14:30:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E09D1DCA-A6A0-4378-9462-4C85564F2DCE@gmail.com>
References: <3BA56133-1567-4EFE-A28D-0D581A659B7D@cisco.com> <60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk> <EMEW3|b61efb0457d7ba5695c7b32f90e233d6n50C2m03tjc|ecs.soton.ac.uk|60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1084)
Cc: renum@ietf.org
Subject: Re: [renum] Revised 6RENUM WG proposed charter
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 18:30:15 -0000

I think the charter is in pretty good shape.  One small point, bordering =
on wordsmithing: delete "low level" from "low level IP addresses".

- Ralph



On Jun 1, 2011, at 7:02 AM 6/1/11, Tim Chown wrote:

> Hi,
>=20
> We have updated the proposed 6RENUM WG description in response to =
various comments.
>=20
> Feedback on this version welcomed, particularly by those who commented =
on the previous version.
>=20
> The main changes are:
> - emphasis on enterprise; future solutions that apply to soho or adhoc =
may arise but are not the target of the work
> - focus on two deliverables: enterprise description and gap analysis
> - removal of specific work on systematic address management approach =
pre future rechartering
> - pushback on milestone dates
>=20
> Tim
>=20
> =
<6renum-proposal-revised.txt>_____________________________________________=
__
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum


From brian.e.carpenter@gmail.com  Wed Jun  1 14:06:58 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61EDDE098C for <renum@ietfa.amsl.com>; Wed,  1 Jun 2011 14:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.59
X-Spam-Level: 
X-Spam-Status: No, score=-103.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2OUvGz6Q6x3Q for <renum@ietfa.amsl.com>; Wed,  1 Jun 2011 14:06:53 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id C8C17E0970 for <renum@ietf.org>; Wed,  1 Jun 2011 14:06:53 -0700 (PDT)
Received: by pzk5 with SMTP id 5so101386pzk.31 for <renum@ietf.org>; Wed, 01 Jun 2011 14:06:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7wlSkMWJZMkiLEJD4gJV83HtAkm1MDwKlpavhFf+ykU=; b=q4aaHH1f9BeEeAAd8L+CfFKOt40QSwZ0wVNQOLx1i3W6iGkOFn2mrJPNh3V4p4q9iL Wxy4kdOhcwWqYThg0UewcUoR71ezt5uTOTOtMyN8yb1r9nlrORluNTopih6zJUT2wzth LljVOAMurc7hMQ0amOj56iTd9yBL2gGcBejHw=
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=C3JocSvtXv8GvODkajAh8FnExBTO40fYc2Uy7ciSRI1AosAKWkMY/7iEaT+kF4Rg6F p1+hoDlFDGQv+jL6t8r66j3J9OG2Ef9mOwae7kywgmBtJwjQAij/YsAkKetfJ1pGi5o1 Sjjgz7gHuFybTgpHmvJ8501Pyp+lSDR/uLhGw=
Received: by 10.68.50.193 with SMTP id e1mr3038844pbo.497.1306962413205; Wed, 01 Jun 2011 14:06:53 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id m9sm16422pbd.7.2011.06.01.14.06.50 (version=SSLv3 cipher=OTHER); Wed, 01 Jun 2011 14:06:52 -0700 (PDT)
Message-ID: <4DE6A9EC.2080000@gmail.com>
Date: Thu, 02 Jun 2011 09:06:52 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
References: <3BA56133-1567-4EFE-A28D-0D581A659B7D@cisco.com>	<60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk>	<EMEW3|b61efb0457d7ba5695c7b32f90e233d6n50C2m03tjc|ecs.soton.ac.uk|60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk> <E09D1DCA-A6A0-4378-9462-4C85564F2DCE@gmail.com>
In-Reply-To: <E09D1DCA-A6A0-4378-9462-4C85564F2DCE@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: renum@ietf.org
Subject: Re: [renum] Revised 6RENUM WG proposed charter
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 21:06:58 -0000

Agreed.

Ron has warned us that time is very short before the next IETF. I suggest that
Tim sends the charter to Ron by close of business (UK time) Thursday, so that
it can go for IETF review immediately.

Regards
   Brian Carpenter

On 2011-06-02 06:30, Ralph Droms wrote:
> I think the charter is in pretty good shape.  One small point, bordering on wordsmithing: delete "low level" from "low level IP addresses".
> 
> - Ralph
> 
> 
> 
> On Jun 1, 2011, at 7:02 AM 6/1/11, Tim Chown wrote:
> 
>> Hi,
>>
>> We have updated the proposed 6RENUM WG description in response to various comments.
>>
>> Feedback on this version welcomed, particularly by those who commented on the previous version.
>>
>> The main changes are:
>> - emphasis on enterprise; future solutions that apply to soho or adhoc may arise but are not the target of the work
>> - focus on two deliverables: enterprise description and gap analysis
>> - removal of specific work on systematic address management approach pre future rechartering
>> - pushback on milestone dates
>>
>> Tim
>>
>> <6renum-proposal-revised.txt>_______________________________________________
>> 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 Jun  1 14:44:19 2011
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54E44E06E3 for <renum@ietfa.amsl.com>; Wed,  1 Jun 2011 14:44:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.299
X-Spam-Level: 
X-Spam-Status: No, score=-103.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Adef53SyRF3 for <renum@ietfa.amsl.com>; Wed,  1 Jun 2011 14:44:18 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2835AE09A6 for <renum@ietf.org>; Wed,  1 Jun 2011 14:43:49 -0700 (PDT)
Received: by qyk29 with SMTP id 29so2182402qyk.10 for <renum@ietf.org>; Wed, 01 Jun 2011 14:43:48 -0700 (PDT)
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=1EHIfvvPJtAtOYqvVfR9VQIe3n9hNdkCF4Gf3/Xygjo=; b=nJYZAxGPcxZHLlr2jNPfjtzlZPW+g0asqYQWpx/6XLMnI65Ly83oyyXf2nCLsi1o+/ cXkjuijXFdPL1PSFp+AquaIvO2dmMXTdLpma7ofsUvvx2iZmWdkbnlLgL3JfmRaZyTeo MOrpSaZO6B6ZOjse5BxyQsCR3ypmZcJAhP6ks=
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=Lb8KlPKBP3mxJ88rJCkI1EfQLwqUirFsLgnMGoXEoiYCHwbX+nSEb3pGOmDBXRpglU aB4w8o4arCN2tabFfjYgTSFQXSh3zr7+6pR1+2F8GajiynutojZdvS31/jHKyef1GrMZ TtlaSbWY4czEcyIHF7By92S7N1T6hvAoo6o7M=
Received: by 10.224.173.199 with SMTP id q7mr1257400qaz.274.1306964628508; Wed, 01 Jun 2011 14:43:48 -0700 (PDT)
Received: from bxb-rdroms-8711.cisco.com (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id f16sm932491qck.33.2011.06.01.14.43.44 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 01 Jun 2011 14:43:47 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <4DE6A9EC.2080000@gmail.com>
Date: Wed, 1 Jun 2011 17:43:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <864A2603-8A6B-4B51-AD7A-1FC3A5B96666@gmail.com>
References: <3BA56133-1567-4EFE-A28D-0D581A659B7D@cisco.com>	<60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk>	<EMEW3|b61efb0457d7ba5695c7b32f90e233d6n50C2m03tjc|ecs.soton.ac.uk|60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk> <E09D1DCA-A6A0-4378-9462-4C85564F2DCE@gmail.com> <4DE6A9EC.2080000@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1084)
Cc: renum@ietf.org
Subject: Re: [renum] Revised 6RENUM WG proposed charter
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 21:44:19 -0000

The charter is certainly ready for IETF review.  Ship it.

- Ralph

On Jun 1, 2011, at 5:06 PM 6/1/11, Brian E Carpenter wrote:

> Agreed.
>=20
> Ron has warned us that time is very short before the next IETF. I =
suggest that
> Tim sends the charter to Ron by close of business (UK time) Thursday, =
so that
> it can go for IETF review immediately.
>=20
> Regards
>   Brian Carpenter
>=20
> On 2011-06-02 06:30, Ralph Droms wrote:
>> I think the charter is in pretty good shape.  One small point, =
bordering on wordsmithing: delete "low level" from "low level IP =
addresses".
>>=20
>> - Ralph
>>=20
>>=20
>>=20
>> On Jun 1, 2011, at 7:02 AM 6/1/11, Tim Chown wrote:
>>=20
>>> Hi,
>>>=20
>>> We have updated the proposed 6RENUM WG description in response to =
various comments.
>>>=20
>>> Feedback on this version welcomed, particularly by those who =
commented on the previous version.
>>>=20
>>> The main changes are:
>>> - emphasis on enterprise; future solutions that apply to soho or =
adhoc may arise but are not the target of the work
>>> - focus on two deliverables: enterprise description and gap analysis
>>> - removal of specific work on systematic address management approach =
pre future rechartering
>>> - pushback on milestone dates
>>>=20
>>> Tim
>>>=20
>>> =
<6renum-proposal-revised.txt>_____________________________________________=
__
>>> 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
>>=20


From scott.brim@gmail.com  Thu Jun  2 04:23:39 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BAA0E06C2 for <renum@ietfa.amsl.com>; Thu,  2 Jun 2011 04:23:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.589
X-Spam-Level: 
X-Spam-Status: No, score=-103.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IdDh-p5Ev+Fp for <renum@ietfa.amsl.com>; Thu,  2 Jun 2011 04:23:38 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 88DA1E069E for <renum@ietf.org>; Thu,  2 Jun 2011 04:23:38 -0700 (PDT)
Received: by iwn39 with SMTP id 39so825268iwn.31 for <renum@ietf.org>; Thu, 02 Jun 2011 04:23:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=adanXYqvMa4sDy63TROsxUaJoWCCfjqZlkBBaMox/KE=; b=rrO0H+QYu/vPAlrleRtXTvJ7m1zvMijpE5kNK6s2lP5PyU7pt66m7Cv8DnMntJbgYA wIZregy99LNQmJtlIyLfMG4CZ4JIAPUhAbvM6X9qy4OlPzC5tzAX6rJS5VidTDfJoywu 3lHvQjFStZSIw2LLcwT+j96EId+UsiwWpjVow=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=DOpF0LmEchoS1hy3XKQyrYw8tOzoUUZqjnc6aoy2SAHngLF2IXWM/mnDvscHV9jFBG SjPTpT1ySlVgxL1AvstvQcGMjrteCiozLfXPeuu+TKb7ZB4X0J5KMARCxHfj70p4ikQi Xy7wK7j6UZXHNdyqMG60ev9l9TMhQCclX7OtA=
Received: by 10.231.1.14 with SMTP id 14mr806568ibd.13.1307013818057; Thu, 02 Jun 2011 04:23:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.19.130 with HTTP; Thu, 2 Jun 2011 04:23:18 -0700 (PDT)
In-Reply-To: <EMEW3|b61efb0457d7ba5695c7b32f90e233d6n50C2m03tjc|ecs.soton.ac.uk|60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk>
References: <3BA56133-1567-4EFE-A28D-0D581A659B7D@cisco.com> <60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk> <EMEW3|b61efb0457d7ba5695c7b32f90e233d6n50C2m03tjc|ecs.soton.ac.uk|60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 2 Jun 2011 07:23:18 -0400
Message-ID: <BANLkTinTDAiYxsBp58JHFqLOk8yTTjs9Dw@mail.gmail.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1
Cc: renum@ietf.org
Subject: Re: [renum] Revised 6RENUM WG proposed charter
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2011 11:23:39 -0000

Just a couple small things, one of which you might consider substantial:

Near the bottom of the description,

> The task of the 6RENUM working group is to ... and to then recharter

Rechartering is not a task, nor should it be a milestone.  When the WG
is nearing completion on its actual tasks, maybe the subject of
rechartering might come up.  Rechartering should not be a goal of
_this_ incarnation of the WG.  If you want this charter to include solution
consideration, include it in this incarnation's milestones, rather than
anticipating rechartering.

In the paragraph about applicability to IPv4,

> 6RENUM is chartered to develop solutions

(for IPv6 renumbering.)

No it isn't.  Just rephrase: 6RENUM is chartered to undertake scenario
descriptions and perform gap analysis for IPv6 renumbering.

Remove 'recharter' as a milestone.

... Scott

From jari.arkko@piuha.net  Thu Jun  2 06:22:14 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72108E06E3 for <renum@ietfa.amsl.com>; Thu,  2 Jun 2011 06:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.213
X-Spam-Level: 
X-Spam-Status: No, score=-102.213 tagged_above=-999 required=5 tests=[AWL=-0.214, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D1GH7K4DywAI for <renum@ietfa.amsl.com>; Thu,  2 Jun 2011 06:22:14 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id A8F60E06B0 for <renum@ietf.org>; Thu,  2 Jun 2011 06:22:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 998252CC3B for <renum@ietf.org>; Thu,  2 Jun 2011 16:22:01 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dztaqdo3E4E8 for <renum@ietf.org>; Thu,  2 Jun 2011 16:22:01 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 23F582CC4D for <renum@ietf.org>; Thu,  2 Jun 2011 16:22:01 +0300 (EEST)
Message-ID: <4DE78E78.8040507@piuha.net>
Date: Thu, 02 Jun 2011 16:22:00 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: renum@ietf.org
References: <3BA56133-1567-4EFE-A28D-0D581A659B7D@cisco.com> <60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk> <EMEW3|b61efb0457d7ba5695c7b32f90e233d6n50C2m03tjc|ecs.soton.ac.uk|60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk> <3BF526A6-0F70-4107-BFA5-3DFCD220D1EB@ecs.soton.ac.uk> <BANLkTinTDAiYxsBp58JHFqLOk8yTTjs9Dw@mail.gmail.com> <EMEW3|cd669d5e8df69a06f03bae5ffd770d4en51DeG03tjc|ecs.soton.ac.uk|3BF526A6-0F70-4107-BFA5-3DFCD220D1EB@ecs.soton.ac.uk> <BANLkTikm4B+OoKqTZZDfZnQq6znQkmEMww@mail.gmail.com>
In-Reply-To: <BANLkTikm4B+OoKqTZZDfZnQq6znQkmEMww@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [renum] Revised 6RENUM WG proposed charter
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2011 13:22:14 -0000

The new charter text looks OK to me.

Someone asked off-list what would happen if a draft were submitted 
tomorrow for some solution or improvement in the renumbering space. My 
understanding of the proposed charter for RENUM WG is that solutions are 
not yet in scope.  If its not obvious that the improvement needs to be 
done then maybe we should wait until RENUM's analysis is complete. That 
being said, I think we would of course always consider any specific 
protocol changes in 6MAN and operational procedures in V6OPS.

Jari


From tjc@ecs.soton.ac.uk  Thu Jun  2 07:05:01 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F984E06C2 for <renum@ietfa.amsl.com>; Thu,  2 Jun 2011 07:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qc7xhkqUxa0o for <renum@ietfa.amsl.com>; Thu,  2 Jun 2011 07:05:00 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id BD28BE065B for <renum@ietf.org>; Thu,  2 Jun 2011 07:04:58 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p52E4tHv029522 for <renum@ietf.org>; Thu, 2 Jun 2011 15:04:55 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p52E4tHv029522
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1307023495; bh=qh2TQNwalj/xSsyhttwb/e8sFQc=; h=From:Mime-Version:Subject:Date:In-Reply-To:To:References; b=bSIJYa/Rt5rr+n1phgJ/SrRzVzLkJeD6iqbg8V2R959aAmIsoW31Tppd0UWzOLvEY RY8dpFIHv4GddUM5QgMnbfx18JMgsOWZdhAlh/UTQI66HIKL2XwniWpClNHgxQicEb zV644nI8Dq6iKtAYwr9bIaHrL78/Px9Jxj9z58PQ=
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 n51F4y0035619039oX ret-id none; Thu, 02 Jun 2011 15:04:55 +0100
Received: from dhcp-152-78-94-254.ecs.soton.ac.uk (dhcp-152-78-94-254.ecs.soton.ac.uk [152.78.94.254]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p52E4mbO009352 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Thu, 2 Jun 2011 15:04:48 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/mixed; boundary=Apple-Mail-22-151289871
Date: Thu, 2 Jun 2011 15:04:47 +0100
In-Reply-To: <BANLkTinTDAiYxsBp58JHFqLOk8yTTjs9Dw@mail.gmail.com>
To: renum@ietf.org
References: <3BA56133-1567-4EFE-A28D-0D581A659B7D@cisco.com> <60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk> <EMEW3|b61efb0457d7ba5695c7b32f90e233d6n50C2m03tjc|ecs.soton.ac.uk|60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk> <BANLkTinTDAiYxsBp58JHFqLOk8yTTjs9Dw@mail.gmail.com> <81B13313-4EC2-45B6-A1A5-111BEF2F6BC2@ecs.soton.ac.uk>
Message-ID: <EMEW3|f8cdefb054f3f69caf31d56c7d0d7ac1n51F4y03tjc|ecs.soton.ac.uk|81B13313-4EC2-45B6-A1A5-111BEF2F6BC2@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n51F4y003561903900; tid=n51F4y0035619039oX; 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: p52E4tHv029522
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [renum] Revised 6RENUM WG proposed charter
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2011 14:05:01 -0000

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

Scott,

I have made changes to reflect Scott's input, and have changed =
'solutions' into 'outputs' in a couple of other places to further =
clarify.  The new text is attached.

Since Ralph and Jari have both stated the text appears ready for review, =
and time is pressing, I will send it to Ron shortly.

Tim

On 2 Jun 2011, at 12:23, Scott Brim wrote:

> Just a couple small things, one of which you might consider =
substantial:
>=20
> Near the bottom of the description,
>=20
>> The task of the 6RENUM working group is to ... and to then recharter
>=20
> Rechartering is not a task, nor should it be a milestone.  When the WG
> is nearing completion on its actual tasks, maybe the subject of
> rechartering might come up.  Rechartering should not be a goal of
> _this_ incarnation of the WG.  If you want this charter to include =
solution
> consideration, include it in this incarnation's milestones, rather =
than
> anticipating rechartering.
>=20
> In the paragraph about applicability to IPv4,
>=20
>> 6RENUM is chartered to develop solutions
>=20
> (for IPv6 renumbering.)
>=20
> No it isn't.  Just rephrase: 6RENUM is chartered to undertake scenario
> descriptions and perform gap analysis for IPv6 renumbering.
>=20
> Remove 'recharter' as a milestone.
>=20
> ... Scott


--Apple-Mail-22-151289871
Content-Disposition: attachment;
	filename=6renum-proposal-final.txt
Content-Type: text/plain;
	name="6renum-proposal-final.txt"
Content-Transfer-Encoding: quoted-printable

IPv6 Enterprise Site Renumbering (6RENUM) WG
Chairs: TBD
Area Director: Ron Bonica

Mailing list Address: renum@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/renum=20
Archive: http://www.ietf.org/mail-archive/web/renum/

Description
-----------

As outlined in RFC 5887, renumbering, especially for medium to large =
sites and networks, is currently viewed as an expensive, painful, and =
error-prone process, avoided by network managers as much as possible.

As that RFC describes, there are triggers that mean some cases of =
renumbering are unavoidable, so it should be considered a given that a =
site may need partial or complete renumbering at some stage. It is thus =
important to implement and deploy techniques that facilitate simpler =
IPv6 site renumbering, so that as IPv6 becomes universally deployed, =
renumbering can be viewed as a more routine event. This includes =
consideration of how the initial assignment and subsequent management of =
address information is performed, as this will affect future renumbering =
operations.

If IPv6 site renumbering continues to be considered difficult, network =
managers will turn to PI addressing for IPv6 to attempt to minimise the =
need for future renumbering. However, widespread use of PI may create =
very serious BGP4 scaling problems. It is thus desirable to develop =
tools and practices that may make renumbering a simpler process to =
reduce demand for IPv6 PI space.

Renumbering, or partial renumbering, can be complicated in an enterprise =
site where a short prefix is divided into subnets with longer prefixes.  =
Aggregation, synchronisation, coordination, etc., need to be carefully =
managed, and the use of manually inserted address literals minimised.

Other factors such as applications binding long-term to low level IP =
addresses may add constraints to what can be realistically achieved, but =
identifying and documenting such factors is a useful objective.  In some =
scenarios, consideration may also need to be made for 'flag day' =
renumbering (in contrast to the procedure described in RFC4192).=20

The task of the 6RENUM working group is to document existing renumbering =
practices for enterprise site networks and to identify specific =
renumbering problems or 'gaps' in the context of partial or site-wide =
renumbering.  Completion of these tasks should provide a basis for =
future work to identify and develop point solutions or system solutions =
to address those problems or to stimulate such development in other =
working groups as appropriate.=20

6RENUM is chartered to perform an analysis of IPv6 site renumbering. If =
the analysis leads to conclusions that are also applicable to IPv4 that =
will be an advantage, but it is not an objective of the WG to make its =
outputs more widely available than IPv6. Similarly the WG is targeting =
enterprise networks, but the analysis may also be applicable to SOHO or =
other (e.g. ad-hoc) scenarios.

It may be that for site renumbering to become more routine, a systematic =
address management approach will be required. By documenting current =
practices and undertaking a gap analysis, we should become better =
informed of the requirements of such an approach. Post-analysis =
rechartering may lead to further work in this area. RFC 4192, RFC 5887, =
and draft-jiang-ipv6-site-renum-guideline are starting points for this =
work.

Goals/deliverables
------------------

The goals of the 6RENUM working group are:

1. To undertake scenario descriptions, including documentation of =
current capability inventories and existing BCPs, for enterprise =
networks, including managed and unmanaged elements. These texts should =
contribute towards a gap analysis and provide an agreed basis for =
subsequent WG rechartering towards development of solutions (which may =
be more appropriate for other WGs to undertake) and improved practices. =
Operator input will be of high value for this text.

2. To perform a gap analysis for renumbering practices, to identify =
generic issues for network design, network management, address =
management and renumbering operations. The methodology for the WG will =
be to begin building the enterprise scenario description while in =
parallel constructing an initial gap analysis drawing on existing work =
in (at least) RFC4192 and RFC5877. As the scenario text hardens, its =
contributions will be incorporated into the more detailed gap analysis, =
which can be published once the scenario text is completed. The =
deliverables are thus the scenario and gap analysis texts.

The following topics are out of scope for the working group:

1. Renumbering avoidance; this can perhaps be considered by appropriate =
IRTF groups. As documented in RFC5887, renumbering cannot be completely =
avoided. The WG is limited to dealing with how to renumber when it is =
unavoidable.

2. IPv4 renumbering. While many sites are likely to run dual-stack, IPv6 =
is the future and, especially given concerns over extensive use of IPv6 =
PI, the most appropriate place to focus effort.

3. ISP renumbering; this is potentially the most complex renumbering =
case. However, more benefit can be achieved by focusing effort on site =
renumbering. The enterprise site analysis should include the ISP's role =
in the site's renumbering events.

4. Neither SOHO nor manet networks are targeted by the WG. However, if =
outputs from the WG are applicable to those scenarios, that would be an =
advantage.

A recharter of the WG will be possible once the gap analysis and =
scenario description are completed and published. Such rechartering =
would identify more specific work items within the 6RENUM WG or =
appropriate protocol WGs, and may include a proposal for work on a =
systematic address management approach.

Milestones
----------

Oct 2011 IPv6 enterprise site scenario draft ready for WG adoption
Nov 2011 Gap analysis document ready for WG adoption=20
Jun 2012 IPv6 enterprise site scenario draft ready for WGLC=20
Jul 2012 Gap analysis document ready for WGLC=20


--Apple-Mail-22-151289871--

From scott.brim@gmail.com  Thu Jun  2 07:22:49 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F062DE0787 for <renum@ietfa.amsl.com>; Thu,  2 Jun 2011 07:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.59
X-Spam-Level: 
X-Spam-Status: No, score=-103.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTqp2JWQhdpL for <renum@ietfa.amsl.com>; Thu,  2 Jun 2011 07:22:49 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 70B1DE0786 for <renum@ietf.org>; Thu,  2 Jun 2011 07:22:49 -0700 (PDT)
Received: by iwn39 with SMTP id 39so991148iwn.31 for <renum@ietf.org>; Thu, 02 Jun 2011 07:22:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=pucCbFGhjBQGB8boG7sacEjk+uQ6N8rcHZR1PCmJ3GM=; b=D7E4TGBQQI3EFP1LDKT11Z/Pg4kmzSAOgqviKMIfngEyXeWzskQoyOw88j1AwHnH9X wcGRP5LdANrbsNHQVRPthIn4754MJyWSz8v2fC3njxWYzAZlQHNUJT4qWSfPMnYQ8pPk ijtjcvrG7kNtQyy68I3PzGPMsmYXzBfzXt/D4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=B6jYqRNfkgndZAMcv7gjhik1jg9f9/6fQPSSUEV5Xc34qUDDFum4xg3NbIu+WkjoAI dy25Q5i9TtdLA0rTY8ckksH2PwAKQux3OWmxhqvqVF6zfJ3r2fv9IuqPT9CA94gXJCIM o/ohyX3DmpIJWfkVwLgiHZ1B/+0gDhmPvHS/E=
Received: by 10.231.68.202 with SMTP id w10mr974965ibi.63.1307024569086; Thu, 02 Jun 2011 07:22:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.19.130 with HTTP; Thu, 2 Jun 2011 07:22:29 -0700 (PDT)
In-Reply-To: <EMEW3|f8cdefb054f3f69caf31d56c7d0d7ac1n51F4y03tjc|ecs.soton.ac.uk|81B13313-4EC2-45B6-A1A5-111BEF2F6BC2@ecs.soton.ac.uk>
References: <3BA56133-1567-4EFE-A28D-0D581A659B7D@cisco.com> <60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk> <EMEW3|b61efb0457d7ba5695c7b32f90e233d6n50C2m03tjc|ecs.soton.ac.uk|60E722A9-F4F9-4D07-92DD-4B3C0FF2E559@ecs.soton.ac.uk> <81B13313-4EC2-45B6-A1A5-111BEF2F6BC2@ecs.soton.ac.uk> <BANLkTinTDAiYxsBp58JHFqLOk8yTTjs9Dw@mail.gmail.com> <EMEW3|f8cdefb054f3f69caf31d56c7d0d7ac1n51F4y03tjc|ecs.soton.ac.uk|81B13313-4EC2-45B6-A1A5-111BEF2F6BC2@ecs.soton.ac.uk>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 2 Jun 2011 10:22:29 -0400
Message-ID: <BANLkTi=-_y=PS+1dMyGqPOd-n=nc0Z8_Ng@mail.gmail.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: renum@ietf.org
Subject: Re: [renum] Revised 6RENUM WG proposed charter
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2011 14:22:50 -0000

Excellent.

On Thu, Jun 2, 2011 at 10:04, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
> Scott,
>
> I have made changes to reflect Scott's input, and have changed 'solutions=
' into 'outputs' in a couple of other places to further clarify. =A0The new=
 text is attached.
>
> Since Ralph and Jari have both stated the text appears ready for review, =
and time is pressing, I will send it to Ron shortly.
>
> Tim
>
> On 2 Jun 2011, at 12:23, Scott Brim wrote:
>
>> Just a couple small things, one of which you might consider substantial:
>>
>> Near the bottom of the description,
>>
>>> The task of the 6RENUM working group is to ... and to then recharter
>>
>> Rechartering is not a task, nor should it be a milestone. =A0When the WG
>> is nearing completion on its actual tasks, maybe the subject of
>> rechartering might come up. =A0Rechartering should not be a goal of
>> _this_ incarnation of the WG. =A0If you want this charter to include sol=
ution
>> consideration, include it in this incarnation's milestones, rather than
>> anticipating rechartering.
>>
>> In the paragraph about applicability to IPv4,
>>
>>> 6RENUM is chartered to develop solutions
>>
>> (for IPv6 renumbering.)
>>
>> No it isn't. =A0Just rephrase: 6RENUM is chartered to undertake scenario
>> descriptions and perform gap analysis for IPv6 renumbering.
>>
>> Remove 'recharter' as a milestone.
>>
>> ... Scott
>
>
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
>
>

From wwwrun@ietfa.amsl.com  Thu Jun  2 10:54:55 2011
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: renum@ietf.org
Delivered-To: renum@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id F218FE080B; Thu,  2 Jun 2011 10:54:54 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110602175454.F218FE080B@ietfa.amsl.com>
Date: Thu,  2 Jun 2011 10:54:54 -0700 (PDT)
Cc: renum@ietf.org
Subject: [renum] WG Review: IPv6 Site Renumbering (6renum)
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: iesg@ietf.org
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2011 17:54:55 -0000

A new IETF working group has been proposed in the Operations and 
Management Area.  The IESG has not made any determination as yet. The 
following draft charter was submitted, and is provided for informational 
purposes only. Please send your comments to the IESG mailing list 
(iesg@ietf.org) by Thursday, June 9, 2011                            

IPv6 Site Renumbering (6renum) 
-------------------------------
Last Modified: 2011-06-02

Current Status: Proposed Working Group

Chairs: TBD

Area Director: Ron Bonica

Mailing list
  Address: renum@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/renum
  Archive: http://www.ietf.org/mail-archive/web/renum/

Description of Working Group
-----------

As outlined in RFC 5887, renumbering, especially for medium to large 
sites and networks, is currently viewed as an expensive, painful, and 
error-prone process, avoided by network managers as much as possible. 

As IPv6 adoption begins to gather momentum, those managers may turn to
PI addressing for IPv6 to attempt to minimise the need for future 
renumbering. However, such an approach would create very serious BGP4
scaling problems if used by millions of end sites; it is thus desirable 
to develop tools, techniques and practices that may make renumbering a
simpler process, to reduce demand for IPv6 PI space. In addition, as
RFC 5887 describes, there are other triggers that mean some cases of
renumbering are unavoidable, so it should be considered a given that
a site may need partial or complete renumbering at some stage.   

Strategically it is thus important to implement and deploy techniques 
that facilitate simpler IPv6 site renumbering, so that as IPv6 becomes 
universally deployed, renumbering can be viewed as a more routine event.
This includes consideration of how the initial assignment and subsequent
management of address information is performed, as this will affect 
future renumbering operations.

For renumbering to become more routine, a systematic address management 
approach will be essential. A large site with a short prefix will be 
divided into subnets with longer prefixes. In this scenario, renumbering 
or partial renumbering can be complicated. Aggregation, synchronisation, 
coordination, etc., need to be carefully managed, and the use of 
manually inserted address literals minimised. In unmanaged scenarios, 
consideration may need to be made for 'flag day' renumbering (in 
contrast to the procedure described in RFC4192).

The task of the 6RENUM working group is to document existing renumbering
practices for managed (enterprise) and unmanaged (SOHO) networks, to 
identify specific renumbering problems in the context of site-wide 
renumbering, and to then recharter with a view to develop point 
solutions and system solutions to address those problems or to stimulate 
such development in other working groups if appropriate.  The principal 
target will be solutions for IPv6.

RFC 4192, RFC 5887, and draft-jiang-ipv6-site-renum-guideline are 
starting points for this work.

Goals/deliverables
------------------

The goals of the 6RENUM working group are:

1. To undertake scenario descriptions, including documentation of 
   current capability inventories and existing BCPs for managed 
   (enterprise) and unmanaged (SOHO) networks.  These texts should 
   contribute towards the gap analysis and provide an agreed basis for 
   subsequent WG rechartering towards development of solutions 
   (potentially in other WGs) and improved practices. Operator input 
   will be of particularly high value for this stage.

2. To examine fully automatic, self-organising networks (manet/autoconf) 
   as a possible third scenario. 

3. To perform a gap analysis for renumbering practices, drawing on RFCs
   4192 and 5887, to identify generic issues for network design, network
   management, and renumbering operations. The scenario texts will
   contribute to the analysis.

4. To document existing IP address management models and practices with
   a view to proposing (at a high level) an appropriate model to allow
   simplification of any partial or full site renumbering process
   (this would likely be applicable to managed rather than unmanaged
   scenarios).

The general methodology for the WG will be to first build managed and
unmanaged baseline scenario descriptions, while in parallel undertaking 
an initial gap analysis from existing work in (at least) RFC4192 and 
RFC5877. As the scenario texts harden, their contributions will be 
incorporated into the gap analysis, which can be published once the 
scenarios are completed.   

The following topics are out of scope for the working group:

1. Renumbering avoidance; this can perhaps be considered by appropriate 
   IRTF groups.  As documented in RFC5887, renumbering cannot be 
   completely avoided. The WG is limited to dealing with how to renumber 
   when it is unavoidable.

2. IPv4 renumbering.  While many sites are likely to run dual-stack, 
   IPv6 is the future and, especially given concerns over extensive use 
   of IPv6 PI, the most appropriate place to focus effort.

3. ISP renumbering; this is potentially the most complex renumbering 
   case.  More benefit can be achieved by focusing effort on site 
   renumbering.  The site analysis should include the ISP's role in its 
   own renumbering event.

A recharter of the WG will be possible once the gap analysis and 
scenario descriptions are completed, and the IP address management 
('numbering tool') review and (high level) proposal have been published.   
The rechartering will identify more specific work items within the 
6RENUM WG or appropriate protocol WGs. 

Milestones
----------

Aug 2011    managed (enterprise) scenario draft ready for WG adoption 
            (partly based on draft-jiang-ipv6-site-renum-guideline)

Aug 2011    unmanaged (SOHO) scenario draft ready for WG adoption

Oct 2011    gap analysis document ready for WG adoption (already some 
            considerations in RFC5887 and 
            draft-jiang-ipv6-site-renum-guideline)

Oct 2011    management model draft ready for WG adoption

Jan 2012    managed (enterprise) scenario draft ready for WGLC

Jan 2012    unmanaged (SOHO) scenario draft ready for WGLC

Feb 2012    management model ready for WGLC

Mar 2012    gap analysis document ready for WGLC

Apr 2012    recharter WG towards solution space




From scott.brim@gmail.com  Thu Jun  2 17:38:33 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84148E07F3; Thu,  2 Jun 2011 17:38:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.59
X-Spam-Level: 
X-Spam-Status: No, score=-103.59 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SR8IEiCYqyn9; Thu,  2 Jun 2011 17:38:32 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id B9170E06AB; Thu,  2 Jun 2011 17:38:32 -0700 (PDT)
Received: by iwn39 with SMTP id 39so1471968iwn.31 for <multiple recipients>; Thu, 02 Jun 2011 17:38:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=j4ZlDsbUku634CORye/XU8jhX0oZPWPMPwbNy3kTgVk=; b=wqmS7Z1KW7NcHpqSjeOGB2FXKK0Hon0dSfp84R9LxEEPBamkZQ4AFGZ04HOnX7v4+o 4/zMYeHWQTQb8BlmnkWJjgg1AtzgiJpLlHjZPy8kV+4O+JLb3fPBnZxeYnDTz6gRTgZd nfsaCw8ycraHPwfpdvoBDbFYszJLogihLeFf8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=qjjlAm3F9uGhT+oc9H54NmjL8UGK9m9Ylqp5KlFRPECoNaHmrKa/RZK0fILwq99/xH cUtVvsdlWUjUAaMxgVNTtINiBRRcdkWPXW8276//WYJcpQ9gf7Y5bJ5BSuO7IfLl5G8R WBlwoDP+UCzhNeNOa9ZseIaIWO3J8O+Gn1xFI=
MIME-Version: 1.0
Received: by 10.42.53.77 with SMTP id m13mr2390621icg.444.1307061512429; Thu, 02 Jun 2011 17:38:32 -0700 (PDT)
Received: by 10.231.19.130 with HTTP; Thu, 2 Jun 2011 17:38:32 -0700 (PDT)
Received: by 10.231.19.130 with HTTP; Thu, 2 Jun 2011 17:38:32 -0700 (PDT)
In-Reply-To: <20110602175454.F218FE080B@ietfa.amsl.com>
References: <20110602175454.F218FE080B@ietfa.amsl.com>
Date: Thu, 2 Jun 2011 20:38:32 -0400
Message-ID: <BANLkTiki=7v6quz8pRBZd8UiMuW0qRpw6Q@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
To: iesg@ietf.org
Content-Type: multipart/alternative; boundary=20cf3022392d25e00b04a4c3f946
Cc: renum@ietf.org
Subject: Re: [renum] WG Review: IPv6 Site Renumbering (6renum)
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 00:38:33 -0000

--20cf3022392d25e00b04a4c3f946
Content-Type: text/plain; charset=ISO-8859-1

In favor. The problems and tradeoffs need to be explored, analyzed and
documented.

--20cf3022392d25e00b04a4c3f946
Content-Type: text/html; charset=ISO-8859-1

<p>In favor. The problems and tradeoffs need to be explored, analyzed and documented. </p>

--20cf3022392d25e00b04a4c3f946--

From tjc@ecs.soton.ac.uk  Fri Jun  3 03:27:04 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2B3AE0729 for <renum@ietfa.amsl.com>; Fri,  3 Jun 2011 03:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.284
X-Spam-Level: 
X-Spam-Status: No, score=-2.284 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r6d9F6CoDqDh for <renum@ietfa.amsl.com>; Fri,  3 Jun 2011 03:27:02 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 51174E0720 for <renum@ietf.org>; Fri,  3 Jun 2011 03:27:00 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p53AQsBN003860 for <renum@ietf.org>; Fri, 3 Jun 2011 11:26:54 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p53AQsBN003860
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1307096814; bh=3YkYdMPDMFu3FNc6ein9t+qVOW0=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=GjMiZ3eSI+nwkneAg7Lu/O6ADyax2YJLHWVTGqAtg45pZoFS8fHdG4Vy6IjaBFnAO 3CbEnBB8VpuV4gUpfzM29QYoHI6iQyf7QQ3BINUcpnEZsykwPnDwzvKwJY+5ZeS2bH XtJcbtZmEj1magrH6O4wzG7Y95ixLb7EenMW6o54=
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 n52BQs00356245930x ret-id none; Fri, 03 Jun 2011 11:26:54 +0100
Received: from [IPv6:2001:630:d0:f105:226:8ff:fee4:215b] ([IPv6:2001:630:d0:f105:226:8ff:fee4:215b]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p53AQmgv028595 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Fri, 3 Jun 2011 11:26:49 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20110602175454.F218FE080B@ietfa.amsl.com>
Date: Fri, 3 Jun 2011 11:26:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|548ba481df1d40481ee40daf1aaa3fddn52BQs03tjc|ecs.soton.ac.uk|C3AA1194-5390-4F27-94B6-FBD7265CD1AA@ecs.soton.ac.uk>
References: <20110602175454.F218FE080B@ietfa.amsl.com> <C3AA1194-5390-4F27-94B6-FBD7265CD1AA@ecs.soton.ac.uk>
To: renum@ietf.org
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n52BQs003562459300; tid=n52BQs00356245930x; 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: p53AQsBN003860
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [renum] WG Review: IPv6 Site Renumbering (6renum)
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 10:27:04 -0000

I have alerted Ron to the fact that the old description has been used. =
The correct description, which was posted to renum yesterday after =
feedback from the list, is as follows:

IPv6 Enterprise Site Renumbering (6RENUM) WG
Chairs: TBD
Area Director: Ron Bonica

Mailing list Address: renum@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/renum=20
Archive: http://www.ietf.org/mail-archive/web/renum/

Description
-----------

As outlined in RFC 5887, renumbering, especially for medium to large =
sites and networks, is currently viewed as an expensive, painful, and =
error-prone process, avoided by network managers as much as possible.

As that RFC describes, there are triggers that mean some cases of =
renumbering are unavoidable, so it should be considered a given that a =
site may need partial or complete renumbering at some stage. It is thus =
important to implement and deploy techniques that facilitate simpler =
IPv6 site renumbering, so that as IPv6 becomes universally deployed, =
renumbering can be viewed as a more routine event. This includes =
consideration of how the initial assignment and subsequent management of =
address information is performed, as this will affect future renumbering =
operations.

If IPv6 site renumbering continues to be considered difficult, network =
managers will turn to PI addressing for IPv6 to attempt to minimise the =
need for future renumbering. However, widespread use of PI may create =
very serious BGP4 scaling problems. It is thus desirable to develop =
tools and practices that may make renumbering a simpler process to =
reduce demand for IPv6 PI space.

Renumbering, or partial renumbering, can be complicated in an enterprise =
site where a short prefix is divided into subnets with longer prefixes.  =
Aggregation, synchronisation, coordination, etc., need to be carefully =
managed, and the use of manually inserted address literals minimised.

Other factors such as applications binding long-term to low level IP =
addresses may add constraints to what can be realistically achieved, but =
identifying and documenting such factors is a useful objective.  In some =
scenarios, consideration may also need to be made for 'flag day' =
renumbering (in contrast to the procedure described in RFC4192).=20

The task of the 6RENUM working group is to document existing renumbering =
practices for enterprise site networks and to identify specific =
renumbering problems or 'gaps' in the context of partial or site-wide =
renumbering.  Completion of these tasks should provide a basis for =
future work to identify and develop point solutions or system solutions =
to address those problems or to stimulate such development in other =
working groups as appropriate.=20

6RENUM is chartered to perform an analysis of IPv6 site renumbering. If =
the analysis leads to conclusions that are also applicable to IPv4 that =
will be an advantage, but it is not an objective of the WG to make its =
outputs more widely available than IPv6. Similarly the WG is targeting =
enterprise networks, but the analysis may also be applicable to SOHO or =
other (e.g. ad-hoc) scenarios.

It may be that for site renumbering to become more routine, a systematic =
address management approach will be required. By documenting current =
practices and undertaking a gap analysis, we should become better =
informed of the requirements of such an approach. Post-analysis =
rechartering may lead to further work in this area. RFC 4192, RFC 5887, =
and draft-jiang-ipv6-site-renum-guideline are starting points for this =
work.

Goals/deliverables
------------------

The goals of the 6RENUM working group are:

1. To undertake scenario descriptions, including documentation of =
current capability inventories and existing BCPs, for enterprise =
networks, including managed and unmanaged elements. These texts should =
contribute towards a gap analysis and provide an agreed basis for =
subsequent WG rechartering towards development of solutions (which may =
be more appropriate for other WGs to undertake) and improved practices. =
Operator input will be of high value for this text.

2. To perform a gap analysis for renumbering practices, to identify =
generic issues for network design, network management, address =
management and renumbering operations. The methodology for the WG will =
be to begin building the enterprise scenario description while in =
parallel constructing an initial gap analysis drawing on existing work =
in (at least) RFC4192 and RFC5887. As the scenario text hardens, its =
contributions will be incorporated into the more detailed gap analysis, =
which can be published once the scenario text is completed. The =
deliverables are thus the scenario and gap analysis texts.

The following topics are out of scope for the working group:

1. Renumbering avoidance; this can perhaps be considered by appropriate =
IRTF groups. As documented in RFC5887, renumbering cannot be completely =
avoided. The WG is limited to dealing with how to renumber when it is =
unavoidable.

2. IPv4 renumbering. While many sites are likely to run dual-stack, IPv6 =
is the future and, especially given concerns over extensive use of IPv6 =
PI, the most appropriate place to focus effort.

3. ISP renumbering; this is potentially the most complex renumbering =
case. However, more benefit can be achieved by focusing effort on site =
renumbering. The enterprise site analysis should include the ISP's role =
in the site's renumbering events.

4. Neither SOHO nor manet networks are targeted by the WG. However, if =
outputs from the WG are applicable to those scenarios, that would be an =
advantage.

A recharter of the WG will be possible once the gap analysis and =
scenario description are completed and published. Such rechartering =
would identify more specific work items within the 6RENUM WG or =
appropriate protocol WGs, and may include a proposal for work on a =
systematic address management approach.

Milestones
----------

Oct 2011 IPv6 enterprise site scenario draft ready for WG adoption
Nov 2011 Gap analysis document ready for WG adoption=20
Jun 2012 IPv6 enterprise site scenario draft ready for WGLC=20
Jul 2012 Gap analysis document ready for WGLC=20

Tim

On 2 Jun 2011, at 18:54, IESG Secretary wrote:

> A new IETF working group has been proposed in the Operations and=20
> Management Area.  The IESG has not made any determination as yet. The=20=

> following draft charter was submitted, and is provided for =
informational=20
> purposes only. Please send your comments to the IESG mailing list=20
> (iesg@ietf.org) by Thursday, June 9, 2011                           =20=

>=20
> IPv6 Site Renumbering (6renum)=20
> -------------------------------
> Last Modified: 2011-06-02
>=20
> Current Status: Proposed Working Group
>=20
> Chairs: TBD
>=20
> Area Director: Ron Bonica
>=20
> Mailing list
>  Address: renum@ietf.org
>  To Subscribe: https://www.ietf.org/mailman/listinfo/renum
>  Archive: http://www.ietf.org/mail-archive/web/renum/
>=20
> Description of Working Group
> -----------
>=20
> As outlined in RFC 5887, renumbering, especially for medium to large=20=

> sites and networks, is currently viewed as an expensive, painful, and=20=

> error-prone process, avoided by network managers as much as possible.=20=

>=20
> As IPv6 adoption begins to gather momentum, those managers may turn to
> PI addressing for IPv6 to attempt to minimise the need for future=20
> renumbering. However, such an approach would create very serious BGP4
> scaling problems if used by millions of end sites; it is thus =
desirable=20
> to develop tools, techniques and practices that may make renumbering a
> simpler process, to reduce demand for IPv6 PI space. In addition, as
> RFC 5887 describes, there are other triggers that mean some cases of
> renumbering are unavoidable, so it should be considered a given that
> a site may need partial or complete renumbering at some stage.  =20
>=20
> Strategically it is thus important to implement and deploy techniques=20=

> that facilitate simpler IPv6 site renumbering, so that as IPv6 becomes=20=

> universally deployed, renumbering can be viewed as a more routine =
event.
> This includes consideration of how the initial assignment and =
subsequent
> management of address information is performed, as this will affect=20
> future renumbering operations.
>=20
> For renumbering to become more routine, a systematic address =
management=20
> approach will be essential. A large site with a short prefix will be=20=

> divided into subnets with longer prefixes. In this scenario, =
renumbering=20
> or partial renumbering can be complicated. Aggregation, =
synchronisation,=20
> coordination, etc., need to be carefully managed, and the use of=20
> manually inserted address literals minimised. In unmanaged scenarios,=20=

> consideration may need to be made for 'flag day' renumbering (in=20
> contrast to the procedure described in RFC4192).
>=20
> The task of the 6RENUM working group is to document existing =
renumbering
> practices for managed (enterprise) and unmanaged (SOHO) networks, to=20=

> identify specific renumbering problems in the context of site-wide=20
> renumbering, and to then recharter with a view to develop point=20
> solutions and system solutions to address those problems or to =
stimulate=20
> such development in other working groups if appropriate.  The =
principal=20
> target will be solutions for IPv6.
>=20
> RFC 4192, RFC 5887, and draft-jiang-ipv6-site-renum-guideline are=20
> starting points for this work.
>=20
> Goals/deliverables
> ------------------
>=20
> The goals of the 6RENUM working group are:
>=20
> 1. To undertake scenario descriptions, including documentation of=20
>   current capability inventories and existing BCPs for managed=20
>   (enterprise) and unmanaged (SOHO) networks.  These texts should=20
>   contribute towards the gap analysis and provide an agreed basis for=20=

>   subsequent WG rechartering towards development of solutions=20
>   (potentially in other WGs) and improved practices. Operator input=20
>   will be of particularly high value for this stage.
>=20
> 2. To examine fully automatic, self-organising networks =
(manet/autoconf)=20
>   as a possible third scenario.=20
>=20
> 3. To perform a gap analysis for renumbering practices, drawing on =
RFCs
>   4192 and 5887, to identify generic issues for network design, =
network
>   management, and renumbering operations. The scenario texts will
>   contribute to the analysis.
>=20
> 4. To document existing IP address management models and practices =
with
>   a view to proposing (at a high level) an appropriate model to allow
>   simplification of any partial or full site renumbering process
>   (this would likely be applicable to managed rather than unmanaged
>   scenarios).
>=20
> The general methodology for the WG will be to first build managed and
> unmanaged baseline scenario descriptions, while in parallel =
undertaking=20
> an initial gap analysis from existing work in (at least) RFC4192 and=20=

> RFC5877. As the scenario texts harden, their contributions will be=20
> incorporated into the gap analysis, which can be published once the=20
> scenarios are completed.  =20
>=20
> The following topics are out of scope for the working group:
>=20
> 1. Renumbering avoidance; this can perhaps be considered by =
appropriate=20
>   IRTF groups.  As documented in RFC5887, renumbering cannot be=20
>   completely avoided. The WG is limited to dealing with how to =
renumber=20
>   when it is unavoidable.
>=20
> 2. IPv4 renumbering.  While many sites are likely to run dual-stack,=20=

>   IPv6 is the future and, especially given concerns over extensive use=20=

>   of IPv6 PI, the most appropriate place to focus effort.
>=20
> 3. ISP renumbering; this is potentially the most complex renumbering=20=

>   case.  More benefit can be achieved by focusing effort on site=20
>   renumbering.  The site analysis should include the ISP's role in its=20=

>   own renumbering event.
>=20
> A recharter of the WG will be possible once the gap analysis and=20
> scenario descriptions are completed, and the IP address management=20
> ('numbering tool') review and (high level) proposal have been =
published.  =20
> The rechartering will identify more specific work items within the=20
> 6RENUM WG or appropriate protocol WGs.=20
>=20
> Milestones
> ----------
>=20
> Aug 2011    managed (enterprise) scenario draft ready for WG adoption=20=

>            (partly based on draft-jiang-ipv6-site-renum-guideline)
>=20
> Aug 2011    unmanaged (SOHO) scenario draft ready for WG adoption
>=20
> Oct 2011    gap analysis document ready for WG adoption (already some=20=

>            considerations in RFC5887 and=20
>            draft-jiang-ipv6-site-renum-guideline)
>=20
> Oct 2011    management model draft ready for WG adoption
>=20
> Jan 2012    managed (enterprise) scenario draft ready for WGLC
>=20
> Jan 2012    unmanaged (SOHO) scenario draft ready for WGLC
>=20
> Feb 2012    management model ready for WGLC
>=20
> Mar 2012    gap analysis document ready for WGLC
>=20
> Apr 2012    recharter WG towards solution space
>=20
>=20
>=20
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


From wwwrun@ietfa.amsl.com  Fri Jun  3 08:36:19 2011
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: renum@ietf.org
Delivered-To: renum@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id E3672E078E; Fri,  3 Jun 2011 08:36:19 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110603153619.E3672E078E@ietfa.amsl.com>
Date: Fri,  3 Jun 2011 08:36:19 -0700 (PDT)
Cc: renum@ietf.org
Subject: [renum] REVISED WG Review: IPv6 Site Renumbering (6renum)
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: iesg@ietf.org
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 15:36:20 -0000

A new IETF working group has been proposed in the Operations and 
Management Area.  The IESG has not made any determination as yet. The 
following draft charter was submitted, and is provided for informational 
purposes only. Please send your comments to the IESG mailing list 
(iesg@ietf.org) by Friday, June 10, 2011.               

IPv6 Site Renumbering (6renum) 
-------------------------------
Last Modified: 2011-06-03

Current Status: Proposed Working Group

Chairs: TBD

Area Director: Ron Bonica

Mailing list
  Address: renum@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/renum
  Archive: http://www.ietf.org/mail-archive/web/renum/

Description
-----------

As outlined in RFC 5887, renumbering, especially for medium to large 
sites and networks, is currently viewed as an expensive, painful, and 
error-prone process, avoided by network managers as much as possible.

As that RFC describes, there are triggers that mean some cases of 
renumbering are unavoidable, so it should be considered a given that a 
site may need partial or complete renumbering at some stage. It is thus 
important to implement and deploy techniques that facilitate simpler 
IPv6 site renumbering, so that as IPv6 becomes universally deployed, 
renumbering can be viewed as a more routine event. This includes 
consideration of how the initial assignment and subsequent management of 
address information is performed, as this will affect future renumbering 
operations.

If IPv6 site renumbering continues to be considered difficult, network 
managers will turn to PI addressing for IPv6 to attempt to minimise the 
need for future renumbering. However, widespread use of PI may create 
very serious BGP4 scaling problems. It is thus desirable to develop 
tools and practices that may make renumbering a simpler process to 
reduce demand for IPv6 PI space.

Renumbering, or partial renumbering, can be complicated in an enterprise 
site where a short prefix is divided into subnets with longer prefixes.  
Aggregation, synchronisation, coordination, etc., need to be carefully 
managed, and the use of manually inserted address literals minimised.

Other factors such as applications binding long-term to low level IP 
addresses may add constraints to what can be realistically achieved, but 
identifying and documenting such factors is a useful objective.  In some 
scenarios, consideration may also need to be made for 'flag day' 
renumbering (in contrast to the procedure described in RFC4192). 

The task of the 6RENUM working group is to document existing renumbering 
practices for enterprise site networks and to identify specific 
renumbering problems or 'gaps' in the context of partial or site-wide 
renumbering.  Completion of these tasks should provide a basis for 
future work to identify and develop point solutions or system solutions 
to address those problems or to stimulate such development in other 
working groups as appropriate. 

6RENUM is chartered to perform an analysis of IPv6 site renumbering. If 
the analysis leads to conclusions that are also applicable to IPv4 that 
will be an advantage, but it is not an objective of the WG to make its 
outputs more widely available than IPv6. Similarly the WG is targeting 
enterprise networks, but the analysis may also be applicable to SOHO or 
other (e.g. ad-hoc) scenarios.

It may be that for site renumbering to become more routine, a systematic 
address management approach will be required. By documenting current 
practices and undertaking a gap analysis, we should become better 
informed of the requirements of such an approach. Post-analysis 
rechartering may lead to further work in this area. RFC 4192, RFC 5887, 
and draft-jiang-ipv6-site-renum-guideline are starting points for this 
work.

Goals/deliverables
------------------

The goals of the 6RENUM working group are:

1. To undertake scenario descriptions, including documentation of 
current capability inventories and existing BCPs, for enterprise 
networks, including managed and unmanaged elements. These texts should 
contribute towards a gap analysis and provide an agreed basis for 
subsequent WG rechartering towards development of solutions (which may 
be more appropriate for other WGs to undertake) and improved practices. 
Operator input will be of high value for this text.

2. To perform a gap analysis for renumbering practices, to identify 
generic issues for network design, network management, address 
management and renumbering operations. The methodology for the WG will 
be to begin building the enterprise scenario description while in 
parallel constructing an initial gap analysis drawing on existing work 
in (at least) RFC4192 and RFC5887. As the scenario text hardens, its 
contributions will be incorporated into the more detailed gap analysis, 
which can be published once the scenario text is completed. The 
deliverables are thus the scenario and gap analysis texts.

The following topics are out of scope for the working group:

1. Renumbering avoidance; this can perhaps be considered by appropriate 
IRTF groups. As documented in RFC5887, renumbering cannot be completely 
avoided. The WG is limited to dealing with how to renumber when it is 
unavoidable.

2. IPv4 renumbering. While many sites are likely to run dual-stack, IPv6 
is the future and, especially given concerns over extensive use of IPv6 
PI, the most appropriate place to focus effort.

3. ISP renumbering; this is potentially the most complex renumbering 
case. However, more benefit can be achieved by focusing effort on site 
renumbering. The enterprise site analysis should include the ISP's role 
in the site's renumbering events.

4. Neither SOHO nor manet networks are targeted by the WG. However, if 
outputs from the WG are applicable to those scenarios, that would be an 
advantage.

A recharter of the WG will be possible once the gap analysis and 
scenario description are completed and published. Such rechartering 
would identify more specific work items within the 6RENUM WG or 
appropriate protocol WGs, and may include a proposal for work on a 
systematic address management approach.

Milestones
----------

Oct 2011 IPv6 enterprise site scenario draft ready for WG adoption
Nov 2011 Gap analysis document ready for WG adoption 
Jun 2012 IPv6 enterprise site scenario draft ready for WGLC 
Jul 2012 Gap analysis document ready for WGLC 



From fred@cisco.com  Fri Jun  3 11:32:13 2011
Return-Path: <fred@cisco.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E97FE07A2 for <renum@ietfa.amsl.com>; Fri,  3 Jun 2011 11:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.211
X-Spam-Level: 
X-Spam-Status: No, score=-110.211 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nPaAOCbzK+VG for <renum@ietfa.amsl.com>; Fri,  3 Jun 2011 11:32:12 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id F064FE079A for <renum@ietf.org>; Fri,  3 Jun 2011 11:32:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=14240; q=dns/txt; s=iport; t=1307125931; x=1308335531; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=6MXIh9v9pfsF3UF4DkcPGD/9l6aSDB8me7DxhzWarXY=; b=WIT8sGWQCTlWcvq6zP0q7CyOTM7O+w8Li5H8Y44x+RW4km7zuCWzPO+N AzSsiXdZu98BW/JQYHqSpZ+MI6rP0TQ+o8GBX/EudA3Xbow3Vp21tumWc pILu5MsmPprrfneP8NyKVruwNXCkfnEHHQGTkzQKwaJ09gfkOKujsrB2G 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAMUn6U2rRDoG/2dsb2JhbABFDhCmKneIcaNqnWWDF4MKBIZwigSESIo8VQ
X-IronPort-AV: E=Sophos;i="4.65,315,1304294400"; d="scan'208";a="708023730"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-6.cisco.com with ESMTP; 03 Jun 2011 18:32:10 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p53IVs5w018012; Fri, 3 Jun 2011 18:32:10 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Fri, 03 Jun 2011 11:32:10 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Fri, 03 Jun 2011 11:32:10 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <EMEW3|548ba481df1d40481ee40daf1aaa3fddn52BQs03tjc|ecs.soton.ac.uk|C3AA1194-5390-4F27-94B6-FBD7265CD1AA@ecs.soton.ac.uk>
Date: Fri, 3 Jun 2011 11:31:44 -0700
Message-Id: <8DA90861-8B93-4A36-B4B9-E38789EA27B0@cisco.com>
References: <20110602175454.F218FE080B@ietfa.amsl.com> <C3AA1194-5390-4F27-94B6-FBD7265CD1AA@ecs.soton.ac.uk> <EMEW3|548ba481df1d40481ee40daf1aaa3fddn52BQs03tjc|ecs.soton.ac.uk|C3AA1194-5390-4F27-94B6-FBD7265CD1AA@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: renum@ietf.org
Subject: Re: [renum] WG Review: IPv6 Site Renumbering (6renum)
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 18:32:13 -0000

Thanks.

I'm in favor of this.

On Jun 3, 2011, at 3:26 AM, Tim Chown wrote:

> I have alerted Ron to the fact that the old description has been used. =
The correct description, which was posted to renum yesterday after =
feedback from the list, is as follows:
>=20
> IPv6 Enterprise Site Renumbering (6RENUM) WG
> Chairs: TBD
> Area Director: Ron Bonica
>=20
> Mailing list Address: renum@ietf.org
> To Subscribe: https://www.ietf.org/mailman/listinfo/renum=20
> Archive: http://www.ietf.org/mail-archive/web/renum/
>=20
> Description
> -----------
>=20
> As outlined in RFC 5887, renumbering, especially for medium to large =
sites and networks, is currently viewed as an expensive, painful, and =
error-prone process, avoided by network managers as much as possible.
>=20
> As that RFC describes, there are triggers that mean some cases of =
renumbering are unavoidable, so it should be considered a given that a =
site may need partial or complete renumbering at some stage. It is thus =
important to implement and deploy techniques that facilitate simpler =
IPv6 site renumbering, so that as IPv6 becomes universally deployed, =
renumbering can be viewed as a more routine event. This includes =
consideration of how the initial assignment and subsequent management of =
address information is performed, as this will affect future renumbering =
operations.
>=20
> If IPv6 site renumbering continues to be considered difficult, network =
managers will turn to PI addressing for IPv6 to attempt to minimise the =
need for future renumbering. However, widespread use of PI may create =
very serious BGP4 scaling problems. It is thus desirable to develop =
tools and practices that may make renumbering a simpler process to =
reduce demand for IPv6 PI space.
>=20
> Renumbering, or partial renumbering, can be complicated in an =
enterprise site where a short prefix is divided into subnets with longer =
prefixes.  Aggregation, synchronisation, coordination, etc., need to be =
carefully managed, and the use of manually inserted address literals =
minimised.
>=20
> Other factors such as applications binding long-term to low level IP =
addresses may add constraints to what can be realistically achieved, but =
identifying and documenting such factors is a useful objective.  In some =
scenarios, consideration may also need to be made for 'flag day' =
renumbering (in contrast to the procedure described in RFC4192).=20
>=20
> The task of the 6RENUM working group is to document existing =
renumbering practices for enterprise site networks and to identify =
specific renumbering problems or 'gaps' in the context of partial or =
site-wide renumbering.  Completion of these tasks should provide a basis =
for future work to identify and develop point solutions or system =
solutions to address those problems or to stimulate such development in =
other working groups as appropriate.=20
>=20
> 6RENUM is chartered to perform an analysis of IPv6 site renumbering. =
If the analysis leads to conclusions that are also applicable to IPv4 =
that will be an advantage, but it is not an objective of the WG to make =
its outputs more widely available than IPv6. Similarly the WG is =
targeting enterprise networks, but the analysis may also be applicable =
to SOHO or other (e.g. ad-hoc) scenarios.
>=20
> It may be that for site renumbering to become more routine, a =
systematic address management approach will be required. By documenting =
current practices and undertaking a gap analysis, we should become =
better informed of the requirements of such an approach. Post-analysis =
rechartering may lead to further work in this area. RFC 4192, RFC 5887, =
and draft-jiang-ipv6-site-renum-guideline are starting points for this =
work.
>=20
> Goals/deliverables
> ------------------
>=20
> The goals of the 6RENUM working group are:
>=20
> 1. To undertake scenario descriptions, including documentation of =
current capability inventories and existing BCPs, for enterprise =
networks, including managed and unmanaged elements. These texts should =
contribute towards a gap analysis and provide an agreed basis for =
subsequent WG rechartering towards development of solutions (which may =
be more appropriate for other WGs to undertake) and improved practices. =
Operator input will be of high value for this text.
>=20
> 2. To perform a gap analysis for renumbering practices, to identify =
generic issues for network design, network management, address =
management and renumbering operations. The methodology for the WG will =
be to begin building the enterprise scenario description while in =
parallel constructing an initial gap analysis drawing on existing work =
in (at least) RFC4192 and RFC5887. As the scenario text hardens, its =
contributions will be incorporated into the more detailed gap analysis, =
which can be published once the scenario text is completed. The =
deliverables are thus the scenario and gap analysis texts.
>=20
> The following topics are out of scope for the working group:
>=20
> 1. Renumbering avoidance; this can perhaps be considered by =
appropriate IRTF groups. As documented in RFC5887, renumbering cannot be =
completely avoided. The WG is limited to dealing with how to renumber =
when it is unavoidable.
>=20
> 2. IPv4 renumbering. While many sites are likely to run dual-stack, =
IPv6 is the future and, especially given concerns over extensive use of =
IPv6 PI, the most appropriate place to focus effort.
>=20
> 3. ISP renumbering; this is potentially the most complex renumbering =
case. However, more benefit can be achieved by focusing effort on site =
renumbering. The enterprise site analysis should include the ISP's role =
in the site's renumbering events.
>=20
> 4. Neither SOHO nor manet networks are targeted by the WG. However, if =
outputs from the WG are applicable to those scenarios, that would be an =
advantage.
>=20
> A recharter of the WG will be possible once the gap analysis and =
scenario description are completed and published. Such rechartering =
would identify more specific work items within the 6RENUM WG or =
appropriate protocol WGs, and may include a proposal for work on a =
systematic address management approach.
>=20
> Milestones
> ----------
>=20
> Oct 2011 IPv6 enterprise site scenario draft ready for WG adoption
> Nov 2011 Gap analysis document ready for WG adoption=20
> Jun 2012 IPv6 enterprise site scenario draft ready for WGLC=20
> Jul 2012 Gap analysis document ready for WGLC=20
>=20
> Tim
>=20
> On 2 Jun 2011, at 18:54, IESG Secretary wrote:
>=20
>> A new IETF working group has been proposed in the Operations and=20
>> Management Area.  The IESG has not made any determination as yet. The=20=

>> following draft charter was submitted, and is provided for =
informational=20
>> purposes only. Please send your comments to the IESG mailing list=20
>> (iesg@ietf.org) by Thursday, June 9, 2011                           =20=

>>=20
>> IPv6 Site Renumbering (6renum)=20
>> -------------------------------
>> Last Modified: 2011-06-02
>>=20
>> Current Status: Proposed Working Group
>>=20
>> Chairs: TBD
>>=20
>> Area Director: Ron Bonica
>>=20
>> Mailing list
>> Address: renum@ietf.org
>> To Subscribe: https://www.ietf.org/mailman/listinfo/renum
>> Archive: http://www.ietf.org/mail-archive/web/renum/
>>=20
>> Description of Working Group
>> -----------
>>=20
>> As outlined in RFC 5887, renumbering, especially for medium to large=20=

>> sites and networks, is currently viewed as an expensive, painful, and=20=

>> error-prone process, avoided by network managers as much as possible.=20=

>>=20
>> As IPv6 adoption begins to gather momentum, those managers may turn =
to
>> PI addressing for IPv6 to attempt to minimise the need for future=20
>> renumbering. However, such an approach would create very serious BGP4
>> scaling problems if used by millions of end sites; it is thus =
desirable=20
>> to develop tools, techniques and practices that may make renumbering =
a
>> simpler process, to reduce demand for IPv6 PI space. In addition, as
>> RFC 5887 describes, there are other triggers that mean some cases of
>> renumbering are unavoidable, so it should be considered a given that
>> a site may need partial or complete renumbering at some stage.  =20
>>=20
>> Strategically it is thus important to implement and deploy techniques=20=

>> that facilitate simpler IPv6 site renumbering, so that as IPv6 =
becomes=20
>> universally deployed, renumbering can be viewed as a more routine =
event.
>> This includes consideration of how the initial assignment and =
subsequent
>> management of address information is performed, as this will affect=20=

>> future renumbering operations.
>>=20
>> For renumbering to become more routine, a systematic address =
management=20
>> approach will be essential. A large site with a short prefix will be=20=

>> divided into subnets with longer prefixes. In this scenario, =
renumbering=20
>> or partial renumbering can be complicated. Aggregation, =
synchronisation,=20
>> coordination, etc., need to be carefully managed, and the use of=20
>> manually inserted address literals minimised. In unmanaged scenarios,=20=

>> consideration may need to be made for 'flag day' renumbering (in=20
>> contrast to the procedure described in RFC4192).
>>=20
>> The task of the 6RENUM working group is to document existing =
renumbering
>> practices for managed (enterprise) and unmanaged (SOHO) networks, to=20=

>> identify specific renumbering problems in the context of site-wide=20
>> renumbering, and to then recharter with a view to develop point=20
>> solutions and system solutions to address those problems or to =
stimulate=20
>> such development in other working groups if appropriate.  The =
principal=20
>> target will be solutions for IPv6.
>>=20
>> RFC 4192, RFC 5887, and draft-jiang-ipv6-site-renum-guideline are=20
>> starting points for this work.
>>=20
>> Goals/deliverables
>> ------------------
>>=20
>> The goals of the 6RENUM working group are:
>>=20
>> 1. To undertake scenario descriptions, including documentation of=20
>>  current capability inventories and existing BCPs for managed=20
>>  (enterprise) and unmanaged (SOHO) networks.  These texts should=20
>>  contribute towards the gap analysis and provide an agreed basis for=20=

>>  subsequent WG rechartering towards development of solutions=20
>>  (potentially in other WGs) and improved practices. Operator input=20
>>  will be of particularly high value for this stage.
>>=20
>> 2. To examine fully automatic, self-organising networks =
(manet/autoconf)=20
>>  as a possible third scenario.=20
>>=20
>> 3. To perform a gap analysis for renumbering practices, drawing on =
RFCs
>>  4192 and 5887, to identify generic issues for network design, =
network
>>  management, and renumbering operations. The scenario texts will
>>  contribute to the analysis.
>>=20
>> 4. To document existing IP address management models and practices =
with
>>  a view to proposing (at a high level) an appropriate model to allow
>>  simplification of any partial or full site renumbering process
>>  (this would likely be applicable to managed rather than unmanaged
>>  scenarios).
>>=20
>> The general methodology for the WG will be to first build managed and
>> unmanaged baseline scenario descriptions, while in parallel =
undertaking=20
>> an initial gap analysis from existing work in (at least) RFC4192 and=20=

>> RFC5877. As the scenario texts harden, their contributions will be=20
>> incorporated into the gap analysis, which can be published once the=20=

>> scenarios are completed.  =20
>>=20
>> The following topics are out of scope for the working group:
>>=20
>> 1. Renumbering avoidance; this can perhaps be considered by =
appropriate=20
>>  IRTF groups.  As documented in RFC5887, renumbering cannot be=20
>>  completely avoided. The WG is limited to dealing with how to =
renumber=20
>>  when it is unavoidable.
>>=20
>> 2. IPv4 renumbering.  While many sites are likely to run dual-stack,=20=

>>  IPv6 is the future and, especially given concerns over extensive use=20=

>>  of IPv6 PI, the most appropriate place to focus effort.
>>=20
>> 3. ISP renumbering; this is potentially the most complex renumbering=20=

>>  case.  More benefit can be achieved by focusing effort on site=20
>>  renumbering.  The site analysis should include the ISP's role in its=20=

>>  own renumbering event.
>>=20
>> A recharter of the WG will be possible once the gap analysis and=20
>> scenario descriptions are completed, and the IP address management=20
>> ('numbering tool') review and (high level) proposal have been =
published.  =20
>> The rechartering will identify more specific work items within the=20
>> 6RENUM WG or appropriate protocol WGs.=20
>>=20
>> Milestones
>> ----------
>>=20
>> Aug 2011    managed (enterprise) scenario draft ready for WG adoption=20=

>>           (partly based on draft-jiang-ipv6-site-renum-guideline)
>>=20
>> Aug 2011    unmanaged (SOHO) scenario draft ready for WG adoption
>>=20
>> Oct 2011    gap analysis document ready for WG adoption (already some=20=

>>           considerations in RFC5887 and=20
>>           draft-jiang-ipv6-site-renum-guideline)
>>=20
>> Oct 2011    management model draft ready for WG adoption
>>=20
>> Jan 2012    managed (enterprise) scenario draft ready for WGLC
>>=20
>> Jan 2012    unmanaged (SOHO) scenario draft ready for WGLC
>>=20
>> Feb 2012    management model ready for WGLC
>>=20
>> Mar 2012    gap analysis document ready for WGLC
>>=20
>> Apr 2012    recharter WG towards solution space
>>=20
>>=20
>>=20
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>=20
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum


From wwwrun@ietfa.amsl.com  Tue Jun 14 09:29:00 2011
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: renum@ietf.org
Delivered-To: renum@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id 358B39E8031; Tue, 14 Jun 2011 09:29:00 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110614162900.358B39E8031@ietfa.amsl.com>
Date: Tue, 14 Jun 2011 09:29:00 -0700 (PDT)
Cc: renum@ietf.org
Subject: [renum] WG Action: IPv6 Site Renumbering (6renum)
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 16:29:00 -0000

A new IETF working group has been formed in the Operations and 
Management Area.  For additional information, please contact the Area 
Directors or the WG Chairs.

IPv6 Site Renumbering (6renum) 
-------------------------------
Current Status: Active Working Group

Chair:
  Tim Chown <tjc@ecs.soton.ac.uk>

Operations and Management Area Directors: 
  Ron Bonica <rbonica@juniper.net>
  Dan Romascanu <dromasca@avaya.com>

Operations and Management Area Advisor: 
  Ron Bonica <rbonica@juniper.net>

Mailing list
  Address: renum@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/renum
  Archive: http://www.ietf.org/mail-archive/web/renum/

Description
-----------

As outlined in RFC 5887, renumbering, especially for medium to large 
sites and networks, is currently viewed as an expensive, painful, and 
error-prone process, avoided by network managers as much as possible.

As that RFC describes, there are triggers that mean some cases of 
renumbering are unavoidable, so it should be considered a given that a 
site may need partial or complete renumbering at some stage. It is thus 
important to implement and deploy techniques that facilitate simpler 
IPv6 site renumbering, so that as IPv6 becomes universally deployed, 
renumbering can be viewed as a more routine event. This includes 
consideration of how the initial assignment and subsequent management of 
address information is performed, as this will affect future renumbering 
operations.

If IPv6 site renumbering continues to be considered difficult, network 
managers will turn to PI addressing for IPv6 to attempt to minimise the 
need for future renumbering. However, widespread use of PI may create 
very serious BGP4 scaling problems. It is thus desirable to develop 
tools and practices that may make renumbering a simpler process to 
reduce demand for IPv6 PI space.

Renumbering, or partial renumbering, can be complicated in an enterprise 
site where a short prefix is divided into subnets with longer prefixes.  
Aggregation, synchronisation, coordination, etc., need to be carefully 
managed, and the use of manually inserted address literals minimised.

Other factors such as applications binding long-term to low level IP 
addresses may add constraints to what can be realistically achieved, but 
identifying and documenting such factors is a useful objective.  In some 
scenarios, consideration may also need to be made for 'flag day' 
renumbering (in contrast to the procedure described in RFC4192). 

The task of the 6RENUM working group is to document existing renumbering 
practices for enterprise site networks and to identify specific 
renumbering problems or 'gaps' in the context of partial or site-wide 
renumbering.  Completion of these tasks should provide a basis for 
future work to identify and develop point solutions or system solutions 
to address those problems or to stimulate such development in other 
working groups as appropriate. 

6RENUM is chartered to perform an analysis of IPv6 site renumbering. If 
the analysis leads to conclusions that are also applicable to IPv4 that 
will be an advantage, but it is not an objective of the WG to make its 
outputs more widely available than IPv6. Similarly the WG is targeting 
enterprise networks, but the analysis may also be applicable to SOHO or 
other (e.g. ad-hoc) scenarios.

It may be that for site renumbering to become more routine, a systematic 
address management approach will be required. By documenting current 
practices and undertaking a gap analysis, we should become better 
informed of the requirements of such an approach. Post-analysis 
rechartering may lead to further work in this area. RFC 4192, RFC 5887, 
and draft-jiang-ipv6-site-renum-guideline are starting points for this 
work.

Goals/deliverables
------------------

The goals of the 6RENUM working group are:

1. To undertake scenario descriptions, including documentation of 
current capability inventories and existing BCPs, for enterprise 
networks, including managed and unmanaged elements. These texts should 
contribute towards a gap analysis and provide an agreed basis for 
subsequent WG rechartering towards development of solutions (which may 
be more appropriate for other WGs to undertake) and improved practices. 
Operator input will be of high value for this text.

2. To perform a gap analysis for renumbering practices, to identify 
generic issues for network design, network management, address 
management and renumbering operations. The methodology for the WG will 
be to begin building the enterprise scenario description while in 
parallel constructing an initial gap analysis drawing on existing work 
in (at least) RFC4192 and RFC5887. As the scenario text hardens, its 
contributions will be incorporated into the more detailed gap analysis, 
which can be published once the scenario text is completed. The 
deliverables are thus the scenario and gap analysis texts.

The following topics are out of scope for the working group:

1. Renumbering avoidance; this can perhaps be considered by appropriate 
IRTF groups. As documented in RFC5887, renumbering cannot be completely 
avoided. The WG is limited to dealing with how to renumber when it is 
unavoidable.

2. IPv4 renumbering. While many sites are likely to run dual-stack, IPv6 
is the future and, especially given concerns over extensive use of IPv6 
PI, the most appropriate place to focus effort.

3. ISP renumbering; this is potentially the most complex renumbering 
case. However, more benefit can be achieved by focusing effort on site 
renumbering. The enterprise site analysis should include the ISP's role 
in the site's renumbering events.

4. Neither SOHO nor manet networks are targeted by the WG. However, if 
outputs from the WG are applicable to those scenarios, that would be an 
advantage.

A recharter of the WG will be possible once the gap analysis and 
scenario description are completed and published. Such rechartering 
would identify more specific work items within the 6RENUM WG or 
appropriate protocol WGs, and may include a proposal for work on a 
systematic address management approach.

Milestones
----------

Oct 2011 IPv6 enterprise site scenario draft ready for WG adoption
Nov 2011 Gap analysis document ready for WG adoption 
Jun 2012 IPv6 enterprise site scenario draft ready for WGLC 
Jul 2012 Gap analysis document ready for WGLC 


From fred@cisco.com  Wed Jun 15 16:25:21 2011
Return-Path: <fred@cisco.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1526621F85D8 for <renum@ietfa.amsl.com>; Wed, 15 Jun 2011 16:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.428
X-Spam-Level: 
X-Spam-Status: No, score=-110.428 tagged_above=-999 required=5 tests=[AWL=-0.429, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fk-8NnfKWbid for <renum@ietfa.amsl.com>; Wed, 15 Jun 2011 16:25:20 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1425B21F85D5 for <renum@ietf.org>; Wed, 15 Jun 2011 16:25:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=56; q=dns/txt; s=iport; t=1308180320; x=1309389920; h=from:subject:date:message-id:to:mime-version: content-transfer-encoding; bh=UETG+TmmGJcqNRuTb9wlaQsrXsyOjsfStCDZPRdPMjw=; b=HEdmd5M1BZhdoycH1YiVPi/BSA/f3jQrA8+owLaKJJ8z9f89vH8zT5dE F8KwoW3qU/m2mcSvtSQ2KBZzXZdnEsbfLHgZ5Ggt34tympt13dTsvSdZQ 7CeeNgw8cwIdLCXN4zVVE+0MeYJNQm8bEy6bA07576EoVDihWhgjiiOpc I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkAHAKg++U2rRDoJ/2dsb2JhbABSmBiOR3eIbKEsgR2eKYYmBIcYijaEW4s1
X-IronPort-AV: E=Sophos;i="4.65,372,1304294400"; d="scan'208";a="337887557"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-3.cisco.com with ESMTP; 15 Jun 2011 23:25:19 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p5FNPE7E017578 for <renum@ietf.org>; Wed, 15 Jun 2011 23:25:19 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Wed, 15 Jun 2011 16:25:20 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Wed, 15 Jun 2011 16:25:20 -0700
From: Fred Baker <fred@cisco.com>
Date: Wed, 15 Jun 2011 16:25:04 -0700
Message-Id: <3398AF96-CDDA-4075-965A-9368B948C5AA@cisco.com>
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [renum] draft-sarikaya-v6ops-prefix-delegation
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 23:25:21 -0000

May I solicit a review of this draft, posted to v6ops?

From jiangsheng@huawei.com  Wed Jun 15 18:07:47 2011
Return-Path: <jiangsheng@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1832521F860F for <renum@ietfa.amsl.com>; Wed, 15 Jun 2011 18:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99TSpy7TDS2F for <renum@ietfa.amsl.com>; Wed, 15 Jun 2011 18:07:46 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 5880521F860B for <renum@ietf.org>; Wed, 15 Jun 2011 18:07:46 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LMU005VYZ4XKK@szxga04-in.huawei.com> for renum@ietf.org; Thu, 16 Jun 2011 09:07:45 +0800 (CST)
Received: from szxeml208-edg.china.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 <0LMU00A7IZ4W6U@szxga04-in.huawei.com> for renum@ietf.org; Thu, 16 Jun 2011 09:07:44 +0800 (CST)
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 16 Jun 2011 09:07:42 +0800
Received: from SZXEML504-MBX.china.huawei.com ([169.254.8.3]) by SZXEML401-HUB.china.huawei.com ([10.82.67.31]) with mapi id 14.01.0270.001; Thu, 16 Jun 2011 09:07:44 +0800
Date: Thu, 16 Jun 2011 01:07:21 +0000
From: Jiangsheng <jiangsheng@huawei.com>
X-Originating-IP: [10.110.98.101]
To: "renum@ietf.org" <renum@ietf.org>
Message-id: <5D36713D8A4E7348A7E10DF7437A4B928636A8@SZXEML504-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: en-GB, zh-CN, en-US
Thread-topic: Work plan towards IETF 81 and contributions needed
Thread-index: AcwrwcvlsrPAuXl6SG+Dtl6lqhdflQ==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Subject: [renum] Work plan towards IETF 81 and contributions needed
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2011 01:07:47 -0000

Hi, all,

Since 6renum WG is chartered, we are now starting the preparation towards IETF 81. As described in the charter, "RFC 4192, RFC 5887, and draft-jiang-ipv6-site-renum-guideline are starting points for this work."

The current work plan is to split draft-jiang-ipv6-site-renum-guideline into two drafts according to the WG charter. Draft-jiang-6renum-enterprise would include newly-added enterprise renumbering scenario description and considerations/guidelines for enterprise renumbering events (mainly section 2 of draft-jiang-ipv6-site-renum-guideline). Draft-liu-6renum-gap-analysis would take the section 4 of draft-jiang-ipv6-site-renum-guideline "Requests to extend current protocol" as the start point of gap analysis and expand it.

Please read and comments on draft-jiang-ipv6-site-renum-guideline while we are working on the new drafts. We have a short time (less than three weeks before 00 version cut-off date). Any contributions/input are welcome. We are open to take additional contributors/authors.

Many thanks and best regards,

Sheng

From wesley.george@twcable.com  Tue Jun 21 10:24:28 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 948E211E80D3 for <renum@ietfa.amsl.com>; Tue, 21 Jun 2011 10:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.181
X-Spam-Level: 
X-Spam-Status: No, score=-0.181 tagged_above=-999 required=5 tests=[AWL=0.282,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DkjIKuiC8CPk for <renum@ietfa.amsl.com>; Tue, 21 Jun 2011 10:24:27 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 68F6D11E80AC for <renum@ietf.org>; Tue, 21 Jun 2011 10:24:27 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.65,402,1304308800"; d="scan'208";a="240885639"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 21 Jun 2011 13:23:36 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.28]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Tue, 21 Jun 2011 13:24:22 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: Jiangsheng <jiangsheng@huawei.com>, "renum@ietf.org" <renum@ietf.org>
Date: Tue, 21 Jun 2011 13:24:21 -0400
Thread-Topic: Work plan towards IETF 81 and contributions needed
Thread-Index: AcwrwcvlsrPAuXl6SG+Dtl6lqhdflQEbZKWw
Message-ID: <34E4F50CAFA10349A41E0756550084FB0A10549D@PRVPEXVS04.corp.twcable.com>
References: <5D36713D8A4E7348A7E10DF7437A4B928636A8@SZXEML504-MBX.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B928636A8@SZXEML504-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [renum] Work plan towards IETF 81 and contributions needed
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 17:24:28 -0000

I have reviewed draft-jiang-ipv6-site-renum-guideline and have some comment=
s.

Section 2.1 -
I would remove "DHCPv6 reconfiguration "doesn't appear to be widely used fo=
r bulk renumbering purposes" [RFC5887]." In reality, none of these things a=
re really used for bulk renumbering today. What we're supposed to be talkin=
g about is how to make that easier. Also, right now, this document favors S=
LAAC over DHCPv6. The reality is that no one is likely to choose SLAAC over=
 DHCPv6 simply because of renumbering. Other factors will contribute to tha=
t decision, so it's better for us to simply discuss how to manage it most e=
ffectively with each. Discussing pros and cons for each is appropriate, but=
 we need to be more even-handed in discussing how to manage renumbering reg=
ardless of which technology is used.

There is currently little or no discussion regarding renumbering of things =
with statically assigned addresses.
I think that there are probably two types of hosts - those who think that t=
hey need a static address, and those who actually do. It would be a good id=
ea to discuss some of the places where typically static addresses are used,=
 but could be eliminated in favor of dynamic addressing vs the places where=
 it's likely static addresses are still required. You make reference to usi=
ng dynamic DNS updates, but don't really draw the conclusion that this can =
be used to reduce dependence on statically-configured addresses.
In the case of static addressing, there are probably some pointers that can=
 be made regarding how addresses are generated and allocated to ease renumb=
ering, such as using a consistent addressing scheme across sites and purpos=
es, so that if the network prefix must change, it's a simple find and repla=
ce of the upper bits. This may not work in all cases, because sometimes the=
 size of the network prefix changes or there are other major changes to the=
 address structure, but it may still be worth being discussed here.

DNS - it's not enough to simply say "It is recommended that the site have a=
n automatic and systematic
      procedure for updating/synchronising its DNS records" without making =
a recommendation as to how this might be implemented - point to a BCP (if e=
xist, or one is needed) for doing this on common platforms. Otherwise this =
is in a similar category to the assertion that making other global changes =
to your network configuration is easier if you have an automated tool to pu=
sh configuration out to your network. Nice to know, but not actually helpfu=
l to the discussion.

Miscellaneous-
What does the following mean? "Addresses should not be used to configure ne=
twork connectivity, such as tunnels." That you should point tunnel endpoint=
s to FQDNs instead of IP addresses? Why specifically mention tunnels? What =
do you mean by configure network connectivity?


2.2 -
This section has several good recommendations, but they are not by any mean=
s recommendations to implement by default in a network. I see all of these =
as temporary changes made just prior to renumbering in order to manage a pe=
nding renumber. Recommending them as temporary changes would go a long way =
to reduce the cost/burden tradeoff in using any of these things to ease a r=
enumber. In other words, all of section 2.2 probably belongs in section 2.3=
.

2.3 - This takes a very limited view of renumbering and treats it still as =
a very light-switch or flag day event. Remember that because IPv6 is capabl=
e of assigning multiple addresses to the same interface, it is quite possib=
le to assign a new address, update the external pointers (DNS, configuratio=
n, etc), and then remove the old address. It's even possible to do this for=
 things like BGP sessions (though today it requires standing up a duplicate=
 BGP session, which has an opportunity for optimization as a part of this e=
ffort). Depending on the network, it may be possible to do this over a long=
 enough period of time that impact to in-flight traffic is minimal, as sess=
ions naturally end and are restarted using the new configuration, leases ag=
e out, etc.
The informative references list RFC4192, but the text does not mention it a=
t all. If anything this should be taking that RFC and building on it - poin=
ting out additional gaps in that process, places where the protocols could =
be updated to correct problems today, etc.

It may even make sense to recommend as a part of section 4/gap analysis tha=
t DHCPv6 and SLAAC supports this type of make-before-break provisioning, wh=
ere it advises the host that there is a new prefix/address which is ADDED t=
o the existing address rather than replacing it, and then gives the host ti=
me to make the migration (update its preferences for each prefix, signal up=
stream applications, etc) at a point that is appropriate for it before forc=
ing the switch while the host may be in mid-communication. Even if this hap=
pens gradually over the hundreds of flows moving through a host, it will al=
low a reduction in the amount of traffic impact caused by the eventual remo=
val of the old prefix.

2.4 - embedded RP needs an informative reference to RFC 3956


Thanks,

Wes George

-----Original Message-----
From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of J=
iangsheng
Sent: Wednesday, June 15, 2011 9:07 PM
To: renum@ietf.org
Subject: [renum] Work plan towards IETF 81 and contributions needed

Hi, all,

Since 6renum WG is chartered, we are now starting the preparation towards I=
ETF 81. As described in the charter, "RFC 4192, RFC 5887, and draft-jiang-i=
pv6-site-renum-guideline are starting points for this work."

The current work plan is to split draft-jiang-ipv6-site-renum-guideline int=
o two drafts according to the WG charter. Draft-jiang-6renum-enterprise wou=
ld include newly-added enterprise renumbering scenario description and cons=
iderations/guidelines for enterprise renumbering events (mainly section 2 o=
f draft-jiang-ipv6-site-renum-guideline). Draft-liu-6renum-gap-analysis wou=
ld take the section 4 of draft-jiang-ipv6-site-renum-guideline "Requests to=
 extend current protocol" as the start point of gap analysis and expand it.

Please read and comments on draft-jiang-ipv6-site-renum-guideline while we =
are working on the new drafts. We have a short time (less than three weeks =
before 00 version cut-off date). Any contributions/input are welcome. We ar=
e open to take additional contributors/authors.

Many thanks and best regards,

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

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

From jiangsheng@huawei.com  Wed Jun 22 03:01:00 2011
Return-Path: <jiangsheng@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B018711E80DC for <renum@ietfa.amsl.com>; Wed, 22 Jun 2011 03:01:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id luncMoA2lkHu for <renum@ietfa.amsl.com>; Wed, 22 Jun 2011 03:00:59 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7BBE111E8098 for <renum@ietf.org>; Wed, 22 Jun 2011 03:00:59 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LN6001OEROELB@szxga05-in.huawei.com> for renum@ietf.org; Wed, 22 Jun 2011 17:57:51 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LN600G4XROEDK@szxga05-in.huawei.com> for renum@ietf.org; Wed, 22 Jun 2011 17:57:50 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml201-edg.china.huawei.com) ([172.24.2.119])	by szxrg01-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ABZ80727; Wed, 22 Jun 2011 17:57:48 +0800 (CST)
Received: from SZXEML407-HUB.china.huawei.com (10.82.67.94) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 22 Jun 2011 17:57:42 +0800
Received: from SZXEML504-MBX.china.huawei.com ([169.254.8.3]) by szxeml407-hub.china.huawei.com ([169.254.34.53]) with mapi id 14.01.0270.001; Wed, 22 Jun 2011 17:57:48 +0800
Date: Wed, 22 Jun 2011 09:56:40 +0000
From: Jiangsheng <jiangsheng@huawei.com>
In-reply-to: <34E4F50CAFA10349A41E0756550084FB0A10549D@PRVPEXVS04.corp.twcable.com>
X-Originating-IP: [10.110.98.101]
To: "George, Wesley" <wesley.george@twcable.com>, "renum@ietf.org" <renum@ietf.org>
Message-id: <5D36713D8A4E7348A7E10DF7437A4B928654DE@SZXEML504-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: en-GB, zh-CN, en-US
Thread-topic: Work plan towards IETF 81 and contributions needed
Thread-index: AcwrwcvlsrPAuXl6SG+Dtl6lqhdflQEbZKWwACQZccA=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <5D36713D8A4E7348A7E10DF7437A4B928636A8@SZXEML504-MBX.china.huawei.com> <34E4F50CAFA10349A41E0756550084FB0A10549D@PRVPEXVS04.corp.twcable.com>
Subject: Re: [renum] Work plan towards IETF 81 and contributions needed
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 10:01:00 -0000

George,

Thanks for your valuable comments. Please see my replies in lines.

Sheng

> -----Original Message-----
> From: George, Wesley [mailto:wesley.george@twcable.com]
> Sent: Wednesday, June 22, 2011 1:24 AM
> To: Jiangsheng; renum@ietf.org
> Subject: RE: Work plan towards IETF 81 and contributions needed
> 
> I have reviewed draft-jiang-ipv6-site-renum-guideline and have some
> comments.
> 
> Section 2.1 -
> I would remove "DHCPv6 reconfiguration "doesn't appear to be widely
> used for bulk renumbering purposes" [RFC5887]." 

Will do in the new draft-jiang-6renum-enterprise.

> In reality, none of
> these things are really used for bulk renumbering today. What we're
> supposed to be talking about is how to make that easier. Also, right
> now, this document favors SLAAC over DHCPv6. The reality is that no one
> is likely to choose SLAAC over DHCPv6 simply because of renumbering.
> Other factors will contribute to that decision, so it's better for us
> to simply discuss how to manage it most effectively with each.
> Discussing pros and cons for each is appropriate, but we need to be
> more even-handed in discussing how to manage renumbering regardless of
> which technology is used.
> 
> There is currently little or no discussion regarding renumbering of
> things with statically assigned addresses.

I am not sure we can cover this. If Ipv6 renumbering, the basic idea is the network change the prefix, then all addresses need to be changed accordingly. Statically assigned addresses seems not fit in this scenarios. Or I need more explanation.

> I think that there are probably two types of hosts - those who think
> that they need a static address, and those who actually do. It would be
> a good idea to discuss some of the places where typically static
> addresses are used, but could be eliminated in favor of dynamic
> addressing vs the places where it's likely static addresses are still
> required. You make reference to using dynamic DNS updates, but don't
> really draw the conclusion that this can be used to reduce dependence
> on statically-configured addresses.
> In the case of static addressing, there are probably some pointers that
> can be made regarding how addresses are generated and allocated to ease
> renumbering, such as using a consistent addressing scheme across sites
> and purposes, so that if the network prefix must change, it's a simple
> find and replace of the upper bits. This may not work in all cases,
> because sometimes the size of the network prefix changes or there are
> other major changes to the address structure, but it may still be worth
> being discussed here.
> 
> DNS - it's not enough to simply say "It is recommended that the site
> have an automatic and systematic
>       procedure for updating/synchronising its DNS records" without
> making a recommendation as to how this might be implemented - point to
> a BCP (if exist, or one is needed) for doing this on common platforms.
> Otherwise this is in a similar category to the assertion that making
> other global changes to your network configuration is easier if you
> have an automated tool to push configuration out to your network. Nice
> to know, but not actually helpful to the discussion.

Have added RFC2874 "DNS Extensions to Support IPv6 Address Aggregation and Renumbering" in the new draft
 
> Miscellaneous-
> What does the following mean? "Addresses should not be used to
> configure network connectivity, such as tunnels." That you should point
> tunnel endpoints to FQDNs instead of IP addresses? Why specifically
> mention tunnels? What do you mean by configure network connectivity?

Will add more clarification.
 
> 2.2 -
> This section has several good recommendations, but they are not by any
> means recommendations to implement by default in a network. I see all
> of these as temporary changes made just prior to renumbering in order
> to manage a pending renumber. Recommending them as temporary changes
> would go a long way to reduce the cost/burden tradeoff in using any of
> these things to ease a renumber. In other words, all of section 2.2
> probably belongs in section 2.3.

En... It seems make sense. However, I am not sure to put section 2.2 into section 2.3. This contents are worth an independent section with a changed title or more clarification text. 
 
> 2.3 - This takes a very limited view of renumbering and treats it still
> as a very light-switch or flag day event. Remember that because IPv6 is
> capable of assigning multiple addresses to the same interface, it is
> quite possible to assign a new address, update the external pointers
> (DNS, configuration, etc), and then remove the old address. It's even
> possible to do this for things like BGP sessions (though today it
> requires standing up a duplicate BGP session, which has an opportunity
> for optimization as a part of this effort). Depending on the network,
> it may be possible to do this over a long enough period of time that
> impact to in-flight traffic is minimal, as sessions naturally end and
> are restarted using the new configuration, leases age out, etc.
> The informative references list RFC4192, but the text does not mention
> it at all. If anything this should be taking that RFC and building on
> it - pointing out additional gaps in that process, places where the
> protocols could be updated to correct problems today, etc.

Good point. Will add some text into the new version. However, the gaps will be addressed in a separated document.
 
> It may even make sense to recommend as a part of section 4/gap analysis
> that DHCPv6 and SLAAC supports this type of make-before-break
> provisioning, where it advises the host that there is a new
> prefix/address which is ADDED to the existing address rather than
> replacing it, and then gives the host time to make the migration
> (update its preferences for each prefix, signal upstream applications,
> etc) at a point that is appropriate for it before forcing the switch
> while the host may be in mid-communication. Even if this happens
> gradually over the hundreds of flows moving through a host, it will
> allow a reduction in the amount of traffic impact caused by the
> eventual removal of the old prefix.

Will address this in 6renum gap analysis draft.
 
> 2.4 - embedded RP needs an informative reference to RFC 3956

Will add this.

Thanks,

Sheng
 
> 
> Thanks,
> 
> Wes George
> 
> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of Jiangsheng
> Sent: Wednesday, June 15, 2011 9:07 PM
> To: renum@ietf.org
> Subject: [renum] Work plan towards IETF 81 and contributions needed
> 
> Hi, all,
> 
> Since 6renum WG is chartered, we are now starting the preparation
> towards IETF 81. As described in the charter, "RFC 4192, RFC 5887, and
> draft-jiang-ipv6-site-renum-guideline are starting points for this
> work."
> 
> The current work plan is to split draft-jiang-ipv6-site-renum-guideline
> into two drafts according to the WG charter. Draft-jiang-6renum-
> enterprise would include newly-added enterprise renumbering scenario
> description and considerations/guidelines for enterprise renumbering
> events (mainly section 2 of draft-jiang-ipv6-site-renum-guideline).
> Draft-liu-6renum-gap-analysis would take the section 4 of draft-jiang-
> ipv6-site-renum-guideline "Requests to extend current protocol" as the
> start point of gap analysis and expand it.
> 
> Please read and comments on draft-jiang-ipv6-site-renum-guideline while
> we are working on the new drafts. We have a short time (less than three
> weeks before 00 version cut-off date). Any contributions/input are
> welcome. We are open to take additional contributors/authors.
> 
> Many thanks and best regards,
> 
> Sheng
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
> 
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject
> to copyright belonging to Time Warner Cable. This E-mail is intended
> solely for the use of the individual or entity to which it is addressed.
> If you are not the intended recipient of this E-mail, you are hereby
> notified that any dissemination, distribution, copying, or action taken
> in relation to the contents of and attachments to this E-mail is
> strictly prohibited and may be unlawful. If you have received this E-
> mail in error, please notify the sender immediately and permanently
> delete the original and any copy of this E-mail and any printout.

From brian.e.carpenter@gmail.com  Wed Jun 22 05:12:30 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9C4D11E80BC for <renum@ietfa.amsl.com>; Wed, 22 Jun 2011 05:12:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.501
X-Spam-Level: 
X-Spam-Status: No, score=-103.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KoddHgcy-A3c for <renum@ietfa.amsl.com>; Wed, 22 Jun 2011 05:12:29 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7FFFA11E8104 for <renum@ietf.org>; Wed, 22 Jun 2011 05:12:29 -0700 (PDT)
Received: by fxm15 with SMTP id 15so646936fxm.31 for <renum@ietf.org>; Wed, 22 Jun 2011 05:12:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=IRsCXRepLIw7xrUrBJc01bZS+SLzIgIh8GKK/+Juggo=; b=BJU+UwbqAvqqekZnyUTsSwh+jMcN2kl+yvcOxPJ9iXgG9oPinWrOZJASkyFbspHnxn 5ng/xxMwT0g0nHqQcfh9Wwt28SNV7d+PXblY4E/bhKRDg7UH4eCUBZ8BePic1DEJds0t ob8f5EGnDJDlLi8jp4I8DyxBSC5fHy7oRFRrE=
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=E0+3+9jYGn+3jNTvBTanb7StfpY7vnDpGybULkrmX3m7J/glO8d8I3p39NcvwlsXmK FHw43sIbfxWSF6BduDljYFpQuqI4h3AYc/1Ik4I+DoZ/198GuU00Kjj7mkG0N9SI48UG hXJDD2rixWlLwKi2rkT2yQ8PBRimfi5xwXUs8=
Received: by 10.223.32.142 with SMTP id c14mr769436fad.59.1308744743977; Wed, 22 Jun 2011 05:12:23 -0700 (PDT)
Received: from [10.255.25.96] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id r10sm294480fah.2.2011.06.22.05.12.21 (version=SSLv3 cipher=OTHER); Wed, 22 Jun 2011 05:12:22 -0700 (PDT)
Message-ID: <4E01DC1B.6070509@gmail.com>
Date: Thu, 23 Jun 2011 00:12:11 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jiangsheng <jiangsheng@huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B928636A8@SZXEML504-MBX.china.huawei.com>	<34E4F50CAFA10349A41E0756550084FB0A10549D@PRVPEXVS04.corp.twcable.com> <5D36713D8A4E7348A7E10DF7437A4B928654DE@SZXEML504-MBX.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B928654DE@SZXEML504-MBX.china.huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Work plan towards IETF 81 and contributions needed
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 12:12:30 -0000

On 2011-06-22 21:56, Jiangsheng wrote:
...
>> There is currently little or no discussion regarding renumbering of
>> things with statically assigned addresses.
> 
> I am not sure we can cover this. If Ipv6 renumbering, the basic idea is the network change the prefix, then all addresses need to be changed accordingly. Statically assigned addresses seems not fit in this scenarios. Or I need more explanation.

I'm not sure we can standardise anything for this but we can certainly write
BCP-type recommendations that configuration data for static addresses SHOULD
be kept in a central repository. I wonder if there can't be a protocol mechanism
in fact: get a dynamic address, ask a configuration server "I am server1.example.com,
please tell me my static address".

    Brian

From wesley.george@twcable.com  Wed Jun 22 12:34:30 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37EB011E808A for <renum@ietfa.amsl.com>; Wed, 22 Jun 2011 12:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.212
X-Spam-Level: 
X-Spam-Status: No, score=-0.212 tagged_above=-999 required=5 tests=[AWL=0.251,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oW0rYYrmbMbL for <renum@ietfa.amsl.com>; Wed, 22 Jun 2011 12:34:29 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id D9BBD11E8073 for <renum@ietf.org>; Wed, 22 Jun 2011 12:34:28 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.65,407,1304308800"; d="scan'208";a="241424620"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 22 Jun 2011 15:33:36 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.28]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Wed, 22 Jun 2011 15:34:27 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Jiangsheng <jiangsheng@huawei.com>
Date: Wed, 22 Jun 2011 15:34:26 -0400
Thread-Topic: [renum] Work plan towards IETF 81 and contributions needed
Thread-Index: Acww1acsTgKj3aKLTpCNfynwndzEbAABasfw
Message-ID: <34E4F50CAFA10349A41E0756550084FB0A105BC0@PRVPEXVS04.corp.twcable.com>
References: <5D36713D8A4E7348A7E10DF7437A4B928636A8@SZXEML504-MBX.china.huawei.com> <34E4F50CAFA10349A41E0756550084FB0A10549D@PRVPEXVS04.corp.twcable.com> <5D36713D8A4E7348A7E10DF7437A4B928654DE@SZXEML504-MBX.china.huawei.com> <4E01DC1B.6070509@gmail.com>
In-Reply-To: <4E01DC1B.6070509@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Work plan towards IETF 81 and contributions needed
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 19:34:30 -0000

DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogQnJpYW4gRSBDYXJwZW50ZXIgW21h
aWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dDQpTZW50OiBXZWRuZXNkYXksIEp1bmUg
MjIsIDIwMTEgODoxMiBBTQ0KVG86IEppYW5nc2hlbmcNCkNjOiBHZW9yZ2UsIFdlc2xleTsgcmVu
dW1AaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbcmVudW1dIFdvcmsgcGxhbiB0b3dhcmRzIElFVEYg
ODEgYW5kIGNvbnRyaWJ1dGlvbnMgbmVlZGVkDQoNCk9uIDIwMTEtMDYtMjIgMjE6NTYsIEppYW5n
c2hlbmcgd3JvdGU6DQouLi4NCj4+IFRoZXJlIGlzIGN1cnJlbnRseSBsaXR0bGUgb3Igbm8gZGlz
Y3Vzc2lvbiByZWdhcmRpbmcgcmVudW1iZXJpbmcgb2YNCj4+IHRoaW5ncyB3aXRoIHN0YXRpY2Fs
bHkgYXNzaWduZWQgYWRkcmVzc2VzLg0KPg0KPiBJIGFtIG5vdCBzdXJlIHdlIGNhbiBjb3ZlciB0
aGlzLiBJZiBJcHY2IHJlbnVtYmVyaW5nLCB0aGUgYmFzaWMgaWRlYSBpcyB0aGUgbmV0d29yayBj
aGFuZ2UgdGhlIHByZWZpeCwgdGhlbiBhbGwgYWRkcmVzc2VzIG5lZWQgdG8gYmUgY2hhbmdlZCBh
Y2NvcmRpbmdseS4gU3RhdGljYWxseSBhc3NpZ25lZCBhZGRyZXNzZXMgc2VlbXMgbm90IGZpdCBp
biB0aGlzIHNjZW5hcmlvcy4gT3IgSSBuZWVkIG1vcmUgZXhwbGFuYXRpb24uDQoNCkknbSBub3Qg
c3VyZSB3ZSBjYW4gc3RhbmRhcmRpc2UgYW55dGhpbmcgZm9yIHRoaXMgYnV0IHdlIGNhbiBjZXJ0
YWlubHkgd3JpdGUNCkJDUC10eXBlIHJlY29tbWVuZGF0aW9ucyB0aGF0IGNvbmZpZ3VyYXRpb24g
ZGF0YSBmb3Igc3RhdGljIGFkZHJlc3NlcyBTSE9VTEQNCmJlIGtlcHQgaW4gYSBjZW50cmFsIHJl
cG9zaXRvcnkuIEkgd29uZGVyIGlmIHRoZXJlIGNhbid0IGJlIGEgcHJvdG9jb2wgbWVjaGFuaXNt
DQppbiBmYWN0OiBnZXQgYSBkeW5hbWljIGFkZHJlc3MsIGFzayBhIGNvbmZpZ3VyYXRpb24gc2Vy
dmVyICJJIGFtIHNlcnZlcjEuZXhhbXBsZS5jb20sDQpwbGVhc2UgdGVsbCBtZSBteSBzdGF0aWMg
YWRkcmVzcyIuDQoNCldFRz4gU28gaW4gbXkgbWluZCwgbWFraW5nIHJlbnVtYmVyaW5nIGVhc2ll
ciBmYWxscyBpbnRvIGEgY291cGxlIG9mIGNhdGVnb3JpZXM6DQoxKSBkb2N1bWVudGluZyBob3cg
dG8gbGV2ZXJhZ2UgZHluYW1pYyBwcm90b2NvbHMgdG8gdGhlIG1heGltdW0gZXh0ZW50IHdoZW4g
cmVudW1iZXJpbmcgaXMgcmVxdWlyZWQNCjIpIGlkZW50aWZ5aW5nIGdhcHMgYW5kIHByb3Bvc2lu
ZyBzb2x1dGlvbnMgaW4gZHluYW1pYyBwcm90b2NvbHMgdG8gbWFrZSByZW51bWJlcmluZyBldmVu
IGVhc2llcg0KMykgZG9jdW1lbnRpbmcgaG93IHRvIGxpbWl0IHRoZSBwbGFjZXMgd2hlcmUgc3Rh
dGljIGFkZHJlc3NlcyBtdXN0IGJlIHVzZWQgKHZzIEZRRE4gb3IgYXV0b2NvbmYpDQo0KSBJZGVu
dGlmeWluZyBnYXBzIGFuZCBwcm9wb3Npbmcgc29sdXRpb25zIGluIG90aGVyIGFyZWFzIHRvIHJl
ZHVjZSB0aGUgbnVtYmVyIG9mIHBsYWNlcyB0aGF0IHN0YXRpYyBhZGRyZXNzZXMgYXJlIHJlcXVp
cmVkDQo1KSBkb2N1bWVudGluZyBhbnkgZ2FwcyBpbiA0MTkyIHRvIG1ha2UgcmVudW1iZXJpbmcg
ZWFzaWVyIGZvciBhIHN0YXRpY2FsbHktbnVtYmVyZWQgc2V0IG9mIGhvc3RzIGFuZCBwb3RlbnRp
YWxseSBpZGVudGlmeWluZyBhIHByb2JsZW0gc3RhdGVtZW50IGZvciBpbXByb3ZpbmcgcmVudW1i
ZXJpbmcgZm9yIHN0YXRpYw0KDQpJIGFkbWl0IHRoYXQgIzQgYW5kIDUgYXJlIG5vbi10cml2YWws
IGJ1dCBJIHRoaW5rIHRoZXkgYXJlIHN0aWxsIHdpdGhpbiBvdXIgc2NvcGUuIFdlJ3JlIG5vdCBz
b2x2aW5nIG11Y2ggb2YgdGhlIHJlbnVtYmVyaW5nIHByb2JsZW0gaWYgd2UgbGltaXQgb3Vyc2Vs
dmVzIHRvIGR5bmFtaWNhbGx5LWFkZHJlc3NlZCBkZXZpY2VzLiBQZXJoYXBzIGluIG9yZGVyIHRv
IGJyZWFrIHRoaXMgaW50byBtYW5hZ2VhYmxlIGNodW5rcywgdGhpcyBkcmFmdCBhbmQgaXRzIGNv
bXBhbmlvbiBzdGF5cyBmb2N1c2VkIHNwZWNpZmljYWxseSBvbiBkeW5hbWljIGFuZCBhbm90aGVy
IHNldCBvZiBkcmFmdHMgYXJlIHNwdW4gdG8gY292ZXIgc3RhdGljPyBJJ20gbm90IHN1cmUgaG93
IG11Y2ggb3ZlcmxhcCB0aGVyZSB3b3VsZCBiZSwgYXMgaWYgaXQncyBhIGxvdCBpdCBtYWtlcyBs
ZXNzIHNlbnNlIHRvIGhhdmUgc2VwYXJhdGUgZHJhZnRzIGluc3RlYWQgb2Ygc2VwYXJhdGUgc2Vj
dGlvbnMgb2YgdGhlc2UgY29tbW9uIGRyYWZ0cy4uLg0KDQoNClRoaXMgRS1tYWlsIGFuZCBhbnkg
b2YgaXRzIGF0dGFjaG1lbnRzIG1heSBjb250YWluIFRpbWUgV2FybmVyIENhYmxlIHByb3ByaWV0
YXJ5IGluZm9ybWF0aW9uLCB3aGljaCBpcyBwcml2aWxlZ2VkLCBjb25maWRlbnRpYWwsIG9yIHN1
YmplY3QgdG8gY29weXJpZ2h0IGJlbG9uZ2luZyB0byBUaW1lIFdhcm5lciBDYWJsZS4gVGhpcyBF
LW1haWwgaXMgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9y
IGVudGl0eSB0byB3aGljaCBpdCBpcyBhZGRyZXNzZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRl
bmRlZCByZWNpcGllbnQgb2YgdGhpcyBFLW1haWwsIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVkIHRo
YXQgYW55IGRpc3NlbWluYXRpb24sIGRpc3RyaWJ1dGlvbiwgY29weWluZywgb3IgYWN0aW9uIHRh
a2VuIGluIHJlbGF0aW9uIHRvIHRoZSBjb250ZW50cyBvZiBhbmQgYXR0YWNobWVudHMgdG8gdGhp
cyBFLW1haWwgaXMgc3RyaWN0bHkgcHJvaGliaXRlZCBhbmQgbWF5IGJlIHVubGF3ZnVsLiBJZiB5
b3UgaGF2ZSByZWNlaXZlZCB0aGlzIEUtbWFpbCBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUg
c2VuZGVyIGltbWVkaWF0ZWx5IGFuZCBwZXJtYW5lbnRseSBkZWxldGUgdGhlIG9yaWdpbmFsIGFu
ZCBhbnkgY29weSBvZiB0aGlzIEUtbWFpbCBhbmQgYW55IHByaW50b3V0Lg0K

From tjc@ecs.soton.ac.uk  Fri Jun 24 08:23:19 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C29011E8096 for <renum@ietfa.amsl.com>; Fri, 24 Jun 2011 08:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9IV2uIqpmGdt for <renum@ietfa.amsl.com>; Fri, 24 Jun 2011 08:23:17 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id F21A911E80A1 for <renum@ietf.org>; Fri, 24 Jun 2011 08:23:14 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5OFN7jf010617 for <renum@ietf.org>; Fri, 24 Jun 2011 16:23:07 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p5OFN7jf010617
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1308928987; bh=VLixR6H+3PMq7nHSWUZsGjYSPdg=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=lu/EPzMPOy6gkgrVf+MlN3fmQe80/PtM2TdeDy7ckc+bsFp0j1GoWzGUDgbu73Rtl p9qJPvOwwIwAHXZcDM49Neu9PsjXSr6Kkjn4qfi/ueOk0pqS4gUeIKOBBI0zYM9yWW qGEJAFfimCsAIYaYu1xY/8u/NXf3X8bCz1tJILGA=
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 n5NGN70366147078Ey ret-id none; Fri, 24 Jun 2011 16:23:07 +0100
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5OFN0RP008494 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Fri, 24 Jun 2011 16:23:04 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB0A105BC0@PRVPEXVS04.corp.twcable.com>
Date: Fri, 24 Jun 2011 16:22:59 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|32b604fda5ab95b09a8981647534d664n5NGN703tjc|ecs.soton.ac.uk|EAFD1137-8897-4B32-A281-5EF0364E4C48@ecs.soton.ac.uk>
References: <5D36713D8A4E7348A7E10DF7437A4B928636A8@SZXEML504-MBX.china.huawei.com> <34E4F50CAFA10349A41E0756550084FB0A10549D@PRVPEXVS04.corp.twcable.com> <5D36713D8A4E7348A7E10DF7437A4B928654DE@SZXEML504-MBX.china.huawei.com> <4E01DC1B.6070509@gmail.com> <34E4F50CAFA10349A41E0756550084FB0A105BC0@PRVPEXVS04.corp.twcable.com> <EAFD1137-8897-4B32-A281-5EF0364E4C48@ecs.soton.ac.uk>
To: renum@ietf.org
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n5NGN7036614707800; tid=n5NGN70366147078Ey; 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: p5OFN7jf010617
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [renum] Work plan towards IETF 81 and contributions needed
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 15:23:19 -0000

On 22 Jun 2011, at 20:34, George, Wesley wrote:

> WEG> So in my mind, making renumbering easier falls into a couple of =
categories:
> 1) documenting how to leverage dynamic protocols to the maximum extent =
when renumbering is required
> 2) identifying gaps and proposing solutions in dynamic protocols to =
make renumbering even easier
> 3) documenting how to limit the places where static addresses must be =
used (vs FQDN or autoconf)
> 4) Identifying gaps and proposing solutions in other areas to reduce =
the number of places that static addresses are required
> 5) documenting any gaps in 4192 to make renumbering easier for a =
statically-numbered set of hosts and potentially identifying a problem =
statement for improving renumbering for static
>=20
> I admit that #4 and 5 are non-trival, but I think they are still =
within our scope. We're not solving much of the renumbering problem if =
we limit ourselves to dynamically-addressed devices. Perhaps in order to =
break this into manageable chunks, this draft and its companion stays =
focused specifically on dynamic and another set of drafts are spun to =
cover static? I'm not sure how much overlap there would be, as if it's a =
lot it makes less sense to have separate drafts instead of separate =
sections of these common drafts...

I think this type of analysis is useful. =20

Our charter focuses on producing two deliverables, one being an =
enterprise scenario text that includes documentation of existing =
practices and capabilities (which would include points 1 and 3 above), =
the other being a gap analysis, which can also draw on RFC4192 and =
RFC5877 (and include points 2, 4 and 5 above).

We should have a WG slot in Quebec, and the deadline for -00 drafts is =
Monday week (4th July).  I believe Sheng is working towards splitting =
his previous draft into starting points for the two new texts, and so =
I'd encourage any interested authors or contributors to contact Sheng to =
work on that over the next few days.   We can then use the meeting slot =
to have a good discussion about those texts, and hopefully generate =
pointers and ideas for their further development after the meeting.

Tim=

From tjc@ecs.soton.ac.uk  Sat Jun 25 02:30:14 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4771F0C37 for <renum@ietfa.amsl.com>; Sat, 25 Jun 2011 02:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ywfKLBWnTGLQ for <renum@ietfa.amsl.com>; Sat, 25 Jun 2011 02:30:13 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4931F0C35 for <renum@ietf.org>; Sat, 25 Jun 2011 02:30:03 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5P9TsSK001960 for <renum@ietf.org>; Sat, 25 Jun 2011 10:29:54 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p5P9TsSK001960
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1308994194; bh=0jJcn8VsC+791bSAXwUoFM9ao18=; h=Subject:References:From:Date:To:Mime-Version; b=1AmXbAr8IOVaXB5DyJy6jQ29aqom+Rh7bdVJmSjOZDAcGLZwDeV1S4rcj+nV+9v8B /wQrPeCRjpgRSV9cVgvSLb4s1s9V+X2xhXIjVCnmwwAfXdeqGSgRVw9G5S5iTXjRLp Ggin0Oo0z+VRsL/37NmRwhpDd2BGPwIiRocbSc6E=
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 n5OAYs0366150169aW ret-id none; Sat, 25 Jun 2011 10:29:54 +0100
Received: from [172.20.10.2] ([82.132.248.9]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5P9TdUO008981 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Sat, 25 Jun 2011 10:29:45 +0100
References: <20110624183513.7035311E81A8@ietfa.amsl.com> <F8CD0B2F-A3AA-4B5E-8DCC-639CFDF61828@ecs.soton.ac.uk>
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=Apple-Mail-2--25501643
X-Mailer: iPad Mail (8J2)
Message-ID: <EMEW3|7658544c4f84448b9453af0155c722b0n5OAYs03tjc|ecs.soton.ac.uk|F8CD0B2F-A3AA-4B5E-8DCC-639CFDF61828@ecs.soton.ac.uk>
Date: Sat, 25 Jun 2011 10:29:32 +0100
To: "renum@ietf.org" <renum@ietf.org>
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPad Mail 8J2)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n5OAYs036615016900; tid=n5OAYs0366150169aW; 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: p5P9TsSK001960
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: [renum] Fwd: Please help the Nomcom
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 09:30:14 -0000

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

Hi,

Please do consider putting yourself forward to help the NomCom. I believe th=
e requirement is having attended 3 of the past 5 IETF meetings.  If you have=
 specific questions, I'm sure Suresh would be happy to field them.

Tim


Begin forwarded message:

> From: NomCom Chair <nomcom-chair@ietf.org>
> Date: 24 June 2011 19:35:13 GMT+01:00
> To: Working Group Chairs <wgchairs@ietf.org>
> Subject: Please help the Nomcom
>=20

> Hi WG chairs,
>  We have had a good response to the first call for volunteers but the=20
> rate at which new volunteers are coming in is slowing down. The Nomcom=20
> process is best served by a large pool of volunteers drawn from a wide=20
> spectrum of IETF attendees. Where else would we find this wide spectrum
> if not in the WG mailing lists.
>=20
> I would really appreciate it if you can forward the message onto your
> working group mailing lists.=20
>=20
> The latest volunteer status and the second call for volunteers can be
> found at
> https://datatracker.ietf.org/ann/nomcom/2964/
>=20
> Thanks in advance for your help.
>=20
> Suresh Krishnan
> Nomcom Chair 2011-2012
> Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com

--Apple-Mail-2--25501643
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><body bgcolor=3D"#FFFFFF"><div>Hi,</div><div><br></div><div>Please do c=
onsider putting yourself forward to help the NomCom. I believe the requireme=
nt is having attended 3 of the past 5 IETF meetings. &nbsp;If you have speci=
fic questions, I'm sure Suresh would be happy to field them.</div><div><br><=
/div><div>Tim<br><br></div><div><br>Begin forwarded message:<br><br></div><b=
lockquote type=3D"cite"><div><b>From:</b> NomCom Chair &lt;<a href=3D"mailto=
:nomcom-chair@ietf.org">nomcom-chair@ietf.org</a>&gt;<br><b>Date:</b> 24 Jun=
e 2011 19:35:13 GMT+01:00<br><b>To:</b> Working Group Chairs &lt;<a href=3D"=
mailto:wgchairs@ietf.org">wgchairs@ietf.org</a>&gt;<br><b>Subject:</b> <b>Pl=
ease help the Nomcom</b><br><br></div></blockquote><div></div><blockquote ty=
pe=3D"cite"><div><span>Hi WG chairs,</span><br><span> &nbsp;We have had a go=
od response to the first call for volunteers but the </span><br><span>rate a=
t which new volunteers are coming in is slowing down. The Nomcom </span><br>=
<span>process is best served by a large pool of volunteers drawn from a wide=
 </span><br><span>spectrum of IETF attendees. Where else would we find this w=
ide spectrum</span><br><span>if not in the WG mailing lists.</span><br><span=
></span><br><span>I would really appreciate it if you can forward the messag=
e onto your</span><br><span>working group mailing lists. </span><br><span></=
span><br><span>The latest volunteer status and the second call for volunteer=
s can be</span><br><span>found at</span><br><span><a href=3D"https://datatra=
cker.ietf.org/ann/nomcom/2964/">https://datatracker.ietf.org/ann/nomcom/2964=
/</a></span><br><span></span><br><span>Thanks in advance for your help.</spa=
n><br><span></span><br><span>Suresh Krishnan</span><br><span>Nomcom Chair 20=
11-2012</span><br><span>Email: <a href=3D"mailto:nomcom-chair@ietf.org">nomc=
om-chair@ietf.org</a>, <a href=3D"mailto:suresh.krishnan@ericsson.com"><a hr=
ef=3D"mailto:suresh.krishnan@ericsson.com">suresh.krishnan@ericsson.com</a><=
/a></span><br></div></blockquote></body></html>=

--Apple-Mail-2--25501643--

From tjc@ecs.soton.ac.uk  Wed Jun 29 02:36:47 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3508421F86A4 for <renum@ietfa.amsl.com>; Wed, 29 Jun 2011 02:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Ag-+roXbQtP for <renum@ietfa.amsl.com>; Wed, 29 Jun 2011 02:36:46 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 4EFC721F86A3 for <renum@ietf.org>; Wed, 29 Jun 2011 02:36:44 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5T9abJ7005445 for <renum@ietf.org>; Wed, 29 Jun 2011 10:36:37 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p5T9abJ7005445
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1309340197; bh=Yn60nxBRx/8rLeqTlC1bVbeAYF0=; h=Subject:References:From:In-Reply-To:Date:To:Mime-Version; b=hTArAU9JyGWPOj2pGpySkzYHu053OHBe8iiQjM8IOy7fSmpddr+RUzVtev/m6r9Hj Vz7dXXUeoGrMASBHrUlEbIMxwsbtTsTAB1c8RVqlLo6/2Xl5u6aIVXTKCRPlohdA3m Hslf/oqg1wI+/SFKjoLE8L76ix0eA0LxrNw38gxo=
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 n5SAab0366105444x9 ret-id none; Wed, 29 Jun 2011 10:36:37 +0100
Received: from [IPv6:2001:630:d0:f103::c0:ffee] ([IPv6:2001:630:d0:f103::c0:ffee]) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5T9aVAe001746 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Wed, 29 Jun 2011 10:36:31 +0100
References: <20110628171341.1B0AA22800E@ietfa.amsl.com> <E04190C4-E739-4464-85B3-1DC95E97B7C8@ecs.soton.ac.uk>
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=Apple-Mail-3-320509245
In-Reply-To: <20110628171341.1B0AA22800E@ietfa.amsl.com>
Message-ID: <EMEW3|a5eadd4c4f83538e953ff2fb7b2e7d9dn5SAab03tjc|ecs.soton.ac.uk|E04190C4-E739-4464-85B3-1DC95E97B7C8@ecs.soton.ac.uk>
Date: Wed, 29 Jun 2011 10:36:30 +0100
To: renum@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n5SAab036610544400; tid=n5SAab0366105444x9; 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: p5T9abJ7005445
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: [renum] 6RENUM - session has been scheduled for IETF 81
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2011 09:36:47 -0000

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

Hi,

We are currently scheduled for 15.10-16.10 on the Wednesday.  We =
requested a 1.5hr slot, but this is the best available at the moment. =
The other offering clashed with 6man. =20

I'm confident we can have a productive first meeting in one hour if we =
minimise powerpoint and focus on discussing open issues.  We're =
expecting initial personal drafts for the two deliverables we're =
chartered to work on to be submitted before this Monday's cut-off, which =
should help drive the discussion.  If you're interested in contributing =
directly to these, please contact Sheng (jiangsheng@huawei.com).

If anyone has any specific item they wish to present in Quebec relevant =
to the two deliverables, please let me know.

Tim

On 28 Jun 2011, at 18:13, IETF Secretariat wrote:

> Dear Wanda Lo,
>=20
> The sessions that you have requested have been scheduled.
> Below is the scheduled session information followed by=20
> the information of sessions that you have requested.
>=20
> 6RENUM Session 1 (1.5 hours)
> Wednesday, Afternoon Session II 1510-1610
> Room Name: 206 A
> ----------------------------------------------
>=20
> Requested Information:
>=20
> ---------------------------------------------------------
> Working Group Name: 6renum
> Area Name: Operations and Management Area
> Session Requester: Wanda Lo
>=20
> Number of Sessions: 1
> Length of Session(s):  1.5 hours
>=20
>=20
> Number of Attendees: 100
> Conflicts to Avoid:
>  BOF or IRTF Session: Working Groups in the OPS, INT areas
>=20
> Special Requests:
>=20
> ---------------------------------------------------------

--Apple-Mail-3-320509245
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hi,<div><br></div><div>We are currently scheduled for 15.10-16.10 on =
the Wednesday. &nbsp;We requested a 1.5hr slot, but this is the best =
available at the moment. The other offering clashed with 6man. =
&nbsp;</div><div><br></div><div>I'm confident we can have a productive =
first meeting in one hour if we minimise powerpoint and focus on =
discussing open issues. &nbsp;We're expecting initial personal drafts =
for the two deliverables we're chartered to work on to be submitted =
before this Monday's cut-off, which should help drive the discussion. =
&nbsp;If you're interested in contributing directly to these, please =
contact Sheng (<a =
href=3D"mailto:jiangsheng@huawei.com">jiangsheng@huawei.com</a>).</div><di=
v><br></div><div>If anyone has any specific item they wish to present in =
Quebec relevant to the two deliverables, please let me =
know.</div><div><br></div><div>Tim</div><div><br><div><div>On 28 Jun =
2011, at 18:13, IETF Secretariat wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>Dear =
Wanda Lo,<br><br>The sessions that you have requested have been =
scheduled.<br>Below is the scheduled session information followed by =
<br>the information of sessions that you have requested.<br><br>6RENUM =
Session 1 (1.5 hours)<br>Wednesday, Afternoon Session II =
1510-1610<br>Room Name: 206 =
A<br>----------------------------------------------<br><br>Requested =
Information:<br><br>------------------------------------------------------=
---<br>Working Group Name: 6renum<br>Area Name: Operations and =
Management Area<br>Session Requester: Wanda Lo<br><br>Number of =
Sessions: 1<br>Length of Session(s): &nbsp;1.5 hours<br><br><br>Number =
of Attendees: 100<br>Conflicts to Avoid:<br> &nbsp;BOF or IRTF Session: =
Working Groups in the OPS, INT areas<br><br>Special =
Requests:<br><br>---------------------------------------------------------=
<font class=3D"Apple-style-span" color=3D"#000000"><font =
class=3D"Apple-style-span" =
color=3D"#144FAE"><br></font></font></div></blockquote></div></div></body>=
</html>=

--Apple-Mail-3-320509245--

From leo.liubing@huawei.com  Wed Jun 29 19:26:22 2011
Return-Path: <leo.liubing@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E39821F84F9 for <renum@ietfa.amsl.com>; Wed, 29 Jun 2011 19:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.788
X-Spam-Level: **
X-Spam-Status: No, score=2.788 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VPbycT1Lq2k4 for <renum@ietfa.amsl.com>; Wed, 29 Jun 2011 19:26:21 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 5579E21F8556 for <renum@ietf.org>; Wed, 29 Jun 2011 19:26:19 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNL005QD00SDV@szxga03-in.huawei.com> for renum@ietf.org; Thu, 30 Jun 2011 10:24:28 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNL0002Z00EIW@szxga03-in.huawei.com> for renum@ietf.org; Thu, 30 Jun 2011 10:24:28 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml207-edg.china.huawei.com) ([172.24.2.119])	by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ABP63254; Thu, 30 Jun 2011 10:24:27 +0800 (CST)
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 30 Jun 2011 10:24:23 +0800
Received: from SZXEML502-MBS.china.huawei.com ([169.254.2.87]) by szxeml409-hub.china.huawei.com ([169.254.89.141]) with mapi id 14.01.0270.001; Thu, 30 Jun 2011 10:24:27 +0800
Date: Thu, 30 Jun 2011 02:24:26 +0000
From: "Leo Liu(bing)" <leo.liubing@huawei.com>
In-reply-to: <EMEW3|32b604fda5ab95b09a8981647534d664n5NGN703tjc|ecs.soton.ac.uk|EAFD1137-8897-4B32-A281-5EF0364E4C48@ecs.soton.ac.uk>
X-Originating-IP: [10.110.98.62]
To: Tim Chown <tjc@ecs.soton.ac.uk>, "renum@ietf.org" <renum@ietf.org>
Message-id: <8AE0F17B87264D4CAC7DE0AA6C406F45017F4E51@SZXEML502-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [renum] Work plan towards IETF 81 and contributions needed
Thread-index: AcwrwcvlsrPAuXl6SG+Dtl6lqhdflQEbZKWwACQZccD//6WVgIAAe5AAgALeaYD/9uW/4A==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <5D36713D8A4E7348A7E10DF7437A4B928636A8@SZXEML504-MBX.china.huawei.com> <34E4F50CAFA10349A41E0756550084FB0A10549D@PRVPEXVS04.corp.twcable.com> <5D36713D8A4E7348A7E10DF7437A4B928654DE@SZXEML504-MBX.china.huawei.com> <4E01DC1B.6070509@gmail.com> <34E4F50CAFA10349A41E0756550084FB0A105BC0@PRVPEXVS04.corp.twcable.com> <EAFD1137-8897-4B32-A281-5EF0364E4C48@ecs.soton.ac.uk> <EMEW3|32b604fda5ab95b09a8981647534d664n5NGN703tjc|ecs.soton.ac.uk|EAFD1137-8897-4B32-A281-5EF0364E4C48@ecs.soton.ac.uk>
Subject: [renum] =?gb2312?b?tPC4tDogIFdvcmsgcGxhbiB0b3dhcmRzIElFVEYgODEg?= =?gb2312?b?YW5kIGNvbnRyaWJ1dGlvbnMgbmVlZGVk?=
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 02:26:22 -0000

SGksIFRpbQ0KDQpUaGFua3MgZm9yIHlvdXIgc3VnZ2VzdGlvbi4gQW5kIHRoYW5rcyBmb3IgR2Vv
cmdlJ3MgY29tbWVudHMgYWdhaW4uDQpSZXBsaWVzIGFyZSBpbmxpbmUuDQoNCi0tLS0t08q8/tSt
vP4tLS0tLQ0Kt6K8/sjLOiByZW51bS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86cmVudW0tYm91
bmNlc0BpZXRmLm9yZ10gtPqx7SBUaW0gQ2hvd24NCreiy83KsbzkOiAyMDExxOo21MIyNMjVIDIz
OjIzDQrK1bz+yMs6IHJlbnVtQGlldGYub3JnDQrW98ziOiBSZTogW3JlbnVtXSBXb3JrIHBsYW4g
dG93YXJkcyBJRVRGIDgxIGFuZCBjb250cmlidXRpb25zIG5lZWRlZA0KDQoNCk9uIDIyIEp1biAy
MDExLCBhdCAyMDozNCwgR2VvcmdlLCBXZXNsZXkgd3JvdGU6DQoNCj4+IFdFRz4gU28gaW4gbXkg
bWluZCwgbWFraW5nIHJlbnVtYmVyaW5nIGVhc2llciBmYWxscyBpbnRvIGEgY291cGxlIG9mIGNh
dGVnb3JpZXM6DQo+PiAxKSBkb2N1bWVudGluZyBob3cgdG8gbGV2ZXJhZ2UgZHluYW1pYyBwcm90
b2NvbHMgdG8gdGhlIG1heGltdW0gZXh0ZW50IHdoZW4gcmVudW1iZXJpbmcgaXMgcmVxdWlyZWQN
Cj4+IDIpIGlkZW50aWZ5aW5nIGdhcHMgYW5kIHByb3Bvc2luZyBzb2x1dGlvbnMgaW4gZHluYW1p
YyBwcm90b2NvbHMgdG8gbWFrZSByZW51bWJlcmluZyBldmVuIGVhc2llcg0KPj4zKSBkb2N1bWVu
dGluZyBob3cgdG8gbGltaXQgdGhlIHBsYWNlcyB3aGVyZSBzdGF0aWMgYWRkcmVzc2VzIG11c3Qg
YmUgdXNlZCAodnMgRlFETiBvciBhdXRvY29uZikNCj4+IDQpIElkZW50aWZ5aW5nIGdhcHMgYW5k
IHByb3Bvc2luZyBzb2x1dGlvbnMgaW4gb3RoZXIgYXJlYXMgdG8gcmVkdWNlIHRoZSBudW1iZXIg
b2YgcGxhY2VzIHRoYXQgc3RhdGljIGFkZHJlc3NlcyBhcmUgcmVxdWlyZWQNCj4+IDUpIGRvY3Vt
ZW50aW5nIGFueSBnYXBzIGluIDQxOTIgdG8gbWFrZSByZW51bWJlcmluZyBlYXNpZXIgZm9yIGEg
c3RhdGljYWxseS1udW1iZXJlZCBzZXQgb2YgaG9zdHMgYW5kIHBvdGVudGlhbGx5IGlkZW50aWZ5
aW5nIGEgcHJvYmxlbSBzdGF0ZW1lbnQgZm9yIGltcHJvdmluZyByZW51bWJlcmluZyBmb3Igc3Rh
dGljDQo+PiANCj4+IEkgYWRtaXQgdGhhdCAjNCBhbmQgNSBhcmUgbm9uLXRyaXZhbCwgYnV0IEkg
dGhpbmsgdGhleSBhcmUgc3RpbGwgd2l0aGluIG91ciBzY29wZS4gV2UncmUgbm90IHNvbHZpbmcg
bXVjaCBvZiB0aGUgcmVudW1iZXJpbmcgcHJvYmxlbSBpZiB3ZSBsaW1pdCBvdXJzZWx2ZXMgdG8g
ZHluYW1pY2FsbHktYWRkcmVzc2VkIGRldmljZXMuIFBlcmhhcHMgaW4gb3JkZXIgdG8gYnJlYWsg
dGhpcyBpbnRvIG1hbmFnZWFibGUgY2h1bmtzLCB0aGlzIGRyYWZ0IGFuZCBpdHMgY29tcGFuaW9u
IHN0YXlzIGZvY3VzZWQgc3BlY2lmaWNhbGx5IG9uIGR5bmFtaWMgYW5kIGFub3RoZXIgc2V0IG9m
IGRyYWZ0cyBhcmUgc3B1biB0byBjb3ZlciBzdGF0aWM/IEknbSBub3Qgc3VyZSBob3cgbXVjaCBv
dmVybGFwIHRoZXJlIHdvdWxkIGJlLCBhcyBpZiBpdCdzIGEgbG90IGl0IG1ha2VzIGxlc3Mgc2Vu
c2UgdG8gaGF2ZSBzZXBhcmF0ZSBkcmFmdHMgaW5zdGVhZCBvZiBzZXBhcmF0ZSBzZWN0aW9ucyBv
ZiB0aGVzZSBjb21tb24gZHJhZnRzLi4uDQoNCj5JIHRoaW5rIHRoaXMgdHlwZSBvZiBhbmFseXNp
cyBpcyB1c2VmdWwuICANCg0KPk91ciBjaGFydGVyIGZvY3VzZXMgb24gcHJvZHVjaW5nIHR3byBk
ZWxpdmVyYWJsZXMsIG9uZSBiZWluZyBhbiBlbnRlcnByaXNlIHNjZW5hcmlvIHRleHQgdGhhdCBp
bmNsdWRlcyBkb2N1bWVudGF0aW9uIG9mIGV4aXN0aW5nIHByYWN0aWNlcyBhbmQgY2FwYWJpbGl0
aWVzICh3aGljaCB3b3VsZCBpbmNsdWRlIHBvaW50cyAxIGFuZCAzIGFib3ZlKSwgdGhlIG90aGVy
IGJlaW5nIGEgZ2FwIGFuYWx5c2lzLCB3aGljaCBjYW4gYWxzbyBkcmF3IG9uIFJGQzQxOTIgYW5k
IFJGQzU4NzcgKGFuZCBpbmNsdWRlIHBvaW50cyAyLCA0IGFuZCA1IGFib3ZlKS4NCg0KV2UndmUg
aW5jbHVkZWQgR2VvcmdlJ3MgY29tbWVudHMgYXMgYSBzdWItY2xhdXNlIGluICJBZGRyZXNzIENv
bmZpZ3VyYXRpb24gR2FwcyIgc2VjdGlvbiBpbiB0aGUgZ2FwIGRvY3VtZW50LCBwb2ludCAzLCA0
LCBhbmQgNSBjb3VsZCBiZSBhIGdvb2QgaW5pdGlhbCBkaXNjdXNzaW9uIGNsdWUuIEZvciB0aGUg
cG9pbnQgMSwgMiwgd2UndmUgYWxyZWFkeSBkaWQgc29tZSBjb25zaWRlcmF0aW9ucyBpbiB0aGUg
ZWFybHkgZ3VpZGVsaW5lIGRyYWZ0LCB3aGljaCB3aWxsIGJlIGluaGVyaXRlZCBpbiB0aGUgZ2Fw
IGFuYWx5c2lzLiBNYW55IHRoYW5rcyB0byBHZW9yZ2UgYWdhaW4gZm9yIGhpcyB2YWx1YWJsZSBj
b21tZW50cy4NCg0KV2UnbGwgc3VibWl0IHRoZSBnYXAgYW5hbHlzaXMgMDAgdmVyc2lvbiBvbiBN
b25kYXkuIEFuZCBhbnkgY29tbWVudHMgdG8gdGhlIDAwIHZlcnNpb24gd291bGQgYmUgZXhwZWN0
ZWQgZWFnZXJseSBzbyB0aGF0IHdlIG1heSBwcm9kdWNlIGEgMDEgdmVyc2lvbiBiZWZvcmUgdGhl
IGN1dC1vZmYgZGF0ZS4gDQoNCg0KPldlIHNob3VsZCBoYXZlIGEgV0cgc2xvdCBpbiBRdWViZWMs
IGFuZCB0aGUgZGVhZGxpbmUgZm9yIC0wMCBkcmFmdHMgaXMgTW9uZGF5IHdlZWsgKDR0aCBKdWx5
KS4gIEkgYmVsaWV2ZSBTaGVuZyBpcyB3b3JraW5nIHRvd2FyZHMgc3BsaXR0aW5nIGhpcyBwcmV2
aW91cyBkcmFmdCBpbnRvIHN0YXJ0aW5nIHBvaW50cyBmb3IgdGhlIHR3byBuZXcgdGV4dHMsIGFu
ZCBzbyBJJ2QgZW5jb3VyYWdlIGFueSBpbnRlcmVzdGVkIGF1dGhvcnMgb3IgY29udHJpYnV0b3Jz
IHRvIGNvbnRhY3QgU2hlbmcgdG8gd29yayBvbiB0aGF0IG92ZXIgdGhlIG5leHQgZmV3IGRheXMu
ICAgV2UgY2FuIHRoZW4gdXNlIHRoZSBtZWV0aW5nIHNsb3QgdG8gaGF2ZSBhIGdvb2QgZGlzY3Vz
c2lvbiBhYm91dCB0aG9zZSB0ZXh0cywgYW5kIGhvcGVmdWxseSBnZW5lcmF0ZSBwb2ludGVycyBh
bmQgaWRlYXMgZm9yIHRoZWlyIGZ1cnRoZXIgZGV2ZWxvcG1lbnQgYWZ0ZXIgdGhlIG1lZXRpbmcu
DQoNClRpbQ0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
CnJlbnVtIG1haWxpbmcgbGlzdA0KcmVudW1AaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vcmVudW0NCg==
