
From ben@nostrum.com  Thu Aug  2 10:46:17 2012
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 C6EB611E81BC; Thu,  2 Aug 2012 10:46:17 -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 NVtHBLOq8qXu; Thu,  2 Aug 2012 10:46:16 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4B07811E81AD; Thu,  2 Aug 2012 10:46:16 -0700 (PDT)
Received: from dhcp-625b.meeting.ietf.org (dhcp-625b.meeting.ietf.org [130.129.98.91]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q72Hk62W012780 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Aug 2012 12:46:11 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <50161BD5.7040901@KingsMountain.com>
Date: Thu, 2 Aug 2012 10:46:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
References: <50161BD5.7040901@KingsMountain.com>
To: =JeffH <Jeff.Hodges@kingsmountain.com>
X-Mailer: Apple Mail (2.1485)
Received-SPF: pass (nostrum.com: 130.129.98.91 is authenticated by a trusted mechanism)
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org, IETF Discussion List <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-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: Thu, 02 Aug 2012 17:46:18 -0000

Hi, thanks for the response.  Comments inline:

On Jul 29, 2012, at 10:29 PM, =3DJeffH <Jeff.Hodges@kingsmountain.com> =
wrote:
>=20
> > -- Does this draft update any other RFCs (e.g. 2616 or 2818)? If so, =
that
> > should be explicitly flagged and mentioned in the abstract.
>=20
> Good question, I don't believe we've discussed this possibility =
directly in the websec wg. In looking at the RFCs that do update =
RFC2616, it doesn't look like draft-ietf-websec-strict-transport-sec =
(HSTS) is of that ilk.
>=20
> However, it nominally appears that an argument could be made that it'd =
be appropriate to update RFC2818 via =
draft-ietf-websec-strict-transport-sec, specifically with regards to =
Section 2.1.  Connection Initiation.
>=20
> Though, RFC2818 is Informational, which may be an issue (?). Also, =
perhaps this is something to more appropriately do via a standards-track =
rfc2818bis, i.e., have the latter reference the HSTS spec.
>=20
> this is something to discuss this coming week @IETF-84 Vancouver it =
seems.
>=20
>=20

I will comment on this in response to your post-meeting email.


> > -- I did not find any guidance on how to handle UAs that do not =
understand
> > this extension. I don't know if this needs to be normative, but the =
draft
> > should at least mention the possibility and implications.
>=20
> Agreed. My -12 working copy now contains these new subsections..
>=20
> ###
> 10.  Server Implementation and Deployment Advice
>=20
>   This section is non-normative.
>=20
> 10.1.  Non-Conformant User Agent Considerations
>=20
>   Non-conformant UAs ignore the Strict-Transport-Security header =
field,
>   thus non-conformant user agents do not address the threats described
>   in Section 2.3.1 "Threats Addressed".  Please refer to Section 14.1
>   "Non-Conformant User Agent Implications" for further discussion.
>=20
>                       .
>                       .
>=20
> 14.  Security Considerations
>                       .
>                       .
> 14.1.  Non-Conformant User Agent Implications
>=20
>   Non-conformant UAs ignore the Strict-Transport-Security header =
field,
>   thus non-conformant user agents do not address the threats described
>   in Section 2.3.1 "Threats Addressed".
>=20
>   This means that the web application and its users wielding non-
>   conformant user agents will be vulnerable to both:
>=20
>      Passive network attacks due to web site development and =
deployment
>      bugs: For example, if the web application contains any insecure,
>      non-"https", references to the web application server, and if not
>      all of its cookies are flagged as "Secure", then its cookies will
>      be vulnerable to passive network sniffing, and potentially
>      subsequent misuse of user credentials.
>=20
>      Active network attacks: If an attacker is able to place a man-in-
>      the-middle, secure transport connection attempts will likely =
yield
>      warnings to the user, but without HSTS Policy being enforced, the
>      present common practice is to allow the user to "click-through"
>      and proceed.  This renders the user and possibly the web
>      application open to abuse by such an attacker.
>=20
>   This is essentially the status-quo for all web applications and =
their
>   users in the absence of HSTS Policy.
> ###

That's all good text, but I'm not sure it actually captures my concern.

=46rom the server's perspective, the fact that non-conformant UAs may =
exist, the server cannot assume that UAs will honor the extension. This =
means that a UA might attempt unprotected access to some resource =
assumed to be protected by this extension. That is, the server can't =
merely select the extension and forget about things--it still needs to =
to take the same care to avoid leaking resources over unprotected =
connections that it would need to do if this extension did not exist in =
the first place.

I think this is implied by your last sentence above, but it would be =
better to say it explicitly.


>=20
> >
> > -- How should a UA handle potential conflicts between a the policy =
record
> > that includes the includeSubdomain, and any records for subdomains =
that might
> > have different parameters?
>=20
> this is in the draft. the short answer is that at policy enforcement =
time, "superdomain matches win".
>=20
> At "noting an HSTS Host" time, the HSTS host's policy (if expressed) =
is noted regardless of whether there are superdomain HSTS hosts =
asserting "includeSubDomains".
>=20
> perhaps this needs to be made more clear?

Maybe I'm missing something, but I'm not getting that answer from the =
text. Can you point out the specific language?

>=20
>=20
> >
> > -- section 6.1:
> >
> > The draft mentions that directives may be extended, but defers =
creation of an
> > IANA registry to the time of first extension. IANA registries are =
not
> > expensive; I suggest it be created now. If there's a good reason not =
to, then
> > the draft should still address the specification policy for =
extensions.
> >
> > Also, do you expect that some future directive might need to have a
> > "required-to-understand" status? Given that this is a =
security-affecting
> > extension, it seems likely. If so, then the mechanism for expressing =
that
> > needs to be defined in this draft.
>=20
>=20
> These are good questions, and they beg the overall question of how =
complex this simple solution really needs to be and whether we really =
think we'll need any extensions. Something for us to discuss in the =
working group meeting on Tue morning I think.

I will comment on this in the post-meeting mail.

>=20
> >
> > -- section 7.2:
> >
> > Am I correct to assume that the server must never just serve the =
content over
> > a non-secure connection? If so, it would be helpful to mention that, =
maybe
> > even normatively.
>=20
> It's a SHOULD, see the Note in that section, so it's already =
effectively stated normatively, though one needs to understand HTTP =
workings to realize it in the way you stated it above.  Perhaps could =
add a simple statement as you suggest to the intro para for section 7 =
Server Processing Model, to address this concern?
>=20

I think something of the form SHOULD redirect to HTTPS, but MUST NOT =
under any circumstances send the content unprotected would improve the =
text. That's probably already implied, and a reasonable implementor =
wouldn't due it anyway. But my experience is that some readers will find =
strange interpretations whenever you give them the wiggle room to do so, =
so it's better to be explicit.

>=20
> >
> > -- section 8.4:
> >
> > Does this imply a duty for compliant UAs to check for revocation one =
way or
> > another?
>=20
> yes. though, per other relevant specifications, as duly cited. AFAIK =
the HSTS spec doesn't need to get into the details because the =
underlying security transport specs, namely TLS, already do this.

If that duty already exists, then I see no reason to add it here. But do =
the cited specs unambiguously _require_ revocation checks? I admit to =
not being an expert here, but on a quick scan it seems more like they =
say how you can do it, but do they say you have to?=20

[...]

>=20
> > -- section 1.2:
> >
> > The description of indented notes is almost precisely the opposite =
of how
> > they are described in the RFC editor's style guide. It describes =
them as
> > "parenthetical" notes, which is how experienced RFC readers are =
likely to
> > perceive them. While it doesn't say so explicitly, I think putting =
normative
> > text in parenthetical notes should be avoided. If these are intended =
to be
> > taken more strongly than that (and by the description, I take it =
they should
> > be taken more strongly than the surrounding text), then I suggest =
choosing a
> > stronger prefix than "NOTE:"
>=20
> As it turns out, almost all the Notes are parenthetical.
>=20
> I'll render the one(s) that are normative as a regular paragraph(s) =
and leave the others as-is. Will that address your concern?
>=20

Yes, thanks.

>=20
> >
> > -- section 7:
> >
> > Does the reference to I-D.ietf-tls-ssl-version3 indicate a =
requirement for
> > SSL3?
>=20
> no, it's just that SSLv3 remains a fact of life and is referenced for =
completeness' sake.
>=20
>=20

Okay.

>=20
> >
> > -- section 8.2, paragraph 5 (first non-numbered paragraph after =
numbered
> > list)
> >
> > To be pedantic, this could be taken to mean a congruent match only =
applies if
> > the includeSubdomains flag is not present. I assume it's intended to =
apply
> > whether or not the flag is present.
>=20
> [ I am assuming you actually are referring to section 8.3, as section =
8.2 doesn't mention the includeSubdomains flag and does not contain a =
numbered list. ]
>=20
> yes, a congruent match is intended to apply whether or not the flag is =
present.
>=20
>=20

yes, I meant 8.3. And on re-reading, I think the text is fine.

>=20
> > -- section 12 and subsections:
> >
> > I was surprised to see more apparently normative material after the
> > non-normative guidance sections. I think it would improve the =
organization to
> > put this closer to the normative rules for UAs.
>=20
> We can move section 12 up ahead of the non-normative guidance =
sections.

I think that would help, thanks.

>=20
>=20
> >
> > -- section 14.1, 4th paragraph (first non-bulleted paragraph =
following bullet
> > list)
> >
> > This issue is only true for proxies that act as a TLS MiTM, right?
>=20
> yes.
>=20
>=20
> > Would
> > proxies that tunnel TLS via the CONNECT method have this issue?
>=20
> I don't think so in the general case.
>=20
> I'm not sure what terminology to use to differentiate such proxies if =
this is a detail worth addressing.
>=20

Okay

>=20
> thanks again,
>=20
> =3DJeffH
>=20
>=20
>=20
>=20
>=20
>=20


From ynir@checkpoint.com  Thu Aug  2 11:18:14 2012
Return-Path: <ynir@checkpoint.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 CF84421E80C4; Thu,  2 Aug 2012 11:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.326
X-Spam-Level: 
X-Spam-Status: No, score=-10.326 tagged_above=-999 required=5 tests=[AWL=0.273, 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 oVZqVKvkAJt4; Thu,  2 Aug 2012 11:18:14 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id A486D21E80DF; Thu,  2 Aug 2012 11:18:13 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q72IIB04011132; Thu, 2 Aug 2012 21:18:11 +0300
X-CheckPoint: {501AC1CA-1-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 2 Aug 2012 21:18:10 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Ben Campbell <ben@nostrum.com>
Date: Thu, 2 Aug 2012 21:18:09 +0300
Thread-Topic: Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
Thread-Index: Ac1w2yvprMHoxvR2RzOTiJG6heTTcA==
Message-ID: <C0912D8D-4DA8-4E0A-9C72-0AF917EE0F9E@checkpoint.com>
References: <50161BD5.7040901@KingsMountain.com> <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
In-Reply-To: <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 02 Aug 2012 13:02:26 -0700
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, "draft-ietf-websec-strict-transport-sec.all@tools.ietf.org" <draft-ietf-websec-strict-transport-sec.all@tools.ietf.org>, =JeffH <Jeff.Hodges@kingsmountain.com>, IETF Discussion List <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-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: Thu, 02 Aug 2012 18:18:15 -0000

On Aug 2, 2012, at 10:46 AM, Ben Campbell wrote:

> Hi, thanks for the response.  Comments inline:
>=20
> On Jul 29, 2012, at 10:29 PM, =3DJeffH <Jeff.Hodges@kingsmountain.com> wr=
ote:
>=20
>>> -- I did not find any guidance on how to handle UAs that do not underst=
and
>>> this extension. I don't know if this needs to be normative, but the dra=
ft
>>> should at least mention the possibility and implications.
>>=20
>> Agreed. My -12 working copy now contains these new subsections..
>>=20
>> ###
>> 10.  Server Implementation and Deployment Advice
>>=20
>>  This section is non-normative.
>>=20
>> 10.1.  Non-Conformant User Agent Considerations
>>=20
>>  Non-conformant UAs ignore the Strict-Transport-Security header field,
>>  thus non-conformant user agents do not address the threats described
>>  in Section 2.3.1 "Threats Addressed".  Please refer to Section 14.1
>>  "Non-Conformant User Agent Implications" for further discussion.
>>=20
>>                      .
>>                      .
>>=20
>> 14.  Security Considerations
>>                      .
>>                      .
>> 14.1.  Non-Conformant User Agent Implications
>>=20
>>  Non-conformant UAs ignore the Strict-Transport-Security header field,
>>  thus non-conformant user agents do not address the threats described
>>  in Section 2.3.1 "Threats Addressed".
>>=20
>>  This means that the web application and its users wielding non-
>>  conformant user agents will be vulnerable to both:
>>=20
>>     Passive network attacks due to web site development and deployment
>>     bugs: For example, if the web application contains any insecure,
>>     non-"https", references to the web application server, and if not
>>     all of its cookies are flagged as "Secure", then its cookies will
>>     be vulnerable to passive network sniffing, and potentially
>>     subsequent misuse of user credentials.
>>=20
>>     Active network attacks: If an attacker is able to place a man-in-
>>     the-middle, secure transport connection attempts will likely yield
>>     warnings to the user, but without HSTS Policy being enforced, the
>>     present common practice is to allow the user to "click-through"
>>     and proceed.  This renders the user and possibly the web
>>     application open to abuse by such an attacker.
>>=20
>>  This is essentially the status-quo for all web applications and their
>>  users in the absence of HSTS Policy.
>> ###
>=20
> That's all good text, but I'm not sure it actually captures my concern.
>=20
> From the server's perspective, the fact that non-conformant UAs may exist=
, the server cannot assume that UAs will honor the extension. This means th=
at a UA might attempt unprotected access to some resource assumed to be pro=
tected by this extension. That is, the server can't merely select the exten=
sion and forget about things--it still needs to to take the same care to av=
oid leaking resources over unprotected connections that it would need to do=
 if this extension did not exist in the first place.
>=20
> I think this is implied by your last sentence above, but it would be bett=
er to say it explicitly.

Hi Ben

On this issue, it should be noted that there is never a guarantee that a UA=
 will respect this extension:
 - Older UAs and the latest and greatest Internet Explorer do not support t=
his
 - Any UA that has not visited this website yet may try to access insecurel=
y
 - Any UA that has visited this website, but has not done so within the tim=
e period may try to access insecurely

A server can use HSTS to reflect a "no HTTP" policy, but it cannot be used =
to enforce a "only clients that know I'm STS" policy. That is outside the s=
cope of the draft.

A DNS-based approach could solve the TOFU issue, but older clients (or thos=
e without access to the secure DNS) could always try to get things over HTT=
P

Yoav


From ben@nostrum.com  Thu Aug  2 15:54:12 2012
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 3DCF811E8087; Thu,  2 Aug 2012 15:54:12 -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 9BLtIgOAPNJW; Thu,  2 Aug 2012 15:54:11 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id D23A711E8125; Thu,  2 Aug 2012 15:54:10 -0700 (PDT)
Received: from dhcp-4516.meeting.ietf.org (dhcp-4516.meeting.ietf.org [130.129.69.22]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q72Ms8Gd041594 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Aug 2012 17:54:09 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
Date: Thu, 2 Aug 2012 15:54:08 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FCCDE600-F790-4804-A860-27CF62493ADA@nostrum.com>
References: <50161BD5.7040901@KingsMountain.com> <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
To: =JeffH <Jeff.Hodges@kingsmountain.com>
X-Mailer: Apple Mail (2.1485)
Received-SPF: pass (nostrum.com: 130.129.69.22 is authenticated by a trusted mechanism)
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org, IETF Discussion List <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-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: Thu, 02 Aug 2012 22:54:12 -0000

Jeff and I spoke f2f. Pending actual text, I believe we have resolutions =
to all of my comments save those about an extension registry, which Jeff =
will discuss with other interested parties.

Thanks!

Ben.

On Aug 2, 2012, at 10:46 AM, Ben Campbell <ben@nostrum.com> wrote:

> Hi, thanks for the response.  Comments inline:
>=20
> On Jul 29, 2012, at 10:29 PM, =3DJeffH <Jeff.Hodges@kingsmountain.com> =
wrote:
>>=20
>>> -- Does this draft update any other RFCs (e.g. 2616 or 2818)? If so, =
that
>>> should be explicitly flagged and mentioned in the abstract.
>>=20
>> Good question, I don't believe we've discussed this possibility =
directly in the websec wg. In looking at the RFCs that do update =
RFC2616, it doesn't look like draft-ietf-websec-strict-transport-sec =
(HSTS) is of that ilk.
>>=20
>> However, it nominally appears that an argument could be made that =
it'd be appropriate to update RFC2818 via =
draft-ietf-websec-strict-transport-sec, specifically with regards to =
Section 2.1.  Connection Initiation.
>>=20
>> Though, RFC2818 is Informational, which may be an issue (?). Also, =
perhaps this is something to more appropriately do via a standards-track =
rfc2818bis, i.e., have the latter reference the HSTS spec.
>>=20
>> this is something to discuss this coming week @IETF-84 Vancouver it =
seems.
>>=20
>>=20
>=20
> I will comment on this in response to your post-meeting email.
>=20
>=20
>>> -- I did not find any guidance on how to handle UAs that do not =
understand
>>> this extension. I don't know if this needs to be normative, but the =
draft
>>> should at least mention the possibility and implications.
>>=20
>> Agreed. My -12 working copy now contains these new subsections..
>>=20
>> ###
>> 10.  Server Implementation and Deployment Advice
>>=20
>>  This section is non-normative.
>>=20
>> 10.1.  Non-Conformant User Agent Considerations
>>=20
>>  Non-conformant UAs ignore the Strict-Transport-Security header =
field,
>>  thus non-conformant user agents do not address the threats described
>>  in Section 2.3.1 "Threats Addressed".  Please refer to Section 14.1
>>  "Non-Conformant User Agent Implications" for further discussion.
>>=20
>>                      .
>>                      .
>>=20
>> 14.  Security Considerations
>>                      .
>>                      .
>> 14.1.  Non-Conformant User Agent Implications
>>=20
>>  Non-conformant UAs ignore the Strict-Transport-Security header =
field,
>>  thus non-conformant user agents do not address the threats described
>>  in Section 2.3.1 "Threats Addressed".
>>=20
>>  This means that the web application and its users wielding non-
>>  conformant user agents will be vulnerable to both:
>>=20
>>     Passive network attacks due to web site development and =
deployment
>>     bugs: For example, if the web application contains any insecure,
>>     non-"https", references to the web application server, and if not
>>     all of its cookies are flagged as "Secure", then its cookies will
>>     be vulnerable to passive network sniffing, and potentially
>>     subsequent misuse of user credentials.
>>=20
>>     Active network attacks: If an attacker is able to place a man-in-
>>     the-middle, secure transport connection attempts will likely =
yield
>>     warnings to the user, but without HSTS Policy being enforced, the
>>     present common practice is to allow the user to "click-through"
>>     and proceed.  This renders the user and possibly the web
>>     application open to abuse by such an attacker.
>>=20
>>  This is essentially the status-quo for all web applications and =
their
>>  users in the absence of HSTS Policy.
>> ###
>=20
> That's all good text, but I'm not sure it actually captures my =
concern.
>=20
> =46rom the server's perspective, the fact that non-conformant UAs may =
exist, the server cannot assume that UAs will honor the extension. This =
means that a UA might attempt unprotected access to some resource =
assumed to be protected by this extension. That is, the server can't =
merely select the extension and forget about things--it still needs to =
to take the same care to avoid leaking resources over unprotected =
connections that it would need to do if this extension did not exist in =
the first place.
>=20
> I think this is implied by your last sentence above, but it would be =
better to say it explicitly.
>=20
>=20
>>=20
>>>=20
>>> -- How should a UA handle potential conflicts between a the policy =
record
>>> that includes the includeSubdomain, and any records for subdomains =
that might
>>> have different parameters?
>>=20
>> this is in the draft. the short answer is that at policy enforcement =
time, "superdomain matches win".
>>=20
>> At "noting an HSTS Host" time, the HSTS host's policy (if expressed) =
is noted regardless of whether there are superdomain HSTS hosts =
asserting "includeSubDomains".
>>=20
>> perhaps this needs to be made more clear?
>=20
> Maybe I'm missing something, but I'm not getting that answer from the =
text. Can you point out the specific language?
>=20
>>=20
>>=20
>>>=20
>>> -- section 6.1:
>>>=20
>>> The draft mentions that directives may be extended, but defers =
creation of an
>>> IANA registry to the time of first extension. IANA registries are =
not
>>> expensive; I suggest it be created now. If there's a good reason not =
to, then
>>> the draft should still address the specification policy for =
extensions.
>>>=20
>>> Also, do you expect that some future directive might need to have a
>>> "required-to-understand" status? Given that this is a =
security-affecting
>>> extension, it seems likely. If so, then the mechanism for expressing =
that
>>> needs to be defined in this draft.
>>=20
>>=20
>> These are good questions, and they beg the overall question of how =
complex this simple solution really needs to be and whether we really =
think we'll need any extensions. Something for us to discuss in the =
working group meeting on Tue morning I think.
>=20
> I will comment on this in the post-meeting mail.
>=20
>>=20
>>>=20
>>> -- section 7.2:
>>>=20
>>> Am I correct to assume that the server must never just serve the =
content over
>>> a non-secure connection? If so, it would be helpful to mention that, =
maybe
>>> even normatively.
>>=20
>> It's a SHOULD, see the Note in that section, so it's already =
effectively stated normatively, though one needs to understand HTTP =
workings to realize it in the way you stated it above.  Perhaps could =
add a simple statement as you suggest to the intro para for section 7 =
Server Processing Model, to address this concern?
>>=20
>=20
> I think something of the form SHOULD redirect to HTTPS, but MUST NOT =
under any circumstances send the content unprotected would improve the =
text. That's probably already implied, and a reasonable implementor =
wouldn't due it anyway. But my experience is that some readers will find =
strange interpretations whenever you give them the wiggle room to do so, =
so it's better to be explicit.
>=20
>>=20
>>>=20
>>> -- section 8.4:
>>>=20
>>> Does this imply a duty for compliant UAs to check for revocation one =
way or
>>> another?
>>=20
>> yes. though, per other relevant specifications, as duly cited. AFAIK =
the HSTS spec doesn't need to get into the details because the =
underlying security transport specs, namely TLS, already do this.
>=20
> If that duty already exists, then I see no reason to add it here. But =
do the cited specs unambiguously _require_ revocation checks? I admit to =
not being an expert here, but on a quick scan it seems more like they =
say how you can do it, but do they say you have to?=20
>=20
> [...]
>=20
>>=20
>>> -- section 1.2:
>>>=20
>>> The description of indented notes is almost precisely the opposite =
of how
>>> they are described in the RFC editor's style guide. It describes =
them as
>>> "parenthetical" notes, which is how experienced RFC readers are =
likely to
>>> perceive them. While it doesn't say so explicitly, I think putting =
normative
>>> text in parenthetical notes should be avoided. If these are intended =
to be
>>> taken more strongly than that (and by the description, I take it =
they should
>>> be taken more strongly than the surrounding text), then I suggest =
choosing a
>>> stronger prefix than "NOTE:"
>>=20
>> As it turns out, almost all the Notes are parenthetical.
>>=20
>> I'll render the one(s) that are normative as a regular paragraph(s) =
and leave the others as-is. Will that address your concern?
>>=20
>=20
> Yes, thanks.
>=20
>>=20
>>>=20
>>> -- section 7:
>>>=20
>>> Does the reference to I-D.ietf-tls-ssl-version3 indicate a =
requirement for
>>> SSL3?
>>=20
>> no, it's just that SSLv3 remains a fact of life and is referenced for =
completeness' sake.
>>=20
>>=20
>=20
> Okay.
>=20
>>=20
>>>=20
>>> -- section 8.2, paragraph 5 (first non-numbered paragraph after =
numbered
>>> list)
>>>=20
>>> To be pedantic, this could be taken to mean a congruent match only =
applies if
>>> the includeSubdomains flag is not present. I assume it's intended to =
apply
>>> whether or not the flag is present.
>>=20
>> [ I am assuming you actually are referring to section 8.3, as section =
8.2 doesn't mention the includeSubdomains flag and does not contain a =
numbered list. ]
>>=20
>> yes, a congruent match is intended to apply whether or not the flag =
is present.
>>=20
>>=20
>=20
> yes, I meant 8.3. And on re-reading, I think the text is fine.
>=20
>>=20
>>> -- section 12 and subsections:
>>>=20
>>> I was surprised to see more apparently normative material after the
>>> non-normative guidance sections. I think it would improve the =
organization to
>>> put this closer to the normative rules for UAs.
>>=20
>> We can move section 12 up ahead of the non-normative guidance =
sections.
>=20
> I think that would help, thanks.
>=20
>>=20
>>=20
>>>=20
>>> -- section 14.1, 4th paragraph (first non-bulleted paragraph =
following bullet
>>> list)
>>>=20
>>> This issue is only true for proxies that act as a TLS MiTM, right?
>>=20
>> yes.
>>=20
>>=20
>>> Would
>>> proxies that tunnel TLS via the CONNECT method have this issue?
>>=20
>> I don't think so in the general case.
>>=20
>> I'm not sure what terminology to use to differentiate such proxies if =
this is a detail worth addressing.
>>=20
>=20
> Okay
>=20
>>=20
>> thanks again,
>>=20
>> =3DJeffH
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>=20


From mahoney@nostrum.com  Thu Aug  2 18:46:15 2012
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 04FE311E80A6 for <gen-art@ietfa.amsl.com>; Thu,  2 Aug 2012 18:46:15 -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 8NFapiVi2LdI for <gen-art@ietfa.amsl.com>; Thu,  2 Aug 2012 18:46:14 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5448421F8C58 for <gen-art@ietf.org>; Thu,  2 Aug 2012 18:46:14 -0700 (PDT)
Received: from dhcp-45b9.meeting.ietf.org (dhcp-45b9.meeting.ietf.org [130.129.69.185]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q731kDHo057193 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 2 Aug 2012 20:46:13 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <501B2D64.4010201@nostrum.com>
Date: Thu, 02 Aug 2012 18:46:12 -0700
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
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 (nostrum.com: 130.129.69.185 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-08-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: Fri, 03 Aug 2012 01:46:15 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Ben Campbell      2012-08-14    draft-ietf-mptcp-api-05

Brian Carpenter   2012-08-14    draft-ietf-ippm-testplan-rfc2679-02

Francis Dupont    2012-08-15    draft-ietf-mptcp-multiaddressed-09


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 Tom.Haynes@netapp.com  Tue Aug  7 13:03:25 2012
Return-Path: <Tom.Haynes@netapp.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 65F5421F86EA; Tue,  7 Aug 2012 13:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.542
X-Spam-Level: 
X-Spam-Status: No, score=-10.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 V1F2dljB4a9m; Tue,  7 Aug 2012 13:03:23 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id CCEE221F86D5; Tue,  7 Aug 2012 13:03:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,728,1336374000"; d="scan'208";a="674310059"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 07 Aug 2012 13:03:00 -0700
Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q77K2xvT016107; Tue, 7 Aug 2012 13:02:59 -0700 (PDT)
Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.188]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0309.002; Tue, 7 Aug 2012 13:02:53 -0700
From: "Haynes, Tom" <Tom.Haynes@netapp.com>
To: "rbarnes@bbn.com" <rbarnes@bbn.com>
Thread-Topic: [nfsv4] Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11 (fwd)
Thread-Index: AQHNUIiR3/6yfq+JwEWuYsxcwIlj9ZdPg48A
Date: Tue, 7 Aug 2012 20:02:58 +0000
Message-ID: <800EE113-E8B8-4C7A-97B6-182C01CA7149@netapp.com>
References: <CC08E06F.1AFEC%tom.haynes@netapp.com>
In-Reply-To: <CC08E06F.1AFEC%tom.haynes@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7F0B98AFBF824349B55FCCD4B78DDEDE@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: nfsv4 list <nfsv4@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org" <draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] [nfsv4] Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11 (fwd)
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, 07 Aug 2012 20:03:25 -0000

Hi Richard,

Here is the proposed text for the remaining issues you raised:

=3D=3D=3D=3D=3D=3D=3D

1. Section 4 does not adequately specify how the certificate in the
FedFsNsdbParams should be used in the verification process.  Is it to be
used as a trust anchor, so that any subordinate certificate is considered
valid?  Or perhaps it is to be matched against the end-entitycertificate.
In either case, it seems like it would be sufficient to
provision a certificate fingerprint (or even a public key fingerprint)inste=
ad
of the whole certificate.

Original:
------------
A value of FEDFS_SEC_TLS indicates that the StartTLS security
    mechanism [RFC4513] MUST be used to protect all connections to the
    NSDB.  In this case, the secData array will contain an X.509v3
    certificate in binary DER format [RFC5280].  The certificate
    SHOULD be used by the fileserver to authenticate the identity of

Lentini, et al.         Expires December 16, 2012              [Page 17]
Internet-Draft  Admin Protocol for Federated Filesystems       June 2012

    the NSDB.  In particular, this certificate SHOULD be used to
    validate the NSDB's TLS certificate list chain (see 7.4.2 of
    [RFC5246]).  The certificate could be that of a certificate
    authority or a self-signed certificate.


New:
-------
A value of FEDFS_SEC_TLS indicates that the StartTLS security
mechanism [RFC4513] MUST be used to protect all connections to the
NSDB.  In this case, the secData array will contain an X.509v3
root certificate in binary DER format [RFC5280] fulfilling the TLS
requirement that root keys be distributed independently from the TLS
protocol. The certificate MUST be used by the fileserver
as a Trust Anchor to validate the NSDB's TLS server certificate list
chain (see section 7.4.2 of [RFC5246]) and thus authenticate the identitiy
of the NSDB. The certificate could be that of a certificate authority or
a self-signed cert.

=3D=3D=3D=3D=3D=3D=3D

2. In the security considerations, the document should discuss the
implications of provisioning trust information in this way (depending on
how it is used), and any requirements for security mechanisms to be used
in these cases.

Original
---------
6.  Security Considerations

 The ONC RPC protocol supports authentication, integrity and privacy
 via the RPCSEC_GSS framework [RFC2203].  Fileservers which support
 the FedFS administration protocol described above MUST support
 RPCSEC_GSS.

 FEDFS_GET_LIMITED_NSDB_PARAMS's interaction with the NSDB's
 connection parameters is discussed in Section 5.10.2.


New
---

6.  Security Considerations

 The ONC RPC protocol supports authentication, integrity and privacy
 via the RPCSEC_GSS framework [RFC2203].  Fileservers which support
 the FedFS administration protocol described above MUST support
 RPCSEC_GSS. When RPCSEC_GSS is employed, RPCSEC_GSS data integrity
 SHOULD be used.

 It is strongly RECOMMENDED that an Access Control Service be employed
 to restrict access to a fileserver's FedFS administration configuration
 data via the FedFS administrative protocol to prevent FedFS namespace
 corruption, and protect NSDB communication parameters.

 For example, when the FedFsNsdbParams secData field value FEDFS_SEC_TLS
 is chosen, the payload is used to provision the trust anchor root
 certificate for TLS secure communication between the fileserver and the NS=
DB.
 In this case, RPCSEC_GSS with data integrity SHOULD be employed along with
 an Access Control Service to restrict access to domain adminstrators.

 FEDFS_GET_LIMITED_NSDB_PARAMS's interaction with the NSDB's
 connection parameters is discussed in Section 5.10.2.

Please let us know if these address the points you raised.

Thanks,
Tom

On Jul 27, 2012, at 12:29 PM, Chuck Lever wrote:

> ..returning FEDFS_ERR_ACCESS... =20
>=20
> That should also go in the body of the Implementation discussion in the A=
DMIN draft, I think.
>=20
> Sent from my iPhone
>=20
> On Jul 27, 2012, at 11:48 AM, "Adamson, Andy" <William.Adamson@netapp.com=
> wrote:
>=20
>> Here is a stab at updating the Security Considerations section to addres=
s the second Gen-ART review comment.
>>=20
>> -->Andy
>>=20
>> ------- second Gen-ART review comment -------------
>> 2. In the security considerations, the document should discuss the
>> implications of provisioning trust information in this way (depending on
>> how it is used), and any requirements for security mechanisms to be used
>> in these cases.
>> ----------------------
>>=20
>> Original
>> ---------
>> 6.  Security Considerations
>>=20
>> The ONC RPC protocol supports authentication, integrity and privacy
>> via the RPCSEC_GSS framework [RFC2203].  Fileservers which support
>> the FedFS administration protocol described above MUST support
>> RPCSEC_GSS.
>>=20
>> FEDFS_GET_LIMITED_NSDB_PARAMS's interaction with the NSDB's
>> connection parameters is discussed in Section 5.10.2.
>>=20
>>=20
>> New
>> ---
>>=20
>> 6.  Security Considerations
>>=20
>> The ONC RPC protocol supports authentication, integrity and privacy
>> via the RPCSEC_GSS framework [RFC2203].  Fileservers which support
>> the FedFS administration protocol described above MUST support
>> RPCSEC_GSS. When RPCSEC_GSS is employed, RPCSEC_GSS data integrity=20
>> SHOULD be used.
>>=20
>> An Access Control Service SHOULD be employed to restrict access to a
>> fileserver's FedFS administration configuration data via the FedFS
>> administrative protocol, returning FEDFS_ERR_ACCESS when the caller
>> does not have the correct permission to perform the requested operation.
>>=20
>> When NSDB connection paramters contains security mechanism sensitive
>> information, RPCSEC_GSS with data integrity SHOULD be used.
>>=20
>> For example, when the FedFsNsdbParams secData field value FEDFS_SEC_TLS
>> is chosen, the payload is used to provision the trust anchor root=20
>> certificate for TLS secure communication between the fileserver and the =
NSDB.
>> In this case, RPCSEC_GSS with data integrity SHOULD be employed along wi=
th
>> an Access Control Service.
>>=20
>> FEDFS_GET_LIMITED_NSDB_PARAMS's interaction with the NSDB's
>> connection parameters is discussed in Section 5.10.2.
>>=20
>>=20
>> On Jul 27, 2012, at 10:30 AM, Nico Williams wrote:
>>=20
>>> Security implementation mandates are fine.  Security use mandates are
>>> at least controversial, and probably impractical.


On Jun 22, 2012, at 8:06 AM, "Haynes, Tom" <Tom.Haynes@netapp.com> wrote:

> <comments inline>
>=20
> On 6/20/12 11:53 AM, "James Lentini" <jlentini@netapp.com> wrote:
>=20
>>=20
>> Below is the Gen-ART review comments for the FedFS admin protocol.
>>=20
>> -james
>>=20
>> ---------- Forwarded message ----------
>> Date: Tue, 19 Jun 2012 11:31:42 -0400
>> From: Richard L. Barnes <rbarnes@bbn.com>
>> To: ietf@ietf.org, The IESG <iesg@ietf.org>,
>>   draft-ietf-nfsv4-federated-fs-admin@tools.ietf.org, gen-art@ietf.org
>> Subject: Gen-ART LC review of draft-ietf-nfsv4-federated-fs-admin-11
>>=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-nfsv4-federated-fs-admin-11
>> Reviewer: Richard Barnes
>> Review Date: Jun-19-2012
>> IETF LC End Date: Not known
>> IESG Telechat date: Jun-28-2012
>>=20
>> Summary: Almost ready, couple of issues
>>=20
>> MAJOR:=20
>>=20
>> 4. / 7.
>> This protocol allows for the provisioning of security information as par=
t
>> of the FedFsNsdbParams, in the form of a certificate to be used in
>> verifying a TLS server certificate.  There are two notable issues with
>> how the document does this now:
>> 1. Section 4 does not adequately specify how the certificate in the
>> FedFsNsdbParams should be used in the verification process.  Is it to be
>> used as a trust anchor, so that any subordinate certificate is considere=
d
>> valid?  Or perhaps it is to be matched against the end-entity
>> certificate.  In either case, it seems like it would be sufficient to
>> provision a certificate fingerprint (or even a public key fingerprint)
>> instead of the whole certificate.
>> 2. In the security considerations, the document should discuss the
>> implications of provisioning trust information in this way (depending on
>> how it is used), and any requirements for security mechanisms to be used
>> in these cases.
>>=20
>=20
>=20
> I'm going to have to work with the rest of the group to answer this one.
>=20
>=20
>>=20
>> MINOR:
>>=20
>> 2.=20
>> It's not clear what the difference is between utf8string_cs and
>> utf8string_cis.  Should you mention at some point that these MUST be
>> UTF-8, even though the XDR won't enforce that?  (Say, at the beginning o=
f
>> Section 4?)
>=20
>=20
> Argh, we did away with utf8string_cs and utf8string_cis in 3530bis.
>=20
>=20
> utf8string_cis should be utf8val_REQUIRED4
> utf8string_cs should be ascii_REQUIRED4
>=20
> In 3530bis, these are defined as:
>=20
> typedef :opaque  :utf8string<>:UTF-8 encoding for strings.
> typedef :utf8string:utf8_expected:String expected to be UTF-8 but no
> validation
> typedef :utf8string:utf8val_RECOMMENDED4:String SHOULD be sent UTF-8 and
> SHOULD be validated
> typedef :utf8string:utf8val_REQUIRED4:String MUST be sent UTF-8 and MUST
> be validated
> typedef :utf8string:ascii_REQUIRED4:String MUST be sent as ASCII and thus
> is automatically UTF-8
>=20
>=20
> I'll change the types and there is already some text pointing the reader
> to Chapter 12 of 3530bis.
>=20
>=20
>>=20
>> 3.
>> It's not clear to me how FEDFS_ERR_PERM differs from FEDFS_ERR_ACCESS.  =
I
>> don't see it called out for use anywhere in the procedure calls.  Perhap=
s
>> this is a legacy of prior versions that should be deleted?
>=20
>=20
> This is inherited from the base NFSv4.0 documentation and also NFSv3. It
> is also the difference between EPERM and EACCES. (see
> http://www.wlug.org.nz/EACCES)
>=20
>=20
> 13.1.6.1.  NFS4ERR_ACCESS (Error Code 13)
>=20
>   Indicates permission denied.  The caller does not have the correct
>   permission to perform the requested operation.  Contrast this with
>   NFS4ERR_PERM (Section 13.1.6.2), which restricts itself to owner or
>   privileged user permission failures.
>=20
> 13.1.6.2.  NFS4ERR_PERM (Error Code 1)
>=20
>   Indicates requester is not the owner.  The operation was not allowed
>   because the caller is neither a privileged user (root) nor the owner
>   of the target of the operation.
>=20
>=20
>=20
>=20
>=20
>=20
>>=20
>>=20
>> EDITORIAL:=20
>>=20
>> 3.=20
>> The definition of FEDFS_ERR_LOOP isn't actually related to looping.  It
>> seems like this should either detect a loop (e.g., via a repeated name),
>> or be renamed something like FEDFS_ERR_TOOMANYREFERS.
>=20
>=20
> This has its roots in a Linux error code:
>=20
>>> As I recall this error is supposed to be returned when fedfsd is passed
>>> a pathname that contains too many symlinks.  The equivalent errno on
>>> Linux is called ELOOP.
>=20
> We are striving to maintain parity.
>=20
>=20
>=20
>=20
>=20
>>=20
>> 4. "The port is the NSDB transport port for the LDAP interface"
>> Suggest rewording to clarify that this is an LDAP/TCP port (I initially
>> wondered if other transports could be used), e.g.:
>> "The port value in the FedFsNsdbName indicates the LDAP port on the NSDB=
"
>=20
>=20
> Thanks, we've been struggling with this issue, I'll take your suggested
> change here.
>=20
>>=20
>> _______________________________________________
>> nfsv4 mailing list
>> nfsv4@ietf.org
>> https://www.ietf.org/mailman/listinfo/nfsv4
>=20
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4


From brian.e.carpenter@gmail.com  Thu Aug  9 06:52:58 2012
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 C7DE221F8665 for <gen-art@ietfa.amsl.com>; Thu,  9 Aug 2012 06:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.473
X-Spam-Level: 
X-Spam-Status: No, score=-101.473 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 ea57572pIGq8 for <gen-art@ietfa.amsl.com>; Thu,  9 Aug 2012 06:52:57 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 74BC221F8650 for <gen-art@ietf.org>; Thu,  9 Aug 2012 06:52:57 -0700 (PDT)
Received: by eekb45 with SMTP id b45so161028eek.31 for <gen-art@ietf.org>; Thu, 09 Aug 2012 06:52:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=lZ4Z3Efv3f7SVJhOU7Hj6oqGGHj86zDqrp7Vi7Srguo=; b=gv+4WFZqQdcD0EogwWKyTiHgveSDI5ZhqW27LFgTTOnvoHIgl79wPvfF24wfo4QNqs QP7/gwJgeD52/7iNiPZwV0oGYVNZeqgYwCbfQpmKRyE/IX4k1mdf6JoAYQT24ixBPG8N K3lLym6SCNeIGq7kTSaZSF+ZCOmj3N4S7/nxT3P/zb8zDN4jirHckryWHyhOmfklq93O vGRyo6eGoATmTVGpVlY5ma/f+Bs8Bis3cRQLnPxR+MXW7KL/7Do6V/RyKZ9T4m4lpSJE SE8e5jcg182BJsQ+ViUs6kVOc/MnLBrCUDcamGLgHoYJjLEUeXt0wlGVtTzoBInEk/Si J3bw==
Received: by 10.14.175.130 with SMTP id z2mr27858687eel.0.1344520376216; Thu, 09 Aug 2012 06:52:56 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-33.as13285.net. [2.102.216.33]) by mx.google.com with ESMTPS id k41sm3686023eep.13.2012.08.09.06.52.53 (version=SSLv3 cipher=OTHER); Thu, 09 Aug 2012 06:52:54 -0700 (PDT)
Message-ID: <5023C0BC.5040605@gmail.com>
Date: Thu, 09 Aug 2012 14:53:00 +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-ippm-testplan-rfc2679.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------080607070903060606000102"
Subject: [Gen-art] Gen-ART LC review of draft-ietf-ippm-testplan-rfc2679-02.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, 09 Aug 2012 13:52:58 -0000

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

Please see attached review.




--------------080607070903060606000102
Content-Type: text/plain;
 name="draft-ietf-ippm-testplan-rfc2679-02-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-ippm-testplan-rfc2679-02-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBM
YXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4NCg0KRG9jdW1lbnQ6IGRyYWZ0
LWlldGYtaXBwbS10ZXN0cGxhbi1yZmMyNjc5LTAyLnR4dA0KUmV2aWV3ZXI6IEJyaWFuIENh
cnBlbnRlcg0KUmV2aWV3IERhdGU6IDIwMTItMDgtMDkNCklFVEYgTEMgRW5kIERhdGU6IDIw
MTItMDgtMTQNCklFU0cgVGVsZWNoYXQgZGF0ZTogDQoNClN1bW1hcnk6ICBBbG1vc3QgcmVh
ZHkNCi0tLS0tLS0tDQoNCkNvbW1lbnQ6DQotLS0tLS0tLQ0KDQpJIG1pc3NlZCB0aGUgZGlz
Y3Vzc2lvbiBvZiBSRkMgNjU3NiwgYnV0IEkgbm90ZSB0aGF0IGl0cyBhYnN0cmFjdCBpcyBs
b2dpY2FsbHkNCmluY29uc2lzdGVudCAgd2l0aCBSRkMgNjQxMCwgaW4gdGhhdCB0aGUgc3Rh
bmRhcmRzIHRyYWNrIG5vIGxvbmdlciByZXF1aXJlcw0KZm9ybWFsIGludGVyb3BlcmFiaWxp
dHkgcmVwb3J0cy4gNjU3NiBhbHNvIGZhaWxzIHRvIG1lbnRpb24gY2hlY2tpbmcgZXJyYXRh
IGFzDQpyZXF1aXJlZCBieSA2NDEwLg0KDQpTaWduaWZpY2FudCBpc3N1ZXM6DQotLS0tLS0t
LS0tLS0tLS0tLS0tDQoNCkF0IHRoZSBlbmQgb2Ygc2VjdGlvbiA2Og0KDQo+ICAgT25seSB0
aGUgVHlwZS1QLU9uZS13YXktRGVsYXktSW52ZXJzZS1QZXJjZW50aWxlIGhhcyBiZWVuIGln
bm9yZWQgaW4NCj4gICBib3RoIGltcGxlbWVudGF0aW9ucywgc28gaXQgaXMgYSBjYW5kaWRh
dGUgZm9yIHJlbW92YWwgaW4gUkZDMjY3OWJpcy4NCg0KV2hhdCBpcyB0aGlzIHRlbGxpbmcg
dXM/IFRoYXQgUkZDIDI3NjkgaXNuJ3QgcmVhZHkgZm9yIGFkdmFuY2VtZW50Pw0KT3IgdGhh
dCB0aGlzIGlzIHRoZSBvbmx5IGRpc2NyZXBhbmN5IGFuZCBjYW4gYmUgc2FmZWx5IGlnbm9y
ZWQ/DQoNCkluIGZhY3QsIHdoYXQgaXMgdGhlIG92ZXJhbGwgY29uY2x1c2lvbj8gSSB3YXMg
cmVhbGx5IGV4cGVjdGluZyB0byBmaW5kDQphIHN1bW1hcnkgYW5kIGNvbmNsdXNpb24gYXQg
dGhlIGVuZCBvZiB0aGUgZG9jdW1lbnQuIFRoZSBBYnN0cmFjdCBzYXlzDQp0aGF0IHRoZSBk
cmFmdCBwcm9wb3NlcyBhZHZhbmNlbWVudCwgYnV0IHRoZSBib2R5IG9mIHRoZSB0ZXh0IGRv
ZXNuJ3QNCmFjdHVhbGx5IHNheSB0aGF0IGFueXdoZXJlIHRoYXQgSSBub3RpY2VkLg0KDQpO
aXRzOg0KLS0tLS0NCg0KPiBvICBUZXN0IGR1cmF0aW9uID0gMzAwIHNlY29uZHMgKE1hcmNo
IDI5KQ0KDQpUaGlzIGFuZCBvdGhlciBkYXRlcyBzaG91bGQgaW5jbHVkZSB0aGUgeWVhci4N
Cg0KVGhlcmUncyBvbmUgZXJyYXR1bSBhZ2FpbnN0IFJGQyAyNjc5LiBXaGlsZSBpdCdzIHRy
aXZpYWwsIGFjY29yZGluZyB0byB0aGUNCmNyaXRlcmlhIGluIFJGQyA2NDEwLCBpdCBzaG91
bGQgYmUgcmV2aWV3ZWQuIE9uZSBzZW50ZW5jZSB3b3VsZCBiZSBlbm91Z2guDQoNCg0KDQoN
Cg0K
--------------080607070903060606000102--

From mahoney@nostrum.com  Thu Aug  9 15:39:03 2012
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 49D5321F86C1 for <gen-art@ietfa.amsl.com>; Thu,  9 Aug 2012 15:39: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 Rd-EWIltebjT for <gen-art@ietfa.amsl.com>; Thu,  9 Aug 2012 15:39:02 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id C4B6C21F86B8 for <gen-art@ietf.org>; Thu,  9 Aug 2012 15:39:02 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-102-202.dllstx.fios.verizon.net [173.57.102.202]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q79Md2nM017344 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 9 Aug 2012 17:39:02 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <50243C05.3080006@nostrum.com>
Date: Thu, 09 Aug 2012 17:39:01 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
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 (nostrum.com: 173.57.102.202 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-08-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, 09 Aug 2012 22:39:03 -0000

Hi all,

The following reviewers have assignments:

Reviewer            LC end        Draft

Christer Holmberg   2012-09-03 draft-kumaki-murai-l3vpn-rsvp-te-06

David Black         2012-08-20 draft-ietf-pwe3-mpls-eth-oam-iwk-06

Elwyn Davies        2012-08-22    draft-ietf-idr-as0-05

Joel Halpern        2012-08-23 draft-ietf-armd-problem-statement-03

Kathleen Moriarty   2012-08-23 draft-ietf-mmusic-media-loopback-22


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 Aug  9 15:42:28 2012
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 0B98521F86D6 for <gen-art@ietfa.amsl.com>; Thu,  9 Aug 2012 15:42: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, 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 rCCDhi8pK0um for <gen-art@ietfa.amsl.com>; Thu,  9 Aug 2012 15:42:27 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 397F621F86D4 for <gen-art@ietf.org>; Thu,  9 Aug 2012 15:42:27 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-102-202.dllstx.fios.verizon.net [173.57.102.202]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q79MgQtW017683 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 9 Aug 2012 17:42:26 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <50243CD2.6020901@nostrum.com>
Date: Thu, 09 Aug 2012 17:42:26 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
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 (nostrum.com: 173.57.102.202 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-08-16 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, 09 Aug 2012 22:42:28 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft

Brian Carpenter        2012-08-08 draft-yegin-pana-encr-avp-06 *

David Black            2011 - draft-polk-local-emergency-rph-namespace-02 *
David Black            2012-06-28 draft-ietf-bliss-shared-appearances-13 *

Meral Shirazipour      2012-07-11   draft-ietf-v6ops-6204bis-09 **

Vijay Gurbani          2012-08-15 
draft-ietf-opsawg-automated-network-configuration-04
Vijay Gurbani          2012-07-06 draft-ietf-ospf-prefix-hiding-05 *
Vijay Gurbani          2012-07-19 draft-ietf-ospf-hybrid-bcast-and-p2mp-03


* Earlier draft reviewed
** Already reviewed
- LC data not in the review tool since it pre-dates the use of the tool


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 david.black@emc.com  Thu Aug  9 16:05:16 2012
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 432D321F85C7; Thu,  9 Aug 2012 16:05:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.404
X-Spam-Level: 
X-Spam-Status: No, score=-102.404 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 qO-dHgqP9ret; Thu,  9 Aug 2012 16:05:15 -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 8670521F85C5; Thu,  9 Aug 2012 16:05:15 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q79N4nAn028185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 19:04:50 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 9 Aug 2012 19:04:40 -0400
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q79N4eAR021633; Thu, 9 Aug 2012 19:04:40 -0400
Received: from mxhub39.corp.emc.com (128.222.70.106) by mxhub13.corp.emc.com (128.222.70.234) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 9 Aug 2012 19:04:40 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub39.corp.emc.com ([128.222.70.106]) with mapi; Thu, 9 Aug 2012 19:04:40 -0400
From: "Black, David" <david.black@emc.com>
To: "michelle.cotton@icann.org" <michelle.cotton@icann.org>, "leo.vegoda@icann.org" <leo.vegoda@icann.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Thu, 9 Aug 2012 19:04:38 -0400
Thread-Topic: Gen-ART review of draft-vegoda-cotton-rfc5735bis-02
Thread-Index: Ac12g1nlR2o6ek4yS0CffYeN22Tw+A==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208F1240F@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>
Subject: [Gen-art] Gen-ART review of draft-vegoda-cotton-rfc5735bis-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, 09 Aug 2012 23:05:16 -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-vegoda-cotton-rfc5735bis-02
Reviewer: David L. Black
Review Date: August 9, 2012
IETF LC End Date: August 9, 2012

Summary:
This draft is basically ready for publication, but has nits that
should be fixed before publication.

This draft provides an updated list of the special use IPv4 address blocks
that have been allocated by IANA along with explanations of their special
uses.

I found one nit and idnits found another one.

Section 5 - the first sentence in the second paragraph is:

   The domain name and IP address spaces involve policy issues (in
   addition to technical issues) so that the requirements of [RFC2860]
   do not apply generally to those spaces.

I'm surprised by "do not apply generally".  I would have expected that
the policy issues create requirements and constraints above and beyond
the requirements in RFC 2860 as opposed to replacing those requirements.

idnits 2.12.13 complained about a lot of IP addresses that aren't in
the address ranges used for examples.  These complaints can be ignored,
but idnits did find one actual nit:

  =3D=3D Unused Reference: 'RFC6441' is defined on line 346, but no explici=
t
     reference was found in the text

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 david.black@emc.com  Thu Aug  9 16:08:45 2012
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 CEBD921F85F0; Thu,  9 Aug 2012 16:08:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.482
X-Spam-Level: 
X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.117, 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 5rrgaodBTzVD; Thu,  9 Aug 2012 16:08: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 BDE6921F85DD; Thu,  9 Aug 2012 16:08:44 -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 q79N8fCO015783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 19:08:42 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Thu, 9 Aug 2012 19:08:21 -0400
Received: from mxhub11.corp.emc.com (mxhub11.corp.emc.com [10.254.92.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q79N8Iec010299; Thu, 9 Aug 2012 19:08:18 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub11.corp.emc.com ([10.254.92.106]) with mapi; Thu, 9 Aug 2012 19:08:18 -0400
From: "Black, David" <david.black@emc.com>
To: "alan.b.johnston@gmail.com" <alan.b.johnston@gmail.com>, "mohsen.soroush@sylantro.com" <mohsen.soroush@sylantro.com>, "vvenkatar@gmail.com" <vvenkatar@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Thu, 9 Aug 2012 19:08:17 -0400
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-13
Thread-Index: Ac1Vb8Dn5IHpqMlJQDmiZm9plrtFJQL1mcsgBU9mF9A=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208F12410@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71208DD8672@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208DD8672@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: Shida Schubert <shida@ntt-at.com>, "bliss@ietf.org" <bliss@ietf.org>, IETF Discussion <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-bliss-shared-appearances-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: Thu, 09 Aug 2012 23:08:46 -0000

These resolutions have been carried forward to the -13 version of the draft=
.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Friday, July 13, 2012 6:25 PM
> To: Black, David; alan.b.johnston@gmail.com; mohsen.soroush@sylantro.com;
> vvenkatar@gmail.com; gen-art@ietf.org
> Cc: Shida Schubert; bliss@ietf.org; IETF Discussion; Robert Sparks
> Subject: Gen-ART review of draft-ietf-bliss-shared-appearances-12
>=20
> The -12 version of this draft resolves all of the comments in the
> Gen-ART review of the -11 version.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Thursday, June 28, 2012 4:51 PM
> > To: alan.b.johnston@gmail.com; mohsen.soroush@sylantro.com;
> > vvenkatar@gmail.com; gen-art@ietf.org
> > Cc: Black, David; Shida Schubert; bliss@ietf.org; IETF Discussion; Robe=
rt
> > Sparks
> > Subject: Gen-ART review of draft-ietf-bliss-shared-appearances-11
> >
> > 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-bliss-shared-appearances-11
> > Reviewer: David L. Black
> > Review Date: June 28, 2012
> > IETF LC End Date: June 28, 2012
> > IESG Telechat date: (if known)
> >
> > Summary:
> >
> > This draft is on the right track but has open issues, described in the
> review.
> >
> > This draft describes support for shared appearances in support of multi=
-line
> > and shared-line telephone often found in businesses.  All of the open i=
ssues
> > are minor.  The draft is well-written and reasonably clear for the most
> part,
> > although significant SIP expertise is required to completely understand=
 it.
> >
> > Major issues:  None.
> >
> > Minor issues:
> >
> > 4.1 - REQ-16:
> >
> >    in this case, seizing the line is the same thing as dialing.
> >
> > That seems wrong - I would have thought it was a "prerequisite" as
> > opposed to "the same thing" because seizing the line is immediately
> > followed by a dialing request.
> >
> > 5.3.
> >
> >    A user may select an appearance number but then abandon placing a
> >    call (go back on hook).  In this case, the UA MUST free up the
> >    appearance number by removing the event state with a PUBLISH as
> >    described in [RFC3903].
> >
> > What happens when that can't be done due to UA or network failure?
> >
> > 5.4.
> >
> >    A 400 response is returned if the chosen appearance number is invali=
d,
> >
> > Is that always a 400 (Bad Request) or is any 4xx response allowed?  If
> > it's always 400, add the words "Bad Request" after "400".
> >
> >    If the Appearance Agent policy does not allow this, a 400 response
> >    is returned.
> >
> > Same question.  In addition, is 403 Forbidden allowed here?
> >
> >    If an INVITE is sent by a member of the group to the shared AOR (i.e=
.
> >    they call their own AOR), the Appearance Agent MUST assign two
> >    appearance numbers.  The first appearance number will be the one
> >    selected or assigned to the outgoing INVITE.  The second appearance
> >    number will be another one assigned by the Appearance Agent for the
> >    INVITE as it is forked back to the members of the group.
> >
> > How does that interact with the single appearance UAs in 8.1.1 that won=
't
> > understand the second appearance number?  A warning that such a UA can'=
t
> > pick up its call to its own AOR would suffice, either here or in 8.1.1.
> >
> > 9.1
> >
> >    A UA that has no knowledge of appearances must will only have
> >    appearance numbers for outgoing calls if assigned by the Appearance
> >    Agent.  If the non-shared appearance UA does not support Join or
> >    Replaces, all dialogs could be marked "exclusive" to indicate that
> >    these options are not available.
> >
> > Should that "could be marked" be changed to "SHOULD be marked" ?
> > Also, analogous questions for "could" in 9.2 and "can" in 9.3.
> >
> > All three of these affect interoperability.
> >
> > 12. Security Considerations
> >
> > In general, this section is weak on rationale - the second, third and
> > fourth paragraphs should all explain more about the purpose of and/or
> > rationale for their security requirements (e.g., what does the security
> > mechanism protect against and when/why might that protection be desired
> > and/or required?).
> >
> >    NOTIFY or PUBLISH message bodies that provide the dialog state
> >    information and the dialog identifiers MAY be encrypted end-to-end
> >    using the standard mechanisms.
> >
> > What are "the standard mechanisms"?  List them, and provide references,
> > please.
> >
> > Please ensure that the section 6 XML and Section 7 ABNF are
> > syntax-checked with actual tools.
> >
> > Nits/editorial comments:
> >
> > p.10:
> >
> >    The next section discusses the operations used to implement parts of
> >    the shared appearance feature.
> >
> > "The following list describes the operations ..." would be better.
> >
> > 5.3.1.
> >
> >    A UA wanting to place a call but not have an appearance number
> >    assigned publishes before sending the INVITE without an 'appearance'
> >    element but with the 'shared' event package parameter present.
> >
> > I think I understand what was intended here, but this would be clearer
> > if "publishes" was replaced with language about sending a PUBLISH.
> > It's also not completely clear whether "without" applies to the
> > INVITE or the PUBLISH, so this sentence probably needs to be reworded.
> >
> > 5.4. - Expand B2BUA acronym on first use.
> >
> > idnits 2.12.13 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 david.black@emc.com  Thu Aug  9 16:17:09 2012
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 1D7CB21F8618; Thu,  9 Aug 2012 16:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.482
X-Spam-Level: 
X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.117, 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 OlD9v+UKxFbo; Thu,  9 Aug 2012 16:17:08 -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 6404321F8617; Thu,  9 Aug 2012 16:17:08 -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 q79NH6xJ022805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Aug 2012 19:17:07 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 9 Aug 2012 19:16:55 -0400
Received: from mxhub29.corp.emc.com (mxhub29.corp.emc.com [128.222.70.169]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q79NGsAE030948; Thu, 9 Aug 2012 19:16:54 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub29.corp.emc.com ([128.222.70.169]) with mapi; Thu, 9 Aug 2012 19:16:54 -0400
From: "Black, David" <david.black@emc.com>
To: "James M. Polk" <jmpolk@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 9 Aug 2012 19:16:53 -0400
Thread-Topic: Gen-ART review of draft-polk-local-emergency-rph-namespace-02
Thread-Index: AcxA9hUNwavoqEelQfeUxmCy5d9fy01jouJA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208F12412@MX15A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E058941360C@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E058941360C@MX14A.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
Subject: [Gen-art] Gen-ART review of draft-polk-local-emergency-rph-namespace-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, 09 Aug 2012 23:17:09 -0000

The nits in the Gen-ART review of the -01 version of this draft
have not been addressed in the -02 version.

idnits found one existing nit and one new one:

  =3D=3D It seems as if not all pages are separated by form feeds - found 0=
 form
     feeds but 8 pages

  =3D=3D Line 156 has weird spacing: '...n, this  is a ...'

Thanks,
--David


> -----Original Message-----
> From: Black, David
> Sent: Tuesday, July 12, 2011 8:45 PM
> To: James M. Polk; gen-art@ietf.org; ietf@ietf.org
> Cc: Black, David; Robert Sparks
> Subject: Gen-ART review of draft-polk-local-emergency-rph-namespace-01
>=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-polk-local-emergency-rph-namespace-01
> Reviewer: David L. Black
> Review Date: July 12, 2011
> IETF LC End Date: July 13, 2011
>=20
> Summary:
> This draft is basically ready for publication, but has nits that should b=
e
> fixed before publication.
>=20
> This draft defines a SIP Resource Priority header namespace, "esnet", for=
 use
> in
> providing preferential treatment to emergency calls (e.g., from on-scene
> responders).
>=20
> This field is an addition to rather than a replacement for existing notio=
ns of
> priority in the SIP Resource Priority header.  Section 2 explains why thi=
s was
> done, but section 2 is a bit sloppy and imprecise.  Some level of impreci=
sion
> is
> necessary as this draft deliberately does not specify how this header
> namespace
> is used to provide preferential treatment.  Nonetheless, the following tw=
o
> items
> could be improved in Section 2's discussion:
>=20
> 1) Explain the reason for including the second paragraph, the paragraph
> 	that references RFC 4412's discouragement of modification of priorities
> 	within an administrative domain.  That paragraph's not connected to the
> 	rest of section 2.
> 2) Explicitly state that one of the anticipated uses of the priorities in=
 the
> 	esnet namespace is to override the ordinary priorities found elsewhere
> in
> 	the Resource Priority header.
>=20
> Small nit: There's an extraneous "to" in the first line of section 3:
>=20
>    The "esnet" namespace should not to be considered generic for all
>                                     ^^
>=20
> idnits 2.12.12 found a few formatting problems:
>=20
>   =3D=3D You're using the IETF Trust Provisions' Section 6.b License Noti=
ce from
>      12 Sep 2009 rather than the newer Notice from 28 Dec 2009.  (See
>      http://trustee.ietf.org/license-info/)
>=20
>   =3D=3D It seems as if not all pages are separated by form feeds - found=
 0 form
>      feeds but 7 pages
>=20
>   =3D=3D The copyright year in the IETF Trust and authors Copyright Line =
does not
>      match the current year
>=20
>=20
> 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-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From jmh@joelhalpern.com  Thu Aug  9 19:28:55 2012
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 81CB721F8646; Thu,  9 Aug 2012 19:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[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 qpZ8ls+y1mzc; Thu,  9 Aug 2012 19:28:55 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 054BE21F8644; Thu,  9 Aug 2012 19:28:55 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id D79AF557F2F; Thu,  9 Aug 2012 19:28:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 072541619C1; Thu,  9 Aug 2012 19:28:54 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.1.2] (c-71-204-207-35.hsd1.de.comcast.net [71.204.207.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 159421619C0; Thu,  9 Aug 2012 19:28:52 -0700 (PDT)
Message-ID: <502471DB.80303@joelhalpern.com>
Date: Thu, 09 Aug 2012 22:28:43 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <50243C05.3080006@nostrum.com>
In-Reply-To: <50243C05.3080006@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, "armd@ietf.org" <armd@ietf.org>
Subject: [Gen-art] Gen-art] review: draft-ietf-armd-problem-statement-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, 10 Aug 2012 02:28:55 -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-armd-problem-statement-03
     Problem Statement for ARMD
Reviewer: Joel M. Halpern
Review Date: 9-Aug-2012
IETF LC End Date: 23-Aug-2012
IESG Telechat date: N/A

Summary: This document is almost ready for publication as an 
Informational RFC

Major issues:
     The use of the term "switch" seems confusing.  I had first assumed 
that it meant an ethernet switch (which might have  abit of L3 smarts, 
or might not.  I was trying not to be picky.)  But then, in section 6.3 
it refers to "core switches ... are the data center gateways to external 
networks" which means that those are routers.

Moderate Issue:
    The document seems to be interestingly selective in what modern 
technologies it chooses to mention.  Mostly it seems to be describing 
problems with data center networks using technology more than 5 years 
old.  Since that is the widely deployed practice, that is defensible. 
But then the document chooses to mention new work such as OpenFlow, 
without mentioning the work IEEE has done on broadcast ad multicast 
containment for data centers.  It seems to me that we need to be 
consistent, either describing only the widely deployed technology, or 
including a fair mention of already defined and productized solutions 
that are not yet widely deployed.

     On a related note, the document assumes that multicast NDs are 
delivered to all nodes, while in practice I believe existing techniques 
to filter such multicast messages closer to the source are widely 
deployed.  (Section 5.)

Minor issues:
     I presume that section 6.4.2 which describes needing to enable all 
VLANs on all aggregation ports is a description of current practice, 
since it is not a requirement of current technologies, either via VLAN 
management or orchestration?

     Section 6.4.4 seems very odd.  The title is "overlays".  Are there 
widely deployed overlays?  If so, it would be good to name the 
technologies being referred to here.  If this is intended to refer to 
the overlay proposal in IETF and IEEE, I think that the characterization 
is somewhat misleading, and probably is best simply removed.

     Is the fifth paragraph of section 71. on ARP processing and 
buffering in the absence of ARP cache entries accurate?  I may well be 
out of date, but it used to be the case that most routers dropped the 
packets, and some would buffer 1 packet deep at most.  This description 
indicates a rather more elaborate behavior.

     Given that this document says it is a general document about 
scaling issues for data centers, I am surprised that the security 
considerations section does not touch on the increased complexity of 
segregating subscriber traffic (customer A can not talk to customer B) 
when there are very large numbers of customers, and the itneraction of 
this with L2 scope.

Nits/editorial comments:

From alexey.melnikov@isode.com  Fri Aug 10 01:55:37 2012
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 8DA4F21F841B; Fri, 10 Aug 2012 01:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.375
X-Spam-Level: 
X-Spam-Status: No, score=-102.375 tagged_above=-999 required=5 tests=[AWL=-0.845, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, 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 ROKsW45Fovmy; Fri, 10 Aug 2012 01:55:37 -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 D4A7821F852C; Fri, 10 Aug 2012 01:55:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1344588934; d=isode.com; s=selector; i=@isode.com; bh=00/1+9E+AM7GqxYBAXVF+YQh/LQlEXBj8s3wxQ/OuJ8=; 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=ncGxuHp0wlue+qJqcRblnzyg4u4o351jL53HTSWq/NtO8sShNNfZnWRsqPQ2bQ1McIQWEA 9APIDlfHgo0XzhOs14XgV9ih2FtGFZDayBHPJZN9suNB8H3W7CBwqepyG03zutOipZpDgy Z4NyOgT5p1jF5tGZHBKnVxHiXIw0dwI=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <UCTMfgBvaBmt@waldorf.isode.com>; Fri, 10 Aug 2012 09:55:33 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <502441B7.8020001@isode.com>
Date: Fri, 10 Aug 2012 00:03:19 +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: Ben Campbell <ben@nostrum.com>, =JeffH <Jeff.Hodges@kingsmountain.com>
References: <50161BD5.7040901@KingsMountain.com> <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
In-Reply-To: <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org, IETF Discussion List <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-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, 10 Aug 2012 08:55:37 -0000

On 02/08/2012 10:46, Ben Campbell wrote:
> Hi, thanks for the response.  Comments inline:
>
> On Jul 29, 2012, at 10:29 PM, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
  [...]
>>> -- section 7.2:
>>>
>>> Am I correct to assume that the server must never just serve the content over
>>> a non-secure connection? If so, it would be helpful to mention that, maybe
>>> even normatively.
>> It's a SHOULD, see the Note in that section, so it's already effectively stated normatively, though one needs to understand HTTP workings to realize it in the way you stated it above.  Perhaps could add a simple statement as you suggest to the intro para for section 7 Server Processing Model, to address this concern?
>>
> I think something of the form SHOULD redirect to HTTPS, but MUST NOT under any circumstances send the content unprotected would improve the text.

Sounds good to me. (And yes, this is implied, but it doesn't hurt to 
state explicitly.)

> That's probably already implied, and a reasonable implementor wouldn't due it anyway. But my experience is that some readers will find strange interpretations whenever you give them the wiggle room to do so, so it's better to be explicit.



From tobias.gondrom@gondrom.org  Fri Aug 10 03:03:18 2012
Return-Path: <tobias.gondrom@gondrom.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 A34DD21F864A for <gen-art@ietfa.amsl.com>; Fri, 10 Aug 2012 03:03:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.434
X-Spam-Level: 
X-Spam-Status: No, score=-97.434 tagged_above=-999 required=5 tests=[AWL=-2.073, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RDNS_DYNAMIC=0.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 uQeghE-Dx287 for <gen-art@ietfa.amsl.com>; Fri, 10 Aug 2012 03:03:18 -0700 (PDT)
Received: from lvps176-28-13-69.dedicated.hosteurope.de (lvps176-28-13-69.dedicated.hosteurope.de [176.28.13.69]) by ietfa.amsl.com (Postfix) with ESMTP id A588B21F8628 for <gen-art@ietf.org>; Fri, 10 Aug 2012 03:03:17 -0700 (PDT)
Received: (qmail 20391 invoked from network); 10 Aug 2012 12:03:11 +0200
Received: from 94-194-102-93.zone8.bethere.co.uk (HELO ?192.168.1.65?) (94.194.102.93) by lvps176-28-13-69.dedicated.hosteurope.de with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 10 Aug 2012 12:03:11 +0200
Message-ID: <5024DC5E.60404@gondrom.org>
Date: Fri, 10 Aug 2012 11:03:10 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: alexey.melnikov@isode.com
References: <50161BD5.7040901@KingsMountain.com> <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com> <502441B7.8020001@isode.com>
In-Reply-To: <502441B7.8020001@isode.com>
Content-Type: multipart/alternative; boundary="------------080205060203060004010107"
Cc: ben@nostrum.com, ietf@ietf.org, gen-art@ietf.org, websec@ietf.org, Jeff.Hodges@kingsmountain.com, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-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, 10 Aug 2012 10:03:18 -0000

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

On 10/08/12 00:03, Alexey Melnikov wrote:
> On 02/08/2012 10:46, Ben Campbell wrote:
>> Hi, thanks for the response.  Comments inline:
>>
>> On Jul 29, 2012, at 10:29 PM, =JeffH <Jeff.Hodges@kingsmountain.com> 
>> wrote:
>  [...]
>>>> -- section 7.2:
>>>>
>>>> Am I correct to assume that the server must never just serve the 
>>>> content over
>>>> a non-secure connection? If so, it would be helpful to mention 
>>>> that, maybe
>>>> even normatively.
>>> It's a SHOULD, see the Note in that section, so it's already 
>>> effectively stated normatively, though one needs to understand HTTP 
>>> workings to realize it in the way you stated it above. Perhaps could 
>>> add a simple statement as you suggest to the intro para for section 
>>> 7 Server Processing Model, to address this concern?
>>>
>> I think something of the form SHOULD redirect to HTTPS, but MUST NOT 
>> under any circumstances send the content unprotected would improve 
>> the text.
>
> Sounds good to me. (And yes, this is implied, but it doesn't hurt to 
> state explicitly.)
>
>> That's probably already implied, and a reasonable implementor 
>> wouldn't due it anyway. But my experience is that some readers will 
>> find strange interpretations whenever you give them the wiggle room 
>> to do so, so it's better to be explicit.
>
>
<hat="individual">
Agree with Alexey and Ben. Tobias



--------------080205060203060004010107
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">On 10/08/12 00:03, Alexey Melnikov
      wrote:<br>
    </div>
    <blockquote cite="mid:502441B7.8020001@isode.com" type="cite">On
      02/08/2012 10:46, Ben Campbell wrote:
      <br>
      <blockquote type="cite">Hi, thanks for the response.&nbsp; Comments
        inline:
        <br>
        <br>
        On Jul 29, 2012, at 10:29 PM, =JeffH
        <a class="moz-txt-link-rfc2396E" href="mailto:Jeff.Hodges@kingsmountain.com">&lt;Jeff.Hodges@kingsmountain.com&gt;</a> wrote:
        <br>
      </blockquote>
      &nbsp;[...]
      <br>
      <blockquote type="cite">
        <blockquote type="cite">
          <blockquote type="cite">-- section 7.2:
            <br>
            <br>
            Am I correct to assume that the server must never just serve
            the content over
            <br>
            a non-secure connection? If so, it would be helpful to
            mention that, maybe
            <br>
            even normatively.
            <br>
          </blockquote>
          It's a SHOULD, see the Note in that section, so it's already
          effectively stated normatively, though one needs to understand
          HTTP workings to realize it in the way you stated it above.&nbsp;
          Perhaps could add a simple statement as you suggest to the
          intro para for section 7 Server Processing Model, to address
          this concern?
          <br>
          <br>
        </blockquote>
        I think something of the form SHOULD redirect to HTTPS, but MUST
        NOT under any circumstances send the content unprotected would
        improve the text.
        <br>
      </blockquote>
      <br>
      Sounds good to me. (And yes, this is implied, but it doesn't hurt
      to state explicitly.)
      <br>
      <br>
      <blockquote type="cite">That's probably already implied, and a
        reasonable implementor wouldn't due it anyway. But my experience
        is that some readers will find strange interpretations whenever
        you give them the wiggle room to do so, so it's better to be
        explicit.
        <br>
      </blockquote>
      <br>
      <br>
    </blockquote>
    &lt;hat="individual"&gt;
    <br>
    <font face="Arial">Agree with Alexey and Ben. Tobias<br>
      <br>
    </font><br>
  </body>
</html>

--------------080205060203060004010107--

From brian.e.carpenter@gmail.com  Fri Aug 10 05:27:54 2012
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 63C2121F858E for <gen-art@ietfa.amsl.com>; Fri, 10 Aug 2012 05:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.479
X-Spam-Level: 
X-Spam-Status: No, score=-101.479 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 p1r4RCAIqRiD for <gen-art@ietfa.amsl.com>; Fri, 10 Aug 2012 05:27:53 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8997121F8582 for <gen-art@ietf.org>; Fri, 10 Aug 2012 05:27:53 -0700 (PDT)
Received: by eaai11 with SMTP id i11so409743eaa.31 for <gen-art@ietf.org>; Fri, 10 Aug 2012 05:27:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=yQT+AK0jju0JEt3dHUWG+34Hr53wX2ffjcoPwlQ+tc0=; b=cxRx87hSm9mFKWkowlc3pGmhzDTFDm1oYZ1u4NrIjNGkRcbOVkQvgs/asA0yW73A4I rqZwctlneHq/fL8GmJK5o6z38/Clr+3FHekjwjyq+x90tcGyqOmns0PRYS4BNRsoqeJj 9FhFSTfKk9PG+ZKYj4m079GQARqXczfUGF3VitljQ1tb41S6zyHt/e1zq/PbPVZ7T6Ts os4pIj21X7tiwLMtHU/3PUuhQT4XquMCmPG7T2U1iPRLJlz0Nu3MbMI/0U1lyOpOGBhR zWwLMfwIe6Bbo2ngpH7vZyaAqYoZCFO4RI8uRv4IIVlA4pnEH6/ufewCo9flkYH6lac9 odlw==
Received: by 10.14.216.198 with SMTP id g46mr2946556eep.32.1344601672754; Fri, 10 Aug 2012 05:27:52 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-218-58.as13285.net. [2.102.218.58]) by mx.google.com with ESMTPS id k41sm11103105eep.13.2012.08.10.05.27.51 (version=SSLv3 cipher=OTHER); Fri, 10 Aug 2012 05:27:51 -0700 (PDT)
Message-ID: <5024FE51.6090904@gmail.com>
Date: Fri, 10 Aug 2012 13:28:01 +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-yegin-pana-encr-avp.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------070408010409050408040501"
Subject: [Gen-art] Gen-ART telechat review of draft-yegin-pana-encr-avp-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: Fri, 10 Aug 2012 12:27:54 -0000

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

Please see attached review.




--------------070408010409050408040501
Content-Type: text/plain;
 name="draft-yegin-pana-encr-avp-06-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-yegin-pana-encr-avp-06-carpenter.txt"

SSBoYXZlIGJlZW4gc2VsZWN0ZWQgYXMgdGhlIEdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbSAo
R2VuLUFSVCkNCnJldmlld2VyIGZvciB0aGlzIGRyYWZ0IChmb3IgYmFja2dyb3VuZCBvbiBH
ZW4tQVJULCBwbGVhc2Ugc2VlDQpodHRwOi8vd3d3LmFsdmVzdHJhbmQubm8vaWV0Zi9nZW4v
YXJ0L2dlbi1hcnQtRkFRLmh0bWwpLg0KDQpQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZy
b20geW91ciBkb2N1bWVudCBzaGVwaGVyZA0Kb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcg
dmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoNCkRvY3VtZW50OiBkcmFmdC15ZWdpbi1wYW5hLWVu
Y3ItYXZwLTA2LnR4dA0KUmV2aWV3ZXI6IEJyaWFuIENhcnBlbnRlcg0KUmV2aWV3IERhdGU6
IDIwMTItMDgtMTANCklFVEYgTEMgRW5kIERhdGU6IDIwMTItMDgtMDgNCklFU0cgVGVsZWNo
YXQgZGF0ZTogMjAxMi0wOC0xNg0KDQpTdW1tYXJ5OiAgUmVhZHkNCi0tLS0tLS0tDQoNCk15
IExhc3QgQ2FsbCBjb21tZW50cyB3ZXJlIHRha2VuIGNhcmUgb2YsIHRoYW5rcy4=
--------------070408010409050408040501--

From ben@estacado.net  Fri Aug 10 07:19:17 2012
Return-Path: <ben@estacado.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 622DB21F8604; Fri, 10 Aug 2012 07:19:17 -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 IqPgMkHDslNP; Fri, 10 Aug 2012 07:19:16 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9771121F85C3; Fri, 10 Aug 2012 07:19:16 -0700 (PDT)
Received: from [10.0.1.30] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q7AEGWUQ049872 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Aug 2012 09:16:38 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <502441B7.8020001@isode.com>
Date: Fri, 10 Aug 2012 09:16:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C11651CD-3713-4F2E-9026-E4D7AFF44B31@estacado.net>
References: <50161BD5.7040901@KingsMountain.com> <344AB802-6D45-4399-A628-6852A4732C16@nostrum.com> <502441B7.8020001@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1485)
Cc: Ben Campbell <ben@nostrum.com>, IETF Discussion List <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, =JeffH <Jeff.Hodges@kingsmountain.com>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-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, 10 Aug 2012 14:19:17 -0000

Jeff and I had a f2f discussion about this point in Vancouver. To =
paraphrase (and I assume he will correct me if if I mischaracterize =
anything), Jeff indicated that this really wasn't a MUST level =
requirement due to the variation and vagaries in application behavior =
and abilities. Rather, it's more of a "do the best you can" sort of =
thing. Specifically, he indicated that an implementation that chose to =
go ahead and serve unprotected content due to the listed caveats on =
redirecting to HTTPS would necessarily be out-of-compliance.

If the requirement really that you SHOULD NOT (rather than MUST NOT) =
serve unprotected content, then I think the original language is okay.

Thanks!

Ben.

On Aug 9, 2012, at 6:03 PM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:

> On 02/08/2012 10:46, Ben Campbell wrote:
>> Hi, thanks for the response.  Comments inline:
>>=20
>> On Jul 29, 2012, at 10:29 PM, =3DJeffH =
<Jeff.Hodges@kingsmountain.com> wrote:
> [...]
>>>> -- section 7.2:
>>>>=20
>>>> Am I correct to assume that the server must never just serve the =
content over
>>>> a non-secure connection? If so, it would be helpful to mention =
that, maybe
>>>> even normatively.
>>> It's a SHOULD, see the Note in that section, so it's already =
effectively stated normatively, though one needs to understand HTTP =
workings to realize it in the way you stated it above.  Perhaps could =
add a simple statement as you suggest to the intro para for section 7 =
Server Processing Model, to address this concern?
>>>=20
>> I think something of the form SHOULD redirect to HTTPS, but MUST NOT =
under any circumstances send the content unprotected would improve the =
text.
>=20
> Sounds good to me. (And yes, this is implied, but it doesn't hurt to =
state explicitly.)
>=20
>> That's probably already implied, and a reasonable implementor =
wouldn't due it anyway. But my experience is that some readers will find =
strange interpretations whenever you give them the wiggle room to do so, =
so it's better to be explicit.
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From mahoney@nostrum.com  Fri Aug 10 08:46:00 2012
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 0CBF421F8766 for <gen-art@ietfa.amsl.com>; Fri, 10 Aug 2012 08:46:00 -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 QCxV0TxA+Lzu for <gen-art@ietfa.amsl.com>; Fri, 10 Aug 2012 08:45:59 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 73AC821F8764 for <gen-art@ietf.org>; Fri, 10 Aug 2012 08:45:58 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-102-202.dllstx.fios.verizon.net [173.57.102.202]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7AFjwZD014989 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Fri, 10 Aug 2012 10:45:58 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <50252CB6.5070908@nostrum.com>
Date: Fri, 10 Aug 2012 10:45:58 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: gen-art@ietf.org
References: <50243C05.3080006@nostrum.com>
In-Reply-To: <50243C05.3080006@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.57.102.202 is authenticated by a trusted mechanism)
Subject: Re: [Gen-art] A *new* batch of IETF LC reviews - 2012-08-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: Fri, 10 Aug 2012 15:46:00 -0000

Update to the assignments:

Meral Shirazipour will be taking on draft-ietf-mmusic-media-loopback-22.

Thanks,

Jean

On 8/9/12 5:39 PM, A. Jean Mahoney wrote:
> Hi all,
>
> The following reviewers have assignments:
>
> Reviewer            LC end        Draft
>
> Christer Holmberg   2012-09-03 draft-kumaki-murai-l3vpn-rsvp-te-06
>
> David Black         2012-08-20 draft-ietf-pwe3-mpls-eth-oam-iwk-06
>
> Elwyn Davies        2012-08-22    draft-ietf-idr-as0-05
>
> Joel Halpern        2012-08-23 draft-ietf-armd-problem-statement-03
>
> Kathleen Moriarty   2012-08-23 draft-ietf-mmusic-media-loopback-22
>
>
> 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:
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From ben@nostrum.com  Fri Aug 10 12:31:17 2012
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 2264121F8666; Fri, 10 Aug 2012 12:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.45
X-Spam-Level: 
X-Spam-Status: No, score=-101.45 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.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 boZ-YnG8a-Mp; Fri, 10 Aug 2012 12:31:16 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id D346C21F865E; Fri, 10 Aug 2012 12:31:15 -0700 (PDT)
Received: from [10.12.11.64] ([4.30.77.1]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7AJVD13036521 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Aug 2012 14:31:15 -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, 10 Aug 2012 14:31:11 -0500
Message-Id: <CCBAA297-B839-4AEA-BB24-F4D320200415@nostrum.com>
To: draft-ietf-mptcp-api.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
X-Mailer: Apple Mail (2.1485)
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: General Area Review Team <gen-art@ietf.org>, IETF Discussion List <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-mptcp-api-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, 10 Aug 2012 19:31: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 resolve these comments along with any other Last Call comments
you may receive.

Document:  draft-ietf-mptcp-api-05

Reviewer: Ben Campbell
Review Date: 2012-08-10
IETF LC End Date: 2012-08-14

Summary: This draft is almost ready for publication, but I have =
questions about its intended informational status.

Major issues: None

Minor issues:

-- Section 5 specifies an abstract "basic" API for MPTCP. The draft =
characterizes this as an extension to the sockets API. On it's face, =
this sounds like it's creating a standard, or will at least have the =
effect of creating a standard. Is that the intent? If so, I wonder why =
the intended status is informational rather than standards track? If =
not, it would be useful to explicitly state the intent. (For example, is =
this intended as an input to inform a standardization effort?)

I realize that the sockets API is not an IETF standard. I don't know if =
that is part of the reason for making this draft informational, nor am I =
familiar with precedent for extending non-IETF-native standards. But at =
the risk of attacking a straw man, I am concerned that putting something =
that could be interpreted as a "standard" in an informational RFC might =
not be the best practice for solving that sort of process issue.


-- It seems like at least passing knowledge of the sockets API is needed =
to understand this document. I'm curious why the POSIX reference is =
informational rather than normative?

Nits/editorial comments:

-- 3.3.1, 1st paragraph: "This will provide greater bandwidth for an =
application. "

I assume this means "as great or greater", given the previous statements =
that MPTCP should be at worst no worse than normal TCP?

-- 3.2.1, 1st paragraph: "...while having TCP SYN/ACK ready to reply =
to..."

I had to think about this a while to figure out the meaning. Perhaps it =
could be rephrased?=

From Jeff.Hodges@KingsMountain.com  Fri Aug 10 14:34:20 2012
Return-Path: <Jeff.Hodges@KingsMountain.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 9EFCF21F8629 for <gen-art@ietfa.amsl.com>; Fri, 10 Aug 2012 14:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.905
X-Spam-Level: 
X-Spam-Status: No, score=-100.905 tagged_above=-999 required=5 tests=[AWL=1.360, 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 iFkFikd85weX for <gen-art@ietfa.amsl.com>; Fri, 10 Aug 2012 14:34:20 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id F0AB421F8618 for <gen-art@ietf.org>; Fri, 10 Aug 2012 14:34:19 -0700 (PDT)
Received: (qmail 23990 invoked by uid 0); 10 Aug 2012 21:33:58 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy3.bluehost.com with SMTP; 10 Aug 2012 21:33:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=zQ42lv4nJ35pqAeoI1DBK7QuzkWuO0maehLqEdWcNw4=;  b=nP7T9HTdfxO9PV1OTuC7BwjLaByYiMHmmqcpWPoSCFT+jwlIiE5BqcKI9hkfVMcVRuPJ3wEKYorwfWULZSHCIfKDfdtB7Ypex/bymket+MziQjEpFNwgTfP/43MTahNx;
Received: from [24.4.122.173] (port=41385 helo=[192.168.11.12]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1SzwqC-0001Ci-He; Fri, 10 Aug 2012 15:33:56 -0600
Message-ID: <50257E43.8010005@KingsMountain.com>
Date: Fri, 10 Aug 2012 14:33:55 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>,  Tobias Gondrom <tobias.gondrom@gondrom.org>, Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org, =JeffH <Jeff.Hodges@KingsMountain.com>, IETF Discussion List <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-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, 10 Aug 2012 21:34:20 -0000

Thanks Ben.

 > Jeff and I had a f2f discussion about this point in Vancouver. To paraphrase
 > (and I assume he will correct me if if I mischaracterize anything), Jeff
 > indicated that this really wasn't a MUST level requirement due to the
 > variation and vagaries in application behavior and abilities.

Yes, see the NOTE in section 7.2.

 > Rather, it's
 > more of a "do the best you can" sort of thing. Specifically, he indicated
 > that an implementation that chose to go ahead and serve unprotected content
 > due to the listed caveats on redirecting to HTTPS would necessarily be
 > out-of-compliance.

I presume you actually mean "not necessarily", which would then be correct, 
unless I'm misunderstanding something.


 > If the requirement really that you SHOULD NOT (rather than MUST NOT) serve
 > unprotected content, then I think the original language is okay.

agreed.

thanks,

=JeffH



From ben@estacado.net  Fri Aug 10 14:58:38 2012
Return-Path: <ben@estacado.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 1E60221F865E; Fri, 10 Aug 2012 14:58:38 -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 v1bz59dq3Dy9; Fri, 10 Aug 2012 14:58:37 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id 69D6221F865C; Fri, 10 Aug 2012 14:58:36 -0700 (PDT)
Received: from [10.12.11.64] ([10.12.11.64]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q7ALttiU010516 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 10 Aug 2012 16:55:55 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <50257E43.8010005@KingsMountain.com>
Date: Fri, 10 Aug 2012 16:55:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <570BD336-2C91-4C7E-AC03-9FD5423AEB35@estacado.net>
References: <50257E43.8010005@KingsMountain.com>
To: =JeffH <Jeff.Hodges@kingsmountain.com>
X-Mailer: Apple Mail (2.1485)
Cc: Ben Campbell <ben@nostrum.com>, IETF Discussion List <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, Tobias Gondrom <tobias.gondrom@gondrom.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-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, 10 Aug 2012 21:58:38 -0000

On Aug 10, 2012, at 4:33 PM, =3DJeffH <Jeff.Hodges@kingsmountain.com> =
wrote:

> Thanks Ben.
>=20
> > Jeff and I had a f2f discussion about this point in Vancouver. To =
paraphrase
> > (and I assume he will correct me if if I mischaracterize anything), =
Jeff
> > indicated that this really wasn't a MUST level requirement due to =
the
> > variation and vagaries in application behavior and abilities.
>=20
> Yes, see the NOTE in section 7.2.
>=20
> > Rather, it's
> > more of a "do the best you can" sort of thing. Specifically, he =
indicated
> > that an implementation that chose to go ahead and serve unprotected =
content
> > due to the listed caveats on redirecting to HTTPS would necessarily =
be
> > out-of-compliance.
>=20
> I presume you actually mean "not necessarily", which would then be =
correct, unless I'm misunderstanding something.

Oops, you are correct, that's a typo.

>=20
>=20
> > If the requirement really that you SHOULD NOT (rather than MUST NOT) =
serve
> > unprotected content, then I think the original language is okay.
>=20
> agreed.
>=20
> thanks,
>=20
> =3DJeffH
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From Jeff.Hodges@KingsMountain.com  Fri Aug 10 21:41:20 2012
Return-Path: <Jeff.Hodges@KingsMountain.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 13DE621F851B for <gen-art@ietfa.amsl.com>; Fri, 10 Aug 2012 21:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.377
X-Spam-Level: 
X-Spam-Status: No, score=-101.377 tagged_above=-999 required=5 tests=[AWL=0.888, 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 Q03GtHMoXBik for <gen-art@ietfa.amsl.com>; Fri, 10 Aug 2012 21:41:19 -0700 (PDT)
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id 8E9AC21F8517 for <gen-art@ietf.org>; Fri, 10 Aug 2012 21:41:19 -0700 (PDT)
Received: (qmail 1457 invoked by uid 0); 11 Aug 2012 04:40:53 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy7.bluehost.com with SMTP; 11 Aug 2012 04:40:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=pAUvay1+OwfsdgXlsoXr/7NnBbFxf3AmRbW1zQy4gVY=;  b=2JCYYopKE5hWt5Dw40q4+QK9rfVYp5cy9gFeYYUfHvOmPlvmXnpiNztH2QgqqV4BHksahsz5o4n29WYkPHuzReCP/hzaT4KTHDRICE4juqTotMrD9ZmyokkLG14pjE4X;
Received: from [24.4.122.173] (port=43149 helo=[192.168.11.12]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1T03VN-0007RE-Lo; Fri, 10 Aug 2012 22:40:53 -0600
Message-ID: <5025E253.7070907@KingsMountain.com>
Date: Fri, 10 Aug 2012 21:40:51 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org, IETF Discussion List <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-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: Sat, 11 Aug 2012 04:41:20 -0000

Hi,

I believe I've made requite changes to draft-ietf-websec-strict-transport-sec
per this thread as well as the WG f2f discussion @IETF-84 Vancouver and also my
f2f discussion with Ben after the websec wg meeting.

In the below I'm just going to try to identify the individual issues from Ben's
review without quoting all the thread discussion, but also highlight the changes
I have queued in my -12 working copy of draft-ietf-websec-strict-transport-sec.

If the below looks nominally OK I can submit my -12 working copy, please let me 
know (Alexey/Barry). (note: I'm going to be mostly offline for the next several 
days)

thanks,

=JeffH
------

Ben's "minor items":

M1) update 2818 ?

 >> -- Does this draft update any other RFCs (e.g. 2616 or 2818)?

Maybe 2818, but based on the informational status of 2818, websec wg 
discussions, and discussions with Ben and EKR, there's no statement of updating 
2818 in my -12 working copy.


M2) non-conformant UAs ?

 >>> -- I did not find any guidance on how to handle UAs that do not
 >>> understand this extension. I don't know if this needs to be normative,
 >>> but the draft should at least mention the possibility and implications.
 >>
 >> Agreed. My -12 working copy now contains these new subsections..
 >>
 >> <snip/>
 >>
 > That's all good text, but I'm not sure it actually captures my concern.
 >
 > <snip/> That is, the server can't merely select the extension and forget
 > about things--it still needs to to take the same care to avoid leaking
 > resources over unprotected connections that it would need to do if this
 > extension did not exist in the first place.
 >
 > I think this is implied by your last sentence above, but it would be better
 > to say it explicitly.

I've added text to my -12 working copy, it now states...

###
14.1.  Non-Conformant User Agent Implications

    Non-conformant user agents ignore the Strict-Transport-Security
    header field, thus non-conformant user agents do not address the
    threats described in Section 2.3.1 "Threats Addressed".

    This means that the web application and its users wielding non-
    conformant UAs will be vulnerable to both:

    o  Passive network attacks due to web site development and deployment
       bugs:

          For example, if the web application contains any insecure,
          non-"https", references to the web application server, and if
          not all of its cookies are flagged as "Secure", then its
          cookies will be vulnerable to passive network sniffing, and
          potentially subsequent misuse of user credentials.

    o  Active network attacks:

          For example, if an attacker is able to place a man-in-the-
          middle, secure transport connection attempts will likely yield
          warnings to the user, but without HSTS Policy being enforced,
          the present common practice is to allow the user to "click-
          through" and proceed.  This renders the user and possibly the
          web application open to abuse by such an attacker.

    This is essentially the status-quo for all web applications and their
    users in the absence of HSTS Policy.  Since web application providers
    typically do not control the type or version of UAs their web
    applications interact with, the implication is that HSTS Host
    deployers must generally exercise the same level of care to avoid web
    site development and deployment bugs (see Section 2.3.1.3) as they
    would if they were not asserting HSTS Policy.
###


M3) the superdomain match wins (?) question  (section 8.x generally)

 >>> -- How should a UA handle potential conflicts between a the policy
 >>> record that includes the includeSubdomain, and any records for subdomains
 >>> that might have different parameters?
 >>
 >> this is in the draft. the short answer is that at policy enforcement time,
 >> "superdomain matches win".
 >>
 >> At "noting an HSTS Host" time, the HSTS host's policy (if expressed) is
 >> noted regardless of whether there are superdomain HSTS hosts asserting
 >> "includeSubDomains".
 >>
 >> perhaps this needs to be made more clear?
 >
 > Maybe I'm missing something, but I'm not getting that answer from the text.

In our f2f discussion, Ben and I agreed that we need to clear that we stop on 
first match when doing policy enforcement -- but it turns out to be not quite 
that simple, due to the includeSubDomains semantics. Here's the relvant text now 
in my -12 working copy, the alterations are in step 5...

###
8.3.  URI Loading and Port Mapping

    Whenever the UA prepares to "load", also known as "dereference", any
    "http" URI [RFC3986] (including when following HTTP redirects
    [RFC2616]), the UA MUST first determine whether a domain name is
    given in the URI and whether it matches a Known HSTS Host, using
    these steps:
                         .
                         .
    4.  Otherwise, the substring is a given domain name, which MUST be
        matched against the UA's Known HSTS Hosts using the procedure in
        Section 8.2 "Known HSTS Host Domain Name Matching".

    5.  If when performing doman name matching, any superdomain match
        with an asserted includeSubDomains flag is found, or, if no
        superdomain matches with asserted includeSubDomains flags are
        found and a congruent match is found (with or without an asserted
        includeSubDomains flag), then before proceeding with the load:
                         .
                         .
###


M4) section 6.1: handling header field extensibility

[ see separate message entitled "handling STS header field extendability" ]
section 7.2 must not serve insecure content?



M5) section 7.2: state explicitly must not serve insecure content?

no changes necessary, see relevant discussion in this thread.



M6) section 8.4:formal duty for revocation checking ?

Based on f2f discussions with Ben and EKR, I now have the following text in my 
-12 working copy, and have moved the references to RFC2560 & RFC5280 to 
Informational. The rationale is that revocation checking is not required by the 
TLS and PKIX specs, they just say "here's how you can do it", and there's not 
really an appropriate spec to point at (which would have any chance at all to be 
actually adhered to by UAs due to the rapidly evolving nature of our 
understanding of the efficacy and performance and utility of "classical" 
revocation checking).

###
8.4.  Errors in Secure Transport Establishment

    When connecting to a Known HSTS Host, the UA MUST terminate the
    connection (see also Section 12 "User Agent Implementation Advice")
    if there are any errors, whether "warning" or "fatal" or any other
    error level, with the underlying secure transport.  For example, this
    includes any errors found in certificate validity checking UAs employ
    such as via Certificate Revocation Lists (CRL) [RFC5280], or via the
    Online Certificate Status Protocol (OCSP) [RFC2560].
###





Ben's editorial items:


E1) Unused Reference: 'RFC6376'                       -- done in -12

E2) fixup indented "Note:" such that one(s) that are normative as a regular 
paragraph(s) and leave the others as-is              -- done in -12

E3) reference to SSLv3, ref 6101 informatively       -- done in -12

E4) section 8.3 congruent match -- text is fine, no changes necessary

E5) move section 12 up ahead of the non-normative guidance sections
                                                      -- done in -12

E6) proxy sec cons apply to CONNECT proxy ?            -- done in -12
( noted that the type of proxy of concern is a "MITM non-transparent proxy",
   which ought to clarify that it's not a transparent HTTP CONNECT-based
   proxy. (I couldn't find any dominating terminology describing these
   beasts, it is all over the map, but maybe I'm missing something) )


---
end












From Francis.Dupont@fdupont.fr  Mon Aug 13 02:17:51 2012
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 49DEC21F8701 for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 02:17: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 JulNPT5w6z7W for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 02:17:50 -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 89CCE21F8578 for <gen-art@ietf.org>; Mon, 13 Aug 2012 02:17:50 -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 q7D9Hmxx004131; Mon, 13 Aug 2012 11:17:48 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201208130917.q7D9Hmxx004131@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 13 Aug 2012 11:17:48 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-sparks-genarea-mailarch.all@tools.ietf.org
Subject: [Gen-art] review of draft-sparks-genarea-mailarch-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, 13 Aug 2012 09:17:51 -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-sparks-genarea-mailarch-05.txt
Reviewer: Francis Dupont
Review Date: 20120810
IETF LC End Date: 20120813
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues:
 - a very minor question: why in the search syntax is there no "NOT" operator,
  only "AND" and "OR"?
 - annoying edition bug in 2.6

Nits/editorial comments:
 - ToC page 2 and 6 page 7: Acknowledgements -> Acknowledgments

 - 1 page 3 and 2.1 page 4: capabilites -> capabilities

 - 2.1 page 4: occuring -> occurring

 - 2.6 page 7: please remove the last item, i.e.:

   o  The system must allow the administrator to delete messages from an
      archived list

  which is already specified by the previous one, i.e.:

   o  The system must allow the administrator to add messages to and
      delete messages from an archived list.  The system should log such
      actions.

Regards

Francis.Dupont@fdupont.fr

From alexey.melnikov@isode.com  Mon Aug 13 03:32:28 2012
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 809FD21F86F8 for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 03:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.89
X-Spam-Level: 
X-Spam-Status: No, score=-102.89 tagged_above=-999 required=5 tests=[AWL=-0.291, 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 y1CKmoo2oc02 for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 03:32:27 -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 B942021F86EE for <gen-art@ietf.org>; Mon, 13 Aug 2012 03:32:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1344853946; d=isode.com; s=selector; i=@isode.com; bh=9SKzO7KJEYj3WxhINUMiOkdcIyZ3vu3QjvRW+mflaRw=; 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=JzLzIJPZz8TxtbdCZklKTV1VQQediQgH6LlxEbm2R6vPEySANw/szlcid523p/5UvIRAfZ tc298+k/QgtbWORRxrw2h09hPeMs0K9kJNXzU0DhBTOFvaVxstGueoZ/kKs5ZpFTXfvlC3 5sdJvx+MiYi/AbQaIzkMMRhFl88IAZI=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <UCjXuQBvaK2X@waldorf.isode.com>; Mon, 13 Aug 2012 11:32:26 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <5028D7F1.1080405@isode.com>
Date: Mon, 13 Aug 2012 11:33:21 +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
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-ccamp-dpm.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-ccamp-dpm-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: Mon, 13 Aug 2012 10:32: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 Last Call comments
you may receive.

Document: draft-ietf-ccamp-dpm-06.txt
Reviewer: Alexey Melnikov
Review Date: 13 August 2012
IETF LC End Date: 15 August 2012
IESG Telechat date: 30 August 2012

Summary: Ready

Major issues: None

Minor issues: None

Nits: None

From vkg@bell-labs.com  Mon Aug 13 07:08:20 2012
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 3055921F8751 for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 07:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.877
X-Spam-Level: 
X-Spam-Status: No, score=-107.877 tagged_above=-999 required=5 tests=[AWL=-1.278, 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 xJ+Ol7WM3Jqw for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 07:08:19 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 7643321F8750 for <gen-art@ietf.org>; Mon, 13 Aug 2012 07:08:19 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id q7DE8DKk011218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 13 Aug 2012 09:08:14 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q7DE8Cqd008021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 13 Aug 2012 09:08:13 -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 q7DE7wwN018431; Mon, 13 Aug 2012 09:08:12 -0500 (CDT)
Message-ID: <50290A45.5020702@bell-labs.com>
Date: Mon, 13 Aug 2012 09:08:05 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: draft-ietf-ospf-hybrid-bcast-and-p2mp@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.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: General Area Review Team <gen-art@ietf.org>, Stewart Bryant <stbryant@cisco.com>, acee.lindem@ericsson.com, akr@cisco.com
Subject: [Gen-art] Gen-ART review of draft-ietf-ospf-hybrid-bcast-and-p2mp-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: Mon, 13 Aug 2012 14:08:20 -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-ospf-hybrid-bcast-and-p2mp-04
Reviewer: Vijay K. Gurbani
Review Date: Aug-13-2012
IETF LC End Date: Unknown
IESG Telechat date: Aug-16-2012


Summary: This draft is ready as a proposed standard.

Major: 0
Minor: 0
Nits: 1

Nits:

1/ S1, second paragraph, 4th line: s/all all/all/


- 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 philip.eardley@bt.com  Mon Aug 13 07:14:09 2012
Return-Path: <philip.eardley@bt.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 4A54F21F8766; Mon, 13 Aug 2012 07:14:09 -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.868, BAYES_00=-2.599, MANGLED_LIST=2.3, 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 0YmuNEPYbjRi; Mon, 13 Aug 2012 07:14:08 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp62.intersmtp.com [62.239.224.235]) by ietfa.amsl.com (Postfix) with ESMTP id 7528F21F8760; Mon, 13 Aug 2012 07:14:08 -0700 (PDT)
Received: from EVMHT64-UKRD.domain1.systemhost.net (10.36.3.101) by RDW083A006ED62.smtp-e2.hygiene.service (10.187.98.11) with Microsoft SMTP Server (TLS) id 8.3.264.0; Mon, 13 Aug 2012 15:14:06 +0100
Received: from EMV65-UKRD.domain1.systemhost.net ([169.254.1.58]) by EVMHT64-UKRD.domain1.systemhost.net ([10.36.3.101]) with mapi; Mon, 13 Aug 2012 15:14:06 +0100
From: <philip.eardley@bt.com>
To: <ben@nostrum.com>, <draft-ietf-mptcp-api.all@tools.ietf.org>
Date: Mon, 13 Aug 2012 15:14:06 +0100
Thread-Topic: Gen-ART LC Review of draft-ietf-mptcp-api-05
Thread-Index: Ac13LsLUMm/ZireBRPufxalExn9KDgCD0gwA
Message-ID: <9510D26531EF184D9017DF24659BB87F33D6B96847@EMV65-UKRD.domain1.systemhost.net>
References: <CCBAA297-B839-4AEA-BB24-F4D320200415@nostrum.com>
In-Reply-To: <CCBAA297-B839-4AEA-BB24-F4D320200415@nostrum.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-mptcp-api-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, 13 Aug 2012 14:14:09 -0000

Ben,
Thanks for your review.=20

The right status isn't clear-cut (I think), but when we (Chairs & Wes) disc=
ussed it, Info seemed best
* mainly because precedent seems to be that API docs are informational, for=
 example socket API extensions for SCTP http://datatracker.ietf.org/doc/rfc=
6458/ =20
* also the doc has two main parts - looking at the impact that MPTCP may ha=
ve on application performance - and describing a basic API for MPTCP-aware =
applications. The first part seems clearly Informational. So if the API par=
t is not Info, there is the effort of splitting the doc. Pragmatically I th=
ink this should only be done if clearly needed.

I'm afraid I don't know case history of how the IETF tries to extend non-IE=
TF standards.

On the status of Posix reference, which appears twice in the doc
>> The abstract specification is in line with the
   Posix standard [17] as much as possible
>> One commonly used TCP socket option (TCP_NODELAY) disables the Nagle
   algorithm as described in [2].  This option is also specified in the
   Posix standard [17]. =20

The guidance:
>> Normative references specify documents that must be read to understand o=
r implement the technology in the new RFC, or whose technology must be pres=
ent for the technology in the new RFC to work.

On its second appearance, I think [17] is definitely being used informative=
ly.
The first appearance is less clear  cut, I think. Am inclined to say this i=
s still informative - it's just explaining the style adopted for the abstra=
ct specification (if [17] changed then it wouldn't be necessary to change t=
his doc).

Thanks also for the nits

Best wishes
phil



-----Original Message-----
From: Ben Campbell [mailto:ben@nostrum.com]=20
Sent: 10 August 2012 20:31
To: draft-ietf-mptcp-api.all@tools.ietf.org
Cc: General Area Review Team; IETF Discussion List
Subject: Gen-ART LC Review of draft-ietf-mptcp-api-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-mptcp-api-05

Reviewer: Ben Campbell
Review Date: 2012-08-10
IETF LC End Date: 2012-08-14

Summary: This draft is almost ready for publication, but I have questions a=
bout its intended informational status.

Major issues: None

Minor issues:

-- Section 5 specifies an abstract "basic" API for MPTCP. The draft charact=
erizes this as an extension to the sockets API. On it's face, this sounds l=
ike it's creating a standard, or will at least have the effect of creating =
a standard. Is that the intent? If so, I wonder why the intended status is =
informational rather than standards track? If not, it would be useful to ex=
plicitly state the intent. (For example, is this intended as an input to in=
form a standardization effort?)

I realize that the sockets API is not an IETF standard. I don't know if tha=
t is part of the reason for making this draft informational, nor am I famil=
iar with precedent for extending non-IETF-native standards. But at the risk=
 of attacking a straw man, I am concerned that putting something that could=
 be interpreted as a "standard" in an informational RFC might not be the be=
st practice for solving that sort of process issue.


-- It seems like at least passing knowledge of the sockets API is needed to=
 understand this document. I'm curious why the POSIX reference is informati=
onal rather than normative?

Nits/editorial comments:

-- 3.3.1, 1st paragraph: "This will provide greater bandwidth for an applic=
ation. "

I assume this means "as great or greater", given the previous statements th=
at MPTCP should be at worst no worse than normal TCP?

-- 3.2.1, 1st paragraph: "...while having TCP SYN/ACK ready to reply to..."

I had to think about this a while to figure out the meaning. Perhaps it cou=
ld be rephrased?

From vkg@bell-labs.com  Mon Aug 13 08:19:47 2012
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 42D2021F8780 for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 08:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.791
X-Spam-Level: 
X-Spam-Status: No, score=-107.791 tagged_above=-999 required=5 tests=[AWL=-1.192, 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 vRyTYZklT2jg for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 08:19:46 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 72ECE21F8743 for <gen-art@ietf.org>; Mon, 13 Aug 2012 08:19:41 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q7DFJYAR006063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 13 Aug 2012 10:19:35 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q7DFJXa4010675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 13 Aug 2012 10:19:34 -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 q7DFJH6J023111; Mon, 13 Aug 2012 10:19:18 -0500 (CDT)
Message-ID: <50291AFB.6010603@bell-labs.com>
Date: Mon, 13 Aug 2012 10:19:23 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: draft-ietf-opsawg-automated-network-configuration@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.9
Cc: christopher.liljenstolpe@bigswitch.com, General Area Review Team <gen-art@ietf.org>, melinda.shore@gmail.com, "Scott O. Bradner" <sob@harvard.edu>, Ron Bonica <rbonica@juniper.net>
Subject: [Gen-art] Gen-ART review of draft-ietf-opsawg-automated-network-configuration-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: Mon, 13 Aug 2012 15:19:47 -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-opsawg-automated-network-configuration-04
Reviewer: Vijay K. Gurbani
Review Date: Aug-13-2012
IETF LC End Date: Aug-15-2012
IESG Telechat date: Aug-16-2012

This draft is on the right track but has open issues, described in
the review.

Major: 0
Minor: 5
Nits:  4

Minor:
1/ S1, paragraph 2: The use of the phrase "...how to implement things
  properly," is too colloquial for a standards document (even though the
  draft is targeted as an Informational).  I would suggest to rewrite the
  phrase with more information on what these "things" are.

2/ S1, similar comment for issue (b), it is too colloquial.  I would
  suggest rewording to something like the following: "network equipment
  vendors introducing who would like to ensure a smooth delivery of many
  devices with new features"

3/ S1, paragraph 4 --- I suspect that simply expanding eNodeB to
  "Evolved Node B" and referencing the appropriate standard body's
  document describing the role of eNodeB should suffice.

4/ S3, second paragraph: "let us agree" is, again, more colloquial than
  standards-oriented prose.  Maybe a good thing to do would be to define
  "configuration data", "configuration server", "joining device" and
  others in a terminology section (either as a subsection in S3 or as a
  section of its own).  You already have a good collection of such
  terminology definitions at the beginning of S3.

5/ S5.4, page 12, while discussing lack of URNs for SAN to carry a MAC:
  one way to carry a MAC in SAN is to use the otherName field as
  discussed in rfc5280. S4.2.1.6.  I suspect that you have evaluated
  this option but decided against it.  If so, it will be good to list it
  as an indication of the reasons why you do not think this option will
  work.

Nits:
1/ S1, s/nodes, in a Wi-Fi rather/nodes in a Wi-Fi rather/

2/ S3, in "Pre-configuration": I suspect that the "certificate"
  mentioned there pertains to an X.509 certificate.  If so, please
  make it apparent.

3/ S5.1: s/non-IETF protocols only./non-IETF protocols./

4/ S5.4: s/identity built in/identity/

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 vkg@bell-labs.com  Mon Aug 13 08:44:44 2012
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 015AB21F873E for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 08:44:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.717
X-Spam-Level: 
X-Spam-Status: No, score=-107.717 tagged_above=-999 required=5 tests=[AWL=-1.118, 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 SgBaBTkDpJaF for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 08:44:43 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF8521F8737 for <gen-art@ietf.org>; Mon, 13 Aug 2012 08:44:43 -0700 (PDT)
Received: from ihemail2.lucent.com (h135-245-2-35.lucent.com [135.245.2.35]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q7DFia4i001924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Aug 2012 10:44:36 -0500 (CDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q7DFiZR2011458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 13 Aug 2012 10:44:36 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q7DFiZ9j016968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 13 Aug 2012 10:44:35 -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 q7DFiYej022203; Mon, 13 Aug 2012 10:44:35 -0500 (CDT)
Message-ID: <502920E9.1060401@bell-labs.com>
Date: Mon, 13 Aug 2012 10:44:41 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: draft-ietf-ospf-prefix-hiding@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.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: General Area Review Team <gen-art@ietf.org>, akr@cisco.com, acee.lindem@ericsson.com, Stewart Bryant <stbryant@cisco.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-ospf-prefix-hiding-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, 13 Aug 2012 15:44:44 -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-ospf-prefix-hiding-05.
Reviewer: Vijay K. Gurbani
Review Date: Aug-13-2012
IETF LC End Date: July-6-2012
IESG Telechat date: Aug-16-2012

Summary: This draft is ready as a Proposed Standard.

I had reviewed the previous version (-04) and found it ready.

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 ron.even.tlv@gmail.com  Mon Aug 13 13:08:40 2012
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 45DE621F84FD; Mon, 13 Aug 2012 13:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[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 zXcpVYg3Oihw; Mon, 13 Aug 2012 13:08:39 -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 6085221F85ED; Mon, 13 Aug 2012 13:08:38 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so2533964wgb.13 for <multiple recipients>; Mon, 13 Aug 2012 13:08:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=3RJBrl7Qzeo2Mn2R+73CZF6OD5IR6lHkUNtmkjIRI4I=; b=IKh02IfSRQaO/xSRa/hbIPpm6o7g0GiM10HJ6b/W+j67VAEXXj9BKtFUZHWkOCRbQH k/Oqm0UHzM7G7rQwuhL8wTjqwx0bnUMBhOlAVue/YGObMIwWPELKzYcBJe47MlgI2wMC PIHNABdlqRsuCZaP/Gj1b/nPhS7fRc3iuhJNiG9Ikw8YJbCOn1upm1ExBlX/b/cCumtR /8jPSxCQ5E8x7i9lI+6B+Rlfbvlt90QEIyRF4zvMbgvBE9HjY2uI3b1AGr7oVECHlLSN lSe5FCwaSXben2B00HB/JNfTZJMNIgpTC3CZSJznolS6YnXP5p9D66I27tlFJE7OjIyr Op4w==
Received: by 10.180.82.39 with SMTP id f7mr21221132wiy.2.1344888517387; Mon, 13 Aug 2012 13:08:37 -0700 (PDT)
Received: from RoniE (bzq-79-182-232-234.red.bezeqint.net. [79.182.232.234]) by mx.google.com with ESMTPS id k2sm26493072wiz.7.2012.08.13.13.08.34 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 13 Aug 2012 13:08:35 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
Date: Mon, 13 Aug 2012 23:07:24 +0200
Message-ID: <002101cd7997$a5204330$ef60c990$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0022_01CD79A8.68A9FD90"
X-Mailer: Microsoft Outlook 14.0
Thread-index: Ac15l6K82vd14GSLS+SGruU3C7QWJA==
Content-language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-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, 13 Aug 2012 20:08:40 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0022_01CD79A8.68A9FD90
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-ccamp-rfc5787bis-05.

Reviewer: Roni Even

Review Date:2012-8-12

IETF LC End Date: 2012-8-17

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

In section 6.1 " If specified more than once, instances preceding the first
will be ignored and condition SHOULD be logged for possible action by the
network operator."  I am not sure what is meant by preceding the first.

 

 

Nits/editorial comments:

 

1.	The following note appears in section 10.1, 10.2 and 10.3. "Note
that the same values for the Inter-RA Export Upward sub-TLV and the Inter-RA
Export Downward Sub-TLV MUST be used when they appear in the Link TLV, Node
Attribute TLV, and Router Address TLV." - why not have it in section 10
before section 10.1.
2.	I saw in appendix  B that one of the changes from RFC 5787 was to
clarify the terminology before defining extensions, I would have found it
easier to read if the ASON hierarchy and the relation to OSPF in section 2
were presented in figures. This was more an issue to me as a reader not
familiar with the terminology and I would like to think that the more
familiar reader will not have problem.

 


------=_NextPart_000_0022_01CD79A8.68A9FD90
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:715087181;
	mso-list-type:hybrid;
	mso-list-template-ids:-1205706658 -1668626108 67698713 67698715 =
67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-bidi-font-family:Calibri;}
@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>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><o:p>&nbsp;</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"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span>draft-ietf-ccamp-rfc5787bis-05.<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:2012&#8211;8&#8211;12<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: 2012&#8211;8&#8211;17<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 almost ready for publication as</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> a =
standard track </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>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=3DMsoNormal>In section 6.1 &#8220; =
If specified more than once, instances preceding the first will be =
ignored and condition SHOULD be logged for possible action by the =
network operator.&#8221;&nbsp; I am not sure what is meant by preceding =
the first.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></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"'>Nits/editor=
ial comments:<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><ol style=3D'margin-top:0in' start=3D1 type=3D1><li =
class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>The following note =
appears in section 10.1, 10.2 and 10.3. &#8220;Note that the same values =
for the Inter-RA Export Upward sub-TLV and the Inter-RA Export Downward =
Sub-TLV MUST be used when they appear in the Link TLV, Node Attribute =
TLV, and Router Address TLV.&#8221; &#8211; why not have it in section =
10 before section 10.1.<o:p></o:p></li><li class=3DMsoNormal =
style=3D'mso-list:l0 level1 lfo1'>I saw in appendix&nbsp; B that one of =
the changes from RFC 5787 was to clarify the terminology before defining =
extensions, I would have found it easier to read if the ASON hierarchy =
and the relation to OSPF in section 2 were presented in figures. This =
was more an issue to me as a reader not familiar with the terminology =
and I would like to think that the more familiar reader will not have =
problem.<o:p></o:p></li></ol><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> =
<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0022_01CD79A8.68A9FD90--


From ben@estacado.net  Mon Aug 13 13:59:48 2012
Return-Path: <ben@estacado.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 4422721F867C; Mon, 13 Aug 2012 13:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kkgScxprJuPW; Mon, 13 Aug 2012 13:59:47 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id 82C5421F8671; Mon, 13 Aug 2012 13:59:47 -0700 (PDT)
Received: from [10.12.11.64] ([10.12.11.64]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q7DKwOPu081872 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Aug 2012 15:58:26 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <9510D26531EF184D9017DF24659BB87F33D6B96847@EMV65-UKRD.domain1.systemhost.net>
Date: Mon, 13 Aug 2012 15:58:15 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4535EA27-3119-477A-8AE1-C893498D5AC5@estacado.net>
References: <CCBAA297-B839-4AEA-BB24-F4D320200415@nostrum.com> <9510D26531EF184D9017DF24659BB87F33D6B96847@EMV65-UKRD.domain1.systemhost.net>
To: philip.eardley@bt.com
X-Mailer: Apple Mail (2.1485)
Cc: ben@nostrum.com, gen-art@ietf.org, draft-ietf-mptcp-api.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-mptcp-api-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, 13 Aug 2012 20:59:48 -0000

On Aug 13, 2012, at 9:14 AM, philip.eardley@bt.com wrote:

> Ben,
> Thanks for your review.=20
>=20
> The right status isn't clear-cut (I think), but when we (Chairs & Wes) =
discussed it, Info seemed best
> * mainly because precedent seems to be that API docs are =
informational, for example socket API extensions for SCTP =
http://datatracker.ietf.org/doc/rfc6458/=20

I'm willing to accept that there is precedent for doing this in an =
informational. (I wonder about the rational used previously, but that's =
probably neither here nor there.)

> * also the doc has two main parts - looking at the impact that MPTCP =
may have on application performance - and describing a basic API for =
MPTCP-aware applications. The first part seems clearly Informational. So =
if the API part is not Info, there is the effort of splitting the doc. =
Pragmatically I think this should only be done if clearly needed.

Agreed.

>=20
> I'm afraid I don't know case history of how the IETF tries to extend =
non-IETF standards.
>=20
> On the status of Posix reference, which appears twice in the doc
>>> The abstract specification is in line with the
>   Posix standard [17] as much as possible
>>> One commonly used TCP socket option (TCP_NODELAY) disables the Nagle
>   algorithm as described in [2].  This option is also specified in the
>   Posix standard [17]. =20
>=20
> The guidance:
>>> Normative references specify documents that must be read to =
understand or implement the technology in the new RFC, or whose =
technology must be present for the technology in the new RFC to work.
>=20
> On its second appearance, I think [17] is definitely being used =
informatively.
> The first appearance is less clear  cut, I think. Am inclined to say =
this is still informative - it's just explaining the style adopted for =
the abstract specification (if [17] changed then it wouldn't be =
necessary to change this doc).
>=20

Agree that the 2nd appearance is informational. But the paragraph =
containing the first citation also contains the language "=20
The de facto standard API for TCP/IP applications is the "sockets" =
interface. This document provides an abstract definition of =
MPTCP-specific extensions to this interface."  It seems to me that one =
needs to understand the sockets api in order to understand an extension =
to the sockets api. . (And, as an additional nit, the first quoted =
sentence could probably also use a citation to [17])=20

> Thanks also for the nits

You're welcome :-)

Thanks!

Ben.=

From david.black@emc.com  Mon Aug 13 14:33:32 2012
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 0030A21F84E4 for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 14:33:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=0.113, 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 eFuJjIxIz6Q6 for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 14:33:30 -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 B16F121F853B for <gen-art@ietf.org>; Mon, 13 Aug 2012 14:33:29 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q7DLXKhk005454 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Aug 2012 17:33:24 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 13 Aug 2012 17:33:00 -0400
Received: from mxhub15.corp.emc.com (mxhub15.corp.emc.com [128.222.70.236]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q7DLWwk3028758; Mon, 13 Aug 2012 17:32:58 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub15.corp.emc.com ([128.222.70.236]) with mapi; Mon, 13 Aug 2012 17:32:58 -0400
From: "Black, David" <david.black@emc.com>
To: Martin Thomson <martin.thomson@gmail.com>, "draft-ietf-storm-iscsi-sam.all@tools.ietf.org" <draft-ietf-storm-iscsi-sam.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Mon, 13 Aug 2012 17:32:56 -0400
Thread-Topic: [Gen-art] GenART review of draft-ietf-storm-iscsi-sam-06
Thread-Index: Ac1p7ztS7WE09KUwRUae6j5CKR0etQPp56Pw
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208F127D3@MX15A.corp.emc.com>
References: <CABkgnnXUW4Lq3uyjd_4-z=01ED3=S9Q1Ui2NP-=LVA7sQTrMDw@mail.gmail.com>
In-Reply-To: <CABkgnnXUW4Lq3uyjd_4-z=01ED3=S9Q1Ui2NP-=LVA7sQTrMDw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: Mallikarjun Chadalapaka <cbm@chadalapaka.com>, Tom Talpey <ttalpey@microsoft.com>
Subject: Re: [Gen-art] GenART review of draft-ietf-storm-iscsi-sam-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: Mon, 13 Aug 2012 21:33:32 -0000

Martin,

Thank you very much for this review - you found a number of things
that need attention, but there are also a few comments that
(probably unbeknownst to you) represent design decisions that
cannot be revisited courtesy of the amount of deployed iSCSI
"running code".

Responses are inline below.

Thanks,
--David

> -----Original Message-----
> From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On Behal=
f Of
> Martin Thomson
> Sent: Tuesday, July 24, 2012 6:54 PM
> To: draft-ietf-storm-iscsi-sam.all@tools.ietf.org; gen-art@ietf.org
> Subject: [Gen-art] GenART review of draft-ietf-storm-iscsi-sam-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-storm-iscsi-sam-06
> Reviewer: Martin Thomson
> Review Date: 2012-07-24
> IESG Telechat date: ?
>=20
> Summary: This document has a few issues that would need to be
> addressed before it is published as a Standards Track RFC.
>=20
> Major Issues: None
>=20
> Minor Issues:
>=20
> Is the intent to reference RFC 3720 or the new -cons draft (as
> published)?  Given that -cons is intended to obsolete 3720, I would
> have expected no reference to 3720 at all.

That's a correct expectation, and results from some confusion over what the
final status of RFC 3720 would be.  As RFC 3720 is being obsoleted by the
-cons draft, RFC3720 cannot be normatively referenced by either the -sam or
-cons drafts, and hence most of the citations in the body of the -sam draft
need to be to the -cons draft.

> Section 5.1 / 5.1.1 does not define how many bits the PRI field
> consumes.  I might infer from the diagram that is the four most
> significant bits of the second byte, but the diagram is unclear.  In
> any case, the diagram should only be used for illustrative purposes
> and the text should provide the definitive answer.
>=20
> Section 5.2.1 also relies on the diagram.  Though in this case it is
> clearer and I can easily infer that the status qualifier is one byte,
> I'm still relying on the diagram.

These two are minor, but I have no problem with changing them as suggested.

> Why is Section 6.2.1 not Section 5.1.2?  Same for 6.2.2 and 6.2.3.
> Aren't these new (?) additions to the Command PDU?  Or is there
> another PDU that these apply to?

There's another PDU that these apply to, the Task Management Function
Request PD - its layout diagram needs to be copied into the -sam
draft from section 11.5 of the -cons draft so that the -sam draft is
somewhat more self-contained.
=20
> Section 7.1.1 What does it mean to not claim support for any
> particular level?  Obviously you can't use the features described
> here, but what else?

It just means that the system is running "iSCSI" without providing
any additional details.  The ability to announce support without
claiming support for any particular level is a SCSI feature that is
applied to all SCSI-related standards.  The other party in the
communication needs to make least common denominator assumptions
about supported functionality, subject to further checks that may
provide additional information (e.g., iSCSI text key negotiation,
read a particular SCSI VPD page).

> Section 8 makes a bold claim that needs substantiation.  Given the
> global nature of task identifiers, is it necessary to prevent one user
> from querying a task that another created?

No it is not - to the extent that iSCSI has a notion of user, that
notion is session-wide across all connections.

> What about triggering reset on a I_T nexus that another user is using?

The I_T NEXUS RESET function in the -sam draft can't do that because that
function is reflexive - it resets the I_T nexus on which the function is
sent.  Yes, this really is a SCSI version of "shoot yourself in the foot"
:-) and it is useful because target systems generally respond by cleaning
out all of the state related to the nexus which can clean up some situation=
s.

Nonetheless, there are already SCSI-defined means in iSCSI to take
out other I_T nexuses, and the security measures for those (primarily
configuration-based access control) are handled at the SCSI level.

Something else to keep in mind is that the usual notion of "user" as a pers=
on
does not apply to SCSI and iSCSI.  The initiator is typically an operating
system driver or iSCSI offload HBA, and hence the identity is a system
identity as opposed to a user identity.
=20
> Questions (for -cons):
>=20
> Section 6.2 makes the following requirement:
>    If the connection is still active (it is not undergoing an
>    implicit or explicit logout), QUERY TASK MUST be issued on the
>    same connection to which the task to be queried is allegiant at
>    the time the Task Management request is issued. If the
>    connection is implicitly or explicitly logged out (i.e., no other
>    request will be issued on the failing connection and no other
>    response will be received on the failing connection), then a
>    QUERY TASK function request may be issued on another connection.
>    This Task Management request will then establish a new allegiance
>    for the command being queried.
>=20
> The comment is probably more for of -cons (Section 4.2.5.1 and Section
> 7.2.2).  Obviously, this design is long-standing, and I'm only reading
> parts of the specification.

And there's a lot of "running code" that uses this design.
=20
> There is an implication that tasks have identification that is
> globally unique, even if the normal behaviour is to bind (ally) a
> request with a connection.  The reasons for allowing this are not
> explained, but it imposes some fragility on the system.  For instance,
> the requirement that the old connection be closed with a "remove the
> connection for recovery" seems counter to the goal of failure
> recovery.  If the point of this is for failure recovery, then a
> primary failure mode would be network failure - in which case this
> mechanism cannot be used.

There are multiple notions of "global" involved here.  Task identity is
global across the session, but not across independent sessions.  SCSI
multipathing (e.g., as used with SANs) involves independent iSCSI sessions
across which there is no shared iSCSI state.  The primary motivation for
this iSCSI failure recovery mechanism is partial network failure, e.g., the
two TCP connections are assigned to two different server NICs on the same
network, and one of those NICs fails.  Complete network failure is not=20
a motivation, as that would be handled at a higher level, e.g., by
SAN-oriented SCSI multipathing across iSCSI sessions on different networks,
and obviously, there's not much that can be done if all network connectivit=
y
is lost between a host and its storage.
=20
> What purpose does this allegiance feature address?

Isolates connection failure effects to I/Os that use the connection as
opposed to making them global.  It's not ideal, in that the CmdSN window
will likely run out by the time that the failure is detected and recovered
from, but at least failure of one connection doesn't stop all I/Os in
their tracks.  This also avoids a functionality shift when moving from
one-TCP-connection sessions (which are common) to multiple-TCP-connection
sessions.
=20
> What are the security implications of using allegiance?

Not much that I can immediately think of.  For any individual I/O, the
state and data are on a single connection, but security considerations
generally do not enter into connection selection - load balancing tends
to be the primary consideration.
=20
> Nits:
>=20
> I don't know what tooling was used to generate this document, but
> there are some strange artifacts.  In particular, diagrams and tables
> are misaligned in a number of places.

Guilty as charged (sorry), and there's actually a mistake in the mapping
table courtesy of another tool glitch.  A more careful check will be done
on the next version before it's submitted.  This is partly my fault, as
I leaned on the editor to get this version submitted with a text correction=
,
not realizing that the tooling would take advantage of the resulting haste
to make waste ...
=20
> There are a few terms like "I_T nexus" that are not explained prior to
> use.  These are defined in -cons.  However, I find the existence of a
> terminology mapping table in this draft to be strange.  Wouldn't that
> table be more useful in the "core" document?

Good suggestion, I've cc:'d the author of the -cons draft, and we'll
figure this out in consultation with the WG.

>=20
> Section 4.1:
>=20
> This seems unnecessarily convoluted:
>=20
>       Note that an operational value of "2" or higher for this key on
>       an iSCSI session does not influence the SCSI level features in
>       any way on that I_T nexus. An operational value of "2" or higher
>       for this key permits the iSCSI-related features defined in this
>       document to be used on all connections on this iSCSI session.
>       SCSI level hand-shakes (e.g. commands, mode pages) eventually
>       determine the existence or lack of various SAM-5 features
>       available for the I_T nexus between the two SCSI end points). To
>       summarize, negotiation of this key to "2" or higher is a
>       necessary but not a sufficient condition of SAM-5 compliant
>       feature usage at the SCSI protocol level.
>=20
> How about:
>=20
>   In addition to negotiating a value of "2" or higher, support for an ind=
ividual
>   MUST also be signaled using SCSI level hand-shakes prior to use.
>=20
> I know that adds 2119 language, but if the goal is to prevent someone
> from attempting to use a feature prior to getting positive
> confirmation of support, then this should be ok.

I think the addition of a "MUST" here is fine, and we'll see about crafting=
 some
language that better reflects the SCSI aspects, as "hand-shakes" is actuall=
y
not a common SCSI term.

> Section 6.2 describes multiple tasks.  It would be good if the
> description of each of the tasks were given a sub-section so that they
> could be cross referenced and more readily found.

Unfortunately, RFC 3720 and the consolidated draft were not written that wa=
y,
and we'd prefer to keep that structure.

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


From martin.thomson@gmail.com  Mon Aug 13 16:12:19 2012
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 194B021F867B for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 16:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.984
X-Spam-Level: 
X-Spam-Status: No, score=-3.984 tagged_above=-999 required=5 tests=[AWL=-0.385, 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 C67unGKul3TW for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 16:12:17 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 600F721F8499 for <gen-art@ietf.org>; Mon, 13 Aug 2012 16:12:17 -0700 (PDT)
Received: by lahm15 with SMTP id m15so2411202lah.31 for <gen-art@ietf.org>; Mon, 13 Aug 2012 16:12:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nXwEQYvg243ak0rJsldHqgkW1btkrfnFrgGTEErGEIo=; b=fAxABXUPVYHsusVks93s2JVsQjnGOa4z6lzPilT7vS80KITsGiR6t8PTFgwJh6gI3Q 3PX2e/zIT76VIJii8eAscfKcROSAtdEGS4rJ2hiE0eHvhA/4EpKYqXRNQ/TgWt7iX9eI ooe86/uUhtTycrzNLUGouL15szZam34ONzsJnYsKPsx0pF4mybqwK7Bq6Aor37q/+BEV dfz20WM7aZbN7IoGnt9a/9/79S6MEWWRaV0CApkX++eT9mRWprfPQeXQlTICna7JtBSr fYk8CJks8EckNH1VXMXqBTu1i+YihPbPpUgVJgdptGLjV+Bv9lWm9l5XQ2mYDjJa4MUS owTQ==
MIME-Version: 1.0
Received: by 10.152.146.169 with SMTP id td9mr10169764lab.42.1344899536201; Mon, 13 Aug 2012 16:12:16 -0700 (PDT)
Received: by 10.112.41.193 with HTTP; Mon, 13 Aug 2012 16:12:16 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208F127D3@MX15A.corp.emc.com>
References: <CABkgnnXUW4Lq3uyjd_4-z=01ED3=S9Q1Ui2NP-=LVA7sQTrMDw@mail.gmail.com> <8D3D17ACE214DC429325B2B98F3AE71208F127D3@MX15A.corp.emc.com>
Date: Mon, 13 Aug 2012 16:12:16 -0700
Message-ID: <CABkgnnUn72e1tExLH9szf-fGaXeQuL4bgp8P3uBodyw+-P2aJw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=UTF-8
Cc: "draft-ietf-storm-iscsi-sam.all@tools.ietf.org" <draft-ietf-storm-iscsi-sam.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Tom Talpey <ttalpey@microsoft.com>, Mallikarjun Chadalapaka <cbm@chadalapaka.com>
Subject: Re: [Gen-art] GenART review of draft-ietf-storm-iscsi-sam-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: Mon, 13 Aug 2012 23:12:19 -0000

David,

I think that you successfully covered most of the concerns.  I fully
expected there to be a number of decisions that would be immutable for
that reason.  I'll look for the update.

--Martin

On 13 August 2012 14:32, Black, David <david.black@emc.com> wrote:
> Martin,
>
> Thank you very much for this review - you found a number of things
> that need attention, but there are also a few comments that
> (probably unbeknownst to you) represent design decisions that
> cannot be revisited courtesy of the amount of deployed iSCSI
> "running code".
>
> Responses are inline below.
>
> Thanks,
> --David
>
>> -----Original Message-----
>> From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On Behalf Of
>> Martin Thomson
>> Sent: Tuesday, July 24, 2012 6:54 PM
>> To: draft-ietf-storm-iscsi-sam.all@tools.ietf.org; gen-art@ietf.org
>> Subject: [Gen-art] GenART review of draft-ietf-storm-iscsi-sam-06
>>
>> 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-storm-iscsi-sam-06
>> Reviewer: Martin Thomson
>> Review Date: 2012-07-24
>> IESG Telechat date: ?
>>
>> Summary: This document has a few issues that would need to be
>> addressed before it is published as a Standards Track RFC.
>>
>> Major Issues: None
>>
>> Minor Issues:
>>
>> Is the intent to reference RFC 3720 or the new -cons draft (as
>> published)?  Given that -cons is intended to obsolete 3720, I would
>> have expected no reference to 3720 at all.
>
> That's a correct expectation, and results from some confusion over what the
> final status of RFC 3720 would be.  As RFC 3720 is being obsoleted by the
> -cons draft, RFC3720 cannot be normatively referenced by either the -sam or
> -cons drafts, and hence most of the citations in the body of the -sam draft
> need to be to the -cons draft.
>
>> Section 5.1 / 5.1.1 does not define how many bits the PRI field
>> consumes.  I might infer from the diagram that is the four most
>> significant bits of the second byte, but the diagram is unclear.  In
>> any case, the diagram should only be used for illustrative purposes
>> and the text should provide the definitive answer.
>>
>> Section 5.2.1 also relies on the diagram.  Though in this case it is
>> clearer and I can easily infer that the status qualifier is one byte,
>> I'm still relying on the diagram.
>
> These two are minor, but I have no problem with changing them as suggested.
>
>> Why is Section 6.2.1 not Section 5.1.2?  Same for 6.2.2 and 6.2.3.
>> Aren't these new (?) additions to the Command PDU?  Or is there
>> another PDU that these apply to?
>
> There's another PDU that these apply to, the Task Management Function
> Request PD - its layout diagram needs to be copied into the -sam
> draft from section 11.5 of the -cons draft so that the -sam draft is
> somewhat more self-contained.
>
>> Section 7.1.1 What does it mean to not claim support for any
>> particular level?  Obviously you can't use the features described
>> here, but what else?
>
> It just means that the system is running "iSCSI" without providing
> any additional details.  The ability to announce support without
> claiming support for any particular level is a SCSI feature that is
> applied to all SCSI-related standards.  The other party in the
> communication needs to make least common denominator assumptions
> about supported functionality, subject to further checks that may
> provide additional information (e.g., iSCSI text key negotiation,
> read a particular SCSI VPD page).
>
>> Section 8 makes a bold claim that needs substantiation.  Given the
>> global nature of task identifiers, is it necessary to prevent one user
>> from querying a task that another created?
>
> No it is not - to the extent that iSCSI has a notion of user, that
> notion is session-wide across all connections.
>
>> What about triggering reset on a I_T nexus that another user is using?
>
> The I_T NEXUS RESET function in the -sam draft can't do that because that
> function is reflexive - it resets the I_T nexus on which the function is
> sent.  Yes, this really is a SCSI version of "shoot yourself in the foot"
> :-) and it is useful because target systems generally respond by cleaning
> out all of the state related to the nexus which can clean up some situations.
>
> Nonetheless, there are already SCSI-defined means in iSCSI to take
> out other I_T nexuses, and the security measures for those (primarily
> configuration-based access control) are handled at the SCSI level.
>
> Something else to keep in mind is that the usual notion of "user" as a person
> does not apply to SCSI and iSCSI.  The initiator is typically an operating
> system driver or iSCSI offload HBA, and hence the identity is a system
> identity as opposed to a user identity.
>
>> Questions (for -cons):
>>
>> Section 6.2 makes the following requirement:
>>    If the connection is still active (it is not undergoing an
>>    implicit or explicit logout), QUERY TASK MUST be issued on the
>>    same connection to which the task to be queried is allegiant at
>>    the time the Task Management request is issued. If the
>>    connection is implicitly or explicitly logged out (i.e., no other
>>    request will be issued on the failing connection and no other
>>    response will be received on the failing connection), then a
>>    QUERY TASK function request may be issued on another connection.
>>    This Task Management request will then establish a new allegiance
>>    for the command being queried.
>>
>> The comment is probably more for of -cons (Section 4.2.5.1 and Section
>> 7.2.2).  Obviously, this design is long-standing, and I'm only reading
>> parts of the specification.
>
> And there's a lot of "running code" that uses this design.
>
>> There is an implication that tasks have identification that is
>> globally unique, even if the normal behaviour is to bind (ally) a
>> request with a connection.  The reasons for allowing this are not
>> explained, but it imposes some fragility on the system.  For instance,
>> the requirement that the old connection be closed with a "remove the
>> connection for recovery" seems counter to the goal of failure
>> recovery.  If the point of this is for failure recovery, then a
>> primary failure mode would be network failure - in which case this
>> mechanism cannot be used.
>
> There are multiple notions of "global" involved here.  Task identity is
> global across the session, but not across independent sessions.  SCSI
> multipathing (e.g., as used with SANs) involves independent iSCSI sessions
> across which there is no shared iSCSI state.  The primary motivation for
> this iSCSI failure recovery mechanism is partial network failure, e.g., the
> two TCP connections are assigned to two different server NICs on the same
> network, and one of those NICs fails.  Complete network failure is not
> a motivation, as that would be handled at a higher level, e.g., by
> SAN-oriented SCSI multipathing across iSCSI sessions on different networks,
> and obviously, there's not much that can be done if all network connectivity
> is lost between a host and its storage.
>
>> What purpose does this allegiance feature address?
>
> Isolates connection failure effects to I/Os that use the connection as
> opposed to making them global.  It's not ideal, in that the CmdSN window
> will likely run out by the time that the failure is detected and recovered
> from, but at least failure of one connection doesn't stop all I/Os in
> their tracks.  This also avoids a functionality shift when moving from
> one-TCP-connection sessions (which are common) to multiple-TCP-connection
> sessions.
>
>> What are the security implications of using allegiance?
>
> Not much that I can immediately think of.  For any individual I/O, the
> state and data are on a single connection, but security considerations
> generally do not enter into connection selection - load balancing tends
> to be the primary consideration.
>
>> Nits:
>>
>> I don't know what tooling was used to generate this document, but
>> there are some strange artifacts.  In particular, diagrams and tables
>> are misaligned in a number of places.
>
> Guilty as charged (sorry), and there's actually a mistake in the mapping
> table courtesy of another tool glitch.  A more careful check will be done
> on the next version before it's submitted.  This is partly my fault, as
> I leaned on the editor to get this version submitted with a text correction,
> not realizing that the tooling would take advantage of the resulting haste
> to make waste ...
>
>> There are a few terms like "I_T nexus" that are not explained prior to
>> use.  These are defined in -cons.  However, I find the existence of a
>> terminology mapping table in this draft to be strange.  Wouldn't that
>> table be more useful in the "core" document?
>
> Good suggestion, I've cc:'d the author of the -cons draft, and we'll
> figure this out in consultation with the WG.
>
>>
>> Section 4.1:
>>
>> This seems unnecessarily convoluted:
>>
>>       Note that an operational value of "2" or higher for this key on
>>       an iSCSI session does not influence the SCSI level features in
>>       any way on that I_T nexus. An operational value of "2" or higher
>>       for this key permits the iSCSI-related features defined in this
>>       document to be used on all connections on this iSCSI session.
>>       SCSI level hand-shakes (e.g. commands, mode pages) eventually
>>       determine the existence or lack of various SAM-5 features
>>       available for the I_T nexus between the two SCSI end points). To
>>       summarize, negotiation of this key to "2" or higher is a
>>       necessary but not a sufficient condition of SAM-5 compliant
>>       feature usage at the SCSI protocol level.
>>
>> How about:
>>
>>   In addition to negotiating a value of "2" or higher, support for an individual
>>   MUST also be signaled using SCSI level hand-shakes prior to use.
>>
>> I know that adds 2119 language, but if the goal is to prevent someone
>> from attempting to use a feature prior to getting positive
>> confirmation of support, then this should be ok.
>
> I think the addition of a "MUST" here is fine, and we'll see about crafting some
> language that better reflects the SCSI aspects, as "hand-shakes" is actually
> not a common SCSI term.
>
>> Section 6.2 describes multiple tasks.  It would be good if the
>> description of each of the tasks were given a sub-section so that they
>> could be cross referenced and more readily found.
>
> Unfortunately, RFC 3720 and the consolidated draft were not written that way,
> and we'd prefer to keep that structure.
>
>>
>> --Martin
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>

From suresh.krishnan@ericsson.com  Mon Aug 13 16:57:26 2012
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 8178821F866A for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 16:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level: 
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.026, 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 S3DwLBxLQ9gO for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 16:57:25 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5EB21F862A for <gen-art@ietf.org>; Mon, 13 Aug 2012 16:57:25 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q7DNvXZL013167; Mon, 13 Aug 2012 18:57:34 -0500
Received: from [142.133.112.80] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.264.1; Mon, 13 Aug 2012 19:57:18 -0400
Message-ID: <5029945D.7010004@ericsson.com>
Date: Mon, 13 Aug 2012 19:57:17 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, <draft-ietf-abfab-usecases-03.all@tools.ietf.org>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-abfab-usecases-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: Mon, 13 Aug 2012 23:57:26 -0000

I am the assigned Gen-ART reviewer for
draft-ietf-abfab-usecases-03.txt

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 ready for publication as an Informational RFC,
but I do have some minor comments that you may like to address.

Minor
=====

* This document references obsolete versions of IMAP and SMTP. Is there
any specific reason for referring to the older versions? If not, I
recommend replacing references to

-> RFC2060 with RFC3501
-> RFC2821 with RFC5321

* Section 3.7

The following text is a bit out of date.

"At present, authentication to these applications will be typically
   configured manually by the user on the device (or on a different
   device connected to that device) but inputting their (usually pre-
   provisioned out-of-band) credentials for that application - one per
   application."

With systems such as IMS that have gotten deployed, at least telco
operator hosted applications can use some form of federated identity
already. I do not have strong feelings about this but I suggest leaving
out operator hosted applications from this characterization.

* Section 3.9

I am not sure I understand the following text

"The utility company may wish to
   grant access only to authorized devices; for example, a consortium of
   utility companies and device manufacturers may certify devices to
   connect to power networks."

What does the word certify mean here? I have always understood it to
mean testing compliance to certain requirements rather than verification
of identity. Can you please clarify?

Thanks
Suresh

















From suresh.krishnan@ericsson.com  Mon Aug 13 16:59:26 2012
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 6C91A21F866A for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 16:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level: 
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.026, 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 Zf-CE+ihc1aB for <gen-art@ietfa.amsl.com>; Mon, 13 Aug 2012 16:59:26 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id DBFF221F862A for <gen-art@ietf.org>; Mon, 13 Aug 2012 16:59:25 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q7DNxMu6030139 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Aug 2012 18:59:25 -0500
Received: from [142.133.112.80] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.31) with Microsoft SMTP Server (TLS) id 8.3.264.1; Mon, 13 Aug 2012 19:59:22 -0400
Message-ID: <502994D9.2010309@ericsson.com>
Date: Mon, 13 Aug 2012 19:59:21 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, <draft-ietf-abfab-usecases.all@tools.ietf.org>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-abfab-usecases-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: Mon, 13 Aug 2012 23:59:26 -0000

I am the assigned Gen-ART reviewer for
draft-ietf-abfab-usecases-03.txt

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 ready for publication as an Informational RFC,
but I do have some minor comments that you may like to address.

Minor
=====

* This document references obsolete versions of IMAP and SMTP. Is there
any specific reason for referring to the older versions? If not, I
recommend replacing references to

-> RFC2060 with RFC3501
-> RFC2821 with RFC5321

* Section 3.7

The following text is a bit out of date.

"At present, authentication to these applications will be typically
   configured manually by the user on the device (or on a different
   device connected to that device) but inputting their (usually pre-
   provisioned out-of-band) credentials for that application - one per
   application."

With systems such as IMS that have gotten deployed, at least telco
operator hosted applications can use some form of federated identity
already. I do not have strong feelings about this but I suggest leaving
out operator hosted applications from this characterization.

* Section 3.9

I am not sure I understand the following text

"The utility company may wish to
   grant access only to authorized devices; for example, a consortium of
   utility companies and device manufacturers may certify devices to
   connect to power networks."

What does the word certify mean here? I have always understood it to
mean testing compliance to certain requirements rather than verification
of identity. Can you please clarify?

Thanks
Suresh
















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

From adrian@olddog.co.uk  Mon Aug 13 22:05:04 2012
Return-Path: <adrian@olddog.co.uk>
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 F294521F8648; Mon, 13 Aug 2012 22:05:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level: 
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.087,  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 ms+wK5KcfPnl; Mon, 13 Aug 2012 22:05:02 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 9A2C621F8621; Mon, 13 Aug 2012 22:05:01 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7E54wrC016653;  Tue, 14 Aug 2012 06:04:58 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7E54q1X016625 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 14 Aug 2012 06:04:56 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Roni Even'" <ron.even.tlv@gmail.com>, <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
References: <002101cd7997$a5204330$ef60c990$@gmail.com>
In-Reply-To: <002101cd7997$a5204330$ef60c990$@gmail.com>
Date: Tue, 14 Aug 2012 06:04:49 +0100
Message-ID: <09c201cd79da$570f3be0$052db3a0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_09C3_01CD79E2.B8D837C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGVMjaGM7HZ8bSlogDWIwhoGoR3V5fJT4Qg
Content-Language: en-gb
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 14 Aug 2012 05:05:04 -0000

This is a multipart message in MIME format.

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

Thanks Roni,
Good catches.
Adrian
 
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Roni
Even
Sent: 13 August 2012 22:07
To: draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org
Cc: gen-art@ietf.org; ietf@ietf.org
Subject: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-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-ccamp-rfc5787bis-05.
Reviewer: Roni Even
Review Date:2012-8-12
IETF LC End Date: 2012-8-17
IESG Telechat date:
 
Summary: This draft is almost ready for publication as a standard track RFC.
 
 
Major issues:
 
Minor issues:
In section 6.1 " If specified more than once, instances preceding the first will
be ignored and condition SHOULD be logged for possible action by the network
operator."  I am not sure what is meant by preceding the first.
 
 
Nits/editorial comments:
 
1.	The following note appears in section 10.1, 10.2 and 10.3. "Note that
the same values for the Inter-RA Export Upward sub-TLV and the Inter-RA Export
Downward Sub-TLV MUST be used when they appear in the Link TLV, Node Attribute
TLV, and Router Address TLV." - why not have it in section 10 before section
10.1.
2.	I saw in appendix  B that one of the changes from RFC 5787 was to
clarify the terminology before defining extensions, I would have found it easier
to read if the ASON hierarchy and the relation to OSPF in section 2 were
presented in figures. This was more an issue to me as a reader not familiar with
the terminology and I would like to think that the more familiar reader will not
have problem.
 
 

------=_NextPart_000_09C3_01CD79E2.B8D837C0
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=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CD79E2.796F9CE0"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520092929 1073786111 9 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-520092929 1073806591 9 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.5pt;
	font-family:Consolas;
	mso-fareast-font-family:Calibri;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:Calibri;
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:715087181;
	mso-list-type:hybrid;
	mso-list-template-ids:-1205706658 -1668626108 67698713 67698715 =
67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-bidi-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:1630161403;
	mso-list-template-ids:-244951626;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[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-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New Roman";color:#1F497D'>Thanks =
Roni,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New Roman";color:#1F497D'>Good =
catches.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New =
Roman";color:#1F497D'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><b><=
span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> =
ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of =
</b>Roni Even<br><b>Sent:</b> 13 August 2012 22:07<br><b>To:</b> =
draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org<br><b>Cc:</b> =
gen-art@ietf.org; ietf@ietf.org<br><b>Subject:</b> Gen-ART LC review of =
draft-ietf-ccamp-rfc5787bis-05<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>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></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Please resolve these comments along =
with any other Last Call comments you may =
receive.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Document: </span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>draft-ietf-ccamp-rfc5787bis-05.</span><=
span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Reviewer: Roni Even<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Review Date:2012&#8211;8&#8211;12<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>IETF LC End Date: =
2012&#8211;8&#8211;17<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>IESG Telechat date:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Summary: This draft is almost ready for publication as a =
standard track RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Major issues:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Minor issues:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>In section 6.1 &#8220; If specified =
more than once, instances preceding the first will be ignored and =
condition SHOULD be logged for possible action by the network =
operator.&#8221;&nbsp; I am not sure what is meant by preceding the =
first.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Nits/editorial comments:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><ol style=3D'margin-top:0cm' =
start=3D1 type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 =
lfo3'><span lang=3DEN-US style=3D'mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:EN-US'>The following note appears in section =
10.1, 10.2 and 10.3. &#8220;Note that the same values for the Inter-RA =
Export Upward sub-TLV and the Inter-RA Export Downward Sub-TLV MUST be =
used when they appear in the Link TLV, Node Attribute TLV, and Router =
Address TLV.&#8221; &#8211; why not have it in section 10 before section =
10.1.<o:p></o:p></span></li><li class=3DMsoNormal style=3D'mso-list:l0 =
level1 lfo3'><span lang=3DEN-US style=3D'mso-fareast-font-family:"Times =
New Roman";mso-ansi-language:EN-US'>I saw in appendix&nbsp; B that one =
of the changes from RFC 5787 was to clarify the terminology before =
defining extensions, I would have found it easier to read if the ASON =
hierarchy and the relation to OSPF in section 2 were presented in =
figures. This was more an issue to me as a reader not familiar with the =
terminology and I would like to think that the more familiar reader will =
not have problem.<o:p></o:p></span></li></ol><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p></div></div=
></body></html>
------=_NextPart_000_09C3_01CD79E2.B8D837C0--


From rjsparks@nostrum.com  Tue Aug 14 08:13:41 2012
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 08BBB21F8543 for <gen-art@ietfa.amsl.com>; Tue, 14 Aug 2012 08:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.461
X-Spam-Level: 
X-Spam-Status: No, score=-102.461 tagged_above=-999 required=5 tests=[AWL=0.139, 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 5gJIrlbfN0Kv for <gen-art@ietfa.amsl.com>; Tue, 14 Aug 2012 08:13:40 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7BE1E21F853A for <gen-art@ietf.org>; Tue, 14 Aug 2012 08:13:40 -0700 (PDT)
Received: from unnumerable.local (pool-173-57-102-202.dllstx.fios.verizon.net [173.57.102.202]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7EFDWSS060393 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 14 Aug 2012 10:13:33 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <502A6B1D.8050706@nostrum.com>
Date: Tue, 14 Aug 2012 10:13:33 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@fdupont.fr>
References: <201208130917.q7D9Hmxx004131@givry.fdupont.fr>
In-Reply-To: <201208130917.q7D9Hmxx004131@givry.fdupont.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.57.102.202 is authenticated by a trusted mechanism)
Cc: gen-art@ietf.org, draft-sparks-genarea-mailarch.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-sparks-genarea-mailarch-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, 14 Aug 2012 15:13:41 -0000

On 8/13/12 4:17 AM, Francis Dupont 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-sparks-genarea-mailarch-05.txt
> Reviewer: Francis Dupont
> Review Date: 20120810
> IETF LC End Date: 20120813
> IESG Telechat date: unknown
>
> Summary: Ready
>
> Major issues: None
>
> Minor issues:
>   - a very minor question: why in the search syntax is there no "NOT" operator,
>    only "AND" and "OR"?
I can add NOT to that list.
>   - annoying edition bug in 2.6
Are you pointing to the last bulleted item in that section being on the 
next page, or something else?
>
> Nits/editorial comments:
Thanks for these.
>   - ToC page 2 and 6 page 7: Acknowledgements -> Acknowledgments
>
>   - 1 page 3 and 2.1 page 4: capabilites -> capabilities
>
>   - 2.1 page 4: occuring -> occurring
>
>   - 2.6 page 7: please remove the last item, i.e.:
>
>     o  The system must allow the administrator to delete messages from an
>        archived list
>
>    which is already specified by the previous one, i.e.:
>
>     o  The system must allow the administrator to add messages to and
>        delete messages from an archived list.  The system should log such
>        actions.
>
> Regards
>
> Francis.Dupont@fdupont.fr
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From david.black@emc.com  Tue Aug 14 16:51:54 2012
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 A15DA21F86D7; Tue, 14 Aug 2012 16:51:54 -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.032, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, 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 7cpcjzksqQle; Tue, 14 Aug 2012 16:51:54 -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 5B5A321F86D6; Tue, 14 Aug 2012 16:51:51 -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 q7ENoSmp032347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Aug 2012 19:50:29 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 14 Aug 2012 19:50:21 -0400
Received: from mxhub07.corp.emc.com (mxhub07.corp.emc.com [128.222.70.204]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q7ENoKWY016763; Tue, 14 Aug 2012 19:50:21 -0400
Received: from mx15a.corp.emc.com ([169.254.1.66]) by mxhub07.corp.emc.com ([128.222.70.204]) with mapi; Tue, 14 Aug 2012 19:50:20 -0400
From: "Black, David" <david.black@emc.com>
To: "michelle.cotton@icann.org" <michelle.cotton@icann.org>, "leo.vegoda@icann.org" <leo.vegoda@icann.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Tue, 14 Aug 2012 19:50:19 -0400
Thread-Topic: Gen-ART review of draft-vegoda-cotton-rfc5735bis-03
Thread-Index: Ac12g1nlR2o6ek4yS0CffYeN22Tw+AD9ATuA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120A2ECED3@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208F1240F@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208F1240F@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>
Subject: Re: [Gen-art] Gen-ART review of draft-vegoda-cotton-rfc5735bis-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, 14 Aug 2012 23:51:54 -0000

The -03 version of this draft addresses the nits in the Gen-ART version
of the -02 version.  Section 5 has been removed in the -03 version,
so the nit that was there is gone.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Thursday, August 09, 2012 7:05 PM
> To: michelle.cotton@icann.org; leo.vegoda@icann.org; gen-art@ietf.org
> Cc: Black, David; ietf@ietf.org
> Subject: Gen-ART review of draft-vegoda-cotton-rfc5735bis-02
>=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-vegoda-cotton-rfc5735bis-02
> Reviewer: David L. Black
> Review Date: August 9, 2012
> IETF LC End Date: August 9, 2012
>=20
> Summary:
> This draft is basically ready for publication, but has nits that
> should be fixed before publication.
>=20
> This draft provides an updated list of the special use IPv4 address block=
s
> that have been allocated by IANA along with explanations of their special
> uses.
>=20
> I found one nit and idnits found another one.
>=20
> Section 5 - the first sentence in the second paragraph is:
>=20
>    The domain name and IP address spaces involve policy issues (in
>    addition to technical issues) so that the requirements of [RFC2860]
>    do not apply generally to those spaces.
>=20
> I'm surprised by "do not apply generally".  I would have expected that
> the policy issues create requirements and constraints above and beyond
> the requirements in RFC 2860 as opposed to replacing those requirements.
>=20
> idnits 2.12.13 complained about a lot of IP addresses that aren't in
> the address ranges used for examples.  These complaints can be ignored,
> but idnits did find one actual nit:
>=20
>   =3D=3D Unused Reference: 'RFC6441' is defined on line 346, but no expli=
cit
>      reference was found in the text
>=20
> 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-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20


From smith@Cardiff.ac.uk  Wed Aug 15 08:05:51 2012
Return-Path: <smith@Cardiff.ac.uk>
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 5885621E80B6 for <gen-art@ietfa.amsl.com>; Wed, 15 Aug 2012 08:05:51 -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=[AWL=0.000,  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 c1adlxiIzgba for <gen-art@ietfa.amsl.com>; Wed, 15 Aug 2012 08:05:50 -0700 (PDT)
Received: from smtpout1.cf.ac.uk (smtpout1.cf.ac.uk [131.251.137.125]) by ietfa.amsl.com (Postfix) with ESMTP id 858E421E80B3 for <gen-art@ietf.org>; Wed, 15 Aug 2012 08:05:50 -0700 (PDT)
Received: from smtpauth.cf.ac.uk ([131.251.248.19]) by smtpout1.cf.ac.uk with esmtp (Exim 4.76) (envelope-from <smith@Cardiff.ac.uk>) id 1T1fAL-00017u-AJ; Wed, 15 Aug 2012 16:05:49 +0100
Received: from [131.251.148.37] (helo=dangermouse.insrv.cf.ac.uk) by smtpauth.cf.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <scmros@smtpauth.cf.ac.uk>) id 1T1fAL-0005xV-9C; Wed, 15 Aug 2012 16:05:49 +0100
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Rhys Smith <smith@cardiff.ac.uk>
In-Reply-To: <502994D9.2010309@ericsson.com>
Date: Wed, 15 Aug 2012 16:05:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6770888-6673-44C0-85B5-62AF553E7DD2@cardiff.ac.uk>
References: <502994D9.2010309@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1278)
Sender: smith@Cardiff.ac.uk
X-Virus-Scanned: Cardiff University Virus Scanner
X-Virus-Scanned: Cardiff University Virus Scanner
X-Mailman-Approved-At: Wed, 15 Aug 2012 08:14:26 -0700
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-abfab-usecases.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-abfab-usecases-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, 15 Aug 2012 15:05:51 -0000

Hi Suresh,

Thanks for the time you've spent looking through the document.

Comments inline:

> Minor
> =3D=3D=3D=3D=3D
>=20
> * This document references obsolete versions of IMAP and SMTP. Is =
there
> any specific reason for referring to the older versions? If not, I
> recommend replacing references to
>=20
> -> RFC2060 with RFC3501
> -> RFC2821 with RFC5321

Fixed.


>=20
> * Section 3.7
>=20
> The following text is a bit out of date.
>=20
> "At present, authentication to these applications will be typically
>   configured manually by the user on the device (or on a different
>   device connected to that device) but inputting their (usually pre-
>   provisioned out-of-band) credentials for that application - one per
>   application."
>=20
> With systems such as IMS that have gotten deployed, at least telco
> operator hosted applications can use some form of federated identity
> already. I do not have strong feelings about this but I suggest =
leaving
> out operator hosted applications from this characterisation.

This use case came directly from some authors involved in operating =
mobile platforms. I think it's still useful to leave it in there as =
there are a variety of non-operator hosted applications that may not =
have such a thing enabled. The text currently says "could be hosted by =
the telecoms operator, or could be any application or system on the =
internet" which I think means the point is still valid...



> * Section 3.9
>=20
> I am not sure I understand the following text
>=20
> "The utility company may wish to
>   grant access only to authorized devices; for example, a consortium =
of
>   utility companies and device manufacturers may certify devices to
>   connect to power networks."
>=20
> What does the word certify mean here? I have always understood it to
> mean testing compliance to certain requirements rather than =
verification
> of identity. Can you please clarify?

In this case it would be exactly as you say - testing compliance to =
certain requirements. In the case of utility networks, it might mean =
that a particular device has the "usual" power certifications about how =
it uses electricity, but also certification around its "smartness" - =
what identity technologies it supports, what levels of assurance it can =
comply with around identity assertion, etc.

Hope that helps?

Thanks!
Rhys.=

From bill.wu@huawei.com  Wed Aug 15 22:00:11 2012
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 BB5E521F84A7 for <gen-art@ietfa.amsl.com>; Wed, 15 Aug 2012 22:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.324
X-Spam-Level: 
X-Spam-Status: No, score=-4.324 tagged_above=-999 required=5 tests=[AWL=0.522,  BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zu5MGFLcIjUP for <gen-art@ietfa.amsl.com>; Wed, 15 Aug 2012 22:00:10 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 409DD21F84B2 for <gen-art@ietf.org>; Wed, 15 Aug 2012 22:00:10 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIX45571; Wed, 15 Aug 2012 21:00:09 -0800 (PST)
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 15 Aug 2012 21:57:40 -0700
Received: from SZXEML407-HUB.china.huawei.com (10.82.67.94) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 15 Aug 2012 21:57:45 -0700
Received: from w53375 (10.138.41.149) by szxeml407-hub.china.huawei.com (10.82.67.94) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 16 Aug 2012 12:57:39 +0800
Message-ID: <C0D04E3710A04C6C8327E441D34CFFFC@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>, <draft-ietf-avtcore-monarch.all@tools.ietf.org>, <gen-art@ietf.org>
References: <25DC600D0CC1F2479C7053ADEB93004E6C4E675DA7@EUSAACMS0703.eamcs.ericsson.se>
Date: Thu, 16 Aug 2012 12:57:39 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-avtcore-monarch-17
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, 16 Aug 2012 05:00:12 -0000

SEksTWVyYWw6DQpTb3JyeSBmb3IgbGF0ZSwgcGxlYXNlIHNlZSBteSByZXBsaWVzIGlubGluZSBi
ZWxvdy4NCg0KUmVnYXJkcyENCi1RaW4NCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gDQpG
cm9tOiAiTWVyYWwgU2hpcmF6aXBvdXIiIDxtZXJhbC5zaGlyYXppcG91ckBlcmljc3Nvbi5jb20+
DQpUbzogPGRyYWZ0LWlldGYtYXZ0Y29yZS1tb25hcmNoLmFsbEB0b29scy5pZXRmLm9yZz47IDxn
ZW4tYXJ0QGlldGYub3JnPg0KU2VudDogV2VkbmVzZGF5LCBBdWd1c3QgMDEsIDIwMTIgMTA6MDIg
QU0NClN1YmplY3Q6IEdlbi1BUlQgTGFzdCBDYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWF2dGNv
cmUtbW9uYXJjaC0xNw0KDQoNCkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9y
IHRoaXMgZHJhZnQuIEZvciBiYWNrZ3JvdW5kIG9uIEdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZB
USBhdCA8aHR0cDovL3dpa2kudG9vbHMuaWV0Zi5vcmcvYXJlYS9nZW4vdHJhYy93aWtpL0dlbkFy
dGZhcT4gLg0KDQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBv
dGhlciBMYXN0IENhbGwgY29tbWVudHMgeW91IG1heSByZWNlaXZlLg0KDQpEb2N1bWVudDogZHJh
ZnQtaWV0Zi1hdnRjb3JlLW1vbmFyY2gtMTcNClJldmlld2VyOiBNZXJhbCBTaGlyYXppcG91cg0K
UmV2aWV3IERhdGU6IDIwMTItMDctMzENCklFVEYgTEMgRW5kIERhdGU6IDIwMTItMDgtMDINCklF
U0cgVGVsZWNoYXQgZGF0ZTogMjAxMi0wOC0xNg0KDQoNCg0KU3VtbWFyeToNClRoaXMgZHJhZnQg
aXMgYWxtb3N0IHJlYWR5IHRvIGJlIHB1Ymxpc2hlZCBhcyBJbmZvcm1hdGlvbmFsIFJGQyBidXQg
SSBoYXZlIHNvbWUgY29tbWVudHMuDQoNCg0KDQpOaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCg0K
LVtQYWdlIDVdLCBpbiB0aGUgZGVmaW5pdGlvbiBvZiAiVHJhbnNwb3J0IGxldmVsIG1ldHJpY3Mi
LCBzdWdnZXN0aW9uOiBwbGVhc2UgY2xhcmlmeSAicGFja2V0IGRlbGF5IHZhcmlhdGlvbiIsIGFz
IGRvbmUgaW4gU2VjdGlvbiA2Lg0KIGV4LjogInBhY2tldCBkZWxheSB2YXJpYXRpb24iIC0tLS0t
PiJwYWNrZXQgZGVsYXkgdmFyaWF0aW9uIChQRFYpIHdoaWNoIGNvdWxkIGJlIGppdHRlciBvciBh
bm90aGVyIG1ldHJpYyIuIA0KDQpbUWluXTogSSBwcmVmZXIgdG8gcmVmZXJlbmNlIHRvIFJGQzU0
ODEgIlBhY2tldCBEZWxheSBWYXJpYXRpb24gUHJvYmxlbSBzdGF0ZW1lbnQiIGFuZCBwcm9wb3Nl
IHRoZSBmb2xsb3dpbmcgY2hhbmdlOg0KInBhY2tldCBkZWxheSB2YXJpYXRpb24iIC0tLS0tLT4g
InBhY2tldCBkZWxheSB2YXJpYXRpb24gd2hpY2ggaXMgc29tZXRpbWVzIGNhbGxlZCBqaXR0ZXIg
W1JGQzU0ODFdIg0KDQotW1BhZ2UgNV0saW4gdGhlIGRlZmluaXRpb24gb2YgIkFwcGxpY2F0aW9u
IGxldmVsIG1ldHJpY3MiLCAiZW5kLXRvLWVuZCIgLS0tLT4iZW5kIHRvIGVuZCIgIChOb3RlOiB0
aGUgcmVzdCBvZiB0aGUgZG9jdW1lbnQgdXNlcyBlbmQgdG8gZW5kKS4NCg0KW1Fpbl06IE9rYXku
DQoNCi1bUGFnZSA1XSxpbiB0aGUgZGVmaW5pdGlvbiBvZiAiQXBwbGljYXRpb24gbGV2ZWwgbWV0
cmljcyIsIHR5cG86ICJ1c3VzYWxseSItLS0tPiJ1c3VhbGx5Ig0KDQpbUWluXTogR29vZCBjYXRj
aCwgdGhhbmtzLg0KDQotW1BhZ2UgN10sIFNlY3Rpb24gMywgIlNJUCIsIGZpcnN0IG9jY3VycmVu
Y2Ugb2YgdGhlIHdvcmQuIFN1Z2dlc3Rpb246IHBsZWFzZSBzcGVsbCBvdXQgIlNlc3Npb24gSW5p
dGlhdGlvbiBQcm90b2NvbCAoU0lQKSINCg0KW1Fpbl06IE9rYXkuDQoNCi1bUGFnZSA3XSwgU2Vj
dGlvbiAzLjEsIHN1Z2dlc3Rpb246ICJzaG93biBiZWxvdyItLS0tLT4iZGVzY3JpYmVkIGJlbG93
Iiwgc2luY2UgRmlndXJlIDEgaXMgb24gYW5vdGhlciBwYWdlLCAiZGVzY3JpYmUgYmVsb3ciIGlz
IG1vcmUgc3VpdGFibGUgdGhhbiAic2hvd24iLg0KDQpbUWluXTogT2theS4NCg0KLVtQYWdlIDdd
LCBTZWN0aW9uIDMuMSwgcmlnaHQgYWZ0ZXIgdHdvIGJ1bGxldHMsIHN1Z2dlc3Rpb246ICJSVFAg
TW9uaXRvciItLS0tLT4iUlRQIG1vbml0b3IiLCBzaW5jZSBtb25pdG9yIGlzIHNtYWxsIGNhcHMg
dGhyb3VnaG91dCB0aGUgcmVzdCBvZiB0aGUgZG9jdW1lbnQuDQoNCltRaW5dOiBPa2F5Lg0KDQot
W1BhZ2UgOF0sIDUgbGluZSBiZWZvcmUgbGFzdCwgInNlZSBmaWd1cmUgMSItLS0tPiJzZWUgRmln
dXJlIDEiDQoNCltRaW5dOiBPa2F5Lg0KDQotW1BhZ2UgOV0sIFNlY3Rpb24gMy4yIGZpcnN0IGxp
bmUsICJzaG93biBpbiB0aGUgRmlndXJlIDEiLS0tLT4ic2hvd24gaW4gRmlndXJlIDEiDQoNCltR
aW5dOiBPa2F5Lg0KDQotW1BhZ2UgOV0sIFNlY3Rpb24gMy4yIGxpbmUgMiwgYW5kIGxpbmUgMSBv
ZiBzZWNvbmQgcGFyYWdyYXBoLCBzdWdnZXN0aW9uOiAiZW5kLXN5c3RlbXMiLS0tLT4iZW5kIHN5
c3RlbXMiLCBmb3IgY29uc2lzdGVuY3kgd2l0aCB0aGUgcmVzdCBvZiB0aGUgZG9jdW1lbnQuDQoN
CltRaW5dOiBPa2F5Lg0KDQotW1BhZ2UgOV0sIFNlY3Rpb24gMy4yIDNyZCBwYXJhZ3JhcGgsICJN
Q1VzIiwgZmlyc3Qgb2NjdXJyZW5jZSBvZiB0aGUgd29yZC4gU3VnZ2VzdGlvbjogcGxlYXNlIHNw
ZWxsIG91dCAiTXVsdGlwb2ludCBDb250cm9sIFVuaXRzIChNQ1VzKSIuDQoNCltRaW5dOiBPa2F5
Lg0KDQotW1BhZ2UgOV0sIFNlY3Rpb24gMy4yIDNyZCBwYXJhZ3JhcGgsICJTU1JDIiwgZmlyc3Qg
b2NjdXJyZW5jZSBvZiB0aGUgd29yZC4gU3VnZ2VzdGlvbjogcGxlYXNlIHNwZWxsIG91dCAiU3lu
Y2hyb25pemF0aW9uIHNvdXJjZSAoU1NSQykiOw0KdGhlbiBbUGFnZSAxMF0sIlN5bmNocm9uaXph
dGlvbiBzb3VyY2UgKFNTUkMpIiBkb2VzIG5vdCBuZWVkIHRvIGJlIHNwZWxsZWQgb3V0IGEgc2Vj
b25kIHRpbWUuDQoNCltRaW5dOiBPa2F5Lg0KDQotW1BhZ2UgOV0sIGxhc3QgcGFyYWdyYXBoLCAy
bmQgc2VudGVuY2UsIHNvbWV0aGluZyBpcyBtaXNzaW5nIGJlZm9yZSB0aGUgbGFzdCBwaHJhc2U6
ICIuLi4sIGFwcGxpY2F0aW9uIGxldmVsIG1ldHJpY3MgdGhhdCBhcmUgcmVwb3J0ZWQgdmlhIHNv
bWUgbmV0d29yayBtYW5hZ2VtZW50IGFwcGxpY2F0aW9uIi4gDQpTdWdnZXN0aW9uLCBhZGQgImxp
a2UiOiAgIi4uLiwgbGlrZSBhcHBsaWNhdGlvbiBsZXZlbCBtZXRyaWNzIHRoYXQgYXJlIHJlcG9y
dGVkIHZpYSBzb21lIG5ldHdvcmsgbWFuYWdlbWVudCBhcHBsaWNhdGlvbiINCg0KW1Fpbl06IEFn
cmVlLCBIb3dldmVyIHdoYXQgSSBtZWFuIGhlcmUgaXMgYm90aCB0cmFuc3BvcnQgbGV2ZWwgbWV0
cmljcywgZW5kIHN5c3RlbSBtZXRyaWNzIGFuZCBhcHBsaWNhdGlvbiBsZXZlbCBtZXRyaWNzIHNo
b3VsZCBiZSBjb2xsZWN0ZWQuDQpJIGxpa2UgdG8gcmV3b3JkcyBhcyBmb2xsb3dzOg0KT0xEIFRF
WFQ6DQoiDQogICBidXQgaW5zdGVhZA0KICAgY29sbGVjdCB0cmFuc3BvcnQgYW5kIGVuZCBzeXN0
ZW0gbWV0cmljcywgYXBwbGljYXRpb24gbGV2ZWwgbWV0cmljcw0KICAgdGhhdCBhcmUgcmVwb3J0
ZWQgdmlhIHNvbWUgbmV0d29yayBtYW5hZ2VtZW50IGFwcGxpY2F0aW9uLiANCiINCk5FVyBURVhU
Og0KIg0KYnV0IGluc3RlYWQgY29sbGVjdCB0cmFuc3BvcnQgbGV2ZWwgbWV0cmljcywgZW5kIHN5
c3RlbSBtZXRyaWNzIGFuZCBhcHBsaWNhdGlvbiBsZXZlbCBtZXRyaWNzLiANCiINCg0KLVtQYWdl
IDEwXSwgU2VjdGlvbiA0LjIsIHR5cG86ICJ0aW1seSItLS0tPiJ0aW1lbHkiDQoNCltRaW5dOiBP
a2F5Lg0KDQotW1BhZ2UgMTBdIGFuZCBbUGFnZSAxM10sICJWT0lQIiAtLS0tLS0+IlZvSVAiIGZv
ciBjb25zaXN0ZW5jeS4NCg0KW1Fpbl06IE9rYXkuDQoNCi1bUGFnZSAxM10sIFNlY3Rpb24gNS4z
LCAidXNlcyB0aGUgU1NSQyBvZiBzb3VyY2UgdG8gYmluZCAiOiB3b3VsZCB0aGUgd29yZGluZyAi
dXNlcyB0aGUgU1NSQyB0byBiaW5kIiBiZSBlbm91Z2g/DQoNCltRaW5dOiBPa2F5Lg0KDQotW1Bh
Z2UgMTNdLCBTZWN0aW9uIDUuMywgInRoZW4gZm9yd2FyZCItLS0tPiJ0aGVuIGZvcndhcmRzIg0K
DQpbUWluXTogT2theS4NCg0KLVtQYWdlIDEzXSwgU2VjdGlvbiA1LjQsIHBsZWFzZSByZW1vdmUg
ZXh0cmEgXCIgYWZ0ZXIgIlhSIEJsb2NrIg0KDQpbUWluXTogQXBwYXJlbnRseSBpdCBpcyBhIHR5
cG8uIEkgZm9yZ290IHRvIGFkZCBsZWZ0IHF1b3RhdGlvbiBtYXJrcy4NCk9MRCBURVhUDQoiDQpN
ZWFzdXJlbWVudCBJZGVudGl0eSBhbmQgaW5mb3JtYXRpb24gUmVwb3J0aW5nIHVzaW5nIFNERVMg
aXRlbSBhbmQgWFIgQmxvY2siIFtNRUFTSV0NCiINCk5FVyBURVhUOg0KIg0KIk1lYXN1cmVtZW50
IElkZW50aXR5IGFuZCBpbmZvcm1hdGlvbiBSZXBvcnRpbmcgdXNpbmcgU0RFUyBpdGVtIGFuZCBY
UiBCbG9jayIgW01FQVNJXSANCg0KIg0KDQotW1BhZ2UgMTVdLCBsaW5lIDMsICJTZWN0aW9uIDUu
MSIsIHNob3VsZCBpdCBzYXkgIlNlY3Rpb24gNSIgPw0KDQpbUWluXTogT2theS4NCg0KLVtQYWdl
IDIxXSwgZm9yIFJlZmVyZW5jZXMgdG8gb25nb2luZyBkcmFmdHMsIHBsZWFzZSBjb25zaWRlciBu
b3QgcG9pbnRpbmcgdG8gc3BlY2lmaWMgdmVyc2lvbnMgaWYgbm90IG5lZWRlZCwgb3IgdXNlIGxh
dGVzdCByZXZpc2lvbnM6DQpleDogICJbUU9FXSIsIHBvaW50IHRvIGh0dHA6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LWlldGYteHJibG9jay1ydGNwLXhyLXFvZSAgKHYwMikuDQphbmQgIltN
RUFTSV0iLCBwb2ludCB0byBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXhy
YmxvY2stcnRjcC14ci1tZWFzLWlkZW50aXR5ICh2MDkpLg0KDQpbUWluXTogT2theS4NCg0KLSBP
dmVyYWxsLCBzdWdnZXN0aW9uOiAgRmlyc3QgbGV2ZWwgaGVhZGluZ3MsIGFsbCB3b3JkcyBzdGFy
dCBieSBDYXBzLg0KDQpbUWluXTogT2theS4NCg0KDQpUaGFua3MsDQpNZXJhbA0KDQotLS0NCk1l
cmFsIFNoaXJhemlwb3VyDQpFcmljc3Nvbg0KUmVzZWFyY2gNCnd3dy5lcmljc3Nvbi5jb20=


From bill.wu@huawei.com  Thu Aug 16 02:31:00 2012
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 4855D21F8548 for <gen-art@ietfa.amsl.com>; Thu, 16 Aug 2012 02:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.03
X-Spam-Level: 
X-Spam-Status: No, score=-4.03 tagged_above=-999 required=5 tests=[AWL=0.216,  BAYES_00=-2.599, J_CHICKENPOX_41=0.6, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G32BKPm2bwWV for <gen-art@ietfa.amsl.com>; Thu, 16 Aug 2012 02:30:59 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2A17F21F8525 for <gen-art@ietf.org>; Thu, 16 Aug 2012 02:30:59 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIX60091; Thu, 16 Aug 2012 01:30:58 -0800 (PST)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 16 Aug 2012 02:28:01 -0700
Received: from SZXEML416-HUB.china.huawei.com (10.82.67.155) by dfweml404-hub.china.huawei.com (10.193.5.203) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 16 Aug 2012 02:28:00 -0700
Received: from w53375 (10.138.41.149) by szxeml416-hub.china.huawei.com (10.82.67.155) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 16 Aug 2012 17:27:48 +0800
Message-ID: <6ECB209D04394F56BD375903055C9C90@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, <gen-art@ietf.org>
References: <500D8884.2070701@isode.com>
Date: Thu, 16 Aug 2012 17:27:46 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
Cc: shida@ntt-at.com, draft-ietf-xrblock-rtcp-xr-pdv.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-xrblock-rtcp-xr-pdv-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, 16 Aug 2012 09:31:00 -0000

SGksIEFsZXg6DQpTb3JyeSBmb3IgbGF0ZSByZXBseS4NClRoYW5rIGZvciB5b3VyIHZhbHVhYmxl
IHJldmlldy4gDQpwbGVhc2Ugc2VlIG15IGZlZWRiYWNrIGlubGluZS4NCg0KUmVnYXJkcyENCi1R
aW4NCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gDQpGcm9tOiAiQWxleGV5IE1lbG5pa292
IiA8YWxleGV5Lm1lbG5pa292QGlzb2RlLmNvbT4NClRvOiA8Z2VuLWFydEBpZXRmLm9yZz4NCkNj
OiA8ZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3AteHItcGR2LmFsbEB0b29scy5pZXRmLm9yZz4NClNl
bnQ6IFR1ZXNkYXksIEp1bHkgMjQsIDIwMTIgMToyMyBBTQ0KU3ViamVjdDogW0dlbi1hcnRdIHJl
dmlldyBvZiBkcmFmdC1pZXRmLXhyYmxvY2stcnRjcC14ci1wZHYtMDMudHh0DQoNCg0KPkkgYW0g
dGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZvciBiYWNrZ3Jv
dW5kIG9uDQo+IEdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPiA8IGh0dHA6Ly93aWtp
LnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0KPiANCj4gUGxl
YXNlIHdhaXQgZm9yIGRpcmVjdGlvbiBmcm9tIHlvdXIgZG9jdW1lbnQgc2hlcGhlcmQNCj4gb3Ig
QUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQo+IA0KPiBEb2N1
bWVudDogZHJhZnQtaWV0Zi14cmJsb2NrLXJ0Y3AteHItcGR2LTAzLnR4dA0KPiBSZXZpZXdlcjog
QWxleGV5IE1lbG5pa292DQo+IFJldmlldyBEYXRlOiAyMyBKdWx5IDIwMTINCj4gSUVURiBMQyBF
bmQgRGF0ZTogMjMgSnVseSAyMDEyDQo+IElFU0cgVGVsZWNoYXQgZGF0ZTogTi9BDQo+IA0KPiBT
dW1tYXJ5OiBBbG1vc3QgUmVhZHkNCj4gDQo+IE1ham9yIGlzc3VlczogTm9uZQ0KPiANCj4gTWlu
b3IgaXNzdWVzOg0KPiANCj4gSW4gU2VjdGlvbiA0Og0KPiANCj4gICAgICAgICBwZHZ0eXBlICAg
ICA9ICJwZHY9IiAgICAwICAgICAgOyBNQVBEVjIgSVRVLVQgRy4xMDIwDQo+ICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIC8gMSAgICAgIDsgMi1wb2ludCBQRFYgSVRVLVQgWS4xNTQwDQo+
IA0KPiBGaXJzdGx5LCBJIHRoaW5rIHlvdSBtZWFudCAiMCIgYW5kICIxIiBhYm92ZSAoeW91IGFy
ZSBtaXNzaW5nIHF1b3RlcykuIA0KDQpbUWluXTogWW91IGFyZSByaWdodC4NCg0KPiBTZWNvbmRs
eSwgdGhpcyBkb2Vzbid0IGFsbG93IGZvciBmdXR1cmUgcGR2dHlwZSByZWdpc3RyYXRpb25zLCBz
byB5b3UgDQo+IHNob3VsZCBiZSB1c2luZyBzb21ldGhpbmcgbGlrZSAxKjJESUdJVCBoZXJlICh3
aXRoIGEgY29tbWVudCB0aGF0IHZhbHVlIA0KPiAwLTE1IGFyZSB2YWxpZCksIG9yIHNvbWV0aGlu
ZyBtb3JlIHNwZWNpZmljLg0KDQpbUWluXTogT2theSxJIHByb3Bvc2UgdG8gZG8gdGhlIGZvbGxv
d2luZ2NoYW5nZToNCk9MRCBURVhUOg0KIg0KICAgICAgICAgcGR2dHlwZSAgICAgPSAicGR2PSIg
ICAgMCAgICAgIDsgTUFQRFYyIElUVS1UIEcuMTAyMA0KICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIC8gMSAgICAgIDsgMi1wb2ludCBQRFYgSVRVLVQgWS4xNTQwDQoNCiINCk5FVyBURVhU
Og0KIg0KICAgICAgICBwZHZ0eXBlICAgICA9ICJwZHY9IiAgIjAiICAgICAgOyBNQVBEVjIgSVRV
LVQgRy4xMDIwDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIC8gIjEiICAgICA7IDIt
cG9pbnQgUERWIElUVS1UIFkuMTU0MA0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAv
MSoyRElHSVQgICAgO1ZhbHVlIDJ+MTUgYXJlIHZhbGlkDQoNCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICA7IGFuZCByZXNlcnZlZCBmb3IgZnV0dXJlDQoNCiAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA7IHVzZS4NCg0KIg0KPiANCj4g
VGhlIGRvY3VtZW50IGNyZWF0ZXMgYSBuZXcgcmVnaXN0cnkgd2l0aCAiU3BlY2lmaWNhdGlvbiBS
ZXF1aXJlZCIsIHlldCANCj4gdGhlIHNoZXBoZXJkaW5nIHdyaXRlLXVwIHNheXMgdGhhdCB0aGUg
ZG9jdW1lbnQgZG9lc24ndCBjcmVhdGUgYW55IA0KPiByZWdpc3RyeSB3aXRoIEV4cGVydCBSZXZp
ZXcgKHF1ZXN0aW9uIDE4KS4gU28gb25lIG9mIHRoZSB0d28gaXMgDQo+IGluY29ycmVjdCwgSSBk
b24ndCBrbm93IHdoaWNoIG9uZS4NCg0KW1Fpbl06IE15IHVuZGVyc3RhbmRpbmcgaXMgdGhlIGZv
cm1lci4NCg0KPiBOaXRzL2VkaXRvcmlhbCBjb21tZW50czogTm9uZQ0KPg==


From mahoney@nostrum.com  Thu Aug 16 14:45:43 2012
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 33A1C21F84D2 for <gen-art@ietfa.amsl.com>; Thu, 16 Aug 2012 14:45:43 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h3OyfWaddA4m for <gen-art@ietfa.amsl.com>; Thu, 16 Aug 2012 14:45:42 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id A45B421F84C4 for <gen-art@ietf.org>; Thu, 16 Aug 2012 14:45:42 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-102-202.dllstx.fios.verizon.net [173.57.102.202]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7GLjVvI081994 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 16 Aug 2012 16:45:37 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <502D69FB.4010103@nostrum.com>
Date: Thu, 16 Aug 2012 16:45:31 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
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 (nostrum.com: 173.57.102.202 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-08-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: Thu, 16 Aug 2012 21:45:43 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Mary Barnes       2012-08-24    draft-ietf-dnsop-rfc4641bis-12

Martin Thomson    2012-08-24    draft-ietf-pce-hierarchy-fwk-04

Peter McCann      2012-08-27    draft-ietf-v6ops-wireline-incremental-ipv6-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 meral.shirazipour@ericsson.com  Thu Aug 16 22:35:33 2012
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 C8DCC21F846C for <gen-art@ietfa.amsl.com>; Thu, 16 Aug 2012 22:35:33 -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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bc454yh2Imwy for <gen-art@ietfa.amsl.com>; Thu, 16 Aug 2012 22:35:32 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6ADFB21F8467 for <gen-art@ietf.org>; Thu, 16 Aug 2012 22:35:28 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q7H5ZKAa022708 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 17 Aug 2012 00:35:25 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.135]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Fri, 17 Aug 2012 01:35:19 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: Qin Wu <bill.wu@huawei.com>, "draft-ietf-avtcore-monarch.all@tools.ietf.org" <draft-ietf-avtcore-monarch.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Fri, 17 Aug 2012 01:32:36 -0400
Thread-Topic: Gen-ART Last Call review of draft-ietf-avtcore-monarch-17
Thread-Index: Ac17a744XiUw/IuESYKo983uMG+U4QAzfcze
Message-ID: <25DC600D0CC1F2479C7053ADEB93004E6C4E529B49@EUSAACMS0703.eamcs.ericsson.se>
References: <25DC600D0CC1F2479C7053ADEB93004E6C4E675DA7@EUSAACMS0703.eamcs.ericsson.se>, <C0D04E3710A04C6C8327E441D34CFFFC@china.huawei.com>
In-Reply-To: <C0D04E3710A04C6C8327E441D34CFFFC@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-avtcore-monarch-17
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, 17 Aug 2012 05:35:33 -0000

Hi Qin,
   thank you, I agree with your comments.

Best Regards,
Meral

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

________________________________________
From: Qin Wu [bill.wu@huawei.com]
Sent: Thursday, August 16, 2012 12:57 AM
To: Meral Shirazipour; draft-ietf-avtcore-monarch.all@tools.ietf.org; gen-a=
rt@ietf.org
Subject: Re: Gen-ART Last Call review of draft-ietf-avtcore-monarch-17

HI,Meral:
Sorry for late, please see my replies inline below.

Regards!
-Qin
----- Original Message -----
From: "Meral Shirazipour" <meral.shirazipour@ericsson.com>
To: <draft-ietf-avtcore-monarch.all@tools.ietf.org>; <gen-art@ietf.org>
Sent: Wednesday, August 01, 2012 10:02 AM
Subject: Gen-ART Last Call review of draft-ietf-avtcore-monarch-17


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

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

Document: draft-ietf-avtcore-monarch-17
Reviewer: Meral Shirazipour
Review Date: 2012-07-31
IETF LC End Date: 2012-08-02
IESG Telechat date: 2012-08-16



Summary:
This draft is almost ready to be published as Informational RFC but I have =
some comments.



Nits/editorial comments:

-[Page 5], in the definition of "Transport level metrics", suggestion: plea=
se clarify "packet delay variation", as done in Section 6.
 ex.: "packet delay variation" ----->"packet delay variation (PDV) which co=
uld be jitter or another metric".

[Qin]: I prefer to reference to RFC5481 "Packet Delay Variation Problem sta=
tement" and propose the following change:
"packet delay variation" ------> "packet delay variation which is sometimes=
 called jitter [RFC5481]"

-[Page 5],in the definition of "Application level metrics", "end-to-end" --=
-->"end to end"  (Note: the rest of the document uses end to end).

[Qin]: Okay.

-[Page 5],in the definition of "Application level metrics", typo: "ususally=
"---->"usually"

[Qin]: Good catch, thanks.

-[Page 7], Section 3, "SIP", first occurrence of the word. Suggestion: plea=
se spell out "Session Initiation Protocol (SIP)"

[Qin]: Okay.

-[Page 7], Section 3.1, suggestion: "shown below"----->"described below", s=
ince Figure 1 is on another page, "describe below" is more suitable than "s=
hown".

[Qin]: Okay.

-[Page 7], Section 3.1, right after two bullets, suggestion: "RTP Monitor"-=
---->"RTP monitor", since monitor is small caps throughout the rest of the =
document.

[Qin]: Okay.

-[Page 8], 5 line before last, "see figure 1"---->"see Figure 1"

[Qin]: Okay.

-[Page 9], Section 3.2 first line, "shown in the Figure 1"---->"shown in Fi=
gure 1"

[Qin]: Okay.

-[Page 9], Section 3.2 line 2, and line 1 of second paragraph, suggestion: =
"end-systems"---->"end systems", for consistency with the rest of the docum=
ent.

[Qin]: Okay.

-[Page 9], Section 3.2 3rd paragraph, "MCUs", first occurrence of the word.=
 Suggestion: please spell out "Multipoint Control Units (MCUs)".

[Qin]: Okay.

-[Page 9], Section 3.2 3rd paragraph, "SSRC", first occurrence of the word.=
 Suggestion: please spell out "Synchronization source (SSRC)";
then [Page 10],"Synchronization source (SSRC)" does not need to be spelled =
out a second time.

[Qin]: Okay.

-[Page 9], last paragraph, 2nd sentence, something is missing before the la=
st phrase: "..., application level metrics that are reported via some netwo=
rk management application".
Suggestion, add "like":  "..., like application level metrics that are repo=
rted via some network management application"

[Qin]: Agree, However what I mean here is both transport level metrics, end=
 system metrics and application level metrics should be collected.
I like to rewords as follows:
OLD TEXT:
"
   but instead
   collect transport and end system metrics, application level metrics
   that are reported via some network management application.
"
NEW TEXT:
"
but instead collect transport level metrics, end system metrics and applica=
tion level metrics.
"

-[Page 10], Section 4.2, typo: "timly"---->"timely"

[Qin]: Okay.

-[Page 10] and [Page 13], "VOIP" ------>"VoIP" for consistency.

[Qin]: Okay.

-[Page 13], Section 5.3, "uses the SSRC of source to bind ": would the word=
ing "uses the SSRC to bind" be enough?

[Qin]: Okay.

-[Page 13], Section 5.3, "then forward"---->"then forwards"

[Qin]: Okay.

-[Page 13], Section 5.4, please remove extra \" after "XR Block"

[Qin]: Apparently it is a typo. I forgot to add left quotation marks.
OLD TEXT
"
Measurement Identity and information Reporting using SDES item and XR Block=
" [MEASI]
"
NEW TEXT:
"
"Measurement Identity and information Reporting using SDES item and XR Bloc=
k" [MEASI]

"

-[Page 15], line 3, "Section 5.1", should it say "Section 5" ?

[Qin]: Okay.

-[Page 21], for References to ongoing drafts, please consider not pointing =
to specific versions if not needed, or use latest revisions:
ex:  "[QOE]", point to http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-x=
r-qoe  (v02).
and "[MEASI]", point to http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-=
xr-meas-identity (v09).

[Qin]: Okay.

- Overall, suggestion:  First level headings, all words start by Caps.

[Qin]: Okay.


Thanks,
Meral

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

From touch@isi.edu  Fri Aug 17 03:16:13 2012
Return-Path: <touch@isi.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 BF60E21F8473; Fri, 17 Aug 2012 03:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.493
X-Spam-Level: 
X-Spam-Status: No, score=-105.493 tagged_above=-999 required=5 tests=[AWL=1.106, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AKdD2r67lqFa; Fri, 17 Aug 2012 03:16:13 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 2107021F8467; Fri, 17 Aug 2012 03:16:13 -0700 (PDT)
Received: from [128.9.176.217] (c2-vpn05.isi.edu [128.9.176.217]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q7HAFR8H023548 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 17 Aug 2012 03:15:29 -0700 (PDT)
Message-ID: <502E19BB.2020101@isi.edu>
Date: Fri, 17 Aug 2012 03:15:23 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: philip.eardley@bt.com
References: <CCBAA297-B839-4AEA-BB24-F4D320200415@nostrum.com> <9510D26531EF184D9017DF24659BB87F33D6B96847@EMV65-UKRD.domain1.systemhost.net>
In-Reply-To: <9510D26531EF184D9017DF24659BB87F33D6B96847@EMV65-UKRD.domain1.systemhost.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Mailman-Approved-At: Fri, 17 Aug 2012 04:59:03 -0700
Cc: ben@nostrum.com, gen-art@ietf.org, draft-ietf-mptcp-api.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-mptcp-api-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, 17 Aug 2012 10:16:13 -0000

On 8/13/2012 7:14 AM, philip.eardley@bt.com wrote:
> Ben,
> Thanks for your review.
>
> The right status isn't clear-cut (I think), but when we (Chairs & Wes) discussed it, Info seemed best
> * mainly because precedent seems to be that API docs are informational, for example socket API extensions for SCTP http://datatracker.ietf.org/doc/rfc6458/

This has been a big mistake in the past, IMO.

A key part of the definition of any protocol is its API. It is exactly 
as important as the "on the wire" component and the endpoint state and 
semantics of message exchanges.

See RFC793 for a great example. What we know as sockets there is 
basically a direct implementation of the *specified* API for TCP.

I can't argue that this document is a reason for the IETF to correct its 
past mistake, but the sooner it does the better. APIs ought to be a 
*mandatory* part of any protocol specification. As such, they should be 
at the same level as any other part of that spec (e.g.., standards track 
or experimental).

Joe

From mahoney@nostrum.com  Fri Aug 17 07:23:23 2012
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 7F58521E804C for <gen-art@ietfa.amsl.com>; Fri, 17 Aug 2012 07:23:23 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t7Rhsc8z-TPC for <gen-art@ietfa.amsl.com>; Fri, 17 Aug 2012 07:23:23 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id F06AF21E8045 for <gen-art@ietf.org>; Fri, 17 Aug 2012 07:23:22 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-102-202.dllstx.fios.verizon.net [173.57.102.202]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7HENKnM077903 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Fri, 17 Aug 2012 09:23:22 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <502E53D8.50809@nostrum.com>
Date: Fri, 17 Aug 2012 09:23:20 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
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 (nostrum.com: 173.57.102.202 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-08-17
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, 17 Aug 2012 14:23:23 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Peter Yee         2012-08-29    draft-ietf-ccamp-assoc-ext-04

Richard Barnes    2012-08-29    draft-ietf-eai-mailinglistbis-05

Roni Even         2012-08-29    draft-ietf-sieve-imap-sieve-06



Since the documents have not appeared in the review tool, I have NOT 
made assignments there.
I'll let you know when they become available.

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 acmorton@att.com  Mon Aug 20 07:33:37 2012
Return-Path: <acmorton@att.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 A43AC21F86A1 for <gen-art@ietfa.amsl.com>; Mon, 20 Aug 2012 07:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.893
X-Spam-Level: 
X-Spam-Status: No, score=-104.893 tagged_above=-999 required=5 tests=[AWL=-0.555, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7NOIBbcFJqD for <gen-art@ietfa.amsl.com>; Mon, 20 Aug 2012 07:33:35 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 50D8B21F847D for <gen-art@ietf.org>; Mon, 20 Aug 2012 07:33:35 -0700 (PDT)
Received: from unknown [144.160.128.153] (EHLO flpi408.enaf.ffdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id eba42305.0.249631.00-388.626199.nbfkord-smmo06.seg.att.com (envelope-from <acmorton@att.com>);  Mon, 20 Aug 2012 14:33:35 +0000 (UTC)
X-MXL-Hash: 50324abf61828353-8c9437222db60c6f79d5f29ebe0b39535a571ebd
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q7KEXYiD006405 for <gen-art@ietf.org>; Mon, 20 Aug 2012 07:33:34 -0700
Received: from fflint03.pst.cso.att.com (fflint03.pst.cso.att.com [150.234.39.63]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q7KEXKMb006225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Mon, 20 Aug 2012 07:33:29 -0700
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by fflint03.pst.cso.att.com (RSA Interceptor) for <gen-art@ietf.org>; Mon, 20 Aug 2012 07:33:04 -0700
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q7KEX3MI029565 for <gen-art@ietf.org>; Mon, 20 Aug 2012 10:33:03 -0400
Received: from dns.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q7KEWoNA028465 for <gen-art@ietf.org>; Mon, 20 Aug 2012 10:32:58 -0400
Message-Id: <201208201432.q7KEWoNA028465@alpd052.aldc.att.com>
Received: from acmt.att.com (vpn-135-70-160-158.vpn.mwst.att.com[135.70.160.158](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120820142800gw100ssp3ke>; Mon, 20 Aug 2012 14:28:01 +0000
X-Originating-IP: [135.70.160.158]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 20 Aug 2012 10:32:02 -0400
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, draft-ietf-ippm-testplan-rfc2679.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
From: Al Morton <acmorton@att.com>
In-Reply-To: <5023C0BC.5040605@gmail.com>
References: <5023C0BC.5040605@gmail.com>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.128.153]
X-AnalysisOut: [v=1.0 c=1 a=j1jovreD4JoA:10 a=C4kiKLETGy4A:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=i-EZtwj-LTsA:1]
X-AnalysisOut: [0 a=xwOvzTHDVLE4u4nGvK72ag==:17 a=u1_Fr5k3-5mCXBYluqkA:9 a]
X-AnalysisOut: [=CjuIK1q_8ugA:10 a=_W_S_7VecoQA:10]
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-ippm-testplan-rfc2679-02.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, 20 Aug 2012 14:33:37 -0000

<html>
<body>
At 09:53 AM 8/9/2012, Brian E Carpenter
wrote:<blockquote type=cite class=cite cite="">
<dl>
<dd>Please see attached review.
</dl></blockquote>Hi Brian,<br><br>
Thanks for your review and comments. I've added a conclusion<br>
section and addressed other nits.<br><br>
Your point on Errata: important to ensure they are evaluated.<br>
We should submit an Erratum on RFC 6576 to identify<br>
and evaluate Errata.<br><br>
Al (for the co-authors)<br>
</body>
</html>


From mahoney@nostrum.com  Mon Aug 20 14:30:11 2012
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 80B2C21F859F for <gen-art@ietfa.amsl.com>; Mon, 20 Aug 2012 14:30:11 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HpD39QvAgj5C for <gen-art@ietfa.amsl.com>; Mon, 20 Aug 2012 14:30:11 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id F25B421F8541 for <gen-art@ietf.org>; Mon, 20 Aug 2012 14:30:10 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([4.30.77.1]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7KLU6LP029814 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Mon, 20 Aug 2012 16:30:10 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <5032AC5E.3090902@nostrum.com>
Date: Mon, 20 Aug 2012 16:30:06 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: gen-art@ietf.org
References: <502E53D8.50809@nostrum.com>
In-Reply-To: <502E53D8.50809@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Subject: Re: [Gen-art] A *new* batch of IETF LC reviews - 2012-08-17
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, 20 Aug 2012 21:30:11 -0000

Hi all,

This set of assignments is now available in the review tool:
http://art.tools.ietf.org/tools/art/genart/

Jean


On 8/17/12 9:23 AM, A. Jean Mahoney wrote:
> Hi all,
>
> The following reviewers have assignments:
>
> Reviewer          LC end        Draft
>
> Peter Yee         2012-08-29    draft-ietf-ccamp-assoc-ext-04
>
> Richard Barnes    2012-08-29    draft-ietf-eai-mailinglistbis-05
>
> Roni Even         2012-08-29    draft-ietf-sieve-imap-sieve-06
>
>
>
> Since the documents have not appeared in the review tool, I have NOT 
> made assignments there.
> I'll let you know when they become available.
>
> 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:
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From david.black@emc.com  Mon Aug 20 18:58:09 2012
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 DF8F121F84A2; Mon, 20 Aug 2012 18:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.49
X-Spam-Level: 
X-Spam-Status: No, score=-102.49 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KGC+ce3XGNYy; Mon, 20 Aug 2012 18:58:09 -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 2C00821F84A1; Mon, 20 Aug 2012 18:58:08 -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 q7L1w39m000583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Aug 2012 21:58:05 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 20 Aug 2012 21:57:47 -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 q7L1vkwO021339; Mon, 20 Aug 2012 21:57:47 -0400
Received: from mx15a.corp.emc.com ([169.254.1.66]) by mxhub23.corp.emc.com ([128.222.70.135]) with mapi; Mon, 20 Aug 2012 21:57:46 -0400
From: "Black, David" <david.black@emc.com>
To: "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "nabil.n.bitar@verizon.com" <nabil.n.bitar@verizon.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Content-Class: urn:content-classes:message
Date: Mon, 20 Aug 2012 21:57:44 -0400
Thread-Topic: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Index: Ac1/QFqQF9gPSsZLRYeNSY3JGwq32g==
Message-ID: <7EB1738E-2545-4A33-B5C0-548630347568@mimectl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mimectl: Produced By Microsoft Exchange V8.3.105.0
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7EB1738E25454A33B5C0548630347568mimectl_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-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, 21 Aug 2012 01:58:10 -0000

--_000_7EB1738E25454A33B5C0548630347568mimectl_
Content-Type: text/plain; charset="iso-8859-1"
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/GenArtfaq>.

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

Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
Reviewer: David L. Black
Review Date: August 20, 2012
IETF LC End Date: August 20, 2012

Summary:
This draft is basically ready for publication, but has nits that
should be fixed before publication.



This draft covers defect behavior for Ethernet pseudowires,

including defect state mapping and PE defect reporting behavior.

The draft is generally in good shape.  I found a few minor nits.



1) The draft uses a lot of acronyms - while each acronym appears to

be expanded on first use, an additional section near the start of the

draft listing all of them would be helpful.



2) There's a typo in the first paragraph of section 2:



     covers the following Ethernet OAM (Opertaions, Administration and



Opertaions -> Operations.



3) The following normative reference is incomplete - please add additional

information that will enable a reader to locate the referenced document:



     [MEF16] "Ethernet Local Management Interface", MEF16, January 2006.



4) idnits 2.12.13 did not like the pagination:



  =3D=3D The page length should not exceed 58 lines per page, but there was=
 22
     longer pages, the longest (page 1) being 61 lines


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<mailto:david.black@emc.com>        Mobile: +1 (978) 394=
-7754
----------------------------------------------------

--_000_7EB1738E25454A33B5C0548630347568mimectl_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD>
<STYLE title=3DowaParaStyle><!--P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></STYLE>
</HEAD>
<BODY ocsi=3D"x">
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3D"Courier New">I am the=
 assigned Gen-ART reviewer for this draft. For background on Gen-ART, pleas=
e<BR>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/w=
iki/GenArtfaq</A>&gt;.<BR><BR>Please resolve these comments along with any =
other Last Call comments you may receive.<BR><BR>Document: <SPAN lang=3DEN>=
draft-ietf-pwe3-mpls-eth-oam-iwk-06</SPAN></FONT></DIV>
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2 face=3D"Courier New"><SPAN la=
ng=3DEN></SPAN>Reviewer: David L. Black<BR>Review Date: August 20, 2012<BR>=
IETF LC End Date: August 20, 2012<BR><BR>Summary:<BR>This draft is basicall=
y ready for publication, but has nits that<BR>should be fixed before public=
ation.</FONT></DIV>
<P><FONT color=3D#000000 size=3D2 face=3D"Courier New"><FONT face=3D"courie=
r new"></FONT></FONT>&nbsp;</P>
<P><FONT color=3D#000000 size=3D2 face=3D"Courier New"><FONT face=3D"courie=
r new">This draft covers defect behavior for Ethernet pseudowires<A target=
=3D_blank></A>,</FONT></FONT></P>
<P><FONT color=3D#000000 size=3D2 face=3D"Courier New"><FONT face=3D"courie=
r new">including defect state mapping and PE defect reporting behavior.</FO=
NT></FONT></P>
<P><FONT color=3D#000000 size=3D2 face=3D"Courier New"><FONT face=3D"courie=
r new">The draft is generally in good shape.&nbsp; I found a few minor nits=
.</FONT></FONT></P>
<P><FONT size=3D2 face=3D"courier new"></FONT>&nbsp;</P>
<P><FONT size=3D2 face=3D"courier new">1) The draft uses a lot of acronyms =
- while each acronym appears to</FONT></P>
<P><FONT size=3D2 face=3D"Courier New">b<FONT face=3D"courier new">e expand=
ed on first use, an additional section near the start of the</FONT></FONT><=
/P>
<P><FONT face=3D"Courier New"><FONT face=3D"courier new"><FONT size=3D2><FO=
NT face=3D"courier new">draft listing</FONT> all of them </FONT></FONT></FO=
NT><FONT size=3D2 face=3D"courier new">would be helpful.</FONT></P>
<P><FONT size=3D2 face=3D"courier new"></FONT>&nbsp;</P>
<P><FONT size=3D2 face=3D"courier new">2) There's&nbsp;a typo in the first =
paragraph of section 2:</FONT></P>
<P><FONT size=3D2 face=3D"courier new"></FONT>&nbsp;</P><FONT color=3D#0000=
00>
<DIV dir=3Dltr><FONT size=3D2><SPAN lang=3DEN>
<P><FONT face=3D"Courier New">&nbsp;&nbsp;&nbsp; &nbsp;covers the following=
 Ethernet OAM (Opertaions<A target=3D_blank></A>, Administration and </FONT=
></P>
<P><FONT face=3D"courier new"></FONT>&nbsp;</P>
<P><FONT face=3D"courier new"><A target=3D_blank></A><FONT face=3D"courier =
new">Opertaions</FONT>&nbsp;-&gt; Operations.</FONT></P>
<P><FONT face=3D"courier new"></FONT>&nbsp;</P>
<P><FONT face=3D"courier new">3) The following normative reference is incom=
plete - please add additional</FONT></P>
<P><FONT face=3D"courier new">information that will enable a reader to loca=
te the referenced document:</FONT></P>
<P><FONT face=3D"courier new"></FONT>&nbsp;</P><FONT face=3D"courier new"><=
SPAN lang=3DEN>
<P>&nbsp;&nbsp;&nbsp; &nbsp;[MEF16] "Ethernet Local Management Interface", =
MEF16, January 2006.</P>
<P><FONT face=3D"courier new"></FONT>&nbsp;</P>
<P><FONT face=3D"courier new"><FONT face=3D"courier new">4)&nbsp;idnits<A t=
arget=3D_blank></A> 2.12.13 did not like the pagination:</FONT></FONT></P>
<P>&nbsp;</P>
<P><FONT face=3D"courier new">&nbsp; =3D=3D The page length should not exce=
ed 58 lines per page, but there was 22<BR>&nbsp;&nbsp;&nbsp;&nbsp; longer p=
ages, the longest (page 1) being 61 lines</FONT></SPAN></FONT></SPAN></FONT=
></P></DIV></FONT>
<DIV dir=3Dltr><FONT face=3D"Courier New"><FONT color=3D#000000 size=3D2>&n=
bsp;</DIV></FONT></FONT>
<DIV><FONT size=3D2 face=3D"Courier New">Thanks,</FONT></DIV>
<DIV><FONT size=3D2 face=3D"courier new">--David</FONT></DIV>
<DIV><FONT face=3D"Courier New"><FONT size=3D2>----------------------------=
------------------------<BR>David L. Black, Distinguished Engineer<BR>EMC C=
orporation, 176 South St., Hopkinton, MA&nbsp; 01748<BR>+1 (508) 293-7953&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FAX:=
 +1 (508) 293-7786<BR></FONT><FONT size=3D2><A href=3D"mailto:david.black@e=
mc.com" target=3D_blank><FONT size=3D2>david.black@emc.com</FONT></A><A tar=
get=3D_blank></A></FONT><FONT size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; Mobile: +1 (978) 394-7754<BR>---------------------------------------=
-------------<BR></FONT></DIV></FONT></BODY></HTML>

--_000_7EB1738E25454A33B5C0548630347568mimectl_--

From christer.holmberg@ericsson.com  Thu Aug 23 02:53:44 2012
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 C2C7521F85B4 for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 02:53:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.171
X-Spam-Level: 
X-Spam-Status: No, score=-6.171 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhnF0U5IueDt for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 02:53:44 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id EE29B21F85AC for <gen-art@ietf.org>; Thu, 23 Aug 2012 02:53:43 -0700 (PDT)
X-AuditID: c1b4fb25-b7f046d00000644c-9a-5035fda60b2f
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id E1.C6.25676.6ADF5305; Thu, 23 Aug 2012 11:53:42 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.99]) by esessmw0256.eemea.ericsson.se ([153.88.115.96]) with mapi; Thu, 23 Aug 2012 11:53:42 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-kumaki-murai-l3vpn-rsvp-te.all@tools.ietf.org" <draft-kumaki-murai-l3vpn-rsvp-te.all@tools.ietf.org>
Date: Thu, 23 Aug 2012 11:53:40 +0200
Thread-Topic: GenART LC review of draft-kumaki-murai-l3vpn-rsvp-te-06
Thread-Index: AQHNgRUs6Go/rR1j7UKDzJisgXmlxQ==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05853409FF2EFC@ESESSCMS0356.eemea.ericsson.se>
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-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCLMWRmVeSWpSXmKPExsUyM+Jvre6yv6YBBidfi1jcO1llcfXVZxYH Jo8lS34yeXy5/JktgCmKyyYlNSezLLVI3y6BK+P2tt3sBQdZKmZ//cTWwHiEuYuRk0NCwETi 9OKJrBC2mMSFe+vZuhi5OIQETjFKLJ+wlhHCWcAo8fbFF6AODg42AQuJ7n/aIHERgVmMEpcv vWcH6WYRUJXYMHMT2CRhAQeJxX//MoHYIgKuEgf3rGSDsPUktr1dA1bPKxAu8fJbHwuIzQi0 +fupNWD1zALiEreezGeCuEhAYsme81CXikq8fPyPFaJeVOJO+3pGiHo9iRtTp7BB2NoSyxa+ ZoaYLyhxcuYTlgmMwrOQjJ2FpGUWkpZZSFoWMLKsYhTOTczMSS830kstykwuLs7P0ytO3cQI DPmDW36r7mC8c07kEKM0B4uSOK/11j3+QgLpiSWp2ampBalF8UWlOanFhxiZODilGhhLlxXY sYdMUJ+/s/FY547z0nvlwjNfT1nhXR7nvKo2SXP+ZOGsFcblVkFxXs6BWnyzfnjPXBNwa552 h9i2KdLrWovnW0ffNZZKeRxqcjtG9zLvquz2vYu3rwhN4//UqKxX4sxkkr6HYy3DzJdeDzLs ZvP6LnrsoX5jNs/bzUtC1hXXRcz9tlqJpTgj0VCLuag4EQDgKh3JRwIAAA==
Subject: [Gen-art] GenART LC review of draft-kumaki-murai-l3vpn-rsvp-te-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, 23 Aug 2012 09:53:44 -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-kumaki-murai-l3vpn-rsvp-te-06
Reviewer:             Christer Holmberg
Review Date:        2012-08-23
IETF LC End Date: 2012-09-03
IESG Telechat date:

Summary: The document is well written, and is ready for publication.

Major issues: -

Minor issues: -

Nits/editorial comments: -

From ron.even.tlv@gmail.com  Thu Aug 23 03:34:25 2012
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 2C40121F8602; Thu, 23 Aug 2012 03:34:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JpeF6yGdxZ4p; Thu, 23 Aug 2012 03:34:24 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id BBBF421F85F7; Thu, 23 Aug 2012 03:34:23 -0700 (PDT)
Received: by bkty7 with SMTP id y7so183836bkt.31 for <multiple recipients>; Thu, 23 Aug 2012 03:34:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=1mgzAF5M7NuPvCTEFBC9S+8BIUd5rwac0BXE9UXOQ5E=; b=NL0RHNFGW9Qq0aILhQ1oxIG4GcIlkQPkBZrnYY7dCMyA2EZe/GxoCGR/r/BnM/YHnx rZgA8y/AANUYl6DVGlsjjPjMObtZRqNBzqoWuqy5Ebuo48LAIX2e5I9fBs0HVs1AZooz xLP3AfJ8IfKHj5rwsb8hl1uR/qHrriHteSpjtI5m1L8JFQ2C8XZpWcaAw/RlEyRZNj+w 8DTiimOpB7WVtHM+j6k3Xnh2Xb1BvDE6BVnmhQFSMGTBGzJM9K+20BtOWHzCwRGFhjrr hXNJkrTF2lv8WfsTfh/ScPSzssfvV7jZ1y7L8puQnAZXmQeINqkW/i40ZV53Js7k0+Np zCJg==
Received: by 10.205.130.17 with SMTP id hk17mr276618bkc.76.1345718062402; Thu, 23 Aug 2012 03:34:22 -0700 (PDT)
Received: from RoniE ([109.64.216.128]) by mx.google.com with ESMTPS id he8sm4306646bkc.3.2012.08.23.03.34.19 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 23 Aug 2012 03:34:21 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-sieve-imap-sieve.all@tools.ietf.org>
Date: Thu, 23 Aug 2012 13:33:01 +0200
Message-ID: <001501cd8123$0fe75630$2fb60290$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01CD8133.D37137A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2BIwFyV1CLj99kQJaJLAKEzhv3Qg==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-sieve-imap-sieve-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, 23 Aug 2012 10:34:25 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0016_01CD8133.D37137A0
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-sieve-imap-sieve-06

Reviewer: Roni Even

Review Date:2012-8-22

IETF LC End Date: 2012-8-29

IESG Telechat date:

 

Summary: This draft is ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

 

1.       At the end of section 3.7 and 3.8 "acton" "should be "action"

 


------=_NextPart_000_0016_01CD8133.D37137A0
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.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:117648904;
	mso-list-type:hybrid;
	mso-list-template-ids:651336890 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><o:p>&nbsp;</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"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document</s=
pan><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>: =
draft-ietf-sieve-imap-sieve-06</span><span style=3D'font-family:"Courier =
New"'><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:2012&#8211;8&#8211;22<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: 2012&#8211;8&#8211;29<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</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> a =
standard track </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>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=3DMsoNormal><o:p>&nbsp;</o:p></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"'>Nits/editor=
ial comments:<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"'>At the end =
of section 3.7 and 3.8 &#8220;acton&#8221; &#8220;should be =
&#8220;action&#8221;<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0016_01CD8133.D37137A0--


From elwynd@dial.pipex.com  Thu Aug 23 05:23:03 2012
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 DE8ED21F84E2 for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 05:23:03 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R5BB2PZHWFbz for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 05:23:03 -0700 (PDT)
Received: from 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 36A0421F84CF for <gen-art@ietf.org>; Thu, 23 Aug 2012 05:23:03 -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 1T4WR9-0006ef-Mo; Thu, 23 Aug 2012 13:23:00 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Thu, 23 Aug 2012 13:27:31 +0100
Message-Id: <1345724851.4622.5259.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-idr-as0.all@tools.ietf.org
Subject: [Gen-art] Gen-art LC review of draft-ietf-idr-as0-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: Thu, 23 Aug 2012 12:23:04 -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-idr-as0-05.txt
Reviewer: Elwyn Davies
Review Date: 22 August 2012
IETF LC End Date: 22 August 2012
IESG Telechat date: (if known) - 

Summary:
Almost ready. 

Major issues:
None.

Minor issues:
s1, para 2:
>    [RFC6491] specifies that AS number zero in a ROA is used to mark an
>    NLRI which is to be marked as Invalid.
This is not what s4 of RFC 6491 says although ultimately this is
(probably) the way in which it is intended to be used.  RFC 6491 just
says that an 'AS 0 ROA' is used to mark a prefix and all its more
specific prefixes as not to be used in a routing context.

s1, para 4:
>    As at least two implementations discard routes containing AS 0, and
>    to allow approaches such as the above, this document codifies this
>    behavior.
This sentence is not entirely clear as to what behavior is being
codified. It could be just discarding routes with AS 0 or the the use of
AS 0 to mark prefixes that shouldn't be routed.  Please make this easier
to parse.  This is partly because of the over interpretation of RFC 6491
mentioned in the previous comment.

Nits/editorial comments:
Abstract: Acronym BGP needs expanding.
s1: Acronyms ROA, AS and NLRI need expanding.
s2: It would be worth reinforcing that the behaviors being modified here
are currently specified in RFC 4271.  Arguably relevant section numbers
would help.
s4: Acronym RPKI needs expanding.
s4, para 2:
> security gotchas often lurk in the undefined spaces
This is slang and cliche that may be difficult for non-US speakers to understand. 


From barryleiba@gmail.com  Thu Aug 23 06:50:52 2012
Return-Path: <barryleiba@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 DA24221F857E for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 06:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.005
X-Spam-Level: 
X-Spam-Status: No, score=-103.005 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WVUJqY92OdHN for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 06:50:52 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 106F421F8569 for <gen-art@ietf.org>; Thu, 23 Aug 2012 06:50:51 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so900309vcb.31 for <gen-art@ietf.org>; Thu, 23 Aug 2012 06:50:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=/v06OG0HmyUgzUQJSMTdu/fa1yS64OwRusA+kRUrfTs=; b=be318SR3CLh57BxW9ZMJTGdHbJv5plBMRutb387pbXINjWN00kNtwOj/sr3DucdrAq 3qYehjmxc5NNhBwYeo8eoTrx1VIbewz7bFUwZKo1uQVBM7+tJVKc2rNBQedVU4HT4GJA n30W7Z7Mbtrq6HYSDMceUClhVJ/2wNglrWzlQCH6Ax3rDBtcE9w3jDd3frlXAjeUFW0X bE8MW0jgoWz/lSSjzdwBcwnm+QpVAf3xECGiVpYqvDRSAA2/6/a8KOc8qJgGkHpP5+8P UPWVBYowY0wJeyia/UP8955mGyU45ewtTj7XZC0U1hUFKxA9uiVZOSa2z8JI6AmSuX0T Lk8g==
MIME-Version: 1.0
Received: by 10.52.90.83 with SMTP id bu19mr219760vdb.64.1345729851389; Thu, 23 Aug 2012 06:50:51 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.58.41 with HTTP; Thu, 23 Aug 2012 06:50:51 -0700 (PDT)
In-Reply-To: <001501cd8123$0fe75630$2fb60290$@gmail.com>
References: <001501cd8123$0fe75630$2fb60290$@gmail.com>
Date: Thu, 23 Aug 2012 09:50:51 -0400
X-Google-Sender-Auth: 1oqjCAiYMB_DZpF5hcSDfz5oMVE
Message-ID: <CALaySJ+m0ZXh3iBPU8KmMOb9h+Y96nLJbGVF6wafbVOpYwORsQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Roni Even <ron.even.tlv@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: draft-ietf-sieve-imap-sieve.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-sieve-imap-sieve-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, 23 Aug 2012 13:50:53 -0000

(Removed mail IETF list.)

> Summary: This draft is ready for publication as a standard track RFC.
...
> Nits/editorial comments:
> 1.       At the end of section 3.7 and 3.8 =93acton=94 =93should be =93ac=
tion=94

Ack; thanks.  Fixed in my local copy for the next update.

Barry

From mahoney@nostrum.com  Thu Aug 23 14:29:00 2012
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 A37AD21F8513 for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 14:29:00 -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=[AWL=0.000, BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TVTf30sqb0mI for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 14:29:00 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 252E721F84F5 for <gen-art@ietf.org>; Thu, 23 Aug 2012 14:28:59 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-102-202.dllstx.fios.verizon.net [173.57.102.202]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7NLStKj058138 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 23 Aug 2012 16:28:59 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <5036A097.7010709@nostrum.com>
Date: Thu, 23 Aug 2012 16:28:55 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
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 (nostrum.com: 173.57.102.202 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-08-23
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, 23 Aug 2012 21:29:00 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Kathleen Moriarty 2012-09-04    draft-ietf-6man-lineid-08 **
  
Suresh Krishnan   2012-09-03    draft-ietf-mpls-entropy-label-05

Vijay Gurbani     2012-09-05    draft-ietf-pkix-rfc5280-clarifications-08

Wassim Haddad     2012-09-04    draft-ietf-isis-mi-06

** 2nd LC



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 Aug 23 14:29:11 2012
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 970E821F8545 for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 14:29:11 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uOFGZYBTOi64 for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 14:29:11 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id F29FD21F8532 for <gen-art@ietf.org>; Thu, 23 Aug 2012 14:29:10 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-102-202.dllstx.fios.verizon.net [173.57.102.202]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7NLTApN058162 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 23 Aug 2012 16:29:10 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <5036A0A6.7030408@nostrum.com>
Date: Thu, 23 Aug 2012 16:29:10 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
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 (nostrum.com: 173.57.102.202 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-8-30 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, 23 Aug 2012 21:29:11 -0000

Hi all,

The following reviewers have assignments:

Reviewer             LC end       Draft

Alexey Melnikov      2012-08-15   draft-ietf-ccamp-dpm-07 *

Ben Campbell         2011 -       draft-eggert-successful-bar-bof-07 *

Brian Carpenter      2012-08-14   draft-ietf-ippm-testplan-rfc2679-02 **

David Black          2012-08-09   draft-vegoda-cotton-rfc5735bis-03 *

Elwyn Davies         2012-03-20   draft-ietf-savi-dhcp-14 *

Francis Dupont       2012-08-13   draft-sparks-genarea-mailarch-06 *
Francis Dupont       2012-08-15   draft-ietf-mptcp-multiaddressed-09

Joel Halpern         2012-06-12   draft-ietf-krb-wg-kdc-model-14 *
Joel Halpern         2012-08-23   draft-ietf-armd-problem-statement-03 **

Mary Barnes          2012-08-24   draft-ietf-dnsop-rfc4641bis-12

Miguel Garcia        2012-07-11   draft-ietf-oauth-v2-threatmodel-07 *

Peter McCann         2012-07-23   draft-ietf-appsawg-http-forwarded-07 *
Peter McCann         2012-06-26   draft-ietf-bmwg-2544-as-05
Peter McCann         2012-08-27   draft-ietf-v6ops-wireline-incremental-ipv6-05

Roni Even            2012-06-13   draft-ietf-nea-pt-tls-07 *

Vijay Gurbani        2012-07-06   draft-ietf-ospf-prefix-hiding-05 **

* Earlier draft reviewed
** Already reviewed
- LC data not in the review tool since it pre-dates the use of the tool


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 martin.thomson@gmail.com  Thu Aug 23 14:35:29 2012
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 207B221F8582 for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 14:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.913
X-Spam-Level: 
X-Spam-Status: No, score=-4.913 tagged_above=-999 required=5 tests=[AWL=0.686,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29JaSFT3UO5H for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 14:35:28 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4475521F858A for <gen-art@ietf.org>; Thu, 23 Aug 2012 14:35:28 -0700 (PDT)
Received: by lbbgg6 with SMTP id gg6so769559lbb.31 for <gen-art@ietf.org>; Thu, 23 Aug 2012 14:35:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Z++toWtvjz81rM/Gkc7kChGsK4/+OBqQ06+AAFA1b64=; b=JMrxIQFfCCmchInYKsDHRJmmN7nH40D9cWAhA6SaWTxdRWJrHUSjYzJDTrRtIrBWZN wmeB1rAuIiod4RvXh8IM8nWGHnfSQwrfQAC2bfPegH8QqNrUeb7iCFkeoSjrz+oRDL92 fITTtx/bMzHG3P0aFsb9CL7PC/1gN8FIOa/bHgcWcSnPFN1svaO63Y+uD3JG+GscPYn8 J1UfbXP3c5LloVkqJh023hhciWaLkBbeH0ZJh5s3wcqQiY+O2AiHV8HK/AxO5gNQelXo eRpv9JraT9rX8O02fG98wsLTHwaaIrNJEZ9wngSqO+TeX3r+y5gNdRR0ucK9swSBZbHv k0rA==
MIME-Version: 1.0
Received: by 10.152.123.206 with SMTP id mc14mr3339527lab.33.1345757726876; Thu, 23 Aug 2012 14:35:26 -0700 (PDT)
Received: by 10.112.41.193 with HTTP; Thu, 23 Aug 2012 14:35:26 -0700 (PDT)
Date: Thu, 23 Aug 2012 14:35:26 -0700
Message-ID: <CABkgnnW_hzwPFfKRRYaPnHfTR8NC1CTEva3hKUdoyaVLRUmsnA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: draft-ietf-pce-hierarchy-fwk.all@tools.ietf.org, gen-art@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [Gen-art] Gen-ART review of draft-ietf-pce-hierarchy-fwk-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, 23 Aug 2012 21:35:29 -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-pce-hierarchy-fwk-04
Reviewer: Martin Thomson
Review Date: 2012-09-23
IETF LC End Date: 2012-08-24
IESG Telechat date: -

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

Nits:
I think that you probably meant to have the second letter of
"Antonymous System" rotated 180 degrees.  This appears several times.

From jmh@joelhalpern.com  Thu Aug 23 14:57:10 2012
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 19D2421F8665 for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 14:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.35
X-Spam-Level: 
X-Spam-Status: No, score=-102.35 tagged_above=-999 required=5 tests=[AWL=-0.085, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xubTqYMcNgug for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 14:57:09 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id B112121F8653 for <gen-art@ietf.org>; Thu, 23 Aug 2012 14:57:09 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 18102557F51 for <gen-art@ietf.org>; Thu, 23 Aug 2012 14:57:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 7C1D71A0500; Thu, 23 Aug 2012 14:57:08 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-50-124.clppva.btas.verizon.net [71.161.50.124]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id EBEB31A050A; Thu, 23 Aug 2012 14:57:07 -0700 (PDT)
Message-ID: <5036A731.90109@joelhalpern.com>
Date: Thu, 23 Aug 2012 17:57:05 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4FC7CB99.50701@nostrum.com>
In-Reply-To: <4FC7CB99.50701@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]   Review: draft-ietf-krb-wg-kdc-model-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: Thu, 23 Aug 2012 21:57:10 -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-krb-wg-kdc-model-14
     An information model for Kerberos version 5
Reviewer: Joel M. Halpern
Review Date: 23-Aug-2012
IETF LC End Date: 12-June-2012
IESG Telechat date: 30-Aug-2012

Summary: This document is ready for publication as a Proposed Standard.

Major issues: None.

Minor issues: None

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


From shares@ndzh.com  Thu Aug 23 16:28:00 2012
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 D215F21F84C4 for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 16:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.296
X-Spam-Level: 
X-Spam-Status: No, score=-2.296 tagged_above=-999 required=5 tests=[AWL=0.303,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zr+OxFF87Xib for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 16:28:00 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web.hickoryhill-consulting.com [64.9.205.140]) by ietfa.amsl.com (Postfix) with ESMTP id 24B9121F84C2 for <gen-art@ietf.org>; Thu, 23 Aug 2012 16:27:59 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=64.112.195.202; 
Received: from SKH2012HPLT (unverified [64.112.195.202])  by hickoryhill-consulting.com (SurgeMail 5.2a) with ESMTP id 3549553-1945496 for multiple; Thu, 23 Aug 2012 19:27:58 -0400
From: "Susan Hares" <shares@ndzh.com>
To: "'Elwyn Davies'" <elwynd@dial.pipex.com>, "'General Area Review Team'" <gen-art@ietf.org>
References: <1345724851.4622.5259.camel@mightyatom.folly.org.uk>
In-Reply-To: <1345724851.4622.5259.camel@mightyatom.folly.org.uk>
Date: Thu, 23 Aug 2012 19:27:55 -0400
Message-ID: <000001cd8186$eefea900$ccfbfb00$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLSmAtGrCMYNZXx5MnxkHHWL8w5a5Vd3bSw
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
X-Mailman-Approved-At: Thu, 23 Aug 2012 17:37:06 -0700
Cc: draft-ietf-idr-as0.all@tools.ietf.org
Subject: Re: [Gen-art] Spam:*******, Gen-art LC review of draft-ietf-idr-as0-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: Thu, 23 Aug 2012 23:28:00 -0000

Elwyn:

Thanks for sending in the review.

Sue 

-----Original Message-----
From: Elwyn Davies [mailto:elwynd@dial.pipex.com] 
Sent: Thursday, August 23, 2012 8:28 AM
To: General Area Review Team
Cc: draft-ietf-idr-as0.all@tools.ietf.org
Subject: Spam:*******, Gen-art LC review of draft-ietf-idr-as0-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-idr-as0-05.txt
Reviewer: Elwyn Davies
Review Date: 22 August 2012
IETF LC End Date: 22 August 2012
IESG Telechat date: (if known) - 

Summary:
Almost ready. 

Major issues:
None.

Minor issues:
s1, para 2:
>    [RFC6491] specifies that AS number zero in a ROA is used to mark an
>    NLRI which is to be marked as Invalid.
This is not what s4 of RFC 6491 says although ultimately this is
(probably) the way in which it is intended to be used.  RFC 6491 just says
that an 'AS 0 ROA' is used to mark a prefix and all its more specific
prefixes as not to be used in a routing context.

s1, para 4:
>    As at least two implementations discard routes containing AS 0, and
>    to allow approaches such as the above, this document codifies this
>    behavior.
This sentence is not entirely clear as to what behavior is being codified.
It could be just discarding routes with AS 0 or the the use of AS 0 to mark
prefixes that shouldn't be routed.  Please make this easier to parse.  This
is partly because of the over interpretation of RFC 6491 mentioned in the
previous comment.

Nits/editorial comments:
Abstract: Acronym BGP needs expanding.
s1: Acronyms ROA, AS and NLRI need expanding.
s2: It would be worth reinforcing that the behaviors being modified here are
currently specified in RFC 4271.  Arguably relevant section numbers would
help.
s4: Acronym RPKI needs expanding.
s4, para 2:
> security gotchas often lurk in the undefined spaces
This is slang and cliche that may be difficult for non-US speakers to
understand. 



From meral.shirazipour@ericsson.com  Thu Aug 23 21:01:02 2012
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 7582E21E8043 for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 21:01:02 -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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dscZ3MbGN4xm for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 21:01:01 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id BC9D621E8039 for <gen-art@ietf.org>; Thu, 23 Aug 2012 21:01:01 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q7O40x8b017475 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Aug 2012 23:01:00 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.2.164]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Fri, 24 Aug 2012 00:00:58 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-mmusic-media-loopback.all@tools.ietf.org" <draft-ietf-mmusic-media-loopback.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Fri, 24 Aug 2012 00:00:58 -0400
Thread-Topic: Gen-ART Last Call review of draft-ietf-mmusic-media-loopback-22
Thread-Index: AQHNga0RiS/Y1cqy60ibIrG4F6NJSw==
Message-ID: <25DC600D0CC1F2479C7053ADEB93004E6DF59B6282@EUSAACMS0703.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-mmusic-media-loopback-22
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, 24 Aug 2012 04:01:02 -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/Gen=
Artfaq> .

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

Document: draft-ietf-mmusic-media-loopback-22
Reviewer: Meral Shirazipour
Review Date: 2012-08-23
IETF LC End Date: 2012-08-23
IESG Telechat date: NA


Summary:
This draft is almost ready for publication as a standard track RFC, but I h=
ave some comments.


Nits/editorial comments:

[Page 4] line 5, suggestion: "that always loop incoming media back for sess=
ions." ----> "that always loop incoming media back for all sessions."

[Page 6] Section 3.1, suggestion for being consistent: "compliant to this m=
emo" ----> "compliant to this specification"

[Page 7] Section 3.1, 'loopback' ----> "loopback"

[Page 10] paragraph 2, "as defined in later sections", if possible please s=
pecify the actual Section number.

[Page 12] line 1, "the offer must contain", please double check that this i=
s not a "MUST"=20

[Page 13] Section 6, "from PLC" ----> "from Packet Loss Concealment (PLC) a=
lgorithm "

[Page 15] , please add Figure caption under the header format.

[Page 15] suggestion: "same clock rate MUST used " --missing be--> "same cl=
ock rate MUST be used "

"Loss RLE report block" ----> "Loss Run Length Encoding (RLE) report block"

Also=20
-please run for section ##, and when referring to specific section use capi=
tal S in Section.
-please spell out first occurrence of acronyms.


Thanks,
Meral



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

From meral.shirazipour@ericsson.com  Thu Aug 23 21:18:28 2012
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 BB29A21E8042 for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 21:18:28 -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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zIFzb06CXAj4 for <gen-art@ietfa.amsl.com>; Thu, 23 Aug 2012 21:18:27 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id A85BB21E8034 for <gen-art@ietf.org>; Thu, 23 Aug 2012 21:18:27 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q7O4JlaV012529; Thu, 23 Aug 2012 23:19:48 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.2.164]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Fri, 24 Aug 2012 00:18:19 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-mmusic-media-loopback.all@tools.ietf.org" <draft-ietf-mmusic-media-loopback.all@tools.ietf.org>
Date: Fri, 24 Aug 2012 00:16:18 -0400
Thread-Topic: Gen-ART Last Call review of draft-ietf-mmusic-media-loopback-22
Thread-Index: AQHNga0RiS/Y1cqy60ibIrG4F6NJS5doWxAQ
Message-ID: <25DC600D0CC1F2479C7053ADEB93004E6DF59B6284@EUSAACMS0703.eamcs.ericsson.se>
References: <25DC600D0CC1F2479C7053ADEB93004E6DF59B6282@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <25DC600D0CC1F2479C7053ADEB93004E6DF59B6282@EUSAACMS0703.eamcs.ericsson.se>
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
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-mmusic-media-loopback-22
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, 24 Aug 2012 04:18:28 -0000

Sorry for re-sending. The first attempt seem not working.

________________________________________
From: Meral Shirazipour
Sent: Friday, August 24, 2012 12:00 AM
To: draft-ietf-mmusic-media-loopback.all@tools.ietf.org; gen-art@ietf.org
Subject: Gen-ART Last Call review of draft-ietf-mmusic-media-loopback-22

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

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

Document: draft-ietf-mmusic-media-loopback-22
Reviewer: Meral Shirazipour
Review Date: 2012-08-23
IETF LC End Date: 2012-08-23
IESG Telechat date: NA


Summary:
This draft is almost ready for publication as a standard track RFC, but I h=
ave some comments.


Nits/editorial comments:

[Page 4] line 5, suggestion: "that always loop incoming media back for sess=
ions." ----> "that always loop incoming media back for all sessions."

[Page 6] Section 3.1, suggestion for being consistent: "compliant to this m=
emo" ----> "compliant to this specification"

[Page 7] Section 3.1, 'loopback' ----> "loopback"

[Page 10] paragraph 2, "as defined in later sections", if possible please s=
pecify the actual Section number.

[Page 12] line 1, "the offer must contain", please double check that this i=
s not a "MUST"

[Page 13] Section 6, "from PLC" ----> "from Packet Loss Concealment (PLC) a=
lgorithm "

[Page 15] , please add Figure caption under the header format.

[Page 15] suggestion: "same clock rate MUST used " --missing be--> "same cl=
ock rate MUST be used "

"Loss RLE report block" ----> "Loss Run Length Encoding (RLE) report block"

Also
-please run for section ##, and when referring to specific section use capi=
tal S in Section.
-please spell out first occurrence of acronyms.


Thanks,
Meral



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

From brian.e.carpenter@gmail.com  Fri Aug 24 06:45:42 2012
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 65E5421F866C for <gen-art@ietfa.amsl.com>; Fri, 24 Aug 2012 06:45:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.511
X-Spam-Level: 
X-Spam-Status: No, score=-101.511 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bYMMERK1a85L for <gen-art@ietfa.amsl.com>; Fri, 24 Aug 2012 06:45:41 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3E97621F864A for <gen-art@ietf.org>; Fri, 24 Aug 2012 06:45:41 -0700 (PDT)
Received: by eaai11 with SMTP id i11so563558eaa.31 for <gen-art@ietf.org>; Fri, 24 Aug 2012 06:45:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=A1zwcqM05c3JqJ2+NLmvdplbnqxlKrIzsXDQ0BaO6M4=; b=L/XLqiR3WPgQmottbvAEdczCYqOL7/gTab8uEIegWmAwYnP/kEdM6iPfyWBLQfH4Sx HuICYYDrh2Awx472rD5o1RtbX3GxOAcmQHBKlDtdQayXcMsYDc2efcPN0fXKbC573McV 1ZyQ/jzqqUGkKOeVH3BRa/CG/K8KOUVy1I+8hmZ8uQesNIFb3De0Rp+KQDhXpBEHs3zC WnZ/SV+VCSfONAZfvkwmqJdcIyhBnMNafJl9Sz2ReYMHehJll/DJjXXvtqcqfV8UzL0l aiilhV2524EB5YPV6cFU99ZNLNpx3BxSgl0W1AXTenJhnfEJXxgCsstE34HjvryY2+Dk mi/w==
Received: by 10.14.203.70 with SMTP id e46mr7652719eeo.2.1345815940327; Fri, 24 Aug 2012 06:45:40 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-59.as13285.net. [2.102.217.59]) by mx.google.com with ESMTPS id h2sm30070243eeo.3.2012.08.24.06.45.38 (version=SSLv3 cipher=OTHER); Fri, 24 Aug 2012 06:45:39 -0700 (PDT)
Message-ID: <50378584.1020503@gmail.com>
Date: Fri, 24 Aug 2012 14:45:40 +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-ippm-testplan-rfc2679.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------040808010305020700060503"
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-ippm-testplan-rfc2679-02.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, 24 Aug 2012 13:45:42 -0000

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

Please see attached review.





--------------040808010305020700060503
Content-Type: text/plain;
 name="draft-ietf-ippm-testplan-rfc2679-02-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-ippm-testplan-rfc2679-02-carpenter.txt"

SSBoYXZlIGJlZW4gc2VsZWN0ZWQgYXMgdGhlIEdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbSAo
R2VuLUFSVCkNCnJldmlld2VyIGZvciB0aGlzIGRyYWZ0IChmb3IgYmFja2dyb3VuZCBvbiBH
ZW4tQVJULCBwbGVhc2Ugc2VlDQpodHRwOi8vd3d3LmFsdmVzdHJhbmQubm8vaWV0Zi9nZW4v
YXJ0L2dlbi1hcnQtRkFRLmh0bWwpLg0KDQpQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZy
b20geW91ciBkb2N1bWVudCBzaGVwaGVyZA0Kb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcg
dmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoNCkRvY3VtZW50OiBkcmFmdC1pZXRmLWlwcG0tdGVz
dHBsYW4tcmZjMjY3OS0wMi50eHQNClJldmlld2VyOiBCcmlhbiBDYXJwZW50ZXINClJldmll
dyBEYXRlOiAyMDEyLTA4LTI0DQpJRVRGIExDIEVuZCBEYXRlOiAyMDEyLTA4LTE0DQpJRVNH
IFRlbGVjaGF0IGRhdGU6IDIwMTItMDgtMzANCg0KU3VtbWFyeTogIEFsbW9zdCByZWFkeQ0K
LS0tLS0tLS0NCg0KTm90ZTogVGhlIHVucHVibGlzaGVkIC0wMyBkcmFmdCBkZWFscyB3aXRo
IGFsbCBteSBjb21tZW50cyBiZWxvdy4NCi0tLS0tDQoNClNpZ25pZmljYW50IGlzc3VlczoN
Ci0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KQXQgdGhlIGVuZCBvZiBzZWN0aW9uIDY6DQoNCj4g
ICBPbmx5IHRoZSBUeXBlLVAtT25lLXdheS1EZWxheS1JbnZlcnNlLVBlcmNlbnRpbGUgaGFz
IGJlZW4gaWdub3JlZCBpbg0KPiAgIGJvdGggaW1wbGVtZW50YXRpb25zLCBzbyBpdCBpcyBh
IGNhbmRpZGF0ZSBmb3IgcmVtb3ZhbCBpbiBSRkMyNjc5YmlzLg0KDQpXaGF0IGlzIHRoaXMg
dGVsbGluZyB1cz8gVGhhdCBSRkMgMjc2OSBpc24ndCByZWFkeSBmb3IgYWR2YW5jZW1lbnQ/
DQpPciB0aGF0IHRoaXMgaXMgdGhlIG9ubHkgZGlzY3JlcGFuY3kgYW5kIGNhbiBiZSBzYWZl
bHkgaWdub3JlZD8NCg0KSW4gZmFjdCwgd2hhdCBpcyB0aGUgb3ZlcmFsbCBjb25jbHVzaW9u
PyBJIHdhcyByZWFsbHkgZXhwZWN0aW5nIHRvIGZpbmQNCmEgc3VtbWFyeSBhbmQgY29uY2x1
c2lvbiBhdCB0aGUgZW5kIG9mIHRoZSBkb2N1bWVudC4gVGhlIEFic3RyYWN0IHNheXMNCnRo
YXQgdGhlIGRyYWZ0IHByb3Bvc2VzIGFkdmFuY2VtZW50LCBidXQgdGhlIGJvZHkgb2YgdGhl
IHRleHQgZG9lc24ndA0KYWN0dWFsbHkgc2F5IHRoYXQgYW55d2hlcmUgdGhhdCBJIG5vdGlj
ZWQuDQoNCk5pdHM6DQotLS0tLQ0KDQo+IG8gIFRlc3QgZHVyYXRpb24gPSAzMDAgc2Vjb25k
cyAoTWFyY2ggMjkpDQoNClRoaXMgYW5kIG90aGVyIGRhdGVzIHNob3VsZCBpbmNsdWRlIHRo
ZSB5ZWFyLg0KDQpUaGVyZSdzIG9uZSBlcnJhdHVtIGFnYWluc3QgUkZDIDI2NzkuIFdoaWxl
IGl0J3MgdHJpdmlhbCwgYWNjb3JkaW5nIHRvIHRoZQ0KY3JpdGVyaWEgaW4gUkZDIDY0MTAs
IGl0IHNob3VsZCBiZSByZXZpZXdlZC4gT25lIHNlbnRlbmNlIHdvdWxkIGJlIGVub3VnaC4N
Cg0KDQoNCg0KDQo=
--------------040808010305020700060503--

From mary.ietf.barnes@gmail.com  Fri Aug 24 14:20:17 2012
Return-Path: <mary.ietf.barnes@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 B3DF921F861C for <gen-art@ietfa.amsl.com>; Fri, 24 Aug 2012 14:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.521
X-Spam-Level: 
X-Spam-Status: No, score=-103.521 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 75xJYFSaca0z for <gen-art@ietfa.amsl.com>; Fri, 24 Aug 2012 14:20:16 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8229E21F8617 for <gen-art@ietf.org>; Fri, 24 Aug 2012 14:20:16 -0700 (PDT)
Received: by lbky2 with SMTP id y2so658075lbk.31 for <gen-art@ietf.org>; Fri, 24 Aug 2012 14:20:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=0nIy129km8ium4cNbVfj4Zfpa4pawH8IMVWp4iMrgbY=; b=ND3F6O/lMP3eb0vYCJ8j6ELPX9l/d7YfDwA8OtY1r6X/aJpaJDLlRERG3kBKWq9LOQ Py9+caaRerdN3i7QRrvV6dA2uwupNwSrvtpHs7wrZZThehNPkHqL+rU+w0NtU65xDHNO IWfxJpxMgrmamitj7khJfLzwSDymoLNTQO1ARGt4zPCa4HsItLGNu7BKpjdAfJXn7ha3 9oPPGxmfSIvhQnGoq7RaznM7e+VyMIozrTkq1vSlOY7DhpGHaREjKj0dfooG2Q6Uy+cV YdAPoH/qK0L59Sz/xY9l8ovoWszbdyIYnkF9/hNUdrw+FikMGStvUFVWeF/XQxjE8P45 kJYw==
MIME-Version: 1.0
Received: by 10.112.46.135 with SMTP id v7mr3326954lbm.3.1345843215292; Fri, 24 Aug 2012 14:20:15 -0700 (PDT)
Received: by 10.112.85.196 with HTTP; Fri, 24 Aug 2012 14:20:15 -0700 (PDT)
Date: Fri, 24 Aug 2012 16:20:15 -0500
Message-ID: <CAHBDyN7UwW4+XRh_Cxx2PdA2Qr-cbSHHdqpx11Si4m=VM9kxhA@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: draft-ietf-dnsop-rfc4641bis.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=bcaec55240bec55b2704c8098a34
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART LC and telechat review: draft-ietf-dnsop-rfc4641bis-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, 24 Aug 2012 21:20:17 -0000

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

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-ietf-dnsop-rfc4641bis-12
Reviewer:  Mary Barnes
Review Date:  24 Aug 2012
IETF LC End Date: 24 Aug 2012
IESG Telechat Date: 30 Aug 2012

Summary:  Ready with nits.

Caveat: I have no expertise at all in this technical area, thus I'm
assuming that people who are have carefully reviewed.  Overall, the
document is quite readable.

Minor issues:
--------------

Section 2:
- 3rd para, last sentence is not clear - this phrase in particular doesn't
grok:  "if you rely on full zone transfers are based

I think you are trying to say the following:
OLD:
   It increases even more
   if you rely on full zone transfers are based on only the SOA timing
   parameters for refresh.
NEW:
   It increases even more if you rely on the full zone transfers
   being based only on the SOA timing parameters for refresh.



Nits:
----
- Section 3.2.3: i.e they -> i.e., they

- Section 4.2.1.1, last sentence: authentic -> authenticate

- Section 4.2.1.2, 2nd para, last sentence: possesion -> possession

- Section 4.2.4:  1st bullet: curren -> currently

- Section 4.3.3: non-existing -> non-existant

- Section 4.3.5.2:
-- redelegation -> re-delegation (2 places)
-- undelegated -> un-delegated (2nd bullet)
-- registers -> registrars (3rd bullet)

- Section 4.4.1:
-- 2nd bullet: minumum - > minimum
-- 3rd from last indented bullet: signatures times out - > signatures time
out

- Section 5.3.3, 1st para, last sentence: precalculated -> pre-calculated

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

<div>I am the assigned Gen-ART reviewer for this draft. For background on G=
en-ART, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/are=
a/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/Ge=
nArtfaq</a>&gt;.</div>
<div><br></div><div>Document: draft-ietf-dnsop-rfc4641bis-12</div><div>Revi=
ewer: =A0Mary Barnes=A0</div><div>Review Date: =A024 Aug 2012</div><div>IET=
F LC End Date: 24 Aug 2012</div><div>IESG Telechat Date: 30 Aug 2012</div><=
div>
<br></div><div>Summary: =A0Ready with nits.</div><div><br></div><div>Caveat=
: I have no expertise at all in this technical area, thus I&#39;m assuming =
that people who are have carefully reviewed. =A0Overall, the document is qu=
ite readable.</div>
<div><br></div><div>Minor issues:=A0</div><div>--------------</div><div><br=
></div><div>Section 2:</div><div>- 3rd para, last sentence is not clear - t=
his phrase in particular doesn&#39;t grok: =A0&quot;if you rely on full zon=
e transfers are based</div>
<div><br></div><div>I think you are trying to say the following:</div><div>=
OLD:</div><div>=A0 =A0It increases even more</div><div>=A0 =A0if you rely o=
n full zone transfers are based on only the SOA timing</div><div>=A0 =A0par=
ameters for refresh.</div>
<div>NEW:</div><div>=A0 =A0It increases even more if you rely on the full z=
one transfers=A0</div><div>=A0 =A0being based only on the SOA timing parame=
ters for refresh.</div><div><br></div><div><br></div><div><br></div><div>Ni=
ts:</div>
<div>----</div><div>- Section 3.2.3: i.e they -&gt; i.e., they</div><div><b=
r></div><div>- Section 4.2.1.1, last sentence: authentic -&gt; authenticate=
</div><div><br></div><div>- Section 4.2.1.2, 2nd para, last sentence: posse=
sion -&gt; possession</div>
<div><br></div><div>- Section 4.2.4: =A01st bullet: curren -&gt; currently=
=A0</div><div><br></div><div>- Section 4.3.3: non-existing -&gt; non-exista=
nt</div><div><br></div><div>- Section <a href=3D"http://4.3.5.2">4.3.5.2</a=
>:=A0</div>
<div>-- redelegation -&gt; re-delegation (2 places)</div><div>-- undelegate=
d -&gt; un-delegated (2nd bullet)</div><div>-- registers -&gt; registrars (=
3rd bullet)</div><div><br></div><div>- Section 4.4.1:</div><div>-- 2nd bull=
et: minumum - &gt; minimum</div>
<div>-- 3rd from last indented bullet: signatures times out - &gt; signatur=
es time out</div><div><br></div><div>- Section 5.3.3, 1st para, last senten=
ce: precalculated -&gt; pre-calculated</div>

--bcaec55240bec55b2704c8098a34--

From suresh.krishnan@ericsson.com  Fri Aug 24 15:55:38 2012
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 980CC21F85A2 for <gen-art@ietfa.amsl.com>; Fri, 24 Aug 2012 15:55:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.575
X-Spam-Level: 
X-Spam-Status: No, score=-106.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-x65BTOVnHX for <gen-art@ietfa.amsl.com>; Fri, 24 Aug 2012 15:55:38 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 07ACC21F8545 for <gen-art@ietf.org>; Fri, 24 Aug 2012 15:55:37 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q7OMuwPh027001; Fri, 24 Aug 2012 17:57:00 -0500
Received: from [142.133.112.80] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.264.1; Fri, 24 Aug 2012 18:55:29 -0400
Message-ID: <50380661.6020200@ericsson.com>
Date: Fri, 24 Aug 2012 18:55:29 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Rhys Smith <smith@cardiff.ac.uk>
References: <502994D9.2010309@ericsson.com> <E6770888-6673-44C0-85B5-62AF553E7DD2@cardiff.ac.uk>
In-Reply-To: <E6770888-6673-44C0-85B5-62AF553E7DD2@cardiff.ac.uk>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-abfab-usecases.all@tools.ietf.org" <draft-ietf-abfab-usecases.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-abfab-usecases-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: Fri, 24 Aug 2012 22:55:38 -0000

Hi Rhys,
  Thanks for making the changes. I have some responses to the open issues.

Rhys Smith wrote:
>> * Section 3.7
>>
>> The following text is a bit out of date.
>>
>> "At present, authentication to these applications will be typically
>>   configured manually by the user on the device (or on a different
>>   device connected to that device) but inputting their (usually pre-
>>   provisioned out-of-band) credentials for that application - one per
>>   application."
>>
>> With systems such as IMS that have gotten deployed, at least telco
>> operator hosted applications can use some form of federated identity
>> already. I do not have strong feelings about this but I suggest leaving
>> out operator hosted applications from this characterisation.
> 
> This use case came directly from some authors involved in operating mobile platforms. I think it's still useful to leave it in there as there are a variety of non-operator hosted applications that may not have such a thing enabled. The text currently says "could be hosted by the telecoms operator, or could be any application or system on the internet" which I think means the point is still valid...

My point was that this characterization was no longer widely applicable
for the operator hosted applications. I do not have strong feelings
about this. I am fine with leaving the text as is.

> 
> 
> 
>> * Section 3.9
>>
>> I am not sure I understand the following text
>>
>> "The utility company may wish to
>>   grant access only to authorized devices; for example, a consortium of
>>   utility companies and device manufacturers may certify devices to
>>   connect to power networks."
>>
>> What does the word certify mean here? I have always understood it to
>> mean testing compliance to certain requirements rather than verification
>> of identity. Can you please clarify?
> 
> In this case it would be exactly as you say - testing compliance to certain requirements. In the case of utility networks, it might mean that a particular device has the "usual" power certifications about how it uses electricity, but also certification around its "smartness" - what identity technologies it supports, what levels of assurance it can comply with around identity assertion, etc.

Great. In that case, it would be good to change the word "authorized" to
"certified" as it conveys the meaning accurately.

Thanks
Suresh


From adrian@olddog.co.uk  Sat Aug 25 02:27:26 2012
Return-Path: <adrian@olddog.co.uk>
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 4FA3721F84F9 for <gen-art@ietfa.amsl.com>; Sat, 25 Aug 2012 02:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.522
X-Spam-Level: 
X-Spam-Status: No, score=-3.522 tagged_above=-999 required=5 tests=[AWL=1.077,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WhmSja5vmWZB for <gen-art@ietfa.amsl.com>; Sat, 25 Aug 2012 02:27:25 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 7D96721F8527 for <gen-art@ietf.org>; Sat, 25 Aug 2012 02:27:25 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7P9RMHs027742;  Sat, 25 Aug 2012 10:27:22 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7P9RLZV027728 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 25 Aug 2012 10:27:22 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Martin Thomson'" <martin.thomson@gmail.com>, <draft-ietf-pce-hierarchy-fwk.all@tools.ietf.org>, <gen-art@ietf.org>
References: <CABkgnnW_hzwPFfKRRYaPnHfTR8NC1CTEva3hKUdoyaVLRUmsnA@mail.gmail.com>
In-Reply-To: <CABkgnnW_hzwPFfKRRYaPnHfTR8NC1CTEva3hKUdoyaVLRUmsnA@mail.gmail.com>
Date: Sat, 25 Aug 2012 10:27:19 +0100
Message-ID: <198d01cd82a3$d38c2670$7aa47350$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKESbsJjX3FrNQ+uO/AEmHVXw57aJX8s+uw
Content-Language: en-gb
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pce-hierarchy-fwk-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 25 Aug 2012 09:27:26 -0000

Got it, thauks.
Adriau


> -----Original Message-----
> From: Martin Thomson [mailto:martin.thomson@gmail.com]
> Sent: 23 August 2012 22:35
> To: draft-ietf-pce-hierarchy-fwk.all@tools.ietf.org; gen-art@ietf.org
> Subject: Gen-ART review of draft-ietf-pce-hierarchy-fwk-04
> 
> 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-pce-hierarchy-fwk-04
> Reviewer: Martin Thomson
> Review Date: 2012-09-23
> IETF LC End Date: 2012-08-24
> IESG Telechat date: -
> 
> Summary:
> This document is ready for publication as an Informational RFC.
> 
> Nits:
> I think that you probably meant to have the second letter of
> "Antonymous System" rotated 180 degrees.  This appears several times.


From warren@kumari.net  Sun Aug 26 08:37:31 2012
Return-Path: <warren@kumari.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 22C3E21F854D for <gen-art@ietfa.amsl.com>; Sun, 26 Aug 2012 08:37:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.497
X-Spam-Level: 
X-Spam-Status: No, score=-106.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhw6tMqQ0JxB for <gen-art@ietfa.amsl.com>; Sun, 26 Aug 2012 08:37:30 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 7062A21F854B for <gen-art@ietf.org>; Sun, 26 Aug 2012 08:37:30 -0700 (PDT)
Received: from [192.168.0.12] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 9C1B31B40038; Sun, 26 Aug 2012 11:37:29 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <1345724851.4622.5259.camel@mightyatom.folly.org.uk>
Date: Sun, 26 Aug 2012 11:37:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A51F2E6-3C49-443E-8C7E-F42095BADD85@kumari.net>
References: <1345724851.4622.5259.camel@mightyatom.folly.org.uk>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Sun, 26 Aug 2012 08:39:08 -0700
Cc: General Area Review Team <gen-art@ietf.org>, Warren Kumari <warren@kumari.net>, draft-ietf-idr-as0.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-idr-as0-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: Sun, 26 Aug 2012 15:37:31 -0000

On Aug 23, 2012, at 8:27 AM, Elwyn Davies wrote:

> I am the assigned Gen-ART reviewer for this draft.

Cool, and thank you for performing the review...


> 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-idr-as0-05.txt
> Reviewer: Elwyn Davies
> Review Date: 22 August 2012
> IETF LC End Date: 22 August 2012
> IESG Telechat date: (if known) -=20
>=20
> Summary:
> Almost ready.=20
>=20
> Major issues:
> None.
>=20
> Minor issues:
> s1, para 2:
>>   [RFC6491] specifies that AS number zero in a ROA is used to mark an
>>   NLRI which is to be marked as Invalid.
> This is not what s4 of RFC 6491 says although ultimately this is
> (probably) the way in which it is intended to be used.  RFC 6491 just
> says that an 'AS 0 ROA' is used to mark a prefix and all its more
> specific prefixes as not to be used in a routing context.

Yup. I think that when I originally wrote the above the pre-6491 draft =
mentioned invalid, but the RFC doesn't :-P

I have reworded it to:
RFC 6491 specifies that AS number zero in a ROA is used to mark a prefix =
and all its more specific prefixes as not to be used in a routing =
context. This allows a resource holder to signal that a prefix (and the =
more specifics) should not be routed by publishing a ROA listing AS0 as =
the only origin. To respond to this signal requres that BGP =
implementations do not accept or propagate routes containing AS0.


>=20
> s1, para 4:
>>   As at least two implementations discard routes containing AS 0, and
>>   to allow approaches such as the above, this document codifies this
>>   behavior.
> This sentence is not entirely clear as to what behavior is being
> codified. It could be just discarding routes with AS 0 or the the use =
of
> AS 0 to mark prefixes that shouldn't be routed.  Please make this =
easier
> to parse.  This is partly because of the over interpretation of RFC =
6491
> mentioned in the previous comment.

'twas supposed to mean just the first part (discarding routes with AS =
0), but this allows the second part :-P

Have modified it to just:
At least two implementations discard routes containing AS 0, and this =
document codifies this behavior.

>=20
> Nits/editorial comments:
> Abstract: Acronym BGP needs expanding.

Done!

> s1: Acronyms ROA, AS and NLRI need expanding.

Done, done and done.

> s2: It would be worth reinforcing that the behaviors being modified =
here
> are currently specified in RFC 4271.  Arguably relevant section =
numbers
> would help.

Done:
This document corrects this omission, most importantly in the case of =
the AS_PATH. This represents an update to the error handling procedures =
given in RFC4271 Sections 6.2 and 6.3 by specifying the behavior in the =
presence of AS0.


> s4: Acronym RPKI needs expanding.

Done.

> s4, para 2:
>> security gotchas often lurk in the undefined spaces
> This is slang and cliche that may be difficult for non-US speakers to =
understand.=20
>=20


Fair 'nuff. I fixed it, y'all. :-P

W

--
"Real children don't go hoppity-skip unless they are on drugs."

    -- Susan, the ultimate sensible governess (Terry Pratchett, =
Hogfather)





From elwynd@dial.pipex.com  Sun Aug 26 18:06:13 2012
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 C77E821F85A8 for <gen-art@ietfa.amsl.com>; Sun, 26 Aug 2012 18:06:13 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 56hYzy+ucfp7 for <gen-art@ietfa.amsl.com>; Sun, 26 Aug 2012 18:06:13 -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 E63EE21F8533 for <gen-art@ietf.org>; Sun, 26 Aug 2012 18:06:12 -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 1T5nmK-0003vO-Nf; Mon, 27 Aug 2012 02:06:08 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Warren Kumari <warren@kumari.net>
In-Reply-To: <0A51F2E6-3C49-443E-8C7E-F42095BADD85@kumari.net>
References: <1345724851.4622.5259.camel@mightyatom.folly.org.uk> <0A51F2E6-3C49-443E-8C7E-F42095BADD85@kumari.net>
Content-Type: text/plain
Date: Mon, 27 Aug 2012 02:10:36 +0100
Message-Id: <1346029836.4622.5278.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-idr-as0.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-idr-as0-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, 27 Aug 2012 01:06:13 -0000

That all looks good.

I think we are done here.

Thanks,
Elwyn

On Sun, 2012-08-26 at 11:37 -0400, Warren Kumari wrote:
> On Aug 23, 2012, at 8:27 AM, Elwyn Davies wrote:
> 
> > I am the assigned Gen-ART reviewer for this draft.
> 
> Cool, and thank you for performing the review...
> 
> 
> > 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-idr-as0-05.txt
> > Reviewer: Elwyn Davies
> > Review Date: 22 August 2012
> > IETF LC End Date: 22 August 2012
> > IESG Telechat date: (if known) - 
> > 
> > Summary:
> > Almost ready. 
> > 
> > Major issues:
> > None.
> > 
> > Minor issues:
> > s1, para 2:
> >>   [RFC6491] specifies that AS number zero in a ROA is used to mark an
> >>   NLRI which is to be marked as Invalid.
> > This is not what s4 of RFC 6491 says although ultimately this is
> > (probably) the way in which it is intended to be used.  RFC 6491 just
> > says that an 'AS 0 ROA' is used to mark a prefix and all its more
> > specific prefixes as not to be used in a routing context.
> 
> Yup. I think that when I originally wrote the above the pre-6491 draft mentioned invalid, but the RFC doesn't :-P
> 
> I have reworded it to:
> RFC 6491 specifies that AS number zero in a ROA is used to mark a prefix and all its more specific prefixes as not to be used in a routing context. This allows a resource holder to signal that a prefix (and the more specifics) should not be routed by publishing a ROA listing AS0 as the only origin. To respond to this signal requres that BGP implementations do not accept or propagate routes containing AS0.
> 
> 
> > 
> > s1, para 4:
> >>   As at least two implementations discard routes containing AS 0, and
> >>   to allow approaches such as the above, this document codifies this
> >>   behavior.
> > This sentence is not entirely clear as to what behavior is being
> > codified. It could be just discarding routes with AS 0 or the the use of
> > AS 0 to mark prefixes that shouldn't be routed.  Please make this easier
> > to parse.  This is partly because of the over interpretation of RFC 6491
> > mentioned in the previous comment.
> 
> 'twas supposed to mean just the first part (discarding routes with AS 0), but this allows the second part :-P
> 
> Have modified it to just:
> At least two implementations discard routes containing AS 0, and this document codifies this behavior.
> 
> > 
> > Nits/editorial comments:
> > Abstract: Acronym BGP needs expanding.
> 
> Done!
> 
> > s1: Acronyms ROA, AS and NLRI need expanding.
> 
> Done, done and done.
> 
> > s2: It would be worth reinforcing that the behaviors being modified here
> > are currently specified in RFC 4271.  Arguably relevant section numbers
> > would help.
> 
> Done:
> This document corrects this omission, most importantly in the case of the AS_PATH. This represents an update to the error handling procedures given in RFC4271 Sections 6.2 and 6.3 by specifying the behavior in the presence of AS0.
> 
> 
> > s4: Acronym RPKI needs expanding.
> 
> Done.
> 
> > s4, para 2:
> >> security gotchas often lurk in the undefined spaces
> > This is slang and cliche that may be difficult for non-US speakers to understand. 
> > 
> 
> 
> Fair 'nuff. I fixed it, y'all. :-P
> 
> W
> 
> --
> "Real children don't go hoppity-skip unless they are on drugs."
> 
>     -- Susan, the ultimate sensible governess (Terry Pratchett, Hogfather)
> 
> 
> 
> 


From mccap@petoni.org  Mon Aug 27 01:30:30 2012
Return-Path: <mccap@petoni.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 4CB8F21F8581 for <gen-art@ietfa.amsl.com>; Mon, 27 Aug 2012 01:30:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Na80rSKWydyY for <gen-art@ietfa.amsl.com>; Mon, 27 Aug 2012 01:30:29 -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 88A3721F857D for <gen-art@ietf.org>; Mon, 27 Aug 2012 01:30:29 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so838996ghb.31 for <gen-art@ietf.org>; Mon, 27 Aug 2012 01:30:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=k51SJe167Lqlpao3juBn/vMDc6Hentv+nmQ8HaDrHpY=; b=b2cBVDjDXScXZANU8hNBxm4OYJzJgc8OfoT1KlR821fpk6ePAMO3HHhw5e6YeWGjXX J3y7HA//N7HOSUSdS+6Sgh9PEKELqp7wh+/E1We7BfVdgeiYVc4FXydTDQQw+mNkln1i y+9Ye0CO+s9/7oHgB5/gOM1FlO2c4rRa7Fpzw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=k51SJe167Lqlpao3juBn/vMDc6Hentv+nmQ8HaDrHpY=; b=dkCBq0uoVrYPDo8FUrG0q+dbpfdZIsxxYfgLoCd9YGnMeXfyhek7gnNY1GlEPUiF4k 1ZR7x/ZZDPYdShs5qocMzlT+EWi3C5cBcE8a/k3qsSaD6iGQnNbXNW5Al1/nbyRbDoKu 5SU29Bw6oy3uCKk8Fe2j5xNq0uVzcDlnGZJFSxUyAgT+vMacG9p/KLVnw+SCxS+d2C+X S5hbSrhhwIdOzIpNNp8lJoNCwsuoJvDt0oMxtsDfAhMY3NYZF9QSKb8zSaJlgP/ZOv0+ p6hyNMNyylb+etZggGL8pNM1PO63zGpSZ0rN+dUknHuhgbwtRCqppdJCandsUQV9R6Pm 6ORg==
MIME-Version: 1.0
Received: by 10.236.197.5 with SMTP id s5mr10185244yhn.114.1346056228986; Mon, 27 Aug 2012 01:30:28 -0700 (PDT)
Received: by 10.101.57.6 with HTTP; Mon, 27 Aug 2012 01:30:28 -0700 (PDT)
X-Originating-IP: [68.45.157.93]
Date: Mon, 27 Aug 2012 04:30:28 -0400
Message-ID: <CACvMsLEg8jQxG_Q6vKMd33fAtAEqNP-5ArGJWScuuooUtt0vhw@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org,  draft-ietf-v6ops-wireline-incremental-ipv6.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnJHvtTjqr12oyhyeVWaL1kA4uZTEs+LVJ+l4ofhyYhIugRGjhvkVkuU2urg9UPnyHjCFFu
Subject: [Gen-art] Gen-ART LC and Telechat Review of draft-ietf-v6ops-wireline-incremental-ipv6-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, 27 Aug 2012 08:30:30 -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-v6ops-wireline-incremental-ipv6
Reviewer:  Peter McCann
Review Date:  2012-08-27
IETF LC End Date:  2012-08-27
IESG Telechat date: 2012-08-30

Summary: Ready

Major issues:  None

Minor issues:  None

Nits/editorial comments:

Section 2:
   or is in progress in
      deploying IPv6
SHOULD BE:
   or is in the process of
      deploying IPv6

Section 3.4:
   base protocol to delivery
SHOULD BE:
   base protocol to deliver

Section 4.1:
   improve it's performance
SHOULD BE:
   improve its performance

Section 4.2:
   will likely
   inherent
SHOULD BE:
   will likely
   inherit

   (i.e.  DHCPv6, DNSv4, TFTP, TR-069
   etc).
SHOULD BE:
   (i.e.  DHCPv4, DNSv4, TFTP, TR-069
   etc).

Section 4.5:
   significant about of external content
SHOULD BE:
   significant amount of external content

Section 4.6:
   host and home network supports
SHOULD BE:
   host and home network support

Section 5:
   (in percentage relative to IPv4)
SHOULD BE:
   (in percentage relative to IPv6)

Section 5.1.2:
   where downstream subscriber
   often move
SHOULD BE:
   where downstream subscribers
   often move

Section 5.1.4:
   Once
   such example may be
SHOULD BE:
   One
   such example may be

Section 5.4:
   subscriber all traffic must traverse
SHOULD BE:
  all subscriber traffic must traverse

Section 5.4.1:
   limiting the deploy based
SHOULD BE:
 limiting the deployed base

Section 5.5.1:
   on the subscribers
   premise device
SHOULD BE:
   on the subscriber
   premises device

Section 5.5.2:
   removal this undesired legacy behavior
SHOULD BE:
   removal of this undesired legacy behavior

From matthijs@nlnetlabs.nl  Mon Aug 27 02:55:38 2012
Return-Path: <matthijs@nlnetlabs.nl>
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 9282521F8471 for <gen-art@ietfa.amsl.com>; Mon, 27 Aug 2012 02:55:38 -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, NORMAL_HTTP_TO_IP=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QPP++zi9jXiX for <gen-art@ietfa.amsl.com>; Mon, 27 Aug 2012 02:55:37 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 68C3221F853E for <gen-art@ietf.org>; Mon, 27 Aug 2012 02:55:37 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:a992:57d9:b1a7:b609] ([IPv6:2001:7b8:206:1:a992:57d9:b1a7:b609]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q7R9tUKF029543 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 27 Aug 2012 11:55:31 +0200 (CEST) (envelope-from matthijs@nlnetlabs.nl)
X-DKIM: OpenDKIM Filter v2.6.7 open.nlnetlabs.nl q7R9tUKF029543
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1346061333; bh=50j/JaEDHgu0mNF8AiJJgAMPSSK4V6d8m5DW8cs0elk=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=WW7hfqSJPdyTYL+2nvKcEEf25abdwluamb5VGSfBxrL+g7Vi6oMBmseTzGpv+4Fys m/Ra0BfC9EnuzSuzTxTeru+nNvUkWjAHd4zyclHopu1lIjJxK1Gm56twf5lLGoFozQ FrkCQXRwMsYSebPBZoPhwD3yGy3yE4KdlS/9eymI=
Message-ID: <503B4414.4080209@nlnetlabs.nl>
Date: Mon, 27 Aug 2012 11:55:32 +0200
From: Matthijs Mekking <matthijs@nlnetlabs.nl>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
References: <CAHBDyN7UwW4+XRh_Cxx2PdA2Qr-cbSHHdqpx11Si4m=VM9kxhA@mail.gmail.com>
In-Reply-To: <CAHBDyN7UwW4+XRh_Cxx2PdA2Qr-cbSHHdqpx11Si4m=VM9kxhA@mail.gmail.com>
X-Enigmail-Version: 1.5pre
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::53]); Mon, 27 Aug 2012 11:55:32 +0200 (CEST)
X-Mailman-Approved-At: Mon, 27 Aug 2012 03:50:45 -0700
Cc: gen-art@ietf.org, draft-ietf-dnsop-rfc4641bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC and telechat review: draft-ietf-dnsop-rfc4641bis-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: Mon, 27 Aug 2012 09:55:38 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Mary,

Thanks for your review. I have incorporated them in the work in
progress. See the diff here:

http://tools.ietf.org//rfcdiff?url1=http://tools.ietf.org/id/draft-ietf-dnsop-rfc4641bis-12.txt&url2=http://www.nlnetlabs.nl/~matje/draft-ietf-dnsop-rfc4641bis.txt

tinyurl: http://tinyurl.com/8luvedk

This diff also includes three small changes from a colleague review.

Best regards,
  Matthijs


On 08/24/2012 11:20 PM, Mary Barnes 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-ietf-dnsop-rfc4641bis-12 Reviewer:  Mary Barnes 
> Review Date:  24 Aug 2012 IETF LC End Date: 24 Aug 2012 IESG
> Telechat Date: 30 Aug 2012
> 
> Summary:  Ready with nits.
> 
> Caveat: I have no expertise at all in this technical area, thus
> I'm assuming that people who are have carefully reviewed.  Overall,
> the document is quite readable.
> 
> Minor issues: --------------
> 
> Section 2: - 3rd para, last sentence is not clear - this phrase in
> particular doesn't grok:  "if you rely on full zone transfers are
> based
> 
> I think you are trying to say the following: OLD: It increases even
> more if you rely on full zone transfers are based on only the SOA
> timing parameters for refresh. NEW: It increases even more if you
> rely on the full zone transfers being based only on the SOA timing
> parameters for refresh.

I read the same thing, so I am going to use your proposed text.

> 
> 
> 
> Nits: ---- - Section 3.2.3: i.e they -> i.e., they
> 
> - Section 4.2.1.1, last sentence: authentic -> authenticate
> 
> - Section 4.2.1.2, 2nd para, last sentence: possesion ->
> possession
> 
> - Section 4.2.4:  1st bullet: curren -> currently
> 
> - Section 4.3.3: non-existing -> non-existant
> 
> - Section 4.3.5.2 <http://4.3.5.2>: -- redelegation ->
> re-delegation (2 places) -- undelegated -> un-delegated (2nd
> bullet) -- registers -> registrars (3rd bullet)
> 
> - Section 4.4.1: -- 2nd bullet: minumum - > minimum -- 3rd from
> last indented bullet: signatures times out - > signatures time out
> 
> - Section 5.3.3, 1st para, last sentence: precalculated ->
> pre-calculated
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJQO0QUAAoJEA8yVCPsQCW5oh8H/0A3r75VwlROQSqCeETMpZMd
iKAlYP6imS8k9zF9OqG3rh3n9BSWtYnv0qfe6ynmTSWy5a/2u3RBwSzTaxzdQLx1
Df9urKoxhGuPzN6qrVLrmUDPdulgRYyzI5Tvm2q4M2OqWm74qkCiw1B2gkE9c+Zn
HNSFpo1AZ8qlSKaMorGrRQMQehH34IKjmPRUXY9ptC98H7ItbDdii3YDz3vsQ0/J
3s9jh2/7Jb1Q5BmoE9wjLLzNzlEwyOoz0UEwKvYM79HW7btAwYa8pIuaucZHbyI7
L6Szor+RvBr65RJfPZshuM3gRCjh7Ws2Y3yijc2ycEUQLIzTEbfWwzZ2ZcGgAH4=
=42y2
-----END PGP SIGNATURE-----

From mary.ietf.barnes@gmail.com  Mon Aug 27 11:09:38 2012
Return-Path: <mary.ietf.barnes@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 2526621F84F9 for <gen-art@ietfa.amsl.com>; Mon, 27 Aug 2012 11:09:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.521
X-Spam-Level: 
X-Spam-Status: No, score=-103.521 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c90vulVyR2pL for <gen-art@ietfa.amsl.com>; Mon, 27 Aug 2012 11:09:37 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id AA88921F84A7 for <gen-art@ietf.org>; Mon, 27 Aug 2012 11:09:36 -0700 (PDT)
Received: by lbky2 with SMTP id y2so2077933lbk.31 for <gen-art@ietf.org>; Mon, 27 Aug 2012 11:09:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cGe3+KSBxZQ+cpG71Z7fYv8109fFPxx/2ru9niX06Fg=; b=DwijJY3vH5+J2TAMSGxu839SXPv4hK02s8KZ5dMX7CaUlz6Vg9GJqVZMDT3K7tKar6 bMHOCuiTwKmsRrK3VMEnTUtiUzMGTkd0+QcyagsbEIkmh+I9KaOnqKY+5IXpCAjfvbB/ 3MGWaa3+FNVbf7eXWx/VVcw5xa5jIV2mz8JLWCDcjivMp/wLeXdGu9SEgjBPcfLc2pK2 Y/U/qkyVmVfquOfqYJEatrWC1ma2jkwTpLRLgUy7mjk8dTPcTlCaJ+hoNXUi8GUHmi1l aR6JZmc0quUqwfpA5PI+DFVSfy/qFWrBl1o7+kBpGjB1sGTZhGEZoSioqpTkL4+uM7ZU uNSg==
MIME-Version: 1.0
Received: by 10.112.101.104 with SMTP id ff8mr7160711lbb.45.1346090975568; Mon, 27 Aug 2012 11:09:35 -0700 (PDT)
Received: by 10.112.17.202 with HTTP; Mon, 27 Aug 2012 11:09:35 -0700 (PDT)
In-Reply-To: <503B4414.4080209@nlnetlabs.nl>
References: <CAHBDyN7UwW4+XRh_Cxx2PdA2Qr-cbSHHdqpx11Si4m=VM9kxhA@mail.gmail.com> <503B4414.4080209@nlnetlabs.nl>
Date: Mon, 27 Aug 2012 13:09:35 -0500
Message-ID: <CAHBDyN7aBKFzNdKGvgXBx7J1NeOvAFdQ+0WZYa=DhXP_wTV2Dg@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Matthijs Mekking <matthijs@nlnetlabs.nl>
Content-Type: multipart/alternative; boundary=14dae9d67c786f243004c8433aa2
Cc: gen-art@ietf.org, draft-ietf-dnsop-rfc4641bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC and telechat review: draft-ietf-dnsop-rfc4641bis-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: Mon, 27 Aug 2012 18:09:38 -0000

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

Thanks - all my comments have been addressed.  However, you did introduce a
typo in the new text in 3.3:

"an unnecessary, inconventiently large" should be
"an unnecessary and inconveniently large"

But, other than that, it looks good.

Thanks,
Mary.

On Mon, Aug 27, 2012 at 4:55 AM, Matthijs Mekking <matthijs@nlnetlabs.nl>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Mary,
>
> Thanks for your review. I have incorporated them in the work in
> progress. See the diff here:
>
>
> http://tools.ietf.org//rfcdiff?url1=http://tools.ietf.org/id/draft-ietf-dnsop-rfc4641bis-12.txt&url2=http://www.nlnetlabs.nl/~matje/draft-ietf-dnsop-rfc4641bis.txt
>
> tinyurl: http://tinyurl.com/8luvedk
>
> This diff also includes three small changes from a colleague review.
>
> Best regards,
>   Matthijs
>
>
> On 08/24/2012 11:20 PM, Mary Barnes 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-ietf-dnsop-rfc4641bis-12 Reviewer:  Mary Barnes
> > Review Date:  24 Aug 2012 IETF LC End Date: 24 Aug 2012 IESG
> > Telechat Date: 30 Aug 2012
> >
> > Summary:  Ready with nits.
> >
> > Caveat: I have no expertise at all in this technical area, thus
> > I'm assuming that people who are have carefully reviewed.  Overall,
> > the document is quite readable.
> >
> > Minor issues: --------------
> >
> > Section 2: - 3rd para, last sentence is not clear - this phrase in
> > particular doesn't grok:  "if you rely on full zone transfers are
> > based
> >
> > I think you are trying to say the following: OLD: It increases even
> > more if you rely on full zone transfers are based on only the SOA
> > timing parameters for refresh. NEW: It increases even more if you
> > rely on the full zone transfers being based only on the SOA timing
> > parameters for refresh.
>
> I read the same thing, so I am going to use your proposed text.
>
> >
> >
> >
> > Nits: ---- - Section 3.2.3: i.e they -> i.e., they
> >
> > - Section 4.2.1.1, last sentence: authentic -> authenticate
> >
> > - Section 4.2.1.2, 2nd para, last sentence: possesion ->
> > possession
> >
> > - Section 4.2.4:  1st bullet: curren -> currently
> >
> > - Section 4.3.3: non-existing -> non-existant
> >
> > - Section 4.3.5.2 <http://4.3.5.2>: -- redelegation ->
> > re-delegation (2 places) -- undelegated -> un-delegated (2nd
> > bullet) -- registers -> registrars (3rd bullet)
> >
> > - Section 4.4.1: -- 2nd bullet: minumum - > minimum -- 3rd from
> > last indented bullet: signatures times out - > signatures time out
> >
> > - Section 5.3.3, 1st para, last sentence: precalculated ->
> > pre-calculated
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJQO0QUAAoJEA8yVCPsQCW5oh8H/0A3r75VwlROQSqCeETMpZMd
> iKAlYP6imS8k9zF9OqG3rh3n9BSWtYnv0qfe6ynmTSWy5a/2u3RBwSzTaxzdQLx1
> Df9urKoxhGuPzN6qrVLrmUDPdulgRYyzI5Tvm2q4M2OqWm74qkCiw1B2gkE9c+Zn
> HNSFpo1AZ8qlSKaMorGrRQMQehH34IKjmPRUXY9ptC98H7ItbDdii3YDz3vsQ0/J
> 3s9jh2/7Jb1Q5BmoE9wjLLzNzlEwyOoz0UEwKvYM79HW7btAwYa8pIuaucZHbyI7
> L6Szor+RvBr65RJfPZshuM3gRCjh7Ws2Y3yijc2ycEUQLIzTEbfWwzZ2ZcGgAH4=
> =42y2
> -----END PGP SIGNATURE-----
>

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

Thanks - all my comments have been addressed. =A0However, you did introduce=
 a typo in the new text in 3.3:<div><br><div><span class=3D"Apple-style-spa=
n" style=3D"white-space:pre"><span class=3D"insert" style=3D"background-col=
or:rgb(255,255,255)"><font class=3D"Apple-style-span" face=3D"monospace" st=
yle=3D"font-size:11px">&quot;an unnecessary, inconventiently large&quot; </=
font><font class=3D"Apple-style-span" face=3D"arial, helvetica, sans-serif"=
>should be</font><font class=3D"Apple-style-span" face=3D"monospace" style=
=3D"font-size:11px">=A0</font></span></span></div>
<div><span class=3D"Apple-style-span" style=3D"font-family:monospace;font-s=
ize:11px;white-space:pre"><span class=3D"insert" style=3D"background-color:=
rgb(255,255,255)">&quot;an unnecessary and inconveniently large&quot;</span=
></span></div>
<div><span class=3D"Apple-style-span" style=3D"font-family:monospace;font-s=
ize:11px;white-space:pre"><span class=3D"insert" style=3D"background-color:=
rgb(255,255,255)"><br></span></span></div><div><font class=3D"Apple-style-s=
pan" face=3D"arial, helvetica, sans-serif"><span class=3D"Apple-style-span"=
 style=3D"white-space:pre">But, other than that, it looks good. </span></fo=
nt></div>
<div><span class=3D"Apple-style-span" style=3D"white-space:pre"><font class=
=3D"Apple-style-span" face=3D"arial, helvetica, sans-serif"><br></font></sp=
an></div><div><span class=3D"Apple-style-span" style=3D"white-space:pre"><f=
ont class=3D"Apple-style-span" face=3D"arial, helvetica, sans-serif">Thanks=
,</font></span></div>
<div><font class=3D"Apple-style-span" face=3D"arial, helvetica, sans-serif"=
><span class=3D"Apple-style-span" style=3D"white-space:pre">Mary. </span></=
font></div><div><font class=3D"Apple-style-span" face=3D"monospace"><span c=
lass=3D"Apple-style-span" style=3D"font-size:11px;white-space:pre"><br>
</span></font><div class=3D"gmail_quote">On Mon, Aug 27, 2012 at 4:55 AM, M=
atthijs Mekking <span dir=3D"ltr">&lt;<a href=3D"mailto:matthijs@nlnetlabs.=
nl" target=3D"_blank">matthijs@nlnetlabs.nl</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hi Mary,<br>
<br>
Thanks for your review. I have incorporated them in the work in<br>
progress. See the diff here:<br>
<br>
<a href=3D"http://tools.ietf.org//rfcdiff?url1=3Dhttp://tools.ietf.org/id/d=
raft-ietf-dnsop-rfc4641bis-12.txt&amp;url2=3Dhttp://www.nlnetlabs.nl/~matje=
/draft-ietf-dnsop-rfc4641bis.txt" target=3D"_blank">http://tools.ietf.org//=
rfcdiff?url1=3Dhttp://tools.ietf.org/id/draft-ietf-dnsop-rfc4641bis-12.txt&=
amp;url2=3Dhttp://www.nlnetlabs.nl/~matje/draft-ietf-dnsop-rfc4641bis.txt</=
a><br>

<br>
tinyurl: <a href=3D"http://tinyurl.com/8luvedk" target=3D"_blank">http://ti=
nyurl.com/8luvedk</a><br>
<br>
This diff also includes three small changes from a colleague review.<br>
<br>
Best regards,<br>
=A0 Matthijs<br>
<div class=3D"im"><br>
<br>
On 08/24/2012 11:20 PM, Mary Barnes wrote:<br>
&gt; I am the assigned Gen-ART reviewer for this draft. For background<br>
&gt; on Gen-ART, please see the FAQ at<br>
&gt; &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;.<br>
&gt;<br>
&gt; Document: draft-ietf-dnsop-rfc4641bis-12 Reviewer: =A0Mary Barnes<br>
&gt; Review Date: =A024 Aug 2012 IETF LC End Date: 24 Aug 2012 IESG<br>
&gt; Telechat Date: 30 Aug 2012<br>
&gt;<br>
&gt; Summary: =A0Ready with nits.<br>
&gt;<br>
&gt; Caveat: I have no expertise at all in this technical area, thus<br>
&gt; I&#39;m assuming that people who are have carefully reviewed. =A0Overa=
ll,<br>
&gt; the document is quite readable.<br>
&gt;<br>
&gt; Minor issues: --------------<br>
&gt;<br>
&gt; Section 2: - 3rd para, last sentence is not clear - this phrase in<br>
&gt; particular doesn&#39;t grok: =A0&quot;if you rely on full zone transfe=
rs are<br>
&gt; based<br>
&gt;<br>
&gt; I think you are trying to say the following: OLD: It increases even<br=
>
&gt; more if you rely on full zone transfers are based on only the SOA<br>
&gt; timing parameters for refresh. NEW: It increases even more if you<br>
&gt; rely on the full zone transfers being based only on the SOA timing<br>
&gt; parameters for refresh.<br>
<br>
</div>I read the same thing, so I am going to use your proposed text.<br>
<div class=3D"im"><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Nits: ---- - Section 3.2.3: i.e they -&gt; i.e., they<br>
&gt;<br>
&gt; - Section 4.2.1.1, last sentence: authentic -&gt; authenticate<br>
&gt;<br>
&gt; - Section 4.2.1.2, 2nd para, last sentence: possesion -&gt;<br>
&gt; possession<br>
&gt;<br>
&gt; - Section 4.2.4: =A01st bullet: curren -&gt; currently<br>
&gt;<br>
&gt; - Section 4.3.3: non-existing -&gt; non-existant<br>
&gt;<br>
</div>&gt; - Section 4.3.5.2 &lt;<a href=3D"http://4.3.5.2" target=3D"_blan=
k">http://4.3.5.2</a>&gt;: -- redelegation -&gt;<br>
<div class=3D"im">&gt; re-delegation (2 places) -- undelegated -&gt; un-del=
egated (2nd<br>
&gt; bullet) -- registers -&gt; registrars (3rd bullet)<br>
&gt;<br>
&gt; - Section 4.4.1: -- 2nd bullet: minumum - &gt; minimum -- 3rd from<br>
&gt; last indented bullet: signatures times out - &gt; signatures time out<=
br>
&gt;<br>
&gt; - Section 5.3.3, 1st para, last sentence: precalculated -&gt;<br>
&gt; pre-calculated<br>
</div>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.11 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a href=3D"http://enigmail.mozdev.org/"=
 target=3D"_blank">http://enigmail.mozdev.org/</a><br>
<br>
iQEcBAEBAgAGBQJQO0QUAAoJEA8yVCPsQCW5oh8H/0A3r75VwlROQSqCeETMpZMd<br>
iKAlYP6imS8k9zF9OqG3rh3n9BSWtYnv0qfe6ynmTSWy5a/2u3RBwSzTaxzdQLx1<br>
Df9urKoxhGuPzN6qrVLrmUDPdulgRYyzI5Tvm2q4M2OqWm74qkCiw1B2gkE9c+Zn<br>
HNSFpo1AZ8qlSKaMorGrRQMQehH34IKjmPRUXY9ptC98H7ItbDdii3YDz3vsQ0/J<br>
3s9jh2/7Jb1Q5BmoE9wjLLzNzlEwyOoz0UEwKvYM79HW7btAwYa8pIuaucZHbyI7<br>
L6Szor+RvBr65RJfPZshuM3gRCjh7Ws2Y3yijc2ycEUQLIzTEbfWwzZ2ZcGgAH4=3D<br>
=3D42y2<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br></div></div>

--14dae9d67c786f243004c8433aa2--

From ben@nostrum.com  Tue Aug 28 12:12:23 2012
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 5F50E21F861E; Tue, 28 Aug 2012 12:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZIaIAEHnDcBH; Tue, 28 Aug 2012 12:12:22 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7D2B221F85B4; Tue, 28 Aug 2012 12:12:21 -0700 (PDT)
Received: from [10.0.1.30] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7SJCKG0028166 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Aug 2012 14:12:20 -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: Tue, 28 Aug 2012 14:12:18 -0500
Message-Id: <F7FBD7FB-6F10-4D1E-93D8-BACC2D46867B@nostrum.com>
To: draft-eggert-successful-bar-bof.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
X-Mailer: Apple Mail (2.1486)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART Telechat review of draft-eggert-successful-bar-bof-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, 28 Aug 2012 19:12:23 -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-eggert-successful-bar-bof-08
Reviewer: Ben Campbell
Review Date: 2012-08-28
IESG Telechat date: 2012-08-30

Summary: Ready for publication as an informational RFC

Note: The review assignment was for version 07, but since 08 was =
published prior to my review, I reviewed it instead. This version and =
related email correspondence address all of my concerns from my Gen-ART =
review of version 06 at IETF last call.

Major issues:

None

Minor issues:

None

Nits/editorial comments:

None=

From mccap@petoni.org  Tue Aug 28 16:37:30 2012
Return-Path: <mccap@petoni.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 AB3F111E80E7 for <gen-art@ietfa.amsl.com>; Tue, 28 Aug 2012 16:37:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 93zKnkP+0sO6 for <gen-art@ietfa.amsl.com>; Tue, 28 Aug 2012 16:37:29 -0700 (PDT)
Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by ietfa.amsl.com (Postfix) with ESMTP id A86E011E80B8 for <gen-art@ietf.org>; Tue, 28 Aug 2012 16:37:28 -0700 (PDT)
Received: by yhfs35 with SMTP id s35so70845yhf.27 for <gen-art@ietf.org>; Tue, 28 Aug 2012 16:37:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=SccxvdZIJQg7nA3viARrCU9wH8eAGonG50aANue8bLo=; b=AAGLCbVXeJnYm2vm4uYsDyNcBcIPIs57wbgiHQ2AgHkNp3PG8LH+XQwtPbQ1OIwb5O Fdm3HDGT303oDvKFxGyS1J48l+k3LxNPf//q56hK/sU3ZbiCDZE6LjBwd2IhcXMmMuwq 2DO2sscZxa5S+b6XYbtN03g2rsI3omQq3ZbPk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=SccxvdZIJQg7nA3viARrCU9wH8eAGonG50aANue8bLo=; b=Iye2hNdckTPafuk5xsffaMjP5JF2HOOnjxLvDyPK1gWsCpCgapOXM6muHx9JtscA/F XUr8wXZMhMa7Jz22Ebkp1+Ua7YXT+lnkp97Ansi2wgrSlTRMpAhC6tiF68HKD+w79zY7 WE6YhaMYQyfdEAOSFzpI13J9bfRNIX1idve3UKkMUrclmML1e4tkkyPZbGCyRo3hM8AT YXC0mhLxlm575VROg7d7ViMbWbgYzBXACVFVSVET44hmJUUYvrH8eMCIok65GQYMR33j 0cQZb1KAAjVknwSHgBsNCKJtRetf8xhfJHwiTHbERWonLj7sJSlR/+1nuPG/2jqgoA37 F+eQ==
MIME-Version: 1.0
Received: by 10.236.78.234 with SMTP id g70mr15536087yhe.24.1346197047827; Tue, 28 Aug 2012 16:37:27 -0700 (PDT)
Received: by 10.101.57.6 with HTTP; Tue, 28 Aug 2012 16:37:27 -0700 (PDT)
X-Originating-IP: [68.45.157.93]
Date: Tue, 28 Aug 2012 19:37:27 -0400
Message-ID: <CACvMsLGLy2zRenxm=wSR12bS3uW0eMeCAQ3CYG-=bj5X6JeL2g@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-bmwg-2544-as.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlPkIlp4KvRVm8tnta1utiRHQxhd3YUrWAjz/gD0Fc2j0HGaJ4mfz6NwlyKf8oXVc7fOCBf
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-bmwg-2544-as-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, 28 Aug 2012 23:37:30 -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-bmwg-2544-as-05
Reviewer:  Peter McCann
Review Date:  2012-08-28
IETF LC End Date:  2012-06-26
IESG Telechat date: 2012-08-30

Summary:  Ready

Major issues:  none

Minor issues:  none

Nits/editorial comments:  none

From mccap@petoni.org  Tue Aug 28 16:49:01 2012
Return-Path: <mccap@petoni.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 7854E21F8532 for <gen-art@ietfa.amsl.com>; Tue, 28 Aug 2012 16:49:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fz7LX6WRbSvE for <gen-art@ietfa.amsl.com>; Tue, 28 Aug 2012 16:49:00 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9AFA221F8530 for <gen-art@ietf.org>; Tue, 28 Aug 2012 16:49:00 -0700 (PDT)
Received: by ggnh4 with SMTP id h4so1212085ggn.31 for <gen-art@ietf.org>; Tue, 28 Aug 2012 16:49:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=mb3a3S1+akPp3L5cnpN/uFqujwoC3lrXRN5eFj3UaYY=; b=F1x1UMNtYnJHNCU648cKSOgCukZg8FRcyWPYw+HAyip+inKA6bG4CgJLw7EGqoebDF 7sVOBlBXgY5vyVJiB5aQ1TL/70kKnqIga4wRthaJ2DPf7trHuG+kFaMGJjRwQmSKIT2z /T4GfClNGdoA0Bh2dr8PAuvDHildnKpKxvijo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=mb3a3S1+akPp3L5cnpN/uFqujwoC3lrXRN5eFj3UaYY=; b=b7Jp0yMB9bYDkU4g6MA2pd9gqEIoryL/bha21gsD+wsL6HnSEuCEpDJMBsIB4b8wQS 6rqh2gxe+ji+ZoIKUtGL9RuCTUjCRFjtRdGb+/sBUGRwle2oB2/cJibFk4tFOjtYYHZ4 6b6Yf4wEjR5I85uTQxiU+opSwkghYtlJU/0ZG/Ree0yjMEwqT10EFeFL6VwVByyovqrK 9tMjccW21sftOzc7GizweW2Wfv5fvwCva8CBgtsKU1uU/kVZyj2FaG/BH2yR5mNyMKkP h/pMS2B+qYKgn0YcBTTXdB3E+/kKNVs0TP6lg0xhcIMMSppCNpA9KEM6BAmvxC2fzhIC eeTA==
MIME-Version: 1.0
Received: by 10.236.161.135 with SMTP id w7mr15554497yhk.15.1346197739630; Tue, 28 Aug 2012 16:48:59 -0700 (PDT)
Received: by 10.101.57.6 with HTTP; Tue, 28 Aug 2012 16:48:59 -0700 (PDT)
X-Originating-IP: [68.45.157.93]
Date: Tue, 28 Aug 2012 19:48:59 -0400
Message-ID: <CACvMsLFunswq42unAThDwe+reH0qc5W=Zn55CDumv3=VpRhvJA@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-appsawg-http-forwarded.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQn0BVOPCd64r49PuPZbSKx7YIbV4WFvlpH71heasrG1VVUujGsjnjRvzKZMkUv42EpJBR8n
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-appsawg-http-forwarded-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, 28 Aug 2012 23:49: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-appsawg-http-forwarded-07
Reviewer:  Peter McCann
Review Date:  2012-08-28
IETF LC End Date:  2012-07-23
IESG Telechat date: 2012-08-30

Summary: Ready

Major issues: none

Minor issues: none

Nits/editorial comments: none, all earlier comments are addressed in
this version

From elwynd@dial.pipex.com  Wed Aug 29 07:10:50 2012
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 4AEBF21F8567 for <gen-art@ietfa.amsl.com>; Wed, 29 Aug 2012 07:10:50 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OAX3jhgOr84i for <gen-art@ietfa.amsl.com>; Wed, 29 Aug 2012 07:10:49 -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 20A4021F8552 for <gen-art@ietf.org>; Wed, 29 Aug 2012 07:10:47 -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 1T6iya-00071F-SQ; Wed, 29 Aug 2012 15:10:37 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Wed, 29 Aug 2012 15:14:58 +0100
Message-Id: <1346249698.4622.5806.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-savi-dhcp.all@tools.ietf.org
Subject: [Gen-art] Gen-art telechat review of draft-ietf-savi-dhcp-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, 29 Aug 2012 14:10: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-savi-dhcp-14.txt
Reviewer: Elwyn Davies
Review Date: 28 August 2012
IETF LC End Date: - 
IESG Telechat date: 30 August 2012

Summary:
Not ready.
The explanation of SAVI Protection Perimeters and other matters in s2 of
RFC 6620 is very significantly better than the work in this draft, and
appears in many ways to be equally applicable.  Either duplicating and
adapting the RFC 6620 work in this draft or, better still, referencing
it so far as is possible and providing some differences would be a
significant improvement for this draft.

There are still a significant number of language issues including a
large number of missing indefinite articles, not all of which I have
noted below.

Major issues:

Minor issues:
s1, para 3: Suggestions for other SAVI mechanisms would be a good idea.
I think FCFS is mentioned later.

s5.1, para 2: 
>    Considering the trivial of configuration, it is expected SAVI-DHCP
>    function will not cause a break of the network even though an
>    attribute is not configured.  Thus, data packet filtering will not be
>    performed on binding anchor with no attribute.
I cannot parse the first sentence of this para. It strikes me that
having a default of 'let everything through' is not very robust.  This
is discussed in RFC 6620 where ports (which are actually what get
attributes in most cases) are either Trusted or not. 

s6.1: I failed to note during LC that recording the Lifetime of a
binding is not very useful.  If recording the Lifetime is needed then
one really wants to record the expiry time of the binding (i.e. the DHCP
lease) - logically recording the Lifetime is useless without the start
time or the implementation has to be specified to count down the
lifetimes of all bindings.

s6.2: Why should this draft seek to constrain the implementation of the 
proposal by mandating that a SAVI device 'MUST only use' a binding 
table that is not necessarily associated with the SAVI code?  Leave it
to the implementor to decide.

s7.3.2, s7.4.1.2 and s13.2 (and other places): The concept of 'binding
entry limit' is not defined.  It is unclear in s7 whether this is
supposed to be a per anchor or per device limit.  It is also unclear
what the purpose of having such a limit is until s13.2.  The text in
s7.3.2: 
> For any message that may
>    trigger a new binding, the binding entry limit (cf. Section 13.2) on
>    the corresponding binding anchor MUST NOT have not been reached.
implies a per-anchor limit but apparently conflicts with the text in
s7.4.1.2 which might imply a per device limit: 
> The binding entry limit can be exceeded when setting up bindings for
>    all addresses in a REPLY message.  If there is enough binding entry
>    resources, corresponding new entries MUST be generated even when the
>    binding number limit is exceeded.  In case that there is not enough
>    resources left, the message MUST be discarded.
The MUST NOT in the s7.3.2 is not a protocol specification issue - the
SAVI node has no control over how many addresses are given to an
interface by DHCP so that the count can exceed the specified max - SAVI
just has to cope with this.

S7.3.2 should refer to s13.2 to explain that excessive bindings is a
potential security risk.
Altogether this sections need to be made consistent.

In s13.2 a mitigation for binding entry limit overload is suggested to
be limiting the DHCP Request rate.  It is unclear that SAVI has any
control over this - or is it intended that SAVI should monitor the
request rate and discard excess messages?

s7.4.2.2: (DHCP)LEASEQUERY requests SHOULD be authenticated (probably
with IPSEC - not surprisingly) - is this envisioned?  The answer to this
question when asked in the previous review misinterpreted the question.
A discussion of how LEASEQUERY messages will be authenticated is
required.

Nits/editorial comments:
Abstract: s/on SAVI/on a SAVI/
Abstract; s1 para 1; and more generally: 'filter' - to what end? filter
just means distinguish the packets - 'identify', 'reject' or 'discard'
is what you mean maybe. More generally in this document the use of
'filter' with the implicit (I take it) meaning of discard is confusing.
There is a particular case in the second para of s5.1 where this is
problematic. 
Abstract: Links do not generate packets.
Abstract: s/complement of/complement to/

s1, para 2:  The term 'binding recovery procedure' is not defined.  It
would be useful to have some idea of why we want to define one before
saying it isn't discussed in [BA2007].
s1, para 3: 'only DHCP addresses': Presumably you mean again 'IP
addresses assigned to an interface via DHCP' . It would probably be
helpful to define a term for this rather than assuming 'DHCP address'.

s3: 'SAVI-DHCP': I am unclear what is being named here.  Is this the
whole set of devices or a mechanism?  What is a 'SAVI instance'? Do you
mean 'SAVI capability'? - also applies to definition of '(Non-)SAVI
device' definitions.

s4, para 1: s/DHCP relay/A DHCP relay/

s4, para 2: 
> Protection perimeter (refer to Section 4 in [savi-framework]) is
>    formed by SAVI Device A and SAVI Device B for scalability.
What has scalability to do with this?

s6.2, para 1: The two sentences need to be interchanged so that the
description of the table content comes first.


s5.1, para 1:
> thus, server type DHCP messages
>    from the binding anchor with no attribute will be discarded.
For consistency this should be about 'DHCP server/relay' messages.

s5.1, para 2:
> For example, in Figure 1, on the binding anchor of SAVI Device A
>    connected to Router B, it is unreasonable to set up bindings for the
>    host behind Router B, or filter out traffic from Router B, or allow
>    forged DHCP message from Router B. Thus, no attribute should be
>    configured on this binding anchor.
Some explanation of why it is unreasonable to do these things would be
desirable.  After reading this several times, I think that is trying to
say that we have to let all the data packets through but discard (bogus)
DHCP messages, but I am not sure about this.  As I mentioned in the
previous review it is unclear how bogus DHCP messages would be
distinguished in a case where the binding anchors are not configured.

s5.2:
> SAVI-Validation attribute is used on a binding anchor on which the
>    source address of data packet and DHCP message is to be validated.
>    The filtering process on the binding anchor with such attribute is
>    described in section 9.
Section 9 talks about 'data packets and control packets'.  The latter
are more than just DHCP messages. 

s5.4, para 3:
> However only when a
>    binding anchor is on the protection perimeter and connected to
>    another link, then it can have no attribute after configuration.
I don't understand the phrase' connected to another link. A binding
anchor is associated with a link/interface... what is connected to
another link?  

s7: It would be worth stating that the procedure uses a state machine.

s7.3.2: As noted in the previous review, the term 'control messages'
from s9.2 covers NDP messages as well as DHCP messages.  It would be
clearer to use server/relay DHCP message term as only DHCP mesages cause
events. 

s7.3.2/s7.5: What happens if a control message arrives but does not 
generate a valid event?  The authors made a statement about this in
response to a previous review but have not specified what happens in the
document (apparently discarding the event with no action).

s7.4.1.2:
> If the binding anchor is not a link layer address and there is not a
>    mapping table from the link layer address to the binding anchor, the
>    message SHOULD be discarded.
What else might happen here if the message is NOT discarded?  It strikes
me that this is a node misconfiguration rather than a protocol error.

s7.4.2.2:
> If there is no such an entry, the SAVI device
>    MUST send a LEASEQUERY [RFC5007] message querying by IP address to
>    All_DHCP_Relay_Agents_and_Servers multicast address [RFC3315] or a
>    configured server address. 
RFC 5007 is IPv6 specific.  If the EVE_DHCP_REPLY_NOLEASE event is
generated as a result of a DHCPv4 event then the relevant RFC is 4388
and it sends DHCPLEASEQUERY messages.

s8.1: What is the rationale for doing the queries twice in stage 1? -
needs explaining still.

s13: Discussion of TID spoofing?



From narten@us.ibm.com  Wed Aug 29 09:01:57 2012
Return-Path: <narten@us.ibm.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 C63CF21F86B5 for <gen-art@ietfa.amsl.com>; Wed, 29 Aug 2012 09:01:57 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RYJnT1D1rub6 for <gen-art@ietfa.amsl.com>; Wed, 29 Aug 2012 09:01:56 -0700 (PDT)
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by ietfa.amsl.com (Postfix) with ESMTP id 8E7D521F867D for <gen-art@ietf.org>; Wed, 29 Aug 2012 09:01:56 -0700 (PDT)
Received: from /spool/local by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <gen-art@ietf.org> from <narten@us.ibm.com>; Wed, 29 Aug 2012 10:01:44 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 29 Aug 2012 10:01:40 -0600
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id ADCDA1FF0055; Wed, 29 Aug 2012 10:01:33 -0600 (MDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q7TG0v1d078682; Wed, 29 Aug 2012 10:01:01 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q7TG0rhA032277; Wed, 29 Aug 2012 10:00:53 -0600
Received: from cichlid.raleigh.ibm.com ([9.80.31.201]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q7TG0nO6031741 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Aug 2012 10:00:51 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q7TFxgmJ012331; Wed, 29 Aug 2012 11:59:43 -0400
Message-Id: <201208291559.q7TFxgmJ012331@cichlid.raleigh.ibm.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
In-reply-to: <502471DB.80303@joelhalpern.com>
References: <50243C05.3080006@nostrum.com> <502471DB.80303@joelhalpern.com>
Comments: In-reply-to "Joel M. Halpern" <jmh@joelhalpern.com> message dated "Thu, 09 Aug 2012 22:28:43 -0400."
Date: Wed, 29 Aug 2012 11:59:41 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12082916-7282-0000-0000-00000C6AFA4E
Cc: gen-art@ietf.org, "armd@ietf.org" <armd@ietf.org>
Subject: Re: [Gen-art] [armd] Gen-art] review: draft-ietf-armd-problem-statement-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, 29 Aug 2012 16:01:58 -0000

Hi Joel.

Thanks for the review comments. (And sorry for taking so long to respond!)

"Joel M. Halpern" <jmh@joelhalpern.com> writes:

> Major issues:
>      The use of the term "switch" seems confusing.  I had first assumed 
> that it meant an ethernet switch (which might have  abit of L3 smarts, 
> or might not.  I was trying not to be picky.)  But then, in section 6.3 
> it refers to "core switches ... are the data center gateways to external 
> networks" which means that those are routers.

The switch vs. router terminology is tricky.

6.3 says:

   Core switches connect multiple aggregation switches and are the data
   center gateway(s) to external networks or interconnect to different
   sets of racks within one data center.

How about I change that to:

   Core switches connect multiple aggregation switches and interface
   with data center gateway(s) to external networks or interconnect to
   different sets of racks within one data center.

I know that is just side stepping this a bit, but Section 6.4 has more
text about the L2/L3 boundaries in various deployments. This document
is walking a bit of tightrope by trying to be general and not too
specific. If we get too specific, folk start screaming "that's not the
way my data center looks".

> Moderate Issue:
>     The document seems to be interestingly selective in what modern 
> technologies it chooses to mention.  Mostly it seems to be describing 
> problems with data center networks using technology more than 5 years 
> old.  Since that is the widely deployed practice, that is
>     defensible.

I think this has to do with how the WG was chartered.

> But then the document chooses to mention new work such as OpenFlow, 
> without mentioning the work IEEE has done on broadcast ad multicast 
> containment for data centers.  It seems to me that we need to be 
> consistent, either describing only the widely deployed technology, or 
> including a fair mention of already defined and productized solutions 
> that are not yet widely deployed.

I'd be fine with taking out the references to OpenFlow. I don't think
it adds much to the document.

>      On a related note, the document assumes that multicast NDs are 
> delivered to all nodes, while in practice I believe existing techniques 
> to filter such multicast messages closer to the source are widely 
> deployed.  (Section 5.)

This paragraph has been signficantly revised. The current proposed
text  is:

	Broadly speaking, from the perspective of address resolution,
        IPv6's Neighbor Discovery (ND) behaves much like ARP, with a
        few notable differences. First, ARP uses broadcast, whereas ND
        uses multicast. Specifically, when querying for a target IP
        address, ND maps the target address into an IPv6 Solicited
        Node multicast address. Using multicast rather than broadcast
        has the benefit that the multicast frames do not necessarily
        need to be sent to all parts of the network, i.e., only to
        segments where listeners for the Solicited Node multicast
        address reside. In the case where multicast frames are
        delivered to all parts of the network, sending to a multicast
        still has the advantage that most (if not all) nodes will
        filter out the (unwanted) multicast query via filters
        installed in the NIC rather than burdening host software with
        the need to process such packets. Thus, whereas all nodes must
        process every ARP query, ND queries are processed only by the
        nodes to which they are intended. In cases where multicast
        filtering can't effectively be implemented in the NIC (e.g.,
        as on hypervisors supporting virtualization), filtering would
        need to be done in software (e.g., in the hypervisor's
        vSwitch).

Is that better?	

> Minor issues:
>      I presume that section 6.4.2 which describes needing to enable all 
> VLANs on all aggregation ports is a description of current practice, 
> since it is not a requirement of current technologies, either via VLAN 
> management or orchestration?

Yes.

>      Section 6.4.4 seems very odd.  The title is "overlays".  Are there 
> widely deployed overlays?

I keep hearing yes, but proprietary, so little can be said about them.

> If so, it would be good to name the 
> technologies being referred to here.  If this is intended to refer to 
> the overlay proposal in IETF and IEEE, I think that the characterization 
> is somewhat misleading, and probably is best simply removed.

Hmm, I didn't actually write this text. It originally came from
draft-karir-armd-datacenter-reference-arch, which was merged into the
problem statement document by the WG.

I agree this section is kind of fuzzy,

I'm on the fence about what to do. Are there other opinions?

>      Is the fifth paragraph of section 71. on ARP processing and 
> buffering in the absence of ARP cache entries accurate?  I may well be 
> out of date, but it used to be the case that most routers dropped the 
> packets, and some would buffer 1 packet deep at most.  This description 
> indicates a rather more elaborate behavior.

RFC 1122 says:

         2.3.2.2  ARP Packet Queue

            The link layer SHOULD save (rather than discard) at least
            one (the latest) packet of each set of packets destined to
            the same unresolved IP address, and transmit the saved
            packet when the address has been resolved.

RFC 1812 says:

3.3.2 Address Resolution Protocol - ARP

   Routers that implement ARP MUST be compliant and SHOULD be
   unconditionally compliant with the requirements in [INTRO:2].

   The link layer MUST NOT report a Destination Unreachable error to IP
   solely because there is no ARP cache entry for a destination; it
   SHOULD queue up to a small number of datagrams breifly while
   performing the ARP request/reply sequence, and reply that the
   destination is unreachable to one of the queued datagrams only when
   this proves fruitless.


>      Given that this document says it is a general document about 
> scaling issues for data centers, I am surprised that the security 
> considerations section does not touch on the increased complexity of 
> segregating subscriber traffic (customer A can not talk to customer B) 
> when there are very large numbers of customers, and the itneraction of 
> this with L2 scope.

The ARMD WG struggled a bit about scope, and all it was chartered to
do was a problem statement related to address resolution.

Looking at the title of the document "Problem Statement for ARMD", I'd
argue that's not helpful for an RFC given that ARMD will close  and
there is no followup WG planned. How about I change the title to
something like:

    Address Resolution Problems in Large Data Center Networks

I don't want to add other issues like traffic segregation to the
document at this point. Amoung other things, the WG really doesn't
have the energy for this... The intro is pretty clear (IMO) about the
limited scope of the document.

Thomas


From jmh@joelhalpern.com  Wed Aug 29 09:07:56 2012
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 432AE21F852E; Wed, 29 Aug 2012 09:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.349
X-Spam-Level: 
X-Spam-Status: No, score=-102.349 tagged_above=-999 required=5 tests=[AWL=-0.084, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xTV7S2f8AiBc; Wed, 29 Aug 2012 09:07:55 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 7427021F853A; Wed, 29 Aug 2012 09:07:55 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 1B5C8A6E0A; Wed, 29 Aug 2012 09:07:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 71D261BD3F68; Wed, 29 Aug 2012 09:07:53 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-50-84.clppva.btas.verizon.net [71.161.50.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 253D71BD4505; Wed, 29 Aug 2012 09:07:52 -0700 (PDT)
Message-ID: <503E3E54.70506@joelhalpern.com>
Date: Wed, 29 Aug 2012 12:07:48 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
References: <50243C05.3080006@nostrum.com> <502471DB.80303@joelhalpern.com> <201208291559.q7TFxgmJ012331@cichlid.raleigh.ibm.com>
In-Reply-To: <201208291559.q7TFxgmJ012331@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, "armd@ietf.org" <armd@ietf.org>
Subject: Re: [Gen-art] [armd] Gen-art] review: draft-ietf-armd-problem-statement-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, 29 Aug 2012 16:07:56 -0000

All of the proposed resolutions look very good.  Thank you.

With regard to routers and ARP caches, my concern is that from what I 
saw of the years, common practice did not seem to match the SHOULD from 
the RFCs.  I am a little remote from most implementations at the moment 
(the ones I can check easily are a tiny fraction of the market), so I 
was suggesting that be double-checked.

Yours,
Joel

On 8/29/2012 11:59 AM, Thomas Narten wrote:
> Hi Joel.
>
> Thanks for the review comments. (And sorry for taking so long to respond!)
>
> "Joel M. Halpern" <jmh@joelhalpern.com> writes:
>
>> Major issues:
>>       The use of the term "switch" seems confusing.  I had first assumed
>> that it meant an ethernet switch (which might have  abit of L3 smarts,
>> or might not.  I was trying not to be picky.)  But then, in section 6.3
>> it refers to "core switches ... are the data center gateways to external
>> networks" which means that those are routers.
>
> The switch vs. router terminology is tricky.
>
> 6.3 says:
>
>     Core switches connect multiple aggregation switches and are the data
>     center gateway(s) to external networks or interconnect to different
>     sets of racks within one data center.
>
> How about I change that to:
>
>     Core switches connect multiple aggregation switches and interface
>     with data center gateway(s) to external networks or interconnect to
>     different sets of racks within one data center.
>
> I know that is just side stepping this a bit, but Section 6.4 has more
> text about the L2/L3 boundaries in various deployments. This document
> is walking a bit of tightrope by trying to be general and not too
> specific. If we get too specific, folk start screaming "that's not the
> way my data center looks".
>
>> Moderate Issue:
>>      The document seems to be interestingly selective in what modern
>> technologies it chooses to mention.  Mostly it seems to be describing
>> problems with data center networks using technology more than 5 years
>> old.  Since that is the widely deployed practice, that is
>>      defensible.
>
> I think this has to do with how the WG was chartered.
>
>> But then the document chooses to mention new work such as OpenFlow,
>> without mentioning the work IEEE has done on broadcast ad multicast
>> containment for data centers.  It seems to me that we need to be
>> consistent, either describing only the widely deployed technology, or
>> including a fair mention of already defined and productized solutions
>> that are not yet widely deployed.
>
> I'd be fine with taking out the references to OpenFlow. I don't think
> it adds much to the document.
>
>>       On a related note, the document assumes that multicast NDs are
>> delivered to all nodes, while in practice I believe existing techniques
>> to filter such multicast messages closer to the source are widely
>> deployed.  (Section 5.)
>
> This paragraph has been signficantly revised. The current proposed
> text  is:
>
> 	Broadly speaking, from the perspective of address resolution,
>          IPv6's Neighbor Discovery (ND) behaves much like ARP, with a
>          few notable differences. First, ARP uses broadcast, whereas ND
>          uses multicast. Specifically, when querying for a target IP
>          address, ND maps the target address into an IPv6 Solicited
>          Node multicast address. Using multicast rather than broadcast
>          has the benefit that the multicast frames do not necessarily
>          need to be sent to all parts of the network, i.e., only to
>          segments where listeners for the Solicited Node multicast
>          address reside. In the case where multicast frames are
>          delivered to all parts of the network, sending to a multicast
>          still has the advantage that most (if not all) nodes will
>          filter out the (unwanted) multicast query via filters
>          installed in the NIC rather than burdening host software with
>          the need to process such packets. Thus, whereas all nodes must
>          process every ARP query, ND queries are processed only by the
>          nodes to which they are intended. In cases where multicast
>          filtering can't effectively be implemented in the NIC (e.g.,
>          as on hypervisors supporting virtualization), filtering would
>          need to be done in software (e.g., in the hypervisor's
>          vSwitch).
>
> Is that better?	
>
>> Minor issues:
>>       I presume that section 6.4.2 which describes needing to enable all
>> VLANs on all aggregation ports is a description of current practice,
>> since it is not a requirement of current technologies, either via VLAN
>> management or orchestration?
>
> Yes.
>
>>       Section 6.4.4 seems very odd.  The title is "overlays".  Are there
>> widely deployed overlays?
>
> I keep hearing yes, but proprietary, so little can be said about them.
>
>> If so, it would be good to name the
>> technologies being referred to here.  If this is intended to refer to
>> the overlay proposal in IETF and IEEE, I think that the characterization
>> is somewhat misleading, and probably is best simply removed.
>
> Hmm, I didn't actually write this text. It originally came from
> draft-karir-armd-datacenter-reference-arch, which was merged into the
> problem statement document by the WG.
>
> I agree this section is kind of fuzzy,
>
> I'm on the fence about what to do. Are there other opinions?
>
>>       Is the fifth paragraph of section 71. on ARP processing and
>> buffering in the absence of ARP cache entries accurate?  I may well be
>> out of date, but it used to be the case that most routers dropped the
>> packets, and some would buffer 1 packet deep at most.  This description
>> indicates a rather more elaborate behavior.
>
> RFC 1122 says:
>
>           2.3.2.2  ARP Packet Queue
>
>              The link layer SHOULD save (rather than discard) at least
>              one (the latest) packet of each set of packets destined to
>              the same unresolved IP address, and transmit the saved
>              packet when the address has been resolved.
>
> RFC 1812 says:
>
> 3.3.2 Address Resolution Protocol - ARP
>
>     Routers that implement ARP MUST be compliant and SHOULD be
>     unconditionally compliant with the requirements in [INTRO:2].
>
>     The link layer MUST NOT report a Destination Unreachable error to IP
>     solely because there is no ARP cache entry for a destination; it
>     SHOULD queue up to a small number of datagrams breifly while
>     performing the ARP request/reply sequence, and reply that the
>     destination is unreachable to one of the queued datagrams only when
>     this proves fruitless.
>
>
>>       Given that this document says it is a general document about
>> scaling issues for data centers, I am surprised that the security
>> considerations section does not touch on the increased complexity of
>> segregating subscriber traffic (customer A can not talk to customer B)
>> when there are very large numbers of customers, and the itneraction of
>> this with L2 scope.
>
> The ARMD WG struggled a bit about scope, and all it was chartered to
> do was a problem statement related to address resolution.
>
> Looking at the title of the document "Problem Statement for ARMD", I'd
> argue that's not helpful for an RFC given that ARMD will close  and
> there is no followup WG planned. How about I change the title to
> something like:
>
>      Address Resolution Problems in Large Data Center Networks
>
> I don't want to add other issues like traffic segregation to the
> document at this point. Amoung other things, the WG really doesn't
> have the energy for this... The intro is pretty clear (IMO) about the
> limited scope of the document.
>
> Thomas
>
>

From narten@us.ibm.com  Wed Aug 29 12:55:05 2012
Return-Path: <narten@us.ibm.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 368D111E80F0 for <gen-art@ietfa.amsl.com>; Wed, 29 Aug 2012 12:55:05 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sPMlPNSc1VtD for <gen-art@ietfa.amsl.com>; Wed, 29 Aug 2012 12:55:04 -0700 (PDT)
Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) by ietfa.amsl.com (Postfix) with ESMTP id 840EB11E80EC for <gen-art@ietf.org>; Wed, 29 Aug 2012 12:55:04 -0700 (PDT)
Received: from /spool/local by e35.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <gen-art@ietf.org> from <narten@us.ibm.com>; Wed, 29 Aug 2012 13:55:03 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e35.co.us.ibm.com (192.168.1.135) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 29 Aug 2012 13:54:22 -0600
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id B43F319D8043; Wed, 29 Aug 2012 13:54:21 -0600 (MDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q7TJsKXr115518; Wed, 29 Aug 2012 13:54:20 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q7TJsJmo007163; Wed, 29 Aug 2012 13:54:19 -0600
Received: from cichlid.raleigh.ibm.com ([9.80.31.201]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q7TJsI1e006958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Aug 2012 13:54:18 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q7TJsGqx015175; Wed, 29 Aug 2012 15:54:17 -0400
Message-Id: <201208291954.q7TJsGqx015175@cichlid.raleigh.ibm.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
In-reply-to: <503E3E54.70506@joelhalpern.com>
References: <50243C05.3080006@nostrum.com> <502471DB.80303@joelhalpern.com> <201208291559.q7TFxgmJ012331@cichlid.raleigh.ibm.com> <503E3E54.70506@joelhalpern.com>
Comments: In-reply-to "Joel M. Halpern" <jmh@joelhalpern.com> message dated "Wed, 29 Aug 2012 12:07:48 -0400."
Date: Wed, 29 Aug 2012 15:54:16 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12082919-6148-0000-0000-0000090DBF5F
Cc: gen-art@ietf.org, "armd@ietf.org" <armd@ietf.org>
Subject: Re: [Gen-art] [armd] Gen-art] review: draft-ietf-armd-problem-statement-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, 29 Aug 2012 19:55:05 -0000

Hi Joel.

> All of the proposed resolutions look very good.  Thank you.

Great!

> With regard to routers and ARP caches, my concern is that from what I 
> saw of the years, common practice did not seem to match the SHOULD from 
> the RFCs.  I am a little remote from most implementations at the moment 
> (the ones I can check easily are a tiny fraction of the market), so I 
> was suggesting that be double-checked.

I hear you, and I suspect that there is a wide variability in what
routers implement. And the easy implementation (especially for the
fast path) is not to queue anything at all, which would still be
compliant since queuing is only a SHOULD...

I've tweaked the text a bit more after looking at the actual
requirements (e.g., the spec doesn't say you have to send an ICMP
unreachable on an ARP miss, it only says that if you do, you shouldn't
do it just because there is no ARP entry).

In any case, the point of this paragraph is really just to explain the
steps, to show they can be "cpu intensive". I think the WG asserted
pretty strongly that for some implementations/deployments, the
implementation cost is a problem (i.e., CPU intensive to the point of
being problematical).

   Finally, another area concerns the overhead of processing IP packets
   for which no ARP entry exists.  Existing standards specify that one
   (or more) IP packets for which no ARP entry exists should be queued
   pending succesful completion of the address resolution process
   [RFC1122] [RFC1812].  Once an ARP query has been resolved, any queued
   packets can be forwarded on.  Again, the processing of such packets
   is handled in the "slow path", effectively limiting the rate at which
   a router can process ARP "cache misses" and is viewed as a problem in
   some deployments today.  Additionally, if no response is received,
   the router may send the ARP/ND query multiple times.  If no response
   is received after a number of ARP/ND requests, the router needs to
   drop any queued data packets, and may send an ICMP destination
   unreachable message as well [RFC0792].  This entire process can be
   CPU intensive.

Is that any better?

Thomas


From jmh@joelhalpern.com  Wed Aug 29 13:59:15 2012
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 0720611E80D7; Wed, 29 Aug 2012 13:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.348
X-Spam-Level: 
X-Spam-Status: No, score=-102.348 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pq+ZQN77TwAS; Wed, 29 Aug 2012 13:59:14 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 7518011E80EA; Wed, 29 Aug 2012 13:59:14 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 2F74CA5FCD; Wed, 29 Aug 2012 13:59:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 9A6B41C9F23; Wed, 29 Aug 2012 13:59:12 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-50-84.clppva.btas.verizon.net [71.161.50.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 9F52E1C9E9D; Wed, 29 Aug 2012 13:59:11 -0700 (PDT)
Message-ID: <503E829B.1000404@joelhalpern.com>
Date: Wed, 29 Aug 2012 16:59:07 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
References: <50243C05.3080006@nostrum.com> <502471DB.80303@joelhalpern.com> <201208291559.q7TFxgmJ012331@cichlid.raleigh.ibm.com> <503E3E54.70506@joelhalpern.com> <201208291954.q7TJsGqx015175@cichlid.raleigh.ibm.com>
In-Reply-To: <201208291954.q7TJsGqx015175@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, "armd@ietf.org" <armd@ietf.org>
Subject: Re: [Gen-art] [armd] Gen-art] review: draft-ietf-armd-problem-statement-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, 29 Aug 2012 20:59:15 -0000

Yes, that is better.
(While I disagree with the WG on some of the drivers here, I think the 
text is sufficiently accurate and clear at this point that I should be 
considered to be in the rough.)

Thank you for the time and attention,
Joel

On 8/29/2012 3:54 PM, Thomas Narten wrote:
> Hi Joel.
>
>> All of the proposed resolutions look very good.  Thank you.
>
> Great!
>
>> With regard to routers and ARP caches, my concern is that from what I
>> saw of the years, common practice did not seem to match the SHOULD from
>> the RFCs.  I am a little remote from most implementations at the moment
>> (the ones I can check easily are a tiny fraction of the market), so I
>> was suggesting that be double-checked.
>
> I hear you, and I suspect that there is a wide variability in what
> routers implement. And the easy implementation (especially for the
> fast path) is not to queue anything at all, which would still be
> compliant since queuing is only a SHOULD...
>
> I've tweaked the text a bit more after looking at the actual
> requirements (e.g., the spec doesn't say you have to send an ICMP
> unreachable on an ARP miss, it only says that if you do, you shouldn't
> do it just because there is no ARP entry).
>
> In any case, the point of this paragraph is really just to explain the
> steps, to show they can be "cpu intensive". I think the WG asserted
> pretty strongly that for some implementations/deployments, the
> implementation cost is a problem (i.e., CPU intensive to the point of
> being problematical).
>
>     Finally, another area concerns the overhead of processing IP packets
>     for which no ARP entry exists.  Existing standards specify that one
>     (or more) IP packets for which no ARP entry exists should be queued
>     pending succesful completion of the address resolution process
>     [RFC1122] [RFC1812].  Once an ARP query has been resolved, any queued
>     packets can be forwarded on.  Again, the processing of such packets
>     is handled in the "slow path", effectively limiting the rate at which
>     a router can process ARP "cache misses" and is viewed as a problem in
>     some deployments today.  Additionally, if no response is received,
>     the router may send the ARP/ND query multiple times.  If no response
>     is received after a number of ARP/ND requests, the router needs to
>     drop any queued data packets, and may send an ICMP destination
>     unreachable message as well [RFC0792].  This entire process can be
>     CPU intensive.
>
> Is that any better?
>
> Thomas
>

From peter@akayla.com  Wed Aug 29 20:31:14 2012
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 0902E11E8106; Wed, 29 Aug 2012 20:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVrD+dtmlRTE; Wed, 29 Aug 2012 20:31:13 -0700 (PDT)
Received: from p3plsmtpa06-03.prod.phx3.secureserver.net (p3plsmtpa06-03.prod.phx3.secureserver.net [173.201.192.104]) by ietfa.amsl.com (Postfix) with ESMTP id 4667811E8103; Wed, 29 Aug 2012 20:31:13 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa06-03.prod.phx3.secureserver.net with  id srXC1j0011huGat01rXCj1; Wed, 29 Aug 2012 20:31:12 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-ccamp-assoc-ext.all@tools.ietf.org>
Date: Wed, 29 Aug 2012 20:31:14 -0700
Message-ID: <005e01cd865f$e9035fe0$bb0a1fa0$@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: Ac2GXGvm+GKVy5bnQKSRdf5PVgZBeA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-ccamp-assoc-ext-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, 30 Aug 2012 03:31: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>

Document: draft-ietf-ccamp-assoc-ext-04
Reviewer: Peter Yee
Review Date: Aug-28-2012
IETF LC End Date: Aug-29-2012
IESG Telechat date: Not known

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

This document provides extensions to the scope of use of the RSVP
ASSOCIATION
object as well as providing an extended ASSOCIATION object capable of
handling
a longer Association ID.

Nits:

In the last example (Symmetric NAT), last sentence: "mechanisms" ->
"mechanism".

Section 2, 4th paragraph (the replacement text): "the the" -> "the".

Section 3.2.1, 2nd paragraph, 1st sentence: "are" -> "is".  Alternatively,
you 
could change "format" to "formats".

Section 3.2.2, 1st sentence: "apply" -> "applies".

Section 4.2, 1st sentence: "a" -> "an" in both occurrences.

Section 4.2, last paragraph, 2nd sentence: "a" -> "an".

Questions:

These are questions you may wish to answer but the draft is acceptable
without response:

1) In Section 4.2, 4th bullet, is there any implied relationship between the
Extended Association ID and the Association ID?  Or are they independent
values that simply must be matched?

2) Section 4.2, 5th bullet, you make a first and only mention of padding
bytes.
Are you using a specific method for generating these padding bytes or are
they random?  Given the matching requirement on ASSOCIATION objects,
it might be best to specify the padding generation so that if the object is
regenerated, it will still be matched by intermediary nodes.  I've presumed
that the padding bytes are for meeting the 4-byte multiple requirement,
but I don't know if implementations would ever be free to regenerate the
object for subsequent transmissions of that object.



From Francis.Dupont@fdupont.fr  Thu Aug 30 02:06:30 2012
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 B0EE321F8616 for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 02:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[AWL=-0.901, BAYES_00=-2.599, LONGWORDS=1.803]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qXPSeX815vkL for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 02:06:29 -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 44DC421F8615 for <gen-art@ietf.org>; Thu, 30 Aug 2012 02:06:26 -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 q7U96OeR038112; Thu, 30 Aug 2012 11:06:24 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201208300906.q7U96OeR038112@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Thu, 30 Aug 2012 11:06:24 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-mptcp-multiaddressed.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-mptcp-multiaddressed-09.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, 30 Aug 2012 09:06:30 -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-mptcp-multiaddressed-09.txt
Reviewer: Francis Dupont
Review Date: 20120828
IETF LC End Date: 20120815
IESG Telechat date: 20120830

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - the topic is not very well introduced but it is a member (and not
   the first one) of a group of documents so IMHO this can be really
   assessed only by reading all documents (in order)...

 - the language is English, not US English (I leave this to the RFC Editor,
  it just made my speller (configured for the US English) a bit fussy.

 - Abstract page 1 and many other places: i.e. -> i.e., (and e.g. -> e.g.,)

 - ToC pages 2 and 3, section 7 page 51:
  Acknowledgements -> Acknowledgments
  
 - 2.3 page 10: implictly -> implicitly

 - 2.4 pages 10 (3) and 11 (2): acknowledgements -> acknowledgments

 - same 3 page 13 and 3.3.2 page 26

 - 3.2 page 19: in
  "Doing the MAC exchange at this stage allow" allow -> allows?

 - 3.2 page 21: Deumultiplexing -> Demultiplexing

 - 3.3.1 page 24: neogiated -> negotiated ?

 - 3.3.2 page 27: restransmited -> restransmitted

 - 3.3.3 page 28: permissable -> permissible && oustanding -> outstanding

 - 3.3.4 page 29 and 3.4 page 34: succesfully -> successfully

 - 6 page 48: illustred -> illustrated

 - 6 page 48 figure 16: get the whole figure on the same page
  (more a warning for the RFC Editor BTW :-)

 - 8 pages 51 and 52: by [21]) Assignments _> by [21]). Assignments ??

 - A page 55: accomodate -> accommodate

 - English vs US English from my speller (other than acknowledgement):
  behaviour utilisation signalled labelled optimisations maximise whilst
  learnt minimise specialised emphasised analyse

Thanks

Francis.Dupont@fdupont.fr

From miguel.a.garcia@ericsson.com  Thu Aug 30 05:52:12 2012
Return-Path: <miguel.a.garcia@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 4F28521F861D for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 05:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.03
X-Spam-Level: 
X-Spam-Status: No, score=-6.03 tagged_above=-999 required=5 tests=[AWL=0.219,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3kTEHyq-wWvR for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 05:52:11 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5B24C21F861B for <gen-art@ietf.org>; Thu, 30 Aug 2012 05:52:11 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fea6d000002ccb-ef-503f61fa6f66
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 79.FE.11467.AF16F305; Thu, 30 Aug 2012 14:52:10 +0200 (CEST)
Received: from [159.107.24.224] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.264.1; Thu, 30 Aug 2012 14:52:09 +0200
Message-ID: <503F61F8.1040309@ericsson.com>
Date: Thu, 30 Aug 2012 14:52:08 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: draft-ietf-oauth-v2-threatmodel.authors@tools.ietf.org,  Barry Leiba <barryleiba@computer.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplluLIzCtJLcpLzFFi42KZGfG3VvdXon2AQcciCYtDiy+xWszqa2W0 uPrqM4vF9L3X2B1YPFpW9TJ7rO2+yuaxZMlPJo8vlz+zBbBEcdmkpOZklqUW6dslcGUc7NjJ XnCHo+Lj3bMsDYxT2LsYOTgkBEwkvn5L62LkBDLFJC7cW8/WxcjFISRwilFi5ot3zBDOGkaJ wxcOMoNU8QpoSxw98pkdxGYRUJX4vvcAmM0mYC7RunEjmC0qECix7uofdoh6QYmTM5+wgAwS EZjMKDFh6hNWkASzgL7EkT+7mUBsYQFHiVlbb7BBxG0lLsy5zgJhy0tsfzsHbLGQgKbE5JtL mScw8s9CMncWkpZZSFoWMDKvYhTOTczMSS831EstykwuLs7P0ytO3cQIDNKDW37r7mA8dU7k EKM0B4uSOC9X0n5/IYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYwG6xmS3DV7j5RKVoW8Pane JOT9WUpSJHn2F7k2tpNL1RbencF0WZKH8alqa6nL3++Tyn7lmLlYFjSE9pswLGHtLz601UF3 NbuT9f5pKmnueTNDrf7fab++b43gWm+XLes2Pfz3tv2d0QyVn+dn5x6Pkv91Y5OErHbg51eX CpidDnZdP3/qm5sSS3FGoqEWc1FxIgDrqxcRIAIAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-oauth-v2-threatmodel-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: Thu, 30 Aug 2012 12:52:12 -0000

I have been selected as the General Area Review Team (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 comments you may receive.

Document: draft-ietf-oauth-v2-threatmodel-06.txt
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 2012-08-30
IESG Telechat date: 2012-08-30

Summary: The document is ready for publication as an Informational RFC.

I reviewed version -06 of this document, indicating that the document was 
ready for publication. In the current version -07, new sections have been 
added. I have reviewed the new and modified text, and I only have an 
editorial comment (see below).

Major issues: none

Minor issues: none

Nits/editorial comments:
There is a typo in the title of Section 8.1. It says "Informative 
References", but I guess it should say "Normative References", because 
the "Information References" are listed in Section 8.2.

/Miguel


-- 
Miguel A. Garcia
+34-91-339-3608
Ericsson Spain

From lberger@labn.net  Thu Aug 30 07:25:27 2012
Return-Path: <lberger@labn.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 79F1C21F866A for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 07:25:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.381
X-Spam-Level: 
X-Spam-Status: No, score=-99.381 tagged_above=-999 required=5 tests=[AWL=0.780, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gXPJ3EXRB5yD for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 07:25:26 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6.bluehost.com [IPv6:2605:dc00:100:2::a6]) by ietfa.amsl.com (Postfix) with SMTP id 6F71221F8679 for <gen-art@ietf.org>; Thu, 30 Aug 2012 07:25:21 -0700 (PDT)
Received: (qmail 32682 invoked by uid 0); 30 Aug 2012 14:25:19 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 30 Aug 2012 14:25:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=jQkBnWbrQPBLdJc3dscCVkC2FPzoVRJcmGFZQOu6+UU=;  b=GIMXVLTBe2ZCQIqj7tQzsE3z6OPQ/nUVwoJT2MPo/bUjTDD8ysxi4pvVt2ttVdcQz/H7VGvqLXkvVFRWIqnHRpQJTYTjzUBs+cJ64sRF2MGlpDId8vhJ659mBM/VsaUn;
Received: from box313.bluehost.com ([69.89.31.113]:57967 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1T75gN-00024h-FN; Thu, 30 Aug 2012 08:25:19 -0600
Message-ID: <503F77CF.1080005@labn.net>
Date: Thu, 30 Aug 2012 10:25:19 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Peter Yee <peter@akayla.com>
References: <005e01cd865f$e9035fe0$bb0a1fa0$@akayla.com>
In-Reply-To: <005e01cd865f$e9035fe0$bb0a1fa0$@akayla.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ccamp-assoc-ext-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, 30 Aug 2012 14:25:27 -0000

Peter,
	Thank you for the comments.  Please see below for responses in-line.


On 8/29/2012 11:31 PM, Peter Yee 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-ietf-ccamp-assoc-ext-04
> Reviewer: Peter Yee
> Review Date: Aug-28-2012
> IETF LC End Date: Aug-29-2012
> IESG Telechat date: Not known
>
> Summary: This draft is basically ready for publication, but has nits that
> should be
> fixed before publication. [Ready with nits.]
>
> This document provides extensions to the scope of use of the RSVP
> ASSOCIATION
> object as well as providing an extended ASSOCIATION object capable of
> handling
> a longer Association ID.
>
> Nits:
>
> In the last example (Symmetric NAT), last sentence: "mechanisms" ->
> "mechanism".
>
> Section 2, 4th paragraph (the replacement text): "the the" -> "the".
>
> Section 3.2.1, 2nd paragraph, 1st sentence: "are" -> "is".  Alternatively,
> you
> could change "format" to "formats".
>
> Section 3.2.2, 1st sentence: "apply" -> "applies".
>
> Section 4.2, 1st sentence: "a" -> "an" in both occurrences.
>
> Section 4.2, last paragraph, 2nd sentence: "a" -> "an".
>

Thank you!

> Questions:
>
> These are questions you may wish to answer but the draft is acceptable
> without response:
>
> 1) In Section 4.2, 4th bullet, is there any implied relationship between the
> Extended Association ID and the Association ID?  Or are they independent
> values that simply must be matched?

The latter (as the text says.)

>
> 2) Section 4.2, 5th bullet, you make a first and only mention of padding
> bytes.
> Are you using a specific method for generating these padding bytes or are
> they random?

No, as it is completely up to the creator of the object to use it 
consistently.

> Given the matching requirement on ASSOCIATION objects,
> it might be best to specify the padding generation so that if the object is
> regenerated, it will still be matched by intermediary nodes.  I've presumed
> that the padding bytes are for meeting the 4-byte multiple requirement,
> but I don't know if implementations would ever be free to regenerate the
> object for subsequent transmissions of that object.

I'll add ", without modification," to the last sentence of 3.1.2 and 3.2.2.

Thank you for the comments!

Lou

From lberger@labn.net  Thu Aug 30 07:27:41 2012
Return-Path: <lberger@labn.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 55E1321F866D for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 07:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.399
X-Spam-Level: 
X-Spam-Status: No, score=-99.399 tagged_above=-999 required=5 tests=[AWL=0.762, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x82eGuoywII2 for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 07:27:38 -0700 (PDT)
Received: from oproxy11-pub.bluehost.com (unknown [IPv6:2605:dc00:100:2::a3]) by ietfa.amsl.com (Postfix) with SMTP id CF25721F8668 for <gen-art@ietf.org>; Thu, 30 Aug 2012 07:27:37 -0700 (PDT)
Received: (qmail 23272 invoked by uid 0); 30 Aug 2012 14:27:36 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy11.bluehost.com with SMTP; 30 Aug 2012 14:27:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=7ptoClnr672/RDznRSIN0sfuNpDTY8VGYIT3ri3U/xU=;  b=RzfZ30ivqsABUR6Ip3Ea9lV08VtoRgksAsI3A4gg/GLVPffWjxZMLN4P1oI78AiM0+6laVOuD062/hh2jHU+pLGHIGdXrk/2weAKjBNfK8qdwXeE/qz/ZjnCUPBsg2fz;
Received: from box313.bluehost.com ([69.89.31.113]:58175 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1T75iZ-0002kf-E6; Thu, 30 Aug 2012 08:27:35 -0600
Message-ID: <503F7857.3070905@labn.net>
Date: Thu, 30 Aug 2012 10:27:35 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>
References: <503F77CF.1080005@labn.net>
In-Reply-To: <503F77CF.1080005@labn.net>
X-Forwarded-Message-Id: <503F77CF.1080005@labn.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Fwd: Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-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, 30 Aug 2012 14:27:41 -0000

Adrian,
     Shout (or change the ID state) when you're ready for the update to 
be submitted.

Thanks,
Lou
-------- Original Message --------
Subject: 	Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
Date: 	Thu, 30 Aug 2012 10:25:19 -0400
From: 	Lou Berger <lberger@labn.net>
To: 	Peter Yee <peter@akayla.com>
CC: 	draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org, 
ietf@ietf.org



Peter,
	Thank you for the comments.  Please see below for responses in-line.


On 8/29/2012 11:31 PM, Peter Yee 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-ietf-ccamp-assoc-ext-04
> Reviewer: Peter Yee
> Review Date: Aug-28-2012
> IETF LC End Date: Aug-29-2012
> IESG Telechat date: Not known
>
> Summary: This draft is basically ready for publication, but has nits that
> should be
> fixed before publication. [Ready with nits.]
>
> This document provides extensions to the scope of use of the RSVP
> ASSOCIATION
> object as well as providing an extended ASSOCIATION object capable of
> handling
> a longer Association ID.
>
> Nits:
>
> In the last example (Symmetric NAT), last sentence: "mechanisms" ->
> "mechanism".
>
> Section 2, 4th paragraph (the replacement text): "the the" -> "the".
>
> Section 3.2.1, 2nd paragraph, 1st sentence: "are" -> "is".  Alternatively,
> you
> could change "format" to "formats".
>
> Section 3.2.2, 1st sentence: "apply" -> "applies".
>
> Section 4.2, 1st sentence: "a" -> "an" in both occurrences.
>
> Section 4.2, last paragraph, 2nd sentence: "a" -> "an".
>

Thank you!

> Questions:
>
> These are questions you may wish to answer but the draft is acceptable
> without response:
>
> 1) In Section 4.2, 4th bullet, is there any implied relationship between the
> Extended Association ID and the Association ID?  Or are they independent
> values that simply must be matched?

The latter (as the text says.)

>
> 2) Section 4.2, 5th bullet, you make a first and only mention of padding
> bytes.
> Are you using a specific method for generating these padding bytes or are
> they random?

No, as it is completely up to the creator of the object to use it
consistently.

> Given the matching requirement on ASSOCIATION objects,
> it might be best to specify the padding generation so that if the object is
> regenerated, it will still be matched by intermediary nodes.  I've presumed
> that the padding bytes are for meeting the 4-byte multiple requirement,
> but I don't know if implementations would ever be free to regenerate the
> object for subsequent transmissions of that object.

I'll add ", without modification," to the last sentence of 3.1.2 and 3.2.2.

Thank you for the comments!

Lou





From adrian@olddog.co.uk  Thu Aug 30 07:49:02 2012
Return-Path: <adrian@olddog.co.uk>
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 45AFE21F8607; Thu, 30 Aug 2012 07:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lomJ1D-VYkwc; Thu, 30 Aug 2012 07:49:01 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 5A70521F8610; Thu, 30 Aug 2012 07:49:01 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7UEmx6g019133;  Thu, 30 Aug 2012 15:48:59 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q7UEmtDP018970 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 30 Aug 2012 15:48:59 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Lou Berger'" <lberger@labn.net>
References: <503F77CF.1080005@labn.net> <503F7857.3070905@labn.net>
In-Reply-To: <503F7857.3070905@labn.net>
Date: Thu, 30 Aug 2012 15:48:55 +0100
Message-ID: <20fa01cd86be$971b0110$c5510330$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI1ZC8sJg8zIh0e8RXzbgNx+W88rQGw6RY+lpUs79A=
Content-Language: en-gb
Cc: draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ccamp-assoc-ext-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 30 Aug 2012 14:49:02 -0000

thnx

I was hoping for a routing directorate review (Dimitri) but it hasn't showed

Give it a couple of days and then we will move on w/o it. If the review comes in
late we will cross the bridge.

Aiming for telechat on 9/13

A

> -----Original Message-----
> From: Lou Berger [mailto:lberger@labn.net]
> Sent: 30 August 2012 15:28
> To: Adrian Farrel
> Cc: draft-ietf-ccamp-assoc-ext.all@tools.ietf.org; gen-art@ietf.org;
ietf@ietf.org
> Subject: Fwd: Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
> 
> 
> 
> Adrian,
>      Shout (or change the ID state) when you're ready for the update to
> be submitted.
> 
> Thanks,
> Lou
> -------- Original Message --------
> Subject: 	Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
> Date: 	Thu, 30 Aug 2012 10:25:19 -0400
> From: 	Lou Berger <lberger@labn.net>
> To: 	Peter Yee <peter@akayla.com>
> CC: 	draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org,
> ietf@ietf.org
> 
> 
> 
> Peter,
> 	Thank you for the comments.  Please see below for responses in-line.
> 
> 
> On 8/29/2012 11:31 PM, Peter Yee 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-ietf-ccamp-assoc-ext-04
> > Reviewer: Peter Yee
> > Review Date: Aug-28-2012
> > IETF LC End Date: Aug-29-2012
> > IESG Telechat date: Not known
> >
> > Summary: This draft is basically ready for publication, but has nits that
> > should be
> > fixed before publication. [Ready with nits.]
> >
> > This document provides extensions to the scope of use of the RSVP
> > ASSOCIATION
> > object as well as providing an extended ASSOCIATION object capable of
> > handling
> > a longer Association ID.
> >
> > Nits:
> >
> > In the last example (Symmetric NAT), last sentence: "mechanisms" ->
> > "mechanism".
> >
> > Section 2, 4th paragraph (the replacement text): "the the" -> "the".
> >
> > Section 3.2.1, 2nd paragraph, 1st sentence: "are" -> "is".  Alternatively,
> > you
> > could change "format" to "formats".
> >
> > Section 3.2.2, 1st sentence: "apply" -> "applies".
> >
> > Section 4.2, 1st sentence: "a" -> "an" in both occurrences.
> >
> > Section 4.2, last paragraph, 2nd sentence: "a" -> "an".
> >
> 
> Thank you!
> 
> > Questions:
> >
> > These are questions you may wish to answer but the draft is acceptable
> > without response:
> >
> > 1) In Section 4.2, 4th bullet, is there any implied relationship between the
> > Extended Association ID and the Association ID?  Or are they independent
> > values that simply must be matched?
> 
> The latter (as the text says.)
> 
> >
> > 2) Section 4.2, 5th bullet, you make a first and only mention of padding
> > bytes.
> > Are you using a specific method for generating these padding bytes or are
> > they random?
> 
> No, as it is completely up to the creator of the object to use it
> consistently.
> 
> > Given the matching requirement on ASSOCIATION objects,
> > it might be best to specify the padding generation so that if the object is
> > regenerated, it will still be matched by intermediary nodes.  I've presumed
> > that the padding bytes are for meeting the 4-byte multiple requirement,
> > but I don't know if implementations would ever be free to regenerate the
> > object for subsequent transmissions of that object.
> 
> I'll add ", without modification," to the last sentence of 3.1.2 and 3.2.2.
> 
> Thank you for the comments!
> 
> Lou
> 
> 



From lberger@labn.net  Thu Aug 30 07:58:07 2012
Return-Path: <lberger@labn.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 5AD5D21F851B for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 07:58:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.417
X-Spam-Level: 
X-Spam-Status: No, score=-99.417 tagged_above=-999 required=5 tests=[AWL=0.744, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ly++D7J41RSu for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 07:58:06 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6.bluehost.com [IPv6:2605:dc00:100:2::a6]) by ietfa.amsl.com (Postfix) with SMTP id 6077121F84A2 for <gen-art@ietf.org>; Thu, 30 Aug 2012 07:58:06 -0700 (PDT)
Received: (qmail 17788 invoked by uid 0); 30 Aug 2012 14:58:05 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 30 Aug 2012 14:58:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=lB8FsGTzYwD2luv33h+mULijVBFzJURM6SjeDTWnkVA=;  b=fJA6vMJ5u8/BIIYSFsANBozw4RWMh2hvG7BE7Pky0TjwFoysKxtYolIbQP8HgERKu++ZAuFEwME1UhSWA2DDe++dQjoQQoTyIzP9D5tfPYI3fw3ahjQARuvUW6hL7/W5;
Received: from box313.bluehost.com ([69.89.31.113]:32973 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1T76C5-0005fU-GM; Thu, 30 Aug 2012 08:58:05 -0600
Message-ID: <503F7F7D.8080404@labn.net>
Date: Thu, 30 Aug 2012 10:58:05 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>, ietf@ietf.org
References: <503F77CF.1080005@labn.net> <503F7857.3070905@labn.net>
In-Reply-To: <503F7857.3070905@labn.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Fwd: Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-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, 30 Aug 2012 14:58:07 -0000

Eek,
     I somehow managed to broadcast this!  My apologies.

Lou

On 8/30/2012 10:27 AM, Lou Berger wrote:
>
> Adrian,
>       Shout (or change the ID state) when you're ready for the update to
> be submitted.
>
> Thanks,
> Lou
> -------- Original Message --------
> Subject: 	Re: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
> Date: 	Thu, 30 Aug 2012 10:25:19 -0400
> From: 	Lou Berger <lberger@labn.net>
> To: 	Peter Yee <peter@akayla.com>
> CC: 	draft-ietf-ccamp-assoc-ext.all@tools.ietf.org, gen-art@ietf.org,
> ietf@ietf.org
>
>
>
> Peter,
> 	Thank you for the comments.  Please see below for responses in-line.
>
>
> On 8/29/2012 11:31 PM, Peter Yee 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-ietf-ccamp-assoc-ext-04
>> Reviewer: Peter Yee
>> Review Date: Aug-28-2012
>> IETF LC End Date: Aug-29-2012
>> IESG Telechat date: Not known
>>
>> Summary: This draft is basically ready for publication, but has nits that
>> should be
>> fixed before publication. [Ready with nits.]
>>
>> This document provides extensions to the scope of use of the RSVP
>> ASSOCIATION
>> object as well as providing an extended ASSOCIATION object capable of
>> handling
>> a longer Association ID.
>>
>> Nits:
>>
>> In the last example (Symmetric NAT), last sentence: "mechanisms" ->
>> "mechanism".
>>
>> Section 2, 4th paragraph (the replacement text): "the the" -> "the".
>>
>> Section 3.2.1, 2nd paragraph, 1st sentence: "are" -> "is".  Alternatively,
>> you
>> could change "format" to "formats".
>>
>> Section 3.2.2, 1st sentence: "apply" -> "applies".
>>
>> Section 4.2, 1st sentence: "a" -> "an" in both occurrences.
>>
>> Section 4.2, last paragraph, 2nd sentence: "a" -> "an".
>>
> Thank you!
>
>> Questions:
>>
>> These are questions you may wish to answer but the draft is acceptable
>> without response:
>>
>> 1) In Section 4.2, 4th bullet, is there any implied relationship between the
>> Extended Association ID and the Association ID?  Or are they independent
>> values that simply must be matched?
> The latter (as the text says.)
>
>> 2) Section 4.2, 5th bullet, you make a first and only mention of padding
>> bytes.
>> Are you using a specific method for generating these padding bytes or are
>> they random?
> No, as it is completely up to the creator of the object to use it
> consistently.
>
>> Given the matching requirement on ASSOCIATION objects,
>> it might be best to specify the padding generation so that if the object is
>> regenerated, it will still be matched by intermediary nodes.  I've presumed
>> that the padding bytes are for meeting the 4-byte multiple requirement,
>> but I don't know if implementations would ever be free to regenerate the
>> object for subsequent transmissions of that object.
> I'll add ", without modification," to the last sentence of 3.1.2 and 3.2.2.
>
> Thank you for the comments!
>
> Lou
>
>
>
>


From mahoney@nostrum.com  Thu Aug 30 14:28:43 2012
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 544B121F8528 for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 14:28:43 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id inYrgVZrML-J for <gen-art@ietfa.amsl.com>; Thu, 30 Aug 2012 14:28:42 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9EAAE21F851B for <gen-art@ietf.org>; Thu, 30 Aug 2012 14:28:42 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([4.30.77.1]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7ULSaBP013570 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 30 Aug 2012 16:28:37 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <503FDB04.4090707@nostrum.com>
Date: Thu, 30 Aug 2012 16:28:36 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
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 (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-08-30
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, 30 Aug 2012 21:28:43 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end        Draft

Alexey Melnikov   2012-09-13 
draft-ietf-grow-ops-reqs-for-bgp-error-handling-05.txt



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:
