
From rjsparks@nostrum.com  Mon Apr  1 13:59:32 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 90B2921E8053 for <renum@ietfa.amsl.com>; Mon,  1 Apr 2013 13:59:32 -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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 G38+k3k6KiOL for <renum@ietfa.amsl.com>; Mon,  1 Apr 2013 13:59:31 -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 A99F121E80AA for <renum@ietf.org>; Mon,  1 Apr 2013 13:59:30 -0700 (PDT)
Received: from unnumerable.tekelec.com ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r31KxSKh073801 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <renum@ietf.org>; Mon, 1 Apr 2013 15:59:29 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <5159F530.3060600@nostrum.com>
Date: Mon, 01 Apr 2013 15:59:28 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: renum@ietf.org
References: <5159F239.1060001@nostrum.com>
In-Reply-To: <5159F239.1060001@nostrum.com>
X-Forwarded-Message-Id: <5159F239.1060001@nostrum.com>
Content-Type: multipart/alternative; boundary="------------000303020001000808030002"
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Subject: [renum] Fwd: [Gen-art] 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, 01 Apr 2013 20:59:32 -0000

This is a multi-part message in MIME format.
--------------000303020001000808030002
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

(forwarding to the correct list address)


-------- Original Message --------
Subject: 	[Gen-art] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
Date: 	Mon, 01 Apr 2013 15:46:49 -0500
From: 	Robert Sparks <rjsparks@nostrum.com>
To: 	6renum@ietf.org, draft-ietf-6renum-gap-analysis@tools.ietf.org
CC: 	gen-art@ietf.org, ietf@ietf.org



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 resolve these comments along with any other Last Call comments
you may receive.

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: Not yet scheduled for a telechat

Summary: This document is not ready for publication as an Informational RFC.
          It may be on the right track, but there issues both in substance
          and form that need to be addressed.

Major issues:

The document doesn't provide what its title and abstract claim it will
provide.
For instance, the abstract claims a gap analysis is presented following
a renumbering
event procedure summary, but neither appear in the draft. There are a
few places
in the text that say "this is a gap", but usually it's not clear what
"this" means.

The stated intent is to identify missing capabilities (gaps) and the work
needed to provide them. The document should lay these out very clearly.
As the
document is currently written, it is difficult to pull out a simple list of
identified gaps. While addressing that, it would help more to provide some
sense of the relative importance of addressing each of the gaps identified.

There are several significant issues with clarity. I will point to the most
difficult in a section below.

----------------------
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.

RFC4076 seems to say very similar things to this document. Should it
have been referenced?

Section 5.3 punts discussion of static addresses off to RFC 6866. That
document was scoped
only to Enterprise Networks. The scope of this document is larger. Are
there gaps because
of that difference in scope that were missed? Would it make sense to
summarize any gaps
RFC 6866 identified that are relevant to this document here?

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.


----------------------
Text needing clarity (more than nits):

Section 4.1, second paragraph: The first sentence needs to be
simplified. Something like
"Delegation routers may need to renumber themselves with new delegated
prefixes" perhaps.
The second sentence speaks of "the router renumbering issue" as if it's
clear which particular
issue you're actually talking about. Is there a gap here? If so,
consider replacing the entire
paragraph with an explicit description of the gap.

Section 5.1, first bullet, 2nd paragraph: The third sentence (starting
"In ND protocol,")
makes no sense. The fourth sentence is also hard to parse.

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?).

Section 5.2, last paragraph. It's not clear what you are trying to say
here. Is it simply
that the natural pressures in an ISP make it more likely that an ISP
would choose to use
DNS names as part of configuration than an enterprise would? If so, can
you list what some
of those pressures are? What gap is this discussion trying to identify?

Section 6.1, first paragraph, first sentence (starting "For DNS records
update") - this sentence
does not parse. What is it trying to say, and what's the gap you are
trying to point to?

Section 6.3, 6th paragraph. "So there's a big gap for configuration
aggregation" is
unclear. Is it that configuration isn't stored in one place, or that it
can't be
found through one place, or something different?

Section 7.1 second bullet. Taking this partial quote from RFC4192
destroyed the meaning
of the sentence. The original sentence said "The suggestion applies" -
this misquote says
"reducing the delay applies". There's no benefit to quoting 4192
directly - say what you
mean and reference 4192.


----------------------
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.

Introduction: "Future efforts may be achieved in the future." doesn't
add anything
to the document. I suggest deleting the sentence.

Section 3.2: Consider deleting "basically" from "an IPAM is basically used"

Section 5.1: draft-ietf-dhc-host-gen-id is no longer new (and it
definitely will not be
new a few years after this is published as an RFC. Please remove "the
new IETF DHC WG
document" from the sentence it appears in.

Section 5.1: This sentence "Using these flags, the two separated address
configuration
modes are somehow correlated." is not clear. ("somehow" isn't going to
help the reader
in any case). Are you trying to say "This flags provide some degree of
correlation in
the use of these separate configuration protocols"? Could you rewrite
this explicitly
identifying gaps?

Section 5.1: Please delete "mainly" from "flags mainly includes"

Section 5.2 (and other places): Is it really the case that router
operators have to
resort to restarting routers in order to pick up configuration changes
these days?
RFC2072 pointed to that, and in 1997 it may have been more routine to
restart, but
for modern systems, that action is more extreme. Surely for something as
basic as
a cache-clear, restarts are vanishingly rare.

Section 5.3: Instead of "the static address issue" could you say
"discussing the
problems associated with renumbering hosts with static addresses"?

Section 6, first paragraph: It's not clear what "the entries in the
site" means.
What's a site and what are entries in this case.  I suggest "then any
configuration
or data store containing the previous number must be updated." as a
replacement, and
then say "Some examples include:" and list DNS records and ACLs.
Consider pointing
forward to the section on DNS Authority listed under "Gaps considered
unsolvable".
Note that some of those ACLS are going to be on machines under control
by another
authority, having the same problem you point to for DNS.

Section 6.1: What do you mean by "the major DNS systems". Do you mean
the major
implementations like BIND?

Section 6.2, first paragraph. This suffers from the ambiguity of the word
"records". You meant it as a verb (DNS writes something down) instead of
a noun (the DNS system contains DNS records). I suggest rewriting this
paragraph to avoid the ambiguity. "While DNS entries contain addresses" -
"Hosts are configured with" - "hosts must update these addreses"

Section 6.2 second paragraph. Please be more clear what you mean by
"DNS lifetimes". You are not trying to refer to the time-to-live of
a DNS record. Rather, you are trying to say how long a bit of configuration
obtained through DHCP should be considered relevant. If there's a gap
(a need for more protocol), please be explicit. You will proabably want
to engage the DHC working group if you are thinking about asking that
DHCP tell you how long DNS server configuration value is good for if you
are really trying to decouple it from the lease time. (Is that what
you're suggesting? If not, then what's the problem?)

Section 6.3, second bullet, second sub-bullet: What does "the entries" mean?
Please be specific. Do you mean "configured addresses or prefixes" or
something
else? Or is this intended to extend to updating things like DNS zone files?
As written, it is vague.

Section 6.3, last sentence. "It is a big gap currently." What specifically
is the big gap. Is it a lack of a standard protocol for updating
configurations
so that there won't be some many vendor-private protocols deployed?
Please consider replacing "It" with something explicit.

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.

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?

Section 7.2 - how is this section helping the document? What are the gaps?

Section 7.3 - again, how is this section helping the document acheive
its goal?
Would anyone working to close gaps do anything differently if this
section were
deleted?

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?

Section 10 - The sentence starting "In the LAN" doesn't parse. Did you mean
"may be needed to"?

Section 10, last paragraph: This sentence doesn't make sense. It would
make more
sense if you replaced "blocking access" with "protecting", but it would
be even
better to expand the discussion and explain what you mean by interruption.

_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art




--------------000303020001000808030002
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    (forwarding to the correct list address)<br>
    <div class="moz-forward-container"><br>
      <br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>[Gen-art] Gen-art review:
              draft-ietf-6renum-gap-analysis-05.txt</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Mon, 01 Apr 2013 15:46:49 -0500</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>Robert Sparks <a class="moz-txt-link-rfc2396E" href="mailto:rjsparks@nostrum.com">&lt;rjsparks@nostrum.com&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:6renum@ietf.org">6renum@ietf.org</a>,
              <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-6renum-gap-analysis@tools.ietf.org">draft-ietf-6renum-gap-analysis@tools.ietf.org</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:gen-art@ietf.org">gen-art@ietf.org</a>, <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<a class="moz-txt-link-rfc2396E" href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>.

Please resolve these comments along with any other Last Call comments
you may receive.

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: Not yet scheduled for a telechat

Summary: This document is not ready for publication as an Informational RFC.
         It may be on the right track, but there issues both in substance
         and form that need to be addressed.

Major issues:

The document doesn't provide what its title and abstract claim it will 
provide.
For instance, the abstract claims a gap analysis is presented following 
a renumbering
event procedure summary, but neither appear in the draft. There are a 
few places
in the text that say "this is a gap", but usually it's not clear what 
"this" means.

The stated intent is to identify missing capabilities (gaps) and the work
needed to provide them. The document should lay these out very clearly. 
As the
document is currently written, it is difficult to pull out a simple list of
identified gaps. While addressing that, it would help more to provide some
sense of the relative importance of addressing each of the gaps identified.

There are several significant issues with clarity. I will point to the most
difficult in a section below.

----------------------
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.

RFC4076 seems to say very similar things to this document. Should it 
have been referenced?

Section 5.3 punts discussion of static addresses off to RFC 6866. That 
document was scoped
only to Enterprise Networks. The scope of this document is larger. Are 
there gaps because
of that difference in scope that were missed? Would it make sense to 
summarize any gaps
RFC 6866 identified that are relevant to this document here?

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.


----------------------
Text needing clarity (more than nits):

Section 4.1, second paragraph: The first sentence needs to be 
simplified. Something like
"Delegation routers may need to renumber themselves with new delegated 
prefixes" perhaps.
The second sentence speaks of "the router renumbering issue" as if it's 
clear which particular
issue you're actually talking about. Is there a gap here? If so, 
consider replacing the entire
paragraph with an explicit description of the gap.

Section 5.1, first bullet, 2nd paragraph: The third sentence (starting 
"In ND protocol,")
makes no sense. The fourth sentence is also hard to parse.

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?).

