
From rjsparks@nostrum.com  Mon Apr  1 13:47:03 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03DFE21F8BBD; Mon,  1 Apr 2013 13:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KoB5gfQCQLQV; Mon,  1 Apr 2013 13:47:02 -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 DC81821F8738; Mon,  1 Apr 2013 13:47:01 -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 r31KkoSQ072419 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Mon, 1 Apr 2013 15:47:01 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <5159F239.1060001@nostrum.com>
Date: Mon, 01 Apr 2013 15:46:49 -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: 6renum@ietf.org, draft-ietf-6renum-gap-analysis@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2013 20:47:03 -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 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.


From Francis.Dupont@fdupont.fr  Tue Apr  2 00:24:28 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4902F21F987F for <gen-art@ietfa.amsl.com>; Tue,  2 Apr 2013 00:24:28 -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 2V7Fla85LL9w for <gen-art@ietfa.amsl.com>; Tue,  2 Apr 2013 00:24:27 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 8DBD721F987E for <gen-art@ietf.org>; Tue,  2 Apr 2013 00:24:27 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r327N5ll001487; Tue, 2 Apr 2013 09:23:05 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201304020723.r327N5ll001487@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Jari Arkko <jari.arkko@piuha.net>
In-reply-to: Your message of Wed, 27 Mar 2013 21:56:06 +0200. <59C82A99-AE80-427F-BCBA-F1A37A8B2981@piuha.net> 
Date: Tue, 02 Apr 2013 09:23:05 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: gen-art@ietf.org, Ben Laurie <benl@google.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Gen-art] [therightkey] review of draft-laurie-pki-sunlight-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2013 07:24:28 -0000

 In your previous mail you wrote:

>  I just wanted to check if you Francis feel that the issues have been
>  adequately addressed. FWIW, I read the document with the respect to the
>  major issues raised in your review at least, and thought that the -09
>  was clear enough for me.

=> oops, it seems I forgot to update the gen-art wiki... I agree there was
nothing still needed to be addressed in the PKI sunlight I-D.

Thanks

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Tue Apr  2 00:53:58 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97ADE21F9838 for <gen-art@ietfa.amsl.com>; Tue,  2 Apr 2013 00:53:58 -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 2IbE25fMzr29 for <gen-art@ietfa.amsl.com>; Tue,  2 Apr 2013 00:53:58 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 3993321F981D for <gen-art@ietf.org>; Tue,  2 Apr 2013 00:53:54 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r327rrXa003215; Tue, 2 Apr 2013 09:53:53 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201304020753.r327rrXa003215@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Tue, 02 Apr 2013 09:53:53 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-roll-terminology.all@tools.ietf.org
Subject: [Gen-art] draft-ietf-roll-terminology-12.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2013 07:53:58 -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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-roll-terminology-12.txt
Reviewer: Francis Dupont
Review Date: 20130323
IETF LC End Date: 20130330
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues:
 There are some missing forward definitions for some abbrevs, i.e., the first
time an abbrev is used it should be explained too (*).
(*) "too" because it is explained (i.e., put in its long form) in its entry
which can be after the first use.

Nits/editorial comments:
 - Abstract page 1: e.g. -> e.g.,

 - ToC page 2 and 5 page 7: Acknowledgements -> Acknowledgments

 - 1 page 2: please introduce the HVAC abbrev (the Abstract should be considered
  as to be independent)

 - 2 page 3: commisioning -> commissioning

 - 2 pages 4 and other: i.e. -> i.e., and e.g. -> e.g.,
  (including at the end of line)

 - 2 page 4: K -> k (or if you prefer Kelvin -> kilo in units :-)

 - 2 page 5 (LLN): refrigeration.. -> refrigeration. or refrigeration...

 - 2 page 5 (PER): I suggest: error- even -> error - even

 - 2 page 5 (P2MP): an example of a missing forward definition for RPL,
  i.e.: RPL -> Routing Protocol for Low-Power and Lossy Networks (RPL)

 - 2 page 6 (RPL): arbitratry -> arbitrary

Regards

Francis.Dupont@fdupont.fr

PS: a terminology with a lot of cross references can be hard to read (so to
write). I had a very bad experience with an ISO OSI one in the past so
the only thing IMHO should be required is to be readable in one pass in
the beginning to end order (vs. hopping order), so my comments about
abbrev definitions.

From leo.liubing@huawei.com  Tue Apr  2 00:46:48 2013
Return-Path: <leo.liubing@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@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
X-Mailman-Approved-At: Tue, 02 Apr 2013 02:13:27 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-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: gen-art@ietfa.amsl.com
Delivered-To: gen-art@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>
Subject: Re: [Gen-art] [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-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: gen-art@ietfa.amsl.com
Delivered-To: gen-art@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>
Subject: Re: [Gen-art] [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-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 stbryant@cisco.com  Tue Apr  2 06:10:15 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8B621F8E6C; Tue,  2 Apr 2013 06:10:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 ve1zmxJqhLC5; Tue,  2 Apr 2013 06:10:14 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6DECB21F8DCF; Tue,  2 Apr 2013 06:10:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8390; q=dns/txt; s=iport; t=1364908213; x=1366117813; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=ucMRQTIov8h8Imb+zvKxGOz9WBKT2GGs97RW6f7sYfQ=; b=QYhI0xnL/UnQrykKVyv9r9vOImhEjXj1j3JRmG+PdCaGdQ48Zq9zSbeB r5nsLSiK8B0OXJgiKAgpXB/o7Ecxi6aY8s/PdelwfygvKq3jFb6JlewA+ zuBLNadESOYtaGPL5y45xhrKAh55+WwClluynYLOHycHFbYl8A4bEvVVk Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFANTXWlGQ/khR/2dsb2JhbABDgzuIfrZFgQMWdIIfAQEBBGcSEAsOBgQJJQ8CRgYBDAEHAQEQiAAMsTOQEI8ZEQeDQAOWa5ELgww
X-IronPort-AV: E=Sophos;i="4.87,393,1363132800"; d="scan'208,217";a="81688324"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 02 Apr 2013 13:10:11 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r32DA93Z015621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Apr 2013 13:10:10 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r32DA8j9011028; Tue, 2 Apr 2013 14:10:08 +0100 (BST)
Message-ID: <515AD8B1.20503@cisco.com>
Date: Tue, 02 Apr 2013 14:10:09 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Richard Barnes <rbarnes@bbn.com>, Richard Barnes <rlb@ipv.sx>
References: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com>
In-Reply-To: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com>
Content-Type: multipart/alternative; boundary="------------060801070601050309000207"
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-tp-ethernet-addressing@tools.ietf.org, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2013 13:10:15 -0000

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

Resending due to Richards change of address.

Stewart

On 11/02/2013 23:45, Richard Barnes wrote:
> I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, pleaseseehttp://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>
> Please wait for direction from your document shepherd or AD before posting a new version of the draft.
>
> Document: draft-ietf-mpls-tp-ethernet-addressing-05
> Reviewer: Richard Barnes
> Review Date: 2013-02-11
> IETF LC End Date: 2013-02-18
> IESG Telechat date: TBD
>
> Summary:  Ready, with a couple of minor questions / clarifications.
>
> Comment:
>
> The document is mostly very clearly written.  (Thanks!)  It would have helped me understand if it could have been clarified up front that the mechanism in this document is intended for "pure Ethernet" MPLS-TP (without assumptions about layer 3+).  The current introduction says as much, but in a negative way, in terms of ARP or ND not being available.
>
> I have some minor unease about the distinction that this document makes between point-to-point and multipoint links.  The document correctly notes that a point-to-point link might become multipoint without either end being aware.  I would have thought this would argue for using GAP in all cases, but instead the document carries on with addressing the point-to-point case separately..
>
Richard

It is always difficult when writing a simple draft dealing with a small
component of a larger technology to know how much tutorial to include,
but I believe the point about operation in the absence IP would be well 
known
to anyone implementing this. In particular we assume that anyone
implementing the draft would have read the required references called
up in the first paragraph of the Introduction:


" The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of protocol
functions that meet the requirements [RFC5654] for the application of
MPLS to the construction and operation of packet-switched transport
networks. The MPLS-TP data plane consists of those MPLS-TP functions
concerned with the encapsulation and forwarding of MPLS-TP packets
and is described in [RFC5960]."

RFC5654 says:

"   36  It MUST be possible to operate and configure the MPLS-TP data
        plane without any IP forwarding capability in the MPLS-TP data
        plane.  That is, the data plane only operates on the MPLS label."
Thus I think that the text is complete as it stands and requires no
further clarification for anyone that needs to consider the technology
it describes.


With regard to your second point, the issue that we are have, is that
there are a number of deployment scenarios where the operator knows
that the link is Pt-Pt, and there is a reluctance by that community to
use anything other than NMS configuration. That has lead them
to use Ethernet broadcast addressing which allows the crafts to
change h/w without the need for reconfiguration by the NMS.
Against that background moving them onto the use of a Ethernet m/c
address is a step forward. To require using the GAP to that
community would illustrate that the IETF is out of touch with
their needs and methods of network operation.

Hopefully this additional background, which I believe is well
known to the MPLS-TP community to which this draft is directed,
satisfies your concern on the latter point.

- Stewart



-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Resending due to Richards change of
      address.<br>
      <br>
      Stewart<br>
      <br>
      On 11/02/2013 23:45, Richard Barnes wrote:<br>
    </div>
    <blockquote cite="mid:BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com"
      type="cite">
      <pre wrap="">I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, pleaseseehttp://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please wait for direction from your document shepherd or AD before posting a new version of the draft.

Document: draft-ietf-mpls-tp-ethernet-addressing-05
Reviewer: Richard Barnes
Review Date: 2013-02-11
IETF LC End Date: 2013-02-18
IESG Telechat date: TBD

Summary:  Ready, with a couple of minor questions / clarifications.

Comment:

The document is mostly very clearly written.  (Thanks!)  It would have helped me understand if it could have been clarified up front that the mechanism in this document is intended for "pure Ethernet" MPLS-TP (without assumptions about layer 3+).  The current introduction says as much, but in a negative way, in terms of ARP or ND not being available.

I have some minor unease about the distinction that this document makes between point-to-point and multipoint links.  The document correctly notes that a point-to-point link might become multipoint without either end being aware.  I would have thought this would argue for using GAP in all cases, but instead the document carries on with addressing the point-to-point case separately..

</pre>
    </blockquote>
    Richard<br>
    <br>
    It is always difficult when writing a simple draft dealing with a
    small<br>
    component of a larger technology to know how much tutorial to
    include,<br>
    but I believe the point about operation in the absence IP would be
    well known<br>
    to anyone implementing this. In particular we assume that anyone<br>
    implementing the draft would have read the required references
    called<br>
    up in the first paragraph of the Introduction:<br>
    <br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    " The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of
    protocol <br>
    functions that meet the requirements [RFC5654] for the application
    of <br>
    MPLS to the construction and operation of packet-switched transport
    <br>
    networks. The MPLS-TP data plane consists of those MPLS-TP functions
    <br>
    concerned with the encapsulation and forwarding of MPLS-TP packets <br>
    and is described in [RFC5960]."<br>
    <pre>RFC5654 says:

<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">"   36  It MUST be possible to operate and configure the MPLS-TP data
       plane without any IP forwarding capability in the MPLS-TP data
       plane.  That is, the data plane only operates on the MPLS label."
Thus I think that the text is complete as it stands and requires no 
further clarification for anyone that needs to consider the technology
it describes.


With regard to your second point, the issue that we are have, is that
there are a number of deployment scenarios where the operator knows
that the link is Pt-Pt, and there is a reluctance by that community to
use anything other than NMS configuration. That has lead them
to use Ethernet broadcast addressing which allows the crafts to 
change h/w without the need for reconfiguration by the NMS. 
Against that background moving them onto the use of a Ethernet m/c 
address is a step forward. To require using the GAP to that 
community would illustrate that the IETF is out of touch with 
their needs and methods of network operation.

Hopefully this additional background, which I believe is well
known to the MPLS-TP community to which this draft is directed,
satisfies your concern on the latter point.

- Stewart
</pre>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------060801070601050309000207--

From Johannes.Merkle@secunet.com  Tue Apr  2 06:22:25 2013
Return-Path: <Johannes.Merkle@secunet.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 807A121F8F05 for <gen-art@ietfa.amsl.com>; Tue,  2 Apr 2013 06:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fj86P2c-pxVV for <gen-art@ietfa.amsl.com>; Tue,  2 Apr 2013 06:22:22 -0700 (PDT)
Received: from a.mx.secunet.com (a.mx.secunet.com [195.81.216.161]) by ietfa.amsl.com (Postfix) with ESMTP id 80F0C21F8EE5 for <gen-art@ietf.org>; Tue,  2 Apr 2013 06:22:21 -0700 (PDT)
Received: from localhost (alg1 [127.0.0.1]) by a.mx.secunet.com (Postfix) with ESMTP id AED851A0083; Tue,  2 Apr 2013 15:22:20 +0200 (CEST)
X-Virus-Scanned: by secunet
Received: from a.mx.secunet.com ([127.0.0.1]) by localhost (a.mx.secunet.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id TnF8gYbFBLTh; Tue,  2 Apr 2013 15:22:18 +0200 (CEST)
Received: from mail-srv1.secumail.de (unknown [10.53.40.200]) by a.mx.secunet.com (Postfix) with ESMTP id D185F1A0081; Tue,  2 Apr 2013 15:22:18 +0200 (CEST)
Received: from [10.208.1.73] ([10.208.1.73]) by mail-srv1.secumail.de with Microsoft SMTPSVC(6.0.3790.4675); Tue, 2 Apr 2013 15:22:18 +0200
Message-ID: <515ADB89.7090801@secunet.com>
Date: Tue, 02 Apr 2013 15:22:17 +0200
From: Johannes Merkle <johannes.merkle@secunet.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
References: <039401ce2952$8bbc17a0$a33446e0$@gmail.com>
In-Reply-To: <039401ce2952$8bbc17a0$a33446e0$@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/mixed; boundary="------------010702060809000604090105"
X-OriginalArrivalTime: 02 Apr 2013 13:22:18.0821 (UTC) FILETIME=[19BC6750:01CE2FA5]
X-Mailman-Approved-At: Tue, 02 Apr 2013 06:25:40 -0700
Cc: gen-art@ietf.org, Dan Harkins <dharkins@arubanetworks.com>, draft-merkle-ikev2-ke-brainpool.all@tools.ietf.org
Subject: Re: [Gen-art] GenART LC review of draft-merkle-ikev2-ke-brainpool-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2013 13:22:25 -0000

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

Hi,

> 1.       In table 1 the Transform ID are specified as TBD1 to TBD4. I noticed that IANA have already assigned values
> 27-30. So they should be specified. If not it will be good to ask the RFC editor before publication to update the table.
> I saw that you only asked IANA to allocate values.

I'll do so in the next version if it is not done by the RFC editor.


> 
> 2.       In the IANA section I did not understand to which table you are referring to “For the new entries in the table
> of the Transform Type 4 repository, a reference to Section 2.3 of [IKE_DH_Req] shall be included in the column named
> "Recipient Tests” indicating the required checks for the other peer's Diffie-Hellman public keys.”
> 
This refers to the Table Transform Type 4 - Diffie-Hellman Group Transform IDs, see
http://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xml#ikev2-parameters-8

[IKE_DH_Req] requests from IANA to add a new column (named "Recipient Tests") to that Table. We request IANA to add in
that new column a a reference to Section 2.3 of [IKE_DH_Req].

This request has been correctly understood by IANA, see email below.

Best regards,
Johannes

--------------010702060809000604090105
Content-Type: message/rfc822;
 name="Nachricht als Anhang"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="Nachricht als Anhang"

X-Mozilla-Keys: 
Received: from a.mx.secunet.com ([195.81.216.161]) by mail-srv1.secumail.de with Microsoft SMTPSVC(6.0.3790.4675);
	 Tue, 26 Mar 2013 16:24:53 +0100
Received: from localhost (alg1 [127.0.0.1])
	by a.mx.secunet.com (Postfix) with ESMTP id C7C211A008A
	for <johannes.merkle@secunet.com>; Tue, 26 Mar 2013 16:24:53 +0100 (CET)
X-Virus-Scanned: by secunet
X-Spam-Flag: NO
X-Spam-Score: -0.889
X-Spam-Level: 
X-Spam-Status: No, score=-0.889 tagged_above=-999 required=3.3
	tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, T_RP_MATCHES_RCVD=-0.01]
	autolearn=no
Received: from a.mx.secunet.com ([127.0.0.1])
	by localhost (a.mx.secunet.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id aBDiVuN_7PDN for <johannes.merkle@secunet.com>;
	Tue, 26 Mar 2013 16:24:50 +0100 (CET)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30])
	by a.mx.secunet.com (Postfix) with ESMTP id BCAA81A0087
	for <johannes.merkle@secunet.com>; Tue, 26 Mar 2013 16:24:50 +0100 (CET)
Received: from smtp01.icann.org ([192.0.33.81]:34945 helo=smtp1.lax.icann.org)
	by grenache.tools.ietf.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.80)
	(envelope-from <iana-shared@icann.org>)
	id 1UKVjz-0001OI-8F
	for draft-merkle-ikev2-ke-brainpool@tools.ietf.org; Tue, 26 Mar 2013 16:24:48 +0100
Received: from request1.lax.icann.org (request1.lax.icann.org [10.32.11.221])
	by smtp1.lax.icann.org (8.13.8/8.13.8) with ESMTP id r2QFOYg4013765;
	Tue, 26 Mar 2013 15:24:34 GMT
Received: by request1.lax.icann.org (Postfix, from userid 48)
	id 03C225606AA; Tue, 26 Mar 2013 15:24:33 +0000 (UTC)
RT-Owner: pearl.liang
From: "Pearl Liang via RT" <drafts-lastcall@iana.org>
Reply-To: drafts-lastcall@iana.org
In-Reply-To: <20130227000623.10646.58571.idtracker@ietfa.amsl.com>
References: <RT-Ticket-662036@icann.org>
 <20130227000623.10646.58571.idtracker@ietfa.amsl.com>
Message-ID: <rt-4.0.8-9188-1364311473-1775.662036-7-0@icann.org>
Precedence: bulk
X-RT-Loop-Prevention: IANA
RT-Ticket: IANA #662036
Managed-BY: RT 4.0.8 (http://www.bestpractical.com/rt/)
RT-Originator: pearl.liang@icann.org
CC: iesg@ietf.org, turners@ieca.com,
        draft-merkle-ikev2-ke-brainpool@tools.ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Date: Tue, 26 Mar 2013 15:24:33 +0000
X-SA-Exim-Connect-IP: 192.0.33.81
X-SA-Exim-Rcpt-To: draft-merkle-ikev2-ke-brainpool@tools.ietf.org
X-SA-Exim-Mail-From: iana-shared@icann.org
Subject: [IANA #662036] Last Call: <draft-merkle-ikev2-ke-brainpool-03.txt> (Using the ECC Brainpool Curves for IKEv2 Key Exchange) to Informational RFC
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on grenache.tools.ietf.org)
Resent-To: johannes.merkle@secunet.com, manfred.lochter@bsi.bund.de
List-ID: <draft-merkle-ikev2-ke-brainpool@tools.ietf.org>
Resent-Message-Id: <20130326152450.BCAA81A0087@a.mx.secunet.com>
Resent-Date: Tue, 26 Mar 2013 16:24:50 +0100 (CET)
Resent-From: draft-alias-bounces@tools.ietf.org
Return-Path: draft-alias-bounces@tools.ietf.org
X-OriginalArrivalTime: 26 Mar 2013 15:24:53.0739 (UTC) FILETIME=[10B793B0:01CE2A36]

(BEGIN IANA LAST CALL COMMENTS)

IESG/Authors/WG Chairs:

IANA has reviewed draft-merkle-ikev2-ke-brainpool-03.  Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon as possible.

We understand that there is a single action required to be completed 
upon approval of this document.  

We understand that the following four new Transform IDs have been 
added to the "Transform Type 4 - Diffie-Hellman Group Transform IDs" 
subregistry upon the completion of ticket 666056:

URL: www.iana.org/assignments/ikev2-parameters

Note (from the designed expert done earlier):

Note, that this draft also requires that the actions from the
draft-ietf-ipsecme-dh-checks is also done.  The
draft-ietf-ipsecme-dh-checks adds the Recipient Tests column to
"Transform Type 4 - Diffie-Hellman Group Transform IDs" registry, and
this draft-merkle-ikev2-ke-brainpool also fills that column.

IANA understands that these are the only actions requested by this 
document.

Thanks,

Pearl Liang
ICANN/IANA

(END IANA LAST CALL COMMENTS)


On Tue Feb 26 16:06:45 2013, noreply@ietf.org wrote:
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Using the ECC Brainpool Curves for IKEv2 Key Exchange'
>   <draft-merkle-ikev2-ke-brainpool-03.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-03-26. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document specifies the use of ECC Brainpool elliptic curve
>    groups for key exchange in the Internet Key Exchange version 2
>    (IKEv2) protocol.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-merkle-ikev2-ke-brainpool/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-merkle-ikev2-ke-brainpool/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 





--------------010702060809000604090105--

From rlb@ipv.sx  Tue Apr  2 07:28:32 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 349F121F8917 for <gen-art@ietfa.amsl.com>; Tue,  2 Apr 2013 07:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.703
X-Spam-Level: 
X-Spam-Status: No, score=-0.703 tagged_above=-999 required=5 tests=[AWL=-0.278, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 oVCpo-XPNf7q for <gen-art@ietfa.amsl.com>; Tue,  2 Apr 2013 07:28:31 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 1BDDC21F8842 for <gen-art@ietf.org>; Tue,  2 Apr 2013 07:28:31 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id wd20so404973obb.23 for <gen-art@ietf.org>; Tue, 02 Apr 2013 07:28:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=Py5BtG+/OD8W6ctWwYFaI1ZL16k20NpCtwq1QJ1i52c=; b=EzAzmtF+tzJ/3d3P6L/VrZzUVDm7CKdSha2Nr/QsbH1V9+Ud+smahRYmy9y91cS6FW Q74SrgwWuWiBmGr9NOVlVINWnFiFqGsK6f1pzuXKqJLfF4lsJo8Xz68b9nor2EEi0K72 Hd9CD4oFqApgFO/OdzGiOwukIyriSDTwMVKXFoMs3VUI07K7Wegpc42GcUzH6g1lOTA6 LVTEqQrfKJBHmCKZ8S+67AWDjzNEq8U6fPmbkiiSDaFOUkpKdOFmShhTcHdIqq5ooHe1 2FpNHxV2V5ktXNgYvqEYEt3FlH1aGs7cDs12Gww9zVbfiDiG5FdOzuXM/sIP9tP0AS8J vnnA==
MIME-Version: 1.0
X-Received: by 10.60.30.131 with SMTP id s3mr5744629oeh.106.1364912910401; Tue, 02 Apr 2013 07:28:30 -0700 (PDT)
Received: by 10.60.160.201 with HTTP; Tue, 2 Apr 2013 07:28:30 -0700 (PDT)
X-Originating-IP: [192.1.51.16]
In-Reply-To: <515AD8B1.20503@cisco.com>
References: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com> <515AD8B1.20503@cisco.com>
Date: Tue, 2 Apr 2013 10:28:30 -0400
Message-ID: <CAL02cgTExcoC+fMYVs0KT==yx1vZgaK5Tc8Dij3vhiR9Os3YkQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: stbryant@cisco.com
Content-Type: multipart/alternative; boundary=e89a8ff1c0362c94ca04d9618d64
X-Gm-Message-State: ALoCoQl725Hu7ukWV196kToYnQ8USPVMp9HLHg2l+ZyHcFmKn2prxqSbX4afmMnvFKrbWfq5ym7J
Cc: Richard Barnes <rbarnes@bbn.com>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-tp-ethernet-addressing@tools.ietf.org, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2013 14:28:32 -0000

--e89a8ff1c0362c94ca04d9618d64
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks for following up, and for the re-send.  Just to be clear, I do not
mean these as blocking points.

On the former point, I might just suggest a minor edit to the introduction:
OLD: "This document specifies the options for determination and selection
of next-hop Ethernet MAC addressing under these circumstances."
NEW: "This document specifies the options for determination and selection
of next-hop Ethernet MAC addressing when MPLS-TP is used in a "pure
Ethernet" manner, without any IP forwarding capability."

On the latter point, I can understand the desire to make the simple case
simple, and the text at the end of Section 2 sends a clear warning. It does
seems like GAP would also allow autoconfiguration without further NMS
interaction.  (Unless the NMS is configuring per-Ethernet-address policies,
e.g., "forward packets with this label to 00:11:22:33:44:55". Is that the
case?)




On Tue, Apr 2, 2013 at 9:10 AM, Stewart Bryant <stbryant@cisco.com> wrote:

>  Resending due to Richards change of address.
>
> Stewart
>
>
> On 11/02/2013 23:45, Richard Barnes wrote:
>
> I have been selected as the General Area Review Team (Gen-ART) reviewer f=
or this draft (for background on Gen-ART, pleaseseehttp://www.alvestrand.no=
/ietf/gen/art/gen-art-FAQ.html).
>
> Please wait for direction from your document shepherd or AD before postin=
g a new version of the draft.
>
> Document: draft-ietf-mpls-tp-ethernet-
> addressing-05
> Reviewer: Richard Barnes
> Review Date: 2013-02-11
> IETF LC End Date: 2013-02-18
> IESG Telechat date: TBD
>
> Summary:  Ready, with a couple of minor questions / clarifications.
>
> Comment:
>
> The document is mostly very clearly written.  (Thanks!)  It would have he=
lped me understand if it could have been clarified up front that the mechan=
ism in this document is intended for "pure Ethernet" MPLS-TP (without assum=
ptions about layer 3+).  The current introduction says as much, but in a ne=
gative way, in terms of ARP or ND not being available.
>
> I have some minor unease about the distinction that this document makes b=
etween point-to-point and multipoint links.  The document correctly notes t=
hat a point-to-point link might become multipoint without either end being =
aware.  I would have thought this would argue for using GAP in all cases, b=
ut instead the document carries on with addressing the point-to-point case =
separately..
>
>
>  Richard
>
> It is always difficult when writing a simple draft dealing with a small
> component of a larger technology to know how much tutorial to include,
> but I believe the point about operation in the absence IP would be well
> known
> to anyone implementing this. In particular we assume that anyone
> implementing the draft would have read the required references called
> up in the first paragraph of the Introduction:
>
>
> " The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of protocol
> functions that meet the requirements [RFC5654] for the application of
> MPLS to the construction and operation of packet-switched transport
> networks. The MPLS-TP data plane consists of those MPLS-TP functions
> concerned with the encapsulation and forwarding of MPLS-TP packets
> and is described in [RFC5960]."
>
> RFC5654 says:
>
> "   36  It MUST be possible to operate and configure the MPLS-TP data
>        plane without any IP forwarding capability in the MPLS-TP data
>        plane.  That is, the data plane only operates on the MPLS label."
> Thus I think that the text is complete as it stands and requires no
> further clarification for anyone that needs to consider the technology
> it describes.
>
>
> With regard to your second point, the issue that we are have, is that
> there are a number of deployment scenarios where the operator knows
> that the link is Pt-Pt, and there is a reluctance by that community to
> use anything other than NMS configuration. That has lead them
> to use Ethernet broadcast addressing which allows the crafts to
> change h/w without the need for reconfiguration by the NMS.
> Against that background moving them onto the use of a Ethernet m/c
> address is a step forward. To require using the GAP to that
> community would illustrate that the IETF is out of touch with
> their needs and methods of network operation.
>
> Hopefully this additional background, which I believe is well
> known to the MPLS-TP community to which this draft is directed,
> satisfies your concern on the latter point.
>
> - Stewart
>
>
>
> --
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>

--e89a8ff1c0362c94ca04d9618d64
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks for following up, and for the re-send. =A0Just to be clear, I do not=
 mean these as blocking points.<div><br></div><div>On the former point, I m=
ight just suggest a minor edit to the introduction:</div><div>OLD: &quot;Th=
is document specifies the options for determination and selection of next-h=
op Ethernet MAC addressing under these circumstances.&quot;</div>
<div>NEW: &quot;This document specifies the options for determination and s=
election of next-hop Ethernet MAC addressing when MPLS-TP is used in a &quo=
t;pure Ethernet&quot; manner, without any IP forwarding capability.&quot;</=
div>
<div><br></div><div>On the latter point, I can understand the desire to mak=
e the simple case simple, and the text at the end of Section 2 sends a clea=
r warning. It does seems like GAP would also allow autoconfiguration withou=
t further NMS interaction. =A0(Unless the NMS is configuring per-Ethernet-a=
ddress policies, e.g., &quot;forward packets with this label to 00:11:22:33=
:44:55&quot;. Is that the case?) =A0</div>
<div><br></div><div><br><br><br><div class=3D"gmail_quote">On Tue, Apr 2, 2=
013 at 9:10 AM, Stewart Bryant <span dir=3D"ltr">&lt;<a href=3D"mailto:stbr=
yant@cisco.com" target=3D"_blank">stbryant@cisco.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div>Resending due to Richards change of
      address.<br>
      <br>
      Stewart<div class=3D"im"><br>
      <br>
      On 11/02/2013 23:45, Richard Barnes wrote:<br>
    </div></div>
    <blockquote type=3D"cite">
      <pre><div><div class=3D"h5">I have been selected as the General Area =
Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, p=
leaseseehttp://<a href=3D"http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ=
.html" target=3D"_blank">www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html</a=
>).

Please wait for direction from your document shepherd or AD before posting =
a new version of the draft.

Document: draft-ietf-mpls-tp-ethernet-</div></div>addressing-05
Reviewer: Richard Barnes
Review Date: 2013-02-11
IETF LC End Date: 2013-02-18
IESG Telechat date: TBD

Summary:  Ready, with a couple of minor questions / clarifications.

Comment:

The document is mostly very clearly written.  (Thanks!)  It would have help=
ed me understand if it could have been clarified up front that the mechanis=
m in this document is intended for &quot;pure Ethernet&quot; MPLS-TP (witho=
ut assumptions about layer 3+).  The current introduction says as much, but=
 in a negative way, in terms of ARP or ND not being available.

I have some minor unease about the distinction that this document makes bet=
ween point-to-point and multipoint links.  The document correctly notes tha=
t a point-to-point link might become multipoint without either end being aw=
are.  I would have thought this would argue for using GAP in all cases, but=
 instead the document carries on with addressing the point-to-point case se=
parately..

</pre>
    </blockquote><div><div class=3D"h5">
    Richard<br>
    <br>
    It is always difficult when writing a simple draft dealing with a
    small<br>
    component of a larger technology to know how much tutorial to
    include,<br>
    but I believe the point about operation in the absence IP would be
    well known<br>
    to anyone implementing this. In particular we assume that anyone<br>
    implementing the draft would have read the required references
    called<br>
    up in the first paragraph of the Introduction:<br>
    <br>
    <br>
   =20
    &quot; The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of
    protocol <br>
    functions that meet the requirements [RFC5654] for the application
    of <br>
    MPLS to the construction and operation of packet-switched transport
    <br>
    networks. The MPLS-TP data plane consists of those MPLS-TP functions
    <br>
    concerned with the encapsulation and forwarding of MPLS-TP packets <br>
    and is described in [RFC5960].&quot;<br>
    <pre>RFC5654 says:

&quot;   36  It MUST be possible to operate and configure the MPLS-TP data
       plane without any IP forwarding capability in the MPLS-TP data
       plane.  That is, the data plane only operates on the MPLS label.&quo=
t;
Thus I think that the text is complete as it stands and requires no=20
further clarification for anyone that needs to consider the technology
it describes.


With regard to your second point, the issue that we are have, is that
there are a number of deployment scenarios where the operator knows
that the link is Pt-Pt, and there is a reluctance by that community to
use anything other than NMS configuration. That has lead them
to use Ethernet broadcast addressing which allows the crafts to=20
change h/w without the need for reconfiguration by the NMS.=20
Against that background moving them onto the use of a Ethernet m/c=20
address is a step forward. To require using the GAP to that=20
community would illustrate that the IETF is out of touch with=20
their needs and methods of network operation.

Hopefully this additional background, which I believe is well
known to the MPLS-TP community to which this draft is directed,
satisfies your concern on the latter point.

- Stewart
</pre>
    <br>
    <br>
    </div></div><span class=3D"HOEnZb"><font color=3D"#888888"><pre cols=3D=
"72">--=20
For corporate legal information go to:

<a href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/index.ht=
ml" target=3D"_blank">http://www.cisco.com/web/about/doing_business/legal/c=
ri/index.html</a>

</pre>
  </font></span></div>

</blockquote></div><br></div>

--e89a8ff1c0362c94ca04d9618d64--

From prakashvn@hcl.com  Tue Apr  2 09:53:18 2013
Return-Path: <prakashvn@hcl.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9CEE21F8712; Tue,  2 Apr 2013 09:53:18 -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 EJDxhXgM4rhG; Tue,  2 Apr 2013 09:53:17 -0700 (PDT)
Received: from GWS07.hcl.com (gws07.hcl.com [192.8.186.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9926B21F870F; Tue,  2 Apr 2013 09:53:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,394,1363113000"; d="scan'208";a="10111419"
Received: from unknown (HELO CHN-CORP-HT01.CORP.HCL.IN) ([10.249.2.33]) by GWS07.hcl.com with ESMTP/TLS/AES128-SHA; 02 Apr 2013 22:21:37 +0530
Received: from CHN-HCLT-HT03.HCLT.CORP.HCL.IN (10.108.45.35) by CHN-CORP-HT01.CORP.HCL.IN (10.249.2.33) with Microsoft SMTP Server (TLS) id 14.2.318.1; Tue, 2 Apr 2013 22:23:13 +0530
Received: from CHN-HCLT-EVS16.HCLT.CORP.HCL.IN ([10.108.45.98]) by CHN-HCLT-HT03.HCLT.CORP.HCL.IN ([::1]) with mapi; Tue, 2 Apr 2013 22:23:13 +0530
From: "Prakash Venkatesen, ERS-HCLTech" <prakashvn@hcl.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Tue, 2 Apr 2013 22:23:13 +0530
Thread-Topic: Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
Thread-Index: Ac38ru1wNGisP6GHRvWY2E+60/tmIwzEpz/h
Message-ID: <62DC16C614A9554F81C8E2E5C174A98838DA0C7742@CHN-HCLT-EVS16.HCLT.CORP.HCL.IN>
References: <9904FB1B0159DA42B0B887B7FA8119CA07867E@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA07867E@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 02 Apr 2013 10:22:09 -0700
Cc: "storm@ietf.org" <storm@ietf.org>, "mark_bakke@dell.com" <mark_bakke@dell.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2013 16:53:19 -0000

Hi Dan,
I have posted an updated version of the draft:
http://www.ietf.org/id/draft-ietf-storm-iscsimib-04.txt

All the review comments from Gen-ART review have been incorporated. Please =
note my comments inline, marked Prakash>.

regards
Prakash

________________________________________
From: Romascanu, Dan (Dan) [dromasca@avaya.com]
Sent: Sunday, January 27, 2013 10:35 PM
To: gen-art@ietf.org
Cc: Prakash Venkatesen, ERS-HCLTech; mark_bakke@dell.com; david.black@emc.c=
om; Martin Stiemerling; storm@ietf.org
Subject: Gen-ART Review of draft-ietf-storm-iscsimib-03.txt

(I missed one of the authors at the first send)

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at < http://wiki.tools.ietf.org/area/gen/trac/wiki/Ge=
nArtfaq>.

Please wait for direction from your document shepherd or AD before posting =
a new version of the draft.

Document: draft-ietf-storm-iscsimib-03.txt
Reviewer: Dan Romascanu
Review Date: 1/27/13
IETF LC End Date: 1/28/13
IESG Telechat date: (if known)

Summary: Almost Ready

Major issues:

1) This document will obsolete (when approved) RFC 4544, and add support fo=
r iSCSI protocol evolution according to the consolidated version of the iSC=
SI protocol (as per draft-ietf-storm-iscsi-cons) and for the updates to iSC=
SI (as per draft-ietf-storm-iscsi-sam) for ProtocolLevel. There is no indic=
ation however in for the operators when an upgrade is recommended or become=
s mandatory, and which version of the protocol is to be used during the tra=
nsition, function of the iSCSI versions of the protocol.

Prakash> As per rough consensus of STORM group, the new features are requir=
ed when implementation supports a value of the iSCSIProtocolLevel key of 2 =
or greater. The new draft has this change.

2) A number of changes where agreed by the WG, as reflected in the message =
http://www.ietf.org/mail-archive/web/storm/current/msg00652.html, according=
 to which:

> In order to move forward, I suggest that the authors make the functional =
changes [1] - [6], not make changes [A] - [F] and [I}, and use their best j=
udgment on what (if anything) to do about [G] and [H]

My understanding is that the changes [1]-[6] were implemented, and the auth=
ors applying their best judgment did not implement [G] and [H]. However, ch=
anges [1]-[6] are npt reflected in Section 5.

Prakash> Fixed this in the new draft: updated Section 5.

3) I did not perform a MIB Doctor review of the document. I notice however =
that the text Security Considerations section and the corresponding referen=
ces do not conform to the latest version of the guidelines for the Security=
 Considerations sections in MIB documents, as per https://svn.tools.ietf.or=
g/area/ops/trac/wiki/mib-security#

Prakash> Fixed this in the new draft: updated Security Considerations secti=
on.

Minor issues:

Nits/editorial comments:


::DISCLAIMER::
---------------------------------------------------------------------------=
-------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and inte=
nded for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as informa=
tion could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in trans=
mission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability =
on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the =
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, disse=
mination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written=
 consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please=
 delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses =
and other defects.

---------------------------------------------------------------------------=
-------------------------------------------------------------------------


From stig@venaas.com  Tue Apr  2 10:24:58 2013
Return-Path: <stig@venaas.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@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>, "Liubing \(Leo\)" <leo.liubing@huawei.com>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>
Subject: Re: [Gen-art] [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-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 mrex@sap.com  Wed Apr  3 01:37:38 2013
Return-Path: <mrex@sap.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58C8E21F86B2; Wed,  3 Apr 2013 01:37:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.206
X-Spam-Level: 
X-Spam-Status: No, score=-10.206 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3s0Jy3scAnX6; Wed,  3 Apr 2013 01:37:37 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 88E8521F857E; Wed,  3 Apr 2013 01:37:37 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r338bMF7017085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 3 Apr 2013 10:37:22 +0200 (MEST)
In-Reply-To: <017c01ce2cb3$7be35ff0$73aa1fd0$@ditenity.com>
To: Piyush Jain <piyush@ditenity.com>
Date: Wed, 3 Apr 2013 10:37:22 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130403083722.3DEE51A68A@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
X-Mailman-Approved-At: Wed, 03 Apr 2013 03:23:00 -0700
Cc: ambarish@gmail.com, mmyers@fastq.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, sts@aaa-sec.com, pkix@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 08:37:38 -0000

Piyush Jain wrote:
> 
> The sole reason cited for overloading the meaning of revoked status with
> non-issued was that it allows new servers to interoperate with legacy
> clients.

There is *NO* overloading of a revoked status.  The change is making use
of an existing temporary revocation status (certificateHold) **EXACTLY**
with the original semantics for a temporary revocation,
originating from X.509 08/2005 8.5.2.2 (a):

   A certificate may be placed on hold with a reason code of
   certificateHold. The certificate hold notice may include an
   optional hold instruction code to convey additional information
   to certificate users (see 8.5.2.3).

   Once a hold has been issued, it may be handled in one of three ways:

   a) it may remain on hold with no further action, causing users to reject
      transactions issued during the hold period; or,


>
>     The WG agreed that there are many better alternatives but they all
> break compatibility with older clients.

If you want to describe "an OCSP responder no longer responding 'good'
for certificate serial numbers for which no records of issuance exist"
as "breaking compatibility with older clients", then yes, this is what
we want to do.

But in reality, this is change is about fixing a security problem that
was documented as such in rfc2560 for the "good" status.


>
> In fact, a more secure and complete
> proposal by Denis was not adopted because of the same reason.

I don't understand this statement, but there can not possibly be a more
secure solution that reporting revoked for not-issued certs.


> 
> I believe that Stefan is trying to convey that requiring servers to return
> revoked in this context will make them non-compliant with 2560 and 5019 as
> opposed to breaking interoperability with legacy clients.

The proposed change primarily intends to _standardize_ how to report
revoked/certificateHold for "not-issued" certificate serial numbers,
something that has been found useful (and already been used) in dealing
with certain kinds of security breaches of CAs/RAs.


Returning revoked/certificateHold for not-issued certs is perfectly
compliant with rfc2560 and rfc5019.  Returning "unknown" is also
perfectly compliant with rfc2560 and rfc5019.  Returning an error code
response status would be just dumb for an authoritative OCSP responder.


Should rfc5019 be interpreted to suggest for authoritative OCSP responders
to returning an error code for "not-issued" certs does not make such
behaviour any less dumb.


-Martin

From dromasca@avaya.com  Wed Apr  3 04:31:08 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0702C21F8A6D; Wed,  3 Apr 2013 04:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.161
X-Spam-Level: 
X-Spam-Status: No, score=-103.161 tagged_above=-999 required=5 tests=[AWL=-0.562, 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 KOyD216aLnM7; Wed,  3 Apr 2013 04:31:07 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 695AE21F8A7E; Wed,  3 Apr 2013 04:31:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFALh+MVHGmAcF/2dsb2JhbABEgma/XoEAFnOCHwEBAQEDEig/DAQCAQgNCA0UCQcyFBEBAQQBDQUIGodxAaQnnEOObCYLB4JfYQOcXIpSgwiCJw
X-IronPort-AV: E=Sophos;i="4.84,766,1355115600";  d="scan'208";a="5335621"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 03 Apr 2013 07:31:06 -0400
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 03 Apr 2013 07:28:41 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.02.0328.009; Wed, 3 Apr 2013 07:31:04 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Prakash Venkatesen, ERS-HCLTech" <prakashvn@hcl.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
Thread-Index: Ac38ru1wNGisP6GHRvWY2E+60/tmIwzEpz/hACbySkA=
Date: Wed, 3 Apr 2013 11:31:03 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA0C06C6@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA07867E@AZ-FFEXMB04.global.avaya.com> <62DC16C614A9554F81C8E2E5C174A98838DA0C7742@CHN-HCLT-EVS16.HCLT.CORP.HCL.IN>
In-Reply-To: <62DC16C614A9554F81C8E2E5C174A98838DA0C7742@CHN-HCLT-EVS16.HCLT.CORP.HCL.IN>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "storm@ietf.org" <storm@ietf.org>, "mark_bakke@dell.com" <mark_bakke@dell.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 11:31:08 -0000

Hi Prakash,

Thank you for addressing the issues raised in the Gen-ART review. The chang=
es made on issues 2 and 3 are fine, however, one clarification is still nee=
ded regarding the first issue. See below (agreed stuff deleted).





> -----Original Message-----
> From: Prakash Venkatesen, ERS-HCLTech [mailto:prakashvn@hcl.com]
>=20
> Summary: Almost Ready
>=20
> Major issues:
>=20
> 1) This document will obsolete (when approved) RFC 4544, and add support
> for iSCSI protocol evolution according to the consolidated version of
> the iSCSI protocol (as per draft-ietf-storm-iscsi-cons) and for the
> updates to iSCSI (as per draft-ietf-storm-iscsi-sam) for ProtocolLevel.
> There is no indication however in for the operators when an upgrade is
> recommended or becomes mandatory, and which version of the protocol is
> to be used during the transition, function of the iSCSI versions of the
> protocol.
>=20
> Prakash> As per rough consensus of STORM group, the new features are
> required when implementation supports a value of the iSCSIProtocolLevel
> key of 2 or greater. The new draft has this change.
>=20

[[DR]] 'the new features are required' means that the MIB support MUST be u=
pdated accordingly when the iSCSI updates are deployed? In other words, wou=
ld an RFC 4544 - based implementation break, or it will continue to work (w=
ith functional limitations) until the updated MIB version is introduced?=20

Thanks and Regards,

Dan


From prakashvn@hcl.com  Wed Apr  3 05:16:13 2013
Return-Path: <prakashvn@hcl.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E429021F8BF8; Wed,  3 Apr 2013 05:16:13 -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 PylzjxAdmLxl; Wed,  3 Apr 2013 05:16:13 -0700 (PDT)
Received: from GWS08.hcl.com (gws08.hcl.com [192.8.186.131]) by ietfa.amsl.com (Postfix) with ESMTP id EF85521F8BC5; Wed,  3 Apr 2013 05:16:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,401,1363113000"; d="scan'208";a="10118904"
Received: from unknown (HELO CHN-CORP-HT01.CORP.HCL.IN) ([10.249.2.33]) by GWS08.hcl.com with ESMTP/TLS/AES128-SHA; 03 Apr 2013 17:48:27 +0530
Received: from CHN-HCLT-HT04.HCLT.CORP.HCL.IN (10.108.45.37) by CHN-CORP-HT01.CORP.HCL.IN (10.249.2.33) with Microsoft SMTP Server (TLS) id 14.2.318.1; Wed, 3 Apr 2013 17:46:09 +0530
Received: from CHN-HCLT-EVS16.HCLT.CORP.HCL.IN ([10.108.45.98]) by CHN-HCLT-HT04.HCLT.CORP.HCL.IN ([::1]) with mapi; Wed, 3 Apr 2013 17:46:08 +0530
From: "Prakash Venkatesen, ERS-HCLTech" <prakashvn@hcl.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Wed, 3 Apr 2013 17:46:08 +0530
Thread-Topic: Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
Thread-Index: Ac38ru1wNGisP6GHRvWY2E+60/tmIwzEpz/hACbySkAAASBrEg==
Message-ID: <62DC16C614A9554F81C8E2E5C174A98838DA0C7744@CHN-HCLT-EVS16.HCLT.CORP.HCL.IN>
References: <9904FB1B0159DA42B0B887B7FA8119CA07867E@AZ-FFEXMB04.global.avaya.com> <62DC16C614A9554F81C8E2E5C174A98838DA0C7742@CHN-HCLT-EVS16.HCLT.CORP.HCL.IN>, <9904FB1B0159DA42B0B887B7FA8119CA0C06C6@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA0C06C6@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: "storm@ietf.org" <storm@ietf.org>, "mark_bakke@dell.com" <mark_bakke@dell.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 12:16:14 -0000

Hi Dan,
An RFC 4544 based implementation should continue to work. The value of iSCS=
IProtocolLevel to be 2 or higher is required to enable use of features in i=
SCSI SCSI Feature update (iscsi-sam). The new objects are required only whe=
n the iSCSIProtocolLevel is negotiated to 2 or higher. It is defined as a C=
onditionally mandatory group. Please note the corresponding portions of the=
 MIB module below:
--
iscsiNewObjectsV2 OBJECT-GROUP
    OBJECTS {
        iscsiInstXNodeArchitecture,
        iscsiSsnTaskReporting,
        iscsiSsnProtocolLevel,
        iscsiSsnNopReceivedPDUs,
        iscsiSsnNopSentPDUs,
        iscsiIntrLastTgtFailurePort,
        iscsiTgtLastIntrFailurePort,
        iscsiPortalDescr,
        iscsiInstSsnTgtUnmappedErrors,
        iscsiTgtLogoutCxnClosed,
        iscsiTgtLogoutCxnRemoved
    }
    STATUS current
    DESCRIPTION
        "A collection of objects added in the second version of the
        iSCSI MIB."
--
    GROUP iscsiNewObjectsV2
    DESCRIPTION
        "This group is mandatory for all iSCSI implementations
        that support a value of the iSCSIProtocolLevel key of
        2 or greater."
--
When an implementation is upgraded to enable using the features of iscsi-sa=
m, it should start using the new MIB module as well. Until then, the new ob=
jects are not required.

regards
Prakash

________________________________________
From: Romascanu, Dan (Dan) [dromasca@avaya.com]
Sent: Wednesday, April 03, 2013 5:01 PM
To: Prakash Venkatesen, ERS-HCLTech; gen-art@ietf.org
Cc: mark_bakke@dell.com; david.black@emc.com; Martin Stiemerling; storm@iet=
f.org
Subject: RE: Gen-ART Review of draft-ietf-storm-iscsimib-03.txt

Hi Prakash,

Thank you for addressing the issues raised in the Gen-ART review. The chang=
es made on issues 2 and 3 are fine, however, one clarification is still nee=
ded regarding the first issue. See below (agreed stuff deleted).





> -----Original Message-----
> From: Prakash Venkatesen, ERS-HCLTech [mailto:prakashvn@hcl.com]
>
> Summary: Almost Ready
>
> Major issues:
>
> 1) This document will obsolete (when approved) RFC 4544, and add support
> for iSCSI protocol evolution according to the consolidated version of
> the iSCSI protocol (as per draft-ietf-storm-iscsi-cons) and for the
> updates to iSCSI (as per draft-ietf-storm-iscsi-sam) for ProtocolLevel.
> There is no indication however in for the operators when an upgrade is
> recommended or becomes mandatory, and which version of the protocol is
> to be used during the transition, function of the iSCSI versions of the
> protocol.
>
> Prakash> As per rough consensus of STORM group, the new features are
> required when implementation supports a value of the iSCSIProtocolLevel
> key of 2 or greater. The new draft has this change.
>

[[DR]] 'the new features are required' means that the MIB support MUST be u=
pdated accordingly when the iSCSI updates are deployed? In other words, wou=
ld an RFC 4544 - based implementation break, or it will continue to work (w=
ith functional limitations) until the updated MIB version is introduced?

Thanks and Regards,

Dan


::DISCLAIMER::
---------------------------------------------------------------------------=
-------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and inte=
nded for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as informa=
tion could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in trans=
mission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability =
on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the =
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, disse=
mination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written=
 consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please=
 delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses =
and other defects.

---------------------------------------------------------------------------=
-------------------------------------------------------------------------


From dromasca@avaya.com  Wed Apr  3 05:20:29 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5783E21F8554; Wed,  3 Apr 2013 05:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.581
X-Spam-Level: 
X-Spam-Status: No, score=-103.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 HIcSh4fY+9Xy; Wed,  3 Apr 2013 05:20:27 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id A094321F8548; Wed,  3 Apr 2013 05:20:26 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAFupNVHGmAcF/2dsb2JhbABEgma/boEEFnOCHwEBAQEDEig/DAQCAQgNBAQBAQsUCQcyFAkIAQEEAQ0FCBqHcQGhVZ0gjUsQDXMmCwcGgllhA5xkilSDCIFrBxce
X-IronPort-AV: E=Sophos;i="4.84,786,1355115600";  d="scan'208";a="4030412"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 03 Apr 2013 08:20:24 -0400
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 03 Apr 2013 08:17:59 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Wed, 3 Apr 2013 08:20:22 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Prakash Venkatesen, ERS-HCLTech" <prakashvn@hcl.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
Thread-Index: Ac38ru1wNGisP6GHRvWY2E+60/tmIwzEpz/hACbySkAAASBrEgAA673g
Date: Wed, 3 Apr 2013 12:20:22 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA0C08D2@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA07867E@AZ-FFEXMB04.global.avaya.com> <62DC16C614A9554F81C8E2E5C174A98838DA0C7742@CHN-HCLT-EVS16.HCLT.CORP.HCL.IN>, <9904FB1B0159DA42B0B887B7FA8119CA0C06C6@AZ-FFEXMB04.global.avaya.com> <62DC16C614A9554F81C8E2E5C174A98838DA0C7744@CHN-HCLT-EVS16.HCLT.CORP.HCL.IN>
In-Reply-To: <62DC16C614A9554F81C8E2E5C174A98838DA0C7744@CHN-HCLT-EVS16.HCLT.CORP.HCL.IN>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "storm@ietf.org" <storm@ietf.org>, "mark_bakke@dell.com" <mark_bakke@dell.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 12:20:29 -0000

Hi Prakash,

Thanks for this further clarification.=20

>From my perspective the document is Ready.=20

Regards,

Dan




> -----Original Message-----
> From: Prakash Venkatesen, ERS-HCLTech [mailto:prakashvn@hcl.com]
> Sent: Wednesday, April 03, 2013 3:16 PM
> To: Romascanu, Dan (Dan); gen-art@ietf.org
> Cc: mark_bakke@dell.com; david.black@emc.com; Martin Stiemerling;
> storm@ietf.org
> Subject: RE: Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
>=20
> Hi Dan,
> An RFC 4544 based implementation should continue to work. The value of
> iSCSIProtocolLevel to be 2 or higher is required to enable use of
> features in iSCSI SCSI Feature update (iscsi-sam). The new objects are
> required only when the iSCSIProtocolLevel is negotiated to 2 or higher.
> It is defined as a Conditionally mandatory group. Please note the
> corresponding portions of the MIB module below:
> --
> iscsiNewObjectsV2 OBJECT-GROUP
>     OBJECTS {
>         iscsiInstXNodeArchitecture,
>         iscsiSsnTaskReporting,
>         iscsiSsnProtocolLevel,
>         iscsiSsnNopReceivedPDUs,
>         iscsiSsnNopSentPDUs,
>         iscsiIntrLastTgtFailurePort,
>         iscsiTgtLastIntrFailurePort,
>         iscsiPortalDescr,
>         iscsiInstSsnTgtUnmappedErrors,
>         iscsiTgtLogoutCxnClosed,
>         iscsiTgtLogoutCxnRemoved
>     }
>     STATUS current
>     DESCRIPTION
>         "A collection of objects added in the second version of the
>         iSCSI MIB."
> --
>     GROUP iscsiNewObjectsV2
>     DESCRIPTION
>         "This group is mandatory for all iSCSI implementations
>         that support a value of the iSCSIProtocolLevel key of
>         2 or greater."
> --
> When an implementation is upgraded to enable using the features of
> iscsi-sam, it should start using the new MIB module as well. Until then,
> the new objects are not required.
>=20
> regards
> Prakash
>=20
> ________________________________________
> From: Romascanu, Dan (Dan) [dromasca@avaya.com]
> Sent: Wednesday, April 03, 2013 5:01 PM
> To: Prakash Venkatesen, ERS-HCLTech; gen-art@ietf.org
> Cc: mark_bakke@dell.com; david.black@emc.com; Martin Stiemerling;
> storm@ietf.org
> Subject: RE: Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
>=20
> Hi Prakash,
>=20
> Thank you for addressing the issues raised in the Gen-ART review. The
> changes made on issues 2 and 3 are fine, however, one clarification is
> still needed regarding the first issue. See below (agreed stuff
> deleted).
>=20
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: Prakash Venkatesen, ERS-HCLTech [mailto:prakashvn@hcl.com]
> >
> > Summary: Almost Ready
> >
> > Major issues:
> >
> > 1) This document will obsolete (when approved) RFC 4544, and add
> > support for iSCSI protocol evolution according to the consolidated
> > version of the iSCSI protocol (as per draft-ietf-storm-iscsi-cons) and
> > for the updates to iSCSI (as per draft-ietf-storm-iscsi-sam) for
> ProtocolLevel.
> > There is no indication however in for the operators when an upgrade is
> > recommended or becomes mandatory, and which version of the protocol is
> > to be used during the transition, function of the iSCSI versions of
> > the protocol.
> >
> > Prakash> As per rough consensus of STORM group, the new features are
> > required when implementation supports a value of the
> > iSCSIProtocolLevel key of 2 or greater. The new draft has this change.
> >
>=20
> [[DR]] 'the new features are required' means that the MIB support MUST
> be updated accordingly when the iSCSI updates are deployed? In other
> words, would an RFC 4544 - based implementation break, or it will
> continue to work (with functional limitations) until the updated MIB
> version is introduced?
>=20
> Thanks and Regards,
>=20
> Dan
>=20
>=20
> ::DISCLAIMER::
> ------------------------------------------------------------------------
> ------------------------------------------------------------------------
> ----
>=20
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only.
> E-mail transmission is not guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, arrive
> late or incomplete, or may contain viruses in transmission. The e mail
> and its contents (with or without referred errors) shall therefore not
> attach any liability on the originator or HCL or its affiliates.
> Views or opinions, if any, presented in this email are solely those of
> the author and may not necessarily reflect the views or opinions of HCL
> or its affiliates. Any form of reproduction, dissemination, copying,
> disclosure, modification, distribution and / or publication of this
> message without the prior written consent of authorized representative
> of HCL is strictly prohibited. If you have received this email in error
> please delete it and notify the sender immediately.
> Before opening any email and/or attachments, please check them for
> viruses and other defects.
>=20
> ------------------------------------------------------------------------
> ------------------------------------------------------------------------
> ----


From piyush@ditenity.com  Wed Apr  3 07:27:39 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42AAF21F8EB1 for <gen-art@ietfa.amsl.com>; Wed,  3 Apr 2013 07:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 B7jCR8jgatCg for <gen-art@ietfa.amsl.com>; Wed,  3 Apr 2013 07:27:34 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id D0B3721F8EB3 for <gen-art@ietf.org>; Wed,  3 Apr 2013 07:27:32 -0700 (PDT)
Received: by mail-gh0-f172.google.com with SMTP id r19so239850ghr.31 for <gen-art@ietf.org>; Wed, 03 Apr 2013 07:27:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language:x-gm-message-state; bh=YHxf1tY/guVoK9LREuIVlVtjEaTE9oGU5gTCunom3x4=; b=kS5U2vmJG6lFyRA5zJe+NB+CFXlz/PhdMt01klyCYrF9mruaQuU4XjlKhpvmCL61kt brq/8V62fBEVz2Rb1YorhrVNkk+RgRU1H5hGYz76q19PC+A5oZs0InNzt3dRcRMtQnw7 2tQe4rWUTUwEGFmMDT4BBctctyFUO8x+3QHRlDy3g4soonFHEUMdRMuA9XnAreiuOVUH LHZX7MUOFJYAOTg9/pnruspjOcfxhAuPoqpOCIwupuuSF7ifSLUdu+c+4X5ps2hnCFey 5tHv1W8YgeQtTmk8ZQpIsVVajYJWoO5dgARmW8hcXDnch1eq29Ap4ckQgptlScSR+iJ4 5qDQ==
X-Received: by 10.236.222.69 with SMTP id s65mr1069481yhp.59.1364999252279; Wed, 03 Apr 2013 07:27:32 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id u80sm9832978yhj.5.2013.04.03.07.27.30 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 03 Apr 2013 07:27:31 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: <mrex@sap.com>
References: <017c01ce2cb3$7be35ff0$73aa1fd0$@ditenity.com> <20130403083722.3DEE51A68A@ld9781.wdf.sap.corp>
In-Reply-To: <20130403083722.3DEE51A68A@ld9781.wdf.sap.corp>
Date: Wed, 3 Apr 2013 07:27:20 -0700
Message-ID: <003e01ce3077$5b6329f0$12297dd0$@ditenity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGP4C5YLbWgWb1CVXRipiGNWyqUf5lBI+fw
Content-Language: en-us
X-Gm-Message-State: ALoCoQk03L8/5PfrTBwNpHuzVobKlCcNKtrV0GVSD1SZeKfJ7RFbPGYLTKVLKsZnxZZcV7nHDSdD
Cc: ambarish@gmail.com, mmyers@fastq.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, sts@aaa-sec.com, pkix@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 14:27:40 -0000

> There is *NO* overloading of a revoked status.  The change is making use
of
> an existing temporary revocation status (certificateHold) **EXACTLY** with
> the original semantics for a temporary revocation, originating from X.509
> 08/2005 8.5.2.2 (a):
> 
[Piyush] Revokes status is being used to communicate non-existent
certificates. 

> 
> If you want to describe "an OCSP responder no longer responding 'good'
> for certificate serial numbers for which no records of issuance exist"
> as "breaking compatibility with older clients", then yes, this is what we
want
> to do.

[Piyush] That is not what I implied.  There were alternatives proposed to
address fraudulently-issued certificates in OCSP (none of them solved the
problem completely BTW). 
The reason cited by you along with a few others was that any other proposal
would require clients to be updated. This is what breaking backward
compatibility means.
> 
> But in reality, this is change is about fixing a security problem that was
> documented as such in rfc2560 for the "good" status.
> 
[Piyush] What security problem? I don't see any security problem documented
in RFC 2560 bis and repeated refusal to discuss how 2560bis solves any
security problems. The only vague goal stated is - "it allows responders to
return revoked for non-issued so clients do not fall back to CRL"
I also see a creative way to circumvent responder trust issue by saying that
servers indicate "non-issued" by setting the revocation date to 1970 but
clients should not interpret the response as non-issued.
> 
> > 
> >
> > I believe that Stefan is trying to convey that requiring servers to
> > return revoked in this context will make them non-compliant with 2560
> > and 5019 as opposed to breaking interoperability with legacy clients.


[Piyush] This part I agree with as I stated in my original post. Backward
compatibility is wrong choice of words. Compliance with other standards is
the right choice.
Standards are not backward compatible. Implementations of standards are.
> 
> The proposed change primarily intends to _standardize_ how to report
> revoked/certificateHold for "not-issued" certificate serial numbers,
> something that has been found useful (and already been used) in dealing
> with certain kinds of security breaches of CAs/RAs.
> 
[Piyush] May be so. But that is not the goal cited for this update. Yes a
few CA vendors may have adopted it but that no way indicates consensus among
CA vendors.
If you refer to CAB forum thread, most reputable CA vendors are reluctant to
adopt it.
> 
> Returning an error code response status would be
> just dumb for an authoritative OCSP responder.
> 
[Piyush] Really. And why is that. It actually makes a lot of sense and that
is why CAs "who are not compromised" continue to return an error code for
such responses.
The only requirement for them is to be confident of the certificates they
have issued. The only reason a CA would return a revoked for non-issued is
that it is not sure if certificates are fraudulently issued using its key.

> 
> Should rfc5019 be interpreted to suggest for authoritative OCSP responders
> to returning an error code for "not-issued" certs does not make such
> behaviour any less dumb.
> 
[Piyush] The behavior that you are calling dumb has enabled the CAs to scale
their OCSP infrastructure.
What is dumb IMO is to continue to run the CA after being compromised and
demanding that standards be updated to support such behavior.
> 
> -Martin


From mrex@sap.com  Wed Apr  3 09:05:53 2013
Return-Path: <mrex@sap.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A386E21F8D14; Wed,  3 Apr 2013 09:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.924
X-Spam-Level: 
X-Spam-Status: No, score=-9.924 tagged_above=-999 required=5 tests=[AWL=-0.275, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iK0ZM0Sm1u2z; Wed,  3 Apr 2013 09:05:52 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6C421F8BF8; Wed,  3 Apr 2013 09:05:52 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r33G5XXE029554 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 3 Apr 2013 18:05:33 +0200 (MEST)
In-Reply-To: <003e01ce3077$5b6329f0$12297dd0$@ditenity.com>
To: Piyush Jain <piyush@ditenity.com>
Date: Wed, 3 Apr 2013 18:05:32 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130403160532.EB4FD1A68A@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: ambarish@gmail.com, mmyers@fastq.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, mrex@sap.com, sts@aaa-sec.com, pkix@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 16:05:53 -0000

I have strong doubts that regurgitating the entire previous
discussion is going to help.


Piyush Jain wrote:
> > 
> > If you want to describe "an OCSP responder no longer responding 'good'
> > for certificate serial numbers for which no records of issuance exist"
> > as "breaking compatibility with older clients", then yes, this is what
> > we want to do.
> 
> [Piyush] That is not what I implied.  There were alternatives proposed to
> address fraudulently-issued certificates in OCSP (none of them solved the
> problem completely BTW). 

OCSP is *NOT* about certificates and therefore the use of the term
"fraudulently-issued" certificate does not make any sense.

OCSP is about certificate serial status.  Everything else is
inferences by RPs, some of them bold, some of them flawed.


>
> The reason cited by you along with a few others was that any other proposal
> would require clients to be updated. This is what breaking backward
> compatibility means.

If you have an installed base with with a ratio of > 1000:1 for Cli:Srv,
and the choice for a protocol feature update between "having to update
all clients and server" and "having to update only servers", then
the latter has a significant deployment advantage.


> 
> > But in reality, this is change is about fixing a security problem that was
> > documented as such in rfc2560 for the "good" status.
> 
> [Piyush] What security problem?

   The "good" state indicates a positive response to the status inquiry.
   At a minimum, this positive response indicates that the certificate
   is not revoked, but does not necessarily mean that the certificate
   was ever issued or that the time at which the response was produced
   is within the certificate's validity interval. 

This text is pretty explicit that "good" is potentially lame, equally lame
as infering "good" from the absence of a revocation on published CRLs.


>
> in RFC 2560 bis and repeated refusal to discuss how 2560bis solves any
> security problems.

rfc2560bis itself does not solve security problems.  We're in the IETF
not in the roman catholic church.

rfc2560bis describes a minimal mitigation that OCSP responder
implementations can adopt to discontinue reporting "good" for "not issued"
certs in a corherent and standardized fashion.


>
> I also see a creative way to circumvent responder trust issue by saying that
> servers indicate "non-issued" by setting the revocation date to 1970 but
> clients should not interpret the response as non-issued.

That is a lame argument.

If you look at the ASN.1 in rfc2560:

   RevokedInfo ::= SEQUENCE {
       revocationTime              GeneralizedTime,
       revocationReason    [0]     EXPLICIT CRLReason OPTIONAL }

the "revocationTime" element in RevokedInfo is a mandatory element.
Since our "synthesized" certificateHold revocation status does not
originate from a CRL, we will have to define what value to convey
in revocationTime -- and choose a value that will not interfere with
any future "traditional" status information in case a certificate
with that serial gets issued.

Defining a simple fixed value for this field that can not possibly
cause any such confusion is an obvious, simple and straightforward
engineering solution.


> > 
> > > I believe that Stefan is trying to convey that requiring servers to
> > > return revoked in this context will make them non-compliant with 2560
> > > and 5019 as opposed to breaking interoperability with legacy clients.
> 
> 
> [Piyush] This part I agree with as I stated in my original post. Backward
> compatibility is wrong choice of words. Compliance with other standards is
> the right choice.
> Standards are not backward compatible. Implementations of standards are.

The issue of backwards compatibility also applies to changes of a standard.
If you either newly require different behaviour or prohibit previously
allowed or previously required behaviour, then a standards change is
backwards-incompabible.


Some Qualified Electronic Signature (QES) consumers (including legislation)
require OCSP responders to include a certificateHash as proof-of-issuance
in an OCSP response and require OCSP clients to verify that the
certificateHash is present in a "good" OCSP response and matches the
hash of the certificate under investigation -- as a means to work
around the shortcoming (security problems) inherent in CRLs and
rfc2560 OCSP.  However, such additional requirements are backwards
incompatible and require updating of the entire installed base,
so this approach is typically embraced only where there is not
installed base yet, or when updating the installed base is not
seen as a deterrent to adoption/deployment.


> 
> > The proposed change primarily intends to _standardize_ how to report
> > revoked/certificateHold for "not-issued" certificate serial numbers,
> > something that has been found useful (and already been used) in dealing
> > with certain kinds of security breaches of CAs/RAs.
> > 
> [Piyush] May be so. But that is not the goal cited for this update. Yes a
> few CA vendors may have adopted it but that no way indicates consensus among
> CA vendors.
> If you refer to CAB forum thread, most reputable CA vendors are reluctant to
> adopt it.

What is so difficult about the concept of standardizing/documenting:
"if you want to do this (e.g in case of emergency response), this is how:"


>
> > Returning an error code response status would be
> > just dumb for an authoritative OCSP responder.
> 
> [Piyush] Really. And why is that. It actually makes a lot of sense

No, it does not make any sense at all.  An error code is unsigned and
can be easily inserted into the communication by an attacker.  Which is
why there exists the fallback to CRL checking -- except that it is
impossible to discourage an RP from trusting a non-issued cert
through CRL checking, because the whole concept of revocation through
CRLs is fundamentally flawed and is unable to convey proof-of-issuance.


>
> and that is why CAs "who are not compromised" continue to return
> an error code for such responses.

These kinds of argument are based on two very flawed premises:

 (1) the premise that there exist only two possible states for a CA:
      (a) safe and pristine
      (b) full and thorough compromise of each and everything

 (2) that a huge PKI (100k+ entities) can be nuked and
     re-personalized after a CA compromise at close to zero cost and
     within the blink of an eye

and both premises exhibit a throrough cluelessness about security,
risk management and the real world.


> 
> > Should rfc5019 be interpreted to suggest for authoritative OCSP responders
> > to returning an error code for "not-issued" certs does not make such
> > behaviour any less dumb.
> > 
> [Piyush] The behavior that you are calling dumb has enabled the CAs to scale
> their OCSP infrastructure.
> What is dumb IMO is to continue to run the CA after being compromised and
> demanding that standards be updated to support such behavior.


"scale their OCSP infrastructure"?  *cough*

The TLS multiple OCSP response stapling extension is a design that scales.

On demand CRL downloading and on demand OCSP checking scales between
poorly and hardly.  AFAIK, Verisign put rfc5019 OCSP responder
behaviour into production in early 2004, but Windows XP and Windows 2003
will be end-of-lifed in 2014, never having had revocation checking
enabled by default in their entire lifetime.  And many RPs which do have
revocation checking enabled still soft-fail on OCSP lookup erros.
Non-negligible amounts of programmatic RPs (curl/wget?) probably still
have revocation checking unconfigured or disabled today.


-Martin

From david.black@emc.com  Wed Apr  3 10:04:42 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 716C221F8F56; Wed,  3 Apr 2013 10:04:42 -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 qPdFAoY03Sjy; Wed,  3 Apr 2013 10:04:40 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6899321F8F40; Wed,  3 Apr 2013 10:04:38 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r33H4Xe3026469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Apr 2013 13:04:33 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Wed, 3 Apr 2013 13:04:14 -0400
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r33H4ALW029953; Wed, 3 Apr 2013 13:04:10 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Wed, 3 Apr 2013 13:04:09 -0400
From: "Black, David" <david.black@emc.com>
To: "Black, David" <david.black@emc.com>, "McPherson, Danny" <dmcpherson@verisign.com>, Fred Baker <fred@cisco.com>, "joel.halpern@ericsson.com" <joel.halpern@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Wed, 3 Apr 2013 13:04:08 -0400
Thread-Topic: Gen-ART review of draft-ietf-savi-threat-scope-07
Thread-Index: AcwRKxLMGPOwf18pRUizv8st+VLKC4QxHuTAAbSUPlA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293D371CF@MX15A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E055F69357F@MX14A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293AEEDC8@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293AEEDC8@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "savi@ietf.org" <savi@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, Jean-Michel Combes <jeanmichel.combes@gmail.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-savi-threat-scope-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 17:04:42 -0000

The -07 version of this draft resolves all of the issues raised by the Gen-=
ART
review of the -06 version.  Discussion of the review with the authors has
resulted in a common understanding that there is no need for additional tex=
t
on statically allowing all source addresses through all links in a set of
teamed/aggregated links - that's at best "nice to have" for this draft, but
not essential.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Monday, March 25, 2013 9:04 PM
> To: McPherson, Danny; Fred Baker; joel.halpern@ericsson.com; gen-art@ietf=
.org
> Cc: Jean-Michel Combes; Ted Lemon; savi@ietf.org; Black, David; ietf@ietf=
.org
> Subject: Gen-ART review of draft-ietf-savi-threat-scope-06
>=20
> I have been selected as the General Area Review Team (Gen-ART) reviewer
> for this draft (for background on Gen-ART, please see
> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>=20
> Please wait for direction from your document shepherd or
> AD before posting a new version of the draft.
>=20
> Document: draft-ietf-savi-threat-scope-06
> Reviewer: David L. Black
> Review Date: March 27, 2013
> IESG Telechat Date: (if known)
>=20
> Summary: This draft is on the right track, but has open issues, described=
 in
> the review.
>=20
> Looking at the original Gen-ART review of the -05 draft and checking the =
diffs
> between -05 and -06, the issues raised by that review have only been part=
ially
> addressed:
>=20
> > There is no discussion of link teaming or aggregation (e.g., via LACP);=
 this
> > may affect source address validation functionality by requiring the sam=
e
> > validation checks on all aggregated ports.  An important case to discus=
s
> > is where the aggregated host links are connected to ports on different
> > switches (e.g., in an active/passive configuration).
>=20
> This is partially addressed on 4.1.2 (new section in -06), but only in te=
rms
> of moving validation state when something like LACP reconfigures.  This h=
as a
> couple of shortcomings:
> a) the alternative of statically  allowing all source addresses through a=
ll
> 	teamed/aggregated links (decouples SAVI state from link
> teaming/aggregation
> 	state) should also be mentioned, and
> b) the new text implies that LACP is the only way to cause this situation=
 -
> it's
> 	not, so LACP should be used as an example.  VRRP is another example.
>=20
> > (1) Some of the software switch implementations are single instance swi=
tches
> > whose implementation is distributed across multiple physical servers.  =
This
> > results in concerns similar to the link aggregation discussion above.
>=20
> I don't think this has been addressed, but the notion of single-instance
> switches
> could be added to the generalization of the new text in 4.1.2.
>=20
> > (2) Live migration of virtual machines among physical servers causes
> > relocation of MAC addresses across switch ports.  A so-called "gratuito=
us
> ARP"
> > is often used to inform the network of the MAC address move; port-based
> > source address validation information needs to move in response to such
> ARPs.
> >
> > (3) MAC address relocation is also used as a failure recovery technique=
; the
> > surviving hardware element (e.g., host in a cluster) takes over the MAC
> > addresses of the failed hardware; like the previous case, a "gratuitous=
 ARP"
> > is a common means of informing the network that the MAC address has mov=
ed,
> > and source address validation information needs to move in response to =
it.
> >
> > Minor issues:
> >
> > There doesn't seem to be much discussion of dynamic network reconfigura=
tion,
> > which may change traffic egress points.  VRRP may be a useful example t=
o
> > discuss beyond the typical routing protocol updates to forwarding table=
s.
>=20
> A paragraph has been added to 5.2.3 to address all three of the above
> concerns.
> I guess that's ok, but I would have liked to see some text pointing out t=
hat a
> MAC move can be detected by the switches and used to update SAVI state ab=
out
> which port(s) a MAC is accessed through.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Friday, May 13, 2011 1:03 AM
> > To: McPherson, Danny; Fred Baker; joel.halpern@ericsson.com; gen-
> art@ietf.org
> > Cc: Black, David; Christian Vogt; Jean-Michel Combes; Jari Arkko;
> > savi@ietf.org
> > Subject: Gen-ART review of draft-ietf-savi-threat-scope-05
> >
> > 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-savi-threat-scope-05
> > Reviewer: David L. Black
> > Review Date: 12 May 2011
> > IETF LC End Date: 18 May 2011
> >
> > Summary: This draft is on the right track, but has open issues, describ=
ed in
> > the review.
> >
> > This draft discusses the threats and deployment environment for IP sour=
ce
> > address validation with particular attention to finer-grain validation =
that
> > could be used within a network to validate IP addresses closer to the
> sources
> > of network traffic than ingress to an ISP's network.
> >
> > Major issues:
> >
> > There is no discussion of link teaming or aggregation (e.g., via LACP);=
 this
> > may affect source address validation functionality by requiring the sam=
e
> > validation checks on all aggregated ports.  An important case to discus=
s
> > is where the aggregated host links are connected to ports on different
> > switches
> > (e.g., in an active/passive configuration).
> >
> > The discussion of multi-instance hosts in section 5.2.3 is incomplete
> > in several important aspects:
> >
> > (1) Some of the software switch implementations are single instance swi=
tches
> > whose implementation is distributed across multiple physical servers.  =
This
> > results in concerns similar to the link aggregation discussion above.
> >
> > (2) Live migration of virtual machines among physical servers causes
> > relocation of MAC addresses across switch ports.  A so-called "gratuito=
us
> ARP"
> > is often used to inform the network of the MAC address move; port-based
> > source address validation information needs to move in response to such
> ARPs.
> >
> > (3) MAC address relocation is also used as a failure recovery technique=
; the
> > surviving hardware element (e.g., host in a cluster) takes over the MAC
> > addresses of the failed hardware; like the previous case, a "gratuitous=
 ARP"
> > is a common means of informing the network that the MAC address has mov=
ed,
> > and source address validation information needs to move in response to =
it.
> >
> > Minor issues:
> >
> > There doesn't seem to be much discussion of dynamic network reconfigura=
tion,
> > which may change traffic egress points.  VRRP may be a useful example t=
o
> > discuss beyond the typical routing protocol updates to forwarding table=
s.
> >
> > Nits/editorial comments:
> >
> > idnits 2.12.11 ran clean.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >


From piyush@ditenity.com  Wed Apr  3 10:38:33 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB5C21F8C1E for <gen-art@ietfa.amsl.com>; Wed,  3 Apr 2013 10:38:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[AWL=-1.335, BAYES_00=-2.599, DOS_OUTLOOK_TO_MX=1, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_EQ_LT4=0.442, RDNS_DYNAMIC=0.1]
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 Zi6q4IIu7yYb for <gen-art@ietfa.amsl.com>; Wed,  3 Apr 2013 10:38:32 -0700 (PDT)
Received: from mail-yh0-x233.google.com (mail-yh0-x233.google.com [IPv6:2607:f8b0:4002:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id BF77621F8758 for <gen-art@ietf.org>; Wed,  3 Apr 2013 10:38:32 -0700 (PDT)
Received: by mail-yh0-f51.google.com with SMTP id q1so275226yhf.24 for <gen-art@ietf.org>; Wed, 03 Apr 2013 10:38:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language:x-gm-message-state; bh=JK5ZCv4NaA4qje+54HJpN/2PfL22jKjnqXWLfJAv3SA=; b=VBt4NAgZRsRFIDAZAXmUaOtVBiJM2cT9JK0EOB6u//aMQERbLnHDdvuh15WMYCRBwF atxHGiJpux4ik0FO+0pel2un5gQdYHgzKXNRmvFvYboR5x696hU0G7fLQiC+y0hOqk14 aFsSs9cZE0sdtMxprLXg5h1+iXSaCbXleDCd5GwD6AqlLdHvfCevgyuEQv6+FIXy0fw8 M6doUt5VSJpZq/A72dilP8gCRgsp/ah8qVhBBjvx9Q8Rlv7cTDost/fu3S/QPWPQqEtQ GyJe9pB95iiia5M0WPVylum3Lcy7XZzW3LOJuRorr5msZjtGWbcacb6QyCURMhqWijuD 3Czg==
X-Received: by 10.236.0.167 with SMTP id 27mr1580138yhb.162.1365010712043; Wed, 03 Apr 2013 10:38:32 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id i78sm10702443yhf.14.2013.04.03.10.38.29 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 03 Apr 2013 10:38:31 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: <mrex@sap.com>
References: <003e01ce3077$5b6329f0$12297dd0$@ditenity.com> <20130403160532.EB4FD1A68A@ld9781.wdf.sap.corp>
In-Reply-To: <20130403160532.EB4FD1A68A@ld9781.wdf.sap.corp>
Date: Wed, 3 Apr 2013 10:38:20 -0700
Message-ID: <00a401ce3092$0a1415d0$1e3c4170$@ditenity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLGPak8yDNHA17reyWVE3Dtue90lZbUkR7w
Content-Language: en-us
X-Gm-Message-State: ALoCoQlcijRsTwZ+ZTwplmJSjDVxN9BM+qUeEAmtzdFHiXtxb938u3ZanCpDtyjbFY9UpvXz+EcV
Cc: ambarish@gmail.com, mmyers@fastq.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, sts@aaa-sec.com, pkix@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 17:38:33 -0000

> No, it does not make any sense at all.  An error code is unsigned and can
be
> easily inserted into the communication by an attacker. 

[Piyush] Funny that you make this argument. How does returning a signed
revoked address this? Attacker can still replace signed revoked with an
UNSIGNED TRY_LATER.

> These kinds of argument are based on two very flawed premises:
> 
>  (1) the premise that there exist only two possible states for a CA:
>       (a) safe and pristine
>       (b) full and thorough compromise of each and everything
[Piyush] NIST has addressed RA compromise and CA key compromise separately
so this is not true.
And you have not listed what other breaches you are trying to address
offering revoked for non-issued as the silver bullet for all those unknown
security breaches.
 You tendency to allude to vague problems to justify a particular solution,
couple with a reluctance to engage in a discussion regarding the security
implications continues to amuse me. List the other states and have a
discussion around how this solution solves those problems.> 
>  (2) that a huge PKI (100k+ entities) can be nuked and
>      re-personalized after a CA compromise at close to zero cost and
>      within the blink of an eye

and both premises exhibit a throrough cluelessness about security, risk
> management and the real world.
 
Let's get this right.
Only possible benefit of revoked for non-issued exists when there are CA
SIGNED certificates floating in the wild and CA has no clue that it has
issued it and therefore cannot revoke it.

Now, to say that clients are secure and CA can continue to operate if it
issues revoked OCSP response for such certificate indicates cluelessness
about security. 

Customers pay a lot of money for certificates for which the marginal cost of
issuance is almost 0. CAs obligation is to make sure that they are secure
and to address any breach securely.
To say that customers will tolerate a CA security breach just because it
issues revoked for non-issued and continues to publish CRLs that imply
fraudulent certificates as good indicates cluelessness about risk management
and real world.



From meral.shirazipour@ericsson.com  Wed Apr  3 19:54:06 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9EDC11E80A2 for <gen-art@ietfa.amsl.com>; Wed,  3 Apr 2013 19:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 yOnU-N1BUpJd for <gen-art@ietfa.amsl.com>; Wed,  3 Apr 2013 19:54:06 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id E8F3721F8EA5 for <gen-art@ietf.org>; Wed,  3 Apr 2013 19:54:05 -0700 (PDT)
X-AuditID: c618062d-b7f0d6d00000097e-62-515ceb4cc427
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 89.16.02430.C4BEC515; Thu,  4 Apr 2013 04:54:05 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0318.004; Wed, 3 Apr 2013 22:54:04 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-dnsext-dnssec-algo-signal.all@tools.ietf.org" <draft-ietf-dnsext-dnssec-algo-signal.all@tools.ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-dnsext-dnssec-algo-signal-09
Thread-Index: Ac4w3VrszGs7IiSEQICoRYrVRTJQmQ==
Date: Thu, 4 Apr 2013 02:54:03 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A0B644B@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A0B644Beusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsUyuXRPgq7v65hAg+nzhSw+vLvNanH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvj2LsFjAWL9CoWPnjG0sB4UaOLkYNDQsBE 4vBDyy5GTiBTTOLCvfVsXYxcHEICRxkljv57AeUsY5R4eLWBDaSKTcBCYvvv56wgtohApcTX bVvBbGYBTYlNTc/BaoQFfCTap9xlhqgJlvj5/ywThK0ncbV5AVgNi4CKxK6jvWA2r4C3xMZb p8FqGIGu+H5qDRPETHGJW0/mM0FcJyCxZM95ZghbVOLl43+sELayxPc5j1gg6vMlOvfuYIKY KShxcuYTlgmMwrOQjJqFpGwWkjKIuI7Egt2f2CBsbYllC18zw9hnDjxmQhZfwMi+ipGjtDi1 LDfdyGATIzBKjkmw6e5g3PPS8hCjNAeLkjhvkOuFACGB9MSS1OzU1ILUovii0pzU4kOMTByc Ug2MWTHix2s/Rs+6cj9pvqV01Zz0t7/uCp3kFl/0u/Rmr074XqMNftVzzp5bc604U8vrdjhb jGPcveolM+ev4bvJs7HJfsWNshKBjds/PHZczaAYPuP3243tN96+KFatyMk+fcLw5oacGyGt f4yFz1Rcrn9bpch0IiB/jVxD2NaYCoG+m1dqgr7MU2Ipzkg01GIuKk4EAEyuScRgAgAA
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-dnsext-dnssec-algo-signal-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2013 02:54:06 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A0B644Beusaamb107ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at http://wiki.tools.ietf.org/area/gen/trac/wiki/GenA=
rtfaq .

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-dnsext-dnssec-algo-signal-09
Reviewer: Meral Shirazipour
Review Date: 2013-04-03
IETF LC End Date: 2013-04-03
IESG Telechat date: N/A

Summary:
This draft is almost ready to be published as Standard RFC but I do have so=
me editorial comments.

Nits/editorial comments:
- Reading the abstract does not tell why these options are necessary. The 4=
th paragraph in Intro mentions the purpose of these options as well as Sect=
ion 8.
Please consider adding a similar sentence as Section 8 to the abstract:
"The proposed extensions allow the signaling of new algorithm uptake in cli=
ent code to allow zone administrators to know when it is possible to comple=
te an algorithm rollover in a DNSSEC signed zone."

-[Page 4], last sentence: "in a potential future example". Suggestion: "in =
potential future examples".

-[Page 7], Section 9, [I-D.ietf-dnsext-rfc2671bis-edns0], latest version is=
 10.

Best Regards,
Meral

---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A0B644Beusaamb107ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-CA" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-dnsext-dnssec-algo-signal-09<o:=
p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-04-03<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-04-03<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: N/A<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is almost ready to be published as Standa=
rd RFC but I do have some editorial comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">- Reading the abstract does not tell why these optio=
ns are necessary. The 4th paragraph in Intro mentions the purpose of these =
options as well as Section 8.<o:p></o:p></p>
<p class=3D"MsoNormal">Please consider adding a similar sentence as Section=
 8 to the abstract:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;The proposed extensions allow the signaling of=
 new algorithm uptake in client code to allow zone administrators to know w=
hen it is possible to complete an algorithm rollover in a DNSSEC signed zon=
e.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 4], last sentence: &quot;in a potential futur=
e example&quot;. Suggestion: &quot;in potential future examples&quot;.<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 7], Section 9, [I-D.ietf-dnsext-rfc2671bis-ed=
ns0], latest version is 10.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A0B644Beusaamb107ericsso_--

From alexey.melnikov@isode.com  Thu Apr  4 06:06:18 2013
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BCED21F8C16 for <gen-art@ietfa.amsl.com>; Thu,  4 Apr 2013 06:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.477
X-Spam-Level: 
X-Spam-Status: No, score=-102.477 tagged_above=-999 required=5 tests=[AWL=0.122, 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 dKpZx76GqRBf for <gen-art@ietfa.amsl.com>; Thu,  4 Apr 2013 06:06:17 -0700 (PDT)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0D83221F8BF4 for <gen-art@ietf.org>; Thu,  4 Apr 2013 06:06:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1365080772; d=isode.com; s=selector; i=@isode.com; bh=T4IR1+pOWlokZnYwcmzyvLiLdGkcwaax+IRmey1n/bc=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=mMTsIveJ7BblXCLcirJGZsbv9gMfgbt5SxvcAuHOPxxRiTa6MrGnlizvSCuyKDhm19UK+n lD+heRZuEN1XOrho7i9PksLvI4EZNyZTe4orqolrdod1P16ChOZZqHE+k8vUK1SnMXilS4 GROQ+xBj7u0Q+9lPP5tOc+dmOGzDCco=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <UV16wwAF4qvh@waldorf.isode.com>; Thu, 4 Apr 2013 14:06:12 +0100
Message-ID: <515D7AF4.8070807@isode.com>
Date: Thu, 04 Apr 2013 14:07:00 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: gen-art@ietf.org, draft-ietf-xrblock-rtcp-xr-decodability.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-xrblock-rtcp-xr-decodability-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2013 13:06:18 -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-xrblock-rtcp-xr-decodability-09
Reviewer: Alexey Melnikov
Review Date:  2013-04-04
IETF LC End Date: 2013-03-15
IESG Telechat date: N/A

Summary: Ready

Major issues: none

Minor issues: none

Nits/editorial comments: none

From ron.even.tlv@gmail.com  Thu Apr  4 11:28:39 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3757721F8493 for <gen-art@ietfa.amsl.com>; Thu,  4 Apr 2013 11:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.646
X-Spam-Level: 
X-Spam-Status: No, score=-0.646 tagged_above=-999 required=5 tests=[AWL=-0.817, BAYES_00=-2.599, DOS_OUTLOOK_TO_MX=1, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1]
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 hU2wqlMANWwi for <gen-art@ietfa.amsl.com>; Thu,  4 Apr 2013 11:28:38 -0700 (PDT)
Received: from mail-bk0-x22f.google.com (mail-bk0-x22f.google.com [IPv6:2a00:1450:4008:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3B3FF21F845A for <gen-art@ietf.org>; Thu,  4 Apr 2013 11:28:38 -0700 (PDT)
Received: by mail-bk0-f47.google.com with SMTP id ik5so1665724bkc.6 for <gen-art@ietf.org>; Thu, 04 Apr 2013 11:28:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=THuyq1gYnlQyMsbxZD2JXzGFE6cjrTZwpcTYtsjts9I=; b=cenXbGxwgHXa1fJ9BJvj5J5ylRtQejsRD2LRIhgbtR28chAce5q7ZTUq5F2JiFJ5uo /6Nn2SsMZrcnYshc/5/2CSA8T2ExDPkwqFqCyFAqXlUJAKUxz4BLmOAiwwnVHqnaWP4e jNVcSXn4Iot7dGZLpSjfwQSTl4B572dAlbq6uzyuQL0rXEx6cbimBcL+d+knNPk4YSCj 7G6uXpKEyWPoG+G8sSGQtp9ZPTGKPzAi+fbzCwED55ll0lHDdVfj3t0mFRmZ+NcYPobR sHTdpm/6pBHQpsAbFMICsR5sqmCs2VDbu3rqXe0PJZbC7ltdonE5+E7tVu5003Gt1keD LcxA==
X-Received: by 10.205.71.72 with SMTP id yj8mr5264373bkb.103.1365100117263; Thu, 04 Apr 2013 11:28:37 -0700 (PDT)
Received: from RoniE (bzq-79-181-177-28.red.bezeqint.net. [79.181.177.28]) by mx.google.com with ESMTPS id w6sm6844664bkz.17.2013.04.04.11.28.34 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 04 Apr 2013 11:28:36 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Johannes Merkle'" <johannes.merkle@secunet.com>
References: <039401ce2952$8bbc17a0$a33446e0$@gmail.com> <515ADB89.7090801@secunet.com>
In-Reply-To: <515ADB89.7090801@secunet.com>
Date: Thu, 4 Apr 2013 21:28:08 +0300
Message-ID: <013301ce3162$2a95a7d0$7fc0f770$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIH/SDbfl8mqRezt69IESmaN9HFNwHnODEBmEOO/LA=
Content-Language: en-us
Cc: gen-art@ietf.org, 'Dan Harkins' <dharkins@arubanetworks.com>, draft-merkle-ikev2-ke-brainpool.all@tools.ietf.org
Subject: Re: [Gen-art] GenART LC review of draft-merkle-ikev2-ke-brainpool-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2013 18:28:39 -0000

Hi Johannes,
Thanks for your clarifications.
I was not aware of the request to add a new column in
draft-ietf-ipsecme-dh-checks and since I did not see the column yet I could
not understand.
So everything look OK for me now.
Roni Even


-----Original Message-----
From: Johannes Merkle [mailto:johannes.merkle@secunet.com] 
Sent: 02 April, 2013 4:22 PM
To: Roni Even
Cc: draft-merkle-ikev2-ke-brainpool.all@tools.ietf.org; gen-art@ietf.org;
Dan Harkins
Subject: Re: GenART LC review of draft-merkle-ikev2-ke-brainpool-03

Hi,

> 1.       In table 1 the Transform ID are specified as TBD1 to TBD4. I
noticed that IANA have already assigned values
> 27-30. So they should be specified. If not it will be good to ask the RFC
editor before publication to update the table.
> I saw that you only asked IANA to allocate values.

I'll do so in the next version if it is not done by the RFC editor.


> 
> 2.       In the IANA section I did not understand to which table you are
referring to "For the new entries in the table
> of the Transform Type 4 repository, a reference to Section 2.3 of 
> [IKE_DH_Req] shall be included in the column named "Recipient Tests"
indicating the required checks for the other peer's Diffie-Hellman public
keys."
> 
This refers to the Table Transform Type 4 - Diffie-Hellman Group Transform
IDs, see
http://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xml#ikev2-
parameters-8

[IKE_DH_Req] requests from IANA to add a new column (named "Recipient
Tests") to that Table. We request IANA to add in that new column a a
reference to Section 2.3 of [IKE_DH_Req].

This request has been correctly understood by IANA, see email below.

Best regards,
Johannes


From mahoney@nostrum.com  Thu Apr  4 15:25:03 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6A9721F8F08 for <gen-art@ietfa.amsl.com>; Thu,  4 Apr 2013 15:25:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 lupgmApZrmAx for <gen-art@ietfa.amsl.com>; Thu,  4 Apr 2013 15:25:03 -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 3BA4121F8F07 for <gen-art@ietf.org>; Thu,  4 Apr 2013 15:25:02 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.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 r34MP1j1081715 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 4 Apr 2013 17:25:02 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <515DFDBD.8070309@nostrum.com>
Date: Thu, 04 Apr 2013 17:25:01 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: gen-art@ietf.org
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)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-04-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2013 22:25:03 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Roni Even         2013-04-12   draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03

Suresh Krishnan   2013-04-15   draft-ietf-sipcore-sip-websocket-08

Vijay Gurbani     2013-04-18   draft-ietf-mpls-tp-ring-protection-05


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From mahoney@nostrum.com  Thu Apr  4 15:33:05 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDAAA21F8FD3 for <gen-art@ietfa.amsl.com>; Thu,  4 Apr 2013 15:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 ESxUX2NEwTOn for <gen-art@ietfa.amsl.com>; Thu,  4 Apr 2013 15:33:05 -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 30A6821F8F07 for <gen-art@ietf.org>; Thu,  4 Apr 2013 15:33:05 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.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 r34MX4dT082579 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 4 Apr 2013 17:33:04 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <515DFFA0.2000500@nostrum.com>
Date: Thu, 04 Apr 2013 17:33:04 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: gen-art@ietf.org
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)
Subject: [Gen-art] Assignments for the 2013-04-11 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2013 22:33:05 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end      Draft
------------------------------------------------------------------------------------
Brian Carpenter        2013-03-18  draft-ietf-appsawg-webfinger-12 *

Christer Holmberg      2013-04-09  draft-saintandre-urn-example-04 **

David Black            2011-05-18  draft-ietf-savi-threat-scope-07 *

David Black            2013-03-27  draft-ietf-pkix-rfc2560bis-16 **

Elwyn Davies           2013-03-29  draft-ietf-tls-multiple-cert-status-extension-06 *

Roni Even              2013-03-26  draft-merkle-ikev2-ke-brainpool-03 **

Peter Yee              2013-03-08  draft-ietf-intarea-nat-reveal-analysis-06 *


* Earlier draft reviewed
** Already reviewed



I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

For your convenience, the review boilerplate template is included below.

Note that reviews should ideally be posted to the gen-art mailing list
by COB on Tuesday:
http://wiki.tools.ietf.org/area/gen/trac/wiki/

Jean

-------------------------------------------------------------------

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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From brian.e.carpenter@gmail.com  Fri Apr  5 00:04:09 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C574A21F8CF7 for <gen-art@ietfa.amsl.com>; Fri,  5 Apr 2013 00:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 7umn5677uJjV for <gen-art@ietfa.amsl.com>; Fri,  5 Apr 2013 00:04:07 -0700 (PDT)
Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) by ietfa.amsl.com (Postfix) with ESMTP id DC3AD21F8437 for <gen-art@ietf.org>; Fri,  5 Apr 2013 00:04:02 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id b12so3380568wgh.6 for <gen-art@ietf.org>; Fri, 05 Apr 2013 00:04:02 -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:content-type:content-transfer-encoding; bh=bsZV3d2DLwzg+OYAzzBQQwUxSDb59gRFvGXn2+PSsL0=; b=AdiH06GegVZWoybp5xqqUGlMHxtcwqW6WkavrhH8PS09a5IEyHGrIBJf1jU8hXPxtM CbirOkgBvF+IJ1VEDl7Xg6g7ivnvoadV/sLn/VrhGDFb/S7GLkKQlS5bLEuoM5ilLcTE M1PuydIHm5dvtBA9jMFpMN9CGJ5CIA7F0UZUtgNapFfO6E5J+4b5WD7No6Lmczxt3ISp cbR4Roj364R2kYFqeMF8fAsRVn85QWD+IKgo7pAuHeFb87B8b7epNiGN+UgLZX0IVFUC +EgEIB3QLDPyf9P+Tcefg+0lGed9BRKre0gNs+5RLtli2X7Wv6frUrCXED2BwrorSIcp ah1g==
X-Received: by 10.194.82.104 with SMTP id h8mr14216174wjy.3.1365145440473; Fri, 05 Apr 2013 00:04:00 -0700 (PDT)
Received: from [192.168.1.65] (host-84-13-238-122.opaltelecom.net. [84.13.238.122]) by mx.google.com with ESMTPS id fv2sm2082115wib.6.2013.04.05.00.03.59 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 05 Apr 2013 00:03:59 -0700 (PDT)
Message-ID: <515E7769.9020600@gmail.com>
Date: Fri, 05 Apr 2013 08:04:09 +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: draft-ietf-appsawg-webfinger.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-appsawg-webfinger-12.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2013 07:04:09 -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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-appsawg-webfinger-12.txt
Reviewer: Brian Carpenter
Review Date: 2013-04-05
IETF LC End Date: 2013-03-18
IESG Telechat date: 2013-04-11

Summary:  Ready
--------

Comments:
---------

Thanks for handling my Last Call comment.




From peter@akayla.com  Fri Apr  5 16:55:06 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97F0F21F990A; Fri,  5 Apr 2013 16:55:06 -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 qFTRGISOl25s; Fri,  5 Apr 2013 16:55:05 -0700 (PDT)
Received: from p3plsmtpa09-06.prod.phx3.secureserver.net (p3plsmtpa09-06.prod.phx3.secureserver.net [173.201.193.235]) by ietfa.amsl.com (Postfix) with ESMTP id C052921F9907; Fri,  5 Apr 2013 16:55:05 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-06.prod.phx3.secureserver.net with  id LPv41l0031huGat01Pv4RV; Fri, 05 Apr 2013 16:55:05 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-intarea-nat-reveal-analysis.all@tools.ietf.org>
Date: Fri, 5 Apr 2013 16:56:18 -0700
Message-ID: <030101ce3259$2b900520$82b00f60$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac4yVqRs/Mt47fa6QWSvsgPU2PDQHw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-intarea-nat-reveal-analysis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2013 23:55:06 -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-intarea-nat-reveal-analysis-06
Reviewer: Peter Yee
Review Date: Apr-5-2013
IETF LC End Date: Mar-8-2013
IESG Telechat date: Apr-11-2013

This draft is basically ready for publication, but has nits that should =
be fixed before publication. [Ready with nits]

It addresses most of the issues raised in my review of the -05 version.  =
Two items from that review that I'm
revisiting are noted below with text from the original review and =
responses from one of the authors (Med).
We agreed that those two revisited items could be addressed in a =
subsequent revision; they are just
recorded here for ease of reference.

Major issues:

Minor issues:

Nits:

[Old]

>>Section 3.1, 5th paragraph: I don't quite follow what's being said =
here.
>>Is the point that the address-sharing function should reveal the same=20
>>HOST_ID for any given host regardless of what layer or mechanism that=20
>>HOST_ID is being conveyed across?  How does this relate to=20
>>interference between HOST_IDs?

>Med: The point is: when several layers are used to inject a host_id, =
the device should check the same subset of information is revealed. For =
instance, there should not be conflict, etc.

Then perhaps you could reword so that "should reveal subsets of the same =
information" becomes "should reveal the same subsets of information at =
each layer"?

>>Section 4.9.2, 4th bullet item, 2nd sentence: Delete "heavy and" =
unless you want to=20
>>explain what heavy means.

>Med: Establishing agreements with the owner of the address sharing =
function and owners of servers is heavy. This is already mentioned in =
the text.

Perhaps you could replace "heavy" with "burdensome".

[New]

In the references, there seem to be an excess of commas in a couple of =
places.   Look for the string ", ," (comma space comma) and you'll see =
what I mean.  The document titles start with an extra comma and end with =
one.

Also in the references, for RFC 1413, put a space between the "M." and =
the "C." in Mike St. Johns' initials.



From ron.even.tlv@gmail.com  Sat Apr  6 00:10:09 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D73A21F93C7; Sat,  6 Apr 2013 00:10:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.181
X-Spam-Level: 
X-Spam-Status: No, score=-2.181 tagged_above=-999 required=5 tests=[AWL=1.417,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 iv2mvnvshxKT; Sat,  6 Apr 2013 00:10:07 -0700 (PDT)
Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com [74.125.83.43]) by ietfa.amsl.com (Postfix) with ESMTP id 34B5921F938E; Sat,  6 Apr 2013 00:10:07 -0700 (PDT)
Received: by mail-ee0-f43.google.com with SMTP id e50so1651953eek.16 for <multiple recipients>; Sat, 06 Apr 2013 00:10:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=Zu49OIjZ+HeCQPPngKG0z4uEQqcXLMfItX9GcU11EUQ=; b=JRuzEMV7OlwXYy2EaAFJl6+09r7CpqrmpJuop+5NKQozPEU2HtpXaiyuiboiGXM4hw LAqSX1GKX/3NYE/mMqfRLP1I8B0rkIai2goGpDXAe2IIh5Ps6TYtZHEZWPaSkSqFajiO FkgKqoL9LMX9XojTbg4EKTM+HauYFx6unpWSUCGysgn13QfWPPTd+097L82xaSjmtGGd No9CDjuHzjUGjLr23VvzZ6jrGo/dO5mstu3Sz0kUYbzfSboY6oPoDSb+l13sarxIS1UG Q/k52wvCCQ8LKK0a4Gl47KjyifZFD/Hdmaqq9YO5t2K9TSYN5X9KKqp3+GTrU50Zjq5M iqBw==
X-Received: by 10.14.39.5 with SMTP id c5mr18035664eeb.27.1365232206108; Sat, 06 Apr 2013 00:10:06 -0700 (PDT)
Received: from RoniE (bzq-79-181-177-28.red.bezeqint.net. [79.181.177.28]) by mx.google.com with ESMTPS id s47sm19329822eeg.8.2013.04.06.00.10.03 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 06 Apr 2013 00:10:05 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets.all@ietf.tools.org>, <ietf@ietf.org>
Date: Sat, 6 Apr 2013 10:09:38 +0300
Message-ID: <01f201ce3295$b5a1aa70$20e4ff50$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01F3_01CE32AE.DAEFCCD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac4ylbNrszEEef+vS7Gk5rMUmr+arQ==
Content-Language: en-us
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Apr 2013 07:10:09 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01F3_01CE32AE.DAEFCCD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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-opsec-ipv6-implications-on-ipv4-nets-03

Reviewer: Roni Even

Review Date:2013-4-6

IETF LC End Date: 2013-4-12

IESG Telechat date: 

 

Summary: This draft is ready for publication as an Informational RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.	I found this draft very informational but I was wondering if it will
be better to have in the introduction and the abstract a sentence that will
mention the target audience for this draft.

 


------=_NextPart_000_01F3_01CE32AE.DAEFCCD0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:551036080;
	mso-list-type:hybrid;
	mso-list-template-ids:-1333356038 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;4&#8211;6<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-4&#8211;12<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>I found =
this draft very informational but I was wondering if it will be better =
to have in the introduction and the abstract a sentence that will =
mention the target audience for this draft.<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_01F3_01CE32AE.DAEFCCD0--


From ron.even.tlv@gmail.com  Sat Apr  6 03:44:18 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB30D21F8C03; Sat,  6 Apr 2013 03:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.223
X-Spam-Level: 
X-Spam-Status: No, score=-0.223 tagged_above=-999 required=5 tests=[AWL=-0.894, BAYES_00=-2.599, DOS_OUTLOOK_TO_MX=1, DYN_RDNS_SHORT_HELO_HTML=0.499, FH_HOST_EQ_D_D_D_D=0.765, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1]
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 XQwUZ5SDxBkn; Sat,  6 Apr 2013 03:44:18 -0700 (PDT)
Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABB021F8BEB; Sat,  6 Apr 2013 03:44:17 -0700 (PDT)
Received: by mail-ea0-f171.google.com with SMTP id b15so1659845eae.2 for <multiple recipients>; Sat, 06 Apr 2013 03:44:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=+Gk8IyAnvRf1MV1HS22URGBmAgw6AEvRgx7sP4GdSgI=; b=jQCCMcp5LZLq3PV1eIm90p3ScKOHi2XprZTvS4HjJPgRre44jZk/pEIno+oHPiajlP UsWZt3+f64aJoeYXSDxTEdMSi20n/gRdXGkD++faeuxQoVSW7pqANe6N8mrHWyWqz1Dy WCuTskTwHtJgx0ea4BzZcBOK3VdPobwFX+SLCbP3kDVrW+e6/yT96tEbz8iDhsWZbIjc HyzshO4jRc44ycmeEAUM29uPVjQJE6g2NVVXvDZiSWURfb0DxTr4a5w2Zajk42PL+a21 73jD370HcPx7/R6h2MuDI/jf00fXFtt2ojSKZxbIgKl9xCHYtttyYaOY4CQ6YG2ryF11 uYqg==
X-Received: by 10.14.39.5 with SMTP id c5mr19649797eeb.27.1365245056295; Sat, 06 Apr 2013 03:44:16 -0700 (PDT)
Received: from RoniE (bzq-79-181-177-28.red.bezeqint.net. [79.181.177.28]) by mx.google.com with ESMTPS id s47sm20232439eeg.8.2013.04.06.03.44.11 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 06 Apr 2013 03:44:15 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <ietf@ietf.org>, <draft-ietf-opsec-ipv6-implications-on-ipv4-nets.all@tools.ietf.org>
Date: Sat, 6 Apr 2013 13:43:43 +0300
Message-ID: <020001ce32b3$a06aed60$e140c820$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0201_01CE32CC.C5B8C1A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac4ylbNrszEEef+vS7Gk5rMUmr+arQ==
Content-Language: en-us
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Apr 2013 10:44:18 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0201_01CE32CC.C5B8C1A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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-opsec-ipv6-implications-on-ipv4-nets-03

Reviewer: Roni Even

Review Date:2013-4-6

IETF LC End Date: 2013-4-12

IESG Telechat date: 

 

Summary: This draft is ready for publication as an Informational RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.	I found this draft very informational but I was wondering if it will
be better to have in the introduction and the abstract a sentence that will
mention the target audience for this draft.

 


------=_NextPart_000_0201_01CE32CC.C5B8C1A0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:486477111;
	mso-list-template-ids:1580108680;}
@list l1
	{mso-list-id:551036080;
	mso-list-type:hybrid;
	mso-list-template-ids:-1333356038 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I am the assigned =
Gen-ART reviewer for this draft. For background on Gen-ART, please see =
the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;4&#8211;6<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-4&#8211;12<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l1 level1 lfo3'>I found =
this draft very informational but I was wondering if it will be better =
to have in the introduction and the abstract a sentence that will =
mention the target audience for this draft.<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0201_01CE32CC.C5B8C1A0--


From stbryant@cisco.com  Mon Apr  8 03:53:59 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0D9E21F89DB; Mon,  8 Apr 2013 03:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 8P-W1BmjXq2b; Mon,  8 Apr 2013 03:53:58 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id A40BB21F8976; Mon,  8 Apr 2013 03:53:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5828; q=dns/txt; s=iport; t=1365418438; x=1366628038; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=tTBT4KoOfA85SAqYSkpTVGcwcw11IuVu/hPwk41Qyf8=; b=cSCssxix4FFUfg1Yei087L7I2pgWvS9/x13skTpSMbrPwJaeQrN5w1SN +DeSS9oEFvV4k24/d4eemINZwQWzFrb47VSpSVoMqS1hbTw5+SFaiKiYC HGJsw0bEVGX2p5WEjMzeYCToDqNK0jcTqA9MIOKHJNhLVPgSfG32xHb0q Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAAOhYlGQ/khN/2dsb2JhbABRgwY2wSiBBxZ0gh8BAQEDATgvEQEQCw4GBAkWCAcJAwIBAgE0EQYNAQUCAQEQh3oGDLxKjyMHg0EDlnSRDoMM
X-IronPort-AV: E=Sophos;i="4.87,429,1363132800"; d="scan'208";a="152633069"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 08 Apr 2013 10:53:56 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r38ArsSI003117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Apr 2013 10:53:54 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r38ArqHx024467; Mon, 8 Apr 2013 11:53:53 +0100 (BST)
Message-ID: <5162A1C0.9020409@cisco.com>
Date: Mon, 08 Apr 2013 11:53:52 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Richard Barnes <rlb@ipv.sx>
References: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com> <515AD8B1.20503@cisco.com> <CAL02cgTExcoC+fMYVs0KT==yx1vZgaK5Tc8Dij3vhiR9Os3YkQ@mail.gmail.com>
In-Reply-To: <CAL02cgTExcoC+fMYVs0KT==yx1vZgaK5Tc8Dij3vhiR9Os3YkQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg@ietf.org>, Richard Barnes <rbarnes@bbn.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-mpls-tp-ethernet-addressing@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2013 10:53:59 -0000

On 02/04/2013 15:28, Richard Barnes wrote:
> Thanks for following up, and for the re-send.  Just to be clear, I do 
> not mean these as blocking points.
>
> On the former point, I might just suggest a minor edit to the 
> introduction:
> OLD: "This document specifies the options for determination and 
> selection of next-hop Ethernet MAC addressing under these circumstances."
> NEW: "This document specifies the options for determination and 
> selection of next-hop Ethernet MAC addressing when MPLS-TP is used in 
> a "pure Ethernet" manner, without any IP forwarding capability."

After various rounds of tweeking:

"This document specifies the options for the determination and selection 
of the next-hop Ethernet MAC address when MPLS-TP is used between nodes 
that do not have an IP dataplane."

The subtly is the network may be mixed IP capable and non-IP capable.


>
> On the latter point, I can understand the desire to make the simple 
> case simple, and the text at the end of Section 2 sends a clear 
> warning. It does seems like GAP would also allow autoconfiguration 
> without further NMS interaction.  (Unless the NMS is configuring 
> per-Ethernet-address policies, e.g., "forward packets with this label 
> to 00:11:22:33:44:55". Is that the case?)
Yes. One case is a network that is generally NMS configured, and wants 
to use unicast MAC addresses, but wants to allow the craft people to 
plug in a new linecard without talking to the NMS. In such circumstances 
the only auto config would be teh MAC addresses.

Stewart

>
>
>
>
> On Tue, Apr 2, 2013 at 9:10 AM, Stewart Bryant <stbryant@cisco.com 
> <mailto:stbryant@cisco.com>> wrote:
>
>     Resending due to Richards change of address.
>
>     Stewart
>
>
>     On 11/02/2013 23:45, Richard Barnes wrote:
>>     I have been selected as the General Area Review Team (Gen-ART)
>>     reviewer for this draft (for background on Gen-ART,
>>     pleaseseehttp://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html
>>     <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>). Please
>>     wait for direction from your document shepherd or AD before
>>     posting a new version of the draft. Document:
>>     draft-ietf-mpls-tp-ethernet-
>>     addressing-05
>>     Reviewer: Richard Barnes
>>     Review Date: 2013-02-11
>>     IETF LC End Date: 2013-02-18
>>     IESG Telechat date: TBD
>>
>>     Summary:  Ready, with a couple of minor questions / clarifications.
>>
>>     Comment:
>>
>>     The document is mostly very clearly written.  (Thanks!)  It would have helped me understand if it could have been clarified up front that the mechanism in this document is intended for "pure Ethernet" MPLS-TP (without assumptions about layer 3+).  The current introduction says as much, but in a negative way, in terms of ARP or ND not being available.
>>
>>     I have some minor unease about the distinction that this document makes between point-to-point and multipoint links.  The document correctly notes that a point-to-point link might become multipoint without either end being aware.  I would have thought this would argue for using GAP in all cases, but instead the document carries on with addressing the point-to-point case separately..
>>
>     Richard
>
>     It is always difficult when writing a simple draft dealing with a
>     small
>     component of a larger technology to know how much tutorial to include,
>     but I believe the point about operation in the absence IP would be
>     well known
>     to anyone implementing this. In particular we assume that anyone
>     implementing the draft would have read the required references called
>     up in the first paragraph of the Introduction:
>
>
>     " The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of
>     protocol
>     functions that meet the requirements [RFC5654] for the application of
>     MPLS to the construction and operation of packet-switched transport
>     networks. The MPLS-TP data plane consists of those MPLS-TP functions
>     concerned with the encapsulation and forwarding of MPLS-TP packets
>     and is described in [RFC5960]."
>
>     RFC5654 says:
>
>     "   36  It MUST be possible to operate and configure the MPLS-TP data
>             plane without any IP forwarding capability in the MPLS-TP data
>             plane.  That is, the data plane only operates on the MPLS label."
>     Thus I think that the text is complete as it stands and requires no
>     further clarification for anyone that needs to consider the technology
>     it describes.
>
>
>     With regard to your second point, the issue that we are have, is that
>     there are a number of deployment scenarios where the operator knows
>     that the link is Pt-Pt, and there is a reluctance by that community to
>     use anything other than NMS configuration. That has lead them
>     to use Ethernet broadcast addressing which allows the crafts to
>     change h/w without the need for reconfiguration by the NMS.
>     Against that background moving them onto the use of a Ethernet m/c
>     address is a step forward. To require using the GAP to that
>     community would illustrate that the IETF is out of touch with
>     their needs and methods of network operation.
>
>     Hopefully this additional background, which I believe is well
>     known to the MPLS-TP community to which this draft is directed,
>     satisfies your concern on the latter point.
>
>     - Stewart
>
>
>
>     -- 
>     For corporate legal information go to:
>
>     http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From stbryant@cisco.com  Mon Apr  8 06:21:42 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B408221F93B1; Mon,  8 Apr 2013 06:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 0nezbyUnOi14; Mon,  8 Apr 2013 06:21:41 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1144B21F919A; Mon,  8 Apr 2013 06:21:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4670; q=dns/txt; s=iport; t=1365427301; x=1366636901; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Q0Xt/neEuvjJ6JCFcjEgH/I9XOwQTECx19TufBP5sOg=; b=L43HiazZqRKXyhRDqPzEeBUuc+4IE7VzlYQOqaltgjxh5vpobmqVJaHa 9YdzYfxe8c4ouZHoDoT2O1QQF2LkCcCiT2VxhOTj4KpXN4LBaP/BwL5wM sbErua4gPogR16/WWCa491UvJnKK8OwfrZRwnFUxZaufRMbyGjfy9QyXB I=;
X-IronPort-AV: E=Sophos;i="4.87,431,1363132800"; d="scan'208";a="81832529"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 08 Apr 2013 13:21:40 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r38DLcUH023639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Apr 2013 13:21:38 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r38DLbpv004576; Mon, 8 Apr 2013 14:21:37 +0100 (BST)
Message-ID: <5162C461.8080303@cisco.com>
Date: Mon, 08 Apr 2013 14:21:37 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
References: <94A203EA12AECE4BA92D42DBFFE0AE470F1636@eusaamb101.ericsson.se>
In-Reply-To: <94A203EA12AECE4BA92D42DBFFE0AE470F1636@eusaamb101.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org List" <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Acee Lindem <acee.lindem@ericsson.com>, "draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org" <draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org>, "ospf-chairs@tools.ietf.org" <ospf-chairs@tools.ietf.org>, "Abhay Roy \(akr\)" <akr@cisco.com>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2013 13:21:42 -0000

Alvaro

Please can you add a line or two of motivation to the draft.

I don't think it needs to be major text, but it will be useful to
record the reason for the update to the registry.

Thanks

Stewart

On 06/03/2013 15:05, Acee Lindem wrote:
> I think the draft can talk to the motivation in general terms with the
> embedded routing draft cited as an example.
> Thanks,
> Acee
>
> On 3/6/13 7:01 AM, "Stewart Bryant" <stbryant@cisco.com> wrote:
>
>> Chairs
>>
>> Please can you re on the question posed by Alvaro below.
>>
>> Do you have any objection to adding motivation text to the draft?
>>
>> Certainly I think it would be useful in IESG review.
>>
>> Stewart
>>
>> On 11/02/2013 21:15, Alvaro Retana (aretana) wrote:
>>> On 1/16/13 5:17 PM, "Ben Campbell" <ben@nostrum.com> wrote:
>>>
>>> Ben:
>>>
>>> Hi!
>>>
>>> Sorry for the delay, my filters put this in a different place..  I'm
>>> explicitly adding the OSPF chairs.  Comments below.
>>>
>>>
>>>> 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-ospf-ospfv3-iid-registry-update-00
>>>> Reviewer: Ben Campbell
>>>> Review Date: 2013-01-16
>>>> IETF LC End Date: 2013-01-24
>>>>
>>>> Summary: This draft is not ready for publication as a proposed
>>>> standard.
>>>> There is a significant IANA registration issue described in the review
>>>> body.
>>>>
>>>> Major issues:
>>>>
>>>> This draft carves out a significant part of a registry with an
>>>> assignment
>>>> policy of "standards action" for "private use". It offers very little
>>>> motivation for the change. In my opinion, this sort of change should
>>>> come
>>>> with a clear justification.
>>>>
>>>> Specifically, the draft modifies the OSPFv3 Address Family Instance ID
>>>> registry to carve out half of the unassigned space for "private use".
>>>> The
>>>> justification for this is a single sentence saying that some networks
>>>> need to use IIDs to identify specific applications. I think that needs
>>>> significant elaboration in order to motivate the change in a way that
>>>> the
>>>> reader can evaluate.
>>>>
>>>> My understanding from the OFPS list is that this is in support of
>>>> draft-ietf-ospf-ipv4-embedded-ipv6-routing, which is an informational
>>>> draft. I have to wonder why the draft under review was not simply the
>>>> IANA considerations for that draft.
>>>>
>>>> I suggest one of two paths forward:
>>>>
>>>> 1) If this change is in support of that draft in particular, then this
>>>> draft should say that, and include a _normative_ reference. I recognize
>>>> the normative downref would complicate things--but I think that
>>>> complication is reasonable under the circumstances.
>>>>
>>>> 2) If this change is to support a general need that goes beyond
>>>> draft-ietf-ospf-ipv4-embedded-ipv6-routing, then this draft should
>>>> describe that need in enough detail for people to think about it,
>>>> perhaps
>>>> with an informative reference to
>>>> draft-ietf-ospf-ipv4-embedded-ipv6-routing as an _example_.
>>> In short (from the shepherd write-up): "The new range is for
>>> applications
>>> that do not justify a standards track OSPFv3 Instance ID allocation. An
>>> example would be "Routing for IPv4-embedded IPv6 Packets"".
>>>
>>> During pre-publication review, the WG chairs asked us to not include
>>> explicit references to draft-ietf-ospf-ipv4-embedded-ipv6-routing as
>>> that
>>> is just an example and not the only potential user/driver.  I don't
>>> have a
>>> problem adding an example, but I want to get agreement/comments/guidance
>>> from the chairs before adding the text.  Acee/Abhay??
>>>
>>>
>>>> Minor issues:
>>>>
>>>> -- section 3:
>>>>
>>>> I don't think it's appropriate to use normative language for IANA
>>>> requests. Especially not "MUST". (I think the strongest thing we can do
>>>> here is a polite request :-)  )   I suggest recasting that to
>>>> descriptive
>>>> language, and removing section 2 and the RFC 2119 reference.
>>> Yes, we already removed that in the -01 version.
>>>
>>> Thanks!!
>>>
>>> Alvaro.
>>>
>>> .
>>>
>>
>> -- 
>> For corporate legal information go to:
>>
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>
> .
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From rlb@ipv.sx  Mon Apr  8 12:34:13 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5209C21F8AB0 for <gen-art@ietfa.amsl.com>; Mon,  8 Apr 2013 12:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level: 
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[AWL=1.083,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 HPYLVhh6LQK2 for <gen-art@ietfa.amsl.com>; Mon,  8 Apr 2013 12:34:12 -0700 (PDT)
Received: from mail-oa0-f49.google.com (mail-oa0-f49.google.com [209.85.219.49]) by ietfa.amsl.com (Postfix) with ESMTP id F360B21F86C3 for <gen-art@ietf.org>; Mon,  8 Apr 2013 12:34:11 -0700 (PDT)
Received: by mail-oa0-f49.google.com with SMTP id j6so6488028oag.8 for <gen-art@ietf.org>; Mon, 08 Apr 2013 12:34:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=V3lC1g8A4fJ+BwKMULhH1ucolMARKTbbrTU8Gbt609I=; b=a08aQQd4TeLQYHLIfAeKnhh591wvBshUAoPmBJAnSk2mUgHle3jIRimVFUHIuH3HtC RQyncKDJR/NsWqBjbTmLWgbePdSyXX4V5APVi/rhcX+yZv/3jfXCCmOhN8gEja25kutQ z8cGydLDJEVHVyYZAtKyeKcJGz+c69Hrfyhxouvz8Cgo0SGbqEXwYinqBVnQL7GEBwR3 jlI6PQULBcEbvHPGZYepd1fI0CJ8HmgnRpJbC+hs0aEqtJTn73X0qPvcCMJQmuoQZijS Xu9PtuF74/uRDmI+6JEsUqrFXixIVYnCm7PoEjQNWZXx6x/xslr+wnIIf3i/d3UND9ZE h+0Q==
MIME-Version: 1.0
X-Received: by 10.182.43.103 with SMTP id v7mr16300451obl.17.1365449651473; Mon, 08 Apr 2013 12:34:11 -0700 (PDT)
Received: by 10.60.25.196 with HTTP; Mon, 8 Apr 2013 12:34:11 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <5162A1C0.9020409@cisco.com>
References: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com> <515AD8B1.20503@cisco.com> <CAL02cgTExcoC+fMYVs0KT==yx1vZgaK5Tc8Dij3vhiR9Os3YkQ@mail.gmail.com> <5162A1C0.9020409@cisco.com>
Date: Mon, 8 Apr 2013 15:34:11 -0400
Message-ID: <CAL02cgRhzi7hE3LQt26cUjqo30CJurF5Sxpph=fdgfgpAX=0GQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: stbryant@cisco.com
Content-Type: multipart/alternative; boundary=f46d044794f36f602c04d9de853d
X-Gm-Message-State: ALoCoQnn07o9PF1QBo1YcgfW19oHPoy1mGn6p2bjJribPwvG60r3DpyL7LfEKizIIcmqHO0GbsOD
Cc: The IESG <iesg@ietf.org>, Richard Barnes <rbarnes@bbn.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-mpls-tp-ethernet-addressing@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2013 19:34:13 -0000

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

Hi Stewart,

I think this resolves my issues.

Thanks,
--Richard


On Mon, Apr 8, 2013 at 6:53 AM, Stewart Bryant <stbryant@cisco.com> wrote:

> On 02/04/2013 15:28, Richard Barnes wrote:
>
>> Thanks for following up, and for the re-send.  Just to be clear, I do not
>> mean these as blocking points.
>>
>> On the former point, I might just suggest a minor edit to the
>> introduction:
>> OLD: "This document specifies the options for determination and selection
>> of next-hop Ethernet MAC addressing under these circumstances."
>> NEW: "This document specifies the options for determination and selection
>> of next-hop Ethernet MAC addressing when MPLS-TP is used in a "pure
>> Ethernet" manner, without any IP forwarding capability."
>>
>
> After various rounds of tweeking:
>
> "This document specifies the options for the determination and selection
> of the next-hop Ethernet MAC address when MPLS-TP is used between nodes
> that do not have an IP dataplane."
>
> The subtly is the network may be mixed IP capable and non-IP capable.
>
>
>
>
>> On the latter point, I can understand the desire to make the simple case
>> simple, and the text at the end of Section 2 sends a clear warning. It does
>> seems like GAP would also allow autoconfiguration without further NMS
>> interaction.  (Unless the NMS is configuring per-Ethernet-address policies,
>> e.g., "forward packets with this label to 00:11:22:33:44:55". Is that the
>> case?)
>>
> Yes. One case is a network that is generally NMS configured, and wants to
> use unicast MAC addresses, but wants to allow the craft people to plug in a
> new linecard without talking to the NMS. In such circumstances the only
> auto config would be teh MAC addresses.
>
> Stewart
>
>
>>
>>
>>
>> On Tue, Apr 2, 2013 at 9:10 AM, Stewart Bryant <stbryant@cisco.com<mailto:
>> stbryant@cisco.com>> wrote:
>>
>>     Resending due to Richards change of address.
>>
>>     Stewart
>>
>>
>>     On 11/02/2013 23:45, Richard Barnes wrote:
>>
>>>     I have been selected as the General Area Review Team (Gen-ART)
>>>     reviewer for this draft (for background on Gen-ART,
>>>     pleaseseehttp://www.**alvestrand.no/ietf/gen/art/**gen-art-FAQ.html<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>
>>>     <http://www.alvestrand.no/**ietf/gen/art/gen-art-FAQ.html<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>
>>> >**). Please
>>>
>>>     wait for direction from your document shepherd or AD before
>>>     posting a new version of the draft. Document:
>>>     draft-ietf-mpls-tp-ethernet-
>>>     addressing-05
>>>     Reviewer: Richard Barnes
>>>     Review Date: 2013-02-11
>>>     IETF LC End Date: 2013-02-18
>>>     IESG Telechat date: TBD
>>>
>>>     Summary:  Ready, with a couple of minor questions / clarifications.
>>>
>>>     Comment:
>>>
>>>     The document is mostly very clearly written.  (Thanks!)  It would
>>> have helped me understand if it could have been clarified up front that the
>>> mechanism in this document is intended for "pure Ethernet" MPLS-TP (without
>>> assumptions about layer 3+).  The current introduction says as much, but in
>>> a negative way, in terms of ARP or ND not being available.
>>>
>>>     I have some minor unease about the distinction that this document
>>> makes between point-to-point and multipoint links.  The document correctly
>>> notes that a point-to-point link might become multipoint without either end
>>> being aware.  I would have thought this would argue for using GAP in all
>>> cases, but instead the document carries on with addressing the
>>> point-to-point case separately..
>>>
>>>      Richard
>>
>>     It is always difficult when writing a simple draft dealing with a
>>     small
>>     component of a larger technology to know how much tutorial to include,
>>     but I believe the point about operation in the absence IP would be
>>     well known
>>     to anyone implementing this. In particular we assume that anyone
>>     implementing the draft would have read the required references called
>>     up in the first paragraph of the Introduction:
>>
>>
>>     " The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of
>>     protocol
>>     functions that meet the requirements [RFC5654] for the application of
>>     MPLS to the construction and operation of packet-switched transport
>>     networks. The MPLS-TP data plane consists of those MPLS-TP functions
>>     concerned with the encapsulation and forwarding of MPLS-TP packets
>>     and is described in [RFC5960]."
>>
>>     RFC5654 says:
>>
>>     "   36  It MUST be possible to operate and configure the MPLS-TP data
>>             plane without any IP forwarding capability in the MPLS-TP data
>>             plane.  That is, the data plane only operates on the MPLS
>> label."
>>     Thus I think that the text is complete as it stands and requires no
>>     further clarification for anyone that needs to consider the technology
>>     it describes.
>>
>>
>>     With regard to your second point, the issue that we are have, is that
>>     there are a number of deployment scenarios where the operator knows
>>     that the link is Pt-Pt, and there is a reluctance by that community to
>>     use anything other than NMS configuration. That has lead them
>>     to use Ethernet broadcast addressing which allows the crafts to
>>     change h/w without the need for reconfiguration by the NMS.
>>     Against that background moving them onto the use of a Ethernet m/c
>>     address is a step forward. To require using the GAP to that
>>     community would illustrate that the IETF is out of touch with
>>     their needs and methods of network operation.
>>
>>     Hopefully this additional background, which I believe is well
>>     known to the MPLS-TP community to which this draft is directed,
>>     satisfies your concern on the latter point.
>>
>>     - Stewart
>>
>>
>>
>>     --     For corporate legal information go to:
>>
>>     http://www.cisco.com/web/**about/doing_business/legal/**
>> cri/index.html<http://www.cisco.com/web/about/doing_business/legal/cri/index.html>
>>
>>
>>
>
> --
> For corporate legal information go to:
>
> http://www.cisco.com/web/**about/doing_business/legal/**cri/index.html<http://www.cisco.com/web/about/doing_business/legal/cri/index.html>
>
>

--f46d044794f36f602c04d9de853d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Stewart,<div><br></div><div>I think this resolves my issues.</div><div><=
br></div><div>Thanks,</div><div>--Richard</div><div><br><br><div class=3D"g=
mail_quote">On Mon, Apr 8, 2013 at 6:53 AM, Stewart Bryant <span dir=3D"ltr=
">&lt;<a href=3D"mailto:stbryant@cisco.com" target=3D"_blank">stbryant@cisc=
o.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 02/04/2013 15:28, Richa=
rd Barnes wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Thanks for following up, and for the re-send. =A0Just to be clear, I do not=
 mean these as blocking points.<br>
<br>
On the former point, I might just suggest a minor edit to the introduction:=
<br>
OLD: &quot;This document specifies the options for determination and select=
ion of next-hop Ethernet MAC addressing under these circumstances.&quot;<br=
>
NEW: &quot;This document specifies the options for determination and select=
ion of next-hop Ethernet MAC addressing when MPLS-TP is used in a &quot;pur=
e Ethernet&quot; manner, without any IP forwarding capability.&quot;<br>

</blockquote>
<br></div>
After various rounds of tweeking:<br>
<br>
&quot;This document specifies the options for the determination and selecti=
on of the next-hop Ethernet MAC address when MPLS-TP is used between nodes =
that do not have an IP dataplane.&quot;<br>
<br>
The subtly is the network may be mixed IP capable and non-IP capable.<div c=
lass=3D"im"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
On the latter point, I can understand the desire to make the simple case si=
mple, and the text at the end of Section 2 sends a clear warning. It does s=
eems like GAP would also allow autoconfiguration without further NMS intera=
ction. =A0(Unless the NMS is configuring per-Ethernet-address policies, e.g=
., &quot;forward packets with this label to 00:11:22:33:44:55&quot;. Is tha=
t the case?)<br>

</blockquote></div>
Yes. One case is a network that is generally NMS configured, and wants to u=
se unicast MAC addresses, but wants to allow the craft people to plug in a =
new linecard without talking to the NMS. In such circumstances the only aut=
o config would be teh MAC addresses.<br>

<br>
Stewart<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">
<br>
<br>
<br>
<br>
On Tue, Apr 2, 2013 at 9:10 AM, Stewart Bryant &lt;<a href=3D"mailto:stbrya=
nt@cisco.com" target=3D"_blank">stbryant@cisco.com</a> &lt;mailto:<a href=
=3D"mailto:stbryant@cisco.com" target=3D"_blank">stbryant@cisco.com</a>&gt;=
&gt; wrote:<br>

<br>
=A0 =A0 Resending due to Richards change of address.<br>
<br>
=A0 =A0 Stewart<br>
<br>
<br>
=A0 =A0 On 11/02/2013 23:45, Richard Barnes wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div class=3D"im">
=A0 =A0 I have been selected as the General Area Review Team (Gen-ART)<br>
=A0 =A0 reviewer for this draft (for background on Gen-ART,<br>
=A0 =A0 pleaseseehttp://<a href=3D"http://www.alvestrand.no/ietf/gen/art/ge=
n-art-FAQ.html" target=3D"_blank">www.<u></u>alvestrand.no/ietf/gen/art/<u>=
</u>gen-art-FAQ.html</a><br></div>
=A0 =A0 &lt;<a href=3D"http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.ht=
ml" target=3D"_blank">http://www.alvestrand.no/<u></u>ietf/gen/art/gen-art-=
FAQ.html</a>&gt;<u></u>). Please<div><div class=3D"h5"><br>
=A0 =A0 wait for direction from your document shepherd or AD before<br>
=A0 =A0 posting a new version of the draft. Document:<br>
=A0 =A0 draft-ietf-mpls-tp-ethernet-<br>
=A0 =A0 addressing-05<br>
=A0 =A0 Reviewer: Richard Barnes<br>
=A0 =A0 Review Date: 2013-02-11<br>
=A0 =A0 IETF LC End Date: 2013-02-18<br>
=A0 =A0 IESG Telechat date: TBD<br>
<br>
=A0 =A0 Summary: =A0Ready, with a couple of minor questions / clarification=
s.<br>
<br>
=A0 =A0 Comment:<br>
<br>
=A0 =A0 The document is mostly very clearly written. =A0(Thanks!) =A0It wou=
ld have helped me understand if it could have been clarified up front that =
the mechanism in this document is intended for &quot;pure Ethernet&quot; MP=
LS-TP (without assumptions about layer 3+). =A0The current introduction say=
s as much, but in a negative way, in terms of ARP or ND not being available=
.<br>

<br>
=A0 =A0 I have some minor unease about the distinction that this document m=
akes between point-to-point and multipoint links. =A0The document correctly=
 notes that a point-to-point link might become multipoint without either en=
d being aware. =A0I would have thought this would argue for using GAP in al=
l cases, but instead the document carries on with addressing the point-to-p=
oint case separately..<br>

<br>
</div></div></blockquote><div><div class=3D"h5">
=A0 =A0 Richard<br>
<br>
=A0 =A0 It is always difficult when writing a simple draft dealing with a<b=
r>
=A0 =A0 small<br>
=A0 =A0 component of a larger technology to know how much tutorial to inclu=
de,<br>
=A0 =A0 but I believe the point about operation in the absence IP would be<=
br>
=A0 =A0 well known<br>
=A0 =A0 to anyone implementing this. In particular we assume that anyone<br=
>
=A0 =A0 implementing the draft would have read the required references call=
ed<br>
=A0 =A0 up in the first paragraph of the Introduction:<br>
<br>
<br>
=A0 =A0 &quot; The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of=
<br>
=A0 =A0 protocol<br>
=A0 =A0 functions that meet the requirements [RFC5654] for the application =
of<br>
=A0 =A0 MPLS to the construction and operation of packet-switched transport=
<br>
=A0 =A0 networks. The MPLS-TP data plane consists of those MPLS-TP function=
s<br>
=A0 =A0 concerned with the encapsulation and forwarding of MPLS-TP packets<=
br>
=A0 =A0 and is described in [RFC5960].&quot;<br>
<br>
=A0 =A0 RFC5654 says:<br>
<br>
=A0 =A0 &quot; =A0 36 =A0It MUST be possible to operate and configure the M=
PLS-TP data<br>
=A0 =A0 =A0 =A0 =A0 =A0 plane without any IP forwarding capability in the M=
PLS-TP data<br>
=A0 =A0 =A0 =A0 =A0 =A0 plane. =A0That is, the data plane only operates on =
the MPLS label.&quot;<br>
=A0 =A0 Thus I think that the text is complete as it stands and requires no=
<br>
=A0 =A0 further clarification for anyone that needs to consider the technol=
ogy<br>
=A0 =A0 it describes.<br>
<br>
<br>
=A0 =A0 With regard to your second point, the issue that we are have, is th=
at<br>
=A0 =A0 there are a number of deployment scenarios where the operator knows=
<br>
=A0 =A0 that the link is Pt-Pt, and there is a reluctance by that community=
 to<br>
=A0 =A0 use anything other than NMS configuration. That has lead them<br>
=A0 =A0 to use Ethernet broadcast addressing which allows the crafts to<br>
=A0 =A0 change h/w without the need for reconfiguration by the NMS.<br>
=A0 =A0 Against that background moving them onto the use of a Ethernet m/c<=
br>
=A0 =A0 address is a step forward. To require using the GAP to that<br>
=A0 =A0 community would illustrate that the IETF is out of touch with<br>
=A0 =A0 their needs and methods of network operation.<br>
<br>
=A0 =A0 Hopefully this additional background, which I believe is well<br>
=A0 =A0 known to the MPLS-TP community to which this draft is directed,<br>
=A0 =A0 satisfies your concern on the latter point.<br>
<br>
=A0 =A0 - Stewart<br>
<br>
<br>
<br>
=A0 =A0 -- =A0 =A0 For corporate legal information go to:<br>
<br>
=A0 =A0 <a href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/=
index.html" target=3D"_blank">http://www.cisco.com/web/<u></u>about/doing_b=
usiness/legal/<u></u>cri/index.html</a><br>
<br>
<br>
</div></div></blockquote><div class=3D"HOEnZb"><div class=3D"h5">
<br>
<br>
-- <br>
For corporate legal information go to:<br>
<br>
<a href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/index.ht=
ml" target=3D"_blank">http://www.cisco.com/web/<u></u>about/doing_business/=
legal/<u></u>cri/index.html</a><br>
<br>
</div></div></blockquote></div><br></div>

--f46d044794f36f602c04d9de853d--

From turners@ieca.com  Mon Apr  8 13:22:47 2013
Return-Path: <turners@ieca.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C90021F8C45 for <gen-art@ietfa.amsl.com>; Mon,  8 Apr 2013 13:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.225
X-Spam-Level: 
X-Spam-Status: No, score=-102.225 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 yrxsg0r4icZM for <gen-art@ietfa.amsl.com>; Mon,  8 Apr 2013 13:22:42 -0700 (PDT)
Received: from gateway05.websitewelcome.com (gateway05.websitewelcome.com [69.93.35.13]) by ietfa.amsl.com (Postfix) with ESMTP id 3B32321F888C for <gen-art@ietf.org>; Mon,  8 Apr 2013 13:22:41 -0700 (PDT)
Received: by gateway05.websitewelcome.com (Postfix, from userid 5007) id 6445EEB4ADDD6; Mon,  8 Apr 2013 15:22:38 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway05.websitewelcome.com (Postfix) with ESMTP id 204FDEB4ADC5A for <gen-art@ietf.org>; Mon,  8 Apr 2013 15:22:38 -0500 (CDT)
Received: from [108.45.16.214] (port=53217 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1UPIaL-0002vt-Lh; Mon, 08 Apr 2013 15:22:37 -0500
Message-ID: <5163270C.20300@ieca.com>
Date: Mon, 08 Apr 2013 16:22:36 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Piyush Jain <piyush@ditenity.com>
References: <003e01ce3077$5b6329f0$12297dd0$@ditenity.com> <20130403160532.EB4FD1A68A@ld9781.wdf.sap.corp> <00a401ce3092$0a1415d0$1e3c4170$@ditenity.com>
In-Reply-To: <00a401ce3092$0a1415d0$1e3c4170$@ditenity.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (thunderfish.local) [108.45.16.214]:53217
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 6
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: ambarish@gmail.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, sts@aaa-sec.com, pkix@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2013 20:22:47 -0000

Piyush,

(David's on the "to:" line because the text in question showed up as a 
result of the gen-art review and it's now in -16)

I've been following this thread trying to figure out what if anything 
needs to be changed to address your concerns in -17.  (Note the thread 
forked later, but I'm addressing the "times" issue in another thread.)

The sentence in questions was added to address the gen-art review is the 
following (it's in a "note" paragraph and there's actually more to it):

   The "revoked" status is still optional in this context in
   order to maintain backwards compatibility with deployments
   of RFC 2560.

1) The first bit I'd like to discuss is this part of your concern:

   And it gives the impression that best course of action
   for 2560bis responders is to start issuing revoked for
   "not-issued", which is far from the originally stated
   goal to provide a way for CAs to be able to return
   revoked for such serial numbers.

and:

   I believe that Stefan is trying to convey that requiring
   servers to return revoked in this context will make them
   non-compliant with 2560 and 5019 as opposed to breaking
   interoperability with legacy clients.

I honestly don't see how you get to your impression, because the 2119 
language about when a responder might used revoked for not-issued is:

  This state MAY also be returned if the associated
  CA has no record of ever having issued a certificate with the
  certificate serial number in the request, using any current or
  previous issuing key (referred to as a "non-issued" certificate in
  this document).

MAY being the operable word here.  That's clear to implementers because 
if you read 2119 for MAY it says:  This word, or the adjective 
"OPTIONAL", mean that an item is truly optional.  One vendor may choose 
to include the item because a particular marketplace requires it or 
because the vendor feels that it enhances the product while another 
vendor may omit the same item. ...

For me this seems clear because the 2119 language trumps any note.

Even Stefan's response to David a couple of days earlier than when you 
posted this concerns includes:

   In theory we could possibly say that responding revoked
   is optional, but if you choose between revoked and unknown
   then you SHOULD favour revoked over unknown. But such nested
   requirements just feels bad and impossible to test compliance
   against. I'd much rather just leave it optional.

I'm not sure what else could be added to alliveate your concern on this 
point.  Maybe this one got over taken by events?

2) The second bit of your concern is that this is not an accurate 
characterization of the WG's rationale for the choices made.  This 
concern is easier to evaluate and I agree that it is important to 
capture the actual rationale.  I think you've suggested that the following:

   "maintain backwards compatibility with deployments of RFC 2560"

be replaced with:

   "maintain compliance with RFC 2560 and RFC 5019"

Using the word "compliance" might set of an entirely new debate. 
Servers/clients can claim compliance if they want to but I'm not sure 
that the primary goal was for a document to claim compliance with 
another set of RFCs.  These drafts for interoperability and that would 
lead me to compatibility and not conformance.

spt

On 4/3/13 1:38 PM, Piyush Jain wrote:
>> No, it does not make any sense at all.  An error code is unsigned and can
> be
>> easily inserted into the communication by an attacker.
>
> [Piyush] Funny that you make this argument. How does returning a signed
> revoked address this? Attacker can still replace signed revoked with an
> UNSIGNED TRY_LATER.
>
>> These kinds of argument are based on two very flawed premises:
>>
>>   (1) the premise that there exist only two possible states for a CA:
>>        (a) safe and pristine
>>        (b) full and thorough compromise of each and everything
> [Piyush] NIST has addressed RA compromise and CA key compromise separately
> so this is not true.
> And you have not listed what other breaches you are trying to address
> offering revoked for non-issued as the silver bullet for all those unknown
> security breaches.
>   You tendency to allude to vague problems to justify a particular solution,
> couple with a reluctance to engage in a discussion regarding the security
> implications continues to amuse me. List the other states and have a
> discussion around how this solution solves those problems.>
>>   (2) that a huge PKI (100k+ entities) can be nuked and
>>       re-personalized after a CA compromise at close to zero cost and
>>       within the blink of an eye
>
> and both premises exhibit a throrough cluelessness about security, risk
>> management and the real world.
>
> Let's get this right.
> Only possible benefit of revoked for non-issued exists when there are CA
> SIGNED certificates floating in the wild and CA has no clue that it has
> issued it and therefore cannot revoke it.
>
> Now, to say that clients are secure and CA can continue to operate if it
> issues revoked OCSP response for such certificate indicates cluelessness
> about security.
>
> Customers pay a lot of money for certificates for which the marginal cost of
> issuance is almost 0. CAs obligation is to make sure that they are secure
> and to address any breach securely.
> To say that customers will tolerate a CA security breach just because it
> issues revoked for non-issued and continues to publish CRLs that imply
> fraudulent certificates as good indicates cluelessness about risk management
> and real world.
>
>
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix
>

From piyush@ditenity.com  Mon Apr  8 14:59:44 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0743321F8CE2 for <gen-art@ietfa.amsl.com>; Mon,  8 Apr 2013 14:59:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.792
X-Spam-Level: 
X-Spam-Status: No, score=-2.792 tagged_above=-999 required=5 tests=[AWL=0.807,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 In7Ez5hQdV6Y for <gen-art@ietfa.amsl.com>; Mon,  8 Apr 2013 14:59:42 -0700 (PDT)
Received: from mail-ye0-f174.google.com (mail-ye0-f174.google.com [209.85.213.174]) by ietfa.amsl.com (Postfix) with ESMTP id B1A4921F8C04 for <gen-art@ietf.org>; Mon,  8 Apr 2013 14:59:42 -0700 (PDT)
Received: by mail-ye0-f174.google.com with SMTP id l2so975913yen.33 for <gen-art@ietf.org>; Mon, 08 Apr 2013 14:59:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language:x-gm-message-state; bh=8rnEkOggHBWhzA2tEg2mr72XPdJMgNB6H3ao8w4vbVk=; b=joNuFwgY9NIysJgM2bELQG6GCRVJnY+8b6SZAgUSO1xCuHg/Cg4TTp767yRIn+TohJ ecPoJgzJ++u/vNPhIEY66Xy0tsxTIp8pK6kIQVY1DsK/XXD/aYkNs9n9yjuY4rvpkKy2 9Xv8dguCYvvNMqnydrsCrcOlIWdV+lrah3b/xUG0M4qQScSEil9wxmnLCqdExRP7wcAd PZlzC+JNUMMzXZpKgcZ2YYCseS8apl6MijpdP+v/kaQw863NzNqrvSDeF2X4sDs5PfN1 /aodpg9556+/1ZhoTlrgKpR29OlDTWzkN059n29dBKU/I6Uhx8X6M+Ofez+5eA7W1A7R EWdQ==
X-Received: by 10.236.121.66 with SMTP id q42mr13866447yhh.48.1365458381977; Mon, 08 Apr 2013 14:59:41 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id f70sm39879962yhi.12.2013.04.08.14.59.39 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 08 Apr 2013 14:59:41 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: "'Sean Turner'" <turners@ieca.com>
References: <003e01ce3077$5b6329f0$12297dd0$@ditenity.com> <20130403160532.EB4FD1A68A@ld9781.wdf.sap.corp> <00a401ce3092$0a1415d0$1e3c4170$@ditenity.com> <5163270C.20300@ieca.com>
In-Reply-To: <5163270C.20300@ieca.com>
Date: Mon, 8 Apr 2013 14:59:27 -0700
Message-ID: <07af01ce34a4$582df1d0$0889d570$@ditenity.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_07B0_01CE3469.ABDFBBA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHHvIU0pEj95jqjILpXYwEgVOm34gLGPak8AXFeg0kBCCz4M5ivwB4A
Content-Language: en-us
X-Gm-Message-State: ALoCoQnJPFVjsDxA4vtap5TSDgWnw4dL7/21upo00hA111taFSxOi+kc6VQW2hXzaKmFJKs/jOhe
Cc: ambarish@gmail.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, sts@aaa-sec.com, pkix@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2013 21:59:44 -0000

This is a multipart message in MIME format.

------=_NextPart_000_07B0_01CE3469.ABDFBBA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Sean,

Thanks for your comments.
There are two points that I would like to cover separately. The first point
is a response to your comments below. The second point is a broader
objection to revoked for issued.

1) The text says - The "revoked" status is still optional in this context in
order to maintain backwards compatibility with deployments of RFC 2560.
This implies that making "revoked" status REQUIRED will break
interoperability between newer and older implementations. This is INCORRECT.

> Using the word "compliance" might set of an entirely new debate.
> Servers/clients can claim compliance if they want to but I'm not sure that
the
> primary goal was for a document to claim compliance with another set of
> RFCs.  
>These drafts for interoperability and that would lead me to
> compatibility and not conformance.
That is fair. I was just pointing at the intent of the author. If you make
"revoked" status REQUIRED it does not break compatibility of newer
implementations with older implementations, however it does break
conformance of older implementations with RFC 5019 and 2560.

2) Returning revoked for non-issued adds confusion without addressing any
real problem. "Allowing CAs to return revoked for non-issued" is a goal that
is vague and meaningless, given that CAs indicate issuance by signing the
certificate in question with their private key. If you question this basic
premise of x.509 that issuance is determined by signature, you should
question the signature on signed response as well. Who is to say that the
responder certificate that was used to sign a good response was issued by
the CA?

Henry nicely articulated the whole issue with this draft in his post
(attached). I second his view on not moving this draft forward.

-Piyush
> -----Original Message-----
> From: Sean Turner [mailto:turners@ieca.com]
> Sent: Monday, April 08, 2013 1:23 PM
> To: Piyush Jain
> Cc: ambarish@gmail.com; slava.galperin@gmail.com;
> cadams@eecs.uottawa.ca; 'Stefan Santesson'; 'Black, David'; sts@aaa-
> sec.com; pkix@ietf.org; gen-art@ietf.org
> Subject: Re: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
> 
> Piyush,
> 
> (David's on the "to:" line because the text in question showed up as a
result
> of the gen-art review and it's now in -16)
> 
> I've been following this thread trying to figure out what if anything
needs to
> be changed to address your concerns in -17.  (Note the thread forked
later,
> but I'm addressing the "times" issue in another thread.)
> 
> The sentence in questions was added to address the gen-art review is the
> following (it's in a "note" paragraph and there's actually more to it):
> 
>    The "revoked" status is still optional in this context in
>    order to maintain backwards compatibility with deployments
>    of RFC 2560.
> 
> 1) The first bit I'd like to discuss is this part of your concern:
> 
>    And it gives the impression that best course of action
>    for 2560bis responders is to start issuing revoked for
>    "not-issued", which is far from the originally stated
>    goal to provide a way for CAs to be able to return
>    revoked for such serial numbers.
> 
> and:
> 
>    I believe that Stefan is trying to convey that requiring
>    servers to return revoked in this context will make them
>    non-compliant with 2560 and 5019 as opposed to breaking
>    interoperability with legacy clients.
> 
> I honestly don't see how you get to your impression, because the 2119
> language about when a responder might used revoked for not-issued is:
> 
>   This state MAY also be returned if the associated
>   CA has no record of ever having issued a certificate with the
>   certificate serial number in the request, using any current or
>   previous issuing key (referred to as a "non-issued" certificate in
>   this document).
> 
> MAY being the operable word here.  That's clear to implementers because if
> you read 2119 for MAY it says:  This word, or the adjective "OPTIONAL",
> mean that an item is truly optional.  One vendor may choose to include the
> item because a particular marketplace requires it or because the vendor
feels
> that it enhances the product while another vendor may omit the same item.
> ...
> 
> For me this seems clear because the 2119 language trumps any note.
> 
> Even Stefan's response to David a couple of days earlier than when you
> posted this concerns includes:
> 
>    In theory we could possibly say that responding revoked
>    is optional, but if you choose between revoked and unknown
>    then you SHOULD favour revoked over unknown. But such nested
>    requirements just feels bad and impossible to test compliance
>    against. I'd much rather just leave it optional.
> 
> I'm not sure what else could be added to alliveate your concern on this
point.
> Maybe this one got over taken by events?
> 
> 2) The second bit of your concern is that this is not an accurate
> characterization of the WG's rationale for the choices made.  This concern
is
> easier to evaluate and I agree that it is important to capture the actual
> rationale.  I think you've suggested that the following:
> 
>    "maintain backwards compatibility with deployments of RFC 2560"
> 
> be replaced with:
> 
>    "maintain compliance with RFC 2560 and RFC 5019"
> 
> Using the word "compliance" might set of an entirely new debate.
> Servers/clients can claim compliance if they want to but I'm not sure that
the
> primary goal was for a document to claim compliance with another set of
> RFCs.  These drafts for interoperability and that would lead me to
> compatibility and not conformance.
> 
> spt
> 
> On 4/3/13 1:38 PM, Piyush Jain wrote:
> >> No, it does not make any sense at all.  An error code is unsigned and
> >> can
> > be
> >> easily inserted into the communication by an attacker.
> >
> > [Piyush] Funny that you make this argument. How does returning a
> > signed revoked address this? Attacker can still replace signed revoked
> > with an UNSIGNED TRY_LATER.
> >
> >> These kinds of argument are based on two very flawed premises:
> >>
> >>   (1) the premise that there exist only two possible states for a CA:
> >>        (a) safe and pristine
> >>        (b) full and thorough compromise of each and everything
> > [Piyush] NIST has addressed RA compromise and CA key compromise
> > separately so this is not true.
> > And you have not listed what other breaches you are trying to address
> > offering revoked for non-issued as the silver bullet for all those
> > unknown security breaches.
> >   You tendency to allude to vague problems to justify a particular
> > solution, couple with a reluctance to engage in a discussion regarding
> > the security implications continues to amuse me. List the other states
> > and have a discussion around how this solution solves those problems.>
> >>   (2) that a huge PKI (100k+ entities) can be nuked and
> >>       re-personalized after a CA compromise at close to zero cost and
> >>       within the blink of an eye
> >
> > and both premises exhibit a throrough cluelessness about security,
> > risk
> >> management and the real world.
> >
> > Let's get this right.
> > Only possible benefit of revoked for non-issued exists when there are
> > CA SIGNED certificates floating in the wild and CA has no clue that it
> > has issued it and therefore cannot revoke it.
> >
> > Now, to say that clients are secure and CA can continue to operate if
> > it issues revoked OCSP response for such certificate indicates
> > cluelessness about security.
> >
> > Customers pay a lot of money for certificates for which the marginal
> > cost of issuance is almost 0. CAs obligation is to make sure that they
> > are secure and to address any breach securely.
> > To say that customers will tolerate a CA security breach just because
> > it issues revoked for non-issued and continues to publish CRLs that
> > imply fraudulent certificates as good indicates cluelessness about
> > risk management and real world.
> >
> >
> > _______________________________________________
> > pkix mailing list
> > pkix@ietf.org
> > https://www.ietf.org/mailman/listinfo/pkix
> >

------=_NextPart_000_07B0_01CE3469.ABDFBBA0
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment

Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
 with ESMTP id A3FCB21F92FB; Mon,  8 Apr 2013 13:35:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com
 (Postfix) with ESMTP id 3372221F930E; Mon,  8 Apr 2013 13:35:08 -0700 (PDT)
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 bTdTjI9SGHIU; Mon,  8
 Apr 2013 13:35:06 -0700 (PDT)
Received: from laphotz.jpl.nasa.gov (laphotz.jpl.nasa.gov [128.149.133.44])
 (authenticated (0 bits)) by smtp.jpl.nasa.gov
 (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r38KZ3xp002425 (using
 TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Mon, 8 Apr 2013
 13:35:04 -0700
Received: from mail.jpl.nasa.gov (sentrion2.jpl.nasa.gov [128.149.139.106]) by
 ietfa.amsl.com (Postfix) with ESMTP id 3C5D921F92F4; Mon,  8 Apr 2013
 13:35:06 -0700 (PDT)
Received: by 10.49.110.33 with SMTP id hx1csp41138qeb; Mon, 8 Apr 2013
 13:35:10 -0700 (PDT)
Received: from mail.ietf.org (mail.ietf.org. [2001:1890:123a::1:1e]) by
 mx.google.com with ESMTP id wb8si296329pab.204.2013.04.08.13.35.09; Mon, 08
 Apr 2013 13:35:09 -0700 (PDT)
Return-Path: <pkix-bounces@ietf.org>
From: "Henry B. Hotz" <hotz@jpl.nasa.gov>
Sender: <pkix-bounces@ietf.org>
To: "Sean Turner" <turners@ieca.com>
Cc: <pkix@ietf.org>,
	<ietf@ietf.org>
References: <20130323065208.090391A65A@ld9781.wdf.sap.corp> <5162D56B.9060404@ieca.com>
In-Reply-To: <5162D56B.9060404@ieca.com>
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
Date: Mon, 8 Apr 2013 13:35:00 -0700
Message-ID: <34EC8B90-9952-4B8E-BFC2-7913F198453F@jpl.nasa.gov>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
Thread-Index: AQKR4daoZiTecUDX96ZN+L83E79W/AHMbHi3AmA5ems=

Actually, what I get from this and all the other discussions is that it's
unclear if the updated OCSP satisfies the "suitability for the intended
purpose" test.  Or at least it fails the KISS principle w.r.t. that.

Rephrasing:  an OCSP client should be able to tell from an OCSP response if:
a) the subject cert is on the CAs white list, b) the subject cert is on the
CAs black list, c) the subject cert is not on either list, or finally d) the
OCSP server is obsolete, and doesn't support making those distinctions.
It's not trivial to see how to parse 2560bis responses w.r.t. those cases,
therefore it's highly likely that computational complexity will prevent us
from doing so.  Even if that's not actually the case, then implementor
misunderstandings will prevent us from doing so in practice.

Therefore I vote against moving this draft forward.  I just don't see the
point.

If someone were to write an informational RFC which explained how to
determine which of the 4 cases an OCSP response fell into, AND if said RFC
also convinced me that the decision process was easy to understand, THEN I
would change my vote.  Obviously an appendix in 2560bis would serve just as
well.
_______________________________________________
pkix mailing list
pkix@ietf.org
https://www.ietf.org/mailman/listinfo/pkix

------=_NextPart_000_07B0_01CE3469.ABDFBBA0--


From turners@ieca.com  Mon Apr  8 19:59:31 2013
Return-Path: <turners@ieca.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21F0A21F8EAA for <gen-art@ietfa.amsl.com>; Mon,  8 Apr 2013 19:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.315
X-Spam-Level: 
X-Spam-Status: No, score=-102.315 tagged_above=-999 required=5 tests=[AWL=0.284, 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 hGerUVq+mIwa for <gen-art@ietfa.amsl.com>; Mon,  8 Apr 2013 19:59:30 -0700 (PDT)
Received: from gateway04.websitewelcome.com (gateway04.websitewelcome.com [64.5.50.5]) by ietfa.amsl.com (Postfix) with ESMTP id CDFCA21F8E96 for <gen-art@ietf.org>; Mon,  8 Apr 2013 19:59:29 -0700 (PDT)
Received: by gateway04.websitewelcome.com (Postfix, from userid 5007) id 64805DB637965; Mon,  8 Apr 2013 21:59:21 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway04.websitewelcome.com (Postfix) with ESMTP id 56CCDDB637914 for <gen-art@ietf.org>; Mon,  8 Apr 2013 21:59:21 -0500 (CDT)
Received: from [108.45.16.214] (port=55153 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1UPOmO-0005DI-V2; Mon, 08 Apr 2013 21:59:29 -0500
Message-ID: <5163840F.2030508@ieca.com>
Date: Mon, 08 Apr 2013 22:59:27 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Piyush Jain <piyush@ditenity.com>
References: <003e01ce3077$5b6329f0$12297dd0$@ditenity.com> <20130403160532.EB4FD1A68A@ld9781.wdf.sap.corp> <00a401ce3092$0a1415d0$1e3c4170$@ditenity.com> <5163270C.20300@ieca.com> <07af01ce34a4$582df1d0$0889d570$@ditenity.com>
In-Reply-To: <07af01ce34a4$582df1d0$0889d570$@ditenity.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (thunderfish.local) [108.45.16.214]:55153
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 2
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: ambarish@gmail.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, sts@aaa-sec.com, pkix@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 02:59:31 -0000

On 4/8/13 5:59 PM, Piyush Jain wrote:
> Sean,
>
> Thanks for your comments.
> There are two points that I would like to cover separately. The first point
> is a response to your comments below. The second point is a broader
> objection to revoked for issued.
>
> 1) The text says - The "revoked" status is still optional in this context in
> order to maintain backwards compatibility with deployments of RFC 2560.
> This implies that making "revoked" status REQUIRED will break
> interoperability between newer and older implementations. This is INCORRECT.
>
>> Using the word "compliance" might set of an entirely new debate.
>> Servers/clients can claim compliance if they want to but I'm not sure that
> the
>> primary goal was for a document to claim compliance with another set of
>> RFCs.
>> These drafts for interoperability and that would lead me to
>> compatibility and not conformance.
> That is fair. I was just pointing at the intent of the author. If you make
> "revoked" status REQUIRED it does not break compatibility of newer
> implementations with older implementations, however it does break
> conformance of older implementations with RFC 5019 and 2560.
>
> 2) Returning revoked for non-issued adds confusion without addressing any
> real problem. "Allowing CAs to return revoked for non-issued" is a goal that
> is vague and meaningless, given that CAs indicate issuance by signing the
> certificate in question with their private key. If you question this basic
> premise of x.509 that issuance is determined by signature, you should
> question the signature on signed response as well. Who is to say that the
> responder certificate that was used to sign a good response was issued by
> the CA?
>
> Henry nicely articulated the whole issue with this draft in his post
> (attached). I second his view on not moving this draft forward.

I went back and looked at the WG poll about this issue that you and lot 
of other people participated in 
(https://www.ietf.org/mail-archive/web/pkix/current/msg31906.html).  The 
WG's rough consensus was to allow "revoked" to be used for non-issued 
certificates with the caveat thrown in by Paul Hoffman that the meaning 
of "revoked" be clear about what it now means.  I've not seen anything 
that would make me want to throw this draft back to the WG to revisit 
that consensus.

spt

> -Piyush
>> -----Original Message-----
>> From: Sean Turner [mailto:turners@ieca.com]
>> Sent: Monday, April 08, 2013 1:23 PM
>> To: Piyush Jain
>> Cc: ambarish@gmail.com; slava.galperin@gmail.com;
>> cadams@eecs.uottawa.ca; 'Stefan Santesson'; 'Black, David'; sts@aaa-
>> sec.com; pkix@ietf.org; gen-art@ietf.org
>> Subject: Re: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
>>
>> Piyush,
>>
>> (David's on the "to:" line because the text in question showed up as a
> result
>> of the gen-art review and it's now in -16)
>>
>> I've been following this thread trying to figure out what if anything
> needs to
>> be changed to address your concerns in -17.  (Note the thread forked
> later,
>> but I'm addressing the "times" issue in another thread.)
>>
>> The sentence in questions was added to address the gen-art review is the
>> following (it's in a "note" paragraph and there's actually more to it):
>>
>>     The "revoked" status is still optional in this context in
>>     order to maintain backwards compatibility with deployments
>>     of RFC 2560.
>>
>> 1) The first bit I'd like to discuss is this part of your concern:
>>
>>     And it gives the impression that best course of action
>>     for 2560bis responders is to start issuing revoked for
>>     "not-issued", which is far from the originally stated
>>     goal to provide a way for CAs to be able to return
>>     revoked for such serial numbers.
>>
>> and:
>>
>>     I believe that Stefan is trying to convey that requiring
>>     servers to return revoked in this context will make them
>>     non-compliant with 2560 and 5019 as opposed to breaking
>>     interoperability with legacy clients.
>>
>> I honestly don't see how you get to your impression, because the 2119
>> language about when a responder might used revoked for not-issued is:
>>
>>    This state MAY also be returned if the associated
>>    CA has no record of ever having issued a certificate with the
>>    certificate serial number in the request, using any current or
>>    previous issuing key (referred to as a "non-issued" certificate in
>>    this document).
>>
>> MAY being the operable word here.  That's clear to implementers because if
>> you read 2119 for MAY it says:  This word, or the adjective "OPTIONAL",
>> mean that an item is truly optional.  One vendor may choose to include the
>> item because a particular marketplace requires it or because the vendor
> feels
>> that it enhances the product while another vendor may omit the same item.
>> ...
>>
>> For me this seems clear because the 2119 language trumps any note.
>>
>> Even Stefan's response to David a couple of days earlier than when you
>> posted this concerns includes:
>>
>>     In theory we could possibly say that responding revoked
>>     is optional, but if you choose between revoked and unknown
>>     then you SHOULD favour revoked over unknown. But such nested
>>     requirements just feels bad and impossible to test compliance
>>     against. I'd much rather just leave it optional.
>>
>> I'm not sure what else could be added to alliveate your concern on this
> point.
>> Maybe this one got over taken by events?
>>
>> 2) The second bit of your concern is that this is not an accurate
>> characterization of the WG's rationale for the choices made.  This concern
> is
>> easier to evaluate and I agree that it is important to capture the actual
>> rationale.  I think you've suggested that the following:
>>
>>     "maintain backwards compatibility with deployments of RFC 2560"
>>
>> be replaced with:
>>
>>     "maintain compliance with RFC 2560 and RFC 5019"
>>
>> Using the word "compliance" might set of an entirely new debate.
>> Servers/clients can claim compliance if they want to but I'm not sure that
> the
>> primary goal was for a document to claim compliance with another set of
>> RFCs.  These drafts for interoperability and that would lead me to
>> compatibility and not conformance.
>>
>> spt
>>
>> On 4/3/13 1:38 PM, Piyush Jain wrote:
>>>> No, it does not make any sense at all.  An error code is unsigned and
>>>> can
>>> be
>>>> easily inserted into the communication by an attacker.
>>>
>>> [Piyush] Funny that you make this argument. How does returning a
>>> signed revoked address this? Attacker can still replace signed revoked
>>> with an UNSIGNED TRY_LATER.
>>>
>>>> These kinds of argument are based on two very flawed premises:
>>>>
>>>>    (1) the premise that there exist only two possible states for a CA:
>>>>         (a) safe and pristine
>>>>         (b) full and thorough compromise of each and everything
>>> [Piyush] NIST has addressed RA compromise and CA key compromise
>>> separately so this is not true.
>>> And you have not listed what other breaches you are trying to address
>>> offering revoked for non-issued as the silver bullet for all those
>>> unknown security breaches.
>>>    You tendency to allude to vague problems to justify a particular
>>> solution, couple with a reluctance to engage in a discussion regarding
>>> the security implications continues to amuse me. List the other states
>>> and have a discussion around how this solution solves those problems.>
>>>>    (2) that a huge PKI (100k+ entities) can be nuked and
>>>>        re-personalized after a CA compromise at close to zero cost and
>>>>        within the blink of an eye
>>>
>>> and both premises exhibit a throrough cluelessness about security,
>>> risk
>>>> management and the real world.
>>>
>>> Let's get this right.
>>> Only possible benefit of revoked for non-issued exists when there are
>>> CA SIGNED certificates floating in the wild and CA has no clue that it
>>> has issued it and therefore cannot revoke it.
>>>
>>> Now, to say that clients are secure and CA can continue to operate if
>>> it issues revoked OCSP response for such certificate indicates
>>> cluelessness about security.
>>>
>>> Customers pay a lot of money for certificates for which the marginal
>>> cost of issuance is almost 0. CAs obligation is to make sure that they
>>> are secure and to address any breach securely.
>>> To say that customers will tolerate a CA security breach just because
>>> it issues revoked for non-issued and continues to publish CRLs that
>>> imply fraudulent certificates as good indicates cluelessness about
>>> risk management and real world.
>>>
>>>
>>> _______________________________________________
>>> pkix mailing list
>>> pkix@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pkix
>>>

From piyush@ditenity.com  Mon Apr  8 23:03:12 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF17021F8F6E for <gen-art@ietfa.amsl.com>; Mon,  8 Apr 2013 23:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.783
X-Spam-Level: 
X-Spam-Status: No, score=-2.783 tagged_above=-999 required=5 tests=[AWL=0.816,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 TEwcgTSJG7+d for <gen-art@ietfa.amsl.com>; Mon,  8 Apr 2013 23:03:12 -0700 (PDT)
Received: from mail-ye0-f179.google.com (mail-ye0-f179.google.com [209.85.213.179]) by ietfa.amsl.com (Postfix) with ESMTP id 165CC21F8C16 for <gen-art@ietf.org>; Mon,  8 Apr 2013 23:03:11 -0700 (PDT)
Received: by mail-ye0-f179.google.com with SMTP id q7so1004625yen.10 for <gen-art@ietf.org>; Mon, 08 Apr 2013 23:03:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language:x-gm-message-state; bh=0zQSvkz/c8H1nqvXhxLERC/TcDswH3zjvS/1nZHaxC4=; b=T1DjqvkXFClLBFVTpN82z/gVRb8/r64MhV5YGJmnPrvtrdsLmMbzXITdiLFb1vI3aO 5J0jQnBEU6wEqCWmR79y60pe1tC1AYwkklCeL/QFkGUXWQlMP00qj2y3wC+YvTEbeLu2 Mj6Abbdg7QjoR9T8W5vMwrNiFfQ2ARo4t2Aqh4DhyBLklXTOno90Q2FcB7yJpd7uUFvD /MsM38D0u0LcOs3tu0voDWNKrQGu3MDt3/3od44UWIbRmVhWYCTMqT+6nF1PqbmW7Vo1 XdB+vdAou6UZDlXbPo68qRp7oOVI+AednWsqZ8pC4eZ2D6syRCe8nY25Fpt23m9k18FR xJcw==
X-Received: by 10.236.162.39 with SMTP id x27mr14488391yhk.50.1365487391545; Mon, 08 Apr 2013 23:03:11 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id t27sm41732077yhm.20.2013.04.08.23.03.09 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 08 Apr 2013 23:03:10 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: "'Sean Turner'" <turners@ieca.com>
References: <003e01ce3077$5b6329f0$12297dd0$@ditenity.com> <20130403160532.EB4FD1A68A@ld9781.wdf.sap.corp> <00a401ce3092$0a1415d0$1e3c4170$@ditenity.com> <5163270C.20300@ieca.com> <07af01ce34a4$582df1d0$0889d570$@ditenity.com> <5163840F.2030508@ieca.com>
In-Reply-To: <5163840F.2030508@ieca.com>
Date: Mon, 8 Apr 2013 23:02:57 -0700
Message-ID: <083601ce34e7$e3dcef40$ab96cdc0$@ditenity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHHvIU0pEj95jqjILpXYwEgVOm34gLGPak8AXFeg0kBCCz4MwNWbgjOAWN27bOYinncUA==
Content-Language: en-us
X-Gm-Message-State: ALoCoQmSOlprG2AtdPXMZoYic/xItstLIQlbcNZ7VN0zlYbdFuVRGj8VTNNNP18pv3vKzA1DyneB
Cc: ambarish@gmail.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, sts@aaa-sec.com, pkix@ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 06:03:12 -0000

> I went back and looked at the WG poll about this issue that you and lot of
> other people participated in (https://www.ietf.org/mail-
> archive/web/pkix/current/msg31906.html).  The WG's rough consensus was
> to allow "revoked" to be used for non-issued certificates with the caveat
> thrown in by Paul Hoffman that the meaning of "revoked" be clear about
> what it now means.  I've not seen anything that would make me want to
> throw this draft back to the WG to revisit that consensus.
> 

I believe that the straw poll consensus was that revoked will be overloaded
to convey non-issued status to the clients.
The deviation from that consensus is that in such cases, the current draft
prohibits clients to interpret the certificate as non-issued, and requires
them to interpret it as issued and revoked by the CA. And this is necessary
to circumvent the responder trust issue for CA delegated responders if they
return extended revoked indicating non-issuance.
Please see http://www.ietf.org/mail-archive/web/pkix/current/msg32336.html.

This is an important distinction because from client's point of view
non-issued response for a CA signed certificate is much more severe than a
revoked response and is indicative of a CA/RA compromise.
The reason I'm raising this at LC is because there were a few WG members who
acknowledged this issue and there was no consensus (other than Stefan's
response in the post linked above) on how this should be handled.

I guess it would be okay if you and David make the determination that this
issue is not worth debating anymore but I would surely have appreciated
hearing the opinions of a few others. 

Best
Piyush




From peter@akayla.com  Tue Apr  9 01:12:50 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30B6821F8521; Tue,  9 Apr 2013 01:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=-0.400,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 PXWzDy4zk0zN; Tue,  9 Apr 2013 01:12:49 -0700 (PDT)
Received: from p3plsmtpa08-05.prod.phx3.secureserver.net (p3plsmtpa08-05.prod.phx3.secureserver.net [173.201.193.106]) by ietfa.amsl.com (Postfix) with ESMTP id 25FCF21F8967; Tue,  9 Apr 2013 01:12:48 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa08-05.prod.phx3.secureserver.net with  id MkCm1l00Q1huGat01kCmbj; Tue, 09 Apr 2013 01:12:48 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
Date: Tue, 9 Apr 2013 01:12:49 -0700
Message-ID: <054201ce34fa$0746ec80$15d4c580$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac409G6BqoWAcV+eTe6M/+710JRlsQ==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 08:12: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 resolve these comments along with any other Last Call comments you
may receive. 

Document: draft-ietf-pcp-upnp-igd-interworking-07
Reviewer: Peter Yee
Review Date: Apr-08-2013
IETF LC End Date: Apr-08-2013
IESG Telechat date: Unknown

Summary: This draft is on the right track but has open issues, described in
the review. [Ready with issues]

This is a well-written draft describing how Universal Plug-and-Play Internet
Gateway Devices interwork with NAT devices that use the Port Control
Protocol.  My review is mostly nits with otherwise minor issues.  I have no
problems with the general concept and enjoyed reading a clearly articulated
concept.

Major Issues:

None.

Minor Issues:

Section 4.1: is the mapping of the state variables between the UPnP IGD
function and the PCP Client function really straightforward such that it
does not need further description?  I'm asking if an implementor would
naturally gravitate to the correct use of the mapping without further
instructions.  Similar questions arise for Sections 4.2 and 4.3, although I
believe those are more straightforward mappings.

Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP error
other than a short-lifetime error, or in the case of a failed resend, any
PCP error at all.  The wording makes it seem like the short-lifetime errors
are somehow not PCP errors and is therefore confusing.  It also doesn't
explicitly deal with how many repeats should be done on a resend.  

Nits:

General: replace "re-send" with "resend".

Page 3, 1st paragraph, 2nd sentence: insert "a" before each occurrence of
UPnP.  

Page 4, section 3, 4th bullet: consider changing "in" to "on" or "over".

Page 4, 1st paragraph after the bullet items: bracket "for instance" with
commas.

Page 5, Figure 3: perhaps the "LAN Side" label could move a bit to the left
to give it better delineation from the "External Side" label?

Page 5, 1st paragraph after Figure 4, 2nd sentence: add a comma after "
[I-D.ietf-pcp-base]".

Page 5, 2nd paragraph after Figure 4: change "can not" to "cannot".

Page 9, section 5, 3rd paragraph: insert "the same way" or "the same" before
"as any PCP Client".

Page 9, section 5.1, 2nd paragraph: insert "whether" before "it should".

Page 9, section 5.1, 3rd paragraph: insert "the" before "requesting UPnP
Control Point".

Page 10, Section 5.3, 2nd paragraph, 1st sentence: consider changing
"retrieve" to "extract".

Page 11, 1st paragraph after bullet items, 2nd sentence: change "to" to
"than".

Page 11, Section 5.6: swap the order of "AddPortMapping()" and
"AddAnyPortMapping()" to match the order of the subsequent subsections.

Page 11, Section 5.6.1, 2nd paragraph, 2nd sentence: change "30s" to "30
seconds".

Page 13, 1st paragraph, 4th sentence: change "re-issue" to "issue"; change
"new requested" to "different requested".

Page 14, last paragraph: delete the comma after "4 times)".

Page 15, Section 5.7, 1st paragraph: append a comma after
"GetSpecificPortMappingEntry()".

Page 15, Section 5.7, 3rd paragraph, 3rd sentence: replace "60s" with "60
seconds".

Page 15, Section 5.7, 3rd paragraph, last sentence: insert "the" before
"error code"; change "enquried" to "queried".

Page 15, Section 5.8, 1st paragraph: insert ", respectively" before the
period.

Page 15, Section 5.8, 2nd paragraph, 2nd sentence: insert "the" before '"606
Action Not'.

Page 16, last paragraph, 2nd sentence: insert "the" before'"731
PortMappingNotFound'.

Page 19, 1st continuation paragraph, 1st sentence fragment: change "of" to
"in".

Page 19, 1st continuation paragraph, 1st full sentence: consider swapping
the positions of "renew" and "periodically" for readability.

Page 19, Section 5.10, 1st paragraph, 2nd sentence: I prefer "In particular"
to "Particularly" here.

Page 19, Section 5.10, 3rd paragraph, 3rd sentence: replace "signalled" with
"signaled".




From mohamed.boucadair@orange.com  Tue Apr  9 05:27:00 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C749621F8EDB; Tue,  9 Apr 2013 05:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level: 
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799, UNPARSEABLE_RELAY=0.001]
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 TKQeWyT+Iblb; Tue,  9 Apr 2013 05:27:00 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id E739221F8EB2; Tue,  9 Apr 2013 05:26:59 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 8BA4F2645B2; Tue,  9 Apr 2013 14:26:57 +0200 (CEST)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 5E41B4C015; Tue,  9 Apr 2013 14:26:57 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Tue, 9 Apr 2013 14:26:57 +0200
From: <mohamed.boucadair@orange.com>
To: Peter Yee <peter@akayla.com>, "draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org" <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
Date: Tue, 9 Apr 2013 14:26:55 +0200
Thread-Topic: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Thread-Index: Ac409G6BqoWAcV+eTe6M/+710JRlsQAJssnw
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr>
References: <054201ce34fa$0746ec80$15d4c580$@akayla.com>
In-Reply-To: <054201ce34fa$0746ec80$15d4c580$@akayla.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.25.85421
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 12:27:00 -0000

Dear Peter,

Thanks for the review.=20
Please see inline.

Cheers,
Med

>-----Message d'origine-----
>De=A0: Peter Yee [mailto:peter@akayla.com]
>Envoy=E9=A0: mardi 9 avril 2013 10:13
>=C0=A0: draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org
>Cc=A0: gen-art@ietf.org; ietf@ietf.org
>Objet=A0: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>
>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-pcp-upnp-igd-interworking-07
>Reviewer: Peter Yee
>Review Date: Apr-08-2013
>IETF LC End Date: Apr-08-2013
>IESG Telechat date: Unknown
>
>Summary: This draft is on the right track but has open issues, described i=
n
>the review. [Ready with issues]
>
>This is a well-written draft describing how Universal Plug-and-Play
>Internet
>Gateway Devices interwork with NAT devices that use the Port Control
>Protocol.  My review is mostly nits with otherwise minor issues.  I have n=
o
>problems with the general concept and enjoyed reading a clearly articulate=
d
>concept.

[Med] Thanks.

>
>Major Issues:
>
>None.
>
>Minor Issues:
>
>Section 4.1: is the mapping of the state variables between the UPnP IGD
>function and the PCP Client function really straightforward such that it
>does not need further description?  I'm asking if an implementor would
>naturally gravitate to the correct use of the mapping without further
>instructions.  Similar questions arise for Sections 4.2 and 4.3, although =
I
>believe those are more straightforward mappings.

[Med] I don't think further explanation is needed. Pointers to the appropri=
ate sections is included in Section 4.2 and Section 4.3. FWIW, there are al=
ready existing implementations of the IWF and no "complaint" was received f=
rom these implementers.

>
>Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP erro=
r
>other than a short-lifetime error, or in the case of a failed resend, any
>PCP error at all.  The wording makes it seem like the short-lifetime error=
s
>are somehow not PCP errors and is therefore confusing.  It also doesn't
>explicitly deal with how many repeats should be done on a resend.

[Med] The basic behavior is to relay the received error to the UPnP CP. For=
 the short-lifetime errors, the IWF may decide to resend the request and no=
t relay those errors immediately to the UPnP CP. The number of repeats is n=
ot specified here as it can be implementation-specific.=20


>Nits:

[Med] Fixed.=20

>
>General: replace "re-send" with "resend".
>
>Page 3, 1st paragraph, 2nd sentence: insert "a" before each occurrence of
>UPnP.
>
>Page 4, section 3, 4th bullet: consider changing "in" to "on" or "over".
>
>Page 4, 1st paragraph after the bullet items: bracket "for instance" with
>commas.
>
>Page 5, Figure 3: perhaps the "LAN Side" label could move a bit to the lef=
t
>to give it better delineation from the "External Side" label?
>
>Page 5, 1st paragraph after Figure 4, 2nd sentence: add a comma after "
>[I-D.ietf-pcp-base]".
>
>Page 5, 2nd paragraph after Figure 4: change "can not" to "cannot".
>
>Page 9, section 5, 3rd paragraph: insert "the same way" or "the same"
>before
>"as any PCP Client".
>
>Page 9, section 5.1, 2nd paragraph: insert "whether" before "it should".
>
>Page 9, section 5.1, 3rd paragraph: insert "the" before "requesting UPnP
>Control Point".
>
>Page 10, Section 5.3, 2nd paragraph, 1st sentence: consider changing
>"retrieve" to "extract".
>
>Page 11, 1st paragraph after bullet items, 2nd sentence: change "to" to
>"than".
>
>Page 11, Section 5.6: swap the order of "AddPortMapping()" and
>"AddAnyPortMapping()" to match the order of the subsequent subsections.
>
>Page 11, Section 5.6.1, 2nd paragraph, 2nd sentence: change "30s" to "30
>seconds".
>
>Page 13, 1st paragraph, 4th sentence: change "re-issue" to "issue"; change
>"new requested" to "different requested".
>
>Page 14, last paragraph: delete the comma after "4 times)".
>
>Page 15, Section 5.7, 1st paragraph: append a comma after
>"GetSpecificPortMappingEntry()".
>
>Page 15, Section 5.7, 3rd paragraph, 3rd sentence: replace "60s" with "60
>seconds".
>
>Page 15, Section 5.7, 3rd paragraph, last sentence: insert "the" before
>"error code"; change "enquried" to "queried".
>
>Page 15, Section 5.8, 1st paragraph: insert ", respectively" before the
>period.
>
>Page 15, Section 5.8, 2nd paragraph, 2nd sentence: insert "the" before
>'"606
>Action Not'.
>
>Page 16, last paragraph, 2nd sentence: insert "the" before'"731
>PortMappingNotFound'.
>
>Page 19, 1st continuation paragraph, 1st sentence fragment: change "of" to
>"in".
>
>Page 19, 1st continuation paragraph, 1st full sentence: consider swapping
>the positions of "renew" and "periodically" for readability.
>
>Page 19, Section 5.10, 1st paragraph, 2nd sentence: I prefer "In
>particular"
>to "Particularly" here.
>
>Page 19, Section 5.10, 3rd paragraph, 3rd sentence: replace "signalled"
>with
>"signaled".
>
>


From elwynd@dial.pipex.com  Tue Apr  9 05:49:14 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCF1D21F849C for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 05:49:14 -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 Y-yugKT0vFLp for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 05:49:14 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 3D58021F8496 for <gen-art@ietf.org>; Tue,  9 Apr 2013 05:49:14 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1UPXyy-0002hb-N4; Tue, 09 Apr 2013 13:49:10 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Tue, 09 Apr 2013 13:44:15 +0100
Message-Id: <1365511455.5273.8789.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: draft-ietf-tls-multiple-cert-status-extension.all@tools.ietf.org
Subject: [Gen-art] Gen-art telechat review: draft-ietf-tls-multiple-cert-status-extension-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 12:49:14 -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-tls-multiple-cert-status-extension-06.txt
Reviewer: Elwyn Davies
Review Date: 07 April 2013
IETF LC End Date:
IESG Telechat date: 11 April 2013

Summary: Ready for the IESG

Issues identified in last call review have been resolved.  Thanks.




From david.black@emc.com  Tue Apr  9 06:36:45 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9121621F8D92; Tue,  9 Apr 2013 06:36:45 -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 zvD5TmSb+UQ3; Tue,  9 Apr 2013 06:36:44 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0A90B21F8D00; Tue,  9 Apr 2013 06:36:43 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r39DaS1l028219 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Apr 2013 09:36:28 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Tue, 9 Apr 2013 09:36:13 -0400
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r39DYpxh009795; Tue, 9 Apr 2013 09:36:10 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Tue, 9 Apr 2013 09:35:25 -0400
From: "Black, David" <david.black@emc.com>
To: Piyush Jain <piyush@ditenity.com>, "'Sean Turner'" <turners@ieca.com>
Date: Tue, 9 Apr 2013 09:35:24 -0400
Thread-Topic: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
Thread-Index: AQHHvIU0pEj95jqjILpXYwEgVOm34gLGPak8AXFeg0kBCCz4MwNWbgjOAWN27bOYinncUIAAg2SQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293E22D3E@MX15A.corp.emc.com>
References: <003e01ce3077$5b6329f0$12297dd0$@ditenity.com> <20130403160532.EB4FD1A68A@ld9781.wdf.sap.corp> <00a401ce3092$0a1415d0$1e3c4170$@ditenity.com> <5163270C.20300@ieca.com> <07af01ce34a4$582df1d0$0889d570$@ditenity.com> <5163840F.2030508@ieca.com> <083601ce34e7$e3dcef40$ab96cdc0$@ditenity.com>
In-Reply-To: <083601ce34e7$e3dcef40$ab96cdc0$@ditenity.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ambarish@gmail.com" <ambarish@gmail.com>, "slava.galperin@gmail.com" <slava.galperin@gmail.com>, "cadams@eecs.uottawa.ca" <cadams@eecs.uottawa.ca>, "gen-art@ietf.org" <gen-art@ietf.org>, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, "sts@aaa-sec.com" <sts@aaa-sec.com>, "pkix@ietf.org" <pkix@ietf.org>
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 13:36:45 -0000

> I guess it would be okay if you and David make the determination that thi=
s
> issue is not worth debating anymore but I would surely have appreciated
> hearing the opinions of a few others.

I'm not sure how much of a say I have in that determination - Sean (as AD)
is absolutely free to acknowledge my input and ignore it ;-).

> The deviation from that consensus is that in such cases, the current draf=
t
> prohibits clients to interpret the certificate as non-issued, and require=
s
> them to interpret it as issued and revoked by the CA. And this is necessa=
ry
> to circumvent the responder trust issue for CA delegated responders if th=
ey
> return extended revoked indicating non-issuance.
> Please see http://www.ietf.org/mail-archive/web/pkix/current/msg32336.htm=
l.

I do not see that prohibition in the new text in -16.  In the cited email
message, I do see a disagreement between you and Stefan about what implemen=
tations
are likely to do, but I don't see any text in the draft that dictates that
implementations must or must not make that interpretation.

Speaking for myself, I would have no problem w/client code that inferred th=
at
any "revoked" response with revocation reason certificateHold (6) and
revocationTime January 1, 1970 most likely indicates a non-issued certifica=
te.
OTOH, such a client *cannot* rely on always receiving that form of response
for a known non-issued certificate for the reasons discussed in the new tex=
t
(e.g., responder not updated to use that response, responder uses only pre
produced responses).

Again speaking for myself, I think the current text in -16 is ok, in that I
don't see the prohibition that Piyush is concerned about there.  OTOH, I'd =
also
be ok with a couple of sentences added to say that (new) clients could use
that response format to infer that the certificate is a known non-issued
certificate, but that clients cannot rely on getting that form of response
for all known non-issued certificate (i.e., may get an "unknown" response).

Thanks,
--David

> -----Original Message-----
> From: Piyush Jain [mailto:piyush@ditenity.com]
> Sent: Tuesday, April 09, 2013 2:03 AM
> To: 'Sean Turner'
> Cc: ambarish@gmail.com; slava.galperin@gmail.com; cadams@eecs.uottawa.ca;
> 'Stefan Santesson'; Black, David; sts@aaa-sec.com; pkix@ietf.org; gen-
> art@ietf.org; 'Henry B. Hotz'
> Subject: RE: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
>=20
> > I went back and looked at the WG poll about this issue that you and lot=
 of
> > other people participated in (https://www.ietf.org/mail-
> > archive/web/pkix/current/msg31906.html).  The WG's rough consensus was
> > to allow "revoked" to be used for non-issued certificates with the cave=
at
> > thrown in by Paul Hoffman that the meaning of "revoked" be clear about
> > what it now means.  I've not seen anything that would make me want to
> > throw this draft back to the WG to revisit that consensus.
> >
>=20
> I believe that the straw poll consensus was that revoked will be overload=
ed
> to convey non-issued status to the clients.
> The deviation from that consensus is that in such cases, the current draf=
t
> prohibits clients to interpret the certificate as non-issued, and require=
s
> them to interpret it as issued and revoked by the CA. And this is necessa=
ry
> to circumvent the responder trust issue for CA delegated responders if th=
ey
> return extended revoked indicating non-issuance.
> Please see http://www.ietf.org/mail-archive/web/pkix/current/msg32336.htm=
l.
>=20
> This is an important distinction because from client's point of view
> non-issued response for a CA signed certificate is much more severe than =
a
> revoked response and is indicative of a CA/RA compromise.
> The reason I'm raising this at LC is because there were a few WG members =
who
> acknowledged this issue and there was no consensus (other than Stefan's
> response in the post linked above) on how this should be handled.
>=20
> I guess it would be okay if you and David make the determination that thi=
s
> issue is not worth debating anymore but I would surely have appreciated
> hearing the opinions of a few others.
>=20
> Best
> Piyush
>=20
>=20
>=20


From stefan@aaa-sec.com  Tue Apr  9 07:57:17 2013
Return-Path: <stefan@aaa-sec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33C1B21F8BAE for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 07:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.65
X-Spam-Level: 
X-Spam-Status: No, score=-99.65 tagged_above=-999 required=5 tests=[HELO_EQ_SE=0.35, 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 NgKtrcgbaAJi for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 07:57:16 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.113]) by ietfa.amsl.com (Postfix) with ESMTP id 5384D21F8B49 for <gen-art@ietf.org>; Tue,  9 Apr 2013 07:57:12 -0700 (PDT)
Received: from s87.loopia.se (localhost [127.0.0.1]) by s87.loopia.se (Postfix) with ESMTP id EF19E2030CCA for <gen-art@ietf.org>; Tue,  9 Apr 2013 16:57:10 +0200 (CEST)
X-Virus-Scanned: amavisd-new at outgoing-smtp.loopia.se
Received: from s87.loopia.se ([127.0.0.1]) by s87.loopia.se (s87.loopia.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ASVT65puzrIK for <gen-art@ietf.org>; Tue,  9 Apr 2013 16:57:10 +0200 (CEST)
Received: from s327.loopia.se (s34.loopia.se [194.9.94.70]) by s87.loopia.se (Postfix) with ESMTP id 8CB2D2030CCC for <gen-art@ietf.org>; Tue,  9 Apr 2013 16:57:10 +0200 (CEST)
Received: (qmail 58890 invoked from network); 9 Apr 2013 14:57:10 -0000
Received: from gw.aaa-sec.ideon.se (HELO [192.168.1.6]) (stefan@fiddler.nu@[85.235.7.89]) (envelope-sender <stefan@aaa-sec.com>) by s327.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <david.black@emc.com>; 9 Apr 2013 14:57:10 -0000
User-Agent: Microsoft-MacOutlook/14.3.2.130206
Date: Tue, 09 Apr 2013 16:57:05 +0100
From: Stefan Santesson <stefan@aaa-sec.com>
To: "Black, David" <david.black@emc.com>, Piyush Jain <piyush@ditenity.com>, 'Sean Turner' <turners@ieca.com>
Message-ID: <CD89F6C1.60183%stefan@aaa-sec.com>
Thread-Topic: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293E22D3E@MX15A.corp.emc.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: "ambarish@gmail.com" <ambarish@gmail.com>, "slava.galperin@gmail.com" <slava.galperin@gmail.com>, "cadams@eecs.uottawa.ca" <cadams@eecs.uottawa.ca>, "gen-art@ietf.org" <gen-art@ietf.org>, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, "sts@aaa-sec.com" <sts@aaa-sec.com>, "pkix@ietf.org" <pkix@ietf.org>
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 14:57:17 -0000

On 4/9/13 2:35 PM, "Black, David" <david.black@emc.com> wrote:

>Again speaking for myself, I think the current text in -16 is ok, in that
>I
>don't see the prohibition that Piyush is concerned about there.  OTOH,
>I'd also
>be ok with a couple of sentences added to say that (new) clients could use
>that response format to infer that the certificate is a known non-issued
>certificate, but that clients cannot rely on getting that form of response
>for all known non-issued certificate (i.e., may get an "unknown"
>response).


I'd rather not try to describe what clients should do or expect in terms
of non-issued certificates.
Clients are really not meant to know anything beyond "revoked" = this cert
should not be trusted.

This is a server choice to prevent the requested cert (if it exist at all)
from being accepted.
For requests for real certs, issued by a trusted CA, this case will never
even occur unless the CA is compromised.
And, if I put something in, given the discussion so far, the chance that
there will be some major disagreements with it, is really high.

The current text works.

/Stefan



From piyush@ditenity.com  Tue Apr  9 08:14:17 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 719E221F9588 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.098
X-Spam-Level: *
X-Spam-Status: No, score=1.098 tagged_above=-999 required=5 tests=[AWL=-2.098,  DOS_OUTLOOK_TO_MX=1, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_EQ_LT4=0.442, RDNS_DYNAMIC=0.1]
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 5-95YQb+iKPP for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:14:17 -0700 (PDT)
Received: from mail-gg0-x232.google.com (mail-gg0-x232.google.com [IPv6:2607:f8b0:4002:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id CA92F21F9452 for <gen-art@ietf.org>; Tue,  9 Apr 2013 08:14:16 -0700 (PDT)
Received: by mail-gg0-f178.google.com with SMTP id e5so1082308ggh.37 for <gen-art@ietf.org>; Tue, 09 Apr 2013 08:14:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language:x-gm-message-state; bh=EeXCAEEUuQXknGjOu3bVGL+OocjcAIezAEBSxxhTTFY=; b=F1lv0+oLZNp7CNYmsV1JIlLJ+Lx+tRvgObnzXxBRG48LIpA+bQhnwSbZHSpjWaJj2H yfVD29n383xhSloyqVdaCxy4tMpkq3axDQXkysYcioGbDtmYl8uImOw33/ge+bKqOMhS Pw/2khmJlJDJiQxu7mGv0yyCZCyIHYveIJUbFm34VrpV5zhPsSI53lBAoLMelavD/hwX xruPLx/mV+eQ5FLEJ9LDQz7tF5B8u0E5pvVoUeNcbB5TEIEDuAttMpcvZn1YHyjZMTET osUgeWrDt+CwHinJz6SJydvp2ZhMHVLPK3xlKQMOJQRXtOls/UCCbdTVWNlhb/Wptf6M /c4A==
X-Received: by 10.236.2.39 with SMTP id 27mr14574375yhe.183.1365520456194; Tue, 09 Apr 2013 08:14:16 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id v60sm43690040yhh.23.2013.04.09.08.14.14 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 09 Apr 2013 08:14:15 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: "'Black, David'" <david.black@emc.com>, "'Sean Turner'" <turners@ieca.com>
References: <003e01ce3077$5b6329f0$12297dd0$@ditenity.com> <20130403160532.EB4FD1A68A@ld9781.wdf.sap.corp> <00a401ce3092$0a1415d0$1e3c4170$@ditenity.com> <5163270C.20300@ieca.com> <07af01ce34a4$582df1d0$0889d570$@ditenity.com> <5163840F.2030508@ieca.com> <083601ce34e7$e3dcef40$ab96cdc0$@ditenity.com> <8D3D17ACE214DC429325B2B98F3AE71293E22D3E@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293E22D3E@MX15A.corp.emc.com>
Date: Tue, 9 Apr 2013 08:14:03 -0700
Message-ID: <08b901ce3534$e057b920$a1072b60$@ditenity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHHvIU0pEj95jqjILpXYwEgVOm34gLGPak8AXFeg0kBCCz4MwNWbgjOAWN27bMCjnis0AKXx8I0mGHZF+A=
Content-Language: en-us
X-Gm-Message-State: ALoCoQmwh2J2UUUhlTsOdgaTdtLW7jw6kts8QYZY2Z4zPVOhAWF2kDTt/QeELDOC0/z4QVOQKNjT
Cc: ambarish@gmail.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, gen-art@ietf.org, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, sts@aaa-sec.com, pkix@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 15:14:17 -0000

> I do not see that prohibition in the new text in -16.  In the cited email
> message, I do see a disagreement between you and Stefan about what
> implementations are likely to do, but I don't see any text in the draft
that
> dictates that implementations must or must not make that interpretation.

I think I failed to clarify this in my last message. Let me try again. I
based my interpretation on the following response from Stefan :

BEGIN QUOTE
~~~~~~~~~~~
" The draft does NOT define a "not-issued" response. It allows the "revoked"
response if a certificate serial number has never been issued. That is two
entirely different things. If you ask how to deal with the response, then
the client will not get a non- issued response. It will get a "revoked"
status."
END QUOTE
~~~~~~~~

The above explanation at the minimum indicates the author's intent that
clients should treat such certificates as "revoked" and not "non-issued".
However, if readers of the draft do not think that the draft explicitly
mandates it, we have a bigger problem w.r.t. to establishing trust in such
responses. Please see the text from section 4.2.2.2 bullet 2 and 3(page 15)

Begin TEXT
~~~~~~~~~
Clients MUST reject the   response if the certificate required to validate
the signature on the response fails to meet at least one of the following
criteria:
   1. Matches a local configuration of OCSP signing authority for the
certificate in question; or
   2. Is the certificate of the CA that issued the certificate in
question; or
   3. Includes a value of id-kp-OCSPSigning in an ExtendedKeyUsage extension
and is issued by the CA that issued the certificate in question as stated
above."
End Text
~~~~~~~

Based on above the responder trust models referred to by "2." and "3."
cannot be used to communicate "non-issued". 

-Piyush



From jari.arkko@piuha.net  Tue Apr  9 08:25:45 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2670321F9724 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[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 z3HUQXvzkmM1 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:25:44 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 3498721F9723 for <gen-art@ietf.org>; Tue,  9 Apr 2013 08:25:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 82B282CC55; Tue,  9 Apr 2013 18:25:43 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KbPaUQXznPME; Tue,  9 Apr 2013 18:25:42 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 8EA762CC4A; Tue,  9 Apr 2013 18:25:42 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B133213@ESESSMB209.ericsson.se>
Date: Tue, 9 Apr 2013 18:25:42 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <E3B4A390-1812-4E8A-AA6D-EB2B98859F8A@piuha.net>
References: <7594FB04B1934943A5C02806D1A2204B133213@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1503)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-saintandre-urn-example.all@tools.ietf.org" <draft-saintandre-urn-example.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-saintandre-urn-example-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 15:25:45 -0000

Thanks for your review, Christer. The document is up for discussion in =
this week's IESG telechat (on Thursday).

Peter: Have you seen Christer's question about Section 2.6?

Jari

On Mar 25, 2013, at 12:48 PM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
> =20
> Document:                         draft-saintandre-urn-example-04
> =20
> Reviewer:                           Christer Holmberg
> =20
> Review Date:                     25 March 2013
> =20
> IETF LC End Date:             9 April 2013
> =20
> IETF Telechat Date           11 April 2013
> =20
> Summary:  The draft is well written, with a very minor editorial =
comment, and is ready for publication.
> =20
> Major Issues: None
> =20
> Minor Issues: None
> =20
> Editorial nits: Section 2.6 contains the word =93counseled=94. While =
not wrong, is there a reason why more common IETF language can=92t be =
used here? E.g. =93recommended against=94, or something? :)
> =20
> Best regards,
> =20
> Christer
> =20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From psaintan@cisco.com  Tue Apr  9 08:32:05 2013
Return-Path: <psaintan@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 667DF21F86C3 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[AWL=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BL89WiW14O8i for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:32:04 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id D533121F86C1 for <gen-art@ietf.org>; Tue,  9 Apr 2013 08:32:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7262; q=dns/txt; s=iport; t=1365521525; x=1366731125; h=cc:message-id:from:to:in-reply-to:mime-version:subject: date:references; bh=zCTfsXoD/CcTuVkecrzJE7Q/k6p9FnvG9Ddo30h2qyE=; b=QQS9dQCdWoV8+4ljqIBDprzUdQGEr9BwWvEH0ciNTGUa/ZREB/xD7kAi htE9i6aHFerKHhdEjoLH9Jnhf7yoA7qKMG9fZJmnAfKduBJhpXXI9iYvj D3KX6NDBQQj6yhGv1uB0gUUrDJX3tUMa8dp+xcWcQ/FsFZjutxDps3nGc 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFANwzZFGrRDoG/2dsb2JhbABRgkJENrh5iDaBFRZ0gh8BAQEDAQEBAWsLBQsLFAQuJzAGE4gOBQ2uSZA6jwMNBAeCYGEDiH6Ne4EhhGKLDIMqHQ
X-IronPort-AV: E=Sophos;i="4.87,439,1363132800"; d="scan'208,217";a="75628667"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 09 Apr 2013 15:32:04 +0000
Received: from [192.168.1.3] (sjc-vpn2-1011.cisco.com [10.21.115.243]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r39FW2Kf020135; Tue, 9 Apr 2013 15:32:03 GMT
Message-Id: <9667F45D-66BC-4BF7-8316-66329B20C061@cisco.com>
From: Peter Saint-Andre <psaintan@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <E3B4A390-1812-4E8A-AA6D-EB2B98859F8A@piuha.net>
Content-Type: multipart/alternative; boundary=Apple-Mail-22-667265695
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 9 Apr 2013 09:32:02 -0600
References: <7594FB04B1934943A5C02806D1A2204B133213@ESESSMB209.ericsson.se> <E3B4A390-1812-4E8A-AA6D-EB2B98859F8A@piuha.net>
X-Mailer: Apple Mail (2.936)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-saintandre-urn-example.all@tools.ietf.org" <draft-saintandre-urn-example.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-saintandre-urn-example-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 15:32:05 -0000

--Apple-Mail-22-667265695
Content-Type: text/plain;
	charset=WINDOWS-1252;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: quoted-printable

On Apr 9, 2013, at 9:25 AM, Jari Arkko wrote:

> Thanks for your review, Christer. The document is up for discussion =20=

> in this week's IESG telechat (on Thursday).
>
> Peter: Have you seen Christer's question about Section 2.6?

Sorry, I had missed Christer's review. That text is an artifact of =20
when the document was Informational, not BCP. I suggest:

OLD
    As a
    result, implementers are counselled against using example URNs for
    any purposes other than documentation, private testing, and truly
    experimental contexts.
NEW
    Therefore, it is NOT RECOMMENDED for implementers to use example
    URNs for any purposes other than documentation, private testing,
    and truly experimental contexts.

>
> Jari
>
> On Mar 25, 2013, at 12:48 PM, Christer Holmberg =
<christer.holmberg@ericsson.com=20
> > wrote:
>
>> I am the assigned Gen-ART reviewer for this draft. For background =20
>> on Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=20
>> >
>>
>> Document:                         draft-saintandre-urn-example-04
>>
>> Reviewer:                           Christer Holmberg
>>
>> Review Date:                     25 March 2013
>>
>> IETF LC End Date:             9 April 2013
>>
>> IETF Telechat Date           11 April 2013
>>
>> Summary:  The draft is well written, with a very minor editorial =20
>> comment, and is ready for publication.
>>
>> Major Issues: None
>>
>> Minor Issues: None
>>
>> Editorial nits: Section 2.6 contains the word =93counseled=94. While =20=

>> not wrong, is there a reason why more common IETF language can=92t be =
=20
>> used here? E.g. =93recommended against=94, or something? :)
>>
>> Best regards,
>>
>> Christer
>>
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>


--Apple-Mail-22-667265695
Content-Type: text/html;
	charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>On Apr 9, 2013, at =
9:25 AM, Jari Arkko wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>Thanks =
for your review, Christer. The document is up for discussion in this =
week's IESG telechat (on Thursday).<br><br>Peter: Have you seen =
Christer's question about Section =
2.6?<br></div></blockquote><div><br></div>Sorry, I had missed Christer's =
review. That text is an artifact of when the document was Informational, =
not BCP. I suggest:</div><div><br></div><div>OLD</div><div><span =
class=3D"Apple-style-span" style=3D"font-size: 16px; font-family: Times; =
"><pre class=3D"newpage" style=3D"font-size: 1em; margin-top: 0px; =
margin-bottom: 0px; page-break-before: always; ">   As a
   result, implementers are counselled against using example URNs for
   any purposes other than documentation, private testing, and truly
   experimental contexts.</pre></span></div><div>NEW</div><div><span =
class=3D"Apple-style-span" style=3D"font-size: 16px; font-family: Times; =
"><pre class=3D"newpage" style=3D"font-size: 1em; margin-top: 0px; =
margin-bottom: 0px; page-break-before: always; ">   Therefore, it is NOT =
RECOMMENDED for implementers to use example&nbsp;</pre><pre =
class=3D"newpage" style=3D"font-size: 1em; margin-top: 0px; =
margin-bottom: 0px; page-break-before: always; ">   URNs for any =
purposes other than documentation, private testing,&nbsp;</pre><pre =
class=3D"newpage" style=3D"font-size: 1em; margin-top: 0px; =
margin-bottom: 0px; page-break-before: always; ">   and truly =
experimental contexts.</pre><pre class=3D"newpage" style=3D"font-size: =
1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; =
"><br></pre></span></div><div><blockquote =
type=3D"cite"><div><br>Jari<br><br>On Mar 25, 2013, at 12:48 PM, =
Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>&gt; wrote:<br><br><blockquote type=3D"cite">I am the assigned =
Gen-ART reviewer for this draft. For background on Gen-ART, please see =
the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;<br></blockquote><bl=
ockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Document: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;draf=
t-saintandre-urn-example-04<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Reviewer: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;Christer Holmberg<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Review Date: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;25 March =
2013<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">IETF LC End =
Date: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9 =
April 2013<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">IETF Telechat =
Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11 =
April 2013<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Summary: =
&nbsp;The draft is well written, with a very minor editorial comment, =
and is ready for publication.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Major Issues: =
None<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Minor Issues: =
None<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Editorial nits: =
Section 2.6 contains the word =93counseled=94. While not wrong, is there =
a reason why more common IETF language can=92t be used here? E.g. =
=93recommended against=94, or something? :)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Best =
regards,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Christer<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">Gen-art mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:Gen-art@ietf.org">Gen-art@ietf.org</a><br></blockquote><blo=
ckquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/gen-art">https://www.ietf.or=
g/mailman/listinfo/gen-art</a><br></blockquote><br></div></blockquote></di=
v><br></body></html>=

--Apple-Mail-22-667265695--

From jari.arkko@piuha.net  Tue Apr  9 08:39:42 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6DF321F972F for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.299,  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 Kt9fSIcndkLo for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:39:42 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE6B21F972C for <gen-art@ietf.org>; Tue,  9 Apr 2013 08:39:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6E9782CC55; Tue,  9 Apr 2013 18:39:41 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nXg9OElzB3XS; Tue,  9 Apr 2013 18:39:39 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 96BF52CC4A; Tue,  9 Apr 2013 18:39:39 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <1365511455.5273.8789.camel@mightyatom>
Date: Tue, 9 Apr 2013 18:39:39 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <EB30A064-EF5D-4534-AA40-C5BD7C0F4173@piuha.net>
References: <1365511455.5273.8789.camel@mightyatom>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1503)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-tls-multiple-cert-status-extension.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art telechat review: draft-ietf-tls-multiple-cert-status-extension-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 15:39:42 -0000

Elwyn,

Thanks for your review and re-review. I'm balloting a no-objection based =
on your review.

Jari

On Apr 9, 2013, at 3:44 PM, Elwyn Davies <elwynd@dial.pipex.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document:draft-ietf-tls-multiple-cert-status-extension-06.txt
> Reviewer: Elwyn Davies
> Review Date: 07 April 2013
> IETF LC End Date:
> IESG Telechat date: 11 April 2013
>=20
> Summary: Ready for the IESG
>=20
> Issues identified in last call review have been resolved.  Thanks.
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From piyush@ditenity.com  Tue Apr  9 08:42:11 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D72FB21F9774 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.251
X-Spam-Level: 
X-Spam-Status: No, score=-1.251 tagged_above=-999 required=5 tests=[AWL=2.348,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 08iy4hHL83Qd for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:42:11 -0700 (PDT)
Received: from mail-gh0-f170.google.com (mail-gh0-f170.google.com [209.85.160.170]) by ietfa.amsl.com (Postfix) with ESMTP id 491F421F976C for <gen-art@ietf.org>; Tue,  9 Apr 2013 08:42:11 -0700 (PDT)
Received: by mail-gh0-f170.google.com with SMTP id z2so1092938ghb.1 for <gen-art@ietf.org>; Tue, 09 Apr 2013 08:42:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language:x-gm-message-state; bh=ZaUQ8IcbuIVYzFzIWxiYFenqK/As61mCYcfKd2v3PPA=; b=MgiGMCm5U4HVtAay41X6K0UChN5WslOaP1dXpCqMXVd0jgaTqJhKd967FyQIwzQ2bS imh7KTD6y5QWPt1knODB4+5s0bGNiyEA971aGYpsaj6AOpvLTzyp07QtGgYn+ZGC/tSs n7na0VTCvEEXt/CAPkb+zh6ZA6d/NoSYoto1Dg0wWMS1GdjNDWIcFBQOdQapkr4NI/3b sNMh7jg9Wf+aHrG8zEEMeNdr2TtZ8J4wQRFZIUIMRogP0wMm6UiuG3PEzIiEGTQiRACO YHbfitwssUrjFSQ9+4bEPRKOqg4GOcyjfXnTfpGebqrNUzGAHU6A+fDhwsIVwltJWxwR 9Ykw==
X-Received: by 10.236.208.34 with SMTP id p22mr16161356yho.114.1365522130729;  Tue, 09 Apr 2013 08:42:10 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id o64sm43848776yhd.16.2013.04.09.08.42.08 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 09 Apr 2013 08:42:10 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: "'Stefan Santesson'" <stefan@aaa-sec.com>, "'Black, David'" <david.black@emc.com>, "'Sean Turner'" <turners@ieca.com>
References: <8D3D17ACE214DC429325B2B98F3AE71293E22D3E@MX15A.corp.emc.com> <CD89F6C1.60183%stefan@aaa-sec.com>
In-Reply-To: <CD89F6C1.60183%stefan@aaa-sec.com>
Date: Tue, 9 Apr 2013 08:41:57 -0700
Message-ID: <08d601ce3538$c67d1550$53773ff0$@ditenity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF1yih3SmaeJVo5r2GHuwJNknT/Lpl+1XuQ
Content-Language: en-us
X-Gm-Message-State: ALoCoQkEDC5Ti8QwKLshewIMMA25D49QwX4dGKYOE/pa1k0/U9ej6vZmAJmQ834RVKYazEzJs8bM
Cc: ambarish@gmail.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, gen-art@ietf.org, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, sts@aaa-sec.com, pkix@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 15:42:12 -0000

> I'd rather not try to describe what clients should do or expect in terms
of
> non-issued certificates.
> Clients are really not meant to know anything beyond "revoked" = this cert
> should not be trusted.
[Piyush] 
Thanks for clarifying your position on this Stefan.
This is the position I disagree with. I think several people in the WG
expressed that the meaning should be clearly conveyed if "revoked" is
extended to communicate "non-issued".  Expectation that clients should treat
these responses as normal revoked is not aligned with WG consensus IMO.
> 
> This is a server choice to prevent the requested cert (if it exist at all)
from
> being accepted.
> For requests for real certs, issued by a trusted CA, this case will never
even
> occur unless the CA is compromised.
[Piyush]
 And I think this is the only case that is interesting to the clients. I
combed through the WG discussion and did not find a single case being
discussed where clients benefit from sending OCSP requests for serial
numbers for non-existent certificates.

> And, if I put something in, given the discussion so far, the chance that
there
> will be some major disagreements with it, is really high.
[Piyush]
These are the issues that implementers will have to deal with. If there are
going to be disagreement, they should be dealt with before the document is
published IMO, unless 2560bis is considered a stop gap measure and OCSP v2
is on the radar.
I understand the desire to wrap up the pending documents so pkix can be
disbanded on schedule. However, I'll leave that to the AD to decide that the
benefits of meeting that schedule outweighs the cons of publishing a
document that can potentially lead to confusion among implementers.




From salvatore.dantonio@uniparthenope.it  Tue Apr  9 08:40:37 2013
Return-Path: <salvatore.dantonio@uniparthenope.it>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6407621F97A8; Tue,  9 Apr 2013 08:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.127
X-Spam-Level: **
X-Spam-Status: No, score=2.127 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, MSGID_MULTIPLE_AT=1.449]
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 GEnIxUhvZSvT; Tue,  9 Apr 2013 08:40:36 -0700 (PDT)
Received: from mail.uniparthenope.it (mail.uniparthenope.it [192.167.9.244]) by ietfa.amsl.com (Postfix) with ESMTP id B09E121F9798; Tue,  9 Apr 2013 08:40:32 -0700 (PDT)
Received: from mail2.uniparthenope.it (unknown [10.1.2.108]) by mail.uniparthenope.it (Postfix) with SMTP id EA27A41711; Tue,  9 Apr 2013 15:40:30 +0000 (UTC)
Received: from (unknown [192.168.241.108]) by mail2.uniparthenope.it with smtp id 1d43_cec0a27c_a12b_11e2_9101_001372515a5c; Tue, 09 Apr 2013 17:40:30 +0200
Received: from spamk.uniparthenope.it (localhost [127.0.0.1]) by spamk.uniparthenope.it (Postfix) with ESMTP id C174CC430A; Tue,  9 Apr 2013 17:40:29 +0200 (CEST)
Received: by spamk.uniparthenope.it (Postfix, from userid 500) id BA7F1C4302; Tue,  9 Apr 2013 17:40:29 +0200 (CEST)
Received: from mail.uniparthenope.it (unknown [192.168.241.109]) by spamk.uniparthenope.it (Postfix) with ESMTP id 593DCC4301; Tue,  9 Apr 2013 17:40:28 +0200 (CEST)
Received: by mail.uniparthenope.it (Postfix, from userid 108) id 452064181E; Tue,  9 Apr 2013 17:40:28 +0200 (CEST)
Received: from saldantoPC (unknown [192.168.162.11]) (Authenticated sender: salvatore.dantonio@uniparthenope.it) by mail.uniparthenope.it (Postfix) with ESMTPA id 803F841526; Tue,  9 Apr 2013 17:40:18 +0200 (CEST)
From: "Salvatore D'Antonio" <salvatore.dantonio@uniparthenope.it>
To: "'Benoit Claise'" <bclaise@cisco.com>, <draft-ietf-ipfix-flow-selection-tech@tools.ietf.org>
References: <20130401072846.32360.9502.idtracker@ietfa.amsl.com> <5162C44B.5030904@cisco.com>
In-Reply-To: <5162C44B.5030904@cisco.com>
Date: Tue, 9 Apr 2013 17:40:03 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac40XDRV3pT1xDzNTsGp6osHVZb3KAA1rsdA
Content-Language: it
Message-ID: <005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it>
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0058_01CE3549.52940480"
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.42/RELEASE, bases: 20130409 #9883311, check: 20130409 clean
X-Mailman-Approved-At: Tue, 09 Apr 2013 08:43:28 -0700
Cc: rahulp@cisco.com, 'IETF discussion list' <ietf@ietf.org>, apps-discuss@ietf.org, 'General Area Review Team' <gen-art@ietf.org>, 'S Moonesamy' <sm+ietf@elandsys.com>, ipfix-chairs@tools.ietf.org, ipfix@ietf.org, iesg@ietf.org
Subject: [Gen-art] R: Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 15:40:37 -0000

Messaggio multipart in formato MIME.

------=_NextPart_000_0058_01CE3549.52940480
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Dear all,

=20

A new version of the Internet Draft on Flow Selection Techniques has =
been submitted. It contains the following changes:

-          A new section illustrating the difference between =
Intermediate Flow Selection Process and Intermediate Selection Process =
has been added,

-          The sentence "In order to be compliant with this document, at =
least the Property  Match Filtering MUST be implemented." has been =
removed in Section 1,

-          =E2=80=9CMUST=E2=80=9D has been replaced with =
=E2=80=9CSHOULD=E2=80=9D in Section 5.1,

-          =E2=80=9CThe flowSelectorAlgorithm registry is maintained by =
IANA." has been replaced with =E2=80=9CIANA is requested to create the =
flowSelectorAlgorithm registry.=E2=80=9D

-          The sentence "The registry can be updated when specifications =
of the new  technique(s) and any new Information Elements are provided." =
has been removed since it did not clarify how the registry will be =
managed.

-           Section 6.1.1 =E2=80=9CProperty Match Filtering=E2=80=9D has =
been changed by adding some text on how Property Match Filtering can be  =
used by an Intermediate Flow Selection Process in the Metering Process, =
in the  Exporting Process and within an IPFIX Mediator.

=20

Best regards,

=20

Salvatore

=20

Da: Benoit Claise [mailto:bclaise@cisco.com]=20
Inviato: luned=C3=AC 8 aprile 2013 15:21
A: draft-ietf-ipfix-flow-selection-tech@tools.ietf.org
Cc: ipfix-chairs@tools.ietf.org
Oggetto: Fwd: Last Call Expired: =
<draft-ietf-ipfix-flow-selection-tech-14.txt>

=20

Dear authors,

The IETF last call has finished.
Can you please update your draft based on the feedback received.
Then I will progress it.

Regards, Benoit



-------- Original Message --------=20


Subject:=20

Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>


Date:=20

Mon, 01 Apr 2013 00:28:46 -0700


From:=20

DraftTracker Mail System  <mailto:iesg-secretary@ietf.org> =
<iesg-secretary@ietf.org>


To:=20

iesg@ietf.org, ipfix-chairs@tools.ietf.org, =
draft-ietf-ipfix-flow-selection-tech@tools.ietf.org


CC:=20

iesg-secretary@ietf.org

=20

Please DO NOT reply to this email.
=20
I-D: <draft-ietf-ipfix-flow-selection-tech-14.txt>
ID Tracker URL: =
http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tech/
=20
IETF Last Call has ended, and the state has been changed to
Waiting for AD Go-Ahead.
=20
=20
=20

=20

=20

  _____ =20

Nessun virus nel messaggio.
Controllato da AVG - www.avg.com
Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data di =
rilascio: 07/04/2013


******************************************************************************=09=0A
IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO=0A
 =0A
Il 5 per mille all'Universita' degli Studi di Napoli "Parthenope" incrementa le borse di studio agli studenti - codice fiscale 80018240632=0A
http://www.uniparthenope.it/index.php/5xmille =0A
 =0A
http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille=0A
 =0A
Questa informativa e' inserita in automatico dal sistema al fine esclusivo della realizzazione dei fini istituzionali dell'ente.=0A

------=_NextPart_000_0058_01CE3549.52940480
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"Preformattato HTML Carattere";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.PreformattatoHTMLCarattere
	{mso-style-name:"Preformattato HTML Carattere";
	mso-style-priority:99;
	mso-style-link:"Preformattato HTML";
	font-family:Consolas;
	color:black;}
span.StileMessaggioDiPostaElettronica19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 2.0cm 2.0cm 2.0cm;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:217212090;
	mso-list-type:hybrid;
	mso-list-template-ids:308057158 -1513439274 134807555 134807557 =
134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-GB link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dear all,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A new version of the Internet Draft on Flow Selection =
Techniques
has been submitted. It contains the following =
changes:<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A new section illustrating the difference between =
Intermediate
Flow Selection Process and Intermediate Selection Process has been =
added,<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The sentence &quot;In order to be compliant with this =
document,
at least the Property =C2=A0Match Filtering MUST be implemented.&quot; =
has been removed
in Section 1,<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>=E2=80=9CMUST=E2=80=9D has been replaced with =
=E2=80=9CSHOULD=E2=80=9D in Section 5.1,<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>=E2=80=9CThe flowSelectorAlgorithm registry is maintained =
by IANA.&quot;
has been replaced with =E2=80=9CIANA is requested to create the =
flowSelectorAlgorithm
registry.=E2=80=9D<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The sentence &quot;The registry can be updated when
specifications of the new=C2=A0 technique(s) and any new Information =
Elements are
provided.&quot; has been removed since it did not clarify how the =
registry will
be managed.<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>=C2=A0Section 6.1.1 =E2=80=9CProperty Match =
Filtering=E2=80=9D has been changed by
adding some text on how Property Match Filtering can be =C2=A0used by an
Intermediate Flow Selection Process in the Metering Process, in the =
=C2=A0Exporting
Process and within an IPFIX Mediator.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Best regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Salvatore<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DIT =
style=3D'font-size:10.0pt;font-family:"Segoe UI","sans-serif";
color:windowtext'>Da:</span></b><span lang=3DIT =
style=3D'font-size:10.0pt;
font-family:"Segoe UI","sans-serif";color:windowtext'> Benoit Claise
[mailto:bclaise@cisco.com] <br>
<b>Inviato:</b> luned=C3=AC 8 aprile 2013 15:21<br>
<b>A:</b> draft-ietf-ipfix-flow-selection-tech@tools.ietf.org<br>
<b>Cc:</b> ipfix-chairs@tools.ietf.org<br>
<b>Oggetto:</b> Fwd: Last Call Expired:
&lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></span></p>=


</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Dear authors,<br>
<br>
The IETF last call has finished.<br>
Can you please update your draft based on the feedback received.<br>
Then I will progress it.<br>
<br>
Regards, Benoit<o:p></o:p></p>

<div>

<p class=3DMsoNormal><br>
<br>
-------- Original Message -------- <o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright =
style=3D'text-align:right'><b>Subject: <o:p></o:p></b></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>Last Call Expired:
  &lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>Date: =
<o:p></o:p></b></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>Mon, 01 Apr 2013 00:28:46 -0700<o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>From: =
<o:p></o:p></b></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>DraftTracker Mail System <a
  =
href=3D"mailto:iesg-secretary@ietf.org">&lt;iesg-secretary@ietf.org&gt;</=
a><o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>To: =
<o:p></o:p></b></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal><a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>, <a
  =
href=3D"mailto:ipfix-chairs@tools.ietf.org">ipfix-chairs@tools.ietf.org</=
a>, <a
  =
href=3D"mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org">draft=
-ietf-ipfix-flow-selection-tech@tools.ietf.org</a><o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>CC: =
<o:p></o:p></b></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal><a =
href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a><o:p><=
/o:p></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p>

<pre>Please DO NOT reply to this =
email.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>I-D: =
&lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></pre><pre>=
ID Tracker URL: <a
href=3D"http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-t=
ech/">http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tec=
h/</a><o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>IETF Last Call =
has ended, and the state has been changed =
to<o:p></o:p></pre><pre>Waiting for AD =
Go-Ahead.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o=
:p></pre><pre><o:p>&nbsp;</o:p></pre>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D1 width=3D"100%" noshade style=3D'color:#A0A0A0' =
align=3Dcenter>

</div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Nessun
virus nel messaggio.<br>
Controllato da AVG - <a href=3D"http://www.avg.com">www.avg.com</a><br>
Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data di =
rilascio:
07/04/2013<o:p></o:p></p>

</div>


<br>=
<STYLE TYPE=3D"text/css">=0A
=09<!--=0A
=09=09@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }=0A
=09=09P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }=0A
=09=09P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }=0A
=09=09P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }=0A
=09=09P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }=0A
=09=09A:link { color: #0000ff }=0A
=09-->=0A
=09</STYLE>=0A
<!--</HEAD></BODY>-->=0A
<P LANG=3D"it-IT" TEXT=3D"#000000" LINK=3D"#0000ff" DIR=3D"LTR">=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">*******************************************************************************************************</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">IL=0A
MERITO DEGLI STUDENTI&nbsp;VIENE RICONOSCIUTO</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">Il=0A
5 per mille all'Universit&agrave degli Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli studenti=0A
- codice fiscale </FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif"><B>80018240632</B></FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">=0A
</FONT></FONT>=0A
</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/5xmille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/5xmille</U></FONT></FONT></A><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">&nbsp;</FONT></FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</U></FONT></FONT></A></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;<FONT FACE=3D"Arial, sans-serif"><BR>Questa=0A
informativa &egrave inserita in automatico dal sistema al fine esclusivo=0A
della realizzazione dei fini istituzionali dell&#39;ente.</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><BR>=0A
</P>=0A
<!--</BODY>-->=0A
<!--</HTML>-->=0A
<br>=
</body>

</html>

<br>=
<STYLE TYPE=3D"text/css">=0A
=09<!--=0A
=09=09@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }=0A
=09=09P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }=0A
=09=09P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }=0A
=09=09P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }=0A
=09=09P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }=0A
=09=09A:link { color: #0000ff }=0A
=09-->=0A
=09</STYLE>=0A
<!--</HEAD></BODY>-->=0A
<P LANG=3D"it-IT" TEXT=3D"#000000" LINK=3D"#0000ff" DIR=3D"LTR">=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">*******************************************************************************************************</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">IL=0A
MERITO DEGLI STUDENTI&nbsp;VIENE RICONOSCIUTO</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">Il=0A
5 per mille all'Universit&agrave degli Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli studenti=0A
- codice fiscale </FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif"><B>80018240632</B></FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">=0A
</FONT></FONT>=0A
</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/5xmille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/5xmille</U></FONT></FONT></A><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">&nbsp;</FONT></FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</U></FONT></FONT></A></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;<FONT FACE=3D"Arial, sans-serif"><BR>Questa=0A
informativa &egrave inserita in automatico dal sistema al fine esclusivo=0A
della realizzazione dei fini istituzionali dell&#39;ente.</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><BR>=0A
</P>=0A
<!--</BODY>-->=0A
<!--</HTML>-->=0A
<br>=
------=_NextPart_000_0058_01CE3549.52940480--

From jari.arkko@piuha.net  Tue Apr  9 08:54:01 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5E0F21F936C for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:54:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.733
X-Spam-Level: 
X-Spam-Status: No, score=-101.733 tagged_above=-999 required=5 tests=[AWL=0.866, 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 3SZuOYjuWvAf for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 08:54:00 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA5821F93CD for <gen-art@ietf.org>; Tue,  9 Apr 2013 08:54:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 60CF32CC55; Tue,  9 Apr 2013 18:53:53 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XYVy95TT1VcW; Tue,  9 Apr 2013 18:53:51 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B89FA2CC4A; Tue,  9 Apr 2013 18:53:51 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <515E7769.9020600@gmail.com>
Date: Tue, 9 Apr 2013 18:53:51 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D90EAE2-1194-4697-AA19-C32111CBC93D@piuha.net>
References: <515E7769.9020600@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-appsawg-webfinger.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-appsawg-webfinger-12.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 15:54:01 -0000

Thanks for your review and re-review, Brian. I'm basing my evaluation in =
Thursday's IESG telechat on your review. (As well as thinking some of =
those privacy issues on my own, too.)

Jari

On Apr 5, 2013, at 10:04 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-appsawg-webfinger-12.txt
> Reviewer: Brian Carpenter
> Review Date: 2013-04-05
> IETF LC End Date: 2013-03-18
> IESG Telechat date: 2013-04-11
>=20
> Summary:  Ready
> --------
>=20
> Comments:
> ---------
>=20
> Thanks for handling my Last Call comment.
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From david.black@emc.com  Tue Apr  9 08:57:47 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 287F421F942D; Tue,  9 Apr 2013 08:57:47 -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 Vy-D2-6oAP1R; Tue,  9 Apr 2013 08:57:43 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 8054321F9415; Tue,  9 Apr 2013 08:57:39 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r39FvP4a032358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Apr 2013 11:57:26 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 9 Apr 2013 11:57:09 -0400
Received: from mxhub06.corp.emc.com (mxhub06.corp.emc.com [128.222.70.203]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r39Fv46i012569; Tue, 9 Apr 2013 11:57:04 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub06.corp.emc.com ([128.222.70.203]) with mapi; Tue, 9 Apr 2013 11:57:03 -0400
From: "Black, David" <david.black@emc.com>
To: Piyush Jain <piyush@ditenity.com>, "'Sean Turner'" <turners@ieca.com>
Date: Tue, 9 Apr 2013 11:57:02 -0400
Thread-Topic: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
Thread-Index: AQHHvIU0pEj95jqjILpXYwEgVOm34gLGPak8AXFeg0kBCCz4MwNWbgjOAWN27bMCjnis0AKXx8I0mGHZF+CAABrXQA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293E22DA2@MX15A.corp.emc.com>
References: <003e01ce3077$5b6329f0$12297dd0$@ditenity.com> <20130403160532.EB4FD1A68A@ld9781.wdf.sap.corp> <00a401ce3092$0a1415d0$1e3c4170$@ditenity.com> <5163270C.20300@ieca.com> <07af01ce34a4$582df1d0$0889d570$@ditenity.com> <5163840F.2030508@ieca.com> <083601ce34e7$e3dcef40$ab96cdc0$@ditenity.com> <8D3D17ACE214DC429325B2B98F3AE71293E22D3E@MX15A.corp.emc.com> <08b901ce3534$e057b920$a1072b60$@ditenity.com>
In-Reply-To: <08b901ce3534$e057b920$a1072b60$@ditenity.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ambarish@gmail.com" <ambarish@gmail.com>, "slava.galperin@gmail.com" <slava.galperin@gmail.com>, "cadams@eecs.uottawa.ca" <cadams@eecs.uottawa.ca>, "gen-art@ietf.org" <gen-art@ietf.org>, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, "sts@aaa-sec.com" <sts@aaa-sec.com>, "pkix@ietf.org" <pkix@ietf.org>
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 15:57:47 -0000

Piyush,

> I think I failed to clarify this in my last message. Let me try again. I
> based my interpretation on the following response from Stefan :

[ ... snip ...]

> The above explanation at the minimum indicates the author's intent that
> clients should treat such certificates as "revoked" and not "non-issued".

This may be where we're talking past each other, because what matters is
the text in the draft.  I understand Stefan's intent, and believe that the
use of lower case "should" in the text quoted above is a fair summary of
what's in the current draft.  That's not an absolute prohibition on or
requirement for client behavior, although it's certainly the client behavio=
r
that responders should expect (again, lower case "should").

> However, if readers of the draft do not think that the draft explicitly
> mandates it, we have a bigger problem w.r.t. to establishing trust in suc=
h
> responses. Please see the text from section 4.2.2.2 bullet 2 and 3(page 1=
5)
>=20
> Begin TEXT
> ~~~~~~~~~
> Clients MUST reject the   response if the certificate required to validat=
e
> the signature on the response fails to meet at least one of the following
> criteria:
>    1. Matches a local configuration of OCSP signing authority for the
> certificate in question; or
>    2. Is the certificate of the CA that issued the certificate in
> question; or
>    3. Includes a value of id-kp-OCSPSigning in an ExtendedKeyUsage extens=
ion
> and is issued by the CA that issued the certificate in question as stated
> above."
> End Text
> ~~~~~~~
>=20
> Based on above the responder trust models referred to by "2." and "3."
> cannot be used to communicate "non-issued".

I think the mechanics of the response validation checks are fine - is the
concern that use of "that issued" for items 2 and 3 may be incorrect wrt
known non-issued certificates? =20

It may be useful to keep in mind that the CA may have issued the
"non-issued" certificate, but no longer has any record of having done so,
so I disagree with the statement that the later two models cannot be used
to communicate "non-issued", as the CA's signature on such a certificate
may be valid.

Thanks,
--David

> -----Original Message-----
> From: Piyush Jain [mailto:piyush@ditenity.com]
> Sent: Tuesday, April 09, 2013 11:14 AM
> To: Black, David; 'Sean Turner'
> Cc: ambarish@gmail.com; slava.galperin@gmail.com; cadams@eecs.uottawa.ca;
> 'Stefan Santesson'; sts@aaa-sec.com; pkix@ietf.org; gen-art@ietf.org; 'He=
nry
> B. Hotz'
> Subject: RE: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
>=20
> > I do not see that prohibition in the new text in -16.  In the cited ema=
il
> > message, I do see a disagreement between you and Stefan about what
> > implementations are likely to do, but I don't see any text in the draft
> that
> > dictates that implementations must or must not make that interpretation=
.
>=20
> I think I failed to clarify this in my last message. Let me try again. I
> based my interpretation on the following response from Stefan :
>=20
> BEGIN QUOTE
> ~~~~~~~~~~~
> " The draft does NOT define a "not-issued" response. It allows the "revok=
ed"
> response if a certificate serial number has never been issued. That is tw=
o
> entirely different things. If you ask how to deal with the response, then
> the client will not get a non- issued response. It will get a "revoked"
> status."
> END QUOTE
> ~~~~~~~~
>=20
> The above explanation at the minimum indicates the author's intent that
> clients should treat such certificates as "revoked" and not "non-issued".
> However, if readers of the draft do not think that the draft explicitly
> mandates it, we have a bigger problem w.r.t. to establishing trust in suc=
h
> responses. Please see the text from section 4.2.2.2 bullet 2 and 3(page 1=
5)
>=20
> Begin TEXT
> ~~~~~~~~~
> Clients MUST reject the   response if the certificate required to validat=
e
> the signature on the response fails to meet at least one of the following
> criteria:
>    1. Matches a local configuration of OCSP signing authority for the
> certificate in question; or
>    2. Is the certificate of the CA that issued the certificate in
> question; or
>    3. Includes a value of id-kp-OCSPSigning in an ExtendedKeyUsage extens=
ion
> and is issued by the CA that issued the certificate in question as stated
> above."
> End Text
> ~~~~~~~
>=20
> Based on above the responder trust models referred to by "2." and "3."
> cannot be used to communicate "non-issued".
>=20
> -Piyush
>=20
>=20


From jari.arkko@piuha.net  Tue Apr  9 09:02:27 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEF9B21F8F39 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 09:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.079
X-Spam-Level: 
X-Spam-Status: No, score=-102.079 tagged_above=-999 required=5 tests=[AWL=0.520, 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 3S-82cJpnSm3 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 09:02:27 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 5A3DB21F8EEB for <gen-art@ietf.org>; Tue,  9 Apr 2013 09:02:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A5A6D2CC55; Tue,  9 Apr 2013 19:02:26 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eBrBy888HI9o; Tue,  9 Apr 2013 19:02:26 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 215272CC4A; Tue,  9 Apr 2013 19:02:26 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9667F45D-66BC-4BF7-8316-66329B20C061@cisco.com>
Date: Tue, 9 Apr 2013 19:02:25 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <474475C2-0C53-450E-A308-8B14BF8ABA41@piuha.net>
References: <7594FB04B1934943A5C02806D1A2204B133213@ESESSMB209.ericsson.se> <E3B4A390-1812-4E8A-AA6D-EB2B98859F8A@piuha.net> <9667F45D-66BC-4BF7-8316-66329B20C061@cisco.com>
To: Peter Saint-Andre <psaintan@cisco.com>
X-Mailer: Apple Mail (2.1503)
Cc: gen-art@ietf.org, draft-saintandre-urn-example.all@tools.ietf.org
Subject: Re: [Gen-art] Genart review of draft-saintandre-urn-example-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 16:02:27 -0000

Thanks, your text suggestion looks fine to me.

jari



From vkg@bell-labs.com  Tue Apr  9 09:19:18 2013
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7735B21F8783 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 09:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 k9uU8r61ZDUA for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 09:19:17 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id B8E8821F871C for <gen-art@ietf.org>; Tue,  9 Apr 2013 09:19:17 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r39GJGKF027906 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 9 Apr 2013 11:19:16 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r39GJFJf015833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Apr 2013 11:19:15 -0500
Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.34.203]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r39GJEHM004977; Tue, 9 Apr 2013 11:19:14 -0500 (CDT)
Message-ID: <5164403A.9040907@bell-labs.com>
Date: Tue, 09 Apr 2013 11:22:18 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130311 Thunderbird/17.0.4
MIME-Version: 1.0
To: draft-ietf-mpls-tp-ring-protection@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: General Area Review Team <gen-art@ietf.org>, mpls-chairs@tools.ietf.org, loa@pi.nu
Subject: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-ring-protection-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 16:19:18 -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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-mpls-tp-ring-protection-05
Reviewer: Vijay K. Gurbani
Review Date: Apr-09-2013
IETF LC End Date: Apr-18-2013
IESG Telechat date: Not known

This document is ready as an Informational.  Some comments for
changes follow.

Major: 0
Minor: 0
Nits: 3

Nits:

- S1.1, bullet numbered 3: s/actionis/action is/
- S2, header "P2P Ring Protection": In the header, "P2P" probably
  refers to "Point-to-Point" and not "Peer-to-Peer".  It is okay
  to leave it as such if you think that the readers in the MPLS
  domain will interpret it as "Point-to-Point", but if you think
  it will help to folks (like me) who do not normally work at the
  network layer then it may be worth expanding the acronym out
  in the header.  (FWIW, I initially assumed "P2P" stood for
  "Peer-to-Peer".)
- S2.1, s/mis-connectivity, should/mis-connectivity should/

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From piyush@ditenity.com  Tue Apr  9 09:34:54 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAED521F8FD4 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 09:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level: 
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[AWL=1.174,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 1VTgILQNlQ16 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 09:34:53 -0700 (PDT)
Received: from mail-gh0-f174.google.com (mail-gh0-f174.google.com [209.85.160.174]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC2D21F8FE8 for <gen-art@ietf.org>; Tue,  9 Apr 2013 09:34:52 -0700 (PDT)
Received: by mail-gh0-f174.google.com with SMTP id g10so1117354ghb.19 for <gen-art@ietf.org>; Tue, 09 Apr 2013 09:34:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language:x-gm-message-state; bh=JM3E/76VZJ4PPBpKxQkfjFurJGh5j2So+c4wzVXxXPc=; b=ccLpo+ey/v9lb6OQeQcTh81QbXsapk2K8duGUVOyGhqHB4JxtVQfuy6acDhCEKQFqo Q05q46bsRPpJunh2Ts8ae1yH50z/MA1vOG+ZYG3/7MB17WFA+EuP9JRXCjb/9n/vAJvv ETDPqrSooOoZo7gds5s1nkrFs5Ogk38Uu4FVRv0bAz4qc+kixIHYG322WFPnYNNtxz3b k7H84UX9A4epZYaem01bCK55pKVdNTDtsCZnM1yCwHIdD801BxZOER3qPuNvLNA3472U y7zs4f93iIIKaMSiKO/Ftg8QfnxdWWGMSOrfeHD0c4jM+Mtl/wS5F+dmlz3DS5j2M5dJ M3HA==
X-Received: by 10.236.184.135 with SMTP id s7mr15954465yhm.204.1365525291761;  Tue, 09 Apr 2013 09:34:51 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id h6sm44104867yhf.19.2013.04.09.09.34.49 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 09 Apr 2013 09:34:51 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: "'Black, David'" <david.black@emc.com>, "'Sean Turner'" <turners@ieca.com>
References: <003e01ce3077$5b6329f0$12297dd0$@ditenity.com> <20130403160532.EB4FD1A68A@ld9781.wdf.sap.corp> <00a401ce3092$0a1415d0$1e3c4170$@ditenity.com> <5163270C.20300@ieca.com> <07af01ce34a4$582df1d0$0889d570$@ditenity.com> <5163840F.2030508@ieca.com> <083601ce34e7$e3dcef40$ab96cdc0$@ditenity.com> <8D3D17ACE214DC429325B2B98F3AE71293E22D3E@MX15A.corp.emc.com> <08b901ce3534$e057b920$a1072b60$@ditenity.com> <8D3D17ACE214DC429325B2B98F3AE71293E22DA2@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293E22DA2@MX15A.corp.emc.com>
Date: Tue, 9 Apr 2013 09:34:39 -0700
Message-ID: <08fc01ce3540$229d3430$67d79c90$@ditenity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHHvIU0pEj95jqjILpXYwEgVOm34gLGPak8AXFeg0kBCCz4MwNWbgjOAWN27bMCjnis0AKXx8I0ApM6LM8B5fVHp5g+Niog
Content-Language: en-us
X-Gm-Message-State: ALoCoQnORkop+ol8y43vjus3nAZtoBScBfWI0Hb5ukisW74Gq6jB3FNbDoq8UOkR0ltvqjgbFl5h
Cc: ambarish@gmail.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, gen-art@ietf.org, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, sts@aaa-sec.com, pkix@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 16:34:54 -0000

> It may be useful to keep in mind that the CA may have issued the
"non-issued" certificate
[Piyush] 
This is what I think will be confusing to many implementers :), who did not
participate in the WG discussions.
But then, it is an assumption on my part and you for one have proved that
the assumption is not universally true.

I guess we can move on if no one else has an input on this and deal with it
later (if needed) when we get more feedback from implementers who sign up
for adopting this feature.

-Piyush


From christer.holmberg@ericsson.com  Tue Apr  9 10:30:29 2013
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18F8A21F9409 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 10:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, 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 2XZyWobBIdb2 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 10:30:25 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 3D34E21F93DC for <gen-art@ietf.org>; Tue,  9 Apr 2013 10:30:08 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f316d0000028db-f9-5164501f5e6d
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 74.BA.10459.F1054615; Tue,  9 Apr 2013 19:30:07 +0200 (CEST)
Received: from ESESSMB208.ericsson.se ([169.254.8.70]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.02.0318.004; Tue, 9 Apr 2013 19:30:06 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Peter Saint-Andre <psaintan@cisco.com>, Jari Arkko <jari.arkko@piuha.net>
Thread-Topic: [Gen-art] Genart review of draft-saintandre-urn-example-04
Thread-Index: Ac4pRisFlSpgfAcDRaa82hCaKlGLbQL35C0AAAA4oAAACFB5bg==
Date: Tue, 9 Apr 2013 17:30:05 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C31C688@ESESSMB208.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B133213@ESESSMB209.ericsson.se> <E3B4A390-1812-4E8A-AA6D-EB2B98859F8A@piuha.net>, <9667F45D-66BC-4BF7-8316-66329B20C061@cisco.com>
In-Reply-To: <9667F45D-66BC-4BF7-8316-66329B20C061@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C31C688ESESSMB208erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFLMWRmVeSWpSXmKPExsUyM+Jvra58QEqgwZ/DYhY3Jnxmsbj6CkjM 2LeCzeLe8hY2BxaPKb83snosWfKTyWPrkulsHl8uf2YLYInisklJzcksSy3St0vgyli8ej1T wUL3is2P+pgaGL/adjFyckgImEhMmzODDcIWk7hwbz2QzcUhJHCYUeLoqVZ2CGcRo8T5Oy2s XYwcHGwCFhLd/7RBGkQEfCUOnJ3KClLDLNDHKPHi5ksmkISwgLvE5x2nmSCKPCRerFvCBmE7 SVz6OQtsDouAisTEz9wgYV6gOV3TL7BA7FrPKNF+czI7SA2ngK3Eok2KIDWMQMd9P7UGbCSz gLjErSfzmSCOFpBYsuc8M4QtKvHy8T+w8cwC+RINk2ogxgtKnJz5hGUCo8gsJN2zEKpmIamC KDGQeH9uPjOErS2xbOFrKFtfYuOXs4zI4gsY2VcxsucmZuaklxtuYgTG18Etv3V3MJ46J3KI UZqDRUmcN8z1QoCQQHpiSWp2ampBalF8UWlOavEhRiYOTqkGRmO9RZ5nb2RrHNg/Vcc44OmJ zld3Sr+WSO5ZXJFoFODXumdmhZ7m9oML97tlaF095sya7fu97zL/E65TTRW2QcdObXrOMdvr nMWUc1NdYo9vs+AR7Gv+9sWa9WG0YM2unz6b1L49+vd4HkfIoZNrd1oFb0o7wth6guWSJq8w w/vJJideSni33FJiKc5INNRiLipOBAAejPYgfQIAAA==
Cc: "gen-art_ietf.org" <gen-art@ietf.org>, "draft-saintandre-urn-example.all_tools.ietf.org" <draft-saintandre-urn-example.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-saintandre-urn-example-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 17:30:29 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1C31C688ESESSMB208erics_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

The suggested change looks ok to me.

Thanks!

Regards,

Christer



Sent from Windows using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Peter Saint-Andre [psaintan@cisco.com]
To: Jari Arkko [jari.arkko@piuha.net]
CC: Christer Holmberg [christer.holmberg@ericsson.com]; gen-art@ietf.org [g=
en-art@ietf.org]; draft-saintandre-urn-example.all@tools.ietf.org [draft-sa=
intandre-urn-example.all@tools.ietf.org]
Subject: Re: [Gen-art] Genart review of draft-saintandre-urn-example-04
On Apr 9, 2013, at 9:25 AM, Jari Arkko wrote:

Thanks for your review, Christer. The document is up for discussion in this=
 week's IESG telechat (on Thursday).

Peter: Have you seen Christer's question about Section 2.6?

Sorry, I had missed Christer's review. That text is an artifact of when the=
 document was Informational, not BCP. I suggest:

OLD

   As a
   result, implementers are counselled against using example URNs for
   any purposes other than documentation, private testing, and truly
   experimental contexts.

NEW

   Therefore, it is NOT RECOMMENDED for implementers to use example

   URNs for any purposes other than documentation, private testing,

   and truly experimental contexts.


Jari

On Mar 25, 2013, at 12:48 PM, Christer Holmberg <christer.holmberg@ericsson=
.com<mailto:christer.holmberg@ericsson.com>> wrote:

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>

Document:                         draft-saintandre-urn-example-04

Reviewer:                           Christer Holmberg

Review Date:                     25 March 2013

IETF LC End Date:             9 April 2013

IETF Telechat Date           11 April 2013

Summary:  The draft is well written, with a very minor editorial comment, a=
nd is ready for publication.

Major Issues: None

Minor Issues: None

Editorial nits: Section 2.6 contains the word =93counseled=94. While not wr=
ong, is there a reason why more common IETF language can=92t be used here? =
E.g. =93recommended against=94, or something? :)

Best regards,

Christer

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



--_000_7594FB04B1934943A5C02806D1A2204B1C31C688ESESSMB208erics_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap:break-word">
<div><span style=3D"color:black; font-family:Calibri,Arial,Helvetica,sans-s=
erif; font-size:11pt">Hi,</span></div>
<div>&nbsp;</div>
<div><font face=3D"Calibri">The suggested change looks ok to me.</font></di=
v>
<div><font face=3D"Calibri"></font>&nbsp;</div>
<div><font face=3D"Calibri">Thanks!</font></div>
<div><font face=3D"Calibri"></font>&nbsp;</div>
<div><font face=3D"Calibri">Regards,</font></div>
<div><font face=3D"Calibri"></font>&nbsp;</div>
<div><font face=3D"Calibri">Christer</font></div>
<span style=3D"color:black; font-family:Calibri,Arial,Helvetica,sans-serif;=
 font-size:11pt">
<div>&nbsp;</div>
<div><br>
<br>
Sent from <b><i>Windows</i></b> using <b style=3D"color:blue">TouchDown</b>=
 (www.nitrodesk.com)</div>
</span>
<div></div>
<br>
<span style=3D"color:black">-----Original Message-----<br>
<b>From:</b> Peter Saint-Andre [psaintan@cisco.com]<br>
<b>To:</b> Jari Arkko [jari.arkko@piuha.net]<br>
<b>CC:</b> Christer Holmberg [christer.holmberg@ericsson.com]; gen-art@ietf=
.org [gen-art@ietf.org]; draft-saintandre-urn-example.all@tools.ietf.org [d=
raft-saintandre-urn-example.all@tools.ietf.org]<br>
<b>Subject:</b> Re: [Gen-art] Genart review of draft-saintandre-urn-example=
-04</span>
<div>
<div>
<div>On Apr 9, 2013, at 9:25 AM, Jari Arkko wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div>Thanks for your review, Christer. The document is up for discussion in=
 this week's IESG telechat (on Thursday).<br>
<br>
Peter: Have you seen Christer's question about Section 2.6?<br>
</div>
</blockquote>
<div><br>
</div>
Sorry, I had missed Christer's review. That text is an artifact of when the=
 document was Informational, not BCP. I suggest:</div>
<div><br>
</div>
<div>OLD</div>
<div><span class=3D"Apple-style-span" style=3D"font-size:16px; font-family:=
Times">
<pre class=3D"newpage" style=3D"font-size:1em; margin-top:0px; margin-botto=
m:0px; page-break-before:always">   As a
   result, implementers are counselled against using example URNs for
   any purposes other than documentation, private testing, and truly
   experimental contexts.</pre>
</span></div>
<div>NEW</div>
<div><span class=3D"Apple-style-span" style=3D"font-size:16px; font-family:=
Times">
<pre class=3D"newpage" style=3D"font-size:1em; margin-top:0px; margin-botto=
m:0px; page-break-before:always">   Therefore, it is NOT RECOMMENDED for im=
plementers to use example&nbsp;</pre>
<pre class=3D"newpage" style=3D"font-size:1em; margin-top:0px; margin-botto=
m:0px; page-break-before:always">   URNs for any purposes other than docume=
ntation, private testing,&nbsp;</pre>
<pre class=3D"newpage" style=3D"font-size:1em; margin-top:0px; margin-botto=
m:0px; page-break-before:always">   and truly experimental contexts.</pre>
<pre class=3D"newpage" style=3D"font-size:1em; margin-top:0px; margin-botto=
m:0px; page-break-before:always"><br></pre>
</span></div>
<div>
<blockquote type=3D"cite">
<div><br>
Jari<br>
<br>
On Mar 25, 2013, at 12:48 PM, Christer Holmberg &lt;<a href=3D"mailto:chris=
ter.holmberg@ericsson.com">christer.holmberg@ericsson.com</a>&gt; wrote:<br=
>
<br>
<blockquote type=3D"cite">I am the assigned Gen-ART reviewer for this draft=
. For background on Gen-ART, please see the FAQ at &lt;<a href=3D"http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq</a>&gt;<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Document: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;draft-saintandre-urn-example-04<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Reviewer: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Christer Holmberg<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Review Date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;25 March 2013<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">IETF LC End Date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9 April 2013<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">IETF Telechat Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11 April 2013<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Summary: &nbsp;The draft is well written, with a =
very minor editorial comment, and is ready for publication.<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Major Issues: None<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Minor Issues: None<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Editorial nits: Section 2.6 contains the word =93=
counseled=94. While not wrong, is there a reason why more common IETF langu=
age can=92t be used here? E.g. =93recommended against=94, or something? :)<=
br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Best regards,<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Christer<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">_______________________________________________<b=
r>
</blockquote>
<blockquote type=3D"cite">Gen-art mailing list<br>
</blockquote>
<blockquote type=3D"cite"><a href=3D"mailto:Gen-art@ietf.org">Gen-art@ietf.=
org</a><br>
</blockquote>
<blockquote type=3D"cite"><a href=3D"https://www.ietf.org/mailman/listinfo/=
gen-art">https://www.ietf.org/mailman/listinfo/gen-art</a><br>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1C31C688ESESSMB208erics_--

From peter@akayla.com  Tue Apr  9 11:57:55 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00B9F21F960D; Tue,  9 Apr 2013 11:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 jUJ8k1c9zHHE; Tue,  9 Apr 2013 11:57:54 -0700 (PDT)
Received: from p3plsmtpa11-08.prod.phx3.secureserver.net (p3plsmtpa11-08.prod.phx3.secureserver.net [68.178.252.109]) by ietfa.amsl.com (Postfix) with ESMTP id 4919421F95EB; Tue,  9 Apr 2013 11:57:54 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa11-08.prod.phx3.secureserver.net with  id Muxo1l00C1huGat01uxo6e; Tue, 09 Apr 2013 11:57:50 -0700
From: "Peter Yee" <peter@akayla.com>
To: <mohamed.boucadair@orange.com>, <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
References: <054201ce34fa$0746ec80$15d4c580$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr>
Date: Tue, 9 Apr 2013 11:57:50 -0700
Message-ID: <059701ce3554$235aa0b0$6a0fe210$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGru2VgIxcOQENUYzhlyQVOZ0pm1wHHP5CkmQTyuIA=
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 18:57:55 -0000

Med,
	Thanks for the swift response to my review.  See my one reply
inline.

		Kind regards,
		-Peter

>>Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP 
>>error other than a short-lifetime error, or in the case of a failed 
>>resend, any PCP error at all.  The wording makes it seem like the 
>>short-lifetime errors are somehow not PCP errors and is therefore 
>>confusing.  It also doesn't explicitly deal with how many repeats should
be done on a resend.

>[Med] The basic behavior is to relay the received error to the UPnP CP. For
the short-lifetime errors, the IWF may decide to resend the request and not
relay those errors immediately to the UPnP CP. The number of repeats is not
specified here as it can be implementation-specific. 

Your explanation is fine.  I just found the wording "If a PCP  error
response is received" to sound ambiguously as if the short-lifetime errors
were not a subset of PCP errors.



From housley@vigilsec.com  Tue Apr  9 15:36:25 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E63C421F90BB; Tue,  9 Apr 2013 15:36:25 -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 eExCO2rGBBNc; Tue,  9 Apr 2013 15:36:24 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id B1E8421F9051; Tue,  9 Apr 2013 15:36:24 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id B50D89A4112; Tue,  9 Apr 2013 18:36:29 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id KKu1GypQBele; Tue,  9 Apr 2013 18:36:20 -0400 (EDT)
Received: from [192.168.2.100] (pool-173-79-232-68.washdc.fios.verizon.net [173.79.232.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id CC52F9A410F; Tue,  9 Apr 2013 18:36:27 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293D371CF@MX15A.corp.emc.com>
Date: Tue, 9 Apr 2013 18:36:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <34B1BF5C-9A14-4B86-BA51-9780F2832ACF@vigilsec.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E055F69357F@MX14A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293AEEDC8@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293D371CF@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF Gen-ART <gen-art@ietf.org>, savi@ietf.org, Fred Baker <fred@cisco.com>, IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-savi-threat-scope-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 22:36:26 -0000

David:

Thanks for your efforts on this document.  Your first review was in May =
2011, and the document has improved greatly for you continued pushing on =
the concerns.

Russ


On Apr 3, 2013, at 1:04 PM, Black, David wrote:

> The -07 version of this draft resolves all of the issues raised by the =
Gen-ART
> review of the -06 version.  Discussion of the review with the authors =
has
> resulted in a common understanding that there is no need for =
additional text
> on statically allowing all source addresses through all links in a set =
of
> teamed/aggregated links - that's at best "nice to have" for this =
draft, but
> not essential.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Black, David
>> Sent: Monday, March 25, 2013 9:04 PM
>> To: McPherson, Danny; Fred Baker; joel.halpern@ericsson.com; =
gen-art@ietf.org
>> Cc: Jean-Michel Combes; Ted Lemon; savi@ietf.org; Black, David; =
ietf@ietf.org
>> Subject: Gen-ART review of draft-ietf-savi-threat-scope-06
>>=20
>> I have been selected as the General Area Review Team (Gen-ART) =
reviewer
>> for this draft (for background on Gen-ART, please see
>> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>>=20
>> Please wait for direction from your document shepherd or
>> AD before posting a new version of the draft.
>>=20
>> Document: draft-ietf-savi-threat-scope-06
>> Reviewer: David L. Black
>> Review Date: March 27, 2013
>> IESG Telechat Date: (if known)
>>=20
>> Summary: This draft is on the right track, but has open issues, =
described in
>> the review.
>>=20
>> Looking at the original Gen-ART review of the -05 draft and checking =
the diffs
>> between -05 and -06, the issues raised by that review have only been =
partially
>> addressed:
>>=20
>>> There is no discussion of link teaming or aggregation (e.g., via =
LACP); this
>>> may affect source address validation functionality by requiring the =
same
>>> validation checks on all aggregated ports.  An important case to =
discuss
>>> is where the aggregated host links are connected to ports on =
different
>>> switches (e.g., in an active/passive configuration).
>>=20
>> This is partially addressed on 4.1.2 (new section in -06), but only =
in terms
>> of moving validation state when something like LACP reconfigures.  =
This has a
>> couple of shortcomings:
>> a) the alternative of statically  allowing all source addresses =
through all
>> 	teamed/aggregated links (decouples SAVI state from link
>> teaming/aggregation
>> 	state) should also be mentioned, and
>> b) the new text implies that LACP is the only way to cause this =
situation -
>> it's
>> 	not, so LACP should be used as an example.  VRRP is another =
example.
>>=20
>>> (1) Some of the software switch implementations are single instance =
switches
>>> whose implementation is distributed across multiple physical =
servers.  This
>>> results in concerns similar to the link aggregation discussion =
above.
>>=20
>> I don't think this has been addressed, but the notion of =
single-instance
>> switches
>> could be added to the generalization of the new text in 4.1.2.
>>=20
>>> (2) Live migration of virtual machines among physical servers causes
>>> relocation of MAC addresses across switch ports.  A so-called =
"gratuitous
>> ARP"
>>> is often used to inform the network of the MAC address move; =
port-based
>>> source address validation information needs to move in response to =
such
>> ARPs.
>>>=20
>>> (3) MAC address relocation is also used as a failure recovery =
technique; the
>>> surviving hardware element (e.g., host in a cluster) takes over the =
MAC
>>> addresses of the failed hardware; like the previous case, a =
"gratuitous ARP"
>>> is a common means of informing the network that the MAC address has =
moved,
>>> and source address validation information needs to move in response =
to it.
>>>=20
>>> Minor issues:
>>>=20
>>> There doesn't seem to be much discussion of dynamic network =
reconfiguration,
>>> which may change traffic egress points.  VRRP may be a useful =
example to
>>> discuss beyond the typical routing protocol updates to forwarding =
tables.
>>=20
>> A paragraph has been added to 5.2.3 to address all three of the above
>> concerns.
>> I guess that's ok, but I would have liked to see some text pointing =
out that a
>> MAC move can be detected by the switches and used to update SAVI =
state about
>> which port(s) a MAC is accessed through.
>>=20
>> Thanks,
>> --David
>>=20
>>> -----Original Message-----
>>> From: Black, David
>>> Sent: Friday, May 13, 2011 1:03 AM
>>> To: McPherson, Danny; Fred Baker; joel.halpern@ericsson.com; gen-
>> art@ietf.org
>>> Cc: Black, David; Christian Vogt; Jean-Michel Combes; Jari Arkko;
>>> savi@ietf.org
>>> Subject: Gen-ART review of draft-ietf-savi-threat-scope-05
>>>=20
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>=20
>>> Please resolve these comments along with any other Last Call =
comments
>>> you may receive.
>>>=20
>>> Document: draft-ietf-savi-threat-scope-05
>>> Reviewer: David L. Black
>>> Review Date: 12 May 2011
>>> IETF LC End Date: 18 May 2011
>>>=20
>>> Summary: This draft is on the right track, but has open issues, =
described in
>>> the review.
>>>=20
>>> This draft discusses the threats and deployment environment for IP =
source
>>> address validation with particular attention to finer-grain =
validation that
>>> could be used within a network to validate IP addresses closer to =
the
>> sources
>>> of network traffic than ingress to an ISP's network.
>>>=20
>>> Major issues:
>>>=20
>>> There is no discussion of link teaming or aggregation (e.g., via =
LACP); this
>>> may affect source address validation functionality by requiring the =
same
>>> validation checks on all aggregated ports.  An important case to =
discuss
>>> is where the aggregated host links are connected to ports on =
different
>>> switches
>>> (e.g., in an active/passive configuration).
>>>=20
>>> The discussion of multi-instance hosts in section 5.2.3 is =
incomplete
>>> in several important aspects:
>>>=20
>>> (1) Some of the software switch implementations are single instance =
switches
>>> whose implementation is distributed across multiple physical =
servers.  This
>>> results in concerns similar to the link aggregation discussion =
above.
>>>=20
>>> (2) Live migration of virtual machines among physical servers causes
>>> relocation of MAC addresses across switch ports.  A so-called =
"gratuitous
>> ARP"
>>> is often used to inform the network of the MAC address move; =
port-based
>>> source address validation information needs to move in response to =
such
>> ARPs.
>>>=20
>>> (3) MAC address relocation is also used as a failure recovery =
technique; the
>>> surviving hardware element (e.g., host in a cluster) takes over the =
MAC
>>> addresses of the failed hardware; like the previous case, a =
"gratuitous ARP"
>>> is a common means of informing the network that the MAC address has =
moved,
>>> and source address validation information needs to move in response =
to it.
>>>=20
>>> Minor issues:
>>>=20
>>> There doesn't seem to be much discussion of dynamic network =
reconfiguration,
>>> which may change traffic egress points.  VRRP may be a useful =
example to
>>> discuss beyond the typical routing protocol updates to forwarding =
tables.
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> idnits 2.12.11 ran clean.
>>>=20
>>> Thanks,
>>> --David
>>> ----------------------------------------------------
>>> David L. Black, Distinguished Engineer
>>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>>> david.black@emc.com        Mobile: +1 (978) 394-7754
>>> ----------------------------------------------------
>>>=20
>=20


From Ted.Lemon@nominum.com  Tue Apr  9 17:30:02 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C65A521F98CE; Tue,  9 Apr 2013 17:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 kmy5Pn66JXMQ; Tue,  9 Apr 2013 17:30:02 -0700 (PDT)
Received: from exprod7og129.obsmtp.com (exprod7og129.obsmtp.com [64.18.2.122]) by ietfa.amsl.com (Postfix) with ESMTP id 1592521F98A4; Tue,  9 Apr 2013 17:30:01 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob129.postini.com ([64.18.6.12]) with SMTP ID DSNKUWSyiQyJGuHL2v8H7olDkAUw+VBzTHxz@postini.com; Tue, 09 Apr 2013 17:30:02 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7423B1B87B0; Tue,  9 Apr 2013 17:30:01 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6B970190061; Tue,  9 Apr 2013 17:30:01 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 9 Apr 2013 17:30:01 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Russ Housley <housley@vigilsec.com>
Thread-Topic: Gen-ART review of draft-ietf-savi-threat-scope-07
Thread-Index: AQHOMI1VsmvJehwUjES862bjgyecEJjO+YyAgAAfwwA=
Date: Wed, 10 Apr 2013 00:30:01 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077513B7E4@mbx-01.win.nominum.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E055F69357F@MX14A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293AEEDC8@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293D371CF@MX15A.corp.emc.com> <34B1BF5C-9A14-4B86-BA51-9780F2832ACF@vigilsec.com>
In-Reply-To: <34B1BF5C-9A14-4B86-BA51-9780F2832ACF@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D734FF2B9DAEB9469441AB80801ACC46@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<savi@ietf.org>" <savi@ietf.org>, IETF Gen-ART <gen-art@ietf.org>, IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-savi-threat-scope-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2013 00:30:02 -0000

On Apr 9, 2013, at 6:36 PM, Russ Housley <housley@vigilsec.com> wrote:
> Thanks for your efforts on this document.  Your first review was in May 2=
011, and the document has improved greatly for you continued pushing on the=
 concerns.

Can we take this to mean that the concerns expressed in your now-deprecated=
 DISCUSS have been successfully addressed?


From stefan@aaa-sec.com  Tue Apr  9 21:31:10 2013
Return-Path: <stefan@aaa-sec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21EEE21F92F4 for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 21:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 a12XzQzp6A4U for <gen-art@ietfa.amsl.com>; Tue,  9 Apr 2013 21:31:09 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.113]) by ietfa.amsl.com (Postfix) with ESMTP id AA99B21F92E8 for <gen-art@ietf.org>; Tue,  9 Apr 2013 21:31:06 -0700 (PDT)
Received: from s87.loopia.se (localhost [127.0.0.1]) by s87.loopia.se (Postfix) with ESMTP id 3F18D203CF6B for <gen-art@ietf.org>; Wed, 10 Apr 2013 06:31:02 +0200 (CEST)
X-Virus-Scanned: amavisd-new at outgoing-smtp.loopia.se
Received: from s87.loopia.se ([127.0.0.1]) by s87.loopia.se (s87.loopia.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id S4gYHfdnMuyw for <gen-art@ietf.org>; Wed, 10 Apr 2013 06:31:01 +0200 (CEST)
Received: from s327.loopia.se (s34.loopia.se [194.9.94.70]) by s87.loopia.se (Postfix) with ESMTP id DA4E3203CF72 for <gen-art@ietf.org>; Wed, 10 Apr 2013 06:31:01 +0200 (CEST)
Received: (qmail 14616 invoked from network); 10 Apr 2013 04:31:01 -0000
Received: from 81-236-19-140-no39.tbcn.telia.com (HELO [192.168.1.69]) (stefan@fiddler.nu@[81.236.19.140]) (envelope-sender <stefan@aaa-sec.com>) by s327.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <piyush@ditenity.com>; 10 Apr 2013 04:31:01 -0000
User-Agent: Microsoft-MacOutlook/14.3.2.130206
Date: Wed, 10 Apr 2013 06:30:57 +0100
From: Stefan Santesson <stefan@aaa-sec.com>
To: Piyush Jain <piyush@ditenity.com>, "'Black, David'" <david.black@emc.com>, 'Sean Turner' <turners@ieca.com>
Message-ID: <CD8AB3B0.60302%stefan@aaa-sec.com>
Thread-Topic: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
In-Reply-To: <08d601ce3538$c67d1550$53773ff0$@ditenity.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: ambarish@gmail.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, gen-art@ietf.org, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, sts@aaa-sec.com, pkix@ietf.org
Subject: Re: [Gen-art] [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2013 04:31:10 -0000

It is impossible to write a text that cannot deliberately be misunderstood.

This debate is so full of constructed, non-existent problems.

Nothing has changed for the clients. The client can receive an error, or
they can receive (good, revoked or unknown).
The meaning of those responses are pretty clearly explained.

The only thing we talk about here is an extremely unlikely and rare
exception case where the responder is allowed to respond revoked even if a
cert was never issued.

I'm sorry to say, but this is getting ridiculous.

/Stefan



On 4/9/13 4:41 PM, "Piyush Jain" <piyush@ditenity.com> wrote:

>> I'd rather not try to describe what clients should do or expect in terms
>of
>> non-issued certificates.
>> Clients are really not meant to know anything beyond "revoked" = this
>>cert
>> should not be trusted.
>[Piyush] 
>Thanks for clarifying your position on this Stefan.
>This is the position I disagree with. I think several people in the WG
>expressed that the meaning should be clearly conveyed if "revoked" is
>extended to communicate "non-issued".  Expectation that clients should
>treat
>these responses as normal revoked is not aligned with WG consensus IMO.
>> 
>> This is a server choice to prevent the requested cert (if it exist at
>>all)
>from
>> being accepted.
>> For requests for real certs, issued by a trusted CA, this case will
>>never
>even
>> occur unless the CA is compromised.
>[Piyush]
> And I think this is the only case that is interesting to the clients. I
>combed through the WG discussion and did not find a single case being
>discussed where clients benefit from sending OCSP requests for serial
>numbers for non-existent certificates.
>
>> And, if I put something in, given the discussion so far, the chance that
>there
>> will be some major disagreements with it, is really high.
>[Piyush]
>These are the issues that implementers will have to deal with. If there
>are
>going to be disagreement, they should be dealt with before the document is
>published IMO, unless 2560bis is considered a stop gap measure and OCSP v2
>is on the radar.
>I understand the desire to wrap up the pending documents so pkix can be
>disbanded on schedule. However, I'll leave that to the AD to decide that
>the
>benefits of meeting that schedule outweighs the cons of publishing a
>document that can potentially lead to confusion among implementers.
>
>
>



From mohamed.boucadair@orange.com  Tue Apr  9 23:53:05 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9445721F8972; Tue,  9 Apr 2013 23:53:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 LgSO57z68hJ8; Tue,  9 Apr 2013 23:53:05 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id BC0E321F8470; Tue,  9 Apr 2013 23:53:04 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id ED2BA2DC35A; Wed, 10 Apr 2013 08:53:03 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id CF75D23808A; Wed, 10 Apr 2013 08:53:03 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Wed, 10 Apr 2013 08:53:03 +0200
From: <mohamed.boucadair@orange.com>
To: Peter Yee <peter@akayla.com>, "draft-ietf-intarea-nat-reveal-analysis.all@tools.ietf.org" <draft-ietf-intarea-nat-reveal-analysis.all@tools.ietf.org>
Date: Wed, 10 Apr 2013 08:53:02 +0200
Thread-Topic: Gen-ART review of draft-ietf-intarea-nat-reveal-analysis-06
Thread-Index: Ac4yVqRs/Mt47fa6QWSvsgPU2PDQHwDYPtrg
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC1AE7905@PUEXCB1B.nanterre.francetelecom.fr>
References: <030101ce3259$2b900520$82b00f60$@akayla.com>
In-Reply-To: <030101ce3259$2b900520$82b00f60$@akayla.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.4.10.60351
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-intarea-nat-reveal-analysis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2013 06:53:05 -0000

RGVhciBQZXRlciwNCg0KVGhlIHR3byBPTEQgbml0cyBhcmUgYWxyZWFkeSBmaXhlZCBpbiBteSBs
b2NhbCBjb3B5Lg0KDQpBcyBmb3IgdGhlIG5ldyBvbmUsIEknbSBnZW5lcmF0aW5nIHRoZSByZWZl
cmVuY2VzIGF1dG9tYXRpY2FsbHkuIFRoZSBSRkMgRWRpdG9yIGNhbiBmaXggdGhpcyBpZiBuZWVk
ZWQuDQoNClRoYW5rcy4NCg0KQ2hlZXJzLA0KTWVkDQoNCj4tLS0tLU1lc3NhZ2UgZCdvcmlnaW5l
LS0tLS0NCj5EZcKgOiBQZXRlciBZZWUgW21haWx0bzpwZXRlckBha2F5bGEuY29tXQ0KPkVudm95
w6nCoDogc2FtZWRpIDYgYXZyaWwgMjAxMyAwMTo1Ng0KPsOAwqA6IGRyYWZ0LWlldGYtaW50YXJl
YS1uYXQtcmV2ZWFsLWFuYWx5c2lzLmFsbEB0b29scy5pZXRmLm9yZw0KPkNjwqA6IGdlbi1hcnRA
aWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCj5PYmpldMKgOiBHZW4tQVJUIHJldmlldyBvZiBkcmFm
dC1pZXRmLWludGFyZWEtbmF0LXJldmVhbC1hbmFseXNpcy0wNg0KPg0KPkkgYW0gdGhlIGFzc2ln
bmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZvciBiYWNrZ3JvdW5kIG9uIEdl
bi0NCj5BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPjxodHRwOi8vd2lraS50b29scy5pZXRm
Lm9yZy9hcmVhL2dlbi90cmFjL3dpa2kvR2VuQXJ0ZmFxPg0KPg0KPlBsZWFzZSB3YWl0IGZvciBk
aXJlY3Rpb24gZnJvbSB5b3VyIGRvY3VtZW50IHNoZXBoZXJkIG9yIEFEIGJlZm9yZSBwb3N0aW5n
DQo+YSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQo+DQo+RG9jdW1lbnQ6IGRyYWZ0LWlldGYt
aW50YXJlYS1uYXQtcmV2ZWFsLWFuYWx5c2lzLTA2DQo+UmV2aWV3ZXI6IFBldGVyIFllZQ0KPlJl
dmlldyBEYXRlOiBBcHItNS0yMDEzDQo+SUVURiBMQyBFbmQgRGF0ZTogTWFyLTgtMjAxMw0KPklF
U0cgVGVsZWNoYXQgZGF0ZTogQXByLTExLTIwMTMNCj4NCj5UaGlzIGRyYWZ0IGlzIGJhc2ljYWxs
eSByZWFkeSBmb3IgcHVibGljYXRpb24sIGJ1dCBoYXMgbml0cyB0aGF0IHNob3VsZCBiZQ0KPmZp
eGVkIGJlZm9yZSBwdWJsaWNhdGlvbi4gW1JlYWR5IHdpdGggbml0c10NCj4NCj5JdCBhZGRyZXNz
ZXMgbW9zdCBvZiB0aGUgaXNzdWVzIHJhaXNlZCBpbiBteSByZXZpZXcgb2YgdGhlIC0wNSB2ZXJz
aW9uLg0KPlR3byBpdGVtcyBmcm9tIHRoYXQgcmV2aWV3IHRoYXQgSSdtDQo+cmV2aXNpdGluZyBh
cmUgbm90ZWQgYmVsb3cgd2l0aCB0ZXh0IGZyb20gdGhlIG9yaWdpbmFsIHJldmlldyBhbmQgcmVz
cG9uc2VzDQo+ZnJvbSBvbmUgb2YgdGhlIGF1dGhvcnMgKE1lZCkuDQo+V2UgYWdyZWVkIHRoYXQg
dGhvc2UgdHdvIHJldmlzaXRlZCBpdGVtcyBjb3VsZCBiZSBhZGRyZXNzZWQgaW4gYSBzdWJzZXF1
ZW50DQo+cmV2aXNpb247IHRoZXkgYXJlIGp1c3QNCj5yZWNvcmRlZCBoZXJlIGZvciBlYXNlIG9m
IHJlZmVyZW5jZS4NCj4NCj5NYWpvciBpc3N1ZXM6DQo+DQo+TWlub3IgaXNzdWVzOg0KPg0KPk5p
dHM6DQo+DQo+W09sZF0NCj4NCj4+PlNlY3Rpb24gMy4xLCA1dGggcGFyYWdyYXBoOiBJIGRvbid0
IHF1aXRlIGZvbGxvdyB3aGF0J3MgYmVpbmcgc2FpZCBoZXJlLg0KPj4+SXMgdGhlIHBvaW50IHRo
YXQgdGhlIGFkZHJlc3Mtc2hhcmluZyBmdW5jdGlvbiBzaG91bGQgcmV2ZWFsIHRoZSBzYW1lDQo+
Pj5IT1NUX0lEIGZvciBhbnkgZ2l2ZW4gaG9zdCByZWdhcmRsZXNzIG9mIHdoYXQgbGF5ZXIgb3Ig
bWVjaGFuaXNtIHRoYXQNCj4+PkhPU1RfSUQgaXMgYmVpbmcgY29udmV5ZWQgYWNyb3NzPyAgSG93
IGRvZXMgdGhpcyByZWxhdGUgdG8NCj4+PmludGVyZmVyZW5jZSBiZXR3ZWVuIEhPU1RfSURzPw0K
Pg0KPj5NZWQ6IFRoZSBwb2ludCBpczogd2hlbiBzZXZlcmFsIGxheWVycyBhcmUgdXNlZCB0byBp
bmplY3QgYSBob3N0X2lkLCB0aGUNCj5kZXZpY2Ugc2hvdWxkIGNoZWNrIHRoZSBzYW1lIHN1YnNl
dCBvZiBpbmZvcm1hdGlvbiBpcyByZXZlYWxlZC4gRm9yDQo+aW5zdGFuY2UsIHRoZXJlIHNob3Vs
ZCBub3QgYmUgY29uZmxpY3QsIGV0Yy4NCj4NCj5UaGVuIHBlcmhhcHMgeW91IGNvdWxkIHJld29y
ZCBzbyB0aGF0ICJzaG91bGQgcmV2ZWFsIHN1YnNldHMgb2YgdGhlIHNhbWUNCj5pbmZvcm1hdGlv
biIgYmVjb21lcyAic2hvdWxkIHJldmVhbCB0aGUgc2FtZSBzdWJzZXRzIG9mIGluZm9ybWF0aW9u
IGF0IGVhY2gNCj5sYXllciI/DQo+DQo+Pj5TZWN0aW9uIDQuOS4yLCA0dGggYnVsbGV0IGl0ZW0s
IDJuZCBzZW50ZW5jZTogRGVsZXRlICJoZWF2eSBhbmQiIHVubGVzcw0KPnlvdSB3YW50IHRvDQo+
Pj5leHBsYWluIHdoYXQgaGVhdnkgbWVhbnMuDQo+DQo+Pk1lZDogRXN0YWJsaXNoaW5nIGFncmVl
bWVudHMgd2l0aCB0aGUgb3duZXIgb2YgdGhlIGFkZHJlc3Mgc2hhcmluZw0KPmZ1bmN0aW9uIGFu
ZCBvd25lcnMgb2Ygc2VydmVycyBpcyBoZWF2eS4gVGhpcyBpcyBhbHJlYWR5IG1lbnRpb25lZCBp
biB0aGUNCj50ZXh0Lg0KPg0KPlBlcmhhcHMgeW91IGNvdWxkIHJlcGxhY2UgImhlYXZ5IiB3aXRo
ICJidXJkZW5zb21lIi4NCj4NCj5bTmV3XQ0KPg0KPkluIHRoZSByZWZlcmVuY2VzLCB0aGVyZSBz
ZWVtIHRvIGJlIGFuIGV4Y2VzcyBvZiBjb21tYXMgaW4gYSBjb3VwbGUgb2YNCj5wbGFjZXMuICAg
TG9vayBmb3IgdGhlIHN0cmluZyAiLCAsIiAoY29tbWEgc3BhY2UgY29tbWEpIGFuZCB5b3UnbGwg
c2VlIHdoYXQNCj5JIG1lYW4uICBUaGUgZG9jdW1lbnQgdGl0bGVzIHN0YXJ0IHdpdGggYW4gZXh0
cmEgY29tbWEgYW5kIGVuZCB3aXRoIG9uZS4NCj4NCj5BbHNvIGluIHRoZSByZWZlcmVuY2VzLCBm
b3IgUkZDIDE0MTMsIHB1dCBhIHNwYWNlIGJldHdlZW4gdGhlICJNLiIgYW5kIHRoZQ0KPiJDLiIg
aW4gTWlrZSBTdC4gSm9obnMnIGluaXRpYWxzLg0KPg0KDQo=

From mohamed.boucadair@orange.com  Wed Apr 10 00:49:28 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 636FF21F8F1A; Wed, 10 Apr 2013 00:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level: 
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799, UNPARSEABLE_RELAY=0.001]
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 DDkryKzKuuaK; Wed, 10 Apr 2013 00:49:27 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id A066121F8F17; Wed, 10 Apr 2013 00:49:27 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 135533B47E9; Wed, 10 Apr 2013 09:49:27 +0200 (CEST)
Received: from puexch91.nanterre.francetelecom.fr (unknown [10.101.44.48]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id A1ABB27C0B4; Wed, 10 Apr 2013 09:49:26 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by puexch91.nanterre.francetelecom.fr ([10.101.44.48]) with mapi; Wed, 10 Apr 2013 09:49:26 +0200
From: <mohamed.boucadair@orange.com>
To: Peter Yee <peter@akayla.com>, "draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org" <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
Date: Wed, 10 Apr 2013 09:49:25 +0200
Thread-Topic: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Thread-Index: AQGru2VgIxcOQENUYzhlyQVOZ0pm1wHHP5CkmQTyuICAANuqoA==
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC1AE796C@PUEXCB1B.nanterre.francetelecom.fr>
References: <054201ce34fa$0746ec80$15d4c580$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr> <059701ce3554$235aa0b0$6a0fe210$@akayla.com>
In-Reply-To: <059701ce3554$235aa0b0$6a0fe210$@akayla.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.4.10.65417
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2013 07:49:28 -0000

Dear Peter,

I changed the text as follows:

OLD:

   If the requested external port is not available, the PCP server will
   send a CANNOT_PROVIDE_EXTERNAL error response.  If a short lifetime
   error is returned, the IGD-PCP IWF MAY re-send the same request to
   the PCP Server after 30 seconds.  If a PCP error response is
   received, the IGD-PCP IWF relays a negative message to the UPnP
   Control Point with ConflictInMappingEntry as the error code.

NEW:

   If the requested external port is not available, the PCP server will
   send a CANNOT_PROVIDE_EXTERNAL error response:

   1.  If a short lifetime error is returned, the IGD-PCP IWF MAY resend
       the same request to the PCP Server after 30 seconds without
       relaying the error to the UPnP Control Point.  The IGD-PCP IWF
       MAY repeat this process until a positive answer is received or
       some maximum retry limit is reached.  When the maximum retry
       limit is reached, the IGD-PCP IWF relays a negative message to
       the UPnP Control Point with ConflictInMappingEntry as the error
       code.

   2.  If a long lifetime error is returned, the IGD-PCP IWF relays a
       negative message to the UPnP Control Point with
       ConflictInMappingEntry as the error code.

Better?

Cheers,
Med

>-----Message d'origine-----
>De=A0: Peter Yee [mailto:peter@akayla.com]
>Envoy=E9=A0: mardi 9 avril 2013 20:58
>=C0=A0: BOUCADAIR Mohamed OLNC/OLN; draft-ietf-pcp-upnp-igd-
>interworking.all@tools.ietf.org
>Cc=A0: gen-art@ietf.org; ietf@ietf.org
>Objet=A0: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>
>Med,
>	Thanks for the swift response to my review.  See my one reply
>inline.
>
>		Kind regards,
>		-Peter
>
>>>Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP
>>>error other than a short-lifetime error, or in the case of a failed
>>>resend, any PCP error at all.  The wording makes it seem like the
>>>short-lifetime errors are somehow not PCP errors and is therefore
>>>confusing.  It also doesn't explicitly deal with how many repeats should
>be done on a resend.
>
>>[Med] The basic behavior is to relay the received error to the UPnP CP.
>For
>the short-lifetime errors, the IWF may decide to resend the request and no=
t
>relay those errors immediately to the UPnP CP. The number of repeats is no=
t
>specified here as it can be implementation-specific.
>
>Your explanation is fine.  I just found the wording "If a PCP  error
>response is received" to sound ambiguously as if the short-lifetime errors
>were not a subset of PCP errors.
>


From jari.arkko@piuha.net  Wed Apr 10 03:35:56 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93D6221F944C for <gen-art@ietfa.amsl.com>; Wed, 10 Apr 2013 03:35:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HbUFL-Ub-Lox for <gen-art@ietfa.amsl.com>; Wed, 10 Apr 2013 03:35:55 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 24E1921F94AF for <gen-art@ietf.org>; Wed, 10 Apr 2013 03:35:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6C3552CC57; Wed, 10 Apr 2013 13:35:54 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iG4EHlaw9i1v; Wed, 10 Apr 2013 13:35:52 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 770EC2CC4A; Wed, 10 Apr 2013 13:35:52 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293D36A70@MX15A.corp.emc.com>
Date: Wed, 10 Apr 2013 13:35:52 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE7ECDE4-A22E-40A0-AE53-5620DBB27491@piuha.net>
References: <8D3D17ACE214DC429325B2B98F3AE71293AEEDBC@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293D36A70@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1503)
Cc: ambarish@gmail.com, mmyers@fastq.com, slava.galperin@gmail.com, cadams@eecs.uottawa.ca, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, sts@aaa-sec.com
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pkix-rfc2560bis-16
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2013 10:35:56 -0000

Thank you for your review and re-review, David. I'm basing my =
recommendation for this document on your review. (Although some of the =
discussion still continues=85)

Jari

On Mar 29, 2013, at 1:15 AM, "Black, David" <david.black@emc.com> wrote:

> The -16 version of this draft resolves all of the concerns raised by =
the
> Gen-ART review of the -15 version.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Black, David
>> Sent: Monday, March 25, 2013 8:26 PM
>> To: sts@aaa-sec.com; mmyers@fastq.com; ambarish@gmail.com;
>> slava.galperin@gmail.com; cadams@eecs.uottawa.ca; gen-art@ietf.org
>> Cc: Black, David; pkix@ietf.org; Sean Turner; ietf@ietf.org
>> Subject: Gen-ART review of draft-ietf-pkix-rfc2560bis-15
>>=20
>> Authors,
>>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART,
>> please
>> see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments =
you may
>> receive.
>>=20
>> Document: draft-ietf-pkix-rfc2560bis-15
>> Reviewer: David L. Black
>> Review Date: March 25, 2013
>> IETF LC End Date: March 27, 2013
>>=20
>> Summary:
>> This draft is on the right track but has open issues, described in =
the review.
>>=20
>> This draft updates the OCSP protocol for obtaining certificate status
>> with some minor extensions.
>>=20
>> Because this is a "bis" draft, I reviewed the diffs against RFC 2560.
>>=20
>> I did not check the ASN.1.  I also did not see a writeup for this =
draft
>> in the data tracker, and so will rely on the document shepherd to
>> ensure that the ASN.1 has been checked when the writeup is prepared.
>>=20
>> I found five open issues, all of which are minor, plus one idnits =
item
>> that is probably ok, but should be double-checked.
>>=20
>> Minor issues:
>>=20
>> [1] Section 2.2:
>>=20
>> 	NOTE: The "revoked" state for known non-issued certificate =
serial
>> 		numbers is allowed in order to reduce the risk of =
relying
>> 		parties using CRLs as a fall back mechanism, which would =
be
>> 		considerably higher if an "unknown" response was =
returned.
>>=20
>> Given this explanation, I'm surprised that the use of "revoked" =
instead of
>> "unknown" for a known non-issued certificate is a "MAY" requirement =
and
>> not a "SHOULD" requirement.  Why is that the case?
>>=20
>> It appears that the reason is that the use of "revoked" in this =
situation
>> may be dangerous when serial numbers can be predicted for =
certificates that
>> will be issued in the future.  If that's what's going on, this =
concern is
>> already explained in the security considerations section, but it =
should
>> also be mentioned here for completeness.
>>=20
>> [2] Section 4.2.2.2:
>>=20
>> 	The key that signs a certificate's status information need not =
be the
>> 	same key that signed the certificate. It is necessary however to
>> 	ensure that the entity signing this information is authorized to =
do
>> 	so.  Therefore, a certificate's issuer MAY either sign the OCSP
>> 	responses itself or it MAY explicitly designate this authority =
to
>> 	another entity.
>>=20
>> The two instances of "MAY" in the above text were both "MUST" in RFC =
2560.
>>=20
>> The RFC 2560 text construction of "MUST" or "MUST" is a bit odd, but =
the two
>> "MAY"s in this draft are even worse, as they allow "MAY do something =
else
>> entirely", despite being enclosed in an either-or construct.  I =
strongly
>> suspect that the latter was not intended, so the following would be =
clearer:
>>=20
>> 	The key that signs a certificate's status information need not =
be the
>> 	same key that signed the certificate. It is necessary however to
>> 	ensure that the entity signing this information is authorized to =
do
>> 	so.  Therefore, a certificate's issuer MUST do one of the =
following:
>> 		- sign the OCSP responses itself, or
>> 		- explicitly designate this authority to another entity.
>>=20
>> [3] Section 4.3:
>>=20
>> Is the "SHOULD" requirement still appropriate for the DSA with SHA-1 =
combo
>> (vs. a "MAY" requirement)?  This requirement was a "MUST" in RFC =
2560, but
>> I wonder about actual usage of DSA in practice.
>>=20
>> [4] Section 5, last paragraph:
>>=20
>> 	Responding a "revoked" state to certificate that has never been
>> 	issued may enable someone to obtain a revocation response for a
>> 	certificate that is not yet issued, but soon will be issued, if =
the
>> 	CA issues certificates using sequential certificate serial =
number
>> 	assignment.
>>=20
>> The above text after starting with the "if" is too narrow - it should =
say:
>>=20
>> 	if the certificate serial number of the certificate that
>> 	will be issued can be predicted or guessed by the requester.
>> 	Such prediction is easy for a CA that issues certificates
>> 	using sequential certificate serial number assignment.
>>=20
>> There's also a nit in original text - its first line should be:
>>=20
>> 	Responding with a "revoked" state for a certificate that has =
never been
>>=20
>> [5] Section 5.1.1:
>>=20
>> 	In archival applications it is quite possible that an OCSP =
responder
>> 	might be asked to report the validity of a certificate on a date =
in
>> 	the distant past. Such a certificate might employ a signing =
method
>> 	that is no longer considered acceptably secure. In such
>> 	circumstances the responder MUST NOT generate a signature using =
a
>> 	signing mechanism that is not considered acceptably secure.
>>=20
>> This could use an additional warning that certificate archival should
>> not rely solely on signatures in archived certificates for ensuring =
the
>> validity and integrity of the archived certificates because the =
signature
>> algorithm(s) may transition to no longer being considered acceptably
>> secure at some point after the certificates are archived.
>>=20
>> Nits:
>>=20
>> idnits 2.12.15 said:
>>=20
>>  -- The document seems to lack a disclaimer for pre-RFC5378 work, but =
may
>>     have content which was first submitted before 10 November 2008.  =
If you
>>     have contacted all the original authors and they are all willing =
to grant
>>     the BCP78 rights to the IETF Trust, then this is fine, and you =
can ignore
>>     this comment.  If not, you may need to add the pre-RFC5378 =
disclaimer.
>>     (See the Legal Provisions document at
>>     http://trustee.ietf.org/license-info for more information.)
>>=20
>> This looks like it's ok because all the authors of RFC 2560 are also =
authors
>> of
>> this draft, but it should be double-checked.
>>=20
>> Thanks,
>> --David
>> ----------------------------------------------------
>> David L. Black, Distinguished Engineer
>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> david.black@emc.com        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Apr 10 04:34:07 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C468B21F8A40 for <gen-art@ietfa.amsl.com>; Wed, 10 Apr 2013 04:34:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.383
X-Spam-Level: 
X-Spam-Status: No, score=-102.383 tagged_above=-999 required=5 tests=[AWL=0.217, 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 jc5yNCo3IWUg for <gen-art@ietfa.amsl.com>; Wed, 10 Apr 2013 04:34:06 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 005FD21F9367 for <gen-art@ietf.org>; Wed, 10 Apr 2013 04:34:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 509E32CC5C; Wed, 10 Apr 2013 14:34:05 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zJ2cj61iy45p; Wed, 10 Apr 2013 14:34:03 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id DC7642CC4A; Wed, 10 Apr 2013 14:34:03 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <013301ce3162$2a95a7d0$7fc0f770$@gmail.com>
Date: Wed, 10 Apr 2013 14:34:03 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <46C684FE-7C7E-4E84-B8ED-E1735F5703A9@piuha.net>
References: <039401ce2952$8bbc17a0$a33446e0$@gmail.com> <515ADB89.7090801@secunet.com> <013301ce3162$2a95a7d0$7fc0f770$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: gen-art@ietf.org, 'Johannes Merkle' <johannes.merkle@secunet.com>, draft-merkle-ikev2-ke-brainpool.all@tools.ietf.org, 'Dan Harkins' <dharkins@arubanetworks.com>
Subject: Re: [Gen-art] GenART LC review of draft-merkle-ikev2-ke-brainpool-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2013 11:34:07 -0000

Roni,

Thanks for your review! It will help me post my vote (no-objection) on =
the document in the IESG call tomorrow.

Jari

On Apr 4, 2013, at 9:28 PM, Roni Even <ron.even.tlv@gmail.com> wrote:

> Hi Johannes,
> Thanks for your clarifications.
> I was not aware of the request to add a new column in
> draft-ietf-ipsecme-dh-checks and since I did not see the column yet I =
could
> not understand.
> So everything look OK for me now.
> Roni Even
>=20
>=20
> -----Original Message-----
> From: Johannes Merkle [mailto:johannes.merkle@secunet.com]=20
> Sent: 02 April, 2013 4:22 PM
> To: Roni Even
> Cc: draft-merkle-ikev2-ke-brainpool.all@tools.ietf.org; =
gen-art@ietf.org;
> Dan Harkins
> Subject: Re: GenART LC review of draft-merkle-ikev2-ke-brainpool-03
>=20
> Hi,
>=20
>> 1.       In table 1 the Transform ID are specified as TBD1 to TBD4. I
> noticed that IANA have already assigned values
>> 27-30. So they should be specified. If not it will be good to ask the =
RFC
> editor before publication to update the table.
>> I saw that you only asked IANA to allocate values.
>=20
> I'll do so in the next version if it is not done by the RFC editor.
>=20
>=20
>>=20
>> 2.       In the IANA section I did not understand to which table you =
are
> referring to "For the new entries in the table
>> of the Transform Type 4 repository, a reference to Section 2.3 of=20
>> [IKE_DH_Req] shall be included in the column named "Recipient Tests"
> indicating the required checks for the other peer's Diffie-Hellman =
public
> keys."
>>=20
> This refers to the Table Transform Type 4 - Diffie-Hellman Group =
Transform
> IDs, see
> =
http://www.iana.org/assignments/ikev2-parameters/ikev2-parameters.xml#ikev=
2-
> parameters-8
>=20
> [IKE_DH_Req] requests from IANA to add a new column (named "Recipient
> Tests") to that Table. We request IANA to add in that new column a a
> reference to Section 2.3 of [IKE_DH_Req].
>=20
> This request has been correctly understood by IANA, see email below.
>=20
> Best regards,
> Johannes
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Apr 10 04:44:01 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDD721F944C for <gen-art@ietfa.amsl.com>; Wed, 10 Apr 2013 04:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.200, 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 lXh8hHH2ucKd for <gen-art@ietfa.amsl.com>; Wed, 10 Apr 2013 04:44:00 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 2D05721F9423 for <gen-art@ietf.org>; Wed, 10 Apr 2013 04:44:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7D6742CC57; Wed, 10 Apr 2013 14:43:59 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MrPNnOanCvzY; Wed, 10 Apr 2013 14:43:59 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 0BD7A2CC4A; Wed, 10 Apr 2013 14:43:59 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EC1AE7905@PUEXCB1B.nanterre.francetelecom.fr>
Date: Wed, 10 Apr 2013 14:43:58 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B415AEC7-646F-4A90-A09E-259F7DC46CD2@piuha.net>
References: <030101ce3259$2b900520$82b00f60$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE7905@PUEXCB1B.nanterre.francetelecom.fr>
To: mohamed.boucadair@orange.com, Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1503)
Cc: "gen-art@ietf.org Team" <gen-art@ietf.org>, draft-ietf-intarea-nat-reveal-analysis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-intarea-nat-reveal-analysis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2013 11:44:01 -0000

Peter: Thank you very much for your review. It helps me form an opinion =
of the document in preparation for tomorrow's IESG telechat.

Jari


From peter@akayla.com  Wed Apr 10 09:46:54 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3F5021F88C6; Wed, 10 Apr 2013 09:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 Sk5C1wZBAbVm; Wed, 10 Apr 2013 09:46:54 -0700 (PDT)
Received: from p3plsmtpa08-06.prod.phx3.secureserver.net (p3plsmtpa08-06.prod.phx3.secureserver.net [173.201.193.107]) by ietfa.amsl.com (Postfix) with ESMTP id 21D2821F86CB; Wed, 10 Apr 2013 09:46:54 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa08-06.prod.phx3.secureserver.net with  id NGmr1l00P1huGat01GmrEq; Wed, 10 Apr 2013 09:46:53 -0700
From: "Peter Yee" <peter@akayla.com>
To: <mohamed.boucadair@orange.com>, <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
References: <054201ce34fa$0746ec80$15d4c580$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr> <059701ce3554$235aa0b0$6a0fe210$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE796C@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EC1AE796C@PUEXCB1B.nanterre.francetelecom.fr>
Date: Wed, 10 Apr 2013 09:46:55 -0700
Message-ID: <004c01ce360b$03fdade0$0bf909a0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGru2VgIxcOQENUYzhlyQVOZ0pm1wHHP5CkAxM512IB11gsjJjfEHeA
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2013 16:46:54 -0000

Med,

	That looks great.  Thanks for accommodating my concern.

			Kind regards,
			-Peter

-----Original Message-----
From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com] =

Sent: Wednesday, April 10, 2013 12:49 AM
To: Peter Yee; draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org
Cc: gen-art@ietf.org; ietf@ietf.org
Subject: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07

Dear Peter,

I changed the text as follows:

OLD:

   If the requested external port is not available, the PCP server will
   send a CANNOT_PROVIDE_EXTERNAL error response.  If a short lifetime
   error is returned, the IGD-PCP IWF MAY re-send the same request to
   the PCP Server after 30 seconds.  If a PCP error response is
   received, the IGD-PCP IWF relays a negative message to the UPnP
   Control Point with ConflictInMappingEntry as the error code.

NEW:

   If the requested external port is not available, the PCP server will
   send a CANNOT_PROVIDE_EXTERNAL error response:

   1.  If a short lifetime error is returned, the IGD-PCP IWF MAY resend
       the same request to the PCP Server after 30 seconds without
       relaying the error to the UPnP Control Point.  The IGD-PCP IWF
       MAY repeat this process until a positive answer is received or
       some maximum retry limit is reached.  When the maximum retry
       limit is reached, the IGD-PCP IWF relays a negative message to
       the UPnP Control Point with ConflictInMappingEntry as the error
       code.

   2.  If a long lifetime error is returned, the IGD-PCP IWF relays a
       negative message to the UPnP Control Point with
       ConflictInMappingEntry as the error code.

Better?

Cheers,
Med

>-----Message d'origine-----
>De=A0: Peter Yee [mailto:peter@akayla.com] Envoy=E9=A0: mardi 9 avril =
2013=20
>20:58 =C0=A0: BOUCADAIR Mohamed OLNC/OLN; draft-ietf-pcp-upnp-igd-=20
>interworking.all@tools.ietf.org Cc=A0: gen-art@ietf.org; ietf@ietf.org=20
>Objet=A0: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>
>Med,
>	Thanks for the swift response to my review.  See my one reply
inline.
>
>		Kind regards,
>		-Peter
>
>>>Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP =

>>>error other than a short-lifetime error, or in the case of a failed=20
>>>resend, any PCP error at all.  The wording makes it seem like the=20
>>>short-lifetime errors are somehow not PCP errors and is therefore=20
>>>confusing.  It also doesn't explicitly deal with how many repeats=20
>>>should
>be done on a resend.
>
>>[Med] The basic behavior is to relay the received error to the UPnP =
CP.
>For
>the short-lifetime errors, the IWF may decide to resend the request and =

>not relay those errors immediately to the UPnP CP. The number of=20
>repeats is not specified here as it can be implementation-specific.
>
>Your explanation is fine.  I just found the wording "If a PCP  error=20
>response is received" to sound ambiguously as if the short-lifetime=20
>errors were not a subset of PCP errors.
>



From mohamed.boucadair@orange.com  Wed Apr 10 22:43:58 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE9D21F8D8D; Wed, 10 Apr 2013 22:43:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[AWL=-0.342, BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799, UNPARSEABLE_RELAY=0.001]
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 YojbI92zc7zW; Wed, 10 Apr 2013 22:43:57 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE5621F8D79; Wed, 10 Apr 2013 22:43:57 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 3185A2DC72E; Thu, 11 Apr 2013 07:43:56 +0200 (CEST)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 11A2E4C070; Thu, 11 Apr 2013 07:43:56 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Thu, 11 Apr 2013 07:43:55 +0200
From: <mohamed.boucadair@orange.com>
To: Peter Yee <peter@akayla.com>, "draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org" <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
Date: Thu, 11 Apr 2013 07:43:53 +0200
Thread-Topic: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Thread-Index: AQGru2VgIxcOQENUYzhlyQVOZ0pm1wHHP5CkAxM512IB11gsjJjfEHeAgADYYbA=
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC1AE7D6E@PUEXCB1B.nanterre.francetelecom.fr>
References: <054201ce34fa$0746ec80$15d4c580$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr> <059701ce3554$235aa0b0$6a0fe210$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE796C@PUEXCB1B.nanterre.francetelecom.fr> <004c01ce360b$03fdade0$0bf909a0$@akayla.com>
In-Reply-To: <004c01ce360b$03fdade0$0bf909a0$@akayla.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.4.11.43316
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2013 05:43:58 -0000

Dear Peter,

The new version is now available online. A diff is available here: http://w=
ww.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-upnp-igd-interworking-08.

Thank you again for the review.

Cheers,
Med

>-----Message d'origine-----
>De=A0: Peter Yee [mailto:peter@akayla.com]
>Envoy=E9=A0: mercredi 10 avril 2013 18:47
>=C0=A0: BOUCADAIR Mohamed OLNC/OLN; draft-ietf-pcp-upnp-igd-
>interworking.all@tools.ietf.org
>Cc=A0: gen-art@ietf.org; ietf@ietf.org
>Objet=A0: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>
>Med,
>
>	That looks great.  Thanks for accommodating my concern.
>
>			Kind regards,
>			-Peter
>
>-----Original Message-----
>From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
>Sent: Wednesday, April 10, 2013 12:49 AM
>To: Peter Yee; draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org
>Cc: gen-art@ietf.org; ietf@ietf.org
>Subject: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>
>Dear Peter,
>
>I changed the text as follows:
>
>OLD:
>
>   If the requested external port is not available, the PCP server will
>   send a CANNOT_PROVIDE_EXTERNAL error response.  If a short lifetime
>   error is returned, the IGD-PCP IWF MAY re-send the same request to
>   the PCP Server after 30 seconds.  If a PCP error response is
>   received, the IGD-PCP IWF relays a negative message to the UPnP
>   Control Point with ConflictInMappingEntry as the error code.
>
>NEW:
>
>   If the requested external port is not available, the PCP server will
>   send a CANNOT_PROVIDE_EXTERNAL error response:
>
>   1.  If a short lifetime error is returned, the IGD-PCP IWF MAY resend
>       the same request to the PCP Server after 30 seconds without
>       relaying the error to the UPnP Control Point.  The IGD-PCP IWF
>       MAY repeat this process until a positive answer is received or
>       some maximum retry limit is reached.  When the maximum retry
>       limit is reached, the IGD-PCP IWF relays a negative message to
>       the UPnP Control Point with ConflictInMappingEntry as the error
>       code.
>
>   2.  If a long lifetime error is returned, the IGD-PCP IWF relays a
>       negative message to the UPnP Control Point with
>       ConflictInMappingEntry as the error code.
>
>Better?
>
>Cheers,
>Med
>
>>-----Message d'origine-----
>>De=A0: Peter Yee [mailto:peter@akayla.com] Envoy=E9=A0: mardi 9 avril 201=
3
>>20:58 =C0=A0: BOUCADAIR Mohamed OLNC/OLN; draft-ietf-pcp-upnp-igd-
>>interworking.all@tools.ietf.org Cc=A0: gen-art@ietf.org; ietf@ietf.org
>>Objet=A0: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>>
>>Med,
>>	Thanks for the swift response to my review.  See my one reply
>inline.
>>
>>		Kind regards,
>>		-Peter
>>
>>>>Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP
>>>>error other than a short-lifetime error, or in the case of a failed
>>>>resend, any PCP error at all.  The wording makes it seem like the
>>>>short-lifetime errors are somehow not PCP errors and is therefore
>>>>confusing.  It also doesn't explicitly deal with how many repeats
>>>>should
>>be done on a resend.
>>
>>>[Med] The basic behavior is to relay the received error to the UPnP CP.
>>For
>>the short-lifetime errors, the IWF may decide to resend the request and
>>not relay those errors immediately to the UPnP CP. The number of
>>repeats is not specified here as it can be implementation-specific.
>>
>>Your explanation is fine.  I just found the wording "If a PCP  error
>>response is received" to sound ambiguously as if the short-lifetime
>>errors were not a subset of PCP errors.
>>
>


From mahoney@nostrum.com  Fri Apr 12 07:57:40 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1385A21F855C for <gen-art@ietfa.amsl.com>; Fri, 12 Apr 2013 07:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
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 OKf+e-nhNX8e for <gen-art@ietfa.amsl.com>; Fri, 12 Apr 2013 07:57:39 -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 5E48021F8540 for <gen-art@ietf.org>; Fri, 12 Apr 2013 07:57:39 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.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 r3CEvbUO012789 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Fri, 12 Apr 2013 09:57:37 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <516820E1.6020209@nostrum.com>
Date: Fri, 12 Apr 2013 09:57:37 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: gen-art@ietf.org
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)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-04-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Apr 2013 14:57:40 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Alexey Melnikov   2013-04-23   draft-ietf-manet-olsrv2-mib-06
  
Wassim Haddad     2013-05-07   draft-sparks-genarea-imaparch-06



I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From bclaise@cisco.com  Mon Apr 15 02:36:29 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77B9F21F936D; Mon, 15 Apr 2013 02:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1-YI7+ehvAv; Mon, 15 Apr 2013 02:36:29 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id A6CA121F9361; Mon, 15 Apr 2013 02:36:28 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3F9aPdv015778; Mon, 15 Apr 2013 11:36:25 +0200 (CEST)
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3F9Zdhs010177; Mon, 15 Apr 2013 11:35:54 +0200 (CEST)
Message-ID: <516BC9EB.3000303@cisco.com>
Date: Mon, 15 Apr 2013 11:35:39 +0200
From: Benoit Claise <bclaise@cisco.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: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <4F6BB53A.3070609@nostrum.com> <514B808F.3050203@joelhalpern.com>
In-Reply-To: <514B808F.3050203@joelhalpern.com>
Content-Type: multipart/alternative; boundary="------------090206070705000507060502"
Cc: General Area Review Team <gen-art@ietf.org>, ipfix-chairs@tools.ietf.org, draft-ietf-ipfix-flow-selection-tech@tools.ietf.org, IETF discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Review: draft-ietf-ipfix-flow-selection-tech-14.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Apr 2013 09:36:29 -0000

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

Joel,

Thanks for your review.
>
> Minor issues:
>
>     If compliance is a big issue, then this document seems 
> under-specified. For example, it says in section 5.1 "In order to be 
> compliant with this document, at least the Property Match Filtering 
> MUST be implemented." However, Property Match Filtering as defined in 
> section 5.1.1 is a range of behaviors, so it is unclear which property 
> tests must be supported (any, all possible?) in order to be compliant.
>
I believe that this is fine.
The compliance statement is similar (i.e. generic) to the PSAMP RFC 5475.


        7 <http://tools.ietf.org/html/rfc5475#section-7>. Parameters for
        the Description of Selection Techniques

        This section gives an overview of different alternative selection
        schemes and their required parameters.  In order to be compliant with
        PSAMP, at least one of proposed schemes MUST be implemented.

Regards, Benoit.

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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Joel,<br>
      <br>
      Thanks for your review.<br>
    </div>
    <blockquote cite="mid:514B808F.3050203@joelhalpern.com" type="cite">
      <br>
      Minor issues:
      <br>
      <br>
      &nbsp;&nbsp;&nbsp;&nbsp;If compliance is a big issue, then this document seems
      under-specified. For example, it says in section 5.1 "In order to
      be compliant with this document, at least the Property Match
      Filtering MUST be implemented." However, Property Match Filtering
      as defined in section 5.1.1 is a range of behaviors, so it is
      unclear which property tests must be supported (any, all
      possible?) in order to be compliant.
      <br>
      <br>
    </blockquote>
    I believe that this is fine.<br>
    The compliance statement is similar (i.e. generic) to the PSAMP RFC
    5475.<br>
    <blockquote>
      <pre class="newpage"><span class="h2"><h2><a class="selflink" name="section-7" href="http://tools.ietf.org/html/rfc5475#section-7">7</a>.  Parameters for the Description of Selection Techniques</h2></span>   This section gives an overview of different alternative selection
   schemes and their required parameters.  In order to be compliant with
   PSAMP, at least one of proposed schemes MUST be implemented.

</pre>
    </blockquote>
    Regards, Benoit.<br>
  </body>
</html>

--------------090206070705000507060502--

From bclaise@cisco.com  Mon Apr 15 02:44:32 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18A8821F9393; Mon, 15 Apr 2013 02:44:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pAhkDykt+3bA; Mon, 15 Apr 2013 02:44:30 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 0A91921F938E; Mon, 15 Apr 2013 02:44:29 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3F9iA4R016779; Mon, 15 Apr 2013 11:44:10 +0200 (CEST)
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3F9glMg020166; Mon, 15 Apr 2013 11:43:07 +0200 (CEST)
Message-ID: <516BCB97.9040404@cisco.com>
Date: Mon, 15 Apr 2013 11:42:47 +0200
From: Benoit Claise <bclaise@cisco.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: "Salvatore D'Antonio" <salvatore.dantonio@uniparthenope.it>
References: <20130401072846.32360.9502.idtracker@ietfa.amsl.com> <5162C44B.5030904@cisco.com> <005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it>
In-Reply-To: <005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it>
Content-Type: multipart/alternative; boundary="------------040708030002030600080801"
Cc: rahulp@cisco.com, 'IETF discussion list' <ietf@ietf.org>, draft-ietf-ipfix-flow-selection-tech@tools.ietf.org, apps-discuss@ietf.org, 'General Area Review Team' <gen-art@ietf.org>, 'S Moonesamy' <sm+ietf@elandsys.com>, ipfix-chairs@tools.ietf.org, ipfix@ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] R: Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Apr 2013 09:44:32 -0000

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

Salvatore
>
> Dear all,
>
> A new version of the Internet Draft on Flow Selection Techniques has 
> been submitted. It contains the following changes:
>
> -A new section illustrating the difference between Intermediate Flow 
> Selection Process and Intermediate Selection Process has been added,
>
> -The sentence "In order to be compliant with this document, at least 
> the Property  Match Filtering MUST be implemented." has been removed 
> in Section 1,
>
> -â€śMUSTâ€ť has been replaced with â€śSHOULDâ€ť in Section 5.1,
>
Actually, the feedback was:

    In Section 1:

       "In order to be compliant with this document, at least the Property
        Match Filtering MUST be implemented."

    The above text is repeated in Section 5.1.  I suggest removing this
    sentence as it does not seem related to scope.

    My reading of the "MUST" is that it is being used for compliance
    instead of the reasons described in RFC 2119.  I suggest reviewing
    the usage of RFC 2119 key words in Section 5.1.

So the solution is not to change MUST to SHOULD.
The question is whether "MUST" versus "must" must be used.
I understand the concern. For compliance reason with the PSAMP RFC 5475 
(which is closely related) ...


        7 <http://tools.ietf.org/html/rfc5475#section-7>. Parameters for
        the Description of Selection Techniques

        This section gives an overview of different alternative selection
        schemes and their required parameters.  In order to be compliant with
        PSAMP, at least one of proposed schemes MUST be implemented.

... I would keep the initial "MUST" from the previous draft version.

> -â€śThe flowSelectorAlgorithm registry is maintained by IANA." has been 
> replaced with â€śIANA is requested to create the flowSelectorAlgorithm 
> registry.â€ť
>
> -The sentence "The registry can be updated when specifications of the 
> new  technique(s) and any new Information Elements are provided." has 
> been removed since it did not clarify how the registry will be managed.
>
> - Section 6.1.1 â€śProperty Match Filteringâ€ť has been changed by adding 
> some text on how Property Match Filtering can be  used by an 
> Intermediate Flow Selection Process in the Metering Process, in the 
>  Exporting Process and within an IPFIX Mediator.
>
When publishing a new version, please correct this editorial issue.

  " ... and Flow duration. in
    the An example is the selection of the largest ..."


> Best regards,
>
> Salvatore
>
> *Da:*Benoit Claise [mailto:bclaise@cisco.com]
> *Inviato:* lunedĂ¬ 8 aprile 2013 15:21
> *A:* draft-ietf-ipfix-flow-selection-tech@tools.ietf.org
> *Cc:* ipfix-chairs@tools.ietf.org
> *Oggetto:* Fwd: Last Call Expired: 
> <draft-ietf-ipfix-flow-selection-tech-14.txt>
>
> Dear authors,
>
> The IETF last call has finished.
> Can you please update your draft based on the feedback received.
> Then I will progress it.
>
> Regards, Benoit
>
>
>
> -------- Original Message --------
>
> *Subject: *
>
> 	
>
> Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>
>
> *Date: *
>
> 	
>
> Mon, 01 Apr 2013 00:28:46 -0700
>
> *From: *
>
> 	
>
> DraftTracker Mail System <iesg-secretary@ietf.org> 
> <mailto:iesg-secretary@ietf.org>
>
> *To: *
>
> 	
>
> iesg@ietf.org <mailto:iesg@ietf.org>, ipfix-chairs@tools.ietf.org 
> <mailto:ipfix-chairs@tools.ietf.org>, 
> draft-ietf-ipfix-flow-selection-tech@tools.ietf.org 
> <mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org>
>
> *CC: *
>
> 	
>
> iesg-secretary@ietf.org <mailto:iesg-secretary@ietf.org>
>
> Please DO NOT reply to this email.
>   
> I-D: <draft-ietf-ipfix-flow-selection-tech-14.txt>
> ID Tracker URL:http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tech/
>   
> IETF Last Call has ended, and the state has been changed to
> Waiting for AD Go-Ahead.
>   
>   
>   
>
> ------------------------------------------------------------------------
>
> Nessun virus nel messaggio.
> Controllato da AVG - www.avg.com <http://www.avg.com>
> Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data di 
> rilascio: 07/04/2013
>
>
> *******************************************************************************************************
>
> IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO
>
> Il 5 per mille all'UniversitĂ  degli Studi di Napoli 
> "Parthenope"incrementa le borse di studio agli studenti - codice 
> fiscale *80018240632*
>
> _http://www.uniparthenope.it/index.php/5xmille_
>
> _http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille_
>
>
> Questa informativa Ă¨ inserita in automatico dal sistema al fine 
> esclusivo della realizzazione dei fini istituzionali dell'ente.
>
>
>
>
> *******************************************************************************************************
>
> IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO
>
> Il 5 per mille all'UniversitĂ  degli Studi di Napoli 
> "Parthenope"incrementa le borse di studio agli studenti - codice 
> fiscale *80018240632*
>
> _http://www.uniparthenope.it/index.php/5xmille_
>
> _http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille_
>
>
> Questa informativa Ă¨ inserita in automatico dal sistema al fine 
> esclusivo della realizzazione dei fini istituzionali dell'ente.
>
>
>


--------------040708030002030600080801
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Salvatore<br>
    </div>
    <blockquote
      cite="mid:005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
      <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"Preformattato HTML Carattere";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.PreformattatoHTMLCarattere
	{mso-style-name:"Preformattato HTML Carattere";
	mso-style-priority:99;
	mso-style-link:"Preformattato HTML";
	font-family:Consolas;
	color:black;}
span.StileMessaggioDiPostaElettronica19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 2.0cm 2.0cm 2.0cm;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:217212090;
	mso-list-type:hybrid;
	mso-list-template-ids:308057158 -1513439274 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
      <div class="Section1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dear
            all,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>Â </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">A
            new version of the Internet Draft on Flow Selection
            Techniques
            has been submitted. It contains the following changes:<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">Â Â Â Â Â Â Â Â Â 
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">A
            new section illustrating the difference between Intermediate
            Flow Selection Process and Intermediate Selection Process
            has been added,<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">Â Â Â Â Â Â Â Â Â 
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The
            sentence "In order to be compliant with this document,
            at least the Property Â Match Filtering MUST be implemented."
            has been removed
            in Section 1,<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">Â Â Â Â Â Â Â Â Â 
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">â€śMUSTâ€ť
            has been replaced with â€śSHOULDâ€ť in Section 5.1,</span></p>
      </div>
    </blockquote>
    Actually, the feedback was:<br>
    <blockquote>In Section 1:
      <br>
      <br>
      Â  "In order to be compliant with this document, at least the
      Property
      <br>
      Â Â  Match Filtering MUST be implemented."
      <br>
      <br>
      The above text is repeated in Section 5.1.Â  I suggest removing
      this sentence as it does not seem related to scope.
      <br>
      <br>
      My reading of the "MUST" is that it is being used for compliance
      instead of the reasons described in RFC 2119.Â  I suggest reviewing
      the usage of RFC 2119 key words in Section 5.1.
      <br>
      <br>
    </blockquote>
    So the solution is not to change MUST to SHOULD.<br>
    The question is whether "MUST" versus "must" must be used.<br>
    I understand the concern. For compliance reason with the PSAMP RFC
    5475 (which is closely related) ...<br>
    <blockquote>
      <pre class="newpage"><span class="h2"><h2><a class="selflink" name="section-7" href="http://tools.ietf.org/html/rfc5475#section-7">7</a>.  Parameters for the Description of Selection Techniques</h2></span>   This section gives an overview of different alternative selection
   schemes and their required parameters.  In order to be compliant with
   PSAMP, at least one of proposed schemes MUST be implemented.

</pre>
    </blockquote>
    ... I would keep the initial "MUST" from the previous draft version.
    <blockquote> </blockquote>
    <blockquote
      cite="mid:005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it"
      type="cite">
      <div class="Section1">
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">Â Â Â Â Â Â Â Â Â 
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">â€śThe
            flowSelectorAlgorithm registry is maintained by IANA."
            has been replaced with â€śIANA is requested to create the
            flowSelectorAlgorithm
            registry.â€ť<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">Â Â Â Â Â Â Â Â Â 
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The
            sentence "The registry can be updated when
            specifications of the newÂ  technique(s) and any new
            Information Elements are
            provided." has been removed since it did not clarify how the
            registry will
            be managed.<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">Â Â Â Â Â Â Â Â Â 
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Â Section
            6.1.1 â€śProperty Match Filteringâ€ť has been changed by
            adding some text on how Property Match Filtering can be
            Â used by an
            Intermediate Flow Selection Process in the Metering Process,
            in the Â Exporting
            Process and within an IPFIX Mediator.</span></p>
      </div>
    </blockquote>
    When publishing a new version, please correct this editorial issue.<br>
    <br>
    <pre class="newpage"> " ... and Flow duration. in
   the An example is the selection of the largest ..."</pre>
    <br>
    <blockquote
      cite="mid:005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it"
      type="cite">
      <div class="Section1">
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>Â </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best
            regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>Â </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Salvatore<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>Â </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal"><b><span
                  style="font-size:10.0pt;font-family:&quot;Segoe
                  UI&quot;,&quot;sans-serif&quot;;
                  color:windowtext" lang="IT">Da:</span></b><span
                style="font-size:10.0pt;
                font-family:&quot;Segoe
                UI&quot;,&quot;sans-serif&quot;;color:windowtext"
                lang="IT"> Benoit Claise
                [<a class="moz-txt-link-freetext" href="mailto:bclaise@cisco.com">mailto:bclaise@cisco.com</a>] <br>
                <b>Inviato:</b> lunedĂ¬ 8 aprile 2013 15:21<br>
                <b>A:</b>
                <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org">draft-ietf-ipfix-flow-selection-tech@tools.ietf.org</a><br>
                <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:ipfix-chairs@tools.ietf.org">ipfix-chairs@tools.ietf.org</a><br>
                <b>Oggetto:</b> Fwd: Last Call Expired:
                &lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p>Â </o:p></p>
        <p class="MsoNormal">Dear authors,<br>
          <br>
          The IETF last call has finished.<br>
          Can you please update your draft based on the feedback
          received.<br>
          Then I will progress it.<br>
          <br>
          Regards, Benoit<o:p></o:p></p>
        <div>
          <p class="MsoNormal"><br>
            <br>
            -------- Original Message -------- <o:p></o:p></p>
          <table class="MsoNormalTable" border="0" cellpadding="0"
            cellspacing="0">
            <tbody>
              <tr>
                <td style="padding:0cm 0cm 0cm 0cm" nowrap="nowrap"
                  valign="top">
                  <p class="MsoNormal" style="text-align:right"
                    align="right"><b>Subject: <o:p></o:p></b></p>
                </td>
                <td style="padding:0cm 0cm 0cm 0cm">
                  <p class="MsoNormal">Last Call Expired:
                    &lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></p>
                </td>
              </tr>
              <tr>
                <td style="padding:0cm 0cm 0cm 0cm" nowrap="nowrap"
                  valign="top">
                  <p class="MsoNormal" style="text-align:right"
                    align="right"><b>Date: <o:p></o:p></b></p>
                </td>
                <td style="padding:0cm 0cm 0cm 0cm">
                  <p class="MsoNormal">Mon, 01 Apr 2013 00:28:46 -0700<o:p></o:p></p>
                </td>
              </tr>
              <tr>
                <td style="padding:0cm 0cm 0cm 0cm" nowrap="nowrap"
                  valign="top">
                  <p class="MsoNormal" style="text-align:right"
                    align="right"><b>From: <o:p></o:p></b></p>
                </td>
                <td style="padding:0cm 0cm 0cm 0cm">
                  <p class="MsoNormal">DraftTracker Mail System <a
                      moz-do-not-send="true"
                      href="mailto:iesg-secretary@ietf.org">&lt;iesg-secretary@ietf.org&gt;</a><o:p></o:p></p>
                </td>
              </tr>
              <tr>
                <td style="padding:0cm 0cm 0cm 0cm" nowrap="nowrap"
                  valign="top">
                  <p class="MsoNormal" style="text-align:right"
                    align="right"><b>To: <o:p></o:p></b></p>
                </td>
                <td style="padding:0cm 0cm 0cm 0cm">
                  <p class="MsoNormal"><a moz-do-not-send="true"
                      href="mailto:iesg@ietf.org">iesg@ietf.org</a>, <a
                      moz-do-not-send="true"
                      href="mailto:ipfix-chairs@tools.ietf.org">ipfix-chairs@tools.ietf.org</a>,
                    <a moz-do-not-send="true"
                      href="mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org">draft-ietf-ipfix-flow-selection-tech@tools.ietf.org</a><o:p></o:p></p>
                </td>
              </tr>
              <tr>
                <td style="padding:0cm 0cm 0cm 0cm" nowrap="nowrap"
                  valign="top">
                  <p class="MsoNormal" style="text-align:right"
                    align="right"><b>CC: <o:p></o:p></b></p>
                </td>
                <td style="padding:0cm 0cm 0cm 0cm">
                  <p class="MsoNormal"><a moz-do-not-send="true"
                      href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a><o:p></o:p></p>
                </td>
              </tr>
            </tbody>
          </table>
          <p class="MsoNormal" style="margin-bottom:12.0pt"><o:p>Â </o:p></p>
          <pre>Please DO NOT reply to this email.<o:p></o:p></pre>
          <pre><o:p>Â </o:p></pre>
          <pre>I-D: &lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></pre>
          <pre>ID Tracker URL: <a moz-do-not-send="true" href="http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tech/">http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tech/</a><o:p></o:p></pre>
          <pre><o:p>Â </o:p></pre>
          <pre>IETF Last Call has ended, and the state has been changed to<o:p></o:p></pre>
          <pre>Waiting for AD Go-Ahead.<o:p></o:p></pre>
          <pre><o:p>Â </o:p></pre>
          <pre><o:p>Â </o:p></pre>
          <pre><o:p>Â </o:p></pre>
          <p class="MsoNormal"><o:p>Â </o:p></p>
        </div>
        <p class="MsoNormal"><o:p>Â </o:p></p>
        <div class="MsoNormal" style="text-align:center" align="center">
          <hr style="color:#A0A0A0" noshade="noshade" size="1"
            width="100%" align="center">
        </div>
        <p class="MsoNormal"
          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Nessun
virus
          nel messaggio.<br>
          Controllato da AVG - <a moz-do-not-send="true"
            href="http://www.avg.com">www.avg.com</a><br>
          Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data
          di rilascio:
          07/04/2013<o:p></o:p></p>
      </div>
      <br>
      <style type="text/css">

	<!--

		@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }

		P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }

		P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }

		P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }

		P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }

		A:link { color: #0000ff }

	-->

	</style>
      <!--</HEAD></BODY>-->
      <p text="#000000" link="#0000ff" dir="LTR" lang="it-IT">
      </p>
      <p class="western" style="margin-bottom: 0cm"><font face="Arial,
          sans-serif">*******************************************************************************************************</font></p>
      <p class="western" style="margin-bottom: 0cm"><font face="Arial,
          sans-serif">IL
          MERITO DEGLI STUDENTIÂ VIENE RICONOSCIUTO</font></p>
      <p class="western" style="margin-bottom: 0cm">Â </p>
      <p class="western" style="margin-bottom: 0cm"><font
          color="#000000"><font face="Arial, sans-serif">Il
            5 per mille all'UniversitĂ  degli Studi di Napoli
            "Parthenope"incrementa le borse di studio agli studenti
            - codice fiscale </font></font><font color="#000000"><font
            face="Arial, sans-serif"><b>80018240632</b></font></font><font
          color="#000000"><font face="Arial, sans-serif">
          </font></font>
      </p>
      <p class="western" style="margin-bottom: 0cm"><a
          moz-do-not-send="true"
          href="http://www.uniparthenope.it/index.php/5xmille"><font
            color="#0000ff"><font face="Arial, sans-serif"><u>http://www.uniparthenope.it/index.php/5xmille</u></font></font></a><font
          color="#000000"><font face="Arial, sans-serif">Â </font></font></p>
      <p class="western" style="margin-bottom: 0cm">Â </p>
      <p class="western" style="margin-bottom: 0cm"><a
          moz-do-not-send="true"
href="http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><font
            color="#0000ff"><font face="Arial, sans-serif"><u>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</u></font></font></a></p>
      <p class="western" style="margin-bottom: 0cm">Â <font face="Arial,
          sans-serif"><br>
          Questa
          informativa Ă¨ inserita in automatico dal sistema al fine
          esclusivo
          della realizzazione dei fini istituzionali dell'ente.</font></p>
      <p class="western" style="margin-bottom: 0cm"><br>
      </p>
      <!--</BODY>-->
      <!--</HTML>-->
      <br>
      <br>
      <style type="text/css">

	<!--

		@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }

		P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }

		P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }

		P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }

		P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }

		A:link { color: #0000ff }

	-->

	</style>
      <!--</HEAD></BODY>-->
      <p text="#000000" link="#0000ff" dir="LTR" lang="it-IT">
      </p>
      <p class="western" style="margin-bottom: 0cm"><font face="Arial,
          sans-serif">*******************************************************************************************************</font></p>
      <p class="western" style="margin-bottom: 0cm"><font face="Arial,
          sans-serif">IL
          MERITO DEGLI STUDENTIÂ VIENE RICONOSCIUTO</font></p>
      <p class="western" style="margin-bottom: 0cm">Â </p>
      <p class="western" style="margin-bottom: 0cm"><font
          color="#000000"><font face="Arial, sans-serif">Il
            5 per mille all'UniversitĂ  degli Studi di Napoli
            "Parthenope"incrementa le borse di studio agli studenti
            - codice fiscale </font></font><font color="#000000"><font
            face="Arial, sans-serif"><b>80018240632</b></font></font><font
          color="#000000"><font face="Arial, sans-serif">
          </font></font>
      </p>
      <p class="western" style="margin-bottom: 0cm"><a
          moz-do-not-send="true"
          href="http://www.uniparthenope.it/index.php/5xmille"><font
            color="#0000ff"><font face="Arial, sans-serif"><u>http://www.uniparthenope.it/index.php/5xmille</u></font></font></a><font
          color="#000000"><font face="Arial, sans-serif">Â </font></font></p>
      <p class="western" style="margin-bottom: 0cm">Â </p>
      <p class="western" style="margin-bottom: 0cm"><a
          moz-do-not-send="true"
href="http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><font
            color="#0000ff"><font face="Arial, sans-serif"><u>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</u></font></font></a></p>
      <p class="western" style="margin-bottom: 0cm">Â <font face="Arial,
          sans-serif"><br>
          Questa
          informativa Ă¨ inserita in automatico dal sistema al fine
          esclusivo
          della realizzazione dei fini istituzionali dell'ente.</font></p>
      <p class="western" style="margin-bottom: 0cm"><br>
      </p>
      <!--</BODY>-->
      <!--</HTML>-->
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------040708030002030600080801--

From martin.thomson@gmail.com  Mon Apr 15 17:41:54 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACB3E21F93F8 for <gen-art@ietfa.amsl.com>; Mon, 15 Apr 2013 17:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
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 ZNQxsMVcxSTx for <gen-art@ietfa.amsl.com>; Mon, 15 Apr 2013 17:41:53 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 356D021F94A4 for <gen-art@ietf.org>; Mon, 15 Apr 2013 17:41:53 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id a12so1865226wgh.23 for <gen-art@ietf.org>; Mon, 15 Apr 2013 17:41:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=u6BDRCji8pEtzuL+W4RLqhRmhjnEhRNiQKcmL5mAKpE=; b=AR7NhTQrTA7EBaHjHwGzCjWhCBgXqV05UQ1CIdgCN76uJdlHevwZqpp3VGUWoEAhgR 4bSISEhcCdpimKubwAkrupT/BwusS0273kmQEBkEozv+iCl12pjC1694nY2qjIg4QD4K awvkc7yxiJ2wgm5gKemtb29blLShkh7xwc815HZFHTyDAStoRD5LyGmvNUj72ZObaGle 1F2bZ2YvB84A/wT/hrXSlziE6vO4bEIJbYSlaClNXH8bif/YJmd9Z7JUyolzS31/tUmZ daj4V8Bh4ccHrlHePUHGs4/1SNBJrJbmCuUteBdEskRCbvWR4Ze6YlC8PQ7v1aJT58UD pstQ==
MIME-Version: 1.0
X-Received: by 10.194.133.232 with SMTP id pf8mr84516wjb.31.1366072912324; Mon, 15 Apr 2013 17:41:52 -0700 (PDT)
Received: by 10.194.41.35 with HTTP; Mon, 15 Apr 2013 17:41:52 -0700 (PDT)
Date: Mon, 15 Apr 2013 17:41:52 -0700
Message-ID: <CABkgnnUaAu7iBsrUnkapebHEM2t5Snk0Kdoc=CF5joY6GTK7qA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: draft-ietf-nfsv4-rfc3530bis.all@tools.ietf.org,  "gen-art@ietf.org" <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Subject: [Gen-art] Partial Gen-ART review of draft-ietf-nfsv4-rfc3530bis-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2013 00:41:54 -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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-nfsv4-rfc3530bis-25
Reviewer: Martin Thomson
Review Date: 2013-04
IETF LC End Date: too soon
IESG Telechat date: ditto

Summary: I have some confidence that this document is ready for
publication.  What I have seen is sufficiently well specified that it
could be implemented, mostly.  There are large parts of this document
that I simply haven't read.  I can't justify spending more time.
(Sorry Jari, I tried.)

Reviewing this document is especially difficult because the it relies
heavily on context.  A lot of this context is only gained by reading on
and stumbling upon that context.  Much of this could be addressed
with appropriate forward references.

It's clear that Section 12 is largely new, or at least significantly
changed from RFC 3530.  Section 12 on its own would constitute a
larger than average RFC.

If accessibility is a goal, the document could have been split and it
probably should have been.  However, I suspect that accessibility
isn't that important to those working on this.

The document talks quite frequently about "before", with reference to
NFSv2 or NFSv3.  This is almost always useless to a reader without
context.  I don't expect you to do anything about this, but I'd
request that any future revision consider removing this.  For one, in
reviewing a -bis draft, I personally think of RFC3530 as the "before"
to which is refered.  On the whole, fewer history lessons and more
real context would have made this a lot easier to read.

General: The document uses lowercase "must" and "may" a lot.  It's not
clear whether these are intended to be interpreted as normative
statements or not.  To my eyes, most of these are.  On the other hand,
there are places where 2119 language is used to effectively specify
implementation details that aren't observable at a protocol level.
If the document weren't so large, I'd suggest that the editors go through
and make sure that every 2119 keyword is in uppercase and then to
check each and every instance.

Nits:

1.5.3 - I realize that it might be premature to explain details when the
draft hasn't yet described how to identify locations (that's a truly
unfortunate choice of word).  Maybe a short primer on that could be
included.  At this point, I'm relying on assumed knowledge about
filesystems to understand concepts like: hierarchical ACLs, pseudo
filesystems, attributes.

Even the fact that a filesystem is a tree with terminal nodes that
contain sequences of bytes.  Non-terminal nodes (directories) and
terminal nodes (files) are named (hence the UTF-8) and have
attributes.  Where it gets fuzzy is when it uses "path name".  Is
"path name" an abstraction that encapsulates "directory name" and
"file name"?  Is a "file name" the name of the node, or is it the
entire locator including the names of the directory above it (and some
unspecified separator)?

1.5.3.1
   [...]  The server provides multiple
   filesystems by gluing them together with pseudo filesystems.  These
   pseudo filesystems provide for potential gaps in the path names
   between real filesystems.

I don't know how to interpret this last statement.  I'm using a fair
bit of guesswork to infer how this works as it is, but that
understanding does not result in gaps, just pseudo filesystems (with
no actual files).


1.5.3.3 - The description of namespaces is singularly unhelpful in
conveying any information about the mechanism.  The benefits of this
snake oil are clearly splendrous.

s/alternate/alternative/ - I know that alternate is acceptable US
English, but alternate means something else to other English speakers.

1.5.5 - NLM could probably use a citation.

3.1 - "The registered port 2049 [RFC3232] for the NFS protocol SHOULD
be the default configuration."  This is an implementation requirement,
not a protocol one.

    - "this will allow NFS to transit firewalls" is only true if the
firewall is configured to recognize NTP using port numbers and allow
its passage.

    - "To date, all NFSv4 implementations are TCP based." Is this
really an appropriate statement for an RFC?

    - "UDP by itself is not sufficient as a transport for NFSv4,
neither is UDP in combination with some other mechanism (e.g., DCCP
[RFC4340], NORM [RFC5740])."  This statement is strange, given that
UDP is specifically prohibited.  I understand that something layered
on UDP (SCTP perhaps) might be able to meet the requirements, but this
statement implies that neither congestion control (DCCP), nor
reliability (NORM) is sufficient.  The draft should enumerate what
properties it expects to obtain from its transport before making such
statements. This section is really fuzzy on reliability expectations
(and 3.1.1 doesn't really help with that).

3.2 - "For NFSv4, the RPCSEC_GSS security flavor MUST be used to
enable the mandatory security mechanism."  Which aspect of security is
mandatory?  I find this confusing.  Earlier statements were pretty
clear: you must implement it, but you don't have to use it.

3.3 - s/may/can/

    - The SHOULD here (which is also a SHOULD in S17) could be
stronger.  I can understand why you need to allow for deployments that
don't use TLS (or equivalent integrity protection), but this

3.3.3 - "For Kerberos V5, the following form is RECOMMENDED:
nfs/hostname" - Q: how do you ensure interoperability if you don't
mandate a format?  Comment: This doesn't provide information on why an
implementation might choose a different form.

4.2 - The definitions of "persistent" and "volatile" are not known,
which makes this introduction to filehandle types hard to place in
context.  In many respects the discussion on the history of the
protocol is unnecessary at this point.  This would flow better if the
entire subsection was replaced with: "There are two[*] types of
filehandle: persistent and volatile.  Servers select the type that
they provide clients and signal the choice using the mandatory
"fh_expire_type" attribute (see Section 4.2.3)."  The rationale for
having both belongs in the respective sections (4.2.2 and 4.2.3).

    * There aren't two types of filehandle, there are six different
      persistence guarantees for filehandles.

4.2.1 - "Clients MUST use filehandle comparisons only to improve
performance, not for correct behavior.  All clients need to be
prepared for situations in which it cannot be determined whether two
filehandles denote the same object and in such cases, avoid making
invalid assumptions which might cause incorrect behavior."  This seems
a little confused.  The context establishes the fact that equal
filehandles always refer to the same file, and sometimes two different
filehandles can refer to the same file (though they SHOULDn't).  So,
what value does the 'MUST' provide here?  (I can't see how this would
be testable at the protocol level.)  Given that there is more
discussion in 10.3.4, I'd recommend dropping these two sentences.

5.1 - Use of lowercase "must" and "may" are confusing.  Consider using
alternatives.

5.2 - is that lowercase "must" in the third sentence really a MUST?

    - "A client MAY ask for the set of attributes the server supports
and SHOULD NOT request attributes the server does not support."  How
does the client ask for the supported set?

    - "A server should provide attributes whenever they don't have to
"tell lies" to the client."  This statement is odd.  Even with an
edit: "Rather than manufacturing fake attribute values, a server is
encouraged to avoid sending attributes that it can't support."  This
seems closer implementation magic than protocol specification.

12.1.2 - LATIN SMALL LETTER E is not U+0xxx

       - This section includes basically the same list twice.  The
first instance is on Page 179 (the first two-item list), the second on
the top of 180.

12.4.2 - What do you do with servers that are identified by server
names?  The last paragraph mentions that IP addresses are just ASCII.
Are server names are subject to the IDNA rules?  Do you want to
reference Section 12.6?

12.7.3 - none of the last four points uses normative 2119 language,
though "must" and "should" appear.  The text looks pretty normative to
me.

       - This looks less predictable than it could be.  Is it
reasonable to require that a server use the same normalization every
time it returns a name?  (That stability would only be required for a
given filehandle, of course.)

From suresh.krishnan@ericsson.com  Mon Apr 15 23:33:42 2013
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFAC21F95E3 for <gen-art@ietfa.amsl.com>; Mon, 15 Apr 2013 23:33:42 -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 n6xTp12ztcpr for <gen-art@ietfa.amsl.com>; Mon, 15 Apr 2013 23:33:41 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 9721921F9195 for <gen-art@ietf.org>; Mon, 15 Apr 2013 23:33:41 -0700 (PDT)
X-AuditID: c6180641-b7faf6d00000096b-ff-516cf0c483fb
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 98.11.02411.4C0FC615; Tue, 16 Apr 2013 08:33:41 +0200 (CEST)
Received: from eusaamw0712.eamcs.ericsson.se (147.117.20.181) by EUSAAHC002.ericsson.se (147.117.188.78) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 16 Apr 2013 02:33:40 -0400
Received: from [164.48.125.62] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 16 Apr 2013 02:33:39 -0400
Message-ID: <516CF028.2030406@ericsson.com>
Date: Tue, 16 Apr 2013 02:31:04 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, <draft-ietf-sipcore-sip-websocket.all@tools.ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNJMWRmVeSWpSXmKPExsUyuXSPn+7RDzmBBv/XcVvMuPef0eLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfGwu1nmQpOcVdsejuFrYHxB0cXIyeHhICJ xJeNh9kgbDGJC/fWA9lcHEICRxkllkzYzALh7GGU6Do1lxnC2coo8WLpfWaQFl4BbYl135+x gNgsAqoSK15fALPZgMZu2PmZCcQWFQiT2HthGhtEvaDEyZlPwGpEBDIkvl8/wAhiCwt4SPTN aGSBOENSYsuLdnYQm1lAT2LK1RZGCFteYvvbOWB7hQQ0Jbau+c46gVFgFpKxs5C0zELSsoCR eRUjR2lxalluupHhJkZgAB6TYHPcwbjgk+UhRmkOFiVx3lDXCwFCAumJJanZqakFqUXxRaU5 qcWHGJk4OKUaGE1uleiH7l0+x1Fwq/sRJ/7PdcZzps0Jaz69RF/u7HyBN2IqK4RLP7Y0zOLa +3RPSb3LqhAxN73Pt1kU/ycE8PLwpG0r+x5mnv7BSmjNjmPB3GZZ8dpfDwZ3Bxd0K3oc7vPi SDR0i9yVedJQbVncm6cNxy3Xe5S6/Ku8a/FwYZSmXnBXLZ+yEktxRqKhFnNRcSIANms2Sw4C AAA=
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-sipcore-sip-websocket-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2013 06:33:42 -0000

I am the assigned Gen-ART reviewer for
draft-ietf-sipcore-sip-websocket-08

For background on Gen-ART, please see the FAQ at
<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.

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

Summary: This draft is almost ready for publication as a Proposed
Standard, but has some minor issues that need to be fixed.

* Section 4.1

There is no error handling specified. i.e. What happens if the server
does not send a 101 reply with sip in the Sec-WebSocket-Protocol header?

* Section 5.2

The updated ABNF provided in section 5.2.1. is confusing. e.g. RFC4168
specifies the entire transport rule as follows

transport         =  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP"
                        / other-transport

while this document just uses an incremental alternative and calls it an
updated rule. I would have expected an *updated* rule to say

transport         =  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP" / "WS"
		        / "WSS" / other-transport

* Section 5.2.2

RFC4168 does not update transport-param. Is this a copy and paste error?

* Section 5.2.4

Maybe it is just me, but the way I read it, this section leaves the
client without any mandatory to implement transport protocol for SIP
since it relaxes the need to implement UDP and TCP, as well as allowing
the implementation of the websocket transport using a MAY.

Thanks
Suresh



From ibc@aliax.net  Tue Apr 16 01:40:59 2013
Return-Path: <ibc@aliax.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53A2221F9686 for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 01:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level: 
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
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 oQanapdeGHeD for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 01:40:58 -0700 (PDT)
Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id B706421F9685 for <gen-art@ietf.org>; Tue, 16 Apr 2013 01:40:58 -0700 (PDT)
Received: by mail-qc0-f180.google.com with SMTP id b40so106474qcq.11 for <gen-art@ietf.org>; Tue, 16 Apr 2013 01:40:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=Yc7gXsWLsZM1GoMxByJmbJns/OIUzgcEJarnEgtFgIU=; b=IwqA5/V+6QGfCPHps1Z6u3zc98RMDdsSlwF3gUydMJHZgtmEsx/r3C0kVCDn4ZfyDV 2v/CnHUXk3q0aEGSjYiVeKMRmvq9+Exe08PHIWmprNiTeOME8jkJNebzfTvy+JZAooUV HfGYhj/fxdf2AQ7R6ePFIX/yqgeAaaDYBj6k/blhbB9Tp7bTNBRECZtkFxsCaF7gaW42 LzDQpYF82r6MDvlsuyf5iv6w3tYDKyFreJV5S0lTHSRyAwMmv9GapQyBsg14XMrKpL9L YcFrXRw+JcZ8eLUFE/HrNT016oNqN7dPlpVj0EUDPs+EBrdrCa03Z0x5QNbIfSOGCV0r m/+A==
X-Received: by 10.49.104.196 with SMTP id gg4mr1358128qeb.53.1366101657740; Tue, 16 Apr 2013 01:40:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.81.175 with HTTP; Tue, 16 Apr 2013 01:40:36 -0700 (PDT)
In-Reply-To: <516CF028.2030406@ericsson.com>
References: <516CF028.2030406@ericsson.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Tue, 16 Apr 2013 10:40:36 +0200
Message-ID: <CALiegfkpY1Dwx3eBvuHf=XcBFNrKq4nhUV-XQzFtBpo7BAegow@mail.gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkCwBqnWKdqilXU8iIgnwm9AsZj0M5HLn88Ad4uuX4BSgLkuuUwS4ACAegjs6k0I9Sv8KPW
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-sipcore-sip-websocket.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-sipcore-sip-websocket-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2013 08:40:59 -0000

Thanks a lot for your review Suresh. Please read replies inline:


2013/4/16 Suresh Krishnan <suresh.krishnan@ericsson.com>:
> Summary: This draft is almost ready for publication as a Proposed
> Standard, but has some minor issues that need to be fixed.
>
> * Section 4.1
>
> There is no error handling specified. i.e. What happens if the server
> does not send a 101 reply with sip in the Sec-WebSocket-Protocol header?

It should be considered a SIP transport error, so a 503 SIP response
should be locally generated. This will be added to that section.



> * Section 5.2
>
> The updated ABNF provided in section 5.2.1. is confusing. e.g. RFC4168
> specifies the entire transport rule as follows
>
> transport         =3D  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP"
>                         / other-transport
>
> while this document just uses an incremental alternative and calls it an
> updated rule. I would have expected an *updated* rule to say
>
> transport         =3D  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP" / "WS"
>                         / "WSS" / other-transport

There was a long discussion in SIPCORE WG about this subject and
finally it was chosen to use the incremental alternative (so the
updated ABNF would be also longer in the future when new SIP
transports are defined).

Do you consider anyhow that using the fully updated rule is required?



> * Section 5.2.2
>
> RFC4168 does not update transport-param. Is this a copy and paste error?

Yes, will be fixed.



> * Section 5.2.4
>
> Maybe it is just me, but the way I read it, this section leaves the
> client without any mandatory to implement transport protocol for SIP
> since it relaxes the need to implement UDP and TCP, as well as allowing
> the implementation of the websocket transport using a MAY.

Yes, such a MAY sounds a look confusing. What the text wants to say is
that a SIP WebSocket Client (which obviously implements the SIP
WebSocket transport) is not mandated to implement UDP and TCP
transports. I wil improve the text by removing the last words and
leave it as follows:

----------------
   The specification of this transport enables SIP to be used as a
   session establishment protocol in scenarios where none of other
   transport protocols defined for SIP can be used.  Since some
   environments do not enable SIP elements to use UDP and TCP as SIP
   transport protocols, a SIP element acting as a SIP WebSocket Client
   is not mandated to implement support of UDP and TCP.
----------------



Thanks a lot.


--
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From rjsparks@nostrum.com  Tue Apr 16 07:40:39 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6314D21F9713 for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 07:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 zWXYi5VBTbbn for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 07:40:39 -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 7C13A21F9702 for <gen-art@ietf.org>; Tue, 16 Apr 2013 07:40:36 -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 r3GEeGVl046836 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Tue, 16 Apr 2013 09:40:17 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <516D62D3.4090402@nostrum.com>
Date: Tue, 16 Apr 2013 09:40:19 -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: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
References: <516CF028.2030406@ericsson.com> <CALiegfkpY1Dwx3eBvuHf=XcBFNrKq4nhUV-XQzFtBpo7BAegow@mail.gmail.com>
In-Reply-To: <CALiegfkpY1Dwx3eBvuHf=XcBFNrKq4nhUV-XQzFtBpo7BAegow@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-sipcore-sip-websocket.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-sipcore-sip-websocket-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2013 14:40:39 -0000

Suresh -

One more comment (trimming heavily)

On 4/16/13 3:40 AM, IĂ±aki Baz Castillo wrote:
>
>> * Section 5.2
>>
>> The updated ABNF provided in section 5.2.1. is confusing. e.g. RFC4168
>> specifies the entire transport rule as follows
>>
>> transport         =  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP"
>>                          / other-transport
>>
>> while this document just uses an incremental alternative and calls it an
>> updated rule. I would have expected an *updated* rule to say
>>
>> transport         =  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP" / "WS"
>>                          / "WSS" / other-transport
> There was a long discussion in SIPCORE WG about this subject and
> finally it was chosen to use the incremental alternative (so the
> updated ABNF would be also longer in the future when new SIP
> transports are defined).
>
> Do you consider anyhow that using the fully updated rule is required?
>
>
Suresh -

The issue is that we have many header fields where more than one 
document may
add a token. Restating the full production each time has proven problematic,
particularly when more than one draft that proposes adding a token is in 
flight at the
same time. Instead, we're adopting a consistent approach of using the 
the incremental
alternative rule to add tokens and IANA registries to make it easy to 
find the
tokens that have been documented to date.

RjS

From aretana@cisco.com  Tue Apr 16 14:06:37 2013
Return-Path: <aretana@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D429321F977D for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 14:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9zI4l0OFJ7Rr for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 14:06:32 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id A92AB21F9404 for <gen-art@ietf.org>; Tue, 16 Apr 2013 14:06:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=851; q=dns/txt; s=iport; t=1366146392; x=1367355992; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=2d1ugwSxf/VutVQYNMoJn9jZKam/+SQtgeWPQllhsCc=; b=Po/oomeCMvbnzXsurzxE2qApiJOPG01/M739Cx/7fJKIBUgNB8CR1dRC M4vDtUVN+SkUnfaCIShdyewZHoHAdVpK6Q5b4BvPhGR4E91CXVNhPwLk8 k/l2dnVYD/9Mv1/U+i9M9BNggsMrcK5Jl973MBOeCiAYI7jD0gl1vYpoh c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAEW8bVGtJXHB/2dsb2JhbABGCoMGgyC+FIELFnSCIQEEOj8SAQgiFEIlAgQBDQUIiAysVJA2jV+BCzEHgmRhA6gagwuCKA
X-IronPort-AV: E=Sophos;i="4.87,487,1363132800"; d="scan'208";a="199502499"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-7.cisco.com with ESMTP; 16 Apr 2013 21:06:32 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r3GL6W6T023339 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 16 Apr 2013 21:06:32 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.219]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Tue, 16 Apr 2013 16:06:31 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "stewart@g3ysx.org.uk" <stewart@g3ysx.org.uk>, "Stewart Bryant (stbryant)" <stbryant@cisco.com>
Thread-Topic: Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
Thread-Index: AQHN9DdZ9OjrkRsEWE2bqOnRv2sH7Zh1YiiAgCQQ4gCAAAFTAIAzrwSAgAx9DQCAAFRvAA==
Date: Tue, 16 Apr 2013 21:06:31 +0000
Message-ID: <BBD66FD99311804F80324E8139B3C94E11D6C7ED@xmb-aln-x15.cisco.com>
In-Reply-To: <516D3E42.9010503@g3ysx.org.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.15.7]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <694D05BD7611D446873438F6391A9361@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ospf-chairs@tools.ietf.org" <ospf-chairs@tools.ietf.org>, Acee Lindem <acee.lindem@ericsson.com>, "draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org" <draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "Abhay Roy \(akr\)" <akr@cisco.com>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2013 21:06:37 -0000

On 4/16/13 8:04 AM, "Stewart Bryant" <stewart@g3ysx.org.uk> wrote:

>We are still short of this text.
>
>I can add it as an editors note. Just give me a few lines
>and I will put it on the telechat.

Stewart:

Here's the text to add to the last paragraph in section 1:

For example, [I-D.ietf-ospf-ipv4-embedded-ipv6-routing] describes an
application in which IPv4-embedded IPv6 addresses are used to transport
IPv4 packets over an IPv6 network.  While the IPv4-embedded IPv6 addresses
do in fact represent IPv6 destinations, it would be operationally
beneficial to be able to easily identify the specific application by
having a separate space to do so.



Besides the text, we need to add the informational reference, and include
Ben in the acks.  Let me know if you rather I publish an update (tonight).

Thanks!

Alvaro.


From suresh.krishnan@ericsson.com  Tue Apr 16 16:05:39 2013
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53F2E21F97B9 for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 16:05:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 A1o-ynWfP7Zo for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 16:05:38 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB7E21F97BC for <gen-art@ietf.org>; Tue, 16 Apr 2013 16:05:37 -0700 (PDT)
X-AuditID: c618062d-b7f0d6d00000097e-78-516dd9388df2
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id CD.5B.02430.839DD615; Wed, 17 Apr 2013 01:05:29 +0200 (CEST)
Received: from eusaamw0711.eamcs.ericsson.se (147.117.20.178) by EUSAAHC008.ericsson.se (147.117.188.96) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 16 Apr 2013 19:05:28 -0400
Received: from [142.133.112.81] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 16 Apr 2013 19:05:27 -0400
Message-ID: <516DD8A1.1050606@ericsson.com>
Date: Tue, 16 Apr 2013 19:02:57 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
References: <516CF028.2030406@ericsson.com> <CALiegfkpY1Dwx3eBvuHf=XcBFNrKq4nhUV-XQzFtBpo7BAegow@mail.gmail.com>
In-Reply-To: <CALiegfkpY1Dwx3eBvuHf=XcBFNrKq4nhUV-XQzFtBpo7BAegow@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGLMWRmVeSWpSXmKPExsUyuXRPgq7lzdxAgxVaFjPu/We0uPrqM4vF 9H02Dswe5xres3ssWfKTyePL5c9sAcxRXDYpqTmZZalF+nYJXBkPLl5mKWiVqOhad4uxgXGR UBcjJ4eEgInE5YffmSBsMYkL99azdTFycQgJHGWUuLF9HyuEs4dR4v7kwywQzjZGiQcP2thB WngFtCUONsxjBbFZBFQlHuxYzQhiswGN3bDzM9hYUYEwiVXrlzFD1AtKnJz5hAXEFhGwkbgx cQJYDbNAhsSlkzfA5ggL+Eh8u7McyOYAWlYgsXZVBUiYUyBQYuflbhaISyUltrxoZ4do1ZRo 3f4bypaXaN46G2yVEFB865rvrBMYhWch2TwLScssJC0LGJlXMXKUFqeW5aYbGWxiBIb1MQk2 3R2Me15aHmKU5mBREucNcr0QICSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoGROWXJ1XdSDJvv Bq53EHC6GHjy+NPqhRO7620k/h64dPC5mPvUjkLVVQeDX++a5uh2iPOeSP7030bm7szuvtMP Jh1RSmf7E/ha3vv43rptPe0y3T9cTy1Sbpu4/RnbU5Np8n84c44KJmTmdLAfctbPfir2WcKu 3lXtjlz56baeJ42/TxXJCH9SYinOSDTUYi4qTgQAEUBHejkCAAA=
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-sipcore-sip-websocket.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-sipcore-sip-websocket-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2013 23:05:39 -0000

Hi IĂ±aki,
  Thanks for the quick reply. Please find responses inline.

On 04/16/2013 04:40 AM, IĂ±aki Baz Castillo wrote:
> Thanks a lot for your review Suresh. Please read replies inline:
> 
> 
> 2013/4/16 Suresh Krishnan <suresh.krishnan@ericsson.com>:
>> Summary: This draft is almost ready for publication as a Proposed
>> Standard, but has some minor issues that need to be fixed.
>>
>> * Section 4.1
>>
>> There is no error handling specified. i.e. What happens if the server
>> does not send a 101 reply with sip in the Sec-WebSocket-Protocol header?
> 
> It should be considered a SIP transport error, so a 503 SIP response
> should be locally generated. This will be added to that section.

Great.

> 
> 
> 
>> * Section 5.2
>>
>> The updated ABNF provided in section 5.2.1. is confusing. e.g. RFC4168
>> specifies the entire transport rule as follows
>>
>> transport         =  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP"
>>                         / other-transport
>>
>> while this document just uses an incremental alternative and calls it an
>> updated rule. I would have expected an *updated* rule to say
>>
>> transport         =  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP" / "WS"
>>                         / "WSS" / other-transport
> 
> There was a long discussion in SIPCORE WG about this subject and
> finally it was chosen to use the incremental alternative (so the
> updated ABNF would be also longer in the future when new SIP
> transports are defined).
> 
> Do you consider anyhow that using the fully updated rule is required?

I saw Robert's response on the same topic and I will reply to that. If
the WG's consensus is to go incremental, please stick with that. I just
want to ensure that there is no ambiguity as to the final result.

> 
> 
> 
>> * Section 5.2.2
>>
>> RFC4168 does not update transport-param. Is this a copy and paste error?
> 
> Yes, will be fixed.

OK.

> 
> 
> 
>> * Section 5.2.4
>>
>> Maybe it is just me, but the way I read it, this section leaves the
>> client without any mandatory to implement transport protocol for SIP
>> since it relaxes the need to implement UDP and TCP, as well as allowing
>> the implementation of the websocket transport using a MAY.
> 
> Yes, such a MAY sounds a look confusing. What the text wants to say is
> that a SIP WebSocket Client (which obviously implements the SIP
> WebSocket transport) is not mandated to implement UDP and TCP
> transports. I wil improve the text by removing the last words and
> leave it as follows:
> 
> ----------------
>    The specification of this transport enables SIP to be used as a
>    session establishment protocol in scenarios where none of other
>    transport protocols defined for SIP can be used.  Since some
>    environments do not enable SIP elements to use UDP and TCP as SIP
>    transport protocols, a SIP element acting as a SIP WebSocket Client
>    is not mandated to implement support of UDP and TCP.
> ----------------

Looks good.

Thanks
Suresh


From suresh.krishnan@ericsson.com  Tue Apr 16 16:05:56 2013
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 125A121F97BB for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 16:05:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 m3TJJxRV8vJB for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 16:05:54 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id BE76321F97B9 for <gen-art@ietf.org>; Tue, 16 Apr 2013 16:05:54 -0700 (PDT)
X-AuditID: c6180641-b7faf6d00000096b-4c-516dd9525d0e
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 91.6D.02411.259DD615; Wed, 17 Apr 2013 01:05:54 +0200 (CEST)
Received: from eusaamw0711.eamcs.ericsson.se (147.117.20.178) by EUSAAHC005.ericsson.se (147.117.188.87) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 16 Apr 2013 19:05:53 -0400
Received: from [142.133.112.81] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 16 Apr 2013 19:05:52 -0400
Message-ID: <516DD8BB.5040307@ericsson.com>
Date: Tue, 16 Apr 2013 19:03:23 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
References: <516CF028.2030406@ericsson.com> <CALiegfkpY1Dwx3eBvuHf=XcBFNrKq4nhUV-XQzFtBpo7BAegow@mail.gmail.com> <516D62D3.4090402@nostrum.com>
In-Reply-To: <516D62D3.4090402@nostrum.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrELMWRmVeSWpSXmKPExsUyuXRPuG7QzdxAgynPZS1m3PvPaHH11WcW i+n7bCyuzWlkc2DxONfwnt1jyZKfTB6zdj5h8fhy+TNbAEsUl01Kak5mWWqRvl0CV8b8Mx/Z Ck7wV1w4PIm5gfENdxcjJ4eEgInE9X9/mSFsMYkL99azdTFycQgJHGWU+HFiMyuEs4dR4uX0 M4wQzjZGiY/7T7GDtPAKaEtMPHmHFcRmEVCVuPj4JguIzQY0dsPOz0wgtqhAmMSq9cuYIeoF JU7OfAJWIyKgIXFtyRKwOcwCyxgldn1LBrGFgeobZ0CcJCTQzyhx7rk7iM0JtOvQgYOsEKdK Smx50Q7VqynRuv03lC0v0bx1NlSvpsTWNd9ZJzAKz0KyehaSlllIWhYwMq9i5CgtTi3LTTcy 3MQIDPdjEmyOOxgXfLI8xCjNwaIkzhvqeiFASCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dUA6Pc ulvFJU23276KLLS8vl1nN/uvuCyn5qSQRWVqLaU/t8g7c3daxTz7oJCaFHB12nL/BPaK156f PuhINDvPEtMKKNq40cHEQ4zlyYE7drM9T03gmLRC3PjlvODflvU2Pff2C5k+v/b+4qRZp7dy 1F18Vvb+nUi38luhYIaT9jOj0plzjs9cUKfEUpyRaKjFXFScCAAEyjFsRQIAAA==
Cc: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>, General Area Review Team <gen-art@ietf.org>, draft-ietf-sipcore-sip-websocket.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-sipcore-sip-websocket-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2013 23:05:56 -0000

Hi Robert,

On 04/16/2013 10:40 AM, Robert Sparks wrote:
> Suresh -
> 
> One more comment (trimming heavily)
> 
> On 4/16/13 3:40 AM, IĂ±aki Baz Castillo wrote:
>>
>>> * Section 5.2
>>>
>>> The updated ABNF provided in section 5.2.1. is confusing. e.g. RFC4168
>>> specifies the entire transport rule as follows
>>>
>>> transport         =  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP"
>>>                          / other-transport
>>>
>>> while this document just uses an incremental alternative and calls it an
>>> updated rule. I would have expected an *updated* rule to say
>>>
>>> transport         =  "UDP" / "TCP" / "TLS" / "SCTP" / "TLS-SCTP" / "WS"
>>>                          / "WSS" / other-transport
>> There was a long discussion in SIPCORE WG about this subject and
>> finally it was chosen to use the incremental alternative (so the
>> updated ABNF would be also longer in the future when new SIP
>> transports are defined).
>>
>> Do you consider anyhow that using the fully updated rule is required?
>>
>>
> Suresh -
> 
> The issue is that we have many header fields where more than one
> document may
> add a token. Restating the full production each time has proven
> problematic,
> particularly when more than one draft that proposes adding a token is in
> flight at the
> same time. Instead, we're adopting a consistent approach of using the
> the incremental
> alternative rule to add tokens and IANA registries to make it easy to
> find the
> tokens that have been documented to date.

That sounds like a good plan. I was more concerned with the wording that
calls this an "updated rule" and the fact that the title of Section 5.2
"Updates to RFC3261" that implies the incremental rule could be
interpreted to add to the rule specified in RFC3261 and lose other
additions since (in this case losing TLS-SCTP). If you have a plan in
place with IANA to take care of this I am fine with this approach.

Thanks
Suresh


From stbryant@cisco.com  Tue Apr 16 16:27:23 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 651C021F9794 for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 16:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 VgFSvnjAkuy4 for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 16:27:22 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id AB85921F9793 for <gen-art@ietf.org>; Tue, 16 Apr 2013 16:27:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1093; q=dns/txt; s=iport; t=1366154842; x=1367364442; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=iXKO4u20xBROWHhrcQ88NiutsjaxqhwAT3tTvYfNW0U=; b=XDQPRn2+AUw+Hkv961yhmp1j5kqeU0i0GyQhq+9rIf/azMvopOX8ZI/t oq10fnBMdY7vZWpWvuLGPd3IOJuuuwMSZ2j7UjW4JcqkbhomLmKF1Uw2w 5fL3wyhzL2miaO5TFqL0l4uA3HsRoCURDPqWy6sn6qsRl3EtrN8RAMDB0 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAPfcbVGtJV2Y/2dsb2JhbABGCoMGwT+BCxZ0gh8BAQEDATo/BQsCAQgYHhAyJQIEDgWIDgasU5AwjV+BCTMHgmRhA5cGkRSDCw
X-IronPort-AV: E=Sophos;i="4.87,488,1363132800"; d="scan'208";a="196575831"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-9.cisco.com with ESMTP; 16 Apr 2013 23:27:22 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3GNRL3a014568 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 16 Apr 2013 23:27:22 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.31]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Tue, 16 Apr 2013 18:27:21 -0500
From: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Thread-Topic: Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
Thread-Index: AQHN9DdZ9OjrkRsEWE2bqOnRv2sH7Zh1YiiAgCQQ4gCAAAFTAIAzrwSAgAx9DQCAAFRvAIAAFpb/
Date: Tue, 16 Apr 2013 23:27:21 +0000
Message-ID: <E20820B4-A689-4090-8621-66AFB14153E7@cisco.com>
References: <516D3E42.9010503@g3ysx.org.uk>, <BBD66FD99311804F80324E8139B3C94E11D6C7ED@xmb-aln-x15.cisco.com>
In-Reply-To: <BBD66FD99311804F80324E8139B3C94E11D6C7ED@xmb-aln-x15.cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Acee Lindem <acee.lindem@ericsson.com>, "draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org" <draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org>, "stewart@g3ysx.org.uk" <stewart@g3ysx.org.uk>, "ospf-chairs@tools.ietf.org" <ospf-chairs@tools.ietf.org>, "Abhay Roy \(akr\)" <akr@cisco.com>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Apr 2013 23:27:23 -0000

If you can respin that would be cool.

Stewart

Sent from my iPad

On 16 Apr 2013, at 14:06, "Alvaro Retana (aretana)" <aretana@cisco.com> wro=
te:

> On 4/16/13 8:04 AM, "Stewart Bryant" <stewart@g3ysx.org.uk> wrote:
>=20
>> We are still short of this text.
>>=20
>> I can add it as an editors note. Just give me a few lines
>> and I will put it on the telechat.
>=20
> Stewart:
>=20
> Here's the text to add to the last paragraph in section 1:
>=20
> For example, [I-D.ietf-ospf-ipv4-embedded-ipv6-routing] describes an
> application in which IPv4-embedded IPv6 addresses are used to transport
> IPv4 packets over an IPv6 network.  While the IPv4-embedded IPv6 addresse=
s
> do in fact represent IPv6 destinations, it would be operationally
> beneficial to be able to easily identify the specific application by
> having a separate space to do so.
>=20
>=20
>=20
> Besides the text, we need to add the informational reference, and include
> Ben in the acks.  Let me know if you rather I publish an update (tonight)=
.
>=20
> Thanks!
>=20
> Alvaro.
>=20

From aretana@cisco.com  Tue Apr 16 18:39:13 2013
Return-Path: <aretana@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06D1521F964A for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 18:39:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nd4DKan4u9mG for <gen-art@ietfa.amsl.com>; Tue, 16 Apr 2013 18:39:12 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id E3E8E21F95F1 for <gen-art@ietf.org>; Tue, 16 Apr 2013 18:39:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=152; q=dns/txt; s=iport; t=1366162752; x=1367372352; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=2eGYNUKcY2oBFNkv9UkCArLnHx+6xdJia6E8ik2xOes=; b=dUgEmSxKjvg2FZ6Q3GzsvpxZ+Qx+uCp8UAibgKdJbS4ZC0BTI0DJQjqk da+Zxa+uPYTKSqkWSXKgMucGcP4rDRJXZRdYb88rHK+bBS1pxsc4j2unX wlQv5f547LDtSa0z9l0B8lfdg0Qv3LlsMqVq2VdMqJ/Mj+jBqib0Xz+J4 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAIn8bVGtJXG+/2dsb2JhbABQgwaDIL4igQ4WdIIhAQQ6PxIBCCIUQiUCBA4FCIgMrxGODo5qMQeCZGEDqBqCfg2CKA
X-IronPort-AV: E=Sophos;i="4.87,488,1363132800"; d="scan'208";a="199582414"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-6.cisco.com with ESMTP; 17 Apr 2013 01:39:11 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r3H1dAHK028479 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 17 Apr 2013 01:39:11 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.219]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Tue, 16 Apr 2013 20:39:02 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
Thread-Topic: Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
Thread-Index: AQHN9DdZ9OjrkRsEWE2bqOnRv2sH7Zh1YiiAgCQQ4gCAAAFTAIAzrwSAgAx9DQCAAFRvAIAAFpb/gAA1jAA=
Date: Wed, 17 Apr 2013 01:39:01 +0000
Message-ID: <BBD66FD99311804F80324E8139B3C94E11D6D3C0@xmb-aln-x15.cisco.com>
In-Reply-To: <E20820B4-A689-4090-8621-66AFB14153E7@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.15.7]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8DE224B2BF87574BAE15706F07DC3440@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Acee Lindem <acee.lindem@ericsson.com>, "draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org" <draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org>, "stewart@g3ysx.org.uk" <stewart@g3ysx.org.uk>, "ospf-chairs@tools.ietf.org" <ospf-chairs@tools.ietf.org>, "Abhay Roy \(akr\)" <akr@cisco.com>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Apr 2013 01:39:13 -0000

Just uploaded -03.

Alvaro.

On 4/16/13 7:27 PM, "Stewart Bryant (stbryant)" <stbryant@cisco.com> wrote:

>If you can respin that would be cool.


From ibc@aliax.net  Wed Apr 17 01:45:44 2013
Return-Path: <ibc@aliax.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 592DD21F8B04 for <gen-art@ietfa.amsl.com>; Wed, 17 Apr 2013 01:45:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.305
X-Spam-Level: 
X-Spam-Status: No, score=-2.305 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 EXSbo6KVVX2b for <gen-art@ietfa.amsl.com>; Wed, 17 Apr 2013 01:45:43 -0700 (PDT)
Received: from mail-qe0-f52.google.com (mail-qe0-f52.google.com [209.85.128.52]) by ietfa.amsl.com (Postfix) with ESMTP id A67E621F8B07 for <gen-art@ietf.org>; Wed, 17 Apr 2013 01:45:38 -0700 (PDT)
Received: by mail-qe0-f52.google.com with SMTP id jy17so763183qeb.11 for <gen-art@ietf.org>; Wed, 17 Apr 2013 01:45:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=aJ+H2h0Ps8AljmSHPYBF8CZDUFZHJlL75BWd0bm18UQ=; b=THEZ0WUChria0IzFMvxH2yaXUmuz8IwEYgtpCF51Pj51AIAdpJE1EgwgvaHNvKUVvl RYH2qcWr/Xrm/dtNp/kmh5r+pucp35GNeQGI+9FWojYby2J0ji0eopvcQ1SdnDCYTduE 9y0MFqZauTdy7K27z+lEhj+bQSBBiWOQJOkNUiVx5BEkBI1xdiQb8wd8zdJzJ/TCLFQY BHidvA9L+stMDliL3e86Ot0kfna8NQ99DyE+Q86cdofxTCgFL0sHL5rY4+kSnWyq5MAZ t+KmjlIXLiBb66ZyDq4Hk0BiV1aLjUbfjqYwv2rc2VWT1FKvI1whad5r/IrllNwqp5t1 LyAg==
X-Received: by 10.49.5.100 with SMTP id r4mr6401003qer.36.1366188338135; Wed, 17 Apr 2013 01:45:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.81.175 with HTTP; Wed, 17 Apr 2013 01:45:18 -0700 (PDT)
In-Reply-To: <516DD8BB.5040307@ericsson.com>
References: <516CF028.2030406@ericsson.com> <CALiegfkpY1Dwx3eBvuHf=XcBFNrKq4nhUV-XQzFtBpo7BAegow@mail.gmail.com> <516D62D3.4090402@nostrum.com> <516DD8BB.5040307@ericsson.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Wed, 17 Apr 2013 10:45:18 +0200
Message-ID: <CALiegfnRZt9BuLKFLLp+Zcz8u3RQHw4iqS2ttA_kbvnUiqwNLQ@mail.gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlDBTn5wwR11Qxp9eD5jHzLfxXF65CmTZx8VqHoLEcGQxYwERkuEbooF32/zg9mCHsoNvIM
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-sipcore-sip-websocket.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-sipcore-sip-websocket-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Apr 2013 08:45:44 -0000

2013/4/17 Suresh Krishnan <suresh.krishnan@ericsson.com>:
> That sounds like a good plan. I was more concerned with the wording that
> calls this an "updated rule" and the fact that the title of Section 5.2
> "Updates to RFC3261" that implies the incremental rule could be
> interpreted to add to the rule specified in RFC3261 and lose other
> additions since (in this case losing TLS-SCTP). If you have a plan in
> place with IANA to take care of this I am fine with this approach.


Hi Suresh. Section 5.2.1 says:

----------------------
   The updated augmented BNF (Backus-Naur Form) [RFC5234] for this
   parameter is the following (the original BNF for this parameter can
   be found in [RFC3261], which was then updated by [RFC4168]):

     transport  =3D/  "WS" / "WSS"
-----------------------

So this BNF updates RFC 3261 but it's also said that same BNF in RFC
3261 was previously updated by RFC 4168. So IMHO it is clear that an
implementor should also check RFC 4168 to get the complete value for
this BNF, am I wrong?


Thanks a lot.


--
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From jari.arkko@piuha.net  Thu Apr 18 05:56:00 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26E1521F8D28 for <gen-art@ietfa.amsl.com>; Thu, 18 Apr 2013 05:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, 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 X5Hh+EKImFS1 for <gen-art@ietfa.amsl.com>; Thu, 18 Apr 2013 05:55:59 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 8F65321F8CA0 for <gen-art@ietf.org>; Thu, 18 Apr 2013 05:55:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DC07E2CC46; Thu, 18 Apr 2013 15:55:58 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j_u5Wg3tWg85; Thu, 18 Apr 2013 15:55:58 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 74CA12CC3C; Thu, 18 Apr 2013 15:55:57 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CABkgnnUaAu7iBsrUnkapebHEM2t5Snk0Kdoc=CF5joY6GTK7qA@mail.gmail.com>
Date: Thu, 18 Apr 2013 15:55:57 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <E62EF17E-63E7-4D0E-B5A7-9F819F7FA48A@piuha.net>
References: <CABkgnnUaAu7iBsrUnkapebHEM2t5Snk0Kdoc=CF5joY6GTK7qA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-nfsv4-rfc3530bis.all@tools.ietf.org
Subject: Re: [Gen-art] Partial Gen-ART review of draft-ietf-nfsv4-rfc3530bis-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2013 12:56:00 -0000

Martin,

> Summary: I have some confidence that this document is ready for
> publication.  What I have seen is sufficiently well specified that it
> could be implemented, mostly.  There are large parts of this document
> that I simply haven't read.  I can't justify spending more time.
> (Sorry Jari, I tried.)

Ok. Nevertheless, I think you've done a LOT on this, based on your =
comments. Thank you!

Jari


From mahoney@nostrum.com  Thu Apr 18 15:22:44 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D18CB21F9110 for <gen-art@ietfa.amsl.com>; Thu, 18 Apr 2013 15:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001]
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 dXhvILwIsKo4 for <gen-art@ietfa.amsl.com>; Thu, 18 Apr 2013 15:22:43 -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 5471A21F90FC for <gen-art@ietf.org>; Thu, 18 Apr 2013 15:22:40 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.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 r3IMMcGq033006 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 18 Apr 2013 17:22:38 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <5170722E.2070401@nostrum.com>
Date: Thu, 18 Apr 2013 17:22:38 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: gen-art@ietf.org
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)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-04-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2013 22:22:44 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Ben Campbell      2013-04-26   draft-ietf-6man-stable-privacy-addresses-06

Christer Holmberg 2013-05-10   draft-sheffer-running-code-04

David Black       2013-04-29   draft-ietf-karp-crypto-key-table-07

Dan Romascanu     2013-04-30   draft-ietf-oauth-revocation-07

Elwyn Davies      2013-05-14   draft-saintandre-impp-call-info-02

Francis Dupont    2013-05-14   draft-housley-rfc2050bis-01

Joel Halpern      2013-05-01   draft-ietf-netmod-rfc6021-bis-01

Kathleen Moriarty 2013-05-01   draft-ietf-ipfix-protocol-rfc5101bis-06

Meral Shirazipour 2013-04-24   draft-ietf-spfbis-4408bis-14 *

* Requested early Gen-ART review for WGLC


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From mahoney@nostrum.com  Thu Apr 18 15:22:50 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6633F21F90B9 for <gen-art@ietfa.amsl.com>; Thu, 18 Apr 2013 15:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001]
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 fpMzzHQ6LSml for <gen-art@ietfa.amsl.com>; Thu, 18 Apr 2013 15:22:46 -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 4B18921F90FC for <gen-art@ietf.org>; Thu, 18 Apr 2013 15:22:44 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.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 r3IMMhrt033010 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 18 Apr 2013 17:22:43 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51707233.4080508@nostrum.com>
Date: Thu, 18 Apr 2013 17:22:43 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: gen-art@ietf.org
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)
Subject: [Gen-art] Assignments for the 2013-04-25 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2013 22:22:50 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end     Draft
------------------------------------------------------------------------------------
Ben Campbell         2013-03-29   draft-ietf-ospf-ipv4-embedded-ipv6-routing-11 *
Ben Campbell         2013-01-24   draft-ietf-ospf-ospfv3-iid-registry-update-03 *

Dan Romascanu        2013-03-27   draft-ietf-core-coap-15 *

Elwyn Davies         2013-02-22   draft-ietf-idr-as-private-reservation-04 *

Meral Shirazipour    2013-04-03   draft-ietf-dnsext-dnssec-algo-signal-10 *

Martin Thomson       2013-02-18   draft-ietf-mpls-tp-ethernet-addressing-07 *

Peter Yee            2013-04-08   draft-ietf-pcp-upnp-igd-interworking-08 *

Roni Even            2013-01-22   draft-ietf-rmt-fcast-08 *

Suresh Krishnan      2013-03-11   draft-ietf-manet-olsrv2-metrics-rationale-03

Vijay Gurbani        2013-03-15   draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13

* Earlier draft reviewed


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

For your convenience, the review boilerplate template is included below.

Note that reviews should ideally be posted to the gen-art mailing list
by COB on Tuesday:
http://wiki.tools.ietf.org/area/gen/trac/wiki/

Jean

-------------------------------------------------------------------

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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From vkg@bell-labs.com  Fri Apr 19 08:09:41 2013
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A899E21F8C10 for <gen-art@ietfa.amsl.com>; Fri, 19 Apr 2013 08:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 gyouzQlWzOGo for <gen-art@ietfa.amsl.com>; Fri, 19 Apr 2013 08:09:41 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id E1E9721F8FD9 for <gen-art@ietf.org>; Fri, 19 Apr 2013 08:09:40 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r3JF9XQ3011306 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 19 Apr 2013 10:09:34 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r3JF9Xr5016877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Apr 2013 10:09:33 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r3JF9Up6028762; Fri, 19 Apr 2013 10:09:31 -0500 (CDT)
Message-ID: <51715EEA.60507@bell-labs.com>
Date: Fri, 19 Apr 2013 10:12:42 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130311 Thunderbird/17.0.4
MIME-Version: 1.0
To: draft-ietf-xrblock-rtcp-xr-burst-gap-discard@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: Shida Schubert <shida@ntt-at.com>, General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 15:09:41 -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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13
Reviewer: Vijay K. Gurbani
Review Date: Apr-19-2013
IETF LC End Date: Mar-15-2013
IESG Telechat date: Apr-25-2013

This document is ready as a Proposed Standard.  One minor comment and
one nit below.

Major: 0
Minor: 1
Nits: 1

Minor:
- S2.1, the sentence, "A packet that arrives within this time window
  but is too early or late to be played out or thrown away before
  playout due to packet duplication or redundancy shall be regarded as
  discarded." is hard to read and parse.

  Clearly, if a packet arrives early, it will be buffered.  Just as
  clearly, if a packet arrives too late to be played out, it will be
  discarded.  Maybe you should break the offending sentence into two
  separate sentences, one dealing with early arrival and the other
  with late arrival.

Nits
- S1.1, last paragraph: s/in[RFC3611]./in [RFC3611]./

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/


From ben@nostrum.com  Fri Apr 19 13:51:26 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ABE121F8D28; Fri, 19 Apr 2013 13:51:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MBwvi9CPW1vl; Fri, 19 Apr 2013 13:51:26 -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 EE24E21F89B0; Fri, 19 Apr 2013 13:51:25 -0700 (PDT)
Received: from [172.20.10.2] (mobile-166-147-077-136.mycingular.net [166.147.77.136]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3JKpN8v086763 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 19 Apr 2013 15:51:24 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Ben Campbell <ben@nostrum.com>
Date: Fri, 19 Apr 2013 15:51:19 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <27120AB3-75C5-4EB0-898B-FE2D354E59D4@nostrum.com>
References: <FA827D6C-D3C0-4F8A-8FF8-636A93A9646D@nostrum.com>
To: "draft-ietf-ospf-ipv4-embedded-ipv6-routing.all@tools.ietf.org" <draft-ietf-ospf-ipv4-embedded-ipv6-routing.all@tools.ietf.org>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 166.147.77.136 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-ospf-ipv4-embedded-ipv6-routing-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 20:51:26 -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-ospf-ipv4-embedded-ipv6-routing-11=20
Reviewer: Ben Campbell
Review Date: 2013-04-19
IESG Telechat date: 2013-04-25

Summary: Ready for publication as an informational RFC. All of the =
comments from my previous review of version 07 have been addressed. =
However, there=20

Major issues:

None

Minor issues:

None

Nits/editorial comments:

Note: The online IDNits tool appears to be broken today, so I was unable =
to recheck this version.

There is a new section 12 added since version 07. If there is another =
revision prior to approval, I suggest the authors make another pass at =
proofreading it. If not, the errors are all of the sort that can be =
reasonably fixed by the RFC editor. Some specifics:

-- paragraph 3, 1st sentence: "If one approach is to be deployed, it is =
the operator's decision for the choice."

-- paragraph 4, 1st sentence: "... there requires some configurations."=

From ben@nostrum.com  Fri Apr 19 14:03:01 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25CA621F919A; Fri, 19 Apr 2013 14:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7Wq0rmR8JN7; Fri, 19 Apr 2013 14:03:00 -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 9B17521F8B0A; Fri, 19 Apr 2013 14:03:00 -0700 (PDT)
Received: from [172.20.10.2] (mobile-166-147-077-136.mycingular.net [166.147.77.136]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3JL2wHF088041 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 19 Apr 2013 16:02:59 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Apr 2013 16:02:55 -0500
Message-Id: <737E8708-A346-42B8-888D-3F551C257239@nostrum.com>
To: "draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org" <draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 166.147.77.136 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-ospf-ospfv3-iid-registry-update-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 21:03:01 -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-ospf-ospfv3-iid-registry-update-03
Reviewer: Ben Campbell
Review Date: 2013-04-19
IESG Telechat date: 2013-04-25

Summary: This draft is ready for publication as a proposed standard. All =
of the comments from my review of 00 at last call have been addressed.

Major issues:

None.

Minor issues:

None.

Nits/editorial comments:

-- The abstract should mention that this draft now updates RFC 5838.

-- IDNits has a comment about the lack of pre-5378 work boilerplate that =
I do not think is valid in this case--but it might be worth checking.=

From jari.arkko@piuha.net  Fri Apr 19 14:40:07 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C22F21F8CE2 for <gen-art@ietfa.amsl.com>; Fri, 19 Apr 2013 14:40:07 -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 TuPL23jd9aMo for <gen-art@ietfa.amsl.com>; Fri, 19 Apr 2013 14:40:06 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 327EF21F8BC7 for <gen-art@ietf.org>; Fri, 19 Apr 2013 14:40:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AF3652CC50; Sat, 20 Apr 2013 00:40:04 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFinh7gOHaEN; Sat, 20 Apr 2013 00:40:04 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 04F7F2CC3C; Sat, 20 Apr 2013 00:40:04 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <E62EF17E-63E7-4D0E-B5A7-9F819F7FA48A@piuha.net>
Date: Sat, 20 Apr 2013 00:40:03 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C0E9CDF-F43A-46EF-BEC7-999860B6256C@piuha.net>
References: <CABkgnnUaAu7iBsrUnkapebHEM2t5Snk0Kdoc=CF5joY6GTK7qA@mail.gmail.com> <E62EF17E-63E7-4D0E-B5A7-9F819F7FA48A@piuha.net>
To: "A. Jean Mahoney" <mahoney@nostrum.com>
X-Mailer: Apple Mail (2.1503)
Cc: "gen-art@ietf.org Team" <gen-art@ietf.org>
Subject: [Gen-art] Another review for the NSFv4 document? (Was: Re: Partial Gen-ART review of draft-ietf-nfsv4-rfc3530bis-25)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 21:40:07 -0000

Returning to this topic. Several ADs have requested more time to do the =
review for this document (including myself). There will be more than a =
month until the approval telechat.

I will attempt to do a review (of at least the changed parts). But this =
will probably be a partial review either in terms of what parts I can =
review (hopefully different than you you Martin T). In the interest of =
sharing workload and attempting to cover a bigger part of the overall =
document, do you think it would be possible to find an additional pair =
of eyes to look at it? If we did, then Martin, me, and the new person =
would have all three have looked at this, and maybe that would be enough =
to assure that no glaring problems are left.=20

I know I am asking a lot, and this would essentially have to be someone =
volunteering to take it on. Thoughts? Anyone willing to do a partial =
review?

Jari

----Martin Stiemerling's mail------

Dear all,

I have moved the two NFSv4 drafts out of the agenda of the 04/25 =
telechat, upon request of Jari,
I also can see very good reasons to give time to address the review =
comments so far.

The next telechat in May for me is 5/30, as I am on holidays on 5/16.

However, I would be pleased if anybody of you who has already read the =
draft and has comments or discusses to raise them already by now. The =
ballots are just out this afternoon.

Thank you,

 Martin=

From jmh@joelhalpern.com  Fri Apr 19 15:24:25 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 134A821F8512; Fri, 19 Apr 2013 15:24:25 -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 52UppMhSmAYj; Fri, 19 Apr 2013 15:24:24 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 86E1C21F8528; Fri, 19 Apr 2013 15:24:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 75C4F1C22147; Fri, 19 Apr 2013 15:24:24 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.155.104.126] (unknown [129.192.170.160]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 521FD1C2212C; Fri, 19 Apr 2013 15:24:24 -0700 (PDT)
Message-ID: <5171C416.5070105@joelhalpern.com>
Date: Fri, 19 Apr 2013 18:24:22 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <5170722E.2070401@nostrum.com>
In-Reply-To: <5170722E.2070401@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, IETF discussion list <ietf@ietf.org>, David Kessens <david.kessens@nsn.com>
Subject: [Gen-art]  Review: draft-ietf-netmod-rfc6021-bis-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 22:24:25 -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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-netmod-rfc6021-bis-01
     Common YANG Data Types
Reviewer: Joel M. Halpern
Review Date: 19-April-2013
IETF LC End Date: 1-May-2013
IESG Telechat date: N/A

Summary: This document is nearly ready for publication as a Standards 
Track RFC

Major issues:
     (The following may well be a non-issue.)
     In the revision of the ietf-inet-types, the patterns for the new 
ip4-address-no-zone and ipv6-address-no-zone are drastically simplified 
from the ipv4-address and ipv6-address patterns.  The new 
ipv4-address-no-zone allows any sequence of decimal digits an periods, 
while the original was carefully defined as dotted quads of 0..255. 
Similarly, te ipv6-address-no-zone allows any arbitrary sequence of hex 
digits and colons.  The original patterns were very careful to match 
rules for validity.  Is there a reason for the change.

Minor issues:

Nits/editorial comments:

From elwynd@dial.pipex.com  Fri Apr 19 16:17:23 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B13121F8FF8 for <gen-art@ietfa.amsl.com>; Fri, 19 Apr 2013 16:17:23 -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 rUZVTvEib2P1 for <gen-art@ietfa.amsl.com>; Fri, 19 Apr 2013 16:17:22 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 3C2E921F9007 for <gen-art@ietf.org>; Fri, 19 Apr 2013 16:17:22 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1UTKYR-0000Ce-0A; Sat, 20 Apr 2013 00:17:19 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6C0E9CDF-F43A-46EF-BEC7-999860B6256C@piuha.net>
References: <CABkgnnUaAu7iBsrUnkapebHEM2t5Snk0Kdoc=CF5joY6GTK7qA@mail.gmail.com> <E62EF17E-63E7-4D0E-B5A7-9F819F7FA48A@piuha.net> <6C0E9CDF-F43A-46EF-BEC7-999860B6256C@piuha.net>
Content-Type: text/plain
Date: Sat, 20 Apr 2013 00:11:34 +0100
Message-Id: <1366413094.5273.8902.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org Team" <gen-art@ietf.org>
Subject: Re: [Gen-art] Another review for the NSFv4 document? (Was: Re: Partial Gen-ART review of draft-ietf-nfsv4-rfc3530bis-25)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 23:17:23 -0000

I will volunteer.

I drew what must be close to the shortest draft on record this month in
the normal lottery!

Regards,
Elwyn

On Sat, 2013-04-20 at 00:40 +0300, Jari Arkko wrote:
> Returning to this topic. Several ADs have requested more time to do the review for this document (including myself). There will be more than a month until the approval telechat.
> 
> I will attempt to do a review (of at least the changed parts). But this will probably be a partial review either in terms of what parts I can review (hopefully different than you you Martin T). In the interest of sharing workload and attempting to cover a bigger part of the overall document, do you think it would be possible to find an additional pair of eyes to look at it? If we did, then Martin, me, and the new person would have all three have looked at this, and maybe that would be enough to assure that no glaring problems are left. 
> 
> I know I am asking a lot, and this would essentially have to be someone volunteering to take it on. Thoughts? Anyone willing to do a partial review?
> 
> Jari
> 
> ----Martin Stiemerling's mail------
> 
> Dear all,
> 
> I have moved the two NFSv4 drafts out of the agenda of the 04/25 telechat, upon request of Jari,
> I also can see very good reasons to give time to address the review comments so far.
> 
> The next telechat in May for me is 5/30, as I am on holidays on 5/16.
> 
> However, I would be pleased if anybody of you who has already read the draft and has comments or discusses to raise them already by now. The ballots are just out this afternoon.
> 
> Thank you,
> 
>  Martin
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From martin.thomson@gmail.com  Fri Apr 19 16:38:28 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CE4621F90A5 for <gen-art@ietfa.amsl.com>; Fri, 19 Apr 2013 16:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 dyEPnjMJV8DM for <gen-art@ietfa.amsl.com>; Fri, 19 Apr 2013 16:38:28 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id B38FC21F905F for <gen-art@ietf.org>; Fri, 19 Apr 2013 16:38:27 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id e11so196286wgh.0 for <gen-art@ietf.org>; Fri, 19 Apr 2013 16:38:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=yhdFSL8LC8AF/JDBNnha9QdIVqVqPgpSHyMy8E1oEiU=; b=RJGaJNVO9P/Z1smYsotE8B5bmxAbQhqKW4oRnIb0IZc4Hxr8a9gvKVjKTOn+V2vo87 /90s6zyQesj1Xudf6OdrMJvGXF3SULxDQHIIsFA+Eb+tRHv0C7b+L/zONsem4k9isuQ7 S3e5ZlGzg7iOhdg7eaxU5YVmYXAtEnIJdobCXtGCzith/k6BMrydsyVT2WLHtwKovLE+ 2bDguRy/fdlfEbEmmqmuE0NGMwHKkZjYiAP/DoYkFmq58ez647g13Jl1iUTDJrytKVVM VtIg6ChAD3icsCykylnvwcqlTSDjN0D2EC0EzPpgK3Vds6KhjGTgvbXEbltQhwXB1TyY hAfg==
MIME-Version: 1.0
X-Received: by 10.180.97.233 with SMTP id ed9mr43959076wib.32.1366414706863; Fri, 19 Apr 2013 16:38:26 -0700 (PDT)
Received: by 10.194.33.102 with HTTP; Fri, 19 Apr 2013 16:38:26 -0700 (PDT)
Date: Fri, 19 Apr 2013 16:38:26 -0700
Message-ID: <CABkgnnVynoYEZCH7PSF89L_RzXCCoEupEApTBQRL1aEbDP1ONQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: draft-ietf-mpls-tp-ethernet-addressing.all@tools.ietf.org,  "gen-art@ietf.org" <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Subject: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 23:38:28 -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 resolve these comments along with any other (post) Last Call comments
you may receive.

Document: draft-ietf-mpls-tp-ethernet-addressing-07
Reviewer: Martin Thomson
Review Date: 2013-04-19
IETF LC End Date: 2013-02-18 (!)
IESG Telechat date: 2013-04-25

Summary: This document is almost ready for publication as proposed
standard.  There are some minor issues

Major issues: None

Minor issues:

The structure of the document is odd.  The individual pieces of
explanation are good, it's just that different bits are revealed in a
strange order.  If the intent is to describe a method of selecting an
Ethernet address to attach to MPLS-TP packets, I would have thought
that structuring the document to correspond to the prioritization of
methods would make sense.  That is, from what I can infer:
If unicast, use a unicast address (MUST for multipoint attachment,
SHOULD for others)
  1. from G-ACh, if available
  2. from static configuration, if operationally feasible
otherwise, for point-to-point links you can use
  3. the IANA-assigned special address
  4. FF-FF-FF-FF-FF-FF
Reordering might help with understanding the process.

If multicast/broadcast LSPs, there doesn't seem to be any actual
recommendations or advice in the document.  There is only an
admonition to use encapsulation, which is probably necessary for other
reasons anyhow.  So it's not clear how Section 3, paragraph 1 is
relevant to this document.  It doesn't offer any guidance on how one
might select an appropriate Ethernet address for those frames.
Presumably these could be unicast, multicast or broadcast depending on
routing requirements for the LSP, in which case maybe there is no good
advice to give. If there really is no good advice to give, or there is
no intent to provide advice for multicast/broadcast LSPs, a statement
to that effect would be helpful.

Section 3, Paragraph 2 just reiterates parts of Section 2, it could be removed.

S5: I can't reconcile "The advertised information SHOULD be persistent
across restarts."  with "Received advertisements MUST be discarded
across restarts."

S4, pp5: Why force a mapping to EUI-64?  Is canonicalization important
for some reason?

S4, pp5: The paragraph beginning with "In the event a GAP message is
not received within the previously received associated Lifetime, ..."
is a little confusing (and I'm familiar with G-ACh already).  This
could be clearer.  Maybe:  "A node could cease transmission of G-ACh
advertisements, or cease to include a Source MAC Address TLV in
advertisements, either of which cause the TLV lifetime to elapse.
After the Source MAC Address TLV lifetime has elapsed, this value
SHOULD no longer be used to select a MAC address; the node SHOULD
return to selecting MAC addresses as though no advertisements were
received."

S7.3: IETF review is a pretty high bar.  (Sadly, I missed this on
G-ACh, or I would have made the same comment.)  Did you consider
allowing IESG Approval as an alternative?


Nits/editorial comments:
There are a couple of lowercase instances of RFC2119 keywords that
could be confusing.  The very last line of S4, the second last
sentence of S2.  Consider alternative wordings for these statements.

S2, pp3: s/i.e.  /i.e., /

From salvatore.dantonio@uniparthenope.it  Sat Apr 20 17:06:26 2013
Return-Path: <salvatore.dantonio@uniparthenope.it>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57DB221F8A00; Sat, 20 Apr 2013 17:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.035
X-Spam-Level: ****
X-Spam-Status: No, score=4.035 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, MSGID_MULTIPLE_AT=1.449, RCVD_ILLEGAL_IP=1.908]
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 RUw3hRp9HRmG; Sat, 20 Apr 2013 17:06:24 -0700 (PDT)
Received: from mail.uniparthenope.it (mail.uniparthenope.it [192.167.9.244]) by ietfa.amsl.com (Postfix) with ESMTP id B657E21F888F; Sat, 20 Apr 2013 17:06:23 -0700 (PDT)
Received: from mail2.uniparthenope.it (unknown [10.1.2.108]) by mail.uniparthenope.it (Postfix) with SMTP id D0D4F42536; Sun, 21 Apr 2013 00:06:22 +0000 (UTC)
Received: from (unknown [192.168.241.108]) by mail2.uniparthenope.it with smtp id 1da8_4bd40ed6_aa17_11e2_9101_001372515a5c; Sun, 21 Apr 2013 02:06:21 +0200
Received: from spamk.uniparthenope.it (localhost [127.0.0.1]) by spamk.uniparthenope.it (Postfix) with ESMTP id 781BFC432C; Sun, 21 Apr 2013 02:06:20 +0200 (CEST)
Received: by spamk.uniparthenope.it (Postfix, from userid 500) id 5D40EC4351; Sun, 21 Apr 2013 02:06:20 +0200 (CEST)
Received: from mail.uniparthenope.it (unknown [192.168.241.109]) by spamk.uniparthenope.it (Postfix) with ESMTP id B34CAC4377; Sun, 21 Apr 2013 02:06:13 +0200 (CEST)
Received: by mail.uniparthenope.it (Postfix, from userid 108) id 9DFC0421AD; Sun, 21 Apr 2013 02:06:13 +0200 (CEST)
Received: from saldantoPC (unknown [2.237.123.176]) (Authenticated sender: salvatore.dantonio@uniparthenope.it) by mail.uniparthenope.it (Postfix) with ESMTPA id ABE80421AD; Sun, 21 Apr 2013 02:06:11 +0200 (CEST)
From: "Salvatore D'Antonio" <salvatore.dantonio@uniparthenope.it>
To: "'Benoit Claise'" <bclaise@cisco.com>
References: <20130401072846.32360.9502.idtracker@ietfa.amsl.com> <5162C44B.5030904@cisco.com> <005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it> <516BCB97.9040404@cisco.com>
In-Reply-To: <516BCB97.9040404@cisco.com>
Date: Sun, 21 Apr 2013 02:06:14 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac45veJiRHrdfH9cTm69S7sEnZNliAEY1GBQ
Content-Language: it
Message-ID: <001001ce3e24$0a931840$1fb948c0$@dantonio@uniparthenope.it>
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0011_01CE3E34.CE1BE840"
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.42/RELEASE, bases: 20130420 #9915320, check: 20130421 clean
Cc: rahulp@cisco.com, 'IETF discussion list' <ietf@ietf.org>, draft-ietf-ipfix-flow-selection-tech@tools.ietf.org, apps-discuss@ietf.org, 'General Area Review Team' <gen-art@ietf.org>, 'S Moonesamy' <sm+ietf@elandsys.com>, ipfix-chairs@tools.ietf.org, ipfix@ietf.org, iesg@ietf.org
Subject: [Gen-art] R: R: Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Apr 2013 00:06:26 -0000

Messaggio multipart in formato MIME.

------=_NextPart_000_0011_01CE3E34.CE1BE840
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Dear Benoit, all

=20

I submitted v16 of the Internet Draft.

=20

I modified section 9.1.1 on the maintenance of the flowSelectorAlgorithm =
registry and fixed the editorial issue in section  6.1.1

=20

I have also used MUST in section 6.1

=20

Best regards,

=20

Salvatore

=20

=20

Da: Benoit Claise [mailto:bclaise@cisco.com]=20
Inviato: luned=C3=AC 15 aprile 2013 11:43
A: Salvatore D'Antonio
Cc: draft-ietf-ipfix-flow-selection-tech@tools.ietf.org; =
ipfix-chairs@tools.ietf.org; 'S Moonesamy'; apps-discuss@ietf.org; =
iesg@ietf.org; 'Joel M. Halpern'; 'A. Jean Mahoney'; 'General Area =
Review Team'; 'IETF discussion list'; rahulp@cisco.com; ipfix@ietf.org
Oggetto: Re: R: Last Call Expired: =
<draft-ietf-ipfix-flow-selection-tech-14.txt>

=20

Salvatore

Dear all,

=20

A new version of the Internet Draft on Flow Selection Techniques has =
been submitted. It contains the following changes:

-          A new section illustrating the difference between =
Intermediate Flow Selection Process and Intermediate Selection Process =
has been added,

-          The sentence "In order to be compliant with this document, at =
least the Property  Match Filtering MUST be implemented." has been =
removed in Section 1,

-          =E2=80=9CMUST=E2=80=9D has been replaced with =
=E2=80=9CSHOULD=E2=80=9D in Section 5.1,

Actually, the feedback was:

In Section 1:=20

  "In order to be compliant with this document, at least the Property=20
   Match Filtering MUST be implemented."=20

The above text is repeated in Section 5.1.  I suggest removing this =
sentence as it does not seem related to scope.=20

My reading of the "MUST" is that it is being used for compliance instead =
of the reasons described in RFC 2119.  I suggest reviewing the usage of =
RFC 2119 key words in Section 5.1.=20

So the solution is not to change MUST to SHOULD.
The question is whether "MUST" versus "must" must be used.
I understand the concern. For compliance reason with the PSAMP RFC 5475 =
(which is closely related) ...


 <http://tools.ietf.org/html/rfc5475#section-7> 7.  Parameters for the =
Description of Selection Techniques

   This section gives an overview of different alternative selection
   schemes and their required parameters.  In order to be compliant with
   PSAMP, at least one of proposed schemes MUST be implemented.
=20

... I would keep the initial "MUST" from the previous draft version.=20

-          =E2=80=9CThe flowSelectorAlgorithm registry is maintained by =
IANA." has been replaced with =E2=80=9CIANA is requested to create the =
flowSelectorAlgorithm registry.=E2=80=9D

-          The sentence "The registry can be updated when specifications =
of the new  technique(s) and any new Information Elements are provided." =
has been removed since it did not clarify how the registry will be =
managed.

-           Section 6.1.1 =E2=80=9CProperty Match Filtering=E2=80=9D has =
been changed by adding some text on how Property Match Filtering can be  =
used by an Intermediate Flow Selection Process in the Metering Process, =
in the  Exporting Process and within an IPFIX Mediator.

When publishing a new version, please correct this editorial issue.

 " ... and Flow duration. in
   the An example is the selection of the largest ..."





=20

Best regards,

=20

Salvatore

=20

Da: Benoit Claise [mailto:bclaise@cisco.com]=20
Inviato: luned=C3=AC 8 aprile 2013 15:21
A: draft-ietf-ipfix-flow-selection-tech@tools.ietf.org
Cc: ipfix-chairs@tools.ietf.org
Oggetto: Fwd: Last Call Expired: =
<draft-ietf-ipfix-flow-selection-tech-14.txt>

=20

Dear authors,

The IETF last call has finished.
Can you please update your draft based on the feedback received.
Then I will progress it.

Regards, Benoit



-------- Original Message --------=20


Subject:=20

Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>


Date:=20

Mon, 01 Apr 2013 00:28:46 -0700


From:=20

DraftTracker Mail System  <mailto:iesg-secretary@ietf.org> =
<iesg-secretary@ietf.org>


To:=20

iesg@ietf.org, ipfix-chairs@tools.ietf.org, =
draft-ietf-ipfix-flow-selection-tech@tools.ietf.org


CC:=20

iesg-secretary@ietf.org

=20

Please DO NOT reply to this email.
=20
I-D: <draft-ietf-ipfix-flow-selection-tech-14.txt>
ID Tracker URL: =
http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tech/
=20
IETF Last Call has ended, and the state has been changed to
Waiting for AD Go-Ahead.
=20
=20
=20

=20

=20

  _____ =20

Nessun virus nel messaggio.
Controllato da AVG - www.avg.com
Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data di =
rilascio: 07/04/2013





*************************************************************************=
******************************

IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO

=20

Il 5 per mille all'Universit=C3=A0 degli Studi di Napoli =
"Parthenope"incrementa le borse di studio agli studenti - codice fiscale =
80018240632=20

 <http://www.uniparthenope.it/index.php/5xmille> =
http://www.uniparthenope.it/index.php/5xmille=20

=20

 =
<http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-p=
arthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-d=
el-5-per-mille> =
http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-pa=
rthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-de=
l-5-per-mille

=20
Questa informativa =C3=A8 inserita in automatico dal sistema al fine =
esclusivo della realizzazione dei fini istituzionali dell'ente.

=20






*************************************************************************=
******************************

IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO

=20

Il 5 per mille all'Universit=C3=A0 degli Studi di Napoli =
"Parthenope"incrementa le borse di studio agli studenti - codice fiscale =
80018240632=20

 <http://www.uniparthenope.it/index.php/5xmille> =
http://www.uniparthenope.it/index.php/5xmille=20

=20

 =
<http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-p=
arthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-d=
el-5-per-mille> =
http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-pa=
rthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-de=
l-5-per-mille

=20
Questa informativa =C3=A8 inserita in automatico dal sistema al fine =
esclusivo della realizzazione dei fini istituzionali dell'ente.

=20

=20

=20


******************************************************************************=09=0A
IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO=0A
 =0A
Il 5 per mille all'Universita' degli Studi di Napoli "Parthenope" incrementa le borse di studio agli studenti - codice fiscale 80018240632=0A
http://www.uniparthenope.it/index.php/5xmille =0A
 =0A
http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille=0A
 =0A
Questa informativa e' inserita in automatico dal sistema al fine esclusivo della realizzazione dei fini istituzionali dell'ente.=0A

------=_NextPart_000_0011_01CE3E34.CE1BE840
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
h2
	{mso-style-priority:9;
	mso-style-link:"Titolo 2 Carattere";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:18.0pt;
	font-family:"Times New Roman","serif";
	color:black;
	font-weight:bold;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	margin-bottom:5.95pt;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"Preformattato HTML Carattere";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.PreformattatoHTMLCarattere
	{mso-style-name:"Preformattato HTML Carattere";
	mso-style-priority:99;
	mso-style-link:"Preformattato HTML";
	font-family:Consolas;
	color:black;}
span.StileMessaggioDiPostaElettronica20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.h2
	{mso-style-name:h2;}
span.Titolo2Carattere
	{mso-style-name:"Titolo 2 Carattere";
	mso-style-priority:9;
	mso-style-link:"Titolo 2";
	font-family:"Cambria","serif";
	color:#4F81BD;
	font-weight:bold;}
p.western, li.western, div.western
	{mso-style-name:western;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	margin-bottom:5.95pt;
	margin-left:0cm;
	font-size:8.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
p.cjk, li.cjk, div.cjk
	{mso-style-name:cjk;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	margin-bottom:5.95pt;
	margin-left:0cm;
	font-size:8.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
p.ctl, li.ctl, div.ctl
	{mso-style-name:ctl;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	margin-bottom:5.95pt;
	margin-left:0cm;
	font-size:8.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.StileMessaggioDiPostaElettronica27
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 2.0cm 2.0cm 2.0cm;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:217212090;
	mso-list-type:hybrid;
	mso-list-template-ids:308057158 -1513439274 134807555 134807557 =
134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DEN-GB link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dear Benoit, all<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I submitted v16 of the Internet =
Draft.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I modified section 9.1.1 on the maintenance of the =
flowSelectorAlgorithm
registry and fixed the editorial issue in section =
=C2=A06.1.1<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have also used MUST in section =
6.1<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Best regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Salvatore<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DIT =
style=3D'font-size:10.0pt;font-family:"Segoe UI","sans-serif";
color:windowtext'>Da:</span></b><span lang=3DIT =
style=3D'font-size:10.0pt;
font-family:"Segoe UI","sans-serif";color:windowtext'> Benoit Claise
[mailto:bclaise@cisco.com] <br>
<b>Inviato:</b> luned=C3=AC 15 aprile 2013 11:43<br>
<b>A:</b> Salvatore D'Antonio<br>
<b>Cc:</b> draft-ietf-ipfix-flow-selection-tech@tools.ietf.org;
ipfix-chairs@tools.ietf.org; 'S Moonesamy'; apps-discuss@ietf.org;
iesg@ietf.org; 'Joel M. Halpern'; 'A. Jean Mahoney'; 'General Area =
Review
Team'; 'IETF discussion list'; rahulp@cisco.com; ipfix@ietf.org<br>
<b>Oggetto:</b> Re: R: Last Call Expired:
&lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></span></p>=


</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=3DMsoNormal>Salvatore<o:p></o:p></p>

</div>

<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dear all,</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A new version of the Internet Draft on Flow Selection =
Techniques
has been submitted. It contains the following =
changes:</span><o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A new section illustrating the difference between =
Intermediate Flow
Selection Process and Intermediate Selection Process has been =
added,</span><o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The sentence &quot;In order to be compliant with this =
document,
at least the Property &nbsp;Match Filtering MUST be implemented.&quot; =
has been
removed in Section 1,</span><o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>=E2=80=9CMUST=E2=80=9D has been replaced with =
=E2=80=9CSHOULD=E2=80=9D in Section 5.1,</span><o:p></o:p></p>

</blockquote>

<p class=3DMsoNormal>Actually, the feedback was:<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>In Section 1: <br>
<br>
&nbsp; &quot;In order to be compliant with this document, at least the =
Property
<br>
&nbsp;&nbsp; Match Filtering MUST be implemented.&quot; <br>
<br>
The above text is repeated in Section 5.1.&nbsp; I suggest removing this =
sentence
as it does not seem related to scope. <br>
<br>
My reading of the &quot;MUST&quot; is that it is being used for =
compliance
instead of the reasons described in RFC 2119.&nbsp; I suggest reviewing =
the
usage of RFC 2119 key words in Section 5.1. <o:p></o:p></p>

<p class=3DMsoNormal>So the solution is not to change MUST to =
SHOULD.<br>
The question is whether &quot;MUST&quot; versus &quot;must&quot; must be =
used.<br>
I understand the concern. For compliance reason with the PSAMP RFC 5475 =
(which
is closely related) ...<o:p></o:p></p>

<h2><a name=3Dsection-7></a><a =
href=3D"http://tools.ietf.org/html/rfc5475#section-7"><span
style=3D'font-family:"Courier New"'>7</span></a><span =
style=3D'font-family:"Courier New"'>.=C2=A0
Parameters for the Description of Selection =
Techniques<o:p></o:p></span></h2>

<pre>=C2=A0=C2=A0 This section gives an overview of different =
alternative selection<o:p></o:p></pre><pre>=C2=A0=C2=A0 schemes and =
their required parameters.=C2=A0 In order to be compliant =
with<o:p></o:p></pre><pre>=C2=A0=C2=A0 PSAMP, at least one of proposed =
schemes MUST be =
implemented.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre>

<p class=3DMsoNormal>... I would keep the initial &quot;MUST&quot; from =
the
previous draft version. <o:p></o:p></p>

<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>=E2=80=9CThe flowSelectorAlgorithm registry is maintained =
by IANA.&quot;
has been replaced with =E2=80=9CIANA is requested to create the =
flowSelectorAlgorithm
registry.=E2=80=9D</span><o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The sentence &quot;The registry can be updated when
specifications of the new&nbsp; technique(s) and any new Information =
Elements
are provided.&quot; has been removed since it did not clarify how the =
registry
will be managed.</span><o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;Section 6.1.1 =E2=80=9CProperty Match =
Filtering=E2=80=9D has been changed
by adding some text on how Property Match Filtering can be &nbsp;used by =
an
Intermediate Flow Selection Process in the Metering Process, in the
&nbsp;Exporting Process and within an IPFIX =
Mediator.</span><o:p></o:p></p>

</blockquote>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>When publishing a =
new version,
please correct this editorial issue.<o:p></o:p></p>

<pre>=C2=A0&quot; ... and Flow duration. =
in<o:p></o:p></pre><pre>=C2=A0=C2=A0 the An example is the selection of =
the largest ...&quot;<o:p></o:p></pre>

<p class=3DMsoNormal><br>
<br>
<o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Best regards,</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Salvatore</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DIT =
style=3D'font-size:10.0pt'>Da:</span></b><span
lang=3DIT style=3D'font-size:10.0pt'> Benoit Claise [<a
href=3D"mailto:bclaise@cisco.com">mailto:bclaise@cisco.com</a>] <br>
<b>Inviato:</b> luned=C3=AC 8 aprile 2013 15:21<br>
<b>A:</b> <a =
href=3D"mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org">draft=
-ietf-ipfix-flow-selection-tech@tools.ietf.org</a><br>
<b>Cc:</b> <a =
href=3D"mailto:ipfix-chairs@tools.ietf.org">ipfix-chairs@tools.ietf.org</=
a><br>
<b>Oggetto:</b> Fwd: Last Call Expired: =
&lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;</span><o:p></o:p></p>=


</div>

</div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal>Dear authors,<br>
<br>
The IETF last call has finished.<br>
Can you please update your draft based on the feedback received.<br>
Then I will progress it.<br>
<br>
Regards, Benoit<o:p></o:p></p>

<div>

<p class=3DMsoNormal><br>
<br>
-------- Original Message -------- <o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright =
style=3D'text-align:right'><b>Subject: </b><o:p></o:p></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>Last Call Expired:
  &lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>Date: =
</b><o:p></o:p></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>Mon, 01 Apr 2013 00:28:46 -0700<o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>From: =
</b><o:p></o:p></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>DraftTracker Mail System <a
  =
href=3D"mailto:iesg-secretary@ietf.org">&lt;iesg-secretary@ietf.org&gt;</=
a><o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>To: =
</b><o:p></o:p></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal><a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>, <a
  =
href=3D"mailto:ipfix-chairs@tools.ietf.org">ipfix-chairs@tools.ietf.org</=
a>, <a
  =
href=3D"mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org">draft=
-ietf-ipfix-flow-selection-tech@tools.ietf.org</a><o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>CC: =
</b><o:p></o:p></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal><a =
href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a><o:p><=
/o:p></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>&nbsp;<o:p></o:p></p>

<pre>Please DO NOT reply to this =
email.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>I-D: =
&lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></pre><pre>=
ID Tracker URL: <a
href=3D"http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-t=
ech/">http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tec=
h/</a><o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>IETF Last Call =
has ended, and the state has been changed =
to<o:p></o:p></pre><pre>Waiting for AD =
Go-Ahead.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:p></o=
:p></pre><pre>&nbsp;<o:p></o:p></pre>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D1 width=3D"100%" noshade style=3D'color:#A0A0A0' =
align=3Dcenter>

</div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Nessun
virus nel messaggio.<br>
Controllato da AVG - <a href=3D"http://www.avg.com">www.avg.com</a><br>
Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data di =
rilascio:
07/04/2013<o:p></o:p></p>

<p class=3DMsoNormal><br>
<br>
<o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>******************************=
*************************************************************************=
</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>IL MERITO DEGLI =
STUDENTI&nbsp;VIENE
RICONOSCIUTO</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>Il 5 per mille =
all'Universit=C3=A0 degli
Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli
studenti - codice fiscale <b>80018240632</b> </span><o:p></o:p></p>

<p class=3Dwestern style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><a
href=3D"http://www.uniparthenope.it/index.php/5xmille"><span =
style=3D'font-family:
"Arial","sans-serif"'>http://www.uniparthenope.it/index.php/5xmille</span=
></a><span
style=3D'font-family:"Arial","sans-serif"'>&nbsp;</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<o:p></o:p></p>

<p class=3Dwestern style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><a
href=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/29=
43-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-pro=
venti-del-5-per-mille"><span
style=3D'font-family:"Arial","sans-serif"'>http://www.uniparthenope.it/in=
dex.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di=
-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</span></a><o:p><=
/o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<span
style=3D'font-family:"Arial","sans-serif"'><br>
Questa informativa =C3=A8 inserita in automatico dal sistema al fine =
esclusivo della
realizzazione dei fini istituzionali dell'ente.</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><br>
<br>
<br>
<o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>******************************=
*************************************************************************=
</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>IL MERITO DEGLI =
STUDENTI&nbsp;VIENE
RICONOSCIUTO</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>Il 5 per mille =
all'Universit=C3=A0 degli
Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli
studenti - codice fiscale <b>80018240632</b> </span><o:p></o:p></p>

<p class=3Dwestern style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><a
href=3D"http://www.uniparthenope.it/index.php/5xmille"><span =
style=3D'font-family:
"Arial","sans-serif"'>http://www.uniparthenope.it/index.php/5xmille</span=
></a><span
style=3D'font-family:"Arial","sans-serif"'>&nbsp;</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<o:p></o:p></p>

<p class=3Dwestern style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><a
href=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/29=
43-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-pro=
venti-del-5-per-mille"><span
style=3D'font-family:"Arial","sans-serif"'>http://www.uniparthenope.it/in=
dex.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di=
-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</span></a><o:p><=
/o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<span
style=3D'font-family:"Arial","sans-serif"'><br>
Questa informativa =C3=A8 inserita in automatico dal sistema al fine =
esclusivo della
realizzazione dei fini istituzionali dell'ente.</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>


<br>=
<STYLE TYPE=3D"text/css">=0A
=09<!--=0A
=09=09@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }=0A
=09=09P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }=0A
=09=09P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }=0A
=09=09P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }=0A
=09=09P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }=0A
=09=09A:link { color: #0000ff }=0A
=09-->=0A
=09</STYLE>=0A
<!--</HEAD></BODY>-->=0A
<P LANG=3D"it-IT" TEXT=3D"#000000" LINK=3D"#0000ff" DIR=3D"LTR">=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">*******************************************************************************************************</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">IL=0A
MERITO DEGLI STUDENTI&nbsp;VIENE RICONOSCIUTO</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">Il=0A
5 per mille all'Universit&agrave degli Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli studenti=0A
- codice fiscale </FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif"><B>80018240632</B></FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">=0A
</FONT></FONT>=0A
</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/5xmille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/5xmille</U></FONT></FONT></A><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">&nbsp;</FONT></FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</U></FONT></FONT></A></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;<FONT FACE=3D"Arial, sans-serif"><BR>Questa=0A
informativa &egrave inserita in automatico dal sistema al fine esclusivo=0A
della realizzazione dei fini istituzionali dell&#39;ente.</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><BR>=0A
</P>=0A
<!--</BODY>-->=0A
<!--</HTML>-->=0A
<br>=
</body>

</html>

<br>=
<STYLE TYPE=3D"text/css">=0A
=09<!--=0A
=09=09@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }=0A
=09=09P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }=0A
=09=09P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }=0A
=09=09P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }=0A
=09=09P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }=0A
=09=09A:link { color: #0000ff }=0A
=09-->=0A
=09</STYLE>=0A
<!--</HEAD></BODY>-->=0A
<P LANG=3D"it-IT" TEXT=3D"#000000" LINK=3D"#0000ff" DIR=3D"LTR">=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">*******************************************************************************************************</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">IL=0A
MERITO DEGLI STUDENTI&nbsp;VIENE RICONOSCIUTO</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">Il=0A
5 per mille all'Universit&agrave degli Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli studenti=0A
- codice fiscale </FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif"><B>80018240632</B></FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">=0A
</FONT></FONT>=0A
</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/5xmille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/5xmille</U></FONT></FONT></A><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">&nbsp;</FONT></FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</U></FONT></FONT></A></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;<FONT FACE=3D"Arial, sans-serif"><BR>Questa=0A
informativa &egrave inserita in automatico dal sistema al fine esclusivo=0A
della realizzazione dei fini istituzionali dell&#39;ente.</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><BR>=0A
</P>=0A
<!--</BODY>-->=0A
<!--</HTML>-->=0A
<br>=
------=_NextPart_000_0011_01CE3E34.CE1BE840--

From Francis.Dupont@fdupont.fr  Mon Apr 22 05:36:41 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C58321F8F6C for <gen-art@ietfa.amsl.com>; Mon, 22 Apr 2013 05:36:41 -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 E0tvYuNPgQeN for <gen-art@ietfa.amsl.com>; Mon, 22 Apr 2013 05:36:40 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 7574621F8F17 for <gen-art@ietf.org>; Mon, 22 Apr 2013 05:36:40 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r3MCab6A070382; Mon, 22 Apr 2013 14:36:37 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201304221236.r3MCab6A070382@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 22 Apr 2013 14:36:37 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: sm@resistor.net, draft-housley-rfc2050bis.all@tools.ietf.org
Subject: [Gen-art] review of draft-housley-rfc2050bis-01.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 12:36:41 -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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-housley-rfc2050bis-01.txt
Reviewer: Francis Dupont
Review Date: 20130420
IETF LC End Date: 20130514
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - ToC page 2 and 9 page 6: Acknowledgements -> Acknowledgments

 - 3 page 3: (more for the RFC Editor) the word "IANA" should be the first
  of the page 4, not the last of page 3.

 - 7 page 6: IMHO it is the right place to add a reference to the RPKI
  (i.e., how the security considerations are implemented)

 - 9 page 6: I give to SM the opportunity to get his full name in the document...

Regards

Francis.Dupont@fdupont.fr

From jari.arkko@piuha.net  Mon Apr 22 06:19:25 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F234B21F8738 for <gen-art@ietfa.amsl.com>; Mon, 22 Apr 2013 06:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, 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 ck7Q-r5h7TeO for <gen-art@ietfa.amsl.com>; Mon, 22 Apr 2013 06:19:24 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id DDBAB21F8691 for <gen-art@ietf.org>; Mon, 22 Apr 2013 06:19:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3350C2CC46; Mon, 22 Apr 2013 16:19:23 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S79eOy_ESBEx; Mon, 22 Apr 2013 16:19:22 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 464422CC3C; Mon, 22 Apr 2013 16:19:22 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201304221236.r3MCab6A070382@givry.fdupont.fr>
Date: Mon, 22 Apr 2013 16:19:22 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <6BD017A3-4A75-4CC9-99B0-C718D4A78787@piuha.net>
References: <201304221236.r3MCab6A070382@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1503)
Cc: sm@resistor.net, gen-art@ietf.org, draft-housley-rfc2050bis.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-housley-rfc2050bis-01.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 13:19:25 -0000

Thank you for the review, Francis! Russ, I assume you will collect these =
(and other) editorial issues and issue a new version when the time is =
appropriate.

Jari

On Apr 22, 2013, at 3:36 PM, Francis Dupont <Francis.Dupont@fdupont.fr> =
wrote:

> 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-housley-rfc2050bis-01.txt
> Reviewer: Francis Dupont
> Review Date: 20130420
> IETF LC End Date: 20130514
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
> - ToC page 2 and 9 page 6: Acknowledgements -> Acknowledgments
>=20
> - 3 page 3: (more for the RFC Editor) the word "IANA" should be the =
first
>  of the page 4, not the last of page 3.
>=20
> - 7 page 6: IMHO it is the right place to add a reference to the RPKI
>  (i.e., how the security considerations are implemented)
>=20
> - 9 page 6: I give to SM the opportunity to get his full name in the =
document...
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr


From bill.wu@huawei.com  Tue Apr 23 00:19:51 2013
Return-Path: <bill.wu@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50A8F21F949A for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 00:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.514
X-Spam-Level: 
X-Spam-Status: No, score=-5.514 tagged_above=-999 required=5 tests=[AWL=1.085,  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 aq46O7HlvLpa for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 00:19:49 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6169A21F86D5 for <gen-art@ietf.org>; Tue, 23 Apr 2013 00:19:47 -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 ASC25771; Tue, 23 Apr 2013 07:19:46 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 23 Apr 2013 08:19:15 +0100
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 23 Apr 2013 08:19:42 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.113]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.01.0323.007; Tue, 23 Apr 2013 15:19:37 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>, "draft-ietf-xrblock-rtcp-xr-burst-gap-discard@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-burst-gap-discard@tools.ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13
Thread-Index: AQHOPQ/2Y7lbOXTGiUCDAQK6vsjD5Jjjayvg
Date: Tue, 23 Apr 2013 07:19:36 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43A4DC30@nkgeml501-mbs.china.huawei.com>
References: <51715EEA.60507@bell-labs.com>
In-Reply-To: <51715EEA.60507@bell-labs.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Shida Schubert <shida@ntt-at.com>, General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 07:19:51 -0000

Hi, Vijay:
Thank for your valuable review. See reply inline below.

-----Original Message-----
From: Vijay K. Gurbani [mailto:vkg@bell-labs.com]=20
Sent: Friday, April 19, 2013 11:13 PM
To: draft-ietf-xrblock-rtcp-xr-burst-gap-discard@tools.ietf.org
Cc: General Area Review Team; Romascanu, Dan (Dan); Shida Schubert; Gonzalo=
 Camarillo
Subject: Gen-ART review of draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13

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-xrblock-rtcp-xr-burst-gap-discard-13
Reviewer: Vijay K. Gurbani
Review Date: Apr-19-2013
IETF LC End Date: Mar-15-2013
IESG Telechat date: Apr-25-2013

This document is ready as a Proposed Standard.  One minor comment and
one nit below.

Major: 0
Minor: 1
Nits: 1

Minor:
- S2.1, the sentence, "A packet that arrives within this time window
  but is too early or late to be played out or thrown away before
  playout due to packet duplication or redundancy shall be regarded as
  discarded." is hard to read and parse.


  Clearly, if a packet arrives early, it will be buffered.  Just as
  clearly, if a packet arrives too late to be played out, it will be
  discarded.  Maybe you should break the offending sentence into two
  separate sentences, one dealing with early arrival and the other
  with late arrival.

[Qin]: Agree and will split.

Nits
- S1.1, last paragraph: s/in[RFC3611]./in [RFC3611]./

[Qin]: Good catch, thanks.

Thanks,

- vijay
--=20
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/


From meral.shirazipour@ericsson.com  Tue Apr 23 09:11:57 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6038321F96C4 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 09:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 HsivPu1r3NSW for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 09:11:56 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC5221F96B4 for <gen-art@ietf.org>; Tue, 23 Apr 2013 09:11:56 -0700 (PDT)
X-AuditID: c6180641-b7faf6d00000096b-87-5176b2cb3061
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id EE.A9.02411.BC2B6715; Tue, 23 Apr 2013 18:11:55 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0318.004; Tue, 23 Apr 2013 12:11:54 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-dnsext-dnssec-algo-signal.all@tools.ietf.org" <draft-ietf-dnsext-dnssec-algo-signal.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-dnsext-dnssec-algo-signal-10
Thread-Index: Ac5APQcnv/Q91x/7R9O+t45YUZiueA==
Date: Tue, 23 Apr 2013 16:11:53 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A0C49C4@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A0C49C4eusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUyuXSPt+7pTWWBBptny1l8eHeb1eLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfG/s4d7AVL5Sver+dpYHwt3cXIySEhYCLR 8PcDE4QtJnHh3nq2LkYuDiGBo4wS7e86oJzljBJNm5ewg1SxCVhIbP/9nBUkISKwiFHiz4bZ YAlhgSCJ+7efgY0SEQiXOPywixHC1pNovPCPGcRmEVCVuNJ2B8zmFfCW2Hl7ISuIzQi0+vup NWC9zALiEreezIc6SUBiyZ7zzBC2qMTLx/9YIWxliSVP9rNA1OdLvFt8ng1ipqDEyZlPWCYw Cs1CMmoWkrJZSMog4joSC3Z/YoOwtSWWLXzNDGOfOfCYCVl8ASP7KkaO0uLUstx0I8NNjMB4 OCbB5riDccEny0OM0hwsSuK8oa4XAoQE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwWikt7BdS U3cMq7WJK/nP/XzCv6j8JB0b3ki12YzejPKvam5NjhBNlsn7qa8X/n6XTf+67/P+b1FuvB8c dqJ5ypkGqdccfYFPQydf3N4rn3cv/+j5Kenvgk/Fb+IpqU25bBPA+8LJr2z1lnzm7kl/r90t PBcWYCehMKdz6gnJJxPqvpbv5KlRYinOSDTUYi4qTgQAHHUReFUCAAA=
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-dnsext-dnssec-algo-signal-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 16:11:57 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A0C49C4eusaamb107ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at < http://wiki.tools.ietf.org/area/gen/trac/wiki/Ge=
nArtfaq> .

Please wait for direction from your document shepherd or AD before posting =
a new version of the draft.

Document: draft-ietf-dnsext-dnssec-algo-signal-10
Reviewer: Meral Shirazipour
Review Date: 2013-04-23
IETF LC End Date: 2013-04-03
IESG Telechat date: 2013-04-25

Summary: This draft is ready to be published as Standard RFC.


Best Regards,
Meral
---
Meral Shirazipour
Ericsson Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A0C49C4eusaamb107ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at &lt;
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt; .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please wait for direction from your document shepher=
d or AD before posting a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-dnsext-dnssec-algo-signal-10<o:=
p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-04-23<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-04-03<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2013-04-25<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready to be published as Stan=
dard RFC.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A0C49C4eusaamb107ericsso_--

From jari.arkko@piuha.net  Tue Apr 23 12:19:24 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50A7821F8E79 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 12:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, 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 A+JWZUmHjfAC for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 12:19:23 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 722F721F8E8F for <gen-art@ietf.org>; Tue, 23 Apr 2013 12:19:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 555572CC56; Tue, 23 Apr 2013 22:19:22 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SEyZg1MJwNQN; Tue, 23 Apr 2013 22:19:21 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 223492CC55; Tue, 23 Apr 2013 22:19:21 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51707233.4080508@nostrum.com>
Date: Tue, 23 Apr 2013 22:19:20 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <727796A1-3C68-47F2-9AE2-CE56D1B03EEF@piuha.net>
References: <51707233.4080508@nostrum.com>
To: Elwyn Davies <elwynd@dial.pipex.com>, Jon.Mitchell@microsoft.com, Susan Hares <shares@ndzh.com>
X-Mailer: Apple Mail (2.1503)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>
Subject: [Gen-art] draft-ietf-idr-as-private-reservation gen-art review status
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 19:19:24 -0000

Elwyn, Sue, Jon:

We are talking about this draft on Thursday evening at the IESG. I see =
that there was a review and discussion earlier in the year. Thank you =
for the reviews and responses! The Gen-ART reviews are very important =
for me, as they enable me to spend time on a number of topics and not =
just the IESG document reviews.

But I had a question. Do you all feel that everything raised in the =
discussion has been properly addressed, and everyone is happy moving =
forward?

Jari


From jari.arkko@piuha.net  Tue Apr 23 12:28:57 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95EE821F9660 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 12:28:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, 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 7KocsrIVfiko for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 12:28:56 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 13FAA21F9609 for <gen-art@ietf.org>; Tue, 23 Apr 2013 12:28:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5D89B2CC56; Tue, 23 Apr 2013 22:28:55 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z5FnJ4MlJ3sP; Tue, 23 Apr 2013 22:28:54 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 84C932CC55; Tue, 23 Apr 2013 22:28:54 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CABkgnnVynoYEZCH7PSF89L_RzXCCoEupEApTBQRL1aEbDP1ONQ@mail.gmail.com>
Date: Tue, 23 Apr 2013 22:28:54 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <E925FC26-CEA4-4DE6-AB95-8397791B5B80@piuha.net>
References: <CABkgnnVynoYEZCH7PSF89L_RzXCCoEupEApTBQRL1aEbDP1ONQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: gen-art@ietf.org, draft-ietf-mpls-tp-ethernet-addressing.all@tools.ietf.org, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 19:28:57 -0000

Martin: Thank you for the review!

Authors, Stewart, can you take a look at the issues below?

Jari

On Apr 20, 2013, at 2:38 AM, Martin Thomson <martin.thomson@gmail.com> =
wrote:

> 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 (post) Last Call =
comments
> you may receive.
>=20
> Document: draft-ietf-mpls-tp-ethernet-addressing-07
> Reviewer: Martin Thomson
> Review Date: 2013-04-19
> IETF LC End Date: 2013-02-18 (!)
> IESG Telechat date: 2013-04-25
>=20
> Summary: This document is almost ready for publication as proposed
> standard.  There are some minor issues
>=20
> Major issues: None
>=20
> Minor issues:
>=20
> The structure of the document is odd.  The individual pieces of
> explanation are good, it's just that different bits are revealed in a
> strange order.  If the intent is to describe a method of selecting an
> Ethernet address to attach to MPLS-TP packets, I would have thought
> that structuring the document to correspond to the prioritization of
> methods would make sense.  That is, from what I can infer:
> If unicast, use a unicast address (MUST for multipoint attachment,
> SHOULD for others)
>  1. from G-ACh, if available
>  2. from static configuration, if operationally feasible
> otherwise, for point-to-point links you can use
>  3. the IANA-assigned special address
>  4. FF-FF-FF-FF-FF-FF
> Reordering might help with understanding the process.
>=20
> If multicast/broadcast LSPs, there doesn't seem to be any actual
> recommendations or advice in the document.  There is only an
> admonition to use encapsulation, which is probably necessary for other
> reasons anyhow.  So it's not clear how Section 3, paragraph 1 is
> relevant to this document.  It doesn't offer any guidance on how one
> might select an appropriate Ethernet address for those frames.
> Presumably these could be unicast, multicast or broadcast depending on
> routing requirements for the LSP, in which case maybe there is no good
> advice to give. If there really is no good advice to give, or there is
> no intent to provide advice for multicast/broadcast LSPs, a statement
> to that effect would be helpful.
>=20
> Section 3, Paragraph 2 just reiterates parts of Section 2, it could be =
removed.
>=20
> S5: I can't reconcile "The advertised information SHOULD be persistent
> across restarts."  with "Received advertisements MUST be discarded
> across restarts."
>=20
> S4, pp5: Why force a mapping to EUI-64?  Is canonicalization important
> for some reason?
>=20
> S4, pp5: The paragraph beginning with "In the event a GAP message is
> not received within the previously received associated Lifetime, ..."
> is a little confusing (and I'm familiar with G-ACh already).  This
> could be clearer.  Maybe:  "A node could cease transmission of G-ACh
> advertisements, or cease to include a Source MAC Address TLV in
> advertisements, either of which cause the TLV lifetime to elapse.
> After the Source MAC Address TLV lifetime has elapsed, this value
> SHOULD no longer be used to select a MAC address; the node SHOULD
> return to selecting MAC addresses as though no advertisements were
> received."
>=20
> S7.3: IETF review is a pretty high bar.  (Sadly, I missed this on
> G-ACh, or I would have made the same comment.)  Did you consider
> allowing IESG Approval as an alternative?
>=20
>=20
> Nits/editorial comments:
> There are a couple of lowercase instances of RFC2119 keywords that
> could be confusing.  The very last line of S4, the second last
> sentence of S2.  Consider alternative wordings for these statements.
>=20
> S2, pp3: s/i.e.  /i.e., /
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From shares@ndzh.com  Tue Apr 23 12:29:30 2013
Return-Path: <shares@ndzh.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB8A21F9660 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 12:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.765
X-Spam-Level: 
X-Spam-Status: No, score=0.765 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, DOS_OUTLOOK_TO_MX=1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 Zv1ENScLvAAN for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 12:29:29 -0700 (PDT)
Received: from hickoryhill-consulting.com (unknown [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 74D6B21F9609 for <gen-art@ietf.org>; Tue, 23 Apr 2013 12:29:29 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=66.129.246.4; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Jari Arkko'" <jari.arkko@piuha.net>, "'Elwyn Davies'" <elwynd@dial.pipex.com>, <Jon.Mitchell@microsoft.com>
References: <51707233.4080508@nostrum.com> <727796A1-3C68-47F2-9AE2-CE56D1B03EEF@piuha.net>
In-Reply-To: <727796A1-3C68-47F2-9AE2-CE56D1B03EEF@piuha.net>
Date: Tue, 23 Apr 2013 15:29:23 -0400
Message-ID: <004f01ce4058$dcde50e0$969af2a0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQKwV/m+14fvLJmGyYacgpGOcO63gAHk7VFYlxDaD1A=
X-Authenticated-User: skh@ndzh.com 
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] draft-ietf-idr-as-private-reservation gen-art review status
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 19:29:30 -0000

Jari and Elwyn:

I thought Jon had completed the changes to address Elwyn's comments.  
If not, he's will to get more comments. 

Doc-Shepherd/co-chair Sue,

Sue 

-----Original Message-----
From: Jari Arkko [mailto:jari.arkko@piuha.net] 
Sent: Tuesday, April 23, 2013 3:19 PM
To: Elwyn Davies; Jon.Mitchell@microsoft.com; Susan Hares
Cc: <gen-art@ietf.org> Team
Subject: draft-ietf-idr-as-private-reservation gen-art review status

Elwyn, Sue, Jon:

We are talking about this draft on Thursday evening at the IESG. I see that
there was a review and discussion earlier in the year. Thank you for the
reviews and responses! The Gen-ART reviews are very important for me, as
they enable me to spend time on a number of topics and not just the IESG
document reviews.

But I had a question. Do you all feel that everything raised in the
discussion has been properly addressed, and everyone is happy moving
forward?

Jari



From elwynd@dial.pipex.com  Tue Apr 23 12:54:57 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8072D21F8738 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 12:54:51 -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 THfHgJoFlUeO for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 12:54:35 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 2FB2521F8FAA for <gen-art@ietf.org>; Tue, 23 Apr 2013 12:54:27 -0700 (PDT)
Received: from [87.192.231.145] (helo=[10.1.0.187]) by b.painless.aa.net.uk with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1UUjIF-0005Vj-Pv; Tue, 23 Apr 2013 20:54:24 +0100
Date: Tue, 23 Apr 2013 20:54:23 +0100
Message-ID: <103vdbw51iyar5bmktcblq8b.1366746863437@email.android.com>
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Susan Hares <shares@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Cc: gen-art@ietf.org, 	 <Jon.Mitchell@microsoft.com>
Subject: Re: [Gen-art] draft-ietf-idr-as-private-reservation gen-art review status
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 19:54:57 -0000

aGkuCgpZZXMuICBKb24gYW5kIEkgZXhjaGFuZ2VkIGVtYWlsIGFuZCBoZSBjaGFuZ2VkIHRoZSBJ
QU5BIGluc3RydWN0aW9ucyAgdG8gYmUgbW9yZSBjb21tYW5kaW5nLiAKCldlIGFsc28gZGlzY3Vz
c2VkIHRoZSBmYWN0IHRoYXQgdGhlIHJlc2VydmF0aW9uIG9mIHRoZSB0b3AgQVMgbnVtYmVyIGlz
IG5vdCBhY3R1YWxseSBpbiBhbnkgUkZDIGFzIEkgdGhvdWdodCB0aGlzIG1pZ2h0IGhhdmUgYmVl
biBhIGdvb2QgcGxhY2UgdG8gZG8gaXQuICBBcHBhcmVudGx5IHRoZSBXRyB0aGlua3Mgb3RoZXJ3
aXNlIHNvIHdlIGxlZnQgdGhhdCBkb2cgc2xlZXBpbmcgcXVpZXRseS4KCk90aGVyd2lzZSBpdCBp
cyBmaW5lIGJ5IG1lLgoKUmVnYXJkcywKRWx3eW4KClNlbnQgZnJvbSBteSBBU1VTIFBhZAoKU3Vz
YW4gSGFyZXMgPHNoYXJlc0BuZHpoLmNvbT4gd3JvdGU6Cgo+SmFyaSBhbmQgRWx3eW46Cj4KPkkg
dGhvdWdodCBKb24gaGFkIGNvbXBsZXRlZCB0aGUgY2hhbmdlcyB0byBhZGRyZXNzIEVsd3luJ3Mg
Y29tbWVudHMuICAKPklmIG5vdCwgaGUncyB3aWxsIHRvIGdldCBtb3JlIGNvbW1lbnRzLiAKPgo+
RG9jLVNoZXBoZXJkL2NvLWNoYWlyIFN1ZSwKPgo+U3VlIAo+Cj4tLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQo+RnJvbTogSmFyaSBBcmtrbyBbbWFpbHRvOmphcmkuYXJra29AcGl1aGEubmV0XSAK
PlNlbnQ6IFR1ZXNkYXksIEFwcmlsIDIzLCAyMDEzIDM6MTkgUE0KPlRvOiBFbHd5biBEYXZpZXM7
IEpvbi5NaXRjaGVsbEBtaWNyb3NvZnQuY29tOyBTdXNhbiBIYXJlcwo+Q2M6IDxnZW4tYXJ0QGll
dGYub3JnPiBUZWFtCj5TdWJqZWN0OiBkcmFmdC1pZXRmLWlkci1hcy1wcml2YXRlLXJlc2VydmF0
aW9uIGdlbi1hcnQgcmV2aWV3IHN0YXR1cwo+Cj5FbHd5biwgU3VlLCBKb246Cj4KPldlIGFyZSB0
YWxraW5nIGFib3V0IHRoaXMgZHJhZnQgb24gVGh1cnNkYXkgZXZlbmluZyBhdCB0aGUgSUVTRy4g
SSBzZWUgdGhhdAo+dGhlcmUgd2FzIGEgcmV2aWV3IGFuZCBkaXNjdXNzaW9uIGVhcmxpZXIgaW4g
dGhlIHllYXIuIFRoYW5rIHlvdSBmb3IgdGhlCj5yZXZpZXdzIGFuZCByZXNwb25zZXMhIFRoZSBH
ZW4tQVJUIHJldmlld3MgYXJlIHZlcnkgaW1wb3J0YW50IGZvciBtZSwgYXMKPnRoZXkgZW5hYmxl
IG1lIHRvIHNwZW5kIHRpbWUgb24gYSBudW1iZXIgb2YgdG9waWNzIGFuZCBub3QganVzdCB0aGUg
SUVTRwo+ZG9jdW1lbnQgcmV2aWV3cy4KPgo+QnV0IEkgaGFkIGEgcXVlc3Rpb24uIERvIHlvdSBh
bGwgZmVlbCB0aGF0IGV2ZXJ5dGhpbmcgcmFpc2VkIGluIHRoZQo+ZGlzY3Vzc2lvbiBoYXMgYmVl
biBwcm9wZXJseSBhZGRyZXNzZWQsIGFuZCBldmVyeW9uZSBpcyBoYXBweSBtb3ZpbmcKPmZvcndh
cmQ/Cj4KPkphcmkKPgo+Cg==


From elwynd@dial.pipex.com  Tue Apr 23 13:07:07 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A99221F9473 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:07:07 -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 LJZd330A4BY4 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:07:06 -0700 (PDT)
Received: from mk-outboundfilter-5.mail.uk.tiscali.com (mk-outboundfilter-5.mail.uk.tiscali.com [212.74.114.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9243A21F93E1 for <gen-art@ietf.org>; Tue, 23 Apr 2013 13:07:06 -0700 (PDT)
X-Trace: 623431695/mk-outboundfilter-5.mail.uk.tiscali.com/PIPEX/$OFF_NET_AUTH_ACCEPTED/None/87.192.231.145/None/elwynd@dial.pipex.com
X-SBRS: None
X-RemoteIP: 87.192.231.145
X-IP-MAIL-FROM: elwynd@dial.pipex.com
X-SMTP-AUTH: elwynd@dial.pipex.com
X-MUA: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAFPpdlFXwOeR/2dsb2JhbAANRIM8vx6BG4NSQAEoBw0WGAMCAQIBSw0BBwEBiByrJIMyjzWPKINQA5cagSOEVjaNfQ
X-IronPort-AV: E=Sophos;i="4.87,537,1363132800"; d="scan'208";a="623431695"
X-IP-Direction: OUT
Received: from unknown (HELO [10.1.0.238]) ([87.192.231.145]) by smtp.pipex.tiscali.co.uk with ESMTP; 23 Apr 2013 21:06:43 +0100
Message-ID: <5176E9CB.7020908@dial.pipex.com>
Date: Tue, 23 Apr 2013 21:06:35 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-idr-as-private-reservation-04.all@tools.ietf.org
Subject: [Gen-art] Gen-art telechat review: draft-ietf-idr-as-private-reservation-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 20:07:07 -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-idr-as-private-reservation-04.txt
Reviewer: Elwyn Davies
Review Date: 23 April 2013
IETF LC End Date:
IESG Telechat date: 25 April 2013

Summary: Ready.  The draft now provides the smack of firm government for 
IANA as it should.  Thanks.


From Jon.Mitchell@microsoft.com  Tue Apr 23 13:11:46 2013
Return-Path: <Jon.Mitchell@microsoft.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B01D21F93B7 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:11:46 -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 MQgE08w1i-bF for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:11:45 -0700 (PDT)
Received: from na01-sn2-obe.outbound.o365filtering.com (na01-sn2-obe.ptr.o365filtering.com [157.55.158.29]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF5821F93AA for <gen-art@ietf.org>; Tue, 23 Apr 2013 13:11:45 -0700 (PDT)
Received: from BL2SR01CA101.namsdf01.sdf.exchangelabs.com (10.255.109.146) by BL2SR01MB605.namsdf01.sdf.exchangelabs.com (10.255.109.167) with Microsoft SMTP Server (TLS) id 15.0.687.4; Tue, 23 Apr 2013 20:11:43 +0000
Received: from SN2FFOFD002.ffo.gbl (157.55.158.30) by BL2SR01CA101.outlook.office365.com (10.255.109.146) with Microsoft SMTP Server (TLS) id 15.0.692.0 via Frontend Transport; Tue, 23 Apr 2013 20:11:43 +0000
Received: from hybrid.exchange.microsoft.com (131.107.1.17) by SN2FFOFD002.mail.o365filtering.com (10.111.201.21) with Microsoft SMTP Server (TLS) id 15.0.687.1 via Frontend Transport; Tue, 23 Apr 2013 20:11:43 +0000
Received: from df-h14-01.exchange.corp.microsoft.com (157.54.78.139) by DF-G14-01.exchange.corp.microsoft.com (157.54.87.87) with Microsoft SMTP Server (TLS) id 14.3.123.1; Tue, 23 Apr 2013 20:11:19 +0000
Received: from DFM-DB3MBX15-07.exchange.corp.microsoft.com (10.166.18.225) by DF-H14-01.exchange.corp.microsoft.com (157.54.78.139) with Microsoft SMTP Server (TLS) id 14.3.123.1; Tue, 23 Apr 2013 13:11:19 -0700
Received: from DFM-DB3MBX15-08.exchange.corp.microsoft.com (10.166.18.226) by DFM-DB3MBX15-07.exchange.corp.microsoft.com (10.166.18.225) with Microsoft SMTP Server (TLS) id 15.0.620.25; Tue, 23 Apr 2013 13:11:17 -0700
Received: from DFM-DB3MBX15-08.exchange.corp.microsoft.com ([169.254.12.113]) by DFM-DB3MBX15-08.exchange.corp.microsoft.com ([169.254.12.113]) with mapi id 15.00.0620.020; Tue, 23 Apr 2013 13:11:16 -0700
From: "Jon Mitchell (GNS)" <Jon.Mitchell@microsoft.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
Thread-Topic: draft-ietf-idr-as-private-reservation gen-art review status
Thread-Index: AQHOQFxZ1wOteIWZ1UK5aZnw7nzZRpjkPLNE
Date: Tue, 23 Apr 2013 20:11:16 +0000
Message-ID: <8ABB8DFE-3352-4B08-B789-34FA14E2E89D@microsoft.com>
References: <103vdbw51iyar5bmktcblq8b.1366746863437@email.android.com>
In-Reply-To: <103vdbw51iyar5bmktcblq8b.1366746863437@email.android.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.1.17; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(13464002)(24454001)(377454001)(199002)(189002)(51704004)(23726002)(4396001)(81542001)(44976003)(46102001)(54316002)(56776001)(56816002)(76482001)(47976001)(49866001)(47736001)(51856001)(81342001)(50986001)(50466001)(36756002)(47446002)(74502001)(69226001)(80022001)(65816001)(6806003)(33656001)(79102001)(63696002)(74662001)(46406003)(53806001)(77982001)(59766001)(31966008)(16406001)(20776003)(47776003)(54356001)(22906002); DIR:OUT; SFP:; SCL:1; SRVR:BL2SR01MB605; H:hybrid.exchange.microsoft.com; RD:mail1.exchange.microsoft.com; A:1; MX:1; LANG:en; 
X-Forefront-PRVS: 08252193F3
X-OriginatorOrg: DuplicateDomain-b1291ffc-369c-4c2a-9225-e2908f70a426.microsoft.com
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "Jon Mitchell \(GNS\)" <Jon.Mitchell@microsoft.com>, Susan Hares <shares@ndzh.com>
Subject: Re: [Gen-art] draft-ietf-idr-as-private-reservation gen-art review status
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 20:11:46 -0000

Elwyn -

Yes, to be clear I will be introducing another draft shortly (in IDR) to co=
ver the top number of both ranges, this is the path WG chairs and AD ok'd..=
.

Cheers,

Jon

On Apr 23, 2013, at 9:55 PM, "Elwyn Davies" <elwynd@dial.pipex.com> wrote:

> hi.
>=20
> Yes.  Jon and I exchanged email and he changed the IANA instructions  to =
be more commanding.=20
>=20
> We also discussed the fact that the reservation of the top AS number is n=
ot actually in any RFC as I thought this might have been a good place to do=
 it.  Apparently the WG thinks otherwise so we left that dog sleeping quiet=
ly.
>=20
> Otherwise it is fine by me.
>=20
> Regards,
> Elwyn
>=20
> Sent from my ASUS Pad
>=20
> Susan Hares <shares@ndzh.com> wrote:
>=20
>> Jari and Elwyn:
>>=20
>> I thought Jon had completed the changes to address Elwyn's comments. =20
>> If not, he's will to get more comments.=20
>>=20
>> Doc-Shepherd/co-chair Sue,
>>=20
>> Sue=20
>>=20
>> -----Original Message-----
>> From: Jari Arkko [mailto:jari.arkko@piuha.net]=20
>> Sent: Tuesday, April 23, 2013 3:19 PM
>> To: Elwyn Davies; Jon.Mitchell@microsoft.com; Susan Hares
>> Cc: <gen-art@ietf.org> Team
>> Subject: draft-ietf-idr-as-private-reservation gen-art review status
>>=20
>> Elwyn, Sue, Jon:
>>=20
>> We are talking about this draft on Thursday evening at the IESG. I see t=
hat
>> there was a review and discussion earlier in the year. Thank you for the
>> reviews and responses! The Gen-ART reviews are very important for me, as
>> they enable me to spend time on a number of topics and not just the IESG
>> document reviews.
>>=20
>> But I had a question. Do you all feel that everything raised in the
>> discussion has been properly addressed, and everyone is happy moving
>> forward?
>>=20
>> Jari
>>=20
>>=20

From elwynd@dial.pipex.com  Tue Apr 23 13:13:01 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E567521F93BA for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:13:00 -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 JmmyPWKoDvBM for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:13:00 -0700 (PDT)
Received: from mk-outboundfilter-6.mail.uk.tiscali.com (mk-outboundfilter-6.mail.uk.tiscali.com [212.74.114.14]) by ietfa.amsl.com (Postfix) with ESMTP id 9B00C21F93AA for <gen-art@ietf.org>; Tue, 23 Apr 2013 13:12:59 -0700 (PDT)
X-Trace: 564765862/mk-outboundfilter-6.mail.uk.tiscali.com/PIPEX/$OFF_NET_AUTH_ACCEPTED/None/87.192.231.145/None/elwynd@dial.pipex.com
X-SBRS: None
X-RemoteIP: 87.192.231.145
X-IP-MAIL-FROM: elwynd@dial.pipex.com
X-SMTP-AUTH: elwynd@dial.pipex.com
X-MUA: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAM/qdlFXwOeR/2dsb2JhbAANRIM8vk2BG4NSQAEoBw0WGAMCAQIBSw0BBwEBiByrJ4MyjzSPKINQA5cagSOEVjaDYIod
X-IronPort-AV: E=Sophos;i="4.87,537,1363132800"; d="scan'208";a="564765862"
X-IP-Direction: OUT
Received: from unknown (HELO [10.1.0.238]) ([87.192.231.145]) by smtp.pipex.tiscali.co.uk with ESMTP; 23 Apr 2013 21:12:53 +0100
Message-ID: <5176EB42.3030501@dial.pipex.com>
Date: Tue, 23 Apr 2013 21:12:50 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: fluffy@cisco.com, adam@nostrum.com, Mary Barnes <mary.h.barnes@gmail.com>, mary.barnes@nortel.com, draft-saintandre-impp-call-info.all@tools.ietf.org
Subject: [Gen-art] Gen-art LC review of draft-saintandre-impp-call-info-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 20:13:01 -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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-saintandre-impp-call-info-02.txt
Reviewer: Elwyn Davies
Review Date: 23 April 2013
IETF LC End Date: 14 May 2013
IESG Telechat date: (if known) -

Summary: Ready.  See the generic issue with the IANA registry mentioned 
below.

Major issues: None

Minor issues: None

Nits/editorial comments:
Generic comment about SIP Header Field Parameters registry: For the 
uninitiated this registry is rather opaque.  Some parameters, such as 
the Call-Info purpose parameter for which an extra value is defined 
here, have predefined values.  However the predefined values themselves 
are not in the registry and just giving a whole RFC reference for places 
where values are defined is not very helpful. For example, in the case 
of Call-Info, the initial predefined values of purpose are buried in the 
Call-Info rule in the ABNF in Section 25.1 of RFC 3261;  also, Section 
20.9 describes the predefined values (such as "icon") as 'parameters' 
rather than values of 'purpose'.  It would probably be helpful to either 
improve the references in the registry table or actaully quote the 
possible predefined values in the table.


From jari.arkko@piuha.net  Tue Apr 23 13:16:37 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7227D21F9421 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, 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 ykzIlr4vROJ9 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:16:37 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 8F41D21F9412 for <gen-art@ietf.org>; Tue, 23 Apr 2013 13:16:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DB2522CC55; Tue, 23 Apr 2013 23:16:35 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dhK1M1_l0yb2; Tue, 23 Apr 2013 23:16:35 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 1F9922CC56; Tue, 23 Apr 2013 23:16:35 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8ABB8DFE-3352-4B08-B789-34FA14E2E89D@microsoft.com>
Date: Tue, 23 Apr 2013 23:16:35 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C353C8C-41F3-4677-AF52-CEE50C593583@piuha.net>
References: <103vdbw51iyar5bmktcblq8b.1366746863437@email.android.com> <8ABB8DFE-3352-4B08-B789-34FA14E2E89D@microsoft.com>
To: "Jon Mitchell (GNS)" <Jon.Mitchell@microsoft.com>
X-Mailer: Apple Mail (2.1503)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, Susan Hares <shares@ndzh.com>
Subject: Re: [Gen-art] draft-ietf-idr-as-private-reservation gen-art review status
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 20:16:37 -0000

Thanks, all.

Jari

On Apr 23, 2013, at 11:11 PM, "Jon Mitchell (GNS)" =
<Jon.Mitchell@microsoft.com> wrote:

> Elwyn -
>=20
> Yes, to be clear I will be introducing another draft shortly (in IDR) =
to cover the top number of both ranges, this is the path WG chairs and =
AD ok'd...
>=20
> Cheers,
>=20
> Jon
>=20
> On Apr 23, 2013, at 9:55 PM, "Elwyn Davies" <elwynd@dial.pipex.com> =
wrote:
>=20
>> hi.
>>=20
>> Yes.  Jon and I exchanged email and he changed the IANA instructions  =
to be more commanding.=20
>>=20
>> We also discussed the fact that the reservation of the top AS number =
is not actually in any RFC as I thought this might have been a good =
place to do it.  Apparently the WG thinks otherwise so we left that dog =
sleeping quietly.
>>=20
>> Otherwise it is fine by me.
>>=20
>> Regards,
>> Elwyn
>>=20
>> Sent from my ASUS Pad
>>=20
>> Susan Hares <shares@ndzh.com> wrote:
>>=20
>>> Jari and Elwyn:
>>>=20
>>> I thought Jon had completed the changes to address Elwyn's comments. =
=20
>>> If not, he's will to get more comments.=20
>>>=20
>>> Doc-Shepherd/co-chair Sue,
>>>=20
>>> Sue=20
>>>=20
>>> -----Original Message-----
>>> From: Jari Arkko [mailto:jari.arkko@piuha.net]=20
>>> Sent: Tuesday, April 23, 2013 3:19 PM
>>> To: Elwyn Davies; Jon.Mitchell@microsoft.com; Susan Hares
>>> Cc: <gen-art@ietf.org> Team
>>> Subject: draft-ietf-idr-as-private-reservation gen-art review status
>>>=20
>>> Elwyn, Sue, Jon:
>>>=20
>>> We are talking about this draft on Thursday evening at the IESG. I =
see that
>>> there was a review and discussion earlier in the year. Thank you for =
the
>>> reviews and responses! The Gen-ART reviews are very important for =
me, as
>>> they enable me to spend time on a number of topics and not just the =
IESG
>>> document reviews.
>>>=20
>>> But I had a question. Do you all feel that everything raised in the
>>> discussion has been properly addressed, and everyone is happy moving
>>> forward?
>>>=20
>>> Jari
>>>=20
>>>=20


From elwynd@dial.pipex.com  Tue Apr 23 13:19:41 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E12A21F9588 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:19:41 -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 Te4UhIHQwwr8 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:19:40 -0700 (PDT)
Received: from mk-outboundfilter-1.mail.uk.tiscali.com (mk-outboundfilter-1.mail.uk.tiscali.com [212.74.114.37]) by ietfa.amsl.com (Postfix) with ESMTP id 61E2A21F93F3 for <gen-art@ietf.org>; Tue, 23 Apr 2013 13:19:40 -0700 (PDT)
X-Trace: 719432651/mk-outboundfilter-1.mail.uk.tiscali.com/PIPEX/$OFF_NET_AUTH_ACCEPTED/None/87.192.231.145/None/elwynd@dial.pipex.com
X-SBRS: None
X-RemoteIP: 87.192.231.145
X-IP-MAIL-FROM: elwynd@dial.pipex.com
X-SMTP-AUTH: elwynd@dial.pipex.com
X-MUA: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAB3sdlFXwOeR/2dsb2JhbAANRMIJgRuDEwEBAQQ4QAEMBAsNBAQBAQEJFggHCQMCAQIBNAkIBg0BBQIBAbNDgzKPNI1mgUIHBoNDA5cahXk2jX2Bcg
X-IronPort-AV: E=Sophos;i="4.87,537,1363132800"; d="scan'208";a="719432651"
X-IP-Direction: OUT
Received: from unknown (HELO [10.1.0.238]) ([87.192.231.145]) by smtp.pipex.tiscali.co.uk with ESMTP; 23 Apr 2013 21:18:40 +0100
Message-ID: <5176EC79.1070809@dial.pipex.com>
Date: Tue, 23 Apr 2013 21:18:01 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: "Jon Mitchell (GNS)" <Jon.Mitchell@microsoft.com>
References: <103vdbw51iyar5bmktcblq8b.1366746863437@email.android.com> <8ABB8DFE-3352-4B08-B789-34FA14E2E89D@microsoft.com>
In-Reply-To: <8ABB8DFE-3352-4B08-B789-34FA14E2E89D@microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, Susan Hares <shares@ndzh.com>
Subject: Re: [Gen-art] draft-ietf-idr-as-private-reservation gen-art review status
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 20:19:41 -0000

Fine.  Thanks.

/E
On 23/04/13 21:11, Jon Mitchell (GNS) wrote:
> Elwyn -
>
> Yes, to be clear I will be introducing another draft shortly (in IDR) to cover the top number of both ranges, this is the path WG chairs and AD ok'd...
>
> Cheers,
>
> Jon
>
> On Apr 23, 2013, at 9:55 PM, "Elwyn Davies" <elwynd@dial.pipex.com> wrote:
>
>> hi.
>>
>> Yes.  Jon and I exchanged email and he changed the IANA instructions  to be more commanding.
>>
>> We also discussed the fact that the reservation of the top AS number is not actually in any RFC as I thought this might have been a good place to do it.  Apparently the WG thinks otherwise so we left that dog sleeping quietly.
>>
>> Otherwise it is fine by me.
>>
>> Regards,
>> Elwyn
>>
>> Sent from my ASUS Pad
>>
>> Susan Hares <shares@ndzh.com> wrote:
>>
>>> Jari and Elwyn:
>>>
>>> I thought Jon had completed the changes to address Elwyn's comments.
>>> If not, he's will to get more comments.
>>>
>>> Doc-Shepherd/co-chair Sue,
>>>
>>> Sue
>>>
>>> -----Original Message-----
>>> From: Jari Arkko [mailto:jari.arkko@piuha.net]
>>> Sent: Tuesday, April 23, 2013 3:19 PM
>>> To: Elwyn Davies; Jon.Mitchell@microsoft.com; Susan Hares
>>> Cc: <gen-art@ietf.org> Team
>>> Subject: draft-ietf-idr-as-private-reservation gen-art review status
>>>
>>> Elwyn, Sue, Jon:
>>>
>>> We are talking about this draft on Thursday evening at the IESG. I see that
>>> there was a review and discussion earlier in the year. Thank you for the
>>> reviews and responses! The Gen-ART reviews are very important for me, as
>>> they enable me to spend time on a number of topics and not just the IESG
>>> document reviews.
>>>
>>> But I had a question. Do you all feel that everything raised in the
>>> discussion has been properly addressed, and everyone is happy moving
>>> forward?
>>>
>>> Jari
>>>
>>>


From jari.arkko@piuha.net  Tue Apr 23 13:33:02 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 648D721F969A for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:33:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, 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 yNiEEG6dF3uR for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 13:33:01 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 506DB21F9696 for <gen-art@ietf.org>; Tue, 23 Apr 2013 13:33:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9C3632CC56; Tue, 23 Apr 2013 23:33:00 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xj1Q5JqFf7Br; Tue, 23 Apr 2013 23:32:59 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 9A1E42CC55; Tue, 23 Apr 2013 23:32:59 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <AA7BC87B-4FB2-406E-80D5-72F0A8FA036E@tzi.org>
Date: Tue, 23 Apr 2013 23:32:59 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <2126E8E4-A8E8-4C49-BF19-3883C888497C@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA0B8EE3@AZ-FFEXMB04.global.avaya.com> <AA7BC87B-4FB2-406E-80D5-72F0A8FA036E@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.1503)
Cc: "draft-ietf-core-coap@tools.ietf.org" <draft-ietf-core-coap@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, Barry Leiba <barryleiba@computer.org>, "core-chairs@tools.ietf.org" <core-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review for draft-ietf-core-coap-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 20:33:02 -0000

Dan:

Many thanks for your review. This is a big document and I believe =
important, and your observations on it are very valuable.

Carsten:

I've seen two responses (both from you and on March 28) to Dan's review. =
If I've understood correctly, you've responded to major issue 1 and =
minor issues 2-5, but what about major issues 2-3 and minor issue 1? =
(I'm searching for e-mails with the draft file name in subject line, so =
it is possible that I've missed issue tracker mails, for instance.)

For your convenience, here are the issues that I did not see a response =
to yet:

> 2 . The WG charter says:=20
>=20
>> 7) Consider operational and manageability aspects of the protocol and =
at
>> a minimum provide a way to tell if a Device is powered on or not.
>=20
>=20
> There is no mention in the protocol document (or other documents in =
core) about manageability and operational considerations. Maybe some =
work is being prepared, although I saw no core documents dealing with =
it. I believe that it would be good for the document to include either =
an Operational and Manageability Considerations section as recommended =
by RFC 5706 or, a short informational 'Future Work' section or appendix =
that mentions the need to deal with the operational and manageability =
aspects, and possibly point to work already done in the IETF for example =
on the coman mail list concerning management of constrained networks.
>=20
> 3. Section 4.8 defines a number of CoAP protocol parameters and =
derived parameters that according to 4.8.1 may be changed. Some of these =
parameters have limitations and their changes may affect the basic =
functionality of the nodes, the interaction between nodes or between =
nodes and servers, as well as the functioning in constrained =
environments. However there is no risk analysis in Section 11 (Security =
Considerations) about the threats related to mis-configuration of the =
modes and un-appropriate or malevolent changes in these parameters, and =
recommendations of security counter-measures on this respect.=20
>=20
> Minor issues:
>=20
> 1. The WG charter says:=20
>=20
>> The WG will coordinate on requirements from many organizations =
including
>> OpenSG/NIST, ZigBee/HomePlug, IPSO Alliance, OASIS, SENSEI,
>> ASHRAE/BACnet; other SDOs and organizations.
>=20
> I am wondering whether the listed organizations were informed about =
the IETF conducting the Last Call on the protocol document. Maybe I =
missed some messages, but I see no feedback in the archives of the WG or =
IETF lists, or in the liaison statements page reflecting such =
interaction.=20

From jari.arkko@piuha.net  Tue Apr 23 14:56:33 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A848721F8ED3 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 14:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, 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 7RZV4T4oX20A for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 14:56:28 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 49E8F21F8E7E for <gen-art@ietf.org>; Tue, 23 Apr 2013 14:56:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id B0D652CC56; Wed, 24 Apr 2013 00:56:20 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPUj7ImutIob; Wed, 24 Apr 2013 00:56:19 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 558D52CC55; Wed, 24 Apr 2013 00:56:19 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A0B644B@eusaamb107.ericsson.se>
Date: Wed, 24 Apr 2013 00:56:19 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <47BD9092-5123-465E-B6A5-6D06E341568B@piuha.net>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A0B644B@eusaamb107.ericsson.se>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
X-Mailer: Apple Mail (2.1503)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dnsext-dnssec-algo-signal.all@tools.ietf.org" <draft-ietf-dnsext-dnssec-algo-signal.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-dnsext-dnssec-algo-signal-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 21:56:33 -0000

Thanks for your review, Meral! I see that the -10 has taken your =
suggestions into account.

Jari

On Apr 4, 2013, at 5:54 AM, Meral Shirazipour =
<meral.shirazipour@ericsson.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq .
> =20
> Please resolve these comments along with any other Last Call comments =
you may receive.
> =20
> Document: draft-ietf-dnsext-dnssec-algo-signal-09
> Reviewer: Meral Shirazipour
> Review Date: 2013-04-03
> IETF LC End Date: 2013-04-03
> IESG Telechat date: N/A
> =20
> Summary:
> This draft is almost ready to be published as Standard RFC but I do =
have some editorial comments.
> =20
> Nits/editorial comments:
> - Reading the abstract does not tell why these options are necessary. =
The 4th paragraph in Intro mentions the purpose of these options as well =
as Section 8.
> Please consider adding a similar sentence as Section 8 to the =
abstract:
> "The proposed extensions allow the signaling of new algorithm uptake =
in client code to allow zone administrators to know when it is possible =
to complete an algorithm rollover in a DNSSEC signed zone."
> =20
> -[Page 4], last sentence: "in a potential future example". Suggestion: =
"in potential future examples".
> =20
> -[Page 7], Section 9, [I-D.ietf-dnsext-rfc2671bis-edns0], latest =
version is 10.
> =20
> Best Regards,
> Meral
> =20
> ---
> Meral Shirazipour
> Ericsson
> Research
> www.ericsson.com
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From suresh.krishnan@ericsson.com  Tue Apr 23 15:05:09 2013
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E24621F94A9 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 15:05:09 -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 aT2fgE50hQ+H for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 15:05:08 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id DC6EC21F9497 for <gen-art@ietf.org>; Tue, 23 Apr 2013 15:05:07 -0700 (PDT)
X-AuditID: c6180641-b7faf6d00000096b-3b-517705924007
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id E8.AF.02411.29507715; Wed, 24 Apr 2013 00:05:07 +0200 (CEST)
Received: from eusaamw0711.eamcs.ericsson.se (147.117.20.178) by EUSAAHC007.ericsson.se (147.117.188.93) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 23 Apr 2013 18:05:06 -0400
Received: from [142.133.112.81] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.279.1; Tue, 23 Apr 2013 18:05:05 -0400
Message-ID: <517704FD.4020005@ericsson.com>
Date: Tue, 23 Apr 2013 18:02:37 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: <draft-ietf-manet-olsrv2-metrics-rationale.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNJMWRmVeSWpSXmKPExsUyuXRPrO5k1vJAg+Z5EhYnfi5htLj66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJVx9tc05oLdohW3Hm9gbmCcItjFyMkhIWAi cXX1MmYIW0ziwr31bF2MXBxCAkcZJR40/mGEcPYwSmw+3MsK4WxjlGj+PJ8JpIVXQFvi17dv YDaLgKrE7QNzwWw2oLEbdn4Gs0UFwiRWrYdYwSsgKHFy5hMWEFtEoFji6cWDYHFhgVCJl223 oc6QlNjyop0dxGYW0JOYcrWFEcKWl9j+dg5YjZCApsTWNd9ZJzAKzEIydhaSlllIWhYwMq9i 5CgtTi3LTTcy3MQIDMBjEmyOOxgXfLI8xCjNwaIkzhvqeiFASCA9sSQ1OzW1ILUovqg0J7X4 ECMTB6dUA6OzOeftbyufuR9TSpeLmJWh41K3aZZBseri23bb7UyzLx7ffWd5dHGNpdq2da2T eli3axU31/GdCanYdobrjGuKQvFFD4XDAvPSbRtFJdmFg3iShAs7PK4tmFii5HZjb/0GHd6n W+qO/kuKXzlX+9ukp/NVN6zzfP17hWn9ufQg/iuikkXxFkosxRmJhlrMRcWJAD9Xs6IOAgAA
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-manet-olsrv2-metrics-rationale-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 22:05:09 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:  draft-ietf-manet-olsrv2-metrics-rationale-03.txt
Reviewer: Suresh Krishnan
Review Date: 2013/04/23
IESG Telechat date: 2013/04/25

Summary: This document is almost ready for publication as an
Informational RFC but I do have some comments you may wish to address.

Major
=====

* Section 5.6 Link Metrics

I had a hard time understanding this section as a whole and specifically
the metric calculation. Intuitively, it was clear to me that you cannot
squeeze 2^24 values into 12 bits :-). So the question immediately became
what values get left out.

If I understand correctly for a given value of b, each increment of a
increases the metric value by 2^b. If my understanding is correct (my
apologies if it is not), please consider modifying the text to clarify
the following

-> The compressed metric is lossy and is not capable of representing
*all* metric values in the range 2^24-2^m. The larger the value of b
more the values that cannot be represented.
-> Two metric values that are different can result in the same
compressed metric and hence cannot be really compared for equality as
described in the section. e.g. metric value 821 and 822 would be mapped
into the same compressed metric and a comparison will conclude that they
are equal.
-> Describe a short algorithm for converting a metric value into a
compressed metric. i.e. Given a metric value x, how to obtain a and b
from it. e.g.

b=log2(x+256)-9

* To achieve interoperability and to avoid loops, the values of e and m
need to be the same across the network. The following sentence seems to
allow for other values of e and m ("An appropriate pair..."). Suggest

OLD:
The required 24 bit limit can be achieved if 2^e+m = 24. An appropriate
pair of values to achieve this is e = 4, m = 8.

NEW:
The required 24 bit limit can be achieved if 2^e+m = 24. Since e+m=12,
solving for e and m will lead to e = 4, m = 8.

Minor
=====

* It is unclear to me how the metrics can be configured to handle the
privileged relay aerial router case described in Section 4. Assume there
is a cost metric on the link to/from the aerial router, would this be
set to low or high (I would assume high)? If the metric is set high, the
ground routers may route through several low quality links which seem to
have a lower path metric but may end up underusing the aerial link. Are
there any guidelines in this regard?

Thanks
Suresh


From stbryant@cisco.com  Tue Apr 23 15:14:52 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9868121F8A48; Tue, 23 Apr 2013 15:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.444
X-Spam-Level: 
X-Spam-Status: No, score=-110.444 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 z329hdo5e+Y6; Tue, 23 Apr 2013 15:14:51 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 545C221F9029; Tue, 23 Apr 2013 15:14:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3959; q=dns/txt; s=iport; t=1366755291; x=1367964891; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=j4TRMRkeTceSoIUOtVY3NASL9nc3RLQ/kJvIRbVtdPI=; b=fAlzep0TcG/fdZKNkhvzlQaYdq4MNHtBUAPzqeUC9hvMFTdElqmtN7OB pKCRY37qKpmUitCdqxSKsjXdxorzQUoOEIQWRLER3JPOc9iywh9kHeQ8I E9kx5T7XvIKpCncaF11SqfZ8NZGRadeMGRX4Nlg5pwuyuJw+1/xmaRu7Y s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAJQHd1GQ/khM/2dsb2JhbABQgwY2gzG7IIEFFnSCHwEBAQQjFUABEAsUBAICBRYLAgIJAwIBAgFFBgEMAQcBAYgQDKt1gkCPJoEjjWMdBQeCNoETA5NLg0+BI496gw8
X-IronPort-AV: E=Sophos;i="4.87,537,1363132800"; d="scan'208";a="153193011"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 23 Apr 2013 22:14:35 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r3NMEXRp013751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Apr 2013 22:14:34 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r3NMEWU3024628; Tue, 23 Apr 2013 23:14:33 +0100 (BST)
Message-ID: <517707C8.8090702@cisco.com>
Date: Tue, 23 Apr 2013 23:14:32 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>, "iesg@ietf.org" <iesg@ietf.org>
References: <CABkgnnVynoYEZCH7PSF89L_RzXCCoEupEApTBQRL1aEbDP1ONQ@mail.gmail.com>
In-Reply-To: <CABkgnnVynoYEZCH7PSF89L_RzXCCoEupEApTBQRL1aEbDP1ONQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-tp-ethernet-addressing.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 22:14:53 -0000

Martin

Thank you for your comments. I will review them after the
telechat and address them along with any additional comments
received from the IESG.

Regards

Stewart

On 20/04/2013 00:38, Martin Thomson wrote:
> 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 (post) Last Call comments
> you may receive.
>
> Document: draft-ietf-mpls-tp-ethernet-addressing-07
> Reviewer: Martin Thomson
> Review Date: 2013-04-19
> IETF LC End Date: 2013-02-18 (!)
> IESG Telechat date: 2013-04-25
>
> Summary: This document is almost ready for publication as proposed
> standard.  There are some minor issues
>
> Major issues: None
>
> Minor issues:
>
> The structure of the document is odd.  The individual pieces of
> explanation are good, it's just that different bits are revealed in a
> strange order.  If the intent is to describe a method of selecting an
> Ethernet address to attach to MPLS-TP packets, I would have thought
> that structuring the document to correspond to the prioritization of
> methods would make sense.  That is, from what I can infer:
> If unicast, use a unicast address (MUST for multipoint attachment,
> SHOULD for others)
>    1. from G-ACh, if available
>    2. from static configuration, if operationally feasible
> otherwise, for point-to-point links you can use
>    3. the IANA-assigned special address
>    4. FF-FF-FF-FF-FF-FF
> Reordering might help with understanding the process.
>
> If multicast/broadcast LSPs, there doesn't seem to be any actual
> recommendations or advice in the document.  There is only an
> admonition to use encapsulation, which is probably necessary for other
> reasons anyhow.  So it's not clear how Section 3, paragraph 1 is
> relevant to this document.  It doesn't offer any guidance on how one
> might select an appropriate Ethernet address for those frames.
> Presumably these could be unicast, multicast or broadcast depending on
> routing requirements for the LSP, in which case maybe there is no good
> advice to give. If there really is no good advice to give, or there is
> no intent to provide advice for multicast/broadcast LSPs, a statement
> to that effect would be helpful.
>
> Section 3, Paragraph 2 just reiterates parts of Section 2, it could be removed.
>
> S5: I can't reconcile "The advertised information SHOULD be persistent
> across restarts."  with "Received advertisements MUST be discarded
> across restarts."
>
> S4, pp5: Why force a mapping to EUI-64?  Is canonicalization important
> for some reason?
>
> S4, pp5: The paragraph beginning with "In the event a GAP message is
> not received within the previously received associated Lifetime, ..."
> is a little confusing (and I'm familiar with G-ACh already).  This
> could be clearer.  Maybe:  "A node could cease transmission of G-ACh
> advertisements, or cease to include a Source MAC Address TLV in
> advertisements, either of which cause the TLV lifetime to elapse.
> After the Source MAC Address TLV lifetime has elapsed, this value
> SHOULD no longer be used to select a MAC address; the node SHOULD
> return to selecting MAC addresses as though no advertisements were
> received."
>
> S7.3: IETF review is a pretty high bar.  (Sadly, I missed this on
> G-ACh, or I would have made the same comment.)  Did you consider
> allowing IESG Approval as an alternative?
>
>
> Nits/editorial comments:
> There are a couple of lowercase instances of RFC2119 keywords that
> could be confusing.  The very last line of S4, the second last
> sentence of S2.  Consider alternative wordings for these statements.
>
> S2, pp3: s/i.e.  /i.e., /
> .
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From cabo@tzi.org  Tue Apr 23 15:41:37 2013
Return-Path: <cabo@tzi.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B41221F93F1 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 15:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.047
X-Spam-Level: 
X-Spam-Status: No, score=-107.047 tagged_above=-999 required=5 tests=[AWL=-0.798, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, 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 xw1L88r4iH1U for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 15:41:36 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 8E0BB21F93F0 for <gen-art@ietf.org>; Tue, 23 Apr 2013 15:41:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r3NMfPsb014380; Wed, 24 Apr 2013 00:41:25 +0200 (CEST)
Received: from [192.168.217.105] (p54891E67.dip0.t-ipconnect.de [84.137.30.103]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 9DADD3A89; Wed, 24 Apr 2013 00:41:24 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=windows-1252
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <2126E8E4-A8E8-4C49-BF19-3883C888497C@piuha.net>
Date: Wed, 24 Apr 2013 00:41:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <52241DAA-FB72-4CE0-9C17-FB5032292CBE@tzi.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA0B8EE3@AZ-FFEXMB04.global.avaya.com> <AA7BC87B-4FB2-406E-80D5-72F0A8FA036E@tzi.org> <2126E8E4-A8E8-4C49-BF19-3883C888497C@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1503)
Cc: draft-ietf-core-coap@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Barry Leiba <barryleiba@computer.org>, core-chairs@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review for draft-ietf-core-coap-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 22:41:37 -0000

Jari,

indeed, it seems we never replied to these two items.

>> 2 . The WG charter says:=20
>>=20
>>> 7) Consider operational and manageability aspects of the protocol =
and at
>>> a minimum provide a way to tell if a Device is powered on or not.
>>=20
>>=20
>> There is no mention in the protocol document (or other documents in =
core) about manageability and operational considerations. Maybe some =
work is being prepared, although I saw no core documents dealing with =
it. I believe that it would be good for the document to include either =
an Operational and Manageability Considerations section as recommended =
by RFC 5706 or, a short informational 'Future Work' section or appendix =
that mentions the need to deal with the operational and manageability =
aspects, and possibly point to work already done in the IETF for example =
on the coman mail list concerning management of constrained networks.
>>=20
>> 3. Section 4.8 defines a number of CoAP protocol parameters and =
derived parameters that according to 4.8.1 may be changed. Some of these =
parameters have limitations and their changes may affect the basic =
functionality of the nodes, the interaction between nodes or between =
nodes and servers, as well as the functioning in constrained =
environments. However there is no risk analysis in Section 11 (Security =
Considerations) about the threats related to mis-configuration of the =
modes and un-appropriate or malevolent changes in these parameters, and =
recommendations of security counter-measures on this respect.=20

There is some discussion of this in the March 11 reply to the ops-dir =
review.

It seems this message is not publicly archived.
I'll dig it out and send it separately.

Re the security considerations:
As of today, we don't have mechanisms to effect any of these parameter =
changes.
I believe any such mechanisms developed in the future will have to =
address the pertinent security considerations.

>> Minor issues:
>>=20
>> 1. The WG charter says:=20
>>=20
>>> The WG will coordinate on requirements from many organizations =
including
>>> OpenSG/NIST, ZigBee/HomePlug, IPSO Alliance, OASIS, SENSEI,
>>> ASHRAE/BACnet; other SDOs and organizations.
>>=20
>> I am wondering whether the listed organizations were informed about =
the IETF conducting the Last Call on the protocol document. Maybe I =
missed some messages, but I see no feedback in the archives of the WG or =
IETF lists, or in the liaison statements page reflecting such =
interaction.=20

The coordination on requirements was mostly done in 2010, and I'm not =
aware of any formal liaisons we picked up from that.
Since then, we have had many people that were both in CoRE and in one or =
more the organizations listed (which now probably need to be =
complemented with OMA, ETSI and oneM2M, ...).
ETSI even ran a couple of CoAP interops...
I must admit that it simply didn't occur to me that we should do =
additional publicity for the IETF last call there =97 I was quite happy =
with the level of visibility that we have right now.

Gr=FC=DFe, Carsten


From cabo@tzi.org  Tue Apr 23 15:42:54 2013
Return-Path: <cabo@tzi.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD0D21F9421 for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 15:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.986
X-Spam-Level: 
X-Spam-Status: No, score=-106.986 tagged_above=-999 required=5 tests=[AWL=-0.737, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, 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 MkS9iAUZ6WWl for <gen-art@ietfa.amsl.com>; Tue, 23 Apr 2013 15:42:53 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 8FCEA21F93F9 for <gen-art@ietf.org>; Tue, 23 Apr 2013 15:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r3NMgbEE016245; Wed, 24 Apr 2013 00:42:37 +0200 (CEST)
Received: from [192.168.217.105] (p54891E67.dip0.t-ipconnect.de [84.137.30.103]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 08B813A8A; Wed, 24 Apr 2013 00:42:36 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Carsten Bormann <cabo@tzi.org>
Date: Wed, 24 Apr 2013 00:42:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F298826C-2F04-420D-AC41-31280843E0A3@tzi.org>
References: <6B8B1B7A-90B6-4E81-99B3-BF2159209D1A@tzi.org>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "draft-ietf-core-coap@tools.ietf.org" <draft-ietf-core-coap@tools.ietf.org>,  General Area Review Team <gen-art@ietf.org>, Barry Leiba <barryleiba@computer.org>, "core-chairs@tools.ietf.org" <core-chairs@tools.ietf.org>, Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1503)
Subject: [Gen-art] Fwd: Operations Directorate Review of draft-ietf-core-coap-13.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 22:42:54 -0000

Here is the reply to the ops-dir review I just talked about.

Gr=FC=DFe, Carsten


Begin forwarded message:

> Resent-From: draft-alias-bounces@tools.ietf.org
> From: Carsten Bormann <cabo@tzi.org>
> Subject: Re: Operations Directorate Review of =
draft-ietf-core-coap-13.txt
> Date: March 11, 2013 22:24:04 +0100
> Resent-To: brian@skyfoundry.com, cabo@tzi.org, hartke@tzi.org, =
zach@sensinode.com
> To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
> Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, =
"draft-ietf-core-coap@tools.ietf.org" =
<draft-ietf-core-coap@tools.ietf.org>, ext Benoit Claise =
<bclaise@cisco.com>, "barryleiba@computer.org" <barryleiba@computer.org>
>=20
> Hi Mehmet,
>=20
> thank you for this input.
>=20
> I read some of it as guidance for future development of the protocol, =
and in particular for shaping the next steps the working group needs to =
take on; it will be quite useful for this even if it is not influencing =
the base spec at this time.
>=20
> I believe we have to address scalability of the environments using the =
protocol in separate work; how we will scale those up is somewhat =
orthogonal to the base specification (which, however, is indeed intended =
to be applicable to trillions of nodes).  Similarly, there are multiple =
models for the interaction with other protocols such as DNS, and =
scalability will have to be considered in refining these models.
>=20
> NSTART is defined as 1 with a MUST; section 4.7 is specific about the =
cases where different values will be allowed.  Again, defining =
congestion control schemes more flexible than the base spec is future =
work.
>=20
> Some specific comments:
>=20
>> - The table in Section 4.8 needs a table number and title.
>=20
> Fixed in SVN (will be in -14).
>=20
>> - Section 4.8.1. "Changing The Parameters" says: "It is recommended =
that an application environment use consistent values for these =
parameters." However, it is unclear what the definition of "consistent" =
is in this context. The values in the table could be seen as an example =
of consistent set of variables. I would like to suggest to provide =
"value intervals" for the parameters, within which the entire parameter =
set appears to be consistent. Also it is unclear what is meant by =
"congestion-safe in the Internet" or "congestion control safety". =
Depending on this understanding the user of the protocol will be able to =
choose the correct values.
>=20
> One problem is that it will require some ongoing research to answer =
these questions.
> So we can't lock them down yet, and instead can just refer to general =
principles.
> This includes limits on the values.
>=20
>> - Concerning default values RFC 5706 states: "It is very useful to =
understand whether defaults are based on best current practice and are =
expected to change as technologies advance".
>> In the CoAP draft this has been done only for a few cases and could =
be further extended.
>=20
> The current draft is quite clear that advances in congestion control =
mechanisms are going to make different values possible.  Those =
implementations that do not follow those advances are served reasonably =
well by the standard values.
>=20
>> - Section 4.8.2.  "Time Values derived from Transmission Parameters": =
I would like to suggest to summarize the discussed time values in a =
table with following column titles: Name, recommended default value, =
allowed value interval, error code if relevant.
>=20
> We don't have the columns 3 and 4 yet.
> I have added a table with columns 1 and 2.
>=20
>> ** Concerning the migration path, and future versions of CoAP in the =
same network:
>>=20
>> - It would be useful to state clearly, in which cases it is dangerous =
to change any of the recommended default values or parameters in future =
versions of CoAP and would potentially impact the co-existence of two =
CoAP versions. Thus such a statement would support an incremental =
deployment to be successful.
>=20
> Again, I believe this is future work, which also applies for the =
configuration and management data model.
>=20
> Protocol debugging is aided by the self-describing nature of the =
protocol messages.
> This has worked pretty well in the (informal and formal) interops so =
far.
>=20
> Future work will have to address management interfaces for CoAP nodes, =
including management of security related events.
> I think some of this will have to integrate with resource discovery, =
an active subject in the working group.
>=20
> Gr=FC=DFe, Carsten
>=20
>=20
>=20


From peter@akayla.com  Tue Apr 23 22:56:17 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2EDA21F93AB; Tue, 23 Apr 2013 22:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 dSoyWZweykaK; Tue, 23 Apr 2013 22:56:17 -0700 (PDT)
Received: from p3plsmtpa09-07.prod.phx3.secureserver.net (p3plsmtpa09-07.prod.phx3.secureserver.net [173.201.193.236]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC5A21F94A9; Tue, 23 Apr 2013 22:56:16 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-07.prod.phx3.secureserver.net with  id ThwE1l00d1huGat01hwF2p; Tue, 23 Apr 2013 22:56:16 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
References: 
In-Reply-To: 
Date: Tue, 23 Apr 2013 22:56:32 -0700
Message-ID: <002c01ce40b0$7951aa60$6bf4ff20$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac409G6BqoWAcV+eTe6M/+710JRlsQLurouw
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 05:56:17 -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-pcp-upnp-igd-interworking-08
Reviewer: Peter Yee
Review Date: Apr-23-2013
IETF LC End Date: Apr-08-2013
IESG Telechat date: Apr-25-2013

Summary: This draft is ready for publication as a Standards Track RFC.
[Ready]

This is a well-written draft describing how Universal Plug-and-Play Internet
Gateway Devices interwork with NAT devices that use the Port Control
Protocol.  All of my previous review comments on the draft have been
addressed.

		-Peter



From peter@akayla.com  Tue Apr 23 22:59:54 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B2EF21F8C08; Tue, 23 Apr 2013 22:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 636cr73JGT7P; Tue, 23 Apr 2013 22:59:53 -0700 (PDT)
Received: from p3plsmtpa09-03.prod.phx3.secureserver.net (p3plsmtpa09-03.prod.phx3.secureserver.net [173.201.193.232]) by ietfa.amsl.com (Postfix) with ESMTP id 8DC4121F8C06; Tue, 23 Apr 2013 22:59:53 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-03.prod.phx3.secureserver.net with  id Thzr1l0081huGat01hzrpr; Tue, 23 Apr 2013 22:59:52 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
References: <002c01ce40b0$7951aa60$6bf4ff20$@akayla.com>
In-Reply-To: <002c01ce40b0$7951aa60$6bf4ff20$@akayla.com>
Date: Tue, 23 Apr 2013 22:59:33 -0700
Message-ID: <002d01ce40b0$fa8b7bb0$efa27310$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHywG2QsLxL61oZqQrX4UAYteW4gJib4LIA
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 05:59:54 -0000

Grrr, typo in the subject line.  That should be draft version -08, as
correctly
referenced below.  Sigh.

		-Peter

-----Original Message-----
From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On Behalf
Of Peter Yee
Sent: Tuesday, April 23, 2013 10:57 PM
To: draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org
Cc: gen-art@ietf.org; ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07

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-pcp-upnp-igd-interworking-08
Reviewer: Peter Yee
Review Date: Apr-23-2013
IETF LC End Date: Apr-08-2013
IESG Telechat date: Apr-25-2013

Summary: This draft is ready for publication as a Standards Track RFC.
[Ready]

This is a well-written draft describing how Universal Plug-and-Play Internet
Gateway Devices interwork with NAT devices that use the Port Control
Protocol.  All of my previous review comments on the draft have been
addressed.

		-Peter


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


From christer.holmberg@ericsson.com  Wed Apr 24 00:40:46 2013
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FEAB21F8FB2 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 00:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.035
X-Spam-Level: 
X-Spam-Status: No, score=-6.035 tagged_above=-999 required=5 tests=[AWL=0.213,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, 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 DCjvPB8Xw+ZW for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 00:40:45 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 13F9921F8F63 for <gen-art@ietf.org>; Wed, 24 Apr 2013 00:40:42 -0700 (PDT)
X-AuditID: c1b4fb25-b7f366d000004d10-83-51778c761721
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 53.96.19728.67C87715; Wed, 24 Apr 2013 09:40:38 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.02.0328.009; Wed, 24 Apr 2013 09:40:37 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-sheffer-running-code-04
Thread-Index: Ac5Avp6kMIKUKs8JSk+ZYcMQZ1aRjQ==
Date: Wed, 24 Apr 2013 07:40:37 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C35D420@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C35D420ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrDLMWRmVeSWpSXmKPExsUyM+JvrW5ZT3mgQcMPUYvH3XuZLK6++szi wOSxZMlPJo8vlz+zBTBFcdmkpOZklqUW6dslcGV82TOBuWCVXsWBPd9YGxg3aHQxcnJICJhI tM86zAZhi0lcuLceyObiEBI4zCixu2M7I4SzhFHi3fPFzF2MHBxsAhYS3f+0QRpEBDQl5q54 ywRiMwukSjw9NJsFxBYWMJf4+r2DDaLGRuLHgt/sELaexNwD65hBbBYBVYkPS6eC2bwCvhLH pywGq2cEOuL7qTVQM8Ulbj2ZzwRxnIDEkj3nmSFsUYmXj/+xQtiKElenL4eqz5c4vXka1ExB iZMzn7BMYBSehWTULCRls5CUQcR1JBbs/sQGYWtLLFv4mhnGPnPgMROy+AJG9lWM7LmJmTnp 5UabGIExcnDLb9UdjHfOiRxilOZgURLnDXe9ECAkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qB Ubjy/KprDyKuMJa8VVx0JNHK1oD7377cl+EbBD7sO6C+O7/V21At6qLNN08dt+kfuS/FFbK4 Mq1f5Vejt0l1lcxJ4+nndh7/lWOxRrV6kuS/OXFOgr/s635I/BafsXuHyzfx73/W7w5esOFl uizXTnFr7i9SbzYrhczZVW4vymE0Y/2RpHWB/EosxRmJhlrMRcWJAHN5xpxfAgAA
Cc: "draft-sheffer-running-code.all@tools.ietf.org" <draft-sheffer-running-code.all@tools.ietf.org>
Subject: [Gen-art] Genart review of draft-sheffer-running-code-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 07:40:46 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1C35D420ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>


Document:                         draft-sheffer-running-code-04



Reviewer:                           Christer Holmberg



Review Date:                     23 April 2013



IETF LC End Date:             10 May 2013



IETF Telechat Date           N/A



Summary:  The draft is well written, with a minor issues/question.



Major Issues: None



Minor Issues: I think it would be good to also describe and/or reference th=
e test cases that were performed in order to determine the interoperability=
. In some cases it may be obvious, but if an Internet-Draft specifies a lar=
ge protocol, with many features and options, just saying that there exist i=
nteroperability between two implementations doesn't really say much.



Editorial nits: None



Best regards,



Christer



--_000_7594FB04B1934943A5C02806D1A2204B1C35D420ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on Gen-ART, please see the FAQ at &lt;<a href=3D"http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq</a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; draft-sheffer-running-code-04<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Reviewer:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Christer Holmberg<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Review Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; 23 April 2013<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10 May 2013<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">IETF Telechat Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; N/A<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary:&nbsp; The draft is well written, with a =
minor issues/question.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major Issues: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor Issues: I think it would be good to also de=
scribe and/or reference the test cases that were performed in order to dete=
rmine the interoperability. In some cases it may be obvious, but if an Inte=
rnet-Draft specifies a large protocol,
 with many features and options, just saying that there exist interoperabil=
ity between two implementations doesn&#8217;t really say much.<o:p></o:p></=
p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Editorial nits: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Best regards,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Christer<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1C35D420ESESSMB209erics_--

From dromasca@avaya.com  Wed Apr 24 00:50:19 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59F3321F8DD4 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 00:50:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.500, 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 aWM2ahJ0O3Lw for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 00:50:18 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 9415A21F8D61 for <gen-art@ietf.org>; Wed, 24 Apr 2013 00:50:16 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAFOOd1GHCzI1/2dsb2JhbABQgmUhvwZ/FAJ0gh8BAQEBAgESZwUHBAIBCA0BAwQBAQsdBzIUCQgCBAENBQgah2wGAaFhm2UXjXaBATEHBoJiYQOIV5Ryim6DDoFzNQ
X-IronPort-AV: E=Sophos;i="4.87,540,1363147200";  d="scan'208";a="8454830"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 24 Apr 2013 03:49:59 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 24 Apr 2013 03:46:51 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.02.0328.009; Wed, 24 Apr 2013 03:49:57 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Carsten Bormann <cabo@tzi.org>, Jari Arkko <jari.arkko@piuha.net>
Thread-Topic: [Gen-art] Gen-ART review for draft-ietf-core-coap-14
Thread-Index: AQHOQGHChtyPRu8gr0aH+K8bu+trTJjkqaeAgABVG6A=
Date: Wed, 24 Apr 2013 07:49:57 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA0D290C@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA0B8EE3@AZ-FFEXMB04.global.avaya.com> <AA7BC87B-4FB2-406E-80D5-72F0A8FA036E@tzi.org> <2126E8E4-A8E8-4C49-BF19-3883C888497C@piuha.net> <52241DAA-FB72-4CE0-9C17-FB5032292CBE@tzi.org>
In-Reply-To: <52241DAA-FB72-4CE0-9C17-FB5032292CBE@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-core-coap@tools.ietf.org" <draft-ietf-core-coap@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, Barry Leiba <barryleiba@computer.org>, "core-chairs@tools.ietf.org" <core-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review for draft-ietf-core-coap-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 07:50:20 -0000

Hi Carsten,

> Re the security considerations:
> As of today, we don't have mechanisms to effect any of these parameter
> changes.
> I believe any such mechanisms developed in the future will have to
> address the pertinent security considerations.

In this case I believe that the Security Considerations sections needs to m=
ention the risks and the need for future work, also as a warning to the ope=
rators deploying the protocol so that they can take adequate protection mea=
sures by proprietary methods if the consider this necessary.=20

Regards,

Dan



> -----Original Message-----
> From: Carsten Bormann [mailto:cabo@tzi.org]
> Sent: Wednesday, April 24, 2013 1:41 AM
> To: Jari Arkko
> Cc: Romascanu, Dan (Dan); draft-ietf-core-coap@tools.ietf.org; General
> Area Review Team; Barry Leiba; core-chairs@tools.ietf.org
> Subject: Re: [Gen-art] Gen-ART review for draft-ietf-core-coap-14
>=20
> Jari,
>=20
> indeed, it seems we never replied to these two items.
>=20
> >> 2 . The WG charter says:
> >>
> >>> 7) Consider operational and manageability aspects of the protocol
> >>> and at a minimum provide a way to tell if a Device is powered on or
> not.
> >>
> >>
> >> There is no mention in the protocol document (or other documents in
> core) about manageability and operational considerations. Maybe some
> work is being prepared, although I saw no core documents dealing with
> it. I believe that it would be good for the document to include either
> an Operational and Manageability Considerations section as recommended
> by RFC 5706 or, a short informational 'Future Work' section or appendix
> that mentions the need to deal with the operational and manageability
> aspects, and possibly point to work already done in the IETF for example
> on the coman mail list concerning management of constrained networks.
> >>
> >> 3. Section 4.8 defines a number of CoAP protocol parameters and
> derived parameters that according to 4.8.1 may be changed. Some of these
> parameters have limitations and their changes may affect the basic
> functionality of the nodes, the interaction between nodes or between
> nodes and servers, as well as the functioning in constrained
> environments. However there is no risk analysis in Section 11 (Security
> Considerations) about the threats related to mis-configuration of the
> modes and un-appropriate or malevolent changes in these parameters, and
> recommendations of security counter-measures on this respect.
>=20
> There is some discussion of this in the March 11 reply to the ops-dir
> review.
>=20
> It seems this message is not publicly archived.
> I'll dig it out and send it separately.
>=20
> Re the security considerations:
> As of today, we don't have mechanisms to effect any of these parameter
> changes.
> I believe any such mechanisms developed in the future will have to
> address the pertinent security considerations.
>=20
> >> Minor issues:
> >>
> >> 1. The WG charter says:
> >>
> >>> The WG will coordinate on requirements from many organizations
> >>> including OpenSG/NIST, ZigBee/HomePlug, IPSO Alliance, OASIS,
> >>> SENSEI, ASHRAE/BACnet; other SDOs and organizations.
> >>
> >> I am wondering whether the listed organizations were informed about
> the IETF conducting the Last Call on the protocol document. Maybe I
> missed some messages, but I see no feedback in the archives of the WG or
> IETF lists, or in the liaison statements page reflecting such
> interaction.
>=20
> The coordination on requirements was mostly done in 2010, and I'm not
> aware of any formal liaisons we picked up from that.
> Since then, we have had many people that were both in CoRE and in one or
> more the organizations listed (which now probably need to be
> complemented with OMA, ETSI and oneM2M, ...).
> ETSI even ran a couple of CoAP interops...
> I must admit that it simply didn't occur to me that we should do
> additional publicity for the IETF last call there - I was quite happy
> with the level of visibility that we have right now.
>=20
> Gr=FC=DFe, Carsten


From jari.arkko@piuha.net  Wed Apr 24 00:54:58 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 326A221F8FE3 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 00:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, 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 kTmRf6yXxvbr for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 00:54:57 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 2201A21F8FAA for <gen-art@ietf.org>; Wed, 24 Apr 2013 00:54:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id CA4DB2CC46; Wed, 24 Apr 2013 10:54:55 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CWPdjM0NgV2x; Wed, 24 Apr 2013 10:54:53 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 378C32CC3C; Wed, 24 Apr 2013 10:54:53 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA43A4DC30@nkgeml501-mbs.china.huawei.com>
Date: Wed, 24 Apr 2013 10:54:54 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <5367086C-1E1F-4734-9A44-9F2681F5E357@piuha.net>
References: <51715EEA.60507@bell-labs.com> <B8F9A780D330094D99AF023C5877DABA43A4DC30@nkgeml501-mbs.china.huawei.com>
To: Qin Wu <bill.wu@huawei.com>, "Vijay K. Gurbani" <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1503)
Cc: draft-ietf-xrblock-rtcp-xr-burst-gap-discard@tools.ietf.org, Shida Schubert <shida@ntt-at.com>, General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 07:54:58 -0000

Vijay: thank you for the review, the Gen-ART reviews are very important =
for me. And Qin: Thanks for the prompt response and a well-written =
document. I plan to ballot a "No objection" position for this document =
in the coming IESG telechat, based on this review and my own quick look =
at the document.

Jari

On Apr 23, 2013, at 10:19 AM, Qin Wu <bill.wu@huawei.com> wrote:

> Hi, Vijay:
> Thank for your valuable review. See reply inline below.
>=20
> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@bell-labs.com]=20
> Sent: Friday, April 19, 2013 11:13 PM
> To: draft-ietf-xrblock-rtcp-xr-burst-gap-discard@tools.ietf.org
> Cc: General Area Review Team; Romascanu, Dan (Dan); Shida Schubert; =
Gonzalo Camarillo
> Subject: Gen-ART review of =
draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13
> Reviewer: Vijay K. Gurbani
> Review Date: Apr-19-2013
> IETF LC End Date: Mar-15-2013
> IESG Telechat date: Apr-25-2013
>=20
> This document is ready as a Proposed Standard.  One minor comment and
> one nit below.
>=20
> Major: 0
> Minor: 1
> Nits: 1
>=20
> Minor:
> - S2.1, the sentence, "A packet that arrives within this time window
>  but is too early or late to be played out or thrown away before
>  playout due to packet duplication or redundancy shall be regarded as
>  discarded." is hard to read and parse.
>=20
>=20
>  Clearly, if a packet arrives early, it will be buffered.  Just as
>  clearly, if a packet arrives too late to be played out, it will be
>  discarded.  Maybe you should break the offending sentence into two
>  separate sentences, one dealing with early arrival and the other
>  with late arrival.
>=20
> [Qin]: Agree and will split.
>=20
> Nits
> - S1.1, last paragraph: s/in[RFC3611]./in [RFC3611]./
>=20
> [Qin]: Good catch, thanks.
>=20
> Thanks,
>=20
> - vijay
> --=20
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web:   http://ect.bell-labs.com/who/vkg/
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From bill.wu@huawei.com  Wed Apr 24 00:57:04 2013
Return-Path: <bill.wu@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EBEF21F8FE3 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 00:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.695
X-Spam-Level: 
X-Spam-Status: No, score=-5.695 tagged_above=-999 required=5 tests=[AWL=0.904,  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 dWwnPaLWfk7s for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 00:57:02 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id BB1F521F8FAA for <gen-art@ietf.org>; Wed, 24 Apr 2013 00:57:00 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQT22600; Wed, 24 Apr 2013 07:56:59 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 24 Apr 2013 08:56:28 +0100
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 24 Apr 2013 08:56:58 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.113]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.01.0323.007; Wed, 24 Apr 2013 15:56:50 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Jari Arkko <jari.arkko@piuha.net>, "Vijay K. Gurbani" <vkg@bell-labs.com>
Thread-Topic: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13
Thread-Index: AQHOPQ/2Y7lbOXTGiUCDAQK6vsjD5JjjayvggAEWmwCAAIZwcA==
Date: Wed, 24 Apr 2013 07:56:50 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43A4E17A@nkgeml501-mbs.china.huawei.com>
References: <51715EEA.60507@bell-labs.com> <B8F9A780D330094D99AF023C5877DABA43A4DC30@nkgeml501-mbs.china.huawei.com> <5367086C-1E1F-4734-9A44-9F2681F5E357@piuha.net>
In-Reply-To: <5367086C-1E1F-4734-9A44-9F2681F5E357@piuha.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "draft-ietf-xrblock-rtcp-xr-burst-gap-discard@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-burst-gap-discard@tools.ietf.org>, Shida Schubert <shida@ntt-at.com>, General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 07:57:04 -0000

Thanks, Jari.

Regards!
-Qin
-----Original Message-----
From: Jari Arkko [mailto:jari.arkko@piuha.net]=20
Sent: Wednesday, April 24, 2013 3:55 PM
To: Qin Wu; Vijay K. Gurbani
Cc: draft-ietf-xrblock-rtcp-xr-burst-gap-discard@tools.ietf.org; Shida Schu=
bert; General Area Review Team; Gonzalo Camarillo
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-burst-g=
ap-discard-13

Vijay: thank you for the review, the Gen-ART reviews are very important for=
 me. And Qin: Thanks for the prompt response and a well-written document. I=
 plan to ballot a "No objection" position for this document in the coming I=
ESG telechat, based on this review and my own quick look at the document.

Jari

On Apr 23, 2013, at 10:19 AM, Qin Wu <bill.wu@huawei.com> wrote:

> Hi, Vijay:
> Thank for your valuable review. See reply inline below.
>=20
> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@bell-labs.com]=20
> Sent: Friday, April 19, 2013 11:13 PM
> To: draft-ietf-xrblock-rtcp-xr-burst-gap-discard@tools.ietf.org
> Cc: General Area Review Team; Romascanu, Dan (Dan); Shida Schubert; Gonza=
lo Camarillo
> Subject: Gen-ART review of draft-ietf-xrblock-rtcp-xr-burst-gap-discard-1=
3
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-xrblock-rtcp-xr-burst-gap-discard-13
> Reviewer: Vijay K. Gurbani
> Review Date: Apr-19-2013
> IETF LC End Date: Mar-15-2013
> IESG Telechat date: Apr-25-2013
>=20
> This document is ready as a Proposed Standard.  One minor comment and
> one nit below.
>=20
> Major: 0
> Minor: 1
> Nits: 1
>=20
> Minor:
> - S2.1, the sentence, "A packet that arrives within this time window
>  but is too early or late to be played out or thrown away before
>  playout due to packet duplication or redundancy shall be regarded as
>  discarded." is hard to read and parse.
>=20
>=20
>  Clearly, if a packet arrives early, it will be buffered.  Just as
>  clearly, if a packet arrives too late to be played out, it will be
>  discarded.  Maybe you should break the offending sentence into two
>  separate sentences, one dealing with early arrival and the other
>  with late arrival.
>=20
> [Qin]: Agree and will split.
>=20
> Nits
> - S1.1, last paragraph: s/in[RFC3611]./in [RFC3611]./
>=20
> [Qin]: Good catch, thanks.
>=20
> Thanks,
>=20
> - vijay
> --=20
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web:   http://ect.bell-labs.com/who/vkg/
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Apr 24 01:31:16 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DCAA21F8F4A for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 01:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.18
X-Spam-Level: 
X-Spam-Status: No, score=-102.18 tagged_above=-999 required=5 tests=[AWL=-0.380, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, 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 eIu72SjQG71a for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 01:31:16 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CEF5F21F8F41 for <gen-art@ietf.org>; Wed, 24 Apr 2013 01:31:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 256C92CC46; Wed, 24 Apr 2013 11:31:15 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Pc7kjrQGyKw; Wed, 24 Apr 2013 11:31:13 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id C0C612CC3C; Wed, 24 Apr 2013 11:31:13 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <002c01ce40b0$7951aa60$6bf4ff20$@akayla.com>
Date: Wed, 24 Apr 2013 11:31:13 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C4533F0-6A9F-4370-BDA8-4E8D7F4922CB@piuha.net>
References: <002c01ce40b0$7951aa60$6bf4ff20$@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1503)
Cc: draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 08:31:16 -0000

Peter: Thank you for your review. These reviews are important for me, =
and for the quality of the specifications. Mohamed: thanks for =
addressing Peter's issues from the earlier version of the review. I am =
balloting a No-Objection, based on this review and my ow review. Thanks =
you all for working on this spec, I believe it has an important role.

Jari

On Apr 24, 2013, at 8:56 AM, Peter Yee <peter@akayla.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Please wait for direction from your document shepherd or AD before =
posting a
> new version of the draft.
>=20
> Document: draft-ietf-pcp-upnp-igd-interworking-08
> Reviewer: Peter Yee
> Review Date: Apr-23-2013
> IETF LC End Date: Apr-08-2013
> IESG Telechat date: Apr-25-2013
>=20
> Summary: This draft is ready for publication as a Standards Track RFC.
> [Ready]
>=20
> This is a well-written draft describing how Universal Plug-and-Play =
Internet
> Gateway Devices interwork with NAT devices that use the Port Control
> Protocol.  All of my previous review comments on the draft have been
> addressed.
>=20
> 		-Peter
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Apr 24 02:45:49 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5422421F9057 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 02:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 WfuFIq7dTer5 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 02:45:48 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6481021F9052 for <gen-art@ietf.org>; Wed, 24 Apr 2013 02:45:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8468D2CC46; Wed, 24 Apr 2013 12:45:46 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xI-_6CR2-UA5; Wed, 24 Apr 2013 12:45:45 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 5E1C42CC3C; Wed, 24 Apr 2013 12:45:45 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <27120AB3-75C5-4EB0-898B-FE2D354E59D4@nostrum.com>
Date: Wed, 24 Apr 2013 12:45:45 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <2E207801-0D8E-465A-97C6-E99E3D45C2D7@piuha.net>
References: <FA827D6C-D3C0-4F8A-8FF8-636A93A9646D@nostrum.com> <27120AB3-75C5-4EB0-898B-FE2D354E59D4@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1503)
Cc: draft-ietf-ospf-ipv4-embedded-ipv6-routing.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-ospf-ipv4-embedded-ipv6-routing-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 09:45:49 -0000

Ben: Thank you very much for this re-review and the original review.  I =
plan to ballot No Objection for this document, based on your review, but =
(as I normally do) I will also do a quick review myself to see if =
there's anything that stands out.

Jari

On Apr 19, 2013, at 11:51 PM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-ospf-ipv4-embedded-ipv6-routing-11=20
> Reviewer: Ben Campbell
> Review Date: 2013-04-19
> IESG Telechat date: 2013-04-25
>=20
> Summary: Ready for publication as an informational RFC. All of the =
comments from my previous review of version 07 have been addressed. =
However, there=20
>=20
> Major issues:
>=20
> None
>=20
> Minor issues:
>=20
> None
>=20
> Nits/editorial comments:
>=20
> Note: The online IDNits tool appears to be broken today, so I was =
unable to recheck this version.
>=20
> There is a new section 12 added since version 07. If there is another =
revision prior to approval, I suggest the authors make another pass at =
proofreading it. If not, the errors are all of the sort that can be =
reasonably fixed by the RFC editor. Some specifics:
>=20
> -- paragraph 3, 1st sentence: "If one approach is to be deployed, it =
is the operator's decision for the choice."
>=20
> -- paragraph 4, 1st sentence: "... there requires some =
configurations."
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From Chris.Dearlove@baesystems.com  Wed Apr 24 02:18:57 2013
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D32721F8F1E for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 02:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gyKL6Sxh-0hD for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 02:18:56 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id B8B4921F8D2B for <gen-art@ietf.org>; Wed, 24 Apr 2013 02:18:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,540,1363132800"; d="scan'208";a="281409192"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 24 Apr 2013 10:18:50 +0100
Received: from baemasodc005.greenlnk.net ([10.108.52.29]) by baemasodc004.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id r3O9InG0023358 for <gen-art@ietf.org>; Wed, 24 Apr 2013 10:18:50 +0100
X-IronPort-AV: E=Sophos;i="4.87,540,1363132800"; d="scan'208";a="14064769"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasodc005.greenlnk.net with ESMTP; 24 Apr 2013 10:18:49 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.244]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.02.0328.009; Wed, 24 Apr 2013 10:18:48 +0100
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, "draft-ietf-manet-olsrv2-metrics-rationale.all@tools.ietf.org" <draft-ietf-manet-olsrv2-metrics-rationale.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat review of draft-ietf-manet-olsrv2-metrics-rationale-03.txt
Thread-Index: AQHOQG6pUdnzCXevSUGXATHuaZXtRZjlEp4g
Date: Wed, 24 Apr 2013 09:18:48 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25063373@GLKXM0002V.GREENLNK.net>
References: <517704FD.4020005@ericsson.com>
In-Reply-To: <517704FD.4020005@ericsson.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 24 Apr 2013 05:22:47 -0700
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-manet-olsrv2-metrics-rationale-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 09:18:57 -0000

Thank you for this, some comments below, marked CD> (Generally, where I hav=
en't commented, I think the point is good.)

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Suresh Krishnan [mailto:suresh.krishnan@ericsson.com]=20
Sent: 23 April 2013 23:03
To: draft-ietf-manet-olsrv2-metrics-rationale.all@tools.ietf.org; General A=
rea Review Team
Subject: Gen-ART Telechat review of draft-ietf-manet-olsrv2-metrics-rationa=
le-03.txt

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document:  draft-ietf-manet-olsrv2-metrics-rationale-03.txt
Reviewer: Suresh Krishnan
Review Date: 2013/04/23
IESG Telechat date: 2013/04/25

Summary: This document is almost ready for publication as an
Informational RFC but I do have some comments you may wish to address.

Major
=3D=3D=3D=3D=3D

* Section 5.6 Link Metrics

I had a hard time understanding this section as a whole and specifically
the metric calculation. Intuitively, it was clear to me that you cannot
squeeze 2^24 values into 12 bits :-). So the question immediately became
what values get left out.

If I understand correctly for a given value of b, each increment of a
increases the metric value by 2^b. If my understanding is correct (my
apologies if it is not), please consider modifying the text to clarify
the following

-> The compressed metric is lossy and is not capable of representing
*all* metric values in the range 2^24-2^m. The larger the value of b
more the values that cannot be represented.
-> Two metric values that are different can result in the same
compressed metric and hence cannot be really compared for equality as
described in the section. e.g. metric value 821 and 822 would be mapped
into the same compressed metric and a comparison will conclude that they
are equal.
-> Describe a short algorithm for converting a metric value into a
compressed metric. i.e. Given a metric value x, how to obtain a and b
from it. e.g.

b=3Dlog2(x+256)-9

CD> Such an algorithm is already in the OLSRv2 draft, it does not seem nece=
ssary to repeat it. It could of course be referred to.

* To achieve interoperability and to avoid loops, the values of e and m
need to be the same across the network. The following sentence seems to
allow for other values of e and m ("An appropriate pair..."). Suggest

OLD:
The required 24 bit limit can be achieved if 2^e+m =3D 24. An appropriate
pair of values to achieve this is e =3D 4, m =3D 8.

NEW:
The required 24 bit limit can be achieved if 2^e+m =3D 24. Since e+m=3D12,
solving for e and m will lead to e =3D 4, m =3D 8.

CD> The NEW text is incorrect, because it assumes e+m =3D 12 was an input t=
o the process. Rather those possible pairs that satisfied 2^e+m =3D 24 were=
 considered, and the preferred (e.m) pair selected, which conveniently gave=
 e+m=3D12. (I remember when first doing this, and the satisfaction that it =
gave 12, which left the 4 bits we wanted, but up to that point were doing d=
ifferently, was great - sometimes things do work out well.) So while the po=
int that this is fixed is good (but clearly in OLSv2 a single choice is use=
d) different alternative wording would be needed.

Minor
=3D=3D=3D=3D=3D

* It is unclear to me how the metrics can be configured to handle the
privileged relay aerial router case described in Section 4. Assume there
is a cost metric on the link to/from the aerial router, would this be
set to low or high (I would assume high)? If the metric is set high, the
ground routers may route through several low quality links which seem to
have a lower path metric but may end up underusing the aerial link. Are
there any guidelines in this regard?

CD> Clearly you set the aerial link metric high. If you want to ensure it i=
s only used when absolutely necessary, you could set it to maximum. If you =
want to allow it in some cases rather than multiple ground links, you set i=
t accordingly - if you want to use an aerial link rather than N ground link=
s with metric 1, set it to N/2 (up and down). It's more complicated if grou=
nd links have variable metrics. But guidance on how to do this is beyond th=
e scope of this document, which describes what has been done, and that woul=
d not be that. (There is a gap the authors are aware of for a broader infor=
mational document -ID/RFC or other format - on use of options in OLSRv2, no=
t just on metrics. Unfortunately so far we haven't had the available time t=
o do so, and can't see that time being available soon.)

Thanks
Suresh



********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From christer.holmberg@ericsson.com  Wed Apr 24 05:45:53 2013
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8BB21F8F22 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 05:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.066
X-Spam-Level: 
X-Spam-Status: No, score=-6.066 tagged_above=-999 required=5 tests=[AWL=0.183,  BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 EpK5XfDMpYLR for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 05:45:52 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 3772E21F8D03 for <gen-art@ietf.org>; Wed, 24 Apr 2013 05:45:52 -0700 (PDT)
X-AuditID: c1b4fb25-b7f366d000004d10-02-5177d3fe6d8d
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 8A.B8.19728.EF3D7715; Wed, 24 Apr 2013 14:45:51 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.167]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.02.0328.009; Wed, 24 Apr 2013 14:45:50 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Thread-Topic: Genart review of draft-sheffer-running-code-04
Thread-Index: Ac5Avp6kMIKUKs8JSk+ZYcMQZ1aRjQAGgHaAAAQ2jAA=
Date: Wed, 24 Apr 2013 12:45:49 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C35E94B@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C35D420@ESESSMB209.ericsson.se> <5177D38F.7090305@gmail.com>
In-Reply-To: <5177D38F.7090305@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsUyM+Jvre7/y+WBBoffcVk87t7LZHH11WcW i1X3Z7A7MHvsnHWX3WPJkp9MHl8uf2YLYI7isklJzcksSy3St0vgyrj8cyVTwQzhiiWdt1ka GG8IdTFyckgImEi0TmhnhLDFJC7cW8/WxcjFISRwmFGi8/47JghnCaPEmeZVQFUcHGwCFhLd /7RBTBEBTYlpR61ASpgF+hgler8tYQWJCwtYS3y76gAyU0TARuLHgt/sELaVxO9bM8B2sQio SjzY94gFxOYV8JX4dXcfO0irkECOxN4DFiBhTqDpD75fZQKxGYFO+35qDZjNLCAucevJfCaI kwUkluw5zwxhi0q8fPyPFcJWlLg6fTkTyEhmoDnrd+lDtCpKTOl+yA6xVVDi5MwnLBMYxWYh mToLoWMWko5ZSDoWMLKsYmTPTczMSS832sQIjJeDW36r7mC8c07kEKM0B4uSOG+464UAIYH0 xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYxdwbzMW6r55+42tI45dsp2oXPW0YIjk34UFi3o0vy4 oufSjdeJq4/kRlTEi738snT93vM//2T4PhJQe6tqOatDf8rMTH9Ld4HO/I+nNBbpTzBo+HRL kavrUNHKx9K39Obsa1xfIb83Ze2LqBQdKcn5P1l6otTOqArcmiG5aePicxbSHqoq0RuUWIoz Eg21mIuKEwEEICYwZQIAAA==
Cc: "draft-sheffer-running-code.all@tools.ietf.org" <draft-sheffer-running-code.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Genart review of draft-sheffer-running-code-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 12:45:53 -0000

SGksDQoNCkNvdWxkIHlvdSBzYXkgc29tZXRoaW5nIGxpa2UgImluY2x1ZGluZyByZWZlcmVuY2Vz
IHRvIHRlc3QgY2FzZSBkZXNjcmlwdGlvbnMgYW5kIGludGVyb3BlcmFiaWxpdHkgcmVwb3J0cywg
d2hlbiBzdWNoIGV4aXN0LiI/DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBZYXJvbiBTaGVmZmVyIFttYWlsdG86eWFyb25mLmlldGZA
Z21haWwuY29tXSANClNlbnQ6IDI0LiBodWh0aWt1dXRhIDIwMTMgMTU6NDQNClRvOiBDaHJpc3Rl
ciBIb2xtYmVyZw0KQ2M6IGdlbi1hcnRAaWV0Zi5vcmc7IGRyYWZ0LXNoZWZmZXItcnVubmluZy1j
b2RlLmFsbEB0b29scy5pZXRmLm9yZw0KU3ViamVjdDogUmU6IEdlbmFydCByZXZpZXcgb2YgZHJh
ZnQtc2hlZmZlci1ydW5uaW5nLWNvZGUtMDQNCg0KSGkgQ2hyaXN0ZXIsDQoNCnRoYW5rcyBmb3Ig
eW91ciByZXZpZXchDQoNClRoZSBjdXJyZW50IChyYXRoZXIgdmFndWUpIHdvcmRpbmcgaXM6DQoN
CiAgICBJbiBhZGRpdGlvbiwgdGhpcyBzZWN0aW9uIGNhbiBjb250YWluIGluZm9ybWF0aW9uIGFi
b3V0IHRoZQ0KICAgIGludGVyb3BlcmFiaWxpdHkgb2YgYW55IG9yIGFsbCBvZiB0aGUgaW1wbGVt
ZW50YXRpb25zLg0KDQpXZSBjb3VsZCBhZGQ6ICJpbmNsdWRpbmcgcmVmZXJlbmNlcyB0byBpbnRl
cm9wZXJhYmlsaXR5IHJlcG9ydHMsIHdoZW4gc3VjaCBleGlzdC4iDQoNClRoYW5rcywNCglZYXJv
bg0KDQpPbiAyMDEzLTA0LTI0IDEwOjQwLCBDaHJpc3RlciBIb2xtYmVyZyB3cm90ZToNCj4gSSBh
bSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9yIGJhY2tn
cm91bmQgb24gDQo+IEdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdCANCj4gPGh0dHA6Ly93
aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+DQo+DQo+IERv
Y3VtZW50OiAgICAgICAgICAgICAgICAgICAgICAgICBkcmFmdC1zaGVmZmVyLXJ1bm5pbmctY29k
ZS0wNA0KPg0KPiBSZXZpZXdlcjogICAgICAgICAgICAgICAgICAgICAgICAgICBDaHJpc3RlciBI
b2xtYmVyZw0KPg0KPiBSZXZpZXcgRGF0ZTogICAgICAgICAgICAgICAgICAgICAyMyBBcHJpbCAy
MDEzDQo+DQo+IElFVEYgTEMgRW5kIERhdGU6ICAgICAgICAgICAgIDEwIE1heSAyMDEzDQo+DQo+
IElFVEYgVGVsZWNoYXQgRGF0ZSAgICAgICAgICAgTi9BDQo+DQo+IFN1bW1hcnk6ICBUaGUgZHJh
ZnQgaXMgd2VsbCB3cml0dGVuLCB3aXRoIGEgbWlub3IgaXNzdWVzL3F1ZXN0aW9uLg0KPg0KPiBN
YWpvciBJc3N1ZXM6IE5vbmUNCj4NCj4gTWlub3IgSXNzdWVzOiBJIHRoaW5rIGl0IHdvdWxkIGJl
IGdvb2QgdG8gYWxzbyBkZXNjcmliZSBhbmQvb3IgDQo+IHJlZmVyZW5jZSB0aGUgdGVzdCBjYXNl
cyB0aGF0IHdlcmUgcGVyZm9ybWVkIGluIG9yZGVyIHRvIGRldGVybWluZSB0aGUgDQo+IGludGVy
b3BlcmFiaWxpdHkuIEluIHNvbWUgY2FzZXMgaXQgbWF5IGJlIG9idmlvdXMsIGJ1dCBpZiBhbiAN
Cj4gSW50ZXJuZXQtRHJhZnQgc3BlY2lmaWVzIGEgbGFyZ2UgcHJvdG9jb2wsIHdpdGggbWFueSBm
ZWF0dXJlcyBhbmQgDQo+IG9wdGlvbnMsIGp1c3Qgc2F5aW5nIHRoYXQgdGhlcmUgZXhpc3QgaW50
ZXJvcGVyYWJpbGl0eSBiZXR3ZWVuIHR3byANCj4gaW1wbGVtZW50YXRpb25zIGRvZXNu4oCZdCBy
ZWFsbHkgc2F5IG11Y2guDQo+DQo+IEVkaXRvcmlhbCBuaXRzOiBOb25lDQo+DQo+IEJlc3QgcmVn
YXJkcywNCj4NCj4gQ2hyaXN0ZXINCj4NCg==

From dromasca@avaya.com  Wed Apr 24 06:05:42 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1E8121F8D13 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 06:05:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.499
X-Spam-Level: 
X-Spam-Status: No, score=-103.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 yz25WMUp+FiE for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 06:05:42 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 60D1621F8D0D for <gen-art@ietf.org>; Wed, 24 Apr 2013 06:05:42 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAAH/ZlGHCzI1/2dsb2JhbABQgmUhNsFIgQcWdIIhAQEDEig/EgEVBw4UQiYBBA4NGodyAQugPJ0jjmUxgmdhA5gjhQaKaIMLgig
X-IronPort-AV: E=Sophos;i="4.87,456,1363147200";  d="scan'208";a="8384783"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 24 Apr 2013 09:05:41 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 24 Apr 2013 09:02:33 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.02.0328.009; Wed, 24 Apr 2013 09:05:09 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: General Area Review Team <gen-art@ietf.org>
Thread-Topic: Gen-ART (Telechat) review for draft-ietf-core-coap-15 
Thread-Index: Ac5A7FgoUjYduZkZSSqPo1dezNgslw==
Date: Wed, 24 Apr 2013 13:05:08 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA0D2F09@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-core-coap@tools.ietf.org" <draft-ietf-core-coap@tools.ietf.org>, Barry Leiba <barryleiba@computer.org>, "core-chairs@tools.ietf.org" <core-chairs@tools.ietf.org>
Subject: [Gen-art] Gen-ART (Telechat) review for draft-ietf-core-coap-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 13:05:43 -0000

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, 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 m=
ay receive.

Document: draft-ietf-core-coap-15
Reviewer: Dan Romascanu
Review Date: 3/27/2013
IETF LC End Date: 3/27/2013
IESG Telechat date: 4/25/2013

Summary: This document is almost ready. Some of the issues in my first revi=
ew of the document were addressed in draft-15, or clarified by the authors =
in their responses. However issues #2 and #3 in the major issues list were =
not addressed in the revised I-D. It is up to the General Area Director and=
 the rest of the IESG to assess whether these issues are blocking.=20

Regards,

Dan



From jari.arkko@piuha.net  Wed Apr 24 06:16:40 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1088C21F9132 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 06:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, 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 lbNhv1QKwh29 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 06:16:39 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 033E121F9128 for <gen-art@ietf.org>; Wed, 24 Apr 2013 06:16:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3814E2CC46; Wed, 24 Apr 2013 16:16:38 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sCewjdgpQwzA; Wed, 24 Apr 2013 16:16:35 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id B61772CC3C; Wed, 24 Apr 2013 16:16:35 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA0D2F09@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 24 Apr 2013 16:16:35 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <688121F1-A27A-402C-ADE9-6563CB1BE19E@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA0D2F09@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1503)
Cc: "draft-ietf-core-coap@tools.ietf.org" <draft-ietf-core-coap@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, Barry Leiba <barryleiba@computer.org>, "core-chairs@tools.ietf.org" <core-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART (Telechat) review for draft-ietf-core-coap-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 13:16:40 -0000

Thanks for your re-review, Dan! This is one of the documents that I have =
already read in-depth before (but a long time ago) and will read the =
latest version in detail for the telechat. When I have done that I can =
form an opinion about the issues that you listed below. Thanks.

Jari

On Apr 24, 2013, at 4:05 PM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> =
wrote:

> 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-core-coap-15
> Reviewer: Dan Romascanu
> Review Date: 3/27/2013
> IETF LC End Date: 3/27/2013
> IESG Telechat date: 4/25/2013
>=20
> Summary: This document is almost ready. Some of the issues in my first =
review of the document were addressed in draft-15, or clarified by the =
authors in their responses. However issues #2 and #3 in the major issues =
list were not addressed in the revised I-D. It is up to the General Area =
Director and the rest of the IESG to assess whether these issues are =
blocking.=20
>=20
> Regards,
>=20
> Dan
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From yaronf.ietf@gmail.com  Wed Apr 24 05:44:05 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39C0B21F84EF for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 05:44:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.222
X-Spam-Level: 
X-Spam-Status: No, score=-102.222 tagged_above=-999 required=5 tests=[AWL=1.377, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 Bt9K93Zg69+L for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 05:44:04 -0700 (PDT)
Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com [74.125.83.43]) by ietfa.amsl.com (Postfix) with ESMTP id 5F74521F90AF for <gen-art@ietf.org>; Wed, 24 Apr 2013 05:44:04 -0700 (PDT)
Received: by mail-ee0-f43.google.com with SMTP id e50so716716eek.30 for <gen-art@ietf.org>; Wed, 24 Apr 2013 05:44:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=RuDh4t4H1OauiQuPauUorww38tdXLue864IugK2C/f8=; b=dH1z2X8MatBrBAjmeeA99uqKGzs1GBttrw2IViavMsQ44qrAXw1q5XnBXLJz/rHq3c 19DznaujlGPXJRHsGRaY1VEa6VjQb7IhvQTQsSAPjTIa8pW+pMzqLOXxK37fnjJdnBMi TMtH3PEia40dEcvIwXLAs7WnTdAK6dm62cE6RWU8hSe1btcLzjrfYHR1VDJDE8G8SOdP djvO5/slwbtGEHTKDkXYwFSK+GFUSR512CItGbHgKS21CcsO+f5m7rrZtsoclpbNJ09f o9EoRcyZRrrQ5yqbBw6LN0yaQY2cMgYtPTSKGpPKxs04Ru2Sq0UpJj7OCYhmKJtbWq9M XBHw==
X-Received: by 10.14.221.67 with SMTP id q43mr18557193eep.20.1366807443524; Wed, 24 Apr 2013 05:44:03 -0700 (PDT)
Received: from [10.0.0.14] (109-186-115-180.bb.netvision.net.il. [109.186.115.180]) by mx.google.com with ESMTPSA id bj2sm4022644eeb.1.2013.04.24.05.44.01 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Apr 2013 05:44:02 -0700 (PDT)
Message-ID: <5177D38F.7090305@gmail.com>
Date: Wed, 24 Apr 2013 15:43:59 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1C35D420@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C35D420@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Wed, 24 Apr 2013 06:21:03 -0700
Cc: "draft-sheffer-running-code.all@tools.ietf.org" <draft-sheffer-running-code.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Genart review of draft-sheffer-running-code-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 12:44:05 -0000

Hi Christer,

thanks for your review!

The current (rather vague) wording is:

    In addition, this section can contain information about the
    interoperability of any or all of the implementations.

We could add: "including references to interoperability reports, when 
such exist."

Thanks,
	Yaron

On 2013-04-24 10:40, Christer Holmberg wrote:
> 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>
>
> Document:                         draft-sheffer-running-code-04
>
> Reviewer:                           Christer Holmberg
>
> Review Date:                     23 April 2013
>
> IETF LC End Date:             10 May 2013
>
> IETF Telechat Date           N/A
>
> Summary:  The draft is well written, with a minor issues/question.
>
> Major Issues: None
>
> Minor Issues: I think it would be good to also describe and/or reference
> the test cases that were performed in order to determine the
> interoperability. In some cases it may be obvious, but if an
> Internet-Draft specifies a large protocol, with many features and
> options, just saying that there exist interoperability between two
> implementations doesnâ€™t really say much.
>
> Editorial nits: None
>
> Best regards,
>
> Christer
>

From yaronf.ietf@gmail.com  Wed Apr 24 05:48:02 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED5421F8F22 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 05:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.411
X-Spam-Level: 
X-Spam-Status: No, score=-102.411 tagged_above=-999 required=5 tests=[AWL=0.188, 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 YrTCP+THf6MI for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 05:48:02 -0700 (PDT)
Received: from mail-ea0-x234.google.com (mail-ea0-x234.google.com [IPv6:2a00:1450:4013:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 5EA1C21F8D03 for <gen-art@ietf.org>; Wed, 24 Apr 2013 05:47:57 -0700 (PDT)
Received: by mail-ea0-f180.google.com with SMTP id q16so649424ead.25 for <gen-art@ietf.org>; Wed, 24 Apr 2013 05:47:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Sryt3fkEThmdXboqdQnoTGzbwxfAM9e/u9lmrlSiS7c=; b=vhhnIDvpKrhTV2OU+besxosb113T9FfeZE/dTMrAM0D9QuzNmKiQsH6NZa7e/k70X3 Mm9WeiVZy+mLHjt8Ntq1MZNkslZyMtExw7UV6pfhsNPfx6MEYvIpq163YMYNPKUhoZaz lOsH4PSOhzvKzww3lAUagisIfcbxglsh1ph4zGJmEcXgz9ePzCk5GR+vKrVOmsaTYzjn Od9Wjm6YegLxZp1sH2pPxRdtAPHRqjiJ8xg6bm5KMyXSrE4sqVdkIjGzD7c4tHkWvF2L 9a3N/9cok8m9pUIpHD+JiB4t7urLDtudqJch9KzkifP3g1ML+vzUw0i1YqOGuJSnCPB3 p3fA==
X-Received: by 10.15.83.73 with SMTP id b49mr62991886eez.25.1366807676489; Wed, 24 Apr 2013 05:47:56 -0700 (PDT)
Received: from [10.0.0.14] (109-186-115-180.bb.netvision.net.il. [109.186.115.180]) by mx.google.com with ESMTPSA id bk42sm4029282eeb.3.2013.04.24.05.47.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Apr 2013 05:47:55 -0700 (PDT)
Message-ID: <5177D473.1020108@gmail.com>
Date: Wed, 24 Apr 2013 15:47:47 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1C35D420@ESESSMB209.ericsson.se> <5177D38F.7090305@gmail.com> <7594FB04B1934943A5C02806D1A2204B1C35E94B@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C35E94B@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Wed, 24 Apr 2013 06:21:03 -0700
Cc: "draft-sheffer-running-code.all@tools.ietf.org" <draft-sheffer-running-code.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Genart review of draft-sheffer-running-code-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 12:48:02 -0000

Sure.

Thanks,
	Yaron

On 2013-04-24 15:45, Christer Holmberg wrote:
> Hi,
>
> Could you say something like "including references to test case descriptions and interoperability reports, when such exist."?
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: Yaron Sheffer [mailto:yaronf.ietf@gmail.com]
> Sent: 24. huhtikuuta 2013 15:44
> To: Christer Holmberg
> Cc: gen-art@ietf.org; draft-sheffer-running-code.all@tools.ietf.org
> Subject: Re: Genart review of draft-sheffer-running-code-04
>
> Hi Christer,
>
> thanks for your review!
>
> The current (rather vague) wording is:
>
>      In addition, this section can contain information about the
>      interoperability of any or all of the implementations.
>
> We could add: "including references to interoperability reports, when such exist."
>
> Thanks,
> 	Yaron
>
> On 2013-04-24 10:40, Christer Holmberg wrote:
>> 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>
>>
>> Document:                         draft-sheffer-running-code-04
>>
>> Reviewer:                           Christer Holmberg
>>
>> Review Date:                     23 April 2013
>>
>> IETF LC End Date:             10 May 2013
>>
>> IETF Telechat Date           N/A
>>
>> Summary:  The draft is well written, with a minor issues/question.
>>
>> Major Issues: None
>>
>> Minor Issues: I think it would be good to also describe and/or
>> reference the test cases that were performed in order to determine the
>> interoperability. In some cases it may be obvious, but if an
>> Internet-Draft specifies a large protocol, with many features and
>> options, just saying that there exist interoperability between two
>> implementations doesnâ€™t really say much.
>>
>> Editorial nits: None
>>
>> Best regards,
>>
>> Christer
>>

From psaintan@cisco.com  Wed Apr 24 07:19:13 2013
Return-Path: <psaintan@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E720721F8B07 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 07:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4p7QZk+nh+Em for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 07:19:13 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 6F94121F8A53 for <gen-art@ietf.org>; Wed, 24 Apr 2013 07:19:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1879; q=dns/txt; s=iport; t=1366813153; x=1368022753; h=cc:message-id:from:to:in-reply-to: content-transfer-encoding:mime-version:subject:date: references; bh=KW5yOpJZc/0+TRrluJggD9WzklISQIm0mCe/6v28Cb0=; b=TNX/k3u57IhXG+wRq4cUbiq4r3QgJBl7Yy85OnwJo8yJ9jnwWO7QvZhw G+lo3I28JZWjlZZtnACkTcWCFAptK1Gqse4aO284mLkGE9QPDTx+Bo+VH h4ipWHQVDBwvdeExTMYxz/jAY+K+Di7fp0U2i07xPnfX4IyGjHkn1KZxc o=;
X-IronPort-AV: E=Sophos;i="4.87,542,1363132800"; d="scan'208";a="79431418"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 24 Apr 2013 14:19:12 +0000
Received: from [192.168.1.4] (sjc-vpn7-952.cisco.com [10.21.147.184]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3OEJA24008971; Wed, 24 Apr 2013 14:19:10 GMT
Message-Id: <BD017FC5-EE95-4ED6-9B52-2AAFA8ADDDD2@cisco.com>
From: Peter Saint-Andre <psaintan@cisco.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
In-Reply-To: <5176EB42.3030501@dial.pipex.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 24 Apr 2013 08:19:10 -0600
References: <5176EB42.3030501@dial.pipex.com>
X-Mailer: Apple Mail (2.936)
Cc: fluffy@cisco.com, adam@nostrum.com, General Area Review Team <gen-art@ietf.org>, mary.barnes@nortel.com, draft-saintandre-impp-call-info.all@tools.ietf.org, Mary Barnes <mary.h.barnes@gmail.com>
Subject: Re: [Gen-art] Gen-art LC review of draft-saintandre-impp-call-info-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 14:19:14 -0000

Hi Elwyn, thanks for the review.

On Apr 23, 2013, at 2:12 PM, Elwyn Davies wrote:

> 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-saintandre-impp-call-info-02.txt
> Reviewer: Elwyn Davies
> Review Date: 23 April 2013
> IETF LC End Date: 14 May 2013
> IESG Telechat date: (if known) -
>
> Summary: Ready.  See the generic issue with the IANA registry  
> mentioned below.
>
> Major issues: None
>
> Minor issues: None
>
> Nits/editorial comments:
> Generic comment about SIP Header Field Parameters registry: For the  
> uninitiated this registry is rather opaque.  Some parameters, such  
> as the Call-Info purpose parameter for which an extra value is  
> defined here, have predefined values.  However the predefined values  
> themselves are not in the registry and just giving a whole RFC  
> reference for places where values are defined is not very helpful.  
> For example, in the case of Call-Info, the initial predefined values  
> of purpose are buried in the Call-Info rule in the ABNF in Section  
> 25.1 of RFC 3261;  also, Section 20.9 describes the predefined  
> values (such as "icon") as 'parameters' rather than values of  
> 'purpose'.  It would probably be helpful to either improve the  
> references in the registry table or actaully quote the possible  
> predefined values in the table.
>

I agree, but as you say that's an issue with the SIP Header Field  
Parameters registry in general. I started to go down the path of  
fixing the registry as a whole, but I think I'd rather leave that for  
3261bis to tackle (sometime before the heat death of the universe).

Peter


From suresh.krishnan@ericsson.com  Wed Apr 24 21:12:36 2013
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF47121F9381 for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 21:12:36 -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 MTSpO0Gkk5PP for <gen-art@ietfa.amsl.com>; Wed, 24 Apr 2013 21:12:35 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 44F0421F937A for <gen-art@ietf.org>; Wed, 24 Apr 2013 21:12:35 -0700 (PDT)
X-AuditID: c618062d-b7f0d6d00000097e-36-5178ad32079f
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 1B.BA.02430.23DA8715; Thu, 25 Apr 2013 06:12:34 +0200 (CEST)
Received: from eusaamw0711.eamcs.ericsson.se (147.117.20.178) by EUSAAHC006.ericsson.se (147.117.188.90) with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 25 Apr 2013 00:12:34 -0400
Received: from [164.48.125.23] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.279.1; Thu, 25 Apr 2013 00:12:33 -0400
Message-ID: <5178AC95.4000505@ericsson.com>
Date: Thu, 25 Apr 2013 00:09:57 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
References: <517704FD.4020005@ericsson.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25063373@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D25063373@GLKXM0002V.GREENLNK.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUyuXRPlK7R2opAg0dztS26ps9msTjxcwmj xdVXn1kcmD1mLt7L5LFkyU8mjy+XP7MFMEdx2aSk5mSWpRbp2yVwZazeuYWx4I1AxeX9/xgb GGfydjFycEgImEh8ucrTxcgJZIpJXLi3ng3EFhI4yiixY3FoFyMXkL2HUWLB8nYWCGcro8T/ jo9MIFW8AtoS5x91M4MMYhFQlTgyRwskzAY0c8POz2AlogJhEqvWL2OGKBeUODnzCQuILSLg ING7oA+shllgC6PE1dW1ILawQITE173HWCCOyJPo/LqYHcTmFPCXeDRhLRvEoZISW160s4Os ZRbQkujdpQ8xRl5i+9s5zBCtmhJb13xnncAoPAvJ5lkIHbOQdCxgZF7FyFFanFqWm25ksIkR GNLHJNh0dzDueWl5iFGag0VJnDfI9UKAkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsbUo+2L hGS7bVP/LO+/UCvENDWOx6faMybrycRIxn8ScwwDP3ZKJT9a9661UWzqX98ljfWPY5rDmm2+ B+R8eblIMbV05fdjB7eJvS/t0L5mprtLfsm6lQH7eBOnn3sgcyPvo4Co7sGSa2bvD4rP/R89 RSx05RbxAt5g6777zMcnaZ0umOY6f6cSS3FGoqEWc1FxIgDdZSI+NwIAAA==
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-manet-olsrv2-metrics-rationale.all@tools.ietf.org" <draft-ietf-manet-olsrv2-metrics-rationale.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-manet-olsrv2-metrics-rationale-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 04:12:37 -0000

Hi Christopher,
  Thanks for your quick response. Trimming the stuff we agree on

On 04/24/2013 05:18 AM, Dearlove, Christopher (UK) wrote:
> Thank you for this, some comments below, marked CD> (Generally, where I haven't commented, I think the point is good.)
> 
>> -> Describe a short algorithm for converting a metric value into a
>> compressed metric. i.e. Given a metric value x, how to obtain a and b
>> from it. e.g.
>>
>> b=log2(x+256)-9
> CD> Such an algorithm is already in the OLSRv2 draft, it does not
> seem necessary to repeat it. It could of course be referred to.

Sounds good. Please add the reference to the OLSRv2 spec Section 6.2 for
the conversion.

>> * To achieve interoperability and to avoid loops, the values of e
>> and m need to be the same across the network. The following sentence
>> seems to allow for other values of e and m ("An appropriate
>> pair..."). Suggest
>>
>> OLD:
>> The required 24 bit limit can be achieved if 2^e+m = 24. An
>> appropriate pair of values to achieve this is e = 4, m = 8.
>>
>> NEW:
>> The required 24 bit limit can be achieved if 2^e+m = 24. Since
>> e+m=12, solving for e and m will lead to e = 4, m = 8.
> CD> The NEW text is incorrect, because it assumes e+m = 12 was an
> input to the process. Rather those possible pairs that satisfied
> 2^e+m = 24 were considered, and the preferred (e.m) pair selected,
> which conveniently gave e+m=12. (I remember when first doing this,
> and the satisfaction that it gave 12, which left the 4 bits we
> wanted, but up to that point were doing differently, was great -
> sometimes things do work out well.) So while the point that this is
> fixed is good (but clearly in OLSv2 a single choice is used)
> different alternative wording would be needed.

Not sure what you mean here. The OLSRv2 link metric is 12 bits long
according to the OLSRv2 draft. So e+m need to add up to 12, right?. In
any case, go for any wording that works for you as long as it ensures
that all the routers in the system will use the same value for e and m
and the metric will fit in the OLSRv2 LINK_METRIC TLV.

Thanks
Suresh


From Chris.Dearlove@baesystems.com  Thu Apr 25 02:44:38 2013
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0278A21F8721 for <gen-art@ietfa.amsl.com>; Thu, 25 Apr 2013 02:44:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kVQhSesV3X3I for <gen-art@ietfa.amsl.com>; Thu, 25 Apr 2013 02:44:37 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 5786B21F86F4 for <gen-art@ietf.org>; Thu, 25 Apr 2013 02:44:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,548,1363132800"; d="scan'208";a="332110952"
Received: from unknown (HELO baemasmds010.greenlnk.net) ([141.245.68.247]) by baemasmds003ir.sharelnk.net with ESMTP; 25 Apr 2013 10:44:07 +0100
Received: from baemasmds017.greenlnk.net ([10.15.207.104]) by baemasmds010.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id r3P9i691026129 for <gen-art@ietf.org>; Thu, 25 Apr 2013 10:44:07 +0100
X-IronPort-AV: E=Sophos;i="4.87,548,1363132800"; d="scan'208";a="14428829"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 25 Apr 2013 10:44:07 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.244]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.02.0328.009; Thu, 25 Apr 2013 10:44:06 +0100
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: Gen-ART Telechat review of draft-ietf-manet-olsrv2-metrics-rationale-03.txt
Thread-Index: AQHOQWsl6fr/Ye61OUeGUsCRkFJ6epjmq52A
Date: Thu, 25 Apr 2013 09:44:05 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D250636AB@GLKXM0002V.GREENLNK.net>
References: <517704FD.4020005@ericsson.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D25063373@GLKXM0002V.GREENLNK.net> <5178AC95.4000505@ericsson.com>
In-Reply-To: <5178AC95.4000505@ericsson.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-manet-olsrv2-metrics-rationale.all@tools.ietf.org" <draft-ietf-manet-olsrv2-metrics-rationale.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-manet-olsrv2-metrics-rationale-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 09:44:38 -0000

With regard to e + m needs to add up to 12, the thing is that this is descr=
ibing how the OLSRv2 draft came to be.

So (for our second attempt, but the first attempt is an ancient history red=
 herring) we (actually, I, so I know exactly the thought processes that hap=
pened) went like this.

We will use some form of modified mantissa/exponent. Not a pure one (that w=
as attempt one) and not a crudely offset one (that some had suggested but w=
as ugly). But the sequence of increments by 1, then by 2, then by 4 etc. se=
emed to have the right sort of properties, so I started there, and turned t=
hat into a formula.

Now we had a request to make the metric a full 24 bits long (so that when a=
ggregated over 255 hops it fitted 32 bits).

And that lead to 2^e + m =3D 24.

Now I looked at solutions (e,m) to that, and the ones that made any sort of=
 sense were (3,16) and (4,8). Which led to 19 and 12 bit values. 19 is nast=
y (quite big) but 12 is OK. It's more than the 8 we previously had (but whi=
ch didn't have a 24 bit range) but still allows us to do it in 2 octets (we=
 have to have exact octets due to RFC 5444). And then something convenient =
clicked. We had 4 options, which can occur in combinations. Previously we w=
ere putting this information somewhere else (and ugly) compressed to 2 bits=
 (as not all option combinations need be allowed for, but at an efficiency =
cost). But 12 is great, we can put all 4 in uncompressed in a 16 bit field.=
 So that all fits together nicely, let's do that.

But as you can see, 12 was not a precondition, but rather a result.

It didn't seem necessary to spell all of that out even in a rationale draft=
. But to start with the a priori assumption of e+m =3D 12 would be both his=
torically wrong, and a bad way to go. Because had the answer come to 13 we =
would probably have gone down a compressed 3 bit flags route (though with h=
indsight, I'm even more glad we didn't have to).

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Suresh Krishnan [mailto:suresh.krishnan@ericsson.com]=20
Sent: 25 April 2013 05:10
To: Dearlove, Christopher (UK)
Cc: draft-ietf-manet-olsrv2-metrics-rationale.all@tools.ietf.org; General A=
rea Review Team
Subject: Re: Gen-ART Telechat review of draft-ietf-manet-olsrv2-metrics-rat=
ionale-03.txt

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

Hi Christopher,
  Thanks for your quick response. Trimming the stuff we agree on

On 04/24/2013 05:18 AM, Dearlove, Christopher (UK) wrote:
> Thank you for this, some comments below, marked CD> (Generally, where I h=
aven't commented, I think the point is good.)
>=20
>> -> Describe a short algorithm for converting a metric value into a
>> compressed metric. i.e. Given a metric value x, how to obtain a and b
>> from it. e.g.
>>
>> b=3Dlog2(x+256)-9
> CD> Such an algorithm is already in the OLSRv2 draft, it does not
> seem necessary to repeat it. It could of course be referred to.

Sounds good. Please add the reference to the OLSRv2 spec Section 6.2 for
the conversion.

>> * To achieve interoperability and to avoid loops, the values of e
>> and m need to be the same across the network. The following sentence
>> seems to allow for other values of e and m ("An appropriate
>> pair..."). Suggest
>>
>> OLD:
>> The required 24 bit limit can be achieved if 2^e+m =3D 24. An
>> appropriate pair of values to achieve this is e =3D 4, m =3D 8.
>>
>> NEW:
>> The required 24 bit limit can be achieved if 2^e+m =3D 24. Since
>> e+m=3D12, solving for e and m will lead to e =3D 4, m =3D 8.
> CD> The NEW text is incorrect, because it assumes e+m =3D 12 was an
> input to the process. Rather those possible pairs that satisfied
> 2^e+m =3D 24 were considered, and the preferred (e.m) pair selected,
> which conveniently gave e+m=3D12. (I remember when first doing this,
> and the satisfaction that it gave 12, which left the 4 bits we
> wanted, but up to that point were doing differently, was great -
> sometimes things do work out well.) So while the point that this is
> fixed is good (but clearly in OLSv2 a single choice is used)
> different alternative wording would be needed.

Not sure what you mean here. The OLSRv2 link metric is 12 bits long
according to the OLSRv2 draft. So e+m need to add up to 12, right?. In
any case, go for any wording that works for you as long as it ensures
that all the routers in the system will use the same value for e and m
and the metric will fit in the OLSRv2 LINK_METRIC TLV.

Thanks
Suresh


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From david.black@emc.com  Thu Apr 25 08:22:25 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5E5F21F93B1; Thu, 25 Apr 2013 08:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.847
X-Spam-Level: 
X-Spam-Status: No, score=-99.847 tagged_above=-999 required=5 tests=[AWL=2.752, 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 eybJpJaj9I7w; Thu, 25 Apr 2013 08:22:16 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3D46121F92C0; Thu, 25 Apr 2013 08:22:10 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3PFLt1U020302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Apr 2013 11:21:56 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 25 Apr 2013 11:21:42 -0400
Received: from mxhub23.corp.emc.com (mxhub23.corp.emc.com [128.222.70.135]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3PFLcj8012731; Thu, 25 Apr 2013 11:21:38 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub23.corp.emc.com ([128.222.70.135]) with mapi; Thu, 25 Apr 2013 11:21:37 -0400
From: "Black, David" <david.black@emc.com>
To: Russ Housley <housley@vigilsec.com>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "hartmans@painless-security.com" <hartmans@painless-security.com>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Thu, 25 Apr 2013 11:21:36 -0400
Thread-Topic: Gen-ART review of draft-ietf-karp-crypto-key-table-07
Thread-Index: Ac5ByJPFxMQV0ntvRsGIbN7yaluElA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "<stbryant@cisco.com>" <stbryant@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-karp-crypto-key-table-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 15:22:26 -0000

Document: draft-ietf-karp-crypto-key-table-07
Reviewer: David L. Black
Review Date: April 25, 2013
IETF LC End Date: April 29, 2013

Summary: This draft is on the right track, but has open issues
described in the review.

This draft describes a conceptual key database for use by protocols.
It's definitely useful and valuable work, as key management is often
an afterthought in protocol design, even when security functionality
is actively worked on in the design process.

The draft text is in good shape and reads cleanly, but the draft is
short on precision in specifying a number of the fields for the database,
and the IANA registries; most of the open issues are requests for the
level of precision needed for interoperability and reuse of database
implementation across different protocol implementations.

Major issues:=20

(Section 2)

[1] LocalKeyName and PeerKeyName are strings.  What character set?
If Unicode (e.g., UTF-8?), add text on Unicode considerations (e.g.,
normalization).  Finding a Unicode expert will help in getting this
done quickly.  I have similar concerns for other strings, and in
particular, IANA should be told what a "string" is for any registry
field that contains one.

[2] I'm not sure that I understand what a KDF really is from its high
level description in this draft.  At the least, I'm surprised that the
importance of non-invertibility of a KDF is not mentioned - beyond that,
a functional description of inputs and outputs would help, including
a strong recommendation to inject unpredictable nonce material.  This
could be handled by referencing material on what a KDF is that exists
elsewhere.

(Section 4)

[3] It's important that this section cover all the fields involved in
the database lookups in Section 3 whose format may be protocol-specific
(the Direction and various time fields aren't).  Protocol should be
covered by the IANA registry, peers and key names are covered here,
but interface appears to be missing - item (9) covers presence vs.
absence of interface information, but not its format.

--- Lots of issues with the IANA Considerations (Section 8)

(Section 8.1.1)

[5] No field format information for the fields in a registry entry.
IANA should be told what formats to expect/use.

[6] "Protocol Specific Values" is not the same as "ProtocolSpecificInfo"
in section 2; the same name should be used, but whitespace differences
are ok.

[7] Should some sort of formats for Peers and Interfaces be included in
registering a Protocol?  If not, the lookups in section 3 may be
implementation-dependent (strings that work w/one implementation may
not work w/other implementations of the same protocol).  The specification
reference may suffice based on the requirements in section 4
for what has to be in each referenced specification.

(Sections 8.2 and 8.3)

[8] No registry entry content descriptions.  Need to supply information
on what to register and the formats of the elements of a registry entry.

[9] I suggest Expert Review for these registries, not just=20
First Come First Served, so that someone with a security "clue" can
check that the proposed registrations are reasonable.

Minor issues:

[A] Overall - I would like to see a paragraph added on how this database
conceptually relates to the IPsec Peer Authorization Database (PAD) -
see RFC 4301, section 4.4.3.

[B] (Section 2) Where is key size recorded?  Is that an implicit attribute
of Key?

[C] (Section 3) Where does key selection occur?  I would suggest that the
database return all possible keys and let the protocol figure out what to
use.  This is particularly important for inbound traffic for obvious reason=
s.

Nits/editorial comments:

I suggest dividing section 3 into
- 3.1 Outgoing Traffic
- 3.2 Incoming Traffic

idnits 2.12.16 found a truly trivial nit -
  =3D=3D Line 76 has weird spacing: '...strains  where...'

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------



From hartmans@painless-security.com  Thu Apr 25 09:47:26 2013
Return-Path: <hartmans@painless-security.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2144A21F9638; Thu, 25 Apr 2013 09:47:26 -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 7Cy5XcuK+CL6; Thu, 25 Apr 2013 09:47:25 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 46EA421F94B1; Thu, 25 Apr 2013 09:47:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 8D2722021D; Thu, 25 Apr 2013 12:45:26 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2RIwvD-7_Bfx; Thu, 25 Apr 2013 12:45:25 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Thu, 25 Apr 2013 12:45:25 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 8FB744499; Thu, 25 Apr 2013 12:47:22 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com>
Date: Thu, 25 Apr 2013 12:47:22 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com> (David Black's message of "Thu, 25 Apr 2013 11:21:36 -0400")
Message-ID: <tsla9omh811.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "gen-art@ietf.org" <gen-art@ietf.org>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "<stbryant@cisco.com>" <stbryant@cisco.com>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-karp-crypto-key-table-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 16:47:26 -0000

Here are some quick initial responses to your comments.

Thanks much for the review and I'll follow up with more detail in a
while.

>>>>> "Black," == Black, David <david.black@emc.com> writes:


    Black,> Major issues:

    Black,> (Section 2)

    Black,> [1] LocalKeyName and PeerKeyName are strings.  What
    Black,> character set?  If Unicode (e.g., UTF-8?), add text on
    Black,> Unicode considerations (e.g., normalization).  Finding a
    Black,> Unicode expert will help in getting this done quickly.  I
    Black,> have similar concerns for other strings, and in particular,
    Black,> IANA should be told what a "string" is for any registry
    Black,> field that contains one.

They are strings that can be compared using binary comparison.
I agree we need to state that in the draft.
Character set, to the extent it is specified will be specified by the
individual protocol.
In practice the protocol will say  that it's an integer represented as
an ASCII string.

We needed to add the entire complexity of making these fields be strings
    not integers because of some non-IETF protocols that use key names.

I'm reasonably confident I can sell Pete on the concept of a binary
    identifier for this field from an i18n standpoint.

But issues, of length, format, etc are all specified by the protocol
spec.

    Black,> [2] I'm not sure that I understand what a KDF really is from
    Black,> its high level description in this draft.  At the least, I'm
    Black,> surprised that the importance of non-invertibility of a KDF
    Black,> is not mentioned - beyond that, a functional description of
    Black,> inputs and outputs would help, including a strong
    Black,> recommendation to inject unpredictable nonce material.  This
    Black,> could be handled by referencing material on what a KDF is
    Black,> that exists elsewhere.

I'm open to text either proposed on the IETF list from one of the other
authors.
Some protocols have a KDF input some do not.
If they do, it will be drawn from a set of allowable valuable for that
protocol.

    Black,> (Section 4)

    Black,> [3] It's important that this section cover all the fields
    Black,> involved in the database lookups in Section 3 whose format
    Black,> may be protocol-specific (the Direction and various time
    Black,> fields aren't).  Protocol should be covered by the IANA
    Black,> registry, peers and key names are covered here, but
    Black,> interface appears to be missing - item (9) covers presence
    Black,> vs.  absence of interface information, but not its format.

The interface is implementation-specific not protocol specific.  We
mandate that you must be able to tie things to interface. However the
format of an interface is quite specific to the routing platform in
questino.  I don't think there's a way that an IETF document can go into
useful detail on that.  SNMP and Netconf have models of how interfaces
are represented.  If we ever put together a Netconf schema for this
database, we'd specify the interface there.

    Black,> --- Lots of issues with the IANA Considerations (Section 8)

    Black,> (Section 8.1.1)

    Black,> [5] No field format information for the fields in a registry
    Black,> entry.  IANA should be told what formats to expect/use.

Thanks, agreed.


    Black,> [6] "Protocol Specific Values" is not the same as
    Black,> "ProtocolSpecificInfo" in section 2; the same name should be
    Black,> used, but whitespace differences are ok.
Good catch.

    Black,> [7] Should some sort of formats for Peers and Interfaces be
    Black,> included in registering a Protocol?  If not, the lookups in
    Black,> section 3 may be implementation-dependent (strings that work
    Black,> w/one implementation may not work w/other implementations of
    Black,> the same protocol).  The specification reference may suffice
    Black,> based on the requirements in section 4 for what has to be in
    Black,> each referenced specification.

When you register a protocol you need to point to a specification that
    gives details on this sort of thing.

    Black,> (Sections 8.2 and 8.3)

    Black,> [8] No registry entry content descriptions.  Need to supply
    Black,> information on what to register and the formats of the
    Black,> elements of a registry entry.

Thanks.

    Black,> [9] I suggest Expert Review for these registries, not just
    Black,> First Come First Served, so that someone with a security
    Black,> "clue" can check that the proposed registrations are
    Black,> reasonable.

As an individual, I support FCFS, because I think getting expert
    approval for some of the uses that have been proposed for these
    registries will be challenging.



From adam@nostrum.com  Thu Apr 25 10:59:11 2013
Return-Path: <adam@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B5E21F96AB for <gen-art@ietfa.amsl.com>; Thu, 25 Apr 2013 10:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OrVDGnwHcmEo for <gen-art@ietfa.amsl.com>; Thu, 25 Apr 2013 10:59:10 -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 B8D3621F96AA for <gen-art@ietf.org>; Thu, 25 Apr 2013 10:59:10 -0700 (PDT)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3PHwW12095470 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 25 Apr 2013 12:58:33 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <51796EC8.3090508@nostrum.com>
Date: Thu, 25 Apr 2013 12:58:32 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Peter Saint-Andre <psaintan@cisco.com>
References: <5176EB42.3030501@dial.pipex.com> <BD017FC5-EE95-4ED6-9B52-2AAFA8ADDDD2@cisco.com>
In-Reply-To: <BD017FC5-EE95-4ED6-9B52-2AAFA8ADDDD2@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
Cc: fluffy@cisco.com, General Area Review Team <gen-art@ietf.org>, 'Paul Kyzivat' <pkyzivat@alum.mit.edu>, mary.barnes@nortel.com, draft-saintandre-impp-call-info.all@tools.ietf.org, Mary Barnes <mary.h.barnes@gmail.com>
Subject: Re: [Gen-art] Gen-art LC review of draft-saintandre-impp-call-info-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 17:59:11 -0000

On 4/24/13 09:19, Peter Saint-Andre wrote:
> Hi Elwyn, thanks for the review.
>
> On Apr 23, 2013, at 2:12 PM, Elwyn Davies wrote:
>> Generic comment about SIP Header Field Parameters registry: For the 
>> uninitiated this registry is rather opaque.  Some parameters, such as 
>> the Call-Info purpose parameter for which an extra value is defined 
>> here, have predefined values.  However the predefined values 
>> themselves are not in the registry and just giving a whole RFC 
>> reference for places where values are defined is not very helpful. 
>> For example, in the case of Call-Info, the initial predefined values 
>> of purpose are buried in the Call-Info rule in the ABNF in Section 
>> 25.1 of RFC 3261;  also, Section 20.9 describes the predefined values 
>> (such as "icon") as 'parameters' rather than values of 'purpose'.  It 
>> would probably be helpful to either improve the references in the 
>> registry table or actaully quote the possible predefined values in 
>> the table.
>>
>
> I agree, but as you say that's an issue with the SIP Header Field 
> Parameters registry in general. I started to go down the path of 
> fixing the registry as a whole, but I think I'd rather leave that for 
> 3261bis to tackle (sometime before the heat death of the universe).

Yes, the registry is a mess, largely due to the rather whimsical 
preferences -- which would vary from year to year -- of the SIP 
community regarding which fields needed a registry and which did not. 
It's grown to be the way it is somewhat organically, and I agree that 
the overall SIP registry is something of a mess.

I'm not sure we need to wait for a 3261bis to fix things, as I doubt we 
could find someone with the fortitude to take on an effort that large. 
It might be worth finding someone to work on a "registry overhaul" 
document that attempts to make the whole thing more coherent. I'll be 
keeping this in mind as a potential SIPCORE item.

/a

From david.black@emc.com  Thu Apr 25 11:50:01 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A70AE21F9647; Thu, 25 Apr 2013 11:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.24
X-Spam-Level: 
X-Spam-Status: No, score=-100.24 tagged_above=-999 required=5 tests=[AWL=2.359, 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 Wqiw+LVwUHSc; Thu, 25 Apr 2013 11:50:00 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 460C221F9644; Thu, 25 Apr 2013 11:49:59 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3PInX2v020434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Apr 2013 14:49:33 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 25 Apr 2013 14:49:21 -0400
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3PInKnE019433; Thu, 25 Apr 2013 14:49:20 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Thu, 25 Apr 2013 14:49:19 -0400
From: "Black, David" <david.black@emc.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 25 Apr 2013 14:49:17 -0400
Thread-Topic: Gen-ART review of draft-ietf-karp-crypto-key-table-07
Thread-Index: Ac5B1KJBGTDzkf65QPacxtWgnCr6KgADLoOg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293F3BDB0@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com> <tsla9omh811.fsf@mit.edu>
In-Reply-To: <tsla9omh811.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "gen-art@ietf.org" <gen-art@ietf.org>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "<stbryant@cisco.com>" <stbryant@cisco.com>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-karp-crypto-key-table-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 18:50:01 -0000

Thanks for the quick response - most of your message looks reasonable to me=
.

I have a few additional comments.

[1] Character set for key names, etc.

> They are strings that can be compared using binary comparison.
> I agree we need to state that in the draft.

That's certainly a reasonable goal, and there are plenty of examples of
protocols that do that.  OTOH, when the character set is Unicode, generatin=
g
strings for which that binary comparison for equality works as expected has
a number of subtleties when the strings are input by humans.  Pete Resnick
and yours truly are among the people familiar with the "dragons" that lurk
here (and the precis WG is grappling with).

> We needed to add the entire complexity of making these fields be strings
>     not integers because of some non-IETF protocols that use key names.
>=20
> I'm reasonably confident I can sell Pete on the concept of a binary
>     identifier for this field from an i18n standpoint.

I have no problem with the field being a binary identifier, but I think
implementers should be put on notice that binary comparison of human input
Unicode strings doesn't work as expected unless some things are done to
make it work (this used to be known as string preparation).  A warning
to that effect, perhaps citing a reference for details on what can go awry,
accompanied by making the protocol spec responsible for getting this right
ought to suffice.

[3] Protocol responsibility to specify interface format

> We
> mandate that you must be able to tie things to interface. However the
> format of an interface is quite specific to the routing platform in
> question.

Ok, I suggest explaining that as part of a statement that a protocol cannot
in general be expected to specify interface formats that apply across all
implementations due to implementation diversity.

[7] Additional format information in registry

>     Black,> [7] Should some sort of formats for Peers and Interfaces be
>     Black,> included in registering a Protocol?  If not, the lookups in
>     Black,> section 3 may be implementation-dependent (strings that work
>     Black,> w/one implementation may not work w/other implementations of
>     Black,> the same protocol).  The specification reference may suffice
>     Black,> based on the requirements in section 4 for what has to be in
>     Black,> each referenced specification.
>=20
> When you register a protocol you need to point to a specification that
>     gives details on this sort of thing.

That makes sense, and section 4's requirements on the specifications=20
cover this area, but I thought I'd ask.

[9] Registry policy

> As an individual, I support FCFS, because I think getting expert
>     approval for some of the uses that have been proposed for these
>     registries will be challenging.

The two registries involved are for KDFs and cryptographic algorithm identi=
fiers.

This feels like something that the security area ought to weigh in on, as i=
t
looks like it includes the "vanity crypto" discussion tarpit ;-).  At a min=
imum,
I would think that there ought to be some means of prohibiting registration
of a crypto algorithm like ROT13 (http://en.wikipedia.org/wiki/ROT13).

Thanks,
--David

> -----Original Message-----
> From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
> Sent: Thursday, April 25, 2013 12:47 PM
> To: Black, David
> Cc: Russ Housley; tim.polk@nist.gov; zhangdacheng@huawei.com; gen-
> art@ietf.org; karp@ietf.org; ietf@ietf.org; <stbryant@cisco.com>
> Subject: Re: Gen-ART review of draft-ietf-karp-crypto-key-table-07
>=20
> Here are some quick initial responses to your comments.
>=20
> Thanks much for the review and I'll follow up with more detail in a
> while.
>=20
> >>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
>=20
>=20
>     Black,> Major issues:
>=20
>     Black,> (Section 2)
>=20
>     Black,> [1] LocalKeyName and PeerKeyName are strings.  What
>     Black,> character set?  If Unicode (e.g., UTF-8?), add text on
>     Black,> Unicode considerations (e.g., normalization).  Finding a
>     Black,> Unicode expert will help in getting this done quickly.  I
>     Black,> have similar concerns for other strings, and in particular,
>     Black,> IANA should be told what a "string" is for any registry
>     Black,> field that contains one.
>=20
> They are strings that can be compared using binary comparison.
> I agree we need to state that in the draft.
> Character set, to the extent it is specified will be specified by the
> individual protocol.
> In practice the protocol will say  that it's an integer represented as
> an ASCII string.
>=20
> We needed to add the entire complexity of making these fields be strings
>     not integers because of some non-IETF protocols that use key names.
>=20
> I'm reasonably confident I can sell Pete on the concept of a binary
>     identifier for this field from an i18n standpoint.
>=20
> But issues, of length, format, etc are all specified by the protocol
> spec.
>=20
>     Black,> [2] I'm not sure that I understand what a KDF really is from
>     Black,> its high level description in this draft.  At the least, I'm
>     Black,> surprised that the importance of non-invertibility of a KDF
>     Black,> is not mentioned - beyond that, a functional description of
>     Black,> inputs and outputs would help, including a strong
>     Black,> recommendation to inject unpredictable nonce material.  This
>     Black,> could be handled by referencing material on what a KDF is
>     Black,> that exists elsewhere.
>=20
> I'm open to text either proposed on the IETF list from one of the other
> authors.
> Some protocols have a KDF input some do not.
> If they do, it will be drawn from a set of allowable valuable for that
> protocol.
>=20
>     Black,> (Section 4)
>=20
>     Black,> [3] It's important that this section cover all the fields
>     Black,> involved in the database lookups in Section 3 whose format
>     Black,> may be protocol-specific (the Direction and various time
>     Black,> fields aren't).  Protocol should be covered by the IANA
>     Black,> registry, peers and key names are covered here, but
>     Black,> interface appears to be missing - item (9) covers presence
>     Black,> vs.  absence of interface information, but not its format.
>=20
> The interface is implementation-specific not protocol specific.  We
> mandate that you must be able to tie things to interface. However the
> format of an interface is quite specific to the routing platform in
> questino.  I don't think there's a way that an IETF document can go into
> useful detail on that.  SNMP and Netconf have models of how interfaces
> are represented.  If we ever put together a Netconf schema for this
> database, we'd specify the interface there.
>=20
>     Black,> --- Lots of issues with the IANA Considerations (Section 8)
>=20
>     Black,> (Section 8.1.1)
>=20
>     Black,> [5] No field format information for the fields in a registry
>     Black,> entry.  IANA should be told what formats to expect/use.
>=20
> Thanks, agreed.
>=20
>=20
>     Black,> [6] "Protocol Specific Values" is not the same as
>     Black,> "ProtocolSpecificInfo" in section 2; the same name should be
>     Black,> used, but whitespace differences are ok.
> Good catch.
>=20
>     Black,> [7] Should some sort of formats for Peers and Interfaces be
>     Black,> included in registering a Protocol?  If not, the lookups in
>     Black,> section 3 may be implementation-dependent (strings that work
>     Black,> w/one implementation may not work w/other implementations of
>     Black,> the same protocol).  The specification reference may suffice
>     Black,> based on the requirements in section 4 for what has to be in
>     Black,> each referenced specification.
>=20
> When you register a protocol you need to point to a specification that
>     gives details on this sort of thing.
>=20
>     Black,> (Sections 8.2 and 8.3)
>=20
>     Black,> [8] No registry entry content descriptions.  Need to supply
>     Black,> information on what to register and the formats of the
>     Black,> elements of a registry entry.
>=20
> Thanks.
>=20
>     Black,> [9] I suggest Expert Review for these registries, not just
>     Black,> First Come First Served, so that someone with a security
>     Black,> "clue" can check that the proposed registrations are
>     Black,> reasonable.
>=20
> As an individual, I support FCFS, because I think getting expert
>     approval for some of the uses that have been proposed for these
>     registries will be challenging.
>=20
>=20


From hartmans@mit.edu  Thu Apr 25 12:04:18 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABDA21F8D2E; Thu, 25 Apr 2013 12:04:18 -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 1pFVlPU-ahta; Thu, 25 Apr 2013 12:04:17 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id CA9E821F8BC0; Thu, 25 Apr 2013 12:04:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 90DEE2021D; Thu, 25 Apr 2013 15:02:19 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yitGTgSfVmK3; Thu, 25 Apr 2013 15:02:18 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Thu, 25 Apr 2013 15:02:18 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id B935E4499; Thu, 25 Apr 2013 15:04:15 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com> <tsla9omh811.fsf@mit.edu> <8D3D17ACE214DC429325B2B98F3AE71293F3BDB0@MX15A.corp.emc.com>
Date: Thu, 25 Apr 2013 15:04:15 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293F3BDB0@MX15A.corp.emc.com> (David Black's message of "Thu, 25 Apr 2013 14:49:17 -0400")
Message-ID: <tsl61zah1ow.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "gen-art@ietf.org" <gen-art@ietf.org>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "<stbryant@cisco.com>" <stbryant@cisco.com>, Sam Hartman <hartmans-ietf@mit.edu>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-karp-crypto-key-table-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 19:04:18 -0000

>>>>> "Black," == Black, David <david.black@emc.com> writes:


I've been there too. I've had a number of recent discussinos with Pete
about what the IESG is and is not happy with .
I'll write something up and I'm sure he and the rest of the IESG will
let us know if we got it wrong:-)

From ben@nostrum.com  Thu Apr 25 13:40:00 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD1521F8DCF; Thu, 25 Apr 2013 13:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level: 
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[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 Uv0Ki38PpqU5; Thu, 25 Apr 2013 13:39:59 -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 7665121F8808; Thu, 25 Apr 2013 13:39:56 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3PKdsTU013628 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Apr 2013 15:39:55 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 25 Apr 2013 15:39:54 -0500
Message-Id: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com>
To: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 20:40:00 -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 resolve these comments along with any other Last Call comments
you may receive.

Document:  draft-ietf-6man-stable-privacy-addresses-06

Reviewer: Ben Campbell
Review Date: 2013-04-25
IETF LC End Date: 2013-04-16

Summary: This draft is almost ready for publication as a proposed =
standard. There are a few minor issues which should be considered first, =
described in the review.


Major issues:

None.

Minor issues:

-- section 3, third paragraph from end:

The paragraph suggests that changing the number of network interfaces =
should be rare. I think it's quite common in practice for the sorts of =
hosts likely to move between subnets regularly. For example, my Macbook =
Pro uses an external (Thunderbolt attached) ethernet interface which =
regularly gets disconnected and reconnected. Same might hold true for a =
USB attached wireless modem. And I have any number of VPNs which may be =
active or not at any given time.

-- section 3, 2nd paragraph from end:

You describe the affects of including Network_ID in some detail. It =
would be helpful to note the consequences of _not_ including it.

Nits/editorial comments:

-- section 1, 4th paragraph: "Therefore, it is vital..."

That seems a bit overstated. We're not talking about breaking the =
Internet here, are we?

-- 1, 6th paragraph: "Also, they result in increased complexity..."

What sort of complexity? Implementation complexity? It's a bit confusion =
because the previous sentences already talk about increased complexity =
of specific sorts. It would help to mention what sort of additional =
complexity is referred to here.

-- 1, paragraph 11: "This document does not update..."

How is adding an alternative algorithm _not_ an update?

--1, paragraph 12: "... may already address"

Is the "already addressing" part in question? Or is it a matter of =
addressing it in some circumstances, but not others? If the latter, it =
would help to elaborate.

-- 6, last paragraph: "... may mitigate..."

Not sure? Or only under some circumstances?

-- references:
 RFC1948 is obsoleted by 6528. Is there a reason to reference the =
obsolete version?


From mahoney@nostrum.com  Thu Apr 25 15:12:19 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEBEE21F9729 for <gen-art@ietfa.amsl.com>; Thu, 25 Apr 2013 15:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001]
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 6wXqMGayqr-a for <gen-art@ietfa.amsl.com>; Thu, 25 Apr 2013 15:12:18 -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 4903221F970D for <gen-art@ietf.org>; Thu, 25 Apr 2013 15:12:18 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.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 r3PMCGF0023869 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 25 Apr 2013 17:12:17 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <5179AA41.9060300@nostrum.com>
Date: Thu, 25 Apr 2013 17:12:17 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: gen-art@ietf.org
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)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-04-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 22:12:19 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Alexey Melnikov   2013-05-09   draft-ietf-6man-impatient-nud-06
  
Peter McCann      2013-05-03   draft-ietf-geopriv-relative-location-04

Peter Yee         2013-05-03   draft-ietf-netmod-ip-cfg-03 *

Roni Even         2013-05-03   draft-ietf-netmod-interfaces-cfg-10 *

Robert Sparks     2013-05-06   draft-ietf-dhc-triggered-reconfigure-05 *

Suresh Krishnan   2013-05-06   draft-ietf-geopriv-held-measurements-07

Vijay Gurbani     2013-05-06   draft-ietf-bmwg-imix-genome-04

Wassim Haddad     2013-05-08   draft-ietf-trill-fine-labeling-06 *

* On the 5/16 telechat


I have made the assignments in the review tool:
http://art.tools.ietf.org/tools/art/genart/

And the assignments are captured in the spreadsheets:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html


The standard template is included below.

Thanks,

Jean

-------------------------------------------------------------------

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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From fluffy@cisco.com  Thu Apr 25 16:09:40 2013
Return-Path: <fluffy@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FE0621F96D8 for <gen-art@ietfa.amsl.com>; Thu, 25 Apr 2013 16:09:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.3
X-Spam-Level: 
X-Spam-Status: No, score=-109.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 kcz1sTnNBpVY for <gen-art@ietfa.amsl.com>; Thu, 25 Apr 2013 16:09:39 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 4F58421F91A3 for <gen-art@ietf.org>; Thu, 25 Apr 2013 16:09:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2172; q=dns/txt; s=iport; t=1366931379; x=1368140979; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=GO/V9WAiEWL/osRh9EGY45+VsmA2i6/Mrr4suzHBbyk=; b=Ydqbv17az0LP+F7FNRNpnFnWye0YTLDWg+03lgM5MloKtvmDKD9DIMTr Y+VRRnWRieZsbFEspPKmdTizxT8WGB5w/MxJZILOSv8ShWfj5VFJomdvd 75yTPKYuMUwJK6WQZQ9zeE7BaCvzeKZDGNTZegEVj4lXamP0TZpxkHyUk o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAFO2eVGtJV2a/2dsb2JhbABRgwa+Z4EFFnSCHwEBAQMBeQULAgEIGAokMiUCBA4FCAyHega+W48CAjEHgm1hA4hZmFaHD4MOgig
X-IronPort-AV: E=Sophos;i="4.87,553,1363132800"; d="scan'208";a="203174775"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-2.cisco.com with ESMTP; 25 Apr 2013 23:09:39 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r3PN9cBf013709 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 25 Apr 2013 23:09:38 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.192]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Thu, 25 Apr 2013 18:09:38 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Adam Roach <adam@nostrum.com>
Thread-Topic: Gen-art LC review of draft-saintandre-impp-call-info-02
Thread-Index: AQHOQgn1mp8zjJa4yEKvMQ/z4Sseyg==
Date: Thu, 25 Apr 2013 23:09:37 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1134A0221@xmb-aln-x02.cisco.com>
References: <5176EB42.3030501@dial.pipex.com> <BD017FC5-EE95-4ED6-9B52-2AAFA8ADDDD2@cisco.com> <51796EC8.3090508@nostrum.com>
In-Reply-To: <51796EC8.3090508@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <915527B69695574AAA9A7CF688429296@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "Peter Saint-Andre \(psaintan\)" <psaintan@cisco.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "<mary.barnes@nortel.com>" <mary.barnes@nortel.com>, "<draft-saintandre-impp-call-info.all@tools.ietf.org>" <draft-saintandre-impp-call-info.all@tools.ietf.org>, Mary Barnes <mary.h.barnes@gmail.com>
Subject: Re: [Gen-art] Gen-art LC review of draft-saintandre-impp-call-info-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 23:09:40 -0000

On Apr 25, 2013, at 11:58 AM, Adam Roach <adam@nostrum.com> wrote:

> On 4/24/13 09:19, Peter Saint-Andre wrote:
>> Hi Elwyn, thanks for the review.
>>=20
>> On Apr 23, 2013, at 2:12 PM, Elwyn Davies wrote:
>>> Generic comment about SIP Header Field Parameters registry: For the uni=
nitiated this registry is rather opaque.  Some parameters, such as the Call=
-Info purpose parameter for which an extra value is defined here, have pred=
efined values.  However the predefined values themselves are not in the reg=
istry and just giving a whole RFC reference for places where values are def=
ined is not very helpful. For example, in the case of Call-Info, the initia=
l predefined values of purpose are buried in the Call-Info rule in the ABNF=
 in Section 25.1 of RFC 3261;  also, Section 20.9 describes the predefined =
values (such as "icon") as 'parameters' rather than values of 'purpose'.  I=
t would probably be helpful to either improve the references in the registr=
y table or actaully quote the possible predefined values in the table.
>>>=20
>>=20
>> I agree, but as you say that's an issue with the SIP Header Field Parame=
ters registry in general. I started to go down the path of fixing the regis=
try as a whole, but I think I'd rather leave that for 3261bis to tackle (so=
metime before the heat death of the universe).
>=20
> Yes, the registry is a mess, largely due to the rather whimsical preferen=
ces -- which would vary from year to year -- of the SIP community regarding=
 which fields needed a registry and which did not. It's grown to be the way=
 it is somewhat organically, and I agree that the overall SIP registry is s=
omething of a mess.
>=20
> I'm not sure we need to wait for a 3261bis to fix things, as I doubt we c=
ould find someone with the fortitude to take on an effort that large. It mi=
ght be worth finding someone to work on a "registry overhaul" document that=
 attempts to make the whole thing more coherent. I'll be keeping this in mi=
nd as a potential SIPCORE item.
>=20
> /a

+1

More importantly, I don't think this draft could reasonably take on cleanin=
g up that mess.=20



From fgont@si6networks.com  Thu Apr 25 16:43:12 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7947D21F973C; Thu, 25 Apr 2013 16:43:12 -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 1LuXdkHb+Veu; Thu, 25 Apr 2013 16:43:11 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 8ADF921F973A; Thu, 25 Apr 2013 16:43:11 -0700 (PDT)
Received: from [186.134.41.225] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UVVoY-00058p-Ta; Fri, 26 Apr 2013 01:42:59 +0200
Message-ID: <5179AEF1.2070306@si6networks.com>
Date: Thu, 25 Apr 2013 17:32:17 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
References: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com>
In-Reply-To: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 23:43:12 -0000

Hi, Ben,

Thanks so much for your feedback! Please find my comments in-line...

On 04/25/2013 03:39 PM, Ben Campbell wrote:
> Minor issues:
> 
> -- section 3, third paragraph from end:
> 
> The paragraph suggests that changing the number of network interfaces
> should be rare. I think it's quite common in practice for the sorts
> of hosts likely to move between subnets regularly. For example, my
> Macbook Pro uses an external (Thunderbolt attached) ethernet
> interface which regularly gets disconnected and reconnected. Same
> might hold true for a USB attached wireless modem. And I have any
> number of VPNs which may be active or not at any given time.

I will tweak the text a bit -- as noted in other threads, I will replace
"Interface Index" with a generic "Interface_ID", and will comment on the
desired properties, and note that two possible options for it are the
Interface Index and the Interface name -- with the interface name
probably being more constant in the scenarios that you describe.



> -- section 3, 2nd paragraph from end:
> 
> You describe the affects of including Network_ID in some detail. It
> would be helpful to note the consequences of _not_ including it.

Well, should we really do it? -- after all, you MUST include it.

> 
> Nits/editorial comments:
> 
> -- section 1, 4th paragraph: "Therefore, it is vital..."
> 
> That seems a bit overstated. We're not talking about breaking the
> Internet here, are we?

Well, that depends... there are scenarios in which privacy is really vital.



> -- 1, 6th paragraph: "Also, they result in increased complexity..."
> 
> What sort of complexity? Implementation complexity? It's a bit
> confusion because the previous sentences already talk about increased
> complexity of specific sorts. It would help to mention what sort of
> additional complexity is referred to here.

Yep, implementation complexity -- I will clarify this.



> -- 1, paragraph 11: "This document does not update..."
> 
> How is adding an alternative algorithm _not_ an update?

Well, you still send an RS, receive an RA, and generate an IID.

Me, I'd probably update RFC 4862, so that we make sure that folks
implementing SLAAC take a look at this document, but....



> --1, paragraph 12: "... may already address"
> 
> Is the "already addressing" part in question? Or is it a matter of
> addressing it in some circumstances, but not others? If the latter,
> it would help to elaborate.

Not sure what you mean. The idea is that, in many scenarios,
draft-ietf-stable-privacy-addresses may be good enough to address your
privacy concerns.



> -- 6, last paragraph: "... may mitigate..."
> 
> Not sure? Or only under some circumstances?

The idea is that the only privacy implication that this doesn't mitigate
is correlation of node activities within the same network.
However, that really depends on the number of active nodes within the
same subnet. For example, if you have only one active node in the
subnet, then no matter whether its changes its addresses, its activities
can be easily correlated.



> -- references: RFC1948 is obsoleted by 6528. Is there a reason to
> reference the obsolete version?

Yes: RFC1948 is only referenced in the Acks section, where I note that
this document was inspired by Bellovin's work on RFC1948. While RFC6528
obsoletes RFC1948, the algorithm in that RFC is the same as that in RFC1948.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From ben@nostrum.com  Thu Apr 25 17:44:25 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A039821F9728; Thu, 25 Apr 2013 17:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.301
X-Spam-Level: 
X-Spam-Status: No, score=-101.301 tagged_above=-999 required=5 tests=[AWL=1.300, 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 KIAf-rEO955Z; Thu, 25 Apr 2013 17:44:24 -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 B7F4021F92C0; Thu, 25 Apr 2013 17:44:24 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3Q0iM8o040262 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Apr 2013 19:44:22 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <5179AEF1.2070306@si6networks.com>
Date: Thu, 25 Apr 2013 19:44:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com>
References: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com> <5179AEF1.2070306@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 00:44:25 -0000

On Apr 25, 2013, at 5:32 PM, Fernando Gont <fgont@si6networks.com> =
wrote:

> Hi, Ben,
>=20
> Thanks so much for your feedback! Please find my comments in-line...
>=20
> On 04/25/2013 03:39 PM, Ben Campbell wrote:
>> Minor issues:
>>=20
>> -- section 3, third paragraph from end:
>>=20
>> The paragraph suggests that changing the number of network interfaces
>> should be rare. I think it's quite common in practice for the sorts
>> of hosts likely to move between subnets regularly. For example, my
>> Macbook Pro uses an external (Thunderbolt attached) ethernet
>> interface which regularly gets disconnected and reconnected. Same
>> might hold true for a USB attached wireless modem. And I have any
>> number of VPNs which may be active or not at any given time.
>=20
> I will tweak the text a bit -- as noted in other threads, I will =
replace
> "Interface Index" with a generic "Interface_ID", and will comment on =
the
> desired properties, and note that two possible options for it are the
> Interface Index and the Interface name -- with the interface name
> probably being more constant in the scenarios that you describe.
>=20

Works for me.

>=20
>=20
>> -- section 3, 2nd paragraph from end:
>>=20
>> You describe the affects of including Network_ID in some detail. It
>> would be helpful to note the consequences of _not_ including it.
>=20
> Well, should we really do it? -- after all, you MUST include it.

Hmm. Section 3 says Network_ID is optional.


>=20
>>=20
>> Nits/editorial comments:
>>=20
>> -- section 1, 4th paragraph: "Therefore, it is vital..."
>>=20
>> That seems a bit overstated. We're not talking about breaking the
>> Internet here, are we?
>=20
> Well, that depends... there are scenarios in which privacy is really =
vital.

It's not a big deal, really, but it might be worth mentioning the =
context in which it's "vital". Or maybe tone it down to merely =
"important" :-)

[...]

>=20
>=20
>=20
>> -- 1, paragraph 11: "This document does not update..."
>>=20
>> How is adding an alternative algorithm _not_ an update?
>=20
> Well, you still send an RS, receive an RA, and generate an IID.
>=20
> Me, I'd probably update RFC 4862, so that we make sure that folks
> implementing SLAAC take a look at this document, but....
>=20

...?

(The reason you mention is one of the best reasons I can think of to =
call it an update--but if the working group consciously chose not to =
make it an update, I can live with it.)


>=20
>> --1, paragraph 12: "... may already address"
>>=20
>> Is the "already addressing" part in question? Or is it a matter of
>> addressing it in some circumstances, but not others? If the latter,
>> it would help to elaborate.
>=20
> Not sure what you mean. The idea is that, in many scenarios,
> draft-ietf-stable-privacy-addresses may be good enough to address your
> privacy concerns.

The way it's worded, it looks like you think it might address the =
concerns, but aren't sure. I doubt that's the intent. Simply saying "may =
address certain privacy concerns", or "in some circumstances, will =
address...". OTOH, elaborating on the specific concerns addressed would =
be even better. Do you mean to say it addresses the concerns already =
mentioned in this draft? If so, you could use language stronger than =
"may".

Your answer to my next comment is instructive for this as well.


>=20
>=20
>=20
>> -- 6, last paragraph: "... may mitigate..."
>>=20
>> Not sure? Or only under some circumstances?
>=20
> The idea is that the only privacy implication that this doesn't =
mitigate
> is correlation of node activities within the same network.
> However, that really depends on the number of active nodes within the
> same subnet. For example, if you have only one active node in the
> subnet, then no matter whether its changes its addresses, its =
activities
> can be easily correlated.
>=20

Saying that would be helpful.

>=20
>=20
>> -- references: RFC1948 is obsoleted by 6528. Is there a reason to
>> reference the obsolete version?
>=20
> Yes: RFC1948 is only referenced in the Acks section, where I note that
> this document was inspired by Bellovin's work on RFC1948. While =
RFC6528
> obsoletes RFC1948, the algorithm in that RFC is the same as that in =
RFC1948.

So 6528 equally illustrates Steve Bellovin's  work, and is also more =
current, right? If someone decided to follow up to better understand =
your inspiration, which draft would you prefer them to read?

Thanks!

Ben.



From ben@nostrum.com  Thu Apr 25 17:51:56 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCC1921F970F; Thu, 25 Apr 2013 17:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.95
X-Spam-Level: 
X-Spam-Status: No, score=-101.95 tagged_above=-999 required=5 tests=[AWL=0.650, 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 mQsS9RGtKOKt; Thu, 25 Apr 2013 17:51:54 -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 D02D721F96C5; Thu, 25 Apr 2013 17:51:52 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3Q0ppVF040997 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Apr 2013 19:51:52 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com>
Date: Thu, 25 Apr 2013 19:51:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E494549B-DCB0-42CD-99DD-6F11B20756D5@nostrum.com>
References: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com> <5179AEF1.2070306@si6networks.com> <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 00:51:56 -0000

On Apr 25, 2013, at 7:44 PM, Ben Campbell <ben@nostrum.com> wrote:

> So 6528 equally illustrates Steve Bellovin's  work, and is also more =
current, right? If someone decided to follow up to better understand =
your inspiration, which draft would you prefer them to read?

oops, s/draft/version.




From fgont@si6networks.com  Thu Apr 25 18:12:51 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2619A21F976E; Thu, 25 Apr 2013 18:12:51 -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 Kgrl8DTN7PQi; Thu, 25 Apr 2013 18:12:50 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 5606E21F976D; Thu, 25 Apr 2013 18:12:49 -0700 (PDT)
Received: from [186.134.41.225] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UVXDJ-0007Fm-6X; Fri, 26 Apr 2013 03:12:37 +0200
Message-ID: <5179D47A.2090202@si6networks.com>
Date: Thu, 25 Apr 2013 22:12:26 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
References: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com> <5179AEF1.2070306@si6networks.com> <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com>
In-Reply-To: <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 01:12:51 -0000

Hi, Ben,

On 04/25/2013 09:44 PM, Ben Campbell wrote:
>>> -- section 3, 2nd paragraph from end:
>>> 
>>> You describe the affects of including Network_ID in some detail. 
>>> It would be helpful to note the consequences of _not_ including 
>>> it.
>> 
>> Well, should we really do it? -- after all, you MUST include it.
> 
> Hmm. Section 3 says Network_ID is optional.

Ooops, sorry -- you're right! I was thinking about the prefix, rather
than the Network_ID. I will address this in the next rev.



>>> -- 1, paragraph 11: "This document does not update..."
>>> 
>>> How is adding an alternative algorithm _not_ an update?
>> 
>> Well, you still send an RS, receive an RA, and generate an IID.
>> 
>> Me, I'd probably update RFC 4862, so that we make sure that folks 
>> implementing SLAAC take a look at this document, but....
> 
> ...?
> 
> (The reason you mention is one of the best reasons I can think of to 
> call it an update--but if the working group consciously chose not to 
> make it an update, I can live with it.)

I'm not sure whether this was "consciously chosen" -- I will check with
a few folks about their thoughts (for the most part, I wouldn't want to
trigger a controversy just because of this).



>>> --1, paragraph 12: "... may already address"
>>> 
>>> Is the "already addressing" part in question? Or is it a matter 
>>> of addressing it in some circumstances, but not others? If the 
>>> latter, it would help to elaborate.
>> 
>> Not sure what you mean. The idea is that, in many scenarios, 
>> draft-ietf-stable-privacy-addresses may be good enough to address 
>> your privacy concerns.
> 
> The way it's worded, it looks like you think it might address the 
> concerns, but aren't sure. I doubt that's the intent. Simply saying 
> "may address certain privacy concerns", or "in some circumstances, 
> will address...". OTOH, elaborating on the specific concerns 
> addressed would be even better. Do you mean to say it addresses the 
> concerns already mentioned in this draft? If so, you could use 
> language stronger than "may".
> 
> Your answer to my next comment is instructive for this as well.

Ok, I will add some text about this.



>>> -- references: RFC1948 is obsoleted by 6528. Is there a reason to
>>> reference the obsolete version?
>> 
>> Yes: RFC1948 is only referenced in the Acks section, where I note 
>> that this document was inspired by Bellovin's work on RFC1948. 
>> While RFC6528 obsoletes RFC1948, the algorithm in that RFC is the 
>> same as that in RFC1948.
> 
> So 6528 equally illustrates Steve Bellovin's  work, and is also more 
> current, right? 

Yes. But I'm a co-author of RFC 6528 -- so it'd be a bit arrogant (and
incorrect) to say that I was inspired by RFC 6528 :-) -- I was inspired
by Bellovin, rather than myself. :-)

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From ben@nostrum.com  Thu Apr 25 20:13:15 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E12A21F97B7; Thu, 25 Apr 2013 20:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.167
X-Spam-Level: 
X-Spam-Status: No, score=-102.167 tagged_above=-999 required=5 tests=[AWL=0.433, 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 u8AipqpzjSsc; Thu, 25 Apr 2013 20:13:14 -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 9F31B21F8E87; Thu, 25 Apr 2013 20:13:14 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3Q3D7Fx056834 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Apr 2013 22:13:08 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <5179D47A.2090202@si6networks.com>
Date: Thu, 25 Apr 2013 22:13:06 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <72639A54-C153-4799-B49A-6FAD338205BC@nostrum.com>
References: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com> <5179AEF1.2070306@si6networks.com> <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com> <5179D47A.2090202@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 03:13:15 -0000

Hi, deleting sections that seem resolved:

On Apr 25, 2013, at 8:12 PM, Fernando Gont <fgont@si6networks.com> wrote:

[...]

> 
> 
>>>> -- 1, paragraph 11: "This document does not update..."
>>>> 
>>>> How is adding an alternative algorithm _not_ an update?
>>> 
>>> Well, you still send an RS, receive an RA, and generate an IID.
>>> 
>>> Me, I'd probably update RFC 4862, so that we make sure that folks 
>>> implementing SLAAC take a look at this document, but....
>> 
>> ...?
>> 
>> (The reason you mention is one of the best reasons I can think of to 
>> call it an update--but if the working group consciously chose not to 
>> make it an update, I can live with it.)
> 
> I'm not sure whether this was "consciously chosen" -- I will check with
> a few folks about their thoughts (for the most part, I wouldn't want to
> trigger a controversy just because of this).
> 
> 

Point taken.

[...]

> 
> 
>>>> -- references: RFC1948 is obsoleted by 6528. Is there a reason to
>>>> reference the obsolete version?
>>> 
>>> Yes: RFC1948 is only referenced in the Acks section, where I note 
>>> that this document was inspired by Bellovin's work on RFC1948. 
>>> While RFC6528 obsoletes RFC1948, the algorithm in that RFC is the 
>>> same as that in RFC1948.
>> 
>> So 6528 equally illustrates Steve Bellovin's  work, and is also more 
>> current, right? 
> 
> Yes. But I'm a co-author of RFC 6528 -- so it'd be a bit arrogant (and
> incorrect) to say that I was inspired by RFC 6528 :-) -- I was inspired
> by Bellovin, rather than myself. :-)
> 

Ah, I see your point :-)



From vkg@bell-labs.com  Fri Apr 26 07:35:40 2013
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E57E21F99AB; Fri, 26 Apr 2013 07:35:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 Yz0AWH0AsKpR; Fri, 26 Apr 2013 07:35:39 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 5844921F95D0; Fri, 26 Apr 2013 07:35:39 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r3QEZXvc008478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 26 Apr 2013 09:35:34 -0500 (CDT)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r3QEZXA4017364 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 26 Apr 2013 09:35:33 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r3QEZWp5001323; Fri, 26 Apr 2013 09:35:33 -0500 (CDT)
Message-ID: <517A9179.1040805@bell-labs.com>
Date: Fri, 26 Apr 2013 09:38:49 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130311 Thunderbird/17.0.4
MIME-Version: 1.0
To: draft-ietf-bmwg-imix-genome@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: Joel Jaeggli <joelja@bogus.com>, General Area Review Team <gen-art@ietf.org>, IESG IESG <iesg@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-bmwg-imix-genome-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 14:35:40 -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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-bmwg-imix-genome-04
Reviewer: Vijay K. Gurbani
Review Date: Apr-26-2013
IETF LC End Date: May-06-2013
IESG Telechat date: May-30-2013

This document is ready as an Informational.  A couple of minor comments
that can benefit the draft below.

Major: 0
Minor: 2
Nits: 0

Minor:

- S1, 4th paragraph: "An IMIX suited for one networking device and
  deployment will not be appropriate for another."  I suspect the
  variability of the packet sizes has to do with the vendor whose device
  is being benchmarked.  In other words, a constant, K, used as a packet
  size by Vendor A does not mean that K can be used while benchmarking a
  device by Vendor B.  If so, it may be helpful to augment the quoted
  sentence above by the phrase "because packet sizes differ across
  different vendor devices."

- S3, "o  Non-RFC2544 packet sizes ... in the table." --- Is this not
  already covered in S4 (Custom IMIX)?  When I read the quoted bullet
  item, I immediately thought of some sort of an encoding scheme to
  encode non standard packet sizes, which is what S4 does.  Maybe I
  am missing something?

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq

From rjsparks@nostrum.com  Fri Apr 26 08:42:11 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3560B21F9A16; Fri, 26 Apr 2013 08:42:11 -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, 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 zmrnO4NroEmx; Fri, 26 Apr 2013 08:42:10 -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 70EF521F9A0C; Fri, 26 Apr 2013 08:42:10 -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 r3QFg80u049436 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Fri, 26 Apr 2013 10:42:09 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <517AA051.8080506@nostrum.com>
Date: Fri, 26 Apr 2013 10:42:09 -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: dhcwg@ietf.org, ietf@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
Content-Type: multipart/alternative; boundary="------------050301090000090703000601"
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Subject: [Gen-art] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 15:42:11 -0000

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

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-dhc-triggered-reconfigure-05
Reviewer: Robert Sparks
Review Date: April 26, 2013
IETF LC End Date: May 6, 2013
IESG Telechat date: May 16, 2013

Summary: This draft is on the right track but has open issues, described in
       the review.

Major issues:

Overall, this document is solid, but I think there is a bug in section 6.3.
I could be wrong, but If I'm right, this paragraph:

    When retransmission is required, the relay may decide to correct the
    content of RECONFIGURE-REQUEST message it issues (e.g., update the
    Client Identifier list).  This decision is local to the relay (e.g.,
    it may be based on observed events such as one or more clients were
    reconfigured on their own).


introduces a race-condition that could lead to an erroneous state. If a 
relay's first message included client A, then the retransmission 
included clients A and B, but that retransmission crosses with a success 
RECONFIGURE-REPLY to the request that only included client A, the relay 
will think it succeeded in asking A and B to be reconfigured.

Minor issues:

This sentence:

    Furthermore, means to recover state in failure events must be
    supported, but are not discussed in this document.

places a requirement on a relay (even though it's not using a 2119 
MUST). Is there some other document that defines this requirement that 
you can reference? If not, the requirement should be discussed in this 
document. Alternatively, you could change the sentence to talk about the 
consequences of not having a proprietary means for recovering state.

Nits/editorial comments:

--------------050301090000090703000601
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">
    I am the assigned Gen-ART reviewer for this draft. For background on
    <br>
    Gen-ART, please see the FAQ at
    <br>
    <br>
    <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>.
    <br>
    <br>
    Please resolve these comments along with any other Last Call
    comments
    <br>
    you may receive.
    <br>
    <br>
    Document:
    draft-ietf-dhc-triggered-reconfigure-05<br>
    Reviewer:&nbsp;
    Robert Sparks<br>
    Review Date: April 26, 2013<br>
    IETF LC End Date:
    May 6, 2013<br>
    IESG Telechat date: May 16, 2013<br>
    <br>
    Summary:
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    This draft is on the right track but has open issues, described in<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the review.<br>
    <br>
    Major issues:
    <br>
    <br>
    Overall, this document is solid, but I think there is a bug in
    section 6.3. <br>
    I could be wrong, but If I'm right, this paragraph:<br>
    <br>
    <blockquote>When retransmission is required, the relay may decide to
      correct the content of RECONFIGURE-REQUEST message it issues
      (e.g., update the Client Identifier list).&nbsp; This decision is local
      to the relay (e.g., it may be based on observed events such as one
      or more clients were reconfigured on their own).<br>
    </blockquote>
    <br>
    introduces a race-condition that could lead to an erroneous state.
    If a relay's first message included client A, then the
    retransmission included clients A and B, but that retransmission
    crosses with a success RECONFIGURE-REPLY to the request that only
    included client A, the relay will think it succeeded in asking A and
    B to be reconfigured.<br>
    <br>
    Minor issues:
    <br>
    <br>
    This sentence:<br>
    <br>
    <blockquote>Furthermore, means to recover state in failure events
      must be supported, but are not discussed in this document.<br>
    </blockquote>
    places a requirement on a relay (even though it's not using a 2119
    MUST). Is there some other document that defines this requirement
    that you can reference? If not, the requirement should be discussed
    in this document. Alternatively, you could change the sentence to
    talk about the consequences of not having a proprietary means for
    recovering state.<br>
    <br>
    Nits/editorial comments:
  </body>
</html>

--------------050301090000090703000601--

From mohamed.boucadair@orange.com  Fri Apr 26 09:02:47 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9967721F9A5D; Fri, 26 Apr 2013 09:02:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.948
X-Spam-Level: 
X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 Hr8Zjd1yoUAg; Fri, 26 Apr 2013 09:02:47 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id C5E9221F9A5B; Fri, 26 Apr 2013 09:02:46 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 8D0832645A1; Fri, 26 Apr 2013 18:02:45 +0200 (CEST)
Received: from puexch91.nanterre.francetelecom.fr (unknown [10.101.44.48]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 69E8535C048; Fri, 26 Apr 2013 18:02:45 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by puexch91.nanterre.francetelecom.fr ([10.101.44.48]) with mapi; Fri, 26 Apr 2013 18:02:45 +0200
From: <mohamed.boucadair@orange.com>
To: Robert Sparks <rjsparks@nostrum.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>,  "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>
Date: Fri, 26 Apr 2013 17:58:38 +0200
Thread-Topic: [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Index: Ac5ClKF6HmqJ6RojQf+w5CK04H/aHwAAkkJb
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr>
References: <517AA051.8080506@nostrum.com>
In-Reply-To: <517AA051.8080506@nostrum.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.4.25.35414
Subject: [Gen-art] RE : [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 16:02:47 -0000

Dear Robert,

Thank you for the review.
Please see inline.

Cheers,
Med
________________________________________
De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de Robert S=
parks [rjsparks@nostrum.com]
Date d'envoi : vendredi 26 avril 2013 17:42
=C0 : dhcwg@ietf.org; ietf@ietf.org; General Area Review Team; draft-ietf-d=
hc-triggered-reconfigure@tools.ietf.org
Objet : [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05

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><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-dhc-triggered-reconfigure-05
Reviewer:  Robert Sparks
Review Date: April 26, 2013
IETF LC End Date: May 6, 2013
IESG Telechat date: May 16, 2013

Summary: This draft is on the right track but has open issues, described in
      the review.

Major issues:

Overall, this document is solid, but I think there is a bug in section 6.3.
I could be wrong, but If I'm right, this paragraph:

When retransmission is required, the relay may decide to correct the conten=
t of RECONFIGURE-REQUEST message it issues (e.g., update the Client Identif=
ier list).  This decision is local to the relay (e.g., it may be based on o=
bserved events such as one or more clients were reconfigured on their own).

introduces a race-condition that could lead to an erroneous state. If a rel=
ay's first message included client A, then the retransmission included clie=
nts A and B, but that retransmission crosses with a success RECONFIGURE-REP=
LY to the request that only included client A, the relay will think it succ=
eeded in asking A and B to be reconfigured.

Med: This example does not apply for that text. In fact, the example should=
 be the other way around. Perhaps, this can be made clearer if we change "(=
e.g., update the Client Identifier list)" to "(e.g., remove a client from t=
he Client Identifier list)".

Minor issues:

This sentence:

Furthermore, means to recover state in failure events must be supported, bu=
t are not discussed in this document.
places a requirement on a relay (even though it's not using a 2119 MUST). I=
s there some other document that defines this requirement that you can refe=
rence?

Med: I'm not aware of any; but if there is one we can cite it.

 If not, the requirement should be discussed in this document. Alternativel=
y, you could change the sentence to talk about the consequences of not havi=
ng a proprietary means for recovering state.

Med: Will consider that option if you think this is really needed.

Nits/editorial comments:

From rjsparks@nostrum.com  Fri Apr 26 09:19:31 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B1B721F9987; Fri, 26 Apr 2013 09:19:31 -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, 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 p94gESGCTazx; Fri, 26 Apr 2013 09:19:30 -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 CCEAA21F9878; Fri, 26 Apr 2013 09:19: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 r3QGJTZr054170 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Fri, 26 Apr 2013 11:19:29 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <517AA910.8030608@nostrum.com>
Date: Fri, 26 Apr 2013 11:19:28 -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: mohamed.boucadair@orange.com
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>
Subject: Re: [Gen-art] RE : [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 16:19:31 -0000

On 4/26/13 10:58 AM, mohamed.boucadair@orange.com wrote:
> Dear Robert,
>
> Thank you for the review.
> Please see inline.
>
> Cheers,
> Med
> ________________________________________
> De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de Robert Sparks [rjsparks@nostrum.com]
> Date d'envoi : vendredi 26 avril 2013 17:42
> Ŕ : dhcwg@ietf.org; ietf@ietf.org; General Area Review Team; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
> Objet : [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
>
> 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><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-dhc-triggered-reconfigure-05
> Reviewer:  Robert Sparks
> Review Date: April 26, 2013
> IETF LC End Date: May 6, 2013
> IESG Telechat date: May 16, 2013
>
> Summary: This draft is on the right track but has open issues, described in
>        the review.
>
> Major issues:
>
> Overall, this document is solid, but I think there is a bug in section 6.3.
> I could be wrong, but If I'm right, this paragraph:
>
> When retransmission is required, the relay may decide to correct the content of RECONFIGURE-REQUEST message it issues (e.g., update the Client Identifier list).  This decision is local to the relay (e.g., it may be based on observed events such as one or more clients were reconfigured on their own).
>
> introduces a race-condition that could lead to an erroneous state. If a relay's first message included client A, then the retransmission included clients A and B, but that retransmission crosses with a success RECONFIGURE-REPLY to the request that only included client A, the relay will think it succeeded in asking A and B to be reconfigured.
>
> Med: This example does not apply for that text.
Really? What text constrains how you change what's in the retransmission?
>   In fact, the example should be the other way around. Perhaps, this can be made clearer if we change "(e.g., update the Client Identifier list)" to "(e.g., remove a client from the Client Identifier list)".
If I understand you correctly, you need more than just changing a 
parenthetical e.g.. I think you're saying that you are constraining the 
message changes to be such that if anything earlier in the 
retransmission sequence succeeded, the request in the retransmission 
would also have succeeded. But why do you need that much complexity? Do 
you have it already with any other request?
>
> Minor issues:
>
> This sentence:
>
> Furthermore, means to recover state in failure events must be supported, but are not discussed in this document.
> places a requirement on a relay (even though it's not using a 2119 MUST). Is there some other document that defines this requirement that you can reference?
>
> Med: I'm not aware of any; but if there is one we can cite it.
>
>   If not, the requirement should be discussed in this document. Alternatively, you could change the sentence to talk about the consequences of not having a proprietary means for recovering state.
>
> Med: Will consider that option if you think this is really needed.
>
> Nits/editorial comments:


From stbryant@cisco.com  Fri Apr 26 10:44:23 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB3121F9841 for <gen-art@ietfa.amsl.com>; Fri, 26 Apr 2013 10:44:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 k8f+Xn9wIkmt for <gen-art@ietfa.amsl.com>; Fri, 26 Apr 2013 10:44:22 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 58D0621F95EE for <gen-art@ietf.org>; Fri, 26 Apr 2013 10:44:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19052; q=dns/txt; s=iport; t=1366998261; x=1368207861; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=WnALQ6KjODEQxO1l5v91EGPQ+q6LRoAQJ5xvD+MLkVg=; b=YxmH3VsShFx+M5l5Fr9syKWdFTR3Ga0U2mVNLtAPqkr0xEd2iUxflCZC 7MyQ6RQEpxDb1uRk1GD/kqAY2iS72P5y5/JsbKNsviIxnWfooqN3zjQp3 t9Fvj7GmWDnKm1ehoqbo54gyzy2oE3OgHd4+cjIwGmmtF+g4i6V+6L9yD 0=;
X-IronPort-AV: E=Sophos;i="4.87,559,1363132800"; d="scan'208,217";a="82239975"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 26 Apr 2013 17:44:20 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3QHiIvM000411 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Apr 2013 17:44:18 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r3QHiHix004724; Fri, 26 Apr 2013 18:44:17 +0100 (BST)
Message-ID: <517ABCF0.2080701@cisco.com>
Date: Fri, 26 Apr 2013 18:44:16 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <CABkgnnW-53MVHZaW4QweqBjrPGCrP=fCNQ+LJdaG__ePh2tn1A@mail.gmail.com> <CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com>
In-Reply-To: <CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------050306080307000809070800"
Cc: "Bocci, Matthew \(Matthew\)" <matthew.bocci@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, danfrost@cisco.com, draft-ietf-mpls-gach-adv.all@tools.ietf.org, sec-ads@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-gach-adv-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 17:44:23 -0000

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

Including Sec ADs as this involves a change to the Authentication section.

Section 6.3 now says

The HMAC proceedure described in [RFC2104] is used to compute the hash.
The hash is computed over the entire GAP message as shown in Fig1.
The length of the Authentication Data field is always less than or equal
to the message digest size of the specific hash function that is being
used, however the implementer needs to consider that although this
decreases the size of the message, it results in a corresponding
reduction in the strength of the assurance provided.
Hash truncation is not RECOMMENDED.

I will address any other security issues in another editing pass and
respond to their Discuss email.


On 10/03/2013 17:52, Martin Thomson wrote:
> I sent the following review a few weeks back.  I just wanted to make 
> sure that it didn't get accidentally stored in /dev/null.
>
>
> On 15 February 2013 14:33, Martin Thomson <martin.thomson@gmail.com 
> <mailto:martin.thomson@gmail.com>> wrote:
>
>     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-mpls-gach-adv-06
>     Reviewer: Martin Thomson
>     Review Date: 2013-02-15
>     IETF LC End Date: 2013-02-27
>     IESG Telechat date: (if known)
>
>     Summary: The document is almost ready for publication as proposed
>     standard.  There is a major issue that should be easy to resolve.
>
>     Major issues:
>
>     Section 6.3 duplicates the description of HMAC provided in RFC 2104.
>     That is likely to cause a bug.
>
>     If you reference RFC 2104, then the only requirement is a clear
>     specification for what message is input to the HMAC.  Currently, this
>     is buried.  It is unclear if the input includes the G-ACh header
>     defined in RFC 5586 (it doesn't need to, but this needs to be made
>     explicit).
>
>     Filling the authentication part with 0x878FE1F3 seems unnecessary busy
>     work, but it's harmless as long as the hash function produces a
>     multiple of 32 bits of output.
>

All done please see above.
>
>
>     Minor issues:
>
>     To avoid forward compatibility issues, reserved fields should come
>     with guidance that says: "Implementations of this protocol version
>     MUST set reserved fields to all zero bits when sending and ignore any
>     value when receiving messages."
>
The following was added just before Fig 1

Implementations of this protocol version MUST set reserved fields in the
message formats that follow, to all zero bits when sending and ignore
any value when receiving messages.

I feel that we should just write an update to RFC2119 to automatically
include this or add it to the standard boiler plate.



>     In Section 4.4, how does the duration interact with the lifetime?
>     What happens when the duration is longer than lifetime such that the
>     TLV is expunged before the duration is up?
>
The TLV would be deleted (per procedure) at its death date, and
would not be sent again until at least duration has expired. This would
be silly if the receiver wanted that TLV, but entirely reasonable
if it dis not care about the TLV.

>
>     Section 5.2 states:
>        [...] If one
>        of the received TLV objects has the same Type as a previously
>        received TLV then the data from the new object SHALL replace
>     the data
>        associated with that Type unless the X specification dictates a
>        different behavior.
>
>     This leads to different retention characteristics depending on some
>     arbitrary application-specific requirements.  It also complicates
>     implementations.  Is there a strong motivation for the "unless the X
>     specification dictates a different behavior" part of this statement?
>
One can imagine alternative behaviors such as maintaining a list of
received values. Our goal was not to prejudge the application.

>
>     If this behaviour is desirable, a note regarding what happens to the
>     composed TLV when some of the values that contribute to it might
>     expire might be necessary.
>
The behaviour described is the action of the data and not of the TLV that
it arrived in, so I don't think the problem you refer to can occur.

>
>     Regarding the last paragraph of Section 6.3:
>               This also means that the use of hash functions with larger
>               output sizes will increase the size of the GAP message as
>               transmitted on the wire.
>
>     If you want to prevent hash truncation, then use 'MUST'.  Personally,
>     I see no reason to do so.  It's a good way to get smaller messages,
>     with a corresponding reduction in the strength of the assurance
>     provided.
>
Please see new text above.

>
>     Nits:
>
>     Section 3 could use some subheadings to aid navigation (and
>     referencing).
>
Done
>
>     Section 3 describes the size of fields only through ASCII-art.  It's a
>     fairly simple thing to add a bit count to the description of each
>     field.  That includes the reserved fields, which have no descriptions.
>
Done
>
>
>     I like the text in the editors note on page 8.  Why is it not the
>     actual text already?
>
That was a hang over from AD review that was already addressed in the
text. The note has been removed.
>
>
>     Sections 4.2 and 4.3 could probably use a note that notes that
>     retention of these TLVs doesn't make any sense.  These could be sent
>     with zero lifetime, except that if these are sent along with the
>     Source Address TLV, that's not possible... unless you send multiple
>     application data blocks for the same application.  Is that possible?
>
>
I have added the following text in each case:

It is not necessary to retain this TLV.

Thanks for the review

Stewart

--------------050306080307000809070800
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Including Sec ADs as this involves a
      change to the Authentication section.<br>
      <br>
      Section 6.3 now says<br>
      <br>
      The HMAC proceedure described in [RFC2104] is used to compute the
      hash.<br>
      The hash is computed over the entire GAP message as shown in Fig1.<br>
      The length of the Authentication Data field is always less than or
      equal<br>
      to the message digest size of the specific hash function that is
      being <br>
      used, however the implementer needs to consider that although this
      <br>
      decreases the size of the message, it results in a corresponding <br>
      reduction in the strength of the assurance provided. <br>
      Hash truncation is not RECOMMENDED.<br>
      <br>
      I will address any other security issues in another editing pass
      and<br>
      respond to their Discuss email.<br>
      <br>
      <br>
      On 10/03/2013 17:52, Martin Thomson wrote:<br>
    </div>
    <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">I sent the following review a few weeks back.Â  I
        just wanted to make sure that it didn't get accidentally stored
        in /dev/null.<br>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On 15 February 2013 14:33, Martin
          Thomson <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:martin.thomson@gmail.com" target="_blank">martin.thomson@gmail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">I am the
            assigned Gen-ART reviewer for this draft. For background on<br>
            Gen-ART, please see the FAQ at<br>
            <br>
            &lt;<a moz-do-not-send="true"
              href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
              target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br>
            <br>
            Please resolve these comments along with any other Last Call
            comments<br>
            you may receive.<br>
            <br>
            Document: draft-ietf-mpls-gach-adv-06<br>
            Reviewer: Martin Thomson<br>
            Review Date: 2013-02-15<br>
            IETF LC End Date: 2013-02-27<br>
            IESG Telechat date: (if known)<br>
            <br>
            Summary: The document is almost ready for publication as
            proposed<br>
            standard. Â There is a major issue that should be easy to
            resolve.<br>
            <br>
            Major issues:<br>
            <br>
            Section 6.3 duplicates the description of HMAC provided in
            RFC 2104.<br>
            That is likely to cause a bug.<br>
            <br>
            If you reference RFC 2104, then the only requirement is a
            clear<br>
            specification for what message is input to the HMAC.
            Â Currently, this<br>
            is buried. Â It is unclear if the input includes the G-ACh
            header<br>
            defined in RFC 5586 (it doesn't need to, but this needs to
            be made<br>
            explicit).<br>
            <br>
            Filling the authentication part with 0x878FE1F3 seems
            unnecessary busy<br>
            work, but it's harmless as long as the hash function
            produces a<br>
            multiple of 32 bits of output.<br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
    All done please see above.<br>
    <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            Minor issues:<br>
            <br>
            To avoid forward compatibility issues, reserved fields
            should come<br>
            with guidance that says: "Implementations of this protocol
            version<br>
            MUST set reserved fields to all zero bits when sending and
            ignore any<br>
            value when receiving messages."<br>
            <br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    The following was added just before Fig 1<br>
    <br>
    Implementations of this protocol version MUST set reserved fields in
    the <br>
    message formats that follow, to all zero bits when sending and
    ignore <br>
    any value when receiving messages.<br>
    <br>
    I feel that we should just write an update to RFC2119 to
    automatically <br>
    include this or add it to the standard boiler plate.<br>
    <br>
    <br>
    <br>
    <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            In Section 4.4, how does the duration interact with the
            lifetime?<br>
            What happens when the duration is longer than lifetime such
            that the<br>
            TLV is expunged before the duration is up?<br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    The TLV would be deleted (per procedure) at its death date, and<br>
    would not be sent again until at least duration has expired. This
    would<br>
    be silly if the receiver wanted that TLV, but entirely reasonable <br>
    if it dis not care about the TLV.<br>
    <br>
    <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            Section 5.2 states:<br>
            Â  Â [...] If one<br>
            Â  Â of the received TLV objects has the same Type as a
            previously<br>
            Â  Â received TLV then the data from the new object SHALL
            replace the data<br>
            Â  Â associated with that Type unless the X specification
            dictates a<br>
            Â  Â different behavior.<br>
            <br>
            This leads to different retention characteristics depending
            on some<br>
            arbitrary application-specific requirements. Â It also
            complicates<br>
            implementations. Â Is there a strong motivation for the
            "unless the X<br>
            specification dictates a different behavior" part of this
            statement?<br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    One can imagine alternative behaviors such as maintaining a list of
    <br>
    received values. Our goal was not to prejudge the application.<br>
    <br>
    <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            If this behaviour is desirable, a note regarding what
            happens to the<br>
            composed TLV when some of the values that contribute to it
            might<br>
            expire might be necessary.<br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    The behaviour described is the action of the data and not of the TLV
    that<br>
    it arrived in, so I don't think the problem you refer to can occur.<br>
    <br>
    <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            Regarding the last paragraph of Section 6.3:<br>
            Â  Â  Â  Â  Â  This also means that the use of hash functions
            with larger<br>
            Â  Â  Â  Â  Â  output sizes will increase the size of the GAP
            message as<br>
            Â  Â  Â  Â  Â  transmitted on the wire.<br>
            <br>
            If you want to prevent hash truncation, then use 'MUST'.
            Â Personally,<br>
            I see no reason to do so. Â It's a good way to get smaller
            messages,<br>
            with a corresponding reduction in the strength of the
            assurance<br>
            provided.<br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    Please see new text above.<br>
    <br>
    <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            Nits:<br>
            <br>
            Section 3 could use some subheadings to aid navigation (and
            referencing).<br>
            <br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    Done<br>
    <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            Section 3 describes the size of fields only through
            ASCII-art. Â It's a<br>
            fairly simple thing to add a bit count to the description of
            each<br>
            field. Â That includes the reserved fields, which have no
            descriptions.<br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    Done<br>
    <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            I like the text in the editors note on page 8. Â Why is it
            not the<br>
            actual text already?<br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    That was a hang over from AD review that was already addressed in
    the <br>
    text. The note has been removed.<br>
    <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            Sections 4.2 and 4.3 could probably use a note that notes
            that<br>
            retention of these TLVs doesn't make any sense. Â These could
            be sent<br>
            with zero lifetime, except that if these are sent along with
            the<br>
            Source Address TLV, that's not possible... unless you send
            multiple<br>
            application data blocks for the same application. Â Is that
            possible?<br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    I have added the following text in each case:<br>
    <br>
    It is not necessary to retain this TLV.<br>
    <br>
    Thanks for the review<br>
    <br>
    Stewart<br>
  </body>
</html>

--------------050306080307000809070800--

From martin.thomson@gmail.com  Fri Apr 26 11:45:24 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10F7E21F990F for <gen-art@ietfa.amsl.com>; Fri, 26 Apr 2013 11:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 jcp4K-WWGdv8 for <gen-art@ietfa.amsl.com>; Fri, 26 Apr 2013 11:45:23 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5B63C21F988B for <gen-art@ietf.org>; Fri, 26 Apr 2013 11:45:23 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id z2so4049933wey.1 for <gen-art@ietf.org>; Fri, 26 Apr 2013 11:45:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=viNz2PrNmEw1m4/6UBRUF9LIWWN97kGmly22QEr5P6s=; b=fKdC/AOHbsZBOl58dF4xcH/MFuHpTnsocx51icPEJWNG9hWicMThNbq2KeAjo4DuBO p1yV8g4n5pxuzQ278pbxUiun15gGZt+ei5HX1e0kZvzsxGosqKq9HdONiAI2zF719hAl Rc+YA0YkUYKSv6iNJXcj3MCA/ieY7wS/zWOg5u3TTiQ19fPAeJWc7VjQutENC18pT1vQ Gaoe165lOCX8zfnxYATWA/kzEVv8BkMB8QzgKrS6YJBRgqmfF34IS5h2iuNB0pHxkwCV +OHME8w6HszIRPK6YXfR00pNr8t55jqfSumiRPbE4BZQv60Rw6j7pmi9w+fRCwi3TKSI 05Xg==
MIME-Version: 1.0
X-Received: by 10.180.183.133 with SMTP id em5mr5796252wic.26.1367001922503; Fri, 26 Apr 2013 11:45:22 -0700 (PDT)
Received: by 10.194.33.102 with HTTP; Fri, 26 Apr 2013 11:45:22 -0700 (PDT)
In-Reply-To: <517ABCF0.2080701@cisco.com>
References: <CABkgnnW-53MVHZaW4QweqBjrPGCrP=fCNQ+LJdaG__ePh2tn1A@mail.gmail.com> <CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com> <517ABCF0.2080701@cisco.com>
Date: Fri, 26 Apr 2013 11:45:22 -0700
Message-ID: <CABkgnnX7H_y1cV4O+k4OcmB1bqkTB3iu+uvzec6Ura89W-JQSQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: stbryant@cisco.com
Content-Type: text/plain; charset=UTF-8
Cc: "Bocci, Matthew \(Matthew\)" <matthew.bocci@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, danfrost@cisco.com, draft-ietf-mpls-gach-adv.all@tools.ietf.org, sec-ads@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-gach-adv-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 18:45:24 -0000

On 26 April 2013 10:44, Stewart Bryant <stbryant@cisco.com> wrote:
> Section 6.3 now says
>
> The HMAC proceedure described in [RFC2104] is used to compute the hash.

s/proceedure/procedure/

> The hash is computed over the entire GAP message as shown in Fig1.

What value does the Authentication TLV have when it is input to the HMAC?

> The length of the Authentication Data field is always less than or equal
> to the message digest size of the specific hash function that is being
> used, however the implementer needs to consider that although this
> decreases the size of the message, it results in a corresponding
> reduction in the strength of the assurance provided.
> Hash truncation is not RECOMMENDED.

This last part could probably be a new paragraph.

From stbryant@cisco.com  Fri Apr 26 16:07:16 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39FBF21F993F for <gen-art@ietfa.amsl.com>; Fri, 26 Apr 2013 16:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.544
X-Spam-Level: 
X-Spam-Status: No, score=-110.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 EhofUXkiv4nx for <gen-art@ietfa.amsl.com>; Fri, 26 Apr 2013 16:07:14 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id A0ED421F9909 for <gen-art@ietf.org>; Fri, 26 Apr 2013 16:07:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1053; q=dns/txt; s=iport; t=1367017635; x=1368227235; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=iMeYd8nxVf8zUyWb+wUn3nR3P+XYXTULb1jf64/9QyE=; b=ABB6TyaZPsKJyxHgH8xB42v5+vXUpBAgotTY5aS4OyneDWAiD6S2nbe+ 4jn4kj07wi5LCe1Dgslln549+/ZkfKxY32R51L9LrOvbAbKov5cgF1dDk jbymMju31+CH7nJYJe7YsZ/MyRHXTF5S/xoewnIOtY/v51YuVhHH9yFyA g=;
X-IronPort-AV: E=Sophos;i="4.87,561,1363132800"; d="scan'208";a="13131416"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 26 Apr 2013 23:07:14 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3QN7BR9014373 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Apr 2013 23:07:12 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r3QN7APC019931; Sat, 27 Apr 2013 00:07:10 +0100 (BST)
Message-ID: <517B089E.4060901@cisco.com>
Date: Sat, 27 Apr 2013 00:07:10 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <CABkgnnW-53MVHZaW4QweqBjrPGCrP=fCNQ+LJdaG__ePh2tn1A@mail.gmail.com> <CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com> <517ABCF0.2080701@cisco.com> <CABkgnnX7H_y1cV4O+k4OcmB1bqkTB3iu+uvzec6Ura89W-JQSQ@mail.gmail.com>
In-Reply-To: <CABkgnnX7H_y1cV4O+k4OcmB1bqkTB3iu+uvzec6Ura89W-JQSQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Bocci, Matthew \(Matthew\)" <matthew.bocci@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, danfrost@cisco.com, draft-ietf-mpls-gach-adv.all@tools.ietf.org, sec-ads@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-gach-adv-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2013 23:07:16 -0000

On 26/04/2013 19:45, Martin Thomson wrote:
> On 26 April 2013 10:44, Stewart Bryant <stbryant@cisco.com> wrote:
>> Section 6.3 now says
>>
>> The HMAC proceedure described in [RFC2104] is used to compute the hash.
> s/proceedure/procedure/
>
>> The hash is computed over the entire GAP message as shown in Fig1.
> What value does the Authentication TLV have when it is input to the HMAC?
Sorry missed that - zero - will address in the inevitable next version.

Stewart
>
>> The length of the Authentication Data field is always less than or equal
>> to the message digest size of the specific hash function that is being
>> used, however the implementer needs to consider that although this
>> decreases the size of the message, it results in a corresponding
>> reduction in the strength of the assurance provided.
>> Hash truncation is not RECOMMENDED.
> This last part could probably be a new paragraph.
> .
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From volz@cisco.com  Fri Apr 26 21:23:43 2013
Return-Path: <volz@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC5C21F988D; Fri, 26 Apr 2013 21:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Li2P7zNg8Mf; Fri, 26 Apr 2013 21:23:42 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 0054F21F988A; Fri, 26 Apr 2013 21:23:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4601; q=dns/txt; s=iport; t=1367036622; x=1368246222; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ocoessXB2ZCDisMmRfUCZNp1/RWstXWXI9AVwd/qPao=; b=Dk6BCwR7kSu4yNeLFxo6KN5wdiXeG959fGc3IjK36MSJ7s8uVRphMlbD ZG8izJPgUjRO1zaEBhS8i1JnRQ44R9lPBD2hyNi1nqxzMHzgpGlMBr+tt 8f4XVWbmKmGrug+pWVs6+s56R41ClYcTPCM8Fi8hUeSJ+4QpTZxoSx9SX U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAN5Re1GtJV2Z/2dsb2JhbABRgwc2vkOBBBZ0gh8BAQEDAQEBAWsLBQcEAgEIDgMDAQEBAQodBycLFAkIAgQBDQUIiAYGDL8UjmExBwaCZ2EDiFqDRYwjhV+KJYMOgig
X-IronPort-AV: E=Sophos;i="4.87,562,1363132800"; d="scan'208";a="203704341"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 27 Apr 2013 04:23:41 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r3R4NeIb030738 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 27 Apr 2013 04:23:40 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.31]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Fri, 26 Apr 2013 23:23:40 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Index: AQHOQpnwLrlO/DVOGkmT6MAmTnOo8Zjpd9oA
Date: Sat, 27 Apr 2013 04:23:39 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com>
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr> <517AA910.8030608@nostrum.com>
In-Reply-To: <517AA910.8030608@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.247.178]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>
Subject: Re: [Gen-art] [dhcwg] RE : Gen-art review:	draft-ietf-dhc-triggered-reconfigure-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Apr 2013 04:23:43 -0000

Robert:

The reason to allow this is that otherwise client A will be unnecessarily r=
econfigured many times. (It is also possible that a client might Renew on i=
ts own just as this is happening and thus it can also be removed from the R=
econfigure.)

I think the text should be cleaned up to indicate that allowing removal of =
already reconfigured clients is recommended (to prevent unnecessary reconfi=
gures) when retransmitting the Reconfigure-Request.

Note that if clients are added, that is not a retransmission but requires a=
 "new" message (new XID).

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of R=
obert Sparks
Sent: Friday, April 26, 2013 12:19 PM
To: mohamed.boucadair@orange.com
Cc: dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf-dhc=
-triggered-reconfigure@tools.ietf.org
Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfig=
ure-05

On 4/26/13 10:58 AM, mohamed.boucadair@orange.com wrote:
> Dear Robert,
>
> Thank you for the review.
> Please see inline.
>
> Cheers,
> Med
> ________________________________________
> De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de=20
> Robert Sparks [rjsparks@nostrum.com] Date d'envoi : vendredi 26 avril=20
> 2013 17:42 =C0 : dhcwg@ietf.org; ietf@ietf.org; General Area Review=20
> Team; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
> Objet : [dhcwg] Gen-art review:=20
> draft-ietf-dhc-triggered-reconfigure-05
>
> I am the assigned Gen-ART reviewer for this draft. For background on=20
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq><http://wiki.too=
ls.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments=20
> you may receive.
>
> Document: draft-ietf-dhc-triggered-reconfigure-05
> Reviewer:  Robert Sparks
> Review Date: April 26, 2013
> IETF LC End Date: May 6, 2013
> IESG Telechat date: May 16, 2013
>
> Summary: This draft is on the right track but has open issues, described =
in
>        the review.
>
> Major issues:
>
> Overall, this document is solid, but I think there is a bug in section 6.=
3.
> I could be wrong, but If I'm right, this paragraph:
>
> When retransmission is required, the relay may decide to correct the cont=
ent of RECONFIGURE-REQUEST message it issues (e.g., update the Client Ident=
ifier list).  This decision is local to the relay (e.g., it may be based on=
 observed events such as one or more clients were reconfigured on their own=
).
>
> introduces a race-condition that could lead to an erroneous state. If a r=
elay's first message included client A, then the retransmission included cl=
ients A and B, but that retransmission crosses with a success RECONFIGURE-R=
EPLY to the request that only included client A, the relay will think it su=
cceeded in asking A and B to be reconfigured.
>
> Med: This example does not apply for that text.
Really? What text constrains how you change what's in the retransmission?
>   In fact, the example should be the other way around. Perhaps, this can =
be made clearer if we change "(e.g., update the Client Identifier list)" to=
 "(e.g., remove a client from the Client Identifier list)".
If I understand you correctly, you need more than just changing a parenthet=
ical e.g.. I think you're saying that you are constraining the message chan=
ges to be such that if anything earlier in the retransmission sequence succ=
eeded, the request in the retransmission would also have succeeded. But why=
 do you need that much complexity? Do you have it already with any other re=
quest?
>
> Minor issues:
>
> This sentence:
>
> Furthermore, means to recover state in failure events must be supported, =
but are not discussed in this document.
> places a requirement on a relay (even though it's not using a 2119 MUST).=
 Is there some other document that defines this requirement that you can re=
ference?
>
> Med: I'm not aware of any; but if there is one we can cite it.
>
>   If not, the requirement should be discussed in this document. Alternati=
vely, you could change the sentence to talk about the consequences of not h=
aving a proprietary means for recovering state.
>
> Med: Will consider that option if you think this is really needed.
>
> Nits/editorial comments:

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

From ron.even.tlv@gmail.com  Sun Apr 28 01:31:47 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FBEC21F97CD; Sun, 28 Apr 2013 01:31:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.598
X-Spam-Level: 
X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001]
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 9Pce2SyBr52Y; Sun, 28 Apr 2013 01:31:46 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 8A50D21F97BF; Sun, 28 Apr 2013 01:31:45 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id m6so1836655wiv.7 for <multiple recipients>; Sun, 28 Apr 2013 01:31:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=DvMD5USsMxsZhydlsJx+28zMSphGwnuBytv27U8h4r0=; b=epILJ/TXQI1bxzWzg1T1cJOhE68/8lmckrZGf207d5nyIxhBdaKEhx1Yppy65GGA0Y DHi5hzHK1WB+uKlpOc7CZ5XpV4UTwhcqtDcMBn+6r5cckWBzvj1vJ1rw+PlQRlhUrXa/ WuWVFc4yMx0KLilINSg25DPKN52Nu1bWMS7M9Y2f7ac0cqzKxpdc5EAlINERsuD1ZFbm ZohGYbR7frzMlIyVBIaibef1Sfju5p1oy29yiGn/vRK6xOZOdszXJSLSMn4Al543VSBN ubU26fQamZHh/cTJit1cWVyjO0ax5UIP78LrrNnblEUXlxfQYxkSRWyGJnsubGRYQSPC K1TQ==
X-Received: by 10.194.93.231 with SMTP id cx7mr28998781wjb.33.1367137904755; Sun, 28 Apr 2013 01:31:44 -0700 (PDT)
Received: from RoniE (bzq-79-181-177-28.red.bezeqint.net. [79.181.177.28]) by mx.google.com with ESMTPSA id j4sm12971665wiz.10.2013.04.28.01.31.41 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 28 Apr 2013 01:31:43 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org>, <ietf@ietf.org>
Date: Sun, 28 Apr 2013 11:31:05 +0300
Message-ID: <019901ce43ea$bbd575a0$338060e0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_019A_01CE4403.E1239800"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5D6pKryX0MWBh9SKaAMkeLEbN6Nw==
Content-Language: en-us
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Apr 2013 08:31:47 -0000

This is a multipart message in MIME format.

------=_NextPart_000_019A_01CE4403.E1239800
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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-netmod-interfaces-cfg-10

Reviewer: Roni Even

Review Date:2013-4-28

IETF LC End Date: 2013-5-3

IESG Telechat date: 2013-5-16

 

Summary: This draft is almost ready for publication as Standard track RFC.

 

 

Major issues:

 

Minor issues:

 

1.       I had some problem understanding the "location" leaf. Section 3.2
has it as a string and says that "The device uses the location string to
identify the physical or logical entity that the configuration applies to".
I am not sure how you identify physical location having no definition of the
mapping. I saw the examples in Appendix E and it looked more to me as
logical mapping but not physical since it attaches a name to something in
the device but I am not clear how you know what it is physically in the
device. If the name 0-n or n/m are real physical entities, I think that it
should be specified some place. 

 

 

Nits/editorial comments:

1.	In the introduction section maybe add to the first sentence a
reference to RFC6244 with some text.
2.	In section 2 are the" must" and "should"  used as described in
RFC2119, if yes need capital letters
3.	In section 3.1 "It is optional in the data model,  but if the type
represents a physical interface, it is mandatory", suggest having RFC2119
language "It is OPTIONAL in the data model,  but if the type represents a
physical interface, it is MUST be specified"

 


------=_NextPart_000_019A_01CE4403.E1239800
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1169102253;
	mso-list-type:hybrid;
	mso-list-template-ids:876275048 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1947733698;
	mso-list-type:hybrid;
	mso-list-template-ids:91134052 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-netmod-interfaces-cfg-10</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;4&#8211;28<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-5&#8211;3<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: 2013-5-16<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as Standard track =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I had some =
problem understanding the &#8220;location&#8221; leaf. Section 3.2 has =
it as a string and says that </span>&#8220;<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The device =
uses the location string to identify the physical or logical entity that =
the configuration applies to&#8221;. I am not sure how you identify =
physical location having no definition of the mapping. I saw the =
examples in Appendix E and it looked more to me as logical mapping but =
not physical since it attaches a name to something in the device but I =
am not clear how you know what it is physically in the device. If the =
name 0-n or n/m are real physical entities, I think that it should be =
specified some place. <o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l1 level1 lfo2'>In the =
introduction section maybe add to the first sentence a reference to =
RFC6244 with some text.<o:p></o:p></li><li class=3DMsoNormal =
style=3D'mso-list:l1 level1 lfo2'>In section 2 are the&#8221; =
must&#8221; and &#8220;should&#8221;&nbsp; used as described in RFC2119, =
if yes need capital letters<o:p></o:p></li><li class=3DMsoNormal =
style=3D'mso-list:l1 level1 lfo2'>In section 3.1 &#8220;It is optional =
in the data model,&nbsp; but if the type represents a physical =
interface, it is mandatory&#8221;, suggest having RFC2119 language =
&#8220;It is OPTIONAL in the data model,&nbsp; but if the type =
represents a physical interface, it is MUST be =
specified&#8221;<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_019A_01CE4403.E1239800--


From ron.even.tlv@gmail.com  Sun Apr 28 05:31:51 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26D2321F9917; Sun, 28 Apr 2013 05:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.598
X-Spam-Level: 
X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, GB_I_LETTER=-2]
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 A4+UUSiIAT7H; Sun, 28 Apr 2013 05:31:50 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 4B4E621F98DA; Sun, 28 Apr 2013 05:31:41 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id s47so3953144wey.22 for <multiple recipients>; Sun, 28 Apr 2013 05:31:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=AvGl41968ax6N4oGf0iGDisRbb+k9EtUYssccTvI+Bk=; b=J+by7LoRUsrgMAFzxA+mGAJ86KCPqQUsBCFqO1rFKjub3D6qJCHwAwTq7E5O9wMe8N stWHRVJKScTM8a4dUkYLIcTZT6jne0dDKdeNo3owl3SEDWbbbVK/ImWp5gmwuInPZ4Ph 6woQw7/5h+wSk0bbRFUUT0CKamcT9u8+v3zstSolEUQKPg10h9yHojm2n6Lrp7Z3CFCt SNfVYHyOczAqIHcTRm5++5eBJpdStPOVhq3VX4QPnQGp5cf5gwKRKVVcTcMoqGifPM+X U0v9xgfe4ArIsHVIztbm1yhKh8kHxC/xIHA8ntp4o/A4A0y7pnJkUeVT8YxsQxZSPvjt 6h2w==
X-Received: by 10.194.62.233 with SMTP id b9mr31042601wjs.37.1367152300381; Sun, 28 Apr 2013 05:31:40 -0700 (PDT)
Received: from RoniE (bzq-79-181-177-28.red.bezeqint.net. [79.181.177.28]) by mx.google.com with ESMTPSA id e8sm8398599wic.5.2013.04.28.05.31.37 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 28 Apr 2013 05:31:39 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Martin Bjorklund'" <mbj@tail-f.com>
References: <019901ce43ea$bbd575a0$338060e0$@gmail.com> <20130428.115010.513224826.mbj@tail-f.com>
In-Reply-To: <20130428.115010.513224826.mbj@tail-f.com>
Date: Sun, 28 Apr 2013 15:31:01 +0300
Message-ID: <01ba01ce440c$408d4720$c1a7d560$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFWiDTvx1wg5jy+XbNDGWkbCL4PFgG0N6f1mc1j5KA=
Content-Language: en-us
Cc: gen-art@ietf.org, draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Apr 2013 12:31:51 -0000

Martin,
Thanks for the response. I am OK with your responses to the nits.

As for the comment on location I think I understand but what got me thinking
was the examples.
In E.1 

"An operator can configure a new interface by sending an <edit-config>
   containing:

     <interface nc:operation="create">
       <name>fastethernet-1/0</name>
     </interface>

   When the server processes this request, it will set the leaf "type"
   to "ethernetCsmacd" and "location" to "1/0".  Thus, if the client
   performs a <get-config> right after the <edit-config> above, it will
   get:

     <interface>
       <name>fastethernet-1/0</name>
       <type>ethernetCsmacd</type>
       <location>1/0</location>
     </interface>"

I can see how the linkage between the location and name is done. I am not
sure how the operator knows from the response what is the physical location
without knowing the device type and manufacturer but at least the linkage is
there and this is why I thought of it more as a logical device and not
physical one.

When looking at E2.2 example
  " An operator can configure a new interface by sending an <edit-config>
   containing:

     <interface nc:operation="create">
       <name>acme-interface</name>
       <type>ethernetCsmacd</type>
       <location>1/0</location>
     </interface>"

Here the operator need to know the device to configure a specific interface
and know how many interface exist and how they are named. So you assume that
for this case this is known to the configuration.

Roni




-----Original Message-----
From: Martin Bjorklund [mailto:mbj@tail-f.com] 
Sent: 28 April, 2013 12:50 PM
To: ron.even.tlv@gmail.com
Cc: draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org; ietf@ietf.org;
gen-art@ietf.org
Subject: Re: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10

Hi,

Thank you for your review.  Comments inline.

"Roni Even" <ron.even.tlv@gmail.com> wrote:
> 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-netmod-interfaces-cfg-10
> 
> Reviewer: Roni Even
> 
> Review Date:2013-4-28
> 
> IETF LC End Date: 2013-5-3
> 
> IESG Telechat date: 2013-5-16
> 
>  
> 
> Summary: This draft is almost ready for publication as Standard track RFC.
> 
>  
> 
>  
> 
> Major issues:
> 
>  
> 
> Minor issues:
> 
>  
> 
> 1.       I had some problem understanding the "location" leaf. Section 3.2
> has it as a string and says that "The device uses the location string 
> to identify the physical or logical entity that the configuration applies
to".
> I am not sure how you identify physical location having no definition 
> of the mapping.

The sentence just before the quoted one above says:

  "The format of this string is device- and type-dependent."

and then the text says:

  "How a client can learn which types and locations are present on a
  certain device is outside the scope of this document."

So the exact procedure is currently left to the vendors, but may be
standardized in a future document (if possible...)

> I saw the examples in Appendix E and it looked more to me as logical 
> mapping but not physical since it attaches a name to something in the 
> device but I am not clear how you know what it is physically in the 
> device. If the name 0-n or n/m are real physical entities, I think 
> that it should be specified some place.
> 
>  
> 
>  
> 
> Nits/editorial comments:
> 
> 1.	In the introduction section maybe add to the first sentence a
> reference to RFC6244 with some text.

Ok, this probably makes sense.  I will check w/ the WG and other documents.



> 2.	In section 2 are the" must" and "should"  used as described in
> RFC2119, if yes need capital letters

Seciton 2 is more of a background, non-normative section.  It lists some of
the design objectives.

> 3.	In section 3.1 "It is optional in the data model,  but if the type
> represents a physical interface, it is mandatory", suggest having 
> RFC2119 language "It is OPTIONAL in the data model,  but if the type 
> represents a physical interface, it is MUST be specified"

I think the first one should not be OPTIONAL, but the second one is correct.
So I suggest this:

  It is defined as being optional in the data model, but if the type
  represents a physical interface, it MUST be specified.


/martin


From mbj@tail-f.com  Sun Apr 28 02:50:15 2013
Return-Path: <mbj@tail-f.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CCE221F980B; Sun, 28 Apr 2013 02:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.046
X-Spam-Level: 
X-Spam-Status: No, score=-4.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553]
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 SwRmQdrJRmVM; Sun, 28 Apr 2013 02:50:14 -0700 (PDT)
Received: from mail.tail-f.com (de-2007.d.ipeer.se [213.180.74.102]) by ietfa.amsl.com (Postfix) with ESMTP id 9F81821F97FB; Sun, 28 Apr 2013 02:50:14 -0700 (PDT)
Received: from localhost (unknown [192.36.80.8]) by mail.tail-f.com (Postfix) with ESMTPSA id 61F831200AE5; Sun, 28 Apr 2013 11:50:12 +0200 (CEST)
Date: Sun, 28 Apr 2013 11:50:10 +0200 (CEST)
Message-Id: <20130428.115010.513224826.mbj@tail-f.com>
To: ron.even.tlv@gmail.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <019901ce43ea$bbd575a0$338060e0$@gmail.com>
References: <019901ce43ea$bbd575a0$338060e0$@gmail.com>
X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sun, 28 Apr 2013 13:02:19 -0700
Cc: gen-art@ietf.org, draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Apr 2013 09:50:15 -0000

Hi,

Thank you for your review.  Comments inline.

"Roni Even" <ron.even.tlv@gmail.com> wrote:
> 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-netmod-interfaces-cfg-10
> 
> Reviewer: Roni Even
> 
> Review Date:2013-4-28
> 
> IETF LC End Date: 2013-5-3
> 
> IESG Telechat date: 2013-5-16
> 
>  
> 
> Summary: This draft is almost ready for publication as Standard track RFC.
> 
>  
> 
>  
> 
> Major issues:
> 
>  
> 
> Minor issues:
> 
>  
> 
> 1.       I had some problem understanding the "location" leaf. Section 3.2
> has it as a string and says that "The device uses the location string to
> identify the physical or logical entity that the configuration applies to".
> I am not sure how you identify physical location having no definition of the
> mapping.

The sentence just before the quoted one above says:

  "The format of this string is device- and type-dependent."

and then the text says:

  "How a client can learn which types and locations are present on a
  certain device is outside the scope of this document."

So the exact procedure is currently left to the vendors, but may be
standardized in a future document (if possible...)

> I saw the examples in Appendix E and it looked more to me as
> logical mapping but not physical since it attaches a name to something in
> the device but I am not clear how you know what it is physically in the
> device. If the name 0-n or n/m are real physical entities, I think that it
> should be specified some place. 
> 
>  
> 
>  
> 
> Nits/editorial comments:
> 
> 1.	In the introduction section maybe add to the first sentence a
> reference to RFC6244 with some text.

Ok, this probably makes sense.  I will check w/ the WG and other
documents.

> 2.	In section 2 are the" must" and "should"  used as described in
> RFC2119, if yes need capital letters

Seciton 2 is more of a background, non-normative section.  It lists
some of the design objectives.

> 3.	In section 3.1 "It is optional in the data model,  but if the type
> represents a physical interface, it is mandatory", suggest having RFC2119
> language "It is OPTIONAL in the data model,  but if the type represents a
> physical interface, it is MUST be specified"

I think the first one should not be OPTIONAL, but the second one is
correct.  So I suggest this:

  It is defined as being optional in the data model, but if the type
  represents a physical interface, it MUST be specified.


/martin

From mohamed.boucadair@orange.com  Sun Apr 28 22:59:57 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C74221F9D31; Sun, 28 Apr 2013 22:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 Mbd+JyNPPzUc; Sun, 28 Apr 2013 22:59:56 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 768FB21F9D2F; Sun, 28 Apr 2013 22:59:53 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 26CC222C2FA; Mon, 29 Apr 2013 07:59:52 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id ED23C35C07A; Mon, 29 Apr 2013 07:59:51 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Mon, 29 Apr 2013 07:59:51 +0200
From: <mohamed.boucadair@orange.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, Robert Sparks <rjsparks@nostrum.com>
Date: Mon, 29 Apr 2013 07:59:50 +0200
Thread-Topic: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Index: AQHOQpnwLrlO/DVOGkmT6MAmTnOo8Zjpd9oAgAM8HYA=
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC9B49B02@PUEXCB1B.nanterre.francetelecom.fr>
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr> <517AA910.8030608@nostrum.com> <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.4.28.223919
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>
Subject: Re: [Gen-art] [dhcwg] RE : Gen-art review:	draft-ietf-dhc-triggered-reconfigure-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 05:59:57 -0000

Robert,

Ted suggested a wording which is better than the one I proposed. I made the=
 following changes my local copy:

(1)

OLD:
   When retransmission is required, the relay may decide to correct the
   content of RECONFIGURE-REQUEST message it issues (e.g., update the
   Client Identifier list).

NEW:
   The relay MAY remove clients from the client identifier list in
   subsequent retransmissions, but MUST NOT add clients to the client
   identifier list.

(2)

OLD:
   Furthermore, means to recover state in failure events must be
   supported, but are not discussed in this document.

NEW:
   Furthermore, means to recover state in failure events (e.g.,
   [RFC5460]) must be supported, but are not discussed in this document.

Is this better?

Cheers,
Med


>-----Message d'origine-----
>De=A0: Bernie Volz (volz) [mailto:volz@cisco.com]
>Envoy=E9=A0: samedi 27 avril 2013 06:24
>=C0=A0: Robert Sparks; BOUCADAIR Mohamed OLNC/OLN
>Cc=A0: dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf=
-
>dhc-triggered-reconfigure@tools.ietf.org
>Objet=A0: RE: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>reconfigure-05
>
>Robert:
>
>The reason to allow this is that otherwise client A will be unnecessarily
>reconfigured many times. (It is also possible that a client might Renew on
>its own just as this is happening and thus it can also be removed from the
>Reconfigure.)
>
>I think the text should be cleaned up to indicate that allowing removal of
>already reconfigured clients is recommended (to prevent unnecessary
>reconfigures) when retransmitting the Reconfigure-Request.
>
>Note that if clients are added, that is not a retransmission but requires =
a
>"new" message (new XID).
>
>- Bernie
>
>-----Original Message-----
>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
>Robert Sparks
>Sent: Friday, April 26, 2013 12:19 PM
>To: mohamed.boucadair@orange.com
>Cc: dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf-
>dhc-triggered-reconfigure@tools.ietf.org
>Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>reconfigure-05
>
>On 4/26/13 10:58 AM, mohamed.boucadair@orange.com wrote:
>> Dear Robert,
>>
>> Thank you for the review.
>> Please see inline.
>>
>> Cheers,
>> Med
>> ________________________________________
>> De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de
>> Robert Sparks [rjsparks@nostrum.com] Date d'envoi : vendredi 26 avril
>> 2013 17:42 =C0 : dhcwg@ietf.org; ietf@ietf.org; General Area Review
>> Team; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
>> Objet : [dhcwg] Gen-art review:
>> draft-ietf-dhc-triggered-reconfigure-05
>>
>> 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><http://wiki.tool=
s
>.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-dhc-triggered-reconfigure-05
>> Reviewer:  Robert Sparks
>> Review Date: April 26, 2013
>> IETF LC End Date: May 6, 2013
>> IESG Telechat date: May 16, 2013
>>
>> Summary: This draft is on the right track but has open issues, described
>in
>>        the review.
>>
>> Major issues:
>>
>> Overall, this document is solid, but I think there is a bug in section
>6.3.
>> I could be wrong, but If I'm right, this paragraph:
>>
>> When retransmission is required, the relay may decide to correct the
>content of RECONFIGURE-REQUEST message it issues (e.g., update the Client
>Identifier list).  This decision is local to the relay (e.g., it may be
>based on observed events such as one or more clients were reconfigured on
>their own).
>>
>> introduces a race-condition that could lead to an erroneous state. If a
>relay's first message included client A, then the retransmission included
>clients A and B, but that retransmission crosses with a success
>RECONFIGURE-REPLY to the request that only included client A, the relay
>will think it succeeded in asking A and B to be reconfigured.
>>
>> Med: This example does not apply for that text.
>Really? What text constrains how you change what's in the retransmission?
>>   In fact, the example should be the other way around. Perhaps, this can
>be made clearer if we change "(e.g., update the Client Identifier list)" t=
o
>"(e.g., remove a client from the Client Identifier list)".
>If I understand you correctly, you need more than just changing a
>parenthetical e.g.. I think you're saying that you are constraining the
>message changes to be such that if anything earlier in the retransmission
>sequence succeeded, the request in the retransmission would also have
>succeeded. But why do you need that much complexity? Do you have it alread=
y
>with any other request?
>>
>> Minor issues:
>>
>> This sentence:
>>
>> Furthermore, means to recover state in failure events must be supported,
>but are not discussed in this document.
>> places a requirement on a relay (even though it's not using a 2119 MUST)=
.
>Is there some other document that defines this requirement that you can
>reference?
>>
>> Med: I'm not aware of any; but if there is one we can cite it.
>>
>>   If not, the requirement should be discussed in this document.
>Alternatively, you could change the sentence to talk about the consequence=
s
>of not having a proprietary means for recovering state.
>>
>> Med: Will consider that option if you think this is really needed.
>>
>> Nits/editorial comments:
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg

From mbj@tail-f.com  Mon Apr 29 01:25:45 2013
Return-Path: <mbj@tail-f.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E41921F9487; Mon, 29 Apr 2013 01:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.046
X-Spam-Level: 
X-Spam-Status: No, score=-3.046 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553]
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 WThuJnsDzXnU; Mon, 29 Apr 2013 01:25:44 -0700 (PDT)
Received: from mail.tail-f.com (de-2007.d.ipeer.se [213.180.74.102]) by ietfa.amsl.com (Postfix) with ESMTP id 43C3321F9389; Mon, 29 Apr 2013 01:25:43 -0700 (PDT)
Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id 6A8A212008D2; Mon, 29 Apr 2013 10:25:42 +0200 (CEST)
Date: Mon, 29 Apr 2013 10:25:42 +0200 (CEST)
Message-Id: <20130429.102542.1993240684524912340.mbj@tail-f.com>
To: ron.even.tlv@gmail.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <01ba01ce440c$408d4720$c1a7d560$@gmail.com>
References: <019901ce43ea$bbd575a0$338060e0$@gmail.com> <20130428.115010.513224826.mbj@tail-f.com> <01ba01ce440c$408d4720$c1a7d560$@gmail.com>
X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 08:25:45 -0000

Hi,

"Roni Even" <ron.even.tlv@gmail.com> wrote:
> Martin,
> Thanks for the response. I am OK with your responses to the nits.
> 
> As for the comment on location I think I understand but what got me thinking
> was the examples.
> In E.1 
> 
> "An operator can configure a new interface by sending an <edit-config>
>    containing:
> 
>      <interface nc:operation="create">
>        <name>fastethernet-1/0</name>
>      </interface>
> 
>    When the server processes this request, it will set the leaf "type"
>    to "ethernetCsmacd" and "location" to "1/0".  Thus, if the client
>    performs a <get-config> right after the <edit-config> above, it will
>    get:
> 
>      <interface>
>        <name>fastethernet-1/0</name>
>        <type>ethernetCsmacd</type>
>        <location>1/0</location>
>      </interface>"
> 
> I can see how the linkage between the location and name is done. I am not
> sure how the operator knows from the response what is the physical location
> without knowing the device type and manufacturer but at least the linkage is
> there and this is why I thought of it more as a logical device and not
> physical one.

Ok.  Since this is an example of a configuration of a physical
interface, it is assumed that the operator somehow knows which
physical port is being reconfigured -- somehow the operator must be
able to know what the port where the new cable was inserted is called
in the config.

But it makes sense to be more clear about this.  How about this
change:


OLD:

  The implementation restricts the names of the interfaces to one of
  "fastethernet-N/M" or "gigabitethernet-N/M".  The "location" of an
  interface is a string on the form "N/M".  The implementation
  auto-initializes the values for "type" and "location" based on the
  interface name.

NEW:

  The implementation restricts the names of the interfaces to one of
  "fastethernet-N/M" or "gigabitethernet-N/M".  The "location" of an
  interface is a string on the form "N/M".  It is assumed that the
  operator is aware of this naming scheme.  The implementation
  auto-initializes the values for "type" and "location" based on the
  interface name.

> When looking at E2.2 example

(ditto for this example.)


/martin



>   " An operator can configure a new interface by sending an <edit-config>
>    containing:
> 
>      <interface nc:operation="create">
>        <name>acme-interface</name>
>        <type>ethernetCsmacd</type>
>        <location>1/0</location>
>      </interface>"
> 
> Here the operator need to know the device to configure a specific interface
> and know how many interface exist and how they are named. So you assume that
> for this case this is known to the configuration.
> 
> Roni
> 
> 
> 
> 
> -----Original Message-----
> From: Martin Bjorklund [mailto:mbj@tail-f.com] 
> Sent: 28 April, 2013 12:50 PM
> To: ron.even.tlv@gmail.com
> Cc: draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org; ietf@ietf.org;
> gen-art@ietf.org
> Subject: Re: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
> 
> Hi,
> 
> Thank you for your review.  Comments inline.
> 
> "Roni Even" <ron.even.tlv@gmail.com> wrote:
> > 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-netmod-interfaces-cfg-10
> > 
> > Reviewer: Roni Even
> > 
> > Review Date:2013-4-28
> > 
> > IETF LC End Date: 2013-5-3
> > 
> > IESG Telechat date: 2013-5-16
> > 
> >  
> > 
> > Summary: This draft is almost ready for publication as Standard track RFC.
> > 
> >  
> > 
> >  
> > 
> > Major issues:
> > 
> >  
> > 
> > Minor issues:
> > 
> >  
> > 
> > 1.       I had some problem understanding the "location" leaf. Section 3.2
> > has it as a string and says that "The device uses the location string 
> > to identify the physical or logical entity that the configuration applies
> to".
> > I am not sure how you identify physical location having no definition 
> > of the mapping.
> 
> The sentence just before the quoted one above says:
> 
>   "The format of this string is device- and type-dependent."
> 
> and then the text says:
> 
>   "How a client can learn which types and locations are present on a
>   certain device is outside the scope of this document."
> 
> So the exact procedure is currently left to the vendors, but may be
> standardized in a future document (if possible...)
> 
> > I saw the examples in Appendix E and it looked more to me as logical 
> > mapping but not physical since it attaches a name to something in the 
> > device but I am not clear how you know what it is physically in the 
> > device. If the name 0-n or n/m are real physical entities, I think 
> > that it should be specified some place.
> > 
> >  
> > 
> >  
> > 
> > Nits/editorial comments:
> > 
> > 1.	In the introduction section maybe add to the first sentence a
> > reference to RFC6244 with some text.
> 
> Ok, this probably makes sense.  I will check w/ the WG and other documents.
> 
> 
> 
> > 2.	In section 2 are the" must" and "should"  used as described in
> > RFC2119, if yes need capital letters
> 
> Seciton 2 is more of a background, non-normative section.  It lists some of
> the design objectives.
> 
> > 3.	In section 3.1 "It is optional in the data model,  but if the type
> > represents a physical interface, it is mandatory", suggest having 
> > RFC2119 language "It is OPTIONAL in the data model,  but if the type 
> > represents a physical interface, it is MUST be specified"
> 
> I think the first one should not be OPTIONAL, but the second one is correct.
> So I suggest this:
> 
>   It is defined as being optional in the data model, but if the type
>   represents a physical interface, it MUST be specified.
> 
> 
> /martin
> 

From stbryant@cisco.com  Mon Apr 29 02:19:29 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B39C21F9D17; Mon, 29 Apr 2013 02:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.765
X-Spam-Level: 
X-Spam-Status: No, score=-109.765 tagged_above=-999 required=5 tests=[AWL=0.833, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 al+ScWb2QxU6; Mon, 29 Apr 2013 02:19:28 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id F354021F9D12; Mon, 29 Apr 2013 02:19:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20795; q=dns/txt; s=iport; t=1367227167; x=1368436767; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=1yMBsnFM3SnZFpZDjHuOLhUnaeimQv/VQZ5zMYipzzk=; b=csLZqwzD+FGwkaj1Q94Evk4r8JEZpp308aEsESbQrTRICop89nWJ940Q t08Fquu4uXeLhhDLVsZyRkNnzt4F7keBh2puSsyVaKHXQTcwy16Km4DnP Q0utuVDqgFDECXDug1pDUAQYdhK7vESQgP/dmq3g/HXR1XewKSS6vYY4z Q=;
X-IronPort-AV: E=Sophos;i="4.87,572,1363132800"; d="scan'208,217";a="13159643"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 29 Apr 2013 09:19:26 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3T9JO3t015207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Apr 2013 09:19:24 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r3T9JMwj018269; Mon, 29 Apr 2013 10:19:23 +0100 (BST)
Message-ID: <517E3B1A.4060403@cisco.com>
Date: Mon, 29 Apr 2013 10:19:22 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: stbryant@cisco.com
References: <CABkgnnW-53MVHZaW4QweqBjrPGCrP=fCNQ+LJdaG__ePh2tn1A@mail.gmail.com> <CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com> <517ABCF0.2080701@cisco.com>
In-Reply-To: <517ABCF0.2080701@cisco.com>
Content-Type: multipart/alternative; boundary="------------090704020608090509060806"
Cc: "Bocci, Matthew \(Matthew\)" <matthew.bocci@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, sec-ads@tools.ietf.org, danfrost@cisco.com, "iesg@ietf.org" <iesg@ietf.org>, draft-ietf-mpls-gach-adv.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-gach-adv-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 09:19:29 -0000

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

Now I understand Adrian's comment.

GenArt review did not go to the IESG.

Stewart

On 26/04/2013 18:44, Stewart Bryant wrote:
> Including Sec ADs as this involves a change to the Authentication section.
>
> Section 6.3 now says
>
> The HMAC proceedure described in [RFC2104] is used to compute the hash.
> The hash is computed over the entire GAP message as shown in Fig1.
> The length of the Authentication Data field is always less than or equal
> to the message digest size of the specific hash function that is being
> used, however the implementer needs to consider that although this
> decreases the size of the message, it results in a corresponding
> reduction in the strength of the assurance provided.
> Hash truncation is not RECOMMENDED.
>
> I will address any other security issues in another editing pass and
> respond to their Discuss email.
>
>
> On 10/03/2013 17:52, Martin Thomson wrote:
>> I sent the following review a few weeks back.  I just wanted to make 
>> sure that it didn't get accidentally stored in /dev/null.
>>
>>
>> On 15 February 2013 14:33, Martin Thomson <martin.thomson@gmail.com 
>> <mailto:martin.thomson@gmail.com>> wrote:
>>
>>     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-mpls-gach-adv-06
>>     Reviewer: Martin Thomson
>>     Review Date: 2013-02-15
>>     IETF LC End Date: 2013-02-27
>>     IESG Telechat date: (if known)
>>
>>     Summary: The document is almost ready for publication as proposed
>>     standard.  There is a major issue that should be easy to resolve.
>>
>>     Major issues:
>>
>>     Section 6.3 duplicates the description of HMAC provided in RFC 2104.
>>     That is likely to cause a bug.
>>
>>     If you reference RFC 2104, then the only requirement is a clear
>>     specification for what message is input to the HMAC.  Currently, this
>>     is buried.  It is unclear if the input includes the G-ACh header
>>     defined in RFC 5586 (it doesn't need to, but this needs to be made
>>     explicit).
>>
>>     Filling the authentication part with 0x878FE1F3 seems unnecessary
>>     busy
>>     work, but it's harmless as long as the hash function produces a
>>     multiple of 32 bits of output.
>>
>
> All done please see above.
>>
>>
>>     Minor issues:
>>
>>     To avoid forward compatibility issues, reserved fields should come
>>     with guidance that says: "Implementations of this protocol version
>>     MUST set reserved fields to all zero bits when sending and ignore any
>>     value when receiving messages."
>>
> The following was added just before Fig 1
>
> Implementations of this protocol version MUST set reserved fields in the
> message formats that follow, to all zero bits when sending and ignore
> any value when receiving messages.
>
> I feel that we should just write an update to RFC2119 to automatically
> include this or add it to the standard boiler plate.
>
>
>
>>     In Section 4.4, how does the duration interact with the lifetime?
>>     What happens when the duration is longer than lifetime such that the
>>     TLV is expunged before the duration is up?
>>
> The TLV would be deleted (per procedure) at its death date, and
> would not be sent again until at least duration has expired. This would
> be silly if the receiver wanted that TLV, but entirely reasonable
> if it dis not care about the TLV.
>
>>
>>     Section 5.2 states:
>>        [...] If one
>>        of the received TLV objects has the same Type as a previously
>>        received TLV then the data from the new object SHALL replace
>>     the data
>>        associated with that Type unless the X specification dictates a
>>        different behavior.
>>
>>     This leads to different retention characteristics depending on some
>>     arbitrary application-specific requirements.  It also complicates
>>     implementations.  Is there a strong motivation for the "unless the X
>>     specification dictates a different behavior" part of this statement?
>>
> One can imagine alternative behaviors such as maintaining a list of
> received values. Our goal was not to prejudge the application.
>
>>
>>     If this behaviour is desirable, a note regarding what happens to the
>>     composed TLV when some of the values that contribute to it might
>>     expire might be necessary.
>>
> The behaviour described is the action of the data and not of the TLV that
> it arrived in, so I don't think the problem you refer to can occur.
>
>>
>>     Regarding the last paragraph of Section 6.3:
>>               This also means that the use of hash functions with larger
>>               output sizes will increase the size of the GAP message as
>>               transmitted on the wire.
>>
>>     If you want to prevent hash truncation, then use 'MUST'.  Personally,
>>     I see no reason to do so.  It's a good way to get smaller messages,
>>     with a corresponding reduction in the strength of the assurance
>>     provided.
>>
> Please see new text above.
>
>>
>>     Nits:
>>
>>     Section 3 could use some subheadings to aid navigation (and
>>     referencing).
>>
> Done
>>
>>     Section 3 describes the size of fields only through ASCII-art.
>>      It's a
>>     fairly simple thing to add a bit count to the description of each
>>     field.  That includes the reserved fields, which have no
>>     descriptions.
>>
> Done
>>
>>
>>     I like the text in the editors note on page 8.  Why is it not the
>>     actual text already?
>>
> That was a hang over from AD review that was already addressed in the
> text. The note has been removed.
>>
>>
>>     Sections 4.2 and 4.3 could probably use a note that notes that
>>     retention of these TLVs doesn't make any sense.  These could be sent
>>     with zero lifetime, except that if these are sent along with the
>>     Source Address TLV, that's not possible... unless you send multiple
>>     application data blocks for the same application.  Is that possible?
>>
>>
> I have added the following text in each case:
>
> It is not necessary to retain this TLV.
>
> Thanks for the review
>
> Stewart


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


--------------090704020608090509060806
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Now I understand Adrian's comment.<br>
      <br>
      GenArt review did not go to the IESG.<br>
      <br>
      Stewart<br>
      <br>
      On 26/04/2013 18:44, Stewart Bryant wrote:<br>
    </div>
    <blockquote cite="mid:517ABCF0.2080701@cisco.com" type="cite">
      <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
      <div class="moz-cite-prefix">Including Sec ADs as this involves a
        change to the Authentication section.<br>
        <br>
        Section 6.3 now says<br>
        <br>
        The HMAC proceedure described in [RFC2104] is used to compute
        the hash.<br>
        The hash is computed over the entire GAP message as shown in
        Fig1.<br>
        The length of the Authentication Data field is always less than
        or equal<br>
        to the message digest size of the specific hash function that is
        being <br>
        used, however the implementer needs to consider that although
        this <br>
        decreases the size of the message, it results in a corresponding
        <br>
        reduction in the strength of the assurance provided. <br>
        Hash truncation is not RECOMMENDED.<br>
        <br>
        I will address any other security issues in another editing pass
        and<br>
        respond to their Discuss email.<br>
        <br>
        <br>
        On 10/03/2013 17:52, Martin Thomson wrote:<br>
      </div>
      <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
        type="cite">
        <meta http-equiv="Content-Type" content="text/html;
          charset=UTF-8">
        <div dir="ltr">I sent the following review a few weeks back.Â  I
          just wanted to make sure that it didn't get accidentally
          stored in /dev/null.<br>
        </div>
        <div class="gmail_extra"><br>
          <br>
          <div class="gmail_quote">On 15 February 2013 14:33, Martin
            Thomson <span dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:martin.thomson@gmail.com" target="_blank">martin.thomson@gmail.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">I am the
              assigned Gen-ART reviewer for this draft. For background
              on<br>
              Gen-ART, please see the FAQ at<br>
              <br>
              &lt;<a moz-do-not-send="true"
                href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
                target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br>
              <br>
              Please resolve these comments along with any other Last
              Call comments<br>
              you may receive.<br>
              <br>
              Document: draft-ietf-mpls-gach-adv-06<br>
              Reviewer: Martin Thomson<br>
              Review Date: 2013-02-15<br>
              IETF LC End Date: 2013-02-27<br>
              IESG Telechat date: (if known)<br>
              <br>
              Summary: The document is almost ready for publication as
              proposed<br>
              standard. Â There is a major issue that should be easy to
              resolve.<br>
              <br>
              Major issues:<br>
              <br>
              Section 6.3 duplicates the description of HMAC provided in
              RFC 2104.<br>
              That is likely to cause a bug.<br>
              <br>
              If you reference RFC 2104, then the only requirement is a
              clear<br>
              specification for what message is input to the HMAC.
              Â Currently, this<br>
              is buried. Â It is unclear if the input includes the G-ACh
              header<br>
              defined in RFC 5586 (it doesn't need to, but this needs to
              be made<br>
              explicit).<br>
              <br>
              Filling the authentication part with 0x878FE1F3 seems
              unnecessary busy<br>
              work, but it's harmless as long as the hash function
              produces a<br>
              multiple of 32 bits of output.<br>
            </blockquote>
          </div>
        </div>
      </blockquote>
      <br>
      All done please see above.<br>
      <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
        type="cite">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
              Minor issues:<br>
              <br>
              To avoid forward compatibility issues, reserved fields
              should come<br>
              with guidance that says: "Implementations of this protocol
              version<br>
              MUST set reserved fields to all zero bits when sending and
              ignore any<br>
              value when receiving messages."<br>
              <br>
            </blockquote>
          </div>
        </div>
      </blockquote>
      The following was added just before Fig 1<br>
      <br>
      Implementations of this protocol version MUST set reserved fields
      in the <br>
      message formats that follow, to all zero bits when sending and
      ignore <br>
      any value when receiving messages.<br>
      <br>
      I feel that we should just write an update to RFC2119 to
      automatically <br>
      include this or add it to the standard boiler plate.<br>
      <br>
      <br>
      <br>
      <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
        type="cite">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"> In
              Section 4.4, how does the duration interact with the
              lifetime?<br>
              What happens when the duration is longer than lifetime
              such that the<br>
              TLV is expunged before the duration is up?<br>
            </blockquote>
          </div>
        </div>
      </blockquote>
      The TLV would be deleted (per procedure) at its death date, and<br>
      would not be sent again until at least duration has expired. This
      would<br>
      be silly if the receiver wanted that TLV, but entirely reasonable
      <br>
      if it dis not care about the TLV.<br>
      <br>
      <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
        type="cite">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
              Section 5.2 states:<br>
              Â  Â [...] If one<br>
              Â  Â of the received TLV objects has the same Type as a
              previously<br>
              Â  Â received TLV then the data from the new object SHALL
              replace the data<br>
              Â  Â associated with that Type unless the X specification
              dictates a<br>
              Â  Â different behavior.<br>
              <br>
              This leads to different retention characteristics
              depending on some<br>
              arbitrary application-specific requirements. Â It also
              complicates<br>
              implementations. Â Is there a strong motivation for the
              "unless the X<br>
              specification dictates a different behavior" part of this
              statement?<br>
            </blockquote>
          </div>
        </div>
      </blockquote>
      One can imagine alternative behaviors such as maintaining a list
      of <br>
      received values. Our goal was not to prejudge the application.<br>
      <br>
      <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
        type="cite">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
              If this behaviour is desirable, a note regarding what
              happens to the<br>
              composed TLV when some of the values that contribute to it
              might<br>
              expire might be necessary.<br>
            </blockquote>
          </div>
        </div>
      </blockquote>
      The behaviour described is the action of the data and not of the
      TLV that<br>
      it arrived in, so I don't think the problem you refer to can
      occur.<br>
      <br>
      <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
        type="cite">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
              Regarding the last paragraph of Section 6.3:<br>
              Â  Â  Â  Â  Â  This also means that the use of hash functions
              with larger<br>
              Â  Â  Â  Â  Â  output sizes will increase the size of the GAP
              message as<br>
              Â  Â  Â  Â  Â  transmitted on the wire.<br>
              <br>
              If you want to prevent hash truncation, then use 'MUST'.
              Â Personally,<br>
              I see no reason to do so. Â It's a good way to get smaller
              messages,<br>
              with a corresponding reduction in the strength of the
              assurance<br>
              provided.<br>
            </blockquote>
          </div>
        </div>
      </blockquote>
      Please see new text above.<br>
      <br>
      <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
        type="cite">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
              Nits:<br>
              <br>
              Section 3 could use some subheadings to aid navigation
              (and referencing).<br>
              <br>
            </blockquote>
          </div>
        </div>
      </blockquote>
      Done<br>
      <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
        type="cite">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"> Section
              3 describes the size of fields only through ASCII-art.
              Â It's a<br>
              fairly simple thing to add a bit count to the description
              of each<br>
              field. Â That includes the reserved fields, which have no
              descriptions.<br>
            </blockquote>
          </div>
        </div>
      </blockquote>
      Done<br>
      <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
        type="cite">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
              I like the text in the editors note on page 8. Â Why is it
              not the<br>
              actual text already?<br>
            </blockquote>
          </div>
        </div>
      </blockquote>
      That was a hang over from AD review that was already addressed in
      the <br>
      text. The note has been removed.<br>
      <blockquote
cite="mid:CABkgnnXOcDRkp=6e8aDdhTbk+s=hkR2wCkXoJcWGn8sjrRi2cg@mail.gmail.com"
        type="cite">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
              Sections 4.2 and 4.3 could probably use a note that notes
              that<br>
              retention of these TLVs doesn't make any sense. Â These
              could be sent<br>
              with zero lifetime, except that if these are sent along
              with the<br>
              Source Address TLV, that's not possible... unless you send
              multiple<br>
              application data blocks for the same application. Â Is that
              possible?<br>
            </blockquote>
          </div>
          <br>
        </div>
      </blockquote>
      I have added the following text in each case:<br>
      <br>
      It is not necessary to retain this TLV.<br>
      <br>
      Thanks for the review<br>
      <br>
      Stewart<br>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------090704020608090509060806--

From ron.even.tlv@gmail.com  Mon Apr 29 02:42:33 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 231EC21F9CED; Mon, 29 Apr 2013 02:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
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 lgDPWDG0dwc7; Mon, 29 Apr 2013 02:42:32 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 8FC3921F9CE3; Mon, 29 Apr 2013 02:42:17 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id c10so2529665wiw.0 for <multiple recipients>; Mon, 29 Apr 2013 02:42:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=9ZdZw8l4tDtl82FECtFoX1vKZV+jKx3CIptivd3Cs8s=; b=vyiBqu4xT9SAEq/FISmohpFfz5b8JZ74v5mIcNf7go3LpyUcPbZGaSAwgv4RxSgcmt YsEF3MW3gDJFLI0EK8SLEmEyMB/bmIFHatjaMrFMpbrqkeIMUSZfA0mjofY2a3bNwLuu 6/5EuxrYjT96Ujs4fZCkZ6nfJbbXCSaFILTGjlGs5ixoEmYxVMwt7KXFWEJ4RcV91G1N cm58LMWWLl3jDkojfODPY8P20bqtReVuuOLew5zdPvWy2rIVa1x5ehrMrWjBzr9Qr3vR bb2LBi0moCtTE9urnB5/jTDywrfHNY4gzEWyTO2SFGROLNnSLYrdv+FyCJKYZQUN+jI1 lOwg==
X-Received: by 10.194.10.129 with SMTP id i1mr1574693wjb.21.1367228536716; Mon, 29 Apr 2013 02:42:16 -0700 (PDT)
Received: from RoniE (bzq-79-181-177-28.red.bezeqint.net. [79.181.177.28]) by mx.google.com with ESMTPSA id e8sm13430147wic.5.2013.04.29.02.42.13 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 29 Apr 2013 02:42:15 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Martin Bjorklund'" <mbj@tail-f.com>
References: <019901ce43ea$bbd575a0$338060e0$@gmail.com>	<20130428.115010.513224826.mbj@tail-f.com>	<01ba01ce440c$408d4720$c1a7d560$@gmail.com> <20130429.102542.1993240684524912340.mbj@tail-f.com>
In-Reply-To: <20130429.102542.1993240684524912340.mbj@tail-f.com>
Date: Mon, 29 Apr 2013 12:41:37 +0300
Message-ID: <020b01ce44bd$c0ba0fd0$422e2f70$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFWiDTvx1wg5jy+XbNDGWkbCL4PFgG0N6f1AovlA7wBcSt+GJmu4G7A
Content-Language: en-us
Cc: gen-art@ietf.org, draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 09:42:33 -0000

Hi,
This new text is OK.
Thanks
Roni

-----Original Message-----
From: Martin Bjorklund [mailto:mbj@tail-f.com] 
Sent: 29 April, 2013 11:26 AM
To: ron.even.tlv@gmail.com
Cc: draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org; ietf@ietf.org;
gen-art@ietf.org
Subject: Re: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10

Hi,

"Roni Even" <ron.even.tlv@gmail.com> wrote:
> Martin,
> Thanks for the response. I am OK with your responses to the nits.
> 
> As for the comment on location I think I understand but what got me 
> thinking was the examples.
> In E.1
> 
> "An operator can configure a new interface by sending an <edit-config>
>    containing:
> 
>      <interface nc:operation="create">
>        <name>fastethernet-1/0</name>
>      </interface>
> 
>    When the server processes this request, it will set the leaf "type"
>    to "ethernetCsmacd" and "location" to "1/0".  Thus, if the client
>    performs a <get-config> right after the <edit-config> above, it will
>    get:
> 
>      <interface>
>        <name>fastethernet-1/0</name>
>        <type>ethernetCsmacd</type>
>        <location>1/0</location>
>      </interface>"
> 
> I can see how the linkage between the location and name is done. I am 
> not sure how the operator knows from the response what is the physical 
> location without knowing the device type and manufacturer but at least 
> the linkage is there and this is why I thought of it more as a logical 
> device and not physical one.

Ok.  Since this is an example of a configuration of a physical interface, it
is assumed that the operator somehow knows which physical port is being
reconfigured -- somehow the operator must be able to know what the port
where the new cable was inserted is called in the config.

But it makes sense to be more clear about this.  How about this
change:


OLD:

  The implementation restricts the names of the interfaces to one of
  "fastethernet-N/M" or "gigabitethernet-N/M".  The "location" of an
  interface is a string on the form "N/M".  The implementation
  auto-initializes the values for "type" and "location" based on the
  interface name.

NEW:

  The implementation restricts the names of the interfaces to one of
  "fastethernet-N/M" or "gigabitethernet-N/M".  The "location" of an
  interface is a string on the form "N/M".  It is assumed that the
  operator is aware of this naming scheme.  The implementation
  auto-initializes the values for "type" and "location" based on the
  interface name.

> When looking at E2.2 example

(ditto for this example.)


/martin



>   " An operator can configure a new interface by sending an <edit-config>
>    containing:
> 
>      <interface nc:operation="create">
>        <name>acme-interface</name>
>        <type>ethernetCsmacd</type>
>        <location>1/0</location>
>      </interface>"
> 
> Here the operator need to know the device to configure a specific 
> interface and know how many interface exist and how they are named. So 
> you assume that for this case this is known to the configuration.
> 
> Roni
> 
> 
> 
> 
> -----Original Message-----
> From: Martin Bjorklund [mailto:mbj@tail-f.com]
> Sent: 28 April, 2013 12:50 PM
> To: ron.even.tlv@gmail.com
> Cc: draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org; 
> ietf@ietf.org; gen-art@ietf.org
> Subject: Re: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
> 
> Hi,
> 
> Thank you for your review.  Comments inline.
> 
> "Roni Even" <ron.even.tlv@gmail.com> wrote:
> > 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-netmod-interfaces-cfg-10
> > 
> > Reviewer: Roni Even
> > 
> > Review Date:2013-4-28
> > 
> > IETF LC End Date: 2013-5-3
> > 
> > IESG Telechat date: 2013-5-16
> > 
> >  
> > 
> > Summary: This draft is almost ready for publication as Standard track
RFC.
> > 
> >  
> > 
> >  
> > 
> > Major issues:
> > 
> >  
> > 
> > Minor issues:
> > 
> >  
> > 
> > 1.       I had some problem understanding the "location" leaf. Section
3.2
> > has it as a string and says that "The device uses the location 
> > string to identify the physical or logical entity that the 
> > configuration applies
> to".
> > I am not sure how you identify physical location having no 
> > definition of the mapping.
> 
> The sentence just before the quoted one above says:
> 
>   "The format of this string is device- and type-dependent."
> 
> and then the text says:
> 
>   "How a client can learn which types and locations are present on a
>   certain device is outside the scope of this document."
> 
> So the exact procedure is currently left to the vendors, but may be 
> standardized in a future document (if possible...)
> 
> > I saw the examples in Appendix E and it looked more to me as logical 
> > mapping but not physical since it attaches a name to something in 
> > the device but I am not clear how you know what it is physically in 
> > the device. If the name 0-n or n/m are real physical entities, I 
> > think that it should be specified some place.
> > 
> >  
> > 
> >  
> > 
> > Nits/editorial comments:
> > 
> > 1.	In the introduction section maybe add to the first sentence a
> > reference to RFC6244 with some text.
> 
> Ok, this probably makes sense.  I will check w/ the WG and other
documents.
> 
> 
> 
> > 2.	In section 2 are the" must" and "should"  used as described in
> > RFC2119, if yes need capital letters
> 
> Seciton 2 is more of a background, non-normative section.  It lists 
> some of the design objectives.
> 
> > 3.	In section 3.1 "It is optional in the data model,  but if the type
> > represents a physical interface, it is mandatory", suggest having
> > RFC2119 language "It is OPTIONAL in the data model,  but if the type 
> > represents a physical interface, it is MUST be specified"
> 
> I think the first one should not be OPTIONAL, but the second one is
correct.
> So I suggest this:
> 
>   It is defined as being optional in the data model, but if the type
>   represents a physical interface, it MUST be specified.
> 
> 
> /martin
> 


From rjsparks@nostrum.com  Mon Apr 29 06:45:19 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFF1621F9DAC; Mon, 29 Apr 2013 06:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.393
X-Spam-Level: 
X-Spam-Status: No, score=-101.393 tagged_above=-999 required=5 tests=[AWL=1.208, 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 jErcWkT5NVVT; Mon, 29 Apr 2013 06:45:16 -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 C838C21F9DAD; Mon, 29 Apr 2013 06:45:15 -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 r3TDjB1R056419 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Mon, 29 Apr 2013 08:45:11 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <517E796E.6040402@nostrum.com>
Date: Mon, 29 Apr 2013 08:45:18 -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: mohamed.boucadair@orange.com
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr> <517AA910.8030608@nostrum.com> <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EC9B49B02@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EC9B49B02@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 13:45:19 -0000

On 4/29/13 12:59 AM, mohamed.boucadair@orange.com wrote:
> Robert,
>
> Ted suggested a wording which is better than the one I proposed. I made the following changes my local copy:
>
> (1)
>
> OLD:
>     When retransmission is required, the relay may decide to correct the
>     content of RECONFIGURE-REQUEST message it issues (e.g., update the
>     Client Identifier list).
>
> NEW:
>     The relay MAY remove clients from the client identifier list in
>     subsequent retransmissions, but MUST NOT add clients to the client
>     identifier list.
>
> (2)
>
> OLD:
>     Furthermore, means to recover state in failure events must be
>     supported, but are not discussed in this document.
>
> NEW:
>     Furthermore, means to recover state in failure events (e.g.,
>     [RFC5460]) must be supported, but are not discussed in this document.
>
> Is this better?
1 is better.

2 is an improvement, I might say "such as" instead of e.g. to even more
strongly avoid someone thinking you are _requiring_ implementation of
RFC5460.  Even then, it's still not clear whether you're trying to say

"Something that doesn't do this is does not conform to this specification"

or

"Something that doesn't do this isn't as good a tool as it can be and 
may create a condition that operators and users will not like much."

You chose not to use MUST in that sentence. Can you make it less likely 
that someone will assume you meant to?
>
> Cheers,
> Med
>
>
>> -----Message d'origine-----
>> De : Bernie Volz (volz) [mailto:volz@cisco.com]
>> Envoyé : samedi 27 avril 2013 06:24
>> Ŕ : Robert Sparks; BOUCADAIR Mohamed OLNC/OLN
>> Cc : dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf-
>> dhc-triggered-reconfigure@tools.ietf.org
>> Objet : RE: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>> reconfigure-05
>>
>> Robert:
>>
>> The reason to allow this is that otherwise client A will be unnecessarily
>> reconfigured many times. (It is also possible that a client might Renew on
>> its own just as this is happening and thus it can also be removed from the
>> Reconfigure.)
>>
>> I think the text should be cleaned up to indicate that allowing removal of
>> already reconfigured clients is recommended (to prevent unnecessary
>> reconfigures) when retransmitting the Reconfigure-Request.
>>
>> Note that if clients are added, that is not a retransmission but requires a
>> "new" message (new XID).
>>
>> - Bernie
>>
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
>> Robert Sparks
>> Sent: Friday, April 26, 2013 12:19 PM
>> To: mohamed.boucadair@orange.com
>> Cc: dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf-
>> dhc-triggered-reconfigure@tools.ietf.org
>> Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>> reconfigure-05
>>
>> On 4/26/13 10:58 AM, mohamed.boucadair@orange.com wrote:
>>> Dear Robert,
>>>
>>> Thank you for the review.
>>> Please see inline.
>>>
>>> Cheers,
>>> Med
>>> ________________________________________
>>> De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de
>>> Robert Sparks [rjsparks@nostrum.com] Date d'envoi : vendredi 26 avril
>>> 2013 17:42 Ŕ : dhcwg@ietf.org; ietf@ietf.org; General Area Review
>>> Team; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
>>> Objet : [dhcwg] Gen-art review:
>>> draft-ietf-dhc-triggered-reconfigure-05
>>>
>>> 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><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-dhc-triggered-reconfigure-05
>>> Reviewer:  Robert Sparks
>>> Review Date: April 26, 2013
>>> IETF LC End Date: May 6, 2013
>>> IESG Telechat date: May 16, 2013
>>>
>>> Summary: This draft is on the right track but has open issues, described
>> in
>>>         the review.
>>>
>>> Major issues:
>>>
>>> Overall, this document is solid, but I think there is a bug in section
>> 6.3.
>>> I could be wrong, but If I'm right, this paragraph:
>>>
>>> When retransmission is required, the relay may decide to correct the
>> content of RECONFIGURE-REQUEST message it issues (e.g., update the Client
>> Identifier list).  This decision is local to the relay (e.g., it may be
>> based on observed events such as one or more clients were reconfigured on
>> their own).
>>> introduces a race-condition that could lead to an erroneous state. If a
>> relay's first message included client A, then the retransmission included
>> clients A and B, but that retransmission crosses with a success
>> RECONFIGURE-REPLY to the request that only included client A, the relay
>> will think it succeeded in asking A and B to be reconfigured.
>>> Med: This example does not apply for that text.
>> Really? What text constrains how you change what's in the retransmission?
>>>    In fact, the example should be the other way around. Perhaps, this can
>> be made clearer if we change "(e.g., update the Client Identifier list)" to
>> "(e.g., remove a client from the Client Identifier list)".
>> If I understand you correctly, you need more than just changing a
>> parenthetical e.g.. I think you're saying that you are constraining the
>> message changes to be such that if anything earlier in the retransmission
>> sequence succeeded, the request in the retransmission would also have
>> succeeded. But why do you need that much complexity? Do you have it already
>> with any other request?
>>> Minor issues:
>>>
>>> This sentence:
>>>
>>> Furthermore, means to recover state in failure events must be supported,
>> but are not discussed in this document.
>>> places a requirement on a relay (even though it's not using a 2119 MUST).
>> Is there some other document that defines this requirement that you can
>> reference?
>>> Med: I'm not aware of any; but if there is one we can cite it.
>>>
>>>    If not, the requirement should be discussed in this document.
>> Alternatively, you could change the sentence to talk about the consequences
>> of not having a proprietary means for recovering state.
>>> Med: Will consider that option if you think this is really needed.
>>>
>>> Nits/editorial comments:
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg


From volz@cisco.com  Mon Apr 29 07:18:36 2013
Return-Path: <volz@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85A3121F9D80; Mon, 29 Apr 2013 07:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id donM72n4hjJv; Mon, 29 Apr 2013 07:18:35 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 3C0A921F9D8C; Mon, 29 Apr 2013 07:18:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8804; q=dns/txt; s=iport; t=1367245115; x=1368454715; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=79UA9FLZu0g3FxXvLo4Lkql6GqmmOh0mD/nUOcM1nj8=; b=WofcX8Csqxt7HQophfHOch7vXGgkL+Fi4pD18TI3tOkhKCrl/nEHZSBB 7ykO45ILrIviQE5OM5vpv+BfCcnuZeCcr87wqChEIFN1agthDP7zZR+CN LL+X7b4pq9WWkydEQjz854u4GYqH2l0WaX/rM9geXmMfXdg5VOGwJXDcv U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFALCAflGtJXG8/2dsb2JhbABTgwc2vkCBAxZ0gh8BAQEEAQEBawsMBAIBCA4DAwEBAQEKHQcnCxQJCAIEAQ0FCBOHewy7RI1uezEHBoJoYQOIWoNFhzCEdYVfiiWDEYFrPQ
X-IronPort-AV: E=Sophos;i="4.87,574,1363132800"; d="scan'208";a="204307575"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-6.cisco.com with ESMTP; 29 Apr 2013 14:18:34 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3TEIY57002491 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 29 Apr 2013 14:18:34 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.31]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.004; Mon, 29 Apr 2013 09:18:34 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Index: AQHORN/GDK4q6qizh0K41HkFQ0/z/ZjtOjmg
Date: Mon, 29 Apr 2013 14:18:33 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1851F76A@xmb-rcd-x04.cisco.com>
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr> <517AA910.8030608@nostrum.com> <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EC9B49B02@PUEXCB1B.nanterre.francetelecom.fr> <517E796E.6040402@nostrum.com>
In-Reply-To: <517E796E.6040402@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.247.178]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>
Subject: Re: [Gen-art] [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 14:18:36 -0000

FYI - Stable storage or some kind of redundancy solution may be another way=
 to recover state. So, I don't think there is a hard requirement for RFC 54=
60.

I don't think there is a strong reason to avoid e.g., it is "for example" s=
o it is only one of many possible. And "such as" is basically saying the sa=
me thing.

---

But then we come to why this is even important ... The original text was:

   This setup assumes the relay has a record of the client, so that it
   has enough information to send the Reconfigure-Request message to the
   server.  How the state is recorded in the relay is out of scope.
   Furthermore, means to recover state in failure events must be
   supported, but are not discussed in this document.

I'm a bit skeptical why this draft even brings the 'recover state' up. Yes,=
 the relay does need to record the client in order to initiate a Reconfigur=
e-Request. But I think the sentence "Furthermore, means to recover state in=
 failure events must be supported, but are not discussed in this document."=
 is not needed. Sure, if the relay has no way of recovering this state, tra=
ffic to/from clients will likely not work and certainly if the relay is rec=
onfigured, it will be unable to generate a Reconfigure-Request. But I don't=
 really see this draft needing this requirement. Reconfigure-request could =
still work until the state is lost. And if the state is lost, there is a lo=
t more than is potentially broken.

But I don't really see this as a big issue and the "must" is the lower-case=
 variant anyway.

- Bernie

-----Original Message-----
From: Robert Sparks [mailto:rjsparks@nostrum.com]=20
Sent: Monday, April 29, 2013 9:45 AM
To: mohamed.boucadair@orange.com
Cc: Bernie Volz (volz); dhcwg@ietf.org; General Area Review Team; ietf@ietf=
.org; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfig=
ure-05

On 4/29/13 12:59 AM, mohamed.boucadair@orange.com wrote:
> Robert,
>
> Ted suggested a wording which is better than the one I proposed. I made t=
he following changes my local copy:
>
> (1)
>
> OLD:
>     When retransmission is required, the relay may decide to correct the
>     content of RECONFIGURE-REQUEST message it issues (e.g., update the
>     Client Identifier list).
>
> NEW:
>     The relay MAY remove clients from the client identifier list in
>     subsequent retransmissions, but MUST NOT add clients to the client
>     identifier list.
>
> (2)
>
> OLD:
>     Furthermore, means to recover state in failure events must be
>     supported, but are not discussed in this document.
>
> NEW:
>     Furthermore, means to recover state in failure events (e.g.,
>     [RFC5460]) must be supported, but are not discussed in this document.
>
> Is this better?
1 is better.

2 is an improvement, I might say "such as" instead of e.g. to even more str=
ongly avoid someone thinking you are _requiring_ implementation of RFC5460.=
  Even then, it's still not clear whether you're trying to say

"Something that doesn't do this is does not conform to this specification"

or

"Something that doesn't do this isn't as good a tool as it can be and may c=
reate a condition that operators and users will not like much."

You chose not to use MUST in that sentence. Can you make it less likely tha=
t someone will assume you meant to?
>
> Cheers,
> Med
>
>
>> -----Message d'origine-----
>> De : Bernie Volz (volz) [mailto:volz@cisco.com] Envoy=E9 : samedi 27=20
>> avril 2013 06:24 =C0 : Robert Sparks; BOUCADAIR Mohamed OLNC/OLN Cc :=20
>> dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf-=20
>> dhc-triggered-reconfigure@tools.ietf.org
>> Objet : RE: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>> reconfigure-05
>>
>> Robert:
>>
>> The reason to allow this is that otherwise client A will be=20
>> unnecessarily reconfigured many times. (It is also possible that a=20
>> client might Renew on its own just as this is happening and thus it=20
>> can also be removed from the
>> Reconfigure.)
>>
>> I think the text should be cleaned up to indicate that allowing=20
>> removal of already reconfigured clients is recommended (to prevent=20
>> unnecessary
>> reconfigures) when retransmitting the Reconfigure-Request.
>>
>> Note that if clients are added, that is not a retransmission but=20
>> requires a "new" message (new XID).
>>
>> - Bernie
>>
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On=20
>> Behalf Of Robert Sparks
>> Sent: Friday, April 26, 2013 12:19 PM
>> To: mohamed.boucadair@orange.com
>> Cc: dhcwg@ietf.org; General Area Review Team; ietf@ietf.org;=20
>> draft-ietf- dhc-triggered-reconfigure@tools.ietf.org
>> Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>> reconfigure-05
>>
>> On 4/26/13 10:58 AM, mohamed.boucadair@orange.com wrote:
>>> Dear Robert,
>>>
>>> Thank you for the review.
>>> Please see inline.
>>>
>>> Cheers,
>>> Med
>>> ________________________________________
>>> De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de=20
>>> Robert Sparks [rjsparks@nostrum.com] Date d'envoi : vendredi 26=20
>>> avril
>>> 2013 17:42 =C0 : dhcwg@ietf.org; ietf@ietf.org; General Area Review=20
>>> Team; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
>>> Objet : [dhcwg] Gen-art review:
>>> draft-ietf-dhc-triggered-reconfigure-05
>>>
>>> I am the assigned Gen-ART reviewer for this draft. For background on=20
>>> Gen-ART, please see the FAQ at
>>>
>>>
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq><http://wiki
>> .tools .ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>> Please resolve these comments along with any other Last Call=20
>>> comments you may receive.
>>>
>>> Document: draft-ietf-dhc-triggered-reconfigure-05
>>> Reviewer:  Robert Sparks
>>> Review Date: April 26, 2013
>>> IETF LC End Date: May 6, 2013
>>> IESG Telechat date: May 16, 2013
>>>
>>> Summary: This draft is on the right track but has open issues,=20
>>> described
>> in
>>>         the review.
>>>
>>> Major issues:
>>>
>>> Overall, this document is solid, but I think there is a bug in=20
>>> section
>> 6.3.
>>> I could be wrong, but If I'm right, this paragraph:
>>>
>>> When retransmission is required, the relay may decide to correct the
>> content of RECONFIGURE-REQUEST message it issues (e.g., update the=20
>> Client Identifier list).  This decision is local to the relay (e.g.,=20
>> it may be based on observed events such as one or more clients were=20
>> reconfigured on their own).
>>> introduces a race-condition that could lead to an erroneous state.=20
>>> If a
>> relay's first message included client A, then the retransmission=20
>> included clients A and B, but that retransmission crosses with a=20
>> success RECONFIGURE-REPLY to the request that only included client A,=20
>> the relay will think it succeeded in asking A and B to be reconfigured.
>>> Med: This example does not apply for that text.
>> Really? What text constrains how you change what's in the retransmission=
?
>>>    In fact, the example should be the other way around. Perhaps,=20
>>> this can
>> be made clearer if we change "(e.g., update the Client Identifier=20
>> list)" to "(e.g., remove a client from the Client Identifier list)".
>> If I understand you correctly, you need more than just changing a=20
>> parenthetical e.g.. I think you're saying that you are constraining=20
>> the message changes to be such that if anything earlier in the=20
>> retransmission sequence succeeded, the request in the retransmission=20
>> would also have succeeded. But why do you need that much complexity?=20
>> Do you have it already with any other request?
>>> Minor issues:
>>>
>>> This sentence:
>>>
>>> Furthermore, means to recover state in failure events must be=20
>>> supported,
>> but are not discussed in this document.
>>> places a requirement on a relay (even though it's not using a 2119 MUST=
).
>> Is there some other document that defines this requirement that you=20
>> can reference?
>>> Med: I'm not aware of any; but if there is one we can cite it.
>>>
>>>    If not, the requirement should be discussed in this document.
>> Alternatively, you could change the sentence to talk about the=20
>> consequences of not having a proprietary means for recovering state.
>>> Med: Will consider that option if you think this is really needed.
>>>
>>> Nits/editorial comments:
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg


From Ted.Lemon@nominum.com  Mon Apr 29 07:37:45 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 742D221F9E4C; Mon, 29 Apr 2013 07:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 nH7-+zp8Gqi1; Mon, 29 Apr 2013 07:37:44 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 66C6521F9E4B; Mon, 29 Apr 2013 07:37:44 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUX6FuHVrwVi3MoijUi9NKPyAb/1Bzlfv@postini.com; Mon, 29 Apr 2013 07:37:44 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0DE851B813F; Mon, 29 Apr 2013 07:37:44 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 017B2190061; Mon, 29 Apr 2013 07:37:44 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 29 Apr 2013 07:37:44 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Black, David" <david.black@emc.com>
Thread-Topic: Gen-ART review of draft-ietf-karp-crypto-key-table-07
Thread-Index: Ac5ByJPFxMQV0ntvRsGIbN7yaluElADGrB/i//p5/YCABgMJAA==
Date: Mon, 29 Apr 2013 14:37:43 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751666F9@mbx-01.win.nominum.com>
References: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com> <tsla9omh811.fsf@mit.edu> <8D3D17ACE214DC429325B2B98F3AE71293F3BDB0@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293F3BDB0@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EA362B2EEBE8244F8BD734E09226EE7D@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "<stbryant@cisco.com>" <stbryant@cisco.com>, Sam Hartman <hartmans-ietf@mit.edu>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-karp-crypto-key-table-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 14:37:45 -0000

On Apr 25, 2013, at 2:49 PM, "Black, David" <david.black@emc.com> wrote:
> I have no problem with the field being a binary identifier, but I think
> implementers should be put on notice that binary comparison of human inpu=
t
> Unicode strings doesn't work as expected unless some things are done to
> make it work (this used to be known as string preparation).

+1.


From dromasca@avaya.com  Mon Apr 29 07:40:00 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF7F21F9E53 for <gen-art@ietfa.amsl.com>; Mon, 29 Apr 2013 07:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 yrG+Wrew4K5F for <gen-art@ietfa.amsl.com>; Mon, 29 Apr 2013 07:39:59 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF8D21F9E50 for <gen-art@ietf.org>; Mon, 29 Apr 2013 07:39:52 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAAH/ZlHGmAcF/2dsb2JhbABQgmUhNsFIgQcWdIIfAQEBAQIBEigxAwsFDQEVBw4UQiYBBA4FCBqHbAYBC6A8nSONZIEBMYJnYQOYI4UGimiDC4FsBxcGGA
X-IronPort-AV: E=Sophos;i="4.87,456,1363147200";  d="scan'208";a="9081290"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 29 Apr 2013 10:39:52 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 29 Apr 2013 10:35:58 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.02.0328.009; Mon, 29 Apr 2013 10:39:50 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: General Area Review Team <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-oauth-revocation-07
Thread-Index: Ac5E52cDcIE97d4oRRqizdgweQp7gw==
Date: Mon, 29 Apr 2013 14:39:50 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA0D7335@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-oauth-revocation.all@tools.ietf.org" <draft-ietf-oauth-revocation.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-oauth-revocation-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 14:40:00 -0000

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, 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 m=
ay receive.

Document: draft-ietf-oauth-revocation-07
Reviewer: Dan Romascanu
Review Date: 4/29/13
IETF LC End Date: 4/30/13
IESG Telechat date: (if known)

Summary: Almost Ready - it's a relatively simple, clear and well written do=
cument. However there is one issue related to the IANA policy for the new r=
egistry defined by this document which must be clarified before the documen=
t is approved. A couple of minor issues also need clarification and fixing.=
=20

Major issues:

I have found one major issue related to the Type Hint Registry policy descr=
ibed in Section 5.1.2.=20

> This specification establishes the OAuth Token Type Hint registry.
   Possible values of the parameter "token_type_hint" (see Section 2.1)
   are registered with a Specification Required ([RFC5226]) after a two-
   week review period on the TBD@ietf.org mailing list, on the advice of
   one or more Designated Experts.  However, to allow for the allocation
   of values prior to publication, the Designated Expert(s) may approve
   registration once they are satisfied that such a specification will
   be published.  Registration requests must be sent to the TBD@ietf.org
   mailing list for review and comment, with an appropriate subject
   (e.g., "Request for parameter: example").  Within the review period,
   the Designated Expert(s) will either approve or deny the registration
   request, communicating this decision to the review list and IANA.
   Denials should include an explanation and, if applicable, suggestions
   as to how to make the request successful.  IANA must only accept
   registry updates from the Designated Expert(s) and should direct all
   requests for registration to the review mailing list.

I find this way of applying the Specification Required policy problematic. =
According to RFC 5226 '... Values and their meanings must be documented in =
a permanent and readily available public specification ...'. Allowing for a=
n approval by the Designated Expert in the absence of a readily available p=
ublic specification based on the promise that 'such a specification will be=
 published' seems to be contradictory to the definition of the policy. Why =
not just Expert Review?=20

Conditioning Specification Required policies on 'a two-week reviews period =
on the TBD@ietf.org mailing list also seems contrary the spirit of RFC 5226=
. A specification is a specification, it's the role of the Designated Exper=
t to validate for IANA the specification, he may use a mail list, expert te=
am, or just his own expertise, but this needs not be defined here. Mail lis=
ts are ephemeral entities relative to the stability implied by the Specific=
ation required policy, and of course, TBD@ietf.org is hardly acceptable at =
this phase of approval.


Minor issues:

1. [RFC5226] mentioned in Section 5.1.2 is not included in the list of refe=
rences.

2. There is no indication what does the server in the case when an erroneou=
s token_type_hint parameter is passed. Error Response is defined in 2.1.1 f=
or unsupported_token_type but not for the case when for example a client se=
nds a hint that indicates an access_token with a revocation request for a r=
efresh token? Can this optional information supposed to help for quicker lo=
ok-up of the tokens by the server be used for a DoS attack by a malicious c=
lient?=20

Nits/editorial comments:



From meral.shirazipour@ericsson.com  Mon Apr 29 08:54:02 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92D4821F9DCF for <gen-art@ietfa.amsl.com>; Mon, 29 Apr 2013 08:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 PbUwvNoC9mVz for <gen-art@ietfa.amsl.com>; Mon, 29 Apr 2013 08:54:01 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 0435F21F9CEF for <gen-art@ietf.org>; Mon, 29 Apr 2013 08:54:00 -0700 (PDT)
X-AuditID: c6180641-b7faf6d00000096b-a4-517e9797df8b
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 8A.BA.02411.8979E715; Mon, 29 Apr 2013 17:54:00 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0328.009; Mon, 29 Apr 2013 11:53:59 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-spfbis-4408bis.all@tools.ietf.org" <draft-ietf-spfbis-4408bis.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-spfbis-4408bis-14
Thread-Index: Ac5E8TAp1Uzt+JVUT4+YBfRG37sjDg==
Date: Mon, 29 Apr 2013 15:53:59 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A0D4633@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A0D4633eusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCLMWRmVeSWpSXmKPExsUyuXRPoO6M6XWBBm2/pS12Tn3FanH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvj0MQzzAUXNzJWfLy/lKWB8ccsxi5GTg4J AROJ1inHmCBsMYkL99azdTFycQgJHGWUWPF6DQuEs5xR4suqfawgVWwCFhLbfz9nBUmICPQw Siy59hvI4eAQFnCUWP7IGKRGRMBN4sTeWawQtp7E7JPbmEFsFgFViQVH74Nt4xXwlph+aDOY zQi0+fupNWA2s4C4xK0n86EuEpBYsuc8M4QtKvHy8T9WCFtZYsmT/SwQ9fkS997OZoWYKShx cuYTlgmMQrOQjJqFpGwWkjKIuI7Egt2f2CBsbYllC18zw9hnDjxmQhZfwMi+ipGjtDi1LDfd yHATIzAmjkmwOe5gXPDJ8hCjNAeLkjjvNKnKQCGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2M +39I7Prldevmne0HnZa1vP988vKBWOYi5sZs7iefe3Oblq+cdbBaz75pocqcCzzehaWqv+ep 5+btyd8aE1X23PffhC1SF7IlGqKZuN7z33pYc3xOqdjTiyvX7pI8G3ol4XrJzhc6nVada7fF T3Bf3WO+5drdGbtLp2V2f97+N1c80tfnJMf3rUosxRmJhlrMRcWJABkXMJlXAgAA
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-spfbis-4408bis-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 15:54:02 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A0D4633eusaamb107ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at http://wiki.tools.ietf.org/area/gen/trac/wiki/GenA=
rtfaq  .

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-spfbis-4408bis-14
Reviewer: Meral Shirazipour
Review Date: 2013-04-29
IETF LC End Date: 2013-04-30
IESG Telechat date: NA



Summary:
This draft is almost ready to be published as Informational RFC but I do ha=
ve some comments.


Nits/editorial comments:
-[Page 6] Section "1.1.2.  Imported Definitions"
Please consider expanding acronyms and giving the section of the RFC where =
each term is defined.
(Also throughout the document it would greatly help the readability if acro=
nyms are expanded when first used.)

-[Page 8] Section 2.2. Line 1:
""MAIL FROM" -> extra \"

-[Page 13], Section 3.3. , first line: "sections 3.3.14 and 3.3".
If both subsection and subsubsection are to be mentioned, please consider: =
"sections 3.3 and 3.3.14"

-[Page 16], Section 4.3, paragraph 1, last sentence: extra text/typo to be =
removed: "on 2.3 of [RFC5890]."

-[Page 16], Section 4.4, paragraph 3,"[RFC2308] suggests on an" --remove "o=
n"--> "[RFC2308] suggests an"

-[Page 21], Section 5.1, line 1,
"This section defines two types of mechanisms." --for clarity--> "This sect=
ion defines two types of mechanisms: basic and designated sender."

-[Page 21], second paragraph before last, " both "AAAA" and "A" secords "--=
typo--> "records"

-[Page 22], Section 5.2, point 3, please review  "include: mechanism" and "=
\"fail ".
Suggestion: instead of "gives a pass" or "gives a fail" is it better to say=
 "signifies" or "represents" as pass/fail?

-[Page 22], second paragraph before last,
"Only the evaluated result of the referenced SPF record is used, rather tha=
n acting as if the referenced SPF
record was literally included in the first."
The part after the comma in this sentence is hard to understand. Please rev=
iew if possible.

-[Page 24], Section 5.4,
"the evaluation terminated"--missing is-->"the evaluation is terminated"
"has no MX records"--no s-->"has no MX record"

-[Page 26], first paragraph,
"and more reliable alternatives used instead"---->"and more reliable altern=
atives should be used instead"

"still in use and part of"---->"still in use as part of"

-[Page 29], paragraph 3,
"is generally be"---->"will generally be"

-[Page 30], paragraph 1,
"such as shown in Section 2.6.4",- is this pointing to the correct section?

-[Page 30], last sentence
"Note: During recursion into an "include" mechanism, an exp=3D modifier
   from the <target-name> MUST NOT be used.  In contrast, when executing
   a "redirect" modifier, an exp=3D modifier from the original domain MUST
   NOT be used.
"
Is it possible to add 1-2 sentence to explain why?(what is the expected con=
sequence if this is not respected)

-[Page 32], line 3,
"p =3D the validated domain name of <ip> (do not use)"
Is it possible to add a reference to section 5.5 which explains why?
Suggested: "(do not use, see Section 5.5)"

-[Page 33], third paragraph before last
"was provide more than once"---->"was provided more than once"

-[Page 34], last "Note":
"....for as long as the shortest Time To Live (TTL) of all the DNS records =
involved."
Please review this sentence ending. It is not clear.
Suggestion: "as long as the DNS record involved with the shortest TTL has n=
ot expired" ?

-[Page 36], sentence 2, "Terse definitions"--typo-->"The definitions"

-[Page 36], paragraph 2,"be explicity"--typo-->"be explicitly"

-[Page 36], Section 8.1,"checked idenity"--typo-->"checked identity"

-[Page 37], Section 8.4, "the 5.7.1 enhanced status code", with reference t=
o RFC3463.
For better clarity please consider adding reference to Section 3.8 of the R=
FC3463.

-[Page 38], Section 8.6,
For better clarity please consider referring to Section 3.5 of RFC3463

-[Page 38], Section 8.8,
For better clarity please consider referring to Section 3.6 of RFC3463

-[Page 39], Section 9 Title, "Recording The Result"---->"the"

-[Page 44], Line 2, "carefully weight"---->"carefully weigh"

-[Page 44], Section 10.1.2, ""ip4" and "ip6" over "a" or "a" or "mx"."
The last part should suggest "mx' over "a" or the reverse?

-[Page 46], Section 10.3 "User actor.[RFC5598]."---->"User actor [RFC5598].=
"

-[Page 47], before last sentence, missing closing parenthesis:"(defined in =
Section 4.6.4."

-[Page 49], Section 11.5.3, "It is necesary"--typo-->"It is necessary"

-[Page 62], line 2, "to implmentation"--typo-->"to implementation"

-[Page 62], second bullet before last, "Section 10 and Appendices D - H bel=
ow.", is this part of the sentence refering to anything, below?

-[Page 65], Section E.3, "Receving ADMDs"--typo-->"Receiving ADMDs"

-[Page 66], last line, "mitiate"--typo-->"mitigate"

-[Page 68], one line before last, "reliabilility"--typo-->"reliability"

-[Page 70], paragraphe 2,
"techincal"--typo-->"technical"
"deplyment"--typo-->"deployment"

-[Page 72], line 7, "obslete"--typo-->"obsolete"

-[Page 72], 2 line before last, "text and figures from Alessandro Vesely", =
is it only to section 9.1, or 10.1.1. as well?

-[Page 73], "Added new section 9 discussion on treatment of bounces", is it=
 section 9 or section 10.1.3?

-[Page 73], 1 line before last, "potental"--typo-->"potential"

-Appendix J., please review the 'section references' pointing to various ch=
anges.



-Throughout the draft, DNS "look up"---->"lookup"

-Throughout the draft, DNS RCODEs are mentioned without any reference to RF=
C1035 (or RFC6195)

-Throughout the draft, many cross references break the follow. I suggested =
revisiting some of them and adding a small text after each reference which =
introduces that section.
Example :[Page 17], Section 4.6.2 "the result is specified in Section 4.7",=
 suggested-->"the result is specified in Section 4.7 where Default results =
are discussed"

-"Section 2.6 Results of Evaluation" lists the possible outputs of check_ho=
st().
Then "Section 8.  Result Handling" continues the description with handling =
guidance.
To avoid breaking the flow, please consider moving the descriptive content =
of Section 2.6 into Section 8. (unless there is another reason to keep them=
 far apart).




Best Regards,
Meral

---
Meral Shirazipour
Ericsson Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A0D4633eusaamb107ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> &nbsp;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CA">Document: draft-ietf-spfbis-440=
8bis-14<o:p></o:p></span></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-04-29<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-04-30<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: NA<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is almost ready to be published as Inform=
ational RFC but I do have some comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 6] Section &quot;1.1.2.&nbsp; Imported Defini=
tions&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">Please consider expanding acronyms and giving the se=
ction of the RFC where each term is defined.
<o:p></o:p></p>
<p class=3D"MsoNormal">(Also throughout the document it would greatly help =
the readability if acronyms are expanded when first used.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 8] Section 2.2. Line 1:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;&quot;MAIL FROM&quot; -&gt; extra \&quot;<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 13], Section 3.3. , first line: &quot;section=
s 3.3.14 and 3.3&quot;.
<o:p></o:p></p>
<p class=3D"MsoNormal">If both subsection and subsubsection are to be menti=
oned, please consider: &quot;sections 3.3 and 3.3.14&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 16], Section 4.3, paragraph 1, last sentence:=
 extra text/typo to be removed: &quot;on 2.3 of [RFC5890].&quot;<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 16], Section 4.4, paragraph 3,&quot;[RFC2308]=
 suggests on an&quot; --remove &quot;on&quot;--&gt; &quot;[RFC2308] suggest=
s an&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 21], Section 5.1, line 1, <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;This section defines two types of mechanisms.&=
quot; --for clarity--&gt; &quot;This section defines two types of mechanism=
s: basic and designated sender.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 21], second paragraph before last, &quot; bot=
h &quot;AAAA&quot; and &quot;A&quot; secords &quot;--typo--&gt; &quot;recor=
ds&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 22], Section 5.2, point 3, please review&nbsp=
; &quot;include: mechanism&quot; and &quot;\&quot;fail &quot;.<o:p></o:p></=
p>
<p class=3D"MsoNormal">Suggestion: instead of &quot;gives a pass&quot; or &=
quot;gives a fail&quot; is it better to say &quot;signifies&quot; or &quot;=
represents&quot; as pass/fail?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 22], second paragraph before last, <o:p></o:p=
></p>
<p class=3D"MsoNormal">&quot;Only the evaluated result of the referenced SP=
F record is used, rather than acting as if the referenced SPF
<o:p></o:p></p>
<p class=3D"MsoNormal">record was literally included in the first.&quot;<o:=
p></o:p></p>
<p class=3D"MsoNormal">The part after the comma in this sentence is hard to=
 understand. Please review if possible.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 24], Section 5.4, <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;the evaluation terminated&quot;--missing is--&=
gt;&quot;the evaluation is terminated&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;has no MX records&quot;--no s--&gt;&quot;has n=
o MX record&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 26], first paragraph, <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;and more reliable alternatives used instead&qu=
ot;----&gt;&quot;and more reliable alternatives should be used instead&quot=
;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;still in use and part of&quot;----&gt;&quot;st=
ill in use as part of&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 29], paragraph 3, <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;is generally be&quot;----&gt;&quot;will genera=
lly be&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 30], paragraph 1, <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;such as shown in Section 2.6.4&quot;,- is this=
 pointing to the correct section?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 30], last sentence<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;Note: During recursion into an &quot;include&q=
uot; mechanism, an exp=3D modifier<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; from the &lt;target-name&gt; MUST NOT b=
e used.&nbsp; In contrast, when executing<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; a &quot;redirect&quot; modifier, an exp=
=3D modifier from the original domain MUST<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; NOT be used.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">Is it possible to add 1-2 sentence to explain why?(w=
hat is the expected consequence if this is not respected)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 32], line 3, <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;p =3D the validated domain name of &lt;ip&gt; =
(do not use)&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">Is it possible to add a reference to section 5.5 whi=
ch explains why?<o:p></o:p></p>
<p class=3D"MsoNormal">Suggested: &quot;(do not use, see Section 5.5)&quot;=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 33], third paragraph before last<o:p></o:p></=
p>
<p class=3D"MsoNormal">&quot;was provide more than once&quot;----&gt;&quot;=
was provided more than once&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 34], last &quot;Note&quot;:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;....for as long as the shortest Time To Live (=
TTL) of all the DNS records involved.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">Please review this sentence ending. It is not clear.=
 <o:p></o:p></p>
<p class=3D"MsoNormal">Suggestion: &quot;as long as the DNS record involved=
 with the shortest TTL has not expired&quot; ?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 36], sentence 2, &quot;Terse definitions&quot=
;--typo--&gt;&quot;The definitions&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 36], paragraph 2,&quot;be explicity&quot;--ty=
po--&gt;&quot;be explicitly&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 36], Section 8.1,&quot;checked idenity&quot;-=
-typo--&gt;&quot;checked identity&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 37], Section 8.4, &quot;the 5.7.1 enhanced st=
atus code&quot;, with reference to RFC3463.
<o:p></o:p></p>
<p class=3D"MsoNormal">For better clarity please consider adding reference =
to Section 3.8 of the RFC3463.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 38], Section 8.6,<o:p></o:p></p>
<p class=3D"MsoNormal">For better clarity please consider referring to Sect=
ion 3.5 of RFC3463<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 38], Section 8.8,<o:p></o:p></p>
<p class=3D"MsoNormal">For better clarity please consider referring to Sect=
ion 3.6 of RFC3463<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 39], Section 9 Title, &quot;Recording The Res=
ult&quot;----&gt;&quot;the&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 44], Line 2, &quot;carefully weight&quot;----=
&gt;&quot;carefully weigh&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 44], Section 10.1.2, &quot;&quot;ip4&quot; an=
d &quot;ip6&quot; over &quot;a&quot; or &quot;a&quot; or &quot;mx&quot;.&qu=
ot;<o:p></o:p></p>
<p class=3D"MsoNormal">The last part should suggest &quot;mx' over &quot;a&=
quot; or the reverse?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 46], Section 10.3 &quot;User actor.[RFC5598].=
&quot;----&gt;&quot;User actor [RFC5598].&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 47], before last sentence, missing closing pa=
renthesis:&quot;(defined in Section 4.6.4.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 49], Section 11.5.3, &quot;It is necesary&quo=
t;--typo--&gt;&quot;It is necessary&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 62], line 2, &quot;to implmentation&quot;--ty=
po--&gt;&quot;to implementation&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 62], second bullet before last, &quot;Section=
 10 and Appendices D - H below.&quot;, is this part of the sentence referin=
g to anything, below?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 65], Section E.3, &quot;Receving ADMDs&quot;-=
-typo--&gt;&quot;Receiving ADMDs&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 66], last line, &quot;mitiate&quot;--typo--&g=
t;&quot;mitigate&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 68], one line before last, &quot;reliabililit=
y&quot;--typo--&gt;&quot;reliability&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CA">-[Page 70], paragraphe 2,<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CA">&quot;techincal&quot;--typo--&g=
t;&quot;technical&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal">&quot;deplyment&quot;--typo--&gt;&quot;deployment&qu=
ot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 72], line 7, &quot;obslete&quot;--typo--&gt;&=
quot;obsolete&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 72], 2 line before last, &quot;text and figur=
es from Alessandro Vesely&quot;, is it only to section 9.1, or 10.1.1. as w=
ell?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 73], &quot;Added new section 9 discussion on =
treatment of bounces&quot;, is it section 9 or section 10.1.3?<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 73], 1 line before last, &quot;potental&quot;=
--typo--&gt;&quot;potential&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-Appendix J., please review the 'section references'=
 pointing to various changes.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-Throughout the draft, DNS &quot;look up&quot;----&g=
t;&quot;lookup&quot; <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-Throughout the draft, DNS RCODEs are mentioned with=
out any reference to RFC1035 (or RFC6195)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-Throughout the draft, many cross references break t=
he follow. I suggested revisiting some of them and adding a small text afte=
r each reference which introduces that section.<o:p></o:p></p>
<p class=3D"MsoNormal">Example :[Page 17], Section 4.6.2 &quot;the result i=
s specified in Section 4.7&quot;, suggested--&gt;&quot;the result is specif=
ied in Section 4.7 where Default results are discussed&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-&quot;Section 2.6 Results of Evaluation&quot; lists=
 the possible outputs of check_host().
<o:p></o:p></p>
<p class=3D"MsoNormal">Then &quot;Section 8.&nbsp; Result Handling&quot; co=
ntinues the description with handling guidance.<o:p></o:p></p>
<p class=3D"MsoNormal">To avoid breaking the flow, please consider moving t=
he descriptive content of Section 2.6 into Section 8. (unless there is anot=
her reason to keep them far apart).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A0D4633eusaamb107ericsso_--

From Ted.Lemon@nominum.com  Mon Apr 29 09:38:06 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3735621F9E07; Mon, 29 Apr 2013 09:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 VDlHR718wayO; Mon, 29 Apr 2013 09:38:05 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id 0CEDA21F9E01; Mon, 29 Apr 2013 09:38:05 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUX6h7C8MLrDsUSNolbSkLQEXAJXa3/MR@postini.com; Mon, 29 Apr 2013 09:38:05 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 8A57D1B815E; Mon, 29 Apr 2013 09:38:04 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 7BE84190061; Mon, 29 Apr 2013 09:38:04 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 29 Apr 2013 09:38:04 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Index: AQHORORy+jlCE9D1eEC77pV047+J55jt22OA
Date: Mon, 29 Apr 2013 16:38:03 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775166969@mbx-01.win.nominum.com>
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr> <517AA910.8030608@nostrum.com> <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EC9B49B02@PUEXCB1B.nanterre.francetelecom.fr> <517E796E.6040402@nostrum.com> <489D13FBFA9B3E41812EA89F188F018E1851F76A@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1851F76A@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <0EEDAECDCBFCE341849C5B85D1C939EA@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Subject: Re: [Gen-art] [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 16:38:06 -0000

On Apr 29, 2013, at 10:18 AM, "Bernie Volz (volz)" <volz@cisco.com> wrote:
> But I don't really see this as a big issue and the "must" is the lower-ca=
se variant anyway.

There's a big debate about whether this makes any difference.   It's genera=
lly thought to be better not to say must if you don't mean MUST.

I think the idea of just saying e.g. is the right thing, and stable storage=
 and bulk leasequery would be two really great examples to use.


From sm@elandsys.com  Mon Apr 29 10:15:05 2013
Return-Path: <sm@elandsys.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA15821F9E7C; Mon, 29 Apr 2013 10:15:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.425
X-Spam-Level: 
X-Spam-Status: No, score=-102.425 tagged_above=-999 required=5 tests=[AWL=0.175, 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 2UcMMURzvdWD; Mon, 29 Apr 2013 10:15:03 -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 6148021F9E82; Mon, 29 Apr 2013 10:15:02 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.145]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r3THEj5N027607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Apr 2013 10:14:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367255697; bh=rsfIQIkYHEBklJVkMy7mHNQrjWIPTgZ1QCX4vkKRnEs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=L1BZrhYub271HjG287Q/Ltl3c2muKI4Tj1zNt0nMN2yEWoyTwlptTt/rr1FNZLljf VhHIHXvW94fSv1P+m+uVdSIXG4C3Cy/6a2P4YYEW4emIVStRkMPXAGwZYw2n1HSg87 XUm/rA07rvXiJ69ZPQisC4PZq67ExdkYOAxkZYS0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1367255697; i=@elandsys.com; bh=rsfIQIkYHEBklJVkMy7mHNQrjWIPTgZ1QCX4vkKRnEs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HJ4KbP8FqtDDUYqVcIyfizpstGBHxocRjMVGJLBVmARqQQU1MCAQ+J0fVjG9Lw6DA 9FFrCdocd791Zh/zzigFWkLgrDg8ZMv/Udlg6wd8PWOy0U0IoYs83fdgKoodiKQD4U BZfV3RZS3vCE7/FzE3GxVZ61fcF1jT0h6MQddLnA=
Message-Id: <6.2.5.6.2.20130429100907.0d0cab88@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 29 Apr 2013 10:14:28 -0700
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A0D4633@eusaamb107.ericsson .se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A0D4633@eusaamb107.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: spfbis@ietf.org, draft-ietf-spfbis-4408bis.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-spfbis-4408bis-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 17:15:05 -0000

Hi Meral,

Thanks for the review.  I am forwarding it to the SPFBIS mailing list 
for discussion.  I'll email you in a few days to address your comments.

Regards,
S. Moonesamy (as document shepherd)

At 08:53 29-04-2013, Meral Shirazipour wrote:
>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>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-spfbis-4408bis-14
>Reviewer: Meral Shirazipour
>Review Date: 2013-04-29
>IETF LC End Date: 2013-04-30
>IESG Telechat date: NA
>
>
>
>Summary:
>This draft is almost ready to be published as Informational RFC but 
>I do have some comments.
>
>
>Nits/editorial comments:
>-[Page 6] Section "1.1.2.  Imported Definitions"
>Please consider expanding acronyms and giving the section of the RFC 
>where each term is defined.
>(Also throughout the document it would greatly help the readability 
>if acronyms are expanded when first used.)
>
>-[Page 8] Section 2.2. Line 1:
>""MAIL FROM" -> extra \"
>
>-[Page 13], Section 3.3. , first line: "sections 3.3.14 and 3.3".
>If both subsection and subsubsection are to be mentioned, please 
>consider: "sections 3.3 and 3.3.14"
>
>-[Page 16], Section 4.3, paragraph 1, last sentence: extra text/typo 
>to be removed: "on 2.3 of [RFC5890]."
>
>-[Page 16], Section 4.4, paragraph 3,"[RFC2308] suggests on an" 
>--remove "on"--> "[RFC2308] suggests an"
>
>-[Page 21], Section 5.1, line 1,
>"This section defines two types of mechanisms." --for clarity--> 
>"This section defines two types of mechanisms: basic and designated sender."
>
>-[Page 21], second paragraph before last, " both "AAAA" and "A" 
>secords "--typo--> "records"
>
>-[Page 22], Section 5.2, point 3, please review  "include: 
>mechanism" and "\"fail ".
>Suggestion: instead of "gives a pass" or "gives a fail" is it better 
>to say "signifies" or "represents" as pass/fail?
>
>-[Page 22], second paragraph before last,
>"Only the evaluated result of the referenced SPF record is used, 
>rather than acting as if the referenced SPF
>record was literally included in the first."
>The part after the comma in this sentence is hard to understand. 
>Please review if possible.
>
>-[Page 24], Section 5.4,
>"the evaluation terminated"--missing is-->"the evaluation is terminated"
>"has no MX records"--no s-->"has no MX record"
>
>-[Page 26], first paragraph,
>"and more reliable alternatives used instead"---->"and more reliable 
>alternatives should be used instead"
>
>"still in use and part of"---->"still in use as part of"
>
>-[Page 29], paragraph 3,
>"is generally be"---->"will generally be"
>
>-[Page 30], paragraph 1,
>"such as shown in Section 2.6.4",- is this pointing to the correct section?
>
>-[Page 30], last sentence
>"Note: During recursion into an "include" mechanism, an exp= modifier
>    from the <target-name> MUST NOT be used.  In contrast, when executing
>    a "redirect" modifier, an exp= modifier from the original domain MUST
>    NOT be used.
>"
>Is it possible to add 1-2 sentence to explain why?(what is the 
>expected consequence if this is not respected)
>
>-[Page 32], line 3,
>"p = the validated domain name of <ip> (do not use)"
>Is it possible to add a reference to section 5.5 which explains why?
>Suggested: "(do not use, see Section 5.5)"
>
>-[Page 33], third paragraph before last
>"was provide more than once"---->"was provided more than once"
>
>-[Page 34], last "Note":
>"....for as long as the shortest Time To Live (TTL) of all the DNS 
>records involved."
>Please review this sentence ending. It is not clear.
>Suggestion: "as long as the DNS record involved with the shortest 
>TTL has not expired" ?
>
>-[Page 36], sentence 2, "Terse definitions"--typo-->"The definitions"
>
>-[Page 36], paragraph 2,"be explicity"--typo-->"be explicitly"
>
>-[Page 36], Section 8.1,"checked idenity"--typo-->"checked identity"
>
>-[Page 37], Section 8.4, "the 5.7.1 enhanced status code", with 
>reference to RFC3463.
>For better clarity please consider adding reference to Section 3.8 
>of the RFC3463.
>
>-[Page 38], Section 8.6,
>For better clarity please consider referring to Section 3.5 of RFC3463
>
>-[Page 38], Section 8.8,
>For better clarity please consider referring to Section 3.6 of RFC3463
>
>-[Page 39], Section 9 Title, "Recording The Result"---->"the"
>
>-[Page 44], Line 2, "carefully weight"---->"carefully weigh"
>
>-[Page 44], Section 10.1.2, ""ip4" and "ip6" over "a" or "a" or "mx"."
>The last part should suggest "mx' over "a" or the reverse?
>
>-[Page 46], Section 10.3 "User actor.[RFC5598]."---->"User actor [RFC5598]."
>
>-[Page 47], before last sentence, missing closing 
>parenthesis:"(defined in Section 4.6.4."
>
>-[Page 49], Section 11.5.3, "It is necesary"--typo-->"It is necessary"
>
>-[Page 62], line 2, "to implmentation"--typo-->"to implementation"
>
>-[Page 62], second bullet before last, "Section 10 and Appendices D 
>- H below.", is this part of the sentence refering to anything, below?
>
>-[Page 65], Section E.3, "Receving ADMDs"--typo-->"Receiving ADMDs"
>
>-[Page 66], last line, "mitiate"--typo-->"mitigate"
>
>-[Page 68], one line before last, "reliabilility"--typo-->"reliability"
>
>-[Page 70], paragraphe 2,
>"techincal"--typo-->"technical"
>"deplyment"--typo-->"deployment"
>
>-[Page 72], line 7, "obslete"--typo-->"obsolete"
>
>-[Page 72], 2 line before last, "text and figures from Alessandro 
>Vesely", is it only to section 9.1, or 10.1.1. as well?
>
>-[Page 73], "Added new section 9 discussion on treatment of 
>bounces", is it section 9 or section 10.1.3?
>
>-[Page 73], 1 line before last, "potental"--typo-->"potential"
>
>-Appendix J., please review the 'section references' pointing to 
>various changes.
>
>
>
>-Throughout the draft, DNS "look up"---->"lookup"
>
>-Throughout the draft, DNS RCODEs are mentioned without any 
>reference to RFC1035 (or RFC6195)
>
>-Throughout the draft, many cross references break the follow. I 
>suggested revisiting some of them and adding a small text after each 
>reference which introduces that section.
>Example :[Page 17], Section 4.6.2 "the result is specified in 
>Section 4.7", suggested-->"the result is specified in Section 4.7 
>where Default results are discussed"
>
>-"Section 2.6 Results of Evaluation" lists the possible outputs of 
>check_host().
>Then "Section 8.  Result Handling" continues the description with 
>handling guidance.
>To avoid breaking the flow, please consider moving the descriptive 
>content of Section 2.6 into Section 8. (unless there is another 
>reason to keep them far apart).
>
>
>
>
>Best Regards,
>Meral
>
>---
>Meral Shirazipour
>Ericsson Research
>www.ericsson.com


From superuser@gmail.com  Mon Apr 29 11:34:46 2013
Return-Path: <superuser@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D98CF21F9AF7; Mon, 29 Apr 2013 11:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.933
X-Spam-Level: 
X-Spam-Status: No, score=-0.933 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_HTML_USL_OBFU=1.666]
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 0RNIjLqVIwXy; Mon, 29 Apr 2013 11:34:46 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id B413621F9AF3; Mon, 29 Apr 2013 11:34:45 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id i48so2591002wef.34 for <multiple recipients>; Mon, 29 Apr 2013 11:34:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/bb7u/i/HWZGya/qLKRTz93JSfR5H/xqpi9YWo+4e7s=; b=p3LvEciQRpwIWmzkRKQSqLyg4odG1YvUsaN18ZeVyrn+HNato0+7YKcPuNGXxDMvXf i6g4b1H9zYsbcdll30am4ZEwo+zTvLwvYBOWTHtBhOZrySJiMxzyPdIghaHWsy3sXbVf 5A1EzEMVoXyIRv6dNg1QiF4xvqnaHB6kCbZRtJ4OzgQQzlksULnKiZmu/GnUTHbZ8YCY 5qCaWIpdKjgXSFvlB9l2K0O6QcWhPcHqncxxkwYXT6jZRl+6BLYRREJsTYdkqvyVcYC2 2P4/tn7UAB6cM/jAssC435zc6xmpyw3G4yjAkBDQ2jS98zhAGoudmgLrEGp7hSf93aSD Qckw==
MIME-Version: 1.0
X-Received: by 10.180.188.198 with SMTP id gc6mr7820334wic.14.1367260484902; Mon, 29 Apr 2013 11:34:44 -0700 (PDT)
Received: by 10.180.14.34 with HTTP; Mon, 29 Apr 2013 11:34:44 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130429100907.0d0cab88@elandnews.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A0D4633@eusaamb107.ericsson.se> <6.2.5.6.2.20130429100907.0d0cab88@elandnews.com>
Date: Mon, 29 Apr 2013 11:34:44 -0700
Message-ID: <CAL0qLwYpnwXxzJDw0KeJHjQoe2sWW81UiuRzsBZFVDxUTNaDpg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=001a11c389a484a4da04db842375
Cc: "spfbis@ietf.org" <spfbis@ietf.org>, General Area Review Team <gen-art@ietf.org>, draft-ietf-spfbis-4408bis.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART Last Call review of draft-ietf-spfbis-4408bis-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 18:34:47 -0000

--001a11c389a484a4da04db842375
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Apr 29, 2013 at 10:14 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Meral,
>
> Thanks for the review.  I am forwarding it to the SPFBIS mailing list for
> discussion.  I'll email you in a few days to address your comments.
>
> Regards,
> S. Moonesamy (as document shepherd)
>
> At 08:53 29-04-2013, Meral Shirazipour wrote:
>
>> 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<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>> >h**ttp://wiki.tools.ietf.org/**area/gen/trac/wiki/GenArtfaq<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-spfbis-4408bis-14
>> Reviewer: Meral Shirazipour
>> Review Date: 2013-04-29
>> IETF LC End Date: 2013-04-30
>> IESG Telechat date: NA
>>
>>
>>
>> Summary:
>> This draft is almost ready to be published as Informational RFC but I do
>> have some comments.
>>
>
Was this a mistake in the preparation of the review, or did the reviewer
believe the intended status was Informational and thus do a review with
less scrutiny in mind?  The intended status is Proposed Standard.

-MSK

--001a11c389a484a4da04db842375
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 29, 2013 at 10:14 AM, S Moonesamy <span dir=3D=
"ltr">&lt;<a href=3D"mailto:sm+ietf@elandsys.com" target=3D"_blank">sm+ietf=
@elandsys.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Meral,<br>
<br>
Thanks for the review. =A0I am forwarding it to the SPFBIS mailing list for=
 discussion. =A0I&#39;ll email you in a few days to address your comments.<=
br>
<br>
Regards,<br>
S. Moonesamy (as document shepherd)<br>
<br>
At 08:53 29-04-2013, Meral Shirazipour wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/<u></u>a=
rea/gen/trac/wiki/GenArtfaq</a>&gt;<a href=3D"http://wiki.tools.ietf.org/ar=
ea/gen/trac/wiki/GenArtfaq" target=3D"_blank">h<u></u>ttp://wiki.tools.ietf=
.org/<u></u>area/gen/trac/wiki/GenArtfaq</a> .<br>

<br>
Please resolve these comments along with any other Last Call comments you m=
ay receive.<br>
<br>
Document: draft-ietf-spfbis-4408bis-14<br>
Reviewer: Meral Shirazipour<br>
Review Date: 2013-04-29<br>
IETF LC End Date: 2013-04-30<br>
IESG Telechat date: NA<br>
<br>
<br>
<br>
Summary:<br>
This draft is almost ready to be published as Informational RFC but I do ha=
ve some comments.<br></blockquote></blockquote><div><br></div><div>Was this=
 a mistake in the preparation of the review, or did the reviewer believe th=
e intended status was Informational and thus do a review with less scrutiny=
 in mind?=A0 The intended status is Proposed Standard.<br>
<br></div><div>-MSK<br></div></div></div></div>

--001a11c389a484a4da04db842375--

From sm@elandsys.com  Mon Apr 29 11:48:35 2013
Return-Path: <sm@elandsys.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E0E121F9A6A; Mon, 29 Apr 2013 11:48:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.459
X-Spam-Level: 
X-Spam-Status: No, score=-102.459 tagged_above=-999 required=5 tests=[AWL=0.140, 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 CTCFmgHw9T9G; Mon, 29 Apr 2013 11:48:34 -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 0DE1F21F9AC5; Mon, 29 Apr 2013 11:48:29 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.145]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r3TIm6ga011371 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Apr 2013 11:48:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367261299; bh=R6iuUKlPGJXFffsU/240+UAmvlzK2Yw3Fetewz9lV/I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2P3rjKLcmg048y/GYQ37AOo+gDhZQSmyY54BMJpc7dbOYjeLgMdwEivyKNju/r/oa wCCquem54uvfWxjynbTr39VIG6ywwpmaIwZex83+YKwI8qwllHhSz0y9B3u93B5AAF b8uDKT9Y4BUmY/UuOXsZ/ecdM9ANF3hht3vRsAgs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1367261299; i=@elandsys.com; bh=R6iuUKlPGJXFffsU/240+UAmvlzK2Yw3Fetewz9lV/I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FiDewJ+thJToaWvbREE6CkgzWRFn7REpblftpv2TrClJr7gGmwPuLqIe93YbDY5T3 18HJL5HiwKbWYB/xT+VHbN7q/u2wJGaNHMxRpRl+fHzZuHp5RKelmX+ydog14DxhI+ nmVjWcflYd5ptWvZOmL7D3Cv8M8brDt89a1RB76s=
Message-Id: <6.2.5.6.2.20130429113656.0d0cbc30@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 29 Apr 2013 11:47:31 -0700
To: "Murray S. Kucherawy" <superuser@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <CAL0qLwYpnwXxzJDw0KeJHjQoe2sWW81UiuRzsBZFVDxUTNaDpg@mail.g mail.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A0D4633@eusaamb107.ericsson.se> <6.2.5.6.2.20130429100907.0d0cab88@elandnews.com> <CAL0qLwYpnwXxzJDw0KeJHjQoe2sWW81UiuRzsBZFVDxUTNaDpg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: spfbis@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-ietf-spfbis-4408bis.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART Last Call review of draft-ietf-spfbis-4408bis-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 18:48:35 -0000

Hi Murray,
At 11:34 29-04-2013, Murray S. Kucherawy wrote:
>Was this a mistake in the preparation of the review, or did the 
>reviewer believe the intended status was Informational and thus do a 
>review with less scrutiny in mind?  The intended status is Proposed Standard.

In my opinion the reviewer read the draft very carefully.  The 
reviewer might have written the word "Informational" to see whether 
the SPFBIS working group will read the Gen-ART review carefully. :-)

The intended status of the draft is "Proposed Standard".

Regards,
S. Moonesamy 


From superuser@gmail.com  Mon Apr 29 12:26:49 2013
Return-Path: <superuser@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFD5B21F9B25; Mon, 29 Apr 2013 12:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.766
X-Spam-Level: 
X-Spam-Status: No, score=-1.766 tagged_above=-999 required=5 tests=[AWL=0.833,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 MUmD85TGFJRn; Mon, 29 Apr 2013 12:26:49 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id EEDEE21F9B24; Mon, 29 Apr 2013 12:26:48 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id e11so2307648wgh.4 for <multiple recipients>; Mon, 29 Apr 2013 12:26:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=cJc9MNZgWhiTCef2rpL9ITE3EzEHnOElwZr6DIeiZTc=; b=BUhDEp24n6Y9p48cvxYktyeU/mFr8BTOx2eX51MXiWNrgyYzAzRJKLL/oli/7BTOx6 LaFd+tp54i8AsF0AjcWdZj+zxKJgSypfghP/P/h9rkdwb6h1Y2X8mAF6TI5kOqWf+Ax4 63s64lA0X3FhPpfiofWHWuPSd84QSsVwhqfmRywcozN94j1vNRc+IG+roBIbWqua5KLf ZNbr9nzE0xO3McoPXfna5hPUYPk/+0j63oLTH59Tey+JgLBGzds9HL0Y3Pfe5qslZusu c/wTXI0VchOOS3gljWWve6Jckiqp5yZdYePWEp0JmLL7zFPSzf81quh8C+UJl87dX/x5 XcIQ==
MIME-Version: 1.0
X-Received: by 10.194.59.208 with SMTP id b16mr15892729wjr.15.1367263604031; Mon, 29 Apr 2013 12:26:44 -0700 (PDT)
Received: by 10.180.14.34 with HTTP; Mon, 29 Apr 2013 12:26:43 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130429113656.0d0cbc30@elandnews.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A0D4633@eusaamb107.ericsson.se> <6.2.5.6.2.20130429100907.0d0cab88@elandnews.com> <CAL0qLwYpnwXxzJDw0KeJHjQoe2sWW81UiuRzsBZFVDxUTNaDpg@mail.gmail.com> <6.2.5.6.2.20130429113656.0d0cbc30@elandnews.com>
Date: Mon, 29 Apr 2013 12:26:43 -0700
Message-ID: <CAL0qLwbPgDT5WcsA+9afwr26kPDVTje_1yGzYQV8AyQLORrt6A@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=047d7b86de326ec9a604db84dd94
Cc: "spfbis@ietf.org" <spfbis@ietf.org>, General Area Review Team <gen-art@ietf.org>, draft-ietf-spfbis-4408bis.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART Last Call review of draft-ietf-spfbis-4408bis-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 19:26:50 -0000

--047d7b86de326ec9a604db84dd94
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Apr 29, 2013 at 11:47 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> In my opinion the reviewer read the draft very carefully.  The reviewer
> might have written the word "Informational" to see whether the SPFBIS
> working group will read the Gen-ART review carefully. :-)
>

Better to ask the question now than have it come up during IETF LC that the
review needs to be repeated with a different perspective.


> The intended status of the draft is "Proposed Standard".
>

Right.

-MSK

--047d7b86de326ec9a604db84dd94
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 29, 2013 at 11:47 AM, S Moonesamy <span dir=3D=
"ltr">&lt;<a href=3D"mailto:sm+ietf@elandsys.com" target=3D"_blank">sm+ietf=
@elandsys.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">In my opinion the reviewer read the draft ve=
ry carefully. =A0The reviewer might have written the word &quot;Information=
al&quot; to see whether the SPFBIS working group will read the Gen-ART revi=
ew carefully. :-)<br>
</blockquote><div><br></div><div>Better to ask the question now than have i=
t come up during IETF LC that the review needs to be repeated with a differ=
ent perspective.<br>=A0<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

The intended status of the draft is &quot;Proposed Standard&quot;.<br></blo=
ckquote><div><br></div><div>Right.<br><br></div><div>-MSK<br></div></div></=
div></div>

--047d7b86de326ec9a604db84dd94--

From meral.shirazipour@ericsson.com  Mon Apr 29 12:26:54 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 788C021F9B38; Mon, 29 Apr 2013 12:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  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 KRJOBBTB-kBY; Mon, 29 Apr 2013 12:26:49 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id AD4EF21F9ADE; Mon, 29 Apr 2013 12:26:48 -0700 (PDT)
X-AuditID: c6180641-b7faf6d00000096b-09-517ec976b45a
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id BE.09.02411.679CE715; Mon, 29 Apr 2013 21:26:47 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0328.009; Mon, 29 Apr 2013 15:26:46 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: S Moonesamy <sm+ietf@elandsys.com>, "Murray S. Kucherawy" <superuser@gmail.com>
Thread-Topic: [spfbis] Gen-ART Last Call review of draft-ietf-spfbis-4408bis-14
Thread-Index: AQHORQohUSx1P65FM0qXGQEpvFzSI5jtk7sQ
Date: Mon, 29 Apr 2013 19:26:46 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A0D4B7B@eusaamb107.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A0D4633@eusaamb107.ericsson.se> <6.2.5.6.2.20130429100907.0d0cab88@elandnews.com> <CAL0qLwYpnwXxzJDw0KeJHjQoe2sWW81UiuRzsBZFVDxUTNaDpg@mail.gmail.com> <6.2.5.6.2.20130429113656.0d0cbc30@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130429113656.0d0cbc30@elandnews.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrGLMWRmVeSWpSXmKPExsUyuXRPoG75ybpAg6tvuC12Tn3FanH11WcW i1f9N1ktns7cz24x8XsDmwOrx703H5k8ds66y+6xZMlPJo8vlz+zBbBEcdmkpOZklqUW6dsl cGW8X7+UveAIV8X8k+1MDYwXOLoYOTkkBEwkFu3tZYSwxSQu3FvP1sXIxSEkcJRR4uDkpywg CSGB5YwSN/trQWw2AQuJ7b+fs3YxcnCICIRKvD3hDFLPLLCTUeLqh/tg9cICgRJdh66xgtgi AkES/3YugbKNJM603QSzWQRUJV68mMAEModXwFvi5wYuiL2/GCVebuphB6nhFLCTWNE4E6ye Eei476fWMIHYzALiEreezGeCOFpAYsme88wQtqjEy8f/WCFsZYklT/azQNTrSCzY/YkNwtaW WLbwNVg9r4CgxMmZT1gmMIrNQjJ2FpKWWUhaZiFpWcDIsoqRo7Q4tSw33chwEyMwro5JsDnu YFzwyfIQozQHi5I47zSpykAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjHrGH+YF36ueH+u4 5SRfDrtz8CUrzt+mHIsk0w52sdz3ZeV5XrdS9NXkr5M+H3qiaZh8QMP8JCNDi/8Z34e16+ek hQcdviyk+C90wbwJ3z5xcLYIxk1KbjfIT+397Ch7xD3qU2e6lEh1QNaJxdJbhNtuVQnqTZ0k 2S5hYKrps2Br3a+Jjl5RSizFGYmGWsxFxYkAdI/FSHkCAAA=
Cc: "spfbis@ietf.org" <spfbis@ietf.org>, "draft-ietf-spfbis-4408bis.all@tools.ietf.org" <draft-ietf-spfbis-4408bis.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] [spfbis] Gen-ART Last Call review of draft-ietf-spfbis-4408bis-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 19:26:54 -0000

Hi,
  Sorry for the confusion. I read it fully aware that it is not information=
al.=20

Original email : http://www.ietf.org/mail-archive/web/gen-art/current/msg08=
509.html should say:
OLD:  "This draft is almost ready to be published as Informational RFC but =
I do have some comments."
NEW: "This draft is almost ready to be published as Standard RFC but I do h=
ave some comments."

Thanks,
Meral

-----Original Message-----
From: S Moonesamy [mailto:sm+ietf@elandsys.com]=20
Sent: Monday, April 29, 2013 11:48 AM
To: Murray S. Kucherawy
Cc: Meral Shirazipour; spfbis@ietf.org; draft-ietf-spfbis-4408bis.all@tools=
.ietf.org; General Area Review Team
Subject: Re: [spfbis] Gen-ART Last Call review of draft-ietf-spfbis-4408bis=
-14

Hi Murray,
At 11:34 29-04-2013, Murray S. Kucherawy wrote:
>Was this a mistake in the preparation of the review, or did the=20
>reviewer believe the intended status was Informational and thus do a=20
>review with less scrutiny in mind?  The intended status is Proposed Standa=
rd.

In my opinion the reviewer read the draft very carefully.  The reviewer mig=
ht have written the word "Informational" to see whether the SPFBIS working =
group will read the Gen-ART review carefully. :-)

The intended status of the draft is "Proposed Standard".

Regards,
S. Moonesamy=20


From dotzero@gmail.com  Mon Apr 29 12:44:55 2013
Return-Path: <dotzero@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 552BE21F9B8F; Mon, 29 Apr 2013 12:44:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 86js6SAAlh9m; Mon, 29 Apr 2013 12:44:55 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 6931021F9AA8; Mon, 29 Apr 2013 12:44:54 -0700 (PDT)
Received: by mail-la0-f42.google.com with SMTP id eb20so1166236lab.29 for <multiple recipients>; Mon, 29 Apr 2013 12:44:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=433KlHb48nbKldyp5+dP3EmZslJhKYFyLNwjuBBEEeM=; b=Fu6UpfteBbUIYbIu3uW5IdLHV4DWoylWKwMoSgf6qgk8YVyMr5MWk0IwpOF0kCW8eP 7xXBmgJZuBOcxYCF16IQxYzMADY7yXsgR7Vv6UVuaoKld5TAcWswkVutEDhWN1sC3BGW L9l0oXvzt8bBpzjF8oUaaDRw6oUnK6j7/MUKoekGhIYfDBxU/5atPW1yIemOQIxMzmWs KXlhuxBJdTqFSkgjfka3zi8TOpFOTJkhhM7d5rUsuxDAq48U7rMXrPgiuC1epagaQFbd BnUnJDlMFchGfH2axNPsFu157Jomr3qWLp5eRJfBLkJ/zGTnzEvndOXkcd/BHp2T5Z74 QSug==
MIME-Version: 1.0
X-Received: by 10.152.88.115 with SMTP id bf19mr12227903lab.56.1367264689447;  Mon, 29 Apr 2013 12:44:49 -0700 (PDT)
Received: by 10.112.72.166 with HTTP; Mon, 29 Apr 2013 12:44:49 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130429113656.0d0cbc30@elandnews.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A0D4633@eusaamb107.ericsson.se> <6.2.5.6.2.20130429100907.0d0cab88@elandnews.com> <CAL0qLwYpnwXxzJDw0KeJHjQoe2sWW81UiuRzsBZFVDxUTNaDpg@mail.gmail.com> <6.2.5.6.2.20130429113656.0d0cbc30@elandnews.com>
Date: Mon, 29 Apr 2013 15:44:49 -0400
Message-ID: <CAJ4XoYddzS2uwmvmRJ01sj0cxHTXrhRxL9DP8htZ6Wdn=OPOBg@mail.gmail.com>
From: Dotzero <dotzero@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Mon, 29 Apr 2013 12:56:46 -0700
Cc: spfbis@ietf.org, General Area Review Team <gen-art@ietf.org>, "Murray S. Kucherawy" <superuser@gmail.com>, draft-ietf-spfbis-4408bis.all@tools.ietf.org
Subject: Re: [Gen-art] [spfbis] Gen-ART Last Call review of draft-ietf-spfbis-4408bis-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 19:44:55 -0000

On Mon, Apr 29, 2013 at 2:47 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> Hi Murray,
>
> At 11:34 29-04-2013, Murray S. Kucherawy wrote:
>>
>> Was this a mistake in the preparation of the review, or did the reviewer
>> believe the intended status was Informational and thus do a review with less
>> scrutiny in mind?  The intended status is Proposed Standard.
>
>
> In my opinion the reviewer read the draft very carefully.  The reviewer
> might have written the word "Informational" to see whether the SPFBIS
> working group will read the Gen-ART review carefully. :-)
>
> The intended status of the draft is "Proposed Standard".
>
> Regards,
> S. Moonesamy
>

I noticed this as well and was just about to respond when I saw Murray respond.

Mike

From j.schoenwaelder@jacobs-university.de  Tue Apr 30 04:49:12 2013
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1FF221F9A52; Tue, 30 Apr 2013 04:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.249
X-Spam-Level: 
X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, 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 rYhmVz2y4gMC; Tue, 30 Apr 2013 04:49:08 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id EF90521F9B2F; Tue, 30 Apr 2013 04:49:07 -0700 (PDT)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 7367B20C12; Tue, 30 Apr 2013 13:49:07 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 2Mg_MdkrI39T; Tue, 30 Apr 2013 13:49:07 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id D35A520C06; Tue, 30 Apr 2013 13:49:06 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id D66D825EB6AA; Tue, 30 Apr 2013 13:49:05 +0200 (CEST)
Date: Tue, 30 Apr 2013 13:49:05 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <20130430114905.GA47531@elstar.local>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, draft-ietf-netmod-rfc6021-bis.all@tools.ietf.org, gen-art@ietf.org, netmod@ietf.org
References: <5171C416.5070105@joelhalpern.com> <517F9AEF.8090601@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <517F9AEF.8090601@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: draft-ietf-netmod-rfc6021-bis.all@tools.ietf.org, gen-art@ietf.org, netmod@ietf.org
Subject: Re: [Gen-art] Fwd:  Review: draft-ietf-netmod-rfc6021-bis-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Apr 2013 11:49:12 -0000

On Tue, Apr 30, 2013 at 12:20:31PM +0200, Benoit Claise wrote:
> Hi,
> 
> Just making sure that you saw this one.
> Next to the APPSDIR review, I believe that this is the one review left.
> 

Thanks for forwarding this. Answers inline. Thanks to Joel Halpern to
review this document.

> 
> 
> -------- Original Message --------
> Subject: 	[Gen-art] Review: draft-ietf-netmod-rfc6021-bis-01
> Date: 	Fri, 19 Apr 2013 18:24:22 -0400
> From: 	Joel M. Halpern <jmh@joelhalpern.com>
> To: 	A. Jean Mahoney <mahoney@nostrum.com>
> CC: 	gen-art@ietf.org, IETF discussion list <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-netmod-rfc6021-bis-01
>     Common YANG Data Types
> Reviewer: Joel M. Halpern
> Review Date: 19-April-2013
> IETF LC End Date: 1-May-2013
> IESG Telechat date: N/A
> 
> Summary: This document is nearly ready for publication as a Standards
> Track RFC
> 
> Major issues:
>     (The following may well be a non-issue.)
>     In the revision of the ietf-inet-types, the patterns for the new
> ip4-address-no-zone and ipv6-address-no-zone are drastically simplified
> from the ipv4-address and ipv6-address patterns.  The new
> ipv4-address-no-zone allows any sequence of decimal digits an periods,
> while the original was carefully defined as dotted quads of 0..255.
> Similarly, te ipv6-address-no-zone allows any arbitrary sequence of hex
> digits and colons.  The original patterns were very careful to match
> rules for validity.  Is there a reason for the change.

Joel,

note that ip4-address-no-zone and ipv6-address-no-zone are _derived_
from the ipv4-address and ipv6-address types:

     typedef ipv4-address-no-zone {
       type inet:ipv4-address {
         pattern '[\.0-9]*';
       }
       // ...
     }

     typedef ipv6-address-no-zone {
       type inet:ipv6-address {
         pattern '[0-9a-fA-F:]*';
       }
       // ...
     }

This means that all rules for ipv4-address and ipv6-address
respectively apply and in addition the patterns for
ip4-address-no-zone and ipv6-address-no-zone apply. In other words,
the pattern in the -no-zone versions only aim to eliminate the zone
identifier by eliminating the % symbol.

Your comment, however, made Lada discover that I missed to allow the
. for IPv4-mapped IPv6 addresses. This was not my intention and is
indeed a bug that I think needs to be fixed. There is a thread on the
netmod mailing list about this.
 
> Minor issues:
> 
> Nits/editorial comments:
> 

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From rjsparks@nostrum.com  Tue Apr 30 08:34:35 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@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>, "Liubing \(Leo\)" <leo.liubing@huawei.com>, "renum@ietf.org" <renum@ietf.org>
Subject: Re: [Gen-art] [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-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:26 2013
Return-Path: <joelja@bogus.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72EF121F9AE3 for <gen-art@ietfa.amsl.com>; Tue, 30 Apr 2013 08:43:26 -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 JoVxz580+uce for <gen-art@ietfa.amsl.com>; Tue, 30 Apr 2013 08:43:26 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3BABE21F9AE0 for <gen-art@ietf.org>; Tue, 30 Apr 2013 08:43:26 -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: "Liubing \(Leo\)" <leo.liubing@huawei.com>, "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: [Gen-art] [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Apr 2013 15:43:26 -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: gen-art@ietfa.amsl.com
Delivered-To: gen-art@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: [Gen-art] Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-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.

