
From leo.liubing@huawei.com  Thu May  2 04:02:48 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 314B621F99A2; Thu,  2 May 2013 04:02:48 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2o2wosR0FX7m; Thu,  2 May 2013 04:02:44 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4A92421F97D9; Thu,  2 May 2013 04:02:42 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ASJ52063; Thu, 02 May 2013 11:02:40 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 2 May 2013 12:01:40 +0100
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 2 May 2013 12:02:34 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.13]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.01.0323.007; Thu, 2 May 2013 19:02:31 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Robert Sparks <rjsparks@nostrum.com>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>
Thread-Topic: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt
Thread-Index: AQHORcBlVceOTpKzJEa6ksAFu9J9J5jxsrWw
Date: Thu, 2 May 2013 11:02:30 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com>
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com>
In-Reply-To: <517FF231.3080700@nostrum.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
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [renum] Gen-art telechat review: draft-ietf-6renum-gap-analysis-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: Thu, 02 May 2013 11:02:48 -0000

Hi, Robert

Thanks a lot for your continuous careful review.
Please see replies inline.

> -----Original Message-----
> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> Sent: Wednesday, May 01, 2013 12:33 AM
> To: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org
> Cc: gen-art@ietf.org; ietf@ietf.org
> Subject: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-6renum-gap-analysis-05.txt
> Reviewer: Robert Sparks
> Review Date: April 1, 2013
> IETF LC End Date: April 10, 2013
> IESG Telechat date: May 16, 2013
>=20
> Summary: Ready with nits (that border on minor issues)
>=20
> This update improved the readability significantly, and addressed my
> major concern about being able to build a list of the gaps. Thank you.
>=20
> There are a few issues from my last call review that are still not
> addressed.
> I have left the classification of minor issue vs nits the same as the
> original review to make referring to the earlier review easier,
> but please consider all of these Nits. The IESG will need to decide
> whether to escalate them.
>=20
> I've trimmed away the points that were addressed.
>=20
> On 4/1/13 3:46 PM, Robert Sparks wrote:
> > ----------------------
> > Minor issues:
> >
> > The document currently references
> > draft-chown-v6ops-renumber-thinkabout several times.
> > That document is long expired (2006). It would be better to simply
> > restate what is
> > important from that document here and reference it only once in the
> > acknowlegements
> > rather than send the reader off to read it.
> This version still references that long expired draft. There was also
> conversation on apps-discuss
> about making that reference normative. IMHO, this is not the right way
> to treat the RFC series, and
> strongly encourage moving the text that you want to reference into
> something that will
> become an RFC.

[Bing] Maybe Brian's suggestion of putting some texts into an appendix is a=
 good way. We'll discuss this problem when make the next time update.

> > Should section 8 belong to some other document? It looks like
> > operational renumbering
> > advice/considerations, but doesn't seem to be exploring renumbering
> > gaps, except for
> > the very short section 8.2 which says "we need a better mechanism"
> > without much explanation.
> Afaict, this wasn't addressed at all. In particular, "we need a better
> mechanism" is still all that
> section 8.2 says.

[Bing] Sorry for leaving it out. Will do in next update.

> >
> > Section 5.1, first bullet. The list below "the impact of ambiguous M/O
> > flags" says things like
> > "there is no standard" and "it is unspecified". I think you are trying
> > to say that there is
> > ambiguity in what's written, not that nothing's written. This entire
> > list would benefit from
> > being recast in terms of what needs to be done (what are the gaps?).
> This text remains unmodified.

[Bing] We made revision focusing on explaining "what are the gaps", but the=
 texts change was omitted, will do in next update.

> > ----------------------
> > Nits/editorial comments:
> >
> > There are a few sentences ending with "etc." in the document. Please
> > consider deleting the
> > word from the list - it doesn't help each sentence make its point.
> There were some changes, but mostly these still exist. I'll leave
> pressing this point further to the RFC Editor.

[Bing] A professional language/editorial check would be helpful.=20

> >
> > Seciton 7.1: The first bullet does not parse. If I guess its meaning
> > correctly
> > (that it would be benificial to tell hosts that local DNS has been
> > updated and
> > they may want to make fresh queries), please be careful with the
> > wording. The
> > hosts don't know which names are likely to resolve locally.
> This text remained unchanged, and when coming back to the document for a
> re-review
> (which is somewhat like coming back to an RFC you've read before just
> for reference),
> it's even harder to understand what it's trying to say than it was when
> reading the document
> linearly.
>=20
> I think you are trying to say
> "A notification mechanism may be needed to indicate _to_ hosts that a
> renumbering event has _changed how local recursive DNS servers will
> respond_. That mechanism may also need to indicate that such a change
> will happen at a specific time in the future."

[Bing] I think it's a better description. Will update, thanks much.=20

>=20
> >
> > Section 7.1, third bullet - This isn't obviously about notification.
> > Why is it
> > in this section? What's the gap this is trying to identify?
> This text was unchanged.

[Bing] For example, if border routers enabled egress filtering based on the=
 SIP, then the router need to know the renumbering events on some internal =
nodes. We'll make it clear in the next version.

> > Section 9.4 - what is it about these that make them gaps, much less
> > unsolvable gaps.
> > Is this discussion in the wrong section of the document?
> This is now section 10.3 and is mostly unchanged. It's still not clear
> why this discussion is in the "unsolvable gaps" section.

[Bing] We considered the two points (ID/Locator overloading in transport la=
yer & address caching in app layer ) are too fundamental that might not be =
proper to modify them just in terms of renumbering.

Best regards,
Bing

