
From ron.even.tlv@gmail.com  Sun Apr  1 08:36:18 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 8509621F8C3D; Sun,  1 Apr 2012 08:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 qypQ4zKdcVXK; Sun,  1 Apr 2012 08:36:17 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 583A121F8C06; Sun,  1 Apr 2012 08:36:14 -0700 (PDT)
Received: by wibhj6 with SMTP id hj6so1569836wib.13 for <multiple recipients>; Sun, 01 Apr 2012 08:36:13 -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=iI3msdMFUd7n+NnYNrvnX3zjPChf7/n+rIo/wqBQNNE=; b=ywwg9REXvussu06Zwf3tLrdYuoaPd2gPccRijcVqBejNJWlI6DDmpfBa+sykpnnr1g trP6ox+4UrWYtR+E1TaAbumyOIOpUfRE/k1T/by5tZHttVxqL0lBUHukUHSlHoStDmgL MwqGQrD4YtjRXaAM7Yvewepna/GX3HU+YjtpQVSJOwn2Dh6JfanzxfLFzY5snT7HryYB e0eSmxi2A5B4HhadaY5lO6meUw23NmFVaqYWX3OmbMJSxUwv075r20mODfjEBgWXjnll tvbdrm37Qp0m/bq4Qa6wyP9VnEzJFXDB6CqvDXWiPJG94ULveoxeZUCkcJY3sLek/ezG kaAg==
Received: by 10.180.80.104 with SMTP id q8mr16052374wix.14.1333294573492; Sun, 01 Apr 2012 08:36:13 -0700 (PDT)
Received: from windows8d787f9 ([109.65.204.117]) by mx.google.com with ESMTPS id ff9sm26119010wib.2.2012.04.01.08.36.11 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 01 Apr 2012 08:36:12 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-ancp-pon.all@tools.ietf.org>
Date: Sun, 1 Apr 2012 18:34:54 +0300
Message-ID: <4f7875ec.6965b40a.3e21.5e69@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_014D_01CD1036.2343B290"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac0QHPwUIzBEvghxQGatn7i3zdgDyg==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC review of draft-ietf-ancp-pon-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: Sun, 01 Apr 2012 15:36:18 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_014D_01CD1036.2343B290
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>.

Sorry for the late review due to IET meeting.

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

 

Document: draft-ietf-ancp-pon-02

Reviewer: Roni Even

Review Date:2012-4-1

IETF LC End Date: 2012-3-30

IESG Telechat date:

 

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

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

In section 4 "However, the broadcast capability on the PON enables the AN
(OLT) to send one copy on the PON as opposed to N  copies of a multicast
channel on the PON serving N premises being  receivers" I think the "being"
before the last word should be deleted

 

General editorial comment is about page breaks which can be better like
section 7 title is at the end of a page and the text is in the next page.
Also some of the figures and their descriptions are split between pages.

 


------=_NextPart_000_014D_01CD1036.2343B290
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 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=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>Sorry for the late review =
due to IET meeting.<o:p></o:p></p><p class=3DMsoNormal>Please resolve =
these comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span lang=3DFR =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span lang=3DFR =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-=
ancp-pon-02</span><span lang=3DFR =
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;4&#8211;1<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;3&#8211;30<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational </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"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>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><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
4 &#8221;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>However, =
the broadcast capability on the PON enables the AN (OLT) to send one =
copy on the PON as opposed to N&nbsp; copies of a multicast channel on =
the PON serving N premises being&nbsp; receivers&#8221; I think the =
&#8220;being&#8221; before the last word should be =
deleted<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"'>General =
editorial comment is about page breaks which can be better like section =
7 title is at the end of a page and the text is in the next page. Also =
some of the figures and their descriptions are split between =
pages.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DHE =
dir=3DRTL =
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p></=
div></body></html>
------=_NextPart_000_014D_01CD1036.2343B290--


From david.black@emc.com  Sun Apr  1 13:57:23 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 7EA4B21F89E5; Sun,  1 Apr 2012 13:57:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.092
X-Spam-Level: 
X-Spam-Status: No, score=-108.092 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_40=-0.185, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HZg4GCnkz5VE; Sun,  1 Apr 2012 13:57:22 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id B1E5221F89E4; Sun,  1 Apr 2012 13:57:22 -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 q31KvIPE025299 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 1 Apr 2012 16:57:19 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Sun, 1 Apr 2012 16:57:10 -0400
Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q31Kv9A1002772; Sun, 1 Apr 2012 16:57:10 -0400
Received: from mx14a.corp.emc.com ([169.254.1.70]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Sun, 1 Apr 2012 16:57:09 -0400
From: <david.black@emc.com>
To: <leifj@nordu.net>, <gen-art@ietf.org>, <ietf@ietf.org>
Date: Sun, 1 Apr 2012 16:57:07 -0400
Thread-Topic: Gen-ART review of draft-johansson-loa-registry-04
Thread-Index: Ac0QSf/k5rjw1b7/R4GhUN2VW96Sjg==
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E80811@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
Cc: tim.polk@nist.gov
Subject: [Gen-art] Gen-ART review of draft-johansson-loa-registry-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: Sun, 01 Apr 2012 20:57:23 -0000

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

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

Document: draft-johansson-loa-registry-04
Reviewer: David L. Black
Review Date: April 1, 2012
IETF LC End Date: April 3, 2012
IESG Telechat date: April 12, 2012

This draft establishes an IETF registry of SAML Level of Assurance (LoA) pr=
ofiles;
it's short and clear, although it does not contain any initial content for =
the
registry - presumably that will be supplied after the registry is created v=
ia the
expert review registration mechanism established by this draft.=20

Summary:
This draft is on the right track but has open issues, described in the revi=
ew.

Major issues: (1)
My major open issue concerns the last paragraph in the Introduction:

   Although the registry will contain URIs that reference SAML
   Authentication Context Profiles other protocols MAY use such URIs to
   represent levels of assurance definitions without relying on their
   SAML XML definitions.  Use of the registry by protocols other than
   SAML or OpenID Connect is encouraged.

While this is good in principle, and one presumes that each registration of
sets of profiles from an existing protocol will be self-consistent, this
text also encourages other (e.g., new) protocols to draw upon this registry
without providing any guidance.  I'm concerned that it's probably possible
to make a serious mess in a new protocol by using an LoA or two from multip=
le
sets of registered LoAs without paying attention to whether the resulting
collection of LoAs is consistent or coherent (or even sensible) for use in
a single protocol.  This concern is reinforced by the guidance to expert
reviewers in Section 4.1, which effectively conveys a desire to get all
of the reasonable LoA profiles registered here, regardless of source or
consistency with other registered LoA profiles.

I'd like to see some guidance to protocol designers and others for how to
appropriately select multiple LoA profiles from this registry in a fashion
that results in a consistent and (hopefully) usable collection.  For exampl=
e,
it may be a good idea to use (or start with) a set of related profiles alre=
ady
in use by an existing protocol in preference to mixing/matching individual
profiles from multiple existing protocols.  At some level, this is common
sense advice that the presence of profiles in this registry does not obviat=
e
the need to apply good design judgment, but that does deserve to be stated.=
 =20

Minor issues: (2)=20

(1) This draft is intended to be an informational RFC, but it uses
RFC 2119 keywords.  That's only a good idea in exceptional circumstances. I
suggest removing section 1.1 and replacing upper case MUST/SHOULD/MAY with
their lower case versions or reworded explanations of rationale.  Most of
the uses of RFC 2119 keywords are not protocol requirements, but requiremen=
ts
on IANA, registrants, and users of the registry for which RFC 2119 keywords
are not appropriate, e.g., see RFC 2119 section 6:

   Imperatives of the type defined in this memo must be used with care
   and sparingly.  In particular, they MUST only be used where it is
   actually required for interoperation or to limit behavior which has
   potential for causing harm (e.g., limiting retransmisssions)

(2) Section 4

OLD
   The initial pool of expert and the
   review criteria are outlined below.
NEW
   The review criteria are outlined below.

The initial pool of experts is not designated by this draft.

Nits/editorial comments:

Section 3

OLD
   The following ABNF productions represent reserved values and names
NEW
   The reserved element defined by the following ABNF productions represent=
s
   a set of reserved values and names

Section 4

   The registry is to be operated under the "Designated Expert Review"
   policy from RFC5226 [RFC5226] employing a pool of experts

Nope, the actual RFC5226 name of that well-known IANA policy is Expert
Review (or Designated Expert), see section 4.1 of RFC5226.  If that
well-known IANA policy isn't what was intended, this is a serious
open issue.

Top of p.7
   The presense of an entry in the registy MUST NOT be taken to imply
                                         ^
r ---------------------------------------/

Section 7

OLD
   An implementor of MUST NOT treat the registry as a trust framework or
NEW
   A protocol implementor MUST NOT treat the registry as a trust framework =
or

The minor issue about RFC 2119 keywords also applies to this text.

idnits 2.12.13 did not find any nits that need attention.

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 leifj@sunet.se  Sun Apr  1 14:59:34 2012
Return-Path: <leifj@sunet.se>
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 521DF21F88B0; Sun,  1 Apr 2012 14:59:34 -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 zorBGEThFOqr; Sun,  1 Apr 2012 14:59:33 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id D1B8021F88AF; Sun,  1 Apr 2012 14:59:32 -0700 (PDT)
Received: from [10.0.0.11] (ua-83-227-179-169.cust.bredbandsbolaget.se [83.227.179.169]) (authenticated bits=0) by backup-server.nordu.net (8.14.3/8.14.3) with ESMTP id q31LxJup022834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 1 Apr 2012 23:59:22 +0200 (CEST)
Message-ID: <4F78CFB7.6000209@sunet.se>
Date: Sun, 01 Apr 2012 23:59:19 +0200
From: Leif Johansson <leifj@sunet.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120310 Thunderbird/11.0
MIME-Version: 1.0
To: david.black@emc.com
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E80811@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E80811@MX14A.corp.emc.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sun, 01 Apr 2012 15:17:27 -0700
Cc: gen-art@ietf.org, ietf@ietf.org, leifj@nordu.net, tim.polk@nist.gov
Subject: Re: [Gen-art] Gen-ART review of draft-johansson-loa-registry-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: Sun, 01 Apr 2012 21:59:34 -0000

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

On 04/01/2012 10:57 PM, david.black@emc.com wrote:
> I am the assigned Gen-ART reviewer for this draft. For background
> on Gen-ART, please see the FAQ at 
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Please resolve these comments along with any other Last Call
> comments you may receive.
> 
> Document: draft-johansson-loa-registry-04 Reviewer: David L. Black 
> Review Date: April 1, 2012 IETF LC End Date: April 3, 2012 IESG
> Telechat date: April 12, 2012
> 
> This draft establishes an IETF registry of SAML Level of Assurance
> (LoA) profiles; it's short and clear, although it does not contain
> any initial content for the registry - presumably that will be
> supplied after the registry is created via the expert review
> registration mechanism established by this draft.
> 
> Summary: This draft is on the right track but has open issues,
> described in the review.
> 
> Major issues: (1) My major open issue concerns the last paragraph
> in the Introduction:
> 
> Although the registry will contain URIs that reference SAML 
> Authentication Context Profiles other protocols MAY use such URIs
> to represent levels of assurance definitions without relying on
> their SAML XML definitions.  Use of the registry by protocols other
> than SAML or OpenID Connect is encouraged.
> 
> While this is good in principle, and one presumes that each
> registration of sets of profiles from an existing protocol will be
> self-consistent, this text also encourages other (e.g., new)
> protocols to draw upon this registry without providing any
> guidance.  I'm concerned that it's probably possible to make a
> serious mess in a new protocol by using an LoA or two from
> multiple sets of registered LoAs without paying attention to
> whether the resulting collection of LoAs is consistent or coherent
> (or even sensible) for use in a single protocol.  This concern is
> reinforced by the guidance to expert reviewers in Section 4.1,
> which effectively conveys a desire to get all of the reasonable LoA
> profiles registered here, regardless of source or consistency with
> other registered LoA profiles.
> 
> I'd like to see some guidance to protocol designers and others for
> how to appropriately select multiple LoA profiles from this
> registry in a fashion that results in a consistent and (hopefully)
> usable collection.  For example, it may be a good idea to use (or
> start with) a set of related profiles already in use by an existing
> protocol in preference to mixing/matching individual profiles from
> multiple existing protocols.  At some level, this is common sense
> advice that the presence of profiles in this registry does not
> obviate the need to apply good design judgment, but that does
> deserve to be stated.

David,

The type of consistency you look for is extremely difficult to ascertain
and often rely on mapping the underlying policies. However I do see your
point. How about this:

"Protocol designers who want to reference this registry should be aware
that registered LoAs may depend on assumptions that do not carry over
to a new protocol."

> 
> Minor issues: (2)
> 
> (1) This draft is intended to be an informational RFC, but it uses 
> RFC 2119 keywords.  That's only a good idea in exceptional
> circumstances. I suggest removing section 1.1 and replacing upper
> case MUST/SHOULD/MAY with their lower case versions or reworded
> explanations of rationale.  Most of the uses of RFC 2119 keywords
> are not protocol requirements, but requirements on IANA,
> registrants, and users of the registry for which RFC 2119 keywords 
> are not appropriate, e.g., see RFC 2119 section 6:
> 
> Imperatives of the type defined in this memo must be used with
> care and sparingly.  In particular, they MUST only be used where it
> is actually required for interoperation or to limit behavior which
> has potential for causing harm (e.g., limiting retransmisssions)

ok

> 
> (2) Section 4
> 
> OLD The initial pool of expert and the review criteria are outlined
> below. NEW The review criteria are outlined below.
> 
> The initial pool of experts is not designated by this draft.
> 

good catch

> Nits/editorial comments:
> 
> Section 3
> 
> OLD The following ABNF productions represent reserved values and
> names NEW The reserved element defined by the following ABNF
> productions represents a set of reserved values and names

ok

> 
> Section 4
> 
> The registry is to be operated under the "Designated Expert
> Review" policy from RFC5226 [RFC5226] employing a pool of experts
> 
> Nope, the actual RFC5226 name of that well-known IANA policy is
> Expert Review (or Designated Expert), see section 4.1 of RFC5226.
> If that well-known IANA policy isn't what was intended, this is a
> serious open issue.

that IANA policy was indeed intended.

> 
> Top of p.7 The presense of an entry in the registy MUST NOT be
> taken to imply ^ r ---------------------------------------/
> 

Here I actually want normative language. It is quite important that the
registry not be over-interpreted.

> Section 7
> 
> OLD An implementor of MUST NOT treat the registry as a trust
> framework or NEW A protocol implementor MUST NOT treat the registry
> as a trust framework or
> 

I actually don't mean protocol implementor here. I mean consumer of the
registry.

> The minor issue about RFC 2119 keywords also applies to this text.
> 

This is another case where I think I disagree!

> idnits 2.12.13 did not find any nits that need attention.
> 
> Thanks, --David

thank you!

	Cheers Leif

> ---------------------------------------------------- David L.
> Black, Distinguished Engineer EMC Corporation, 176 South St.,
> Hopkinton, MA  01748 +1 (508) 293-7953             FAX: +1 (508)
> 293-7786 david.black@emc.com        Mobile: +1 (978) 394-7754 
> ----------------------------------------------------
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk94z7cACgkQ8Jx8FtbMZnczSACgtOd/Ltv7PXDMYFkdbDHBeKdB
n7UAoKNkSnBB/ZQZF96gwvKbTnXQq8Nt
=lEQ5
-----END PGP SIGNATURE-----

From david.black@emc.com  Sun Apr  1 20:58:27 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 C098D21F87D8; Sun,  1 Apr 2012 20:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.346
X-Spam-Level: 
X-Spam-Status: No, score=-109.346 tagged_above=-999 required=5 tests=[AWL=1.253, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oIPnAEMZGoSX; Sun,  1 Apr 2012 20:58:26 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id B273221F8748; Sun,  1 Apr 2012 20:58:26 -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 q323wMCG004185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 1 Apr 2012 23:58:23 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sun, 1 Apr 2012 23:58:13 -0400
Received: from mxhub31.corp.emc.com (mxhub31.corp.emc.com [128.222.70.171]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q323wCHP009500; Sun, 1 Apr 2012 23:58:12 -0400
Received: from mx14a.corp.emc.com ([169.254.1.70]) by mxhub31.corp.emc.com ([128.222.70.171]) with mapi; Sun, 1 Apr 2012 23:58:12 -0400
From: <david.black@emc.com>
To: <leifj@sunet.se>
Date: Sun, 1 Apr 2012 23:58:09 -0400
Thread-Topic: Gen-ART review of draft-johansson-loa-registry-04
Thread-Index: Ac0QUsWopmgqpOdLTuWE1NhMZA4iUwAMKDjw
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E8082E@MX14A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E80811@MX14A.corp.emc.com> <4F78CFB7.6000209@sunet.se>
In-Reply-To: <4F78CFB7.6000209@sunet.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
X-EMM-MHVC: 1
Cc: gen-art@ietf.org, ietf@ietf.org, leifj@nordu.net, tim.polk@nist.gov
Subject: Re: [Gen-art] Gen-ART review of draft-johansson-loa-registry-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, 02 Apr 2012 03:58:27 -0000

Leif,

> The type of consistency you look for is extremely difficult to ascertain
> and often rely on mapping the underlying policies. However I do see your
> point. How about this:
>=20
> "Protocol designers who want to reference this registry should be aware
> that registered LoAs may depend on assumptions that do not carry over
> to a new protocol."

Could you add "and that those assumptions may vary among the protocols for
which the LoAs were originally registered" ?

On RFC 2119 terms, I suggest that you talk to your AD (Sean).  The IESG
recently approved an IANA registry creation draft that I co-authored,
draft-ietf-storm-rddp-registries, and as part of that approval, removal of
RFC 2119 terms was requested.  See:

http://datatracker.ietf.org/doc/draft-ietf-storm-rddp-registries/history/

Thanks,
--David

> -----Original Message-----
> From: Leif Johansson [mailto:leifj@sunet.se]
> Sent: Sunday, April 01, 2012 5:59 PM
> To: Black, David
> Cc: leifj@nordu.net; gen-art@ietf.org; ietf@ietf.org; turners@ieca.com; t=
im.polk@nist.gov
> Subject: Re: Gen-ART review of draft-johansson-loa-registry-04
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On 04/01/2012 10:57 PM, david.black@emc.com wrote:
> > I am the assigned Gen-ART reviewer for this draft. For background
> > on Gen-ART, please see the FAQ at
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call
> > comments you may receive.
> >
> > Document: draft-johansson-loa-registry-04 Reviewer: David L. Black
> > Review Date: April 1, 2012 IETF LC End Date: April 3, 2012 IESG
> > Telechat date: April 12, 2012
> >
> > This draft establishes an IETF registry of SAML Level of Assurance
> > (LoA) profiles; it's short and clear, although it does not contain
> > any initial content for the registry - presumably that will be
> > supplied after the registry is created via the expert review
> > registration mechanism established by this draft.
> >
> > Summary: This draft is on the right track but has open issues,
> > described in the review.
> >
> > Major issues: (1) My major open issue concerns the last paragraph
> > in the Introduction:
> >
> > Although the registry will contain URIs that reference SAML
> > Authentication Context Profiles other protocols MAY use such URIs
> > to represent levels of assurance definitions without relying on
> > their SAML XML definitions.  Use of the registry by protocols other
> > than SAML or OpenID Connect is encouraged.
> >
> > While this is good in principle, and one presumes that each
> > registration of sets of profiles from an existing protocol will be
> > self-consistent, this text also encourages other (e.g., new)
> > protocols to draw upon this registry without providing any
> > guidance.  I'm concerned that it's probably possible to make a
> > serious mess in a new protocol by using an LoA or two from
> > multiple sets of registered LoAs without paying attention to
> > whether the resulting collection of LoAs is consistent or coherent
> > (or even sensible) for use in a single protocol.  This concern is
> > reinforced by the guidance to expert reviewers in Section 4.1,
> > which effectively conveys a desire to get all of the reasonable LoA
> > profiles registered here, regardless of source or consistency with
> > other registered LoA profiles.
> >
> > I'd like to see some guidance to protocol designers and others for
> > how to appropriately select multiple LoA profiles from this
> > registry in a fashion that results in a consistent and (hopefully)
> > usable collection.  For example, it may be a good idea to use (or
> > start with) a set of related profiles already in use by an existing
> > protocol in preference to mixing/matching individual profiles from
> > multiple existing protocols.  At some level, this is common sense
> > advice that the presence of profiles in this registry does not
> > obviate the need to apply good design judgment, but that does
> > deserve to be stated.
>=20
> David,
>=20
> The type of consistency you look for is extremely difficult to ascertain
> and often rely on mapping the underlying policies. However I do see your
> point. How about this:
>=20
> "Protocol designers who want to reference this registry should be aware
> that registered LoAs may depend on assumptions that do not carry over
> to a new protocol."
>=20
> >
> > Minor issues: (2)
> >
> > (1) This draft is intended to be an informational RFC, but it uses
> > RFC 2119 keywords.  That's only a good idea in exceptional
> > circumstances. I suggest removing section 1.1 and replacing upper
> > case MUST/SHOULD/MAY with their lower case versions or reworded
> > explanations of rationale.  Most of the uses of RFC 2119 keywords
> > are not protocol requirements, but requirements on IANA,
> > registrants, and users of the registry for which RFC 2119 keywords
> > are not appropriate, e.g., see RFC 2119 section 6:
> >
> > Imperatives of the type defined in this memo must be used with
> > care and sparingly.  In particular, they MUST only be used where it
> > is actually required for interoperation or to limit behavior which
> > has potential for causing harm (e.g., limiting retransmisssions)
>=20
> ok
>=20
> >
> > (2) Section 4
> >
> > OLD The initial pool of expert and the review criteria are outlined
> > below. NEW The review criteria are outlined below.
> >
> > The initial pool of experts is not designated by this draft.
> >
>=20
> good catch
>=20
> > Nits/editorial comments:
> >
> > Section 3
> >
> > OLD The following ABNF productions represent reserved values and
> > names NEW The reserved element defined by the following ABNF
> > productions represents a set of reserved values and names
>=20
> ok
>=20
> >
> > Section 4
> >
> > The registry is to be operated under the "Designated Expert
> > Review" policy from RFC5226 [RFC5226] employing a pool of experts
> >
> > Nope, the actual RFC5226 name of that well-known IANA policy is
> > Expert Review (or Designated Expert), see section 4.1 of RFC5226.
> > If that well-known IANA policy isn't what was intended, this is a
> > serious open issue.
>=20
> that IANA policy was indeed intended.
>=20
> >
> > Top of p.7 The presense of an entry in the registy MUST NOT be
> > taken to imply ^ r ---------------------------------------/
> >
>=20
> Here I actually want normative language. It is quite important that the
> registry not be over-interpreted.
>=20
> > Section 7
> >
> > OLD An implementor of MUST NOT treat the registry as a trust
> > framework or NEW A protocol implementor MUST NOT treat the registry
> > as a trust framework or
> >
>=20
> I actually don't mean protocol implementor here. I mean consumer of the
> registry.
>=20
> > The minor issue about RFC 2119 keywords also applies to this text.
> >
>=20
> This is another case where I think I disagree!
>=20
> > idnits 2.12.13 did not find any nits that need attention.
> >
> > Thanks, --David
>=20
> thank you!
>=20
> 	Cheers Leif
>=20
> > ---------------------------------------------------- David L.
> > Black, Distinguished Engineer EMC Corporation, 176 South St.,
> > Hopkinton, MA  01748 +1 (508) 293-7953             FAX: +1 (508)
> > 293-7786 david.black@emc.com        Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>=20
> iEYEARECAAYFAk94z7cACgkQ8Jx8FtbMZnczSACgtOd/Ltv7PXDMYFkdbDHBeKdB
> n7UAoKNkSnBB/ZQZF96gwvKbTnXQq8Nt
> =3DlEQ5
> -----END PGP SIGNATURE-----


From leifj@sunet.se  Mon Apr  2 00:07:13 2012
Return-Path: <leifj@sunet.se>
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 E70C711E8073; Mon,  2 Apr 2012 00:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ULIIFO75T126; Mon,  2 Apr 2012 00:07:12 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id 4A10111E80B6; Mon,  2 Apr 2012 00:07:11 -0700 (PDT)
Received: from [192.36.125.227] (dhcp.pilsnet.sunet.se [192.36.125.227]) (authenticated bits=0) by backup-server.nordu.net (8.14.3/8.14.3) with ESMTP id q3276vjA005610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Apr 2012 09:07:02 +0200 (CEST)
Message-ID: <4F795011.2000402@sunet.se>
Date: Mon, 02 Apr 2012 09:06:57 +0200
From: Leif Johansson <leifj@sunet.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120310 Thunderbird/11.0
MIME-Version: 1.0
To: david.black@emc.com
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E80811@MX14A.corp.emc.com> <4F78CFB7.6000209@sunet.se> <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E8082E@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E8082E@MX14A.corp.emc.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, ietf@ietf.org, leifj@nordu.net, tim.polk@nist.gov
Subject: Re: [Gen-art] Gen-ART review of draft-johansson-loa-registry-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, 02 Apr 2012 07:07:14 -0000

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

On 04/02/2012 05:58 AM, david.black@emc.com wrote:
> Leif,
> 
>> The type of consistency you look for is extremely difficult to
>> ascertain and often rely on mapping the underlying policies.
>> However I do see your point. How about this:
>> 
>> "Protocol designers who want to reference this registry should be
>> aware that registered LoAs may depend on assumptions that do not
>> carry over to a new protocol."
> 
> Could you add "and that those assumptions may vary among the
> protocols for which the LoAs were originally registered" ?

yep

> 
> On RFC 2119 terms, I suggest that you talk to your AD (Sean).  The
> IESG recently approved an IANA registry creation draft that I
> co-authored, draft-ietf-storm-rddp-registries, and as part of that
> approval, removal of RFC 2119 terms was requested.  See:
> 
> http://datatracker.ietf.org/doc/draft-ietf-storm-rddp-registries/history/
>
> 
ok I'll do that. Thanks again!

> Thanks, --David
> 
>> -----Original Message----- From: Leif Johansson
>> [mailto:leifj@sunet.se] Sent: Sunday, April 01, 2012 5:59 PM To:
>> Black, David Cc: leifj@nordu.net; gen-art@ietf.org;
>> ietf@ietf.org; turners@ieca.com; tim.polk@nist.gov Subject: Re:
>> Gen-ART review of draft-johansson-loa-registry-04
>> 
> On 04/01/2012 10:57 PM, david.black@emc.com wrote:
>>>> I am the assigned Gen-ART reviewer for this draft. For
>>>> background on Gen-ART, please see the FAQ at 
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>> 
>>>> Please resolve these comments along with any other Last Call 
>>>> comments you may receive.
>>>> 
>>>> Document: draft-johansson-loa-registry-04 Reviewer: David L.
>>>> Black Review Date: April 1, 2012 IETF LC End Date: April 3,
>>>> 2012 IESG Telechat date: April 12, 2012
>>>> 
>>>> This draft establishes an IETF registry of SAML Level of
>>>> Assurance (LoA) profiles; it's short and clear, although it
>>>> does not contain any initial content for the registry -
>>>> presumably that will be supplied after the registry is
>>>> created via the expert review registration mechanism
>>>> established by this draft.
>>>> 
>>>> Summary: This draft is on the right track but has open
>>>> issues, described in the review.
>>>> 
>>>> Major issues: (1) My major open issue concerns the last
>>>> paragraph in the Introduction:
>>>> 
>>>> Although the registry will contain URIs that reference SAML 
>>>> Authentication Context Profiles other protocols MAY use such
>>>> URIs to represent levels of assurance definitions without
>>>> relying on their SAML XML definitions.  Use of the registry
>>>> by protocols other than SAML or OpenID Connect is
>>>> encouraged.
>>>> 
>>>> While this is good in principle, and one presumes that each 
>>>> registration of sets of profiles from an existing protocol
>>>> will be self-consistent, this text also encourages other
>>>> (e.g., new) protocols to draw upon this registry without
>>>> providing any guidance.  I'm concerned that it's probably
>>>> possible to make a serious mess in a new protocol by using an
>>>> LoA or two from multiple sets of registered LoAs without
>>>> paying attention to whether the resulting collection of LoAs
>>>> is consistent or coherent (or even sensible) for use in a
>>>> single protocol.  This concern is reinforced by the guidance
>>>> to expert reviewers in Section 4.1, which effectively conveys
>>>> a desire to get all of the reasonable LoA profiles registered
>>>> here, regardless of source or consistency with other
>>>> registered LoA profiles.
>>>> 
>>>> I'd like to see some guidance to protocol designers and
>>>> others for how to appropriately select multiple LoA profiles
>>>> from this registry in a fashion that results in a consistent
>>>> and (hopefully) usable collection.  For example, it may be a
>>>> good idea to use (or start with) a set of related profiles
>>>> already in use by an existing protocol in preference to
>>>> mixing/matching individual profiles from multiple existing
>>>> protocols.  At some level, this is common sense advice that
>>>> the presence of profiles in this registry does not obviate
>>>> the need to apply good design judgment, but that does deserve
>>>> to be stated.
> 
> David,
> 
> The type of consistency you look for is extremely difficult to
> ascertain and often rely on mapping the underlying policies.
> However I do see your point. How about this:
> 
> "Protocol designers who want to reference this registry should be
> aware that registered LoAs may depend on assumptions that do not
> carry over to a new protocol."
> 
>>>> 
>>>> Minor issues: (2)
>>>> 
>>>> (1) This draft is intended to be an informational RFC, but it
>>>> uses RFC 2119 keywords.  That's only a good idea in
>>>> exceptional circumstances. I suggest removing section 1.1 and
>>>> replacing upper case MUST/SHOULD/MAY with their lower case
>>>> versions or reworded explanations of rationale.  Most of the
>>>> uses of RFC 2119 keywords are not protocol requirements, but
>>>> requirements on IANA, registrants, and users of the registry
>>>> for which RFC 2119 keywords are not appropriate, e.g., see
>>>> RFC 2119 section 6:
>>>> 
>>>> Imperatives of the type defined in this memo must be used
>>>> with care and sparingly.  In particular, they MUST only be
>>>> used where it is actually required for interoperation or to
>>>> limit behavior which has potential for causing harm (e.g.,
>>>> limiting retransmisssions)
> 
> ok
> 
>>>> 
>>>> (2) Section 4
>>>> 
>>>> OLD The initial pool of expert and the review criteria are
>>>> outlined below. NEW The review criteria are outlined below.
>>>> 
>>>> The initial pool of experts is not designated by this draft.
>>>> 
> 
> good catch
> 
>>>> Nits/editorial comments:
>>>> 
>>>> Section 3
>>>> 
>>>> OLD The following ABNF productions represent reserved values
>>>> and names NEW The reserved element defined by the following
>>>> ABNF productions represents a set of reserved values and
>>>> names
> 
> ok
> 
>>>> 
>>>> Section 4
>>>> 
>>>> The registry is to be operated under the "Designated Expert 
>>>> Review" policy from RFC5226 [RFC5226] employing a pool of
>>>> experts
>>>> 
>>>> Nope, the actual RFC5226 name of that well-known IANA policy
>>>> is Expert Review (or Designated Expert), see section 4.1 of
>>>> RFC5226. If that well-known IANA policy isn't what was
>>>> intended, this is a serious open issue.
> 
> that IANA policy was indeed intended.
> 
>>>> 
>>>> Top of p.7 The presense of an entry in the registy MUST NOT
>>>> be taken to imply ^ r
>>>> ---------------------------------------/
>>>> 
> 
> Here I actually want normative language. It is quite important that
> the registry not be over-interpreted.
> 
>>>> Section 7
>>>> 
>>>> OLD An implementor of MUST NOT treat the registry as a trust 
>>>> framework or NEW A protocol implementor MUST NOT treat the
>>>> registry as a trust framework or
>>>> 
> 
> I actually don't mean protocol implementor here. I mean consumer of
> the registry.
> 
>>>> The minor issue about RFC 2119 keywords also applies to this
>>>> text.
>>>> 
> 
> This is another case where I think I disagree!
> 
>>>> idnits 2.12.13 did not find any nits that need attention.
>>>> 
>>>> Thanks, --David
> 
> thank you!
> 
> Cheers Leif
> 
>>>> ---------------------------------------------------- David
>>>> L. Black, Distinguished Engineer EMC Corporation, 176 South
>>>> St., Hopkinton, MA  01748 +1 (508) 293-7953             FAX:
>>>> +1 (508) 293-7786 david.black@emc.com        Mobile: +1 (978)
>>>> 394-7754 
>>>> ----------------------------------------------------
>>>> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk95UAwACgkQ8Jx8FtbMZnermACfYaNXTG9wfDIfauRXPPV++mal
EVwAoJgNIk/1iXwEBMjURYOpyi3L3SUw
=5XrB
-----END PGP SIGNATURE-----

From magnus.westerlund@ericsson.com  Mon Apr  2 02:00:25 2012
Return-Path: <magnus.westerlund@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 52A8421F88B8 for <gen-art@ietfa.amsl.com>; Mon,  2 Apr 2012 02:00:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UrlQhmUzVSRs for <gen-art@ietfa.amsl.com>; Mon,  2 Apr 2012 02:00:24 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 48D5021F889F for <gen-art@ietf.org>; Mon,  2 Apr 2012 02:00:24 -0700 (PDT)
X-AuditID: c1b4fb2d-b7b76ae0000063d8-b4-4f796aa649a4
Authentication-Results: mailgw1.ericsson.se x-tls.subject="/CN=esessmw0247"; auth=fail (cipher=AES128-SHA)
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client CN "esessmw0247", Issuer "esessmw0247" (not verified)) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 91.26.25560.6AA697F4; Mon,  2 Apr 2012 11:00:23 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.213.0; Mon, 2 Apr 2012 11:00:13 +0200
Message-ID: <4F796A9C.4000800@ericsson.com>
Date: Mon, 2 Apr 2012 11:00:12 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <4F7798E9.2060806@ericsson.com>
In-Reply-To: <4F7798E9.2060806@ericsson.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-avtcore-ecn-for-rtp.all@tools.ietf.org" <draft-ietf-avtcore-ecn-for-rtp.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-avtcore-ecn-for-rtp-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: Mon, 02 Apr 2012 09:00:25 -0000

On 2012-04-01 01:53, Suresh Krishnan wrote:
> I am the assigned Gen-ART reviewer for
> draft-ietf-avtcore-ecn-for-rtp-07.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 Proposed Standard, but I
> have a minor concern that you may like to address.
> 
> Minor
> =====
> 
> * The document uses some addresses in the RFC1918 range as example
> addresses. It would be better to use addresses explicitly reserved for
> documentation (The document does indeed use these addresses as well).
> Specifically I would recommend replacing the RFC1918 address 10.0.1.4
> with an address in the 203.0.113.0/24 range from RFC5735.
> 

Thanks for the review.

I am very well aware of that I am using an none documentation range. The
point of the example is that it is an ICE and ECN SDP signalling
example. When using ICE (RFC5245) it is likely that an end-point will
have an private range address, either in the 10.0.0.0/8 or
192.168.0.0/16 address in their candidate lists. Thus to keep the
example correct considering that the SDP represents a client attached to
a NATed network and have multiple candidates I do need to use a private
range address in this example or it would not make sense.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From christer.holmberg@ericsson.com  Tue Apr  3 12:11:05 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 E77CD11E818E for <gen-art@ietfa.amsl.com>; Tue,  3 Apr 2012 12:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQqGhynw0EIV for <gen-art@ietfa.amsl.com>; Tue,  3 Apr 2012 12:11:05 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id B804411E8180 for <gen-art@ietf.org>; Tue,  3 Apr 2012 12:11:04 -0700 (PDT)
X-AuditID: c1b4fb2d-b7b76ae0000063d8-b7-4f7b4b453e62
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id A3.44.25560.54B4B7F4; Tue,  3 Apr 2012 21:11:02 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.177]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Tue, 3 Apr 2012 21:11:01 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-krb-wg-des-die-die-die.all@tools.ietf.org" <draft-ietf-krb-wg-des-die-die-die.all@tools.ietf.org>
Date: Tue, 3 Apr 2012 21:11:00 +0200
Thread-Topic: Gen-ART LC Review of draft-ietf-krb-wg-des-die-die-die-04
Thread-Index: AQHNEc1uI67oMnyK/0qDS/XjNsuuzA==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C428E2F6D@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-krb-wg-des-die-die-die-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Apr 2012 19:11:06 -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-krb-wg-des-die-die-die-04.txt

Reviewer:                 Christer Holmberg

Review Date:            2012-04-03

IETF LC End Date:    2012-04-08

IESG Telechat date: (if known) -

Summary:           The draft is ready for publication, with an editorial is=
sue.

=20
Major issues:     -

Minor issues:     -

Nits/editorial comments:

- Section 5, which updates the affected RFCs, is named 'Recommendations'. W=
ould it be better to use 'Updates to RFC XXXX' naming instead, and have a s=
eparate section for each RFC updated?

Regards,

Christer

From miguel.a.garcia@ericsson.com  Wed Apr  4 07:39:17 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 4F51121F8711 for <gen-art@ietfa.amsl.com>; Wed,  4 Apr 2012 07:39:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CuPOiVRo+QVn for <gen-art@ietfa.amsl.com>; Wed,  4 Apr 2012 07:39:16 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 6FAC321F86E0 for <gen-art@ietf.org>; Wed,  4 Apr 2012 07:39:16 -0700 (PDT)
X-AuditID: c1b4fb25-b7b18ae000000dce-6e-4f7c5d12f490
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 85.A2.03534.31D5C7F4; Wed,  4 Apr 2012 16:39:15 +0200 (CEST)
Received: from [159.107.48.214] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.213.0; Wed, 4 Apr 2012 16:39:15 +0200
Message-ID: <4F7C5D0F.8070000@ericsson.com>
Date: Wed, 4 Apr 2012 16:39:11 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: j.schoenwaelder@jacobs-university.de,  David Kessens <david.kessens@nsn.com>, Benoit Claise <bclaise@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-netmod-smi-yang-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Apr 2012 14:39:17 -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-netmod-smi-yang-04
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 2012-04-04
IETF LC End Date: 2012-04-12

Summary: The document is ready for publication as a standards track RFC.

Major issues: none

Minor issues: none

Nits/editorial comments: none

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

From alexey.melnikov@isode.com  Wed Apr  4 10:09:00 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 EC91721F8795; Wed,  4 Apr 2012 10:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.351
X-Spam-Level: 
X-Spam-Status: No, score=-102.351 tagged_above=-999 required=5 tests=[AWL=0.248, 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 eYGKjYCr7y1o; Wed,  4 Apr 2012 10:08:59 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id CA04421F876E; Wed,  4 Apr 2012 10:08:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1333559336; d=isode.com; s=selector; i=@isode.com; bh=lJ0YeMTqy8d0Egzm7PDcbVBBLUJn5bvqAPDzNo/6KRg=; 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=ATpjBiTFIxgY3u84fda3YSVGSJpzPWma4lo0MJrq66HB52vgUUuO34aykvGDEW+R3E2Av3 Qg2DCG9pjW1hG8RADWr4KV2BvByyrfk/kxP4O8kf+z0FxZtpNCExHedBiRcBWCn7pT8/K1 vQhGJW9e6hCs4fSDn2OGJWQzDPDN2Lg=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T3yAJwAk6SnJ@rufus.isode.com>; Wed, 4 Apr 2012 18:08:56 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F7C803F.2040308@isode.com>
Date: Wed, 04 Apr 2012 18:09:19 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: j.schoenwaelder@jacobs-university.de, Bob Briscoe <bob.briscoe@bt.com>, Richard Woundy <richard_woundy@cable.comcast.com>, Alissa Cooper <acooper@cdt.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Nandita Dukkipati <nanditad@google.com>, General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-conex-concepts-uses-04.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, 04 Apr 2012 17:09:00 -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-conex-concepts-uses-04.txt
Reviewer: Alexey Melnikov
Review Date: 2012-04-04
IETF LC End Date: 2012-04-12
IESG Review: 2012-04-12

Summary: The document is nearly ready for publication as an 
Informational RFC (see one issue below)


Major issues: none

Minor issues:

This might be pedantic, but I think some of your Informational 
references are actually Normative, because they are needed to understand 
the document. See "IESG Statement: Normative and Informative References" 
for more details 
<http://www.ietf.org/iesg/statement/normative-informative.html>.

This almost doesn't matter for an Informational document, however if any 
of 5 drafts becomes Normative, publication of this document as an RFC 
will be delayed. Still, this might be better than just getting it 
published with "work in progress" references.

But otherwise this is a well written document and I enjoyed reading it.


Nits/editorial comments: none

From bob.briscoe@bt.com  Wed Apr  4 10:45:20 2012
Return-Path: <bob.briscoe@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 6501C11E8072 for <gen-art@ietfa.amsl.com>; Wed,  4 Apr 2012 10:45:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.332
X-Spam-Level: 
X-Spam-Status: No, score=-2.332 tagged_above=-999 required=5 tests=[AWL=0.267,  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 S6iaC5JM-6BM for <gen-art@ietfa.amsl.com>; Wed,  4 Apr 2012 10:45:20 -0700 (PDT)
Received: from hubrelay-by-03.bt.com (hubrelay-by-03.bt.com [62.7.242.139]) by ietfa.amsl.com (Postfix) with ESMTP id EFE5811E808D for <gen-art@ietf.org>; Wed,  4 Apr 2012 10:45:19 -0700 (PDT)
Received: from EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) by EVMHR03-UKBR.bt.com (10.216.161.35) with Microsoft SMTP Server (TLS) id 8.3.159.2; Wed, 4 Apr 2012 18:45:16 +0100
Received: from dyw02134app01.domain1.systemhost.net (193.113.249.13) by EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 4 Apr 2012 18:45:16 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com (147.149.196.177) by dyw02134app01.domain1.systemhost.net (10.35.25.214) with Microsoft SMTP Server id 14.2.247.3; Wed, 4 Apr 2012 18:45:07 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1333561522985; Wed, 4 Apr 2012 18:45:22 +0100
Received: from MUT.jungle.bt.co.uk ([10.215.130.204])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id q34Hj2w6005980; Wed, 4 Apr 2012 18:45:02 +0100
Message-ID: <201204041745.q34Hj2w6005980@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 4 Apr 2012 18:45:06 +0100
To: Alexey Melnikov <alexey.melnikov@isode.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <4F7C803F.2040308@isode.com>
References: <4F7C803F.2040308@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Cc: Nandita Dukkipati <nanditad@google.com>, General Area Review Team <gen-art@ietf.org>, j.schoenwaelder@jacobs-university.de, Alissa Cooper <acooper@cdt.org>, The IESG <iesg@ietf.org>, Richard Woundy <richard_woundy@cable.comcast.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-conex-concepts-uses-04.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, 04 Apr 2012 17:45:20 -0000

Alexey,

Thanks for your review - we are all indebted to people like you who 
commit to review stuff that you don't necessarily have an interest in.


We're concerned if you think the doc isn't understandable without 
reading the I-D refs. This is meant to be the entry-point to the set 
of ConEx documentation, so we intended it to be understandable 
without knowing how ConEx works (beyond the high level description in 
the introduction). "Understandable" here means sufficient to satisfy 
the stated purpose of the doc, which is to motivate ConEx (not to 
understand how it works).

The refs are intended to be used the other way round - having read 
this, you should be motivated to go and read more, so it provides 
pointers to what's available.

Are you sure the need to read the refs is not a symptom of your 
(natural) curiosity to know how ConEx works? Is it really necessary 
to know the details of how ConEx works to understand the motivation 
for building it?

The second paragraph sets out the purpose of the doc:
"
    This document provides the entry point to the set of documentation
    about the Congestion Exposure (ConEx) protocol.  It focuses on the
    motivation for including a ConEx marking at the IP layer.  (A
    companion document, [I-D.ietf-conex-abstract-mech], focuses on the
    mechanics of the protocol.)
"


Bob

At 18:09 04/04/2012, Alexey Melnikov wrote:
>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-conex-concepts-uses-04.txt
>Reviewer: Alexey Melnikov
>Review Date: 2012-04-04
>IETF LC End Date: 2012-04-12
>IESG Review: 2012-04-12
>
>Summary: The document is nearly ready for publication as an 
>Informational RFC (see one issue below)
>
>
>Major issues: none
>
>Minor issues:
>
>This might be pedantic, but I think some of your Informational 
>references are actually Normative, because they are needed to 
>understand the document. See "IESG Statement: Normative and 
>Informative References" for more details 
><http://www.ietf.org/iesg/statement/normative-informative.html>.
>
>This almost doesn't matter for an Informational document, however if 
>any of 5 drafts becomes Normative, publication of this document as 
>an RFC will be delayed. Still, this might be better than just 
>getting it published with "work in progress" references.
>
>But otherwise this is a well written document and I enjoyed reading it.
>
>
>Nits/editorial comments: none

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design 


From stockhammer@nomor.de  Wed Apr  4 11:27:34 2012
Return-Path: <stockhammer@nomor.de>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 704C621F8762 for <gen-art@ietfa.amsl.com>; Wed,  4 Apr 2012 11:27:34 -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 uisdCpP9pd8I for <gen-art@ietfa.amsl.com>; Wed,  4 Apr 2012 11:27:33 -0700 (PDT)
Received: from mo-p00-ob6.rzone.de (mo-p00-ob6.rzone.de [IPv6:2a01:238:20a:202:53f0::1]) by ietfa.amsl.com (Postfix) with ESMTP id 36BBC21F8755 for <gen-art@ietf.org>; Wed,  4 Apr 2012 11:27:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1333564049; l=3259; s=domk; d=nomor.de; h=To:References:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From: Content-Type:Mime-Version:Subject:X-RZG-CLASS-ID:X-RZG-AUTH; bh=Dom1juNT9vaCDoCXT59jFfxKHkw=; b=MLyc02DobcapBA5KZSQobgfYwlXjtUWVZbHULe5ARZGPKQksxOsPn9zNgLdiHLnUONQ wUzt63DJrtj+gmit6mVrTyhixY75ujcbCY10SFU80reHr+D9fW5K0F4/EgxVMr42W8SeK 7mFGVHJw53L53pq4MqaJiJHItMsiRD+L2jo=
X-RZG-AUTH: :P3gLdkugevKirJkjH/RoTtk5THWq6nlFgKpnuMPeiu1/8loZf+4JHTB1Efz/7Ks9
X-RZG-CLASS-ID: mo00
Received: from [192.168.1.13] (188-192-154-212-dynip.superkabel.de [188.192.154.212]) by smtp.strato.de (fruni mo6) (RZmta 28.6 DYNA|AUTH) with ESMTPA id z0551eo34HvmCh ; Wed, 4 Apr 2012 20:27:08 +0200 (MEST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Thomas Stockhammer <stockhammer@nomor.de>
In-Reply-To: <AE31510960917D478171C79369B660FA0E31E2A66A@MX06A.corp.emc.com>
Date: Wed, 4 Apr 2012 20:27:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F249E67-E796-42EF-AF0E-9A20B4C40E2D@nomor.de>
References: <AE31510960917D478171C79369B660FA0E31E2A66A@MX06A.corp.emc.com>
To: <kathleen.moriarty@emc.com> <kathleen.moriarty@emc.com>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Wed, 04 Apr 2012 11:28:52 -0700
Cc: gen-art@ietf.org, watsonm@netflix.com, draft-watson-fecframe-raptor.all@tools.ietf.org, luby@qualcomm.com
Subject: Re: [Gen-art] Gen-ART Review of draft-watson-fecframe-raptor-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Apr 2012 18:27:34 -0000

Kathleen,

thanks! I have updated the draft accordingly.
I am waiting for direction from your document shepherd or AD before =
posting a new version of the draft.

Thomas

On Mar 19, 2012, at 3:42 AM, <kathleen.moriarty@emc.com> =
<kathleen.moriarty@emc.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: =
draft-watson-fecframe-raptor<https://datatracker.ietf.org/doc/draft-watson=
-fecframe-raptor/>-10
> Reviewer: Kathleen Moriarty
> Review Date: 3/18/12
> IETF LC End Date:
> IESG Telechat date: (if known)
>=20
> Summary:  There are minor nits that should be resolved.
>   This document describes Fully-Specified Forward Error Correction
>   (FEC) Schemes for the Raptor and RaptorQ codes and their application
>   to reliable delivery of media streams in the context of FEC
>   Framework.
>=20
>=20
> Major issues:
>=20
> Minor issues:
>=20
> Nits/editorial comments:
> Introduction:  Consider changing the first sentence to introduce the =
acronym FEC:
> The FEC Framework [RFC6363] describes a general framework for the use
>   of Forward Error Correction in association with arbitrary packet =
flows.
> TO: The Forward Error Correction (FEC) Framework [RFC6363] describes a =
general framework for the use
>   of FEC in association with arbitrary packet flows.
>=20
> Second paragraph:  Consider reducing the number of transition phrases:
> From:  The FEC protection mechanism is independent of the type of the =
source
>   data, which can be an arbitrary sequence of packets, including for
>   example audio or video data.
> To: The FEC protection mechanism is independent of the type of the =
source
>   data, which can be an arbitrary sequence of packets, for
>   example audio or video data.
> Third bullet: define RTP
>=20
> Section 2, second and third bullets,  Add a space after 'Section 6'
>=20
> Section 4.2, add a colon after MSBL
>=20
> Section 6.2.1.2:  There appears to be two spaces after MSBL in the =
second paragraph
>=20
> Section 6.2.2:  There is a  '.' Out of place before Figure 2
> In the paragraph after both figure 2 and 3, the trailing 'to' at the =
end of the sentence isn't necessary.
>=20
> Section 6.2.3:
> In the paragraph after both figure 4 and 5, the trailing 'to' at the =
end of the sentence isn't necessary.
>=20
> Section 7.4:  Consider breaking the second sentence into multiple =
sentences.
>=20
> Second paragraph, second sentence, consider using commas instead of =
dashes:
> The
>   MSBL parameter, and hence the number of symbols used in the FEC
>   Encoding and Decoding operations, SHALL be set to one of the
>   following values:
>=20
>=20
>=20
>=20

---
Dr. Thomas Stockhammer (CEO) || stockhammer@nomor.de || phone +49 89 =
978980 02 || cell +491725702667 || http://www.nomor-research.com
Nomor Research GmbH  -  Sitz der Gesellschaft: M=FCnchen - =
Registergericht: M=FCnchen, HRB 165856 =96 Umsatzsteuer-ID: DE238047637 =
- Gesch=E4ftsf=FChrer: Dr. Thomas Stockhammer, Dr. Ingo Viering.








From ben@nostrum.com  Wed Apr  4 15:05:22 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 E45C611E80EC; Wed,  4 Apr 2012 15:05:22 -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 EKCoaT8le8o7; Wed,  4 Apr 2012 15:05: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 2DD7511E80D9; Wed,  4 Apr 2012 15:05:19 -0700 (PDT)
Received: from frankenstein.test.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q34M5GvQ080380 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 4 Apr 2012 17:05:18 -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: Wed, 4 Apr 2012 17:05:15 -0500
Message-Id: <D4F3F164-20B5-4115-A114-909C97EC1984@nostrum.com>
To: draft-ietf-tcpm-3517bis.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-tcpm-3517bis-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Apr 2012 22:05: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 resolve these comments along with any other Last Call comments =
you may receive.

Document: draft-ietf-tcpm-3517bis-02
Reviewer: Ben Campbell
Review Date: 2012-04-04
IETF LC End Date: 2012-04-11

Summary: Essentially ready for publication. I've got a few editorial =
comments and nits that might should be considered prior to publication.

Major issues:

None

Minor issues:

None

Nits/editorial comments:

-- IDNits reports some issues--please check.

-- The headers say the draft obsoletes 3517, but this is not mentioned =
in the abstract. The introduction says this is a revision of 3517, which =
is a bit ambiguous as to whether "revise" means to "obsolete" or =
"update".

-- Abstract: Any reason not to put the abstract on the first page as is =
currently conventional?

-- section 1, 2nd paragraph, [RFC793]

Consider moving the reference to the first TCP mention.

-- section 1, 2nd paragraph, 2nd to last sentence: "Alternate SACK-based =
loss recovery methods can be used in TCP as implementers see fit (as =
long as the alternate algorithms follow the guidelines provided in =
[RFC5681])."

This seems redundant with the first sentence in the paragraph.

-- section 2, definition of "Pipe": 'The algorithm is often referred to =
as the "pipe algorithm"'

Which algorithm? The one in this document? The "fundamentally different =
one"?

-- section 4:

Please expand SMSS on first mention.







From tlyu@mit.edu  Thu Apr  5 07:46:14 2012
Return-Path: <tlyu@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08A8421F86A4 for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 07:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.099
X-Spam-Level: 
X-Spam-Status: No, score=-104.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cngwgKJhME5r for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 07:46:13 -0700 (PDT)
Received: from dmz-mailsec-scanner-3.mit.edu (DMZ-MAILSEC-SCANNER-3.MIT.EDU [18.9.25.14]) by ietfa.amsl.com (Postfix) with ESMTP id 5863121F866A for <gen-art@ietf.org>; Thu,  5 Apr 2012 07:46:13 -0700 (PDT)
X-AuditID: 1209190e-b7f7c6d0000008c3-b8-4f7db034aefa
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id EE.37.02243.430BD7F4; Thu,  5 Apr 2012 10:46:12 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id q35EkB2F003954;  Thu, 5 Apr 2012 10:46:11 -0400
Received: from cathode-dark-space.mit.edu (CATHODE-DARK-SPACE.MIT.EDU [18.18.1.96]) (authenticated bits=56) (User authenticated as tlyu@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q35Ek8O4008865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 5 Apr 2012 10:46:09 -0400 (EDT)
Received: (from tlyu@localhost) by cathode-dark-space.mit.edu (8.12.9.20060308) id q35Ek80n025964; Thu, 5 Apr 2012 10:46:08 -0400 (EDT)
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7F2072F1E0DE894DA4B517B93C6A05852C428E2F6D@ESESSCMS0356.eemea.ericsson.se>
From: Tom Yu <tlyu@MIT.EDU>
Date: Thu, 05 Apr 2012 10:46:08 -0400
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852C428E2F6D@ESESSCMS0356.eemea.ericsson.se> (Christer Holmberg's message of "Tue, 3 Apr 2012 21:11:00 +0200")
Message-ID: <ldvaa2qjky7.fsf@cathode-dark-space.mit.edu>
Lines: 15
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOIsWRmVeSWpSXmKPExsUixCmqrGuyodbfYMFXLYsLMw8zWkx6/4/N 4uqrzywOzB6/vl5l81iy5CeTx5fLn9kCmKO4bFJSczLLUov07RK4Mnatb2IseMla0X27ib2B 8R5LFyMnh4SAicTMLfvYIWwxiQv31rN1MXJxCAnsY5T4feY9K4SznlFi54IbYB1CApeZJO7e 04FIdDJKXOs4xASSEBEwk7j+uZcJJMEssJBR4sa+56wgCWEBN4nFE/4wQ3SHS5xofAY0iYOD TUBa4ujiMpAwi4CqxJNPu8C2cQrMYpSY9/MgO0gNr4CFxNWLCiA1PAKcEk1LdoON4RUQlDg5 8wnYQcwCWhI3/r1kmsAoOAtJahaS1AJGplWMsim5Vbq5iZk5xanJusXJiXl5qUW6xnq5mSV6 qSmlmxjB4SvJt4Px60GlQ4wCHIxKPLxak2v8hVgTy4orcw8xSnIwKYnyyq2r9RfiS8pPqcxI LM6ILyrNSS0+xCjBwawkwis4CyjHm5JYWZValA+TkuZgURLnVdN65yckkJ5YkpqdmlqQWgST leHgUJLgnbUeqFGwKDU9tSItM6cEIc3EwQkynAdo+DKQGt7igsTc4sx0iPwpRkUpcd56kIQA SCKjNA+uF5ZeXjGKA70izNsGUsUDTE1w3a+ABjMBDT75tRpkcEkiQkqqgdG7LupqwL7i6i0d 81YFfnqu3idq+UFuZemG1Ji68A2ZNRLbm9ytDjWG663nCJ9V07n2ZMzaT4EZca8y3/1L4j20 Tzvwrp7rR+FQ9S9mu0TDuz+LtiYKMX7/vNQ4rkRt3s2tDzrCuLeni+s6r3r5/Wf+KyPPfewX mXoucE284l7FcFLRb2nyfSWW4oxEQy3mouJEAAfhrmcKAwAA
X-Mailman-Approved-At: Thu, 05 Apr 2012 07:47:28 -0700
Cc: "draft-ietf-krb-wg-des-die-die-die.all@tools.ietf.org" <draft-ietf-krb-wg-des-die-die-die.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-krb-wg-des-die-die-die-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, 05 Apr 2012 14:46:14 -0000

Christer Holmberg <christer.holmberg@ericsson.com> writes:

> Nits/editorial comments:
>
> - Section 5, which updates the affected RFCs, is named 'Recommendations'. Would it be better to use 'Updates to RFC XXXX' naming instead, and have a separate section for each RFC updated?

The paragraphs in Section 5 are roughly grouped by the type of
algorithm they refer to, which seems logical to me.  Do you believe
that other readers would prefer that the updates be grouped by the
affected RFC?

I should be able to rearrange the contents of Section 5 with
subsection headings of "Updates to RFC XXXX" with minimal textual
changes.  Section 5 might also be better titled "Actions" or "Updates
to specifications".  What do you think?

From hartmans@mit.edu  Thu Apr  5 08:01:34 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCA5A21F8542 for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 08:01:34 -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 YV-CsWByb2zb for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 08:01:34 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2B75C21F850D for <gen-art@ietf.org>; Thu,  5 Apr 2012 08:01:32 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id D57482014A; Thu,  5 Apr 2012 11:00:37 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 30D1E4766; Thu,  5 Apr 2012 11:01:21 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Tom Yu <tlyu@MIT.EDU>
References: <7F2072F1E0DE894DA4B517B93C6A05852C428E2F6D@ESESSCMS0356.eemea.ericsson.se> <ldvaa2qjky7.fsf@cathode-dark-space.mit.edu>
Date: Thu, 05 Apr 2012 11:01:21 -0400
In-Reply-To: <ldvaa2qjky7.fsf@cathode-dark-space.mit.edu> (Tom Yu's message of "Thu, 05 Apr 2012 10:46:08 -0400")
Message-ID: <tslwr5uql32.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "draft-ietf-krb-wg-des-die-die-die.all@tools.ietf.org" <draft-ietf-krb-wg-des-die-die-die.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-krb-wg-des-die-die-die-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, 05 Apr 2012 15:01:35 -0000

My peresonal preference is to retain Recommendations as the title to
section 5.
I have no opinion on whether adding subsections would be a good idea or
not.
It's probably not worth spinning a new draft for that but if people
believe it desirable it's fine to fold in with other changes in my
opinion.
Obviously, wait for direction from our AD.

From suresh.krishnan@ericsson.com  Thu Apr  5 08:19:02 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 26B3421F86D9 for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 08:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLscUmic7hQx for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 08:19:01 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 60B4C21F865D for <gen-art@ietf.org>; Thu,  5 Apr 2012 08:19:01 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q35FIpPS000809; Thu, 5 Apr 2012 10:19:00 -0500
Received: from [142.133.112.66] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.32) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 5 Apr 2012 11:18:50 -0400
Message-ID: <4F7DB7D9.8000904@ericsson.com>
Date: Thu, 5 Apr 2012 11:18:49 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120310 Thunderbird/11.0
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <4F7798E9.2060806@ericsson.com> <4F796A9C.4000800@ericsson.com>
In-Reply-To: <4F796A9C.4000800@ericsson.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-avtcore-ecn-for-rtp.all@tools.ietf.org" <draft-ietf-avtcore-ecn-for-rtp.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-avtcore-ecn-for-rtp-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, 05 Apr 2012 15:19:02 -0000

Hi Magnus,

On 04/02/2012 05:00 AM, Magnus Westerlund wrote:
> On 2012-04-01 01:53, Suresh Krishnan wrote:
>> I am the assigned Gen-ART reviewer for
>> draft-ietf-avtcore-ecn-for-rtp-07.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 Proposed Standard, but I
>> have a minor concern that you may like to address.
>>
>> Minor
>> =====
>>
>> * The document uses some addresses in the RFC1918 range as example
>> addresses. It would be better to use addresses explicitly reserved for
>> documentation (The document does indeed use these addresses as well).
>> Specifically I would recommend replacing the RFC1918 address 10.0.1.4
>> with an address in the 203.0.113.0/24 range from RFC5735.
>>
> 
> Thanks for the review.
> 
> I am very well aware of that I am using an none documentation range. The
> point of the example is that it is an ICE and ECN SDP signalling
> example. When using ICE (RFC5245) it is likely that an end-point will
> have an private range address, either in the 10.0.0.0/8 or
> 192.168.0.0/16 address in their candidate lists. Thus to keep the
> example correct considering that the SDP represents a client attached to
> a NATed network and have multiple candidates I do need to use a private
> range address in this example or it would not make sense.

That makes sense. Too bad there is no documentation addresses set aside
for denoting private space.

Cheers
Suresh

From stbryant@cisco.com  Thu Apr  5 10:02:29 2012
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5C6D21F86DF; Thu,  5 Apr 2012 10:02:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.224
X-Spam-Level: 
X-Spam-Status: No, score=-110.224 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iBffbiD5jm0U; Thu,  5 Apr 2012 10:02:28 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1AC21F8648; Thu,  5 Apr 2012 10:02:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=3344; q=dns/txt; s=iport; t=1333645348; x=1334854948; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=rAPEzZXb4tzeoXKa08Qn+Y+j+LGaIYaHJqzFXK4VNcI=; b=VxDD1E0eCo13r6jFbdxfJvXz4s8YdbUzbaWIfON583iIrQzYqeBp39pj kXxQ7i1yxgfyjhnug/X0dIPKXy7n4AIMv3DgMdRoE8Hav6J6KZZXKb2t/ 5K/RUq1Ndzb0fx7WZj2bchxZG2e1yDOHBTykV27Rt4/ejXr37/alnI8cr I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAD7PfU+Q/khR/2dsb2JhbABFhW+zAIEHggkBAQEEEgECDhVAARALFAQCAgUWCwICCQMCAQIBRQYNAQcBAR6HbAubA4M8EIk8kmeBL44TgRgElWuBEY06gQJngmg
X-IronPort-AV: E=Sophos;i="4.75,377,1330905600"; d="scan'208";a="134423395"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 05 Apr 2012 17:02:27 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q35H2RQg023880; Thu, 5 Apr 2012 17:02:27 GMT
Received: from dhcp-bdlk10-data-vlan300-64-103-107-147.cisco.com (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q35H2PVe028809; Thu, 5 Apr 2012 18:02:25 +0100 (BST)
Message-ID: <4F7DD021.4070807@cisco.com>
Date: Thu, 05 Apr 2012 18:02:25 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <CABkgnnWefLUiSfxyEZpMck9moFeu7wHWk9-yAgHKDukLAt7EiQ@mail.gmail.com>
In-Reply-To: <CABkgnnWefLUiSfxyEZpMck9moFeu7wHWk9-yAgHKDukLAt7EiQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-pwe3-redundancy.all@tools.ietf.org, gen-art@ietf.org, pwe3 <pwe3@ietf.org>, IETF Discussion <ietf@ietf.org>
Subject: Re: [Gen-art] GenART review of draft-ietf-pwe3-redundancy-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Apr 2012 17:02:29 -0000

Authors

Please can you answer or address these comments

Thanks

Stewart

On 16/03/2012 03:06, Martin Thomson wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-pwe3-redundancy-06
> Reviewer: Martin Thomson
> Review Date: 2012-03-15
> IETF LC End Date: 2012-03-21
> IESG Telechat date: (if known)
>
> Summary: The draft has some minor issues.
>
> Major issues: none
>
> Minor issues:
>
> 3.2.2 states: "The mechanisms for achieving this selection are outside
> the scope of this document."
>
> The example then describes the _conditions_ under which the selection
> is made.  So the statement doesn't quite make sense.  It's reasonable
> to presume that a standard doesn't prescribe the internal behaviour of
> a PE where interoperability is no concern.  Even though this is just
> an example, it makes a very specific presumption about the behaviour
> of the PE in reaction to an event.  I can't imagine any other reaction
> in this case, so I'm left wondering: what exactly is out of scope for
> this?  Communication of the event between PE1 and PE2?
>
> Section 4.1: "Non-revertive behavior MUST be supported, while
> revertive behavior is OPTIONAL."
>
> The reason for this requirement is non-obvious (at least to me).  Some
> justification for it seems appropriate.
>
> Section 4.1:    "Protection switchover can be triggered by the operator [...]"
>
> Again, justification would be nice.  This actually smells more like a
> product specification that requirement for interoperability.  If the
> requirement is, as I suspect, that switchovers triggered by manual
> intervention can be marked as such in the protocol _so that they can
> be treated with lower priority_, then that is definitely
> understandable.
>
> Section 4.2:    "[...] MUST support the configuration of revertive or
> non-revertive protection switching modes."
>
> If revertive switching is optional, then this requirement makes not
> sense for (T-)PEs that don't implement it.
>
> Nits:
> The figures are somewhat difficult to read overall.  It's unclear what
> significance is attached to the dots in many of the diagrams, since
> they aren't always consistent (see Figure 3).
> Figure 5 is especially difficult to read.  Another instance is the
> choice of '.' or '|' in Figure 4, which could have some significance,
> but probably doesn't because the usage is quite inconsistent.  Having
> labels for lines/tunnels impinge on boxes is difficult to interpret.
> Reducing the noise in the diagrams would help.  The text is adequate
> to make up the shortfall.  (Figure 7 is perfectly clear.)
>
> Labeling of PEs in 3.2.2 makes it hard to follow because PE2 is
> attached to CE2.  I'd suggest renames such that you have {CE1, PE1a,
> PE1b} and likewise.
>
> The first requirement in 4.1 is missing a couple of spaces (after the
> comma, in "besupported").
>
> 4.2 has an empty bullet.
>
> Not expanded on first use: PSN, LDP
>


-- 
For corporate legal information go to:

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



From christer.holmberg@ericsson.com  Thu Apr  5 15:20:45 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 3945421F8629 for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 15:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EkW4Xxqmypln for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 15:20:44 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 148F121F85C0 for <gen-art@ietf.org>; Thu,  5 Apr 2012 15:20:43 -0700 (PDT)
X-AuditID: c1b4fb25-b7b18ae000000dce-3f-4f7e1abac37d
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 06.D1.03534.ABA1E7F4; Fri,  6 Apr 2012 00:20:42 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.177]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Fri, 6 Apr 2012 00:20:41 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Sam Hartman <hartmans-ietf@mit.edu>, Tom Yu <tlyu@MIT.EDU>
Date: Fri, 6 Apr 2012 00:17:14 +0200
Thread-Topic: Gen-ART LC Review of draft-ietf-krb-wg-des-die-die-die-04
Thread-Index: Ac0TPP1nIhmyh61gRnCCnJ3/RdcT2gAPN2N3
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C428E2F72@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A05852C428E2F6D@ESESSCMS0356.eemea.ericsson.se> <ldvaa2qjky7.fsf@cathode-dark-space.mit.edu>, <tslwr5uql32.fsf@mit.edu>
In-Reply-To: <tslwr5uql32.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-krb-wg-des-die-die-die.all@tools.ietf.org" <draft-ietf-krb-wg-des-die-die-die.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-krb-wg-des-die-die-die-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, 05 Apr 2012 22:20:45 -0000

Hi,

I think it's good to have separate (sub-)sections per RFC. Also, if some sp=
ecific section of an RFC is updated, it is sometimes good to mention, depen=
ding on how difficult it will be for a reader to "map" the updates into the=
 RFCs.

Things may be obvious to people who have worked with the RFCs, and know the=
m by heart, but we have to think about the first-time readers/implementors =
:)

Also, I think "Recommendations" sounds confusing. The "recommend" wording n=
ormally has another meaning in RFCs. And, you are not recommending anything=
 - you are specifying.

Regards,

Christer

________________________________________
From: Sam Hartman [hartmans-ietf@mit.edu]
Sent: Thursday, April 05, 2012 6:01 PM
To: Tom Yu
Cc: Christer Holmberg; gen-art@ietf.org; draft-ietf-krb-wg-des-die-die-die.=
all@tools.ietf.org
Subject: Re: Gen-ART LC Review of draft-ietf-krb-wg-des-die-die-die-04

My peresonal preference is to retain Recommendations as the title to
section 5.
I have no opinion on whether adding subsections would be a good idea or
not.
It's probably not worth spinning a new draft for that but if people
believe it desirable it's fine to fold in with other changes in my
opinion.
Obviously, wait for direction from our AD.=

From mahoney@nostrum.com  Thu Apr  5 16:15:41 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 B4D1C21F86CB for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 16:15:41 -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 WYfPl4xeZRNa for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 16:15:41 -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 3F90C21F869E for <gen-art@ietf.org>; Thu,  5 Apr 2012 16:15:41 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-125-181.dllstx.fios.verizon.net [71.170.125.181]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q35NFeeO031542 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 5 Apr 2012 18:15:40 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4F7E279C.3030707@nostrum.com>
Date: Thu, 05 Apr 2012 18:15:40 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120313 Thunderbird/11.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: 71.170.125.181 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-04-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, 05 Apr 2012 23:15:41 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft

Joel Halpern          2012-04-16  draft-ietf-manet-nhdp-mib-12

Kathleen Moriarty     2012-04-13  draft-ietf-appsawg-greylisting-06


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

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


The standard template is included below.

Thanks,

Jean

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

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

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

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From mahoney@nostrum.com  Thu Apr  5 16:17:32 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 97E4121F872B for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 16:17:32 -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 Faqs2banrySx for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 16:17:32 -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 016DB21F8724 for <gen-art@ietf.org>; Thu,  5 Apr 2012 16:17:31 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-125-181.dllstx.fios.verizon.net [71.170.125.181]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q35NHVqv031649 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 5 Apr 2012 18:17:31 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4F7E280B.1050500@nostrum.com>
Date: Thu, 05 Apr 2012 18:17:31 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120313 Thunderbird/11.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: 71.170.125.181 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-04-12 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, 05 Apr 2012 23:17:32 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft

Alexey Melnikov        2012-02-07  draft-ietf-oauth-v2-bearer-18
Alexey Melnikov        2012-04-12  draft-ietf-conex-concepts-uses-04*

Ben Campbell           2012-03-19  draft-ietf-ippm-rt-loss-03
Ben Campbell           2012-04-11  draft-ietf-tcpm-3517bis-02*

Christer Holmberg      2012-04-09  draft-jivsov-openpgp-ecc-11

David Black            2012-04-03  draft-johansson-loa-registry-04*

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

Francis Dupont         2012-04-11  
draft-ietf-dhc-dhcpv6-reconfigure-rebind-09
Francis Dupont         2012-03-26  
draft-ietf-avtcore-feedback-supression-rtp-16

Joel Halpern           2012-03-26  draft-ietf-bmwg-ipflow-meth-09*

Mary Barnes            2012-03-21  draft-ietf-pwe3-pw-typed-wc-fec-03

Martin Thomson         2012-03-06  draft-george-travel-faq-05

Richard Barnes         2012-02-07  draft-ietf-oauth-v2-25
Richard Barnes         2012-03-12  draft-ietf-hokey-rfc5296bis-06

Roni Even              2012-03-22  
draft-ietf-behave-nat64-learn-analysis-03*
Roni Even              2012-03-30  draft-ietf-ancp-pon-02*

Suresh Krishnan        2012-03-30  draft-ietf-dnsext-rfc2671bis-edns0-08
Suresh Krishnan        2012-03-22  draft-ietf-avtcore-ecn-for-rtp-07*

Vijay Gurbani          2012-03-08  draft-desruisseaux-caldav-sched-12
Vijay Gurbani          2012-01-04  
draft-ietf-softwire-gateway-init-ds-lite-06*

* draft already reviewed.


Spreadsheets have been updated:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

I've also updated the review tool:
http://art.tools.ietf.org/tools/art/genart/

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 Apr  5 16:38:32 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 D3FE621F86C4 for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 16:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.099
X-Spam-Level: 
X-Spam-Status: No, score=-4.099 tagged_above=-999 required=5 tests=[AWL=-0.500, 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 lbqHPJef5NHy for <gen-art@ietfa.amsl.com>; Thu,  5 Apr 2012 16:38:32 -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 248F621F8636 for <gen-art@ietf.org>; Thu,  5 Apr 2012 16:38:31 -0700 (PDT)
Received: by bkuw5 with SMTP id w5so1848343bku.31 for <gen-art@ietf.org>; Thu, 05 Apr 2012 16:38:31 -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=pK+LVuA7VXmmJdlYinq3yzOc8FKpeU/C02+RkO+iLDg=; b=KmSAKE2QwzuFvuOmvc6yQJAAhicAu3Udi9lxbWnaTcVzQnLnz3R6a+T76zLV5Wv71x hmQwcV+NrevwbtdkR8J8UGTP8lRki9ygbAms2ZXK/JD7XB/gNQCqBZIsVTg5YMadgOy8 /5t+otg2/Tu3cUc1Hp1HutkMwY6cCnqhulAmNojniaf5uichVX0U5YqCiM5AEvMqCUJU cGDXJM35ZdpI6NyRtoIdfIDEm47ewhrQ+LpPZyQmug8GUFaHajCrTt9/x7oVdJ0uu7Mb ELjvtg7zNwHE5rSocLczxUeQ+Krtb+BbJMvF/o9HDNAeC6mpUSy2EzdYPwWEg4AR9Av4 we6A==
MIME-Version: 1.0
Received: by 10.204.152.27 with SMTP id e27mr2198833bkw.55.1333669110992; Thu, 05 Apr 2012 16:38:30 -0700 (PDT)
Received: by 10.205.38.73 with HTTP; Thu, 5 Apr 2012 16:38:30 -0700 (PDT)
In-Reply-To: <CABkgnnWu8HaM-EaKbB=_yxNF0Q5k9PyF99yFOcq0S6DxMxFLcA@mail.gmail.com>
References: <CABkgnnWu8HaM-EaKbB=_yxNF0Q5k9PyF99yFOcq0S6DxMxFLcA@mail.gmail.com>
Date: Thu, 5 Apr 2012 16:38:30 -0700
Message-ID: <CABkgnnUCa-TnaZ16ANai0-Ej+KYAsjWypBJirwyQv9ZmNKCo7w@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: draft-george-travel-faq.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-george-travel-faq-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Apr 2012 23:38:32 -0000

-05 is good.

On 10 February 2012 10:15, Martin Thomson <martin.thomson@gmail.com> wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <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-george-travel-faq-03
> Reviewer: Martin Thomson
> Review Date: 2012-02-10
> IETF LC End Date: 2012-03-06
> IESG Telechat date: ?
>
> Summary: Ready
>
> Major issues: none
>
> Minor issues: none
>
> Nits/editorial comments:
> List construction throughout is a little haphazard. Check
> capitalization in particular.
> s/Souvenier/Souvenir/

From jmh@joelhalpern.com  Fri Apr  6 08:58:23 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 9854F21F84E4; Fri,  6 Apr 2012 08:58:23 -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 1XGhbB9he5yN; Fri,  6 Apr 2012 08:58:23 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id F303821F84DC; Fri,  6 Apr 2012 08:58:22 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id B0835A652C; Fri,  6 Apr 2012 08:58:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 57FBC1C5B3F; Fri,  6 Apr 2012 08:58:22 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.100] (pool-71-161-51-182.clppva.btas.verizon.net [71.161.51.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 2F1DA1C08DC; Fri,  6 Apr 2012 08:58:21 -0700 (PDT)
Message-ID: <4F7F12CA.9010009@joelhalpern.com>
Date: Fri, 06 Apr 2012 11:59:06 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
References: <4F7E279C.3030707@nostrum.com>
In-Reply-To: <4F7E279C.3030707@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Adrian Farrel <adrian@olddog.co.uk>, manet@ietf.org, sratliff@cisco.com
Subject: [Gen-art]  review:  draft-ietf-manet-nhdp-mib-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, 06 Apr 2012 15:58: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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-manet-nhdp-mib-12
     Definition of Managed Objects for the
         Neighborhood Discovery Protocol
Reviewer: Joel M. Halpern
Review Date: 6-April-2012
IETF LC End Date: 16-April-2012
IESG Telechat date: (if known)

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

Major issues:
     Section 5.1.3.1 on Ignoring Initial Activity is trying to do a very 
reasonable thing, namely suppress notifications for activity which is 
expected.  The text references RFC 4750 as precedent.  RFC 4750 is clear 
that the suppress window is tied to specific events (interface up and 
election as a DR.)  Section 5.1.3.1 does not specify which condition(s) 
start(s) the suppress window.  If, as seems likely, it is Interface Up 
which starts the window, please state that explicitly in the text.

     In section 5.4, in addition to describing objects which are defined 
in the MIB, the text describes, under the heading "The following objects 
return statistics related to HELLO messages:", a number of what it 
refers to as "Derived Objects".  These do not appear to be actual 
elements of the MIB.  They appear rather to be descriptions of 
calculations which the manager can perform using the information from 
the MIB.  It is not at all clear why they are here.  If I am 
understanding their role properly, and if they belong in this document, 
they belong in some other section, as they are NOT objects which return 
statistics related to HELLO messages.  They appear not to be returned by 
the managed device at all.

Minor issues:
     I can not find the object that corresponds to the setting for 
Ignoring the Initial Activity.  I presume this is my error.  The 
document would be helped if the object were named in section 5.1.3.1.

     I believe section 5.1.3.2 on Throttling Traps is intended to refer 
to the StateChange Threshold and StateChangeWindow objects.  It would be 
very helpful if these were actually named in section 5.1.3.2.

     Most MIBs I review have a description of the tables they contain, 
how the tables relate to each other, and how they are indexed, in the 
front matter that is roughly equivalent to section 5.2, 5.3, and 5.4. 
As I am not a MIB Doctor, I do not know if that is formally required, 
but I find it very helpful, and am surprised not to see it here.

     In looking at the fields in the NhdpInterfaceEntry, some of the 
field definitions include some of the constraints from RFC 6130 section 
5 in their DESCRIPTION clauses.  Some do not.  (For exampple, 
REFRESH_INTERVAL >= HELLO_INTERVAL is captured in nhdbpRefreshInterval, 
but not in nhdpHelloInterval.  The requirement that nhdpHelloInterval be 
greater than 0 is not captured anywhere.  Neither is H_HOLD_TIME >= 
REFRESH_INTERVAL captured.)  Some elements have a statement that the 
object is persistent, while others do not, but these do not seem to 
correspond to a difference in RFC 6130.  It is possible that there is a 
good reason for this apparent variation.  Is there?

     Particularly for top-level objects such as nhdpNHoldTime and 
NhdpIHoldTime I would really like to see a better description than just 
this is <named> object from section 5 of RFC 6130.  Someone who is using 
the MIB, who is looking at the description clause for assistance, really 
needs something more than the name of the field in the MIB.  (I think 
better descriptions would be a good idea through much of the MIB.)

Nits/editorial comments:
     The tracker claims this is "In WG Last Call (manet), but also seems 
to indicate that it is in IETF Last Call.  Are the two happening at the 
same time?

From ron.even.tlv@gmail.com  Sat Apr  7 02:56:04 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 D751C21F8541; Sat,  7 Apr 2012 02:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.338
X-Spam-Level: 
X-Spam-Status: No, score=-3.338 tagged_above=-999 required=5 tests=[AWL=0.260,  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 6ERYMTKJfhmn; Sat,  7 Apr 2012 02:56:02 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 589E621F850B; Sat,  7 Apr 2012 02:56:02 -0700 (PDT)
Received: by werb10 with SMTP id b10so2154168wer.31 for <multiple recipients>; Sat, 07 Apr 2012 02:56:01 -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=I+BgFIi8lfL0Blu+zQu6V+8cMgXaUpH/JKQnZN28U7w=; b=yq6o5N5rZRm0iInIlu502BLycwLGjEgE0XLBmzG5MRE0Q/aCn1CF0PKrgvgD3TjQmO 2il4pMHpxxQu+xAeH+cxdsp52Eathb6OjvN+rmnHydb3dob9gZ3BoFPgXqsN25XQGQns MtvViS3DmNNFu5bd7g9DP6xmtHcTcW9QpyQa1qQECyZSXqpJi8aFd0ctQXVbW4RLa8Ef +xC4LN1FqR7u28FKSvlrqIeLu5TDV2gOIL/T8ADOn8+IDuB6mwEQraMrfxZ8d54WxO/D AxfBu4xgx3dshTvhPG7IKEXeiVmSJjXH3XhnT2Hl3C8xUFyTa9gjr0Zx96Go+s8bwYHv tzhg==
Received: by 10.180.104.65 with SMTP id gc1mr2186264wib.13.1333792561353; Sat, 07 Apr 2012 02:56:01 -0700 (PDT)
Received: from windows8d787f9 ([109.65.204.117]) by mx.google.com with ESMTPS id j3sm21903374wiw.1.2012.04.07.02.55.57 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 07 Apr 2012 02:55:59 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-claise-export-application-info-in-ipfix.all@tools.ietf.org>
Date: Sat, 7 Apr 2012 12:54:31 +0300
Message-ID: <4f800f2f.634cb40a.13a1.ffff8003@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01CD14BD.951D43F0"
X-Mailer: Microsoft Office Outlook 12.0
thread-index: Ac0UpG0cMvU2C0UrT7SzRsZNsOhy0w==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC review of draft-claise-export-application-info-in-ipfix-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Apr 2012 09:56:05 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_001F_01CD14BD.951D43F0
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-claise-export-application-info-in-ipfix-05

Reviewer: Roni Even

Review Date:2012-4-7

IETF LC End Date: 2012-4-17

IESG Telechat date:

 

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

 

Major issues:

 

Minor issues:

 

1.       In sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to
information in Cisco web page. I could not locate and information that is
referenced. The link is to the main Cisco web page. For example in section
6.5 it lists the selectorID as 10000, where is this value located?

2.       For the definition of Classification engine IDs in section 4.1 for
the non standard values like PANA-L3, PANA-L4, PANA-L7, PANA-L2, is there a
requirement that the selector IDs will be publically available?

3.       In section 4.2 "However, an IANA L3 protocol encoding may encoded
with 3 bytes." When is it encoded in 3 bytes, also figure 2 is not
reflecting this example, I expected to see a 32 bit value according to the
text and not a general figure. (small nit in the above sentence "may be"
instead of "may".

4.       In section 7 I noticed that "p2pTechnology, tunnelTechnology, and
encryptedTechnology" are already assigned in the IANA IPFIX Information
elements so why assign them again as new?

5.       In section 7 I noticed that you request that the
applicationDescription, applicationId, applicationName,
classificationEngineId will receive elementid values from the range 0-127.
My reading from section 4.2 is this is not required, maybe add text that
will explain this request.

6.       In the security section are there additional considerations when
the applicationid information is coming from a proprietary classification
engine about authentication of the information source?

 

Nits/editorial comments:

 

1.       In section 4.1 last sentence what is the meaning of "by theses
specifications" , I did not understand the context.

2.       In section 6.6 "to determine whether or the default HTTP port"
delete the "or"

3.       In section 6.6 "The Classification Engine ID is 2" should be "3".

 


------=_NextPart_000_001F_01CD14BD.951D43F0
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 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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;}
@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:1032532832;
	mso-list-type:hybrid;
	mso-list-template-ids:-209704826 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-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1347488741;
	mso-list-type:hybrid;
	mso-list-template-ids:-636856504 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
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><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-clais=
e-export-application-info-in-ipfix-05<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;4&#8211;7<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;4&#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 an Informational =
</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"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 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"'>In =
sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to information in =
Cisco web page. I could not locate and information that is referenced. =
The link is to the main Cisco web page. For example in section 6.5 it =
lists the selectorID as 10000, where is this value =
located?<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<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"'>For the =
definition of Classification engine IDs in section 4.1 for the non =
standard values like PANA-L3, PANA-L4, PANA-L7, PANA-L2, is there a =
requirement that the selector IDs will be publically =
available?</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>3.<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"'>In section =
4.2 &#8220;However, an IANA L3 protocol encoding may encoded with 3 =
bytes.&#8221; When is it encoded in 3 bytes, also figure 2 is not =
reflecting this example, I expected to see a 32 bit value according to =
the text and not a general figure. (small nit in the above sentence =
&#8220;may be&#8221; instead of &#8220;may&#8221;.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>4.<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"'>In section =
7 I noticed that &#8221;p2pTechnology, tunnelTechnology, and =
encryptedTechnology&#8221; are already assigned in the IANA IPFIX =
Information elements so why assign them again as new?</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>5.<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"'>In section =
7 I noticed that you request that the&nbsp; applicationDescription, =
applicationId, applicationName, classificationEngineId will receive =
elementid values from the range 0-127. My reading from section 4.2 is =
this is not required, maybe add text that will explain this =
request.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>6.<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"'>In the =
security section are</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> there =
additional considerations when the applicationid information is coming =
from a proprietary classification engine about authentication of the =
information source?<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"'>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 =
lfo2'><![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"'>In section =
4.1 last sentence what is the meaning of &#8220;by theses =
specifications&#8221; , I did not understand the =
context.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<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"'>In section =
6.6 &#8220;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>to =
determine whether or the default HTTP port&#8221; delete the =
&#8220;or&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>3.<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"'>In section =
6.6 &#8220;The Classification Engine ID is 2&#8221; should be =
&#8220;3&#8221;.<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_001F_01CD14BD.951D43F0--


From mary.ietf.barnes@gmail.com  Mon Apr  9 12:21:47 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 95AE421F87B5 for <gen-art@ietfa.amsl.com>; Mon,  9 Apr 2012 12:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 C8oRk2mfNq9p for <gen-art@ietfa.amsl.com>; Mon,  9 Apr 2012 12:21:46 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7459221F86D4 for <gen-art@ietf.org>; Mon,  9 Apr 2012 12:21:46 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so2420090vcb.31 for <gen-art@ietf.org>; Mon, 09 Apr 2012 12:21:46 -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=0RRe1100zrBRuPOmHILp1ppC24za7bajngG0u5oYiMk=; b=DRFcTtQK4STJ5n4qKKlo5kz11nCNLyVbchdA8zXxqcAFwg2QGqifcr8vmoIXkKzqZ7 RGF6e1bdbDFgeaNz67B+NjuNyiURLU5Xila9s8SkjCJ+efWzOwdbw9arFmrOHIHCGIoM Gz9Fc8fq3lXvvaloW0FjU370kLFt5BtzRn8eYbZh2v4PAUW0JE2irO2PcsO31hcmOui3 xehyxVYKR8vIaObtlyLzQAcEqPoPV6OnPmLltf0Clz1+u9HcVuy/L2srx2Y/WEZCExHr oGzUv0mBRaLqVJgviOATifuXSoacERI+zU4dGQVUn6NeMjhY2jCwjrusI3nqMWqHHMHS SXoA==
MIME-Version: 1.0
Received: by 10.52.72.169 with SMTP id e9mr3446249vdv.21.1333999305987; Mon, 09 Apr 2012 12:21:45 -0700 (PDT)
Received: by 10.52.68.145 with HTTP; Mon, 9 Apr 2012 12:21:45 -0700 (PDT)
Date: Mon, 9 Apr 2012 14:21:45 -0500
Message-ID: <CAHBDyN4-z57zkkc8_thG+PPPso38vZNZy496xNviS+10BPj6_w@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: draft-ietf-pwe3-pw-typed-wc-fec.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=20cf3071d0a2c3978204bd43ea8c
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART review: draft-ietf-pwe3-pw-typed-wc-fec-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: Mon, 09 Apr 2012 19:21:47 -0000

--20cf3071d0a2c3978204bd43ea8c
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

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-pwe3-pw-typed-wc-fec-03.txt
Reviewer:  Mary Barnes
Review Date:  9 April 2012
IESG Telechat Date: 12 April 2012

Summary:  Ready with nits.

Comments: there are some editorial nits, many summarized below.  There are
several cases where an article - i.e., "the", "an", etc. is missing.   I
believe these can be fixed in AUTH48 and I imagine the RFC editor will
catch them. But, if the doc needs any other updates, it would be good to
make these fixes at the same time.

Nits:
-----
Section 1:
- first paragraph, second sentence is very awkward and could be rewritten
something like (unless I've misunderstood the objective of that sentence:
OLD:
   This can be used when it is
   desired to request all label bindings for a given type of FEC
   Element, or to release or withdraw all label bindings for a given
   type of FEC element.
NEW:
   This can be used to request, release or withdraw all label
   bindings for a given type of FEC element.

- second paragraph, last sentence - missing articles (PWID, same)
OLD:
   The procedures for Typed Wildcard processing for PWid and
   Generalized PWid FEC Elements are same as described in [RFC5918] for
   any typed wildcard FEC Element type.
NEW:
   The procedures for Typed Wildcard processing for the PWid and
   Generalized PWid FEC Elements are the same as described in [RFC5918] for
   any typed wildcard FEC Element type.

Section 3:
- third paragraph, last sentence before list:
OLD:
 provide
  more generalized and comprehensive solution by allowing:
NEW:
  provide a
  more generalized and comprehensive solution by allowing:

- list item 2: "constraint" -> "constrain"



Section 4.1:
OLD:
 "=85 had learnt from LSR B over LDP session."
NEW:
 " =85 learned from the LSR B over the LDP session."

OLD:
 "=85such request=85"
NEW:
 "=85such a request=85"  OR "..the request=85"

OLD:
 (no stale)
NEW:
 (not stale)

OLD:
  completes consistency check
NEW:
  completes the consistency check

Section 4.3:
- first paragraph, last sentence:
OLD:
  with large number
NEW:
  with a large number

Section 4.4:
- 1st para, 2nd sentence:
OLD:
   These procedures use LDP Address Withdraw message
NEW:
   These procedures use an LDP Address Withdraw message

- 2nd paragraph, last sentence:
OLD:
  This per PW (VPLS instance) MAC Withdraw messages
NEW:
  These per PW (VPLS instance) MAC Withdraw messages

3rd paragraph - 1st sentence:
OLD:
  this document allows use of
NEW:
  this document allows the use of

--20cf3071d0a2c3978204bd43ea8c
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>I am the assigned Gen-ART reviewer for this draft. For background on</=
div><div>Gen-ART, please see the FAQ at</div><div>&lt; <a href=3D"http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq</a>&gt;.</div>
<div><br></div><div>Please wait for direction from your document shepherd</=
div><div>or AD before posting a new version of the draft.</div><div><br></d=
iv><div>Document: draft-ietf-pwe3-pw-typed-wc-fec-03.txt</div><div>Reviewer=
: =A0Mary Barnes=A0</div>
<div>Review Date: =A09 April 2012</div><div>IESG Telechat Date: 12 April 20=
12</div><div><br></div><div>Summary: =A0Ready with nits.</div><div><br></di=
v><div>Comments: there are some editorial nits, many summarized below. =A0T=
here are several cases where an article - i.e., &quot;the&quot;, &quot;an&q=
uot;, etc. is missing. =A0 I believe these can be fixed in AUTH48 and I ima=
gine the RFC editor will catch them. But, if the doc needs any other update=
s, it would be good to make these fixes at the same time. =A0</div>
<div><br></div><div>Nits:</div><div>-----</div><div>Section 1:=A0</div><div=
>- first paragraph, second sentence is very awkward and could be rewritten =
something like (unless I&#39;ve misunderstood the objective of that sentenc=
e:</div>
<div>OLD:</div><div>=A0 =A0This can be used when it is=A0</div><div>=A0 =A0=
desired to request all label bindings for a given type of FEC=A0</div><div>=
=A0 =A0Element, or to release or withdraw all label bindings for a given=A0=
</div><div>=A0 =A0type of FEC element.=A0</div>
<div>NEW:=A0</div><div>=A0 =A0This can be used to request, release or withd=
raw all label=A0</div><div>=A0 =A0bindings for a given type of FEC element.=
</div><div><br></div><div>- second paragraph, last sentence - missing artic=
les (PWID, same)</div>
<div>OLD:</div><div>=A0 =A0The procedures for Typed Wildcard processing for=
 PWid and =A0</div><div>=A0 =A0Generalized PWid FEC Elements are same as de=
scribed in [RFC5918] for=A0</div><div>=A0 =A0any typed wildcard FEC Element=
 type.</div>
<div>NEW:=A0</div><div>=A0 =A0The procedures for Typed Wildcard processing =
for the PWid and =A0</div><div>=A0 =A0Generalized PWid FEC Elements are the=
 same as described in [RFC5918] for=A0</div><div>=A0 =A0any typed wildcard =
FEC Element type.</div>
<div><br></div><div>Section 3:</div><div>- third paragraph, last sentence b=
efore list:=A0</div><div>OLD:=A0</div><div>=A0provide=A0</div><div>=A0 more=
 generalized and comprehensive solution by allowing:=A0</div><div>NEW:=A0</=
div><div>=A0 provide a</div>
<div>=A0 more generalized and comprehensive solution by allowing:=A0</div><=
div><br></div><div>- list item 2: &quot;constraint&quot; -&gt; &quot;constr=
ain&quot;</div><div><br></div><div><br></div><div><br></div><div>Section 4.=
1:=A0</div>
<div>OLD:</div><div>=A0&quot;=85 had learnt from LSR B over LDP session.&qu=
ot;</div><div>NEW:=A0</div><div>=A0&quot; =85 learned from the LSR B over t=
he LDP session.&quot;</div><div><br></div><div>OLD:</div><div>=A0&quot;=85s=
uch request=85&quot;=A0</div>
<div>NEW:</div><div>=A0&quot;=85such a request=85&quot; =A0OR &quot;..the r=
equest=85&quot;</div><div><br></div><div>OLD:=A0</div><div>=A0(no stale)</d=
iv><div>NEW:=A0</div><div>=A0(not stale)</div><div><br></div><div>OLD:</div=
><div>=A0 completes consistency check</div>
<div>NEW:</div><div>=A0 completes the consistency check</div><div><br></div=
><div>Section 4.3:=A0</div><div>- first paragraph, last sentence: =A0</div>=
<div>OLD:=A0</div><div>=A0 with large number</div><div>NEW:</div><div>=A0 w=
ith a large number</div>
<div><br></div><div>Section 4.4:</div><div>- 1st para, 2nd sentence:</div><=
div>OLD:=A0</div><div>=A0 =A0These procedures use LDP Address Withdraw mess=
age</div><div>NEW:=A0</div><div>=A0 =A0These procedures use an LDP Address =
Withdraw message</div>
<div><br></div><div>- 2nd paragraph, last sentence:</div><div>OLD:</div><di=
v>=A0 This per PW (VPLS instance) MAC Withdraw messages=A0</div><div>NEW:=
=A0</div><div>=A0 These per PW (VPLS instance) MAC Withdraw messages=A0</di=
v><div><br>
</div><div>3rd paragraph - 1st sentence:</div><div>OLD:</div><div>=A0 this =
document allows use of</div><div>NEW:=A0</div><div>=A0 this document allows=
 the use of</div>

--20cf3071d0a2c3978204bd43ea8c--

From cpignata@cisco.com  Mon Apr  9 12:32:11 2012
Return-Path: <cpignata@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99DAD21F879C for <gen-art@ietfa.amsl.com>; Mon,  9 Apr 2012 12:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.531
X-Spam-Level: 
X-Spam-Status: No, score=-108.531 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, 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 5nn-GegK73TM for <gen-art@ietfa.amsl.com>; Mon,  9 Apr 2012 12:32:10 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 55BEE21F867F for <gen-art@ietf.org>; Mon,  9 Apr 2012 12:32:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12030; q=dns/txt; s=iport; t=1333999930; x=1335209530; h=subject:references:content-transfer-encoding:from: in-reply-to:message-id:date:to:cc:mime-version; bh=OFJhoQCkeihSNhy2w0879Sz7L9XNZ4GKA8sJeN8Cjkg=; b=mwvMKZs0uTIHmBlFnlJ4/AfGQwgV4SQSO6HsmkuQN9RjzPdD/o4YVrL7 sL1HfDJH2rfN92D1WvhucA5Kh/WwKGHWpXudqSFeha5P2MyTecmfQ4Hr6 m49+MwSCvX4QbR5b22FMjaQysL9gtSjjZ5sVDNy0ZLJjBPHvnSsZwuobr 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArAIAG04g0+tJV2Z/2dsb2JhbABEhWaBRakQiBqBAAKBB4IJAQEBAwESARAEUgULAgEIFAYCJgICAh82AQEEExsHh14DBgULmgyNC4kkDYlTgS+IfoUmNWMElWyBEYoogxSBaYMD
X-IronPort-AV: E=Sophos;i="4.75,393,1330905600"; d="scan'208,217";a="70232543"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 09 Apr 2012 19:32:09 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q39JW9fo002903;  Mon, 9 Apr 2012 19:32:09 GMT
Received: from xmb-rcd-206.cisco.com ([72.163.62.213]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 9 Apr 2012 14:32:09 -0500
Received: from 72.163.63.13 ([72.163.63.13]) by XMB-RCD-206.cisco.com ([72.163.62.213]) with Microsoft Exchange Server HTTP-DAV ;  Mon,  9 Apr 2012 19:32:09 +0000
References: <CAHBDyN4-z57zkkc8_thG+PPPso38vZNZy496xNviS+10BPj6_w@mail.gmail.com>
Content-Transfer-Encoding: 7bit
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-CB26F6DD-1506-47F2-A7CA-546B2141E33D"; charset="utf-8"
Thread-Topic: Gen-ART review: draft-ietf-pwe3-pw-typed-wc-fec-03
Thread-Index: Ac0Wh3RGOE28fudHTnO0DwXkeLBpLQ==
In-Reply-To: <CAHBDyN4-z57zkkc8_thG+PPPso38vZNZy496xNviS+10BPj6_w@mail.gmail.com>
Message-ID: <BDBE18D9-0584-415D-8262-59D8F070D95E@cisco.com>
Date: Mon, 9 Apr 2012 15:32:05 -0400
To: "Mary Barnes" <mary.ietf.barnes@gmail.com>
MIME-Version: 1.0 (1.0)
X-OriginalArrivalTime: 09 Apr 2012 19:32:09.0415 (UTC) FILETIME=[7479D570:01CD1687]
Cc: gen-art@ietf.org, draft-ietf-pwe3-pw-typed-wc-fec.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review: draft-ietf-pwe3-pw-typed-wc-fec-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: Mon, 09 Apr 2012 19:32:11 -0000

--Apple-Mail-CB26F6DD-1506-47F2-A7CA-546B2141E33D
Content-Transfer-Encoding: base64
Content-Type: text/plain;
	charset=utf-8

VGhhbmsgeW91IE1hcnkgZm9yIHRoZSByZXZpZXcgYW5kIGZvciBjYXRjaGluZyBhbGwgdGhlc2Ug
ZWRpdG9yaWFscyENCg0KVGh1bWIgdHlwZWQgYnkgQ2FybG9zIFBpZ25hdGFyby4NCkV4Y3V6ZSB0
eXBvZnJhcGhpY2FrIGVycm93cw0KDQpPbiBBcHIgOSwgMjAxMiwgYXQgMzoyMiBQTSwgIk1hcnkg
QmFybmVzIiA8bWFyeS5pZXRmLmJhcm5lc0BnbWFpbC5jb20+IHdyb3RlOg0KDQo+IEkgYW0gdGhl
IGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZvciBiYWNrZ3JvdW5k
IG9uDQo+IEdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPiA8IGh0dHA6Ly93aWtpLnRv
b2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0KPiANCj4gUGxlYXNl
IHdhaXQgZm9yIGRpcmVjdGlvbiBmcm9tIHlvdXIgZG9jdW1lbnQgc2hlcGhlcmQNCj4gb3IgQUQg
YmVmb3JlIHBvc3RpbmcgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQo+IA0KPiBEb2N1bWVu
dDogZHJhZnQtaWV0Zi1wd2UzLXB3LXR5cGVkLXdjLWZlYy0wMy50eHQNCj4gUmV2aWV3ZXI6ICBN
YXJ5IEJhcm5lcyANCj4gUmV2aWV3IERhdGU6ICA5IEFwcmlsIDIwMTINCj4gSUVTRyBUZWxlY2hh
dCBEYXRlOiAxMiBBcHJpbCAyMDEyDQo+IA0KPiBTdW1tYXJ5OiAgUmVhZHkgd2l0aCBuaXRzLg0K
PiANCj4gQ29tbWVudHM6IHRoZXJlIGFyZSBzb21lIGVkaXRvcmlhbCBuaXRzLCBtYW55IHN1bW1h
cml6ZWQgYmVsb3cuICBUaGVyZSBhcmUgc2V2ZXJhbCBjYXNlcyB3aGVyZSBhbiBhcnRpY2xlIC0g
aS5lLiwgInRoZSIsICJhbiIsIGV0Yy4gaXMgbWlzc2luZy4gICBJIGJlbGlldmUgdGhlc2UgY2Fu
IGJlIGZpeGVkIGluIEFVVEg0OCBhbmQgSSBpbWFnaW5lIHRoZSBSRkMgZWRpdG9yIHdpbGwgY2F0
Y2ggdGhlbS4gQnV0LCBpZiB0aGUgZG9jIG5lZWRzIGFueSBvdGhlciB1cGRhdGVzLCBpdCB3b3Vs
ZCBiZSBnb29kIHRvIG1ha2UgdGhlc2UgZml4ZXMgYXQgdGhlIHNhbWUgdGltZS4gIA0KPiANCj4g
Tml0czoNCj4gLS0tLS0NCj4gU2VjdGlvbiAxOiANCj4gLSBmaXJzdCBwYXJhZ3JhcGgsIHNlY29u
ZCBzZW50ZW5jZSBpcyB2ZXJ5IGF3a3dhcmQgYW5kIGNvdWxkIGJlIHJld3JpdHRlbiBzb21ldGhp
bmcgbGlrZSAodW5sZXNzIEkndmUgbWlzdW5kZXJzdG9vZCB0aGUgb2JqZWN0aXZlIG9mIHRoYXQg
c2VudGVuY2U6DQo+IE9MRDoNCj4gICAgVGhpcyBjYW4gYmUgdXNlZCB3aGVuIGl0IGlzIA0KPiAg
ICBkZXNpcmVkIHRvIHJlcXVlc3QgYWxsIGxhYmVsIGJpbmRpbmdzIGZvciBhIGdpdmVuIHR5cGUg
b2YgRkVDIA0KPiAgICBFbGVtZW50LCBvciB0byByZWxlYXNlIG9yIHdpdGhkcmF3IGFsbCBsYWJl
bCBiaW5kaW5ncyBmb3IgYSBnaXZlbiANCj4gICAgdHlwZSBvZiBGRUMgZWxlbWVudC4gDQo+IE5F
VzogDQo+ICAgIFRoaXMgY2FuIGJlIHVzZWQgdG8gcmVxdWVzdCwgcmVsZWFzZSBvciB3aXRoZHJh
dyBhbGwgbGFiZWwgDQo+ICAgIGJpbmRpbmdzIGZvciBhIGdpdmVuIHR5cGUgb2YgRkVDIGVsZW1l
bnQuDQo+IA0KPiAtIHNlY29uZCBwYXJhZ3JhcGgsIGxhc3Qgc2VudGVuY2UgLSBtaXNzaW5nIGFy
dGljbGVzIChQV0lELCBzYW1lKQ0KPiBPTEQ6DQo+ICAgIFRoZSBwcm9jZWR1cmVzIGZvciBUeXBl
ZCBXaWxkY2FyZCBwcm9jZXNzaW5nIGZvciBQV2lkIGFuZCAgDQo+ICAgIEdlbmVyYWxpemVkIFBX
aWQgRkVDIEVsZW1lbnRzIGFyZSBzYW1lIGFzIGRlc2NyaWJlZCBpbiBbUkZDNTkxOF0gZm9yIA0K
PiAgICBhbnkgdHlwZWQgd2lsZGNhcmQgRkVDIEVsZW1lbnQgdHlwZS4NCj4gTkVXOiANCj4gICAg
VGhlIHByb2NlZHVyZXMgZm9yIFR5cGVkIFdpbGRjYXJkIHByb2Nlc3NpbmcgZm9yIHRoZSBQV2lk
IGFuZCAgDQo+ICAgIEdlbmVyYWxpemVkIFBXaWQgRkVDIEVsZW1lbnRzIGFyZSB0aGUgc2FtZSBh
cyBkZXNjcmliZWQgaW4gW1JGQzU5MThdIGZvciANCj4gICAgYW55IHR5cGVkIHdpbGRjYXJkIEZF
QyBFbGVtZW50IHR5cGUuDQo+IA0KPiBTZWN0aW9uIDM6DQo+IC0gdGhpcmQgcGFyYWdyYXBoLCBs
YXN0IHNlbnRlbmNlIGJlZm9yZSBsaXN0OiANCj4gT0xEOiANCj4gIHByb3ZpZGUgDQo+ICAgbW9y
ZSBnZW5lcmFsaXplZCBhbmQgY29tcHJlaGVuc2l2ZSBzb2x1dGlvbiBieSBhbGxvd2luZzogDQo+
IE5FVzogDQo+ICAgcHJvdmlkZSBhDQo+ICAgbW9yZSBnZW5lcmFsaXplZCBhbmQgY29tcHJlaGVu
c2l2ZSBzb2x1dGlvbiBieSBhbGxvd2luZzogDQo+IA0KPiAtIGxpc3QgaXRlbSAyOiAiY29uc3Ry
YWludCIgLT4gImNvbnN0cmFpbiINCj4gDQo+IA0KPiANCj4gU2VjdGlvbiA0LjE6IA0KPiBPTEQ6
DQo+ICAi4oCmIGhhZCBsZWFybnQgZnJvbSBMU1IgQiBvdmVyIExEUCBzZXNzaW9uLiINCj4gTkVX
OiANCj4gICIg4oCmIGxlYXJuZWQgZnJvbSB0aGUgTFNSIEIgb3ZlciB0aGUgTERQIHNlc3Npb24u
Ig0KPiANCj4gT0xEOg0KPiAgIuKApnN1Y2ggcmVxdWVzdOKApiIgDQo+IE5FVzoNCj4gICLigKZz
dWNoIGEgcmVxdWVzdOKApiIgIE9SICIuLnRoZSByZXF1ZXN04oCmIg0KPiANCj4gT0xEOiANCj4g
IChubyBzdGFsZSkNCj4gTkVXOiANCj4gIChub3Qgc3RhbGUpDQo+IA0KPiBPTEQ6DQo+ICAgY29t
cGxldGVzIGNvbnNpc3RlbmN5IGNoZWNrDQo+IE5FVzoNCj4gICBjb21wbGV0ZXMgdGhlIGNvbnNp
c3RlbmN5IGNoZWNrDQo+IA0KPiBTZWN0aW9uIDQuMzogDQo+IC0gZmlyc3QgcGFyYWdyYXBoLCBs
YXN0IHNlbnRlbmNlOiAgDQo+IE9MRDogDQo+ICAgd2l0aCBsYXJnZSBudW1iZXINCj4gTkVXOg0K
PiAgIHdpdGggYSBsYXJnZSBudW1iZXINCj4gDQo+IFNlY3Rpb24gNC40Og0KPiAtIDFzdCBwYXJh
LCAybmQgc2VudGVuY2U6DQo+IE9MRDogDQo+ICAgIFRoZXNlIHByb2NlZHVyZXMgdXNlIExEUCBB
ZGRyZXNzIFdpdGhkcmF3IG1lc3NhZ2UNCj4gTkVXOiANCj4gICAgVGhlc2UgcHJvY2VkdXJlcyB1
c2UgYW4gTERQIEFkZHJlc3MgV2l0aGRyYXcgbWVzc2FnZQ0KPiANCj4gLSAybmQgcGFyYWdyYXBo
LCBsYXN0IHNlbnRlbmNlOg0KPiBPTEQ6DQo+ICAgVGhpcyBwZXIgUFcgKFZQTFMgaW5zdGFuY2Up
IE1BQyBXaXRoZHJhdyBtZXNzYWdlcyANCj4gTkVXOiANCj4gICBUaGVzZSBwZXIgUFcgKFZQTFMg
aW5zdGFuY2UpIE1BQyBXaXRoZHJhdyBtZXNzYWdlcyANCj4gDQo+IDNyZCBwYXJhZ3JhcGggLSAx
c3Qgc2VudGVuY2U6DQo+IE9MRDoNCj4gICB0aGlzIGRvY3VtZW50IGFsbG93cyB1c2Ugb2YNCj4g
TkVXOiANCj4gICB0aGlzIGRvY3VtZW50IGFsbG93cyB0aGUgdXNlIG9mDQo=

--Apple-Mail-CB26F6DD-1506-47F2-A7CA-546B2141E33D
Content-Transfer-Encoding: base64
Content-Type: text/html;
	charset=utf-8

PGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5IGJnY29sb3I9IiNGRkZGRkYiPjxkaXY+VGhhbmsgeW91
IE1hcnkgZm9yIHRoZSByZXZpZXcgYW5kIGZvciBjYXRjaGluZyBhbGwgdGhlc2UgZWRpdG9yaWFs
cyE8YnI+PGJyPjxzcGFuIGNsYXNzPSJBcHBsZS1zdHlsZS1zcGFuIiBzdHlsZT0iLXdlYmtpdC10
YXAtaGlnaGxpZ2h0LWNvbG9yOiByZ2JhKDI2LCAyNiwgMjYsIDAuMjk2ODc1KTsgLXdlYmtpdC1j
b21wb3NpdGlvbi1maWxsLWNvbG9yOiByZ2JhKDE3NSwgMTkyLCAyMjcsIDAuMjMwNDY5KTsgLXdl
YmtpdC1jb21wb3NpdGlvbi1mcmFtZS1jb2xvcjogcmdiYSg3NywgMTI4LCAxODAsIDAuMjMwNDY5
KTsgIj5UaHVtYiB0eXBlZCBieSBDYXJsb3MgUGlnbmF0YXJvLjwvc3Bhbj48ZGl2PjxzcGFuIGNs
YXNzPSJBcHBsZS1zdHlsZS1zcGFuIiBzdHlsZT0iLXdlYmtpdC10YXAtaGlnaGxpZ2h0LWNvbG9y
OiByZ2JhKDI2LCAyNiwgMjYsIDAuMjk2ODc1KTsgLXdlYmtpdC1jb21wb3NpdGlvbi1maWxsLWNv
bG9yOiByZ2JhKDE3NSwgMTkyLCAyMjcsIDAuMjMwNDY5KTsgLXdlYmtpdC1jb21wb3NpdGlvbi1m
cmFtZS1jb2xvcjogcmdiYSg3NywgMTI4LCAxODAsIDAuMjMwNDY5KTsgIj5FeGN1emUgdHlwb2Zy
YXBoaWNhayBlcnJvd3M8L3NwYW4+PC9kaXY+PC9kaXY+PGRpdj48YnI+T24gQXByIDksIDIwMTIs
IGF0IDM6MjIgUE0sICJNYXJ5IEJhcm5lcyIgJmx0OzxhIGhyZWY9Im1haWx0bzptYXJ5LmlldGYu
YmFybmVzQGdtYWlsLmNvbSI+bWFyeS5pZXRmLmJhcm5lc0BnbWFpbC5jb208L2E+Jmd0OyB3cm90
ZTo8YnI+PGJyPjwvZGl2PjxkaXY+PC9kaXY+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PGRpdj48
ZGl2PkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZv
ciBiYWNrZ3JvdW5kIG9uPC9kaXY+PGRpdj5HZW4tQVJULCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQ8
L2Rpdj48ZGl2PiZsdDsgPGEgaHJlZj0iaHR0cDovL3dpa2kudG9vbHMuaWV0Zi5vcmcvYXJlYS9n
ZW4vdHJhYy93aWtpL0dlbkFydGZhcSI+aHR0cDovL3dpa2kudG9vbHMuaWV0Zi5vcmcvYXJlYS9n
ZW4vdHJhYy93aWtpL0dlbkFydGZhcTwvYT4mZ3Q7LjwvZGl2Pg0KPGRpdj48YnI+PC9kaXY+PGRp
dj5QbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZyb20geW91ciBkb2N1bWVudCBzaGVwaGVyZDwv
ZGl2PjxkaXY+b3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQu
PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5Eb2N1bWVudDogZHJhZnQtaWV0Zi1wd2UzLXB3LXR5
cGVkLXdjLWZlYy0wMy50eHQ8L2Rpdj48ZGl2PlJldmlld2VyOiAmbmJzcDtNYXJ5IEJhcm5lcyZu
YnNwOzwvZGl2Pg0KPGRpdj5SZXZpZXcgRGF0ZTogJm5ic3A7OSBBcHJpbCAyMDEyPC9kaXY+PGRp
dj5JRVNHIFRlbGVjaGF0IERhdGU6IDEyIEFwcmlsIDIwMTI8L2Rpdj48ZGl2Pjxicj48L2Rpdj48
ZGl2PlN1bW1hcnk6ICZuYnNwO1JlYWR5IHdpdGggbml0cy48L2Rpdj48ZGl2Pjxicj48L2Rpdj48
ZGl2PkNvbW1lbnRzOiB0aGVyZSBhcmUgc29tZSBlZGl0b3JpYWwgbml0cywgbWFueSBzdW1tYXJp
emVkIGJlbG93LiAmbmJzcDtUaGVyZSBhcmUgc2V2ZXJhbCBjYXNlcyB3aGVyZSBhbiBhcnRpY2xl
IC0gaS5lLiwgInRoZSIsICJhbiIsIGV0Yy4gaXMgbWlzc2luZy4gJm5ic3A7IEkgYmVsaWV2ZSB0
aGVzZSBjYW4gYmUgZml4ZWQgaW4gQVVUSDQ4IGFuZCBJIGltYWdpbmUgdGhlIFJGQyBlZGl0b3Ig
d2lsbCBjYXRjaCB0aGVtLiBCdXQsIGlmIHRoZSBkb2MgbmVlZHMgYW55IG90aGVyIHVwZGF0ZXMs
IGl0IHdvdWxkIGJlIGdvb2QgdG8gbWFrZSB0aGVzZSBmaXhlcyBhdCB0aGUgc2FtZSB0aW1lLiAm
bmJzcDs8L2Rpdj4NCjxkaXY+PGJyPjwvZGl2PjxkaXY+Tml0czo8L2Rpdj48ZGl2Pi0tLS0tPC9k
aXY+PGRpdj5TZWN0aW9uIDE6Jm5ic3A7PC9kaXY+PGRpdj4tIGZpcnN0IHBhcmFncmFwaCwgc2Vj
b25kIHNlbnRlbmNlIGlzIHZlcnkgYXdrd2FyZCBhbmQgY291bGQgYmUgcmV3cml0dGVuIHNvbWV0
aGluZyBsaWtlICh1bmxlc3MgSSd2ZSBtaXN1bmRlcnN0b29kIHRoZSBvYmplY3RpdmUgb2YgdGhh
dCBzZW50ZW5jZTo8L2Rpdj4NCjxkaXY+T0xEOjwvZGl2PjxkaXY+Jm5ic3A7ICZuYnNwO1RoaXMg
Y2FuIGJlIHVzZWQgd2hlbiBpdCBpcyZuYnNwOzwvZGl2PjxkaXY+Jm5ic3A7ICZuYnNwO2Rlc2ly
ZWQgdG8gcmVxdWVzdCBhbGwgbGFiZWwgYmluZGluZ3MgZm9yIGEgZ2l2ZW4gdHlwZSBvZiBGRUMm
bmJzcDs8L2Rpdj48ZGl2PiZuYnNwOyAmbmJzcDtFbGVtZW50LCBvciB0byByZWxlYXNlIG9yIHdp
dGhkcmF3IGFsbCBsYWJlbCBiaW5kaW5ncyBmb3IgYSBnaXZlbiZuYnNwOzwvZGl2PjxkaXY+Jm5i
c3A7ICZuYnNwO3R5cGUgb2YgRkVDIGVsZW1lbnQuJm5ic3A7PC9kaXY+DQo8ZGl2Pk5FVzombmJz
cDs8L2Rpdj48ZGl2PiZuYnNwOyAmbmJzcDtUaGlzIGNhbiBiZSB1c2VkIHRvIHJlcXVlc3QsIHJl
bGVhc2Ugb3Igd2l0aGRyYXcgYWxsIGxhYmVsJm5ic3A7PC9kaXY+PGRpdj4mbmJzcDsgJm5ic3A7
YmluZGluZ3MgZm9yIGEgZ2l2ZW4gdHlwZSBvZiBGRUMgZWxlbWVudC48L2Rpdj48ZGl2Pjxicj48
L2Rpdj48ZGl2Pi0gc2Vjb25kIHBhcmFncmFwaCwgbGFzdCBzZW50ZW5jZSAtIG1pc3NpbmcgYXJ0
aWNsZXMgKFBXSUQsIHNhbWUpPC9kaXY+DQo8ZGl2Pk9MRDo8L2Rpdj48ZGl2PiZuYnNwOyAmbmJz
cDtUaGUgcHJvY2VkdXJlcyBmb3IgVHlwZWQgV2lsZGNhcmQgcHJvY2Vzc2luZyBmb3IgUFdpZCBh
bmQgJm5ic3A7PC9kaXY+PGRpdj4mbmJzcDsgJm5ic3A7R2VuZXJhbGl6ZWQgUFdpZCBGRUMgRWxl
bWVudHMgYXJlIHNhbWUgYXMgZGVzY3JpYmVkIGluIFtSRkM1OTE4XSBmb3ImbmJzcDs8L2Rpdj48
ZGl2PiZuYnNwOyAmbmJzcDthbnkgdHlwZWQgd2lsZGNhcmQgRkVDIEVsZW1lbnQgdHlwZS48L2Rp
dj4NCjxkaXY+TkVXOiZuYnNwOzwvZGl2PjxkaXY+Jm5ic3A7ICZuYnNwO1RoZSBwcm9jZWR1cmVz
IGZvciBUeXBlZCBXaWxkY2FyZCBwcm9jZXNzaW5nIGZvciB0aGUgUFdpZCBhbmQgJm5ic3A7PC9k
aXY+PGRpdj4mbmJzcDsgJm5ic3A7R2VuZXJhbGl6ZWQgUFdpZCBGRUMgRWxlbWVudHMgYXJlIHRo
ZSBzYW1lIGFzIGRlc2NyaWJlZCBpbiBbUkZDNTkxOF0gZm9yJm5ic3A7PC9kaXY+PGRpdj4mbmJz
cDsgJm5ic3A7YW55IHR5cGVkIHdpbGRjYXJkIEZFQyBFbGVtZW50IHR5cGUuPC9kaXY+DQo8ZGl2
Pjxicj48L2Rpdj48ZGl2PlNlY3Rpb24gMzo8L2Rpdj48ZGl2Pi0gdGhpcmQgcGFyYWdyYXBoLCBs
YXN0IHNlbnRlbmNlIGJlZm9yZSBsaXN0OiZuYnNwOzwvZGl2PjxkaXY+T0xEOiZuYnNwOzwvZGl2
PjxkaXY+Jm5ic3A7cHJvdmlkZSZuYnNwOzwvZGl2PjxkaXY+Jm5ic3A7IG1vcmUgZ2VuZXJhbGl6
ZWQgYW5kIGNvbXByZWhlbnNpdmUgc29sdXRpb24gYnkgYWxsb3dpbmc6Jm5ic3A7PC9kaXY+PGRp
dj5ORVc6Jm5ic3A7PC9kaXY+PGRpdj4mbmJzcDsgcHJvdmlkZSBhPC9kaXY+DQo8ZGl2PiZuYnNw
OyBtb3JlIGdlbmVyYWxpemVkIGFuZCBjb21wcmVoZW5zaXZlIHNvbHV0aW9uIGJ5IGFsbG93aW5n
OiZuYnNwOzwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+LSBsaXN0IGl0ZW0gMjogImNvbnN0cmFp
bnQiIC0mZ3Q7ICJjb25zdHJhaW4iPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+
PGRpdj48YnI+PC9kaXY+PGRpdj5TZWN0aW9uIDQuMTombmJzcDs8L2Rpdj4NCjxkaXY+T0xEOjwv
ZGl2PjxkaXY+Jm5ic3A7IuKApiBoYWQgbGVhcm50IGZyb20gTFNSIEIgb3ZlciBMRFAgc2Vzc2lv
bi4iPC9kaXY+PGRpdj5ORVc6Jm5ic3A7PC9kaXY+PGRpdj4mbmJzcDsiIOKApiBsZWFybmVkIGZy
b20gdGhlIExTUiBCIG92ZXIgdGhlIExEUCBzZXNzaW9uLiI8L2Rpdj48ZGl2Pjxicj48L2Rpdj48
ZGl2Pk9MRDo8L2Rpdj48ZGl2PiZuYnNwOyLigKZzdWNoIHJlcXVlc3TigKYiJm5ic3A7PC9kaXY+
DQo8ZGl2Pk5FVzo8L2Rpdj48ZGl2PiZuYnNwOyLigKZzdWNoIGEgcmVxdWVzdOKApiIgJm5ic3A7
T1IgIi4udGhlIHJlcXVlc3TigKYiPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5PTEQ6Jm5ic3A7
PC9kaXY+PGRpdj4mbmJzcDsobm8gc3RhbGUpPC9kaXY+PGRpdj5ORVc6Jm5ic3A7PC9kaXY+PGRp
dj4mbmJzcDsobm90IHN0YWxlKTwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+T0xEOjwvZGl2Pjxk
aXY+Jm5ic3A7IGNvbXBsZXRlcyBjb25zaXN0ZW5jeSBjaGVjazwvZGl2Pg0KPGRpdj5ORVc6PC9k
aXY+PGRpdj4mbmJzcDsgY29tcGxldGVzIHRoZSBjb25zaXN0ZW5jeSBjaGVjazwvZGl2PjxkaXY+
PGJyPjwvZGl2PjxkaXY+U2VjdGlvbiA0LjM6Jm5ic3A7PC9kaXY+PGRpdj4tIGZpcnN0IHBhcmFn
cmFwaCwgbGFzdCBzZW50ZW5jZTogJm5ic3A7PC9kaXY+PGRpdj5PTEQ6Jm5ic3A7PC9kaXY+PGRp
dj4mbmJzcDsgd2l0aCBsYXJnZSBudW1iZXI8L2Rpdj48ZGl2Pk5FVzo8L2Rpdj48ZGl2PiZuYnNw
OyB3aXRoIGEgbGFyZ2UgbnVtYmVyPC9kaXY+DQo8ZGl2Pjxicj48L2Rpdj48ZGl2PlNlY3Rpb24g
NC40OjwvZGl2PjxkaXY+LSAxc3QgcGFyYSwgMm5kIHNlbnRlbmNlOjwvZGl2PjxkaXY+T0xEOiZu
YnNwOzwvZGl2PjxkaXY+Jm5ic3A7ICZuYnNwO1RoZXNlIHByb2NlZHVyZXMgdXNlIExEUCBBZGRy
ZXNzIFdpdGhkcmF3IG1lc3NhZ2U8L2Rpdj48ZGl2Pk5FVzombmJzcDs8L2Rpdj48ZGl2PiZuYnNw
OyAmbmJzcDtUaGVzZSBwcm9jZWR1cmVzIHVzZSBhbiBMRFAgQWRkcmVzcyBXaXRoZHJhdyBtZXNz
YWdlPC9kaXY+DQo8ZGl2Pjxicj48L2Rpdj48ZGl2Pi0gMm5kIHBhcmFncmFwaCwgbGFzdCBzZW50
ZW5jZTo8L2Rpdj48ZGl2Pk9MRDo8L2Rpdj48ZGl2PiZuYnNwOyBUaGlzIHBlciBQVyAoVlBMUyBp
bnN0YW5jZSkgTUFDIFdpdGhkcmF3IG1lc3NhZ2VzJm5ic3A7PC9kaXY+PGRpdj5ORVc6Jm5ic3A7
PC9kaXY+PGRpdj4mbmJzcDsgVGhlc2UgcGVyIFBXIChWUExTIGluc3RhbmNlKSBNQUMgV2l0aGRy
YXcgbWVzc2FnZXMmbmJzcDs8L2Rpdj48ZGl2Pjxicj4NCjwvZGl2PjxkaXY+M3JkIHBhcmFncmFw
aCAtIDFzdCBzZW50ZW5jZTo8L2Rpdj48ZGl2Pk9MRDo8L2Rpdj48ZGl2PiZuYnNwOyB0aGlzIGRv
Y3VtZW50IGFsbG93cyB1c2Ugb2Y8L2Rpdj48ZGl2Pk5FVzombmJzcDs8L2Rpdj48ZGl2PiZuYnNw
OyB0aGlzIGRvY3VtZW50IGFsbG93cyB0aGUgdXNlIG9mPC9kaXY+DQo8L2Rpdj48L2Jsb2NrcXVv
dGU+PC9ib2R5PjwvaHRtbD4=

--Apple-Mail-CB26F6DD-1506-47F2-A7CA-546B2141E33D--

From skraza@cisco.com  Mon Apr  9 12:49:24 2012
Return-Path: <skraza@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA5F21F87E4 for <gen-art@ietfa.amsl.com>; Mon,  9 Apr 2012 12:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.135
X-Spam-Level: 
X-Spam-Status: No, score=-7.135 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
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 ft3rIOvdQYEL for <gen-art@ietfa.amsl.com>; Mon,  9 Apr 2012 12:49:22 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 3380B21F87E3 for <gen-art@ietf.org>; Mon,  9 Apr 2012 12:49:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=skraza@cisco.com; l=9099; q=dns/txt; s=iport; t=1334000962; x=1335210562; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version; bh=gw+rG5vfiI2T8+GvSWR0c3YFON8k76sZ0TFihl5L30w=; b=UsZwnunMBYB7/JdfLSKf5+pcLINnle8lzdkOGSTvdESb90Fxym6uzMrc QFkT5LKRh9uHRTJmrPgD433UMxIxFJ5H8YYeWC+US9YP4P0qGxiGem0b0 +JFnl9w+b/gno43GDWa85a/QB2EyzurZn0hgq3rr1XhLstF9InQ72vlKv g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4IAFQ8g0+tJV2d/2dsb2JhbABAA4JTrXWII3MCgQeCCQEBAQMBEgEUFhgREwUNAQgUUzYBAQQBDQUbB4deAwYFC55bljMNgWuKLYMVgykEiCeNRYERiiiDFCeBQoMD
X-IronPort-AV: E=Sophos;i="4.75,393,1330905600"; d="scan'208,217";a="73223570"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-2.cisco.com with ESMTP; 09 Apr 2012 19:49:21 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id q39JnLa1014368;  Mon, 9 Apr 2012 19:49:21 GMT
Received: from xmb-rcd-103.cisco.com ([72.163.62.145]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 9 Apr 2012 14:49:07 -0500
Received: from 161.44.193.212 ([161.44.193.212]) by XMB-RCD-103.cisco.com ([72.163.62.145]) with Microsoft Exchange Server HTTP-DAV ;  Mon,  9 Apr 2012 19:49:07 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Mon, 09 Apr 2012 15:51:01 -0400
From: Kamran Raza <skraza@cisco.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, <draft-ietf-pwe3-pw-typed-wc-fec.all@tools.ietf.org>
Message-ID: <CBA8B5E5.27E2D%skraza@cisco.com>
Thread-Topic: Gen-ART review: draft-ietf-pwe3-pw-typed-wc-fec-03
Thread-Index: Ac0Wihb0KiakvUC5Ck2YBEcnhBobPg==
In-Reply-To: <CAHBDyN4-z57zkkc8_thG+PPPso38vZNZy496xNviS+10BPj6_w@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3416831462_48426"
X-OriginalArrivalTime: 09 Apr 2012 19:49:07.0946 (UTC) FILETIME=[D39154A0:01CD1689]
X-Mailman-Approved-At: Mon, 09 Apr 2012 12:52:18 -0700
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART review: draft-ietf-pwe3-pw-typed-wc-fec-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: Mon, 09 Apr 2012 19:49:24 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3416831462_48426
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Thanks Mary for your review.

Agree with all your comments and will fix them in next revision accordingly=
.

Rgds,
-- Kamran

On 12-04-09 3:21 PM, "Mary Barnes" <mary.ietf.barnes@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-pwe3-pw-typed-wc-fec-03.txt
> Reviewer: =A0Mary Barnes=A0
> Review Date: =A09 April 2012
> IESG Telechat Date: 12 April 2012
>=20
> Summary: =A0Ready with nits.
>=20
> Comments: there are some editorial nits, many summarized below. =A0There ar=
e
> several cases where an article - i.e., "the", "an", etc. is missing. =A0 I
> believe these can be fixed in AUTH48 and I imagine the RFC editor will ca=
tch
> them. But, if the doc needs any other updates, it would be good to make t=
hese
> fixes at the same time. =A0
>=20
> Nits:
> -----
> Section 1:=A0
> - first paragraph, second sentence is very awkward and could be rewritten
> something like (unless I've misunderstood the objective of that sentence:
> OLD:
> =A0 =A0This can be used when it is=A0
> =A0 =A0desired to request all label bindings for a given type of FEC=A0
> =A0 =A0Element, or to release or withdraw all label bindings for a given=A0
> =A0 =A0type of FEC element.=A0
> NEW:=A0
> =A0 =A0This can be used to request, release or withdraw all label=A0
> =A0 =A0bindings for a given type of FEC element.
>=20
> [skraza]: Agree.
>=20
> - second paragraph, last sentence - missing articles (PWID, same)
> OLD:
> =A0 =A0The procedures for Typed Wildcard processing for PWid and =A0
> =A0 =A0Generalized PWid FEC Elements are same as described in [RFC5918] for=A0
> =A0 =A0any typed wildcard FEC Element type.
> NEW:=A0
> =A0 =A0The procedures for Typed Wildcard processing for the PWid and =A0
> =A0 =A0Generalized PWid FEC Elements are the same as described in [RFC5918] f=
or=A0
> =A0 =A0any typed wildcard FEC Element type.
>=20
> Section 3:
> - third paragraph, last sentence before list:=A0
> OLD:=A0
> =A0provide=A0
> =A0 more generalized and comprehensive solution by allowing:=A0
> NEW:=A0
> =A0 provide a
> =A0 more generalized and comprehensive solution by allowing:=A0
>=20
> - list item 2: "constraint" -> "constrain"
>=20
>=20
>=20
> Section 4.1:=A0
> OLD:
> =A0"=8A had learnt from LSR B over LDP session."
> NEW:=A0
> =A0" =8A learned from the LSR B over the LDP session."
>=20
> OLD:
> =A0"=8Asuch request=8A"=A0
> NEW:
> =A0"=8Asuch a request=8A" =A0OR "..the request=8A"
>=20
> OLD:=A0
> =A0(no stale)
> NEW:=A0
> =A0(not stale)
>=20
> OLD:
> =A0 completes consistency check
> NEW:
> =A0 completes the consistency check
>=20
> Section 4.3:=A0
> - first paragraph, last sentence: =A0
> OLD:=A0
> =A0 with large number
> NEW:
> =A0 with a large number
>=20
> Section 4.4:
> - 1st para, 2nd sentence:
> OLD:=A0
> =A0 =A0These procedures use LDP Address Withdraw message
> NEW:=A0
> =A0 =A0These procedures use an LDP Address Withdraw message
>=20
> - 2nd paragraph, last sentence:
> OLD:
> =A0 This per PW (VPLS instance) MAC Withdraw messages=A0
> NEW:=A0
> =A0 These per PW (VPLS instance) MAC Withdraw messages=A0
>=20
> 3rd paragraph - 1st sentence:
> OLD:
> =A0 this document allows use of
> NEW:=A0
> =A0 this document allows the use of
>=20

--=20
Syed Kamran Raza
Technical Leader, SPRSG IOS-XR Routing (MPLS)
Cisco Systems, Inc.,
Kanata, ON, K2K 3E8, Canada
Ph: +1 (613) 254-4520
http://www.cisco.com





--B_3416831462_48426
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: Gen-ART review: draft-ietf-pwe3-pw-typed-wc-fec-03</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>Thanks Mary for your review. <BR>
<BR>
Agree with all your comments and will fix them in next revision accordingly=
.<BR>
<BR>
Rgds,<BR>
-- Kamran<BR>
<BR>
On 12-04-09 3:21 PM, &quot;Mary Barnes&quot; &lt;<a href=3D"mary.ietf.barnes@=
gmail.com">mary.ietf.barnes@gmail.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'>I am the assigned Gen-ART reviewer for this draf=
t. For background on<BR>
Gen-ART, please see the FAQ at<BR>
&lt; <a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<BR>
<BR>
Please wait for direction from your document shepherd<BR>
or AD before posting a new version of the draft.<BR>
<BR>
Document: draft-ietf-pwe3-pw-typed-wc-fec-03.txt<BR>
Reviewer: =A0Mary Barnes=A0<BR>
Review Date: =A09 April 2012<BR>
IESG Telechat Date: 12 April 2012<BR>
<BR>
Summary: =A0Ready with nits.<BR>
<BR>
Comments: there are some editorial nits, many summarized below. =A0There are =
several cases where an article - i.e., &quot;the&quot;, &quot;an&quot;, etc.=
 is missing. =A0 I believe these can be fixed in AUTH48 and I imagine the RFC =
editor will catch them. But, if the doc needs any other updates, it would be=
 good to make these fixes at the same time. =A0<BR>
<BR>
Nits:<BR>
-----<BR>
Section 1:=A0<BR>
- first paragraph, second sentence is very awkward and could be rewritten s=
omething like (unless I've misunderstood the objective of that sentence:<BR>
OLD:<BR>
=A0 =A0This can be used when it is=A0<BR>
=A0 =A0desired to request all label bindings for a given type of FEC=A0<BR>
=A0 =A0Element, or to release or withdraw all label bindings for a given=A0<BR>
=A0 =A0type of FEC element.=A0<BR>
NEW:=A0<BR>
=A0 =A0This can be used to request, release or withdraw all label=A0<BR>
=A0 =A0bindings for a given type of FEC element.<BR>
<BR>
[skraza]: Agree.<BR>
<BR>
- second paragraph, last sentence - missing articles (PWID, same)<BR>
OLD:<BR>
=A0 =A0The procedures for Typed Wildcard processing for PWid and =A0<BR>
=A0 =A0Generalized PWid FEC Elements are same as described in [RFC5918] for=A0<BR=
>
=A0 =A0any typed wildcard FEC Element type.<BR>
NEW:=A0<BR>
=A0 =A0The procedures for Typed Wildcard processing for the PWid and =A0<BR>
=A0 =A0Generalized PWid FEC Elements are the same as described in [RFC5918] for=
=A0<BR>
=A0 =A0any typed wildcard FEC Element type.<BR>
<BR>
Section 3:<BR>
- third paragraph, last sentence before list:=A0<BR>
OLD:=A0<BR>
=A0provide=A0<BR>
=A0 more generalized and comprehensive solution by allowing:=A0<BR>
NEW:=A0<BR>
=A0 provide a<BR>
=A0 more generalized and comprehensive solution by allowing:=A0<BR>
<BR>
- list item 2: &quot;constraint&quot; -&gt; &quot;constrain&quot;<BR>
<BR>
<BR>
<BR>
Section 4.1:=A0<BR>
OLD:<BR>
=A0&quot;&#8230; had learnt from LSR B over LDP session.&quot;<BR>
NEW:=A0<BR>
=A0&quot; &#8230; learned from the LSR B over the LDP session.&quot;<BR>
<BR>
OLD:<BR>
=A0&quot;&#8230;such request&#8230;&quot;=A0<BR>
NEW:<BR>
=A0&quot;&#8230;such a request&#8230;&quot; =A0OR &quot;..the request&#8230;&qu=
ot;<BR>
<BR>
OLD:=A0<BR>
=A0(no stale)<BR>
NEW:=A0<BR>
=A0(not stale)<BR>
<BR>
OLD:<BR>
=A0 completes consistency check<BR>
NEW:<BR>
=A0 completes the consistency check<BR>
<BR>
Section 4.3:=A0<BR>
- first paragraph, last sentence: =A0<BR>
OLD:=A0<BR>
=A0 with large number<BR>
NEW:<BR>
=A0 with a large number<BR>
<BR>
Section 4.4:<BR>
- 1st para, 2nd sentence:<BR>
OLD:=A0<BR>
=A0 =A0These procedures use LDP Address Withdraw message<BR>
NEW:=A0<BR>
=A0 =A0These procedures use an LDP Address Withdraw message<BR>
<BR>
- 2nd paragraph, last sentence:<BR>
OLD:<BR>
=A0 This per PW (VPLS instance) MAC Withdraw messages=A0<BR>
NEW:=A0<BR>
=A0 These per PW (VPLS instance) MAC Withdraw messages=A0<BR>
<BR>
3rd paragraph - 1st sentence:<BR>
OLD:<BR>
=A0 this document allows use of<BR>
NEW:=A0<BR>
=A0 this document allows the use of<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial">=
<SPAN STYLE=3D'font-size:11pt'><BR>
-- <BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Courier, Courier New"><SPAN STYLE=3D=
'font-size:9pt'>Syed Kamran Raza<BR>
Technical Leader, SPRSG IOS-XR Routing (MPLS)<BR>
Cisco Systems, Inc., <BR>
Kanata, ON, K2K 3E8, Canada <BR>
Ph: +1 (613) 254-4520<BR>
<FONT COLOR=3D"#0F32EF"><U><a href=3D"http://www.cisco.com">http://www.cisco.co=
m</a></U></FONT> <BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'><BR>
<BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3416831462_48426--


From alexey.melnikov@isode.com  Tue Apr 10 04:34:24 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 B785321F8547; Tue, 10 Apr 2012 04:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.027
X-Spam-Level: 
X-Spam-Status: No, score=-101.027 tagged_above=-999 required=5 tests=[AWL=-0.728, BAYES_00=-2.599, MANGLED_SAVELE=2.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sWIFZRPMLehq; Tue, 10 Apr 2012 04:34:21 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id BE9BF21F8514; Tue, 10 Apr 2012 04:34:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1334057544; d=isode.com; s=selector; i=@isode.com; bh=jW7uXFnN/5roD4VDP1gr0T2UaWVBQSPPajt8GUxYAjI=; 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=dI+cNtJ5RccfQdibnvZBWLug9TM8BMTYs8pQSlAltbQhsbLclr6RnaVqHMBlXV4mNFfK8N Y0p3tIdto+G56ZJRx0SgwvATLIrimLRMGBmTJ4azSVs0U3PqgBRB05qzwnsl6AqmwmRxFu dNfrPkXPkRPkwTT2OJ/Q1ni3y4hV3iA=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T4QaRwAg2z0T@rufus.isode.com>; Tue, 10 Apr 2012 12:32:24 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F840F94.1080703@isode.com>
Date: Tue, 10 Apr 2012 11:46:44 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Adam Roach <adam@nostrum.com>
References: <CAHBDyN6PN-vp9wXo6fF8G4VfODXjkfbWBaJN8EPopeWfOg9PmQ@mail.gmail.com>
In-Reply-To: <CAHBDyN6PN-vp9wXo6fF8G4VfODXjkfbWBaJN8EPopeWfOg9PmQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, The IESG <iesg@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: [Gen-art] Gen-Art review of draft-ietf-sipcore-rfc3265bis-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Apr 2012 11:34:24 -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-sipcore-rfc3265bis-07.txt
Reviewer: Alexey Melnikov
Review Date: 10-April-2012
IETF LC End Date: past
IESG Telechat date: 26-April-2012

Summary: This documents is ready for publication as a Proposed Standard 
RFC (with nits). But please see a couple of questions below.


3.2.1.  Identification of Reported Events, Event Classes, and Current
         State

    When present, the body of the NOTIFY request MUST be formatted into
    one of the body formats specified in the "Accept" header field of the
    corresponding SUBSCRIBE request.  This body will contain either the
    state of the subscribed resource or a pointer to such state in the
    form of a URI (see Section 5.4.13).

Nit: or the default according to the event package definition, if no Accept
header field was specified.

Also, it might be good to reference RFC 3986 for URIs here.



4.1.1.  Detecting Support for SIP Events

    The extension described in this document does not make use of the use
    of "Require" or "Proxy-Require" header fields; similarly, there is no

Nit: too many "use of".

    token defined for "Supported" header fields.  Potential subscribers
    may probe for the support of SIP Events using the OPTIONS request
    defined in [RFC3261].

4.1.3.  Receiving and Processing State Information

    To prevent spoofing of events, NOTIFY requests SHOULD be
    authenticated, using any defined SIP authentication mechanism.

Minor: How can this SHOULD be satisfied? Any reference which might be 
appropriate here?

4.2.1.3.  Authentication/Authorization of SUBSCRIBE Requests

    SIP authentication mechanisms are discussed in [RFC3261].  Note that,
    even if the notifier node typically acts as a proxy, authentication
    for SUBSCRIBE requests will always be performed via a "401" response,
    not a "407;" notifiers always act as a user agents when accepting

Nit: Is the ";" after "407" a typo?

    subscriptions and sending notifications.


4.4.4.  Allow-Events header field usage

    The "Allow-Events" header field does not include a list of the etvent

  typo: event

    template packages supported by an implementation.  If a subscriber
    wishes to determine which event template packages are supported by a
    notifier, it can probe for such support by attempting to subscribe to
    the event template packages it wishes to use.

Can you clarify how such request would look like? An example would be nice.

5.4.3.  SUBSCRIBE Request Bodies

    It is expected that most, but not all, event packages will define
    syntax and semantics for SUBSCRIBE request bodies; these bodies will
    typically modify, expand, filter, throttle, and/or set thresholds for
    the class of events being requested.  Designers of event packages are
    strongly encouraged to re-use existing MIME types for message bodies
    where practical.

Nit: MIME types are now called "media types" in more recent IETF RFCs.
I would recommend pointing to the Media Type Registration Procedure 
document [RFC 4288] here, which points to the IANA registry.

5.4.5.  NOTIFY Request Bodies

    Event packages also MUST define which MIME type is to be assumed if
    none are specified in the "Accept" header field of the SUBSCRIBE
    request.

The same nit as above.

7.2.  Reason Codes

    This document further defines "reason" codes for use in the
    "Subscription-State" header field (see Section 4.1.3).

    Following the policies outlined in "Guidelines for Writing an IANA
    Considerations Section in RFCs" [RFC5226], new reason codes require a
    Standards Action.

Minor: This would prevent registration of new Reason Codes in an 
Experimental RFC (for example). I would like to double check that that 
is intentional.

    Registrations with the IANA include the reason code being registered
    and a reference to a published document which describes the event
    package.  Insertion of such values takes place as part of the RFC
    publication process or as the result of inter-SDO liaison activity.

I don't think Standards Action allows for "inter-SDO liaison activity", 
unless such documents from other SDOs are published as Standard Track 
RFCs. So I find your text confusing: either your registration procedure 
should also allow for direct IESG approvals (to allow registrations from 
other SDOs with no RFCs), or you should remove "as the result of 
inter-SDO liaison activity".

    New reason codes must conform to the syntax of the ABNF "token"
    element defined in [RFC3261].

8.4.  Augmented BNF Definitions

    event-type        =  event-package *( "." event-template )

Minor: Does this mean that multiple template packages can be applied?
Is there any ordering for them? How would "foo.A.B" differ from "foo.B.A"?


Nit: id-nits complains:

   -- Duplicate reference: RFC4660, mentioned in 'RFC4660', was also 
mentioned
      in 'RFC 4660'.

"[RFC 4660]" reference is used in section 7.2.

From alexey.melnikov@isode.com  Tue Apr 10 06:09:26 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 E9B2621F85D4; Tue, 10 Apr 2012 06:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.251
X-Spam-Level: 
X-Spam-Status: No, score=-102.251 tagged_above=-999 required=5 tests=[AWL=0.348, 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 huuwelazUrQ5; Tue, 10 Apr 2012 06:09:26 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id C313321F85D0; Tue, 10 Apr 2012 06:09:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1334063364; d=isode.com; s=selector; i=@isode.com; bh=McsEq1266l+vaPxpvakj0Ss1PbEOCwKorvQqNn5PcU8=; 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=tFCT+DmkocNyF8W/beEvjnjx0ak7WOhtFUGQE2PeXawJ3yav5buoPAmedmcvdaHPQ7QGm6 DCwxasC2QjapzkH3+F4LyvruQOJCnn1sYVa7t6k0HSoEJ7fSubpTdnobakvixZbUC5qRZd rNC+NgbLLprWKfG8S2QNh0SJ0kt6yC0=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T4QxAwAg2zGP@rufus.isode.com>; Tue, 10 Apr 2012 14:09:24 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F843129.5030908@isode.com>
Date: Tue, 10 Apr 2012 14:10:01 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Bob Briscoe <bob.briscoe@bt.com>
References: <4F7C803F.2040308@isode.com> <201204041745.q34Hj2w6005980@bagheera.jungle.bt.co.uk>
In-Reply-To: <201204041745.q34Hj2w6005980@bagheera.jungle.bt.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Nandita Dukkipati <nanditad@google.com>, General Area Review Team <gen-art@ietf.org>, j.schoenwaelder@jacobs-university.de, Alissa Cooper <acooper@cdt.org>, The IESG <iesg@ietf.org>, Richard Woundy <richard_woundy@cable.comcast.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-conex-concepts-uses-04.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, 10 Apr 2012 13:09:27 -0000

On 04/04/2012 18:45, Bob Briscoe wrote:
> Alexey,
Hi Bob,
> Thanks for your review - we are all indebted to people like you who 
> commit to review stuff that you don't necessarily have an interest in.
>
>
> We're concerned if you think the doc isn't understandable without 
> reading the I-D refs. This is meant to be the entry-point to the set 
> of ConEx documentation, so we intended it to be understandable without 
> knowing how ConEx works (beyond the high level description in the 
> introduction). "Understandable" here means sufficient to satisfy the 
> stated purpose of the doc, which is to motivate ConEx (not to 
> understand how it works).
Maybe I wasn't very clear: the document was understandable without 
checking out the references.
>
> The refs are intended to be used the other way round - having read 
> this, you should be motivated to go and read more, so it provides 
> pointers to what's available.
>
> Are you sure the need to read the refs is not a symptom of your 
> (natural) curiosity to know how ConEx works? Is it really necessary to 
> know the details of how ConEx works to understand the motivation for 
> building it?
>
> The second paragraph sets out the purpose of the doc:
> "
>    This document provides the entry point to the set of documentation
>    about the Congestion Exposure (ConEx) protocol.  It focuses on the
>    motivation for including a ConEx marking at the IP layer.  (A
>    companion document, [I-D.ietf-conex-abstract-mech], focuses on the
>    mechanics of the protocol.)
> "
I've just rechecked references to drafts and I can see them being 
Informative. So thank you for your response and your document is getting 
"all clear" from me.

Thank you,
Alexey
> Bob
>
> At 18:09 04/04/2012, Alexey Melnikov wrote:
>> 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-conex-concepts-uses-04.txt
>> Reviewer: Alexey Melnikov
>> Review Date: 2012-04-04
>> IETF LC End Date: 2012-04-12
>> IESG Review: 2012-04-12
>>
>> Summary: The document is nearly ready for publication as an 
>> Informational RFC (see one issue below)
>>
>>
>> Major issues: none
>>
>> Minor issues:
>>
>> This might be pedantic, but I think some of your Informational 
>> references are actually Normative, because they are needed to 
>> understand the document. See "IESG Statement: Normative and 
>> Informative References" for more details 
>> <http://www.ietf.org/iesg/statement/normative-informative.html>.
>>
>> This almost doesn't matter for an Informational document, however if 
>> any of 5 drafts becomes Normative, publication of this document as an 
>> RFC will be delayed. Still, this might be better than just getting it 
>> published with "work in progress" references.
>>
>> But otherwise this is a well written document and I enjoyed reading it.
>>
>>
>> Nits/editorial comments: none


From rbarnes@bbn.com  Tue Apr 10 06:10:54 2012
Return-Path: <rbarnes@bbn.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 1126521F85F6; Tue, 10 Apr 2012 06:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j2ejoQvcdaWn; Tue, 10 Apr 2012 06:10:53 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 5D02121F85D0; Tue, 10 Apr 2012 06:10:53 -0700 (PDT)
Received: from [128.89.253.10] (port=55028) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1SHaq4-000FpD-0l; Tue, 10 Apr 2012 09:10:28 -0400
From: Richard L. Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Apr 2012 09:11:19 -0400
Message-Id: <22E22875-8112-42A3-974D-770167AB9536@bbn.com>
To: General Area Review Team <gen-art@ietf.org>, draft-ietf-oauth-v2.all@tools.ietf.org, IETF-Discussion list <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-oauth-v2-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Apr 2012 13:10:54 -0000

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

Document: draft-ietf-oauth-v2.txt
Reviewer:  Richard Barnes=20
Review Date:  10 Apr 2012
IETF LC End Date:=20
IESG Telechat Date: 12 Apr 2012

Summary: Almost ready, but with some gaps that need to be addressed


MAJOR:

General: At several points, the document seems to deal in plain-text =
usernames and passwords, ranging from the requirement for HTTP Basic =
authentication (2.3.1) to the explicit username and password fields one =
of the grant types (4.3.2, 10.7).  In these cases, it seems like it =
would encourage better security practices to use some sort of digest or =
other secure scheme for proving ownership of passwords.  Otherwise, =
there's a risk that proxies, caches, etc. will have access to users' =
plaintext credentials.

General: The document requires the Authorization Server to distinguish =
between confidential and public clients at several points.  It's not =
clear, however, how the server is supposed to tell which is which.  =
Perhaps Section 2.1 could elaborate a little more on this? =20

4: Throughout the document, the assumption is that the client is moved =
from one URI to another via HTTP redirects (302 responses).  Could the =
protocol also accommodate other techniques of moving clients around, =
e.g., in JavaScript (setting window.location).  It seems like this could =
make deployment much easier in some cases.

10.3: This section seems to ignore the risk of client impersonation at =
the resource server.  Just as with client credentials in Section 10.2, =
if an access token is compromised, then it could be presented by another =
party in order to access the protected resource.  So the Resource Server =
needs to authenticate the client and validate that the token goes with =
the client, in addition to just checking the validity of the token.

10: Throughout this section, there are mentions of which parameters =
require secure transmission/storage and which do not.  It would be =
helpful to summarize these requirements, say in a table at the end of =
the section.


MINOR:

2.3.1: When you say "request body" in this section, do you actually mean =
"query"?  I don't see a prohibition on GET here, in which case the =
parameters would be in the URI query section.

3.1.2.2: It seems like an explicit requirement would be helpful here, =
e.g.:
"
The Authorization Server MUST verify that either no redirect_uri is =
provided (in which case it uses the registered URI), or else that the =
provided redirect_uri matches the registered redirection URI for the =
authenticated client_id (where the match can be based on a full or =
partial registered URI).
"

4.1.3: Why does this request use redirect_uri and not client_id to =
identify the client?  (Or both?)  It seems like involving the client_id =
would better support the goal of client authentication, in order to =
mitigate the risk of client impersonation.

4.3.2: Shouldn't there be a client authentication here? (In particular, =
a client_id.)  Otherwise, it seems like this is essentially the same as =
the  flow in 4.4.

7. It seems like it would be helpful to have a way to pass access tokens =
in the request URI / query in some deployment cases (e.g., a JavaScript =
based client).  Is there any particular reason this was excluded?


EDITORIAL:

3. Would be helpful to note here that these endpoints are in addition to =
the resource endpoint (the one started out to protect), which is handled =
in Section 7.

3.2: It's not clear why only POST is allowed here.  A couple of words of =
explanation would help.

5.1: Why bother with a  case-insensitive token_type here?  It doesn't =
look like anything else in the whole document has this property.


From alexey.melnikov@isode.com  Tue Apr 10 06:12:39 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 9A76521F8604; Tue, 10 Apr 2012 06:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.278
X-Spam-Level: 
X-Spam-Status: No, score=-102.278 tagged_above=-999 required=5 tests=[AWL=0.321, 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 iwdaeWAonzF0; Tue, 10 Apr 2012 06:12:39 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id DAD6D21F8566; Tue, 10 Apr 2012 06:12:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1334063557; d=isode.com; s=selector; i=@isode.com; bh=/4s5UnCX8p2/6no7HwCp6k2/VI4eyuuwtLFyGAnSDyA=; 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=D9KqFI0c8RxtnV4yegN0htIdouVsoB7YeT7OMjkbqEh5pLLvdC7txmS7j6Vz5ECxgoCCgv Rzp/B84GDKtVAcz5YHGqatAG4f2Tq6AIY5uzF2klFqj3l0Wk/0Y0oYhQWdUOW/KZwW2NkF /RJ80qsk7oAWeyOhYLEnaWNsugDaLP8=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T4QxxAAg28Cv@rufus.isode.com>; Tue, 10 Apr 2012 14:12:37 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F8431EB.9000900@isode.com>
Date: Tue, 10 Apr 2012 14:13:15 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: j.schoenwaelder@jacobs-university.de, Bob Briscoe <bob.briscoe@bt.com>, Richard Woundy <richard_woundy@cable.comcast.com>, Alissa Cooper <acooper@cdt.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Nandita Dukkipati <nanditad@google.com>, General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-conex-concepts-uses-04.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, 10 Apr 2012 13:12:39 -0000

[IESG telechat re-review.]

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-conex-concepts-uses-04.txt
Reviewer: Alexey Melnikov
Review Date: 2012-04-10
IETF LC End Date: 2012-04-12
IESG Review: 2012-04-12

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

My question was answered and resulted in no changes to the document.

Major issues: none
Minor issues: none
Nits/editorial comments: none

From alexey.melnikov@isode.com  Tue Apr 10 06:47:46 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 6AFED21F85F4; Tue, 10 Apr 2012 06:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.32
X-Spam-Level: 
X-Spam-Status: No, score=-102.32 tagged_above=-999 required=5 tests=[AWL=0.279, 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 CrIGDDjWgWMK; Tue, 10 Apr 2012 06:47:45 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC6021F85D6; Tue, 10 Apr 2012 06:47:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1334065664; d=isode.com; s=selector; i=@isode.com; bh=XNGmDZTKRipUA6dftlaMuOIziTczDoq3IBCKRkSlcdE=; 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=Wd8UspvHARyeVhqASVJhssS1uMUrz2xuTVqBmT30chhQeBQmMsmFiC8O9ggnBsSh/zAGmx BDWCKp7st6OgtPU3pA4uHSOVomY7BHIctfB+ttPw78Flm+IrntNh0bLW7VgKWqROqGEnKv GaBT0eadY24c4fIOPPZMeEgjpSlwI9c=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T4Q5=gAg26fi@rufus.isode.com>; Tue, 10 Apr 2012 14:47:43 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F843A22.4020908@isode.com>
Date: Tue, 10 Apr 2012 14:48:18 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Mike Jones <Michael.Jones@microsoft.com>
References: <4F2575CE.9040001@isode.com> <4E1F6AAD24975D4BA5B16804296739436638B7AD@TK5EX14MBXC284.redmond.corp.microsoft.com> <4F27C37C.1090008@isode.com>
In-Reply-To: <4F27C37C.1090008@isode.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>, "oauth@ietf.org" <oauth@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-oauth-v2-bearer-15.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, 10 Apr 2012 13:47:46 -0000

Hi Mike,

On 31/01/2012 10:33, Alexey Melnikov wrote:
> On 30/01/2012 05:20, Mike Jones wrote:
>> Thanks for your useful feedback, Alexey.
> Hi Mike,
>>    Below, I'll respond to each of your comments.  I've also added the 
>> OAuth working group to the thread, so they are aware of them as well 
>> and can participate in the discussion.
  [...]
>> About your comments on scope:  OAuth 2.0 (both the Core and Bearer 
>> specs) is designed to be deployed in diverse and non-interoperable 
>> application contexts, meeting a variety of application needs.  In 
>> those various settings, which are often distinct and potentially 
>> non-interoperable, parameters such as scope, realm, etc. may have 
>> very different meanings.  This is not a bug; it is a feature, because 
>> it allows the OAuth pattern to meet the needs of numerous, often 
>> distinct, application environments.  For that reason, a registry of 
>> scope (or realm) parameters would be ill-advised and 
>> counterproductive.  It's perfectly OK and expected for a scope value 
>> such as "email" to have one meaning in one application context and a 
>> different meaning in a different, but distinct application context.  
>> Trying to impose a single meaning on particular scope values across 
>> distinct application contexts is both unnecessary and could break 
>> many existing deployments.  That being said, we fully expect
>> interoperability profiles to emerge that define interoperable sets of 
>> scope values within particular application contexts.  (The OpenID 
>> Connect specifications are one such set of profiles.)  But these 
>> meanings will always be context-specific - not global in scope.
> The way "scope" is currently defined in the document is completely 
> useless. You don't have a single example in the document. You don't 
> say how the semantics of the value differs from realm. You don't say 
> that its values are deployment specific and can be profiled in future 
> documents. Please say something about these issues in the document 
> (your explanation above would work.)
  [...]
>> About your second minor issue on error codes, the error codes 
>> registry already exists, but is in the OAuth Core spec.  See 
>> http://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-11.4.
> Can you please make this clear in the document (by adding a reference)?

I didn't see any of these addressed in -16...18. If I've missed that or 
if I've missed the discussion why these are not valid concerns, please 
let me know.


From alexey.melnikov@isode.com  Tue Apr 10 07:02: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 5439211E80D5; Tue, 10 Apr 2012 07:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.338
X-Spam-Level: 
X-Spam-Status: No, score=-102.338 tagged_above=-999 required=5 tests=[AWL=0.261, 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 n9EswgLPvxrz; Tue, 10 Apr 2012 07:02:36 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 52E8211E80D3; Tue, 10 Apr 2012 07:02:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1334066555; d=isode.com; s=selector; i=@isode.com; bh=bYQCBLIapiUTmkuq8okRogKIFoQ5k3TMEx2zcTMW47E=; 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=cUKknYQcFaZrKmvjSkIP/Z1yOODUoHiUWhjaFTJl6b7p1UMtT5K7Ib4zxjjTzZ+xQmoeuM yWiQjxhzOP3QpfB0yuzEcoWRtTPZUV2kAzQndzsco4hjn6DFDET7W/fIgVp81/gEz/Rztp c0YBGOkJG2mx/5b4XWcU+LcWaVt9GXk=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T4Q9egAg23l2@rufus.isode.com>; Tue, 10 Apr 2012 15:02:35 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F843DA1.8080703@isode.com>
Date: Tue, 10 Apr 2012 15:03:13 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>
References: <4F2575CE.9040001@isode.com> <4E1F6AAD24975D4BA5B16804296739436638B7AD@TK5EX14MBXC284.redmond.corp.microsoft.com> <4F27C37C.1090008@isode.com> <4F843A22.4020908@isode.com>
In-Reply-To: <4F843A22.4020908@isode.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>, "oauth@ietf.org" <oauth@ietf.org>, The IESG <iesg@ietf.org>
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-18.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, 10 Apr 2012 14:02:37 -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-oauth-v2-bearer-18.txt
Reviewer: Alexey Melnikov
Review Date: 10 April 2012
IETF LC End Date: 7 Feb 2012
IESG Telechat date: 12 April 2012

Summary: Nearly ready to be published as Proposed Standard, with a 
couple of things that should be addressed or at least discussed.

Thank you for addressing most of my other issues. However there are a 
couple remaining which I think are important.

Major Issues:

1).
    The "scope" attribute is a space-delimited list of scope values
    indicating the required scope of the access token for accessing the
    requested resource.  In some cases, the "scope" value will be used
    when requesting a new access token with sufficient scope of access to
    utilize the protected resource.  The "scope" attribute MUST NOT
    appear more than once.  The "scope" value is intended for
    programmatic use and is not meant to be displayed to end users.

I don't think this provide enough information about what this is, how it 
is to be used and which values are allowed. As this is not meant to be 
displayed to end users, then you need to say what values are allowed and 
which entity can allocate them. Is there a registry for these tokens, 
e.g. an IANA registry?

The editor provided explanation in email, however this was not reflected 
in any version of the draft.

2). Section "3.1.  Error Codes"

I've suggested to use an IANA registry for this field. Apparently there 
is already a registry created by 
<http://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-11.4>. 
However this document doesn't register values defined in section 3.1 
with IANA and doesn't point to draft-ietf-oauth-v2-23 for the registry. 
I find this to be very confusing.

Minor issues: none

Nits: none


From eran@hueniverse.com  Tue Apr 10 10:29:58 2012
Return-Path: <eran@hueniverse.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 6221D11E80FE; Tue, 10 Apr 2012 10:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h-Sceb1xJA1W; Tue, 10 Apr 2012 10:29:57 -0700 (PDT)
Received: from p3plex2out01.prod.phx3.secureserver.net (p3plex2out01.prod.phx3.secureserver.net [184.168.131.12]) by ietfa.amsl.com (Postfix) with ESMTP id 4178411E80DF; Tue, 10 Apr 2012 10:29:51 -0700 (PDT)
Received: from P3PWEX2HT002.ex2.secureserver.net ([184.168.131.10]) by p3plex2out01.prod.phx3.secureserver.net with bizsmtp id wHVq1i0020Dcg9U01HVqCZ; Tue, 10 Apr 2012 10:29:50 -0700
Received: from P3PWEX2MB008.ex2.secureserver.net ([169.254.8.115]) by P3PWEX2HT002.ex2.secureserver.net ([184.168.131.10]) with mapi id 14.02.0247.003; Tue, 10 Apr 2012 10:29:50 -0700
From: Eran Hammer <eran@hueniverse.com>
To: Richard L.Barnes <rbarnes@bbn.com>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-oauth-v2.all@tools.ietf.org" <draft-ietf-oauth-v2.all@tools.ietf.org>, IETF-Discussion list <ietf@ietf.org>
Thread-Topic: Gen-ART Telechat review of draft-ietf-oauth-v2-25
Thread-Index: AQHNFxtkvp6I6RAu2k+zUIJZ24saaJaUQLLw
Date: Tue, 10 Apr 2012 17:29:50 +0000
Message-ID: <0CBAEB56DDB3A140BA8E8C124C04ECA2FDE162@P3PWEX2MB008.ex2.secureserver.net>
References: <22E22875-8112-42A3-974D-770167AB9536@bbn.com>
In-Reply-To: <22E22875-8112-42A3-974D-770167AB9536@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [71.172.63.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "oauth-chairs@tools.ietf.org" <oauth-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-oauth-v2-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Apr 2012 17:29:58 -0000

Thanks Richard,

IMO, no changes are required as result of this review. I did mention one ch=
ange that's missing from the current draft -25 which was decided during the=
 IETF meeting period and was not push out yet (my appologized) - it is not =
significant.

EH

> -----Original Message-----
> From: Richard L.Barnes [mailto:rbarnes@bbn.com]
> Sent: Tuesday, April 10, 2012 6:11 AM

> MAJOR:
>=20
> General: At several points, the document seems to deal in plain-text
> usernames and passwords, ranging from the requirement for HTTP Basic
> authentication (2.3.1) to the explicit username and password fields one o=
f
> the grant types (4.3.2, 10.7).  In these cases, it seems like it would en=
courage
> better security practices to use some sort of digest or other secure sche=
me
> for proving ownership of passwords.  Otherwise, there's a risk that proxi=
es,
> caches, etc. will have access to users' plaintext credentials.

The use of HTTP Basic is limited to client credentials, not end-user creden=
tials. In both cases, the credentials are sent over a secure channel via TL=
S. The use of HTTP Digest was discussed and ruled out by WG consensus due t=
o its complexity and limited adoption. As a general rule, the WG has opted =
to rely on TLS when transmitting plaintext credentials (as well as not to t=
ransmit them in the URI query).

I believe section 10.7 Resource Owner Password Credentials sufficiently add=
resses these concerns when it comes to end-user credentials.

> General: The document requires the Authorization Server to distinguish
> between confidential and public clients at several points.  It's not clea=
r,
> however, how the server is supposed to tell which is which.  Perhaps Sect=
ion
> 2.1 could elaborate a little more on this?

Addressed in section 2: the client type is provided by the client developer=
 during registration.

BTW, there is one change approved by the WG which has not yet been applied =
to -25 (due to timing issues with the IESG review and IETF meeting feeze). =
The text in section 2.1 beginning with "A client application consisting of"=
 is to be replaced with:

---
A clients may be implemented as a distributed set of components, each with =
a different client type and security context (e.g. a distributed client wit=
h both a confidential server-based component and a public browser-based com=
ponent). If the authorization  server does not provide support for such cli=
ents, or does not provide guidance with regard to their registration, the c=
lient SHOULD register each component as a separate client.
---

> 4: Throughout the document, the assumption is that the client is moved fr=
om
> one URI to another via HTTP redirects (302 responses).  Could the protoco=
l
> also accommodate other techniques of moving clients around, e.g., in
> JavaScript (setting window.location).  It seems like this could make
> deployment much easier in some cases.

302 is only used in two examples but the normative text only discussed "red=
irects" and "directs" which are open to any implementation alternatives.

> 10.3: This section seems to ignore the risk of client impersonation at th=
e
> resource server.  Just as with client credentials in Section 10.2, if an =
access
> token is compromised, then it could be presented by another party in orde=
r
> to access the protected resource.  So the Resource Server needs to
> authenticate the client and validate that the token goes with the client,=
 in
> addition to just checking the validity of the token.

Client authentication is intentionally not included in protected resources =
requests. This is a change made from 1.0 because of significant deployment =
issues.

I can add a warning but there is nothing the resource server can do given t=
he protocol design.

> 10: Throughout this section, there are mentions of which parameters requi=
re
> secure transmission/storage and which do not.  It would be helpful to
> summarize these requirements, say in a table at the end of the section.

I find the current organization with each item featured in a separate secti=
on easier to implement. Also, while some require secure transmission, it is=
 still optional for everything else. Adding such a table might give the wro=
ng impression that this list is normative and restrictive.

> MINOR:
>=20
> 2.3.1: When you say "request body" in this section, do you actually mean
> "query"?  I don't see a prohibition on GET here, in which case the parame=
ters
> would be in the URI query section.

This is only used with the Token Endpoint (3.2) which is limited to POST on=
ly.

> 3.1.2.2: It seems like an explicit requirement would be helpful here, e.g=
.:
> "
> The Authorization Server MUST verify that either no redirect_uri is provi=
ded
> (in which case it uses the registered URI), or else that the provided
> redirect_uri matches the registered redirection URI for the authenticated
> client_id (where the match can be based on a full or partial registered U=
RI).
> "

We did not have WG consensus to mandate redirection URI registration for al=
l clients.

> 4.1.3: Why does this request use redirect_uri and not client_id to identi=
fy the
> client?  (Or both?)  It seems like involving the client_id would better s=
upport
> the goal of client authentication, in order to mitigate the risk of clien=
t
> impersonation.

It does include the client identifier via the client authentication require=
ments specified for the Token endpoint. The example shows that.

Notice the text:

   If the client type is confidential or the client was issued client
   credentials (or assigned other authentication requirements), the
   client MUST authenticate with the authorization server as described
   in Section 3.2.1.

The reason for including the redirect_uri is explained here:

http://hueniverse.com/2011/06/oauth-2-0-redirection-uri-validation/

> 4.3.2: Shouldn't there be a client authentication here? (In particular, a
> client_id.)  Otherwise, it seems like this is essentially the same as the=
  flow in
> 4.4.

Same as above.

> 7. It seems like it would be helpful to have a way to pass access tokens =
in the
> request URI / query in some deployment cases (e.g., a JavaScript based
> client).  Is there any particular reason this was excluded?

It's not. The examples show the header but there is nothing to prevent usin=
g other means. In fact, the bearer draft offers such mechanism (IIRC).

> EDITORIAL:
>=20
> 3. Would be helpful to note here that these endpoints are in addition to =
the
> resource endpoint (the one started out to protect), which is handled in
> Section 7.

The resource endpoint isn't really part of the authorization protocol.
=20
> 3.2: It's not clear why only POST is allowed here.  A couple of words of
> explanation would help.

To prevent credentials from leaking via the URI query. I don't think we nee=
d to explain the reason as we do not explain any other similar choices made=
.

> 5.1: Why bother with a  case-insensitive token_type here?  It doesn't loo=
k
> like anything else in the whole document has this property.

Because it is linked to the HTTP authentication scheme name which is case i=
nsensitive.

EH

From ben@nostrum.com  Tue Apr 10 14:54:02 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 994C611E80FA; Tue, 10 Apr 2012 14:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.368
X-Spam-Level: 
X-Spam-Status: No, score=-102.368 tagged_above=-999 required=5 tests=[AWL=0.232, 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 i1OD7QrXcCRJ; Tue, 10 Apr 2012 14:54: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 F066011E80EA; Tue, 10 Apr 2012 14:54:01 -0700 (PDT)
Received: from [10.0.1.33] (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 q3ALrxTS096421 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 10 Apr 2012 16:53:59 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Apr 2012 16:53:58 -0500
Message-Id: <E2823518-321A-475F-A713-17F28D7828C0@nostrum.com>
To: draft-ietf-ippm-rt-loss.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
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>, The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-ippm-rt-loss-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, 10 Apr 2012 21:54:02 -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-ippm-rt-loss-03
Reviewer: Ben Campbell
Review Date: 2012-04-10
IETF LC End Date: 2012-03-19
IESG Telechat date: 2012-04-12

Summary: This draft is effectively ready for publication as a proposed =
standard, but there are a few minor issues that may need attention =
first.

Major issues:

None

Minor issues:

-- section 5, last paragraph: " ... (or other process, the details of =
which MUST be specified if used)."

Specified how? Does 2330 state what level of spec is needed? I note this =
draft mentions the lack of an IANA registry...

-- section 7, paragraph 4: "Measurement implementations SHOULD address =
this possible outcome."

This seems to conflict with the MUST in the last paragraph of section =
5.4.

-- section 9.1, last paragraph: "should establish bilateral or =
multi-lateral agreements"

Normative?

Also, are such policies really up to the IETF to recommend?

-- section 9.2, first paragraph: "Passive measurement must restrict =
attention"

Normative?



Nits/editorial comments:

-- section 3.2:

Is Tmax measured at src or dst? Does it effectively represent the =
"reasonable" time limit mentioned in TstampDst?

-- section 5.3:

This seems redundant with last paragraph of section 5.

-- section 7, paragraph 4: "As discussed above..."

A section number would be helpful.

-- section 8, 2nd paragraph: "Both unexpected test packet discards and
   the systematic and random errors and uncertainties MUST be recorded."

Sentence needs some commas to demarcate the two choices.=

From Michael.Jones@microsoft.com  Tue Apr 10 17:25:07 2012
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F4D811E812C; Tue, 10 Apr 2012 17:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.732
X-Spam-Level: 
X-Spam-Status: No, score=-3.732 tagged_above=-999 required=5 tests=[AWL=-0.133, 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 0YI2aBARC2Y2; Tue, 10 Apr 2012 17:25:06 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe005.messaging.microsoft.com [216.32.181.185]) by ietfa.amsl.com (Postfix) with ESMTP id 705F211E80FD; Tue, 10 Apr 2012 17:25:06 -0700 (PDT)
Received: from mail193-ch1-R.bigfish.com (10.43.68.226) by CH1EHSOBE004.bigfish.com (10.43.70.54) with Microsoft SMTP Server id 14.1.225.23; Wed, 11 Apr 2012 00:25:05 +0000
Received: from mail193-ch1 (localhost [127.0.0.1])	by mail193-ch1-R.bigfish.com (Postfix) with ESMTP id 7766E2602ED; Wed, 11 Apr 2012 00:25:05 +0000 (UTC)
X-SpamScore: -26
X-BigFish: VS-26(zz9371I542Mzz1202hzz1033IL8275dhz2fh2a8h668h839h944hd25h)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14MLTC101.redmond.corp.microsoft.com; RD:none; EFVD:NLI
Received-SPF: pass (mail193-ch1: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=Michael.Jones@microsoft.com; helo=TK5EX14MLTC101.redmond.corp.microsoft.com ; icrosoft.com ; 
Received: from mail193-ch1 (localhost.localdomain [127.0.0.1]) by mail193-ch1 (MessageSwitch) id 1334103903768780_14168; Wed, 11 Apr 2012 00:25:03 +0000 (UTC)
Received: from CH1EHSMHS024.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.233])	by mail193-ch1.bigfish.com (Postfix) with ESMTP id B6DDD1C0055;	Wed, 11 Apr 2012 00:25:03 +0000 (UTC)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (131.107.125.8) by CH1EHSMHS024.bigfish.com (10.43.70.24) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 11 Apr 2012 00:25:03 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.13]) by TK5EX14MLTC101.redmond.corp.microsoft.com ([157.54.79.178]) with mapi id 14.02.0283.004; Wed, 11 Apr 2012 00:25:02 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>
Thread-Topic: [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-18.txt
Thread-Index: Ac0XeYjHJBC3cdHfRaCIvdSewfDQIQ==
Date: Wed, 11 Apr 2012 00:25:02 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436646237B@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.78]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Cc: General Area Review Team <gen-art@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-18.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, 11 Apr 2012 00:25:07 -0000

Hi Alexey,

About your issue 1:  The OAuth Core spec, where "scope" is primarily define=
d, includes the sentence "The [scope] strings are defined by the authorizat=
ion server" (see http://tools.ietf.org/html/draft-ietf-oauth-v2-25#section-=
3.3).  I could add that clarification to the Bearer spec as well to make it=
 clear that the scope values are context-dependent, if that would address y=
our concern.

About your issue 2:  Investigating the OAuth Errors Registry a bit further =
(see http://tools.ietf.org/html/draft-ietf-oauth-v2-25#section-11.4.1) whil=
e I'd like to be able to register the OAuth Bearer errors in this registry,=
 what I believe to be a defect in the errors registry text currently preven=
ts this.  Specifically, the registry enumerates only three "Error usage loc=
ation" values:  authorization code grant error response, implicit grant err=
or response, and token error response.  To be able to use this registry, it=
 would also have to have a fourth usage location:  "resource access error r=
esponse".  If you'd like to file an issue against the OAuth Core spec to ge=
t this additional usage location added to the registry, then I'd be glad to=
 use it.  I believe that this would be significantly preferable to adding a=
 separate OAuth Bearer errors registry that's exactly like the general-purp=
ose one, only separate from it.

				Best wishes,
				-- Mike

-----Original Message-----
From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of A=
lexey Melnikov
Sent: Tuesday, April 10, 2012 7:03 AM
To: draft-ietf-oauth-v2-bearer.all@tools.ietf.org
Cc: General Area Review Team; oauth@ietf.org; The IESG
Subject: [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-1=
8.txt

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-oauth-v2-bearer-18.txt
Reviewer: Alexey Melnikov
Review Date: 10 April 2012
IETF LC End Date: 7 Feb 2012
IESG Telechat date: 12 April 2012

Summary: Nearly ready to be published as Proposed Standard, with a couple o=
f things that should be addressed or at least discussed.

Thank you for addressing most of my other issues. However there are a coupl=
e remaining which I think are important.

Major Issues:

1).
    The "scope" attribute is a space-delimited list of scope values
    indicating the required scope of the access token for accessing the
    requested resource.  In some cases, the "scope" value will be used
    when requesting a new access token with sufficient scope of access to
    utilize the protected resource.  The "scope" attribute MUST NOT
    appear more than once.  The "scope" value is intended for
    programmatic use and is not meant to be displayed to end users.

I don't think this provide enough information about what this is, how it is=
 to be used and which values are allowed. As this is not meant to be displa=
yed to end users, then you need to say what values are allowed and which en=
tity can allocate them. Is there a registry for these tokens, e.g. an IANA =
registry?

The editor provided explanation in email, however this was not reflected in=
 any version of the draft.

2). Section "3.1.  Error Codes"

I've suggested to use an IANA registry for this field. Apparently there is =
already a registry created by <http://tools.ietf.org/html/draft-ietf-oauth-=
v2-23#section-11.4>.=20
However this document doesn't register values defined in section 3.1 with I=
ANA and doesn't point to draft-ietf-oauth-v2-23 for the registry.=20
I find this to be very confusing.

Minor issues: none

Nits: none

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



From suresh.krishnan@ericsson.com  Tue Apr 10 20:06:56 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 BECE011E80AD for <gen-art@ietfa.amsl.com>; Tue, 10 Apr 2012 20:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGEewBWzRmDC for <gen-art@ietfa.amsl.com>; Tue, 10 Apr 2012 20:06:55 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 35DEB11E8079 for <gen-art@ietf.org>; Tue, 10 Apr 2012 20:06:48 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q3B36fxx001712; Tue, 10 Apr 2012 22:06:43 -0500
Received: from [164.48.125.29] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.32) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 10 Apr 2012 23:06:35 -0400
Message-ID: <4F84F535.5090502@ericsson.com>
Date: Tue, 10 Apr 2012 23:06:29 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120310 Thunderbird/11.0
MIME-Version: 1.0
To: <draft-ietf-dnsext-rfc2671bis-edns0.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-dnsext-rfc2671bis-edns0-08.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, 11 Apr 2012 03:06:56 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

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

Document: draft-ietf-dnsext-rfc2671bis-edns0-08.txt
Reviewer: Suresh Krishnan
Review Date: 2012/04/10
IESG Telechat date: 2012/04/12

Summary: This draft is almost ready for publication as a Standard but it
has some issues.

Substantive:

* Section 6.1.2

The draft defines a new option space for the OPT option codes. It is not
clear who allocates and maintains these. Section 7 seems to talk about
what seems to be a well known IANA policy definition ("Expert Review")
but there is no directive to the IANA to create a new options registry
in the IANA considerations section. Please clarify.

Minor:

* Section 5:

This sentence does not read right the way it is written. It is probably
missing a negative.

OLD:
Extended Label Types are difficult to use due to support in clients
and intermediate gateways...

Propose replacing with

NEW:
Extended Label Types are difficult to use due to the lack of support in
clients and intermediate gateways...


Thanks
Suresh


From matthew.bocci@alcatel-lucent.com  Wed Apr 11 06:45:33 2012
Return-Path: <matthew.bocci@alcatel-lucent.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 92A6B21F8627 for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 06:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.649
X-Spam-Level: 
X-Spam-Status: No, score=-109.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XXsT8Gjrqyja for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 06:45:32 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE9921F8616 for <gen-art@ietf.org>; Wed, 11 Apr 2012 06:45:32 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q3BDhI0I026807 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 11 Apr 2012 15:45:27 +0200
Received: from FRMRSSXCHMBSA3.dc-m.alcatel-lucent.com ([135.120.45.34]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Wed, 11 Apr 2012 15:44:51 +0200
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: Martin Thomson <martin.thomson@gmail.com>, "draft-ietf-pwe3-redundancy.all@tools.ietf.org" <draft-ietf-pwe3-redundancy.all@tools.ietf.org>
Date: Wed, 11 Apr 2012 15:44:45 +0200
Thread-Topic: GenART review of draft-ietf-pwe3-redundancy-06
Thread-Index: Ac0X6URP0RH2aO40Sa2RmNFdTPZyxA==
Message-ID: <CBAA1236.28476%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <CABkgnnWefLUiSfxyEZpMck9moFeu7wHWk9-yAgHKDukLAt7EiQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] GenART review of draft-ietf-pwe3-redundancy-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2012 13:45:33 -0000

Martin,

Many thanks for your review.

Please see below for some comments and proposed amendments to the draft.

Best regards,

Matthew

On 16/03/2012 03:06, "Martin Thomson" <martin.thomson@gmail.com> wrote:

>I am the assigned Gen-ART reviewer for this draft. For background on
>Gen-ART, please see the FAQ at
><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-pwe3-redundancy-06
>Reviewer: Martin Thomson
>Review Date: 2012-03-15
>IETF LC End Date: 2012-03-21
>IESG Telechat date: (if known)
>
>Summary: The draft has some minor issues.
>
>Major issues: none
>
>Minor issues:
>
>3.2.2 states: "The mechanisms for achieving this selection are outside
>the scope of this document."
>
>The example then describes the _conditions_ under which the selection
>is made.  So the statement doesn't quite make sense.  It's reasonable
>to presume that a standard doesn't prescribe the internal behaviour of
>a PE where interoperability is no concern.  Even though this is just
>an example, it makes a very specific presumption about the behaviour
>of the PE in reaction to an event.  I can't imagine any other reaction
>in this case, so I'm left wondering: what exactly is out of scope for
>this?  Communication of the event between PE1 and PE2?

MB> Yes, it's really the communication mechanisms. Those details are
specified in the separate, standards-track,
draft-ietf-pwe3-redundancy-bit, which does impact interoperability.
Therefore I propose updating this sentence to clarify what is out of
scope.=20
"The mechanism for communicating the preferential forwarding status are
outside the scope of this document. "



>
>Section 4.1: "Non-revertive behavior MUST be supported, while
>revertive behavior is OPTIONAL."
>
>The reason for this requirement is non-obvious (at least to me).  Some
>justification for it seems appropriate.

MB> This is an operator requirement to ensure that the protocols developed
in support of PW redundancy at least support non-revertive operation as a
baseline. To implement a revertive behaviour, you will need to designate
one of the Pws=20
as the primary such that you always revert to it when it comes back up and
qualifies for active state.
I believe the consensus when the requirements were discussed was that the
primary mechanism will be optional and that the basic mode of operation
will be to just switch to the next available PW and stick to it until an
event causes a new selection to be performed.
>
>Section 4.1:    "Protection switchover can be triggered by the operator
>[...]"
>
>Again, justification would be nice.  This actually smells more like a
>product specification that requirement for interoperability.  If the
>requirement is, as I suspect, that switchovers triggered by manual
>intervention can be marked as such in the protocol _so that they can
>be treated with lower priority_, then that is definitely
>understandable.

MB> This requirement does have a protocol implication, both in terms of
the state machine and the ability to coordinate the state at both PEs in
the case=20
that a manual switchover is initiated from only one PE.
draft-ietf-pwe3-redundancy-bit
defines a force switchover bit to enable this coordination, and its
operation
is described in Section 6.3.1 of that draft:
"
f.	If while waiting for the acknowledgment, the requesting endpoint
detects that the requested PW went into DOWN state locally, and could use
an alternate PW which is UP, it must perform the following:
i.	Abort the timer.
ii.	Issue a new request to switchover to the alternate PW.
iii.	Re-start the timer.

g.	If, while waiting for the acknowledgment, the requesting endpoint
detects that the requested PW went into the DOWN state locally, and could
not use an alternate PW which is UP, it must perform the following:
i.	Abort the timer.
ii.	Send an update status notification message with the 'Preferential
Forwarding' status bit unchanged and the 'request switchover' bit reset
for the requested PW.
"





>
>Section 4.2:    "[...] MUST support the configuration of revertive or
>non-revertive protection switching modes."
>
>If revertive switching is optional, then this requirement makes not
>sense for (T-)PEs that don't implement it.

MB> Agreed. I propose adding "...if both modes are supported" to the
end of the sentence.


>
>Nits:
>The figures are somewhat difficult to read overall.  It's unclear what
>significance is attached to the dots in many of the diagrams, since
>they aren't always consistent (see Figure 3).
>Figure 5 is especially difficult to read.  Another instance is the
>choice of '.' or '|' in Figure 4, which could have some significance,
>but probably doesn't because the usage is quite inconsistent.  Having
>labels for lines/tunnels impinge on boxes is difficult to interpret.
>Reducing the noise in the diagrams would help.  The text is adequate
>to make up the shortfall.  (Figure 7 is perfectly clear.)
>
>Labeling of PEs in 3.2.2 makes it hard to follow because PE2 is
>attached to CE2.  I'd suggest renames such that you have {CE1, PE1a,
>PE1b} and likewise.
>
>The first requirement in 4.1 is missing a couple of spaces (after the
>comma, in "besupported").

MB> Agreed. In some cases the figures follow established PWE3 conventions
which are '...' for PWs and '=3D=3D=3D' for PSN tunnels, but it is not at a=
ll
consistent. I will try to redraw the diagrams with better consistency.


>
>4.2 has an empty bullet.

MB> Thanks

>
>Not expanded on first use: PSN, LDP

MB> Thanks.

>


From Francis.Dupont@fdupont.fr  Wed Apr 11 07:32:19 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 67E2D21F8512 for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 07:32:19 -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 RhMURGSK5KBy for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 07:32:19 -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 A691821F850C for <gen-art@ietf.org>; Wed, 11 Apr 2012 07:32:18 -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 q3BEWH66057510; Wed, 11 Apr 2012 16:32:17 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201204111432.q3BEWH66057510@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Wed, 11 Apr 2012 16:32:17 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-dhc-dhcpv6-reconfigure-rebind.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-dhc-dhcpv6-reconfigure-rebind-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: Wed, 11 Apr 2012 14:32:19 -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-dhc-dhcpv6-reconfigure-rebind-09.txt
Reviewer: Francis Dupont
Review Date: 20120407
IETF LC End Date: 20120412
IESG Telechat date: 20120412

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:

Note I know very well DHCPv6 so some details could have been too obvious for me...

 - Abstract page 1: RFC 3315 -> RFC 3315 (DHCPv6)

 - Introduction page 4: msg-type -> message type

 - Introduction page 4: I'd like to get a better name for T1 but as far as I know it has
 no name, so I propose: T1 -> the timer T1.

 - 5 page 6: I don't understand (i.e., wording problem) "ignores" in:

   ... If the client
   does not receive a response from the server by the end of the
   retransmission process, the client ignores and discards the
   Reconfigure message.

 - 7 page 6: IMHO the fake Reconfigure message is already a known threat (but I have
  no concern to see it explained again)

Thanks

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Wed Apr 11 08:05:36 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 BE57411E815A for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 08:05:36 -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 jxHIxxf0aJJK for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 08:05:36 -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 D70F511E80AA for <gen-art@ietf.org>; Wed, 11 Apr 2012 08:05:35 -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 q3BF5Y2d059608; Wed, 11 Apr 2012 17:05:35 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201204111505.q3BF5Y2d059608@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Wed, 11 Apr 2012 17:05:34 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-emu-chbind.all@tools.ietf.org
Subject: [Gen-art] review of
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, 11 Apr 2012 15:05:36 -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-emu-chbind-14.txt
Reviewer: Francis Dupont
Review Date: 20120407
IETF LC End Date: 20120412
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - Abstract page 1: NAS -> Network Access Server (BTW NAS has two meanings so this is really
  needed)

 - ToC page 3 and many other places: Radius -> RADIUS

 - Toc page 3 and 12 page 27: Acknowledgements -> Acknowledgments

 - Introduction page 5 (twice) and many other places: e.g. -> e.g.,

 - Introduction page 5: advertized -> advertised

 - 3 page 6: I don't understand (i.e., wording problem):
      ...  the EAP server can be
   far removed from the authenticator.
       ^^^^^^^

 - 3 page 6: Lads -> LANs

 - 3 page 7 and other places: adversarial -> adversarious???
  (BTW if my dictionary can't find it I have no problem to understand it)

 - 4 page 8: I really appreciated this section!

 - 4.1 page 9: a universal or an universal?

 - 4.3 page 12: I don't know the expression "pockets of trust"?

 - 5.2 page 15 (3 times) and at other places: i.e. -> i.e.,

 - 5.3 page 16: IMHO the text should explain before the Figure 2 than the format can
  includes multiple ( Length, NSID, NS-Specific... ) triples (in fact one per attribute
  type)

 - 5.3 page 17: of 1 . -> of 1. (or of "1". if 1. is ambiguous)

 - 7.2 page 21: missing space in the figure?

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length     |             Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
             Value (cont)         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  ^
                                  |

 - 9.1 page 23: interesting conclusion (:-)!

 - 11.1 page 26: what is the size (or range) of this new parameter? IMHO the best
  should be to add a 10-XXX Unassigned line at the end (as it is done for eap-numbers).
  Note I believe IANA will have the same request...

 - 12 page 27: Sam hartman -> Sam Hartman

 - A.5 page 30: make the peer believe -> to believe?

 - A.5 page 30: from the on the -> from the one the?

Thanks

Francis.Dupont@fdupont.fr

From Francis.Dupont@fdupont.fr  Wed Apr 11 08:42:17 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 0C1C021F84EB for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 08:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, J_CHICKENPOX_36=0.6, J_CHICKENPOX_43=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktu3AclpVT3G for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 08:42:16 -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 3DE3121F84EA for <gen-art@ietf.org>; Wed, 11 Apr 2012 08:42:16 -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 q3BFgFsG061765; Wed, 11 Apr 2012 17:42:15 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201204111542.q3BFgFsG061765@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Wed, 11 Apr 2012 17:42:15 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-avtcore-feedback-supression-rtp-16.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, 11 Apr 2012 15:42:17 -0000

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

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

Document: draft-ietf-avtcore-feedback-supression-16.txt
Reviewer: Francis Dupont
Review Date: 20120323
IETF LC End Date: 20120326
IESG Telechat date: 20120412

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:

These are about the -15 version updated to -16

 - I-D name: supression -> suppression

 - Abstract page 1: implosion -> explosion (things which can implode are rare :-)

 - Abstract page 1: signalling -> signaling

 - Toc page 2 and 9 page 12: Acknowledgement -> Acknowledgment

 - Introduction page 4: RTCP is not a well known abbrev: as it is first you have
 to introduce it.

 - Introduction page 4: same for SSM: please introduce the abbrev

 - Introduction page 4: implosion -> explosion

 - Introduction page 4 and other places: e.g. -> e.g.,

 - 3 page 6: ,which -> , which

 - 4 page 6: missing characters/words in "the PT, FMT,length SSRC"

 - 4.1 page 7: all caps in "transport layer third-party loss"

 - 4.2 page 7: if the SSRC is an IPv4 address the "set to 0" is not very correct.

 - 4.2 page 7: media Source -> media source

 - 4.2 page 8: :32 -> : 32

 - 6.1 page 9: source- specific -> source-specific

 - 6.1 page 9: reason( -> reason ( & a RTCP -> an RTCP & NACK)and -> NACK) and

 - 6.2 page 10: Sources(BRS) -> Sources (BRS)

 - 6.2 page 10: a RTCP -> an RTCP

 - 6.4 page 10: receivers. e.g., -> receivers: e.g.,

 - 6.4 page 10:	a RTCP -> an RTCP

 - 6.5 page 11: a RTCP -> an RTCP (with a line break in the middle :-)

 - 7 page 11: supression -> suppression

 - 9 page 12: Acknowledgement -> Acknowledgment, VAN CAENEGEM -> van Caenegem,
  Johansson S -> Johansson

 - 10.2 page 14: please give the names of I-Ds

 - Appendix A page 14: usually the change log is in the reverse order (?)

 - A.8 page 16: ,Security -> , Security

 - A.14 page 17: refereces -> references

Regards

Francis.Dupont@fdupont.fr

From martin.thomson@gmail.com  Wed Apr 11 08:55:25 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 D5D6111E80AA for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 08:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.037
X-Spam-Level: 
X-Spam-Status: No, score=-4.037 tagged_above=-999 required=5 tests=[AWL=-0.438, 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 TgyvsliUyM8c for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 08:55: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 EF1A011E809C for <gen-art@ietf.org>; Wed, 11 Apr 2012 08:55:23 -0700 (PDT)
Received: by bkuw5 with SMTP id w5so1020482bku.31 for <gen-art@ietf.org>; Wed, 11 Apr 2012 08:55:23 -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:content-transfer-encoding; bh=bsafEqXIIdujL7H8e4iiFMbxWyQP9sVjeXj1Xvld3Rs=; b=eR+tgef4Y9DyvGpr4YoV/0q5w2l6METcpvfE3qhGk0JP8i99zbujCo2yUlSS0ANYBR zBJ2FoyKySDmqybAIU3Gj5Z82swcHrM+OhRsuiyd05YjSyLB9bDXPiVxdweZfW7xoFOX JndOTd/z1+NvYuBquTegGin8YjDf+ey/z26vS6H/byB733F3Po2IzTpIeaoUY8yPkpuK 2sT094pSzWoUWyyK9N18kVj25PdiV1Z4HaU+2r59UcERw/MeyXM+vOLYp2I/kSDu7qqt 6JcpXggyDMForY3ROsII334C6rAH4VKKamlQGbTsvIdkSeEB8hHcCI26XF7f2FXUxuAG cwFA==
MIME-Version: 1.0
Received: by 10.204.156.79 with SMTP id v15mr6193549bkw.37.1334159722926; Wed, 11 Apr 2012 08:55:22 -0700 (PDT)
Received: by 10.204.165.66 with HTTP; Wed, 11 Apr 2012 08:55:22 -0700 (PDT)
In-Reply-To: <CBAA1236.28476%matthew.bocci@alcatel-lucent.com>
References: <CABkgnnWefLUiSfxyEZpMck9moFeu7wHWk9-yAgHKDukLAt7EiQ@mail.gmail.com> <CBAA1236.28476%matthew.bocci@alcatel-lucent.com>
Date: Wed, 11 Apr 2012 08:55:22 -0700
Message-ID: <CABkgnnV8WCeQWiYY9wdVfQM8p5n=S6JxdqQ4gZgkLxg21J8RMw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "draft-ietf-pwe3-redundancy.all@tools.ietf.org" <draft-ietf-pwe3-redundancy.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] GenART review of draft-ietf-pwe3-redundancy-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2012 15:55:25 -0000

On 11 April 2012 06:44, Bocci, Matthew (Matthew)
<matthew.bocci@alcatel-lucent.com> wrote:
> MB> Yes, it's really the communication mechanisms. Those details are
> specified in the separate, standards-track,
> draft-ietf-pwe3-redundancy-bit, which does impact interoperability.
> Therefore I propose updating this sentence to clarify what is out of
> scope.
> "The mechanism for communicating the preferential forwarding status are
> outside the scope of this document. "

Since you have the reference, is the reason you don't want to
reference it that you don't want a downref?

>>Section 4.1: "Non-revertive behavior MUST be supported, while
>>revertive behavior is OPTIONAL."
>>
>>The reason for this requirement is non-obvious (at least to me). =C2=A0So=
me
>>justification for it seems appropriate.
>
> MB> This is an operator requirement to ensure that the protocols develope=
d
> in support of PW redundancy at least support non-revertive operation as a
> baseline. To implement a revertive behaviour, you will need to designate
> one of the Pws

So you had a choice: one mandatory, but which; or both mandatory.  The
WG chose non-revertive as the only mandatory option.  I guess I was
(obliquely) requesting that you provide motivation in the document,
rather than just in response to my mail.

>>Section 4.1: =C2=A0 =C2=A0"Protection switchover can be triggered by the =
operator
> MB> This requirement does have a protocol implication, both in terms of
> the state machine and the ability to coordinate the state at both PEs in
> the case
> that a manual switchover is initiated from only one PE.

The process that you describe doesn't address that requirement.  That
process ensures that operator intervention doesn't cause a failure by
ensuring that the operator is unable to disable a redundant PW by
removing the only active path.  From the protocol perspective, you
need a mechanism for signaling that a path is being administratively
disabled.

So:

Requirement: Protection switchover can be initiated by either PE.
Motivation: Operator intervention may be necessary to disable one part
of a redundant PW.

Product requirement: Operator intervention shall not be able to
disable a PW by disabling the only available part of a redundant PW.

(Excuse the sloppy terminology, it's been a while and I'm too lazy to
get this right.)

I don't have any real problem with your explanations, but it seems to
me at least that it could be made clearer.  Don't feel obligated to
change on my accord alone, but there are value in being really clear
about these requirements.

--Martin

From matthew.bocci@alcatel-lucent.com  Wed Apr 11 09:31:33 2012
Return-Path: <matthew.bocci@alcatel-lucent.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 CE13411E809F for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 09:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.949
X-Spam-Level: 
X-Spam-Status: No, score=-107.949 tagged_above=-999 required=5 tests=[AWL=-1.700, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id isFPMH44l7Ve for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 09:31:33 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [62.23.212.42]) by ietfa.amsl.com (Postfix) with ESMTP id F1B3711E80AA for <gen-art@ietf.org>; Wed, 11 Apr 2012 09:31:32 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q3BGVSgg031199 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 11 Apr 2012 18:31:28 +0200
Received: from FRMRSSXCHMBSA3.dc-m.alcatel-lucent.com ([135.120.45.34]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Wed, 11 Apr 2012 18:31:28 +0200
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 11 Apr 2012 18:31:18 +0200
Thread-Topic: GenART review of draft-ietf-pwe3-redundancy-06
Thread-Index: Ac0YAItj8mmkt7XcQbGaEsXUR9hKjw==
Message-ID: <CBAB69E9.28C5C%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <CABkgnnV8WCeQWiYY9wdVfQM8p5n=S6JxdqQ4gZgkLxg21J8RMw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "draft-ietf-pwe3-redundancy.all@tools.ietf.org" <draft-ietf-pwe3-redundancy.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] GenART review of draft-ietf-pwe3-redundancy-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2012 16:31:33 -0000

Martin,

On 11/04/2012 16:55, "Martin Thomson" <martin.thomson@gmail.com> wrote:

>On 11 April 2012 06:44, Bocci, Matthew (Matthew)
><matthew.bocci@alcatel-lucent.com> wrote:
>> MB> Yes, it's really the communication mechanisms. Those details are
>> specified in the separate, standards-track,
>> draft-ietf-pwe3-redundancy-bit, which does impact interoperability.
>> Therefore I propose updating this sentence to clarify what is out of
>> scope.
>> "The mechanism for communicating the preferential forwarding status are
>> outside the scope of this document. "
>
>Since you have the reference, is the reason you don't want to
>reference it that you don't want a downref?

MB> No. This is a framework/requirements document, and
the WG made a specific decision early on to separate this from the
mechanism used to convey preferential forwarding status.


>
>>>Section 4.1: "Non-revertive behavior MUST be supported, while
>>>revertive behavior is OPTIONAL."
>>>
>>>The reason for this requirement is non-obvious (at least to me).  Some
>>>justification for it seems appropriate.
>>
>> MB> This is an operator requirement to ensure that the protocols
>>developed
>> in support of PW redundancy at least support non-revertive operation as
>>a
>> baseline. To implement a revertive behaviour, you will need to designate
>> one of the Pws
>
>So you had a choice: one mandatory, but which; or both mandatory.  The
>WG chose non-revertive as the only mandatory option.  I guess I was
>(obliquely) requesting that you provide motivation in the document,
>rather than just in response to my mail.


MB> I propose modifying the paragraph as follows:

 o  Non-revertive behavior MUST be supported, while revertive behavior
      is OPTIONAL. This avoids the need to designate one PW as primary
unless revertive
behavior is explicitly required.


>
>>>Section 4.1:    "Protection switchover can be triggered by the operator
>> MB> This requirement does have a protocol implication, both in terms of
>> the state machine and the ability to coordinate the state at both PEs in
>> the case
>> that a manual switchover is initiated from only one PE.
>
>The process that you describe doesn't address that requirement.  That
>process ensures that operator intervention doesn't cause a failure by
>ensuring that the operator is unable to disable a redundant PW by
>removing the only active path.  From the protocol perspective, you
>need a mechanism for signaling that a path is being administratively
>disabled.
>
>So:
>
>Requirement: Protection switchover can be initiated by either PE.
>Motivation: Operator intervention may be necessary to disable one part
>of a redundant PW.
>
>Product requirement: Operator intervention shall not be able to
>disable a PW by disabling the only available part of a redundant PW.
>
>(Excuse the sloppy terminology, it's been a while and I'm too lazy to
>get this right.)
>
>I don't have any real problem with your explanations, but it seems to
>me at least that it could be made clearer.  Don't feel obligated to
>change on my accord alone, but there are value in being really clear
>about these requirements.

MB> I propose modifying the paragraph as follows:

  o  Protection switchover can be initiated from a PE e.g. using
      a Manual lockout/force switchover, or it may be triggered by a
      signal failure i.e. a defect in the PW or PSN. Manual switchover may
be necessary=20
if it is required to disable one PW in a redundant set. Both methods MUST
      be supported and signal failure triggers MUST be treated with a
      higher priority than any local or far-end manual
      trigger.


Regards

Matthew


>
>--Martin


From martin.thomson@gmail.com  Wed Apr 11 10:23:18 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 061AC11E8089 for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 10:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.988
X-Spam-Level: 
X-Spam-Status: No, score=-3.988 tagged_above=-999 required=5 tests=[AWL=-0.389, 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 u-n4Igfqu-3c for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 10:23:17 -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 E705E11E809B for <gen-art@ietf.org>; Wed, 11 Apr 2012 10:23:16 -0700 (PDT)
Received: by bkuw5 with SMTP id w5so1105099bku.31 for <gen-art@ietf.org>; Wed, 11 Apr 2012 10:23: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:content-transfer-encoding; bh=PnY6lOoEgUr4pCRrEowXDsI4Gw98ZvNsbk8Nx7gABoc=; b=btJe+D7fDwYmnOCBqDh9ARJ3oO1TLWaokqThRzslmk5GNm0Hq+eX7Era2Ob8MJFiRD /+H30mWnz6CeuuZ1v5RBjFaCSgvEjyQNsm5iEycOLrnwHMtBAK3N/tnGmtennXLtZaTW Y1yFXsMqPAhSYWDrGAO3ldtvIlHYCQO8YaABDCgp057HlLybZFe/DCmk5pzGoUEFVQT8 6CwLGsSZkfQNtCPamAUjs0bTF1QsE6DCQrnEdEOyXsELTmUHVU5kQbpZXQbbUYtzovg4 MP2uSDCFGXaAB/e+slgtS5m3h51OfWaRdEqvter0Yp03sQjU4i+QVmComCMG/Yj5mccb grCw==
MIME-Version: 1.0
Received: by 10.205.138.9 with SMTP id iq9mr6280150bkc.139.1334164996004; Wed, 11 Apr 2012 10:23:16 -0700 (PDT)
Received: by 10.204.165.66 with HTTP; Wed, 11 Apr 2012 10:23:15 -0700 (PDT)
In-Reply-To: <CBAB69E9.28C5C%matthew.bocci@alcatel-lucent.com>
References: <CABkgnnV8WCeQWiYY9wdVfQM8p5n=S6JxdqQ4gZgkLxg21J8RMw@mail.gmail.com> <CBAB69E9.28C5C%matthew.bocci@alcatel-lucent.com>
Date: Wed, 11 Apr 2012 10:23:15 -0700
Message-ID: <CABkgnnV-HaVLCy+YfCdRJv9ddcUFBP8wv3xqY1bj0Z6yONHsjw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "draft-ietf-pwe3-redundancy.all@tools.ietf.org" <draft-ietf-pwe3-redundancy.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] GenART review of draft-ietf-pwe3-redundancy-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2012 17:23:18 -0000

Thanks! Looks good.

On 11 April 2012 09:31, Bocci, Matthew (Matthew)
<matthew.bocci@alcatel-lucent.com> wrote:
> Martin,
>
> On 11/04/2012 16:55, "Martin Thomson" <martin.thomson@gmail.com> wrote:
>
>>On 11 April 2012 06:44, Bocci, Matthew (Matthew)
>><matthew.bocci@alcatel-lucent.com> wrote:
>>> MB> Yes, it's really the communication mechanisms. Those details are
>>> specified in the separate, standards-track,
>>> draft-ietf-pwe3-redundancy-bit, which does impact interoperability.
>>> Therefore I propose updating this sentence to clarify what is out of
>>> scope.
>>> "The mechanism for communicating the preferential forwarding status are
>>> outside the scope of this document. "
>>
>>Since you have the reference, is the reason you don't want to
>>reference it that you don't want a downref?
>
> MB> No. This is a framework/requirements document, and
> the WG made a specific decision early on to separate this from the
> mechanism used to convey preferential forwarding status.
>
>
>>
>>>>Section 4.1: "Non-revertive behavior MUST be supported, while
>>>>revertive behavior is OPTIONAL."
>>>>
>>>>The reason for this requirement is non-obvious (at least to me). =C2=A0=
Some
>>>>justification for it seems appropriate.
>>>
>>> MB> This is an operator requirement to ensure that the protocols
>>>developed
>>> in support of PW redundancy at least support non-revertive operation as
>>>a
>>> baseline. To implement a revertive behaviour, you will need to designat=
e
>>> one of the Pws
>>
>>So you had a choice: one mandatory, but which; or both mandatory. =C2=A0T=
he
>>WG chose non-revertive as the only mandatory option. =C2=A0I guess I was
>>(obliquely) requesting that you provide motivation in the document,
>>rather than just in response to my mail.
>
>
> MB> I propose modifying the paragraph as follows:
>
> =C2=A0o =C2=A0Non-revertive behavior MUST be supported, while revertive b=
ehavior
> =C2=A0 =C2=A0 =C2=A0is OPTIONAL. This avoids the need to designate one PW=
 as primary
> unless revertive
> behavior is explicitly required.
>
>
>>
>>>>Section 4.1: =C2=A0 =C2=A0"Protection switchover can be triggered by th=
e operator
>>> MB> This requirement does have a protocol implication, both in terms of
>>> the state machine and the ability to coordinate the state at both PEs i=
n
>>> the case
>>> that a manual switchover is initiated from only one PE.
>>
>>The process that you describe doesn't address that requirement. =C2=A0Tha=
t
>>process ensures that operator intervention doesn't cause a failure by
>>ensuring that the operator is unable to disable a redundant PW by
>>removing the only active path. =C2=A0From the protocol perspective, you
>>need a mechanism for signaling that a path is being administratively
>>disabled.
>>
>>So:
>>
>>Requirement: Protection switchover can be initiated by either PE.
>>Motivation: Operator intervention may be necessary to disable one part
>>of a redundant PW.
>>
>>Product requirement: Operator intervention shall not be able to
>>disable a PW by disabling the only available part of a redundant PW.
>>
>>(Excuse the sloppy terminology, it's been a while and I'm too lazy to
>>get this right.)
>>
>>I don't have any real problem with your explanations, but it seems to
>>me at least that it could be made clearer. =C2=A0Don't feel obligated to
>>change on my accord alone, but there are value in being really clear
>>about these requirements.
>
> MB> I propose modifying the paragraph as follows:
>
> =C2=A0o =C2=A0Protection switchover can be initiated from a PE e.g. using
> =C2=A0 =C2=A0 =C2=A0a Manual lockout/force switchover, or it may be trigg=
ered by a
> =C2=A0 =C2=A0 =C2=A0signal failure i.e. a defect in the PW or PSN. Manual=
 switchover may
> be necessary
> if it is required to disable one PW in a redundant set. Both methods MUST
> =C2=A0 =C2=A0 =C2=A0be supported and signal failure triggers MUST be trea=
ted with a
> =C2=A0 =C2=A0 =C2=A0higher priority than any local or far-end manual
> =C2=A0 =C2=A0 =C2=A0trigger.
>
>
> Regards
>
> Matthew
>
>
>>
>>--Martin
>

From nabil.n.bitar@verizon.com  Wed Apr 11 13:09:03 2012
Return-Path: <nabil.n.bitar@verizon.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 1A35C11E80BB; Wed, 11 Apr 2012 13:09:03 -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 0oG0nKdcJ-d7; Wed, 11 Apr 2012 13:09:02 -0700 (PDT)
Received: from fldsmtpe03.verizon.com (fldsmtpe03.verizon.com [140.108.26.142]) by ietfa.amsl.com (Postfix) with ESMTP id 0202E11E8075; Wed, 11 Apr 2012 13:09:01 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi02.verizon.com) ([166.68.71.144]) by fldsmtpe03.verizon.com with ESMTP; 11 Apr 2012 20:09:01 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
X-IronPort-AV: E=Sophos;i="4.75,406,1330905600";  d="scan'208,217";a="251432354"
Received: from fldp1lumxc7hb01.verizon.com (HELO FLDP1LUMXC7HB01.us.one.verizon.com) ([166.68.45.78]) by fldsmtpi02.verizon.com with ESMTP; 11 Apr 2012 20:09:01 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([169.254.3.155]) by FLDP1LUMXC7HB01.us.one.verizon.com ([166.68.45.78]) with mapi; Wed, 11 Apr 2012 16:09:01 -0400
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-ancp-pon.all@tools.ietf.org" <draft-ietf-ancp-pon.all@tools.ietf.org>
Date: Wed, 11 Apr 2012 16:09:01 -0400
Thread-Topic: Gen-ART LC review of draft-ietf-ancp-pon-02
Thread-Index: Ac0YHu+pZKCam1sKTTW3ItioRETerA==
Message-ID: <CBAB592E.25BBC%nabil.n.bitar@verizon.com>
In-Reply-To: <4f7875ec.6965b40a.3e21.5e69@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.10.0.110310
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CBAB592E25BBCnabilnbitarverizoncom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 11 Apr 2012 13:09:59 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, 'IETF' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-ancp-pon-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2012 20:09:03 -0000

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

Hi,
Thanks for the comments. Please see inline.

Thanks,
Nabil

From: Roni Even <ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>>
Date: Sun, 1 Apr 2012 11:34:54 -0400
To: "draft-ietf-ancp-pon.all@tools.ietf.org<mailto:draft-ietf-ancp-pon.all@=
tools.ietf.org>" <draft-ietf-ancp-pon.all@tools.ietf.org<mailto:draft-ietf-=
ancp-pon.all@tools.ietf.org>>
Cc: "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:ge=
n-art@ietf.org>>, 'IETF' <ietf@ietf.org<mailto:ietf@ietf.org>>
Subject: Gen-ART LC review of draft-ietf-ancp-pon-02

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>.
Sorry for the late review due to IET meeting.
Please resolve these comments along with any other Last Call comments you m=
ay receive.



Document: draft-ietf-ancp-pon-02

Reviewer: Roni Even

Review Date:2012=964=961

IETF LC End Date: 2012=963=9630

IESG Telechat date:



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



Major issues:



Minor issues:



Nits/editorial comments:



In section 4 =94However, the broadcast capability on the PON enables the AN=
 (OLT) to send one copy on the PON as opposed to N  copies of a multicast c=
hannel on the PON serving N premises being  receivers=94 I think the =93bei=
ng=94 before the last word should be deleted

<NB> are you OK saying: "However, the broadcast capability on the PON enabl=
es the AN (OLT) to send one copy on the PON as opposed to one copy to each =
receiver on the PON



General editorial comment is about page breaks which can be better like sec=
tion 7 title is at the end of a page and the text is in the next page. Also=
 some of the figures and their descriptions are split between pages.

<NB> will address that.


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

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;=
 -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14p=
x; font-family: Calibri, sans-serif; "><div>Hi,</div><div>Thanks for the co=
mments. Please see inline.</div><div><br></div><div>Thanks,</div><div>Nabil=
</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div style=3D"font-f=
amily:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM:=
 medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: =
0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: mediu=
m none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From: </span> Ro=
ni Even &lt;<a href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.co=
m</a>&gt;<br><span style=3D"font-weight:bold">Date: </span> Sun, 1 Apr 2012=
 11:34:54 -0400<br><span style=3D"font-weight:bold">To: </span> &quot;<a hr=
ef=3D"mailto:draft-ietf-ancp-pon.all@tools.ietf.org">draft-ietf-ancp-pon.al=
l@tools.ietf.org</a>&quot; &lt;<a href=3D"mailto:draft-ietf-ancp-pon.all@to=
ols.ietf.org">draft-ietf-ancp-pon.all@tools.ietf.org</a>&gt;<br><span style=
=3D"font-weight:bold">Cc: </span> &quot;<a href=3D"mailto:gen-art@ietf.org"=
>gen-art@ietf.org</a>&quot; &lt;<a href=3D"mailto:gen-art@ietf.org">gen-art=
@ietf.org</a>&gt;, 'IETF' &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.or=
g</a>&gt;<br><span style=3D"font-weight:bold">Subject: </span> Gen-ART LC r=
eview of draft-ietf-ancp-pon-02<br></div><div><br></div><div xmlns:v=3D"urn=
:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:off=
ice" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xmlns:m=3D"http://sc=
hemas.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-=
html40"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--><div lang=3D"EN-US" link=3D"blue" vlink=
=3D"purple"><div class=3D"WordSection1"><p class=3D"MsoNormal">I am the ass=
igned Gen-ART reviewer for this draft. For background on Gen-ART, please se=
e the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/G=
enArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/G=
enArtfaq</a>&gt;.<o:p></o:p></p><p class=3D"MsoNormal">Sorry for the late r=
eview due to IET meeting.<o:p></o:p></p><p class=3D"MsoNormal">Please resol=
ve these comments along with any other Last Call comments you may receive.<=
o:p></o:p></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; fon=
t-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p class=3D"Ms=
oPlainText"><span lang=3D"FR" style=3D"font-size: 11pt; font-family: Calibr=
i, sans-serif; ">Document: </span><span lang=3D"FR" style=3D"font-size: 11p=
t; font-family: Calibri, sans-serif; ">draft-ietf-ancp-pon-02</span><span l=
ang=3D"FR" style=3D"font-size: 11pt; font-family: Calibri, sans-serif; "><o=
:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11p=
t; font-family: Calibri, sans-serif; ">Reviewer: Roni Even<o:p></o:p></span=
></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family:=
 Calibri, sans-serif; ">Review Date:2012=964=961<o:p></o:p></span></p><p cl=
ass=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">IETF LC End Date: 2012=963=9630<o:p></o:p></span></p><p class=
=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calibri, san=
s-serif; ">IESG Telechat date:<o:p></o:p></span></p><p class=3D"MsoPlainTex=
t"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; "><o:p=
>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size:=
 11pt; font-family: Calibri, sans-serif; ">Summary: This draft is ready for=
 publication as an Informational </span><span style=3D"font-size: 11pt; fon=
t-family: Calibri, sans-serif; ">RFC</span><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">.<o:p></o:p></span></p><p class=3D"MsoP=
lainText"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif;=
 "><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span style=3D"fon=
t-size: 11pt; font-family: Calibri, sans-serif; ">Major issues:<o:p></o:p><=
/span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-fa=
mily: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPla=
inText"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; "=
>Minor issues:<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=
=3D"font-size: 11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p><=
/span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-fa=
mily: Calibri, sans-serif; ">Nits/editorial comments:<o:p></o:p></span></p>=
<p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Cali=
bri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><s=
pan style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">In sectio=
n 4 =94</span><span style=3D"font-size: 11pt; font-family: Calibri, sans-se=
rif; ">However, the broadcast capability on the PON enables the AN (OLT) to=
 send one copy on the PON as opposed to N&nbsp; copies of a multicast chann=
el on the PON serving N premises being&nbsp; receivers=94 I think the =93be=
ing=94 before the last word should be deleted</span></p></div></div></div><=
/span><div><br></div><div>&lt;NB&gt; are you OK saying: &quot;<span class=
=3D"Apple-style-span" style=3D"font-size: 15px; ">However, the broadcast ca=
pability on the PON enables the AN (OLT) to send one copy on the PON as opp=
osed to one copy to each receiver on the PON&nbsp;</span></div><span id=3D"=
OLK_SRC_BODY_SECTION"><div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:=
o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schemas-micros=
oft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12=
/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><div lang=3D"EN-US" link=
=3D"blue" vlink=3D"purple"><div class=3D"WordSection1"><p class=3D"MsoPlain=
Text"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; "><=
o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11=
pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p clas=
s=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calibri, sa=
ns-serif; ">General editorial comment is about page breaks which can be bet=
ter like section 7 title is at the end of a page and the text is in the nex=
t page. Also some of the figures and their descriptions are split between p=
ages.<o:p></o:p></span></p></div></div></div></span><div>&lt;NB&gt; will ad=
dress that.</div><span id=3D"OLK_SRC_BODY_SECTION"><div xmlns:v=3D"urn:sche=
mas-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-html4=
0"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSec=
tion1"><p class=3D"MsoNormal"><span lang=3D"HE" dir=3D"RTL" style=3D"font-f=
amily: Arial, sans-serif; "><o:p>&nbsp;</o:p></span></p></div></div></div><=
/span></body></html>

--_000_CBAB592E25BBCnabilnbitarverizoncom_--

From david.black@emc.com  Wed Apr 11 14:49:44 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 1C5C911E80EC; Wed, 11 Apr 2012 14:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.355
X-Spam-Level: 
X-Spam-Status: No, score=-110.355 tagged_above=-999 required=5 tests=[AWL=0.244, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2lZ5bW4PwfrF; Wed, 11 Apr 2012 14:49:43 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 365A811E80DC; Wed, 11 Apr 2012 14:49:36 -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 q3BLnXDc010891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Apr 2012 17:49:34 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 11 Apr 2012 17:49:25 -0400
Received: from mxhub02.corp.emc.com (mxhub02.corp.emc.com [10.254.141.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q3BLnOsW015710; Wed, 11 Apr 2012 17:49:24 -0400
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub02.corp.emc.com ([10.254.141.104]) with mapi; Wed, 11 Apr 2012 17:49:23 -0400
From: <david.black@emc.com>
To: <leifj@nordu.net>, <gen-art@ietf.org>, <ietf@ietf.org>
Date: Wed, 11 Apr 2012 17:49:23 -0400
Thread-Topic: Gen-ART review of draft-johansson-loa-registry-05
Thread-Index: Ac0QSf/k5rjw1b7/R4GhUN2VW96SjgH4d37Q
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120535DC@MX15A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E80811@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E80811@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
Cc: tim.polk@nist.gov
Subject: [Gen-art] Gen-ART review of draft-johansson-loa-registry-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: Wed, 11 Apr 2012 21:49:44 -0000

The -05 version of this draft resolves all of the issues and comments raise=
d
in the Gen-ART review of the -04 version.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Sunday, April 01, 2012 4:57 PM
> To: leifj@nordu.net; gen-art@ietf.org; ietf@ietf.org
> Cc: Black, David; Sean Turner; tim.polk@nist.gov
> Subject: Gen-ART review of draft-johansson-loa-registry-04
>=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-johansson-loa-registry-04
> Reviewer: David L. Black
> Review Date: April 1, 2012
> IETF LC End Date: April 3, 2012
> IESG Telechat date: April 12, 2012
>=20
> This draft establishes an IETF registry of SAML Level of Assurance (LoA)
> profiles;
> it's short and clear, although it does not contain any initial content fo=
r the
> registry - presumably that will be supplied after the registry is created=
 via
> the
> expert review registration mechanism established by this draft.
>=20
> Summary:
> This draft is on the right track but has open issues, described in the re=
view.
>=20
> Major issues: (1)
> My major open issue concerns the last paragraph in the Introduction:
>=20
>    Although the registry will contain URIs that reference SAML
>    Authentication Context Profiles other protocols MAY use such URIs to
>    represent levels of assurance definitions without relying on their
>    SAML XML definitions.  Use of the registry by protocols other than
>    SAML or OpenID Connect is encouraged.
>=20
> While this is good in principle, and one presumes that each registration =
of
> sets of profiles from an existing protocol will be self-consistent, this
> text also encourages other (e.g., new) protocols to draw upon this regist=
ry
> without providing any guidance.  I'm concerned that it's probably possibl=
e
> to make a serious mess in a new protocol by using an LoA or two from mult=
iple
> sets of registered LoAs without paying attention to whether the resulting
> collection of LoAs is consistent or coherent (or even sensible) for use i=
n
> a single protocol.  This concern is reinforced by the guidance to expert
> reviewers in Section 4.1, which effectively conveys a desire to get all
> of the reasonable LoA profiles registered here, regardless of source or
> consistency with other registered LoA profiles.
>=20
> I'd like to see some guidance to protocol designers and others for how to
> appropriately select multiple LoA profiles from this registry in a fashio=
n
> that results in a consistent and (hopefully) usable collection.  For exam=
ple,
> it may be a good idea to use (or start with) a set of related profiles al=
ready
> in use by an existing protocol in preference to mixing/matching individua=
l
> profiles from multiple existing protocols.  At some level, this is common
> sense advice that the presence of profiles in this registry does not obvi=
ate
> the need to apply good design judgment, but that does deserve to be state=
d.
>=20
> Minor issues: (2)
>=20
> (1) This draft is intended to be an informational RFC, but it uses
> RFC 2119 keywords.  That's only a good idea in exceptional circumstances.=
 I
> suggest removing section 1.1 and replacing upper case MUST/SHOULD/MAY wit=
h
> their lower case versions or reworded explanations of rationale.  Most of
> the uses of RFC 2119 keywords are not protocol requirements, but requirem=
ents
> on IANA, registrants, and users of the registry for which RFC 2119 keywor=
ds
> are not appropriate, e.g., see RFC 2119 section 6:
>=20
>    Imperatives of the type defined in this memo must be used with care
>    and sparingly.  In particular, they MUST only be used where it is
>    actually required for interoperation or to limit behavior which has
>    potential for causing harm (e.g., limiting retransmisssions)
>=20
> (2) Section 4
>=20
> OLD
>    The initial pool of expert and the
>    review criteria are outlined below.
> NEW
>    The review criteria are outlined below.
>=20
> The initial pool of experts is not designated by this draft.
>=20
> Nits/editorial comments:
>=20
> Section 3
>=20
> OLD
>    The following ABNF productions represent reserved values and names
> NEW
>    The reserved element defined by the following ABNF productions represe=
nts
>    a set of reserved values and names
>=20
> Section 4
>=20
>    The registry is to be operated under the "Designated Expert Review"
>    policy from RFC5226 [RFC5226] employing a pool of experts
>=20
> Nope, the actual RFC5226 name of that well-known IANA policy is Expert
> Review (or Designated Expert), see section 4.1 of RFC5226.  If that
> well-known IANA policy isn't what was intended, this is a serious
> open issue.
>=20
> Top of p.7
>    The presense of an entry in the registy MUST NOT be taken to imply
>                                          ^
> r ---------------------------------------/
>=20
> Section 7
>=20
> OLD
>    An implementor of MUST NOT treat the registry as a trust framework or
> NEW
>    A protocol implementor MUST NOT treat the registry as a trust framewor=
k or
>=20
> The minor issue about RFC 2119 keywords also applies to this text.
>=20
> idnits 2.12.13 did not find any nits that need attention.
>=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 leifj@sunet.se  Wed Apr 11 14:50:47 2012
Return-Path: <leifj@sunet.se>
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 2E2E911E80EC; Wed, 11 Apr 2012 14:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level: 
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118,  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 m2mflu4IsvcE; Wed, 11 Apr 2012 14:50:46 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id 6D0E511E80DC; Wed, 11 Apr 2012 14:50:46 -0700 (PDT)
Received: from [10.0.0.11] (ua-83-227-179-169.cust.bredbandsbolaget.se [83.227.179.169]) (authenticated bits=0) by backup-server.nordu.net (8.14.3/8.14.3) with ESMTP id q3BLoZo1021108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Apr 2012 23:50:38 +0200 (CEST)
Message-ID: <4F85FCAB.1010601@sunet.se>
Date: Wed, 11 Apr 2012 23:50:35 +0200
From: Leif Johansson <leifj@sunet.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: david.black@emc.com
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05B2E80811@MX14A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE7120535DC@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120535DC@MX15A.corp.emc.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, ietf@ietf.org, leifj@nordu.net, tim.polk@nist.gov
Subject: Re: [Gen-art] Gen-ART review of draft-johansson-loa-registry-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: Wed, 11 Apr 2012 21:50:47 -0000

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

On 04/11/2012 11:49 PM, david.black@emc.com wrote:
> The -05 version of this draft resolves all of the issues and
> comments raised in the Gen-ART review of the -04 version.

that was quick! thanks

	Leif

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+F/KsACgkQ8Jx8FtbMZnfhbACglsmw8UwPI/90Sc2JGrBEzU0+
yfIAnRdgKK2vCkdEhJhB1HDaO3SU/cqV
=nQXL
-----END PGP SIGNATURE-----

From adam@nostrum.com  Wed Apr 11 15:03:11 2012
Return-Path: <adam@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3D111E80DB; Wed, 11 Apr 2012 15:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.42
X-Spam-Level: 
X-Spam-Status: No, score=-101.42 tagged_above=-999 required=5 tests=[AWL=-1.120, BAYES_00=-2.599, MANGLED_SAVELE=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 ZZg+WKGUIosS; Wed, 11 Apr 2012 15:03:10 -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 4459A11E80CC; Wed, 11 Apr 2012 15:03:07 -0700 (PDT)
Received: from dn3-228.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q3BM34Lj041723 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 11 Apr 2012 17:03:05 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4F85FF98.8000102@nostrum.com>
Date: Wed, 11 Apr 2012 17:03:04 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <CAHBDyN6PN-vp9wXo6fF8G4VfODXjkfbWBaJN8EPopeWfOg9PmQ@mail.gmail.com> <4F840F94.1080703@isode.com>
In-Reply-To: <4F840F94.1080703@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: gen-art@ietf.org, The IESG <iesg@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-sipcore-rfc3265bis-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: Wed, 11 Apr 2012 22:03:11 -0000

On 4/10/12 5:46 AM, Alexey Melnikov wrote:
>
> 3.2.1.  Identification of Reported Events, Event Classes, and Current
>         State
>
>    When present, the body of the NOTIFY request MUST be formatted into
>    one of the body formats specified in the "Accept" header field of the
>    corresponding SUBSCRIBE request.  This body will contain either the
>    state of the subscribed resource or a pointer to such state in the
>    form of a URI (see Section 5.4.13).
>
> Nit: or the default according to the event package definition, if no 
> Accept
> header field was specified.

I've added text to point this case out.

> Also, it might be good to reference RFC 3986 for URIs here.

Given that SIP uses URIs everywhere, I'm not sure what benefit is 
derived by referencing the URI syntax draft here.

> 4.1.1.  Detecting Support for SIP Events
>
>    The extension described in this document does not make use of the use
>    of "Require" or "Proxy-Require" header fields; similarly, there is no
>
> Nit: too many "use of".

Fixed.

> 4.1.3.  Receiving and Processing State Information
>
>    To prevent spoofing of events, NOTIFY requests SHOULD be
>    authenticated, using any defined SIP authentication mechanism.
>
> Minor: How can this SHOULD be satisfied? Any reference which might be 
> appropriate here?

Added: "...such as those described in sections 22.2 and 23 of [RFC3261]."

>
> 4.2.1.3.  Authentication/Authorization of SUBSCRIBE Requests
>
>    SIP authentication mechanisms are discussed in [RFC3261].  Note that,
>    even if the notifier node typically acts as a proxy, authentication
>    for SUBSCRIBE requests will always be performed via a "401" response,
>    not a "407;" notifiers always act as a user agents when accepting
>
> Nit: Is the ";" after "407" a typo?

Thanks -- that should have been outside the quotation marks (and 
probably should be a full stop, which I've changed it to).

>
> 4.4.4.  Allow-Events header field usage
>
>    The "Allow-Events" header field does not include a list of the etvent
>
>  typo: event

I don't find "etvent" in the document:

http://tools.ietf.org/html/draft-ietf-sipcore-rfc3265bis-07#section-4.4.4

Is it possible you accidentally edited a local copy of the file prior to 
your review?

I also don't find this typo in the source (which would surprise me in 
any case, as I made sure to run the -07 version through a spell checker).
>
>    template packages supported by an implementation.  If a subscriber
>    wishes to determine which event template packages are supported by a
>    notifier, it can probe for such support by attempting to subscribe to
>    the event template packages it wishes to use.
>
> Can you clarify how such request would look like? An example would be 
> nice.

I'm not sure what you're asking for here. It would be a SUBSCRIBE 
message, with an "Event" header field set to name the template you want 
to use. Basically it just says "we don't negotiate templates -- just try 
it and see if it fails."

> 5.4.3.  SUBSCRIBE Request Bodies
>
>    It is expected that most, but not all, event packages will define
>    syntax and semantics for SUBSCRIBE request bodies; these bodies will
>    typically modify, expand, filter, throttle, and/or set thresholds for
>    the class of events being requested.  Designers of event packages are
>    strongly encouraged to re-use existing MIME types for message bodies
>    where practical.
>
> Nit: MIME types are now called "media types" in more recent IETF RFCs.

Thanks. Fixed in three places.

> I would recommend pointing to the Media Type Registration Procedure 
> document [RFC 4288] here, which points to the IANA registry.

Done.

>
> 5.4.5.  NOTIFY Request Bodies
>
>    Event packages also MUST define which MIME type is to be assumed if
>    none are specified in the "Accept" header field of the SUBSCRIBE
>    request.
>
> The same nit as above.

Fixed.

>
> 7.2.  Reason Codes
>
>    This document further defines "reason" codes for use in the
>    "Subscription-State" header field (see Section 4.1.3).
>
>    Following the policies outlined in "Guidelines for Writing an IANA
>    Considerations Section in RFCs" [RFC5226], new reason codes require a
>    Standards Action.
>
> Minor: This would prevent registration of new Reason Codes in an 
> Experimental RFC (for example). I would like to double check that that 
> is intentional.

It never came up explicitly during working group discussions, to my memory.

>    Registrations with the IANA include the reason code being registered
>    and a reference to a published document which describes the event
>    package.  Insertion of such values takes place as part of the RFC
>    publication process or as the result of inter-SDO liaison activity.
>
> I don't think Standards Action allows for "inter-SDO liaison 
> activity", unless such documents from other SDOs are published as 
> Standard Track RFCs. So I find your text confusing: either your 
> registration procedure should also allow for direct IESG approvals (to 
> allow registrations from other SDOs with no RFCs), or you should 
> remove "as the result of inter-SDO liaison activity".

You're right. I suspect we really intended to make this registrable by 
external SDOs, meaning we probably really wanted Specification Required. 
I'm leaving this as-is for now, and will need to coordinate with our AD 
to iron out where to go with this.

> 8.4.  Augmented BNF Definitions
>
>    event-type        =  event-package *( "." event-template )
>
> Minor: Does this mean that multiple template packages can be applied?
> Is there any ordering for them?
Yes, and yes.
> How would "foo.A.B" differ from "foo.B.A"?

Right now, we have only one template defined -- but imagine that we did 
define a new "list" template event package (we almost did this some 
years ago) which is used to aggregate several resources into a single 
subscription.

"Event: presence.winfo.list" would subscribe to the aggregation of 
several watcher-info documents into a single list.

"Event: presence.list.winfo" would subscribe to the watcher-info state 
of the indicated list.

> Nit: id-nits complains:
>
>   -- Duplicate reference: RFC4660, mentioned in 'RFC4660', was also 
> mentioned
>      in 'RFC 4660'.
>
> "[RFC 4660]" reference is used in section 7.2.

id-nits is wrong. It incorrectly thinks that the paragraph starting with 
[RFC4660] on page 40 is trying to define a reference.

/a

From ron.even.tlv@gmail.com  Wed Apr 11 15:16:01 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 5CCD711E80A4; Wed, 11 Apr 2012 15:16:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.436
X-Spam-Level: 
X-Spam-Status: No, score=-3.436 tagged_above=-999 required=5 tests=[AWL=0.162,  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 kFIbawMcITRb; Wed, 11 Apr 2012 15:16:00 -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 5045D11E8073; Wed, 11 Apr 2012 15:15:59 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so920355wgb.13 for <multiple recipients>; Wed, 11 Apr 2012 15:15:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=8moXx4gUplrUcCw9cbjXZ+0yz202N2vGHQxojCSdw6o=; b=O7HZDakhcVyABd5vRi6Ll3LbVGWWQKbQQPLxZYy+fa3l954MqcWgjLLZksMEtsWF6M Eq7zdwyWPt60ktyV1xsPtBUjsppzv8F2iY9cxIeMc2HCgYlzQjOrQtdfmMBss05eq1zn 78w9cZPvNejv8GzJxPmAqT1iMB6WDfwpKU20vuu1OILaMgWHGEUab0gkmlvtHg8DdfrG q+JEVBGWrUK0DxaTUs2HrvCVFigdpCCO9RY9wh2aZWqRQ6OaX0O82ldR5+/jsEKQ7YvG TiQdikhL3XLRRK5elHikmRSyIMuWyiWwZ+/Jt9V3dGA8j89H9G71Pa9zGZf7ZNhoS8x6 SR2g==
Received: by 10.180.91.168 with SMTP id cf8mr343613wib.0.1334182558258; Wed, 11 Apr 2012 15:15:58 -0700 (PDT)
Received: from windows8d787f9 ([109.65.204.117]) by mx.google.com with ESMTPS id o2sm14215432wiv.11.2012.04.11.15.15.54 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 Apr 2012 15:15:55 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Bitar, Nabil N'" <nabil.n.bitar@verizon.com>, <draft-ietf-ancp-pon.all@tools.ietf.org>
References: <4f7875ec.6965b40a.3e21.5e69@mx.google.com> <CBAB592E.25BBC%nabil.n.bitar@verizon.com>
In-Reply-To: <CBAB592E.25BBC%nabil.n.bitar@verizon.com>
Date: Thu, 12 Apr 2012 01:14:30 +0300
Message-ID: <4f86029b.e249b40a.6b94.4aa7@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004D_01CD1849.9E6B3E00"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac0YHu+pZKCam1sKTTW3ItioRETerAAEXnOg
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-ancp-pon-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2012 22:16:01 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_004D_01CD1849.9E6B3E00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Nabil,

I am OK with your proposed text

Roni

 

From: Bitar, Nabil N [mailto:nabil.n.bitar@verizon.com] 
Sent: Wednesday, April 11, 2012 11:09 PM
To: Roni Even; draft-ietf-ancp-pon.all@tools.ietf.org
Cc: gen-art@ietf.org; 'IETF'
Subject: Re: Gen-ART LC review of draft-ietf-ancp-pon-02

 

Hi,

Thanks for the comments. Please see inline.

 

Thanks,

Nabil

 

From: Roni Even <ron.even.tlv@gmail.com>
Date: Sun, 1 Apr 2012 11:34:54 -0400
To: "draft-ietf-ancp-pon.all@tools.ietf.org"
<draft-ietf-ancp-pon.all@tools.ietf.org>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, 'IETF' <ietf@ietf.org>
Subject: Gen-ART LC review of draft-ietf-ancp-pon-02

 

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

Sorry for the late review due to IET meeting.

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

 

Document: draft-ietf-ancp-pon-02

Reviewer: Roni Even

Review Date:2012-4-1

IETF LC End Date: 2012-3-30

IESG Telechat date:

 

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

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

In section 4 "However, the broadcast capability on the PON enables the AN
(OLT) to send one copy on the PON as opposed to N  copies of a multicast
channel on the PON serving N premises being  receivers" I think the "being"
before the last word should be deleted

 

<NB> are you OK saying: "However, the broadcast capability on the PON
enables the AN (OLT) to send one copy on the PON as opposed to one copy to
each receiver on the PON 

 

General editorial comment is about page breaks which can be better like
section 7 title is at the end of a page and the text is in the next page.
Also some of the figures and their descriptions are split between pages.

<NB> will address that.

 


------=_NextPart_000_004D_01CD1849.9E6B3E00
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 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></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><span =
style=3D'color:#1F497D'>Hi Nabil,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I am OK with your =
proposed text<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Bitar, Nabil N [mailto:nabil.n.bitar@verizon.com] <br><b>Sent:</b> =
Wednesday, April 11, 2012 11:09 PM<br><b>To:</b> Roni Even; =
draft-ietf-ancp-pon.all@tools.ietf.org<br><b>Cc:</b> gen-art@ietf.org; =
'IETF'<br><b>Subject:</b> Re: Gen-ART LC review of =
draft-ietf-ancp-pon-02<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'>Hi,<o:p></o:p></s=
pan></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'>Thanks for the =
comments. Please see inline.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'>Thanks,<o:p></o:p=
></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'>Nabil<o:p></o:p><=
/span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'color:black'>From: </span></b><span style=3D'color:black'>Roni =
Even &lt;<a =
href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>&gt;<br>=
<b>Date: </b>Sun, 1 Apr 2012 11:34:54 -0400<br><b>To: </b>&quot;<a =
href=3D"mailto:draft-ietf-ancp-pon.all@tools.ietf.org">draft-ietf-ancp-po=
n.all@tools.ietf.org</a>&quot; &lt;<a =
href=3D"mailto:draft-ietf-ancp-pon.all@tools.ietf.org">draft-ietf-ancp-po=
n.all@tools.ietf.org</a>&gt;<br><b>Cc: </b>&quot;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;, 'IETF' &lt;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br><b>Subject: =
</b>Gen-ART LC review of =
draft-ietf-ancp-pon-02<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div><div><p class=3DMsoNormal><span =
style=3D'color:black'>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 =
style=3D'color:black'>Sorry for the late review due to IET =
meeting.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:black'>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>&nbsp;</span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DFR =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>Document: draft-ietf-ancp-pon-02</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>Reviewer: Roni Even</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>Review Date:2012&#8211;4&#8211;1</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>IETF LC End Date: 2012&#8211;3&#8211;30</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>IESG Telechat date:</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>&nbsp;</span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>Summary: This draft is ready for publication as an Informational =
RFC.</span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>&nbsp;</span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>Major issues:</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>&nbsp;</span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>Minor issues:</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>&nbsp;</span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>Nits/editorial comments:</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>&nbsp;</span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>In section 4 &#8221;However, the broadcast capability on the PON =
enables the AN (OLT) to send one copy on the PON as opposed to N&nbsp; =
copies of a multicast channel on the PON serving N premises being&nbsp; =
receivers&#8221; I think the &#8220;being&#8221; before the last word =
should be deleted</span><span =
style=3D'color:black'><o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.5pt;color:black'>&lt;NB&gt; are you OK saying: =
&quot;</span><span class=3Dapple-style-span><span =
style=3D'font-size:11.5pt;color:black'>However, the broadcast capability =
on the PON enables the AN (OLT) to send one copy on the PON as opposed =
to one copy to each receiver on the PON&nbsp;</span></span><span =
style=3D'font-size:10.5pt;color:black'><o:p></o:p></span></p></div><div><=
div><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>&nbsp;</span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>General editorial comment is about page breaks which can be better like =
section 7 title is at the end of a page and the text is in the next =
page. Also some of the figures and their descriptions are split between =
pages.</span><span =
style=3D'color:black'><o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.5pt;color:black'>&lt;NB&gt; will address =
that.<o:p></o:p></span></p></div><div><div><p class=3DMsoNormal><span =
dir=3DRTL></span><span lang=3DHE dir=3DRTL =
style=3D'font-family:"Arial","sans-serif";color:black'><span =
dir=3DRTL></span>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p></div></div></div></div></bod=
y></html>
------=_NextPart_000_004D_01CD1849.9E6B3E00--


From turners@ieca.com  Wed Apr 11 16:42:12 2012
Return-Path: <turners@ieca.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC4DF21F8554 for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 16:42:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.665
X-Spam-Level: 
X-Spam-Status: No, score=-102.665 tagged_above=-999 required=5 tests=[AWL=-0.400, 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 qLxKKFQqYE-z for <gen-art@ietfa.amsl.com>; Wed, 11 Apr 2012 16:42:12 -0700 (PDT)
Received: from gateway13.websitewelcome.com (gateway13.websitewelcome.com [67.18.21.4]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5A421F854F for <gen-art@ietf.org>; Wed, 11 Apr 2012 16:42:12 -0700 (PDT)
Received: by gateway13.websitewelcome.com (Postfix, from userid 5007) id B74B4321EB2FE; Wed, 11 Apr 2012 18:42:11 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway13.websitewelcome.com (Postfix) with ESMTP id A9C1A321EB2D1 for <gen-art@ietf.org>; Wed, 11 Apr 2012 18:42:11 -0500 (CDT)
Received: from [71.191.3.52] (port=33351 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1SI7Aw-0007HK-RI; Wed, 11 Apr 2012 18:42:11 -0500
Message-ID: <4F8616D1.2080003@ieca.com>
Date: Wed, 11 Apr 2012 19:42:09 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Mike Jones <Michael.Jones@microsoft.com>
References: <4E1F6AAD24975D4BA5B16804296739436646237B@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436646237B@TK5EX14MBXC283.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-3-52.washdc.east.verizon.net (thunderfish.local) [71.191.3.52]:33351
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 7
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: General Area Review Team <gen-art@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-18.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, 11 Apr 2012 23:42:13 -0000

On issue 2, Russ has already entered his ballot on the base spec so I'll 
pick this one up.

spt

On 4/10/12 8:25 PM, Mike Jones wrote:
> Hi Alexey,
>
> About your issue 1:  The OAuth Core spec, where "scope" is primarily defined, includes the sentence "The [scope] strings are defined by the authorization server" (see http://tools.ietf.org/html/draft-ietf-oauth-v2-25#section-3.3).  I could add that clarification to the Bearer spec as well to make it clear that the scope values are context-dependent, if that would address your concern.
>
> About your issue 2:  Investigating the OAuth Errors Registry a bit further (see http://tools.ietf.org/html/draft-ietf-oauth-v2-25#section-11.4.1) while I'd like to be able to register the OAuth Bearer errors in this registry, what I believe to be a defect in the errors registry text currently prevents this.  Specifically, the registry enumerates only three "Error usage location" values:  authorization code grant error response, implicit grant error response, and token error response.  To be able to use this registry, it would also have to have a fourth usage location:  "resource access error response".  If you'd like to file an issue against the OAuth Core spec to get this additional usage location added to the registry, then I'd be glad to use it.  I believe that this would be significantly preferable to adding a separate OAuth Bearer errors registry that's exactly like the general-purpose one, only separate from it.
>
> 				Best wishes,
> 				-- Mike
>
> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of Alexey Melnikov
> Sent: Tuesday, April 10, 2012 7:03 AM
> To: draft-ietf-oauth-v2-bearer.all@tools.ietf.org
> Cc: General Area Review Team; oauth@ietf.org; The IESG
> Subject: [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-18.txt
>
> I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments you may receive.
> Document: draft-ietf-oauth-v2-bearer-18.txt
> Reviewer: Alexey Melnikov
> Review Date: 10 April 2012
> IETF LC End Date: 7 Feb 2012
> IESG Telechat date: 12 April 2012
>
> Summary: Nearly ready to be published as Proposed Standard, with a couple of things that should be addressed or at least discussed.
>
> Thank you for addressing most of my other issues. However there are a couple remaining which I think are important.
>
> Major Issues:
>
> 1).
>      The "scope" attribute is a space-delimited list of scope values
>      indicating the required scope of the access token for accessing the
>      requested resource.  In some cases, the "scope" value will be used
>      when requesting a new access token with sufficient scope of access to
>      utilize the protected resource.  The "scope" attribute MUST NOT
>      appear more than once.  The "scope" value is intended for
>      programmatic use and is not meant to be displayed to end users.
>
> I don't think this provide enough information about what this is, how it is to be used and which values are allowed. As this is not meant to be displayed to end users, then you need to say what values are allowed and which entity can allocate them. Is there a registry for these tokens, e.g. an IANA registry?
>
> The editor provided explanation in email, however this was not reflected in any version of the draft.
>
> 2). Section "3.1.  Error Codes"
>
> I've suggested to use an IANA registry for this field. Apparently there is already a registry created by<http://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-11.4>.
> However this document doesn't register values defined in section 3.1 with IANA and doesn't point to draft-ietf-oauth-v2-23 for the registry.
> I find this to be very confusing.
>
> Minor issues: none
>
> Nits: none
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>
>

From eran@hueniverse.com  Wed Apr 11 20:44:41 2012
Return-Path: <eran@hueniverse.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 B661211E80B2; Wed, 11 Apr 2012 20:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 92pMGC7quluw; Wed, 11 Apr 2012 20:44:40 -0700 (PDT)
Received: from p3plex2out01.prod.phx3.secureserver.net (p3plex2out01.prod.phx3.secureserver.net [184.168.131.12]) by ietfa.amsl.com (Postfix) with ESMTP id B336011E80A6; Wed, 11 Apr 2012 20:44:40 -0700 (PDT)
Received: from P3PWEX2HT003.ex2.secureserver.net ([184.168.131.11]) by p3plex2out01.prod.phx3.secureserver.net with bizsmtp id wrkf1i0010EuLVk01rkf8V; Wed, 11 Apr 2012 20:44:39 -0700
Received: from P3PWEX2MB008.ex2.secureserver.net ([169.254.8.115]) by P3PWEX2HT003.ex2.secureserver.net ([184.168.131.11]) with mapi id 14.02.0247.003; Wed, 11 Apr 2012 20:44:39 -0700
From: Eran Hammer <eran@hueniverse.com>
To: Sean Turner <turners@ieca.com>
Thread-Topic: [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-18.txt
Thread-Index: AQHNGDy+7gVTWsO88kiAN2vkgbM5PZaW912A
Date: Thu, 12 Apr 2012 03:44:38 +0000
Message-ID: <D5321BE6-806D-4EF1-A2DF-EA4284B29B95@hueniverse.com>
References: <4E1F6AAD24975D4BA5B16804296739436646237B@TK5EX14MBXC283.redmond.corp.microsoft.com> <4F8616D1.2080003@ieca.com>
In-Reply-To: <4F8616D1.2080003@ieca.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9E1239C5316E6544A94A3AF1737CF0CD@53553.exhost2.secureserver.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: The IESG <iesg@ietf.org>, Mike Jones <Michael.Jones@microsoft.com>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [Gen-art] [OAUTH-WG] Gen-ART Telechat review of	draft-ietf-oauth-v2-bearer-18.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, 12 Apr 2012 03:44:41 -0000

Issue 2 received extensive WG discussion.

At the core of it was the question of how the IETF should handle HTTP authe=
ntication error codes. We consults with the HTTPbis WG and consensus was th=
at at this point we do not want to create a general purpose error registry =
for HTTP authentication schemes. In fact, Bearer is the exception using spe=
cial error codes which could (and should) just use HTTP 4xx code.=20

While bearer is closely linked to OAuth, it is still a standalone scheme. T=
here was no consensus that other schemes (even the OAuth related MAC scheme=
) will sign into such a registry.=20

In short, the OAuth error registry is not an appropriate venue for the bear=
er error codes. It is unfortunate that Mr. Jones failed to represent the WG=
 consensus on this issue in his response to the IESG.=20

EH

On Apr 11, 2012, at 19:42, "Sean Turner" <turners@ieca.com> wrote:

> On issue 2, Russ has already entered his ballot on the base spec so I'll =
pick this one up.
>=20
> spt
>=20
> On 4/10/12 8:25 PM, Mike Jones wrote:
>> Hi Alexey,
>>=20
>> About your issue 1:  The OAuth Core spec, where "scope" is primarily def=
ined, includes the sentence "The [scope] strings are defined by the authori=
zation server" (see http://tools.ietf.org/html/draft-ietf-oauth-v2-25#secti=
on-3.3).  I could add that clarification to the Bearer spec as well to make=
 it clear that the scope values are context-dependent, if that would addres=
s your concern.
>>=20
>> About your issue 2:  Investigating the OAuth Errors Registry a bit furth=
er (see http://tools.ietf.org/html/draft-ietf-oauth-v2-25#section-11.4.1) w=
hile I'd like to be able to register the OAuth Bearer errors in this regist=
ry, what I believe to be a defect in the errors registry text currently pre=
vents this.  Specifically, the registry enumerates only three "Error usage =
location" values:  authorization code grant error response, implicit grant =
error response, and token error response.  To be able to use this registry,=
 it would also have to have a fourth usage location:  "resource access erro=
r response".  If you'd like to file an issue against the OAuth Core spec to=
 get this additional usage location added to the registry, then I'd be glad=
 to use it.  I believe that this would be significantly preferable to addin=
g a separate OAuth Bearer errors registry that's exactly like the general-p=
urpose one, only separate from it.
>>=20
>>                Best wishes,
>>                -- Mike
>>=20
>> -----Original Message-----
>> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf O=
f Alexey Melnikov
>> Sent: Tuesday, April 10, 2012 7:03 AM
>> To: draft-ietf-oauth-v2-bearer.all@tools.ietf.org
>> Cc: General Area Review Team; oauth@ietf.org; The IESG
>> Subject: [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-beare=
r-18.txt
>>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on Gen=
-ART, please see the FAQ at<http://wiki.tools.ietf.org/area/gen/trac/wiki/G=
enArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments yo=
u may receive.
>> Document: draft-ietf-oauth-v2-bearer-18.txt
>> Reviewer: Alexey Melnikov
>> Review Date: 10 April 2012
>> IETF LC End Date: 7 Feb 2012
>> IESG Telechat date: 12 April 2012
>>=20
>> Summary: Nearly ready to be published as Proposed Standard, with a coupl=
e of things that should be addressed or at least discussed.
>>=20
>> Thank you for addressing most of my other issues. However there are a co=
uple remaining which I think are important.
>>=20
>> Major Issues:
>>=20
>> 1).
>>     The "scope" attribute is a space-delimited list of scope values
>>     indicating the required scope of the access token for accessing the
>>     requested resource.  In some cases, the "scope" value will be used
>>     when requesting a new access token with sufficient scope of access t=
o
>>     utilize the protected resource.  The "scope" attribute MUST NOT
>>     appear more than once.  The "scope" value is intended for
>>     programmatic use and is not meant to be displayed to end users.
>>=20
>> I don't think this provide enough information about what this is, how it=
 is to be used and which values are allowed. As this is not meant to be dis=
played to end users, then you need to say what values are allowed and which=
 entity can allocate them. Is there a registry for these tokens, e.g. an IA=
NA registry?
>>=20
>> The editor provided explanation in email, however this was not reflected=
 in any version of the draft.
>>=20
>> 2). Section "3.1.  Error Codes"
>>=20
>> I've suggested to use an IANA registry for this field. Apparently there =
is already a registry created by<http://tools.ietf.org/html/draft-ietf-oaut=
h-v2-23#section-11.4>.
>> However this document doesn't register values defined in section 3.1 wit=
h IANA and doesn't point to draft-ietf-oauth-v2-23 for the registry.
>> I find this to be very confusing.
>>=20
>> Minor issues: none
>>=20
>> Nits: none
>>=20
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>=20
>>=20
>>=20
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

From julian.reschke@gmx.de  Thu Apr 12 01:54:37 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4492C21F8664 for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 01:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.897
X-Spam-Level: 
X-Spam-Status: No, score=-103.897 tagged_above=-999 required=5 tests=[AWL=-1.297, 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 vFR9XZw14cm1 for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 01:54:36 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 4556621F865D for <gen-art@ietf.org>; Thu, 12 Apr 2012 01:54:36 -0700 (PDT)
Received: (qmail invoked by alias); 12 Apr 2012 08:54:35 -0000
Received: from p57A6EA96.dip.t-dialin.net (EHLO [192.168.178.36]) [87.166.234.150] by mail.gmx.net (mp036) with SMTP; 12 Apr 2012 10:54:35 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+jjXw75uijlbuoBXu+sASyCksWPaiMYWSlxOSlFH dW3jrdQkFsDo3a
Message-ID: <4F869849.1060508@gmx.de>
Date: Thu, 12 Apr 2012 10:54:33 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Eran Hammer <eran@hueniverse.com>
References: <4E1F6AAD24975D4BA5B16804296739436646237B@TK5EX14MBXC283.redmond.corp.microsoft.com> <4F8616D1.2080003@ieca.com> <D5321BE6-806D-4EF1-A2DF-EA4284B29B95@hueniverse.com>
In-Reply-To: <D5321BE6-806D-4EF1-A2DF-EA4284B29B95@hueniverse.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [Gen-art] [OAUTH-WG] Gen-ART Telechat review of	draft-ietf-oauth-v2-bearer-18.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, 12 Apr 2012 08:54:37 -0000

Citing from Sean's dicuss 
(<https://datatracker.ietf.org/doc/draft-ietf-oauth-v2-bearer/ballot/#sean-turner>):

> 1) I'm hoping the answer to this one is "there's no problem" but I gotta ask and
> maybe the APPs ADs can confirm:  Is there any issue with this specification
> using ABNF from [I-D.ietf-httpbis-p1-messaging] while OAUTH 2.0 uses [RFC5234]?

The ABNF from HTTPbis is a superset of RFC 5234 in that it defines a 
list rule for readability. I don't think that this rule is used anymore 
in the bearer spec, so it can just say it's using RFC 5234.

Best regards, Julian

From bill.wu@huawei.com  Thu Apr 12 02:06:23 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 A1D5021F869E for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 02:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.227
X-Spam-Level: 
X-Spam-Status: No, score=0.227 tagged_above=-999 required=5 tests=[AWL=-1.327,  BAYES_00=-2.599, J_CHICKENPOX_36=0.6, J_CHICKENPOX_41=0.6, J_CHICKENPOX_43=0.6, J_CHICKENPOX_66=0.6, MIME_BASE64_TEXT=1.753]
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 4mX56zPor245 for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 02:06:23 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id E882021F869A for <gen-art@ietf.org>; Thu, 12 Apr 2012 02:06:22 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFD82603; Thu, 12 Apr 2012 05:06:22 -0400 (EDT)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Apr 2012 02:03:22 -0700
Received: from SZXEML409-HUB.china.huawei.com (10.82.67.136) by dfweml403-hub.china.huawei.com (10.193.5.151) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Apr 2012 02:02:52 -0700
Received: from w53375 (10.138.41.149) by szxeml409-hub.china.huawei.com (10.82.67.136) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Apr 2012 17:03:22 +0800
Message-ID: <112421EADFC943FEA74836FF9F72F81F@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, <gen-art@ietf.org>
References: <201204111542.q3BFgFsG061765@givry.fdupont.fr>
Date: Thu, 12 Apr 2012 17:03:21 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
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: draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-avtcore-feedback-supression-rtp-16.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, 12 Apr 2012 09:06:23 -0000

SGksRnJhbmNpczoNClRoYW5rIHlvdSBmb3IgY2FyZWZ1bCBhbmQgdmFsdWFibGUgcmV2aWV3LnBs
ZWFzZSBzZWUgbXkgcmVwbGllcyBiZWxvdyBpbmxpbmUuDQoNClJlZ2FyZHMhDQotUWluDQotLS0t
LSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkZyYW5jaXMgRHVwb250IiA8RnJhbmNp
cy5EdXBvbnRAZmR1cG9udC5mcj4NClRvOiA8Z2VuLWFydEBpZXRmLm9yZz4NCkNjOiA8ZHJhZnQt
aWV0Zi1hdnRjb3JlLWZlZWRiYWNrLXN1cHJlc3Npb24tcnRwLmFsbEB0b29scy5pZXRmLm9yZz4N
ClNlbnQ6IFdlZG5lc2RheSwgQXByaWwgMTEsIDIwMTIgMTE6NDIgUE0NClN1YmplY3Q6IHJldmll
dyBvZiBkcmFmdC1pZXRmLWF2dGNvcmUtZmVlZGJhY2stc3VwcmVzc2lvbi1ydHAtMTYudHh0DQoN
Cg0KPkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZv
ciBiYWNrZ3JvdW5kIG9uDQo+IEdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPiA8IGh0
dHA6Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
PiANCj4gUGxlYXNlIHdhaXQgZm9yIGRpcmVjdGlvbiBmcm9tIHlvdXIgZG9jdW1lbnQgc2hlcGhl
cmQNCj4gb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQo+
IA0KPiBEb2N1bWVudDogZHJhZnQtaWV0Zi1hdnRjb3JlLWZlZWRiYWNrLXN1cHJlc3Npb24tMTYu
dHh0DQo+IFJldmlld2VyOiBGcmFuY2lzIER1cG9udA0KPiBSZXZpZXcgRGF0ZTogMjAxMjAzMjMN
Cj4gSUVURiBMQyBFbmQgRGF0ZTogMjAxMjAzMjYNCj4gSUVTRyBUZWxlY2hhdCBkYXRlOiAyMDEy
MDQxMg0KPiANCj4gU3VtbWFyeTogUmVhZHkNCj4gDQo+IE1ham9yIGlzc3VlczogTm9uZQ0KPiAN
Cj4gTWlub3IgaXNzdWVzOiBOb25lDQo+IA0KPiBOaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCj4g
DQo+IFRoZXNlIGFyZSBhYm91dCB0aGUgLTE1IHZlcnNpb24gdXBkYXRlZCB0byAtMTYNCj4gDQo+
IC0gSS1EIG5hbWU6IHN1cHJlc3Npb24gLT4gc3VwcHJlc3Npb24NCg0KW1Fpbl06IEFncmVlLCBi
dXQgSSBhc3N1bWUgSSBhbSBub3QgYWxsb3dlZCB0byBjaGFuZ2UgSS1EIG5hbWUgYXQgdGhpcyBz
dGFnZSw6LSkuDQoNCg0KPiAtIEFic3RyYWN0IHBhZ2UgMTogaW1wbG9zaW9uIC0+IGV4cGxvc2lv
biAodGhpbmdzIHdoaWNoIGNhbiBpbXBsb2RlIGFyZSByYXJlIDotKQ0KDQpbUWluXTogUkZDNDU4
OCByZWZlcmVuY2VkIGJ5IHRoaXMgZG9jdW1lbnQgaXMgdXNpbmcgImltcGxvc2lvbiIuIFNvIEkg
dGhpbmsgaXQgc2hvdWxkDQpiZSBmaW5lIHRvIHVzZSB0aGUgc2FtZSB0ZXJtIGluIHRoaXMgZG9j
dW1lbnQuOi0pDQogDQo+IC0gQWJzdHJhY3QgcGFnZSAxOiBzaWduYWxsaW5nIC0+IHNpZ25hbGlu
Zw0KDQpbUWluXTogT2theS4NCj4gDQo+IC0gVG9jIHBhZ2UgMiBhbmQgOSBwYWdlIDEyOiBBY2tu
b3dsZWRnZW1lbnQgLT4gQWNrbm93bGVkZ21lbnQNCg0KW1Fpbl06IE9rYXkuDQo+IA0KPiAtIElu
dHJvZHVjdGlvbiBwYWdlIDQ6IFJUQ1AgaXMgbm90IGEgd2VsbCBrbm93biBhYmJyZXY6IGFzIGl0
IGlzIGZpcnN0IHlvdSBoYXZlDQo+IHRvIGludHJvZHVjZSBpdC4NCg0KW1Fpbl1Pa2F5IGFuZCB3
aWxsIGV4cGFuZCB0aGlzIGFiYnJldi4NCg0KPiANCj4gLSBJbnRyb2R1Y3Rpb24gcGFnZSA0OiBz
YW1lIGZvciBTU006IHBsZWFzZSBpbnRyb2R1Y2UgdGhlIGFiYnJldg0KDQpbUWluXTogSSBoYXZl
IGludHJvZHVjZWQgdGhpcyBhYmJyZXYgaW4gdGhlIGdsb3NzYXJ5IHNlY3Rpb24oaS5lLiwgc2Vj
dGlvbiAyLjEpLg0KPiANCj4gLSBJbnRyb2R1Y3Rpb24gcGFnZSA0OiBpbXBsb3Npb24gLT4gZXhw
bG9zaW9uDQoNCltRaW5dOiBTZWUgYWJvdmUuDQoNCj4gLSBJbnRyb2R1Y3Rpb24gcGFnZSA0IGFu
ZCBvdGhlciBwbGFjZXM6IGUuZy4gLT4gZS5nLiwNCg0KW1Fpbl06IE9rYXkuDQo+IA0KPiAtIDMg
cGFnZSA2OiAsd2hpY2ggLT4gLCB3aGljaA0KDQpbUWluXTogT2theS4NCj4gDQo+IC0gNCBwYWdl
IDY6IG1pc3NpbmcgY2hhcmFjdGVycy93b3JkcyBpbiAidGhlIFBULCBGTVQsbGVuZ3RoIFNTUkMi
DQoNCltRaW5dOiBZZXMsIG1pc3NpbmcgYSBjb21tYSBiZXR3ZWVuICJsZW5ndGgiIGFuZCAiU1NS
QyIuDQo+IA0KPiAtIDQuMSBwYWdlIDc6IGFsbCBjYXBzIGluICJ0cmFuc3BvcnQgbGF5ZXIgdGhp
cmQtcGFydHkgbG9zcyINCg0KW1Fpbl06IE9rYXkuDQo+IA0KPiAtIDQuMiBwYWdlIDc6IGlmIHRo
ZSBTU1JDIGlzIGFuIElQdjQgYWRkcmVzcyB0aGUgInNldCB0byAwIiBpcyBub3QgdmVyeSBjb3Jy
ZWN0Lg0KDQpbUWluXSBJZiBTU1JDIGlzIG5vdCB1c2VkLCBpdCBzaG91bGQgYmUgc2V0IHRvIDAu
IA0KUkZDNTEwNCBhbHNvIHVzZSB0aGlzIHJ1bGUuIFNvIHdlIGZvbGxvdyB0aGlzLg0KT24gdGhl
IG90aGVyIGhhbmQgaWYgdGhlIFNTUkMgaXMgYW4gSVB2NCBhZGRyZXNzLCBJUHY0IGFkZHJlc3Mg
TVVTVCBub3QgYmUgc2V0IHRvDQowIHNpbmNlIDAgaGFzIGFscmVhZHkgYmUgcmVzZXJ2ZWQgZm9y
IHRoZSBvdGhlciB1c2UgbWVudGlvbmVkIGFib3ZlLiANCkFsc28gaXQgaXMgZWFzeSB0byBjYXVz
ZSBTU1JDIGNvbGxpc2lvbiBpZiBJUHY0IGFkZHJlc3MgY2FuIGJlIGNob29zZSBhcyAwLjAuMC4w
IHdoaWNoIGlzIGJyb2FkY2FzdCBhZGRyZXNzLg0KDQo+IA0KPiAtIDQuMiBwYWdlIDc6IG1lZGlh
IFNvdXJjZSAtPiBtZWRpYSBzb3VyY2UNCg0KW1Fpbl06IE9rYXkuDQo+IA0KPiAtIDQuMiBwYWdl
IDg6IDozMiAtPiA6IDMyDQoNCltRaW5dOiBPa2F5Lg0KPiANCj4gLSA2LjEgcGFnZSA5OiBzb3Vy
Y2UtIHNwZWNpZmljIC0+IHNvdXJjZS1zcGVjaWZpYw0KDQpbUWluXTogT2theS4NCg0KPiANCj4g
LSA2LjEgcGFnZSA5OiByZWFzb24oIC0+IHJlYXNvbiAoICYgYSBSVENQIC0+IGFuIFJUQ1AgJiBO
QUNLKWFuZCAtPiBOQUNLKSBhbmQNCg0KW1Fpbl06IE9rYXkuDQoNCj4gDQo+IC0gNi4yIHBhZ2Ug
MTA6IFNvdXJjZXMoQlJTKSAtPiBTb3VyY2VzIChCUlMpDQoNCltRaW5dOiBPa2F5Lg0KDQo+IA0K
PiAtIDYuMiBwYWdlIDEwOiBhIFJUQ1AgLT4gYW4gUlRDUA0KDQpbUWluXTogT2theS4NCg0KPiAN
Cj4gLSA2LjQgcGFnZSAxMDogcmVjZWl2ZXJzLiBlLmcuLCAtPiByZWNlaXZlcnM6IGUuZy4sDQoN
CltRaW5dOiBPa2F5Lg0KDQo+IA0KPiAtIDYuNCBwYWdlIDEwOiBhIFJUQ1AgLT4gYW4gUlRDUA0K
PiANCg0KW1Fpbl06IE9rYXkuDQoNCj4gLSA2LjUgcGFnZSAxMTogYSBSVENQIC0+IGFuIFJUQ1Ag
KHdpdGggYSBsaW5lIGJyZWFrIGluIHRoZSBtaWRkbGUgOi0pDQoNCltRaW5dOiBPa2F5LDotKS4N
Cg0KPiANCj4gLSA3IHBhZ2UgMTE6IHN1cHJlc3Npb24gLT4gc3VwcHJlc3Npb24NCg0KW1Fpbl06
IE9rYXkuDQoNCj4gDQo+IC0gOSBwYWdlIDEyOiBBY2tub3dsZWRnZW1lbnQgLT4gQWNrbm93bGVk
Z21lbnQsIFZBTiBDQUVORUdFTSAtPiB2YW4gQ2FlbmVnZW0sDQo+ICBKb2hhbnNzb24gUyAtPiBK
b2hhbnNzb24NCg0KW1Fpbl06IE9rYXkuDQoNCj4gDQo+IC0gMTAuMiBwYWdlIDE0OiBwbGVhc2Ug
Z2l2ZSB0aGUgbmFtZXMgb2YgSS1Ecw0KDQpbUWluXTogT2theS4NCg0KPiANCj4gLSBBcHBlbmRp
eCBBIHBhZ2UgMTQ6IHVzdWFsbHkgdGhlIGNoYW5nZSBsb2cgaXMgaW4gdGhlIHJldmVyc2Ugb3Jk
ZXIgKD8pDQoNCltRaW5dOiBPa2F5LEkgY2FuIGNoYW5nZSB0aGF0IGJhc2VkIG9uIHlvdXIgc3Vn
Z2VzdGlvbi4NCg0KPiANCj4gLSBBLjggcGFnZSAxNjogLFNlY3VyaXR5IC0+ICwgU2VjdXJpdHkN
Cg0KW1Fpbl06IE9rYXkuDQoNCj4gDQo+IC0gQS4xNCBwYWdlIDE3OiByZWZlcmVjZXMgLT4gcmVm
ZXJlbmNlcw0KDQpbUWluXTogT2theS4NCg0KPiANCj4gUmVnYXJkcw0KPiANCj4gRnJhbmNpcy5E
dXBvbnRAZmR1cG9udC5mcg==


From alexey.melnikov@isode.com  Thu Apr 12 04:21:43 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 4A20021F85D2; Thu, 12 Apr 2012 04:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.377
X-Spam-Level: 
X-Spam-Status: No, score=-102.377 tagged_above=-999 required=5 tests=[AWL=0.222, 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 foCJl+6xzN2V; Thu, 12 Apr 2012 04:21:41 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id F10E921F85D1; Thu, 12 Apr 2012 04:21:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1334229699; d=isode.com; s=selector; i=@isode.com; bh=S7YOLNgfjxY2v/2AcHrHUWHnO5Cu9VZ/AvAY08aBh2A=; 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=B+gKdxnkQ0KKmNs8b8c3aAkqSKmwgrE3kAq+h+S5+YVL95xEdDsfMxY2bSBjKMWpBu7fOF kjm4pfgnAntnFFk76mkSbS2R2UgPgJYACt5KmMln+hdwHMJSAH9bdfMm6p661xjT7oD4xn ENerZ3Riu4gwbP9LragMqw0zg/p62VE=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T4a6wQAg26kV@rufus.isode.com>; Thu, 12 Apr 2012 12:21:39 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F86BAE9.4000406@isode.com>
Date: Thu, 12 Apr 2012 12:22:17 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Mike Jones <Michael.Jones@microsoft.com>
References: <4E1F6AAD24975D4BA5B16804296739436646237B@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436646237B@TK5EX14MBXC283.redmond.corp.microsoft.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>, "oauth@ietf.org" <oauth@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [Gen-art] [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-18.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, 12 Apr 2012 11:21:44 -0000

On 11/04/2012 01:25, Mike Jones wrote:
> Hi Alexey,
Hi Mike,
I've dropped issue 2, Sean took charge of discussing it with IESG.
> About your issue 1:  The OAuth Core spec, where "scope" is primarily defined, includes the sentence "The [scope] strings are defined by the authorization server" (see http://tools.ietf.org/html/draft-ietf-oauth-v2-25#section-3.3).  I could add that clarification to the Bearer spec as well to make it clear that the scope values are context-dependent, if that would address your concern.
Yes, but only partially. I would also like to see a clear statement that 
there is no centralized registry for scope values, plus some examples 
(more than 1) of how values of this attribute can look like.

With out this information I don't think the spec is implementable.




From Francis.Dupont@fdupont.fr  Thu Apr 12 04:43:28 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 5232A21F861C for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 04:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  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 T0nLhFIFNDEy for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 04:43:27 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 839DB21F858F for <gen-art@ietf.org>; Thu, 12 Apr 2012 04:43:27 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id q3CBhKgh034929; Thu, 12 Apr 2012 13:43:20 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201204121143.q3CBhKgh034929@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Qin Wu <bill.wu@huawei.com>
In-reply-to: Your message of Thu, 12 Apr 2012 17:03:21 +0800. <112421EADFC943FEA74836FF9F72F81F@china.huawei.com> 
Date: Thu, 12 Apr 2012 13:43:20 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: gen-art@ietf.org, draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-avtcore-feedback-supression-rtp-16.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, 12 Apr 2012 11:43:28 -0000

 In your previous mail you wrote:

>  > - Abstract page 1: implosion -> explosion (things which can implode are rare :-)
>  
>  [Qin]: RFC4588 referenced by this document is using "implosion". So
>  I think it should be fine to use the same term in this document.:-)

=> RFC 2887 too. IMHO it is time to stop this "implosion" madness and
to return to a correct language (BTW we have the same problem in French, for
an unknown reason the word implosion is often used in place of explosion
when it has the exact opposite meaning...).

>  [Qin]: Okay.
>  > 
>  > - 4.2 page 7: if the SSRC is an IPv4 address the "set to 0" is not very correct.

=> the real problem is what is the SSRC. No spec is very clear, so the
assumption it is not an IPv4 address is right IMHO. (i.e., I withdraw this comment)

> Also it is easy to cause SSRC collision if IPv4 address can be
>  choose as 0.0.0.0 which is broadcast address.

=> BTW 0.0.0.0 is *never* a broadcast address (it could be the only address
in this case :-).

Regards

Francis.Dupont@fdupont.fr

From julian.reschke@gmx.de  Thu Apr 12 06:34:03 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A630821F85F7 for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 06:34:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.963
X-Spam-Level: 
X-Spam-Status: No, score=-102.963 tagged_above=-999 required=5 tests=[AWL=-0.363, 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 27xt1VMHzM3O for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 06:34:03 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id D7F8821F85EF for <gen-art@ietf.org>; Thu, 12 Apr 2012 06:34:02 -0700 (PDT)
Received: (qmail invoked by alias); 12 Apr 2012 13:27:22 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp071) with SMTP; 12 Apr 2012 15:27:22 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX193xHMS4aB3fFeEvCqwQj7noTY5I/LVTZdIGqsvvt ai4/Iy+ghzUMzz
Message-ID: <4F86D836.1000007@gmx.de>
Date: Thu, 12 Apr 2012 15:27:18 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <4F2575CE.9040001@isode.com> <4E1F6AAD24975D4BA5B16804296739436638B7AD@TK5EX14MBXC284.redmond.corp.microsoft.com> <4F27C37C.1090008@isode.com> <4F843A22.4020908@isode.com> <4F843DA1.8080703@isode.com>
In-Reply-To: <4F843DA1.8080703@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: General Area Review Team <gen-art@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, The IESG <iesg@ietf.org>
Subject: [Gen-art] where do error codes go?, was: [OAUTH-WG] Gen-ART Telechat review of draft-ietf-oauth-v2-bearer-18.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, 12 Apr 2012 13:34:03 -0000

On 2012-04-10 16:03, Alexey Melnikov wrote:
> ...
> 2). Section "3.1. Error Codes"
>
> I've suggested to use an IANA registry for this field. Apparently there
> is already a registry created by
> <http://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-11.4>.
> However this document doesn't register values defined in section 3.1
> with IANA and doesn't point to draft-ietf-oauth-v2-23 for the registry.
> I find this to be very confusing.
> ...

Speaking of which, how is an error code returned if the HTTP status is 
*not* 401?

3.1. Error Codes


    When a request fails, the resource server responds using the
    appropriate HTTP status code (typically, 400, 401, 403, or 405), and
    includes one of the following error codes in the response:

    invalid_request
          The request is missing a required parameter, includes an
          unsupported parameter or parameter value, repeats the same
          parameter, uses more than one method for including an access
          token, or is otherwise malformed.  The resource server SHOULD
          respond with the HTTP 400 (Bad Request) status code.

    ...

Is the assumption that the response body is always application/json in 
that case? It might be good to clarify that.

Best regards, Julian

From hartmans@mit.edu  Thu Apr 12 07:36:11 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8555621F864D for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 07:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.443
X-Spam-Level: 
X-Spam-Status: No, score=-103.443 tagged_above=-999 required=5 tests=[AWL=-1.178, 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 FnDY7Bnq884L for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 07:36:10 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id A8C7B21F8642 for <gen-art@ietf.org>; Thu, 12 Apr 2012 07:36:10 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id DF3A82014A; Thu, 12 Apr 2012 10:35:07 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id A804D4766; Thu, 12 Apr 2012 10:36:06 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
References: <201204111505.q3BF5Y2d059608@givry.fdupont.fr>
Date: Thu, 12 Apr 2012 10:36:06 -0400
In-Reply-To: <201204111505.q3BF5Y2d059608@givry.fdupont.fr> (Francis Dupont's message of "Wed, 11 Apr 2012 17:05:34 +0200")
Message-ID: <tsld37d81bd.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: draft-ietf-emu-chbind.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] review of draft-ietf-emu-chbind
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, 12 Apr 2012 14:36:11 -0000

Thanks for the review.
There are a number of very useful comments here and I'd like to have an
opportunity to submit a new draft to address them.
I think it would be fine to do that post-telechat  if there are no other
pre-telechat comments.
I'd also be fine to delay and do a pre-telechat update depending on what
Sean wants.
I won't be able to have any time to work on this until the week of April
23.

From turners@ieca.com  Thu Apr 12 08:53:57 2012
Return-Path: <turners@ieca.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EACE221F8653 for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 08:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.432
X-Spam-Level: 
X-Spam-Status: No, score=-102.432 tagged_above=-999 required=5 tests=[AWL=-0.167, 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 v51zpGKy-4Hv for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 08:53:56 -0700 (PDT)
Received: from gateway15.websitewelcome.com (gateway15.websitewelcome.com [69.56.195.19]) by ietfa.amsl.com (Postfix) with ESMTP id 7F27821F8593 for <gen-art@ietf.org>; Thu, 12 Apr 2012 08:53:56 -0700 (PDT)
Received: by gateway15.websitewelcome.com (Postfix, from userid 5007) id 3BEC830182FFF; Thu, 12 Apr 2012 10:53:56 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway15.websitewelcome.com (Postfix) with ESMTP id 2EE3530182FC4 for <gen-art@ietf.org>; Thu, 12 Apr 2012 10:53:56 -0500 (CDT)
Received: from [71.191.6.163] (port=44232 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1SIMLL-0003uf-PO; Thu, 12 Apr 2012 10:53:56 -0500
Message-ID: <4F86FA92.1030705@ieca.com>
Date: Thu, 12 Apr 2012 11:53:54 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
References: <201204111505.q3BF5Y2d059608@givry.fdupont.fr> <tsld37d81bd.fsf@mit.edu>
In-Reply-To: <tsld37d81bd.fsf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-6-163.washdc.east.verizon.net (thunderfish.local) [71.191.6.163]:44232
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 24
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: draft-ietf-emu-chbind.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] review of draft-ietf-emu-chbind
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, 12 Apr 2012 15:53:57 -0000

Sam,

I'm happy with your suggestions: do a post-telechat update if there are 
no other pre-telechat comments.  If you get other comments, then feel 
free to fire off an update if you have time before the telechat.

spt

On 4/12/12 10:36 AM, Sam Hartman wrote:
> Thanks for the review.
> There are a number of very useful comments here and I'd like to have an
> opportunity to submit a new draft to address them.
> I think it would be fine to do that post-telechat  if there are no other
> pre-telechat comments.
> I'd also be fine to delay and do a pre-telechat update depending on what
> Sean wants.
> I won't be able to have any time to work on this until the week of April
> 23.
>

From nabil.n.bitar@verizon.com  Thu Apr 12 09:06:28 2012
Return-Path: <nabil.n.bitar@verizon.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 02BE621F86C1; Thu, 12 Apr 2012 09:06:28 -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 7D83kjE+MJPB; Thu, 12 Apr 2012 09:06:27 -0700 (PDT)
Received: from fldsmtpe01.verizon.com (fldsmtpe01.verizon.com [140.108.26.140]) by ietfa.amsl.com (Postfix) with ESMTP id A662521F86BE; Thu, 12 Apr 2012 09:06:26 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi02.verizon.com) ([166.68.71.144]) by fldsmtpe01.verizon.com with ESMTP; 12 Apr 2012 16:06:19 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
To: Roni Even <ron.even.tlv@gmail.com>, "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, "draft-ietf-ancp-pon.all@tools.ietf.org" <draft-ietf-ancp-pon.all@tools.ietf.org>
X-IronPort-AV: E=Sophos;i="4.75,410,1330905600";  d="scan'208,217";a="251886159"
Received: from fldp1lumxc7hb03.verizon.com (HELO FLDP1LUMXC7HB03.us.one.verizon.com) ([166.68.75.86]) by fldsmtpi02.verizon.com with ESMTP; 12 Apr 2012 16:06:18 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([169.254.3.155]) by FLDP1LUMXC7HB03.us.one.verizon.com ([166.68.75.86]) with mapi; Thu, 12 Apr 2012 12:06:18 -0400
Date: Thu, 12 Apr 2012 12:06:18 -0400
Thread-Topic: Gen-ART LC review of draft-ietf-ancp-pon-02
Thread-Index: Ac0YxjIy6KryeXQURri9qFPfWPoDgQ==
Message-ID: <CBAC75AC.260C7%nabil.n.bitar@verizon.com>
In-Reply-To: <4f86029b.e249b40a.6b94.4aa7@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.10.0.110310
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CBAC75AC260C7nabilnbitarverizoncom_"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, 'IETF' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-ancp-pon-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, 12 Apr 2012 16:06:28 -0000

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

Thanks.

- Nabil

From: Roni Even <ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>>
Date: Wed, 11 Apr 2012 18:14:30 -0400
To: "Bitar, Nabil N" <nabil.n.bitar@one.verizon.com<mailto:nabil.n.bitar@on=
e.verizon.com>>, "draft-ietf-ancp-pon.all@tools.ietf.org<mailto:draft-ietf-=
ancp-pon.all@tools.ietf.org>" <draft-ietf-ancp-pon.all@tools.ietf.org<mailt=
o:draft-ietf-ancp-pon.all@tools.ietf.org>>
Cc: "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:ge=
n-art@ietf.org>>, 'IETF' <ietf@ietf.org<mailto:ietf@ietf.org>>
Subject: RE: Gen-ART LC review of draft-ietf-ancp-pon-02

Hi Nabil,
I am OK with your proposed text
Roni

From: Bitar, Nabil N [mailto:nabil.n.bitar@verizon.com]
Sent: Wednesday, April 11, 2012 11:09 PM
To: Roni Even; draft-ietf-ancp-pon.all@tools.ietf.org<mailto:draft-ietf-anc=
p-pon.all@tools.ietf.org>
Cc: gen-art@ietf.org<mailto:gen-art@ietf.org>; 'IETF'
Subject: Re: Gen-ART LC review of draft-ietf-ancp-pon-02

Hi,
Thanks for the comments. Please see inline.

Thanks,
Nabil

From: Roni Even <ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>>
Date: Sun, 1 Apr 2012 11:34:54 -0400
To: "draft-ietf-ancp-pon.all@tools.ietf.org<mailto:draft-ietf-ancp-pon.all@=
tools.ietf.org>" <draft-ietf-ancp-pon.all@tools.ietf.org<mailto:draft-ietf-=
ancp-pon.all@tools.ietf.org>>
Cc: "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:ge=
n-art@ietf.org>>, 'IETF' <ietf@ietf.org<mailto:ietf@ietf.org>>
Subject: Gen-ART LC review of draft-ietf-ancp-pon-02

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>.
Sorry for the late review due to IET meeting.
Please resolve these comments along with any other Last Call comments you m=
ay receive.



Document: draft-ietf-ancp-pon-02

Reviewer: Roni Even

Review Date:2012=964=961

IETF LC End Date: 2012=963=9630

IESG Telechat date:



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



Major issues:



Minor issues:



Nits/editorial comments:



In section 4 =94However, the broadcast capability on the PON enables the AN=
 (OLT) to send one copy on the PON as opposed to N  copies of a multicast c=
hannel on the PON serving N premises being  receivers=94 I think the =93bei=
ng=94 before the last word should be deleted

<NB> are you OK saying: "However, the broadcast capability on the PON enabl=
es the AN (OLT) to send one copy on the PON as opposed to one copy to each =
receiver on the PON



General editorial comment is about page breaks which can be better like sec=
tion 7 title is at the end of a page and the text is in the next page. Also=
 some of the figures and their descriptions are split between pages.
<NB> will address that.


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

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;=
 -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14p=
x; font-family: Calibri, sans-serif; "><div>Thanks.</div><div><br></div><di=
v>- Nabil</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div style=
=3D"font-family:Calibri; font-size:11pt; text-align:left; color:black; BORD=
ER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADD=
ING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RI=
GHT: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From: =
</span> Roni Even &lt;<a href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tl=
v@gmail.com</a>&gt;<br><span style=3D"font-weight:bold">Date: </span> Wed, =
11 Apr 2012 18:14:30 -0400<br><span style=3D"font-weight:bold">To: </span> =
&quot;Bitar, Nabil N&quot; &lt;<a href=3D"mailto:nabil.n.bitar@one.verizon.=
com">nabil.n.bitar@one.verizon.com</a>&gt;, &quot;<a href=3D"mailto:draft-i=
etf-ancp-pon.all@tools.ietf.org">draft-ietf-ancp-pon.all@tools.ietf.org</a>=
&quot; &lt;<a href=3D"mailto:draft-ietf-ancp-pon.all@tools.ietf.org">draft-=
ietf-ancp-pon.all@tools.ietf.org</a>&gt;<br><span style=3D"font-weight:bold=
">Cc: </span> &quot;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a=
>&quot; &lt;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;, '=
IETF' &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br><span s=
tyle=3D"font-weight:bold">Subject: </span> RE: Gen-ART LC review of draft-i=
etf-ancp-pon-02<br></div><div><br></div><div xmlns:v=3D"urn:schemas-microso=
ft-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"><style><=
!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></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]--><div lang=3D"EN-US" link=3D"blue" vlink=
=3D"purple"><div class=3D"WordSection1"><p class=3D"MsoNormal"><span style=
=3D"color:#1F497D">Hi Nabil,<o:p></o:p></span></p><p class=3D"MsoNormal"><s=
pan style=3D"color:#1F497D">I am OK with your proposed text<o:p></o:p></spa=
n></p><p class=3D"MsoNormal"><span style=3D"color:#1F497D">Roni<o:p></o:p><=
/span></p><p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;<=
/o:p></span></p><div style=3D"border:none;border-left:solid blue 1.5pt;padd=
ing:0in 0in 0in 4.0pt"><div><div style=3D"border:none;border-top:solid #B5C=
4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class=3D"MsoNormal" style=3D"margin=
-bottom:0in;margin-bottom:.0001pt;line-height:normal"><b><span style=3D"fon=
t-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span styl=
e=3D"font-size: 10pt; font-family: Tahoma, sans-serif; "> Bitar, Nabil N [<=
a href=3D"mailto:nabil.n.bitar@verizon.com">mailto:nabil.n.bitar@verizon.co=
m</a>] <br><b>Sent:</b> Wednesday, April 11, 2012 11:09 PM<br><b>To:</b> Ro=
ni Even; <a href=3D"mailto:draft-ietf-ancp-pon.all@tools.ietf.org">draft-ie=
tf-ancp-pon.all@tools.ietf.org</a><br><b>Cc:</b> <a href=3D"mailto:gen-art@=
ietf.org">gen-art@ietf.org</a>; 'IETF'<br><b>Subject:</b> Re: Gen-ART LC re=
view of draft-ietf-ancp-pon-02<o:p></o:p></span></p></div></div><p class=3D=
"MsoNormal"><o:p>&nbsp;</o:p></p><div><p class=3D"MsoNormal"><span style=3D=
"font-size:10.5pt;line-height:115%;color:black">Hi,<o:p></o:p></span></p></=
div><div><p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;line-height=
:115%;color:black">Thanks for the comments. Please see inline.<o:p></o:p></=
span></p></div><div><p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;=
line-height:115%;color:black"><o:p>&nbsp;</o:p></span></p></div><div><p cla=
ss=3D"MsoNormal"><span style=3D"font-size:10.5pt;line-height:115%;color:bla=
ck">Thanks,<o:p></o:p></span></p></div><div><p class=3D"MsoNormal"><span st=
yle=3D"font-size:10.5pt;line-height:115%;color:black">Nabil<o:p></o:p></spa=
n></p></div><div><p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;lin=
e-height:115%;color:black"><o:p>&nbsp;</o:p></span></p></div><div style=3D"=
border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p cl=
ass=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><span sty=
le=3D"color:black">Roni Even &lt;<a href=3D"mailto:ron.even.tlv@gmail.com">=
ron.even.tlv@gmail.com</a>&gt;<br><b>Date: </b>Sun, 1 Apr 2012 11:34:54 -04=
00<br><b>To: </b>&quot;<a href=3D"mailto:draft-ietf-ancp-pon.all@tools.ietf=
.org">draft-ietf-ancp-pon.all@tools.ietf.org</a>&quot; &lt;<a href=3D"mailt=
o:draft-ietf-ancp-pon.all@tools.ietf.org">draft-ietf-ancp-pon.all@tools.iet=
f.org</a>&gt;<br><b>Cc: </b>&quot;<a href=3D"mailto:gen-art@ietf.org">gen-a=
rt@ietf.org</a>&quot; &lt;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.=
org</a>&gt;, 'IETF' &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&=
gt;<br><b>Subject: </b>Gen-ART LC review of draft-ietf-ancp-pon-02<o:p></o:=
p></span></p></div><div><p class=3D"MsoNormal"><span style=3D"font-size:10.=
5pt;line-height:115%;color:black"><o:p>&nbsp;</o:p></span></p></div><div><d=
iv><p class=3D"MsoNormal"><span style=3D"color:black">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=3D"MsoNormal"><span style=3D"color:b=
lack">Sorry for the late review due to IET meeting.<o:p></o:p></span></p><p=
 class=3D"MsoNormal"><span style=3D"color:black">Please resolve these comme=
nts along with any other Last Call comments you may receive.<o:p></o:p></sp=
an></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; color: bla=
ck; font-family: Calibri, sans-serif; ">&nbsp;</span><span style=3D"color:b=
lack"><o:p></o:p></span></p><p class=3D"MsoPlainText"><span lang=3D"FR" sty=
le=3D"font-size: 11pt; color: black; font-family: Calibri, sans-serif; ">Do=
cument: draft-ietf-ancp-pon-02</span><span style=3D"color:black"><o:p></o:p=
></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; color=
: black; font-family: Calibri, sans-serif; ">Reviewer: Roni Even</span><spa=
n style=3D"color:black"><o:p></o:p></span></p><p class=3D"MsoPlainText"><sp=
an style=3D"font-size: 11pt; color: black; font-family: Calibri, sans-serif=
; ">Review Date:2012=964=961</span><span style=3D"color:black"><o:p></o:p><=
/span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; color: =
black; font-family: Calibri, sans-serif; ">IETF LC End Date: 2012=963=9630<=
/span><span style=3D"color:black"><o:p></o:p></span></p><p class=3D"MsoPlai=
nText"><span style=3D"font-size: 11pt; color: black; font-family: Calibri, =
sans-serif; ">IESG Telechat date:</span><span style=3D"color:black"><o:p></=
o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; co=
lor: black; font-family: Calibri, sans-serif; ">&nbsp;</span><span style=3D=
"color:black"><o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=
=3D"font-size: 11pt; color: black; font-family: Calibri, sans-serif; ">Summ=
ary: This draft is ready for publication as an Informational RFC.</span><sp=
an style=3D"color:black"><o:p></o:p></span></p><p class=3D"MsoPlainText"><s=
pan style=3D"font-size: 11pt; color: black; font-family: Calibri, sans-seri=
f; ">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p><p clas=
s=3D"MsoPlainText"><span style=3D"font-size: 11pt; color: black; font-famil=
y: Calibri, sans-serif; ">Major issues:</span><span style=3D"color:black"><=
o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11=
pt; color: black; font-family: Calibri, sans-serif; ">&nbsp;</span><span st=
yle=3D"color:black"><o:p></o:p></span></p><p class=3D"MsoPlainText"><span s=
tyle=3D"font-size: 11pt; color: black; font-family: Calibri, sans-serif; ">=
Minor issues:</span><span style=3D"color:black"><o:p></o:p></span></p><p cl=
ass=3D"MsoPlainText"><span style=3D"font-size: 11pt; color: black; font-fam=
ily: Calibri, sans-serif; ">&nbsp;</span><span style=3D"color:black"><o:p><=
/o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; c=
olor: black; font-family: Calibri, sans-serif; ">Nits/editorial comments:</=
span><span style=3D"color:black"><o:p></o:p></span></p><p class=3D"MsoPlain=
Text"><span style=3D"font-size: 11pt; color: black; font-family: Calibri, s=
ans-serif; ">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p=
><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; color: black; fo=
nt-family: Calibri, sans-serif; ">In section 4 =94However, the broadcast ca=
pability on the PON enables the AN (OLT) to send one copy on the PON as opp=
osed to N&nbsp; copies of a multicast channel on the PON serving N premises=
 being&nbsp; receivers=94 I think the =93being=94 before the last word shou=
ld be deleted</span><span style=3D"color:black"><o:p></o:p></span></p></div=
></div><div><p class=3D"MsoNormal" style=3D"margin-bottom:0in;margin-bottom=
:.0001pt;line-height:normal"><span style=3D"font-size:10.5pt;color:black"><=
o:p>&nbsp;</o:p></span></p></div><div><p class=3D"MsoNormal" style=3D"margi=
n-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span style=3D"font-=
size:10.5pt;color:black">&lt;NB&gt; are you OK saying: &quot;</span><span c=
lass=3D"apple-style-span"><span style=3D"font-size:11.5pt;color:black">Howe=
ver, the broadcast capability on the PON enables the AN (OLT) to send one c=
opy on the PON as opposed to one copy to each receiver on the PON&nbsp;</sp=
an></span><span style=3D"font-size:10.5pt;color:black"><o:p></o:p></span></=
p></div><div><div><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt;=
 color: black; font-family: Calibri, sans-serif; ">&nbsp;</span><span style=
=3D"color:black"><o:p></o:p></span></p><p class=3D"MsoPlainText"><span styl=
e=3D"font-size: 11pt; color: black; font-family: Calibri, sans-serif; ">Gen=
eral editorial comment is about page breaks which can be better like sectio=
n 7 title is at the end of a page and the text is in the next page. Also so=
me of the figures and their descriptions are split between pages.</span><sp=
an style=3D"color:black"><o:p></o:p></span></p></div></div><div><p class=3D=
"MsoNormal" style=3D"margin-bottom:0in;margin-bottom:.0001pt;line-height:no=
rmal"><span style=3D"font-size:10.5pt;color:black">&lt;NB&gt; will address =
that.<o:p></o:p></span></p></div><div><div><p class=3D"MsoNormal"><span dir=
=3D"RTL"></span><span lang=3D"HE" dir=3D"RTL" style=3D"color: black; font-f=
amily: Arial, sans-serif; "><span dir=3D"RTL"></span>&nbsp;</span><span sty=
le=3D"color:black"><o:p></o:p></span></p></div></div></div></div></div></di=
v></span></body></html>

--_000_CBAC75AC260C7nabilnbitarverizoncom_--

From mahoney@nostrum.com  Thu Apr 12 16:05:09 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 C152221F8764 for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 16:05:09 -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 Ij4N+tzoouX9 for <gen-art@ietfa.amsl.com>; Thu, 12 Apr 2012 16:05:09 -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 E117221F8738 for <gen-art@ietf.org>; Thu, 12 Apr 2012 16:05:08 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-40-17.dllstx.fios.verizon.net [71.170.40.17]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q3CN58fB092790 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 12 Apr 2012 18:05:08 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4F875FA4.6000409@nostrum.com>
Date: Thu, 12 Apr 2012 18:05:08 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
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: 71.170.40.17 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-04-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Apr 2012 23:05:10 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft

Mary Barnes            2012-04-20  draft-ietf-pkix-pubkey-caps-04

Martin Thomson         2012-04-24  draft-ietf-marf-as-13

Miguel Garcia          2012-04-25  draft-ietf-dane-protocol-19

Peter McCann           2012-04-26  draft-ietf-l2vpn-arp-mediation-19



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

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


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 bill.wu@huawei.com  Fri Apr 13 01:22:49 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 E60A621F84BF for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 01:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.773
X-Spam-Level: 
X-Spam-Status: No, score=-0.773 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599, MIME_BASE64_TEXT=1.753]
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 iXu5+BFzkrVb for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 01:22:48 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 7104821F8491 for <gen-art@ietf.org>; Fri, 13 Apr 2012 01:22:46 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFE56503; Fri, 13 Apr 2012 04:22:46 -0400 (EDT)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 01:19:51 -0700
Received: from SZXEML422-HUB.china.huawei.com (10.82.67.161) by dfweml403-hub.china.huawei.com (10.193.5.151) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 01:19:12 -0700
Received: from w53375 (10.138.41.149) by szxeml422-hub.china.huawei.com (10.82.67.161) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 16:19:45 +0800
Message-ID: <3E7F70F6BF7A49EC834DD001A636D13E@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
References: <201204121143.q3CBhKgh034929@givry.fdupont.fr>
Date: Fri, 13 Apr 2012 16:19:44 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
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: gen-art@ietf.org, draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-avtcore-feedback-supression-rtp-16.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, 13 Apr 2012 08:22:49 -0000

SGksRnJhbmNpczoNClNvcnJ5IGZvciBsYXRlIHJlcGx5LiBwbGVhc2Ugc2VlIG15IHJlcHkgaW5s
aW5lLg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJGcmFuY2lzIER1cG9u
dCIgPEZyYW5jaXMuRHVwb250QGZkdXBvbnQuZnI+DQpUbzogIlFpbiBXdSIgPGJpbGwud3VAaHVh
d2VpLmNvbT4NCkNjOiA8Z2VuLWFydEBpZXRmLm9yZz47IDxkcmFmdC1pZXRmLWF2dGNvcmUtZmVl
ZGJhY2stc3VwcmVzc2lvbi1ydHAuYWxsQHRvb2xzLmlldGYub3JnPg0KU2VudDogVGh1cnNkYXks
IEFwcmlsIDEyLCAyMDEyIDc6NDMgUE0NClN1YmplY3Q6IFJlOiByZXZpZXcgb2YgZHJhZnQtaWV0
Zi1hdnRjb3JlLWZlZWRiYWNrLXN1cHJlc3Npb24tcnRwLTE2LnR4dCANCg0KDQo+IEluIHlvdXIg
cHJldmlvdXMgbWFpbCB5b3Ugd3JvdGU6DQo+IA0KPj4gID4gLSBBYnN0cmFjdCBwYWdlIDE6IGlt
cGxvc2lvbiAtPiBleHBsb3Npb24gKHRoaW5ncyB3aGljaCBjYW4gaW1wbG9kZSBhcmUgcmFyZSA6
LSkNCj4+ICANCj4+ICBbUWluXTogUkZDNDU4OCByZWZlcmVuY2VkIGJ5IHRoaXMgZG9jdW1lbnQg
aXMgdXNpbmcgImltcGxvc2lvbiIuIFNvDQo+PiAgSSB0aGluayBpdCBzaG91bGQgYmUgZmluZSB0
byB1c2UgdGhlIHNhbWUgdGVybSBpbiB0aGlzIGRvY3VtZW50LjotKQ0KPiANCj4gPT4gUkZDIDI4
ODcgdG9vLiBJTUhPIGl0IGlzIHRpbWUgdG8gc3RvcCB0aGlzICJpbXBsb3Npb24iIG1hZG5lc3Mg
YW5kDQo+IHRvIHJldHVybiB0byBhIGNvcnJlY3QgbGFuZ3VhZ2UgKEJUVyB3ZSBoYXZlIHRoZSBz
YW1lIHByb2JsZW0gaW4gRnJlbmNoLCBmb3INCj4gYW4gdW5rbm93biByZWFzb24gdGhlIHdvcmQg
aW1wbG9zaW9uIGlzIG9mdGVuIHVzZWQgaW4gcGxhY2Ugb2YgZXhwbG9zaW9uDQo+IHdoZW4gaXQg
aGFzIHRoZSBleGFjdCBvcHBvc2l0ZSBtZWFuaW5nLi4uKS4NCg0KW1Fpbl06SSBjYW4gdW5kZXJz
dGFuZCBpdCBpcyBtb3JlIHNlbnNpdGl2ZSB0byB1c2UgImV4cGxvc2lvbiIgdGhhbiAiaW1wbG9z
aW9uImluIEZyYW5jZS46LSkNCkhvd2V2ZXIgbXkgdW5kZXJzdGFuZGluZyBpcyBpbXBsb3Npb24g
c2VlbXMgdG8gbWVhbiBmZWVkYmFjayBtZXNzYWdlcyBvdmVyd2hlbG0gdGhlIG5ldHdvcmsgY2Fw
YWNpdHkuDQpJZiB3ZSBjaGFuZ2UgImltcGxvc2lvbiIgaW50byAiZXhwbG9zaW9uIiwgd2Ugc2Vl
bXMgdG8gY2hhbmdlIHRoZSBtZWFuaW5nIG9mICJmZWVkYmFjayBpbXBsb3Npb24iLCANCnRoYXQg
aXMgdG8gc2F5LCAiZmVlZGJhY2sgZXhwbGlzaW9uICIgbWVhbnMgZmVlZGJhY2sgbWVzc2FnZSBo
YXMgYWxyZWFkeSBwYXJhbHl6ZWQgdGhlIG5ldHdvcmsuIFRoZSBOZXR3b3JrIGRpZXMgOi0pLg0K
SSBhbSBhd2FyZSB0aGF0IFJGQzQ1ODUgYWxzbyB1c2UgImZlZWRiYWNrIGltcGxvc2lvbiIuIFNp
bmNlIHRoaXMgZHJhZnQgcmVmZXJlbmNlcyBSRkM0NTg1LA0KSXNuJ3QgZHJhZnQtaWV0Zi1hdnRj
b3JlLWZlZWRiYWNrLXN1cHJlc3Npb24tcnRwIGluIGFjY29yZGFuY2Ugd2l0aCBSRkM0NTg1Pw0K
DQo+IA0KPj4gIFtRaW5dOiBPa2F5Lg0KPj4gID4gDQo+PiAgPiAtIDQuMiBwYWdlIDc6IGlmIHRo
ZSBTU1JDIGlzIGFuIElQdjQgYWRkcmVzcyB0aGUgInNldCB0byAwIiBpcyBub3QgdmVyeSBjb3Jy
ZWN0Lg0KPiANCj4gPT4gdGhlIHJlYWwgcHJvYmxlbSBpcyB3aGF0IGlzIHRoZSBTU1JDLiBObyBz
cGVjIGlzIHZlcnkgY2xlYXIsIHNvIHRoZQ0KPiBhc3N1bXB0aW9uIGl0IGlzIG5vdCBhbiBJUHY0
IGFkZHJlc3MgaXMgcmlnaHQgSU1ITy4gKGkuZS4sIEkgd2l0aGRyYXcgdGhpcyBjb21tZW50KQ0K
DQpbUWluXTogT2theS4NCj4gDQo+PiBBbHNvIGl0IGlzIGVhc3kgdG8gY2F1c2UgU1NSQyBjb2xs
aXNpb24gaWYgSVB2NCBhZGRyZXNzIGNhbiBiZQ0KPj4gIGNob29zZSBhcyAwLjAuMC4wIHdoaWNo
IGlzIGJyb2FkY2FzdCBhZGRyZXNzLg0KPiANCj4gPT4gQlRXIDAuMC4wLjAgaXMgKm5ldmVyKiBh
IGJyb2FkY2FzdCBhZGRyZXNzIChpdCBjb3VsZCBiZSB0aGUgb25seSBhZGRyZXNzDQo+IGluIHRo
aXMgY2FzZSA6LSkuDQoNCltRaW5dOiBBZ3JlZS4NCj4gDQo+IFJlZ2FyZHMNCj4gDQo+IEZyYW5j
aXMuRHVwb250QGZkdXBvbnQuZnI=


From magnus.westerlund@ericsson.com  Fri Apr 13 01:37:28 2012
Return-Path: <magnus.westerlund@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 A4C1421F84AE for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 01:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.186
X-Spam-Level: 
X-Spam-Status: No, score=-106.186 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQGw9RGMa5YX for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 01:37:28 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id BA7B121F84A7 for <gen-art@ietf.org>; Fri, 13 Apr 2012 01:37:20 -0700 (PDT)
X-AuditID: c1b4fb2d-b7b76ae0000063d8-2d-4f87e5bf321b
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id D1.75.25560.FB5E78F4; Fri, 13 Apr 2012 10:37:19 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.213.0; Fri, 13 Apr 2012 10:37:19 +0200
Message-ID: <4F87E5BE.3080100@ericsson.com>
Date: Fri, 13 Apr 2012 10:37:18 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <201204121143.q3CBhKgh034929@givry.fdupont.fr> <3E7F70F6BF7A49EC834DD001A636D13E@china.huawei.com>
In-Reply-To: <3E7F70F6BF7A49EC834DD001A636D13E@china.huawei.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org" <draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-avtcore-feedback-supression-rtp-16.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, 13 Apr 2012 08:37:28 -0000

On 2012-04-13 10:19, Qin Wu wrote:
> Hi,Francis:
> Sorry for late reply. please see my repy inline.
> ----- Original Message ----- 
> From: "Francis Dupont" <Francis.Dupont@fdupont.fr>
> To: "Qin Wu" <bill.wu@huawei.com>
> Cc: <gen-art@ietf.org>; <draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org>
> Sent: Thursday, April 12, 2012 7:43 PM
> Subject: Re: review of draft-ietf-avtcore-feedback-supression-rtp-16.txt 
> 
> 
>> In your previous mail you wrote:
>>
>>>  > - Abstract page 1: implosion -> explosion (things which can implode are rare :-)
>>>  
>>>  [Qin]: RFC4588 referenced by this document is using "implosion". So
>>>  I think it should be fine to use the same term in this document.:-)
>>
>> => RFC 2887 too. IMHO it is time to stop this "implosion" madness and
>> to return to a correct language (BTW we have the same problem in French, for
>> an unknown reason the word implosion is often used in place of explosion
>> when it has the exact opposite meaning...).
> 
> [Qin]:I can understand it is more sensitive to use "explosion" than "implosion"in France.:-)
> However my understanding is implosion seems to mean feedback messages overwhelm the network capacity.
> If we change "implosion" into "explosion", we seems to change the meaning of "feedback implosion", 
> that is to say, "feedback explision " means feedback message has already paralyzed the network. The Network dies :-).
> I am aware that RFC4585 also use "feedback implosion". Since this draft references RFC4585,
> Isn't draft-ietf-avtcore-feedback-supression-rtp in accordance with RFC4585?

I would like to point out that feedback implosion actually can be seen
as an implosion event. All the feedback traffic generated are
concentrated at the target for the feedback. Thus causing an implosion
of the feedback target under the "weight" of all the feedback.

But, seriously "Feedback Implosion" is an established expression within
computer science. Thus although it may not be all correct we shouldn't
change it. I would recommend that you google "Feedback Implosion" all
the hits on the first page are related to computer science, at least for me.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From bill.wu@huawei.com  Fri Apr 13 01:59:19 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 E7DE421F848F for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 01:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Level: 
X-Spam-Status: No, score=-1.652 tagged_above=-999 required=5 tests=[AWL=0.947,  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 EFELeLoyn7wq for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 01:59:19 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id D56A021F8606 for <gen-art@ietf.org>; Fri, 13 Apr 2012 01:59:17 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFE58507; Fri, 13 Apr 2012 04:59:17 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 01:56:02 -0700
Received: from SZXEML422-HUB.china.huawei.com (10.82.67.161) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 01:56:08 -0700
Received: from w53375 (10.138.41.149) by szxeml422-hub.china.huawei.com (10.82.67.161) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 16:56:02 +0800
Message-ID: <C92761F5031B46058D647B52CEF649A5@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <201204121143.q3CBhKgh034929@givry.fdupont.fr> <3E7F70F6BF7A49EC834DD001A636D13E@china.huawei.com> <4F87E5BE.3080100@ericsson.com>
Date: Fri, 13 Apr 2012 16:56:01 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
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: gen-art@ietf.org, draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-avtcore-feedback-supression-rtp-16.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, 13 Apr 2012 08:59:20 -0000

SGksDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIk1hZ251cyBXZXN0ZXJs
dW5kIiA8bWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tPg0KVG86ICJRaW4gV3UiIDxiaWxs
Lnd1QGh1YXdlaS5jb20+DQpDYzogIkZyYW5jaXMgRHVwb250IiA8RnJhbmNpcy5EdXBvbnRAZmR1
cG9udC5mcj47IDxnZW4tYXJ0QGlldGYub3JnPjsgPGRyYWZ0LWlldGYtYXZ0Y29yZS1mZWVkYmFj
ay1zdXByZXNzaW9uLXJ0cC5hbGxAdG9vbHMuaWV0Zi5vcmc+DQpTZW50OiBGcmlkYXksIEFwcmls
IDEzLCAyMDEyIDQ6MzcgUE0NClN1YmplY3Q6IFJlOiByZXZpZXcgb2YgZHJhZnQtaWV0Zi1hdnRj
b3JlLWZlZWRiYWNrLXN1cHJlc3Npb24tcnRwLTE2LnR4dA0KDQoNCj4gT24gMjAxMi0wNC0xMyAx
MDoxOSwgUWluIFd1IHdyb3RlOg0KPj4gSGksRnJhbmNpczoNCj4+IFNvcnJ5IGZvciBsYXRlIHJl
cGx5LiBwbGVhc2Ugc2VlIG15IHJlcHkgaW5saW5lLg0KPj4gLS0tLS0gT3JpZ2luYWwgTWVzc2Fn
ZSAtLS0tLSANCj4+IEZyb206ICJGcmFuY2lzIER1cG9udCIgPEZyYW5jaXMuRHVwb250QGZkdXBv
bnQuZnI+DQo+PiBUbzogIlFpbiBXdSIgPGJpbGwud3VAaHVhd2VpLmNvbT4NCj4+IENjOiA8Z2Vu
LWFydEBpZXRmLm9yZz47IDxkcmFmdC1pZXRmLWF2dGNvcmUtZmVlZGJhY2stc3VwcmVzc2lvbi1y
dHAuYWxsQHRvb2xzLmlldGYub3JnPg0KPj4gU2VudDogVGh1cnNkYXksIEFwcmlsIDEyLCAyMDEy
IDc6NDMgUE0NCj4+IFN1YmplY3Q6IFJlOiByZXZpZXcgb2YgZHJhZnQtaWV0Zi1hdnRjb3JlLWZl
ZWRiYWNrLXN1cHJlc3Npb24tcnRwLTE2LnR4dCANCj4+IA0KPj4gDQo+Pj4gSW4geW91ciBwcmV2
aW91cyBtYWlsIHlvdSB3cm90ZToNCj4+Pg0KPj4+PiAgPiAtIEFic3RyYWN0IHBhZ2UgMTogaW1w
bG9zaW9uIC0+IGV4cGxvc2lvbiAodGhpbmdzIHdoaWNoIGNhbiBpbXBsb2RlIGFyZSByYXJlIDot
KQ0KPj4+PiAgDQo+Pj4+ICBbUWluXTogUkZDNDU4OCByZWZlcmVuY2VkIGJ5IHRoaXMgZG9jdW1l
bnQgaXMgdXNpbmcgImltcGxvc2lvbiIuIFNvDQo+Pj4+ICBJIHRoaW5rIGl0IHNob3VsZCBiZSBm
aW5lIHRvIHVzZSB0aGUgc2FtZSB0ZXJtIGluIHRoaXMgZG9jdW1lbnQuOi0pDQo+Pj4NCj4+PiA9
PiBSRkMgMjg4NyB0b28uIElNSE8gaXQgaXMgdGltZSB0byBzdG9wIHRoaXMgImltcGxvc2lvbiIg
bWFkbmVzcyBhbmQNCj4+PiB0byByZXR1cm4gdG8gYSBjb3JyZWN0IGxhbmd1YWdlIChCVFcgd2Ug
aGF2ZSB0aGUgc2FtZSBwcm9ibGVtIGluIEZyZW5jaCwgZm9yDQo+Pj4gYW4gdW5rbm93biByZWFz
b24gdGhlIHdvcmQgaW1wbG9zaW9uIGlzIG9mdGVuIHVzZWQgaW4gcGxhY2Ugb2YgZXhwbG9zaW9u
DQo+Pj4gd2hlbiBpdCBoYXMgdGhlIGV4YWN0IG9wcG9zaXRlIG1lYW5pbmcuLi4pLg0KPj4gDQo+
PiBbUWluXTpJIGNhbiB1bmRlcnN0YW5kIGl0IGlzIG1vcmUgc2Vuc2l0aXZlIHRvIHVzZSAiZXhw
bG9zaW9uIiB0aGFuICJpbXBsb3Npb24iaW4gRnJhbmNlLjotKQ0KPj4gSG93ZXZlciBteSB1bmRl
cnN0YW5kaW5nIGlzIGltcGxvc2lvbiBzZWVtcyB0byBtZWFuIGZlZWRiYWNrIG1lc3NhZ2VzIG92
ZXJ3aGVsbSB0aGUgbmV0d29yayBjYXBhY2l0eS4NCj4+IElmIHdlIGNoYW5nZSAiaW1wbG9zaW9u
IiBpbnRvICJleHBsb3Npb24iLCB3ZSBzZWVtcyB0byBjaGFuZ2UgdGhlIG1lYW5pbmcgb2YgImZl
ZWRiYWNrIGltcGxvc2lvbiIsIA0KPj4gdGhhdCBpcyB0byBzYXksICJmZWVkYmFjayBleHBsaXNp
b24gIiBtZWFucyBmZWVkYmFjayBtZXNzYWdlIGhhcyBhbHJlYWR5IHBhcmFseXplZCB0aGUgbmV0
d29yay4gVGhlIE5ldHdvcmsgZGllcyA6LSkuDQo+PiBJIGFtIGF3YXJlIHRoYXQgUkZDNDU4NSBh
bHNvIHVzZSAiZmVlZGJhY2sgaW1wbG9zaW9uIi4gU2luY2UgdGhpcyBkcmFmdCByZWZlcmVuY2Vz
IFJGQzQ1ODUsDQo+PiBJc24ndCBkcmFmdC1pZXRmLWF2dGNvcmUtZmVlZGJhY2stc3VwcmVzc2lv
bi1ydHAgaW4gYWNjb3JkYW5jZSB3aXRoIFJGQzQ1ODU/DQo+IA0KPiBJIHdvdWxkIGxpa2UgdG8g
cG9pbnQgb3V0IHRoYXQgZmVlZGJhY2sgaW1wbG9zaW9uIGFjdHVhbGx5IGNhbiBiZSBzZWVuDQo+
IGFzIGFuIGltcGxvc2lvbiBldmVudC4gQWxsIHRoZSBmZWVkYmFjayB0cmFmZmljIGdlbmVyYXRl
ZCBhcmUNCj4gY29uY2VudHJhdGVkIGF0IHRoZSB0YXJnZXQgZm9yIHRoZSBmZWVkYmFjay4gVGh1
cyBjYXVzaW5nIGFuIGltcGxvc2lvbg0KPiBvZiB0aGUgZmVlZGJhY2sgdGFyZ2V0IHVuZGVyIHRo
ZSAid2VpZ2h0IiBvZiBhbGwgdGhlIGZlZWRiYWNrLg0KDQpbUWluXTogRXhhY3RseS4NCg0KPiBC
dXQsIHNlcmlvdXNseSAiRmVlZGJhY2sgSW1wbG9zaW9uIiBpcyBhbiBlc3RhYmxpc2hlZCBleHBy
ZXNzaW9uIHdpdGhpbg0KPiBjb21wdXRlciBzY2llbmNlLiBUaHVzIGFsdGhvdWdoIGl0IG1heSBu
b3QgYmUgYWxsIGNvcnJlY3Qgd2Ugc2hvdWxkbid0DQo+IGNoYW5nZSBpdC4gDQoNCltRaW5dOiBB
Z3JlZS4gDQoNCj5JIHdvdWxkIHJlY29tbWVuZCB0aGF0IHlvdSBnb29nbGUgIkZlZWRiYWNrIElt
cGxvc2lvbiIgYWxsDQo+IHRoZSBoaXRzIG9uIHRoZSBmaXJzdCBwYWdlIGFyZSByZWxhdGVkIHRv
IGNvbXB1dGVyIHNjaWVuY2UsIGF0IGxlYXN0IGZvciBtZS4NCj4gDQo+IENoZWVycw0KPiANCj4g
TWFnbnVzIFdlc3Rlcmx1bmQNCj4gDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gTXVsdGltZWRpYSBUZWNo
bm9sb2dpZXMsIEVyaWNzc29uIFJlc2VhcmNoIEVBQi9UVk0NCj4gLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiBF
cmljc3NvbiBBQiAgICAgICAgICAgICAgICB8IFBob25lICArNDYgMTAgNzE0ODI4Nw0KPiBGw6Ry
w7ZnYXRhbiA2ICAgICAgICAgICAgICAgIHwgTW9iaWxlICs0NiA3MyAwOTQ5MDc5DQo+IFNFLTE2
NCA4MCBTdG9ja2hvbG0sIFN3ZWRlbnwgbWFpbHRvOiBtYWdudXMud2VzdGVybHVuZEBlcmljc3Nv
bi5jb20NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPg==


From Francis.Dupont@fdupont.fr  Fri Apr 13 02:07:04 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 7B74A21F8491 for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 02:07:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WdF3S6w0pnGb for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 02:07:04 -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 AF6B721F847D for <gen-art@ietf.org>; Fri, 13 Apr 2012 02:07:03 -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 q3D96t6a013105; Fri, 13 Apr 2012 11:06:57 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201204130906.q3D96t6a013105@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Qin Wu <bill.wu@huawei.com>
In-reply-to: Your message of Fri, 13 Apr 2012 16:19:44 +0800. <3E7F70F6BF7A49EC834DD001A636D13E@china.huawei.com> 
Date: Fri, 13 Apr 2012 11:06:55 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: gen-art@ietf.org, draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-avtcore-feedback-supression-rtp-16.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, 13 Apr 2012 09:07:04 -0000

 In your previous mail you wrote:

> [Qin]:I can understand it is more sensitive to use "explosion" than
> "implosion" in France.:-)

=> both words exist in both language with the same spelling and
meaning.  Perhaps do you mean we are more attached to use the right
term in France (:-)?

> However my understanding is implosion seems to mean feedback
> messages overwhelm the network capacity.

=> this is the definition of explosion.

>  If we change "implosion" into "explosion", we seems to change the
>  meaning of "feedback implosion", that is to say, "feedback
>  explosion " means feedback message has already paralyzed the
>  network. The Network dies :-).  I am aware that RFC4585 also use
>  "feedback implosion". Since this draft references RFC4585, Isn't
>  draft-ietf-avtcore-feedback-supression-rtp in accordance with
>  RFC4585?

=> you have the choice between using the correct term or keeping the
wrong term because some did the error in referenced documents.
You know my opinion.

Regards

Francis.Dupont@fdupont.fr

PS: perhaps we should ask the RFC Editor to produce a collective
Errata to fix this misuse of implosion for explosion?

From Francis.Dupont@fdupont.fr  Fri Apr 13 02:14:05 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 6CEC221F8675 for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 02:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level: 
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.056,  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 c3EblTT+YqTJ for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 02:14:05 -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 9DDE121F8606 for <gen-art@ietf.org>; Fri, 13 Apr 2012 02:14:04 -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 q3D9DvDB013527; Fri, 13 Apr 2012 11:13:57 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201204130913.q3D9DvDB013527@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-reply-to: Your message of Fri, 13 Apr 2012 10:37:18 +0200. <4F87E5BE.3080100@ericsson.com> 
Date: Fri, 13 Apr 2012 11:13:57 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org" <draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org>, Qin Wu <bill.wu@huawei.com>
Subject: Re: [Gen-art] review of draft-ietf-avtcore-feedback-supression-rtp-16.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, 13 Apr 2012 09:14:05 -0000

 In your previous mail you wrote:

>  I would like to point out that feedback implosion actually can be
>  seen as an implosion event. All the feedback traffic generated are
>  concentrated at the target for the feedback. Thus causing an
>  implosion of the feedback target under the "weight" of all the
>  feedback.
>
>  But, seriously "Feedback Implosion" is an established expression
>  within computer science. Thus although it may not be all correct we
>  shouldn't change it. I would recommend that you google "Feedback
>  Implosion" all the hits on the first page are related to computer
>  science, at least for me.

=> hum, it seems the incorrect use of the term implosion is well
established. IMHO it should be like the use of the incorrect term
encrypted, so should be handled the same way: to fix it is the right
way in French, in English it is pedantic so in general should not be
fixed (and this is a real example for RFCs).

So I give up on it...

Thanks

Francis.Dupont@fdupont.fr

From bill.wu@huawei.com  Fri Apr 13 02:21:25 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 745F821F8793 for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 02:21:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.815
X-Spam-Level: 
X-Spam-Status: No, score=-0.815 tagged_above=-999 required=5 tests=[AWL=0.031,  BAYES_00=-2.599, MIME_BASE64_TEXT=1.753]
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 4tjV7p6jMupo for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 02:21:25 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id DD84E21F8786 for <gen-art@ietf.org>; Fri, 13 Apr 2012 02:21:24 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFE59654; Fri, 13 Apr 2012 05:21:24 -0400 (EDT)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 02:18:44 -0700
Received: from SZXEML420-HUB.china.huawei.com (10.82.67.159) by dfweml403-hub.china.huawei.com (10.193.5.151) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 02:18:13 -0700
Received: from w53375 (10.138.41.149) by szxeml420-hub.china.huawei.com (10.82.67.159) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 17:18:44 +0800
Message-ID: <7F3265D310AF4AC499672FD504930FAC@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
References: <201204130906.q3D96t6a013105@givry.fdupont.fr>
Date: Fri, 13 Apr 2012 17:18:43 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
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: gen-art@ietf.org, draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-avtcore-feedback-supression-rtp-16.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, 13 Apr 2012 09:21:25 -0000

SGksDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkZyYW5jaXMgRHVwb250
IiA8RnJhbmNpcy5EdXBvbnRAZmR1cG9udC5mcj4NClRvOiAiUWluIFd1IiA8YmlsbC53dUBodWF3
ZWkuY29tPg0KQ2M6IDxnZW4tYXJ0QGlldGYub3JnPjsgPGRyYWZ0LWlldGYtYXZ0Y29yZS1mZWVk
YmFjay1zdXByZXNzaW9uLXJ0cC5hbGxAdG9vbHMuaWV0Zi5vcmc+DQpTZW50OiBGcmlkYXksIEFw
cmlsIDEzLCAyMDEyIDU6MDYgUE0NClN1YmplY3Q6IFJlOiByZXZpZXcgb2YgZHJhZnQtaWV0Zi1h
dnRjb3JlLWZlZWRiYWNrLXN1cHJlc3Npb24tcnRwLTE2LnR4dCANCg0KDQo+IEluIHlvdXIgcHJl
dmlvdXMgbWFpbCB5b3Ugd3JvdGU6DQo+IA0KPj4gW1Fpbl06SSBjYW4gdW5kZXJzdGFuZCBpdCBp
cyBtb3JlIHNlbnNpdGl2ZSB0byB1c2UgImV4cGxvc2lvbiIgdGhhbg0KPj4gImltcGxvc2lvbiIg
aW4gRnJhbmNlLjotKQ0KPiANCj4gPT4gYm90aCB3b3JkcyBleGlzdCBpbiBib3RoIGxhbmd1YWdl
IHdpdGggdGhlIHNhbWUgc3BlbGxpbmcgYW5kDQo+IG1lYW5pbmcuICBQZXJoYXBzIGRvIHlvdSBt
ZWFuIHdlIGFyZSBtb3JlIGF0dGFjaGVkIHRvIHVzZSB0aGUgcmlnaHQNCj4gdGVybSBpbiBGcmFu
Y2UgKDotKT8NCg0KW1Fpbl06IFllcy46LSkNCg0KPj4gSG93ZXZlciBteSB1bmRlcnN0YW5kaW5n
IGlzIGltcGxvc2lvbiBzZWVtcyB0byBtZWFuIGZlZWRiYWNrDQo+PiBtZXNzYWdlcyBvdmVyd2hl
bG0gdGhlIG5ldHdvcmsgY2FwYWNpdHkuDQo+IA0KPiA9PiB0aGlzIGlzIHRoZSBkZWZpbml0aW9u
IG9mIGV4cGxvc2lvbi4NCg0KW1Fpbl06IHBsZWFzZSByZWZlciB0byBNYWdudXMncyBmZWVkYmFj
ayBvbiB0aGlzIHRocmVhZCBpbiBhIHNlcGFyYXRlIGVtYWlsLiANCg0KPiANCj4+ICBJZiB3ZSBj
aGFuZ2UgImltcGxvc2lvbiIgaW50byAiZXhwbG9zaW9uIiwgd2Ugc2VlbXMgdG8gY2hhbmdlIHRo
ZQ0KPj4gIG1lYW5pbmcgb2YgImZlZWRiYWNrIGltcGxvc2lvbiIsIHRoYXQgaXMgdG8gc2F5LCAi
ZmVlZGJhY2sNCj4+ICBleHBsb3Npb24gIiBtZWFucyBmZWVkYmFjayBtZXNzYWdlIGhhcyBhbHJl
YWR5IHBhcmFseXplZCB0aGUNCj4+ICBuZXR3b3JrLiBUaGUgTmV0d29yayBkaWVzIDotKS4gIEkg
YW0gYXdhcmUgdGhhdCBSRkM0NTg1IGFsc28gdXNlDQo+PiAgImZlZWRiYWNrIGltcGxvc2lvbiIu
IFNpbmNlIHRoaXMgZHJhZnQgcmVmZXJlbmNlcyBSRkM0NTg1LCBJc24ndA0KPj4gIGRyYWZ0LWll
dGYtYXZ0Y29yZS1mZWVkYmFjay1zdXByZXNzaW9uLXJ0cCBpbiBhY2NvcmRhbmNlIHdpdGgNCj4+
ICBSRkM0NTg1Pw0KPiANCj4gPT4geW91IGhhdmUgdGhlIGNob2ljZSBiZXR3ZWVuIHVzaW5nIHRo
ZSBjb3JyZWN0IHRlcm0gb3Iga2VlcGluZyB0aGUNCj4gd3JvbmcgdGVybSBiZWNhdXNlIHNvbWUg
ZGlkIHRoZSBlcnJvciBpbiByZWZlcmVuY2VkIGRvY3VtZW50cy4NCg0KW1Fpbl06IE9rYXkuDQoN
Cj4gWW91IGtub3cgbXkgb3Bpbmlvbi4NCg0KW1Fpbl06IFVuZGVyc3RhbmQgc3VjaCBhbWJpZ3Vp
dHkuDQoNCj4gDQo+IFJlZ2FyZHMNCj4gDQo+IEZyYW5jaXMuRHVwb250QGZkdXBvbnQuZnINCj4g
DQo+IFBTOiBwZXJoYXBzIHdlIHNob3VsZCBhc2sgdGhlIFJGQyBFZGl0b3IgdG8gcHJvZHVjZSBh
IGNvbGxlY3RpdmUNCj4gRXJyYXRhIHRvIGZpeCB0aGlzIG1pc3VzZSBvZiBpbXBsb3Npb24gZm9y
IGV4cGxvc2lvbj8=


From martin.thomson@gmail.com  Fri Apr 13 09:13:59 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 2A37821F8618 for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 09:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level: 
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[AWL=-0.350, 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 dd4PPNpDBsVp for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 09:13:58 -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 30E7121F8603 for <gen-art@ietf.org>; Fri, 13 Apr 2012 09:13:58 -0700 (PDT)
Received: by bkuw5 with SMTP id w5so3089643bku.31 for <gen-art@ietf.org>; Fri, 13 Apr 2012 09:13:57 -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=dXfIUspZXN6JNaaujNBqmmNcOGxiPwP44TDJ7u5zEk0=; b=jrnLZWzQtByp4QPJ7PgibJG02C8YCHxWZlhqSPy3FQnXFGABjuMAHOTra8XsxHB4xA pVEqFzCIr1B2C0R4kR/FAdiMHAQUM3cEJqPKcHAnrsJ0FH6ggt+WMh+A2zVd5a4ZvO/s kdy08YdNXkq5PLJLT8ZnUPxoEWId0LYelDwSoaknjFopXsf4F1027O/HQxvUaUbvQ/Pc SMsfs/h6eg7XaeOCR7acfD838mWR5rVI8lJm23wM5kPWtkT2Uwwt0VVfLFLJ0EIECg9U 6+2GI7mQqVVD3wKXR+5z9fLPup2r0PzpbJiBddlREMn2esT/xMNY7qLHbjRPwD7A12E8 UU8Q==
MIME-Version: 1.0
Received: by 10.204.154.28 with SMTP id m28mr625580bkw.102.1334333637241; Fri, 13 Apr 2012 09:13:57 -0700 (PDT)
Received: by 10.204.165.66 with HTTP; Fri, 13 Apr 2012 09:13:57 -0700 (PDT)
Date: Fri, 13 Apr 2012 09:13:57 -0700
Message-ID: <CABkgnnXEnqmOcszw4KcXOcs_Z-C+zwhtC2tpdr73YQqjQmX3ZQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: draft-ietf-marf-as.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART review: draft-ietf-marf-as-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Apr 2012 16:13:59 -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-marf-as-13
Reviewer: Martin Thomson
Review Date: 2012-04-12
IETF LC End Date:
IESG Telechat date: (if known)

Summary: This document is fit for publication, though some minor
issues might warrant further consideration.

Major issues: None

Minor issues:

Reading through, this doesn't smell very much like an applicability
statement at all.  It has the distinct odor of a profile, or a set of
implementation/deployment/operational guidelines.  That might just be
me.

Section 4.2 doesn't really contain enough information for me to
determine when I might want to ignore your SHOULD.

Section 6.1, point 1 cannot be an interoperability requirement if
there isn't a mechanism provided.  The text is perfectly clear, but I
can't implement anything here to address the "MUST".  The problem is
that the reports are unsolicited, and therefore an out-of-band
"session" has not been established between providers. (Is an abuse
report the in-band solution you are looking for?  Yes, Section 7,
point 2, I know...)

Section 6.3, point 1 has the same complaint for the "SHOULD", though
in this case the softness of the "SHOULD" makes this more tolerable.

Nits/editorial comments:

Expand on first use: MUA, SPF, DKIM.

Parentheses around references is excessive ([CITE]).

Section 5.2, point 2 is a bit of a truism...MUST support optional
fields being optional.  Is it really necessary?

Section 6.3, point 3, sentence 2: missing comma after "([RFC3912])"

Section 6.4, point 3, did not parse: "reports are generated with use
by recipients not using"

Section 6.5, point 3 could be made MUST NOT by saying "MUST NOT reject
non-ARF messages based solely on the format" or by adding other
qualifications to that effect.  Obviously this has to allow for local
policy that rejects messages on other criteria, but you can make a
requirement like this.

From msk@cloudmark.com  Fri Apr 13 12:14:26 2012
Return-Path: <msk@cloudmark.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 17CF921F87A2 for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 12:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 0zIsWXf1ZoM5 for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 12:14:25 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id 3D41C21F877B for <gen-art@ietf.org>; Fri, 13 Apr 2012 12:14:25 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.25]) by mail.cloudmark.com with bizsmtp id xXEJ1i0020ZaKgw01XEJjn; Fri, 13 Apr 2012 12:14:24 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=H85ZMpki c=1 sm=1 a=LdFkGDrDWH2mcjCZERnC4w==:17 a=LvckAehuu68A:10 a=7kMX6eKFbxAA:10 a=zutiEJmiVI4A:10 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=pGLkceISAAAA:8 a=48vgC7mUAAAA:8 a=aBl6_qVZLh-e_HCwMi4A:9 a=88_gob-PgkVewUbxR-kA:7 a=QEXdDO2ut3YA:10 a=MSl-tDqOz04A:10 a=lZB815dzVvQA:10 a=QQTW8CIwiUlVY4Xl:21 a=HANvhiNlQJPq0I6t:21 a=LdFkGDrDWH2mcjCZERnC4w==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas901.corp.cloudmark.com ([fe80::2524:76b6:a865:539c%10]) with mapi id 14.01.0355.002; Fri, 13 Apr 2012 12:14:18 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Martin Thomson <martin.thomson@gmail.com>, "draft-ietf-marf-as.all@tools.ietf.org" <draft-ietf-marf-as.all@tools.ietf.org>, "marf@ietf.org" <marf@ietf.org>
Thread-Topic: Gen-ART review: draft-ietf-marf-as-13
Thread-Index: AQHNGZB+7c4QMrJmK06xaah5486YRZaZGYxA
Date: Fri, 13 Apr 2012 19:14:17 +0000
Message-ID: <9452079D1A51524AA5749AD23E0039280F0958@exch-mbx901.corp.cloudmark.com>
References: <CABkgnnXEnqmOcszw4KcXOcs_Z-C+zwhtC2tpdr73YQqjQmX3ZQ@mail.gmail.com>
In-Reply-To: <CABkgnnXEnqmOcszw4KcXOcs_Z-C+zwhtC2tpdr73YQqjQmX3ZQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1334344464; bh=ixXgRY7oSk6nqmOc1NHXp241tkmZCEZH7zkWbnSSGFw=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=lNWQNy7EQwJ1jwDo1SIAoo850XX1HyhgijlqEvax5e0S2LGQ/qbr/F88LqM4ATli3 EfzT7cOPlefklMD0UM7Tz5UvzlhVAqxxNySI9hhaiKLVEZ1UPGCuvtkJVEZRWieWu3 oTtkOVhnP0ZCGFyWYavahNA3GWg2Mn/C3WOhReT8=
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review: draft-ietf-marf-as-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Apr 2012 19:14:26 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBNYXJ0aW4gVGhvbXNvbiBbbWFp
bHRvOm1hcnRpbi50aG9tc29uQGdtYWlsLmNvbV0NCj4gU2VudDogRnJpZGF5LCBBcHJpbCAxMywg
MjAxMiA5OjE0IEFNDQo+IFRvOiBkcmFmdC1pZXRmLW1hcmYtYXMuYWxsQHRvb2xzLmlldGYub3Jn
DQo+IENjOiBnZW4tYXJ0QGlldGYub3JnDQo+IFN1YmplY3Q6IEdlbi1BUlQgcmV2aWV3OiBkcmFm
dC1pZXRmLW1hcmYtYXMtMTMNCg0KSGkgTWFydGluLCB0aGFua3MgZm9yIHRoZSByZXZpZXcuDQoN
Cj4gTWlub3IgaXNzdWVzOg0KPiANCj4gUmVhZGluZyB0aHJvdWdoLCB0aGlzIGRvZXNuJ3Qgc21l
bGwgdmVyeSBtdWNoIGxpa2UgYW4gYXBwbGljYWJpbGl0eQ0KPiBzdGF0ZW1lbnQgYXQgYWxsLiAg
SXQgaGFzIHRoZSBkaXN0aW5jdCBvZG9yIG9mIGEgcHJvZmlsZSwgb3IgYSBzZXQgb2YNCj4gaW1w
bGVtZW50YXRpb24vZGVwbG95bWVudC9vcGVyYXRpb25hbCBndWlkZWxpbmVzLiAgVGhhdCBtaWdo
dCBqdXN0IGJlDQo+IG1lLg0KDQpJdCBpcyBhbiBBcHBsaWNhYmlsaXR5IFN0YXRlbWVudCBpbiB0
aGUgc2Vuc2Ugb2YgU2VjdGlvbiAzLjIgb2YgUkZDIDIwMjYuDQoNCj4gU2VjdGlvbiA0LjIgZG9l
c24ndCByZWFsbHkgY29udGFpbiBlbm91Z2ggaW5mb3JtYXRpb24gZm9yIG1lIHRvDQo+IGRldGVy
bWluZSB3aGVuIEkgbWlnaHQgd2FudCB0byBpZ25vcmUgeW91ciBTSE9VTEQuDQoNClNvbWUga2lu
ZCBvZiBvdXQtb2YtYmFuZCBrbm93bGVkZ2Ugb2YgYW4gb3ZlcnJpZGUgYWRkcmVzcywgb3IgbG9j
YWwgcG9saWN5LCBpcyB3aGF0IHdlIGhhdmUgaW4gbWluZCBoZXJlLiAgT2YgY291cnNlLCBzdWNo
IG91dC1vZi1iYW5kIGtub3dsZWRnZSBpcyBsaWtlbHkgYW4gaW1wbGljaXQgcGFydCBvZiB0aGUg
ZmVlZGJhY2sgc29saWNpdGF0aW9uIGFncmVlbWVudCBhbnl3YXksIHNvIHJlYWxseSBsb2NhbCBw
b2xpY3kgaXMgdGhlIG9ubHkgdGhpbmcgdGhhdCBtaWdodCBhcHBseS4gIFdlIGNhbiBtZW50aW9u
IHRoYXQgZXhwbGljaXRseS4NCg0KPiBTZWN0aW9uIDYuMSwgcG9pbnQgMSBjYW5ub3QgYmUgYW4g
aW50ZXJvcGVyYWJpbGl0eSByZXF1aXJlbWVudCBpZiB0aGVyZQ0KPiBpc24ndCBhIG1lY2hhbmlz
bSBwcm92aWRlZC4gIFRoZSB0ZXh0IGlzIHBlcmZlY3RseSBjbGVhciwgYnV0IEkgY2FuJ3QNCj4g
aW1wbGVtZW50IGFueXRoaW5nIGhlcmUgdG8gYWRkcmVzcyB0aGUgIk1VU1QiLiAgVGhlIHByb2Js
ZW0gaXMgdGhhdCB0aGUNCj4gcmVwb3J0cyBhcmUgdW5zb2xpY2l0ZWQsIGFuZCB0aGVyZWZvcmUg
YW4gb3V0LW9mLWJhbmQgInNlc3Npb24iIGhhcyBub3QNCj4gYmVlbiBlc3RhYmxpc2hlZCBiZXR3
ZWVuIHByb3ZpZGVycy4gKElzIGFuIGFidXNlIHJlcG9ydCB0aGUgaW4tYmFuZA0KPiBzb2x1dGlv
biB5b3UgYXJlIGxvb2tpbmcgZm9yPyAgWWVzLCBTZWN0aW9uIDcsIHBvaW50IDIsIEkga25vdy4u
LikNCg0KRXhpc3RpbmcgaW1wbGVtZW50YXRpb25zIGdlbmVyYWxseSBzdXBwb3J0IHRoaXMgY2Fw
YWJpbGl0eSwgYnV0IHRoZXkgYWxsIGhhdmUgZGlmZmVyZW50IHdheXMgb2YgZG9pbmcgc28uICBU
aHVzLCB0aGVyZSdzIChjdXJyZW50bHkpIG5vIHN0YW5kYXJkIHdheSB0byBkbyBpdC4gIE91ciBB
RHMgdGh1cyBzdWdnZXN0ZWQgdGhlIHRleHQgdGhhdCdzIHRoZXJlLg0KDQo+IFNlY3Rpb24gNi4z
LCBwb2ludCAxIGhhcyB0aGUgc2FtZSBjb21wbGFpbnQgZm9yIHRoZSAiU0hPVUxEIiwgdGhvdWdo
IGluDQo+IHRoaXMgY2FzZSB0aGUgc29mdG5lc3Mgb2YgdGhlICJTSE9VTEQiIG1ha2VzIHRoaXMg
bW9yZSB0b2xlcmFibGUuDQoNClRoZSBjaG9pY2UgdG8gZGV2aWF0ZSBtZWFucyB0aGUgYmVuZWZp
dHMgZGVzY3JpYmVkIGxhdGVyIGluIHRoYXQgcG9pbnQncyB0ZXh0IGFyZSBsb3N0LiAgVGhhdCdz
IHRoZSB0cmFkZW9mZi4NCg0KPiBOaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCj4gDQo+IEV4cGFu
ZCBvbiBmaXJzdCB1c2U6IE1VQSwgU1BGLCBES0lNLg0KDQpPSy4NCg0KPiBQYXJlbnRoZXNlcyBh
cm91bmQgcmVmZXJlbmNlcyBpcyBleGNlc3NpdmUgKFtDSVRFXSkuDQoNClN0eWxpc3RpYyBwcmVm
ZXJlbmNlLCBJIHRoaW5rLiAgOi0pDQoNCj4gU2VjdGlvbiA1LjIsIHBvaW50IDIgaXMgYSBiaXQg
b2YgYSB0cnVpc20uLi5NVVNUIHN1cHBvcnQgb3B0aW9uYWwNCj4gZmllbGRzIGJlaW5nIG9wdGlv
bmFsLiAgSXMgaXQgcmVhbGx5IG5lY2Vzc2FyeT8NCg0KSG0sIHRydWUuICBJJ2xsIGhhdmUgdG8g
bG9vayBhdCBob3cgdGhhdCB0ZXh0IGV2b2x2ZWQgYW5kIGZpZ3VyZSBvdXQgaWYgaXQgbmVlZHMg
cmV3b3JkaW5nIG9yIGNhbiBqdXN0IGJlIGRyb3BwZWQuDQoNCj4gU2VjdGlvbiA2LjMsIHBvaW50
IDMsIHNlbnRlbmNlIDI6IG1pc3NpbmcgY29tbWEgYWZ0ZXIgIihbUkZDMzkxMl0pIg0KDQpXaHk/
ICBJdCBkb2Vzbid0IHBhcnNlIHByb3Blcmx5IHdpdGggdGhhdCBjaGFuZ2UuDQoNCj4gU2VjdGlv
biA2LjQsIHBvaW50IDMsIGRpZCBub3QgcGFyc2U6ICJyZXBvcnRzIGFyZSBnZW5lcmF0ZWQgd2l0
aCB1c2UgYnkNCj4gcmVjaXBpZW50cyBub3QgdXNpbmciDQoNCiJ3aXRoIC4uLiBpbiBtaW5kIiBp
cyB0aGUgY29uc3RydWN0LCBidXQgdGhleSBhcmUga2luZCBvZiBmYXIgYXBhcnQuICBXaWxsIHJl
d29yZC4NCg0KPiBTZWN0aW9uIDYuNSwgcG9pbnQgMyBjb3VsZCBiZSBtYWRlIE1VU1QgTk9UIGJ5
IHNheWluZyAiTVVTVCBOT1QgcmVqZWN0DQo+IG5vbi1BUkYgbWVzc2FnZXMgYmFzZWQgc29sZWx5
IG9uIHRoZSBmb3JtYXQiIG9yIGJ5IGFkZGluZyBvdGhlcg0KPiBxdWFsaWZpY2F0aW9ucyB0byB0
aGF0IGVmZmVjdC4gIE9idmlvdXNseSB0aGlzIGhhcyB0byBhbGxvdyBmb3IgbG9jYWwNCj4gcG9s
aWN5IHRoYXQgcmVqZWN0cyBtZXNzYWdlcyBvbiBvdGhlciBjcml0ZXJpYSwgYnV0IHlvdSBjYW4g
bWFrZSBhDQo+IHJlcXVpcmVtZW50IGxpa2UgdGhpcy4NCg0KSSB0aGluayBhIG1peCBvZiB0aGUg
dHdvIG1ha2VzIHNlbnNlOiBMZWF2ZSBpdCBhIFNIT1VMRCBOT1QsIHVzZSB5b3VyIHdvcmRpbmcg
b3RoZXJ3aXNlLCBhbmQgdGhlbiBkZXNjcmliZSB2YWxpZCBkZXZpYXRpb24gY3JpdGVyaWEgYXMg
eW91J3ZlIGRvbmUuDQoNClRoYW5rczsgTEMgZW5kcyA0LzI0LCB3aWxsIHBvc3QgYSByZXZpc2lv
biBiZXR3ZWVuIHRoYXQgYW5kIHRoZSB0ZWxlY2hhdC4NCg0KLU1TSw0KDQo=

From barryleiba.mailing.lists@gmail.com  Fri Apr 13 14:06:46 2012
Return-Path: <barryleiba.mailing.lists@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 1BA0011E80FD; Fri, 13 Apr 2012 14:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.808
X-Spam-Level: 
X-Spam-Status: No, score=-102.808 tagged_above=-999 required=5 tests=[AWL=0.169, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 1262gd1AHtzB; Fri, 13 Apr 2012 14:06:45 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8BB11E80E4; Fri, 13 Apr 2012 14:05:46 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so2131211ghb.31 for <multiple recipients>; Fri, 13 Apr 2012 14:05:45 -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=ErQ/XrLI8AYnbwhhVW3jgJj5TMHmvNTbaAiqxrK6xU4=; b=gF7KnSNAsytTuTkpgQ2PXhZaT7GR3RLxMd7UkIF4a3FcKqFJBMGSFuY76TevGJ+Ifl BF7DFkUCZ3DiIKQS9YoMNN4ciz3vbUjgjZmyISxw4TvswYR5I/VTrW/g3yUfL36r4EQO ues9c5U9giC5QIGnrn/yJZeh0FoR/uotQ0IE9cn4P0Xwwv9tM83ciuGNac5SDl2I9QpF Abm1PzomdURyqA9WGAweB7C9oYjT11WKWzGuhnIP1HJMXDQSOIg8s/l4VVOb+NJnu6N+ H0+72pujmUgk/8/JR9ZxS6l2jpzCD3yfpf+e/XHhyf/cixHkrJ9OlziYxUJd4sGvhNiu C49w==
MIME-Version: 1.0
Received: by 10.100.233.35 with SMTP id f35mr169267anh.37.1334351145863; Fri, 13 Apr 2012 14:05:45 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.146.230.1 with HTTP; Fri, 13 Apr 2012 14:05:45 -0700 (PDT)
In-Reply-To: <9452079D1A51524AA5749AD23E0039280F0958@exch-mbx901.corp.cloudmark.com>
References: <CABkgnnXEnqmOcszw4KcXOcs_Z-C+zwhtC2tpdr73YQqjQmX3ZQ@mail.gmail.com> <9452079D1A51524AA5749AD23E0039280F0958@exch-mbx901.corp.cloudmark.com>
Date: Fri, 13 Apr 2012 17:05:45 -0400
X-Google-Sender-Auth: 7lyvmUc_jB9HRkd26nAQuk8EMO0
Message-ID: <CAC4RtVAkUQEQBP8ZMNszOUsH7pMwYfyUZppMV_sr3KmDg2ZRCg@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "marf@ietf.org" <marf@ietf.org>, "draft-ietf-marf-as.all@tools.ietf.org" <draft-ietf-marf-as.all@tools.ietf.org>
Subject: Re: [Gen-art] [marf] Gen-ART review: draft-ietf-marf-as-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Apr 2012 21:06:46 -0000

Just one comment here; leaving the rest for Murray:

Martin:
>> Reading through, this doesn't smell very much like an applicability
>> statement at all. =A0It has the distinct odor of a profile, or a set of
>> implementation/deployment/operational guidelines. =A0That might just be
>> me.

Murray:
> It is an Applicability Statement in the sense of Section 3.2 of RFC 2026.

Indeed, and the problem is that we've used stand-along Applicability
Statements so infrequently in recent years that we don't seem to know
what they are any more.  Worse, we've often started to call them
"profiles".

I think an Applicability Statement is a normative document that does
not in itself define a protocol, but specifies how to *apply* one or
more profiles to solve a particular (set of) problem(s) or to perform
a particular (set of) function(s).  It might well be that we should
start calling many of the "profiles" that we do "Applicability
Statements" instead.

The advantage here is that the AS is a standards-track document, and
will progress along the standards track just as a Technical
Specification would.  Making it Information loses that aspect.

Barry, document shepherd

From martin.thomson@gmail.com  Sat Apr 14 05:58:44 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 EC20B21F84F8; Sat, 14 Apr 2012 05:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.917
X-Spam-Level: 
X-Spam-Status: No, score=-3.917 tagged_above=-999 required=5 tests=[AWL=-0.318, 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 n-fSUiz5D6nm; Sat, 14 Apr 2012 05:58:44 -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 0CE2E21F84EF; Sat, 14 Apr 2012 05:58:43 -0700 (PDT)
Received: by bkuw5 with SMTP id w5so3598810bku.31 for <multiple recipients>; Sat, 14 Apr 2012 05:58:43 -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:content-transfer-encoding; bh=KzSf6gwAhdT8KZ/dBLe6kdAP9qOlRvgaFfcFL5KW32k=; b=AvNnzliwGMAO7aogjOfFAUueImvMttAhtaQtSPabwY+Ar1wCiQtv+8gFgoPy+sVtVS gFZPG/P3SdmlEPve6ORL718wOpS7zpk1lm7B7/bq6dIGu9xIczdl1hWmLqWQjevWNlYP APEi82Z0/a8NoD4xpeKhLaDkOIrmlbMbG46emu179wO+Oj/3bh3ME1kbntEZxn8kkxeh MGKfcqsYwhCsY9tc+/z89U+nxA3u9wiKW6v5hAHoaiCYjLQWtd4xAXcGo/fPi3qn19n2 C13q1HAkOd6sANzc/JE87MVIx1NmPH1ivdnTT9KFXSPkuCrggYjan+OitHM2Fa756h7i 9tUw==
MIME-Version: 1.0
Received: by 10.204.128.65 with SMTP id j1mr1544414bks.74.1334408323107; Sat, 14 Apr 2012 05:58:43 -0700 (PDT)
Received: by 10.204.165.66 with HTTP; Sat, 14 Apr 2012 05:58:43 -0700 (PDT)
In-Reply-To: <CAC4RtVAkUQEQBP8ZMNszOUsH7pMwYfyUZppMV_sr3KmDg2ZRCg@mail.gmail.com>
References: <CABkgnnXEnqmOcszw4KcXOcs_Z-C+zwhtC2tpdr73YQqjQmX3ZQ@mail.gmail.com> <9452079D1A51524AA5749AD23E0039280F0958@exch-mbx901.corp.cloudmark.com> <CAC4RtVAkUQEQBP8ZMNszOUsH7pMwYfyUZppMV_sr3KmDg2ZRCg@mail.gmail.com>
Date: Sat, 14 Apr 2012 05:58:43 -0700
Message-ID: <CABkgnnU=rbb3BjN0k6Wo3dzxC2YCgLiuTjvw8dzec6OR1X5vJg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-marf-as.all@tools.ietf.org" <draft-ietf-marf-as.all@tools.ietf.org>, "marf@ietf.org" <marf@ietf.org>, "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: [Gen-art] [marf] Gen-ART review: draft-ietf-marf-as-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: Sat, 14 Apr 2012 12:58:45 -0000

On 13 April 2012 14:05, Barry Leiba <barryleiba@computer.org> wrote:
> The advantage here is that the AS is a standards-track document, and
> will progress along the standards track just as a Technical
> Specification would. =C2=A0Making it Information loses that aspect.

It wouldn't make sense for this to be made informational.  There are
too many all-caps words.

From martin.thomson@gmail.com  Sat Apr 14 06:16:34 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 77BC821F861F; Sat, 14 Apr 2012 06:16:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.891
X-Spam-Level: 
X-Spam-Status: No, score=-3.891 tagged_above=-999 required=5 tests=[AWL=-0.292, 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 xwXgH4sxrURf; Sat, 14 Apr 2012 06:16:33 -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 2A36821F8611; Sat, 14 Apr 2012 06:16:33 -0700 (PDT)
Received: by bkuw5 with SMTP id w5so3605523bku.31 for <multiple recipients>; Sat, 14 Apr 2012 06:16:26 -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:content-transfer-encoding; bh=JF5mK4RNny8zvkiJ3+m9QVTq1vXCNBcetR+5dGXXSJs=; b=gS1NKOCL+0UP0ybbwCL36DsITv8qlOEW1Eua4J9i0FftTKoXpectlZCanHE68YtgSl 2Rbro07/912mvevmJ26WVraLrfAojVFRGTv8bLZxKbKe0D9G1CIUIBpsRam4mNPsb/6e 9FPybOJoe8Nrg2MJ3taYvcuUhGahGQUDwzZIZP0MGxQLNt+wlMukkflF8GBxQKt9XQ9M fH9I8tilnV0Te6RlYyGYiNNXlPI6vK7yTgP1/NqdKWQxZBmkDmjicM5n064wsEnt1WDd Nv7LZi4QX+MMa+DjmwtmnHBxGsXg0fDrPcJWmvrQxRjrifcKDPmermXg149YidaC8AMe 5EOg==
MIME-Version: 1.0
Received: by 10.204.156.79 with SMTP id v15mr1551718bkw.37.1334409386085; Sat, 14 Apr 2012 06:16:26 -0700 (PDT)
Received: by 10.204.165.66 with HTTP; Sat, 14 Apr 2012 06:16:26 -0700 (PDT)
In-Reply-To: <9452079D1A51524AA5749AD23E0039280F0958@exch-mbx901.corp.cloudmark.com>
References: <CABkgnnXEnqmOcszw4KcXOcs_Z-C+zwhtC2tpdr73YQqjQmX3ZQ@mail.gmail.com> <9452079D1A51524AA5749AD23E0039280F0958@exch-mbx901.corp.cloudmark.com>
Date: Sat, 14 Apr 2012 06:16:26 -0700
Message-ID: <CABkgnnVW4gk51__4gTR_C9eJG5OpaN4PiDr7Rj+tw=bonqgJ_A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "marf@ietf.org" <marf@ietf.org>, "draft-ietf-marf-as.all@tools.ietf.org" <draft-ietf-marf-as.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review: draft-ietf-marf-as-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: Sat, 14 Apr 2012 13:16:34 -0000

Look, this really doesn't bother me that much.  But I can't even
imagine what a sensible implementation would do for these two points.
I don't like 2119 language that I can't see how to comply with.

Maybe I'm just not imaginative enough.

On 13 April 2012 12:14, Murray S. Kucherawy <msk@cloudmark.com> wrote:
>> Section 6.1, point 1 cannot be an interoperability requirement if there
>> isn't a mechanism provided.
> Existing implementations generally support this capability, but they all =
have different ways of doing so. =C2=A0Thus, there's (currently) no standar=
d way to do it. =C2=A0Our ADs thus suggested the text that's there.

It's the unsolicited case that bothers me here.  Is there some sort of
general advice that can be given on how to implement this for an
unsolicited report? Or are these existing implementations so radically
different that is tricky?  (That would be interesting in and of
itself.)

>> Section 6.3, point 1 has the same complaint for the "SHOULD", though in
>> this case the softness of the "SHOULD" makes this more tolerable.
>
> The choice to deviate means the benefits described later in that point's =
text are lost. =C2=A0That's the tradeoff.

Again, I'm less concerned with the why, but the how.

--Martin

From fluffy@iii.ca  Wed Apr 18 11:40:52 2012
Return-Path: <fluffy@iii.ca>
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 AC91D21F84FA; Wed, 18 Apr 2012 11:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 F2AIUUFAFLS3; Wed, 18 Apr 2012 11:40:52 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id D3E0821F84EB; Wed, 18 Apr 2012 11:40:51 -0700 (PDT)
Received: from [192.168.4.100] (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id BBA5B22E25D; Wed, 18 Apr 2012 14:40:44 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <78A0D3BA-5EFE-4AD7-ACD6-56196CB588CF@sensinode.com>
Date: Wed, 18 Apr 2012 12:40:43 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <0EAC1438-90B0-459D-8A7B-1C54683E1C0C@iii.ca>
References: <4F3D931C.1000101@nostrum.com> <4F3FFB16.6030502@joelhalpern.com> <78A0D3BA-5EFE-4AD7-ACD6-56196CB588CF@sensinode.com>
To: Zach Shelby <zach@sensinode.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Wed, 18 Apr 2012 11:41:47 -0700
Cc: gen-art@ietf.org, core WG <core@ietf.org>
Subject: Re: [Gen-art] [core]  Review: draft-ietf-core-link-format-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 18:40:52 -0000

On Mar 8, 2012, at 5:55 AM, Zach Shelby wrote:

>>=20
>> Major issues:
>>   What is the registration / collision avoidance strategy for =
resource type (rt) and interface description (if) values?  They are both =
defined as opaque strings which can happen to be URIs.  So there seems =
to be potential for collision.
>=20
> There is definitely a possibility for collision for those two =
attributes, especially as there will be a mix of specifications that =
define specific values to be used, and developers using their own =
values. Currently while those are being defined in CoRE drafts we can =
avoid collisions, but when other WGs or SDOs start defining them...
>=20
> We have deliberated on the idea of defining registries for rt=3D and =
if=3D values, but it has not been clear if that should be done in this =
document. Recently several CoRE drafts have been written that do specify =
well-known values for those fields, so it starts to become obvious that =
those registries would be useful. If I understand right, your =
recommendation would be that we define those registries in the IANA =
section of this document? I would be in favor of doing that.

Where are we on resolving topic? This is closely linked with the =
registry proposed in senml.=20




From zach@sensinode.com  Wed Apr 18 13:06:33 2012
Return-Path: <zach@sensinode.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 B0D1D21F8460; Wed, 18 Apr 2012 13:06:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  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 SO8pEaxitGMU; Wed, 18 Apr 2012 13:06:28 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 8649121F8462; Wed, 18 Apr 2012 13:06:28 -0700 (PDT)
Received: from [192.168.1.102] (188-67-41-63.bb.dnainternet.fi [188.67.41.63]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id q3IK6Nit008913; Wed, 18 Apr 2012 23:06:24 +0300
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <0EAC1438-90B0-459D-8A7B-1C54683E1C0C@iii.ca>
Date: Wed, 18 Apr 2012 23:06:23 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <19A8C610-C350-44E1-8DCA-275FF3BD19D1@sensinode.com>
References: <4F3D931C.1000101@nostrum.com> <4F3FFB16.6030502@joelhalpern.com> <78A0D3BA-5EFE-4AD7-ACD6-56196CB588CF@sensinode.com> <0EAC1438-90B0-459D-8A7B-1C54683E1C0C@iii.ca>
To: Cullen Jennings <fluffy@iii.ca>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, core WG <core@ietf.org>
Subject: Re: [Gen-art] [core]  Review: draft-ietf-core-link-format-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2012 20:06:34 -0000

On Apr 18, 2012, at 9:40 PM, Cullen Jennings wrote:

>=20
> On Mar 8, 2012, at 5:55 AM, Zach Shelby wrote:
>=20
>>>=20
>>> Major issues:
>>>  What is the registration / collision avoidance strategy for =
resource type (rt) and interface description (if) values?  They are both =
defined as opaque strings which can happen to be URIs.  So there seems =
to be potential for collision.
>>=20
>> There is definitely a possibility for collision for those two =
attributes, especially as there will be a mix of specifications that =
define specific values to be used, and developers using their own =
values. Currently while those are being defined in CoRE drafts we can =
avoid collisions, but when other WGs or SDOs start defining them...
>>=20
>> We have deliberated on the idea of defining registries for rt=3D and =
if=3D values, but it has not been clear if that should be done in this =
document. Recently several CoRE drafts have been written that do specify =
well-known values for those fields, so it starts to become obvious that =
those registries would be useful. If I understand right, your =
recommendation would be that we define those registries in the IANA =
section of this document? I would be in favor of doing that.
>=20
> Where are we on resolving topic? This is closely linked with the =
registry proposed in senml.=20

Yes, it is being resolved in Ticket #195. I am adding both registries =
following the same style as the relation registry in RFC5988.=20

http://trac.tools.ietf.org/wg/core/trac/ticket/195

The only action point right now is for me to update the draft closing =
this and the other tickets.

Zach

--=20
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com
http://zachshelby.org  - My blog "On the Internet of Things"
http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297


From mahoney@nostrum.com  Thu Apr 19 15:09:34 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 0C71B11E80D7 for <gen-art@ietfa.amsl.com>; Thu, 19 Apr 2012 15:09:34 -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 gbdV67tJa8ri for <gen-art@ietfa.amsl.com>; Thu, 19 Apr 2012 15:09:33 -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 6ADBA11E80D2 for <gen-art@ietf.org>; Thu, 19 Apr 2012 15:09:30 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-40-17.dllstx.fios.verizon.net [71.170.40.17]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q3JM9TGT055789 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 19 Apr 2012 17:09:29 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4F908D19.6010805@nostrum.com>
Date: Thu, 19 Apr 2012 17:09:29 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
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: 71.170.40.17 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-04-19
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, 19 Apr 2012 22:09:34 -0000

Hi all,

The following reviewers have assignments:


Reviewer               LC end       Draft

Ben Campbell           2012-04-30  draft-ietf-pwe3-static-pw-status-10

Richard Barnes         2012-05-02  draft-ietf-appsawg-about-uri-scheme-04

Roni Even              2012-05-02  draft-ietf-mboned-mcaddrdoc-03

Suresh Krishnan        2012-05-02  
draft-ietf-mboned-64-multicast-address-format-01



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

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


The standard template is included below.

Thanks,

Jean

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

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

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

Document:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From mahoney@nostrum.com  Thu Apr 19 15:10:10 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 3434421F85A4 for <gen-art@ietfa.amsl.com>; Thu, 19 Apr 2012 15:10:10 -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 KkSr8y2Z9kOa for <gen-art@ietfa.amsl.com>; Thu, 19 Apr 2012 15:10:09 -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 7F1D821F85A2 for <gen-art@ietf.org>; Thu, 19 Apr 2012 15:10:09 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-40-17.dllstx.fios.verizon.net [71.170.40.17]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q3JMA7G3056103 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 19 Apr 2012 17:10:08 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4F908D3F.7070507@nostrum.com>
Date: Thu, 19 Apr 2012 17:10:07 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
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: 71.170.40.17 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-04-26 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, 19 Apr 2012 22:10:10 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft

Alexey Melnikov        2012-04-03  draft-ietf-sipcore-rfc3265bis-08

Christer Holmberg      2012-04-08  draft-ietf-krb-wg-des-die-die-die-04 *

Francis Dupont         2012-04-12  draft-ietf-emu-chbind-14 *

Kathleen Moriarty      2012-04-13  draft-ietf-appsawg-greylisting-07
Kathleen Moriarty      2012-03-20  draft-ietf-fecframe-raptor-10 *

Mary Barnes            2012-04-20  draft-ietf-pkix-pubkey-caps-04

Martin Thomson         2012-04-24  draft-ietf-marf-as-13 *

Peter McCann           2012-04-18  draft-templin-aero-10
Peter McCann           2012-03-30  
draft-ietf-dhc-dhcpv6-redundancy-consider-02
Peter McCann           2012-04-10  draft-ietf-kitten-gssapi-naming-exts-14
Peter McCann           2011-06-15  draft-ietf-ipfix-psamp-mib-04
Peter McCann           2012-04-16  draft-dbider-sha2-mac-for-ssh-05

Suresh Krishnan        2012-04-03  draft-ietf-geopriv-policy-25

Wassim Haddad          2012-03-15  draft-ietf-appsawg-xdash-05
Wassim Haddad          2012-04-18  draft-ietf-ecrit-lost-sync-17

* Draft already reviewed


Spreadsheets have been updated:
http://wiki.tools.ietf.org/dav/genart/gen-art.html
http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html

I've also updated the review tool:
http://art.tools.ietf.org/tools/art/genart/

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 miguel.a.garcia@ericsson.com  Mon Apr 23 06:52:34 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 7464D21F864C for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 06:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.212
X-Spam-Level: 
X-Spam-Status: No, score=-6.212 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54bR1eG8ehhD for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 06:52:33 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 842D721F864A for <gen-art@ietf.org>; Mon, 23 Apr 2012 06:52:33 -0700 (PDT)
X-AuditID: c1b4fb25-b7b18ae000000dce-2e-4f955ea09c38
Authentication-Results: mailgw2.ericsson.se x-tls.subject="/CN=esessmw0184"; auth=fail (cipher=AES128-SHA)
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client CN "esessmw0184", Issuer "esessmw0184" (not verified)) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 62.C5.03534.0AE559F4; Mon, 23 Apr 2012 15:52:32 +0200 (CEST)
Received: from [159.107.24.202] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.213.0; Mon, 23 Apr 2012 15:52:31 +0200
Message-ID: <4F955E9E.1000601@ericsson.com>
Date: Mon, 23 Apr 2012 15:52:30 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>, jakob@kirei.se
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: Ondrej Sury <ondrej.sury@nic.cz>, Warren Kumari <warren@kumari.net>, General Area Review Team <gen-art@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: [Gen-art] Gen-ART review of draft-ietf-dane-protocol-19.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, 23 Apr 2012 13:52:34 -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-dane-protocol-19.txt
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 23-Apr-2012
IETF LC End Date: 25-Apr-2012
IESG Telechat date:

Summary: The document is ready for publication as a standards track RFC.

Major issues: none

Minor issues: none

Nits/editorial comments:

The document is well written and I have no problems with it. Perhaps the 
IANA Considerations section can be improved by having clear instructions 
to IANA, especially on the registry they need to operate.

For example, take a look at the text on Section 7.1:

"This document uses a new DNS RR type, TLSA, whose value is TBD. "

I have a problem with the word "uses". It is not clear if IANA has to 
allocate a value or the document uses an existing value. Assuming IANA 
has to allocate an existing value, please indicate the registry where 
that value should be allocated. For example, the text could say:

This document request IANA to allocate a new "TLSA" value in the Resource 
Record (RR) TYPEs subregistry of the Domain Name System
(DNS) Parameters registry:

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

From kathleen.moriarty@emc.com  Mon Apr 23 09:59:58 2012
Return-Path: <kathleen.moriarty@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 489E821F869E; Mon, 23 Apr 2012 09:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.506
X-Spam-Level: 
X-Spam-Status: No, score=-10.506 tagged_above=-999 required=5 tests=[AWL=0.093, 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 fozxY-PVZ7RN; Mon, 23 Apr 2012 09:59:56 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5CE3921F8681; Mon, 23 Apr 2012 09:59:56 -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 q3NGxTRD009152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Apr 2012 12:59:48 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 23 Apr 2012 12:59:12 -0400
Received: from mxhub33.corp.emc.com (mxhub33.corp.emc.com [10.254.93.81]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q3NGxCeU025570; Mon, 23 Apr 2012 12:59:12 -0400
Received: from mx06a.corp.emc.com ([169.254.1.106]) by mxhub33.corp.emc.com ([::1]) with mapi; Mon, 23 Apr 2012 12:59:11 -0400
From: <kathleen.moriarty@emc.com>
To: <draft-ietf-appsawg-greylisting.all@tools.ietf.org>, <iesg@ietf.org>, <gen-art@ietf.org>
Date: Mon, 23 Apr 2012 12:59:10 -0400
Thread-Topic: Gen-Art review of draft-ietf-appsawg-greylisting
Thread-Index: Ac0hcmcyQR3NBVo/Rl6IFM4VkVIGNw==
Message-ID: <AE31510960917D478171C79369B660FA0E7CB761E7@MX06A.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: dcrocker@bbiw.net, msk@cloudmark.com
Subject: [Gen-art] Gen-Art review of draft-ietf-appsawg-greylisting
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, 23 Apr 2012 16:59:58 -0000

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

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

Document: draft-ietf-appsawg-greylisting
Reviewer: Kathleen Moriarty
Review Date: 23 April
IETF LC End Date:
IESG Telechat date: (if known)

Summary:  Ready with nits.
This memo describes the art of email greylisting, the practice of
   providing temporarily degraded service to unknown email clients as an
   anti-abuse mechanism.

Major issues:

Minor issues:

Nits/editorial comments:
Introduction: First sentence:  The word 'differential' should be 'different=
' unless you change the sentence structure.  It could be that there is a di=
fferential between services.
Second sentence:  Change provider to providing
Change from: "In some cases an actor does not have a known reputation; this=
 can justify providing degraded service, until there is a basis for provide=
r better service."
To: "In some cases an actor does not have a known reputation;
   this can justify providing degraded service, until there is a basis
   for providing better service."

Section 2.1: The double dashes should be parentheses instead -- -- replaced=
 by ()
Section 3, third paragraph, last sentence: add a comma:
From: To the greylisting
   implementation such clients are once again unknown, and they will
   once again be subjected to the delay.
To: To the greylisting
   Implementation, such clients are once again unknown, and they will
   once again be subjected to the delay.

Section 3, fourth paragraph, second sentence: remove the comma:
From: It has to be
   large enough to keep the necessary history, and fast enough to avoid
   excessive inefficiencies in the server's operations.
To: It has to be
   large enough to keep the necessary history and fast enough to avoid
   excessive inefficiencies in the server's operations.

Section 3, fifth paragraph, second to last sentence: remove "the," and "suc=
h"
From: Experience suggests that
   the, the vast majority of mail comes from places on such a developed
   exception list, so after a training period, only a small proportion
   of mail is actually affected.
To: Experience suggests that
   the vast majority of mail comes from places on a developed
   exception list, so after a training period, only a small proportion
   of mail is actually affected.

Section 4.1: second to last paragraph: remove unnecessary comma:
From: Other side effects include out-of-order delivery of related,
   sequenced messages.
To: Other side effects include out-of-order delivery of related
   sequenced messages.

Section 4.2: Second paragraph:  The commas can be removed as only two items=
 are joined in the list.  When you have three or more, a comma is used.



From mary.ietf.barnes@gmail.com  Mon Apr 23 10:48:55 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 4979C21F873C for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 10:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.414
X-Spam-Level: 
X-Spam-Status: No, score=-102.414 tagged_above=-999 required=5 tests=[AWL=-1.116, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 qhLKfmAzVvW1 for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 10:48:54 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 648E421F8721 for <gen-art@ietf.org>; Mon, 23 Apr 2012 10:48:54 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so5186913vcb.31 for <gen-art@ietf.org>; Mon, 23 Apr 2012 10:48:54 -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=epDR7nlYMghLmse7rK3ZPskG1jwrnZSxrZMehlomguQ=; b=ss/72izvgI360XZeXys/zY+QX5ASMrN6TgjQ53o2IYaVDHDP+Eo9uRLGAqvNgfzywr fHvkp3T0MNCLFET5A7xUxq0H368/KnV7GJrKCOU3qY1ghS2ioHbGIT1ayXdBMgSacL3y Uoa72rpauX3U45NVIoykouB70vZE2CveENNmnDnW2uvCT0P6/pIKJfgKhjtD/RYSs9el 0rpfa1Ns7gBb4SHpO5KwEXhO6q7o5sGWZcLusjbHmt3lJlbDc7fEZz7+fHV9xbVAWe0w lO7dTFlganRdbsYTncQONPr7llxcCuQDGZrumnB/FJmYO6Nn9xX1Ofu5QtO0rY9L0GUF iMuQ==
MIME-Version: 1.0
Received: by 10.52.28.200 with SMTP id d8mr6135334vdh.38.1335203333916; Mon, 23 Apr 2012 10:48:53 -0700 (PDT)
Received: by 10.52.68.145 with HTTP; Mon, 23 Apr 2012 10:48:53 -0700 (PDT)
Date: Mon, 23 Apr 2012 12:48:53 -0500
Message-ID: <CAHBDyN4Fkt45-ikM9twDkyt7vK9fYb+gRPUqMir8AnuUtqS75Q@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: draft-ietf-pkix-pubkey-caps.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=20cf3079bc9e6bc77704be5c40aa
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-ART Review: draft-ietf-pkix-pubkey-caps-04.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, 23 Apr 2012 17:48:55 -0000

--20cf3079bc9e6bc77704be5c40aa
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

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-pkix-pubkey-caps-04.txt
Reviewer:  Mary Barnes
Review Date:  23 April 2012
IETF LC Date: 20 April 2012
IESG Telechat Date: 26 April 2012


Summary:  Almost ready (nits & minor issues).

Comments: There are quite a number of editorial nits, and a couple cases
where those result in lack of clarity, thus minor issues.  I am also
assuming that someone has validated the ASN.1 notation.

Minor Issues:
--------------
Section 1:
- 2nd paragraph:
 -- last sentence.  The phrase "most just consisted" in the following
sentence is missing an object - most what?
   This was especially easy since most just
   consisted of the object identifier for the algorithm.
I think based on the context that it should be written as
"most values", but it's not entirely clear to me, or perhaps it should be
"most parameters".

- 3rd paragraph:
  -- RFC 2119 language is used - "MUST NOT", however, there is no reference
to RFC 2119 language, which is fine given this is an informational
document.  It would seem that should be written lower case, in particular
given this is an introduction, which in general shouldn't include normative
language.

Section 4.2 & 4.3:
- there's a "(id-??)" in these two sections.  Is that intentional or should
that be referring to an explicit existing object identifier?

- There seems to be typos in the names of the ASN.1 elements that are being
defined:
  -- scap-ec-dh:  Shouldn't this be scap-pk-ecDH or am I just not
understanding the notation here?
 -- scap-ec-MQV: Shouldn't this be scap-pk-ecMQV?


Nits:
-----
Section 1:
- 2nd paragraph:
  -- 1st sentence:  "senders" -> "sender's"
  -- 5th sentence:  "=85were ever use." -> "=85were ever used."

Section 1.1:
- 1st paragraph after description fields:
  "The square brackets defined optional =85" ->  "The square brackets defin=
e
optional=85"

Section 2.2:
- 1st paragraph, last sentence: there's a stray "s" in the sentence after
"location"

Section 4.1:
- 1st paragraph, 1st sentence: "All most" -> "Almost"

Section 5:
- title: "RSASSA-PSS" ->  "RSA-SSA-PSS"
- second paragraph: there's inconsistent use of tense in these sentences.
 I would suggest changing"
  --  "it is always placed" -> "it was always placed"
  --  "meant that one can place" to "meant that one could place"

- last paragraph:  "=85the assumption that entire matrix=85" -> ""=85the
assumption that the entire matrix=85"

Section 6:
- 1st paragraph: "=85that need to be taking into account=85" ->  "=85that n=
eed to
be taken into account=85"

- 5th paragraph:  I don't find the first sentence helpful. I would find it
much easier to read if the 4th and 5th paragraphs were combined and the
first sentence of the 5th removed entirely and reword the 2nd sentence of
the 5th as:
"However, passing too much information=85"

--20cf3079bc9e6bc77704be5c40aa
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div><br></div><div>I am the assigned Gen-ART reviewer for this draft. For =
background on</div><div>Gen-ART, please see the FAQ at</div><div>&lt; <a hr=
ef=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.=
tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.</div>
<div><br></div><div>Please wait for direction from your document shepherd</=
div><div>or AD before posting a new version of the draft.</div><div><br></d=
iv><div>Document: draft-ietf-pkix-pubkey-caps-04.txt</div><div>Reviewer: =
=A0Mary Barnes=A0</div>
<div>Review Date: =A023 April 2012</div><div>IETF LC Date: 20 April 2012</d=
iv><div>IESG Telechat Date: 26 April 2012</div><div><br></div><div><br></di=
v><div>Summary: =A0Almost ready (nits &amp; minor issues). =A0</div><div><b=
r>
</div><div>Comments: There are quite a number of editorial nits, and a coup=
le cases where those result in lack of clarity, thus minor issues. =A0I am =
also assuming that someone has validated the ASN.1 notation.=A0</div><div><=
br>
</div><div>Minor Issues:</div><div>--------------</div><div>Section 1:=A0</=
div><div>- 2nd paragraph:</div><div>=A0-- last sentence. =A0The phrase &quo=
t;most just consisted&quot; in the following sentence is missing an object =
- most what? =A0</div>
<div>=A0 =A0This was especially easy since most just</div><div>=A0 =A0consi=
sted of the object identifier for the algorithm.</div><div>I think based on=
 the context that it should be written as=A0</div><div>&quot;most values&qu=
ot;, but it&#39;s not entirely clear to me, or perhaps it should be &quot;m=
ost parameters&quot;.=A0</div>
<div><br></div><div>- 3rd paragraph: =A0</div><div>=A0 -- RFC 2119 language=
 is used - &quot;MUST NOT&quot;, however, there is no reference to RFC 2119=
 language, which is fine given this is an informational document. =A0It wou=
ld seem that should be written lower case, in particular given this is an i=
ntroduction, which in general shouldn&#39;t include normative language. =A0=
</div>
<div><br></div><div>Section 4.2 &amp; 4.3:=A0</div><div>- there&#39;s a &qu=
ot;(id-??)&quot; in these two sections. =A0Is that intentional or should th=
at be referring to an explicit existing object identifier?=A0</div><div>=A0=
=A0</div>
<div>- There seems to be typos in the names of the ASN.1 elements that are =
being defined:</div><div>=A0 -- scap-ec-dh: =A0Shouldn&#39;t this be scap-p=
k-ecDH or am I just not understanding the notation here?</div><div>=A0-- sc=
ap-ec-MQV: Shouldn&#39;t this be scap-pk-ecMQV?</div>
<div><br></div><div><br></div><div>Nits:</div><div>-----</div><div>Section =
1:=A0</div><div>- 2nd paragraph:</div><div>=A0 -- 1st sentence: =A0&quot;se=
nders&quot; -&gt; &quot;sender&#39;s&quot;=A0</div><div>=A0 -- 5th sentence=
: =A0&quot;=85were ever use.&quot; -&gt; &quot;=85were ever used.&quot;</di=
v>
<div><br></div><div>Section 1.1:=A0</div><div>- 1st paragraph after descrip=
tion fields:=A0</div><div>=A0 &quot;The square brackets defined optional =
=85&quot; -&gt; =A0&quot;The square brackets define optional=85&quot;</div>=
<div><br></div>
<div>Section 2.2:=A0</div><div>- 1st paragraph, last sentence: there&#39;s =
a stray &quot;s&quot; in the sentence after &quot;location&quot;=A0</div><d=
iv><br></div><div>Section 4.1:=A0</div><div>- 1st paragraph, 1st sentence: =
&quot;All most&quot; -&gt; &quot;Almost&quot;=A0</div>
<div><br></div><div>Section 5:</div><div>- title: &quot;RSASSA-PSS&quot; -&=
gt; =A0&quot;RSA-SSA-PSS&quot;</div><div>- second paragraph: there&#39;s in=
consistent use of tense in these sentences. =A0I would suggest changing&quo=
t;</div>
<div>=A0 -- =A0&quot;it is always placed&quot; -&gt; &quot;it was always pl=
aced&quot;</div><div>=A0 -- =A0&quot;meant that one can place&quot; to &quo=
t;meant that one could place&quot;=A0</div><div><br></div><div>- last parag=
raph: =A0&quot;=85the assumption that entire matrix=85&quot; -&gt; &quot;&q=
uot;=85the assumption that the entire matrix=85&quot; =A0</div>
<div><br></div><div>Section 6:</div><div>- 1st paragraph: &quot;=85that nee=
d to be taking into account=85&quot; -&gt; =A0&quot;=85that need to be take=
n into account=85&quot;</div><div><br></div><div>- 5th paragraph: =A0I don&=
#39;t find the first sentence helpful. I would find it much easier to read =
if the 4th and 5th paragraphs were combined and the first sentence of the 5=
th removed entirely and reword the 2nd sentence of the 5th as:</div>
<div>&quot;However, passing too much information=85&quot; =A0</div>

--20cf3079bc9e6bc77704be5c40aa--

From mccap@petoni.org  Mon Apr 23 20:45:56 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 E795521F84D0 for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 20:45:56 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hsafAtUY0EYt for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 20:45:56 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id D9DD021F84CF for <gen-art@ietf.org>; Mon, 23 Apr 2012 20:45:55 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so143149qcs.31 for <gen-art@ietf.org>; Mon, 23 Apr 2012 20:45:55 -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=3GAcKOyu7eaD+0WK0k1NXYWFHl2SP5AznVgTdc/RKh4=; b=gygbD7rk1bBroF60WPak0Wihuf54sNYz8IfEnv0ZFXrQDtA958V6qJqqFXO6jR7B78 50bEN175rFfjUtGQZDvrEVP6ImbleIQZVvNcd1Oryn3cfGen92PmtoBXx9/EFvMCrfUH JcK0f5w+rcvfPCNyaMwCCvbhiTGeKV0pf1VTs=
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=3GAcKOyu7eaD+0WK0k1NXYWFHl2SP5AznVgTdc/RKh4=; b=OPyOHiQDZs9S7LM/pCsFEZvgvJsW/NeezLyGy4z08ulft4OfN0HfFX5weaZpZO552t QQ5AJAQQMAVaPMY+RS5cIIA4f4bVw+76XgtIf17ZUKLmbuoihfwcR0msDME8tYHerKdV i/Cay9tSDbWpkhATuySrzU4LVS7aCMEfnDXXLNNREl9XK852yDPK2NrAlf7S6IPEnSE6 qhe2cvlhm6zaN66gbkWjfLN6unTXTOCFffj0Sp5otP1loj6SiRctkbVlA9f+QGOLT1pI ByBBsavK/Y7+u4rxTsGKvZhCwghpv+XAI6BmLfLy1DXMEiMIf9XRI4iJDy9jWWI9tB2z gODw==
MIME-Version: 1.0
Received: by 10.224.211.72 with SMTP id gn8mr163196qab.10.1335239155316; Mon, 23 Apr 2012 20:45:55 -0700 (PDT)
Received: by 10.229.219.135 with HTTP; Mon, 23 Apr 2012 20:45:55 -0700 (PDT)
X-Originating-IP: [173.101.177.161]
Date: Mon, 23 Apr 2012 23:45:55 -0400
Message-ID: <CACvMsLHm0U5z4pJ3RWVe+s=75ujJh+YOwZK=Y4Det9XPBvn58g@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-dbider-sha2-mac-for-ssh.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmBrZfJ2eXifeVBa+4KyuUMnjwdaHJpxyeOVMRPjreXWzw+BeheCeB+HZO1C2lpiVDmRcKE
Subject: [Gen-art] Gen-ART Telechat Review of draft-dbider-sha2-mac-for-ssh-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, 24 Apr 2012 03:45:57 -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-dbider-sha2-mac-for-ssh-05
Reviewer: Peter McCann
Review Date: 2012-04-23
IETF LC End Date:
IESG Telechat date: 2012-04-26

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: None

From mccap@petoni.org  Mon Apr 23 21:42:52 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 75D5D21F84FB for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 21:42:52 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bnDnYXfbiM4w for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 21:42:50 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id D25A221F850C for <gen-art@ietf.org>; Mon, 23 Apr 2012 21:42:45 -0700 (PDT)
Received: by qaea16 with SMTP id a16so1958534qae.10 for <gen-art@ietf.org>; Mon, 23 Apr 2012 21:42:45 -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=PpVH7pxe7vAljcl2mTwERqWy0Tu75r7crV4OuQhyW3c=; b=Pzhp9JpWysT5248pYrtjDFK8KGFv4anrSCGTIohVJTpwAX+6mKhlnR9Q6DN6CN3Q8Q LX1gVplJ5zF4rT7G76mSXH41WUk/7iLXokF+J7K+chcmnPT+rdM5ds+sraHZH1QB8GQv +eVAJ3cfywgWNGZhsdoqybVa7twiI9/TF30Tw=
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=PpVH7pxe7vAljcl2mTwERqWy0Tu75r7crV4OuQhyW3c=; b=X8ecrU2vXDWdA0I+YJrseIq8s8y/ldnqW6QI3Sz5t8LPFMeAa/ICEVlA3HC4gxIlwd KCfWiUaEjIpgEO3F/BuCQLimJ7h+GviI7gZUmcePiJbafxw7j87geu5ufSiDzFsWOEQI TN5Y9Larpda6sHYIU93VI8NZdoEmA3V4S41qytxl6X0+qHgmp29VYeFT8glD3tPDFjot PDrlmPScNaFYKi55w7yUvM8I+gKWqNidFWQ8FhFO3DbFR+k9d1eHq8oqK98DAzAaKNau k3VEFVIMLRPv7W48GRdb3n0ocwtGQTJdf4Z+ur23kWeTI3xN2ap69zmetvyEw1XtoJHz DWSw==
MIME-Version: 1.0
Received: by 10.229.106.34 with SMTP id v34mr4660230qco.57.1335242565322; Mon, 23 Apr 2012 21:42:45 -0700 (PDT)
Received: by 10.229.219.135 with HTTP; Mon, 23 Apr 2012 21:42:45 -0700 (PDT)
X-Originating-IP: [173.101.177.161]
Date: Tue, 24 Apr 2012 00:42:45 -0400
Message-ID: <CACvMsLG0C=yYYmWP4Y29fOxdkkJaTqGz7A1aXdrwOEYtHWQpzw@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-templin-aero.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkeu+0ERxUjNX38rEW0zgGkAtxrjt0b9f+VpvBroHWFQ/nQ0mpMnWCqmfVeY7/75nji7Uur
Subject: [Gen-art] Gen-ART Telechat Review of draft-templin-aero-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 04:42:52 -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-templin-aero-10
Reviewer: Peter McCann
Review Date: 2012-04-23
IETF LC End Date:
IESG Telechat date: 2012-04-26

Summary: Discuss

Major issues:

Section 4.1 attempts to provide some motivation for this draft:
   In many AERO link use case scenarios (e.g., small enterprise
   networks, small and stable MANETs, etc.), routers can engage in a
   classical dynamic routing protocol (e.g., OSPF, RIP, IS-IS, etc.) so
   that routing/forwarding tables can be populated and standard
   forwarding between routers can be used.  In other scenarios (e.g.,
   large enterprise/ISP networks, cellular service provider networks,
   dynamic MANETs, etc.), this might be impractical due to routing
   protocol control message scaling issues.
However, it isn't clear to me that the mechanisms proposed in this draft
would be any more scalable than existing dynamic routing protocols.

In general, the draft appears to be mixing the concepts of service provider
and end-user networks in strange ways.  The AERO link uses host-based
mechanisms for prefix delegation, but it is intended to be a backbone of
a service provider network.  There seem to be some trust assumptions
borrowed from access links (such as the need for ingress filtering), yet
the routers on the AERO link are expected to work together in a peer-to-
peer fashion to compute direct routes to each other.  I do not feel that the
draft has adequately motivated this somewhat quirky set of assumptions.
Perhaps a deployment example that motivates why the different edge
routers cannot trust each other is in order.


Minor issues:

Section 4.4.5:
The text says to use experimental type code "100" but the ASCII art
still says "137."  Does the figure need to be changed?

Section 4.4.12:
   Eventually, any such correspondent AERO nodes will receive a NULL
   AERO Redirect message and will cease to use the egress node ('D') as
   a next hop.  They will then revert to sending packets destined to the
   EUN node ('E') via a trusted intermediate router and may subsequently
   receive new AERO Redirect messages to discover that the EUN node ('E'
   ) is now associated with a new AERO edge router.
Seems like this scenario requires that *part* of a prefix that was delegated
to D is now re-routed by the intermediate router A to a different destination.
Is that correct?  You are proposing to punch a hole in the original allocation,
and put in a more-specific (perhaps host-specific) route to E through a new
path?  What kind of protocols would be used to establish this new forwarding
state?

Nits/editorial comments:

Section 4.4.4:
   Note that on links in which link-layer address spoofing is possible,
   AERO nodes may be obliged to require the use of digital signatures.
   In that case, only the third of the above conditions can be accepted
   in order to ensure adequate data origin authentication.
Did you mean to say "only the fourth of the above conditions can be
accepted..."?

Section 5:
You say there are no IANA considerations, but do you need an experimental
ICMPv6 type code allocated?

From mccap@petoni.org  Mon Apr 23 21:58:05 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 392CA21F8603 for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 21:58:05 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BzuCYK+v87od for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 21:58:04 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7528B21F8601 for <gen-art@ietf.org>; Mon, 23 Apr 2012 21:58:04 -0700 (PDT)
Received: by qaea16 with SMTP id a16so1962306qae.10 for <gen-art@ietf.org>; Mon, 23 Apr 2012 21:58:03 -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=Hcy1AmRTpQbiZ9P3lszHjPDamAhk/EB+9/3utFkC/Lw=; b=OJcbXkCaVA59EbvNaNaJQELGspocBd+ok0N1Fc55DI2aaCejuzsGpCxnZwK7zMKaKr qsJIX26ORgUL1s0P5JUFYpeTJ9T/9vQQGNCnk1k80qpnqQhXfaAFvysP8v4UQjJ8BjjY UpcFc4sh0dmuNDOpcLStb8Gm4D+99oYr8XSCk=
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=Hcy1AmRTpQbiZ9P3lszHjPDamAhk/EB+9/3utFkC/Lw=; b=YHYRcs4eBl1SWc++8Mq9hoNXjnrYiIkjgunLA8YBiZjRFKovXvt8LfZBVUOVJ/YPdp YrBDPyfA9A8i9qOnDafTBRNOU/1zKJjdZy4v1fUGEcnMXOEJSUXyUCNmhbV6rNbdx9Od CXqsOQ230cjinzPeQxBpNmOirIPEZXvUA8aVE2ZlyGmzxJmv17rZW3PFJQjfFMc0EWIA hdivHsiX40TlX00+knua5LrRqtGC69hPg9Sf8s0whGzFEuE7J3GaZt21KFn8RbsmP/Ex 4b6hVUkTAqCda4E0qhbJfeJPhkMxw9nG5mBpNxqpp0JdfRxB+ptjFs5pf/TDI6UN7nUV 3NmA==
MIME-Version: 1.0
Received: by 10.229.137.143 with SMTP id w15mr4516391qct.37.1335243483690; Mon, 23 Apr 2012 21:58:03 -0700 (PDT)
Received: by 10.229.219.135 with HTTP; Mon, 23 Apr 2012 21:58:03 -0700 (PDT)
X-Originating-IP: [173.101.177.161]
Date: Tue, 24 Apr 2012 00:58:03 -0400
Message-ID: <CACvMsLG9gjBs4FUvamGetnHz5_VLQ+fqotWxYw=QeXMx3QK=AQ@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-ipfix-psamp-mib.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnNOZuxqk+ZCTFHrw9p7uAps23KUQ4Mf/MqMHcB8zRzpn8zz/Gt8iWTNO7frS6bRbDmIn3R
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-ipfix-psamp-mib-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 04:58:05 -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-ipfix-psamp-mib-04
Reviewer: Peter McCann
Review Date: 2012-04-24
IETF LC End Date:
IESG Telechat date: 2012-04-26

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: None

From mccap@petoni.org  Mon Apr 23 22:10:09 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 0E24421F8658 for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 22:10:09 -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=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 JA1hQAf+5dLg for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 22:10:07 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6148621F8655 for <gen-art@ietf.org>; Mon, 23 Apr 2012 22:10:07 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so166087qcs.31 for <gen-art@ietf.org>; Mon, 23 Apr 2012 22:10:06 -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=suQd6ZAIb0vVygnecVIJ3B2bHwpw794TtOHiSkG+FUs=; b=ME4+bt4SFYG8+64d0pjWUfaqdNRX63P+16EzQHr5OGGahKscwSjN+Wsux7Wpy6s/IE Ai6mCYhuQMmYUJoKQFwXzkTO30GUY2UTABSrLUs5DWwtXj2R4V8qgDoS1xNnrJmddr74 q3UlduH9MA/6ODRubX3q6vh+qIl8b4Zn4wlDE=
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=suQd6ZAIb0vVygnecVIJ3B2bHwpw794TtOHiSkG+FUs=; b=npMoYqm1CKRiaTmVG0OU5hzdsptkwkYB513VckZRwPyWE5On7HAGRZeQ++aUdZT+4w u48ETmndXgEJHdVCB7wjq1ESgBUsi2iXIYIRZL0NqB13YUOBv0blYTm0VUrwej5eTcq6 WeUL/EYK1f03f3cxj+OqJSvGOs7qUJja55SIgrP1N7sX8CkuhhcfjR4+8jRPoxtC8QP3 hZIwBZ62SAzU3xrGpbizBLDAUvV9cm4nG/kLMSMTRysBjOR5j6CuwO15MnIOHJFKtnXt uPc6PDV07RvZksNksOC9B4PRgWQyLLuN5lKUJvTxioVnj6pXtoZVOp1H0b6o63aIMpbS T01g==
MIME-Version: 1.0
Received: by 10.224.202.193 with SMTP id ff1mr15733756qab.36.1335244206850; Mon, 23 Apr 2012 22:10:06 -0700 (PDT)
Received: by 10.229.219.135 with HTTP; Mon, 23 Apr 2012 22:10:06 -0700 (PDT)
X-Originating-IP: [173.101.177.161]
Date: Tue, 24 Apr 2012 01:10:06 -0400
Message-ID: <CACvMsLG5b7amwOv0=dKfiAzDK48_=0Ce0t=G4Xi54AOPFYZwSA@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-kitten-gssapi-naming-exts.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkAjTGFdcfU6SfvY8SAwpm3bKK3mZbPehObelR5lEAovh2zBZSEZRuWaYfFLuBchK65cyS5
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-kitten-gssapi-naming-exts-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 05:10:09 -0000

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

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

Document: draft-ietf-kitten-gssapi-naming-exts-14
Reviewer: Peter McCann
Review Date: 2012-04-24
IETF LC End Date:
IESG Telechat date: 2012-04-26

Summary: Editorial nits remain

Major issues: None

Minor issues: None

Nits/editorial comments:

Four editorial comments from my earlier review of -08 still remain in
the document:


Section 3:
   un-authentciated
SHOULD BE:
   un-authenticated

   follows.This
SHOULD BE:
   follows.  This

Section 7.5.1:
   gss_name_attribute_get()
SHOULD BE:
   gss_get_name_attribute()

Section 9:
   another situations
SHOULD BE:
   another situation

From suresh.krishnan@ericsson.com  Mon Apr 23 22:38:46 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 577E121F8633 for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 22:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rm+0mU8wRbel for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 22:38:45 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2123921F862F for <gen-art@ietf.org>; Mon, 23 Apr 2012 22:38:44 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q3O5ce58004157; Tue, 24 Apr 2012 00:38:41 -0500
Received: from [164.48.125.54] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.178) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 24 Apr 2012 01:38:34 -0400
Message-ID: <4F963C45.6090702@ericsson.com>
Date: Tue, 24 Apr 2012 01:38:13 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120310 Thunderbird/11.0
MIME-Version: 1.0
To: <draft-ietf-geopriv-policy.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-geopriv-policy-25.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, 24 Apr 2012 05:38:46 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

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

Document: draft-ietf-geopriv-policy-25.txt
Reviewer: Suresh Krishnan
Review Date: 2012/04/23
IESG Telechat date: 2012/04/26

Summary: This draft is almost ready for publication as a Proposed
Standard but I have some comments.

Minor
=====

* Section 7.2 "Rule Example with Geodetic Location Condition" refers to
a location condition based on a polygon but the XML below refers to a
location condition based on a circle. Can you please fix this inconsistency.

* Section 13.2

It is unclear how this quotient (0.13) was calculated using the
information provided in Section 6.5.2. Can you please clarify?

   The choices of 6.5.2 are such that this maximum leakage can
   be established: by any statistical procedures, without using
   geographic information (highways, etc. as discussed above), the
   quotient A1/A is larger than 0.13 (= 1/(5*1.5) )


Editorial
=========

* Section 13.2

OLD:

Whenever location information is returned to a location recipient then
it contains the location of the Target.

NEW:
Whenever location information is returned to a location recipient it
contains the location of the Target.


OLD:
However, even without the Target's movement there is danger to reveal
information over time

NEW:
However, even without any Target movement there is a danger that more
information may be revealed over time.

OLD:
informationa bout the Target.

NEW:
information about the Target.


Thanks
Suresh



From mccap@petoni.org  Mon Apr 23 22:41:45 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 5301811E8081 for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 22:41:45 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FuoagS0DLURw for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 22:41:44 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id DAA0821F8483 for <gen-art@ietf.org>; Mon, 23 Apr 2012 22:41:43 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so175030qcs.31 for <gen-art@ietf.org>; Mon, 23 Apr 2012 22:41:43 -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=vL/0R0+v45TqDpKLf4ZBA6W6syKS1OxMcZ0oWqvru8U=; b=ABVSLKf26dU3OrfiPJdDACrAa9zmNvFXO4I/umyGV3C3wxiXEPVuIc/GodumcmJ20c ZjwxTDotxeuKxR/dWAdr8f7cg4BpfPstQ2805yvNI92asVZB45yMM/HBr440YGl8z3B5 ENYjtIT/GujTo8r89wxfSvtgjCByXI5d1Wqro=
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=vL/0R0+v45TqDpKLf4ZBA6W6syKS1OxMcZ0oWqvru8U=; b=ZjEULDYIbXEdKrx1s9HXTLjqPFkx9td10o6lL57zwf5hBjWArdGhQAFwTvoKrV4WN8 564sL9V/yv0CwV8SBzCgSf1jdBvJvx2eCjvsT09gJ1atzss0XMqO+ZLrjXmYiZg0Dm/T VynqufciFv4fHhiTlf5XSHNI6TNmVMxnpV4j1sXjYQ5Nyx8jaM3DQXPAh3oJu3TZfMB5 3d7lkZz8J3CFy694J+tsRgrspJHUBPLA3Ob9LIK/zSWrSKaUtSEa2P6k5+Niet3y7nhi Jua5PRu00EsHM4dELtOkDkSUmp8VMsQpe+8C5AzPUO7Yew9cX28z/2zxmpT0e+MPDSwi cqrg==
MIME-Version: 1.0
Received: by 10.229.137.143 with SMTP id w15mr4532665qct.37.1335246103330; Mon, 23 Apr 2012 22:41:43 -0700 (PDT)
Received: by 10.229.219.135 with HTTP; Mon, 23 Apr 2012 22:41:43 -0700 (PDT)
X-Originating-IP: [173.101.177.161]
Date: Tue, 24 Apr 2012 01:41:43 -0400
Message-ID: <CACvMsLEAJ2oND1zXPAEvDn39XUvf-qfUA=-Kr9SmFhgMaY4H4w@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org,  draft-ietf-dhc-dhcpv6-redundancy-consider.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmah3Tb66louYVYfM8gCd2hplapIRT/vW4hvqYvG2KvIJbt8dpk8MUjbITnFx5dQNBl17SM
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-dhc-dhcpv6-redundancy-consider-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 05:41:45 -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-dhc-dhcpv6-redundancy-consider-02
Reviewer: Peter McCann
Review Date: 2012-04-24
IETF LC End Date:
IESG Telechat date: 2012-04-26

Summary: Ready (with nits)

Major issues: None

Minor issues:

Section 2.1:
   without any intermediate devices (like
   home routers used in service provider model).
SHOULD BE:
   with or without any intermediate devices.

Nits/editorial comments:

Abstract:
   those who
   wishing to use
SHOULD BE:
   those who
   wish to use

Section 2:
   The proposed architecture may be used in
   wide range of networks, two notable
SHOULD BE:
   While the proposed architecture may be used in
   a wide range of networks, two notable

   Although DHCPv6 redundancy may be useful in a wide range of
   scenarios, they may be generalized for illustration purposes in the
   two aforementioned.
SHOULD BE:
   Although DHCPv6 redundancy may be useful in a wide range of
   scenarios, we may generalize for illustration purposes from the
   two aforementioned scenarios.

   Clients requesting IPv6 addresses, prefixes, and or options care
   of DHCPv6
SHOULD BE:
   Clients requesting IPv6 addresses, prefixes, and or options by way
   of DHCPv6

   available until DHCPv6 protocol is standardized
SHOULD BE:
   available until a DHCPv6 failover protocol is standardized

Section 2.1:
   represents cases, where end-user devices
SHOULD BE:
  represents cases where end-user devices

   4.  CPE devices must implement a stateful DHCPv6 client [RFC3315],
       support for DHCPv6 prefix delegation [RFC3633] or stateless
       DHCPv6 [RFC3736] may also be implemented.
SHOULD BE:
   4.  CPE devices must implement a stateful DHCPv6 client [RFC3315];
       support for DHCPv6 prefix delegation [RFC3633] or stateless
       DHCPv6 [RFC3736] may also be implemented.

Section 3.1:
   Essential to the the use of
SHOULD BE:
   Essential to the use of

Section 5:
   In indentical prefixes scenario,
SHOULD BE:
   In the identical prefixes scenario,

   way how to solve
SHOULD BE:
   way to solve

   IPv6 lease data care of the DHCPv6 Leasequery
SHOULD BE:
   IPv6 lease data by way of the DHCPv6 Leasequery

From suresh.krishnan@ericsson.com  Mon Apr 23 22:42:08 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 A145721F8495 for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 22:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FZALXfMeRlVy for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 22:42:06 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id B7F3321F8493 for <gen-art@ietf.org>; Mon, 23 Apr 2012 22:42:06 -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 q3O5g5BO027626 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 24 Apr 2012 00:42:06 -0500
Received: from [164.48.125.54] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.31) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 24 Apr 2012 01:42:04 -0400
Message-ID: <4F963D27.4010902@ericsson.com>
Date: Tue, 24 Apr 2012 01:41:59 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120310 Thunderbird/11.0
MIME-Version: 1.0
To: "draft-ietf-avtcore-ecn-for-rtp.all@tools.ietf.org" <draft-ietf-avtcore-ecn-for-rtp.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-avtcore-ecn-for-rtp-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 05:42:08 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

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

Document: draft-ietf-avtcore-ecn-for-rtp-07.txt
Reviewer: Suresh Krishnan
Review Date: 2012/04/23
IESG Telechat date: 2012/04/26

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

Thanks
Suresh



From mccap@petoni.org  Mon Apr 23 22:50:19 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 F2B7C11E8080 for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 22:50:18 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wrlLFfyak1Ao for <gen-art@ietfa.amsl.com>; Mon, 23 Apr 2012 22:50:17 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3734C11E809B for <gen-art@ietf.org>; Mon, 23 Apr 2012 22:50:15 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so177408qcs.31 for <gen-art@ietf.org>; Mon, 23 Apr 2012 22:50:14 -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=yXcgrSFF7BDeHWbUFxNGOO0juYOohNekLDJehMThZuw=; b=TqHtFjOsiRWYmCftNCt8Og0+NaFPkjQHDjkTiUp3CzCtXu0Vikox2KNe30ejTiiR1Y M+jJymt7pbVRkpOVW9J/UzPT2apFo0I2NEzvaeeZ45tZqOhTAnfGpS7KbyS1lTnDJOnw aqnRMeBInv31zhME4rGIA5kMtouT0CtOQzZJw=
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=yXcgrSFF7BDeHWbUFxNGOO0juYOohNekLDJehMThZuw=; b=b+pf4ylJvPIhW6kBVdUrdZfxVSZBIc/Rlkl2rklHYdxPTOh8FeWnu6wumV3LUvvlrN ZToDFCpFSVQgecdbgAumziJ07NNfzpJIiDgFjqNDeJp4l08CWV7hKpWac4KcCF34dZ1L M9nVS/PalYzD8NElatIkXdM3LxSmJQDQ5CldV877obPcdaKDVjBhotyMDYJ8qmwq5l3B JGTTfBylXtQPsrMSlTbIMlOHADxnsxSLKeU+6BzcTOKncG1Us4LIbQmw6ap4lee1wFcr Mt6x0xVWiC4KzbHOstf8RdObC7KfeIw1asy7LQtZ9UjsO7t39nTDKvN0SVtoVeHcC7dl cgyw==
MIME-Version: 1.0
Received: by 10.229.136.198 with SMTP id s6mr4673115qct.77.1335246614695; Mon, 23 Apr 2012 22:50:14 -0700 (PDT)
Received: by 10.229.219.135 with HTTP; Mon, 23 Apr 2012 22:50:14 -0700 (PDT)
X-Originating-IP: [173.101.177.161]
Date: Tue, 24 Apr 2012 01:50:14 -0400
Message-ID: <CACvMsLHJb3Qz5BxtZU3t0zXU6DiHz0Kz--rLimg_f3Fu0=S0+A@mail.gmail.com>
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-l2vpn-arp-mediation.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlAh5xpz0JW+oFGJlRqDyBRO6twDMM/vHvi4ELIn28toqmgMUGnKo9SCFQrkkJSo/waztIZ
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-l2vpn-arp-mediation-19
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, 24 Apr 2012 05:50:19 -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-l2vpn-arp-mediation-19
Reviewer: Peter McCann
Review Date: 2012-04-24
IETF LC End Date:
IESG Telechat date: 2012-04-26

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:

The only negative changes in this version with respect to -18 were the
cross-referenced section numbers, some of which now have a trailing
period.  Also, the reference to multiple sections that appears in Section 4.1.6
was changed to a perhaps incorrect value.

From ron.even.tlv@gmail.com  Tue Apr 24 05:11:50 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 5AD9421F87D2; Tue, 24 Apr 2012 05:11:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.099,  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 LrphiDOxQ7kQ; Tue, 24 Apr 2012 05:11:49 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9A6D221F87C7; Tue, 24 Apr 2012 05:11:46 -0700 (PDT)
Received: by werb10 with SMTP id b10so458158wer.31 for <multiple recipients>; Tue, 24 Apr 2012 05:11:45 -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=P5JcAPZYXoPqR4oBCZNvCDS46NxlqLu/vkpM/Fw/y9Y=; b=TmotFnhgTLysiDoTenMc5xiN/KNNsnb+gLbMSXwEjWXf++2SEkQMrupGUleM8XvgCL FgW0GtLh5LpomRQlpXaQKmiY6fNKybuDdvBcTV/00hfT7MlwcRrJ6zPf2KzFQK45Dkq6 XTMNS335UxKSHbnyO4X2PUbMkh47Ztir2uVsU/W3xDWtS40X9XcRE4oEUOjc+XZ3aRm7 nksMk1kg946CnDJOGu/tXqRTEw0omTkat4WGi3910xwryqFkmKS5+7Qzbyg+ZlyzT6Kp IKHdccva3Fjt8sxQTgU2cUiyX52ZHYIJqD+bWViY8Sb1x4rrhi6TlRLD49rPj2CJLxRd IL7Q==
Received: by 10.216.137.74 with SMTP id x52mr8373887wei.77.1335269505821; Tue, 24 Apr 2012 05:11:45 -0700 (PDT)
Received: from windows8d787f9 ([109.65.204.117]) by mx.google.com with ESMTPS id w10sm46251989wiy.3.2012.04.24.05.11.43 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 Apr 2012 05:11:44 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-mboned-mcaddrdoc.all@tools.ietf.org>
Date: Tue, 24 Apr 2012 15:10:02 +0300
Message-ID: <4f969880.4a54b40a.69b2.fffff84b@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002B_01CD222C.547101D0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac0iEy0XtYR8sg28SUqAje+nEOhjjw==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>
Subject: [Gen-art] GenART LC review of draft-ietf-mboned-mcaddrdoc-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, 24 Apr 2012 12:11:50 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_002B_01CD222C.547101D0
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-mboned-mcaddrdoc-03

Reviewer: Roni Even

Review Date:2012-4-24

IETF LC End Date: 2012-5-2

IESG Telechat date:

 

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

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

 

 


------=_NextPart_000_002B_01CD222C.547101D0
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 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=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><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-=
mboned-mcaddrdoc-03<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;4&#8211;24<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;5&#8211;2<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational </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"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=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=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_002B_01CD222C.547101D0--


From fltemplin@acm.org  Tue Apr 24 07:58:31 2012
Return-Path: <fltemplin@acm.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 5030C21F87F2 for <gen-art@ietfa.amsl.com>; Tue, 24 Apr 2012 07:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.288
X-Spam-Level: 
X-Spam-Status: No, score=-102.288 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, HTML_MESSAGE=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 LdHmTExP7u0v for <gen-art@ietfa.amsl.com>; Tue, 24 Apr 2012 07:58:30 -0700 (PDT)
Received: from nm31-vm1.bullet.mail.bf1.yahoo.com (nm31-vm1.bullet.mail.bf1.yahoo.com [72.30.239.9]) by ietfa.amsl.com (Postfix) with SMTP id BDB2E21F87F4 for <gen-art@ietf.org>; Tue, 24 Apr 2012 07:58:28 -0700 (PDT)
Received: from [98.139.212.153] by nm31.bullet.mail.bf1.yahoo.com with NNFMP; 24 Apr 2012 14:58:27 -0000
Received: from [98.139.212.215] by tm10.bullet.mail.bf1.yahoo.com with NNFMP; 24 Apr 2012 14:58:27 -0000
Received: from [127.0.0.1] by omp1024.mail.bf1.yahoo.com with NNFMP; 24 Apr 2012 14:58:27 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 794887.38719.bm@omp1024.mail.bf1.yahoo.com
Received: (qmail 33384 invoked by uid 60001); 24 Apr 2012 14:58:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1335279507; bh=2SOvEEwCfsECaMaSzfJuTPuyFDKguX/iJnlKC+7fsDY=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=RRu5DhWaacXVTGgdHA0UkfH8nkjY1hT1yvnhRDb9LbJB/mLN43iQokCVKVOJkh4rqYDOlsQlzciEeGAmVcftlrQY7m8pg5NCyQnN+lo4SgM8wm8gFdBvrm4u6Qb1dCePEgIFRSo0XDTRF7fHeWHjA++bTgA4wJq5nawuDPKmOHg=
X-YMail-OSG: IoftIhYVM1lWs4PCp_3JF435KX7UKMmpvT1OJVCSXSZFHqf ri9Gy1prQqKCvS1IBTnEtMJ7qGPCv3rnFnyXn9LQlT4Dn9z4jCx2_egzVRC1 PaFugya1VD7f2LFcOf7XMD9ivhWjfOPxyeMflgajpnE0GVOyEFP7Okuu7so0 k7iKO9.umf8o0N_kL_.kY0P7Kr__EGvcn3_xyxBpzhqxHLZpow4tuN1QzK0k 4r8.fgXVh.KvYeliCyDa4p7GxEv.VqJ16nyJNF_bHHazSjnaCsnumTypDPah iXST_qBMCNbKm8k5p55nolHiS6_EBJaWsvzpfFffDPyPupRecv0Vcjzc3fDm Y_5OGegsSP.BDiWNGSUU19sqGPoXjKsAa9U50joZmWS._.31QtdMqW3RSKmj c2qySWn0Mh_hIBilvCJwdQ27bKpxruzNN0MHU8EX1E1d5xpNYm95vA2Ufv6U QZgZgIfTCudyJF0gcEgtfsrIbPHCOWSqYjJ8gVZYF66TktPE-
Received: from [130.76.32.212] by web161603.mail.bf1.yahoo.com via HTTP; Tue, 24 Apr 2012 07:58:27 PDT
X-RocketYMMF: fltemplin
X-Mailer: YahooMailWebService/0.8.117.340979
References: <CACvMsLG0C=yYYmWP4Y29fOxdkkJaTqGz7A1aXdrwOEYtHWQpzw@mail.gmail.com>
Message-ID: <1335279507.26159.YahooMailNeo@web161603.mail.bf1.yahoo.com>
Date: Tue, 24 Apr 2012 07:58:27 -0700 (PDT)
From: "Fred L. Templin" <fltemplin@acm.org>
To: Pete McCann <mccap@petoni.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-templin-aero.all@tools.ietf.org" <draft-templin-aero.all@tools.ietf.org>
In-Reply-To: <CACvMsLG0C=yYYmWP4Y29fOxdkkJaTqGz7A1aXdrwOEYtHWQpzw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-2012143828-282926690-1335279507=:26159"
X-Mailman-Approved-At: Tue, 24 Apr 2012 08:01:01 -0700
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-templin-aero-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Fred L. Templin" <fltemplin@acm.org>
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, 24 Apr 2012 14:58:31 -0000

---2012143828-282926690-1335279507=:26159
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hello Pete,=0A=0AThank you for your comments, and please see below for prop=
osed resolutions:=0A=0AFred=0Afltemplin@acm.org=0A=0A>_____________________=
___________=0A> From: Pete McCann <mccap@petoni.org>=0A>To: gen-art@ietf.or=
g; draft-templin-aero.all@tools.ietf.org =0A>Sent: Monday, April 23, 2012 9=
:42 PM=0A>Subject: Gen-ART Telechat Review of draft-templin-aero-10=0A> =0A=
>I am the assigned Gen-ART reviewer for this draft. For background on=0A>Ge=
n-ART, please see the FAQ at=0A>< http://wiki.tools.ietf.org/area/gen/trac/=
wiki/GenArtfaq>.=0A>=0A>Please wait for direction from your document shephe=
rd=0A>or AD before posting a new version of the draft.=0A>=0A>Document: dra=
ft-templin-aero-10=0A>Reviewer: Peter McCann=0A>Review Date: 2012-04-23=0A>=
IETF LC End Date:=0A>IESG Telechat date: 2012-04-26=0A>=0A>Summary: Discuss=
=0A>=0A>Major issues:=0A>=0A>Section 4.1 attempts to provide some motivatio=
n for this draft:=0A>=C2=A0=C2=A0=C2=A0In many AERO link use case scenarios=
 (e.g., small enterprise=0A>=C2=A0=C2=A0=C2=A0networks, small and stable MA=
NETs, etc.), routers can engage in a=0A>=C2=A0=C2=A0=C2=A0classical dynamic=
 routing protocol (e.g., OSPF, RIP, IS-IS, etc.) so=0A>=C2=A0=C2=A0=C2=A0th=
at routing/forwarding tables can be populated and standard=0A>=C2=A0=C2=A0=
=C2=A0forwarding between routers can be used.=C2=A0 In other scenarios (e.g=
.,=0A>=C2=A0=C2=A0=C2=A0large enterprise/ISP networks, cellular service pro=
vider networks,=0A>=C2=A0=C2=A0=C2=A0dynamic MANETs, etc.), this might be i=
mpractical due to routing=0A>=C2=A0=C2=A0=C2=A0protocol control message sca=
ling issues.=0A>However, it isn't clear to me that the mechanisms proposed =
in this draft=0A>would be any more scalable than existing dynamic routing p=
rotocols.=0A=0AScaling properties of the mechanism are proportional to=0Ath=
e number of distinct=0A(ingress, egress) pairs of active communications.=0A=
Intuitively, the mechanism will=0Aprovide better scaling properties than=0A=
traditional dynamic routing protocols if=0Athe number of active pairs is sp=
arse=0Ain relation to the number of nodes on the=0Alink. Quantitative analy=
sis would be=0Athrough experimentation after publication.=0A=0A>In general,=
 the draft appears to be mixing the concepts of service provider=0A>and end=
-user networks in strange ways.=C2=A0 The AERO link uses host-based=0A>mech=
anisms for prefix delegation, but it is intended to be a backbone of=0A>a s=
ervice provider network.=C2=A0 There seem to be some trust assumptions=0A>b=
orrowed from access links (such as the need for ingress filtering), yet=0A>=
the routers on the AERO link are expected to work together in a peer-to-=0A=
>peer fashion to compute direct routes to each other.=C2=A0 I do not feel t=
hat the=0A>draft has adequately motivated this somewhat quirky set of assum=
ptions.=0A>Perhaps a deployment example that motivates why the different ed=
ge=0A>routers cannot trust each other is in order.=0A=0AA deployment exampl=
e could be added as a new Section=0A4.4 (causing existing=0ASections 4.4 on=
ward to be renumbered beginning with=0ASection 4.5). The new=0ASection coul=
d read:=0A=C2=A0=0A=E2=80=9CAs a simple example, consider a large service p=
rovider=0Anetwork that is extended=0Aprimarily using L2 bridges instead of =
L3 routers. The=0Anetwork is therefore seen as=0Aa single link by the IP la=
yer. In that case, a new=0Aspoofing attack vector is open to=0Amalicious no=
des on the link that could send=0Apackets with spoofed IP source=0Aaddresse=
s with low probability of detection,=0Ae.g., to initiate a DoS attack direc=
ted=0Ato some other node on the link. AERO=0Atherefore applies to links on =
which attached=0Anodes do not necessarily trust=0Aeach other.=E2=80=9D=0A=
=0A>Minor issues:=0A>=0A>Section 4.4.5:=0A>The text says to use experimenta=
l type code "100" but the ASCII art=0A>still says "137."=C2=A0 Does the fig=
ure need to be changed?=0A=0AYes; the figure is incorrect, and will be corr=
ected to say "100".=0A=0A>Section 4.4.12:=0A>=C2=A0=C2=A0=C2=A0Eventually, =
any such correspondent AERO nodes will receive a NULL=0A>=C2=A0=C2=A0=C2=A0=
AERO Redirect message and will cease to use the egress node ('D') as=0A>=C2=
=A0=C2=A0=C2=A0a next hop.=C2=A0 They will then revert to sending packets d=
estined to the=0A>=C2=A0=C2=A0=C2=A0EUN node ('E') via a trusted intermedia=
te router and may subsequently=0A>=C2=A0=C2=A0=C2=A0receive new AERO Redire=
ct messages to discover that the EUN node ('E'=0A>=C2=A0=C2=A0=C2=A0) is no=
w associated with a new AERO edge router.=0A>Seems like this scenario requi=
res that *part* of a prefix that was delegated=0A>to D is now re-routed by =
the intermediate router A to a different destination.=0A>Is that correct?=
=C2=A0 You are proposing to punch a hole in the original allocation,=0A>and=
 put in a more-specific (perhaps host-specific) route to E through a new=0A=
>path?=C2=A0 What kind of protocols would be used to establish this new for=
warding=0A>state?=0A=0APunching a hole in a short aggregated prefix is one=
=0Apossibility, but another=0Apossibility is that the edge router is delega=
ted many=0Anon-aggregated long=0Aprefixes. In that case, the mobile node ca=
n take its long=0Aprefix to a new=0Aedge router without the old edge router=
 needing to punch any=0Aholes.=0A=0A>Nits/editorial comments:=0A>=0A>Sectio=
n 4.4.4:=0A>=C2=A0=C2=A0=C2=A0Note that on links in which link-layer addres=
s spoofing is possible,=0A>=C2=A0=C2=A0=C2=A0AERO nodes may be obliged to r=
equire the use of digital signatures.=0A>=C2=A0=C2=A0=C2=A0In that case, on=
ly the third of the above conditions can be accepted=0A>=C2=A0=C2=A0=C2=A0i=
n order to ensure adequate data origin authentication.=0A>Did you mean to s=
ay "only the fourth of the above conditions can be=0A>accepted..."? =0A=0A=
=0AYou are correct; this was also mentioned in an earlier comment and=0Awil=
l be fixed in the next document version.=0A=0A=0A>Section 5:=0A>You say the=
re are no IANA considerations, but do you need an experimental=0A>ICMPv6 ty=
pe code allocated?=0A=0ANo new experimental ICMPv6 code type needs to be=0A=
allocated, since RFC4443=0Asets aside the value =E2=80=9C100=E2=80=9D as an=
 experimental ICMPv6=0Acode point.=0A>
---2012143828-282926690-1335279507=:26159
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:12pt"><div><span>Hello Pete=
,</span></div><div><br><span></span></div><div><span>Thank you for your com=
ments, and please see below for proposed resolutions:</span></div><div><br>=
</div><div>Fred</div><div>fltemplin@acm.org</div><div><br></div><div>&gt;__=
______________________________<br>&gt; From: Pete McCann &lt;mccap@petoni.o=
rg&gt;<br>&gt;To: gen-art@ietf.org; draft-templin-aero.all@tools.ietf.org <=
br>&gt;Sent: Monday, April 23, 2012 9:42 PM<br>&gt;Subject: Gen-ART Telecha=
t Review of draft-templin-aero-10<br>&gt; <br>&gt;I am the assigned Gen-ART=
 reviewer for this draft. For background on<br>&gt;Gen-ART, please see the =
FAQ at<br>&gt;&lt; <a target=3D"_blank" href=3D"http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki=
/GenArtfaq</a>&gt;.<br>&gt;<br>&gt;Please wait for direction from your
 document shepherd<br>&gt;or AD before posting a new version of the draft.<=
br>&gt;<br>&gt;Document: draft-templin-aero-10<br>&gt;Reviewer: Peter McCan=
n<br>&gt;Review Date: 2012-04-23<br>&gt;IETF LC End Date:<br>&gt;IESG Telec=
hat date: 2012-04-26<br>&gt;<br>&gt;Summary: Discuss<br>&gt;<br>&gt;Major i=
ssues:<br>&gt;<br>&gt;Section 4.1 attempts to provide some motivation for t=
his draft:<br>&gt;&nbsp;&nbsp;&nbsp;In many AERO link use case scenarios (e=
.g., small enterprise<br>&gt;&nbsp;&nbsp;&nbsp;networks, small and stable M=
ANETs, etc.), routers can engage in a<br>&gt;&nbsp;&nbsp;&nbsp;classical dy=
namic routing protocol (e.g., OSPF, RIP, IS-IS, etc.) so<br>&gt;&nbsp;&nbsp=
;&nbsp;that routing/forwarding tables can be populated and standard<br>&gt;=
&nbsp;&nbsp;&nbsp;forwarding between routers can be used.&nbsp; In other sc=
enarios (e.g.,<br>&gt;&nbsp;&nbsp;&nbsp;large enterprise/ISP networks, cell=
ular service provider networks,<br>&gt;&nbsp;&nbsp;&nbsp;dynamic
 MANETs, etc.), this might be impractical due to routing<br>&gt;&nbsp;&nbsp=
;&nbsp;protocol control message scaling issues.<br>&gt;However, it isn't cl=
ear to me that the mechanisms proposed in this draft<br>&gt;would be any mo=
re scalable than existing dynamic routing protocols.</div><div><br></div><d=
iv><!--[if gte mso 9]><xml>=0A <w:WordDocument>=0A  <w:View>Normal</w:View>=
=0A  <w:Zoom>0</w:Zoom>=0A  <w:TrackMoves/>=0A  <w:TrackFormatting/>=0A  <w=
:PunctuationKerning/>=0A  <w:ValidateAgainstSchemas/>=0A  <w:SaveIfXMLInval=
id>false</w:SaveIfXMLInvalid>=0A  <w:IgnoreMixedContent>false</w:IgnoreMixe=
dContent>=0A  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderTe=
xt>=0A  <w:DoNotPromoteQF/>=0A  <w:LidThemeOther>EN-US</w:LidThemeOther>=0A=
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>=0A  <w:LidThemeComplexScript>X-=
NONE</w:LidThemeComplexScript>=0A  <w:Compatibility>=0A   <w:BreakWrappedTa=
bles/>=0A   <w:SnapToGridInCell/>=0A   <w:WrapTextWithPunct/>=0A   <w:UseAs=
ianBreakRules/>=0A   <w:DontGrowAutofit/>=0A   <w:SplitPgBreakAndParaMark/>=
=0A   <w:DontVertAlignCellWithSp/>=0A   <w:DontBreakConstrainedForcedTables=
/>=0A   <w:DontVertAlignInTxbx/>=0A   <w:Word11KerningPairs/>=0A   <w:Cache=
dColBalance/>=0A  </w:Compatibility>=0A  <m:mathPr>=0A   <m:mathFont m:val=
=3D"Cambria Math"/>=0A   <m:brkBin m:val=3D"before"/>=0A   <m:brkBinSub m:v=
al=3D"&#45;-"/>=0A   <m:smallFrac m:val=3D"off"/>=0A   <m:dispDef/>=0A   <m=
:lMargin m:val=3D"0"/>=0A   <m:rMargin m:val=3D"0"/>=0A   <m:defJc m:val=3D=
"centerGroup"/>=0A   <m:wrapIndent m:val=3D"1440"/>=0A   <m:intLim m:val=3D=
"subSup"/>=0A   <m:naryLim m:val=3D"undOvr"/>=0A  </m:mathPr></w:WordDocume=
nt>=0A</xml><![endif]--><!--[if gte mso 9]><xml>=0A <w:LatentStyles DefLock=
edState=3D"false" DefUnhideWhenUsed=3D"true"=0A  DefSemiHidden=3D"true" Def=
QFormat=3D"false" DefPriority=3D"99"=0A  LatentStyleCount=3D"267">=0A  <w:L=
sdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"=0A   Unhid=
eWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>=0A  <w:LsdException =
Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D=
"false" QFormat=3D"true" Name=3D"heading 1"/>=0A  <w:LsdException Locked=3D=
"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 2"/>=0A  <w:LsdExce=
ption Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 3"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=
=3D"heading 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" QForma=
t=3D"true" Name=3D"heading 5"/>=0A  <w:LsdException Locked=3D"false" Priori=
ty=3D"9" QFormat=3D"true" Name=3D"heading 6"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 7"/>=0A  <w:LsdE=
xception Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 8=
"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Na=
me=3D"heading 9"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Nam=
e=3D"toc 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"=
toc 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3=
"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>=0A  =
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>=0A  <w:LsdExce=
ption Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D"caption"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"1" Name=3D"Default Paragraph Font"/>=0A  <w:LsdE=
xception Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"=0A   UnhideW=
henUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>=0A  <w:LsdException =
Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" QFormat=3D"true" Name=3D"Strong"/>=0A  <w:LsdException Locked=3D=
"false" Priority=3D"20" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" =
QFormat=3D"true" Name=3D"Emphasis"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"59" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"T=
able Grid"/>=0A  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"1" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" =
Name=3D"No Spacing"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" =
SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Light List"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Light Grid"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium S=
hading 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A   Un=
hideWhenUsed=3D"false" Name=3D"Medium List 1"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Medium List 2"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium G=
rid 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   UnhideWh=
enUsed=3D"false" Name=3D"Medium Grid 3"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Dark List"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" SemiH=
idden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Colorful Grid"/>=0A  <w:LsdException Locked=3D"false" Pr=
iority=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Li=
ght Shading Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"61=
" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List Acc=
ent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=0A   Un=
hideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWhenU=
sed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fa=
lse" Name=3D"Medium List 1 Accent 1"/>=0A  <w:LsdException Locked=3D"false"=
 UnhideWhenUsed=3D"false" Name=3D"Revision"/>=0A  <w:LsdException Locked=3D=
"false" Priority=3D"34" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" =
QFormat=3D"true" Name=3D"List Paragraph"/>=0A  <w:LsdException Locked=3D"fa=
lse" Priority=3D"29" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFo=
rmat=3D"true" Name=3D"Quote"/>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"30" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true=
" Name=3D"Intense Quote"/>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List=
 2 Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHid=
den=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"=
/>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false=
"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   Unhid=
eWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D=
"false" Name=3D"Dark List Accent 1"/>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"=
Colorful Shading Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful=
 List Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"73" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent=
 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=0A   Un=
hideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D=
"false" Name=3D"Light Grid Accent 2"/>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D=
"Medium Shading 1 Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium S=
hading 2 Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"65" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Acc=
ent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=0A   UnhideWhenU=
sed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Medium Grid 3 Accent 2"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"D=
ark List Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading =
Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"61" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Light List Accent 3"/>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"=
Light Grid Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"63"=
 SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading =
1 Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidd=
en=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent =
3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"fal=
se"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=0A   Unh=
ideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Medium Grid 1 Accent 3"/>=0A  <w:LsdException Locked=3D"=
false" Priority=3D"68" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" N=
ame=3D"Medium Grid 2 Accent 3"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"69" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Mediu=
m Grid 3 Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"70" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent =
3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"fal=
se"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>=0A  =
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=0A   =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUs=
ed=3D"false" Name=3D"Colorful Grid Accent 3"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Light Shading Accent 4"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"61" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"L=
ight List Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" =
SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accen=
t 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"f=
alse"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>=0A=
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=0A =
  UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>=0A  <w:LsdE=
xception Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A   UnhideW=
henUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"f=
alse" Name=3D"Medium List 2 Accent 4"/>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Medium Grid 1 Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"68" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium G=
rid 2 Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"69" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent=
 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Colorful List Accent 4"/>=0A  <w:LsdException Locked=3D"=
false" Priority=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" N=
ame=3D"Colorful Grid Accent 4"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light=
 Shading Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"61" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List Accent=
 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=0A   Unhid=
eWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Medium Shading 2 Accent 5"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Medium List 1 Accent 5"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"M=
edium List 2 Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"6=
7" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1=
 Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidde=
n=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Dark List Accent 5"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Colorful Shading Accent 5"/>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Colorful List Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful=
 Grid Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent=
 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   Unhid=
eWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fa=
lse" Name=3D"Medium Shading 1 Accent 6"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Medium Shading 2 Accent 6"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Mediu=
m List 1 Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"66" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Acc=
ent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   UnhideWhenU=
sed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Dark List Accent 6"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Color=
ful Shading Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"72=
" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful List =
Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D"=
TOC Heading"/>=0A </w:LatentStyles>=0A</xml><![endif]--><!--[if gte mso 10]=
>=0A<style>=0A /* Style Definitions */=0A table.MsoNormalTable=0A=09{mso-st=
yle-name:"Table Normal";=0A=09mso-tstyle-rowband-size:0;=0A=09mso-tstyle-co=
lband-size:0;=0A=09mso-style-noshow:yes;=0A=09mso-style-priority:99;=0A=09m=
so-style-qformat:yes;=0A=09mso-style-parent:"";=0A=09mso-padding-alt:0in 5.=
4pt 0in 5.4pt;=0A=09mso-para-margin-top:0in;=0A=09mso-para-margin-right:0in=
;=0A=09mso-para-margin-bottom:10.0pt;=0A=09mso-para-margin-left:0in;=0A=09l=
ine-height:115%;=0A=09mso-pagination:widow-orphan;=0A=09font-size:11.0pt;=
=0A=09font-family:"Calibri","sans-serif";=0A=09mso-ascii-font-family:Calibr=
i;=0A=09mso-ascii-theme-font:minor-latin;=0A=09mso-fareast-font-family:"Tim=
es New Roman";=0A=09mso-fareast-theme-font:minor-fareast;=0A=09mso-hansi-fo=
nt-family:Calibri;=0A=09mso-hansi-theme-font:minor-latin;}=0A</style>=0A<![=
endif]--><!--[if gte mso 9]><xml>=0A <o:shapedefaults v:ext=3D"edit" spidma=
x=3D"1026"/>=0A</xml><![endif]--><!--[if gte mso 9]><xml>=0A <o:shapelayout=
 v:ext=3D"edit">=0A  <o:idmap v:ext=3D"edit" data=3D"1"/>=0A </o:shapelayou=
t></xml><![endif]-->=0A=0A</div><div class=3D"MsoCommentText">Scaling prope=
rties of the mechanism are proportional to=0Athe number of distinct</div><d=
iv class=3D"MsoCommentText">(ingress, egress) pairs of active communication=
s.=0AIntuitively, the mechanism will</div><div class=3D"MsoCommentText">pro=
vide better scaling properties than=0Atraditional dynamic routing protocols=
 if</div><div class=3D"MsoCommentText">the number of active pairs is sparse=
=0Ain relation to the number of nodes on the</div><div class=3D"MsoCommentT=
ext">link. Quantitative analysis would be=0Athrough experimentation after p=
ublication.</div>=0A=0A<div><br>&gt;In general, the draft appears to be mix=
ing the concepts of service provider<br>&gt;and end-user networks in strang=
e ways.&nbsp; The AERO link uses host-based<br>&gt;mechanisms for prefix de=
legation, but it is intended to be a backbone of<br>&gt;a service provider =
network.&nbsp; There seem to be some trust assumptions<br>&gt;borrowed from=
 access links (such as the need for ingress filtering), yet<br>&gt;the rout=
ers on the AERO link are expected to work together in a peer-to-<br>&gt;pee=
r fashion to compute direct routes to each other.&nbsp; I do not feel that =
the<br>&gt;draft has adequately motivated this somewhat quirky set of assum=
ptions.<br>&gt;Perhaps a deployment example that motivates why the differen=
t edge<br>&gt;routers cannot trust each other is in order.</div><div><br></=
div><div><!--[if gte mso 9]><xml>=0A <w:WordDocument>=0A  <w:View>Normal</w=
:View>=0A  <w:Zoom>0</w:Zoom>=0A  <w:TrackMoves/>=0A  <w:TrackFormatting/>=
=0A  <w:PunctuationKerning/>=0A  <w:ValidateAgainstSchemas/>=0A  <w:SaveIfX=
MLInvalid>false</w:SaveIfXMLInvalid>=0A  <w:IgnoreMixedContent>false</w:Ign=
oreMixedContent>=0A  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceh=
olderText>=0A  <w:DoNotPromoteQF/>=0A  <w:LidThemeOther>EN-US</w:LidThemeOt=
her>=0A  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>=0A  <w:LidThemeComplexSc=
ript>X-NONE</w:LidThemeComplexScript>=0A  <w:Compatibility>=0A   <w:BreakWr=
appedTables/>=0A   <w:SnapToGridInCell/>=0A   <w:WrapTextWithPunct/>=0A   <=
w:UseAsianBreakRules/>=0A   <w:DontGrowAutofit/>=0A   <w:SplitPgBreakAndPar=
aMark/>=0A   <w:DontVertAlignCellWithSp/>=0A   <w:DontBreakConstrainedForce=
dTables/>=0A   <w:DontVertAlignInTxbx/>=0A   <w:Word11KerningPairs/>=0A   <=
w:CachedColBalance/>=0A  </w:Compatibility>=0A  <m:mathPr>=0A   <m:mathFont=
 m:val=3D"Cambria Math"/>=0A   <m:brkBin m:val=3D"before"/>=0A   <m:brkBinS=
ub m:val=3D"&#45;-"/>=0A   <m:smallFrac m:val=3D"off"/>=0A   <m:dispDef/>=
=0A   <m:lMargin m:val=3D"0"/>=0A   <m:rMargin m:val=3D"0"/>=0A   <m:defJc =
m:val=3D"centerGroup"/>=0A   <m:wrapIndent m:val=3D"1440"/>=0A   <m:intLim =
m:val=3D"subSup"/>=0A   <m:naryLim m:val=3D"undOvr"/>=0A  </m:mathPr></w:Wo=
rdDocument>=0A</xml><![endif]--><!--[if gte mso 9]><xml>=0A <w:LatentStyles=
 DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"=0A  DefSemiHidden=3D"t=
rue" DefQFormat=3D"false" DefPriority=3D"99"=0A  LatentStyleCount=3D"267">=
=0A  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 2"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"h=
eading 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"=
true" Name=3D"heading 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"9" QFormat=3D"true" Name=3D"heading 5"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"9" QFormat=3D"true" Name=3D"heading 6"/>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 7"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"h=
eading 8"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"=
true" Name=3D"heading 9"/>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"39" Name=3D"toc 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" =
Name=3D"toc 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=
=3D"toc 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"t=
oc 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"=
/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>=0A=
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>=0A  <w:LsdExcepti=
on Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D"caption"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph Font"/>=0A  =
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"=0A   =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>=0A  <w:LsdExc=
eption Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"=0A   UnhideWhe=
nUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"20" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fa=
lse" QFormat=3D"true" Name=3D"Emphasis"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"59" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Table Grid"/>=0A  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"fa=
lse" Name=3D"Placeholder Text"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"1" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=3D"tru=
e" Name=3D"No Spacing"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"6=
0" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Shading=
"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"fals=
e"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List"/>=0A  <w:LsdException =
Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Light Grid"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Mediu=
m Shading 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHid=
den=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fa=
lse" Name=3D"Medium List 2"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium G=
rid 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   UnhideWh=
enUsed=3D"false" Name=3D"Medium Grid 3"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Dark List"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" SemiH=
idden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Colorful Grid"/>=0A  <w:LsdException Locked=3D"false" Pr=
iority=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Li=
ght Shading Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"61=
" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List Acc=
ent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=0A   Un=
hideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWhenU=
sed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fa=
lse" Name=3D"Medium List 1 Accent 1"/>=0A  <w:LsdException Locked=3D"false"=
 UnhideWhenUsed=3D"false" Name=3D"Revision"/>=0A  <w:LsdException Locked=3D=
"false" Priority=3D"34" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" =
QFormat=3D"true" Name=3D"List Paragraph"/>=0A  <w:LsdException Locked=3D"fa=
lse" Priority=3D"29" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFo=
rmat=3D"true" Name=3D"Quote"/>=0A  <w:LsdException Locked=3D"false" Priorit=
y=3D"30" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true=
" Name=3D"Intense Quote"/>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List=
 2 Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHid=
den=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"=
/>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false=
"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   Unhid=
eWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D=
"false" Name=3D"Dark List Accent 1"/>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"=
Colorful Shading Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful=
 List Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"73" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent=
 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=0A   Un=
hideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D=
"false" Name=3D"Light Grid Accent 2"/>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D=
"Medium Shading 1 Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium S=
hading 2 Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"65" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Acc=
ent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=0A   UnhideWhenU=
sed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Medium Grid 3 Accent 2"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"D=
ark List Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading =
Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"61" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Light List Accent 3"/>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"=
Light Grid Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"63"=
 SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading =
1 Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidd=
en=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent =
3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"fal=
se"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=0A   Unh=
ideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Medium Grid 1 Accent 3"/>=0A  <w:LsdException Locked=3D"=
false" Priority=3D"68" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" N=
ame=3D"Medium Grid 2 Accent 3"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"69" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Mediu=
m Grid 3 Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"70" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent =
3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"fal=
se"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>=0A  =
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=0A   =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUs=
ed=3D"false" Name=3D"Colorful Grid Accent 3"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Light Shading Accent 4"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"61" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"L=
ight List Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" =
SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accen=
t 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"f=
alse"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>=0A=
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=0A =
  UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>=0A  <w:LsdE=
xception Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A   UnhideW=
henUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>=0A  <w:LsdException Loc=
ked=3D"false" Priority=3D"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"f=
alse" Name=3D"Medium List 2 Accent 4"/>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Medium Grid 1 Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"68" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium G=
rid 2 Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"69" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent=
 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Colorful List Accent 4"/>=0A  <w:LsdException Locked=3D"=
false" Priority=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" N=
ame=3D"Colorful Grid Accent 4"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light=
 Shading Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"61" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List Accent=
 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=0A   Unhid=
eWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Medium Shading 2 Accent 5"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Medium List 1 Accent 5"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"M=
edium List 2 Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"6=
7" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1=
 Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidde=
n=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Dark List Accent 5"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Colorful Shading Accent 5"/>=0A  <w:LsdException Locked=3D"false=
" Priority=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Colorful List Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful=
 Grid Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent=
 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   Unhid=
eWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fa=
lse" Name=3D"Medium Shading 1 Accent 6"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Medium Shading 2 Accent 6"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Mediu=
m List 1 Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"66" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Acc=
ent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   UnhideWhenU=
sed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Dark List Accent 6"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Color=
ful Shading Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"72=
" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful List =
Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D"=
TOC Heading"/>=0A </w:LatentStyles>=0A</xml><![endif]--><!--[if gte mso 10]=
>=0A<style>=0A /* Style Definitions */=0A table.MsoNormalTable=0A=09{mso-st=
yle-name:"Table Normal";=0A=09mso-tstyle-rowband-size:0;=0A=09mso-tstyle-co=
lband-size:0;=0A=09mso-style-noshow:yes;=0A=09mso-style-priority:99;=0A=09m=
so-style-qformat:yes;=0A=09mso-style-parent:"";=0A=09mso-padding-alt:0in 5.=
4pt 0in 5.4pt;=0A=09mso-para-margin-top:0in;=0A=09mso-para-margin-right:0in=
;=0A=09mso-para-margin-bottom:10.0pt;=0A=09mso-para-margin-left:0in;=0A=09l=
ine-height:115%;=0A=09mso-pagination:widow-orphan;=0A=09font-size:11.0pt;=
=0A=09font-family:"Calibri","sans-serif";=0A=09mso-ascii-font-family:Calibr=
i;=0A=09mso-ascii-theme-font:minor-latin;=0A=09mso-fareast-font-family:"Tim=
es New Roman";=0A=09mso-fareast-theme-font:minor-fareast;=0A=09mso-hansi-fo=
nt-family:Calibri;=0A=09mso-hansi-theme-font:minor-latin;}=0A</style>=0A<![=
endif]-->=0A=0A</div><div class=3D"MsoCommentText">A deployment example cou=
ld be added as a new Section=0A4.4 (causing existing</div><div class=3D"Mso=
CommentText">Sections 4.4 onward to be renumbered beginning with=0ASection =
4.5). The new</div><div class=3D"MsoCommentText">Section could read:</div>=
=0A=0A<div class=3D"MsoCommentText">&nbsp;</div>=0A=0A<div class=3D"MsoComm=
entText">=E2=80=9CAs a simple example, consider a large service provider=0A=
network that is extended</div><div class=3D"MsoCommentText">primarily using=
 L2 bridges instead of L3 routers. The=0Anetwork is therefore seen as</div>=
<div class=3D"MsoCommentText">a single link by the IP layer. In that case, =
a new=0Aspoofing attack vector is open to</div><div class=3D"MsoCommentText=
">malicious nodes on the link that could send=0Apackets with spoofed IP sou=
rce</div><div class=3D"MsoCommentText">addresses with low probability of de=
tection,=0Ae.g., to initiate a DoS attack directed</div><div class=3D"MsoCo=
mmentText">to some other node on the link. AERO=0Atherefore applies to link=
s on which attached</div><div class=3D"MsoCommentText">nodes do not necessa=
rily trust=0Aeach other.=E2=80=9D</div>=0A=0A<div><br>&gt;Minor issues:<br>=
&gt;<br>&gt;Section 4.4.5:<br>&gt;The text says to use experimental type co=
de "100" but the ASCII art<br>&gt;still says "137."&nbsp; Does the figure n=
eed to be changed?<span style=3D"font-size: 11pt; line-height: 115%; font-f=
amily: &quot;Calibri&quot;,&quot;sans-serif&quot;;"></span></div><div><br><=
span style=3D"font-size: 11pt; line-height: 115%; font-family: &quot;Calibr=
i&quot;,&quot;sans-serif&quot;;"></span><span style=3D"font-size:11.0pt;lin=
e-height:115%;=0Afont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso=
-ascii-theme-font:minor-latin;mso-fareast-font-family:=0ACalibri;mso-fareas=
t-theme-font:minor-latin;mso-hansi-theme-font:minor-latin;=0Amso-bidi-font-=
family:&quot;Times New Roman&quot;;mso-bidi-theme-font:minor-bidi;=0Amso-an=
si-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA"></spa=
n></div><div>Yes; the figure is incorrect, and will be corrected to say "10=
0".<br><br>&gt;Section 4.4.12:<br>&gt;&nbsp;&nbsp;&nbsp;Eventually, any suc=
h correspondent AERO nodes will receive a NULL<br>&gt;&nbsp;&nbsp;&nbsp;AER=
O Redirect message and will cease to use the egress node ('D') as<br>&gt;&n=
bsp;&nbsp;&nbsp;a next hop.&nbsp; They will then revert to sending packets =
destined to the<br>&gt;&nbsp;&nbsp;&nbsp;EUN node ('E') via a trusted inter=
mediate router and may subsequently<br>&gt;&nbsp;&nbsp;&nbsp;receive new AE=
RO Redirect messages to discover that the EUN node ('E'<br>&gt;&nbsp;&nbsp;=
&nbsp;) is now associated with a new AERO edge router.<br>&gt;Seems like th=
is scenario requires that *part* of a prefix that was delegated<br>&gt;to D=
 is now re-routed by the intermediate router A to a different destination.<=
br>&gt;Is that correct?&nbsp; You are proposing to punch a
 hole in the original allocation,<br>&gt;and put in a more-specific (perhap=
s host-specific) route to E through a new<br>&gt;path?&nbsp; What kind of p=
rotocols would be used to establish this new forwarding<br>&gt;state?</div>=
<div><br></div><div><!--[if gte mso 9]><xml>=0A <w:WordDocument>=0A  <w:Vie=
w>Normal</w:View>=0A  <w:Zoom>0</w:Zoom>=0A  <w:TrackMoves/>=0A  <w:TrackFo=
rmatting/>=0A  <w:PunctuationKerning/>=0A  <w:ValidateAgainstSchemas/>=0A  =
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>=0A  <w:IgnoreMixedContent>fa=
lse</w:IgnoreMixedContent>=0A  <w:AlwaysShowPlaceholderText>false</w:Always=
ShowPlaceholderText>=0A  <w:DoNotPromoteQF/>=0A  <w:LidThemeOther>EN-US</w:=
LidThemeOther>=0A  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>=0A  <w:LidThem=
eComplexScript>X-NONE</w:LidThemeComplexScript>=0A  <w:Compatibility>=0A   =
<w:BreakWrappedTables/>=0A   <w:SnapToGridInCell/>=0A   <w:WrapTextWithPunc=
t/>=0A   <w:UseAsianBreakRules/>=0A   <w:DontGrowAutofit/>=0A   <w:SplitPgB=
reakAndParaMark/>=0A   <w:DontVertAlignCellWithSp/>=0A   <w:DontBreakConstr=
ainedForcedTables/>=0A   <w:DontVertAlignInTxbx/>=0A   <w:Word11KerningPair=
s/>=0A   <w:CachedColBalance/>=0A  </w:Compatibility>=0A  <m:mathPr>=0A   <=
m:mathFont m:val=3D"Cambria Math"/>=0A   <m:brkBin m:val=3D"before"/>=0A   =
<m:brkBinSub m:val=3D"&#45;-"/>=0A   <m:smallFrac m:val=3D"off"/>=0A   <m:d=
ispDef/>=0A   <m:lMargin m:val=3D"0"/>=0A   <m:rMargin m:val=3D"0"/>=0A   <=
m:defJc m:val=3D"centerGroup"/>=0A   <m:wrapIndent m:val=3D"1440"/>=0A   <m=
:intLim m:val=3D"subSup"/>=0A   <m:naryLim m:val=3D"undOvr"/>=0A  </m:mathP=
r></w:WordDocument>=0A</xml><![endif]--><!--[if gte mso 9]><xml>=0A <w:Late=
ntStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"=0A  DefSemiHid=
den=3D"true" DefQFormat=3D"false" DefPriority=3D"99"=0A  LatentStyleCount=
=3D"267">=0A  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>=0A=
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>=0A  <w:LsdE=
xception Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 2=
"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Na=
me=3D"heading 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" QFor=
mat=3D"true" Name=3D"heading 4"/>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"9" QFormat=3D"true" Name=3D"heading 5"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 6"/>=0A  <w:LsdE=
xception Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 7=
"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Na=
me=3D"heading 8"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" QFor=
mat=3D"true" Name=3D"heading 9"/>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"39" Name=3D"toc 1"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"39" Name=3D"toc 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"3=
9" Name=3D"toc 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Na=
me=3D"toc 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D=
"toc 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc =
6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>=0A  =
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>=0A  <w:Ls=
dException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D"captio=
n"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"fal=
se"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph Font=
"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"fals=
e"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"=0A   U=
nhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"=0A   UnhideWhenUs=
ed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>=0A  <w:LsdException Locke=
d=3D"false" Priority=3D"59" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fal=
se" Name=3D"Table Grid"/>=0A  <w:LsdException Locked=3D"false" UnhideWhenUs=
ed=3D"false" Name=3D"Placeholder Text"/>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"1" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QForma=
t=3D"true" Name=3D"No Spacing"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light=
 Shading"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List"/>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWh=
enUsed=3D"false" Name=3D"Light Grid"/>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D=
"Medium Shading 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"=
/>=0A  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false=
"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Medium List 2"/>=0A  <w:LsdException Locked=3D"false" Pr=
iority=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Me=
dium Grid 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHid=
den=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   Un=
hideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Dark List"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"71=
" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Shadi=
ng"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=0A   UnhideWhenU=
sed=3D"false" Name=3D"Colorful Grid"/>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D=
"Light Shading Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"61" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List =
Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWh=
enUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D=
"false" Name=3D"Medium List 1 Accent 1"/>=0A  <w:LsdException Locked=3D"fal=
se" UnhideWhenUsed=3D"false" Name=3D"Revision"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"34" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" QFormat=3D"true" Name=3D"List Paragraph"/>=0A  <w:LsdException Locked=3D=
"false" Priority=3D"29" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" =
QFormat=3D"true" Name=3D"Quote"/>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"30" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=3D"t=
rue" Name=3D"Intense Quote"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium L=
ist 2 Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent=
 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   Un=
hideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Dark List Accent 1"/>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Colorful Shading Accent 1"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Color=
ful List Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"73" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Acc=
ent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Light Grid Accent 2"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Medium Shading 1 Accent 2"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Mediu=
m Shading 2 Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"65=
" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 =
Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Medium Grid 3 Accent 2"/>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Dark List Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"=
71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Sha=
ding Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" SemiH=
idden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent =
2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"fal=
se"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=0A   Unh=
ideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Light List Accent 3"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Light Grid Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shad=
ing 1 Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Acc=
ent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=0A   UnhideWhenU=
sed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"68" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Medium Grid 2 Accent 3"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"69" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"M=
edium Grid 3 Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"7=
0" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Dark List Acc=
ent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Light Shading Accent 4"/>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"61" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Light List Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Grid =
Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"=
/>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false=
"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A   Un=
hideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Medium List 2 Accent 4"/>=0A  <w:LsdException Locked=3D"=
false" Priority=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" N=
ame=3D"Medium Grid 1 Accent 4"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"68" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Mediu=
m Grid 2 Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"69" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Acc=
ent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=0A   Unh=
ideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUs=
ed=3D"false" Name=3D"Colorful List Accent 4"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Colorful Grid Accent 4"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"L=
ight Shading Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"6=
1" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List Ac=
cent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWh=
enUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D=
"false" Name=3D"Medium List 1 Accent 5"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Medium List 2 Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium G=
rid 1 Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent=
 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   Un=
hideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Colorful Shading Accent 5"/>=0A  <w:LsdException Locked=3D"f=
alse" Priority=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Na=
me=3D"Colorful List Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priori=
ty=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorf=
ul Grid Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" Se=
miHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Shading Acce=
nt 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"=
false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   Unh=
ideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Medium Shading 1 Accent 6"/>=0A  <w:LsdException Locked=3D"f=
alse" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Na=
me=3D"Medium Shading 2 Accent 6"/>=0A  <w:LsdException Locked=3D"false" Pri=
ority=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Med=
ium List 1 Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"66"=
 SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 A=
ccent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Dark List Accent 6"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"C=
olorful Shading Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful=
 List Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"73" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent=
 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis=
"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"fals=
e"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"=
/>=0A  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false=
"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/=
>=0A  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D"=
TOC Heading"/>=0A </w:LatentStyles>=0A</xml><![endif]--><!--[if gte mso 10]=
>=0A<style>=0A /* Style Definitions */=0A table.MsoNormalTable=0A=09{mso-st=
yle-name:"Table Normal";=0A=09mso-tstyle-rowband-size:0;=0A=09mso-tstyle-co=
lband-size:0;=0A=09mso-style-noshow:yes;=0A=09mso-style-priority:99;=0A=09m=
so-style-qformat:yes;=0A=09mso-style-parent:"";=0A=09mso-padding-alt:0in 5.=
4pt 0in 5.4pt;=0A=09mso-para-margin-top:0in;=0A=09mso-para-margin-right:0in=
;=0A=09mso-para-margin-bottom:10.0pt;=0A=09mso-para-margin-left:0in;=0A=09l=
ine-height:115%;=0A=09mso-pagination:widow-orphan;=0A=09font-size:11.0pt;=
=0A=09font-family:"Calibri","sans-serif";=0A=09mso-ascii-font-family:Calibr=
i;=0A=09mso-ascii-theme-font:minor-latin;=0A=09mso-fareast-font-family:"Tim=
es New Roman";=0A=09mso-fareast-theme-font:minor-fareast;=0A=09mso-hansi-fo=
nt-family:Calibri;=0A=09mso-hansi-theme-font:minor-latin;}=0A</style>=0A<![=
endif]-->=0A=0A</div><div class=3D"MsoCommentText">Punching a hole in a sho=
rt aggregated prefix is one=0Apossibility, but another</div><div class=3D"M=
soCommentText">possibility is that the edge router is delegated many=0Anon-=
aggregated long</div><div class=3D"MsoCommentText">prefixes. In that case, =
the mobile node can take its long=0Aprefix to a new</div><div class=3D"MsoC=
ommentText">edge router without the old edge router needing to punch any=0A=
holes.</div>=0A=0A<div><br>&gt;Nits/editorial comments:<br>&gt;<br>&gt;Sect=
ion 4.4.4:<br>&gt;&nbsp;&nbsp;&nbsp;Note that on links in which link-layer =
address spoofing is possible,<br>&gt;&nbsp;&nbsp;&nbsp;AERO nodes may be ob=
liged to require the use of digital signatures.<br>&gt;&nbsp;&nbsp;&nbsp;In=
 that case, only the third of the above conditions can be accepted<br>&gt;&=
nbsp;&nbsp;&nbsp;in order to ensure adequate data origin authentication.<br=
>&gt;Did you mean to say "only the fourth of the above conditions can be<br=
>&gt;accepted..."? <br></div><div><br></div><div>You are correct; this was =
also mentioned in an earlier comment and</div><div>will be fixed in the nex=
t document version.<br></div><div><br></div><div>&gt;Section 5:<br>&gt;You =
say there are no IANA considerations, but do you need an experimental<br>&g=
t;ICMPv6 type code allocated?</div><div><br></div><div><!--[if gte mso 9]><=
xml>=0A <w:WordDocument>=0A  <w:View>Normal</w:View>=0A  <w:Zoom>0</w:Zoom>=
=0A  <w:TrackMoves/>=0A  <w:TrackFormatting/>=0A  <w:PunctuationKerning/>=
=0A  <w:ValidateAgainstSchemas/>=0A  <w:SaveIfXMLInvalid>false</w:SaveIfXML=
Invalid>=0A  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>=0A  <w:Alwa=
ysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>=0A  <w:DoNotPromo=
teQF/>=0A  <w:LidThemeOther>EN-US</w:LidThemeOther>=0A  <w:LidThemeAsian>X-=
NONE</w:LidThemeAsian>=0A  <w:LidThemeComplexScript>X-NONE</w:LidThemeCompl=
exScript>=0A  <w:Compatibility>=0A   <w:BreakWrappedTables/>=0A   <w:SnapTo=
GridInCell/>=0A   <w:WrapTextWithPunct/>=0A   <w:UseAsianBreakRules/>=0A   =
<w:DontGrowAutofit/>=0A   <w:SplitPgBreakAndParaMark/>=0A   <w:DontVertAlig=
nCellWithSp/>=0A   <w:DontBreakConstrainedForcedTables/>=0A   <w:DontVertAl=
ignInTxbx/>=0A   <w:Word11KerningPairs/>=0A   <w:CachedColBalance/>=0A  </w=
:Compatibility>=0A  <m:mathPr>=0A   <m:mathFont m:val=3D"Cambria Math"/>=0A=
   <m:brkBin m:val=3D"before"/>=0A   <m:brkBinSub m:val=3D"&#45;-"/>=0A   <=
m:smallFrac m:val=3D"off"/>=0A   <m:dispDef/>=0A   <m:lMargin m:val=3D"0"/>=
=0A   <m:rMargin m:val=3D"0"/>=0A   <m:defJc m:val=3D"centerGroup"/>=0A   <=
m:wrapIndent m:val=3D"1440"/>=0A   <m:intLim m:val=3D"subSup"/>=0A   <m:nar=
yLim m:val=3D"undOvr"/>=0A  </m:mathPr></w:WordDocument>=0A</xml><![endif]-=
-><!--[if gte mso 9]><xml>=0A <w:LatentStyles DefLockedState=3D"false" DefU=
nhideWhenUsed=3D"true"=0A  DefSemiHidden=3D"true" DefQFormat=3D"false" DefP=
riority=3D"99"=0A  LatentStyleCount=3D"267">=0A  <w:LsdException Locked=3D"=
false" Priority=3D"0" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QF=
ormat=3D"true" Name=3D"Normal"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"9" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=3D"tru=
e" Name=3D"heading 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"9"=
 QFormat=3D"true" Name=3D"heading 2"/>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"9" QFormat=3D"true" Name=3D"heading 3"/>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 4"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"head=
ing 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"tru=
e" Name=3D"heading 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"9"=
 QFormat=3D"true" Name=3D"heading 7"/>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"9" QFormat=3D"true" Name=3D"heading 8"/>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"heading 9"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>=0A  <w:LsdE=
xception Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"39" Name=3D"toc 4"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"39" Name=3D"toc 5"/>=0A  <w:LsdException Locked=3D"f=
alse" Priority=3D"39" Name=3D"toc 6"/>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"39" Name=3D"toc 7"/>=0A  <w:LsdException Locked=3D"false" Prio=
rity=3D"39" Name=3D"toc 8"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"39" Name=3D"toc 9"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"3=
5" QFormat=3D"true" Name=3D"caption"/>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"10" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=
=3D"true" Name=3D"Title"/>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"1" Name=3D"Default Paragraph Font"/>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"11" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=
=3D"true" Name=3D"Subtitle"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"22" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true"=
 Name=3D"Strong"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"20" Sem=
iHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Em=
phasis"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>=0A  <w:LsdEx=
ception Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeholder Text"=
/>=0A  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>=0A  <=
w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=0A   U=
nhideWhenUsed=3D"false" Name=3D"Light Shading"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"61" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Light List"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"6=
2" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUs=
ed=3D"false" Name=3D"Medium Shading 2"/>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Medium List 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"66" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Medium Grid 2"/>=0A  <w:LsdException Locked=3D"false" Pr=
iority=3D"69" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Me=
dium Grid 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHid=
den=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Colorful Shading"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Colorful List"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful=
 Grid"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>=0A  <w:LsdExceptio=
n Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Light Grid Accent 1"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Medium Shading 1 Accent 1"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Mediu=
m Shading 2 Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"65=
" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 =
Accent 1"/>=0A  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" N=
ame=3D"Revision"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"34" Sem=
iHidden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Li=
st Paragraph"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHi=
dden=3D"false"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote=
"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"fals=
e"=0A   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"68" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Medium Grid 2 Accent 1"/>=0A  <w:LsdException Locked=3D"fals=
e" Priority=3D"69" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Medium Grid 3 Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Dark Lis=
t Accent 1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidd=
en=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent =
1"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"fal=
se"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=0A   Unh=
ideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Light Shading Accent 2"/>=0A  <w:LsdException Locked=3D"=
false" Priority=3D"61" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" N=
ame=3D"Light List Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Gr=
id Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHid=
den=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent=
 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=0A   UnhideWhenU=
sed=3D"false" Name=3D"Medium List 2 Accent 2"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Medium Grid 1 Accent 2"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"68" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"M=
edium Grid 2 Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"6=
9" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3=
 Accent 2"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidde=
n=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=0A   UnhideWh=
enUsed=3D"false" Name=3D"Colorful List Accent 2"/>=0A  <w:LsdException Lock=
ed=3D"false" Priority=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fa=
lse" Name=3D"Colorful Grid Accent 2"/>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"60" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D=
"Light Shading Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D=
"61" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List =
Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>=0A  <w:LsdEx=
ception Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWh=
enUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D=
"false" Name=3D"Medium List 1 Accent 3"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"66" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=
=3D"Medium List 2 Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium G=
rid 1 Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"68" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent=
 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   Un=
hideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Colorful Shading Accent 3"/>=0A  <w:LsdException Locked=3D"f=
alse" Priority=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Na=
me=3D"Colorful List Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priori=
ty=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorf=
ul Grid Accent 3"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" Se=
miHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Shading Acce=
nt 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"=
false"=0A   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   Unh=
ideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Medium Shading 1 Accent 4"/>=0A  <w:LsdException Locked=3D"f=
alse" Priority=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Na=
me=3D"Medium Shading 2 Accent 4"/>=0A  <w:LsdException Locked=3D"false" Pri=
ority=3D"65" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Med=
ium List 1 Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"66"=
 SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 A=
ccent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Dark List Accent 4"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"71" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"C=
olorful Shading Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"72" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful=
 List Accent 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"73" Semi=
Hidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent=
 4"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"fa=
lse"=0A   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>=0A  <w=
:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"=0A   Un=
hideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>=0A  <w:LsdException L=
ocked=3D"false" Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D=
"false" Name=3D"Light Grid Accent 5"/>=0A  <w:LsdException Locked=3D"false"=
 Priority=3D"63" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D=
"Medium Shading 1 Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=
=3D"64" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium S=
hading 2 Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"65" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Acc=
ent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D=
"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>=0A =
 <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=0A  =
 UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>=0A  <w:LsdExcep=
tion Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"=0A   UnhideWhenU=
sed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"69" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" Name=3D"Medium Grid 3 Accent 5"/>=0A  <w:LsdException Locked=3D"false" P=
riority=3D"70" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"D=
ark List Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading =
Accent 5"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=
=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>=
=0A  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=
=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>=0A  <w:Lsd=
Exception Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"=0A   Unhide=
WhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>=0A  <w:LsdException Lo=
cked=3D"false" Priority=3D"61" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"=
false" Name=3D"Light List Accent 6"/>=0A  <w:LsdException Locked=3D"false" =
Priority=3D"62" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"=
Light Grid Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"63"=
 SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading =
1 Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidd=
en=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent =
6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"fal=
se"=0A   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>=0A  <w:=
LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"=0A   Unh=
ideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>=0A  <w:LsdException=
 Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"=0A   UnhideWhenUsed=
=3D"false" Name=3D"Medium Grid 1 Accent 6"/>=0A  <w:LsdException Locked=3D"=
false" Priority=3D"68" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" N=
ame=3D"Medium Grid 2 Accent 6"/>=0A  <w:LsdException Locked=3D"false" Prior=
ity=3D"69" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Mediu=
m Grid 3 Accent 6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"70" S=
emiHidden=3D"false"=0A   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent =
6"/>=0A  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"fal=
se"=0A   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>=0A  =
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"=0A   =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>=0A  <w:LsdExcept=
ion Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"=0A   UnhideWhenUs=
ed=3D"false" Name=3D"Colorful Grid Accent 6"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"19" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" QFormat=3D"true" Name=3D"Subtle Emphasis"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"21" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" QFormat=3D"true" Name=3D"Intense Emphasis"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"31" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" QFormat=3D"true" Name=3D"Subtle Reference"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"32" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" QFormat=3D"true" Name=3D"Intense Reference"/>=0A  <w:LsdException Locked=
=3D"false" Priority=3D"33" SemiHidden=3D"false"=0A   UnhideWhenUsed=3D"fals=
e" QFormat=3D"true" Name=3D"Book Title"/>=0A  <w:LsdException Locked=3D"fal=
se" Priority=3D"37" Name=3D"Bibliography"/>=0A  <w:LsdException Locked=3D"f=
alse" Priority=3D"39" QFormat=3D"true" Name=3D"TOC Heading"/>=0A </w:Latent=
Styles>=0A</xml><![endif]--><!--[if gte mso 10]>=0A<style>=0A /* Style Defi=
nitions */=0A table.MsoNormalTable=0A=09{mso-style-name:"Table Normal";=0A=
=09mso-tstyle-rowband-size:0;=0A=09mso-tstyle-colband-size:0;=0A=09mso-styl=
e-noshow:yes;=0A=09mso-style-priority:99;=0A=09mso-style-qformat:yes;=0A=09=
mso-style-parent:"";=0A=09mso-padding-alt:0in 5.4pt 0in 5.4pt;=0A=09mso-par=
a-margin-top:0in;=0A=09mso-para-margin-right:0in;=0A=09mso-para-margin-bott=
om:10.0pt;=0A=09mso-para-margin-left:0in;=0A=09line-height:115%;=0A=09mso-p=
agination:widow-orphan;=0A=09font-size:11.0pt;=0A=09font-family:"Calibri","=
sans-serif";=0A=09mso-ascii-font-family:Calibri;=0A=09mso-ascii-theme-font:=
minor-latin;=0A=09mso-fareast-font-family:"Times New Roman";=0A=09mso-farea=
st-theme-font:minor-fareast;=0A=09mso-hansi-font-family:Calibri;=0A=09mso-h=
ansi-theme-font:minor-latin;}=0A</style>=0A<![endif]-->=0A=0A</div><div cla=
ss=3D"MsoCommentText">No new experimental ICMPv6 code type needs to be=0Aal=
located, since RFC4443</div>=0A=0A<div>sets aside the value =E2=80=9C100=E2=
=80=9D as an experimental ICMPv6=0Acode point.<br>&gt;</div></div></body></=
html>
---2012143828-282926690-1335279507=:26159--

From alexey.melnikov@isode.com  Tue Apr 24 08:06:20 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 E3FDF21F87B9; Tue, 24 Apr 2012 08:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, 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 h-E6KHt8TJZc; Tue, 24 Apr 2012 08:06:18 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 426CA21F8610; Tue, 24 Apr 2012 08:06:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1335279971; d=isode.com; s=selector; i=@isode.com; bh=bGWfEmN/Kqlk3MUYRJ5mQixliT/6EKtfO/SfTXFIWO4=; 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=WErpXfn7JrjeRZv9YVuX/yMVHSSHkhKyRxi2dbrW0qr9jR4QbTCxwiANGtB2ZZCmEzsec5 8AY4Ute41iy/8v4Y4K/Qe0FwY0LvnCCnQIQ3/vfsd6u3XbgzIVWZpsCGAa/RQBnF6Z0X/g o/2/9r5Jg5JEc3wkK3DoTlzJtLxmDaA=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T5bBYgAg25I3@rufus.isode.com>; Tue, 24 Apr 2012 16:06:11 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F96C173.3020706@isode.com>
Date: Tue, 24 Apr 2012 16:06:27 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Adam Roach <adam@nostrum.com>
References: <CAHBDyN6PN-vp9wXo6fF8G4VfODXjkfbWBaJN8EPopeWfOg9PmQ@mail.gmail.com> <4F840F94.1080703@isode.com> <4F85FF98.8000102@nostrum.com>
In-Reply-To: <4F85FF98.8000102@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, The IESG <iesg@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-sipcore-rfc3265bis-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2012 15:06:20 -0000

Hi Adam,
Sorry I've missed your reply earlier.

On 11/04/2012 23:03, Adam Roach wrote:
> On 4/10/12 5:46 AM, Alexey Melnikov wrote:
  [...]
>> Also, it might be good to reference RFC 3986 for URIs here.
> Given that SIP uses URIs everywhere, I'm not sure what benefit is 
> derived by referencing the URI syntax draft here.
Ok.

>>
>> 4.4.4.  Allow-Events header field usage
>>
>>    The "Allow-Events" header field does not include a list of the etvent
>>
>>  typo: event
>
> I don't find "etvent" in the document:
>
> http://tools.ietf.org/html/draft-ietf-sipcore-rfc3265bis-07#section-4.4.4
>
> Is it possible you accidentally edited a local copy of the file prior 
> to your review?
It is possible. Not a big deal either way.
> I also don't find this typo in the source (which would surprise me in 
> any case, as I made sure to run the -07 version through a spell checker).
>>
>>    template packages supported by an implementation.  If a subscriber
>>    wishes to determine which event template packages are supported by a
>>    notifier, it can probe for such support by attempting to subscribe to
>>    the event template packages it wishes to use.
>>
>> Can you clarify how such request would look like? An example would be 
>> nice.
>
> I'm not sure what you're asking for here. It would be a SUBSCRIBE 
> message, with an "Event" header field set to name the template you 
> want to use. Basically it just says "we don't negotiate templates -- 
> just try it and see if it fails." 
So my understanding is that it is not possible to just request a 
template event (it needs to be combined with something else)? I think 
some explanation and/or examples of this would be good, I don't think 
this is very clear in the document.
  [...]

>> 7.2.  Reason Codes
>>
>>    This document further defines "reason" codes for use in the
>>    "Subscription-State" header field (see Section 4.1.3).
>>
>>    Following the policies outlined in "Guidelines for Writing an IANA
>>    Considerations Section in RFCs" [RFC5226], new reason codes require a
>>    Standards Action.
>>
>> Minor: This would prevent registration of new Reason Codes in an 
>> Experimental RFC (for example). I would like to double check that 
>> that is intentional.
>
> It never came up explicitly during working group discussions, to my 
> memory.
>
>>    Registrations with the IANA include the reason code being registered
>>    and a reference to a published document which describes the event
>>    package.  Insertion of such values takes place as part of the RFC
>>    publication process or as the result of inter-SDO liaison activity.
>>
>> I don't think Standards Action allows for "inter-SDO liaison 
>> activity", unless such documents from other SDOs are published as 
>> Standard Track RFCs. So I find your text confusing: either your 
>> registration procedure should also allow for direct IESG approvals 
>> (to allow registrations from other SDOs with no RFCs), or you should 
>> remove "as the result of inter-SDO liaison activity".
>
> You're right. I suspect we really intended to make this registrable by 
> external SDOs, meaning we probably really wanted Specification 
> Required. I'm leaving this as-is for now, and will need to coordinate 
> with our AD to iron out where to go with this.
>
Ok, I will tell Russ that these 2 issues are still pending resolution.
>> 8.4.  Augmented BNF Definitions
>>
>>    event-type        =  event-package *( "." event-template )
>>
>> Minor: Does this mean that multiple template packages can be applied?
>> Is there any ordering for them?
> Yes, and yes.
>> How would "foo.A.B" differ from "foo.B.A"?
>
> Right now, we have only one template defined -- but imagine that we 
> did define a new "list" template event package (we almost did this 
> some years ago) which is used to aggregate several resources into a 
> single subscription.
>
> "Event: presence.winfo.list" would subscribe to the aggregation of 
> several watcher-info documents into a single list.
>
> "Event: presence.list.winfo" would subscribe to the watcher-info state 
> of the indicated list.
Ok, so the ordering is important. Is this documented anywhere?
>
>> Nit: id-nits complains:
>>
>>   -- Duplicate reference: RFC4660, mentioned in 'RFC4660', was also 
>> mentioned
>>      in 'RFC 4660'.
>>
>> "[RFC 4660]" reference is used in section 7.2.
>
> id-nits is wrong. It incorrectly thinks that the paragraph starting 
> with [RFC4660] on page 40 is trying to define a reference.
I thought it was a reference, but this is not a big deal.


From msk@cloudmark.com  Tue Apr 24 15:28:11 2012
Return-Path: <msk@cloudmark.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 2714521F86D8 for <gen-art@ietfa.amsl.com>; Tue, 24 Apr 2012 15:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Level: 
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, 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 cDzaeF5q-+io for <gen-art@ietfa.amsl.com>; Tue, 24 Apr 2012 15:28:10 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id 4E21121F86D6 for <gen-art@ietf.org>; Tue, 24 Apr 2012 15:28:09 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.25]) by mail.cloudmark.com with bizsmtp id 1yUL1j0010ZaKgw01yULRw; Tue, 24 Apr 2012 15:28:29 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=fNu7LOme c=1 sm=1 a=LdFkGDrDWH2mcjCZERnC4w==:17 a=LvckAehuu68A:10 a=XDoa0A5SzUQA:10 a=zutiEJmiVI4A:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=G0_B3m8xAAAA:8 a=48vgC7mUAAAA:8 a=k7Ga1wGzAAAA:8 a=eWNgu4SYTvBnYhoLPl0A:9 a=bNehmqa9pE8moRC2vJUA:7 a=CjuIK1q_8ugA:10 a=lW_bInUQU2sA:10 a=lZB815dzVvQA:10 a=fcAx7uNQz4EA:10 a=LdFkGDrDWH2mcjCZERnC4w==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas901.corp.cloudmark.com ([fe80::2524:76b6:a865:539c%10]) with mapi id 14.01.0355.002; Tue, 24 Apr 2012 15:27:59 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "kathleen.moriarty@emc.com" <kathleen.moriarty@emc.com>, "draft-ietf-appsawg-greylisting.all@tools.ietf.org" <draft-ietf-appsawg-greylisting.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-Art review of draft-ietf-appsawg-greylisting
Thread-Index: Ac0hcmcyQR3NBVo/Rl6IFM4VkVIGNwA9oqgQ
Date: Tue, 24 Apr 2012 22:27:58 +0000
Message-ID: <9452079D1A51524AA5749AD23E0039281017B8@exch-mbx901.corp.cloudmark.com>
References: <AE31510960917D478171C79369B660FA0E7CB761E7@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E7CB761E7@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1335306509; bh=h2zl95gZNOhfY73Vm9wK0GuCNx5dYc+GcDU1ngI6saI=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=HbmvBfv6RBFaMDiJcCm83m4vigWDgout9kwSP+IsHYHxQua+p3oaFMCg0ZC6aUD2c h3+CNXgnkznqmecKRhxDN9eHyGyij8K5Qenwx+RtQvEJ2qb11rD08VBT5cJYclyEbe fXqwRYVDo6lMDiB3EomrrpUbQH+vnV/AECc5vCpo=
Cc: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-appsawg-greylisting
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, 24 Apr 2012 22:28:11 -0000

Hi Kathleen, thanks for the review.

> -----Original Message-----
> From: kathleen.moriarty@emc.com [mailto:kathleen.moriarty@emc.com]
> Sent: Monday, April 23, 2012 9:59 AM
> To: draft-ietf-appsawg-greylisting.all@tools.ietf.org; iesg@ietf.org; gen=
-art@ietf.org
> Cc: Murray S. Kucherawy; dcrocker@bbiw.net
> Subject: Gen-Art review of draft-ietf-appsawg-greylisting
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at <
> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd or AD before
> posting a new version of the draft.
> [...]
> Nits/editorial comments:
> Introduction: First sentence:  The word 'differential' should be
> 'different' unless you change the sentence structure.  It could be that
> there is a differential between services.

"different qualities of service" is more like what we want here, because it=
's the same service really.

> Second sentence:  Change provider to providing

Fixed.

> Section 2.1: The double dashes should be parentheses instead -- --
> replaced by ()

Done.

> Section 3, third paragraph, last sentence: add a comma:
> From: To the greylisting
>    implementation such clients are once again unknown, and they will
>    once again be subjected to the delay.
> To: To the greylisting
>    Implementation, such clients are once again unknown, and they will
>    once again be subjected to the delay.

Done.

> Section 3, fourth paragraph, second sentence: remove the comma:
> From: It has to be
>    large enough to keep the necessary history, and fast enough to avoid
>    excessive inefficiencies in the server's operations.
> To: It has to be
>    large enough to keep the necessary history and fast enough to avoid
>    excessive inefficiencies in the server's operations.

Done.

> Section 3, fifth paragraph, second to last sentence: remove "the," and
> "such"
> From: Experience suggests that
>    the, the vast majority of mail comes from places on such a developed
>    exception list, so after a training period, only a small proportion
>    of mail is actually affected.
> To: Experience suggests that
>    the vast majority of mail comes from places on a developed
>    exception list, so after a training period, only a small proportion
>    of mail is actually affected.

Done.

> Section 4.1: second to last paragraph: remove unnecessary comma:
> From: Other side effects include out-of-order delivery of related,
>    sequenced messages.
> To: Other side effects include out-of-order delivery of related
>    sequenced messages.

OK.

> Section 4.2: Second paragraph:  The commas can be removed as only two
> items are joined in the list.  When you have three or more, a comma is
> used.

Done.

-MSK

From wassim.haddad@ericsson.com  Tue Apr 24 22:11:33 2012
Return-Path: <wassim.haddad@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 587FB21F8705 for <gen-art@ietfa.amsl.com>; Tue, 24 Apr 2012 22:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6zFt4yEHWUxP for <gen-art@ietfa.amsl.com>; Tue, 24 Apr 2012 22:11:32 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9DBC621F8701 for <gen-art@ietf.org>; Tue, 24 Apr 2012 22:11:32 -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 q3P5BPbE021197; Wed, 25 Apr 2012 00:11:29 -0500
Received: from client-vpn-011.edd.ericsson.se (147.117.20.214) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.3.213.0; Wed, 25 Apr 2012 01:11:22 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 24 Apr 2012 22:11:19 -0700
Message-ID: <F66AF7B2-541D-4F63-940D-72CE228BD12B@ericsson.com>
To: Gen-art <gen-art@ietf.org>, <draft-ietf-ecrit-lost-sync.all@tools.ietf.org>
MIME-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Subject: [Gen-art]  Gen-ART review of draft-ietf-ecrit-lost-sync-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: Wed, 25 Apr 2012 05:11:33 -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 comments you may =
receive.

Document:  draft-ietf-ecrit-lost-sync-17
Reviewer: Wassim Haddad
Review Date: 2012-04-24
IETF LC End Date: 2012-04-18
IESG Telechat date: 2012-04-26

Summary: This draft is ready for publication as experimental standard =
but some=20
clarifications/re-writings would be helpful.

Major issues: None

Minor issues:=20

- Perhaps I missed it somewhere in the document, but I could not find =
the meaning of "ESRPs" (page 5)
- Suggest re-writing the last paragraph on page 8=20
- Suggest re-writing the 3-line paragraph on page 9


Regards,

Wassim H.






From ben@nostrum.com  Thu Apr 26 15:55:34 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 8F82911E8088; Thu, 26 Apr 2012 15:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.445
X-Spam-Level: 
X-Spam-Status: No, score=-102.445 tagged_above=-999 required=5 tests=[AWL=0.155, 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 tUmjYNjnvTx3; Thu, 26 Apr 2012 15:55:34 -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 5B99111E808D; Thu, 26 Apr 2012 15:55:33 -0700 (PDT)
Received: from [10.0.1.33] (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 q3QMtV9h090230 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 26 Apr 2012 17:55:32 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 26 Apr 2012 17:55:31 -0500
Message-Id: <ED4FC298-44C1-409D-9D0A-01CA75E14059@nostrum.com>
To: draft-ietf-pwe3-static-pw-status.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
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>, The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-pwe3-static-pw-status-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Apr 2012 22:55:34 -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:  (Proposed RFC 6478) (was draft-ietf-pwe3-static-pw-status-10)
Reviewer: Ben Campbell
Review Date:  2012-04-26
IETF LC End Date:  2012-04-30

**** Note: This draft has previously been approved as RFC 6478, but I =
understand we are last calling it again due to some material changes in =
AUTH48. Therefore this is a review of the diff between revision 10 and =
the text at http://www.rfc-editor.org/authors/rfc6478.txt ****


Summary:

The edited text is essentially ready for publication, but I have a =
couple of minor issues that might should be considered first.

Major issues:

None

Minor issues:

-- 5.3, last paragraph:

The last sentence changed from a non-normative statement to "This SHOULD =
cause the PE sending the PW status notification message with a PW status =
code equal to zero to stop sending and to continue normal operation."

Is that really intended as a normative statement, or a statement of =
fact? I suspect it's the latter, but if the former, then it should be =
stated more of the form "If the sending PE receives ... it SHOULD stop =
..."

-- IANA considerations:

Maybe I missed it, but I don't see a registration policy for adding =
things to the new registry. This wasn't an AUTH48 change, but it should =
probably be there.=

From mahoney@nostrum.com  Thu Apr 26 16:08:53 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 CF8F721E8048 for <gen-art@ietfa.amsl.com>; Thu, 26 Apr 2012 16:08:53 -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 uaOmjVKCcrN2 for <gen-art@ietfa.amsl.com>; Thu, 26 Apr 2012 16:08:53 -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 5310B21E8029 for <gen-art@ietf.org>; Thu, 26 Apr 2012 16:08:46 -0700 (PDT)
Received: from dn3-30.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q3QN8jZx092091 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 26 Apr 2012 18:08:45 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4F99D57E.1080807@nostrum.com>
Date: Thu, 26 Apr 2012 18:08:46 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
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: 75.53.54.121 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of LC reviews - 2012-04-26
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, 26 Apr 2012 23:08:54 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft

Alexey Melnikov       2012-05-09   
draft-ietf-netext-access-network-option-10

Vijay Gurbani         2012-05-07   
draft-ietf-appsawg-mime-default-charset-03

Wassim Haddad         2012-05-07   draft-ietf-ledbat-congestion-09


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

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


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 ulrich@herberg.name  Fri Apr 27 09:56:51 2012
Return-Path: <ulrich@herberg.name>
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 994E021F86D6 for <gen-art@ietfa.amsl.com>; Fri, 27 Apr 2012 09:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.912
X-Spam-Level: 
X-Spam-Status: No, score=-2.912 tagged_above=-999 required=5 tests=[AWL=0.063,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=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 RP+eTkvf0B3l for <gen-art@ietfa.amsl.com>; Fri, 27 Apr 2012 09:56:50 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 79C4421F8671 for <gen-art@ietf.org>; Fri, 27 Apr 2012 09:56:50 -0700 (PDT)
Received: by pbbrp16 with SMTP id rp16so1222770pbb.31 for <gen-art@ietf.org>; Fri, 27 Apr 2012 09:56:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NKqLJ892KVJ0dYOwA5GSlOq0Hrl50owbAnD+Fx6pH7A=; b=To5RWmqW7CqpqO5mGcSp+lsuxBtqZmyoyDwPhSGDiWOf/8gigX/jNkp6gJsXDHfGpJ GSYC6pSeoUQMB8hV+Ydc9KqUeJljL4kiLvnn+5KPIORnBP0yBnCuwy4vuaMRSQNPoHzb AyHk1zqemd9VKx/Hff+vMBI5Oiff+7/DNAJZM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=NKqLJ892KVJ0dYOwA5GSlOq0Hrl50owbAnD+Fx6pH7A=; b=mHb/sseNRL5kyeNWMS0P6RMpbDiXMgK+ahjuQs2pNoj1/aLlEmlJ1MdtFsP/BZ4/Aq iOVN2uis+eXX+tdlJPonVhl64Il8g1OqfSFBYAhc7dNdoULywA/coYevefN6wYnuJnky nlXXEA4xERZVaed/vUo9Q3KL8BjRN2HnEYmyMw4+aEGYIz7p1pQFN1uj9E2wYzgKQpcS +nqO5l0kk1nIxxk7NSJJn2GSTYFYSQtb8ZNsuFas3x2OWPcqX7HVoMXsu3FGqHmzDh0K 7rFTwhs6r6iHUboi/wViDAvwlMb6CkFCBl0GHShPf4onxklATMGz6CCbwZxK7DJyHzAA jUFA==
MIME-Version: 1.0
Received: by 10.68.220.2 with SMTP id ps2mr25095647pbc.109.1335545810242; Fri, 27 Apr 2012 09:56:50 -0700 (PDT)
Received: by 10.142.89.17 with HTTP; Fri, 27 Apr 2012 09:56:49 -0700 (PDT)
In-Reply-To: <4F7F12CA.9010009@joelhalpern.com>
References: <4F7E279C.3030707@nostrum.com> <4F7F12CA.9010009@joelhalpern.com>
Date: Fri, 27 Apr 2012 09:56:49 -0700
Message-ID: <CAK=bVC9EfdXVPj3b+mhjzsDyiYjOEwQEH+jQ49KcFbO4PkV=YA@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=047d7b2ee19999ce0404beabfd77
X-Gm-Message-State: ALoCoQmKE9r6H6cnAj1UekaLPuJVGSwlleakkXpbCXx2h+QX6gqE+qicgtYKvnCwxL/JuhAi0Ib0
X-Mailman-Approved-At: Fri, 27 Apr 2012 10:26:53 -0700
Cc: gen-art@ietf.org, manet@ietf.org, sratliff@cisco.com
Subject: Re: [Gen-art] [manet]  review: draft-ietf-manet-nhdp-mib-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, 27 Apr 2012 16:56:51 -0000

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

 Dear Joel,

thank you very much for your review and apologies for our late reply. Find
our answers below, and
please tell us if they address your comments.

 ---------- Forwarded message ----------
From: Joel M. Halpern <jmh@joelhalpern.com>
Date: Fri, Apr 6, 2012 at 8:59 AM
Subject: [manet] [Gen-art] review: draft-ietf-manet-nhdp-mib-12
To: gen-art@ietf.org
Cc: manet@ietf.org, "A. Jean Mahoney" <mahoney@nostrum.com>,
sratliff@cisco.com


> 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-manet-nhdp-mib-12
>    Definition of Managed Objects for the
>        Neighborhood Discovery Protocol
> Reviewer: Joel M. Halpern
> Review Date: 6-April-2012
> IETF LC End Date: 16-April-2012
> IESG Telechat date: (if known)
>
> Summary: This document is almost ready for publication as a Proposed
> Standard.


<nhdp-mib-authors>
That's good :-)
</nhdp-mib-authors>




> Major issues:
>    Section 5.1.3.1 on Ignoring Initial Activity is trying to do a very
> reasonable thing, namely suppress notifications for activity which is
> expected.  The text references RFC 4750 as precedent.  RFC 4750 is
> clear that the suppress window is tied to specific events (interface
> up and election as a DR.)  Section 5.1.3.1 does not specify which
> condition(s) start(s) the suppress window.  If, as seems likely, it is
> Interface Up which starts the window, please state that explicitly in
> the text.


<nhdp-mib-authors>
How about adding the following sentence at the end of
the paragraph of 5.1.3.1:
"The suppression window for notifications is started when the 'nhdpIfStatus'
transitions
 from its default value of 'false' to 'true'."
</nhdp-mib-authors>



>    In section 5.4, in addition to describing objects which are defined
> in the MIB, the text describes, under the heading "The following
> objects return statistics related to HELLO messages:", a number of
> what it refers to as "Derived Objects".  These do not appear to be
> actual elements of the MIB.  They appear rather to be descriptions of
> calculations which the manager can perform using the information from
> the MIB.  It is not at all clear why they are here.  If I am
> understanding their role properly, and if they belong in this
> document, they belong in some other section, as they are NOT objects
> which return statistics related to HELLO messages.  They appear not to
> be returned by the managed device at all.



<nhdp-mib-authors>
Yes, you are right. We we pull these from the draft and
save the text and possibly use elsewhere in the future.
</nhdp-mib-authors>



> Minor issues:
>    I can not find the object that corresponds to the setting for
> Ignoring the Initial Activity.  I presume this is my error.  The
> document would be helped if the object were named in section 5.1.3.1.
>


<nhdp-mib-authors>
We can change 'HELLO_INTERVAL' in Section 5.1.3.1 to 'nhdpHelloInterval'.
</nhdp-mib-authors>



>    I believe section 5.1.3.2 on Throttling Traps is intended to refer
> to the StateChange Threshold and StateChangeWindow objects.  It would
> be very helpful if these were actually named in section 5.1.3.2.


<nhdp-mib-authors>
How about adding the following sentence to 5.1.3.2:
The following objects are used to define the thresholds and time
windows for specific Notifications defined in the NHDP-MIB module:
nhdpNbrStateChangeThreshold,
nhdpNbrStateChangeWindow, nhdp2HopNbrStateChangeThreshold,
nhdp2HopNbrStateChangeWindow,         nhdpIfRxBadPacketThreshold,
nhdpIfRxBadPacketWindow.
</nhdp-mib-authors>


>    Most MIBs I review have a description of the tables they contain,
> how the tables relate to each other, and how they are indexed, in the
> front matter that is roughly equivalent to section 5.2, 5.3, and 5.4.
> As I am not a MIB Doctor, I do not know if that is formally required,
> but I find it very helpful, and am surprised not to see it here.


<nhdp-mib-authors>
We agree that this is probably a good practice to follow and will work up
text to handle this.
</nhdp-mib-authors>


>    In looking at the fields in the NhdpInterfaceEntry, some of the
> field definitions include some of the constraints from RFC 6130
> section 5 in their DESCRIPTION clauses.  Some do not.  (For exampple,
> REFRESH_INTERVAL >= HELLO_INTERVAL is captured in
> nhdbpRefreshInterval, but not in nhdpHelloInterval.  The requirement
> that nhdpHelloInterval be greater than 0 is not captured anywhere.
>  Neither is H_HOLD_TIME >= REFRESH_INTERVAL captured.)  Some elements
> have a statement that the object is persistent, while others do not,
> but these do not seem to correspond to a difference in RFC 6130.  It
> is possible that there is a good reason for this apparent variation.
>  Is there?


<nhdp-mib-authors>
That's true. We will go through all constraints from NHDP and
add them to the MIB.
</nhdp-mib-authors>



>    Particularly for top-level objects such as nhdpNHoldTime and
> NhdpIHoldTime I would really like to see a better description than
> just this is <named> object from section 5 of RFC 6130.  Someone who
> is using the MIB, who is looking at the description clause for
> assistance, really needs something more than the name of the field in
> the MIB.  (I think better descriptions would be a good idea through
> much of the MIB.)



<nhdp-mib-authors>
We will can look at the descriptions and copy some more text from
NHDP. However, we would like to avoid copying all NHDP into the MIB.
</nhdp-mib-authors>


> Nits/editorial comments:
>    The tracker claims this is "In WG Last Call (manet), but also seems
> to indicate that it is in IETF Last Call.  Are the two happening at
> the same time?


<nhdp-mib-authors>
We actually don't know, and will ask the chairs about that.
</nhdp-mib-authors>


Best regards
Ulrich and Bob

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

<div class=3D"gmail_extra">
Dear Joel,<br>
<br>
thank you very much for your review and apologies for our late reply. Find =
our answers below, and<br>
please tell us if they address your comments.<br>
<br>=A0---------- Forwarded message ----------<br>
From: Joel M. Halpern &lt;<a href=3D"mailto:jmh@joelhalpern.com">jmh@joelha=
lpern.com</a>&gt;<br>
Date: Fri, Apr 6, 2012 at 8:59 AM<br>
Subject: [manet] [Gen-art] review: draft-ietf-manet-nhdp-mib-12<br>
To: <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br>
Cc: <a href=3D"mailto:manet@ietf.org">manet@ietf.org</a>, &quot;A. Jean Mah=
oney&quot; &lt;<a href=3D"mailto:mahoney@nostrum.com">mahoney@nostrum.com</=
a>&gt;,<br>
<a href=3D"mailto:sratliff@cisco.com">sratliff@cisco.com</a><br>
<br>
<br>
&gt; I am the assigned Gen-ART reviewer for this draft. For background on<b=
r>
&gt; 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; Please resolve these comments along with any other Last Call comments<=
br>
&gt; you may receive.<br>
&gt;<br>
&gt; Document: draft-ietf-manet-nhdp-mib-12<br>
&gt; =A0 =A0Definition of Managed Objects for the<br>
&gt; =A0 =A0 =A0 =A0Neighborhood Discovery Protocol<br>
&gt; Reviewer: Joel M. Halpern<br>
&gt; Review Date: 6-April-2012<br>
&gt; IETF LC End Date: 16-April-2012<br>
&gt; IESG Telechat date: (if known)<br>
&gt;<br>
&gt; Summary: This document is almost ready for publication as a Proposed<b=
r>
&gt; Standard.<br>
<br><br>
&lt;nhdp-mib-authors&gt;<br>
That&#39;s good :-)<br>
&lt;/nhdp-mib-authors&gt;<br>
<br><br><br><br>
&gt; Major issues:<br>
&gt; =A0 =A0Section 5.1.3.1 on Ignoring Initial Activity is trying to do a =
very<br>
&gt; reasonable thing, namely suppress notifications for activity which is<=
br>
&gt; expected. =A0The text references RFC 4750 as precedent. =A0RFC 4750 is=
<br>
&gt; clear that the suppress window is tied to specific events (interface<b=
r>
&gt; up and election as a DR.) =A0Section 5.1.3.1 does not specify which<br=
>
&gt; condition(s) start(s) the suppress window. =A0If, as seems likely, it =
is<br>
&gt; Interface Up which starts the window, please state that explicitly in<=
br>
&gt; the text.<br>
<br><br>
&lt;nhdp-mib-authors&gt;<br>
How about adding the following sentence at the end of<br>
the paragraph of <a href=3D"http://5.1.3.1">5.1.3.1</a>:<br>
&quot;The suppression window for notifications is started when the &#39;nhd=
pIfStatus&#39;<br>
transitions<br>=A0from its default value of &#39;false&#39; to &#39;true&#3=
9;.&quot;<br>
&lt;/nhdp-mib-authors&gt;<br>
<br><br><br>
&gt; =A0 =A0In section 5.4, in addition to describing objects which are def=
ined<br>
&gt; in the MIB, the text describes, under the heading &quot;The following<=
br>
&gt; objects return statistics related to HELLO messages:&quot;, a number o=
f<br>
&gt; what it refers to as &quot;Derived Objects&quot;. =A0These do not appe=
ar to be<br>
&gt; actual elements of the MIB. =A0They appear rather to be descriptions o=
f<br>
&gt; calculations which the manager can perform using the information from<=
br>
&gt; the MIB. =A0It is not at all clear why they are here. =A0If I am<br>
&gt; understanding their role properly, and if they belong in this<br>
&gt; document, they belong in some other section, as they are NOT objects<b=
r>
&gt; which return statistics related to HELLO messages. =A0They appear not =
to<br>
&gt; be returned by the managed device at all.<br>
<br><br><br>
&lt;nhdp-mib-authors&gt;<br>Yes, you are right. We we pull these from the d=
raft and<br>
save the text and possibly use elsewhere in the future.<br>
&lt;/nhdp-mib-authors&gt;<br>
<br><br><br>
&gt; Minor issues:<br>
&gt; =A0 =A0I can not find the object that corresponds to the setting for<b=
r>
&gt; Ignoring the Initial Activity. =A0I presume this is my error. =A0The<b=
r>
&gt; document would be helped if the object were named in section 5.1.3.1.<=
br>
&gt;<br>
<br><br>&lt;nhdp-mib-authors&gt;<br>
We can change &#39;HELLO_INTERVAL&#39; in Section 5.1.3.1 to &#39;nhdpHello=
Interval&#39;.<br>
&lt;/nhdp-mib-authors&gt;<br>
<br><br><br>
&gt; =A0 =A0I believe section 5.1.3.2 on Throttling Traps is intended to re=
fer<br>
&gt; to the StateChange Threshold and StateChangeWindow objects. =A0It woul=
d<br>
&gt; be very helpful if these were actually named in section 5.1.3.2.<br>
<br><br>
&lt;nhdp-mib-authors&gt;<br>
How about adding the following sentence to <a href=3D"http://5.1.3.2">5.1.3=
.2</a>:<br>
The following objects are used to define the thresholds and time<br>
windows for specific Notifications defined in the NHDP-MIB module:<br>
nhdpNbrStateChangeThreshold,<br>
nhdpNbrStateChangeWindow, nhdp2HopNbrStateChangeThreshold,<br><div id=3D":2=
ac">
nhdp2HopNbrStateChangeWindow, =A0 =A0 =A0 =A0 nhdpIfRxBadPacketThreshold,<b=
r>
nhdpIfRxBadPacketWindow.<br>
&lt;/nhdp-mib-authors&gt;<br>
<br>
<br>
&gt; =A0 =A0Most MIBs I review have a description of the tables they contai=
n,<br>
&gt; how the tables relate to each other, and how they are indexed, in the<=
br>
&gt; front matter that is roughly equivalent to section 5.2, 5.3, and 5.4.<=
br>
&gt; As I am not a MIB Doctor, I do not know if that is formally required,<=
br>
&gt; but I find it very helpful, and am surprised not to see it here.<br>
<br>
<br>&lt;nhdp-mib-authors&gt;<br>
We agree that this is probably a good practice to follow and will work up t=
ext to handle this.<br>
&lt;/nhdp-mib-authors&gt;<br>
<br><br>
&gt; =A0 =A0In looking at the fields in the NhdpInterfaceEntry, some of the=
<br>
&gt; field definitions include some of the constraints from RFC 6130<br>
&gt; section 5 in their DESCRIPTION clauses. =A0Some do not. =A0(For exampp=
le,<br>
&gt; REFRESH_INTERVAL &gt;=3D HELLO_INTERVAL is captured in<br>
&gt; nhdbpRefreshInterval, but not in nhdpHelloInterval. =A0The requirement=
<br>
&gt; that nhdpHelloInterval be greater than 0 is not captured anywhere.<br>
&gt; =A0Neither is H_HOLD_TIME &gt;=3D REFRESH_INTERVAL captured.) =A0Some =
elements<br>
&gt; have a statement that the object is persistent, while others do not,<b=
r>
&gt; but these do not seem to correspond to a difference in RFC 6130. =A0It=
<br>
&gt; is possible that there is a good reason for this apparent variation.<b=
r>
&gt; =A0Is there?<br>
<br><br>&lt;nhdp-mib-authors&gt;<br>
That&#39;s true. We will go through all constraints from NHDP and<br>
add them to the MIB.<br>
&lt;/nhdp-mib-authors&gt;<br>
<br><br><br>
&gt; =A0 =A0Particularly for top-level objects such as nhdpNHoldTime and<br=
>
&gt; NhdpIHoldTime I would really like to see a better description than<br>
&gt; just this is &lt;named&gt; object from section 5 of RFC 6130. =A0Someo=
ne who<br>
&gt; is using the MIB, who is looking at the description clause for<br>
&gt; assistance, really needs something more than the name of the field in<=
br>
&gt; the MIB. =A0(I think better descriptions would be a good idea through<=
br>
&gt; much of the MIB.)<br>
<br><br><br>
&lt;nhdp-mib-authors&gt;<br>
We will can look at the descriptions and copy some more text from<br>
NHDP. However, we would like to avoid copying all NHDP into the MIB.<br>
&lt;/nhdp-mib-authors&gt;<br>
<br><br>
&gt; Nits/editorial comments:<br>
&gt; =A0 =A0The tracker claims this is &quot;In WG Last Call (manet), but a=
lso seems<br>
&gt; to indicate that it is in IETF Last Call. =A0Are the two happening at<=
br>
&gt; the same time?<br>
<br><br>&lt;nhdp-mib-authors&gt;<br>
We actually don&#39;t know, and will ask the chairs about that.<br>
&lt;/nhdp-mib-authors&gt;<br><br><br>Best regards<br>Ulrich and Bob<br></di=
v></div>

--047d7b2ee19999ce0404beabfd77--

From jmh@joelhalpern.com  Fri Apr 27 11:03:26 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 9314521F86F5; Fri, 27 Apr 2012 11:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.372
X-Spam-Level: 
X-Spam-Status: No, score=-102.372 tagged_above=-999 required=5 tests=[AWL=-0.108, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, NORMAL_HTTP_TO_IP=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 TjBFTpNEdj4B; Fri, 27 Apr 2012 11:03:25 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id E2BFA21F86E8; Fri, 27 Apr 2012 11:03:25 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id CEB795580DD; Fri, 27 Apr 2012 11:03:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 9CC521BCE071; Fri, 27 Apr 2012 11:03:25 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.100] (pool-71-161-51-182.clppva.btas.verizon.net [71.161.51.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 378DF1BCE06F; Fri, 27 Apr 2012 11:03:24 -0700 (PDT)
Message-ID: <4F9ADF8B.804@joelhalpern.com>
Date: Fri, 27 Apr 2012 14:03:55 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Ulrich Herberg <ulrich@herberg.name>
References: <4F7E279C.3030707@nostrum.com> <4F7F12CA.9010009@joelhalpern.com> <CAK=bVC9EfdXVPj3b+mhjzsDyiYjOEwQEH+jQ49KcFbO4PkV=YA@mail.gmail.com>
In-Reply-To: <CAK=bVC9EfdXVPj3b+mhjzsDyiYjOEwQEH+jQ49KcFbO4PkV=YA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, manet@ietf.org, sratliff@cisco.com
Subject: Re: [Gen-art] [manet]  review: draft-ietf-manet-nhdp-mib-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, 27 Apr 2012 18:03:26 -0000

Pending actual text availability, the approaches described seem to 
recognize the issues and plan to address them appropriately.
I look forward to seeing the result when it is ready,
Thank you,
Joel

On 4/27/2012 12:56 PM, Ulrich Herberg wrote:
> Dear Joel,
>
> thank you very much for your review and apologies for our late reply.
> Find our answers below, and
> please tell us if they address your comments.
>
>   ---------- Forwarded message ----------
> From: Joel M. Halpern <jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>
> Date: Fri, Apr 6, 2012 at 8:59 AM
> Subject: [manet] [Gen-art] review: draft-ietf-manet-nhdp-mib-12
> To: gen-art@ietf.org <mailto:gen-art@ietf.org>
> Cc: manet@ietf.org <mailto:manet@ietf.org>, "A. Jean Mahoney"
> <mahoney@nostrum.com <mailto:mahoney@nostrum.com>>,
> sratliff@cisco.com <mailto:sratliff@cisco.com>
>
>
>  > 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-manet-nhdp-mib-12
>  >    Definition of Managed Objects for the
>  >        Neighborhood Discovery Protocol
>  > Reviewer: Joel M. Halpern
>  > Review Date: 6-April-2012
>  > IETF LC End Date: 16-April-2012
>  > IESG Telechat date: (if known)
>  >
>  > Summary: This document is almost ready for publication as a Proposed
>  > Standard.
>
>
> <nhdp-mib-authors>
> That's good :-)
> </nhdp-mib-authors>
>
>
>
>
>  > Major issues:
>  >    Section 5.1.3.1 on Ignoring Initial Activity is trying to do a very
>  > reasonable thing, namely suppress notifications for activity which is
>  > expected.  The text references RFC 4750 as precedent.  RFC 4750 is
>  > clear that the suppress window is tied to specific events (interface
>  > up and election as a DR.)  Section 5.1.3.1 does not specify which
>  > condition(s) start(s) the suppress window.  If, as seems likely, it is
>  > Interface Up which starts the window, please state that explicitly in
>  > the text.
>
>
> <nhdp-mib-authors>
> How about adding the following sentence at the end of
> the paragraph of 5.1.3.1 <http://5.1.3.1>:
> "The suppression window for notifications is started when the 'nhdpIfStatus'
> transitions
>   from its default value of 'false' to 'true'."
> </nhdp-mib-authors>
>
>
>
>  >    In section 5.4, in addition to describing objects which are defined
>  > in the MIB, the text describes, under the heading "The following
>  > objects return statistics related to HELLO messages:", a number of
>  > what it refers to as "Derived Objects".  These do not appear to be
>  > actual elements of the MIB.  They appear rather to be descriptions of
>  > calculations which the manager can perform using the information from
>  > the MIB.  It is not at all clear why they are here.  If I am
>  > understanding their role properly, and if they belong in this
>  > document, they belong in some other section, as they are NOT objects
>  > which return statistics related to HELLO messages.  They appear not to
>  > be returned by the managed device at all.
>
>
>
> <nhdp-mib-authors>
> Yes, you are right. We we pull these from the draft and
> save the text and possibly use elsewhere in the future.
> </nhdp-mib-authors>
>
>
>
>  > Minor issues:
>  >    I can not find the object that corresponds to the setting for
>  > Ignoring the Initial Activity.  I presume this is my error.  The
>  > document would be helped if the object were named in section 5.1.3.1.
>  >
>
>
> <nhdp-mib-authors>
> We can change 'HELLO_INTERVAL' in Section 5.1.3.1 to 'nhdpHelloInterval'.
> </nhdp-mib-authors>
>
>
>
>  >    I believe section 5.1.3.2 on Throttling Traps is intended to refer
>  > to the StateChange Threshold and StateChangeWindow objects.  It would
>  > be very helpful if these were actually named in section 5.1.3.2.
>
>
> <nhdp-mib-authors>
> How about adding the following sentence to 5.1.3.2 <http://5.1.3.2>:
> The following objects are used to define the thresholds and time
> windows for specific Notifications defined in the NHDP-MIB module:
> nhdpNbrStateChangeThreshold,
> nhdpNbrStateChangeWindow, nhdp2HopNbrStateChangeThreshold,
> nhdp2HopNbrStateChangeWindow,         nhdpIfRxBadPacketThreshold,
> nhdpIfRxBadPacketWindow.
> </nhdp-mib-authors>
>
>
>  >    Most MIBs I review have a description of the tables they contain,
>  > how the tables relate to each other, and how they are indexed, in the
>  > front matter that is roughly equivalent to section 5.2, 5.3, and 5.4.
>  > As I am not a MIB Doctor, I do not know if that is formally required,
>  > but I find it very helpful, and am surprised not to see it here.
>
>
> <nhdp-mib-authors>
> We agree that this is probably a good practice to follow and will work
> up text to handle this.
> </nhdp-mib-authors>
>
>
>  >    In looking at the fields in the NhdpInterfaceEntry, some of the
>  > field definitions include some of the constraints from RFC 6130
>  > section 5 in their DESCRIPTION clauses.  Some do not.  (For exampple,
>  > REFRESH_INTERVAL >= HELLO_INTERVAL is captured in
>  > nhdbpRefreshInterval, but not in nhdpHelloInterval.  The requirement
>  > that nhdpHelloInterval be greater than 0 is not captured anywhere.
>  >  Neither is H_HOLD_TIME >= REFRESH_INTERVAL captured.)  Some elements
>  > have a statement that the object is persistent, while others do not,
>  > but these do not seem to correspond to a difference in RFC 6130.  It
>  > is possible that there is a good reason for this apparent variation.
>  >  Is there?
>
>
> <nhdp-mib-authors>
> That's true. We will go through all constraints from NHDP and
> add them to the MIB.
> </nhdp-mib-authors>
>
>
>
>  >    Particularly for top-level objects such as nhdpNHoldTime and
>  > NhdpIHoldTime I would really like to see a better description than
>  > just this is <named> object from section 5 of RFC 6130.  Someone who
>  > is using the MIB, who is looking at the description clause for
>  > assistance, really needs something more than the name of the field in
>  > the MIB.  (I think better descriptions would be a good idea through
>  > much of the MIB.)
>
>
>
> <nhdp-mib-authors>
> We will can look at the descriptions and copy some more text from
> NHDP. However, we would like to avoid copying all NHDP into the MIB.
> </nhdp-mib-authors>
>
>
>  > Nits/editorial comments:
>  >    The tracker claims this is "In WG Last Call (manet), but also seems
>  > to indicate that it is in IETF Last Call.  Are the two happening at
>  > the same time?
>
>
> <nhdp-mib-authors>
> We actually don't know, and will ask the chairs about that.
> </nhdp-mib-authors>
>
>
> Best regards
> Ulrich and Bob

From vkg@bell-labs.com  Fri Apr 27 11:15:39 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 6E60E21F8653 for <gen-art@ietfa.amsl.com>; Fri, 27 Apr 2012 11:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.724
X-Spam-Level: 
X-Spam-Status: No, score=-109.724 tagged_above=-999 required=5 tests=[AWL=0.875, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6SbY5sb5Q0L2 for <gen-art@ietfa.amsl.com>; Fri, 27 Apr 2012 11:15:38 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 98FFB21F8649 for <gen-art@ietf.org>; Fri, 27 Apr 2012 11:15:38 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id q3RIFNv2009697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 27 Apr 2012 13:15:24 -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 q3RIFLkG020815 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 27 Apr 2012 13:15:22 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q3RIFKOs001875; Fri, 27 Apr 2012 13:15:20 -0500 (CDT)
Message-ID: <4F9AE36B.1090805@bell-labs.com>
Date: Fri, 27 Apr 2012 13:20:27 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: draft-ietf-appsawg-mime-default-charset@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.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: General Area Review Team <gen-art@ietf.org>, Barry Leiba <barryleiba@computer.org>, "msk@cloudmark.com" <msk@cloudmark.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-appsawg-mime-default-charset-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, 27 Apr 2012 18:15:39 -0000

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

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

Document: draft-ietf-appsawg-mime-default-charset-03
Reviewer: Vijay K. Gurbani
Review Date: Apr-27-2012
IETF LC End Date: May-07-2012
IESG Telechat date: May-10-2012

Summary: This draft is ready as a Proposed Standard.

Major issues: 0
Minor issues: 0
Nits/editorial comments: 1

Nit: For better readability, I would suggest the following change in S1:

   s/value used when it is not/value used when the parameter is not/

Other than that, it is ready to go.

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  Fri Apr 27 11:55:35 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 42AC821F8763 for <gen-art@ietfa.amsl.com>; Fri, 27 Apr 2012 11:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.775
X-Spam-Level: 
X-Spam-Status: No, score=-109.775 tagged_above=-999 required=5 tests=[AWL=0.824, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bq-8Z+IeYL4O for <gen-art@ietfa.amsl.com>; Fri, 27 Apr 2012 11:55:34 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 6A10521F874C for <gen-art@ietf.org>; Fri, 27 Apr 2012 11:55:34 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id q3RItU7j024073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 27 Apr 2012 13:55:32 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q3RItURC013072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 27 Apr 2012 13:55:30 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q3RItTvm001836; Fri, 27 Apr 2012 13:55:30 -0500 (CDT)
Message-ID: <4F9AECD4.1000800@bell-labs.com>
Date: Fri, 27 Apr 2012 14:00:36 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: draft-ietf-avtext-rams-scenarios@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.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, General Area Review Team <gen-art@ietf.org>, "Drage, Keith \(Keith\)" <keith.drage@ALCATEL-LUCENT.COM>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-avtext-rams-scenarios-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Apr 2012 18:55:35 -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-avtext-rams-scenarios-04
Reviewer: Vijay K. Gurbani
Review Date: Apr-27-2012
IETF LC End Date: Not known
IESG Telechat date: May-10-2012

Summary: This draft is ready as an Informational.

Major issues: 0
Minor issues: 0
Nits/editorial comments: 5

Nits/editorials:

- S1: For readability, I would suggest the following change:

   OLD:
   ... In scenarios where multiple RAMS sessions, each initiated
    with an individual RAMS Request message to a different feedback
    target, will be simultaneously run by an RTP receiver, they need to
    be coordinated.

    NEW:
    ... Close coordination is required for multiple RAMS sessions
    simultaneously started by an RTP server, where each session
    is initiated with an individual RAMS Request message to a different
    feedback target.

- S2, second line: the use of the word "somewhow" just seems
  wishy-washy here.  Instead, I think it is better to say "... that
  are in some manner associated with each other."

- S3.1: Instead of saying "We run ..." and "we want to ..." better
  to say that "An individual RAMS sesson is run for each of the RTP
  streams that requires rapid acquisition."

- S3.4, same problem: instead of saying "we have only one RTP
  stream..." better to say "there is only one RTP stream ..."

- S6: Probably better to say that there are no new security attacks
  made possible by the this draft, however, security considerations of
  RFC6285 still apply.  Or something to that effect.

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 stbryant@cisco.com  Mon Apr 30 10:26:03 2012
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34FCD21F86DB; Mon, 30 Apr 2012 10:26:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.483
X-Spam-Level: 
X-Spam-Status: No, score=-110.483 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EeNv-2wzwxea; Mon, 30 Apr 2012 10:26:02 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id E836021F8657; Mon, 30 Apr 2012 10:26:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=1840; q=dns/txt; s=iport; t=1335806762; x=1337016362; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=baKfUvMNr17/OaV1zcWr69S32z51WzU4pWoHI/KqzIg=; b=XihZk4h+C69BOITTQ4YIIwUJ6YXdSDFJyfqkTlZPrjUkzmKndyVcLE8s MtM9GE4jX+yDlzzM+Gaq50m8g5GZ1J21C3XqrAvy8U/gqn61/uqviek86 tv6NURZbMnDICxlDz4lIpMHbDuXI3EaxyClQHyk+keZX6QipCByYhgkAJ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAPXKnk+Q/khM/2dsb2JhbABEr0+DAIEHggkBAQEEEgECI0ABEAsUBAkWDwkDAgECAUUGDQEHAQEeh2sLmimDQhCcKpEiBJV+gRGNSIECZ4Jp
X-IronPort-AV: E=Sophos;i="4.75,505,1330905600"; d="scan'208";a="136639932"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 30 Apr 2012 17:25:42 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q3UHPgps021791; Mon, 30 Apr 2012 17:25:42 GMT
Received: from dhcp-128-107-166-59.cisco.com (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q3UHPddg007627; Mon, 30 Apr 2012 18:25:41 +0100 (BST)
Message-ID: <4F9ECB13.3040001@cisco.com>
Date: Mon, 30 Apr 2012 18:25:39 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
References: <ED4FC298-44C1-409D-9D0A-01CA75E14059@nostrum.com>
In-Reply-To: <ED4FC298-44C1-409D-9D0A-01CA75E14059@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-pwe3-static-pw-status.all@tools.ietf.org, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-pwe3-static-pw-status-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 17:26:03 -0000

On 26/04/2012 23:55, Ben Campbell 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:  (Proposed RFC 6478) (was draft-ietf-pwe3-static-pw-status-10)
> Reviewer: Ben Campbell
> Review Date:  2012-04-26
> IETF LC End Date:  2012-04-30
>
> **** Note: This draft has previously been approved as RFC 6478, but I understand we are last calling it again due to some material changes in AUTH48. Therefore this is a review of the diff between revision 10 and the text at http://www.rfc-editor.org/authors/rfc6478.txt ****
>
>
> Summary:
>
> The edited text is essentially ready for publication, but I have a couple of minor issues that might should be considered first.
>
> Major issues:
>
> None
>
> Minor issues:
>
> -- 5.3, last paragraph:
>
> The last sentence changed from a non-normative statement to "This SHOULD cause the PE sending the PW status notification message with a PW status code equal to zero to stop sending and to continue normal operation."
>
> Is that really intended as a normative statement, or a statement of fact? I suspect it's the latter, but if the former, then it should be stated more of the form "If the sending PE receives ... it SHOULD stop ..."
>
> -- IANA considerations:
>
> Maybe I missed it, but I don't see a registration policy for adding things to the new registry. This wasn't an AUTH48 change, but it should probably be there.
Hi Ben

Thank you for your review.

The IANA policy is stated as IETF Review (end of first para in IANA)

The normative text is deliberate - this was part of the change that we 
needed to make.

- Stewart






From ben@nostrum.com  Mon Apr 30 11:32:20 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 BD4AB21F88F4; Mon, 30 Apr 2012 11:32:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.467
X-Spam-Level: 
X-Spam-Status: No, score=-102.467 tagged_above=-999 required=5 tests=[AWL=0.133, 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 r7y2YUjxQnNV; Mon, 30 Apr 2012 11:32:19 -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 262F621F88F1; Mon, 30 Apr 2012 11:32:19 -0700 (PDT)
Received: from [10.0.1.33] (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 q3UIWHb9039603 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 30 Apr 2012 13:32:18 -0500 (CDT) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <4F9ECB13.3040001@cisco.com>
Date: Mon, 30 Apr 2012 13:32:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <74F09118-B4F8-4C4D-8B91-ACD487ED0598@nostrum.com>
References: <ED4FC298-44C1-409D-9D0A-01CA75E14059@nostrum.com> <4F9ECB13.3040001@cisco.com>
To: stbryant@cisco.com
X-Mailer: Apple Mail (2.1257)
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>, draft-ietf-pwe3-static-pw-status.all@tools.ietf.org, The IETF <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-pwe3-static-pw-status-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Apr 2012 18:32:20 -0000

On Apr 30, 2012, at 12:25 PM, Stewart Bryant wrote:

> Hi Ben
>=20
> Thank you for your review.
>=20
> The IANA policy is stated as IETF Review (end of first para in IANA)

Okay, I guess I just missed it.

>=20
> The normative text is deliberate - this was part of the change that we =
needed to make.
>=20

Then as a reviewer, I think the proposed text is a bit confusing, as a =
paragraph describing how one element operates seems to make a normative =
requirement on the behavior of a different element. It would be better =
to make that assertion in the description of behavior for that other =
element. This is not a big deal, and certainly not a show stopper if =
people are attached to the current approach. It's just a personal =
opinion.

(Sorry, I'd offer more specifics, but am not in a position to pull up =
the text at the moment, so I'm responding from memory. I will look again =
when I get the chance.)

Thanks!

Ben.=
