
From iesg-secretary@ietf.org  Wed Jan  2 12:47:55 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF1D721F8A0C; Wed,  2 Jan 2013 12:47:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.495
X-Spam-Level: 
X-Spam-Status: No, score=-102.495 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9i5dJe0cHQF; Wed,  2 Jan 2013 12:47:54 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 183E021F8A41; Wed,  2 Jan 2013 12:47:54 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130102204754.27485.3292.idtracker@ietfa.amsl.com>
Date: Wed, 02 Jan 2013 12:47:54 -0800
Cc: 6renum chair <6renum-chairs@tools.ietf.org>, 6renum mailing list <renum@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [renum] Document Action: 'Problem Statement for Renumbering IPv6 Hosts with	Static Addresses in Enterprise Networks' to Informational RFC	(draft-ietf-6renum-static-problem-03.txt)
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 20:47:55 -0000

The IESG has approved the following document:
- 'Problem Statement for Renumbering IPv6 Hosts with Static Addresses in
   Enterprise Networks'
  (draft-ietf-6renum-static-problem-03.txt) as Informational RFC

This document is the product of the IPv6 Site Renumbering Working Group.

The IESG contact persons are Ronald Bonica and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem/




Technical Summary: 

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

Working Group Summary: 

Very little controversy.  There was discussion about whether it should have been included in the document draft-6renum-enterprise-scenarios, but the authors, chairs, and AD decided it should stand alone.
 
Document Quality: 

RJ Atkinson did an especially thorough review during WGLC. 

Personnel: 

Shepherd: Lee Howard.  
AD: Ron Bonica 



From adrian@olddog.co.uk  Fri Jan  4 14:31:38 2013
Return-Path: <adrian@olddog.co.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 4FDBC21F8732 for <renum@ietfa.amsl.com>; Fri,  4 Jan 2013 14:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.221
X-Spam-Level: 
X-Spam-Status: No, score=-2.221 tagged_above=-999 required=5 tests=[AWL=0.379,  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 sOir1O7keyh0 for <renum@ietfa.amsl.com>; Fri,  4 Jan 2013 14:31:37 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 93CE021F8809 for <renum@ietf.org>; Fri,  4 Jan 2013 14:31:36 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r04MVYqg007756;  Fri, 4 Jan 2013 22:31:34 GMT
Received: from 950129200 (089144192219.atnat0001.highway.a1.net [89.144.192.219]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r04MVUEa007710;  Fri, 4 Jan 2013 22:31:33 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, <renum@ietf.org>
References: <20121224074420.1190.74267.idtracker@ietfa.amsl.com> <50D80B11.60201@gmail.com>
In-Reply-To: <50D80B11.60201@gmail.com>
Date: Fri, 4 Jan 2013 22:31:30 -0000
Message-ID: <072b01cdeacb$40b07820$c2116860$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFy8/L3Viu+r8fw10ySai4sxgFNGQGgByr9mOKktAA=
Content-Language: en-gb
Cc: 'Pete Resnick' <presnick@qti.qualcomm.com>, 'Adrian Farrel' <adrian@olddog.co.uk>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-static-problem-03.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 04 Jan 2013 22:31:38 -0000

Brian,
Thanks for taking the time to look at my Comments.
Adrian

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> Sent: 24 December 2012 07:58
> To: renum@ietf.org
> Cc: Ron Bonica; Brian Haberman; Pete Resnick; Adrian Farrel; Ralph Droms
> Subject: Re: [renum] I-D Action: draft-ietf-6renum-static-problem-03.txt
> 
> Hi 6renum WG and others,
> 
> This update is intended to deal with comments received during
> IETF Last Call and IESG review.
> 
> The comments from Brian Haberman, Pete Resnick, and Adrian Farrel
> were quite straightforward and have been dealt with. In particular,
> the document scope was clarified and the discussion of Dynamic DNS
> update has been corrected.
> 
> The review by Ralph Droms raised a number of points:
> 
> > > DNS, mDNS and SLP are mentioned in the context of name resolution.  Is
> > > SLP deployed widely enough to warrant mention?
> 
> Lack of deployment is exactly the reason for mentioning it. The text
> should make that clear now.
> 
> > > What about LLMNR and uPNP?
> 
> These are not IETF standards track protocols and don't seem to be aimed
> at enterprise networks. However, we have modified the text to refer to
> discovery protocols in general.
> 
> > > I don't understand why ULAs are identified as somehow affecting the
> > > use or impact of static addresses.
> 
> Clarified the text.
> 
> > > DHCPv6 PD should be mentioned in the context of prefix assignment.
> 
> This is discussed in the more general document draft-ietf-6renum-enterprise.
> It isn't specific to static addressing.
> 
> > > Is it really still common practice that "printers in particular are
> > > manually assigned a fixed address (typically an [RFC1918] address) and
> > > that users are told to manually configure printer access using that
> > > fixed address"?
> 
> Unfortunately there are plenty of smaller sites that still do this (and many
> that don't, of course).
> 
> > > In section 2.3, addresses assigned through DHCPv6 are considered
> > > problematic because the address might expire, but later DHCPv6 is
> > > suggested as a way of assigning addresses to solve renumbering of
> > > static addresses.
> 
> Both things can be simultaneously valid; that's part of the renumbering
> dilemma. Tuned the text to make it seem less paradoxical.
> 
> > > I don't understand the first sentence of 2.4.  Isn't the requirement
> > > for a static address based on the need to maintain transport sessions
> > > over VM movement (which isn't really how I understand the first
> > > sentence).
> 
> Yes. This text has been updated for clarity.
> 
> > > In section 2.5, if asset management is based on MAC addresses, why are
> > > static IP addresses an issue?
> > >
> > > I don't understand the connection between "If [...] a particular host
> > > is found to be generating some form of unwanted traffic, it is urgent
> > > to be able to track back from its IP address to its physical location"
> > > and renumbering of static addressing.
> 
> There are indeed sites where IPv4 addresses are statically bound to
> the MAC address but SLAAC is used for IPv6, with privacy addresses permitted.
> But sites that choose to migrate IPv4 practices to IPv6 will probably bind
> the MAC address and the IPv6 address. Surely the IETF can't tell them
> not to do that?
> 
> > > In section 2.7, this claim may be true:
> > >
> > >   In any case, when network elements are renumbered, existing user
> > >   sessions may not survive, because of temporary "destination
> > >   unreachable" conditions being treated as fatal errors.  This aspect
> > >   needs further investigation.
> > >
> > > but what is its connection to renumbering static addresses?
> 
> None in particular ;-). Deleted.
> 
> > > Section 2.8 makes a valid point about the relationship between static
> > > addresses and asset management, but goes into solution space when it
> > > talks about DHCPv6 for configuring static addresses.
> 
> Toned down the "should" language.
> 
> > > I don't understand the first paragraph of section 3.
> 
> Reworded.
> 
> > >   4.  If external prefix renumbering is required, the RFC 4192
> > >       procedure is followed.
> > >
> > > What about renumbering required by strictly internal topology changes
> > > in the network?  I.e., I think "external" can be dropped.
> 
> Agreed.
> 
> Regards
>    Brian Carpenter


From brian.e.carpenter@gmail.com  Wed Jan  9 23:44:03 2013
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 0C0D621F8911 for <renum@ietfa.amsl.com>; Wed,  9 Jan 2013 23:44:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.434
X-Spam-Level: 
X-Spam-Status: No, score=-100.434 tagged_above=-999 required=5 tests=[AWL=-1.043, BAYES_00=-2.599, MANGLED_PAIN=2.3, RCVD_ILLEGAL_IP=1.908, 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 bCCn5XRp+KUx for <renum@ietfa.amsl.com>; Wed,  9 Jan 2013 23:44:02 -0800 (PST)
Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by ietfa.amsl.com (Postfix) with ESMTP id D662421F8903 for <renum@ietf.org>; Wed,  9 Jan 2013 23:44:01 -0800 (PST)
Received: by mail-wg0-f54.google.com with SMTP id fg15so95794wgb.33 for <renum@ietf.org>; Wed, 09 Jan 2013 23:44:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=t22U3I22WywDyyCB0VYkJc74X3VGFHnKsIsTWCrQrYo=; b=hBUm5SavVPaeaLNkyq3nAnrjGIit2SaY9udJw4RpwdVeGJsxy+rIdEqXuVnBFpNF3g 0umHZWsqNy2+CCKswtpKMJ6lg25wFNe1cIabPxrc5bnLk3qFoabQTqyEf9WPm2osnkeW Axthle3cF2qhP6GxUPjXnOhEMRd4qvzCcjngl4jpZ1aoBU0a2Aw4KOQNjdjWO4TtVOoB DJwBmCJ+ukVhd4fGi5eMYGxFq/7oiZiKGllKnA/ecwzx62K35FujYCHwAqVFnvz0iMXD cocWOyOGWpMfAep3scVGE2VCuRjy4IcgRRfbYLusjuBT8pcqERrwgBBCjTXpmSs43wSe qr5w==
X-Received: by 10.194.88.98 with SMTP id bf2mr112972017wjb.49.1357803840878; Wed, 09 Jan 2013 23:44:00 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-229.as13285.net. [2.102.216.229]) by mx.google.com with ESMTPS id u6sm1028154wif.2.2013.01.09.23.43.59 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Jan 2013 23:43:59 -0800 (PST)
Message-ID: <50EE7145.5040406@gmail.com>
Date: Thu, 10 Jan 2013 07:44:05 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: renum@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [renum] Late gap in the gap analysis
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, 10 Jan 2013 07:44:03 -0000

I know this comes late in the process, but the attached comment
on draft-ietf-6renum-enterprise actually identifies a gap
in the gap analysis.

    Brian

-------- Original Message --------
Subject: Re: [OPS-DIR] OPS-DIR review of draft-ietf-6renum-enterprise-04
Date: Wed, 09 Jan 2013 18:23:25 +0100
From: Benoit Claise <bclaise@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Romascanu, Dan (Dan) <dromasca@avaya.com>,        ops-dir@ietf.org <ops-dir@ietf.org>,        leo.liubing@huawei.com
<leo.liubing@huawei.com>,        jiangsheng@huawei.com <jiangsheng@huawei.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA03B08B@AZ-FFEXMB04.global.avaya.com> <50C866F0.9050607@gmail.com>

Brian,
> Dan,
>
> Thanks. At the moment we definitely don't have a mandate to make
> this a BCP; I agree that its status needs to be a bit clearer.
>
> Your other comments are useful.
>
>> 7. From the list of operational issues to be verified as per RFC 5706 I believe that the following applies: Have suggestions for verifying correct operation been discussed? In this case this translates into the question whether there are any recommended practices to ensure that the renumbering process was fully completed and the transformation that occurred is exactly what the operators planned.
> That's a very interesting point. For example one could monitor
> RA and ND messages to check that the old prefixes had really died.
> I suspect that in the scope of this draft we can only really mention
> the problem, but maybe you have found a gap in the gap analysis
> draft.
Yes, this should be covered in the gap analysis draft.

Regards, Benoit
>
> Regards
>     Brian Carpenter
>
> On 11/12/2012 15:58, Romascanu, Dan (Dan) wrote:
>> Please find below the OPS-DIR review of draft-ietf-6renum-enterprise-04.
>>
>> This review is performed for the benefit of the OPS ADs and focuses on operational and manageability issues. RFC 5706 was used as a reference for this review.
>>
>> The document targets Informational RFC status and provides a useful set of scenarios and guidelines to network operators on best renumbering practices. It is almost ready for publication, a few glitches are mentioned below and the ADs may decide whether they consider these as blocking and include in a DISCUSS or nice-to-fix and then they could be part of a COMMENT or may be completely ignore.
>>
>> 1. the language used in this document in some places sounds like BCP-ish. It is fine as it stands because the document has Intended Status of Informational, but in case the IESG has any thoughts about changing the Intended Status and approving this I-D as a BCP, then it needs revisiting for consistency of the language and possible usage of RFC 2119 keywords.
>>
>> 2. [RFC4057] needs to be a Normative Reference. All the document is about the Enterprise Networks, a clear definition is thus required in order to understand its scope, and document where this definition is taken from is essential for the understanding of the document.
>>
>> 3. In Section 2 I see:
>>> Figure 1 provides a sample enterprise network architecture. Those
>>     entities relevant to renumbering are highlighted.
>> I do not understand what 'are highlighted' means on Figure 1 which is ASCII art
>>
>> 4. Some acronyms are not expanded at first occurrence - for example PD, PA in Section 4.1, etc.
>>
>> 5. 'ND is considered easier to renumber' (where ND is Network Discovery) - I could not understand what this means
>> - Section 5 starts with the following statement:
>>> As noted, a site that is listed by IP address in a black list can
>>     escape that list by renumbering itself.
>> I am uncertain where this was noted, as this seems to be the first occurrence of the issue of black list in the document.
>>
>> 6. The document can benefit from a pass with a native English speaker. I spotted several grammar and vocabulary problems which I did not list as these are our of the scope of an OPS-DIR review, and the RFC Editor will certainly do a fine job, but in some cases these problems distort the sense of the sentences - for example ' This work is illuminated by RFC5887, so thank for RFC 5887 authors' this is probably ' This work is inspired by (or derived from)  RFC5887, so thanks to RFC 5887 authors'
>>
>>
>> 7. From the list of operational issues to be verified as per RFC 5706 I believe that the following applies: Have suggestions for verifying correct operation been discussed? In this case this translates into the question whether there are any recommended practices to ensure that the renumbering process was fully completed and the transformation that occurred is exactly what the operators planned.
>>
>> Thanks and Regards,
>>
>> Dan
>>   
>>
> _______________________________________________
> OPS-DIR mailing list
> OPS-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-dir
>
>



-- 
Regards
   Brian Carpenter



From leo.liubing@huawei.com  Thu Jan 10 00:15:39 2013
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 91B5121F8935 for <renum@ietfa.amsl.com>; Thu, 10 Jan 2013 00:15:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.449
X-Spam-Level: 
X-Spam-Status: No, score=-5.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_PAIN=2.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NuhJLsr9NF2A for <renum@ietfa.amsl.com>; Thu, 10 Jan 2013 00:15:38 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id DD0FB21F8598 for <renum@ietf.org>; Thu, 10 Jan 2013 00:15:27 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOP26474; Thu, 10 Jan 2013 08:15:25 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 10 Jan 2013 08:14:25 +0000
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 10 Jan 2013 08:15:24 +0000
Received: from SZXEML509-MBX.china.huawei.com ([10.82.67.37]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0323.003; Thu, 10 Jan 2013 16:15:20 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: [renum] Late gap in the gap analysis
Thread-Index: AQHN7wZKQ6mtk3KTmUSc4h5PaXGFB5hCNQoQ
Date: Thu, 10 Jan 2013 08:15:20 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453CD00A4A@szxeml509-mbx>
References: <50EE7145.5040406@gmail.com>
In-Reply-To: <50EE7145.5040406@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [renum] Late gap in the gap analysis
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, 10 Jan 2013 08:15:39 -0000

Hi, Brian

I think the current section 7.3 in gap draft covering that, however, it is =
not so explicit.
But I think it is sufficient. How do you think about it?

/* 7.3. Renumbering Monitoring
   While treating renumbering as a network event, mechanisms to monitor
   the renumbering process may be needed. Considering the address
   configuration operation may be stateless (if ND is used for
   renumbering), it is difficult for monitoring. But for the DNS and
   filter update, it is quite possible to monitor the whole process. */

B.R.
Bing


> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of Brian E Carpenter
> Sent: Thursday, January 10, 2013 3:44 PM
> To: renum@ietf.org
> Subject: [renum] Late gap in the gap analysis
>=20
> I know this comes late in the process, but the attached comment
> on draft-ietf-6renum-enterprise actually identifies a gap
> in the gap analysis.
>=20
>     Brian
>=20
> -------- Original Message --------
> Subject: Re: [OPS-DIR] OPS-DIR review of draft-ietf-6renum-enterprise-04
> Date: Wed, 09 Jan 2013 18:23:25 +0100
> From: Benoit Claise <bclaise@cisco.com>
> To: Brian E Carpenter <brian.e.carpenter@gmail.com>
> CC: Romascanu, Dan (Dan) <dromasca@avaya.com>,
> ops-dir@ietf.org <ops-dir@ietf.org>,        leo.liubing@huawei.com
> <leo.liubing@huawei.com>,        jiangsheng@huawei.com
> <jiangsheng@huawei.com>
> References:
> <9904FB1B0159DA42B0B887B7FA8119CA03B08B@AZ-FFEXMB04.global.ava
> ya.com> <50C866F0.9050607@gmail.com>
>=20
> Brian,
> > Dan,
> >
> > Thanks. At the moment we definitely don't have a mandate to make
> > this a BCP; I agree that its status needs to be a bit clearer.
> >
> > Your other comments are useful.
> >
> >> 7. From the list of operational issues to be verified as per RFC 5706 =
I
> believe that the following applies: Have suggestions for verifying correc=
t
> operation been discussed? In this case this translates into the question
> whether there are any recommended practices to ensure that the
> renumbering process was fully completed and the transformation that
> occurred is exactly what the operators planned.
> > That's a very interesting point. For example one could monitor
> > RA and ND messages to check that the old prefixes had really died.
> > I suspect that in the scope of this draft we can only really mention
> > the problem, but maybe you have found a gap in the gap analysis
> > draft.
> Yes, this should be covered in the gap analysis draft.
>=20
> Regards, Benoit
> >
> > Regards
> >     Brian Carpenter
> >
> > On 11/12/2012 15:58, Romascanu, Dan (Dan) wrote:
> >> Please find below the OPS-DIR review of draft-ietf-6renum-enterprise-0=
4.
> >>
> >> This review is performed for the benefit of the OPS ADs and focuses on
> operational and manageability issues. RFC 5706 was used as a reference fo=
r
> this review.
> >>
> >> The document targets Informational RFC status and provides a useful se=
t
> of scenarios and guidelines to network operators on best renumbering
> practices. It is almost ready for publication, a few glitches are mention=
ed
> below and the ADs may decide whether they consider these as blocking and
> include in a DISCUSS or nice-to-fix and then they could be part of a
> COMMENT or may be completely ignore.
> >>
> >> 1. the language used in this document in some places sounds like BCP-i=
sh.
> It is fine as it stands because the document has Intended Status of
> Informational, but in case the IESG has any thoughts about changing the
> Intended Status and approving this I-D as a BCP, then it needs revisiting=
 for
> consistency of the language and possible usage of RFC 2119 keywords.
> >>
> >> 2. [RFC4057] needs to be a Normative Reference. All the document is
> about the Enterprise Networks, a clear definition is thus required in ord=
er to
> understand its scope, and document where this definition is taken from is
> essential for the understanding of the document.
> >>
> >> 3. In Section 2 I see:
> >>> Figure 1 provides a sample enterprise network architecture. Those
> >>     entities relevant to renumbering are highlighted.
> >> I do not understand what 'are highlighted' means on Figure 1 which is
> ASCII art
> >>
> >> 4. Some acronyms are not expanded at first occurrence - for example PD=
,
> PA in Section 4.1, etc.
> >>
> >> 5. 'ND is considered easier to renumber' (where ND is Network Discover=
y)
> - I could not understand what this means
> >> - Section 5 starts with the following statement:
> >>> As noted, a site that is listed by IP address in a black list can
> >>     escape that list by renumbering itself.
> >> I am uncertain where this was noted, as this seems to be the first
> occurrence of the issue of black list in the document.
> >>
> >> 6. The document can benefit from a pass with a native English speaker.=
 I
> spotted several grammar and vocabulary problems which I did not list as
> these are our of the scope of an OPS-DIR review, and the RFC Editor will
> certainly do a fine job, but in some cases these problems distort the sen=
se of
> the sentences - for example ' This work is illuminated by RFC5887, so tha=
nk
> for RFC 5887 authors' this is probably ' This work is inspired by (or der=
ived
> from)  RFC5887, so thanks to RFC 5887 authors'
> >>
> >>
> >> 7. From the list of operational issues to be verified as per RFC 5706 =
I
> believe that the following applies: Have suggestions for verifying correc=
t
> operation been discussed? In this case this translates into the question
> whether there are any recommended practices to ensure that the
> renumbering process was fully completed and the transformation that
> occurred is exactly what the operators planned.
> >>
> >> Thanks and Regards,
> >>
> >> Dan
> >>
> >>
> > _______________________________________________
> > OPS-DIR mailing list
> > OPS-DIR@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-dir
> >
> >
>=20
>=20
>=20
> --
> Regards
>    Brian Carpenter
>=20
>=20
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

From brian.e.carpenter@gmail.com  Thu Jan 10 00:52:48 2013
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 DEAD521F890E for <renum@ietfa.amsl.com>; Thu, 10 Jan 2013 00:52:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.372
X-Spam-Level: 
X-Spam-Status: No, score=-100.372 tagged_above=-999 required=5 tests=[AWL=-0.981, BAYES_00=-2.599, MANGLED_PAIN=2.3, RCVD_ILLEGAL_IP=1.908, 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 aXzYnqM5aPma for <renum@ietfa.amsl.com>; Thu, 10 Jan 2013 00:52:48 -0800 (PST)
Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) by ietfa.amsl.com (Postfix) with ESMTP id 681F421F86CE for <renum@ietf.org>; Thu, 10 Jan 2013 00:52:47 -0800 (PST)
Received: by mail-wi0-f181.google.com with SMTP id hq4so144456wib.8 for <renum@ietf.org>; Thu, 10 Jan 2013 00:52:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lIx51jJJikm22c48exGdMJpTAbzlQ5wfDkRk4o78Ges=; b=jDFRiSCe1uAlnpeHgIsJu1FnqHJSNTm3PEqX9dgk/OaYdcdOnOc41cvPnubl9N2YBW PFEE24niYGrNgzPQCrYakUqK4C5v6pGe0YlC0i1JrESOkFT03g9rSOxmzkl2TQ0J72ah c5CTBLhYrr/P4OGb64vNIUpMmlVjDhd+nz3JHXmyVIGitKlQpEGIMUOPBjgmLtcsJgr8 YlreGVyXm00gyngB7JIMx29Vk8Z1KkHlQ+hzFApJO5uDik5CgpG5gQIdP+G+zHVTVL7+ hWIw+j5ktwVxi3pRR7/0R4lMgLFNsz2N+IaWDkCv+eYHfLQQDQoSep5+IEbWEsT79zqJ oPDA==
X-Received: by 10.194.78.207 with SMTP id d15mr112922741wjx.52.1357807966233;  Thu, 10 Jan 2013 00:52:46 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-229.as13285.net. [2.102.216.229]) by mx.google.com with ESMTPS id t17sm1276307wiv.6.2013.01.10.00.52.44 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Jan 2013 00:52:45 -0800 (PST)
Message-ID: <50EE8167.2000205@gmail.com>
Date: Thu, 10 Jan 2013 08:52:55 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Liubing (Leo)" <leo.liubing@huawei.com>
References: <50EE7145.5040406@gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F453CD00A4A@szxeml509-mbx>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453CD00A4A@szxeml509-mbx>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Late gap in the gap analysis
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, 10 Jan 2013 08:52:49 -0000

Well,I think it is wrong to say "may be needed" - I would prefer
to make a stronger statement such as "are needed". Actually the text
is pessimistic - it doesn't seem hard to check that the old prefix is
no longer announced, for example.

Regards
   Brian

On 10/01/2013 08:15, Liubing (Leo) wrote:
> Hi, Brian
> 
> I think the current section 7.3 in gap draft covering that, however, it is not so explicit.
> But I think it is sufficient. How do you think about it?
> 
> /* 7.3. Renumbering Monitoring
>    While treating renumbering as a network event, mechanisms to monitor
>    the renumbering process may be needed. Considering the address
>    configuration operation may be stateless (if ND is used for
>    renumbering), it is difficult for monitoring. But for the DNS and
>    filter update, it is quite possible to monitor the whole process. */
> 
> B.R.
> Bing
> 
> 
>> -----Original Message-----
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
>> Of Brian E Carpenter
>> Sent: Thursday, January 10, 2013 3:44 PM
>> To: renum@ietf.org
>> Subject: [renum] Late gap in the gap analysis
>>
>> I know this comes late in the process, but the attached comment
>> on draft-ietf-6renum-enterprise actually identifies a gap
>> in the gap analysis.
>>
>>     Brian
>>
>> -------- Original Message --------
>> Subject: Re: [OPS-DIR] OPS-DIR review of draft-ietf-6renum-enterprise-04
>> Date: Wed, 09 Jan 2013 18:23:25 +0100
>> From: Benoit Claise <bclaise@cisco.com>
>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>
>> CC: Romascanu, Dan (Dan) <dromasca@avaya.com>,
>> ops-dir@ietf.org <ops-dir@ietf.org>,        leo.liubing@huawei.com
>> <leo.liubing@huawei.com>,        jiangsheng@huawei.com
>> <jiangsheng@huawei.com>
>> References:
>> <9904FB1B0159DA42B0B887B7FA8119CA03B08B@AZ-FFEXMB04.global.ava
>> ya.com> <50C866F0.9050607@gmail.com>
>>
>> Brian,
>>> Dan,
>>>
>>> Thanks. At the moment we definitely don't have a mandate to make
>>> this a BCP; I agree that its status needs to be a bit clearer.
>>>
>>> Your other comments are useful.
>>>
>>>> 7. From the list of operational issues to be verified as per RFC 5706 I
>> believe that the following applies: Have suggestions for verifying correct
>> operation been discussed? In this case this translates into the question
>> whether there are any recommended practices to ensure that the
>> renumbering process was fully completed and the transformation that
>> occurred is exactly what the operators planned.
>>> That's a very interesting point. For example one could monitor
>>> RA and ND messages to check that the old prefixes had really died.
>>> I suspect that in the scope of this draft we can only really mention
>>> the problem, but maybe you have found a gap in the gap analysis
>>> draft.
>> Yes, this should be covered in the gap analysis draft.
>>
>> Regards, Benoit
>>> Regards
>>>     Brian Carpenter
>>>
>>> On 11/12/2012 15:58, Romascanu, Dan (Dan) wrote:
>>>> Please find below the OPS-DIR review of draft-ietf-6renum-enterprise-04.
>>>>
>>>> This review is performed for the benefit of the OPS ADs and focuses on
>> operational and manageability issues. RFC 5706 was used as a reference for
>> this review.
>>>> The document targets Informational RFC status and provides a useful set
>> of scenarios and guidelines to network operators on best renumbering
>> practices. It is almost ready for publication, a few glitches are mentioned
>> below and the ADs may decide whether they consider these as blocking and
>> include in a DISCUSS or nice-to-fix and then they could be part of a
>> COMMENT or may be completely ignore.
>>>> 1. the language used in this document in some places sounds like BCP-ish.
>> It is fine as it stands because the document has Intended Status of
>> Informational, but in case the IESG has any thoughts about changing the
>> Intended Status and approving this I-D as a BCP, then it needs revisiting for
>> consistency of the language and possible usage of RFC 2119 keywords.
>>>> 2. [RFC4057] needs to be a Normative Reference. All the document is
>> about the Enterprise Networks, a clear definition is thus required in order to
>> understand its scope, and document where this definition is taken from is
>> essential for the understanding of the document.
>>>> 3. In Section 2 I see:
>>>>> Figure 1 provides a sample enterprise network architecture. Those
>>>>     entities relevant to renumbering are highlighted.
>>>> I do not understand what 'are highlighted' means on Figure 1 which is
>> ASCII art
>>>> 4. Some acronyms are not expanded at first occurrence - for example PD,
>> PA in Section 4.1, etc.
>>>> 5. 'ND is considered easier to renumber' (where ND is Network Discovery)
>> - I could not understand what this means
>>>> - Section 5 starts with the following statement:
>>>>> As noted, a site that is listed by IP address in a black list can
>>>>     escape that list by renumbering itself.
>>>> I am uncertain where this was noted, as this seems to be the first
>> occurrence of the issue of black list in the document.
>>>> 6. The document can benefit from a pass with a native English speaker. I
>> spotted several grammar and vocabulary problems which I did not list as
>> these are our of the scope of an OPS-DIR review, and the RFC Editor will
>> certainly do a fine job, but in some cases these problems distort the sense of
>> the sentences - for example ' This work is illuminated by RFC5887, so thank
>> for RFC 5887 authors' this is probably ' This work is inspired by (or derived
>> from)  RFC5887, so thanks to RFC 5887 authors'
>>>>
>>>> 7. From the list of operational issues to be verified as per RFC 5706 I
>> believe that the following applies: Have suggestions for verifying correct
>> operation been discussed? In this case this translates into the question
>> whether there are any recommended practices to ensure that the
>> renumbering process was fully completed and the transformation that
>> occurred is exactly what the operators planned.
>>>> Thanks and Regards,
>>>>
>>>> Dan
>>>>
>>>>
>>> _______________________________________________
>>> OPS-DIR mailing list
>>> OPS-DIR@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ops-dir
>>>
>>>
>>
>>
>> --
>> Regards
>>    Brian Carpenter
>>
>>
>> _______________________________________________
>> renum mailing list
>> renum@ietf.org
>> https://www.ietf.org/mailman/listinfo/renum
> 

From leo.liubing@huawei.com  Thu Jan 10 01:14:10 2013
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 82C5721F8820 for <renum@ietfa.amsl.com>; Thu, 10 Jan 2013 01:14:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.574
X-Spam-Level: 
X-Spam-Status: No, score=-4.574 tagged_above=-999 required=5 tests=[AWL=-0.875, BAYES_00=-2.599, J_CHICKENPOX_41=0.6, MANGLED_PAIN=2.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FOd8MA1PCTyu for <renum@ietfa.amsl.com>; Thu, 10 Jan 2013 01:14:09 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id BF9CA21F87A3 for <renum@ietf.org>; Thu, 10 Jan 2013 01:14:05 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOP30861; Thu, 10 Jan 2013 09:14:04 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 10 Jan 2013 09:12:20 +0000
Received: from SZXEML457-HUB.china.huawei.com (10.82.67.200) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 10 Jan 2013 09:13:06 +0000
Received: from SZXEML509-MBX.china.huawei.com ([10.82.67.37]) by szxeml457-hub.china.huawei.com ([10.82.67.200]) with mapi id 14.01.0323.003; Thu, 10 Jan 2013 17:12:49 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [renum] Late gap in the gap analysis
Thread-Index: AQHN7wZKQ6mtk3KTmUSc4h5PaXGFB5hCNQoQ//+GkICAAIt80A==
Date: Thu, 10 Jan 2013 09:12:50 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453CD00A7D@szxeml509-mbx>
References: <50EE7145.5040406@gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F453CD00A4A@szxeml509-mbx> <50EE8167.2000205@gmail.com>
In-Reply-To: <50EE8167.2000205@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Late gap in the gap analysis
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, 10 Jan 2013 09:14:11 -0000

T0ssIEkgY2FuIHVwZGF0ZSBpdCBhY2NvcmRpbmdseS4gDQpUaGUgb3JpZ2luYWwgdGV4dCBpbXBs
eWluZyB0aGUgc29sdXRpb25zIG1pZ2h0IGJlIGRpZmZpY3VsdCwgYnV0IHdlIG5lZWQgdG8gbWFr
ZSBpdCBjbGVhciB0aGF0IHRoZSBnYXAgaXMgZGVmaW5pdGUuDQoNCkIuUi4NCkJpbmcNCg0KPiAt
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBCcmlhbiBFIENhcnBlbnRlciBbbWFp
bHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbV0NCj4gU2VudDogVGh1cnNkYXksIEphbnVh
cnkgMTAsIDIwMTMgNDo1MyBQTQ0KPiBUbzogTGl1YmluZyAoTGVvKQ0KPiBDYzogcmVudW1AaWV0
Zi5vcmcNCj4gU3ViamVjdDogUmU6IFtyZW51bV0gTGF0ZSBnYXAgaW4gdGhlIGdhcCBhbmFseXNp
cw0KPiANCj4gV2VsbCxJIHRoaW5rIGl0IGlzIHdyb25nIHRvIHNheSAibWF5IGJlIG5lZWRlZCIg
LSBJIHdvdWxkIHByZWZlcg0KPiB0byBtYWtlIGEgc3Ryb25nZXIgc3RhdGVtZW50IHN1Y2ggYXMg
ImFyZSBuZWVkZWQiLiBBY3R1YWxseSB0aGUgdGV4dA0KPiBpcyBwZXNzaW1pc3RpYyAtIGl0IGRv
ZXNuJ3Qgc2VlbSBoYXJkIHRvIGNoZWNrIHRoYXQgdGhlIG9sZCBwcmVmaXggaXMNCj4gbm8gbG9u
Z2VyIGFubm91bmNlZCwgZm9yIGV4YW1wbGUuDQo+IA0KPiBSZWdhcmRzDQo+ICAgIEJyaWFuDQo+
IA0KPiBPbiAxMC8wMS8yMDEzIDA4OjE1LCBMaXViaW5nIChMZW8pIHdyb3RlOg0KPiA+IEhpLCBC
cmlhbg0KPiA+DQo+ID4gSSB0aGluayB0aGUgY3VycmVudCBzZWN0aW9uIDcuMyBpbiBnYXAgZHJh
ZnQgY292ZXJpbmcgdGhhdCwgaG93ZXZlciwgaXQgaXMgbm90DQo+IHNvIGV4cGxpY2l0Lg0KPiA+
IEJ1dCBJIHRoaW5rIGl0IGlzIHN1ZmZpY2llbnQuIEhvdyBkbyB5b3UgdGhpbmsgYWJvdXQgaXQ/
DQo+ID4NCj4gPiAvKiA3LjMuIFJlbnVtYmVyaW5nIE1vbml0b3JpbmcNCj4gPiAgICBXaGlsZSB0
cmVhdGluZyByZW51bWJlcmluZyBhcyBhIG5ldHdvcmsgZXZlbnQsIG1lY2hhbmlzbXMgdG8NCj4g
bW9uaXRvcg0KPiA+ICAgIHRoZSByZW51bWJlcmluZyBwcm9jZXNzIG1heSBiZSBuZWVkZWQuIENv
bnNpZGVyaW5nIHRoZSBhZGRyZXNzDQo+ID4gICAgY29uZmlndXJhdGlvbiBvcGVyYXRpb24gbWF5
IGJlIHN0YXRlbGVzcyAoaWYgTkQgaXMgdXNlZCBmb3INCj4gPiAgICByZW51bWJlcmluZyksIGl0
IGlzIGRpZmZpY3VsdCBmb3IgbW9uaXRvcmluZy4gQnV0IGZvciB0aGUgRE5TIGFuZA0KPiA+ICAg
IGZpbHRlciB1cGRhdGUsIGl0IGlzIHF1aXRlIHBvc3NpYmxlIHRvIG1vbml0b3IgdGhlIHdob2xl
IHByb2Nlc3MuICovDQo+ID4NCj4gPiBCLlIuDQo+ID4gQmluZw0KPiA+DQo+ID4NCj4gPj4gLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTogcmVudW0tYm91bmNlc0BpZXRmLm9y
ZyBbbWFpbHRvOnJlbnVtLWJvdW5jZXNAaWV0Zi5vcmddIE9uDQo+IEJlaGFsZg0KPiA+PiBPZiBC
cmlhbiBFIENhcnBlbnRlcg0KPiA+PiBTZW50OiBUaHVyc2RheSwgSmFudWFyeSAxMCwgMjAxMyAz
OjQ0IFBNDQo+ID4+IFRvOiByZW51bUBpZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBbcmVudW1dIExh
dGUgZ2FwIGluIHRoZSBnYXAgYW5hbHlzaXMNCj4gPj4NCj4gPj4gSSBrbm93IHRoaXMgY29tZXMg
bGF0ZSBpbiB0aGUgcHJvY2VzcywgYnV0IHRoZSBhdHRhY2hlZCBjb21tZW50DQo+ID4+IG9uIGRy
YWZ0LWlldGYtNnJlbnVtLWVudGVycHJpc2UgYWN0dWFsbHkgaWRlbnRpZmllcyBhIGdhcA0KPiA+
PiBpbiB0aGUgZ2FwIGFuYWx5c2lzLg0KPiA+Pg0KPiA+PiAgICAgQnJpYW4NCj4gPj4NCj4gPj4g
LS0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tLQ0KPiA+PiBTdWJqZWN0OiBSZTogW09Q
Uy1ESVJdIE9QUy1ESVIgcmV2aWV3IG9mIGRyYWZ0LWlldGYtNnJlbnVtLWVudGVycHJpc2UtMDQN
Cj4gPj4gRGF0ZTogV2VkLCAwOSBKYW4gMjAxMyAxODoyMzoyNSArMDEwMA0KPiA+PiBGcm9tOiBC
ZW5vaXQgQ2xhaXNlIDxiY2xhaXNlQGNpc2NvLmNvbT4NCj4gPj4gVG86IEJyaWFuIEUgQ2FycGVu
dGVyIDxicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb20+DQo+ID4+IENDOiBSb21hc2NhbnUsIERh
biAoRGFuKSA8ZHJvbWFzY2FAYXZheWEuY29tPiwNCj4gPj4gb3BzLWRpckBpZXRmLm9yZyA8b3Bz
LWRpckBpZXRmLm9yZz4sICAgICAgICBsZW8ubGl1YmluZ0BodWF3ZWkuY29tDQo+ID4+IDxsZW8u
bGl1YmluZ0BodWF3ZWkuY29tPiwgICAgICAgIGppYW5nc2hlbmdAaHVhd2VpLmNvbQ0KPiA+PiA8
amlhbmdzaGVuZ0BodWF3ZWkuY29tPg0KPiA+PiBSZWZlcmVuY2VzOg0KPiA+Pg0KPiA8OTkwNEZC
MUIwMTU5REE0MkIwQjg4N0I3RkE4MTE5Q0EwM0IwOEJAQVotRkZFWE1CMDQuZ2xvYmFsLmF2YQ0K
PiA+PiB5YS5jb20+IDw1MEM4NjZGMC45MDUwNjA3QGdtYWlsLmNvbT4NCj4gPj4NCj4gPj4gQnJp
YW4sDQo+ID4+PiBEYW4sDQo+ID4+Pg0KPiA+Pj4gVGhhbmtzLiBBdCB0aGUgbW9tZW50IHdlIGRl
ZmluaXRlbHkgZG9uJ3QgaGF2ZSBhIG1hbmRhdGUgdG8gbWFrZQ0KPiA+Pj4gdGhpcyBhIEJDUDsg
SSBhZ3JlZSB0aGF0IGl0cyBzdGF0dXMgbmVlZHMgdG8gYmUgYSBiaXQgY2xlYXJlci4NCj4gPj4+
DQo+ID4+PiBZb3VyIG90aGVyIGNvbW1lbnRzIGFyZSB1c2VmdWwuDQo+ID4+Pg0KPiA+Pj4+IDcu
IEZyb20gdGhlIGxpc3Qgb2Ygb3BlcmF0aW9uYWwgaXNzdWVzIHRvIGJlIHZlcmlmaWVkIGFzIHBl
ciBSRkMgNTcwNiBJDQo+ID4+IGJlbGlldmUgdGhhdCB0aGUgZm9sbG93aW5nIGFwcGxpZXM6IEhh
dmUgc3VnZ2VzdGlvbnMgZm9yIHZlcmlmeWluZyBjb3JyZWN0DQo+ID4+IG9wZXJhdGlvbiBiZWVu
IGRpc2N1c3NlZD8gSW4gdGhpcyBjYXNlIHRoaXMgdHJhbnNsYXRlcyBpbnRvIHRoZSBxdWVzdGlv
bg0KPiA+PiB3aGV0aGVyIHRoZXJlIGFyZSBhbnkgcmVjb21tZW5kZWQgcHJhY3RpY2VzIHRvIGVu
c3VyZSB0aGF0IHRoZQ0KPiA+PiByZW51bWJlcmluZyBwcm9jZXNzIHdhcyBmdWxseSBjb21wbGV0
ZWQgYW5kIHRoZSB0cmFuc2Zvcm1hdGlvbiB0aGF0DQo+ID4+IG9jY3VycmVkIGlzIGV4YWN0bHkg
d2hhdCB0aGUgb3BlcmF0b3JzIHBsYW5uZWQuDQo+ID4+PiBUaGF0J3MgYSB2ZXJ5IGludGVyZXN0
aW5nIHBvaW50LiBGb3IgZXhhbXBsZSBvbmUgY291bGQgbW9uaXRvcg0KPiA+Pj4gUkEgYW5kIE5E
IG1lc3NhZ2VzIHRvIGNoZWNrIHRoYXQgdGhlIG9sZCBwcmVmaXhlcyBoYWQgcmVhbGx5IGRpZWQu
DQo+ID4+PiBJIHN1c3BlY3QgdGhhdCBpbiB0aGUgc2NvcGUgb2YgdGhpcyBkcmFmdCB3ZSBjYW4g
b25seSByZWFsbHkgbWVudGlvbg0KPiA+Pj4gdGhlIHByb2JsZW0sIGJ1dCBtYXliZSB5b3UgaGF2
ZSBmb3VuZCBhIGdhcCBpbiB0aGUgZ2FwIGFuYWx5c2lzDQo+ID4+PiBkcmFmdC4NCj4gPj4gWWVz
LCB0aGlzIHNob3VsZCBiZSBjb3ZlcmVkIGluIHRoZSBnYXAgYW5hbHlzaXMgZHJhZnQuDQo+ID4+
DQo+ID4+IFJlZ2FyZHMsIEJlbm9pdA0KPiA+Pj4gUmVnYXJkcw0KPiA+Pj4gICAgIEJyaWFuIENh
cnBlbnRlcg0KPiA+Pj4NCj4gPj4+IE9uIDExLzEyLzIwMTIgMTU6NTgsIFJvbWFzY2FudSwgRGFu
IChEYW4pIHdyb3RlOg0KPiA+Pj4+IFBsZWFzZSBmaW5kIGJlbG93IHRoZSBPUFMtRElSIHJldmll
dyBvZg0KPiBkcmFmdC1pZXRmLTZyZW51bS1lbnRlcnByaXNlLTA0Lg0KPiA+Pj4+DQo+ID4+Pj4g
VGhpcyByZXZpZXcgaXMgcGVyZm9ybWVkIGZvciB0aGUgYmVuZWZpdCBvZiB0aGUgT1BTIEFEcyBh
bmQgZm9jdXNlcyBvbg0KPiA+PiBvcGVyYXRpb25hbCBhbmQgbWFuYWdlYWJpbGl0eSBpc3N1ZXMu
IFJGQyA1NzA2IHdhcyB1c2VkIGFzIGEgcmVmZXJlbmNlDQo+IGZvcg0KPiA+PiB0aGlzIHJldmll
dy4NCj4gPj4+PiBUaGUgZG9jdW1lbnQgdGFyZ2V0cyBJbmZvcm1hdGlvbmFsIFJGQyBzdGF0dXMg
YW5kIHByb3ZpZGVzIGEgdXNlZnVsDQo+IHNldA0KPiA+PiBvZiBzY2VuYXJpb3MgYW5kIGd1aWRl
bGluZXMgdG8gbmV0d29yayBvcGVyYXRvcnMgb24gYmVzdCByZW51bWJlcmluZw0KPiA+PiBwcmFj
dGljZXMuIEl0IGlzIGFsbW9zdCByZWFkeSBmb3IgcHVibGljYXRpb24sIGEgZmV3IGdsaXRjaGVz
IGFyZSBtZW50aW9uZWQNCj4gPj4gYmVsb3cgYW5kIHRoZSBBRHMgbWF5IGRlY2lkZSB3aGV0aGVy
IHRoZXkgY29uc2lkZXIgdGhlc2UgYXMgYmxvY2tpbmcNCj4gYW5kDQo+ID4+IGluY2x1ZGUgaW4g
YSBESVNDVVNTIG9yIG5pY2UtdG8tZml4IGFuZCB0aGVuIHRoZXkgY291bGQgYmUgcGFydCBvZiBh
DQo+ID4+IENPTU1FTlQgb3IgbWF5IGJlIGNvbXBsZXRlbHkgaWdub3JlLg0KPiA+Pj4+IDEuIHRo
ZSBsYW5ndWFnZSB1c2VkIGluIHRoaXMgZG9jdW1lbnQgaW4gc29tZSBwbGFjZXMgc291bmRzIGxp
a2UNCj4gQkNQLWlzaC4NCj4gPj4gSXQgaXMgZmluZSBhcyBpdCBzdGFuZHMgYmVjYXVzZSB0aGUg
ZG9jdW1lbnQgaGFzIEludGVuZGVkIFN0YXR1cyBvZg0KPiA+PiBJbmZvcm1hdGlvbmFsLCBidXQg
aW4gY2FzZSB0aGUgSUVTRyBoYXMgYW55IHRob3VnaHRzIGFib3V0IGNoYW5naW5nIHRoZQ0KPiA+
PiBJbnRlbmRlZCBTdGF0dXMgYW5kIGFwcHJvdmluZyB0aGlzIEktRCBhcyBhIEJDUCwgdGhlbiBp
dCBuZWVkcyByZXZpc2l0aW5nDQo+IGZvcg0KPiA+PiBjb25zaXN0ZW5jeSBvZiB0aGUgbGFuZ3Vh
Z2UgYW5kIHBvc3NpYmxlIHVzYWdlIG9mIFJGQyAyMTE5IGtleXdvcmRzLg0KPiA+Pj4+IDIuIFtS
RkM0MDU3XSBuZWVkcyB0byBiZSBhIE5vcm1hdGl2ZSBSZWZlcmVuY2UuIEFsbCB0aGUgZG9jdW1l
bnQgaXMNCj4gPj4gYWJvdXQgdGhlIEVudGVycHJpc2UgTmV0d29ya3MsIGEgY2xlYXIgZGVmaW5p
dGlvbiBpcyB0aHVzIHJlcXVpcmVkIGluIG9yZGVyDQo+IHRvDQo+ID4+IHVuZGVyc3RhbmQgaXRz
IHNjb3BlLCBhbmQgZG9jdW1lbnQgd2hlcmUgdGhpcyBkZWZpbml0aW9uIGlzIHRha2VuIGZyb20g
aXMNCj4gPj4gZXNzZW50aWFsIGZvciB0aGUgdW5kZXJzdGFuZGluZyBvZiB0aGUgZG9jdW1lbnQu
DQo+ID4+Pj4gMy4gSW4gU2VjdGlvbiAyIEkgc2VlOg0KPiA+Pj4+PiBGaWd1cmUgMSBwcm92aWRl
cyBhIHNhbXBsZSBlbnRlcnByaXNlIG5ldHdvcmsgYXJjaGl0ZWN0dXJlLiBUaG9zZQ0KPiA+Pj4+
ICAgICBlbnRpdGllcyByZWxldmFudCB0byByZW51bWJlcmluZyBhcmUgaGlnaGxpZ2h0ZWQuDQo+
ID4+Pj4gSSBkbyBub3QgdW5kZXJzdGFuZCB3aGF0ICdhcmUgaGlnaGxpZ2h0ZWQnIG1lYW5zIG9u
IEZpZ3VyZSAxIHdoaWNoIGlzDQo+ID4+IEFTQ0lJIGFydA0KPiA+Pj4+IDQuIFNvbWUgYWNyb255
bXMgYXJlIG5vdCBleHBhbmRlZCBhdCBmaXJzdCBvY2N1cnJlbmNlIC0gZm9yIGV4YW1wbGUNCj4g
UEQsDQo+ID4+IFBBIGluIFNlY3Rpb24gNC4xLCBldGMuDQo+ID4+Pj4gNS4gJ05EIGlzIGNvbnNp
ZGVyZWQgZWFzaWVyIHRvIHJlbnVtYmVyJyAod2hlcmUgTkQgaXMgTmV0d29yaw0KPiBEaXNjb3Zl
cnkpDQo+ID4+IC0gSSBjb3VsZCBub3QgdW5kZXJzdGFuZCB3aGF0IHRoaXMgbWVhbnMNCj4gPj4+
PiAtIFNlY3Rpb24gNSBzdGFydHMgd2l0aCB0aGUgZm9sbG93aW5nIHN0YXRlbWVudDoNCj4gPj4+
Pj4gQXMgbm90ZWQsIGEgc2l0ZSB0aGF0IGlzIGxpc3RlZCBieSBJUCBhZGRyZXNzIGluIGEgYmxh
Y2sgbGlzdCBjYW4NCj4gPj4+PiAgICAgZXNjYXBlIHRoYXQgbGlzdCBieSByZW51bWJlcmluZyBp
dHNlbGYuDQo+ID4+Pj4gSSBhbSB1bmNlcnRhaW4gd2hlcmUgdGhpcyB3YXMgbm90ZWQsIGFzIHRo
aXMgc2VlbXMgdG8gYmUgdGhlIGZpcnN0DQo+ID4+IG9jY3VycmVuY2Ugb2YgdGhlIGlzc3VlIG9m
IGJsYWNrIGxpc3QgaW4gdGhlIGRvY3VtZW50Lg0KPiA+Pj4+IDYuIFRoZSBkb2N1bWVudCBjYW4g
YmVuZWZpdCBmcm9tIGEgcGFzcyB3aXRoIGEgbmF0aXZlIEVuZ2xpc2ggc3BlYWtlci4NCj4gSQ0K
PiA+PiBzcG90dGVkIHNldmVyYWwgZ3JhbW1hciBhbmQgdm9jYWJ1bGFyeSBwcm9ibGVtcyB3aGlj
aCBJIGRpZCBub3QgbGlzdCBhcw0KPiA+PiB0aGVzZSBhcmUgb3VyIG9mIHRoZSBzY29wZSBvZiBh
biBPUFMtRElSIHJldmlldywgYW5kIHRoZSBSRkMgRWRpdG9yIHdpbGwNCj4gPj4gY2VydGFpbmx5
IGRvIGEgZmluZSBqb2IsIGJ1dCBpbiBzb21lIGNhc2VzIHRoZXNlIHByb2JsZW1zIGRpc3RvcnQg
dGhlIHNlbnNlDQo+IG9mDQo+ID4+IHRoZSBzZW50ZW5jZXMgLSBmb3IgZXhhbXBsZSAnIFRoaXMg
d29yayBpcyBpbGx1bWluYXRlZCBieSBSRkM1ODg3LCBzbw0KPiB0aGFuaw0KPiA+PiBmb3IgUkZD
IDU4ODcgYXV0aG9ycycgdGhpcyBpcyBwcm9iYWJseSAnIFRoaXMgd29yayBpcyBpbnNwaXJlZCBi
eSAob3IgZGVyaXZlZA0KPiA+PiBmcm9tKSAgUkZDNTg4Nywgc28gdGhhbmtzIHRvIFJGQyA1ODg3
IGF1dGhvcnMnDQo+ID4+Pj4NCj4gPj4+PiA3LiBGcm9tIHRoZSBsaXN0IG9mIG9wZXJhdGlvbmFs
IGlzc3VlcyB0byBiZSB2ZXJpZmllZCBhcyBwZXIgUkZDIDU3MDYgSQ0KPiA+PiBiZWxpZXZlIHRo
YXQgdGhlIGZvbGxvd2luZyBhcHBsaWVzOiBIYXZlIHN1Z2dlc3Rpb25zIGZvciB2ZXJpZnlpbmcg
Y29ycmVjdA0KPiA+PiBvcGVyYXRpb24gYmVlbiBkaXNjdXNzZWQ/IEluIHRoaXMgY2FzZSB0aGlz
IHRyYW5zbGF0ZXMgaW50byB0aGUgcXVlc3Rpb24NCj4gPj4gd2hldGhlciB0aGVyZSBhcmUgYW55
IHJlY29tbWVuZGVkIHByYWN0aWNlcyB0byBlbnN1cmUgdGhhdCB0aGUNCj4gPj4gcmVudW1iZXJp
bmcgcHJvY2VzcyB3YXMgZnVsbHkgY29tcGxldGVkIGFuZCB0aGUgdHJhbnNmb3JtYXRpb24gdGhh
dA0KPiA+PiBvY2N1cnJlZCBpcyBleGFjdGx5IHdoYXQgdGhlIG9wZXJhdG9ycyBwbGFubmVkLg0K
PiA+Pj4+IFRoYW5rcyBhbmQgUmVnYXJkcywNCj4gPj4+Pg0KPiA+Pj4+IERhbg0KPiA+Pj4+DQo+
ID4+Pj4NCj4gPj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQo+ID4+PiBPUFMtRElSIG1haWxpbmcgbGlzdA0KPiA+Pj4gT1BTLURJUkBpZXRmLm9yZw0K
PiA+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vcHMtZGlyDQo+ID4+
Pg0KPiA+Pj4NCj4gPj4NCj4gPj4NCj4gPj4gLS0NCj4gPj4gUmVnYXJkcw0KPiA+PiAgICBCcmlh
biBDYXJwZW50ZXINCj4gPj4NCj4gPj4NCj4gPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj4gPj4gcmVudW0gbWFpbGluZyBsaXN0DQo+ID4+IHJlbnVt
QGlldGYub3JnDQo+ID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcmVu
dW0NCj4gPg0K

From internet-drafts@ietf.org  Mon Jan 14 18:33:09 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6307021F8B98; Mon, 14 Jan 2013 18:33:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDXvnIUHl5+O; Mon, 14 Jan 2013 18:33:08 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA2AB21F8B94; Mon, 14 Jan 2013 18:33:08 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130115023308.22568.13424.idtracker@ietfa.amsl.com>
Date: Mon, 14 Jan 2013 18:33:08 -0800
Cc: renum@ietf.org
Subject: [renum] I-D Action: draft-ietf-6renum-enterprise-06.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 02:33:09 -0000

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

	Title           : IPv6 Enterprise Network Renumbering Scenarios, Considera=
tions and Methods
	Author(s)       : Sheng Jiang
                          Bing Liu
                          Brian Carpenter
	Filename        : draft-ietf-6renum-enterprise-06.txt
	Pages           : 18
	Date            : 2013-01-14

Abstract:
   This document analyzes events that cause renumbering and describes
   the current renumbering methods. These are described in three
   categories: those applicable during network design, those applicable
   during preparation for renumbering, and those applicable during the
   renumbering operation.


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

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

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


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


From leo.liubing@huawei.com  Mon Jan 14 18:37:53 2013
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 13D2621F87A6 for <renum@ietfa.amsl.com>; Mon, 14 Jan 2013 18:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.732
X-Spam-Level: 
X-Spam-Status: No, score=-5.732 tagged_above=-999 required=5 tests=[AWL=0.867,  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 gaAj-qZIthCA for <renum@ietfa.amsl.com>; Mon, 14 Jan 2013 18:37:52 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 55BF121F8477 for <renum@ietf.org>; Mon, 14 Jan 2013 18:37:50 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOT81437; Tue, 15 Jan 2013 02:37:49 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 15 Jan 2013 02:37:41 +0000
Received: from SZXEML420-HUB.china.huawei.com (10.82.67.159) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 15 Jan 2013 02:37:48 +0000
Received: from SZXEML509-MBX.china.huawei.com ([10.82.67.37]) by szxeml420-hub.china.huawei.com ([10.82.67.159]) with mapi id 14.01.0323.003; Tue, 15 Jan 2013 10:37:40 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "renum@ietf.org" <renum@ietf.org>
Thread-Topic: [renum] I-D Action: draft-ietf-6renum-enterprise-06.txt
Thread-Index: AQHN8si5dbBU6mRH10uczmedTzgbd5hJrD3w
Date: Tue, 15 Jan 2013 02:37:39 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453CD18EB1@szxeml509-mbx>
References: <20130115023308.22568.13424.idtracker@ietfa.amsl.com>
In-Reply-To: <20130115023308.22568.13424.idtracker@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-06.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 02:37:53 -0000

Hi, all

The draft-enterprise has been updated according to the IESG's comments.

B.R.
Bing

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of internet-drafts@ietf.org
> Sent: Tuesday, January 15, 2013 10:33 AM
> To: i-d-announce@ietf.org
> Cc: renum@ietf.org
> Subject: [renum] I-D Action: draft-ietf-6renum-enterprise-06.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the IPv6 Site Renumbering Working Group of =
the
> IETF.
>=20
> 	Title           : IPv6 Enterprise Network Renumbering Scenarios,
> Considerations and Methods
> 	Author(s)       : Sheng Jiang
>                           Bing Liu
>                           Brian Carpenter
> 	Filename        : draft-ietf-6renum-enterprise-06.txt
> 	Pages           : 18
> 	Date            : 2013-01-14
>=20
> Abstract:
>    This document analyzes events that cause renumbering and describes
>    the current renumbering methods. These are described in three
>    categories: those applicable during network design, those applicable
>    during preparation for renumbering, and those applicable during the
>    renumbering operation.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6renum-enterprise-06
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-enterprise-06
>=20
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

From iesg-secretary@ietf.org  Tue Jan 15 07:50:15 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63DC121F8726; Tue, 15 Jan 2013 07:50:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ZCqBjfgA8oR; Tue, 15 Jan 2013 07:50:14 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A85421F88BC; Tue, 15 Jan 2013 07:50:14 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130115155014.4059.87184.idtracker@ietfa.amsl.com>
Date: Tue, 15 Jan 2013 07:50:14 -0800
Cc: 6renum chair <6renum-chairs@tools.ietf.org>, 6renum mailing list <renum@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [renum] Document Action: 'IPv6 Enterprise Network Renumbering Scenarios, Considerations and Methods' to Informational RFC	(draft-ietf-6renum-enterprise-06.txt)
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 15:50:15 -0000

The IESG has approved the following document:
- 'IPv6 Enterprise Network Renumbering Scenarios, Considerations and
   Methods'
  (draft-ietf-6renum-enterprise-06.txt) as Informational RFC

This document is the product of the IPv6 Site Renumbering Working Group.

The IESG contact persons are Ronald Bonica and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise/




Technical Summary: 

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

Working Group Summary: 
Very little controversy.  

Document Quality: 
RJ Atkinson did an especially thorough review during WGLC. 

Personnel: 

Shepherd: Lee Howard.  
AD: Ron Bonica 


From brian.e.carpenter@gmail.com  Thu Jan 24 05:39:54 2013
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 5DEBF21F8A25 for <renum@ietfa.amsl.com>; Thu, 24 Jan 2013 05:39:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.574
X-Spam-Level: 
X-Spam-Status: No, score=-101.574 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 atlV2kTFR0or for <renum@ietfa.amsl.com>; Thu, 24 Jan 2013 05:39:53 -0800 (PST)
Received: from mail-ee0-f50.google.com (mail-ee0-f50.google.com [74.125.83.50]) by ietfa.amsl.com (Postfix) with ESMTP id 4881E21F89E1 for <renum@ietf.org>; Thu, 24 Jan 2013 05:39:53 -0800 (PST)
Received: by mail-ee0-f50.google.com with SMTP id e51so4725994eek.23 for <renum@ietf.org>; Thu, 24 Jan 2013 05:39:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=Q0C7wo+ZuFjZwg9N6FuynX6MBPdTKKjLCvNQo+xvXcw=; b=UbfbzUa5MaYmS7bXMUd7s3j+noahTG7+kcdRKxakNfxJnj+u7RDPnnr/L1YTP6mPr9 Q4WtQagwUu+xb5x4SLfkA+W8VizZ/MGXmvKn5Ez0COyVU94cfdZaXdzfMzKUVs7mEXfi QYtcdFLoBa7QCmjujsxVhOCVXsLEVe1GsW8sDeXUQgA9G9162qsVU7gwVhTmD5yJZatF +5RLW+PzXKhAIHh0t2QPPksLGymJUs7Mgu/0S5vqmdpWds0AsLx5Adz0VmaqsUuEWFaq OHtRGhEkFO7ApYJ11yfDC7gQx0O5t/iV1+jyXvvdv/V7/bN5pkwYcmZAihC7MEPWWaq2 GTfw==
X-Received: by 10.14.194.195 with SMTP id m43mr6211856een.44.1359034792321; Thu, 24 Jan 2013 05:39:52 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-128.as13285.net. [2.102.219.128]) by mx.google.com with ESMTPS id k4sm35332116eep.15.2013.01.24.05.39.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Jan 2013 05:39:51 -0800 (PST)
Message-ID: <510139AE.2090200@gmail.com>
Date: Thu, 24 Jan 2013 13:39:58 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: renum@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [renum] Embedding Globally-Routable Internet Addresses Considered Harmful
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, 24 Jan 2013 13:39:54 -0000

Hi,

Somehow we managed to miss RFC 4085 "Embedding Globally-Routable
Internet Addresses Considered Harmful" when writing
draft-ietf-6renum-static-problem.

Would anyone here object to sliding in a citation during AUTH48?

Regards
   Brian Carpenter



From tjc@ecs.soton.ac.uk  Mon Jan 28 09:56:40 2013
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 C4D9621F8915 for <renum@ietfa.amsl.com>; Mon, 28 Jan 2013 09:56:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Cyct2NumiOi for <renum@ietfa.amsl.com>; Mon, 28 Jan 2013 09:56:40 -0800 (PST)
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 ECCB021F87E0 for <renum@ietf.org>; Mon, 28 Jan 2013 09:56:39 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r0SHuZZP016371 for <renum@ietf.org>; Mon, 28 Jan 2013 17:56:35 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r0SHuZZP016371
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1359395795; bh=hm92/O748/MFBkg1TKQ5o7jI5lY=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=tXlbVSRFbXUI/dvzDAAHgEAI2OcbUNTE6UOLtTsm8rLiiMew4kj+04a1OVFPVKmFi XcTFoRRLqZvVHoQGzZM+ozjsRWg9VTWtr6ZRR8KQbGhf7Q7PxHojpLyv/f5fb6HSe6 Qb5yAisdyaECUlGB0Np1ZK21mOPhk6nrx0WhbjPk=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p0RHuZ0430609726Vf ret-id none; Mon, 28 Jan 2013 17:56:35 +0000
Received: from [192.168.1.102] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r0SHuVOt007783 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Mon, 28 Jan 2013 17:56:31 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <510139AE.2090200@gmail.com>
Date: Mon, 28 Jan 2013 17:56:31 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|ae7c3cfafbd464da59eb121be3c73f2bp0RHuZ03tjc|ecs.soton.ac.uk|F514BE0E-6A66-4631-A74B-ACB5CC7E445A@ecs.soton.ac.uk>
References: <510139AE.2090200@gmail.com> <F514BE0E-6A66-4631-A74B-ACB5CC7E445A@ecs.soton.ac.uk>
To: "renum@ietf.org" <renum@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p0RHuZ043060972600; tid=p0RHuZ0430609726Vf; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r0SHuZZP016371
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [renum] Embedding Globally-Routable Internet Addresses Considered Harmful
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jan 2013 17:56:40 -0000

On 24 Jan 2013, at 13:39, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> Hi,
>=20
> Somehow we managed to miss RFC 4085 "Embedding Globally-Routable
> Internet Addresses Considered Harmful" when writing
> draft-ietf-6renum-static-problem.
>=20
> Would anyone here object to sliding in a citation during AUTH48?

This seems worthwhile, if it fits within the AUTH48 process. I must =
admit I had forgotten about that document.=20

Tim=

From brian.e.carpenter@gmail.com  Tue Jan 29 01:02:29 2013
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 C63B521F85E7 for <renum@ietfa.amsl.com>; Tue, 29 Jan 2013 01:02:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.407
X-Spam-Level: 
X-Spam-Status: No, score=-101.407 tagged_above=-999 required=5 tests=[AWL=0.284, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 u+ieV7rKWsrv for <renum@ietfa.amsl.com>; Tue, 29 Jan 2013 01:02:29 -0800 (PST)
Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com [74.125.83.53]) by ietfa.amsl.com (Postfix) with ESMTP id 4CF7321F85DF for <renum@ietf.org>; Tue, 29 Jan 2013 01:02:23 -0800 (PST)
Received: by mail-ee0-f53.google.com with SMTP id e53so101950eek.40 for <renum@ietf.org>; Tue, 29 Jan 2013 01:02:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=tH5EbRYUXQAxkPG1IaIwLxuEi7U5WzOUOVM5eudnbCQ=; b=wJSDoBukR2byfM4H1LLqbkx94cZIPQoDR4MFwf9sHdvGKEvmpDfgaf+ItFIvbgRH1K /zgBSYnRusslyXcbEsFz+Ib3TkE4e78LmtZHH6XQjH1SwY28lrvP/25vgEcL6tRcnA/W cdB4IXbJ4QM/4ut3uLe73mjT1z7JFRzuLwQyuuNj6UxMVYQr4BJpWyFETYEdYkYgkIRH 2lY7JaldYrjlb1Blu3DXemkmNWVf+YZio5S42HtDz32weSKKt0xnJmw5F+zvykTEqUdM bAUG6wNrV4nat1b1vfIouII7U+bOG8HE6sYC7yl+HYgCpR5/+q/5BN7nlEN++UbU/JDC Gdkw==
X-Received: by 10.14.218.71 with SMTP id j47mr1306711eep.28.1359450142353; Tue, 29 Jan 2013 01:02:22 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-172.as13285.net. [2.102.217.172]) by mx.google.com with ESMTPS id 44sm19595540eek.5.2013.01.29.01.02.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Jan 2013 01:02:21 -0800 (PST)
Message-ID: <51079021.2030406@gmail.com>
Date: Tue, 29 Jan 2013 09:02:25 +0000
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: Tim Chown <tjc@ecs.soton.ac.uk>
References: <510139AE.2090200@gmail.com>	<F514BE0E-6A66-4631-A74B-ACB5CC7E445A@ecs.soton.ac.uk> <EMEW3|ae7c3cfafbd464da59eb121be3c73f2bp0RHuZ03tjc|ecs.soton.ac.uk|F514BE0E-6A66-4631-A74B-ACB5CC7E445A@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|ae7c3cfafbd464da59eb121be3c73f2bp0RHuZ03tjc|ecs.soton.ac.uk|F514BE0E-6A66-4631-A74B-ACB5CC7E445A@ecs.soton.ac.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Embedding Globally-Routable Internet Addresses Considered Harmful
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, 29 Jan 2013 09:02:30 -0000

On 28/01/2013 17:56, Tim Chown wrote:
> On 24 Jan 2013, at 13:39, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> Hi,
>>
>> Somehow we managed to miss RFC 4085 "Embedding Globally-Routable
>> Internet Addresses Considered Harmful" when writing
>> draft-ietf-6renum-static-problem.
>>
>> Would anyone here object to sliding in a citation during AUTH48?
> 
> This seems worthwhile, if it fits within the AUTH48 process. I must admit I had forgotten about that document. 
> 

Hmm. I was just looking at the draft to see where this would fit in,
and the answer is nowhere, without creating a new section, which is
really too much for AUTH48. I do think we should consider RFC 4085
as an important recommendation, however.

    Brian

From tjc@ecs.soton.ac.uk  Tue Jan 29 01:21:02 2013
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 CB7E321F8629 for <renum@ietfa.amsl.com>; Tue, 29 Jan 2013 01:21:00 -0800 (PST)
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 PmlpJzAlrcot for <renum@ietfa.amsl.com>; Tue, 29 Jan 2013 01:20:59 -0800 (PST)
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 9F59521F8837 for <renum@ietf.org>; Tue, 29 Jan 2013 01:20:58 -0800 (PST)
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 r0T9Kpl5001582 for <renum@ietf.org>; Tue, 29 Jan 2013 09:20:51 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r0T9Kpl5001582
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1359451251; bh=6Pl0dsejD5T+6oEt4j11H4BHAEI=; h=From:Mime-Version:Subject:Date:References:To:In-Reply-To; b=A1fstLQrOzFuLwGJ0yWIrlIP4Dis76AfyN3kSJs4W8DgyxwsDPY15DJHUPV0rdYUX KXDl5UhFdxGRi4DYvimJJLm+mDq2UpBHqLBhCpK/s32mM76P/t96lDVUFWm2ynnKny XidMultcWKqFM3LRnkglqV+KYfhw0wcbgyaQMLbM=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p0S9Kp0430617110CW ret-id none; Tue, 29 Jan 2013 09:20:51 +0000
Received: from [192.168.1.102] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r0T9KiGO010896 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Tue, 29 Jan 2013 09:20:45 GMT
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_07C7B362-0CA5-4394-ADDF-5638AF4EDB81"
Message-ID: <EMEW3|9c8366221dcbf73cbfd7bf2a0cc7f0acp0S9Kp03tjc|ecs.soton.ac.uk|C0385DA0-9F01-4146-B8DB-99953DF90E04@ecs.soton.ac.uk>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Date: Tue, 29 Jan 2013 09:20:45 +0000
References: <510139AE.2090200@gmail.com>	<F514BE0E-6A66-4631-A74B-ACB5CC7E445A@ecs.soton.ac.uk> <EMEW3|ae7c3cfafbd464da59eb121be3c73f2bp0RHuZ03tjc|ecs.soton.ac.uk|F514BE0E-6A66-4631-A74B-ACB5CC7E445A@ecs.soton.ac.uk> <51079021.2030406@gmail.com> <C0385DA0-9F01-4146-B8DB-99953DF90E04@ecs.soton.ac.uk>
To: "renum@ietf.org" <renum@ietf.org>
In-Reply-To: <51079021.2030406@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p0S9Kp043061711000; tid=p0S9Kp0430617110CW; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r0T9Kpl5001582
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [renum] Embedding Globally-Routable Internet Addresses Considered Harmful
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, 29 Jan 2013 09:21:03 -0000

--Apple-Mail=_07C7B362-0CA5-4394-ADDF-5638AF4EDB81
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 29 Jan 2013, at 09:02, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 28/01/2013 17:56, Tim Chown wrote:
>> On 24 Jan 2013, at 13:39, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>=20
>>> Hi,
>>>=20
>>> Somehow we managed to miss RFC 4085 "Embedding Globally-Routable
>>> Internet Addresses Considered Harmful" when writing
>>> draft-ietf-6renum-static-problem.
>>>=20
>>> Would anyone here object to sliding in a citation during AUTH48?
>>=20
>> This seems worthwhile, if it fits within the AUTH48 process. I must =
admit I had forgotten about that document.=20
>>=20
>=20
> Hmm. I was just looking at the draft to see where this would fit in,
> and the answer is nowhere, without creating a new section, which is
> really too much for AUTH48. I do think we should consider RFC 4085
> as an important recommendation, however.


I see what you mean; the discussion is specifically about long-lived =
static addresses, rather than embedding globally routable addresses in =
configurations (that may or may not be long-lived).

You could perhaps add "While a BCP exists discouraging use of static =
addresses [RFC4085], their use is still very much common practice." =
after the first sentence in the introduction?

Or in the enterprise draft you could maybe add RFC 4085 to the sentence =
"The reader is assumed to be familiar with [RFC4192] and [RFC5887]", =
given the previous sentence talks about current practices, and 4085 is a =
BCP, albeit one not followed as much as one might hope.

Again, it depends on the limitations of AUTH48 tweaks. It would be good =
to include a reference to this in the suite of 6renum deliverables. I =
haven't looked at gap-analysis (which is more open to minor edits being =
with the IESG now).

Tim=

--Apple-Mail=_07C7B362-0CA5-4394-ADDF-5638AF4EDB81
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On 29 Jan 2013, at 09:02, Brian E Carpenter &lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a=
>&gt; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">On 28/01/2013 17:56, Tim Chown wrote:<br><blockquote =
type=3D"cite">On 24 Jan 2013, at 13:39, Brian E Carpenter &lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a=
>&gt; wrote:<br><br><blockquote type=3D"cite">Hi,<br><br>Somehow we =
managed to miss RFC 4085 "Embedding Globally-Routable<br>Internet =
Addresses Considered Harmful" when =
writing<br>draft-ietf-6renum-static-problem.<br><br>Would anyone here =
object to sliding in a citation during AUTH48?<br></blockquote><br>This =
seems worthwhile, if it fits within the AUTH48 process. I must admit I =
had forgotten about that document. <br><br></blockquote><br>Hmm. I was =
just looking at the draft to see where this would fit in,<br>and the =
answer is nowhere, without creating a new section, which is<br>really =
too much for AUTH48. I do think we should consider RFC 4085<br>as an =
important recommendation, =
however.<br></blockquote></div><div><br></div>I see what you mean; the =
discussion is specifically about long-lived static addresses, rather =
than embedding globally routable addresses in configurations (that may =
or may not be long-lived).<div><br><div>You could perhaps add "While a =
BCP exists discouraging use of static addresses [RFC4085], their use is =
still very much common practice." after the first sentence in the =
introduction?</div><div><br></div><div>Or in the enterprise draft you =
could maybe add RFC 4085 to the sentence "The&nbsp;reader is assumed to =
be familiar with [<a href=3D"http://tools.ietf.org/html/rfc4192" =
title=3D"&quot;Procedures for Renumbering an IPv6 Network without a Flag =
Day&quot;">RFC4192</a>] and [<a =
href=3D"http://tools.ietf.org/html/rfc5887" title=3D"&quot;Renumbering =
Still Needs Work&quot;">RFC5887</a>]", given the previous sentence talks =
about current practices, and 4085 is a BCP, albeit one not followed as =
much as one might hope.</div><div><br></div><div>Again, it depends on =
the limitations of AUTH48 tweaks. It would be good to include a =
reference to this in the suite of 6renum deliverables. I haven't looked =
at gap-analysis (which is more open to minor edits being with the IESG =
now).</div><div><br></div><div>Tim</div></div></body></html>=

--Apple-Mail=_07C7B362-0CA5-4394-ADDF-5638AF4EDB81--