From tjc@ecs.soton.ac.uk  Mon May  6 09:26:51 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 059BD21F860B; Mon,  6 May 2013 09:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MM2Kv4sCixzj; Mon,  6 May 2013 09:26:50 -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 7328A21F859B; Mon,  6 May 2013 09:26:49 -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 r46GQXx2031601;  Mon, 6 May 2013 17:26:33 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r46GQXx2031601
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1367857594; bh=a4l+aSSARNwGz2AqrW5G4eZdHFM=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=L82Xa2K/Kwfl4zOPNpitfsUTWpEkGMuBe5kK7NKyVoWWPWRwqcB1T/6mizDZyWsKB mXLdjfWP5Qi8+e6PaZH763lxFVvGf7/i7cVK4OZKVyDE/SVQqvc8aqkcu3fcSNYh+H /Br4D/UEvQ85KDwBdpY3AjzBzu3TChsOxf9N8LEY=
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 p45HQX0430647178yw ret-id none; Mon, 06 May 2013 17:26:33 +0100
Received: from [192.168.1.110] (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 r46GPCHe011521 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 May 2013 17:25:13 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <517FE691.2070707@bogus.com>
Date: Mon, 6 May 2013 17:25:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|8d29bcd8f9cb5293eee024b76facd925p45HQX03tjc|ecs.soton.ac.uk|1F756E4B-5011-4B49-AB77-F4D51BC20E94@ecs.soton.ac.uk>
References: <5159F239.1060001@nostrum.com>	<8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com>	<515AABB5.5050202@gmail.com> <517FE44C.7000609@nostrum.com> <517FE691.2070707@bogus.com> <1F756E4B-5011-4B49-AB77-F4D51BC20E94@ecs.soton.ac.uk>
To: joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p45HQX043064717800; tid=p45HQX0430647178yw; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=8:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r46GQXx2031601
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2013 16:26:52 -0000

On 30 Apr 2013, at 16:43, joel jaeggli <joelja@bogus.com> wrote:

> On 4/30/13 8:33 AM, Robert Sparks wrote:
>> On 4/2/13 4:58 AM, Brian E Carpenter wrote:
>>> Just picking a couple of points for further comment:
>>>=20
>>> On 02/04/2013 08:46, Liubing (Leo) wrote:
>>>>=20
>>>> [Bing] draft-chown-v6ops-renumber-thinkabout is an important input =
for the gap analysis. Although the draft is expired, most of the content =
are still valid.
>>>> draft-chown is a more comprehensive analysis, while the gap draft =
is focusing on gaps in enterprise renumbering. So it might not easy to =
abstract several points as important from draft-chown to this draft. We =
actually encourage people to read it.
>>> Robert is right, though, sending people to a long-expired draft is a =
bad idea.
> I'm not sure I see that as worse than referring to Wikipedia, an =
expired draft has the property that it's not going to change. I have no =
problem with the idea that it would be an informative reference.   but =
yes it's a bit much to say go read this.
>>> Of course we have to acknowledge it, but maybe we should pull some =
of its text
>>> into an Appendix.
>>>=20
>>> Tim Chown, any opinion?
>> The most recent version (and the one slated for the next telechat) =
still has this long-expired draft referenced.


Hi,

The old renumbering "thinkabout" draft came out of experiments on IPv6 =
renumbering we did in 6NET some 10 (yikes!) years ago, for both =
enterprise and ISP networks. I think most of what was written is still =
applicable.  Brian borrowed a fair deal of it for RFC 5887.  I stopped =
work on it as there was little/no interest in the problem in v6ops at =
the time (or whatever v6ops was called back then). We produced technical =
6NET reports separately, and did some follow-up work with Cisco =
separately.

Personally I don't mind if the principles are mentioned without the =
explicit reference - an ack in the Acknowledgements is adequate.=20

It would be interesting to review the "thinkabout" draft to see how much =
still holds true.  Glancing at it, sections like "Application and =
Service-Oriented Issues" are still very much relevant. I guess Stig and =
I could consider advancing it along the Independent Submission path, or =
look for publication to an appropriate journal.  Life is short :)

Tim


From internet-drafts@ietf.org  Fri May 10 05:50:57 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 71C7D21F87FB; Fri, 10 May 2013 05:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Jz1p6bioiaB; Fri, 10 May 2013 05:50:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0740221F86CA; Fri, 10 May 2013 05:50:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.44.p7
Message-ID: <20130510125054.11255.38356.idtracker@ietfa.amsl.com>
Date: Fri, 10 May 2013 05:50:54 -0700
Cc: renum@ietf.org
Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-07.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 12:50:57 -0000

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

	Title           : IPv6 Site Renumbering Gap Analysis
	Author(s)       : Bing Liu
                          Sheng Jiang
                          Brian Carpenter
                          Stig Venaas
                          Wesley George
	Filename        : draft-ietf-6renum-gap-analysis-07.txt
	Pages           : 24
	Date            : 2013-05-10

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




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

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

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


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


From leo.liubing@huawei.com  Fri May 10 05:57:56 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 8CC8C21F8F4A for <renum@ietfa.amsl.com>; Fri, 10 May 2013 05:57:56 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YdK0Hg5tYTRq for <renum@ietfa.amsl.com>; Fri, 10 May 2013 05:57:52 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C67AC21F8E77 for <renum@ietf.org>; Fri, 10 May 2013 05:57:51 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARG35845; Fri, 10 May 2013 12:57:50 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 10 May 2013 13:57:30 +0100
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 10 May 2013 20:57:45 +0800
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.13]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.01.0323.007; Fri, 10 May 2013 20:57:40 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "renum@ietf.org" <renum@ietf.org>
Thread-Topic: About the Gap-07 update-//FW: [renum] I-D Action: draft-ietf-6renum-gap-analysis-07.txt
Thread-Index: AQHOTX3zCWUrq8SPKkWVnLeDDrsitA==
Date: Fri, 10 May 2013 12:57:39 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D701DB9@nkgeml506-mbx.china.huawei.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: [renum] About the Gap-07 update-//FW: I-D Action: draft-ietf-6renum-gap-analysis-07.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 12:57:56 -0000

