
From mahoney@nostrum.com  Fri Aug  2 01:23:41 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2016021E82D2 for <gen-art@ietfa.amsl.com>; Fri,  2 Aug 2013 01:23: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 7+a-DtUvieU7 for <gen-art@ietfa.amsl.com>; Fri,  2 Aug 2013 01:23:39 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id E907621E8271 for <gen-art@ietf.org>; Fri,  2 Aug 2013 01:23:28 -0700 (PDT)
Received: from dhcp-4107.meeting.ietf.org (dhcp-4107.meeting.ietf.org [130.129.65.7]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r728NLKr087284 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Fri, 2 Aug 2013 03:23:22 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <51FB6C78.2000204@nostrum.com>
Date: Fri, 02 Aug 2013 10:23:20 +0200
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 130.129.65.7 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-08-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 08:23:42 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Ben Campbell      2013-08-12   draft-ietf-websec-x-frame-options-07

Brian Carpenter   2013-08-21   draft-ietf-mpls-tp-mip-mep-map-08

Christer Holmberg 2013-08-16   draft-ietf-tls-oob-pubkey-09

Robert Sparks     2013-08-18   draft-ietf-karp-ops-model-07



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

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


The standard template is included below.

Thanks,

Jean

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From ron.even.tlv@gmail.com  Mon Aug  5 05:36:50 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1286C21F9473; Mon,  5 Aug 2013 05:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.704
X-Spam-Level: 
X-Spam-Status: No, score=-1.704 tagged_above=-999 required=5 tests=[AWL=-0.595, BAYES_05=-1.11, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AxaJc+DMqn-b; Mon,  5 Aug 2013 05:36:47 -0700 (PDT)
Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com [IPv6:2a00:1450:4013:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 910DA21F969F; Mon,  5 Aug 2013 05:36:46 -0700 (PDT)
Received: by mail-ea0-f177.google.com with SMTP id f15so1572260eak.36 for <multiple recipients>; Mon, 05 Aug 2013 05:36:40 -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=6qf9WOgrwLrQj+4FUsGAVIydcMN3g0cuk8FDDn75lXE=; b=wArx/2vF5vsxD6fqWTL51P2vAVKOnlf0C33TXpvprMnwo/HzHfUTxclAiOqngj8h4W /WcOd9dxhGGPAkGRI0wecspSdkYrA94TFZKoy2c3tNBvP6BWv8GBI7peF/SDFqE1adrx WfAuUvQDIg31/Tc2qZcF4SQJLmfs0K9gwZjuf0j6iZBxG3GCUo4S2L47wgVTIDt0DnZR /utdaBlUjEVFp3e6Z8cDh0QKA6b6q66+qJwzppC6NveaiGImY8ImFWiLTqr78yRNYd/Z gSIudXMZx1dgPGC1TZh7BAf5TJxWTyE/UGCf48NOSs6fHEFpeUXffVBpob/U7+pbZnNb sy9g==
X-Received: by 10.15.26.199 with SMTP id n47mr16975662eeu.88.1375706200822; Mon, 05 Aug 2013 05:36:40 -0700 (PDT)
Received: from RoniE (bzq-79-176-222-74.red.bezeqint.net. [79.176.222.74]) by mx.google.com with ESMTPSA id l42sm32998889eeo.14.2013.08.05.05.36.38 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 05 Aug 2013 05:36:39 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-allen-dispatch-imei-urn-as-instanceid.all@tools.ietf.org>
Date: Mon, 5 Aug 2013 15:34:34 +0300
Message-ID: <00a401ce91d8$26b96210$742c2630$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A5_01CE91F1.4C073650"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6R2AMm9KzL7XkgSVWmyWq12ZGCoA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART IETF LC review of draft-allen-dispatch-imei-urn-as-instanceid-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, 05 Aug 2013 12:36:50 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00A5_01CE91F1.4C073650
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-allen-dispatch-imei-urn-as-instanceid-10

Reviewer: Roni Even

Review Date:2013-8-5

IETF LC End Date: 2013-8-16

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

 

Why is it going to be an Informational RFC, considering that there is a lot
of normative language in the document.

 

 

 

Nits/editorial comments:

According to RFC editor guidelines
(http://www.rfc-editor.org/policy.html#policy.abstract) the abstract section
should not contain citations unless they are completely defined within the
Abstract.

 


------=_NextPart_000_00A5_01CE91F1.4C073650
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-allen-dispatch-imei-urn-as-instanceid-10</span><o:p></o:p></p=
><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;8&#8211;5<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-8&#8211;16<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 =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Why is it =
going to be an Informational RFC, considering that there is a lot of =
normative language in the document.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>According =
to RFC editor guidelines (</span><a =
href=3D"http://www.rfc-editor.org/policy.html#policy.abstract">http://www=
.rfc-editor.org/policy.html#policy.abstract</a>)<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> the <a =
name=3Dpolicy.abstract>abstract section <span =
style=3D'color:black'>should not contain citations unless they are =
completely defined within the Abstract.</span></a><span =
style=3D'color:black'><o:p></o:p></span></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00A5_01CE91F1.4C073650--


From zach@sensinode.com  Mon Aug  5 10:51:11 2013
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 A1CA421F8F3C; Mon,  5 Aug 2013 10:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hmZXlsUo5DcG; Mon,  5 Aug 2013 10:51:06 -0700 (PDT)
Received: from auth-smtp.nebula.fi (auth-smtp.nebula.fi [217.30.180.105]) by ietfa.amsl.com (Postfix) with ESMTP id 2473821F9CC5; Mon,  5 Aug 2013 10:50:55 -0700 (PDT)
Received: from [10.37.109.3] ([77.95.242.69]) (authenticated bits=0) by auth-smtp.nebula.fi (8.13.8/8.13.4) with ESMTP id r75HomTd026733 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 5 Aug 2013 20:50:49 +0300
X-Authenticated-User: sensinodecom
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com>
Date: Mon, 5 Aug 2013 20:50:49 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <607B7E5D-EEF3-4D53-A5C1-5484795B64C7@sensinode.com>
References: <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
X-Mailer: Apple Mail (2.1503)
Cc: "draft-bormann-cbor-04.all@tools.ietf.org" <draft-bormann-cbor-04.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 05 Aug 2013 17:51:11 -0000

On Aug 5, 2013, at 8:43 PM, "Joe Hildebrand (jhildebr)" =
<jhildebr@cisco.com> wrote:

>> 7.  The format must be extensible, with the extended data being able
>> to be parsed by earlier parsers.
>=20
>=20
> This is interesting, and I would be willing to give up several kinds =
of
> extensibility to get more simplicity.  Perhaps this is your greatest
> issue, and I don't think you are necessarily wrong.

As an IoT end-user of this kind of format, I would have no issues with =
giving up quite a bit of extensibility for more simplicity. If that is =
the major push-back, then I think we should look at reassessing the need =
for e.g. tags.=20

Zach

--=20
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com @SensinodeIoT
Mobile: +358 40 7796297
Twitter: @zach_shelby
LinkedIn: http://fi.linkedin.com/in/zachshelby
6LoWPAN Book: http://6lowpan.net





From jhildebr@cisco.com  Mon Aug  5 10:43:40 2013
Return-Path: <jhildebr@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 E431821F9F4F; Mon,  5 Aug 2013 10:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.66
X-Spam-Level: 
X-Spam-Status: No, score=-10.66 tagged_above=-999 required=5 tests=[AWL=-0.061, 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 Zt7QNd+k30q3; Mon,  5 Aug 2013 10:43:35 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id EBE4A21F9F21; Mon,  5 Aug 2013 10:43:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25628; q=dns/txt; s=iport; t=1375724611; x=1376934211; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=t0pNcc++f7DtoC2yZhB+4YA1X8NBjMYZguO3w53V21k=; b=QfQHTlpDj/mIoKVjVwruirZ1LupUc0zm1XZEEAvbX4AazdGdsNC4+mM6 jSzakb67Nr3JrrfqC1FQbNlzgI0FeqVIcKxl1aVayZut62Ps2ZKB1AIzp Oyz/Vaew/EJBFxNLgPmlsg7CP2TIFRbwL3lSMp0YRUf+d/TvIY/mGSw4m U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAA7j/1GtJXHB/2dsb2JhbABbgwY1UL51gSEWdIIkAQEBAwEODA0TKwIHCwUNAQgiFDERJQIEAQ0FCBaHYAMJBgysQA2IWgSNJ4EkBQsBBoEGMQeDGXQDlAmBbo4RhSeDF4FoAR8i
X-IronPort-AV: E=Sophos;i="4.89,819,1367971200"; d="scan'208";a="243695153"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-3.cisco.com with ESMTP; 05 Aug 2013 17:43:30 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r75HhUZw026822 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 5 Aug 2013 17:43:30 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.159]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Mon, 5 Aug 2013 12:43:29 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Martin Thomson <martin.thomson@gmail.com>, "draft-bormann-cbor-04.all@tools.ietf.org" <draft-bormann-cbor-04.all@tools.ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Thread-Topic: [apps-discuss] Gen-ART review of draft-bormann-cbor-04
Thread-Index: AQHOjPNCXWeGtSFAj0iRwScRzl7yuJmG2+2A
Date: Mon, 5 Aug 2013 17:43:29 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com>
In-Reply-To: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [10.21.116.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F6CCB6D461B913479C62B2AA09EEE810@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 05 Aug 2013 11:43:01 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 05 Aug 2013 17:43:41 -0000

Sorry, my response is also correspondingly long.  There are some original
comments at the end that are not just responses to Martin.

On 7/30/13 9:05 AM, "Martin Thomson" <martin.thomson@gmail.com> wrote:

>I'm glad that I held this review until Paul's appsarea presentation.
>This made it very clear to me that the types of concerns I have are
>considered basically irrelevant by the authors because they aren't
>interested in changing the design goals.  I don't find the specific
>design goals to be interesting and am of the opinion that the goals
>are significant as a matter of general application.  I hope that is
>clear from my review.

I don't think you made it clear which of the design goals you thought
weren't interesting.  I'll give my take on each of them here:

> 1.  The representation must be able to unambiguously encode most
> common data formats used in Internet standards.


Seems reasonable.  For example, dates *do* come up quite often (e.g. MIME
headers).

> 2.  The code for an encoder or parser must be able to be compact in
> order to support systems with very limited memory and processor
> power and instruction sets.


Seems reasonable, particularly if you're targeting embedded devices and
sensors.  One of the other corollaries they ought to mention here is that
devices that have small implementations should be able to receive a subset
of the value of the format, implementing only the parts that they need to
and skipping everything they don't understand.

> 3.  Data must be able to be parsed without a schema description.


I'd put this first.  It's an absolute must-have for future extensibility.


> 4.  The serialization must be reasonably compact, but data
> compactness is secondary to code compactness for the encoder and
> parser.


This is one of the things that people don't like about XML, which leads
them to come up with aggressively complicated approaches like EXI.  I
might argue that it's a little more important than code compactness for my
use cases, but I think CBOR currently strikes an adequate balance.

> 5.  The format must be applicable to both constrained nodes and high-
> volume applications.

In IoT applications, both will be true at the same time, so I like this
requirement.  Low CPU usually means less battery usage anyway.


> 6.  The format must support all JSON data types for conversion to and
> from JSON.


Why not?  There are some bits that don't convert quite cleanly enough to
JSON, but it's pretty close.

> 7.  The format must be extensible, with the extended data being able
> to be parsed by earlier parsers.


This is interesting, and I would be willing to give up several kinds of
extensibility to get more simplicity.  Perhaps this is your greatest
issue, and I don't think you are necessarily wrong.



>I have reviewed the mailing list feedback, and it's not clear to me
>that there is consensus to publish this.  It might be that the dissent
>that I have observed is not significant in Barry's learned judgment,
>or that this is merely dissent on design goals and therefore
>irrelevant.  The fact that this work isn't a product of a working
>group still concerns me.  I'm actually interested in why this is
>AD-sponsored rather than a working group product.

I think this draft is interesting, and might benefit from a short-lived
working group to ensure that enough people have reviewed it.  As well, I
think there might need to be a BCP70-style document that explores how to
design protocols using CBOR, after we've got some implementation
experience.

I do think that rather a lot of the dissent from the list was heard and
incorporated, including streaming, which I personally think is an
over-complication, but others really seemed to want.

>Major issues:
>My major concerns with this document might be viewed as disagreements
>with particular design choices.  And, I consider it likely that the
>authors will conclude that the document is still worth publishing as
>is, or perhaps with some minor changes.  In the end, I have no issue
>with that, but expect that the end result will be that the resulting
>RFC is ignored.

I don't agree that CBOR will be ignored if published in the current form,
but I do believe it could use a little more review and polish.

>What would cause this to be tragic, is if publication of this were
>used to prevent other work in this area from subsequently being
>published.  (For those drawing less-than-charitable inferences from
>this, I have no desire to throw my hat into this particular ring,
>except perhaps in jest [1].)

There will be other formats, even if this is published.


>This design is far too complex and large.  Regardless of how
>well-considered it might be, or how well this meets the stated design
>goals, I can't see anything but failure in this document's future.
>JSON succeeds largely because it doesn't attempt to address so many
>needs at once, but I could even make a case for why JSON contains too
>many features.

I've implemented it twice now, using two different approaches.  The second
time, I separated the lexing and generation using a SAX-style eventing
model.  There were a total of eight events fired:

- value=20
- array start/stop
- map start/stop
- stream start/stop
- end

That seems roughly minimal for data shaped similarly to JSON (except for
streams), and significantly less complex than the equivalent SAX2 set for
XML.

>In comparison with JSON, this document does one major thing wrong: it
>has more options than JSON in several dimensions.  There are more
>types, there are several more dimensions for extensibility than JSON:
>types extensions, values extensions (values of 28-30 in the lower bits
>of the type byte), plus the ability to apply arbitrary tags to any
>value.  I believe all of these to be major problems that will cause
>them to be ignored, poorly implemented, and therefore useless.

I agree that not everyone will implement all of the semantic tags, but the
fact that you can continue parsing even if you receive a tag you don't
implement is an interesting and useful property.

I do agree that the extensibility of the patterns 28-30 is scary; those
came about when streaming was added.

>In part, this complexity produces implementations that are far more
>complex than they might need to be, unless additional standardization
>is undertaken.  That idea is something I'm uncomfortable with.

I didn't find either of those properties to be challenging to code around.
 I error on bit patterns for 28-30, capture but ignore tags in the
eventing layer, and in the generation layer am able to implement new tags
with code that looks like:

tag_DATE_STRING: (val)->
  new Date(val)

Which doesn't seem like an onerous burden for the upside of being able to
round-trip all of the built-in JavaScript types.


I guess I disagree with your characterization of overcomplexity, based on
implementation experience.

>Design issue: extensibility:
>This document avoids discussion of issues regarding schema-less
>document formats that I believe to be fundamental.  These issues are
>critical when considering the creation of a new interchange format.
>By choosing this specific design it makes a number of trade-offs that
>in my opinion are ill-chosen.  This may be in part because the
>document is unclear about how applications intend to use the documents
>it describes.
>
>You may conclude after reading this review that this is simply because
>the document does not explain the rationale for selecting the approach
>it takes.  I hope that isn't the conclusion you reach, but appreciate
>the reasons why you might do so.
>
>I believe the fundamental problem to be one that arises from a
>misunderstanding about what it means to have no schema.  Aside from
>formats that require detailed contextual knowledge to interpret, there
>are several steps toward the impossible, platonic ideal of a perfectly
>self-describing format.  It's impossible because ultimately the entity
>that consumes the data is required at some level to understand the
>semantics that are being conveyed.  In practice, no generic format can
>effectively self-describe to the level of semantics.
>
>This draft describes a format that is more capable at self-description
>than JSON.  I believe that to not just be unnecessary, but
>counterproductive.  At best, it might provide implementations with a
>way to avoid an occasional extra line of code for type conversion.

As an example, the binary string type would be quite useful for JOSE-style
documents that need to reproduce a set of octets exactly.  Today, Base64
is required for that in JSON, which is causing the JOSE working group to
limit the size (and therefore the ease of understanding) of value names,
as multiple layers of Base64 can expand their output size past the
external limits placed on applications by browsers.

Secondly, numeric types in JSON are pretty woefully underspecified, and
cannot be fixed. Transmitting both integers and floats with precise
understanding of how they will be received is often quite useful.

I don't see either of these as simple type conversion issues.

>Extensibility as it relates to types:
>The use of extensive typing in CBOR implies an assumption of a major
>role for generic processing.  XML schema and XQuery demonstrate that
>this desire is not new, but they also demonstrate the folly of
>pursuing those goals.

XML schema keeps these bits in a (quite complex) separate stream, which
requires significant extra processing to add type information into the
parse stream.  I agree that we've learned that this approach doesn't work
well.  I don't think that either XSD or XQuery prove anything about
putting some type information into the data stream itself.


>JSON relies on a single mechanism for extensibility. JSON maps that
>contain unknown or unsupported keys are (usually) ignored.  This
>allows new values to be added to documents without destroying the
>ability of an old processor to extract the values that it supports.
>The limited type information JSON carries leaks out, but it's unclear
>what value this has to a generic processor.  All of the generic uses
>I've seen merely carry that type information, no specific use is made
>of the knowledge it provides.

I don't see how this is relevant.  Most CBOR extensibility for a given
protocol will follow this model exactly.

>ASN.1 extensibility, as encoded in PER, leads to no type information
>leaking.  Unsupported extensions are skipped based on a length field.

I'd say that CBOR has a slight advantage here, because you can still get
some interesting information out of many tag types, even if you don't
support that tag type.  That allows a non-extensible parsing system to be
used, if desired.

>(As an aside, PER is omitted from the analysis in the appendix, which
>I note from the mailing lists is due to its dependency on schema.
>Interestingly, I believe it to be possible - though not trivial - to
>create an ASN.1 description with all the properties described in CBOR
>that would have roughly equivalent, if not fully equivalent,
>properties to CBOR when serialized.)

Let's add PER to the analysis.  I don't think it will have the properties
desired, since the decoder has to have access to the same schema the
sender had.  I agree that it might be possible to create CBOR Encoding
Rules or the moral equivalent, but I'm not sure I agree that it would be
worth the effort.

>By defining an extensibility scheme for types, CBOR effectively
>acknowledges that a generic processor doesn't need type information
>(just delineation information), but it then creates an extensive type
>system.  That seems wasteful.

In a given system using CBOR, the protocol designers will decide which
types to use.  All of the tooling in that ecosystem will parse and encode
the selected types.

Think of the extensibility here being more for generating lots of
different protocols on top of CBOR, not lots of different types in one
protocol.

>Design issue: types:
>The addition of the ability to carry uninterpreted binary data is a
>valuable and important feature.  If that was all this document did,
>then that might have been enough.  But instead it adds numerous
>different types.

I agree that binary is the most important.  However, unambiguous,
unescaped, UTF8-only text is also a big win over JSON.  Precise floats are
a distant third for me, but seem to be the most important for folks that
do remote sensors.

>I can understand why multiple integer encoding sizes are desirable,
>and maybe even floating point representations, but this describes
>bignums in both base 2 and 10,

I agree that the bignums are overkill.  I implemented them the second
time, but I made sure they were slow. :)

Seriously, I don't see using these in any applications, unless the
security folks decide they are a good fit for an RSA modulus.

>embedded CBOR documents in three forms,
>URIs, base64 encoded strings, regexes, MIME bodies, date and times in
>two different forms, and potentially more.

I think I may be responsible for having suggested URIs and regexes, and
would fully support removing them from the base draft, along with all of
the baseX and the (underspecified) MIME stuff.

Please keep the dates.

>I also challenge the assertion made where the code required for
>parsing a data type produces larger code sizes if performed outside of
>a common shared library.  That's arguably provably true, but last time
>I checked a few extra procedure calls (or equivalent) weren't the
>issue for code size.  Sheer number of options on the other hand might
>be.

That assertion is also unconvincing to me.  However, I'd really like my
docs to round-trip, and dates are a big hole in that.  I personally want
precisely one date type (rather than two), and don't care which one is
selected.  Javascript floating point milliseconds before/after the epoch
seems like a reasonable starting point, for example.

>Half-precision floating point numbers are a good example of excessive
>exuberance.  They are not available in many languages for good reason:
>they aren't good for much.

They're also relatively new.

>They actually tend to cause errors in
>software in the same way that threading libraries do: it's not that
>it's hard to use them, it's that it's harder than people think.  And
>requiring that implementations parse these creates unnecessary
>complexity. =20

I know that it took me an hour or two with the IEEE754 docs to implement
them in JavaScript, and that code passes a ton of unit tests, including
subnormals, +/- infinity, and NaNs.  That said, I don't need halfs for my
use cases, but if sensor folks feel strongly about them, I'm willing to
keep that code in place.

It's *really* nice to be able to encode NaN and +/- Infinity as separate
from null, which JSON does not allow.

>I do not believe that for the very small subset of cases
>where half precision is actually useful, the cost of transmitting the
>extra 2 bytes of a single-precision number is not going to be a
>burden.  However, the cost of carrying the code required to decode
>them is not as trivial as this makes out.  The fact that this requires
>an appendix would seem to indicate that this is special enough that
>inclusion should have been very carefully considered.  To be honest,
>if it were my choice, I would have excluded single-precision floating
>point numbers as well, they too create more trouble than they are
>worth.

I'd be fine with that for my use cases, too, but realize there are other
use cases where people care about both half- and single-precision, and am
willing to write a couple of extra lines of code to get them onboard.

>Design issue: optionality
>CBOR embraces the idea that support for types is optional.  Given the
>extensive nature of the type system, it's almost certain that
>implementations will choose to avoid implementation of some subset of
>the types.  The document makes no statements about what types are
>mandatory for implementations, so I'm not sure how it is possible to
>provide interoperable implementations.

I think it should say that *none* of the types is mandatory, which I think
is implied by the text in section 2.4.

>If published in its current form, I predict that only a small subset
>of types will be implemented and become interoperable.

I'd say let's agree on what those types are, and move all of the others to
separate drafts.  My list:

- Date (one type)
- CBOR (sometimes parsed, other times kept intact for processing as a byte
stream)

>Design issue: tagging
>The tagging feature has a wonderful property: the ability to create
>emergency complexity.  Given that a tag itself can be arbitrarily
>complex, I'm almost certain that this is a feature you do not want.

I'm not sure I understand fully what your issue is.  Protocol designers
can abuse any format, and when they do, implementors curse them down the
ages.  Don't do that.

>Minor issues:
>Design issue: negative numbers
>Obviously, the authors will be well-prepared for arguments that
>describe as silly the separation of integer types into distinct
>positive and negative types.  But it's true, this is a strange choice,
>and a very strange design.

I think it came from some of the other things in this space (e.g.
zigzag-encoding).  I think another option would be to have both signed and
unsigned types.  This choice didn't bother me too much in implementation,
except when it was repeated in bigints.

>The fact that this format is capable of describing 64-bit negative
>numbers creates a problem for implementations that I'm surprised
>hasn't been raised already.  In most languages I use, there is no
>native type that is capable of carrying the most negative value that
>can be expressed in this format.  -2^64 is twice as large as a 64-bit
>twos-complement integer can store.

Yes, that should be mentioned in the doc, probably with a MUST NOT.

>It almost looks as though CBOR is defining a 65-bit, 33-bit or 17-bit
>twos complement integer format, with the most significant bit isolated
>from the others, except that the negative expression doesn't even have
>the good sense to be properly sortable.  Given that and the fact that
>bignums are also defined, I find this choice to be baffling.

This is a quite valid concern.  Let's get it fixed.

>Document issue: Canonicalization
>Please remove Section 3.6.  c14n is hard, and this format actually
>makes it impossible to standardize a c14n scheme, that says a lot
>about it.  In comparison, JSON is almost trivial to canonicalize.

Agree with removing section 3.6, and moving to another doc if really
desired.

STRONGLY disagree that JSON is trivial to canonicalize.  The Unicode
issues notwithstanding (escaping, etc), the numeric format is a mess to
get into canonical form.

>If the intent of this section is to describe some of the possible
>gotchas, such as those described in the last paragraph, then that
>would be good.  Changing the focus to "Canonicalization
>Considerations" might help.
>
>I believe that there are several issues that this section would still
>need to consider.  For instance, the use of the types that contain
>additional JSON encoding hints carry additional semantics that might
>not be significant to the application protocol.
>
>Extension based on minor values 28-30 (the "additional information"
>space):
>...is impossible as defined.  Section 5.1 seems to imply otherwise.
>I'm not sure how that would ever happen without breaking existing
>parsers.  Section 5.2 actually makes this worse by making a
>wishy-washy commitment to size for 28 and 29, but no commitment at all
>for 30.

+1.  I'd prefer we remove streaming and tighten the additional information
bits back up to all being used as in previous versions of the draft.

>Nits:
>Section 3.7 uses the terms "well-formed" and "valid" in a sense that I
>believe to be consistent with their use in XML and XML Schema.  I
>found the definition of "valid" to be a little difficult to parse;
>specifically, it's not clear whether invalid is the logical inverse of
>valid.

Agree that language needs to be massaged.

>Appendix B/Table 4 has a TBD on it.  Can this be checked?

Sure.

>Table 4 keeps getting forward references, but it's hidden in an
>appendix.  I found that frustrating as a reader because the forward
>references imply that there is something important there.  And that
>implication was completely right, this needs promotion.  I know why
>it's hidden, but that reason just supports my earlier theses.

I think it should not be referred to earlier.  It's an implementation
choice, and not one that I (for example) made.  Thinking about that table
made it more difficult for me to get started.

>Section 5.1 says "An IANA registry is appropriate here.".  Why not
>reference Section 7.1?

Yes, that needs to be fixed.

>[1] https://github.com/martinthomson/aweson

Add binary, and remove the string quoting requirements, please. :)



Other things that ought to be discussed:

I would like to see another design goal: "May be implemented in modern web
browsers".  That should be possible with the new binary types.


I still don't see the need for non-string map keys.  JSON mapping would be
easier without them, as would uniqueness checking.  If they are to be
retained, they should have some motivation in the spec, describing how and
why they might be used.

I wish I could think of another good simple value that we might register
one day.  The only one I've come up with is "no-op", which I might use in
a streaming application as a trivial keep-alive or a marker between
records to ensure parser state sync.  I wouldn't classify that as "good"
however.

Nested tags ought to be forbidden until we come up with a strong use case
for them.

I could use some implementation guidance on how to generate the most
compact floating-point type for a given number, assuming we keep all of
the floating-point types.

I don't like 2.4.4.2 "Expected Later Encoding for CBOR to JSON
Converters".  Having a sender care about the encoding of a second format
at the same time seems unnecessarily complex.  I'd like to see this
section and the corresponding tags moved to another spec, or just removed.

Similar for tags 33 and 34.  Just send the raw bytes as a byte string;
there's no need to actually base64 encode.


Section 3.2.3, we should call out the heresy of including UTF-16
surrogates encoded as UTF-8 for those that can't read the UTF-8 spec.

Overall in section 3.2, "should probably issue an error but might take
some other action" seems like it will cause some interop surprises in
practice.

Section 3.3, "all number representations are equivalent" is unclear, even
with the clarifying phrase afterward.

If section 3.6 stays, the numerics need more work.  +/- Infinity should be
treated like NaN.  "if the result is the same value" would benefit from
some more clarity.  The tags section is also somewhat unclear.

Section 4.2, what about numbers with uninteresting fractional parts, like
1.0?  What about numbers in exponential format without fractional parts,
like 1e10?  I would recommend against even suggest encoding in place.
It's likely to cause a security issue for the reason mentioned.

Section 6, including the diagnostic notation is a little strange.  I would
at least like "it is not meant to be parsed" to be strengthened to "MUST
NOT be parsed".

Section 7.1, simple values 0..15 can never be used with this construction.
 If that's intentional, then give a good reason.

Section 7.2, do we have language we can use about how to reclaim
first-come-first-serve tags that aren't being used anymore?  e.g. the web
page is down and the requestor may be dead.

In section 7.3, yes, we should make "application/mmmmm+cbor" valid.

In section 8, perhaps mention a stack attack like:

0x818181818181818181...

I implemented depth counting with a maximum as an approach to avoid this.

There are likely to be lots of other security concerns.

I have checked all of the examples in Appendix A.  I would have expected

2(h'010000000000000000') | 0xc249010000000000000000

Not 18446744073709551616, since in the diagnostic, I don't necessarily
support bignums.

Same with 0xc349010000000000000000.

For numbers, section 9.8.1 of ECMA-262 (JSON.stringify) is relevant.  So:

5.960464477539063e-8 | 0xf90001   (not e-08)
0.00006103515625 | 0xf90400       (not e-05)



In Appendix B, there are holes in the jump table.  If you're going to have
a table, call out the invalid values, such as 0x1c-0x1f.

In Appendix C, the use of the variable "breakable" is unclear, and it's
not obvious how you'll get to the "no enclosing indefinite" case.

In Appendix D, shouldn't the input be unsigned or an array of bytes?

Appendix E.1, aren't there some cases of DER where you need the schema to
parse?  Add PER.

Appendix E, we should mention Smile, since the first two octets are so
cute.

Overall, I think this doc shows a lot of promise, and I'm looking forward
to having something on standards track that has these properties.

--=20
Joe Hildebrand


From tbray@textuality.com  Mon Aug  5 10:51:36 2013
Return-Path: <tbray@textuality.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F31A21F9AEF for <gen-art@ietfa.amsl.com>; Mon,  5 Aug 2013 10:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.783
X-Spam-Level: 
X-Spam-Status: No, score=-2.783 tagged_above=-999 required=5 tests=[AWL=0.193,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MhpMVLYgMX9u for <gen-art@ietfa.amsl.com>; Mon,  5 Aug 2013 10:51:22 -0700 (PDT)
Received: from mail-ve0-f181.google.com (mail-ve0-f181.google.com [209.85.128.181]) by ietfa.amsl.com (Postfix) with ESMTP id ACE6D21F9D18 for <gen-art@ietf.org>; Mon,  5 Aug 2013 10:51:15 -0700 (PDT)
Received: by mail-ve0-f181.google.com with SMTP id jz10so3431395veb.12 for <gen-art@ietf.org>; Mon, 05 Aug 2013 10:51:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=7RVUOPOBougtHZVVSi1ntw7Zb9mIW72rHzJvdigzBY4=; b=EZMaCRx/tHIi7leIEbOVnhIj6D/+/92VyVAK8ctHUxa71ATrFKzZAzvn7GyBEehC1j 8zawl8rA42JJhHT+XxfqbUUe3HmhGja1ao51Er7/7UrZliOBUzY19lrSSs/mh/UYZIcC AfKiGypTCmQocZSgmyYUzicz2a6gS3A3L7Bmbe9iFwNskRmNz1ZviUspMLd9leN+ViA7 Xjhvlw0npmXa5w9AdVTZvhlC2Y8PQ1e/FTMGtLVcp20OiteGc+q3CgJ4wjJ5C9oHI6QZ jwYYlu3JciYSnTIR1mTHlK2kBkuSG20/0IPZ2X7tSFlquvrBJ0z7uVZolKLh5f58jqLE 7Qig==
MIME-Version: 1.0
X-Received: by 10.58.85.161 with SMTP id i1mr6015300vez.97.1375725074035; Mon, 05 Aug 2013 10:51:14 -0700 (PDT)
Received: by 10.220.212.202 with HTTP; Mon, 5 Aug 2013 10:51:13 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com> <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com>
Date: Mon, 5 Aug 2013 10:51:13 -0700
Message-ID: <CAHBU6iu37cvh0VTDXnsuXe_cORXLgCL871Dtd0fMDMk7vdRu3g@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b6da6ac58c4a504e336f480
X-Gm-Message-State: ALoCoQn51PR5jdvTWri5rr7oWA8s4Qtx74Vz+m4wyChLpjIje0XGwV68tU8Zx8vuioukoQmktyN3
X-Mailman-Approved-At: Mon, 05 Aug 2013 11:43:01 -0700
Cc: "draft-bormann-cbor-04.all@tools.ietf.org" <draft-bormann-cbor-04.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 05 Aug 2013 17:51:36 -0000

--047d7b6da6ac58c4a504e336f480
Content-Type: text/plain; charset=UTF-8

I like the design of CBOR but my big question is how much code-size and
memory-size and performance it actually buys you.  My experience is that
the performance of software that parses XML & JSON is often dominated by
memory allocation as it builds the structures to hold the parsed data.  Do
we have any data? -T


On Mon, Aug 5, 2013 at 10:43 AM, Joe Hildebrand (jhildebr) <
jhildebr@cisco.com> wrote:

> Sorry, my response is also correspondingly long.  There are some original
> comments at the end that are not just responses to Martin.
>
> On 7/30/13 9:05 AM, "Martin Thomson" <martin.thomson@gmail.com> wrote:
>
> >I'm glad that I held this review until Paul's appsarea presentation.
> >This made it very clear to me that the types of concerns I have are
> >considered basically irrelevant by the authors because they aren't
> >interested in changing the design goals.  I don't find the specific
> >design goals to be interesting and am of the opinion that the goals
> >are significant as a matter of general application.  I hope that is
> >clear from my review.
>
> I don't think you made it clear which of the design goals you thought
> weren't interesting.  I'll give my take on each of them here:
>
> > 1.  The representation must be able to unambiguously encode most
> > common data formats used in Internet standards.
>
>
> Seems reasonable.  For example, dates *do* come up quite often (e.g. MIME
> headers).
>
> > 2.  The code for an encoder or parser must be able to be compact in
> > order to support systems with very limited memory and processor
> > power and instruction sets.
>
>
> Seems reasonable, particularly if you're targeting embedded devices and
> sensors.  One of the other corollaries they ought to mention here is that
> devices that have small implementations should be able to receive a subset
> of the value of the format, implementing only the parts that they need to
> and skipping everything they don't understand.
>
> > 3.  Data must be able to be parsed without a schema description.
>
>
> I'd put this first.  It's an absolute must-have for future extensibility.
>
>
> > 4.  The serialization must be reasonably compact, but data
> > compactness is secondary to code compactness for the encoder and
> > parser.
>
>
> This is one of the things that people don't like about XML, which leads
> them to come up with aggressively complicated approaches like EXI.  I
> might argue that it's a little more important than code compactness for my
> use cases, but I think CBOR currently strikes an adequate balance.
>
> > 5.  The format must be applicable to both constrained nodes and high-
> > volume applications.
>
> In IoT applications, both will be true at the same time, so I like this
> requirement.  Low CPU usually means less battery usage anyway.
>
>
> > 6.  The format must support all JSON data types for conversion to and
> > from JSON.
>
>
> Why not?  There are some bits that don't convert quite cleanly enough to
> JSON, but it's pretty close.
>
> > 7.  The format must be extensible, with the extended data being able
> > to be parsed by earlier parsers.
>
>
> This is interesting, and I would be willing to give up several kinds of
> extensibility to get more simplicity.  Perhaps this is your greatest
> issue, and I don't think you are necessarily wrong.
>
>
>
> >I have reviewed the mailing list feedback, and it's not clear to me
> >that there is consensus to publish this.  It might be that the dissent
> >that I have observed is not significant in Barry's learned judgment,
> >or that this is merely dissent on design goals and therefore
> >irrelevant.  The fact that this work isn't a product of a working
> >group still concerns me.  I'm actually interested in why this is
> >AD-sponsored rather than a working group product.
>
> I think this draft is interesting, and might benefit from a short-lived
> working group to ensure that enough people have reviewed it.  As well, I
> think there might need to be a BCP70-style document that explores how to
> design protocols using CBOR, after we've got some implementation
> experience.
>
> I do think that rather a lot of the dissent from the list was heard and
> incorporated, including streaming, which I personally think is an
> over-complication, but others really seemed to want.
>
> >Major issues:
> >My major concerns with this document might be viewed as disagreements
> >with particular design choices.  And, I consider it likely that the
> >authors will conclude that the document is still worth publishing as
> >is, or perhaps with some minor changes.  In the end, I have no issue
> >with that, but expect that the end result will be that the resulting
> >RFC is ignored.
>
> I don't agree that CBOR will be ignored if published in the current form,
> but I do believe it could use a little more review and polish.
>
> >What would cause this to be tragic, is if publication of this were
> >used to prevent other work in this area from subsequently being
> >published.  (For those drawing less-than-charitable inferences from
> >this, I have no desire to throw my hat into this particular ring,
> >except perhaps in jest [1].)
>
> There will be other formats, even if this is published.
>
>
> >This design is far too complex and large.  Regardless of how
> >well-considered it might be, or how well this meets the stated design
> >goals, I can't see anything but failure in this document's future.
> >JSON succeeds largely because it doesn't attempt to address so many
> >needs at once, but I could even make a case for why JSON contains too
> >many features.
>
> I've implemented it twice now, using two different approaches.  The second
> time, I separated the lexing and generation using a SAX-style eventing
> model.  There were a total of eight events fired:
>
> - value
> - array start/stop
> - map start/stop
> - stream start/stop
> - end
>
> That seems roughly minimal for data shaped similarly to JSON (except for
> streams), and significantly less complex than the equivalent SAX2 set for
> XML.
>
> >In comparison with JSON, this document does one major thing wrong: it
> >has more options than JSON in several dimensions.  There are more
> >types, there are several more dimensions for extensibility than JSON:
> >types extensions, values extensions (values of 28-30 in the lower bits
> >of the type byte), plus the ability to apply arbitrary tags to any
> >value.  I believe all of these to be major problems that will cause
> >them to be ignored, poorly implemented, and therefore useless.
>
> I agree that not everyone will implement all of the semantic tags, but the
> fact that you can continue parsing even if you receive a tag you don't
> implement is an interesting and useful property.
>
> I do agree that the extensibility of the patterns 28-30 is scary; those
> came about when streaming was added.
>
> >In part, this complexity produces implementations that are far more
> >complex than they might need to be, unless additional standardization
> >is undertaken.  That idea is something I'm uncomfortable with.
>
> I didn't find either of those properties to be challenging to code around.
>  I error on bit patterns for 28-30, capture but ignore tags in the
> eventing layer, and in the generation layer am able to implement new tags
> with code that looks like:
>
> tag_DATE_STRING: (val)->
>   new Date(val)
>
> Which doesn't seem like an onerous burden for the upside of being able to
> round-trip all of the built-in JavaScript types.
>
>
> I guess I disagree with your characterization of overcomplexity, based on
> implementation experience.
>
> >Design issue: extensibility:
> >This document avoids discussion of issues regarding schema-less
> >document formats that I believe to be fundamental.  These issues are
> >critical when considering the creation of a new interchange format.
> >By choosing this specific design it makes a number of trade-offs that
> >in my opinion are ill-chosen.  This may be in part because the
> >document is unclear about how applications intend to use the documents
> >it describes.
> >
> >You may conclude after reading this review that this is simply because
> >the document does not explain the rationale for selecting the approach
> >it takes.  I hope that isn't the conclusion you reach, but appreciate
> >the reasons why you might do so.
> >
> >I believe the fundamental problem to be one that arises from a
> >misunderstanding about what it means to have no schema.  Aside from
> >formats that require detailed contextual knowledge to interpret, there
> >are several steps toward the impossible, platonic ideal of a perfectly
> >self-describing format.  It's impossible because ultimately the entity
> >that consumes the data is required at some level to understand the
> >semantics that are being conveyed.  In practice, no generic format can
> >effectively self-describe to the level of semantics.
> >
> >This draft describes a format that is more capable at self-description
> >than JSON.  I believe that to not just be unnecessary, but
> >counterproductive.  At best, it might provide implementations with a
> >way to avoid an occasional extra line of code for type conversion.
>
> As an example, the binary string type would be quite useful for JOSE-style
> documents that need to reproduce a set of octets exactly.  Today, Base64
> is required for that in JSON, which is causing the JOSE working group to
> limit the size (and therefore the ease of understanding) of value names,
> as multiple layers of Base64 can expand their output size past the
> external limits placed on applications by browsers.
>
> Secondly, numeric types in JSON are pretty woefully underspecified, and
> cannot be fixed. Transmitting both integers and floats with precise
> understanding of how they will be received is often quite useful.
>
> I don't see either of these as simple type conversion issues.
>
> >Extensibility as it relates to types:
> >The use of extensive typing in CBOR implies an assumption of a major
> >role for generic processing.  XML schema and XQuery demonstrate that
> >this desire is not new, but they also demonstrate the folly of
> >pursuing those goals.
>
> XML schema keeps these bits in a (quite complex) separate stream, which
> requires significant extra processing to add type information into the
> parse stream.  I agree that we've learned that this approach doesn't work
> well.  I don't think that either XSD or XQuery prove anything about
> putting some type information into the data stream itself.
>
>
> >JSON relies on a single mechanism for extensibility. JSON maps that
> >contain unknown or unsupported keys are (usually) ignored.  This
> >allows new values to be added to documents without destroying the
> >ability of an old processor to extract the values that it supports.
> >The limited type information JSON carries leaks out, but it's unclear
> >what value this has to a generic processor.  All of the generic uses
> >I've seen merely carry that type information, no specific use is made
> >of the knowledge it provides.
>
> I don't see how this is relevant.  Most CBOR extensibility for a given
> protocol will follow this model exactly.
>
> >ASN.1 extensibility, as encoded in PER, leads to no type information
> >leaking.  Unsupported extensions are skipped based on a length field.
>
> I'd say that CBOR has a slight advantage here, because you can still get
> some interesting information out of many tag types, even if you don't
> support that tag type.  That allows a non-extensible parsing system to be
> used, if desired.
>
> >(As an aside, PER is omitted from the analysis in the appendix, which
> >I note from the mailing lists is due to its dependency on schema.
> >Interestingly, I believe it to be possible - though not trivial - to
> >create an ASN.1 description with all the properties described in CBOR
> >that would have roughly equivalent, if not fully equivalent,
> >properties to CBOR when serialized.)
>
> Let's add PER to the analysis.  I don't think it will have the properties
> desired, since the decoder has to have access to the same schema the
> sender had.  I agree that it might be possible to create CBOR Encoding
> Rules or the moral equivalent, but I'm not sure I agree that it would be
> worth the effort.
>
> >By defining an extensibility scheme for types, CBOR effectively
> >acknowledges that a generic processor doesn't need type information
> >(just delineation information), but it then creates an extensive type
> >system.  That seems wasteful.
>
> In a given system using CBOR, the protocol designers will decide which
> types to use.  All of the tooling in that ecosystem will parse and encode
> the selected types.
>
> Think of the extensibility here being more for generating lots of
> different protocols on top of CBOR, not lots of different types in one
> protocol.
>
> >Design issue: types:
> >The addition of the ability to carry uninterpreted binary data is a
> >valuable and important feature.  If that was all this document did,
> >then that might have been enough.  But instead it adds numerous
> >different types.
>
> I agree that binary is the most important.  However, unambiguous,
> unescaped, UTF8-only text is also a big win over JSON.  Precise floats are
> a distant third for me, but seem to be the most important for folks that
> do remote sensors.
>
> >I can understand why multiple integer encoding sizes are desirable,
> >and maybe even floating point representations, but this describes
> >bignums in both base 2 and 10,
>
> I agree that the bignums are overkill.  I implemented them the second
> time, but I made sure they were slow. :)
>
> Seriously, I don't see using these in any applications, unless the
> security folks decide they are a good fit for an RSA modulus.
>
> >embedded CBOR documents in three forms,
> >URIs, base64 encoded strings, regexes, MIME bodies, date and times in
> >two different forms, and potentially more.
>
> I think I may be responsible for having suggested URIs and regexes, and
> would fully support removing them from the base draft, along with all of
> the baseX and the (underspecified) MIME stuff.
>
> Please keep the dates.
>
> >I also challenge the assertion made where the code required for
> >parsing a data type produces larger code sizes if performed outside of
> >a common shared library.  That's arguably provably true, but last time
> >I checked a few extra procedure calls (or equivalent) weren't the
> >issue for code size.  Sheer number of options on the other hand might
> >be.
>
> That assertion is also unconvincing to me.  However, I'd really like my
> docs to round-trip, and dates are a big hole in that.  I personally want
> precisely one date type (rather than two), and don't care which one is
> selected.  Javascript floating point milliseconds before/after the epoch
> seems like a reasonable starting point, for example.
>
> >Half-precision floating point numbers are a good example of excessive
> >exuberance.  They are not available in many languages for good reason:
> >they aren't good for much.
>
> They're also relatively new.
>
> >They actually tend to cause errors in
> >software in the same way that threading libraries do: it's not that
> >it's hard to use them, it's that it's harder than people think.  And
> >requiring that implementations parse these creates unnecessary
> >complexity.
>
> I know that it took me an hour or two with the IEEE754 docs to implement
> them in JavaScript, and that code passes a ton of unit tests, including
> subnormals, +/- infinity, and NaNs.  That said, I don't need halfs for my
> use cases, but if sensor folks feel strongly about them, I'm willing to
> keep that code in place.
>
> It's *really* nice to be able to encode NaN and +/- Infinity as separate
> from null, which JSON does not allow.
>
> >I do not believe that for the very small subset of cases
> >where half precision is actually useful, the cost of transmitting the
> >extra 2 bytes of a single-precision number is not going to be a
> >burden.  However, the cost of carrying the code required to decode
> >them is not as trivial as this makes out.  The fact that this requires
> >an appendix would seem to indicate that this is special enough that
> >inclusion should have been very carefully considered.  To be honest,
> >if it were my choice, I would have excluded single-precision floating
> >point numbers as well, they too create more trouble than they are
> >worth.
>
> I'd be fine with that for my use cases, too, but realize there are other
> use cases where people care about both half- and single-precision, and am
> willing to write a couple of extra lines of code to get them onboard.
>
> >Design issue: optionality
> >CBOR embraces the idea that support for types is optional.  Given the
> >extensive nature of the type system, it's almost certain that
> >implementations will choose to avoid implementation of some subset of
> >the types.  The document makes no statements about what types are
> >mandatory for implementations, so I'm not sure how it is possible to
> >provide interoperable implementations.
>
> I think it should say that *none* of the types is mandatory, which I think
> is implied by the text in section 2.4.
>
> >If published in its current form, I predict that only a small subset
> >of types will be implemented and become interoperable.
>
> I'd say let's agree on what those types are, and move all of the others to
> separate drafts.  My list:
>
> - Date (one type)
> - CBOR (sometimes parsed, other times kept intact for processing as a byte
> stream)
>
> >Design issue: tagging
> >The tagging feature has a wonderful property: the ability to create
> >emergency complexity.  Given that a tag itself can be arbitrarily
> >complex, I'm almost certain that this is a feature you do not want.
>
> I'm not sure I understand fully what your issue is.  Protocol designers
> can abuse any format, and when they do, implementors curse them down the
> ages.  Don't do that.
>
> >Minor issues:
> >Design issue: negative numbers
> >Obviously, the authors will be well-prepared for arguments that
> >describe as silly the separation of integer types into distinct
> >positive and negative types.  But it's true, this is a strange choice,
> >and a very strange design.
>
> I think it came from some of the other things in this space (e.g.
> zigzag-encoding).  I think another option would be to have both signed and
> unsigned types.  This choice didn't bother me too much in implementation,
> except when it was repeated in bigints.
>
> >The fact that this format is capable of describing 64-bit negative
> >numbers creates a problem for implementations that I'm surprised
> >hasn't been raised already.  In most languages I use, there is no
> >native type that is capable of carrying the most negative value that
> >can be expressed in this format.  -2^64 is twice as large as a 64-bit
> >twos-complement integer can store.
>
> Yes, that should be mentioned in the doc, probably with a MUST NOT.
>
> >It almost looks as though CBOR is defining a 65-bit, 33-bit or 17-bit
> >twos complement integer format, with the most significant bit isolated
> >from the others, except that the negative expression doesn't even have
> >the good sense to be properly sortable.  Given that and the fact that
> >bignums are also defined, I find this choice to be baffling.
>
> This is a quite valid concern.  Let's get it fixed.
>
> >Document issue: Canonicalization
> >Please remove Section 3.6.  c14n is hard, and this format actually
> >makes it impossible to standardize a c14n scheme, that says a lot
> >about it.  In comparison, JSON is almost trivial to canonicalize.
>
> Agree with removing section 3.6, and moving to another doc if really
> desired.
>
> STRONGLY disagree that JSON is trivial to canonicalize.  The Unicode
> issues notwithstanding (escaping, etc), the numeric format is a mess to
> get into canonical form.
>
> >If the intent of this section is to describe some of the possible
> >gotchas, such as those described in the last paragraph, then that
> >would be good.  Changing the focus to "Canonicalization
> >Considerations" might help.
> >
> >I believe that there are several issues that this section would still
> >need to consider.  For instance, the use of the types that contain
> >additional JSON encoding hints carry additional semantics that might
> >not be significant to the application protocol.
> >
> >Extension based on minor values 28-30 (the "additional information"
> >space):
> >...is impossible as defined.  Section 5.1 seems to imply otherwise.
> >I'm not sure how that would ever happen without breaking existing
> >parsers.  Section 5.2 actually makes this worse by making a
> >wishy-washy commitment to size for 28 and 29, but no commitment at all
> >for 30.
>
> +1.  I'd prefer we remove streaming and tighten the additional information
> bits back up to all being used as in previous versions of the draft.
>
> >Nits:
> >Section 3.7 uses the terms "well-formed" and "valid" in a sense that I
> >believe to be consistent with their use in XML and XML Schema.  I
> >found the definition of "valid" to be a little difficult to parse;
> >specifically, it's not clear whether invalid is the logical inverse of
> >valid.
>
> Agree that language needs to be massaged.
>
> >Appendix B/Table 4 has a TBD on it.  Can this be checked?
>
> Sure.
>
> >Table 4 keeps getting forward references, but it's hidden in an
> >appendix.  I found that frustrating as a reader because the forward
> >references imply that there is something important there.  And that
> >implication was completely right, this needs promotion.  I know why
> >it's hidden, but that reason just supports my earlier theses.
>
> I think it should not be referred to earlier.  It's an implementation
> choice, and not one that I (for example) made.  Thinking about that table
> made it more difficult for me to get started.
>
> >Section 5.1 says "An IANA registry is appropriate here.".  Why not
> >reference Section 7.1?
>
> Yes, that needs to be fixed.
>
> >[1] https://github.com/martinthomson/aweson
>
> Add binary, and remove the string quoting requirements, please. :)
>
>
>
> Other things that ought to be discussed:
>
> I would like to see another design goal: "May be implemented in modern web
> browsers".  That should be possible with the new binary types.
>
>
> I still don't see the need for non-string map keys.  JSON mapping would be
> easier without them, as would uniqueness checking.  If they are to be
> retained, they should have some motivation in the spec, describing how and
> why they might be used.
>
> I wish I could think of another good simple value that we might register
> one day.  The only one I've come up with is "no-op", which I might use in
> a streaming application as a trivial keep-alive or a marker between
> records to ensure parser state sync.  I wouldn't classify that as "good"
> however.
>
> Nested tags ought to be forbidden until we come up with a strong use case
> for them.
>
> I could use some implementation guidance on how to generate the most
> compact floating-point type for a given number, assuming we keep all of
> the floating-point types.
>
> I don't like 2.4.4.2 "Expected Later Encoding for CBOR to JSON
> Converters".  Having a sender care about the encoding of a second format
> at the same time seems unnecessarily complex.  I'd like to see this
> section and the corresponding tags moved to another spec, or just removed.
>
> Similar for tags 33 and 34.  Just send the raw bytes as a byte string;
> there's no need to actually base64 encode.
>
>
> Section 3.2.3, we should call out the heresy of including UTF-16
> surrogates encoded as UTF-8 for those that can't read the UTF-8 spec.
>
> Overall in section 3.2, "should probably issue an error but might take
> some other action" seems like it will cause some interop surprises in
> practice.
>
> Section 3.3, "all number representations are equivalent" is unclear, even
> with the clarifying phrase afterward.
>
> If section 3.6 stays, the numerics need more work.  +/- Infinity should be
> treated like NaN.  "if the result is the same value" would benefit from
> some more clarity.  The tags section is also somewhat unclear.
>
> Section 4.2, what about numbers with uninteresting fractional parts, like
> 1.0?  What about numbers in exponential format without fractional parts,
> like 1e10?  I would recommend against even suggest encoding in place.
> It's likely to cause a security issue for the reason mentioned.
>
> Section 6, including the diagnostic notation is a little strange.  I would
> at least like "it is not meant to be parsed" to be strengthened to "MUST
> NOT be parsed".
>
> Section 7.1, simple values 0..15 can never be used with this construction.
>  If that's intentional, then give a good reason.
>
> Section 7.2, do we have language we can use about how to reclaim
> first-come-first-serve tags that aren't being used anymore?  e.g. the web
> page is down and the requestor may be dead.
>
> In section 7.3, yes, we should make "application/mmmmm+cbor" valid.
>
> In section 8, perhaps mention a stack attack like:
>
> 0x818181818181818181...
>
> I implemented depth counting with a maximum as an approach to avoid this.
>
> There are likely to be lots of other security concerns.
>
> I have checked all of the examples in Appendix A.  I would have expected
>
> 2(h'010000000000000000') | 0xc249010000000000000000
>
> Not 18446744073709551616, since in the diagnostic, I don't necessarily
> support bignums.
>
> Same with 0xc349010000000000000000.
>
> For numbers, section 9.8.1 of ECMA-262 (JSON.stringify) is relevant.  So:
>
> 5.960464477539063e-8 | 0xf90001   (not e-08)
> 0.00006103515625 | 0xf90400       (not e-05)
>
>
>
> In Appendix B, there are holes in the jump table.  If you're going to have
> a table, call out the invalid values, such as 0x1c-0x1f.
>
> In Appendix C, the use of the variable "breakable" is unclear, and it's
> not obvious how you'll get to the "no enclosing indefinite" case.
>
> In Appendix D, shouldn't the input be unsigned or an array of bytes?
>
> Appendix E.1, aren't there some cases of DER where you need the schema to
> parse?  Add PER.
>
> Appendix E, we should mention Smile, since the first two octets are so
> cute.
>
> Overall, I think this doc shows a lot of promise, and I'm looking forward
> to having something on standards track that has these properties.
>
> --
> Joe Hildebrand
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

--047d7b6da6ac58c4a504e336f480
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I like the design of CBOR but my big question is how much =
code-size and memory-size and performance it actually buys you.=C2=A0 My ex=
perience is that the performance of software that parses XML &amp; JSON is =
often dominated by memory allocation as it builds the structures to hold th=
e parsed data.=C2=A0 Do we have any data? -T<br>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon,=
 Aug 5, 2013 at 10:43 AM, Joe Hildebrand (jhildebr) <span dir=3D"ltr">&lt;<=
a href=3D"mailto:jhildebr@cisco.com" target=3D"_blank">jhildebr@cisco.com</=
a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Sorry, my response is also correspondingly l=
ong. =C2=A0There are some original<br>
comments at the end that are not just responses to Martin.<br>
<br>
On 7/30/13 9:05 AM, &quot;Martin Thomson&quot; &lt;<a href=3D"mailto:martin=
.thomson@gmail.com">martin.thomson@gmail.com</a>&gt; wrote:<br>
<br>
&gt;I&#39;m glad that I held this review until Paul&#39;s appsarea presenta=
tion.<br>
&gt;This made it very clear to me that the types of concerns I have are<br>
&gt;considered basically irrelevant by the authors because they aren&#39;t<=
br>
&gt;interested in changing the design goals. =C2=A0I don&#39;t find the spe=
cific<br>
&gt;design goals to be interesting and am of the opinion that the goals<br>
&gt;are significant as a matter of general application. =C2=A0I hope that i=
s<br>
&gt;clear from my review.<br>
<br>
I don&#39;t think you made it clear which of the design goals you thought<b=
r>
weren&#39;t interesting. =C2=A0I&#39;ll give my take on each of them here:<=
br>
<br>
&gt; 1. =C2=A0The representation must be able to unambiguously encode most<=
br>
&gt; common data formats used in Internet standards.<br>
<br>
<br>
Seems reasonable. =C2=A0For example, dates *do* come up quite often (e.g. M=
IME<br>
headers).<br>
<br>
&gt; 2. =C2=A0The code for an encoder or parser must be able to be compact =
in<br>
&gt; order to support systems with very limited memory and processor<br>
&gt; power and instruction sets.<br>
<br>
<br>
Seems reasonable, particularly if you&#39;re targeting embedded devices and=
<br>
sensors. =C2=A0One of the other corollaries they ought to mention here is t=
hat<br>
devices that have small implementations should be able to receive a subset<=
br>
of the value of the format, implementing only the parts that they need to<b=
r>
and skipping everything they don&#39;t understand.<br>
<br>
&gt; 3. =C2=A0Data must be able to be parsed without a schema description.<=
br>
<br>
<br>
I&#39;d put this first. =C2=A0It&#39;s an absolute must-have for future ext=
ensibility.<br>
<br>
<br>
&gt; 4. =C2=A0The serialization must be reasonably compact, but data<br>
&gt; compactness is secondary to code compactness for the encoder and<br>
&gt; parser.<br>
<br>
<br>
This is one of the things that people don&#39;t like about XML, which leads=
<br>
them to come up with aggressively complicated approaches like EXI. =C2=A0I<=
br>
might argue that it&#39;s a little more important than code compactness for=
 my<br>
use cases, but I think CBOR currently strikes an adequate balance.<br>
<br>
&gt; 5. =C2=A0The format must be applicable to both constrained nodes and h=
igh-<br>
&gt; volume applications.<br>
<br>
In IoT applications, both will be true at the same time, so I like this<br>
requirement. =C2=A0Low CPU usually means less battery usage anyway.<br>
<br>
<br>
&gt; 6. =C2=A0The format must support all JSON data types for conversion to=
 and<br>
&gt; from JSON.<br>
<br>
<br>
Why not? =C2=A0There are some bits that don&#39;t convert quite cleanly eno=
ugh to<br>
JSON, but it&#39;s pretty close.<br>
<br>
&gt; 7. =C2=A0The format must be extensible, with the extended data being a=
ble<br>
&gt; to be parsed by earlier parsers.<br>
<br>
<br>
This is interesting, and I would be willing to give up several kinds of<br>
extensibility to get more simplicity. =C2=A0Perhaps this is your greatest<b=
r>
issue, and I don&#39;t think you are necessarily wrong.<br>
<br>
<br>
<br>
&gt;I have reviewed the mailing list feedback, and it&#39;s not clear to me=
<br>
&gt;that there is consensus to publish this. =C2=A0It might be that the dis=
sent<br>
&gt;that I have observed is not significant in Barry&#39;s learned judgment=
,<br>
&gt;or that this is merely dissent on design goals and therefore<br>
&gt;irrelevant. =C2=A0The fact that this work isn&#39;t a product of a work=
ing<br>
&gt;group still concerns me. =C2=A0I&#39;m actually interested in why this =
is<br>
&gt;AD-sponsored rather than a working group product.<br>
<br>
I think this draft is interesting, and might benefit from a short-lived<br>
working group to ensure that enough people have reviewed it. =C2=A0As well,=
 I<br>
think there might need to be a BCP70-style document that explores how to<br=
>
design protocols using CBOR, after we&#39;ve got some implementation<br>
experience.<br>
<br>
I do think that rather a lot of the dissent from the list was heard and<br>
incorporated, including streaming, which I personally think is an<br>
over-complication, but others really seemed to want.<br>
<br>
&gt;Major issues:<br>
&gt;My major concerns with this document might be viewed as disagreements<b=
r>
&gt;with particular design choices. =C2=A0And, I consider it likely that th=
e<br>
&gt;authors will conclude that the document is still worth publishing as<br=
>
&gt;is, or perhaps with some minor changes. =C2=A0In the end, I have no iss=
ue<br>
&gt;with that, but expect that the end result will be that the resulting<br=
>
&gt;RFC is ignored.<br>
<br>
I don&#39;t agree that CBOR will be ignored if published in the current for=
m,<br>
but I do believe it could use a little more review and polish.<br>
<br>
&gt;What would cause this to be tragic, is if publication of this were<br>
&gt;used to prevent other work in this area from subsequently being<br>
&gt;published. =C2=A0(For those drawing less-than-charitable inferences fro=
m<br>
&gt;this, I have no desire to throw my hat into this particular ring,<br>
&gt;except perhaps in jest [1].)<br>
<br>
There will be other formats, even if this is published.<br>
<br>
<br>
&gt;This design is far too complex and large. =C2=A0Regardless of how<br>
&gt;well-considered it might be, or how well this meets the stated design<b=
r>
&gt;goals, I can&#39;t see anything but failure in this document&#39;s futu=
re.<br>
&gt;JSON succeeds largely because it doesn&#39;t attempt to address so many=
<br>
&gt;needs at once, but I could even make a case for why JSON contains too<b=
r>
&gt;many features.<br>
<br>
I&#39;ve implemented it twice now, using two different approaches. =C2=A0Th=
e second<br>
time, I separated the lexing and generation using a SAX-style eventing<br>
model. =C2=A0There were a total of eight events fired:<br>
<br>
- value<br>
- array start/stop<br>
- map start/stop<br>
- stream start/stop<br>
- end<br>
<br>
That seems roughly minimal for data shaped similarly to JSON (except for<br=
>
streams), and significantly less complex than the equivalent SAX2 set for<b=
r>
XML.<br>
<br>
&gt;In comparison with JSON, this document does one major thing wrong: it<b=
r>
&gt;has more options than JSON in several dimensions. =C2=A0There are more<=
br>
&gt;types, there are several more dimensions for extensibility than JSON:<b=
r>
&gt;types extensions, values extensions (values of 28-30 in the lower bits<=
br>
&gt;of the type byte), plus the ability to apply arbitrary tags to any<br>
&gt;value. =C2=A0I believe all of these to be major problems that will caus=
e<br>
&gt;them to be ignored, poorly implemented, and therefore useless.<br>
<br>
I agree that not everyone will implement all of the semantic tags, but the<=
br>
fact that you can continue parsing even if you receive a tag you don&#39;t<=
br>
implement is an interesting and useful property.<br>
<br>
I do agree that the extensibility of the patterns 28-30 is scary; those<br>
came about when streaming was added.<br>
<br>
&gt;In part, this complexity produces implementations that are far more<br>
&gt;complex than they might need to be, unless additional standardization<b=
r>
&gt;is undertaken. =C2=A0That idea is something I&#39;m uncomfortable with.=
<br>
<br>
I didn&#39;t find either of those properties to be challenging to code arou=
nd.<br>
=C2=A0I error on bit patterns for 28-30, capture but ignore tags in the<br>
eventing layer, and in the generation layer am able to implement new tags<b=
r>
with code that looks like:<br>
<br>
tag_DATE_STRING: (val)-&gt;<br>
=C2=A0 new Date(val)<br>
<br>
Which doesn&#39;t seem like an onerous burden for the upside of being able =
to<br>
round-trip all of the built-in JavaScript types.<br>
<br>
<br>
I guess I disagree with your characterization of overcomplexity, based on<b=
r>
implementation experience.<br>
<br>
&gt;Design issue: extensibility:<br>
&gt;This document avoids discussion of issues regarding schema-less<br>
&gt;document formats that I believe to be fundamental. =C2=A0These issues a=
re<br>
&gt;critical when considering the creation of a new interchange format.<br>
&gt;By choosing this specific design it makes a number of trade-offs that<b=
r>
&gt;in my opinion are ill-chosen. =C2=A0This may be in part because the<br>
&gt;document is unclear about how applications intend to use the documents<=
br>
&gt;it describes.<br>
&gt;<br>
&gt;You may conclude after reading this review that this is simply because<=
br>
&gt;the document does not explain the rationale for selecting the approach<=
br>
&gt;it takes. =C2=A0I hope that isn&#39;t the conclusion you reach, but app=
reciate<br>
&gt;the reasons why you might do so.<br>
&gt;<br>
&gt;I believe the fundamental problem to be one that arises from a<br>
&gt;misunderstanding about what it means to have no schema. =C2=A0Aside fro=
m<br>
&gt;formats that require detailed contextual knowledge to interpret, there<=
br>
&gt;are several steps toward the impossible, platonic ideal of a perfectly<=
br>
&gt;self-describing format. =C2=A0It&#39;s impossible because ultimately th=
e entity<br>
&gt;that consumes the data is required at some level to understand the<br>
&gt;semantics that are being conveyed. =C2=A0In practice, no generic format=
 can<br>
&gt;effectively self-describe to the level of semantics.<br>
&gt;<br>
&gt;This draft describes a format that is more capable at self-description<=
br>
&gt;than JSON. =C2=A0I believe that to not just be unnecessary, but<br>
&gt;counterproductive. =C2=A0At best, it might provide implementations with=
 a<br>
&gt;way to avoid an occasional extra line of code for type conversion.<br>
<br>
As an example, the binary string type would be quite useful for JOSE-style<=
br>
documents that need to reproduce a set of octets exactly. =C2=A0Today, Base=
64<br>
is required for that in JSON, which is causing the JOSE working group to<br=
>
limit the size (and therefore the ease of understanding) of value names,<br=
>
as multiple layers of Base64 can expand their output size past the<br>
external limits placed on applications by browsers.<br>
<br>
Secondly, numeric types in JSON are pretty woefully underspecified, and<br>
cannot be fixed. Transmitting both integers and floats with precise<br>
understanding of how they will be received is often quite useful.<br>
<br>
I don&#39;t see either of these as simple type conversion issues.<br>
<br>
&gt;Extensibility as it relates to types:<br>
&gt;The use of extensive typing in CBOR implies an assumption of a major<br=
>
&gt;role for generic processing. =C2=A0XML schema and XQuery demonstrate th=
at<br>
&gt;this desire is not new, but they also demonstrate the folly of<br>
&gt;pursuing those goals.<br>
<br>
XML schema keeps these bits in a (quite complex) separate stream, which<br>
requires significant extra processing to add type information into the<br>
parse stream. =C2=A0I agree that we&#39;ve learned that this approach doesn=
&#39;t work<br>
well. =C2=A0I don&#39;t think that either XSD or XQuery prove anything abou=
t<br>
putting some type information into the data stream itself.<br>
<br>
<br>
&gt;JSON relies on a single mechanism for extensibility. JSON maps that<br>
&gt;contain unknown or unsupported keys are (usually) ignored. =C2=A0This<b=
r>
&gt;allows new values to be added to documents without destroying the<br>
&gt;ability of an old processor to extract the values that it supports.<br>
&gt;The limited type information JSON carries leaks out, but it&#39;s uncle=
ar<br>
&gt;what value this has to a generic processor. =C2=A0All of the generic us=
es<br>
&gt;I&#39;ve seen merely carry that type information, no specific use is ma=
de<br>
&gt;of the knowledge it provides.<br>
<br>
I don&#39;t see how this is relevant. =C2=A0Most CBOR extensibility for a g=
iven<br>
protocol will follow this model exactly.<br>
<br>
&gt;ASN.1 extensibility, as encoded in PER, leads to no type information<br=
>
&gt;leaking. =C2=A0Unsupported extensions are skipped based on a length fie=
ld.<br>
<br>
I&#39;d say that CBOR has a slight advantage here, because you can still ge=
t<br>
some interesting information out of many tag types, even if you don&#39;t<b=
r>
support that tag type. =C2=A0That allows a non-extensible parsing system to=
 be<br>
used, if desired.<br>
<br>
&gt;(As an aside, PER is omitted from the analysis in the appendix, which<b=
r>
&gt;I note from the mailing lists is due to its dependency on schema.<br>
&gt;Interestingly, I believe it to be possible - though not trivial - to<br=
>
&gt;create an ASN.1 description with all the properties described in CBOR<b=
r>
&gt;that would have roughly equivalent, if not fully equivalent,<br>
&gt;properties to CBOR when serialized.)<br>
<br>
Let&#39;s add PER to the analysis. =C2=A0I don&#39;t think it will have the=
 properties<br>
desired, since the decoder has to have access to the same schema the<br>
sender had. =C2=A0I agree that it might be possible to create CBOR Encoding=
<br>
Rules or the moral equivalent, but I&#39;m not sure I agree that it would b=
e<br>
worth the effort.<br>
<br>
&gt;By defining an extensibility scheme for types, CBOR effectively<br>
&gt;acknowledges that a generic processor doesn&#39;t need type information=
<br>
&gt;(just delineation information), but it then creates an extensive type<b=
r>
&gt;system. =C2=A0That seems wasteful.<br>
<br>
In a given system using CBOR, the protocol designers will decide which<br>
types to use. =C2=A0All of the tooling in that ecosystem will parse and enc=
ode<br>
the selected types.<br>
<br>
Think of the extensibility here being more for generating lots of<br>
different protocols on top of CBOR, not lots of different types in one<br>
protocol.<br>
<br>
&gt;Design issue: types:<br>
&gt;The addition of the ability to carry uninterpreted binary data is a<br>
&gt;valuable and important feature. =C2=A0If that was all this document did=
,<br>
&gt;then that might have been enough. =C2=A0But instead it adds numerous<br=
>
&gt;different types.<br>
<br>
I agree that binary is the most important. =C2=A0However, unambiguous,<br>
unescaped, UTF8-only text is also a big win over JSON. =C2=A0Precise floats=
 are<br>
a distant third for me, but seem to be the most important for folks that<br=
>
do remote sensors.<br>
<br>
&gt;I can understand why multiple integer encoding sizes are desirable,<br>
&gt;and maybe even floating point representations, but this describes<br>
&gt;bignums in both base 2 and 10,<br>
<br>
I agree that the bignums are overkill. =C2=A0I implemented them the second<=
br>
time, but I made sure they were slow. :)<br>
<br>
Seriously, I don&#39;t see using these in any applications, unless the<br>
security folks decide they are a good fit for an RSA modulus.<br>
<br>
&gt;embedded CBOR documents in three forms,<br>
&gt;URIs, base64 encoded strings, regexes, MIME bodies, date and times in<b=
r>
&gt;two different forms, and potentially more.<br>
<br>
I think I may be responsible for having suggested URIs and regexes, and<br>
would fully support removing them from the base draft, along with all of<br=
>
the baseX and the (underspecified) MIME stuff.<br>
<br>
Please keep the dates.<br>
<br>
&gt;I also challenge the assertion made where the code required for<br>
&gt;parsing a data type produces larger code sizes if performed outside of<=
br>
&gt;a common shared library. =C2=A0That&#39;s arguably provably true, but l=
ast time<br>
&gt;I checked a few extra procedure calls (or equivalent) weren&#39;t the<b=
r>
&gt;issue for code size. =C2=A0Sheer number of options on the other hand mi=
ght<br>
&gt;be.<br>
<br>
That assertion is also unconvincing to me. =C2=A0However, I&#39;d really li=
ke my<br>
docs to round-trip, and dates are a big hole in that. =C2=A0I personally wa=
nt<br>
precisely one date type (rather than two), and don&#39;t care which one is<=
br>
selected. =C2=A0Javascript floating point milliseconds before/after the epo=
ch<br>
seems like a reasonable starting point, for example.<br>
<br>
&gt;Half-precision floating point numbers are a good example of excessive<b=
r>
&gt;exuberance. =C2=A0They are not available in many languages for good rea=
son:<br>
&gt;they aren&#39;t good for much.<br>
<br>
They&#39;re also relatively new.<br>
<br>
&gt;They actually tend to cause errors in<br>
&gt;software in the same way that threading libraries do: it&#39;s not that=
<br>
&gt;it&#39;s hard to use them, it&#39;s that it&#39;s harder than people th=
ink. =C2=A0And<br>
&gt;requiring that implementations parse these creates unnecessary<br>
&gt;complexity.<br>
<br>
I know that it took me an hour or two with the IEEE754 docs to implement<br=
>
them in JavaScript, and that code passes a ton of unit tests, including<br>
subnormals, +/- infinity, and NaNs. =C2=A0That said, I don&#39;t need halfs=
 for my<br>
use cases, but if sensor folks feel strongly about them, I&#39;m willing to=
<br>
keep that code in place.<br>
<br>
It&#39;s *really* nice to be able to encode NaN and +/- Infinity as separat=
e<br>
from null, which JSON does not allow.<br>
<br>
&gt;I do not believe that for the very small subset of cases<br>
&gt;where half precision is actually useful, the cost of transmitting the<b=
r>
&gt;extra 2 bytes of a single-precision number is not going to be a<br>
&gt;burden. =C2=A0However, the cost of carrying the code required to decode=
<br>
&gt;them is not as trivial as this makes out. =C2=A0The fact that this requ=
ires<br>
&gt;an appendix would seem to indicate that this is special enough that<br>
&gt;inclusion should have been very carefully considered. =C2=A0To be hones=
t,<br>
&gt;if it were my choice, I would have excluded single-precision floating<b=
r>
&gt;point numbers as well, they too create more trouble than they are<br>
&gt;worth.<br>
<br>
I&#39;d be fine with that for my use cases, too, but realize there are othe=
r<br>
use cases where people care about both half- and single-precision, and am<b=
r>
willing to write a couple of extra lines of code to get them onboard.<br>
<br>
&gt;Design issue: optionality<br>
&gt;CBOR embraces the idea that support for types is optional. =C2=A0Given =
the<br>
&gt;extensive nature of the type system, it&#39;s almost certain that<br>
&gt;implementations will choose to avoid implementation of some subset of<b=
r>
&gt;the types. =C2=A0The document makes no statements about what types are<=
br>
&gt;mandatory for implementations, so I&#39;m not sure how it is possible t=
o<br>
&gt;provide interoperable implementations.<br>
<br>
I think it should say that *none* of the types is mandatory, which I think<=
br>
is implied by the text in section 2.4.<br>
<br>
&gt;If published in its current form, I predict that only a small subset<br=
>
&gt;of types will be implemented and become interoperable.<br>
<br>
I&#39;d say let&#39;s agree on what those types are, and move all of the ot=
hers to<br>
separate drafts. =C2=A0My list:<br>
<br>
- Date (one type)<br>
- CBOR (sometimes parsed, other times kept intact for processing as a byte<=
br>
stream)<br>
<br>
&gt;Design issue: tagging<br>
&gt;The tagging feature has a wonderful property: the ability to create<br>
&gt;emergency complexity. =C2=A0Given that a tag itself can be arbitrarily<=
br>
&gt;complex, I&#39;m almost certain that this is a feature you do not want.=
<br>
<br>
I&#39;m not sure I understand fully what your issue is. =C2=A0Protocol desi=
gners<br>
can abuse any format, and when they do, implementors curse them down the<br=
>
ages. =C2=A0Don&#39;t do that.<br>
<br>
&gt;Minor issues:<br>
&gt;Design issue: negative numbers<br>
&gt;Obviously, the authors will be well-prepared for arguments that<br>
&gt;describe as silly the separation of integer types into distinct<br>
&gt;positive and negative types. =C2=A0But it&#39;s true, this is a strange=
 choice,<br>
&gt;and a very strange design.<br>
<br>
I think it came from some of the other things in this space (e.g.<br>
zigzag-encoding). =C2=A0I think another option would be to have both signed=
 and<br>
unsigned types. =C2=A0This choice didn&#39;t bother me too much in implemen=
tation,<br>
except when it was repeated in bigints.<br>
<br>
&gt;The fact that this format is capable of describing 64-bit negative<br>
&gt;numbers creates a problem for implementations that I&#39;m surprised<br=
>
&gt;hasn&#39;t been raised already. =C2=A0In most languages I use, there is=
 no<br>
&gt;native type that is capable of carrying the most negative value that<br=
>
&gt;can be expressed in this format. =C2=A0-2^64 is twice as large as a 64-=
bit<br>
&gt;twos-complement integer can store.<br>
<br>
Yes, that should be mentioned in the doc, probably with a MUST NOT.<br>
<br>
&gt;It almost looks as though CBOR is defining a 65-bit, 33-bit or 17-bit<b=
r>
&gt;twos complement integer format, with the most significant bit isolated<=
br>
&gt;from the others, except that the negative expression doesn&#39;t even h=
ave<br>
&gt;the good sense to be properly sortable. =C2=A0Given that and the fact t=
hat<br>
&gt;bignums are also defined, I find this choice to be baffling.<br>
<br>
This is a quite valid concern. =C2=A0Let&#39;s get it fixed.<br>
<br>
&gt;Document issue: Canonicalization<br>
&gt;Please remove Section 3.6. =C2=A0c14n is hard, and this format actually=
<br>
&gt;makes it impossible to standardize a c14n scheme, that says a lot<br>
&gt;about it. =C2=A0In comparison, JSON is almost trivial to canonicalize.<=
br>
<br>
Agree with removing section 3.6, and moving to another doc if really<br>
desired.<br>
<br>
STRONGLY disagree that JSON is trivial to canonicalize. =C2=A0The Unicode<b=
r>
issues notwithstanding (escaping, etc), the numeric format is a mess to<br>
get into canonical form.<br>
<br>
&gt;If the intent of this section is to describe some of the possible<br>
&gt;gotchas, such as those described in the last paragraph, then that<br>
&gt;would be good. =C2=A0Changing the focus to &quot;Canonicalization<br>
&gt;Considerations&quot; might help.<br>
&gt;<br>
&gt;I believe that there are several issues that this section would still<b=
r>
&gt;need to consider. =C2=A0For instance, the use of the types that contain=
<br>
&gt;additional JSON encoding hints carry additional semantics that might<br=
>
&gt;not be significant to the application protocol.<br>
&gt;<br>
&gt;Extension based on minor values 28-30 (the &quot;additional information=
&quot;<br>
&gt;space):<br>
&gt;...is impossible as defined. =C2=A0Section 5.1 seems to imply otherwise=
.<br>
&gt;I&#39;m not sure how that would ever happen without breaking existing<b=
r>
&gt;parsers. =C2=A0Section 5.2 actually makes this worse by making a<br>
&gt;wishy-washy commitment to size for 28 and 29, but no commitment at all<=
br>
&gt;for 30.<br>
<br>
+1. =C2=A0I&#39;d prefer we remove streaming and tighten the additional inf=
ormation<br>
bits back up to all being used as in previous versions of the draft.<br>
<br>
&gt;Nits:<br>
&gt;Section 3.7 uses the terms &quot;well-formed&quot; and &quot;valid&quot=
; in a sense that I<br>
&gt;believe to be consistent with their use in XML and XML Schema. =C2=A0I<=
br>
&gt;found the definition of &quot;valid&quot; to be a little difficult to p=
arse;<br>
&gt;specifically, it&#39;s not clear whether invalid is the logical inverse=
 of<br>
&gt;valid.<br>
<br>
Agree that language needs to be massaged.<br>
<br>
&gt;Appendix B/Table 4 has a TBD on it. =C2=A0Can this be checked?<br>
<br>
Sure.<br>
<br>
&gt;Table 4 keeps getting forward references, but it&#39;s hidden in an<br>
&gt;appendix. =C2=A0I found that frustrating as a reader because the forwar=
d<br>
&gt;references imply that there is something important there. =C2=A0And tha=
t<br>
&gt;implication was completely right, this needs promotion. =C2=A0I know wh=
y<br>
&gt;it&#39;s hidden, but that reason just supports my earlier theses.<br>
<br>
I think it should not be referred to earlier. =C2=A0It&#39;s an implementat=
ion<br>
choice, and not one that I (for example) made. =C2=A0Thinking about that ta=
ble<br>
made it more difficult for me to get started.<br>
<br>
&gt;Section 5.1 says &quot;An IANA registry is appropriate here.&quot;. =C2=
=A0Why not<br>
&gt;reference Section 7.1?<br>
<br>
Yes, that needs to be fixed.<br>
<br>
&gt;[1] <a href=3D"https://github.com/martinthomson/aweson" target=3D"_blan=
k">https://github.com/martinthomson/aweson</a><br>
<br>
Add binary, and remove the string quoting requirements, please. :)<br>
<br>
<br>
<br>
Other things that ought to be discussed:<br>
<br>
I would like to see another design goal: &quot;May be implemented in modern=
 web<br>
browsers&quot;. =C2=A0That should be possible with the new binary types.<br=
>
<br>
<br>
I still don&#39;t see the need for non-string map keys. =C2=A0JSON mapping =
would be<br>
easier without them, as would uniqueness checking. =C2=A0If they are to be<=
br>
retained, they should have some motivation in the spec, describing how and<=
br>
why they might be used.<br>
<br>
I wish I could think of another good simple value that we might register<br=
>
one day. =C2=A0The only one I&#39;ve come up with is &quot;no-op&quot;, whi=
ch I might use in<br>
a streaming application as a trivial keep-alive or a marker between<br>
records to ensure parser state sync. =C2=A0I wouldn&#39;t classify that as =
&quot;good&quot;<br>
however.<br>
<br>
Nested tags ought to be forbidden until we come up with a strong use case<b=
r>
for them.<br>
<br>
I could use some implementation guidance on how to generate the most<br>
compact floating-point type for a given number, assuming we keep all of<br>
the floating-point types.<br>
<br>
I don&#39;t like 2.4.4.2 &quot;Expected Later Encoding for CBOR to JSON<br>
Converters&quot;. =C2=A0Having a sender care about the encoding of a second=
 format<br>
at the same time seems unnecessarily complex. =C2=A0I&#39;d like to see thi=
s<br>
section and the corresponding tags moved to another spec, or just removed.<=
br>
<br>
Similar for tags 33 and 34. =C2=A0Just send the raw bytes as a byte string;=
<br>
there&#39;s no need to actually base64 encode.<br>
<br>
<br>
Section 3.2.3, we should call out the heresy of including UTF-16<br>
surrogates encoded as UTF-8 for those that can&#39;t read the UTF-8 spec.<b=
r>
<br>
Overall in section 3.2, &quot;should probably issue an error but might take=
<br>
some other action&quot; seems like it will cause some interop surprises in<=
br>
practice.<br>
<br>
Section 3.3, &quot;all number representations are equivalent&quot; is uncle=
ar, even<br>
with the clarifying phrase afterward.<br>
<br>
If section 3.6 stays, the numerics need more work. =C2=A0+/- Infinity shoul=
d be<br>
treated like NaN. =C2=A0&quot;if the result is the same value&quot; would b=
enefit from<br>
some more clarity. =C2=A0The tags section is also somewhat unclear.<br>
<br>
Section 4.2, what about numbers with uninteresting fractional parts, like<b=
r>
1.0? =C2=A0What about numbers in exponential format without fractional part=
s,<br>
like 1e10? =C2=A0I would recommend against even suggest encoding in place.<=
br>
It&#39;s likely to cause a security issue for the reason mentioned.<br>
<br>
Section 6, including the diagnostic notation is a little strange. =C2=A0I w=
ould<br>
at least like &quot;it is not meant to be parsed&quot; to be strengthened t=
o &quot;MUST<br>
NOT be parsed&quot;.<br>
<br>
Section 7.1, simple values 0..15 can never be used with this construction.<=
br>
=C2=A0If that&#39;s intentional, then give a good reason.<br>
<br>
Section 7.2, do we have language we can use about how to reclaim<br>
first-come-first-serve tags that aren&#39;t being used anymore? =C2=A0e.g. =
the web<br>
page is down and the requestor may be dead.<br>
<br>
In section 7.3, yes, we should make &quot;application/mmmmm+cbor&quot; vali=
d.<br>
<br>
In section 8, perhaps mention a stack attack like:<br>
<br>
0x818181818181818181...<br>
<br>
I implemented depth counting with a maximum as an approach to avoid this.<b=
r>
<br>
There are likely to be lots of other security concerns.<br>
<br>
I have checked all of the examples in Appendix A. =C2=A0I would have expect=
ed<br>
<br>
2(h&#39;010000000000000000&#39;) | 0xc249010000000000000000<br>
<br>
Not 18446744073709551616, since in the diagnostic, I don&#39;t necessarily<=
br>
support bignums.<br>
<br>
Same with 0xc349010000000000000000.<br>
<br>
For numbers, section 9.8.1 of ECMA-262 (JSON.stringify) is relevant. =C2=A0=
So:<br>
<br>
5.960464477539063e-8 | 0xf90001 =C2=A0 (not e-08)<br>
0.00006103515625 | 0xf90400 =C2=A0 =C2=A0 =C2=A0 (not e-05)<br>
<br>
<br>
<br>
In Appendix B, there are holes in the jump table. =C2=A0If you&#39;re going=
 to have<br>
a table, call out the invalid values, such as 0x1c-0x1f.<br>
<br>
In Appendix C, the use of the variable &quot;breakable&quot; is unclear, an=
d it&#39;s<br>
not obvious how you&#39;ll get to the &quot;no enclosing indefinite&quot; c=
ase.<br>
<br>
In Appendix D, shouldn&#39;t the input be unsigned or an array of bytes?<br=
>
<br>
Appendix E.1, aren&#39;t there some cases of DER where you need the schema =
to<br>
parse? =C2=A0Add PER.<br>
<br>
Appendix E, we should mention Smile, since the first two octets are so<br>
cute.<br>
<br>
Overall, I think this doc shows a lot of promise, and I&#39;m looking forwa=
rd<br>
to having something on standards track that has these properties.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Joe Hildebrand<br>
<br>
_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
</font></span></blockquote></div><br></div>

--047d7b6da6ac58c4a504e336f480--

From wassim.haddad@ericsson.com  Mon Aug  5 15:58:48 2013
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 A6B0F21F9F2D for <gen-art@ietfa.amsl.com>; Mon,  5 Aug 2013 15:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.001, 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 7P3z1co1np6a for <gen-art@ietfa.amsl.com>; Mon,  5 Aug 2013 15:58:43 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1AE21F9F12 for <gen-art@ietf.org>; Mon,  5 Aug 2013 15:58:43 -0700 (PDT)
X-AuditID: c6180641-b7f986d000007a82-8b-52002e22ef87
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id AE.97.31362.22E20025; Tue,  6 Aug 2013 00:58:42 +0200 (CEST)
Received: from eusjgala119.dyn.sj.us.am.ericsson.se (147.117.188.134) by smtp-am.internal.ericsson.com (147.117.188.83) with Microsoft SMTP Server id 14.2.328.9; Mon, 5 Aug 2013 18:58:42 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1BCD31F2-9BA8-4215-9AB4-64438D16435E"
Date: Mon, 5 Aug 2013 15:58:50 -0700
Message-ID: <878D10B0-A968-46C8-8520-2C9F2E7A55C5@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
MIME-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphluLIzCtJLcpLzFFi42KZXLonUFdJjyHIYMcfE4vFk6axWFx99ZnF gcljyZKfTB5fLn9mC2CK4rJJSc3JLEst0rdL4Mr40RhUsEmkYsqx60wNjL8Fuxg5OSQETCQe bdjBDmGLSVy4t56ti5GLQ0jgKKPEl4nv2CGcI4wSG17cZQGpYhMwkPi6/CwriM0skCTxbV0T I4gtLOAhsfTbf7AaFgEViUO3XoHFeQXsJT6ubGKBqE+X6Dx+nxnEFhHQlJi74i0TRI2exJnN c4FqOICukJXY+TsJJCwkoC4x5dYElgmMfLOQbJuFpAMiri2xbOFrZghbR2LB7k9smOLaEmcO PGZawMi2ipGjtDi1LDfdyHATIzAkj0mwOe5gXPDJ8hCjNAeLkjjvBr0zgUIC6YklqdmpqQWp RfFFpTmpxYcYmTg4pRoYl5xreHitt/6RlOo8H5t9pp4JUfqHmBu46gNUD1Ty6qVUfDT+FcP+ Xd430W+K8ZeP/YebdKdHOp294jsvu6AzT4A9QHq9oX+1Ay8/k3WmZG/93UcvPyZIbbVyrnmg usKw9aQ7l7e1z87MtDYrvb1cP3ZYrHp98G7nWecbPbabJ+61PHztXasSS3FGoqEWc1FxIgBv ji3uFwIAAA==
Cc: draft-ietf-manet-nhdp-olsrv2-sec.all@tools.ietf.org
Subject: [Gen-art]  Gen-ART Review of draft-ietf-manet-nhdp-olsrv2-sec-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, 05 Aug 2013 22:58:48 -0000

--Apple-Mail=_1BCD31F2-9BA8-4215-9AB4-64438D16435E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"

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

Document: draft-ietf-manet-nhdp-olsrv2-sec-03
Reviewer:  Wassim Haddad
Review Date: 05 August 2013
IETF LC End Date: 02 August 2013
IETF Telechat Date: 15 August 2013

Summary:  This draft is ready for publication as proposed standard=20

- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.





--Apple-Mail=_1BCD31F2-9BA8-4215-9AB4-64438D16435E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="us-ascii"

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><pre =
style=3D"word-wrap: break-word; white-space: pre-wrap; "><div =
style=3D"font-family: Helvetica; white-space: normal; ">I am the =
assigned Gen-ART reviewer for this draft. For background on =
Gen-ART,&nbsp;<br>please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;<br><br>Document:&nb=
sp;draft-ietf-manet-nhdp-olsrv2-sec-03<br>Reviewer: &nbsp;Wassim =
Haddad<br>Review Date: 05 August 2013<br>IETF LC End Date: 02 August =
2013<br>IETF Telechat Date: 15 August 2013<br><br>Summary: &nbsp;This =
draft is ready for publication as proposed standard&nbsp;</div><div =
style=3D"font-family: Helvetica; white-space: normal; "><br></div><div =
style=3D"font-family: Helvetica; white-space: normal; ">- Major Issues: =
None<br><br>- Minor Issues: None<br><br><br>Regards,<br><br>Wassim =
H.</div></pre><div><br></div><div apple-content-edited=3D"true">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
medium; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div></div><br class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_1BCD31F2-9BA8-4215-9AB4-64438D16435E--

From brian.e.carpenter@gmail.com  Mon Aug  5 21:26:41 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41C7A21F9ADC for <gen-art@ietfa.amsl.com>; Mon,  5 Aug 2013 21:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T+eFd8AeWwz1 for <gen-art@ietfa.amsl.com>; Mon,  5 Aug 2013 21:26:40 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id C052521F9ADA for <gen-art@ietf.org>; Mon,  5 Aug 2013 21:26:40 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id wz12so4163857pbc.39 for <gen-art@ietf.org>; Mon, 05 Aug 2013 21:26:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=01iEjCDMxiJSBhlRm3iWeTGdg46VcvYsjalTN0CJ9kE=; b=DJnv7RpciTxLQh2Jzl1S7BrnEr3qzJAnkHKRae46dV+fh6872otC6hfNFfl80z4UZx Bt6+pTJTOYGzTin+OX3hH2HO5+BdIcPkFZOFc+i020BGXhbOMWhH6sFPlz/EwZ5DcyN7 +u0KMbz3joUCW1DQTGvMAx2YMdPmLbsfXbiluhuSRB9CqXa8JBZvtGUyTcP2+Ek3/BQq SK4NKQu7WRLyqTh6eAMVfCZNINJYxHOs8UC5P/PxBYV45SmJK+9XMo+1jxbT9hYSxlFa 2cuAI+N784wIuE1RYLFSg/LLZ4mZ7ywHyxM2Oyakh30IJ91WPpy8WQvxci1YpOmh/6fp dH+Q==
X-Received: by 10.68.105.195 with SMTP id go3mr25417066pbb.180.1375763200187;  Mon, 05 Aug 2013 21:26:40 -0700 (PDT)
Received: from [172.24.31.170] (wireless-nat-1.auckland.ac.nz. [130.216.30.112]) by mx.google.com with ESMTPSA id is3sm2568673pbc.25.2013.08.05.21.26.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 21:26:39 -0700 (PDT)
Message-ID: <52007AFE.1040902@gmail.com>
Date: Tue, 06 Aug 2013 16:26:38 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-mpls-tp-mip-mep-map.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART LC review of draft-ietf-mpls-tp-mip-mep-map-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: Tue, 06 Aug 2013 04:26:41 -0000

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

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

Document: draft-ietf-mpls-tp-mip-mep-map-08.txt (Informational)
Reviewer: Brian Carpenter
Review Date: 2013-08-06
IETF LC End Date: 2013-08-21
IESG Telechat date:

Summary:  Ready
--------

Minor Issue:
------------

I don't see the value in citing RFC 2119. I only spotted two MUSTs, which would
be perfectly fine in lower case. The second of them is in a sentence whose
syntax needs fixing:

"It MUST be assured that all traffic for which the MEP/MIP is associated with
must pass through or be terminated at that point."

I think this means:

"All traffic associated with the MEP/MIP must pass through or be terminated
at that point."


From chris.dearlove@baesystems.com  Tue Aug  6 02:03:33 2013
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53C1121F9D96 for <gen-art@ietfa.amsl.com>; Tue,  6 Aug 2013 02:03:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.494
X-Spam-Level: 
X-Spam-Status: No, score=-8.494 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L22kTWCW-NEc for <gen-art@ietfa.amsl.com>; Tue,  6 Aug 2013 02:03:29 -0700 (PDT)
Received: from ukmta1.baesystems.com (unknown [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 482FE21F9D17 for <gen-art@ietf.org>; Tue,  6 Aug 2013 02:03:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,825,1367967600";  d="scan'208,217";a="361763564"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 06 Aug 2013 10:03:21 +0100
X-IronPort-AV: E=Sophos;i="4.89,825,1367967600"; d="scan'208,217";a="23644627"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 06 Aug 2013 10:03:21 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.90]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.02.0328.009; Tue, 6 Aug 2013 10:03:21 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Wassim Haddad <wassim.haddad@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Gen-ART Review of draft-ietf-manet-nhdp-olsrv2-sec-03
Thread-Index: AQHOki9kWCf9oJKwY06FobB8p5oXBpmH4w8A
Date: Tue, 6 Aug 2013 09:03:21 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBC5269@GLKXM0002V.GREENLNK.net>
References: <878D10B0-A968-46C8-8520-2C9F2E7A55C5@ericsson.com>
In-Reply-To: <878D10B0-A968-46C8-8520-2C9F2E7A55C5@ericsson.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBC5269GLKXM0002VGREEN_"
MIME-Version: 1.0
Cc: "draft-ietf-manet-nhdp-olsrv2-sec.all@tools.ietf.org" <draft-ietf-manet-nhdp-olsrv2-sec.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-manet-nhdp-olsrv2-sec-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, 06 Aug 2013 09:03:33 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBC5269GLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Wassim

Thank you for that,

Christopher

--
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194 |  Fax: +44 1245 242124
chris.dearlove@baesystems.com<mailto:chris.dearlove@baesystems.com> | http:=
//www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

From: Wassim Haddad [mailto:wassim.haddad@ericsson.com]
Sent: 05 August 2013 23:59
To: gen-art@ietf.org
Cc: Wassim Haddad; draft-ietf-manet-nhdp-olsrv2-sec.all@tools.ietf.org
Subject: [Gen-art] Gen-ART Review of draft-ietf-manet-nhdp-olsrv2-sec-03


*** WARNING ***
This message originates from outside our organisation, either from an exter=
nal partner or the internet.
Keep this in mind if you answer this message.
For information regarding Red Flags that you can look out for in emails you=
 receive, click here<http://intranet.ent.baesystems.com/howwework/security/=
spotlights/Documents/Red%20Flags.pdf>.
If you feel the email is suspicious, please follow this process<http://intr=
anet.ent.baesystems.com/howwework/security/spotlights/Documents/Dealing%20W=
ith%20Suspicious%20Emails.pdf>.

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/GenArt=
faq>

Document: draft-ietf-manet-nhdp-olsrv2-sec-03
Reviewer:  Wassim Haddad
Review Date: 05 August 2013
IETF LC End Date: 02 August 2013
IETF Telechat Date: 15 August 2013

Summary:  This draft is ready for publication as proposed standard



- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.




********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBC5269GLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 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:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{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:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Wassim<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thank you for that,<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Christopher<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">--
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Christopher Dearlove<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: &#43;44 1245 242194&nbsp;|&nbsp; Fax: &#43;44 1245 242124<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><a href=3D"mailto:chris.dearlove@baesystems.com"><span style=3D"color:#1F=
497D;text-decoration:none">chris.dearlove@baesystems.com</span></a>
 | http://www.baesystems.com<br>
<br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US">BAE Systems (O=
perations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Wassim Haddad [mailto:wassim.haddad@ericsson.com]
<br>
<b>Sent:</b> 05 August 2013 23:59<br>
<b>To:</b> gen-art@ietf.org<br>
<b>Cc:</b> Wassim Haddad; draft-ietf-manet-nhdp-olsrv2-sec.all@tools.ietf.o=
rg<br>
<b>Subject:</b> [Gen-art] Gen-ART Review of draft-ietf-manet-nhdp-olsrv2-se=
c-03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"border:solid black 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;color:black"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><b><span style=3D"font-size:15.0pt;font-family:&quot;Arial&quot;,=
&quot;sans-serif&quot;;color:#333972">*** WARNING ***<o:p></o:p></span></b>=
</p>
</div>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"margin-bottom:12.0pt;text-=
align:center;background:white">
<em><span style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;san=
s-serif&quot;;color:#333972">This message originates from outside our organ=
isation, either from an external partner or the internet.</span></em><i><sp=
an style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif=
&quot;;color:#333972"><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Ke=
ep this in mind if you answer this message.</span></em><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Fo=
r information regarding Red Flags that you can look out for in emails you r=
eceive, click
<a href=3D"http://intranet.ent.baesystems.com/howwework/security/spotlights=
/Documents/Red%20Flags.pdf">
here</a>.</span></em><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">If=
 you feel the email is suspicious, please follow
<a href=3D"http://intranet.ent.baesystems.com/howwework/security/spotlights=
/Documents/Dealing%20With%20Suspicious%20Emails.pdf">
this process</a>.</span></em></span></i><span style=3D"font-size:10.5pt;fon=
t-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#333972"><o:p></o:p=
></span></p>
</div>
</div>
<div>
<pre style=3D"word-wrap: break-word;white-space:pre-wrap"><span style=3D"fo=
nt-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">I am the assigned G=
en-ART reviewer for this draft. For background on Gen-ART,&nbsp;<br>please =
see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki=
/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;=
<br><br>Document:&nbsp;draft-ietf-manet-nhdp-olsrv2-sec-03<br>Reviewer: &nb=
sp;Wassim Haddad<br>Review Date: 05 August 2013<br>IETF LC End Date: 02 Aug=
ust 2013<br>IETF Telechat Date: 15 August 2013<br><br>Summary: &nbsp;This d=
raft is ready for publication as proposed standard&nbsp;<o:p></o:p></span><=
/pre>
</div>
<div>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;"><o:p>&nbsp;</o:p></span></pre>
</div>
<div>
<pre><span style=3D"font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot=
;">- Major Issues: None<br><br>- Minor Issues: None<br><br><br>Regards,<br>=
<br>Wassim H.<o:p></o:p></span></pre>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;He=
lvetica&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span><=
/p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBC5269GLKXM0002VGREEN_--


From christer.holmberg@ericsson.com  Tue Aug  6 07:19:25 2013
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BDE821F9A4B for <gen-art@ietfa.amsl.com>; Tue,  6 Aug 2013 07:19:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.793
X-Spam-Level: 
X-Spam-Status: No, score=-5.793 tagged_above=-999 required=5 tests=[AWL=0.455,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rf35IinoL9mt for <gen-art@ietfa.amsl.com>; Tue,  6 Aug 2013 07:19:20 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id A3B6121F9F5E for <gen-art@ietf.org>; Tue,  6 Aug 2013 07:19:18 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f0b6d0000002d5-44-520105e45f21
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 23.D5.00725.4E501025; Tue,  6 Aug 2013 16:19:17 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.135]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.02.0328.009; Tue, 6 Aug 2013 16:19:16 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-tls-oob-pubkey-09
Thread-Index: Ac6SrveOVn5FNGmwQR6MMa+u1J/h4w==
Date: Tue, 6 Aug 2013 14:19:16 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C41E75F@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C41E75FESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHLMWRmVeSWpSXmKPExsUyM+Jvre5TVsYgg299IhZ7Ws+wW1x99ZnF gcljyZKfTB5fLn9mC2CK4rJJSc3JLEst0rdL4Mo4e2obU8HNa4wVD59eZmpgPLqbsYuRk0NC wESifckjJghbTOLCvfVsXYxcHEIChxklNt/8wgrhLGaU+DfhNlCGg4NNwEKi+582SIOIgKbE 3BVvwZqZBZIl3m+6zwJiCwuYS+x42ckGUWMj0bnoDTOErSex6ssaMJtFQEXi+a7fYEfwCvhK nJ+/H6yXEeiI76fWQM0Ul/hw8DozxHECEkv2nIeyRSVePv7HCmErSTQuecIKUZ8vcejTJlaI mYISJ2c+YZnAKDwLyahZSMpmISmDiOtILNj9iQ3C1pZYtvA1M4x95sBjJmTxBYzsqxjZcxMz c9LLDTcxAuPk4JbfujsYT50TOcQozcGiJM67Se9MoJBAemJJanZqakFqUXxRaU5q8SFGJg5O qQZGkQMHef1PmDD5HebOFT56SjD4wtFKXX695g0L7NdZmmRd/CzCrXMv1o9d/6cNn/Ykrspv Ry/8+bLlvcM5nsXrTjW8Wr+jODz82Lyws2cOtZgfzWLpUTte7RLCvCvgkLVVbqSWlWmtVUnu E77sj/MXBzE3GEqpf/U/PIHvR/Pfn7VazvYBzleUWIozEg21mIuKEwHhmM2KYQIAAA==
Cc: "draft-ietf-tls-oob-pubkey.all@tools.ietf.org" <draft-ietf-tls-oob-pubkey.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-tls-oob-pubkey-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 14:19:25 -0000

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

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



Document:                         draft-ietf-tls-oob-pubkey-09



Reviewer:                           Christer Holmberg



Review Date:                     6 August 2013



IETF LC End Date:             16 August 2013



IETF Telechat Date:         N/A



Summary:  There some editorial issues, that I personally think would make t=
he document more clear.



Major Issues: None



Minor Issues:


GENERAL:
=3D=3D=3D=3D=3D=3D=3D=3D

QGEN_1:

The document talks about "raw public keys". I know it is a commonly used te=
rm, but it is not defined in RFC 5246, I think it would be good to have a s=
hort section which
describes what it is, the advantages compared to certificates etc. I KNOW t=
here is some text in the Security Section, but I think a general descriptio=
n would be useful in
the beginning of the spec also. Note that the security aspects do not need =
to be described in such section.


QGEN_2:

Some parts of the document talk about "TLS clients and servers", while othe=
r parts talk only about "clients and servers". I suggest to use consistant =
wording.


Section 1:
=3D=3D=3D=3D=3D=3D=3D


Q1_1:

s/"using the TLS handshake"/"as part of the TLS handshake procedure"


Q1_2:

s/"TLS handshake and validated"/"TLS handshake and are validated"


Q1_3:

At the end of the section, I would suggest a new paragraph, which says some=
thing like:

                             "Section 3 defines the two TLS extensions 'cli=
ent_certificate_type' and 'server_certificate_type',
                             which can be used as part of an extended TLS h=
andshake when raw public keys are to be used. Section
                             4 defines the TLS handshake extension."


Section 3:
=3D=3D=3D=3D=3D=3D=3D


Q3_1:

I would suggest to have an introduction sub-section, and then separate sub-=
sections for
the 'client_certificate_type' and 'server_certificate_type' usage details, =
e.g. something like:

                             3.1.                      General
                             3.2.                      'client_certificate_=
type' usage

                             When used in a Client Hello message, the 'clie=
nt_certificate_type' is used to blah blah blah
                             When used in a Server Hello message, the 'clie=
nt_certificate_type' is used to blah blah blah

                             3.3.                      'server_certificate_=
type' usage

                             When used in a Client Hello message, the 'serv=
er_certificate_type' is used to blah blah blah
                             When used in a Server Hello message, the 'serv=
er_certificate_type' is used to blah blah blah"


(Of course, if you rather want to devide the sub-sctions based on hello typ=
e, I'm fine with that also :)


Q3_2:

The first sentence in the section says:

                             "This section describes the changes to the TLS=
 handshake message contents when raw public keys are to be used."


I think this is a little missleading, as the TLS handshake message is exten=
ded in section 4. So, similar to the text I suggested
for section 1, I suggest something like:


                             "This section defines the two TLS extensions '=
client_certificate_type' and 'server_certificate_type',
                             which can be used as part of an extended TLS h=
andshake when raw public keys are to be used. Section
                             4 defines the TLS handshake extension."


SECTION 4:
=3D=3D=3D=3D=3D=3D=3D=3D

Q4_1:

I would suggest an introduction section, e.g. something like:

                             "4.1. General

                             This section extends the ClientHello and Serve=
rHello messages, according
                             to the extension procedures defined in [RFC524=
6].

                             The specification does not extend or modify an=
y other TLS messages."

...and then remove current sections 4.3. and 4.4.


Section 5:
=3D=3D=3D=3D=3D=3D=3D


Q5_1:

I would suggest to have sub-sections for each example, e.g. something like:

                             5.1. TLS client indicates ability to receive a=
nd validate raw public keys from the server
                             5.2. TLS client ans server use raw public keys=
.
                             5.3. Combined usage of raw publis keys and X.5=
09 certificate

Then, each sub-section would start with: "This section shows an example whe=
re blah blah blah...".


Q5_2:

The text in the FIRST example says:

                             "The 'client_certificate_type' extension indic=
ates this in [1].  When the
                             TLS server receives the client hello it proces=
ses the 'client_certificate_type' extension."

However, in the flow picutre there is no 'client_certificate_type'. Is ther=
e some copy/paste error?









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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Vain tekstin\00E4 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Shkpostityyli17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.VaintekstinChar
	{mso-style-name:"Vain tekstin\00E4 Char";
	mso-style-priority:99;
	mso-style-link:"Vain tekstin\00E4";
	font-family:"Calibri","sans-serif";
	mso-fareast-language:FI;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 2.0cm 70.85pt 2.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FI" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText"><span lang=3D"EN-US">I am the assigned Gen-ART re=
viewer for this draft. For background on Gen-ART, please see the FAQ at &lt=
;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http:/=
/wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Document:&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-tls-oob-pubke=
y-09<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Reviewer:&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Christer Hol=
mberg<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Review Date:&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6 August 2013<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">IETF LC End Date:&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 16 August 201=
3<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">IETF Telechat Date:&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; N/A<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Summary:&nbsp; There some ed=
itorial issues, that I personally think would make the document more clear.=
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Major Issues: None<o:p></o:p=
></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Minor Issues:<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">GENERAL:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D=3D=3D=3D=3D=3D=3D<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">QGEN_1:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The document talks about &quot;=
raw public keys&quot;. I know it is a commonly used term, but it is not def=
ined in RFC 5246, I think it would be good to have a short section which<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">describes what it is, the advan=
tages compared to certificates etc. I KNOW there is some text in the Securi=
ty Section, but I think a general description would be useful in<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">the beginning of the spec also.=
 Note that the security aspects do not need to be described in such section=
.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">QGEN_2:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Some parts of the document talk=
 about &quot;TLS clients and servers&quot;, while other parts talk only abo=
ut &quot;clients and servers&quot;. I suggest to use consistant wording.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Section 1:<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D=3D=3D=3D=3D=3D<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Q1_1:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">s/&quot;using the TLS handshake=
&quot;/&quot;as part of the TLS handshake procedure&quot;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Q1_2:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">s/&quot;TLS handshake and valid=
ated&quot;/&quot;TLS handshake and are validated&quot;<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Q1_3:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">At the end of the section, I wo=
uld suggest a new paragraph, which says something like:<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;Sectio=
n 3 defines the two TLS extensions 'client_certificate_type' and 'server_ce=
rtificate_type',
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; which can be=
 used as part of an extended TLS handshake when raw public keys are to be u=
sed. Section<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4 defines th=
e TLS handshake extension.&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Section 3:<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D=3D=3D=3D=3D=3D<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Q3_1:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I would suggest to have an intr=
oduction sub-section, and then separate sub-sections for
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">the 'client_certificate_type' a=
nd 'server_certificate_type' usage details, e.g. something like:<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.1.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; General<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.2. &nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 'client_certificate_type' usage<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When used in=
 a Client Hello message, the 'client_certificate_type' is used to blah blah=
 blah<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When used in=
 a Server Hello message, the 'client_certificate_type' is used to blah blah=
 blah<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.3. &nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 'server_certificate_type' usage<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When used in=
 a Client Hello message, the 'server_certificate_type' is used to blah blah=
 blah<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When used in=
 a Server Hello message, the 'server_certificate_type' is used to blah blah=
 blah&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">(Of course, if you rather want =
to devide the sub-sctions based on hello type, I'm fine with that also :)<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Q3_2:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The first sentence in the secti=
on says:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;This s=
ection describes the changes to the TLS handshake message contents when raw=
 public keys are to be used.&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I think this is a little missle=
ading, as the TLS handshake message is extended in section 4. So, similar t=
o the text I suggested<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">for section 1, I suggest someth=
ing like:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;This s=
ection defines the two TLS extensions 'client_certificate_type' and 'server=
_certificate_type',
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; which can be=
 used as part of an extended TLS handshake when raw public keys are to be u=
sed. Section<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4 defines th=
e TLS handshake extension.&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">SECTION 4:<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D=3D=3D=3D=3D=3D=3D<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Q4_1:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I would suggest an introduction=
 section, e.g. something like:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;4.1. G=
eneral<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This section=
 extends the ClientHello and ServerHello messages, according
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to the exten=
sion procedures defined in [RFC5246].<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The specific=
ation does not extend or modify any other TLS messages.&quot;<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">...and then remove current sect=
ions 4.3. and 4.4.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Section 5:<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D=3D=3D=3D=3D=3D<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Q5_1: <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I would suggest to have sub-sec=
tions for each example, e.g. something like:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5.1. TLS cli=
ent indicates ability to receive and validate raw public keys from the serv=
er<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5.2. TLS cli=
ent ans server use raw public keys.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5.3. Combine=
d usage of raw publis keys and X.509 certificate<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Then, each sub-section would st=
art with: &quot;This section shows an example where blah blah blah...&quot;=
.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Q5_2: <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The text in the FIRST example s=
ays:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;The 'c=
lient_certificate_type' extension indicates this in [1].&nbsp; When the<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TLS server receiv=
es the client hello it processes the 'client_certificate_type' extension.&q=
uot;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">However, in the flow picutre th=
ere is no 'client_certificate_type'. Is there some copy/paste error?<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1C41E75FESESSMB209erics_--

From alexey.melnikov@isode.com  Thu Aug  8 03:55:47 2013
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9838A11E811D for <gen-art@ietfa.amsl.com>; Thu,  8 Aug 2013 03:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.859
X-Spam-Level: 
X-Spam-Status: No, score=-101.859 tagged_above=-999 required=5 tests=[AWL=0.740, 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 LD0-W68xsF7e for <gen-art@ietfa.amsl.com>; Thu,  8 Aug 2013 03:55:43 -0700 (PDT)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 367FD21E8083 for <gen-art@ietf.org>; Thu,  8 Aug 2013 03:55:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1375959341; d=isode.com; s=selector; i=@isode.com; bh=M//c8DHANzr2R/3lvfiZ8lP6blX0U1IG1cqZQN9xmNU=; 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=CUtiisSKBPlg1lKnl95KLLk70J/4vN/kEH4M7ApSYnp6LZj2F/MA31rMwwFVwdabjlBuJP reVn/ByCIP6Stm2NOmDOzbR0ohiqcW3bvwbw7uvHPp1EmsqKoGZkoPeNoDbPM6xAmhxp6m D37fATvM8ab0iTSzn6Xr1044xvDC69U=;
Received: from [192.168.0.4] (cpc5-nmal20-2-0-cust24.19-2.cable.virginmedia.com [92.234.84.25])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <UgN5KgBjM7B2@waldorf.isode.com>; Thu, 8 Aug 2013 11:55:41 +0100
Message-ID: <52037931.5070602@isode.com>
Date: Thu, 08 Aug 2013 11:55:45 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: draft-montemurro-gsma-imei-urn.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-montemurro-gsma-imei-urn-16
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 10:55:47 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document:  draft-montemurro-gsma-imei-urn-16
Reviewer: Alexey Melnikov	
Review Date: 2013-08-08
IETF LC End Date: 2013-08-16

Summary: This draft is ready for publication as an Informational 
document (with nits).

Major issues:

-- None

Minor issues:

In 3.1:

Rules for Lexical Equivalence:
       Two GSMA IMEI URNs are equivalent if they have the same "imeival"
       value, and the same gsma-specifier-params values in the same
       sequential order, with the exception that the gsma-specifier-param
       "vers=0" is to be ignored for the purposes of comparison.  All of
       these comparisons are to be case-insensitive.

       Any identifier in GSMA namespaces can be compared using the normal
       mechanisms for percent-encoded UTF-8 strings.

UTF-8 reference (RFC 3629) is missing here.


A minor point:

10.2.  Informative references

    [8]   Crocker, D. and P. Overell, "Augmented BNF for Syntax
          Specifications: ABNF", STD 68, RFC 5234, January 2008.

This reference is Normative, because it is required to be understood in 
order to interpret ABNF syntax.


From cabo@tzi.org  Thu Aug  8 12:58:55 2013
Return-Path: <cabo@tzi.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 360C611E8225; Thu,  8 Aug 2013 12:58:55 -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=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9gCERiLa0Jry; Thu,  8 Aug 2013 12:58:49 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id CB6C411E822F; Thu,  8 Aug 2013 12:58:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r78JwJrM009599; Thu, 8 Aug 2013 21:58:19 +0200 (CEST)
Received: from [192.168.217.105] (p5489221B.dip0.t-ipconnect.de [84.137.34.27]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 86A8C152; Thu,  8 Aug 2013 21:58:18 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com>
Date: Thu, 8 Aug 2013 21:58:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: draft-bormann-cbor-04.all@tools.ietf.org, gen-art@ietf.org, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 08 Aug 2013 19:58:55 -0000

On Jul 30, 2013, at 09:05, Martin Thomson <martin.thomson@gmail.com> =
wrote:

> What would cause this to be tragic, is if publication of this were
> used to prevent other work in this area from subsequently being
> published.

Indeed.

As Paul and I have repeatedly said, CBOR is not trying to be the final, =
definitive, binary object representation for all purposes.  It was =
written to some specific objectives, clearly stated in the document.  It =
is being proposed for standards-track because specific ongoing work that =
works well with these objectives will benefit greatly from being able to =
reference a common specification.  If the objectives for other work are =
different, that work may benefit from using a different format, existing =
or newly designed.

We had some offline discussion of what can be done to make this more =
apparent from the document, and decided to start at the most visible =
part, the abstract.

In -04, the abstract says:

   The Concise Binary Object Representation (CBOR) is a data format
   whose design goals include the possibility of extremely small code
   size, fairly small message size, and extensibility without the need
   for version negotiation.  These design goals make it different from
   earlier binary serializations such as ASN.1 and MessagePack.

Now this seemed fairly clear to the authors, but without context it =
might be read as trying to be the final, end-all format because it only =
talks about earlier formats.
We propose to fix this (at the danger of being slightly tautological) by =
making it clear other formats will be created in the future:

   The Concise Binary Object Representation (CBOR) is a data format
   whose design goals include the possibility of extremely small code
   size, fairly small message size, and extensibility without the need
   for version negotiation.  These design goals make it different from
   earlier binary serializations such as ASN.1 and MessagePack, or other
   binary serializations that may be created in the future.

Serialization/encoding of data structures for transmission continues to =
be an exciting (if sometimes arcane) subject of computer science and its =
long history will not end with CBOR.

(CC to ietf@ietf.org because some discussion there appears to be =
related.)

Gr=FC=DFe, Carsten


From rjsparks@nostrum.com  Thu Aug  8 13:00:06 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 878E911E8229 for <gen-art@ietfa.amsl.com>; Thu,  8 Aug 2013 13:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.047, 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 lp4XC-HzFILz for <gen-art@ietfa.amsl.com>; Thu,  8 Aug 2013 13:00:05 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5D08F11E8205 for <gen-art@ietf.org>; Thu,  8 Aug 2013 13:00:05 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r78K03jv001730 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Thu, 8 Aug 2013 15:00:04 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <5203F8C2.3060807@nostrum.com>
Date: Thu, 08 Aug 2013 15:00:02 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, draft-ietf-websec-x-frame-options@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] Genart LC review: draft-ietf-websec-x-frame-options-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 20:00:06 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document: draft-ietf-websec-x-frame-options-07
Reviewer: Robert Sparks
Review Date: 2013-08-08
IETF LC End Date: 2013-08-12
IESG Telechat date: 2013-08-15

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

This document is intended to act as a informational reference describing 
what's already deployed, and not to act as a standard for new 
implementations to follow. It's obvious that some care has been taken to 
keep that tone in the text, but there are places where it still looks 
like a proposed standard. Please make it even more clear who the 
audience for this document is, and look for places to reinforce that 
this is documenting what _is_, as opposed to trying to influence what 
should be.

The introduction of this version of the document does a good job of 
describing what a clickjack attack is. Appendix B is not really adding 
to that description. I suggest that the two usecases it call out be 
reduced to a couple of sentences in the introduction as examples, and a 
reference to a more in-depth treatment of scenarios like them be added 
for those looking for more information. Section B.3 is different, and 
doesn't add to the understanding of this document. Again, I suggest 
pointing to somewhere else that provides an in-depth treatment. 
(Hopefully, that source would discuss the nested frame issue the 
security considerations section points out in the context of the this 
specific configuration page). [FRAME-BUSTING] might be enough, but 
pointers to something even more rich would certainly be helpful.

Here are some suggestions in document order:

In the Abstract, I suggest replace "specification" with either 
"definition" as the introduction uses, or with "the syntax and behavior 
observed in current deployments".

The last paragraph of the introduction reads like standards text. Please 
consider rewriting it with a tone of history and current fact. Perhaps 
starting with "In existing implementations, ", and replacing the last 
sentence with something like "The policy this HTTP header declares is 
enforced by the browser implementations documented here".

Since this is documenting an existing deployed header (not standardizing 
it), it would be useful to comment whether the existing known 
implementations allow all the productions of the ABNF described here to 
be used. For instance, would they all honor X-FRAME-OPTIONS: deny? 
(While thinking about this, focus on who this document is for.)

The last sentence of 2.3.1 as written is an attempt to be a standard, 
and is an odd use of 2119. I suggest rewriting it as a warning about 
what happens with existing plugins that ignore the policy carrid in the 
header. That keeps the message aligned with documenting what exists.

The first sentence of 2.3.2 is not adding anything to the document. I 
suggest deleting it. The second sentence is placing an implementation 
requirement again. Please consider rewriting as an observation of what 
existing things do, calling out the ramifications of the ones that 
behave differently.

Similarly, the first paragraphs of Section 2.3.2.1 is written to affect 
new implementation, not document existing implementation. They could be 
re-tuned as above. The third paragraph is good history

The last sentence of 2.3.2.2 should not say "replace this document" - 
this document is informational documentation about existing deployments. 
CSP1.1 won't Obsolete or Replace this document. Rather it should say 
something like "it is expected that newer implementations will use it 
rather than the mechanisms documented here".

Nit: s/does support only one/only supports one/

Do the known implementations follow the pattern described in 2.3.2.3? 
Saying something would help tie this to being information about the 
known deployment rather than trying to constrain new development.

Nit: If Appendix B is kept, please expand CSRF (and consider re-pointing 
to a reference)


From mahoney@nostrum.com  Thu Aug  8 14:48:17 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4183311E822C for <gen-art@ietfa.amsl.com>; Thu,  8 Aug 2013 14:48:17 -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 3HuSi9btXqkD for <gen-art@ietfa.amsl.com>; Thu,  8 Aug 2013 14:48:16 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 539DB11E812C for <gen-art@ietf.org>; Thu,  8 Aug 2013 14:48:14 -0700 (PDT)
Received: from nclt8dp0wl1.tekelec.com ([198.89.36.10]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r78LmCGI013648 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 8 Aug 2013 16:48:13 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <52041217.8050301@nostrum.com>
Date: Thu, 08 Aug 2013 16:48:07 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 198.89.36.10 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-08-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 21:48:17 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Dan Romascanu     2013-08-30   draft-kaplan-insipid-session-id-03

David Black       2013-08-16   draft-ietf-dime-overload-reqs-10

Elwyn Davies      2013-08-17   draft-ietf-homenet-arch-10

Francis Dupont    2013-08-19   draft-ietf-storm-ipsec-ips-update-03

Martin Thomson    2013-08-22   draft-ietf-storm-iscsi-sam-08 *

* Second Last Call


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

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


The standard template is included below.

Thanks,

Jean

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From mahoney@nostrum.com  Thu Aug  8 14:54:28 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B5E221F9967 for <gen-art@ietfa.amsl.com>; Thu,  8 Aug 2013 14:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id htnODQtnIWSq for <gen-art@ietfa.amsl.com>; Thu,  8 Aug 2013 14:54:27 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5EA6811E812C for <gen-art@ietf.org>; Thu,  8 Aug 2013 14:53:44 -0700 (PDT)
Received: from nclt8dp0wl1.tekelec.com ([198.89.36.10]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r78LrRx1014283 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 8 Aug 2013 16:53:27 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <52041351.9060803@nostrum.com>
Date: Thu, 08 Aug 2013 16:53:21 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 198.89.36.10 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2013-08-15 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, 08 Aug 2013 21:54:28 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft
------------------------------------------------------------------------------------
Alexey Melnikov        TR2013-07-03 draft-ietf-multimob-pmipv6-ropt-07 **

David Black            TR2013-04-29 draft-ietf-karp-crypto-key-table-08 *
David Black            TR2013-06-04 draft-eastlake-rfc5342bis-04 *
David Black            TR2013-07-18 
draft-ietf-trill-directory-framework-06 *

Francis Dupont         TR2013-05-27 draft-ietf-mpls-ldp-dod-09 *
Francis Dupont         TR2013-07-25 draft-ietf-emu-crypto-bind-04 **

Joel Halpern           TR2013-07-29 draft-ietf-weirds-using-http-07 **

Kathleen Moriarty      TR2013-07-29 draft-ietf-weirds-rdap-sec-04

Meral Shirazipour      TR2013-07-30 draft-ietf-emu-eap-tunnel-method-07 **

Martin Thomson         TR2013-08-13 draft-bormann-cbor-04 **

Peter McCann           TR2013-07-31 draft-ietf-mpls-retire-ach-tlv-03 *

Peter Yee              TR2013-07-17 
draft-jabley-dnsext-eui48-eui64-rrtypes-05 **

Roni Even              TR2013-07-23 draft-merkle-tls-brainpool-04 *

Russ Housley           TR2013-06-27 draft-ietf-manet-rfc6622-bis-04 *

Robert Sparks          TR2013-08-12 draft-ietf-websec-x-frame-options-07 **

Suresh Krishnan        TR2013-06-05 draft-ietf-lwig-terminology-05

Wassim Haddad          TR2013-07-31 draft-housley-ltans-oids-01
Wassim Haddad          TR2013-08-14 draft-ietf-manet-nhdp-olsrv2-sec-03 **

* Earlier draft reviewed
** Already reviewed


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

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

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

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

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From housley@vigilsec.com  Thu Aug  8 15:10:24 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DE9621E80B6; Thu,  8 Aug 2013 15:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.662
X-Spam-Level: 
X-Spam-Status: No, score=-102.662 tagged_above=-999 required=5 tests=[AWL=-0.063, 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 QTIdJQUntgfU; Thu,  8 Aug 2013 15:10:19 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 6B56F21E8095; Thu,  8 Aug 2013 15:09:46 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 21BC1F2408A; Thu,  8 Aug 2013 18:10:21 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id dQe-PJ+tLBiS; Thu,  8 Aug 2013 18:09:38 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-154-95.washdc.fios.verizon.net [96.241.154.95]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 98EE8F24089; Thu,  8 Aug 2013 18:10:19 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 8 Aug 2013 18:09:43 -0400
Message-Id: <3140092F-123B-4FD3-A7DF-A61C44C76262@vigilsec.com>
To: manet@ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IETF Gen-ART <gen-art@ietf.org>, IESG <iesg@ietf.org>
Subject: [Gen-art] Gen-ART Review of draft-ietf-manet-rfc6622-bis-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, 08 Aug 2013 22:10: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-manet-rfc6622-bis-04
Reviewer: Russ Housley
Review Date: 2013-06-15
IETF LC End Date: 2013-06-27
IESG Telechat date: 2013-08-15

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

I reviewed -02 during IETF Last Call, and all of my concerns have
been addressed in -04.

From david.black@emc.com  Fri Aug  9 08:12:38 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40D2C21F9F7F; Fri,  9 Aug 2013 08:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 BGXXwHK-WSKl; Fri,  9 Aug 2013 08:12:33 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0767221E8116; Fri,  9 Aug 2013 08:05:09 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r79EsEOd003669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Aug 2013 10:54:15 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Fri, 9 Aug 2013 10:53:57 -0400
Received: from mxhub36.corp.emc.com (mxhub36.corp.emc.com [10.254.93.84]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r79Err6x005981; Fri, 9 Aug 2013 10:53:55 -0400
Received: from mxhub37.corp.emc.com (128.222.70.104) by mxhub36.corp.emc.com (10.254.93.84) with Microsoft SMTP Server (TLS) id 8.3.297.1; Fri, 9 Aug 2013 10:53:54 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub37.corp.emc.com ([128.222.70.104]) with mapi; Fri, 9 Aug 2013 10:53:53 -0400
From: "Black, David" <david.black@emc.com>
To: "d3e3e3@gmail.com" <d3e3e3@gmail.com>, "joe.abley@icann.org" <joe.abley@icann.org>, General Area Review Team <gen-art@ietf.org>
Date: Fri, 9 Aug 2013 10:53:52 -0400
Thread-Topic: Gen-ART review of draft-eastlake-rfc5342bis-04
Thread-Index: Ac6VEEKdA2xd69LGR46X1qbivgZDPw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C2B7446@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "joelja@bogus.com" <joelja@bogus.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-eastlake-rfc5342bis-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, 09 Aug 2013 15:12:38 -0000

The -04 version of this draft resolves the typo/thinko that snuck into
the -03 version, and fixed a number of related instances of that problem
that I missed in that review.

The -04 version of this draft is ready for publication as a BCP RFC.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Sunday, June 09, 2013 1:47 PM
> To: d3e3e3@gmail.com; joe.abley@icann.org; General Area Review Team
> Cc: joelja@bogus.com; ietf@ietf.org; Black, David
> Subject: Gen-ART review of draft-eastlake-rfc5342bis-03
>=20
> The -03 version of this draft resolves all of the concerns raised by
> the Gen-ART review of the -02 version.
>=20
> Unfortunately, a serious typo/thinko snuck into the -03 version (been
> there, done that, myself).  Section 3.2 currently says:
>=20
>    00-42 is a protocol number under the IANA OUI (that is,
>    00-00-0E-00-42) to be used for documentation purposes.
>=20
> The parenthetical expansion of the protocol number is incorrect.
> The correct expansion uses -5E- instead of -0E-:
>=20
>    00-42 is a protocol number under the IANA OUI (that is,
>    00-00-5E-00-42) to be used for documentation purposes.
>=20
> I strongly suggest submitting a -04 version of this draft to make
> the necessary single character correction (e.g., as opposed to using
> a RFC Editor Note for that purpose).
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Wednesday, June 05, 2013 6:13 PM
> > To: d3e3e3@gmail.com; joe.abley@icann.org; General Area Review Team
> > Cc: Black, David; joelja@bogus.com; ietf@ietf.org
> > Subject: Gen-ART review of draft-eastlake-rfc5342bis-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>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-eastlake-rfc5342bis-02
> > Reviewer: David L. Black
> > Review Date: June 5, 2013
> > IETF LC End Date: June 4, 2013
> >
> > Summary:
> > This draft is on the right track but has open issues, described in the
> review.
> >
> > This draft updates the IANA registered Ethernet parameters for IETF use=
,
> > including recording values assigned for documentation.  It also makes s=
ome
> > minor changes to IANA procedures.
> >
> > IANA should review this entire draft, not just its IANA Considerations
> > section;
> > Pearl Liang appears to have done that comprehensive review for IANA.
> >
> > Major issues: None
> >
> > Minor issues: One, the IANA review also found this issue.
> >
> > Section 3.2 states:
> >
> > 	IANA will assign "00-00-0E-00-42" as the protocol number under the
> > 	IANA OUI to be used for documentation purposes.
> >
> > IANA has not made this assignment, but this assignment request is not
> > recorded in the IANA Considerations section where IANA actions are
> > requested and recorded by IANA after they have been performed.  This
> > assignment needs to be added to the IANA Considerations section;
> > see item 5 in the IANA review.
> >
> > Nits/editorial comments:
> >
> > Section 1: This document uses an "IESG Ratification" process for some
> > assignments.  This is not the same process as the "IESG Approval" proce=
ss
> > defined in RFC 5226.  As those names could be confused by a casual read=
er
> > who is not strongly familiar with IANA processes, I suggest adding a
> > statement that the "IESG Ratification" process is defined in this docum=
ent
> > and is not the same as the "IESG Approval" process in RFC 5226.  This c=
ould
> > be added after the sentence that cites RFC 5226.
> >
> > Section 1.4: It would be helpful to point out that there is no OUI assi=
gned
> > for documentation purposes, but there are identifiers based on the IANA=
 OUI
> > that have been assigned for documentation purposes.
> >
> > In general, the use of the acronym IAB for Individual Address Block is
> > unfortunate, but unavoidable, and this is clearly pointed out in the
> > definition of the IAB acronym in section 1.2.  Nothing can or should be
> > done about this.
> >
> > idnits 2.12.17 did not find any nits.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From david.black@emc.com  Fri Aug  9 08:19:36 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A0BC11E8196; Fri,  9 Aug 2013 08:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, 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 rxH3MI7Ew7wF; Fri,  9 Aug 2013 08:19:28 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 86E9021F9EFC; Fri,  9 Aug 2013 08:11:18 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r79ElVGn030222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Aug 2013 10:47:31 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 9 Aug 2013 10:47:07 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r79El6Ae021361; Fri, 9 Aug 2013 10:47:06 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Fri, 9 Aug 2013 10:47:05 -0400
From: "Black, David" <david.black@emc.com>
To: "housley@vigilsec.com" <housley@vigilsec.com>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "Sam Hartman (hartmans@painless-security.com)" <hartmans@painless-security.com>, "Dacheng Zhang (zhangdacheng@huawei.com)" <zhangdacheng@huawei.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Fri, 9 Aug 2013 10:47:05 -0400
Thread-Topic: Gen-ART review of draft-ietf-karp-crypto-key-table-08
Thread-Index: Ac6VD0rmlAaf+56PTd+LLDqqvEOcAQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "karp@ietf.org" <karp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 15:19: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-karp-crypto-key-table-08
Reviewer: David L. Black
Review Date: August 9, 2013
IETF LC End Date: April 29, 2013
IETF Telechat Date: August 15, 2013

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

This draft describes a conceptual key database for use by protocols.
It's definitely useful and valuable work, as key management is often
an afterthought in protocol design, even when security functionality
is actively worked on in the design process.  The draft text is in
good shape and reads cleanly.

The draft authors have addressed most of the issues and concerns from
the GenART review of the -07 version of this draft, but three issues
remain.  I am particularly concerned with the first issue about whether
FCFS is appropriate for these security-related registries, and believe
that topic deserves IESG discussion.  The three issues are ([9], [A] and
[C] are the issue identifiers used on the original Gen-ART review of the
-07 version of this draft):

Major issue:

[9] I suggest Expert Review for the new IANA registries, not just=20
First Come First Served, so that someone with a security "clue" can
check that the proposed registrations are reasonable.

Minor issues:

[A] Overall - I would like to see a paragraph added on how this database
conceptually relates to the IPsec Peer Authorization Database (PAD) -
see RFC 4301, section 4.4.3.

[C] (Section 3) Where does key selection occur?  I would suggest that
the database return all possible keys and let the protocol figure out
what to use.  This is particularly important for inbound traffic for
obvious reasons.

Nits/editorial comments:

First paragraph in 8.1.2 should be at end of 8.1.1.

idnits 2.12.17 found two nits - the latter one (2119 reference/boilerplate)
needs attention:

  ** There are 2 instances of too long lines in the document, the longest o=
ne
     being 6 characters in excess of 72.

  ** The document seems to lack a both a reference to RFC 2119 and the
     recommended RFC 2119 boilerplate, even if it appears to use RFC 2119
     keywords.=20

     RFC 2119 keyword, line 194: '...tion of key material.  The KDF MAY use=
...'
     RFC 2119 keyword, line 196: '... or received but MUST NOT depend on ot=
...'

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 martin.thomson@gmail.com  Fri Aug  9 12:22:20 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3330F21F9C6F; Fri,  9 Aug 2013 12:22:20 -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.119,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50+FLKPGeH8K; Fri,  9 Aug 2013 12:22:18 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0905121F9CA4; Fri,  9 Aug 2013 12:15:59 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id hq12so54075wib.8 for <multiple recipients>; Fri, 09 Aug 2013 12:15:59 -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=P80X2GWxj+KN8MQRcIAotFWswVu1xzQmFUH0eR05jqg=; b=pRdcidlps6o6xqI500MMoX7u1d5nnpQSvgxqWo98PED0/IBEjjC2+tgsJvXaERH5tD p83zrtM58bNtvF+O7iw9bwqVOpcjNu2z8syowuaWdSDR3/Dg0RsTNZIlMwFqS86Ieiss ORUHTufnUh7SEFLZzu0eaBr3u4aeXsezcPUYUC703ZjbQshZvReNYT/qiFPM2p6zytkZ aE63qcY72Nka3BTAy26hBZLIdPzAR7wdEWNPb9YapDr33zMt0szQb0eyC97QjW/3DBYu y6OzIXaRUEG48G2FNb8qG5ts5nYM2Y9k5ioZTzC+u1mZ7a+4OoO4iCPfNbKr5fBuMwII lNYw==
MIME-Version: 1.0
X-Received: by 10.194.78.110 with SMTP id a14mr1234019wjx.84.1376075759165; Fri, 09 Aug 2013 12:15:59 -0700 (PDT)
Received: by 10.194.28.39 with HTTP; Fri, 9 Aug 2013 12:15:59 -0700 (PDT)
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com> <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com>
Date: Fri, 9 Aug 2013 20:15:59 +0100
Message-ID: <CABkgnnW2un9Dn+2rkdq=QSZPE9WYE-Rap=_HfwTj_CaahG=D=Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Content-Type: text/plain; charset=UTF-8
Cc: "draft-bormann-cbor-04.all@tools.ietf.org" <draft-bormann-cbor-04.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 09 Aug 2013 19:22:20 -0000

On 5 August 2013 18:43, Joe Hildebrand (jhildebr) <jhildebr@cisco.com> wrote:
> Sorry, my response is also correspondingly long.

I'll be brief.  Though Joe missed my point on several of his rebuttals
(which I found to be an odd thing to do anyway), I see no reason to
quibble.  I think that the bulk of the comments are valid, though I
might disagree on several.

From hallam@gmail.com  Fri Aug  9 13:30:06 2013
Return-Path: <hallam@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 919FF21F9DAA; Fri,  9 Aug 2013 13:30:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level: 
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ufrSwvlQUNL9; Fri,  9 Aug 2013 13:30:05 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 786DE21F9D04; Fri,  9 Aug 2013 13:23:50 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id k13so3834728wgh.13 for <multiple recipients>; Fri, 09 Aug 2013 13:23:49 -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=lZt2kAum6Lhz6sJP+VZLDs6zCLH27vodXKdpafMc3sU=; b=sqO/Ixbmju/+Hxj0FXBksN9R6Qf5OQ6KIMDnBX4/qBsQIB+ObcHV1RRkPq6EVFLWOe pMZU66RIRcwndpVE8etl0hv89CSQWvyPBUbVeTVVb4m4tnhg+MsJH2+Z9LUKuJIxWhQ8 juNsKOZykykvHAIqNvuwxuZtHkMA4LvtyrAS2aWJfzq6s6EIkWNe2eUfZXGNfzaobj7H nMAQ/dRmShIyEiag7c1I7p+rAUOallznftvpKks27BRtZStQ+lylGWF2zGabmi+FIzIF MAWf5MuFGb+rOrHJN5qK/tly9yf7Rw/r1YuQSZeDm85vGbxq624TrOyUii+wNZx47/3v dvqw==
MIME-Version: 1.0
X-Received: by 10.180.95.133 with SMTP id dk5mr1181291wib.33.1376079829481; Fri, 09 Aug 2013 13:23:49 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Fri, 9 Aug 2013 13:23:49 -0700 (PDT)
In-Reply-To: <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com> <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org>
Date: Fri, 9 Aug 2013 16:23:49 -0400
Message-ID: <CAMm+LwgmEYXMroiTjbS8aZg3uihm5bQmTdK-bmV5Fx2t7u4jXg@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=f46d0444e87f6b418c04e3898da9
Cc: draft-bormann-cbor-04.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 09 Aug 2013 20:30:06 -0000

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

On Thu, Aug 8, 2013 at 3:58 PM, Carsten Bormann <cabo@tzi.org> wrote:

> On Jul 30, 2013, at 09:05, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>
> > What would cause this to be tragic, is if publication of this were
> > used to prevent other work in this area from subsequently being
> > published.
>
> Indeed.
>
> As Paul and I have repeatedly said, CBOR is not trying to be the final,
> definitive, binary object representation for all purposes.  It was written
> to some specific objectives, clearly stated in the document.  It is being
> proposed for standards-track because specific ongoing work that works well
> with these objectives will benefit greatly from being able to reference a
> common specification.  If the objectives for other work are different, that
> work may benefit from using a different format, existing or newly designed.
>

I do not expect you to succeed in being the final definitive format.

But if you are not prepared to try then I don't want the result.


You keep talking about your design requirements, but where are the use
cases that drive them? When I am discussing a specification I am always
referring to illustrative use cases that motivate the requirements. When
you are discussing your spec you wave away every objection by saying it
isn't a design requirement but I have never seen you give the rationale.

Coming back to Martin's comments about the type system. I think that is
what JSON does so well. It has exactly as much type system as is useful and
no more. The developers realized that there was no need to distinguish
lists and sets because both are going to serialize as lists on the wire.


-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Aug 8, 2013 at 3:58 PM, Carsten Bormann <span dir=3D"ltr">&=
lt;<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Jul 30, 2013, at 09:05,=
 Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.thom=
son@gmail.com</a>&gt; wrote:<br>

<br>
&gt; What would cause this to be tragic, is if publication of this were<br>
&gt; used to prevent other work in this area from subsequently being<br>
&gt; published.<br>
<br>
</div>Indeed.<br>
<br>
As Paul and I have repeatedly said, CBOR is not trying to be the final, def=
initive, binary object representation for all purposes. =A0It was written t=
o some specific objectives, clearly stated in the document. =A0It is being =
proposed for standards-track because specific ongoing work that works well =
with these objectives will benefit greatly from being able to reference a c=
ommon specification. =A0If the objectives for other work are different, tha=
t work may benefit from using a different format, existing or newly designe=
d.<br>
</blockquote><div><br></div><div>I do not expect you to succeed in being th=
e final definitive format.</div><div><br></div><div>But if you are not prep=
ared to try then I don&#39;t want the result.</div><div><br></div><div>
<br></div><div>You keep talking about your design requirements, but where a=
re the use cases that drive them? When I am discussing a specification I am=
 always referring to illustrative use cases that motivate the requirements.=
 When you are discussing your spec you wave away every objection by saying =
it isn&#39;t a design requirement but I have never seen you give the ration=
ale.</div>
<div><br></div><div>Coming back to Martin&#39;s comments about the type sys=
tem. I think that is what JSON does so well. It has exactly as much type sy=
stem as is useful and no more. The developers realized that there was no ne=
ed to distinguish lists and sets because both are going to serialize as lis=
ts on the wire.=A0</div>
<div>=A0<br></div></div><div><br></div>-- <br>Website: <a href=3D"http://ha=
llambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--f46d0444e87f6b418c04e3898da9--

From kathleen.moriarty@emc.com  Fri Aug  9 14:02:16 2013
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 04D5821F9CF8; Fri,  9 Aug 2013 14:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.251
X-Spam-Level: 
X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[AWL=0.348,  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 GZLDA6ZxOgPA; Fri,  9 Aug 2013 14:02:10 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2742C1F0CB2; Fri,  9 Aug 2013 13:55:24 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r79Kruke022864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Aug 2013 16:54:01 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 9 Aug 2013 16:53:41 -0400
Received: from mxhub30.corp.emc.com (mxhub30.corp.emc.com [128.222.70.170]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r79KreAw020164; Fri, 9 Aug 2013 16:53:40 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub30.corp.emc.com ([128.222.70.170]) with mapi; Fri, 9 Aug 2013 16:53:39 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-weirds-rdap-sec.all@tools.ietf.org" <draft-ietf-weirds-rdap-sec.all@tools.ietf.org>
Date: Fri, 9 Aug 2013 16:53:24 -0400
Thread-Topic: Gen-art review of draft-ietf-weirds-rdap-sec-04
Thread-Index: AQHOlUKGo9O1fzm1QESFUp6H8053SA==
Message-ID: <F5063677821E3B4F81ACFB7905573F24E36595B7@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "nkong@cnnic.cn" <nkong@cnnic.cn>, "shollenbeck@verisign.com" <shollenbeck@verisign.com>
Subject: [Gen-art] Gen-art review of draft-ietf-weirds-rdap-sec-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, 09 Aug 2013 21:02:16 -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-weirds-rdap-sec-04
Reviewer: Kathleen Moriarty
Review Date: 8/9/13
IETF LC End Date:=20
IESG Telechat date: (if known)

Summary:  The draft is well written and is ready for publication.  There ma=
y be a downref and there will be references to adjust in Auth48, but otherw=
ise is ready.

Major issues:

Minor issues:

Nits/editorial comments:  Please check the idnits, there may be a down ref:=
=20
-- Possible downref: Non-RFC (?) normative reference: ref. 'OpenID'

  ** Downref: Normative reference to an Informational RFC: RFC 2818=

From jsalowey@cisco.com  Fri Aug  9 16:00:32 2013
Return-Path: <jsalowey@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 7AF7421F9BA2 for <gen-art@ietfa.amsl.com>; Fri,  9 Aug 2013 16:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.498
X-Spam-Level: 
X-Spam-Status: No, score=-110.498 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ex6tremlkljc for <gen-art@ietfa.amsl.com>; Fri,  9 Aug 2013 16:00:27 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id BB94311E80E9 for <gen-art@ietf.org>; Fri,  9 Aug 2013 15:54:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12479; q=dns/txt; s=iport; t=1376088883; x=1377298483; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=a2AXD0/rFzLumZk2qeWJ/oJfrjIbGSTQ/xvbu5qtdKE=; b=k+8FfaVgM8he4Jgb11Uzofs+cxr8K7YYPsm1HOSJuCLE8Ww5ngRi9fJB ZFKaS2Z1MEWPQaRVxh6IghTrhBg4PHtPvzPYtvp4rhu1kbe0kwMa0Pn2K 54gqPq+yBdDWrmDnuhZPG4QJtBMHdIPG4X5v68Jae9D2XgsqDHwrmu5xu o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhMFAK5xBVKtJXHB/2dsb2JhbABbgkJENVC2HYg9gRwWdIIlAQEEJyIwEAIBCAcNDh0HMhQRAQEEDgUIiAgMuFeQASARBwmDEXUDmQyQJYMbgio
X-IronPort-AV: E=Sophos;i="4.89,849,1367971200";  d="scan'208,217";a="245736708"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-4.cisco.com with ESMTP; 09 Aug 2013 22:54:43 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r79MsgNp004952 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 9 Aug 2013 22:54:43 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.235]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Fri, 9 Aug 2013 17:54:42 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
Thread-Topic: Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-method-07
Thread-Index: Ac6NbJMxWaq0WGIaSDy4raLO8rZmygIEMVmA
Date: Fri, 9 Aug 2013 22:54:42 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628DB480F@xmb-rcd-x09.cisco.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A5D6541@eusaamb107.ericsson.se>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A5D6541@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.248.54]
Content-Type: multipart/alternative; boundary="_000_A95B4818FD85874D8F16607F1AC7C628DB480Fxmbrcdx09ciscocom_"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org" <draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-method-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 23:00:32 -0000

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

Hi Meral,

Thanks for your review, comments inline below.

Cheers,

Joe
On Jul 30, 2013, at 2:47 PM, Meral Shirazipour <meral.shirazipour@ericsson.=
com<mailto:meral.shirazipour@ericsson.com>> wrote:

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

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

Document: draft-ietf-emu-eap-tunnel-method-07
Reviewer: Meral Shirazipour
Review Date: 2013-07-30
IETF LC End Date: 2013-07-30
IESG Telechat date: NA


Summary:
This draft is almost ready to be published as Standards Track RFC but I hav=
e some comments.


Nits/editorial comments:
Many sections of the document are a direct copy paste of RFC4851(EAP-FAST) =
with a minor change: "EAP-FAST"->"TEAP".
Since RFC4851 is mentioned as being well adopted, is there a reason why it =
has not been used as reference point and then only mention the diffs in mor=
e detail? (for the sections concerned).
Appendix B is useful, but the above suggestion could have made the document=
 a lot shorter and easier to understand by people already familiar with EAP=
-FAST.
Unless this draft is to replace RFC4851? In which case the abstract should =
mention this.
e.g.
[Page 20], Section 3.7 Fragmentation, is a copy of RFC4851's Section 3.7 wi=
th "EAP-FAST"->"TEAP".
Why not use RFC4851's Fragmentation proposal as a reference point and just =
mention what is different (e.g. nothing but the EAP-Type in this case).



[Joe] RFC 4851 is informational and making normative reference to it would =
be a downref.  We felt it would be better to include the complete text in t=
he standards track document and remove any normative dependency on the info=
rmation document.


Nits:
[Page 6], Section 1.2, reference [RFC5077] appears twice.
[Page 21], section 3.8, paragraph 2, "which the the peer"--typo-->remove ex=
tra "the"
[Page 24], Section 3.8.4, paragraph 2, "succ;essfully"--typo-->"successfull=
y"
[Page 56], line 3, "Note: Peer's are"---->"Peers"
[Page 73], Section 7.6, "is remoted"--typo-->"is remote"


[Joe] OK



Best Regards,
Meral
---
Meral Shirazipour
Ericsson
Research
www.ericsson.com<http://www.ericsson.com/>


--_000_A95B4818FD85874D8F16607F1AC7C628DB480Fxmbrcdx09ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <8B42F474507D944DB2C2707A426EA885@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Hi Meral,
<div><br>
</div>
<div>Thanks for your review, comments inline below. &nbsp;</div>
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<div>Joe<br>
<div>
<div>On Jul 30, 2013, at 2:47 PM, Meral Shirazipour &lt;<a href=3D"mailto:m=
eral.shirazipour@ericsson.com">meral.shirazipour@ericsson.com</a>&gt; wrote=
:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"font-family: He=
lvetica; font-size: medium; font-style: normal; font-variant: normal; font-=
weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; te=
xt-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space=
: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -we=
bkit-text-stroke-width: 0px; ">
<div class=3D"WordSection1" style=3D"page: WordSection1; ">
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at<a href=3D"http://wiki.tools.ietf.org/area/gen/trac=
/wiki/GenArtfaq" style=3D"color: purple; text-decoration: underline; ">http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a><span class=3D"Apple=
-converted-space">&nbsp;</span>&nbsp;.<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Please resolve these comments along with any other Last Call comments you m=
ay receive.<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Document: draft-ietf-emu-eap-tunnel-method-07<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Reviewer: Meral Shirazipour<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Review Date: 2013-07-30<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
IETF LC End Date: 2013-07-30<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
IESG Telechat date: NA<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Summary:<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
This draft is almost ready to be published as Standards Track RFC but I hav=
e some comments.<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Nits/editorial comments:<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Many sections of the document are a direct copy paste of RFC4851(EAP-FAST) =
with a minor change: &quot;EAP-FAST&quot;-&gt;&quot;TEAP&quot;.<o:p></o:p><=
/div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Since RFC4851 is mentioned as being well adopted, is there a reason why it =
has not been used as reference point and then only mention the diffs in mor=
e detail? (for the sections concerned).<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Appendix B is useful, but the above suggestion could have made the document=
 a lot shorter and easier to understand by people already familiar with EAP=
-FAST.<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Unless this draft is to replace RFC4851? In which case the abstract should =
mention this.<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
e.g.<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
[Page 20], Section 3.7 Fragmentation, is a copy of RFC4851's Section 3.7 wi=
th &quot;EAP-FAST&quot;-&gt;&quot;TEAP&quot;.<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Why not use RFC4851's Fragmentation proposal as a reference point and just =
mention what is different (e.g. nothing but the EAP-Type in this case).<o:p=
></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>[Joe] RFC 4851 is informational and making normative reference to it w=
ould be a downref. &nbsp;We felt it would be better to include the complete=
 text in the standards track document and remove any normative dependency o=
n the information document. &nbsp;</div>
<div><br>
</div>
<br>
<blockquote type=3D"cite">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"font-family: He=
lvetica; font-size: medium; font-style: normal; font-variant: normal; font-=
weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; te=
xt-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space=
: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -we=
bkit-text-stroke-width: 0px; ">
<div class=3D"WordSection1" style=3D"page: WordSection1; ">
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Nits:<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
[Page 6], Section 1.2, reference [RFC5077] appears twice.<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
[Page 21], section 3.8, paragraph 2, &quot;which the the peer&quot;--typo--=
&gt;remove extra &quot;the&quot;<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
[Page 24], Section 3.8.4, paragraph 2, &quot;succ;essfully&quot;--typo--&gt=
;&quot;successfully&quot;<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
[Page 56], line 3, &quot;Note: Peer's are&quot;----&gt;&quot;Peers&quot;<o:=
p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
[Page 73], Section 7.6, &quot;is remoted&quot;--typo--&gt;&quot;is remote&q=
uot;<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>[Joe] OK</div>
<div><br>
</div>
<br>
<blockquote type=3D"cite">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"font-family: He=
lvetica; font-size: medium; font-style: normal; font-variant: normal; font-=
weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; te=
xt-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space=
: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -we=
bkit-text-stroke-width: 0px; ">
<div class=3D"WordSection1" style=3D"page: WordSection1; ">
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Best Regards,<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Meral<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
---<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Meral Shirazipour<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Ericsson<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
Research<o:p></o:p></div>
<div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; ">
<a href=3D"http://www.ericsson.com/" style=3D"color: purple; text-decoratio=
n: underline; ">www.ericsson.com</a><o:p></o:p></div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_A95B4818FD85874D8F16607F1AC7C628DB480Fxmbrcdx09ciscocom_--

From meral.shirazipour@ericsson.com  Fri Aug  9 16:28:24 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BF8B21F98AD for <gen-art@ietfa.amsl.com>; Fri,  9 Aug 2013 16:28:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C8Pr-xgchgMB for <gen-art@ietfa.amsl.com>; Fri,  9 Aug 2013 16:28:18 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 8510C21F9B8D for <gen-art@ietf.org>; Fri,  9 Aug 2013 16:24:00 -0700 (PDT)
X-AuditID: c6180641-b7f986d000007a82-f1-52057a0d58eb
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 24.6B.31362.D0A75025; Sat, 10 Aug 2013 01:23:58 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0328.009; Fri, 9 Aug 2013 19:23:54 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
Thread-Topic: Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-method-07
Thread-Index: Ac6NbJMxWaq0WGIaSDy4raLO8rZmygIEMVmAAAmhttA=
Date: Fri, 9 Aug 2013 23:23:53 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A5E687C@eusaamb107.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A5D6541@eusaamb107.ericsson.se> <A95B4818FD85874D8F16607F1AC7C628DB480F@xmb-rcd-x09.cisco.com>
In-Reply-To: <A95B4818FD85874D8F16607F1AC7C628DB480F@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A5E687Ceusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyuXRPgi5fFWuQweJGUYveLctYLa6++sxi 0XV0LbsDs8eU3xtZPZYs+cnk8eXyZ7YA5igum5TUnMyy1CJ9uwSujFMnfrIXvG5irFj8bzlj A+Odki5GDg4JAROJx89yuhg5gUwxiQv31rN1MXJxCAkcZZSYce8xK0hCSGAZo8SD5ZYgNpuA hcT238/B4iJAvZPfr2QGaWAWmMUo8WLDTrCEsICPxI7fnVBFvhKTlt1gBlkmImAlsfJlNUiY RUBFYsezXewgNq+At8Sy939YIBb3MEqcmXCcCaSeEygxabcWSA0j0HHfT61hArGZBcQlbj2Z zwRxtIDEkj3nmSFsUYmXj/+xQtjKEkue7GeBqM+X+Nnxmglil6DEyZlPWCYwis5CMmoWkrJZ SMog4joSC3Z/YoOwtSWWLXzNDGOfOfCYCVl8ASP7KkaO0uLUstx0I8NNjMBIOybB5riDccEn y0OM0hwsSuK8G/TOBAoJpCeWpGanphakFsUXleakFh9iZOLglGpgXNUhnMTW8/bgT43rq755 5lg6xvJdVeVv+ma4/uDOrUdCprA+0zO9X791//VzYU90//JodmWu9J2h6fth2qVNiy6s+197 +sz+9itqGseCE5+yOTeaMtiuZ3az2JnIZvU6luHf7LgffnuPzef+9aS/omZeR1a+otKlDQe4 e1vnbE0X2vyzmlF6lxJLcUaioRZzUXEiAFgncESCAgAA
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org" <draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-method-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 23:28:24 -0000

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

Hi Joe,
   Thank you for the answer. Fine with me, if the document shepherd or AD a=
pprove, I would still suggest adding a comment in the abstract or intro men=
tioning that RFC4851 text is reused.

Best,
Meral

From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com]
Sent: Friday, August 09, 2013 15:55
To: Meral Shirazipour
Cc: draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org; gen-art@ietf.org
Subject: Re: Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-method-0=
7

Hi Meral,

Thanks for your review, comments inline below.

Cheers,

Joe
On Jul 30, 2013, at 2:47 PM, Meral Shirazipour <meral.shirazipour@ericsson.=
com<mailto:meral.shirazipour@ericsson.com>> wrote:


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

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

Document: draft-ietf-emu-eap-tunnel-method-07
Reviewer: Meral Shirazipour
Review Date: 2013-07-30
IETF LC End Date: 2013-07-30
IESG Telechat date: NA


Summary:
This draft is almost ready to be published as Standards Track RFC but I hav=
e some comments.


Nits/editorial comments:
Many sections of the document are a direct copy paste of RFC4851(EAP-FAST) =
with a minor change: "EAP-FAST"->"TEAP".
Since RFC4851 is mentioned as being well adopted, is there a reason why it =
has not been used as reference point and then only mention the diffs in mor=
e detail? (for the sections concerned).
Appendix B is useful, but the above suggestion could have made the document=
 a lot shorter and easier to understand by people already familiar with EAP=
-FAST.
Unless this draft is to replace RFC4851? In which case the abstract should =
mention this.
e.g.
[Page 20], Section 3.7 Fragmentation, is a copy of RFC4851's Section 3.7 wi=
th "EAP-FAST"->"TEAP".
Why not use RFC4851's Fragmentation proposal as a reference point and just =
mention what is different (e.g. nothing but the EAP-Type in this case).



[Joe] RFC 4851 is informational and making normative reference to it would =
be a downref.  We felt it would be better to include the complete text in t=
he standards track document and remove any normative dependency on the info=
rmation document.



Nits:
[Page 6], Section 1.2, reference [RFC5077] appears twice.
[Page 21], section 3.8, paragraph 2, "which the the peer"--typo-->remove ex=
tra "the"
[Page 24], Section 3.8.4, paragraph 2, "succ;essfully"--typo-->"successfull=
y"
[Page 56], line 3, "Note: Peer's are"---->"Peers"
[Page 73], Section 7.6, "is remoted"--typo-->"is remote"


[Joe] OK




Best Regards,
Meral
---
Meral Shirazipour
Ericsson
Research
www.ericsson.com<http://www.ericsson.com/>


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.EmailStyle18
	{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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Joe,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; Thank you fo=
r the answer. Fine with me, if the document shepherd or AD approve, I would=
 still suggest adding a comment in the abstract or intro mentioning
 that RFC4851 text is reused.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best,<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Meral
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><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=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Joseph S=
alowey (jsalowey) [mailto:jsalowey@cisco.com]
<br>
<b>Sent:</b> Friday, August 09, 2013 15:55<br>
<b>To:</b> Meral Shirazipour<br>
<b>Cc:</b> draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org; gen-art@iet=
f.org<br>
<b>Subject:</b> Re: Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-m=
ethod-07<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi Meral, <o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks for your review, comments inline below. &nbsp=
;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Cheers,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Joe<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On Jul 30, 2013, at 2:47 PM, Meral Shirazipour &lt;<=
a href=3D"mailto:meral.shirazipour@ericsson.com">meral.shirazipour@ericsson=
.com</a>&gt; wrote:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">I am the assigned Gen-ART reviewer for =
this draft. For background on Gen-ART, please see the FAQ at<a href=3D"http=
://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"><span style=3D"color:p=
urple">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</span></a><s=
pan class=3D"apple-converted-space">&nbsp;</span>&nbsp;.<o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Please resolve these comments along wit=
h any other Last Call comments you may receive.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Document: draft-ietf-emu-eap-tunnel-met=
hod-07<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Reviewer: Meral Shirazipour<o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Review Date: 2013-07-30<o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">IETF LC End Date: 2013-07-30<o:p></o:p>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">IESG Telechat date: NA<o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Summary:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">This draft is almost ready to be publis=
hed as Standards Track RFC but I have some comments.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Nits/editorial comments:<o:p></o:p></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Many sections of the document are a dir=
ect copy paste of RFC4851(EAP-FAST) with a minor change: &quot;EAP-FAST&quo=
t;-&gt;&quot;TEAP&quot;.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Since RFC4851 is mentioned as being wel=
l adopted, is there a reason why it has not been used as reference point an=
d then only mention the diffs in more detail? (for the sections
 concerned).<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Appendix B is useful, but the above sug=
gestion could have made the document a lot shorter and easier to understand=
 by people already familiar with EAP-FAST.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Unless this draft is to replace RFC4851=
? In which case the abstract should mention this.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">e.g.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[Page 20], Section 3.7 Fragmentation, i=
s a copy of RFC4851's Section 3.7 with &quot;EAP-FAST&quot;-&gt;&quot;TEAP&=
quot;.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Why not use RFC4851's Fragmentation pro=
posal as a reference point and just mention what is different (e.g. nothing=
 but the EAP-Type in this case).<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">[Joe] RFC 4851 is informational and making normative=
 reference to it would be a downref. &nbsp;We felt it would be better to in=
clude the complete text in the standards track document and remove any norm=
ative dependency on the information document.
 &nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Nits:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[Page 6], Section 1.2, reference [RFC50=
77] appears twice.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[Page 21], section 3.8, paragraph 2, &q=
uot;which the the peer&quot;--typo--&gt;remove extra &quot;the&quot;<o:p></=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[Page 24], Section 3.8.4, paragraph 2, =
&quot;succ;essfully&quot;--typo--&gt;&quot;successfully&quot;<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[Page 56], line 3, &quot;Note: Peer's a=
re&quot;----&gt;&quot;Peers&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[Page 73], Section 7.6, &quot;is remote=
d&quot;--typo--&gt;&quot;is remote&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">[Joe] OK<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Best Regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Meral<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">---<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Meral Shirazipour<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Ericsson<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Research<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><a href=3D"http://www.ericsson.com/"><s=
pan style=3D"color:purple">www.ericsson.com</span></a><o:p></o:p></span></p=
>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A5E687Ceusaamb107ericsso_--

From peter@akayla.com  Sat Aug 10 21:57:00 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D207811E80D7; Sat, 10 Aug 2013 21:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0mIgiuRhOm+I; Sat, 10 Aug 2013 21:56:52 -0700 (PDT)
Received: from p3plsmtpa07-10.prod.phx3.secureserver.net (p3plsmtpa07-10.prod.phx3.secureserver.net [173.201.192.239]) by ietfa.amsl.com (Postfix) with ESMTP id 5EE5D21F9A71; Sat, 10 Aug 2013 21:52:25 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa07-10.prod.phx3.secureserver.net with  id BGsN1m00A1huGat01GsNgf; Sat, 10 Aug 2013 21:52:24 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-jabley-dnsext-eui48-eui64-rrtypes.all@tools.ietf.org>
Date: Sat, 10 Aug 2013 21:52:55 -0700
Message-ID: <08c101ce964e$a618c620$f24a5260$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6WTjVLeQ4X/0nrTsSskAoejQ+VSw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART Telechat review of draft-jabley-dnsext-eui48-eui64-rrtypes-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Aug 2013 04:57:01 -0000

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

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

Document: draft-jabley-dnsext-eui48-eui64-rrtypes-05
Reviewer: Peter Yee
Review Date: July-07-2013
IETF LC End Date: July-17-2013
IESG Telechat date: August-15-2013

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

This review is the same as the IETF LC review of this draft, which remain
unchanged for the telechat.  This draft defines DNS Resources Record Types
for encoding IEEE 802 EUI-48 and EUI-64 addresses.  Potential privacy issues
with this scheme have been soundly beaten to death with extreme prejudice.

Major issues:

Minor issues:

Nits:

Page 1, Abstract, 1st paragraph: After "e.g.", append a comma and delete an
extraneous space before "Ethernet".

Page 3, Introduction, 1st paragraph, 2nd sentence: change "This" to "These"
and change "specification defines" to "specifications define". 

Page 3, Introduction, 2nd paragraph: append a comma after "e.g.".

		-Peter Yee




From tobias.gondrom@gondrom.org  Sun Aug 11 13:52:44 2013
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8D8C11E80E4 for <gen-art@ietfa.amsl.com>; Sun, 11 Aug 2013 13:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.362
X-Spam-Level: 
X-Spam-Status: No, score=-95.362 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Nv6d1pb-ubz for <gen-art@ietfa.amsl.com>; Sun, 11 Aug 2013 13:52:40 -0700 (PDT)
Received: from lvps176-28-13-69.dedicated.hosteurope.de (lvps176-28-13-69.dedicated.hosteurope.de [176.28.13.69]) by ietfa.amsl.com (Postfix) with ESMTP id ECA8221F9E5C for <gen-art@ietf.org>; Sun, 11 Aug 2013 13:46:57 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=cTfyyDDE2rFo/h3Lg0isCi7lKo6b083BbNJ9BI446ldyCiwP6QZOU+VskmDPT/t27NI29Ft7jKw+qt9jPE2kzWS735OO6P8T+GVQ4QPRFQlUBidPmTiNBcGmVNbqxdrY; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
Received: (qmail 11711 invoked from network); 11 Aug 2013 22:46:54 +0200
Received: from 188-222-103-191.zone13.bethere.co.uk (HELO ?192.168.1.64?) (188.222.103.191) by lvps176-28-13-69.dedicated.hosteurope.de with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 11 Aug 2013 22:46:53 +0200
Message-ID: <5207F83D.9010207@gondrom.org>
Date: Sun, 11 Aug 2013 21:46:53 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: rjsparks@nostrum.com
References: <5203F8C2.3060807@nostrum.com>
In-Reply-To: <5203F8C2.3060807@nostrum.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-websec-x-frame-options@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Genart LC review: draft-ietf-websec-x-frame-options-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Aug 2013 20:52:44 -0000

Dear Robert,

thank you very much for the review.
I revised the document to version-08 (also including feedback from other
reviews) accordingly including most of your feedback.
Answers inline.
Best regards, Tobias


On 08/08/13 21:00, Robert Sparks 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-websec-x-frame-options-07
> Reviewer: Robert Sparks
> Review Date: 2013-08-08
> IETF LC End Date: 2013-08-12
> IESG Telechat date: 2013-08-15
>
> Summary: This draft is basically ready for publication, but has nits
> that should be fixed before publication.
>
> This document is intended to act as a informational reference
> describing what's already deployed, and not to act as a standard for
> new implementations to follow. It's obvious that some care has been
> taken to keep that tone in the text, but there are places where it
> still looks like a proposed standard. Please make it even more clear
> who the audience for this document is, and look for places to
> reinforce that this is documenting what _is_, as opposed to trying to
> influence what should be.
>
> The introduction of this version of the document does a good job of
> describing what a clickjack attack is. Appendix B is not really adding
> to that description. I suggest that the two usecases it call out be
> reduced to a couple of sentences in the introduction as examples, and
> a reference to a more in-depth treatment of scenarios like them be
> added for those looking for more information. Section B.3 is
> different, and doesn't add to the understanding of this document.
> Again, I suggest pointing to somewhere else that provides an in-depth
> treatment. (Hopefully, that source would discuss the nested frame
> issue the security considerations section points out in the context of
> the this specific configuration page). [FRAME-BUSTING] might be
> enough, but pointers to something even more rich would certainly be
> helpful.

Apologies, but I would rather keep the three example cases in the
appendix of the document as this will allow better understanding of the
document if references are no longer available. Consider that
clickjacking  description references are not IETF, nor other SDOs and
potentially not stable over the full lifecycle of the RFC.



>
> Here are some suggestions in document order:
>
> In the Abstract, I suggest replace "specification" with either
> "definition" as the introduction uses, or with "the syntax and
> behavior observed in current deployments".
Ok. changed to "definition".


>
> The last paragraph of the introduction reads like standards text.
> Please consider rewriting it with a tone of history and current fact.
> Perhaps starting with "In existing implementations, ", and replacing
> the last sentence with something like "The policy this HTTP header
> declares is enforced by the browser implementations documented here".

Changed accordingly.
Please note: IMHO I did not feel that the last paragraph of the
introduction reads like standards text. However, I appreciate your
feedback and did modify the last sentence of the last paragraph of the
introduction accordingly to remove the word "conforming".
(I believe the remaining text describes sufficiently that this is
documentation. So I did not want to rewrite the whole paragraph and add
history.)


> Since this is documenting an existing deployed header (not
> standardizing it), it would be useful to comment whether the existing
> known implementations allow all the productions of the ABNF described
> here to be used. For instance, would they all honor X-FRAME-OPTIONS:
> deny? (While thinking about this, focus on who this document is for.)

Please note, that section 2.3.2.2. describes the variation in behaviour
between different browsers.
As existing browser implementations may change with regards to whether
they allow _all_ the productions of the ABNF, we intentionally did not
investigate and document all possible outcomes and combinations.

>
> The last sentence of 2.3.1 as written is an attempt to be a standard,
> and is an odd use of 2119. I suggest rewriting it as a warning about
> what happens with existing plugins that ignore the policy carrid in
> the header. That keeps the message aligned with documenting what exists.

Ok. I changed it to non-2119.
However, the remaining text is appropriate and adds clarity to declare
the scope of the x-frame-options header effects. And implementations and
specifications of x-frame-options out there consider it as part that
plug-ins observe x-frame-options if "these plugins appear essentially as
frames".
Please consider that a plug-in that would "essentially appear as a
frame" but would not be observing x-frame-options would in effect break
the security model of the browser implementation, so I think the
remaining text is appropriate and needed in this case.


>
> The first sentence of 2.3.2 is not adding anything to the document. I
> suggest deleting it. The second sentence is placing an implementation
> requirement again. Please consider rewriting as an observation of what
> existing things do, calling out the ramifications of the ones that
> behave differently.

Please consider that even though this is to document existing use
(especially until we get CSP1.1), it's documentation can also help guide
new implementations for the purpose to reduce or avoid divergence of
implementations. This leads to the first sentence and also to the use of
"MAY" in the second sentence, which in fact is not a requirement of the
browser implementation but points out an implementation option.

>
> Similarly, the first paragraphs of Section 2.3.2.1 is written to
> affect new implementation, not document existing implementation. They
> could be re-tuned as above. The third paragraph is good history

As the comment before, this documentation also helps to reduce or avoid
divergence of implementations. So the "SHOULD" is appropriate and as
intended here.


>
> The last sentence of 2.3.2.2 should not say "replace this document" -
> this document is informational documentation about existing
> deployments. CSP1.1 won't Obsolete or Replace this document. Rather it
> should say something like "it is expected that newer implementations
> will use it rather than the mechanisms documented here".

Ok. Changed accordingly.

>
> Nit: s/does support only one/only supports one/
Ok. Changed.
>
> Do the known implementations follow the pattern described in 2.3.2.3?
> Saying something would help tie this to being information about the
> known deployment rather than trying to constrain new development.

Hm. First, as outlined in 2.3.2.2 not all of the browsers support
"Allow-From". And second, the pattern is actually not for the browser
but a way for the server to achieve the specific goal (i.e. of a source
page being framed by more than one web page, even though allow-from
supports only on URI).
To accomodate your feedback and make clear this is not trying to
contrain new development, I changed the word "is recommended" to "can
fulfill that need".

>
> Nit: If Appendix B is kept, please expand CSRF (and consider
> re-pointing to a reference)
>
Ok. Done.

From jari.arkko@piuha.net  Mon Aug 12 10:10:37 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D44B621F84F9 for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, 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 QPeYl7ho2oA4 for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:10:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 95D2E21E80F7 for <gen-art@ietf.org>; Mon, 12 Aug 2013 09:53:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8A36E2CC51; Mon, 12 Aug 2013 19:53:47 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJMxUYBQrkDA; Mon, 12 Aug 2013 19:53:46 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 8066A2CC48; Mon, 12 Aug 2013 19:53:46 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201306030940.r539eEsH093352@givry.fdupont.fr>
Date: Mon, 12 Aug 2013 19:53:46 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DAF9B22-1BC5-4323-8E69-9D2FF8B16369@piuha.net>
References: <201306030940.r539eEsH093352@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1508)
Cc: draft-ietf-mpls-ldp-dod.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] review of draft-ietf-mpls-ldp-dod-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: Mon, 12 Aug 2013 17:10:40 -0000

Francis: thank you for your detailed review! Based on this review I have =
decided to ballot a No-Objection position.=20

Authors: However, there are some editorial issues that Francis raises =
here, and I can not find an e-mail where you would respond to them? Has =
there been a response and/or have the comments been taken into account =
in a newer version? I tried to look at the diffs, but there are quite =
many changes, so I wanted to check that you have seen these and acted on =
those that you believe need to be acted upon.

Jari

On Jun 3, 2013, at 12:40 PM, Francis Dupont <Francis.Dupont@fdupont.fr> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-mpls-ldp-dod-08.txt
> Reviewer: Francis Dupont
> Review Date: 20130527
> IETF LC End Date: 20130527
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
> (Note most of them should be handled by the RFC Editor)
>=20
> - "Requirement Language" section page 1 is not in the body
>=20
> - the requirement keywords are not used everywhere in the document,
>  if I understand well there is a normative part. BTW the question
>  stands too about the Security Considerations.
>=20
> - ToC page 2 and 8 page 31: Acknowledgements -> Acknowledgments
>=20
> - I have some problems with the abbrevs, I suggest:
>  * refer to the RFC Editor list to know if an abbrev is well known or =
not,
>   in the second case consider to introduce it
>  * IMHO all not well known abbrev required to understand the text or =
used
>   more than once must be introduced at the first use
>  * another way is to refer to a terminology RFC
>=20
> - 2 pages 4 and 5: figure 1 should be on one page (BTW this is a good
>  example of something which could be handled by the RFC Editor)
>=20
> - same figure problems for figures 2
>=20
> - 2.1 page 8: examples of the abbrev issue with ECMP, LAG and FEC.
>=20
> - 4.1 page 19: i.e. -> i.e.,
>=20
> - 4.3.2 page 23: [RFC5036] (section A.1.1, page# 100) ->
>  ([RFC5036] section A.1.1, page 100) ??
>=20
> - 4.4 page 23 and 5 page 25: the title should not be at the last line
>=20
> - 4.4 page 24, 7 page 28 and 7.1.2 page 29: e.g. -> e.g.,
>=20
> - 5 is a normative part so uses KEYWORDS (IMHO this should be =
explained,
>  for instance in the Requirement Language section if it is moved to
>  a more standard position)
>=20
> - 5 page 26: the Queue Request Type is TBD but is 0x0971 in the =
schema?
>=20
> - 6.1 page 27: I suggest to add a reference for RFC5036
>  (i.e., RFC5036 -> [RFC5036] as it is in other positions)
>=20
> - 7: I have no problem at all (:-) with using KEYWORDS in Security
>  Considerations!
>=20
> - 7 page 28: are considered as -> are applied as ?
>=20
> - 7.2 page 30 (about keywords): for instance 'should NOT' ->
>  'SHOULD NOT' and keep the MAY in 5.
>=20
> - 7.3 page 30: a more questionable 'may'
>=20
> - 7.4 page 31: two should's which should be IMHO 'SHOULD'
>=20
> - Authors' Addresses page 32: another paging (?) issue
>=20
> - Authors' Addresses page 33: some issues:
> * French ZIP codes are in front (but is it possible to change from
>  the XML? I don't know so if you find a simple way to fix it please
>  both fix it and explain it to me)
> * ITU TS E.123 requires no optional part in the middle of a phone
>  number, i.e., 1-(978)-589-8861 -> +1-978-589-8861
> * no ZIP code for London? BTW grep finds 'FELTHAM  TW14 8HA'
>  (Cisco's communication department should know the canonical
>   address. BTW in my company we had to agree about the canonical
>   company name... :-)
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Mon Aug 12 10:14:31 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F5B821F938E for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:14:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.501
X-Spam-Level: 
X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.098, 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 KZ+Q2Tn5p5BR for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:14:27 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 11C2721F9A05 for <gen-art@ietf.org>; Mon, 12 Aug 2013 09:58:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5DE702CC51; Mon, 12 Aug 2013 19:58:28 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sB73IsnaP77v; Mon, 12 Aug 2013 19:58:27 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 8883F2CC48; Mon, 12 Aug 2013 19:58:27 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201307261325.r6QDPvHn028898@givry.fdupont.fr>
Date: Mon, 12 Aug 2013 19:58:27 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBBDE22B-3731-4CEC-BCFE-7AE265C3D4C6@piuha.net>
References: <201307261325.r6QDPvHn028898@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1508)
Cc: draft-ietf-emu-crypto-bind.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] review of draft-ietf-emu-crypto-bind-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, 12 Aug 2013 17:14:31 -0000

Thanks again for your review, Francis. These really are very helpful. I =
have balloted No-Objection on this document. But authors, have you seen =
the comments, and have you taken them into account?

Jari

On Jul 26, 2013, at 4:25 PM, Francis Dupont <Francis.Dupont@fdupont.fr> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-emu-crypto-bind-04.txt
> Reviewer: Francis Dupont
> Review Date: 20130722
> IETF LC End Date: 20130724
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
> - headers page 2: the keyword section is in the headers (vs the body).
>  This is not the usual place... (BTW it is not the first time I do
>  this comment so either the policy is different than I believe or
>  there is a draft skeleton with this in it?)
>=20
> - Toc page 3 and 7 page 22: Acknowledgements -> Acknowledgments
>=20
> - 3.2.4 page 14: IMHO it should be fine to have an informational
>  reference about EMSK (my idea is to help people to add it in design
>  from the beginning).
>=20
> - 4.2 page 17: edition problem? in:
>=20
>   should require mutual authentication be present in the session.
>=20
>   to accomplish this, implementations including channel binding or
>=20
> - 5.2 page 19 (at the end of the line) EAp- -> EAP-
>=20
> - 5.2 page 19: my spell checker has a concern with "interoperably"
>=20
> Thanks
>=20
> Francis.Dupont@fdupont.fr
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Mon Aug 12 10:18:24 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA2F21F85C3 for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:18:24 -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 lyWlt5hwV0EI for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:18:20 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D427221F8749 for <gen-art@ietf.org>; Mon, 12 Aug 2013 10:07:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 850322CC51; Mon, 12 Aug 2013 20:07:06 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZvLQ-kLYZdpV; Mon, 12 Aug 2013 20:07:05 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 78BB22CC48; Mon, 12 Aug 2013 20:07:05 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51D2C656.3080608@secunet.com>
Date: Mon, 12 Aug 2013 20:07:05 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <1FF74F80-0C66-4F0D-A1C1-C68460F9423B@piuha.net>
References: <048001ce755d$505996e0$f10cc4a0$@gmail.com> <51D2C656.3080608@secunet.com>
To: Johannes Merkle <johannes.merkle@secunet.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org Team" <gen-art@ietf.org>, draft-merkle-tls-brainpool.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-merkle-tls-brainpool-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: Mon, 12 Aug 2013 17:18:24 -0000

Roni, Johannes - thank you. These reviews are important for me to form =
an opinion, and it is good to see that the comments were addressed. I =
have placed a no-objection ballot for this draft.

Jari

On Jul 2, 2013, at 3:23 PM, Johannes Merkle =
<johannes.merkle@secunet.com> wrote:

> a new version addressing your review is on its way.
>=20
> Johannes
>=20
>=20
> Roni Even schrieb am 30.06.2013 08:44:
>> 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-merkle-tls-brainpool-02
>>=20
>> Reviewer: Roni Even
>>=20
>> Review Date:2013=966=9630
>>=20
>> IETF LC End Date: 2013-7=9623
>>=20
>> IESG Telechat date:
>>=20
>>=20
>>=20
>> Summary: This draft is almost ready for publication as Standard track =
RFC.
>>=20
>>=20
>>=20
>>=20
>>=20
>> Major issues:
>>=20
>>=20
>>=20
>> Minor issues:
>>=20
>>=20
>>=20
>> In section 1 you reference TLS 1.0 and 1.1 usage based on RFC 4492. =
What about TLS 1.2 usage specified in RFC5246 A.7
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> Nits/editorial comments:
>>=20
>> 1. In section 3 the  registry name is EC Named Curve
>> 2. In section 3 change =93suitability=94 to =93suitable=94
>>=20
>>=20
>>=20
>=20
>=20
> --=20
>=20
> Mit freundlichen Gr=FC=DFen,
> Dr. Johannes Merkle
> Principal Beratung, Elektronische Identit=E4ten
> Public Sector
> secunet Security Networks AG
> Mergenthaler Allee 77
> 65760 Eschborn
> Germany
> Telefon +49 201 54 54-3091
> Telefax +49 201 54 54-1325
> Mobil   +49 175 2224439
> johannes.merkle@secunet.com
> www.secunet.com
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Mon Aug 12 10:20:00 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D255821F9D70; Mon, 12 Aug 2013 10:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.207
X-Spam-Level: 
X-Spam-Status: No, score=-102.207 tagged_above=-999 required=5 tests=[AWL=-0.208, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, 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 GVJ9toRXm5Xb; Mon, 12 Aug 2013 10:19:57 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id ACFB821F9A0C; Mon, 12 Aug 2013 10:11:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 180C72CC48; Mon, 12 Aug 2013 20:11:54 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lSibXQxwopJw; Mon, 12 Aug 2013 20:11:52 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id F2E522F63C; Mon, 12 Aug 2013 20:11:51 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712984AD61D@MX15A.corp.emc.com>
Date: Mon, 12 Aug 2013 20:11:51 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <617E3D65-CFF1-4006-BAAA-336728231284@piuha.net>
References: <8D3D17ACE214DC429325B2B98F3AE712984AD61D@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Cc: "ldunbar@huawei.com" <ldunbar@huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, Ted Lemon <Ted.Lemon@nominum.com>, "trill@ietf.org" <trill@ietf.org>, Donald Eastlake <d3e3e3@gmail.com>, "igor@yahoo-inc.com" <igor@yahoo-inc.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-directory-framework-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 17:20:01 -0000

David: Thank you. I have placed a no-objection ballot for this draft.

Jari

On Jul 29, 2013, at 2:20 PM, "Black, David" <david.black@emc.com> wrote:

> The -06 version of this draft resolves all of the concerns raised by =
the Gen-ART
> review of the -05 version - the -06 version is ready for publication =
as an
> Informational RFC.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Black, David
>> Sent: Wednesday, July 17, 2013 7:54 PM
>> To: ldunbar@huawei.com; Donald Eastlake; Radia@alum.mit.edu; =
igor@yahoo-
>> inc.com; General Area Review Team
>> Cc: trill@ietf.org; ietf@ietf.org; Black, David; Ted Lemon
>> Subject: Gen-ART review of draft-ietf-trill-directory-framework-05
>>=20
>> Document: draft-ietf-trill-directory-framework-05
>> Reviewer: David L. Black
>> Review Date: July 17, 2013
>> IETF LC End Date: July 18, 2013
>>=20
>> Summary:
>> This draft is on the right track but has open issues, described in =
the review.
>>=20
>> This draft describes a framework for using directory servers to =
provide
>> address mappings (address -> destination RBridge) to TRILL Rbridges =
as an
>> alternative to data plane learning and use of the TRILL ESADI =
protocol.
>>=20
>> The draft's generally well written and clear.  I found a couple of =
minor
>> issues.
>>=20
>> Major issues: None.
>>=20
>> Minor issues:
>>=20
>> [1] The last bullet in Section 3.1 says:
>>=20
>>       - In an environment where VMs migrate, there is a higher chance
>>         of cached information becoming invalid, causing traffic to be
>>         black-holed by the ingress RBridge, that is, persistently =
sent
>>         to the wrong egress RBridge. If VMs do not flood gratuitous
>>         ARP/ND or VDP [802.1Qbg] messages upon arriving at new
>>         locations, the ingress nodes might not have MAC entries for =
the
>>         MAC of the newly arrived VMs, causing unknown address =
flooding.
>>=20
>> This is incorrect in multiple ways and should just be removed:
>>=20
>> - Persistent black-holing is rare in practice because all common
>> 	VM migration implementations issue the gratuitous messages.
>> - VMs don't send the gratuitous messages, hypervisors do.
>> - VDP is not flooded.  The receiver's always a bridge.
>> - At least one common VM migration implementation actually uses a =
gratuitous
>> 	RARP, not ARP.
>> - Flooding is done by the bridges and Rbridges, not the VMs.
>>=20
>> [2] There are some unfortunate notation problems in Section 5.1 that =
carry
>> into the following sections, based on the logical data structure:
>>=20
>>   [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
>>   interested RBridges}]
>>=20
>> - The first open curly brace ('{') is unmatched.
>> - Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
>> 	none of which appear in that structure.
>>=20
>> Nits/editorial comments:
>>=20
>> Section 1 - item 1 in the numbered list does not explain why it makes
>> a directory approach attractive.  This should be added, as it is
>> present for the other three items .
>>=20
>> Section 2 - Say that IS-IS is a routing protocol.
>> The definition of Station should say that the node or virtual node
>> is on a network.  Also, please define or explain "virtual node".
>>=20
>> Section 3.2 - Add the number of entries to be learned to scenario #1
>> in order to parallel the scenario # 2 discussion.
>>=20
>> Section 4 - remove "(distributed model)" from first paragraph,
>> as it's not explained.
>>=20
>> Section 5.3, top of p.13:
>>=20
>>   therefore, there needs to be some mechanism by which RBridges that
>>   have pulled information that has not expired can be informed when
>>   that information changes or the like.
>>=20
>> "or the like" is vague.  I suggest "or becomes invalid for other
>> reasons".
>>=20
>> idnits 2.12.17 didn't find any nits that need attention.
>>=20
>> Thanks,
>> --David
>> ----------------------------------------------------
>> David L. Black, Distinguished Engineer
>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> david.black@emc.com        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Mon Aug 12 10:20:16 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C662721F88FB for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:20:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.501
X-Spam-Level: 
X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.098, 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 s17RRPZ7Tc-T for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:20:11 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4A29D21F96B6 for <gen-art@ietf.org>; Mon, 12 Aug 2013 10:12:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5CFF22F63C; Mon, 12 Aug 2013 20:12:29 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x0GILEvyjVud; Mon, 12 Aug 2013 20:12:27 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id A95EE2CC48; Mon, 12 Aug 2013 20:12:27 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CACvMsLFSS4iYp6vS5iDNP1xk=VXqwOAqH0jUCNkR6DYSPjSxNw@mail.gmail.com>
Date: Mon, 12 Aug 2013 20:12:27 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <24FCED9A-CA8D-4ED8-8F1C-C78B5032265C@piuha.net>
References: <CACvMsLFSS4iYp6vS5iDNP1xk=VXqwOAqH0jUCNkR6DYSPjSxNw@mail.gmail.com>
To: Pete McCann <mccap@petoni.org>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org, draft-ietf-mpls-retire-ach-tlv.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-mpls-retire-ach-tlv-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, 12 Aug 2013 17:20:17 -0000

Pete: Thank you very much for your review. For your information, I have =
placed a no-objection ballot for this draft.

jari

On Jul 31, 2013, at 11:58 PM, Pete McCann <mccap@petoni.org> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document:   draft-ietf-mpls-retire-ach-tlv-03
> Reviewer:     Peter McCann
> Review Date:  2013-07-31
> IETF LC End Date:  2013-07-31
> IESG Telechat date: (unknown)
>=20
> Summary:  Ready
>=20
> Major issues:  None
>=20
> Minor issues:  None
>=20
> Nits/editorial comments:  None
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Mon Aug 12 10:21:25 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D511B21F9A33 for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:21:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.504
X-Spam-Level: 
X-Spam-Status: No, score=-102.504 tagged_above=-999 required=5 tests=[AWL=0.095, 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 cT42lmfLsnKS for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:21:21 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id B9DF421F994C for <gen-art@ietf.org>; Mon, 12 Aug 2013 10:15:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1287A2CC51; Mon, 12 Aug 2013 20:15:31 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f4qK2_wu82Is; Mon, 12 Aug 2013 20:15:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 2831F2CC48; Mon, 12 Aug 2013 20:15:30 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <08c101ce964e$a618c620$f24a5260$@akayla.com>
Date: Mon, 12 Aug 2013 20:15:29 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AA04089-CCC7-4F15-8BBA-9B8B27ADF854@piuha.net>
References: <08c101ce964e$a618c620$f24a5260$@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1508)
Cc: draft-jabley-dnsext-eui48-eui64-rrtypes.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-jabley-dnsext-eui48-eui64-rrtypes-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 17:21:26 -0000

Peter: Thank you very much for your (re)review. Authors, have you seen =
the comments?

For what it is worth, I have placed a no-objection ballot for this =
draft. (Largely based on this review, because I'm on vacation and have =
less time to do my own review, which I would normally do at least =
briefly.)

Jari

On Aug 11, 2013, at 7:52 AM, Peter Yee <peter@akayla.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Please wait for direction from your document shepherd or AD before =
posting a
> new version of the draft.
>=20
> Document: draft-jabley-dnsext-eui48-eui64-rrtypes-05
> Reviewer: Peter Yee
> Review Date: July-07-2013
> IETF LC End Date: July-17-2013
> IESG Telechat date: August-15-2013
>=20
> Summary: This draft is basically ready for publication as an =
Informational
> RFC, but has nits that should be fixed before publication. [Ready with =
nits]
>=20
> This review is the same as the IETF LC review of this draft, which =
remain
> unchanged for the telechat.  This draft defines DNS Resources Record =
Types
> for encoding IEEE 802 EUI-48 and EUI-64 addresses.  Potential privacy =
issues
> with this scheme have been soundly beaten to death with extreme =
prejudice.
>=20
> Major issues:
>=20
> Minor issues:
>=20
> Nits:
>=20
> Page 1, Abstract, 1st paragraph: After "e.g.", append a comma and =
delete an
> extraneous space before "Ethernet".
>=20
> Page 3, Introduction, 1st paragraph, 2nd sentence: change "This" to =
"These"
> and change "specification defines" to "specifications define".=20
>=20
> Page 3, Introduction, 2nd paragraph: append a comma after "e.g.".
>=20
> 		-Peter Yee
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jabley@teksavvy.ca  Mon Aug 12 10:26:18 2013
Return-Path: <jabley@teksavvy.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 C128521F8F29 for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:26:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n1yGYMuyFkGB for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:26:10 -0700 (PDT)
Received: from ironport2-out.teksavvy.com (ironport2-out.teksavvy.com [206.248.154.182]) by ietfa.amsl.com (Postfix) with ESMTP id A629A21F9E47 for <gen-art@ietf.org>; Mon, 12 Aug 2013 10:22:48 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFABK/CFGt9p8q/2dsb2JhbABEgmy8IxZzgh4BAQEBAgEBAQE3NAsFCwIBCBQEHhAnCyUBAQQOBYgLBgEBCsEhkClhA4RokkGPL4J3giQ
X-IPAS-Result: AgEFABK/CFGt9p8q/2dsb2JhbABEgmy8IxZzgh4BAQEBAgEBAQE3NAsFCwIBCBQEHhAnCyUBAQQOBYgLBgEBCsEhkClhA4RokkGPL4J3giQ
X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="21520931"
Received: from postage.chatham.teksavvy.ca ([173.246.159.42]) by ironport2-out.teksavvy.com with ESMTP; 12 Aug 2013 13:22:40 -0400
Received: from POSTAGE.CHATHAM.TEKSAVVY.CA ([2002:adf6:9f2a::adf6:9f2a]) by postage.CHATHAM.TEKSAVVY.CA ([2002:adf6:9f2a::adf6:9f2a]) with mapi id 14.01.0355.002; Mon, 12 Aug 2013 13:22:47 -0400
From: Joe Abley <jabley@teksavvy.ca>
To: Jari Arkko <jari.arkko@piuha.net>
Thread-Topic: [Gen-art] Gen-ART Telechat review of draft-jabley-dnsext-eui48-eui64-rrtypes-05
Thread-Index: Ac6WTjVLeQ4X/0nrTsSskAoejQ+VSwBUtzWAAABBRIA=
Date: Mon, 12 Aug 2013 17:22:46 +0000
Message-ID: <400886F3-7666-498E-8A9F-3405471899E7@teksavvy.ca>
References: <08c101ce964e$a618c620$f24a5260$@akayla.com> <5AA04089-CCC7-4F15-8BBA-9B8B27ADF854@piuha.net>
In-Reply-To: <5AA04089-CCC7-4F15-8BBA-9B8B27ADF854@piuha.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [186.1.202.38]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <95D8D75A5BF02645825AAF6E924E932C@teksavvy.ca>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 12 Aug 2013 10:46:56 -0700
Cc: "<draft-jabley-dnsext-eui48-eui64-rrtypes.all@tools.ietf.org>" <draft-jabley-dnsext-eui48-eui64-rrtypes.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-jabley-dnsext-eui48-eui64-rrtypes-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 17:26:22 -0000

Hi Jari,

I have seen the comments and I have no objection to incorporating the sugge=
sted edits. I have avoided doing that to date, following the advice to wait=
 for the responsible AD before submitting any new versions.


Joe

On 2013-08-12, at 13:15, Jari Arkko <jari.arkko@piuha.net>
 wrote:

> Peter: Thank you very much for your (re)review. Authors, have you seen th=
e comments?
>=20
> For what it is worth, I have placed a no-objection ballot for this draft.=
 (Largely based on this review, because I'm on vacation and have less time =
to do my own review, which I would normally do at least briefly.)
>=20
> Jari
>=20
> On Aug 11, 2013, at 7:52 AM, Peter Yee <peter@akayla.com> wrote:
>=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 posti=
ng a
>> new version of the draft.
>>=20
>> Document: draft-jabley-dnsext-eui48-eui64-rrtypes-05
>> Reviewer: Peter Yee
>> Review Date: July-07-2013
>> IETF LC End Date: July-17-2013
>> IESG Telechat date: August-15-2013
>>=20
>> Summary: This draft is basically ready for publication as an Information=
al
>> RFC, but has nits that should be fixed before publication. [Ready with n=
its]
>>=20
>> This review is the same as the IETF LC review of this draft, which remai=
n
>> unchanged for the telechat.  This draft defines DNS Resources Record Typ=
es
>> for encoding IEEE 802 EUI-48 and EUI-64 addresses.  Potential privacy is=
sues
>> with this scheme have been soundly beaten to death with extreme prejudic=
e.
>>=20
>> Major issues:
>>=20
>> Minor issues:
>>=20
>> Nits:
>>=20
>> Page 1, Abstract, 1st paragraph: After "e.g.", append a comma and delete=
 an
>> extraneous space before "Ethernet".
>>=20
>> Page 3, Introduction, 1st paragraph, 2nd sentence: change "This" to "The=
se"
>> and change "specification defines" to "specifications define".=20
>>=20
>> Page 3, Introduction, 2nd paragraph: append a comma after "e.g.".
>>=20
>> 		-Peter Yee
>>=20
>>=20
>>=20
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20


From jari.arkko@piuha.net  Mon Aug 12 10:47:04 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4301F21F8616 for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.509
X-Spam-Level: 
X-Spam-Status: No, score=-102.509 tagged_above=-999 required=5 tests=[AWL=0.090, 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 hG0QA6jUQjkY for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 10:47:00 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id EE04021F8481 for <gen-art@ietf.org>; Mon, 12 Aug 2013 10:45:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 414262CC51; Mon, 12 Aug 2013 20:45:38 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XcIQ07PUr6Q3; Mon, 12 Aug 2013 20:45:37 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 470052CC48; Mon, 12 Aug 2013 20:45:37 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51E96693.4060605@joelhalpern.com>
Date: Mon, 12 Aug 2013 20:45:37 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4327A224-8FF4-4578-977A-BBE72256B6ED@piuha.net>
References: <51E871B2.3070003@nostrum.com> <51E96693.4060605@joelhalpern.com>
To: Joel M. Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] review: draft-ietf-weirds-using-http-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 17:47:04 -0000

Joel: Thank you for your review! I have placed a no-objection ballot for =
this draft.

Jari

On Jul 19, 2013, at 7:17 PM, Joel M. Halpern <jmh@joelhalpern.com> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-weirds-using-http-07
>    HTTP usage in the Registration Data Access Protocol (RDAP)
> Reviewer: Joel M. Halpern
> Review Date: 19-July-2013
> IETF LC End Date: 29-July-2013
> IESG Telechat date: 15-Aug-2013
>=20
> Summary: This document is ready for publication as a Proposed Standard =
RFC.
>=20
> Major issues:
>=20
> Minor issues:
>=20
> Nits/editorial comments:
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Mon Aug 12 10:48:40 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 237AA21F8A53; Mon, 12 Aug 2013 10:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.087, 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 ScEOqae-vA9A; Mon, 12 Aug 2013 10:48:35 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 128CC21F944C; Mon, 12 Aug 2013 10:48:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 57B5A2CC51; Mon, 12 Aug 2013 20:48:34 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PQTHPLU4G63N; Mon, 12 Aug 2013 20:48:32 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id C1F0B2CC48; Mon, 12 Aug 2013 20:48:32 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24E36595B7@MX15A.corp.emc.com>
Date: Mon, 12 Aug 2013 20:48:32 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <83FEEC19-CF7D-4745-A660-8E90BD9022EB@piuha.net>
References: <F5063677821E3B4F81ACFB7905573F24E36595B7@MX15A.corp.emc.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
X-Mailer: Apple Mail (2.1508)
Cc: "nkong@cnnic.cn" <nkong@cnnic.cn>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-weirds-rdap-sec.all@tools.ietf.org" <draft-ietf-weirds-rdap-sec.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "shollenbeck@verisign.com" <shollenbeck@verisign.com>
Subject: Re: [Gen-art] Gen-art review of draft-ietf-weirds-rdap-sec-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, 12 Aug 2013 17:48:40 -0000

Kathleen: Thank you for your review - these are very important for me. I =
have placed a no-objection ballot for this draft. (Barry and Pete may =
still track the down ref issue, if there's something not completely =
resolved yet.)

Jari

On Aug 9, 2013, at 11:53 PM, "Moriarty, Kathleen" =
<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-ietf-weirds-rdap-sec-04
> Reviewer: Kathleen Moriarty
> Review Date: 8/9/13
> IETF LC End Date:=20
> IESG Telechat date: (if known)
>=20
> Summary:  The draft is well written and is ready for publication.  =
There may be a downref and there will be references to adjust in Auth48, =
but otherwise is ready.
>=20
> Major issues:
>=20
> Minor issues:
>=20
> Nits/editorial comments:  Please check the idnits, there may be a down =
ref:=20
> -- Possible downref: Non-RFC (?) normative reference: ref. 'OpenID'
>=20
>  ** Downref: Normative reference to an Informational RFC: RFC 2818
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Mon Aug 12 10:50:26 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C950021F9C20; Mon, 12 Aug 2013 10:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, 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 dyee2HZNjM1O; Mon, 12 Aug 2013 10:50:21 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id DACB721F9BF7; Mon, 12 Aug 2013 10:50:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 348252CC51; Mon, 12 Aug 2013 20:50:19 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XDhImv3E4Vu; Mon, 12 Aug 2013 20:50:18 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 59D062CC48; Mon, 12 Aug 2013 20:50:18 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <3140092F-123B-4FD3-A7DF-A61C44C76262@vigilsec.com>
Date: Mon, 12 Aug 2013 20:50:18 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A7CC2DAB-89A9-41FD-B5CC-6AE8954A4117@piuha.net>
References: <3140092F-123B-4FD3-A7DF-A61C44C76262@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1508)
Cc: IETF Gen-ART <gen-art@ietf.org>, manet@ietf.org, IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-manet-rfc6622-bis-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, 12 Aug 2013 17:50:27 -0000

Russ: Thank you very much for your review and re-review. I have placed a =
no-objection ballot for this draft for the upcoming IESG telechat.

Jari

On Aug 9, 2013, at 1:09 AM, Russ Housley <housley@vigilsec.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-manet-rfc6622-bis-04
> Reviewer: Russ Housley
> Review Date: 2013-06-15
> IETF LC End Date: 2013-06-27
> IESG Telechat date: 2013-08-15
>=20
> Summary:  The document is ready for publication as a
> standards track RFC.
>=20
> I reviewed -02 during IETF Last Call, and all of my concerns have
> been addressed in -04.


From barryleiba@gmail.com  Mon Aug 12 11:45:30 2013
Return-Path: <barryleiba@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9200D21F9E2B; Mon, 12 Aug 2013 11:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.987
X-Spam-Level: 
X-Spam-Status: No, score=-101.987 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2AC8JKIH5RF; Mon, 12 Aug 2013 11:45:30 -0700 (PDT)
Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 195B621F9E2A; Mon, 12 Aug 2013 11:45:30 -0700 (PDT)
Received: by mail-qc0-f179.google.com with SMTP id n10so1765194qcx.38 for <multiple recipients>; Mon, 12 Aug 2013 11:45:25 -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:message-id:subject :from:to:cc:content-type; bh=5bfA+EzZmSRnKeTHk8P3Cd+1uJuiLeQiNp8BgSIvBe4=; b=jWY3sfA5UJr5gb6O9NiF+g1PfqPrOoUZJK9lsn58OUJbKriDlDVouZFKKQw6gChdOF ivxE03bpU/6GsbFj9i9KqN26Lw11l4njxLQ0hJkiH31ASFFlD4JEgAHCaWPJPTwBLdIs c7GtxQKB3iGcbm/hpivnqPHVBNWuNsNoOENfnGcljbyp7Oee8a0/MXqzhUu0KHlGt+zA 7bdnc3qyaWCyq5VxBh9vJYXhjNpcY/1XUwwAfSK2SbBcOtEjfGhqYy5OUVr9MFsljkAF T8gD8wy2SuTuWUNwxjF1LPFAmWH6kjQ4NWrCZAsONIQJrunF2fi4gEibfhmka3rrG80x 8P7w==
MIME-Version: 1.0
X-Received: by 10.224.97.66 with SMTP id k2mr501153qan.109.1376333124421; Mon, 12 Aug 2013 11:45:24 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.59.211 with HTTP; Mon, 12 Aug 2013 11:45:24 -0700 (PDT)
In-Reply-To: <83FEEC19-CF7D-4745-A660-8E90BD9022EB@piuha.net>
References: <F5063677821E3B4F81ACFB7905573F24E36595B7@MX15A.corp.emc.com> <83FEEC19-CF7D-4745-A660-8E90BD9022EB@piuha.net>
Date: Mon, 12 Aug 2013 20:45:24 +0200
X-Google-Sender-Auth: TAltxDwhu4YtZevgS9tSw-YulM4
Message-ID: <CALaySJKD-i4DgjoUr40TAOX2WeZwvH+AJ-BPrja-smZZ7VeiQw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "draft-ietf-weirds-rdap-sec.all@tools.ietf.org" <draft-ietf-weirds-rdap-sec.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "nkong@cnnic.cn" <nkong@cnnic.cn>, "shollenbeck@verisign.com" <shollenbeck@verisign.com>, "iesg@ietf.org" <iesg@ietf.org>, "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Subject: Re: [Gen-art] Gen-art review of draft-ietf-weirds-rdap-sec-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, 12 Aug 2013 18:45:30 -0000

> (Barry and Pete may still track the down ref issue, if there's something not
> completely resolved yet.)

No, nothing left to do: the references in question all have become or
are becoming informative.

Barry

From cabo@tzi.org  Mon Aug 12 12:28:51 2013
Return-Path: <cabo@tzi.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1902721F9976; Mon, 12 Aug 2013 12:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.166
X-Spam-Level: 
X-Spam-Status: No, score=-105.166 tagged_above=-999 required=5 tests=[AWL=-1.083, BAYES_00=-2.599, FF_IHOPE_YOU_SINK=2.166, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7+aBbeGXauj; Mon, 12 Aug 2013 12:28:45 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id D8A0921F994C; Mon, 12 Aug 2013 12:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7CJSW8A004192; Mon, 12 Aug 2013 21:28:32 +0200 (CEST)
Received: from [192.168.217.105] (p54894F9F.dip0.t-ipconnect.de [84.137.79.159]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id E2C59ED8; Mon, 12 Aug 2013 21:28:31 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=windows-1252
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com>
Date: Mon, 12 Aug 2013 21:28:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F51C4773-131F-43DE-8140-EAB95708584E@tzi.org>
References: <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com>
To: Joe Hildebrand (jhildebr) <jhildebr@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: "draft-bormann-cbor-04.all@tools.ietf.org" <draft-bormann-cbor-04.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 12 Aug 2013 19:28:51 -0000

On Aug 5, 2013, at 19:43, Joe Hildebrand (jhildebr) <jhildebr@cisco.com> =
wrote:

> Sorry, my response is also correspondingly long. =20


The present message wraps up the more general comments sent by Joe
Hildebrand concerning CBOR.  Lots of juicy comments.  Thanks to all!
For these, we are not using the line-by-line style because many of the
topics were touched on by more than one person.

A separate message will follow with line-by-line replies to the more
specific comments.

# Data model

## Extensibility

It is easy to fall into the trap of optimizing for the current
environment.  Experience says there will be some future requirements
that are genuinely unknown today, which may require extending a format
in unforeseen ways.  CBOR plans for this by leaving ~ 10 % of the
encoding space unused (additional information 28..30).  There is
fundamentally no way to guarantee backward compatibility for this kind
of unpredicted extension process.  Leaving code space unallocated may
allow for forward compatibility, though.

CBOR also will be used in multiple environments.  Instead of forcing
each environment to invent their own format, CBOR allows adapting the
format by providing extensible tagging and extensible primitive
("simple") values.  Both are based on registries.  Tags are more
important in practice (and likely to be more numerous).  The tagging
scheme even allows first-come-first-served registration.

Obviously, there is a trade-off between adaptability and
interoperability.  CBOR tries to maximize interoperability by allowing
a generic parser to easily handle tags and primitives the registration
of which it is not aware of.  This will also enable evolving the
decoders and the applications using them on separate timescales, if
that is desired.

We have the same cognitive dissonance as everybody else about opening
the floodgates to extensibility.  The alternative, making it painful
or impossible to adapt the spec to a specific environment, is not
necessarily more desirable. Many existing data formats make
extensibility impossible; if a protocol or application wants one of
those, that's fine; in fact, some of the other data formats that have
been brought up since we started the discussion of CBOR have also
chosen the "no extensibility" path.

## Tags

CBOR has a number of predefined tags.  This is one of the pain points
for extensibility: most tags will not be of interest to some
application or protocol developers, but having them specified early in
the process will lead to better interoperability for those who want
them. During the early development of the spec, Paul and I disagreed
about which tags should be in the first RFC, but ultimately it doesn't
really matter because the choice of tags is up to the protocol or
application that uses CBOR. For all of these tags, a specific CBOR
application will specify which of them are actually in use.

There is little disagreement that we need a tag for a date/time
format; there is probably no way to agree on a single one, so the
document currently includes both RFC 3339 and epoch-based formats.
Bignums (integer) may be less obvious to some, they are very obvious
in other environments.  Having (extended precision) base2 floating
point as well as a base10 floating point in there also seems obvious
for those environments that need it. These are the typical programming
language types.  YAGNI doesn't apply; leaving them out of the spec
just means that there likely will be several, incompatible versions of
them.

Four tags on strings indicate further likely kinds of data.  Nesting
CBOR encoding into a byte string seems natural to support.  We also
included tags for URIs, regular expressions, and MIME messages (OK,
maybe less obvious).

Then we have two tags that indicate that a text string is encoded in
Base64/Base64url (33/34).  The argument could be made that these could
be decoded and sent as byte strings; however, there may be a need to
keep the exact format (whitespace and padding), e.g. for signature
checking.

Tags 21-23 do the inverse: they tag byte strings with the base
encoding that any JSON converter on the path should be
using. Converter hints may be a new concept in a data format; in a
world where JSON is widely used in processing chains, they could be
eminently useful (Paul and I still disagree on this one.)

Tags can be nested.  Actually, since every tag specifies its possible
contents, none of the tags specified in -04 can be nested.  To cite an
obvious example where nested tagging would be used, tag 1 accepts a
floating point value and might be changed to also accept a base10
floating point value (tag 1 currently does not allow that, though).

Disallowing the nesting of tags just forces a protocol designer to
turn tag1(tag2(x)) into something more complex like
tag1([tag2(x)]). We don't think forcing the introduction of this
complexity reduces complexity.

For an implementation that does know both tags, the processing will be
natural.  Any other implementation can ignore the unknown tags or
(preferably) hand them to the application in a similar way the other
containing data structures are handed to the application (i.e, tagx(y)
is not much different in handling from [x, y] or {x: y}).

A later BCP might want to warn specifiers of future tags that
designing them in such a way you get recursion (as opposed to mere
nesting) is not such a good idea, but you have to come up with very
contrived examples before that becomes a concern.

# Encoding issues

## Numbers

Interchanging numbers is a much more complicated issue than one would
think.  Recent discussions of number precision issues in the JSON WG
show that it is easy to underestimate the problem and get this wrong.

In the area of integer numbers, CBOR is highly opinionated in favor of
unsigned (i.e., non-negative) numbers =97 this is what is actually
needed in the majority of applications.  Many applications also will
clearly need negative numbers, so they have their own encoding.
Obviously, if you encode N bits for a negative number, you need N+1
bits in a signed representation of that since you need to add the sign
bit.  We chose to keep N at 8, 16, 32, 64, so N+1 has a slightly odd
size, which implementers indeed need to be aware of if that is larger
than their number range (not a problem, e.g., for JavaScript).  CBOR
protocols should be explicit about the number range and precision that
is expected to be supported.

In the area of floating point numbers, CBOR ignores IEEE 754 decimal
numbers (in favor of its own, simpler format) and only supports three
sizes of the IEEE 754 binary floating point numbers.  That is, again,
opinionated (but can be fixed in a pinch by introducing appropriate
tags).  The inclusion of 16-bit floating point is motivated by its
usefulness for low-precision sensor data.  The reason this may not be
obvious to many is likely that programming languages evolve on time
scales where this 2008 addition to IEEE 754 is still very, very
recent.

## Maps

As with most modern programming languages, CBOR has a map type; this
is intended to be a general map and not to be limited to text string
keys as in JSON objects.  Dependent specifications have already been
started that make good use of non-text keys.  In particular, integer
keys are a good match for environments that already maintain some form
of registry based on integers.

CBOR maps are intended to be maps, not multimaps.  Duplicate keys are
an encoding error.  Unfortunately, what should be considered duplicate
is often application dependent (are 0 and 0.0 the same key?  "=C5" and
"=C5"?), so a generic parser will only be able to do part of the work.

CBOR maps do not ascribe meaning to the order of items in the
map. This is hard to prescribe in the format; it is a requirement on
the applications using it.

# Implementation issues

Complexity/Code size: We will leave an assessment of that to those who
have implemented the spec (and we have heard from a few).  The
pseudo-code in Appendix C should give some impression how a minimal
implementation could look like.

Performance: Memory allocation indeed is a significant contributor to
the CPU use of a format decoder.  CBOR tries to help a bit by
providing right at the start of a data item the size of the object
that needs to be allocated (as opposed to the length of its
representation as in ASN.1 BER).

Of course, that is not possible in indefinite length encoding
("streaming"); here we trade off some additional CPU in the decoder
(needed for reallocation/copying of unknown-length structures) against
less complexity in the encoder, for those cases where the encoder
would need to perform significant buffering to obtain these sizes
before encoding a data item.

# Document issues

We are open to suggestions for replacement words for "well-formed" and
"valid" in Section 3.7.  A definition of "valid" is not actually
needed; that term is only used in its English sense in the discussion
of generic parsers (and the connotation with XML's sense of valid is
unfortunate).  "Well-formed" is defined algorithmically in the
pseudocode in Appendix C.

For a binary format, there is a strong requirement for a diagnostic
notation that everyone understands that is trying to get an
application going.  So defining it in the document is the best way to
get this.  This definition is not needed for interop, so we can do
away with ABNF etc.  I started out by saying something equivalent to
"MUST NOT be parsed", but an RFC 2119 MUST struck me as silly when
diagnostic notation is not meant for interop in the first
place. (Also, there might be tools for encoding test vectors etc. that
do parse diagnostic notation; in -05, we have added a pointer to YAML
as another format that may be useful for text-based specification of
CBOR data items in configuration files.)

Gr=FC=DFe, Carsten


From shollenbeck@verisign.com  Mon Aug 12 12:43:14 2013
Return-Path: <shollenbeck@verisign.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02F9D21F9C0E; Mon, 12 Aug 2013 12:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.682
X-Spam-Level: 
X-Spam-Status: No, score=-6.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cebe6DKHo269; Mon, 12 Aug 2013 12:43:04 -0700 (PDT)
Received: from exprod6og127.obsmtp.com (exprod6og127.obsmtp.com [64.18.1.78]) by ietfa.amsl.com (Postfix) with ESMTP id 9463921F9F85; Mon, 12 Aug 2013 12:41:17 -0700 (PDT)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob127.postini.com ([64.18.5.12]) with SMTP ID DSNKUgk6W0MH1vhtM3hk2z7B7BEiYyy4muMo@postini.com; Mon, 12 Aug 2013 12:43:03 PDT
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id r7CJf9kk001263 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 12 Aug 2013 15:41:09 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Mon, 12 Aug 2013 15:41:09 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Barry Leiba <barryleiba@computer.org>, Jari Arkko <jari.arkko@piuha.net>
Thread-Topic: [Gen-art] Gen-art review of draft-ietf-weirds-rdap-sec-04
Thread-Index: AQHOlUKGo9O1fzm1QESFUp6H8053SJmSINsAgAAP4wD//8xr8A==
Date: Mon, 12 Aug 2013 19:41:08 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F49232CDD@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <F5063677821E3B4F81ACFB7905573F24E36595B7@MX15A.corp.emc.com> <83FEEC19-CF7D-4745-A660-8E90BD9022EB@piuha.net> <CALaySJKD-i4DgjoUr40TAOX2WeZwvH+AJ-BPrja-smZZ7VeiQw@mail.gmail.com>
In-Reply-To: <CALaySJKD-i4DgjoUr40TAOX2WeZwvH+AJ-BPrja-smZZ7VeiQw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-weirds-rdap-sec.all@tools.ietf.org" <draft-ietf-weirds-rdap-sec.all@tools.ietf.org>, "nkong@cnnic.cn" <nkong@cnnic.cn>, "gen-art@ietf.org" <gen-art@ietf.org>, "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-ietf-weirds-rdap-sec-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, 12 Aug 2013 19:43:14 -0000

> -----Original Message-----
> From: barryleiba@gmail.com [mailto:barryleiba@gmail.com] On Behalf Of
> Barry Leiba
> Sent: Monday, August 12, 2013 2:45 PM
> To: Jari Arkko
> Cc: Moriarty, Kathleen; nkong@cnnic.cn; gen-art@ietf.org; draft-ietf-
> weirds-rdap-sec.all@tools.ietf.org; iesg@ietf.org; Hollenbeck, Scott
> Subject: Re: [Gen-art] Gen-art review of draft-ietf-weirds-rdap-sec-04
>=20
> > (Barry and Pete may still track the down ref issue, if there's
> something not
> > completely resolved yet.)
>=20
> No, nothing left to do: the references in question all have become or
> are becoming informative.

Correct.

Scott

From cabo@tzi.org  Mon Aug 12 13:37:47 2013
Return-Path: <cabo@tzi.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2C921F9FD6; Mon, 12 Aug 2013 13:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.098
X-Spam-Level: 
X-Spam-Status: No, score=-105.098 tagged_above=-999 required=5 tests=[AWL=-1.015, BAYES_00=-2.599, FF_IHOPE_YOU_SINK=2.166, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oW6sw8fnEPk4; Mon, 12 Aug 2013 13:37:35 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 9502421F9E45; Mon, 12 Aug 2013 13:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7CKbUYQ012599; Mon, 12 Aug 2013 22:37:30 +0200 (CEST)
Received: from [192.168.217.105] (p54894F9F.dip0.t-ipconnect.de [84.137.79.159]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 38411F01; Mon, 12 Aug 2013 22:37:29 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com>
Date: Mon, 12 Aug 2013 22:37:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B377A8B-C954-4DEE-B19C-506CE8B295A2@tzi.org>
References: <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com>
To: Joe Hildebrand (jhildebr) <jhildebr@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: "draft-bormann-cbor-04.all@tools.ietf.org" <draft-bormann-cbor-04.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 12 Aug 2013 20:37:47 -0000

On Aug 5, 2013, at 19:43, Joe Hildebrand (jhildebr) <jhildebr@cisco.com> =
wrote:

> Sorry, my response is also correspondingly long.  There are some =
original
> comments at the end=20

[...]

We have worked a bit on the detail remarks of your review.
(The previous message addressed the grander aspects).
Item-by-item replies below:

        Other things that ought to be discussed:

        I would like to see another design goal: "May be implemented in =
modern web
        browsers".  That should be possible with the new binary types.

Indeed, implementability on a wide set of platforms is an important
goal, somewhat implicit in out objective 2.  I believe the design goal
was achieved.

        I still don't see the need for non-string map keys.  JSON =
mapping would be
        easier without them, as would uniqueness checking.  If they are =
to be
        retained, they should have some motivation in the spec, =
describing how and
        why they might be used.

I'm not sure they particularly need to be motivated in the spec. =
However, we will
add something like "For example, using numbers for keys is useful in
cases where the values are numeric and numeric ordering of keys is =
important."

Further, data formats have been using complex map keys for a long time,
e.g. cf. YAML.

As an example, CBOR (diagnostic notation)

{ {"country": "DE", "license": "HB-MH 765"}: {"make": "Ford", "km": =
192735.2},
  {"country": "FI", "license": "601 ICE"}: {"make": "BMW", "km": =
68923.1} }

might be used to describe a map of cars, indexed by their license
plate, where the license plate uses a country identifier and the plate
text as its two components.

In JSON, I would be forced to munge together the unrelated country and
license strings using some custom delimiter syntax (say,
"DE/HB-MH 765"); in CBOR (or YAML), I can keep them nice and semantic.

In YAML:

---
? country: DE
  license: HB-MH 765
: make: Ford
  km: 192735.2
? country: FI
  license: 601 ICE
: make: BMW
  km: 68923.1

As always, protocols based on CBOR do not have to use this
functionality; in section 3.4 we encourage using strings, or integers,
as map keys (and =BBkeys should be of a single CBOR type=AB).

        I wish I could think of another good simple value that we might =
register
        one day.  The only one I've come up with is "no-op", which I =
might use in
        a streaming application as a trivial keep-alive or a marker =
between
        records to ensure parser state sync.  I wouldn't classify that =
as "good"
        however.

This is indeed the less likely avenue of extension of the format.
However, as an example, we would have used simple values for the
Infinities and NaN if the IEEE 754 formats didn't already provide a
good representation.

        Nested tags ought to be forbidden until we come up with a strong =
use case
        for them.

The tag 55799 ("self-describing CBOR", allowing to start a CBOR data
item with 0xd9d9f7 for file type disambiguation) in -05 is a pretty
strong use case; you should be able to use it independent of whether
the data item is top-level tagged or not.

        I could use some implementation guidance on how to generate the =
most
        compact floating-point type for a given number, assuming we keep =
all of
        the floating-point types.

I hope to have my C code for this on github, soon...
I did it like this:

void cbor_encoder_write_double(double v)
{
  float fv =3D v;
  if (fv =3D=3D v) {  // i.e., the 32-bit float value doesn't lose data
    // ... do the same thing for half; encode as half or single
  } else {
    // ... encode as double
  }
}

If your platform doesn't give you the necessary floating point types,
but you have (possibly coded yourself) the bitwise access to the
floating point representation you need to send binary doubles, this is
a bit more work, which I haven't done yet (it will probably look a bit
like the Python code in Appendix D).

        I don't like 2.4.4.2 "Expected Later Encoding for CBOR to JSON
        Converters".  Having a sender care about the encoding of a =
second format
        at the same time seems unnecessarily complex.  I'd like to see =
this
        section and the corresponding tags moved to another spec, or =
just removed.

I think we have a pretty good use case in constrained implementations
that marshal data for later use a CBOR to JSON converter.
(See other message.)

        Similar for tags 33 and 34.  Just send the raw bytes as a byte =
string;
        there's no need to actually base64 encode.

(See other message.)

        Section 3.2.3, we should call out the heresy of including UTF-16
        surrogates encoded as UTF-8 for those that can't read the UTF-8 =
spec.

I'm with you on the subject matter, but I'm not sure if adorning
normative references with "hey, we really mean this" should be
necessary...

        Overall in section 3.2, "should probably issue an error but =
might take
        some other action" seems like it will cause some interop =
surprises in
        practice.

-05 will have some cleanups here.

        Section 3.3, "all number representations are equivalent" is =
unclear, even
        with the clarifying phrase afterward.

Slightly clarified.

        If section 3.6 stays, the numerics need more work.  +/- Infinity =
should be
        treated like NaN.

(Why?)

        "if the result is the same value" would benefit from
        some more clarity.  The tags section is also somewhat unclear.

Clarified slightly.

        Section 4.2, what about numbers with uninteresting fractional =
parts, like
        1.0?  What about numbers in exponential format without =
fractional parts,
        like 1e10?  I would recommend against even suggest encoding in =
place.
        It's likely to cause a security issue for the reason mentioned.

Clarified in -05 that it is actually warning against the in-place
strategy.

        Section 6, including the diagnostic notation is a little =
strange.  I would
        at least like "it is not meant to be parsed" to be strengthened =
to "MUST
        NOT be parsed".

(See other message.)

        Section 7.1, simple values 0..15 can never be used with this =
construction.
         If that's intentional, then give a good reason.

(Fixed the wording based on IANA input.)

        Section 7.2, do we have language we can use about how to reclaim
        first-come-first-serve tags that aren't being used anymore?  =
e.g. the web
        page is down and the requestor may be dead.

It is generally impossible to reclaim IANA values once assigned --
even if the requestor is no longer active, the data may still be in
use on the wire or in some archive.  Our registry should be no
different than anyone else's.

        In section 7.3, yes, we should make "application/mmmmm+cbor" =
valid.

Added section 7.4 based on text suggested by Tony Hansen.

        In section 8, perhaps mention a stack attack like:

        0x818181818181818181...

        I implemented depth counting with a maximum as an approach to =
avoid this.

        There are likely to be lots of other security concerns.

Added a paragraph on resource exhaustion attacks.

        I have checked all of the examples in Appendix A.  I would have =
expected

        2(h'010000000000000000') | 0xc249010000000000000000

        Not 18446744073709551616, since in the diagnostic, I don't =
necessarily
        support bignums.

        Same with 0xc349010000000000000000.

I prefer to keep the explanatory value of actually giving the decoded
bignum value.  Text added:
=BBIn the diagnostic notation provided for bignums, their intended
numeric value is shown as a decimal number (such as
18446744073709551616) instead of showing a tagged byte string (such as
2(h'010000000000000000')).=AB


        For numbers, section 9.8.1 of ECMA-262 (JSON.stringify) is =
relevant.  So:

        5.960464477539063e-8 | 0xf90001   (not e-08)
        0.00006103515625 | 0xf90400       (not e-05)

Changed this way in -05.

        In Appendix B, there are holes in the jump table.  If you're =
going to have
        a table, call out the invalid values, such as 0x1c-0x1f.

This may be shortened to rather call out the remaining valid values.
Done in -05.

        In Appendix C, the use of the variable "breakable" is unclear, =
and it's
        not obvious how you'll get to the "no enclosing indefinite" =
case.

breakable starts out as false.  It is given as true where instead of a
data item a "break" stop code is allowed to occur.
The "no enclosing indefinite" case is reached if breakable is not set
and an 0xFF is encountered anyway.

        In Appendix D, shouldn't the input be unsigned or an array of =
bytes?

It could also be unsigned short (which would be widened to int
anyway), but in this case it shouldn't matter.
(Array of bytes would just be slightly more tedious.)

        Appendix E.1, aren't there some cases of DER where you need the =
schema to
        parse?

As opposed to in BER?  I'm not aware of that.
(DER is a restricted subset of BER.)
DER and BER are not exactly enabling schemaless decoding; they have in
common that that implicit tagging may hide the data type information
so you may need the schema information (ASN.1 definition) to find out
the actual data type in use.
(However, you can parse the surface structure of a BER/DER object
without schema information.)
We included this not because it is an alternative to CBOR, but because
its use in the IETF is widespread.

        Add PER.

PER does need schema information even for parsing and would require
its own little dissertation, so we left this off.

        Appendix E, we should mention Smile, since the first two octets =
are so
        cute.

:)

(Smile was on my initial list of formats to cover in the appendix, but
it is rather complicated and would need large amounts of text, beyond
what would be appropriate for this little appendix.)

        Overall, I think this doc shows a lot of promise, and I'm =
looking forward
        to having something on standards track that has these =
properties.

Thank you for this detailed review!

Gr=FC=DFe, Carsten


From jhildebr@cisco.com  Mon Aug 12 14:41:55 2013
Return-Path: <jhildebr@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 47EAD21F9F44; Mon, 12 Aug 2013 14:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.635
X-Spam-Level: 
X-Spam-Status: No, score=-10.635 tagged_above=-999 required=5 tests=[AWL=-0.036, 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 BLiHwp8MECFP; Mon, 12 Aug 2013 14:41:49 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 0B18F21F9EE1; Mon, 12 Aug 2013 14:41:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1544; q=dns/txt; s=iport; t=1376343709; x=1377553309; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=hh5P89+HJrpOPIUiHsJwPmEDK+1zKRZsomVxADyZp2A=; b=BcJibycpQD9yqDh0Xq1qUiN6cx0DVweS3rCBEf/zQDcv8tflNIYzn4lo Yk8f6bFGcDDnwkpWZ5vzhUTl1FMjkuKVDC4uQP4ep+Av3KX513tg/z0Bx 6X3yaKHVSeIidyuOz8ZdafXbKUetVCV2Uvhb2UqKyGoRGgQ281LQmbtgh E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFADtWCVKtJXG+/2dsb2JhbABbgwaBBb5XgRwWdIIkAQEBAwE6PwUNAQgOFBRCJQIEDgUIiAIGtnaQCjEHgxt2A5QNlSiDG4Iq
X-IronPort-AV: E=Sophos;i="4.89,864,1367971200"; d="scan'208";a="246479680"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-6.cisco.com with ESMTP; 12 Aug 2013 21:41:24 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r7CLfNG2019159 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 12 Aug 2013 21:41:23 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.159]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Mon, 12 Aug 2013 16:41:23 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Carsten Bormann <cabo@tzi.org>
Thread-Topic: [apps-discuss] Gen-ART review of draft-bormann-cbor-04
Thread-Index: AQHOjPNCXWeGtSFAj0iRwScRzl7yuJmG2+2AgAuVgwD//61EgA==
Date: Mon, 12 Aug 2013 21:41:23 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A714199D03@xmb-rcd-x10.cisco.com>
In-Reply-To: <2B377A8B-C954-4DEE-B19C-506CE8B295A2@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [10.21.146.155]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <720240F1A24B6246958F976DA5B2D52E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-bormann-cbor-04.all@tools.ietf.org" <draft-bormann-cbor-04.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 12 Aug 2013 21:41:55 -0000

On 8/12/13 2:37 PM, "Carsten Bormann" <cabo@tzi.org> wrote:

>        If section 3.6 stays, the numerics need more work.  +/- Infinity
>should be
>        treated like NaN.
>
>(Why?)

Having more than one way to encode +/- Infinity seems like a recipe for
generating slightly different canonical output.  For example, in my code
right now, I think I'm always generating a half-precision Infinity, and
I'm thinking about changing that to always be the 4-byte version.

I now see that this section is just a recipe for how to define a
canonicalization, not the actual rules you need to follow, and my comment
may be moot.  However, I suggest that section 3.6 is therefore not
terribly useful, and it might be removed without harming the document.

>        In Appendix D, shouldn't the input be unsigned or an array of
>bytes?
>
>It could also be unsigned short (which would be widened to int
>anyway), but in this case it shouldn't matter.
>(Array of bytes would just be slightly more tedious.)

Agree that it's merely a tedious transformation, but I think it would be a
lot more clear.  Semantically, the input isn't an integer of any size.
It's two bytes in a specific order.

>        Add PER.
>
>PER does need schema information even for parsing and would require
>its own little dissertation, so we left this off.

I think it's useful to call out an example that is explicitly
schema-ridden, particularly since it has been called out in this
conversation as something relevant.

--=20
Joe Hildebrand




From martin.thomson@gmail.com  Mon Aug 12 14:51:40 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDC0A21F9FD6; Mon, 12 Aug 2013 14:51:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.114,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sMulzN-rECQV; Mon, 12 Aug 2013 14:51:37 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 42FE221F9F9D; Mon, 12 Aug 2013 14:51:37 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w60so6055812wes.15 for <multiple recipients>; Mon, 12 Aug 2013 14:51:34 -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=iT/YWtLfJX7b5J47Ymo5M9Lp1Ne5+pXoAYrpiq7vhvA=; b=PmZCKiCKxH0rQG84QVwSM3cyNDqLBvXoE4n1VNGUa0HsHZ/MnfbLHMegVC+hHiyJQF seuExi+B73xBvm1Nw0CMolFK7H4Ti2msQFFsuvmrqIk4la5Ijvb7GT4ygC+9U6MnXXQ8 K4Y5ecpRfwpYdsNIqjG87Nen5dDcj+txG3xHZQwmLwAXLf2ovOUt9i+78Yde9boyjlpM pZV+ZLU1DR1l++kpCVmyFhSLt4jRdYjG25UIJfMcGplOdyDfQ8dXzdfX2OuZLSMceMI4 u8VWllt4g1l7bYGfAecHL1kdMr0j3CeT2EVdwNtkocdMiHsOpc2JLVZgqNm4UWSpDzS+ C3+g==
MIME-Version: 1.0
X-Received: by 10.180.187.2 with SMTP id fo2mr516200wic.65.1376344294802; Mon, 12 Aug 2013 14:51:34 -0700 (PDT)
Received: by 10.194.28.39 with HTTP; Mon, 12 Aug 2013 14:51:34 -0700 (PDT)
In-Reply-To: <F51C4773-131F-43DE-8140-EAB95708584E@tzi.org>
References: <A723FC6ECC552A4D8C8249D9E07425A71418233A@xmb-rcd-x10.cisco.com> <F51C4773-131F-43DE-8140-EAB95708584E@tzi.org>
Date: Mon, 12 Aug 2013 22:51:34 +0100
Message-ID: <CABkgnnU5u0P7G=ojLoLD1H_hiOjRz9d5yS3iiA69rUumwJDMjA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>, Joe Hildebrand <jhildebr@cisco.com>, draft-bormann-cbor.all@tools.ietf.org
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 12 Aug 2013 21:51:40 -0000

Hi Carsten,

I wasn't really looking for a defense of the design in the form you
just provided, cogent as it was.  I want to know what value you get
from these extensibility features, not a reiteration (and expansion)
of the characteristics of those features.

My operating assumption was that JSON was successful precisely because
it was only extensible in one limited direction.  In some ways, this
is the challenge I wanted to set by writing my review.  Can you a)
invalidate that theory somehow, and b) motivate the addition of each
axis of extensibility.

As I said privately, I have no problem with shipping a proposed
standard RFC that has a clear set of goals, and I think that you are
doing the right thing in that regard.  What I really want to do is
have is that other conversation.  And maybe long review threads are
the wrong place for that conversation, I don't know (maybe I'll drop
gen-art on my next reply).

On 12 August 2013 20:28, Carsten Bormann <cabo@tzi.org> wrote:
> CBOR maps are intended to be maps, not multimaps.  Duplicate keys are
> an encoding error.  Unfortunately, what should be considered duplicate
> is often application dependent (are 0 and 0.0 the same key?  "=C3=85" and
> "=C3=85"?), so a generic parser will only be able to do part of the work.

Ouch, really?  Add this to the list of things that a using
application/specification needs to worry about.  SASLprep anyone?
Maybe there should be a list of those somewhere in the draft, which
includes:

The types to implement (and whether to disallow or ignore others)
What map keys to permit and how to compare them (with a special note
about IEEE 754 NaN values, which might be bit-exact, but don't compare
equal)
The extension points to implement (and how to ignore 28-30)
Whether to allow tags
Which tags to ignore
What date format(s) to use
What to do about JSON if you are performing translation (see tags)
What types to permit indefinite length encoding for
... and I'm sure I've missed something

--Martin

From wassim.haddad@ericsson.com  Mon Aug 12 18:09:59 2013
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 1969121F9F62 for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 18:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 kTeJkI7kxmBD for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 18:09:53 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 6959C21F9BDB for <gen-art@ietf.org>; Mon, 12 Aug 2013 18:09:53 -0700 (PDT)
X-AuditID: c6180641-b7f986d000007a82-2a-5209875f6ce1
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id FC.10.31362.F5789025; Tue, 13 Aug 2013 03:09:51 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0328.009; Mon, 12 Aug 2013 21:09:50 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Gen-ART Review of draft-housley-ltans-oids-01
Thread-Index: AQHOl8HPp+oUC/z4jkmy64A5Sdlrtw==
Date: Tue, 13 Aug 2013 01:09:50 +0000
Message-ID: <2887062F9ADE75448F0F3A2780C21B621C67688C@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_2887062F9ADE75448F0F3A2780C21B621C67688Ceusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyuXRPrG58O2eQwff/OhZXX31msWjeeZLJ gcljyZKfTB5fLn9mC2CK4rJJSc3JLEst0rdL4MqYPXc7S8ENoYoVm+8zNjCuFehi5OCQEDCR OLSUo4uRE8gUk7hwbz1bFyMXh5DAUUaJCacmMUE4yxklNs6eyghSxSZgIPF1+VlWEFtEQFNi 7oq3YEXMAs2MEm1HuplBpgoLOEjsOK8GUeMq8f/9AyaQsIiAnsT2hV4gYRYBVYm/71pZQGxe AV+J9U8b2UBsRqAjvp9awwRiMwuIS9x6Mp8J4jgBiSV7zjND2KISLx//AztBFGhk96zlrBBx ZYnvcx6xQPTmS9zr/MUIMV9Q4uTMJywTGEVmIRk7C0nZLCRlEHEdiQW7P7FB2NoSyxa+Zoax zxx4DNTLAWRbS2w+xIysZAEjxypGjtLi1LLcdCPDTYzAiDomwea4g3HBJ8tDjNIcLErivBv0 zgQKCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYCznLZq16NkD9oKULceO2e2c4NgsdExqR/+c Te4291IN5ulfWF+99+nmjR3HFqYslJk1L76v9qT9hnXLXcq5WczuKUoefeX1u1vz65FHqtri B0uWaSw+1rrMmvFSuwvbDOd5Feq1+1acuFfuNLuX+ctvg+Aj56+3dzg4r2X4nNGZNUtw7WXx 9RJKLMUZiYZazEXFiQB6y7ZzdgIAAA==
Cc: "housley-ltans-oids.all@tools.ietf.org" <housley-ltans-oids.all@tools.ietf.org>
Subject: [Gen-art]  Gen-ART Review of draft-housley-ltans-oids-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 01:09:59 -0000

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

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

Document: draft-housley-ltans-oids-01
Reviewer:  Wassim Haddad
Review Date: 13 August 2013
IETF LC End Date: 31 July 2013
IETF Telechat Date: 15 August 2013

Summary:  This draft is ready for publication as an informational RFC

- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.


--_000_2887062F9ADE75448F0F3A2780C21B621C67688Ceusaamb103erics_
Content-Type: text/html; charset="us-ascii"
Content-ID: <5775C1BCAF145F4894C2548C38E7B057@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>
<div>
<div>
<pre style=3D"word-wrap: break-word; white-space: pre-wrap; "><div style=3D=
"white-space: normal; "><font face=3D"Calibri">I am the assigned Gen-ART re=
viewer for this draft. For background on Gen-ART,&nbsp;<br>please see the F=
AQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfa=
q">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;<br><br>D=
ocument:&nbsp;draft-housley-ltans-oids-01<br>Reviewer: &nbsp;Wassim Haddad<=
br>Review Date: 13 August 2013<br>IETF LC End Date: 31 July 2013<br>IETF Te=
lechat Date: 15 August 2013<br><br>Summary: &nbsp;This draft is ready for p=
ublication as an informational RFC</font></div><div style=3D"white-space: n=
ormal; "><font face=3D"Calibri"><br></font></div><div style=3D"white-space:=
 normal; "><font face=3D"Calibri">- Major Issues: None<br><br>- Minor Issue=
s: None<br></font></div><div style=3D"white-space: normal; "><font face=3D"=
Calibri"><br></font></div></pre>
</div>
<div style=3D"font-family: Calibri, sans-serif; ">
<div>Regards,</div>
<div><br>
</div>
<div>Wassim H.</div>
<div><br>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_2887062F9ADE75448F0F3A2780C21B621C67688Ceusaamb103erics_--

From wassim.haddad@ericsson.com  Mon Aug 12 19:22:57 2013
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 1BDF911E8104 for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 19:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[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 riSNpozVv0rv for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 19:22:48 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id D236111E80FE for <gen-art@ietf.org>; Mon, 12 Aug 2013 19:22:44 -0700 (PDT)
X-AuditID: c618062d-b7fc36d0000032ea-cc-520998734648
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 83.6C.13034.37899025; Tue, 13 Aug 2013 04:22:44 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0328.009; Mon, 12 Aug 2013 22:22:43 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Gen-ART Review of draft-housley-ltans-oids-01
Thread-Index: AQHOl8HPp+oUC/z4jkmy64A5Sdlrt5mTMZ+A
Date: Tue, 13 Aug 2013 02:22:42 +0000
Message-ID: <2887062F9ADE75448F0F3A2780C21B621C6768ED@eusaamb103.ericsson.se>
In-Reply-To: <2887062F9ADE75448F0F3A2780C21B621C67688C@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_2887062F9ADE75448F0F3A2780C21B621C6768EDeusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyuXRPlG7JDM4gg8WzeCx+71jMYnH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvj69sDjAUPVCsm7V3N1MC4V7GLkZNDQsBE 4tyPd2wQtpjEhXvrgWwuDiGBo4wSy088ZIFwljNKTF6wgR2kik3AQOLr8rOsILaIgKbE3BVv mUCKmAX6GSXebJ8INkpYwEWi/fAhZogiV4n/7x8wQdhGEv9PrwJrZhFQlTg+YR8jiM0r4Csx 5ckLoDgHB6eAn8Sha1EgYUagi76fWgPWyiwgLnHryXwmiEsFJJbsOc8MYYtKvHz8D2ykqICe RPes5awQcWWJ73MesUD05kss+36RDWKVoMTJmU9YJjCKzkIydhaSsllIyiDiBhLvz81nhrC1 JZYtfA1l60ts/HKWEcK2lmjqXsKGrGYBI8cqRo7S4tSy3HQjg02MwHg7JsGmu4Nxz0vLQ4zS HCxK4ryr9M4ECgmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamAUqFeUeGwZOi/h4OkTc35XGl+t OC6zJn3Ze9MNLzsX+gi36lb5vX7dnuDTsveN8mKOQ9YLd1/TrNbQvbpUzkk27l6FTctfCX/l tGLbA0dL2k/lBS9VD7iv7HRs62wZAct6jlqrYu7GXWlJn886CL6bMqs3NvLSz9lTApbtzFi1 XHrmscybzJeUWIozEg21mIuKEwEEqO7khQIAAA==
Cc: "draft-housley-ltans-oids.all@tools.ietf.org" <draft-housley-ltans-oids.all@tools.ietf.org>
Subject: [Gen-art] FW:  Gen-ART Review of draft-housley-ltans-oids-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 02:22:57 -0000

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

Re-sending=85


Regards,

Wassim H.


From: Wassim Haddad <Wassim.Haddad@ericsson.com<mailto:Wassim.Haddad@ericss=
on.com>>
Date: Tuesday, August 13, 2013 9:09 AM
To: "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:ge=
n-art@ietf.org>>
Cc: Wassim Haddad <Wassim.Haddad@ericsson.com<mailto:Wassim.Haddad@ericsson=
.com>>, "housley-ltans-oids.all@tools.ietf.org<mailto:housley-ltans-oids.al=
l@tools.ietf.org>" <housley-ltans-oids.all@tools.ietf.org<mailto:housley-lt=
ans-oids.all@tools.ietf.org>>
Subject: [Gen-art] Gen-ART Review of draft-housley-ltans-oids-01


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/GenArt=
faq>

Document: draft-housley-ltans-oids-01
Reviewer:  Wassim Haddad
Review Date: 13 August 2013
IETF LC End Date: 31 July 2013
IETF Telechat Date: 15 August 2013

Summary:  This draft is ready for publication as an informational RFC

- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.


--_000_2887062F9ADE75448F0F3A2780C21B621C6768EDeusaamb103erics_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <ADE2ADB63EAD3242B05526D59C64C401@ericsson.com>
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-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>
<div>Re-sending=85</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>Regards,</div>
<div><br>
</div>
<div>Wassim H.</div>
<div><br>
</div>
</div>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Wassim Haddad &lt;<a href=3D"=
mailto:Wassim.Haddad@ericsson.com">Wassim.Haddad@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, August 13, 2013 9:09=
 AM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:gen-art=
@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a href=3D"mailto:gen-art@ietf.or=
g">gen-art@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>Wassim Haddad &lt;<a href=3D"ma=
ilto:Wassim.Haddad@ericsson.com">Wassim.Haddad@ericsson.com</a>&gt;, &quot;=
<a href=3D"mailto:housley-ltans-oids.all@tools.ietf.org">housley-ltans-oids=
.all@tools.ietf.org</a>&quot; &lt;<a href=3D"mailto:housley-ltans-oids.all@=
tools.ietf.org">housley-ltans-oids.all@tools.ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[Gen-art] Gen-ART Review o=
f draft-housley-ltans-oids-01<br>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif; ">
<div>
<div>
<div>
<pre style=3D"word-wrap: break-word; white-space: pre-wrap; "><div style=3D=
"white-space: normal; "><font face=3D"Calibri">I am the assigned Gen-ART re=
viewer for this draft. For background on Gen-ART,&nbsp;<br>please see the F=
AQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfa=
q">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;<br><br>D=
ocument:&nbsp;draft-housley-ltans-oids-01<br>Reviewer: &nbsp;Wassim Haddad<=
br>Review Date: 13 August 2013<br>IETF LC End Date: 31 July 2013<br>IETF Te=
lechat Date: 15 August 2013<br><br>Summary: &nbsp;This draft is ready for p=
ublication as an informational RFC</font></div><div style=3D"white-space: n=
ormal; "><font face=3D"Calibri"><br></font></div><div style=3D"white-space:=
 normal; "><font face=3D"Calibri">- Major Issues: None<br><br>- Minor Issue=
s: None<br></font></div><div style=3D"white-space: normal; "><font face=3D"=
Calibri"><br></font></div></pre>
</div>
<div style=3D"font-family: Calibri, sans-serif; ">
<div>Regards,</div>
<div><br>
</div>
<div>Wassim H.</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>

--_000_2887062F9ADE75448F0F3A2780C21B621C6768EDeusaamb103erics_--

From suresh.krishnan@ericsson.com  Mon Aug 12 21:41:30 2013
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 832F421E80AC for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 21:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4nu4DfgC3LkH for <gen-art@ietfa.amsl.com>; Mon, 12 Aug 2013 21:41:25 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 59AA521E80AF for <gen-art@ietf.org>; Mon, 12 Aug 2013 21:41:23 -0700 (PDT)
X-AuditID: c6180641-b7f986d000007a82-71-5209b8f1ffd2
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 02.92.31362.2F8B9025; Tue, 13 Aug 2013 06:41:22 +0200 (CEST)
Received: from [164.48.125.13] (147.117.188.135) by smtps-am.internal.ericsson.com (147.117.188.78) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 13 Aug 2013 00:41:21 -0400
Message-ID: <5209B84B.3090001@ericsson.com>
Date: Tue, 13 Aug 2013 00:38:35 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: <draft-ietf-lwig-terminology.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [147.117.188.135]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJJMWRmVeSWpSXmKPExsUyuXSPn+6nHZxBBu3NYhbtLX0sFldffWZx YPJYsuQnk8eXy5/ZApiiuGxSUnMyy1KL9O0SuDKazuxmLljOW3F80hmmBsYrXF2MnBwSAiYS E5Y0M0HYYhIX7q1n62Lk4hASOMoo8e7na3YIZzujxOFrE9hAqngFtCWeds1jBrFZBFQl7q6+ xAJiswFN2rDzM9gkUYEwifvnDjFB1AtKnJz5BKxGRCBZ4uPjVWC9wgJuEnf2nGaD2CwpsW3R MXYQm1lAT2LK1RZGCFteYvvbOWD1QgKaElvXfGftYuQAqleW2DEjcQKjwCwkG2Yh6Z6FpHsB I/MqRo7S4tSy3HQjw02MwOA7JsHmuINxwSfLQ4zSHCxK4rwb9M4ECgmkJ5akZqemFqQWxReV 5qQWH2Jk4uCUamBMSc8r5UnsvbeoufPFvHlrFQt1lv7MjD3/5sIU9xPHAybEPFv/y6xLIthP ZKtYCd9eOakaRlWOg2IdD45Y8Ktr109V4jWwceuve3X2dk9+iUCUgP5bo2mPW76b8J9n09Of VJZ+yGenktws/+aOxEi+mw0lk4IW7zqolGQ5rXFizpV5ZY2OckosxRmJhlrMRcWJAIeSrq8M AgAA
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-lwig-terminology-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 04:41:30 -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-lwig-terminology-05.txt
Reviewer: Suresh Krishnan
Review Date: 2013/08/12
IESG Telechat date: 2013/08/15

Summary: This draft is ready for publication as an Informational RFC but
I do have a few comments that the authors may wish to consider.

Minor
=====

* Section 1

Aren't actuators also one class of constrained devices? The section
talks about gathering information but does not talk about constrained
devices acting on information.

* Section 2.1

When speaking about the multiple facets of constraints on the nodes
shouldn't processing power be included as well? There is an item for
power but it is unclear if that means energy/power or processing power.
In either case one of them probably needs to be added.

* Section 2.2

Would it be worth mentioning the asymmetric nature of some of these link
as a constraint?

* Section 2.3.1

This sentence does not read right. Suggest rewording.

OLD:
In its terminology document, the ROLL working group is saying
[I-D.ietf-roll-terminology]:

NEW:
The ROLL terminology document [I-D.ietf-roll-terminology] defines LLNs
as follows:


* Section 3

Please add a reference to the CoAP draft at first use of CoAP.


* Section 4.3

Should this section also talk a bit about the term "duty cycle" since
this term is used frequently in the constrained device context?

Thanks
Suresh




From cabo@tzi.org  Tue Aug 13 07:06:44 2013
Return-Path: <cabo@tzi.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B772321E8144; Tue, 13 Aug 2013 07:06:38 -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_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id guUZ88RDRVgE; Tue, 13 Aug 2013 07:06:32 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id E88AE21E8123; Tue, 13 Aug 2013 07:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7DE6QK5020593; Tue, 13 Aug 2013 16:06:26 +0200 (CEST)
Received: from [192.168.217.105] (p5489267F.dip0.t-ipconnect.de [84.137.38.127]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C710648C; Tue, 13 Aug 2013 16:06:25 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A714199D03@xmb-rcd-x10.cisco.com>
Date: Tue, 13 Aug 2013 16:06:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <923B1D67-3325-418A-AFA8-FE1A7543B68D@tzi.org>
References: <A723FC6ECC552A4D8C8249D9E07425A714199D03@xmb-rcd-x10.cisco.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>, draft-bormann-cbor.all@tools.ietf.org
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 13 Aug 2013 14:06:45 -0000

On Aug 12, 2013, at 23:41, "Joe Hildebrand (jhildebr)" =
<jhildebr@cisco.com> wrote:

> Having more than one way to encode +/- Infinity seems like a recipe =
for
> generating slightly different canonical output.  For example, in my =
code
> right now, I think I'm always generating a half-precision Infinity, =
and
> I'm thinking about changing that to always be the 4-byte version.

Ah, got it.
Infinity/-Infinity are supposed to be covered by the float shortening =
rule
(which just doesn't work with NaNs).
We'll make that explicit.

Gr=FC=DFe, Carsten


From jari.arkko@piuha.net  Tue Aug 13 12:06:59 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8297121E819B; Tue, 13 Aug 2013 12:06:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VCSG0zwi-Gpp; Tue, 13 Aug 2013 12:06:54 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id F0A6321E8182; Tue, 13 Aug 2013 12:06:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5474D2CC48; Tue, 13 Aug 2013 22:06:52 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dNMQpgcndOya; Tue, 13 Aug 2013 22:06:51 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 56AE62CC5B; Tue, 13 Aug 2013 22:06:46 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com>
Date: Wed, 14 Aug 2013 03:06:45 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D641C7D-768F-4FB0-8DFC-D2C247E0F63A@piuha.net>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Cc: "Sam Hartman \(hartmans@painless-security.com\)" <hartmans@painless-security.com>, "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "stbryant@cisco.com" <stbryant@cisco.com>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 19:06:59 -0000

Thank you for your review, David. The Gen-ART reviews are important =
feedback for me to understand where I should look more closely.=20

In this case your review caused me to read the draft in detail, and I =
now have similar question as you did. I have raised a Discuss in my IESG =
ballot so that we can talk about those issues with the authors. In =
particular, it would be useful to discuss whether FCFS or some other =
assignment policy is most appropriate for the algorithm ID and KDF =
registries. I too thought Expert Review would have been a more natural =
fit. But I do not mind another policy, as long as we have a good reason =
for picking it. Secondly, I too was wondering what the relationship of =
this database is to the PAD.

Jari


From jari.arkko@piuha.net  Tue Aug 13 12:26:46 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFF7F21F9D04 for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 12:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.134
X-Spam-Level: 
X-Spam-Status: No, score=-102.134 tagged_above=-999 required=5 tests=[AWL=0.465, 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 gxqSVkQ4-9lr for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 12:26:40 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 2461C21E8188 for <gen-art@ietf.org>; Tue, 13 Aug 2013 12:26:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 68EF72CC5B; Tue, 13 Aug 2013 22:26:37 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IyFl2Bl13_E7; Tue, 13 Aug 2013 22:26:36 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E051A2CC48; Tue, 13 Aug 2013 22:26:33 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBC5269@GLKXM0002V.GREENLNK.net>
Date: Wed, 14 Aug 2013 03:26:31 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D08D48E-252B-4DED-9B12-5D79EC10D4FF@piuha.net>
References: <878D10B0-A968-46C8-8520-2C9F2E7A55C5@ericsson.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBC5269@GLKXM0002V.GREENLNK.net>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-manet-nhdp-olsrv2-sec.all@tools.ietf.org" <draft-ietf-manet-nhdp-olsrv2-sec.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-manet-nhdp-olsrv2-sec-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, 13 Aug 2013 19:26:46 -0000

Wassim: Thank you for your review. I'm placing a "No-Objection" ballot =
based on this review.

Jari

On Aug 6, 2013, at 5:03 PM, "Dearlove, Christopher (UK)" =
<chris.dearlove@baesystems.com> wrote:

> Wassim
> =20
> Thank you for that,
> =20
> Christopher
> =20
> --
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>=20
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace =
Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
> =20
> From: Wassim Haddad [mailto:wassim.haddad@ericsson.com]=20
> Sent: 05 August 2013 23:59
> To: gen-art@ietf.org
> Cc: Wassim Haddad; draft-ietf-manet-nhdp-olsrv2-sec.all@tools.ietf.org
> Subject: [Gen-art] Gen-ART Review of =
draft-ietf-manet-nhdp-olsrv2-sec-03
> =20
> =20
> *** WARNING ***
> This message originates from outside our organisation, either from an =
external partner or the internet.
> Keep this in mind if you answer this message.
> For information regarding Red Flags that you can look out for in =
emails you receive, click here.
> If you feel the email is suspicious, please follow this process.
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART,=20
> please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Document: draft-ietf-manet-nhdp-olsrv2-sec-03
> Reviewer:  Wassim Haddad
> Review Date: 05 August 2013
> IETF LC End Date: 02 August 2013
> IETF Telechat Date: 15 August 2013
>=20
> Summary:  This draft is ready for publication as proposed standard=20
> =20
> - Major Issues: None
>=20
> - Minor Issues: None
>=20
>=20
> Regards,
>=20
> Wassim H.
> =20
> =20
> =20
> =20
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Aug 13 12:31:39 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2484B21E80C3 for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 12:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level: 
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=0.310, 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 PVWn+Jf0P8jr for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 12:31:35 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D9A0911E81B2 for <gen-art@ietf.org>; Tue, 13 Aug 2013 12:31:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 96E152CC5B; Tue, 13 Aug 2013 22:31:26 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fcNOB42byC86; Tue, 13 Aug 2013 22:31:24 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 49F592CC48; Tue, 13 Aug 2013 22:31:21 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A5E687C@eusaamb107.ericsson.se>
Date: Wed, 14 Aug 2013 03:31:20 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD1B475C-CF7E-444D-BAE3-9B358AA97D8E@piuha.net>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A5D6541@eusaamb107.ericsson.se> <A95B4818FD85874D8F16607F1AC7C628DB480F@xmb-rcd-x09.cisco.com> <ABCAA4EF18F17B4FB619EA93DEF7939A5E687C@eusaamb107.ericsson.se>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org" <draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org>, "Joseph Salowey \(jsalowey\)" <jsalowey@cisco.com>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-method-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 19:31:39 -0000

Meral: thank you very much for your review. Joe: are the comments going =
to be addressed in a new version?

Jari

On Aug 10, 2013, at 7:23 AM, Meral Shirazipour =
<meral.shirazipour@ericsson.com> wrote:

> Hi Joe,
>    Thank you for the answer. Fine with me, if the document shepherd or =
AD approve, I would still suggest adding a comment in the abstract or =
intro mentioning that RFC4851 text is reused.
> =20
> Best,
> Meral
> =20
> From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com]=20
> Sent: Friday, August 09, 2013 15:55
> To: Meral Shirazipour
> Cc: draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org; =
gen-art@ietf.org
> Subject: Re: Gen-ART Last Call review of =
draft-ietf-emu-eap-tunnel-method-07
> =20
> Hi Meral,
> =20
> Thanks for your review, comments inline below. =20
> =20
> Cheers,
> =20
> Joe
> On Jul 30, 2013, at 2:47 PM, Meral Shirazipour =
<meral.shirazipour@ericsson.com> wrote:
>=20
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ =
athttp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq  .
> =20
> Please resolve these comments along with any other Last Call comments =
you may receive.
> =20
> Document: draft-ietf-emu-eap-tunnel-method-07
> Reviewer: Meral Shirazipour
> Review Date: 2013-07-30
> IETF LC End Date: 2013-07-30
> IESG Telechat date: NA
> =20
> =20
> Summary:
> This draft is almost ready to be published as Standards Track RFC but =
I have some comments.
> =20
> =20
> Nits/editorial comments:
> Many sections of the document are a direct copy paste of =
RFC4851(EAP-FAST) with a minor change: "EAP-FAST"->"TEAP".
> Since RFC4851 is mentioned as being well adopted, is there a reason =
why it has not been used as reference point and then only mention the =
diffs in more detail? (for the sections concerned).
> Appendix B is useful, but the above suggestion could have made the =
document a lot shorter and easier to understand by people already =
familiar with EAP-FAST.
> Unless this draft is to replace RFC4851? In which case the abstract =
should mention this.
> e.g.
> [Page 20], Section 3.7 Fragmentation, is a copy of RFC4851's Section =
3.7 with "EAP-FAST"->"TEAP".
> Why not use RFC4851's Fragmentation proposal as a reference point and =
just mention what is different (e.g. nothing but the EAP-Type in this =
case).
> =20
> =20
> =20
> [Joe] RFC 4851 is informational and making normative reference to it =
would be a downref.  We felt it would be better to include the complete =
text in the standards track document and remove any normative dependency =
on the information document. =20
> =20
>=20
>=20
> Nits:
> [Page 6], Section 1.2, reference [RFC5077] appears twice.
> [Page 21], section 3.8, paragraph 2, "which the the =
peer"--typo-->remove extra "the"
> [Page 24], Section 3.8.4, paragraph 2, =
"succ;essfully"--typo-->"successfully"
> [Page 56], line 3, "Note: Peer's are"---->"Peers"
> [Page 73], Section 7.6, "is remoted"--typo-->"is remote"
> =20
> =20
> [Joe] OK
> =20
>=20
>=20
> =20
> Best Regards,
> Meral
> ---
> Meral Shirazipour
> Ericsson
> Research
> www.ericsson.com
> =20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Aug 13 12:52:35 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4434711E81A8 for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 12:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.367
X-Spam-Level: 
X-Spam-Status: No, score=-102.367 tagged_above=-999 required=5 tests=[AWL=0.232, 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 gZMKQLl4iUqv for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 12:52:31 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 651C011E817E for <gen-art@ietf.org>; Tue, 13 Aug 2013 12:52:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 52BF62CC5B; Tue, 13 Aug 2013 22:52:29 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YqTH2CQ5f8Rb; Tue, 13 Aug 2013 22:52:25 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 652FF2CC48; Tue, 13 Aug 2013 22:52:23 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5207F83D.9010207@gondrom.org>
Date: Wed, 14 Aug 2013 03:52:20 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <00E6E44C-78D7-4FEA-A540-72AFA12E0D81@piuha.net>
References: <5203F8C2.3060807@nostrum.com> <5207F83D.9010207@gondrom.org>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
X-Mailer: Apple Mail (2.1508)
Cc: draft-ietf-websec-x-frame-options@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Genart LC review: draft-ietf-websec-x-frame-options-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 19:52:35 -0000

Robert: Thank you very much for your review. This has been very helpful. =
Tobias: Thank you for the changes.

(I can see that there could be some discussion about some of the =
remaining text changes. Do you Robert think the remaining points are =
important enough to warrant me raising them in the IESG discussion? For =
now I have filed a No-Objection position.)

Jari

On Aug 12, 2013, at 4:46 AM, Tobias Gondrom <tobias.gondrom@gondrom.org> =
wrote:

> Dear Robert,
>=20
> thank you very much for the review.
> I revised the document to version-08 (also including feedback from =
other
> reviews) accordingly including most of your feedback.
> Answers inline.
> Best regards, Tobias
>=20
>=20
> On 08/08/13 21:00, Robert Sparks wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>=20
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document: draft-ietf-websec-x-frame-options-07
>> Reviewer: Robert Sparks
>> Review Date: 2013-08-08
>> IETF LC End Date: 2013-08-12
>> IESG Telechat date: 2013-08-15
>>=20
>> Summary: This draft is basically ready for publication, but has nits
>> that should be fixed before publication.
>>=20
>> This document is intended to act as a informational reference
>> describing what's already deployed, and not to act as a standard for
>> new implementations to follow. It's obvious that some care has been
>> taken to keep that tone in the text, but there are places where it
>> still looks like a proposed standard. Please make it even more clear
>> who the audience for this document is, and look for places to
>> reinforce that this is documenting what _is_, as opposed to trying to
>> influence what should be.
>>=20
>> The introduction of this version of the document does a good job of
>> describing what a clickjack attack is. Appendix B is not really =
adding
>> to that description. I suggest that the two usecases it call out be
>> reduced to a couple of sentences in the introduction as examples, and
>> a reference to a more in-depth treatment of scenarios like them be
>> added for those looking for more information. Section B.3 is
>> different, and doesn't add to the understanding of this document.
>> Again, I suggest pointing to somewhere else that provides an in-depth
>> treatment. (Hopefully, that source would discuss the nested frame
>> issue the security considerations section points out in the context =
of
>> the this specific configuration page). [FRAME-BUSTING] might be
>> enough, but pointers to something even more rich would certainly be
>> helpful.
>=20
> Apologies, but I would rather keep the three example cases in the
> appendix of the document as this will allow better understanding of =
the
> document if references are no longer available. Consider that
> clickjacking  description references are not IETF, nor other SDOs and
> potentially not stable over the full lifecycle of the RFC.
>=20
>=20
>=20
>>=20
>> Here are some suggestions in document order:
>>=20
>> In the Abstract, I suggest replace "specification" with either
>> "definition" as the introduction uses, or with "the syntax and
>> behavior observed in current deployments".
> Ok. changed to "definition".
>=20
>=20
>>=20
>> The last paragraph of the introduction reads like standards text.
>> Please consider rewriting it with a tone of history and current fact.
>> Perhaps starting with "In existing implementations, ", and replacing
>> the last sentence with something like "The policy this HTTP header
>> declares is enforced by the browser implementations documented here".
>=20
> Changed accordingly.
> Please note: IMHO I did not feel that the last paragraph of the
> introduction reads like standards text. However, I appreciate your
> feedback and did modify the last sentence of the last paragraph of the
> introduction accordingly to remove the word "conforming".
> (I believe the remaining text describes sufficiently that this is
> documentation. So I did not want to rewrite the whole paragraph and =
add
> history.)
>=20
>=20
>> Since this is documenting an existing deployed header (not
>> standardizing it), it would be useful to comment whether the existing
>> known implementations allow all the productions of the ABNF described
>> here to be used. For instance, would they all honor X-FRAME-OPTIONS:
>> deny? (While thinking about this, focus on who this document is for.)
>=20
> Please note, that section 2.3.2.2. describes the variation in =
behaviour
> between different browsers.
> As existing browser implementations may change with regards to whether
> they allow _all_ the productions of the ABNF, we intentionally did not
> investigate and document all possible outcomes and combinations.
>=20
>>=20
>> The last sentence of 2.3.1 as written is an attempt to be a standard,
>> and is an odd use of 2119. I suggest rewriting it as a warning about
>> what happens with existing plugins that ignore the policy carrid in
>> the header. That keeps the message aligned with documenting what =
exists.
>=20
> Ok. I changed it to non-2119.
> However, the remaining text is appropriate and adds clarity to declare
> the scope of the x-frame-options header effects. And implementations =
and
> specifications of x-frame-options out there consider it as part that
> plug-ins observe x-frame-options if "these plugins appear essentially =
as
> frames".
> Please consider that a plug-in that would "essentially appear as a
> frame" but would not be observing x-frame-options would in effect =
break
> the security model of the browser implementation, so I think the
> remaining text is appropriate and needed in this case.
>=20
>=20
>>=20
>> The first sentence of 2.3.2 is not adding anything to the document. I
>> suggest deleting it. The second sentence is placing an implementation
>> requirement again. Please consider rewriting as an observation of =
what
>> existing things do, calling out the ramifications of the ones that
>> behave differently.
>=20
> Please consider that even though this is to document existing use
> (especially until we get CSP1.1), it's documentation can also help =
guide
> new implementations for the purpose to reduce or avoid divergence of
> implementations. This leads to the first sentence and also to the use =
of
> "MAY" in the second sentence, which in fact is not a requirement of =
the
> browser implementation but points out an implementation option.
>=20
>>=20
>> Similarly, the first paragraphs of Section 2.3.2.1 is written to
>> affect new implementation, not document existing implementation. They
>> could be re-tuned as above. The third paragraph is good history
>=20
> As the comment before, this documentation also helps to reduce or =
avoid
> divergence of implementations. So the "SHOULD" is appropriate and as
> intended here.
>=20
>=20
>>=20
>> The last sentence of 2.3.2.2 should not say "replace this document" -
>> this document is informational documentation about existing
>> deployments. CSP1.1 won't Obsolete or Replace this document. Rather =
it
>> should say something like "it is expected that newer implementations
>> will use it rather than the mechanisms documented here".
>=20
> Ok. Changed accordingly.
>=20
>>=20
>> Nit: s/does support only one/only supports one/
> Ok. Changed.
>>=20
>> Do the known implementations follow the pattern described in 2.3.2.3?
>> Saying something would help tie this to being information about the
>> known deployment rather than trying to constrain new development.
>=20
> Hm. First, as outlined in 2.3.2.2 not all of the browsers support
> "Allow-From". And second, the pattern is actually not for the browser
> but a way for the server to achieve the specific goal (i.e. of a =
source
> page being framed by more than one web page, even though allow-from
> supports only on URI).
> To accomodate your feedback and make clear this is not trying to
> contrain new development, I changed the word "is recommended" to "can
> fulfill that need".
>=20
>>=20
>> Nit: If Appendix B is kept, please expand CSRF (and consider
>> re-pointing to a reference)
>>=20
> Ok. Done.
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Aug 13 13:40:42 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C093621F9ED4 for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 13:40:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, 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 pBPbu6GgmuG7 for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 13:40:37 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 29AF321F9E6D for <gen-art@ietf.org>; Tue, 13 Aug 2013 13:40:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 728C32CC48; Tue, 13 Aug 2013 23:40:36 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1PyLM-M53BPB; Tue, 13 Aug 2013 23:40:35 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 50D002CC5B; Tue, 13 Aug 2013 23:40:32 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <2887062F9ADE75448F0F3A2780C21B621C6768ED@eusaamb103.ericsson.se>
Date: Wed, 14 Aug 2013 04:40:28 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD5331C4-6A8C-4321-B406-CAA4395D044B@piuha.net>
References: <2887062F9ADE75448F0F3A2780C21B621C6768ED@eusaamb103.ericsson.se>
To: Wassim Haddad <wassim.haddad@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-housley-ltans-oids.all@tools.ietf.org" <draft-housley-ltans-oids.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Review of draft-housley-ltans-oids-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 20:40:43 -0000

Thank you very much your review, Wassim!

Jari

On Aug 13, 2013, at 10:22 AM, Wassim Haddad <wassim.haddad@ericsson.com> =
wrote:

> Re-sending=85
>=20
>=20
> Regards,
>=20
> Wassim H.
>=20
>=20
> From: Wassim Haddad <Wassim.Haddad@ericsson.com>
> Date: Tuesday, August 13, 2013 9:09 AM
> To: "gen-art@ietf.org" <gen-art@ietf.org>
> Cc: Wassim Haddad <Wassim.Haddad@ericsson.com>, =
"housley-ltans-oids.all@tools.ietf.org" =
<housley-ltans-oids.all@tools.ietf.org>
> Subject: [Gen-art] Gen-ART Review of draft-housley-ltans-oids-01
>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART,=20
>> please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>=20
>> Document: draft-housley-ltans-oids-01
>> Reviewer:  Wassim Haddad
>> Review Date: 13 August 2013
>> IETF LC End Date: 31 July 2013
>> IETF Telechat Date: 15 August 2013
>>=20
>> Summary:  This draft is ready for publication as an informational RFC
>>=20
>> - Major Issues: None
>>=20
>> - Minor Issues: None
>>=20
>> Regards,
>>=20
>> Wassim H.
>>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jsalowey@cisco.com  Tue Aug 13 14:14:57 2013
Return-Path: <jsalowey@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 7660521F9E5A for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 14:14:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XjLPsMKdqOl for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 14:14:49 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id ED77521F8FB4 for <gen-art@ietf.org>; Tue, 13 Aug 2013 14:14:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3535; q=dns/txt; s=iport; t=1376428457; x=1377638057; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=fGIT5ykOorfuDJOjXiXhC7/+mVPU6VrTAPyBh+I+OK4=; b=OMnrM8dN87hI3D1YTzAm1uCsl1kQbrlJoqmtHUAHuMem7IG8J/u6PK2h c2EX1/Afo6uWn+40MjfGYaS+mpyMaTiwZQ+hvl7SzMjkqCuyijtgBp/OG xYkK+J3duUNfyaaB8HrvH1shbJfXorA6RvcT855k6sp315saeVQxgpP9x A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4FAL6gClKtJV2c/2dsb2JhbABbgwY1UKp0k2yBJBZ0giQBAQEDAQEBASQTDyULBQsCAQgRAwEBAQEKFAkHJwsUCQgBAQQOBQiIAgYMuCuQCQIxB4MbdgOZEZAkgxuCKg
X-IronPort-AV: E=Sophos;i="4.89,872,1367971200"; d="scan'208";a="246929378"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 13 Aug 2013 21:14:16 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r7DLEGA4013432 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 13 Aug 2013 21:14:16 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.187]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Tue, 13 Aug 2013 16:14:16 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>
Thread-Topic: [Gen-art] Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-method-07
Thread-Index: Ac6NbJMxWaq0WGIaSDy4raLO8rZmygIEMVmAAAmhttAAuG5QAAADmCaA
Date: Tue, 13 Aug 2013 21:14:16 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628DC8E01@xmb-aln-x09.cisco.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A5D6541@eusaamb107.ericsson.se> <A95B4818FD85874D8F16607F1AC7C628DB480F@xmb-rcd-x09.cisco.com> <ABCAA4EF18F17B4FB619EA93DEF7939A5E687C@eusaamb107.ericsson.se> <AD1B475C-CF7E-444D-BAE3-9B358AA97D8E@piuha.net>
In-Reply-To: <AD1B475C-CF7E-444D-BAE3-9B358AA97D8E@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.33.248.54]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <37FFFAEEBFDCA443A5BD0BF9530EE9D5@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org" <draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-method-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 21:14:57 -0000

Yes.=20
On Aug 13, 2013, at 12:31 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> Meral: thank you very much for your review. Joe: are the comments going t=
o be addressed in a new version?
>=20
> Jari
>=20
> On Aug 10, 2013, at 7:23 AM, Meral Shirazipour <meral.shirazipour@ericsso=
n.com> wrote:
>=20
>> Hi Joe,
>>   Thank you for the answer. Fine with me, if the document shepherd or AD=
 approve, I would still suggest adding a comment in the abstract or intro m=
entioning that RFC4851 text is reused.
>>=20
>> Best,
>> Meral
>>=20
>> From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com]=20
>> Sent: Friday, August 09, 2013 15:55
>> To: Meral Shirazipour
>> Cc: draft-ietf-emu-eap-tunnel-method.all@tools.ietf.org; gen-art@ietf.or=
g
>> Subject: Re: Gen-ART Last Call review of draft-ietf-emu-eap-tunnel-metho=
d-07
>>=20
>> Hi Meral,
>>=20
>> Thanks for your review, comments inline below. =20
>>=20
>> Cheers,
>>=20
>> Joe
>> On Jul 30, 2013, at 2:47 PM, Meral Shirazipour <meral.shirazipour@ericss=
on.com> wrote:
>>=20
>>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on Gen=
-ART, please see the FAQ athttp://wiki.tools.ietf.org/area/gen/trac/wiki/Ge=
nArtfaq  .
>>=20
>> Please resolve these comments along with any other Last Call comments yo=
u may receive.
>>=20
>> Document: draft-ietf-emu-eap-tunnel-method-07
>> Reviewer: Meral Shirazipour
>> Review Date: 2013-07-30
>> IETF LC End Date: 2013-07-30
>> IESG Telechat date: NA
>>=20
>>=20
>> Summary:
>> This draft is almost ready to be published as Standards Track RFC but I =
have some comments.
>>=20
>>=20
>> Nits/editorial comments:
>> Many sections of the document are a direct copy paste of RFC4851(EAP-FAS=
T) with a minor change: "EAP-FAST"->"TEAP".
>> Since RFC4851 is mentioned as being well adopted, is there a reason why =
it has not been used as reference point and then only mention the diffs in =
more detail? (for the sections concerned).
>> Appendix B is useful, but the above suggestion could have made the docum=
ent a lot shorter and easier to understand by people already familiar with =
EAP-FAST.
>> Unless this draft is to replace RFC4851? In which case the abstract shou=
ld mention this.
>> e.g.
>> [Page 20], Section 3.7 Fragmentation, is a copy of RFC4851's Section 3.7=
 with "EAP-FAST"->"TEAP".
>> Why not use RFC4851's Fragmentation proposal as a reference point and ju=
st mention what is different (e.g. nothing but the EAP-Type in this case).
>>=20
>>=20
>>=20
>> [Joe] RFC 4851 is informational and making normative reference to it wou=
ld be a downref.  We felt it would be better to include the complete text i=
n the standards track document and remove any normative dependency on the i=
nformation document. =20
>>=20
>>=20
>>=20
>> Nits:
>> [Page 6], Section 1.2, reference [RFC5077] appears twice.
>> [Page 21], section 3.8, paragraph 2, "which the the peer"--typo-->remove=
 extra "the"
>> [Page 24], Section 3.8.4, paragraph 2, "succ;essfully"--typo-->"successf=
ully"
>> [Page 56], line 3, "Note: Peer's are"---->"Peers"
>> [Page 73], Section 7.6, "is remoted"--typo-->"is remote"
>>=20
>>=20
>> [Joe] OK
>>=20
>>=20
>>=20
>>=20
>> Best Regards,
>> Meral
>> ---
>> Meral Shirazipour
>> Ericsson
>> Research
>> www.ericsson.com
>>=20
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20


From rjsparks@nostrum.com  Tue Aug 13 14:34:40 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 307EA21F8F4A; Tue, 13 Aug 2013 14:34:40 -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 izCVaDFEO-8U; Tue, 13 Aug 2013 14:34:39 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2173121F8D90; Tue, 13 Aug 2013 14:34:36 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7DLYTHx015954 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Tue, 13 Aug 2013 16:34:29 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <520AA664.2080208@nostrum.com>
Date: Tue, 13 Aug 2013 16:34:28 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <5203F8C2.3060807@nostrum.com> <5207F83D.9010207@gondrom.org> <00E6E44C-78D7-4FEA-A540-72AFA12E0D81@piuha.net>
In-Reply-To: <00E6E44C-78D7-4FEA-A540-72AFA12E0D81@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Cc: Tobias Gondrom <tobias.gondrom@gondrom.org>, draft-ietf-websec-x-frame-options@tools.ietf.org, gen-art@ietf.org, websec@ietf.org
Subject: Re: [Gen-art] Genart LC review: draft-ietf-websec-x-frame-options-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 21:34:40 -0000

Copying websec at Barry's request:

On 8/13/13 2:52 PM, Jari Arkko wrote:
> Robert: Thank you very much for your review. This has been very helpful. Tobias: Thank you for the changes.
>
> (I can see that there could be some discussion about some of the remaining text changes. Do you Robert think the remaining points are important enough to warrant me raising them in the IESG discussion? For now I have filed a No-Objection position.)
Thanks for the nudge Jari. I've continued the conversation below.
I would still like to see some adjustment of the character of the text, 
but if I were a balloting AD, I would be putting in comments, not discusses.

Tobias - Thanks for your changes so far. I appreciate that some of what 
I'm pushing for may seem subtle.

I've had to handle several documents that might have been 
standardization fodder at some point in time but for various reasons 
turned out not to be.
The resulting documentation of some of those came out looking to me like 
a standards document with an Informational or Independent Submission label
taped to the top. You've done a good job of avoiding that with this 
document, and the changes I'm pushing for are to make that aspect even 
better (I hope). Thank you (and the WG) for considering them.
>
> Jari
>
> On Aug 12, 2013, at 4:46 AM, Tobias Gondrom <tobias.gondrom@gondrom.org> wrote:
>
>> Dear Robert,
>>
>> thank you very much for the review.
>> I revised the document to version-08 (also including feedback from other
>> reviews) accordingly including most of your feedback.
>> Answers inline.
>> Best regards, Tobias
>>
>>
>> On 08/08/13 21:00, Robert Sparks 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-websec-x-frame-options-07
>>> Reviewer: Robert Sparks
>>> Review Date: 2013-08-08
>>> IETF LC End Date: 2013-08-12
>>> IESG Telechat date: 2013-08-15
>>>
>>> Summary: This draft is basically ready for publication, but has nits
>>> that should be fixed before publication.
>>>
>>> This document is intended to act as a informational reference
>>> describing what's already deployed, and not to act as a standard for
>>> new implementations to follow. It's obvious that some care has been
>>> taken to keep that tone in the text, but there are places where it
>>> still looks like a proposed standard. Please make it even more clear
>>> who the audience for this document is, and look for places to
>>> reinforce that this is documenting what _is_, as opposed to trying to
>>> influence what should be.
>>>
>>> The introduction of this version of the document does a good job of
>>> describing what a clickjack attack is. Appendix B is not really adding
>>> to that description. I suggest that the two usecases it call out be
>>> reduced to a couple of sentences in the introduction as examples, and
>>> a reference to a more in-depth treatment of scenarios like them be
>>> added for those looking for more information. Section B.3 is
>>> different, and doesn't add to the understanding of this document.
>>> Again, I suggest pointing to somewhere else that provides an in-depth
>>> treatment. (Hopefully, that source would discuss the nested frame
>>> issue the security considerations section points out in the context of
>>> the this specific configuration page). [FRAME-BUSTING] might be
>>> enough, but pointers to something even more rich would certainly be
>>> helpful.
>> Apologies, but I would rather keep the three example cases in the
>> appendix of the document as this will allow better understanding of the
>> document if references are no longer available.
I don't think they do, actually. If those references are gone, there is not
enough in this document, particularly in those appendices, to inform
someone who didn't already understand clickjacking. To state that more
strongly, I don't think you're helping the type of future reading you are
trying to help, and as a consequence, you may even add to their confusion.
I don't think adding more to this document is the right thing to do.
I really think you should point to references instead. If you don't 
trust the
ones you have to be stable for the period of time this document is needed
(which surprises me), then perhaps you should look for something more 
stable?

>>   Consider that
>> clickjacking  description references are not IETF, nor other SDOs and
>> potentially not stable over the full lifecycle of the RFC.
>>
>>
>>
>>> Here are some suggestions in document order:
>>>
>>> In the Abstract, I suggest replace "specification" with either
>>> "definition" as the introduction uses, or with "the syntax and
>>> behavior observed in current deployments".
>> Ok. changed to "definition".
I wasn't specific with which instance of specification I meant (I missed 
that there were two).
With the new text (-09), in this paragraph, I would say "this document 
describes" instead of
"this definition describes", and "definition of this X-Frame-Options" 
rather than "specification
of this X-Frame-Options".


>>
>>
>>> The last paragraph of the introduction reads like standards text.
>>> Please consider rewriting it with a tone of history and current fact.
>>> Perhaps starting with "In existing implementations, ", and replacing
>>> the last sentence with something like "The policy this HTTP header
>>> declares is enforced by the browser implementations documented here".
>> Changed accordingly.
>> Please note: IMHO I did not feel that the last paragraph of the
>> introduction reads like standards text. However, I appreciate your
>> feedback and did modify the last sentence of the last paragraph of the
>> introduction accordingly to remove the word "conforming".
>> (I believe the remaining text describes sufficiently that this is
>> documentation. So I did not want to rewrite the whole paragraph and add
>> history.)
Thanks for those edits, and the ones you call out below.

>>
>>
>>> Since this is documenting an existing deployed header (not
>>> standardizing it), it would be useful to comment whether the existing
>>> known implementations allow all the productions of the ABNF described
>>> here to be used. For instance, would they all honor X-FRAME-OPTIONS:
>>> deny? (While thinking about this, focus on who this document is for.)
>> Please note, that section 2.3.2.2. describes the variation in behaviour
>> between different browsers.
>> As existing browser implementations may change with regards to whether
>> they allow _all_ the productions of the ABNF, we intentionally did not
>> investigate and document all possible outcomes and combinations.
>>
>>> The last sentence of 2.3.1 as written is an attempt to be a standard,
>>> and is an odd use of 2119. I suggest rewriting it as a warning about
>>> what happens with existing plugins that ignore the policy carrid in
>>> the header. That keeps the message aligned with documenting what exists.
>> Ok. I changed it to non-2119.
>> However, the remaining text is appropriate and adds clarity to declare
>> the scope of the x-frame-options header effects. And implementations and
>> specifications of x-frame-options out there consider it as part that
>> plug-ins observe x-frame-options if "these plugins appear essentially as
>> frames".
>> Please consider that a plug-in that would "essentially appear as a
>> frame" but would not be observing x-frame-options would in effect break
>> the security model of the browser implementation, so I think the
>> remaining text is appropriate and needed in this case.
This takes you into talking about what new implementations should do, 
rather than documenting what's in the wild.
You can avoid that by noting that any existing plug-in implementations 
that don't do the right thing here create a problem.
(It would follow that any new ones would have that same problem).
>>
>>
>>> The first sentence of 2.3.2 is not adding anything to the document. I
>>> suggest deleting it. The second sentence is placing an implementation
>>> requirement again. Please consider rewriting as an observation of what
>>> existing things do, calling out the ramifications of the ones that
>>> behave differently.
>> Please consider that even though this is to document existing use
>> (especially until we get CSP1.1), it's documentation can also help guide
>> new implementations for the purpose to reduce or avoid divergence of
>> implementations.
You can have that influence by reporting on what is rather than trying 
to write constraints on new things.
>> This leads to the first sentence and also to the use of
>> "MAY" in the second sentence, which in fact is not a requirement of the
>> browser implementation but points out an implementation option.

>>
>>> Similarly, the first paragraphs of Section 2.3.2.1 is written to
>>> affect new implementation, not document existing implementation. They
>>> could be re-tuned as above. The third paragraph is good history
>> As the comment before, this documentation also helps to reduce or avoid
>> divergence of implementations. So the "SHOULD" is appropriate and as
>> intended here.
How about simply saying that any change or divergence to the 
implementations will result in (this list of bad things).
That's informative rather than trying to be normative.
>>
>>
>>> The last sentence of 2.3.2.2 should not say "replace this document" -
>>> this document is informational documentation about existing
>>> deployments. CSP1.1 won't Obsolete or Replace this document. Rather it
>>> should say something like "it is expected that newer implementations
>>> will use it rather than the mechanisms documented here".
>> Ok. Changed accordingly.
>>
>>> Nit: s/does support only one/only supports one/
>> Ok. Changed.
>>> Do the known implementations follow the pattern described in 2.3.2.3?
>>> Saying something would help tie this to being information about the
>>> known deployment rather than trying to constrain new development.
>> Hm. First, as outlined in 2.3.2.2 not all of the browsers support
>> "Allow-From". And second, the pattern is actually not for the browser
>> but a way for the server to achieve the specific goal (i.e. of a source
>> page being framed by more than one web page, even though allow-from
>> supports only on URI).
>> To accomodate your feedback and make clear this is not trying to
>> contrain new development, I changed the word "is recommended" to "can
>> fulfill that need".
>>
>>> Nit: If Appendix B is kept, please expand CSRF (and consider
>>> re-pointing to a reference)
>>>
>> Ok. Done.
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Aug 13 18:37:00 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84E6411E81D4 for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 18:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.528
X-Spam-Level: 
X-Spam-Status: No, score=-102.528 tagged_above=-999 required=5 tests=[AWL=0.072, 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 GKGibaXrfgnZ for <gen-art@ietfa.amsl.com>; Tue, 13 Aug 2013 18:36:56 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 903AA11E81D0 for <gen-art@ietf.org>; Tue, 13 Aug 2013 18:36:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5A4FF2CC48; Wed, 14 Aug 2013 04:36:53 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qyXqQqvmnR-z; Wed, 14 Aug 2013 04:36:52 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id F3BBF2CC44; Wed, 14 Aug 2013 04:36:50 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5209B84B.3090001@ericsson.com>
Date: Wed, 14 Aug 2013 09:36:48 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B8B33BF-6513-43A4-8D3C-2C9818E92488@piuha.net>
References: <5209B84B.3090001@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Cc: draft-ietf-lwig-terminology.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-lwig-terminology-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 01:37:00 -0000

Suresh: Thank you very much for your review. Carsten et al, I think =
Suresh raises some valid points here. I'll note the focus on other =
things besides sensors in particular.

Jari

On Aug 13, 2013, at 12:38 PM, Suresh Krishnan =
<suresh.krishnan@ericsson.com> wrote:

> I have been selected as the General Area Review Team (Gen-ART)
> reviewer for this draft (for background on Gen-ART, please see
> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-lwig-terminology-05.txt
> Reviewer: Suresh Krishnan
> Review Date: 2013/08/12
> IESG Telechat date: 2013/08/15
>=20
> Summary: This draft is ready for publication as an Informational RFC =
but
> I do have a few comments that the authors may wish to consider.
>=20
> Minor
> =3D=3D=3D=3D=3D
>=20
> * Section 1
>=20
> Aren't actuators also one class of constrained devices? The section
> talks about gathering information but does not talk about constrained
> devices acting on information.
>=20
> * Section 2.1
>=20
> When speaking about the multiple facets of constraints on the nodes
> shouldn't processing power be included as well? There is an item for
> power but it is unclear if that means energy/power or processing =
power.
> In either case one of them probably needs to be added.
>=20
> * Section 2.2
>=20
> Would it be worth mentioning the asymmetric nature of some of these =
link
> as a constraint?
>=20
> * Section 2.3.1
>=20
> This sentence does not read right. Suggest rewording.
>=20
> OLD:
> In its terminology document, the ROLL working group is saying
> [I-D.ietf-roll-terminology]:
>=20
> NEW:
> The ROLL terminology document [I-D.ietf-roll-terminology] defines LLNs
> as follows:
>=20
>=20
> * Section 3
>=20
> Please add a reference to the CoAP draft at first use of CoAP.
>=20
>=20
> * Section 4.3
>=20
> Should this section also talk a bit about the term "duty cycle" since
> this term is used frequently in the constrained device context?
>=20
> Thanks
> Suresh
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From hartmans@mit.edu  Wed Aug 14 12:19:21 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43AE911E81F0; Wed, 14 Aug 2013 12:19:21 -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 ZCuz8wprUAt7; Wed, 14 Aug 2013 12:19:15 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id D417411E81D3; Wed, 14 Aug 2013 12:19:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 5681420288; Wed, 14 Aug 2013 15:17:58 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ad05Q-xHOkXP; Wed, 14 Aug 2013 15:17:57 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Wed, 14 Aug 2013 15:17:57 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 0E4688051A; Wed, 14 Aug 2013 15:19:06 -0400 (EDT)
From: Sam Hartman <hartmans-ietfc@mit.edu>
Newsgroups: 
To: "Black\, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com>
Date: Wed, 14 Aug 2013 15:19:06 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> (David Black's message of "Fri, 9 Aug 2013 10:47:05 -0400")
Message-ID: <tslvc38cc7p.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Wed, 14 Aug 2013 12:24:42 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] [karp] IANA policy for draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 19:19:21 -0000

David, as we mentioned in the IESG thread, we seem to have dropped the
response to your comments about IANA actions.

WG:
>From the genart review:

[9] I suggest Expert Review for the new IANA registries, not just 
First Come First Served, so that someone with a security "clue" can
check that the proposed registrations are reasonable.


Stephen has filed a related DISCUSS position.  He's confused why we need
a registry for  KDFs or algorithms.
He argues that the protocols should already have such a registry.  He
argues that it would be non-sensical to register a value in this
registry but not the protocol registry.

In a somewhat related discussion, multiple people have asked what the
scope of this document is.  Are we defining something for routing
protocols?  Any security protocol in the world?  Something in-between?


IU'm going to make two responses:

1)
I think FCFS is not harmful for these registries.

David's main concern is that bad security will get registered.

I'll point out that these registries are not about what security you can
use with a routing protocol, but about what security you can configure
from a management standpoint.
Registering rot13 or similarly questionable security here wouldn't mean
I could use it with a routing protocol, only that I could ask a system
to do so.  If ROT13 was not actually in the security-specific registries
for the protocols in question there'd be no way to send a
rot13-transformed message.

I think people wanting to use bad security in routing protocols will
focus on specifying how to use the security for the protocols, and
that's the appropriate place to do any gateway review.
Yeah, I guess with FCFS it's possible someone could register here and
then later realize they cannot get their md4 security approved in the
actual protocol registry document.

That might be confusing but doesn't seem very harmful.

Also, some routing protocols are protected by cleartext passwords sent
over the network.  We want to be able to manage that, so we will be
registering plaintext password in these registries.
I don't think anyone will come up with anything worse than that.

Finally, I think a lot of us have begun to question the value in
security review for codepoint assignment.  Some security WGs care a lot;
some don't seem to care much at all.

2)  Why I prefer FCFS or at least would object strongly to expert
review.

If we're going to say we want expert review I want us to give  expert
instructions at least good enough that I believe I could answer the
question of what registrations to approve if I were appointed the
expert.

I don't think we could come to consensus on those instructions very
easily.
In particular, I think it would be challenging for us to describe what
security protocols the protocol registry applies to and which ones it
does not.

I'm totally fine publishing this document knowing it will be used for
routing protocols but not knowing what beyond routing protocols it will
be used for.
If we do that FCFS makes a lot of sense.

So, my recommendation is that we keep our current registration policy.

From hartmans@mit.edu  Wed Aug 14 12:31:58 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF3221E808C; Wed, 14 Aug 2013 12:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 8VZudT0fEjn7; Wed, 14 Aug 2013 12:31:53 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id DFCE921F99D0; Wed, 14 Aug 2013 12:31:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 9212A20280; Wed, 14 Aug 2013 15:30:41 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TLmALA9OwzD7; Wed, 14 Aug 2013 15:30:41 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Wed, 14 Aug 2013 15:30:41 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3D9D48051A; Wed, 14 Aug 2013 15:31:50 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com>
Date: Wed, 14 Aug 2013 15:31:50 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> (David Black's message of "Fri, 9 Aug 2013 10:47:05 -0400")
Message-ID: <tslr4dwcbmh.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 19:31:59 -0000

>>>>> "Black," == Black, David <david.black@emc.com> writes:


    Black,> [A] Overall - I would like to see a paragraph added on how
    Black,> this database conceptually relates to the IPsec Peer
    Black,> Authorization Database (PAD) - see RFC 4301, section 4.4.3.

It doesn't.
not even a little bit.
It's not IPsec; it's not about what key management peers to interact
with.

It's conceptually similar to the Security Association Database (SAD).
In a discussion with Jari I agreed to propose text for a paragraph
describing how this interacts with IPsec.

If this conceptual database is used to manage to keys for a security
    protocol that uses IPsec [RFC4301] security services, then  the
    interactions between this conceptual database and the IPsec
    databases needs to be described by the protocol specification.
    Typically such a protocol would insert entries into the Security
    Association Database (SAD) when rows are inserted into the key table
    and remove SAD entries when key table rows are removed.  The
    protocol specification needs to describe how the SAD entries are
    constructed along with any other IPsec database entries that are
    needed, including a description of how these entries are ordered
    along with other IPsec database entries.  The question of whether it
    is desirable to use this conceptual database to manage protocols
    that use IPsec security services is open and has not been evaluated.

    Black,> [C] (Section 3) Where does key selection occur?  I would
    Black,> suggest that the database return all possible keys and let
    Black,> the protocol figure out what to use.  This is particularly
    Black,> important for inbound traffic for obvious reasons.

I think we've discussed key selection in the WG and come to a different
conclusion.  The key table selects the key.  We expect peer, key ID,
protocol and interface to identify a unique key for an inbound packet.

So, I think the concern you raise is not a problem.
While there was not a specific thread discussing key selection or this
issue, there were multiple reviewers who provided comments on key
selection over the development of the document, and making a major
change at this point without a technical problem seems undesirable.
If I'm missing something and the inbound packet issue is a problem then
we need to discuss it.

From jari.arkko@piuha.net  Thu Aug 15 01:27:32 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3860D11E80EA for <gen-art@ietfa.amsl.com>; Thu, 15 Aug 2013 01:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.066, 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 pmx7z08XBSEs for <gen-art@ietfa.amsl.com>; Thu, 15 Aug 2013 01:27:28 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C4A0211E8107 for <gen-art@ietf.org>; Thu, 15 Aug 2013 01:27:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0A71E2CC48; Thu, 15 Aug 2013 11:27:27 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DYgoNO12KlRk; Thu, 15 Aug 2013 11:27:25 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D448E2CC44; Thu, 15 Aug 2013 11:27:21 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <1374000138.7044.90.camel@acorde.it.uc3m.es>
Date: Thu, 15 Aug 2013 18:27:19 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C601446-1C59-4AEC-897F-9D952528C2CE@piuha.net>
References: <51E51DA9.8000005@isode.com> <1374000138.7044.90.camel@acorde.it.uc3m.es>
To: cjbc@it.uc3m.es
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org, draft-ietf-multimob-pmipv6-ropt.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-multimob-pmipv6-ropt-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, 15 Aug 2013 08:27:32 -0000

Many thanks for your review, Alexey! And thank you Carlos for updating =
the draft. I have balloted a No-Objection position, mostly based on the =
Gen-ART review. I'd normally do a little bit of review myself as well, =
but I'm on vacation, so I have been unable to review more than a couple =
of documents this time.

When will the -08 be published.

Jari

On Jul 17, 2013, at 4:42 AM, Carlos Jes=FAs Bernardos Cano =
<cjbc@it.uc3m.es> wrote:

> Hi Alexey,
>=20
> Thanks a lot for the review. Please see below some comments inline.
>=20
> On Tue, 2013-07-16 at 11:17 +0100, Alexey Melnikov wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.=20
>>=20
>>=20
>>=20
>> Document: draft-ietf-multimob-pmipv6-ropt-07.txt
>>=20
>> Reviewer: Alexey Melnikov
>>=20
>> Review Date: 16 July 2013
>>=20
>> IETF LC End Date: 3 July 2013
>>=20
>> IESG Telechat date: 18 July 2013
>>=20
>>=20
>>=20
>> Summary: Ready for publication as an Experimental RFC with some nits
>>=20
>>=20
>> Major issues: None
>>=20
>>=20
>>=20
>> Minor issues:
>>=20
>>=20
>>=20
>>=20
>> In 5.1.2:
>>=20
>> Dynamic IP Multicast Selector Mode Flag:
>>=20
>>      This field indicates the subscription via MTMA/direct routing
>>      mode.  If the (M) flag value is set to a value of (1), it is an
>>      indication that the IP multicast traffic associated to the
>>      multicast group(s) identified by the Multicast Address Record(s)
>>      in this mobility option SHOULD be routed locally (subscription
>> via
>>      direct routing mode).  If the (M) flag value is set to a value
>> of
>>      (0), it is an indication that IP multicast traffic associated to
>>      the multicast group(s) identified by the Multicast Address
>> Record
>>      in this mobility option(s) SHOULD be routed to the home network,
>>      via the MTMA (subscription via MTMA mode).  All other IP traffic
>>      associated with the mobile node SHOULD be managed according to a
>>      default policy configured at the PMIPv6 multicast domain.
>>=20
>> The last sentence: I don't think you should use RFC 2119 SHOULD here.
>> I think you are saying that this document doesn't affect all other IP
>> traffic. So just use "is managed" instead of "SHOULD be managed".
>>=20
> OK, updated in version -08 (to be submitted once we get all the
> comments).
>=20
>>=20
>> Is IANA Considerations section clear to IANA? I suggest you add at
>> least the URI for the IANA registry.
>> Is IANA registration policy compatible with the type of document
>> (Experimental)? I can't check that, as I don't know which registry =
you
>> are talking about.
>>=20
> The IANA has not complained about it, but we will update the text in =
-08
> so it reads like this:
>=20
> 9.  IANA Considerations
>=20
>   This document defines a new mobility option, the Dynamic IP =
Multicast
>   Selector, which has been assigned the Type TBD by IANA.  The Type
>   value for these options has been assigned from the same numbering
>   space as allocated for the other mobility options, as defined in
>   [RFC6275]: http://www.iana.org/assignments/mobility-parameters/
>   mobility-parameters.xhtml.
>>=20
>>=20
>>=20
>> Nits/editorial comments:
>>=20
>>=20
>>=20
>> In 3.3: acronyms PBU and PBA need to be expanded on first use. They
>> are expanded further down in the document.
>=20
> Fixed in -08, thanks.
>=20
> Thanks again for the review,
>=20
> Carlos
>>=20
>>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From Francis.Dupont@fdupont.fr  Thu Aug 15 01:45:00 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3A2221F92E7 for <gen-art@ietfa.amsl.com>; Thu, 15 Aug 2013 01:44:59 -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 ERGroo3LHAdR for <gen-art@ietfa.amsl.com>; Thu, 15 Aug 2013 01:44:56 -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 DD2A521F92A5 for <gen-art@ietf.org>; Thu, 15 Aug 2013 01:44:55 -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 r7F8isj8008081; Thu, 15 Aug 2013 10:44:54 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201308150844.r7F8isj8008081@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Thu, 15 Aug 2013 10:44:53 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-storm-ipsec-ips-update.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-storm-ipsec-ips-update-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 08:45:00 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document: draft-ietf-storm-ipsec-ips-update-03.txt
Reviewer: Francis Dupont
Review Date: 2013-08-14
IETF LC End Date: 2013-08-19
IESG Telechat date: unknown

Summary: Almost ready

Major issues: None

Minor issues:
 - this is in fact a pure editorial concern but as it can have a big impact
  on not IETF expert readers I put it here:
  At the end of 3 page 9:
   use of IPsec v3 is recommended -> use of IPsec v3 is RECOMMENDED
 Two notes for the discussion:
  - a RFC 2119 keyword doesn't need to be capitalized
  - it is the only place with a preference for IPsec v3 over v2.

Nits/editorial comments:
 - Authors' Addresses page 16 (twice): US -> USA

Regards

Francis.Dupont@fdupont.fr

From david.black@emc.com  Thu Aug 15 04:42:39 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5A121E8123 for <gen-art@ietfa.amsl.com>; Thu, 15 Aug 2013 04:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xb3CKnFjhWMW for <gen-art@ietfa.amsl.com>; Thu, 15 Aug 2013 04:42:34 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 7A95521E804B for <gen-art@ietf.org>; Thu, 15 Aug 2013 04:42:34 -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 r7FBgPGr027945 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Aug 2013 07:42:26 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 15 Aug 2013 07:42:10 -0400
Received: from mxhub32.corp.emc.com (mxhub32.corp.emc.com [128.222.70.172]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7FBgA84014984; Thu, 15 Aug 2013 07:42:10 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub32.corp.emc.com ([128.222.70.172]) with mapi; Thu, 15 Aug 2013 07:42:10 -0400
From: "Black, David" <david.black@emc.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Thu, 15 Aug 2013 07:42:06 -0400
Thread-Topic: [Gen-art] review of draft-ietf-storm-ipsec-ips-update-03.txt
Thread-Index: Ac6Zk64cThJlsFl/TPapKN3TnltJDwAGKX7g
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C2B7C4B@MX15A.corp.emc.com>
References: <201308150844.r7F8isj8008081@givry.fdupont.fr>
In-Reply-To: <201308150844.r7F8isj8008081@givry.fdupont.fr>
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: "draft-ietf-storm-ipsec-ips-update.all@tools.ietf.org" <draft-ietf-storm-ipsec-ips-update.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-storm-ipsec-ips-update-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 11:42:39 -0000

Francis,

Thank you for the review.  I have made all three changes in my working vers=
ion that
will become the -04.

Merci,
--David

> -----Original Message-----
> From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On Behal=
f Of
> Francis Dupont
> Sent: Thursday, August 15, 2013 4:45 AM
> To: gen-art@ietf.org
> Cc: draft-ietf-storm-ipsec-ips-update.all@tools.ietf.org
> Subject: [Gen-art] review of draft-ietf-storm-ipsec-ips-update-03.txt
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-storm-ipsec-ips-update-03.txt
> Reviewer: Francis Dupont
> Review Date: 2013-08-14
> IETF LC End Date: 2013-08-19
> IESG Telechat date: unknown
>=20
> Summary: Almost ready
>=20
> Major issues: None
>=20
> Minor issues:
>  - this is in fact a pure editorial concern but as it can have a big impa=
ct
>   on not IETF expert readers I put it here:
>   At the end of 3 page 9:
>    use of IPsec v3 is recommended -> use of IPsec v3 is RECOMMENDED
>  Two notes for the discussion:
>   - a RFC 2119 keyword doesn't need to be capitalized
>   - it is the only place with a preference for IPsec v3 over v2.
>=20
> Nits/editorial comments:
>  - Authors' Addresses page 16 (twice): US -> USA
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From cjbc@it.uc3m.es  Thu Aug 15 05:12:32 2013
Return-Path: <cjbc@it.uc3m.es>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A95A11E81B7 for <gen-art@ietfa.amsl.com>; Thu, 15 Aug 2013 05:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 0lSplmQbJxZk for <gen-art@ietfa.amsl.com>; Thu, 15 Aug 2013 05:12:27 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by ietfa.amsl.com (Postfix) with ESMTP id 8C0D011E81A6 for <gen-art@ietf.org>; Thu, 15 Aug 2013 05:12:24 -0700 (PDT)
Received: from smtp01.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 1D06DCC601D; Thu, 15 Aug 2013 14:12:23 +0200 (CEST)
X-uc3m-safe: yes
X-uc3m-safe: yes
Received: from [192.168.0.101] (modemcable143.234-81-70.mc.videotron.ca [70.81.234.143]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp01.uc3m.es) by smtp01.uc3m.es (Postfix) with ESMTPSA id 44444C34AEE; Thu, 15 Aug 2013 14:12:22 +0200 (CEST)
Message-ID: <1376568736.4128.5.camel@acorde.it.uc3m.es>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: Jari Arkko <jari.arkko@piuha.net>
Date: Thu, 15 Aug 2013 14:12:16 +0200
In-Reply-To: <3C601446-1C59-4AEC-897F-9D952528C2CE@piuha.net>
References: <51E51DA9.8000005@isode.com> <1374000138.7044.90.camel@acorde.it.uc3m.es> <3C601446-1C59-4AEC-897F-9D952528C2CE@piuha.net>
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.4.4-3 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.0.0.1014-20082.006
Cc: gen-art@ietf.org, draft-ietf-multimob-pmipv6-ropt.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-multimob-pmipv6-ropt-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cjbc@it.uc3m.es
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 15 Aug 2013 12:12:32 -0000

Hi Jari, all,

We have already added all the received comments in the (unpublished) -08
version. We were waiting for the IESG review to be finished to publish
it (to address any additional comments that we may receive). If you
prefer us to publish it already or to make current version available
(without publishing it yet), let us know.

Thanks,

Carlos

On Thu, 2013-08-15 at 18:27 +1000, Jari Arkko wrote:
> Many thanks for your review, Alexey! And thank you Carlos for updating the draft. I have balloted a No-Objection position, mostly based on the Gen-ART review. I'd normally do a little bit of review myself as well, but I'm on vacation, so I have been unable to review more than a couple of documents this time.
> 
> When will the -08 be published.
> 
> Jari
> 
> On Jul 17, 2013, at 4:42 AM, Carlos JesÃºs Bernardos Cano <cjbc@it.uc3m.es> wrote:
> 
> > Hi Alexey,
> > 
> > Thanks a lot for the review. Please see below some comments inline.
> > 
> > On Tue, 2013-07-16 at 11:17 +0100, Alexey Melnikov 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-multimob-pmipv6-ropt-07.txt
> >> 
> >> Reviewer: Alexey Melnikov
> >> 
> >> Review Date: 16 July 2013
> >> 
> >> IETF LC End Date: 3 July 2013
> >> 
> >> IESG Telechat date: 18 July 2013
> >> 
> >> 
> >> 
> >> Summary: Ready for publication as an Experimental RFC with some nits
> >> 
> >> 
> >> Major issues: None
> >> 
> >> 
> >> 
> >> Minor issues:
> >> 
> >> 
> >> 
> >> 
> >> In 5.1.2:
> >> 
> >> Dynamic IP Multicast Selector Mode Flag:
> >> 
> >>      This field indicates the subscription via MTMA/direct routing
> >>      mode.  If the (M) flag value is set to a value of (1), it is an
> >>      indication that the IP multicast traffic associated to the
> >>      multicast group(s) identified by the Multicast Address Record(s)
> >>      in this mobility option SHOULD be routed locally (subscription
> >> via
> >>      direct routing mode).  If the (M) flag value is set to a value
> >> of
> >>      (0), it is an indication that IP multicast traffic associated to
> >>      the multicast group(s) identified by the Multicast Address
> >> Record
> >>      in this mobility option(s) SHOULD be routed to the home network,
> >>      via the MTMA (subscription via MTMA mode).  All other IP traffic
> >>      associated with the mobile node SHOULD be managed according to a
> >>      default policy configured at the PMIPv6 multicast domain.
> >> 
> >> The last sentence: I don't think you should use RFC 2119 SHOULD here.
> >> I think you are saying that this document doesn't affect all other IP
> >> traffic. So just use "is managed" instead of "SHOULD be managed".
> >> 
> > OK, updated in version -08 (to be submitted once we get all the
> > comments).
> > 
> >> 
> >> Is IANA Considerations section clear to IANA? I suggest you add at
> >> least the URI for the IANA registry.
> >> Is IANA registration policy compatible with the type of document
> >> (Experimental)? I can't check that, as I don't know which registry you
> >> are talking about.
> >> 
> > The IANA has not complained about it, but we will update the text in -08
> > so it reads like this:
> > 
> > 9.  IANA Considerations
> > 
> >   This document defines a new mobility option, the Dynamic IP Multicast
> >   Selector, which has been assigned the Type TBD by IANA.  The Type
> >   value for these options has been assigned from the same numbering
> >   space as allocated for the other mobility options, as defined in
> >   [RFC6275]: http://www.iana.org/assignments/mobility-parameters/
> >   mobility-parameters.xhtml.
> >> 
> >> 
> >> 
> >> Nits/editorial comments:
> >> 
> >> 
> >> 
> >> In 3.3: acronyms PBU and PBA need to be expanded on first use. They
> >> are expanded further down in the document.
> > 
> > Fixed in -08, thanks.
> > 
> > Thanks again for the review,
> > 
> > Carlos
> >> 
> >> 
> > 
> > 
> > _______________________________________________
> > Gen-art mailing list
> > Gen-art@ietf.org
> > https://www.ietf.org/mailman/listinfo/gen-art
> 



From kent@bbn.com  Thu Aug 15 13:05:05 2013
Return-Path: <kent@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 1DD4121F994C; Thu, 15 Aug 2013 13:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.518
X-Spam-Level: 
X-Spam-Status: No, score=-106.518 tagged_above=-999 required=5 tests=[AWL=0.081, 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 MR3E+1z9E4C4; Thu, 15 Aug 2013 13:04:57 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id A2AF421F9798; Thu, 15 Aug 2013 13:04:57 -0700 (PDT)
Received: from dhcp89-089-218.bbn.com ([128.89.89.218]:53876) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1VA3my-0007db-3Y; Thu, 15 Aug 2013 16:04:56 -0400
Message-ID: <520D3467.1080107@bbn.com>
Date: Thu, 15 Aug 2013 16:04:55 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> <tslr4dwcbmh.fsf@mit.edu>
In-Reply-To: <tslr4dwcbmh.fsf@mit.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "tim.polk@nist.gov" <tim.polk@nist.gov>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 20:05:06 -0000

David,

I agree with Sam here. The key table is analogous to the SPD in 4301, 
but not
the PAD.

Another doc being developed in the KARP WG does have a "Routing 
Authentication Policy
Database" (RAPD) that incorporates aspects of the PAD from 4301, as well 
as some
SPD fields.

Steve

From mahoney@nostrum.com  Thu Aug 15 15:35:40 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66E4E11E818D for <gen-art@ietfa.amsl.com>; Thu, 15 Aug 2013 15:35:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HD1wExXDQXWp for <gen-art@ietfa.amsl.com>; Thu, 15 Aug 2013 15:35:40 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id CCD1411E8150 for <gen-art@ietf.org>; Thu, 15 Aug 2013 15:35:39 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7FMZbgX089552 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 15 Aug 2013 17:35:38 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <520D57B9.50309@nostrum.com>
Date: Thu, 15 Aug 2013 17:35:37 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-08-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 22:35:40 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Joel Halpern      2013-08-26   draft-ietf-tsvwg-sctp-sack-immediately-03

Kathleen Moriarty 2013-08-27   draft-ietf-dime-realm-based-redirect-11

Meral Shirazipour 2013-08-29   draft-ietf-repute-query-http-09

Peter McCann      2013-08-29   draft-ietf-repute-email-identifiers-08

Peter Yee         2013-08-29   draft-ietf-repute-media-type-10

Roni Even         2013-08-29   draft-ietf-repute-model-07

Robert Sparks     2013-08-29   draft-ietf-netext-update-notifications-07


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

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


The standard template is included below.

Thanks,

Jean

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From uma.chunduri@ericsson.com  Thu Aug 15 16:06:28 2013
Return-Path: <uma.chunduri@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 7FCD211E8219; Thu, 15 Aug 2013 16:06:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ozKzQkLAR7SH; Thu, 15 Aug 2013 16:06:21 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id C6DB711E8138; Thu, 15 Aug 2013 16:06:20 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-5e-520d5eeb6002
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 1F.0F.09414.BEE5D025; Fri, 16 Aug 2013 01:06:19 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0328.009; Thu, 15 Aug 2013 19:06:18 -0400
From: Uma Chunduri <uma.chunduri@ericsson.com>
To: Stephen Kent <kent@bbn.com>, Sam Hartman <hartmans-ietf@mit.edu>
Thread-Topic: [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
Thread-Index: Ac6VD0rmlAaf+56PTd+LLDqqvEOcAQEFcz9OADvJOYAAAi6WMA==
Date: Thu, 15 Aug 2013 23:06:18 +0000
Message-ID: <1B502206DFA0C544B7A60469152008631747F84B@eusaamb105.ericsson.se>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> <tslr4dwcbmh.fsf@mit.edu> <520D3467.1080107@bbn.com>
In-Reply-To: <520D3467.1080107@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [155.53.74.98]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyuXRPlO7rON4gg3t3JS22Hl7LbnH11WcW izlfV7NZPNs4n8Vi77c1jBYbZzNafFr1mMmB3WPq+VCPI0dms3gsWfKTyaPpzFFmj2sn/7IG sEZx2aSk5mSWpRbp2yVwZUxbGFpwl7Hi7/ZGpgbGZYxdjJwcEgImEs1PG9khbDGJC/fWs3Ux cnEICRxllNiz5iQ7hLOcUeLVu2msIFVsAnoSH6f+BOsQEXCR2PdsNSNIEbPATUaJI5u+MoEk hAU8JRa2rQYaxQFU5CXxq5cFwnSS+NKQB1LBIqAqsW/OQ2aQMK+Ar8Sas1CrGhgl/k7YD3Yc p4C6xJRNZ8DWMgId9/3UGrDpzALiEreezGeCOFpAYsme88wQtqjEy8f/WCFsBYkdi36xQNTr SCzY/YkNwtaWWLbwNVg9r4CgxMmZT1gmMIrNQjJ2FpKWWUhaZiFpWcDIsoqRo7Q4tSw33chg EyMw3o5JsOnuYNzz0vIQozQHi5I47yq9M4FCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGE2+ f+c7ynouv2y1oUl5ydP9O38+PmgYniD7KYVrudOOTU3TLrYcZph+7dmSRUqcVVb1Nb9+cbZI XH9pyMsn6tXzl+9Khb3KnF/l96VTGH5tc534Wsmr34bVsp2xdc+N+jBujisXb+r1hNyzaj+z dfnuFdkeLWFGXdFBXCK7XPOun2Nnzjt0XImlOCPRUIu5qDgRACJAkDGFAgAA
X-Mailman-Approved-At: Thu, 15 Aug 2013 18:23:19 -0700
Cc: "tim.polk@nist.gov" <tim.polk@nist.gov>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 23:06:28 -0000

=20
>> The key table is analogous to the SPD in 4301, but not the PAD.


Close to SAD not SPD for some RPs as it have negotiation result including k=
eys.=20
But not definitely analogous to the PAD.

--
Uma C.=

From jmh@joelhalpern.com  Fri Aug 16 02:12:33 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C80611E826A for <gen-art@ietfa.amsl.com>; Fri, 16 Aug 2013 02:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DIlNDOkttd48 for <gen-art@ietfa.amsl.com>; Fri, 16 Aug 2013 02:12:28 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id E1DAD11E825F for <gen-art@ietf.org>; Fri, 16 Aug 2013 02:12:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id DB0B81C0541; Fri, 16 Aug 2013 02:12:26 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [192.165.183.201]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 3CC771C0198; Fri, 16 Aug 2013 02:12:26 -0700 (PDT)
Message-ID: <520DECF8.9040605@joelhalpern.com>
Date: Fri, 16 Aug 2013 05:12:24 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <520D57B9.50309@nostrum.com>
In-Reply-To: <520D57B9.50309@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]  review: draft-ietf-tsvwg-sctp-sack-immediately-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 09:12: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: draft-ietf-tsvwg-sctp-sack-immediately-03.txt
Reviewer: Joel M. Halpern
Review Date: 16-August-2013
IETF LC End Date: 26-August-2013
IESG Telechat date: N/A

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

Major issues: N/A

Minor issues: N/A

Nits/editorial comments: N/A

From david.black@emc.com  Fri Aug 16 10:01:07 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D239421F9AEF; Fri, 16 Aug 2013 10:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, 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 SDlzf6VHIBZc; Fri, 16 Aug 2013 10:01:02 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 088F521F9A2A; Fri, 16 Aug 2013 10:01:00 -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 r7GH0YWt004445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 13:00:36 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 16 Aug 2013 13:00:14 -0400
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7GH0Dvp023435; Fri, 16 Aug 2013 13:00:13 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Fri, 16 Aug 2013 13:00:12 -0400
From: "Black, David" <david.black@emc.com>
To: Sam Hartman <hartmans-ietfc@mit.edu>
Date: Fri, 16 Aug 2013 13:00:11 -0400
Thread-Topic: [karp] IANA policy for  draft-ietf-karp-crypto-key-table-08
Thread-Index: Ac6ZIxPCrHP82d6uQRm+ncYL1wquCwBezKGg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C489288@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> <tslvc38cc7p.fsf@mit.edu>
In-Reply-To: <tslvc38cc7p.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] [karp] IANA policy for draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 17:01:08 -0000

Sam,

Thanks for picking this up.  Unlike my other two concerns with this draft,
I think we have a longer discussion ahead of us on this one.

Your summary of my concern is on the mark:

> David's main concern is that bad security will get registered.

I understand the response to be two-fold:

1) It doesn't matter; the controlling registry for crypto algorithm usage
is the protocol-specific registry, not the key table database registry.

2) The guidance for the Expert Reviewer will be very difficult to write.

I'm not convinced by either of these, sorry.

I'm concerned that the two-registry subtlety in 1) will be lost on
implementers, especially because (as mentioned in the IESG thread), this
key table database is likely to see use beyond routing protocols.  Among
other things, it's being proposed as a general mechanism for keying RSVP,
not just RSVP-TE (I'm one of the co-chairs of the tsvwg WG that's
responsible for RSVP).  That key table databases registry is also likely
to be a place that designers of new protocols look to figure out what to
use for security.

As for cleartext passwords:

> Also, some routing protocols are protected by cleartext passwords sent
> over the network.  We want to be able to manage that, so we will be
> registering plaintext password in these registries.
> I don't think anyone will come up with anything worse than that.

I read the first sentence in Section 2 of this draft as excluding
cleartext passwords:

   The database is characterized as a table, where each row represents
   a single long-lived symmetric cryptographic key.

If someone wants to argue that a cleartext password is a "long-lived
symmetric cryptographic key", I'll go break out the popcorn and watch
w/amusement :-).

Seriously, if the intention is to include cleartext passwords, then I
think some more rewriting is in order, and I would suggest checking
directly with the Security ADs before going there.

As for 2), the fact that it will be difficult (with which I agree)
doesn't imply that it isn't necessary or shouldn't be done.  IMHO, we
really should be setting a bar that says that this sort of IETF
imprimatur of approval of a crypto algorithm actually means something.

I appreciate that FCFS provides an easier path forward, however I'm
reminded by analogy of something I learned from my grad school
software engineering professor:

	I can make the code run arbitrarily fast ...
	...  if it doesn't have to be correct.

I'm rather uncomfortable with this use of process expediency as a
rationale for avoiding a technical concern.

This may ultimately be an issue that the IESG needs to sort out, as the
level of security for IETF protocols and concerns about "vanity crypto"=20
extend well beyond the karp WG, but discussion ought to start here.

Thanks,
--David


> -----Original Message-----
> From: Sam Hartman [mailto:hartmans-ietfc@mit.edu]
> Sent: Wednesday, August 14, 2013 3:19 PM
> To: Black, David
> Cc: housley@vigilsec.com; tim.polk@nist.gov; Dacheng Zhang
> (zhangdacheng@huawei.com); General Area Review Team (gen-art@ietf.org);
> karp@ietf.org; ietf@ietf.org
> Subject: Re: [karp] IANA policy for draft-ietf-karp-crypto-key-table-08
>=20
>=20
>=20
> David, as we mentioned in the IESG thread, we seem to have dropped the
> response to your comments about IANA actions.
>=20
> WG:
> From the genart review:
>=20
> [9] I suggest Expert Review for the new IANA registries, not just
> First Come First Served, so that someone with a security "clue" can
> check that the proposed registrations are reasonable.
>=20
>=20
> Stephen has filed a related DISCUSS position.  He's confused why we need
> a registry for  KDFs or algorithms.
> He argues that the protocols should already have such a registry.  He
> argues that it would be non-sensical to register a value in this
> registry but not the protocol registry.
>=20
> In a somewhat related discussion, multiple people have asked what the
> scope of this document is.  Are we defining something for routing
> protocols?  Any security protocol in the world?  Something in-between?
>=20
>=20
> IU'm going to make two responses:
>=20
> 1)
> I think FCFS is not harmful for these registries.
>=20
> David's main concern is that bad security will get registered.
>=20
> I'll point out that these registries are not about what security you can
> use with a routing protocol, but about what security you can configure
> from a management standpoint.
> Registering rot13 or similarly questionable security here wouldn't mean
> I could use it with a routing protocol, only that I could ask a system
> to do so.  If ROT13 was not actually in the security-specific registries
> for the protocols in question there'd be no way to send a
> rot13-transformed message.
>=20
> I think people wanting to use bad security in routing protocols will
> focus on specifying how to use the security for the protocols, and
> that's the appropriate place to do any gateway review.
> Yeah, I guess with FCFS it's possible someone could register here and
> then later realize they cannot get their md4 security approved in the
> actual protocol registry document.
>=20
> That might be confusing but doesn't seem very harmful.
>=20
> Also, some routing protocols are protected by cleartext passwords sent
> over the network.  We want to be able to manage that, so we will be
> registering plaintext password in these registries.
> I don't think anyone will come up with anything worse than that.
>=20
> Finally, I think a lot of us have begun to question the value in
> security review for codepoint assignment.  Some security WGs care a lot;
> some don't seem to care much at all.
>=20
> 2)  Why I prefer FCFS or at least would object strongly to expert
> review.
>=20
> If we're going to say we want expert review I want us to give  expert
> instructions at least good enough that I believe I could answer the
> question of what registrations to approve if I were appointed the
> expert.
>=20
> I don't think we could come to consensus on those instructions very
> easily.
> In particular, I think it would be challenging for us to describe what
> security protocols the protocol registry applies to and which ones it
> does not.
>=20
> I'm totally fine publishing this document knowing it will be used for
> routing protocols but not knowing what beyond routing protocols it will
> be used for.
> If we do that FCFS makes a lot of sense.
>=20
> So, my recommendation is that we keep our current registration policy.


From david.black@emc.com  Fri Aug 16 10:50:04 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 269D821F92B9; Fri, 16 Aug 2013 10:50:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ExS4MwCrFlK8; Fri, 16 Aug 2013 10:49:58 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 626BC21F844D; Fri, 16 Aug 2013 10:49:57 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7GGVjBB013274 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 12:31:46 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 16 Aug 2013 12:31:23 -0400
Received: from mxhub23.corp.emc.com (mxhub23.corp.emc.com [128.222.70.135]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7GGVMQ7020802; Fri, 16 Aug 2013 12:31:23 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub23.corp.emc.com ([128.222.70.135]) with mapi; Fri, 16 Aug 2013 12:31:22 -0400
From: "Black, David" <david.black@emc.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Date: Fri, 16 Aug 2013 12:31:20 -0400
Thread-Topic: [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
Thread-Index: Ac6ZJNjZjowH+sHwRJSBvO6n+kH4QABddLkA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C489279@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> <tslr4dwcbmh.fsf@mit.edu>
In-Reply-To: <tslr4dwcbmh.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 17:50:04 -0000

Sam,

Thanks for taking another look at this.  I think we're in good shape on
the IPsec relationship concern, but I think key selection responsibility
could use some more attention.

[A] The new text on the IPsec relationship looks good - I'd suggest also
adding a sentence to state that keys for IPsec pre-shared-key authenticatio=
n
are not appropriate for this key database.

[C] The key selection responsibility was not clear to me from the draft -
the intent/design stated in your message is fine (and having one key
be returned is simpler, and probably more robust than handing
multiple keys to different protocol implementations and hoping
that they do something consistent):

> I think we've discussed key selection in the WG and come to a different
> conclusion.  The key table selects the key.  We expect peer, key ID,
> protocol and interface to identify a unique key for an inbound packet.

My confusion stems from section 3 starting out by stating that the
key database is consulted "to find the key to use on an outgoing message"
followed by several sentences that indicate that the consultation may
result in multiple keys.  That leads to a suggestion and a question.

Suggestion:=20

Add a new paragraph at the start of Section 3 to make the functional
responsibility clear:

  Key selection is the responsibility of the key database functionality;
  in all cases, the protocol requests a key, and the database returns one
  key or an indication that there is no matching key.  When multiple keys
  match a protocol's request, the key database selects one as described
  further in this section.

Question:

What happens, when despite all the measures described in Section 3,
multiple keys match a protocol's request?  How does one ensure that the
key databases at both ends of the security association return the same
key?

Thanks,
--David

> -----Original Message-----
> From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
> Sent: Wednesday, August 14, 2013 3:32 PM
> To: Black, David
> Cc: housley@vigilsec.com; tim.polk@nist.gov; Dacheng Zhang
> (zhangdacheng@huawei.com); General Area Review Team (gen-art@ietf.org);
> karp@ietf.org; ietf@ietf.org
> Subject: Re: [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
>=20
> >>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
>=20
>=20
>     Black,> [A] Overall - I would like to see a paragraph added on how
>     Black,> this database conceptually relates to the IPsec Peer
>     Black,> Authorization Database (PAD) - see RFC 4301, section 4.4.3.
>=20
> It doesn't.
> not even a little bit.
> It's not IPsec; it's not about what key management peers to interact
> with.
>=20
> It's conceptually similar to the Security Association Database (SAD).
> In a discussion with Jari I agreed to propose text for a paragraph
> describing how this interacts with IPsec.
>=20
> If this conceptual database is used to manage to keys for a security
>     protocol that uses IPsec [RFC4301] security services, then  the
>     interactions between this conceptual database and the IPsec
>     databases needs to be described by the protocol specification.
>     Typically such a protocol would insert entries into the Security
>     Association Database (SAD) when rows are inserted into the key table
>     and remove SAD entries when key table rows are removed.  The
>     protocol specification needs to describe how the SAD entries are
>     constructed along with any other IPsec database entries that are
>     needed, including a description of how these entries are ordered
>     along with other IPsec database entries.  The question of whether it
>     is desirable to use this conceptual database to manage protocols
>     that use IPsec security services is open and has not been evaluated.
>=20
>     Black,> [C] (Section 3) Where does key selection occur?  I would
>     Black,> suggest that the database return all possible keys and let
>     Black,> the protocol figure out what to use.  This is particularly
>     Black,> important for inbound traffic for obvious reasons.
>=20
> I think we've discussed key selection in the WG and come to a different
> conclusion.  The key table selects the key.  We expect peer, key ID,
> protocol and interface to identify a unique key for an inbound packet.
>=20
> So, I think the concern you raise is not a problem.
> While there was not a specific thread discussing key selection or this
> issue, there were multiple reviewers who provided comments on key
> selection over the development of the document, and making a major
> change at this point without a technical problem seems undesirable.
> If I'm missing something and the inbound packet issue is a problem then
> we need to discuss it.


From hartmans@mit.edu  Fri Aug 16 11:01:00 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36FA021F8C65; Fri, 16 Aug 2013 11:01:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, 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 Kpb-CSxpnfLn; Fri, 16 Aug 2013 11:00:54 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 3955511E817A; Fri, 16 Aug 2013 11:00:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id E7FA72029E; Fri, 16 Aug 2013 13:59:33 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JS0HoaQLAGBV; Fri, 16 Aug 2013 13:59:32 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Fri, 16 Aug 2013 13:59:32 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3890B8052F; Fri, 16 Aug 2013 14:00:47 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com>
Date: Fri, 16 Aug 2013 14:00:47 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com> (David Black's message of "Fri, 16 Aug 2013 13:02:35 -0400")
Message-ID: <tslpptd348g.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, Sam Hartman <hartmans-ietfc@mit.edu>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] [karp] IANA policy for draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 18:01:00 -0000

>>>>> "Black," == Black, David <david.black@emc.com> writes:

    Black,> done.  IMHO, we really should be setting a bar that says
    Black,> that this sort of IETF imprimatur of approval of a crypto
    Black,> algorithm actually means something.



Something got manged there.
I agree that publishing a standards-track document  should endorce the
algorithm in question.

I'm somewhat uncomfortable with that sort of bar for IANA registries in
general, although I have supported it from time to time.  (My discomfort
with this has grown significantly since my time as an AD).  I do not
support that sort of bar for this registry.

I think we understand each other, but disagree.

The question now is whether you can gain sufficient support to show
rough consensus for a change in the document or to show that while there
was rough consensus behind the document in the KARP WG, there's a lack
of consensus on handling this issue between KARP and some other
significant segment of the IETF like the security area.

From hartmans@mit.edu  Fri Aug 16 11:02:35 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD5011E81FF; Fri, 16 Aug 2013 11:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, 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 2g8uESl0QDlu; Fri, 16 Aug 2013 11:02:35 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 13E4011E8165; Fri, 16 Aug 2013 11:02:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 5E8AA202AC; Fri, 16 Aug 2013 14:01:19 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQ7nmKCcgc0z; Fri, 16 Aug 2013 14:01:19 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Fri, 16 Aug 2013 14:01:19 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id C99958052F; Fri, 16 Aug 2013 14:02:33 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com> (David Black's message of "Fri, 16 Aug 2013 13:02:35 -0400")
References: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Date: Fri, 16 Aug 2013 14:02:33 -0400
Message-ID: <tslob8x345i.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, Sam Hartman <hartmans-ietf@mit.edu>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] [karp] IANA policy for draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 18:02:35 -0000

>>>>> "Black," == Black, David <david.black@emc.com> writes:

    Black,> done.  IMHO, we really should be setting a bar that says
    Black,> that this sort of IETF imprimatur of approval of a crypto
    Black,> algorithm actually means something.



Something got manged there.
I agree that publishing a standards-track document  should endorce the
algorithm in question.

I'm somewhat uncomfortable with that sort of bar for IANA registries in
general, although I have supported it from time to time.  (My discomfort
with this has grown significantly since my time as an AD).  I do not
support that sort of bar for this registry.

I think we understand each other, but disagree.

The question now is whether you can gain sufficient support to show
rough consensus for a change in the document or to show that while there
was rough consensus behind the document in the KARP WG, there's a lack
of consensus on handling this issue between KARP and some other
significant segment of the IETF like the security area.

From carter@qosient.com  Fri Aug 16 10:57:28 2013
Return-Path: <carter@qosient.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4242421F9FCA; Fri, 16 Aug 2013 10:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6, 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 2PzfUL3FHnV7; Fri, 16 Aug 2013 10:57:23 -0700 (PDT)
Received: from mail1.g1.pair.com (mail1.g1.pair.com [66.39.3.162]) by ietfa.amsl.com (Postfix) with ESMTP id 3F0BD21F9D5F; Fri, 16 Aug 2013 10:57:23 -0700 (PDT)
Received: from thoth.newyork.qosient.com (207-237-36-98.c3-0.avec-ubr1.nyr-avec.ny.static.cable.rcn.com [207.237.36.98]) by mail1.g1.pair.com (Postfix) with ESMTPSA id 242F32BD37; Fri, 16 Aug 2013 13:57:18 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_69F64EE4-81C0-425F-8C9E-CD3C38D0CCEC"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Carter Bullard <carter@qosient.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C489288@MX15A.corp.emc.com>
Date: Fri, 16 Aug 2013 13:57:17 -0400
Message-Id: <41E3D887-7FAD-47BA-AEBB-FF65F14F3F88@qosient.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> <tslvc38cc7p.fsf@mit.edu> <8D3D17ACE214DC429325B2B98F3AE7129C489288@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Fri, 16 Aug 2013 11:15:03 -0700
Cc: "tim.polk@nist.gov" <tim.polk@nist.gov>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Sam Hartman <hartmans-ietfc@mit.edu>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] [karp] IANA policy for draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 17:57:28 -0000

--Apple-Mail=_69F64EE4-81C0-425F-8C9E-CD3C38D0CCEC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hey David,
Having been down this path a number of times, I would like to
suggest that one shouldn't attempt to qualify any algorithm,
technique, method or approach that may be submitted to the
registration process.

By suggesting that the registry somehow contains only " good "
strategies, without any consideration regarding a specific
implementation, you're making a claim that is unsupportable.
Bad implementations of " good " strategies can be worst than
plaintext passwords =85 really.

Let the user decide what mechanisms they want to use, based
on their criteria.

Clear text passwords used over a triple AES encrypted channel
is not "by definition" a bad strategy.  Theoretically, it could
be abstracted as a two-factor system, which has its advantages,
regardless of the perceived " strength ".  Why not ??

Carter

On Aug 16, 2013, at 1:00 PM, "Black, David" <david.black@emc.com> wrote:

> Sam,
>=20
> Thanks for picking this up.  Unlike my other two concerns with this =
draft,
> I think we have a longer discussion ahead of us on this one.
>=20
> Your summary of my concern is on the mark:
>=20
>> David's main concern is that bad security will get registered.
>=20
> I understand the response to be two-fold:
>=20
> 1) It doesn't matter; the controlling registry for crypto algorithm =
usage
> is the protocol-specific registry, not the key table database =
registry.
>=20
> 2) The guidance for the Expert Reviewer will be very difficult to =
write.
>=20
> I'm not convinced by either of these, sorry.
>=20
> I'm concerned that the two-registry subtlety in 1) will be lost on
> implementers, especially because (as mentioned in the IESG thread), =
this
> key table database is likely to see use beyond routing protocols.  =
Among
> other things, it's being proposed as a general mechanism for keying =
RSVP,
> not just RSVP-TE (I'm one of the co-chairs of the tsvwg WG that's
> responsible for RSVP).  That key table databases registry is also =
likely
> to be a place that designers of new protocols look to figure out what =
to
> use for security.
>=20
> As for cleartext passwords:
>=20
>> Also, some routing protocols are protected by cleartext passwords =
sent
>> over the network.  We want to be able to manage that, so we will be
>> registering plaintext password in these registries.
>> I don't think anyone will come up with anything worse than that.
>=20
> I read the first sentence in Section 2 of this draft as excluding
> cleartext passwords:
>=20
>   The database is characterized as a table, where each row represents
>   a single long-lived symmetric cryptographic key.
>=20
> If someone wants to argue that a cleartext password is a "long-lived
> symmetric cryptographic key", I'll go break out the popcorn and watch
> w/amusement :-).
>=20
> Seriously, if the intention is to include cleartext passwords, then I
> think some more rewriting is in order, and I would suggest checking
> directly with the Security ADs before going there.
>=20
> As for 2), the fact that it will be difficult (with which I agree)
> doesn't imply that it isn't necessary or shouldn't be done.  IMHO, we
> really should be setting a bar that says that this sort of IETF
> imprimatur of approval of a crypto algorithm actually means something.
>=20
> I appreciate that FCFS provides an easier path forward, however I'm
> reminded by analogy of something I learned from my grad school
> software engineering professor:
>=20
> 	I can make the code run arbitrarily fast ...
> 	...  if it doesn't have to be correct.
>=20
> I'm rather uncomfortable with this use of process expediency as a
> rationale for avoiding a technical concern.
>=20
> This may ultimately be an issue that the IESG needs to sort out, as =
the
> level of security for IETF protocols and concerns about "vanity =
crypto"=20
> extend well beyond the karp WG, but discussion ought to start here.
>=20
> Thanks,
> --David
>=20
>=20
>> -----Original Message-----
>> From: Sam Hartman [mailto:hartmans-ietfc@mit.edu]
>> Sent: Wednesday, August 14, 2013 3:19 PM
>> To: Black, David
>> Cc: housley@vigilsec.com; tim.polk@nist.gov; Dacheng Zhang
>> (zhangdacheng@huawei.com); General Area Review Team =
(gen-art@ietf.org);
>> karp@ietf.org; ietf@ietf.org
>> Subject: Re: [karp] IANA policy for =
draft-ietf-karp-crypto-key-table-08
>>=20
>>=20
>>=20
>> David, as we mentioned in the IESG thread, we seem to have dropped =
the
>> response to your comments about IANA actions.
>>=20
>> WG:
>> =46rom the genart review:
>>=20
>> [9] I suggest Expert Review for the new IANA registries, not just
>> First Come First Served, so that someone with a security "clue" can
>> check that the proposed registrations are reasonable.
>>=20
>>=20
>> Stephen has filed a related DISCUSS position.  He's confused why we =
need
>> a registry for  KDFs or algorithms.
>> He argues that the protocols should already have such a registry.  He
>> argues that it would be non-sensical to register a value in this
>> registry but not the protocol registry.
>>=20
>> In a somewhat related discussion, multiple people have asked what the
>> scope of this document is.  Are we defining something for routing
>> protocols?  Any security protocol in the world?  Something =
in-between?
>>=20
>>=20
>> IU'm going to make two responses:
>>=20
>> 1)
>> I think FCFS is not harmful for these registries.
>>=20
>> David's main concern is that bad security will get registered.
>>=20
>> I'll point out that these registries are not about what security you =
can
>> use with a routing protocol, but about what security you can =
configure
>> from a management standpoint.
>> Registering rot13 or similarly questionable security here wouldn't =
mean
>> I could use it with a routing protocol, only that I could ask a =
system
>> to do so.  If ROT13 was not actually in the security-specific =
registries
>> for the protocols in question there'd be no way to send a
>> rot13-transformed message.
>>=20
>> I think people wanting to use bad security in routing protocols will
>> focus on specifying how to use the security for the protocols, and
>> that's the appropriate place to do any gateway review.
>> Yeah, I guess with FCFS it's possible someone could register here and
>> then later realize they cannot get their md4 security approved in the
>> actual protocol registry document.
>>=20
>> That might be confusing but doesn't seem very harmful.
>>=20
>> Also, some routing protocols are protected by cleartext passwords =
sent
>> over the network.  We want to be able to manage that, so we will be
>> registering plaintext password in these registries.
>> I don't think anyone will come up with anything worse than that.
>>=20
>> Finally, I think a lot of us have begun to question the value in
>> security review for codepoint assignment.  Some security WGs care a =
lot;
>> some don't seem to care much at all.
>>=20
>> 2)  Why I prefer FCFS or at least would object strongly to expert
>> review.
>>=20
>> If we're going to say we want expert review I want us to give  expert
>> instructions at least good enough that I believe I could answer the
>> question of what registrations to approve if I were appointed the
>> expert.
>>=20
>> I don't think we could come to consensus on those instructions very
>> easily.
>> In particular, I think it would be challenging for us to describe =
what
>> security protocols the protocol registry applies to and which ones it
>> does not.
>>=20
>> I'm totally fine publishing this document knowing it will be used for
>> routing protocols but not knowing what beyond routing protocols it =
will
>> be used for.
>> If we do that FCFS makes a lot of sense.
>>=20
>> So, my recommendation is that we keep our current registration =
policy.
>=20
> _______________________________________________
> karp mailing list
> karp@ietf.org
> https://www.ietf.org/mailman/listinfo/karp
>=20


--Apple-Mail=_69F64EE4-81C0-425F-8C9E-CD3C38D0CCEC
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIXZzCCBXAw
ggRYoAMCAQICAQ8wDQYJKoZIhvcNAQEFBQAwTTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g
R292ZXJubWVudDEMMAoGA1UECxMDRUNBMRYwFAYDVQQDEw1FQ0EgUm9vdCBDQSAyMB4XDTExMDYw
MTEzNDMzM1oXDTE3MDUzMDEzNDMzM1owcDELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292
ZXJubWVudDEMMAoGA1UECxMDRUNBMSIwIAYDVQQLExlDZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVz
MRUwEwYDVQQDEwxPUkMgRUNBIFNXIDQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDM
p/zFNAJfjYagDX701xRpK6QjRa7rhtR2U/CIE1pTSAR1BINfsYNHt2+bi0SH4SwZ61Xw9hMqCMBP
y05JJpeerEz0xpDbkqDz2NDqBm02rwdcRFqOWQn8Of3ALJKopAF6ZSkeF1j7KFCKQlIntAIyJ/c+
THyZJJD0Ns4SUrmQmBsm3q0kEl06lT7MHLPTv5LXkB+5PayhAJUWEXq/iUEhLDBstTaD1NGOleIM
sv3i1X01amB9GywN2v/kKlfGuGQpFAWi0QabC4hMfUjM217bGQS0/v1VV11zBpRlEEzH0zJgQQDX
WQy+V7vRbLav2bK3oWwvNTJGhb2CWHah7FrlAgMBAAGjggI2MIICMjASBgNVHRMBAf8ECDAGAQH/
AgEAMA4GA1UdDwEB/wQEAwIBhjAdBgNVHQ4EFgQUQpz0um9t6TDXOtZG9LI07p3STyYwHwYDVR0j
BBgwFoAU7eSH0CfEUOaEOvfM9+s6SfxSTiEwMwYDVR0gBCwwKjAMBgpghkgBZQMCAQwBMAwGCmCG
SAFlAwIBDAIwDAYKYIZIAWUDAgEMAzCBwAYDVR0fBIG4MIG1MCygKqAohiZodHRwOi8vY3JsLmRp
c2EubWlsL2NybC9FQ0FST09UQ0EyLmNybDCBhKCBgaB/hn1sZGFwOi8vY3JsLmdkcy5kaXNhLm1p
bC9jbiUzZEVDQSUyMFJvb3QlMjBDQSUyMDIlMmNvdSUzZEVDQSUyY28lM2RVLlMuJTIwR292ZXJu
bWVudCUyY2MlM2RVUz9jZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0O2JpbmFyeTCB0wYIKwYBBQUH
AQEEgcYwgcMwOgYIKwYBBQUHMAKGLmh0dHA6Ly9jcmwuZGlzYS5taWwvaXNzdWVkdG8vRUNBUk9P
VENBMl9JVC5wN2MwgYQGCCsGAQUFBzAChnhsZGFwOi8vY3JsLmdkcy5kaXNhLm1pbC9jbiUzZEVD
QSUyMFJvb3QlMjBDQSUyMDIlMmNvdSUzZEVDQSUyY28lM2RVLlMuJTIwR292ZXJubWVudCUyY2Ml
M2RVUz9jcm9zc0NlcnRpZmljYXRlUGFpcjtiaW5hcnkwDQYJKoZIhvcNAQEFBQADggEBAIP4M608
IEZJdXBySeHjlgiTtsQTq9xo6icy9Fa/zaJag+SoGitVohk26JAX44c+WsTdOmjnqCROFMwRDz3O
Qa5QBLt5+PGbsZhL+s1L4XLh6+961ALZxMi88jiIcR71uBnZqm3WnImmf0ebnK4N8N8ZJbQfncbj
ZlOOPo5NuVhEi22Mq8LHZd6UMl9xdSVAcHBV0F+sEBPY6S8OwptTz7+XusknKSkVPthJEEYnpHpk
pcBVe9HY2M421E8MSYeXZxuKvEjNMMRk2pkH8lOWU1uKsNCjHQYvK7GJtptFpc5aKbOIgI/jSrSr
qjcybZreD76lb1vZ8lcbHsnG+k22CCAwggVwMIIEWKADAgECAgEPMA0GCSqGSIb3DQEBBQUAME0x
CzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0VDQTEWMBQG
A1UEAxMNRUNBIFJvb3QgQ0EgMjAeFw0xMTA2MDExMzQzMzNaFw0xNzA1MzAxMzQzMzNaMHAxCzAJ
BgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0VDQTEiMCAGA1UE
CxMZQ2VydGlmaWNhdGlvbiBBdXRob3JpdGllczEVMBMGA1UEAxMMT1JDIEVDQSBTVyA0MIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzKf8xTQCX42GoA1+9NcUaSukI0Wu64bUdlPwiBNa
U0gEdQSDX7GDR7dvm4tEh+EsGetV8PYTKgjAT8tOSSaXnqxM9MaQ25Kg89jQ6gZtNq8HXERajlkJ
/Dn9wCySqKQBemUpHhdY+yhQikJSJ7QCMif3Pkx8mSSQ9DbOElK5kJgbJt6tJBJdOpU+zByz07+S
15AfuT2soQCVFhF6v4lBISwwbLU2g9TRjpXiDLL94tV9NWpgfRssDdr/5CpXxrhkKRQFotEGmwuI
TH1IzNte2xkEtP79VVddcwaUZRBMx9MyYEEA11kMvle70Wy2r9myt6FsLzUyRoW9glh2oexa5QID
AQABo4ICNjCCAjIwEgYDVR0TAQH/BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwHQYDVR0OBBYE
FEKc9Lpvbekw1zrWRvSyNO6d0k8mMB8GA1UdIwQYMBaAFO3kh9AnxFDmhDr3zPfrOkn8Uk4hMDMG
A1UdIAQsMCowDAYKYIZIAWUDAgEMATAMBgpghkgBZQMCAQwCMAwGCmCGSAFlAwIBDAMwgcAGA1Ud
HwSBuDCBtTAsoCqgKIYmaHR0cDovL2NybC5kaXNhLm1pbC9jcmwvRUNBUk9PVENBMi5jcmwwgYSg
gYGgf4Z9bGRhcDovL2NybC5nZHMuZGlzYS5taWwvY24lM2RFQ0ElMjBSb290JTIwQ0ElMjAyJTJj
b3UlM2RFQ0ElMmNvJTNkVS5TLiUyMEdvdmVybm1lbnQlMmNjJTNkVVM/Y2VydGlmaWNhdGVSZXZv
Y2F0aW9uTGlzdDtiaW5hcnkwgdMGCCsGAQUFBwEBBIHGMIHDMDoGCCsGAQUFBzAChi5odHRwOi8v
Y3JsLmRpc2EubWlsL2lzc3VlZHRvL0VDQVJPT1RDQTJfSVQucDdjMIGEBggrBgEFBQcwAoZ4bGRh
cDovL2NybC5nZHMuZGlzYS5taWwvY24lM2RFQ0ElMjBSb290JTIwQ0ElMjAyJTJjb3UlM2RFQ0El
MmNvJTNkVS5TLiUyMEdvdmVybm1lbnQlMmNjJTNkVVM/Y3Jvc3NDZXJ0aWZpY2F0ZVBhaXI7Ymlu
YXJ5MA0GCSqGSIb3DQEBBQUAA4IBAQCD+DOtPCBGSXVwcknh45YIk7bEE6vcaOonMvRWv82iWoPk
qBorVaIZNuiQF+OHPlrE3Tpo56gkThTMEQ89zkGuUAS7efjxm7GYS/rNS+Fy4evvetQC2cTIvPI4
iHEe9bgZ2apt1pyJpn9Hm5yuDfDfGSW0H53G42ZTjj6OTblYRIttjKvCx2XelDJfcXUlQHBwVdBf
rBAT2OkvDsKbU8+/l7rJJykpFT7YSRBGJ6R6ZKXAVXvR2NjONtRPDEmHl2cbirxIzTDEZNqZB/JT
llNbirDQox0GLyuxibabRaXOWimziICP40q0q6o3Mm2a3g++pW9b2fJXGx7JxvpNtgggMIIGOTCC
BSGgAwIBAgICMX0wDQYJKoZIhvcNAQEFBQAwcDELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g
R292ZXJubWVudDEMMAoGA1UECxMDRUNBMSIwIAYDVQQLExlDZXJ0aWZpY2F0aW9uIEF1dGhvcml0
aWVzMRUwEwYDVQQDEwxPUkMgRUNBIFNXIDQwHhcNMTMwNDIzMjA1MDI5WhcNMTYwNDIyMjA1MDI5
WjCBhjELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRUNB
MQwwCgYDVQQLEwNPUkMxFDASBgNVBAsTC1FvU2llbnQgTExDMSswKQYDVQQDEyJCdWxsYXJkLldp
bGxpYW0uQy5PUkMxMDAwMDM3MTAxLklEMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
uVgzvMTViFK3KLdCW8Ah9TtLt57dyDCaw2yroulxbhKpJVXv5lpLt/h0WFgYdOKOohJn9zA8ngRO
9BRocofISpQmLV/dqJg1a0zrTRHAxbQvJIihZ1/hIcC9/+iA/4ZEKUwVdcd619V70w6+wsh3UIQj
DLJsB7Zrs2bAsEjaJ+SoBCrvNiSCpV6D/32/bV2B/gnZ/5a09jasJEIYGbKVVp9f/SVh8XV5DSSu
ppsb7ZCaKnNgwGLeIpwS3iRa6FqAMJK6K07F5EYeltjXb006U5rwk00dvoqvww3vV/D9sgjeuNYj
va0uKxJ3E8t7p493CG4bzs7SW6aRaFOe5XPANwIDAQABo4ICxDCCAsAwHwYDVR0jBBgwFoAUQpz0
um9t6TDXOtZG9LI07p3STyYwHQYDVR0OBBYEFC7uy3C6OCsNX5V3mBpvbPf/B4keMIIBIwYIKwYB
BQUHAQEEggEVMIIBETAeBggrBgEFBQcwAYYSaHR0cDovL2V2YS5vcmMuY29tMDIGCCsGAQUFBzAC
hiZodHRwOi8vZWNhLm9yYy5jb20vY2FDZXJ0cy9FQ0EtU1c0LnA3YzCBugYIKwYBBQUHMAKGga1s
ZGFwOi8vZWNhLWRzLm9yYy5jb20vY24lM2RPUkMlMjBFQ0ElMjBTVyUyMDQlMmNvdSUzZENlcnRp
ZmljYXRpb24lMjBBdXRob3JpdGllcyUyY291JTNkRUNBJTJjbyUzZFUuUy4lMjBHb3Zlcm5tZW50
JTJjYyUzZFVTP2NBQ2VydGlmaWNhdGU7YmluYXJ5LGNyb3NzQ2VydGlmaWNhdGVQYWlyO2JpbmFy
eTAOBgNVHQ8BAf8EBAMCBsAwHQYDVR0RBBYwFIESY2FydGVyQHFvc2llbnQuY29tMBcGA1UdIAQQ
MA4wDAYKYIZIAWUDAgEMATCB8QYDVR0fBIHpMIHmMCugKaAnhiVodHRwOi8vZWNhLm9yYy5jb20v
Q1JMcy9PUkNFQ0FTVzQuY3JsMIG2oIGzoIGwhoGtbGRhcDovL2VjYS1kcy5vcmMuY29tOjM4OS9j
biUzRE9SQyUyMEVDQSUyMFNXJTIwNCUyQyUyMG91JTNEQ2VydGlmaWNhdGlvbiUyMEF1dGhvcml0
aWVzJTJDJTIwb3UlM0RFQ0ElMkMlMjBvJTNEVS5TLiUyMEdvdmVybm1lbnQlMkMlMjBjJTNEVVM/
Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdDtiaW5hcnkwGwYDVR0JBBQwEjAQBggrBgEFBQcJBDEE
EwJVUzANBgkqhkiG9w0BAQUFAAOCAQEAHi35mJzjiIIok76AITqnPNaWmW8J6CQnss/fVgXpcfAJ
OqM0UX6OEzc638AmGpTL5f3yI0b0daetLCEvOK/4v4Tw9HHTpfHRa1g64JoEDyNgAG/oCH2HDviP
ybd1C1/2OZB969gUoxvd0VdhKFI3ZF/mCCmdv+CBbvTCFpBXkeDkglC9IUHotxu6n+ZqKzZTVn3v
2T+2IwW6Pn++i6Gyak9QBQAKPJWovOlO5y4fS5yjOEshZWCdmkKQOj48oorv09gOfNpFFR9KtlTh
tpal1Lf+7c+XHXMKdrnRvYzYLqdklL27qAze4AiW1/Fj0IRfQ17YiylEE4F2BZSCcOLq0TCCBj4w
ggUmoAMCAQICAjF+MA0GCSqGSIb3DQEBBQUAMHAxCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMu
IEdvdmVybm1lbnQxDDAKBgNVBAsTA0VDQTEiMCAGA1UECxMZQ2VydGlmaWNhdGlvbiBBdXRob3Jp
dGllczEVMBMGA1UEAxMMT1JDIEVDQSBTVyA0MB4XDTEzMDQyMzIwNTE1MloXDTE2MDQyMjIwNTE1
MlowgYsxCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0VD
QTEMMAoGA1UECxMDT1JDMRQwEgYDVQQLEwtRb1NpZW50IExMQzEwMC4GA1UEAxMnQnVsbGFyZC5X
aWxsaWFtLkMuT1JDMTAwMDAzNzEwMS5FbmNyeXB0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEA0KufbZ9gPXn75bWXHqJsr49YLh0gkRXxWIUg5pUWkpnbqlxKmaXu97U2syVtCThHzzMr
9jb93pGVe9qgqsgeaPmI6UN0NHWlPlkfMZfib4PSmp9gFxDxaTCXGtxBJs1HGR/XHd7d34P17RKv
ucgajz1KkZgp8GMRj2qL1SZAQcZCRt5O4XxVIbl+BL3mKdEtSk24NUtTT9WjwVSHHoonZzsTBbkz
7gBcgP+a7vE/1W9KBAnn0RGtPeqCHz9PUFHhjYGzloKxD8lI4Y+UFX6n5uW56b80LsqV+1mfl5Dy
FwfBegaO69dwtUzcqJ95doauexSFe22y7yU3v+7TcYarRwIDAQABo4ICxDCCAsAwHwYDVR0jBBgw
FoAUQpz0um9t6TDXOtZG9LI07p3STyYwHQYDVR0OBBYEFEmIoE5Wahgjz6mivsXWwtbvptwGMIIB
IwYIKwYBBQUHAQEEggEVMIIBETAeBggrBgEFBQcwAYYSaHR0cDovL2V2YS5vcmMuY29tMDIGCCsG
AQUFBzAChiZodHRwOi8vZWNhLm9yYy5jb20vY2FDZXJ0cy9FQ0EtU1c0LnA3YzCBugYIKwYBBQUH
MAKGga1sZGFwOi8vZWNhLWRzLm9yYy5jb20vY24lM2RPUkMlMjBFQ0ElMjBTVyUyMDQlMmNvdSUz
ZENlcnRpZmljYXRpb24lMjBBdXRob3JpdGllcyUyY291JTNkRUNBJTJjbyUzZFUuUy4lMjBHb3Zl
cm5tZW50JTJjYyUzZFVTP2NBQ2VydGlmaWNhdGU7YmluYXJ5LGNyb3NzQ2VydGlmaWNhdGVQYWly
O2JpbmFyeTAOBgNVHQ8BAf8EBAMCBSAwHQYDVR0RBBYwFIESY2FydGVyQHFvc2llbnQuY29tMBcG
A1UdIAQQMA4wDAYKYIZIAWUDAgEMATCB8QYDVR0fBIHpMIHmMCugKaAnhiVodHRwOi8vZWNhLm9y
Yy5jb20vQ1JMcy9PUkNFQ0FTVzQuY3JsMIG2oIGzoIGwhoGtbGRhcDovL2VjYS1kcy5vcmMuY29t
OjM4OS9jbiUzRE9SQyUyMEVDQSUyMFNXJTIwNCUyQyUyMG91JTNEQ2VydGlmaWNhdGlvbiUyMEF1
dGhvcml0aWVzJTJDJTIwb3UlM0RFQ0ElMkMlMjBvJTNEVS5TLiUyMEdvdmVybm1lbnQlMkMlMjBj
JTNEVVM/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdDtiaW5hcnkwGwYDVR0JBBQwEjAQBggrBgEF
BQcJBDEEEwJVUzANBgkqhkiG9w0BAQUFAAOCAQEAi8sBhl4hOnT1puxe0CiOKgkFfMybOPqCPjfi
/Rm+OVZFk2uCFnTqZBePzqDjkH/SDdv8hZyLySDEoLbJuH8NzW2pHWP7+anW46Bxfpkm4WGf33S7
VorBXhZvwd3kktNzHiX2hEPZs/V4PGhlHMekqcq6TvKxKYWBix5bq0mcaelycj2mC9UTUm3SBwJm
rp83IgUrJgI6Ow+6SQduYQX/KSFxyTXnr6XZzWTo/c6HOH1oG1TlLnX32l7ZlosBdBkK8IhYoWbB
DnDehnii9X2jpFLAH3aPQ379m/kzP2rkIq1DZnNMRwL6Cl4QxNmQZbGCThh8iq3NG4A5pQqd94lf
aDGCAxAwggMMAgEBMHYwcDELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEM
MAoGA1UECxMDRUNBMSIwIAYDVQQLExlDZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVzMRUwEwYDVQQD
EwxPUkMgRUNBIFNXIDQCAjF9MAkGBSsOAwIaBQCgggFvMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTEzMDgxNjE3NTcxOFowIwYJKoZIhvcNAQkEMRYEFHPRhVdOtog8
qVXtCA7JNt+SFYaQMIGFBgkrBgEEAYI3EAQxeDB2MHAxCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9V
LlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0VDQTEiMCAGA1UECxMZQ2VydGlmaWNhdGlvbiBBdXRo
b3JpdGllczEVMBMGA1UEAxMMT1JDIEVDQSBTVyA0AgIxfjCBhwYLKoZIhvcNAQkQAgsxeKB2MHAx
CzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0VDQTEiMCAG
A1UECxMZQ2VydGlmaWNhdGlvbiBBdXRob3JpdGllczEVMBMGA1UEAxMMT1JDIEVDQSBTVyA0AgIx
fjANBgkqhkiG9w0BAQEFAASCAQCkJiMfCeHBvlXePgsPshFc2dRpua9hvRHCk3GVnY7IAVnRxxe5
YLbyjEspXRhYqnmdB8pkwZasRVlku7Tbt3IgX/vXcFzFLZjnJgTv1ZcCIHcU0PcK12kfP6h5fijz
EhpqfrE43mOILWM8m+aUE/pSsU7WS0T2IDa5kGs6qyIeTQofj7vIdEJDRiYwqeUq0/gYwqeTfiG1
tQQoLxypgkbJICcezOLhTZ6ObvSSn9UpP5DiCDjffS7jEzmbllQoOoL2ktacWy3LNB1cMcsOvXid
GT5S0dksz4MgfYiH/y26rCJ+Su2GZGTAJKUIyY6gO6Sq3IyCrh9e0XPCrR1Ohro0AAAAAAAA

--Apple-Mail=_69F64EE4-81C0-425F-8C9E-CD3C38D0CCEC--

From ben@nostrum.com  Fri Aug 16 14:13:46 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC65B11E8159; Fri, 16 Aug 2013 14:13:46 -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 7ZLx2AYDsc0F; Fri, 16 Aug 2013 14:13:46 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1FF2311E8158; Fri, 16 Aug 2013 14:13:46 -0700 (PDT)
Received: from [172.20.10.7] (mobile-166-147-071-199.mycingular.net [166.147.71.199]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7GLDbB9039117 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 16 Aug 2013 16:13:38 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 16 Aug 2013 16:13:32 -0500
Message-Id: <F0728D4E-4DEA-47B4-BA75-CCDB9C562924@nostrum.com>
To: draft-ietf-karp-ops-model.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 166.147.71.199 is authenticated by a trusted mechanism)
Cc: gen-art@ietf.org, IETF-Discussion list <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-karp-ops-model-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 21:13:47 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document:  draft-ietf-karp-ops-model-07.txt
Reviewer: Ben Campbell
Review Date: 2013-08-16
IETF LC End Date: 2013-08-18
IESG Telechat date:=20

Summary: This draft is almost ready for publication as an informational =
RFC. I have a few clarity related comments that might be worth =
considering prior to publication.

Major issues:

None.


Minor issues:

-- This abstract claims that this draft is a discussion of issues. =46rom =
that perspective, I don't think the use of 2119 language is appropriate. =
There are some specific areas (mentioned below) where 2119 language is =
used in imprecise ways, and may do harm to the reader's understanding. =
There are other uses that may be more reasonable. But I think the draft =
would be better off dispensing with 2119 language altogether.

-- Section 3, paragraph 4:

This seems like a place where descriptive language would be better than =
2119 language. In particular, "and so on" leaves things too open ended =
and imprecise. Also, the use of 2119 language in an example seems a bit =
off.

-- section 3.1, last paragraph:

I'm not sure what guidance is intended in this paragraph. It offers an =
example, then refutes it. Are there better examples to offer? Is the =
point that one shouldn't make such checks?

-- section 3.2, paragraph 2:

What distinguishes SHOULD from "desirable" in this context? That is, why =
use 2119 language for one and not the other?

-- section 3.2, last paragraph: "Implementations SHOULD permit a =
configuration in which if no unexpired key is available, existing =
security associations continue using the expired key with which they =
were established."

This may need further guidance. For example, it seems risky to do this =
silently.

-- section 3.3, last paragraph: "... then there is complexity in key =
management protocols."

Can you elaborate? Too much complexity? Are there key management systems =
that are not complex?

-- section 4, 2nd to last paragraph:

Seems like other disadvantages are worth mentioning. For example, the =
potential impact of a compromised CA.

-- 4.1:

I understand why one might choose not to include a real-world example =
here, but is there something that can be referenced?

-- 4.4, 2nd paragraph: "... it will be critical to make sure that they =
are not required during routine operation or a cold-start of a network."

Can you elaborate on why?


Nits/editorial comments:

Abstract: Might be worth mentioning KARP and how this draft fits with =
others.

-- Section 1, paragraph 1: Please expand KARP on first mention.

-- Section 1, paragraph 3: Missing punctuation.

-- section 3:=20
The text seems to rather abruptly start talking about key considered =
actions with little background. A quick summary of how these keys re =
used would be helpful.

-- section 3, paragraph 2: "Each OSPF link needs to use the same =
authentication configuration, ..."

Same configuration as what? The sentence appears to say keys must be the =
same among links but can be different.

-- section 3.2, first 2 paragraphs:

I'm not sure how a configuration management system and a configuration =
interface differ for the purposes of this discussion.

-- 4.1, paragraph 4: "Preshared keys that are used via automatic key =
management have not been specified for KARP."

I'm not sure what's intended here--if they are not specified why does =
the paragraph go on to talk about them?

-- 4.4, 1st paragraph: "... like RADIUS or directories."

Is there a word missing?=20

-- 5, bullet list of management objects:

There may be management objects implied by the second and third bullets, =
but they are not mentioned as such. Can you explicitly state them? For =
example, in bullet 2 is the "peer" the object being discussed? Or is it =
the "name or key". In bullet 3, is "group" the managed object, rather =
than "routing protocol"?

-- 5, paragraphs 7 and 8:

s/what/which  (two occurrences)
=20


From david.black@emc.com  Sat Aug 17 08:23:35 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 010D911E8160; Sat, 17 Aug 2013 08:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 9I8LUnnJ425G; Sat, 17 Aug 2013 08:23:30 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id ED3DE11E815A; Sat, 17 Aug 2013 08:23:29 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7HEJEVs019625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Aug 2013 10:19:14 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sat, 17 Aug 2013 10:19:03 -0400
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7HEJ22i011575; Sat, 17 Aug 2013 10:19:02 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Sat, 17 Aug 2013 10:19:01 -0400
From: "Black, David" <david.black@emc.com>
To: "emcmurry@computer.org" <emcmurry@computer.org>, "ben@nostrum.com" <ben@nostrum.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Date: Sat, 17 Aug 2013 10:18:59 -0400
Thread-Topic: Gen-ART review of draft-ietf-dime-overload-reqs-10
Thread-Index: Ac6bVLdI1RcyJR65QjGW3iUjaKrpUQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C489319@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "bclaise@cisco.com" <bclaise@cisco.com>, "dime@ietf.org" <dime@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-dime-overload-reqs-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: Sat, 17 Aug 2013 15:23: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-dime-overload-reqs-10
Reviewer: David L. Black
Review Date: August 17, 2013
IETF LC End Date: August 16, 2013
IESG Telechat date: (if known)

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

This draft describes scenarios in which Diameter overload can occur and pro=
vides
requirements for development of new overload control functionality in Diame=
ter.
It is well written, and the inclusion of scenarios in which overload can oc=
cur,
both in terms of the relationships among types of Diameter nodes and actual=
 mobile
network experience is very helpful.

I apologize for this review being a day late, as I've been on vacation for =
most
of this draft's IETF Last Call period.

Major issues: (none)

Minor issues: (none)

Nits/editorial comments:

The following two comments could be minor issues, but I'm going to treat th=
em
as editorial, as I expect that they will be addressed in development of the
actual overload functionality:

a) I assume that overload control development work will derive more specifi=
c
security requirements - e.g., as REQ 27 is stated at a rather high level.
The discussion in security considerations section seems reasonable.

b) The draft, and especially its requirements in Section 7 are strongly
focused on individual Diameter node overload.  That's necessary, but overlo=
ad
conditions can be broader, affecting an entire service or application, or
multiple instances of either/both, even if not every individual Diameter no=
de
involved is overloaded.  A number of the requirements, starting with REQ 22
could be generalized to cover broader overload conditions.

This (b) has implications for other requirements, e.g., REQ 13 should also =
be
generalized beyond a single node to avoid increased traffic in an overload
situation, even from a node that is not overloaded by itself.  There are li=
mits
on what is reasonable here, as the desired overload functionality is TCP/SC=
TP-
like reaction to congestion where individual actions taken by nodes based o=
n
the information they have (which is not the complete state of the network)
results in an overall reduction of load.

Section 1.2, 2nd paragraph:

   as network congestion, network congestion can reduce a Diameter nodes

"nodes" -> "node's"

Section 5, 1st paragraph:

 This inadequacy may, in turn, contribute to broader congestion collapse=20

"collapse" is not the right word here - I suggest "issues", "impacts",
"effects" or "problems".

Section 7

The long enumerated list of requirements is not an easy read.  It would be
better if these could somehow be grouped by functional category, e.g.,
security, transport interactions, operational/administrative, etc.

idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - this is fine=
,
as the boilerplate has been appropriately modified for this draft that
expresses requirements (as opposed to a draft that specifies a protocol).

idnits 2.12.17 got confused by the 3GPP and GSMA Informative References.
I assume that they're all sufficiently stable to be informative references.
However, [TR23.843] is a work in progress, and should be noted as such in
its reference - is this needed for any of the other 3GPP or GSMA references=
?

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


From david.black@emc.com  Mon Aug 19 06:08:55 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FD8111E827A; Mon, 19 Aug 2013 06:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tUwSZBWAfM4E; Mon, 19 Aug 2013 06:08:47 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id A8A0511E826F; Mon, 19 Aug 2013 06:08: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 r7JD80FS005380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Aug 2013 09:08:02 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 19 Aug 2013 09:07:48 -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 r7JD7l9m025893; Mon, 19 Aug 2013 09:07:47 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub02.corp.emc.com ([10.254.141.104]) with mapi; Mon, 19 Aug 2013 09:07:47 -0400
From: "Black, David" <david.black@emc.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Date: Mon, 19 Aug 2013 09:07:46 -0400
Thread-Topic: [karp] IANA policy for  draft-ietf-karp-crypto-key-table-08
Thread-Index: Ac6aqrVVQtelCuouRdyi7Cd0ThxhZgCMHC6g
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C4893A1@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com> <tslob8x345i.fsf@mit.edu>
In-Reply-To: <tslob8x345i.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [Gen-art] [karp] IANA policy for draft-ietf-karp-crypto-key-table-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 13:08:55 -0000

> I'm somewhat uncomfortable with that sort of bar for IANA registries in
> general, although I have supported it from time to time.  (My discomfort
> with this has grown significantly since my time as an AD).  I do not
> support that sort of bar for this registry.
>=20
> I think we understand each other, but disagree.

I believe that is the case (we understand each other, but disagree).

> The question now is whether you can gain sufficient support to show
> rough consensus for a change in the document or to show that while there
> was rough consensus behind the document in the KARP WG, there's a lack
> of consensus on handling this issue between KARP and some other
> significant segment of the IETF like the security area.

I will simply point to RFC 3365 ("Strong Security Requirements for
Internet Engineering Task Force Standard Protocols") and suggest that it
is relevant to determining what the registration procedure should be
based on how this registry is likely to be used and as an example of
reasons for the IESG to not follow the rough consensus of a WG.

I believe that a discussion of how the registry is likely to be used
in practice would be productive, although I am concerned about statements
that weak password mechanisms are intended to be in scope, even though
the draft (as I read it) excludes them, starting with the draft's title.

Thanks,
--David


> -----Original Message-----
> From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
> Sent: Friday, August 16, 2013 2:03 PM
> To: Black, David
> Cc: Sam Hartman; housley@vigilsec.com; tim.polk@nist.gov; Dacheng Zhang
> (zhangdacheng@huawei.com); General Area Review Team (gen-art@ietf.org);
> karp@ietf.org; ietf@ietf.org
> Subject: Re: [karp] IANA policy for draft-ietf-karp-crypto-key-table-08
>=20
> >>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
>=20
>     Black,> done.  IMHO, we really should be setting a bar that says
>     Black,> that this sort of IETF imprimatur of approval of a crypto
>     Black,> algorithm actually means something.
>=20
>=20
>=20
> Something got manged there.
> I agree that publishing a standards-track document  should endorce the
> algorithm in question.
>=20
> I'm somewhat uncomfortable with that sort of bar for IANA registries in
> general, although I have supported it from time to time.  (My discomfort
> with this has grown significantly since my time as an AD).  I do not
> support that sort of bar for this registry.
>=20
> I think we understand each other, but disagree.
>=20
> The question now is whether you can gain sufficient support to show
> rough consensus for a change in the document or to show that while there
> was rough consensus behind the document in the KARP WG, there's a lack
> of consensus on handling this issue between KARP and some other
> significant segment of the IETF like the security area.


From david.noveck@emc.com  Mon Aug 19 12:56:52 2013
Return-Path: <david.noveck@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 2F0E611E82BA; Mon, 19 Aug 2013 12:56:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, J_CHICKENPOX_23=0.6, J_CHICKENPOX_29=0.6, J_CHICKENPOX_46=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 xTx5fIlZnQcS; Mon, 19 Aug 2013 12:56:14 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9947B21F9A35; Mon, 19 Aug 2013 12:56:11 -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 r7JJtbhx028496 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Aug 2013 15:55:44 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 19 Aug 2013 15:55:12 -0400
Received: from mxhub27.corp.emc.com (mxhub27.corp.emc.com [10.254.110.183]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7JJtBZK004440; Mon, 19 Aug 2013 15:55:11 -0400
Received: from mx31a.corp.emc.com ([169.254.1.238]) by mxhub27.corp.emc.com ([10.254.110.183]) with mapi; Mon, 19 Aug 2013 15:55:10 -0400
From: "Noveck, David" <david.noveck@emc.com>
To: Thomas Haynes <loghyr@gmail.com>, Elwyn Davies <elwynd@dial.pipex.com>
Date: Mon, 19 Aug 2013 15:55:08 -0400
Thread-Topic: Gen-art additional review of draft-ietf-nfsv4-rfc3530bis-25
Thread-Index: Ac6ay7IZNN/9U+82R5SGYjHbtkd4iwCRQ9Eg
Message-ID: <5DEA8DB993B81040A21CF3CB332489F607B5AAD7D7@MX31A.corp.emc.com>
References: <C5D71833-AD50-47F2-8BB9-2E5FFF03CF2E@gmail.com>
In-Reply-To: <C5D71833-AD50-47F2-8BB9-2E5FFF03CF2E@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5DEA8DB993B81040A21CF3CB332489F607B5AAD7D7MX31Acorpemcc_"
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 19 Aug 2013 13:40:38 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-nfsv4-rfc3530bis.all@tools.ietf.org" <draft-ietf-nfsv4-rfc3530bis.all@tools.ietf.org>, "nfsv4 list \(nfsv4@ietf.org\)" <nfsv4@ietf.org>
Subject: Re: [Gen-art] Gen-art additional review of draft-ietf-nfsv4-rfc3530bis-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 19:56:52 -0000

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

I have some comments on the XXX items.

> so... should the client be able to find out which version of Unicode the =
server is working to?

The problem with this is that the way to do this is a new attribute and tha=
t the minor versioning rules as now written preclude adding such a new attr=
ibute in v4.0. , giving that v4.1 exists and v4.2 almost exists.  Those rul=
es could be modified but it would be very hard to reach consensus on such a=
 change, so I'd prefer we not open up that can of worms, unless it were rea=
lly necessary, and not just a nice-to-have.

Also, this needs to be looked at in the context of the new (really old) I18=
N chapter in -27.   The goal of that is to describe what actual NFSv4.0 ser=
vers and clients actually do,  making adding a new attribute that none of t=
hem has asked for pretty much out of bounds.

Maybe we can defer this discussion until we consider the new I18N chapter i=
n a later pass of the process.

> s6.3.1.2: Is there any interaction between delegation and client consider=
ations for ACLs? Do
> clients holding delegations have to do any access checks in the client th=
at would normally be
> done in the server if there was no delegation?  I'm not sure

The client doesn't have to do any access checks.  If it doesn't want to do =
ACL Interpretation it can do
an OPEN(CLAIM_DELEGATE_CUR) and let the server do it.

> - Is there any interaction between byte range locks and share reservation=
s?  e.g., does a client
> holding (say) a byte range write lock but with no DENY state prevent anot=
her client taking
> out a DENY_WRITE  share reservation on the same file?

I don't think it does.  I think the intention is that server implementation=
s can grant an open just
knowing about existing share reservations and delegations.


> This needs some tidying up.  One could try using 'data object' as an unam=
biguous term for the
> union of the actual file (NF4REG) class and the named attribute class.
I agree this needs tidying up.


From: Thomas Haynes [mailto:loghyr@gmail.com]
Sent: Friday, August 16, 2013 5:56 PM
To: Elwyn Davies
Cc: General Area Review Team; draft-ietf-nfsv4-rfc3530bis.all@tools.ietf.or=
g; nfsv4 list (nfsv4@ietf.org)
Subject: Re: Gen-art additional review of draft-ietf-nfsv4-rfc3530bis-25

Hi Elwyn,

Thank you for the detailed review. It has taken so long because even for th=
e
points which I disagreed with, I spent considerable time proving to myself
first your objection and second why I wasn't going to take the suggested ch=
ange.

Also, the WG needed to meet to agree with what to do with the i18n comments=
.

I've left XXX or xxx where other people in the WG might want to reply.

I'll be sending out a new version of the drafts by Aug 18th.

Tom

On May 8, 2013, at 3:35 PM, Elwyn Davies <elwynd@dial.pipex.com<mailto:elwy=
nd@dial.pipex.com>> wrote:



I am another Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq><http://wiki.tools=
.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document: draft-ietf-nfsv4-rfc3530bis-25
Reviewer: Elwyn Davies
Review Date: 8 May 2013
IETF LC End Date: -
IESG Telechat date: 30 May 2013

Summary:
This is a mammoth document.  The comments run to 650 lines.  Clearly there =
ae issues in modifying a -bis document given that it has to be pretty much =
compatible with its progenitor  - but that is now going on 14 years old. I =
believe that there are a significant number of minor issues to address and =
parts of the document (despite the overall size) need to provide a bit more=
 explanation of what is going on.  In particular I think that a little bit =
more rationale over the way in which an NFS server attempts to provide some=
thing like a common interface to the two big player filesystem types (*ix a=
nd Windows)

Outside of the scope of the document.



[Aside: I am disappointed that it doesn't try to handle versioning file sys=
tems like the venerable VAX filing system! ;-) ]  There are some areas wher=
e the addition of named attributes hasn't really been properly dealt with A=
FAICS. One major area that I felt ought to have been better addressed in th=
e -bis was internationalisation.

As agreed, this is being rewritten.

(BTW - this is why I've held off on replying.)



  As mentioned below, I don't understand why additional atrributes couldn't=
 be added to help clients understand what the server is doing with internat=
ionalisation - the client has to do some complex acrobatics which seem clos=
e to guesswork to work out what is going on in the server.


Which is actually a design mantra when it comes to NFS - we talk about dumb=
 servers and smart clients. We push the burden
to the client to figure out what to do.





  As ever, I am not an expert in NFSv4 (although I used v2 extensively almo=
st 30 years ago... arrrgghhh!) so there may well be comments where I don't =
understand the problem.

Major issues:

Overall section comments:
s6: AccessControl Attributes
Combining two different access control paradigms (UNIX-clone mode control b=
itmasks and access control lists) is an uphill struggle and provides a deal=
 of complexity in situations where both, either one or neither may be speci=
fied.  The detailed text deals reasonably with the various cases.  There ar=
e, in my view, a couple of significant problems:
- The first is essentially editorial:  I would say that rather more than ba=
sic understanding of UNIX-like file systems is needed.  An explanation or a=
t least a suitable reference to explain the use of the mode bits in s6.2.2,=
 especially the first three (SUID, SGID, SVTX) would help, and a clearer li=
nkage to the explanations of owner, group and other sets of users that are =
distributed in parts of the text.

It is more complex than that unfortunately - we had another document which =
discussed such issues and it atrophied off.

I'll look at resurrecting it, we actually have confusion in the community a=
s different vendors like to quote different revisions.






- The second is more fundamental:  The intended functionality of inheritanc=
e is not explicitly documented.  To come to any sort of understanding of ho=
w inheritance is supposed to work you have to read through to the next to t=
he last section (s6.4.3).  I have now read through the section two or three=
 times and I have a model in my mind, but there is no text that would allow=
 me to verify my understanding.  I *think* i have understood that (1) inher=
itance only applies when you initially create an object rather than being f=
ed through to all 'inferior' objects in the tree if a superior object has a=
 heritable ACE added; (2) inheritance only applies if you don't explicitly =
give any ACEs when the object is created, and (3) if you give a mode but no=
 ACL then some complex combination of inherited ACL and mode is applied.  A=
n upfront explanation of what is trying to be achieved would have helped a =
lot.  However, none of this explains what happens with either hard or symbo=
lic links.  It is unclear to me whether inheritance of ACLs is applied when=
 creating a hard or symbolic link to an existing object.

s7, Multi-Server Namespace:
This section is very verbose and contains a number of areas that bring in t=
opics that  are actually forward references without indicating where the in=
formation can be found, particularly in relation to various 'change classes=
'.  Some reordering might help.  The whole concept of change classes seems =
a little odd, because when they are finally defined (s7.9.1), it appears th=
at servers are rarely in the same class during any of the interesting trans=
itions (s7.9.1 says that in most cases they have to be taken as in differen=
t classes).  Overall, this section contains an awful lot of discursive spec=
ification relating to servers that may not have any coordination which make=
s it very difficult both from the specification and the implementation angl=
es to check that everything is working.


We brought this section forward from 5661 in order to provide some help in =
dealing with the migration issues implementors are having with 3550.

And I really want to thank your review here, I don't think we can make this=
 work at all. I've yanked it.




s8, NFS Server namespace:  This is a important section for overall understa=
nding and I think it would help to have it much earlier, certainly before s=
7.

We want to maintain as much section compatibility with 3550 as possible.




s9, File Locking and Share Reservations:
Generally very well written, but the treatment of share reservations is ver=
y skimpy,
It would also be good to be more 'honest' about the interaction with the se=
mantics of the underlying file system as regards locks as described in s15.=
12.

s10, Clientside Caching:
Clearly very complex to implement but seems to be well-described.  A bit of=
 earlier explanation of the use of CLAIM_PREVIOUS vs CLAIM_DELEGATION_PREV =
in client/server reboots would help.

s11, Minor Versions:
No particular issues.

s12, Internationalisation:
A minefield.  There seems to be an awful lot of guess work for clients tryi=
ng to decide how the sever behaves.  On reflection, I am surprised that sev=
eral of the things that clients are supposed to deduce (e.g., what normalis=
ation the server does) were not supplied as attributes of the server.  Is t=
here some good reason for this?  I was also surprised that there didn't see=
m to be a requirement that servers working on a particular filesystem all d=
id the same internationalisation things.  It appears to me that if a filesy=
stem gets migrated the client doesn't have any sort of guarantee that the i=
nternationalisation behaviour won't change under its feet - and it has no e=
asy way to check if this is or is not the case because of the lack of attri=
butes.  I have no idea to what extent the internationalisation is implement=
ed in current servers.

s13, Error Codes:
Generally OK but with a few code value inconsistencies.  I haven't checked =
the cross-consistency of Table 9 and Table 11 or whether the sets of error =
codes per operation are really right - they are just too voluminous.


They are machine generated from a common source.




s14, NFSv4 Requests:
No problems.

s15/16, Operations:
Generally in good shape apart from some issues with the meaning of 'regular=
 files'.

s17: Security:
I have some doubts about the Kerberos algorithms suggested.  Maybe should b=
e moving on to better algorithms even if this is a bis.


As discussed on the mailing list, we agreed and fixed it.

Again, here is where I would prefer we push this to another document which =
tracks which Kerberos algorithms should be used.





=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Minor issues:
S1.1, bullet 7: Are there issues with backwards compatibility after removal=
 of LIPKEY and SPKM-3 completely?

No, not a single vendor implemented these.




s1.5.1: Should NFSv4 be using RPCSEC_GSS v2 (RFC 5403) rather than v1 (RFC =
2203)?


It should be "and" and not "rather". v1 is not widely adopted, but nothing =
precludes its use.

I've updated the instances of references to include both.



s.1.5.3.2, para 4, and s5.3: It would be useful to say upfront in s1.5.3.2 =
whether the attribute names are fully internationalized or whether this is =
still an ASCII name.


I don't think anything precludes an internationalized name here since these=
 are in the directory space.



s2.1:  This section contains a number of symbolic constants (chiefly for op=
aque element sizes) which have not been defined as yet.  It would be highly=
 desirable if these were also defined before this section.

These are in the companion document.

We broke the XDR out starting with RFC 5661 - we've made the same effort
here as readers prefer having the other document to reference.




s2.1, utf8val_RECOMMENDED4:


 String SHOULD be sent UTF-8
What else could it be sent as in this type?


We will revisit with the i18n rewhack.




s2.2/s6.2.1:  The type nfsace4 is used in the protocol: Accordingly it ough=
t to be defined in s2.2 rather than s6.2.1.

Part of the XDR document.



s2.2.3/s5.8.2.34/s5.8.2.40: It would probably be nicer if the union case SE=
T_TO_SERVER_TIME4 were put into the union explicitly.  A note about being a=
ble to set the access and modify times to either client or server time woul=
d be appropriate in the two items in s5.8.2.  Are there any constraints on =
the values that can be given when setting from the client.. like not moving=
 the time backwards (or is this explained later?).

We can't change the enum or union at this point.

Given that there can be time skew, the server cannot tell if the client is =
moving things backward or not.

In this case, the server would assume that the client was correct and allow=
 the change.





s3.1, para 1:


 Using the registered port for NFS services

   means the NFS client will not need to use the RPC binding protocols

   as described in [RFC1833<http://tools.ietf.org/html/rfc1833>]; this will=
 allow NFS to transit firewalls.
I think some explanation of why this will definitively allow NFS to transit=
 firewalls is needed.


In NFSv3, there were several sideband protocols which did not sit on well d=
efined ports. Each
server vendor either picked a port or allowed for them to be configurable. =
As such, it is somewhat
unwieldily to configure firewalls.

With just using port 2049, it is easy to determine which single port needs =
to be open.




s3.1.1: Presumably the requirement to eschew silent dropping of 'requests' =
does not apply if security is being negotiated.  I take it 'requests' shoul=
d be interpreted as  'NFSv4 requests' and procedures as defined in s14/15 a=
nd this requirement should apply only once the secure connection is establi=
shed.  The word 'established' might help.


Yes, NFSv4 requests and established.

I can add both.





s3.2: (reprise) Should we be using RPCSEC_GSSv2 (RFC 5203) rather than v1?

Same reply as above.



s3.2.1.1: The Kerberos specifications appear to use rather ancient algorith=
ms.  In particular DES, MD5.. should there not be more  modern algorithms? =
 DES and MD5 get a pretty bad press these days.  RFC 2623 is also a bit of =
an antique so I can't say its a modern assessment.

Already taken care of.



s3.3.1,security poiicy boundaries etc:


 In general, the client will not have to use the SECINFO

   operation except during initial communication with the server or when

   the client crosses policy boundaries at the server.  It is possible

   that the server's policies change during the client's interaction

   therefore forcing the client to negotiate a new security triple.
 The  concept of 'security policy boundary' has not been previously discuss=
ed in the doc.  How would the client know it had crossed a security boundar=
y or that the server had changed the policy under its feet? I suppose maybe=
 the next section tells me... but... How does this interact with the no sil=
ent drop, mostly no retries requirement in s3.1.1? or have i to read s15.33=
.

I suspect that some discussion of the interaction of mount points and secur=
ity policy boundaries may be needed at an earlier stage.  I suspect that mo=
unt points might well be security policy boundaries and crossing mount poin=
ts might interact.  There is nothing in the description of mounted_on_filei=
d (s5.8.2.19).


I think this was an effort to avoid talking about exports.




s5.6, item lease_time:  I can't find a definition of nfs_lease4 type used f=
or this.

The accompanying XDR document has it.




s5.6, item rdattr_error: Just giving 'enum' as the type isn't too specific!

Agreed, I'll put nfsstat4




s5.8.2.25:


It is understood that this space may be

   consumed by allocations to other files or directories though there is

   a rule as to which other files or directories.
Where do I find the rule?

Yes, confusing. The next section illustrates that this is defined by the se=
rver.

I'll make it more explicit here.




s5.10, para 1:


although there are variations that occur additional characters with a

   name including "SMALL" or "CAPITAL" are added in a subsequent version

   of Unicode.
so... should the client be able to find out which version of Unicode the se=
rver is working to?

XXX



s6.3.1.2: Is there any interaction between delegation and client considerat=
ions for ACLs? Do clients holding delegations have to do any access checks =
in the client that would normally be done in the server if there was no del=
egation?  I'm not sure.

XXX



s7.5:


   If a single location entry designates multiple server IP addresses,

   the client cannot assume that these addresses are multiple paths to

   the same server.  In most cases, they will be, but the client MUST

   verify that before acting on that assumption.
How is the verification achieved?  I don't see any attributes within NFSv4 =
that would help.

A swear word needs to be inserted here.

It is possible in NFSv4.1, but not NFSv4.0. I've removed this section.




s7.7.6.1, para 3:


   If state has not been transferred transparently because the client ID

   is rejected when presented to the new server, the client should fetch

   the value of lease_time on the new (i.e., destination) server, and

   use it for subsequent locking requests.  However, the server must

   respect a grace period of at least as long as the lease_time on the

   source server, in order to ensure that clients have ample time to

   reclaim their lock before potentially conflicting non-reclaimed locks

   are granted.
How does the destination server know what the lease_time/grace period on th=
e source server was? It doesn't know what server the client was previously =
connected to in many cases and so can't ask.  Doesn't this amount to saying=
 all servers for a given file system should (MUST) be configured with the s=
ame lease time in the non-transparent transparent case?

It doesn't, it makes an assumption that they were the same.




s9.9: This section is a little skimpy.  There are several points that proba=
bly ought to be clarified:
- The section explicitly refers to files:  Does it actually apply to all fi=
lesystem objects?

No, just regular files.



- An explicit statement that the 'file_state' is maintained for each file(s=
ystem object)




- The pseudo-code applies to the OPEN case; different pseudo-code (presumab=
ly) applies to OPEN_DOWNGRADE.  I *think* I could guess it but it would be =
good to be explicit.

I'm happy enough without another example here.



- Is there any interaction between byte range locks and share reservations?=
  e.g., does a client holding (say) a byte range write lock but with no DEN=
Y state prevent another client taking out a DENY_WRITE  share reservation o=
n the same file?


XXX


- Does the discussion of placing lock state into stable storage across serv=
er reboot also apply to the share reservation file_state?

s9.14:  The text in this section addresses topics also covered in s7.  This=
 does  not seem desirable as there may be discrepancies (see next comment).=
  It would seem better to merge the text into s7 and possibly provide a ref=
erence back to s7 from s9.

s9.14.1:  This section envisages migration of state from one server to anot=
her where the client already has state on the other server using the same c=
lient ID.  Merging of the states is suggested.  AFAICS this situation is no=
t discussed in s7 which seems a little odd.

We are going to have a new document on migration come out based on this tex=
t.

I would prefer to keep this as is and allow those authors to drive that dis=
cussion.




s12:  It seems the client has to play '20 questions' with the server to fin=
d out how it treats internationalized component names.  Some of it seems li=
ttle better than guesswork.  I was wondering why some of the server choices=
 are not described using attributes so that the client doesn't have to thra=
sh around in the dark.  Also there doesn't seem to be any requirement for a=
 filesystem to be treated identically after migration. As far as I can see =
the client can't really rely on the internationalisation treatment not chan=
ging after migration.

Again, i18n is going to be addressed.



s18.1:  The NFSv4 Named Attribute Definitions registry has already been cre=
ated in exactly the form specified here by RFC 5661 (NFSv4.1).  This sectio=
n should be removed and words noting that the existing registry is common t=
o all minor versions of NFSv4  should be substituted.


I'd prefer to leave this as is because:

     IANA had created a registry called the "NFSv4 Named Attribute Definiti=
ons Registry"
     for <xref target=3D"RFC3530" /> and <xref target=3D"RFC5661" />. This =
section introduces no new
     changes, but it does recap the intent.





=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Nits/editorial comments:
General: Review the remaining instances of 'file' and 'files' to determine =
if they should really be 'filesystem objects'.

General: Consistency between 'file system' and 'filesystem'.  'filesystem' =
is used first in abstract and s1.3 but only File System is defined.  I cann=
ot see whether there is any real distinction between the usages... but  am =
open to argument! OTOH there is definitely inconsistency: Consider 'fsid' a=
nd 'fsid4' - the type definition says fsid4 is for a filesystem (s2.2.5) bu=
t s5.8.1.9 says this is about a 'file system'

And finally got to this one: "file system"!





General: The terms 'regular file' and 'named attribute' are not used unifor=
mly.  s5.8.1.2 typifies the confusion.  In the first set of bullets, NF4REG=
 is defined as 'a regular file' and NF4NAMEDATTR is defined as a Named Attr=
ibute.  In the last bullet, "is an[sic] regular file" is defined as implyin=
g either type NF4REG or NF4NAMEDATTR.
Thus we have the same term used for a set and a superset of the same set (m=
aybe when qualified with 'is a').  Consequently, for example in s15.25.4,  =
we have "the READ operation reads data from the regular file...".  Presumab=
ly this is supposed to cover both NF4REG and NF4NAMEDATTR types but one can=
't be absolutely sure (to be pedantic it doesn't explicitly say 'is a regul=
ar file' so perhaps it should be read as NF4REG only).  OTOH the OPEN opera=
tion (s15.18.5) has two separate paragraphs for regular files and named att=
ributes.  This needs some tidying up.  One could try using 'data object' as=
 an unambiguous term for the union of the actual file (NF4REG) class and th=
e named attribute class.


XXX



Abstract: s/owes heritage to/builds on the heritage of/

ok



s1.1: Expand IDNA acronym.

ok



s1.2, bullet 5:s/mounted_on_filed/mounted_on_fileid/

ok


s1.3: Expand acronyms ONCRPC and RPCSEC_GSS (and/or ref to RFC 2203 or 5403=
).

Fixed ONC RPC.

RPCSEC_GSS is not defined as an acronym



s1.5: s/the reader that is new/the reader who is new/

ok



s1.5.1, para 2: s/provides the client a method/provides the client with a m=
ethod/


ok


s1.5.3:  A couple of sentences outlining the presentational scheme for file=
system object names (i.e., /a/b/c etc) would be worthwhile even if 'we all =
know what this means'!  This could include defining 'component name' used l=
ater with no introduction.

s1.5.3.1, et seq: Would it be useful to identify 'persistent' and 'volatile=
' as key words: e.g., 'Persistent' and 'Volatile'.

s1.5.3.2, para 3: For consistency the 'acl' example should have a ref (s6.2=
.1) earlier in the para.  So s/((Section 6)/(Section 6.2.1)/ and move one s=
entence earlier.

ok


s1.5.5: There should be a discussion of share reservations in this section.

s1.6, definition of Lease: There should be a definition of 'grace period' (=
as per s9.6.2) as there are lots of references to it earlier than s9.6.2.

s1.6, definition of Lock:  There should be a definition of share reservatio=
n.

s2.1 et seq:  Whilst the terms 'hard link' and 'symbolic link' are pretty c=
ommonly known,  they are so fundamental that I think putting them in the de=
finitions would be highly desirable.


I'm okay with this as is.



s2.1, attrlist4:  In line with comment about opaque max sizes, should this =
have a max size? (Might also apply to bitmap4)

In the XDR



s2.2: It would be useful to have section references to the places where the=
 types are used where these are explicitly mentioned.

s2.2.8 (and s2.1):  I guess that the bit ordering in bitmap4 is implicitly =
derived from the XDR representation, but it would be useful  to remind peop=
le of what this bit ordering actually is.

s2.2.9, atomic element:  With a name like that are there any special handli=
ng requirements for this element/structure?

s2.2.10: Note  to self: verify external refs in this section.

s2.2.11, cb_program: It should be explained that the cb_program is an RPC p=
rogram number (had to ferret in s15.35.4 to understand this).  BTW this wou=
ld entail an earlier expansion of RPC acronym.

1.1 is the earliest (in newest draft.)

But okay with leaving this as is.




s2.2.12:  It would be good to have a definition of NFS4_OPAQUE_LIMIT before=
 this section (see earlier comment about s2.1) so that all the magic number=
 constants are concentrated in one place.

s2.2.13:  Arrgh! Now we have two definitions of NFS_OPAQUE_LIMIT (fortunate=
ly they are the same until they aren't).

s2.2.14: ARRRGGGHHH! THREE defs.

It is now only defined in the XDR document.




s2.2.16, 'other':  And this definition contains the magic number 12 not as =
a symbolic constant and with no explanation of why 12 is a good value!

No explanation, but provided a name for the magic number.




s3.1, para 2:


   Where an NFSv4 implementation supports operation over the IP network

   protocol, the supported transports between NFS and IP MUST be among

   the IETF-approved congestion control transport protocols, which

   include TCP and SCTP.
I know what is meant, but technically, I don't believe the IETF actually ha=
s a list marked 'congestion control transport protocols'.  A better way of =
phrasing this might be:
   Where an NFSv4 implementation supports operation over the IP network
   protocol, the supported transport layer between NFS and IP MUST be an IE=
TF
   standardised transport protocol that is specified to avoid network
   congestion; such  transports include TCP and SCTP.

ok


[Check whether SCTP is on the IANA well-known acronym list].

Also:
OLD:
to use a different IETF-approved congestion control transport protocol.
NEW:
to use a different IETF standardised transport protocol with appropriate co=
ngestion control.

ok



s3.1, para 3: Expand WAN acronym. (I think)

ok



s3.1, para 4:  Where would I find a justification that DCCP or NORM are ina=
dequate?

It must have been debated on the mailing list.

I know this came up again in the context of 3530bis and we determined that =
they were not adequate.




s3.1, para 5: s/regardless whether/regardless of whether/

ok



s3.1, para 6: A rather throwaway comment about avoiding timer sync.  Not su=
re yet how many timers, but it would be good to know which ones were critic=
al.  After reding the document I am still not sure.  It might almost be wor=
th adding a section that summarizes the set of timers used.

I think removing the comment altogether is better.


s3.2.1/s3.2.1.1: Check section title capitalization.  (Mostly OK - spotted =
also s6.4.1/s6.4.1.x - possibly)

ok




s4.2.1: Earlier parts of s4 have been generalised to talk about 'filesystem=
 objects'.  This section still has filehandles referring to 'files'.

ok




s4.2.3, para at top of p33; s4.3, para 4: Ditto talking about 'files'.

In this case, the context establishes that the filehandle is to a file.




s4.3, para 1:


   If possible, the client SHOULD recover from the receipt of an

   NFS4ERR_FHEXPIRED error.
I think this is a 'should' rather than a 'SHOULD'. Its not something that t=
he protocol designer has any control over.

ok



s5 title:  Attributes apply to more than just files.

ok



s5, para 4: s/new  OPENATTR operation/OPENATTR operation introduced in NFSv=
4/

I think just removing "new" suffices.




s5.1, last sentence: I think the 'must' is a 'MUST' - the server is constra=
ined to send the values if asked (but the client has a choice to ask or not=
).

Agreed.



s5.2:


A client MAY ask for the

   set of attributes the server supports and SHOULD NOT request

   attributes the server does not support.
This should probably be
   An operation allows the client to determine the set of attributes
   that the server supports; a client should not request attributes the
   server does not support.
Its not something the protocol can do anything about.

What I don't like here is what does the server do if the client requests
an attribute that is neither REQUIRED nor RECOMMENDED?

I.e., say the last supported attribute is X, and a client queries on X+2.

Should the server silently ignore this?

What if two different client implementations use that attribute to mean
different things?

For those reasons, I like the wording as is.



s5.8.1.4:s/may/MAY/

ok



s5.8.2.10, para 2: Not sure what root path has to do with locations.

This specifies how root path can be communicated.



s5.9, para 4:


 Servers that do not provide support for all possible values of the

   owner and owner_group attributes SHOULD return an error

   (NFS4ERR_BADOWNER) when a string is presented that has no

   translation, as the value to be set for a SETATTR of the owner,

   owner_group, or acl attributes.
What might the server do if it doesn't return NFS4ERR_BADOWNER? I would hav=
e thought this ought to be  MUST.

They might just accept it as untranslatable and not return an error.

As long as they give it back on the GETATTR, this is valid.




s5.9, para 5:


   The "dns_domain" portion of the owner string is meant to be a DNS

   domain name.  For example, user@example.org<mailto:user@example.org>.  S=
ervers should accept

   as valid a set of users for at least one domain.  A server may treat

   other domains as having no valid translations.  A more general

   service is provided when a server is capable of accepting users for

   multiple domains, or for all domains, subject to security

   constraints.
I suspect that the 'should' and 'may' ought to be 'SHOULD' and 'MAY'.  Argu=
ably the 'should' ought to be a 'MUST' if the server recognises owner and o=
wner_group as attributes. i.e., a mandatory to implement.

ok



s5.9, para 6:


In the absence of such a

   configuration, or as a default, the current DNS domain name should be

   the value used for the "dns_domain".
The term 'current DNS domain' is not very specific. Do you mean the DNS dom=
ain in which the host resides?

Yes, tried to make clearer



s5.9, 1st bullet point on page 50: A reference to (probably) RFC 5890 is ne=
eded to explain U-labels and other IDN stuff is needed (probably best in s1=
.6).

Added the reference, even though this may change.


s5.10: Expand UCS acronym (and add ref to ISO.10646-1.1993).

ok



s6.1, bullet 3:  An explanation of what is meant by (acl) inheritance is ne=
eded.

I'm okay with inheritance being well understood by the target audience.



s6.1, bullet 4, sub-bullet 1:


      *  Setting only the mode attribute should effectively control the

         traditional UNIX-like permissions of read, write, and execute

         on owner, owner_group, and other.
Does this extend to the interpretation of the x bit as searchability on dir=
ectory objects as per UNIX?


Yes, the next question is does it need to be explained? I think not.




s6.1, bullet 5:  Does mode setting affect the inherited ACL attributes as w=
ell as the those of the object for which the mode is set?

s6.2.1, next to last para: Expand SMB (and/or give reference).

expanded, getting correct reference



s6.2.1.1, sentence above table:


   All four but types are permitted in the acl attribute.
'but' is clearly not the right word but I am not quite sure what this tryin=
g to say.

'bit'




s6.2.1.3.1, ACE4_ADD_SUBDIRECTORY:
Why is the RENAME operation affected if the object being renamed is a file =
rather than a directory?


Good question,



s6.2.1.3.1, ACE4_EXECUTE:
Given that directory operation aliases for ACE4_READ_DATA and ACE4_WRITE_DA=
TA have been defined, it would seem sensible to define an alias for the dir=
ectory/traverse use case of ACE4_EXECUTE.

s6.2.1.3.1, ACE4_DELETE_CHILD and ACE4_DELETE:
s/for information on/for information on how/

ok



s6.2.1.3.1, ACE4_WRITE_ATTRIBUTES - file times modification:
Can the client find out if the server uses client or server times? I didn't=
 see an attribute that tells me which is allowed on the server - cansettime=
 only allows the client to find out if it can modify the times.  What happe=
ns (which error code comes back) if the SETATTR has the wrong sort of time =
spec (e.g., client time when the server only supports server times)? As pre=
viously mentioned, is the server expected to do any sanity checks on suppli=
ed client times (maybe not allowing - at least - ordinary users to set time=
s backwards from previous values.)

          Permission to change the times associated with a
          file or directory to an arbitrary value.

Which means to me that no sanity check need be applied.




s6.2.1.4: A few words on the effect of inheritance would help and and clari=
fy the next two comments.  Points that arise from the discussions in s6.2.1=
.4.1:
- Is there a time factor in ACEs?  The phrase 'newly created' seems to impl=
y that there is.  The document doesn't really explain how it is expected th=
at inheritance will be implemented: It could be seen as copying the current=
 set of ACEs from the parents up the tree at the time an object is created =
or tracking the ACEs up the tree when a access request has to be verified.
- Is the inheritance fully recursive down a directory tree?  I guess that i=
t is unless the NO_PROPAGATE flag is set.. but what about symbolic links?
- Does the inheritance propagate across mount points?

Define what you mean by mount point. Remember that a mount point is a clien=
t
side artifact and not a server one.

If you however consider a server which has a namespace in which one filesys=
tem
is mounted on another and that is exported to the client as a single namesp=
ace,
then my expectation is that the inheritance is not propagated across the
filesystems.




Additionally, how does ACE inheritance interact with hard and symbolic link=
s?  Does the inheritance attach to the underlying object or only to the nam=
e path?

s6.2.1.4.1, ACE4_FILE_INHERIT_ACE:
Three issues:
- presumably this implies the ACE is (primarily) inherited by files in the =
directory to which it applies
- does 'any sub-directory' imply that the inheritance applies recursively d=
own the tree?
- does 'any non-directory file' include symbolic links?

s6.2.1.4.1, ACE4_DIRECTORY_INHERIT_ACE:
Three issues:
- Does 'should be added to each *new* directory created' imply that the ACE=
 does not get inherited by sub-directories are already in existence when th=
e ACE is applied? Either way it would be good to be explicit about the effe=
ct.
- Does this apply recursively down the tree?
- Would the inheritance apply to symbolic links to directories?

s6.2.2:
It would be worth pointing out that the execute permission bits imply searc=
hability for directory objects.  This isn't mentioned in READDIR... is this=
 something missing?

Those are POSIX semantics.




s6.2.2:
Are there restrictions on the mode bits that can be set on named attributes=
 and their directories?  Wouldn't make a lot of sense to set the x bits on =
named attributes  (probably), nor the suid and svtx bits.

The mode bits set on a named attribute would be those on the base file.




s6.3.1.2, para 1: s/interpretation the ACL/interpretation of the ACL/

ok



s6.1, last para: Expand DCE/DFS acronyms.

deleted



s6.2: Expand TLS and SPKM acronyms. (IPsec is 'well-known')

deleted, but I did expand TLS in another place.



s7.1:


These attributes specify such file system

   instances by specifying a server address target (either as a DNS name

   representing one or more IP addresses or as a literal IP address)

   together with the path of that file system within the associated

   single-server namespace.
I don't understand 'associated single-server namespace'.  Does this mean th=
e aggregated logical file system or something else?  Having read further I =
suspect that this at least needs a forward reference to Section 8.

Doesn't the first paragraph of Section 7 introduce the term?




s7.2 and s7.3:  These sections are very repetitive.  They essentially conve=
y the fact that if a file system is absent only GETATTR on the absent syste=
m and READDIR on a  referring system will produce useful answers and only a=
 couple of attributes are valid.

s7.6:


   A potential problem exists if a client were to allow an open owner to

   have state on multiple filesystems on server, in that it is unclear

   how the sequence numbers associated with open owners are to be dealt

   with, in the event of transparent state migration.  A client can

   avoid such a situation, if it ensures that any use of an open owner

   is confined to a single filesystem.
This paragraph is not very helpful because the concepts of 'open owner', as=
sociated state and sequence numbers have not been introduced up to this poi=
nt apart from as cryptic references in type definitions.  At worst a forwar=
d reference is needed.  It might be better to have a brief introduction to =
the state mechanism under the NFSv4 basic concepts section (maybe around s1=
.5.4).

Without this introduction I have no idea under what circumstances the 'open=
 owner' might have state on multiple file systems - and hence what I would =
have to do to avoid going down this rat hole.

As a whole, this document assumes you have already read this document befor=
e you read it.

Changing that is beyond the scope of work I want to undertake.




s7.7, last para:  Would be worthwhile to either substitute 'network order' =
for 'big endian' or add it as an alternative. (It turns out that s9.14 uses=
 network order for just this requirement - consistency would be good!)

The entirety 7.7 from draft 25 is now gone.



s7.7.1:


   When a single file system may be accessed at multiple locations,

   either because of an indication of file system identity as reported

   by the fs_locations attribute, the client will, depending on specific

   circumstances as discussed below, either:
The first 'either' has no corresponding 'or'.
The second 'either' needs an 'or' at the end of the first bullet.

s7.7.1, 2nd bullet: s/Accesses/Access/

s7.7.2, para 3 (and  para 2):


   When there is co-operation in filehandle assignment, the two file

   systems are reported as being in the same handle classes.
It appears that the term 'handle class' is not defined until s7.9.1 (like f=
ileid class in the s7.7.3 and various other attribute classes).  A forward =
reference to this section is essential  (or maybe better a reordering of th=
e sections).  It would be worth a note somewhere in this area that a client=
 needs to ensure that it knows the fh_expire_type for any filesystem instan=
ce it is accessing  in case it get forcibly transitioned, since it can't fi=
nd out post-facto from an absent filesystem.

s7.7.2, paras 2 and 3:


   When there is no such cooperation in filehandle assignment, the two

   file systems are reported as being in different handle classes.  In

   this case, all filehandles are assumed to expire as part of the file

   system transition.  Note that this behavior does not depend on

   fh_expire_type attribute and depends on the specification of the

   FH4_VOL_MIGRATION bit.



   When there is co-operation in filehandle assignment, the two file

   systems are reported as being in the same handle classes.  In this

   case, persistent filehandles remain valid after the file system

   transition, while volatile filehandles (excluding those that are only

   volatile due to the FH4_VOL_MIGRATION bit) are subject to expiration

   on the target server.
I do not understand the final parts of these paras where FH4_VOL_MIGRATION =
is mentioned:
- In para 2, FH4_VOL_MIGRATION is a bit in fh_expire_type, so I fail to und=
erstand how the behavior can both be independent of fh_expire_type and depe=
ndent on a bit within it at the same time.
- In para 3, the wording appears to imply that filehandles with FH4_VOL_MIG=
RATION set will not expire. My  understanding of the definition of this bit=
 was that such filehandles would explicitly expire on migration.  According=
ly I would have expected that such filehandles would have been guaranteed t=
o expire on transition  - but maybe this is some difficulty with the meanin=
gs of transition and migration?

s7.7.3, last para:


   Note that when consistent fileids do not exist across a transition

   (either because there is no continuity of fileids or because fileid

   is not a supported attribute on one of instances involved), and there

   are no reliable filehandles across a transition event (either because

   there is no filehandle continuity or because the filehandles are

   volatile),
I don't understand how there can be no filehandle continuity other than bec=
ause the filehandle is volatile.  If a filehandle is not volatile, then it =
is persistent and s4.2.2 appears to indicate that any persistent filehandle=
 would be valid across a transition.

s7.7.5 and s7.7.6, last paras:  s7.9.1 states that distinct server instance=
s are always in different change classes. Since there doesn't seem to be an=
yway to check that two instances of a server are actually the same when acc=
essed over different connections, the consistent change class mentioned in =
the last para of s7.7.5 and the continuity mentioned in the last para of s7=
.7.6 can never occur in practice and would probably be better omitted.

s7.7.6, para 7: A reference to s9.6.3.4 where the edge conditions are descr=
ibed would be desirable.

s7,7,8:  s7.9.1 says all server instances have different readdir classes, s=
o once again the instances will never be deemed consistent.

^^GONE^^





s7.9:  Copying the fs_location(s)4 structure definitions here creates a dou=
ble maintenance problem.  Better just to reference ss2.2.6/2.2.7 where they=
 are defined.

Actually, due to the way we structure our document source, this is always i=
n sync.

But I don't like how we have two sections and 1 description here:

2.2.6.  fs_location4

   struct fs_location4 {
           utf8val_REQUIRED4       server<>;
           pathname4               rootpath;
   };

2.2.7.  fs_locations4

   struct fs_locations4 {
           pathname4       fs_root;
           fs_location4    locations<>;
   };

   The fs_location4 and fs_locations4 data types are used for the
   fs_locations recommended attribute which is used for migration and
   replication support.

5661 got rid of these as Structured Data Types.

XXX




s8:  Placing this section much earlier in the document would help understan=
ding, especially of Section 7.

Ouch. Yes, single server namespace before multi-server.



s9:  There is a comment in s15.12.5 (para 2) that exactly how locks behave =
depends on the underlying semantics of the exported  file system.  It would=
 be worth reproducing that statement here to ensure that this section is in=
terpreted in that context.

I don't see how to tie that into the content of s9. In s9, we are talking a=
bout the needs of the
protocol and not the permission checking of s15.12.5.



s9, last para:


To support Win32 share reservations it is necessary to atomically

   OPEN or CREATE files.
Add 'and apply the appropriate locks in the same operation' to the end of t=
his sentence.

ack



s9.1: I think that for the sake of clarity, it would be worth explicitly st=
ating that the client has to hold an open before applying locks to the same=
 file.

You need a FH to apply a LOCK. That means either you got it from a OPEN (in=
 which case it is supposed to be a regular file)
or you got it from a LOOKUP, PUTROOTFH, etc (in which case it may be a regu=
lar file or any other filesystem object).




s9.1:  What happens if you try to acquire a byte range lock on a non-file f=
ilesystem object?


I would expect to see NFS4ERR_BADHANDLE returned.




s9.1.1, para after struct nfs_client_id4 definition: s/which the server has=
 previously recorded the client/which the server has previously recorded fo=
r the client/.  Also copying the structure definition creates a double main=
tenance problem.  A ref to s2.2.12 would be better.

Ack.

There isn't a maintenance issue and since the text is directly explaining t=
he
fields, I want to avoid a reference.

I.e., here is why the XDR presented in the document is not a maintenance is=
sue:

<pre>
      <t>
        Client identification is encapsulated in the following structure:

        <?rfc include=3D'autogen/type_nfs_client_id4.xml'?>
      </t>
</pre>



s9.1.3, first sentence:  Question: Should the 'including' list also have sh=
are reservations or are these included in byte-range locks or opens?

Opens.

In any event, the entire parenthetical clause can go.



s9.1.3.5: Expand acronym I/O - this isn't on the RFC Editors 'well known' l=
ist - maybe strangely.

Can you suggest they add it? Pretty well understood acronym.




s9.1.3.2: NFS4_UINT32_MAX should be in the proposed constants section.

Which would mean we have such a section.



s9.1.3.2, para 2 and s9.1.6, para 1: The two paragraphs have conflicting st=
atements about the initial value of seqid for locks (s9.1.3.2 =3D> 1, s9.1.=
6 =3D> server choice) - not that it really matters much unless clients chec=
k that they always get 1!  Note that s9.1.6 does say anything about missing=
 out 0 when wrapping round.

So S9.1.3.2 is correct, thanks for catching this one!





s9.1.5, para 9 (bottom of page 116): s/ (e.g., another open specify denial =
of READs)/(e.g., another open specifying denial of READs)/


ack


s9.4:  Changing:
OLD:
   The server is not
   required to maintain a list of pending blocked locks as it is used to
   increase fairness and not correct operation.
NEW:
   The server is not
   required to maintain a list of pending blocked locks as it is not used t=
o
   provide correct operation but only to increase fairness.
scans more easily.

Ok



s9.6: If I understand correctly, share reservations with a DENY reservation=
 are essentially locks that cover the whole file and adjust dynamically to =
cover the entire byte range of the file if it changes. Presumably. therefor=
e, the whole discussion of lock recovery applies both to byte range locks a=
nd share reservation implicit locks.  I think it would be worth pointing ou=
t that this is the case at the beginning of s9.6 (assuming this is indeed t=
he case - or alternatively explaining how things differ with share reservat=
ions).

Share reservations are a subset of locks. Seeing an unadorned usage of lock=
s
should alert the reader that it means both share and byte level locks.




s9.8, para 4: In the last sentence s/may not/MUST NOT/.

OK



s9.8, para 5:


The client may accomplish this task by

   issuing an I/O request, either a pending I/O or a zero-length read,

   specifying the stateid associated with the lock in question.
I am not sure how you 'issue a pending I/O'.  Does this mean checking wheth=
er there is already a pending I/O request associated with this stateid?

What I think it means is that if there is a pending I/O in the client's que=
ue,
it should issue that and if not, then it can do a zero-length read.





s10.2, para 6: s/server times its wait/server times out its wait/


ok


s10.2, para 7: I think the lat two sentences are requiremenst:
next to last sentence: s/may/MAY/
last sentence: s/should not/SHOULD NOT/

ok


s10.2.1, para 9 (last para on p146):  I think that this para is referring t=
o the server not the client: s/client/server/

The paragraph details how a client might be able to determine if the
server is limiting the number of available delegations.



s10.2.1, para 12 (2nd bullet): Good to have a ref to the Courtesy Locks sec=
tion (s9.6.3.1)

ok



s10.2.1, para 17:  "s special semantic adjustments" =3D> either "special se=
mantic adjustments" or "a special semantic adjustment"

ok




s10.2.1, para 19:  It might be better to explain about the distinction betw=
een the CLAIM_xxx attribute to be used after server and client restarts tha=
t doesn't come till para 24 currently - the changeover to CLAIM_PREVIOUS in=
 this para isn't obvious without this discussion.


XXX



s10.2.1, last para, sentence 1: s/Is/is/

ok


s10.3, 1st bullet: s/and not change/and not the change attribute/ ... there=
 are a couple of other instances where this might also be helpful.

ok



s10.3, 2nd bullet: s/client OPENS as file/the client OPENS a file/

thanks



s10.3.3:  I need to think a bit more about what mandatory locking implies.

s10.4, para after 2nd set of bullets: should the 'standard stateid' be asso=
ciated with the open-owner rather than the lock-owner as currently stated.

Yes, very good catch!

I had to go back to the RFC 3530 to clear it up...



s10.4.3: Should there be some discussion of wrap round in the 'change' attr=
ibute?

No, there is nothing special about a change value of 0. This is unlike a se=
qid, which
has semantics on a wrap.



s10.5.1, para 2: s/a complete cached copy  of file/a complete cached copy  =
of the file/,
s/In other case/In other cases/

ok



s10.7, para 2:
OLD:

(regardless whether the file is local file or is being access remotely)
NEW:

(regardless of whether the file is local file or is being accessed remotely=
)

ok


s11, item 8, first sentence: s/implement/inplemented/

ok



s11, items 9 and 10: Its probably not that important, but would OPTIONAL <=
=3D> REQURED be allowed - i.e., two 'levels' of change rather then the expl=
icit one currently documented.

Yes, but we don't want a change here.



s12.1.1, bullet 2: s/in many case/in many cases/

s12.1.2, para 1: s/important to understand/important to understanding/

s12.1.2: The quoted sections should be attributed to where they come from (=
including section numbers).

s12.1.2: There seems to be a spurious ACCENT in this para:


         LATIN SMALL LETTER E, COMBINING MACRON, ACCENT, COMBINING ACUTE

         ACCENT (U+0xxx, U+0304, U+0301)
s12.1.2 (Maybe expand IDNA again - its 180 pages since it was last expanded=
).

s12.2.3, para just after Table 5: s/or it in may/or it may/

s12.3: (maybe expand UCS again since it is 130 pages since previous occurre=
nce).

s12.7, 2nd bullet: s/lintext4/linktext4/;  also the term 'link text' hasn't=
 been properly defined.

s12.7.1.5.1: Need to expand NFC and NFD and provide a reference.

s12.7.1.5.2, para 8, last sentence: s/it should generally mapped/it should =
generally be mapped/

s12.7.3, bullet 4: Should 'converting a user to group to an internal id' be=
 'converting a user or group to an internal id'?


All of 12 is rewritten.



s13.1.1.7: s/fit/fitted/

ok


s13.1.2.1 s/file handle/filehandle/

ok



s13.1.2.7: should refer to filesystem object rather than file.

ok




s13.1.4.2: Value of NFS4ERR_DQUOT is 19 here but 69 in table 8

Fied



s13.1.4.3/4/5/7: should refer to filesystem object rather than file.

done




s13.1.4.8: Does this apply to any filesystem object rather than just file o=
r directory?


We could just say filesystem object.

fixed up




s13,1.4.11: Value of NFS4ERR_NXIO is 5 here but 6 in table 8 (and value 5 i=
s already used for NFS4ERR_IO).

ok



s13.1.5.2: Value of NFS4ERR_BAD_STATEID is 10026 here but 10025 in table 8 =
(and value 10026 is already used for NFS4ERR_BAD_SEQID).

ok



s13.1.5.2, bullet 1: should refer to filesystem object rather than file.

xxx




s13.1.7: s/When the strings are not are of length zero./When the strings ar=
e not of length zero./

ok



s13.2-13.4: I didn't check these tables.  Table 11 can be checked automatic=
ally if it is thought worthwhile by inverting tables 9 and 10.

These are autogenerated from the same source.

As can be seen, the section titles were not.




s14.2: Might be worth stating that COMPOUND doesn't represent a 'transactio=
n', as is expressed in para 3.

ok



s14.2, para 4:  The operation descriptions explicitly mention what happens =
to the current filehandle after operations.  Nothing is said about the stab=
ility of the saved filehandle.  Can this be assumed to be preserved in all =
cases whether the operation succeeds or fails?  I guess it would also be us=
eful to explicitly state that there are no guarantees about the contents of=
 the current filehandle after an operation unless explicitly stated (i.e., =
after most errors you ought to reload the current filehandle).

Yes, if you do not modify these filehandles, then the last one entered is v=
alid. I.e., think of it as a register.



s14.3, para 1: s/UNSTABLE/UNSTABLE4/

ok




s15.2.5, para 2: I am not sure how you *could* mix operations - I was under=
 the impression that the COMPOUND is submitted in the context of a particul=
ar client ID and the current/saved filehandles are tied to the client ID/co=
nnection. The client ID can't be changed in a single compound statement so =
this seems a spurious statement.  Presumably if stateid's etc are used on t=
he wrong client ID the server will object. See also s15.18.6.


It is possible to migrate a filesystem and state from one server to another=
, in which case the client could have a client ID that
was migrated.

The intent here is to not mingle such state in a COMPOUND.



s15.3.4: Presumably the access permissions generally apply to named attribu=
tes.  Currently it only talks about files and directories.


   ACCESS determines the access rights that a user, as identified by the
   credentials in the RPC request, has with respect to the file system
   object specified by the current filehandle.

So a named attribute is a file system object.



s15.3.5, para 2, sentence 3: s/which will result/which might result/?

ok



s15.3.5, para 4: I found the following confusing:


   The client should use the effective credentials of the user to build

   the authentication information in the ACCESS request used to

   determine access rights.
I am not sure where there is any authentication info (explicitly) "in the A=
CCESS request" - the parameter is just the requested access mask.  Where is=
 the auth info?

The entire COMPOUND is inside a RPC layer request. NFS operations use the c=
redentials
from that layer to determine ACCESS.




s15.9.4:
OLD:


The server returns an attribute bitmap that

   indicates the attribute values for which it was able to return,

NEW:


The server returns an attribute bitmap that

   indicates the attributes for which it was able to return values,


ack


s15.9.5, last sentence: s/returned if while a delegation/returned if [or wh=
ile] a delegation/

ok


s15.11.4:  This section refers explicitly to files.  Is it ever possible to=
 make hard links to:
- directories?
- named attributes?
- device and other special types of 'file'?
It would be good to be explicit.

Going to pass on this one.




s15.12.4, para 2:


 To lock the file from a specific offset

   through the end-of-file (no matter how long the file actually is) use

   a length field with all bits set to 1 (one).
Is the end offset fixed at the value given by the length of the file at the=
 time of applying the lock, or does this byte range vary as the length of t=
he file changes?

It should vary as the length varies.


What happens if the length of the file gets to be less than the start offse=
t, or indeed is currently less than the length of the file?

Someone else can comment, my guess is that POSIX file locking semantics wou=
ld apply.


Actually that is a more general question: Is any special treatment needed f=
or locks that are outside the current length of the file?  Does the server =
make any checks on whether a lock is within the current length of the file =
when applied - or automatically delete locks off the end of a file.. probab=
ly not but would be good to be explicit.

s15.14.5, para 1:

In all of

   these cases, allowed by POSIX locking [fcntl<cid:part4.00080701.00010200=
@dial.pipex.com>] semantics, a client

   receiving this error, should if it desires support for such

   operations, simulate the operation using LOCKU on ranges

   corresponding to locks it actually holds, possibly followed by LOCK

   requests for the sub-ranges not being unlocked.
Shouldn't the client apply the sub-range locks before unlocking?  Otherwise=
 there is a potential race condition and some other client could get in a l=
ock between the unlock and the relock. [After a bit of background reading I=
 understand that this rather silly arrangement is 'the way it is done'

ack


s15.16.4/5:  What happens when you apply LOOKUPP to the 'hidden' named attr=
ibutes directory?  Do you get NFS4ERR_NOENT or the filehandle of the object=
 that owns the named attributes (inverting OPENATTR)?  s15.16.4 only talks =
about the root of the server's file tree.

s15.18.6: Do SHARES work on named attributes?  Just checking...

Named attributes are not always implemented.

They would be treated as a normal file as far as I can see.





s15.20.5, para3, sentence 1:  "Servers must not require..." I think this is=
 a 'MUST NOT'.

ok




s15.23.5: Acronm SNEGO needs an expansion and a reference (RFC 2478?)

RFC 4178



s15.25.4, para 4: If the OPEN didn't use locks or share reservations and th=
ere is no delegation, is the stateid in the READ request the 'basic' OPEN s=
tateid returned with all OPENs? It doesn't explicitly say this.  (also rele=
vant to WRITE operation - s15.38.4, para 3).

Yes, this is to your earlier question on s10.4




s15.25.5, para 1:
OLD:


 It

   is possible that the server reduce the transfer size and so return a

   short read result.  Server resource exhaustion may also occur in a

   short read.
NEW:


 It

   is possible that the server reduces the transfer size and so returns a

   short read result.  Server resource exhaustion may also result in a

   short read.


ok



s15.28.4: The specification says nothing about the semantics of sub-directo=
ry removal.  NFSv3 says that 'some servers won't allow removal of non-empty=
 directories'.  What is the story for NFSv4?  Is there any standardised str=
ategy for dealing with 'orphaned' resources in sub-directories if the serve=
r does allow a non-empty sub-directory to be deleted?


My guess is that server implementations fall back on their NFSv3 behavior.




s15.29.4, para 5:  It would be clearer to say that the operation will fail =
if the saved and current file handles refer to named attribute directories =
attached to different filesystem objects.

I'd like to keep the pain in place for anyone who reads that sentence.

XXX


s15.30.5, para 1 , last sentence: s/such that is could/such that it could/

ok



s15.33.5, para 2:


The filehandle is either provided by the client (PUTFH,

   PUTPUBFH, PUTROOTFH) or generated as a result of a name to filehandle

   translation (LOOKUP and OPEN).
Aren't the PUTxxx filehandles supplied by the server?

The filehandles are provided by the server, but the operations are provided=
 by the client.




s15.38.4:  Does all the discussion of writing to stable storage apply when =
writing to a named attribute?

yes.



s15.38.5, para next to next to last:


   Some implementations may return NFS4ERR_NOSPC instead of

   NFS4ERR_DQUOT when a user's quota is exceeded.  In the case that the

   current filehandle is a directory, the server will return

   NFS4ERR_ISDIR.  If the current filehandle is not a regular file or a

   directory, the server will return NFS4ERR_INVAL.
 I am not sure what circumstances the last sentence is referring to.  One i=
nterpretation would be that WRITE is not allowed at all for special files. =
 I guess this is not what is intended - please clarify.

named attribute?








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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><title>Gen-art additional review of draft-ie=
tf-nfsv4-rfc3530bis-25</title><style><!--
/* Font Definitions */
@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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.grey
	{mso-style-name:grey;}
span.EmailStyle20
	{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.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have so=
me comments on the XXX items.<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F49=
7D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&gt; </span>so.=
.. should the client be able to find out which version of Unicode the serve=
r is working to?<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>The problem with this is that the way to do this =
is a new attribute and that the minor versioning rules as now written precl=
ude adding such a new attribute in v4.0. , giving that v4.1 exists and v4.2=
 almost exists.&nbsp; Those rules could be modified but it would be very ha=
rd to reach consensus on such a change, so I&#8217;d prefer we not open up =
that can of worms, unless it were really necessary, and not just a nice-to-=
have. &nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fa=
mily:"Calibri","sans-serif";color:#1F497D'>Also, this needs to be looked at=
 in the context of the new (really old) I18N chapter in -27.&nbsp; &nbsp;Th=
e goal of that is to describe what actual NFSv4.0 servers and clients actua=
lly do,&nbsp; making adding a new attribute that none of them has asked for=
 pretty much out of bounds.<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Maybe we can defe=
r this discussion until we consider the new I18N chapter in a later pass of=
 the process.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>&gt; </span>s6.3.1.2: Is there =
any interaction between delegation and client considerations for ACLs? Do <=
o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-family:"Calibri","sa=
ns-serif"'>&gt;</span> clients holding delegations have to do any access ch=
ecks in the client that would normally be <o:p></o:p></p><p class=3DMsoNorm=
al><span style=3D'font-family:"Calibri","sans-serif"'>&gt; </span>done in t=
he server if there was no delegation?&nbsp; I'm not sure<span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:=
"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>The client doesn&#8217;t have to do any access checks.&=
nbsp; If it doesn&#8217;t want to do ACL Interpretation it can do <o:p></o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>an OPEN(CLAIM_DELEGATE_CUR) and le=
t the server do it.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>&gt; </span>- Is there =
any interaction between byte range locks and share reservations?&nbsp; e.g.=
, does a client <o:p></o:p></p><p class=3DMsoNormal>&gt; holding (say) a by=
te range write lock but with no DENY state prevent another client taking <o=
:p></o:p></p><p class=3DMsoNormal>&gt; out a DENY_WRITE&nbsp; share reserva=
tion on the same file?<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p>=
</p><p class=3DMsoNormal><span style=3D'font-family:"Calibri","sans-serif";=
color:#1F497D'>I don&#8217;t think it does.&nbsp; I think the intention is =
that server implementations can grant an open just<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Calibri","sans-serif";color:#=
1F497D'>knowing about existing share reservations and delegations.<o:p></o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-family:"Calibri","san=
s-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormalCxS=
pMiddle style=3D'margin-bottom:12.0pt;mso-add-space:auto'><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&gt; </spa=
n>This needs some tidying up.&nbsp; One could try using 'data object' as an=
 unambiguous term for the <o:p></o:p></p><p class=3DMsoNormal style=3D'marg=
in-bottom:12.0pt'><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'>&gt; </span>union of the actual file (NF4REG) clas=
s and the named attribute class.<o:p></o:p></p><p class=3DMsoNormal style=
=3D'margin-bottom:12.0pt'><span style=3D'font-family:"Calibri","sans-serif"=
;color:#1F497D'>I agree this needs tidying up.</span><o:p></o:p></p><p clas=
s=3DMsoNormal><span style=3D'font-family:"Calibri","sans-serif";color:#1F49=
7D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:=
p></span></p><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;=
padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size=
:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif"'> Thomas Haynes [mailto:l=
oghyr@gmail.com] <br><b>Sent:</b> Friday, August 16, 2013 5:56 PM<br><b>To:=
</b> Elwyn Davies<br><b>Cc:</b> General Area Review Team; draft-ietf-nfsv4-=
rfc3530bis.all@tools.ietf.org; nfsv4 list (nfsv4@ietf.org)<br><b>Subject:</=
b> Re: Gen-art additional review of draft-ietf-nfsv4-rfc3530bis-25<o:p></o:=
p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>Hi Elwyn, <o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;=
</o:p></p></div><div><p class=3DMsoNormal>Thank you for the detailed review=
. It has taken so long because even for the<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal>points which I disagreed with, I spent considerable time pro=
ving to myself<o:p></o:p></p></div><div><p class=3DMsoNormal>first your obj=
ection and second why I wasn't going to take the suggested change.<o:p></o:=
p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p cl=
ass=3DMsoNormal>Also, the WG needed to meet to agree with what to do with t=
he i18n comments.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;=
</o:p></p></div><div><p class=3DMsoNormal>I've left XXX or xxx where other =
people in the WG might want to reply.<o:p></o:p></p></div><div><p class=3DM=
soNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I'll be sendi=
ng out a new version of the drafts by Aug 18th.<o:p></o:p></p></div><div><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Tom=
<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><d=
iv><p class=3DMsoNormal>On May 8, 2013, at 3:35 PM, Elwyn Davies &lt;<a hre=
f=3D"mailto:elwynd@dial.pipex.com">elwynd@dial.pipex.com</a>&gt; wrote:<o:p=
></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=
=3DMsoNormal><br>I am another Gen-ART reviewer for this draft. For backgrou=
nd on <br>Gen-ART, please see the FAQ at <br><br><a href=3D"http://wiki.too=
ls.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wiki.tools.ietf.org/ar=
ea/gen/trac/wiki/GenArtfaq&gt;</a>. <br><br>Please resolve these comments a=
long with any other Last Call comments <br>you may receive. <br><br>Documen=
t: draft-ietf-nfsv4-rfc3530bis-25<br>Reviewer: Elwyn Davies<br>Review Date:=
 8 May 2013<br>IETF LC End Date: -<br>IESG Telechat date: 30 May 2013 <br><=
br>Summary: <br>This is a mammoth document.&nbsp; The comments run to 650 l=
ines.&nbsp; Clearly there ae issues in modifying a -bis document given that=
 it has to be pretty much compatible with its progenitor&nbsp; - but that i=
s now going on 14 years old. I believe that there are a significant number =
of minor issues to address and parts of the document (despite the overall s=
ize) need to provide a bit more explanation of what is going on.&nbsp; In p=
articular I think that a little bit more rationale over the way in which an=
 NFS server attempts to provide something like a common interface to the tw=
o big player filesystem types (*ix and Windows) <o:p></o:p></p></div><div><=
p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Ou=
tside of the scope of the document.<o:p></o:p></p></div><div><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p><=
/p><div><p class=3DMsoNormal>[Aside: I am disappointed that it doesn't try =
to handle versioning file systems like the venerable VAX filing system! ;-)=
 ]&nbsp; There are some areas where the addition of named attributes hasn't=
 really been properly dealt with AFAICS. One major area that I felt ought t=
o have been better addressed in the -bis was internationalisation.<o:p></o:=
p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p cl=
ass=3DMsoNormal>As agreed, this is being rewritten.<o:p></o:p></p></div><di=
v><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal=
>(BTW - this is why I've held off on replying.)<o:p></o:p></p></div><div><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br>=
<o:p></o:p></p><div><p class=3DMsoNormal>&nbsp; As mentioned below, I don't=
 understand why additional atrributes couldn't be added to help clients und=
erstand what the server is doing with internationalisation - the client has=
 to do some complex acrobatics which seem close to guesswork to work out wh=
at is going on in the server. <o:p></o:p></p></div><div><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div><div><p class=3DMsoNormal>Which is actually a design mantra when it =
comes to NFS - we talk about dumb servers and smart clients. We push the bu=
rden<o:p></o:p></p></div><div><p class=3DMsoNormal>to the client to figure =
out what to do.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</=
o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><=
o:p></o:p></p><div><p class=3DMsoNormal>&nbsp; As ever, I am not an expert =
in NFSv4 (although I used v2 extensively almost 30 years ago... arrrgghhh!)=
 so there may well be comments where I don't understand the problem.<br>&nb=
sp;&nbsp; &nbsp;&nbsp; <br>Major issues:<br><br>Overall section comments:<b=
r>s6: AccessControl Attributes<br>Combining two different access control pa=
radigms (UNIX-clone mode control bitmasks and access control lists) is an u=
phill struggle and provides a deal of complexity in situations where both, =
either one or neither may be specified.&nbsp; The detailed text deals reaso=
nably with the various cases.&nbsp; There are, in my view, a couple of sign=
ificant problems:<br>- The first is essentially editorial:&nbsp; I would sa=
y that rather more than basic understanding of UNIX-like file systems is ne=
eded.&nbsp; An explanation or at least a suitable reference to explain the =
use of the mode bits in s6.2.2, especially the first three (SUID, SGID, SVT=
X) would help, and a clearer linkage to the explanations of owner, group an=
d other sets of users that are distributed in parts of the text.<o:p></o:p>=
</p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p clas=
s=3DMsoNormal>It is more complex than that unfortunately - we had another d=
ocument which discussed such issues and it atrophied off.<o:p></o:p></p></d=
iv><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMso=
Normal>I'll look at resurrecting it, we actually have confusion in the comm=
unity as different vendors like to quote different revisions.<o:p></o:p></p=
></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p c=
lass=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal style=3D'=
margin-bottom:12.0pt'>- The second is more fundamental:&nbsp; The intended =
functionality of inheritance is not explicitly documented.&nbsp; To come to=
 any sort of understanding of how inheritance is supposed to work you have =
to read through to the next to the last section (s6.4.3).&nbsp; I have now =
read through the section two or three times and I have a model in my mind, =
but there is no text that would allow me to verify my understanding.&nbsp; =
I *think* i have understood that (1) inheritance only applies when you init=
ially create an object rather than being fed through to all 'inferior' obje=
cts in the tree if a superior object has a heritable ACE added; (2) inherit=
ance only applies if you don't explicitly give any ACEs when the object is =
created, and (3) if you give a mode but no ACL then some complex combinatio=
n of inherited ACL and mode is applied.&nbsp; An upfront explanation of wha=
t is trying to be achieved would have helped a lot.&nbsp; However, none of =
this explains what happens with either hard or symbolic links.&nbsp; It is =
unclear to me whether inheritance of ACLs is applied when creating a hard o=
r symbolic link to an existing object.<br><br>s7, Multi-Server Namespace:<b=
r>This section is very verbose and contains a number of areas that bring in=
 topics that&nbsp; are actually forward references without indicating where=
 the information can be found, particularly in relation to various 'change =
classes'.&nbsp; Some reordering might help.&nbsp; The whole concept of chan=
ge classes seems a little odd, because when they are finally defined (s7.9.=
1), it appears that servers are rarely in the same class during any of the =
interesting transitions (s7.9.1 says that in most cases they have to be tak=
en as in different classes).&nbsp; Overall, this section contains an awful =
lot of discursive specification relating to servers that may not have any c=
oordination which makes it very difficult both from the specification and t=
he implementation angles to check that everything is working.<o:p></o:p></p=
></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>We brough=
t this section forward from 5661 in order to provide some help in dealing w=
ith the migration issues implementors are having with 3550.<o:p></o:p></p><=
/div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DM=
soNormal>And I really want to thank your review here, I don't think we can =
make this work at all. I've yanked it.<o:p></o:p></p></div><div><p class=3D=
MsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3D=
MsoNormal>s8, NFS Server namespace:&nbsp; This is a important section for o=
verall understanding and I think it would help to have it much earlier, cer=
tainly before s7.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;=
</o:p></p></div><div><p class=3DMsoNormal>We want to maintain as much secti=
on compatibility with 3550 as possible.<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p><=
/o:p></p><div><p class=3DMsoNormal><br>s9, File Locking and Share Reservati=
ons:<br>Generally very well written, but the treatment of share reservation=
s is very skimpy,<br>It would also be good to be more 'honest' about the in=
teraction with the semantics of the underlying file system as regards locks=
 as described in s15.12.<br><br>s10, Clientside Caching:<br>Clearly very co=
mplex to implement but seems to be well-described.&nbsp; A bit of earlier e=
xplanation of the use of CLAIM_PREVIOUS vs CLAIM_DELEGATION_PREV in client/=
server reboots would help.<br><br>s11, Minor Versions:<br>No particular iss=
ues.<br><br>s12, Internationalisation:<br>A minefield.&nbsp; There seems to=
 be an awful lot of guess work for clients trying to decide how the sever b=
ehaves.&nbsp; On reflection, I am surprised that several of the things that=
 clients are supposed to deduce (e.g., what normalisation the server does) =
were not supplied as attributes of the server.&nbsp; Is there some good rea=
son for this?&nbsp; I was also surprised that there didn't seem to be a req=
uirement that servers working on a particular filesystem all did the same i=
nternationalisation things.&nbsp; It appears to me that if a filesystem get=
s migrated the client doesn't have any sort of guarantee that the internati=
onalisation behaviour won't change under its feet - and it has no easy way =
to check if this is or is not the case because of the lack of attributes.&n=
bsp; I have no idea to what extent the internationalisation is implemented =
in current servers.<br><br>s13, Error Codes:<br>Generally OK but with a few=
 code value inconsistencies.&nbsp; I haven't checked the cross-consistency =
of Table 9 and Table 11 or whether the sets of error codes per operation ar=
e really right - they are just too voluminous.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>They are machine generated=
 from a common source.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p cl=
ass=3DMsoNormal><br>s14, NFSv4 Requests:<br>No problems.<br><br>s15/16, Ope=
rations:<br>Generally in good shape apart from some issues with the meaning=
 of 'regular files'.<br><br>s17: Security:<br>I have some doubts about the =
Kerberos algorithms suggested.&nbsp; Maybe should be moving on to better al=
gorithms even if this is a bis.<o:p></o:p></p></div><div><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div><div><p class=3DMsoNormal>As discussed on the mailing list, we agre=
ed and fixed it.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p></div><div><p class=3DMsoNormal>Again, here is where I would prefe=
r we push this to another document which tracks which Kerberos algorithms s=
hould be used.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o=
:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMs=
oNormal><br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Minor issues: <b=
r>S1.1, bullet 7: Are there issues with backwards compatibility after remov=
al of LIPKEY and SPKM-3 completely?<o:p></o:p></p></div><div><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>No, not a singl=
e vendor implemented these.<o:p></o:p></p></div><div><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div>=
<p class=3DMsoNormal><br>s1.5.1: Should NFSv4 be using RPCSEC_GSS v2 (RFC 5=
403) rather than v1 (RFC 2203)?<o:p></o:p></p></div><div><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div><div><p class=3DMsoNormal>It should be &quot;and&quot; and not &quo=
t;rather&quot;. v1 is not widely adopted, but nothing precludes its use.<o:=
p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div=
><p class=3DMsoNormal>I've updated the instances of references to include b=
oth.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></d=
iv><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><blockquote style=
=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=3DMsoNormal><br>s.1=
.5.3.2, para 4, and s5.3: It would be useful to say upfront in s1.5.3.2 whe=
ther the attribute names are fully internationalized or whether this is sti=
ll an ASCII name.<o:p></o:p></p></div></blockquote><div><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div><div><p class=3DMsoNormal>I don't think anything precludes an&nbsp;i=
nternationalized name here since these are in the directory space.<o:p></o:=
p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMso=
Normal><br>s2.1:&nbsp; This section contains a number of symbolic constants=
 (chiefly for opaque element sizes) which have not been defined as yet.&nbs=
p; It would be highly desirable if these were also defined before this sect=
ion.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></d=
iv><div><p class=3DMsoNormal>These are in the companion document.<o:p></o:p=
></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p cla=
ss=3DMsoNormal>We broke the XDR out starting with RFC 5661 - we've made the=
 same effort<o:p></o:p></p></div><div><p class=3DMsoNormal>here as readers =
prefer having the other document to reference.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><=
o:p></o:p></p><div><p class=3DMsoNormal><br>s2.1, utf8val_RECOMMENDED4:&nbs=
p; <br><br><o:p></o:p></p><pre>&nbsp;String SHOULD be sent UTF-8 <o:p></o:p=
></pre><p class=3DMsoNormal>What else could it be sent as in this type?<o:p=
></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>W=
e will revisit with the i18n rewhack.<o:p></o:p></p></div><div><p class=3DM=
soNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p=
></p><div><p class=3DMsoNormal><br>s2.2/s6.2.1:&nbsp; The type nfsace4 is u=
sed in the protocol: Accordingly it ought to be defined in s2.2 rather than=
 s6.2.1.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div><div><p class=3DMsoNormal>Part of the XDR document.<o:p></o:p></p></=
div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><=
br>s2.2.3/s5.8.2.34/s5.8.2.40: It would probably be nicer if the union case=
 SET_TO_SERVER_TIME4 were put into the union explicitly.&nbsp; A note about=
 being able to set the access and modify times to either client or server t=
ime would be appropriate in the two items in s5.8.2.&nbsp; Are there any co=
nstraints on the values that can be given when setting from the client.. li=
ke not moving the time backwards (or is this explained later?).<o:p></o:p><=
/p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal>We can't change the enum or union at this point.<o:p></o:p></p=
></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal>Given that there can be time skew, the server cannot tell if t=
he client is moving things backward or not.<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>In this=
 case, the server would assume that the client was correct and allow the ch=
ange.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></=
div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNorm=
al><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s3.1, para 1:<br><b=
r><o:p></o:p></p><pre> Using the registered port for NFS services<o:p></o:p=
></pre><pre>&nbsp;&nbsp; means the NFS client will not need to use the RPC =
binding protocols<o:p></o:p></pre><pre>&nbsp;&nbsp; as described in [<a hre=
f=3D"http://tools.ietf.org/html/rfc1833" title=3D"&quot;Binding Protocols f=
or ONC RPC Version 2&quot;">RFC1833</a>]; this will allow NFS to transit fi=
rewalls.<o:p></o:p></pre><p class=3DMsoNormal>I think some explanation of w=
hy this will definitively allow NFS to transit firewalls is needed. <o:p></=
o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>In N=
FSv3, there were several sideband protocols which did not sit on well defin=
ed ports. Each<o:p></o:p></p></div><div><p class=3DMsoNormal>server vendor =
either picked a port or allowed for them to be configurable. As such, it is=
 somewhat<o:p></o:p></p></div><div><p class=3DMsoNormal>unwieldily to confi=
gure firewalls.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</=
o:p></p></div><div><p class=3DMsoNormal>With just using port 2049, it is ea=
sy to determine which single port needs to be open.<o:p></o:p></p></div><di=
v><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br>=
<br><o:p></o:p></p><div><p class=3DMsoNormal><br>s3.1.1: Presumably the req=
uirement to eschew silent dropping of 'requests' does not apply if security=
 is being negotiated.&nbsp; I take it 'requests' should be interpreted as&n=
bsp; 'NFSv4 requests' and procedures as defined in s14/15 and this requirem=
ent should apply only once the secure connection is established.&nbsp; The =
word 'established' might help.<o:p></o:p></p></div><div><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div><div><p class=3DMsoNormal>Yes, NFSv4 requests and established.<o:p><=
/o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p=
 class=3DMsoNormal>I can add both.<o:p></o:p></p></div><div><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoN=
ormal><br>s3.2: (reprise) Should we be using RPCSEC_GSSv2 (RFC 5203) rather=
 than v1?<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div><div><p class=3DMsoNormal>Same reply as above.<o:p></o:p></p></div>=
<p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal>&nbsp=
;<br>s3.2.1.1: The Kerberos specifications appear to use rather ancient alg=
orithms.&nbsp; In particular DES, MD5.. should there not be more&nbsp; mode=
rn algorithms?&nbsp; DES and MD5 get a pretty bad press these days.&nbsp; R=
FC 2623 is also a bit of an antique so I can't say its a modern assessment.=
<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><=
div><p class=3DMsoNormal>Already taken care of.<o:p></o:p></p></div><p clas=
s=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s3.3.1,s=
ecurity poiicy boundaries etc:<br><br><o:p></o:p></p><pre> In general, the =
client will not have to use the SECINFO<o:p></o:p></pre><pre>&nbsp;&nbsp; o=
peration except during initial communication with the server or when<o:p></=
o:p></pre><pre>&nbsp;&nbsp; the client crosses policy boundaries at the ser=
ver.&nbsp; It is possible<o:p></o:p></pre><pre>&nbsp;&nbsp; that the server=
's policies change during the client's interaction<o:p></o:p></pre><pre>&nb=
sp;&nbsp; therefore forcing the client to negotiate a new security triple.<=
o:p></o:p></pre><p class=3DMsoNormal>&nbsp;The&nbsp; concept of 'security p=
olicy boundary' has not been previously discussed in the doc.&nbsp; How wou=
ld the client know it had crossed a security boundary or that the server ha=
d changed the policy under its feet? I suppose maybe the next section tells=
 me... but... How does this interact with the no silent drop, mostly no ret=
ries requirement in s3.1.1? or have i to read s15.33. &nbsp;&nbsp; <br><br>=
I suspect that some discussion of the interaction of mount points and secur=
ity policy boundaries may be needed at an earlier stage.&nbsp; I suspect th=
at mount points might well be security policy boundaries and crossing mount=
 points might interact.&nbsp; There is nothing in the description of mounte=
d_on_fileid (s5.8.2.19).<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div=
><div><p class=3DMsoNormal>I think this was an effort to avoid talking abou=
t exports.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNor=
mal><br>s5.6, item lease_time:&nbsp; I can't find a definition of nfs_lease=
4 type used for this.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p></div><div><p class=3DMsoNormal>The accompanying XDR document=
 has it.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNorma=
l><br>s5.6, item rdattr_error: Just giving 'enum' as the type isn't too spe=
cific!<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
/div><div><p class=3DMsoNormal>Agreed, I'll put&nbsp;nfsstat4<o:p></o:p></p=
></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoN=
ormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s5.8.2.25:<br><b=
r><o:p></o:p></p><pre>It is understood that this space may be<o:p></o:p></p=
re><pre>&nbsp;&nbsp; consumed by allocations to other files or directories =
though there is<o:p></o:p></pre><pre>&nbsp;&nbsp; a rule as to which other =
files or directories.<o:p></o:p></pre><p class=3DMsoNormal>Where do I find =
the rule?<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div><div><p class=3DMsoNormal>Yes, confusing. The next section illustra=
tes that this is defined by the server.<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I'll make=
 it more explicit here.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p c=
lass=3DMsoNormal><br>s5.10, para 1:&nbsp; <br><br><o:p></o:p></p><pre>altho=
ugh there are variations that occur additional characters with a<o:p></o:p>=
</pre><pre>&nbsp;&nbsp; name including &quot;SMALL&quot; or &quot;CAPITAL&q=
uot; are added in a subsequent version<o:p></o:p></pre><pre>&nbsp;&nbsp; of=
 Unicode.<o:p></o:p></pre><p class=3DMsoNormal>so... should the client be a=
ble to find out which version of Unicode the server is working to?<o:p></o:=
p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p cl=
ass=3DMsoNormal>XXX<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p><=
/o:p></p><div><p class=3DMsoNormal><br>s6.3.1.2: Is there any interaction b=
etween delegation and client considerations for ACLs? Do clients holding de=
legations have to do any access checks in the client that would normally be=
 done in the server if there was no delegation?&nbsp; I'm not sure.<o:p></o=
:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p c=
lass=3DMsoNormal>XXX<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p>=
</o:p></p><div><p class=3DMsoNormal><br>s7.5:<br><br><o:p></o:p></p><pre>&n=
bsp;&nbsp; If a single location entry designates multiple server IP address=
es,<o:p></o:p></pre><pre>&nbsp;&nbsp; the client cannot assume that these a=
ddresses are multiple paths to<o:p></o:p></pre><pre>&nbsp;&nbsp; the same s=
erver.&nbsp; In most cases, they will be, but the client MUST<o:p></o:p></p=
re><pre>&nbsp;&nbsp; verify that before acting on that assumption. <o:p></o=
:p></pre><p class=3DMsoNormal>How is the verification achieved?&nbsp; I don=
't see any attributes within NFSv4 that would help.<o:p></o:p></p></div><di=
v><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal=
>A swear word needs to be inserted here.<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>It is pos=
sible in NFSv4.1, but not NFSv4.0. I've removed this section.<o:p></o:p></p=
></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoN=
ormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s7.7.6.1, para 3=
: <br><br><o:p></o:p></p><pre>&nbsp;&nbsp;&nbsp;If state has not been trans=
ferred transparently because the client ID<o:p></o:p></pre><pre>&nbsp;&nbsp=
; is rejected when presented to the new server, the client should fetch<o:p=
></o:p></pre><pre>&nbsp;&nbsp; the value of lease_time on the new (i.e., de=
stination) server, and<o:p></o:p></pre><pre>&nbsp;&nbsp; use it for subsequ=
ent locking requests.&nbsp; However, the server must<o:p></o:p></pre><pre>&=
nbsp;&nbsp; respect a grace period of at least as long as the lease_time on=
 the<o:p></o:p></pre><pre>&nbsp;&nbsp; source server, in order to ensure th=
at clients have ample time to<o:p></o:p></pre><pre>&nbsp;&nbsp; reclaim the=
ir lock before potentially conflicting non-reclaimed locks<o:p></o:p></pre>=
<pre>&nbsp;&nbsp; are granted.<o:p></o:p></pre><p class=3DMsoNormal style=
=3D'margin-bottom:12.0pt'>How does the destination server know what the lea=
se_time/grace period on the source server was? It doesn't know what server =
the client was previously connected to in many cases and so can't ask.&nbsp=
; Doesn't this amount to saying all servers for a given file system should =
(MUST) be configured with the same lease time in the non-transparent transp=
arent case?<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p>=
</p></div><div><p class=3DMsoNormal>It doesn't, it makes an assumption that=
 they were the same.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal>s9.9: Th=
is section is a little skimpy.&nbsp; There are several points that probably=
 ought to be clarified:<br>- The section explicitly refers to files:&nbsp; =
Does it actually apply to all filesystem objects?<o:p></o:p></p></div><div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>N=
o, just regular files.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p cl=
ass=3DMsoNormal>- An explicit statement that the 'file_state' is maintained=
 for each file(system object)<o:p></o:p></p></div><div><p class=3DMsoNormal=
><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p>=
</div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal=
>- The pseudo-code applies to the OPEN case; different pseudo-code (presuma=
bly) applies to OPEN_DOWNGRADE.&nbsp; I *think* I could guess it but it wou=
ld be good to be explicit.<o:p></o:p></p></div><div><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I'm happy enough without=
 another example here.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p cl=
ass=3DMsoNormal>- Is there any interaction between byte range locks and sha=
re reservations?&nbsp; e.g., does a client holding (say) a byte range write=
 lock but with no DENY state prevent another client taking out a DENY_WRITE=
&nbsp; share reservation on the same file?<o:p></o:p></p></div><div><p clas=
s=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p></div><div><p class=3DMsoNormal>XXX<o:p></o:p></p></div><p cla=
ss=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal>- Does the =
discussion of placing lock state into stable storage across server reboot a=
lso apply to the share reservation file_state?<br><br>s9.14:&nbsp; The text=
 in this section addresses topics also covered in s7.&nbsp; This does&nbsp;=
 not seem desirable as there may be discrepancies (see next comment).&nbsp;=
 It would seem better to merge the text into s7 and possibly provide a refe=
rence back to s7 from s9.&nbsp; <br><br>s9.14.1:&nbsp; This section envisag=
es migration of state from one server to another where the client already h=
as state on the other server using the same client ID.&nbsp; Merging of the=
 states is suggested.&nbsp; AFAICS this situation is not discussed in s7 wh=
ich seems a little odd.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div><div><p class=3DMsoNormal>We are going to have a new =
document on migration come out based on this text.<o:p></o:p></p></div><div=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>=
I would prefer to keep this as is and allow those authors to drive that dis=
cussion.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNorma=
l style=3D'margin-bottom:12.0pt'><br>s12:&nbsp; It seems the client has to =
play '20 questions' with the server to find out how it treats international=
ized component names.&nbsp; Some of it seems little better than guesswork.&=
nbsp; I was wondering why some of the server choices are not described usin=
g attributes so that the client doesn't have to thrash around in the dark.&=
nbsp; Also there doesn't seem to be any requirement for a filesystem to be =
treated identically after migration. As far as I can see the client can't r=
eally rely on the internationalisation treatment not changing after migrati=
on.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></di=
v><div><p class=3DMsoNormal>Again, i18n is going to be addressed.<o:p></o:p=
></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3D=
MsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal>s18.1:&nbsp; The=
 NFSv4 Named Attribute Definitions registry has already been created in exa=
ctly the form specified here by RFC 5661 (NFSv4.1).&nbsp; This section shou=
ld be removed and words noting that the existing registry is common to all =
minor versions of NFSv4&nbsp; should be substituted.<o:p></o:p></p></div><d=
iv><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I'd prefer to leave =
this as is because:<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p></div><div><div><p class=3DMsoNormal>&nbsp; &nbsp; &nbsp;IANA h=
ad created a registry called the &quot;NFSv4 Named Attribute Definitions Re=
gistry&quot;<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp; &nbsp; &n=
bsp;for &lt;xref target=3D&quot;RFC3530&quot; /&gt; and &lt;xref target=3D&=
quot;RFC5661&quot; /&gt;. This section introduces no new<o:p></o:p></p></di=
v><div><p class=3DMsoNormal>&nbsp; &nbsp; &nbsp;changes, but it does recap =
the intent.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p>=
</p></div></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p cla=
ss=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Nits/editorial comments=
:<br>General: Review the remaining instances of 'file' and 'files' to deter=
mine if they should really be 'filesystem objects'.<br><br>General: Consist=
ency between 'file system' and 'filesystem'.&nbsp; 'filesystem' is used fir=
st in abstract and s1.3 but only File System is defined.&nbsp; I cannot see=
 whether there is any real distinction between the usages... but&nbsp; am o=
pen to argument! OTOH there is definitely inconsistency: Consider 'fsid' an=
d 'fsid4' - the type definition says fsid4 is for a filesystem (s2.2.5) but=
 s5.8.1.9 says this is about a 'file system'<o:p></o:p></p></div><div><p cl=
ass=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>And fi=
nally got to this one: &quot;file system&quot;!<o:p></o:p></p></div><div><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p=
 class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>General: The terms 'r=
egular file' and 'named attribute' are not used uniformly.&nbsp; s5.8.1.2 t=
ypifies the confusion.&nbsp; In the first set of bullets, NF4REG is defined=
 as 'a regular file' and NF4NAMEDATTR is defined as a Named Attribute.&nbsp=
; In the last bullet, &quot;is an[sic] regular file&quot; is defined as imp=
lying either type NF4REG or NF4NAMEDATTR.&nbsp; <br>Thus we have the same t=
erm used for a set and a superset of the same set (maybe when qualified wit=
h 'is a').&nbsp; Consequently, for example in s15.25.4,&nbsp; we have &quot=
;the READ operation reads data from the regular file...&quot;.&nbsp; Presum=
ably this is supposed to cover both NF4REG and NF4NAMEDATTR types but one c=
an't be absolutely sure (to be pedantic it doesn't explicitly say 'is a reg=
ular file' so perhaps it should be read as NF4REG only).&nbsp; OTOH the OPE=
N operation (s15.18.5) has two separate paragraphs for regular files and na=
med attributes.&nbsp; This needs some tidying up.&nbsp; One could try using=
 'data object' as an unambiguous term for the union of the actual file (NF4=
REG) class and the named attribute class.<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p></div><div><p class=3DMsoNormal>XXX<o:p></o:p></p></div><div><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br>=
<o:p></o:p></p><div><p class=3DMsoNormal>Abstract: s/owes heritage to/build=
s on the heritage of/&nbsp; <o:p></o:p></p></div><div><p class=3DMsoNormal>=
<o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p></o:p></p></div=
><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>=
s1.1: Expand IDNA acronym.<o:p></o:p></p></div><div><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p></o:p></p></div><=
p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal style=
=3D'margin-bottom:12.0pt'><br>s1.2, bullet 5:s/mounted_on_filed/mounted_on_=
fileid/<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p>=
</div><div><p class=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal=
><br><br><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12=
.0pt'>s1.3: Expand acronyms ONCRPC and RPCSEC_GSS (and/or ref to RFC 2203 o=
r 5403).<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div><div><p class=3DMsoNormal>Fixed ONC RPC.<o:p></o:p></p></div><div><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>RPC=
SEC_GSS is not defined as an acronym<o:p></o:p></p></div><div><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p>=
</p><div><p class=3DMsoNormal>s1.5: s/the reader that is new/the reader who=
 is new/<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div><p class=3DMsoNormal>ok<o:p></o:p></p></div><div><p class=3DMsoNorma=
l><br><br><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:1=
2.0pt'><br>s1.5.1, para 2: s/provides the client a method/provides the clie=
nt with a method/<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;=
</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><=
p class=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:=
p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>s1.5.3=
:&nbsp; A couple of sentences outlining the presentational scheme for files=
ystem object names (i.e., /a/b/c etc) would be worthwhile even if 'we all k=
now what this means'!&nbsp; This could include defining 'component name' us=
ed later with no introduction.<br><br>s1.5.3.1, et seq: Would it be useful =
to identify 'persistent' and 'volatile' as key words: e.g., 'Persistent' an=
d 'Volatile'. <br><br>s1.5.3.2, para 3: For consistency the 'acl' example s=
hould have a ref (s6.2.1) earlier in the para.&nbsp; So s/((Section 6)/(Sec=
tion 6.2.1)/ and move one sentence earlier.<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p>=
</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=
=3DMsoNormal>s1.5.5: There should be a discussion of share reservations in =
this section.<br><br>s1.6, definition of Lease: There should be a definitio=
n of 'grace period' (as per s9.6.2) as there are lots of references to it e=
arlier than s9.6.2.<br><br>s1.6, definition of Lock:&nbsp; There should be =
a definition of share reservation.<br><br>s2.1 et seq:&nbsp; Whilst the ter=
ms 'hard link' and 'symbolic link' are pretty commonly known,&nbsp; they ar=
e so fundamental that I think putting them in the definitions would be high=
ly desirable.<br>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I'm okay with this as is.<o=
:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal>s2.1, at=
trlist4:&nbsp; In line with comment about opaque max sizes, should this hav=
e a max size? (Might also apply to bitmap4)<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>In the =
XDR<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p=
 class=3DMsoNormal><br>s2.2: It would be useful to have section references =
to the places where the types are used where these are explicitly mentioned=
.<br><br>s2.2.8 (and s2.1):&nbsp; I guess that the bit ordering in bitmap4 =
is implicitly derived from the XDR representation, but it would be useful&n=
bsp; to remind people of what this bit ordering actually is. <br><br>s2.2.9=
, atomic element:&nbsp; With a name like that are there any special handlin=
g requirements for this element/structure?<br><br>s2.2.10: Note&nbsp; to se=
lf: verify external refs in this section.<br>&nbsp;<br>s2.2.11, cb_program:=
 It should be explained that the cb_program is an RPC program number (had t=
o ferret in s15.35.4 to understand this).&nbsp; BTW this would entail an ea=
rlier expansion of RPC acronym.<o:p></o:p></p></div><div><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>1.1 is the earliest (in =
newest draft.)<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o=
:p></p></div><div><p class=3DMsoNormal>But okay with leaving this as is.<o:=
p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div=
><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>=
s2.2.12:&nbsp; It would be good to have a definition of NFS4_OPAQUE_LIMIT b=
efore this section (see earlier comment about s2.1) so that all the magic n=
umber constants are concentrated in one place.<br><br>s2.2.13:&nbsp; Arrgh!=
 Now we have two definitions of NFS_OPAQUE_LIMIT (fortunately they are the =
same until they aren't).<br><br>s2.2.14: ARRRGGGHHH! THREE defs.<o:p></o:p>=
</p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p clas=
s=3DMsoNormal>It is now only defined in the XDR document.<o:p></o:p></p></d=
iv><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNorma=
l><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s2.2.16, 'other':&nb=
sp; And this definition contains the magic number 12 not as a symbolic cons=
tant and with no explanation of why 12 is a good value! <o:p></o:p></p></di=
v><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoN=
ormal>No explanation, but provided a name for the magic number.<o:p></o:p><=
/p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMs=
oNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s3.1, para 2:&=
nbsp; <br><br><o:p></o:p></p><pre>&nbsp;&nbsp;&nbsp;Where an NFSv4 implemen=
tation supports operation over the IP network<o:p></o:p></pre><pre>&nbsp;&n=
bsp; protocol, the supported transports between NFS and IP MUST be among<o:=
p></o:p></pre><pre>&nbsp;&nbsp; the IETF-approved congestion control transp=
ort protocols, which<o:p></o:p></pre><pre>&nbsp;&nbsp; include TCP and SCTP=
. <o:p></o:p></pre><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>I kn=
ow what is meant, but technically, I don't believe the IETF actually has a =
list marked 'congestion control transport protocols'.&nbsp; A better way of=
 phrasing this might be:<br>&nbsp;&nbsp; Where an NFSv4 implementation supp=
orts operation over the IP network<br>&nbsp;&nbsp; protocol, the supported =
transport layer between NFS and IP MUST be an IETF<br>&nbsp;&nbsp; standard=
ised transport protocol that is specified to avoid network <br>&nbsp;&nbsp;=
 congestion; such&nbsp; transports include TCP and SCTP.<o:p></o:p></p></di=
v><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoN=
ormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><d=
iv><p class=3DMsoNormal>[Check whether SCTP is on the IANA well-known acron=
ym list]. <br><br>Also:<br>OLD:<br>to use a different IETF-approved congest=
ion control transport protocol.<br>NEW:<br>to use a different IETF standard=
ised transport protocol with appropriate congestion control.<o:p></o:p></p>=
</div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3D=
MsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></=
p><div><p class=3DMsoNormal><br>s3.1, para 3: Expand WAN acronym. (I think)=
<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><=
div><p class=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><br><b=
r><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><=
br>s3.1, para 4:&nbsp; Where would I find a justification that DCCP or NORM=
 are inadequate?<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p></div><div><p class=3DMsoNormal>It must have been debated on the m=
ailing list.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p></div><div><p class=3DMsoNormal>I know this came up again in the conte=
xt of 3530bis and we determined that they were not adequate.<o:p></o:p></p>=
</div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3D=
MsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:=
p></p><div><p class=3DMsoNormal>s3.1, para 5: s/regardless whether/regardle=
ss of whether/<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o=
:p></p></div><div><p class=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMs=
oNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bo=
ttom:12.0pt'><br>s3.1, para 6: A rather throwaway comment about avoiding ti=
mer sync.&nbsp; Not sure yet how many timers, but it would be good to know =
which ones were critical.&nbsp; After reding the document I am still not su=
re.&nbsp; It might almost be worth adding a section that summarizes the set=
 of timers used.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p></div><div><p class=3DMsoNormal>I think removing the comment altog=
ether is better.<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:=
p></p><div><p class=3DMsoNormal>s3.2.1/s3.2.1.1: Check section title capita=
lization.&nbsp; (Mostly OK - spotted also s6.4.1/s6.4.1.x - possibly)<o:p><=
/o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p clas=
s=3DMsoNormal>ok<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p></div><div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p cla=
ss=3DMsoNormal><br>s4.2.1: Earlier parts of s4 have been generalised to tal=
k about 'filesystem objects'.&nbsp; This section still has filehandles refe=
rring to 'files'.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;=
</o:p></p></div><p class=3DMsoNormal>ok<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><br><br><=
o:p></o:p></p><div><p class=3DMsoNormal><br>s4.2.3, para at top of p33; s4.=
3, para 4: Ditto talking about 'files'.<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>In this c=
ase, the context establishes that the filehandle is to a file.<o:p></o:p></=
p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMso=
Normal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s4.3, para 1:&n=
bsp; <br><br><o:p></o:p></p><pre>&nbsp;&nbsp;&nbsp;If possible, the client =
SHOULD recover from the receipt of an<o:p></o:p></pre><pre>&nbsp;&nbsp; NFS=
4ERR_FHEXPIRED error. <o:p></o:p></pre><p class=3DMsoNormal style=3D'margin=
-bottom:12.0pt'>I think this is a 'should' rather than a 'SHOULD'. Its not =
something that the protocol designer has any control over.<o:p></o:p></p></=
div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMs=
oNormal>ok<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNor=
mal>s5 title:&nbsp; Attributes apply to more than just files. <o:p></o:p></=
p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMso=
Normal>ok<o:p></o:p></p></div><div><p class=3DMsoNormal><br><br><o:p></o:p>=
</p><div><p class=3DMsoNormal><br>s5, para 4: s/new&nbsp; OPENATTR operatio=
n/OPENATTR operation introduced in NFSv4/<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I think j=
ust removing &quot;new&quot; suffices.<o:p></o:p></p></div><div><p class=3D=
MsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:=
p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>s5.1, la=
st sentence: I think the 'must' is a 'MUST' - the server is constrained to =
send the values if asked (but the client has a choice to ask or not).<o:p><=
/o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p=
 class=3DMsoNormal>Agreed.<o:p></o:p></p></div><div><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><=
p class=3DMsoNormal>s5.2: <br><br><o:p></o:p></p><pre>A client MAY ask for =
the<o:p></o:p></pre><pre>&nbsp;&nbsp; set of attributes the server supports=
 and SHOULD NOT request<o:p></o:p></pre><pre>&nbsp;&nbsp; attributes the se=
rver does not support.<o:p></o:p></pre><p class=3DMsoNormal>This should pro=
bably be <br>&nbsp;&nbsp; An operation allows the client to determine the s=
et of attributes <br>&nbsp;&nbsp; that the server supports; a client should=
 not request attributes the <br>&nbsp;&nbsp; server does not support.<br>It=
s not something the protocol can do anything about.<o:p></o:p></p></div><di=
v><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal=
>What I don't like here is what does the server do if the client requests<o=
:p></o:p></p></div><div><p class=3DMsoNormal>an attribute that is neither R=
EQUIRED nor RECOMMENDED?<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I.e., say the last support=
ed attribute is X, and a client queries on X+2.<o:p></o:p></p></div><div><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Sho=
uld the server silently ignore this?<o:p></o:p></p></div><div><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>What if two di=
fferent client implementations use that attribute to mean<o:p></o:p></p></d=
iv><div><p class=3DMsoNormal>different things?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>For =
those reasons, I like the wording as is.<o:p></o:p></p></div><p class=3DMso=
Normal><br><br><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bot=
tom:12.0pt'><br>s5.8.1.4:s/may/MAY/<o:p></o:p></p></div><div><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p></o:p></=
p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMso=
Normal><br><br><o:p></o:p></p><div><p class=3DMsoNormal>s5.8.2.10, para 2: =
Not sure what root path has to do with locations.<o:p></o:p></p></div><div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>T=
his specifies how root path can be communicated.<o:p></o:p></p></div><p cla=
ss=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s5.9, p=
ara 4:<br><br><o:p></o:p></p><pre> Servers that do not provide support for =
all possible values of the<o:p></o:p></pre><pre>&nbsp;&nbsp; owner and owne=
r_group attributes SHOULD return an error<o:p></o:p></pre><pre>&nbsp;&nbsp;=
 (NFS4ERR_BADOWNER) when a string is presented that has no<o:p></o:p></pre>=
<pre>&nbsp;&nbsp; translation, as the value to be set for a SETATTR of the =
owner,<o:p></o:p></pre><pre>&nbsp;&nbsp; owner_group, or acl attributes.<o:=
p></o:p></pre><p class=3DMsoNormal>What might the server do if it doesn't r=
eturn NFS4ERR_BADOWNER? I would have thought this ought to be&nbsp; MUST.<o=
:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><di=
v><p class=3DMsoNormal>They might just accept it as untranslatable and not =
return an error.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p></div><div><p class=3DMsoNormal>As long as they give it back on th=
e GETATTR, this is valid.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p=
 class=3DMsoNormal><br>s5.9, para 5:<br><br><o:p></o:p></p><pre>&nbsp;&nbsp=
; The &quot;dns_domain&quot; portion of the owner string is meant to be a D=
NS<o:p></o:p></pre><pre>&nbsp;&nbsp; domain name.&nbsp; For example, <a hre=
f=3D"mailto:user@example.org">user@example.org</a>.&nbsp; Servers should ac=
cept<o:p></o:p></pre><pre>&nbsp;&nbsp; as valid a set of users for at least=
 one domain.&nbsp; A server may treat<o:p></o:p></pre><pre>&nbsp;&nbsp; oth=
er domains as having no valid translations.&nbsp; A more general<o:p></o:p>=
</pre><pre>&nbsp;&nbsp; service is provided when a server is capable of acc=
epting users for<o:p></o:p></pre><pre>&nbsp;&nbsp; multiple domains, or for=
 all domains, subject to security<o:p></o:p></pre><pre>&nbsp;&nbsp; constra=
ints.<o:p></o:p></pre><p class=3DMsoNormal>I suspect that the 'should' and =
'may' ought to be 'SHOULD' and 'MAY'.&nbsp; Arguably the 'should' ought to =
be a 'MUST' if the server recognises owner and owner_group as attributes. i=
.e., a mandatory to implement.<o:p></o:p></p></div><div><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p></o:p></p></d=
iv><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><b=
r>s5.9, para 6:<br><br><o:p></o:p></p><pre>In the absence of such a<o:p></o=
:p></pre><pre>&nbsp;&nbsp; configuration, or as a default, the current DNS =
domain name should be<o:p></o:p></pre><pre>&nbsp;&nbsp; the value used for =
the &quot;dns_domain&quot;.<o:p></o:p></pre><p class=3DMsoNormal style=3D'm=
argin-bottom:12.0pt'>The term 'current DNS domain' is not very specific. Do=
 you mean the DNS domain in which the host resides?&nbsp; <o:p></o:p></p></=
div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMs=
oNormal>Yes, tried to make clearer<o:p></o:p></p></div><div><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></=
p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>s5.9, 1st bullet=
 point on page 50: A reference to (probably) RFC 5890 is needed to explain =
U-labels and other IDN stuff is needed (probably best in s1.6).<o:p></o:p><=
/p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal>Added the reference, even though this may change.<o:p></o:p></=
p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNorm=
al>s5.10: Expand UCS acronym (and add ref to ISO.10646-1.1993).<o:p></o:p><=
/p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal>ok <o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:=
p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>s6.1, bu=
llet 3:&nbsp; An explanation of what is meant by (acl) inheritance is neede=
d.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div=
><div><p class=3DMsoNormal>I'm okay with&nbsp;inheritance being well unders=
tood by the target audience.<o:p></o:p></p></div><div><p class=3DMsoNormal>=
<o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div=
><p class=3DMsoNormal>s6.1, bullet 4, sub-bullet 1:<br><br><o:p></o:p></p><=
pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; Setting only the mode attribute =
should effectively control the<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; traditional UNIX-like permissions of read, write,=
 and execute<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; on owner, owner_group, and other.<o:p></o:p></pre><p class=3DMsoNor=
mal>Does this extend to the interpretation of the x bit as searchability on=
 directory objects as per UNIX?&nbsp; <o:p></o:p></p></div><div><p class=3D=
MsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p></div><div><p class=3DMsoNormal>Yes, the next question is does it =
need to be explained? I think not.&nbsp;<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p><=
/o:p></p><div><p class=3DMsoNormal><br>s6.1, bullet 5:&nbsp; Does mode sett=
ing affect the inherited ACL attributes as well as the those of the object =
for which the mode is set?<br><br>s6.2.1, next to last para: Expand SMB (an=
d/or give reference).<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p></div><div><p class=3DMsoNormal>expanded, getting correct ref=
erence<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div=
><p class=3DMsoNormal><br>s6.2.1.1, sentence above table:<br><br><o:p></o:p=
></p><pre>&nbsp;&nbsp; All four but types are permitted in the acl attribut=
e.<o:p></o:p></pre><p class=3DMsoNormal>'but' is clearly not the right word=
 but I am not quite sure what this trying to say.<o:p></o:p></p></div><div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>'=
bit'<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></d=
iv><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><b=
r>s6.2.1.3.1, ACE4_ADD_SUBDIRECTORY:<br>Why is the RENAME operation affecte=
d if the object being renamed is a file rather than a directory?<o:p></o:p>=
</p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p clas=
s=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Good que=
stion,&nbsp;<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></=
p><div><p class=3DMsoNormal><br>s6.2.1.3.1, ACE4_EXECUTE:&nbsp; <br>Given t=
hat directory operation aliases for ACE4_READ_DATA and ACE4_WRITE_DATA have=
 been defined, it would seem sensible to define an alias for the directory/=
traverse use case of ACE4_EXECUTE.<br><br>s6.2.1.3.1, ACE4_DELETE_CHILD and=
 ACE4_DELETE:<br>s/for information on/for information on how/ <o:p></o:p></=
p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p=
></p><div><p class=3DMsoNormal><br>s6.2.1.3.1, ACE4_WRITE_ATTRIBUTES - file=
 times modification:<br>Can the client find out if the server uses client o=
r server times? I didn't see an attribute that tells me which is allowed on=
 the server - cansettime only allows the client to find out if it can modif=
y the times.&nbsp; What happens (which error code comes back) if the SETATT=
R has the wrong sort of time spec (e.g., client time when the server only s=
upports server times)? As previously mentioned, is the server expected to d=
o any sanity checks on supplied client times (maybe not allowing - at least=
 - ordinary users to set times backwards from previous values.)<o:p></o:p><=
/p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><div><p =
class=3DMsoNormal>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Permission to change t=
he times associated with a<o:p></o:p></p></div><div><p class=3DMsoNormal>&n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; file or directory to an arbitrary value.<o=
:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><di=
v><p class=3DMsoNormal>Which means to me that no sanity check need be appli=
ed.<o:p></o:p></p></div></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNorm=
al><br>s6.2.1.4: A few words on the effect of inheritance would help and an=
d clarify the next two comments.&nbsp; Points that arise from the discussio=
ns in s6.2.1.4.1:<br>- Is there a time factor in ACEs?&nbsp; The phrase 'ne=
wly created' seems to imply that there is.&nbsp; The document doesn't reall=
y explain how it is expected that inheritance will be implemented: It could=
 be seen as copying the current set of ACEs from the parents up the tree at=
 the time an object is created or tracking the ACEs up the tree when a acce=
ss request has to be verified. <br>- Is the inheritance fully recursive dow=
n a directory tree?&nbsp; I guess that it is unless the NO_PROPAGATE flag i=
s set.. but what about symbolic links?<br>- Does the inheritance propagate =
across mount points?<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p></div><div><p class=3DMsoNormal>Define what you mean by mount =
point. Remember that a mount point is a client<o:p></o:p></p></div><div><p =
class=3DMsoNormal>side artifact and not a server one.<o:p></o:p></p></div><=
div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNorm=
al>If you however consider a server which has a namespace in which one file=
system<o:p></o:p></p></div><div><p class=3DMsoNormal>is mounted on another =
and that is exported to the client as a single namespace,<o:p></o:p></p></d=
iv><div><p class=3DMsoNormal>then my expectation is that the inheritance is=
 not propagated across the<o:p></o:p></p></div><div><p class=3DMsoNormal>fi=
lesystems.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNor=
mal><br>Additionally, how does ACE inheritance interact with hard and symbo=
lic links?&nbsp; Does the inheritance attach to the underlying object or on=
ly to the name path?<br><br>s6.2.1.4.1, ACE4_FILE_INHERIT_ACE:<br>Three iss=
ues:<br>- presumably this implies the ACE is (primarily) inherited by files=
 in the directory to which it applies<br>- does 'any sub-directory' imply t=
hat the inheritance applies recursively down the tree?<br>- does 'any non-d=
irectory file' include symbolic links?<br><br>s6.2.1.4.1, ACE4_DIRECTORY_IN=
HERIT_ACE:<br>Three issues:<br>- Does 'should be added to each *new* direct=
ory created' imply that the ACE does not get inherited by sub-directories a=
re already in existence when the ACE is applied? Either way it would be goo=
d to be explicit about the effect.<br>- Does this apply recursively down th=
e tree?<br>- Would the inheritance apply to symbolic links to directories?<=
br><br>s6.2.2:<br>It would be worth pointing out that the execute permissio=
n bits imply searchability for directory objects.&nbsp; This isn't mentione=
d in READDIR... is this something missing?<o:p></o:p></p></div><div><p clas=
s=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Those ar=
e POSIX semantics.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=
=3DMsoNormal><br>s6.2.2:<br>Are there restrictions on the mode bits that ca=
n be set on named attributes and their directories?&nbsp; Wouldn't make a l=
ot of sense to set the x bits on named attributes&nbsp; (probably), nor the=
 suid and svtx bits.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nb=
sp;</o:p></p></div><div><p class=3DMsoNormal>The mode bits set on a named a=
ttribute would be those on the base file.<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p><=
/o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>s6.3.=
1.2, para 1: s/interpretation the ACL/interpretation of the ACL/<o:p></o:p>=
</p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DM=
soNormal>ok<o:p></o:p></p></div><div><p class=3DMsoNormal><br><br><o:p></o:=
p></p><div><p class=3DMsoNormal><br>s6.1, last para: Expand DCE/DFS acronym=
s.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div=
><div><p class=3DMsoNormal>deleted<o:p></o:p></p></div><p class=3DMsoNormal=
><br><br><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12=
.0pt'><br>s6.2: Expand TLS and SPKM acronyms. (IPsec is 'well-known')<o:p><=
/o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p=
 class=3DMsoNormal>deleted, but I did expand TLS in another place.<o:p></o:=
p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=
=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal>s7.1:<br><br>=
<o:p></o:p></p><pre>These attributes specify such file system<o:p></o:p></p=
re><pre>&nbsp;&nbsp; instances by specifying a server address target (eithe=
r as a DNS name<o:p></o:p></pre><pre>&nbsp;&nbsp; representing one or more =
IP addresses or as a literal IP address)<o:p></o:p></pre><pre>&nbsp;&nbsp; =
together with the path of that file system within the associated<o:p></o:p>=
</pre><pre>&nbsp;&nbsp; single-server namespace.<o:p></o:p></pre><p class=
=3DMsoNormal>I don't understand 'associated single-server namespace'.&nbsp;=
 Does this mean the aggregated logical file system or something else?&nbsp;=
 Having read further I suspect that this at least needs a forward reference=
 to Section 8.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o=
:p></p></div><div><p class=3DMsoNormal>Doesn't the first paragraph of Secti=
on 7 introduce the term?<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p =
class=3DMsoNormal><br>s7.2 and s7.3:&nbsp; These sections are very repetiti=
ve.&nbsp; They essentially convey the fact that if a file system is absent =
only GETATTR on the absent system and READDIR on a&nbsp; referring system w=
ill produce useful answers and only a couple of attributes are valid.<br><b=
r>s7.6:<br><br><o:p></o:p></p><pre>&nbsp;&nbsp; A potential problem exists =
if a client were to allow an open owner to<o:p></o:p></pre><pre>&nbsp;&nbsp=
; have state on multiple filesystems on server, in that it is unclear<o:p><=
/o:p></pre><pre>&nbsp;&nbsp; how the sequence numbers associated with open =
owners are to be dealt<o:p></o:p></pre><pre>&nbsp;&nbsp; with, in the event=
 of transparent state migration.&nbsp; A client can<o:p></o:p></pre><pre>&n=
bsp;&nbsp; avoid such a situation, if it ensures that any use of an open ow=
ner<o:p></o:p></pre><pre>&nbsp;&nbsp; is confined to a single filesystem.<o=
:p></o:p></pre><p class=3DMsoNormal>This paragraph is not very helpful beca=
use the concepts of 'open owner', associated state and sequence numbers hav=
e not been introduced up to this point apart from as cryptic references in =
type definitions.&nbsp; At worst a forward reference is needed.&nbsp; It mi=
ght be better to have a brief introduction to the state mechanism under the=
 NFSv4 basic concepts section (maybe around s1.5.4).<br><br>Without this in=
troduction I have no idea under what circumstances the 'open owner' might h=
ave state on multiple file systems - and hence what I would have to do to a=
void going down this rat hole.<o:p></o:p></p></div><div><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>As a whole, this doc=
ument assumes you have already read this document before you read it.<o:p><=
/o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p=
 class=3DMsoNormal>Changing that is beyond the scope of work I want to unde=
rtake.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
/div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal>=
<br>s7.7, last para:&nbsp; Would be worthwhile to either substitute 'networ=
k order' for 'big endian' or add it as an alternative. (It turns out that s=
9.14 uses network order for just this requirement - consistency would be go=
od!)<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></d=
iv><div><p class=3DMsoNormal>The entirety 7.7 from draft 25 is now gone.<o:=
p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=
=3DMsoNormal><br>s7.7.1:<br><br><o:p></o:p></p><pre>&nbsp;&nbsp; When a sin=
gle file system may be accessed at multiple locations,<o:p></o:p></pre><pre=
>&nbsp;&nbsp; either because of an indication of file system identity as re=
ported<o:p></o:p></pre><pre>&nbsp;&nbsp; by the fs_locations attribute, the=
 client will, depending on specific<o:p></o:p></pre><pre>&nbsp;&nbsp; circu=
mstances as discussed below, either:<o:p></o:p></pre><p class=3DMsoNormal>T=
he first 'either' has no corresponding 'or'.<br>The second 'either' needs a=
n 'or' at the end of the first bullet.<br><br>s7.7.1, 2nd bullet: s/Accesse=
s/Access/<br><br>s7.7.2, para 3 (and&nbsp; para 2):<br><br><o:p></o:p></p><=
pre>&nbsp;&nbsp; When there is co-operation in filehandle assignment, the t=
wo file<o:p></o:p></pre><pre>&nbsp;&nbsp; systems are reported as being in =
the same handle classes.<o:p></o:p></pre><p class=3DMsoNormal>It appears th=
at the term 'handle class' is not defined until s7.9.1 (like fileid class i=
n the s7.7.3 and various other attribute classes).&nbsp; A forward referenc=
e to this section is essential&nbsp; (or maybe better a reordering of the s=
ections).&nbsp; It would be worth a note somewhere in this area that a clie=
nt needs to ensure that it knows the fh_expire_type for any filesystem inst=
ance it is accessing&nbsp; in case it get forcibly transitioned, since it c=
an't find out post-facto from an absent filesystem.<br><br>s7.7.2, paras 2 =
and 3:<br><br><o:p></o:p></p><pre>&nbsp;&nbsp; When there is no such cooper=
ation in filehandle assignment, the two<o:p></o:p></pre><pre>&nbsp;&nbsp; f=
ile systems are reported as being in different handle classes.&nbsp; In<o:p=
></o:p></pre><pre>&nbsp;&nbsp; this case, all filehandles are assumed to ex=
pire as part of the file<o:p></o:p></pre><pre>&nbsp;&nbsp; system transitio=
n.&nbsp; Note that this behavior does not depend on<o:p></o:p></pre><pre>&n=
bsp;&nbsp; fh_expire_type attribute and depends on the specification of the=
<o:p></o:p></pre><pre>&nbsp;&nbsp; FH4_VOL_MIGRATION bit.<o:p></o:p></pre><=
pre><o:p>&nbsp;</o:p></pre><pre>&nbsp;&nbsp; When there is co-operation in =
filehandle assignment, the two file<o:p></o:p></pre><pre>&nbsp;&nbsp; syste=
ms are reported as being in the same handle classes.&nbsp; In this<o:p></o:=
p></pre><pre>&nbsp; &nbsp;case, persistent filehandles remain valid after t=
he file system<o:p></o:p></pre><pre>&nbsp;&nbsp; transition, while volatile=
 filehandles (excluding those that are only<o:p></o:p></pre><pre>&nbsp;&nbs=
p; volatile due to the FH4_VOL_MIGRATION bit) are subject to expiration<o:p=
></o:p></pre><pre>&nbsp;&nbsp; on the target server.<o:p></o:p></pre><p cla=
ss=3DMsoNormal>I do not understand the final parts of these paras where FH4=
_VOL_MIGRATION is mentioned:<br>- In para 2, FH4_VOL_MIGRATION is a bit in =
fh_expire_type, so I fail to understand how the behavior can both be indepe=
ndent of fh_expire_type and dependent on a bit within it at the same time.<=
br>- In para 3, the wording appears to imply that filehandles with FH4_VOL_=
MIGRATION set will not expire. My&nbsp; understanding of the definition of =
this bit was that such filehandles would explicitly expire on migration.&nb=
sp; Accordingly I would have expected that such filehandles would have been=
 guaranteed to expire on transition&nbsp; - but maybe this is some difficul=
ty with the meanings of transition and migration?<br><br>s7.7.3, last para:=
<br><br><o:p></o:p></p><pre>&nbsp;&nbsp; Note that when consistent fileids =
do not exist across a transition<o:p></o:p></pre><pre>&nbsp;&nbsp; (either =
because there is no continuity of fileids or because fileid<o:p></o:p></pre=
><pre>&nbsp;&nbsp; is not a supported attribute on one of instances involve=
d), and there<o:p></o:p></pre><pre>&nbsp;&nbsp; are no reliable filehandles=
 across a transition event (either because<o:p></o:p></pre><pre>&nbsp;&nbsp=
; there is no filehandle continuity or because the filehandles are<o:p></o:=
p></pre><pre>&nbsp;&nbsp; volatile),<o:p></o:p></pre><p class=3DMsoNormal>I=
 don't understand how there can be no filehandle continuity other than beca=
use the filehandle is volatile.&nbsp; If a filehandle is not volatile, then=
 it is persistent and s4.2.2 appears to indicate that any persistent fileha=
ndle would be valid across a transition.<br><br>s7.7.5 and s7.7.6, last par=
as:&nbsp; s7.9.1 states that distinct server instances are always in differ=
ent change classes. Since there doesn't seem to be anyway to check that two=
 instances of a server are actually the same when accessed over different c=
onnections, the consistent change class mentioned in the last para of s7.7.=
5 and the continuity mentioned in the last para of s7.7.6 can never occur i=
n practice and would probably be better omitted.<br><br>s7.7.6, para 7: A r=
eference to s9.6.3.4 where the edge conditions are described would be desir=
able.<br><br>s7,7,8:&nbsp; s7.9.1 says all server instances have different =
readdir classes, so once again the instances will never be deemed consisten=
t.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div=
><div><p class=3DMsoNormal>^^GONE^^ <o:p></o:p></p></div><div><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o=
:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMs=
oNormal><br>s7.9:&nbsp; Copying the fs_location(s)4 structure definitions h=
ere creates a double maintenance problem.&nbsp; Better just to reference ss=
2.2.6/2.2.7 where they are defined.<o:p></o:p></p></div><div><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Actually, due t=
o the way we structure our document source, this is always in sync.<o:p></o=
:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p c=
lass=3DMsoNormal>But I don't like how we have two sections and 1 descriptio=
n here:<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p>=
</div><div><div><p class=3DMsoNormal>2.2.6. &nbsp;fs_location4<o:p></o:p></=
p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal>&nbsp; &nbsp;struct fs_location4 {<o:p></o:p></p></div><div><p=
 class=3DMsoNormal>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;utf8val_REQUIRE=
D4 &nbsp; &nbsp; &nbsp; server&lt;&gt;;<o:p></o:p></p></div><div><p class=
=3DMsoNormal>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pathname4 &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; rootpath;<o:p></o:p></p></div><div><p=
 class=3DMsoNormal>&nbsp; &nbsp;};<o:p></o:p></p></div><div><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>2.2.7. &nbsp;fs_=
locations4<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p></div><div><p class=3DMsoNormal>&nbsp; &nbsp;struct fs_locations4 {<o:p>=
</o:p></p></div><div><p class=3DMsoNormal>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp;pathname4 &nbsp; &nbsp; &nbsp; fs_root;<o:p></o:p></p></div><div><p=
 class=3DMsoNormal>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;fs_location4 &n=
bsp; &nbsp;locations&lt;&gt;;<o:p></o:p></p></div><div><p class=3DMsoNormal=
>&nbsp; &nbsp;};<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p></div><div><p class=3DMsoNormal>&nbsp; &nbsp;The fs_location4 and =
fs_locations4 data types are used for the<o:p></o:p></p></div><div><div><p =
class=3DMsoNormal>&nbsp; &nbsp;fs_locations recommended attribute which is =
used for migration and<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp;=
 &nbsp;replication support.<o:p></o:p></p></div></div><div><p class=3DMsoNo=
rmal><o:p>&nbsp;</o:p></p></div></div><div><p class=3DMsoNormal>5661 got ri=
d of these as Structured Data Types.<o:p></o:p></p></div><div><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>XXX<o:p></o:p>=
</p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DM=
soNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s8:&nbsp; Pla=
cing this section much earlier in the document would help understanding, es=
pecially of Section 7.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p></div><div><p class=3DMsoNormal>Ouch. Yes, single server nam=
espace before multi-server.<o:p></o:p></p></div><p class=3DMsoNormal><br><b=
r><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><=
br>s9:&nbsp; There is a comment in s15.12.5 (para 2) that exactly how locks=
 behave depends on the underlying semantics of the exported&nbsp; file syst=
em.&nbsp; It would be worth reproducing that statement here to ensure that =
this section is interpreted in that context. <o:p></o:p></p></div><div><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I don=
't see how to tie that into the content of s9. In s9, we are talking about =
the needs of the<o:p></o:p></p></div><div><p class=3DMsoNormal>protocol and=
 not the permission checking of s15.12.5.<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p><=
/o:p></p><div><p class=3DMsoNormal>s9, last para:<br><br><o:p></o:p></p><pr=
e>To support Win32 share reservations it is necessary to atomically<o:p></o=
:p></pre><pre>&nbsp;&nbsp; OPEN or CREATE files.<o:p></o:p></pre><p class=
=3DMsoNormal>Add 'and apply the appropriate locks in the same operation' to=
 the end of this sentence.<o:p></o:p></p></div><div><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>ack<o:p></o:p></p></div><div>=
<p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s=
9.1: I think that for the sake of clarity, it would be worth explicitly sta=
ting that the client has to hold an open before applying locks to the same =
file.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></=
div><div><p class=3DMsoNormal>You need a FH to apply a LOCK. That means eit=
her you got it from a OPEN (in which case it is supposed to be a regular fi=
le)<o:p></o:p></p></div><div><p class=3DMsoNormal>or you got it from a LOOK=
UP, PUTROOTFH, etc (in which case it may be a regular file or any other fil=
esystem object).<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3D=
MsoNormal><br>s9.1:&nbsp; What happens if you try to acquire a byte range l=
ock on a non-file filesystem object?<o:p></o:p></p></div><div><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o=
:p></p></div><div><p class=3DMsoNormal>I would expect to see&nbsp;NFS4ERR_B=
ADHANDLE returned.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=
=3DMsoNormal><br>s9.1.1, para after struct nfs_client_id4 definition: s/whi=
ch the server has previously recorded the client/which the server has previ=
ously recorded for the client/.&nbsp; Also copying the structure definition=
 creates a double maintenance problem.&nbsp; A ref to s2.2.12 would be bett=
er.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></di=
v><div><p class=3DMsoNormal>Ack.<o:p></o:p></p></div><div><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>There isn't a main=
tenance issue and since the text is directly explaining the<o:p></o:p></p><=
/div><div><p class=3DMsoNormal>fields, I want to avoid a reference.<o:p></o=
:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p c=
lass=3DMsoNormal>I.e., here is why the XDR presented in the document is not=
 a maintenance issue:<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p></div><div><p class=3DMsoNormal>&lt;pre&gt;<o:p></o:p></p></d=
iv><div><div><p class=3DMsoNormal>&nbsp; &nbsp; &nbsp; &lt;t&gt;<o:p></o:p>=
</p></div><div><p class=3DMsoNormal>&nbsp; &nbsp; &nbsp; &nbsp; Client iden=
tification is encapsulated in the following structure:<o:p></o:p></p></div>=
<div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNor=
mal>&nbsp; &nbsp; &nbsp; &nbsp; &lt;?rfc include=3D'autogen/type_nfs_client=
_id4.xml'?&gt;<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp; &nbsp; =
&nbsp; &lt;/t&gt;<o:p></o:p></p></div><div><p class=3DMsoNormal>&lt;/pre&gt=
;<o:p></o:p></p></div></div><p class=3DMsoNormal><br><br><o:p></o:p></p><di=
v><p class=3DMsoNormal><br>s9.1.3, first sentence:&nbsp; Question: Should t=
he 'including' list also have share reservations or are these included in b=
yte-range locks or opens?<o:p></o:p></p></div><div><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Opens.<o:p></o:p></p></di=
v><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoN=
ormal>In any event, the entire parenthetical clause can go.&nbsp;<o:p></o:p=
></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoN=
ormal><br>s9.1.3.5: Expand acronym I/O - this isn't on the RFC Editors 'wel=
l known' list - maybe strangely. <o:p></o:p></p></div><div><p class=3DMsoNo=
rmal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Can you suggest t=
hey add it? Pretty well understood acronym.<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p=
></o:p></p><div><p class=3DMsoNormal><br>s9.1.3.2: NFS4_UINT32_MAX should b=
e in the proposed constants section.<o:p></o:p></p></div><div><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Which would me=
an we have such a section.<o:p></o:p></p></div><p class=3DMsoNormal><br><br=
><o:p></o:p></p><div><p class=3DMsoNormal><br>s9.1.3.2, para 2 and s9.1.6, =
para 1: The two paragraphs have conflicting statements about the initial va=
lue of seqid for locks (s9.1.3.2 =3D&gt; 1, s9.1.6 =3D&gt; server choice) -=
 not that it really matters much unless clients check that they always get =
1!&nbsp; Note that s9.1.6 does say anything about missing out 0 when wrappi=
ng round.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div><div><p class=3DMsoNormal>So S9.1.3.2 is correct, thanks for catchi=
ng this one!<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3D=
MsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-=
bottom:12.0pt'><br>s9.1.5, para 9 (bottom of page 116): s/ (e.g., another o=
pen specify denial of READs)/(e.g., another open specifying denial of READs=
)/<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div=
><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNo=
rmal>ack<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><d=
iv><p class=3DMsoNormal>s9.4:&nbsp; Changing:<br>OLD:<br>&nbsp;&nbsp; The s=
erver is not<br>&nbsp;&nbsp; required to maintain a list of pending blocked=
 locks as it is used to<br>&nbsp;&nbsp; increase fairness and not correct o=
peration.<br>NEW:<br>&nbsp;&nbsp; The server is not<br>&nbsp;&nbsp; require=
d to maintain a list of pending blocked locks as it is not used to<br>&nbsp=
;&nbsp; provide correct operation but only to increase fairness.<br>scans m=
ore easily.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p>=
</p></div><div><p class=3DMsoNormal>Ok<o:p></o:p></p></div><p class=3DMsoNo=
rmal><br><br><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-botto=
m:12.0pt'><br>s9.6: If I understand correctly, share reservations with a DE=
NY reservation are essentially locks that cover the whole file and adjust d=
ynamically to cover the entire byte range of the file if it changes. Presum=
ably. therefore, the whole discussion of lock recovery applies both to byte=
 range locks and share reservation implicit locks.&nbsp; I think it would b=
e worth pointing out that this is the case at the beginning of s9.6 (assumi=
ng this is indeed the case - or alternatively explaining how things differ =
with share reservations).<o:p></o:p></p></div><div><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Share reservations are a =
subset of locks. Seeing an unadorned usage of locks<o:p></o:p></p></div><di=
v><p class=3DMsoNormal>should alert the reader that it means both share and=
 byte level locks.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p cl=
ass=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal>s9.8, para=
 4: In the last sentence s/may not/MUST NOT/. <o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>OK<o=
:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p clas=
s=3DMsoNormal><br>s9.8, para 5: <br><br><o:p></o:p></p><pre>The client may =
accomplish this task by<o:p></o:p></pre><pre>&nbsp;&nbsp; issuing an I/O re=
quest, either a pending I/O or a zero-length read,<o:p></o:p></pre><pre>&nb=
sp;&nbsp; specifying the stateid associated with the lock in question.<o:p>=
</o:p></pre><p class=3DMsoNormal>I am not sure how you 'issue a pending I/O=
'.&nbsp; Does this mean checking whether there is already a pending I/O req=
uest associated with this stateid? <o:p></o:p></p></div><div><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>What I think it=
 means is that if there is a pending I/O in the client's queue,<o:p></o:p><=
/p></div><div><p class=3DMsoNormal>it should issue that and if not, then it=
 can do a zero-length read.<o:p></o:p></p></div><div><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></=
div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal s=
tyle=3D'margin-bottom:12.0pt'><br>s10.2, para 6: s/server times its wait/se=
rver times out its wait/<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div=
><div><p class=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><br>=
<br><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'=
>s10.2, para 7: I think the lat two sentences are requiremenst:<br>next to =
last sentence: s/may/MAY/<br>last sentence: s/should not/SHOULD NOT/<o:p></=
o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p>=
</o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>s10.2.1,=
 para 9 (last para on p146):&nbsp; I think that this para is referring to t=
he server not the client: s/client/server/<o:p></o:p></p></div><div><p clas=
s=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>The para=
graph details how a client might be able to determine if the<o:p></o:p></p>=
</div><div><p class=3DMsoNormal>server is limiting the number of available =
delegations.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoN=
ormal>s10.2.1, para 12 (2nd bullet): Good to have a ref to the Courtesy Loc=
ks section (s9.6.3.1)<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p></div><p class=3DMsoNormal>ok<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s10.2.1=
, para 17:&nbsp; &quot;s special semantic adjustments&quot; =3D&gt; either =
&quot;special semantic adjustments&quot; or &quot;a special semantic adjust=
ment&quot;<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p></div><div><p class=3DMsoNormal>ok<o:p></o:p></p></div><div><p class=3DM=
soNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p=
></p><div><p class=3DMsoNormal><br>s10.2.1, para 19:&nbsp; It might be bett=
er to explain about the distinction between the CLAIM_xxx attribute to be u=
sed after server and client restarts that doesn't come till para 24 current=
ly - the changeover to CLAIM_PREVIOUS in this para isn't obvious without th=
is discussion. <o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</=
o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>XXX<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p=
></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>s10=
.2.1, last para, sentence 1: s/Is/is/<o:p></o:p></p></div><div><p class=3DM=
soNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p></o:p>=
</p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNo=
rmal style=3D'margin-bottom:12.0pt'>s10.3, 1st bullet: s/and not change/and=
 not the change attribute/ ... there are a couple of other instances where =
this might also be helpful.<o:p></o:p></p></div><div><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p></o:p></p></div>=
<div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><=
br><br><o:p></o:p></p><div><p class=3DMsoNormal>s10.3, 2nd bullet: s/client=
 OPENS as file/the client OPENS a file/<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>thanks<o:p></o=
:p></p></div><div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=
=3DMsoNormal><br>s10.3.3:&nbsp; I need to think a bit more about what manda=
tory locking implies.<br><br>s10.4, para after 2nd set of bullets: should t=
he 'standard stateid' be associated with the open-owner rather than the loc=
k-owner as currently stated.<o:p></o:p></p></div><div><p class=3DMsoNormal>=
<o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Yes, very good catch!<=
o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><d=
iv><p class=3DMsoNormal>I had to go back to the RFC 3530 to clear it up...<=
o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p cla=
ss=3DMsoNormal><br>s10.4.3: Should there be some discussion of wrap round i=
n the 'change' attribute?<o:p></o:p></p></div><div><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>No, there is nothing spec=
ial about a change value of 0. This is unlike a seqid, which<o:p></o:p></p>=
</div><div><p class=3DMsoNormal>has semantics on a wrap.<o:p></o:p></p></di=
v><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br=
>s10.5.1, para 2: s/a complete cached copy&nbsp; of file/a complete cached =
copy&nbsp; of the file/,<br>s/In other case/In other cases/<o:p></o:p></p><=
/div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DM=
soNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p=
><div><p class=3DMsoNormal><br>s10.7, para 2:<br>OLD:<o:p></o:p></p><pre>(r=
egardless whether the file is local file or is being access remotely)<o:p><=
/o:p></pre><p class=3DMsoNormal>NEW:<o:p></o:p></p><pre>(regardless of whet=
her the file is local file or is being accessed remotely)<o:p></o:p></pre><=
/div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DM=
soNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p=
><div><p class=3DMsoNormal>s11, item 8, first sentence: s/implement/inpleme=
nted/<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></=
div><div><p class=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><=
br><br><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0=
pt'><br>s11, items 9 and 10: Its probably not that important, but would OPT=
IONAL &lt;=3D&gt; REQURED be allowed - i.e., two 'levels' of change rather =
then the explicit one currently documented.<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Yes, bu=
t we don't want a change here.<o:p></o:p></p></div><div><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><d=
iv><p class=3DMsoNormal>s12.1.1, bullet 2: s/in many case/in many cases/<br=
><br>s12.1.2, para 1: s/important to understand/important to understanding/=
<br><br>s12.1.2: The quoted sections should be attributed to where they com=
e from (including section numbers).<br><br>s12.1.2: There seems to be a spu=
rious ACCENT in this para: <br><br><o:p></o:p></p><pre>&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;LATIN SMALL LETTER E, COMBINING MACRON, A=
CCENT, COMBINING ACUTE<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; ACCENT (U+0xxx, U+0304, U+0301)<o:p></o:p></pre><p class=
=3DMsoNormal style=3D'margin-bottom:12.0pt'>s12.1.2 (Maybe expand IDNA agai=
n - its 180 pages since it was last expanded).<br><br>s12.2.3, para just af=
ter Table 5: s/or it in may/or it may/<br><br>s12.3: (maybe expand UCS agai=
n since it is 130 pages since previous occurrence).<br><br>s12.7, 2nd bulle=
t: s/lintext4/linktext4/;&nbsp; also the term 'link text' hasn't been prope=
rly defined.<br><br>s12.7.1.5.1: Need to expand NFC and NFD and provide a r=
eference.<br><br>s12.7.1.5.2, para 8, last sentence: s/it should generally =
mapped/it should generally be mapped/<br><br>s12.7.3, bullet 4: Should 'con=
verting a user to group to an internal id' be 'converting a user or group t=
o an internal id'?<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div>=
<p class=3DMsoNormal>All of 12 is rewritten.<o:p></o:p></p></div><div><p cl=
ass=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:=
p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>s13.1.=
1.7: s/fit/fitted/<o:p></o:p></p></div><p class=3DMsoNormal><o:p>&nbsp;</o:=
p></p><div><p class=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal=
><br><br><o:p></o:p></p><div><p class=3DMsoNormal>s13.1.2.1 s/file handle/f=
ilehandle/<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p></div><div><p class=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNor=
mal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s13.1.2.7: should =
refer to filesystem object rather than file.<o:p></o:p></p></div><div><p cl=
ass=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>ok<o:p></o:=
p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p cl=
ass=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s13.1.=
4.2: Value of NFS4ERR_DQUOT is 19 here but 69 in table 8<o:p></o:p></p></di=
v><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoN=
ormal>Fied<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p>=
<div><p class=3DMsoNormal><br>s13.1.4.3/4/5/7: should refer to filesystem o=
bject rather than file.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div><div><p class=3DMsoNormal>done<o:p></o:p></p></div><d=
iv><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br=
><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s13.1.4.8: Does this appl=
y to any filesystem object rather than just file or directory?<o:p></o:p></=
p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>We could =
just say filesystem object.<o:p></o:p></p></div><div><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>fixed up<o:p></o:p></p>=
</div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNo=
rmal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s13,1.4.11: Value=
 of NFS4ERR_NXIO is 5 here but 6 in table 8 (and value 5 is already used fo=
r NFS4ERR_IO).<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o=
:p></p></div><p class=3DMsoNormal>ok<o:p></o:p></p></div><div><p class=3DMs=
oNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s13.1.5.2: Val=
ue of NFS4ERR_BAD_STATEID is 10026 here but 10025 in table 8 (and value 100=
26 is already used for NFS4ERR_BAD_SEQID).<o:p></o:p></p></div><div><p clas=
s=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p><=
/o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3D=
MsoNormal><br>s13.1.5.2, bullet 1: should refer to filesystem object rather=
 than file.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p>=
</p></div><div><p class=3DMsoNormal>xxx<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p><=
/o:p></p><div><p class=3DMsoNormal><br>s13.1.7: s/When the strings are not =
are of length zero./When the strings are not of length zero./<o:p></o:p></p=
></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p=
></p><div><p class=3DMsoNormal><br>s13.2-13.4: I didn't check these tables.=
&nbsp; Table 11 can be checked automatically if it is thought worthwhile by=
 inverting tables 9 and 10.<o:p></o:p></p></div><div><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>These are autogenerated=
 from the same source.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p></div><div><p class=3DMsoNormal>As can be seen, the section =
titles were not.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3D=
MsoNormal style=3D'margin-bottom:12.0pt'><br>s14.2: Might be worth stating =
that COMPOUND doesn't represent a 'transaction', as is expressed in para 3.=
<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><=
div><p class=3DMsoNormal>ok<o:p></o:p></p></div><div><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div>=
<p class=3DMsoNormal>s14.2, para 4:&nbsp; The operation descriptions explic=
itly mention what happens to the current filehandle after operations.&nbsp;=
 Nothing is said about the stability of the saved filehandle.&nbsp; Can thi=
s be assumed to be preserved in all cases whether the operation succeeds or=
 fails?&nbsp; I guess it would also be useful to explicitly state that ther=
e are no guarantees about the contents of the current filehandle after an o=
peration unless explicitly stated (i.e., after most errors you ought to rel=
oad the current filehandle).<o:p></o:p></p></div><div><p class=3DMsoNormal>=
<o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Yes, if you do not mod=
ify these filehandles, then the last one entered is valid. I.e., think of i=
t as a register.<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:=
p></p><div><p class=3DMsoNormal><br>s14.3, para 1: s/UNSTABLE/UNSTABLE4/<o:=
p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p c=
lass=3DMsoNormal>ok<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p></div><div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>s15.2.5, para 2: I am =
not sure how you *could* mix operations - I was under the impression that t=
he COMPOUND is submitted in the context of a particular client ID and the c=
urrent/saved filehandles are tied to the client ID/connection. The client I=
D can't be changed in a single compound statement so this seems a spurious =
statement.&nbsp; Presumably if stateid's etc are used on the wrong client I=
D the server will object. See also s15.18.6.<o:p></o:p></p></div><div><p cl=
ass=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p></div><div><p class=3DMsoNormal>It is possible to migrate a =
filesystem and state from one server to another, in which case the client c=
ould have a client ID that<o:p></o:p></p></div><div><p class=3DMsoNormal>wa=
s migrated.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p>=
</p></div><div><p class=3DMsoNormal>The intent here is to not mingle such s=
tate in a COMPOUND.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=
=3DMsoNormal style=3D'margin-bottom:12.0pt'>s15.3.4: Presumably the access =
permissions generally apply to named attributes.&nbsp; Currently it only ta=
lks about files and directories.<o:p></o:p></p></div><div><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p></div><div><div><p class=3DMsoNormal>&nbsp; &nbsp;ACCESS determines the =
access rights that a user, as identified by the<o:p></o:p></p></div><div><p=
 class=3DMsoNormal>&nbsp; &nbsp;credentials in the RPC request, has with re=
spect to the file system<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbs=
p; &nbsp;object specified by the current filehandle.<o:p></o:p></p></div><d=
iv><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNorma=
l>So a named attribute is a file system object.<o:p></o:p></p></div></div><=
div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><b=
r><br><o:p></o:p></p><div><p class=3DMsoNormal>s15.3.5, para 2, sentence 3:=
 s/which will result/which might result/?<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p></=
o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DM=
soNormal><br>s15.3.5, para 4: I found the following confusing:<br><br><o:p>=
</o:p></p><pre>&nbsp;&nbsp; The client should use the effective credentials=
 of the user to build<o:p></o:p></pre><pre>&nbsp;&nbsp; the authentication =
information in the ACCESS request used to<o:p></o:p></pre><pre>&nbsp;&nbsp;=
 determine access rights.<o:p></o:p></pre><p class=3DMsoNormal style=3D'mar=
gin-bottom:12.0pt'>I am not sure where there is any authentication info (ex=
plicitly) &quot;in the ACCESS request&quot; - the parameter is just the req=
uested access mask.&nbsp; Where is the auth info?<o:p></o:p></p></div><div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>T=
he entire COMPOUND is inside a RPC layer request. NFS operations use the cr=
edentials<o:p></o:p></p></div><div><p class=3DMsoNormal>from that layer to =
determine ACCESS.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;=
</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p cla=
ss=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal>s15.9.4:<br=
>OLD:<br><br><o:p></o:p></p><pre>The server returns an attribute bitmap tha=
t<o:p></o:p></pre><pre>&nbsp;&nbsp; indicates the attribute values for whic=
h it was able to return,<o:p></o:p></pre><p class=3DMsoNormal><br>NEW:<br><=
br><o:p></o:p></p><pre>The server returns an attribute bitmap that<o:p></o:=
p></pre><pre>&nbsp;&nbsp; indicates the attributes for which it was able to=
 return values,<o:p></o:p></pre><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
/div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DM=
soNormal>ack<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></=
p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>s15.9.5, last se=
ntence: s/returned if while a delegation/returned if [or while] a delegatio=
n/<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div=
><div><p class=3DMsoNormal>ok<o:p></o:p></p></div><p class=3DMsoNormal><br>=
<br><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'=
>s15.11.4:&nbsp; This section refers explicitly to files.&nbsp; Is it ever =
possible to make hard links to:<br>- directories?<br>- named attributes?<br=
>- device and other special types of 'file'?<br>It would be good to be expl=
icit.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></=
div><div><p class=3DMsoNormal>Going to pass on this one.<o:p></o:p></p></di=
v><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></=
p><div><p class=3DMsoNormal>s15.12.4, para 2:<br><br><o:p></o:p></p><pre> T=
o lock the file from a specific offset<o:p></o:p></pre><pre>&nbsp;&nbsp; th=
rough the end-of-file (no matter how long the file actually is) use<o:p></o=
:p></pre><pre>&nbsp;&nbsp; a length field with all bits set to 1 (one).<o:p=
></o:p></pre><p class=3DMsoNormal>Is the end offset fixed at the value give=
n by the length of the file at the time of applying the lock, or does this =
byte range vary as the length of the file changes?<o:p></o:p></p></div><div=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>=
It should vary as the length varies.<o:p></o:p></p></div><p class=3DMsoNorm=
al><br><br><o:p></o:p></p><div><p class=3DMsoNormal>What happens if the len=
gth of the file gets to be less than the start offset, or indeed is current=
ly less than the length of the file?<o:p></o:p></p></div><div><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Someone else c=
an comment, my guess is that POSIX file locking semantics would apply.<o:p>=
</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=
=3DMsoNormal>Actually that is a more general question: Is any special treat=
ment needed for locks that are outside the current length of the file?&nbsp=
; Does the server make any checks on whether&nbsp;a lock is within the curr=
ent length of the file when applied - or automatically delete locks off the=
 end of a file.. probably not but would be good to be explicit. <br><br>s15=
.14.5, para 1:<o:p></o:p></p><blockquote style=3D'margin-top:5.0pt;margin-b=
ottom:5.0pt'><pre>In all of<o:p></o:p></pre><pre>&nbsp;&nbsp; these cases, =
allowed by POSIX locking [<a href=3D"cid:part4.00080701.00010200@dial.pipex=
.com" title=3D"&quot;Section 'fcntl()' of System Interfaces of The Open Gro=
up Base Specifications Issue 6 IEEE Std 1003.1, 2004 Edition, HTML Version =
(www.opengroup.org), ISBN 1931624232&quot;">fcntl</a>] semantics, a client<=
o:p></o:p></pre><pre>&nbsp;&nbsp; receiving this error, should if it desire=
s support for such<o:p></o:p></pre><pre>&nbsp;&nbsp; operations, simulate t=
he operation using LOCKU on ranges<o:p></o:p></pre><pre>&nbsp;&nbsp; corres=
ponding to locks it actually holds, possibly followed by LOCK<o:p></o:p></p=
re><pre>&nbsp;&nbsp; requests for the sub-ranges not being unlocked.<o:p></=
o:p></pre></blockquote><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>=
Shouldn't the client apply the sub-range locks before unlocking?&nbsp; Othe=
rwise there is a potential race condition and some other client could get i=
n a lock between the unlock and the relock. [After a bit of background read=
ing I understand that this rather silly arrangement is 'the way it is done'=
<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><=
div><p class=3DMsoNormal>ack<o:p></o:p></p></div><p class=3DMsoNormal><br><=
br><o:p></o:p></p><div><p class=3DMsoNormal>s15.16.4/5:&nbsp; What happens =
when you apply LOOKUPP to the 'hidden' named attributes directory?&nbsp; Do=
 you get NFS4ERR_NOENT or the filehandle of the object that owns the named =
attributes (inverting OPENATTR)?&nbsp; s15.16.4 only talks about the root o=
f the server's file tree. <br><br>s15.18.6: Do SHARES work on named attribu=
tes?&nbsp; Just checking&#8230;<o:p></o:p></p></div><div><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Named attributes ar=
e not always implemented.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>They would be treated as =
a normal file as far as I can see.<o:p></o:p></p></div><div><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoN=
ormal><br>s15.20.5, para3, sentence 1:&nbsp; &quot;Servers must not require=
...&quot; I think this is a 'MUST NOT'.<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p></=
o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=
=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><br>s15.23.5:=
 Acronm SNEGO needs an expansion and a reference (RFC 2478?)<o:p></o:p></p>=
</div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3D=
MsoNormal>RFC 4178<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></=
o:p></p><div><p class=3DMsoNormal><br>s15.25.4, para 4: If the OPEN didn't =
use locks or share reservations and there is no delegation, is the stateid =
in the READ request the 'basic' OPEN stateid returned with all OPENs? It do=
esn't explicitly say this.&nbsp; (also relevant to WRITE operation - s15.38=
.4, para 3).<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p></div><div><p class=3DMsoNormal>Yes, this is to your earlier question =
on&nbsp;s10.4<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:=
p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMso=
Normal><br>s15.25.5, para 1:<br>OLD:<br><br><o:p></o:p></p><pre> It<o:p></o=
:p></pre><pre>&nbsp;&nbsp; is possible that the server reduce the transfer =
size and so return a<o:p></o:p></pre><pre>&nbsp;&nbsp; short read result.&n=
bsp; Server resource exhaustion may also occur in a<o:p></o:p></pre><pre>&n=
bsp;&nbsp; short read.<o:p></o:p></pre><p class=3DMsoNormal>NEW:<br><br><o:=
p></o:p></p><pre> It<o:p></o:p></pre><pre>&nbsp;&nbsp; is possible that the=
 server reduces the transfer size and so returns a<o:p></o:p></pre><pre>&nb=
sp;&nbsp; short read result.&nbsp; Server resource exhaustion may also resu=
lt in a<o:p></o:p></pre><pre>&nbsp;&nbsp; short read.<o:p></o:p></pre><p cl=
ass=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p></o:p></p></div><div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><b=
r><o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>s=
15.28.4: The specification says nothing about the semantics of sub-director=
y removal.&nbsp; NFSv3 says that 'some servers won't allow removal of non-e=
mpty directories'.&nbsp; What is the story for NFSv4?&nbsp; Is there any st=
andardised strategy for dealing with 'orphaned' resources in sub-directorie=
s if the server does allow a non-empty sub-directory to be deleted?<o:p></o=
:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>My gu=
ess is that server implementations fall back on their NFSv3 behavior.<o:p><=
/o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br>=
<o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>s15=
.29.4, para 5:&nbsp; It would be clearer to say that the operation will fai=
l if the saved and current file handles refer to named attribute directorie=
s attached to different filesystem objects.<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I'd lik=
e to keep the pain in place for anyone who reads that sentence.<o:p></o:p><=
/p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal>XXX<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:=
p></p><div><p class=3DMsoNormal>s15.30.5, para 1 , last sentence: s/such th=
at is could/such that it could/<o:p></o:p></p></div><div><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>ok<o:p></o:p></p></=
div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal><=
br>s15.33.5, para 2:<br><br><o:p></o:p></p><pre>The filehandle is either pr=
ovided by the client (PUTFH,<o:p></o:p></pre><pre>&nbsp;&nbsp; PUTPUBFH, PU=
TROOTFH) or generated as a result of a name to filehandle<o:p></o:p></pre><=
pre>&nbsp;&nbsp; translation (LOOKUP and OPEN).<o:p></o:p></pre><p class=3D=
MsoNormal>Aren't the PUTxxx filehandles supplied by the server?<o:p></o:p><=
/p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=
=3DMsoNormal>The filehandles are provided by the server, but the operations=
 are provided by the client.<o:p></o:p></p></div><div><p class=3DMsoNormal>=
<o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div=
><p class=3DMsoNormal><br>s15.38.4:&nbsp; Does all the discussion of writin=
g to stable storage apply when writing to a named attribute?<o:p></o:p></p>=
</div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3D=
MsoNormal>yes.<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p>=
</p><div><p class=3DMsoNormal><br>s15.38.5, para next to next to last:<br><=
br><o:p></o:p></p><pre>&nbsp;&nbsp; Some implementations may return NFS4ERR=
_NOSPC instead of<o:p></o:p></pre><pre>&nbsp;&nbsp; NFS4ERR_DQUOT when a us=
er's quota is exceeded.&nbsp; In the case that the<o:p></o:p></pre><pre>&nb=
sp;&nbsp; current filehandle is a directory, the server will return<o:p></o=
:p></pre><pre>&nbsp; &nbsp;NFS4ERR_ISDIR.&nbsp; If the current filehandle i=
s not a regular file or a<o:p></o:p></pre><pre>&nbsp;&nbsp; directory, the =
server will return NFS4ERR_INVAL.<o:p></o:p></pre><p class=3DMsoNormal>&nbs=
p;I am not sure what circumstances the last sentence is referring to.&nbsp;=
 One interpretation would be that WRITE is not allowed at all for special f=
iles.&nbsp; I guess this is not what is intended - please clarify.<o:p></o:=
p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p cl=
ass=3DMsoNormal>named attribute?<o:p></o:p></p></div><div><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p>=
<div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br><br><br><o:p><=
/o:p></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div>=
</body></html>=

--_000_5DEA8DB993B81040A21CF3CB332489F607B5AAD7D7MX31Acorpemcc_--

From ron.even.tlv@gmail.com  Wed Aug 21 06:29:35 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F23011E8396; Wed, 21 Aug 2013 06:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iNaQLPa3imcn; Wed, 21 Aug 2013 06:29:34 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id C32F111E80DE; Wed, 21 Aug 2013 06:29:33 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id n12so408877wgh.24 for <multiple recipients>; Wed, 21 Aug 2013 06:29:32 -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 :thread-index:content-language; bh=h7MnCGGYN6vapeaS4e4bugFkN5rC80oWOpaLWkXN998=; b=VNObMlPgE+sV/CST+4Cezae8PkyhcjbzZ8K3uR2WvghQpQDUjtlN0G/F6CMQY3brzC ufxGObtt29GO7EEpl0u++uko2mZKnsGolFzAjwpeQKkSjl4JPJWvoe9476k0olKabByh jCexvvyrg3+iKdTbW5kVpwi3NG/sAKxb7KZrAZo6fjFHPPc7Fm8yrjcbHbis1BYeD+nq sAkSUkwhg2jEyhy+f3uulPVco2ujGgM3ubMA9vdWqUHbJBS5igpTMSt16vCHdQtgywAs o0fvjMQvEhpyDWbrFyyljqqJJpNg/wA/jPRbzsBFssjsEi9wuOQGY4oDKXvu/6jby90D Xtlw==
X-Received: by 10.180.109.10 with SMTP id ho10mr16607757wib.14.1377091772810;  Wed, 21 Aug 2013 06:29:32 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id dt17sm31148295wic.1.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 21 Aug 2013 06:29:32 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-repute-model.all@tools.ietf.org>
Date: Wed, 21 Aug 2013 16:27:03 +0300
Message-ID: <02be01ce9e72$25ac43f0$7104cbd0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02BF_01CE9E8B.4AFA1830"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6ech93EjPEiJ4iR5m11MTCM0qVkg==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-repute-model-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 13:29:35 -0000

This is a multipart message in MIME format.

------=_NextPart_000_02BF_01CE9E8B.4AFA1830
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-repute-model-07

Reviewer: Roni Even

Review Date:2013-8-20

IETF LC End Date: 2013-8-29

IESG Telechat date: 

 

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

 

 

Major issues:

Minor issues:

I was wondering why the "Further Discussion" section 9.3 is part of the
security section. I think it should be a separate section.

Nits/editorial comments:

Section 3 the end of 2nd paragraph "mechansisms" to "mechanisms"

 

 


------=_NextPart_000_02BF_01CE9E8B.4AFA1830
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-repute-model-07</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;8&#8211;20<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-8&#8211;29<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Major issues:<o:p></o:p></p><p =
class=3DMsoNormal>Minor issues:<o:p></o:p></p><p class=3DMsoNormal>I was =
wondering why the &#8220;Further Discussion&#8221; section 9.3 is part =
of the security section. I think it should be a separate =
section.<o:p></o:p></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p class=3DMsoNormal>Section 3 the end of =
2<sup>nd</sup> paragraph &#8220;mechansisms&#8221; to =
&#8220;mechanisms&#8221;<span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><a =
name=3Dpolicy.abstract></a><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_02BF_01CE9E8B.4AFA1830--


From dromasca@avaya.com  Wed Aug 21 10:27:06 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F7011E8262 for <gen-art@ietfa.amsl.com>; Wed, 21 Aug 2013 10:26:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.799
X-Spam-Level: 
X-Spam-Status: No, score=-101.799 tagged_above=-999 required=5 tests=[AWL=-1.500, 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 LSjphdzsl8-Y for <gen-art@ietfa.amsl.com>; Wed, 21 Aug 2013 10:26:43 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 65CD511E8234 for <gen-art@ietf.org>; Wed, 21 Aug 2013 10:26:31 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoULALb3FFKHCzI1/2dsb2JhbABagmQhNVGrM5QxgR8WbQeCJgEBAxIoMQ4SARUHDhRCJgEEDg0TB4duAQuYa5UekCQxgyJ5A5kQhSGLCYMdgis
X-IronPort-AV: E=Sophos;i="4.89,929,1367985600"; d="scan'208";a="24967685"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 21 Aug 2013 13:26:29 -0400
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 21 Aug 2013 13:19:13 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0146.000; Wed, 21 Aug 2013 19:26:28 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-kaplan-insipid-session-id-03.txt
Thread-Index: Ac6ek5GZKwzOmypGSHuK9xUqfDsYrw==
Date: Wed, 21 Aug 2013 17:26:28 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA128B4D41@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-kaplan-insipid-session-id.all@tools.ietf.org" <draft-kaplan-insipid-session-id.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-kaplan-insipid-session-id-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 17:27:10 -0000

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document: draft-kaplan-insipid-session-id-03.txt
Reviewer: Dan Romascanu
Review Date: 8/21
IETF LC End Date: 8/30
IESG Telechat date:=20

Summary:
Ready with Issues

Major issues:

1. In similar situations when IETF WGs decided to document proprietary solu=
tions that were used as a basis for standards-track RFCs Historic RFCs were=
 issued rather than Informational RFCs. See for example RFC 5412, 5413, 541=
4 which documented the prior art that was used to create RFC 5415. Publicat=
ion of these documents was also withhold until the standards-track RFC was =
published. None of these precedents is followed here. One of the reasons fo=
r the WG to prefer Informational rather than Historic is the fact that the =
registration of a new SIP header field is required from IANA, and in confor=
mance with RFC 5727 this can be done in an Informational RFC, but not in a =
Historic one. What is missing however is clear text that the solution descr=
ibed in this document is a legacy solution and that the solution going forw=
ard is the one that is being defined by the INSIPID WG. The IESG should als=
o consider whether this document should be approved for publication before =
the standards-track solution defined by the INSIPID WG is also published.

2. The Abstract makes the claim that the Standards-Track RFC that will be e=
ventually produced by the INSIPID WG will be developped in a backwards-comp=
atible manner with this document. This does not seem appropriate here - if =
at all such a requirement should be included in draft-ietf-insipid-session-=
id-reqts-08.txt. However it does not appear there, and that document was re=
cently submitted for publication to the IESG, so the WG did not include it =
in its consensus.=20

Minor issues:

1. The IANA considerations sections need to be more explicit in demonstrati=
ng that the conditions for registration of extension SIP header fields in I=
nformational RFCs have been met as per RFC 5727. That RFC defines that Desi=
gnated Expert review needs to happen for such new registrations - I could n=
ot find a proof that such a review took place in the shepherd write-up. Act=
ually the question about the expert reviews is not answered directly, inste=
ad of an answer wide deployment is mentioned, but that deployment could not=
 use this SIP header field which was not yet approved. According to RFC 572=
7 there are two basic conditions that need to be verified by the Designated=
 Expert - that the proposed header field must be of a purely informational =
nature and must not significantly change the behavior of SIP entities that =
support it, and that the proposed header field must not undermine SIP secur=
ity in any sense, and that the Informational RFC defining the header field =
must address security issues in detail, as if it were a standards-track doc=
ument. I believe that both conditions are met by the I-D, but there is no a=
dequate text in the IANA considerations section to explain this.=20

Nits/editorial comments:


Regards,

Dan



From presnick@qti.qualcomm.com  Wed Aug 21 11:48:04 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D40CC21F9C91; Wed, 21 Aug 2013 11:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.013, 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 o-IJFpPjFZaI; Wed, 21 Aug 2013 11:48:00 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 368A121F9C68; Wed, 21 Aug 2013 11:48:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377110880; x=1408646880; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=/bM+OhFCHv4uJLxCYp43sF7LwG5vfn1T7lUXXZYTsq0=; b=tBFgKUAirtgN2o0J6JfkdpZJxx36ioSpHZDVVDtYIi0OxivwbgMjILif AqzjieRyOGDW+asKkqSAYYJTi5pk6zpkv7UPy8AvOdGl/TevVtmgLWglK mf/pQkNV1DmDoGClAg8NLuE0If/9q6uLOOpE1PXEPPJfIu8DrFuYrSAy9 Q=;
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="50045704"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth02.qualcomm.com with ESMTP; 21 Aug 2013 11:47:57 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="524707818"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Aug 2013 11:47:57 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.146.2; Wed, 21 Aug 2013 11:47:57 -0700
Message-ID: <52150B5A.1060503@qti.qualcomm.com>
Date: Wed, 21 Aug 2013 13:47:54 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
References: <02be01ce9e72$25ac43f0$7104cbd0$@gmail.com>
In-Reply-To: <02be01ce9e72$25ac43f0$7104cbd0$@gmail.com>
Content-Type: multipart/alternative; boundary="------------050508060307080700060401"
X-Originating-IP: [172.30.39.5]
Cc: draft-ietf-repute-model.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-repute-model-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 18:48:05 -0000

--------------050508060307080700060401
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

As per a suggestion in another thread: Would you also say that this 
draft is ready for publication as a Proposed Standard? This is more 
architectural overview than protocol per-se, but I do think it is 
necessary to the understanding of the other protocol documents (hence it 
is a normative reference), and I think it can progress with the rest.

(I haven't seen an objection to doing so in the other Last Call thread, 
so unless there is a good reason not to, I'm inclined to re-initiate the 
Last Call for Proposed Standard instead.)

pr

On 8/21/13 8:27 AM, Roni Even 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-repute-model-07
>
> Reviewer: Roni Even
>
> Review Date:2013--8--20
>
> IETF LC End Date: 2013-8--29
>
> IESG Telechat date:
>
> Summary: This draft is ready for publication as an Informational RFC.
>
> Major issues:
>
> Minor issues:
>
> I was wondering why the "Further Discussion" section 9.3 is part of 
> the security section. I think it should be a separate section.
>
> Nits/editorial comments:
>
> Section 3 the end of 2^nd paragraph "mechansisms" to "mechanisms"
>

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
As per a suggestion in another thread: Would you also say that this
draft is ready for publication as a Proposed Standard? This is more
architectural overview than protocol per-se, but I do think it is
necessary to the understanding of the other protocol documents (hence
it is a normative reference), and I think it can progress with the rest.<br>
<br>
(I haven't seen an objection to doing so in the other Last Call thread,
so unless there is a good reason not to, I'm inclined to re-initiate
the Last Call for Proposed Standard instead.)<br>
<br>
pr<br>
<br>
On 8/21/13 8:27 AM, Roni Even wrote:
<blockquote cite="mid:02be01ce9e72$25ac43f0$7104cbd0$@gmail.com"
 type="cite">
  <meta http-equiv="Content-Type"
 content="text/html; charset=ISO-8859-1">
  <meta name="Generator" content="Microsoft Word 14 (filtered medium)">
  <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
  <div class="WordSection1">
  <p class="MsoNormal"><a moz-do-not-send="true" name="OLE_LINK1"></a><a
 moz-do-not-send="true" name="OLE_LINK2">I am the assigned Gen-ART
reviewer for this draft. For background on Gen-ART, please see the FAQ
at &lt;</a><a moz-do-not-send="true"
 href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
 target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
  <p class="MsoNormal">Please resolve these comments along with any
other Last Call comments you may receive.<o:p></o:p></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">Document:
  </span><span style="font-family: &quot;Courier New&quot;;">draft-ietf-repute-model-07</span><o:p></o:p></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">Reviewer:
Roni Even<o:p></o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">Review
Date:2013&#8211;8&#8211;20<o:p></o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">IETF LC
End Date: 2013-8&#8211;29<o:p></o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">IESG
Telechat date: <o:p></o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><o:p>&nbsp;</o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">Summary:
This draft is ready for publication as an Informational RFC</span><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">.<o:p></o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><o:p>&nbsp;</o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><o:p>&nbsp;</o:p></span></p>
  <p class="MsoNormal">Major issues:<o:p></o:p></p>
  <p class="MsoNormal">Minor issues:<o:p></o:p></p>
  <p class="MsoNormal">I was wondering why the &#8220;Further Discussion&#8221;
section 9.3 is part of the security section. I think it should be a
separate section.<o:p></o:p></p>
  <p class="MsoNormal">Nits/editorial comments:<o:p></o:p></p>
  <p class="MsoNormal">Section 3 the end of 2<sup>nd</sup> paragraph
&#8220;mechansisms&#8221; to &#8220;mechanisms&#8221;<span style="color: black;"><o:p></o:p></span></p>
  <p class="MsoNormal"><a moz-do-not-send="true" name="policy.abstract"></a><o:p>&nbsp;</o:p></p>
  <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
  </div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Pete Resnick <a class="moz-txt-link-rfc2396E" href="http://www.qualcomm.com/~presnick/">&lt;http://www.qualcomm.com/~presnick/&gt;</a>
Qualcomm Technologies, Inc. - +1 (858)651-4478</pre>
</body>
</html>

--------------050508060307080700060401--

From rjsparks@nostrum.com  Thu Aug 22 10:08:33 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 276BD21F9C82; Thu, 22 Aug 2013 10:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.45
X-Spam-Level: 
X-Spam-Status: No, score=-101.45 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_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 B-rRvRJ5r3lS; Thu, 22 Aug 2013 10:08:32 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 69EEB21F9F3D; Thu, 22 Aug 2013 10:08:29 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7MH8QW9078421 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Thu, 22 Aug 2013 12:08:26 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <5216458A.5040608@nostrum.com>
Date: Thu, 22 Aug 2013 12:08:26 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA128B4D41@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA128B4D41@AZ-FFEXMB04.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-kaplan-insipid-session-id.all@tools.ietf.org" <draft-kaplan-insipid-session-id.all@tools.ietf.org>, "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-kaplan-insipid-session-id-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 17:08:33 -0000

Adding the working group.

Dan - thanks for this review. I've been working towards trying to=20
express a concern, and this really helped clarify what was bothering me.

This document, AFAIK, _is not_ actually trying to register the=20
Session-ID header with IANA, even though there is a section that looks=20
like it does.

Rather, that registration is in=20
http://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/

That is a very good example of how just adding the explanatory paragraph =

at the beginning of the document isn't enough to turn this into=20
something that documents an earlier path considered and implementation=20
that exists current deployments - the text needs to be touched in=20
several places to make it clear that's what the document is doing.  In=20
the IANA considerations case, one possible adjustment is to change the=20
text to "here's what known implementations have used for syntax. See=20
[draft-ietf-insipid-session-id] for the intended registered syntax", and =

not issue instructions to IANA.

It's more work for Hadriel, but I think it's necessary.

RjS


On 8/21/13 12:26 PM, Romascanu, Dan (Dan) wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on Ge=
n-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 y=
ou may receive.
>
> Document: draft-kaplan-insipid-session-id-03.txt
> Reviewer: Dan Romascanu
> Review Date: 8/21
> IETF LC End Date: 8/30
> IESG Telechat date:
>
> Summary:
> Ready with Issues
>
> Major issues:
>
> 1. In similar situations when IETF WGs decided to document proprietary =
solutions that were used as a basis for standards-track RFCs Historic RFC=
s were issued rather than Informational RFCs. See for example RFC 5412, 5=
413, 5414 which documented the prior art that was used to create RFC 5415=
=2E Publication of these documents was also withhold until the standards-=
track RFC was published. None of these precedents is followed here. One o=
f the reasons for the WG to prefer Informational rather than Historic is =
the fact that the registration of a new SIP header field is required from=
 IANA, and in conformance with RFC 5727 this can be done in an Informatio=
nal RFC, but not in a Historic one. What is missing however is clear text=
 that the solution described in this document is a legacy solution and th=
at the solution going forward is the one that is being defined by the INS=
IPID WG. The IESG should also consider whether this document should be ap=
proved for publication before the standards-t
>   rack solution defined by the INSIPID WG is also published.
>
> 2. The Abstract makes the claim that the Standards-Track RFC that will =
be eventually produced by the INSIPID WG will be developped in a backward=
s-compatible manner with this document. This does not seem appropriate he=
re - if at all such a requirement should be included in draft-ietf-insipi=
d-session-id-reqts-08.txt. However it does not appear there, and that doc=
ument was recently submitted for publication to the IESG, so the WG did n=
ot include it in its consensus.
>
> Minor issues:
>
> 1. The IANA considerations sections need to be more explicit in demonst=
rating that the conditions for registration of extension SIP header field=
s in Informational RFCs have been met as per RFC 5727. That RFC defines t=
hat Designated Expert review needs to happen for such new registrations -=
 I could not find a proof that such a review took place in the shepherd w=
rite-up. Actually the question about the expert reviews is not answered d=
irectly, instead of an answer wide deployment is mentioned, but that depl=
oyment could not use this SIP header field which was not yet approved. Ac=
cording to RFC 5727 there are two basic conditions that need to be verifi=
ed by the Designated Expert - that the proposed header field must be of a=
 purely informational nature and must not significantly change the behavi=
or of SIP entities that support it, and that the proposed header field mu=
st not undermine SIP security in any sense, and that the Informational RF=
C defining the header field must address se
>   curity issues in detail, as if it were a standards-track document. I =
believe that both conditions are met by the I-D, but there is no adequate=
 text in the IANA considerations section to explain this.
>
> Nits/editorial comments:
>
>
> Regards,
>
> Dan
>
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art



From gsalguei@cisco.com  Thu Aug 22 10:30:54 2013
Return-Path: <gsalguei@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 2864221F9E89 for <gen-art@ietfa.amsl.com>; Thu, 22 Aug 2013 10:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.329
X-Spam-Level: 
X-Spam-Status: No, score=-9.329 tagged_above=-999 required=5 tests=[AWL=-1.030, BAYES_00=-2.599, MANGLED_SAVELE=2.3, 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 AyyUYFShw5TN for <gen-art@ietfa.amsl.com>; Thu, 22 Aug 2013 10:30:50 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 590AD21F9E62 for <gen-art@ietf.org>; Thu, 22 Aug 2013 10:30:49 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r7MHUkjB024201 for <gen-art@ietf.org>; Thu, 22 Aug 2013 19:30:46 +0200 (CEST)
Received: from rtp-gsalguei-8917.cisco.com (rtp-gsalguei-8917.cisco.com [10.116.132.56]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r7MHUhOJ024627; Thu, 22 Aug 2013 13:30:45 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <5216458A.5040608@nostrum.com>
Date: Thu, 22 Aug 2013 13:30:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <45C07F42-21DD-45BF-B9F4-CCFC01B022FB@cisco.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA128B4D41@AZ-FFEXMB04.global.avaya.com> <5216458A.5040608@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-kaplan-insipid-session-id.all@tools.ietf.org, insipid@ietf.org
Subject: Re: [Gen-art] [Insipid] Gen-ART review of	draft-kaplan-insipid-session-id-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 17:30:54 -0000

On Aug 22, 2013, at 1:08 PM, Robert Sparks <rjsparks@nostrum.com>
 wrote:

> Adding the working group.
>=20
> Dan - thanks for this review. I've been working towards trying to =
express a concern, and this really helped clarify what was bothering me.
>=20
> This document, AFAIK, _is not_ actually trying to register the =
Session-ID header with IANA, even though there is a section that looks =
like it does.
>=20
> Rather, that registration is in =
http://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/
>=20
> That is a very good example of how just adding the explanatory =
paragraph at the beginning of the document isn't enough to turn this =
into something that documents an earlier path considered and =
implementation that exists current deployments - the text needs to be =
touched in several places to make it clear that's what the document is =
doing.  In the IANA considerations case, one possible adjustment is to =
change the text to "here's what known implementations have used for =
syntax. See [draft-ietf-insipid-session-id] for the intended registered =
syntax", and not issue instructions to IANA.

During the shepherd write-up I made a similar same comment.  I think the =
right thing to do is to write explanatory text detailing that this =
document is in fact not registering anything because all relevant IANA =
registrations are deferred to the active WG document defining the new =
session id (draft-ietf-insipid-session-id).  It should also explain that =
documeny has the responsibility to assure backwards compatibility with =
this document.

--G

>=20
> It's more work for Hadriel, but I think it's necessary.
>=20
> RjS
>=20
>=20
> On 8/21/13 12:26 PM, Romascanu, Dan (Dan) wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at
>>=20
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments =
you may receive.
>>=20
>> Document: draft-kaplan-insipid-session-id-03.txt
>> Reviewer: Dan Romascanu
>> Review Date: 8/21
>> IETF LC End Date: 8/30
>> IESG Telechat date:
>>=20
>> Summary:
>> Ready with Issues
>>=20
>> Major issues:
>>=20
>> 1. In similar situations when IETF WGs decided to document =
proprietary solutions that were used as a basis for standards-track RFCs =
Historic RFCs were issued rather than Informational RFCs. See for =
example RFC 5412, 5413, 5414 which documented the prior art that was =
used to create RFC 5415. Publication of these documents was also =
withhold until the standards-track RFC was published. None of these =
precedents is followed here. One of the reasons for the WG to prefer =
Informational rather than Historic is the fact that the registration of =
a new SIP header field is required from IANA, and in conformance with =
RFC 5727 this can be done in an Informational RFC, but not in a Historic =
one. What is missing however is clear text that the solution described =
in this document is a legacy solution and that the solution going =
forward is the one that is being defined by the INSIPID WG. The IESG =
should also consider whether this document should be approved for =
publication before the standards
> -t
>>  rack solution defined by the INSIPID WG is also published.
>>=20
>> 2. The Abstract makes the claim that the Standards-Track RFC that =
will be eventually produced by the INSIPID WG will be developped in a =
backwards-compatible manner with this document. This does not seem =
appropriate here - if at all such a requirement should be included in =
draft-ietf-insipid-session-id-reqts-08.txt. However it does not appear =
there, and that document was recently submitted for publication to the =
IESG, so the WG did not include it in its consensus.
>>=20
>> Minor issues:
>>=20
>> 1. The IANA considerations sections need to be more explicit in =
demonstrating that the conditions for registration of extension SIP =
header fields in Informational RFCs have been met as per RFC 5727. That =
RFC defines that Designated Expert review needs to happen for such new =
registrations - I could not find a proof that such a review took place =
in the shepherd write-up. Actually the question about the expert reviews =
is not answered directly, instead of an answer wide deployment is =
mentioned, but that deployment could not use this SIP header field which =
was not yet approved. According to RFC 5727 there are two basic =
conditions that need to be verified by the Designated Expert - that the =
proposed header field must be of a purely informational nature and must =
not significantly change the behavior of SIP entities that support it, =
and that the proposed header field must not undermine SIP security in =
any sense, and that the Informational RFC defining the header field must =
address=20
> se
>>  curity issues in detail, as if it were a standards-track document. I =
believe that both conditions are met by the I-D, but there is no =
adequate text in the IANA considerations section to explain this.
>>=20
>> Nits/editorial comments:
>>=20
>>=20
>> Regards,
>>=20
>> Dan
>>=20
>>=20
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20
>=20
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>=20


From rjsparks@nostrum.com  Thu Aug 22 11:05:31 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7485211E8100; Thu, 22 Aug 2013 11:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.216
X-Spam-Level: 
X-Spam-Status: No, score=-102.216 tagged_above=-999 required=5 tests=[AWL=0.383, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nz5Ivs39-Mia; Thu, 22 Aug 2013 11:05:30 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 236FD21F9E7E; Thu, 22 Aug 2013 11:05:29 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7MI5KIL084756 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Thu, 22 Aug 2013 13:05:22 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <521652E0.8030300@nostrum.com>
Date: Thu, 22 Aug 2013 13:05:20 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, netext@ietf.org, draft-ietf-netext-update-notifications@tools.ietf.org
Content-Type: multipart/alternative; boundary="------------040800040901010008090007"
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] Gen-ART LC review: draft-ietf-netext-update-notifications-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 18:05:31 -0000

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document: draft-ietf-netext-update-notifications-07
Reviewer: Robert Sparks
Review Date: 2013-08-22
IETF LC End Date: 2013-08-29
IESG Telechat date: not scheduled

Summary: This draft is ready for publication as Proposed Standard

I had to read through this text several times to convince myself 
implementers could figure out what order they were required to take 
steps in vs where they had flexibility:

    o  Upon accepting the Update Notification message, the mobile access
       gateway MUST process the message and perform the actions based on
       the Notification Reason.
       *  If the (A) flag in the message is set to a value of (1), the
          mobile access gateway MUST first send an Update Notification
          Acknowledgement message and set the status code field according
          to the result of processing the Update Notification message.

In particular, it's not immediately obvious if there is tension between 
that "MUST first" and having "the result of processing" available.
Please consider rewording to make it clearer that this "result of 
processing" is not intended to include waiting for the result of some 
action processing this notification message might trigger.

It might help readers understand the intended usual case retransmission 
mechanics if the expected default values listed in section 7 were called 
out earlier in the document.

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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I&nbsp;am&nbsp;the&nbsp;assigned&nbsp;Gen-ART&nbsp;reviewer&nbsp;for&nbsp;this&nbsp;draft.&nbsp;For&nbsp;background&nbsp;on
    <br>
    Gen-ART,&nbsp;please&nbsp;see&nbsp;the&nbsp;FAQ&nbsp;at
    <br>
    <br>
    <a class="moz-txt-link-rfc2396E"
      href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>.
    <br>
    <br>
Please&nbsp;resolve&nbsp;these&nbsp;comments&nbsp;along&nbsp;with&nbsp;any&nbsp;other&nbsp;Last&nbsp;Call&nbsp;comments
    <br>
    you&nbsp;may&nbsp;receive.
    <br>
    <br>
    Document: draft-ietf-netext-update-notifications-07<br>
    Reviewer:&nbsp;Robert&nbsp;Sparks
    <br>
    Review&nbsp;Date:&nbsp;2013-08-22<br>
    IETF&nbsp;LC&nbsp;End&nbsp;Date:&nbsp;2013-08-29<br>
    IESG&nbsp;Telechat&nbsp;date: not scheduled<br>
    <br>
    Summary: This draft is ready for publication as Proposed Standard<br>
    <br>
    I had to read through this text several times to convince myself
    implementers could figure out what order they were required to take
    steps in vs where they had flexibility:<br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre>   o  Upon accepting the Update Notification message, the mobile access
      gateway MUST process the message and perform the actions based on
      the Notification Reason.
      *  If the (A) flag in the message is set to a value of (1), the
         mobile access gateway MUST first send an Update Notification
         Acknowledgement message and set the status code field according
         to the result of processing the Update Notification message.

</pre>
    In particular, it's not immediately obvious if there is tension
    between that "MUST first" and having "the result of processing"
    available.<br>
    Please consider rewording to make it clearer that this "result of
    processing" is not intended to include waiting for the result of
    some action processing this notification message might trigger.<br>
    <br>
    It might help readers understand the intended usual case
    retransmission mechanics if the expected default values listed in
    section 7 were called out earlier in the document.<br>
  </body>
</html>

--------------040800040901010008090007--

From emcmurry@computer.org  Thu Aug 22 12:05:51 2013
Return-Path: <emcmurry@computer.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 156D711E81FA; Thu, 22 Aug 2013 12:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ev-m0gFe5sN; Thu, 22 Aug 2013 12:05:45 -0700 (PDT)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id 4204621F9F98; Thu, 22 Aug 2013 12:05:45 -0700 (PDT)
Received: from cpe-76-184-161-215.tx.res.rr.com ([76.184.161.215] helo=antikythera.casamcmurry.com) by mho-02-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from <emcmurry@computer.org>) id 1VCaCR-000GZK-Ol; Thu, 22 Aug 2013 19:05:39 +0000
Received: from localhost (localhost [127.0.0.1]) by antikythera.casamcmurry.com (Postfix) with ESMTP id 039731349AE7; Thu, 22 Aug 2013 14:05:38 -0500 (CDT)
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 76.184.161.215
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+MrAzNsRukkmVX47ydeww6zOUrVBG7aRA=
X-Virus-Scanned: amavisd-new at casamcmurry.com
Received: from antikythera.casamcmurry.com ([127.0.0.1]) by localhost (antikythera.casamcmurry.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmEzOiU_Y3lK; Thu, 22 Aug 2013 14:05:37 -0500 (CDT)
Received: from ericlaptop.casamcmurry.com (ericlaptop.casamcmurry.com [192.168.111.91]) by antikythera.casamcmurry.com (Postfix) with ESMTPSA id 9494D1349AD9;  Thu, 22 Aug 2013 14:05:37 -0500 (CDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Eric McMurry <emcmurry@computer.org>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C489319@MX15A.corp.emc.com>
Date: Thu, 22 Aug 2013 14:05:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <AEC7E92F-7370-4D76-B0DF-E9738FABCB86@computer.org>
References: <8D3D17ACE214DC429325B2B98F3AE7129C489319@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Thu, 22 Aug 2013 12:18:03 -0700
Cc: "bclaise@cisco.com" <bclaise@cisco.com>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dime-overload-reqs-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, 22 Aug 2013 19:05:52 -0000

Hi David,

Thank you for the review.  Your time and comments are appreciated!

comments/questions inline.


Eric



On Aug 17, 2013, at 9:18 , "Black, David" <david.black@emc.com> wrote:

>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-dime-overload-reqs-10
> Reviewer: David L. Black
> Review Date: August 17, 2013
> IETF LC End Date: August 16, 2013
> IESG Telechat date: (if known)
>=20
> Summary:
> This draft is basically ready for publication, but has nits that =
should be
> fixed before publication.
>=20
> This draft describes scenarios in which Diameter overload can occur =
and provides
> requirements for development of new overload control functionality in =
Diameter.
> It is well written, and the inclusion of scenarios in which overload =
can occur,
> both in terms of the relationships among types of Diameter nodes and =
actual mobile
> network experience is very helpful.
>=20
> I apologize for this review being a day late, as I've been on vacation =
for most
> of this draft's IETF Last Call period.
>=20
> Major issues: (none)
>=20
> Minor issues: (none)
>=20
> Nits/editorial comments:
>=20
> The following two comments could be minor issues, but I'm going to =
treat them
> as editorial, as I expect that they will be addressed in development =
of the
> actual overload functionality:
>=20
> a) I assume that overload control development work will derive more =
specific
> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
> The discussion in security considerations section seems reasonable.

We agree with this.  The thinking here was that we didn't want to =
specify this in a way that would be specific to a particular type of =
mechanism.  It might not hurt to state that assumption, either as a note =
on Req 27 or in the sec considerations.

>=20
> b) The draft, and especially its requirements in Section 7 are =
strongly
> focused on individual Diameter node overload.  That's necessary, but =
overload
> conditions can be broader, affecting an entire service or application, =
or
> multiple instances of either/both, even if not every individual =
Diameter node
> involved is overloaded.  A number of the requirements, starting with =
REQ 22
> could be generalized to cover broader overload conditions.
>=20
> This (b) has implications for other requirements, e.g., REQ 13 should =
also be
> generalized beyond a single node to avoid increased traffic in an =
overload
> situation, even from a node that is not overloaded by itself.  There =
are limits
> on what is reasonable here, as the desired overload functionality is =
TCP/SCTP-
> like reaction to congestion where individual actions taken by nodes =
based on
> the information they have (which is not the complete state of the =
network)
> results in an overall reduction of load.

The intent was very much as you say, where requirements on individual =
node capabilities are hoped to result in better overall system =
behaviors. There are also some requirements that are stated more at the =
system level (e.g. 7 and 17.) Also the text in section 2.2 that =
discusses Figure 5 talks about how insufficient server capacity at a =
cluster of servers behind a Diameter agent can be treated as if the =
agent itself was overloaded.

On the other hand, any mechanism we design will have to focus on actions =
of individual nodes, so the numbered requirements tend to focus on that. =
I'm not sure where to change the balance here--do you have specific =
suggestions?

>=20
> Section 1.2, 2nd paragraph:
>=20
>   as network congestion, network congestion can reduce a Diameter =
nodes
>=20
> "nodes" -> "node's"

good catch.

>=20
> Section 5, 1st paragraph:
>=20
> This inadequacy may, in turn, contribute to broader congestion =
collapse=20
>=20
> "collapse" is not the right word here - I suggest "issues", "impacts",
> "effects" or "problems".

We are fine with any of those alternatives.  How about impacts.

>=20
> Section 7
>=20
> The long enumerated list of requirements is not an easy read.  It =
would be
> better if these could somehow be grouped by functional category, e.g.,
> security, transport interactions, operational/administrative, etc.

agree.  It is actually in sections in the XML (denoted by comments), we =
just did not promote those to visible sections in the txt.  I recall =
there being some issue with xml2rfc and numbering, but now that the =
numbers are set, this would not be hard to do.

>=20
> idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - this is =
fine,
> as the boilerplate has been appropriately modified for this draft that
> expresses requirements (as opposed to a draft that specifies a =
protocol).
>=20
> idnits 2.12.17 got confused by the 3GPP and GSMA Informative =
References.
> I assume that they're all sufficiently stable to be informative =
references.
> However, [TR23.843] is a work in progress, and should be noted as such =
in
> its reference - is this needed for any of the other 3GPP or GSMA =
references?

23.843 is the least stable reference.  I don't have any issue with =
pointing that out.  The part of it we are referencing is historical =
front matter though.


I tried the web and downloaded versions of 2.12.17 and was not able to =
get the warnings you saw (about the references).  What did it say?


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


From hadriel.kaplan@oracle.com  Thu Aug 22 12:17:07 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC04F11E820A; Thu, 22 Aug 2013 12:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.369
X-Spam-Level: 
X-Spam-Status: No, score=-5.369 tagged_above=-999 required=5 tests=[AWL=-1.070, BAYES_00=-2.599, MANGLED_SAVELE=2.3, 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 sfaHwktrZbrn; Thu, 22 Aug 2013 12:16:44 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id EB31911E8203; Thu, 22 Aug 2013 12:16:43 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7MJGcjW021701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Aug 2013 19:16:39 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7MJGbqF001140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Aug 2013 19:16:37 GMT
Received: from abhmt111.oracle.com (abhmt111.oracle.com [141.146.116.63]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7MJGaov019607; Thu, 22 Aug 2013 19:16:36 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 22 Aug 2013 12:16:36 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <5216458A.5040608@nostrum.com>
Date: Thu, 22 Aug 2013 15:16:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AEEDE5E6-54CE-4557-B03B-4341B00F3EC3@oracle.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA128B4D41@AZ-FFEXMB04.global.avaya.com> <5216458A.5040608@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
X-Mailman-Approved-At: Thu, 22 Aug 2013 12:18:03 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-kaplan-insipid-session-id.all@tools.ietf.org" <draft-kaplan-insipid-session-id.all@tools.ietf.org>, "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-kaplan-insipid-session-id-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 19:17:08 -0000

Actually I consciously left the IANA section as registering the header, =
and it was not an oversight.

For background: I did not submit the draft as Informational originally =
in version-00 - I submitted it as Historic, and was asked by the =
shepherding AD to change it to Informational later, based on IESG =
feedback (I think; I could be wrong about it being from IESG feedback).

Once it became Informational, we (myself, the AD, and the WG chairs) did =
actually discuss whether it would register the header in IANA or not.  =
My understanding was that this Informational draft *would* in fact =
register the new header in IANA.  Technically there's nothing wrong with =
that, afaik, other than I do need to get Designated Expert review as Dan =
correctly pointed out.

We discussed that once the WG draft-ietf-insipid-session-id is =
published, it would then update IANA's entry for the header to point to =
the new WG RFC.  Whether the WG draft-ietf-insipid-session-id text needs =
to change to make that clear or not, or change to extend the =
already-registered header or not, etc., is of course also still =
change-able.

If the WG draft-ietf-insipid-session-id fundamentally changes the =
'Session-ID' header from what it is in draft-kaplan-insipid-session-id, =
in a non-backwards-compatible fashion, then it won't have met the =
agreement reached in IETF 85 for adopting =
draft-jones-insipid-session-id-0 as the new WG document solution.  If we =
decide that's ok, then I think it actually needs to register a new =
header name regardless.  We know 'Session-ID' is already in-use in the =
wild, and there are plenty of more strings available for header names.

-hadriel
=20

On Aug 22, 2013, at 1:08 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

> Adding the working group.
>=20
> Dan - thanks for this review. I've been working towards trying to =
express a concern, and this really helped clarify what was bothering me.
>=20
> This document, AFAIK, _is not_ actually trying to register the =
Session-ID header with IANA, even though there is a section that looks =
like it does.
>=20
> Rather, that registration is in =
http://datatracker.ietf.org/doc/draft-ietf-insipid-session-id/
>=20
> That is a very good example of how just adding the explanatory =
paragraph at the beginning of the document isn't enough to turn this =
into something that documents an earlier path considered and =
implementation that exists current deployments - the text needs to be =
touched in several places to make it clear that's what the document is =
doing.  In the IANA considerations case, one possible adjustment is to =
change the text to "here's what known implementations have used for =
syntax. See [draft-ietf-insipid-session-id] for the intended registered =
syntax", and not issue instructions to IANA.
>=20
> It's more work for Hadriel, but I think it's necessary.
>=20
> RjS
>=20
>=20
> On 8/21/13 12:26 PM, Romascanu, Dan (Dan) wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at
>>=20
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments =
you may receive.
>>=20
>> Document: draft-kaplan-insipid-session-id-03.txt
>> Reviewer: Dan Romascanu
>> Review Date: 8/21
>> IETF LC End Date: 8/30
>> IESG Telechat date:
>>=20
>> Summary:
>> Ready with Issues
>>=20
>> Major issues:
>>=20
>> 1. In similar situations when IETF WGs decided to document =
proprietary solutions that were used as a basis for standards-track RFCs =
Historic RFCs were issued rather than Informational RFCs. See for =
example RFC 5412, 5413, 5414 which documented the prior art that was =
used to create RFC 5415. Publication of these documents was also =
withhold until the standards-track RFC was published. None of these =
precedents is followed here. One of the reasons for the WG to prefer =
Informational rather than Historic is the fact that the registration of =
a new SIP header field is required from IANA, and in conformance with =
RFC 5727 this can be done in an Informational RFC, but not in a Historic =
one. What is missing however is clear text that the solution described =
in this document is a legacy solution and that the solution going =
forward is the one that is being defined by the INSIPID WG. The IESG =
should also consider whether this document should be approved for =
publication before the standards-t
>>  rack solution defined by the INSIPID WG is also published.
>>=20
>> 2. The Abstract makes the claim that the Standards-Track RFC that =
will be eventually produced by the INSIPID WG will be developped in a =
backwards-compatible manner with this document. This does not seem =
appropriate here - if at all such a requirement should be included in =
draft-ietf-insipid-session-id-reqts-08.txt. However it does not appear =
there, and that document was recently submitted for publication to the =
IESG, so the WG did not include it in its consensus.
>>=20
>> Minor issues:
>>=20
>> 1. The IANA considerations sections need to be more explicit in =
demonstrating that the conditions for registration of extension SIP =
header fields in Informational RFCs have been met as per RFC 5727. That =
RFC defines that Designated Expert review needs to happen for such new =
registrations - I could not find a proof that such a review took place =
in the shepherd write-up. Actually the question about the expert reviews =
is not answered directly, instead of an answer wide deployment is =
mentioned, but that deployment could not use this SIP header field which =
was not yet approved. According to RFC 5727 there are two basic =
conditions that need to be verified by the Designated Expert - that the =
proposed header field must be of a purely informational nature and must =
not significantly change the behavior of SIP entities that support it, =
and that the proposed header field must not undermine SIP security in =
any sense, and that the Informational RFC defining the header field must =
address se
>>  curity issues in detail, as if it were a standards-track document. I =
believe that both conditions are met by the I-D, but there is no =
adequate text in the IANA considerations section to explain this.
>>=20
>> Nits/editorial comments:
>>=20
>>=20
>> Regards,
>>=20
>> Dan
>>=20
>>=20
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20
>=20


From david.black@emc.com  Thu Aug 22 12:51:07 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83EAA11E811E; Thu, 22 Aug 2013 12:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.425
X-Spam-Level: 
X-Spam-Status: No, score=-102.425 tagged_above=-999 required=5 tests=[AWL=-0.054, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 IVOVbWK7J3D8; Thu, 22 Aug 2013 12:51:03 -0700 (PDT)
Received: from mexforward.lss.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id EB34F11E8117; Thu, 22 Aug 2013 12:51:02 -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 r7MJocLW001146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Aug 2013 15:50:39 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 22 Aug 2013 15:50:28 -0400
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7MJoBsN001185; Thu, 22 Aug 2013 15:50:20 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub18.corp.emc.com ([10.254.93.47]) with mapi; Thu, 22 Aug 2013 15:50:12 -0400
From: "Black, David" <david.black@emc.com>
To: Eric McMurry <emcmurry@computer.org>
Date: Thu, 22 Aug 2013 15:50:10 -0400
Thread-Topic: Gen-ART review of draft-ietf-dime-overload-reqs-10
Thread-Index: Ac6faozXVsVQVwMSQy+X8V1n0OAyZAAA9Z1g
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C489C55@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C489319@MX15A.corp.emc.com> <AEC7E92F-7370-4D76-B0DF-E9738FABCB86@computer.org>
In-Reply-To: <AEC7E92F-7370-4D76-B0DF-E9738FABCB86@computer.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "bclaise@cisco.com" <bclaise@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dime-overload-reqs-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, 22 Aug 2013 19:51:07 -0000

Hi Eric,

This looks good - comments follow ...

> > a) I assume that overload control development work will derive more spe=
cific
> > security requirements - e.g., as REQ 27 is stated at a rather high leve=
l.
> > The discussion in security considerations section seems reasonable.
>=20
> We agree with this.  The thinking here was that we didn't want to specify=
 this
> in a way that would be specific to a particular type of mechanism.  It mi=
ght
> not hurt to state that assumption, either as a note on Req 27 or in the s=
ec
> considerations.

That would be good to add as a note on REQ 27.

> The intent was very much as you say, where requirements on individual nod=
e
> capabilities are hoped to result in better overall system behaviors. Ther=
e are
> also some requirements that are stated more at the system level (e.g. 7 a=
nd
> 17.) Also the text in section 2.2 that discusses Figure 5 talks about how
> insufficient server capacity at a cluster of servers behind a Diameter ag=
ent
> can be treated as if the agent itself was overloaded.
>=20
> On the other hand, any mechanism we design will have to focus on actions =
of
> individual nodes, so the numbered requirements tend to focus on that. I'm=
 not
> sure where to change the balance here--do you have specific suggestions?

I noted this as editorial rather than a minor issue, as I was mostly concer=
ned
that the actual design work will be informed by a sufficient architectural =
"clue"
that the goal is "better overall system behaviors", which your response ind=
icates
will definitely be the case ;-).

Rather than edit individual requirements, how about adding the following se=
ntence
immediately following the introductory sentence in Section 7?:

	These requirements are stated primarily in terms of individual node
	behavior to inform the design of the improved mechanism;
	that design effort should keep in mind that the overall goal is
	improved overall system behavior across all the nodes involved,=20
	not just improved behavior from specific individual nodes.

> > This inadequacy may, in turn, contribute to broader congestion collapse
> >
> > "collapse" is not the right word here - I suggest "issues", "impacts",
> > "effects" or "problems".
>=20
> We are fine with any of those alternatives.  How about impacts.

That's fine.  FWIW, "congestion collapse" has a specific (rather severe)
meaning over in the Transport Area, and that meaning was not intended here.

> 23.843 is the least stable reference.  I don't have any issue with pointi=
ng
> that out.  The part of it we are referencing is historical front matter
> though.

I'd note the reference as work in progress, and put the statement about sta=
ble
front matter (historical is a bad work to use here) in the body of the draf=
t
that cites the reference.
=20
> I tried the web and downloaded versions of 2.12.17 and was not able to ge=
t the
> warnings you saw (about the references).  What did it say?

Sorry, I didn't mean to send you on a wild goose chase :-).  The idnits con=
fusion
manifested right at the top of the output, where everyone ignores it ...

   Attempted to download rfc272 state...
   Failure fetching the file, proceeding without it.

You didn't reference RFC 272, so that output's apparently courtesy of idnit=
s
misinterpreting this reference:

1195	   [TS29.272]
1196	              3GPP, "Evolved Packet System (EPS); Mobility Management
1197	              Entity (MME) and Serving GPRS Support Node (SGSN) relate=
d
1198	              interfaces based on Diameter protocol", TS 29.272 11.4.0=
,
1199	              September 2012.

I was amused :-).

Thanks,
--David

> -----Original Message-----
> From: Eric McMurry [mailto:emcmurry@computer.org]
> Sent: Thursday, August 22, 2013 3:06 PM
> To: Black, David
> Cc: ben@nostrum.com; General Area Review Team (gen-art@ietf.org);
> ietf@ietf.org; dime@ietf.org; bclaise@cisco.com
> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>=20
> Hi David,
>=20
> Thank you for the review.  Your time and comments are appreciated!
>=20
> comments/questions inline.
>=20
>=20
> Eric
>=20
>=20
>=20
> On Aug 17, 2013, at 9:18 , "Black, David" <david.black@emc.com> wrote:
>=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>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-dime-overload-reqs-10
> > Reviewer: David L. Black
> > Review Date: August 17, 2013
> > IETF LC End Date: August 16, 2013
> > IESG Telechat date: (if known)
> >
> > Summary:
> > This draft is basically ready for publication, but has nits that should=
 be
> > fixed before publication.
> >
> > This draft describes scenarios in which Diameter overload can occur and=
 provides
> > requirements for development of new overload control functionality in D=
iameter.
> > It is well written, and the inclusion of scenarios in which overload ca=
n occur,
> > both in terms of the relationships among types of Diameter nodes and ac=
tual mobile
> > network experience is very helpful.
> >
> > I apologize for this review being a day late, as I've been on vacation =
for most
> > of this draft's IETF Last Call period.
> >
> > Major issues: (none)
> >
> > Minor issues: (none)
> >
> > Nits/editorial comments:
> >
> > The following two comments could be minor issues, but I'm going to trea=
t them
> > as editorial, as I expect that they will be addressed in development of=
 the
> > actual overload functionality:
> >
> > a) I assume that overload control development work will derive more spe=
cific
> > security requirements - e.g., as REQ 27 is stated at a rather high leve=
l.
> > The discussion in security considerations section seems reasonable.
>=20
> We agree with this.  The thinking here was that we didn't want to specify=
 this
> in a way that would be specific to a particular type of mechanism.  It mi=
ght
> not hurt to state that assumption, either as a note on Req 27 or in the s=
ec
> considerations.
>=20
> >
> > b) The draft, and especially its requirements in Section 7 are strongly
> > focused on individual Diameter node overload.  That's necessary, but ov=
erload
> > conditions can be broader, affecting an entire service or application, =
or
> > multiple instances of either/both, even if not every individual Diamete=
r node
> > involved is overloaded.  A number of the requirements, starting with RE=
Q 22
> > could be generalized to cover broader overload conditions.
> >
> > This (b) has implications for other requirements, e.g., REQ 13 should a=
lso be
> > generalized beyond a single node to avoid increased traffic in an overl=
oad
> > situation, even from a node that is not overloaded by itself.  There ar=
e limits
> > on what is reasonable here, as the desired overload functionality is TC=
P/SCTP-
> > like reaction to congestion where individual actions taken by nodes bas=
ed on
> > the information they have (which is not the complete state of the netwo=
rk)
> > results in an overall reduction of load.
>=20
> The intent was very much as you say, where requirements on individual nod=
e
> capabilities are hoped to result in better overall system behaviors. Ther=
e are
> also some requirements that are stated more at the system level (e.g. 7 a=
nd
> 17.) Also the text in section 2.2 that discusses Figure 5 talks about how
> insufficient server capacity at a cluster of servers behind a Diameter ag=
ent
> can be treated as if the agent itself was overloaded.
>=20
> On the other hand, any mechanism we design will have to focus on actions =
of
> individual nodes, so the numbered requirements tend to focus on that. I'm=
 not
> sure where to change the balance here--do you have specific suggestions?
>=20
> >
> > Section 1.2, 2nd paragraph:
> >
> >   as network congestion, network congestion can reduce a Diameter nodes
> >
> > "nodes" -> "node's"
>=20
> good catch.
>=20
> >
> > Section 5, 1st paragraph:
> >
> > This inadequacy may, in turn, contribute to broader congestion collapse
> >
> > "collapse" is not the right word here - I suggest "issues", "impacts",
> > "effects" or "problems".
>=20
> We are fine with any of those alternatives.  How about impacts.
>=20
> >
> > Section 7
> >
> > The long enumerated list of requirements is not an easy read.  It would=
 be
> > better if these could somehow be grouped by functional category, e.g.,
> > security, transport interactions, operational/administrative, etc.
>=20
> agree.  It is actually in sections in the XML (denoted by comments), we j=
ust
> did not promote those to visible sections in the txt.  I recall there bei=
ng
> some issue with xml2rfc and numbering, but now that the numbers are set, =
this
> would not be hard to do.
>=20
>=20
> >
> > idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - this is =
fine,
> > as the boilerplate has been appropriately modified for this draft that
> > expresses requirements (as opposed to a draft that specifies a protocol=
).
> >
> > idnits 2.12.17 got confused by the 3GPP and GSMA Informative References=
.
> > I assume that they're all sufficiently stable to be informative referen=
ces.
> > However, [TR23.843] is a work in progress, and should be noted as such =
in
> > its reference - is this needed for any of the other 3GPP or GSMA refere=
nces?
>=20
> 23.843 is the least stable reference.  I don't have any issue with pointi=
ng
> that out.  The part of it we are referencing is historical front matter
> though.
>=20
>=20
> I tried the web and downloaded versions of 2.12.17 and was not able to ge=
t the
> warnings you saw (about the references).  What did it say?
>=20
>=20
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > david.black@emc.com        Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >
>=20


From rjsparks@nostrum.com  Thu Aug 22 13:11:24 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8E2011E8123; Thu, 22 Aug 2013 13:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.162
X-Spam-Level: 
X-Spam-Status: No, score=-101.162 tagged_above=-999 required=5 tests=[AWL=-0.862, 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 wuBTjw+XloGO; Thu, 22 Aug 2013 13:11:23 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9F41121F9FDA; Thu, 22 Aug 2013 13:11:23 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7MKBIYi098763 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Thu, 22 Aug 2013 15:11:19 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <52167066.7040605@nostrum.com>
Date: Thu, 22 Aug 2013 15:11:18 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA128B4D41@AZ-FFEXMB04.global.avaya.com> <5216458A.5040608@nostrum.com> <AEEDE5E6-54CE-4557-B03B-4341B00F3EC3@oracle.com>
In-Reply-To: <AEEDE5E6-54CE-4557-B03B-4341B00F3EC3@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-kaplan-insipid-session-id.all@tools.ietf.org" <draft-kaplan-insipid-session-id.all@tools.ietf.org>, "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-kaplan-insipid-session-id-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 20:11:24 -0000

On 8/22/13 2:16 PM, Hadriel Kaplan wrote:
> Actually I consciously left the IANA section as registering the header,=
 and it was not an oversight.
>
> For background: I did not submit the draft as Informational originally =
in version-00 - I submitted it as Historic, and was asked by the shepherd=
ing AD to change it to Informational later, based on IESG feedback (I thi=
nk; I could be wrong about it being from IESG feedback).
>
> Once it became Informational, we (myself, the AD, and the WG chairs) di=
d actually discuss whether it would register the header in IANA or not.  =
My understanding was that this Informational draft *would* in fact regist=
er the new header in IANA.  Technically there's nothing wrong with that, =
afaik, other than I do need to get Designated Expert review as Dan correc=
tly pointed out.
>
> We discussed that once the WG draft-ietf-insipid-session-id is publishe=
d, it would then update IANA's entry for the header to point to the new W=
G RFC.  Whether the WG draft-ietf-insipid-session-id text needs to change=
 to make that clear or not, or change to extend the already-registered he=
ader or not, etc., is of course also still change-able.
>
> If the WG draft-ietf-insipid-session-id fundamentally changes the 'Sess=
ion-ID' header from what it is in draft-kaplan-insipid-session-id, in a n=
on-backwards-compatible fashion, then it won't have met the agreement rea=
ched in IETF 85 for adopting draft-jones-insipid-session-id-0 as the new =
WG document solution.  If we decide that's ok, then I think it actually n=
eeds to register a new header name regardless.  We know 'Session-ID' is a=
lready in-use in the wild, and there are plenty of more strings available=
 for header names.
As you note, and as RFC5727 allows, we _can_ register a header with an=20
Informational RFC, as long as it meets the two restrictions in that=20
document.
(And I believe this one does). I also think the IESG could be convinced=20
that a Historic RFC would meet those requirements, and I don't think it=20
was the intent to exclude them when RFC5727 was put together.

I, obviously, expected that since there _was_ a standards effort around=20
this concept, and an expectation that it would use the same name in a=20
backwards compatible way, that the standards track document would do the =

registration, and there would be some relationship like the one Dan=20
points to in order to tie in this document.

I don't really care if we thread the registration differently, as long=20
as we leave a _very_ clear record of what's happening since there is=20
standards activity here. I don't think we have that in the current docume=
nt.

But my _main_ concern is that this still reads like a PS, and I would=20
rather we take the time to change the language to be clear it's=20
documenting a current situation rather than providing instructions to=20
new implementers.

RjS
>
> -hadriel
>  =20
>
> On Aug 22, 2013, at 1:08 PM, Robert Sparks <rjsparks@nostrum.com> wrote=
:
>
>> Adding the working group.
>>
>> Dan - thanks for this review. I've been working towards trying to expr=
ess a concern, and this really helped clarify what was bothering me.
>>
>> This document, AFAIK, _is not_ actually trying to register the Session=
-ID header with IANA, even though there is a section that looks like it d=
oes.
>>
>> Rather, that registration is in http://datatracker.ietf.org/doc/draft-=
ietf-insipid-session-id/
>>
>> That is a very good example of how just adding the explanatory paragra=
ph at the beginning of the document isn't enough to turn this into someth=
ing that documents an earlier path considered and implementation that exi=
sts current deployments - the text needs to be touched in several places =
to make it clear that's what the document is doing.  In the IANA consider=
ations case, one possible adjustment is to change the text to "here's wha=
t known implementations have used for syntax. See [draft-ietf-insipid-ses=
sion-id] for the intended registered syntax", and not issue instructions =
to IANA.
>>
>> It's more work for Hadriel, but I think it's necessary.
>>
>> RjS
>>
>>
>> On 8/21/13 12:26 PM, Romascanu, Dan (Dan) 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-kaplan-insipid-session-id-03.txt
>>> Reviewer: Dan Romascanu
>>> Review Date: 8/21
>>> IETF LC End Date: 8/30
>>> IESG Telechat date:
>>>
>>> Summary:
>>> Ready with Issues
>>>
>>> Major issues:
>>>
>>> 1. In similar situations when IETF WGs decided to document proprietar=
y solutions that were used as a basis for standards-track RFCs Historic R=
FCs were issued rather than Informational RFCs. See for example RFC 5412,=
 5413, 5414 which documented the prior art that was used to create RFC 54=
15. Publication of these documents was also withhold until the standards-=
track RFC was published. None of these precedents is followed here. One o=
f the reasons for the WG to prefer Informational rather than Historic is =
the fact that the registration of a new SIP header field is required from=
 IANA, and in conformance with RFC 5727 this can be done in an Informatio=
nal RFC, but not in a Historic one. What is missing however is clear text=
 that the solution described in this document is a legacy solution and th=
at the solution going forward is the one that is being defined by the INS=
IPID WG. The IESG should also consider whether this document should be ap=
proved for publication before the standards-t
>>>   rack solution defined by the INSIPID WG is also published.
>>>
>>> 2. The Abstract makes the claim that the Standards-Track RFC that wil=
l be eventually produced by the INSIPID WG will be developped in a backwa=
rds-compatible manner with this document. This does not seem appropriate =
here - if at all such a requirement should be included in draft-ietf-insi=
pid-session-id-reqts-08.txt. However it does not appear there, and that d=
ocument was recently submitted for publication to the IESG, so the WG did=
 not include it in its consensus.
>>>
>>> Minor issues:
>>>
>>> 1. The IANA considerations sections need to be more explicit in demon=
strating that the conditions for registration of extension SIP header fie=
lds in Informational RFCs have been met as per RFC 5727. That RFC defines=
 that Designated Expert review needs to happen for such new registrations=
 - I could not find a proof that such a review took place in the shepherd=
 write-up. Actually the question about the expert reviews is not answered=
 directly, instead of an answer wide deployment is mentioned, but that de=
ployment could not use this SIP header field which was not yet approved. =
According to RFC 5727 there are two basic conditions that need to be veri=
fied by the Designated Expert - that the proposed header field must be of=
 a purely informational nature and must not significantly change the beha=
vior of SIP entities that support it, and that the proposed header field =
must not undermine SIP security in any sense, and that the Informational =
RFC defining the header field must address se
>>>   curity issues in detail, as if it were a standards-track document. =
I believe that both conditions are met by the I-D, but there is no adequa=
te text in the IANA considerations section to explain this.
>>>
>>> Nits/editorial comments:
>>>
>>>
>>> Regards,
>>>
>>> Dan
>>>
>>>
>>> _______________________________________________
>>> Gen-art mailing list
>>> Gen-art@ietf.org
>>> https://www.ietf.org/mailman/listinfo/gen-art
>>



From ben@nostrum.com  Thu Aug 22 13:50:25 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F067811E820D; Thu, 22 Aug 2013 13:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 OXc8-2JcpDCq; Thu, 22 Aug 2013 13:50:24 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BF54411E812C; Thu, 22 Aug 2013 13:50:23 -0700 (PDT)
Received: from [10.0.1.9] (cpe-76-187-89-238.tx.res.rr.com [76.187.89.238]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7MKoAjg003176 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 22 Aug 2013 15:50:10 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C489C55@MX15A.corp.emc.com>
Date: Thu, 22 Aug 2013 15:50:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <731F5428-B21C-411E-AC44-EEAD241202C4@nostrum.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C489319@MX15A.corp.emc.com> <AEC7E92F-7370-4D76-B0DF-E9738FABCB86@computer.org> <8D3D17ACE214DC429325B2B98F3AE7129C489C55@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.89.238 is authenticated by a trusted mechanism)
Cc: "bclaise@cisco.com" <bclaise@cisco.com>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Eric McMurry <emcmurry@computer.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dime-overload-reqs-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, 22 Aug 2013 20:50:25 -0000

Hi David,

We agree on all your points, and will make the updates in the next =
version, pending shepherd instructions.

Thanks!

Ben.

On Aug 22, 2013, at 2:50 PM, "Black, David" <david.black@emc.com> wrote:

> Hi Eric,
>=20
> This looks good - comments follow ...
>=20
>>> a) I assume that overload control development work will derive more =
specific
>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>> The discussion in security considerations section seems reasonable.
>>=20
>> We agree with this.  The thinking here was that we didn't want to =
specify this
>> in a way that would be specific to a particular type of mechanism.  =
It might
>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>> considerations.
>=20
> That would be good to add as a note on REQ 27.
>=20
>> The intent was very much as you say, where requirements on individual =
node
>> capabilities are hoped to result in better overall system behaviors. =
There are
>> also some requirements that are stated more at the system level (e.g. =
7 and
>> 17.) Also the text in section 2.2 that discusses Figure 5 talks about =
how
>> insufficient server capacity at a cluster of servers behind a =
Diameter agent
>> can be treated as if the agent itself was overloaded.
>>=20
>> On the other hand, any mechanism we design will have to focus on =
actions of
>> individual nodes, so the numbered requirements tend to focus on that. =
I'm not
>> sure where to change the balance here--do you have specific =
suggestions?
>=20
> I noted this as editorial rather than a minor issue, as I was mostly =
concerned
> that the actual design work will be informed by a sufficient =
architectural "clue"
> that the goal is "better overall system behaviors", which your =
response indicates
> will definitely be the case ;-).
>=20
> Rather than edit individual requirements, how about adding the =
following sentence
> immediately following the introductory sentence in Section 7?:
>=20
> 	These requirements are stated primarily in terms of individual =
node
> 	behavior to inform the design of the improved mechanism;
> 	that design effort should keep in mind that the overall goal is
> 	improved overall system behavior across all the nodes involved,=20=

> 	not just improved behavior from specific individual nodes.
>=20
>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>=20
>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>> "effects" or "problems".
>>=20
>> We are fine with any of those alternatives.  How about impacts.
>=20
> That's fine.  FWIW, "congestion collapse" has a specific (rather =
severe)
> meaning over in the Transport Area, and that meaning was not intended =
here.
>=20
>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>> that out.  The part of it we are referencing is historical front =
matter
>> though.
>=20
> I'd note the reference as work in progress, and put the statement =
about stable
> front matter (historical is a bad work to use here) in the body of the =
draft
> that cites the reference.
>=20
>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get the
>> warnings you saw (about the references).  What did it say?
>=20
> Sorry, I didn't mean to send you on a wild goose chase :-).  The =
idnits confusion
> manifested right at the top of the output, where everyone ignores it =
...
>=20
>   Attempted to download rfc272 state...
>   Failure fetching the file, proceeding without it.
>=20
> You didn't reference RFC 272, so that output's apparently courtesy of =
idnits
> misinterpreting this reference:
>=20
> 1195	   [TS29.272]
> 1196	              3GPP, "Evolved Packet System (EPS); Mobility =
Management
> 1197	              Entity (MME) and Serving GPRS Support Node (SGSN) =
related
> 1198	              interfaces based on Diameter protocol", TS 29.272 =
11.4.0,
> 1199	              September 2012.
>=20
> I was amused :-).
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Eric McMurry [mailto:emcmurry@computer.org]
>> Sent: Thursday, August 22, 2013 3:06 PM
>> To: Black, David
>> Cc: ben@nostrum.com; General Area Review Team (gen-art@ietf.org);
>> ietf@ietf.org; dime@ietf.org; bclaise@cisco.com
>> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>>=20
>> Hi David,
>>=20
>> Thank you for the review.  Your time and comments are appreciated!
>>=20
>> comments/questions inline.
>>=20
>>=20
>> Eric
>>=20
>>=20
>>=20
>> On Aug 17, 2013, at 9:18 , "Black, David" <david.black@emc.com> =
wrote:
>>=20
>>>=20
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>>=20
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>=20
>>> Please resolve these comments along with any other Last Call =
comments
>>> you may receive.
>>>=20
>>> Document: draft-ietf-dime-overload-reqs-10
>>> Reviewer: David L. Black
>>> Review Date: August 17, 2013
>>> IETF LC End Date: August 16, 2013
>>> IESG Telechat date: (if known)
>>>=20
>>> Summary:
>>> This draft is basically ready for publication, but has nits that =
should be
>>> fixed before publication.
>>>=20
>>> This draft describes scenarios in which Diameter overload can occur =
and provides
>>> requirements for development of new overload control functionality =
in Diameter.
>>> It is well written, and the inclusion of scenarios in which overload =
can occur,
>>> both in terms of the relationships among types of Diameter nodes and =
actual mobile
>>> network experience is very helpful.
>>>=20
>>> I apologize for this review being a day late, as I've been on =
vacation for most
>>> of this draft's IETF Last Call period.
>>>=20
>>> Major issues: (none)
>>>=20
>>> Minor issues: (none)
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> The following two comments could be minor issues, but I'm going to =
treat them
>>> as editorial, as I expect that they will be addressed in development =
of the
>>> actual overload functionality:
>>>=20
>>> a) I assume that overload control development work will derive more =
specific
>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>> The discussion in security considerations section seems reasonable.
>>=20
>> We agree with this.  The thinking here was that we didn't want to =
specify this
>> in a way that would be specific to a particular type of mechanism.  =
It might
>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>> considerations.
>>=20
>>>=20
>>> b) The draft, and especially its requirements in Section 7 are =
strongly
>>> focused on individual Diameter node overload.  That's necessary, but =
overload
>>> conditions can be broader, affecting an entire service or =
application, or
>>> multiple instances of either/both, even if not every individual =
Diameter node
>>> involved is overloaded.  A number of the requirements, starting with =
REQ 22
>>> could be generalized to cover broader overload conditions.
>>>=20
>>> This (b) has implications for other requirements, e.g., REQ 13 =
should also be
>>> generalized beyond a single node to avoid increased traffic in an =
overload
>>> situation, even from a node that is not overloaded by itself.  There =
are limits
>>> on what is reasonable here, as the desired overload functionality is =
TCP/SCTP-
>>> like reaction to congestion where individual actions taken by nodes =
based on
>>> the information they have (which is not the complete state of the =
network)
>>> results in an overall reduction of load.
>>=20
>> The intent was very much as you say, where requirements on individual =
node
>> capabilities are hoped to result in better overall system behaviors. =
There are
>> also some requirements that are stated more at the system level (e.g. =
7 and
>> 17.) Also the text in section 2.2 that discusses Figure 5 talks about =
how
>> insufficient server capacity at a cluster of servers behind a =
Diameter agent
>> can be treated as if the agent itself was overloaded.
>>=20
>> On the other hand, any mechanism we design will have to focus on =
actions of
>> individual nodes, so the numbered requirements tend to focus on that. =
I'm not
>> sure where to change the balance here--do you have specific =
suggestions?
>>=20
>>>=20
>>> Section 1.2, 2nd paragraph:
>>>=20
>>>  as network congestion, network congestion can reduce a Diameter =
nodes
>>>=20
>>> "nodes" -> "node's"
>>=20
>> good catch.
>>=20
>>>=20
>>> Section 5, 1st paragraph:
>>>=20
>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>=20
>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>> "effects" or "problems".
>>=20
>> We are fine with any of those alternatives.  How about impacts.
>>=20
>>>=20
>>> Section 7
>>>=20
>>> The long enumerated list of requirements is not an easy read.  It =
would be
>>> better if these could somehow be grouped by functional category, =
e.g.,
>>> security, transport interactions, operational/administrative, etc.
>>=20
>> agree.  It is actually in sections in the XML (denoted by comments), =
we just
>> did not promote those to visible sections in the txt.  I recall there =
being
>> some issue with xml2rfc and numbering, but now that the numbers are =
set, this
>> would not be hard to do.
>>=20
>>=20
>>>=20
>>> idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - this =
is fine,
>>> as the boilerplate has been appropriately modified for this draft =
that
>>> expresses requirements (as opposed to a draft that specifies a =
protocol).
>>>=20
>>> idnits 2.12.17 got confused by the 3GPP and GSMA Informative =
References.
>>> I assume that they're all sufficiently stable to be informative =
references.
>>> However, [TR23.843] is a work in progress, and should be noted as =
such in
>>> its reference - is this needed for any of the other 3GPP or GSMA =
references?
>>=20
>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>> that out.  The part of it we are referencing is historical front =
matter
>> though.
>>=20
>>=20
>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get the
>> warnings you saw (about the references).  What did it say?
>>=20
>>=20
>>>=20
>>> Thanks,
>>> --David
>>> ----------------------------------------------------
>>> David L. Black, Distinguished Engineer
>>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>>> david.black@emc.com        Mobile: +1 (978) 394-7754
>>> ----------------------------------------------------
>>>=20
>>=20
>=20


From suresh.krishnan@ericsson.com  Thu Aug 22 14:09:34 2013
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCF2511E81F8; Thu, 22 Aug 2013 14:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Skf9UoqItuAF; Thu, 22 Aug 2013 14:09:29 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 39E4311E8131; Thu, 22 Aug 2013 14:09:27 -0700 (PDT)
X-AuditID: c6180641-b7fe28e000000d82-a2-52167e0640d1
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 30.42.03458.60E76125; Thu, 22 Aug 2013 23:09:26 +0200 (CEST)
Received: from [142.133.113.185] (147.117.188.134) by smtps-am.internal.ericsson.com (147.117.188.90) with Microsoft SMTP Server (TLS) id 14.2.328.9; Thu, 22 Aug 2013 17:09:25 -0400
Message-ID: <52167D67.2010103@ericsson.com>
Date: Thu, 22 Aug 2013 17:06:47 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
References: <521652E0.8030300@nostrum.com>
In-Reply-To: <521652E0.8030300@nostrum.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [147.117.188.134]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFLMWRmVeSWpSXmKPExsUyuXRPlC5bnViQwc9LShYPNixhtLj66jOL xbWfT9ktrs1pZHNg8Viy5CeTx6ydT1g8vlz+zBbAHMVlk5Kak1mWWqRvl8CVsbzhLEvBJpGK 1TeKGxh7BLoYOTkkBEwkFm/5ywZhi0lcuLcezBYSOMoocWBKaRcjF5C9k1Fi1pWbzF2MHBy8 AtoSb064g9SwCKhKTFv5DqyeDWjOhp2fmUBsUYEwifvnDoHZvAKCEidnPmEBsUUENCSuLVnC DmIzC9RKnOp5wAhiCwsESUzfP58JYq+WRO/vy8wgNifQqmk//jFB3CYpsW3RMahePYkpV1sY IWx5ie1v5zBD9GpKbF3znRWiXlni37sVLBMYhWchOWMWkvZZSNoXMDKvYuQoLU4ty003MtzE CAzvYxJsjjsYF3yyPMQozcGiJM67Qe9MoJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbGUKNW R78bD7Z27fx6Y+E27fot1zWf7Zh1iM1QnGs645/0FTeu7P3v8eb1H0nhN62yieFdJa3iD3dm CL5uuPVhfve2feZ7+n5M2Brt+e3gq4bi1JblLDZxXletz23iLddbECR/4Xk7845f7pLr1a0m a3b+X8uXxmzH/2nh3IvNMtFJ5yXVP7bPVGIpzkg01GIuKk4EAGPVpu89AgAA
Cc: netext@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-ietf-netext-update-notifications@tools.ietf.org
Subject: Re: [Gen-art] [netext] Gen-ART LC review: draft-ietf-netext-update-notifications-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 21:09:35 -0000

Hi Robert,
  Thanks a lot for the review. We will include the changes in the next
revision we submit. Please see proposed changes inline.

On 08/22/2013 02:05 PM, Robert Sparks 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-netext-update-notifications-07
> Reviewer: Robert Sparks
> Review Date: 2013-08-22
> IETF LC End Date: 2013-08-29
> IESG Telechat date: not scheduled
> 
> Summary: This draft is ready for publication as Proposed Standard
> 
> I had to read through this text several times to convince myself
> implementers could figure out what order they were required to take
> steps in vs where they had flexibility:
> 
>    o  Upon accepting the Update Notification message, the mobile access
>       gateway MUST process the message and perform the actions based on
>       the Notification Reason.
>       *  If the (A) flag in the message is set to a value of (1), the
>          mobile access gateway MUST first send an Update Notification
>          Acknowledgement message and set the status code field according
>          to the result of processing the Update Notification message.
> 
> In particular, it's not immediately obvious if there is tension between
> that "MUST first" and having "the result of processing" available.
> Please consider rewording to make it clearer that this "result of
> processing" is not intended to include waiting for the result of some
> action processing this notification message might trigger.

I think we can lose the word first without losing anything. Does the
following rewording work for you?

OLD:
If the (A) flag in the message is set to a value of (1), the mobile
access gateway MUST first send an Update Notification Acknowledgement
message and set the status code field according to the result of
processing the Update Notification message.

NEW:
If the (A) flag in the message is set to a value of (1), the mobile
access gateway MUST send an Update Notification Acknowledgement message
with the status code field set based on the result of processing the
Update Notification message.

> 
> It might help readers understand the intended usual case retransmission
> mechanics if the expected default values listed in section 7 were called
> out earlier in the document.

Sure. Will call out the defaults at first use.

Thanks
Suresh


From rjsparks@nostrum.com  Thu Aug 22 14:51:16 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3870E21F9F0A; Thu, 22 Aug 2013 14:51:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.14
X-Spam-Level: 
X-Spam-Status: No, score=-102.14 tagged_above=-999 required=5 tests=[AWL=0.460, 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 pah0-4iHErQ3; Thu, 22 Aug 2013 14:51:15 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4B29C21F9EED; Thu, 22 Aug 2013 14:51:15 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7MLp9lP009783 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Thu, 22 Aug 2013 16:51:11 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <521687CD.40502@nostrum.com>
Date: Thu, 22 Aug 2013 16:51:09 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <521652E0.8030300@nostrum.com> <52167D67.2010103@ericsson.com>
In-Reply-To: <52167D67.2010103@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Cc: netext@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-ietf-netext-update-notifications@tools.ietf.org
Subject: Re: [Gen-art] [netext] Gen-ART LC review: draft-ietf-netext-update-notifications-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 21:51:16 -0000

On 8/22/13 4:06 PM, Suresh Krishnan wrote:
> Hi Robert,
>    Thanks a lot for the review. We will include the changes in the next
> revision we submit. Please see proposed changes inline.
>
> On 08/22/2013 02:05 PM, Robert Sparks 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-netext-update-notifications-07
>> Reviewer: Robert Sparks
>> Review Date: 2013-08-22
>> IETF LC End Date: 2013-08-29
>> IESG Telechat date: not scheduled
>>
>> Summary: This draft is ready for publication as Proposed Standard
>>
>> I had to read through this text several times to convince myself
>> implementers could figure out what order they were required to take
>> steps in vs where they had flexibility:
>>
>>     o  Upon accepting the Update Notification message, the mobile access
>>        gateway MUST process the message and perform the actions based on
>>        the Notification Reason.
>>        *  If the (A) flag in the message is set to a value of (1), the
>>           mobile access gateway MUST first send an Update Notification
>>           Acknowledgement message and set the status code field according
>>           to the result of processing the Update Notification message.
>>
>> In particular, it's not immediately obvious if there is tension between
>> that "MUST first" and having "the result of processing" available.
>> Please consider rewording to make it clearer that this "result of
>> processing" is not intended to include waiting for the result of some
>> action processing this notification message might trigger.
> I think we can lose the word first without losing anything. Does the
> following rewording work for you?
Yes, thanks!
>
> OLD:
> If the (A) flag in the message is set to a value of (1), the mobile
> access gateway MUST first send an Update Notification Acknowledgement
> message and set the status code field according to the result of
> processing the Update Notification message.
>
> NEW:
> If the (A) flag in the message is set to a value of (1), the mobile
> access gateway MUST send an Update Notification Acknowledgement message
> with the status code field set based on the result of processing the
> Update Notification message.
>
>> It might help readers understand the intended usual case retransmission
>> mechanics if the expected default values listed in section 7 were called
>> out earlier in the document.
> Sure. Will call out the defaults at first use.
>
> Thanks
> Suresh
>


From mahoney@nostrum.com  Thu Aug 22 15:23:05 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3229321F9DDB for <gen-art@ietfa.amsl.com>; Thu, 22 Aug 2013 15:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SnJis6bC69aA for <gen-art@ietfa.amsl.com>; Thu, 22 Aug 2013 15:23:04 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 628BA21F96A8 for <gen-art@ietf.org>; Thu, 22 Aug 2013 15:23:04 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7MMMxsw013104 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 22 Aug 2013 17:23:03 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <52168F43.9030306@nostrum.com>
Date: Thu, 22 Aug 2013 17:22:59 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-08-22
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 22:23:05 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Alexey Melnikov   2013-09-02   draft-ietf-v6ops-rfc3316bis-03

Ben Campbell      2013-09-16   draft-kelsey-intarea-mesh-link-establishment-05

Brian Carpenter   2013-09-13   draft-ietf-mediactrl-call-flows-13

Christer Holmberg 2013-09-03   draft-ietf-pim-rfc4601-update-survey-report-03

Dan Romascanu     2013-09-03   draft-ietf-dhc-dhcpv6-solmaxrt-update-03

Francis Dupont    2013-09-03   draft-ietf-mpls-targeted-mldp-03

Joel Halpern      2013-09-18   draft-boucadair-rfc6153-update-01

Meral Shirazipour 2013-09-02   draft-ietf-spfbis-4408bis-19 *
                   2013-09-05   draft-ietf-alto-server-discovery-09 **

Roni Even         2013-09-04   draft-ietf-mpls-return-path-specified-lsp-ping-12

Russ Housley      2013-09-02   draft-ietf-ccamp-gmpls-g709-framework-14

Suresh Krishnan   2013-09-13   draft-worley-service-example-13

Vijay Gurbani     2013-09-02   draft-ietf-ccamp-gmpls-signaling-g709v3-11

Wassim Haddad     2013-09-02   draft-ietf-v6ops-mobile-device-profile-04

* Previous Early Review
** 2nd Last Call


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

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


The standard template is included below.

Thanks,

Jean

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From mahoney@nostrum.com  Thu Aug 22 15:27:36 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 705FF21F9CA4 for <gen-art@ietfa.amsl.com>; Thu, 22 Aug 2013 15:27:36 -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 bc8C8EEa94oY for <gen-art@ietfa.amsl.com>; Thu, 22 Aug 2013 15:27:36 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id CEE4E21F9C53 for <gen-art@ietf.org>; Thu, 22 Aug 2013 15:27:35 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-53-173.dllstx.fios.verizon.net [173.71.53.173]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7MMRZFW013603 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 22 Aug 2013 17:27:35 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <52169057.1000809@nostrum.com>
Date: Thu, 22 Aug 2013 17:27:35 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.53.173 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2013-08-29 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, 22 Aug 2013 22:27:36 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft
------------------------------------------------------------------------------------
Brian Carpenter        2013-07-15 draft-ietf-lisp-deployment-10 *

Christer Holmberg      2013-05-15 draft-ietf-6man-addr-select-opt-11 *

David Black            2013-07-18 draft-ietf-trill-directory-framework-07 *

Dan Romascanu          2013-01-28 draft-ietf-storm-iscsimib-04 *

Francis Dupont         2013-08-19 draft-ietf-storm-ipsec-ips-update-03 **

Martin Thomson         2013-08-13 draft-bormann-cbor-05 *

* Earlier draft reviewed
** Already reviewed


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

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

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

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

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From david.black@emc.com  Thu Aug 22 15:35:05 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D38F811E8215; Thu, 22 Aug 2013 15:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.947
X-Spam-Level: 
X-Spam-Status: No, score=-102.947 tagged_above=-999 required=5 tests=[AWL=-0.948, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, 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 VKnpJQGr3JaM; Thu, 22 Aug 2013 15:35:01 -0700 (PDT)
Received: from mexforward.lss.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2767911E81C7; Thu, 22 Aug 2013 15:35:00 -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 r7MMYkK8009837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Aug 2013 18:34:46 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 22 Aug 2013 18:34:37 -0400
Received: from mxhub16.corp.emc.com (mxhub16.corp.emc.com [128.222.70.237]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7MMYa2Y015790; Thu, 22 Aug 2013 18:34:37 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub16.corp.emc.com ([128.222.70.237]) with mapi; Thu, 22 Aug 2013 18:34:36 -0400
From: "Black, David" <david.black@emc.com>
To: "Black, David" <david.black@emc.com>, "ldunbar@huawei.com" <ldunbar@huawei.com>, Donald Eastlake <d3e3e3@gmail.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "igor@yahoo-inc.com" <igor@yahoo-inc.com>, General Area Review Team <gen-art@ietf.org>
Date: Thu, 22 Aug 2013 18:34:35 -0400
Thread-Topic: Gen-ART review of draft-ietf-trill-directory-framework-07
Thread-Index: Ac6fh8c0o2/+z0qDRW228DSyR4uVuQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C489C9C@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "trill@ietf.org" <trill@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-trill-directory-framework-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 22:35:06 -0000

The -07 version is also ready for publication as an Informational RFC

Thanks,
--David

> -----Original Message-----
> From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On Behal=
f Of
> Black, David
> Sent: Monday, July 29, 2013 7:20 AM
> To: ldunbar@huawei.com; Donald Eastlake; Radia@alum.mit.edu; igor@yahoo-
> inc.com; General Area Review Team
> Cc: Ted Lemon; ietf@ietf.org; trill@ietf.org
> Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-directory-frame=
work-
> 06
>=20
> The -06 version of this draft resolves all of the concerns raised by the =
Gen- ART
> review of the -05 version - the -06 version is ready for publication as a=
n
> Informational RFC.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Wednesday, July 17, 2013 7:54 PM
> > To: ldunbar@huawei.com; Donald Eastlake; Radia@alum.mit.edu; igor@yahoo=
-
> > inc.com; General Area Review Team
> > Cc: trill@ietf.org; ietf@ietf.org; Black, David; Ted Lemon
> > Subject: Gen-ART review of draft-ietf-trill-directory-framework-05
> >
> > Document: draft-ietf-trill-directory-framework-05
> > Reviewer: David L. Black
> > Review Date: July 17, 2013
> > IETF LC End Date: July 18, 2013
> >
> > Summary:
> > This draft is on the right track but has open issues, described in the =
review.
> >
> > This draft describes a framework for using directory servers to provide
> > address mappings (address -> destination RBridge) to TRILL Rbridges as =
an
> > alternative to data plane learning and use of the TRILL ESADI protocol.
> >
> > The draft's generally well written and clear.  I found a couple of mino=
r
> > issues.
> >
> > Major issues: None.
> >
> > Minor issues:
> >
> > [1] The last bullet in Section 3.1 says:
> >
> >        - In an environment where VMs migrate, there is a higher chance
> >          of cached information becoming invalid, causing traffic to be
> >          black-holed by the ingress RBridge, that is, persistently sent
> >          to the wrong egress RBridge. If VMs do not flood gratuitous
> >          ARP/ND or VDP [802.1Qbg] messages upon arriving at new
> >          locations, the ingress nodes might not have MAC entries for th=
e
> >          MAC of the newly arrived VMs, causing unknown address flooding=
.
> >
> > This is incorrect in multiple ways and should just be removed:
> >
> > - Persistent black-holing is rare in practice because all common
> > 	VM migration implementations issue the gratuitous messages.
> > - VMs don't send the gratuitous messages, hypervisors do.
> > - VDP is not flooded.  The receiver's always a bridge.
> > - At least one common VM migration implementation actually uses a gratu=
itous
> > 	RARP, not ARP.
> > - Flooding is done by the bridges and Rbridges, not the VMs.
> >
> > [2] There are some unfortunate notation problems in Section 5.1 that ca=
rry
> > into the following sections, based on the logical data structure:
> >
> >    [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
> >    interested RBridges}]
> >
> > - The first open curly brace ('{') is unmatched.
> > - Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
> > 	none of which appear in that structure.
> >
> > Nits/editorial comments:
> >
> > Section 1 - item 1 in the numbered list does not explain why it makes
> > a directory approach attractive.  This should be added, as it is
> > present for the other three items .
> >
> > Section 2 - Say that IS-IS is a routing protocol.
> > The definition of Station should say that the node or virtual node
> > is on a network.  Also, please define or explain "virtual node".
> >
> > Section 3.2 - Add the number of entries to be learned to scenario #1
> > in order to parallel the scenario # 2 discussion.
> >
> > Section 4 - remove "(distributed model)" from first paragraph,
> > as it's not explained.
> >
> > Section 5.3, top of p.13:
> >
> >    therefore, there needs to be some mechanism by which RBridges that
> >    have pulled information that has not expired can be informed when
> >    that information changes or the like.
> >
> > "or the like" is vague.  I suggest "or becomes invalid for other
> >  reasons".
> >
> > idnits 2.12.17 didn't 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=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From brian.e.carpenter@gmail.com  Thu Aug 22 16:38:48 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CEA811E8270 for <gen-art@ietfa.amsl.com>; Thu, 22 Aug 2013 16:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yk+2RyS2NkDt for <gen-art@ietfa.amsl.com>; Thu, 22 Aug 2013 16:38:47 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id A2FC611E8239 for <gen-art@ietf.org>; Thu, 22 Aug 2013 16:38:47 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id q10so2524185pdj.20 for <gen-art@ietf.org>; Thu, 22 Aug 2013 16:38:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=ujYhf5fPMFv+ku0Qm+Zzvyap8T2BSYdDkKJLpUoTR4E=; b=iwOtJadc5+5L449WZb6z8xJs7Q6kk24w8HYJymRh9qQVNq6mLbhW+qiaM+NfFRWFDi OqWyDAvKsO81iJ6ULHepraSa1oIOdKr51bQMN/SPsNz6ACvAroKck+FnUzqPQUQSNLNc FVkBCgpuDTPFG6nbcd3G28hCqbhaR6/bW/RAj2hYqbO5YE3+VtnZsyp5omQ1/L+rsrqX O3aYY1yKdDhesQXnKvOlOX8mCo5R7PCvNlmND9dncQeXUJgNpWmRXT2DIkno9UL9qEXL XDo41ZQpnyuU7MpubwM3Wlhk0uYbPoNekeJnoLoF4JuTvEtfKb1XcjZJQypmNTNucRHC Fy0A==
X-Received: by 10.66.152.102 with SMTP id ux6mr17493640pab.79.1377214727379; Thu, 22 Aug 2013 16:38:47 -0700 (PDT)
Received: from [192.168.178.20] (10.200.69.111.dynamic.snap.net.nz. [111.69.200.10]) by mx.google.com with ESMTPSA id mz5sm17414171pbc.18.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 22 Aug 2013 16:38:46 -0700 (PDT)
Message-ID: <5216A111.1020100@gmail.com>
Date: Fri, 23 Aug 2013 11:38:57 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-lisp-deployment.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-lisp-deployment-10.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, 22 Aug 2013 23:38:48 -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-lisp-deployment-10.txt
Reviewer: Brian Carpenter
Review Date: 2013-08-23
IETF LC End Date: 2013-07-15
IESG Telechat date: 2013-08-29

Summary:  Ready
--------

Comments:
---------

Thanks for handling my Last Call comments.

From christer.holmberg@ericsson.com  Thu Aug 22 23:27:39 2013
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6C9B21F9AB8 for <gen-art@ietfa.amsl.com>; Thu, 22 Aug 2013 23:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.968
X-Spam-Level: 
X-Spam-Status: No, score=-5.968 tagged_above=-999 required=5 tests=[AWL=0.280,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KO6GCOqXaI81 for <gen-art@ietfa.amsl.com>; Thu, 22 Aug 2013 23:27:34 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 108C411E8243 for <gen-art@ietf.org>; Thu, 22 Aug 2013 23:27:33 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f738e000003ee3-c7-521700d4a7c3
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 51.ED.16099.4D007125; Fri, 23 Aug 2013 08:27:32 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.146]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.02.0328.009; Fri, 23 Aug 2013 08:27:32 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Genart review of draft-ietf-6man-addr-select-opt-11.txt
Thread-Index: Ac6fyZ8eXq5W0KzNRL2SiGihBg9rtw==
Date: Fri, 23 Aug 2013 06:27:31 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C476333@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.19]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C476333ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFLMWRmVeSWpSXmKPExsUyM+Jvje4VBvEgg7WnLSzOLp7EanH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvjyxbXgptqFafvPWFrYPyi2MXIySEhYCKx 9PtiJghbTOLCvfVsILaQwGFGiRXfgeJcQPYSRokrr38xdjFycLAJWEh0/9MGqRER0JSYu+It WC+zQL7EhL2TwXqFBRwkTl3dzQpR4yqx6v19JghbT2Lj0v0sIDaLgKpE06MdYPW8Ar4Sf+Yf B6thBLrh+6k1UDPFJW49mQ91m4DEkj3nmSFsUYmXj/+xQtiKEu1PGxhhbth8+xc7xExBiZMz n7BMYBSehWTULCRls5CUQcR1JBbs/sQGYWtLLFv4mhnGPnPgMROy+AJG9lWM7LmJmTnp5Yab GIHxcXDLb90djKfOiRxilOZgURLn3aR3JlBIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDo90v G3vJ3RtT77xoeGzv+etdk5l9Tdrdc1uusR7sPijA++S9+6L7rUW9x/uaZOZJP5v02+EDW9ac 4Dt1N+vqXS98lI/833H12PE3St0XwjbJn6sOqgvTr7L75ct6MDrMhfHi531vVLbN1jeLjXxv fez6/kMmL7h8szR1P/idDJd8VOwnq8G1T4mlOCPRUIu5qDgRADjl3kpdAgAA
Cc: "draft-ietf-6man-addr-select-opt.all@tools.ietf.org" <draft-ietf-6man-addr-select-opt.all@tools.ietf.org>
Subject: [Gen-art] Genart review of draft-ietf-6man-addr-select-opt-11.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, 23 Aug 2013 06:27:39 -0000

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

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



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



Document: draft-ietf-6man-addr-select-opt-11.txt

Reviewer: Christer Holmberg

Review Date: 23 August 2013

IETF LC End Date: 15 May, 2013

IESG Telechat date: 29 August, 2013



Summary: The minor editorial issue I had on the previous version (-10) of t=
he draft has been addressed. The document is ready for publication, without=
 any further comments.



Major issues: -



Minor issues: -



Nits/editorial comments: -



Regards,



Christer


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@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:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on Gen-ART, please see the FAQ at &lt;
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please wait for direction from your document shep=
herd or AD before posting a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document: draft-ietf-6man-addr-select-opt-11.txt<=
o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: Christer Holmberg<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 23 August 2013<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 15 May, 2013<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: 29 August, 2013<o:p></o:p></p=
>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary: The minor editorial issue I had on the p=
revious version (-10) of the draft has been addressed. The document is read=
y for publication, without any further comments.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major issues: -<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor issues: -<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Nits/editorial comments: -<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Regards,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Christer<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1C476333ESESSMB209erics_--

From magnus.westerlund@ericsson.com  Fri Aug 23 01:51:35 2013
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 6BF7E11E82E5; Fri, 23 Aug 2013 01:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.351
X-Spam-Level: 
X-Spam-Status: No, score=-105.351 tagged_above=-999 required=5 tests=[AWL=0.898, 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 TalCClRElYpF; Fri, 23 Aug 2013 01:51:29 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id F099711E82D2; Fri, 23 Aug 2013 01:51:25 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f738e000003ee3-e8-5217228cc16d
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 4A.0D.16099.C8227125; Fri, 23 Aug 2013 10:51:24 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.148) by smtp.internal.ericsson.com (153.88.183.38) with Microsoft SMTP Server id 14.2.328.9; Fri, 23 Aug 2013 10:51:22 +0200
Message-ID: <521722BF.8010207@ericsson.com>
Date: Fri, 23 Aug 2013 10:52:15 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Elwyn Davies <elwynd@folly.org.uk>
References: <1370477514.4596.9052.camel@mightyatom>
In-Reply-To: <1370477514.4596.9052.camel@mightyatom>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPLMWRmVeSWpSXmKPExsUyM+JvjW6PkniQwY9ZlhYXvxxhtzh+YAe7 xdVXn1kspi5/zOLA4vH1ZDuLx5IlP5k8vlz+zBbAHMVlk5Kak1mWWqRvl8CVsftJRcH7woqz u18yNjA+jOpi5OCQEDCROLkltIuRE8gUk7hwbz1bFyMXh5DAYUaJz/OnsUA4yxklrr3sYAap 4hXQluiYMYMJxGYRUJU4P7WfEcRmE7CQuPmjkQ3EFhUIlmjf/pUNol5Q4uTMJywgtoiAmsTm rw8YQYYyC3QzSsx+dgFskLCAj8SWCavBioQEjCUef33PCmJzAl13t7WLFeI8SYlti46xg9jM AnoSU662MELY8hLNW2czQ/RqSzQ0dbBOYBSahWT3LCQts5C0LGBkXsXInpuYmZNebriJERjI B7f81t3BeOqcyCFGaQ4WJXHeTXpnAoUE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwGgpGdNe/ /furfYvdjhuOUWJTU41vam0yVlA2ONNVxCy1goVv0Ue3/tTAD/6f1n6sPLP/lXfHvf2T/zo3 ykZPTK6a+EBAYe1E7tWft/3jmhbInHTFb+1OK5uOT0szFF1+CIrG8s5LFVPc7GWh1irIU/7p RHr0NZaqHs9Cx/6pMTf3lW99ecpCiaU4I9FQi7moOBEAD+ZUZTICAAA=
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 23 Aug 2013 08:51:35 -0000

Hi,

Continuing with the issues after Section 11.

Once more a big thanks for the work you have put into this. It is really
helpful, both from clarity point of view and finding some actual
protocol issues.



On 2013-06-06 02:11, Elwyn Davies wrote:

 >
> s13.4.1, para 2:
>> Upon receipt of the PLAY request, the server MUST position the normal
>>    play time to the beginning of the range specified in the received
>>    Range header 
> 
> Should this mention the caveat that (if I understood earlier statements
> correctly) the server may not be able to deliver exactly on this MUST
> and then sets it the nearest it can manage? This is borne out by the
> example later in this section where the server sets the start point back
> 10ms (and says so), etc.  Seek-Style affects the interpreation of MUST!

Yes, I have added that this needs to happen ".. within the limits of the
media resource and in accordance with the Seek-Style header (Section
X.Y) ..".



> 
> s13.4.4/.5/.7/.8: In these sections the Media-Property random access
> property is stated as being required to be Random-Access.  Is
> Conditional Random Access a possible value for this property? The
> confusion in s4.9.1 does not allow me to conclude that this shouldn't be
> a value for the property (sorry for the double negative but this looks a
> bit confused).

These section lists the Media-Properties for the media resource one
request delivery for. Thus from a PLAY request perspective using a
Seek-Style: CoRAP header is fine for the ones that has Random Access
property as Random-Access in these section.


> 
> s13.5.1:  Apologies if this question is stupid - I am not a media stream
> wxpert.  Suppose we have an aggregated stream with (say) a number of
> recorded media items making up the aggregate.  The client sets it on to
> play to the end.  What happens if not all the streams end at the same
> time?  Do we get PLAY_NOTIFY End-of-Stream notifications for each
> individual stream as it ends or just one when the complete aggregate
> ends?

Not at all a stupid question. This should have been clearly specified
for all usages of PLAY_NOTIFY in regards to aggregated sessions. Thus I
have added both a general requirement on PLAY_NOTIFY level:

PLAY_NOTIFY requests MAY use both aggregate control URI and individual
media resource URIs depending on scope of the notification. This scope
may have important distinctions for aggregated sessions, and each reason
for a PLAY_NOTIFY request needs to specify the interpretation and if
aggregated control URIs or individual URIs may be used in requests.

And specified the following for end-of-stream:

For RTSP Session where media resources under aggregated control the
media resources will normally end at approximately the same time,
although some small differences may exist, on the scale of  a few
hundred of milliseconds. In those cases a RTSP session under aggregated
control SHOULD send only a single PLAY_NOTIFY request. By using the
aggregate control URI in the PLAY_NOTIFY request the RTSP server
indicates that this applies to all media resources within the session.
In cases RTP is used for media delivery corresponding RTP-Info needs to
be included for all media resources. In cases where one or more media
resource has significantly shorter duration than some other resources in
the aggregated session the server MAY send end-of-stream notifications
using individual media resource URIs to indicate to agents that there
will be no more media for this particular media resource related to the
current active PLAY request. In such cases when the remaining media
resources comes to end-of-stream they MUST send a PLAY_NOTIFY request
using the aggregate control URI to indicate that no more resources remains.

And the following for Media-Properties-Update

The Media-Properties header has session scope, thus for aggregated
sessions the PLAY_NOTIFY request MUST be using the aggregated control URI.

And for Scale-Change

PLAY_NOTIFY requests for aggregated sessions MUST use the aggregated
control URI in the request. The scale change for any aggregated session
do apply to all media streams part of the aggregate.



> 
> s13.5.2, para 2:
>> that changes the basis for making
>>    estimates on how the media range progress. 
> I can't parse the last part of this and I am not sure what it should be.

I hope this is better

This notification MUST be sent for media that are Time-Progressing every
time an event happens that changes the basis for making estimates on how
the available for play-back media range will progress with wall clock time.


> 
> s14: What happens if the upper layer PDU is longer than (2^16 - 1)?

I have added this note:

Note that this mechanism does not support larger PDUs than 65535 bytes,
which is the same that regular IPv4 and IPv6 is capable. If the media
delivery protocol intended to be used has larger PDUs than that, the
definition of such mechanisms usage of this mechanism will require the
definition of a PDU fragmentation mechanism.



> 
> s18.10, private para:  Is there any way in RTSP for the cache to know
> whether this is a private cache for the user that should cache this
> content?

To my understanding this is something the cache itself knows through its
behavior and deployment.


> s18.10, last para:  I am not absolutely certain, but I think this para
> is specific to the max-age cache type rather than being generic as
> implied by the indentation. [If so use the <vspace blankLines=1/> trick
> to provide a pseudo-paragraph break]

Yes, you are correct. I did the equally easy choice for hanging lists to
simply make a new paragraph without any paragraph text.

> s18.14: Consider adding the 'identity' value explicitly to the ABNF.

If I understand you correctly what you are requesting is that "identity"
is listed as an construct in the content-coding ABNF construction that
are used by Accept-Encoding and Content-Encoding headers.

Accept-Encoding   =  "Accept-Encoding" HCOLON
                     [ encoding *(COMMA encoding) ]
encoding          =  codings [SEMI accept-params]
codings           =  content-coding / "*"
content-coding    =  "identity" / token
Content-Encoding   =  "Content-Encoding" HCOLON
                      content-coding *(COMMA content-coding)


> 
> s18.29, para 2: Are (or should there be) constraints on the ordering of
> media ranges for a non-continuous media stream?  It would probably make
> the client's job easier if they were in incresing order. 

This is a interesting question. If one simply expresses what pieces of
media that are currently available then using a requirement that the
first ranges end-time must be prior any of the subsequent ranges start
times would work. However, my head gets stuck on considering when
desired playback is non linear. But that is probably a higher function
question.

So a possible addition after this existing sentence:

The server MAY include more than one range specification of any given
time format to indicate media that has non-continuous range.

would be:
The range specifications shall be ordered with the range with the lowest
value or earliest start time first, followed by ranges with increasingly
higher values or later start time.

Comments on this?

> s18.41: It appears from a literal interpretation (the third sentence is
> an unqualified MUST) that the responder has to respond with error code
> 551 and an (empty?) list of Unsupported features if it actually does
> support all the features.  I suspect this is not what is wanted.

Correct, reformulated proposal is:

In case any of the feature-tags listed by the Require header are not
supported by the server or client receiving the request, it MUST respond
to the request using the error code 551 (Option Not Supported) and
include  the Unsupported header listing those feature-tags which are NOT
supported.

> s18.45, para 4: Harummph! Political Correctness strikes again.  Every
> protocol should (and probably does) have a CRAP policy. ;-)

Yes, the lower case o is silent here ;-).


> 
> s18.52, 'setup' section:  There seems to be some inconsistency in the
> spcification of the 'active/passive/actpass' values.  a) Is there some
> reason for specifying them in square brackets?

Not, that I can remember. Removing both brackets and quotes.

 b) should they say
> ["active:"] or ["active":] - both formats are used?  The ABNF has the
> plain words with no brackets or quotes.

The later would be correct, but now it will only say
active: <description>

The ABNF is clear that it will be
RTP/SAVPF/TCP;unicast;setup=active;connection=new


> 
> 18.52, 'connection' section, 1st line:
> s/Clients use the setup parameter/Clients use the connection parameter/
> (I assume).

Had to tweak that sentence a bit more:

Clients use the connection parameter in a transport specification part
of the Transport header in a SETUP request, to indicate the client's
preference for either reusing an existing connection between client and
server (in which case the client sets the "connection" parameter to
"existing"), or requesting the creation of a new connection between
client and server (in which cast the client sets the "connection"
parameter to "new").



> 
> s21.1, transfer of sensitive info: Is there an equivalent of the Referer
> header in RTSP?  Not sure there is but it would be good to explain one
> way or the other (either there isn't one so it's less of a problem or
> this is the equivalent...)

Yes, the Referer header is retained also in RTSP.


> 
> s21.1, DNS Spoofing:  Presumably RTSP will interact significantly with
> content delivery networks.  Some of these work by DNS 'spoofing' that
> was in its infancy when RFC 2616 was published.  Are there any other
> issues that come out of the greater prevalence of CDNs since 1999?

I have no experience with large scale deployment of RTSP. To my
knowledge there hasn't been the same development with CDNs for RTSP as
HTTP. This I think is dependent on several factors. One has been the
issues with deploying RTSP on global scale due to NAT traversal etc,
instead progressive download and HTTP adaptive streaming has mostly
taken this market. Thus most large scale deployments has been in
contexts within single operators providing Video On Demand services etc.

Thus, I don't really know of any additional issues around this.


> 
> s21.1, Session Hijacking:  The last part of this is written so that it
> appears to mandate authentication in all cases.  As far as I understand
> it is up to the client to decide if it needs authentication etc and some
> content will be offered on unsecured URIs.  I think this needs to be
> clearer that authentication will mitigate the problem but whether it is
> done is up to the client if the server doesn't care.

Is this better?

Another choice for preventing session hijacking is to use client
authentication and only allow the authenticated client creating the
session to access that session.

> 
> s21.1, Persistently suspicious behaviour:  There seems to be a mismatch
> between the title (persistently..) and the first sentence (a single
> instance).  Do we have examples of the sort of security risk which is
> supposed to be met with a 403 response the first time?

Yes, it is a bit inconsistent. I propose:

Suspicious behavior: RTSP servers upon detecting intances of behavior
which is deemed a security risk SHOULD return error code 403
(Forbidden). RTSP servers SHOULD also be aware of attempts to probe the
server for weaknesses and entry points and MAY arbitrarily disconnect
and ignore further requests from clients which are deemed to be in
violation of local security policy.



> 
> s21.1, last sentence:
>>    Some of the above threats are such that
>>    the implementation of the RTSP functionality itself needs to consider
>>    which policy and strategy it uses to mitigate them.
> It strikes me that this is not very helpful to a prospective
> implementer.  The point of this section is at least in part to provide
> that policy and strategy.  I am not quite sure how to rewrite this (or
> if indeed other people think it does need rewriting). 

No, it is not helpful in other ways then, you need to think about this
and consider what mitigations you think should be implemented and how
that affects your implementation design.

For now I am leaving this as it is.



> s22.3:  The rules about allocating in the sections above x50 should be
> explained here (see s8.1.1).  The  numbers below x50 in each section
> should be marked as a special category of reserved so they are only
> allocated to HTTP analogues.  Is an experimental/private segment in each
> category desirable?   

Yes I think adding something like the below to at least make clear the
intention that RTSP specific status codes should first be registered in
the x50-x99 range.

New RTSP functionality requiring Status Codes should first be registered
in the range x50-x99. Only when the range is full should registrations
be done in the x00-x49 range, unless it is to adopt an HTTP extension
also to RTSP. The reason is to enable any HTTP extension to be adopted
to RTSP without needing to renumber any related status codes.


Regarding experimental and private I am very torn about such range.
Unless someone else in the WG thinks this is worth the work I will leave
it out.

> 
> s22.9: Being allowed to register new Range header formats will currently
> be restricted to times specified by NPT, SMPTE or UTC because no
> registry is defined for Accept-Ranges.  Is this what is intended?

No, the intention is that Range header format registry is shared between
Range and Accept-Ranges. However, I see the description is not clear on
this and needs to be amended.

I have sent a separate email on this.

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 magnus.westerlund@ericsson.com  Fri Aug 23 06:53:49 2013
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 A2CA911E817A; Fri, 23 Aug 2013 06:53:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.673
X-Spam-Level: 
X-Spam-Status: No, score=-103.673 tagged_above=-999 required=5 tests=[AWL=-0.874, BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_15=0.6, J_CHICKENPOX_43=0.6, J_CHICKENPOX_45=0.6, 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 NYp7vYN7diGQ; Fri, 23 Aug 2013 06:53:43 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 7B08211E81A4; Fri, 23 Aug 2013 06:53:42 -0700 (PDT)
X-AuditID: c1b4fb38-b7fcf8e0000062b8-46-5217696389fb
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id D8.D9.25272.36967125; Fri, 23 Aug 2013 15:53:39 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.20) by smtp.internal.ericsson.com (153.88.183.32) with Microsoft SMTP Server id 14.2.328.9; Fri, 23 Aug 2013 15:53:38 +0200
Message-ID: <52176998.5000101@ericsson.com>
Date: Fri, 23 Aug 2013 15:54:32 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Elwyn Davies <elwynd@folly.org.uk>
References: <1370477514.4596.9052.camel@mightyatom> <51C85D02.1050907@ericsson.com> <1372164466.4524.9526.camel@mightyatom>
In-Reply-To: <1372164466.4524.9526.camel@mightyatom>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrELMWRmVeSWpSXmKPExsUyM+JvjW5ypniQwa/TohYXvxxhtzh+YAe7 xdVXn1kspi5/zOLA4vH1ZDuLx5IlP5k8vlz+zBbAHMVlk5Kak1mWWqRvl8CVsXHLJKaCnWkV e3+sZm5gbA7oYuTkkBAwkfg1s4cRwhaTuHBvPVsXIxeHkMBRRonDs0+wQzjLGCVWzNjPClLF K6At0b5iAwuIzSKgKjHn2XF2EJtNwELi5o9GNhBbVCBYon37VzaIekGJkzOfgNWLCKhJbP76 gBFkKLNAN6PE7GcXmEASwgJhEvO2dIPZQgI1Es9a7oAN5QQ6b/2aJhaI8yQlti06BhZnFtCT mHK1hRHClpdo3jqbGaJXW6KhqYN1AqPQLCS7ZyFpmYWkZQEj8ypGjuLU4qTcdCODTYzAcD64 5bfFDsbLf20OMUpzsCiJ827ROxMoJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgVEna7bC54Pi b1ie1RdNKL/OtkpqJcsyVXf2t3qnN8/lZvZNmtqs9Xfqc8cFBjv2LznMyPnuUPv0WeqKTc85 jy9Vsq7aHdy0emWf6NZL8VWXf4dldUw/lm0XL5bnJXh2tp1vj0oXh51cTfmPXdJ7bfQLpW2b 7997HhHOblv2NWX95CDG/vZ7skosxRmJhlrMRcWJALC5bf81AgAA
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-mmusic-rfc2326bis.all@tools.ietf.org, "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [Gen-art] Gen-art additional LC review of draft-ietf-mmusic-rfc2326bis-34
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 23 Aug 2013 13:53:49 -0000

Hi,

Now getting to implement your response in our source.

Some few additional comments or notes below.

On 2013-06-25 14:47, Elwyn Davies wrote:
> 
> On Mon, 2013-06-24 at 16:51 +0200, Magnus Westerlund wrote:
>> Elwyn,
>>
>> Follow up on some of the nits that is not simply to implement or where I
>> disagree or want to provide feedback.
>>
>> This email covers all issues up to and including Section 11. That is as
>> far as I have managed to process them yet. I will now handle over the
>> rest of this list to my co-authors.
>>
>> On 2013-06-06 02:11, Elwyn Davies wrote:




>>>
>>>
>>> ss4.4/4.5/4.6: If I read the ABNF in s20.2.1 correctly, the unqualified 
>>> values "smpte", "npt" and "clock" are valid  in the Range parameter.  
>>> What is the meaning of such an unqualified value?
>>
>> You are correct about that the basic definition in ABNF allows for
>> empty. The reason for this is the following stated in Section 18.38:
>>
>>     It MAY be
>>    included in GET_PARAMETER requests from the client to the server with
>>    only a Range format and no value to request the current media
>>    position, whether the session is in Play or Ready state in the
>>    included format.
>>
> Two points:
> - A suggestion: Make ss4.4/4.5/4.6 into subsections of a new s4.4.  Add
> a bit of text in the new s4.4 saying that the range specifiers are used
> in the RANGE header and pointing to s18.38 for the unqualified use.
> (consistent with s2.7 which gives usage).
> - An issue I hadn't spotted: I haven't checked but are the unqualified
> values allowed in the SDP extension case (s20.3)?
>>
>>

I think your suggestion is a good one and I have written such a section,
initial proposal below:

4.4.  Media Time Formats

   RTSP currently supports three different media time formats defined
   below.  Additional time formats may be specified in the future.
   These time formats can be used with the Range header (Section 18.38)
   to request playback and specify at which media position protocol
   requests actually will or has taken place.  They are also used in
   description of the media's properties using the Media-Range header
   (Section 18.29).  The format identifier only are used in Accept-
   Ranges header (Section 18.5) to declare supported time formats and
   also in the Range header (Section 18.38) to request the time format
   used in the response.

4.4.1.  SMPTE Relative Timestamps


Regarding the SDP a=range attribute. The ABNF allows the unqualified
usage. The textual specification of a=range attribute in D.1.6 is silent
on unqualified usage.

The only usage of unqualified usage in a=range would be to indicate that
although this media has unknown or time-progressing properties it does
support the time formats for the a=range with unqualified values that
has been included.



>>
>>>
>>> s10.2, para 6 and following note:  I can't see that the note following 
>>> para 6 can be justified: since the restriction on multiple connections 
>>> from a client to a server is only a SHOULD, an interoperable server MUST 
>>> be capable of handling multiple connections from a client unless the 
>>> server can explicitly send back a TOO MANY CONNECTIONS status.
>>
>> See separate email
> 
> Should I have had this already?

It was sent to the MMUSIC WG mailing list on the 24th of June. I have
forwarded if to you personally.

> 
>>
>>>
>>> s10.6: RFC 3986 has capability for dealing with IP versions beyond 6... 
>>> should these be carried over into RTSP?  The IANA registry says they are.
>>
>> I am uncertain what you want here? Yes, the URI format allows for future
>> definitions of literal IP address versions. However, RTSP does contain
>> explicit IPv4 and IPv6 address fields that aren't URIs. Thus, future IP
>> versions will require some extension definition to function.
> 
> Perhaps an excess of zeal on my behalf.  Perhaps a (non-normative) note
> saying what you just wrote: 'Although the general URI format envisages 
> potential future new versions of the literal IP address, usage of any
> such new version would require other modifications to the RTSP
> specofication (e.g., ...[any relevant section(s)]).' 

Yes, I added such text.


>>
>>>
>>> s10.7, last para: Should the doubling of the wait timer have an upper limit?
>>
>> Yes, I added an upper limit of 30 minutes. This is way beyond what any
>> human will accept, only robots will keep on going at this timeout value.
>> And I think that is large enough to avoid any issues.
> 
> Agreed
> 
>>
>> I also propose to clarify the range for the variations and added the
>> classical 0.5 to 1.5 times the deterministic value.
>>
>> Text proposal.
>>
>> That timer MUST be doubled for each additional failure to connect or
>> receive response until the value exceeds 30 minutes when the timers
>> deterministic value may be set to 30 minutes. It is RECOMMENDED to not
>   ^^^^^^^^^^^^^
>   base?
>> set the same value in the timer for each scheduling, but instead to add
>> a variation to the mean value, resulting in picking a random value
>> within the range of 0.5 to 1.5 of the mean value.

This has gotten changed a bit more and currently reads:

A more complex case may arise when a load balancing RTSP proxy is in
use, i.e., where an RTSP proxy is used to select amongst a set of RTSP
servers to handle the requests, or when multiple server addresses are
available for a given server name. The proxy or client may receive a 503
(Service Unavailable) or 553 (Proxy Unavailable) from one of its RTSP
servers or proxies, or a TCP timeout (if the server is even unable to
handle the request message). The proxy or client simply retries the
other addresses or configured proxies, but may also receive a 503
(Service Unavailable) or 553 (Proxy Unavailable) response or TCP
timeouts from those addresses. In such a situation, where none of the
RTSP servers/proxies/addresses can handle the request, the RTSP agent
has to wait before it can send any new requests to the RTSP server. Any
additional request to a specific address MUST be delayed according to
the Retry-After headers received. For addresses where no response was
received or TCP timeout occurred, an initial wait timer SHOULD be set to
5 seconds. That timer MUST be doubled for each additional failure to
connect or receive response until the value exceeds 30 minutes when the
timers mean value may be set to 30 minutes. It is REQUIRED to not set
the same value in the timer for each scheduling, but instead to add a
variation to the mean value, resulting in picking a random value within
the range of 0.5 to 1.5 of the mean value.


>>
>>>
>>> s11, para 4: According to s22.1.3, play.basic, play.scale and play.speed
>>> are 'defined' in this draft.  The nearest thing to a definition of
>>> play.basic that I can find is the last sentence of para 4 in this
>>> section.  I am not convinced that I could produce an interoperable
>>> implementation of a server with this feature-tag with the one sentence
>>> 'definition'.  References to where play.xxx are defined would be useful
>>> (play.scale in s18.44, play.speed in s18.48).
>>>
>>
>> Hmmm, the other feature-tags than play.basic are pretty straightforward
>> and well contained. play-basic is really a minimal RTSP server
>> implementation according to the whole spec for media playback.
>>
>> This can probably be more clearly expressed somewhere, but it can't
>> really be enumerated. Then we are back to the issue we had with RFC 2326
>> minimal implementation list that was incomplete and lacked a lot of
>> things really necessary.
>>
>> This issue still haven't resulted in any changes to our source.
> 
> Ah!  I see I have (re-)opened a can of worms!  One thought for providing
> the proverbial larger can into which the worms can be stuffed back:
> 
> Define 'play.basic' as the default that you get back if none of the
> others apply.  How's that for weasel words!

After my leave I have written a bit of definition for play.basic:

11.1.  Feature Tag: play.basic

   The play.basic feature tag represents an RTSP implementation
   according to all normative RTSP protocol features specified in this
   specification.  This specification is both a RTSP core specification
   as well intended to enable setup and control of playback of media.
   Thus following all normative parts in the main sections (the ones
   with numbers), not the appendices (starting with letters), unless
   explicitly specified in a main section for being a required appendix.

      Note: This feature tag does not mandate any media delivery
      protocol, such as RTP.

      In RTSP 1.0 there was a minimal implementation section.  However,
      that was not consistent with the rest of the specification.  So
      rather than making an attempt to explicitly enumerate the features
      for play.basic this specification have to be read in completeness
      and the necessary features normatively defined as being required
      are included.

>>
>>
>>> s11, Supported (and Proxy-Supported) bullets: 
>>> OLD:
>>>          This results in the
>>>          receiver is learning the requester's feature support.
>>> NEW:
>>>          This results in the
>>>          receiver learning the requester's feature support 
>>>          relevant to the specified resource.
>>> [Note: I added 'specified resource' here and then thought about whether
>>> this made any sense.  It probably needs to be clearer what set of
>>> features are included in the Supported list for both requester and
>>> responder.  Are they restricted to those relevant to the specified
>>> resource that might of course be the whole server, proxy - or client?? -
>>> in which case there isn't an issue, but it might be a specific
>>> presentation - what happens then?  Affects s13.1, para 3 also.]
>>
>> Actually, I don't think it is specific to the media resource. The issue
>> with making it specific to a media resource is that a RTSP client needs
>> to be able to look into the future and supply an answer for a media
>> resource it may not yet know sufficient to provide a tailored response
>> for. I think it is simpler and better to provide general capabilities in
>> the supported header and then later determine how well they apply for
>> the media resource itself.
> 
> So maybe make it clear that feature support returned is just what the
> responder can do generally and is not specific to the URI provided.

Yes, I have tried to make it clear that it is not resource specific.

   Supported:  This header is used to determine the complete set of
         functionality that both client and server have in general and
         is not dependent on specific resource.  The intended usage is
         to determine before one needs to use a functionality that it is
         supported.  It can be used in any method, but OPTIONS is the
         most suitable one as it at the same time determines all methods
         that are implemented.  When sending a request the requester
         declares all its capabilities by including all supported
         feature-tags.  This results in the receiver is learning the
         requester's feature support.  The receiver then includes its
         set of features in the response.

   Proxy-Supported:  This header is used similarly to the Supported
         header, but instead of giving the supported functionality of
         the client or server it provides both the requester and the
         responder a view of the common functionality supported in
         general by all members of the proxy chain between the two
         supports and not dependent on the resource.  Proxies are
         required to add this header whenever the Supported header is
         present, but proxies may also add it independently of the
         requester.

I also added variations of this sentence to the Supported and
Proxy-Supported headers description:

These feature tags are the ones the server or client support in general,
and is not specific to the request resource.

> 
> Either that or make the request valid only for non-specific URIs (i.e.
> at the server/client level) if that is possible (not sure how that would
> work for server asking client if that is allowed).

Doesn't really work as supported is intended to be possible to add to
any request to determine the functionality supported by the replying agent.

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 housley@vigilsec.com  Fri Aug 23 19:50:03 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D2F421F9D7C; Fri, 23 Aug 2013 19:50:03 -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 3YANx2EIJFik; Fri, 23 Aug 2013 19:49:58 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 121EF21F9D8B; Fri, 23 Aug 2013 19:49:58 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 9BC06F240A5; Fri, 23 Aug 2013 22:50:16 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 9paTfNS7gMGK; Fri, 23 Aug 2013 22:49:55 -0400 (EDT)
Received: from [192.168.0.8] (75-139-113-21.dhcp.mant.nc.charter.com [75.139.113.21]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id EECE4F240A1; Fri, 23 Aug 2013 22:50:14 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 23 Aug 2013 22:49:53 -0400
Message-Id: <5C6D74D1-CA25-4EA9-8ABC-AB85D2789969@vigilsec.com>
To: draft-ietf-ccamp-gmpls-g709-framework.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IETF Gen-ART <gen-art@ietf.org>, IESG <iesg@ietf.org>
Subject: [Gen-art] Gen-ART Review of draft-ietf-ccamp-gmpls-g709-framework-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: Sat, 24 Aug 2013 02:50:03 -0000

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

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

Document: draft-ietf-ccamp-gmpls-g709-framework-14
Reviewer: Russ Housley
Review Date: 2013-08-23
IETF LC End Date: 2013-09-02
IESG Telechat date: Unknown

Summary:  The document is almost ready for publication as a
informational RFC.  I raise minor concerns that should be resolved
before IESG evaluation.

Minor Concerns:  

In section 3, there is a discussion that includes ODU0, ODU2e, and ODU4,
but these terms are not defined in the paragraph or in the terminology
section.  I realize that these are ODUj values, but ODUflex is an ODUj,
and it is included in the terminology section.

In section 3.1, OCh needs to be defined or at least expanded.

In section3.1.2.1, please expand MSI on first use.


Editorial:

In section 8: s/not requests/no requests/

From adrian@olddog.co.uk  Sat Aug 24 00:38:49 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 641EF21F9C13; Sat, 24 Aug 2013 00:38:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.037,  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 EKKAsJNELacq; Sat, 24 Aug 2013 00:38:43 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 5156F21F9B25; Sat, 24 Aug 2013 00:38:41 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7O7cavf014255;  Sat, 24 Aug 2013 08:38:36 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7O7cZkp014249 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 24 Aug 2013 08:38:35 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Russ Housley'" <housley@vigilsec.com>, <draft-ietf-ccamp-gmpls-g709-framework.all@tools.ietf.org>
References: <5C6D74D1-CA25-4EA9-8ABC-AB85D2789969@vigilsec.com>
In-Reply-To: <5C6D74D1-CA25-4EA9-8ABC-AB85D2789969@vigilsec.com>
Date: Sat, 24 Aug 2013 08:38:34 +0100
Message-ID: <059701cea09c$f1436030$d3ca2090$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIQAX6+WncaIGGCHxDmtq/bNkzKupkhNZyw
Content-Language: en-gb
Cc: 'IETF Gen-ART' <gen-art@ietf.org>, 'IESG' <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-ccamp-gmpls-g709-framework-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Aug 2013 07:38:49 -0000

Thanks Russ!

> Minor Concerns:
> 
> In section 3, there is a discussion that includes ODU0, ODU2e, and ODU4,
> but these terms are not defined in the paragraph or in the terminology
> section.  I realize that these are ODUj values, but ODUflex is an ODUj,
> and it is included in the terminology section.

 I think these are covered in the Terminology section in the two paragraphs 

   LO ODU: Lower Order ODU. The LO ODUj (j can be 0, 1, 2, 2e, 3, 4,
   flex.) represents the container transporting a client of the OTN that
   is either directly mapped into an OTUk (k = j) or multiplexed into a
   server HO ODUk (k > j) container.

   HO ODU: Higher Order ODU. The HO ODUk (k can be 1, 2, 2e, 3, 4.)
   represents the entity transporting a multiplex of LO ODUj tributary
   signals in its OPUk area.

For ease of searching, I suppose this could read

OLD
(j can be 0, 1, 2, 2e, 3, 4, flex.)
NEW
(j can be 0, 1, 2, 2e, 3, 4, flex yielding ODU0, ODU1, ODU2e, ODU3, ODU4, and
ODUflex)
END

Seems a bit excessive, but if it would help the reader.

> In section 3.1, OCh needs to be defined or at least expanded.

OCh is found in the last paragraph of Section 1

   For the purposes of the control plane the OTN can be considered as
   being comprised of ODU and wavelength (Optical Channel (OCh)) layers.
   This document focuses on the control of the ODU layer, with control
   of the wavelength layer considered out of the scope. Please refer to
   [RFC6163] for further information about the wavelength layer.

> In section3.1.2.1, please expand MSI on first use.

MSI is in the terminology section 

   MSI: Multiplex Structure Identifier

> Editorial:
> 
> In section 8: s/not requests/no requests/

Yes.

Cheers,
Adrian


From dromasca@avaya.com  Sun Aug 25 03:23:55 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C712B21F898A for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 03:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.804
X-Spam-Level: 
X-Spam-Status: No, score=-102.804 tagged_above=-999 required=5 tests=[AWL=-0.205, 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 UMN0lx-7KUDn for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 03:23:50 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 5402F21F89A6 for <gen-art@ietf.org>; Sun, 25 Aug 2013 03:23:50 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq8LAObZGVKHCzI1/2dsb2JhbABZgmYhNVGrYZQzgRoWbQeCJgEBAxIoPxIBFQcOFEImAQQODRqHXwELmgecK5BHMYMjfQOZG4UkixCDHoIq
X-IronPort-AV: E=Sophos;i="4.89,951,1367985600"; d="scan'208";a="25459037"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 25 Aug 2013 06:23:49 -0400
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 25 Aug 2013 06:16:25 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0146.000; Sun, 25 Aug 2013 12:23:47 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Review for draft-ietf-storm-iscsimib-04 
Thread-Index: Ac6hfS7eXeeB2ah1R5G89ugF+QAx4A==
Date: Sun, 25 Aug 2013 10:23:47 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA128B7362@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-storm-iscsimib.all@ietf.org" <draft-ietf-storm-iscsimib.all@ietf.org>
Subject: [Gen-art] Gen-ART Review for draft-ietf-storm-iscsimib-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, 25 Aug 2013 10:23:55 -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/Ge=
nArtfaq>.

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

Document: draft-ietf-storm-iscsimib-04.txt
Reviewer: Dan Romascanu
Review Date: 8/25/13
IETF LC End Date: 1/28/13
IESG Telechat date: 8/29/13

Summary: Ready - All issues raised in the IETF LC review were addressed. Th=
anks to the authors for the responsiveness and cooperation.=20

Major issues:

Minor issues:

Nits/editorial comments:


From dromasca@avaya.com  Sun Aug 25 03:25:05 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CAAA21F9D0A for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 03:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.804
X-Spam-Level: 
X-Spam-Status: No, score=-102.804 tagged_above=-999 required=5 tests=[AWL=-0.205, 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 vP7hoVIkxR4E for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 03:25:05 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id D87B321F89A6 for <gen-art@ietf.org>; Sun, 25 Aug 2013 03:25:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq8LABvbGVKHCzI1/2dsb2JhbABZgmYhNVGrYZQzgRoWbQeCJgEBAxIoPxIBFQcOFEImAQQODRqHXwELmgucK5BHMYMjfQOZG4UkixCDHoIq
X-IronPort-AV: E=Sophos;i="4.89,951,1367985600"; d="scan'208";a="25459091"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 25 Aug 2013 06:25:04 -0400
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 25 Aug 2013 06:17:40 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0146.000; Sun, 25 Aug 2013 12:25:03 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Review for draft-ietf-storm-iscsimib-04 
Thread-Index: Ac6hfS7eXeeB2ah1R5G89ugF+QAx4A==
Date: Sun, 25 Aug 2013 10:25:02 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA128B737E@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-storm-iscsimib.all@tools.ietf.org" <draft-ietf-storm-iscsimib.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART Review for draft-ietf-storm-iscsimib-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, 25 Aug 2013 10:25:05 -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/Ge=
nArtfaq>.

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

Document: draft-ietf-storm-iscsimib-04.txt
Reviewer: Dan Romascanu
Review Date: 8/25/13
IETF LC End Date: 1/28/13
IESG Telechat date: 8/29/13

Summary: Ready - All issues raised in the IETF LC review were addressed. Th=
anks to the authors for the responsiveness and cooperation.=20

Major issues:

Minor issues:

Nits/editorial comments:


From dromasca@avaya.com  Sun Aug 25 04:29:26 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F116B21F9C68 for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 04:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.297
X-Spam-Level: 
X-Spam-Status: No, score=-103.297 tagged_above=-999 required=5 tests=[AWL=0.302, 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 6E+SyKnC6jbt for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 04:29:21 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 56FBC21F9C60 for <gen-art@ietf.org>; Sun, 25 Aug 2013 04:29:21 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq8LAJfpGVKHCzI1/2dsb2JhbABZgmYhNVGrYZQzgRoWbQeCJgEBAxIoPxIBFQcOFEImAQQODRqHXwELmXmcKpBHMYMjfQOZG4UkixCDHoIq
X-IronPort-AV: E=Sophos;i="4.89,951,1367985600"; d="scan'208";a="21229853"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 25 Aug 2013 07:29:19 -0400
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 25 Aug 2013 07:21:54 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0146.000; Sun, 25 Aug 2013 07:29:17 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-dhc-dhcpv6-solmaxrt-update-03
Thread-Index: Ac6hhlVUdvoB/lq5S0+dyAesAOqvsQ==
Date: Sun, 25 Aug 2013 11:29:17 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA128B73AA@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-dhc-dhcpv6-solmaxrt-update.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-solmaxrt-update.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-solmaxrt-update-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 11:29:27 -0000

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document: draft-ietf-dhc-dhcpv6-solmaxrt-update-03
Reviewer: Dan Romascanu
Review Date: 8/25/13
IETF LC End Date: 9/3/13
IESG Telechat date: (if known)

Summary: Ready with minor issues

Major issues: None

Minor issues:

1. My understanding is that although the default values of SOL_MAX_RT and I=
NF_MAX_RT were the same in RFC 3315, and now they are change to similar val=
ues, there is no mandatory behavior defined for servers to set them at the =
same values using the new override options. If this is the case then the Ab=
stract should say=20

OLD:=20

... override the client's default value for SOL_MAX_RT
   and INF_MAX_RT with a new value.

NEW:=20

... override the client's default value for SOL_MAX_RT
   and INF_MAX_RT with new values.

If I am wrong, and the values of the two parameters are always identical at=
 defalult or after changes, then something needs to be said on this respect=
 in Section 8 (DHCPv6 Server Behavior)

2. This is not a document problem but a WG management issue. I could not fi=
nd anything in the dhc WG charter that corresponds to this document, so I c=
annot say whether this document meets the conditions of the 'contract with =
the IESG'. Actually the charter seems not to have been updated for five yea=
rs, if not more. I guess that with Ralph as an author all is OK, but an upd=
ate of the charter seems to be needed.=20
=20

Nits/editorial comments:

Section 7:=20

OLD:

   a DHCPv6 client MUST silently ignore any SOL_MAX_RT or INF_MAX_RT
   values that are less than 60 or more than 86400.


New:

   A DHCPv6 client MUST silently ignore any SOL_MAX_RT or INF_MAX_RT
   values that are less than 60 or more than 86400.


Regards,

Dan


From rdroms.ietf@gmail.com  Sun Aug 25 05:27:46 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCA3321F9CA9 for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 05:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level: 
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 7NsWLKPbKIqT for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 05:27:46 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 59A9821F9CA0 for <gen-art@ietf.org>; Sun, 25 Aug 2013 05:27:46 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id f4so3551256iea.9 for <gen-art@ietf.org>; Sun, 25 Aug 2013 05:27:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=o/AV+qiFh7LgLz05dzozwVOAgRf7pO7VV25suV9rlI8=; b=gaFGzpclzx2Jdn+NmAVUQ3C/A3uzZmaAIdCLVXSCKNqoURZoqI1xM5NKSIRFtsZ5x5 +lDJRSRBJ5/xHu4SwHAE8HcY3oN3fvAbMacTDyt1wa797g4jc2iUcYez7W7NbazOw4Tr WB3qvBP15yvE1n9f0j1NsusUKNqUr8mVratf/4/cQnQCu3ZGWQ4I1xXEw722GApz7SEv imQzk+6s/FroYmPOdMJoZY0Rb8Ty9dcycUee0172nSgR3d/craP6VYUi9frN1wj+jzDo EqZDRvIbLNMKgloWl7GBUei1Uqqac+wqcl6waB/rXNsDZ2XgxinGwoMwtepJ6VLH+mDR IBVA==
X-Received: by 10.50.36.5 with SMTP id m5mr3656452igj.3.1377433665716; Sun, 25 Aug 2013 05:27:45 -0700 (PDT)
Received: from [10.202.201.102] ([166.137.85.123]) by mx.google.com with ESMTPSA id pk8sm10615541igb.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 25 Aug 2013 05:27:44 -0700 (PDT)
References: <9904FB1B0159DA42B0B887B7FA8119CA128B73AA@AZ-FFEXMB04.global.avaya.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA128B73AA@AZ-FFEXMB04.global.avaya.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E001FAA-9EB7-4609-B3BA-B0E231C8DC95@gmail.com>
X-Mailer: iPhone Mail (10B350)
From: Ralph Droms <rdroms.ietf@gmail.com>
Date: Sun, 25 Aug 2013 08:27:42 -0400
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-solmaxrt-update.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-solmaxrt-update.all@tools.ietf.org>, dhc-chairs@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-solmaxrt-update-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 12:27:47 -0000

Dan - thanks for your review.

On Aug 25, 2013, at 7:29 AM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> wro=
te:

>=20
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on Gen-A=
RT, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments you m=
ay receive.
>=20
> Document: draft-ietf-dhc-dhcpv6-solmaxrt-update-03
> Reviewer: Dan Romascanu
> Review Date: 8/25/13
> IETF LC End Date: 9/3/13
> IESG Telechat date: (if known)
>=20
> Summary: Ready with minor issues
>=20
> Major issues: None
>=20
> Minor issues:
>=20
> 1. My understanding is that although the default values of SOL_MAX_RT and I=
NF_MAX_RT were the same in RFC 3315, and now they are change to similar valu=
es, there is no mandatory behavior defined for servers to set them at the sa=
me values using the new override options. If this is the case then the Abstr=
act should say=20
>=20
> OLD:=20
>=20
> ... override the client's default value for SOL_MAX_RT
>   and INF_MAX_RT with a new value.
>=20
> NEW:=20
>=20
> ... override the client's default value for SOL_MAX_RT
>   and INF_MAX_RT with new values.
>=20
> If I am wrong, and the values of the two parameters are always identical a=
t defalult or after changes, then something needs to be said on this respect=
 in Section 8 (DHCPv6 Server Behavior)

Dan, your understanding that SOL_MAX_RT and INF_MAX_RT are allowed to have i=
ndependent values is correct.  The document originally addressed SOL_MAX_RT a=
nd I missed  the text you cite when I updated the doc to include INF_MAX_RT.=
  I'll make your suggested changes in the next rev of the doc.



>=20
> 2. This is not a document problem but a WG management issue. I could not f=
ind anything in the dhc WG charter that corresponds to this document, so I c=
annot say whether this document meets the conditions of the 'contract with t=
he IESG'. Actually the charter seems not to have been updated for five years=
, if not more. I guess that with Ralph as an author all is OK, but an update=
 of the charter seems to be needed.=20
>=20

In my opinion, this document falls under the following clause of the dhc WG c=
harter:

   However, the DHC WG can in some cases develop its own options that=20
relate to either maintenance of existing specifications or=20
   improvements in the operation of the DHCP infrastructure itself.

Regarding the charter more generally, the WG is currently in the process of r=
echartering.

Tomek and Bernie can add detail or correct me...

>=20
> Nits/editorial comments:
>=20
> Section 7:=20
>=20
> OLD:
>=20
>   a DHCPv6 client MUST silently ignore any SOL_MAX_RT or INF_MAX_RT
>   values that are less than 60 or more than 86400.
>=20
>=20
> New:
>=20
>   A DHCPv6 client MUST silently ignore any SOL_MAX_RT or INF_MAX_RT
>   values that are less than 60 or more than 86400.

Thanks for catching that typo.

>=20
>=20
> Regards,
>=20
> Dan

- Ralph

>=20

From volz@cisco.com  Sun Aug 25 05:57:12 2013
Return-Path: <volz@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7893521F9C3A for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 05:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 jSTTkIfQToZE for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 05:57:07 -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 28D4221F9CC0 for <gen-art@ietf.org>; Sun, 25 Aug 2013 05:57:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3832; q=dns/txt; s=iport; t=1377435427; x=1378645027; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=R1WpMqzkXvR7TjsdfsYL403gh9brfj+55vXyBZYTV1k=; b=R3/vdlw+MQgu5uL6x1JKfOtbLtIFCtYucihkzI2duFVDIa0P78Acgu3E 5UCyn43/lDt4MQqjdjJwXKA5A4Z4FPaAuAstEdZP8J9CVfjVWffzXCczU NceCj/omvOljSLsfxMC344h8t3VGCG2m+REalf6HOLH37WIkB9poMVeo/ Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAP/9GVKtJXG8/2dsb2JhbABZgwc1UcAVgRoWdIIkAQEBAwE6PwwEAgEIDgMDAQEBCxQJByERFAkIAQEEDgUIh2cDCQYMrDYNiWqNf4JIMQcGgxZ9A5YFgxaLCIUsgx6CKg
X-IronPort-AV: E=Sophos;i="4.89,951,1367971200"; d="scan'208";a="248370735"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-9.cisco.com with ESMTP; 25 Aug 2013 12:57:05 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r7PCv5pq014465 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 25 Aug 2013 12:57:05 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.201]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.004; Sun, 25 Aug 2013 07:57:05 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ralph Droms <rdroms.ietf@gmail.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Thread-Topic: Gen-ART review of draft-ietf-dhc-dhcpv6-solmaxrt-update-03
Thread-Index: Ac6hhlVUdvoB/lq5S0+dyAesAOqvsQAMhIAAAAmI5wA=
Date: Sun, 25 Aug 2013 12:57:04 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E186AB8EE@xmb-rcd-x04.cisco.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA128B73AA@AZ-FFEXMB04.global.avaya.com> <0E001FAA-9EB7-4609-B3BA-B0E231C8DC95@gmail.com>
In-Reply-To: <0E001FAA-9EB7-4609-B3BA-B0E231C8DC95@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.252.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dhc-dhcpv6-solmaxrt-update.all@tools.ietf.org" <draft-ietf-dhc-dhcpv6-solmaxrt-update.all@tools.ietf.org>, "dhc-chairs@tools.ietf.org" <dhc-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dhc-dhcpv6-solmaxrt-update-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 12:57:12 -0000

We are in the process of re-chartering. (Whether this document is included =
in that new charter will depend on timing as it would be unnecessary to inc=
lude it if it is already 'done'.)=20

The draft proposed rechartering (which has some minor updates since then), =
is at http://datatracker.ietf.org/doc/charter-ietf-dhc/ and does include SO=
LMAXRT work.

- Bernie

-----Original Message-----
From: Ralph Droms [mailto:rdroms.ietf@gmail.com]=20
Sent: Sunday, August 25, 2013 8:28 AM
To: Romascanu, Dan (Dan)
Cc: gen-art@ietf.org; draft-ietf-dhc-dhcpv6-solmaxrt-update.all@tools.ietf.=
org; dhc-chairs@tools.ietf.org
Subject: Re: Gen-ART review of draft-ietf-dhc-dhcpv6-solmaxrt-update-03

Dan - thanks for your review.

On Aug 25, 2013, at 7:29 AM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> wr=
ote:

>=20
>=20
> 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>.
>=20
> Please resolve these comments along with any other Last Call comments you=
 may receive.
>=20
> Document: draft-ietf-dhc-dhcpv6-solmaxrt-update-03
> Reviewer: Dan Romascanu
> Review Date: 8/25/13
> IETF LC End Date: 9/3/13
> IESG Telechat date: (if known)
>=20
> Summary: Ready with minor issues
>=20
> Major issues: None
>=20
> Minor issues:
>=20
> 1. My understanding is that although the default values of SOL_MAX_RT=20
> and INF_MAX_RT were the same in RFC 3315, and now they are change to=20
> similar values, there is no mandatory behavior defined for servers to=20
> set them at the same values using the new override options. If this is=20
> the case then the Abstract should say
>=20
> OLD:=20
>=20
> ... override the client's default value for SOL_MAX_RT
>   and INF_MAX_RT with a new value.
>=20
> NEW:=20
>=20
> ... override the client's default value for SOL_MAX_RT
>   and INF_MAX_RT with new values.
>=20
> If I am wrong, and the values of the two parameters are always=20
> identical at defalult or after changes, then something needs to be=20
> said on this respect in Section 8 (DHCPv6 Server Behavior)

Dan, your understanding that SOL_MAX_RT and INF_MAX_RT are allowed to have =
independent values is correct.  The document originally addressed SOL_MAX_R=
T and I missed  the text you cite when I updated the doc to include INF_MAX=
_RT.  I'll make your suggested changes in the next rev of the doc.



>=20
> 2. This is not a document problem but a WG management issue. I could not =
find anything in the dhc WG charter that corresponds to this document, so I=
 cannot say whether this document meets the conditions of the 'contract wit=
h the IESG'. Actually the charter seems not to have been updated for five y=
ears, if not more. I guess that with Ralph as an author all is OK, but an u=
pdate of the charter seems to be needed.=20
>=20

In my opinion, this document falls under the following clause of the dhc WG=
 charter:

   However, the DHC WG can in some cases develop its own options that relat=
e to either maintenance of existing specifications or=20
   improvements in the operation of the DHCP infrastructure itself.

Regarding the charter more generally, the WG is currently in the process of=
 rechartering.

Tomek and Bernie can add detail or correct me...

>=20
> Nits/editorial comments:
>=20
> Section 7:=20
>=20
> OLD:
>=20
>   a DHCPv6 client MUST silently ignore any SOL_MAX_RT or INF_MAX_RT
>   values that are less than 60 or more than 86400.
>=20
>=20
> New:
>=20
>   A DHCPv6 client MUST silently ignore any SOL_MAX_RT or INF_MAX_RT
>   values that are less than 60 or more than 86400.

Thanks for catching that typo.

>=20
>=20
> Regards,
>=20
> Dan

- Ralph

>=20

From brian.e.carpenter@gmail.com  Sun Aug 25 13:50:23 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E3A321F9F62 for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 13:50:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, 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 FmuNtXNmxekf for <gen-art@ietfa.amsl.com>; Sun, 25 Aug 2013 13:50:22 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id A379E21F9E5C for <gen-art@ietf.org>; Sun, 25 Aug 2013 13:50:22 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id bg4so2630338pad.18 for <gen-art@ietf.org>; Sun, 25 Aug 2013 13:50:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=ZQJ8bUQ5kGIrv4r38/v5aaVuOeAsHfSQ4ZiOV8Mgq5I=; b=aSIcW/R9LhOzNg12GQedQVixq6CymafFVVi9IscqhlBlCBO7U6R14nZBWSWz2nMbHd iwOb6TsokN7DCJnBhJ5mL1ewZxBFiiVzlfqq7xxCCY6pe8c6IgvkBuFfq4AOL+A8oYGg ON3WInuubj7Keb2wwUwQ84QvCGtfgwv618FS17KcFcZ/0K54/U1d/iL2vu8Wt2avF0XX ttCBmwf0NACBqrHWWJASA74F0FZ5l9NJgv4YNoRR1ihTTTVNTdcc131MdrQTvGeQqIOB KrBM1M9QSRg81zgg9o5ks1pLM2RiS/2nADf6Et5PCsA1lBEqLM8qxJ8Qb2Ebq1SqTdcY DTTg==
X-Received: by 10.68.162.36 with SMTP id xx4mr11538944pbb.47.1377463809912; Sun, 25 Aug 2013 13:50:09 -0700 (PDT)
Received: from [192.168.178.20] (63.199.69.111.dynamic.snap.net.nz. [111.69.199.63]) by mx.google.com with ESMTPSA id xe9sm13625327pbc.21.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 25 Aug 2013 13:50:09 -0700 (PDT)
Message-ID: <521A6DF9.8030702@gmail.com>
Date: Mon, 26 Aug 2013 08:50:01 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-mediactrl-call-flows.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART LC review of draft-ietf-mediactrl-call-flows-13.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 20:50: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-mediactrl-call-flows-13.txt (Informational)
Reviewer: Brian Carpenter
Review Date: 2013-08-26
IETF LC End Date: 2013-09-13
IESG Telechat date:

Summary:  Ready
--------

Comment:
--------

This is a massive (175pp) and highly specialised document, for which a generalist
review is pretty much useless. I have not checked the example flows, XML extracts, etc.
IMHO, we have to trust the authors and the WG in a case like this.

The document is clear and where I have sampled the text in the examples it is
up to standard.

Editorial:
----------

There are a few abbreviations (AS, MS, CFW) that could usefully be included
in the Terminology section.

Also, AS is widely used in the IETF to mean Autonomous System. Some readers
might be confused at first, so this should be stated very clearly.

"Mealy automaton" (section 4.1) needs a reference. Or it might be sufficient
just to say "finite state automaton."

From vkg@bell-labs.com  Mon Aug 26 08:27:47 2013
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE4B911E81A2 for <gen-art@ietfa.amsl.com>; Mon, 26 Aug 2013 08:27:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.186
X-Spam-Level: 
X-Spam-Status: No, score=-110.186 tagged_above=-999 required=5 tests=[AWL=0.413, 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 WzVhIJ2LzThg for <gen-art@ietfa.amsl.com>; Mon, 26 Aug 2013 08:27:42 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 4926311E8193 for <gen-art@ietf.org>; Mon, 26 Aug 2013 08:27:42 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r7QFRdpB023063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 26 Aug 2013 10:27:39 -0500 (CDT)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r7QFRc7D022349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 26 Aug 2013 10:27:38 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r7QFRbsr028010; Mon, 26 Aug 2013 10:27:38 -0500 (CDT)
Message-ID: <521B7507.6000706@bell-labs.com>
Date: Mon, 26 Aug 2013 10:32:23 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version: 1.0
To: draft-ietf-ccamp-gmpls-signaling-g709v3@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: Adrian Farrel <adrian@olddog.co.uk>, General Area Review Team <gen-art@ietf.org>, Lou Berger <lberger@labn.net>, dbrungard@att.com
Subject: [Gen-art] Gen-ART review of draft-ietf-ccamp-gmpls-signaling-g709v3-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: Mon, 26 Aug 2013 15:27:47 -0000

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

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

Document: draft-ietf-ccamp-gmpls-signaling-g709v3-11
Reviewer: Vijay K. Gurbani
Review Date: Aug-26-2013
IETF LC End Date: Unknown
IESG Telechat date: Unknown

This document is ready as an Proposed Standard.

Major: 0
Minor: 0
Nits: 1

Nits:

- S1, first paragraph: Expand "OTN" on first use.  Also,
  s/provided for [G709-2012]./provided for OTNs [G709-2012]./

  The last substitution above is a general comment since this construct
  appears multiple times in S1 and the rest of the document.

  Essentially, you need a label before the reference itself.  Making the
  reference itself a label seems incongruent (at least to me).  I am
  filing this as a nit, so I will let you decide whether to change it or
  not.

Thanks,

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

From david.black@emc.com  Tue Aug 27 09:41:40 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5870C11E81C0; Tue, 27 Aug 2013 09:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.934
X-Spam-Level: 
X-Spam-Status: No, score=-102.934 tagged_above=-999 required=5 tests=[AWL=-0.562, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 IiqZ6gQLqXav; Tue, 27 Aug 2013 09:41:32 -0700 (PDT)
Received: from mexforward.lss.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0555511E8261; Tue, 27 Aug 2013 09:41:29 -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 r7RGf9PK002555 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Aug 2013 12:41:12 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 27 Aug 2013 12:40:54 -0400
Received: from mxhub07.corp.emc.com (mxhub07.corp.emc.com [128.222.70.204]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7RGeMR0007155; Tue, 27 Aug 2013 12:40:52 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub07.corp.emc.com ([128.222.70.204]) with mapi; Tue, 27 Aug 2013 12:40:49 -0400
From: "Black, David" <david.black@emc.com>
To: Ben Campbell <ben@nostrum.com>
Date: Tue, 27 Aug 2013 12:40:47 -0400
Thread-Topic: Gen-ART review of draft-ietf-dime-overload-reqs-11
Thread-Index: Ac6jRC6xkQX5gZxLRrufngsSRaWGvQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C675453@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "bclaise@cisco.com" <bclaise@cisco.com>, Eric McMurry <emcmurry@computer.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-dime-overload-reqs-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: Tue, 27 Aug 2013 16:41:41 -0000

The -11 version of this draft addresses all of the nits and editorial comme=
nts
noted in the Gen-ART review of the -10 version.  It's ready for publication=
 as
an Informational RFC.

Thanks,
--David

> -----Original Message-----
> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Thursday, August 22, 2013 4:50 PM
> To: Black, David
> Cc: Eric McMurry; General Area Review Team (gen-art@ietf.org); ietf@ietf.=
org;
> dime@ietf.org; bclaise@cisco.com
> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>=20
> Hi David,
>=20
> We agree on all your points, and will make the updates in the next versio=
n,
> pending shepherd instructions. =20
>=20
> Thanks!
>=20
> Ben.
>=20
> On Aug 22, 2013, at 2:50 PM, "Black, David" <david.black@emc.com> wrote:
>=20
> > Hi Eric,
> >
> > This looks good - comments follow ...
> >
> >>> a) I assume that overload control development work will derive more
> specific
> >>> security requirements - e.g., as REQ 27 is stated at a rather high le=
vel.
> >>> The discussion in security considerations section seems reasonable.
> >>
> >> We agree with this.  The thinking here was that we didn't want to spec=
ify this
> >> in a way that would be specific to a particular type of mechanism.  It=
 might
> >> not hurt to state that assumption, either as a note on Req 27 or in th=
e sec
> >> considerations.
> >
> > That would be good to add as a note on REQ 27.
> >
> >> The intent was very much as you say, where requirements on individual =
node
> >> capabilities are hoped to result in better overall system behaviors. T=
here are
> >> also some requirements that are stated more at the system level (e.g. =
7 and
> >> 17.) Also the text in section 2.2 that discusses Figure 5 talks about =
how
> >> insufficient server capacity at a cluster of servers behind a Diameter=
 agent
> >> can be treated as if the agent itself was overloaded.
> >>
> >> On the other hand, any mechanism we design will have to focus on actio=
ns of
> >> individual nodes, so the numbered requirements tend to focus on that. =
I'm not
> >> sure where to change the balance here--do you have specific suggestion=
s?
> >
> > I noted this as editorial rather than a minor issue, as I was mostly co=
ncerned
> > that the actual design work will be informed by a sufficient architectu=
ral "clue"
> > that the goal is "better overall system behaviors", which your response=
 indicates
> > will definitely be the case ;-).
> >
> > Rather than edit individual requirements, how about adding the followin=
g sentence
> > immediately following the introductory sentence in Section 7?:
> >
> > 	These requirements are stated primarily in terms of individual node
> > 	behavior to inform the design of the improved mechanism;
> > 	that design effort should keep in mind that the overall goal is
> > 	improved overall system behavior across all the nodes involved,
> > 	not just improved behavior from specific individual nodes.
> >
> >>> This inadequacy may, in turn, contribute to broader congestion collap=
se
> >>>
> >>> "collapse" is not the right word here - I suggest "issues", "impacts"=
,
> >>> "effects" or "problems".
> >>
> >> We are fine with any of those alternatives.  How about impacts.
> >
> > That's fine.  FWIW, "congestion collapse" has a specific (rather severe=
)
> > meaning over in the Transport Area, and that meaning was not intended h=
ere.
> >
> >> 23.843 is the least stable reference.  I don't have any issue with poi=
nting
> >> that out.  The part of it we are referencing is historical front matte=
r
> >> though.
> >
> > I'd note the reference as work in progress, and put the statement about=
 stable
> > front matter (historical is a bad work to use here) in the body of the =
draft
> > that cites the reference.
> >
> >> I tried the web and downloaded versions of 2.12.17 and was not able to=
 get the
> >> warnings you saw (about the references).  What did it say?
> >
> > Sorry, I didn't mean to send you on a wild goose chase :-).  The idnits=
 confusion
> > manifested right at the top of the output, where everyone ignores it ..=
.
> >
> >   Attempted to download rfc272 state...
> >   Failure fetching the file, proceeding without it.
> >
> > You didn't reference RFC 272, so that output's apparently courtesy of i=
dnits
> > misinterpreting this reference:
> >
> > 1195	   [TS29.272]
> > 1196	              3GPP, "Evolved Packet System (EPS); Mobility Managem=
ent
> > 1197	              Entity (MME) and Serving GPRS Support Node (SGSN) re=
lated
> > 1198	              interfaces based on Diameter protocol", TS 29.272 11=
.4.0,
> > 1199	              September 2012.
> >
> > I was amused :-).
> >
> > Thanks,
> > --David
> >
> >> -----Original Message-----
> >> From: Eric McMurry [mailto:emcmurry@computer.org]
> >> Sent: Thursday, August 22, 2013 3:06 PM
> >> To: Black, David
> >> Cc: ben@nostrum.com; General Area Review Team (gen-art@ietf.org);
> >> ietf@ietf.org; dime@ietf.org; bclaise@cisco.com
> >> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
> >>
> >> Hi David,
> >>
> >> Thank you for the review.  Your time and comments are appreciated!
> >>
> >> comments/questions inline.
> >>
> >>
> >> Eric
> >>
> >>
> >>
> >> On Aug 17, 2013, at 9:18 , "Black, David" <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-ietf-dime-overload-reqs-10
> >>> Reviewer: David L. Black
> >>> Review Date: August 17, 2013
> >>> IETF LC End Date: August 16, 2013
> >>> IESG Telechat date: (if known)
> >>>
> >>> Summary:
> >>> This draft is basically ready for publication, but has nits that shou=
ld be
> >>> fixed before publication.
> >>>
> >>> This draft describes scenarios in which Diameter overload can occur a=
nd
> provides
> >>> requirements for development of new overload control functionality in
> Diameter.
> >>> It is well written, and the inclusion of scenarios in which overload =
can
> occur,
> >>> both in terms of the relationships among types of Diameter nodes and
> actual mobile
> >>> network experience is very helpful.
> >>>
> >>> I apologize for this review being a day late, as I've been on vacatio=
n for
> most
> >>> of this draft's IETF Last Call period.
> >>>
> >>> Major issues: (none)
> >>>
> >>> Minor issues: (none)
> >>>
> >>> Nits/editorial comments:
> >>>
> >>> The following two comments could be minor issues, but I'm going to tr=
eat
> them
> >>> as editorial, as I expect that they will be addressed in development =
of
> the
> >>> actual overload functionality:
> >>>
> >>> a) I assume that overload control development work will derive more
> specific
> >>> security requirements - e.g., as REQ 27 is stated at a rather high le=
vel.
> >>> The discussion in security considerations section seems reasonable.
> >>
> >> We agree with this.  The thinking here was that we didn't want to spec=
ify
> this
> >> in a way that would be specific to a particular type of mechanism.  It
> might
> >> not hurt to state that assumption, either as a note on Req 27 or in th=
e sec
> >> considerations.
> >>
> >>>
> >>> b) The draft, and especially its requirements in Section 7 are strong=
ly
> >>> focused on individual Diameter node overload.  That's necessary, but
> overload
> >>> conditions can be broader, affecting an entire service or application=
, or
> >>> multiple instances of either/both, even if not every individual Diame=
ter
> node
> >>> involved is overloaded.  A number of the requirements, starting with =
REQ
> 22
> >>> could be generalized to cover broader overload conditions.
> >>>
> >>> This (b) has implications for other requirements, e.g., REQ 13 should=
 also
> be
> >>> generalized beyond a single node to avoid increased traffic in an ove=
rload
> >>> situation, even from a node that is not overloaded by itself.  There =
are
> limits
> >>> on what is reasonable here, as the desired overload functionality is
> TCP/SCTP-
> >>> like reaction to congestion where individual actions taken by nodes b=
ased
> on
> >>> the information they have (which is not the complete state of the net=
work)
> >>> results in an overall reduction of load.
> >>
> >> The intent was very much as you say, where requirements on individual =
node
> >> capabilities are hoped to result in better overall system behaviors. T=
here
> are
> >> also some requirements that are stated more at the system level (e.g. =
7 and
> >> 17.) Also the text in section 2.2 that discusses Figure 5 talks about =
how
> >> insufficient server capacity at a cluster of servers behind a Diameter
> agent
> >> can be treated as if the agent itself was overloaded.
> >>
> >> On the other hand, any mechanism we design will have to focus on actio=
ns of
> >> individual nodes, so the numbered requirements tend to focus on that. =
I'm
> not
> >> sure where to change the balance here--do you have specific suggestion=
s?
> >>
> >>>
> >>> Section 1.2, 2nd paragraph:
> >>>
> >>>  as network congestion, network congestion can reduce a Diameter node=
s
> >>>
> >>> "nodes" -> "node's"
> >>
> >> good catch.
> >>
> >>>
> >>> Section 5, 1st paragraph:
> >>>
> >>> This inadequacy may, in turn, contribute to broader congestion collap=
se
> >>>
> >>> "collapse" is not the right word here - I suggest "issues", "impacts"=
,
> >>> "effects" or "problems".
> >>
> >> We are fine with any of those alternatives.  How about impacts.
> >>
> >>>
> >>> Section 7
> >>>
> >>> The long enumerated list of requirements is not an easy read.  It wou=
ld be
> >>> better if these could somehow be grouped by functional category, e.g.=
,
> >>> security, transport interactions, operational/administrative, etc.
> >>
> >> agree.  It is actually in sections in the XML (denoted by comments), w=
e
> just
> >> did not promote those to visible sections in the txt.  I recall there =
being
> >> some issue with xml2rfc and numbering, but now that the numbers are se=
t,
> this
> >> would not be hard to do.
> >>
> >>
> >>>
> >>> idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - this i=
s
> fine,
> >>> as the boilerplate has been appropriately modified for this draft tha=
t
> >>> expresses requirements (as opposed to a draft that specifies a protoc=
ol).
> >>>
> >>> idnits 2.12.17 got confused by the 3GPP and GSMA Informative Referenc=
es.
> >>> I assume that they're all sufficiently stable to be informative
> references.
> >>> However, [TR23.843] is a work in progress, and should be noted as suc=
h in
> >>> its reference - is this needed for any of the other 3GPP or GSMA
> references?
> >>
> >> 23.843 is the least stable reference.  I don't have any issue with poi=
nting
> >> that out.  The part of it we are referencing is historical front matte=
r
> >> though.
> >>
> >>
> >> I tried the web and downloaded versions of 2.12.17 and was not able to=
 get
> the
> >> warnings you saw (about the references).  What did it say?
> >>
> >>
> >>>
> >>> Thanks,
> >>> --David
> >>> ----------------------------------------------------
> >>> David L. Black, Distinguished Engineer
> >>> EMC Corporation, 176 South St., Hopkinton, MA  01748
> >>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> >>> david.black@emc.com        Mobile: +1 (978) 394-7754
> >>> ----------------------------------------------------
> >>>
> >>
> >
>=20


From ben@nostrum.com  Tue Aug 27 10:18:15 2013
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4016521E8085; Tue, 27 Aug 2013 10:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.444
X-Spam-Level: 
X-Spam-Status: No, score=-102.444 tagged_above=-999 required=5 tests=[AWL=-0.071, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 Acw0vuiredUW; Tue, 27 Aug 2013 10:18:14 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id C1B4021E8056; Tue, 27 Aug 2013 10:18:13 -0700 (PDT)
Received: from [10.0.1.27] (cpe-76-187-89-238.tx.res.rr.com [76.187.89.238]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7RHI271080461 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 27 Aug 2013 12:18:03 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C675453@MX15A.corp.emc.com>
Date: Tue, 27 Aug 2013 12:18:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E777B5F-BF39-4F12-BB93-5E55342BA93A@nostrum.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C675453@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.89.238 is authenticated by a trusted mechanism)
Cc: "bclaise@cisco.com" <bclaise@cisco.com>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Eric McMurry <emcmurry@computer.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dime-overload-reqs-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: Tue, 27 Aug 2013 17:18:15 -0000

Thanks, David!

On Aug 27, 2013, at 11:40 AM, "Black, David" <david.black@emc.com> =
wrote:

> The -11 version of this draft addresses all of the nits and editorial =
comments
> noted in the Gen-ART review of the -10 version.  It's ready for =
publication as
> an Informational RFC.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Ben Campbell [mailto:ben@nostrum.com]
>> Sent: Thursday, August 22, 2013 4:50 PM
>> To: Black, David
>> Cc: Eric McMurry; General Area Review Team (gen-art@ietf.org); =
ietf@ietf.org;
>> dime@ietf.org; bclaise@cisco.com
>> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>>=20
>> Hi David,
>>=20
>> We agree on all your points, and will make the updates in the next =
version,
>> pending shepherd instructions. =20
>>=20
>> Thanks!
>>=20
>> Ben.
>>=20
>> On Aug 22, 2013, at 2:50 PM, "Black, David" <david.black@emc.com> =
wrote:
>>=20
>>> Hi Eric,
>>>=20
>>> This looks good - comments follow ...
>>>=20
>>>>> a) I assume that overload control development work will derive =
more
>> specific
>>>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>>>> The discussion in security considerations section seems =
reasonable.
>>>>=20
>>>> We agree with this.  The thinking here was that we didn't want to =
specify this
>>>> in a way that would be specific to a particular type of mechanism.  =
It might
>>>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>>>> considerations.
>>>=20
>>> That would be good to add as a note on REQ 27.
>>>=20
>>>> The intent was very much as you say, where requirements on =
individual node
>>>> capabilities are hoped to result in better overall system =
behaviors. There are
>>>> also some requirements that are stated more at the system level =
(e.g. 7 and
>>>> 17.) Also the text in section 2.2 that discusses Figure 5 talks =
about how
>>>> insufficient server capacity at a cluster of servers behind a =
Diameter agent
>>>> can be treated as if the agent itself was overloaded.
>>>>=20
>>>> On the other hand, any mechanism we design will have to focus on =
actions of
>>>> individual nodes, so the numbered requirements tend to focus on =
that. I'm not
>>>> sure where to change the balance here--do you have specific =
suggestions?
>>>=20
>>> I noted this as editorial rather than a minor issue, as I was mostly =
concerned
>>> that the actual design work will be informed by a sufficient =
architectural "clue"
>>> that the goal is "better overall system behaviors", which your =
response indicates
>>> will definitely be the case ;-).
>>>=20
>>> Rather than edit individual requirements, how about adding the =
following sentence
>>> immediately following the introductory sentence in Section 7?:
>>>=20
>>> 	These requirements are stated primarily in terms of individual =
node
>>> 	behavior to inform the design of the improved mechanism;
>>> 	that design effort should keep in mind that the overall goal is
>>> 	improved overall system behavior across all the nodes involved,
>>> 	not just improved behavior from specific individual nodes.
>>>=20
>>>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>>>=20
>>>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>>>> "effects" or "problems".
>>>>=20
>>>> We are fine with any of those alternatives.  How about impacts.
>>>=20
>>> That's fine.  FWIW, "congestion collapse" has a specific (rather =
severe)
>>> meaning over in the Transport Area, and that meaning was not =
intended here.
>>>=20
>>>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>>>> that out.  The part of it we are referencing is historical front =
matter
>>>> though.
>>>=20
>>> I'd note the reference as work in progress, and put the statement =
about stable
>>> front matter (historical is a bad work to use here) in the body of =
the draft
>>> that cites the reference.
>>>=20
>>>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get the
>>>> warnings you saw (about the references).  What did it say?
>>>=20
>>> Sorry, I didn't mean to send you on a wild goose chase :-).  The =
idnits confusion
>>> manifested right at the top of the output, where everyone ignores it =
...
>>>=20
>>>  Attempted to download rfc272 state...
>>>  Failure fetching the file, proceeding without it.
>>>=20
>>> You didn't reference RFC 272, so that output's apparently courtesy =
of idnits
>>> misinterpreting this reference:
>>>=20
>>> 1195	   [TS29.272]
>>> 1196	              3GPP, "Evolved Packet System (EPS); =
Mobility Management
>>> 1197	              Entity (MME) and Serving GPRS Support Node =
(SGSN) related
>>> 1198	              interfaces based on Diameter protocol", TS =
29.272 11.4.0,
>>> 1199	              September 2012.
>>>=20
>>> I was amused :-).
>>>=20
>>> Thanks,
>>> --David
>>>=20
>>>> -----Original Message-----
>>>> From: Eric McMurry [mailto:emcmurry@computer.org]
>>>> Sent: Thursday, August 22, 2013 3:06 PM
>>>> To: Black, David
>>>> Cc: ben@nostrum.com; General Area Review Team (gen-art@ietf.org);
>>>> ietf@ietf.org; dime@ietf.org; bclaise@cisco.com
>>>> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>>>>=20
>>>> Hi David,
>>>>=20
>>>> Thank you for the review.  Your time and comments are appreciated!
>>>>=20
>>>> comments/questions inline.
>>>>=20
>>>>=20
>>>> Eric
>>>>=20
>>>>=20
>>>>=20
>>>> On Aug 17, 2013, at 9:18 , "Black, David" <david.black@emc.com> =
wrote:
>>>>=20
>>>>>=20
>>>>> I am the assigned Gen-ART reviewer for this draft. For background =
on
>>>>> Gen-ART, please see the FAQ at
>>>>>=20
>>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>>=20
>>>>> Please resolve these comments along with any other Last Call =
comments
>>>>> you may receive.
>>>>>=20
>>>>> Document: draft-ietf-dime-overload-reqs-10
>>>>> Reviewer: David L. Black
>>>>> Review Date: August 17, 2013
>>>>> IETF LC End Date: August 16, 2013
>>>>> IESG Telechat date: (if known)
>>>>>=20
>>>>> Summary:
>>>>> This draft is basically ready for publication, but has nits that =
should be
>>>>> fixed before publication.
>>>>>=20
>>>>> This draft describes scenarios in which Diameter overload can =
occur and
>> provides
>>>>> requirements for development of new overload control functionality =
in
>> Diameter.
>>>>> It is well written, and the inclusion of scenarios in which =
overload can
>> occur,
>>>>> both in terms of the relationships among types of Diameter nodes =
and
>> actual mobile
>>>>> network experience is very helpful.
>>>>>=20
>>>>> I apologize for this review being a day late, as I've been on =
vacation for
>> most
>>>>> of this draft's IETF Last Call period.
>>>>>=20
>>>>> Major issues: (none)
>>>>>=20
>>>>> Minor issues: (none)
>>>>>=20
>>>>> Nits/editorial comments:
>>>>>=20
>>>>> The following two comments could be minor issues, but I'm going to =
treat
>> them
>>>>> as editorial, as I expect that they will be addressed in =
development of
>> the
>>>>> actual overload functionality:
>>>>>=20
>>>>> a) I assume that overload control development work will derive =
more
>> specific
>>>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>>>> The discussion in security considerations section seems =
reasonable.
>>>>=20
>>>> We agree with this.  The thinking here was that we didn't want to =
specify
>> this
>>>> in a way that would be specific to a particular type of mechanism.  =
It
>> might
>>>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>>>> considerations.
>>>>=20
>>>>>=20
>>>>> b) The draft, and especially its requirements in Section 7 are =
strongly
>>>>> focused on individual Diameter node overload.  That's necessary, =
but
>> overload
>>>>> conditions can be broader, affecting an entire service or =
application, or
>>>>> multiple instances of either/both, even if not every individual =
Diameter
>> node
>>>>> involved is overloaded.  A number of the requirements, starting =
with REQ
>> 22
>>>>> could be generalized to cover broader overload conditions.
>>>>>=20
>>>>> This (b) has implications for other requirements, e.g., REQ 13 =
should also
>> be
>>>>> generalized beyond a single node to avoid increased traffic in an =
overload
>>>>> situation, even from a node that is not overloaded by itself.  =
There are
>> limits
>>>>> on what is reasonable here, as the desired overload functionality =
is
>> TCP/SCTP-
>>>>> like reaction to congestion where individual actions taken by =
nodes based
>> on
>>>>> the information they have (which is not the complete state of the =
network)
>>>>> results in an overall reduction of load.
>>>>=20
>>>> The intent was very much as you say, where requirements on =
individual node
>>>> capabilities are hoped to result in better overall system =
behaviors. There
>> are
>>>> also some requirements that are stated more at the system level =
(e.g. 7 and
>>>> 17.) Also the text in section 2.2 that discusses Figure 5 talks =
about how
>>>> insufficient server capacity at a cluster of servers behind a =
Diameter
>> agent
>>>> can be treated as if the agent itself was overloaded.
>>>>=20
>>>> On the other hand, any mechanism we design will have to focus on =
actions of
>>>> individual nodes, so the numbered requirements tend to focus on =
that. I'm
>> not
>>>> sure where to change the balance here--do you have specific =
suggestions?
>>>>=20
>>>>>=20
>>>>> Section 1.2, 2nd paragraph:
>>>>>=20
>>>>> as network congestion, network congestion can reduce a Diameter =
nodes
>>>>>=20
>>>>> "nodes" -> "node's"
>>>>=20
>>>> good catch.
>>>>=20
>>>>>=20
>>>>> Section 5, 1st paragraph:
>>>>>=20
>>>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>>>=20
>>>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>>>> "effects" or "problems".
>>>>=20
>>>> We are fine with any of those alternatives.  How about impacts.
>>>>=20
>>>>>=20
>>>>> Section 7
>>>>>=20
>>>>> The long enumerated list of requirements is not an easy read.  It =
would be
>>>>> better if these could somehow be grouped by functional category, =
e.g.,
>>>>> security, transport interactions, operational/administrative, etc.
>>>>=20
>>>> agree.  It is actually in sections in the XML (denoted by =
comments), we
>> just
>>>> did not promote those to visible sections in the txt.  I recall =
there being
>>>> some issue with xml2rfc and numbering, but now that the numbers are =
set,
>> this
>>>> would not be hard to do.
>>>>=20
>>>>=20
>>>>>=20
>>>>> idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - =
this is
>> fine,
>>>>> as the boilerplate has been appropriately modified for this draft =
that
>>>>> expresses requirements (as opposed to a draft that specifies a =
protocol).
>>>>>=20
>>>>> idnits 2.12.17 got confused by the 3GPP and GSMA Informative =
References.
>>>>> I assume that they're all sufficiently stable to be informative
>> references.
>>>>> However, [TR23.843] is a work in progress, and should be noted as =
such in
>>>>> its reference - is this needed for any of the other 3GPP or GSMA
>> references?
>>>>=20
>>>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>>>> that out.  The part of it we are referencing is historical front =
matter
>>>> though.
>>>>=20
>>>>=20
>>>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get
>> the
>>>> warnings you saw (about the references).  What did it say?
>>>>=20
>>>>=20
>>>>>=20
>>>>> Thanks,
>>>>> --David
>>>>> ----------------------------------------------------
>>>>> David L. Black, Distinguished Engineer
>>>>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>>>>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>>>>> david.black@emc.com        Mobile: +1 (978) 394-7754
>>>>> ----------------------------------------------------
>>>>>=20
>>>>=20
>>>=20
>>=20
>=20


From jouni.nospam@gmail.com  Tue Aug 27 13:26:55 2013
Return-Path: <jouni.nospam@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 587A711E81C8; Tue, 27 Aug 2013 13:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.296
X-Spam-Level: 
X-Spam-Status: No, score=-2.296 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4EDIgc1VYY2; Tue, 27 Aug 2013 13:26:54 -0700 (PDT)
Received: from mail-ee0-x230.google.com (mail-ee0-x230.google.com [IPv6:2a00:1450:4013:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 6F86511E81BC; Tue, 27 Aug 2013 13:26:53 -0700 (PDT)
Received: by mail-ee0-f48.google.com with SMTP id l10so2466690eei.7 for <multiple recipients>; Tue, 27 Aug 2013 13:26:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=znDVBMXGyKlkBXQRv8j2FXcQjkoReAui0jeiK0GTZ1M=; b=vOHw3z52ZF6zHZu0Me+fyZ/LOFEfpOE5HpM/ahzdjlZ+0dPUC+pLL0FhpXagDGoPhZ x1mp+z96Gs3LWQ/XZ3WL7opAwzPDfgaP2AMjHV+CYWdX4jmzgCnH1n+97K3O98WB+8Ue 5pQxu59VTYGtm3CraQXwkKiNDGvfYG4ULpvYz3EUa1wFGBFhexXjUdIGFr5fhqiwf2ez SadYrnhaNUIwU0KWggWCTcyh+K8N9eYVab0U0/eYm2/TN/G9g0Z3YrNlcZEC7zOjkRu/ QSw+ZVtmBX0pbppK8JeZyh6b/sGVYJONAAb0gJfaZ0PhA05+KwjCpt5iZrp7a+OAQMZG 1nGw==
X-Received: by 10.15.83.2 with SMTP id b2mr37325764eez.28.1377635211120; Tue, 27 Aug 2013 13:26:51 -0700 (PDT)
Received: from ?IPv6:2001:1bc8:101:f101:fc5e:23e4:7126:ddab? ([2001:1bc8:101:f101:fc5e:23e4:7126:ddab]) by mx.google.com with ESMTPSA id h52sm31777998eez.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 27 Aug 2013 13:26:47 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C675453@MX15A.corp.emc.com>
Date: Tue, 27 Aug 2013 23:26:45 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <26019E7F-3973-460A-94F1-C7076FD80D0F@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C675453@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Eric McMurry <emcmurry@computer.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dime-overload-reqs-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: Tue, 27 Aug 2013 20:26:55 -0000

Great. Thanks!


- Jouni


On Aug 27, 2013, at 7:40 PM, "Black, David" <david.black@emc.com> wrote:

> The -11 version of this draft addresses all of the nits and editorial =
comments
> noted in the Gen-ART review of the -10 version.  It's ready for =
publication as
> an Informational RFC.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Ben Campbell [mailto:ben@nostrum.com]
>> Sent: Thursday, August 22, 2013 4:50 PM
>> To: Black, David
>> Cc: Eric McMurry; General Area Review Team (gen-art@ietf.org); =
ietf@ietf.org;
>> dime@ietf.org; bclaise@cisco.com
>> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>>=20
>> Hi David,
>>=20
>> We agree on all your points, and will make the updates in the next =
version,
>> pending shepherd instructions. =20
>>=20
>> Thanks!
>>=20
>> Ben.
>>=20
>> On Aug 22, 2013, at 2:50 PM, "Black, David" <david.black@emc.com> =
wrote:
>>=20
>>> Hi Eric,
>>>=20
>>> This looks good - comments follow ...
>>>=20
>>>>> a) I assume that overload control development work will derive =
more
>> specific
>>>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>>>> The discussion in security considerations section seems =
reasonable.
>>>>=20
>>>> We agree with this.  The thinking here was that we didn't want to =
specify this
>>>> in a way that would be specific to a particular type of mechanism.  =
It might
>>>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>>>> considerations.
>>>=20
>>> That would be good to add as a note on REQ 27.
>>>=20
>>>> The intent was very much as you say, where requirements on =
individual node
>>>> capabilities are hoped to result in better overall system =
behaviors. There are
>>>> also some requirements that are stated more at the system level =
(e.g. 7 and
>>>> 17.) Also the text in section 2.2 that discusses Figure 5 talks =
about how
>>>> insufficient server capacity at a cluster of servers behind a =
Diameter agent
>>>> can be treated as if the agent itself was overloaded.
>>>>=20
>>>> On the other hand, any mechanism we design will have to focus on =
actions of
>>>> individual nodes, so the numbered requirements tend to focus on =
that. I'm not
>>>> sure where to change the balance here--do you have specific =
suggestions?
>>>=20
>>> I noted this as editorial rather than a minor issue, as I was mostly =
concerned
>>> that the actual design work will be informed by a sufficient =
architectural "clue"
>>> that the goal is "better overall system behaviors", which your =
response indicates
>>> will definitely be the case ;-).
>>>=20
>>> Rather than edit individual requirements, how about adding the =
following sentence
>>> immediately following the introductory sentence in Section 7?:
>>>=20
>>> 	These requirements are stated primarily in terms of individual =
node
>>> 	behavior to inform the design of the improved mechanism;
>>> 	that design effort should keep in mind that the overall goal is
>>> 	improved overall system behavior across all the nodes involved,
>>> 	not just improved behavior from specific individual nodes.
>>>=20
>>>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>>>=20
>>>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>>>> "effects" or "problems".
>>>>=20
>>>> We are fine with any of those alternatives.  How about impacts.
>>>=20
>>> That's fine.  FWIW, "congestion collapse" has a specific (rather =
severe)
>>> meaning over in the Transport Area, and that meaning was not =
intended here.
>>>=20
>>>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>>>> that out.  The part of it we are referencing is historical front =
matter
>>>> though.
>>>=20
>>> I'd note the reference as work in progress, and put the statement =
about stable
>>> front matter (historical is a bad work to use here) in the body of =
the draft
>>> that cites the reference.
>>>=20
>>>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get the
>>>> warnings you saw (about the references).  What did it say?
>>>=20
>>> Sorry, I didn't mean to send you on a wild goose chase :-).  The =
idnits confusion
>>> manifested right at the top of the output, where everyone ignores it =
...
>>>=20
>>>  Attempted to download rfc272 state...
>>>  Failure fetching the file, proceeding without it.
>>>=20
>>> You didn't reference RFC 272, so that output's apparently courtesy =
of idnits
>>> misinterpreting this reference:
>>>=20
>>> 1195	   [TS29.272]
>>> 1196	              3GPP, "Evolved Packet System (EPS); =
Mobility Management
>>> 1197	              Entity (MME) and Serving GPRS Support Node =
(SGSN) related
>>> 1198	              interfaces based on Diameter protocol", TS =
29.272 11.4.0,
>>> 1199	              September 2012.
>>>=20
>>> I was amused :-).
>>>=20
>>> Thanks,
>>> --David
>>>=20
>>>> -----Original Message-----
>>>> From: Eric McMurry [mailto:emcmurry@computer.org]
>>>> Sent: Thursday, August 22, 2013 3:06 PM
>>>> To: Black, David
>>>> Cc: ben@nostrum.com; General Area Review Team (gen-art@ietf.org);
>>>> ietf@ietf.org; dime@ietf.org; bclaise@cisco.com
>>>> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>>>>=20
>>>> Hi David,
>>>>=20
>>>> Thank you for the review.  Your time and comments are appreciated!
>>>>=20
>>>> comments/questions inline.
>>>>=20
>>>>=20
>>>> Eric
>>>>=20
>>>>=20
>>>>=20
>>>> On Aug 17, 2013, at 9:18 , "Black, David" <david.black@emc.com> =
wrote:
>>>>=20
>>>>>=20
>>>>> I am the assigned Gen-ART reviewer for this draft. For background =
on
>>>>> Gen-ART, please see the FAQ at
>>>>>=20
>>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>>=20
>>>>> Please resolve these comments along with any other Last Call =
comments
>>>>> you may receive.
>>>>>=20
>>>>> Document: draft-ietf-dime-overload-reqs-10
>>>>> Reviewer: David L. Black
>>>>> Review Date: August 17, 2013
>>>>> IETF LC End Date: August 16, 2013
>>>>> IESG Telechat date: (if known)
>>>>>=20
>>>>> Summary:
>>>>> This draft is basically ready for publication, but has nits that =
should be
>>>>> fixed before publication.
>>>>>=20
>>>>> This draft describes scenarios in which Diameter overload can =
occur and
>> provides
>>>>> requirements for development of new overload control functionality =
in
>> Diameter.
>>>>> It is well written, and the inclusion of scenarios in which =
overload can
>> occur,
>>>>> both in terms of the relationships among types of Diameter nodes =
and
>> actual mobile
>>>>> network experience is very helpful.
>>>>>=20
>>>>> I apologize for this review being a day late, as I've been on =
vacation for
>> most
>>>>> of this draft's IETF Last Call period.
>>>>>=20
>>>>> Major issues: (none)
>>>>>=20
>>>>> Minor issues: (none)
>>>>>=20
>>>>> Nits/editorial comments:
>>>>>=20
>>>>> The following two comments could be minor issues, but I'm going to =
treat
>> them
>>>>> as editorial, as I expect that they will be addressed in =
development of
>> the
>>>>> actual overload functionality:
>>>>>=20
>>>>> a) I assume that overload control development work will derive =
more
>> specific
>>>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>>>> The discussion in security considerations section seems =
reasonable.
>>>>=20
>>>> We agree with this.  The thinking here was that we didn't want to =
specify
>> this
>>>> in a way that would be specific to a particular type of mechanism.  =
It
>> might
>>>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>>>> considerations.
>>>>=20
>>>>>=20
>>>>> b) The draft, and especially its requirements in Section 7 are =
strongly
>>>>> focused on individual Diameter node overload.  That's necessary, =
but
>> overload
>>>>> conditions can be broader, affecting an entire service or =
application, or
>>>>> multiple instances of either/both, even if not every individual =
Diameter
>> node
>>>>> involved is overloaded.  A number of the requirements, starting =
with REQ
>> 22
>>>>> could be generalized to cover broader overload conditions.
>>>>>=20
>>>>> This (b) has implications for other requirements, e.g., REQ 13 =
should also
>> be
>>>>> generalized beyond a single node to avoid increased traffic in an =
overload
>>>>> situation, even from a node that is not overloaded by itself.  =
There are
>> limits
>>>>> on what is reasonable here, as the desired overload functionality =
is
>> TCP/SCTP-
>>>>> like reaction to congestion where individual actions taken by =
nodes based
>> on
>>>>> the information they have (which is not the complete state of the =
network)
>>>>> results in an overall reduction of load.
>>>>=20
>>>> The intent was very much as you say, where requirements on =
individual node
>>>> capabilities are hoped to result in better overall system =
behaviors. There
>> are
>>>> also some requirements that are stated more at the system level =
(e.g. 7 and
>>>> 17.) Also the text in section 2.2 that discusses Figure 5 talks =
about how
>>>> insufficient server capacity at a cluster of servers behind a =
Diameter
>> agent
>>>> can be treated as if the agent itself was overloaded.
>>>>=20
>>>> On the other hand, any mechanism we design will have to focus on =
actions of
>>>> individual nodes, so the numbered requirements tend to focus on =
that. I'm
>> not
>>>> sure where to change the balance here--do you have specific =
suggestions?
>>>>=20
>>>>>=20
>>>>> Section 1.2, 2nd paragraph:
>>>>>=20
>>>>> as network congestion, network congestion can reduce a Diameter =
nodes
>>>>>=20
>>>>> "nodes" -> "node's"
>>>>=20
>>>> good catch.
>>>>=20
>>>>>=20
>>>>> Section 5, 1st paragraph:
>>>>>=20
>>>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>>>=20
>>>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>>>> "effects" or "problems".
>>>>=20
>>>> We are fine with any of those alternatives.  How about impacts.
>>>>=20
>>>>>=20
>>>>> Section 7
>>>>>=20
>>>>> The long enumerated list of requirements is not an easy read.  It =
would be
>>>>> better if these could somehow be grouped by functional category, =
e.g.,
>>>>> security, transport interactions, operational/administrative, etc.
>>>>=20
>>>> agree.  It is actually in sections in the XML (denoted by =
comments), we
>> just
>>>> did not promote those to visible sections in the txt.  I recall =
there being
>>>> some issue with xml2rfc and numbering, but now that the numbers are =
set,
>> this
>>>> would not be hard to do.
>>>>=20
>>>>=20
>>>>>=20
>>>>> idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - =
this is
>> fine,
>>>>> as the boilerplate has been appropriately modified for this draft =
that
>>>>> expresses requirements (as opposed to a draft that specifies a =
protocol).
>>>>>=20
>>>>> idnits 2.12.17 got confused by the 3GPP and GSMA Informative =
References.
>>>>> I assume that they're all sufficiently stable to be informative
>> references.
>>>>> However, [TR23.843] is a work in progress, and should be noted as =
such in
>>>>> its reference - is this needed for any of the other 3GPP or GSMA
>> references?
>>>>=20
>>>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>>>> that out.  The part of it we are referencing is historical front =
matter
>>>> though.
>>>>=20
>>>>=20
>>>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get
>> the
>>>> warnings you saw (about the references).  What did it say?
>>>>=20
>>>>=20
>>>>>=20
>>>>> Thanks,
>>>>> --David
>>>>> ----------------------------------------------------
>>>>> David L. Black, Distinguished Engineer
>>>>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>>>>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>>>>> david.black@emc.com        Mobile: +1 (978) 394-7754
>>>>> ----------------------------------------------------
>>>>>=20
>>>>=20
>>>=20
>>=20
>=20


From Francis.Dupont@fdupont.fr  Wed Aug 28 06:05:08 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8641021E80A5 for <gen-art@ietfa.amsl.com>; Wed, 28 Aug 2013 06:05:08 -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 Uo1tUqLAcUGS for <gen-art@ietfa.amsl.com>; Wed, 28 Aug 2013 06:05:07 -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 95FC021E804E for <gen-art@ietf.org>; Wed, 28 Aug 2013 06:05:06 -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 r7SD4v8Y071846; Wed, 28 Aug 2013 15:04:57 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201308281304.r7SD4v8Y071846@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Black, David" <david.black@emc.com>
In-reply-to: Your message of Thu, 15 Aug 2013 07:42:06 EDT. <8D3D17ACE214DC429325B2B98F3AE7129C2B7C4B@MX15A.corp.emc.com> 
Date: Wed, 28 Aug 2013 15:04:57 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-storm-ipsec-ips-update.all@tools.ietf.org" <draft-ietf-storm-ipsec-ips-update.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-storm-ipsec-ips-update-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 13:05:08 -0000

 In your previous mail you wrote:

> Thank you for the review.  I have made all three changes in my
> working version that will become the -04.

=> thanks, I raised the status to "Ready" even the -04 doesn't seem
to be available in the tools.ietf.org I-D repository?

Francis.Dupont@fdupont.fr

PS: the draft-ietf-storm-ipsec-ips-update is at the IESG agenda
of the 2013-08-29 teleconf
(cf http://datatracker.ietf.org/iesg/agenda/)

From ron.even.tlv@gmail.com  Wed Aug 28 06:09:04 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46E3321E8050; Wed, 28 Aug 2013 06:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8JzL-e8fZu2i; Wed, 28 Aug 2013 06:09:03 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id BDF1411E818B; Wed, 28 Aug 2013 06:09:01 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id q54so5234987wes.33 for <multiple recipients>; Wed, 28 Aug 2013 06:09:00 -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 :thread-index:content-language; bh=TjoJ5THm/b/sHaxDZ2zkbVL7Fq+zQZWsmGZmeyIdRmw=; b=ssCBw3J3T6rKfySaciQjl/semwm+3ZhXdQxhb+EvrIddlfTp8+Lm+QAdAhG9Kgoz/j uq7OGmXn90z4KSk1GBsM/A/aacjnKtrjGSAAHdFFPfaIH/7O2r0tOEBTV9WE4TKtFr2H YUtDJGwNDHyajX3lHIlJ87o6Ga52LP09c0/InqODL9iXDo3Qv3s68TmGHsmL9gp0APS0 yrie10E0UET36Uj5RdNZT8IH2hBavXwnm2jyQ9nJj263NEcTtZqhd7qYQEqpbwWZa/wI Dsgcxouql64EtZgAgg9M3kAKCJvR589aumHqpBAt6Xtnes06erLyEZ+ah2gqJTiT7anN 8ZXg==
X-Received: by 10.194.94.201 with SMTP id de9mr1846225wjb.78.1377695339756; Wed, 28 Aug 2013 06:08:59 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id om9sm4957786wic.8.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 28 Aug 2013 06:08:58 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
Date: Wed, 28 Aug 2013 16:06:28 +0300
Message-ID: <041001cea3ef$6a931b60$3fb95220$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0411_01CEA408.8FE116B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6j72iTQaEc2KyVR6aJXw9+GJi+Ew==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-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: Wed, 28 Aug 2013 13:09:04 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0411_01CEA408.8FE116B0
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-mpls-return-path-specified-lsp-ping-12

Reviewer: Roni Even

Review Date:2013-8-28

IETF LC End Date: 2013-9-4

IESG Telechat date: 

 

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

 

 

Major issues:

Minor issues:

I am not clear on the sub-TLV in section 6.2

1.	If a new sub-TLV is defined for TLV type 1 do they need also to be
added to TLV type 21. This should be clear, and if there is some relation I
think it should be reflected in the IANA registry for TLV type 1
2.	For the vendor or private use why a difference policy than the rest
of the sub-TLV registry 

 

Nits/editorial comments:

1.	In section 3.4 I assume that "TC" is traffic class. It will be good
to expand and have reference.

 


------=_NextPart_000_0411_01CEA408.8FE116B0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2001153705;
	mso-list-type:hybrid;
	mso-list-template-ids:811757280 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:2027515742;
	mso-list-type:hybrid;
	mso-list-template-ids:-121760254 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-mpls-return-path-specified-lsp-ping-12</span><o:p></o:p>=
</p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;8&#8211;28<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-9&#8211;4<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 a standard track =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Major issues:<o:p></o:p></p><p =
class=3DMsoNormal>Minor issues:<o:p></o:p></p><p class=3DMsoNormal>I am =
not clear on the sub-TLV in section 6.2<o:p></o:p></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l1 level1 lfo1'>If a new sub-TLV is defined for TLV =
type 1 do they need also to be added to TLV type 21. This should be =
clear, and if there is some relation I think it should be reflected in =
the IANA registry for TLV type 1<o:p></o:p></li><li class=3DMsoNormal =
style=3D'mso-list:l1 level1 lfo1'>For the vendor or private use why a =
difference policy than the rest of the sub-TLV registry =
<o:p></o:p></li></ol><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Nits/editorial comments:<o:p></o:p></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l0 level1 lfo2'>In section 3.4 I assume that =
&#8220;TC&#8221; is traffic class. It will be good to expand and have =
reference.<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0411_01CEA408.8FE116B0--


From loa@pi.nu  Wed Aug 28 07:20:17 2013
Return-Path: <loa@pi.nu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5506211E813A; Wed, 28 Aug 2013 07:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 48JZT6KHO0rk; Wed, 28 Aug 2013 07:20:12 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 794B911E811F; Wed, 28 Aug 2013 07:20:12 -0700 (PDT)
Received: from [192.168.5.58] (81-229-83-119-no65.business.telia.com [81.229.83.119]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id B6CD918033E4; Wed, 28 Aug 2013 16:20:11 +0200 (CEST)
Message-ID: <521E071F.7050607@pi.nu>
Date: Wed, 28 Aug 2013 16:20:15 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
References: <041001cea3ef$6a931b60$3fb95220$@gmail.com>
In-Reply-To: <041001cea3ef$6a931b60$3fb95220$@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: gen-art@ietf.org, draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-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: Wed, 28 Aug 2013 14:20:17 -0000

Roni,

Thanks for an insightful review, you have captured much of what we
been struggling with when it comes to the IANA allocations.

On 2013-08-28 15:06, Roni Even wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> Summary: This draft is almost ready for publication as a standard track RFC.
>
> Major issues:
>
> Minor issues:
>
> I am not clear on the sub-TLV in section 6.2
>
>  1. If a new sub-TLV is defined for TLV type 1 do they need also to be
>     added to TLV type 21.

Yes the document says "Directly copied from TLV Type 1, MUST NOT be
assigned" the intention is that this applies to future sub-TLVs also.
I guess it could be changed to "Directly copied from TLV Type 1
(including future allocations for TLV Type 1, MUST NOT be assigned"
if that makes thing clearer.

>     This should be clear, and if there is some
>     relation I think it should be reflected in the IANA registry for TLV
>     type 1

I guess that makes sense - but it has not been the what we've done 
earlier - I think we could add this where needed by directly
communicate  this to IANA.

>  2. For the vendor or private use why a difference policy than the rest
>     of the sub-TLV registry

We don't assign vendor private use at all, so by default it is
different. I don't see that it could be different.

/Loa
>
> Nits/editorial comments:
>
>  1. In section 3.4 I assume that “TC” is traffic class. It will be good
>     to expand and have reference.
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From david.black@emc.com  Wed Aug 28 07:52:20 2013
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0C8A11E811F for <gen-art@ietfa.amsl.com>; Wed, 28 Aug 2013 07:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tAJY+ukUrSjj for <gen-art@ietfa.amsl.com>; Wed, 28 Aug 2013 07:52:16 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id B952311E8192 for <gen-art@ietf.org>; Wed, 28 Aug 2013 07:52:08 -0700 (PDT)
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com [10.106.48.159]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r7SEpsub020247 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Aug 2013 10:51:55 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com r7SEpsub020247
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1377701515; bh=cuE/gt6mKPdqY6eDQfZYV1WjakA=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=PcJGfl59MyZSbeWyWboWS1LhspHi4ozlI+FXHFDXnEE0gOceViEgcaGG0Z/OJrcsG IjxbtKFlvgIcY2RBtK15ZF2817aEY2zyCSTiilH6IEmQT01L60lXInCEMiQ6Sc7+u+ y749DpgdMOYWNfoVfl2UnUuSLE7cdXMLHtI7jcIM=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com r7SEpsub020247
Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd55.lss.emc.com (RSA Interceptor); Wed, 28 Aug 2013 10:51:39 -0400
Received: from mxhub34.corp.emc.com (mxhub34.corp.emc.com [10.254.93.82]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r7SEpckv023287 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 28 Aug 2013 10:51:39 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub34.corp.emc.com ([::1]) with mapi; Wed, 28 Aug 2013 10:51:38 -0400
From: "Black, David" <david.black@emc.com>
To: "Francis.Dupont@fdupont.fr" <Francis.Dupont@fdupont.fr>
Date: Wed, 28 Aug 2013 10:51:36 -0400
Thread-Topic: [Gen-art] review of draft-ietf-storm-ipsec-ips-update-03.txt 
Thread-Index: Ac6j7xvO0mGIsBAcQMyRpxAqaEZ3KAADdHlA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C6755B7@MX15A.corp.emc.com>
References: Your message of Thu, 15 Aug 2013 07:42:06 EDT. <8D3D17ACE214DC429325B2B98F3AE7129C2B7C4B@MX15A.corp.emc.com> <201308281304.r7SD4v8Y071846@givry.fdupont.fr>
In-Reply-To: <201308281304.r7SD4v8Y071846@givry.fdupont.fr>
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-Sentrion-Hostname: mailusrhubprd53.lss.emc.com
X-EMM-GWVC: 1
X-RSA-Classifications: DLM_1, public
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-storm-ipsec-ips-update.all@tools.ietf.org" <draft-ietf-storm-ipsec-ips-update.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-storm-ipsec-ips-update-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 14:52:20 -0000

Thank you - the -04 will appear after the results of the IETF telechat
on Thursday, probably sometime next week, as there are some additional chan=
ges
that will be necessary.

Thanks,
--David

> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Wednesday, August 28, 2013 9:05 AM
> To: Black, David
> Cc: gen-art@ietf.org; draft-ietf-storm-ipsec-ips-update.all@tools.ietf.or=
g
> Subject: Re: [Gen-art] review of draft-ietf-storm-ipsec-ips-update-03.txt
>=20
>  In your previous mail you wrote:
>=20
> > Thank you for the review.  I have made all three changes in my
> > working version that will become the -04.
>=20
> =3D> thanks, I raised the status to "Ready" even the -04 doesn't seem
> to be available in the tools.ietf.org I-D repository?
>=20
> Francis.Dupont@fdupont.fr
>=20
> PS: the draft-ietf-storm-ipsec-ips-update is at the IESG agenda
> of the 2013-08-29 teleconf
> (cf http://datatracker.ietf.org/iesg/agenda/)


From ron.even.tlv@gmail.com  Wed Aug 28 08:25:25 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A09FC11E81FE; Wed, 28 Aug 2013 08:25:25 -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 Dii-V+9ZX1HA; Wed, 28 Aug 2013 08:25:25 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id E896E11E81BD; Wed, 28 Aug 2013 08:25:23 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id e11so2350211wgh.33 for <multiple recipients>; Wed, 28 Aug 2013 08:25:21 -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:content-transfer-encoding:thread-index :content-language; bh=OPIjaM97TcBH5tn4aWo8b40YpCiRSaDFfIGQfT3oMnA=; b=RMwsWjxf6jxqgru7jPTsjfcF5pXc+8uQkn274aR89e78uEr0JcBcKoW2bYhUmaV3Ix Zi1CbpQWoVQpv5mTn+ChMM3x2gHTkqyb7QBZtAqIht8eQoDZjoHpaI3W9EMp9VpwD9h7 DitT1oXm2l0ZPVygnkW9fya1cc4uU1VGPezRlCNIIjh9PB78ZayXS7FmgaMtQYGEkq+D sw5TFtgqUpYSFNl/Mx1lIEt9IFYCzbaizAR/RlnXkGnu732pe9pUWQBLWCmF7lkEakNr vAtALy/dhQsyEpJ65fZQdLRFhsSduMKKpdKDD/lHBCQmJTgnhRNfKzzDjzgqBfge5oaa S5aA==
X-Received: by 10.194.250.69 with SMTP id za5mr2967820wjc.80.1377703521719; Wed, 28 Aug 2013 08:25:21 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id iz19sm5825241wic.9.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 28 Aug 2013 08:25:21 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Loa Andersson'" <loa@pi.nu>
References: <041001cea3ef$6a931b60$3fb95220$@gmail.com> <521E071F.7050607@pi.nu>
In-Reply-To: <521E071F.7050607@pi.nu>
Date: Wed, 28 Aug 2013 18:22:52 +0300
Message-ID: <042801cea402$77bf5200$673df600$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI9zAalsB4SCJWxv5dBStZUqxRAeQE/hjT7mMJs2uA=
Content-Language: en-us
Cc: gen-art@ietf.org, draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-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: Wed, 28 Aug 2013 15:25:25 -0000

Hi Loa,
See inline
Roni

> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.nu]
> Sent: 28 August, 2013 5:20 PM
> To: Roni Even
> Cc: draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org;
gen-
> art@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART LC review of
draft-ietf-mpls-return-path-specified-lsp-
> ping-12
> 
> Roni,
> 
> Thanks for an insightful review, you have captured much of what we been
> struggling with when it comes to the IANA allocations.
> 
> On 2013-08-28 15:06, Roni Even wrote:
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > Summary: This draft is almost ready for publication as a standard track
RFC.
> >
> > Major issues:
> >
> > Minor issues:
> >
> > I am not clear on the sub-TLV in section 6.2
> >
> >  1. If a new sub-TLV is defined for TLV type 1 do they need also to be
> >     added to TLV type 21.
> 
> Yes the document says "Directly copied from TLV Type 1, MUST NOT be
> assigned" the intention is that this applies to future sub-TLVs also.
> I guess it could be changed to "Directly copied from TLV Type 1 (including
> future allocations for TLV Type 1, MUST NOT be assigned"
> if that makes thing clearer.
> 
> >     This should be clear, and if there is some
> >     relation I think it should be reflected in the IANA registry for TLV
> >     type 1
> 
> I guess that makes sense - but it has not been the what we've done earlier
- I
> think we could add this where needed by directly communicate  this to
IANA.


[Roni Even] I think that the directive for future allocation must be clear
both in the IANA registry and the document for example look at
http://tools.ietf.org/html/rfc6426#section-7.3 
I also think that is this case this document updates RFC4379 .

> 
> >  2. For the vendor or private use why a difference policy than the rest
> >     of the sub-TLV registry
> 
> We don't assign vendor private use at all, so by default it is different.
I don't
> see that it could be different.> 
[Roni Even] RFC4379 says 
"If a TLV or sub-TLV has a Type that falls in the range for Vendor
   Private Use, the Length MUST be at least 4, and the first four octets
   MUST be that vendor's SMI Private Enterprise Number, in network octet
   order.  The rest of the Value field is private to the vendor."

> /Loa
> >
> > Nits/editorial comments:
> >
> >  1. In section 3.4 I assume that "TC" is traffic class. It will be good
> >     to expand and have reference.
> >
> 
> --
> 
> 
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64


From jari.arkko@piuha.net  Wed Aug 28 08:36:00 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 729FC11E81AC; Wed, 28 Aug 2013 08:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.601
X-Spam-Level: 
X-Spam-Status: No, score=-102.601 tagged_above=-999 required=5 tests=[AWL=-0.002, 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 jRefeZus73M3; Wed, 28 Aug 2013 08:35:56 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 19C4511E81A4; Wed, 28 Aug 2013 08:35:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 454512CC5B; Wed, 28 Aug 2013 18:35:48 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QmEURBkv7K2C; Wed, 28 Aug 2013 18:35:47 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3061E2CC50; Wed, 28 Aug 2013 18:35:47 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA0C08D2@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 28 Aug 2013 18:35:46 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <14B40768-44A0-4ECE-9904-70F044EA2C16@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA07867E@AZ-FFEXMB04.global.avaya.com> <62DC16C614A9554F81C8E2E5C174A98838DA0C7742@CHN-HCLT-EVS16.HCLT.CORP.HCL.IN>, <9904FB1B0159DA42B0B887B7FA8119CA0C06C6@AZ-FFEXMB04.global.avaya.com> <62DC16C614A9554F81C8E2E5C174A98838DA0C7744@CHN-HCLT-EVS16.HCLT.CORP.HCL.IN> <9904FB1B0159DA42B0B887B7FA8119CA0C08D2@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1508)
Cc: Martin Stiemerling <Martin.Stiemerling@neclab.eu>, "mark_bakke@dell.com" <mark_bakke@dell.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "Prakash Venkatesen, ERS-HCLTech" <prakashvn@hcl.com>, "storm@ietf.org" <storm@ietf.org>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 15:36:00 -0000

Dan: Thank you very much your review. And Prakash, thank you for =
addressing Dan's concerns. I'm happy to recommend the document for =
approval in our next telechat.

Jari

On Apr 3, 2013, at 3:20 PM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> =
wrote:

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


From jari.arkko@piuha.net  Wed Aug 28 08:43:49 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC8A011E80FA for <gen-art@ietfa.amsl.com>; Wed, 28 Aug 2013 08:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.601
X-Spam-Level: 
X-Spam-Status: No, score=-103.601 tagged_above=-999 required=5 tests=[AWL=0.998, BAYES_00=-2.599, GB_I_LETTER=-2, 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 Yc+vwdjL2HFH for <gen-art@ietfa.amsl.com>; Wed, 28 Aug 2013 08:43:45 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5898D11E81BA for <gen-art@ietf.org>; Wed, 28 Aug 2013 08:43:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9E8122CC50; Wed, 28 Aug 2013 18:43:44 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fd_9aEVTxn7v; Wed, 28 Aug 2013 18:43:43 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 9E4482CC46; Wed, 28 Aug 2013 18:43:43 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A133F1E@eusaamb107.ericsson.se>
Date: Wed, 28 Aug 2013 18:43:43 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <039D93DD-DE69-496B-B414-02BEEE7E2D90@piuha.net>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A133F1E@eusaamb107.ericsson.se>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-alto-server-discovery.all@tools.ietf.org" <draft-ietf-alto-server-discovery.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-alto-server-discovery-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 15:43:49 -0000

Meral: Thank you very much your review. I did not see a response to your =
review, but maybe it was sent privately. In any case, the suggested =
edits seem to be included in the new version so, with your review and my =
quick review, I'll be happy to recommend the approval of the draft.

Jari

On Jun 21, 2013, at 8:54 AM, Meral Shirazipour =
<meral.shirazipour@ericsson.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq  .
> =20
> Please resolve these comments along with any other Last Call comments =
you may receive.
> =20
> Document: draft-ietf-alto-server-discovery-08
> Reviewer: Meral Shirazipour
> Review Date: 2013-06-20
> IETF LC End Date: 2013-06-20
> IESG Telechat date: NA
> =20
> =20
> Summary:
> This draft is almost ready to be published as Standards Track RFC but =
I do have some comments.
> =20
> Nits/editorial comments:
> -[Page 4], 2nd line before last, "funcional"--typo-->"functional"
> -[Page 5], Section 2, Point 2, "neccessary"--typo-->"necessary"
> -[Page 5], 2nd paragraph before last, "whishes"--typo-->"wishes"
> -[Page 5], last paragraph, "neccessarily"--typo-->"necessarily"
> -[Page 6], Section 3.1.1.
> "If DHCP-based discovery succeeds the software SHOULD inform the user =
that the user input has been ignored and replaced by information =
retrieved from the network."
> Suggestion to put "," after "If DHCP-based discovery succeeds".
> -[Page 8], Section 4, line 3, "mobilility"--typo-->"mobility"
> -[Page 8], Section 4, paragraph 2, "familly"--typo-->"family"
> -[Page 8], Section 4, paragraph 2, "familiy"--typo-->"family"
> -[Page 9], last line, "corrsponding"--typo-->"corresponding"
> -[Page 11], paragraph 3, "anormalities"--typo-->"abnormalities"
> -[page 12]
> "The security aspects of obtaining the domain name that is used for =
input to the U-NAPTR process is described in respective documents, such =
as [RFC5986]."
> Refers to more than one documents but only lists RFC5986. It would be =
better to either list the other documents or say "described in =
[RFC5986]."
> -[Page 13], Section 7.2, Ref. [I-D.ietf-alto-protocol] points to older =
version.
> -[Page 13], Section 7.2, Ref. [I-D.kist-alto-3pdisc] points to older =
version.
> -General, please consider spelling out acronyms when first used. Also =
using a common way (first letters capital or not):
> "network address translation (NAT)" versus "Virtual Private Network =
(VPN)"
> =20
> Best Regards,
> Meral
> ---
> Meral Shirazipour
> Ericsson
> Research
> www.ericsson.com
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From meral.shirazipour@ericsson.com  Thu Aug 29 01:24:24 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DF8D21E8092 for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 01:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WgQnISL0VBLW for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 01:24:18 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id C98F921F9A05 for <gen-art@ietf.org>; Thu, 29 Aug 2013 01:23:56 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-e2-521f051a1196
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 1D.C3.09414.A150F125; Thu, 29 Aug 2013 10:23:54 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0328.009; Thu, 29 Aug 2013 04:23:53 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "raft-ietf-repute-query-http.all@tools.ietf.org" <raft-ietf-repute-query-http.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-repute-query-http-09
Thread-Index: Ac6kkPXooOcV08hVTj2rU+UwNX/c+Q==
Date: Thu, 29 Aug 2013 08:23:53 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A630DF5@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A630DF5eusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyuXRPlK4Uq3yQwaX1ihZXX31msTjxfDu7 A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJWxoekCU8Fz44p3X5YwNTAe0O1i5OSQEDCR 2PzzHRuELSZx4d56MFtI4CijxOVJgV2MXED2ckaJ6e1TWUASbAIWEtt/P2cFSYgITGCUWHNl KitIQljARWLnx3WMILaIgKfEkZnLmSFsPYm5PfuBbA4OFgFViUdXRUDCvALeEo3NT8FmMgIt /n5qDROIzSwgLnHryXwmiIMEJJbsOc8MYYtKvHz8jxXCVpb4PucRC0R9vsS+rjOsEDMFJU7O fMIygVFoFpJRs5CUzUJSBhHXkViw+xMbhK0tsWzha2YY+8yBx0zI4gsY2VcxcpQWp5blphsZ bGIERsMxCTbdHYx7XloeYpTmYFES512ldyZQSCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dUA6P6 Tmmvbcsi79yyyPv73LFWj2fzrEnJ0xlDj8trS6y60Khv+8LT1uHB6llXZkZutpXln6b3WpPZ 0GrF904PbmmXlWHu2p2BAhO5lSX1tn479HDJk+rA73tmx3/elZp0QlrofOVt0w5vA6mwm3nn tl/s3Lhd8N/vbQW6jFmup6wDKpl3/lKQWqPEUpyRaKjFXFScCACyxc0MVAIAAA==
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-repute-query-http-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 08:24:24 -0000

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

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

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

Document: draft-ietf-repute-query-http-09
Reviewer: Meral Shirazipour
Review Date: 2013-08-29
IETF LC End Date:  2013-08-29
IESG Telechat date: 2013-09-12


Summary:
This draft is almost ready to be published as Standards Track RFC but I hav=
e some comments.


Nits/editorial comments:
Nits:
-[Page 4], line 2, "attributies" --typo-->"attributes"
-[Page 4], line 8, "support support" ----> remove duplicate
-[Page 4], line 5 before last, "is cable of" ----->"is capable of"
-[Page 4], line 4 before last, "until finds" ----->"until it finds"
-[Page 5], Section 3.3, line 2, "[URI-TEMPLATE].  (See Section 3.2.)  ",  m=
isplaced dot after the reference.
-[Page 6], line 2, "An media" --typo-->"A media"

comments:
-Not sure if it was forgotten or by choice: second author's affiliation is =
missing.
-Suggestion: for references to RFCs, it is better to use the [RFC####] as r=
eference in the text instead of ["name"].
-Section 4, please double check to make sure RFC5226 is followed.
-Appendix B, not sure if necessary since it is the WGs list and not some ot=
her mailing list.


Best Regards,
Meral
---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-repute-query-http-09<o:p></o:p>=
</p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-08-29<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date:&nbsp; 2013-08-29<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2013-09-12<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is almost ready to be published as Standa=
rds Track RFC but I have some comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">Nits:<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], line 2, &quot;attributies&quot; --typo--&=
gt;&quot;attributes&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], line 8, &quot;support support&quot; ----&=
gt; remove duplicate<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], line 5 before last, &quot;is cable of&quo=
t; -----&gt;&quot;is capable of&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], line 4 before last, &quot;until finds&quo=
t; -----&gt;&quot;until it finds&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 5], Section 3.3, line 2, &quot;[URI-TEMPLATE]=
.&nbsp; (See Section 3.2.)&nbsp; &quot;,&nbsp; misplaced dot after the refe=
rence.<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 6], line 2, &quot;An media&quot; --typo--&gt;=
&quot;A media&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-Not sure if it was forgotten or by choice: second a=
uthor's affiliation is missing.<o:p></o:p></p>
<p class=3D"MsoNormal">-Suggestion: for references to RFCs, it is better to=
 use the [RFC####] as reference in the text instead of [&quot;name&quot;].<=
o:p></o:p></p>
<p class=3D"MsoNormal">-Section 4, please double check to make sure RFC5226=
 is followed.<o:p></o:p></p>
<p class=3D"MsoNormal">-Appendix B, not sure if necessary since it is the W=
Gs list and not some other mailing list.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A630DF5eusaamb107ericsso_--

From meral.shirazipour@ericsson.com  Thu Aug 29 01:26:02 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 248CD21F9B6A for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 01:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T-E6+axwzv-g for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 01:25:54 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 7579421F8793 for <gen-art@ietf.org>; Thu, 29 Aug 2013 01:25:53 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-f6-521f0590a300
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 92.D3.09414.0950F125; Thu, 29 Aug 2013 10:25:53 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0328.009; Thu, 29 Aug 2013 04:25:52 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-repute-query-http.all@tools.ietf.org" <draft-ietf-repute-query-http.all@tools.ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-repute-query-http-09
Thread-Index: Ac6kkU8GOcc/k7z1Rr2UreUbccKhCQ==
Date: Thu, 29 Aug 2013 08:25:52 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A630E6A@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A630E6Aeusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsUyuXSPt+5EVvkggztLuC1enIu2uPrqM4sD k8eSJT+ZPL5c/swWwBTFZZOSmpNZllqkb5fAlXFxzW+2gtUmFcuXtrI2MDbqdTFyckgImEjc fH6ABcIWk7hwbz1bFyMXh5DAUUaJdbe+QjnLGSVObXvKDFLFJmAhsf33c1YQW0QgU2Lhg1Vg NrOApsSmpudsILawgIvEzo/rGCFqPCWOzFzODGHrSdzrmARmswioStxaNR2shlfAW+LSsStg VzACXfH91BomiJniEreezGeCuE5AYsme88wQtqjEy8f/WCFsZYnvcx6xQNTnS0w92ckMMVNQ 4uTMJywTGIVnIRk1C0nZLCRlEHEdiQW7P7FB2NoSyxa+Zoaxzxx4zIQsvoCRfRUjR2lxallu upHBJkZglByTYNPdwbjnpeUhRmkOFiVx3lV6ZwKFBNITS1KzU1MLUovii0pzUosPMTJxcEo1 MGa3mnBt+LfX7xZb31OHd6Wy9166J+jcYpA8z5x57r7rohXx7DobJ4h23naTCmXN3qoaUcGm 5PUh/9qukoy+lfW7bfSjY66pGIWlLTAv7e03DvjOd+fS7X/Hjj9SUmaOPDzp2drwo1rZfRt3 /T3N9chp6vTjez7t2LRReG53teXjhRwVDaV2PEosxRmJhlrMRcWJAC/Gr4lgAgAA
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-repute-query-http-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 08:26:02 -0000

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

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at http://wiki.tools.ietf.org/area/gen/trac/wiki/GenA=
rtfaq .
Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-repute-query-http-09
Reviewer: Meral Shirazipour
Review Date: 2013-08-29
IETF LC End Date:  2013-08-29
IESG Telechat date: 2013-09-12


Summary:
This draft is almost ready to be published as Standards Track RFC but I hav=
e some comments.


Nits/editorial comments:
Nits:
-[Page 4], line 2, "attributies" --typo-->"attributes"
-[Page 4], line 8, "support support" ----> remove duplicate
-[Page 4], line 5 before last, "is cable of" ----->"is capable of"
-[Page 4], line 4 before last, "until finds" ----->"until it finds"
-[Page 5], Section 3.3, line 2, "[URI-TEMPLATE].  (See Section 3.2.)  ",  m=
isplaced dot after the reference.
-[Page 6], line 2, "An media" --typo-->"A media"

comments:
-Not sure if it was forgotten or by choice: second author's affiliation is =
missing.
-Suggestion: for references to RFCs, it is better to use the [RFC####] as r=
eference in the text instead of ["name"].
-Section 4, please double check to make sure RFC5226 is followed.
-Appendix B, not sure if necessary since it is the WGs list and not some ot=
her mailing list.


Best Regards,
Meral
---
Meral Shirazipour
Ericsson
Research
www.ericsson.com<http://www.ericsson.com>


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> .<o:p></o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-repute-query-http-09<o:p></o:p>=
</p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-08-29<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date:&nbsp; 2013-08-29<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2013-09-12<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is almost ready to be published as Standa=
rds Track RFC but I have some comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">Nits:<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], line 2, &quot;attributies&quot; --typo--&=
gt;&quot;attributes&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], line 8, &quot;support support&quot; ----&=
gt; remove duplicate<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], line 5 before last, &quot;is cable of&quo=
t; -----&gt;&quot;is capable of&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], line 4 before last, &quot;until finds&quo=
t; -----&gt;&quot;until it finds&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 5], Section 3.3, line 2, &quot;[URI-TEMPLATE]=
.&nbsp; (See Section 3.2.)&nbsp; &quot;,&nbsp; misplaced dot after the refe=
rence.<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 6], line 2, &quot;An media&quot; --typo--&gt;=
&quot;A media&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-Not sure if it was forgotten or by choice: second a=
uthor's affiliation is missing.<o:p></o:p></p>
<p class=3D"MsoNormal">-Suggestion: for references to RFCs, it is better to=
 use the [RFC####] as reference in the text instead of [&quot;name&quot;].<=
o:p></o:p></p>
<p class=3D"MsoNormal">-Section 4, please double check to make sure RFC5226=
 is followed.<o:p></o:p></p>
<p class=3D"MsoNormal">-Appendix B, not sure if necessary since it is the W=
Gs list and not some other mailing list.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://www.ericsson.com">www.ericsson.com=
</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A630E6Aeusaamb107ericsso_--

From ron.even.tlv@gmail.com  Thu Aug 29 02:23:58 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8B0F11E810C; Thu, 29 Aug 2013 02:23:57 -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 oCjqZLUbQV-H; Thu, 29 Aug 2013 02:23:57 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 9E02B11E8109; Thu, 29 Aug 2013 02:23:56 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id e11so161647wgh.33 for <multiple recipients>; Thu, 29 Aug 2013 02:23:54 -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:content-transfer-encoding:thread-index :content-language; bh=Tgj7/CB4UuBexTphdsz6va6OccZY4hz9+AIA+fSYiV4=; b=JBqEdgQU2mXnbcXgOKEBEZYQ6pGHrnmM10IrymaRzjqH36lVFMgSRBSf+TcET17GMl qpHhtQZH3MHnzfHjrsL0zqvX/0YdaoTZu0DRPSyvTC6KsPkIEK8ZE+FFGCeoC9qdAeoi U19M3gsJyt2BBGaZWST67rnE95TvUuIxZ1sfgrdwRPFk+UVjwd+y4VF3aNG9j9XCug3q T46wv1BpwMB1JhMz8NiDQX9lLQH5cRqP3CSsDekv3IHfEKuus1DwwHhD6R20cqZ0W9NU gBg68swPYIpgd6F2e4Ao8jDUgiagQQqkgeis13EmlIJolcxfc20OnQuyWJBnCnomzGyz 1mJQ==
X-Received: by 10.194.176.163 with SMTP id cj3mr4408016wjc.8.1377768233925; Thu, 29 Aug 2013 02:23:53 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id mb7sm10953960wic.10.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 29 Aug 2013 02:23:53 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Mach Chen'" <mach.chen@huawei.com>, <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com>
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com>
Date: Thu, 29 Aug 2013 12:21:23 +0300
Message-ID: <04cf01cea499$22eb4a80$68c1df80$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFOtCz/kupT/msuDkJxBc8cYmi4kAJrrZpSmphrvgA=
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-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, 29 Aug 2013 09:23:58 -0000

Hi,
I am not sure you responded to my latest email.

Having the policy for TLV type 1 here is not enough in my view since I only
look at RFC4379 and create a new TLV type I will not know that I have to
register it also for the type 21 if it will not be mentioned

As for the vendor specific see my other email
Roni

> -----Original Message-----
> From: Mach Chen [mailto:mach.chen@huawei.com]
> Sent: 29 August, 2013 11:33 AM
> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> ping.all@tools.ietf.org
> Cc: ietf@ietf.org; gen-art@ietf.org
> Subject: RE: Gen-ART LC review of
draft-ietf-mpls-return-path-specified-lsp-
> ping-12
> 
> Hi Roni,
> 
> Thanks for your detailed review and comments!
> 
> Please see my reply inline...
> 
> > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > Sent: Wednesday, August 28, 2013 9:06 PM
> > To: draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > Cc: ietf@ietf.org; gen-art@ietf.org
> > Subject: Gen-ART LC review of
> > draft-ietf-mpls-return-path-specified-lsp-ping-12
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > Reviewer: Roni Even
> > Review Date:2013-8-28
> > IETF LC End Date: 2013-9-4
> > IESG Telechat date:
> >
> > Summary: This draft is almost ready for publication as a standard track
RFC.
> >
> >
> > Major issues:
> > Minor issues:
> > I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV is
> > defined for TLV type 1 do they need also to be added to TLV type 21.
> > This should be clear, and if there is some relation I think it should
> > be reflected in the IANA registry for TLV type 1
> 
> Yes, type 21 TLV intends to reuse existing and future defined sub-TLVs for
> type TLV 1. And in Section 3.3, it has already stated this, it says:
> 
> "The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
>    identify a specific return path.  The Reply Path TLV can carry any
>    sub-TLV defined for use in the Target FEC Stack TLV that can be
>    registered."
> 
> So, for Section 6.2, to make it cleaner and more explicit, how about this
> change:
> 
> Old:
> 
> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>    are made directly for TLV Type 21, sub-TLVs in these ranges are
>    copied from the assignments made for TLV Type 1. Assignments of
sub-..."
> 
> New:
> 
> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>    are made directly for TLV Type 21, sub-TLVs in these ranges are
>    copied from the assignments (including existing and future allocations)
>    made for TLV Type 1. Assignments of sub-..."
> 
> 
> > 2. For the vendor or private use why a difference policy than the rest
> > of the sub-TLV registry
> 
> This document does not make any changes to the "Vendor and Private use"
> definition, range and policy as defined in RFC4379. In RFC4379, it's
policy is
> defined different from other ranges.
> 
> >
> > Nits/editorial comments:
> > 1. In section 3.4 I assume that "TC" is traffic class. It will be good
> > to expand and have reference.
> 
> OK, will fix it when all last call comments received.
> 
> Best regards,
> Mach


From Martin.Stiemerling@neclab.eu  Thu Aug 29 02:34:58 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6497D11E8110 for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 02:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.589
X-Spam-Level: 
X-Spam-Status: No, score=-104.589 tagged_above=-999 required=5 tests=[AWL=1.010, BAYES_00=-2.599, GB_I_LETTER=-2, 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 Sv8Av5mDAT7b for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 02:34:54 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id C5FA911E810A for <gen-art@ietf.org>; Thu, 29 Aug 2013 02:34:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 2D3E710558C; Thu, 29 Aug 2013 11:33:51 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id htcPux9vDw1h; Thu, 29 Aug 2013 11:33:51 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 11E44105585; Thu, 29 Aug 2013 11:33:36 +0200 (CEST)
Received: from [10.1.99.64] (10.1.99.64) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 29 Aug 2013 11:31:49 +0200
Message-ID: <521F1504.5070502@neclab.eu>
Date: Thu, 29 Aug 2013 11:31:48 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A133F1E@eusaamb107.ericsson.se>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A133F1E@eusaamb107.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.99.64]
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-alto-server-discovery.all@tools.ietf.org" <draft-ietf-alto-server-discovery.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-alto-server-discovery-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 09:34:58 -0000

Hi Meral,

Thanks for your review and we will address your editorials in the next 
update coming soon.

   Martin

On 06/21/2013 07:54 AM, Meral Shirazipour wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq  .
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-alto-server-discovery-08
>
> Reviewer: Meral Shirazipour
>
> Review Date: 2013-06-20
>
> IETF LC End Date: 2013-06-20
>
> IESG Telechat date: NA
>
> Summary:
>
> This draft is almost ready to be published as Standards Track RFC but I
> do have some comments.
>
> Nits/editorial comments:
>
> -[Page 4], 2nd line before last, "funcional"--typo-->"functional"
>
> -[Page 5], Section 2, Point 2, "neccessary"--typo-->"necessary"
>
> -[Page 5], 2nd paragraph before last, "whishes"--typo-->"wishes"
>
> -[Page 5], last paragraph, "neccessarily"--typo-->"necessarily"
>
> -[Page 6], Section 3.1.1.
>
> "If DHCP-based discovery succeeds the software SHOULD inform the user
> that the user input has been ignored and replaced by information
> retrieved from the network."
>
> Suggestion to put "," after "If DHCP-based discovery succeeds".
>
> -[Page 8], Section 4, line 3, "mobilility"--typo-->"mobility"
>
> -[Page 8], Section 4, paragraph 2, "familly"--typo-->"family"
>
> -[Page 8], Section 4, paragraph 2, "familiy"--typo-->"family"
>
> -[Page 9], last line, "corrsponding"--typo-->"corresponding"
>
> -[Page 11], paragraph 3, "anormalities"--typo-->"abnormalities"
>
> -[page 12]
>
> "The security aspects of obtaining the domain name that is used for
> input to the U-NAPTR process is described in respective documents, such
> as [RFC5986]."
>
> Refers to more than one documents but only lists RFC5986. It would be
> better to either list the other documents or say "described in [RFC5986]."
>
> -[Page 13], Section 7.2, Ref. [I-D.ietf-alto-protocol] points to older
> version.
>
> -[Page 13], Section 7.2, Ref. [I-D.kist-alto-3pdisc] points to older
> version.
>
> -General, please consider spelling out acronyms when first used. Also
> using a common way (first letters capital or not):
>
> "network address translation (NAT)" versus "Virtual Private Network (VPN)"
>
> Best Regards,
>
> Meral
>
> ---
>
> Meral Shirazipour
>
> Ericsson
>
> Research
>
> www.ericsson.com
>

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From jari.arkko@piuha.net  Thu Aug 29 02:59:23 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E8AC21F9EF4; Thu, 29 Aug 2013 02:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.475
X-Spam-Level: 
X-Spam-Status: No, score=-101.475 tagged_above=-999 required=5 tests=[AWL=-1.176, BAYES_00=-2.599, MANGLED_LIST=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 cd8bq78UQHAW; Thu, 29 Aug 2013 02:59:12 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id E1EAE21F9F19; Thu, 29 Aug 2013 02:59:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5C4382CC54; Thu, 29 Aug 2013 12:59:07 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIAn2P32oVi9; Thu, 29 Aug 2013 12:59:06 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 55A9B2CC50; Thu, 29 Aug 2013 12:59:06 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CE1EC68E.5B19%peter@akayla.com>
Date: Thu, 29 Aug 2013 12:59:06 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <65B21C40-435C-45DB-8E64-CEE73E728037@piuha.net>
References: <CE1EC68E.5B19%peter@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-geopriv-res-gw-lis-discovery.all@tools.ietf.org, "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-geopriv-res-gw-lis-discovery-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, 29 Aug 2013 09:59:24 -0000

Peter: Thank you very much for your review.=20

Based on this review and my own review, I am recommending the approval =
of this draft in today's telechat. (Note that other ADs have raised a =
number of other issues, some of which I agree with, but I did not want =
to repeat their comments.)

Jari

On Jul 31, 2013, at 11:50 PM, Peter Yee <peter@akayla.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Document: draft-ietf-geopriv-res-gw-lis-discovery-05
> Reviewer: Peter Yee
> Review Date: Jul-31-2013
> IETF LC End Date: Jul-31-2013
> IESG Telechat date: TBD
>=20
> Summary: This draft is basically ready for publication, but has nits =
that
> should be fixed before publication. [Ready with nits.]
>=20
> The draft describes a means by which Devices behind a residential =
gateway
> may discover the correct Location Information Server on the access =
network
> providing Internet access to residential gateway.  The Device may =
thereby
> gain access to certain location-based services.
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits:
>=20
> Section 1, 1st paragraph, 2nd sentence: should "data" be appended
> after "location"?  The wording is otherwise odd.
>=20
> Page 7, 3rd paragraph: change "which" to "that".
>=20
> Page 9, section 4.2, 2nd paragraph, 1st sentence: I'll admit my =
ignorance
> of the finer points of the DNS and inquire what this sentence is =
supposed
> to mean.  To what are the additional domain names added and how does =
this
> allow a DNS record to cover a larger set of addresses?  Perhaps it's =
just
> the wording or my lack of knowledge, but I didn't follow this point =
fully.
>=20
> Page 9, section 4.2, 2nd bullet item: change "sucessively" to
> "successively".
>=20
> Page 11, section 4.6, 1st paragraph, 4th sentence: insert "a" before
> "STUN server" or change "server" to "servers" depending on how many
> need to be configured.
>=20
> Page 12, 1st sentence: delete "a".
>=20
> Page 12, 1st sentence: What about /56 for IPv6?
>=20
> Page 14, 3rd paragraph, 2nd sentence: delete "a" before
> "IP addresses" or change "addresses" to "address" depending on
> how many false addresses you mean.
>=20
> Page 14, 6th paragraph, last sentence: Are there any concrete
> suggestions on who a device might determine accuracy?
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From ron.even.tlv@gmail.com  Thu Aug 29 03:27:12 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21A4521F9B8A; Thu, 29 Aug 2013 03:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Kr5GP1oKVUmE; Thu, 29 Aug 2013 03:27:11 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC8A21F9CA8; Thu, 29 Aug 2013 03:27:09 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id q58so234827wes.11 for <multiple recipients>; Thu, 29 Aug 2013 03:27:08 -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:content-transfer-encoding:thread-index :content-language; bh=12I2Qk2wcGdRuI2OutOi0wUwTaUYNePL/nsso8VHbiA=; b=l8iztrY4b8nYHJAPu4iqImgmE1Z4QHPCqLjneLbF6iK9BdHpwOyaZ+CjzwSl8389eu aBQo4oQ3eaUIhi9QAsdI54/8CWgmLzHaXRnn2pUMB1feX8E0ArKVxgssxPqvIpvpINWG zU7WESvgkP3/nAUXr+R89Md2kmdk+HE+CzgO7UgJillwg9rFHToBslgdKt04Ai/yYSXG j15/xJBZEKJyEtV1Z6xhHk42HUa49eLwHeAknbhEaN2bEkQwh1ymp1afykUUBvfh5JFb P+IBHnyq/ePZs84GrYqPLRmvCvb++vlK1IZ647EGYLZ9KTI85ovGy1CmgY4F06kLDhIl Otkg==
X-Received: by 10.194.109.68 with SMTP id hq4mr4967067wjb.12.1377772028762; Thu, 29 Aug 2013 03:27:08 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id i8sm11388391wib.1.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 29 Aug 2013 03:27:08 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Mach Chen'" <mach.chen@huawei.com>, <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com> <04cf01cea499$22eb4a80$68c1df80$@gmail.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com>
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com>
Date: Thu, 29 Aug 2013 13:24:38 +0300
Message-ID: <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFOtCz/kupT/msuDkJxBc8cYmi4kAJrrZpSAxjw2zQBgMlGEZpzr4RQ
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-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, 29 Aug 2013 10:27:12 -0000

Hi,
This text is OK if one wants to implement this draft.
My concern was about the consistency of the IANA registration so that if
someone defines a new TLV type 1 based on RFC4379, IANA will know that it
must update also the registry for TLV type 21. If you see no such problem, I
have no concerns
Roni

> -----Original Message-----
> From: Mach Chen [mailto:mach.chen@huawei.com]
> Sent: 29 August, 2013 1:05 PM
> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> ping.all@tools.ietf.org
> Cc: ietf@ietf.org; gen-art@ietf.org
> Subject: RE: Gen-ART LC review of
draft-ietf-mpls-return-path-specified-lsp-
> ping-12
> 
> Hi Roni,
> 
> How about this:
> 
> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>     are made directly for TLV Type 21, sub-TLVs in these ranges are
>     copied from the assignments made for TLV Type 1 and kept the same
>     as that for TLV Type 1. All sub-TLVs in these ranges (include existing
>     and future defined) defined for TLV Type 1 apply to TLV Type 21.
>     Assignments of sub-..."
> 
> Best regards,
> Mach
> 
> > -----Original Message-----
> > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > Sent: Thursday, August 29, 2013 5:21 PM
> > To: Mach Chen;
> > draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > Cc: ietf@ietf.org; gen-art@ietf.org
> > Subject: RE: Gen-ART LC review of
> > draft-ietf-mpls-return-path-specified-lsp-ping-12
> >
> > Hi,
> > I am not sure you responded to my latest email.
> >
> > Having the policy for TLV type 1 here is not enough in my view since I
> > only look at RFC4379 and create a new TLV type I will not know that I
> > have to register it also for the type 21 if it will not be mentioned
> >
> > As for the vendor specific see my other email Roni
> >
> > > -----Original Message-----
> > > From: Mach Chen [mailto:mach.chen@huawei.com]
> > > Sent: 29 August, 2013 11:33 AM
> > > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > > ping.all@tools.ietf.org
> > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > Subject: RE: Gen-ART LC review of
> > draft-ietf-mpls-return-path-specified-lsp-
> > > ping-12
> > >
> > > Hi Roni,
> > >
> > > Thanks for your detailed review and comments!
> > >
> > > Please see my reply inline...
> > >
> > > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > > Sent: Wednesday, August 28, 2013 9:06 PM
> > > > To:
> > > > draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > Subject: Gen-ART LC review of
> > > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > >
> > > > I am the assigned Gen-ART reviewer for this draft. For background
> > > > on Gen-ART, please see the FAQ at
> > > > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > > > Please resolve these comments along with any other Last Call
> > > > comments you may receive.
> > > > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > > Reviewer: Roni Even
> > > > Review Date:2013-8-28
> > > > IETF LC End Date: 2013-9-4
> > > > IESG Telechat date:
> > > >
> > > > Summary: This draft is almost ready for publication as a standard
> > > > track
> > RFC.
> > > >
> > > >
> > > > Major issues:
> > > > Minor issues:
> > > > I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV
> > > > is defined for TLV type 1 do they need also to be added to TLV type
21.
> > > > This should be clear, and if there is some relation I think it
> > > > should be reflected in the IANA registry for TLV type 1
> > >
> > > Yes, type 21 TLV intends to reuse existing and future defined
> > > sub-TLVs for type TLV 1. And in Section 3.3, it has already stated
this, it
> says:
> > >
> > > "The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
> > >    identify a specific return path.  The Reply Path TLV can carry any
> > >    sub-TLV defined for use in the Target FEC Stack TLV that can be
> > >    registered."
> > >
> > > So, for Section 6.2, to make it cleaner and more explicit, how about
> > > this
> > > change:
> > >
> > > Old:
> > >
> > > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> > >    are made directly for TLV Type 21, sub-TLVs in these ranges are
> > >    copied from the assignments made for TLV Type 1. Assignments of
> > sub-..."
> > >
> > > New:
> > >
> > > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> > >    are made directly for TLV Type 21, sub-TLVs in these ranges are
> > >    copied from the assignments (including existing and future
allocations)
> > >    made for TLV Type 1. Assignments of sub-..."
> > >
> > >
> > > > 2. For the vendor or private use why a difference policy than the
> > > > rest of the sub-TLV registry
> > >
> > > This document does not make any changes to the "Vendor and Private
> use"
> > > definition, range and policy as defined in RFC4379. In RFC4379, it's
> > policy is
> > > defined different from other ranges.
> > >
> > > >
> > > > Nits/editorial comments:
> > > > 1. In section 3.4 I assume that "TC" is traffic class. It will be
> > > > good to expand and have reference.
> > >
> > > OK, will fix it when all last call comments received.
> > >
> > > Best regards,
> > > Mach


From jari.arkko@piuha.net  Thu Aug 29 03:37:04 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6118121F9DED for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 03:37:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, 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 UaJvc3Dl7tJR for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 03:36:42 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id BD0AA21F9DD0 for <gen-art@ietf.org>; Thu, 29 Aug 2013 03:36:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A55852CC54; Thu, 29 Aug 2013 13:36:40 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id puLX6Q0sVNtY; Thu, 29 Aug 2013 13:36:39 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id CB3CE2CC50; Thu, 29 Aug 2013 13:36:39 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C6755B7@MX15A.corp.emc.com>
Date: Thu, 29 Aug 2013 13:36:39 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F4EC385-1F79-4B25-A851-A6EC16378199@piuha.net>
References: Your message of Thu, 15 Aug 2013 07:42:06 EDT. <8D3D17ACE214DC429325B2B98F3AE7129C2B7C4B@MX15A.corp.emc.com> <201308281304.r7SD4v8Y071846@givry.fdupont.fr> <8D3D17ACE214DC429325B2B98F3AE7129C6755B7@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-storm-ipsec-ips-update.all@tools.ietf.org" <draft-ietf-storm-ipsec-ips-update.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-storm-ipsec-ips-update-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 10:37:05 -0000

Thank you Francis for your review and David for you attention to the =
comments. I have placed a No-Objection ballot for the draft.

Jari

On Aug 28, 2013, at 5:51 PM, "Black, David" <david.black@emc.com> wrote:

> Thank you - the -04 will appear after the results of the IETF telechat
> on Thursday, probably sometime next week, as there are some additional =
changes
> that will be necessary.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
>> Sent: Wednesday, August 28, 2013 9:05 AM
>> To: Black, David
>> Cc: gen-art@ietf.org; =
draft-ietf-storm-ipsec-ips-update.all@tools.ietf.org
>> Subject: Re: [Gen-art] review of =
draft-ietf-storm-ipsec-ips-update-03.txt
>>=20
>> In your previous mail you wrote:
>>=20
>>> Thank you for the review.  I have made all three changes in my
>>> working version that will become the -04.
>>=20
>> =3D> thanks, I raised the status to "Ready" even the -04 doesn't seem
>> to be available in the tools.ietf.org I-D repository?
>>=20
>> Francis.Dupont@fdupont.fr
>>=20
>> PS: the draft-ietf-storm-ipsec-ips-update is at the IESG agenda
>> of the 2013-08-29 teleconf
>> (cf http://datatracker.ietf.org/iesg/agenda/)
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Thu Aug 29 03:51:36 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD56821F9CE3 for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 03:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, 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 pqsG0CLm98pG for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 03:51:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 2466521F9BF3 for <gen-art@ietf.org>; Thu, 29 Aug 2013 03:51:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 90CB02CC54; Thu, 29 Aug 2013 13:51:29 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Mt6CBrJTqLb; Thu, 29 Aug 2013 13:51:28 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id A99002CC50; Thu, 29 Aug 2013 13:51:28 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C476333@ESESSMB209.ericsson.se>
Date: Thu, 29 Aug 2013 13:51:28 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <8418AB42-8D9E-4EFE-B48F-9D453708770B@piuha.net>
References: <7594FB04B1934943A5C02806D1A2204B1C476333@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-6man-addr-select-opt.all@tools.ietf.org" <draft-ietf-6man-addr-select-opt.all@tools.ietf.org>
Subject: Re: [Gen-art] Genart review of draft-ietf-6man-addr-select-opt-11.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, 29 Aug 2013 10:51:36 -0000

Christer: thank you for your review!

Jari

On Aug 23, 2013, at 9:27 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at < =
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> =20
> Please wait for direction from your document shepherd or AD before =
posting a new version of the draft.
> =20
> Document: draft-ietf-6man-addr-select-opt-11.txt
> Reviewer: Christer Holmberg
> Review Date: 23 August 2013
> IETF LC End Date: 15 May, 2013
> IESG Telechat date: 29 August, 2013
> =20
> Summary: The minor editorial issue I had on the previous version (-10) =
of the draft has been addressed. The document is ready for publication, =
without any further comments.
> =20
> Major issues: -
> =20
> Minor issues: -
> =20
> Nits/editorial comments: -
> =20
> Regards,
> =20
> Christer
> =20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From loa@pi.nu  Thu Aug 29 04:46:25 2013
Return-Path: <loa@pi.nu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31AF321F9D9C; Thu, 29 Aug 2013 04:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3PssOf5XD6XP; Thu, 29 Aug 2013 04:46:20 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3814A21F9D99; Thu, 29 Aug 2013 04:46:20 -0700 (PDT)
Received: from [192.168.5.58] (81-229-83-119-no65.business.telia.com [81.229.83.119]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 8E89118033E4; Thu, 29 Aug 2013 13:46:18 +0200 (CEST)
Message-ID: <521F3489.1060600@pi.nu>
Date: Thu, 29 Aug 2013 13:46:17 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com> <04cf01cea499$22eb4a80$68c1df80$@gmail.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com> <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com>
In-Reply-To: <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org, gen-art@ietf.org, 'Mach Chen' <mach.chen@huawei.com>, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-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, 29 Aug 2013 11:46:25 -0000

Roni,

tnx - the authors should add words in the IANA section requesting that
IANA add this the pointed in the registry; they normally do anyway, but
writing it down should not be a problem.

As for "Vendor Private" RFC 4379 says:

   "Values from "Vendor Private" ranges MUST NOT be registered with IANA;
    however, the message MUST contain an enterprise code as registered
    with the IANA SMI Private Network Management Private Enterprise
    Numbers.  For each name space that has a Vendor Private range, it
    must be specified where exactly the SMI Private Enterprise Number
    resides; see below for examples.  In this way, several enterprises
    (vendors) can use the same code point without fear of collision."

The way I read this is that the paragraph does two things (1) defines
the allocation policy (in this case that "vendor private" won't be
assigned by IANA) and (2) put a restriction on the "vendor private"
(sub-)TLVs; they must contain a "private enterprise number".

Up to now I've thought the restriction on the format was global for
all "vendor private" sub-TLVs that are used by TLV for LSP Ping.
However we put words to the same effect in e.g. 6424, wo there is no
reason not to do it here also. A pointer to RFC4379 should be enough
e.g.:

"For the vendor private sub-TLVs defined for this document, the
same allocation policies and requirement on the sub-TLV format that is
specified for vendor private sub-TLVs in RFC4379 [RFC4379] appliacable."

Would that cover you concern?

/Loa



On 2013-08-29 12:24, Roni Even wrote:
> Hi,
> This text is OK if one wants to implement this draft.
> My concern was about the consistency of the IANA registration so that if
> someone defines a new TLV type 1 based on RFC4379, IANA will know that it
> must update also the registry for TLV type 21. If you see no such problem, I
> have no concerns
> Roni
>
>> -----Original Message-----
>> From: Mach Chen [mailto:mach.chen@huawei.com]
>> Sent: 29 August, 2013 1:05 PM
>> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
>> ping.all@tools.ietf.org
>> Cc: ietf@ietf.org; gen-art@ietf.org
>> Subject: RE: Gen-ART LC review of
> draft-ietf-mpls-return-path-specified-lsp-
>> ping-12
>>
>> Hi Roni,
>>
>> How about this:
>>
>> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>>      are made directly for TLV Type 21, sub-TLVs in these ranges are
>>      copied from the assignments made for TLV Type 1 and kept the same
>>      as that for TLV Type 1. All sub-TLVs in these ranges (include existing
>>      and future defined) defined for TLV Type 1 apply to TLV Type 21.
>>      Assignments of sub-..."
>>
>> Best regards,
>> Mach
>>
>>> -----Original Message-----
>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>>> Sent: Thursday, August 29, 2013 5:21 PM
>>> To: Mach Chen;
>>> draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
>>> Cc: ietf@ietf.org; gen-art@ietf.org
>>> Subject: RE: Gen-ART LC review of
>>> draft-ietf-mpls-return-path-specified-lsp-ping-12
>>>
>>> Hi,
>>> I am not sure you responded to my latest email.
>>>
>>> Having the policy for TLV type 1 here is not enough in my view since I
>>> only look at RFC4379 and create a new TLV type I will not know that I
>>> have to register it also for the type 21 if it will not be mentioned
>>>
>>> As for the vendor specific see my other email Roni
>>>
>>>> -----Original Message-----
>>>> From: Mach Chen [mailto:mach.chen@huawei.com]
>>>> Sent: 29 August, 2013 11:33 AM
>>>> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
>>>> ping.all@tools.ietf.org
>>>> Cc: ietf@ietf.org; gen-art@ietf.org
>>>> Subject: RE: Gen-ART LC review of
>>> draft-ietf-mpls-return-path-specified-lsp-
>>>> ping-12
>>>>
>>>> Hi Roni,
>>>>
>>>> Thanks for your detailed review and comments!
>>>>
>>>> Please see my reply inline...
>>>>
>>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>>>>> Sent: Wednesday, August 28, 2013 9:06 PM
>>>>> To:
>>>>> draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
>>>>> Cc: ietf@ietf.org; gen-art@ietf.org
>>>>> Subject: Gen-ART LC review of
>>>>> draft-ietf-mpls-return-path-specified-lsp-ping-12
>>>>>
>>>>> I am the assigned Gen-ART reviewer for this draft. For background
>>>>> on Gen-ART, please see the FAQ at
>>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>> Please resolve these comments along with any other Last Call
>>>>> comments you may receive.
>>>>> Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
>>>>> Reviewer: Roni Even
>>>>> Review Date:2013-8-28
>>>>> IETF LC End Date: 2013-9-4
>>>>> IESG Telechat date:
>>>>>
>>>>> Summary: This draft is almost ready for publication as a standard
>>>>> track
>>> RFC.
>>>>>
>>>>>
>>>>> Major issues:
>>>>> Minor issues:
>>>>> I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV
>>>>> is defined for TLV type 1 do they need also to be added to TLV type
> 21.
>>>>> This should be clear, and if there is some relation I think it
>>>>> should be reflected in the IANA registry for TLV type 1
>>>>
>>>> Yes, type 21 TLV intends to reuse existing and future defined
>>>> sub-TLVs for type TLV 1. And in Section 3.3, it has already stated
> this, it
>> says:
>>>>
>>>> "The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
>>>>     identify a specific return path.  The Reply Path TLV can carry any
>>>>     sub-TLV defined for use in the Target FEC Stack TLV that can be
>>>>     registered."
>>>>
>>>> So, for Section 6.2, to make it cleaner and more explicit, how about
>>>> this
>>>> change:
>>>>
>>>> Old:
>>>>
>>>> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>>>>     are made directly for TLV Type 21, sub-TLVs in these ranges are
>>>>     copied from the assignments made for TLV Type 1. Assignments of
>>> sub-..."
>>>>
>>>> New:
>>>>
>>>> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>>>>     are made directly for TLV Type 21, sub-TLVs in these ranges are
>>>>     copied from the assignments (including existing and future
> allocations)
>>>>     made for TLV Type 1. Assignments of sub-..."
>>>>
>>>>
>>>>> 2. For the vendor or private use why a difference policy than the
>>>>> rest of the sub-TLV registry
>>>>
>>>> This document does not make any changes to the "Vendor and Private
>> use"
>>>> definition, range and policy as defined in RFC4379. In RFC4379, it's
>>> policy is
>>>> defined different from other ranges.
>>>>
>>>>>
>>>>> Nits/editorial comments:
>>>>> 1. In section 3.4 I assume that "TC" is traffic class. It will be
>>>>> good to expand and have reference.
>>>>
>>>> OK, will fix it when all last call comments received.
>>>>
>>>> Best regards,
>>>> Mach
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From jari.arkko@piuha.net  Thu Aug 29 04:50:58 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE1A721F9EB0 for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 04:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, 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 vXepI7dfT1bm for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 04:50:53 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 534A321F8F07 for <gen-art@ietf.org>; Thu, 29 Aug 2013 04:50:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A29942CC54; Thu, 29 Aug 2013 14:50:52 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MDL44GDFdW80; Thu, 29 Aug 2013 14:50:51 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 5C3EE2CC50; Thu, 29 Aug 2013 14:50:51 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <FCC100FC8D6B034CB88CD8173B2DA1581F34EEA4@EXC-MBX03.tsn.tno.nl>
Date: Thu, 29 Aug 2013 14:50:51 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <27E24AC2-3C01-4101-94CE-2D42D39B1A9B@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199C1B@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34CC74@EXC-MBX03.tsn.tno.nl> <FCC100FC8D6B034CB88CD8173B2DA1581F34CDCD@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199D6F@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D281@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199E37@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D3C2@EXC-MBX03.tsn.tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA199EBA@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34D520@EXC-MBX03.tsn.tno.nl>, <9904FB1B0159DA42B0B887B7FA8119CA199F21@AZ-FFEXMB04.global.avaya.com> <3DFD3155-BBD9-4BE0-8912-81B92C93D3CB@tno.nl> <9904FB1B0159DA42B0B887B7FA8119CA19A0A6@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34EEA4@EXC-MBX03.tsn.t no.nl>
To: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
X-Mailer: Apple Mail (2.1508)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-avtcore-idms.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-avtcore-idms-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 11:50:58 -0000

Thank you Dan very, very much for your detailed review. And thank you =
Ray and others for addressing the points noted by Dan - I think the =
document has improved as a result. Thanks again. I have balloted =
no-objection for this document in today's IESG telechat.

Jari

On Jun 11, 2013, at 1:29 PM, "Brandenburg, R. (Ray) van" =
<ray.vanbrandenburg@tno.nl> wrote:

>=20
>=20
> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]=20
> Sent: maandag 10 juni 2013 19:00
> To: Brandenburg, R. (Ray) van
> Cc: avt@ietf.org; General Area Review Team; Roni Even =
(ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>=20
>=20
>=20
>=20
>=20
>> -----Original Message-----
>> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
>> Sent: Monday, June 10, 2013 7:19 PM
>> To: Romascanu, Dan (Dan)
>> Cc: avt@ietf.org; General Area Review Team; Roni Even=20
>> (ron.even.tlv@gmail.com); draft-ietf-avtcore-idms.all@tools.ietf.org
>> Subject: Re: Gen-ART review of draft-ietf-avtcore-idms-09
>>=20
>>=20
>>=20
>> On 10 jun. 2013, at 17:11, "Romascanu, Dan (Dan)" =
<dromasca@avaya.com>
>> wrote:
>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
>>>> Sent: Monday, June 10, 2013 6:06 PM
>>>> To: Romascanu, Dan (Dan)
>>>> Cc: avt@ietf.org; General Area Review Team; Roni Even=20
>>>> (ron.even.tlv@gmail.com);=20
>>>> draft-ietf-avtcore-idms.all@tools.ietf.org
>>>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>>>>=20
>>>>=20
>>>>=20
>>>> -----Original Message-----
>>>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
>>>> Sent: maandag 10 juni 2013 16:57
>>>> To: Brandenburg, R. (Ray) van
>>>> Cc: avt@ietf.org; General Area Review Team; Roni Even=20
>>>> (ron.even.tlv@gmail.com);=20
>>>> draft-ietf-avtcore-idms.all@tools.ietf.org
>>>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>> -----Original Message-----
>>>>> From: Brandenburg, R. (Ray) van [mailto:ray.vanbrandenburg@tno.nl]
>>>>> Sent: Monday, June 10, 2013 5:52 PM
>>>>> To: Romascanu, Dan (Dan)
>>>>> Cc: avt@ietf.org; General Area Review Team; Roni Even=20
>>>>> (ron.even.tlv@gmail.com);=20
>>>>> draft-ietf-avtcore-idms.all@tools.ietf.org
>>>>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>>>>>=20
>>>>> Hi Dan,
>>>>>=20
>>>>> See below...
>>>>>=20
>>>>> Best regards,
>>>>>=20
>>>>> Ray
>>>>>=20
>>>>> -----Original Message-----
>>>>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
>>>>> Sent: maandag 10 juni 2013 16:35
>>>>> To: Brandenburg, R. (Ray) van
>>>>> Cc: avt@ietf.org; General Area Review Team; Roni Even=20
>>>>> (ron.even.tlv@gmail.com);=20
>>>>> draft-ietf-avtcore-idms.all@tools.ietf.org
>>>>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>>>>>=20
>>>>>=20
>>>>> Yes, we seem to get closer and closer, focus on one last issue=20
>>>>> (and much agreement deleted)
>>>>>=20
>>>>> Thanks and Regards,
>>>>>=20
>>>>> Dan
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: Brandenburg, R. (Ray) van=20
>>>>>> [mailto:ray.vanbrandenburg@tno.nl]
>>>>>> Sent: Monday, June 10, 2013 5:27 PM
>>>>>> To: Romascanu, Dan (Dan)
>>>>>> Cc: avt@ietf.org; General Area Review Team; Roni Even=20
>>>>>> (ron.even.tlv@gmail.com);=20
>>>>>> draft-ietf-avtcore-idms.all@tools.ietf.org
>>>>>> Subject: RE: Gen-ART review of draft-ietf-avtcore-idms-09
>>>>>>=20
>>>>>> Hi Dan,
>>>>>>=20
>>>>>> Please see inline. We seem to be converging:)
>>>>>>=20
>>>>>> Ray
>>>>>=20
>>>>>>>> 7. In Section 8:
>>>>>>>>=20
>>>>>>>>  The timestamp is formatted based on the NTP
>>>>>>>>  timestamp format as specified in [RFC5905].  If this field is
>>>>>>> empty,
>>>>>>>>  then it SHALL be set to 0.  This field MAY be left empty if=20
>>>>>>>> none
>>>>>> or
>>>>>>>>  only one of the receivers reported on presentation
>>>> timestamps.
>>>>>>>>=20
>>>>>>>> Why a MAY here? Especially for the case when none of the=20
>>>>>>>> receivers reported, what content can be set there but 0 ?
>>>>>>>>=20
>>>>>>>> [Ray: I believe it should be up to the implementation to decide=20=

>>>>>>>> how it wants to handle the case of there being only one=20
>>>>>>>> receiver who reported on presentation timestamps].
>>>>>>>>=20
>>>>>>> [[DR]] OK, so the cases when none of the receivers reported and=20=

>>>>>>> one receiver only reported should be dealt with differently.=20
>>>>>>> This needs to be clarified.
>>>>>>>=20
>>>>>>> [Ray] What exactly is the problem with the MAY here? IMO it=20
>>>>>>> doesn't create any interop issues: whatever is the reason for=20
>>>>>>> setting the value to 0, to the client the end result is the =
same:
>>>> ignore it.
>>>>>>>=20
>>>>>>=20
>>>>>> [[DR]] In the case when none of the receivers reported we want to=20=

>>>>>> avoid leaving some garbage in this field which could be=20
>>>>>> interpreted differently - don't we?
>>>>>>=20
>>>>>> [Ray] I think I see where we disagree. The paragraph says: "If=20
>>>>>> this field is empty, then it SHALL be set to 0. This field MAY be=20=

>>>>>> left empty if none or only one of the receivers reported on=20
>>>>>> presentation timestamps". The way I read this is as: In the case=20=

>>>>>> the field is declared empty (=3D contains NULL information), it =
SHALL be set to 0.
>>>>>> There can be different reasons for declaring the field=20
>>>>>> empty/NULL, one of those reasons is if none or only one receiver=20=

>>>>>> reported on presentation timestamps. To me, the paragraph doesn't=20=

>>>>>> say that this is the only possible reason, but it does specify=20
>>>>>> very clearly that if you decide the field should be empty, you =
SHALL set it to zero.
>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>> [[DR]] But then, why do not you take out 'if none or' - because=20
>>>>> for the option of 'none' there is no alternative but the 'null'
>>>>> information, and the MAY does not make sense.
>>>>>=20
>>>>> [Ray] The fact that no receiver reported on the packet=20
>>>>> presentation timestamp does not necessarily mean that the MSAS=20
>>>>> does not want to indicate a proposed packet presentation=20
>>>>> timestamp. The absence of such reports just means that the=20
>>>>> proposed playout moment might not be realistic, or be supported by =
any receiver.
>>>>>=20
>>>>=20
>>>> [[DR]] yes, but is the field set to anything but 0 in such cases?
>>>>=20
>>>> [Ray] If the MSAS decides to leave the field empty, it is set to 0=20=

>>>> according to the SHALL. If the MSAS decides to include a timestamp=20=

>>>> anyway, it is set to whatever value the MSAS proposes.
>>>>=20
>>>=20
>>> [[DR]] So two different implementations may behave differently in
>> similar situations. Is this a problem?
>>>=20
>>=20
>> No, I don't think it is a problem if two different MSAS=20
>> implementations behave differently in this regard. I see it as=20
>> server-side configuration. Anyway, even if we would replace the MAY=20=

>> with a SHOULD or remove the sentence all together, there would still=20=

>> be different
>> implementations: for example, let's say we have a sync group of 12=20
>> devices, with 7 of them reporting presentation timestamps. What =
should=20
>> the MSAS do? Set the field in the IDMS Settings Packet to 0 or not? I=20=

>> feel this decision should be up to the implementation as I don't see=20=

>> an advantage to us specifying either one way or the other.
>>=20
>> Ray
>>=20
>=20
> [[DR]] The open issue is not about this case but about the case when =
no receiver reported. You say one MSAS implementation may treat this as =
null information setting the field to 0 (which would seem to me like the =
obvious thing to do), but other MSAS implementation may include a =
timestamp anyway (which one?). My question 'Is this a problem' was about =
this case?=20
>=20
> [Ray] I don't see a difference between the two cases: in both cases =
the MSAS can decide to send 'some' timestamp.  I'm not saying this is =
recommended, but I also don't see any interop issues. In any =
synchronization group there will be a maximum of 1 MSAS, so all =
receivers will receive the same presentation timestamp. What they do =
with that timestamp is up to the SCs themselves.=20
>=20
> Ray
>=20
> This e-mail and its contents are subject to the DISCLAIMER at =
http://www.tno.nl/emaildisclaimer
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From mach.chen@huawei.com  Thu Aug 29 01:33:08 2013
Return-Path: <mach.chen@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 1553F21F9E51; Thu, 29 Aug 2013 01:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oZiGKUDQU57P; Thu, 29 Aug 2013 01:33:04 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1B4B121F9E83; Thu, 29 Aug 2013 01:33:01 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AWR89767; Thu, 29 Aug 2013 08:33:01 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 09:32:11 +0100
Received: from SZXEML448-HUB.china.huawei.com (10.82.67.191) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 09:33:00 +0100
Received: from szxeml558-mbs.china.huawei.com ([169.254.8.196]) by szxeml448-hub.china.huawei.com ([10.82.67.191]) with mapi id 14.01.0323.007; Thu, 29 Aug 2013 16:32:53 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org" <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
Thread-Topic: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
Thread-Index: Ac6j72iTQaEc2KyVR6aJXw9+GJi+EwAZqLIAAA8JaoA=
Date: Thu, 29 Aug 2013 08:32:53 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com>
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.96.176]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Thu, 29 Aug 2013 05:13:40 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-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, 29 Aug 2013 08:33:08 -0000

Hi Roni,

Thanks for your detailed review and comments!

Please see my reply inline...

> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> Sent: Wednesday, August 28, 2013 9:06 PM
> To: draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> Cc: ietf@ietf.org; gen-art@ietf.org
> Subject: Gen-ART LC review of=20
> draft-ietf-mpls-return-path-specified-lsp-ping-12
>=20
> 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-ietf-mpls-return-path-specified-lsp-ping-12
> Reviewer: Roni Even
> Review Date:2013-8-28
> IETF LC End Date: 2013-9-4
> IESG Telechat date:
>=20
> Summary: This draft is almost ready for publication as a standard track R=
FC.
>=20
>=20
> Major issues:
> Minor issues:
> I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV is=20
> defined for TLV type 1 do they need also to be added to TLV type 21.=20
> This should be clear, and if there is some relation I think it should=20
> be reflected in the IANA registry for TLV type 1

Yes, type 21 TLV intends to reuse existing and future defined sub-TLVs for =
type TLV 1. And in Section 3.3, it has already stated this, it says:

"The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
   identify a specific return path.  The Reply Path TLV can carry any
   sub-TLV defined for use in the Target FEC Stack TLV that can be
   registered."

So, for Section 6.2, to make it cleaner and more explicit, how about this c=
hange:

Old:

" No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
   are made directly for TLV Type 21, sub-TLVs in these ranges are
   copied from the assignments made for TLV Type 1. Assignments of sub-..."

New:

" No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
   are made directly for TLV Type 21, sub-TLVs in these ranges are
   copied from the assignments (including existing and future allocations)
   made for TLV Type 1. Assignments of sub-..."


> 2. For the vendor or private use why a difference policy than the rest=20
> of the sub-TLV registry

This document does not make any changes to the "Vendor and Private use" def=
inition, range and policy as defined in RFC4379. In RFC4379, it's policy is=
 defined different from other ranges.=20

>=20
> Nits/editorial comments:
> 1. In section 3.4 I assume that "TC" is traffic class. It will be good=20
> to expand and have reference.

OK, will fix it when all last call comments received.

Best regards,
Mach


From mach.chen@huawei.com  Thu Aug 29 03:05:43 2013
Return-Path: <mach.chen@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 4794321F9FB1; Thu, 29 Aug 2013 03:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zBOdid8HmWI5; Thu, 29 Aug 2013 03:05:38 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id EE05821F8411; Thu, 29 Aug 2013 03:05:36 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AWR99230; Thu, 29 Aug 2013 10:05:35 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 11:04:28 +0100
Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 11:05:17 +0100
Received: from szxeml558-mbs.china.huawei.com ([169.254.8.196]) by szxeml408-hub.china.huawei.com ([10.82.67.95]) with mapi id 14.01.0323.007; Thu, 29 Aug 2013 18:05:13 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org" <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
Thread-Topic: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
Thread-Index: Ac6j72iTQaEc2KyVR6aJXw9+GJi+EwAZqLIAAA8JaoD//4fDgP//cOtg
Date: Thu, 29 Aug 2013 10:05:12 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com> <04cf01cea499$22eb4a80$68c1df80$@gmail.com>
In-Reply-To: <04cf01cea499$22eb4a80$68c1df80$@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.96.176]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Thu, 29 Aug 2013 05:13:40 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-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, 29 Aug 2013 10:05:43 -0000

Hi Roni,

How about this:

" No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
    are made directly for TLV Type 21, sub-TLVs in these ranges are=20
    copied from the assignments made for TLV Type 1 and kept the same
    as that for TLV Type 1. All sub-TLVs in these ranges (include existing
    and future defined) defined for TLV Type 1 apply to TLV Type 21.=20
    Assignments of sub-..."

Best regards,
Mach

> -----Original Message-----
> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> Sent: Thursday, August 29, 2013 5:21 PM
> To: Mach Chen; draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.i=
etf.org
> Cc: ietf@ietf.org; gen-art@ietf.org
> Subject: RE: Gen-ART LC review of
> draft-ietf-mpls-return-path-specified-lsp-ping-12
>=20
> Hi,
> I am not sure you responded to my latest email.
>=20
> Having the policy for TLV type 1 here is not enough in my view since I on=
ly
> look at RFC4379 and create a new TLV type I will not know that I have to
> register it also for the type 21 if it will not be mentioned
>=20
> As for the vendor specific see my other email
> Roni
>=20
> > -----Original Message-----
> > From: Mach Chen [mailto:mach.chen@huawei.com]
> > Sent: 29 August, 2013 11:33 AM
> > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > ping.all@tools.ietf.org
> > Cc: ietf@ietf.org; gen-art@ietf.org
> > Subject: RE: Gen-ART LC review of
> draft-ietf-mpls-return-path-specified-lsp-
> > ping-12
> >
> > Hi Roni,
> >
> > Thanks for your detailed review and comments!
> >
> > Please see my reply inline...
> >
> > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > Sent: Wednesday, August 28, 2013 9:06 PM
> > > To: draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > Subject: Gen-ART LC review of
> > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > >
> > > I am the assigned Gen-ART reviewer for this draft. For background on
> > > Gen-ART, please see the FAQ at
> > > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > > Please resolve these comments along with any other Last Call comments
> > > you may receive.
> > > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > Reviewer: Roni Even
> > > Review Date:2013-8-28
> > > IETF LC End Date: 2013-9-4
> > > IESG Telechat date:
> > >
> > > Summary: This draft is almost ready for publication as a standard tra=
ck
> RFC.
> > >
> > >
> > > Major issues:
> > > Minor issues:
> > > I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV is
> > > defined for TLV type 1 do they need also to be added to TLV type 21.
> > > This should be clear, and if there is some relation I think it should
> > > be reflected in the IANA registry for TLV type 1
> >
> > Yes, type 21 TLV intends to reuse existing and future defined sub-TLVs =
for
> > type TLV 1. And in Section 3.3, it has already stated this, it says:
> >
> > "The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
> >    identify a specific return path.  The Reply Path TLV can carry any
> >    sub-TLV defined for use in the Target FEC Stack TLV that can be
> >    registered."
> >
> > So, for Section 6.2, to make it cleaner and more explicit, how about th=
is
> > change:
> >
> > Old:
> >
> > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >    are made directly for TLV Type 21, sub-TLVs in these ranges are
> >    copied from the assignments made for TLV Type 1. Assignments of
> sub-..."
> >
> > New:
> >
> > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >    are made directly for TLV Type 21, sub-TLVs in these ranges are
> >    copied from the assignments (including existing and future allocatio=
ns)
> >    made for TLV Type 1. Assignments of sub-..."
> >
> >
> > > 2. For the vendor or private use why a difference policy than the res=
t
> > > of the sub-TLV registry
> >
> > This document does not make any changes to the "Vendor and Private use"
> > definition, range and policy as defined in RFC4379. In RFC4379, it's
> policy is
> > defined different from other ranges.
> >
> > >
> > > Nits/editorial comments:
> > > 1. In section 3.4 I assume that "TC" is traffic class. It will be goo=
d
> > > to expand and have reference.
> >
> > OK, will fix it when all last call comments received.
> >
> > Best regards,
> > Mach


From jari.arkko@piuha.net  Thu Aug 29 05:43:03 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACA6811E8103 for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 05:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, 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 dcYrnh8NNnE8 for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 05:42:58 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A315511E8108 for <gen-art@ietf.org>; Thu, 29 Aug 2013 05:42:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id EE9322CC54; Thu, 29 Aug 2013 15:42:43 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2tCJQ3-PZWHa; Thu, 29 Aug 2013 15:42:43 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 692D02CC50; Thu, 29 Aug 2013 15:42:43 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5216A111.1020100@gmail.com>
Date: Thu, 29 Aug 2013 15:42:43 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <DCEBCE90-1871-4A4C-B02F-39DED7AF0D02@piuha.net>
References: <5216A111.1020100@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: draft-ietf-lisp-deployment.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-lisp-deployment-10.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, 29 Aug 2013 12:43:04 -0000

Brian: Thank you for your review.=20

(I am working on my own review of the document - this is one of the ones =
that I will read very carefully on my own as well.)

Jari

On Aug 23, 2013, at 2:38 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at =
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq.
>=20
> Please wait for direction from your document shepherd or AD before =
posting a
> new version of the draft.
>=20
> Document: draft-ietf-lisp-deployment-10.txt
> Reviewer: Brian Carpenter
> Review Date: 2013-08-23
> IETF LC End Date: 2013-07-15
> IESG Telechat date: 2013-08-29
>=20
> Summary:  Ready
> --------
>=20
> Comments:
> ---------
>=20
> Thanks for handling my Last Call comments.
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From ron.even.tlv@gmail.com  Thu Aug 29 05:51:45 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7633721F9F50; Thu, 29 Aug 2013 05:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019,  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 RqD3BstNMqy2; Thu, 29 Aug 2013 05:51:44 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id E5EAC21F9F23; Thu, 29 Aug 2013 05:51:43 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id c11so370134wgh.3 for <multiple recipients>; Thu, 29 Aug 2013 05:51:41 -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:content-transfer-encoding:thread-index :content-language; bh=NSNHutGeSCDbwOw4EiFesN2iJUHusMjEDKPGOP4qRq0=; b=nYJ4VSPfngbaH7A+pH7D+lF+mJNBPoE9p6Sq/sANrczhoK9infBoBkcgJh0jKlUVNX 9durBlWrvOw5kco99xbaX0n1y52YOek1rxGDCC6hzj6soJfnGfCnJxXknWd5YFQWv4xs lKkd7gJkF3HkpFMVFQDtKGkYDJXEsXRYbpkKBOQtEO/Uy7CY/v6HhCzaTEodsGzjg5e1 5F0TRjHFsxODX5cRmjVROpuQBpA6rp+yQi+9UYLG4PQQSqvG0AjU3+j718pC1rouXvok 3hujde3EnnfWEPnyRGxuTbv2K6EXSl+yEENS/R11BkzBR/Hwa+5E0WZidraJ1+TTpqqS PeBQ==
X-Received: by 10.194.123.164 with SMTP id mb4mr2716426wjb.84.1377780701483; Thu, 29 Aug 2013 05:51:41 -0700 (PDT)
Received: from RoniE (bzq-109-67-221-133.red.bezeqint.net. [109.67.221.133]) by mx.google.com with ESMTPSA id v9sm12246255wiw.8.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 29 Aug 2013 05:51:40 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Loa Andersson'" <loa@pi.nu>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com> <04cf01cea499$22eb4a80$68c1df80$@gmail.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com> <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com> <521F3489.1060600@pi.nu>
In-Reply-To: <521F3489.1060600@pi.nu>
Date: Thu, 29 Aug 2013 15:49:03 +0300
Message-ID: <04f301cea4b6$2a282440$7e786cc0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFOtCz/kupT/msuDkJxBc8cYmi4kAJrrZpSAxjw2zQBgMlGEQLYu/AFAg83QJWaTJj8EA==
Content-Language: en-us
Cc: draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org, gen-art@ietf.org, 'Mach Chen' <mach.chen@huawei.com>, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-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, 29 Aug 2013 12:51:45 -0000

Hi,
This is OK . I have no concerns
Roni

> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.nu]
> Sent: 29 August, 2013 2:46 PM
> To: Roni Even
> Cc: 'Mach Chen'; draft-ietf-mpls-return-path-specified-lsp-
> ping.all@tools.ietf.org; gen-art@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART LC review of
draft-ietf-mpls-return-path-specified-lsp-
> ping-12
> 
> Roni,
> 
> tnx - the authors should add words in the IANA section requesting that
IANA
> add this the pointed in the registry; they normally do anyway, but writing
it
> down should not be a problem.
> 
> As for "Vendor Private" RFC 4379 says:
> 
>    "Values from "Vendor Private" ranges MUST NOT be registered with IANA;
>     however, the message MUST contain an enterprise code as registered
>     with the IANA SMI Private Network Management Private Enterprise
>     Numbers.  For each name space that has a Vendor Private range, it
>     must be specified where exactly the SMI Private Enterprise Number
>     resides; see below for examples.  In this way, several enterprises
>     (vendors) can use the same code point without fear of collision."
> 
> The way I read this is that the paragraph does two things (1) defines the
> allocation policy (in this case that "vendor private" won't be assigned by
> IANA) and (2) put a restriction on the "vendor private"
> (sub-)TLVs; they must contain a "private enterprise number".
> 
> Up to now I've thought the restriction on the format was global for all
> "vendor private" sub-TLVs that are used by TLV for LSP Ping.
> However we put words to the same effect in e.g. 6424, wo there is no
reason
> not to do it here also. A pointer to RFC4379 should be enough
> e.g.:
> 
> "For the vendor private sub-TLVs defined for this document, the same
> allocation policies and requirement on the sub-TLV format that is
specified
> for vendor private sub-TLVs in RFC4379 [RFC4379] appliacable."
> 
> Would that cover you concern?
> 
> /Loa
> 
> 
> 
> On 2013-08-29 12:24, Roni Even wrote:
> > Hi,
> > This text is OK if one wants to implement this draft.
> > My concern was about the consistency of the IANA registration so that
> > if someone defines a new TLV type 1 based on RFC4379, IANA will know
> > that it must update also the registry for TLV type 21. If you see no
> > such problem, I have no concerns Roni
> >
> >> -----Original Message-----
> >> From: Mach Chen [mailto:mach.chen@huawei.com]
> >> Sent: 29 August, 2013 1:05 PM
> >> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> >> ping.all@tools.ietf.org
> >> Cc: ietf@ietf.org; gen-art@ietf.org
> >> Subject: RE: Gen-ART LC review of
> > draft-ietf-mpls-return-path-specified-lsp-
> >> ping-12
> >>
> >> Hi Roni,
> >>
> >> How about this:
> >>
> >> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >>      are made directly for TLV Type 21, sub-TLVs in these ranges are
> >>      copied from the assignments made for TLV Type 1 and kept the same
> >>      as that for TLV Type 1. All sub-TLVs in these ranges (include
existing
> >>      and future defined) defined for TLV Type 1 apply to TLV Type 21.
> >>      Assignments of sub-..."
> >>
> >> Best regards,
> >> Mach
> >>
> >>> -----Original Message-----
> >>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> >>> Sent: Thursday, August 29, 2013 5:21 PM
> >>> To: Mach Chen;
> >>> draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> >>> Cc: ietf@ietf.org; gen-art@ietf.org
> >>> Subject: RE: Gen-ART LC review of
> >>> draft-ietf-mpls-return-path-specified-lsp-ping-12
> >>>
> >>> Hi,
> >>> I am not sure you responded to my latest email.
> >>>
> >>> Having the policy for TLV type 1 here is not enough in my view since
> >>> I only look at RFC4379 and create a new TLV type I will not know
> >>> that I have to register it also for the type 21 if it will not be
> >>> mentioned
> >>>
> >>> As for the vendor specific see my other email Roni
> >>>
> >>>> -----Original Message-----
> >>>> From: Mach Chen [mailto:mach.chen@huawei.com]
> >>>> Sent: 29 August, 2013 11:33 AM
> >>>> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> >>>> ping.all@tools.ietf.org
> >>>> Cc: ietf@ietf.org; gen-art@ietf.org
> >>>> Subject: RE: Gen-ART LC review of
> >>> draft-ietf-mpls-return-path-specified-lsp-
> >>>> ping-12
> >>>>
> >>>> Hi Roni,
> >>>>
> >>>> Thanks for your detailed review and comments!
> >>>>
> >>>> Please see my reply inline...
> >>>>
> >>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> >>>>> Sent: Wednesday, August 28, 2013 9:06 PM
> >>>>> To:
> >>>>> draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> >>>>> Cc: ietf@ietf.org; gen-art@ietf.org
> >>>>> Subject: Gen-ART LC review of
> >>>>> draft-ietf-mpls-return-path-specified-lsp-ping-12
> >>>>>
> >>>>> I am the assigned Gen-ART reviewer for this draft. For background
> >>>>> on Gen-ART, please see the FAQ at
> >>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >>>>> Please resolve these comments along with any other Last Call
> >>>>> comments you may receive.
> >>>>> Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> >>>>> Reviewer: Roni Even
> >>>>> Review Date:2013-8-28
> >>>>> IETF LC End Date: 2013-9-4
> >>>>> IESG Telechat date:
> >>>>>
> >>>>> Summary: This draft is almost ready for publication as a standard
> >>>>> track
> >>> RFC.
> >>>>>
> >>>>>
> >>>>> Major issues:
> >>>>> Minor issues:
> >>>>> I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV
> >>>>> is defined for TLV type 1 do they need also to be added to TLV
> >>>>> type
> > 21.
> >>>>> This should be clear, and if there is some relation I think it
> >>>>> should be reflected in the IANA registry for TLV type 1
> >>>>
> >>>> Yes, type 21 TLV intends to reuse existing and future defined
> >>>> sub-TLVs for type TLV 1. And in Section 3.3, it has already stated
> > this, it
> >> says:
> >>>>
> >>>> "The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
> >>>>     identify a specific return path.  The Reply Path TLV can carry
any
> >>>>     sub-TLV defined for use in the Target FEC Stack TLV that can be
> >>>>     registered."
> >>>>
> >>>> So, for Section 6.2, to make it cleaner and more explicit, how
> >>>> about this
> >>>> change:
> >>>>
> >>>> Old:
> >>>>
> >>>> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >>>>     are made directly for TLV Type 21, sub-TLVs in these ranges are
> >>>>     copied from the assignments made for TLV Type 1. Assignments of
> >>> sub-..."
> >>>>
> >>>> New:
> >>>>
> >>>> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >>>>     are made directly for TLV Type 21, sub-TLVs in these ranges are
> >>>>     copied from the assignments (including existing and future
> > allocations)
> >>>>     made for TLV Type 1. Assignments of sub-..."
> >>>>
> >>>>
> >>>>> 2. For the vendor or private use why a difference policy than the
> >>>>> rest of the sub-TLV registry
> >>>>
> >>>> This document does not make any changes to the "Vendor and Private
> >> use"
> >>>> definition, range and policy as defined in RFC4379. In RFC4379,
> >>>> it's
> >>> policy is
> >>>> defined different from other ranges.
> >>>>
> >>>>>
> >>>>> Nits/editorial comments:
> >>>>> 1. In section 3.4 I assume that "TC" is traffic class. It will be
> >>>>> good to expand and have reference.
> >>>>
> >>>> OK, will fix it when all last call comments received.
> >>>>
> >>>> Best regards,
> >>>> Mach
> >
> 
> --
> 
> 
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64


From sebi@gw01.ehlo.wurstkaes.de  Thu Aug 29 05:28:20 2013
Return-Path: <sebi@gw01.ehlo.wurstkaes.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 E69DE11E80A2 for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 05:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.525
X-Spam-Level: 
X-Spam-Status: No, score=-3.525 tagged_above=-999 required=5 tests=[AWL=1.075,  BAYES_00=-2.599, GB_I_LETTER=-2, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uIIjM4v+cKdI for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 05:28:20 -0700 (PDT)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE0721F9F88 for <gen-art@ietf.org>; Thu, 29 Aug 2013 05:28:16 -0700 (PDT)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1VF1KO-0007Zs-LX; Thu, 29 Aug 2013 14:27:56 +0200
Date: Thu, 29 Aug 2013 14:27:56 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: Martin Stiemerling <martin.stiemerling@neclab.eu>
Message-ID: <20130829122756.GC3536@gw01.ehlo.wurstkaes.de>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A133F1E@eusaamb107.ericsson.se> <521F1504.5070502@neclab.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <521F1504.5070502@neclab.eu>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Mailman-Approved-At: Thu, 29 Aug 2013 06:09:24 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-alto-server-discovery.all@tools.ietf.org" <draft-ietf-alto-server-discovery.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-alto-server-discovery-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 12:28:21 -0000

Martin,
Meral,

these comments have already been addressed in the -09 version,

Meral, thanks for raising these issues and sorry that I forgot
an explicit acknowlegment.

Sebastian


On Thu, Aug 29, 2013 at 11:31:48AM +0200, Martin Stiemerling wrote:
> Hi Meral,
> 
> Thanks for your review and we will address your editorials in the
> next update coming soon.
> 
>   Martin
> 
> On 06/21/2013 07:54 AM, Meral Shirazipour wrote:
> >I am the assigned Gen-ART reviewer for this draft. For background on
> >Gen-ART, please see the FAQ at
> >http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq  .
> >
> >Please resolve these comments along with any other Last Call comments
> >you may receive.
> >
> >Document: draft-ietf-alto-server-discovery-08
> >
> >Reviewer: Meral Shirazipour
> >
> >Review Date: 2013-06-20
> >
> >IETF LC End Date: 2013-06-20
> >
> >IESG Telechat date: NA
> >
> >Summary:
> >
> >This draft is almost ready to be published as Standards Track RFC but I
> >do have some comments.
> >
> >Nits/editorial comments:
> >
> >-[Page 4], 2nd line before last, "funcional"--typo-->"functional"
> >
> >-[Page 5], Section 2, Point 2, "neccessary"--typo-->"necessary"
> >
> >-[Page 5], 2nd paragraph before last, "whishes"--typo-->"wishes"
> >
> >-[Page 5], last paragraph, "neccessarily"--typo-->"necessarily"
> >
> >-[Page 6], Section 3.1.1.
> >
> >"If DHCP-based discovery succeeds the software SHOULD inform the user
> >that the user input has been ignored and replaced by information
> >retrieved from the network."
> >
> >Suggestion to put "," after "If DHCP-based discovery succeeds".
> >
> >-[Page 8], Section 4, line 3, "mobilility"--typo-->"mobility"
> >
> >-[Page 8], Section 4, paragraph 2, "familly"--typo-->"family"
> >
> >-[Page 8], Section 4, paragraph 2, "familiy"--typo-->"family"
> >
> >-[Page 9], last line, "corrsponding"--typo-->"corresponding"
> >
> >-[Page 11], paragraph 3, "anormalities"--typo-->"abnormalities"
> >
> >-[page 12]
> >
> >"The security aspects of obtaining the domain name that is used for
> >input to the U-NAPTR process is described in respective documents, such
> >as [RFC5986]."
> >
> >Refers to more than one documents but only lists RFC5986. It would be
> >better to either list the other documents or say "described in [RFC5986]."
> >
> >-[Page 13], Section 7.2, Ref. [I-D.ietf-alto-protocol] points to older
> >version.
> >
> >-[Page 13], Section 7.2, Ref. [I-D.kist-alto-3pdisc] points to older
> >version.
> >
> >-General, please consider spelling out acronyms when first used. Also
> >using a common way (first letters capital or not):
> >
> >"network address translation (NAT)" versus "Virtual Private Network (VPN)"
> >
> >Best Regards,
> >
> >Meral
> >
> >---
> >
> >Meral Shirazipour
> >
> >Ericsson
> >
> >Research
> >
> >www.ericsson.com
> >
> 
> -- 
> martin.stiemerling@neclab.eu
> 
> NEC Laboratories Europe
> NEC Europe Limited
> Registered Office:
> Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
> Registered in England 2832014

From jari.arkko@piuha.net  Thu Aug 29 07:07:25 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9762921E8083 for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 07:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, 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 CEd6kd0UznGa for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 07:07:21 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 3082A11E810F for <gen-art@ietf.org>; Thu, 29 Aug 2013 07:07:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 77E502CC55; Thu, 29 Aug 2013 17:07:19 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LE0jncSVVqxl; Thu, 29 Aug 2013 17:07:16 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 54C9B2CC50; Thu, 29 Aug 2013 17:07:16 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com>
Date: Thu, 29 Aug 2013 17:07:16 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <95E63B93-CC54-4A50-9472-EAB843F7474E@piuha.net>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] [apps-discuss] Gen-ART review of draft-bormann-cbor-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, 29 Aug 2013 14:07:25 -0000

Thank you for your review! It was certainly different from most Gen-ART =
reviews, but has generated interesting discussion. I believe other ADs =
at the IESG have raised the issue whether this should be the standard =
way to do things, or just a way. Lets see where the discussion ends.

Jari

On Jul 30, 2013, at 10:05 AM, Martin Thomson <martin.thomson@gmail.com> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-bormann-cbor-04
> Reviewer: Martin Thomson
> Review Date: 2013-07-29
> IETF LC End Date: ?
> IESG Telechat date: 2013-08-15
>=20
> Summary:
> This document is not ready for publication as proposed standard.
>=20
> I'm glad that I held this review until Paul's appsarea presentation.
> This made it very clear to me that the types of concerns I have are
> considered basically irrelevant by the authors because they aren't
> interested in changing the design goals.  I don't find the specific
> design goals to be interesting and am of the opinion that the goals
> are significant as a matter of general application.  I hope that is
> clear from my review.
>=20
> Independent of any conclusions regarding design goals, there are
> issues that need addressing.
>=20
> (This is an atypical Gen-ART review.  I make no apologies for that.  I
> didn't intend to write a review like this when I started, but feel
> that it's important to commit these thoughts to the record.  It's also
> somewhat long, sorry.  I tried to edit it down.)
>=20
> I have reviewed the mailing list feedback, and it's not clear to me
> that there is consensus to publish this.  It might be that the dissent
> that I have observed is not significant in Barry's learned judgment,
> or that this is merely dissent on design goals and therefore
> irrelevant.  The fact that this work isn't a product of a working
> group still concerns me.  I'm actually interested in why this is
> AD-sponsored rather than a working group product.
>=20
> Major issues:
> My major concerns with this document might be viewed as disagreements
> with particular design choices.  And, I consider it likely that the
> authors will conclude that the document is still worth publishing as
> is, or perhaps with some minor changes.  In the end, I have no issue
> with that, but expect that the end result will be that the resulting
> RFC is ignored.
>=20
> What would cause this to be tragic, is if publication of this were
> used to prevent other work in this area from subsequently being
> published.  (For those drawing less-than-charitable inferences from
> this, I have no desire to throw my hat into this particular ring,
> except perhaps in jest [1].)
>=20
> This design is far too complex and large.  Regardless of how
> well-considered it might be, or how well this meets the stated design
> goals, I can't see anything but failure in this document's future.
> JSON succeeds largely because it doesn't attempt to address so many
> needs at once, but I could even make a case for why JSON contains too
> many features.
>=20
> In comparison with JSON, this document does one major thing wrong: it
> has more options than JSON in several dimensions.  There are more
> types, there are several more dimensions for extensibility than JSON:
> types extensions, values extensions (values of 28-30 in the lower bits
> of the type byte), plus the ability to apply arbitrary tags to any
> value.  I believe all of these to be major problems that will cause
> them to be ignored, poorly implemented, and therefore useless.
>=20
> In part, this complexity produces implementations that are far more
> complex than they might need to be, unless additional standardization
> is undertaken.  That idea is something I'm uncomfortable with.
>=20
> Design issue: extensibility:
> This document avoids discussion of issues regarding schema-less
> document formats that I believe to be fundamental.  These issues are
> critical when considering the creation of a new interchange format.
> By choosing this specific design it makes a number of trade-offs that
> in my opinion are ill-chosen.  This may be in part because the
> document is unclear about how applications intend to use the documents
> it describes.
>=20
> You may conclude after reading this review that this is simply because
> the document does not explain the rationale for selecting the approach
> it takes.  I hope that isn't the conclusion you reach, but appreciate
> the reasons why you might do so.
>=20
> I believe the fundamental problem to be one that arises from a
> misunderstanding about what it means to have no schema.  Aside from
> formats that require detailed contextual knowledge to interpret, there
> are several steps toward the impossible, platonic ideal of a perfectly
> self-describing format.  It's impossible because ultimately the entity
> that consumes the data is required at some level to understand the
> semantics that are being conveyed.  In practice, no generic format can
> effectively self-describe to the level of semantics.
>=20
> This draft describes a format that is more capable at self-description
> than JSON.  I believe that to not just be unnecessary, but
> counterproductive.  At best, it might provide implementations with a
> way to avoid an occasional extra line of code for type conversion.
>=20
> Extensibility as it relates to types:
> The use of extensive typing in CBOR implies an assumption of a major
> role for generic processing.  XML schema and XQuery demonstrate that
> this desire is not new, but they also demonstrate the folly of
> pursuing those goals.
>=20
> JSON relies on a single mechanism for extensibility. JSON maps that
> contain unknown or unsupported keys are (usually) ignored.  This
> allows new values to be added to documents without destroying the
> ability of an old processor to extract the values that it supports.
> The limited type information JSON carries leaks out, but it's unclear
> what value this has to a generic processor.  All of the generic uses
> I've seen merely carry that type information, no specific use is made
> of the knowledge it provides.
>=20
> ASN.1 extensibility, as encoded in PER, leads to no type information
> leaking.  Unsupported extensions are skipped based on a length field.
>=20
> (As an aside, PER is omitted from the analysis in the appendix, which
> I note from the mailing lists is due to its dependency on schema.
> Interestingly, I believe it to be possible - though not trivial - to
> create an ASN.1 description with all the properties described in CBOR
> that would have roughly equivalent, if not fully equivalent,
> properties to CBOR when serialized.)
>=20
> By defining an extensibility scheme for types, CBOR effectively
> acknowledges that a generic processor doesn't need type information
> (just delineation information), but it then creates an extensive type
> system.  That seems wasteful.
>=20
> Design issue: types:
> The addition of the ability to carry uninterpreted binary data is a
> valuable and important feature.  If that was all this document did,
> then that might have been enough.  But instead it adds numerous
> different types.
>=20
> I can understand why multiple integer encoding sizes are desirable,
> and maybe even floating point representations, but this describes
> bignums in both base 2 and 10, embedded CBOR documents in three forms,
> URIs, base64 encoded strings, regexes, MIME bodies, date and times in
> two different forms, and potentially more.
>=20
> I also challenge the assertion made where the code required for
> parsing a data type produces larger code sizes if performed outside of
> a common shared library.  That's arguably provably true, but last time
> I checked a few extra procedure calls (or equivalent) weren't the
> issue for code size.  Sheer number of options on the other hand might
> be.
>=20
> Half-precision floating point numbers are a good example of excessive
> exuberance.  They are not available in many languages for good reason:
> they aren't good for much.  They actually tend to cause errors in
> software in the same way that threading libraries do: it's not that
> it's hard to use them, it's that it's harder than people think.  And
> requiring that implementations parse these creates unnecessary
> complexity.  I do not believe that for the very small subset of cases
> where half precision is actually useful, the cost of transmitting the
> extra 2 bytes of a single-precision number is not going to be a
> burden.  However, the cost of carrying the code required to decode
> them is not as trivial as this makes out.  The fact that this requires
> an appendix would seem to indicate that this is special enough that
> inclusion should have been very carefully considered.  To be honest,
> if it were my choice, I would have excluded single-precision floating
> point numbers as well, they too create more trouble than they are
> worth.
>=20
> Design issue: optionality
> CBOR embraces the idea that support for types is optional.  Given the
> extensive nature of the type system, it's almost certain that
> implementations will choose to avoid implementation of some subset of
> the types.  The document makes no statements about what types are
> mandatory for implementations, so I'm not sure how it is possible to
> provide interoperable implementations.
>=20
> If published in its current form, I predict that only a small subset
> of types will be implemented and become interoperable.
>=20
> Design issue: tagging
> The tagging feature has a wonderful property: the ability to create
> emergency complexity.  Given that a tag itself can be arbitrarily
> complex, I'm almost certain that this is a feature you do not want.
>=20
> Minor issues:
> Design issue: negative numbers
> Obviously, the authors will be well-prepared for arguments that
> describe as silly the separation of integer types into distinct
> positive and negative types.  But it's true, this is a strange choice,
> and a very strange design.
>=20
> The fact that this format is capable of describing 64-bit negative
> numbers creates a problem for implementations that I'm surprised
> hasn't been raised already.  In most languages I use, there is no
> native type that is capable of carrying the most negative value that
> can be expressed in this format.  -2^64 is twice as large as a 64-bit
> twos-complement integer can store.
>=20
> It almost looks as though CBOR is defining a 65-bit, 33-bit or 17-bit
> twos complement integer format, with the most significant bit isolated
> from the others, except that the negative expression doesn't even have
> the good sense to be properly sortable.  Given that and the fact that
> bignums are also defined, I find this choice to be baffling.
>=20
> Document issue: Canonicalization
> Please remove Section 3.6.  c14n is hard, and this format actually
> makes it impossible to standardize a c14n scheme, that says a lot
> about it.  In comparison, JSON is almost trivial to canonicalize.
>=20
> If the intent of this section is to describe some of the possible
> gotchas, such as those described in the last paragraph, then that
> would be good.  Changing the focus to "Canonicalization
> Considerations" might help.
>=20
> I believe that there are several issues that this section would still
> need to consider.  For instance, the use of the types that contain
> additional JSON encoding hints carry additional semantics that might
> not be significant to the application protocol.
>=20
> Extension based on minor values 28-30 (the "additional information" =
space):
> ...is impossible as defined.  Section 5.1 seems to imply otherwise.
> I'm not sure how that would ever happen without breaking existing
> parsers.  Section 5.2 actually makes this worse by making a
> wishy-washy commitment to size for 28 and 29, but no commitment at all
> for 30.
>=20
> Nits:
> Section 3.7 uses the terms "well-formed" and "valid" in a sense that I
> believe to be consistent with their use in XML and XML Schema.  I
> found the definition of "valid" to be a little difficult to parse;
> specifically, it's not clear whether invalid is the logical inverse of
> valid.
>=20
> Appendix B/Table 4 has a TBD on it.  Can this be checked?
>=20
> Table 4 keeps getting forward references, but it's hidden in an
> appendix.  I found that frustrating as a reader because the forward
> references imply that there is something important there.  And that
> implication was completely right, this needs promotion.  I know why
> it's hidden, but that reason just supports my earlier theses.
>=20
> Section 5.1 says "An IANA registry is appropriate here.".  Why not
> reference Section 7.1?
>=20
> [1] https://github.com/martinthomson/aweson
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss


From daedulus@btconnect.com  Thu Aug 29 08:34:38 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBCAF21E805A; Thu, 29 Aug 2013 08:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.073
X-Spam-Level: 
X-Spam-Status: No, score=-3.073 tagged_above=-999 required=5 tests=[AWL=-0.474, 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 rll+h33EFdzL; Thu, 29 Aug 2013 08:34:22 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0250.outbound.messaging.microsoft.com [213.199.154.250]) by ietfa.amsl.com (Postfix) with ESMTP id 2637D21F9CD1; Thu, 29 Aug 2013 08:34:20 -0700 (PDT)
Received: from mail162-db9-R.bigfish.com (10.174.16.250) by DB9EHSOBE029.bigfish.com (10.174.14.92) with Microsoft SMTP Server id 14.1.225.22; Thu, 29 Aug 2013 15:34:19 +0000
Received: from mail162-db9 (localhost [127.0.0.1])	by mail162-db9-R.bigfish.com (Postfix) with ESMTP id 3069B4200C4; Thu, 29 Aug 2013 15:34:19 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.181; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0711HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zz9371I936eI542I1432I168aJzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah186068h8275bh8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail162-db9 (localhost.localdomain [127.0.0.1]) by mail162-db9 (MessageSwitch) id 1377790456452990_6643; Thu, 29 Aug 2013 15:34:16 +0000 (UTC)
Received: from DB9EHSMHS022.bigfish.com (unknown [10.174.16.239])	by mail162-db9.bigfish.com (Postfix) with ESMTP id 4326A1C017A; Thu, 29 Aug 2013 15:34:16 +0000 (UTC)
Received: from DBXPRD0711HT001.eurprd07.prod.outlook.com (157.56.254.181) by DB9EHSMHS022.bigfish.com (10.174.14.32) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 29 Aug 2013 15:34:13 +0000
Received: from DBXPRD0611HT004.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.178.34) with Microsoft SMTP Server (TLS) id 14.16.353.4; Thu, 29 Aug 2013 15:34:11 +0000
Message-ID: <012001cea4cd$1845c680$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Roni Even <ron.even.tlv@gmail.com>, <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com><F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com><04cf01cea499$22eb4a80$68c1df80$@gmail.com><F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com> <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com>
Date: Thu, 29 Aug 2013 16:33:04 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review ofdraft-ietf-mpls-return-path-specified-lsp-ping-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, 29 Aug 2013 15:34:38 -0000

Roni

I find it difficult to know whether to agree with you or not since there
is another "gorilla" operating in this namespace, namely
draft-andersson-mpls-lsp-ping-upd-00
which sort of gives the option of taking out the sub-TLV types of a TLV
Type into a separate registry which can then be referenced by the
specifications of several TLV Types.  This I-D formally calls for no
action by IANA, except that it implies a reorganisation of the
registries which IANA might well already have executed - certainly, the
registries no longer look the same as they did a few months ago although
that might also be a coincidence.

You make reference to the registry set up by RFC6426 but you should be
aware that what is now in the IANA registries is not what was there when
that RFC was approved; rather, it has changed as alluded to above..

If
draft-andersson-mpls-lsp-ping-upd-00
is approved, and my perception is that IANA assumes it has been, then
this, return-path I-D would appear to be barking up the wrong tree and
needs revising to reflect the new IANA structure, namely that it needs
to update
the title which already exists
Sub-TLVs for TLV Types 1 and 16
to become
Sub-TLVs for TLV Types 1 and 16 and 21
whereupon things start to fall into place

draft-andersson-mpls-lsp-ping-upd-00
also updates RFC4379 which, if accepted, means, I think, that this I-D
need not.

All very technically sound but we seem to have our processes upside
down.

There is of course a lengthy history to this that is not material to the
current discussion.

Tom Petch

----- Original Message -----
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Mach Chen'" <mach.chen@huawei.com>;
<draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
Cc: <gen-art@ietf.org>; <ietf@ietf.org>
Sent: Thursday, August 29, 2013 11:24 AM
Subject: RE: Gen-ART LC review
ofdraft-ietf-mpls-return-path-specified-lsp-ping-12


> Hi,
> This text is OK if one wants to implement this draft.
> My concern was about the consistency of the IANA registration so that
if
> someone defines a new TLV type 1 based on RFC4379, IANA will know that
it
> must update also the registry for TLV type 21. If you see no such
problem, I
> have no concerns
> Roni
>
> > -----Original Message-----
> > From: Mach Chen [mailto:mach.chen@huawei.com]
> > Sent: 29 August, 2013 1:05 PM
> > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > ping.all@tools.ietf.org
> > Cc: ietf@ietf.org; gen-art@ietf.org
> > Subject: RE: Gen-ART LC review of
> draft-ietf-mpls-return-path-specified-lsp-
> > ping-12
> >
> > Hi Roni,
> >
> > How about this:
> >
> > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >     are made directly for TLV Type 21, sub-TLVs in these ranges are
> >     copied from the assignments made for TLV Type 1 and kept the
same
> >     as that for TLV Type 1. All sub-TLVs in these ranges (include
existing
> >     and future defined) defined for TLV Type 1 apply to TLV Type 21.
> >     Assignments of sub-..."
> >
> > Best regards,
> > Mach
> >
> > > -----Original Message-----
> > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > Sent: Thursday, August 29, 2013 5:21 PM
> > > To: Mach Chen;
> > > draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > Subject: RE: Gen-ART LC review of
> > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > >
> > > Hi,
> > > I am not sure you responded to my latest email.
> > >
> > > Having the policy for TLV type 1 here is not enough in my view
since I
> > > only look at RFC4379 and create a new TLV type I will not know
that I
> > > have to register it also for the type 21 if it will not be
mentioned
> > >
> > > As for the vendor specific see my other email Roni
> > >
> > > > -----Original Message-----
> > > > From: Mach Chen [mailto:mach.chen@huawei.com]
> > > > Sent: 29 August, 2013 11:33 AM
> > > > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > > > ping.all@tools.ietf.org
> > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > Subject: RE: Gen-ART LC review of
> > > draft-ietf-mpls-return-path-specified-lsp-
> > > > ping-12
> > > >
> > > > Hi Roni,
> > > >
> > > > Thanks for your detailed review and comments!
> > > >
> > > > Please see my reply inline...
> > > >
> > > > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > > > Sent: Wednesday, August 28, 2013 9:06 PM
> > > > > To:
> > > > >
draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > > Subject: Gen-ART LC review of
> > > > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > > >
> > > > > I am the assigned Gen-ART reviewer for this draft. For
background
> > > > > on Gen-ART, please see the FAQ at
> > > > > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > > > > Please resolve these comments along with any other Last Call
> > > > > comments you may receive.
> > > > > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > > > Reviewer: Roni Even
> > > > > Review Date:2013-8-28
> > > > > IETF LC End Date: 2013-9-4
> > > > > IESG Telechat date:
> > > > >
> > > > > Summary: This draft is almost ready for publication as a
standard
> > > > > track
> > > RFC.
> > > > >
> > > > >
> > > > > Major issues:
> > > > > Minor issues:
> > > > > I am not clear on the sub-TLV in section 6.2 1. If a new
sub-TLV
> > > > > is defined for TLV type 1 do they need also to be added to TLV
type
> 21.
> > > > > This should be clear, and if there is some relation I think it
> > > > > should be reflected in the IANA registry for TLV type 1
> > > >
> > > > Yes, type 21 TLV intends to reuse existing and future defined
> > > > sub-TLVs for type TLV 1. And in Section 3.3, it has already
stated
> this, it
> > says:
> > > >
> > > > "The Target FEC sub-TLVs defined in [RFC4379] provide a good way
to
> > > >    identify a specific return path.  The Reply Path TLV can
carry any
> > > >    sub-TLV defined for use in the Target FEC Stack TLV that can
be
> > > >    registered."
> > > >
> > > > So, for Section 6.2, to make it cleaner and more explicit, how
about
> > > > this
> > > > change:
> > > >
> > > > Old:
> > > >
> > > > " No assignments of sub-TLVs in the range of 0-16383 and
32768-49161
> > > >    are made directly for TLV Type 21, sub-TLVs in these ranges
are
> > > >    copied from the assignments made for TLV Type 1. Assignments
of
> > > sub-..."
> > > >
> > > > New:
> > > >
> > > > " No assignments of sub-TLVs in the range of 0-16383 and
32768-49161
> > > >    are made directly for TLV Type 21, sub-TLVs in these ranges
are
> > > >    copied from the assignments (including existing and future
> allocations)
> > > >    made for TLV Type 1. Assignments of sub-..."
> > > >
> > > >
> > > > > 2. For the vendor or private use why a difference policy than
the
> > > > > rest of the sub-TLV registry
> > > >
> > > > This document does not make any changes to the "Vendor and
Private
> > use"
> > > > definition, range and policy as defined in RFC4379. In RFC4379,
it's
> > > policy is
> > > > defined different from other ranges.
> > > >
> > > > >
> > > > > Nits/editorial comments:
> > > > > 1. In section 3.4 I assume that "TC" is traffic class. It will
be
> > > > > good to expand and have reference.
> > > >
> > > > OK, will fix it when all last call comments received.
> > > >
> > > > Best regards,
> > > > Mach
>
>



From ron.even.tlv@gmail.com  Thu Aug 29 11:17:40 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E025611E814B; Thu, 29 Aug 2013 11:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018,  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 s1ZlOJdRAmVF; Thu, 29 Aug 2013 11:17:38 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 3C81911E813D; Thu, 29 Aug 2013 11:17:38 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id hi5so614652wib.3 for <multiple recipients>; Thu, 29 Aug 2013 11:17:37 -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:content-transfer-encoding:thread-index :content-language; bh=oUzB1BwQ0IXz07y6AdqXVRFfDfFY0zqRjajLcV08vuU=; b=SAMF7pusISQp0aT8MB24QQTGvyxmo0lVHiWeYD6qAHi9loj/t5zRr/QETCPP3cfj99 NWwGBSsjYXBQDGwzE2M/sFEUw8ghf+CLlGEIGpS9YW2Bvfx1tFigWGwnqNpeJ1F/U92O ZujsuY0YjhiFfC79s/RlflHETHn5OndBHAT55Hg928Rbw5F6cPKzuNHaRphIWgcaP7B2 E5MbJznUnhVJOhdrXPFl8qWrTMLmI/RaScwYhEsDpHXLb+ZcCdseq2253C/rK0YuwNaf SeBkDocgN6b1q2I7NY9ejO9zVjFb1XsZcTeWvlyiP0jcNOGLc3xKOHMFOnRnhmBwqS6d a3Dg==
X-Received: by 10.180.184.107 with SMTP id et11mr16086773wic.60.1377800257198;  Thu, 29 Aug 2013 11:17:37 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id b13sm2571282wic.9.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 29 Aug 2013 11:17:36 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'t.p.'" <daedulus@btconnect.com>, <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com><F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com><04cf01cea499$22eb4a80$68c1df80$@gmail.com><F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com> <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com> <012001cea4cd$1845c680$4001a8c0@gateway.2wire.net>
In-Reply-To: <012001cea4cd$1845c680$4001a8c0@gateway.2wire.net>
Date: Thu, 29 Aug 2013 21:15:06 +0300
Message-ID: <054c01cea4e3$b207cc30$16176490$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFOtCz/kupT/msuDkJxBc8cYmi4kAJrrZpSAxjw2zQBgMlGEQLYu/AFA01uBKSaQv41wA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review ofdraft-ietf-mpls-return-path-specified-lsp-ping-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, 29 Aug 2013 18:17:40 -0000

HI,
I do not follow all the MPLS work, this Gen-ART review is done during the
IETF LC.  
I would think that your point should have been discussed in the WG before
sending the return path ping to publication.
BTW: I took a quick look at draft-andersson-mpls-lsp-ping-upd-00 third
paragraph of section 2 and I am not sure that the return path ping is
influenced since it does not use all the sub-tlv from tlv type 1 so it
should be a separate registry
Roni

> -----Original Message-----
> From: t.p. [mailto:daedulus@btconnect.com]
> Sent: 29 August, 2013 6:33 PM
> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> ping.all@tools.ietf.org
> Cc: gen-art@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART LC review
ofdraft-ietf-mpls-return-path-specified-lsp-
> ping-12
> 
> Roni
> 
> I find it difficult to know whether to agree with you or not since there
is
> another "gorilla" operating in this namespace, namely
> draft-andersson-mpls-lsp-ping-upd-00
> which sort of gives the option of taking out the sub-TLV types of a TLV
Type
> into a separate registry which can then be referenced by the
specifications of
> several TLV Types.  This I-D formally calls for no action by IANA, except
that it
> implies a reorganisation of the registries which IANA might well already
have
> executed - certainly, the registries no longer look the same as they did a
few
> months ago although that might also be a coincidence.
> 
> You make reference to the registry set up by RFC6426 but you should be
> aware that what is now in the IANA registries is not what was there when
> that RFC was approved; rather, it has changed as alluded to above..
> 
> If
> draft-andersson-mpls-lsp-ping-upd-00
> is approved, and my perception is that IANA assumes it has been, then
this,
> return-path I-D would appear to be barking up the wrong tree and needs
> revising to reflect the new IANA structure, namely that it needs to update
> the title which already exists Sub-TLVs for TLV Types 1 and 16 to become
Sub-
> TLVs for TLV Types 1 and 16 and 21 whereupon things start to fall into
place
> 
> draft-andersson-mpls-lsp-ping-upd-00
> also updates RFC4379 which, if accepted, means, I think, that this I-D
need
> not.
> 
> All very technically sound but we seem to have our processes upside down.
> 
> There is of course a lengthy history to this that is not material to the
current
> discussion.
> 
> Tom Petch
> 
> ----- Original Message -----
> From: "Roni Even" <ron.even.tlv@gmail.com>
> To: "'Mach Chen'" <mach.chen@huawei.com>; <draft-ietf-mpls-return-path-
> specified-lsp-ping.all@tools.ietf.org>
> Cc: <gen-art@ietf.org>; <ietf@ietf.org>
> Sent: Thursday, August 29, 2013 11:24 AM
> Subject: RE: Gen-ART LC review
> ofdraft-ietf-mpls-return-path-specified-lsp-ping-12
> 
> 
> > Hi,
> > This text is OK if one wants to implement this draft.
> > My concern was about the consistency of the IANA registration so that
> if
> > someone defines a new TLV type 1 based on RFC4379, IANA will know that
> it
> > must update also the registry for TLV type 21. If you see no such
> problem, I
> > have no concerns
> > Roni
> >
> > > -----Original Message-----
> > > From: Mach Chen [mailto:mach.chen@huawei.com]
> > > Sent: 29 August, 2013 1:05 PM
> > > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > > ping.all@tools.ietf.org
> > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > Subject: RE: Gen-ART LC review of
> > draft-ietf-mpls-return-path-specified-lsp-
> > > ping-12
> > >
> > > Hi Roni,
> > >
> > > How about this:
> > >
> > > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> > >     are made directly for TLV Type 21, sub-TLVs in these ranges are
> > >     copied from the assignments made for TLV Type 1 and kept the
> same
> > >     as that for TLV Type 1. All sub-TLVs in these ranges (include
> existing
> > >     and future defined) defined for TLV Type 1 apply to TLV Type 21.
> > >     Assignments of sub-..."
> > >
> > > Best regards,
> > > Mach
> > >
> > > > -----Original Message-----
> > > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > > Sent: Thursday, August 29, 2013 5:21 PM
> > > > To: Mach Chen;
> > > > draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > Subject: RE: Gen-ART LC review of
> > > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > >
> > > > Hi,
> > > > I am not sure you responded to my latest email.
> > > >
> > > > Having the policy for TLV type 1 here is not enough in my view
> since I
> > > > only look at RFC4379 and create a new TLV type I will not know
> that I
> > > > have to register it also for the type 21 if it will not be
> mentioned
> > > >
> > > > As for the vendor specific see my other email Roni
> > > >
> > > > > -----Original Message-----
> > > > > From: Mach Chen [mailto:mach.chen@huawei.com]
> > > > > Sent: 29 August, 2013 11:33 AM
> > > > > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > > > > ping.all@tools.ietf.org
> > > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > > Subject: RE: Gen-ART LC review of
> > > > draft-ietf-mpls-return-path-specified-lsp-
> > > > > ping-12
> > > > >
> > > > > Hi Roni,
> > > > >
> > > > > Thanks for your detailed review and comments!
> > > > >
> > > > > Please see my reply inline...
> > > > >
> > > > > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > > > > Sent: Wednesday, August 28, 2013 9:06 PM
> > > > > > To:
> > > > > >
> draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > > > Subject: Gen-ART LC review of
> > > > > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > > > >
> > > > > > I am the assigned Gen-ART reviewer for this draft. For
> background
> > > > > > on Gen-ART, please see the FAQ at
> > > > > > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > > > > > Please resolve these comments along with any other Last Call
> > > > > > comments you may receive.
> > > > > > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > > > > Reviewer: Roni Even
> > > > > > Review Date:2013-8-28
> > > > > > IETF LC End Date: 2013-9-4
> > > > > > IESG Telechat date:
> > > > > >
> > > > > > Summary: This draft is almost ready for publication as a
> standard
> > > > > > track
> > > > RFC.
> > > > > >
> > > > > >
> > > > > > Major issues:
> > > > > > Minor issues:
> > > > > > I am not clear on the sub-TLV in section 6.2 1. If a new
> sub-TLV
> > > > > > is defined for TLV type 1 do they need also to be added to TLV
> type
> > 21.
> > > > > > This should be clear, and if there is some relation I think it
> > > > > > should be reflected in the IANA registry for TLV type 1
> > > > >
> > > > > Yes, type 21 TLV intends to reuse existing and future defined
> > > > > sub-TLVs for type TLV 1. And in Section 3.3, it has already
> stated
> > this, it
> > > says:
> > > > >
> > > > > "The Target FEC sub-TLVs defined in [RFC4379] provide a good way
> to
> > > > >    identify a specific return path.  The Reply Path TLV can
> carry any
> > > > >    sub-TLV defined for use in the Target FEC Stack TLV that can
> be
> > > > >    registered."
> > > > >
> > > > > So, for Section 6.2, to make it cleaner and more explicit, how
> about
> > > > > this
> > > > > change:
> > > > >
> > > > > Old:
> > > > >
> > > > > " No assignments of sub-TLVs in the range of 0-16383 and
> 32768-49161
> > > > >    are made directly for TLV Type 21, sub-TLVs in these ranges
> are
> > > > >    copied from the assignments made for TLV Type 1. Assignments
> of
> > > > sub-..."
> > > > >
> > > > > New:
> > > > >
> > > > > " No assignments of sub-TLVs in the range of 0-16383 and
> 32768-49161
> > > > >    are made directly for TLV Type 21, sub-TLVs in these ranges
> are
> > > > >    copied from the assignments (including existing and future
> > allocations)
> > > > >    made for TLV Type 1. Assignments of sub-..."
> > > > >
> > > > >
> > > > > > 2. For the vendor or private use why a difference policy than
> the
> > > > > > rest of the sub-TLV registry
> > > > >
> > > > > This document does not make any changes to the "Vendor and
> Private
> > > use"
> > > > > definition, range and policy as defined in RFC4379. In RFC4379,
> it's
> > > > policy is
> > > > > defined different from other ranges.
> > > > >
> > > > > >
> > > > > > Nits/editorial comments:
> > > > > > 1. In section 3.4 I assume that "TC" is traffic class. It will
> be
> > > > > > good to expand and have reference.
> > > > >
> > > > > OK, will fix it when all last call comments received.
> > > > >
> > > > > Best regards,
> > > > > Mach
> >
> >



From superuser@gmail.com  Thu Aug 29 11:34:29 2013
Return-Path: <superuser@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C72021E80B1 for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 11:34:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.445
X-Spam-Level: 
X-Spam-Status: No, score=-2.445 tagged_above=-999 required=5 tests=[AWL=0.154,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c7353KMigweT for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 11:34:28 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 4FDCB21E80AA for <gen-art@ietf.org>; Thu, 29 Aug 2013 11:34:28 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id q58so766387wes.25 for <gen-art@ietf.org>; Thu, 29 Aug 2013 11:34:27 -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=bD2X0vnmI+eGTiRDAbWNVdUutOvRJBBYDoG9qD/3IAo=; b=WFrwaIH+xbgZZVwPgiredEGo+h84o0vsSiENJKTJMdVqkHhHyh2zAnxhHH7Sg8OHcz epaS5cYbBxotLupuMDaRap29Ij6tsSJv5qHU+xQH5AByKipM64arF8fkGXSo+bYvpO6H iTISLYMHUOSpXLgkFwKCtgFufELYFbYasY022fCA57Ds73JsntRcX3TGOHhEkrS/HxZ1 rI6fwW/VWjy8uforMefmK4zsS2T5zVTwypnizU3VeSkHVxOow0B3i0Z49NK7xYHjEYeB briyt/uTCKhLKqX1cKlG+AUFgxsbSFkAO8UtTzIrhpvSIV7CmIIHjYCngdfI1igOkVee d9Tg==
MIME-Version: 1.0
X-Received: by 10.194.122.129 with SMTP id ls1mr7388947wjb.37.1377801267477; Thu, 29 Aug 2013 11:34:27 -0700 (PDT)
Received: by 10.180.75.144 with HTTP; Thu, 29 Aug 2013 11:34:27 -0700 (PDT)
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A630E6A@eusaamb107.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A630E6A@eusaamb107.ericsson.se>
Date: Thu, 29 Aug 2013 11:34:27 -0700
Message-ID: <CAL0qLwZmTaPFT9RgO6H=x23CC5ntSpmCS5u9gzgVE3Sf2WrGgg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
Content-Type: multipart/alternative; boundary=089e012299c81e81ea04e51a5b49
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-repute-query-http.all@tools.ietf.org" <draft-ietf-repute-query-http.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-repute-query-http-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 18:34:29 -0000

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

Thanks for the review, Meral.  Answers inline.

On Thu, Aug 29, 2013 at 1:25 AM, Meral Shirazipour <
meral.shirazipour@ericsson.com> wrote:

>  I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq .****
>
> Please resolve these comments along with any other Last Call comments you
> may receive.****
>
> ** **
>
> Document: draft-ietf-repute-query-http-09****
>
> Reviewer: Meral Shirazipour****
>
> Review Date: 2013-08-29****
>
> IETF LC End Date:  2013-08-29****
>
> IESG Telechat date: 2013-09-12****
>
> ** **
>
> ** **
>
> Summary:****
>
> This draft is almost ready to be published as Standards Track RFC but I
> have some comments.****
>
> ** **
>
> ** **
>
> Nits/editorial comments:****
>
> Nits:****
>
> -[Page 4], line 2, "attributies" --typo-->"attributes"****
>
> -[Page 4], line 8, "support support" ----> remove duplicate****
>
> -[Page 4], line 5 before last, "is cable of" ----->"is capable of"****
>
> -[Page 4], line 4 before last, "until finds" ----->"until it finds"****
>
> -[Page 5], Section 3.3, line 2, "[URI-TEMPLATE].  (See Section 3.2.)  ",
> misplaced dot after the reference.****
>
> -[Page 6], line 2, "An media" --typo-->"A media"
>

All fixed.


> ****
>
> ** **
>
> comments:****
>
> -Not sure if it was forgotten or by choice: second author's affiliation is
> missing.
>

This was intentional.


> ****
>
> -Suggestion: for references to RFCs, it is better to use the [RFC####] as
> reference in the text instead of ["name"].
>

This seems to be a stylistic choice; all of mine so far have used names.


> ****
>
> -Section 4, please double check to make sure RFC5226 is followed.
>

Is there something in particular that was missed?  There's only a single
action here, and it's pretty simple at that.


> ****
>
> -Appendix B, not sure if necessary since it is the WGs list and not some
> other mailing list.
>

I've tagged it for the RFC Editor to remove it prior to publication.

Thanks again,

-MSK

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

<div dir=3D"ltr">Thanks for the review, Meral.=A0 Answers inline.<br><br><d=
iv class=3D"gmail_extra"><div class=3D"gmail_quote">On Thu, Aug 29, 2013 at=
 1:25 AM, Meral Shirazipour <span dir=3D"ltr">&lt;<a href=3D"mailto:meral.s=
hirazipour@ericsson.com" target=3D"_blank">meral.shirazipour@ericsson.com</=
a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=
=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> .<u=
></u><u></u></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Document: draft-ietf-repute-query-http-09<u></u><u><=
/u></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<u></u><u></u></p>
<p class=3D"MsoNormal">Review Date: 2013-08-29<u></u><u></u></p>
<p class=3D"MsoNormal">IETF LC End Date:=A0 2013-08-29<u></u><u></u></p>
<p class=3D"MsoNormal">IESG Telechat date: 2013-09-12<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Summary:<u></u><u></u></p>
<p class=3D"MsoNormal">This draft is almost ready to be published as Standa=
rds Track RFC but I have some comments.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Nits/editorial comments:<u></u><u></u></p>
<p class=3D"MsoNormal">Nits:<u></u><u></u></p>
<p class=3D"MsoNormal">-[Page 4], line 2, &quot;attributies&quot; --typo--&=
gt;&quot;attributes&quot;<u></u><u></u></p>
<p class=3D"MsoNormal">-[Page 4], line 8, &quot;support support&quot; ----&=
gt; remove duplicate<u></u><u></u></p>
<p class=3D"MsoNormal">-[Page 4], line 5 before last, &quot;is cable of&quo=
t; -----&gt;&quot;is capable of&quot;<u></u><u></u></p>
<p class=3D"MsoNormal">-[Page 4], line 4 before last, &quot;until finds&quo=
t; -----&gt;&quot;until it finds&quot;<u></u><u></u></p>
<p class=3D"MsoNormal">-[Page 5], Section 3.3, line 2, &quot;[URI-TEMPLATE]=
.=A0 (See Section 3.2.)=A0 &quot;,=A0 misplaced dot after the reference.<u>=
</u><u></u></p>
<p class=3D"MsoNormal">-[Page 6], line 2, &quot;An media&quot; --typo--&gt;=
&quot;A media&quot;</p></div></div></blockquote><div><br></div><div>All fix=
ed.<br>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div><p class=3D"MsoNorm=
al"><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">comments:<u></u><u></u></p>
<p class=3D"MsoNormal">-Not sure if it was forgotten or by choice: second a=
uthor&#39;s affiliation is missing.</p></div></div></blockquote><div><br></=
div><div>This was intentional.<br>=A0<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div><p class=3D"MsoNorm=
al"><u></u><u></u></p>
<p class=3D"MsoNormal">-Suggestion: for references to RFCs, it is better to=
 use the [RFC####] as reference in the text instead of [&quot;name&quot;].<=
/p></div></div></blockquote><div><br></div><div>This seems to be a stylisti=
c choice; all of mine so far have used names.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"pur=
ple" lang=3D"EN-US"><div><p class=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal">-Section 4, please double check to make sure RFC5226=
 is followed.</p></div></div></blockquote><div><br></div><div>Is there some=
thing in particular that was missed?=A0 There&#39;s only a single action he=
re, and it&#39;s pretty simple at that.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"pur=
ple" lang=3D"EN-US"><div><p class=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal">-Appendix B, not sure if necessary since it is the W=
Gs list and not some other mailing list.</p></div></div></blockquote><div><=
br></div><div>I&#39;ve tagged it for the RFC Editor to remove it prior to p=
ublication.<br>
<br></div><div>Thanks again,<br><br></div><div>-MSK<br></div></div></div></=
div>

--089e012299c81e81ea04e51a5b49--

From meral.shirazipour@ericsson.com  Thu Aug 29 11:36:40 2013
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8A721F9F2B for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 11:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NfTPKjC72uo6 for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 11:36:35 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id E771B21F9EE5 for <gen-art@ietf.org>; Thu, 29 Aug 2013 11:36:34 -0700 (PDT)
X-AuditID: c6180641-b7fe28e000000d82-b8-521f94b16d02
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id E9.BA.03458.1B49F125; Thu, 29 Aug 2013 20:36:34 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.02.0328.009; Thu, 29 Aug 2013 14:36:33 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Thread-Topic: Gen-ART Last Call review of draft-ietf-repute-query-http-09
Thread-Index: Ac6kkU8GOcc/k7z1Rr2UreUbccKhCQAdpwyAAAhYwcA=
Date: Thu, 29 Aug 2013 18:36:33 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A632D1A@eusaamb107.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A630E6A@eusaamb107.ericsson.se> <CAL0qLwZmTaPFT9RgO6H=x23CC5ntSpmCS5u9gzgVE3Sf2WrGgg@mail.gmail.com>
In-Reply-To: <CAL0qLwZmTaPFT9RgO6H=x23CC5ntSpmCS5u9gzgVE3Sf2WrGgg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A632D1Aeusaamb107ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrALMWRmVeSWpSXmKPExsUyuXRPiO6mKfJBBu8uCli8OBdtcfXVZxaL id8b2ByYPXbOusvusWTJTyaPL5c/swUwR3HZpKTmZJalFunbJXBltL7Yx14wLbli1cm7LA2M kyK6GDk5JARMJK6d28kMYYtJXLi3nq2LkYtDSOAoo8TluesYQRJCAssZJW798gWx2QQsJLb/ fs4KYosI6Et86J3NCNLALDCJUeL36dtgCWEBD4mNdx+wQxR5ShyZuZwZwraSOP9zDRuIzSKg KtGz7w4LiM0r4C2x9OMFZojNQINm/n8F1sApECixfVE7mM0IdN73U2uYQGxmAXGJW0/mM0Gc LSCxZM95qBdEJV4+/scKYStLfJ/ziAWiPl/i8M+HjBDLBCVOznzCMoFRdBaSUbOQlM1CUgYR 15FYsPsTG4StLbFs4WtmGPvMgcdMyOILGNlXMXKUFqeW5aYbGW5iBMbaMQk2xx2MCz5ZHmKU 5mBREufdoHcmUEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVANjVIc/u0nXSTsNw+UmPaZy58QX /uw4kKh/9tHFuCNcp1zS/R8pFTTm9fyTbcxO+eSie9Pwk/Rr0Zt5phFb/fl/b26bsD+plTPz OWNj5+eaq4090ZeTg6+vOnC3OO/l7RMud6brVjCwhL9gr285+/g356OjKmELtnLNWqWXc6xG Y26xbmxNwBklluKMREMt5qLiRACVhxaVgwIAAA==
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-repute-query-http.all@tools.ietf.org" <draft-ietf-repute-query-http.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-repute-query-http-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 18:36:40 -0000

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

Hi,
   Thank you for the clarifications. I have no more comments.

Best Regards,
Meral

From: Murray S. Kucherawy [mailto:superuser@gmail.com]
Sent: Thursday, August 29, 2013 11:34 AM
To: Meral Shirazipour
Cc: draft-ietf-repute-query-http.all@tools.ietf.org; gen-art@ietf.org
Subject: Re: Gen-ART Last Call review of draft-ietf-repute-query-http-09

Thanks for the review, Meral.  Answers inline.
On Thu, Aug 29, 2013 at 1:25 AM, Meral Shirazipour <meral.shirazipour@erics=
son.com<mailto:meral.shirazipour@ericsson.com>> wrote:
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at http://wiki.tools.ietf.org/area/gen/trac/wiki/GenA=
rtfaq .
Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-repute-query-http-09
Reviewer: Meral Shirazipour
Review Date: 2013-08-29
IETF LC End Date:  2013-08-29
IESG Telechat date: 2013-09-12


Summary:
This draft is almost ready to be published as Standards Track RFC but I hav=
e some comments.


Nits/editorial comments:
Nits:
-[Page 4], line 2, "attributies" --typo-->"attributes"
-[Page 4], line 8, "support support" ----> remove duplicate
-[Page 4], line 5 before last, "is cable of" ----->"is capable of"
-[Page 4], line 4 before last, "until finds" ----->"until it finds"
-[Page 5], Section 3.3, line 2, "[URI-TEMPLATE].  (See Section 3.2.)  ",  m=
isplaced dot after the reference.
-[Page 6], line 2, "An media" --typo-->"A media"

All fixed.


comments:
-Not sure if it was forgotten or by choice: second author's affiliation is =
missing.

This was intentional.

-Suggestion: for references to RFCs, it is better to use the [RFC####] as r=
eference in the text instead of ["name"].

This seems to be a stylistic choice; all of mine so far have used names.

-Section 4, please double check to make sure RFC5226 is followed.

Is there something in particular that was missed?  There's only a single ac=
tion here, and it's pretty simple at that.

-Appendix B, not sure if necessary since it is the WGs list and not some ot=
her mailing list.

I've tagged it for the RFC Editor to remove it prior to publication.
Thanks again,
-MSK

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp; Thank you fo=
r the clarifications. I have no more comments.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best Regards,<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Meral<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Murray S=
. Kucherawy [mailto:superuser@gmail.com]
<br>
<b>Sent:</b> Thursday, August 29, 2013 11:34 AM<br>
<b>To:</b> Meral Shirazipour<br>
<b>Cc:</b> draft-ietf-repute-query-http.all@tools.ietf.org; gen-art@ietf.or=
g<br>
<b>Subject:</b> Re: Gen-ART Last Call review of draft-ietf-repute-query-htt=
p-09<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Thanks for the review=
, Meral.&nbsp; Answers inline.<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On Thu, Aug 29, 2013 at 1:25 AM, Meral Shirazipour &=
lt;<a href=3D"mailto:meral.shirazipour@ericsson.com" target=3D"_blank">mera=
l.shirazipour@ericsson.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I am the assigned Gen-ART reviewer for this draft. For background =
on Gen-ART, please see the FAQ at
<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> .<o:p></o:p></p=
>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Please resolve these comments along with any other Last Call comme=
nts you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Document: draft-ietf-repute-query-http-09<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Review Date: 2013-08-29<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">IETF LC End Date:&nbsp; 2013-08-29<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">IESG Telechat date: 2013-09-12<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">This draft is almost ready to be published as Standards Track RFC =
but I have some comments.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Nits:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-[Page 4], line 2, &quot;attributies&quot; --typo--&gt;&quot;attri=
butes&quot;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-[Page 4], line 8, &quot;support support&quot; ----&gt; remove dup=
licate<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-[Page 4], line 5 before last, &quot;is cable of&quot; -----&gt;&q=
uot;is capable of&quot;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-[Page 4], line 4 before last, &quot;until finds&quot; -----&gt;&q=
uot;until it finds&quot;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-[Page 5], Section 3.3, line 2, &quot;[URI-TEMPLATE].&nbsp; (See S=
ection 3.2.)&nbsp; &quot;,&nbsp; misplaced dot after the reference.<o:p></o=
:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-[Page 6], line 2, &quot;An media&quot; --typo--&gt;&quot;A media&=
quot;<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">All fixed.<br>
&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">comments:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-Not sure if it was forgotten or by choice: second author's affili=
ation is missing.<o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This was intentional.<br>
&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-Suggestion: for references to RFCs, it is better to use the [RFC#=
###] as reference in the text instead of [&quot;name&quot;].<o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This seems to be a stylistic choice; all of mine so =
far have used names.<br>
&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-Section 4, please double check to make sure RFC5226 is followed.<=
o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Is there something in particular that was missed?&nb=
sp; There's only a single action here, and it's pretty simple at that.<br>
&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-Appendix B, not sure if necessary since it is the WGs list and no=
t some other mailing list.<o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">I've tagged it for th=
e RFC Editor to remove it prior to publication.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Thanks again,<o:p></o=
:p></p>
</div>
<div>
<p class=3D"MsoNormal">-MSK<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A632D1Aeusaamb107ericsso_--

From mahoney@nostrum.com  Thu Aug 29 15:49:11 2013
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2274411E818E for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 15:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YdAZP9xhpqOr for <gen-art@ietfa.amsl.com>; Thu, 29 Aug 2013 15:49:10 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9E27911E818B for <gen-art@ietf.org>; Thu, 29 Aug 2013 15:49:10 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-52-22.dllstx.fios.verizon.net [173.71.52.22]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7TMmt3P056590 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 29 Aug 2013 17:49:09 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <521FCFD7.3050607@nostrum.com>
Date: Thu, 29 Aug 2013 17:48:55 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.52.22 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-08-29
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 29 Aug 2013 22:49:11 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Roni Even         2013-09-10   draft-ietf-repute-model-08 *

Robert Sparks     2013-09-24   draft-cotton-rfc4020bis-01

* 2nd Last Call


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

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


The standard template is included below.

Thanks,

Jean

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From peter@akayla.com  Thu Aug 29 23:20:58 2013
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAD3F21F9E54; Thu, 29 Aug 2013 23:20: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 z5HoVmoz9f2j; Thu, 29 Aug 2013 23:20:54 -0700 (PDT)
Received: from p3plsmtpa07-09.prod.phx3.secureserver.net (p3plsmtpa07-09.prod.phx3.secureserver.net [173.201.192.238]) by ietfa.amsl.com (Postfix) with ESMTP id EE44121F9F13; Thu, 29 Aug 2013 23:20:53 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa07-09.prod.phx3.secureserver.net with  id JuLr1m00H1huGat01uLr4F; Thu, 29 Aug 2013 23:20:53 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-repute-media-type.all@tools.ietf.org>
Date: Thu, 29 Aug 2013 23:21:12 -0700
Message-ID: <01f201cea549$20f84420$62e8cc60$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6lRc04j9eLeFbcRyehsozJ+8Ayhw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-repute-media-type-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: Fri, 30 Aug 2013 06:20:58 -0000

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

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

Document: draft-ietf-repute-media-type-10
Reviewer: Peter Yee
Review Date: August-27-2013
IETF LC End Date: August-29-2013
IESG Telechat date: September-12-2013

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

This draft directs IANA to register an application/reputon+json media type.
It also defines a new IANA registry for reputation application-specific uses
of that media type.

Major issues:

Minor issues:

Authenticity and confidence ratings seem to be used interchangeably in the
document.  Authenticity is never defined, but it appears that it may
previously have been used in place of confidence.  The example spanning
pages 9 and 10 notes a confidence of 95% but uses that for the (undefined in
the document) authenticity value instead of the confidence value.  Either
define authenticity (which is absent in Section 3.1) or switch to
confidence.

Section 3.1, definition of rater: the wording of this definition could be
interpreted to mean either the party that is returning the rating
information in response to the query but which is not necessarily the party
creating the rating, or it could mean the party that created the rating.
This may go back to the muddled concept of authenticity (which seems to be
used to mean how much an unspecified "someone" believes that the rating
originated with the named rater) vs. confidence (how confident the rater is
in the rating).  This definition should be cleared up to remove the
ambiguity that floats throughout the document.

Nits:

Page 3, Section 3, 1st paragraph, 1st sentence: change "representaton" to
"representation".  Change "Javascript" to "JavaScript".

Page 3, Section 3, 1st paragraph, 3rd sentence: delete the 3rd occurrence of
"context".

Page 5, Section 4, 2nd paragraph, 2nd sentence: after "given" is there a
missing "application" or "query"?

Page 6, 1st paragraph, 1st sentence: change "specificaiton" to
"specification".

Page 7, definition of "auth-value": What is this??

Page 7, definition of ext-value, 1st comment: I think "specific syntax is
specified in specific  application" lacks specificity. ;-)

Page 8, Section 6.2, 1st sentence after 1st example: who is "we", Kemo Sabe?
This seems to imply a rater who is rating the rater.  There's also the
aforementioned issue of what authenticity means vs. confidence.

Page 9, 2nd paragraph after the example: change "an" to "a".

Page 9, 3rd paragraph after the example, 1st sentence: change " idenfities"
to "identifies".


		-Peter Yee




From alexey.melnikov@isode.com  Fri Aug 30 04:31:29 2013
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A87621F9E21; Fri, 30 Aug 2013 04:31:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=-0.596, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, 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 kNKN3YeIDQBT; Fri, 30 Aug 2013 04:31:29 -0700 (PDT)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 99A3421F9DBA; Fri, 30 Aug 2013 04:31:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1377862286; d=isode.com; s=selector; i=@isode.com; bh=mOpHpSkQptmR0bPFWHm7BJ83Y1HvZXHnibzgnNwGoXk=; 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=i3QToOf24Nmy6WXaFXMGigQ0L32K/r7hdsi9wlDMB9PUTSclAO4KACjZOr25j3y1eIPYqm uLROlNCvndNZCGuVonDnHGCgUD8L3+UvwPIjyWX8b4lY6Lyjz3kT1BIo2IES5qwDX7DY9u al8mpMCXGSg9YDBigXEC3+fj7FZxrCI=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <UiCCjQAl1ZZC@waldorf.isode.com>; Fri, 30 Aug 2013 12:31:25 +0100
Message-ID: <52208294.4030207@isode.com>
Date: Fri, 30 Aug 2013 12:31:32 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
To: draft-ietf-v6ops-rfc3316bis.all@tools.ietf.org
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>
Subject: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-rfc3316bis-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, 30 Aug 2013 11:31:29 -0000

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

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

Document: draft-ietf-v6ops-rfc3316bis-03
Reviewer: Alexey Melnikov
Review Date: 30 August 2013
IETF LC End Date: 2 September 2013
IESG Telechat date: 12 September 2013

Summary: Ready with nits.

Major issues: None

Minor issues: None

Nits:

In 1.1

This document complements the IPv6 node requirements [RFC6434] in
    places where clarifications are needed the with discussion on the use

Delete "the" before "with"?

    of these selected IPv6 specifications when operating over a cellular
    interface.

In 2.2:

RTP and SIP need Informative references.

In 2.4:

PPP needs an Informative reference.

Also, where is IPv6CP defined?


Appendix B.  Changes to RFC 3316

I think that before publication this section needs to be reworked a bit 
to have a single list of changes, referencing particular draft versions 
is not going to be very useful in the final RFC.

From jouni.nospam@gmail.com  Fri Aug 30 04:42:50 2013
Return-Path: <jouni.nospam@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 5483E21F9E3B; Fri, 30 Aug 2013 04:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_32=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 KvzhGBaSJtZO; Fri, 30 Aug 2013 04:42:50 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 66EB021F9D70; Fri, 30 Aug 2013 04:42:49 -0700 (PDT)
Received: by mail-la0-f42.google.com with SMTP id ep20so1440067lab.29 for <multiple recipients>; Fri, 30 Aug 2013 04:42:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=89uPp2INkoxEhaB9lAcogXmqrIa6L3oG0XIA1tLXc9g=; b=AmQcvYJKcAm61E7vzBg4CZPVliTwVLU818TGJHfeOPZZ0Q3lwObDB0FuKWFLbceY8H y6cU9OT8GEVDDpQY7vItk5+9Gp5JfeMlLgF/zPGzeBMgh+wr9yFbGwg8j0fOhlWaWJZL WzW6nfj6UThoBD8Yn66MHgarLYFlexXGN/YdCB9P4Nf/XfM/0IFS7gMzQm1mSx1MUvme N81H2VP3Mrh/NL1OZYVztvl43LWzMeZWMbqscHraNBxi7etc4vY/r6yaolwmADZZo/D3 Mw6gn0WPGXbfd7UydxOBXkdpVIlfyKa9kw4KHoZCKmibUp16Dv4wa1CdHqfO6JpCXOmZ 0TZg==
X-Received: by 10.152.3.42 with SMTP id 10mr7688574laz.22.1377862967064; Fri, 30 Aug 2013 04:42:47 -0700 (PDT)
Received: from [192.168.250.230] ([194.100.71.98]) by mx.google.com with ESMTPSA id bg3sm13690271lbb.15.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 30 Aug 2013 04:42:42 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <52208294.4030207@isode.com>
Date: Fri, 30 Aug 2013 14:42:41 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D0FD40F-E0D2-4A80-8400-840C799EC386@gmail.com>
References: <52208294.4030207@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-v6ops-rfc3316bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-rfc3316bis-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, 30 Aug 2013 11:42:50 -0000

Thanks Alexey,

We'll take care of these comments asap.

- Jouni


On Aug 30, 2013, at 2:31 PM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document: draft-ietf-v6ops-rfc3316bis-03
> Reviewer: Alexey Melnikov
> Review Date: 30 August 2013
> IETF LC End Date: 2 September 2013
> IESG Telechat date: 12 September 2013
>=20
> Summary: Ready with nits.
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits:
>=20
> In 1.1
>=20
> This document complements the IPv6 node requirements [RFC6434] in
>   places where clarifications are needed the with discussion on the =
use
>=20
> Delete "the" before "with"?
>=20
>   of these selected IPv6 specifications when operating over a cellular
>   interface.
>=20
> In 2.2:
>=20
> RTP and SIP need Informative references.
>=20
> In 2.4:
>=20
> PPP needs an Informative reference.
>=20
> Also, where is IPv6CP defined?
>=20
>=20
> Appendix B.  Changes to RFC 3316
>=20
> I think that before publication this section needs to be reworked a =
bit to have a single list of changes, referencing particular draft =
versions is not going to be very useful in the final RFC.


From jari.arkko@piuha.net  Fri Aug 30 04:52:11 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 083B321F9ECE; Fri, 30 Aug 2013 04:52:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.298
X-Spam-Level: 
X-Spam-Status: No, score=-102.298 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, 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 TS0HXY3kHkrC; Fri, 30 Aug 2013 04:52:06 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id F346821F9EA9; Fri, 30 Aug 2013 04:51:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8BD1C2CC56; Fri, 30 Aug 2013 14:51:51 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gHj0GBndV3Yy; Fri, 30 Aug 2013 14:51:50 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id ECF332CC48; Fri, 30 Aug 2013 14:51:50 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D0FD40F-E0D2-4A80-8400-840C799EC386@gmail.com>
Date: Fri, 30 Aug 2013 14:51:50 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7D461EE-FE2C-46A6-A7CD-BCC0DA656BB0@piuha.net>
References: <52208294.4030207@isode.com> <8D0FD40F-E0D2-4A80-8400-840C799EC386@gmail.com>
To: Jouni Korhonen <jouni.nospam@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-v6ops-rfc3316bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-rfc3316bis-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, 30 Aug 2013 11:52:11 -0000

Thank you Alexey for your comments!

jari

On Aug 30, 2013, at 2:42 PM, Jouni Korhonen <jouni.nospam@gmail.com> =
wrote:

>=20
> Thanks Alexey,
>=20
> We'll take care of these comments asap.
>=20
> - Jouni
>=20
>=20
> On Aug 30, 2013, at 2:31 PM, Alexey Melnikov =
<alexey.melnikov@isode.com> wrote:
>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>=20
>> Please resolve these comments along with any other Last Call comments =
you may receive.
>>=20
>> Document: draft-ietf-v6ops-rfc3316bis-03
>> Reviewer: Alexey Melnikov
>> Review Date: 30 August 2013
>> IETF LC End Date: 2 September 2013
>> IESG Telechat date: 12 September 2013
>>=20
>> Summary: Ready with nits.
>>=20
>> Major issues: None
>>=20
>> Minor issues: None
>>=20
>> Nits:
>>=20
>> In 1.1
>>=20
>> This document complements the IPv6 node requirements [RFC6434] in
>>  places where clarifications are needed the with discussion on the =
use
>>=20
>> Delete "the" before "with"?
>>=20
>>  of these selected IPv6 specifications when operating over a cellular
>>  interface.
>>=20
>> In 2.2:
>>=20
>> RTP and SIP need Informative references.
>>=20
>> In 2.4:
>>=20
>> PPP needs an Informative reference.
>>=20
>> Also, where is IPv6CP defined?
>>=20
>>=20
>> Appendix B.  Changes to RFC 3316
>>=20
>> I think that before publication this section needs to be reworked a =
bit to have a single list of changes, referencing particular draft =
versions is not going to be very useful in the final RFC.
>=20


From ron.even.tlv@gmail.com  Sat Aug 31 04:30:07 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A98BF11E8141; Sat, 31 Aug 2013 04:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.583
X-Spam-Level: 
X-Spam-Status: No, score=-2.583 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hKGuVdPg-+Ae; Sat, 31 Aug 2013 04:30:06 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id E510411E8140; Sat, 31 Aug 2013 04:30:05 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id c11so389898wgh.5 for <multiple recipients>; Sat, 31 Aug 2013 04:30:05 -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 :thread-index:content-language; bh=E/xERvTptF4plyVZLXWy0wbK/w5jq5nWAfcOoGoBFO4=; b=VlFHP7tWjNBB+Jzqu7fvTMi8idPsrzQfuo7gcvQRCHGXAyXA75cIs2i2o9jWP3mfHx /UlU8oKeiHJeApv3Xi7K6k6+f+uiwGvY7AN7cHy6xDpxe06+Jowyzt0gWHkE9oKEMIWp 5vDlXTxoz1g4VoLq/5maOrYmSwRsUZZyKbLAr4lWQ1Ii8IE2rKTxNNpc2QU9WrXN3STV hfpeLPars12xRbJJRfjkLtuexYq9OXGUgVXwmNYnFdiEetSTCrZYjNnFY2qH7CROZLU7 RSSbjI38wttoJG2UHfGhmgXgh89iymoStlo6s/4aPwq3uaWictW1AmmiJyBuuAEPjTH/ 2z7g==
X-Received: by 10.180.9.69 with SMTP id x5mr6048842wia.41.1377948605046; Sat, 31 Aug 2013 04:30:05 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id r6sm3346401wiw.0.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 31 Aug 2013 04:30:04 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-repute-model.all@tools.ietf.org>
Date: Sat, 31 Aug 2013 14:27:34 +0300
Message-ID: <00bc01cea63d$186aee80$4940cb80$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BD_01CEA656.3DB8C2C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6mPJbMGY3dBgwARLqHKWvc/8h3RA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-repute-model-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 11:30:07 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00BD_01CEA656.3DB8C2C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I was asked to review the 08 version but my comments from 07 were not
addressed and I did not see any response. So I am resending my previous
review

As for making it a standard track document, I am not sure since it looks to
me as an overview and not standard. And there is no normative language in
the document.

Roni Even

 

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-repute-model-07

Reviewer: Roni Even

Review Date:2013-8-20

IETF LC End Date: 2013-8-29

IESG Telechat date: 

 

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

 

 

Major issues:

Minor issues:

I was wondering why the "Further Discussion" section 9.3 is part of the
security section. I think it should be a separate section.

Nits/editorial comments:

Section 3 the end of 2nd paragraph "mechansisms" to "mechanisms"

 

 


------=_NextPart_000_00BD_01CEA656.3DB8C2C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I was asked to review =
the 08 version but my comments from 07 were not addressed and I did not =
see any response. So I am resending my previous review<o:p></o:p></p><p =
class=3DMsoNormal>As for making it a standard track document, I am not =
sure since it looks to me as an overview and not standard. And there is =
no normative language in the document.<o:p></o:p></p><p =
class=3DMsoNormal>Roni Even<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><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>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-repute-model-07</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;8&#8211;20<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-8&#8211;29<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Major issues:<o:p></o:p></p><p =
class=3DMsoNormal>Minor issues:<o:p></o:p></p><p class=3DMsoNormal>I was =
wondering why the &#8220;Further Discussion&#8221; section 9.3 is part =
of the security section. I think it should be a separate =
section.<o:p></o:p></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p class=3DMsoNormal>Section 3 the end of =
2<sup>nd</sup> paragraph &#8220;mechansisms&#8221; to =
&#8220;mechanisms&#8221;<span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><a =
name=3Dpolicy.abstract></a><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00BD_01CEA656.3DB8C2C0--


From superuser@gmail.com  Sat Aug 31 07:40:01 2013
Return-Path: <superuser@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED29411E8119; Sat, 31 Aug 2013 07:40:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iHvkUbd1bcv6; Sat, 31 Aug 2013 07:40:01 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id C8FCA11E810C; Sat, 31 Aug 2013 07:40:00 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id c11so483434wgh.1 for <multiple recipients>; Sat, 31 Aug 2013 07:40:00 -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=MXUQ6fxwfafnmtrQjqj0q9IMbXC2RxoGbIzCkO8gqRY=; b=Ug7KQp212HiXxqpiDPtGzFK1YDiMTIeIYCnC6kcLyOfhWLB1U95eaE4DGlWVGi8pan 80QdaTjl2pOrbn/Pysd9vdvo/lg5KfF+g7fxoJ30PKmruynFvk5bctKAJmt2HVgUyMts qS4Ipc+hFmJT60pMNZaPu9gNAdjTZbLqOhYZ01eqscA1lBwB2ieWc6UeikvSRxFqn7+Y u4wakYrLphbB3J+57b8Hub/NV7iLDoDrLnxL43ISXvEMOcvK3117hUmkjPOn5jWAXsOr YeYEeOY97AXKtOZYjD2ZzSYYqX71Vd/qAPIHlQhzNtpGDhAk9bmrnQoSEeB0KVBvHUNs P/+Q==
MIME-Version: 1.0
X-Received: by 10.194.8.9 with SMTP id n9mr15608649wja.11.1377959999949; Sat, 31 Aug 2013 07:39:59 -0700 (PDT)
Received: by 10.180.75.144 with HTTP; Sat, 31 Aug 2013 07:39:59 -0700 (PDT)
In-Reply-To: <00bc01cea63d$186aee80$4940cb80$@gmail.com>
References: <00bc01cea63d$186aee80$4940cb80$@gmail.com>
Date: Sat, 31 Aug 2013 07:39:59 -0700
Message-ID: <CAL0qLwYWYMbZgtR0rAuqb9sdNY7ttXhePbCdSrq5vrfvsNaHzw@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b41c54c4fd73204e53f5001
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-repute-model.all@tools.ietf.org, ietf <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-repute-model-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 14:40:02 -0000

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

Hi Roni,

I didn't see your previous review for some reason.  I can't respond in full
now as I'm about to travel, but I will over the long weekend (unless Andrew
gets to it first).

Thanks,

-MSK



On Sat, Aug 31, 2013 at 4:27 AM, Roni Even <ron.even.tlv@gmail.com> wrote:

> I was asked to review the 08 version but my comments from 07 were not
> addressed and I did not see any response. So I am resending my previous
> review****
>
> As for making it a standard track document, I am not sure since it looks
> to me as an overview and not standard. And there is no normative language
> in the document.****
>
> Roni Even****
>
> ** **
>
> 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-repute-model-07****
>
> Reviewer: Roni Even****
>
> Review Date:2013=968=9620****
>
> IETF LC End Date: 2013-8=9629****
>
> IESG Telechat date: ****
>
> ** **
>
> Summary: This draft is ready for publication as an Informational RFC.****
>
> ** **
>
> ** **
>
> Major issues:****
>
> Minor issues:****
>
> I was wondering why the =93Further Discussion=94 section 9.3 is part of t=
he
> security section. I think it should be a separate section.****
>
> Nits/editorial comments:****
>
> Section 3 the end of 2nd paragraph =93mechansisms=94 to =93mechanisms=94*=
***
>
> ** **
>
> ** **
>

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

<div dir=3D"ltr"><div><div>Hi Roni,<br><br>I didn&#39;t see your previous r=
eview for some reason.=A0 I can&#39;t respond in full now as I&#39;m about =
to travel, but I will over the long weekend (unless Andrew gets to it first=
).<br>
<br></div>Thanks,<br><br></div>-MSK<br><br></div><div class=3D"gmail_extra"=
><br><br><div class=3D"gmail_quote">On Sat, Aug 31, 2013 at 4:27 AM, Roni E=
ven <span dir=3D"ltr">&lt;<a href=3D"mailto:ron.even.tlv@gmail.com" target=
=3D"_blank">ron.even.tlv@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"=
EN-US"><div><p class=3D"MsoNormal"><a name=3D"140d4236f5d32334_OLE_LINK2"><=
/a><a name=3D"140d4236f5d32334_OLE_LINK1"></a>I was asked to review the 08 =
version but my comments from 07 were not addressed and I did not see any re=
sponse. So I am resending my previous review<u></u><u></u></p>
<p class=3D"MsoNormal">As for making it a standard track document, I am not=
 sure since it looks to me as an overview and not standard. And there is no=
 normative language in the document.<u></u><u></u></p><p class=3D"MsoNormal=
">
Roni Even<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=A0<u></u></p><p c=
lass=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. For b=
ackground on Gen-ART, please see the FAQ at &lt;<a href=3D"http://wiki.tool=
s.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tool=
s.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<u></u><u></u></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<u></u><u></u></p><p><span style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Documen=
t: </span><span style=3D"font-family:&quot;Courier New&quot;">draft-ietf-re=
pute-model-07</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;">Reviewer: Roni Even<u></u><u></u></span></p><p><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
">Review Date:2013=968=9620<u></u><u></u></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;">IETF LC End Date: 2013-8=9629<u></u><u></u></span></p><p><s=
pan style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;">IESG Telechat date: <u></u><u></u></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;"><u></u>=A0<u></u></span></p><p><span style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary: This d=
raft is ready for publication as an Informational RFC.<u></u><u></u></span>=
</p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;"><u></u>=A0<u></u></span></p><p><span style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><u></u>=A0<u></=
u></span></p>
<p class=3D"MsoNormal">Major issues:<u></u><u></u></p><p class=3D"MsoNormal=
">Minor issues:<u></u><u></u></p><p class=3D"MsoNormal">I was wondering why=
 the =93Further Discussion=94 section 9.3 is part of the security section. =
I think it should be a separate section.<u></u><u></u></p>
<p class=3D"MsoNormal">Nits/editorial comments:<u></u><u></u></p><p class=
=3D"MsoNormal">Section 3 the end of 2<sup>nd</sup> paragraph =93mechansisms=
=94 to =93mechanisms=94<span style><u></u><u></u></span></p><p class=3D"Mso=
Normal"><a name=3D"140d4236f5d32334_policy.abstract"></a><u></u>=A0<u></u><=
/p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div></blockquote></div>=
<br></div>

--047d7b41c54c4fd73204e53f5001--

From jouni.nospam@gmail.com  Sat Aug 31 13:17:49 2013
Return-Path: <jouni.nospam@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 CAB6A11E8185; Sat, 31 Aug 2013 13:17:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.261
X-Spam-Level: 
X-Spam-Status: No, score=-2.261 tagged_above=-999 required=5 tests=[AWL=-0.262, BAYES_00=-2.599, J_CHICKENPOX_32=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 qqUWqDFMLgqH; Sat, 31 Aug 2013 13:17:49 -0700 (PDT)
Received: from mail-ee0-x233.google.com (mail-ee0-x233.google.com [IPv6:2a00:1450:4013:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id AF25211E8183; Sat, 31 Aug 2013 13:17:48 -0700 (PDT)
Received: by mail-ee0-f51.google.com with SMTP id c1so1533067eek.24 for <multiple recipients>; Sat, 31 Aug 2013 13:17:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=lYo8CGgLZD7JzBPHe3aZfLFIQOaz0WUfpepKsRfbxcA=; b=qBA9UTtQPJIOnU7kDsFbIf3yAmcHY7xDVlVh3ztcTgJ5GNw3KF68QG0EAPzbkTGY1Q lBP6zZT0CprTS2cfAyQ9BiOPxFIsBoh+IxdvhZkWorh8FUmoa94L8Dw/T7razvG9kZz1 K5/Bdg0RVxiFMo9m5RChsqIEWFXmgfXIdzc/XqMeS0q9jldcYUPlQ5EJgNdUQqXFePum fWF8vcjg+jhQDAS7SXk/f8L5aKjeb2LBEz4A0AHfVqjFpy2Q1OWzYQzzRs+QIfoM3d4O UTpin68B3dEWFpCt6wjQoDGUr6KvQXkHDklS7o4Ic4ES9pdNqY/Txw94hQvaxcKYpK/s 1n9g==
X-Received: by 10.15.99.72 with SMTP id bk48mr23085122eeb.22.1377980267735; Sat, 31 Aug 2013 13:17:47 -0700 (PDT)
Received: from [188.117.15.108] ([188.117.15.108]) by mx.google.com with ESMTPSA id x47sm7709849eea.16.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 31 Aug 2013 13:17:47 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <52208294.4030207@isode.com>
Date: Sat, 31 Aug 2013 23:17:49 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <280B4451-D7F9-49C2-B6EF-D378F80208F3@gmail.com>
References: <52208294.4030207@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1508)
Cc: gen-art@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-v6ops-rfc3316bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-v6ops-rfc3316bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 20:17:49 -0000

Alexey,

The review comments have been implemented and are visible in the github =
in-progress version:
=
https://github.com/jounikor/draft-ietf-v6ops-rfc3316bis/blob/master/draft-=
ietf-v6ops-rfc3316bis-04.txt

- Jouni


On Aug 30, 2013, at 2:31 PM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document: draft-ietf-v6ops-rfc3316bis-03
> Reviewer: Alexey Melnikov
> Review Date: 30 August 2013
> IETF LC End Date: 2 September 2013
> IESG Telechat date: 12 September 2013
>=20
> Summary: Ready with nits.
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits:
>=20
> In 1.1
>=20
> This document complements the IPv6 node requirements [RFC6434] in
>   places where clarifications are needed the with discussion on the =
use
>=20
> Delete "the" before "with"?
>=20
>   of these selected IPv6 specifications when operating over a cellular
>   interface.
>=20
> In 2.2:
>=20
> RTP and SIP need Informative references.
>=20
> In 2.4:
>=20
> PPP needs an Informative reference.
>=20
> Also, where is IPv6CP defined?
>=20
>=20
> Appendix B.  Changes to RFC 3316
>=20
> I think that before publication this section needs to be reworked a =
bit to have a single list of changes, referencing particular draft =
versions is not going to be very useful in the final RFC.