Section 5.2, last paragraph. It's not clear what you are trying to say 
here. Is it simply
that the natural pressures in an ISP make it more likely that an ISP 
would choose to use
DNS names as part of configuration than an enterprise would? If so, can 
you list what some
of those pressures are? What gap is this discussion trying to identify?

Section 6.1, first paragraph, first sentence (starting "For DNS records 
update") - this sentence
does not parse. What is it trying to say, and what's the gap you are 
trying to point to?

Section 6.3, 6th paragraph. "So there's a big gap for configuration 
aggregation" is
unclear. Is it that configuration isn't stored in one place, or that it 
can't be
found through one place, or something different?

Section 7.1 second bullet. Taking this partial quote from RFC4192 
destroyed the meaning
of the sentence. The original sentence said "The suggestion applies" - 
this misquote says
"reducing the delay applies". There's no benefit to quoting 4192 
directly - say what you
mean and reference 4192.


----------------------
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.

Introduction: "Future efforts may be achieved in the future." doesn't 
add anything
to the document. I suggest deleting the sentence.

Section 3.2: Consider deleting "basically" from "an IPAM is basically used"

Section 5.1: draft-ietf-dhc-host-gen-id is no longer new (and it 
definitely will not be
new a few years after this is published as an RFC. Please remove "the 
new IETF DHC WG
document" from the sentence it appears in.

Section 5.1: This sentence "Using these flags, the two separated address 
configuration
modes are somehow correlated." is not clear. ("somehow" isn't going to 
help the reader
in any case). Are you trying to say "This flags provide some degree of 
correlation in
the use of these separate configuration protocols"? Could you rewrite 
this explicitly
identifying gaps?

Section 5.1: Please delete "mainly" from "flags mainly includes"

Section 5.2 (and other places): Is it really the case that router 
operators have to
resort to restarting routers in order to pick up configuration changes 
these days?
RFC2072 pointed to that, and in 1997 it may have been more routine to 
restart, but
for modern systems, that action is more extreme. Surely for something as 
basic as
a cache-clear, restarts are vanishingly rare.

Section 5.3: Instead of "the static address issue" could you say 
"discussing the
problems associated with renumbering hosts with static addresses"?

Section 6, first paragraph: It's not clear what "the entries in the 
site" means.
What's a site and what are entries in this case.  I suggest "then any 
configuration
or data store containing the previous number must be updated." as a 
replacement, and
then say "Some examples include:" and list DNS records and ACLs. 
Consider pointing
forward to the section on DNS Authority listed under "Gaps considered 
unsolvable".
Note that some of those ACLS are going to be on machines under control 
by another
authority, having the same problem you point to for DNS.

Section 6.1: What do you mean by "the major DNS systems". Do you mean 
the major
implementations like BIND?

Section 6.2, first paragraph. This suffers from the ambiguity of the word
"records". You meant it as a verb (DNS writes something down) instead of
a noun (the DNS system contains DNS records). I suggest rewriting this
paragraph to avoid the ambiguity. "While DNS entries contain addresses" -
"Hosts are configured with" - "hosts must update these addreses"

Section 6.2 second paragraph. Please be more clear what you mean by
"DNS lifetimes". You are not trying to refer to the time-to-live of
a DNS record. Rather, you are trying to say how long a bit of configuration
obtained through DHCP should be considered relevant. If there's a gap
(a need for more protocol), please be explicit. You will proabably want
to engage the DHC working group if you are thinking about asking that
DHCP tell you how long DNS server configuration value is good for if you
are really trying to decouple it from the lease time. (Is that what
you're suggesting? If not, then what's the problem?)

Section 6.3, second bullet, second sub-bullet: What does "the entries" mean?
Please be specific. Do you mean "configured addresses or prefixes" or 
something
else? Or is this intended to extend to updating things like DNS zone files?
As written, it is vague.

Section 6.3, last sentence. "It is a big gap currently." What specifically
is the big gap. Is it a lack of a standard protocol for updating 
configurations
so that there won't be some many vendor-private protocols deployed?
Please consider replacing "It" with something explicit.

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.

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?

Section 7.2 - how is this section helping the document? What are the gaps?

Section 7.3 - again, how is this section helping the document acheive 
its goal?
Would anyone working to close gaps do anything differently if this 
section were
deleted?

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?

Section 10 - The sentence starting "In the LAN" doesn't parse. Did you mean
"may be needed to"?

Section 10, last paragraph: This sentence doesn't make sense. It would 
make more
sense if you replaced "blocking access" with "protecting", but it would 
be even
better to expand the discussion and explain what you mean by interruption.

_______________________________________________
Gen-art mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gen-art@ietf.org">Gen-art@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/gen-art">https://www.ietf.org/mailman/listinfo/gen-art</a>
</pre>
      <br>
    </div>
    <br>
  </body>
</html>

--------------000303020001000808030002--

From leo.liubing@huawei.com  Tue Apr  2 00:46: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 A553D21F985C; Tue,  2 Apr 2013 00:46: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 J0eBt83nWuZs; Tue,  2 Apr 2013 00:46:47 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D362121F985B; Tue,  2 Apr 2013 00:46:45 -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 ARI19611; Tue, 02 Apr 2013 07:46:44 +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; Tue, 2 Apr 2013 08:46:32 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 2 Apr 2013 15:46:41 +0800
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.42]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.01.0323.007; Tue, 2 Apr 2013 15:46:34 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Robert Sparks <rjsparks@nostrum.com>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
Thread-Index: AQHOLxocMFWfMeFT5EmCEaSFUOUemZjCTHqg
Date: Tue, 2 Apr 2013 07:46:33 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com>
References: <5159F239.1060001@nostrum.com>
In-Reply-To: <5159F239.1060001@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 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: Tue, 02 Apr 2013 07:46:48 -0000

Hi, Robert

Thanks a lot for your careful and detailed review. It is very helpful to re=
fine the draft.
Please see replies inline.=20

> -----Original Message-----
> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> Sent: Tuesday, April 02, 2013 4:47 AM
> To: 6renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org
> Cc: gen-art@ietf.org; ietf@ietf.org
> Subject: Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=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: Not yet scheduled for a telechat
>=20
> Summary: This document is not ready for publication as an Informational
> RFC.
>           It may be on the right track, but there issues both in substanc=
e
>           and form that need to be addressed.
>=20
> Major issues:
>=20
> The document doesn't provide what its title and abstract claim it will
> provide.
> For instance, the abstract claims a gap analysis is presented following
> a renumbering
> event procedure summary, but neither appear in the draft.=20

[Bing] In fact the subtitles have the implication of a renumbering event pr=
ocedure summary. But it is indeed not explicit in the main texts. We'll add=
 some texts to represent it explicitly in the next version.

> There are a few places
> in the text that say "this is a gap", but usually it's not clear what
> "this" means.

[Bing] We'll make them more clear in the next version.=20
=20
> The stated intent is to identify missing capabilities (gaps) and the work
> needed to provide them. The document should lay these out very clearly.
> As the document is currently written, it is difficult to pull out a simpl=
e list of
> identified gaps.=20

[Bing] A good suggestion. We once had a summary subtitle in previous versio=
ns, but we deleted it since we thought it might be a little redundancy.=20
Now we can add it back, it could be helpful for the readers.

> While addressing that, it would help more to provide some
> sense of the relative importance of addressing each of the gaps identifie=
d.

[Bing] We used to divide the gaps into "solvable" and "unsolvable". Some im=
portant gaps might be unsolvable; while some of the solvable ones might not=
 be so important. We'll consider to reflex the two dimensions in the next v=
ersion.

> There are several significant issues with clarity. I will point to the mo=
st
> difficult in a section below.
>=20
> ----------------------
> 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.

[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.=20
draft-chown is a more comprehensive analysis, while the gap draft is focusi=
ng on gaps in enterprise renumbering. So it might not easy to abstract seve=
ral points as important from draft-chown to this draft. We actually encoura=
ge people to read it.

> RFC4076 seems to say very similar things to this document. Should it
> have been referenced?

[Bing] RFC4076 is a more specific case of stateless-DHCPv6 [RFC3736], which=
 might not be common usage in enterprise. But sure we can consider referenc=
e it.=20

> Section 5.3 punts discussion of static addresses off to RFC 6866. That
> document was scoped
> only to Enterprise Networks. The scope of this document is larger. Are
> there gaps because
> of that difference in scope that were missed? Would it make sense to
> summarize any gaps
> RFC 6866 identified that are relevant to this document here?

[Bing] This document scope is also for enterprise (it is the 6renum WG scop=
e). In fact the RFC6866 is a sub-document of this draft. We considered stat=
ic address problem is an important topic that need a separated document to =
describe. We can consider add a brief summary there.

> 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.

[Bing] The multicast and mobility in section 8 were considered as important=
 standalone topics that need to be addressed.=20
Since multicast is complex, we need more texts to describe the problem than=
 describing the gaps directly. But we can make the gaps more clear.

> ----------------------
> Text needing clarity (more than nits):

[Bing] We'll also deal with the following clarity and nits comments in the =
next version. Thanks for the careful review.

Best regards,
Bing


> Section 4.1, second paragraph: The first sentence needs to be
> simplified. Something like
> "Delegation routers may need to renumber themselves with new delegated
> prefixes" perhaps.
> The second sentence speaks of "the router renumbering issue" as if it's
> clear which particular
> issue you're actually talking about. Is there a gap here? If so,
> consider replacing the entire
> paragraph with an explicit description of the gap.
>=20
> Section 5.1, first bullet, 2nd paragraph: The third sentence (starting
> "In ND protocol,")
> makes no sense. The fourth sentence is also hard to parse.
>=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?).
>=20
> Section 5.2, last paragraph. It's not clear what you are trying to say
> here. Is it simply
> that the natural pressures in an ISP make it more likely that an ISP
> would choose to use
> DNS names as part of configuration than an enterprise would? If so, can
> you list what some
> of those pressures are? What gap is this discussion trying to identify?
>=20
> Section 6.1, first paragraph, first sentence (starting "For DNS records
> update") - this sentence
> does not parse. What is it trying to say, and what's the gap you are
> trying to point to?
>=20
> Section 6.3, 6th paragraph. "So there's a big gap for configuration
> aggregation" is
> unclear. Is it that configuration isn't stored in one place, or that it
> can't be
> found through one place, or something different?
>=20
> Section 7.1 second bullet. Taking this partial quote from RFC4192
> destroyed the meaning
> of the sentence. The original sentence said "The suggestion applies" -
> this misquote says
> "reducing the delay applies". There's no benefit to quoting 4192
> directly - say what you
> mean and reference 4192.
>=20
>=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.
>=20
> Introduction: "Future efforts may be achieved in the future." doesn't
> add anything
> to the document. I suggest deleting the sentence.
>=20
> Section 3.2: Consider deleting "basically" from "an IPAM is basically use=
d"
>=20
> Section 5.1: draft-ietf-dhc-host-gen-id is no longer new (and it
> definitely will not be
> new a few years after this is published as an RFC. Please remove "the
> new IETF DHC WG
> document" from the sentence it appears in.
>=20
> Section 5.1: This sentence "Using these flags, the two separated address
> configuration
> modes are somehow correlated." is not clear. ("somehow" isn't going to
> help the reader
> in any case). Are you trying to say "This flags provide some degree of
> correlation in
> the use of these separate configuration protocols"? Could you rewrite
> this explicitly
> identifying gaps?
>=20
> Section 5.1: Please delete "mainly" from "flags mainly includes"
>=20
> Section 5.2 (and other places): Is it really the case that router
> operators have to
> resort to restarting routers in order to pick up configuration changes
> these days?
> RFC2072 pointed to that, and in 1997 it may have been more routine to
> restart, but
> for modern systems, that action is more extreme. Surely for something as
> basic as
> a cache-clear, restarts are vanishingly rare.
>=20
> Section 5.3: Instead of "the static address issue" could you say
> "discussing the
> problems associated with renumbering hosts with static addresses"?
>=20
> Section 6, first paragraph: It's not clear what "the entries in the
> site" means.
> What's a site and what are entries in this case.  I suggest "then any
> configuration
> or data store containing the previous number must be updated." as a
> replacement, and
> then say "Some examples include:" and list DNS records and ACLs.
> Consider pointing
> forward to the section on DNS Authority listed under "Gaps considered
> unsolvable".
> Note that some of those ACLS are going to be on machines under control
> by another
> authority, having the same problem you point to for DNS.
>=20
> Section 6.1: What do you mean by "the major DNS systems". Do you mean
> the major
> implementations like BIND?
>=20
> Section 6.2, first paragraph. This suffers from the ambiguity of the word
> "records". You meant it as a verb (DNS writes something down) instead of
> a noun (the DNS system contains DNS records). I suggest rewriting this
> paragraph to avoid the ambiguity. "While DNS entries contain addresses" -
> "Hosts are configured with" - "hosts must update these addreses"
>=20
> Section 6.2 second paragraph. Please be more clear what you mean by
> "DNS lifetimes". You are not trying to refer to the time-to-live of
> a DNS record. Rather, you are trying to say how long a bit of configurati=
on
> obtained through DHCP should be considered relevant. If there's a gap
> (a need for more protocol), please be explicit. You will proabably want
> to engage the DHC working group if you are thinking about asking that
> DHCP tell you how long DNS server configuration value is good for if you
> are really trying to decouple it from the lease time. (Is that what
> you're suggesting? If not, then what's the problem?)
>=20
> Section 6.3, second bullet, second sub-bullet: What does "the entries" me=
an?
> Please be specific. Do you mean "configured addresses or prefixes" or
> something
> else? Or is this intended to extend to updating things like DNS zone file=
s?
> As written, it is vague.
>=20
> Section 6.3, last sentence. "It is a big gap currently." What specificall=
y
> is the big gap. Is it a lack of a standard protocol for updating
> configurations
> so that there won't be some many vendor-private protocols deployed?
> Please consider replacing "It" with something explicit.
>=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.
>=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?
>=20
> Section 7.2 - how is this section helping the document? What are the gaps=
?
>=20
> Section 7.3 - again, how is this section helping the document acheive
> its goal?
> Would anyone working to close gaps do anything differently if this
> section were
> deleted?
>=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?
>=20
> Section 10 - The sentence starting "In the LAN" doesn't parse. Did you me=
an
> "may be needed to"?
>=20
> Section 10, last paragraph: This sentence doesn't make sense. It would
> make more
> sense if you replaced "blocking access" with "protecting", but it would
> be even
> better to expand the discussion and explain what you mean by interruption=
.


From brian.e.carpenter@gmail.com  Tue Apr  2 02:58:44 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 D910121F97A6; Tue,  2 Apr 2013 02:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.48
X-Spam-Level: 
X-Spam-Status: No, score=-101.48 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IP_ADDR=1.119, 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 Yt7JYDKMwFsg; Tue,  2 Apr 2013 02:58:44 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E07AC21F9776; Tue,  2 Apr 2013 02:58:14 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id u12so179306wey.33 for <multiple recipients>; Tue, 02 Apr 2013 02:58:11 -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=sn/5PJyrWKgXR2Yr614/5IZ0Wx5Bb9oYiO+TYeHmQnI=; b=VEpnfDuuQD/pYpfOM3xOejxmcSNxgJmp5ZDwGKmB8/MKXKWnCsuLPJ3Wp7aZ9iKgOq b85yhPcDJtRn/36G2l8iY/gQUFMrmpl1oyTSOzMd+09kKGqBL+fCMcV2z1eKtgMP8hIa xmBmz/mUDQqn0RMV/E7QxYhaivRytXZLJcpSi0qZ6ZCOUS8aLNdC9FItXb53YM0OaEww DqjNsm0MYPBI8VERhmwmS3sgXaOXKDtOGB8Dhu86H4lFRgMZ5dZQxdFDs1MJsRijNQPx TiiFyW37jA/duxSBTgjlNH4QtfcODtQNySBqI/ICyCzQSGN+3nFy5O6sgQp0r/Ap4Wh3 Wa2A==
X-Received: by 10.194.89.169 with SMTP id bp9mr20469780wjb.57.1364896691847; Tue, 02 Apr 2013 02:58:11 -0700 (PDT)
Received: from [128.232.110.128] (c128.al.cl.cam.ac.uk. [128.232.110.128]) by mx.google.com with ESMTPS id bk1sm1494604wib.2.2013.04.02.02.58.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 02:58:11 -0700 (PDT)
Message-ID: <515AABB5.5050202@gmail.com>
Date: Tue, 02 Apr 2013 10:58:13 +0100
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: <5159F239.1060001@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com>
Content-Type: text/plain; charset=UTF-8
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>, 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: Tue, 02 Apr 2013 09:58:45 -0000

Just picking a couple of points for further comment:

On 02/04/2013 08:46, Liubing (Leo) wrote:
> Hi, Robert
...

>> -----Original Message-----
>> From: Robert Sparks [mailto:rjsparks@nostrum.com]

...
>> 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.
> 
> [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.
Of course we have to acknowledge it, but maybe we should pull some of its text
into an Appendix.

Tim Chown, any opinion?

>> RFC4076 seems to say very similar things to this document. Should it
>> have been referenced?
> 
> [Bing] RFC4076 is a more specific case of stateless-DHCPv6 [RFC3736], which might not be common usage in enterprise. But sure we can consider reference it. 

Yes, and check if it identifies any gaps that we should mention.

Bing: we should also add a reference to RFC 4085 "Embedding Globally-Routable
Internet Addresses Considered Harmful" which I missed for RFC 6866.

>> Section 5.3 punts discussion of static addresses off to RFC 6866. That
>> document was scoped
>> only to Enterprise Networks. The scope of this document is larger. 

As Bing said, the *intended* scope is enterprise networks. We should
add that in the Abstract and Introduction. Indeed, many of the points
are more general.

Thanks again Robert!

   Brian

From leo.liubing@huawei.com  Tue Apr  2 05:36:36 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 150B521F976B; Tue,  2 Apr 2013 05:36:36 -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 dQUq1fovwMPC; Tue,  2 Apr 2013 05:36:35 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 608A421F9767; Tue,  2 Apr 2013 05:36:34 -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 APZ64617; Tue, 02 Apr 2013 12:36:33 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 2 Apr 2013 13:36:01 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 2 Apr 2013 13:36:09 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.42]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.01.0323.007; Tue, 2 Apr 2013 20:36:05 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
Thread-Index: AQHOLxocMFWfMeFT5EmCEaSFUOUemZjCTHqg///gYoCAALD3MA==
Date: Tue, 2 Apr 2013 12:36:05 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED729@nkgeml506-mbx.china.huawei.com>
References: <5159F239.1060001@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com> <515AABB5.5050202@gmail.com>
In-Reply-To: <515AABB5.5050202@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: "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 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: Tue, 02 Apr 2013 12:36:36 -0000

SGksIEJyaWFuDQoNCj4gPj4gVGhlIGRvY3VtZW50IGN1cnJlbnRseSByZWZlcmVuY2VzDQo+ID4+
IGRyYWZ0LWNob3duLXY2b3BzLXJlbnVtYmVyLXRoaW5rYWJvdXQNCj4gPj4gc2V2ZXJhbCB0aW1l
cy4NCj4gPj4gVGhhdCBkb2N1bWVudCBpcyBsb25nIGV4cGlyZWQgKDIwMDYpLiBJdCB3b3VsZCBi
ZSBiZXR0ZXIgdG8gc2ltcGx5DQo+ID4+IHJlc3RhdGUgd2hhdCBpcw0KPiA+PiBpbXBvcnRhbnQg
ZnJvbSB0aGF0IGRvY3VtZW50IGhlcmUgYW5kIHJlZmVyZW5jZSBpdCBvbmx5IG9uY2UgaW4gdGhl
DQo+ID4+IGFja25vd2xlZ2VtZW50cw0KPiA+PiByYXRoZXIgdGhhbiBzZW5kIHRoZSByZWFkZXIg
b2ZmIHRvIHJlYWQgaXQuDQo+ID4NCj4gPiBbQmluZ10gZHJhZnQtY2hvd24tdjZvcHMtcmVudW1i
ZXItdGhpbmthYm91dCBpcyBhbiBpbXBvcnRhbnQgaW5wdXQgZm9yDQo+IHRoZSBnYXAgYW5hbHlz
aXMuIEFsdGhvdWdoIHRoZSBkcmFmdCBpcyBleHBpcmVkLCBtb3N0IG9mIHRoZSBjb250ZW50IGFy
ZSBzdGlsbA0KPiB2YWxpZC4NCj4gPiBkcmFmdC1jaG93biBpcyBhIG1vcmUgY29tcHJlaGVuc2l2
ZSBhbmFseXNpcywgd2hpbGUgdGhlIGdhcCBkcmFmdCBpcw0KPiBmb2N1c2luZyBvbiBnYXBzIGlu
IGVudGVycHJpc2UgcmVudW1iZXJpbmcuIFNvIGl0IG1pZ2h0IG5vdCBlYXN5IHRvIGFic3RyYWN0
DQo+IHNldmVyYWwgcG9pbnRzIGFzIGltcG9ydGFudCBmcm9tIGRyYWZ0LWNob3duIHRvIHRoaXMg
ZHJhZnQuIFdlIGFjdHVhbGx5DQo+IGVuY291cmFnZSBwZW9wbGUgdG8gcmVhZCBpdC4NCj4gDQo+
IFJvYmVydCBpcyByaWdodCwgdGhvdWdoLCBzZW5kaW5nIHBlb3BsZSB0byBhIGxvbmctZXhwaXJl
ZCBkcmFmdCBpcyBhIGJhZCBpZGVhLg0KPiBPZiBjb3Vyc2Ugd2UgaGF2ZSB0byBhY2tub3dsZWRn
ZSBpdCwgYnV0IG1heWJlIHdlIHNob3VsZCBwdWxsIHNvbWUgb2YgaXRzDQo+IHRleHQNCj4gaW50
byBhbiBBcHBlbmRpeC4NCj4gDQo+IFRpbSBDaG93biwgYW55IG9waW5pb24/DQoNCltCaW5nXSBP
aywgdGhlbiB3ZSBjYW4gaGVhciBzb21lIG9waW5pb25zIGZyb20gVGltLg0KDQo+IA0KPiA+PiBS
RkM0MDc2IHNlZW1zIHRvIHNheSB2ZXJ5IHNpbWlsYXIgdGhpbmdzIHRvIHRoaXMgZG9jdW1lbnQu
IFNob3VsZCBpdA0KPiA+PiBoYXZlIGJlZW4gcmVmZXJlbmNlZD8NCj4gPg0KPiA+IFtCaW5nXSBS
RkM0MDc2IGlzIGEgbW9yZSBzcGVjaWZpYyBjYXNlIG9mIHN0YXRlbGVzcy1ESENQdjYgW1JGQzM3
MzZdLA0KPiB3aGljaCBtaWdodCBub3QgYmUgY29tbW9uIHVzYWdlIGluIGVudGVycHJpc2UuIEJ1
dCBzdXJlIHdlIGNhbiBjb25zaWRlcg0KPiByZWZlcmVuY2UgaXQuDQo+IA0KPiBZZXMsIGFuZCBj
aGVjayBpZiBpdCBpZGVudGlmaWVzIGFueSBnYXBzIHRoYXQgd2Ugc2hvdWxkIG1lbnRpb24uDQo+
IA0KPiBCaW5nOiB3ZSBzaG91bGQgYWxzbyBhZGQgYSByZWZlcmVuY2UgdG8gUkZDIDQwODUgIkVt
YmVkZGluZw0KPiBHbG9iYWxseS1Sb3V0YWJsZQ0KPiBJbnRlcm5ldCBBZGRyZXNzZXMgQ29uc2lk
ZXJlZCBIYXJtZnVsIiB3aGljaCBJIG1pc3NlZCBmb3IgUkZDIDY4NjYuDQoNCltCaW5nXSBHb3Qg
aXQuIEknbGwgYWRkIGl0IGluIHRoZSBuZXh0IHZlcnNpb24uDQoNCj4gPj4gU2VjdGlvbiA1LjMg
cHVudHMgZGlzY3Vzc2lvbiBvZiBzdGF0aWMgYWRkcmVzc2VzIG9mZiB0byBSRkMgNjg2Ni4gVGhh
dA0KPiA+PiBkb2N1bWVudCB3YXMgc2NvcGVkDQo+ID4+IG9ubHkgdG8gRW50ZXJwcmlzZSBOZXR3
b3Jrcy4gVGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQgaXMgbGFyZ2VyLg0KPiANCj4gQXMgQmlu
ZyBzYWlkLCB0aGUgKmludGVuZGVkKiBzY29wZSBpcyBlbnRlcnByaXNlIG5ldHdvcmtzLiBXZSBz
aG91bGQNCj4gYWRkIHRoYXQgaW4gdGhlIEFic3RyYWN0IGFuZCBJbnRyb2R1Y3Rpb24uIEluZGVl
ZCwgbWFueSBvZiB0aGUgcG9pbnRzDQo+IGFyZSBtb3JlIGdlbmVyYWwuDQoNCltCaW5nXSBPSy4g
VGhhbmtzLg0KDQo+IFRoYW5rcyBhZ2FpbiBSb2JlcnQhDQo+IA0KPiAgICBCcmlhbg0K

From stig@venaas.com  Tue Apr  2 10:24:58 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 69CC021F8A0C; Tue,  2 Apr 2013 10:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, 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 Dh7uvGymbpT4; Tue,  2 Apr 2013 10:24:58 -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 C5EED21F89E2; Tue,  2 Apr 2013 10:24:57 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 61D568012; Tue,  2 Apr 2013 19:24:55 +0200 (CEST)
Message-ID: <515B140C.3060707@venaas.com>
Date: Tue, 02 Apr 2013 10:23:24 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <5159F239.1060001@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com> <515AABB5.5050202@gmail.com>
In-Reply-To: <515AABB5.5050202@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
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 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: Tue, 02 Apr 2013 17:24:58 -0000

On 4/2/2013 2:58 AM, Brian E Carpenter wrote:
> Just picking a couple of points for further comment:
>
> On 02/04/2013 08:46, Liubing (Leo) wrote:
>> Hi, Robert
> ...
>
>>> -----Original Message-----
>>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>
> ...
>>> 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.
>>
>> [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.
> Of course we have to acknowledge it, but maybe we should pull some of its text
> into an Appendix.
>
> Tim Chown, any opinion?

I still think that old draft is fairly good, and a shame to let it all
just die. But there is no chance of getting that out as an RFC I guess?

Stig

>
>>> RFC4076 seems to say very similar things to this document. Should it
>>> have been referenced?
>>
>> [Bing] RFC4076 is a more specific case of stateless-DHCPv6 [RFC3736], which might not be common usage in enterprise. But sure we can consider reference it.
>
> Yes, and check if it identifies any gaps that we should mention.
>
> Bing: we should also add a reference to RFC 4085 "Embedding Globally-Routable
> Internet Addresses Considered Harmful" which I missed for RFC 6866.
>
>>> Section 5.3 punts discussion of static addresses off to RFC 6866. That
>>> document was scoped
>>> only to Enterprise Networks. The scope of this document is larger.
>
> As Bing said, the *intended* scope is enterprise networks. We should
> add that in the Abstract and Introduction. Indeed, many of the points
> are more general.
>
> Thanks again Robert!
>
>     Brian
>


From sm@elandsys.com  Tue Apr 16 12:36:48 2013
Return-Path: <sm@elandsys.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 414E021F9742; Tue, 16 Apr 2013 12:36:48 -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=[AWL=0.000, 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 tGW04HhK5Bcn; Tue, 16 Apr 2013 12:36:47 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A1CA21F973A; Tue, 16 Apr 2013 12:36:47 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.138.179]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r3GJZRj7011253 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Apr 2013 12:35:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1366140941; bh=fOvrmS88agpU0TjUzxZppqFBXBBAWd9vbk5t+sMcmVA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=C0lrhNw1LOn+i1LJul7hUNp1FISbOw4InOyVgswgiqUPrZIgsEW34wg0K2ZbqNjiB I1Y92j0nUn/h8D+CCX7K37cZ9ov3pJekjiI8mhj3Y4DZ7rpAAvWFl9cYnjsvwxAjTl GStLZEnBPiYc3M4ztdnZjlH7A054ycI1qEsbn8s8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1366140941; i=@elandsys.com; bh=fOvrmS88agpU0TjUzxZppqFBXBBAWd9vbk5t+sMcmVA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RZLmDHQ7P6r+/pEHNSzbtWh1oP/e1mT4xG81iLB41cVaaMwieROElX7IuEvGF+EFo XbL/ROBVjoLB1WYtJvdRPkCEbrwo7PK2bF8/W6mRUz2b2Xhffx8dwICr5Z/4VO7XZZ LwfQH5RDGV7K5T/U75yLr2ewEY0xDND1DZIVJIiw=
Message-Id: <6.2.5.6.2.20130416112752.0b46f6e0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 16 Apr 2013 12:28:38 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <516D6EF1.90001@gmail.com>
References: <CA+9kkMDEc1mX77eRYMXPBKnH9X+jOXGVD7pVFArkwSwNsF+wMA@mail.gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6EEAEE@nkgeml506-mbx.china.huawei.com> <CA+9kkMA7+_m5s-iEo24H9jrGt9Osn32iMBDSSEyL7FNyeDT5+g@mail.gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6FC22B@nkgeml506-mbx.china.huawei.com> <516CF39D.7020306@gmail.com> <CAC4RtVB_BN3oYwpWBW6pGHXK_OvbP2588AnpxEU_L+RV5jE9ng@mail.gmail.com> <516D4583.7020707@gmail.com> <CA+9kkMA2FDH3DSLED33uS5R0VSxyUok96OEU9=LtODu+nYRv3A@mail.gmail.com> <516D6EF1.90001@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Tue, 16 Apr 2013 12:41:21 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, draft-ietf-6renum-gap-analysis.all@tools.ietf.org, apps-discuss@ietf.org, renum@ietf.org
Subject: Re: [renum] [apps-discuss] Review of draft-ietf-6renum-gap-analysis-05
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, 16 Apr 2013 19:36:48 -0000

Hi Brian,
At 08:32 16-04-2013, Brian E Carpenter wrote:
>Of course, as an author I will follow whatever the WG chairs and AD
>decide is the consensus - it's just that doing a second downref Last Call
>for this document seems a bit OTT.

Agreed.

I agree with the comments posted by Ted Hardie at 
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg09296.html

RFC 2874 is a normative reference which is only mentioned in Section 
9.2.  The status of that RFC is Historic.

RFC 2894 is a normative reference.  It is referenced in Section 3.1 
(relevant protocols and mechanisms).  It is mentioned that the 
protocol is not widely used.  Should I read that RFC before reading 
draft-ietf-6renum-gap-analysis-05?

RFC 3971 is a normative reference in 
draft-ietf-6renum-gap-analysis-05.  It is only referenced in the 
Security Considerations section.

RFC 3956 is listed both as an informative and a normative reference.

Section 1 mentions that:

   "This document does further analysis and identifies the valuable and
    solvable issues, digs out of some undiscovered gaps, and gives some
    solution suggestions."

Should I read RFC 5887, I-D.chown-v6ops-renumber-thinkabout and RFC 
4192 before reading draft-ietf-6renum-gap-analysis-05?

Regards,
S. Moonesamy  


From internet-drafts@ietf.org  Fri Apr 26 01:50:28 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 5CE0921F9841; Fri, 26 Apr 2013 01:50:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.476
X-Spam-Level: 
X-Spam-Status: No, score=-102.476 tagged_above=-999 required=5 tests=[AWL=0.124, 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 DB1gXl5aVga7; Fri, 26 Apr 2013 01:50:27 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2825C21F983E; Fri, 26 Apr 2013 01:50:27 -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.p4
Message-ID: <20130426085027.14512.79756.idtracker@ietfa.amsl.com>
Date: Fri, 26 Apr 2013 01:50:27 -0700
Cc: renum@ietf.org
Subject: [renum] I-D Action: 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: Fri, 26 Apr 2013 08:50:28 -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-06.txt
	Pages           : 24
	Date            : 2013-04-26

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-06

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


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


From leo.liubing@huawei.com  Fri Apr 26 02:07:27 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 B0A8021F9862 for <renum@ietfa.amsl.com>; Fri, 26 Apr 2013 02:07:27 -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 SJlVqf889TCj for <renum@ietfa.amsl.com>; Fri, 26 Apr 2013 02:07:27 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2FC3B21F9865 for <renum@ietf.org>; Fri, 26 Apr 2013 02:07:26 -0700 (PDT)
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 ASF02916; Fri, 26 Apr 2013 09:07:25 +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; Fri, 26 Apr 2013 10:06:50 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 26 Apr 2013 10:07:23 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.13]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.01.0323.007; Fri, 26 Apr 2013 17:07:19 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "renum@ietf.org" <renum@ietf.org>
Thread-Topic: Gap-analysis update-//RE: [renum] I-D Action: draft-ietf-6renum-gap-analysis-06.txt
Thread-Index: AQHOQlscTEV2/01yvECeOaYSHcbckJjoMc5w
Date: Fri, 26 Apr 2013 09:07:18 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6FE9D0@nkgeml506-mbx.china.huawei.com>
References: <20130426085027.14512.79756.idtracker@ietfa.amsl.com>
In-Reply-To: <20130426085027.14512.79756.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
Cc: "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, "6renum-chairs@tools.ietf.org" <6renum-chairs@tools.ietf.org>
Subject: [renum] Gap-analysis update-//RE: I-D Action: 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: Fri, 26 Apr 2013 09:07:27 -0000

Hi, Dear All

We've revised the draft according to the IETF last call.

As suggested in the comment, we added a gap summary as section 9.=20
Another main issue raised during IETF LC was the unclear description in som=
e places. So the authors checked through the whole document, and made not a=
 few scattered revisions.=20
But there's no substantial technical revision, it's mostly about rewording =
to explain the gaps more clearly.

Next step the draft would be going to the IESG. If anyone think there's pro=
blem, please let us know.=20
Many thanks.

Best regards,
The authors

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of internet-drafts@ietf.org
> Sent: Friday, April 26, 2013 4:50 PM
> To: i-d-announce@ietf.org
> Cc: renum@ietf.org
> Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-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 Site Renumbering Gap Analysis
> 	Author(s)       : Bing Liu
>                           Sheng Jiang
>                           Brian Carpenter
>                           Stig Venaas
>                           Wesley George
> 	Filename        : draft-ietf-6renum-gap-analysis-06.txt
> 	Pages           : 24
> 	Date            : 2013-04-26
>=20
> 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.
>=20
>=20
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-06
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-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 johnsonhammond1@hushmail.com  Sat Apr 27 10:26:37 2013
Return-Path: <johnsonhammond1@hushmail.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 D01CF21F9820 for <renum@ietfa.amsl.com>; Sat, 27 Apr 2013 10:26:37 -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 bDOKruMEWerW for <renum@ietfa.amsl.com>; Sat, 27 Apr 2013 10:26:37 -0700 (PDT)
Received: from smtp2.hushmail.com (smtp2a.hushmail.com [65.39.178.237]) by ietfa.amsl.com (Postfix) with ESMTP id A1A1F21F96CD for <renum@ietf.org>; Sat, 27 Apr 2013 10:26:27 -0700 (PDT)
Received: from smtp2.hushmail.com (smtp2a.hushmail.com [65.39.178.237]) by smtp2.hushmail.com (Postfix) with SMTP id 40AEBE7C5F for <renum@ietf.org>; Sat, 27 Apr 2013 17:26:27 +0000 (UTC)
Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80]) by smtp2.hushmail.com (Postfix) with ESMTP for <renum@ietf.org>; Sat, 27 Apr 2013 17:26:27 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99) id 047FDE6736; Sat, 27 Apr 2013 17:26:26 +0000 (UTC)
MIME-Version: 1.0
Date: Sat, 27 Apr 2013 13:26:26 -0400
To: renum@ietf.org
From: johnsonhammond1@hushmail.com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20130427172627.047FDE6736@smtp.hushmail.com>
Subject: [renum] Biggest Fake Conference in Computer Science
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Apr 2013 18:32:55 -0000

Biggest Fake Conference in Computer Science


We are researchers from different parts of the world and conducted a study on  
the world’s biggest bogus computer science conference WORLDCOMP 
( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia 
from University of Georgia, USA.


We submitted a fake paper to WORLDCOMP 2011 and again (the same paper 
with a modified title) to WORLDCOMP 2012. This paper had numerous 
fundamental mistakes. Sample statements from that paper include: 

(1). Binary logic is fuzzy logic and vice versa
(2). Pascal developed fuzzy logic
(3). Object oriented languages do not exhibit any polymorphism or inheritance
(4). TCP and IP are synonyms and are part of OSI model 
(5). Distributed systems deal with only one computer
(6). Laptop is an example for a super computer
(7). Operating system is an example for computer hardware


Also, our paper did not express any conceptual meaning.  However, it 
was accepted both the times without any modifications (and without 
any reviews) and we were invited to submit the final paper and a 
payment of $500+ fee to present the paper. We decided to use the 
fee for better purposes than making Prof. Hamid Arabnia (Chairman 
of WORLDCOMP) rich. After that, we received few reminders from 
WORLDCOMP to pay the fee but we never responded. 


We MUST say that you should look at the above website if you have any thoughts 
to submit a paper to WORLDCOMP.  DBLP and other indexing agencies have stopped 
indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See 
http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the 
conferences of WORLDCOMP and notice that there is no listing after 2010. See Section 2 of
http://sites.google.com/site/dumpconf for comments from well-known researchers 
about WORLDCOMP. 


The status of your WORLDCOMP papers can be changed from scientific
to other (i.e., junk or non-technical) at any time. Better not to have a paper than 
having it in WORLDCOMP and spoil the resume and peace of mind forever!


Our study revealed that WORLDCOMP is a money making business, 
using University of Georgia mask, for Prof. Hamid Arabnia. He is throwing 
out a small chunk of that money (around 20 dollars per paper published 
in WORLDCOMP’s proceedings) to his puppet (Mr. Ashu Solo or A.M.G. Solo) 
who publicizes WORLDCOMP and also defends it at various forums, using 
fake/anonymous names. The puppet uses fake names and defames other conferences
to divert traffic to WORLDCOMP. He also makes anonymous phone calls and tries to 
threaten the critiques of WORLDCOMP (See Item 7 of Section 5 of above website). 
That is, the puppet does all his best to get a maximum number of papers published 
at WORLDCOMP to get more money into his (and Prof. Hamid Arabnia’s) pockets. 


Monte Carlo Resort (the venue of WORLDCOMP for more than 10 years, until 2012) has 
refused to provide the venue for WORLDCOMP’13 because of the fears of their image 
being tarnished due to WORLDCOMP’s fraudulent activities. That is why WORLDCOMP’13 
is taking place at a different resort. WORLDCOMP will not be held after 2013. 


The draft paper submission deadline is over but still there are no committee 
members, no reviewers, and there is no conference Chairman. The only contact 
details available on WORLDCOMP’s website is just an email address! 

Let us make a direct request to Prof. Hamid arabnia: publish all reviews for 
all the papers (after blocking identifiable details) since 2000 conference. Reveal 
the names and affiliations of all the reviewers (for each year) and how many 
papers each reviewer had reviewed on average. We also request him to look at 
the Open Challenge (Section 6) at https://sites.google.com/site/moneycomp1 


Sorry for posting to multiple lists. Spreading the word is the only way to stop 
this bogus conference. Please forward this message to other mailing lists and people. 


We are shocked with Prof. Hamid Arabnia and his puppet’s activities 
http://worldcomp-fake-bogus.blogspot.com   Search Google using the 
keyword worldcomp fake for additional links.


From brian.e.carpenter@gmail.com  Sat Apr 27 12:38:49 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 D484621F8EA5 for <renum@ietfa.amsl.com>; Sat, 27 Apr 2013 12:38:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level: 
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[AWL=-0.100, 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 wegIKFp2rR2y for <renum@ietfa.amsl.com>; Sat, 27 Apr 2013 12:38:49 -0700 (PDT)
Received: from mail-da0-x22f.google.com (mail-da0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 79B7A21F843F for <renum@ietf.org>; Sat, 27 Apr 2013 12:38:49 -0700 (PDT)
Received: by mail-da0-f47.google.com with SMTP id p1so2374272dad.6 for <renum@ietf.org>; Sat, 27 Apr 2013 12:38:49 -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:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9oxYUzXADEgqmRiGh6FbbYq/A/pTOxQXgKgXHaOYRaQ=; b=fcYIJI5hh2oFLsS93eStdHVoiwja8SZDqjRXbjSk94txTW5glHfl2cZm68pKChV3ER 0e6RoYkeY2CT9a2jgEQIW+oE6k/EQlIoGNsHEeJQ3Z1X2V2vdTUBflMFTD2Ie6HYxZaJ 4XHWL5kvlkVJjDpApBEzbXzvPjUWowxXqtuG0p0ee6kk9VCCYOZHgdztZXgqZW9SCh54 sQQtqb/RubjQkVFMEJtTQFK49i5yPy4AyM7mWg7fkdaCWomwCgWyN/QIbJmG4t7HI9ex 4WUCEhvSx/1BZZYgiZ/M+QF6moObkpyXNzi07s9ZhQOdNz1zoagF6amSCaNKvMz+ado7 XJYQ==
X-Received: by 10.68.102.66 with SMTP id fm2mr6726933pbb.168.1367091529248; Sat, 27 Apr 2013 12:38:49 -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 wi6sm16972164pbc.22.2013.04.27.12.38.46 for <renum@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 27 Apr 2013 12:38:47 -0700 (PDT)
Message-ID: <517C293F.9000104@gmail.com>
Date: Sun, 28 Apr 2013 07:38:39 +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: renum@ietf.org
References: <20130427172627.047FDE6736@smtp.hushmail.com>
In-Reply-To: <20130427172627.047FDE6736@smtp.hushmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [renum] Biggest Fake Conference in Computer Science
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Apr 2013 19:38:49 -0000

Sorry about this off-topic posting. I have removed the person from
the list. (It was a bit interesting, but totally irrelevant.)

Regards
   Brian Carpenter (list admin)

From rjsparks@nostrum.com  Tue Apr 30 08:34:35 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 655E221F9900; Tue, 30 Apr 2013 08:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.996
X-Spam-Level: 
X-Spam-Status: No, score=-101.996 tagged_above=-999 required=5 tests=[AWL=0.604, 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 vzeiUHvTRxKw; Tue, 30 Apr 2013 08:34:35 -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 BDA9721F98B9; Tue, 30 Apr 2013 08:34:34 -0700 (PDT)
Received: from unnumerable.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3UFXWuF036166 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Tue, 30 Apr 2013 10:33:33 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <517FE44C.7000609@nostrum.com>
Date: Tue, 30 Apr 2013 10:33:32 -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: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <5159F239.1060001@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com> <515AABB5.5050202@gmail.com>
In-Reply-To: <515AABB5.5050202@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, "renum@ietf.org" <renum@ietf.org>
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: Tue, 30 Apr 2013 15:34:35 -0000

On 4/2/13 4:58 AM, Brian E Carpenter wrote:
> Just picking a couple of points for further comment:
>
> On 02/04/2013 08:46, Liubing (Leo) wrote:
>> Hi, Robert
> ...
>
>>> -----Original Message-----
>>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> ...
>>> 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.
>> [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.
> Of course we have to acknowledge it, but maybe we should pull some of its text
> into an Appendix.
>
> Tim Chown, any opinion?
The most recent version (and the one slated for the next telechat) still 
has this long-expired draft referenced.

RjS


From joelja@bogus.com  Tue Apr 30 08:43:28 2013
Return-Path: <joelja@bogus.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 A38B521F9AF1 for <renum@ietfa.amsl.com>; Tue, 30 Apr 2013 08:43:28 -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 VrTlOk85YLq1 for <renum@ietfa.amsl.com>; Tue, 30 Apr 2013 08:43:28 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 4C91E21F9AF0 for <renum@ietf.org>; Tue, 30 Apr 2013 08:43:28 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r3UFhIpf077060 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 30 Apr 2013 15:43:18 GMT (envelope-from joelja@bogus.com)
Message-ID: <517FE691.2070707@bogus.com>
Date: Tue, 30 Apr 2013 08:43:13 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <5159F239.1060001@nostrum.com>	<8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com>	<515AABB5.5050202@gmail.com> <517FE44C.7000609@nostrum.com>
In-Reply-To: <517FE44C.7000609@nostrum.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 30 Apr 2013 15:43:19 +0000 (UTC)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, "renum@ietf.org" <renum@ietf.org>
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: Tue, 30 Apr 2013 15:43:28 -0000

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:
>>
>> On 02/04/2013 08:46, Liubing (Leo) wrote:
>>> Hi, Robert
>> ...
>>
>>>> -----Original Message-----
>>>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>> ...
>>>> 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.
>>> [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.
>>
>> Tim Chown, any opinion?
> The most recent version (and the one slated for the next telechat) 
> still has this long-expired draft referenced.
>
> RjS
>


From rjsparks@nostrum.com  Tue Apr 30 09:32:50 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 9F74321F9BA3; Tue, 30 Apr 2013 09:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.198
X-Spam-Level: 
X-Spam-Status: No, score=-102.198 tagged_above=-999 required=5 tests=[AWL=0.403, 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 6hD3nUno+zXG; Tue, 30 Apr 2013 09:32:50 -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 BC5FE21F9ADF; Tue, 30 Apr 2013 09:32:49 -0700 (PDT)
Received: from unnumerable.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3UGWnxl042939 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Tue, 30 Apr 2013 11:32:49 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <517FF231.3080700@nostrum.com>
Date: Tue, 30 Apr 2013 11:32:49 -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: "renum@ietf.org" <renum@ietf.org>, draft-ietf-6renum-gap-analysis@tools.ietf.org
References: <5159F239.1060001@nostrum.com>
In-Reply-To: <5159F239.1060001@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [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: Tue, 30 Apr 2013 16:32:50 -0000

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.
>
>
> 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.

>
> 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.
>
> ----------------------
> 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.
>
>
> 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."

>
> 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.
>
> 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.