Hi, Dear all

We updated the draft according to the recent GenART reviewer (Robert)'s com=
ments.=20

Revisions summary:
1. Deleted "DHCPv6-only address management might not be applicable" topic i=
n section 5.1, according to recent discussion that DHCPv6 relying on ND RA =
messages is not harmful. It is even an advantage comparing IPv4.
2. Deleted [draft-chow] in reference and main texts, leaving it in acknowle=
dgement and added a bit more explanation.
3. In 5.1, modified the expression of "there is no standard for M/O flags b=
ehavior", since in fact there's some behavior description in standard, but =
there is ambiguity.
4. In 7.1, made a better description of the DNS server update notification =
to the hosts.
5. In 7.1, made a clearer description of border router aware of the inside =
hosts renumbering.
6. In the beginning of section 8, added a brief clarification of this secti=
on; in the end of section 8.1, added a brief summary; in section 8.2, added=
 some more description of "we need a better mechanism" for MIPv6 IP home ad=
dress renumbering issue.=20
7. Moved two references from normative to informative; added two informativ=
e references.

Any comment, please feel free to post. Thanks.

Best regards,
Bing

-----Original Message-----
From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of i=
nternet-drafts@ietf.org
Sent: Friday, May 10, 2013 8:51 PM
To: i-d-announce@ietf.org
Cc: renum@ietf.org
Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-07.txt


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

	Title           : IPv6 Site Renumbering Gap Analysis
	Author(s)       : Bing Liu
                          Sheng Jiang
                          Brian Carpenter
                          Stig Venaas
                          Wesley George
	Filename        : draft-ietf-6renum-gap-analysis-07.txt
	Pages           : 24
	Date            : 2013-05-10

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




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

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

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


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

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

From rjsparks@nostrum.com  Fri May 10 08:12:48 2013
Return-Path: <rjsparks@nostrum.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 8FA4B21F8CB4; Fri, 10 May 2013 08:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lym-4T45rWIR; Fri, 10 May 2013 08:12:47 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8131A21F8C40; Fri, 10 May 2013 08:12:46 -0700 (PDT)
Received: from unnumerable.local (mobile-166-147-077-105.mycingular.net [166.147.77.105]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r4AFCcj3079542 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Fri, 10 May 2013 10:12:39 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <518D0E64.6020504@nostrum.com>
Date: Fri, 10 May 2013 10:12:36 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Liubing (Leo)" <leo.liubing@huawei.com>
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 166.147.77.105 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [renum] Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
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, 10 May 2013 15:12:48 -0000

Thanks Bing -

The updates make the document better, and I appreciate the resolution of 
referencing Tim's expired draft.
I think you've addressed all my comments except for the one on section 
5.1, but that's ok.

For completeness and ease on the ADs, here's an updated summary:

Document: draft-ietf-6renum-gap-analysis-05.txt
Reviewer: Robert Sparks
Review Date: May 10, 2013
IETF LC End Date: April 10, 2013
IESG Telechat date: May 16, 2013

Summary: Ready



On 5/2/13 6:02 AM, Liubing (Leo) wrote:
> Hi, Robert
>
> Thanks a lot for your continuous careful review.
> Please see replies inline.
>
>> -----Original Message-----
>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>> Sent: Wednesday, May 01, 2013 12:33 AM
>> To: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org
>> Cc: gen-art@ietf.org; ietf@ietf.org
>> Subject: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt
>>
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please wait for direction from your document shepherd
>> or AD before posting a new version of the draft.
>>
>> Document: draft-ietf-6renum-gap-analysis-05.txt
>> Reviewer: Robert Sparks
>> Review Date: April 1, 2013
>> IETF LC End Date: April 10, 2013
>> IESG Telechat date: May 16, 2013
>>
>> Summary: Ready with nits (that border on minor issues)
>>
>> This update improved the readability significantly, and addressed my
>> major concern about being able to build a list of the gaps. Thank you.
>>
>> There are a few issues from my last call review that are still not
>> addressed.
>> I have left the classification of minor issue vs nits the same as the
>> original review to make referring to the earlier review easier,
>> but please consider all of these Nits. The IESG will need to decide
>> whether to escalate them.
>>
>> I've trimmed away the points that were addressed.
>>
>> On 4/1/13 3:46 PM, Robert Sparks wrote:
>>> ----------------------
>>> Minor issues:
>>>
>>> The document currently references
>>> draft-chown-v6ops-renumber-thinkabout several times.
>>> That document is long expired (2006). It would be better to simply
>>> restate what is
>>> important from that document here and reference it only once in the
>>> acknowlegements
>>> rather than send the reader off to read it.
>> This version still references that long expired draft. There was also
>> conversation on apps-discuss
>> about making that reference normative. IMHO, this is not the right way
>> to treat the RFC series, and
>> strongly encourage moving the text that you want to reference into
>> something that will
>> become an RFC.
> [Bing] Maybe Brian's suggestion of putting some texts into an appendix is a good way. We'll discuss this problem when make the next time update.
>
>>> Should section 8 belong to some other document? It looks like
>>> operational renumbering
>>> advice/considerations, but doesn't seem to be exploring renumbering
>>> gaps, except for
>>> the very short section 8.2 which says "we need a better mechanism"
>>> without much explanation.
>> Afaict, this wasn't addressed at all. In particular, "we need a better
>> mechanism" is still all that
>> section 8.2 says.
> [Bing] Sorry for leaving it out. Will do in next update.
>
>>> Section 5.1, first bullet. The list below "the impact of ambiguous M/O
>>> flags" says things like
>>> "there is no standard" and "it is unspecified". I think you are trying
>>> to say that there is
>>> ambiguity in what's written, not that nothing's written. This entire
>>> list would benefit from
>>> being recast in terms of what needs to be done (what are the gaps?).
>> This text remains unmodified.
> [Bing] We made revision focusing on explaining "what are the gaps", but the texts change was omitted, will do in next update.
>
>>> ----------------------
>>> Nits/editorial comments:
>>>
>>> There are a few sentences ending with "etc." in the document. Please
>>> consider deleting the
>>> word from the list - it doesn't help each sentence make its point.
>> There were some changes, but mostly these still exist. I'll leave
>> pressing this point further to the RFC Editor.
> [Bing] A professional language/editorial check would be helpful.
>
>>> Seciton 7.1: The first bullet does not parse. If I guess its meaning
>>> correctly
>>> (that it would be benificial to tell hosts that local DNS has been
>>> updated and
>>> they may want to make fresh queries), please be careful with the
>>> wording. The
>>> hosts don't know which names are likely to resolve locally.
>> This text remained unchanged, and when coming back to the document for a
>> re-review
>> (which is somewhat like coming back to an RFC you've read before just
>> for reference),
>> it's even harder to understand what it's trying to say than it was when
>> reading the document
>> linearly.
>>
>> I think you are trying to say
>> "A notification mechanism may be needed to indicate _to_ hosts that a
>> renumbering event has _changed how local recursive DNS servers will
>> respond_. That mechanism may also need to indicate that such a change
>> will happen at a specific time in the future."
> [Bing] I think it's a better description. Will update, thanks much.
>
>>> Section 7.1, third bullet - This isn't obviously about notification.
>>> Why is it
>>> in this section? What's the gap this is trying to identify?
>> This text was unchanged.
> [Bing] For example, if border routers enabled egress filtering based on the SIP, then the router need to know the renumbering events on some internal nodes. We'll make it clear in the next version.
>
>>> Section 9.4 - what is it about these that make them gaps, much less
>>> unsolvable gaps.
>>> Is this discussion in the wrong section of the document?
>> This is now section 10.3 and is mostly unchanged. It's still not clear
>> why this discussion is in the "unsolvable gaps" section.
> [Bing] We considered the two points (ID/Locator overloading in transport layer & address caching in app layer ) are too fundamental that might not be proper to modify them just in terms of renumbering.
>
> Best regards,
> Bing


From stig@cisco.com  Fri May 10 09:58:24 2013
Return-Path: <stig@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 2A5AC21F89D5; Fri, 10 May 2013 09:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6np02ebi3SSB; Fri, 10 May 2013 09:58:19 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 2A19621F8F12; Fri, 10 May 2013 09:58:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=478; q=dns/txt; s=iport; t=1368205098; x=1369414698; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=cCAwPwFspHJgIkwZuzYsQObc7I8lI1aJxsONWU4/1Jk=; b=dRz2bbBu+1EMoho0QG1FMr+BOTFtzhzTky3tbqWKMyPsOkQHg+nVlAag mgM5L+0CZIvbUPi2ELcHWuitsI+DkDR7ZfmqEMgydB2UCjqibWiN8PK+y yceZ3ima1IbLHYKVddfZjH3Qb4Nech+ZRWhRFUGa6TMf8Cgd6TYKN4BVK M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFANckjVGrRDoG/2dsb2JhbABSgwe9YoJwfBZ0gh8BAQEEOEABEAsOCgkWDwkDAgECAUUGDQEHAQEXh3C9W48oB4NVA4kajhKGFosfgVeBWBw
X-IronPort-AV: E=Sophos;i="4.87,648,1363132800"; d="scan'208";a="78224302"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 10 May 2013 16:58:17 +0000
Received: from [10.33.12.93] ([10.33.12.93]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4AGwGdm020541; Fri, 10 May 2013 16:58:16 GMT
Message-ID: <518D2728.9000606@cisco.com>
Date: Fri, 10 May 2013 09:58:16 -0700
From: Stig Venaas <stig@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com> <518D0E64.6020504@nostrum.com>
In-Reply-To: <518D0E64.6020504@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>
Subject: Re: [renum] Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
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, 10 May 2013 16:58:24 -0000

On 5/10/2013 8:12 AM, Robert Sparks wrote:
> Thanks Bing -
>
> The updates make the document better, and I appreciate the resolution of
> referencing Tim's expired draft.

So the solution is to not reference it? I see the name of the draft is
mentioned in the acknowledgments as:
  [draft-chown-v6ops-renumber-thinkabout].

Shouldn't it then be an informational reference? It doesn't make sense
to me to mention a draft in the text and not have a reference.

Stig


From brian.e.carpenter@gmail.com  Fri May 10 12:35:06 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 17B6921F871C; Fri, 10 May 2013 12:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35uAp+djjH17; Fri, 10 May 2013 12:35:05 -0700 (PDT)
Received: from mail-ia0-x235.google.com (mail-ia0-x235.google.com [IPv6:2607:f8b0:4001:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 76D3621F86BB; Fri, 10 May 2013 12:35:05 -0700 (PDT)
Received: by mail-ia0-f181.google.com with SMTP id f27so4895301iae.26 for <multiple recipients>; Fri, 10 May 2013 12:35:05 -0700 (PDT)
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=EJ2AfnDAPi4SEvRs54lKASllD7RywbFqg465zkTjASo=; b=VI3nPqMjqwbnYAAUU0RPAB9kOPhnO6v9bC4J9hkq3KITLuPLPilCFi2mWokb5sfNqU I1EuwvSvtycS1VL+K8S39P8WAn7ev5O93vNSRRdPA/HrUw8EX/bjZ9VsMUsH75bXhQGL oRohPgagq7ScqSykc84c8vx1bcG2A0XseE+MY22PCWFzay6ZY8J5oQaDJoRjV+Q5M4XU hMeXZl9tcz+9zeT9g2X43RAdSYOxYcYkuHqmmewRwDHfu6Xvuyq75EoCQAVoY/lMjoFy scEdO3zlhZjtYIhQKs1tKUN6G6RWysD79RR5a/CgKPxPLQ2QOdzHOs/8lfVYiAias6+F rvhQ==
X-Received: by 10.42.168.198 with SMTP id x6mr8274651icy.45.1368214505068; Fri, 10 May 2013 12:35:05 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id lr1sm6051138igb.6.2013.05.10.12.35.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 10 May 2013 12:35:04 -0700 (PDT)
Message-ID: <518D4BF0.8030307@gmail.com>
Date: Sat, 11 May 2013 07:35:12 +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: Stig Venaas <stig@cisco.com>
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com> <518D0E64.6020504@nostrum.com> <518D2728.9000606@cisco.com>
In-Reply-To: <518D2728.9000606@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [renum] Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
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, 10 May 2013 19:35:06 -0000

On 11/05/2013 04:58, Stig Venaas wrote:
> On 5/10/2013 8:12 AM, Robert Sparks wrote:
>> Thanks Bing -
>>
>> The updates make the document better, and I appreciate the resolution of
>> referencing Tim's expired draft.
> 
> So the solution is to not reference it? I see the name of the draft is
> mentioned in the acknowledgments as:
>  [draft-chown-v6ops-renumber-thinkabout].
> 
> Shouldn't it then be an informational reference? It doesn't make sense
> to me to mention a draft in the text and not have a reference.

YMMV, but I expect the RFC Editor will resolve this.

   Brian


From leo.liubing@huawei.com  Sun May 12 18:59: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 EC19521F8D41; Sun, 12 May 2013 18:59:09 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ODqeG74CbjmY; Sun, 12 May 2013 18:59:05 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A94E921F8464; Sun, 12 May 2013 18:59:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARH79014; Mon, 13 May 2013 01:59:03 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 13 May 2013 02:58:45 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 13 May 2013 02:59:02 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.102]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Mon, 13 May 2013 09:58:59 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Robert Sparks <rjsparks@nostrum.com>
Thread-Topic: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
Thread-Index: AQHOTZDVCx2KD3Z6N0mmZwguV2SXypkCXtWQ
Date: Mon, 13 May 2013 01:58:59 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D70E78D@nkgeml506-mbx.china.huawei.com>
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com> <518D0E64.6020504@nostrum.com>
In-Reply-To: <518D0E64.6020504@nostrum.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
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [renum] Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
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, 13 May 2013 01:59:10 -0000

Hi, Robert

Your careful review and comments really helped improving the document a lot=
.
Many thanks to you.

All the best,
Bing

> -----Original Message-----
> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> Sent: Friday, May 10, 2013 11:13 PM
> To: Liubing (Leo)
> Cc: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org;
> gen-art@ietf.org; ietf@ietf.org
> Subject: Re: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.t=
xt
> (updated for -07)
>=20
> Thanks Bing -
>=20
> The updates make the document better, and I appreciate the resolution of
> referencing Tim's expired draft.
> I think you've addressed all my comments except for the one on section
> 5.1, but that's ok.
>=20
> For completeness and ease on the ADs, here's an updated summary:
>=20
> Document: draft-ietf-6renum-gap-analysis-05.txt
> Reviewer: Robert Sparks
> Review Date: May 10, 2013
> IETF LC End Date: April 10, 2013
> IESG Telechat date: May 16, 2013
>=20
> Summary: Ready
>=20
>=20
>=20
> On 5/2/13 6:02 AM, Liubing (Leo) wrote:
> > Hi, Robert
> >
> > Thanks a lot for your continuous careful review.
> > Please see replies inline.
> >
> >> -----Original Message-----
> >> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> >> Sent: Wednesday, May 01, 2013 12:33 AM
> >> To: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org
> >> Cc: gen-art@ietf.org; ietf@ietf.org
> >> Subject: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.tx=
t
> >>
> >> I am the assigned Gen-ART reviewer for this draft. For background on
> >> Gen-ART, please see the FAQ at
> >> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >>
> >> Please wait for direction from your document shepherd
> >> or AD before posting a new version of the draft.
> >>
> >> Document: draft-ietf-6renum-gap-analysis-05.txt
> >> Reviewer: Robert Sparks
> >> Review Date: April 1, 2013
> >> IETF LC End Date: April 10, 2013
> >> IESG Telechat date: May 16, 2013
> >>
> >> Summary: Ready with nits (that border on minor issues)
> >>
> >> This update improved the readability significantly, and addressed my
> >> major concern about being able to build a list of the gaps. Thank you.
> >>
> >> There are a few issues from my last call review that are still not
> >> addressed.
> >> I have left the classification of minor issue vs nits the same as the
> >> original review to make referring to the earlier review easier,
> >> but please consider all of these Nits. The IESG will need to decide
> >> whether to escalate them.
> >>
> >> I've trimmed away the points that were addressed.
> >>
> >> On 4/1/13 3:46 PM, Robert Sparks wrote:
> >>> ----------------------
> >>> Minor issues:
> >>>
> >>> The document currently references
> >>> draft-chown-v6ops-renumber-thinkabout several times.
> >>> That document is long expired (2006). It would be better to simply
> >>> restate what is
> >>> important from that document here and reference it only once in the
> >>> acknowlegements
> >>> rather than send the reader off to read it.
> >> This version still references that long expired draft. There was also
> >> conversation on apps-discuss
> >> about making that reference normative. IMHO, this is not the right way
> >> to treat the RFC series, and
> >> strongly encourage moving the text that you want to reference into
> >> something that will
> >> become an RFC.
> > [Bing] Maybe Brian's suggestion of putting some texts into an appendix =
is a
> good way. We'll discuss this problem when make the next time update.
> >
> >>> Should section 8 belong to some other document? It looks like
> >>> operational renumbering
> >>> advice/considerations, but doesn't seem to be exploring renumbering
> >>> gaps, except for
> >>> the very short section 8.2 which says "we need a better mechanism"
> >>> without much explanation.
> >> Afaict, this wasn't addressed at all. In particular, "we need a better
> >> mechanism" is still all that
> >> section 8.2 says.
> > [Bing] Sorry for leaving it out. Will do in next update.
> >
> >>> Section 5.1, first bullet. The list below "the impact of ambiguous M/=
O
> >>> flags" says things like
> >>> "there is no standard" and "it is unspecified". I think you are tryin=
g
> >>> to say that there is
> >>> ambiguity in what's written, not that nothing's written. This entire
> >>> list would benefit from
> >>> being recast in terms of what needs to be done (what are the gaps?).
> >> This text remains unmodified.
> > [Bing] We made revision focusing on explaining "what are the gaps", but
> the texts change was omitted, will do in next update.
> >
> >>> ----------------------
> >>> Nits/editorial comments:
> >>>
> >>> There are a few sentences ending with "etc." in the document. Please
> >>> consider deleting the
> >>> word from the list - it doesn't help each sentence make its point.
> >> There were some changes, but mostly these still exist. I'll leave
> >> pressing this point further to the RFC Editor.
> > [Bing] A professional language/editorial check would be helpful.
> >
> >>> Seciton 7.1: The first bullet does not parse. If I guess its meaning
> >>> correctly
> >>> (that it would be benificial to tell hosts that local DNS has been
> >>> updated and
> >>> they may want to make fresh queries), please be careful with the
> >>> wording. The
> >>> hosts don't know which names are likely to resolve locally.
> >> This text remained unchanged, and when coming back to the document
> for a
> >> re-review
> >> (which is somewhat like coming back to an RFC you've read before just
> >> for reference),
> >> it's even harder to understand what it's trying to say than it was whe=
n
> >> reading the document
> >> linearly.
> >>
> >> I think you are trying to say
> >> "A notification mechanism may be needed to indicate _to_ hosts that a
> >> renumbering event has _changed how local recursive DNS servers will
> >> respond_. That mechanism may also need to indicate that such a change
> >> will happen at a specific time in the future."
> > [Bing] I think it's a better description. Will update, thanks much.
> >
> >>> Section 7.1, third bullet - This isn't obviously about notification.
> >>> Why is it
> >>> in this section? What's the gap this is trying to identify?
> >> This text was unchanged.
> > [Bing] For example, if border routers enabled egress filtering based on=
 the
> SIP, then the router need to know the renumbering events on some internal
> nodes. We'll make it clear in the next version.
> >
> >>> Section 9.4 - what is it about these that make them gaps, much less
> >>> unsolvable gaps.
> >>> Is this discussion in the wrong section of the document?
> >> This is now section 10.3 and is mostly unchanged. It's still not clear
> >> why this discussion is in the "unsolvable gaps" section.
> > [Bing] We considered the two points (ID/Locator overloading in transpor=
t
> layer & address caching in app layer ) are too fundamental that might not=
 be
> proper to modify them just in terms of renumbering.
> >
> > Best regards,
> > Bing


From tjc@ecs.soton.ac.uk  Mon May 13 10:36:52 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 70C8B21F9360; Mon, 13 May 2013 10:36:52 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yqWy7cKTAL7e; Mon, 13 May 2013 10:36:51 -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 AF72221F92EC; Mon, 13 May 2013 10:36:50 -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 r4DHaeb7002327;  Mon, 13 May 2013 18:36:40 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4DHaeb7002327
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1368466601; bh=2V0DYH5kp9U5ILMW21bt8kk2W2I=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=l9vEDQOez3IKjkJVvVEJcc75j6MNN0PxoUceAzPSypWWNGuG9SG21fh0mVrQrr9Tx 45hGi5VDDMWGDoB1F1wE29FIdtNrn194D5OOKyCdslLUzuwRk+896BeVot5GnqYuCb PT1MY9H+EPpNHH/Iiujaw3yL+sn11Tjxsli6UuT0=
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 p4CIae0430602276Nl ret-id none; Mon, 13 May 2013 18:36:41 +0100
Received: from [192.168.1.110] (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 r4DHaVuD017767 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 May 2013 18:36:32 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D70E78D@nkgeml506-mbx.china.huawei.com>
Date: Mon, 13 May 2013 18:36:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|fe2727486afbb9ad7009bcf9319d50dbp4CIae03tjc|ecs.soton.ac.uk|3D439D9C-E9FE-427C-9E35-8EC8468202F0@ecs.soton.ac.uk>
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com> <518D0E64.6020504@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D70E78D@nkgeml506-mbx.china.huawei.com> <3D439D9C-E9FE-427C-9E35-8EC8468202F0@ecs.soton.ac.uk>
To: Liubing (Leo) <leo.liubing@huawei.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4CIae043060227600; tid=p4CIae0430602276Nl; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=6:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4DHaeb7002327
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [renum] Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
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, 13 May 2013 17:36:52 -0000

Yes, thanks all - I think we're nearly there=85

Tim

On 13 May 2013, at 02:58, Liubing (Leo) <leo.liubing@huawei.com> wrote:

> Hi, Robert
>=20
> Your careful review and comments really helped improving the document =
a lot.
> Many thanks to you.
>=20
> All the best,
> Bing
>=20
>> -----Original Message-----
>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>> Sent: Friday, May 10, 2013 11:13 PM
>> To: Liubing (Leo)
>> Cc: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org;
>> gen-art@ietf.org; ietf@ietf.org
>> Subject: Re: Gen-art telechat review: =
draft-ietf-6renum-gap-analysis-06.txt
>> (updated for -07)
>>=20
>> Thanks Bing -
>>=20
>> The updates make the document better, and I appreciate the resolution =
of
>> referencing Tim's expired draft.
>> I think you've addressed all my comments except for the one on =
section
>> 5.1, but that's ok.
>>=20
>> For completeness and ease on the ADs, here's an updated summary:
>>=20
>> Document: draft-ietf-6renum-gap-analysis-05.txt
>> Reviewer: Robert Sparks
>> Review Date: May 10, 2013
>> IETF LC End Date: April 10, 2013
>> IESG Telechat date: May 16, 2013
>>=20
>> Summary: Ready
>>=20
>>=20
>>=20
>> On 5/2/13 6:02 AM, Liubing (Leo) wrote:
>>> Hi, Robert
>>>=20
>>> Thanks a lot for your continuous careful review.
>>> Please see replies inline.
>>>=20
>>>> -----Original Message-----
>>>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>>>> Sent: Wednesday, May 01, 2013 12:33 AM
>>>> To: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org
>>>> Cc: gen-art@ietf.org; ietf@ietf.org
>>>> Subject: Gen-art telechat review: =
draft-ietf-6renum-gap-analysis-06.txt
>>>>=20
>>>> I am the assigned Gen-ART reviewer for this draft. For background =
on
>>>> Gen-ART, please see the FAQ at
>>>> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>=20
>>>> Please wait for direction from your document shepherd
>>>> or AD before posting a new version of the draft.
>>>>=20
>>>> Document: draft-ietf-6renum-gap-analysis-05.txt
>>>> Reviewer: Robert Sparks
>>>> Review Date: April 1, 2013
>>>> IETF LC End Date: April 10, 2013
>>>> IESG Telechat date: May 16, 2013
>>>>=20
>>>> Summary: Ready with nits (that border on minor issues)
>>>>=20
>>>> This update improved the readability significantly, and addressed =
my
>>>> major concern about being able to build a list of the gaps. Thank =
you.
>>>>=20
>>>> There are a few issues from my last call review that are still not
>>>> addressed.
>>>> I have left the classification of minor issue vs nits the same as =
the
>>>> original review to make referring to the earlier review easier,
>>>> but please consider all of these Nits. The IESG will need to decide
>>>> whether to escalate them.
>>>>=20
>>>> I've trimmed away the points that were addressed.
>>>>=20
>>>> On 4/1/13 3:46 PM, Robert Sparks wrote:
>>>>> ----------------------
>>>>> Minor issues:
>>>>>=20
>>>>> The document currently references
>>>>> draft-chown-v6ops-renumber-thinkabout several times.
>>>>> That document is long expired (2006). It would be better to simply
>>>>> restate what is
>>>>> important from that document here and reference it only once in =
the
>>>>> acknowlegements
>>>>> rather than send the reader off to read it.
>>>> This version still references that long expired draft. There was =
also
>>>> conversation on apps-discuss
>>>> about making that reference normative. IMHO, this is not the right =
way
>>>> to treat the RFC series, and
>>>> strongly encourage moving the text that you want to reference into
>>>> something that will
>>>> become an RFC.
>>> [Bing] Maybe Brian's suggestion of putting some texts into an =
appendix is a
>> good way. We'll discuss this problem when make the next time update.
>>>=20
>>>>> Should section 8 belong to some other document? It looks like
>>>>> operational renumbering
>>>>> advice/considerations, but doesn't seem to be exploring =
renumbering
>>>>> gaps, except for
>>>>> the very short section 8.2 which says "we need a better mechanism"
>>>>> without much explanation.
>>>> Afaict, this wasn't addressed at all. In particular, "we need a =
better
>>>> mechanism" is still all that
>>>> section 8.2 says.
>>> [Bing] Sorry for leaving it out. Will do in next update.
>>>=20
>>>>> Section 5.1, first bullet. The list below "the impact of ambiguous =
M/O
>>>>> flags" says things like
>>>>> "there is no standard" and "it is unspecified". I think you are =
trying
>>>>> to say that there is
>>>>> ambiguity in what's written, not that nothing's written. This =
entire
>>>>> list would benefit from
>>>>> being recast in terms of what needs to be done (what are the =
gaps?).
>>>> This text remains unmodified.
>>> [Bing] We made revision focusing on explaining "what are the gaps", =
but
>> the texts change was omitted, will do in next update.
>>>=20
>>>>> ----------------------
>>>>> Nits/editorial comments:
>>>>>=20
>>>>> There are a few sentences ending with "etc." in the document. =
Please
>>>>> consider deleting the
>>>>> word from the list - it doesn't help each sentence make its point.
>>>> There were some changes, but mostly these still exist. I'll leave
>>>> pressing this point further to the RFC Editor.
>>> [Bing] A professional language/editorial check would be helpful.
>>>=20
>>>>> Seciton 7.1: The first bullet does not parse. If I guess its =
meaning
>>>>> correctly
>>>>> (that it would be benificial to tell hosts that local DNS has been
>>>>> updated and
>>>>> they may want to make fresh queries), please be careful with the
>>>>> wording. The
>>>>> hosts don't know which names are likely to resolve locally.
>>>> This text remained unchanged, and when coming back to the document
>> for a
>>>> re-review
>>>> (which is somewhat like coming back to an RFC you've read before =
just
>>>> for reference),
>>>> it's even harder to understand what it's trying to say than it was =
when
>>>> reading the document
>>>> linearly.
>>>>=20
>>>> I think you are trying to say
>>>> "A notification mechanism may be needed to indicate _to_ hosts that =
a
>>>> renumbering event has _changed how local recursive DNS servers will
>>>> respond_. That mechanism may also need to indicate that such a =
change
>>>> will happen at a specific time in the future."
>>> [Bing] I think it's a better description. Will update, thanks much.
>>>=20
>>>>> Section 7.1, third bullet - This isn't obviously about =
notification.
>>>>> Why is it
>>>>> in this section? What's the gap this is trying to identify?
>>>> This text was unchanged.
>>> [Bing] For example, if border routers enabled egress filtering based =
on the
>> SIP, then the router need to know the renumbering events on some =
internal
>> nodes. We'll make it clear in the next version.
>>>=20
>>>>> Section 9.4 - what is it about these that make them gaps, much =
less
>>>>> unsolvable gaps.
>>>>> Is this discussion in the wrong section of the document?
>>>> This is now section 10.3 and is mostly unchanged. It's still not =
clear
>>>> why this discussion is in the "unsolvable gaps" section.
>>> [Bing] We considered the two points (ID/Locator overloading in =
transport
>> layer & address caching in app layer ) are too fundamental that might =
not be
>> proper to modify them just in terms of renumbering.
>>>=20
>>> Best regards,
>>> Bing
>=20


From jari.arkko@piuha.net  Wed May 15 13:50:40 2013
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 9AD6521F9023; Wed, 15 May 2013 13:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level: 
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVnkfnmUzrXS; Wed, 15 May 2013 13:50:35 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CE24721F85D6; Wed, 15 May 2013 13:50:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1FC422CC64; Wed, 15 May 2013 23:50:34 +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 9iLkHBt4eIYQ; Wed, 15 May 2013 23:50:33 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 853992CC56; Wed, 15 May 2013 23:50:33 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <EMEW3|fe2727486afbb9ad7009bcf9319d50dbp4CIae03tjc|ecs.soton.ac.uk|3D439D9C-E9FE-427C-9E35-8EC8468202F0@ecs.soton.ac.uk>
Date: Wed, 15 May 2013 23:50:33 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A63EFE6-0CF1-4DF4-989F-95216E30110D@piuha.net>
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com> <518D0E64.6020504@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D70E78D@nkgeml506-mbx.china.huawei.com> <3D439D9C-E9FE-427C-9E35-8EC8468202F0@ecs.soton.ac.uk> <EMEW3|fe2727486afbb9ad7009bcf9319d50dbp4CIae03tjc|ecs.soton.ac.uk|3D439D9C-E9FE-427C-9E35-8EC8468202F0@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>, Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1503)
Cc: gen-art@ietf.org, renum@ietf.org, draft-ietf-6renum-gap-analysis@tools.ietf.org
Subject: Re: [renum] [Gen-art] Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
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 May 2013 20:50:40 -0000

Robert:

Thanks again for your careful review, and for the authors and you for =
the discussion and revisions that resulted in a much improved document. =
I plan to support the document's approval in tomorrow's IESG telechat. A =
big part of my document approval decisions are the Gen-ART reviews, and =
they help me greatly.

I think the expired draft discussion that you guys had is a minor side =
issue, but I thought I'd provide my perspective on it. While a normative =
reference to discontinued work is problematic, some informative =
references are IMHO OK and in some cases even necessary. One such =
category is expressing source of ideas or text. The correct attribution =
of material and ideas is important. =46rom that point of view this =
particular reference is fine as far as I am concerned (though I am also =
fine with text in the acknowledgments section, which is what the draft =
has now).

Jari


From stig@venaas.com  Wed May 15 15:08:05 2013
Return-Path: <stig@venaas.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 46C9921F848A; Wed, 15 May 2013 15:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L2LaBY8ybORj; Wed, 15 May 2013 15:08:04 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id A36E421F8481; Wed, 15 May 2013 15:08:04 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-234.cisco.com [128.107.239.234]) by ufisa.uninett.no (Postfix) with ESMTPSA id 158438079; Thu, 16 May 2013 00:08:01 +0200 (CEST)
Message-ID: <5194073F.3030602@venaas.com>
Date: Wed, 15 May 2013 15:07:59 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com> <518D0E64.6020504@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D70E78D@nkgeml506-mbx.china.huawei.com> <3D439D9C-E9FE-427C-9E35-8EC8468202F0@ecs.soton.ac.uk> <EMEW3|fe2727486afbb9ad7009bcf9319d50dbp4CIae03tjc|ecs.soton.ac.uk|3D439D9C-E9FE-427C-9E35-8EC8468202F0@ecs.soton.ac.uk> <6A63EFE6-0CF1-4DF4-989F-95216E30110D@piuha.net>
In-Reply-To: <6A63EFE6-0CF1-4DF4-989F-95216E30110D@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: renum@ietf.org, gen-art@ietf.org, draft-ietf-6renum-gap-analysis@tools.ietf.org, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [renum] [Gen-art] Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
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 May 2013 22:08:05 -0000

On 5/15/2013 1:50 PM, Jari Arkko wrote:
> Robert:
>
> Thanks again for your careful review, and for the authors and you for the discussion and revisions that resulted in a much improved document. I plan to support the document's approval in tomorrow's IESG telechat. A big part of my document approval decisions are the Gen-ART reviews, and they help me greatly.
>
> I think the expired draft discussion that you guys had is a minor side issue, but I thought I'd provide my perspective on it. While a normative reference to discontinued work is problematic, some informative references are IMHO OK and in some cases even necessary. One such category is expressing source of ideas or text. The correct attribution of material and ideas is important. From that point of view this particular reference is fine as far as I am concerned (though I am also fine with text in the acknowledgments section, which is what the draft has now).

As an author of both, I agree with Jari. I'm OK with the current text,
but I think we should have an informational reference since the draft
is mentioned in the text. It is pretty common to have informational
references to expired drafts (and any other document on the internet
that has a stable reference).

Stig

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

