
From meral.shirazipour@ericsson.com  Thu Jan  2 13:56:11 2014
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3FAB1AC7F3 for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 13:56:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z66HEHFW6Elv for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 13:56:09 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE621A1F4A for <gen-art@ietf.org>; Thu,  2 Jan 2014 13:56:09 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-13-52c5e06f1cdf
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id D9.A8.23183.F60E5C25; Thu,  2 Jan 2014 22:55:59 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0347.000; Thu, 2 Jan 2014 16:55:37 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-pwe3-mpls-tp-cv-adv.all@tools.ietf.org" <draft-ietf-pwe3-mpls-tp-cv-adv.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03
Thread-Index: Ac8IBRnQxbSrfPmcTXiji8qor5CPFQ==
Date: Thu, 2 Jan 2014 21:55:37 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493@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_ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUyuXSPt27+g6NBBv/brC0e7Otns7j66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJWxdH4LW0Gnf8XJt11MDYyrXLsYOTkkBEwk 7pzZwwphi0lcuLeerYuRi0NI4AijxLKJ35ghnGWMEg92rmYHqWITsJDY/vs5K0hCRGAao8Tu +/sYQRLCAm4Sn+fvB7I5gBLeEl//RoCERQT0JO42vAYrYRFQkfi59xETiM0r4Cux4egtFhCb EWjz91NrwOLMAuISt57MZ4K4SEBiyZ7zzBC2qMTLx/+gLlWW+D7nEQtEfb7EjQMNLBAzBSVO znzCMoFRaBaSUbOQlM1CUgYR15FYsPsTG4StLbFs4WtmGPvMgcdMyOILGNlXMXKUFqeW5aYb GWxiBMbDMQk23R2Me15aHmKU5mBREuf98tY5SEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAOj zT3e8sXbmfNVe5xvi0v8MUn4e0ZEedY+b+MdAgf+Ljj8b+GSRxZnVbkP7jKcsrHx385wP/n6 Mv4gHt668wcnHrqu917wtTJzklPvn9syFQtKuub9D0gVk5/P1OzzverT6aolM0x+7ftpEx73 Jjo63LpCo/7gDv4S60/Jf0suyp73339/LvsqJZbijERDLeai4kQA5adzKFUCAAA=
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 21:56:12 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493eusaamb107erics_
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-pwe3-mpls-tp-cv-adv-03
Reviewer: Meral Shirazipour
Review Date: 2014-01-02
IETF LC End Date:  2014-01-16
IESG Telechat date: NA


Summary:
This draft is ready to be published as Standards Track RFC but I have some =
editorial comments (mostly nits).


Nits/editorial comments:
Nits:
-[Page 3] Introduction, line 4, "PW s"--extra space-->"PWs".

-[Page 3] Section 2, "types of CV been defined"--missing have-->"types of C=
V have been defined"

-[Page 4] Section 2.1 "It it isrecommended"--extra it and no space--->"It i=
s recommended"

-[Page 4] Section 2.1, this statement is repeated twice, another time on th=
e sentence above it:
"The Reserved field must be set to zeroes on transmit and ignored on receiv=
e.
"
-[Page 4], Table 1 "Signalling"--for consistency with the rest of the occur=
rences-->"Signaling"

-[Page 5], Section 2.4 "advertized"--more common-->"advertised"

-[Page 5], Section 2.4 missing "a" and "are":

old:
"and common set of proactive CV types advertized"

new:
"and a common set of proactive CV types are advertised"

-[Page 5], Section 2.4 missing "are" and "the"

old:
"
If multiple MPLS-TP CV types advertised by both PEs, then following list so=
rted in
descending priority order is used:
"
new:
"
If multiple MPLS-TP CV types are advertised by both PEs, then the following=
 list sorted in
descending priority order is used:
"

General suggestion:
-
In the abstract something is missing to make it more suitable for standard =
track. Right now it only says "this document specifies how use of ABC affec=
ts XYZ".
Examples (to inspire from), Section 1 and 2 mention:

"
This document specifies how signaling
and selection processes are modified to ensure backward compatibility
and allow use of proactive CV-CC-RDI over MPLS-TP PWs.
"

and

"
This document introduces four
new CV types and, to accommodate them, a new VCCV Extended CV
parameter for PW Interface Parameters Sub-TLV is defined.
"


Best Regards,
Meral
---
Meral Shirazipour
Ericsson Research
www.ericsson.com

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493eusaamb107erics_
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-pwe3-mpls-tp-cv-adv-03<o:p></o:=
p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2014-01-02<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date:&nbsp; 2014-01-16<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: NA<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is ready to be published as Standards Tra=
ck RFC but I have some editorial comments (mostly nits).<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 3] Introduction, line 4, &quot;PW s&quot;--ex=
tra space--&gt;&quot;PWs&quot;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 3] Section 2, &quot;types of CV been defined&=
quot;--missing have--&gt;&quot;types of CV have been defined&quot;<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 4] Section 2.1 &quot;It it isrecommended&quot=
;--extra it and no space---&gt;&quot;It is recommended&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 4] Section 2.1, this statement is repeated tw=
ice, another time on the sentence above it:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;The Reserved field must be set to zeroes on tr=
ansmit and ignored on receive.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], Table 1 &quot;Signalling&quot;--for consi=
stency with the rest of the occurrences--&gt;&quot;Signaling&quot;<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 5], Section 2.4 &quot;advertized&quot;--more =
common--&gt;&quot;advertised&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 5], Section 2.4 missing &quot;a&quot; and &qu=
ot;are&quot;:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">old:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;and common set of proactive CV types advertize=
d&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">new:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;and a common set of proactive CV types are adv=
ertised&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 5], Section 2.4 missing &quot;are&quot; and &=
quot;the&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">old:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">If multiple MPLS-TP CV types advertised by both PEs,=
 then following list sorted in<o:p></o:p></p>
<p class=3D"MsoNormal">descending priority order is used:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">new:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">If multiple MPLS-TP CV types are advertised by both =
PEs, then the following list sorted in<o:p></o:p></p>
<p class=3D"MsoNormal">descending priority order is used:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">General suggestion: <o:p></o:p></p>
<p class=3D"MsoNormal">-<o:p></o:p></p>
<p class=3D"MsoNormal">In the abstract something is missing to make it more=
 suitable for standard track. Right now it only says &quot;this document sp=
ecifies how use of ABC affects XYZ&quot;.<o:p></o:p></p>
<p class=3D"MsoNormal">Examples (to inspire from), Section 1 and 2 mention:=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">This document specifies how signaling<o:p></o:p></p>
<p class=3D"MsoNormal">and selection processes are modified to ensure backw=
ard compatibility<o:p></o:p></p>
<p class=3D"MsoNormal">and allow use of proactive CV-CC-RDI over MPLS-TP PW=
s.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">and <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">This document introduces four<o:p></o:p></p>
<p class=3D"MsoNormal">new CV types and, to accommodate them, a new VCCV Ex=
tended CV<o:p></o:p></p>
<p class=3D"MsoNormal">parameter for PW Interface Parameters Sub-TLV is def=
ined.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493eusaamb107erics_--

From gregory.mirsky@ericsson.com  Thu Jan  2 14:56:56 2014
Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9D561ACCF8 for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 14:56:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 426b_tQT4K_A for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 14:56:55 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id C99F21ACCE5 for <gen-art@ietf.org>; Thu,  2 Jan 2014 14:56:54 -0800 (PST)
X-AuditID: c6180641-b7fbd8e0000011cc-32-52c5eeae6a44
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 28.8B.04556.EAEE5C25; Thu,  2 Jan 2014 23:56:47 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0347.000; Thu, 2 Jan 2014 17:56:21 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03
Thread-Index: Ac8IBRnQxbSrfPmcTXiji8qor5CPFQAAyGlw
Date: Thu, 2 Jan 2014 22:56:20 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B74265A@eusaamb103.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493@eusaamb107.ericsson.se>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493@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_7347100B5761DC41A166AC17F22DF1121B74265Aeusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNLMWRmVeSWpSXmKPExsUyuXRPgu76d0eDDF7+Z7W4+uoziwOjx5Il P5kCGKO4bFJSczLLUov07RK4Mp4eTyy4Ylsxf8YHpgbGbrMuRk4OCQETidVvfjNB2GISF+6t Z+ti5OIQEjjCKNHz6TALhLOMUWLOil5WkCo2ASOJFxt72EFsEYF4iZMzXgMVcXAIC3hJnFoS AWKKCHhLfP0LZRpJ7LguAlLMIqAicWP1DSaQMK+Ar8SkhdIgYSEgs71hFwuIzSngJ9E4ow1s DyPQNd9PrQG7jFlAXOLWk/lQVwpILNlznhnCFpV4+fgfK4StLPF9ziMWiPp8iWmPN4PV8woI Spyc+YRlAqPILCSjZiEpm4WkDCKuI7Fg9yc2CFtbYtnC18ww9pkDj5mQxRcwsq9i5CgtTi3L TTcy3MQIjJBjEmyOOxgXfLI8xCjNwaIkzvvlrXOQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6p BsbMoOuvqrpD3tsfqNe/9HFhJbPYwdiPaqIxiQWP5l4v+zapV17W3XTpo7lf6+ZWah7ykqie 9qBg0tfXih+r75W/fH/6eR6Dq47bVlWzKQdf5V86N+/hFY0TUqtLPkwN/c21SKvCU6P8ZMq8 jp0LS/bmPo1feHn6kfiOxtNHWN5ltv78+az6QIWlEktxRqKhFnNRcSIAJTW5tV4CAAA=
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 22:56:57 -0000

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

Dear Meral,
many thanks for your kind consideration and thoughtful suggestions. I've up=
dated text accordingly with exception of only one. Please check proposed mi=
nor changes below. Please let me know if you agree.

                Regards,
                                Greg

[...]
-[Page 5], Section 2.4 missing "a" and "are":

old:
"and common set of proactive CV types advertized"

new:
"and a common set of proactive CV types are advertised"
GIM>> "and a common set of proactive CV types that are advertised ..."

General suggestion:
-
In the abstract something is missing to make it more suitable for standard =
track. Right now it only says "this document specifies how use of ABC affec=
ts XYZ".
Examples (to inspire from), Section 1 and 2 mention:

"
This document specifies how signaling
and selection processes are modified to ensure backward compatibility
and allow use of proactive CV-CC-RDI over MPLS-TP PWs.
"
GIM>>
"This document specifies how signaling and selection processes for Pseudowi=
re (PW) Virtual Circuit Connectivity Verification (VCCV) are modified to en=
sure backward compatibility and allow use of proactive Connectivity Verific=
ation (CV), Continuity Check (CC), and Remote Defect Indication (RDI) over =
MPLS Transport Profile (MPLS-TP) PWs."
and

"
This document introduces four
new CV types and, to accommodate them, a new VCCV Extended CV
parameter for PW Interface Parameters Sub-TLV is defined.
"


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

--_000_7347100B5761DC41A166AC17F22DF1121B74265Aeusaamb103erics_
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: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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
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.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"color:#1F497D">Dear Meral,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">many thanks for your k=
ind consideration and thoughtful suggestions. I&#8217;ve updated text accor=
dingly with exception of only one. Please check proposed minor changes belo=
w. Please let me know if you agree.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regard=
s,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Greg<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:#1F497D">[&#8230;]</span></b><o:=
p></o:p></p>
<p class=3D"MsoNormal">-[Page 5], Section 2.4 missing &quot;a&quot; and &qu=
ot;are&quot;:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">old:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;and common set of proactive CV types advertize=
d&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">new:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;and a common set of proactive CV types are adv=
ertised&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">GIM&gt;&gt; &#8220;and=
 a common set of proactive CV types that are advertised &#8230;&#8221;</spa=
n><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">General suggestion: <o:p></o:p></p>
<p class=3D"MsoNormal">-<o:p></o:p></p>
<p class=3D"MsoNormal">In the abstract something is missing to make it more=
 suitable for standard track. Right now it only says &quot;this document sp=
ecifies how use of ABC affects XYZ&quot;.<o:p></o:p></p>
<p class=3D"MsoNormal">Examples (to inspire from), Section 1 and 2 mention:=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">This document specifies how signaling<o:p></o:p></p>
<p class=3D"MsoNormal">and selection processes are modified to ensure backw=
ard compatibility<o:p></o:p></p>
<p class=3D"MsoNormal">and allow use of proactive CV-CC-RDI over MPLS-TP PW=
s.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">GIM&gt;&gt;<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;This document s=
pecifies how signaling and selection processes for Pseudowire (PW) Virtual =
Circuit Connectivity Verification (VCCV) are modified to ensure backward co=
mpatibility and allow use of proactive Connectivity
 Verification (CV), Continuity Check (CC), and Remote Defect Indication (RD=
I) over MPLS Transport Profile (MPLS-TP) PWs.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal">and <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">This document introduces four<o:p></o:p></p>
<p class=3D"MsoNormal">new CV types and, to accommodate them, a new VCCV Ex=
tended CV<o:p></o:p></p>
<p class=3D"MsoNormal">parameter for PW Interface Parameters Sub-TLV is def=
ined.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://www.ericsson.com">www.ericsson.com=
</a><o:p></o:p></p>
</div>
</body>
</html>

--_000_7347100B5761DC41A166AC17F22DF1121B74265Aeusaamb103erics_--

From mahoney@nostrum.com  Thu Jan  2 15:18:24 2014
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22CE41A1F78 for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 15:18:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VWXagNJGAEyA for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 15:18:22 -0800 (PST)
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 D01051A1DFA for <gen-art@ietf.org>; Thu,  2 Jan 2014 15:18:22 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s02NIEvh080059 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 2 Jan 2014 17:18:15 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52C5F3B6.9000704@nostrum.com>
Date: Thu, 02 Jan 2014 17:18:14 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2013-01-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 23:18:24 -0000

Happy new year, all!

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Peter Yee         2014-01-17   draft-ietf-mpls-multipath-use-03

Roni Even         2014-01-16   draft-ietf-mpls-in-udp-04

Robert Sparks     2014-01-17   draft-ietf-mpls-moving-iana-registries-03

Russ Housley      2014-01-16   draft-ietf-mpls-tp-p2mp-framework-05

Scott Brim        2014-01-16   draft-ietf-avtcore-clksrc-09

Suresh Krishnan   2014-01-30   status-change-5343-5590-5991-6353-to-internet-standard



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 Jan  2 15:30:05 2014
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92D531AD6BF for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 15:30:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YSTDjxJpZwI6 for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 15:30:04 -0800 (PST)
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 5E1291AD67A for <gen-art@ietf.org>; Thu,  2 Jan 2014 15:30:04 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s02NTuYK080466 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 2 Jan 2014 17:29:57 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52C5F674.10407@nostrum.com>
Date: Thu, 02 Jan 2014 17:29:56 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2014-01-09 Telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 23:30:05 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft
------------------------------------------------------------------------------------
Alexey Melnikov        2013-12-23   draft-ietf-savi-send-10

Ben Campbell           2013-12-09 draft-ietf-avtcore-leap-second-07 *

Brian Carpenter        2013-12-01 draft-moonesamy-ietf-conduct-3184bis-05 *

Christer Holmberg      2013-11-27 draft-ietf-pwe3-dynamic-ms-pw-20 *
Christer Holmberg      2013-12-17 draft-ietf-ospf-manet-single-hop-or-04 *
Christer Holmberg      2013-12-23   draft-ietf-trill-o-pw-04 *

Dan Romascanu          2013-12-24 draft-ietf-isis-rfc1142-to-historic-00 **

Elwyn Davies           2013-12-23   draft-ietf-trill-rfc6327bis-02 **

Kathleen Moriarty      2013-09-26 
draft-ietf-clue-telepresence-use-cases-08 *
Kathleen Moriarty      2013-11-06 draft-ietf-pim-explicit-tracking-09 **

Roni Even              2013-11-27   draft-ietf-idr-extcomm-iana-02

Russ Housley           2013-10-01 draft-ietf-siprec-architecture-11 *

Wassim Haddad          2013-12-23 draft-ietf-netmod-iana-if-type-09 **

* Earlier draft reviewed
** Already reviewed


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

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

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

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

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From brian.e.carpenter@gmail.com  Thu Jan  2 15:54:50 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A70A1AD957 for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 15:54:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2LmAReNRYr-r for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 15:54:48 -0800 (PST)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 9FFD41AC4A7 for <gen-art@ietf.org>; Thu,  2 Jan 2014 15:54:48 -0800 (PST)
Received: by mail-pb0-f49.google.com with SMTP id jt11so14971088pbb.36 for <gen-art@ietf.org>; Thu, 02 Jan 2014 15:54:41 -0800 (PST)
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=KrjN4u8USxksAN2jB6IjsaaRnp15gcnsqvFypXWheGo=; b=xJm8CT6itm9fKk7OAzmipqAwFzm1jVHC5ese1PevSAxK1JE42hhtzTZ+NUEuqtOwhO h/fAvpJ6Eb/W5ze/rqVqqEKDdEwo/OsYb1EFnoqsEm516J4uXcIAPWZ1HLG7kZGXdC9M vkqRfhiNaxaFmNT6USe501dLnhkcHyeRMK/YxcawHAuddbLRM6t9gSEc87U7iqiItQdm oSPpAqgPxClXJUjbNMRGeuwBjOy+6iIt2XgJuu2W+Dr4RfbYGIy3+fuc8JkU9Z/oxkKC 6/JvCU2T71aOJD/vfg1EAdNVA7oYis2DG571Y1v21PqZkYwcxW/j7lLIlBI4+yHANmwo umzA==
X-Received: by 10.66.25.36 with SMTP id z4mr92122643paf.101.1388706881705; Thu, 02 Jan 2014 15:54:41 -0800 (PST)
Received: from [192.168.178.21] (165.199.69.111.dynamic.snap.net.nz. [111.69.199.165]) by mx.google.com with ESMTPSA id wp8sm104447124pbc.26.2014.01.02.15.54.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Jan 2014 15:54:41 -0800 (PST)
Message-ID: <52C5FC48.70809@gmail.com>
Date: Fri, 03 Jan 2014 12:54:48 +1300
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-moonesamy-ietf-conduct-3184bis.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-moonesamy-ietf-conduct-3184bis-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 23:54:50 -0000

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

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

Document: draft-moonesamy-ietf-conduct-3184bis-05.txt
Reviewer: Brian Carpenter
Review Date: 2014-01-03
IETF LC End Date: 2013-12-01 (+ extension)
IESG Telechat date: 2014-01-09

Summary:  Ready
--------

Comment:
--------

I made some comments on my personal opinion of the content of
this draft, which contributed to the recent updates. I also have
some sympathy with Russ Housley's recent comments, but the
wordsmithing has to stop somewhere.

Issues:
-------

>From the Gen-ART point of view, I found no problems in this draft.


From jari.arkko@ericsson.com  Thu Jan  2 15:55:35 2014
Return-Path: <jari.arkko@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E2071A1F63 for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 15:55:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pM4In4IIbXsW for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 15:55:34 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 696351A1521 for <gen-art@ietf.org>; Thu,  2 Jan 2014 15:55:33 -0800 (PST)
X-AuditID: c1b4fb25-b7eff8e000000eda-e5-52c5fc6dbc63
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 5E.5B.03802.D6CF5C25; Fri,  3 Jan 2014 00:55:25 +0100 (CET)
Received: from ESESSMB307.ericsson.se ([169.254.7.171]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.02.0347.000; Fri, 3 Jan 2014 00:55:00 +0100
From: Jari Arkko <jari.arkko@ericsson.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: Gen-ART telechat review of draft-moonesamy-ietf-conduct-3184bis-05.txt
Thread-Index: AQHPCBX7lCrBKDtoKUy8f5SqIRz9nZpyC0UA
Date: Thu, 2 Jan 2014 23:54:59 +0000
Message-ID: <7EE4112C-72CF-4463-A17E-295ED6527E76@ericsson.com>
References: <52C5FC48.70809@gmail.com>
In-Reply-To: <52C5FC48.70809@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/signed; boundary="Apple-Mail=_92C9E041-BB2E-4CA7-BE60-04DDCA06506C"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyM+JvrW7un6NBBud2qVu0XdzHZLGgdRaL xdVXn1kcmD12zrrL7rFkyU8mjy+XP7MFMEdx2aSk5mSWpRbp2yVwZfza/o6p4KR5xa3O/AbG cyZdjJwcEgImEh1XP7FA2GISF+6tZ+ti5OIQEjjEKHFhz11WCGcxo8TuxgVsIFVsAloSG5dD 2CICxhKNXafBipgF1jBKfJz2mxEkISwQKvF7xStWiKIwiftH/0M1GEkcWdkFFmcRUJFY8Xo5 O4jNK2Avse3BGiYQW0hATaKl6TdYDaeAusTyn63MIDYj0HnfT0HUMAuIS9x6Mp8J4mwRiYcX T7NB2KISLx//Y4WwlSQalzyBOm4Ko8TmqyfYIJYJSpyc+YRlAqPoLCSzZiGrm4WkDqJIW2LZ wtfMsxg5gGwdickLGSHCphKvj36Esq0lZvw6yAZhK0pM6X7IvoCRYxUje25iZk56udEmRmAM HtzyW3UH451zIocYpTlYlMR5P7x1DhISSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAqPWS4Vii TLo476X9DZ/LdA16HkyYZzBNJJrjqGtg+yc2GQ03m7aEwh77qHjXaZrmCqo1W5m/qRif37n8 lZPzza3b9/ceyWNlWDlz7/wrnM5ssfPzp7XJHymX1ddavv7qOZHDQQw1+9dc6K35zFN8m7Gu 8eb+gGAdtmkhU7N0bWd5+6/8KuOqxFKckWioxVxUnAgAToDXuo8CAAA=
Cc: General Area Review Team <gen-art@ietf.org>, "<draft-moonesamy-ietf-conduct-3184bis.all@tools.ietf.org>" <draft-moonesamy-ietf-conduct-3184bis.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-moonesamy-ietf-conduct-3184bis-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 23:55:35 -0000

--Apple-Mail=_92C9E041-BB2E-4CA7-BE60-04DDCA06506C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks for your review, Brian!

Jari

On Jan 3, 2014, at 12:54 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For
> background on Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call
> comments you may receive.
>=20
> Document: draft-moonesamy-ietf-conduct-3184bis-05.txt
> Reviewer: Brian Carpenter
> Review Date: 2014-01-03
> IETF LC End Date: 2013-12-01 (+ extension)
> IESG Telechat date: 2014-01-09
>=20
> Summary:  Ready
> --------
>=20
> Comment:
> --------
>=20
> I made some comments on my personal opinion of the content of
> this draft, which contributed to the recent updates. I also have
> some sympathy with Russ Housley's recent comments, but the
> wordsmithing has to stop somewhere.
>=20
> Issues:
> -------
>=20
> =46rom the Gen-ART point of view, I found no problems in this draft.
>=20


--Apple-Mail=_92C9E041-BB2E-4CA7-BE60-04DDCA06506C
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINaDCCBEUw
ggMtoAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVs
aWFTb25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4X
DTA2MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv
1rLnfub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqT
u3TT39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMc
CYXRlobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUb
Az2oFRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB
/wQIMAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8v
cmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRh
cC50cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2
MSxvPVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNV
HQ8BAf8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb
8I+4GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXI
v6tPjhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzY
FSzz6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67
OzIKXrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3k
MXuiNuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OY
CMZ9lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAw
OjEZMBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDgg
VjMwHhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVy
YSBHcm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5D
uVdWPMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe
1X7/jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF4
6H1ibp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjgh
XYpw/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGj
ggFiMIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7ga
YqGoIxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0F
BgEwMDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7Bgcq
hXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20w
cAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vv
bi9yZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkww
DgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUE
kUm25PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDC
fkDJSgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6b
KuTPBH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHn
tP+npjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPd
OI5GtDYPMIIEqjCCA5KgAwIBAgIQTyXs3vXto5joAjtwrbnc3jANBgkqhkiG9w0BAQUFADA5MREw
DwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQTAxMB4X
DTEzMDMwNDEzMjUyMVoXDTE2MDMwNDEzMjUxOVowYjERMA8GA1UECgwIRXJpY3Nzb24xEzARBgNV
BAMMCkphcmkgQXJra28xEDAOBgNVBAUTB2xtZmphYXIxJjAkBgkqhkiG9w0BCQEWF2phcmkuYXJr
a29AZXJpY3Nzb24uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAhwriyJIY5Bbz
yZrfnFAjWFLMNc6O6Z6dw5HqexTVyrUymDobuwcFtGl3n+yc6tYcvzM85LJMotJlOJH4NHEqClEc
iMw+gFvN17PXxM2aAPuv1ZUL1wSdQ9dS94zxQEQuh4Myyfy+eqvrEBkzZaDPu4Evz6xsmCYPYSZP
t4Bo6zbwQqkRvSQUO659ytmlyiPOiWN6wxEpwwO43LEw12xFrVSOQw3AG8ULW/xHbQvInuyWQdBC
ug/1n6IJETsMWSrLFnk888IjABXKkmq42EG6RQ0BWLw8lAQwTju7rsDF9HrcTYBcu9z2u/d4cSgH
P9SkRncRm68xrt7bD2RhPf3rkQIDAQABo4IBgzCCAX8wgcAGA1UdHwSBuDCBtTCBsqCBr6CBrIY3
aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20vRXJpY3Nzb25OTEluZGl2aWR1YWxDQTAxLmNybIZx
bGRhcDovL2xkYXAudHJ1c3QudGVsaWEuY29tL2NuPUVyaWNzc29uJTIwTkwlMjBJbmRpdmlkdWFs
JTIwQ0EwMSxvPUVyaWNzc29uP2NlcnRpZmljYXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5P2Jhc2Uw
IgYDVR0RBBswGYEXamFyaS5hcmtrb0Blcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEw
MTAvBggrBgEFBQcCARYjaHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0O
BBYEFLk/k+8oySkNxYm0GyPaFaKSRQufMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCb
MA4GA1UdDwEB/wQEAwIFoDANBgkqhkiG9w0BAQUFAAOCAQEAECF65IiGH7GS+EEHre+itv2wv0OQ
Z68DWR6G9IqMkBgb8dj6JcfFsu+9p8ID1e1L/0ybeTwz1t4IPhuOuWBPohj5irYiCBJkIokUr09B
rWPyxfBrSoZ+uXVWfmZSdp15pWlEnHhuGuJkZ2a0MKrj+OEM9qfQR5Cvdlmx5PvsIhFkAFcZWldI
xBwHsEeSoGJbVvvNImiY6M27u6rhuR8HanXVdcW4B8gK489LutxKhyhT9QDFUhmyWk2qYCUJgwM/
w44sLz8tv95jDbJxAR/aOwdwF3fQgj8VB5Xwvdn6B0PhfEcd3Ju4yUz6HE6ELZWG4ruE2haUCOn4
8WStKZ/RPDGCApMwggKPAgEBME0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNz
c29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQTyXs3vXto5joAjtwrbnc3jAJBgUrDgMCGgUAoIIBGzAY
BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDAxMDIyMzU1MjRaMCMG
CSqGSIb3DQEJBDEWBBT9igUw2wtNTXmwGyg5KL7gC2NK/zBcBgkrBgEEAYI3EAQxTzBNMDkxETAP
BgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE8l
7N717aOY6AI7cK253N4wXgYLKoZIhvcNAQkQAgsxT6BNMDkxETAPBgNVBAoMCEVyaWNzc29uMSQw
IgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE8l7N717aOY6AI7cK253N4wDQYJ
KoZIhvcNAQEBBQAEggEAHuczjtqicRZzdePBD95XjmvXEbi7fnCs25cZ167opQqIpTgt35vx1jcv
Wls6BwBfbSauhTqCf01MpAN5UzMI4mktZ7ovTgYtuY/vWHtUAD0N32bLusCsssSjn+xjzz9NCeAG
E65Ku117xVqbvJRhFCn1X7nCv72hJUBs22t7Clh90EgUGfPhNXfF5vOt2+zlg5JwBAGSmL+9GBYr
c83Xq+GmrU7gOy80ng8MuYv1xTJ0+eMrmih7tcAcSZ/d1LxOU9htbAI7EsP3TRHeKnHQUAAIdrD3
c+Z7BX6gAc0EqmZUsZaUv1/zp/0OvxRE4Y8xb3MI1VgAeraBiWN3Ndg5qwAAAAAAAA==

--Apple-Mail=_92C9E041-BB2E-4CA7-BE60-04DDCA06506C--

From meral.shirazipour@ericsson.com  Thu Jan  2 16:01:38 2014
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4313E1A1EF9 for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 16:01:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETa_crvlpAVh for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 16:01:36 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id C59BD1A1521 for <gen-art@ietf.org>; Thu,  2 Jan 2014 16:01:35 -0800 (PST)
X-AuditID: c6180641-b7fbd8e0000011cc-31-52c5fdd850ee
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 34.0D.04556.8DDF5C25; Fri,  3 Jan 2014 01:01:28 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0347.000; Thu, 2 Jan 2014 19:01:03 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>
Thread-Topic: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03
Thread-Index: Ac8IBRnQxbSrfPmcTXiji8qor5CPFQAAyGlwAAOW5IA=
Date: Fri, 3 Jan 2014 00:01:02 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC93B@eusaamb107.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493@eusaamb107.ericsson.se> <7347100B5761DC41A166AC17F22DF1121B74265A@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B74265A@eusaamb103.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_ABCAA4EF18F17B4FB619EA93DEF7939A32CDC93Beusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFLMWRmVeSWpSXmKPExsUyuXRPuO6Nv0eDDO73GFhcffWZxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGa23TrIUXPCq+PqxsIHxkmMXIyeHhICJxI1t01ghbDGJC/fW s3UxcnEICRxhlHgxfQ8LhLOMUeLtzh52kCo2AQuJ7b+fg3WICBhI3F62nBnEZhbQlNjU9Byo m4NDWMBL4tSSCBBTRMBb4uvfCIhqK4lZzZvBOlkEVCT2PZ3DAmLzCvhKTHt7mRli1URGiVP3 54IlOAX8JLbMfMQEYjMCHff91BomiFXiEreezGeCOFpAYsme88wQtqjEy8f/oJ5Rlvg+5xEL RH2+xORrfxkhlglKnJz5hGUCo+gsJKNmISmbhaQMIq4jsWD3JzYIW1ti2cLXzDD2mQOPmZDF FzCyr2LkKC1OLctNNzLcxAiMn2MSbI47GBd8sjzEKM3BoiTO++Wtc5CQQHpiSWp2ampBalF8 UWlOavEhRiYOTqkGRin2Na98/qisnmOft6E8QuKw6kOL29yB6WlNi+WTZ7nGsi6SuDQnjn0+ /6SZS9Wrsn8pdl9cNCX16Nzp+bMO+W3UejTrr2uJ7gVh0aaElk19Fewsk/qV97nc2J+j9Pv0 0Tvf5OYwXLjjJvFJ58Pf9ZmBe0uXHV7dtsiCqUSLl01W4gjrKcvuGCWW4oxEQy3mouJEAAi7 wO5tAgAA
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 00:01:38 -0000

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

Hi Greg,
   Thank you for considering, it looks very good to me.

Best,
Meral

From: Gregory Mirsky
Sent: Thursday, January 02, 2014 2:56 PM
To: Meral Shirazipour; gen-art@ietf.org
Subject: RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03

Dear Meral,
many thanks for your kind consideration and thoughtful suggestions. I've up=
dated text accordingly with exception of only one. Please check proposed mi=
nor changes below. Please let me know if you agree.

                Regards,
                                Greg

[...]
-[Page 5], Section 2.4 missing "a" and "are":

old:
"and common set of proactive CV types advertized"

new:
"and a common set of proactive CV types are advertised"
GIM>> "and a common set of proactive CV types that are advertised ..."

General suggestion:
-
In the abstract something is missing to make it more suitable for standard =
track. Right now it only says "this document specifies how use of ABC affec=
ts XYZ".
Examples (to inspire from), Section 1 and 2 mention:

"
This document specifies how signaling
and selection processes are modified to ensure backward compatibility
and allow use of proactive CV-CC-RDI over MPLS-TP PWs.
"
GIM>>
"This document specifies how signaling and selection processes for Pseudowi=
re (PW) Virtual Circuit Connectivity Verification (VCCV) are modified to en=
sure backward compatibility and allow use of proactive Connectivity Verific=
ation (CV), Continuity Check (CC), and Remote Defect Indication (RDI) over =
MPLS Transport Profile (MPLS-TP) PWs."
and

"
This document introduces four
new CV types and, to accommodate them, a new VCCV Extended CV
parameter for PW Interface Parameters Sub-TLV is defined.
"


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

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32CDC93Beusaamb107erics_
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: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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Greg,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp; Thank you=
 for considering, it looks very good to me.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Best,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Meral<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=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;"> Gregory =
Mirsky
<br>
<b>Sent:</b> Thursday, January 02, 2014 2:56 PM<br>
<b>To:</b> Meral Shirazipour; gen-art@ietf.org<br>
<b>Subject:</b> RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-=
adv-03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Dear Meral,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">many thanks for your k=
ind consideration and thoughtful suggestions. I&#8217;ve updated text accor=
dingly with exception of only one. Please check proposed minor changes belo=
w. Please let me know if you agree.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regard=
s,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Greg<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:#1F497D">[&#8230;]</span></b><o:=
p></o:p></p>
<p class=3D"MsoNormal">-[Page 5], Section 2.4 missing &quot;a&quot; and &qu=
ot;are&quot;:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">old:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;and common set of proactive CV types advertize=
d&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">new:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;and a common set of proactive CV types are adv=
ertised&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">GIM&gt;&gt; &#8220;and=
 a common set of proactive CV types that are advertised &#8230;&#8221;</spa=
n><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">General suggestion: <o:p></o:p></p>
<p class=3D"MsoNormal">-<o:p></o:p></p>
<p class=3D"MsoNormal">In the abstract something is missing to make it more=
 suitable for standard track. Right now it only says &quot;this document sp=
ecifies how use of ABC affects XYZ&quot;.<o:p></o:p></p>
<p class=3D"MsoNormal">Examples (to inspire from), Section 1 and 2 mention:=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">This document specifies how signaling<o:p></o:p></p>
<p class=3D"MsoNormal">and selection processes are modified to ensure backw=
ard compatibility<o:p></o:p></p>
<p class=3D"MsoNormal">and allow use of proactive CV-CC-RDI over MPLS-TP PW=
s.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">GIM&gt;&gt;<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;This document s=
pecifies how signaling and selection processes for Pseudowire (PW) Virtual =
Circuit Connectivity Verification (VCCV) are modified to ensure backward co=
mpatibility and allow use of proactive Connectivity
 Verification (CV), Continuity Check (CC), and Remote Defect Indication (RD=
I) over MPLS Transport Profile (MPLS-TP) PWs.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal">and <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">This document introduces four<o:p></o:p></p>
<p class=3D"MsoNormal">new CV types and, to accommodate them, a new VCCV Ex=
tended CV<o:p></o:p></p>
<p class=3D"MsoNormal">parameter for PW Interface Parameters Sub-TLV is def=
ined.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://www.ericsson.com">www.ericsson.com=
</a><o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32CDC93Beusaamb107erics_--

From gregory.mirsky@ericsson.com  Thu Jan  2 16:08:51 2014
Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40F0A1A1F76 for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 16:08:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mUBomuFMeisF for <gen-art@ietfa.amsl.com>; Thu,  2 Jan 2014 16:08:47 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 86DA31A1F63 for <gen-art@ietf.org>; Thu,  2 Jan 2014 16:08:47 -0800 (PST)
X-AuditID: c6180641-b7fbd8e0000011cc-b4-52c5ff88a2dc
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 36.2D.04556.88FF5C25; Fri,  3 Jan 2014 01:08:40 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0347.000; Thu, 2 Jan 2014 19:08:15 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
Thread-Topic: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03
Thread-Index: Ac8IBRnQxbSrfPmcTXiji8qor5CPFQAAyGlwAAOW5IAAAEvoUA==
Date: Fri, 3 Jan 2014 00:08:14 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B7426F0@eusaamb103.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493@eusaamb107.ericsson.se> <7347100B5761DC41A166AC17F22DF1121B74265A@eusaamb103.ericsson.se> <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC93B@eusaamb107.ericsson.se>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC93B@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/mixed; boundary="_004_7347100B5761DC41A166AC17F22DF1121B7426F0eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA2WSe0hTURzHO7t316sgHOfMn2YRK+hpOYvQ0lKDyMIwCbIodNFNJTOZjwoq 7OFrpU1Nq6VuylxONG2TSBMq85EvXIGgU5JStNQUzSEJZts9C6T++3x/53fO9/c4LCVSMp5s XEIyJ0+QxUsYJ7ogpem4d9Zya4TPksnXr2/iJx2EDmu1vwTh6LRTwHkuPi6Vk+/cH+0Ua+nP RolZ6ehqyXIxnYbMqQrEsoB3Q0WJSIEcrbgaTJ9rGQVyYkW4BcFspoEmQofgUUM/ZctisC98 e3HfwcZivAfyH1uQjSm8BQy3xxnbo674CHRqI20oxkfBshRJskOgR98gsDGNN0LNszf8TWcc Bv1KpZBY9SFYrqrgrRzxMZiuV/MXkLW4hc5qAbFyB/MoiQMWw5ePXQxhN/g+8ltIeAMsFH+l SX4cDE+/Y4iZC3Q8GaWVyE214inVijTVijQSvwzm5jk7bwfN6zmG8DbQlU1Sf7n77Yjg/7gX GAuzkcraG4XTETQpuhkV36gRwcydDkREHYL26mwHIvQCKMqfsZ98QDD4wGIXDxE0VI4JiXiJ oLd8giaiAIFCr+Y9GbwPnle28zZi3ItgoKuUL9gVh0L6okWo4pcRDh2tSzThHdCtHOHjtsXo aocdyBCCQbdooP4dFFiHMJX31M6BkJ1XRhPGoG3qpQivhSl1qVC1Yi+2ggDrWRirmbYK8vnq M65pkHcVYlOSuNRLMb5SA7L+6jZggl8hzZx/M1rD0hJ35/kfByNEOEaWzF3kuEROHiVPieeS mpGAdfRMQ43XFQNy4ybfqfKc0M78KwX6gCHR3QPr0k7B7FJIhmJecsMQ0HLO3zTzaZVXpibU f3xjjxEkJmmHm0dbVdBN5/Xh9dGHRIbNSMpqS86oc7BXUe4uc6ClwKW60E8p7L432XhyMESt 8ZGdPRFl2Jsf5p17i3K7EDFf9r4uZsijSUInxcqkWyl5kuwP5E0Zp6MDAAA=
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 00:08:51 -0000

--_004_7347100B5761DC41A166AC17F22DF1121B7426F0eusaamb103erics_
Content-Type: multipart/alternative;
	boundary="_000_7347100B5761DC41A166AC17F22DF1121B7426F0eusaamb103erics_"

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

Hi Meral,
just published the updated version.

                Kind regards,
                                Greg

From: Meral Shirazipour
Sent: Thursday, January 02, 2014 4:01 PM
To: Gregory Mirsky
Cc: gen-art@ietf.org
Subject: RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03

Hi Greg,
   Thank you for considering, it looks very good to me.

Best,
Meral

From: Gregory Mirsky
Sent: Thursday, January 02, 2014 2:56 PM
To: Meral Shirazipour; gen-art@ietf.org<mailto:gen-art@ietf.org>
Subject: RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03

Dear Meral,
many thanks for your kind consideration and thoughtful suggestions. I've up=
dated text accordingly with exception of only one. Please check proposed mi=
nor changes below. Please let me know if you agree.

                Regards,
                                Greg

[...]
-[Page 5], Section 2.4 missing "a" and "are":

old:
"and common set of proactive CV types advertized"

new:
"and a common set of proactive CV types are advertised"
GIM>> "and a common set of proactive CV types that are advertised ..."

General suggestion:
-
In the abstract something is missing to make it more suitable for standard =
track. Right now it only says "this document specifies how use of ABC affec=
ts XYZ".
Examples (to inspire from), Section 1 and 2 mention:

"
This document specifies how signaling
and selection processes are modified to ensure backward compatibility
and allow use of proactive CV-CC-RDI over MPLS-TP PWs.
"
GIM>>
"This document specifies how signaling and selection processes for Pseudowi=
re (PW) Virtual Circuit Connectivity Verification (VCCV) are modified to en=
sure backward compatibility and allow use of proactive Connectivity Verific=
ation (CV), Continuity Check (CC), and Remote Defect Indication (RDI) over =
MPLS Transport Profile (MPLS-TP) PWs."
and

"
This document introduces four
new CV types and, to accommodate them, a new VCCV Extended CV
parameter for PW Interface Parameters Sub-TLV is defined.
"


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

--_000_7347100B5761DC41A166AC17F22DF1121B7426F0eusaamb103erics_
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: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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Meral,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">just published the upd=
ated version.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Kind r=
egards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Greg<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></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;"> Meral Sh=
irazipour
<br>
<b>Sent:</b> Thursday, January 02, 2014 4:01 PM<br>
<b>To:</b> Gregory Mirsky<br>
<b>Cc:</b> gen-art@ietf.org<br>
<b>Subject:</b> RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-=
adv-03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Greg,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp; Thank you=
 for considering, it looks very good to me.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Best,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Meral<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=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;"> Gregory =
Mirsky
<br>
<b>Sent:</b> Thursday, January 02, 2014 2:56 PM<br>
<b>To:</b> Meral Shirazipour; <a href=3D"mailto:gen-art@ietf.org">gen-art@i=
etf.org</a><br>
<b>Subject:</b> RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-=
adv-03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Dear Meral,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">many thanks for your k=
ind consideration and thoughtful suggestions. I&#8217;ve updated text accor=
dingly with exception of only one. Please check proposed minor changes belo=
w. Please let me know if you agree.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regard=
s,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Greg<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:#1F497D">[&#8230;]</span></b><o:=
p></o:p></p>
<p class=3D"MsoNormal">-[Page 5], Section 2.4 missing &quot;a&quot; and &qu=
ot;are&quot;:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">old:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;and common set of proactive CV types advertize=
d&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">new:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;and a common set of proactive CV types are adv=
ertised&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">GIM&gt;&gt; &#8220;and=
 a common set of proactive CV types that are advertised &#8230;&#8221;</spa=
n><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">General suggestion: <o:p></o:p></p>
<p class=3D"MsoNormal">-<o:p></o:p></p>
<p class=3D"MsoNormal">In the abstract something is missing to make it more=
 suitable for standard track. Right now it only says &quot;this document sp=
ecifies how use of ABC affects XYZ&quot;.<o:p></o:p></p>
<p class=3D"MsoNormal">Examples (to inspire from), Section 1 and 2 mention:=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">This document specifies how signaling<o:p></o:p></p>
<p class=3D"MsoNormal">and selection processes are modified to ensure backw=
ard compatibility<o:p></o:p></p>
<p class=3D"MsoNormal">and allow use of proactive CV-CC-RDI over MPLS-TP PW=
s.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">GIM&gt;&gt;<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;This document s=
pecifies how signaling and selection processes for Pseudowire (PW) Virtual =
Circuit Connectivity Verification (VCCV) are modified to ensure backward co=
mpatibility and allow use of proactive Connectivity
 Verification (CV), Continuity Check (CC), and Remote Defect Indication (RD=
I) over MPLS Transport Profile (MPLS-TP) PWs.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal">and <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">This document introduces four<o:p></o:p></p>
<p class=3D"MsoNormal">new CV types and, to accommodate them, a new VCCV Ex=
tended CV<o:p></o:p></p>
<p class=3D"MsoNormal">parameter for PW Interface Parameters Sub-TLV is def=
ined.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://www.ericsson.com">www.ericsson.com=
</a><o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_7347100B5761DC41A166AC17F22DF1121B7426F0eusaamb103erics_--

--_004_7347100B5761DC41A166AC17F22DF1121B7426F0eusaamb103erics_
Content-Type: message/rfc822
Content-Disposition: attachment;
	creation-date="Fri, 03 Jan 2014 00:08:12 GMT";
	modification-date="Fri, 03 Jan 2014 00:08:12 GMT"

Received: from ESESSHC022.ericsson.se (153.88.183.84) by
 EUSAAHC003.ericsson.se (147.117.188.81) with Microsoft SMTP Server (TLS) id
 14.2.347.0; Thu, 2 Jan 2014 19:06:39 -0500
Received: from sessmg10.ericsson.net (153.88.183.153) by
 smtp.internal.ericsson.com (153.88.183.85) with Microsoft SMTP Server id
 14.2.347.0; Fri, 3 Jan 2014 01:06:38 +0100
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org
 [77.72.230.30])	(using TLS with cipher AES128-SHA (128/128 bits))	(Client did
 not present a certificate)	by sessmg10.ericsson.net (Symantec Mail Security)
 with SMTP id 36.B3.07004.62FF5C25; Fri,  3 Jan 2014 01:07:02 +0100 (CET)
Received: from mail.ietf.org ([4.31.198.44]:58275)	by grenache.tools.ietf.org
 with esmtp (Exim 4.80)	(envelope-from <internet-drafts@ietf.org>)	id
 1VysI0-0002WM-Io; Fri, 03 Jan 2014 01:07:01 +0100
Received: from localhost (ietfa.amsl.com [127.0.0.1])	by ietfa.amsl.com
 (Postfix) with ESMTP id 581841A1F63;	Thu,  2 Jan 2014 16:07:00 -0800 (PST)
Received: from mail.ietf.org ([4.31.198.44])	by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024)	with ESMTP id FMtHog9DIHyg; Thu,  2
 Jan 2014 16:06:59 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1])	by ietfa.amsl.com
 (Postfix) with ESMTP id B664A1A8031;	Thu,  2 Jan 2014 16:06:57 -0800 (PST)
From: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
To: "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>,
	"draft-ietf-pwe3-mpls-tp-cv-adv@tools.ietf.org"
	<draft-ietf-pwe3-mpls-tp-cv-adv@tools.ietf.org>, "stbryant@cisco.com"
	<stbryant@cisco.com>
Subject: New Version Notification - draft-ietf-pwe3-mpls-tp-cv-adv-04.txt
Thread-Topic: New Version Notification -
 draft-ietf-pwe3-mpls-tp-cv-adv-04.txt
Thread-Index: AQHPCBesE676weM3+0qRc9Q/KwqgNQ==
Date: Fri, 3 Jan 2014 00:06:57 +0000
Message-ID: <20140103000657.11565.93437.idtracker@ietfa.amsl.com>
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: ESESSHC022.ericsson.se
X-MS-Has-Attach: 
X-Auto-Response-Suppress: All
X-MS-TNEF-Correlator: 
x-brightmail-tracker: H4sIAAAAAAAAA+NgFvrLKsWRWlGSWpSXmKPExsXi6/FMTlft/9Egg+Ub1CyeP+lidGD0+PX1
	KlsAYxSXTUpqTmZZapG+XQJXxoyFy9gLlrFULO3YxN7AeI+5i5GTQ0LARGLLjr9sELaYxIV7
	64FsLg4hgZVMEjNWtbODJIQETjFK7DitC5GYxigxf04/K0SHhsSMlRcYIRLbGCW2/t3JAuFM
	ZZTYdfMhWDuvgKDEyZlPgBIcHMwCmhLrd+mDhJkFtCWWLXwNdgabgJzE6lfTGEFsEYFkiVdP
	7rNDLBCReHf1ITPMeR2dy8AWMwLV/zj2mAnEFhAQkPg36QILxCpHiWW/NjGDrGIRUJXYdLkA
	olVRYun6OSwQdozEo7PLoGxdiW3tD6BWhUjsmTodyuaTuPjiBxPIGAmBAomFXREgYWEBT4nW
	X1+hXneQmHXqPTTgjCVeTf3LCgkrNYnlu5exQdixEm+v94M9ziNgITHvmtMERvlZSEEyCxEk
	s5CCZAEj8ypG0eLU4uLcdEMDvdSizOTi4vw8vbzUkk2MwDg/uOW33Q7Gaw8NDzFKcjApifKG
	/j0aJMSXlJ9SmZFYnBFfVJqTWnyIUZqDRUmc10LjTKCQQHpiSWp2ampBahFMVoaDQ0mCdzFI
	p2BRanpqRVpmTglCmomD8xCjBAePkghvJUgNb3FBYm5xZjpE/hSjopQ4768/QAkBkERGaR5c
	LyxVXmKUlRLmZWRgYBDiAdqbm1mCKv+KUZyDUUmYtx5kPE9mXgnc9FdAi5mAFouUHAJZXJKI
	kJJqYAwtqp19oaJFQusB9+LguxxRC50UlZWUKw32e25TN2tSZRSz5cg73hywP+HRNPOt3yTf
	znlxYNYJb5mKt27GptI/xbl+sOrvzBd5xpg1e7nVij2JjropEwt51BJWtuxVWW+S7+N300po
	S1MYZ57i5Ok/9D7+MQqsT4265dAf5iY5q+Wmf+gZJZbijERDLeai4kQAbbgx2ZADAAA=
x-auditid: c1b4fb3e-b7fe08e000001b5c-a0-52c5ff265f25
list-id: <draft-ietf-pwe3-mpls-tp-cv-adv@tools.ietf.org>
x-spam-level: 
x-spam-status: No, score=-1.9 required=3.0 tests=BAYES_00,RP_MATCHES_RCVD,
	SPF_PASS autolearn=no version=3.3.2
x-virus-scanned: amavisd-new at amsl.com
x-spam-checker-version: SpamAssassin 3.3.2 (2011-06-06) on
	grenache.tools.ietf.org
x-sa-exim-connect-ip: 4.31.198.44
x-sa-exim-scanned: Yes (on grenache.tools.ietf.org)
x-sa-exim-version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
x-sa-exim-mail-from: internet-drafts@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-ID: <07A3C690DF89DE4E83518BA5A27EBCC3@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0

DQpBIG5ldyB2ZXJzaW9uICgtMDQpIGhhcyBiZWVuIHN1Ym1pdHRlZCBmb3IgZHJhZnQtaWV0Zi1w
d2UzLW1wbHMtdHAtY3YtYWR2Og0KaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMv
ZHJhZnQtaWV0Zi1wd2UzLW1wbHMtdHAtY3YtYWR2LTA0LnR4dA0KDQoNClRoZSBJRVRGIGRhdGF0
cmFja2VyIHBhZ2UgZm9yIHRoaXMgSW50ZXJuZXQtRHJhZnQgaXM6DQpodHRwczovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLXB3ZTMtbXBscy10cC1jdi1hZHYvDQoNCkRpZmYg
ZnJvbSBwcmV2aW91cyB2ZXJzaW9uOg0KaHR0cDovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9
ZHJhZnQtaWV0Zi1wd2UzLW1wbHMtdHAtY3YtYWR2LTA0DQoNClBsZWFzZSBub3RlIHRoYXQgaXQg
bWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24N
CnVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9v
bHMuaWV0Zi5vcmcuDQoNCklFVEYgU2VjcmV0YXJpYXQuDQoNCg==

--_004_7347100B5761DC41A166AC17F22DF1121B7426F0eusaamb103erics_--

From housley@vigilsec.com  Fri Jan  3 09:00:32 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172661ADFF7; Fri,  3 Jan 2014 09:00:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9xcLLSWywrId; Fri,  3 Jan 2014 09:00:30 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 3BAC41ADFDF; Fri,  3 Jan 2014 09:00:30 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id EF0929A4241; Fri,  3 Jan 2014 12:00:12 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id 3Q38S8zLi0mS; Fri,  3 Jan 2014 11:59:51 -0500 (EST)
Received: from [192.168.2.110] (pool-96-255-140-248.washdc.fios.verizon.net [96.255.140.248]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id DE1249A4243; Fri,  3 Jan 2014 11:59:51 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 3 Jan 2014 11:59:40 -0500
Message-Id: <200D1BD7-800E-4F28-A4FD-C509B0F2EEC6@vigilsec.com>
To: draft-ietf-siprec-architecture.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-siprec-architecture-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 17:00:32 -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-siprec-architecture-11
Reviewer: Russ Housley
Review Date: 2014-01-03
IETF LC End Date: 2013-10-01
IESG Telechat date: 2014-01-09

Summary:  

Thank you for addressing the issues raised in my previous review.
This document is ready for publication as an Informational RFC.

Major Concerns:  None.

Minor Concerns:  None.

Editorial Comments:

The changes to Section 3.2.4 to resolve my earlier comment have
introduced a clarity problem.  I suggest a minor rewording to fix it.

3.2.4.  Media Stream Mixing

   In a basic session involving only audio there are typically two
   audio/RTP streams between the two UAs involved transporting media in
   each direction.  When recording this media, the two streams may be
   mixed or not mixed at the SRC before being transmitted to the SRS.
   In the case when they are not mixed, two separate streams are sent
   to the SRS.  In the mixed case, a single mixed media stream is sent
   to the SRS.  However, in the case when the media streams are not
   mixed, the SDP offer sent to the SRS must describe two separate
   media streams.


From housley@vigilsec.com  Fri Jan  3 09:31:38 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 401771ADFD7; Fri,  3 Jan 2014 09:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99ydKST2lQl5; Fri,  3 Jan 2014 09:31:36 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 7B5FB1ADBD2; Fri,  3 Jan 2014 09:31:36 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 51F2A9A423D; Fri,  3 Jan 2014 12:31:19 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id ORVn7GDBu3Km; Fri,  3 Jan 2014 12:30:58 -0500 (EST)
Received: from [192.168.2.110] (pool-96-255-140-248.washdc.fios.verizon.net [96.255.140.248]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 192259A4246; Fri,  3 Jan 2014 12:30:57 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 3 Jan 2014 12:30:45 -0500
Message-Id: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
To: draft-ietf-mpls-tp-p2mp-framework.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-p2mp-framework-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 17:31:38 -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-p2mp-framework-05
Reviewer: Russ Housley
Review Date: 2014-01-02
IETF LC End Date: 2014-01-16
IESG Telechat date: Unknown

Summary:  Ready for publication.


Question:

Should this document be an update to the MPLS-TP Framework (RFC 5921)?
I am not sure.  RFC 5921 does make it clear that it covers only point-
to-point transport paths.  The answer may be further complicated by
the fact that RFC 5921 is joint work with the ITU-T.


Major Concerns:  None.


Minor Concerns:  None.


Other Comments:

In the first sentence of Section 1, please define MPLS-TP as follows:
OLD:
   The Multiprotocol Label Switching Transport Profile is the ...
NEW:
   The Multiprotocol Label Switching Transport Profile (MPLS-TP) is ...

Please add TE-LSP to the terms defined in Section 1.2.

In Section 5.1, I cannot understand this sentence:
>
>  Per [RFC6373], the definitions of P2MP, [RFC4875], and GMPLS
>  recovery, [RFC4872] and [RFC4873], do not explicitly cover their
>  interactions.
>
I think that the references are getting in the way.  I think the
message is: "the definitions of P2MP and GMPLS recovery do not
explicitly cover their interactions."  If I am correct, then some
commas need to be removed.

The phrase "MPLS Transport Profile" appears many places, and it would
be easier if they were replaces with "MPLS-TP" for consistency.


From meral.shirazipour@ericsson.com  Fri Jan  3 09:45:08 2014
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68EF61AE041 for <gen-art@ietfa.amsl.com>; Fri,  3 Jan 2014 09:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L1Z115tyBIAj for <gen-art@ietfa.amsl.com>; Fri,  3 Jan 2014 09:45:05 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 944751AE03B for <gen-art@ietf.org>; Fri,  3 Jan 2014 09:45:05 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-72-52c6f712c944
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 02.4E.23183.217F6C25; Fri,  3 Jan 2014 18:44:50 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0347.000; Fri, 3 Jan 2014 12:44:25 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>
Thread-Topic: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03
Thread-Index: Ac8IBRnQxbSrfPmcTXiji8qor5CPFQAAyGlwAAOW5IAAAEvoUAAk5J7Q
Date: Fri, 3 Jan 2014 17:44:24 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A32CDD469@eusaamb107.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493@eusaamb107.ericsson.se> <7347100B5761DC41A166AC17F22DF1121B74265A@eusaamb103.ericsson.se> <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC93B@eusaamb107.ericsson.se> <7347100B5761DC41A166AC17F22DF1121B7426F0@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B7426F0@eusaamb103.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_ABCAA4EF18F17B4FB619EA93DEF7939A32CDD469eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrJLMWRmVeSWpSXmKPExsUyuXRPoK7Q92NBBl179S2uvvrM4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujEd/f7MWPMms6N62hbWBcVtsFyMnh4SAiUT3w1ZGCFtM4sK9 9WxdjFwcQgJHGCW6l85nhHCWMUrsf3uDDaSKTcBCYvvv56wgtoiAgcTtZcuZQWxmAU2JTU3P gWo4OIQFvCROLYkAMUUEvCW+/o2AqHaTmNbbADaFRUBFYv65mewgNq+Ar8SahrdQq2YySay8 eQLsIE4BP4nr7R/AxjMCHff91BomiFXiEreezGeCOFpAYsme88wQtqjEy8f/WCFsZYnvcx6x gNzALJAvcfELH8QuQYmTM5+wTGAUnYVk0iyEqllIqiBKdCQW7P7EBmFrSyxb+JoZxj5z4DET svgCRvZVjBylxalluelGBpsYgdFzTIJNdwfjnpeWhxilOViUxHm/vHUOEhJITyxJzU5NLUgt ii8qzUktPsTIxMEp1cCo2zufRfXv1Dezkt5MdY4sDFO/t3SmqoaS4tvwL7MjM5bPU8pJXxxd 9dX9ifMchs2G8XnMbT+M159/c9huX7IIX9a7PKazqy+57HZclpVSoLY4UvxAF9edj3devb8h 8fGw7/6OxF9Xv4YrPynWY1V/PJvtyssQj0nvrnpdzz9ktbv5/s6nHYdPKrEUZyQaajEXFScC AMWCykJsAgAA
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 17:45:08 -0000

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

Hi,
  Many thanks, looks great.

Best,
Meral

From: Gregory Mirsky
Sent: Thursday, January 02, 2014 4:08 PM
To: Meral Shirazipour
Cc: gen-art@ietf.org
Subject: RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03

Hi Meral,
just published the updated version.

                Kind regards,
                                Greg

From: Meral Shirazipour
Sent: Thursday, January 02, 2014 4:01 PM
To: Gregory Mirsky
Cc: gen-art@ietf.org<mailto:gen-art@ietf.org>
Subject: RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03

Hi Greg,
   Thank you for considering, it looks very good to me.

Best,
Meral

From: Gregory Mirsky
Sent: Thursday, January 02, 2014 2:56 PM
To: Meral Shirazipour; gen-art@ietf.org<mailto:gen-art@ietf.org>
Subject: RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03

Dear Meral,
many thanks for your kind consideration and thoughtful suggestions. I've up=
dated text accordingly with exception of only one. Please check proposed mi=
nor changes below. Please let me know if you agree.

                Regards,
                                Greg

[...]
-[Page 5], Section 2.4 missing "a" and "are":

old:
"and common set of proactive CV types advertized"

new:
"and a common set of proactive CV types are advertised"
GIM>> "and a common set of proactive CV types that are advertised ..."

General suggestion:
-
In the abstract something is missing to make it more suitable for standard =
track. Right now it only says "this document specifies how use of ABC affec=
ts XYZ".
Examples (to inspire from), Section 1 and 2 mention:

"
This document specifies how signaling
and selection processes are modified to ensure backward compatibility
and allow use of proactive CV-CC-RDI over MPLS-TP PWs.
"
GIM>>
"This document specifies how signaling and selection processes for Pseudowi=
re (PW) Virtual Circuit Connectivity Verification (VCCV) are modified to en=
sure backward compatibility and allow use of proactive Connectivity Verific=
ation (CV), Continuity Check (CC), and Remote Defect Indication (RDI) over =
MPLS Transport Profile (MPLS-TP) PWs."
and

"
This document introduces four
new CV types and, to accommodate them, a new VCCV Extended CV
parameter for PW Interface Parameters Sub-TLV is defined.
"


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

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32CDD469eusaamb107erics_
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: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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.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"color:#1F497D">Hi,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp; Many thanks, lo=
oks great.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Best,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Meral<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=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;"> Gregory =
Mirsky
<br>
<b>Sent:</b> Thursday, January 02, 2014 4:08 PM<br>
<b>To:</b> Meral Shirazipour<br>
<b>Cc:</b> gen-art@ietf.org<br>
<b>Subject:</b> RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-=
adv-03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Meral,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">just published the upd=
ated version.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Kind r=
egards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Greg<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></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;"> Meral Sh=
irazipour
<br>
<b>Sent:</b> Thursday, January 02, 2014 4:01 PM<br>
<b>To:</b> Gregory Mirsky<br>
<b>Cc:</b> <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br>
<b>Subject:</b> RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-=
adv-03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Greg,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp; Thank you=
 for considering, it looks very good to me.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Best,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Meral<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=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;"> Gregory =
Mirsky
<br>
<b>Sent:</b> Thursday, January 02, 2014 2:56 PM<br>
<b>To:</b> Meral Shirazipour; <a href=3D"mailto:gen-art@ietf.org">gen-art@i=
etf.org</a><br>
<b>Subject:</b> RE: Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-=
adv-03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Dear Meral,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">many thanks for your k=
ind consideration and thoughtful suggestions. I&#8217;ve updated text accor=
dingly with exception of only one. Please check proposed minor changes belo=
w. Please let me know if you agree.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regard=
s,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Greg<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:#1F497D">[&#8230;]</span></b><o:=
p></o:p></p>
<p class=3D"MsoNormal">-[Page 5], Section 2.4 missing &quot;a&quot; and &qu=
ot;are&quot;:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">old:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;and common set of proactive CV types advertize=
d&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">new:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;and a common set of proactive CV types are adv=
ertised&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">GIM&gt;&gt; &#8220;and=
 a common set of proactive CV types that are advertised &#8230;&#8221;</spa=
n><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">General suggestion: <o:p></o:p></p>
<p class=3D"MsoNormal">-<o:p></o:p></p>
<p class=3D"MsoNormal">In the abstract something is missing to make it more=
 suitable for standard track. Right now it only says &quot;this document sp=
ecifies how use of ABC affects XYZ&quot;.<o:p></o:p></p>
<p class=3D"MsoNormal">Examples (to inspire from), Section 1 and 2 mention:=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">This document specifies how signaling<o:p></o:p></p>
<p class=3D"MsoNormal">and selection processes are modified to ensure backw=
ard compatibility<o:p></o:p></p>
<p class=3D"MsoNormal">and allow use of proactive CV-CC-RDI over MPLS-TP PW=
s.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">GIM&gt;&gt;<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;This document s=
pecifies how signaling and selection processes for Pseudowire (PW) Virtual =
Circuit Connectivity Verification (VCCV) are modified to ensure backward co=
mpatibility and allow use of proactive Connectivity
 Verification (CV), Continuity Check (CC), and Remote Defect Indication (RD=
I) over MPLS Transport Profile (MPLS-TP) PWs.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal">and <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">This document introduces four<o:p></o:p></p>
<p class=3D"MsoNormal">new CV types and, to accommodate them, a new VCCV Ex=
tended CV<o:p></o:p></p>
<p class=3D"MsoNormal">parameter for PW Interface Parameters Sub-TLV is def=
ined.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://www.ericsson.com">www.ericsson.com=
</a><o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32CDD469eusaamb107erics_--

From agmalis@gmail.com  Fri Jan  3 11:05:23 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC7C81AC3FA for <gen-art@ietfa.amsl.com>; Fri,  3 Jan 2014 11:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCss7BL_p10F for <gen-art@ietfa.amsl.com>; Fri,  3 Jan 2014 11:05:21 -0800 (PST)
Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id B57991AC441 for <gen-art@ietf.org>; Fri,  3 Jan 2014 11:05:21 -0800 (PST)
Received: by mail-qe0-f51.google.com with SMTP id 1so15879954qee.24 for <gen-art@ietf.org>; Fri, 03 Jan 2014 11:05:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=576VjYAahpz9VY7g1mLvx3tnh57Jg+ky4DAtgJI6GmI=; b=OASBSFVouHbvTWDen0bYsBNPd9X8dRjBiEFq+X0847gXtTtdXZBEgPeVO48bAldtiF oMs75DsAmEf8SqmbpuyCyaUcHJIHzfBGgoVe1hUJ9L5S1ecTZdwMZfCfrYzKMJtEMr5E SRkR8KYxoGIvBI8xzcoai2yssX2++HI+lRGPuwJ/B4YqF3+h/Lok5+0Itcrwwls58G8B o9JPd47xylu0G2IwBCFssbWyq49RrqfmZOsvqIthe8panLeJtMN2IgE05ZKCzwEwxvDo GjTo5r6AA47DAfdWdmx/yiD7dGQsZHVI7xxK7xbcLAyOsIZ6kHwkf16gAcuz8DNB6we8 m3gQ==
X-Received: by 10.224.79.13 with SMTP id n13mr149441574qak.70.1388775914264; Fri, 03 Jan 2014 11:05:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.166.9 with HTTP; Fri, 3 Jan 2014 11:04:54 -0800 (PST)
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493@eusaamb107.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32CDC493@eusaamb107.ericsson.se>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Fri, 3 Jan 2014 14:04:54 -0500
Message-ID: <CAA=duU1-f87HLEcv3sTVTU5waEK-R=r4Uz67nsJA0C6RwtF-+A@mail.gmail.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>,  Gregory Mirsky <gregory.mirsky@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "draft-ietf-pwe3-mpls-tp-cv-adv.all@tools.ietf.org" <draft-ietf-pwe3-mpls-tp-cv-adv.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-pwe3-mpls-tp-cv-adv-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 19:05:23 -0000

Meral,

Thanks for the review!

Greg,

It looks like most, but not all, of these comments were already caught
in -04. This is really up to Stewart, but IMHO, the remaining comments
can go in instructions to the RFC Editor, or wait for a revision
triggered by further IESG or IETF-wide review.

Cheers,
Andy

On Thu, Jan 2, 2014 at 4:55 PM, 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-pwe3-mpls-tp-cv-adv-03
>
> Reviewer: Meral Shirazipour
>
> Review Date: 2014-01-02
>
> IETF LC End Date:  2014-01-16
>
> IESG Telechat date: NA
>
>
>
>
>
> Summary:
>
> This draft is ready to be published as Standards Track RFC but I have some
> editorial comments (mostly nits).
>
>
>
>
>
> Nits/editorial comments:
>
> Nits:
>
> -[Page 3] Introduction, line 4, "PW s"--extra space-->"PWs".
>
>
>
> -[Page 3] Section 2, "types of CV been defined"--missing have-->"types of CV
> have been defined"
>
>
>
> -[Page 4] Section 2.1 "It it isrecommended"--extra it and no space--->"It is
> recommended"
>
>
>
> -[Page 4] Section 2.1, this statement is repeated twice, another time on the
> sentence above it:
>
> "The Reserved field must be set to zeroes on transmit and ignored on
> receive.
>
> "
>
> -[Page 4], Table 1 "Signalling"--for consistency with the rest of the
> occurrences-->"Signaling"
>
>
>
> -[Page 5], Section 2.4 "advertized"--more common-->"advertised"
>
>
>
> -[Page 5], Section 2.4 missing "a" and "are":
>
>
>
> old:
>
> "and common set of proactive CV types advertized"
>
>
>
> new:
>
> "and a common set of proactive CV types are advertised"
>
>
>
> -[Page 5], Section 2.4 missing "are" and "the"
>
>
>
> old:
>
> "
>
> If multiple MPLS-TP CV types advertised by both PEs, then following list
> sorted in
>
> descending priority order is used:
>
> "
>
> new:
>
> "
>
> If multiple MPLS-TP CV types are advertised by both PEs, then the following
> list sorted in
>
> descending priority order is used:
>
> "
>
>
>
> General suggestion:
>
> -
>
> In the abstract something is missing to make it more suitable for standard
> track. Right now it only says "this document specifies how use of ABC
> affects XYZ".
>
> Examples (to inspire from), Section 1 and 2 mention:
>
>
>
> "
>
> This document specifies how signaling
>
> and selection processes are modified to ensure backward compatibility
>
> and allow use of proactive CV-CC-RDI over MPLS-TP PWs.
>
> "
>
>
>
> and
>
>
>
> "
>
> This document introduces four
>
> new CV types and, to accommodate them, a new VCCV Extended CV
>
> parameter for PW Interface Parameters Sub-TLV is defined.
>
> "
>
>
>
>
>
> Best Regards,
>
> Meral
>
> ---
>
> Meral Shirazipour
>
> Ericsson Research
>
> www.ericsson.com

From loa@pi.nu  Sat Jan  4 04:32:27 2014
Return-Path: <loa@pi.nu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A549D1ADF38; Sat,  4 Jan 2014 04:32:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x7o221jWLVd0; Sat,  4 Jan 2014 04:32:26 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 084F51ADE8A; Sat,  4 Jan 2014 04:32:26 -0800 (PST)
Received: from [192.168.1.5] (unknown [112.208.5.107]) (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 F2FF7180150F; Sat,  4 Jan 2014 13:32:13 +0100 (CET)
Message-ID: <52C7FF47.6080705@pi.nu>
Date: Sat, 04 Jan 2014 20:32:07 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>,  draft-ietf-mpls-tp-p2mp-framework.all@tools.ietf.org
References: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
In-Reply-To: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-p2mp-framework-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 04 Jan 2014 12:32:27 -0000

Russ,

I never thought about this as an update to RFC 5921. If we publish
this document as is, every syllable of RFC 5921 remains unchanged.

This is hardly an update.

/Loa


On 2014-01-04 01:30, Russ Housley 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-tp-p2mp-framework-05
> Reviewer: Russ Housley
> Review Date: 2014-01-02
> IETF LC End Date: 2014-01-16
> IESG Telechat date: Unknown
>
> Summary:  Ready for publication.
>
>
> Question:
>
> Should this document be an update to the MPLS-TP Framework (RFC 5921)?
> I am not sure.  RFC 5921 does make it clear that it covers only point-
> to-point transport paths.  The answer may be further complicated by
> the fact that RFC 5921 is joint work with the ITU-T.
>
>
> Major Concerns:  None.
>
>
> Minor Concerns:  None.
>
>
> Other Comments:
>
> In the first sentence of Section 1, please define MPLS-TP as follows:
> OLD:
>     The Multiprotocol Label Switching Transport Profile is the ...
> NEW:
>     The Multiprotocol Label Switching Transport Profile (MPLS-TP) is ...
>
> Please add TE-LSP to the terms defined in Section 1.2.
>
> In Section 5.1, I cannot understand this sentence:
>>
>>   Per [RFC6373], the definitions of P2MP, [RFC4875], and GMPLS
>>   recovery, [RFC4872] and [RFC4873], do not explicitly cover their
>>   interactions.
>>
> I think that the references are getting in the way.  I think the
> message is: "the definitions of P2MP and GMPLS recovery do not
> explicitly cover their interactions."  If I am correct, then some
> commas need to be removed.
>
> The phrase "MPLS Transport Profile" appears many places, and it would
> be easier if they were replaces with "MPLS-TP" for consistency.
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From adrian@olddog.co.uk  Sat Jan  4 05:28:34 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E3051ADF7B; Sat,  4 Jan 2014 05:28:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s5mVbOktUCKP; Sat,  4 Jan 2014 05:28:32 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 80A8A1ADF85; Sat,  4 Jan 2014 05:28:32 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s04DSN0O024623; Sat, 4 Jan 2014 13:28:23 GMT
Received: from 950129200 (AGrenoble-651-1-487-66.w90-42.abo.wanadoo.fr [90.42.183.66]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s04DSI4X024598 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 4 Jan 2014 13:28:22 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Russ Housley'" <housley@vigilsec.com>, <draft-ietf-mpls-tp-p2mp-framework.all@tools.ietf.org>
References: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
In-Reply-To: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
Date: Sat, 4 Jan 2014 13:28:20 -0000
Message-ID: <008d01cf0950$d86d2920$89477b60$@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: AQFtY8DzS5vZJbZaAyHEQlLbsO5TQ5s3zxZQ
Content-Language: en-gb
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-p2mp-framework-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Jan 2014 13:28:34 -0000

Hi Russ,

Thanks for the review.

> Question:
> 
> Should this document be an update to the MPLS-TP Framework (RFC 5921)?
> I am not sure.  RFC 5921 does make it clear that it covers only point-
> to-point transport paths.  The answer may be further complicated by
> the fact that RFC 5921 is joint work with the ITU-T.

I don't think so.
That is, it is perfectly acceptable to build a P2P MPLS-TP system and that
system could be built on protocol solutions that do not include P2MP support.

As you say, 5921 explicitly says:

   This document defines the subset of the MPLS-TP applicable in general
   and to point-to-point transport paths.  The remaining subset,
   applicable specifically to point-to-multipoint transport paths, is
   outside the scope of this document.

...so an "updates" relationship would render this statement doubtful.

I'm pretty comfortable with the documents being separate.

> Other Comments:
> 
> In the first sentence of Section 1, please define MPLS-TP as follows:
> OLD:
>    The Multiprotocol Label Switching Transport Profile is the ...
> NEW:
>    The Multiprotocol Label Switching Transport Profile (MPLS-TP) is ...

Sure.

> Please add TE-LSP to the terms defined in Section 1.2.

Sure.

> In Section 5.1, I cannot understand this sentence:
> >
> >  Per [RFC6373], the definitions of P2MP, [RFC4875], and GMPLS
> >  recovery, [RFC4872] and [RFC4873], do not explicitly cover their
> >  interactions.
> >
> I think that the references are getting in the way.  I think the
> message is: "the definitions of P2MP and GMPLS recovery do not
> explicitly cover their interactions."  If I am correct, then some
> commas need to be removed.

Yes, you're right. And a minor rewrite could make this even clearer.

> The phrase "MPLS Transport Profile" appears many places, and it would
> be easier if they were replaces with "MPLS-TP" for consistency.

OK



From ron.even.tlv@gmail.com  Sun Jan  5 04:32:40 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DBA41AE3E7; Sun,  5 Jan 2014 04:32:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YviX7tnTVdf; Sun,  5 Jan 2014 04:32:38 -0800 (PST)
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 C6B171AE3E4; Sun,  5 Jan 2014 04:32:37 -0800 (PST)
Received: by mail-ee0-f48.google.com with SMTP id e49so7296692eek.21 for <multiple recipients>; Sun, 05 Jan 2014 04:32:29 -0800 (PST)
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=tbsLjjtvpKtvKwpX93zJjgzORyUjpxLVOGZXnkDnhKo=; b=1IjC70AOyXMUVxzqHi9EgMdcjGw96fegPHIov42cd4nRWFZ9AWRu+X5F7yveoLjF0i zKmdTMJ1hcRa8yxTLGPmG8JBYLAR5sI1pFZWZEU/hOIshgGEoa//n1d+wym/J5J/+7/H NT5xIDZ5XAJAl8nrplgglxRrFxVHzOSCqmGePzIhuGAWaGOHrdDOhsKWe7UfJNDAmqu1 t9RsbpszFhWj+omWu7mAJRqZqqyyoNHAA8KABU/oBdet/OShY+kzurS+AIjh7H2UoHVz 475YQr5jKR17krSAk8fFg8tdimBk/vM7FtbIIa4EMXeQPDQSYn+xSsBQLbKQ6GjbdloJ 2KQA==
X-Received: by 10.14.194.131 with SMTP id m3mr84100400een.2.1388925149359; Sun, 05 Jan 2014 04:32:29 -0800 (PST)
Received: from RoniE ([109.64.17.204]) by mx.google.com with ESMTPSA id a51sm161747789eeh.8.2014.01.05.04.32.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 05 Jan 2014 04:32:28 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-idr-extcomm-iana.all@tools.ietf.org>
Date: Sun, 5 Jan 2014 14:28:49 +0200
Message-ID: <0bb301cf0a11$b1ea5540$15beffc0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0BB4_01CF0A22.7573E890"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8KEZjLiHThTsGxQfWaz2m0UstXsA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-idr-extcomm-iana-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 05 Jan 2014 12:32:40 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0BB4_01CF0A22.7573E890
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-idr-extcomm-iana-02

Reviewer: Roni Even

Review Date:2014-1-5

IETF LC End Date: 

IESG Telechat date: 2014-1-9

 

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

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.	I assume that the text in the IANA registry will reflect that the
old registries are close and point at the ones that replace them.  I noticed
that the document was prepared in cooperation with IANA so I assume that
there will be no problems.

 


------=_NextPart_000_0BB4_01CF0A22.7573E890
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:1212841117;
	mso-list-type:hybrid;
	mso-list-template-ids:1031841726 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-idr-extcomm-iana-02<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2014&#8211;1-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: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: 2014-1-9<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 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=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>I =
assume that the text in the IANA registry will reflect that the old =
registries are close and point at the ones that replace them.&nbsp; I =
noticed that the document was prepared in cooperation with IANA so I =
assume that there will be no problems.<o:p></o:p></li></ol><p =
class=3DMsoNormal><span lang=3DHE dir=3DRTL =
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p></=
div></body></html>
------=_NextPart_000_0BB4_01CF0A22.7573E890--


From jari.arkko@piuha.net  Mon Jan  6 04:25:31 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95A1D1ADBD1 for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 04:25:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a9pJ-OIWxKrn for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 04:25:29 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 48EDF1ADBCD for <gen-art@ietf.org>; Mon,  6 Jan 2014 04:25:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 921E92CEB6; Mon,  6 Jan 2014 14:25:20 +0200 (EET)
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 FVtNJIiCeXWX; Mon,  6 Jan 2014 14:25:18 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 1470E2CC5D; Mon,  6 Jan 2014 14:25:16 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <B096F268-3F53-40DB-BC8E-4FDA10C1B2F0@ericsson.com>
Date: Mon, 6 Jan 2014 04:25:15 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <18482D7B-0115-48EF-9AB2-B29ED222C4AB@piuha.net>
References: <B096F268-3F53-40DB-BC8E-4FDA10C1B2F0@ericsson.com>
To: Wassim Haddad <wassim.haddad@ericsson.com>
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-netmod-iana-if-type.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-netmod-iana-if-type-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 06 Jan 2014 12:25:31 -0000

Thank you Wassim for your review! I have placed a no-objection position =
for this document based on your review and my quick own review.

Jari

On Dec 12, 2013, at 4:08 PM, Wassim Haddad <wassim.haddad@ericsson.com> =
wrote:

> 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-netmod-iana-if-type-09
> Reviewer:  Wassim Haddad
> Review Date: 12 Dec 2013
> IETF LC End Date: 23 Dec 2013
> IETF Telechat Date: unknown
>=20
> Summary:  This draft is ready to be published as proposed standard
>=20
> Major Issues: None
>=20
> Minor Issues: none
>=20
>=20
> Regards,
>=20
> Wassim H.
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Mon Jan  6 04:44:56 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF8571ADFA3; Mon,  6 Jan 2014 04:44:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OEbMxqrCfaal; Mon,  6 Jan 2014 04:44:55 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5951AE19D; Mon,  6 Jan 2014 04:42:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AF13D2CEB6; Mon,  6 Jan 2014 14:42:11 +0200 (EET)
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 hVs_-C9p1yMc; Mon,  6 Jan 2014 14:42:11 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D2C9B2CC5D; Mon,  6 Jan 2014 14:42:09 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <0bb301cf0a11$b1ea5540$15beffc0$@gmail.com>
Date: Mon, 6 Jan 2014 04:42:08 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F03C7242-19B2-4705-81EF-0B42E4BCE990@piuha.net>
References: <0bb301cf0a11$b1ea5540$15beffc0$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: draft-ietf-idr-extcomm-iana.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-idr-extcomm-iana-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 06 Jan 2014 12:44:57 -0000

Roni: thank you for your review of this document. The Gen-ART reviews =
are important for me to decide whether I need to look at the document in =
more detail, and often provide useful comments that the authors use to =
improve their documents.

I have placed a no-objection position for this document for the upcoming =
IESG telechat, based on your review and my own quick review. Thank you =
for writing a clear document for a set of complex registries.

> =95 I assume that the text in the IANA registry will reflect that the =
old registries are close and point at the ones that replace them.  I =
noticed that the document was prepared in cooperation with IANA so I =
assume that there will be no problems.

FWIW, even if there had not been IANA involvement earlier, IANA also =
reviews all documents as they come through approval to the IESG, so if =
there was a problem then we'd hear about it. In this case Pearl said:

> IANA OK.  Comments in tracker.
> IANA Actions - YES


Jari


From jari.arkko@piuha.net  Mon Jan  6 04:47:55 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F0FD1ADBD4 for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 04:47:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.838
X-Spam-Level: 
X-Spam-Status: No, score=-1.838 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_54=0.6, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tJy2Hyv3TUai for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 04:47:52 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF7A1AE02A for <gen-art@ietf.org>; Mon,  6 Jan 2014 04:45:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 73C892CEB6; Mon,  6 Jan 2014 14:45:37 +0200 (EET)
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 iC2aYNVZZ-IO; Mon,  6 Jan 2014 14:45:36 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id F12212CC5D; Mon,  6 Jan 2014 14:45:34 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C55DAC2@ESESSMB209.ericsson.se>
Date: Mon, 6 Jan 2014 04:45:33 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C37FC8A-46C8-4B61-A2DE-A0ED9BA3D0DB@piuha.net>
References: <7594FB04B1934943A5C02806D1A2204B1C553A63@ESESSMB209.ericsson.se> <CEBB7480.5841E%matthew.bocci@alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1C55DAC2@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1510)
Cc: "Bocci, Matthew \(Matthew\)" <matthew.bocci@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pwe3-dynamic-ms-pw.all@tools.ietf.org" <draft-ietf-pwe3-dynamic-ms-pw.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pwe3-dynamic-ms-pw-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 06 Jan 2014 12:47:55 -0000

Thanks for your review, Christer. I see that a new version has been =
posted with at least some of these edits in - thank you Matthew for =
that.

I have placed a no-obj position on this document for the upcoming IESG =
telechat.

Jari

On Nov 27, 2013, at 3:24 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:

> Hi Matthew,
>=20
> Your suggested ways to address my issues look good. I assumed that =
some of the terms were well known, but raised the issue just in case :)
>=20
> The cases where you have a different opinion (e.g. usage of roman =
numbers) are very minor editorial ones, so no reason spending time =
arguing about that :)
>=20
> Regards,
>=20
> Christer
>=20
> -----Original Message-----
> From: Bocci, Matthew (Matthew) =
[mailto:matthew.bocci@alcatel-lucent.com]=20
> Sent: 27. marraskuuta 2013 12:33
> To: Christer Holmberg; gen-art@ietf.org
> Cc: draft-ietf-pwe3-dynamic-ms-pw.all@tools.ietf.org
> Subject: Re: Gen-ART review of draft-ietf-pwe3-dynamic-ms-pw-19
>=20
> Christer
>=20
> Thank you for your review and comments. Please see below.
>=20
> Matthew
>=20
> On 24/11/2013 15:36, "Christer Holmberg" =
<christer.holmberg@ericsson.com>
> wrote:
>=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
>> =
<https://rvi.se.ericsson.net/owa/,DanaInfo=3Dmail.internal.ericsson.com,S
>> SL+=20
>> =
redir.aspx?C=3DvCr1L8PWQUqCZeSAn6cKI_Abm6K8vNAI1hJJwcnXe8VAikdG2PcMrstLsz
>> aJe
>> =
Ao7bR8W3uA2uu0.&URL=3Dhttp%3a%2f%2fwiki.tools.ietf.org%2farea%2fgen%2ftra
>> c%2
>> fwiki%2fGenArtfaq>>
>>=20
>> Document:                         draft-ietf-pwe3-dynamic-ms-pw-19
>>=20
>> Reviewer:                           Christer Holmberg
>>=20
>> Review Date:                     24 November 2013
>>=20
>> IETF LC End Date:             27 November 2013
>>=20
>> IETF Telechat Date:         N/A
>>=20
>> Summary:  The document is well written, but there are some minor=20
>> editorial nits that the authors may want to consider addressing =
before=20
>> publication.
>>=20
>> Major Issues: None
>>=20
>> Minor Issues: None
>>=20
>> Editorial nits:
>>=20
>> Abstract:
>> -----------
>>=20
>> Q_A_1:
>>=20
>> The first sentence says:
>>=20
>>   "There is a requirement for service providers to be able to extend =
the
>>      reach of pseudowires (PW) across multiple Packet Switched =
Network
>>      domains."
>>=20
>> I would suggest to replace that with the sentence you are using later=20=

>> in the Introduction:
>>=20
>>    "RFC 5254 describes the service provider requirements for =
extending
>>      the reach of pseudowires across multiple Packet Switched Network
>>      (PSN) domains."
>>=20
>> ...assuming, of course, that you are referring to the requirements in
>> 5254 :)
>>=20
>>=20
>>=20
>=20
> MB> Agreed. I=B9ll make that change.
>=20
>>=20
>> Section 1:
>> ------------
>>=20
>> Q_1_1:
>>=20
>> In the text, and in Figure 1, you use "CE" and "PE" terminology, but=20=

>> they are nowhere extended (e.g. on first occurance). In addition, =
"CE"=20
>> is not defined in the  document, and it is unclear whether the=20
>> definition exists in some other document.
>=20
> These are well known terms for L2VPNs, but I agree they should be =
expanded on first use, regardless. The terminology section states that =
the terminology from RFC5659 is used. In addition, RFC5659 references =
RFC3916 and RFC
>=20
>>=20
>> Q_1_2:
>>=20
>> Should MPLS be extended on first occurance?
>=20
> MB> It=B9s a well known term, but I will expand.
>=20
>>=20
>> Q_1_3:
>>=20
>> Should there be a reference to MPLS?
>=20
> MB> I don=B9t think so. MPLS is well known and isn=B9t even referenced =
from
> RFC5659 and RFC3916 (the MS-PW and PW architectures).
>=20
>=20
>>=20
>> Q_1_4:
>>=20
>> There is text saying  "Attachment Identifier (AII)" and later in the=20=

>> document (section 3.2)  "Attachment Identifier (AI)". Please make =
sure=20
>> that both "AII" and  "AI" are correctly extended (e.g. on first=20
>> occurance).
>=20
> MB> Agreed. AII should read =8CAttachment Individual Identifier=B9. =
I=B9ll
> double check these throughout.
>=20
>>=20
>>=20
>> Section 2:
>> ------------
>>=20
>> Q_2_1:
>>=20
>> I suggest to say "This document describes..." rather than "In this=20
>> document we describe...".
>=20
> MB> Agreed
>=20
>>=20
>>=20
>> Q_2_2:
>>=20
>> Should "LDP" and/or "TLV" be extended on first occurance?
>=20
> MB> I will expand LDP, but =8CTLV=B9 is so well known that it is used =
in=20
> MB> most
> RFCs without expansion.
>=20
>>=20
>> Section 4:
>> ------------
>>=20
>> Q_4_1:
>>=20
>> Should there be a reference for "Target Attachment Individual=20
>> Identifier (TAII)"?
>=20
>=20
> MB> this is the =3Dsame as for SAII (RFC5003). I=B9ll add a cross =
reference
> where it is first used.
>=20
>>=20
>> Q_4_2:
>>=20
>> I would suggest to not use roman numbers in the bullet list in 4.2.3.=20=

>> It will become unclear if you need to reference (in a document, or
>> elsewhere) a specific
>> bullet in the list.
>=20
> MB> Why is this any worse than any other method e.g. a,b,c=8A or =
1,2,3...?
> Wouldn=B9t you just say Section 4.2.3, Bullet (ii) ?
>=20
>=20
>>=20
>> Section 5.1:
>> --------------
>>=20
>> Q_5_1:
>>=20
>> I think it would be useful to have a reference, and perhaps an =
example,=20
>> or what is meant by "PSN mechanisms".
>=20
> MB> I can add an example of this e.g. MPLS Fast Reroute.
>=20
>>=20
>> Q_5_2:
>>=20
>> See Q_4_2 regarding usage of roman numbers.
>>=20
>>=20
>> Section 6:
>> ------------
>>=20
>> Q_6_1:
>>=20
>> There is a sentence saying:
>>=20
>>    "However, note that the length MUST be set to 14."
>>=20
>> As the sentence contains a MUST, I would suggest to make the sentence=20=

>> more stronger, and remove "note". Perhaps simply something like:
>>=20
>>   "The length value MUST be set to 14."
>=20
> MB> OK
>=20
>>=20
>> Section 7:
>> ------------
>>=20
>> Q_7_1:
>>=20
>> The text indicates that the existing protocols may have security=20
>> issues, but that they are not affected by this document. When I read=20=

>> it, it sounds like you are not very sure whether  there are security=20=

>> issues, but you still know that they are not affected
>> :)
>>=20
>> I would suggest to re-word the second sentence to something like:
>>=20
>>   "The extensions defined in this document do not affect the security=20=

>> issues associated with those protocols."
>=20
> MB> Agreed, but perhaps =B9security considerations=B9 rather than =
=B9security
> issues=B9 would be more accurate.
>=20
>>=20
>>=20
>> Section 8:
>> ------------
>>=20
>> Q_8_1:
>>=20
>> In section 8.1, s/"IANA needs to"/"IANA is requested to"
>=20
> MB> OK
>=20
>>=20
>> Q_8_2:
>>=20
>> In section 8.2, s/"The IANA is requested to"/"IANA is requested to"
>=20
> MB> OK
>=20
>>=20
>>=20
>> Section 10:
>> --------------
>>=20
>> Q_10_1:
>>=20
>> I would suggest to move the paragraph to the beginning of section 11.
>> Something like:
>>=20
>>   "11. Acknowledgements
>>=20
>>      The editors gratefully acknowledge the following additional co-
>>      authors of this document:  Mustapha Aissaoui, Nabil Bitar, Mike=20=

>> Loomis, David McDysan,
>>      Chris Metz, Andy Malis, Jason Rusmeisel, Himanshu Shah, Jeff
>>      Sugimoto.
>>=20
>>      The editors also gratefully acknowledge the input of the =
following
>>      people:  Mike Duckett, Paul Doolan, Prayson Pate, Ping Pan, =
Vasile
>>      Radoaca, Yeongil Seo, Yetik Serbest, Yuichiro Wada."
>=20
>=20
> MB> The intent was to explicitly and clearly call out people who
> contributed text but were too numerous to list at the top of the =
draft.
> I=B9d therefore rather keep these in a separate section.
>=20
>=20
>>=20
>>=20
>> Regards,
>>=20
>> Christer
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Mon Jan  6 04:52:14 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CDAF1ADBD4 for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 04:52:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u4vnStronAdw for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 04:52:12 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 92B921ADEA0 for <gen-art@ietf.org>; Mon,  6 Jan 2014 04:52:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E4E822CEB6; Mon,  6 Jan 2014 14:52:01 +0200 (EET)
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 cvCjdCZ9L9Yo; Mon,  6 Jan 2014 14:52:00 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 003D32CC5D; Mon,  6 Jan 2014 14:51:58 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAF4+nEHCjPs5AYQZy616rV8gpsRe1gQwbqBwSN6JPtwsYw+FLQ@mail.gmail.com>
Date: Mon, 6 Jan 2014 04:51:57 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <1CCDF17C-FE69-4CCB-9A8A-1E192C26BE90@piuha.net>
References: <1387836011.24761.1524.camel@mightyatom> <CAF4+nEHCjPs5AYQZy616rV8gpsRe1gQwbqBwSN6JPtwsYw+FLQ@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-trill-rfc6327bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art Yuletide LC review of draft-ietf-trill-rfc6327bis-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 06 Jan 2014 12:52:14 -0000

Thanks for your review, Elwyn, and Donald for your response and new =
version. I have placed a no-obj position for this document for the =
upcoming IESG telechat.

Jari

On Dec 24, 2013, at 10:34 AM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> Hi Elwyn,
>=20
> Seasons Greetings!
>=20
> On Mon, Dec 23, 2013 at 5:00 PM, Elwyn Davies <elwynd@dial.pipex.com>
> wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>=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-trill-rfc6327bis-02.txt
>> Reviewer: Elwyn Davies
>> Review Date: 23 December 2013
>> IETF LC End Date: 23 December 2012
>> IESG Telechat date: (if known) -
>>=20
>> Summary:
>> Almost ready for the IESG.  There is one minor issue that seems as
>> if it needs a better way to explain how the defense against rogue
>> native packets is supposed to work and a number of nits.  Apologies
>=20
> It=92s not actually defense =93against rogue native packets=94 but =
defense
> against a native packet being multiply ingressed or egressed...
>=20
>> if the festive spirit got the better of a few comments.
>=20
> No apologies needed...
>=20
>> Major issues:
>> None.
>=20
>  Thanks.
>=20
>> Minor issues:
>> s2.2, last para:
>>>   The primary TRILL defense mechanism against such loops, which is
>>>   mandatory, is to assure that, as far as practically possible,
>>>   there is only a single RBridge that is in charge of ingressing
>>>   and egressing native frames...
>> This seems to be difficult to implement: Implementing some defense
>> mechanism is stated to be mandatory but the proposed defense is at
>> best, best efforts.  It strikes me that given the expected
>> catastrophic results of failure to have a robust defense, as
>> delineated in the previous para, indicates that this either needs
>> some better explanation or possibly a better defense.  I can't tell,
>> but I guess we may be talking about some extraneous measure beyond
>> this spec - please explain.
>=20
>  The mandatory mechanism is explained in greatest detail in RFC
>  6439. Perhaps the references to that RFC should be stronger and
>  clearer. (It requires very peculiar and unlikely events for there to
>  be a problem and, while such a problem will be bad, it will be
>  transient - cleared up as soon as Hellos are exchanged on the link.)
>=20
>=20
>> Nits/editorial comments:
>> General: Adding titles/caption to figures and tables would be =
helpful.
>=20
>  OK.
>=20
>=20
>> General: s/byte/octet/
>=20
>  I would agree that it is important for this to be consistent within
>  the document. There seem to currently be 2 occurrences of "octet"
>  and 12+ occurrences of "byte". Also, "byte" seems to be the preferred
>  term for IS-IS TLV sub-field diagrams. So, I would prefer to change
>  the two occurrences of "octet" to "byte".
>=20
>=20
>> Abstract: s/IS-IS adjacency between/IS-IS adjacencies between/
>> s1, para 1: multipathing?? horrid non-word!!  Suggest:
>> OLD:
>> support for multipathing of both unicast and multicast traffic in
>>   multi-hop networks with arbitrary topology.
>> NEW:
>> support for transmission of both unicast and multicast traffic
>> taking advantage of multiple paths in multi-hop networks with
>> arbitrary topology.
>=20
>  OK.
>=20
>=20
>> s1, para 1: 'and a header that includes a hop count': A header for
>> what?  Please make it clear what the header is added to.
>=20
>  "a header" -> "a header in TRILL data packets"
>=20
>=20
>> s1, para 1, next to last sentence: Has two 'ands'
>> Suggest s/and optimization/as well as optimization/
>=20
>  OK.
>=20
>=20
>> s1, table: Probably worth expanding BFD again (even though it is
>> in the abstract and terminology).
>=20
>  OK.
>=20
>=20
>> s1: Definition and explanation of 'pseudonode': There is no
>> explanation of the pseudonode term until s7 - and even there it is
>> buried a couple of paras down in the text.  A definition/explanation
>> either in s1 or s1.2 would be helpful.
>=20
>  "pseudonode" is a fundamental concept of IS-IS and I'm really not
>  sure that it should be the role of this draft to explain it. I can
>  add a reference to ISO 10589 after the first occurrence of
>  "pseudonode" in Section 1.
>=20
>=20
>> s2.1, para 1, sentence 2: This sentence is difficult to parse: After
>> two or three reads, I realized that the material starting at
>> 'devices or services' is not part of the 'includes' and ceased
>> looking for an 'and'.  Suggest reversing the components of the main
>> body thus:
>> OLD:
>>   Because this includes general bridged LANs
>>   [802.1Q], devices or services that can restrict VLAN connectivity,
>>   such as [802.1Q] bridges or carrier Ethernet services, can be part =
of
>>   a link between RBridges.
>> NEW:
>>   Because this includes general bridged LANs
>>   [802.1Q], the links between RBridges may contain devices or =
services that
>>   can restrict VLAN connectivity, such as [802.1Q] bridges or carrier
>>   Ethernet services.
>=20
>  OK, I think that's an improvement.
>=20
>=20
>> s2.4, para 1: s/reasonably restricted MTU/relatively restricted MTU/
>=20
>  I think it really means that the restriction of MTU is reasonable,
>  as opposed to unreasonable.
>=20
>=20
>> s3.3, Event A4: I was initially slightly confused as to how one timer
>> expiring resulted in both being expired in the broadcast case.  Maybe
>> reword a bit:
>> OLD:
>>      A4. Either (1) the Hello holding timer expires on a =
point-to-point
>>          adjacency or (2) one or both Hello holding timers expire on =
a
>>          broadcast LAN adjacency resulting in them both being in the
>>          expired state for that adjacency.
>> NEW:
>>      A4. Either (1) the Hello holding timer expires on a =
point-to-point
>>          adjacency or (2), on a broadcast LAN adjacency, both Hello =
timers
>>          expire together or, after one timer expired previously (see
>>          Event A5), the second timer expires resulting in them both =
being
>>          in the expired state for that adjacency.
>=20
>  There is yet another possibility: One timer could expire while the
>  other is still in its initial expired state so it would be incorrect
>  to speak about it having "expired previously". How about the
>  following:
>=20
> NEWER:
>=20
>    A4. Either (1) the Hello holding timer expires on a point-to-point
>        adjacency or (2), on a broadcast LAN adjacency, (2a) both
>        Hello timers expire simultaneously or (2b) one Hello timer
>        expires when the other Hello timer is already in the expired
>        state.
>=20
>=20
>> s5, para 3: Although it isn't wrong, given that RFC 2119 language is
>> called out in s1.2, it might be better to explicitly use MUST
>> instead of mandatory here.  MUST could also be used about the 1,470
>> bytes (octets) minimum in para 2
>=20
>  I don't particularly like using "MUST" here. The RFC 2119 MUSTs are
>  in the TRILL base protocol specification, RFC 6325.
>=20
>=20
>> s5, para 5: s/If it tests MTU/If it tests the MTU size/
>=20
>  OK.
>=20
>=20
>> s6, (not the) definition of BFD Enabled TLV: The figure shows a
>> fixed value of 3 for the Length field and exactly one topology entry
>> (2 octets) and a Protocol ID (1 octet).  The text indicates that
>> there could be several, it isn't specific as to whether there has to
>> be a match between topology and protocol entries but the length sort
>> of indicates that there might be.  Frankly this is a mess (probably
>> due to not being the definition of the TLV which isn't totally
>> obvious).
>=20
>  The BFD enabled TLV is specified in RFC 6213 that is referenced
>  elsewhere in this draft but, curiously, not in Section 6. A
>  reference should be added there.
>=20
>> So if multiple topology and protocol entries are present:
>> - must there be a matching number of them (the length text sort of
>> implies this)?
>=20
>  Yes. The text should clarify this.
>=20
>> - do they go in matched pairs: (topology, proto), (topology, proto), =
etc or
>>  all topologies first and then all protocols?
>=20
>    Matched pairs.
>=20
>> - Where topology ID's come from?
>=20
>    A few are pre-assigned but mostly they are made up by the
>    network's management. See RFC 5120 that should probably be
>    referenced here.
>=20
>> - Where do NLPIDs come from?
>=20
>    =46rom ISO/IEC (see ISO9577), but there is a range available to
>    other organizations, including the IETF. See RFC 6328 that is
>    referenced here in the draft.
>=20
>> All of this can probably be done by citing the right reference as I
>> eventually realized.
>=20
>=20
>> s7, para 3:
>>> It is anticipated that many links between RBridges will actually be
>>>   point-to-point, in which case using a pseudonode merely adds to =
the
>>>   complexity.
>> Does this actually mean they actually be point-to-point even though =
they are
>> on and using a broadcast LAN TRILL setup?   If so this should be =
clarified.
>=20
>  How about replacing "... will actually be point-to-point, ..." with
>  "... will actually be point-to-point even if the link technology
>  supports operation as a multi-access broadcast link, ...".
>=20
>=20
>> s8.2.1, para 1: s/should not be included/SHOULD NOT be included/
>=20
>  OK.
>=20
>=20
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> 155 Beaver Street, Milford, MA 01757 USA
> d3e3e3@gmail.com
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From alexey.melnikov@isode.com  Mon Jan  6 07:48:31 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 189A51AE04A for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 07:48:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ac56oqn_9k27 for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 07:48:29 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 1A9871AE038 for <gen-art@ietf.org>; Mon,  6 Jan 2014 07:48:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1389023299; d=isode.com; s=selector; i=@isode.com; bh=UXmb64TbhjeIssVaGz3264zJ+sYGXv+D3xgblLNxXgg=; 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=HH4/dKJoO/ATWdBnZFBYJ4yd4fAjNLX6ChyXB08o7uW6HFXZol8n4Tit3QIMdpQ7seWVLe ni4kL0cyNzKK8MWWQsv2zF6WnPZ6yiM/BBHI3QKHXd9HwkbH3mYcxUogT4aNaOBBN1HKME wkBgmZvpfwf9D4N3OPi4rNENEZTQuws=;
Received: from [172.17.128.75] (richard.isode.com [62.3.217.249])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <UsrQQwBvgSff@statler.isode.com>; Mon, 6 Jan 2014 15:48:19 +0000
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <52CAD041.5060106@isode.com>
Date: Mon, 06 Jan 2014 15:48:17 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: draft-ietf-savi-send.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
Subject: [Gen-art] Gen-ART review of draft-ietf-savi-send-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 06 Jan 2014 15:48:31 -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-savi-send-10
Reviewer: Alexey Melnikov
Review Date: 2014-01-06
IETF LC End Date: 2013-12-23
IESG Telechat date: 2014-01-09


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

Major issues: None

Minor issues: None

Nits/editorial comments: There were a couple of minor editorial issues 
like an extra "to" or a misplaced "for", but I think RFC Editor will fix 
these for you.



From martin.thomson@gmail.com  Mon Jan  6 10:44:32 2014
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 344601AE17A for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 10:44:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YzizODX73R9J for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 10:44:30 -0800 (PST)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 0843D1AE15B for <gen-art@ietf.org>; Mon,  6 Jan 2014 10:44:29 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id z2so3193186wiv.1 for <gen-art@ietf.org>; Mon, 06 Jan 2014 10:44:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=OmZK9BsgJsncy69fHrUuCvl3q8i4p0MPE5Cx8YyJAtY=; b=xpOQ5Ik7iapla5Qk0x/b9fpmN1zEWqsYeQxpqULoObtFS1rLyqBk+Lg9ZUZ2Dje4nx 1ZF31wZyK7FdJKi1Gh21fswAGvCik78HnqCDk5mQFCcJGDbjiGJmLr9CNJ9B6fq4FUNR 7rqEdazb61kPX9JQcgg18iuk+DkvoB75Jr1oPqo+giukSpn0IdBxAJXwKSvju66n9H73 zsttwsw4WFaw9MCgfBmjBaWeMhva2l5aiMwHaMozPWEvt+1Da/mQk8sJIKUalbD6GksP ioI9HopqgOGrxGGf2vZK4frupgkRBt/dW9wL/4ELSER4CPgtqLXaiCiMHbrxmMkl6DNV eP3A==
MIME-Version: 1.0
X-Received: by 10.180.188.175 with SMTP id gb15mr13524873wic.50.1389033861049;  Mon, 06 Jan 2014 10:44:21 -0800 (PST)
Received: by 10.227.134.195 with HTTP; Mon, 6 Jan 2014 10:44:20 -0800 (PST)
Date: Mon, 6 Jan 2014 10:44:20 -0800
Message-ID: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 06 Jan 2014 18:44:32 -0000

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

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

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

Document: draft-ietf-opsawg-lsn-deployment-04
Reviewer: Martin Thomson
Review Date: 2014-01-06
IETF LC End Date: 2014-01-06
IESG Telechat date: (if known)

Summary:  This document describes a generic way that MPLS LSPs can be
deployed to support the deployment of CGNs in a way that addresses a
range of common requirements.  As a draft, it's still a little rough,
but it is mostly ready for publication as an Informational RFC.

Major issues: none

Minor issues:

The abstract says this:

  This document does not intend to defend the
   merits of CGN.

Which seems wise given their somewhat contentious nature.  But then
the entirely of Section 2 does exactly the opposite.  I don't know
what the right answer is here, but maybe the right thing to do is
delete Section 2.

Figures 1 and 2 should probably use different labels for the two CPE
boxes.  The top one is being translated, the bottom one isn't.

Section 6 is a little too speculative to be valuable.  How about using
the boilerplate:

      This document has no IANA actions.

I'm not sure what "security measures" might be employed here:

   If a provider plans to operate the pre-translation realm (CPE towards
   translator IPv4 zone) as a non-public like network, then additional
   security measures may be needed to secure this environment.

What might be secured in these scenarios?  Confidentiality?  Access to
network resources?  Perhaps this should talk about what a network
operator wants to secure: access to the network.  Then maybe talk
about access control and isolation.

In Section 4, this seems a little vague:

   Various redundancy models
   can be used within this architecture to support failover from one
   physical CGN hardware instance to another.

I don't expect an enumeration of the options, but this seems important
enough to at least point to where the redundancy options might exist?
Redundant "VPNs"/LSPs?  Redundant paths from the VRF termination?

Nits:

Missing period in Section 9

I found the structure of the first part of Section 3.1 difficult:

   Centralized deployments of CGN (longer proximity to end user and/or
   higher densities of subscribers/connections to CGN instances) differ
   from distributed deployments of CGN (closer proximity to end user and
   /or lower densities of subscribers/connections to CGN instances).

Maybe this could be expanded a little to improve comprehension.

This statement seems redundant:

   Other requirements may be assessed on a operator-by-operator basis,
   but those listed above may be considered for any given deployment
   architecture.

As far as it goes, some of the requirements listed might not apply to
a particular deployment, or part thereof.

From ben@nostrum.com  Mon Jan  6 14:01:06 2014
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB8F1AE27E for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 14:01:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id svOjCqhHfLKi for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 14:01:05 -0800 (PST)
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 336C91AE1C1 for <gen-art@ietf.org>; Mon,  6 Jan 2014 14:01:05 -0800 (PST)
Received: from [172.20.10.7] (mobile-166-147-070-187.mycingular.net [166.147.70.187]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s06M0rJs044964 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Jan 2014 16:00:56 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 6 Jan 2014 16:00:47 -0600
Message-Id: <4521C493-D819-406E-B2B0-F45BAD760C08@nostrum.com>
To: draft-ietf-avtcore-leap-second.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
X-Mailer: Apple Mail (2.1827)
Received-SPF: pass (shaman.nostrum.com: 166.147.70.187 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Telechat Review of draft-ietf-avtcore-leap-second-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 06 Jan 2014 22:01:06 -0000

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

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

Document: draft-ietf-avtcore-leap-second-07
Reviewer: Ben Campbell=09
Review Date: 2014-01-06
IESG Telechat date: 2014-01-09

Summary: This draft is ready for publication as a proposed standard. All =
comments from my previous review of version 06 have been addressed.

Major issues: None

Minor issues: None

Nits/editorial comments: None

From elwynd@dial.pipex.com  Mon Jan  6 14:28:25 2014
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 145941AE296 for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 14:28:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ok_tZkeVHN8z for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 14:28:22 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id EA7861AE293 for <gen-art@ietf.org>; Mon,  6 Jan 2014 14:28:21 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1W0IeW-0002yO-5d; Mon, 06 Jan 2014 22:28:10 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Mon, 06 Jan 2014 22:28:05 +0000
Message-Id: <1389047285.24761.1599.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -1.0
Cc: draft-ietf-trill-rfc6327bis.all@tools.ietf.org
Subject: [Gen-art] Gen-art telechat review of draft-ietf-trill-rfc6327bis-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 06 Jan 2014 22:28:25 -0000

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

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

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

Document: draft-ietf-trill-rfc6327bis-03.txt
Reviewer: Elwyn Davies
Review Date: 6 January 2014
IETF LC End Date: 23 December 2012
IESG Telechat date: (if known) -9 January 2014

Summary:
Ready.  Thanks to Donald for the updates after the LC review.

Major issues:
None.

Minor issues:
None

Nits/editorial comments:

s8.2.1, para 1: s/include/included/  (was in the LC comments ;-) )





From lberger@labn.net  Mon Jan  6 15:41:46 2014
Return-Path: <lberger@labn.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 746D81AE339 for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 15:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lGeaPcR44aNS for <gen-art@ietfa.amsl.com>; Mon,  6 Jan 2014 15:41:45 -0800 (PST)
Received: from alt-proxy6.mail.unifiedlayer.com (alt-proxy6.mail.unifiedlayer.com [66.147.245.65]) by ietfa.amsl.com (Postfix) with SMTP id CA53A1AE332 for <gen-art@ietf.org>; Mon,  6 Jan 2014 15:41:44 -0800 (PST)
Received: (qmail 5369 invoked by uid 0); 6 Jan 2014 23:41:31 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy14.mail.unifiedlayer.com with SMTP; 6 Jan 2014 23:41:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=gldf/3zDjkEqfBdH3uqlpAPdalGbeReDJ4MuxV4YwVI=;  b=T7MD4OR1TxyFEJjgXWw/Nj+9TRDYWssJRhqQOjgxcbS9J/EMPrumHQFcwibQkQAWo8OfH3v2dozgjlA7pHSW66yBIeiEEqihasv/IvGlei+nHr/UFEAkPQZZL43Y5iL0;
Received: from box313.bluehost.com ([69.89.31.113]:49702 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1W0JnW-0002te-QD; Mon, 06 Jan 2014 16:41:30 -0700
Message-ID: <52CB3F28.4070100@labn.net>
Date: Mon, 06 Jan 2014 18:41:28 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, 'Russ Housley' <housley@vigilsec.com>,  draft-ietf-mpls-tp-p2mp-framework.all@tools.ietf.org
References: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com> <008d01cf0950$d86d2920$89477b60$@olddog.co.uk>
In-Reply-To: <008d01cf0950$d86d2920$89477b60$@olddog.co.uk>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-p2mp-framework-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 06 Jan 2014 23:41:46 -0000

Russ/Adrian,

A couple of editorial points:

On 1/4/2014 8:28 AM, Adrian Farrel wrote:
> Hi Russ,
> 
> Thanks for the review.

Agreed!

> 
...

> 
>> Other Comments:
>>
>> In the first sentence of Section 1, please define MPLS-TP as follows:
>> OLD:
>>    The Multiprotocol Label Switching Transport Profile is the ...
>> NEW:
>>    The Multiprotocol Label Switching Transport Profile (MPLS-TP) is ...
> 
> Sure.
> 
>> Please add TE-LSP to the terms defined in Section 1.2.
> 
> Sure.
Actually, this is a good catch as it really should say: "Traffic
Engineered P2MP LSP" and "Traffic Engineered multipoint-to-multipoint LSPs".

> 
>> In Section 5.1, I cannot understand this sentence:
>>>
>>>  Per [RFC6373], the definitions of P2MP, [RFC4875], and GMPLS
>>>  recovery, [RFC4872] and [RFC4873], do not explicitly cover their
>>>  interactions.
>>>
>> I think that the references are getting in the way.  I think the
>> message is: "the definitions of P2MP and GMPLS recovery do not
>> explicitly cover their interactions."  If I am correct, then some
>> commas need to be removed.
> 
> Yes, you're right. And a minor rewrite could make this even clearer.
> 

How about:
[RFC6373] notes that recovery techniques for Traffic Engineered P2MP
LSPs are not formally defined, and such that a definition is needed.   A
formal definition will be based on existing RFCs and may not require any
new protocol mechanisms but, nonetheless, should be documented. GMPLS
recovery is defined in [RFC4872] and [RFC4873]. Protection of P2MP LSPs
is also discussed in [RFC6372] Section 4.7.3.

>> The phrase "MPLS Transport Profile" appears many places, and it would
>> be easier if they were replaces with "MPLS-TP" for consistency.
> 

Sure.

> OK

We'll have a version ready to go soon and will coordinate with Adrian on
publication.

Thanks again,
Lou


From christer.holmberg@ericsson.com  Tue Jan  7 01:16:15 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A6661ADFB2 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 01:16:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level: 
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oUSzASvv_0-D for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 01:16:14 -0800 (PST)
Received: from sesbmg21.mgmt.ericsson.se (sesbmg21.ericsson.net [193.180.251.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4221ADF53 for <gen-art@ietf.org>; Tue,  7 Jan 2014 01:16:13 -0800 (PST)
X-AuditID: c1b4fb31-b7fa78e0000005dd-24-52cbc5d430b6
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id CD.31.01501.4D5CBC25; Tue,  7 Jan 2014 10:16:04 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.201]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0347.000; Tue, 7 Jan 2014 10:15:30 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Gen-ART review of draft-ietf-ospf-manet-single-hop-or-04
Thread-Index: Ac8LiIzNbs9cNIexQrSc9KbEv9W2CQ==
Date: Tue, 7 Jan 2014 09:15:29 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C5EEB9D@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsUyM+Jvre6Vo6eDDHp3ylqsfPiM0eLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfGtyUr2QsOsVZ8ObSBpYFxB0sXIweHhICJ xOfFYV2MnECmmMSFe+vZuhi5OIQETjBKtO85wgzhLGaUuNo9lw2kgU3AQqL7nzZIg4iApsTc FW+ZQGxmgXKJA2tvMoPYwgLeEjdXHGcCKRcRCJK4MDMRwtSTeHUtBaSCRUBF4tW/eawgNq+A r0TzmXtgUxiBTvh+ag3URHGJW0/mM0GcJiCxZM95ZghbVOLl43+sELaixNXpy6HqdSQW7P7E BmFrSyxb+JoZYr6gxMmZT1gmMIrMQjJ2FpKWWUhaZiFpWcDIsopRsji1OCk33chQLzc9t0Qv tSgzubg4P0+vOHUTIzAiDm75bbiDceI1+0OM0hwsSuK8DNM7g4QE0hNLUrNTUwtSi+KLSnNS iw8xMnFwSjUw9umcSD/KoJ3Q+OL/Mecfb07ZME34WfivoGeVh94hpZOfhP6YOZy9q3jG5t2C vTsezAy1OxvFF8XucrjEdUuRv83amEcT/DUDNY48la7w99gbrn3smtF3o/drNFrvBx7Ypabe edX8E/Pzu+qMKbbrXJi1XeQ39sTeVJo03/pGle5D175Apx01SizFGYmGWsxFxYkANG8kC1YC AAA=
Cc: "draft-ietf-ospf-manet-single-hop-or.all@tools.ietf.org" <draft-ietf-ospf-manet-single-hop-or.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of	draft-ietf-ospf-manet-single-hop-or-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 09:16:15 -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-ospf-manet-single-hop-or-04.txt
Reviewer: 		Christer Holmberg
Review Date: 		7 January 2014
IETF LC End Date:	17 December 2013
IESG Telechat date: 	9 January 2014=20

Summary:	My issue on the previously reviewed version of the document has be=
en addressed, and the document is now ready for publication.

Major issues: -

Minor issues: -

Nits/editorial comments: -

Regards,

Christer

From christer.holmberg@ericsson.com  Tue Jan  7 01:20:52 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E88741AE04E for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 01:20:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level: 
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4LHKEiyorNfd for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 01:20:51 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 8FACA1AE01B for <gen-art@ietf.org>; Tue,  7 Jan 2014 01:20:50 -0800 (PST)
X-AuditID: c1b4fb25-b7eff8e000000eda-9c-52cbc6e9b610
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 77.52.03802.9E6CBC25; Tue,  7 Jan 2014 10:20:41 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.201]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.02.0347.000; Tue, 7 Jan 2014 10:20:06 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-trill-o-pw-04
Thread-Index: Ac8LiUOcZKAhaAqCR9mhbkwlpLQJuQ==
Date: Tue, 7 Jan 2014 09:20:06 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C5EEBB1@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C5EEBB1ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+Jvre7LY6eDDHYcFrRoXP6E0eLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfG+ca8gla9iosP1jI2MLZrdDFycEgImEhM P1zSxcgJZIpJXLi3nq2LkYtDSOAQo8SLyccYIZzFjBJrP/WygDSwCVhIdP/TBmkQEdCUmLvi LROIzSwQLbF1XwcriC0sYCwx8fZMNogaC4mLLbuZIGw9ibuvroONYRFQkTgwJQUkzCvgKzHj /hcWEJsR6Ibvp9ZAjRSXuPVkPhPEbQISS/acZ4awRSVePv7HCmErSlydvhyqPl+i//MsdoiZ ghInZz5hmcAoPAvJqFlIymYhKYOI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGNlzEzNz 0suNNjECo+Pglt+qOxjvnBM5xCjNwaIkzvvhrXOQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6p BsbJX3/4m2o57Vg/g/fm694fnutruEUOV75bIhOs8OKYjlTQtlmPA1n/5vfzv/j/pKo8sNjn 0M6Ux6Ibd9zLb2rU4Tm8xGqmk7VRw6EjQl/OFAR5Oit++v1B/cPvI3nL3718cj/L3/nOmQlN /nLJS1wFXhXeZznI/ss3NebJrPCTkhW3eiwN8l4rsRRnJBpqMRcVJwIAZCwbflwCAAA=
Cc: "draft-ietf-trill-o-pw.all@tools.ietf.org" <draft-ietf-trill-o-pw.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-trill-o-pw-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 09:20:53 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1C5EEBB1ESESSMB209erics_
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-trill-o-pw-04.txt

Reviewer:                           Christer Holmberg

Review Date:                     7 January 2014

IETF LC End Date:             23 December 2013

IESG Telechat date:         9 January 2014



Summary:           My issue on the previously reviewed version of the docum=
ent has been addressed, and the document is now ready for publication.



Major issues: -



Minor issues: -



Nits/editorial comments: -



Regards,



Christer


--_000_7594FB04B1934943A5C02806D1A2204B1C5EEBB1ESESSMB209erics_
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: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;}
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";}
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.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
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-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-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; http://wiki.tools.i=
etf.org/area/gen/trac/wiki/GenArtfaq&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: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; draft-ietf-trill-o-pw-04.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Christer Holmberg<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7=
 January 2014<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 23 December 2013<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; 9 January 2014 <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; My issue on the previously reviewed version of the docu=
ment has been addressed, and the document is now ready for publication.<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"><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>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1C5EEBB1ESESSMB209erics_--

From christer.holmberg@ericsson.com  Tue Jan  7 01:26:58 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18AB81ADFB7 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 01:26:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level: 
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fVStMer8Tbep for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 01:26:57 -0800 (PST)
Received: from sessmg21.mgmt.ericsson.se (sessmg21.ericsson.net [193.180.251.40]) by ietfa.amsl.com (Postfix) with ESMTP id C11001ADEC8 for <gen-art@ietf.org>; Tue,  7 Jan 2014 01:26:56 -0800 (PST)
X-AuditID: c1b4fb28-b7f318e00000037c-95-52cbc857b974
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.125]) by sessmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 0A.A9.00892.758CBC25; Tue,  7 Jan 2014 10:26:47 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.201]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0347.000; Tue, 7 Jan 2014 10:26:12 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-pwe3-dynamic-ms-pw-20
Thread-Index: Ac8LikWecuraxMJaR5+luSbb/vRq6Q==
Date: Tue, 7 Jan 2014 09:26:12 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C5EEBF0@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsUyM+JvrW74idNBBh2LpC3OnPjHZnH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugStj3dpTbAWT2SqWz01oYNzC0sXIySEhYCLx bNVMVghbTOLCvfVsXYxcHEICJxgllnXfYIdwFjNK7Dl9HaiKg4NNwEKi+582SIOIgKbE3BVv mUBsZoFsib43S8EGCQtYS2w8eJQRosZBYt/61VC2nsTHE4vBFrMIqADZE5lBbF4BX4kVf7eD zWEEOuL7qTVQM8Ulbj2ZzwRxnIDEkj3nmSFsUYmXj/9BHa0ocXX6cqh6HYkFuz+xQdjaEssW voaaLyhxcuYTlgmMIrOQjJ2FpGUWkpZZSFoWMLKsYpQsTi0uzk03MtTLTc8t0UstykwuLs7P 0ytO3cQIjIqDW35r7GDsvmZ/iFGag0VJnLdqZmeQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6p Bkbj7HXFpq75VezqeguVS35lq6cdSP6wepejrpu+xvedeyRtne/XZ/xI3v2isNeFeU1ta3rF h+UbFz3bMmEfo2ezmSpjtdXX9oLguIdlfKuTubq2uwQW7dS4NsOkT0/ni+2fWXppb5btjhBq Vpm613tyYl5D1tbQ9TtKvHWzPPfwRfqpXxBaqsRSnJFoqMVcVJwIAMWDQWtYAgAA
Cc: "draft-ietf-pwe3-dynamic-ms-pw.all@tools.ietf.org" <draft-ietf-pwe3-dynamic-ms-pw.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-pwe3-dynamic-ms-pw-20
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 09:26:58 -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-pwe3-dynamic-ms-pw-20.txt
Reviewer:                        Christer Holmberg
Review Date:                   7 January 2014
IETF LC End Date:            27 November 2013
IESG Telechat date:         9 January 2014=20

Summary:           My issues on the previously reviewed version of the docu=
ment have been addressed, and the document is now ready for publication.

Major issues: -

Minor issues: -

Nits/editorial comments: -

Regards,

Christer

From agmalis@gmail.com  Tue Jan  7 05:01:26 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1ED11ADEA0 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 05:01:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rFaAH0O9rN6I for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 05:01:25 -0800 (PST)
Received: from mail-qe0-x22b.google.com (mail-qe0-x22b.google.com [IPv6:2607:f8b0:400d:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 95FCE1ADBD4 for <gen-art@ietf.org>; Tue,  7 Jan 2014 05:01:25 -0800 (PST)
Received: by mail-qe0-f43.google.com with SMTP id jy17so296975qeb.30 for <gen-art@ietf.org>; Tue, 07 Jan 2014 05:01:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=EIp/yErt2RMvPAAKhffR4f4ZCOTOi33bUyCe5VkNC1Q=; b=MgdpSC0Hm7+Ij17veeugJj1eFP6x/aDU5iCyM3uoH4sZCAJiPec6dkaOt2OMMbNNCe 5LUrkcghVJWU3gPAzfVwZ1YU2pKMXVemYBQLYntLhCQblUZV02ACQyYF5qH5fX4M1Sc7 cU+IyCj71z9AFvuf6O9hbwh5uloARBPqZ7nrRxWhy0foAE3YB7elmCqo3GA+hLr7SrYf WumcoSWbbMGf6yqqGS/lgHWN7dez4kaAZ7PiXoreiw4qxaCgcaHI4MW2LQUC/KFPaZvM RZSuTmpxeKM8LRZ3NxohHRSeRrB8AGlb2z4NljTrsGCCHby2Y3nVggYazG1H2Z8JrLVp R0YA==
X-Received: by 10.49.15.227 with SMTP id a3mr198178430qed.66.1389099676529; Tue, 07 Jan 2014 05:01:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.166.9 with HTTP; Tue, 7 Jan 2014 05:00:55 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C5EEBF0@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C5EEBF0@ESESSMB209.ericsson.se>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 7 Jan 2014 08:00:55 -0500
Message-ID: <CAA=duU3VBF2Tvx0_Ew3s2vHX7MPaQiXDR7GnYXH8jZ+pDia3vA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pwe3-dynamic-ms-pw.all@tools.ietf.org" <draft-ietf-pwe3-dynamic-ms-pw.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pwe3-dynamic-ms-pw-20
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 13:01:27 -0000

Christer,

Thanks for the update!

Cheers,
Andy

On Tue, Jan 7, 2014 at 4:26 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>.
>
> Please wait for direction from your document shepherd or AD before posting a new version of the draft.
>
> Document:                       draft-ietf-pwe3-dynamic-ms-pw-20.txt
> Reviewer:                        Christer Holmberg
> Review Date:                   7 January 2014
> IETF LC End Date:            27 November 2013
> IESG Telechat date:         9 January 2014
>
> Summary:           My issues on the previously reviewed version of the document have been addressed, and the document is now ready for publication.
>
> Major issues: -
>
> Minor issues: -
>
> Nits/editorial comments: -
>
> Regards,
>
> Christer

From jari.arkko@piuha.net  Tue Jan  7 12:44:03 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C1281AE1A2 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:44:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RKDHTZ3-ldy0 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:44:00 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0021AE19E for <gen-art@ietf.org>; Tue,  7 Jan 2014 12:44:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6BC992CC61; Tue,  7 Jan 2014 22:43:50 +0200 (EET)
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 8yIoT5E-Wmpn; Tue,  7 Jan 2014 22:43:49 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 344E22CC5D; Tue,  7 Jan 2014 22:43:47 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52CAD041.5060106@isode.com>
Date: Tue, 7 Jan 2014 12:43:46 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <DAF1DB6A-592D-4FF9-B62B-241D500D1B9B@piuha.net>
References: <52CAD041.5060106@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1510)
Cc: draft-ietf-savi-send.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-savi-send-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 20:44:03 -0000

Thanks for your review, Alexey!

Jari

On Jan 6, 2014, at 7:48 AM, 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-savi-send-10
> Reviewer: Alexey Melnikov
> Review Date: 2014-01-06
> IETF LC End Date: 2013-12-23
> IESG Telechat date: 2014-01-09
>=20
>=20
> Summary: This draft is ready for publication as a standard track RFC.
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments: There were a couple of minor editorial issues =
like an extra "to" or a misplaced "for", but I think RFC Editor will fix =
these for you.
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Jan  7 12:45:26 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AEF41AE1C3 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:45:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c-RsIJ-j1vW5 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:45:25 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CE9E21AE19E for <gen-art@ietf.org>; Tue,  7 Jan 2014 12:45:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9DC342CC5D; Tue,  7 Jan 2014 22:45:15 +0200 (EET)
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 igd6EHrv3c1r; Tue,  7 Jan 2014 22:45:13 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7FE212CC48; Tue,  7 Jan 2014 22:45:11 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <4521C493-D819-406E-B2B0-F45BAD760C08@nostrum.com>
Date: Tue, 7 Jan 2014 12:45:10 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <111AD084-0104-4C7F-9821-67B7EF5643BF@piuha.net>
References: <4521C493-D819-406E-B2B0-F45BAD760C08@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1510)
Cc: draft-ietf-avtcore-leap-second.all@tools.ietf.org, "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Review of draft-ietf-avtcore-leap-second-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 20:45:26 -0000

Thanks for your review, re-review and thank you authors for addressing =
the earlier comments. I have placed a no-obj position for this document =
for the upcoming IESG telechat.

Jari

On Jan 6, 2014, at 2:00 PM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-avtcore-leap-second-07
> Reviewer: Ben Campbell=09
> Review Date: 2014-01-06
> IESG Telechat date: 2014-01-09
>=20
> Summary: This draft is ready for publication as a proposed standard. =
All comments from my previous review of version 06 have been addressed.
>=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  Tue Jan  7 12:47:58 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 069C01AE1CB for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:47:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id auno7Wf-KOs9 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:47:56 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4E2861AE1C8 for <gen-art@ietf.org>; Tue,  7 Jan 2014 12:47:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 15A8C2CC61; Tue,  7 Jan 2014 22:47:47 +0200 (EET)
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 fmhMNDIuf50S; Tue,  7 Jan 2014 22:47:46 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id ECE5D2CC5D; Tue,  7 Jan 2014 22:47:44 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C5EEBB1@ESESSMB209.ericsson.se>
Date: Tue, 7 Jan 2014 12:47:43 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B100CAB-9676-4647-87CA-73E91D9F73A1@piuha.net>
References: <7594FB04B1934943A5C02806D1A2204B1C5EEBB1@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1510)
Cc: "draft-ietf-trill-o-pw.all@tools.ietf.org" <draft-ietf-trill-o-pw.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-o-pw-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 20:47:58 -0000

Christer: Thank you for the review and re-review! And thanks for the =
update, Lucy et al!

Jari

On Jan 7, 2014, at 1:20 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-trill-o-pw-04.txt
> Reviewer:                           Christer Holmberg
> Review Date:                     7 January 2014
> IETF LC End Date:             23 December 2013
> IESG Telechat date:         9 January 2014
> =20
> Summary:           My issue on the previously reviewed version of the =
document has been addressed, and the document is now ready for =
publication.
> =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 jari.arkko@piuha.net  Tue Jan  7 12:49:07 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0B91AE1CB for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:49:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ybjt-91oBKl6 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:49:05 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id AFA571AE1C8 for <gen-art@ietf.org>; Tue,  7 Jan 2014 12:49:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7EC442CC5D; Tue,  7 Jan 2014 22:48:37 +0200 (EET)
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 B9rpSMzxejvx; Tue,  7 Jan 2014 22:48:36 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 05C5C2CC48; Tue,  7 Jan 2014 22:48:34 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52792320.2060003@isode.com>
Date: Tue, 7 Jan 2014 12:48:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5FBA4C9B-12F0-483A-83A3-53B8037BB46A@piuha.net>
References: <52792320.2060003@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1510)
Cc: draft-turner-ct-keypackage-receipt-n-error-algs.all@tools.ietf.org, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-turner-ct-keypackage-receipt-n-error-algs-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 20:49:07 -0000

Thanks for your review again, Alexey.

Jari

On Nov 5, 2013, at 8:56 AM, 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
>=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-turner-ct-keypackage-receipt-n-error-algs-03
> Reviewer: Alexey Melnikov
> Review Date: 4 November 2013
> IETF LC End Date: 27 November 2013
> IESG Telechat date: N/A
>=20
> Summary: This draft is ready for publication as a Proposed Standard.
>=20
> Major issues: none
> Minor issues: none
> Nits: none
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Jan  7 12:50:20 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A080F1AE1D1 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:50:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FLO97WcGeWxa for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:50:19 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D4CCE1AE1D3 for <gen-art@ietf.org>; Tue,  7 Jan 2014 12:50:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AFAEA2CC5D; Tue,  7 Jan 2014 22:50:09 +0200 (EET)
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 6ikUZqAUBJVM; Tue,  7 Jan 2014 22:50:08 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 0E9C12CC48; Tue,  7 Jan 2014 22:50:06 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <71C7F6F1-E6B1-4894-9653-5969E2806723@vigilsec.com>
Date: Tue, 7 Jan 2014 12:50:05 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FA84B55-D3B8-4410-8011-0727651D6EBE@piuha.net>
References: <529511C9.2090005@nostrum.com> <71C7F6F1-E6B1-4894-9653-5969E2806723@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1510)
Cc: IETF Gen-ART <gen-art@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Gen-art] Gen-art last call review: draft-housley-ct-keypackage-receipt-n-error-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 20:50:20 -0000

Robert: thanks for the review. Russ: thanks for the update. I have =
placed a no-obj in the ballot for this document.

Jari

On Dec 1, 2013, at 7:35 AM, Russ Housley <housley@vigilsec.com> wrote:

>> Document: draft-housley-ct-keypackage-receipt-n-error-05
>> Reviewer: Robert Sparks
>> Review Date: 26 Nov 2013
>> IETF LC End Date: 27 Nov 2013
>> IESG Telechat date: not yet scheduled
>>=20
>> Summary: Ready
>>=20
>> Two nit-level comments:
>>=20
>> I found the formulation 'The key package error content type MUST be =
signed if the entity generating it is capable of signing it' awkward. =
Protocols break if you don't follow a MUST. As written, this says its ok =
to break the protocol. Is this, instead, really trying to say something =
about the thing that's going to evaluate the error content type (like =
"expect a signature unless you're explicitly configured to allow a lack =
of one")?
>=20
> Given that this is an error response, I was trying to allow for the =
situation where the signature cannot be created.  I was trying to say: =
If it can be signed, please do so.
>=20
>> The word "above" in "Error codes above this point" is ambiguous. It =
can mean either "earlier in the document" or "with numbers greater than =
this value".
>> That ambiguity may be harmless (it's easy to resolve by looking at =
the referenced document), but if you want to remove it, I suggest saying =
"The error codes listed here with values <=3D33".
>=20
> No problem.  Fixed in -06.  I shortened the suggested phrase to avoid =
a line wrap:
>=20
>   --  Error codes with values <=3D 33 are aligned with [RFC5934]
>=20
> Russ
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Jan  7 12:52:41 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B95B1AE1DC for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:52:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9KFTb0LTkjAD for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:52:39 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 2978F1AE1E5 for <gen-art@ietf.org>; Tue,  7 Jan 2014 12:52:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id EDC462CC5D; Tue,  7 Jan 2014 22:52:27 +0200 (EET)
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 5LxH4U1w9lW7; Tue,  7 Jan 2014 22:52:27 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id A5D332CC48; Tue,  7 Jan 2014 22:52:25 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <064c01cf0406$b1d07fa0$15717ee0$@olddog.co.uk>
Date: Tue, 7 Jan 2014 12:52:24 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4F6D95A-F849-4E66-9661-DEFEA0570359@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA129F13C6@AZ-FFEXMB04.global.avaya.com> <F3ADE4747C9E124B89F0ED2180CC814F23BDB1CE@xmb-aln-x02.cisco.com>, <52B1B033.6070507@gmail.com> <2e21e2d356bc46bd81b925abacbc1fa7@BLUPR05MB151.namprd05.prod.outlook.com> <064c01cf0406$b1d07fa0$15717ee0$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1510)
Cc: gen-art@ietf.org, draft-ietf-isis-rfc1142-to-historic.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-isis-rfc1142-to-historic-00
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 20:52:41 -0000

Thanks Dan & all=85 I have placed a no-obj for this document.

Jari

On Dec 28, 2013, at 11:55 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Thanks,
> I added an RFC editor note.
>=20
> Adrian
>=20
>> From: Mike Shand
>> Sent: 18 December 2013 14:24:51 (UTC) Dublin, Edinburgh, Lisbon, =
London
>> To: Les Ginsberg (ginsberg); Romascanu, Dan (Dan); gen-art@ietf.org
>> Cc: draft-ietf-isis-rfc1142-to-historic.all@tools.ietf.org
>> Subject: Re: Gen-ART review of draft-ietf-isis-rfc1142-to-historic-00
>>=20
>> I agree.
>>=20
>>     Mike
>>=20
>> On 17/12/2013 14:52, Les Ginsberg (ginsberg) wrote:
>>> Dan -
>>>=20
>>> Thanx for the review.
>>> I have no objection to your suggestion. I would hope this change can =
be done
>> by the RFC Editor.
>>>=20
>>>    Les
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
>>>> Sent: Tuesday, December 17, 2013 5:35 AM
>>>> To: gen-art@ietf.org
>>>> Cc: draft-ietf-isis-rfc1142-to-historic.all@tools.ietf.org
>>>> Subject: Gen-ART review of draft-ietf-isis-rfc1142-to-historic-00
>>>>=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-isis-rfc1142-to-historic-00
>>>> Reviewer: Dan Romascanu
>>>> Review Date: 12/17/13
>>>> IETF LC End Date: 12/24/13
>>>> IESG Telechat date:
>>>>=20
>>>> Summary: Ready
>>>>=20
>>>> Major issues:
>>>>=20
>>>> Minor issues:
>>>>=20
>>>> It may be more cautious refer to the 'latest available' version of =
the
> IS-IS
>>>> standard as we cannot be completely sure that the Second Edition =
will also
> be
>>>> the very last one. Suggested change in Section 1:
>>>>=20
>>>> OLD:
>>>>=20
>>>>    All references to IS-IS should be to ISO/IEC 10589:2002, Second
>>>>    Edition and RFC 1142 is only of historic interest.
>>>>=20
>>>> NEW:
>>>>=20
>>>>    All references to IS-IS should be to the latest edition of the =
IS-IS
>>>>    standard (currently ISO/IEC 10589:2002, Second
>>>>    Edition) and RFC 1142 is only of historic interest.
>>>>=20
>>>> Nits/editorial comments:
>>>>=20
>>>>=20
>>>>=20
>>=20
>>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Jan  7 12:54:15 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74C241AE1E1 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:54:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l-orxhUqKb78 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 12:54:13 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 1B48B1AE1DC for <gen-art@ietf.org>; Tue,  7 Jan 2014 12:54:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D52DC2CC61; Tue,  7 Jan 2014 22:54:03 +0200 (EET)
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 GSzX5eJrBW6F; Tue,  7 Jan 2014 22:54:00 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7DD402CC48; Tue,  7 Jan 2014 22:53:57 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24049E8BCCBB@MX15A.corp.emc.com>
Date: Tue, 7 Jan 2014 12:53:55 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8563878-8683-4F44-9D4A-F290DCF94F5F@piuha.net>
References: <F5063677821E3B4F81ACFB7905573F24049E65498D@MX15A.corp.emc.com> <047c01cecc14$4912e3b0$db38ab10$@gmail.com> <F5063677821E3B4F81ACFB7905573F24049E8BCCBB@MX15A.corp.emc.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
X-Mailer: Apple Mail (2.1510)
Cc: "draft-ietf-clue-telepresence-use-cases.all@tools.ietf.org" <draft-ietf-clue-telepresence-use-cases.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "allyn@cisco.com" <allyn@cisco.com>, "iesg@iesg.org" <iesg@iesg.org>, "mark.duckworth@polycom.com" <mark.duckworth@polycom.com>, "roni.even@mail01.huawei.com" <roni.even@mail01.huawei.com>, "stephen.botzko@polycom.com" <stephen.botzko@polycom.com>
Subject: Re: [Gen-art] Gen-art review of	draft-ietf-clue-telepresence-use-cases-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 20:54:15 -0000

Kathleen, Roni: Thank you both of you. I have placed a no-obj position =
for this document on this week's IESG telechat.

Jari

On Oct 18, 2013, at 10:37 AM, "Moriarty, Kathleen" =
<kathleen.moriarty@emc.com> wrote:

> Roni,
>=20
> Thank you for making the changes.
>=20
> Best regards,
> Kathleen
>=20
> -----Original Message-----
> From: Roni Even [mailto:ron.even.tlv@gmail.com]=20
> Sent: Friday, October 18, 2013 11:11 AM
> To: Moriarty, Kathleen; =
draft-ietf-clue-telepresence-use-cases.all@tools.ietf.org; =
iesg@iesg.org; gen-art@ietf.org
> Cc: mark.duckworth@polycom.com; allyn@cisco.com; =
stephen.botzko@polycom.com; roni.even@mail01.huawei.com
> Subject: RE: [Gen-art] Gen-art review of =
draft-ietf-clue-telepresence-use-cases-07
>=20
> Hi Kathleen,
> Thanks for the review.
> See inline
> Roni
>=20
>> -----Original Message-----
>> From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On=20=

>> Behalf Of Moriarty, Kathleen
>> Sent: 19 September, 2013 6:44 PM
>> To: draft-ietf-clue-telepresence-use-cases.all@tools.ietf.org;
> iesg@iesg.org;
>> gen-art@ietf.org
>> Cc: mark.duckworth@polycom.com; allyn@cisco.com;=20
>> stephen.botzko@polycom.com; roni.even@mail01.huawei.com
>> Subject: [Gen-art] Gen-art review of
> draft-ietf-clue-telepresence-use-cases-07
>>=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=20=

>> you may receive.
>>=20
>> Document: draft-ietf-clue-telepresence-use-cases-07
>> Reviewer: Kathleen Moriarty
>> Review Date: 9-19-13
>> IETF LC End Date: 9-26-13
>> IESG Telechat date: (if known)
>>=20
>> Summary: The draft is ready with nits to resolve.
>>=20
>> Major issues:
>>=20
>> Minor issues:
>>=20
>> Nits/editorial comments:
>> End of first paragraph on page 4 (section 2), change - to ,
>>   This state of affairs
>>   is not acceptable for the continued growth of telepresence -
>>   telepresence systems should have the same ease of interoperability =
as
>>   do telephones.
> [Roni Even] this paragraph is duplicated, appears also in section 1. =
So I deleted it from here and reference section 1 and made the change is =
section 1.
>>=20
>> Last paragraph in section 2, first sentence.  Consider correcting the=20=

>> punctuation, changing from:
>> The receiving device that decides how to render incoming information
>>   needs to understand a number of variables such as the spatial
>>   position of the speaker, the field of view of the cameras; the =
camera
>>   zoom; which media stream is related to each of the screens; etc.
>> To:
>>  The receiving device that decides how to render incoming information
>>   needs to understand a number of variables such as the spatial
>>   position of the speaker, the field of view of the cameras, the =
camera
>>   zoom, which media stream is related to each of the screens, etc.
>>=20
> [Roni Even] OK
>=20
>> End of section 3, consider changing from "on one site" to "at one =
site".
> I would
>> use on if I were referring to one side of the virtual table and '"at"=20=

>> for
> a location.
>>       Likewise, if a participant on one
>>       site gestures to a participant on the other site, all
>>       participants observe the gesture itself and the participants it
>>       includes.
>>=20
>> This phrase is used in the rest of section 3, consider changing it.
> Section 3.3
>> switches back to use "at a site".
> [Roni Even] OK
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Jan  7 13:03:55 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C162B1AE150 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 13:03:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MF9RL8Jcc4Tc for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 13:03:54 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9068C1AE089 for <gen-art@ietf.org>; Tue,  7 Jan 2014 13:03:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 55E6C2CC61; Tue,  7 Jan 2014 23:03:45 +0200 (EET)
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 YfYkauXJlK4q; Tue,  7 Jan 2014 23:03:44 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7FF3E2CC48; Tue,  7 Jan 2014 23:03:43 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <200D1BD7-800E-4F28-A4FD-C509B0F2EEC6@vigilsec.com>
Date: Tue, 7 Jan 2014 13:03:41 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <703695F5-9990-4851-BD81-C2B857574A15@piuha.net>
References: <200D1BD7-800E-4F28-A4FD-C509B0F2EEC6@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org Gen-ART" <gen-art@ietf.org>, draft-ietf-siprec-architecture.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-siprec-architecture-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 21:03:56 -0000

Thanks for your review and re-review, Russ. I have placed a no-obj =
position for this document.=20

Authors, please consider Russ's comment on Section 3.2.3 clarity.

Jari


From jari.arkko@piuha.net  Tue Jan  7 13:05:14 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ABDF1AE1D3 for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 13:05:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gFTMrT4JNWnF for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 13:05:11 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7D56C1AE1CE for <gen-art@ietf.org>; Tue,  7 Jan 2014 13:05:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 468A82CC61; Tue,  7 Jan 2014 23:05:02 +0200 (EET)
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 X53eIHZpv8Vy; Tue,  7 Jan 2014 23:04:59 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 93FF32CC48; Tue,  7 Jan 2014 23:04:58 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C5EEB9D@ESESSMB209.ericsson.se>
Date: Tue, 7 Jan 2014 13:04:57 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <59F68227-8EF0-45DB-A6D9-C36163952D6C@piuha.net>
References: <7594FB04B1934943A5C02806D1A2204B1C5EEB9D@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-ospf-manet-single-hop-or.all@tools.ietf.org" <draft-ietf-ospf-manet-single-hop-or.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of	draft-ietf-ospf-manet-single-hop-or-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 21:05:14 -0000

Christer: Thanks for the review and re-review. I have placed a no-obj =
position for this document.

Jari

On Jan 7, 2014, at 1:15 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-ospf-manet-single-hop-or-04.txt
> Reviewer: 		Christer Holmberg
> Review Date: 		7 January 2014
> IETF LC End Date:	17 December 2013
> IESG Telechat date: 	9 January 2014=20
>=20
> Summary:	My issue on the previously reviewed version of the =
document has been addressed, and the document is now ready for =
publication.
>=20
> Major issues: -
>=20
> Minor issues: -
>=20
> Nits/editorial comments: -
>=20
> Regards,
>=20
> Christer
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From wassim.haddad@ericsson.com  Tue Jan  7 15:19:04 2014
Return-Path: <wassim.haddad@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 516BB1AE22B for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 15:19:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JoevAj3yaKCX for <gen-art@ietfa.amsl.com>; Tue,  7 Jan 2014 15:19:02 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 57DF61AE22E for <gen-art@ietf.org>; Tue,  7 Jan 2014 15:19:02 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-a7-52cc8b59f9fb
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 29.D6.23183.95B8CC25; Wed,  8 Jan 2014 00:18:49 +0100 (CET)
Received: from eusjgala119.dyn.sj.us.am.ericsson.se (147.117.188.8) by smtp-am.internal.ericsson.com (147.117.188.92) with Microsoft SMTP Server id 14.2.347.0; Tue, 7 Jan 2014 18:17:45 -0500
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BBE8D31E-06B0-46B9-8BFA-5D1EA7C2143A"
Date: Tue, 7 Jan 2014 15:18:39 -0800
Message-ID: <8E64569C-4B2E-4E07-AD70-9D6301796D3E@ericsson.com>
To: General Area Review <gen-art@ietf.org>
MIME-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphluLIzCtJLcpLzFFi42KZXLonSjey+0yQwe/bZhbb979isbj66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJXx/msrU8EznorF2xazNzBu5u5i5OCQEDCR uP7AqIuRE8gUk7hwbz1bFyMXh5DAEUaJxwdXskM4hxglzj+ZywRSxSZgIPF1+VlWEJtZIEni 0I0FjCC2sIC/xI6FHewgQ1kEVCQmLs0ECfMK2Ev8bV7ODFGeJ7F1/3V2EFtEQEuiefVHNoga PYnnj7+yQBwhK3H63HMwW0hAXWLKrQksExj5ZiHZNgtJC0RcW2LZwtfMELaOxILdn9ggbHmJ 7W/nMMPUnDnwmGkBI9sqRo7S4tSy3HQjg02MwJA8JsGmu4Nxz0vLQ4zSHCxK4rxf3joHCQmk J5akZqemFqQWxReV5qQWH2Jk4uCUamBUcp+WkRSkER5jsi5stds7D5YKzrjTXCIaW2N0vP7d zdVeZ/POfdbrnQkb9UyvRjYLTJ8Ql2auyPUq/E4hf22+QnSwys/7VrP6Jm7aLXhQVSThRndH 7c8ZTtm/r1VKLLy431G+nPMRyzrlrovnfh6bdavZaZPBNNWJ1lmOzHfn9zI/+/X26GElluKM REMt5qLiRAALn51tFwIAAA==
Cc: draft-turner-application-cms-media-type.all@tools.ietf.org
Subject: [Gen-art] Gen-ART Review of draft-turner-application-cms-media-type-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 23:19:04 -0000

--Apple-Mail=_BBE8D31E-06B0-46B9-8BFA-5D1EA7C2143A
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-turner-application-cms-media-type-07
Reviewer:  Wassim Haddad
Review Date: 07 Jan 2014
IETF LC End Date: 27 Nov 2013
IETF Telechat Date: 09 Jan 2014

Summary:  This draft is ready to be published as informational standard

Major Issues: None

Minor Issues: none


Regards,

Wassim H.=

--Apple-Mail=_BBE8D31E-06B0-46B9-8BFA-5D1EA7C2143A
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset="us-ascii"

<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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="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-turner-application-cms-media-type-07<br>Reviewer: &nbsp;Wassim Haddad<br>Review Date: 07 Jan 2014<br>IETF LC End Date: 27 Nov 2013<br>IETF Telechat Date: 09 Jan 2014<br><br>Summary: &nbsp;This draft is ready to be published as informational standard<div><br></div><div>Major Issues: None</div><div><br></div><div>Minor Issues: none</div><div><br></div><div><br></div><div>Regards,</div><div><br></div><div>Wassim H.</div></body></html>
--Apple-Mail=_BBE8D31E-06B0-46B9-8BFA-5D1EA7C2143A--

From andrew.hutton@unify.com  Thu Jan  9 06:49:48 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCA21AE39C; Thu,  9 Jan 2014 06:49:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQPmvEQ9MD0S; Thu,  9 Jan 2014 06:49:43 -0800 (PST)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 835A71AE364; Thu,  9 Jan 2014 06:49:43 -0800 (PST)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx11.unify.com (Server) with ESMTP id A47971EB85C2; Thu,  9 Jan 2014 15:49:33 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.126]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Thu, 9 Jan 2014 15:49:30 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Russ Housley <housley@vigilsec.com>, "draft-ietf-siprec-architecture.all@tools.ietf.org" <draft-ietf-siprec-architecture.all@tools.ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-siprec-architecture-11
Thread-Index: AQHPCKVRfiG9pNCJ2kOTJueeYg99Wpp8glyg
Date: Thu, 9 Jan 2014 14:49:30 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17C9D8A2@MCHP04MSX.global-ad.net>
References: <200D1BD7-800E-4F28-A4FD-C509B0F2EEC6@vigilsec.com>
In-Reply-To: <200D1BD7-800E-4F28-A4FD-C509B0F2EEC6@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
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>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-siprec-architecture-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 14:49:48 -0000

Hi Russ,

Personally I can see that your suggested change to the text would result in=
 more clarity.

I would be happy to make this change.

Regards
Andy




> -----Original Message-----
> From: Russ Housley [mailto:housley@vigilsec.com]
> Sent: 03 January 2014 17:00
> To: draft-ietf-siprec-architecture.all@tools.ietf.org
> Cc: gen-art@ietf.org; ietf@ietf.org
> Subject: Gen-ART review of draft-ietf-siprec-architecture-11
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-siprec-architecture-11
> Reviewer: Russ Housley
> Review Date: 2014-01-03
> IETF LC End Date: 2013-10-01
> IESG Telechat date: 2014-01-09
>=20
> Summary:
>=20
> Thank you for addressing the issues raised in my previous review.
> This document is ready for publication as an Informational RFC.
>=20
> Major Concerns:  None.
>=20
> Minor Concerns:  None.
>=20
> Editorial Comments:
>=20
> The changes to Section 3.2.4 to resolve my earlier comment have
> introduced a clarity problem.  I suggest a minor rewording to fix it.
>=20
> 3.2.4.  Media Stream Mixing
>=20
>    In a basic session involving only audio there are typically two
>    audio/RTP streams between the two UAs involved transporting media in
>    each direction.  When recording this media, the two streams may be
>    mixed or not mixed at the SRC before being transmitted to the SRS.
>    In the case when they are not mixed, two separate streams are sent
>    to the SRS.  In the mixed case, a single mixed media stream is sent
>    to the SRS.  However, in the case when the media streams are not
>    mixed, the SDP offer sent to the SRS must describe two separate
>    media streams.


From mahoney@nostrum.com  Thu Jan  9 16:07:45 2014
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E0321AD8F9 for <gen-art@ietfa.amsl.com>; Thu,  9 Jan 2014 16:07:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-_IN74cxnOt for <gen-art@ietfa.amsl.com>; Thu,  9 Jan 2014 16:07:44 -0800 (PST)
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 E16E41AD34C for <gen-art@ietf.org>; Thu,  9 Jan 2014 16:07:43 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0A07T1u046711 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 9 Jan 2014 18:07:34 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52CF39C1.4080203@nostrum.com>
Date: Thu, 09 Jan 2014 18:07:29 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-01-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 00:07:45 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Alexey Melnikov   2014-01-22   draft-ietf-isis-rfc6326bis-01

Brian Carpenter   2014-01-22   draft-ietf-netmod-system-mgmt-10

Christer Holmberg 2014-01-22   draft-ietf-ancp-mc-extensions-14

Dan Romascanu     2014-01-23   draft-ietf-dane-registry-acronyms-03

Peter Yee         2014-01-23   draft-ietf-netmod-ip-cfg-12 *

Vijay Gurbani     2014-01-17   draft-ietf-abfab-arch-10

Wassim Haddad     2014-01-31   draft-crocker-id-adoption-05

* 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 brian.e.carpenter@gmail.com  Sat Jan 11 17:02:23 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 340161ACC88 for <gen-art@ietfa.amsl.com>; Sat, 11 Jan 2014 17:02:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxHDFHhdG_cz for <gen-art@ietfa.amsl.com>; Sat, 11 Jan 2014 17:02:21 -0800 (PST)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id A18711A1F71 for <gen-art@ietf.org>; Sat, 11 Jan 2014 17:02:21 -0800 (PST)
Received: by mail-pb0-f51.google.com with SMTP id up15so5952906pbc.38 for <gen-art@ietf.org>; Sat, 11 Jan 2014 17:02:11 -0800 (PST)
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=LjeOJ8ii43+jUT/YsIs/j258AGh48SM0S4vvM2jwhqc=; b=HP7eqTd2sMMC1oGiUqM7V7YBrL06uHkFj0lzAdy2O08dXdcxUrPMMQAXGobUYd24w2 JmTyjSf52rQrwQVA7Y8x1p8rOCSao1qDannoeLmypmZM79LHUpXM1+I1o8r6INjboZ3L fldi5CkkoKMpVl2hw73ps1MHVD9fPtXu3GN9fytqG/y5faPxj+HXiW9YTCoz3tD9NQLY /425dPUmou+oSSvJJGUi7QOstxiTtNVuiaR8ZmrOQ/xgoI7jDZXZ/eyIEMf6WSQM0vKe j96O6Y2HG6j0dHl7K6VKIAjTBJa3fOcn7dHu3GuYy2gcelfoqVGQzUThqMpqHoaH16zH 3OTg==
X-Received: by 10.68.237.228 with SMTP id vf4mr20973352pbc.131.1389488531242;  Sat, 11 Jan 2014 17:02:11 -0800 (PST)
Received: from [192.168.178.23] (87.199.69.111.dynamic.snap.net.nz. [111.69.199.87]) by mx.google.com with ESMTPSA id y9sm34994597pas.10.2014.01.11.17.02.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 11 Jan 2014 17:02:10 -0800 (PST)
Message-ID: <52D1E9A1.6060209@gmail.com>
Date: Sun, 12 Jan 2014 14:02:25 +1300
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-netmod-system-mgmt.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-netmod-system-mgmt-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 12 Jan 2014 01:02: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-netmod-system-mgmt-10.txt
Reviewer: Brian Carpenter
Review Date: 2014-01-12
IETF LC End Date: 2014-01-22
IESG Telechat date:

Summary:  Almost ready
--------

Comments:
---------

I haven't checked the yang syntax in detail. At first glance,
it looks good.

Minor Issues:
------------

"2.1.  System Identification

   There are many common properties used to identify devices, operating
   systems, software versions, etc. that need to be supported in the
   system data module.  These objects are defined as operational state
   data and the information returned by the server is intended to be
   specific to the device vendor."

Does "server" mean the NETCONF server?

"2.2.  System Time Management

   The management of the date and time used by the system need to be
   supported.  Use of one or more NTP servers to automatically set the
   system date and time need to be possible.  Utilization of the
   Timezone database [RFC6557] also need to be supported.  It should be
   possible for the server, as well as clients, to configure the system
   to use NTP."

Again, does this mean the NETCONF server? Also, which clients? This is
the first time the document mentions clients.

"2.3.  User Authentication

...It should be possible for the server, as well as
   clients, to configure the system authentication properties."

Same comment as for 2.2. Also, how does the network administrator enforce
a specific strength of authentication? It seems as though the clients can
choose to downgrade security.

"2.4.  DNS Resolver

   The configuration of the DNS resolver within the system containing
   the NETCONF server is required to control how domain names are
   resolved."

This is very hard to parse and could mean several things. Does it
mean that it MUST be possible to configure the DNS resolver?
(And I wonder what happens if the device is running mDNS?)

"3.6.  System Control

   The following operations are defined:

      set-current-datetime
      system-restart
      system-shutdown"

My reaction is that this is a very limited set of operations. For example
how about system standby (enter power-saving mode)? Yes, I know that
creates the problem of how to wake the system up again, but there are
solutions to that problem (e.g. polling). I can imagine many vendor-specific
extensions in this area, too.



From Attila.Takacs@ericsson.com  Sat Jan 11 23:39:17 2014
Return-Path: <Attila.Takacs@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F9301ADF4D for <gen-art@ietfa.amsl.com>; Sat, 11 Jan 2014 23:39:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0-Vg2kIqpth for <gen-art@ietfa.amsl.com>; Sat, 11 Jan 2014 23:39:14 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB5B1ADBD2 for <gen-art@ietf.org>; Sat, 11 Jan 2014 23:39:12 -0800 (PST)
X-AuditID: c1b4fb38-b7f2c8e000006d25-6e-52d24694f972
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 1C.57.27941.49642D25; Sun, 12 Jan 2014 08:39:00 +0100 (CET)
Received: from ESESSMB201.ericsson.se ([169.254.1.59]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.02.0347.000; Sun, 12 Jan 2014 08:39:00 +0100
From: Attila Takacs <Attila.Takacs@ericsson.com>
To: "Black, David" <david.black@emc.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-11
Thread-Index: Ac8FCULxJlQ5F8h9QISxvng85TrjLQAAIYDAApZ5F2A=
Date: Sun, 12 Jan 2014 07:38:59 +0000
Message-ID: <B336D1B7DDD08C44AE2B75E37932D09C1C4213F2@ESESSMB201.ericsson.se>
References: <8D3D17ACE214DC429325B2B98F3AE712026ECD43D7@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE712026ECD43D8@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026ECD43D8@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrGLMWRmVeSWpSXmKPExsUyM+Jvje4Ut0tBBg+eCVv86LnBbDH16DE2 i62H17JbvNi0i9Hi6qvPLA6sHkeOzGbxWLLkJ5PHis0rGT2+XP7MFsASxWWTkpqTWZZapG+X wJXRfGANS8Et/Yq5+1cyNTAuU+ti5OCQEDCRWLfKqIuRE8gUk7hwbz1bFyMXh5DAEUaJpgln 2CGcxYwSXV86mECq2AQMJC40T2YGsUUEciRObtvBCmIzCzxmlDjUIAhiCwt4SMy/dgeqxlOi /cUqJpBlIgJWEve++oKEWQRUJfr7WthBbF4BX4mNbU9YIXb1Mkqc3PcVbCangI/EpJ9tYEWM QNd9P7WGCWKXuMStJ/OZIK4WkFiy5zwzhC0q8fLxP1YIW0li7eHtLBD1ehLPTs2CsrUlli18 zQyxWFDi5MwnLBMYxWYhGTsLScssJC2zkLQsYGRZxchRnFqclJtuZLCJERhXB7f8ttjBePmv zSFGaQ4WJXHej2+dg4QE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUw1gaV7mK58atH8lvstX+f t+7ri3n9/qz7fyOeq88+FFQve/H1qkqr2KHnT8piy9a2Jpeu+/Dp7kyusyynOzzkrnRaHFfu 2qa6bIPCEtuwr0nis5Uz1vvJv+/cmROYd4V7H+PtsIT9k4Ukru87Vrxoje6KJY1XPt/e6B4x W7v0jPyZj1YhG1wq/iuxFGckGmoxFxUnAgBa0WGteQIAAA==
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "draft-ietf-ccamp-oam-configuration-fwk@tools.ietf.org" <draft-ietf-ccamp-oam-configuration-fwk@tools.ietf.org>, "ccamp-chairs@tools.ietf.org" <ccamp-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 12 Jan 2014 07:39:17 -0000

Hi David,
Thanks for the review!=20
Please look for [at] below to see how we address your comments.
Attila


-----Original Message-----
From: Black, David [mailto:david.black@emc.com]=20
Sent: Sunday, December 29, 2013 6:51 PM
To: General Area Review Team (gen-art@ietf.org); Attila Takacs; donald.fedy=
k@alcatel-lucent.com; hejia@huawei.com
Cc: adrian@olddog.co.uk; ccamp@ietf.org; ietf@ietf.org
Subject: RE: Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-11

One additional nit - Don Fedyk's email address listed in the draft does not=
 work.

[at] email address updated.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Sunday, December 29, 2013 9:46 PM
> To: General Area Review Team (gen-art@ietf.org);=20
> attila.takacs@ericsson.com; donald.fedyk@alcatel-lucent.com;=20
> hejia@huawei.com
> Cc: Black, David; adrian@olddog.co.uk; ccamp@ietf.org; ietf@ietf.org
> Subject: Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-11
>=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=20
> you may receive.
>=20
> Document: draft-ietf-ccamp-oam-configuration-fwk-11
> Reviewer: David L. Black
> Review Date: December 29, 2013
> IETF LC End Date: January 5, 2014
>=20
> Summary: This draft is basically ready for publication, but has nits=20
> that should be fixed before publication.
>=20
> This draft describes the GMPLS framework for signaling OAM=20
> configuration, and specifies additional RSVP elements to support that=20
> signaling.  Knowledge of RSVP, and specifically RSVP-TE is assumed;=20
> beyond that, the draft is complete, although it is very detailed - see=20
> editorial comment below on Section 3.
>=20
> Nits/editorial comments:
>=20
> Sections 3.1-3.3 dive into the details very quickly.  They would be=20
> easier to understand if there was an overview paragraph near the start=20
> of Section 3 that describes the roles of the two ADMIN_STATUS flags=20
> and the two LSP Attributes flags in OAM configuration (establishment,=20
> change/adjustment, deletion) before the current text that contains the de=
tails of RSVP message processing.
>=20

[at]  Added the two paragraphs below preceding the start of the detailed di=
scussions of Sections 3.1-3.3.

      Administrative Status Information is carried in the
      ADMIN_STATUS Object.  The Administrative Status Information is
      described in [RFC3471], the ADMIN_STATUS Object is specified for
      RSVP-TE in [RFC3473]. Two bits are allocated for the
      administrative control of OAM monitoring: the "OAM Flows
      Enabled" (M) and "OAM Alarms Enabled" (O) bits.  When the "OAM
      Flows Enabled" bit is set, OAM mechanisms MUST be enabled; if it
      is cleared, OAM mechanisms MUST be disabled.  When the "OAM
      Alarms Enabled" bit is set OAM triggered alarms are enabled and
      associated consequent actions MUST be executed including the
      notification to the management system.  When this bit is
      cleared, alarms are suppressed and no action SHOULD be executed
      and the management system SHOULD NOT be notified.

     The LSP_ATTRIBUTES and the LSP_REQUIRED_ATTRIBUTES objects
      are defined in [RFC5420] to provide means to signal LSP
      attributes and options in the form of TLVs.  Options and
      attributes signaled in the LSP_ATTRIBUTES object can be passed
      transparently through LSRs not supporting a particular option or
      attribute, while the contents of the LSP_REQUIRED_ATTRIBUTES
      object MUST be examined and processed by each LSR. One bit "OAM
      MEP entities desired" is allocated in the LSP Attributes Flags
      TLV to be used in the LSP_ATTRIBUTES object.  If the "OAM MEP
      entities desired" bit is set it is indicating that the
      establishment of OAM MEP entities are required at the endpoints
      of the signaled LSP. One bit "OAM MIP entities desired" is
      allocated in the LSP Attributes Flags TLV to be used in the
      LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUES objects. If the "OAM
      MIP entities desired" bit is set in the LSP_ATTRIBUTES Flags TLV
      in the LSP_REQUIRED_ATTRIBUTES Object, it is indicating that the
      establishment of OAM MIP entities is required at every transit
      node of the signaled LSP.

> There are a number of instances of "(IANA to assign)" in section 4=20
> that the RFC Editor will need to remove - an RFC Editor note to that=20
> effect should be inserted at the start of Section 4.

[at] note added
>=20
> Section 4.5 is necessarily incomplete on P2MP considerations, because=20
> (as it says) "P2MP OAM mechanisms are very specific to the data plane tec=
hnology".
> It would be helpful if section 4.5 contained language indicating what=20
> a specific data plane specification should include to completely=20
> specify P2MP OAM configuration for that data plane.
>=20

[at] Updated the text to reflect that the procedures highlighted in the sec=
tion are the baseline aspects that a technology specific document should sp=
ecify for a particular OAM technology to be sufficiently complete for use. =
It would be difficult to indicate what would be required for a complete P2M=
P OAM specification for any data plane; hence we took the approach to clari=
fy what the minimum requirements are. This is basically what is described i=
n Section 4.5.=20


> idnits 2.13.01 didn't find anything that needs attention.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer EMC Corporation, 176 South St.,=20
> Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From mbj@tail-f.com  Sun Jan 12 03:17:02 2014
Return-Path: <mbj@tail-f.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C94BE1ADF7F for <gen-art@ietfa.amsl.com>; Sun, 12 Jan 2014 03:17:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3FgAeNnFS9Zs for <gen-art@ietfa.amsl.com>; Sun, 12 Jan 2014 03:17:01 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [109.74.15.94]) by ietfa.amsl.com (Postfix) with ESMTP id 8AAAA1ACD04 for <gen-art@ietf.org>; Sun, 12 Jan 2014 03:17:00 -0800 (PST)
Received: from localhost (unknown [193.12.32.88]) by mail.tail-f.com (Postfix) with ESMTPSA id 36DAB240C187; Sun, 12 Jan 2014 12:16:48 +0100 (CET)
Date: Sun, 12 Jan 2014 12:16:47 +0100 (CET)
Message-Id: <20140112.121647.148657049.mbj@tail-f.com>
To: brian.e.carpenter@gmail.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <52D1E9A1.6060209@gmail.com>
References: <52D1E9A1.6060209@gmail.com>
X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-netmod-system-mgmt.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-netmod-system-mgmt-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 12 Jan 2014 11:17:03 -0000

Hi,

Thank you for this review.  Comments inline.

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>.
> 
> Please resolve these comments along with any other Last Call comments
> you may receive.
> 
> Document: draft-ietf-netmod-system-mgmt-10.txt
> Reviewer: Brian Carpenter
> Review Date: 2014-01-12
> IETF LC End Date: 2014-01-22
> IESG Telechat date:
> 
> Summary:  Almost ready
> --------
> 
> Comments:
> ---------
> 
> I haven't checked the yang syntax in detail. At first glance,
> it looks good.
> 
> Minor Issues:
> ------------
> 
> "2.1.  System Identification
> 
>    There are many common properties used to identify devices, operating
>    systems, software versions, etc. that need to be supported in the
>    system data module.  These objects are defined as operational state
>    data and the information returned by the server is intended to be
>    specific to the device vendor."
> 
> Does "server" mean the NETCONF server?

Yes.  We usually include the text below in the Terminology section,
and we should do that in this document as well.  We missed it.

   The following terms are defined in [RFC6241] and are not redefined
   here:

   o  client

   o  configuration data

   o  server

   o  state data

I will add this text.

> "2.2.  System Time Management
> 
>    The management of the date and time used by the system need to be
>    supported.  Use of one or more NTP servers to automatically set the
>    system date and time need to be possible.  Utilization of the
>    Timezone database [RFC6557] also need to be supported.  It should be
>    possible for the server, as well as clients, to configure the system
>    to use NTP."
> 
> Again, does this mean the NETCONF server? Also, which clients? This is
> the first time the document mentions clients.

See above.

> "2.3.  User Authentication
> 
> ...It should be possible for the server, as well as
>    clients, to configure the system authentication properties."
> 
> Same comment as for 2.2. Also, how does the network administrator enforce
> a specific strength of authentication? It seems as though the clients can
> choose to downgrade security.

I agree that this sounds a bit weird - servers do not configure
anything spontaneously.  Clients can not in general choose to
downgrade security.  It simply means that the data model should make
it possible to configure user authentication.  Access control must be
used to control which clients are authorized to do so.

NEW:

   It should be possible for clients to configure the system
   authentication properties.


> "2.4.  DNS Resolver
> 
>    The configuration of the DNS resolver within the system containing
>    the NETCONF server is required to control how domain names are
>    resolved."
> 
> This is very hard to parse and could mean several things. Does it
> mean that it MUST be possible to configure the DNS resolver?

Note that this is the "Objectives" section.  It means that an
objective is that the data model should allow for dns resolver
configuration.

Would it be more clear to say 

    The configuration of the DNS resolver within the system containing
    the NETCONF server is required in order to control how domain
    names are resolved.


> (And I wonder what happens if the device is running mDNS?)

Hmm, AFAICT, no special config is needed for mDNS to work?  So if
the device supports mDNS, it will be used for .local. names, right?

Or are you suggesting that this model should support configuration of
mDNS as well?

> "3.6.  System Control
> 
>    The following operations are defined:
> 
>       set-current-datetime
>       system-restart
>       system-shutdown"
> 
> My reaction is that this is a very limited set of operations.

Yes.  We tried to come up with a useful limited set of operations (and
config / oper data) that can be implemented on almost all devices.

> For example
> how about system standby (enter power-saving mode)? Yes, I know that
> creates the problem of how to wake the system up again, but there are
> solutions to that problem (e.g. polling). I can imagine many vendor-specific
> extensions in this area, too.

There are probably lots of other operations that can be useful.
However, we need to start somewhere, and more operations can be added
over time.  In general, we expect vendor-specific extensions to both
the supported set of operations, and the config and oper data.


/martin

From ron.even.tlv@gmail.com  Sun Jan 12 04:37:14 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 977131ADED7; Sun, 12 Jan 2014 04:37:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XzVYH_dWL-SF; Sun, 12 Jan 2014 04:37:12 -0800 (PST)
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 EF2871AD738; Sun, 12 Jan 2014 04:37:11 -0800 (PST)
Received: by mail-ea0-f177.google.com with SMTP id n15so2840461ead.8 for <multiple recipients>; Sun, 12 Jan 2014 04:37:01 -0800 (PST)
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=zIa5p7O5Qp3j9Ac4piQlJALHO6C8x2rim4+sGVq1PR0=; b=XKocWa5W0aypVBlY+w5CnZmUfjX3yIbLvLZDo9xJar2lD7lVPnvdPcRcAZCAgMIrY/ O05wEDbSftMsmTnCbjMugkdhhabsXSqdn1xd8KjZqy4ZP7H77gGrpeALOHBGtuwgvm6B IVdMSgtwAjynmjGIGdq09SwjHzWKfzaZYjylzCk/MTpqPAj4z5kb0BK/EZz+VMv9e+0I OD3bDpM+5pUdSqN3AD4PrGcD0TKBD35l5uhoA9YePl9ZFD97znbmImYSDXzyNCIoHCVb c6P5b8RzROh2T1Yu2KzFvAzcCZFi+Q773ZVl2W+D//5CyLrpLWXf7Yx37DZvpER0JPe3 Q8tw==
X-Received: by 10.15.51.13 with SMTP id m13mr2294734eew.103.1389530220943; Sun, 12 Jan 2014 04:37:00 -0800 (PST)
Received: from RoniE ([109.64.17.204]) by mx.google.com with ESMTPSA id o13sm30735504eex.19.2014.01.12.04.36.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 12 Jan 2014 04:37:00 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-mpls-in-udp.all@tools.ietf.org>
Date: Sun, 12 Jan 2014 14:33:13 +0200
Message-ID: <10b001cf0f92$7c6ddb90$754992b0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_10B1_01CF0FA3.3FF795F0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8PkQgMv9aHcPU1QKqHAKnrA2qEzA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-mpls-in-udp-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 12 Jan 2014 12:37:14 -0000

This is a multipart message in MIME format.

------=_NextPart_000_10B1_01CF0FA3.3FF795F0
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-in-udp-04

Reviewer: Roni Even

Review Date:2014-1-12

IETF LC End Date: 2014-1-16

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments

1.       The abstract section can be expanded with text from the first
paragraph of the introduction providing more information about usage

2.       The congestion section may need some text on UDP congestion
support, maybe reference RFC4505 but I am also OK with most of the current
text.

 

 


------=_NextPart_000_10B1_01CF0FA3.3FF795F0
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:.5in;
	line-height:115%;
	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: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:246115313;
	mso-list-type:hybrid;
	mso-list-template-ids:1460930480 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document:&n=
bsp; </span><span style=3D'font-family:"Courier =
New"'>draft-ietf-mpls-in-udp-04<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2014&#8211;1-12<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2014&#8211;1-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 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=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>The abstract section can =
be expanded with text from the first paragraph of the introduction =
providing more information about usage<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>The congestion section =
may need some text on UDP congestion support, maybe reference RFC4505 =
but I am also OK with most of the current text.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_10B1_01CF0FA3.3FF795F0--


From brian.e.carpenter@gmail.com  Sun Jan 12 10:52:05 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55A281AE00C for <gen-art@ietfa.amsl.com>; Sun, 12 Jan 2014 10:52:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r5N8FadZrrrx for <gen-art@ietfa.amsl.com>; Sun, 12 Jan 2014 10:52:03 -0800 (PST)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id EF2871AE00D for <gen-art@ietf.org>; Sun, 12 Jan 2014 10:52:02 -0800 (PST)
Received: by mail-pb0-f48.google.com with SMTP id md12so160626pbc.35 for <gen-art@ietf.org>; Sun, 12 Jan 2014 10:51:52 -0800 (PST)
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:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=csh6czSQvdE5bt5+4ltL/ILKwfY6qbs5aLYBODfkgC0=; b=R5/H5nX4FxwXrm1vVWRuiBRW4Drqjvp3m2XVA/SWtRnj5vycbxFuMpFSNMSyrSjiht +cQgSF2l9HDUD3iG/no8M8HDLuJA3ALS85MV7sJw8To8cIv4Nbn59PyHubsaDzhyswsu o/R0r1wgtF8rGicNEN38c6yesiJcIu5GuOZz/bz6UXqJRTPvwSFrBKaBdKuKoyglkYBf /k5fHPNtY+qRqTp8WRBm6k4JEyIoHKHNYp3qzuFceTD3Bfpoqp3kGYKyvDNiy6MEhW9Y 7RcJDjp9Nu/2q0rFI10mwa5cwnAVqW9Exs7pk7i2sPDUkKV5O77mzd/4YMvFRUxZ+yq4 dJpA==
X-Received: by 10.66.163.2 with SMTP id ye2mr25118873pab.110.1389552712375; Sun, 12 Jan 2014 10:51:52 -0800 (PST)
Received: from [192.168.178.23] (72.197.69.111.dynamic.snap.net.nz. [111.69.197.72]) by mx.google.com with ESMTPSA id yz5sm41617603pac.9.2014.01.12.10.51.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 12 Jan 2014 10:51:51 -0800 (PST)
Message-ID: <52D2E43F.2050105@gmail.com>
Date: Mon, 13 Jan 2014 07:51:43 +1300
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: Martin Bjorklund <mbj@tail-f.com>
References: <52D1E9A1.6060209@gmail.com> <20140112.121647.148657049.mbj@tail-f.com>
In-Reply-To: <20140112.121647.148657049.mbj@tail-f.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-netmod-system-mgmt.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-netmod-system-mgmt-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 12 Jan 2014 18:52:05 -0000

Hi Martin,

I'm fine with your answers and proposed changes.

> Hmm, AFAICT, no special config is needed for mDNS to work?  So if
> the device supports mDNS, it will be used for .local. names, right?

I think that's the main point, but RFC6762 does say this:
  "The ".local."
   suffix could appear in the search list because the user manually
   configured it, or because it was received via DHCP [RFC2132] or via
   any other mechanism for configuring the DNS search list."
That means it would be quite legitimate to configure it with NETMOD.
So probably you can ignore my comment ;-).

(There's also a more general question: what does the host do if it
receives conflicting config via DHCP and NETMOD? I guess you have a
general answer to that.)

> Or are you suggesting that this model should support configuration of
> mDNS as well?

As far as I know, mDNS is intended to be a zero-configuration
mechanism, so I think the answer is "No". It might be worth checking
with somebody in the DNSSD WG though.

Regards
   Brian

On 13/01/2014 00:16, Martin Bjorklund wrote:
> Hi,
> 
> Thank you for this review.  Comments inline.
> 
> 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>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-netmod-system-mgmt-10.txt
>> Reviewer: Brian Carpenter
>> Review Date: 2014-01-12
>> IETF LC End Date: 2014-01-22
>> IESG Telechat date:
>>
>> Summary:  Almost ready
>> --------
>>
>> Comments:
>> ---------
>>
>> I haven't checked the yang syntax in detail. At first glance,
>> it looks good.
>>
>> Minor Issues:
>> ------------
>>
>> "2.1.  System Identification
>>
>>    There are many common properties used to identify devices, operating
>>    systems, software versions, etc. that need to be supported in the
>>    system data module.  These objects are defined as operational state
>>    data and the information returned by the server is intended to be
>>    specific to the device vendor."
>>
>> Does "server" mean the NETCONF server?
> 
> Yes.  We usually include the text below in the Terminology section,
> and we should do that in this document as well.  We missed it.
> 
>    The following terms are defined in [RFC6241] and are not redefined
>    here:
> 
>    o  client
> 
>    o  configuration data
> 
>    o  server
> 
>    o  state data
> 
> I will add this text.
> 
>> "2.2.  System Time Management
>>
>>    The management of the date and time used by the system need to be
>>    supported.  Use of one or more NTP servers to automatically set the
>>    system date and time need to be possible.  Utilization of the
>>    Timezone database [RFC6557] also need to be supported.  It should be
>>    possible for the server, as well as clients, to configure the system
>>    to use NTP."
>>
>> Again, does this mean the NETCONF server? Also, which clients? This is
>> the first time the document mentions clients.
> 
> See above.
> 
>> "2.3.  User Authentication
>>
>> ...It should be possible for the server, as well as
>>    clients, to configure the system authentication properties."
>>
>> Same comment as for 2.2. Also, how does the network administrator enforce
>> a specific strength of authentication? It seems as though the clients can
>> choose to downgrade security.
> 
> I agree that this sounds a bit weird - servers do not configure
> anything spontaneously.  Clients can not in general choose to
> downgrade security.  It simply means that the data model should make
> it possible to configure user authentication.  Access control must be
> used to control which clients are authorized to do so.
> 
> NEW:
> 
>    It should be possible for clients to configure the system
>    authentication properties.
> 
> 
>> "2.4.  DNS Resolver
>>
>>    The configuration of the DNS resolver within the system containing
>>    the NETCONF server is required to control how domain names are
>>    resolved."
>>
>> This is very hard to parse and could mean several things. Does it
>> mean that it MUST be possible to configure the DNS resolver?
> 
> Note that this is the "Objectives" section.  It means that an
> objective is that the data model should allow for dns resolver
> configuration.
> 
> Would it be more clear to say 
> 
>     The configuration of the DNS resolver within the system containing
>     the NETCONF server is required in order to control how domain
>     names are resolved.
> 
> 
>> (And I wonder what happens if the device is running mDNS?)
> 
> Hmm, AFAICT, no special config is needed for mDNS to work?  So if
> the device supports mDNS, it will be used for .local. names, right?
> 
> Or are you suggesting that this model should support configuration of
> mDNS as well?
> 
>> "3.6.  System Control
>>
>>    The following operations are defined:
>>
>>       set-current-datetime
>>       system-restart
>>       system-shutdown"
>>
>> My reaction is that this is a very limited set of operations.
> 
> Yes.  We tried to come up with a useful limited set of operations (and
> config / oper data) that can be implemented on almost all devices.
> 
>> For example
>> how about system standby (enter power-saving mode)? Yes, I know that
>> creates the problem of how to wake the system up again, but there are
>> solutions to that problem (e.g. polling). I can imagine many vendor-specific
>> extensions in this area, too.
> 
> There are probably lots of other operations that can be useful.
> However, we need to start somewhere, and more operations can be added
> over time.  In general, we expect vendor-specific extensions to both
> the supported set of operations, and the config and oper data.
> 
> 
> /martin
> 

From csp@csperkins.org  Sun Jan 12 11:33:28 2014
Return-Path: <csp@csperkins.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3991AE019 for <gen-art@ietfa.amsl.com>; Sun, 12 Jan 2014 11:33:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4-o2qMeDzqVz for <gen-art@ietfa.amsl.com>; Sun, 12 Jan 2014 11:33:26 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id BE1181AE013 for <gen-art@ietf.org>; Sun, 12 Jan 2014 11:33:26 -0800 (PST)
Received: from [81.187.2.149] (port=37456 helo=[192.168.0.15]) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1W2QmX-0004m6-2W; Sun, 12 Jan 2014 19:33:14 +0000
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <52AFFC87.60707@ericsson.com>
Date: Sun, 12 Jan 2014 19:33:11 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <47EB6A3A-03B4-4EAA-A3C0-5E1A2A5B287E@csperkins.org>
References: <52AFDFBD.5010307@ericsson.com> <52AFFC87.60707@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.1827)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-avtcore-rtp-security-options.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-avtcore-rtp-security-options-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 12 Jan 2014 19:33:28 -0000

Hi,

Thanks, I incorporated changes to address these. For Section 2.1, I =
changed =93protecting the RTP session and its RTP and RTCP traffic and =
the key-management protocol becomes important in which security =
statements one can do=94 to =93protecting the RTP session (and hence the =
RTP and RTCP traffic) and the key-management protocol becomes important =
to determine what security claims can be made=94. Hopefully this is =
clearer.

Cheers,
Colin


On 17 Dec 2013, at 07:25, Magnus Westerlund =
<magnus.westerlund@ericsson.com> wrote:
> Thanks Suresh,
>=20
> We will take your comment into account when we do the next revision.
>=20
> Cheers
>=20
> Magnus
>=20
> On 2013-12-17 06:23, Suresh Krishnan 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-avtcore-rtp-security-options-09.txt
>> Reviewer: Suresh Krishnan
>> Review Date: 2013/12/16
>> IESG Telechat date: 2013/12/19
>>=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
>> This sentence is a bit awkward
>>=20
>> The IETF considers it important that protocols implement, and makes
>> available to the user, secure modes of operation
>>=20
>> Suggest rewording to something like
>>=20
>> The IETF considers it important that protocols implement secure modes =
of
>> operation and make them available to users.
>>=20
>> * Section 2.1
>>=20
>> I am not sure what this statement means. Can you please clarify?
>>=20
>> "Here the combination of the security protocol protecting the RTP
>> session and its RTP and RTCP traffic and the key-management protocol
>> becomes important in which security statements one can do."
>>=20
>> * Section 4.1.4
>>=20
>> s/will be more relevant then/will be more relevant than/
>>=20
>> This sentence is hard to read. Please consider rewording
>>=20
>> "Commonly by provisioning the verifier with the public part of a root
>> certificate, this enables the verifier to verify a trust chain from =
the
>> root certificate down to the identity certificate."
>>=20
>>=20
>> Thanks
>> Suresh
>>=20
>>=20
>=20
>=20
> --=20
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20



--=20
Colin Perkins
http://csperkins.org/




From mbj@tail-f.com  Sun Jan 12 12:27:13 2014
Return-Path: <mbj@tail-f.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D393F1ACC85 for <gen-art@ietfa.amsl.com>; Sun, 12 Jan 2014 12:27:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OsyxtZFu3ZlG for <gen-art@ietfa.amsl.com>; Sun, 12 Jan 2014 12:27:12 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [109.74.15.94]) by ietfa.amsl.com (Postfix) with ESMTP id ED8E31ACAD7 for <gen-art@ietf.org>; Sun, 12 Jan 2014 12:27:11 -0800 (PST)
Received: from localhost (unknown [193.12.32.88]) by mail.tail-f.com (Postfix) with ESMTPSA id 2DFD8240C07D; Sun, 12 Jan 2014 21:27:00 +0100 (CET)
Date: Sun, 12 Jan 2014 21:26:59 +0100 (CET)
Message-Id: <20140112.212659.483265232.mbj@tail-f.com>
To: brian.e.carpenter@gmail.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <52D2E43F.2050105@gmail.com>
References: <52D1E9A1.6060209@gmail.com> <20140112.121647.148657049.mbj@tail-f.com> <52D2E43F.2050105@gmail.com>
X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-netmod-system-mgmt.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-netmod-system-mgmt-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 12 Jan 2014 20:27:14 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> Hi Martin,
> 
> I'm fine with your answers and proposed changes.
> 
> > Hmm, AFAICT, no special config is needed for mDNS to work?  So if
> > the device supports mDNS, it will be used for .local. names, right?
> 
> I think that's the main point, but RFC6762 does say this:
>   "The ".local."
>    suffix could appear in the search list because the user manually
>    configured it, or because it was received via DHCP [RFC2132] or via
>    any other mechanism for configuring the DNS search list."
> That means it would be quite legitimate to configure it with NETMOD.

Yes that is my understanding as well.

> So probably you can ignore my comment ;-).
> 
> (There's also a more general question: what does the host do if it
> receives conflicting config via DHCP and NETMOD? I guess you have a
> general answer to that.)

Yes; so the YANG configuration data models is the "static" or "manual"
configuration.  Then there are all kinds of other mechanism that can
influence what the device is actually using, i.e., influence its
operational state.  DHCP is one example.  RA is another.  Exactly how
this dynamic influence of the operational state is done depends on the
mechanism, on the different parmeters, and maybe on local policy.
Sometimes the manually configured value has higher precedence,
sometimes the value received over DHCP, and sometimes the values may
be both be used.

> > Or are you suggesting that this model should support configuration of
> > mDNS as well?
> 
> As far as I know, mDNS is intended to be a zero-configuration
> mechanism, so I think the answer is "No". It might be worth checking
> with somebody in the DNSSD WG though.

Ok.


/martin

From Francis.Dupont@fdupont.fr  Mon Jan 13 05:55:53 2014
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC0771AE183 for <gen-art@ietfa.amsl.com>; Mon, 13 Jan 2014 05:55:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level: 
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gcukugvrf37f for <gen-art@ietfa.amsl.com>; Mon, 13 Jan 2014 05:55:51 -0800 (PST)
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 B13A51AE181 for <gen-art@ietf.org>; Mon, 13 Jan 2014 05:55:50 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id s0DDtd4t028318; Mon, 13 Jan 2014 14:55:39 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201401131355.s0DDtd4t028318@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 13 Jan 2014 14:55:39 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: draft-moriarty-pkcs12v1-1.all@tools.ietf.org
Subject: [Gen-art] review of draft-moriarty-pkcs12v1-1-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 13:55:53 -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-moriarty-pkcs12v1-1-03.txt
Reviewer: Francis Dupont
Review Date: 20130104
IETF LC End Date: 20130110
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: (not really technical)
PKCS#12 was subject to concerns from teh cryptography community,
in particular from Peter Gutmann, based on:
 - its (too) high complexity (BTW IMHO it is a legitimate concern:
 complexity is not wellcome for a security device)
 - (related to the previous item) its possible misuse with private
 key, summarized by this famous warning in OpenSSL FAQ:
"Occasionally someone suggests using a command such as:

openssl pkcs12 -export -out cacert.p12 -in cacert.pem -inkey cakey.pem

DO NOT DO THIS! This command will give away your CAs private key and
reduces its security to zero: allowing anyone to forge certificates in
whatever name they choose."

Unfortunately I can't see how we can address these concerns in
the document. Perhaps with a stronger security considerations section?

Nits/editorial comments:
 - TOC page 3 and F page 29: Acknowledgements -> Acknowledgments

 - 1 page 4 in:
      The most secure of the privacy
   and integrity modes require the source and destination platforms to
   have trusted public/private key pairs usable for digital signatures
   and encryption, respectively.

  respectively suggests the same order but the private key is used to
  sign and the public key to encrypt. I propose to swap keys, i.e.,
  to use "private/public" key pairs.

 - 5.1 5 B page 16: i.e. -> i.e.,

 - a full example should have been wellcome but IMHO it is far too late
  (and there are a lot of tools able to produce examples if needed :-).

Regards

Francis.Dupont@fdupont.fr

From kathleen.moriarty@emc.com  Mon Jan 13 06:42:51 2014
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B89C1ADF7F for <gen-art@ietfa.amsl.com>; Mon, 13 Jan 2014 06:42:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYM-IZWRoYiR for <gen-art@ietfa.amsl.com>; Mon, 13 Jan 2014 06:42:49 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 8E7C01ADF53 for <gen-art@ietf.org>; Mon, 13 Jan 2014 06:42:48 -0800 (PST)
Received: from maildlpprd51.lss.emc.com (maildlpprd51.lss.emc.com [10.106.48.155]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0DEgT0O024678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Jan 2014 09:42:30 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s0DEgT0O024678
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1389624150; bh=bDNbPTeu6E9jmOIkKXVJEsHBezA=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=ZlgeuduDn+T/DhZT8G4+9fwd16MLmTHW8tcVOcV79ykTZwXyN6SU7n4SV9lnlxM7I G86vw/qtOpPAvSksy2+1mlHbMKkUgCb7r/aCAZbxtAktH354+YpFqdK9zU443g0ep3 CCz770IgjS2SLTQl8UeizV3XKHLvMKS6J9ZlgDp0=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s0DEgT0O024678
Received: from mailusrhubprd03.lss.emc.com (mailusrhubprd03.lss.emc.com [10.253.24.21]) by maildlpprd51.lss.emc.com (RSA Interceptor); Mon, 13 Jan 2014 09:42:10 -0500
Received: from mxhub02.corp.emc.com (mxhub02.corp.emc.com [10.254.141.104]) by mailusrhubprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0DEg8Wb000618 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Jan 2014 09:42:09 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub02.corp.emc.com ([10.254.141.104]) with mapi; Mon, 13 Jan 2014 09:42:08 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "Francis.Dupont@fdupont.fr" <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Mon, 13 Jan 2014 09:42:07 -0500
Thread-Topic: review of draft-moriarty-pkcs12v1-1-03.txt
Thread-Index: Ac8QZy98U0qnQvQxTba4mb0jBVVbXAABh3AQ
Message-ID: <F5063677821E3B4F81ACFB7905573F2406584BA440@MX15A.corp.emc.com>
References: <201401131355.s0DDtd4t028318@givry.fdupont.fr>
In-Reply-To: <201401131355.s0DDtd4t028318@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: mailusrhubprd03.lss.emc.com
X-RSA-Classifications: public
Cc: "draft-moriarty-pkcs12v1-1.all@tools.ietf.org" <draft-moriarty-pkcs12v1-1.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-moriarty-pkcs12v1-1-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 14:42:51 -0000

Thank you for the review, Francis.

Once this version is published, change control and copyright is transferred=
 to the IETF.  The next version of this document will work to improve known=
 issues.

I will make the change from public/private to private/public as noted, that=
 makes sense.  I would imagine it was only written that way as the key pair=
s are typically referred to in that order as opposed to the original author=
 thinking through the sentence as you had done.

I have a few other edits to include and will have this ready before the end=
 of the week.

Thank you,
Kathleen

-----Original Message-----
From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]=20
Sent: Monday, January 13, 2014 8:56 AM
To: gen-art@ietf.org
Cc: draft-moriarty-pkcs12v1-1.all@tools.ietf.org
Subject: review of draft-moriarty-pkcs12v1-1-03.txt

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

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

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

Document: draft-moriarty-pkcs12v1-1-03.txt
Reviewer: Francis Dupont
Review Date: 20130104
IETF LC End Date: 20130110
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: (not really technical)
PKCS#12 was subject to concerns from teh cryptography community, in particu=
lar from Peter Gutmann, based on:
 - its (too) high complexity (BTW IMHO it is a legitimate concern:
 complexity is not wellcome for a security device)
 - (related to the previous item) its possible misuse with private  key, su=
mmarized by this famous warning in OpenSSL FAQ:
"Occasionally someone suggests using a command such as:

openssl pkcs12 -export -out cacert.p12 -in cacert.pem -inkey cakey.pem

DO NOT DO THIS! This command will give away your CAs private key and reduce=
s its security to zero: allowing anyone to forge certificates in whatever n=
ame they choose."

Unfortunately I can't see how we can address these concerns in the document=
. Perhaps with a stronger security considerations section?

Nits/editorial comments:
 - TOC page 3 and F page 29: Acknowledgements -> Acknowledgments

 - 1 page 4 in:
      The most secure of the privacy
   and integrity modes require the source and destination platforms to
   have trusted public/private key pairs usable for digital signatures
   and encryption, respectively.

  respectively suggests the same order but the private key is used to
  sign and the public key to encrypt. I propose to swap keys, i.e.,
  to use "private/public" key pairs.

 - 5.1 5 B page 16: i.e. -> i.e.,

 - a full example should have been wellcome but IMHO it is far too late
  (and there are a lot of tools able to produce examples if needed :-).

Regards

Francis.Dupont@fdupont.fr


From xuxiaohu@huawei.com  Sun Jan 12 23:07:18 2014
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414781AE050; Sun, 12 Jan 2014 23:07:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.212
X-Spam-Level: *
X-Spam-Status: No, score=1.212 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xD8FXE6wBVYI; Sun, 12 Jan 2014 23:07:16 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id B1FAD1AE04C; Sun, 12 Jan 2014 23:07:15 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCK83381; Mon, 13 Jan 2014 07:07:03 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 13 Jan 2014 07:06:24 +0000
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 13 Jan 2014 07:07:00 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.45]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Mon, 13 Jan 2014 15:06:54 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-mpls-in-udp.all@tools.ietf.org" <draft-ietf-mpls-in-udp.all@tools.ietf.org>
Thread-Topic: Gen-ART LC review of draft-ietf-mpls-in-udp-04
Thread-Index: Ac8PkQgMv9aHcPU1QKqHAKnrA2qEzAAnLfyA
Date: Mon, 13 Jan 2014 07:06:53 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824433B@NKGEML512-MBS.china.huawei.com>
References: <10b001cf0f92$7c6ddb90$754992b0$@gmail.com>
In-Reply-To: <10b001cf0f92$7c6ddb90$754992b0$@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.134]
Content-Type: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824433BNKGEML512MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:17:29 -0800
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] =?gb2312?b?tPC4tDogR2VuLUFSVCBMQyByZXZpZXcgb2YgZHJhZnQt?= =?gb2312?b?aWV0Zi1tcGxzLWluLXVkcC0wNA==?=
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 07:07:18 -0000

--_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824433BNKGEML512MBSchi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SGkgUm9uaSwNCg0KVGhhbmtzIGEgbG90IGZvciB5b3VyIEdlbi1BUlQgcmV2aWV3IGFuZCBjb21t
ZW50cy4gWW91ciBjb21tZW50cyB3b3VsZCBiZSBjb25zaWRlcmVkIGluIHRoZSBuZXh0IHJldmlz
aW9uLg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0Kt6K8/sjLOiBSb25pIEV2ZW4gW21haWx0
bzpyb24uZXZlbi50bHZAZ21haWwuY29tXQ0Kt6LLzcqxvOQ6IDIwMTTE6jHUwjEyyNUgMjA6MzMN
CsrVvP7IyzogZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC5hbGxAdG9vbHMuaWV0Zi5vcmcNCrOty806
IGdlbi1hcnRAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCtb3zOI6IEdlbi1BUlQgTEMgcmV2aWV3
IG9mIGRyYWZ0LWlldGYtbXBscy1pbi11ZHAtMDQNCg0KSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFS
VCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9yIGJhY2tncm91bmQgb24gR2VuLUFSVCwgcGxl
YXNlIHNlZSB0aGUgRkFRIGF0IDxodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90
cmFjL3dpa2kvR2VuQXJ0ZmFxPi4NClBsZWFzZSByZXNvbHZlIHRoZXNlIGNvbW1lbnRzIGFsb25n
IHdpdGggYW55IG90aGVyIExhc3QgQ2FsbCBjb21tZW50cyB5b3UgbWF5IHJlY2VpdmUuDQoNCkRv
Y3VtZW50OiAgZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC0wNA0KDQpSZXZpZXdlcjogUm9uaSBFdmVu
DQoNClJldmlldyBEYXRlOjIwMTSoQzEtMTINCg0KSUVURiBMQyBFbmQgRGF0ZTogMjAxNKhDMS0x
Ng0KDQpJRVNHIFRlbGVjaGF0IGRhdGU6DQoNCg0KDQpTdW1tYXJ5OiBUaGlzIGRyYWZ0IGlzIGFs
bW9zdCByZWFkeSBmb3IgcHVibGljYXRpb24gYXMgYSBzdGFuZGFyZCB0cmFjayBSRkMuDQoNCg0K
DQoNCg0KTWFqb3IgaXNzdWVzOg0KDQoNCg0KTWlub3IgaXNzdWVzOg0KDQoNCg0KDQpOaXRzL2Vk
aXRvcmlhbCBjb21tZW50cw0KDQoxLiAgICAgICBUaGUgYWJzdHJhY3Qgc2VjdGlvbiBjYW4gYmUg
ZXhwYW5kZWQgd2l0aCB0ZXh0IGZyb20gdGhlIGZpcnN0IHBhcmFncmFwaCBvZiB0aGUgaW50cm9k
dWN0aW9uIHByb3ZpZGluZyBtb3JlIGluZm9ybWF0aW9uIGFib3V0IHVzYWdlDQoNCjIuICAgICAg
IFRoZSBjb25nZXN0aW9uIHNlY3Rpb24gbWF5IG5lZWQgc29tZSB0ZXh0IG9uIFVEUCBjb25nZXN0
aW9uIHN1cHBvcnQsIG1heWJlIHJlZmVyZW5jZSBSRkM0NTA1IGJ1dCBJIGFtIGFsc28gT0sgd2l0
aCBtb3N0IG9mIHRoZSBjdXJyZW50IHRleHQuDQoNCg0K

--_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824433BNKGEML512MBSchi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	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:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:36.0pt;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:SimSun;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:246115313;
	mso-list-type:hybrid;
	mso-list-template-ids:1460930480 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D">Hi Roni,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D">Thanks a lot for your Gen-ART review and comment=
s. Your comments would be considered in the next revision.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D">Xiaohu<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal">
<b><span style=3D"font-size:10.0pt;font-family:SimSun">=B7=A2=BC=FE=C8=CB<s=
pan lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D"font-si=
ze:10.0pt;font-family:SimSun"> Roni Even [mailto:ron.even.tlv@gmail.com]
<br>
</span><b><span style=3D"font-size:10.0pt;font-family:SimSun">=B7=A2=CB=CD=
=CA=B1=BC=E4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:SimSun"> 2014</span><span style=3D"font=
-size:10.0pt;font-family:SimSun">=C4=EA<span lang=3D"EN-US">1</span>=D4=C2<=
span lang=3D"EN-US">12</span>=C8=D5<span lang=3D"EN-US">
 20:33<br>
</span><b>=CA=D5=BC=FE=C8=CB<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> draft-ietf-mpls-in-udp.all@tools.ietf.org<br>
</span><b>=B3=AD=CB=CD<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> gen-art@ietf.org; ietf@ietf.org<br>
</span><b>=D6=F7=CC=E2<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> Gen-ART LC review of draft-ietf-mpls-in-udp-04<o:p></o:p></span></span></=
p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><a name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>=
<span lang=3D"EN-US">I am the assigned Gen-ART reviewer for this draft. For=
 background on Gen-ART, please see the FAQ at &lt;</span><span lang=3D"EN-U=
S"><a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" targ=
et=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&g=
t;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Please resolve these comments a=
long with any other Last Call comments you may receive.<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Document:&nbsp;
</span><span lang=3D"EN-US" style=3D"font-family:&quot;Courier New&quot;">d=
raft-ietf-mpls-in-udp-04<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Reviewer: Roni Even<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Review Date:2014=A8C1=
-12<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IETF LC End Date: 201=
4=A8C1-16<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IESG Telechat date:
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary: This draft i=
s almost ready for publication as a standard track RFC.<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Major issues:<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Minor issues:<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Nits/editorial comments<o:p></o=
:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:=
Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">The abstract section ca=
n be expanded with text from the first paragraph of the introduction provid=
ing more information about usage<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:=
Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">The congestion section =
may need some text on UDP congestion support, maybe reference RFC4505 but I=
 am also OK with most of the current text.<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>
</div>
</div>
</body>
</html>

--_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824433BNKGEML512MBSchi_--

From kathleen.moriarty@emc.com  Mon Jan 13 08:02:57 2014
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ED451AE09F for <gen-art@ietfa.amsl.com>; Mon, 13 Jan 2014 08:02:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tp9RqwvDJtey for <gen-art@ietfa.amsl.com>; Mon, 13 Jan 2014 08:02:54 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id B7D921AE04F for <gen-art@ietf.org>; Mon, 13 Jan 2014 08:02:54 -0800 (PST)
Received: from maildlpprd52.lss.emc.com (maildlpprd52.lss.emc.com [10.106.48.156]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0DG2ZJm018280 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Jan 2014 11:02:35 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s0DG2ZJm018280
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1389628956; bh=4G0eXYSOWlxiUr8iTMgCAq1ET8M=; h=From:To:CC:Date:Subject:Message-ID:References:Content-Type: Content-Transfer-Encoding:MIME-Version; b=dU9nHjnMkAKeXNjPRoi6UuDMCEIU/ZD8YWCUyfDoZdt8Yg6RQatWOICjstwJ8Zi25 ZtIEv9DMco39UrVmCUd3cu3tn7lSKTf63dbNPP8GwaXLwYh3Hk+L4LHdNE2hfcRYUm vJY4zNdRgR/k6X+FkIV1lQVby4X8RHocyGFVc8ow=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s0DG2ZJm018280
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd52.lss.emc.com (RSA Interceptor); Mon, 13 Jan 2014 11:02:22 -0500
Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0DG2MgM024198 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Jan 2014 11:02:22 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Mon, 13 Jan 2014 11:02:21 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "Francis.Dupont@fdupont.fr" <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Mon, 13 Jan 2014 11:02:21 -0500
Thread-Topic: review of draft-moriarty-pkcs12v1-1-03.txt
Thread-Index: Ac8QZy98U0qnQvQxTba4mb0jBVVbXAABh3AQAALSuxA=
Message-ID: <F5063677821E3B4F81ACFB7905573F2406584BA472@MX15A.corp.emc.com>
References: <201401131355.s0DDtd4t028318@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: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: DLM_1, public
Cc: "draft-moriarty-pkcs12v1-1.all@tools.ietf.org" <draft-moriarty-pkcs12v1-1.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-moriarty-pkcs12v1-1-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 16:02:57 -0000

Hi Francis,

I went to update your comments in my draft version and in thinking about it=
 more, I agree with the current text on the public/private order.  As I rea=
d it, the referenced keys are discussed for the keys that validate and I as=
sume you read it as the creation of a signature or to encrypt.  I'm going t=
o leave that as-is.

Thanks,
Kathleen

-----Original Message-----
From: Moriarty, Kathleen=20
Sent: Monday, January 13, 2014 9:42 AM
To: 'Francis.Dupont@fdupont.fr'; gen-art@ietf.org
Cc: draft-moriarty-pkcs12v1-1.all@tools.ietf.org
Subject: RE: review of draft-moriarty-pkcs12v1-1-03.txt

Thank you for the review, Francis.

Once this version is published, change control and copyright is transferred=
 to the IETF.  The next version of this document will work to improve known=
 issues.

I will make the change from public/private to private/public as noted, that=
 makes sense.  I would imagine it was only written that way as the key pair=
s are typically referred to in that order as opposed to the original author=
 thinking through the sentence as you had done.

I have a few other edits to include and will have this ready before the end=
 of the week.

Thank you,
Kathleen

-----Original Message-----
From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]=20
Sent: Monday, January 13, 2014 8:56 AM
To: gen-art@ietf.org
Cc: draft-moriarty-pkcs12v1-1.all@tools.ietf.org
Subject: review of draft-moriarty-pkcs12v1-1-03.txt

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

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

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

Document: draft-moriarty-pkcs12v1-1-03.txt
Reviewer: Francis Dupont
Review Date: 20130104
IETF LC End Date: 20130110
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: (not really technical)
PKCS#12 was subject to concerns from teh cryptography community, in particu=
lar from Peter Gutmann, based on:
 - its (too) high complexity (BTW IMHO it is a legitimate concern:
 complexity is not wellcome for a security device)
 - (related to the previous item) its possible misuse with private  key, su=
mmarized by this famous warning in OpenSSL FAQ:
"Occasionally someone suggests using a command such as:

openssl pkcs12 -export -out cacert.p12 -in cacert.pem -inkey cakey.pem

DO NOT DO THIS! This command will give away your CAs private key and reduce=
s its security to zero: allowing anyone to forge certificates in whatever n=
ame they choose."

Unfortunately I can't see how we can address these concerns in the document=
. Perhaps with a stronger security considerations section?

Nits/editorial comments:
 - TOC page 3 and F page 29: Acknowledgements -> Acknowledgments

 - 1 page 4 in:
      The most secure of the privacy
   and integrity modes require the source and destination platforms to
   have trusted public/private key pairs usable for digital signatures
   and encryption, respectively.

  respectively suggests the same order but the private key is used to
  sign and the public key to encrypt. I propose to swap keys, i.e.,
  to use "private/public" key pairs.

 - 5.1 5 B page 16: i.e. -> i.e.,

 - a full example should have been wellcome but IMHO it is far too late
  (and there are a lot of tools able to produce examples if needed :-).

Regards

Francis.Dupont@fdupont.fr


From scott.brim@gmail.com  Mon Jan 13 10:20:57 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B00CC1AE04F for <gen-art@ietfa.amsl.com>; Mon, 13 Jan 2014 10:20:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsehFaLHZj7Y for <gen-art@ietfa.amsl.com>; Mon, 13 Jan 2014 10:20:55 -0800 (PST)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E22411AE18C for <gen-art@ietf.org>; Mon, 13 Jan 2014 10:20:54 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id wo20so1422619obc.33 for <gen-art@ietf.org>; Mon, 13 Jan 2014 10:20:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=aekz+FfcwuQ/w5ge0YR/rVP3rNH/EO0Qwc7ZBiZrB8E=; b=D8zY8QNCqfeHVSuuHvVs+KKcprSfXDEeAj6+RKbGwILT2JCjsHaL3vExbI9xvLNSp1 gcuXwH0LYH78z9PhxiY4A+eoXwaIjOtQLj/qj7+TWBRq2OVmo5dUYM0PocD6TkDsFuav LyzuA7q0mU4HlA1/bCO3yJolVxXmAxNd25PQJFYzYEXKqf8TVW31qFYEMSYlxxx1dB+b ZcQkhtSjKh9kPyZWFsY3gvRHvvU+FFnDiam4W7AnYUct2oNI5ocT6a4Lx+o4wBpbJk91 KJ/jDSiRdA8YTyXxL8FK6WLWrLe9mnCxMQTIM9tiEIvlmWiy0+sQdsDgfkCDoaX2XejH /0gA==
X-Received: by 10.182.42.105 with SMTP id n9mr21706345obl.33.1389637243690; Mon, 13 Jan 2014 10:20:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 13 Jan 2014 10:20:23 -0800 (PST)
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 13 Jan 2014 13:20:23 -0500
Message-ID: <CAPv4CP99LPczouE0VJkvmtDhZ+xOw0qOo3hongohTABT=WJoZQ@mail.gmail.com>
To: draft-ietf-avtcore-clksrc.all@tools.ietf.org, gen-art <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] GEN-ART LC review of draft-ietf-avtcore-clksrc-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 18:20:57 -0000

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

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

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

Document: draft-ietf-avtcore-clksrc-09
Reviewer: Scott Brim
Review Date: 2014-01-13
IETF LC End Date: 2014-01-16
IESG Telechat date: (if known)

Summary: Ready with a minor issue

Major issues:

Minor issues:

In 6.1.2 and 6.1.3: "If the answerer rejects the offer because the
available reference clocks are incompatible, the rejection MUST
contain at least one timestamp reference clock specification usable by
the answerer." If the answerer suggests a clock that is not among
those offered, what happens next?  The offerer could abort, but could
it start over and use what the answerer suggested? That's not
documented -- is it obvious to those more familiar with SDP?

Scott

From bclaise@cisco.com  Tue Jan 14 09:11:05 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3268E1AE13C for <gen-art@ietfa.amsl.com>; Tue, 14 Jan 2014 09:11:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4EpQOdKxmbzo for <gen-art@ietfa.amsl.com>; Tue, 14 Jan 2014 09:11:03 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id BD19A1AE0F6 for <gen-art@ietf.org>; Tue, 14 Jan 2014 09:11:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3280; q=dns/txt; s=iport; t=1389719451; x=1390929051; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=cAljBL+H7u+qp1SUPaUa0Fu/nRpvbf+McHLdIgh9L5w=; b=VYrETT4hRqhSJ4Jm2mdNRnO9EF7AhF4GvRYnt8w5SzzTUBIPaWjdLKda SqpL5Qf4O/ut2yrRTkPKdK+NJmCQJmMvZfQFPC1oH5BfMENIbnGtVDk0V VcPhxGVowBmonv1oKtp5/6/7FPeBB5GmXQwtP/mKaqSQBY2uneAgfFaud Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkAFAGFv1VKQ/khL/2dsb2JhbABagws4g1S3XoEVFnSCJgEBBCMVQAEQCxICBgIFFgsCAgkDAgECATcOEwEHAQGIAA2of5sSF4Epi26BcAeCb4FIAQOYHoEwhRWLUIMuOw
X-IronPort-AV: E=Sophos;i="4.95,658,1384300800";  d="scan'208";a="3620795"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 14 Jan 2014 17:10:50 +0000
Received: from [10.149.0.203] (dhcp-10-149-0-203.cisco.com [10.149.0.203]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0EHAobj028958; Tue, 14 Jan 2014 17:10:50 GMT
Message-ID: <52D56F9A.2010402@cisco.com>
Date: Tue, 14 Jan 2014 18:10:50 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com>
In-Reply-To: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 17:11:05 -0000

Dear authors, doc. shepherd,

Can you please answer Martin.

Regards, Benoit
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-opsawg-lsn-deployment-04
> Reviewer: Martin Thomson
> Review Date: 2014-01-06
> IETF LC End Date: 2014-01-06
> IESG Telechat date: (if known)
>
> Summary:  This document describes a generic way that MPLS LSPs can be
> deployed to support the deployment of CGNs in a way that addresses a
> range of common requirements.  As a draft, it's still a little rough,
> but it is mostly ready for publication as an Informational RFC.
>
> Major issues: none
>
> Minor issues:
>
> The abstract says this:
>
>    This document does not intend to defend the
>     merits of CGN.
>
> Which seems wise given their somewhat contentious nature.  But then
> the entirely of Section 2 does exactly the opposite.  I don't know
> what the right answer is here, but maybe the right thing to do is
> delete Section 2.
>
> Figures 1 and 2 should probably use different labels for the two CPE
> boxes.  The top one is being translated, the bottom one isn't.
>
> Section 6 is a little too speculative to be valuable.  How about using
> the boilerplate:
>
>        This document has no IANA actions.
>
> I'm not sure what "security measures" might be employed here:
>
>     If a provider plans to operate the pre-translation realm (CPE towards
>     translator IPv4 zone) as a non-public like network, then additional
>     security measures may be needed to secure this environment.
>
> What might be secured in these scenarios?  Confidentiality?  Access to
> network resources?  Perhaps this should talk about what a network
> operator wants to secure: access to the network.  Then maybe talk
> about access control and isolation.
>
> In Section 4, this seems a little vague:
>
>     Various redundancy models
>     can be used within this architecture to support failover from one
>     physical CGN hardware instance to another.
>
> I don't expect an enumeration of the options, but this seems important
> enough to at least point to where the redundancy options might exist?
> Redundant "VPNs"/LSPs?  Redundant paths from the VRF termination?
>
> Nits:
>
> Missing period in Section 9
>
> I found the structure of the first part of Section 3.1 difficult:
>
>     Centralized deployments of CGN (longer proximity to end user and/or
>     higher densities of subscribers/connections to CGN instances) differ
>     from distributed deployments of CGN (closer proximity to end user and
>     /or lower densities of subscribers/connections to CGN instances).
>
> Maybe this could be expanded a little to improve comprehension.
>
> This statement seems redundant:
>
>     Other requirements may be assessed on a operator-by-operator basis,
>     but those listed above may be considered for any given deployment
>     architecture.
>
> As far as it goes, some of the requirements listed might not apply to
> a particular deployment, or part thereof.
> .
>


From suresh.krishnan@ericsson.com  Tue Jan 14 15:19:55 2014
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10EAD1ADFF3 for <gen-art@ietfa.amsl.com>; Tue, 14 Jan 2014 15:19:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KXdMm8g2CMT6 for <gen-art@ietfa.amsl.com>; Tue, 14 Jan 2014 15:19:51 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id C81EB1A1F1F for <gen-art@ietf.org>; Tue, 14 Jan 2014 15:19:51 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-f2-52d5c609b1af
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id D9.BA.23183.906C5D25; Wed, 15 Jan 2014 00:19:37 +0100 (CET)
Received: from [142.133.113.185] (147.117.188.8) by smtps-am.internal.ericsson.com (147.117.188.90) with Microsoft SMTP Server (TLS) id 14.2.347.0; Tue, 14 Jan 2014 18:19:39 -0500
Message-ID: <52D5C5FB.6050801@ericsson.com>
Date: Tue, 14 Jan 2014 18:19:23 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <52AFDFBD.5010307@ericsson.com> <52AFFC87.60707@ericsson.com> <47EB6A3A-03B4-4EAA-A3C0-5E1A2A5B287E@csperkins.org>
In-Reply-To: <47EB6A3A-03B4-4EAA-A3C0-5E1A2A5B287E@csperkins.org>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [147.117.188.8]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBLMWRmVeSWpSXmKPExsUyuXRPlC7nsatBBrf6dCyWvzzBaDH/yhI2 i6uvPrM4MHtMu3+fzWPJkp9MHl8uf2YLYI7isklJzcksSy3St0vgyjh59gh7wROJiq5/O1gb GJtEuhg5OSQETCTObz7NBGGLSVy4t54NxBYSOMIocXu2dRcjF5C9nVGit7eXESTBK6AtsWlt GzuIzSKgKrHqwUpmEJsNaNCGnZ/BBokKhEm0X5jJDFEvKHFy5hMWEFtEIFpi1Y/zQAs4OJgF 8iXaJuuAhIWBylfM6meC2Fsn0XrwJlg5p4CjRM+0u4wQ5fYSD7aWgYSZBeQlmrfOZoYo15TY uuY7K8T5ihIvjv9kmsAoNAvJ4lkI3bOQdC9gZF7FyFFanFqWm25ksIkRGLrHJNh0dzDueWl5 iFGag0VJnPfLW+cgIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYyrfLRzX75VjZXazFbpUrw6 6vWeO/0OOiJuM9VqDKYmX6z7ybJj27qdfZef9JUsm7Tv5ftFH+S3//lRN69+Yvmn+b3njG6v WbUiW6I/+74fUzHjtLI+Ta+viw0/Bv76XLbgdqS3X7vYI2bVMzXbZ9wIWzO/b/ulqFXKAodK /5QWa22TCLQJ++6jxFKckWioxVxUnAgAVl5X7CsCAAA=
Cc: draft-ietf-avtcore-rtp-security-options.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-avtcore-rtp-security-options-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 23:19:55 -0000

Hi Colin,
   Thanks for making the changes. I will look at the next rev when you 
publish it.

Thanks
Suresh

On 01/12/2014 02:33 PM, Colin Perkins wrote:
> Hi,
>
> Thanks, I incorporated changes to address these. For Section 2.1, I changed “protecting the RTP session and its RTP and RTCP traffic and the key-management protocol becomes important in which security statements one can do” to “protecting the RTP session (and hence the RTP and RTCP traffic) and the key-management protocol becomes important to determine what security claims can be made”. Hopefully this is clearer.
>
> Cheers,
> Colin
>
>
> On 17 Dec 2013, at 07:25, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
>> Thanks Suresh,
>>
>> We will take your comment into account when we do the next revision.
>>
>> Cheers
>>
>> Magnus
>>
>> On 2013-12-17 06:23, Suresh Krishnan 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).
>>>
>>> Please wait for direction from your document shepherd or AD before
>>> posting a new version of the draft.
>>>
>>> Document: draft-ietf-avtcore-rtp-security-options-09.txt
>>> Reviewer: Suresh Krishnan
>>> Review Date: 2013/12/16
>>> IESG Telechat date: 2013/12/19
>>>
>>> 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
>>>
>>> This sentence is a bit awkward
>>>
>>> The IETF considers it important that protocols implement, and makes
>>> available to the user, secure modes of operation
>>>
>>> Suggest rewording to something like
>>>
>>> The IETF considers it important that protocols implement secure modes of
>>> operation and make them available to users.
>>>
>>> * Section 2.1
>>>
>>> I am not sure what this statement means. Can you please clarify?
>>>
>>> "Here the combination of the security protocol protecting the RTP
>>> session and its RTP and RTCP traffic and the key-management protocol
>>> becomes important in which security statements one can do."
>>>
>>> * Section 4.1.4
>>>
>>> s/will be more relevant then/will be more relevant than/
>>>
>>> This sentence is hard to read. Please consider rewording
>>>
>>> "Commonly by provisioning the verifier with the public part of a root
>>> certificate, this enables the verifier to verify a trust chain from the
>>> root certificate down to the identity certificate."
>>>
>>>
>>> Thanks
>>> Suresh
>>>
>>>
>>
>>
>> --
>>
>> 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  Wed Jan 15 00:55:51 2014
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA62D1AE33E for <gen-art@ietfa.amsl.com>; Wed, 15 Jan 2014 00:55:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wSKjsHyRltI for <gen-art@ietfa.amsl.com>; Wed, 15 Jan 2014 00:55:49 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 26A3A1AE2E5 for <gen-art@ietf.org>; Wed, 15 Jan 2014 00:55:48 -0800 (PST)
X-AuditID: c1b4fb2d-b7f1c8e000005ceb-76-52d64d08f5d8
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 59.EC.23787.80D46D25; Wed, 15 Jan 2014 09:55:36 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.26) with Microsoft SMTP Server id 14.2.347.0; Wed, 15 Jan 2014 09:55:36 +0100
Message-ID: <52D64CFB.1000805@ericsson.com>
Date: Wed, 15 Jan 2014 09:55:23 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Colin Perkins <csp@csperkins.org>
References: <52AFDFBD.5010307@ericsson.com> <52AFFC87.60707@ericsson.com> <47EB6A3A-03B4-4EAA-A3C0-5E1A2A5B287E@csperkins.org> <52D5C5FB.6050801@ericsson.com>
In-Reply-To: <52D5C5FB.6050801@ericsson.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJLMWRmVeSWpSXmKPExsUyM+JvjS6H77Ugg//dOhbLX55gtJh/ZQmb xdVXn1kcmD2m3b/P5rFkyU8mjy+XP7MFMEdx2aSk5mSWpRbp2yVwZTy88Jqx4KJcxdL2eewN jPcluhg5OSQETCQWzNjOCmGLSVy4t56ti5GLQ0jgEKNEy/SHrBDOckaJ/78WsYFU8QpoS0w7 tBPMZhFQlXi48xFYN5uAhcTNH41gcVGBYIlb0x6wQ9QLSpyc+YQFxBYRCJc4MnMPUD0HB7NA vkTbZB2QsLBAmMSKWf1MILaQwDxGiXnnDEFsTgEdic3T97OBlEsIiEv0NAaBhJkFDCSOLJrD CmHLSzRvnc0M0aot0dDUwTqBUWgWksWzkLTMQtKygJF5FSN7bmJmTnq54SZGYPAe3PJbdwfj qXMihxilOViUxHk/vHUOEhJITyxJzU5NLUgtii8qzUktPsTIxMEp1cDomXx2qV4fp5DXnMqW jZ/VpSc+d0j/uFb7kkn+HJl/Lyu3+MVYab93WLv++fKkaP3YCMn7lmns8/y2it7WWTNFqX6+ TF9BjqPOwuATrTUTdWXnBb5iFZlx6ZK4oseO6N5cR2MneY9ff5aduvAm5zffRrUlizJdj76+ vyZ6T6Xb3vqD2+6aOnEpsRRnJBpqMRcVJwIArL1u4CwCAAA=
Cc: draft-ietf-avtcore-rtp-security-options.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-avtcore-rtp-security-options-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 08:55:51 -0000

On 2014-01-15 00:19, Suresh Krishnan wrote:
> Hi Colin,
>   Thanks for making the changes. I will look at the next rev when you
> publish it.

Thanks,

I will submit the revision now.

Cheers

Magnus

> 
> Thanks
> Suresh
> 
> On 01/12/2014 02:33 PM, Colin Perkins wrote:
>> Hi,
>>
>> Thanks, I incorporated changes to address these. For Section 2.1, I
>> changed “protecting the RTP session and its RTP and RTCP traffic and
>> the key-management protocol becomes important in which security
>> statements one can do” to “protecting the RTP session (and hence the
>> RTP and RTCP traffic) and the key-management protocol becomes
>> important to determine what security claims can be made”. Hopefully
>> this is clearer.
>>
>> Cheers,
>> Colin
>>
>>
>> On 17 Dec 2013, at 07:25, Magnus Westerlund
>> <magnus.westerlund@ericsson.com> wrote:
>>> Thanks Suresh,
>>>
>>> We will take your comment into account when we do the next revision.
>>>
>>> Cheers
>>>
>>> Magnus
>>>
>>> On 2013-12-17 06:23, Suresh Krishnan 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).
>>>>
>>>> Please wait for direction from your document shepherd or AD before
>>>> posting a new version of the draft.
>>>>
>>>> Document: draft-ietf-avtcore-rtp-security-options-09.txt
>>>> Reviewer: Suresh Krishnan
>>>> Review Date: 2013/12/16
>>>> IESG Telechat date: 2013/12/19
>>>>
>>>> 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
>>>>
>>>> This sentence is a bit awkward
>>>>
>>>> The IETF considers it important that protocols implement, and makes
>>>> available to the user, secure modes of operation
>>>>
>>>> Suggest rewording to something like
>>>>
>>>> The IETF considers it important that protocols implement secure
>>>> modes of
>>>> operation and make them available to users.
>>>>
>>>> * Section 2.1
>>>>
>>>> I am not sure what this statement means. Can you please clarify?
>>>>
>>>> "Here the combination of the security protocol protecting the RTP
>>>> session and its RTP and RTCP traffic and the key-management protocol
>>>> becomes important in which security statements one can do."
>>>>
>>>> * Section 4.1.4
>>>>
>>>> s/will be more relevant then/will be more relevant than/
>>>>
>>>> This sentence is hard to read. Please consider rewording
>>>>
>>>> "Commonly by provisioning the verifier with the public part of a root
>>>> certificate, this enables the verifier to verify a trust chain from the
>>>> root certificate down to the identity certificate."
>>>>
>>>>
>>>> Thanks
>>>> Suresh
>>>>
>>>>
>>>
>>>
>>> -- 
>>>
>>> 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
>>> ----------------------------------------------------------------------
>>>
>>
>>
>>
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
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 dromasca@avaya.com  Wed Jan 15 07:11:52 2014
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79F281AE38D; Wed, 15 Jan 2014 07:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.137
X-Spam-Level: 
X-Spam-Status: No, score=-3.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JMqYjjT4AMJY; Wed, 15 Jan 2014 07:11:46 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id EDA0C1AE395; Wed, 15 Jan 2014 07:11:35 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsYYAE6k1lKHCzI1/2dsb2JhbABZgkcjIThWpXkIjCOIW4EVFnSCJwEBAxIbTBIBFQcOViYBBA4NARmHYgEMnWWmQ40OgUAgEYI2D2aBEwSZUIU8iymDLYIq
X-IronPort-AV: E=Sophos;i="4.95,663,1384318800"; d="scan'208,217";a="45074901"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 15 Jan 2014 10:11:21 -0500
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 15 Jan 2014 09:59:27 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0158.001; Wed, 15 Jan 2014 16:11:20 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Review of draft-ietf-dane-registry-acronyms-03
Thread-Index: Ac8SBAXAPosF7k1MRom7f+BaACrMYw==
Date: Wed, 15 Jan 2014 15:11:19 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA243CEC9A@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: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA243CEC9AAZFFEXMB04globa_"
MIME-Version: 1.0
Cc: "draft-ietf-dane-registry-acronyms.all@tools.ietf.org" <draft-ietf-dane-registry-acronyms.all@tools.ietf.org>, "dane@ietf.org" <dane@ietf.org>
Subject: [Gen-art] Gen-ART Review of draft-ietf-dane-registry-acronyms-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 15:11:52 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA243CEC9AAZFFEXMB04globa_
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/GenArtfaq>.



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



Document: http://www.ietf.org/id/draft-ietf-dane-registry-acronyms-03.txt

Reviewer: Dan Romascanu

Review Date: 1/15/2014

IETF LC End Date: 1/23/2014

IESG Telechat date:



Summary:

Ready with issues



Major issues:

None - it's a simple, clear and useful document.



Minor issues:

1.       In Section 2.3 the I-D recommends that the values in reference col=
umn for SHA-256 and SHA-512 refer to [RFC 6698] while the IANA Consideratio=
ns section in RFC 6698 recommends and the registry entries in the TLSA Matc=
hing Types table at http://www.iana.org/assignments/dane-parameters/dane-pa=
rameters.xhtml  point to [RFC 6234].

2.       As this I-D updates the registries with a column for acronyms, it =
seems more accurate that the reference columns of all tables mention both  =
[RFC 6698] and [RFC XXXX] (this RFC)



Nits/editorial comments:

In the Introduction section:

'This document updates the IANA registry definition for TLSA

   record to add a column with acronym for each specified field'

s/acronym/an acronym/










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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
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.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";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.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;}
/* List Definitions */
@list l0
	{mso-list-id:238946756;
	mso-list-type:hybrid;
	mso-list-template-ids:1833483516 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body 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<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&lt;<a href=3D"http://wiki.tools.ietf.org/area/ge=
n/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArt=
faq</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please resolve these comments along with any othe=
r Last Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document: http://www.ietf.org/id/draft-ietf-dane-=
registry-acronyms-03.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 1/15/2014<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 1/23/2014<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary:<o:p></o:p></p>
<p class=3D"MsoPlainText">Ready with issues<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">None &#8211; it&#8217;s a simple, clear and usefu=
l document. <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" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>In Section 2.3 the I-D rec=
ommends that the values in reference column for SHA-256 and SHA-512 refer t=
o [RFC 6698] while the IANA Considerations section in RFC 6698 recommends a=
nd the registry entries in the TLSA
 Matching Types table at <a href=3D"http://www.iana.org/assignments/dane-pa=
rameters/dane-parameters.xhtml">
http://www.iana.org/assignments/dane-parameters/dane-parameters.xhtml</a> &=
nbsp;point to [RFC 6234].<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>As this I-D updates the re=
gistries with a column for acronyms, it seems more accurate that the refere=
nce columns of all tables mention both &nbsp;[RFC 6698] and [RFC XXXX] (thi=
s RFC)<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">In the Introduction section: <o:p></o:p></p>
<pre>&#8216;This document updates the IANA registry definition for TLSA<o:p=
></o:p></pre>
<p class=3D"MsoPlainText"><span style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;">&nbsp;&nbsp; record to add a colu=
mn with acronym for each specified field&#8217;
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;">s/acronym/an acronym/<o:p></o:p><=
/span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:12.0pt;font-family:&quot=
;Times New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA243CEC9AAZFFEXMB04globa_--

From victor@jvknet.com  Wed Jan 15 19:06:41 2014
Return-Path: <victor@jvknet.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 411381AE4B4 for <gen-art@ietfa.amsl.com>; Wed, 15 Jan 2014 19:06:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ikKsjDYpD5l for <gen-art@ietfa.amsl.com>; Wed, 15 Jan 2014 19:06:38 -0800 (PST)
Received: from mail-we0-f170.google.com (mail-we0-f170.google.com [74.125.82.170]) by ietfa.amsl.com (Postfix) with ESMTP id 9F9FC1AE4B3 for <gen-art@ietf.org>; Wed, 15 Jan 2014 19:06:38 -0800 (PST)
Received: by mail-we0-f170.google.com with SMTP id u57so2646755wes.1 for <gen-art@ietf.org>; Wed, 15 Jan 2014 19:06:26 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=X6jsJnCGvQYxNtbyUA4wzi9dih8S9lN6vE6CdmBN5sA=; b=R2qgsZBTJ+iwE+lrEhPSiP/3jmuzjkRRgP2bR6+FzUzZBXyMUeGwnXNCctucURVxs6 tG+6mbioPFvrmsoMajnKRTiApWUgyfpPLdvJ1KWgEChPNc+M+wxg4kiHqtMNtEYWDVIY JUAj0rozmFuWnYDIxaDCfDcwLfA1PzowRZHtaQsrsVHg8sDwHhoFQperZkVIt2ItS+Uf C+b1Unnr7ljvSIgM47ro/MfHMTwIgjSZSVMM63fnNwfE4vCRSAv4eZ3s14GxwyVUAuGl JvLYD/Mz4lgR1vW1p/G3z2pw8rLXskr1F+HJVIcLCWTn9fcV/Qlv7RqGCxFzTyKgUmBi cDEw==
X-Gm-Message-State: ALoCoQl64BT4SvAFdr6GbLnAz0B9JkGiB3nNqBGidFMbOnmzrxekozgF4i7TkYIqOTWG17A3D3tr
MIME-Version: 1.0
X-Received: by 10.180.73.196 with SMTP id n4mr5695821wiv.24.1389841585954; Wed, 15 Jan 2014 19:06:25 -0800 (PST)
Received: by 10.216.89.193 with HTTP; Wed, 15 Jan 2014 19:06:25 -0800 (PST)
In-Reply-To: <52D56F9A.2010402@cisco.com>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com> <52D56F9A.2010402@cisco.com>
Date: Wed, 15 Jan 2014 22:06:25 -0500
Message-ID: <CAJc3aaMmEbTWL69VnDsUwwrb7qPjiZpjk+3NBr63AHovOPtVdA@mail.gmail.com>
From: Victor Kuarsingh <victor@jvknet.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=f46d043d66e1067a3c04f00db619
X-Mailman-Approved-At: Wed, 15 Jan 2014 20:02:13 -0800
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 03:06:41 -0000

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

Benoit/Martin,

I apologize. I seem to have missed reading that email.  I review and replay.

regards,

Victor K


On Tue, Jan 14, 2014 at 12:10 PM, Benoit Claise <bclaise@cisco.com> wrote:

> Dear authors, doc. shepherd,
>
> Can you please answer Martin.
>
> Regards, Benoit
>
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-opsawg-lsn-deployment-04
>> Reviewer: Martin Thomson
>> Review Date: 2014-01-06
>> IETF LC End Date: 2014-01-06
>> IESG Telechat date: (if known)
>>
>> Summary:  This document describes a generic way that MPLS LSPs can be
>> deployed to support the deployment of CGNs in a way that addresses a
>> range of common requirements.  As a draft, it's still a little rough,
>> but it is mostly ready for publication as an Informational RFC.
>>
>> Major issues: none
>>
>> Minor issues:
>>
>> The abstract says this:
>>
>>    This document does not intend to defend the
>>     merits of CGN.
>>
>> Which seems wise given their somewhat contentious nature.  But then
>> the entirely of Section 2 does exactly the opposite.  I don't know
>> what the right answer is here, but maybe the right thing to do is
>> delete Section 2.
>>
>> Figures 1 and 2 should probably use different labels for the two CPE
>> boxes.  The top one is being translated, the bottom one isn't.
>>
>> Section 6 is a little too speculative to be valuable.  How about using
>> the boilerplate:
>>
>>        This document has no IANA actions.
>>
>> I'm not sure what "security measures" might be employed here:
>>
>>     If a provider plans to operate the pre-translation realm (CPE towards
>>     translator IPv4 zone) as a non-public like network, then additional
>>     security measures may be needed to secure this environment.
>>
>> What might be secured in these scenarios?  Confidentiality?  Access to
>> network resources?  Perhaps this should talk about what a network
>> operator wants to secure: access to the network.  Then maybe talk
>> about access control and isolation.
>>
>> In Section 4, this seems a little vague:
>>
>>     Various redundancy models
>>     can be used within this architecture to support failover from one
>>     physical CGN hardware instance to another.
>>
>> I don't expect an enumeration of the options, but this seems important
>> enough to at least point to where the redundancy options might exist?
>> Redundant "VPNs"/LSPs?  Redundant paths from the VRF termination?
>>
>> Nits:
>>
>> Missing period in Section 9
>>
>> I found the structure of the first part of Section 3.1 difficult:
>>
>>     Centralized deployments of CGN (longer proximity to end user and/or
>>     higher densities of subscribers/connections to CGN instances) differ
>>     from distributed deployments of CGN (closer proximity to end user and
>>     /or lower densities of subscribers/connections to CGN instances).
>>
>> Maybe this could be expanded a little to improve comprehension.
>>
>> This statement seems redundant:
>>
>>     Other requirements may be assessed on a operator-by-operator basis,
>>     but those listed above may be considered for any given deployment
>>     architecture.
>>
>> As far as it goes, some of the requirements listed might not apply to
>> a particular deployment, or part thereof.
>> .
>>
>>
>

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

<div dir=3D"ltr">Benoit/Martin,<div><br></div><div>I apologize. I seem to h=
ave missed reading that email. =A0I review and replay.</div><div><br></div>=
<div>regards,</div><div><br></div><div>Victor K</div></div><div class=3D"gm=
ail_extra">
<br><br><div class=3D"gmail_quote">On Tue, Jan 14, 2014 at 12:10 PM, Benoit=
 Claise <span dir=3D"ltr">&lt;<a href=3D"mailto:bclaise@cisco.com" target=
=3D"_blank">bclaise@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
Dear authors, doc. shepherd,<br>
<br>
Can you please answer Martin.<br>
<br>
Regards, Benoit<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I am the assigned Gen-ART reviewer for this draft. For background on<br>
Gen-ART, please see the FAQ at<br>
<br>
&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" tar=
get=3D"_blank">http://wiki.tools.ietf.org/<u></u>area/gen/trac/wiki/GenArtf=
aq</a>&gt;.<br>
<br>
Please resolve these comments along with any other Last Call comments<br>
you may receive.<br>
<br>
Document: draft-ietf-opsawg-lsn-<u></u>deployment-04<br>
Reviewer: Martin Thomson<br>
Review Date: 2014-01-06<br>
IETF LC End Date: 2014-01-06<br>
IESG Telechat date: (if known)<br>
<br>
Summary: =A0This document describes a generic way that MPLS LSPs can be<br>
deployed to support the deployment of CGNs in a way that addresses a<br>
range of common requirements. =A0As a draft, it&#39;s still a little rough,=
<br>
but it is mostly ready for publication as an Informational RFC.<br>
<br>
Major issues: none<br>
<br>
Minor issues:<br>
<br>
The abstract says this:<br>
<br>
=A0 =A0This document does not intend to defend the<br>
=A0 =A0 merits of CGN.<br>
<br>
Which seems wise given their somewhat contentious nature. =A0But then<br>
the entirely of Section 2 does exactly the opposite. =A0I don&#39;t know<br=
>
what the right answer is here, but maybe the right thing to do is<br>
delete Section 2.<br>
<br>
Figures 1 and 2 should probably use different labels for the two CPE<br>
boxes. =A0The top one is being translated, the bottom one isn&#39;t.<br>
<br>
Section 6 is a little too speculative to be valuable. =A0How about using<br=
>
the boilerplate:<br>
<br>
=A0 =A0 =A0 =A0This document has no IANA actions.<br>
<br>
I&#39;m not sure what &quot;security measures&quot; might be employed here:=
<br>
<br>
=A0 =A0 If a provider plans to operate the pre-translation realm (CPE towar=
ds<br>
=A0 =A0 translator IPv4 zone) as a non-public like network, then additional=
<br>
=A0 =A0 security measures may be needed to secure this environment.<br>
<br>
What might be secured in these scenarios? =A0Confidentiality? =A0Access to<=
br>
network resources? =A0Perhaps this should talk about what a network<br>
operator wants to secure: access to the network. =A0Then maybe talk<br>
about access control and isolation.<br>
<br>
In Section 4, this seems a little vague:<br>
<br>
=A0 =A0 Various redundancy models<br>
=A0 =A0 can be used within this architecture to support failover from one<b=
r>
=A0 =A0 physical CGN hardware instance to another.<br>
<br>
I don&#39;t expect an enumeration of the options, but this seems important<=
br>
enough to at least point to where the redundancy options might exist?<br>
Redundant &quot;VPNs&quot;/LSPs? =A0Redundant paths from the VRF terminatio=
n?<br>
<br>
Nits:<br>
<br>
Missing period in Section 9<br>
<br>
I found the structure of the first part of Section 3.1 difficult:<br>
<br>
=A0 =A0 Centralized deployments of CGN (longer proximity to end user and/or=
<br>
=A0 =A0 higher densities of subscribers/connections to CGN instances) diffe=
r<br>
=A0 =A0 from distributed deployments of CGN (closer proximity to end user a=
nd<br>
=A0 =A0 /or lower densities of subscribers/connections to CGN instances).<b=
r>
<br>
Maybe this could be expanded a little to improve comprehension.<br>
<br>
This statement seems redundant:<br>
<br>
=A0 =A0 Other requirements may be assessed on a operator-by-operator basis,=
<br>
=A0 =A0 but those listed above may be considered for any given deployment<b=
r>
=A0 =A0 architecture.<br>
<br>
As far as it goes, some of the requirements listed might not apply to<br>
a particular deployment, or part thereof.<br>
.<br>
<br>
</blockquote>
<br>
</blockquote></div><br></div>

--f46d043d66e1067a3c04f00db619--

From victor@jvknet.com  Wed Jan 15 19:40:36 2014
Return-Path: <victor@jvknet.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 027521AE1C9 for <gen-art@ietfa.amsl.com>; Wed, 15 Jan 2014 19:40:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bkjoonom3cGP for <gen-art@ietfa.amsl.com>; Wed, 15 Jan 2014 19:40:33 -0800 (PST)
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by ietfa.amsl.com (Postfix) with ESMTP id C528D1AE1B4 for <gen-art@ietf.org>; Wed, 15 Jan 2014 19:40:32 -0800 (PST)
Received: by mail-wi0-f173.google.com with SMTP id d13so4666304wiw.12 for <gen-art@ietf.org>; Wed, 15 Jan 2014 19:40:20 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=9TcYj5lVpjOxmjYngbGhAUFUKxmnkEwpjoZW5jDh4rQ=; b=Hd0IGr8tM6WjEl3+uj/U2kVOHF2S5JoClwUqEcMgq95bwx6DVFVKQkLUVLPa8K5k78 40ps5NRn2e33HYtPQ3IGlnoTmF8ikScZsLzPB0E8mLWeuq/BCfXVWpLjzzyaYrwknESe v4fy2A8hR8DTxe8C0sUIPuPwSrxXC9NQZ3TaelWcA+4+QM/m4PvY+kDCVd3Hv4n9fO86 czqBJWlqYAQzSJJCsHg+MlcZtadTIQ7/3kHG96nVKqqaksC77pFDVeJZoKM32Ek+X7JB g2gnQL1FYIXptuvywgN5wlao4DiKqGYyzKDxl+GYwl1aAvJI9W7nb84LdLq5MFZQDIBc AiGg==
X-Gm-Message-State: ALoCoQkosEmwXxAwHijglNf9MVltUoLkDuyuZ9Jt7cN9H6JJ7d6XStu8x5AqQO2XWPYrGh4xKDh+
MIME-Version: 1.0
X-Received: by 10.194.48.74 with SMTP id j10mr5855426wjn.41.1389843620301; Wed, 15 Jan 2014 19:40:20 -0800 (PST)
Received: by 10.216.89.193 with HTTP; Wed, 15 Jan 2014 19:40:20 -0800 (PST)
In-Reply-To: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com>
Date: Wed, 15 Jan 2014 22:40:20 -0500
Message-ID: <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com>
From: Victor Kuarsingh <victor@jvknet.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=047d7ba975c84826ef04f00e2fb0
X-Mailman-Approved-At: Wed, 15 Jan 2014 20:02:13 -0800
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 03:40:36 -0000

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

Martin,

My responses in-line


On Mon, Jan 6, 2014 at 1:44 PM, Martin Thomson <martin.thomson@gmail.com>wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-opsawg-lsn-deployment-04
> Reviewer: Martin Thomson
> Review Date: 2014-01-06
> IETF LC End Date: 2014-01-06
> IESG Telechat date: (if known)
>
> Summary:  This document describes a generic way that MPLS LSPs can be
> deployed to support the deployment of CGNs in a way that addresses a
> range of common requirements.  As a draft, it's still a little rough,
> but it is mostly ready for publication as an Informational RFC.
>
> Major issues: none
>
> Minor issues:
>
> The abstract says this:
>
>   This document does not intend to defend the
>    merits of CGN.
>
> Which seems wise given their somewhat contentious nature.  But then
> the entirely of Section 2 does exactly the opposite.  I don't know
> what the right answer is here, but maybe the right thing to do is
> delete Section 2.
>

[VK]  The intention of this section was to explain that CGN may be used by
operators and discuss some of the factors that may go (or have gone) into
that decision.  The point in the abstract was intended to tell the reader
that the authors were not suggesting that CGN was "good" or "needed".

There are some important points that I think are important within the
section (section 2), so perhaps if I/we can remove specific text that seems
to given the impression that we are defending CGN, I can do so.


>
> Figures 1 and 2 should probably use different labels for the two CPE
> boxes.  The top one is being translated, the bottom one isn't.
>

[VK]  Yes, that makes sense.  I can make that update.  Thanks for the
suggestion


>
> Section 6 is a little too speculative to be valuable.  How about using
> the boilerplate:
>
>       This document has no IANA actions.
>

[VK]  I am ok with that.   Noted.


>
> I'm not sure what "security measures" might be employed here:
>
>    If a provider plans to operate the pre-translation realm (CPE towards
>    translator IPv4 zone) as a non-public like network, then additional
>    security measures may be needed to secure this environment.
>
> What might be secured in these scenarios?  Confidentiality?  Access to
> network resources?  Perhaps this should talk about what a network
> operator wants to secure: access to the network.  Then maybe talk
> about access control and isolation.
>

[VK]  The point here was that the document/authors have assumed the
position that the CGN realm (within the context of this document) is that
it's publicly accessible (to the extent that it can be behind a translation
function.   The point was that if an operator wanted something more secure
(which can be a number of thinks include items you listed like access
to/from the Internet etc) that those would require mode consideration.

We did not itemize those considerations as any list I generate would be
somewhat arbitrary (should I select a few examples).  If you feel that such
a partial listing is material, I can do so.  My concern here is that once
we put in such a list, we may have to deal with conversations like "why did
you not include such and such .. etc"

The overall expectation is that the operator should expect the same level
of exposure as traditional customers.


>
> In Section 4, this seems a little vague:
>
>    Various redundancy models
>    can be used within this architecture to support failover from one
>    physical CGN hardware instance to another.
>
> I don't expect an enumeration of the options, but this seems important
> enough to at least point to where the redundancy options might exist?
> Redundant "VPNs"/LSPs?  Redundant paths from the VRF termination?
>

[VK] Our expectation was that the operator would be able to derive their
own answers on how to enable redundancy in their model.  The expectation is
that the reader already would understand (or would need to verse
themselves) CGN and MPLS/VPNs.  Therefore they would be able to enumerate
the options on their own.

We were trying to keep the text simple and show the basic association of
how to deploy the CGN using MPLS/VPNs.  I would not want to sound
prescriptive on how to actually design a specific instance.

In disclosure, when I did my design, I did use multiple RD/RTs and imported
those routes into a common CPE VPN.  But that specific option may not be
used by others. I would expect an operator who has already deployed
MPLS/VPNs to have a redundancy model already in place, and they would
evolve that for this purpose.

To exemplify that point, I had discussions with two other Canadian ISPs who
tested/integrated CGNs using this method (MPLS/VPNs) and one did not put in
network based redundancy (just had to CGN functions at a common
endpoint/VRF) and the other did have redundancy but only employed a single
RD/RT (and just had multiple defaults).  Each of us (three) chose
redundancy models which matched our pre-existing MPLS network designs.  I
would expect the same from others as well (although this may be a poor
assumption).



> Nits:
>
> Missing period in Section 9
>
> I found the structure of the first part of Section 3.1 difficult:
>
>    Centralized deployments of CGN (longer proximity to end user and/or
>    higher densities of subscribers/connections to CGN instances) differ
>    from distributed deployments of CGN (closer proximity to end user and
>    /or lower densities of subscribers/connections to CGN instances).
>
> Maybe this could be expanded a little to improve comprehension.
>
> This statement seems redundant:
>
>    Other requirements may be assessed on a operator-by-operator basis,
>    but those listed above may be considered for any given deployment
>    architecture.
>
> As far as it goes, some of the requirements listed might not apply to
> a particular deployment, or part thereof.
>

[VK]  I will make adjustments as specified.  I appreciate the text.

[VK]  I hope my responses are adequate.  Once again, I appreciate your
review of the draft.

regards,

Victor K

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

<div dir=3D"ltr">Martin,<div><br></div><div>My responses in-line</div><div>=
<div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Jan 6, 2014 at 1:44 PM, Martin Thomson <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson@=
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">I am the assigned Gen-ART reviewer for this =
draft. For background on<br>
Gen-ART, please see the FAQ at<br>
<br>
&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" tar=
get=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&=
gt;.<br>
<br>
Please resolve these comments along with any other Last Call comments<br>
you may receive.<br>
<br>
Document: draft-ietf-opsawg-lsn-deployment-04<br>
Reviewer: Martin Thomson<br>
Review Date: 2014-01-06<br>
IETF LC End Date: 2014-01-06<br>
IESG Telechat date: (if known)<br>
<br>
Summary: =A0This document describes a generic way that MPLS LSPs can be<br>
deployed to support the deployment of CGNs in a way that addresses a<br>
range of common requirements. =A0As a draft, it&#39;s still a little rough,=
<br>
but it is mostly ready for publication as an Informational RFC.<br>
<br>
Major issues: none<br>
<br>
Minor issues:<br>
<br>
The abstract says this:<br>
<br>
=A0 This document does not intend to defend the<br>
=A0 =A0merits of CGN.<br>
<br>
Which seems wise given their somewhat contentious nature. =A0But then<br>
the entirely of Section 2 does exactly the opposite. =A0I don&#39;t know<br=
>
what the right answer is here, but maybe the right thing to do is<br>
delete Section 2.<br></blockquote><div><br></div><div>[VK] =A0The intention=
 of this section was to explain that CGN may be used by operators and discu=
ss some of the factors that may go (or have gone) into that decision. =A0Th=
e point in the abstract was intended to tell the reader that the authors we=
re not suggesting that CGN was &quot;good&quot; or &quot;needed&quot;. =A0<=
/div>

<div><br></div><div>There are some important points that I think are import=
ant within the section (section 2), so perhaps if I/we can remove specific =
text that seems to given the impression that we are defending CGN, I can do=
 so.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<br>
Figures 1 and 2 should probably use different labels for the two CPE<br>
boxes. =A0The top one is being translated, the bottom one isn&#39;t.<br></b=
lockquote><div><br></div><div>[VK] =A0Yes, that makes sense. =A0I can make =
that update. =A0Thanks for the suggestion</div><div>=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">


<br>
Section 6 is a little too speculative to be valuable. =A0How about using<br=
>
the boilerplate:<br>
<br>
=A0 =A0 =A0 This document has no IANA actions.<br></blockquote><div><br></d=
iv><div>[VK] =A0I am ok with that. =A0 Noted.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<br>
I&#39;m not sure what &quot;security measures&quot; might be employed here:=
<br>
<br>
=A0 =A0If a provider plans to operate the pre-translation realm (CPE toward=
s<br>
=A0 =A0translator IPv4 zone) as a non-public like network, then additional<=
br>
=A0 =A0security measures may be needed to secure this environment.<br>
<br>
What might be secured in these scenarios? =A0Confidentiality? =A0Access to<=
br>
network resources? =A0Perhaps this should talk about what a network<br>
operator wants to secure: access to the network. =A0Then maybe talk<br>
about access control and isolation.<br></blockquote><div><br></div><div>[VK=
] =A0The point here was that the document/authors have assumed the position=
 that the CGN realm (within the context of this document) is that it&#39;s =
publicly accessible (to the extent that it can be behind a translation func=
tion. =A0 The point was that if an operator wanted something more secure (w=
hich can be a number of thinks include items you listed like access to/from=
 the Internet etc) that those would require mode consideration.</div>
<div><br></div><div>We did not itemize those considerations as any list I g=
enerate would be somewhat arbitrary (should I select a few examples). =A0If=
 you feel that such a partial listing is material, I can do so. =A0My conce=
rn here is that once we put in such a list, we may have to deal with conver=
sations like &quot;why did you not include such and such .. etc&quot;</div>
<div><br></div><div>The overall expectation is that the operator should exp=
ect the same level of exposure as traditional customers.</div><div>=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">

<br>
In Section 4, this seems a little vague:<br>
<br>
=A0 =A0Various redundancy models<br>
=A0 =A0can be used within this architecture to support failover from one<br=
>
=A0 =A0physical CGN hardware instance to another.<br>
<br>
I don&#39;t expect an enumeration of the options, but this seems important<=
br>
enough to at least point to where the redundancy options might exist?<br>
Redundant &quot;VPNs&quot;/LSPs? =A0Redundant paths from the VRF terminatio=
n?<br></blockquote><div><br></div><div>[VK] Our expectation was that the op=
erator would be able to derive their own answers on how to enable redundanc=
y in their model. =A0The expectation is that the reader already would under=
stand (or would need to verse themselves) CGN and MPLS/VPNs. =A0Therefore t=
hey would be able to enumerate the options on their own. =A0</div>
<div><br></div><div>We were trying to keep the text simple and show the bas=
ic association of how to deploy the CGN using MPLS/VPNs. =A0I would not wan=
t to sound prescriptive on how to actually design a specific instance. =A0<=
/div>
<div><br></div><div>In disclosure, when I did my design, I did use multiple=
 RD/RTs and imported those routes into a common CPE VPN. =A0But that specif=
ic option may not be used by others. I would expect an operator who has alr=
eady deployed MPLS/VPNs to have a redundancy model already in place, and th=
ey would evolve that for this purpose.</div>
<div><br></div><div>To exemplify that point, I had discussions with two oth=
er Canadian ISPs who tested/integrated CGNs using this method (MPLS/VPNs) a=
nd one did not put in network based redundancy (just had to CGN functions a=
t a common endpoint/VRF) and the other did have redundancy but only employe=
d a single RD/RT (and just had multiple defaults). =A0Each of us (three) ch=
ose redundancy models which matched our pre-existing MPLS network designs. =
=A0I would expect the same from others as well (although this may be a poor=
 assumption).</div>
<div>=A0<br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Nits:<br>
<br>
Missing period in Section 9<br>
<br>
I found the structure of the first part of Section 3.1 difficult:<br>
<br>
=A0 =A0Centralized deployments of CGN (longer proximity to end user and/or<=
br>
=A0 =A0higher densities of subscribers/connections to CGN instances) differ=
<br>
=A0 =A0from distributed deployments of CGN (closer proximity to end user an=
d<br>
=A0 =A0/or lower densities of subscribers/connections to CGN instances).<br=
>
<br>
Maybe this could be expanded a little to improve comprehension.<br>
<br>
This statement seems redundant:<br>
<br>
=A0 =A0Other requirements may be assessed on a operator-by-operator basis,<=
br>
=A0 =A0but those listed above may be considered for any given deployment<br=
>
=A0 =A0architecture.<br>
<br>
As far as it goes, some of the requirements listed might not apply to<br>
a particular deployment, or part thereof.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">[VK] =A0I will make=
 adjustments as specified. =A0I appreciate the text.</div><div class=3D"gma=
il_extra"><br></div><div class=3D"gmail_extra">[VK] =A0I hope my responses =
are adequate. =A0Once again, I appreciate your review of the draft.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">regards,</d=
iv><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Victor K=
</div><div class=3D"gmail_extra"><br></div></div>

--047d7ba975c84826ef04f00e2fb0--

From aidan.williams@audinate.com  Wed Jan 15 20:58:17 2014
Return-Path: <aidan.williams@audinate.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A81031AE2B3 for <gen-art@ietfa.amsl.com>; Wed, 15 Jan 2014 20:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BKs5xHTKWaKj for <gen-art@ietfa.amsl.com>; Wed, 15 Jan 2014 20:58:16 -0800 (PST)
Received: from zimbra8.audinate.com (sydney.audinate.com [150.101.200.21]) by ietfa.amsl.com (Postfix) with ESMTP id B63EC1AE2B0 for <gen-art@ietf.org>; Wed, 15 Jan 2014 20:58:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by zimbra8.audinate.com (Postfix) with ESMTP id 003353A8BA5; Thu, 16 Jan 2014 15:58:02 +1100 (EST)
Received: from zimbra8.audinate.com ([127.0.0.1]) by localhost (zimbra8.audinate.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id HzchASx4hbuq; Thu, 16 Jan 2014 15:58:00 +1100 (EST)
Received: from localhost (localhost [127.0.0.1]) by zimbra8.audinate.com (Postfix) with ESMTP id 35C203A8B9F; Thu, 16 Jan 2014 15:58:00 +1100 (EST)
X-Virus-Scanned: amavisd-new at audinate.com
Received: from zimbra8.audinate.com ([127.0.0.1]) by localhost (zimbra8.audinate.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id k6TH9oesxbrb; Thu, 16 Jan 2014 15:58:00 +1100 (EST)
Received: from zimbra8.audinate.com (zimbra8.audinate.com [10.12.0.4]) by zimbra8.audinate.com (Postfix) with ESMTP id 0C13F3A8B9A; Thu, 16 Jan 2014 15:58:00 +1100 (EST)
Date: Thu, 16 Jan 2014 15:57:59 +1100 (EST)
From: Aidan Williams <aidan.williams@audinate.com>
To: Scott Brim <scott.brim@gmail.com>
Message-ID: <4950007.112.1389848276062.JavaMail.aidan@praxis.audinate.com>
In-Reply-To: <CAPv4CP99LPczouE0VJkvmtDhZ+xOw0qOo3hongohTABT=WJoZQ@mail.gmail.com>
References: <CAPv4CP99LPczouE0VJkvmtDhZ+xOw0qOo3hongohTABT=WJoZQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_111_2421995.1389848276061"
X-Mailer: Zimbra 8.0.5_GA_5839 (Zimbra Desktop/7.2.2_11951_Mac)
Thread-Topic: GEN-ART LC review of draft-ietf-avtcore-clksrc-09
Thread-Index: wa/izlXLEyBb1ufyD4uFgwNgwbk3ow==
X-Mailman-Approved-At: Thu, 16 Jan 2014 04:42:01 -0800
Cc: draft-ietf-avtcore-clksrc all <draft-ietf-avtcore-clksrc.all@tools.ietf.org>, gen-art <gen-art@ietf.org>
Subject: Re: [Gen-art] GEN-ART LC review of draft-ietf-avtcore-clksrc-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 04:58:17 -0000

------=_Part_111_2421995.1389848276061
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi Scott, 

Thanks for the review. 

The model described in the draft is declarative and it is expected that the receiver will choose to adapt in the event that shared clocks are not available, or reject the offer. The SDP is expected to be used SIP offer/answer and also with protocols similar to SAP. The sender declares the set of reference and/or media clocks is using and the receiver signals back if there is an acceptable match. The receiver may choose to receive the stream even if some or all the clocks are not in fact shared (e.g. by receiving media without time synchronisation (section 6) or by using rate conversation for the media). 

If the senders' offer is rejected, that would mean that either the clocks are not shared, or the receiver is not prepared to adapt. In this case there is little prospect that the sender could usefully start over with a different set of reference and/or media clocks. 

I trust the above comments are clarifying. We kicked the offer/answer text around the WG a few times and I believe the text is comprehensible to those familiar with SDP. 

regards 
aidan 
____ 
:wq! 

----- Original Message -----

> From: "Scott Brim" <scott.brim@gmail.com>
> To: "draft-ietf-avtcore-clksrc all"
> <draft-ietf-avtcore-clksrc.all@tools.ietf.org>, "gen-art"
> <gen-art@ietf.org>
> Sent: Tuesday, 14 January, 2014 5:20:23 AM
> Subject: GEN-ART LC review of draft-ietf-avtcore-clksrc-09

> 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-avtcore-clksrc-09
> Reviewer: Scott Brim
> Review Date: 2014-01-13
> IETF LC End Date: 2014-01-16
> IESG Telechat date: (if known)

> Summary: Ready with a minor issue

> Major issues:

> Minor issues:

> In 6.1.2 and 6.1.3: "If the answerer rejects the offer because the
> available reference clocks are incompatible, the rejection MUST
> contain at least one timestamp reference clock specification usable
> by
> the answerer." If the answerer suggests a clock that is not among
> those offered, what happens next? The offerer could abort, but could
> it start over and use what the answerer suggested? That's not
> documented -- is it obvious to those more familiar with SDP?

> Scott

------=_Part_111_2421995.1389848276061
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D'text/css'>p { margin: 0; }</style></head><body><=
div style=3D'font-family: verdana,helvetica,sans-serif; font-size: 10pt; co=
lor: #000000'>Hi Scott,<br><br>Thanks for the review.<br><br>The model desc=
ribed in the draft is declarative and it is expected that the receiver will=
 choose to adapt in the event that shared clocks are not available, or reje=
ct the offer.&nbsp; The SDP is expected to be used SIP offer/answer and als=
o with protocols similar to SAP.&nbsp; The sender declares the set of refer=
ence and/or media clocks is using and the receiver signals back if there is=
 an acceptable match.&nbsp; The receiver may choose to receive the stream e=
ven if some or all the clocks are not in fact shared (e.g. by receiving med=
ia without time synchronisation (section 6) or by using rate conversation f=
or the media).<br><br>If the senders' offer is rejected, that would mean th=
at either the clocks are not shared, or the receiver is not prepared to ada=
pt.&nbsp; In this case there is little prospect that the sender could usefu=
lly start over with a different set of reference and/or media clocks.<br><b=
r>I trust the above comments are clarifying.&nbsp; We kicked the offer/answ=
er text around the WG a few times and I believe the text is comprehensible =
to those familiar with SDP.<br><br>regards<br><span style=3D"white-space: p=
re;">=09</span>aidan<br>____<br>:wq!<br><br><br><hr id=3D"zwchr"><blockquot=
e style=3D"border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; paddi=
ng-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal;=
 text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size:=
 12pt;"><b>From: </b>"Scott Brim" &lt;scott.brim@gmail.com&gt;<br><b>To: </=
b>"draft-ietf-avtcore-clksrc all" &lt;draft-ietf-avtcore-clksrc.all@tools.i=
etf.org&gt;, "gen-art" &lt;gen-art@ietf.org&gt;<br><b>Sent: </b>Tuesday, 14=
 January, 2014 5:20:23 AM<br><b>Subject: </b>GEN-ART LC review of draft-iet=
f-avtcore-clksrc-09<br><br>I am the assigned Gen-ART reviewer for this draf=
t. For background on<br>Gen-ART, please see the FAQ at<br><br>&lt;http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.<br><br>Please resolve t=
hese comments along with any other Last Call comments<br>you may receive.<b=
r><br>Document: draft-ietf-avtcore-clksrc-09<br>Reviewer: Scott Brim<br>Rev=
iew Date: 2014-01-13<br>IETF LC End Date: 2014-01-16<br>IESG Telechat date:=
 (if known)<br><br>Summary: Ready with a minor issue<br><br>Major issues:<b=
r><br>Minor issues:<br><br>In 6.1.2 and 6.1.3: "If the answerer rejects the=
 offer because the<br>available reference clocks are incompatible, the reje=
ction MUST<br>contain at least one timestamp reference clock specification =
usable by<br>the answerer." If the answerer suggests a clock that is not am=
ong<br>those offered, what happens next? &nbsp;The offerer could abort, but=
 could<br>it start over and use what the answerer suggested? That's not<br>=
documented -- is it obvious to those more familiar with SDP?<br><br>Scott<b=
r></blockquote><br></div></body></html>
------=_Part_111_2421995.1389848276061--

From martin.thomson@gmail.com  Thu Jan 16 10:33:16 2014
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 961C91A1F54 for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 10:33:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZAZpHh2zu3mY for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 10:33:14 -0800 (PST)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id 155811A1F3D for <gen-art@ietf.org>; Thu, 16 Jan 2014 10:33:13 -0800 (PST)
Received: by mail-wi0-f182.google.com with SMTP id ex4so4105609wid.9 for <gen-art@ietf.org>; Thu, 16 Jan 2014 10:33:01 -0800 (PST)
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=GgT3lMcbV6+99jGq0FrxtMu/GhGbO1VsTsjwAXpGUb8=; b=lqDo4+RgMCY81QM9Jrwg+wYXGKmNAi5yWY4fFARcw6aIp3GTA5Br7osfCGP4YoVVFH CPkmAJCFwIcRRPdwnPI6CUUVED1l6Rim+LuAirVK+1rsTfTR0OlUErvrfljpO3gwU+B+ rjM4d8/Huke7VONfxVwOlfnM9JV66/mUSROD1YUi2YZu3yN4VKlWJCZkRT7NAEGc6+X0 m7B0XfGQ9rcbpeau9DcEHXvB2DoVVUO3hyoZYtWc7ZSQO8zGhCdNj8z85B5VZ5ry9PmG ldk87Lj8dFaJv3wFWjnQ312NWg6w7h5mx4lEe3fJfneqK07c+NXu0EFXnJj0qlmRr6pJ dAQg==
MIME-Version: 1.0
X-Received: by 10.195.13.130 with SMTP id ey2mr9922389wjd.7.1389897181511; Thu, 16 Jan 2014 10:33:01 -0800 (PST)
Received: by 10.227.105.132 with HTTP; Thu, 16 Jan 2014 10:33:01 -0800 (PST)
In-Reply-To: <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com> <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com>
Date: Thu, 16 Jan 2014 10:33:01 -0800
Message-ID: <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Victor Kuarsingh <victor@jvknet.com>
Content-Type: text/plain; charset=UTF-8
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 18:33:16 -0000

On 15 January 2014 19:40, Victor Kuarsingh <victor@jvknet.com> wrote:
>> Which seems wise given their somewhat contentious nature.  But then
>> the entirely of Section 2 does exactly the opposite.  I don't know
>> what the right answer is here, but maybe the right thing to do is
>> delete Section 2.
>
>
> [VK]  The intention of this section was to explain that CGN may be used by
> operators and discuss some of the factors that may go (or have gone) into
> that decision.  The point in the abstract was intended to tell the reader
> that the authors were not suggesting that CGN was "good" or "needed".
>
> There are some important points that I think are important within the
> section (section 2), so perhaps if I/we can remove specific text that seems
> to given the impression that we are defending CGN, I can do so.

I'd like to understand what you think is important here.  Much of the
text explaining why CGN is used basically amounts to justification for
it.

In contrast, the list of requirements you provide is fairly neutral
and seems to cover most of the reasons well enough for me at least.

>> I'm not sure what "security measures" might be employed here:
>>
>>    If a provider plans to operate the pre-translation realm (CPE towards
>>    translator IPv4 zone) as a non-public like network, then additional
>>    security measures may be needed to secure this environment.
>>
>> What might be secured in these scenarios?  Confidentiality?  Access to
>> network resources?  Perhaps this should talk about what a network
>> operator wants to secure: access to the network.  Then maybe talk
>> about access control and isolation.
>
>
> [VK]  The point here was that the document/authors have assumed the position
> that the CGN realm (within the context of this document) is that it's
> publicly accessible (to the extent that it can be behind a translation
> function.   The point was that if an operator wanted something more secure
> (which can be a number of thinks include items you listed like access
> to/from the Internet etc) that those would require mode consideration.
>
> We did not itemize those considerations as any list I generate would be
> somewhat arbitrary (should I select a few examples).  If you feel that such
> a partial listing is material, I can do so.  My concern here is that once we
> put in such a list, we may have to deal with conversations like "why did you
> not include such and such .. etc"
>
> The overall expectation is that the operator should expect the same level of
> exposure as traditional customers.

The problem with the text as it stands is that it is vague to the
point that it actively encourages the sorts of questions I raised.

If you want to avoid the questions, maybe consider whether the
sentence is even needed.

>> In Section 4, this seems a little vague:
>>
>>    Various redundancy models
>>    can be used within this architecture to support failover from one
>>    physical CGN hardware instance to another.
>>
>> I don't expect an enumeration of the options, but this seems important
>> enough to at least point to where the redundancy options might exist?
>> Redundant "VPNs"/LSPs?  Redundant paths from the VRF termination?
>
>
> [VK] Our expectation was that the operator would be able to derive their own
> answers on how to enable redundancy in their model.  The expectation is that
> the reader already would understand (or would need to verse themselves) CGN
> and MPLS/VPNs.  Therefore they would be able to enumerate the options on
> their own.
>
> We were trying to keep the text simple and show the basic association of how
> to deploy the CGN using MPLS/VPNs.  I would not want to sound prescriptive
> on how to actually design a specific instance.
>
> In disclosure, when I did my design, I did use multiple RD/RTs and imported
> those routes into a common CPE VPN.  But that specific option may not be
> used by others. I would expect an operator who has already deployed
> MPLS/VPNs to have a redundancy model already in place, and they would evolve
> that for this purpose.
>
> To exemplify that point, I had discussions with two other Canadian ISPs who
> tested/integrated CGNs using this method (MPLS/VPNs) and one did not put in
> network based redundancy (just had to CGN functions at a common
> endpoint/VRF) and the other did have redundancy but only employed a single
> RD/RT (and just had multiple defaults).  Each of us (three) chose redundancy
> models which matched our pre-existing MPLS network designs.  I would expect
> the same from others as well (although this may be a poor assumption).

I don't think that you have to enumerate, though it is perhaps the
wording that is the problem here.  As phrased it implies a panoply of
wonderful options that are being purposefully withheld from the
reader.  Perhaps a rephrasing will make this intent clearer:

The described architecture does not prescribe a single redundancy
model that ensures network availability as a result of CGN failure.
Deployments are able to select a redundancy model that fits best with
their network design.

From rjsparks@nostrum.com  Thu Jan 16 10:58:32 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABD331A1F79; Thu, 16 Jan 2014 10:58:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mt6NNQ3jn7HH; Thu, 16 Jan 2014 10:58:31 -0800 (PST)
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 54DDB1A1F72; Thu, 16 Jan 2014 10:58:31 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0GIwIaw001256 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Thu, 16 Jan 2014 12:58:19 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52D82BAA.1010007@nostrum.com>
Date: Thu, 16 Jan 2014 12:57:46 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, mpls@ietf.org, draft-ietf-mpls-moving-iana-registries@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.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] Gen-Art LC review of draft-ietf-mpls-moving-iana-registries
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 18:58:32 -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-moving-iana-registries
Reviewer: Robert Sparks
Review Date: 16-Jan-2014
IETF LC End Date: 17-Jan-2014
IESG Telechat date: 23-Jan-2014

Summary: This document is ready for publication as Proposed Standard



From rjsparks@nostrum.com  Thu Jan 16 11:11:19 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D72561AC43F for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 11:11:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OeTl4vzKcbZZ for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 11:11:19 -0800 (PST)
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 CE2DA1AC441 for <gen-art@ietf.org>; Thu, 16 Jan 2014 11:11:17 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0GJB53p001904 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Thu, 16 Jan 2014 13:11:05 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52D82EA9.1000202@nostrum.com>
Date: Thu, 16 Jan 2014 13:10:33 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, draft-crocker-id-adoption@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.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] Gen-art LC review of draft-crocker-id-adoption-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 19:11:20 -0000

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

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

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

Document: draft-crocker-id-adoption-05
Reviewer: Robert Sparks
Review Date: 16-Jan-2014
IETF LC End Date: 31-Jan-2014
IESG Telechat date: 6-Feb-2014

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



From scott.brim@gmail.com  Thu Jan 16 12:23:07 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97DC31ACCDC for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 12:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uRR86KIHQeE5 for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 12:23:06 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 54DCB1ACCDA for <gen-art@ietf.org>; Thu, 16 Jan 2014 12:23:06 -0800 (PST)
Received: by mail-ob0-f173.google.com with SMTP id vb8so3340090obc.18 for <gen-art@ietf.org>; Thu, 16 Jan 2014 12:22:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=sIhUnxMsnDhXZrARnonwjgg6GzMMZLpgUgttRHcJ5hw=; b=G8sdTLd3+L+VxXPskTjL6uIclq3e3ayrGVPTNBz70lIyGM4MxYfhqH57++MWO37859 2Zzn58tSQJZitu8Q5Ze5nEdJrOGZ8Pf9wSG0i+STvZ3eAO2g7U1tYB+KFLOx+hPQHKJr Y3b5qFc5WHH/m2qrELwu0YcosRut4mYiR+yFDGY5MxeME8FDMFBZyQsyPSB64vqegJ0Z 4r8ueWiXIW3uiAhD46vhrmzZ6PpZkdviEENrUs534dKaU3oX4Ra6wc2zpx8nw925sVGm EDzIH94igeYWCz6czUDSfn0fKg25y1Ose2RCd8WnVxmxuB7SiAQK0/2nPXbb0jCUk2nK KaZg==
X-Received: by 10.60.174.167 with SMTP id bt7mr8865852oec.54.1389903773859; Thu, 16 Jan 2014 12:22:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Thu, 16 Jan 2014 12:22:33 -0800 (PST)
In-Reply-To: <4950007.112.1389848276062.JavaMail.aidan@praxis.audinate.com>
References: <CAPv4CP99LPczouE0VJkvmtDhZ+xOw0qOo3hongohTABT=WJoZQ@mail.gmail.com> <4950007.112.1389848276062.JavaMail.aidan@praxis.audinate.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 16 Jan 2014 15:22:33 -0500
Message-ID: <CAPv4CP-T1yrLTnyKJJ_mkzYVtCh+8j3T98ApX0cvU4zkeFHjFA@mail.gmail.com>
To: Aidan Williams <aidan.williams@audinate.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-ietf-avtcore-clksrc all <draft-ietf-avtcore-clksrc.all@tools.ietf.org>, gen-art <gen-art@ietf.org>
Subject: Re: [Gen-art] GEN-ART LC review of draft-ietf-avtcore-clksrc-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 20:23:07 -0000

On Wed, Jan 15, 2014 at 11:57 PM, Aidan Williams
<aidan.williams@audinate.com> wrote:
>
> Hi Scott,


Hi Aidan. Let me try to be clearer. My problem is with the sentence:
"If the answerer rejects the offer because the available reference
clocks are incompatible, the rejection MUST
contain at least one timestamp reference clock specification usable by
the answerer."

"If the answerer rejects the offer because the available reference
clocks are incompatible, ..."

As you say, in this case there is little prospect that the sender
could usefully start over. Therefore why would the answerer include,
in the rejection, a clock that is usable by him (the answerer)?

"... the rejection MUST contain at least one timestamp reference clock
specification usable by the answerer."

Either there's no point in the rejection including a reference clock,
or there is.  If there is no point, why do you say a reference clock
MUST be included?  If there is a point, that means there is some
expectation that the sender might do something with the reference
clock in the rejection. What is that expectation? It would be good to
document it.

Is that clearer?

Thanks ... Scott

From ogud@ogud.com  Thu Jan 16 12:46:14 2014
Return-Path: <ogud@ogud.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01F4E1ACCFC for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 12:46:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TLm0-ylSSDPg for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 12:46:11 -0800 (PST)
Received: from smtp125.ord1c.emailsrvr.com (smtp125.ord1c.emailsrvr.com [108.166.43.125]) by ietfa.amsl.com (Postfix) with ESMTP id 9DCBA1ACCEF for <gen-art@ietf.org>; Thu, 16 Jan 2014 12:46:11 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp8.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 521171A0278; Thu, 16 Jan 2014 15:45:59 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp8.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id D84A61A02D0;  Thu, 16 Jan 2014 15:45:58 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_6FC5AE16-B863-46CE-8F49-E2D7CCFD7A92"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA243CEC9A@AZ-FFEXMB04.global.avaya.com>
Date: Thu, 16 Jan 2014 15:45:58 -0500
Message-Id: <08A37247-FE33-4FC4-B56D-9925957D8920@ogud.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA243CEC9A@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dane-registry-acronyms.all@tools.ietf.org" <draft-ietf-dane-registry-acronyms.all@tools.ietf.org>, "dane@ietf.org" <dane@ietf.org>
Subject: Re: [Gen-art] [dane] Gen-ART Review of draft-ietf-dane-registry-acronyms-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 20:46:14 -0000

--Apple-Mail=_6FC5AE16-B863-46CE-8F49-E2D7CCFD7A92
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Jan 15, 2014, at 10:11 AM, "Romascanu, Dan (Dan)" =
<dromasca@avaya.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at
> =20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> =20
> Please resolve these comments along with any other Last Call comments =
you may receive.
> =20
> Document: =
http://www.ietf.org/id/draft-ietf-dane-registry-acronyms-03.txt
> Reviewer: Dan Romascanu
> Review Date: 1/15/2014
> IETF LC End Date: 1/23/2014
> IESG Telechat date:
> =20
> Summary:
> Ready with issues
> =20
> Major issues:
> None =96 it=92s a simple, clear and useful document.

thanks=20

> =20
> Minor issues:
> 1.       In Section 2.3 the I-D recommends that the values in =
reference column for SHA-256 and SHA-512 refer to [RFC 6698] while the =
IANA Considerations section in RFC 6698 recommends and the registry =
entries in the TLSA Matching Types table =
athttp://www.iana.org/assignments/dane-parameters/dane-parameters.xhtml  =
point to [RFC 6234].

Good Catch, fixed=20

> 2.       As this I-D updates the registries with a column for =
acronyms, it seems more accurate that the reference columns of all =
tables mention both  [RFC 6698] and [RFC XXXX] (this RFC)

I'm not sure if I agree, all this document does is to change the format =
of the registries it is not the definitions of any table entry.=20
But I think it would be good to change the reference for each of the =
registries to point to both RFC6698 and RFCXXXX=20

I propose adding to each registry sections the following text:=20
        "Update reference for this registry to include both [RFC6698] =
and [RFC-this-document]"

> =20
> Nits/editorial comments:
> In the Introduction section:
> =91This document updates the IANA registry definition for TLSA
>    record to add a column with acronym for each specified field=92
> s/acronym/an acronym/
> =20

Fixed=20

thanks=20

	Olafur


--Apple-Mail=_6FC5AE16-B863-46CE-8F49-E2D7CCFD7A92
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"><base href=3D"x-msg://1557/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Jan 15, 2014, =
at 10:11 AM, "Romascanu, Dan (Dan)" &lt;<a =
href=3D"mailto:dromasca@avaya.com">dromasca@avaya.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: 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; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">I am the assigned Gen-ART reviewer for this =
draft. For background on Gen-ART, please see the FAQ =
at<o:p></o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">&lt;<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>&gt;.<o:p></o=
:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">Please resolve these comments along with any =
other Last Call comments you may receive.<o:p></o:p></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
">Document:<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://www.ietf.org/id/draft-ietf-dane-registry-acronyms-03.txt" =
style=3D"color: purple; text-decoration: underline; =
">http://www.ietf.org/id/draft-ietf-dane-registry-acronyms-03.txt</a><o:p>=
</o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; ">Reviewer: Dan =
Romascanu<o:p></o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">Review Date: =
1/15/2014<o:p></o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">IETF LC End Date: =
1/23/2014<o:p></o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">IESG Telechat =
date:<o:p></o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">Summary:<o:p></o:p></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
">Ready with issues<o:p></o:p></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">Major =
issues:<o:p></o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">None =96 it=92s a =
simple, clear and useful =
document.</div></div></div></blockquote><div><br></div>thanks&nbsp;</div><=
div><br><blockquote type=3D"cite"><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple" style=3D"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; "><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p></o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">Minor issues:<o:p></o:p></div><div style=3D"margin:=
 0cm 0cm 0.0001pt 36pt; font-size: 11pt; font-family: Calibri, =
sans-serif; text-indent: -18pt; "><span>1.<span style=3D"font-style: =
normal; font-variant: normal; font-weight: normal; font-size: 7pt; =
line-height: normal; font-family: 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In Section 2.3 the I-D recommends that the values in =
reference column for SHA-256 and SHA-512 refer to [RFC 6698] while the =
IANA Considerations section in RFC 6698 recommends and the registry =
entries in the TLSA Matching Types table at<a =
href=3D"http://www.iana.org/assignments/dane-parameters/dane-parameters.xh=
tml" style=3D"color: purple; text-decoration: underline; =
">http://www.iana.org/assignments/dane-parameters/dane-parameters.xhtml</a=
><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp;point to [RFC =
6234].</div></div></div></blockquote><div><br></div>Good Catch, =
fixed&nbsp;</div><div><br><blockquote type=3D"cite"><div lang=3D"EN-US" =
link=3D"blue" vlink=3D"purple" style=3D"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; "><div =
class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt 36pt; font-size: 11pt; font-family: =
Calibri, sans-serif; text-indent: -18pt; "><o:p></o:p></div><div =
style=3D"margin: 0cm 0cm 0.0001pt 36pt; font-size: 11pt; font-family: =
Calibri, sans-serif; text-indent: -18pt; "><span>2.<span =
style=3D"font-style: normal; font-variant: normal; font-weight: normal; =
font-size: 7pt; line-height: normal; font-family: 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>As this I-D updates the registries with a column for =
acronyms, it seems more accurate that the reference columns of all =
tables mention both &nbsp;[RFC 6698] and [RFC XXXX] (this =
RFC)</div></div></div></blockquote><div><br></div>I'm not sure if I =
agree, all this document does is to change the format of the registries =
it is not the definitions of any table entry.&nbsp;</div><div>But I =
think it would be good to change the reference for each of the =
registries to point to both RFC6698 and =
RFCXXXX&nbsp;</div><div><br></div><div>I propose adding to each registry =
sections the following text:&nbsp;</div><div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; "Update reference for this registry to include =
both&nbsp;[RFC6698] and =
[RFC-this-document]"</div><div><br></div></div><div><blockquote =
type=3D"cite"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" =
style=3D"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; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt 36pt; font-size: 11pt; font-family: =
Calibri, sans-serif; text-indent: -18pt; "><o:p></o:p></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
">Nits/editorial comments:<o:p></o:p></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">In the =
Introduction section:<o:p></o:p></div><pre style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">=91This =
document updates the IANA registry definition for =
TLSA<o:p></o:p></pre><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-size: =
12pt; font-family: 'Times New Roman', serif; ">&nbsp;&nbsp; record to =
add a column with acronym for each specified =
field=92<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-size: 12pt; font-family: 'Times New Roman', serif; =
">s/acronym/an acronym/<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-size: 12pt; font-family: 'Times New Roman', serif; =
">&nbsp;</span></div></div></div></blockquote><div><br></div>Fixed&nbsp;</=
div><div><br></div><div>thanks&nbsp;</div><div><br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Olafur</div><div><br></div></body></html>=

--Apple-Mail=_6FC5AE16-B863-46CE-8F49-E2D7CCFD7A92--

From mahoney@nostrum.com  Thu Jan 16 15:11:59 2014
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B195C1ACC89 for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 15:11:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZJ2HsgyEBtb3 for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 15:11:58 -0800 (PST)
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 ED6951AD8EE for <gen-art@ietf.org>; Thu, 16 Jan 2014 15:11:55 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0GNBhji011668 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 16 Jan 2014 17:11:43 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52D8672F.5010303@nostrum.com>
Date: Thu, 16 Jan 2014 17:11:43 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-01-16
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 23:11:59 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
David Black       2014-01-27   draft-ietf-qresync-rfc5162bis-09

Elwyn Davies      2014-01-28   draft-ietf-v6ops-nat64-experience-09

Francis Dupont    2014-02-11   draft-housley-pkix-test-oids-00


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 aidan.williams@audinate.com  Thu Jan 16 15:16:41 2014
Return-Path: <aidan.williams@audinate.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB9781AD8DC for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 15:16:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yTBXorU_KMXP for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 15:16:40 -0800 (PST)
Received: from zimbra8.audinate.com (sydney.audinate.com [150.101.200.21]) by ietfa.amsl.com (Postfix) with ESMTP id 934551A1521 for <gen-art@ietf.org>; Thu, 16 Jan 2014 15:16:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by zimbra8.audinate.com (Postfix) with ESMTP id 5FCF63A76B6; Fri, 17 Jan 2014 10:16:26 +1100 (EST)
Received: from zimbra8.audinate.com ([127.0.0.1]) by localhost (zimbra8.audinate.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id C9YXCngGN2iZ; Fri, 17 Jan 2014 10:16:25 +1100 (EST)
Received: from localhost (localhost [127.0.0.1]) by zimbra8.audinate.com (Postfix) with ESMTP id 7229F3A76B0; Fri, 17 Jan 2014 10:16:25 +1100 (EST)
X-Virus-Scanned: amavisd-new at audinate.com
Received: from zimbra8.audinate.com ([127.0.0.1]) by localhost (zimbra8.audinate.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id OkKrmU-BnBzH; Fri, 17 Jan 2014 10:16:25 +1100 (EST)
Received: from zimbra8.audinate.com (zimbra8.audinate.com [10.12.0.4]) by zimbra8.audinate.com (Postfix) with ESMTP id 51B353A76A9; Fri, 17 Jan 2014 10:16:25 +1100 (EST)
Date: Fri, 17 Jan 2014 10:16:25 +1100 (EST)
From: Aidan Williams <aidan.williams@audinate.com>
To: Scott Brim <scott.brim@gmail.com>
Message-ID: <12479873.119.1389914182745.JavaMail.aidan@praxis.audinate.com>
In-Reply-To: <CAPv4CP-T1yrLTnyKJJ_mkzYVtCh+8j3T98ApX0cvU4zkeFHjFA@mail.gmail.com>
References: <CAPv4CP99LPczouE0VJkvmtDhZ+xOw0qOo3hongohTABT=WJoZQ@mail.gmail.com> <4950007.112.1389848276062.JavaMail.aidan@praxis.audinate.com> <CAPv4CP-T1yrLTnyKJJ_mkzYVtCh+8j3T98ApX0cvU4zkeFHjFA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_118_15824650.1389914182744"
X-Mailer: Zimbra 8.0.5_GA_5839 (Zimbra Desktop/7.2.2_11951_Mac)
Thread-Topic: GEN-ART LC review of draft-ietf-avtcore-clksrc-09
Thread-Index: PsCo2SC7UNfios0Y6uKW0InxQ5gMgw==
Cc: draft-ietf-avtcore-clksrc all <draft-ietf-avtcore-clksrc.all@tools.ietf.org>, gen-art <gen-art@ietf.org>
Subject: Re: [Gen-art] GEN-ART LC review of draft-ietf-avtcore-clksrc-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 23:16:42 -0000

------=_Part_118_15824650.1389914182744
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi Scott, 

Thanks for the clarification.. it helped. 

The inclusion of the receivers reference clock in a rejection is intended to allow useful information to be logged and provided to the system operator. An operator should be able to look at a log file (or a packet trace) and understand why the clksrc signaling failed. We did consider just rejecting with no extra information, but felt it would be more useful to offer information that was likely to be useful to the operator. We did not expect the information to be used to re-start negotiation. 

The motivational discussion didn't make it into the document.. I guess you feel a sentence describing the motivation/expectation would be helpful? What are the mechanics of making a change at this stage: would such a change involve a -10 of the draft or can we do it as a final editorial tweak? 

- aidan 

----- Original Message -----

> From: "Scott Brim" <scott.brim@gmail.com>
> To: "Aidan Williams" <aidan.williams@audinate.com>
> Cc: "draft-ietf-avtcore-clksrc all"
> <draft-ietf-avtcore-clksrc.all@tools.ietf.org>, "gen-art"
> <gen-art@ietf.org>
> Sent: Friday, 17 January, 2014 7:22:33 AM
> Subject: Re: GEN-ART LC review of draft-ietf-avtcore-clksrc-09

> On Wed, Jan 15, 2014 at 11:57 PM, Aidan Williams
> <aidan.williams@audinate.com> wrote:
> >
> > Hi Scott,

> Hi Aidan. Let me try to be clearer. My problem is with the sentence:
> "If the answerer rejects the offer because the available reference
> clocks are incompatible, the rejection MUST
> contain at least one timestamp reference clock specification usable
> by
> the answerer."

> "If the answerer rejects the offer because the available reference
> clocks are incompatible, ..."

> As you say, in this case there is little prospect that the sender
> could usefully start over. Therefore why would the answerer include,
> in the rejection, a clock that is usable by him (the answerer)?

> "... the rejection MUST contain at least one timestamp reference
> clock
> specification usable by the answerer."

> Either there's no point in the rejection including a reference clock,
> or there is. If there is no point, why do you say a reference clock
> MUST be included? If there is a point, that means there is some
> expectation that the sender might do something with the reference
> clock in the rejection. What is that expectation? It would be good to
> document it.

> Is that clearer?

> Thanks ... Scott

------=_Part_118_15824650.1389914182744
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D'text/css'>p { margin: 0; }</style></head><body><=
div style=3D'font-family: verdana,helvetica,sans-serif; font-size: 10pt; co=
lor: #000000'>Hi Scott,<br><br>Thanks for the clarification..&nbsp; it help=
ed.<br><br>The inclusion of the receivers reference clock in a rejection is=
 intended to allow useful information to be logged and provided to the syst=
em operator.&nbsp; An operator should be able to look at a log file (or a p=
acket trace) and understand why the clksrc signaling failed.&nbsp; We did c=
onsider just rejecting with no extra information, but felt it would be more=
 useful to offer information that was likely to be useful to the operator.&=
nbsp; We did not expect the information to be used to re-start negotiation.=
<br><br>The motivational discussion didn't make it into the document..&nbsp=
; I guess you feel a sentence describing the motivation/expectation would b=
e helpful?&nbsp; What are the mechanics of making a change at this stage: w=
ould such a change involve a -10 of the draft or can we do it as a final ed=
itorial tweak?<br><br>- aidan<br><br><br><hr id=3D"zwchr"><blockquote style=
=3D"border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left=
: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-d=
ecoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"=
><b>From: </b>"Scott Brim" &lt;scott.brim@gmail.com&gt;<br><b>To: </b>"Aida=
n Williams" &lt;aidan.williams@audinate.com&gt;<br><b>Cc: </b>"draft-ietf-a=
vtcore-clksrc all" &lt;draft-ietf-avtcore-clksrc.all@tools.ietf.org&gt;, "g=
en-art" &lt;gen-art@ietf.org&gt;<br><b>Sent: </b>Friday, 17 January, 2014 7=
:22:33 AM<br><b>Subject: </b>Re: GEN-ART LC review of draft-ietf-avtcore-cl=
ksrc-09<br><br>On Wed, Jan 15, 2014 at 11:57 PM, Aidan Williams<br>&lt;aida=
n.williams@audinate.com&gt; wrote:<br>&gt;<br>&gt; Hi Scott,<br><br><br>Hi =
Aidan. Let me try to be clearer. My problem is with the sentence:<br>"If th=
e answerer rejects the offer because the available reference<br>clocks are =
incompatible, the rejection MUST<br>contain at least one timestamp referenc=
e clock specification usable by<br>the answerer."<br><br>"If the answerer r=
ejects the offer because the available reference<br>clocks are incompatible=
, ..."<br><br>As you say, in this case there is little prospect that the se=
nder<br>could usefully start over. Therefore why would the answerer include=
,<br>in the rejection, a clock that is usable by him (the answerer)?<br><br=
>"... the rejection MUST contain at least one timestamp reference clock<br>=
specification usable by the answerer."<br><br>Either there's no point in th=
e rejection including a reference clock,<br>or there is. &nbsp;If there is =
no point, why do you say a reference clock<br>MUST be included? &nbsp;If th=
ere is a point, that means there is some<br>expectation that the sender mig=
ht do something with the reference<br>clock in the rejection. What is that =
expectation? It would be good to<br>document it.<br><br>Is that clearer?<br=
><br>Thanks ... Scott<br></blockquote><br></div></body></html>
------=_Part_118_15824650.1389914182744--

From mahoney@nostrum.com  Thu Jan 16 15:19:12 2014
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C630D1AD8E1 for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 15:19:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kwr2GT5zcqgL for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 15:19:11 -0800 (PST)
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 796FF1AD8DC for <gen-art@ietf.org>; Thu, 16 Jan 2014 15:19:11 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0GNIwcl011916 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 16 Jan 2014 17:18:59 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52D868E2.2020303@nostrum.com>
Date: Thu, 16 Jan 2014 17:18:58 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2014-01-23 Telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 23:19:13 -0000

Hi all,

The following reviewers have assignments:

Reviewer            LC end       Draft
------------------------------------------------------------------------------------
Alexey Melnikov     2014-01-22   draft-ietf-isis-rfc6326bis-01

Ben Campbell        2013-12-25   draft-ietf-6man-stable-privacy-addresses-16 **

Brian Carpenter     2014-01-22   draft-ietf-netmod-system-mgmt-10 **

David Black         2014-01-05   draft-ietf-ccamp-oam-configuration-fwk-12 *

Francis Dupont      2014-01-10   draft-moriarty-pkcs12v1-1-03 **

Kathleen Moriarty   2014-01-22   draft-housley-number-registries-02

Meral Shirazipour   2014-01-16   draft-ietf-pwe3-mpls-tp-cv-adv-04

Martin Thomson      2014-01-06   draft-ietf-opsawg-lsn-deployment-04 **

Peter Yee           2014-01-17   draft-ietf-mpls-multipath-use-03

Roni Even           2013-12-23   draft-ietf-netmod-interfaces-cfg-15 *

Russ Housley        2014-01-16   draft-ietf-mpls-tp-p2mp-framework-05 **

Robert Sparks       2014-01-17   draft-ietf-mpls-moving-iana-registries-03 **

Scott Brim          2013-12-31   draft-farrell-perpass-attack-03 **

Vijay Gurbani       2013-11-18   draft-shore-icmp-aup-09 *
Vijay Gurbani       2013-11-27   draft-ietf-l2vpn-evpn-req-06

* Earlier draft reviewed
** Already reviewed


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

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

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

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

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:


From david.black@emc.com  Thu Jan 16 15:30:46 2014
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 445191AD8DC; Thu, 16 Jan 2014 15:30:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8J2BoqhG88xP; Thu, 16 Jan 2014 15:30:43 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA971AD8F1; Thu, 16 Jan 2014 15:30:42 -0800 (PST)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0GNULYB011556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jan 2014 18:30:22 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s0GNULYB011556
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1389915022; bh=IcrX37rbU6dLxyqQDK6Gr/DzMGM=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=XfMLFdqepTYNinQMvjQbRYdhNPnbPnU0uCDkiU/WMvtnqD0OOpl6A8tC0+GKikC3U xrTZzzWz6NBUISPoY1y9Ek+cNCDnFIrLtJMP+A9zUs8v81Tk+9SOzU1pvN9ZDF5QHT g6O/j5klzILfUmqvRhRwEOEuueQnViCcG+VImkyE=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s0GNULYB011556
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd04.lss.emc.com (RSA Interceptor); Thu, 16 Jan 2014 15:30:13 -0800
Received: from mxhub14.corp.emc.com (mxhub14.corp.emc.com [128.222.70.235]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0GNUBHm026761 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Jan 2014 18:30:12 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub14.corp.emc.com ([128.222.70.235]) with mapi; Thu, 16 Jan 2014 18:30:11 -0500
From: "Black, David" <david.black@emc.com>
To: "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>, "attila.takacs@ericsson.com" <attila.takacs@ericsson.com>, "hejia@huawei.com" <hejia@huawei.com>, "don.fedyk@gmail.com" <don.fedyk@gmail.com>
Date: Thu, 16 Jan 2014 18:30:09 -0500
Thread-Topic: Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-12
Thread-Index: Ac8TEuVFfzpzNuIgSz6mj6KV0hTVBg==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F04760D@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-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: public, Resumes
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 23:30:46 -0000

The -12 version of this draft addresses the nits and editorial items
noted in the Gen-ART review of the -11 version.  It's ready for
RFC publication.

Thanks,
--David

> -----Original Message-----
> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Black, David
> Sent: Sunday, December 29, 2013 9:51 PM
> To: General Area Review Team (gen-art@ietf.org); attila.takacs@ericsson.c=
om;
> donald.fedyk@alcatel-lucent.com; hejia@huawei.com
> Cc: adrian@olddog.co.uk; ccamp@ietf.org; ietf@ietf.org
> Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ccamp-oam-configurati=
on-
> fwk-11
>=20
> One additional nit - Don Fedyk's email address listed in the draft does n=
ot
> work.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Sunday, December 29, 2013 9:46 PM
> > To: General Area Review Team (gen-art@ietf.org); attila.takacs@ericsson=
.com;
> > donald.fedyk@alcatel-lucent.com; hejia@huawei.com
> > Cc: Black, David; adrian@olddog.co.uk; ccamp@ietf.org; ietf@ietf.org
> > Subject: Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-11
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-ccamp-oam-configuration-fwk-11
> > Reviewer: David L. Black
> > Review Date: December 29, 2013
> > IETF LC End Date: January 5, 2014
> >
> > Summary: This draft is basically ready for publication, but has nits th=
at
> > should be fixed before publication.
> >
> > This draft describes the GMPLS framework for signaling OAM configuratio=
n,
> > and specifies additional RSVP elements to support that signaling.  Know=
ledge
> > of RSVP, and specifically RSVP-TE is assumed; beyond that, the draft is
> > complete, although it is very detailed - see editorial comment below on
> > Section 3.
> >
> > Nits/editorial comments:
> >
> > Sections 3.1-3.3 dive into the details very quickly.  They would be eas=
ier
> to
> > understand if there was an overview paragraph near the start of Section=
 3
> that
> > describes the roles of the two ADMIN_STATUS flags and the two LSP Attri=
butes
> > flags in OAM configuration (establishment, change/adjustment, deletion)
> before
> > the current text that contains the details of RSVP message processing.
> >
> > There are a number of instances of "(IANA to assign)" in section 4 that=
 the
> > RFC Editor will need to remove - an RFC Editor note to that effect shou=
ld
> > be inserted at the start of Section 4.
> >
> > Section 4.5 is necessarily incomplete on P2MP considerations, because (=
as
> > it says) "P2MP OAM mechanisms are very specific to the data plane
> technology".
> > It would be helpful if section 4.5 contained language indicating what a
> > specific data plane specification should include to completely specify
> > P2MP OAM configuration for that data plane.
> >
> > idnits 2.13.01 didn't find anything that needs 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 scott.brim@gmail.com  Thu Jan 16 15:45:17 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 056B21AD8F4 for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 15:45:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BcUGJrMILN67 for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 15:45:15 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 99DA61AD8F5 for <gen-art@ietf.org>; Thu, 16 Jan 2014 15:45:15 -0800 (PST)
Received: by mail-ob0-f173.google.com with SMTP id vb8so3578725obc.18 for <gen-art@ietf.org>; Thu, 16 Jan 2014 15:45:03 -0800 (PST)
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=8G3RywlHXlUuBKl5sPEihCvMNS+GVRF1r5FmEqkhIUM=; b=D9BX3O+5nYQc4uWi4FntzpjLU3JoC/WhBnLseH5g/75WqxBxOPwF/6GN9HGzkGFRro CYfV8zvE3a/+RFcWMhMvbM8zjMBZkh6t1EQaNUWEGtVRd9hffAo2dMkF2llJzv4zL9J4 F/gcvR7jEZWRogIal32dDMhXtxIMKcNabBSBr5ziGgouR7OdFZ/BaOJrZ9xvwZdGqcQd ykoXp3UlU8zR8y9g2m0cov7aOcH1ilEVFoOMVMyzvyzHtZNHc+399mPgW/P5x/5A0eRT rQwqfkaXPNUwQNDMr8eLNqiGkrYyFIqYIB/EsuPVJ8B1yG7mSsenhlFuv1DYHRh3MvhF 2sIA==
MIME-Version: 1.0
X-Received: by 10.60.37.33 with SMTP id v1mr9621379oej.2.1389915903249; Thu, 16 Jan 2014 15:45:03 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 16 Jan 2014 15:45:03 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 16 Jan 2014 15:45:03 -0800 (PST)
In-Reply-To: <12479873.119.1389914182745.JavaMail.aidan@praxis.audinate.com>
References: <CAPv4CP99LPczouE0VJkvmtDhZ+xOw0qOo3hongohTABT=WJoZQ@mail.gmail.com> <4950007.112.1389848276062.JavaMail.aidan@praxis.audinate.com> <CAPv4CP-T1yrLTnyKJJ_mkzYVtCh+8j3T98ApX0cvU4zkeFHjFA@mail.gmail.com> <12479873.119.1389914182745.JavaMail.aidan@praxis.audinate.com>
Date: Thu, 16 Jan 2014 18:45:03 -0500
Message-ID: <CAPv4CP-PA_dfiasvRr+Zbfw8JrNACQaOzo+mT7wbi1dMa7=+LA@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
To: Aidan Williams <aidan.williams@audinate.com>
Content-Type: multipart/alternative; boundary=089e0117691fae56ab04f01f03f3
Cc: gen-art <gen-art@ietf.org>, draft-ietf-avtcore-clksrc.all@tools.ietf.org
Subject: Re: [Gen-art] GEN-ART LC review of draft-ietf-avtcore-clksrc-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 23:45:17 -0000

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

Got it! Now that I understand, this is a simple editorial fix. How about
adding ", for information." or ", for logging."? Something like that.

I leave it to Jari whether you need a new version, but I would tell the WG
what you decide to do in any case. Since it's just editorial and doesn't
change anything substantial, imho you could even put it off until AUTH48
time.

Thanks!

Scott

--089e0117691fae56ab04f01f03f3
Content-Type: text/html; charset=ISO-8859-1

<p dir="ltr">Got it! Now that I understand, this is a simple editorial fix. How about adding &quot;, for information.&quot; or &quot;, for logging.&quot;? Something like that.</p>
<p dir="ltr">I leave it to Jari whether you need a new version, but I would tell the WG what you decide to do in any case. Since it&#39;s just editorial and doesn&#39;t change anything substantial, imho you could even put it off until AUTH48 time. </p>

<p dir="ltr">Thanks!</p>
<p dir="ltr">Scott<br>
</p>

--089e0117691fae56ab04f01f03f3--

From scott.brim@gmail.com  Thu Jan 16 16:08:47 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5BF31ACC86 for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 16:08:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id paPbhxKJxR3A for <gen-art@ietfa.amsl.com>; Thu, 16 Jan 2014 16:08:46 -0800 (PST)
Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 958A01AC4A3 for <gen-art@ietf.org>; Thu, 16 Jan 2014 16:08:46 -0800 (PST)
Received: by mail-oa0-f47.google.com with SMTP id m1so2574275oag.6 for <gen-art@ietf.org>; Thu, 16 Jan 2014 16:08:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=HaiwPt0ODwPXsx0RSw6NuHiRnPKZoscu4hmC3nZy1to=; b=Du6OV+t37p0UIWtTSyFqlZA0MEKPFxap/TfG6jx3X7bZk0+sc+uaPQxhPfgh59Ftiy hHoAu3lEGRPQ3b0Lfu3Bh9d7gSiU2TBigWPBf+Qxcsc/UTX/LuwQTO2MZrrnC0l4d87S 4xt/GCQbn41XV3Nf6M2muHgqJGdUz3lanPwFQv6NxyUzIZSgVH3CefxkaPagWsOkfYWE 8+DEP+5FrzcBhAXba+Sp2LePptUI3xnqVoeio/o3QYztBQpLItl/HbUOteYUGDGt+rwV H+sdW+NeLcRn4QigdTBPI1MKSbswRtBYiFEBX8efGTklsPV727bVoG56XFG9HYlf54zA zozw==
MIME-Version: 1.0
X-Received: by 10.60.58.36 with SMTP id n4mr9625679oeq.51.1389917313229; Thu, 16 Jan 2014 16:08:33 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 16 Jan 2014 16:08:32 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 16 Jan 2014 16:08:32 -0800 (PST)
Date: Thu, 16 Jan 2014 19:08:32 -0500
Message-ID: <CAPv4CP9dHq5UH4AC-zmyg-ur8H2NamUg_a=LG3VUUUPu=PPcBg@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
To: gen-art <gen-art@ietf.org>
Content-Type: multipart/alternative; boundary=089e01538baab8eaa104f01f57b2
Subject: [Gen-art] Review of perpass-attack?
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 00:08:48 -0000

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

Jari, what do you want me to do for a perpass-attack review? We're still in
the middle of hashing it out. What are you going to do in the telechat?

Scott

--089e01538baab8eaa104f01f57b2
Content-Type: text/html; charset=ISO-8859-1

<p dir="ltr">Jari, what do you want me to do for a perpass-attack review? We&#39;re still in the middle of hashing it out. What are you going to do in the telechat?</p>
<p dir="ltr">Scott</p>

--089e01538baab8eaa104f01f57b2--

From ron.even.tlv@gmail.com  Fri Jan 17 01:38:53 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19F241ADFB4 for <gen-art@ietfa.amsl.com>; Fri, 17 Jan 2014 01:38:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zT6I7QOfdoRf for <gen-art@ietfa.amsl.com>; Fri, 17 Jan 2014 01:38:51 -0800 (PST)
Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id A6ED31ADFB3 for <gen-art@ietf.org>; Fri, 17 Jan 2014 01:38:50 -0800 (PST)
Received: by mail-ea0-f171.google.com with SMTP id h10so1635017eak.2 for <gen-art@ietf.org>; Fri, 17 Jan 2014 01:38:37 -0800 (PST)
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=+AdP3894qKuvxCeE497satOn+hmSnEn9C9E0WdVMr/o=; b=vJnQEzLKiy5F8uusoHZ4s7tp0ojiGoNKOH9MOF3uof/iDIc+Qx8QAwM2ZHbHLAxFsN wDKrEtZdrhkNe8WCsRmOAiaFOjsrlTJGdRhZ3KhgoaRtjp7K8x11icVgyPhNCtCLjfPi 8ft/dUVHscGSNXNuBld6T9P9hY2IXwXqB75dXB9N0f2RxCW5r3O0ItDCxxpy+MfXmjW8 tuDLPIeO55tZcDXAVwhwXzvUYaeJwp2AtxAs4ggOSiGdFFBmymUXR54IHMKVl4sfS08z K9OVzC612awTG0V7YfSdhbPqj9GHhzP3tv9XA9VifMZmKekxxrUZBQ5kzntd33SbJQdQ B0Nw==
X-Received: by 10.14.201.68 with SMTP id a44mr1250566eeo.46.1389951517845; Fri, 17 Jan 2014 01:38:37 -0800 (PST)
Received: from RoniE ([109.66.49.55]) by mx.google.com with ESMTPSA id v1sm25220229eef.9.2014.01.17.01.38.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 17 Jan 2014 01:38:37 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Aidan Williams'" <aidan.williams@audinate.com>
References: <CAPv4CP99LPczouE0VJkvmtDhZ+xOw0qOo3hongohTABT=WJoZQ@mail.gmail.com> <4950007.112.1389848276062.JavaMail.aidan@praxis.audinate.com> <CAPv4CP-T1yrLTnyKJJ_mkzYVtCh+8j3T98ApX0cvU4zkeFHjFA@mail.gmail.com>
In-Reply-To: <CAPv4CP-T1yrLTnyKJJ_mkzYVtCh+8j3T98ApX0cvU4zkeFHjFA@mail.gmail.com>
Date: Fri, 17 Jan 2014 11:34:55 +0200
Message-ID: <00d401cf1367$63948230$2abd8690$@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: AQJxILf2R/qT8UFJbyRZLG/fY7aS2gNAT/HbAtmquR+ZE7yqMA==
Content-Language: en-us
Cc: 'draft-ietf-avtcore-clksrc all' <draft-ietf-avtcore-clksrc.all@tools.ietf.org>, 'gen-art' <gen-art@ietf.org>
Subject: Re: [Gen-art] GEN-ART LC review of draft-ietf-avtcore-clksrc-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 09:38:53 -0000

Hi Aidan,
You should look at all LC comments (I saw none and the LC finished
yesterday) and at the comments from the AD review (from Richard).
To me they look like editorial so you can put a new revision after
addressing Richard's comments
Roni Even

> -----Original Message-----
> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Scott Brim
> Sent: 16 January, 2014 10:23 PM
> To: Aidan Williams
> Cc: draft-ietf-avtcore-clksrc all; gen-art
> Subject: Re: [Gen-art] GEN-ART LC review of draft-ietf-avtcore-clksrc-09
> 
> On Wed, Jan 15, 2014 at 11:57 PM, Aidan Williams
> <aidan.williams@audinate.com> wrote:
> >
> > Hi Scott,
> 
> 
> Hi Aidan. Let me try to be clearer. My problem is with the sentence:
> "If the answerer rejects the offer because the available reference clocks
are
> incompatible, the rejection MUST contain at least one timestamp reference
> clock specification usable by the answerer."
> 
> "If the answerer rejects the offer because the available reference clocks
are
> incompatible, ..."
> 
> As you say, in this case there is little prospect that the sender could
usefully
> start over. Therefore why would the answerer include, in the rejection, a
clock
> that is usable by him (the answerer)?
> 
> "... the rejection MUST contain at least one timestamp reference clock
> specification usable by the answerer."
> 
> Either there's no point in the rejection including a reference clock, or
there is.
> If there is no point, why do you say a reference clock MUST be included?
If
> there is a point, that means there is some expectation that the sender
might do
> something with the reference clock in the rejection. What is that
expectation?
> It would be good to document it.
> 
> Is that clearer?
> 
> Thanks ... Scott
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From lberger@labn.net  Fri Jan 17 11:15:26 2014
Return-Path: <lberger@labn.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D739B1AE17F; Fri, 17 Jan 2014 11:15:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.188
X-Spam-Level: **
X-Spam-Status: No, score=2.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_EQ_BIZ=0.288, HELO_MISMATCH_BIZ=0.443, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.793, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t_HcWel49cae; Fri, 17 Jan 2014 11:15:24 -0800 (PST)
Received: from newdragon.webhostserver.biz (unknown [69.25.137.16]) by ietfa.amsl.com (Postfix) with ESMTP id 0E11C1AE0E9; Fri, 17 Jan 2014 11:15:23 -0800 (PST)
Received: from localhost ([::1]:35483 helo=[127.0.0.1]) by newdragon.webhostserver.biz with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.82) (envelope-from <lberger@labn.net>) id 1W4Esp-0004kQ-5K; Fri, 17 Jan 2014 22:15:11 +0300
Message-ID: <52D9813D.7040904@labn.net>
Date: Fri, 17 Jan 2014 14:15:09 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: mpls@ietf.org
References: <20140117134852.25272.87457.idtracker@ietfa.amsl.com>
In-Reply-To: <20140117134852.25272.87457.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - newdragon.webhostserver.biz
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-Get-Message-Sender-Via: newdragon.webhostserver.biz: authenticated_id: lberger@blabn.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: Adrian Farrel <adrian@olddog.co.uk>, gen-art@ietf.org
Subject: Re: [Gen-art] [mpls] I-D Action: draft-ietf-mpls-tp-p2mp-framework-06.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: lberger@labn.net
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 19:15:27 -0000

Hello,
	This version addresses received editorial comments (some of which may
not have been cc'ed to the mpls list), and update's Dan's contact info.

Lou (and co-authors)

On 01/17/2014 08:48 AM, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.
> 
>         Title           : A Framework for Point-to-Multipoint MPLS in Transport Networks
>         Authors         : Dan Frost
>                           Stewart Bryant
>                           Matthew Bocci
>                           Lou Berger
> 	Filename        : draft-ietf-mpls-tp-p2mp-framework-06.txt
> 	Pages           : 12
> 	Date            : 2014-01-16
> 
> Abstract:
>    The Multiprotocol Label Switching Transport Profile is the common set
>    of MPLS protocol functions defined to enable the construction and
>    operation of packet transport networks.  The MPLS-TP supports both
>    point-to-point and point-to-multipoint transport paths.  This
>    document defines the elements and functions of the MPLS-TP
>    architecture applicable specifically to supporting point-to-
>    multipoint transport paths.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-p2mp-framework/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-mpls-tp-p2mp-framework-06
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-mpls-tp-p2mp-framework-06
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 


From peter@akayla.com  Fri Jan 17 23:21:44 2014
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22CD71A1F56; Fri, 17 Jan 2014 23:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.4
X-Spam-Level: 
X-Spam-Status: No, score=0.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_LIST=2.3, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G1tcia87JT9x; Fri, 17 Jan 2014 23:21:42 -0800 (PST)
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 5B72B1A1F1F; Fri, 17 Jan 2014 23:21:42 -0800 (PST)
Received: from spectre ([173.8.184.78]) by p3plsmtpa07-09.prod.phx3.secureserver.net with  id FKMR1n0061huGat01KMRgb; Sat, 18 Jan 2014 00:21:29 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-mpls-multipath-use.all@tools.ietf.org>
Date: Fri, 17 Jan 2014 23:21:28 -0800
Message-ID: <02d101cf141d$ea1a8f50$be4fadf0$@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: Ac8UHcdwianJ3UTFS4ylM1d/AUj2Sg==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-mpls-multipath-use-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 18 Jan 2014 07:21:44 -0000

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

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

Document: draft-ietf-mpls-multipath-use-03
Reviewer: Peter Yee
Review Date: January-16-2014
IETF LC End Date: January-17-2014
IESG Telechat date: January-23-2014

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 document discusses multipath MPLS operations and describes the means of
supporting MPLS as a server layer for MPLS-TP and vice versa.  It lists
requirements and implications for these operations.


Nits:

General nits:

Make all references to the expansion of ECMP read "Equal-Cost Multipath" for
consistency with RFC 2991.

In the usage RFCxxxx, use a space between RFC and xxxx except when used as a
reference, e.g., [RFCxxxx].

There are many unexplained acronyms without definition or reference.  Unless
these are abundantly clear to most readers, expand them on first usage and
provide a reference pointer where feasible.

Specific nits:

Page 1, Abstract, 2nd paragraph, 1st sentence: change "MPLS Entropy label"
to "the MPLS Entropy Label".

Page 2, Section 1, 1st paragraph,  1st sentence: delete the comma after
"traffic".

Page 2, Section 1, 1st paragraph, last sentence: change "load split" to
"load splitting".

Page 2, Section 1, 2nd paragraph, last sentence: hyphenate "fate sharing".

Page 3, Section 1, 1st paragraph, 1st sentence: hyphenate "equal cost".

Page 3, definition of "Loop Free Alternate Paths (LFA)": hyphenate "Loop
Free".

Page 3, definition of "Loop Free Alternate Paths (LFA), 1st sentence: change
the terminating period to a colon.

Page 4, Section 3.1, 1st paragraph, 1st sentence: change "date" to "data".

Page 4, Section 3.1, 1st paragraph, 2nd sentence: change the terminating
period to a colon.

Page 5, 1st full paragraph, 1st sentence: insert "Section 3.1.1" between
"[RFC5960]" and "paragraph 3".  Capitalize "paragraph".

Page 5, 1st full paragraph, 3rd sentence: same as previous instructions.

Page 5, 2nd paragraph, 2nd sentence: change ' "Section 1 Introduction"' to '
Section 1 ("Introduction")'.

Page 6, 1st paragraph, 3rd sentence: change ' "Section 2.9.4 Equal Cost
Multipath") to ' Section 2.9.4 ("Equal Cost Multipath")'.

Page 6, Section 3.2, 1st paragraph, 1st sentence: hyphenate "MPLS-TP
conformant" and delete the comma after "multipath".

Page 7, 2nd paragraph, 2nd sentence: change "A" to "An".

Page 7, 2nd paragraph, 5th and 6th sentences: change all occurrences of
"LSP" to "LSPs".

Page 7, 3rd paragraph, 2nd sentence: change "LSP" to "LSPs".

Page 7, 4th paragraph, 2nd sentence: change "LSR" to "LSRs".

Page 7, 5th paragraph: change all occurrences of "LSP" to "LSPs".

Page 7, 5th paragraph last sentence: change "co-existance" to "coexistence".

Page 8, 1st partial paragraph, 2nd full sentence: change all occurrences of
"LSP" to "LPSs" and change "LSR" to "LSRs".

Page 8, 2nd full paragraph: change all occurrences of "LSP" to "LSPs".

Page 8, 4th paragraph, 1st sentence: change "LSP" to "LSPs".

Page 8, 4th paragraph, 2nd sentence: is there a quantitative definition for
"very infrequent" that can be substituted or explained?

Page 8, 4th paragraph, 3rd sentence: change "presense" to "presence".
Insert "a" before "GAL".

Page 9, 1st partial paragraph: delete "label" following "EL" in two
locations.

Page 9, Section 4, 1st paragraph, 1st sentence: change first "LSP" to
"LSPs".  Change "a MPLS-TP" to "an MPLS-TP" unless MPLS is pronounced liked
"mipples" or something similar and not just spelled out.

Page 9, Section 4, 2nd paragraph: replace all occurrences of "LSP" with
"LSPs".

Page 9, Section 4, 2nd paragraph, 2nd sentence: insert "the" between "in"
and "number".

Page 9, Section 4, 2nd paragraph, 3rd sentence: change "ILM" to "ILMs".

Page 9, Section 4, 3rd paragraph, 1st sentence: change "Server Layer" to
"server layer" for consistency of usage.  Insert "of" between "use" and
"MPLS-TP".  Change "LSP" to "LSPs".

Page 9, Section 4, 3rd paragraph, 4th sentence: change "LSP" to "LSPs".

Page 9, Section 4, 3rd paragraph, 5th sentence: change "LSP" to "LSPs".
Change "capacity" to "capacities".  Insert "generally" before "not integer"
unless it is always the case that the capacity is not a multiple of 10 Gb/s.

Page 9, Section 4, 4th paragraph, 1st sentence: change "Server Layer" to
"server layer".

Page 10, Section 6, 2nd paragraph, 2nd sentence: hyphenate "high end" and
append a comma after that.  Hyphenate "packet processing".

Page 10, Section 6, 3rd paragraph, last sentence: same as previous
instructions.

Page 10, Section 8, 1st sentence: insert "a" between "of" and "framework".


I'm not particularly knowledgeable about MPLS, so I'm unable to express much
about the correctness of the operational points made in the document.

		-Peter Yee




From scott.brim@gmail.com  Sat Jan 18 12:41:59 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6B4F1ADFB2; Sat, 18 Jan 2014 12:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bElx65-BpJLe; Sat, 18 Jan 2014 12:41:58 -0800 (PST)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 258571ADFB0; Sat, 18 Jan 2014 12:41:58 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id wp4so592121obc.2 for <multiple recipients>; Sat, 18 Jan 2014 12:41:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=nPeVYMZi4X8oKDE3pW+Qrv4MBL5tiQy2b03ZYGFM9eg=; b=U19wfrZS9MWi2hlDFj6v7rcT939XQ23wN5TQrggTDz8rRiQ97VWkgrkFa2Xf1gBXcd FFrybXrIDt/vvwLOTdVhFg5xfj729Jfh5N40I87lZLXowv8iK8gmOTdm7p91X0d8SugG +0Kfs7mv6pv5DwN+0B/0q3GlwfY9eEBz8kAbeyECJsJ1x8hYHWVMQV/+gvJxsz15duVg gbyOsJ4ODjtNVDrCE//DYb5SmJMqNLh1sfOaBFbwa+QVJ6Rm4vIVPp9r/KHwPhr3nudh S+Np2jodecvhU+pjAsiDlJTTVsRqCkL7dmAz7sea3mHgpHoH6s4iAx2IXxeHlT6GgSWd i9cw==
X-Received: by 10.182.102.7 with SMTP id fk7mr7978828obb.28.1390077705063; Sat, 18 Jan 2014 12:41:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Sat, 18 Jan 2014 12:41:24 -0800 (PST)
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 18 Jan 2014 15:41:24 -0500
Message-ID: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com>
To: gen-art <gen-art@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e015369f0d2126704f044afec
Subject: [Gen-art] Gen-Art telechat review of draft-farrell-perpass-attack-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 18 Jan 2014 20:41:59 -0000

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

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

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

Document: draft-farrell-perpass-attack-04
Reviewer: Scott Brim
Review Date: 2014-01-18
IETF LC End Date: 2013-12-31
IESG Telechat date: (if known): 2014-01-23

Summary: Ready

Major issues: none

Minor issues: none

Nits/editorial comments: There are editorial changes I could suggest, but
it's good enough.

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

<div dir=3D"ltr"><div><span style=3D"font-family:arial,sans-serif;font-size=
:12.727272033691406px">I am the assigned Gen-ART reviewer for this draft. F=
or background on</span><br style=3D"font-family:arial,sans-serif;font-size:=
12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Gen-ART, please see the FAQ at</span><br style=3D"font-family:arial,sans-s=
erif;font-size:12.727272033691406px"><span style=3D"font-family:arial,sans-=
serif;font-size:12.727272033691406px">&lt;=A0</span><a href=3D"http://wiki.=
tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank" style=3D"fon=
t-family:arial,sans-serif;font-size:12.727272033691406px">http://wiki.tools=
.ietf.org/<u></u>area/gen/trac/wiki/GenArtfaq</a><span style=3D"font-family=
:arial,sans-serif;font-size:12.727272033691406px">&gt;.</span><br style=3D"=
font-family:arial,sans-serif;font-size:12.727272033691406px">

<br style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"><=
span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px">=
Please wait for direction from your document shepherd</span><br style=3D"fo=
nt-family:arial,sans-serif;font-size:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>or AD before posting a new version of the draft.</span><br style=3D"font-f=
amily:arial,sans-serif;font-size:12.727272033691406px"><br style=3D"font-fa=
mily:arial,sans-serif;font-size:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Document: draft-farrell-perpass-attack-04</span><br style=3D"font-family:a=
rial,sans-serif;font-size:12.727272033691406px"><span style=3D"font-family:=
arial,sans-serif;font-size:12.727272033691406px">Reviewer: Scott Brim</span=
><br style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Review Date: 2014-01-18</span><br style=3D"font-family:arial,sans-serif;fo=
nt-size:12.727272033691406px"><span style=3D"font-family:arial,sans-serif;f=
ont-size:12.727272033691406px">IETF LC End Date: 2013-12-31</span><br style=
=3D"font-family:arial,sans-serif;font-size:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>IESG Telechat date: (if known): 2014-01-23</span><br style=3D"font-family:=
arial,sans-serif;font-size:12.727272033691406px"><br style=3D"font-family:a=
rial,sans-serif;font-size:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Summary: Ready</span><br style=3D"font-family:arial,sans-serif;font-size:1=
2.727272033691406px"><br style=3D"font-family:arial,sans-serif;font-size:12=
.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Major issues: none</span><br style=3D"font-family:arial,sans-serif;font-si=
ze:12.727272033691406px"><br style=3D"font-family:arial,sans-serif;font-siz=
e:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Minor issues: none</span><br style=3D"font-family:arial,sans-serif;font-si=
ze:12.727272033691406px"><br style=3D"font-family:arial,sans-serif;font-siz=
e:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Nits/editorial comments: There are editorial changes I could suggest, but =
it&#39;s good enough.=A0</span></div></div>

--089e015369f0d2126704f044afec--

From jari.arkko@piuha.net  Sat Jan 18 12:53:28 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2C571ADFB3; Sat, 18 Jan 2014 12:53:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WKJRl8sRz4wJ; Sat, 18 Jan 2014 12:53:26 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id E86041A1F79; Sat, 18 Jan 2014 12:53:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E3E602CC5D; Sat, 18 Jan 2014 22:53:11 +0200 (EET)
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 MZc5GEEJz606; Sat, 18 Jan 2014 22:53:11 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 59DEE2CC48; Sat, 18 Jan 2014 22:53:11 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com>
Date: Sat, 18 Jan 2014 22:53:12 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art telechat review of draft-farrell-perpass-attack-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 18 Jan 2014 20:53:28 -0000

Thanks for your review, Scott.

Jari


From brian.e.carpenter@gmail.com  Sat Jan 18 14:38:12 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8A41AD7C2 for <gen-art@ietfa.amsl.com>; Sat, 18 Jan 2014 14:38:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gX-TOH1yc4nD for <gen-art@ietfa.amsl.com>; Sat, 18 Jan 2014 14:38:10 -0800 (PST)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 04F2E1ADFD7 for <gen-art@ietf.org>; Sat, 18 Jan 2014 14:38:09 -0800 (PST)
Received: by mail-pb0-f48.google.com with SMTP id rr13so5489035pbb.7 for <gen-art@ietf.org>; Sat, 18 Jan 2014 14:37:57 -0800 (PST)
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=hGdy8/UseKP/ZqobdFTiivgYMqcgrsee2Ri3j80fy1M=; b=ddMJfsoGW5pacpA0VrBUA1yvLE2lF/GQPryA0OIMDfyweoDCLR1nQL1nI6dmEl8AF6 h3xiWcGGy/PkeHMANOxgc8ZdpXJSyTQIUGVs6Gr0Ln7LYyOJcZpPxv3Jd24aHo86esWq CfafoVar5WHUhs2KCOkbNodPNdszOq1oyqwejY5bxeV+D+MSROvLkUps14pU6QOGRQDO ZdhhZPA9hyoGv7BNdkiRAPgUMvEIBCdLBxVRKdxkAayy27qcOe+4nhoIHipLgmnVfPXJ +WbR6RiC7642AXPQxYNJbEO2Ofb9olo+IwCdZt+AY5wyTEUcpsyzyAqAVIlbbryi1+n8 X1HQ==
X-Received: by 10.68.164.131 with SMTP id yq3mr10214673pbb.56.1390084677191; Sat, 18 Jan 2014 14:37:57 -0800 (PST)
Received: from [192.168.178.23] (243.199.69.111.dynamic.snap.net.nz. [111.69.199.243]) by mx.google.com with ESMTPSA id id1sm32770331pbc.11.2014.01.18.14.37.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 Jan 2014 14:37:56 -0800 (PST)
Message-ID: <52DB0241.1040401@gmail.com>
Date: Sun, 19 Jan 2014 11:37:53 +1300
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-netmod-system-mgmt.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-netmod-system-mgmt-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 18 Jan 2014 22:38:12 -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-netmod-system-mgmt-10.txt
Reviewer: Brian Carpenter
Review Date: 2014-01-19
IETF LC End Date: 2014-01-22
IESG Telechat date: 2014-01-23

Summary:  Almost ready
--------

Comments:
---------

Since the version hasn't been updated yet I haven't changed the
review, but the authors' proposed changes are fine. Please
let me know if the -11 version comes out before the telechat.

I haven't checked the yang syntax in detail. At first glance,
it looks good.


Minor Issues:
------------

"2.1.  System Identification

   There are many common properties used to identify devices, operating
   systems, software versions, etc. that need to be supported in the
   system data module.  These objects are defined as operational state
   data and the information returned by the server is intended to be
   specific to the device vendor."

Does "server" mean the NETCONF server?

"2.2.  System Time Management

   The management of the date and time used by the system need to be
   supported.  Use of one or more NTP servers to automatically set the
   system date and time need to be possible.  Utilization of the
   Timezone database [RFC6557] also need to be supported.  It should be
   possible for the server, as well as clients, to configure the system
   to use NTP."

Again, does this mean the NETCONF server? Also, which clients? This is
the first time the document mentions clients.

"2.3.  User Authentication

...It should be possible for the server, as well as
   clients, to configure the system authentication properties."

Same comment as for 2.2. Also, how does the network administrator enforce
a specific strength of authentication? It seems as though the clients can
choose to downgrade security.

"2.4.  DNS Resolver

   The configuration of the DNS resolver within the system containing
   the NETCONF server is required to control how domain names are
   resolved."

This is very hard to parse and could mean several things. Does it
mean that it MUST be possible to configure the DNS resolver?
(And I wonder what happens if the device is running mDNS?)

"3.6.  System Control

   The following operations are defined:

      set-current-datetime
      system-restart
      system-shutdown"

My reaction is that this is a very limited set of operations. For example
how about system standby (enter power-saving mode)? Yes, I know that
creates the problem of how to wake the system up again, but there are
solutions to that problem (e.g. polling). I can imagine many vendor-specific
extensions in this area, too.

From lear@cisco.com  Sun Jan 19 00:30:25 2014
Return-Path: <lear@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA4F31A8034; Sun, 19 Jan 2014 00:30:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.139
X-Spam-Level: 
X-Spam-Status: No, score=-8.139 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hdt8IIL9HOGi; Sun, 19 Jan 2014 00:30:23 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id EA3FC1A1F7B; Sun, 19 Jan 2014 00:30:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5652; q=dns/txt; s=iport; t=1390120210; x=1391329810; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=jXVIzQrCfT0Oi3RVcfY3OxkoaM2eTqpycptsq1w1jqs=; b=R0VRpSzZ631asioSGD0cqQqbED1l93EQMfFpYj9tyWzjomujdeZ9dONj IHJQThe7xRTilOxYho/LtEJVBxeTYK9K7Gj4EcaInmkQ7nbNfyrdygPqz eMApbvR5TWVcX5SZLkqeVjoCaPhoUri+1LmwnuEpdxMkweANZS4fE8PIA o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFANeL21KQ/khL/2dsb2JhbABZgwuEC7g5gQYWdIIlAQEBAwEjVQEFCwsEHRYLAgIJAwIBAgFFBgEMAQcBAYd5CKdznCgXjn8Hgm+BSQSYIpIYgy47
X-IronPort-AV: E=Sophos;i="4.95,684,1384300800"; d="scan'208,217";a="3841992"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 19 Jan 2014 08:30:09 +0000
Received: from rtp-vpn4-845.cisco.com (rtp-vpn4-845.cisco.com [10.82.211.77]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0J8U4XI021152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);  Sun, 19 Jan 2014 08:30:07 GMT
Message-ID: <52DB8D0E.8000708@cisco.com>
Date: Sun, 19 Jan 2014 09:30:06 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, Scott Brim <scott.brim@gmail.com>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net>
In-Reply-To: <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative; boundary="------------050702060508070806070605"
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art telechat review of draft-farrell-perpass-attack-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 19 Jan 2014 08:30:26 -0000

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

Jari,

I oppose changes made to the document in the last round as stated
below.  If they remain, I would urge publication as Informational and
not BCP:

>    In particular, architectural decisions, including which existing
>    technology is re-used, may significantly impact the vulnerability of
>    a protocol to PM.  Those developing IETF specifications therefore
>    need to consider mitigating PM when making these architectural
>    decisions and be prepared to justify their decisions.  Getting
>    adequate, early review of architectural decisions including whether
>    appropriate mitigation of PM can be made is important.  Revisiting
>    these architectural decisions late in the process is very costly.

In the fact of a lack of common understanding regarding the threat, this
text can subject a working group to abuse and confusion.  This isn't
theoretical, as it has happened in the past that working group chairs
and area directors in particular have derailed efforts, setting
standardization and deployment of useful technology back years, and this
wasn't that long ago.

Let's make this discussion concrete with a few examples: the
implications may be that a working group chair or any participant
(although chairs are in a very good position to cause damage) could
insist that DHCP not be used to carry new attributes because there is no
common understanding of the scope of remediation that will be required. 
Before certain ADs roll their eyes, the discussion gets derailed as follows:

>> I propose the following DHCP option to configure my new frob.
<< But DHCP is transmitted in the clear.  Please justify this decision.
(or worse) << and by the way here is my very heavy weight alternative
that requires a valid cert chain
>> It's meant for the local wire.
<< But we don't know the scope of the attack.
...
...
>> Nevermind, I'll just use a vendor extension.  Goodbye.

Rinse and repeat with any other protocol that allows extensions.

It is fair to say that we should consider this threat at an
architectural level.  It's fair (albeit a truism) that finding design
flaws earlier in the process rather than later is less costly
(ENG-101).  Justification language like the above, however, is likely to
actively impede the IETF, as these sorts of things have in the past.

Eliot

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

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Jari,<br>
    <br>
    I oppose changes made to the document in the last round as stated
    below.Â  If they remain, I would urge publication as Informational
    and not BCP:<br>
    <br>
    <blockquote type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <pre class="newpage">   In particular, architectural decisions, including which existing
   technology is re-used, may significantly impact the vulnerability of
   a protocol to PM.  Those developing IETF specifications therefore
   need to consider mitigating PM when making these architectural
   decisions and be prepared to justify their decisions.  Getting
   adequate, early review of architectural decisions including whether
   appropriate mitigation of PM can be made is important.  Revisiting
   these architectural decisions late in the process is very costly.</pre>
    </blockquote>
    <br>
    In the fact of a lack of common understanding regarding the threat,
    this text can subject a working group to abuse and confusion.Â  This
    isn't theoretical, as it has happened in the past that working group
    chairs and area directors in particular have derailed efforts,
    setting standardization and deployment of useful technology back
    years, and this wasn't that long ago.<br>
    <br>
    Let's make this discussion concrete with a few examples: the
    implications may be that a working group chair or any participant
    (although chairs are in a very good position to cause damage) could
    insist that DHCP not be used to carry new attributes because there
    is no common understanding of the scope of remediation that will be
    required.Â  Before certain ADs roll their eyes, the discussion gets
    derailed as follows:<br>
    <br>
    &gt;&gt; I propose the following DHCP option to configure my new
    frob.<br>
    &lt;&lt; But DHCP is transmitted in the clear.Â  Please justify this
    decision.<br>
    (or worse) &lt;&lt; and by the way here is my very heavy weight
    alternative that requires a valid cert chain<br>
    &gt;&gt; It's meant for the local wire.<br>
    &lt;&lt; But we don't know the scope of the attack.<br>
    ...<br>
    ...<br>
    &gt;&gt; Nevermind, I'll just use a vendor extension.Â  Goodbye.<br>
    <br>
    Rinse and repeat with any other protocol that allows extensions.<br>
    <br>
    It is fair to say that we should consider this threat at an
    architectural level.Â  It's fair (albeit a truism) that finding
    design flaws earlier in the process rather than later is less costly
    (ENG-101).Â  Justification language like the above, however, is
    likely to actively impede the IETF, as these sorts of things have in
    the past.<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------050702060508070806070605--

From dromasca@avaya.com  Sun Jan 19 00:39:36 2014
Return-Path: <dromasca@avaya.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 940621AC404; Sun, 19 Jan 2014 00:39:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.137
X-Spam-Level: 
X-Spam-Status: No, score=-3.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QE-8s6JCaZih; Sun, 19 Jan 2014 00:39:34 -0800 (PST)
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 8B6831A1F7B; Sun, 19 Jan 2014 00:39:33 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqUOAP+N21LGmAcV/2dsb2JhbABZgkcjIThWpigDjDqIUYEGFnSCJQEBAQEDEhtMEAIBBgINAQMDAQEBCx0HMhQJCAIEDgUIARmHYwEMi3WRMKZoF40OgUAgEQYBgySBFASZVIU9iymDLYIq
X-IronPort-AV: E=Sophos;i="4.95,684,1384318800"; d="scan'208,217";a="39547489"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 19 Jan 2014 03:39:18 -0500
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 19 Jan 2014 03:29:21 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0158.001; Sun, 19 Jan 2014 09:39:15 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Olafur Gudmundsson <ogud@ogud.com>
Thread-Topic: [dane] Gen-ART Review of draft-ietf-dane-registry-acronyms-03
Thread-Index: AQHPEvv5AiogVuwlM0a8So6zPE/EZZqLvbyw
Date: Sun, 19 Jan 2014 08:39:14 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA243D0ED9@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA243CEC9A@AZ-FFEXMB04.global.avaya.com> <08A37247-FE33-4FC4-B56D-9925957D8920@ogud.com>
In-Reply-To: <08A37247-FE33-4FC4-B56D-9925957D8920@ogud.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: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA243D0ED9AZFFEXMB04globa_"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dane-registry-acronyms.all@tools.ietf.org" <draft-ietf-dane-registry-acronyms.all@tools.ietf.org>, "dane@ietf.org" <dane@ietf.org>
Subject: Re: [Gen-art] [dane] Gen-ART Review of draft-ietf-dane-registry-acronyms-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 19 Jan 2014 08:39:36 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA243D0ED9AZFFEXMB04globa_
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Looks good, thank you for addressing my comments.

Regards,

Dan


From: Olafur Gudmundsson [mailto:ogud@ogud.com]
Sent: =E9=E5=ED =E4 16 =E9=F0=E5=E0=F8 2014 22:46
To: Romascanu, Dan (Dan)
Cc: gen-art@ietf.org; draft-ietf-dane-registry-acronyms.all@tools.ietf.org;=
 dane@ietf.org
Subject: Re: [dane] Gen-ART Review of draft-ietf-dane-registry-acronyms-03


On Jan 15, 2014, at 10:11 AM, "Romascanu, Dan (Dan)" <dromasca@avaya.com<ma=
ilto:dromasca@avaya.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/GenArtfaq>.

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

Document: http://www.ietf.org/id/draft-ietf-dane-registry-acronyms-03.txt
Reviewer: Dan Romascanu
Review Date: 1/15/2014
IETF LC End Date: 1/23/2014
IESG Telechat date:

Summary:
Ready with issues

Major issues:
None =96 it=92s a simple, clear and useful document.

thanks



Minor issues:
1.       In Section 2.3 the I-D recommends that the values in reference col=
umn for SHA-256 and SHA-512 refer to [RFC 6698] while the IANA Consideratio=
ns section in RFC 6698 recommends and the registry entries in the TLSA Matc=
hing Types table athttp://www.iana.org/assignments/dane-parameters/dane-par=
ameters.xhtml  point to [RFC 6234].

Good Catch, fixed


2.       As this I-D updates the registries with a column for acronyms, it =
seems more accurate that the reference columns of all tables mention both  =
[RFC 6698] and [RFC XXXX] (this RFC)

I'm not sure if I agree, all this document does is to change the format of =
the registries it is not the definitions of any table entry.
But I think it would be good to change the reference for each of the regist=
ries to point to both RFC6698 and RFCXXXX

I propose adding to each registry sections the following text:
        "Update reference for this registry to include both [RFC6698] and [=
RFC-this-document]"


Nits/editorial comments:
In the Introduction section:

=91This document updates the IANA registry definition for TLSA
   record to add a column with acronym for each specified field=92
s/acronym/an acronym/


Fixed

thanks

          Olafur


--_000_9904FB1B0159DA42B0B887B7FA8119CA243D0ED9AZFFEXMB04globa_
Content-Type: text/html; charset="windows-1255"
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=3Dwindows-1=
255">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<base href=3D"x-msg://1557/"><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.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Consolas","serif";}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.EmailStyle21
	{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-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">Looks good, thank you for=
 addressing my 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">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"><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">Dan<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"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=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;"> Olafur G=
udmundsson [mailto:ogud@ogud.com]
<br>
<b>Sent:</b> <span lang=3D"HE" dir=3D"RTL">=E9=E5=ED</span><span dir=3D"LTR=
"></span><span dir=3D"LTR"></span>&nbsp;<span lang=3D"HE" dir=3D"RTL">=E4</=
span><span dir=3D"LTR"></span><span dir=3D"LTR"></span> 16
<span lang=3D"HE" dir=3D"RTL">=E9=F0=E5=E0=F8</span><span dir=3D"LTR"></spa=
n><span dir=3D"LTR"></span> 2014 22:46<br>
<b>To:</b> Romascanu, Dan (Dan)<br>
<b>Cc:</b> gen-art@ietf.org; draft-ietf-dane-registry-acronyms.all@tools.ie=
tf.org; dane@ietf.org<br>
<b>Subject:</b> Re: [dane] Gen-ART Review of draft-ietf-dane-registry-acron=
yms-03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On Jan 15, 2014, at 10:11 AM, &quot;Romascanu, Dan (=
Dan)&quot; &lt;<a href=3D"mailto:dromasca@avaya.com">dromasca@avaya.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<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;">&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;">&lt;<a href=3D"http://wiki.tools.ietf.o=
rg/area/gen/trac/wiki/GenArtfaq"><span style=3D"color:purple">http://wiki.t=
ools.ietf.org/area/gen/trac/wiki/GenArtfaq</span></a>&gt;.<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:<span class=3D"apple-converted=
-space">&nbsp;</span><a href=3D"http://www.ietf.org/id/draft-ietf-dane-regi=
stry-acronyms-03.txt"><span style=3D"color:purple">http://www.ietf.org/id/d=
raft-ietf-dane-registry-acronyms-03.txt</span></a><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: Dan Romascanu<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;">Review Date: 1/15/2014<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;">IETF LC End Date: 1/23/2014<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:<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;">Ready with issues<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;">Major issues:<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;">None =96 it=92s a simple, clear and use=
ful document.<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">thanks&nbsp;<o:p></o:p></p>
</div>
<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;">Minor issues:<o:p></o:p></span></p>
</div>
<div style=3D"margin-left:36.0pt">
<p class=3D"MsoNormal" style=3D"text-indent:-18.0pt"><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">1.</span>=
<span style=3D"font-size:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span c=
lass=3D"apple-converted-space">&nbsp;</span></span><span style=3D"font-size=
:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
 Section 2.3 the I-D recommends that the values in reference column for SHA=
-256 and SHA-512 refer to [RFC 6698] while the IANA Considerations section =
in RFC 6698 recommends and the registry entries in the TLSA Matching Types =
table at<a href=3D"http://www.iana.org/assignments/dane-parameters/dane-par=
ameters.xhtml"><span style=3D"color:purple">http://www.iana.org/assignments=
/dane-parameters/dane-parameters.xhtml</span></a><span class=3D"apple-conve=
rted-space">&nbsp;</span>&nbsp;point
 to [RFC 6234].<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">Good Catch, fixed&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div style=3D"margin-left:36.0pt">
<p class=3D"MsoNormal" style=3D"text-indent:-18.0pt"><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">2.</span>=
<span style=3D"font-size:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span c=
lass=3D"apple-converted-space">&nbsp;</span></span><span style=3D"font-size=
:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">As
 this I-D updates the registries with a column for acronyms, it seems more =
accurate that the reference columns of all tables mention both &nbsp;[RFC 6=
698] and [RFC XXXX] (this RFC)<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">I'm not sure if I agree, all this document does is t=
o change the format of the registries it is not the definitions of any tabl=
e entry.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">But I think it would be good to change the reference=
 for each of the registries to point to both RFC6698 and RFCXXXX&nbsp;<o:p>=
</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I propose adding to each registry sections the follo=
wing text:&nbsp;<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">&nbsp; &nbsp; &nbsp; &nbsp; &quot;Update reference f=
or this registry to include both&nbsp;[RFC6698] and [RFC-this-document]&quo=
t;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<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;">In the Introduction section:<o:p></o:p>=
</span></p>
</div>
<pre>=91This document updates the IANA registry definition for TLSA<o:p></o=
:p></pre>
<div>
<p class=3D"MsoNormal">&nbsp;&nbsp; record to add a column with acronym for=
 each specified field=92<span style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal">s/acronym/an acronym/<span style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">Fixed&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">thanks&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Olafur<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA243D0ED9AZFFEXMB04globa_--

From l.wood@surrey.ac.uk  Sun Jan 19 00:44:07 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A10E61AC404; Sun, 19 Jan 2014 00:44:07 -0800 (PST)
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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nfJWmohPcnER; Sun, 19 Jan 2014 00:44:01 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.173]) by ietfa.amsl.com (Postfix) with ESMTP id E0F641A1F7B; Sun, 19 Jan 2014 00:44:00 -0800 (PST)
Received: from [195.245.230.131:26705] by server-13.bemta-3.messagelabs.com id FB/D3-28603-3409BD25; Sun, 19 Jan 2014 08:43:47 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-8.tower-78.messagelabs.com!1390121026!34043651!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30602 invoked from network); 19 Jan 2014 08:43:46 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-8.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 19 Jan 2014 08:43:46 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Sun, 19 Jan 2014 08:43:46 +0000
From: <l.wood@surrey.ac.uk>
To: <lear@cisco.com>, <jari.arkko@piuha.net>, <scott.brim@gmail.com>
Date: Sun, 19 Jan 2014 08:40:47 +0000
Thread-Topic: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Index: Ac8U8MEok9fz/WlXRMWMb8h7UVlG7gAAWTgr
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346D3@EXMB01CMS.surrey.ac.uk>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net>, <52DB8D0E.8000708@cisco.com>
In-Reply-To: <52DB8D0E.8000708@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Sun, 19 Jan 2014 07:49:18 -0800
Cc: gen-art@ietf.org, ietf@ietf.org, draft-farrell-perpass-attack.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art telechat review of draft-farrell-perpass-attack-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 19 Jan 2014 08:44:07 -0000

+1. if you must publish this, publish as informational, as previous referen=
ced security docs have been.

A doc that says 'you just haven't considered security enough' is not specif=
ying the details or scope of a best current practice that can be sensibly f=
ollowed.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Eliot Lear [lear@cisco.com]
Sent: 19 January 2014 08:30
To: Jari Arkko; Scott Brim
Cc: gen-art; IETF discussion list; draft-farrell-perpass-attack.all@tools.i=
etf.org
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04

Jari,

I oppose changes made to the document in the last round as stated below.  I=
f they remain, I would urge publication as Informational and not BCP:


   In particular, architectural decisions, including which existing
   technology is re-used, may significantly impact the vulnerability of
   a protocol to PM.  Those developing IETF specifications therefore
   need to consider mitigating PM when making these architectural
   decisions and be prepared to justify their decisions.  Getting
   adequate, early review of architectural decisions including whether
   appropriate mitigation of PM can be made is important.  Revisiting
   these architectural decisions late in the process is very costly.

In the fact of a lack of common understanding regarding the threat, this te=
xt can subject a working group to abuse and confusion.  This isn't theoreti=
cal, as it has happened in the past that working group chairs and area dire=
ctors in particular have derailed efforts, setting standardization and depl=
oyment of useful technology back years, and this wasn't that long ago.

Let's make this discussion concrete with a few examples: the implications m=
ay be that a working group chair or any participant (although chairs are in=
 a very good position to cause damage) could insist that DHCP not be used t=
o carry new attributes because there is no common understanding of the scop=
e of remediation that will be required.  Before certain ADs roll their eyes=
, the discussion gets derailed as follows:

>> I propose the following DHCP option to configure my new frob.
<< But DHCP is transmitted in the clear.  Please justify this decision.
(or worse) << and by the way here is my very heavy weight alternative that =
requires a valid cert chain
>> It's meant for the local wire.
<< But we don't know the scope of the attack.
...
...
>> Nevermind, I'll just use a vendor extension.  Goodbye.

Rinse and repeat with any other protocol that allows extensions.

It is fair to say that we should consider this threat at an architectural l=
evel.  It's fair (albeit a truism) that finding design flaws earlier in the=
 process rather than later is less costly (ENG-101).  Justification languag=
e like the above, however, is likely to actively impede the IETF, as these =
sorts of things have in the past.

Eliot

From stbryant@cisco.com  Sun Jan 19 10:17:38 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DACE41ACC80; Sun, 19 Jan 2014 10:17:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level: 
X-Spam-Status: No, score=-15.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2GzlSu0Gz0Mq; Sun, 19 Jan 2014 10:17:37 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 56CE61A1F76; Sun, 19 Jan 2014 10:17:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2582; q=dns/txt; s=iport; t=1390155444; x=1391365044; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=r2ZehbOMaAjDpohEXUIssEz5nwHUijh0u1iphl4Zvdk=; b=HA34Qi9c678pKgWW8ruoDji2YjgOMA3NJNVqaYsa/wA83h9DcZEHf/6k LQYAOHTpAyr3zwulI81XTdW0lBOuhOsAhL2Zla15FvGQFwD+M3lKz/UC6 jM4uicQSeUcIh2InjGGAJXnfKSlbtyRofM3Hb9GgCjONqg/4OQSgO35U7 k=;
X-IronPort-AV: E=Sophos;i="4.95,685,1384300800"; d="scan'208";a="298305467"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-7.cisco.com with ESMTP; 19 Jan 2014 18:17:24 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0JIHOhO010078 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 19 Jan 2014 18:17:24 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Sun, 19 Jan 2014 12:17:23 -0600
From: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
To: Eliot Lear <lear@cisco.com>
Thread-Topic: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Index: AQHPFI3E/nItobbHr0ey+uLOGq3uepqLWhMAgADCtgCAAD+Akg==
Date: Sun, 19 Jan 2014 18:17:22 +0000
Message-ID: <DAE99191-66E7-4C50-AF2B-24FDEE21EB7C@cisco.com>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net>, <52DB8D0E.8000708@cisco.com>
In-Reply-To: <52DB8D0E.8000708@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-perpass-attack.all@tools.ietf.org" <draft-farrell-perpass-attack.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-Art telechat review of draft-farrell-perpass-attack-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 19 Jan 2014 18:17:39 -0000

I share these concern.

Stewart

Sent from my iPad

> On 19 Jan 2014, at 08:30, "Eliot Lear" <lear@cisco.com> wrote:
>=20
> Jari,
>=20
> I oppose changes made to the document in the last round as stated below. =
 If they remain, I would urge publication as Informational and not BCP:
>=20
>>    In particular, architectural decisions, including which existing
>>    technology is re-used, may significantly impact the vulnerability of
>>    a protocol to PM.  Those developing IETF specifications therefore
>>    need to consider mitigating PM when making these architectural
>>    decisions and be prepared to justify their decisions.  Getting
>>    adequate, early review of architectural decisions including whether
>>    appropriate mitigation of PM can be made is important.  Revisiting
>>    these architectural decisions late in the process is very costly.
>=20
> In the fact of a lack of common understanding regarding the threat, this =
text can subject a working group to abuse and confusion.  This isn't theore=
tical, as it has happened in the past that working group chairs and area di=
rectors in particular have derailed efforts, setting standardization and de=
ployment of useful technology back years, and this wasn't that long ago.
>=20
> Let's make this discussion concrete with a few examples: the implications=
 may be that a working group chair or any participant (although chairs are =
in a very good position to cause damage) could insist that DHCP not be used=
 to carry new attributes because there is no common understanding of the sc=
ope of remediation that will be required.  Before certain ADs roll their ey=
es, the discussion gets derailed as follows:
>=20
> >> I propose the following DHCP option to configure my new frob.
> << But DHCP is transmitted in the clear.  Please justify this decision.
> (or worse) << and by the way here is my very heavy weight alternative tha=
t requires a valid cert chain
> >> It's meant for the local wire.
> << But we don't know the scope of the attack.
> ...
> ...
> >> Nevermind, I'll just use a vendor extension.  Goodbye.
>=20
> Rinse and repeat with any other protocol that allows extensions.
>=20
> It is fair to say that we should consider this threat at an architectural=
 level.  It's fair (albeit a truism) that finding design flaws earlier in t=
he process rather than later is less costly (ENG-101).  Justification langu=
age like the above, however, is likely to actively impede the IETF, as thes=
e sorts of things have in the past.
>=20
> Eliot

From stephen.farrell@cs.tcd.ie  Sun Jan 19 10:55:21 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A1781ADF8A; Sun, 19 Jan 2014 10:55:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s_P8riCdnLxM; Sun, 19 Jan 2014 10:55:18 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 08FD51ADF84; Sun, 19 Jan 2014 10:55:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 1363CBE24; Sun, 19 Jan 2014 18:54:58 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a4+05lCTJm2z; Sun, 19 Jan 2014 18:54:56 +0000 (GMT)
Received: from [10.87.48.5] (unknown [86.46.27.208]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1B3C5BE25; Sun, 19 Jan 2014 18:54:54 +0000 (GMT)
Message-ID: <52DC1F71.80102@cs.tcd.ie>
Date: Sun, 19 Jan 2014 18:54:41 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>, Jari Arkko <jari.arkko@piuha.net>,  Scott Brim <scott.brim@gmail.com>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com>
In-Reply-To: <52DB8D0E.8000708@cisco.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art telechat review of draft-farrell-perpass-attack-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 19 Jan 2014 18:55:21 -0000

On 01/19/2014 08:30 AM, Eliot Lear wrote:
> Jari,
> 
> I oppose changes made to the document in the last round as stated
> below.  If they remain, I would urge publication as Informational and
> not BCP:
> 
>>    In particular, architectural decisions, including which existing
>>    technology is re-used, may significantly impact the vulnerability of
>>    a protocol to PM.  Those developing IETF specifications therefore
>>    need to consider mitigating PM when making these architectural
>>    decisions and be prepared to justify their decisions.  Getting
>>    adequate, early review of architectural decisions including whether
>>    appropriate mitigation of PM can be made is important.  Revisiting
>>    these architectural decisions late in the process is very costly.

I'm not particularly fussed if this is included or not. I'm ok with
Jari and/or the IESG figuring it out however they do.

> In the fact of a lack of common understanding regarding the threat, this
> text can subject a working group to abuse and confusion.  This isn't
> theoretical, as it has happened in the past that working group chairs
> and area directors in particular have derailed efforts, setting
> standardization and deployment of useful technology back years, and this
> wasn't that long ago.

To be honest that seems both overblown and unjustified to me.
I'm also entirely unconvinced by the example below and by your
analysis of how text that says nothing much new is somehow at
the same time horribly threatening. 'Abuse' and setting things
back years and the rest seem to me to bear no relationship to
the text in question. Best I can guess is that your fear of
over-zealous ADs causes you to read this text in some way that I
can't figure out, but that argument has been had already for
earlier text which seems to me entirely as strong as this text.

And that's why I included this in -04, it seemed to have support
from others and consideration of architecture is reasonable
and your objection is afaics nothing to do with the text itself
and hence invalid.

But as I said, I'm fine with this being resolved either way.

Cheers,
S.

> 
> Let's make this discussion concrete with a few examples: the
> implications may be that a working group chair or any participant
> (although chairs are in a very good position to cause damage) could
> insist that DHCP not be used to carry new attributes because there is no
> common understanding of the scope of remediation that will be required. 
> Before certain ADs roll their eyes, the discussion gets derailed as follows:
> 
>>> I propose the following DHCP option to configure my new frob.
> << But DHCP is transmitted in the clear.  Please justify this decision.
> (or worse) << and by the way here is my very heavy weight alternative
> that requires a valid cert chain
>>> It's meant for the local wire.
> << But we don't know the scope of the attack.
> ...
> ...
>>> Nevermind, I'll just use a vendor extension.  Goodbye.
> 
> Rinse and repeat with any other protocol that allows extensions.
> 
> It is fair to say that we should consider this threat at an
> architectural level.  It's fair (albeit a truism) that finding design
> flaws earlier in the process rather than later is less costly
> (ENG-101).  Justification language like the above, however, is likely to
> actively impede the IETF, as these sorts of things have in the past.
> 
> Eliot
> 

From dhc@dcrocker.net  Sun Jan 19 11:48:16 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DEAC1ADF78; Sun, 19 Jan 2014 11:48:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ppw2ixrsXhCn; Sun, 19 Jan 2014 11:48:14 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A39231ADF31; Sun, 19 Jan 2014 11:48:14 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s0JJlhYQ023839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 19 Jan 2014 11:47:46 -0800
Message-ID: <52DC2BD0.4000803@dcrocker.net>
Date: Sun, 19 Jan 2014 11:47:28 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>, Jari Arkko <jari.arkko@piuha.net>, Scott Brim <scott.brim@gmail.com>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com>
In-Reply-To: <52DB8D0E.8000708@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 19 Jan 2014 11:47:47 -0800 (PST)
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
Subject: [Gen-art] Consideration vs. Blocking (was Re: Gen-Art telechat review of draft-farrell-perpass-attack-04)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 19 Jan 2014 19:48:16 -0000

On 1/19/2014 12:30 AM, Eliot Lear wrote:
> It is fair to say that we should consider this threat at an
> architectural level.  It's fair (albeit a truism) that finding design
> flaws earlier in the process rather than later is less costly
> (ENG-101).  Justification language like the above, however, is likely to
> actively impede the IETF, as these sorts of things have in the past.


If I'm understanding this exchange, it hinges on the distinction between 
due consideration vs. appropriate design response.

Pressing to have work "consider" an issue early and thoughtfully makes 
sense for any topic that is as important as pervasive monitoring. 
Having IESG evaluation produce a blocking Discuss because an AD feels 
that the consideration was not sufficient or the resulting design flawed 
in terms of this issue is another matter.

The point I'm seeing Eliot make is that we don't have enough community 
understanding of the topic to be sure what constitutes appropriate 
design consideration.  So, in the face of such minimal community 
understanding, an AD's blocking progress would be whimsical at best.

Based on how new this topic is -- we don't even yet have stable and 
shared terminology for the problem space nor the solution space -- 
Eliot's concern isn't just valid, it's important.

We /do/ have a long track record of well-intentioned ADs asserting 
Discusses that are reasonable in the abstract but impractical for work 
in the IETF, especially when the topic is frankly still vague.

While the formal status of this document is relevant to the concern, the 
more important issue I see is our community sense that work going 
forward needs serious effort, but also an understanding that the basis 
for blocking specification needs to be extremely cautiously applied.

By way of trying to be practical about being practical, I'll suggest 
that any IESG blocks based on a concern about pervasive monitoring needs 
to reflect a consensus view of the IESG, not just the concern of a 
single AD....

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From l.wood@surrey.ac.uk  Sun Jan 19 13:34:51 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3A581ADF96; Sun, 19 Jan 2014 13:34:51 -0800 (PST)
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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DWwr4ArznaNa; Sun, 19 Jan 2014 13:34:48 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.162]) by ietfa.amsl.com (Postfix) with ESMTP id D74501ADF92; Sun, 19 Jan 2014 13:34:47 -0800 (PST)
Received: from [195.245.230.131:63330] by server-2.bemta-3.messagelabs.com id B0/A7-17329-8E44CD25; Sun, 19 Jan 2014 21:34:32 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-5.tower-78.messagelabs.com!1390167270!33925865!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29620 invoked from network); 19 Jan 2014 21:34:30 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-5.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 19 Jan 2014 21:34:30 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Sun, 19 Jan 2014 21:34:29 +0000
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>, <lear@cisco.com>, <jari.arkko@piuha.net>, <scott.brim@gmail.com>
Date: Sun, 19 Jan 2014 21:34:28 +0000
Thread-Topic: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Index: Ac8VSApEqInOZnNTRByucu6FJ5deEQAFBss1
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346D4@EXMB01CMS.surrey.ac.uk>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com>,<52DC1F71.80102@cs.tcd.ie>
In-Reply-To: <52DC1F71.80102@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: gen-art@ietf.org, ietf@ietf.org, draft-farrell-perpass-attack.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art telechat review of draft-farrell-perpass-attack-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 19 Jan 2014 21:34:51 -0000

>> In the fact of a lack of common understanding regarding the threat, this
>> text can subject a working group to abuse and confusion.  This isn't
>> theoretical, as it has happened in the past that working group chairs
>> and area directors in particular have derailed efforts, setting
>> standardization and deployment of useful technology back years, and this
>> wasn't that long ago.

> To be honest that seems both overblown and unjustified to me.
> I'm also entirely unconvinced by the example below and by your
> analysis of how text that says nothing much new is somehow at
> the same time horribly threatening. 'Abuse' and setting things
> back years and the rest seem to me to bear no relationship to
> the text in question.

Stephen,

you might recall interrupting a couple of early presentations we
made on Saratoga to raise a (in hindsight pretty much spurious
and irrelevant) security issue. We could see that you would block
any further work there, and we moved Saratoga away from DTNRG.

DTNRG has since produced a security protocol, rather than
exploring the DTN problem space. It has, in my opinion, set
DTN research back years. DTNRG considered security at
every point.

I view this as an early example of Eliot's doubts.
If you'd had this document then, you'd be pointing at that as well.

The concern is justified. Raise the 'but it's not secure! It's
snoopable!' cry too much, and watch work either die in process,
or leave the IETF.

(Perpass still isn't a working group, is it?)

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stephen Farrell [stephen.fa=
rrell@cs.tcd.ie]
Sent: 19 January 2014 18:54
To: Eliot Lear; Jari Arkko; Scott Brim
Cc: gen-art; IETF discussion list; draft-farrell-perpass-attack.all@tools.i=
etf.org
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04

On 01/19/2014 08:30 AM, Eliot Lear wrote:
> Jari,
>
> I oppose changes made to the document in the last round as stated
> below.  If they remain, I would urge publication as Informational and
> not BCP:
>
>>    In particular, architectural decisions, including which existing
>>    technology is re-used, may significantly impact the vulnerability of
>>    a protocol to PM.  Those developing IETF specifications therefore
>>    need to consider mitigating PM when making these architectural
>>    decisions and be prepared to justify their decisions.  Getting
>>    adequate, early review of architectural decisions including whether
>>    appropriate mitigation of PM can be made is important.  Revisiting
>>    these architectural decisions late in the process is very costly.

I'm not particularly fussed if this is included or not. I'm ok with
Jari and/or the IESG figuring it out however they do.

> In the fact of a lack of common understanding regarding the threat, this
> text can subject a working group to abuse and confusion.  This isn't
> theoretical, as it has happened in the past that working group chairs
> and area directors in particular have derailed efforts, setting
> standardization and deployment of useful technology back years, and this
> wasn't that long ago.

To be honest that seems both overblown and unjustified to me.
I'm also entirely unconvinced by the example below and by your
analysis of how text that says nothing much new is somehow at
the same time horribly threatening. 'Abuse' and setting things
back years and the rest seem to me to bear no relationship to
the text in question. Best I can guess is that your fear of
over-zealous ADs causes you to read this text in some way that I
can't figure out, but that argument has been had already for
earlier text which seems to me entirely as strong as this text.

And that's why I included this in -04, it seemed to have support
from others and consideration of architecture is reasonable
and your objection is afaics nothing to do with the text itself
and hence invalid.

But as I said, I'm fine with this being resolved either way.

Cheers,
S.

>
> Let's make this discussion concrete with a few examples: the
> implications may be that a working group chair or any participant
> (although chairs are in a very good position to cause damage) could
> insist that DHCP not be used to carry new attributes because there is no
> common understanding of the scope of remediation that will be required.
> Before certain ADs roll their eyes, the discussion gets derailed as follo=
ws:
>
>>> I propose the following DHCP option to configure my new frob.
> << But DHCP is transmitted in the clear.  Please justify this decision.
> (or worse) << and by the way here is my very heavy weight alternative
> that requires a valid cert chain
>>> It's meant for the local wire.
> << But we don't know the scope of the attack.
> ...
> ...
>>> Nevermind, I'll just use a vendor extension.  Goodbye.
>
> Rinse and repeat with any other protocol that allows extensions.
>
> It is fair to say that we should consider this threat at an
> architectural level.  It's fair (albeit a truism) that finding design
> flaws earlier in the process rather than later is less costly
> (ENG-101).  Justification language like the above, however, is likely to
> actively impede the IETF, as these sorts of things have in the past.
>
> Eliot
>

From huitema@microsoft.com  Sun Jan 19 16:49:32 2014
Return-Path: <huitema@microsoft.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1CD21A0013; Sun, 19 Jan 2014 16:49:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vdlQayAmpYgP; Sun, 19 Jan 2014 16:49:30 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0206.outbound.protection.outlook.com [207.46.163.206]) by ietfa.amsl.com (Postfix) with ESMTP id 5869E1A000D; Sun, 19 Jan 2014 16:49:30 -0800 (PST)
Received: from DM2PR03CA008.namprd03.prod.outlook.com (10.141.52.156) by BN1PR03MB236.namprd03.prod.outlook.com (10.255.200.28) with Microsoft SMTP Server (TLS) id 15.0.847.13; Mon, 20 Jan 2014 00:49:24 +0000
Received: from BY2FFO11FD044.protection.gbl (2a01:111:f400:7c0c::161) by DM2PR03CA008.outlook.office365.com (2a01:111:e400:2414::28) with Microsoft SMTP Server (TLS) id 15.0.847.13 via Frontend Transport; Mon, 20 Jan 2014 00:49:23 +0000
Received: from mail.microsoft.com (131.107.125.37) by BY2FFO11FD044.mail.protection.outlook.com (10.1.14.229) with Microsoft SMTP Server (TLS) id 15.0.847.12 via Frontend Transport; Mon, 20 Jan 2014 00:49:23 +0000
Received: from TK5EX14MBXC303.redmond.corp.microsoft.com ([169.254.3.123]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.03.0174.002; Mon, 20 Jan 2014 00:48:52 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Eliot Lear <lear@cisco.com>, Jari Arkko <jari.arkko@piuha.net>, Scott Brim <scott.brim@gmail.com>
Thread-Topic: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Index: AQHPFI3ZW+Ddq54mlkqF92wuCJ/egpqK9X4AgADCtgCAAQvBAA==
Date: Mon, 20 Jan 2014 00:48:50 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA360668B6@TK5EX14MBXC303.redmond.corp.microsoft.com>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com>
In-Reply-To: <52DB8D0E.8000708@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.36]
Content-Type: multipart/alternative; boundary="_000_C91E67751B1EFF41B857DE2FE1F68ABA360668B6TK5EX14MBXC303r_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(199002)(189002)(20776003)(44976005)(65816001)(63696002)(83322001)(6806004)(85306002)(66066001)(15975445006)(74366001)(74662001)(19580395003)(93136001)(74502001)(86362001)(53806001)(512874002)(93516002)(31966008)(47446002)(92566001)(74876001)(50986001)(77096001)(77982001)(47736001)(81342001)(2656002)(80022001)(51856001)(59766001)(19300405004)(79102001)(56816005)(74706001)(81686001)(76796001)(85852003)(90146001)(33656001)(87936001)(76482001)(69226001)(56776001)(54316002)(15202345003)(81542001)(81816001)(83072002)(71186001)(84326002)(4396001)(49866001)(87266001)(55846006)(54356001)(92726001)(46102001)(16236675002)(47976001)(80976001)(76786001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN1PR03MB236; H:mail.microsoft.com; CLIP:131.107.125.37; FPR:; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 00979FCB3A
X-OriginatorOrg: microsoft.com
X-Mailman-Approved-At: Sun, 19 Jan 2014 17:00:33 -0800
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-perpass-attack.all@tools.ietf.org" <draft-farrell-perpass-attack.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-Art telechat review of draft-farrell-perpass-attack-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 00:49:33 -0000

--_000_C91E67751B1EFF41B857DE2FE1F68ABA360668B6TK5EX14MBXC303r_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

Pj4gTmV2ZXJtaW5kLCBJJ2xsIGp1c3QgdXNlIGEgdmVuZG9yIGV4dGVuc2lvbi4gIEdvb2RieWUu
DQoNCj4gUmluc2UgYW5kIHJlcGVhdCB3aXRoIGFueSBvdGhlciBwcm90b2NvbCB0aGF0IGFsbG93
cyBleHRlbnNpb25zLg0KDQpUaGF04oCZcyBhIHZlcnkgcHJhY3RpY2FsIGNvbmNlcm4uIElmIHN0
YW5kYXJkIHNvbHV0aW9ucyBhcmUgdG9vIGhhcmQgdG8gZGV2ZWxvcCwgdGhlbiBwcm9kdWN0cyB3
aWxsIHVzZSBwcm9wcmlldGFyeSBzb2x1dGlvbnMgaW5zdGVhZCwgYW5kIHdlIHdpbGwgbm90IGhh
dmUgd29uIG11Y2ggZGVmZW5zZSBhZ2FpbnN0IHBlcnZhc2l2ZSBtb25pdG9yaW5nLg0KDQpJIHBl
cnNvbmFsbHkgYWdyZWUgd2l0aCB0aGUgZ2VuZXJhbCBpZGVhIHRoYXQgbmV3IGRldmVsb3BtZW50
cyBzaG91bGQgY29uc2lkZXIgUE0gYXMgcGFydCBvZiB0aGUgdGhyZWF0IG1vZGVsLiBCdXQgRWxs
aW90IG1ha2VzIGEgZ29vZCBwb2ludC4gSW4gcHJhY3RpY2UsIHRoZSBnb29kIHJldmlld3MgZG9u
4oCZdCBzdG9wIGF0IG5lZ2F0aXZlIGFkdmljZSwg4oCcZG9u4oCZdCBkbyB0aGlzIGJlY2F1c2Ug
dGhlIHNwb29rcyB3aWxsIHNub29wLuKAnSBUaGUgYmV0dGVyIHJldmlld3MgZ28gb24gd2l0aCDi
gJxkbyB0aGlzIGluc3RlYWQsIGl0IGlzIGFsbW9zdCBhcyBlYXN5IHRvIHVzZSBhbmQgaXQgcHJv
dmlkZXMgbXVjaCBiZXR0ZXIgcHJpdmFjeS7igJ0NCg0KSXQgd291bGQgYmUgaW50ZXJlc3Rpbmcg
dG8gbGlzdCB0aGUgc3BlY2lmaWMgcGF0dGVybnMgdGhhdCBhcmUgbW9zdCBsaWtlbHkgdG8gdHJp
Z2dlciB0aGUg4oCcYmFkIGJlY2F1c2Ugb2YgUE3igJ0gY29tbWVudHMsIGFuZCB0byBkZXZlbG9w
IHNlY3VyZSBhbHRlcm5hdGl2ZXMuIEZyb20gd2hhdCBJIHNlZSwgdGhlcmUgc2VlbXMgdG8gYmUg
dHdvIGJpZyBvZmZlbmRlcnMsIGxvZ3MgYW5kIGNvbmZpZ3VyYXRpb24uIFNvIG1heWJlIHdlIHNo
b3VsZCBkZXZlbG9wIGEgc2ltcGxlIHdheSB0byBhbm9ueW1pemUgbG9ncywgYW5kIGEgc2VjdXJl
IHdheSB0byBnZXQgY29uZmlndXJhdGlvbiBkYXRh4oCmDQoNCi0tIENocmlzdGlhbiBIdWl0ZW1h
DQoNCg0K

--_000_C91E67751B1EFF41B857DE2FE1F68ABA360668B6TK5EX14MBXC303r_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLCJzZXJpZiI7DQoJY29sb3I6YmxhY2s7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGlu
aw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1NjNDMTsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3MjsNCgl0ZXh0LWRlY29yYXRp
b246dW5kZXJsaW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxl
LWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJv
dHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIg
TmV3IjsNCgljb2xvcjpibGFjazt9DQpzcGFuLkhUTUxQcmVmb3JtYXR0ZWRDaGFyDQoJe21zby1z
dHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIjsNCglmb250LWZhbWlseTpD
b25zb2xhczsNCgljb2xvcjpibGFjazt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUt
dHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYi
Ow0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhw
b3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6
ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5X
b3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0
ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEw
MjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo
YXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAv
Pg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgYmdj
b2xvcj0id2hpdGUiIGxhbmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+
DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyZn
dDsgTmV2ZXJtaW5kLCBJJ2xsIGp1c3QgdXNlIGEgdmVuZG9yIGV4dGVuc2lvbi4mbmJzcDsgR29v
ZGJ5ZS48YnI+DQo8YnI+DQo8c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jmd0OyA8L3NwYW4+
Umluc2UgYW5kIHJlcGVhdCB3aXRoIGFueSBvdGhlciBwcm90b2NvbCB0aGF0IGFsbG93cyBleHRl
bnNpb25zLjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlRoYXTigJlzIGEgdmVy
eSBwcmFjdGljYWwgY29uY2Vybi4gSWYgc3RhbmRhcmQgc29sdXRpb25zIGFyZSB0b28gaGFyZCB0
byBkZXZlbG9wLCB0aGVuIHByb2R1Y3RzIHdpbGwgdXNlIHByb3ByaWV0YXJ5IHNvbHV0aW9ucyBp
bnN0ZWFkLCBhbmQgd2Ugd2lsbCBub3QgaGF2ZSB3b24NCiBtdWNoIGRlZmVuc2UgYWdhaW5zdCBw
ZXJ2YXNpdmUgbW9uaXRvcmluZy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkkgcGVyc29uYWxseSBhZ3JlZSB3aXRoIHRo
ZSBnZW5lcmFsIGlkZWEgdGhhdCBuZXcgZGV2ZWxvcG1lbnRzIHNob3VsZCBjb25zaWRlciBQTSBh
cyBwYXJ0IG9mIHRoZSB0aHJlYXQgbW9kZWwuIEJ1dCBFbGxpb3QgbWFrZXMgYSBnb29kIHBvaW50
LiBJbiBwcmFjdGljZSwgdGhlDQogZ29vZCByZXZpZXdzIGRvbuKAmXQgc3RvcCBhdCBuZWdhdGl2
ZSBhZHZpY2UsIOKAnGRvbuKAmXQgZG8gdGhpcyBiZWNhdXNlIHRoZSBzcG9va3Mgd2lsbCBzbm9v
cC7igJ0gVGhlIGJldHRlciByZXZpZXdzIGdvIG9uIHdpdGgg4oCcZG8gdGhpcyBpbnN0ZWFkLCBp
dCBpcyBhbG1vc3QgYXMgZWFzeSB0byB1c2UgYW5kIGl0IHByb3ZpZGVzIG11Y2ggYmV0dGVyIHBy
aXZhY3ku4oCdPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj5JdCB3b3VsZCBiZSBpbnRlcmVzdGluZyB0byBsaXN0IHRoZSBz
cGVjaWZpYyBwYXR0ZXJucyB0aGF0IGFyZSBtb3N0IGxpa2VseSB0byB0cmlnZ2VyIHRoZSDigJxi
YWQgYmVjYXVzZSBvZiBQTeKAnSBjb21tZW50cywgYW5kIHRvIGRldmVsb3Agc2VjdXJlIGFsdGVy
bmF0aXZlcy4NCiBGcm9tIHdoYXQgSSBzZWUsIHRoZXJlIHNlZW1zIHRvIGJlIHR3byBiaWcgb2Zm
ZW5kZXJzLCBsb2dzIGFuZCBjb25maWd1cmF0aW9uLiBTbyBtYXliZSB3ZSBzaG91bGQgZGV2ZWxv
cCBhIHNpbXBsZSB3YXkgdG8gYW5vbnltaXplIGxvZ3MsIGFuZCBhIHNlY3VyZSB3YXkgdG8gZ2V0
IGNvbmZpZ3VyYXRpb24gZGF0YeKApjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RDttc28tbGlnYXR1cmVzOnN0YW5kYXJkIj4t
LSBDaHJpc3RpYW4gSHVpdGVtYTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_C91E67751B1EFF41B857DE2FE1F68ABA360668B6TK5EX14MBXC303r_--

From meral.shirazipour@ericsson.com  Sun Jan 19 23:20:27 2014
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 832771A005B for <gen-art@ietfa.amsl.com>; Sun, 19 Jan 2014 23:20:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r67k_NC1oKGQ for <gen-art@ietfa.amsl.com>; Sun, 19 Jan 2014 23:20:26 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1591A0042 for <gen-art@ietf.org>; Sun, 19 Jan 2014 23:20:26 -0800 (PST)
X-AuditID: c6180641-b7fbd8e0000011cc-bf-52dcce3a3f50
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 30.51.04556.A3ECCD25; Mon, 20 Jan 2014 08:20:26 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0387.000; Mon, 20 Jan 2014 02:20:25 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-pwe3-mpls-tp-cv-adv.all@tools.ietf.org" <draft-ietf-pwe3-mpls-tp-cv-adv.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-pwe3-mpls-tp-cv-adv-04
Thread-Index: Ac8Vr7wGoqi48k7LT7ia84dhhgO+eg==
Date: Mon, 20 Jan 2014 07:20:25 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A32D06251@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.11]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D06251eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPLMWRmVeSWpSXmKPExsUyuXSPn67VuTtBBsv/GFo82NfPZnH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvj9sk+xoLb8hWzds5gbGCcJdPFyMkhIWAi saV/OQuELSZx4d56NhBbSOAIo8Tf74FdjFxA9nJGiTmffjCCJNgELCS2/37OCpIQEZjGKLH7 /j6gBAeHsICXxNk5XCA1IgKBEts3n2eBsPUkbr38AGazCKhKdJxtYwexeQV8Jb5M7QaLMwIt /n5qDROIzSwgLnHryXwmiIMEJJbsOc8MYYtKvHz8jxXCVpL4+Hs+O8haZoF8iTdfKiFGCkqc nPmEZQKj0Cwkk2YhVM1CUgVRoiOxYPcnNghbW2LZwtfMMPaZA4+ZkMUXMLKvYuQoLU4ty003 MtzECIyEYxJsjjsYF3yyPMQozcGiJM775a1zkJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbG vl9bk0XTW65O3bXXOeFl8A6jw1/uR785eK/q847A1a09l3v3Lu5s6p4k/2n3lalzWjUEeC11 91qezQr4+uC33AUe/Z3btEMjUlWX/FC4JfQyZtZOsXMRR84f07C5vPvc3DdHTj8uKeW+JrVA uevj4SciE14oV/05s5XB2CylbtH6V8Y9pUtuWCqxFGckGmoxFxUnAgBSrOqyUgIAAA==
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-pwe3-mpls-tp-cv-adv-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 07:20:27 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D06251eusaamb107erics_
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-pwe3-mpls-tp-cv-adv-04
Reviewer: Meral Shirazipour
Review Date: 2014-01-19
IETF LC End Date: 2014-01-16
IESG Telechat date: 2014-01-23

Summary: This draft is ready for publication as a Standards Track RFC.



Best Regards,
Meral
---
Meral Shirazipour
Ericsson Research
www.ericsson.com

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at &lt;
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt; .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please wait for direction from your document shepher=
d or AD before posting a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-pwe3-mpls-tp-cv-adv-04<o:p></o:=
p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2014-01-19<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2014-01-16<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2014-01-23<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready for publication as a St=
andards Track RFC.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D06251eusaamb107erics_--

From alexey.melnikov@isode.com  Mon Jan 20 03:12:49 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D61A91A011B for <gen-art@ietfa.amsl.com>; Mon, 20 Jan 2014 03:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q4SO3gyzpFWp for <gen-art@ietfa.amsl.com>; Mon, 20 Jan 2014 03:12:47 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id BD9F71A0118 for <gen-art@ietf.org>; Mon, 20 Jan 2014 03:12:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1390216367; d=isode.com; s=selector; i=@isode.com; bh=zcLlROWNU+o0UdchuL8YjTEYkGESgc1d3md62s/Pt0Y=; 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=JjC8kMKMGIuWv0P28hY66qo5gkeucrXsWJWD6PhnFi25/NwiAhYudU+Ru6THlL4LH3AkjI w5t4IHaIy288sGETPlIozwrEfEYoNFsWxNcdkW70lB45HpY4fPXEj4aJ96YUp3izM0RLRN hZc0go9Gksm9NmIGZJeW0Ok7V8rpMjE=;
Received: from [172.17.128.75] (richard.isode.com [62.3.217.249])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <Ut0ErgBvgYWd@statler.isode.com>; Mon, 20 Jan 2014 11:12:47 +0000
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <52DD04AE.8070604@isode.com>
Date: Mon, 20 Jan 2014 11:12:46 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: draft-ietf-isis-rfc6326bis.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
Subject: [Gen-art] Gen-ART review of draft-ietf-isis-rfc6326bis-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 11:12:50 -0000

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

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

Document: draft-ietf-isis-rfc6326bis-01
Reviewer: Alexey Melnikov
Review Date: 2014-01-20
IETF LC End Date: 2014-01-22
IESG Telechat date: 2014-01-23


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

Major issues: None

Minor issues:

o  Label: This carries the fine-grained label identifier for all
       subsequent MAC addresses in this sub-TLV, or the value zero if no
       label is specified.


I fully admit ignorance of the topic, but what is exactly "fine-grained 
label" and where is the exact format defined? If it is defined later in 
the document, can you please add a forward reference. If it is defined 
in another document, can you please add a reference to that.


In Sections 2.2.4 and 2.3.1:

What are the requirements on backward compatibility between different 
versions of TRILL. Are TLVs formats supported for a version N also valid 
for version N+M? If you have any implied assumptions, please state them 
in the document.



Nits/editorial comments: None


From alexey.melnikov@isode.com  Mon Jan 20 03:26:08 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 094431A012B for <gen-art@ietfa.amsl.com>; Mon, 20 Jan 2014 03:26:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jWLJjP81Z5Fr for <gen-art@ietfa.amsl.com>; Mon, 20 Jan 2014 03:26:05 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 8F53E1A0122 for <gen-art@ietf.org>; Mon, 20 Jan 2014 03:26:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1390217165; d=isode.com; s=selector; i=@isode.com; bh=/0Lb2Fakez5/m8Bk8vwWjOL5DDufAv/PKy5rvjO+uGM=; 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=GM7Stj+iYVYLdZSEc5mYg5/zZGCbcqmheRdIxlnqpGsRyiRDZj6oHBMzhijQw6ghJ2SYS5 6PY8gQgKRrYWDUOb2y6+frBr4lyS2mZLdQEXV6upKAyUAYFiuIYT/Ho5oojGsygJ+tR0Ng bsEcqja+1lruGFvQxRTpDtFJe3t0lmU=;
Received: from [172.17.128.75] (richard.isode.com [62.3.217.249])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <Ut0HzAAIP795@waldorf.isode.com>; Mon, 20 Jan 2014 11:26:05 +0000
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <52DD07CC.6070703@isode.com>
Date: Mon, 20 Jan 2014 11:26:04 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: Andrew Allen <aallen@blackberry.com>
References: <52037931.5070602@isode.com> <BBF5DDFE515C3946BC18D733B20DAD2338E18E6A@XMB104ADS.rim.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338E18E6A@XMB104ADS.rim.net>
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>, "draft-montemurro-gsma-imei-urn.all@tools.ietf.org" <draft-montemurro-gsma-imei-urn.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-montemurro-gsma-imei-urn-16
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 11:26:08 -0000

On 17/09/2013 17:15, Andrew Allen wrote:
> Alexy
>
> Thank you for the review.
>
> My responses below prepended with [AA]
>
> Andrew
>
> -----Original Message-----
> From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]
> Sent: Thursday, August 08, 2013 6:56 AM
> To: draft-montemurro-gsma-imei-urn.all@tools.ietf.org
> Cc: <gen-art@ietf.org> Team
> Subject: Gen-ART LC Review of draft-montemurro-gsma-imei-urn-16
>
> 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.
>
> [AA] Will add the RFC 3629 reference
In -19 I see:

3.  Namespace Registration Template

    Rules for Lexical Equivalence:

       Any identifier in 'gsma' NSS can be compared using the normal
       mechanisms for percent-encoded UTF-8 strings (see RFC 3629 [10]) .

The reference should be [8], not [10]. This just demonstrates why 
numeric references are a bad idea ;-).
> 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.
>
> [AA] As indicated in an earlier response I will make this normative


From d3e3e3@gmail.com  Mon Jan 20 08:45:29 2014
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07E4F1A01C1 for <gen-art@ietfa.amsl.com>; Mon, 20 Jan 2014 08:45:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H68Q9TkaOLEs for <gen-art@ietfa.amsl.com>; Mon, 20 Jan 2014 08:45:27 -0800 (PST)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 7BC5D1A01BE for <gen-art@ietf.org>; Mon, 20 Jan 2014 08:45:27 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id i7so5570200oag.36 for <gen-art@ietf.org>; Mon, 20 Jan 2014 08:45:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0WYVHmGd+du8UBk+AXywcUcIGZM4PaK7uTPvc1yHNys=; b=T8v7Q+epQLcCduH0ujiWuU4dP3VtKSkO4CQzZUnzo+G2Zrfk9ijiigMovSxzBJmblZ 8E4QMDF3JEgdwgzChreILYO+pInJO1js/TWjdMIsHYXWbylxL0SIDb66p1Qvkzjya2N1 1Ah5n9QnB9aa96+joMdaQBOBQsbXV+LFb2UnVbwjIyDgHLtAXbqp9QXQOSbg6CxZWeey Vnk/vZpaUAuRhgVN5M/lK0kgqV/dzWrcGpsgE2JdG3W43UKUCnNxmt/wNXqG154FfNuM niwMiSRB3Q4xLfvXmKOzWF3pXeoIBnEsWUiHZXfX3Mf1iFK7ZvnRlFX+N4GZJYEyYnTX xKAg==
X-Received: by 10.182.114.132 with SMTP id jg4mr16664409obb.29.1390236327407;  Mon, 20 Jan 2014 08:45:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.33.102 with HTTP; Mon, 20 Jan 2014 08:45:07 -0800 (PST)
In-Reply-To: <52DD04AE.8070604@isode.com>
References: <52DD04AE.8070604@isode.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 20 Jan 2014 11:45:07 -0500
Message-ID: <CAF4+nEFuPdVmyqa5x0QwFOysLB14eGzPM8gLRy6wb4yMXuzLJw@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-isis-rfc6326bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-isis-rfc6326bis-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 16:45:29 -0000

Hi Alexey,

Thanks for your review, see below:

On Mon, Jan 20, 2014 at 6:12 AM, 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>.
>
> Please resolve these comments along with any other Last Call
> comments you may receive.
>
> Document: draft-ietf-isis-rfc6326bis-01
> Reviewer: Alexey Melnikov
> Review Date: 2014-01-20
> IETF LC End Date: 2014-01-22
> IESG Telechat date: 2014-01-23
>
>
> Summary: This draft is nearly ready for publication as a standard track RFC.
>
> Major issues: None
>
> Minor issues:
>
> o  Label: This carries the fine-grained label identifier for all
>       subsequent MAC addresses in this sub-TLV, or the value zero if no
>       label is specified.
>
> I fully admit ignorance of the topic, but what is exactly
> "fine-grained label" and where is the exact format defined? If it is
> defined later in the document, can you please add a forward
> reference. If it is defined in another document, can you please add
> a reference to that.

Fine grained labels are specified in draft-ietf-trill-fine-labeling-07,
which is an approved standard track draft in the RFC Editor's
queue. Adding a reference to it here would be good.

> In Sections 2.2.4 and 2.3.1:
>
> What are the requirements on backward compatibility between different
> versions of TRILL. Are TLVs formats supported for a version N also valid for
> version N+M? If you have any implied assumptions, please state them in the
> document.

There are no explicit requirements. Incremental changes and
improvements are generally handed with capability bits or the
presence/absence of data strucutres in control messages. A version
change would probably indicate a pretty major modification but, since
these version numbers are within IS-IS TLVs, I would say that
implicitly the intent is to stay with the IS-IS PDU structure for the
control plane.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Nits/editorial comments: None

From alexey.melnikov@isode.com  Mon Jan 20 10:11:50 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7BDE1A0169 for <gen-art@ietfa.amsl.com>; Mon, 20 Jan 2014 10:11:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LnmhvqM6qI6u for <gen-art@ietfa.amsl.com>; Mon, 20 Jan 2014 10:11:48 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 4B2771A0224 for <gen-art@ietf.org>; Mon, 20 Jan 2014 10:11:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1390241501; d=isode.com; s=selector; i=@isode.com; bh=6KEUy/N5FK46wMgdNuzxTy+pcyNZPQN9WBgXNVlYOd0=; 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=UBfbepk6NvpdrFLvt2Iig7SNVpgH+AuGMx1rrZSSqfI0ct5Wo1E2wJZ5F7E3oNU8W2nZPd u+4U/aJoVnnXO5UCCI0eG5v99R2oxTw7SVx++du+FhpFnkvSfFu+/Q5fk3TWODAHVcRKrR App6qjgCRHR2bwj+S8rTjiDWHgCc/cY=;
Received: from [172.16.1.29] (richard.isode.com [62.3.217.249])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <Ut1m2wAIP0z6@waldorf.isode.com>; Mon, 20 Jan 2014 18:11:41 +0000
Message-ID: <52DD66D7.7020107@isode.com>
Date: Mon, 20 Jan 2014 18:11:35 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
To: Donald Eastlake <d3e3e3@gmail.com>
References: <52DD04AE.8070604@isode.com> <CAF4+nEFuPdVmyqa5x0QwFOysLB14eGzPM8gLRy6wb4yMXuzLJw@mail.gmail.com>
In-Reply-To: <CAF4+nEFuPdVmyqa5x0QwFOysLB14eGzPM8gLRy6wb4yMXuzLJw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-isis-rfc6326bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-isis-rfc6326bis-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 18:11:51 -0000

Hi Donald,

On 20/01/2014 16:45, Donald Eastlake wrote:
> Hi Alexey,
>
> Thanks for your review, see below:
>
> On Mon, Jan 20, 2014 at 6:12 AM, 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>.
>>
>> Please resolve these comments along with any other Last Call
>> comments you may receive.
>>
>> Document: draft-ietf-isis-rfc6326bis-01
>> Reviewer: Alexey Melnikov
>> Review Date: 2014-01-20
>> IETF LC End Date: 2014-01-22
>> IESG Telechat date: 2014-01-23
>>
>>
>> Summary: This draft is nearly ready for publication as a standard track RFC.
>>
>> Major issues: None
>>
>> Minor issues:
>>
>> o  Label: This carries the fine-grained label identifier for all
>>        subsequent MAC addresses in this sub-TLV, or the value zero if no
>>        label is specified.
>>
>> I fully admit ignorance of the topic, but what is exactly
>> "fine-grained label" and where is the exact format defined? If it is
>> defined later in the document, can you please add a forward
>> reference. If it is defined in another document, can you please add
>> a reference to that.
> Fine grained labels are specified in draft-ietf-trill-fine-labeling-07,
> which is an approved standard track draft in the RFC Editor's
> queue. Adding a reference to it here would be good.
Sounds great. Thanks.
>> In Sections 2.2.4 and 2.3.1:
>>
>> What are the requirements on backward compatibility between different
>> versions of TRILL. Are TLVs formats supported for a version N also valid for
>> version N+M? If you have any implied assumptions, please state them in the
>> document.
> There are no explicit requirements. Incremental changes and
> improvements are generally handed with capability bits or the
> presence/absence of data strucutres in control messages. A version
> change would probably indicate a pretty major modification but, since
> these version numbers are within IS-IS TLVs, I would say that
> implicitly the intent is to stay with the IS-IS PDU structure for the
> control plane.
I think the document should state that. Also, if you want any messages 
to be unchanged (fully or partially) irrespectively of version numbers, 
you should state that too.

Best Regards,
Alexey


From brian.e.carpenter@gmail.com  Mon Jan 20 11:05:45 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 572251A0259 for <gen-art@ietfa.amsl.com>; Mon, 20 Jan 2014 11:05:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ppz0n31bAGHe for <gen-art@ietfa.amsl.com>; Mon, 20 Jan 2014 11:05:43 -0800 (PST)
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 4596E1A0251 for <gen-art@ietf.org>; Mon, 20 Jan 2014 11:05:43 -0800 (PST)
Received: by mail-pd0-f175.google.com with SMTP id w10so1906873pde.6 for <gen-art@ietf.org>; Mon, 20 Jan 2014 11:05:43 -0800 (PST)
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:references:in-reply-to:content-type :content-transfer-encoding; bh=DjvLYPJRK+8X+Z6OSO03Oa+t3PLCjQ2lkNdXCn+EM/c=; b=Yp9WemXLqM3jDFkVyllyk+vk6Q/Gk96N/ZBc4+5euq9Y9iDHNIjKRhZonVOjoHTpnv Pqn7BgHOYfuztNrrb5IVtv5WniYiFncQDNMmpMoj4WvN0v7SDTbIppaDumQJYslM1Mno N6yaL0MiSxMSnvnG1EWV+KuCtL3MDREf8P/HQ2VzWiQIF/4IT2ME3FdUs/bBVPHqwnKW /0NVmd+pdsXOPg1XpZHGFGKHcbgalYLXil7te7Lgi/uccipmHXZIGlEqG9kD85lCjrV7 mxNrxmpfHUAiHA+3fDHfxzmqmPolH/Pi+FuVc1qFRwaurwKhH0G1BgPp5vGSGMnM0dRm rs9Q==
X-Received: by 10.68.138.226 with SMTP id qt2mr20046587pbb.65.1390244743525; Mon, 20 Jan 2014 11:05:43 -0800 (PST)
Received: from [192.168.178.23] (58.199.69.111.dynamic.snap.net.nz. [111.69.199.58]) by mx.google.com with ESMTPSA id sx8sm9701094pab.5.2014.01.20.11.05.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Jan 2014 11:05:42 -0800 (PST)
Message-ID: <52DD7386.9020502@gmail.com>
Date: Tue, 21 Jan 2014 08:05:42 +1300
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-netmod-system-mgmt.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
References: <52DB0241.1040401@gmail.com>
In-Reply-To: <52DB0241.1040401@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-netmod-system-mgmt-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 19:05:45 -0000

I've looked at the -11 draft that just came out and it's fine.
I understand that the document has been deferred from this week's
agenda, so if I'm asked to review it again the answer will
be "Ready".

Regards
   Brian

On 19/01/2014 11:37, Brian E Carpenter 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 wait for direction from your document shepherd
> or AD before posting a new version of the draft.
> 
> Document: draft-ietf-netmod-system-mgmt-10.txt
> Reviewer: Brian Carpenter
> Review Date: 2014-01-19
> IETF LC End Date: 2014-01-22
> IESG Telechat date: 2014-01-23
> 
> Summary:  Almost ready
> --------
> 
> Comments:
> ---------
> 
> Since the version hasn't been updated yet I haven't changed the
> review, but the authors' proposed changes are fine. Please
> let me know if the -11 version comes out before the telechat.
> 
> I haven't checked the yang syntax in detail. At first glance,
> it looks good.
> 
> 
> Minor Issues:
> ------------
> 
> "2.1.  System Identification
> 
>    There are many common properties used to identify devices, operating
>    systems, software versions, etc. that need to be supported in the
>    system data module.  These objects are defined as operational state
>    data and the information returned by the server is intended to be
>    specific to the device vendor."
> 
> Does "server" mean the NETCONF server?
> 
> "2.2.  System Time Management
> 
>    The management of the date and time used by the system need to be
>    supported.  Use of one or more NTP servers to automatically set the
>    system date and time need to be possible.  Utilization of the
>    Timezone database [RFC6557] also need to be supported.  It should be
>    possible for the server, as well as clients, to configure the system
>    to use NTP."
> 
> Again, does this mean the NETCONF server? Also, which clients? This is
> the first time the document mentions clients.
> 
> "2.3.  User Authentication
> 
> ...It should be possible for the server, as well as
>    clients, to configure the system authentication properties."
> 
> Same comment as for 2.2. Also, how does the network administrator enforce
> a specific strength of authentication? It seems as though the clients can
> choose to downgrade security.
> 
> "2.4.  DNS Resolver
> 
>    The configuration of the DNS resolver within the system containing
>    the NETCONF server is required to control how domain names are
>    resolved."
> 
> This is very hard to parse and could mean several things. Does it
> mean that it MUST be possible to configure the DNS resolver?
> (And I wonder what happens if the device is running mDNS?)
> 
> "3.6.  System Control
> 
>    The following operations are defined:
> 
>       set-current-datetime
>       system-restart
>       system-shutdown"
> 
> My reaction is that this is a very limited set of operations. For example
> how about system standby (enter power-saving mode)? Yes, I know that
> creates the problem of how to wake the system up again, but there are
> solutions to that problem (e.g. polling). I can imagine many vendor-specific
> extensions in this area, too.
> 

From curtis@ipv6.occnc.com  Mon Jan 20 21:17:35 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A199D1A0036; Mon, 20 Jan 2014 21:17:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.137
X-Spam-Level: 
X-Spam-Status: No, score=-0.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_LIST=2.3, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qj_ujqFTuoYX; Mon, 20 Jan 2014 21:17:33 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id CE4C11A002F; Mon, 20 Jan 2014 21:17:32 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0L5HKkg051900; Tue, 21 Jan 2014 00:17:20 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401210517.s0L5HKkg051900@maildrop2.v6ds.occnc.com>
To: "Peter Yee" <peter@akayla.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Fri, 17 Jan 2014 23:21:28 -0800." <02d101cf141d$ea1a8f50$be4fadf0$@akayla.com>
Date: Tue, 21 Jan 2014 00:17:20 -0500
Cc: draft-ietf-mpls-multipath-use.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-multipath-use-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 05:17:35 -0000

In message <02d101cf141d$ea1a8f50$be4fadf0$@akayla.com>
"Peter Yee" writes:
> 
> 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-multipath-use-03
> Reviewer: Peter Yee
> Review Date: January-16-2014
> IETF LC End Date: January-17-2014
> IESG Telechat date: January-23-2014
>  
> 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 document discusses multipath MPLS operations and describes the means of
> supporting MPLS as a server layer for MPLS-TP and vice versa.  It lists
> requirements and implications for these operations.
>  
>  
> Nits:
>  
> General nits:
>  
> Make all references to the expansion of ECMP read "Equal-Cost Multipath" for
> consistency with RFC 2991.

ECMP is expanded on first use in compliance with RFC Editor quidelines
for abbreviations.  ECMP is also expanded on first use within each
section where it is used with the exception of one place where ECMP is
contained in a verbatim excerpt in a quote from RFC6374.

> In the usage RFCxxxx, use a space between RFC and xxxx except when used as a
> reference, e.g., [RFCxxxx].

Nine instances were found and fixed, including two instancees of
"pre-RFC6790" changed to "pre- RFC 6790".  I don't think that one
looks right as "pre-RFC 6790".

> There are many unexplained acronyms without definition or reference.  Unless
> these are abundantly clear to most readers, expand them on first usage and
> provide a reference pointer where feasible.

The following acronyms were found and checked for expansion on first
use:

  Listed in RFC Editor guidelines on acronyms as well known:

    BGP GMPLS IANA IEEE IP IS-IS ITU-T MPLS OSPF

  Used only in verbatim quoted text (expanded in one use)

    E-LSP L-LSP

  Already expanded on first use

    ECMP EL ELI FA GAL ILM LACP LAG LFA LM LSP LSR PHB PSC RSVP-TE

  Changed to be expanded on first use

    IPFRR MPLS-TP OAM TC

Many of the acronyms are explained in the referenced documents.  The
intended audience should be familiar with this set of acronyms.

Almost all of these acronyms are in the RFC Editor list with only a
few exceptions.  The RFC Editor may want to add the following:

  Traffic CLass (TC) and cite RFC 5462 (Multiprotocol Label Switching
  (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class"
  Field),

  Loss Measurement (LM) and and Delay Measurement (DM) and cite RFC
  6374 (Packet Loss and Delay Measurement for MPLS Networks).  The
  abbreviations LM and DM are also used in other OAM documents from
  other SDO (with the same expansion).

  Entropy Label Indicator (ELI) and Entropy Label (EL) and cite RFC
  6790 (The Use of Entropy Labels in MPLS Forwarding).

This document cites the above three RFCs and expands each of these
acronyms on first use (except DM which is not used).

> Specific nits:
>  
> Page 1, Abstract, 2nd paragraph, 1st sentence: change "MPLS Entropy label"
> to "the MPLS Entropy Label".

In this instance the phrase "MPLS Entropy Labels" is the name of the
technique and the short name of RFC 6790 (plural in the RFC 6790 short
name).  The abstract cannot contain citations but I can put "RFC 6790"
in parens.

I suggest s/Using MPLS Entropy label/Using MPLS Entropy Labels (RFC 6790)/
and if there are no objections will make that change.

> Page 2, Section 1, 1st paragraph,  1st sentence: delete the comma after
> "traffic".

OK.

> Page 2, Section 1, 1st paragraph, last sentence: change "load split" to
> "load splitting".

OK.

> Page 2, Section 1, 2nd paragraph, last sentence: hyphenate "fate sharing".

OK

> Page 3, Section 1, 1st paragraph, 1st sentence: hyphenate "equal cost".

I do not think equal cost needs to be hyphenated.  In the technique
Equal-Cost Multipath (ECMP) the choice to hyphenate was made for
historic reasons, but for example in the RFC Editor list of acroyms
"Unequal Loss Protection (ULP)" does not hyphenate "unequal loss".

No ambiguity is created in the instances where hyphenation is not used
and equal cost is consistently not hyphenated in this document.

> Page 3, definition of "Loop Free Alternate Paths (LFA)": hyphenate "Loop
> Free".

OK.

> Page 3, definition of "Loop Free Alternate Paths (LFA), 1st sentence: change
> the terminating period to a colon.

OK.

> Page 4, Section 3.1, 1st paragraph, 1st sentence: change "date" to "data".

OK.

> Page 4, Section 3.1, 1st paragraph, 2nd sentence: change the terminating
> period to a colon.

OK.

> Page 5, 1st full paragraph, 1st sentence: insert "Section 3.1.1" between
> "[RFC5960]" and "paragraph 3".  Capitalize "paragraph".

OK.

> Page 5, 1st full paragraph, 3rd sentence: same as previous instructions.

OK.

> Page 5, 2nd paragraph, 2nd sentence: change ' "Section 1 Introduction"' to '
> Section 1 ("Introduction")'.

OK.

> Page 6, 1st paragraph, 3rd sentence: change ' "Section 2.9.4 Equal Cost
> Multipath") to ' Section 2.9.4 ("Equal Cost Multipath")'.

OK.

> Page 6, Section 3.2, 1st paragraph, 1st sentence: hyphenate "MPLS-TP
> conformant" and delete the comma after "multipath".

In existing RFCs, including some that are quite recent, a spec acronym
followed by the word conformant is both hyphenated and not hyphenated.

I prefer not to hyphenate because the acronym itself is already
hyphentated and no ambiguity is created either way.

> Page 7, 2nd paragraph, 2nd sentence: change "A" to "An".

OK.  In future reviews please include the noun that follows.

> Page 7, 2nd paragraph, 5th and 6th sentences: change all occurrences of
> "LSP" to "LSPs".

I added the "s" where "LSP" should have been plural in that paragraph.

> Page 7, 3rd paragraph, 2nd sentence: change "LSP" to "LSPs".

OK.

> Page 7, 4th paragraph, 2nd sentence: change "LSR" to "LSRs".

OK.

> Page 7, 5th paragraph: change all occurrences of "LSP" to "LSPs".

I added the "s" where "LSP" should have been plural in that paragraph.

> Page 7, 5th paragraph last sentence: change "co-existance" to "coexistence".

OK.

> Page 8, 1st partial paragraph, 2nd full sentence: change all occurrences of
> "LSP" to "LPSs" and change "LSR" to "LSRs".

I added the "s" where "LSP" or "LSR" should have been plural in that
paragraph.

> Page 8, 2nd full paragraph: change all occurrences of "LSP" to "LSPs".

I added the "s" where "LSP" should have been plural in that paragraph.

> Page 8, 4th paragraph, 1st sentence: change "LSP" to "LSPs".

I added the "s" where "LSP" should have been plural in that paragraph.

> Page 8, 4th paragraph, 2nd sentence: is there a quantitative definition for
> "very infrequent" that can be substituted or explained?

Any time load balancing occurs there is a chance of reordering and TCP
generally backs off (sans SACK support) when such an event occurs as
it would back off if a single packet was dropped.  The frequency of
load balancing has to be kept low to avoid this, but how low is the
topic of debate and will certainly vary among services with different
expectations (for example financial transactions vs plain old
Internet).

For the purpose of the discussion here the phrase "except during very
infrequent transitions due to load balancing" acknowledges that load
balance causes some imperfection, but does not try to quantify it.

> Page 8, 4th paragraph, 3rd sentence: change "presense" to "presence".
> Insert "a" before "GAL".

OK.

> Page 9, 1st partial paragraph: delete "label" following "EL" in two
> locations.

OK.

> Page 9, Section 4, 1st paragraph, 1st sentence: change first "LSP" to
> "LSPs".  Change "a MPLS-TP" to "an MPLS-TP" unless MPLS is pronounced liked
> "mipples" or something similar and not just spelled out.

OK.

> Page 9, Section 4, 2nd paragraph: replace all occurrences of "LSP" with
> "LSPs".

OK.

> Page 9, Section 4, 2nd paragraph, 2nd sentence: insert "the" between "in"
> and "number".

OK.

> Page 9, Section 4, 2nd paragraph, 3rd sentence: change "ILM" to "ILMs".

OK.

> Page 9, Section 4, 3rd paragraph, 1st sentence: change "Server Layer" to
> "server layer" for consistency of usage.  Insert "of" between "use" and
> "MPLS-TP".  Change "LSP" to "LSPs".

OK.

> Page 9, Section 4, 3rd paragraph, 4th sentence: change "LSP" to "LSPs".

OK.

> Page 9, Section 4, 3rd paragraph, 5th sentence: change "LSP" to "LSPs".
> Change "capacity" to "capacities".  Insert "generally" before "not integer"
> unless it is always the case that the capacity is not a multiple of 10 Gb/s.

OK.

> Page 9, Section 4, 4th paragraph, 1st sentence: change "Server Layer" to
> "server layer".

OK.

> Page 10, Section 6, 2nd paragraph, 2nd sentence: hyphenate "high end" and
> append a comma after that.  Hyphenate "packet processing".

OK.

> Page 10, Section 6, 3rd paragraph, last sentence: same as previous
> instructions.

OK.

> Page 10, Section 8, 1st sentence: insert "a" between "of" and "framework".

OK.

> I'm not particularly knowledgeable about MPLS, so I'm unable to express much
> about the correctness of the operational points made in the document.
>  
> 		-Peter Yee

OK.  But you certainly did read this thoroughly and pick out a lot of
nits.  Thanks for doing so.

Curtis

From jari.arkko@piuha.net  Tue Jan 21 07:30:53 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D23851A014A for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 07:30:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71JZilx4EUJL for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 07:30:51 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5523F1A0199 for <gen-art@ietf.org>; Tue, 21 Jan 2014 07:30:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E0ED22CEB1; Tue, 21 Jan 2014 17:30:50 +0200 (EET)
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 sCNtPrG5qeWy; Tue, 21 Jan 2014 17:30:46 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E16302CC48; Tue, 21 Jan 2014 17:30:46 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F2406584BA472@MX15A.corp.emc.com>
Date: Tue, 21 Jan 2014 17:30:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <60C55DB1-4D56-4031-8A79-D56D71B55246@piuha.net>
References: <201401131355.s0DDtd4t028318@givry.fdupont.fr> <F5063677821E3B4F81ACFB7905573F2406584BA472@MX15A.corp.emc.com>
To: Kathleen Moriarty <kathleen.moriarty@emc.com>, "Sean P. Turner" <turners@ieca.com>
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-moriarty-pkcs12v1-1.all@tools.ietf.org" <draft-moriarty-pkcs12v1-1.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-moriarty-pkcs12v1-1-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 15:30:54 -0000

Thanks for your review, Francis, and for your edits, Kathleen.

Do you Kathleen or Sean think that Francis' comment on strengthening the =
security considerations would be something that you should address?

jari

On Jan 13, 2014, at 6:02 PM, "Moriarty, Kathleen" =
<kathleen.moriarty@emc.com> wrote:

> Hi Francis,
>=20
> I went to update your comments in my draft version and in thinking =
about it more, I agree with the current text on the public/private =
order.  As I read it, the referenced keys are discussed for the keys =
that validate and I assume you read it as the creation of a signature or =
to encrypt.  I'm going to leave that as-is.
>=20
> Thanks,
> Kathleen
>=20
> -----Original Message-----
> From: Moriarty, Kathleen=20
> Sent: Monday, January 13, 2014 9:42 AM
> To: 'Francis.Dupont@fdupont.fr'; gen-art@ietf.org
> Cc: draft-moriarty-pkcs12v1-1.all@tools.ietf.org
> Subject: RE: review of draft-moriarty-pkcs12v1-1-03.txt
>=20
> Thank you for the review, Francis.
>=20
> Once this version is published, change control and copyright is =
transferred to the IETF.  The next version of this document will work to =
improve known issues.
>=20
> I will make the change from public/private to private/public as noted, =
that makes sense.  I would imagine it was only written that way as the =
key pairs are typically referred to in that order as opposed to the =
original author thinking through the sentence as you had done.
>=20
> I have a few other edits to include and will have this ready before =
the end of the week.
>=20
> Thank you,
> Kathleen
>=20
> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]=20
> Sent: Monday, January 13, 2014 8:56 AM
> To: gen-art@ietf.org
> Cc: draft-moriarty-pkcs12v1-1.all@tools.ietf.org
> Subject: review of draft-moriarty-pkcs12v1-1-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-moriarty-pkcs12v1-1-03.txt
> Reviewer: Francis Dupont
> Review Date: 20130104
> IETF LC End Date: 20130110
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: (not really technical)
> PKCS#12 was subject to concerns from teh cryptography community, in =
particular from Peter Gutmann, based on:
> - its (too) high complexity (BTW IMHO it is a legitimate concern:
> complexity is not wellcome for a security device)
> - (related to the previous item) its possible misuse with private  =
key, summarized by this famous warning in OpenSSL FAQ:
> "Occasionally someone suggests using a command such as:
>=20
> openssl pkcs12 -export -out cacert.p12 -in cacert.pem -inkey cakey.pem
>=20
> DO NOT DO THIS! This command will give away your CAs private key and =
reduces its security to zero: allowing anyone to forge certificates in =
whatever name they choose."
>=20
> Unfortunately I can't see how we can address these concerns in the =
document. Perhaps with a stronger security considerations section?
>=20
> Nits/editorial comments:
> - TOC page 3 and F page 29: Acknowledgements -> Acknowledgments
>=20
> - 1 page 4 in:
>      The most secure of the privacy
>   and integrity modes require the source and destination platforms to
>   have trusted public/private key pairs usable for digital signatures
>   and encryption, respectively.
>=20
>  respectively suggests the same order but the private key is used to
>  sign and the public key to encrypt. I propose to swap keys, i.e.,
>  to use "private/public" key pairs.
>=20
> - 5.1 5 B page 16: i.e. -> i.e.,
>=20
> - a full example should have been wellcome but IMHO it is far too late
>  (and there are a lot of tools able to produce examples if needed :-).
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From kathleen.moriarty@emc.com  Tue Jan 21 07:38:42 2014
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9F331A033F for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 07:38:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jRUSrmCC9CEd for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 07:38:40 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 234561A02F5 for <gen-art@ietf.org>; Tue, 21 Jan 2014 07:38:39 -0800 (PST)
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com [10.106.48.159]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0LFcMwh013525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Jan 2014 10:38:23 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com s0LFcMwh013525
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390318704; bh=oaetPW0o+hSR5mGN+xiX38/70ds=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=E1JPVxm2MccpJRnO4ImoMrTQpW7h5O1s77P7zZVZL6QTEkeK9tGkHowGsjI0V6kjJ VJzHQfRnZcSNvKxjjwO+AlIbKF56FJULzgG/QMVb67H+uFLFIWaEib5NjWycdp+s5T VxRe9POGZtzsmlgq7S0Mh5db5Wa4veDgRZvxeo6M=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com s0LFcMwh013525
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd55.lss.emc.com (RSA Interceptor); Tue, 21 Jan 2014 10:38:08 -0500
Received: from mxhub17.corp.emc.com (mxhub17.corp.emc.com [10.254.93.46]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0LFc87q007766 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Jan 2014 10:38:08 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub17.corp.emc.com ([10.254.93.46]) with mapi; Tue, 21 Jan 2014 10:38:07 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Jari Arkko <jari.arkko@piuha.net>, "Sean P. Turner" <turners@ieca.com>
Date: Tue, 21 Jan 2014 10:38:06 -0500
Thread-Topic: [Gen-art] review of draft-moriarty-pkcs12v1-1-03.txt
Thread-Index: Ac8WvcpDc1k7zPpOSx6B4zfGj4XgAgAAH38A
Message-ID: <F5063677821E3B4F81ACFB7905573F2406584BAC24@MX15A.corp.emc.com>
References: <201401131355.s0DDtd4t028318@givry.fdupont.fr> <F5063677821E3B4F81ACFB7905573F2406584BA472@MX15A.corp.emc.com> <60C55DB1-4D56-4031-8A79-D56D71B55246@piuha.net>
In-Reply-To: <60C55DB1-4D56-4031-8A79-D56D71B55246@piuha.net>
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: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: DLM_1, public
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-moriarty-pkcs12v1-1.all@tools.ietf.org" <draft-moriarty-pkcs12v1-1.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-moriarty-pkcs12v1-1-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 15:38:42 -0000

Hi Jari,

Since this document is meant to transfer change control to the IETF, RSA wo=
uld prefer to leave the document in-tact to match their published version a=
s much as possible.  There is IETF interest in starting a draft as soon as =
this is published to correct the well-known issues.  We would prefer to tak=
e that approach and I am working to make sure we have at least one resource=
 to edit the new document who has the background to make the changes and th=
ere may be others.

Thank you,
Kathleen

-----Original Message-----
From: Jari Arkko [mailto:jari.arkko@piuha.net]=20
Sent: Tuesday, January 21, 2014 10:31 AM
To: Moriarty, Kathleen; Sean P. Turner
Cc: Francis.Dupont@fdupont.fr; gen-art@ietf.org; draft-moriarty-pkcs12v1-1.=
all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-moriarty-pkcs12v1-1-03.txt

Thanks for your review, Francis, and for your edits, Kathleen.

Do you Kathleen or Sean think that Francis' comment on strengthening the se=
curity considerations would be something that you should address?

jari

On Jan 13, 2014, at 6:02 PM, "Moriarty, Kathleen" <kathleen.moriarty@emc.co=
m> wrote:

> Hi Francis,
>=20
> I went to update your comments in my draft version and in thinking about =
it more, I agree with the current text on the public/private order.  As I r=
ead it, the referenced keys are discussed for the keys that validate and I =
assume you read it as the creation of a signature or to encrypt.  I'm going=
 to leave that as-is.
>=20
> Thanks,
> Kathleen
>=20
> -----Original Message-----
> From: Moriarty, Kathleen
> Sent: Monday, January 13, 2014 9:42 AM
> To: 'Francis.Dupont@fdupont.fr'; gen-art@ietf.org
> Cc: draft-moriarty-pkcs12v1-1.all@tools.ietf.org
> Subject: RE: review of draft-moriarty-pkcs12v1-1-03.txt
>=20
> Thank you for the review, Francis.
>=20
> Once this version is published, change control and copyright is transferr=
ed to the IETF.  The next version of this document will work to improve kno=
wn issues.
>=20
> I will make the change from public/private to private/public as noted, th=
at makes sense.  I would imagine it was only written that way as the key pa=
irs are typically referred to in that order as opposed to the original auth=
or thinking through the sentence as you had done.
>=20
> I have a few other edits to include and will have this ready before the e=
nd of the week.
>=20
> Thank you,
> Kathleen
>=20
> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
> Sent: Monday, January 13, 2014 8:56 AM
> To: gen-art@ietf.org
> Cc: draft-moriarty-pkcs12v1-1.all@tools.ietf.org
> Subject: review of draft-moriarty-pkcs12v1-1-03.txt
>=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-moriarty-pkcs12v1-1-03.txt
> Reviewer: Francis Dupont
> Review Date: 20130104
> IETF LC End Date: 20130110
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: (not really technical)
> PKCS#12 was subject to concerns from teh cryptography community, in parti=
cular from Peter Gutmann, based on:
> - its (too) high complexity (BTW IMHO it is a legitimate concern:
> complexity is not wellcome for a security device)
> - (related to the previous item) its possible misuse with private  key, s=
ummarized by this famous warning in OpenSSL FAQ:
> "Occasionally someone suggests using a command such as:
>=20
> openssl pkcs12 -export -out cacert.p12 -in cacert.pem -inkey cakey.pem
>=20
> DO NOT DO THIS! This command will give away your CAs private key and redu=
ces its security to zero: allowing anyone to forge certificates in whatever=
 name they choose."
>=20
> Unfortunately I can't see how we can address these concerns in the docume=
nt. Perhaps with a stronger security considerations section?
>=20
> Nits/editorial comments:
> - TOC page 3 and F page 29: Acknowledgements -> Acknowledgments
>=20
> - 1 page 4 in:
>      The most secure of the privacy
>   and integrity modes require the source and destination platforms to
>   have trusted public/private key pairs usable for digital signatures
>   and encryption, respectively.
>=20
>  respectively suggests the same order but the private key is used to =20
> sign and the public key to encrypt. I propose to swap keys, i.e.,  to=20
> use "private/public" key pairs.
>=20
> - 5.1 5 B page 16: i.e. -> i.e.,
>=20
> - a full example should have been wellcome but IMHO it is far too late =20
> (and there are a lot of tools able to produce examples if needed :-).
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art



From jari.arkko@piuha.net  Tue Jan 21 07:50:55 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4620F1A019F; Tue, 21 Jan 2014 07:50:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t0gjyZIyck5w; Tue, 21 Jan 2014 07:50:54 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CBC091A018D; Tue, 21 Jan 2014 07:50:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 64E692CEB1; Tue, 21 Jan 2014 17:50:53 +0200 (EET)
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 JYeLQJPySbMX; Tue, 21 Jan 2014 17:50:52 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D8B4E2CC48; Tue, 21 Jan 2014 17:50:52 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201401210517.s0L5HKkg051900@maildrop2.v6ds.occnc.com>
Date: Tue, 21 Jan 2014 17:50:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E736F946-88D0-4262-B2DD-C62FC461A885@piuha.net>
References: <201401210517.s0L5HKkg051900@maildrop2.v6ds.occnc.com>
To: curtis@ipv6.occnc.com, Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1510)
Cc: draft-ietf-mpls-multipath-use.all@tools.ietf.org, "gen-art@ietf.org Gen-ART" <gen-art@ietf.org>, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-multipath-use-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 15:50:55 -0000

Many thanks for your (once again) detailed review, Peter! And thank you =
Curtis for making the fixes. One comment below:

>> Make all references to the expansion of ECMP read "Equal-Cost =
Multipath" for
>> consistency with RFC 2991.
>=20
> ECMP is expanded on first use in compliance with RFC Editor quidelines
> for abbreviations.  ECMP is also expanded on first use within each
> section where it is used with the exception of one place where ECMP is
> contained in a verbatim excerpt in a quote from RFC6374.

I thought Peter was referring to the fact that your draft has some =
variation on the way the term is expanded, even outside verbatim =
examples:

> % grep -i 'equal' draft-ietf-mpls-multipath-use-03.txt
> draft-ietf-mpls-multipath-use-03.txt:94:   than parallel links =
includes Equal Cost MultiPath (ECMP) as applied
> draft-ietf-mpls-multipath-use-03.txt:148:   Equal Cost Multipath =
(ECMP)
> draft-ietf-mpls-multipath-use-03.txt:149:       Equal Cost Multipath =
(ECMP) is a specific form of multipath in
> draft-ietf-mpls-multipath-use-03.txt:229:       Equal-Cost Multi-Path =
(ECMP) load-balancing MUST NOT be performed
> draft-ietf-mpls-multipath-use-03.txt:288:   following paragraph in =
"Section 2.9.4 Equal Cost Multipath" gives the
> =85
> % grep -i "equal" rfc2991.txt
> rfc2991.txt:   allow "Equal-Cost Multipath" (ECMP) routing.  Some =
router
> =85

I think you could align other instances than those relating to verbatim =
text from RFC 5960 or 6374.

Anyway, minor things. I have balloted no-objection for this draft for =
the Thursday's IESG telechat. Thanks for your hard work, all.

Jari


From vkg@bell-labs.com  Tue Jan 21 08:41:36 2014
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEFE1A01AD; Tue, 21 Jan 2014 08:41:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bmG5zkclqcz5; Tue, 21 Jan 2014 08:40:39 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 640011A01A6; Tue, 21 Jan 2014 08:40:36 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id s0LGeYss025690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 21 Jan 2014 10:40:35 -0600 (CST)
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 s0LGVhvB024513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Jan 2014 10:31:43 -0600
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 s0LGVh1d020008; Tue, 21 Jan 2014 10:31:43 -0600 (CST)
Message-ID: <52DEA11F.3040703@bell-labs.com>
Date: Tue, 21 Jan 2014 10:32:31 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: draft-ietf-l2vpn-evpn-req@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: l2vpn-chairs@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, IESG IESG <iesg@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-l2vpn-evpn-req-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 16:41: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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-l2vpn-evpn-req-06
Reviewer: Vijay K. Gurbani
Review Date: Jan-21-2014
IETF LC End Date: Unknown
IESG Telechat date: Jan-23-2014

Major: 0
Minor: 0
Nits: 2

This document is ready for publication as an Informational.

The document is ready, most of the nits in the nit-list I had have
been addressed by the IESG during balloting.  That said, the remaining
nits on my list are:

- The requirements in the Security Considerations section (R13 and R14)
  are better put in Section 6 (Ease of Provisioning Requirements), no?
  Is there something intrinsic to do with security on R13 and R14 that
  they are put in the Security Considerations section?  If there is, it
  is not apparent to me.

- Grammar/language: Section 7, Requirement 9:
  s/This gives rise to two/This results in two/
  (Reason: "gives rise to" is probably best left to works of
  fiction :-) )

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 vkg@bell-labs.com  Tue Jan 21 08:41:42 2014
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A07AB1A0373 for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 08:41:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zKV9Xvu8I5B2 for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 08:41:40 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9C7441A019D for <gen-art@ietf.org>; Tue, 21 Jan 2014 08:40:54 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s0LGelPQ009681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 21 Jan 2014 10:40:47 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s0LGejsq017345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Jan 2014 10:40:46 -0600
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 s0LGejxX028048; Tue, 21 Jan 2014 10:40:45 -0600 (CST)
Message-ID: <52DEA33E.7040903@bell-labs.com>
Date: Tue, 21 Jan 2014 10:41:34 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: draft-shore-icmp-aup@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: Benoit Claise <bclaise@cisco.com>, Ron Bonica <rbonica@juniper.net>, General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-shore-icmp-aup-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 16:41:42 -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-shore-icmp-aup-09
Reviewer: Vijay K. Gurbani
Review Date: Jan-21-2014
IETF LC End Date: Unknown
IESG Telechat date: Jan-23-2014

Major: 0
Minor: 0
Nits: 0

This document is ready as a BCP.

I had reviewed -06 for Gen-ART and all of my comments in -06 have been
addressed.  I have no further comments.

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 jari.arkko@piuha.net  Tue Jan 21 13:28:40 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8E31A037B; Tue, 21 Jan 2014 13:28:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aEHZrGEDxiyL; Tue, 21 Jan 2014 13:28:37 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 43D441A0250; Tue, 21 Jan 2014 13:28:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2F91D2CEB6; Tue, 21 Jan 2014 23:28:35 +0200 (EET)
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 T2nXAAYyvW8U; Tue, 21 Jan 2014 23:28:32 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D7D9F2CC48; Tue, 21 Jan 2014 23:28:31 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <46B4DC5A-723A-49E2-992F-FA1906F228FB@nostrum.com>
Date: Tue, 21 Jan 2014 23:28:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2AC7B5C-5A2B-4CA1-9DF0-016EA7AFA727@piuha.net>
References: <46B4DC5A-723A-49E2-992F-FA1906F228FB@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1510)
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, 6man@ietf.org, "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-16
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 21:28:40 -0000

Ben: thanks for your review & re-review.

Jari

On Dec 24, 2013, at 4:31 AM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=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-6man-stable-privacy-addresses-16
> Reviewer: Ben Campbell
> Review Date: 2013-12-23
> IETF LC End Date: 2013-12-25
>=20
> Summary: Ready for publication as a standards track RFC.=20
>=20
> Note: I performed a Gen-ART review on version 06 of this draft at a =
previous IETF LC. While the draft has evolved quite a bit since then, =
this review is mostly incremental to that one. All of my comments from =
that review have been addressed.
>=20
> Major issues:
>=20
> None
>=20
>=20
> Minor issues:
>=20
> None
>=20
> Nits/editorial comments:
>=20
> None
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From hartmans@mit.edu  Tue Jan 21 13:38:44 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 954981A0393; Tue, 21 Jan 2014 13:38:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IvEI1sLEYw4J; Tue, 21 Jan 2014 13:38:43 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id D79A81A0381; Tue, 21 Jan 2014 13:38:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 8DD492064F; Tue, 21 Jan 2014 16:35:55 -0500 (EST)
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 bCpIgOxvohNk; Tue, 21 Jan 2014 16:35:55 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 21 Jan 2014 16:35:55 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 8561E8351F; Tue, 21 Jan 2014 16:38:41 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie>
Date: Tue, 21 Jan 2014 16:38:41 -0500
In-Reply-To: <52DC1F71.80102@cs.tcd.ie> (Stephen Farrell's message of "Sun, 19 Jan 2014 18:54:41 +0000")
Message-ID: <tsl8uu9dnha.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 discussion list <ietf@ietf.org>, Eliot Lear <lear@cisco.com>, draft-farrell-perpass-attack.all@tools.ietf.org, gen-art <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-Art telechat review of draft-farrell-perpass-attack-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 21:38:44 -0000

I think that consideration of perpass at the architectural  level, being
prepared to justify decisions, and seeking adequate review of those
decision early enough to make changes if we're wrong are critical to
this document.
strongly object to publication of this document without that.

I value integrity and honesty very highly and am feel sick when I think
about claiming to the world that we're going to address perpass
mitigations without being willing to commit to ourselves  to do the
architectural work.
You cannot simply  take a protocol and mitigate these sorts of issues.
Many of our existing technologies leak a lot of information to
attackers.
One of the most important decisions when we start work on new protocols
in terms of perpass mitigation will be what building blocks we use.

If we're not willing to commit to having those discussions up front,
reviewing them and when questions arise during that review , I don't
think we're being truthful or acting with integrity if we claim that
we're mittigating perpass threats.

I'd much rather us be honest that we're not willing to do what it takes
to deal with perpass threats than to claim to try and mitigate them with
a solution that I think will be unsuccessful.

I do understand being concerned and worried that an AD would block
something late in the process because of bad architecture.
If the architecture was appropriately reviewed, I think that's the right
wrong approach.  I'd support language making that more clear.
If the architecture was inadequately reviewed, I strongly feel  that
should be handled like any process problem.  Some process problems are
blocking; some cases of inadequate review of an architecture also should
be blocking.
Yes, some of that is subjective and needs to be argued by the IESG and
community if there is conflict.

From jari.arkko@piuha.net  Tue Jan 21 13:58:16 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 340661A01CA for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 13:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sggu1FKlDBFM for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 13:58:15 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D37041A0182 for <gen-art@ietf.org>; Tue, 21 Jan 2014 13:58:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5189F2CEB6; Tue, 21 Jan 2014 23:58:14 +0200 (EET)
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 7z3gIWsNk0d2; Tue, 21 Jan 2014 23:58:13 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id CECB22CC48; Tue, 21 Jan 2014 23:58:13 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <020b01ce44bd$c0ba0fd0$422e2f70$@gmail.com>
Date: Tue, 21 Jan 2014 23:58:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CAC94984-561F-4504-A609-6B6F85041C9A@piuha.net>
References: <019901ce43ea$bbd575a0$338060e0$@gmail.com>	<20130428.115010.513224826.mbj@tail-f.com>	<01ba01ce440c$408d4720$c1a7d560$@gmail.com> <20130429.102542.1993240684524912340.mbj@tail-f.com> <020b01ce44bd$c0ba0fd0$422e2f70$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org, gen-art@ietf.org, Martin Bjorklund <mbj@tail-f.com>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 21:58:16 -0000

This is an old thread - but the document is now up for IESG review this =
Thursday. Thanks for your review & corrections. I have balloted no-obj.

Jari


From jari.arkko@piuha.net  Tue Jan 21 14:01:46 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE4E11A01F3 for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 14:01:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ld5-PQZ-T_1o for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 14:01:44 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C51231A0182 for <gen-art@ietf.org>; Tue, 21 Jan 2014 14:01:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 441942CEB6; Wed, 22 Jan 2014 00:01:43 +0200 (EET)
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 TQMAAENoRpdG; Wed, 22 Jan 2014 00:01:42 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 70AE42CC48; Wed, 22 Jan 2014 00:01:42 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52DD66D7.7020107@isode.com>
Date: Wed, 22 Jan 2014 00:01:42 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <90658F23-325C-44A0-93A3-429E5FFF5C7B@piuha.net>
References: <52DD04AE.8070604@isode.com> <CAF4+nEFuPdVmyqa5x0QwFOysLB14eGzPM8gLRy6wb4yMXuzLJw@mail.gmail.com> <52DD66D7.7020107@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1510)
Cc: Donald Eastlake <d3e3e3@gmail.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-isis-rfc6326bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-isis-rfc6326bis-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 22:01:46 -0000

Thanks for your review, Alexey! And thank you Donald for considering the =
comments. I have placed a no-obj position on the ballot for this =
Thursday's IESG telechat. But I do think Alexey raised valid points and =
I expect the draft to be revised. Will you take care of that, Donald?

Jari

On Jan 20, 2014, at 8:11 PM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:

> Hi Donald,
>=20
> On 20/01/2014 16:45, Donald Eastlake wrote:
>> Hi Alexey,
>>=20
>> Thanks for your review, see below:
>>=20
>> On Mon, Jan 20, 2014 at 6:12 AM, 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-isis-rfc6326bis-01
>>> Reviewer: Alexey Melnikov
>>> Review Date: 2014-01-20
>>> IETF LC End Date: 2014-01-22
>>> IESG Telechat date: 2014-01-23
>>>=20
>>>=20
>>> Summary: This draft is nearly ready for publication as a standard =
track RFC.
>>>=20
>>> Major issues: None
>>>=20
>>> Minor issues:
>>>=20
>>> o  Label: This carries the fine-grained label identifier for all
>>>       subsequent MAC addresses in this sub-TLV, or the value zero if =
no
>>>       label is specified.
>>>=20
>>> I fully admit ignorance of the topic, but what is exactly
>>> "fine-grained label" and where is the exact format defined? If it is
>>> defined later in the document, can you please add a forward
>>> reference. If it is defined in another document, can you please add
>>> a reference to that.
>> Fine grained labels are specified in =
draft-ietf-trill-fine-labeling-07,
>> which is an approved standard track draft in the RFC Editor's
>> queue. Adding a reference to it here would be good.
> Sounds great. Thanks.
>>> In Sections 2.2.4 and 2.3.1:
>>>=20
>>> What are the requirements on backward compatibility between =
different
>>> versions of TRILL. Are TLVs formats supported for a version N also =
valid for
>>> version N+M? If you have any implied assumptions, please state them =
in the
>>> document.
>> There are no explicit requirements. Incremental changes and
>> improvements are generally handed with capability bits or the
>> presence/absence of data strucutres in control messages. A version
>> change would probably indicate a pretty major modification but, since
>> these version numbers are within IS-IS TLVs, I would say that
>> implicitly the intent is to stay with the IS-IS PDU structure for the
>> control plane.
> I think the document should state that. Also, if you want any messages =
to be unchanged (fully or partially) irrespectively of version numbers, =
you should state that too.
>=20
> Best Regards,
> Alexey
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Jan 21 14:05:52 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0528F1A01D4; Tue, 21 Jan 2014 14:05:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HH9n-luZk5HK; Tue, 21 Jan 2014 14:05:49 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 965441A01D3; Tue, 21 Jan 2014 14:05:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 13BD52CEB6; Wed, 22 Jan 2014 00:05:48 +0200 (EET)
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 qDpp4qMnenkY; Wed, 22 Jan 2014 00:05:44 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 1FA2D2CC48; Wed, 22 Jan 2014 00:05:44 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026F04760D@MX15A.corp.emc.com>
Date: Wed, 22 Jan 2014 00:05:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <41354F78-C61F-424E-B612-7023A277D63E@piuha.net>
References: <8D3D17ACE214DC429325B2B98F3AE712026F04760D@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1510)
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, attila.takacs@ericsson.com, don.fedyk@gmail.com, hejia@huawei.com, "adrian@olddog.co.uk Farrel" <adrian@olddog.co.uk>, ccamp@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 22:05:52 -0000

Thanks for your review & re-review, David! I have balloted no-obj, for =
this Thursday's IESG telechat.

Jari

On Jan 17, 2014, at 1:30 AM, "Black, David" <david.black@emc.com> wrote:

> The -12 version of this draft addresses the nits and editorial items
> noted in the Gen-ART review of the -11 version.  It's ready for
> RFC publication.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Black, =
David
>> Sent: Sunday, December 29, 2013 9:51 PM
>> To: General Area Review Team (gen-art@ietf.org); =
attila.takacs@ericsson.com;
>> donald.fedyk@alcatel-lucent.com; hejia@huawei.com
>> Cc: adrian@olddog.co.uk; ccamp@ietf.org; ietf@ietf.org
>> Subject: Re: [Gen-art] Gen-ART review of =
draft-ietf-ccamp-oam-configuration-
>> fwk-11
>>=20
>> One additional nit - Don Fedyk's email address listed in the draft =
does not
>> work.
>>=20
>> Thanks,
>> --David
>>=20
>>> -----Original Message-----
>>> From: Black, David
>>> Sent: Sunday, December 29, 2013 9:46 PM
>>> To: General Area Review Team (gen-art@ietf.org); =
attila.takacs@ericsson.com;
>>> donald.fedyk@alcatel-lucent.com; hejia@huawei.com
>>> Cc: Black, David; adrian@olddog.co.uk; ccamp@ietf.org; ietf@ietf.org
>>> Subject: Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-11
>>>=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-ccamp-oam-configuration-fwk-11
>>> Reviewer: David L. Black
>>> Review Date: December 29, 2013
>>> IETF LC End Date: January 5, 2014
>>>=20
>>> Summary: This draft is basically ready for publication, but has nits =
that
>>> should be fixed before publication.
>>>=20
>>> This draft describes the GMPLS framework for signaling OAM =
configuration,
>>> and specifies additional RSVP elements to support that signaling.  =
Knowledge
>>> of RSVP, and specifically RSVP-TE is assumed; beyond that, the draft =
is
>>> complete, although it is very detailed - see editorial comment below =
on
>>> Section 3.
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> Sections 3.1-3.3 dive into the details very quickly.  They would be =
easier
>> to
>>> understand if there was an overview paragraph near the start of =
Section 3
>> that
>>> describes the roles of the two ADMIN_STATUS flags and the two LSP =
Attributes
>>> flags in OAM configuration (establishment, change/adjustment, =
deletion)
>> before
>>> the current text that contains the details of RSVP message =
processing.
>>>=20
>>> There are a number of instances of "(IANA to assign)" in section 4 =
that the
>>> RFC Editor will need to remove - an RFC Editor note to that effect =
should
>>> be inserted at the start of Section 4.
>>>=20
>>> Section 4.5 is necessarily incomplete on P2MP considerations, =
because (as
>>> it says) "P2MP OAM mechanisms are very specific to the data plane
>> technology".
>>> It would be helpful if section 4.5 contained language indicating =
what a
>>> specific data plane specification should include to completely =
specify
>>> P2MP OAM configuration for that data plane.
>>>=20
>>> idnits 2.13.01 didn't find anything that needs 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
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From curtis@ipv6.occnc.com  Tue Jan 21 14:06:58 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC721A0225; Tue, 21 Jan 2014 14:06:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7DDumnr8LSh; Tue, 21 Jan 2014 14:06:54 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 05C211A01D3; Tue, 21 Jan 2014 14:06:51 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0LM6l4b067118; Tue, 21 Jan 2014 17:06:47 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401212206.s0LM6l4b067118@maildrop2.v6ds.occnc.com>
To: Jari Arkko <jari.arkko@piuha.net>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Tue, 21 Jan 2014 17:50:52 +0200." <E736F946-88D0-4262-B2DD-C62FC461A885@piuha.net>
Date: Tue, 21 Jan 2014 17:06:47 -0500
Cc: draft-ietf-mpls-multipath-use.all@tools.ietf.org, "gen-art@ietf.org Gen-ART" <gen-art@ietf.org>, ietf@ietf.org, curtis@ipv6.occnc.com
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-multipath-use-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 22:06:59 -0000

In message <E736F946-88D0-4262-B2DD-C62FC461A885@piuha.net>
Jari Arkko writes:
>  
> Many thanks for your (once again) detailed review, Peter! And thank
> you Curtis for making the fixes. One comment below:
>  
> >> Make all references to the expansion of ECMP read "Equal-Cost Multipath" for
> >> consistency with RFC 2991.
> > 
> > ECMP is expanded on first use in compliance with RFC Editor quidelines
> > for abbreviations.  ECMP is also expanded on first use within each
> > section where it is used with the exception of one place where ECMP is
> > contained in a verbatim excerpt in a quote from RFC6374.
>  
> I thought Peter was referring to the fact that your draft has some variation on the way the term is expanded, even outside verbatim examples:
>  
> > % grep -i 'equal' draft-ietf-mpls-multipath-use-03.txt
> > draft-ietf-mpls-multipath-use-03.txt:94:   than parallel links includes Equal Cost MultiPath (ECMP) as applied
> > draft-ietf-mpls-multipath-use-03.txt:148:   Equal Cost Multipath (ECMP)
> > draft-ietf-mpls-multipath-use-03.txt:149:       Equal Cost Multipath (ECMP) is a specific form of multipath in
> > draft-ietf-mpls-multipath-use-03.txt:229:       Equal-Cost Multi-Path (ECMP) load-balancing MUST NOT be performed
> > draft-ietf-mpls-multipath-use-03.txt:288:   following paragraph in "Section 2.9.4 Equal Cost Multipath" gives the
> > 
> > % grep -i "equal" rfc2991.txt
> > rfc2991.txt:   allow "Equal-Cost Multipath" (ECMP) routing.  Some router
> > 
>  
> I think you could align other instances than those relating to
> verbatim text from RFC 5960 or 6374.
>  
> Anyway, minor things. I have balloted no-objection for this draft for
> the Thursday's IESG telechat. Thanks for your hard work, all.
>  
> Jari


Jari,

Thanks for the no-objection.

There doesn't seem to be much consistency on ECMP expansion.

Checking abstracts in rfc-index:

RFC2992 (same authors as RFC2991) uses:

  Equal-Cost Multi-Path        - in the title
  Equal-cost multi-path (ECMP) - in the abstract

RFC4928 uses:

  Equal Cost Multipath (ECMP)

RFC5640 uses:

  equal cost multiple paths (ECMPs)

RFC6391 uses:

  Equal Cost Multiple Paths (ECMPs)

RFC6754 in the title uses:

  Equal-Cost Multipath (ECMP)

You'll get a few more combinations of hyphenation and capitalization
if you try:

  grep -i 'equal[- ]cost' rfc????.txt | grep ECMP

The total count for space vs hyphen (up to rfc7052) are:

  grep -i 'equal cost multi' rfc????.txt | grep ECMP | wc -l
      47
  grep -i 'equal-cost multi' rfc????.txt | grep ECMP | wc -l
      26

  grep -i 'equal cost multi' rfc????.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
      34
  grep -i 'equal-cost multi' rfc????.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
      18

The hyphen form is used less often recently (May 2008 - Oct 2013).

  grep -i 'equal cost multi' rfc[567]???.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
      27
  grep -i 'equal-cost multi' rfc[567]???.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
      10

  grep -i 'equal cost multi' rfc[67]???.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
      15
  grep -i 'equal-cost multi' rfc[67]???.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
       8

I prefer the RFC4928 flavor of this acronym and the above greps show
that it is more widely used in the RFC series.

Curtis

From jari.arkko@piuha.net  Tue Jan 21 14:09:00 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0023A1A01FF for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 14:09:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Q_WvunnGdyd for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 14:08:58 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA1A1A01D3 for <gen-art@ietf.org>; Tue, 21 Jan 2014 14:08:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DE62A2CEC1; Wed, 22 Jan 2014 00:08:56 +0200 (EET)
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 YrvlJJZmvs7C; Wed, 22 Jan 2014 00:08:55 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7ACB22CC48; Wed, 22 Jan 2014 00:08:55 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A32D06251@eusaamb107.ericsson.se>
Date: Wed, 22 Jan 2014 00:08:55 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A6D1802-347A-480F-9751-8F18D630E8AA@piuha.net>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32D06251@eusaamb107.ericsson.se>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
X-Mailer: Apple Mail (2.1510)
Cc: "draft-ietf-pwe3-mpls-tp-cv-adv.all@tools.ietf.org" <draft-ietf-pwe3-mpls-tp-cv-adv.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Call review of draft-ietf-pwe3-mpls-tp-cv-adv-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 22:09:00 -0000

Thanks for you review, Meral!

Jari

On Jan 20, 2014, at 9:20 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 wait for direction from your document shepherd or AD before =
posting a new version of the draft.
> =20
> Document: draft-ietf-pwe3-mpls-tp-cv-adv-04
> Reviewer: Meral Shirazipour
> Review Date: 2014-01-19
> IETF LC End Date: 2014-01-16
> IESG Telechat date: 2014-01-23
> =20
> Summary: This draft is ready for publication as a Standards Track RFC.
> =20
> =20
> =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 jari.arkko@piuha.net  Tue Jan 21 14:11:28 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 195B51A01B9; Tue, 21 Jan 2014 14:11:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ayaUbIKZwi4h; Tue, 21 Jan 2014 14:11:26 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 503401A01BB; Tue, 21 Jan 2014 14:11:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C5C052CEB6; Wed, 22 Jan 2014 00:11:24 +0200 (EET)
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 KVubkAdSVrQT; Wed, 22 Jan 2014 00:11:22 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B84162CC48; Wed, 22 Jan 2014 00:11:22 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52D82BAA.1010007@nostrum.com>
Date: Wed, 22 Jan 2014 00:11:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9F8D043A-DDA7-4B0C-BFCB-71935EA99DD6@piuha.net>
References: <52D82BAA.1010007@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1510)
Cc: mpls@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-ietf-mpls-moving-iana-registries@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art LC review of draft-ietf-mpls-moving-iana-registries
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 22:11:28 -0000

Thanks for your review, Robert. These reviews are important for helping =
me to determine whether a document needs further review or if there are =
issues that I'd need to pay special attention to. I have balloted no-obj =
for this document on the upcoming IESG telechat.

Jari

On Jan 16, 2014, at 8:57 PM, Robert Sparks <rjsparks@nostrum.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-mpls-moving-iana-registries
> Reviewer: Robert Sparks
> Review Date: 16-Jan-2014
> IETF LC End Date: 17-Jan-2014
> IESG Telechat date: 23-Jan-2014
>=20
> Summary: This document is ready for publication as Proposed Standard
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Jan 21 14:12:29 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54A131A01C8 for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 14:12:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5PmsoijYEZP for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 14:12:26 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 534BB1A01BB for <gen-art@ietf.org>; Tue, 21 Jan 2014 14:12:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C91312CEB6; Wed, 22 Jan 2014 00:12:25 +0200 (EET)
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 fU9PdaCnzjDS; Wed, 22 Jan 2014 00:12:23 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id DB23A2CC48; Wed, 22 Jan 2014 00:12:23 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52DEA33E.7040903@bell-labs.com>
Date: Wed, 22 Jan 2014 00:12:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD379A77-8DE0-441D-8824-2AAABA1B5FD8@piuha.net>
References: <52DEA33E.7040903@bell-labs.com>
To: Vijay K. Gurbani <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1510)
Cc: Benoit Claise <bclaise@cisco.com>, Ron Bonica <rbonica@juniper.net>, General Area Review Team <gen-art@ietf.org>, draft-shore-icmp-aup@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-shore-icmp-aup-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 22:12:29 -0000

Thank you for the review and re-review, and for the changes that =
occurred in between. I have balloted no-obj=85

Jari

On Jan 21, 2014, at 6:41 PM, Vijay K. Gurbani <vkg@bell-labs.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-shore-icmp-aup-09
> Reviewer: Vijay K. Gurbani
> Review Date: Jan-21-2014
> IETF LC End Date: Unknown
> IESG Telechat date: Jan-23-2014
>=20
> Major: 0
> Minor: 0
> Nits: 0
>=20
> This document is ready as a BCP.
>=20
> I had reviewed -06 for Gen-ART and all of my comments in -06 have been
> addressed.  I have no further comments.
>=20
> Thanks,
>=20
> - vijay
> --=20
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web: http://ect.bell-labs.com/who/vkg/  | Calendar: =
http://goo.gl/x3Ogq
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Tue Jan 21 14:19:37 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFD311A01BB; Tue, 21 Jan 2014 14:19:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dcXLGD3iorLb; Tue, 21 Jan 2014 14:19:35 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A82171A0127; Tue, 21 Jan 2014 14:19:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 263832CEB6; Wed, 22 Jan 2014 00:19:34 +0200 (EET)
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 TXus-HaQksxM; Wed, 22 Jan 2014 00:19:33 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 631242CC48; Wed, 22 Jan 2014 00:19:33 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52DEA11F.3040703@bell-labs.com>
Date: Wed, 22 Jan 2014 00:19:33 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <73A43A96-248E-47FD-8589-D79BC316B9C2@piuha.net>
References: <52DEA11F.3040703@bell-labs.com>
To: Vijay K. Gurbani <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1510)
Cc: draft-ietf-l2vpn-evpn-req@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, IESG IESG <iesg@ietf.org>, l2vpn-chairs@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-l2vpn-evpn-req-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 22:19:37 -0000

Thanks for your review and re-review, Vijay. And thanks for the authors =
for the changes that occurred between the two reviews.

I do agree with Vijay's point about R13 and R14.

Jari

On Jan 21, 2014, at 6:32 PM, Vijay K. Gurbani <vkg@bell-labs.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-l2vpn-evpn-req-06
> Reviewer: Vijay K. Gurbani
> Review Date: Jan-21-2014
> IETF LC End Date: Unknown
> IESG Telechat date: Jan-23-2014
>=20
> Major: 0
> Minor: 0
> Nits: 2
>=20
> This document is ready for publication as an Informational.
>=20
> The document is ready, most of the nits in the nit-list I had have
> been addressed by the IESG during balloting.  That said, the remaining
> nits on my list are:
>=20
> - The requirements in the Security Considerations section (R13 and =
R14)
> are better put in Section 6 (Ease of Provisioning Requirements), no?
> Is there something intrinsic to do with security on R13 and R14 that
> they are put in the Security Considerations section?  If there is, it
> is not apparent to me.
>=20
> - Grammar/language: Section 7, Requirement 9:
> s/This gives rise to two/This results in two/
> (Reason: "gives rise to" is probably best left to works of
> fiction :-) )
>=20
> Thanks,
>=20
> - vijay
> --=20
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web: http://ect.bell-labs.com/who/vkg/  | Calendar: =
http://goo.gl/x3Ogq


From scott.brim@gmail.com  Tue Jan 21 14:26:32 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8171A0232; Tue, 21 Jan 2014 14:26:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id plQnuMDA9cO2; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 9ADA51A01F6; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id j17so4045199oag.28 for <multiple recipients>; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
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=zfsiA/cLT0pbUGnMFWF+nruSdueijanTYy6qxbiYRB0=; b=ZIHwbAxdSRmEa1rpGjLZcdPIbOvsHSo582GeevTrEqw9+/loONcMovijfmA4oLMDXm 4qYy7tf21ik2G78wXqSGbxFa0jPELH1TJubti/iyCPS/01r5/U0wMBMMZbuHbQ1NeBv/ 1JiPCNRt710iRl5XuJWbnjrsu2y2bkBsewWPIXre6oC3vivReU8GfwdNDJnAw/P6Chhf nZGAfa7/QhfmaY3hbk1HCA83nBOf3CJz46gQX5lBeD3mRl7ZEFCmJBwChNEJZl29LV0Q AT0biXG0O8p3k2azq07PhPzDzW4JkMFwis9f2x7UyqVCBvhhSSzL+R7cqvAuXQPUSsdb QLZQ==
MIME-Version: 1.0
X-Received: by 10.60.63.102 with SMTP id f6mr3020461oes.76.1390343190212; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
In-Reply-To: <tsl8uu9dnha.fsf@mit.edu>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu>
Date: Tue, 21 Jan 2014 17:26:30 -0500
Message-ID: <CAPv4CP-d2BNzG6Ww+sCFWcXGZgYi59bqqenksgaDqSggqRhmyg@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Content-Type: multipart/alternative; boundary=001a11c25532f7f7e904f0827f51
Cc: IETF discussion list <ietf@ietf.org>, Eliot Lear <lear@cisco.com>, draft-farrell-perpass-attack.all@tools.ietf.org, gen-art <gen-art@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Gen-art] Gen-Art telechat review of draft-farrell-perpass-attack-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 22:26:32 -0000

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

Sam: I believe that all you ask is still there.  We will consider PM at
architecture time, and anyone can contribute. We'll take it seriously.
What's missing is the requirement to demonstrate that you have covered all
the issues, to an unknown level.  Essentially this is how we work already.

Scott

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

<p dir=3D"ltr">Sam: I believe that all you ask is still there.=A0 We will c=
onsider PM at architecture time, and anyone can contribute. We&#39;ll take =
it seriously.=A0 What&#39;s missing is the requirement to demonstrate that =
you have covered all the issues, to an unknown level.=A0 Essentially this i=
s how we work already. </p>

<p dir=3D"ltr">Scott </p>

--001a11c25532f7f7e904f0827f51--

From dhc@dcrocker.net  Tue Jan 21 14:56:09 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A911D1A0263; Tue, 21 Jan 2014 14:56:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EJimi9DLK9Dy; Tue, 21 Jan 2014 14:56:08 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB231A01D7; Tue, 21 Jan 2014 14:56:08 -0800 (PST)
Received: from [192.168.1.6] (cpe-76-93-140-82.san.res.rr.com [76.93.140.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s0LMtvt3006178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Jan 2014 14:56:00 -0800
Message-ID: <52DEFAEE.3000900@dcrocker.net>
Date: Tue, 21 Jan 2014 14:55:42 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu>
In-Reply-To: <tsl8uu9dnha.fsf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 21 Jan 2014 14:56:01 -0800 (PST)
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art telechat review of draft-farrell-perpass-attack-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 22:56:09 -0000

On 1/21/2014 1:38 PM, Sam Hartman wrote:
> I think that consideration of perpass at the architectural  level, being
> prepared to justify decisions, and seeking adequate review of those
> decision
...
> I value integrity and honesty very highly and am feel sick when I think
> about claiming to the world that we're going to address perpass
> mitigations without being willing to commit to ourselves  to do the
> architectural work.


Sam,

Consider the level of activity on this topic that is already happening 
in the IETF, as well as the nature of this initial document.  I'll 
suggest that that's the most important demonstration of organizational 
commitment.

The document in question marks that commitment, but it needs to be 
careful not to mark it beyond our current capabilities.

In particular please point me/us to established consensus documents that 
define the problem space, the solution space and the architectural 
choices appropriate to this topic.  I'm not aware of any, but perhaps I 
missed them.

Absent established documents on this topic, "justifying" is only 
reasonable in terms of demonstrating thoughtfulness, not demonstrating 
that the choices are "correct".  Yet a term like "justify" encourages 
this latter expectations.   the view that we have far more community 
clue about this topic than we currently have.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jari.arkko@piuha.net  Tue Jan 21 15:06:24 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FB541A0232 for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 15:06:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gOXPwI7kR-cc for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 15:06:22 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9325D1A01CD for <gen-art@ietf.org>; Tue, 21 Jan 2014 15:06:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0F3672CEB6; Wed, 22 Jan 2014 01:06:21 +0200 (EET)
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 QRaCPxXlduYD; Wed, 22 Jan 2014 01:06:20 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 82AB32CC48; Wed, 22 Jan 2014 01:06:20 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com>
Date: Wed, 22 Jan 2014 01:06:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C5B486D-ED82-4ABC-9CAE-B720729791D2@piuha.net>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com> <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com> <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org, Victor Kuarsingh <victor@jvknet.com>
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 23:06:24 -0000

Thanks for your detailed review, Martin!

And thank you Victor for a very useful document!

Much of the discussion in this thread is important but also partly =
editorial. I'll leave it to sort out between yourselves.

However, I do think Section 6 last sentence:

   Should a provide choose to use non-assigned IP address space within =
their translation realms, then considerations may apply.

gives an odd impression. We already have shared address space (as the =
document notes elsewhere), so it is not clear to me what the above might =
entail, particularly when (a) regular address space assignments go =
through the RIR system not IANA (b) use of unassigned address space is =
probably not something that we want to recommend and (c) if we need to =
do something beyond the existing shared address space allocation, then =
that probably deserves its own document.

I can see that Victor you've already agreed to make a change wrt Section =
6. I just wanted to check that this is indeed the plan, so that we can =
move on to approving the document :-)

Jari


From d3e3e3@gmail.com  Tue Jan 21 15:21:29 2014
Return-Path: <d3e3e3@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 144BB1A01BB for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 15:21:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MvO_yHbzCCdX for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 15:21:27 -0800 (PST)
Received: from mail-oa0-x230.google.com (mail-oa0-x230.google.com [IPv6:2607:f8b0:4003:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 6088A1A017A for <gen-art@ietf.org>; Tue, 21 Jan 2014 15:21:25 -0800 (PST)
Received: by mail-oa0-f48.google.com with SMTP id l6so5218834oag.35 for <gen-art@ietf.org>; Tue, 21 Jan 2014 15:21:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=C8lQiRp2UolSBl1DuLyLPh4wd70+Me2gKmU1CC0+qss=; b=Q8/GPBaHw7OzahZSygXfnbvzt7Z3VDXjPim3kLl0AaXgW/nDxiS29Aql0cLD5CQmN1 YO9b54xrrujPBmSxD6hFZyoTSTHIvHAGyq6TU3bj/RxgAWKFpocETBGrah1bldarTd/U TLhyYmswyphO81w7Esqeuw6K9mGbA6c+H+ze7Wwgoo3ZQJwjexNZvUb13Ja5qPsjih1O MoLYXvZ0Q2Ma8/Hzw9B9+8wojh53YxWqQJ8vviacxqn1f8m3NxWPs99ycpcfadJKb8ZR oETo55XOp2owSHRFK+UnHcyNYoPzZSa6pwlD4NpIiel/M3dAGyeIzwmFG9BW7D6FSemN 2DGQ==
X-Received: by 10.60.37.33 with SMTP id v1mr23429416oej.2.1390346485000; Tue, 21 Jan 2014 15:21:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.33.102 with HTTP; Tue, 21 Jan 2014 15:21:04 -0800 (PST)
In-Reply-To: <90658F23-325C-44A0-93A3-429E5FFF5C7B@piuha.net>
References: <52DD04AE.8070604@isode.com> <CAF4+nEFuPdVmyqa5x0QwFOysLB14eGzPM8gLRy6wb4yMXuzLJw@mail.gmail.com> <52DD66D7.7020107@isode.com> <90658F23-325C-44A0-93A3-429E5FFF5C7B@piuha.net>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 21 Jan 2014 18:21:04 -0500
Message-ID: <CAF4+nEHnM_LTroNHuZXXzVEH+Och19F+5AU19P6yGqpNOtxQnA@mail.gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-isis-rfc6326bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-isis-rfc6326bis-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 23:21:29 -0000

Hi Jari,

On Tue, Jan 21, 2014 at 5:01 PM, Jari Arkko <jari.arkko@piuha.net> wrote:
> Thanks for your review, Alexey! And thank you Donald for considering the =
comments. I have placed a no-obj position on the ballot for this Thursday's=
 IESG telechat. But I do think Alexey raised valid points and I expect the =
draft to be revised. Will you take care of that, Donald?

I have a version ready to post with some minor editorial fixes and the
like and would be happy to include the missing reference to
draft-ietf-trill-fine-labeling; however, I would prefer not to include
the somewhat hand-waving text I wrote about TRILL protocol version
number and I am not sure how long it would take to come up with a good
statement on that...

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Jari
>
> On Jan 20, 2014, at 8:11 PM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:
>
>> Hi Donald,
>>
>> On 20/01/2014 16:45, Donald Eastlake wrote:
>>> Hi Alexey,
>>>
>>> Thanks for your review, see below:
>>>
>>> On Mon, Jan 20, 2014 at 6:12 AM, 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>.
>>>>
>>>> Please resolve these comments along with any other Last Call
>>>> comments you may receive.
>>>>
>>>> Document: draft-ietf-isis-rfc6326bis-01
>>>> Reviewer: Alexey Melnikov
>>>> Review Date: 2014-01-20
>>>> IETF LC End Date: 2014-01-22
>>>> IESG Telechat date: 2014-01-23
>>>>
>>>>
>>>> Summary: This draft is nearly ready for publication as a standard trac=
k RFC.
>>>>
>>>> Major issues: None
>>>>
>>>> Minor issues:
>>>>
>>>> o  Label: This carries the fine-grained label identifier for all
>>>>       subsequent MAC addresses in this sub-TLV, or the value zero if n=
o
>>>>       label is specified.
>>>>
>>>> I fully admit ignorance of the topic, but what is exactly
>>>> "fine-grained label" and where is the exact format defined? If it is
>>>> defined later in the document, can you please add a forward
>>>> reference. If it is defined in another document, can you please add
>>>> a reference to that.
>>> Fine grained labels are specified in draft-ietf-trill-fine-labeling-07,
>>> which is an approved standard track draft in the RFC Editor's
>>> queue. Adding a reference to it here would be good.
>> Sounds great. Thanks.
>>>> In Sections 2.2.4 and 2.3.1:
>>>>
>>>> What are the requirements on backward compatibility between different
>>>> versions of TRILL. Are TLVs formats supported for a version N also val=
id for
>>>> version N+M? If you have any implied assumptions, please state them in=
 the
>>>> document.
>>> There are no explicit requirements. Incremental changes and
>>> improvements are generally handed with capability bits or the
>>> presence/absence of data strucutres in control messages. A version
>>> change would probably indicate a pretty major modification but, since
>>> these version numbers are within IS-IS TLVs, I would say that
>>> implicitly the intent is to stay with the IS-IS PDU structure for the
>>> control plane.
>> I think the document should state that. Also, if you want any messages t=
o be unchanged (fully or partially) irrespectively of version numbers, you =
should state that too.
>>
>> Best Regards,
>> Alexey
>>
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>

From jari.arkko@piuha.net  Tue Jan 21 19:12:37 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A0861A03A9 for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 19:12:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hlB-TzyI8LnL for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 19:12:34 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 74B171A0373 for <gen-art@ietf.org>; Tue, 21 Jan 2014 19:12:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 01D402CC5D; Wed, 22 Jan 2014 05:12:33 +0200 (EET)
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 lZaaEPw9Rzhn; Wed, 22 Jan 2014 05:12:32 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 10EB72CC48; Wed, 22 Jan 2014 05:12:32 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAF4+nEHnM_LTroNHuZXXzVEH+Och19F+5AU19P6yGqpNOtxQnA@mail.gmail.com>
Date: Wed, 22 Jan 2014 05:12:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE8DCF47-7467-4DAA-9697-0EA4081E5C13@piuha.net>
References: <52DD04AE.8070604@isode.com> <CAF4+nEFuPdVmyqa5x0QwFOysLB14eGzPM8gLRy6wb4yMXuzLJw@mail.gmail.com> <52DD66D7.7020107@isode.com> <90658F23-325C-44A0-93A3-429E5FFF5C7B@piuha.net> <CAF4+nEHnM_LTroNHuZXXzVEH+Och19F+5AU19P6yGqpNOtxQnA@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-isis-rfc6326bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-isis-rfc6326bis-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jan 2014 03:12:37 -0000

On Jan 22, 2014, at 1:21 AM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> Hi Jari,
>=20
> On Tue, Jan 21, 2014 at 5:01 PM, Jari Arkko <jari.arkko@piuha.net> =
wrote:
>> Thanks for your review, Alexey! And thank you Donald for considering =
the comments. I have placed a no-obj position on the ballot for this =
Thursday's IESG telechat. But I do think Alexey raised valid points and =
I expect the draft to be revised. Will you take care of that, Donald?
>=20
> I have a version ready to post with some minor editorial fixes and the
> like and would be happy to include the missing reference to
> draft-ietf-trill-fine-labeling;

Great!

> however, I would prefer not to include
> the somewhat hand-waving text I wrote about TRILL protocol version
> number and I am not sure how long it would take to come up with a good
> statement on that=85

Ok

Jari


From victor@jvknet.com  Tue Jan 21 20:24:43 2014
Return-Path: <victor@jvknet.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB25B1A018E for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 20:24:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ODsF0nW3mOtL for <gen-art@ietfa.amsl.com>; Tue, 21 Jan 2014 20:24:40 -0800 (PST)
Received: from mail-vc0-f170.google.com (mail-vc0-f170.google.com [209.85.220.170]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDBC1A017B for <gen-art@ietf.org>; Tue, 21 Jan 2014 20:24:40 -0800 (PST)
Received: by mail-vc0-f170.google.com with SMTP id hu8so4138765vcb.29 for <gen-art@ietf.org>; Tue, 21 Jan 2014 20:24:39 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=qqEZJ8KczFL/fSORhY9feaQn6gHhcGYvb5EnjaES8MY=; b=VyB7+6InTsDLaMIjigM8MWYnlE3uYc8xQJmMjnMBMBQK80ORDqJk+nU2DQWkhIjnPY +X7NtbAFgZRNOxMkb7WZGaq+1jePjHmIzeiR4WCLIVhYyTz2gorSWfmCp8K7OPRXKKF3 B/ascvCIK9qLw0xk2V7FhSyu4bHtN5IUjEYQ43X3MAAP0nWMFPBQzC6hI6jkJVv17t2E gPYe6/VCCTDyOAtv//0kqHToTv2f5kqoOxzTn4HyWJMrZeftJ8PHSQSVmCbwggK7iXo7 VOQIv4n76Vlt2q7heDmvNuHysTfd76BjD5KCZnD+vGn5T8wHsV/l5Bcu6Ji/SJsx7HZr 6kSg==
X-Gm-Message-State: ALoCoQm4l1PC9OVEe3zNgmtYjhXPwQW7/prdoE8UwOP0yjVicGPeNYFuOhv1XT2seTJ0R7KgALG+
MIME-Version: 1.0
X-Received: by 10.58.196.211 with SMTP id io19mr16493501vec.9.1390364679774; Tue, 21 Jan 2014 20:24:39 -0800 (PST)
Received: by 10.58.123.35 with HTTP; Tue, 21 Jan 2014 20:24:39 -0800 (PST)
In-Reply-To: <3C5B486D-ED82-4ABC-9CAE-B720729791D2@piuha.net>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com> <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com> <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com> <3C5B486D-ED82-4ABC-9CAE-B720729791D2@piuha.net>
Date: Tue, 21 Jan 2014 23:24:39 -0500
Message-ID: <CAJc3aaMPMbpyxPjwZ-OdTnewuhGpU298g+1DzB1Kn7DLNhd5kA@mail.gmail.com>
From: Victor Kuarsingh <victor@jvknet.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=047d7b6dca96d8ba6504f087808c
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jan 2014 04:24:43 -0000

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

Jari/Martin,

With respect to section 6, I agree we can remove the odd text and I will
follow Martin's suggestion.  The inclusion of that text was a bit
historical as the document was actual first drafted before RFC6598.

I would agree that (as this point) that text, as I have in the document,
servers little value - so it will be removed.  I will also respond to
Martins last email and confirm some of the editorial changes.

Jari,  Please let me know if I need if you need to see a new draft spun
before approvals or if confirmation of the changes is sufficient (I am ok
with either).  I was trying to capture all final adjustments for a -05
version before publishing.

regards,

Victor K


On Tue, Jan 21, 2014 at 6:06 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> Thanks for your detailed review, Martin!
>
> And thank you Victor for a very useful document!
>
> Much of the discussion in this thread is important but also partly
> editorial. I'll leave it to sort out between yourselves.
>
> However, I do think Section 6 last sentence:
>
>    Should a provide choose to use non-assigned IP address space within
> their translation realms, then considerations may apply.
>
> gives an odd impression. We already have shared address space (as the
> document notes elsewhere), so it is not clear to me what the above might
> entail, particularly when (a) regular address space assignments go through
> the RIR system not IANA (b) use of unassigned address space is probably not
> something that we want to recommend and (c) if we need to do something
> beyond the existing shared address space allocation, then that probably
> deserves its own document.
>
> I can see that Victor you've already agreed to make a change wrt Section
> 6. I just wanted to check that this is indeed the plan, so that we can move
> on to approving the document :-)
>
> Jari
>
>

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

<div dir=3D"ltr">Jari/Martin,<div><br></div><div>With respect to section 6,=
 I agree we can remove the odd text and I will follow Martin&#39;s suggesti=
on. =A0The inclusion of that text was a bit historical as the document was =
actual first drafted before RFC6598.</div>
<div><br></div><div>I would agree that (as this point) that text, as I have=
 in the document, servers little value - so it will be removed. =A0I will a=
lso respond to Martins last email and confirm some of the editorial changes=
.</div>
<div><br></div><div>Jari, =A0Please let me know if I need if you need to se=
e a new draft spun before approvals or if confirmation of the changes is su=
fficient (I am ok with either). =A0I was trying to capture all final adjust=
ments for a -05 version before publishing.</div>
<div><br></div><div>regards,</div><div><br></div><div>Victor K</div></div><=
div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Jan 21=
, 2014 at 6:06 PM, Jari Arkko <span dir=3D"ltr">&lt;<a href=3D"mailto:jari.=
arkko@piuha.net" target=3D"_blank">jari.arkko@piuha.net</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Thanks for your detailed review, Martin!<br>
<br>
And thank you Victor for a very useful document!<br>
<br>
Much of the discussion in this thread is important but also partly editoria=
l. I&#39;ll leave it to sort out between yourselves.<br>
<br>
However, I do think Section 6 last sentence:<br>
<br>
=A0 =A0Should a provide choose to use non-assigned IP address space within =
their translation realms, then considerations may apply.<br>
<br>
gives an odd impression. We already have shared address space (as the docum=
ent notes elsewhere), so it is not clear to me what the above might entail,=
 particularly when (a) regular address space assignments go through the RIR=
 system not IANA (b) use of unassigned address space is probably not someth=
ing that we want to recommend and (c) if we need to do something beyond the=
 existing shared address space allocation, then that probably deserves its =
own document.<br>

<br>
I can see that Victor you&#39;ve already agreed to make a change wrt Sectio=
n 6. I just wanted to check that this is indeed the plan, so that we can mo=
ve on to approving the document :-)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br></div>

--047d7b6dca96d8ba6504f087808c--

From jari.arkko@piuha.net  Wed Jan 22 01:36:50 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 783D91A0416 for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 01:36:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aZwxa5g0DUEi for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 01:36:48 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 66A7B1A03FA for <gen-art@ietf.org>; Wed, 22 Jan 2014 01:36:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id F2C0C2CC5D; Wed, 22 Jan 2014 11:36:46 +0200 (EET)
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 4s0jSDagjim4; Wed, 22 Jan 2014 11:36:46 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 424372CC48; Wed, 22 Jan 2014 11:36:46 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
Date: Wed, 22 Jan 2014 11:36:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E608FDA6-8F47-45C1-BA7D-50DE3BDC73F3@piuha.net>
References: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1510)
Cc: draft-ietf-mpls-tp-p2mp-framework.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mpls-tp-p2mp-framework-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jan 2014 09:36:50 -0000

Thanks for your review, Russ!

(Btw I looked and I think this doc and 5921 can exist separately, =
without updates relationship.)

Jari


From bclaise@cisco.com  Wed Jan 22 04:00:28 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEA491A00B1 for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 04:00:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKQUYF8X0KfX for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 04:00:27 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 571FA1A00B9 for <gen-art@ietf.org>; Wed, 22 Jan 2014 04:00:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1323; q=dns/txt; s=iport; t=1390392027; x=1391601627; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=87ocdNLeNvg0+T6EluRJ6HTTBA89tqYMDFZAQ2o7Bsk=; b=AJRQdhgTeyTv1Fylvhw5jJbbEvQLCqRejnoqFe1d3NuvuFAjIU+WLbuz bqcma4VmZ+D/1F1lhwG5f5au7RiaWvKfBUxzI+1EMWHukms/kZ9euSQ+y QCVMQfbQiynxDWMgUtjpebSPoqdd+VN0hCcPQY4FmbwGiffPPRCEbHk0l 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFABmy31KQ/khL/2dsb2JhbABbgwuEDLhfgREWdIIlAQEBBCMVQAEQCxgCAgUWCwICCQMCAQIBRQYBDAEFAgEBiAGlQ5w1F4EpjVMHgm+BSQEDmCKGR4tRgy47
X-IronPort-AV: E=Sophos;i="4.95,699,1384300800";  d="scan'208";a="4007555"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 22 Jan 2014 12:00:26 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0MC0QfH022658; Wed, 22 Jan 2014 12:00:26 GMT
Message-ID: <52DFB2D9.7030300@cisco.com>
Date: Wed, 22 Jan 2014 13:00:25 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>, Victor Kuarsingh <victor@jvknet.com>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com>	<CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com> <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com>
In-Reply-To: <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jan 2014 12:00:29 -0000

Martin,
> On 15 January 2014 19:40, Victor Kuarsingh<victor@jvknet.com>  wrote:
>>> >>Which seems wise given their somewhat contentious nature.  But then
>>> >>the entirely of Section 2 does exactly the opposite.  I don't know
>>> >>what the right answer is here, but maybe the right thing to do is
>>> >>delete Section 2.
>> >
>> >
>> >[VK]  The intention of this section was to explain that CGN may be used by
>> >operators and discuss some of the factors that may go (or have gone) into
>> >that decision.  The point in the abstract was intended to tell the reader
>> >that the authors were not suggesting that CGN was "good" or "needed".
>> >
>> >There are some important points that I think are important within the
>> >section (section 2), so perhaps if I/we can remove specific text that seems
>> >to given the impression that we are defending CGN, I can do so.
> I'd like to understand what you think is important here.  Much of the
> text explaining why CGN is used basically amounts to justification for
> it.
Is your concern that  the sentence "IPv6 is considered the strategic 
answer" in section 2 is not stressed enough?

Regards, Benoit
>
> In contrast, the list of requirements you provide is fairly neutral
> and seems to cover most of the reasons well enough for me at least.
>


From martin.thomson@gmail.com  Wed Jan 22 07:01:51 2014
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84EB01A00DC for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 07:01:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QAxqZAvraQW0 for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 07:01:50 -0800 (PST)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD241A00CF for <gen-art@ietf.org>; Wed, 22 Jan 2014 07:01:49 -0800 (PST)
Received: by mail-we0-f169.google.com with SMTP id u57so410891wes.0 for <gen-art@ietf.org>; Wed, 22 Jan 2014 07:01:49 -0800 (PST)
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=l9KnD9oiXc2C9tdGwWAq9USDkPoS2GR5x3YPLMrkinc=; b=pUM29iPXdEgRUtNm7To3CpolaVunSS7hmMcQzvggOJ0fzJSRMN0nwT79ppy4t5PQQ3 CCPn6OVpllpHoWRIooMs411B8/Iq/D+alp82WCrq+eQvPdHlAlwIfryeqzdCbLDVHTWA FZcGwYL9w2+kBcR2tST2lsidgjmfLZCYvveq+Y4Icc+QKKqaTe79RY3khHGYamRBpANj AkYXXVN01GU+PYvvE9akcd/wA5jeq5PcJJCM7zCY2RYn/Lbo/BuqiTZ73nRzWAQeugQR sC7PmSdg8ZqEvL3h/38K1WwuA7WF41phjWp8srS8Bk4s3KxALSXhQ8C6/s6BIEu9ZSur R1Ag==
MIME-Version: 1.0
X-Received: by 10.181.13.165 with SMTP id ez5mr20236454wid.56.1390402909124; Wed, 22 Jan 2014 07:01:49 -0800 (PST)
Received: by 10.227.105.132 with HTTP; Wed, 22 Jan 2014 07:01:49 -0800 (PST)
In-Reply-To: <52DFB2D9.7030300@cisco.com>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com> <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com> <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com> <52DFB2D9.7030300@cisco.com>
Date: Wed, 22 Jan 2014 16:01:49 +0100
Message-ID: <CABkgnnW6ACt95BwkFQoLPU=3d=cQ_bZAYfnuuM3OzbVahXUWww@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: text/plain; charset=UTF-8
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org, Victor Kuarsingh <victor@jvknet.com>
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jan 2014 15:01:51 -0000

On 22 January 2014 13:00, Benoit Claise <bclaise@cisco.com> wrote:
> Is your concern that  the sentence "IPv6 is considered the strategic answer"
> in section 2 is not stressed enough?


I think that the text in the second paragraph is slightly more loaded.
 In particular,

   These issues
   leave an operator in a precarious position which may lead to the
   decision to deploy CGN.

The rest of the section uses similarly loaded:

   The ability to replace IPv4-only equipment may be out of the control
   of the operator, and even when it's in the administrative control, it
   poses both cost and technical challenges as operators build out
   massive programs for equipment retirement or upgrade.

"precarious position", "poses both cost and technical challenges", ...
all arguably true, but not strictly neutral.

From bclaise@cisco.com  Wed Jan 22 07:16:08 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E10A1A0116 for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 07:16:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7aiYg95TLrob for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 07:16:07 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 0E3DA1A00CF for <gen-art@ietf.org>; Wed, 22 Jan 2014 07:16:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1159; q=dns/txt; s=iport; t=1390403767; x=1391613367; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=1uDn2m+MoBab5vGEfGFLYJNzmnSemOHoeDy7+XTxb7c=; b=I38PzfISsMQ++X9uGsfgGcimBIDOwVPWwbI5RUBpHf39hTXSIYpgUyNi 8XalknZBXZ2suJoFVp7l4hBAwPXcUW3AgtLkF0unazyVnAt/9q+pqxKoW 7gvdeYEGgerX8QlcAg7vz8A8AaXFTul578V24hRoVg722yg2rwOpUyJ9Z A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAJPf31KQ/khR/2dsb2JhbABagwuEDLhggRIWdIIlAQEBBCMVQAEQCxgCAgUWCwICCQMCAQIBRQYNAQUCAQGIAaYVnDUXgSmNUweCb4FJAQOYIoZHi1GDLjs
X-IronPort-AV: E=Sophos;i="4.95,700,1384300800";  d="scan'208";a="3349445"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 22 Jan 2014 15:16:05 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0MFG5k9022914; Wed, 22 Jan 2014 15:16:05 GMT
Message-ID: <52DFE0B5.7010206@cisco.com>
Date: Wed, 22 Jan 2014 16:16:05 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com>	<CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com>	<CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com>	<52DFB2D9.7030300@cisco.com> <CABkgnnW6ACt95BwkFQoLPU=3d=cQ_bZAYfnuuM3OzbVahXUWww@mail.gmail.com>
In-Reply-To: <CABkgnnW6ACt95BwkFQoLPU=3d=cQ_bZAYfnuuM3OzbVahXUWww@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org, Victor Kuarsingh <victor@jvknet.com>
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jan 2014 15:16:08 -0000

On 22/01/2014 16:01, Martin Thomson wrote:
> On 22 January 2014 13:00, Benoit Claise <bclaise@cisco.com> wrote:
>> Is your concern that  the sentence "IPv6 is considered the strategic answer"
>> in section 2 is not stressed enough?
>
> I think that the text in the second paragraph is slightly more loaded.
>   In particular,
>
>     These issues
>     leave an operator in a precarious position which may lead to the
>     decision to deploy CGN.
>
> The rest of the section uses similarly loaded:
>
>     The ability to replace IPv4-only equipment may be out of the control
>     of the operator, and even when it's in the administrative control, it
>     poses both cost and technical challenges as operators build out
>     massive programs for equipment retirement or upgrade.
>
> "precarious position", "poses both cost and technical challenges", ...
> all arguably true, but not strictly neutral.
Understood.

Victor, can you please improve those sentences, to be more neutral.
Also, you might be stress again in that section:

    This document does not intend to defend the
    merits of CGN.


Regards, Benoit
> .
>


From victor@jvknet.com  Wed Jan 22 14:14:19 2014
Return-Path: <victor@jvknet.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 079011A0431 for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 14:14:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uB__Nwd1K4Vi for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 14:14:15 -0800 (PST)
Received: from mail-ve0-f178.google.com (mail-ve0-f178.google.com [209.85.128.178]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFAB1A03A7 for <gen-art@ietf.org>; Wed, 22 Jan 2014 14:14:15 -0800 (PST)
Received: by mail-ve0-f178.google.com with SMTP id oy12so650415veb.9 for <gen-art@ietf.org>; Wed, 22 Jan 2014 14:14:14 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=bQxX6n5245Jc9vuWVB3kE6ywkYfEyk/v3dvb6l1bHf0=; b=iJJ9r1/AlhtyAk4CJA1/sn6eoBmJgYEXGybb9S8jWtJvEGmLijSapr2f9Lv2Kgf7t8 W1ghK4iukp0Oi7K2952FXlaaB15QSDGAIisqw5uN/Tx2v1XJLB62HiRj3zZyYLYXKvD0 tUmAetbA/E7kumI/q/SbggWuVFzuQPr+h53C3HRGR5cvqisf1GLEC02miegcwuJcZBBe GxFCzVn5b/PYISpE9RT1kjyo0Ld5apF1IkN0t4RltXgkMIlJ3gKR6hFuoldbGJxeTBlb cfFEEdevQlkl60UuMV6ttC4pmeX/h0Hm3Spt6j8VCiutBkEwSzdJVdJOXp+Nox1gizNR +IPA==
X-Gm-Message-State: ALoCoQn99tWYdRtV0WW6xXej6EOX/UVCMfb2onOliRqp6ecz2TSEiLMFsoDznlG738+eGmcANbsV
MIME-Version: 1.0
X-Received: by 10.58.202.65 with SMTP id kg1mr27007vec.59.1390428854652; Wed, 22 Jan 2014 14:14:14 -0800 (PST)
Received: by 10.58.123.35 with HTTP; Wed, 22 Jan 2014 14:14:14 -0800 (PST)
In-Reply-To: <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com> <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com> <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com>
Date: Wed, 22 Jan 2014 17:14:14 -0500
Message-ID: <CAJc3aaOR4EFp4=fpY3tNRUKJEQCsnDGnq2troMX0ObP6yEPG0g@mail.gmail.com>
From: Victor Kuarsingh <victor@jvknet.com>
To: Martin Thomson <martin.thomson@gmail.com>, Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=047d7bdc8bc8f7a5b304f096711b
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jan 2014 22:14:19 -0000

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

Martin,

I appreciate your review and followup.  Your input was most helpful.  I
have made a few changes which will address you concerns.

(1). Used your simplified text in IANA considerations section

(2).  Added CGN label to Diagrams

(3). Removed significant amount of text from Modification section.  Basic
points say that IPv6 is the strategic answer, and CGN choice is an operator
independent decision. If used (CGN) deployment should not impact IPv4
legacy or IPv6 deployment.

(4). Removed second paragraph from security section as you suggested to
help up and remove vagueness.

(5)  Used your recommended text on redundancy model.

regards,

Victor K







On Thu, Jan 16, 2014 at 1:33 PM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 15 January 2014 19:40, Victor Kuarsingh <victor@jvknet.com> wrote:
> >> Which seems wise given their somewhat contentious nature.  But then
> >> the entirely of Section 2 does exactly the opposite.  I don't know
> >> what the right answer is here, but maybe the right thing to do is
> >> delete Section 2.
> >
> >
> > [VK]  The intention of this section was to explain that CGN may be used
> by
> > operators and discuss some of the factors that may go (or have gone) into
> > that decision.  The point in the abstract was intended to tell the reader
> > that the authors were not suggesting that CGN was "good" or "needed".
> >
> > There are some important points that I think are important within the
> > section (section 2), so perhaps if I/we can remove specific text that
> seems
> > to given the impression that we are defending CGN, I can do so.
>
> I'd like to understand what you think is important here.  Much of the
> text explaining why CGN is used basically amounts to justification for
> it.
>
> In contrast, the list of requirements you provide is fairly neutral
> and seems to cover most of the reasons well enough for me at least.
>
> >> I'm not sure what "security measures" might be employed here:
> >>
> >>    If a provider plans to operate the pre-translation realm (CPE towards
> >>    translator IPv4 zone) as a non-public like network, then additional
> >>    security measures may be needed to secure this environment.
> >>
> >> What might be secured in these scenarios?  Confidentiality?  Access to
> >> network resources?  Perhaps this should talk about what a network
> >> operator wants to secure: access to the network.  Then maybe talk
> >> about access control and isolation.
> >
> >
> > [VK]  The point here was that the document/authors have assumed the
> position
> > that the CGN realm (within the context of this document) is that it's
> > publicly accessible (to the extent that it can be behind a translation
> > function.   The point was that if an operator wanted something more
> secure
> > (which can be a number of thinks include items you listed like access
> > to/from the Internet etc) that those would require mode consideration.
> >
> > We did not itemize those considerations as any list I generate would be
> > somewhat arbitrary (should I select a few examples).  If you feel that
> such
> > a partial listing is material, I can do so.  My concern here is that
> once we
> > put in such a list, we may have to deal with conversations like "why did
> you
> > not include such and such .. etc"
> >
> > The overall expectation is that the operator should expect the same
> level of
> > exposure as traditional customers.
>
> The problem with the text as it stands is that it is vague to the
> point that it actively encourages the sorts of questions I raised.
>
> If you want to avoid the questions, maybe consider whether the
> sentence is even needed.
>
> >> In Section 4, this seems a little vague:
> >>
> >>    Various redundancy models
> >>    can be used within this architecture to support failover from one
> >>    physical CGN hardware instance to another.
> >>
> >> I don't expect an enumeration of the options, but this seems important
> >> enough to at least point to where the redundancy options might exist?
> >> Redundant "VPNs"/LSPs?  Redundant paths from the VRF termination?
> >
> >
> > [VK] Our expectation was that the operator would be able to derive their
> own
> > answers on how to enable redundancy in their model.  The expectation is
> that
> > the reader already would understand (or would need to verse themselves)
> CGN
> > and MPLS/VPNs.  Therefore they would be able to enumerate the options on
> > their own.
> >
> > We were trying to keep the text simple and show the basic association of
> how
> > to deploy the CGN using MPLS/VPNs.  I would not want to sound
> prescriptive
> > on how to actually design a specific instance.
> >
> > In disclosure, when I did my design, I did use multiple RD/RTs and
> imported
> > those routes into a common CPE VPN.  But that specific option may not be
> > used by others. I would expect an operator who has already deployed
> > MPLS/VPNs to have a redundancy model already in place, and they would
> evolve
> > that for this purpose.
> >
> > To exemplify that point, I had discussions with two other Canadian ISPs
> who
> > tested/integrated CGNs using this method (MPLS/VPNs) and one did not put
> in
> > network based redundancy (just had to CGN functions at a common
> > endpoint/VRF) and the other did have redundancy but only employed a
> single
> > RD/RT (and just had multiple defaults).  Each of us (three) chose
> redundancy
> > models which matched our pre-existing MPLS network designs.  I would
> expect
> > the same from others as well (although this may be a poor assumption).
>
> I don't think that you have to enumerate, though it is perhaps the
> wording that is the problem here.  As phrased it implies a panoply of
> wonderful options that are being purposefully withheld from the
> reader.  Perhaps a rephrasing will make this intent clearer:
>
> The described architecture does not prescribe a single redundancy
> model that ensures network availability as a result of CGN failure.
> Deployments are able to select a redundancy model that fits best with
> their network design.
>

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

<div dir=3D"ltr">Martin,<div><br></div><div>I appreciate your review and fo=
llowup. =A0Your input was most helpful. =A0I have made a few changes which =
will address you concerns.</div><div><br></div><div>(1). Used your simplifi=
ed text in IANA considerations section</div>
<div><br></div><div>(2). =A0Added CGN label to Diagrams</div><div><br></div=
><div>(3). Removed significant amount of text from Modification section. =
=A0Basic points say that IPv6 is the strategic answer, and CGN choice is an=
 operator independent decision. If used (CGN) deployment should not impact =
IPv4 legacy or IPv6 deployment.</div>
<div><br></div><div>(4). Removed second paragraph from security section as =
you suggested to help up and remove vagueness.</div><div><br></div><div>(5)=
 =A0Used your recommended text on redundancy model.</div><div><br></div><di=
v>
regards,</div><div><br></div><div>Victor K</div><div><br></div><div><br></d=
iv><div><br></div><div><br></div><div><br></div></div><div class=3D"gmail_e=
xtra"><br><br><div class=3D"gmail_quote">On Thu, Jan 16, 2014 at 1:33 PM, M=
artin Thomson <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.thomson@gmail.=
com" target=3D"_blank">martin.thomson@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">On 15 January 2014 19:40, Victor Kuarsingh &=
lt;<a href=3D"mailto:victor@jvknet.com">victor@jvknet.com</a>&gt; wrote:<br=
>
&gt;&gt; Which seems wise given their somewhat contentious nature. =A0But t=
hen<br>
&gt;&gt; the entirely of Section 2 does exactly the opposite. =A0I don&#39;=
t know<br>
&gt;&gt; what the right answer is here, but maybe the right thing to do is<=
br>
&gt;&gt; delete Section 2.<br>
&gt;<br>
&gt;<br>
&gt; [VK] =A0The intention of this section was to explain that CGN may be u=
sed by<br>
&gt; operators and discuss some of the factors that may go (or have gone) i=
nto<br>
&gt; that decision. =A0The point in the abstract was intended to tell the r=
eader<br>
&gt; that the authors were not suggesting that CGN was &quot;good&quot; or =
&quot;needed&quot;.<br>
&gt;<br>
&gt; There are some important points that I think are important within the<=
br>
&gt; section (section 2), so perhaps if I/we can remove specific text that =
seems<br>
&gt; to given the impression that we are defending CGN, I can do so.<br>
<br>
I&#39;d like to understand what you think is important here. =A0Much of the=
<br>
text explaining why CGN is used basically amounts to justification for<br>
it.<br>
<br>
In contrast, the list of requirements you provide is fairly neutral<br>
and seems to cover most of the reasons well enough for me at least.<br>
<br>
&gt;&gt; I&#39;m not sure what &quot;security measures&quot; might be emplo=
yed here:<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0If a provider plans to operate the pre-translation realm (C=
PE towards<br>
&gt;&gt; =A0 =A0translator IPv4 zone) as a non-public like network, then ad=
ditional<br>
&gt;&gt; =A0 =A0security measures may be needed to secure this environment.=
<br>
&gt;&gt;<br>
&gt;&gt; What might be secured in these scenarios? =A0Confidentiality? =A0A=
ccess to<br>
&gt;&gt; network resources? =A0Perhaps this should talk about what a networ=
k<br>
&gt;&gt; operator wants to secure: access to the network. =A0Then maybe tal=
k<br>
&gt;&gt; about access control and isolation.<br>
&gt;<br>
&gt;<br>
&gt; [VK] =A0The point here was that the document/authors have assumed the =
position<br>
&gt; that the CGN realm (within the context of this document) is that it&#3=
9;s<br>
&gt; publicly accessible (to the extent that it can be behind a translation=
<br>
&gt; function. =A0 The point was that if an operator wanted something more =
secure<br>
&gt; (which can be a number of thinks include items you listed like access<=
br>
&gt; to/from the Internet etc) that those would require mode consideration.=
<br>
&gt;<br>
&gt; We did not itemize those considerations as any list I generate would b=
e<br>
&gt; somewhat arbitrary (should I select a few examples). =A0If you feel th=
at such<br>
&gt; a partial listing is material, I can do so. =A0My concern here is that=
 once we<br>
&gt; put in such a list, we may have to deal with conversations like &quot;=
why did you<br>
&gt; not include such and such .. etc&quot;<br>
&gt;<br>
&gt; The overall expectation is that the operator should expect the same le=
vel of<br>
&gt; exposure as traditional customers.<br>
<br>
The problem with the text as it stands is that it is vague to the<br>
point that it actively encourages the sorts of questions I raised.<br>
<br>
If you want to avoid the questions, maybe consider whether the<br>
sentence is even needed.<br>
<br>
&gt;&gt; In Section 4, this seems a little vague:<br>
&gt;&gt;<br>
&gt;&gt; =A0 =A0Various redundancy models<br>
&gt;&gt; =A0 =A0can be used within this architecture to support failover fr=
om one<br>
&gt;&gt; =A0 =A0physical CGN hardware instance to another.<br>
&gt;&gt;<br>
&gt;&gt; I don&#39;t expect an enumeration of the options, but this seems i=
mportant<br>
&gt;&gt; enough to at least point to where the redundancy options might exi=
st?<br>
&gt;&gt; Redundant &quot;VPNs&quot;/LSPs? =A0Redundant paths from the VRF t=
ermination?<br>
&gt;<br>
&gt;<br>
&gt; [VK] Our expectation was that the operator would be able to derive the=
ir own<br>
&gt; answers on how to enable redundancy in their model. =A0The expectation=
 is that<br>
&gt; the reader already would understand (or would need to verse themselves=
) CGN<br>
&gt; and MPLS/VPNs. =A0Therefore they would be able to enumerate the option=
s on<br>
&gt; their own.<br>
&gt;<br>
&gt; We were trying to keep the text simple and show the basic association =
of how<br>
&gt; to deploy the CGN using MPLS/VPNs. =A0I would not want to sound prescr=
iptive<br>
&gt; on how to actually design a specific instance.<br>
&gt;<br>
&gt; In disclosure, when I did my design, I did use multiple RD/RTs and imp=
orted<br>
&gt; those routes into a common CPE VPN. =A0But that specific option may no=
t be<br>
&gt; used by others. I would expect an operator who has already deployed<br=
>
&gt; MPLS/VPNs to have a redundancy model already in place, and they would =
evolve<br>
&gt; that for this purpose.<br>
&gt;<br>
&gt; To exemplify that point, I had discussions with two other Canadian ISP=
s who<br>
&gt; tested/integrated CGNs using this method (MPLS/VPNs) and one did not p=
ut in<br>
&gt; network based redundancy (just had to CGN functions at a common<br>
&gt; endpoint/VRF) and the other did have redundancy but only employed a si=
ngle<br>
&gt; RD/RT (and just had multiple defaults). =A0Each of us (three) chose re=
dundancy<br>
&gt; models which matched our pre-existing MPLS network designs. =A0I would=
 expect<br>
&gt; the same from others as well (although this may be a poor assumption).=
<br>
<br>
I don&#39;t think that you have to enumerate, though it is perhaps the<br>
wording that is the problem here. =A0As phrased it implies a panoply of<br>
wonderful options that are being purposefully withheld from the<br>
reader. =A0Perhaps a rephrasing will make this intent clearer:<br>
<br>
The described architecture does not prescribe a single redundancy<br>
model that ensures network availability as a result of CGN failure.<br>
Deployments are able to select a redundancy model that fits best with<br>
their network design.<br>
</blockquote></div><br></div>

--047d7bdc8bc8f7a5b304f096711b--

From victor@jvknet.com  Wed Jan 22 14:18:20 2014
Return-Path: <victor@jvknet.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 714601A04A4 for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 14:18:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b78y88l7LXZz for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 14:18:18 -0800 (PST)
Received: from mail-ve0-f169.google.com (mail-ve0-f169.google.com [209.85.128.169]) by ietfa.amsl.com (Postfix) with ESMTP id 6070B1A0492 for <gen-art@ietf.org>; Wed, 22 Jan 2014 14:18:18 -0800 (PST)
Received: by mail-ve0-f169.google.com with SMTP id oy12so645135veb.0 for <gen-art@ietf.org>; Wed, 22 Jan 2014 14:18:17 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Rhs6DIdntHDEXOavk3T7sC1K5SkAhdyotdB0GDP/+lM=; b=bcijyPuDCCfawup7akAHySbAmEAD5MAusyEy6ew0J6/Rkf1nPRYHzlxhCOhgR6zeLW 2u+fGSHy3LjdYv68kUm8rxpALUdrRTIJTxKHJnprMkr9ipnBrAQiRXubrIDs4T4j7jgM UtvHB/ssTyXSf18iUS/JDOUFhV5WakWsbVQqI3G3dWCpY+tL8YmebxgEAi9JUnG486Vo vNzIfJKpp/9ZGtcXKjKfKF+bYtYOL6hqBjHey108EQAH7ALlpuhp1eJA2qOUqpeV6wdg UuexHS1rmYD+T5WevxCqeR7Mr4GGn2f2memm1RRvg5fpmzJlcDLWfnIFK3T1vLs8NzCN +CcA==
X-Gm-Message-State: ALoCoQkijffXuvjR4Jo7pKOKP9aDOMl0mDvlZBa5eBzPKEo2TLo9wW1wOfJbT4rQmu/F9q5H/OzG
MIME-Version: 1.0
X-Received: by 10.220.164.80 with SMTP id d16mr2577746vcy.15.1390429097699; Wed, 22 Jan 2014 14:18:17 -0800 (PST)
Received: by 10.58.123.35 with HTTP; Wed, 22 Jan 2014 14:18:17 -0800 (PST)
In-Reply-To: <3C5B486D-ED82-4ABC-9CAE-B720729791D2@piuha.net>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com> <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com> <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com> <3C5B486D-ED82-4ABC-9CAE-B720729791D2@piuha.net>
Date: Wed, 22 Jan 2014 17:18:17 -0500
Message-ID: <CAJc3aaOPNxMOcejieKucB4e_DSpGYOPtiF8w6TDvG4fbYDOqxA@mail.gmail.com>
From: Victor Kuarsingh <victor@jvknet.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=047d7b3a946a743dc304f09680fb
Cc: Benoit Claise <bclaise@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jan 2014 22:18:20 -0000

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

Jari,

I just responded to the gen-art list and Martin on his comments.

I have made a number of changes that address his comments and have used
much of his text.  ( I will be sending the Benoit and the rest of the IESG
a full summary of changes and new version posting tonight).

This includes the changes to section 6 as prescribed.

regards,

Victor K


On Tue, Jan 21, 2014 at 6:06 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> Thanks for your detailed review, Martin!
>
> And thank you Victor for a very useful document!
>
> Much of the discussion in this thread is important but also partly
> editorial. I'll leave it to sort out between yourselves.
>
> However, I do think Section 6 last sentence:
>
>    Should a provide choose to use non-assigned IP address space within
> their translation realms, then considerations may apply.
>
> gives an odd impression. We already have shared address space (as the
> document notes elsewhere), so it is not clear to me what the above might
> entail, particularly when (a) regular address space assignments go through
> the RIR system not IANA (b) use of unassigned address space is probably not
> something that we want to recommend and (c) if we need to do something
> beyond the existing shared address space allocation, then that probably
> deserves its own document.
>
> I can see that Victor you've already agreed to make a change wrt Section
> 6. I just wanted to check that this is indeed the plan, so that we can move
> on to approving the document :-)
>
> Jari
>
>

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

<div dir=3D"ltr">Jari,<div><br></div><div>I just responded to the gen-art l=
ist and Martin on his comments.</div><div><br></div><div>I have made a numb=
er of changes that address his comments and have used much of his text. =A0=
( I will be sending the Benoit and the rest of the IESG a full summary of c=
hanges and new version posting tonight).</div>
<div><br></div><div>This includes the changes to section 6 as prescribed.</=
div><div><br></div><div>regards,</div><div><br></div><div>Victor K</div></d=
iv><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Ja=
n 21, 2014 at 6:06 PM, Jari Arkko <span dir=3D"ltr">&lt;<a href=3D"mailto:j=
ari.arkko@piuha.net" target=3D"_blank">jari.arkko@piuha.net</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">Thanks for your detailed review, Martin!<br>
<br>
And thank you Victor for a very useful document!<br>
<br>
Much of the discussion in this thread is important but also partly editoria=
l. I&#39;ll leave it to sort out between yourselves.<br>
<br>
However, I do think Section 6 last sentence:<br>
<br>
=A0 =A0Should a provide choose to use non-assigned IP address space within =
their translation realms, then considerations may apply.<br>
<br>
gives an odd impression. We already have shared address space (as the docum=
ent notes elsewhere), so it is not clear to me what the above might entail,=
 particularly when (a) regular address space assignments go through the RIR=
 system not IANA (b) use of unassigned address space is probably not someth=
ing that we want to recommend and (c) if we need to do something beyond the=
 existing shared address space allocation, then that probably deserves its =
own document.<br>

<br>
I can see that Victor you&#39;ve already agreed to make a change wrt Sectio=
n 6. I just wanted to check that this is indeed the plan, so that we can mo=
ve on to approving the document :-)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br></div>

--047d7b3a946a743dc304f09680fb--

From victor@jvknet.com  Wed Jan 22 14:22:10 2014
Return-Path: <victor@jvknet.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36F541A04CB for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 14:22:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l8zNo2smjLXl for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 14:22:08 -0800 (PST)
Received: from mail-ve0-f175.google.com (mail-ve0-f175.google.com [209.85.128.175]) by ietfa.amsl.com (Postfix) with ESMTP id 625881A04DA for <gen-art@ietf.org>; Wed, 22 Jan 2014 14:22:08 -0800 (PST)
Received: by mail-ve0-f175.google.com with SMTP id c14so636309vea.20 for <gen-art@ietf.org>; Wed, 22 Jan 2014 14:22:07 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ums0ljgvk4pXaNeFXm3sspu+meX5FY3oYTQNJqBf+vg=; b=ENejcQ6LFswywyt8PlZGZ9SpzqWO3zBrU5uag0s02g2DMNBDPdpdab/yOeREk15qX5 pCJ9HL7w0f0sEJoXz7vkjEOqHKzNFiJezC5hi8koaVAUNJHfA+o5/nqiPlIqR/yGOKsP SGkDzCnCR22uEp6VAgrd5w1owbe0K3lyl1fR0MxSDiaPgBwBl1Zjxft4ZXC9TTf+YuQz JkoqBDTamIdGeum0flvVR7VMSeHlvEwUI4PXZwmBoFcphrq67LtE//LCdyF0CdU3m+HJ dIrr57iXvp+D9a48JpIeAHlqTXSoSetGWN2VormGyXo7Gpn1FZRa2M0xWcYt/VyPBL8U Iokw==
X-Gm-Message-State: ALoCoQkGwaUbXRDebfeKClS838+CArjHzxcQqCK1p00diK6JT7QMFgvszuV0c6wHNt8LM4RTRWb6
MIME-Version: 1.0
X-Received: by 10.59.6.225 with SMTP id cx1mr99991ved.50.1390429327656; Wed, 22 Jan 2014 14:22:07 -0800 (PST)
Received: by 10.58.123.35 with HTTP; Wed, 22 Jan 2014 14:22:07 -0800 (PST)
In-Reply-To: <CABkgnnW6ACt95BwkFQoLPU=3d=cQ_bZAYfnuuM3OzbVahXUWww@mail.gmail.com>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com> <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com> <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com> <52DFB2D9.7030300@cisco.com> <CABkgnnW6ACt95BwkFQoLPU=3d=cQ_bZAYfnuuM3OzbVahXUWww@mail.gmail.com>
Date: Wed, 22 Jan 2014 17:22:07 -0500
Message-ID: <CAJc3aaOBz3j2F37-hjmffgpQZnPwgiEZVv_b3hFXvV4VgB9fKQ@mail.gmail.com>
From: Victor Kuarsingh <victor@jvknet.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bf0cce22922cd04f0968e1f
Cc: Benoit Claise <bclaise@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 22 Jan 2014 22:22:10 -0000

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

Martin,

I am loading a new new version today, but here is that section (originally
called "Motivation") for quick review.

** Beginning of section **

Existing Network Considerations (new name of section)

The selection of CGN may be made by an operator based on a number of
factors. The overall driver to use CGN may be the depletion of IPv4 address
pools which leaves little to no addresses for a growing IPv4 service or
connection demand growth. IPv6 is considered the strategic answer for IPv4
address depletion; however, the operator may independently decide that CGN
is needed to supplement IPv6 and address their particular IPv4 service
deployment needs.

If the operator has chosen to deploy CGN, they should do this in a manner
as not to negatively impact the existing IPv4 or IPv6 subscriber base. This
will include solving a number of challenges since subscribers whose
connections require translation will have network routing and flow needs
which are different from legacy IPv4 connections.

** End of section **

regards,

Victor K



On Wed, Jan 22, 2014 at 10:01 AM, Martin Thomson
<martin.thomson@gmail.com>wrote:

> On 22 January 2014 13:00, Benoit Claise <bclaise@cisco.com> wrote:
> > Is your concern that  the sentence "IPv6 is considered the strategic
> answer"
> > in section 2 is not stressed enough?
>
>
> I think that the text in the second paragraph is slightly more loaded.
>  In particular,
>
>    These issues
>    leave an operator in a precarious position which may lead to the
>    decision to deploy CGN.
>
> The rest of the section uses similarly loaded:
>
>    The ability to replace IPv4-only equipment may be out of the control
>    of the operator, and even when it's in the administrative control, it
>    poses both cost and technical challenges as operators build out
>    massive programs for equipment retirement or upgrade.
>
> "precarious position", "poses both cost and technical challenges", ...
> all arguably true, but not strictly neutral.
>

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

<div dir=3D"ltr">Martin,<div><br></div><div>I am loading a new new version =
today, but here is that section (originally called &quot;Motivation&quot;) =
for quick review.</div><div><br></div><div>** Beginning of section **</div>
<div><br></div><div>Existing Network Considerations (new name of section)<b=
r></div><div><br></div><div>The selection of CGN may be made by an operator=
 based on a number of factors. The overall driver to use CGN may be the dep=
letion of IPv4 address pools which leaves little to no addresses for a grow=
ing IPv4 service or connection demand growth. IPv6 is considered the strate=
gic answer for IPv4 address depletion; however, the operator may independen=
tly decide that CGN is needed to supplement IPv6 and address their particul=
ar IPv4 service deployment needs.<br>
</div><div><br></div><div>If the operator has chosen to deploy CGN, they sh=
ould do this in a manner as not to negatively impact the existing IPv4 or I=
Pv6 subscriber base. This will include solving a number of challenges since=
 subscribers whose connections require translation will have network routin=
g and flow needs which are different from legacy IPv4 connections.<br>
</div><div><br></div><div>** End of section **</div><div><br></div><div>reg=
ards,</div><div><br></div><div>Victor K</div><div><br></div></div><div clas=
s=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Jan 22, 2014 a=
t 10:01 AM, Martin Thomson <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.t=
homson@gmail.com" target=3D"_blank">martin.thomson@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">On 22 January 2014 13:00, Benoit Claise &lt;=
<a href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt; wrote:<br>
&gt; Is your concern that =A0the sentence &quot;IPv6 is considered the stra=
tegic answer&quot;<br>
&gt; in section 2 is not stressed enough?<br>
<br>
<br>
I think that the text in the second paragraph is slightly more loaded.<br>
=A0In particular,<br>
<br>
=A0 =A0These issues<br>
=A0 =A0leave an operator in a precarious position which may lead to the<br>
=A0 =A0decision to deploy CGN.<br>
<br>
The rest of the section uses similarly loaded:<br>
<br>
=A0 =A0The ability to replace IPv4-only equipment may be out of the control=
<br>
=A0 =A0of the operator, and even when it&#39;s in the administrative contro=
l, it<br>
=A0 =A0poses both cost and technical challenges as operators build out<br>
=A0 =A0massive programs for equipment retirement or upgrade.<br>
<br>
&quot;precarious position&quot;, &quot;poses both cost and technical challe=
nges&quot;, ...<br>
all arguably true, but not strictly neutral.<br>
</blockquote></div><br></div>

--047d7bf0cce22922cd04f0968e1f--

From martin.thomson@gmail.com  Wed Jan 22 20:21:16 2014
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8775C1A0157 for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 20:21:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uInU4PwLibe2 for <gen-art@ietfa.amsl.com>; Wed, 22 Jan 2014 20:21:14 -0800 (PST)
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 5E16A1A0101 for <gen-art@ietf.org>; Wed, 22 Jan 2014 20:21:14 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id hr1so6398827wib.8 for <gen-art@ietf.org>; Wed, 22 Jan 2014 20:21:13 -0800 (PST)
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=PvdO3oTrosumdOtPHYyVLJH5bKs9qF76FJPC2rO3CAs=; b=xROS9QTfcjYnt91hHgANvCBWzS7hAnUVchmF4Kz/xqEKSbuOpqmd5+zpuoybbL6/vE 3TlL409xqe5Y+tn0k8KhtRG6eGBuicI3GJSmwY58FYcBffV9e9I1iRW4BaWLTZufzYgC mvHuqcgg8CAYWym3Qfrpdx8MI2a4umfdmxKgYFelOASSBenx/xODLM8RB7V5XRV+0Muo 3UmglE9OK7apWgGqkYX0oRtipQHpfIm61wrgjK2ytrpGnYvD0VkDBUfXtCKtpgHaOoRi uWk6zwtB5veJJm247haCwazlE0rb9UKSAjAoYiMVxVT7LThTKFJ+B0Lkp8hpgMyxqy+W XQ6Q==
MIME-Version: 1.0
X-Received: by 10.194.79.165 with SMTP id k5mr4833707wjx.44.1390450873160; Wed, 22 Jan 2014 20:21:13 -0800 (PST)
Received: by 10.227.105.132 with HTTP; Wed, 22 Jan 2014 20:21:13 -0800 (PST)
In-Reply-To: <CAJc3aaOBz3j2F37-hjmffgpQZnPwgiEZVv_b3hFXvV4VgB9fKQ@mail.gmail.com>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com> <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com> <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com> <52DFB2D9.7030300@cisco.com> <CABkgnnW6ACt95BwkFQoLPU=3d=cQ_bZAYfnuuM3OzbVahXUWww@mail.gmail.com> <CAJc3aaOBz3j2F37-hjmffgpQZnPwgiEZVv_b3hFXvV4VgB9fKQ@mail.gmail.com>
Date: Thu, 23 Jan 2014 05:21:13 +0100
Message-ID: <CABkgnnVcLjsvr69v8be4ivLohVbJSNydP+_55hm2wXp-=LXSXw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Victor Kuarsingh <victor@jvknet.com>
Content-Type: text/plain; charset=UTF-8
Cc: Benoit Claise <bclaise@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 04:21:16 -0000

WFM

On 22 January 2014 23:22, Victor Kuarsingh <victor@jvknet.com> wrote:
> Martin,
>
> I am loading a new new version today, but here is that section (originally
> called "Motivation") for quick review.
>
> ** Beginning of section **
>
> Existing Network Considerations (new name of section)
>
> The selection of CGN may be made by an operator based on a number of
> factors. The overall driver to use CGN may be the depletion of IPv4 address
> pools which leaves little to no addresses for a growing IPv4 service or
> connection demand growth. IPv6 is considered the strategic answer for IPv4
> address depletion; however, the operator may independently decide that CGN
> is needed to supplement IPv6 and address their particular IPv4 service
> deployment needs.
>
> If the operator has chosen to deploy CGN, they should do this in a manner as
> not to negatively impact the existing IPv4 or IPv6 subscriber base. This
> will include solving a number of challenges since subscribers whose
> connections require translation will have network routing and flow needs
> which are different from legacy IPv4 connections.
>
> ** End of section **
>
> regards,
>
> Victor K
>
>
>
> On Wed, Jan 22, 2014 at 10:01 AM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>>
>> On 22 January 2014 13:00, Benoit Claise <bclaise@cisco.com> wrote:
>> > Is your concern that  the sentence "IPv6 is considered the strategic
>> > answer"
>> > in section 2 is not stressed enough?
>>
>>
>> I think that the text in the second paragraph is slightly more loaded.
>>  In particular,
>>
>>    These issues
>>    leave an operator in a precarious position which may lead to the
>>    decision to deploy CGN.
>>
>> The rest of the section uses similarly loaded:
>>
>>    The ability to replace IPv4-only equipment may be out of the control
>>    of the operator, and even when it's in the administrative control, it
>>    poses both cost and technical challenges as operators build out
>>    massive programs for equipment retirement or upgrade.
>>
>> "precarious position", "poses both cost and technical challenges", ...
>> all arguably true, but not strictly neutral.
>
>

From TurnerS@ieca.com  Thu Jan 23 05:05:46 2014
Return-Path: <TurnerS@ieca.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBE281A03E3 for <gen-art@ietfa.amsl.com>; Thu, 23 Jan 2014 05:05:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level: 
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nWwsqn8q3-64 for <gen-art@ietfa.amsl.com>; Thu, 23 Jan 2014 05:05:45 -0800 (PST)
Received: from gateway03.websitewelcome.com (gateway03.websitewelcome.com [69.93.139.30]) by ietfa.amsl.com (Postfix) with ESMTP id EE3E81A00CA for <gen-art@ietf.org>; Thu, 23 Jan 2014 05:05:44 -0800 (PST)
Received: by gateway03.websitewelcome.com (Postfix, from userid 5007) id 0ECA6F083663; Thu, 23 Jan 2014 07:05:44 -0600 (CST)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway03.websitewelcome.com (Postfix) with ESMTP id E2075F083609 for <gen-art@ietf.org>; Thu, 23 Jan 2014 07:05:43 -0600 (CST)
Received: from [198.180.150.142] (port=52119 helo=v142.vpn.iad.rg.net) by gator3286.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <TurnerS@ieca.com>) id 1W6JyT-0000Wz-0d; Thu, 23 Jan 2014 07:05:42 -0600
Content-Type: multipart/signed; boundary="Apple-Mail=_183BD477-3F23-4506-8B3F-8034893C1791"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Sean Turner <TurnerS@ieca.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F2406584BAC24@MX15A.corp.emc.com>
Date: Thu, 23 Jan 2014 14:05:19 +0100
Message-Id: <D0B4A07D-66D3-47C3-A6AE-0E52C6469209@ieca.com>
References: <201401131355.s0DDtd4t028318@givry.fdupont.fr> <F5063677821E3B4F81ACFB7905573F2406584BA472@MX15A.corp.emc.com> <60C55DB1-4D56-4031-8A79-D56D71B55246@piuha.net> <F5063677821E3B4F81ACFB7905573F2406584BAC24@MX15A.corp.emc.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1827)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source-IP: 198.180.150.142
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (v142.vpn.iad.rg.net) [198.180.150.142]:52119
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 2
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-moriarty-pkcs12v1-1.all@tools.ietf.org" <draft-moriarty-pkcs12v1-1.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-moriarty-pkcs12v1-1-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 13:05:46 -0000

--Apple-Mail=_183BD477-3F23-4506-8B3F-8034893C1791
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

My other thought here is that we know complexity is bad ;)  The specific =
concern about that command is specific to openssl ad though widely =
deployed doesn=92t really belong in this draft.

spt

On Jan 21, 2014, at 16:38, Moriarty, Kathleen =
<kathleen.moriarty@emc.com> wrote:

> Hi Jari,
>=20
> Since this document is meant to transfer change control to the IETF, =
RSA would prefer to leave the document in-tact to match their published =
version as much as possible.  There is IETF interest in starting a draft =
as soon as this is published to correct the well-known issues.  We would =
prefer to take that approach and I am working to make sure we have at =
least one resource to edit the new document who has the background to =
make the changes and there may be others.
>=20
> Thank you,
> Kathleen
>=20
> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko@piuha.net]=20
> Sent: Tuesday, January 21, 2014 10:31 AM
> To: Moriarty, Kathleen; Sean P. Turner
> Cc: Francis.Dupont@fdupont.fr; gen-art@ietf.org; =
draft-moriarty-pkcs12v1-1.all@tools.ietf.org
> Subject: Re: [Gen-art] review of draft-moriarty-pkcs12v1-1-03.txt
>=20
> Thanks for your review, Francis, and for your edits, Kathleen.
>=20
> Do you Kathleen or Sean think that Francis' comment on strengthening =
the security considerations would be something that you should address?
>=20
> jari
>=20
> On Jan 13, 2014, at 6:02 PM, "Moriarty, Kathleen" =
<kathleen.moriarty@emc.com> wrote:
>=20
>> Hi Francis,
>>=20
>> I went to update your comments in my draft version and in thinking =
about it more, I agree with the current text on the public/private =
order.  As I read it, the referenced keys are discussed for the keys =
that validate and I assume you read it as the creation of a signature or =
to encrypt.  I'm going to leave that as-is.
>>=20
>> Thanks,
>> Kathleen
>>=20
>> -----Original Message-----
>> From: Moriarty, Kathleen
>> Sent: Monday, January 13, 2014 9:42 AM
>> To: 'Francis.Dupont@fdupont.fr'; gen-art@ietf.org
>> Cc: draft-moriarty-pkcs12v1-1.all@tools.ietf.org
>> Subject: RE: review of draft-moriarty-pkcs12v1-1-03.txt
>>=20
>> Thank you for the review, Francis.
>>=20
>> Once this version is published, change control and copyright is =
transferred to the IETF.  The next version of this document will work to =
improve known issues.
>>=20
>> I will make the change from public/private to private/public as =
noted, that makes sense.  I would imagine it was only written that way =
as the key pairs are typically referred to in that order as opposed to =
the original author thinking through the sentence as you had done.
>>=20
>> I have a few other edits to include and will have this ready before =
the end of the week.
>>=20
>> Thank you,
>> Kathleen
>>=20
>> -----Original Message-----
>> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
>> Sent: Monday, January 13, 2014 8:56 AM
>> To: gen-art@ietf.org
>> Cc: draft-moriarty-pkcs12v1-1.all@tools.ietf.org
>> Subject: review of draft-moriarty-pkcs12v1-1-03.txt
>>=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-moriarty-pkcs12v1-1-03.txt
>> Reviewer: Francis Dupont
>> Review Date: 20130104
>> IETF LC End Date: 20130110
>> IESG Telechat date: unknown
>>=20
>> Summary: Ready
>>=20
>> Major issues: None
>>=20
>> Minor issues: (not really technical)
>> PKCS#12 was subject to concerns from teh cryptography community, in =
particular from Peter Gutmann, based on:
>> - its (too) high complexity (BTW IMHO it is a legitimate concern:
>> complexity is not wellcome for a security device)
>> - (related to the previous item) its possible misuse with private  =
key, summarized by this famous warning in OpenSSL FAQ:
>> "Occasionally someone suggests using a command such as:
>>=20
>> openssl pkcs12 -export -out cacert.p12 -in cacert.pem -inkey =
cakey.pem
>>=20
>> DO NOT DO THIS! This command will give away your CAs private key and =
reduces its security to zero: allowing anyone to forge certificates in =
whatever name they choose."
>>=20
>> Unfortunately I can't see how we can address these concerns in the =
document. Perhaps with a stronger security considerations section?
>>=20
>> Nits/editorial comments:
>> - TOC page 3 and F page 29: Acknowledgements -> Acknowledgments
>>=20
>> - 1 page 4 in:
>>     The most secure of the privacy
>>  and integrity modes require the source and destination platforms to
>>  have trusted public/private key pairs usable for digital signatures
>>  and encryption, respectively.
>>=20
>> respectively suggests the same order but the private key is used to =20=

>> sign and the public key to encrypt. I propose to swap keys, i.e.,  to=20=

>> use "private/public" key pairs.
>>=20
>> - 5.1 5 B page 16: i.e. -> i.e.,
>>=20
>> - a full example should have been wellcome but IMHO it is far too =
late =20
>> (and there are a lot of tools able to produce examples if needed :-).
>>=20
>> Regards
>>=20
>> Francis.Dupont@fdupont.fr
>>=20
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20
>=20


--Apple-Mail=_183BD477-3F23-4506-8B3F-8034893C1791
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIEgDCCBHww
ggJkoAMCAQICCQCdWMxKNutUeTANBgkqhkiG9w0BAQsFADAiMQswCQYDVQQGEwJVUzETMBEGA1UE
ChMKSUVDQSwgSW5jLjAeFw0xMzA0MDMxNDUxMThaFw0xNDA0MDMxNDUxMThaMDgxCzAJBgNVBAYT
AlVTMRMwEQYDVQQKEwpJRUNBLCBJbmMuMRQwEgYDVQQDEwtTZWFuIFR1cm5lcjCCASIwDQYJKoZI
hvcNAQEBBQADggEPADCCAQoCggEBAOpCGCRptT1m+bIpLTmbahZLZ0Qe4X99f8SgTQ7QISvUfpmn
tfOD1oA1AttXlOULEERYubzvDnUTXvstFomQx0XTA67IaV+mw9ODRtG1hPN/erdKX6sU6rH4tsEb
ba3Drr/I0HT3YVvD3SjWtGXjF12XLvTP6+LfMIIDTCAPiEd9KPG23D7skVu/4BvvmdLFI96OARhg
wQ86M+lTIn83KRJlbbfAeIevbRx/rUB7D+uvMdWxOzR0KZJhd6dEeTXVwBXZG4rnQ4uFM+mRSiD4
rxDCyOuIuOzR07tnOyCRio6sRipOZvwQUWttdsgMEs6IxLdWsaTXcs1HjCsxrdedovMCAwEAAaOB
njCBmzAOBgNVHQ8BAf8EBAMCBeAwHwYDVR0jBBgwFoAUAHRsSeXJUmFxTVY4q2HJ8uHl+w0wGwYD
VR0RBBQwEoEQVHVybmVyU0BpZWNhLmNvbTAyBgNVHR8EKzApMCegJaAjhiFodHRwOi8vd3d3Lmll
Y2EuY29tL2NybHMvaWVjYS5jcmwwFwYDVR0gBBAwDjAMBgorBgEEAYHXAAAAMA0GCSqGSIb3DQEB
CwUAA4ICAQAimDYm77ppTi4vK6qJSUhyvCDMGb8mngiEXEYKxsfdHPWoDO7+06j7dAZ8sDD9/FtE
kiUMyoNGSUmKHR+tGperVnNiM/Zk6WwCJv8dYZwhGXNQeEGzeys/UkFv7CFX7uDSn8GQeB8sOAZ1
N1hxV/TvT8qXvcRxP5+aWTAGAq3TKtCQxZjuU74L3st2hZiOhJlhjhqz0K5FIwWzXUK9uwhZe1th
GUpDbRustVgmKN2Xa0pzwqI1VUO0jnWt24A4u59xo6DJQXzQVMhCx0xhpemuT9BrsBDTX8eJdI1i
Wv9wp3ivSrfHjKXp8y8OGD+usiG40HCjj0W9C+dH0VfbgrB6QOI4vA9+kTg4mANth1cxyxwPYOSJ
v0zi1qR0eDIGI//2v2/s6TmGuNqbnRa26Ldv5gGqS7xj32Fiaby6UOXs4+aAIWGZEOH+BXjozcvE
eGBwjU/VRQYu6itR28PaNhNVji4D5ITaGxWWiycqK1EUaFraWHtk7W100ROX69xTeFVZP86D2ymi
/aohl5Vb1vlYHdqlbgqjDRl9dPbTxVCXEHf+jkexcuwlLTvr7F+5DIN6c/EbCpRqQx3edy193L48
OGyRDh1/Wmzpew0VWWAWOSXGl/P9VzXf3Z6GPt7flN/V9iEJAa3Mo+w+eIdzJkHBWR+yJcqQcCRM
MSyishMwLDGCAjgwggI0AgEBMC8wIjELMAkGA1UEBhMCVVMxEzARBgNVBAoTCklFQ0EsIEluYy4C
CQCdWMxKNutUeTAJBgUrDgMCGgUAoIHfMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTE0MDEyMzEzMDUyNVowIwYJKoZIhvcNAQkEMRYEFOzbB7bQFl0nzJLQCd/3hQqg
yVSfMD4GCSsGAQQBgjcQBDExMC8wIjELMAkGA1UEBhMCVVMxEzARBgNVBAoTCklFQ0EsIEluYy4C
CQCdWMxKNutUeTBABgsqhkiG9w0BCRACCzExoC8wIjELMAkGA1UEBhMCVVMxEzARBgNVBAoTCklF
Q0EsIEluYy4CCQCdWMxKNutUeTANBgkqhkiG9w0BAQEFAASCAQA1bCAjzZ9IukpGhERRxjq9ov76
esrRcsyWAVQ5Alj7NW80A4VnbDzgVe4HkAFkydFtAJDO4okzW2hPFph1IUytrFP3F4Xlhtus4Mye
4GgR9lxGz+DjkXWof1TKxxXvXlGqvyjPFoUAx95iQI99NcrIp72waGFmO2yYlr4Pl1bstTzxKl7u
lsMEfRTPi4WBBH3FdKDbwnabV9UhYEtHaAjvotDdMRfhSlLD0tDusvUXN67YE/nNaFPVf+jgTQbx
LqMZYmd7iMODn4bvxF21s2iF03vltPivNUALY24RHMr2YbMurcOPosxhLuY60mk17vKS0fVwUBhy
VYS9rA9kAxTZAAAAAAAA

--Apple-Mail=_183BD477-3F23-4506-8B3F-8034893C1791--

From jari.arkko@piuha.net  Thu Jan 23 09:03:07 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4912B1A0055; Thu, 23 Jan 2014 09:03:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ukYBOg3corta; Thu, 23 Jan 2014 09:03:05 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 17E061A0056; Thu, 23 Jan 2014 09:03:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E3D532CC5F; Thu, 23 Jan 2014 19:03:03 +0200 (EET)
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 gfhafgKeMOmZ; Thu, 23 Jan 2014 19:03:03 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 78D132CC48; Thu, 23 Jan 2014 19:03:02 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAJc3aaOPNxMOcejieKucB4e_DSpGYOPtiF8w6TDvG4fbYDOqxA@mail.gmail.com>
Date: Thu, 23 Jan 2014 18:03:01 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F200F0D2-AD27-4309-BF35-8EF08C806A54@piuha.net>
References: <CABkgnnXj07R25LQ64-=bha6iFpabgAt=xsRP0+5A20wnF8JUdQ@mail.gmail.com> <CAJc3aaPKeuPicy_X+MG-T-XyZ+YdONphhkp1Ow666jq9_ubzew@mail.gmail.com> <CABkgnnWWLHKV7NZX4dZJM-YpRg4doSPKLRMD43sC9t23Pbx-VQ@mail.gmail.com> <3C5B486D-ED82-4ABC-9CAE-B720729791D2@piuha.net> <CAJc3aaOPNxMOcejieKucB4e_DSpGYOPtiF8w6TDvG4fbYDOqxA@mail.gmail.com>
To: Victor Kuarsingh <victor@jvknet.com>
X-Mailer: Apple Mail (2.1510)
Cc: Benoit Claise <bclaise@cisco.com>, "gen-art@ietf.org Team" <gen-art@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>, draft-ietf-opsawg-lsn-deployment.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-opsawg-lsn-deployment-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:03:07 -0000

Thanks! I have cleared.

Jari

On Jan 22, 2014, at 11:18 PM, Victor Kuarsingh <victor@jvknet.com> =
wrote:

> Jari,
>=20
> I just responded to the gen-art list and Martin on his comments.
>=20
> I have made a number of changes that address his comments and have =
used much of his text.  ( I will be sending the Benoit and the rest of =
the IESG a full summary of changes and new version posting tonight).
>=20
> This includes the changes to section 6 as prescribed.
>=20
> regards,
>=20
> Victor K
>=20
>=20
> On Tue, Jan 21, 2014 at 6:06 PM, Jari Arkko <jari.arkko@piuha.net> =
wrote:
> Thanks for your detailed review, Martin!
>=20
> And thank you Victor for a very useful document!
>=20
> Much of the discussion in this thread is important but also partly =
editorial. I'll leave it to sort out between yourselves.
>=20
> However, I do think Section 6 last sentence:
>=20
>    Should a provide choose to use non-assigned IP address space within =
their translation realms, then considerations may apply.
>=20
> gives an odd impression. We already have shared address space (as the =
document notes elsewhere), so it is not clear to me what the above might =
entail, particularly when (a) regular address space assignments go =
through the RIR system not IANA (b) use of unassigned address space is =
probably not something that we want to recommend and (c) if we need to =
do something beyond the existing shared address space allocation, then =
that probably deserves its own document.
>=20
> I can see that Victor you've already agreed to make a change wrt =
Section 6. I just wanted to check that this is indeed the plan, so that =
we can move on to approving the document :-)
>=20
> Jari
>=20
>=20


From aland@deployingradius.com  Thu Jan 23 11:06:33 2014
Return-Path: <aland@deployingradius.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 733791A019E; Thu, 23 Jan 2014 11:06:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.4
X-Spam-Level: 
X-Spam-Status: No, score=0.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_LIST=2.3] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uj2ssDEyyYjr; Thu, 23 Jan 2014 11:06:28 -0800 (PST)
Received: from power.freeradius.org (power.freeradius.org [88.190.25.44]) by ietfa.amsl.com (Postfix) with ESMTP id 61FFD1A01E5; Thu, 23 Jan 2014 11:06:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id EBE4E224015C; Thu, 23 Jan 2014 20:05:48 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cztsKwlFyhsl; Thu, 23 Jan 2014 20:05:46 +0100 (CET)
Received: from Thor.local (unknown [70.50.217.206]) by power.freeradius.org (Postfix) with ESMTPSA id 469D7224013A; Thu, 23 Jan 2014 20:05:45 +0100 (CET)
Message-ID: <52E16808.3070308@deployingradius.com>
Date: Thu, 23 Jan 2014 14:05:44 -0500
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
References: <C3DF6E99-2B7E-4606-A8F6-5D76C338B265@nostrum.com>
In-Reply-To: <C3DF6E99-2B7E-4606-A8F6-5D76C338B265@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: radext@ietf.org, draft-ietf-radext-dtls.all@tools.ietf.org, "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-Art Early Review of draft-ietf-radext-dtls-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 19:06:34 -0000

Ben Campbell wrote:
> *** Major issues:
> 
> -- General:
> 
> The draft needs an overhaul of it's use of normative language. There appears to be redundant (and possibly contradictory) language for the same requirements sprinkled throughout. There are also cases of normative language being used for internal implementation guidance, which is not appropriate as described by RFC 2119. (See the minor issues section for details--most of the instances would not qualify as major issues by themselves, but I think they constitute a major issue in the aggregate.)
> 
> -- section 3, 2nd paragraph:  "... long-term use of RADIUS/UDP is NOT RECOMMENDED." 
> 
> While I agree with the sentiment, that's not an appropriate assertion for an experimental RFC. It would either need to go into an standards-track update to the RADIUS spec, or a BCP.

  OK.

> (Also applies to the reiteration in 10.1)

  I'm less sure of that.  10.1 doesn't re-iterate the point above.  It
makes a security recommendation.  i.e. allowing secure and insecure
traffic from the same client is bad.

  This imposes no change on existing RADIUS/UDP clients, as they will
only be sending RADIUS/UDP.  It does impose security requirements on
RADIUS/DTLS clients and servers, which is the intent of the section.

> *** Minor issues:
> 
> -- General:  It might be worth some text on why this is experimental rather than informational. Is there any plan to evaluate the implementation results? Is there an expectation that a future RADIUS/DTLS spec could become standards-track? Is there any plan to evaluate the outcome of this document?

  It's probably easiest to reference Section 1.3 of RFC 6614.  The
issues are the same.

> -- Section 1, 2nd paragraph:
> 
> Isn't this true for almost any use of IPSec? Is there some specific reason this is worse for RADIUS than for other protocols?

  It's true for most protocols.

> -- Section 1, 4th paragraph:
> 
> The second sentence mentions that firewall rules do not need to be changed. The following sentence recommends a change to firewall rules.

  That's left over from earlier drafts.  I'll fix it.

> The firewall rule recommendations in the 3rd sentence seems odd, since it seems like any protocol over DTLS would pass. Also, does this imply a recommendation that firewalls with DPI be used in the first place, since the absence of such a firewall has the same effect as having one that doesn't enforce the protocol? (Is there a reason a protocol spec should recommend firewall rules in the first place, other than to mention places where certain firewall rules might prevent interfere with operation?)

  I'll clarify it, and move it to the Security Considerations section.

> -- section 2.1, 5th paragraph (3rd paragraph after bullet list) :  "Implementations MUST support encapsulated RADIUS packets of 4096 in length..."
> 
> Please be more precise than "MUST support". Specifically, does "MUST support" indicate you must support both sending and receiving of that size? (since 4096 would generally exceed PMTU even for RADIUS/UDP)

  Yes.  RADIUS/UDP has the same 4096 octet limit for sending and
receiving packets.

> -- 2.2 and children:
> 
> I find this section confusing as to where to find the authoritative text. Some, but not all, of the material from 6614 is repeated as normative text in later sections.  The description of this draft as applying 'semantic "patches"' to 6614 seems to imply you mean the 6114 text, with these patches applied, to be normative, which creates some potential conflicts. If, on the other hand, 2.2 (.x) is intended more as a informative description of the differences, please say so.

  What conflicts occur?  The intent is show this specification as a
revision / patch from 6614.

> -- 3, 1st paragraph:
> 
> Can you elaborate on the resulting "timeouts, lost traffic, and network instabilities"?

  RADIUS/UDP has no provisions for protocol negotiation.  So simply
disabling UDP makes it look like the server is gone, rather than
transitioned to DTLS.

> -- 3.1: 
> 
> The section describes UDP/2083 as the "default port". But later sections describe port related behavior in a way that makes it it look like the impementations must always use 2083, which makes it more than just a default. Is the administrator allowed to choose some other port for any reason?

  Yes.  As with most protocols, implementations allow the administrator
to use non0-standard ports.

> If so, it might make more sense to refer to the port by role rather than number when discussing port related behavior. (I note that 6614 only mentions the port number in the initial assignment, the IANA considerations, and the appendix.)

  Maybe.  That makes the text a bit more awkward.  "UDP/2083" would get
replaced by "that or any other port you happen to use".

> -- 3.2, last paragraph:
> 
> Can you elaborate on the bid down attack? Given that the use of dtls is configured, rather than negotiated, how would an attacker bid it down?

  When secure and insecure packets are allowed from the same client, a
malicious or broken client can choose the insecure one.  That's bad,
when the intent is to use DTLS.

> -- 4, 2nd paragraph:
> 
> Seems like an (or maybe even the) important point would be that a client should not fall back to cleartext if a server appears to not support it.

  That's reasonable.

> -4, 3rd paragraph:
> 
> Is the recommendation to use a local proxy for all clients, or just those implemented as multiple processes?

  Only ones with multiple processes.

> -- 5.1.1, third paragraph: "In those cases, the implementation MAY delete the underlying session"
> 
> Can you elaborate on why that's a MAY and not a SHOULD or MUST?

  There was a long discussion about this on the RADEXT list.  In short,
the session MUST be closed when there are security issues, or when the
tunneled data isn't RADIUS.

  When security is OK and the tunneled data is RADIUS, it's OK to
silently drop the unexpected RADIUS packets.  Doing so doesn't cause any
problems.

> -- 5.1.1, 4th paragraph:
> 
> This paragraph rephrases 2119 normative language with more normative language. That creates confusion about which text is authoritative. I suggest either keeping the second paragraph and deleting the first, or make the second non-normative.

  I'm not sure what you mean here.  The two paragraphs discuss different
things, so deleting one isn't possible.

> -- 5.1.1, 6th paragraph: "The timestamp SHOULD be updated ..."
> 
> Why not MUST?

  The granularity could be 1 second, with packets being received 1000's
of times per second.

> -- 5.1.1, 7th paragraph:
> 
> Is the "idle time" configurable setting on a per peer or global basis?

  Possibly both.  That depends on the implementation.  I don't see it as
being useful to either restrict the implementations, or make
recommendations here.

  The text here talks about idle timeouts per *session*.  How the
implementation takes that from a configuration setting to a session is
up to the implementation.

> -- 5.1.1, 8th paragraph:
> 
> What does it mean to "track" sessions?  Also, it seems like the "SHOULD stop creating" guidance contradicts later guidance that least recently used sessions might get dropped instead?

  Perhaps "open sessions" is better than "tracked sessions".

  The idea is that it will either drop the new one, or drop an old one.
 Either way, the "maximum sessions" value should not be exceeded.  I'll
update the text.

> -- 5.1.1, 10th paragraph:  
> 
> Should the second sentence contain a normative MUST?

  Yes.

> Also, the 2nd and 3rd sentences taken together seem say "the server must keep the session open until it decides not to" 

  It closes the session when the client asks for it to be closed, or
when the idle timeouts are reached.

  But really, the server is allowed to close sessions any time it wants.
 I don't think we want to restrict that power.

> How would an unauthenticated client close an active DTLS session?

  If a 4-tuple is re-used, AND the server closes an old session to
handle the "new" one.  I'll clarify the text.

> -- 5.2, 1st paragraph:
> 
> The normative requirement for a client to use heartbeats _or_ the application level watchdog algorithm seems to contradict the normative guidance that a server SHOULD use both.

  I'll clarify the text.

> -- 5.2, 3rd paragraph, 1st sentence:
> 
> I would hesitate to phrase this that a client may violate the previous normative SHOULDs. It would be better to phrase this as describing th econsequences should the client ignore the SHOULD.

  I'll clarify the text.

> -- 5.2, 2nd to last paragraph:
> 
> Does this have actual interop or security issues beyond saying, "it's harder to implement and you might screw it up"? If not, it seems counter to the 2119 guidance on when normative language is appropriate. It would be more properly non-normative  implementation guidance.

  OK.

> -- 6, 1st paragraph:
> 
> You mention that these are implementation guidelines, and not part of the protocol. But the section contains 2119 style normative requirements. in general, that's not appropriate unless non-compliance impact interoperability or create some other Bad Thing, such as insecure behavior, excessive bandwidth usage, congestion, etc. Implementation guidance for behavior that is not externally observable should use non-normative.

  OK.

> -- 6, 2nd and 3rd paragraph:
> 
> The RECOMMENDation to allow administrative entry of keys and to derive keys from a PRNG seem contradictory.

  The idea is that admins shouldn't be entering "0xabababab" as a key.
Instead, they get secure keys from a secure location.  People are
notoriously bad at creating randomness.

> -- 6.1, 1st paragraph:
> 
> Does the guidance to use connected sockets remove previous normative requirements about session management and tracking? If not, please indicate the difference.

  No.  The previous text about client session management doesn't talk
about multiple sessions.  It just talks about how to manage *one* session.

  This text is intended to suggest that managing multiple DTLS sessions
on one socket isn't necessary.

> -- 6.1, 3rd paragraph:
> 
> This seems to assume that all radius clients are implementd as multiple processes. Is that the intent?

  No.

> Also,  it's better not to use normative requirements for internal implementation choices. Describe the externally visible behavior normatively. You can give implementation advice in the form of example strategies to fulfill the black-box normative requirements.

  I'll copy the text from earlier in the document which discusses this.

> -- 9
> 
> Why not choose a new port? Is there absolute certainty this won't conflict with the previous usage? I do note that 6414 made the same choice, so I guess consistency with radius/TLS has some value. But that draft talks about compatibility between radsec and radius/tls, which is not mentioned here.

  No one is using UDP/2083 for anything.  Re-using it is OK.

> -- 10, last paragraph:
> 
> You describe the use of null crypto as an implementation or configuration error. Was it intended to be forbidden from intentional use? Is there a need to remove the fixed secret requirement for null crypto, or to disallow null crypto entirely?

  null crypto should be forbidden.

> -- 10.1, 3rd paragraph:
> 
> It would be helpful to have guidance on how to match a certificate to a client or server identity,

  I'll add a note to see RFC 6614 Section 2.5.

> how to configure trust for a self-signed cert, etc.

  I'll avoid that, to be honest.

> -- 10.1, 4th paragraph: 
> 
> -- 10.1, last paragraph:
> 
> Why does the historic use of shared secrets matter, since this document requires all implementations to use a fixed value? Or do you mean the use of poor secrets as PSKs?

  I mean the use of poor secrets as PSKs.

> -- 10.2, 2nd paragraph:
> 
> This is redundant with previous normative requirements. (Also contradictory, since the previous text said "SHOULD", and contradictory guidance on what to do when the limit is exceeded.)

  I've fixed the text to be consistent.

> -- 10.3, 4th paragraph:
> 
> Does this need to be as strong as SHOULD? Is this likely to conflict with dynamic discovery, should it ever exist?

  RADIUS is a critical piece of infrastructure.  Exposing your RADIUS
server to the entire IPv4 range is a bad idea.

  The recommendation is a SHOULD so that it does not conflict with
dynamic discovery.

> -- 10.3, 5th and 6th paragraphs:
> 
> Paragraph 5 says credentials should be statically configured. To me, "credentials" means "the certificate" in this case. That seems to disallow things like statically configuring a name that must match a certificate (perhaps signed by a CA.)

  Credentials for the client should be statically configured.  It could
be a PSK, or a certificate.

  I'm not sure what "name" would match a certificate.  The document
doesn't refer to names, and doesn't use names for anything.

> Paragraph 6 seems to entirely contradict paragraph 5 by recommending private CAs, and accepting any peer that presents a cert signed by that CA. That's pretty much the opposite of statically configured credentials. (Paragraph 8 also seems to contradict the static configuration part.)

  Both client and server still need to be configured with the private
CA.  The alternative is to allow anyone to connect with any credentials,
which seems odd.

> The last sentence refers to "the invalid server". What invalid server is that? None have been mentioned so far.

  The previous sentence talks about a "valid" server.  I'll clarify.

> -- 10.4:
> 
> The guidance in the last paragraph does not make sense. The section seems to say that NATs will break radius/dtls, so you should use dtls when behind a NAT.

  RADIUS/UDP clients should not be behind a NAT.  I'll clarify.

> -- 10.6, last paragraph:
> 
> Can you elaborate on this? Why would an unauthorized 3rd party be able to get packets past the DTLS layer? OTOH, If an authorized client is sending invalid radius packets, wouldn't  you want to terminate the session?

  That was a *long* discussion on the RADEXT list.

  A server may be at protocol rev X, and a client may be at protocol rev
X+1.  If the client sends packets allowed by X+1, the server should
ignore them, as it does today with RADIUS/UDP.  Closing the connection
is not necessary.

> -- 10.7
> 
> Redundant normative requirements (This is at least the third time the separate process issue and local proxy guidance has been described.)

  It's a security considerations section, and needs to mention this.  It
refers to Section 6.1, and adds new text explaining the security
benefits of the approach.

> 
> 
> *** Nits/editorial comments:
> 
> -- IDNits reports some issues; please check.

  They're fine.

> -- Abstract:
> Please avoid citations in the abstract. Please consider removing the "scare quotes".

  OK.

> -- Section 1, 5th paragraph:
> 
> it seems like the RADIUS problems that this does not solve are in generally solved by RADIUS/TLS. If so, it would probably be worth a mention.

  OK.

> -- section 2.1, 4th paragraph from end: 
> 
> Seems like there are other changes as well. For example, you don't include "Use DTLS" as one of the changes in RADIUS/DTLS from RADIUS/USP.

  OK.

> -- 2.2 and children:
> 
> In my strictly personal opinion, the approach of patching 6614 transfers a lot of effort from the author to the reader. A reader will basically need to keep both docs open side by side to understand this.  I understand the desire to avoid duplicating normative text, but I think that the balance here has swung too far away from readability.  (OTOH, see my related comment under "minor issues).

  I think re-doing the document is a non-starter at this point.

  Having done this myself, the bulk of the implementation work in doing
DTLS is the UDP layer.  Most everything else can be re-used directly
from RADIUS/TLS.

> -- 2.2.1, paragraph 5:
> 
> should TLS parameters be DTLS parameters?

  Yes.

> -- 2.2.2:
> 
> Why a separate section to say sections 4 and 6 also apply? (The re-iteration seems unneeded.)

  OK.

> -- 3.1, last sentence:
> 
> Really, 2.2.1 doesn't describe that. 6114 describes that. Better to cite the source than to cite a citation to the source, especially when that citation doesn't mention the issues at all.

  OK.

> -- 4, 3rd paragraph:
> 
> Do you really mean multiple independent _implementations_? Or multiple independent instances or processes, perhaps running the same implementation?

  All of that.

> -- section 5 and children:
> 
> In consistent use of "connection" vs "session".

  I'll fix that.

> -- 5.1.1, 2nd paragraph:
> 
> What is an "entry" session?

  The 4-tuple is logically a table tracking (4-tuple) -> (session data).
 Each one is an entry.

  I'll try to clarify the text.

> -- 6.1, 2nd paragraph:
> 
> Source port? Source address? Both?

  Both.

> -- 7:
> 
> Only the first paragraph seems to be about implementation experience.

  OK.

> -- 10, 2nd paragraph: "All of the security considerations for RADIUS apply to the RADIUS portion of the specification."
> 
> The next paragraph seems to contradict this.

  OK.

> -- 10.3, 2nd paragraph: "... a client has a fixed IP address for a server ..."
> 
> This is ambiguous. Do you mean the server knows the client address, or the client knows the server address? It sounds like the latter, but later text makes me wonder if you meant the former.

  The following sentence addresses this.  The client has a fixed IP for
the server, and the server has a fixed IP for the client.

> -- 10.3, 7th paragraph: "... pre-configured with a list of known public CAs."
> 
> By pre-configured, you mean by the manufacturer or vendor, right?

  Yes.

> -- 10.5, 2nd paragraph:
> 
> Does this contradict guidance about using a private CA to identify multiple peers?

  No.

> I don't think you intend it that way; I assume you mean the cert presented by a client must be unique, but as written it's easy to assume that you mean the server has to have unique certs configured for each client, which it would not if it were to allow any arbitrary client that has a cert signed by a private CA.

  That's what it says, so far as I can tell.

From mahoney@nostrum.com  Thu Jan 23 14:33:09 2014
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B231A035C for <gen-art@ietfa.amsl.com>; Thu, 23 Jan 2014 14:33:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLQ5_DMGfNgK for <gen-art@ietfa.amsl.com>; Thu, 23 Jan 2014 14:33:08 -0800 (PST)
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 1A5A41A023D for <gen-art@ietf.org>; Thu, 23 Jan 2014 14:33:08 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0NMX1ds075085 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 23 Jan 2014 16:33:06 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52E1989D.4020804@nostrum.com>
Date: Thu, 23 Jan 2014 16:33:01 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-01-23
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 22:33:09 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Ben Campbell      2014-02-04   draft-ietf-radext-ieee802ext-10

Joel Halpern      2014-02-04   draft-ietf-manet-olsrv2-rmpr-optimization-00

Kathleen Moriarty 2014-02-18   draft-yourtchenko-cisco-ies-09

Martin Thomson    2014-02-04   draft-ietf-alto-protocol-25

Meral Shirazipour 2014-02-04   draft-ietf-xrblock-rtcp-xr-synchronization-07

Roni Even         2014-02-04   draft-ietf-pcp-description-option-02

Robert Sparks     2014-02-04   draft-ietf-pcp-nat64-prefix64-04

Suresh Krishnan   2014-02-04   draft-ietf-avtext-rtp-duplication-04

Vijay Gurbani     2014-02-04   draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01


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 jmh@joelhalpern.com  Thu Jan 23 19:14:20 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F1881A0141 for <gen-art@ietfa.amsl.com>; Thu, 23 Jan 2014 19:14:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7A__4MnvkArt for <gen-art@ietfa.amsl.com>; Thu, 23 Jan 2014 19:14:18 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC8D1A012A for <gen-art@ietf.org>; Thu, 23 Jan 2014 19:14:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id CE9601C0B4F; Thu, 23 Jan 2014 19:14:17 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (24-104-115-2-ip-static.hfc.comcastbusiness.net [24.104.115.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id A357F1C05A5; Thu, 23 Jan 2014 19:14:17 -0800 (PST)
Message-ID: <52E1DA89.40707@joelhalpern.com>
Date: Thu, 23 Jan 2014 22:14:17 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org
References: <52E1989D.4020804@nostrum.com>
In-Reply-To: <52E1989D.4020804@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art]  review: draft-ietf-manet-olsrv2-rmpr-optimization-00
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 03:14:20 -0000

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

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

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

Document: draft-ietf-manet-olsrv2-rmpr-optimization-00
     Routing MPR Optimization for the Optimized Link State
              Routing Protocol version 2 (OLSRv2)
Reviewer: Joel M. Halpern
Review Date: 21-January-2014
IETF LC End Date: 4-February-2014
IESG Telechat date: N/A

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

Major issues: N/A

Minor issues: N/A

Nits/editorial comments: N/A

From vkg@bell-labs.com  Fri Jan 24 07:01:43 2014
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D2C71A04B1 for <gen-art@ietfa.amsl.com>; Fri, 24 Jan 2014 07:01:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05sxmC418G_K for <gen-art@ietfa.amsl.com>; Fri, 24 Jan 2014 07:01:42 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 0EEBF1A04B2 for <gen-art@ietf.org>; Fri, 24 Jan 2014 07:01:37 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s0OF1alM022312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 24 Jan 2014 09:01:36 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s0OF1Zhi022647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Jan 2014 09:01:36 -0600
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 s0OF1ZqU020858; Fri, 24 Jan 2014 09:01:35 -0600 (CST)
Message-ID: <52E28081.4000102@bell-labs.com>
Date: Fri, 24 Jan 2014 09:02:25 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: xrblock-chairs@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 15:01:43 -0000

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

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

Document: draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01
Reviewer: Vijay K. Gurbani
Review Date: Jan-24-2014
IETF LC End Date: Feb-04-2014
IESG Telechat date: Unknown

Major: 0
Minor: 0
Nits: 1

This document is ready as a Proposed Standard.

Nits:
- S6, "In some situations, returning very detailed error information
  (e.g., over-range measurement or measurement unavailable) using this
  report block can provide an attacker with insight into the security
  processing." I am not sure what you mean by "security processing"
  here --- maybe you meant the byte discard block leaks privacy of the
  user?

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 peter@akayla.com  Fri Jan 24 07:22:50 2014
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23F611A03FF for <gen-art@ietfa.amsl.com>; Fri, 24 Jan 2014 07:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.879
X-Spam-Level: 
X-Spam-Status: No, score=-0.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AwbLHzB5y5GI for <gen-art@ietfa.amsl.com>; Fri, 24 Jan 2014 07:22:49 -0800 (PST)
Received: from p3plsmtpa08-07.prod.phx3.secureserver.net (p3plsmtpa08-07.prod.phx3.secureserver.net [173.201.193.108]) by ietfa.amsl.com (Postfix) with ESMTP id A392A1A03EF for <gen-art@ietf.org>; Fri, 24 Jan 2014 07:22:48 -0800 (PST)
Received: from [172.20.7.225] ([69.63.220.2]) by p3plsmtpa08-07.prod.phx3.secureserver.net with  id HrNl1n00903iA9901rNmty; Fri, 24 Jan 2014 08:22:47 -0700
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Fri, 24 Jan 2014 07:22:44 -0800
From: Peter Yee <peter@akayla.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>
Message-ID: <CF07C501.8F7D%peter@akayla.com>
Thread-Topic: Gen-ART LC review of draft-ietf-netmod-ip-cfg-12
References: <CF075E77.8F72%peter@akayla.com>
In-Reply-To: <CF075E77.8F72%peter@akayla.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: [Gen-art] Gen-ART LC review of draft-ietf-netmod-ip-cfg-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 15:22:50 -0000

(Resending for the record.)

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

Document: draft-ietf-netmod-ip-cfg-12
Reviewer: Peter Yee
Review Date: Jan-23-2014
IETF LC End Date: Jan-23-2014
IESG Telechat date: TBD

Summary: This draft is ready for publication as a Standards Track
RFC. [Ready]

The abstract says it pretty well: This document defines a YANG data model
for management of IP implementations.

Major issues: None

Minor issues: None

Nits: None

All of the issues from my -09 review have been addressed in the
-12 version.

		-Peter Yee



From jouni.nospam@gmail.com  Fri Jan 24 07:48:21 2014
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 965D81A0444 for <gen-art@ietfa.amsl.com>; Fri, 24 Jan 2014 07:48:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.3
X-Spam-Level: 
X-Spam-Status: No, score=0.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MANGLED_LIST=2.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHoghVhNYEsq for <gen-art@ietfa.amsl.com>; Fri, 24 Jan 2014 07:48:18 -0800 (PST)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 29BE01A0021 for <gen-art@ietf.org>; Fri, 24 Jan 2014 07:48:18 -0800 (PST)
Received: by mail-pd0-f172.google.com with SMTP id p10so3263574pdj.31 for <gen-art@ietf.org>; Fri, 24 Jan 2014 07:48:17 -0800 (PST)
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=HKQiHeewlphLKEdAd0NwWJ8JiY9T+9CnwdL8z6f74A0=; b=lLPoI6xKXfz6Cz9AS7JxnO8QEF3HXHwWCcQkmyfYZFVsuRfc3M9CtGaeWdqqiK3/lr uwJsb/XxdspzpjJmiGnOeMFaDgotuSq8QptJxwHIRq3lw3cIQmH4AvhXMNhwE3QSZ9Gb Sxjcjql8ON+j4Ckeymcbz0f+vrGjSCtp5kx4dX5nchWBJNPfTHuGvB43QL5o/JA8NaxL E9hhngiOBLHcnU6OGk0lUygm2EfdWmWQAwnvnR3KSj+oqok2NfpOM3APD+LJdojW8BYi ULrX/n4yJZTZIjUtZ4PS8uxKYaSiq1g7/Ysi6GnJHNQgmeeZS51+KuFrML5CmdZtZEqj wZ/A==
X-Received: by 10.69.26.228 with SMTP id jb4mr14925565pbd.83.1390578497053; Fri, 24 Jan 2014 07:48:17 -0800 (PST)
Received: from dhcp-18-187.meeting.verilan.com ([205.201.168.123]) by mx.google.com with ESMTPSA id sx8sm10220007pab.5.2014.01.24.07.48.14 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Jan 2014 07:48:15 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <52E16808.3070308@deployingradius.com>
Date: Fri, 24 Jan 2014 17:47:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <34C50C19-4CFF-403B-A93E-F652D485FE4B@gmail.com>
References: <C3DF6E99-2B7E-4606-A8F6-5D76C338B265@nostrum.com> <52E16808.3070308@deployingradius.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, Mauricio Sanchez <mauricio.sanchez@hp.com>, Alan DeKok <aland@deployingradius.com>
Subject: Re: [Gen-art] [radext] Gen-Art Early Review of draft-ietf-radext-dtls-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 15:48:21 -0000

Ben,

Alan just posted -08 revision. Could you check it whether all your =
concerns
have been addressed and you are OK with the revision.

- JOuni (doc shepherd)


On Jan 23, 2014, at 9:05 PM, Alan DeKok <aland@deployingradius.com> =
wrote:

> Ben Campbell wrote:
>> *** Major issues:
>>=20
>> -- General:
>>=20
>> The draft needs an overhaul of it's use of normative language. There =
appears to be redundant (and possibly contradictory) language for the =
same requirements sprinkled throughout. There are also cases of =
normative language being used for internal implementation guidance, =
which is not appropriate as described by RFC 2119. (See the minor issues =
section for details--most of the instances would not qualify as major =
issues by themselves, but I think they constitute a major issue in the =
aggregate.)
>>=20
>> -- section 3, 2nd paragraph:  "... long-term use of RADIUS/UDP is NOT =
RECOMMENDED."=20
>>=20
>> While I agree with the sentiment, that's not an appropriate assertion =
for an experimental RFC. It would either need to go into an =
standards-track update to the RADIUS spec, or a BCP.
>=20
>  OK.
>=20
>> (Also applies to the reiteration in 10.1)
>=20
>  I'm less sure of that.  10.1 doesn't re-iterate the point above.  It
> makes a security recommendation.  i.e. allowing secure and insecure
> traffic from the same client is bad.
>=20
>  This imposes no change on existing RADIUS/UDP clients, as they will
> only be sending RADIUS/UDP.  It does impose security requirements on
> RADIUS/DTLS clients and servers, which is the intent of the section.
>=20
>> *** Minor issues:
>>=20
>> -- General:  It might be worth some text on why this is experimental =
rather than informational. Is there any plan to evaluate the =
implementation results? Is there an expectation that a future =
RADIUS/DTLS spec could become standards-track? Is there any plan to =
evaluate the outcome of this document?
>=20
>  It's probably easiest to reference Section 1.3 of RFC 6614.  The
> issues are the same.
>=20
>> -- Section 1, 2nd paragraph:
>>=20
>> Isn't this true for almost any use of IPSec? Is there some specific =
reason this is worse for RADIUS than for other protocols?
>=20
>  It's true for most protocols.
>=20
>> -- Section 1, 4th paragraph:
>>=20
>> The second sentence mentions that firewall rules do not need to be =
changed. The following sentence recommends a change to firewall rules.
>=20
>  That's left over from earlier drafts.  I'll fix it.
>=20
>> The firewall rule recommendations in the 3rd sentence seems odd, =
since it seems like any protocol over DTLS would pass. Also, does this =
imply a recommendation that firewalls with DPI be used in the first =
place, since the absence of such a firewall has the same effect as =
having one that doesn't enforce the protocol? (Is there a reason a =
protocol spec should recommend firewall rules in the first place, other =
than to mention places where certain firewall rules might prevent =
interfere with operation?)
>=20
>  I'll clarify it, and move it to the Security Considerations section.
>=20
>> -- section 2.1, 5th paragraph (3rd paragraph after bullet list) :  =
"Implementations MUST support encapsulated RADIUS packets of 4096 in =
length..."
>>=20
>> Please be more precise than "MUST support". Specifically, does "MUST =
support" indicate you must support both sending and receiving of that =
size? (since 4096 would generally exceed PMTU even for RADIUS/UDP)
>=20
>  Yes.  RADIUS/UDP has the same 4096 octet limit for sending and
> receiving packets.
>=20
>> -- 2.2 and children:
>>=20
>> I find this section confusing as to where to find the authoritative =
text. Some, but not all, of the material from 6614 is repeated as =
normative text in later sections.  The description of this draft as =
applying 'semantic "patches"' to 6614 seems to imply you mean the 6114 =
text, with these patches applied, to be normative, which creates some =
potential conflicts. If, on the other hand, 2.2 (.x) is intended more as =
a informative description of the differences, please say so.
>=20
>  What conflicts occur?  The intent is show this specification as a
> revision / patch from 6614.
>=20
>> -- 3, 1st paragraph:
>>=20
>> Can you elaborate on the resulting "timeouts, lost traffic, and =
network instabilities"?
>=20
>  RADIUS/UDP has no provisions for protocol negotiation.  So simply
> disabling UDP makes it look like the server is gone, rather than
> transitioned to DTLS.
>=20
>> -- 3.1:=20
>>=20
>> The section describes UDP/2083 as the "default port". But later =
sections describe port related behavior in a way that makes it it look =
like the impementations must always use 2083, which makes it more than =
just a default. Is the administrator allowed to choose some other port =
for any reason?
>=20
>  Yes.  As with most protocols, implementations allow the administrator
> to use non0-standard ports.
>=20
>> If so, it might make more sense to refer to the port by role rather =
than number when discussing port related behavior. (I note that 6614 =
only mentions the port number in the initial assignment, the IANA =
considerations, and the appendix.)
>=20
>  Maybe.  That makes the text a bit more awkward.  "UDP/2083" would get
> replaced by "that or any other port you happen to use".
>=20
>> -- 3.2, last paragraph:
>>=20
>> Can you elaborate on the bid down attack? Given that the use of dtls =
is configured, rather than negotiated, how would an attacker bid it =
down?
>=20
>  When secure and insecure packets are allowed from the same client, a
> malicious or broken client can choose the insecure one.  That's bad,
> when the intent is to use DTLS.
>=20
>> -- 4, 2nd paragraph:
>>=20
>> Seems like an (or maybe even the) important point would be that a =
client should not fall back to cleartext if a server appears to not =
support it.
>=20
>  That's reasonable.
>=20
>> -4, 3rd paragraph:
>>=20
>> Is the recommendation to use a local proxy for all clients, or just =
those implemented as multiple processes?
>=20
>  Only ones with multiple processes.
>=20
>> -- 5.1.1, third paragraph: "In those cases, the implementation MAY =
delete the underlying session"
>>=20
>> Can you elaborate on why that's a MAY and not a SHOULD or MUST?
>=20
>  There was a long discussion about this on the RADEXT list.  In short,
> the session MUST be closed when there are security issues, or when the
> tunneled data isn't RADIUS.
>=20
>  When security is OK and the tunneled data is RADIUS, it's OK to
> silently drop the unexpected RADIUS packets.  Doing so doesn't cause =
any
> problems.
>=20
>> -- 5.1.1, 4th paragraph:
>>=20
>> This paragraph rephrases 2119 normative language with more normative =
language. That creates confusion about which text is authoritative. I =
suggest either keeping the second paragraph and deleting the first, or =
make the second non-normative.
>=20
>  I'm not sure what you mean here.  The two paragraphs discuss =
different
> things, so deleting one isn't possible.
>=20
>> -- 5.1.1, 6th paragraph: "The timestamp SHOULD be updated ..."
>>=20
>> Why not MUST?
>=20
>  The granularity could be 1 second, with packets being received 1000's
> of times per second.
>=20
>> -- 5.1.1, 7th paragraph:
>>=20
>> Is the "idle time" configurable setting on a per peer or global =
basis?
>=20
>  Possibly both.  That depends on the implementation.  I don't see it =
as
> being useful to either restrict the implementations, or make
> recommendations here.
>=20
>  The text here talks about idle timeouts per *session*.  How the
> implementation takes that from a configuration setting to a session is
> up to the implementation.
>=20
>> -- 5.1.1, 8th paragraph:
>>=20
>> What does it mean to "track" sessions?  Also, it seems like the =
"SHOULD stop creating" guidance contradicts later guidance that least =
recently used sessions might get dropped instead?
>=20
>  Perhaps "open sessions" is better than "tracked sessions".
>=20
>  The idea is that it will either drop the new one, or drop an old one.
> Either way, the "maximum sessions" value should not be exceeded.  I'll
> update the text.
>=20
>> -- 5.1.1, 10th paragraph: =20
>>=20
>> Should the second sentence contain a normative MUST?
>=20
>  Yes.
>=20
>> Also, the 2nd and 3rd sentences taken together seem say "the server =
must keep the session open until it decides not to"=20
>=20
>  It closes the session when the client asks for it to be closed, or
> when the idle timeouts are reached.
>=20
>  But really, the server is allowed to close sessions any time it =
wants.
> I don't think we want to restrict that power.
>=20
>> How would an unauthenticated client close an active DTLS session?
>=20
>  If a 4-tuple is re-used, AND the server closes an old session to
> handle the "new" one.  I'll clarify the text.
>=20
>> -- 5.2, 1st paragraph:
>>=20
>> The normative requirement for a client to use heartbeats _or_ the =
application level watchdog algorithm seems to contradict the normative =
guidance that a server SHOULD use both.
>=20
>  I'll clarify the text.
>=20
>> -- 5.2, 3rd paragraph, 1st sentence:
>>=20
>> I would hesitate to phrase this that a client may violate the =
previous normative SHOULDs. It would be better to phrase this as =
describing th econsequences should the client ignore the SHOULD.
>=20
>  I'll clarify the text.
>=20
>> -- 5.2, 2nd to last paragraph:
>>=20
>> Does this have actual interop or security issues beyond saying, "it's =
harder to implement and you might screw it up"? If not, it seems counter =
to the 2119 guidance on when normative language is appropriate. It would =
be more properly non-normative  implementation guidance.
>=20
>  OK.
>=20
>> -- 6, 1st paragraph:
>>=20
>> You mention that these are implementation guidelines, and not part of =
the protocol. But the section contains 2119 style normative =
requirements. in general, that's not appropriate unless non-compliance =
impact interoperability or create some other Bad Thing, such as insecure =
behavior, excessive bandwidth usage, congestion, etc. Implementation =
guidance for behavior that is not externally observable should use =
non-normative.
>=20
>  OK.
>=20
>> -- 6, 2nd and 3rd paragraph:
>>=20
>> The RECOMMENDation to allow administrative entry of keys and to =
derive keys from a PRNG seem contradictory.
>=20
>  The idea is that admins shouldn't be entering "0xabababab" as a key.
> Instead, they get secure keys from a secure location.  People are
> notoriously bad at creating randomness.
>=20
>> -- 6.1, 1st paragraph:
>>=20
>> Does the guidance to use connected sockets remove previous normative =
requirements about session management and tracking? If not, please =
indicate the difference.
>=20
>  No.  The previous text about client session management doesn't talk
> about multiple sessions.  It just talks about how to manage *one* =
session.
>=20
>  This text is intended to suggest that managing multiple DTLS sessions
> on one socket isn't necessary.
>=20
>> -- 6.1, 3rd paragraph:
>>=20
>> This seems to assume that all radius clients are implementd as =
multiple processes. Is that the intent?
>=20
>  No.
>=20
>> Also,  it's better not to use normative requirements for internal =
implementation choices. Describe the externally visible behavior =
normatively. You can give implementation advice in the form of example =
strategies to fulfill the black-box normative requirements.
>=20
>  I'll copy the text from earlier in the document which discusses this.
>=20
>> -- 9
>>=20
>> Why not choose a new port? Is there absolute certainty this won't =
conflict with the previous usage? I do note that 6414 made the same =
choice, so I guess consistency with radius/TLS has some value. But that =
draft talks about compatibility between radsec and radius/tls, which is =
not mentioned here.
>=20
>  No one is using UDP/2083 for anything.  Re-using it is OK.
>=20
>> -- 10, last paragraph:
>>=20
>> You describe the use of null crypto as an implementation or =
configuration error. Was it intended to be forbidden from intentional =
use? Is there a need to remove the fixed secret requirement for null =
crypto, or to disallow null crypto entirely?
>=20
>  null crypto should be forbidden.
>=20
>> -- 10.1, 3rd paragraph:
>>=20
>> It would be helpful to have guidance on how to match a certificate to =
a client or server identity,
>=20
>  I'll add a note to see RFC 6614 Section 2.5.
>=20
>> how to configure trust for a self-signed cert, etc.
>=20
>  I'll avoid that, to be honest.
>=20
>> -- 10.1, 4th paragraph:=20
>>=20
>> -- 10.1, last paragraph:
>>=20
>> Why does the historic use of shared secrets matter, since this =
document requires all implementations to use a fixed value? Or do you =
mean the use of poor secrets as PSKs?
>=20
>  I mean the use of poor secrets as PSKs.
>=20
>> -- 10.2, 2nd paragraph:
>>=20
>> This is redundant with previous normative requirements. (Also =
contradictory, since the previous text said "SHOULD", and contradictory =
guidance on what to do when the limit is exceeded.)
>=20
>  I've fixed the text to be consistent.
>=20
>> -- 10.3, 4th paragraph:
>>=20
>> Does this need to be as strong as SHOULD? Is this likely to conflict =
with dynamic discovery, should it ever exist?
>=20
>  RADIUS is a critical piece of infrastructure.  Exposing your RADIUS
> server to the entire IPv4 range is a bad idea.
>=20
>  The recommendation is a SHOULD so that it does not conflict with
> dynamic discovery.
>=20
>> -- 10.3, 5th and 6th paragraphs:
>>=20
>> Paragraph 5 says credentials should be statically configured. To me, =
"credentials" means "the certificate" in this case. That seems to =
disallow things like statically configuring a name that must match a =
certificate (perhaps signed by a CA.)
>=20
>  Credentials for the client should be statically configured.  It could
> be a PSK, or a certificate.
>=20
>  I'm not sure what "name" would match a certificate.  The document
> doesn't refer to names, and doesn't use names for anything.
>=20
>> Paragraph 6 seems to entirely contradict paragraph 5 by recommending =
private CAs, and accepting any peer that presents a cert signed by that =
CA. That's pretty much the opposite of statically configured =
credentials. (Paragraph 8 also seems to contradict the static =
configuration part.)
>=20
>  Both client and server still need to be configured with the private
> CA.  The alternative is to allow anyone to connect with any =
credentials,
> which seems odd.
>=20
>> The last sentence refers to "the invalid server". What invalid server =
is that? None have been mentioned so far.
>=20
>  The previous sentence talks about a "valid" server.  I'll clarify.
>=20
>> -- 10.4:
>>=20
>> The guidance in the last paragraph does not make sense. The section =
seems to say that NATs will break radius/dtls, so you should use dtls =
when behind a NAT.
>=20
>  RADIUS/UDP clients should not be behind a NAT.  I'll clarify.
>=20
>> -- 10.6, last paragraph:
>>=20
>> Can you elaborate on this? Why would an unauthorized 3rd party be =
able to get packets past the DTLS layer? OTOH, If an authorized client =
is sending invalid radius packets, wouldn't  you want to terminate the =
session?
>=20
>  That was a *long* discussion on the RADEXT list.
>=20
>  A server may be at protocol rev X, and a client may be at protocol =
rev
> X+1.  If the client sends packets allowed by X+1, the server should
> ignore them, as it does today with RADIUS/UDP.  Closing the connection
> is not necessary.
>=20
>> -- 10.7
>>=20
>> Redundant normative requirements (This is at least the third time the =
separate process issue and local proxy guidance has been described.)
>=20
>  It's a security considerations section, and needs to mention this.  =
It
> refers to Section 6.1, and adds new text explaining the security
> benefits of the approach.
>=20
>>=20
>>=20
>> *** Nits/editorial comments:
>>=20
>> -- IDNits reports some issues; please check.
>=20
>  They're fine.
>=20
>> -- Abstract:
>> Please avoid citations in the abstract. Please consider removing the =
"scare quotes".
>=20
>  OK.
>=20
>> -- Section 1, 5th paragraph:
>>=20
>> it seems like the RADIUS problems that this does not solve are in =
generally solved by RADIUS/TLS. If so, it would probably be worth a =
mention.
>=20
>  OK.
>=20
>> -- section 2.1, 4th paragraph from end:=20
>>=20
>> Seems like there are other changes as well. For example, you don't =
include "Use DTLS" as one of the changes in RADIUS/DTLS from RADIUS/USP.
>=20
>  OK.
>=20
>> -- 2.2 and children:
>>=20
>> In my strictly personal opinion, the approach of patching 6614 =
transfers a lot of effort from the author to the reader. A reader will =
basically need to keep both docs open side by side to understand this.  =
I understand the desire to avoid duplicating normative text, but I think =
that the balance here has swung too far away from readability.  (OTOH, =
see my related comment under "minor issues).
>=20
>  I think re-doing the document is a non-starter at this point.
>=20
>  Having done this myself, the bulk of the implementation work in doing
> DTLS is the UDP layer.  Most everything else can be re-used directly
> from RADIUS/TLS.
>=20
>> -- 2.2.1, paragraph 5:
>>=20
>> should TLS parameters be DTLS parameters?
>=20
>  Yes.
>=20
>> -- 2.2.2:
>>=20
>> Why a separate section to say sections 4 and 6 also apply? (The =
re-iteration seems unneeded.)
>=20
>  OK.
>=20
>> -- 3.1, last sentence:
>>=20
>> Really, 2.2.1 doesn't describe that. 6114 describes that. Better to =
cite the source than to cite a citation to the source, especially when =
that citation doesn't mention the issues at all.
>=20
>  OK.
>=20
>> -- 4, 3rd paragraph:
>>=20
>> Do you really mean multiple independent _implementations_? Or =
multiple independent instances or processes, perhaps running the same =
implementation?
>=20
>  All of that.
>=20
>> -- section 5 and children:
>>=20
>> In consistent use of "connection" vs "session".
>=20
>  I'll fix that.
>=20
>> -- 5.1.1, 2nd paragraph:
>>=20
>> What is an "entry" session?
>=20
>  The 4-tuple is logically a table tracking (4-tuple) -> (session =
data).
> Each one is an entry.
>=20
>  I'll try to clarify the text.
>=20
>> -- 6.1, 2nd paragraph:
>>=20
>> Source port? Source address? Both?
>=20
>  Both.
>=20
>> -- 7:
>>=20
>> Only the first paragraph seems to be about implementation experience.
>=20
>  OK.
>=20
>> -- 10, 2nd paragraph: "All of the security considerations for RADIUS =
apply to the RADIUS portion of the specification."
>>=20
>> The next paragraph seems to contradict this.
>=20
>  OK.
>=20
>> -- 10.3, 2nd paragraph: "... a client has a fixed IP address for a =
server ..."
>>=20
>> This is ambiguous. Do you mean the server knows the client address, =
or the client knows the server address? It sounds like the latter, but =
later text makes me wonder if you meant the former.
>=20
>  The following sentence addresses this.  The client has a fixed IP for
> the server, and the server has a fixed IP for the client.
>=20
>> -- 10.3, 7th paragraph: "... pre-configured with a list of known =
public CAs."
>>=20
>> By pre-configured, you mean by the manufacturer or vendor, right?
>=20
>  Yes.
>=20
>> -- 10.5, 2nd paragraph:
>>=20
>> Does this contradict guidance about using a private CA to identify =
multiple peers?
>=20
>  No.
>=20
>> I don't think you intend it that way; I assume you mean the cert =
presented by a client must be unique, but as written it's easy to assume =
that you mean the server has to have unique certs configured for each =
client, which it would not if it were to allow any arbitrary client that =
has a cert signed by a private CA.
>=20
>  That's what it says, so far as I can tell.
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext


From varun@comnet.tkk.fi  Fri Jan 24 08:44:49 2014
Return-Path: <varun@comnet.tkk.fi>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD511A0032 for <gen-art@ietfa.amsl.com>; Fri, 24 Jan 2014 08:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a1cyRmFQGWsH for <gen-art@ietfa.amsl.com>; Fri, 24 Jan 2014 08:44:46 -0800 (PST)
Received: from smtp-out-02.aalto.fi (smtp-out-02.aalto.fi [130.233.228.121]) by ietfa.amsl.com (Postfix) with ESMTP id 8C60F1A0023 for <gen-art@ietf.org>; Fri, 24 Jan 2014 08:44:46 -0800 (PST)
Received: from smtp-out-02.aalto.fi (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 11C5C2710BA_2E2987CB; Fri, 24 Jan 2014 16:44:44 +0000 (GMT)
Received: from smtp.netlab.hut.fi (luuri.netlab.hut.fi [130.233.154.177]) by smtp-out-02.aalto.fi (Sophos Email Appliance) with ESMTP id CF16D271075_2E2987BF; Fri, 24 Jan 2014 16:44:43 +0000 (GMT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.netlab.hut.fi (Postfix) with ESMTP id C771C1E0DD; Fri, 24 Jan 2014 18:44:43 +0200 (EET)
X-Virus-Scanned: by amavisd-new at luuri.netlab.hut.fi
Received: from smtp.netlab.hut.fi ([127.0.0.1]) by localhost (luuri.netlab.hut.fi [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gtGOaA-1umtj; Fri, 24 Jan 2014 18:44:38 +0200 (EET)
Received: from [10.249.94.180] (37-219-213-63.nat.bb.dnainternet.fi [37.219.213.63]) by smtp.netlab.hut.fi (Postfix) with ESMTPSA id 9A7851E040; Fri, 24 Jan 2014 18:44:38 +0200 (EET)
References: <52E28081.4000102@bell-labs.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <52E28081.4000102@bell-labs.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C0868AA-166D-4C0E-B176-C0A88EAE97E5@comnet.tkk.fi>
X-Mailer: iPhone Mail (11B554a)
From: Varun Singh <varun@comnet.tkk.fi>
Date: Fri, 24 Jan 2014 18:44:36 +0200
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Cc: "xrblock-chairs@tools.ietf.org" <xrblock-chairs@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 16:44:49 -0000

Hi Vijay,

Thank you for the careful review.=20

Comment inline.=20

Regards,
Varun

----
http://www.netlab.tkk.fi/~varun

> On 24.1.2014, at 17.02, "Vijay K. Gurbani" <vkg@bell-labs.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-xrblock-rtcp-xr-bytes-discarded-metric-01
> Reviewer: Vijay K. Gurbani
> Review Date: Jan-24-2014
> IETF LC End Date: Feb-04-2014
> IESG Telechat date: Unknown
>=20
> Major: 0
> Minor: 0
> Nits: 1
>=20
> This document is ready as a Proposed Standard.
>=20
> Nits:
> - S6, "In some situations, returning very detailed error information
> (e.g., over-range measurement or measurement unavailable) using this
> report block can provide an attacker with insight into the security
> processing." I am not sure what you mean by "security processing"
> here --- maybe you meant the byte discard block leaks privacy of the
> user?
>=20

It is not necessarily privacy of the user, but a situation when the receiver=
 reports a packet as discarded and If the packet was carefully crafted by an=
 attacker,  they infer something about the security processing of the endpoi=
nt.=20

AFAIR the wording of the paragraph is adapted from other drafts discussing d=
iscarded packets (RFC7097 and RFC7002) and with input from sec-dir. That bei=
ng said, if the wording can be made more clear, I'm happy to incorporate the=
 proposal.=20


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

From vkg@bell-labs.com  Fri Jan 24 10:57:22 2014
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA5181A00E6 for <gen-art@ietfa.amsl.com>; Fri, 24 Jan 2014 10:57:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qhfBq2V1jTFf for <gen-art@ietfa.amsl.com>; Fri, 24 Jan 2014 10:57:21 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id E5C991A00A9 for <gen-art@ietf.org>; Fri, 24 Jan 2014 10:57:20 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s0OIvFUH006404 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 24 Jan 2014 12:57:15 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s0OIvEWt032311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Jan 2014 12:57:15 -0600
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 s0OIvE7t000176; Fri, 24 Jan 2014 12:57:14 -0600 (CST)
Message-ID: <52E2B7BC.5070506@bell-labs.com>
Date: Fri, 24 Jan 2014 12:58:04 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Varun Singh <varun@comnet.tkk.fi>
References: <52E28081.4000102@bell-labs.com> <8C0868AA-166D-4C0E-B176-C0A88EAE97E5@comnet.tkk.fi>
In-Reply-To: <8C0868AA-166D-4C0E-B176-C0A88EAE97E5@comnet.tkk.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: "xrblock-chairs@tools.ietf.org" <xrblock-chairs@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 18:57:23 -0000

On 01/24/2014 10:44 AM, Varun Singh wrote:
>> Nits: - S6, "In some situations, returning very detailed error
>> information (e.g., over-range measurement or measurement
>> unavailable) using this report block can provide an attacker with
>> insight into the security processing." I am not sure what you mean
>> by "security processing" here --- maybe you meant the byte discard
>> block leaks privacy of the user?
>>
> It is not necessarily privacy of the user, but a situation when the
> receiver reports a packet as discarded and If the packet was
> carefully crafted by an attacker,  they infer something about the
> security processing of the endpoint.

Varun: It was not immediately clear to me that your threat model when
you discuss this included the attacker mounting an active attack, but
regardless, the larger question of what you mean by "security
processing" remains --- who is doing the "processing" and how is the
"security" impacted?

If an attacker crafts a packet and sends it to the victim, who discards
it, then the attacker gets a XR Bytes Discarded report block, and at
best the attacker knows that the packet was discarded due to either
early arrival or late arrival (the 'E' bit).  What is the "security
processing" insight that we are worried about here?

Furthermore, if the attacker is capable of mounting an attack such that
it can inject arbitrary packets to the victim, then the attacker is
either in a session with the victim (a session the victim can stop
at any time), or the attacker has usurped the channel between the
victim and the original participant that the victim was conversing
with.  In both cases, I suspect that the damage done is more than the
attacker just getting back discard report blocks.

> AFAIR the wording of the paragraph is adapted from other drafts
> discussing discarded packets (RFC7097 and RFC7002) and with input
> from sec-dir. That being said, if the wording can be made more clear,
> I'm happy to incorporate the proposal.

I would have had the same questions of rfc7097 or rfc7002 if I had been
chosen to Gen-ART review them :-)

I think you need to motivate your threat model in S6 to determine the
mitigation strategies where SRTP/SAVPF will help.  You can discuss this
with your chair or your friendly sec-dir personnel and if they
indicate that no threat model is needed, then please go ahead with the
draft.  Gen-ART reviews are advisory in nature anyway.  However, since
I was confused on reading the section and remain so after our brief
email exchange, I think some text added on the motivation may be helpful
to future readers (and implementers) of the extension.

Cheers,

- 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 ron.even.tlv@gmail.com  Sun Jan 26 00:16:30 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE0271A010D; Sun, 26 Jan 2014 00:16:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AzA0I3lxGfXy; Sun, 26 Jan 2014 00:16:28 -0800 (PST)
Received: from mail-ee0-x231.google.com (mail-ee0-x231.google.com [IPv6:2a00:1450:4013:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 8F8CF1A010C; Sun, 26 Jan 2014 00:16:27 -0800 (PST)
Received: by mail-ee0-f49.google.com with SMTP id d17so1681733eek.36 for <multiple recipients>; Sun, 26 Jan 2014 00:16:25 -0800 (PST)
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=O8aXxEzj547gHhS2QvvNZQL63A7ZKrMn44kQsRc1wXY=; b=xrrASH8WzplIeptgwit7mNgTmh3W2FuQcpNSYB8sOgpU2XXyesHrdQDR/3InivtcK5 +KXXJJgTQG/TlW9x6Wmvz4+xtNGnKIqPgT2KYE4U4gZbNd3gxoeS8IPMLW36DFaMwv52 YGkqxcZHPVq4etHBbiTtk7T+Jjg5FYsI9rzKwZwj10JBXTjCLwMGslWT3LYAVr34Ffjj u9I1PwWpUsd4DZV6qWlWLfvtrrPm5qgqu1ejNwQnFLMN/6TmgIu9RgLZrTxOmkAZHUwj bvhLp6aqDDsUYOXa6gtV1yVH+UFaE8htGnEdaROEgZ+vaPgTXPrd8Pa35KcblVyieeuL Rj8Q==
X-Received: by 10.14.9.70 with SMTP id 46mr109460ees.102.1390724185298; Sun, 26 Jan 2014 00:16:25 -0800 (PST)
Received: from RoniE ([109.66.49.55]) by mx.google.com with ESMTPSA id z49sm26153432eeo.10.2014.01.26.00.16.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 26 Jan 2014 00:16:24 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-pcp-description-option.all@tools.ietf.org>
Date: Sun, 26 Jan 2014 10:12:38 +0200
Message-ID: <02db01cf1a6e$62eb8280$28c28780$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02DC_01CF1A7F.267563F0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8ablfn3UbFfKwfSEyn6Pcjjhog/Q==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-pcp-description-option-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jan 2014 08:16:31 -0000

This is a multipart message in MIME format.

------=_NextPart_000_02DC_01CF1A7F.267563F0
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-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014-1-26

IETF LC End Date: 2014-2-4

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

 

1.       I am not sure what the use of the "description" option is. I can
see how to create one but as for usage the only text I can see is "Querying
the PCP server to get the description text of an existing mapping is out of
scope." I think that the document should provide information about the
purpose of this option.

 

Nits/editorial comments:

1.	The IANA section should provide enough information to fill the
registry
http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options 

 


------=_NextPart_000_02DC_01CF1A7F.267563F0
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:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 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:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 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:&n=
bsp; </span><span style=3D'font-family:"Courier =
New"'>draft-ietf-pcp-description-option-03<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2014&#8211;1-26<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: 2014&#8211;2-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=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I am not =
sure what the use of the &#8220;description&#8221; option is. I can see =
how to create one but as for usage the only text I can see is =
&#8220;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Querying =
the PCP server to get the description text of an existing mapping is out =
of scope.&#8221; I think that the document should provide information =
about the purpose of this option.</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=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l1 level1 lfo2'>The =
IANA section should provide enough information to fill the registry <a =
href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml=
#options">http://www.iana.org/assignments/pcp-parameters/pcp-parameters.x=
ml#options</a> <o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_02DC_01CF1A7F.267563F0--


From martin.thomson@gmail.com  Sun Jan 26 13:12:13 2014
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 421B01A0068 for <gen-art@ietfa.amsl.com>; Sun, 26 Jan 2014 13:12:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ONcdfFPgHjsf for <gen-art@ietfa.amsl.com>; Sun, 26 Jan 2014 13:12:09 -0800 (PST)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 0ABCF1A005B for <gen-art@ietf.org>; Sun, 26 Jan 2014 13:12:08 -0800 (PST)
Received: by mail-we0-f181.google.com with SMTP id u56so4579196wes.12 for <gen-art@ietf.org>; Sun, 26 Jan 2014 13:12:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=uBiwP/84UrKtoKdAYywLmOIA0EuKTsVe9zec8Z0nKNk=; b=tmdwcMrVnVyBD0kj+PIhDbxPzMchn5O8lwxbX7AI29ndP6tYxbaWcb4J1qKGXV3EXh nSe03ZUq55zirOG44aem5c+0urH2k5Zw5EdWoD5smcvs7OjKGIaMTn9HCwh/Y//Rcx1r 0TehyKDMSJl2i50Idy45W6FJQJSdCgPkc2sn2A90MKAzZya6kGWRx3xRmf74OGF0MBEg VmHwHJHu8SjEPSgM1LfvAHOePp+/2eIx/LRi7pIkmMFrC0U/YPs1nSOHwhUSIMCP3URn XutcKWSAoFA7+Mv4mUnXNwzOgh7+gdrLiDW4wby8ujb+z1EWQmmzs0mYZocp9P0tuZP3 whrQ==
MIME-Version: 1.0
X-Received: by 10.180.77.129 with SMTP id s1mr9712580wiw.56.1390770726646; Sun, 26 Jan 2014 13:12:06 -0800 (PST)
Received: by 10.227.145.131 with HTTP; Sun, 26 Jan 2014 13:12:06 -0800 (PST)
Date: Sun, 26 Jan 2014 13:12:06 -0800
Message-ID: <CABkgnnVN=mxwwvbMKw=F-+cfgxYUrO8hzmF0r14ApfP7cXAcTQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-alto-protocol.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [Gen-art] Gen-ART review of draft-ietf-alto-protocol-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jan 2014 21:12:13 -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-alto-protocol-25
Reviewer: Martin Thomson
Review Date: 2014-01-25
IETF LC End Date: 2014-02-04
IESG Telechat date: ?

Summary:  This is a pretty damned good document and an impressive
achievement.  Don't let the number of issues I raise lead you to
conclude that it isn't.  It's huge and complex and does a decent job
of containing that complexity, even though at times it requires a deal
of back-and-forth to comprehend properly.  I don't think it should be
published until at least the major issues I raise have been addressed,
but those issues don't represent fundamental flaws.

Major Issues:

You can't use US ASCII encoding as you do; simply stating that the
value is a string would be better.  JSON is required to be
UTF-{8|16|32}, so mandating an alternative encoding could be a real
problem.  Same for most of the string-based types.  In most cases you
can simply s/US ASCII string/string/ safely.  This extends to the way
that specific characters are identified; this should use the U+
notation, rather than the 0x notation used.

Section 10.2 defines a resource ID.  Why do this when you could use
URIs?  After all, that's what URIs are for.  I realize that this would
be something of a major change to the protocol, but I think that the
question is particularly important.

Use of URIs has particularly benefits too.  For example, the "uses"
attribute of the IRD would be made far more easily navigable if URIs
were used.

It's unclear to me what value VersionTag (Section 10.3) has over URI +
ETag.  Section 10.3 doesn't really explain this at all, and the bulk
of the explanation is ad hoc at best.  I'll note that the way of
describing a dependency is quite roundabout and potentially
problematic.  Each resource that has a dependency has a name+tag for
each dependency.

The name is a name from an IRD, but this creates a uniqueness problem
if multiple IRDs reference the same IR.  This seems likely for cases
where adjunct services like the endpoint cost service rely on a common
network map.

On the other hand, if this were changed to URI + ETag, consistent with
my earlier recommendation, there would be no need for the extra
indirection and HTTP headers could carry version information for each
resource.  All that would be required is to identify dependencies
correctly.  Even better, a link relation.

I note also that vtag is used in filtered documents.  I think that
this is problematic because two differently filtered maps will have
the same ID, and - according to 11.3.1.6 - the same vtag.  That makes
it impossible to identify a filtered map.  Better to instead identify
each with their own URI (use Content-Location) and to separately
identify the complete map from the filtered one so that it can be made
clear that identifiers in each of the filtered maps is from the same
namespace.

Minor Issues:

I think that the document needs to be clearer with respect to how the
source and destination in a cost map are identified.  For example,
Section 6.1.2 specially calls out IP addresses as the basis for costs.
 However, the introduction to Section 6 states (though I may be
inferring this) that PID is the only basis.

Section 8.2 leaves quite a few questions unanswered.  For instance, is
'object' and 'object-map' the only reserved words?  How is Type2
actually defined as a string?  How might I define Type4 as an array?
I'm not expecting formal grammar or a rigorous definition, but the
definition is a wee bit sparse.

The MUST in Section 8.3.3 isn't really necessary.  Particularly when
it is so immediately contradicted.

Section 8.3.4.3 isn't exhaustive, obviously, but it does highlight
just two of the major fallback techniques:
 * ask another server
 * manage without the information (since it's basically advisory in
most use cases anyway)
The third option is to find an alternative way to obtain the desired
information, since the protocol provides redundancy at more than the
resource level.  For example, a complete cost map could be requested
if the endpoint cost service fails.  This would be suboptimal, but
probably better than managing without.

Section 8.3.7 seems odd.  At the server, it would be easier to require
that cookies not be set.  A client is likely going to use a general
purpose client for making requests, so cookies set by the server are
probably going to be returned as per spec.  In either case, forcing
cookies to be ignored is potentially restrictive on the server choices
(authentication springs to mind here) or requiring of special work on
the client.  Either requires greater justification than this document
provides.

In Section 8.4.1, why not define ResponseMeta as an object with an
optional "code" attribute and all of the other optional "meta"
occupants you define?  Otherwise, this object is a non-definition of
sorts.

Section 10.6 and 10.8.2 define a prefixing rule for cost metric type
and endpoint properties.  This is contradictory to the received wisdom
of RFC 6648 and I encourage you not to define these special rules.
(Note: "priv:" =~ "x-", "exp:" == "x=")

With that, I think that it would be appropriate to lower the
registration requirements to "Expert Review".  "IETF Review" is a high
bar to set.

I am not convinced that a namespace system based on a period ('.') is
necessary when the CostType object can be expanded with additional
attributes.  Removing the significance of ':' and '.' (and either
allowing as regular characters or forbidding entirely) would be both
sufficient and considerably simpler.

I found it quite difficult to work out what an endpoint property was.
The explanation is a little lacking here.  I also think that the
structure could be greatly improved.

Furthermore, I find the construction of identifiers to be brittle.
The following would simpler in my opinion:

Request:
  {
    "properties" : [ "pid",
                     "my-example-prop" ],
    "endpoints"  : [ "ipv4:192.0.2.34",
                     "ipv4:203.0.113.129" ],
    "network-maps": [ "http://example.com/my-default-network-map" ]
  }

Response:
    {
    "meta" : {
      "depends" : { "http://example.com/my-default-network-map": "xyzzy" }
    },
    "endpoint-properties": {
      "ipv4:192.0.2.34"    : { "pid": {
"http://example.com/my-default-network-map": "PID1" }
                               "my-example-prop": "1" },
      "ipv4:203.0.113.129" : { "pid": {
"http://example.com/my-default-network-map": "PID3" } }
    }
  }

I'm tempted to suggest that there be a little consistency with respect
to network locations as well.  Sometimes type and value are in
separate fields, other times not.  (I know that this was a point of
long discussion in the WG though, so I'm less concerned here.)

Section 15.4.1 should probably mention the tracking of clients using
cookies or fingerprinting techniques.  (Is this where the Cookie
prohibition in Section 8.3.7 came from?  Because if it is, then it
should be MUST NOT send for clients as opposed to MUST NOT use for
servers.)


For Section 15.5.2, a server could also limit the size of M and N that
it is happy to accept a request for.

Is Appendix C normative?  It looks like it, but it's insufficiently
specified, particularly with respect to the formatting of "field" to
be normative.

Nits:

There's a bunch of lowercase "may" and "should" throughout.  I know
that opinions differ on the use of these in combination with 2119
lanauge, but I'll note that some of the statements appear to be
normative.

Later in p3, the SHOULD here doesn't seem particularly testable, as
phrased, though a rewording might make it so.

Section 8.2 is a little cramped.  Don't be scared of using more whitespace.

In Section 8.2, why 'JSONString' and not simply 'string'?  After all,
you use object rather than JSONObject.

Section 8.3.4.2 s/should normally be/is/

In Section 8.4.2 check the spelling of Info[r]ResourceDirectory.

Section 9.1.4, consider quoting "accepts" in "The associated accepts
attribute of an Information Resource [...]"

Last character of Section 9.2.5.1, delete ".

In Section 10.1, the definition of PID seems like an exemplar
candidate for ABNF.

In Section 11.2.1, the idea of optimizing for compactness in a
text-based format is somewhat laughable.  Compactness is best achieved
in these cases through the use of compression.  Readability is
laudable, as is accessibility to software.

Section 15.3.2, p2 s/need/needs/

Section 15.5.1 p1, missing space(s), consider capitalizing "m" and "n".

From yang.r.yang@gmail.com  Sun Jan 26 13:40:16 2014
Return-Path: <yang.r.yang@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B31121A00D7 for <gen-art@ietfa.amsl.com>; Sun, 26 Jan 2014 13:40:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4r4KumyiXWsA for <gen-art@ietfa.amsl.com>; Sun, 26 Jan 2014 13:40:13 -0800 (PST)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id AFF661A009E for <gen-art@ietf.org>; Sun, 26 Jan 2014 13:40:13 -0800 (PST)
Received: by mail-pb0-f48.google.com with SMTP id rr13so5116901pbb.21 for <gen-art@ietf.org>; Sun, 26 Jan 2014 13:40:11 -0800 (PST)
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=CmtM/frD7g//9tT41Q2A8xyimOuEKE4xtmUvsDR0u/w=; b=JNuMZVcAO2MIZKE96bW819eO0B8kEjh2xG+neMB2HwDp+9VsTUIxUik2AnPH1/KgCR bs3DqqX1UsZbDIr/tLC93Mb55Ortk9G82y9B/QFi9C5QGmCBBGnaJo4W5ncjT7/dANww KD6RyJ0DLFvZVP40e5F/Jp5iv+9j9aBcWBn/yHi9uyC2hI9aA+wQAmRp/SHcT5kyJVeK IEkPZKUVOAMIyrEtZhlDYamKyjLjb22+fPuERweNBLXnbEzb81YLnromxcG4pEWgZ2RL JEYRR/3wZU1MvsM69WzRPe8AptxryHr6xsF0153LDhS9zoxEpNLaBm7HKZ7/hMRB7Nwx Ceqg==
MIME-Version: 1.0
X-Received: by 10.66.192.74 with SMTP id he10mr26857709pac.126.1390772411824;  Sun, 26 Jan 2014 13:40:11 -0800 (PST)
Sender: yang.r.yang@gmail.com
Received: by 10.68.106.193 with HTTP; Sun, 26 Jan 2014 13:40:11 -0800 (PST)
Received: by 10.68.106.193 with HTTP; Sun, 26 Jan 2014 13:40:11 -0800 (PST)
In-Reply-To: <CABkgnnVN=mxwwvbMKw=F-+cfgxYUrO8hzmF0r14ApfP7cXAcTQ@mail.gmail.com>
References: <CABkgnnVN=mxwwvbMKw=F-+cfgxYUrO8hzmF0r14ApfP7cXAcTQ@mail.gmail.com>
Date: Sun, 26 Jan 2014 16:40:11 -0500
X-Google-Sender-Auth: g6aTA6D082JJzOlcEmLejKreECo
Message-ID: <CANUuoLpVQ71VM=M8J7FmYiJK6VwdF7JvqzG36ymGWAr2Z2qXQg@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdc9ebc92016904f0e66f25
X-Mailman-Approved-At: Sun, 26 Jan 2014 13:41:14 -0800
Cc: Wendy Roome <w.roome@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "N:" <draft-ietf-alto-protocol.all@tools.ietf.org>, Sebastian Kiesel <ietf-alto@skiesel.de>, Richard Alimi <ralimi@google.com>, "Reinaldo Penno, \(repenno\)" <repenno@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-alto-protocol-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jan 2014 21:40:16 -0000

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

Dear Martin,

This is an Ack that the authors have received the wonderful comments. Thank
you so much!

The first major issue (regarding string) is a good suggestion. We will take
a pass to address it.

The second major issue (uri) is more involved. There was one initial
proposal of using URI, and then the URI may point to any arbitrary
location. In light of your comments, the authors will discuss and get back
to you soon. Do you want to get involved in the discussions, or prefer that
the authors first discuss internally to get certain conclusion and then
involve you? Please advise. We will respond to the other issues within a
few days as well.

Thanks again!

Richard
On Jan 26, 2014 4:12 PM, "Martin Thomson" <martin.thomson@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-alto-protocol-25
> Reviewer: Martin Thomson
> Review Date: 2014-01-25
> IETF LC End Date: 2014-02-04
> IESG Telechat date: ?
>
> Summary:  This is a pretty damned good document and an impressive
> achievement.  Don't let the number of issues I raise lead you to
> conclude that it isn't.  It's huge and complex and does a decent job
> of containing that complexity, even though at times it requires a deal
> of back-and-forth to comprehend properly.  I don't think it should be
> published until at least the major issues I raise have been addressed,
> but those issues don't represent fundamental flaws.
>
> Major Issues:
>
> You can't use US ASCII encoding as you do; simply stating that the
> value is a string would be better.  JSON is required to be
> UTF-{8|16|32}, so mandating an alternative encoding could be a real
> problem.  Same for most of the string-based types.  In most cases you
> can simply s/US ASCII string/string/ safely.  This extends to the way
> that specific characters are identified; this should use the U+
> notation, rather than the 0x notation used.
>
> Section 10.2 defines a resource ID.  Why do this when you could use
> URIs?  After all, that's what URIs are for.  I realize that this would
> be something of a major change to the protocol, but I think that the
> question is particularly important.
>
> Use of URIs has particularly benefits too.  For example, the "uses"
> attribute of the IRD would be made far more easily navigable if URIs
> were used.
>
> It's unclear to me what value VersionTag (Section 10.3) has over URI +
> ETag.  Section 10.3 doesn't really explain this at all, and the bulk
> of the explanation is ad hoc at best.  I'll note that the way of
> describing a dependency is quite roundabout and potentially
> problematic.  Each resource that has a dependency has a name+tag for
> each dependency.
>
> The name is a name from an IRD, but this creates a uniqueness problem
> if multiple IRDs reference the same IR.  This seems likely for cases
> where adjunct services like the endpoint cost service rely on a common
> network map.
>
> On the other hand, if this were changed to URI + ETag, consistent with
> my earlier recommendation, there would be no need for the extra
> indirection and HTTP headers could carry version information for each
> resource.  All that would be required is to identify dependencies
> correctly.  Even better, a link relation.
>
> I note also that vtag is used in filtered documents.  I think that
> this is problematic because two differently filtered maps will have
> the same ID, and - according to 11.3.1.6 - the same vtag.  That makes
> it impossible to identify a filtered map.  Better to instead identify
> each with their own URI (use Content-Location) and to separately
> identify the complete map from the filtered one so that it can be made
> clear that identifiers in each of the filtered maps is from the same
> namespace.
>
> Minor Issues:
>
> I think that the document needs to be clearer with respect to how the
> source and destination in a cost map are identified.  For example,
> Section 6.1.2 specially calls out IP addresses as the basis for costs.
>  However, the introduction to Section 6 states (though I may be
> inferring this) that PID is the only basis.
>
> Section 8.2 leaves quite a few questions unanswered.  For instance, is
> 'object' and 'object-map' the only reserved words?  How is Type2
> actually defined as a string?  How might I define Type4 as an array?
> I'm not expecting formal grammar or a rigorous definition, but the
> definition is a wee bit sparse.
>
> The MUST in Section 8.3.3 isn't really necessary.  Particularly when
> it is so immediately contradicted.
>
> Section 8.3.4.3 isn't exhaustive, obviously, but it does highlight
> just two of the major fallback techniques:
>  * ask another server
>  * manage without the information (since it's basically advisory in
> most use cases anyway)
> The third option is to find an alternative way to obtain the desired
> information, since the protocol provides redundancy at more than the
> resource level.  For example, a complete cost map could be requested
> if the endpoint cost service fails.  This would be suboptimal, but
> probably better than managing without.
>
> Section 8.3.7 seems odd.  At the server, it would be easier to require
> that cookies not be set.  A client is likely going to use a general
> purpose client for making requests, so cookies set by the server are
> probably going to be returned as per spec.  In either case, forcing
> cookies to be ignored is potentially restrictive on the server choices
> (authentication springs to mind here) or requiring of special work on
> the client.  Either requires greater justification than this document
> provides.
>
> In Section 8.4.1, why not define ResponseMeta as an object with an
> optional "code" attribute and all of the other optional "meta"
> occupants you define?  Otherwise, this object is a non-definition of
> sorts.
>
> Section 10.6 and 10.8.2 define a prefixing rule for cost metric type
> and endpoint properties.  This is contradictory to the received wisdom
> of RFC 6648 and I encourage you not to define these special rules.
> (Note: "priv:" =~ "x-", "exp:" == "x=")
>
> With that, I think that it would be appropriate to lower the
> registration requirements to "Expert Review".  "IETF Review" is a high
> bar to set.
>
> I am not convinced that a namespace system based on a period ('.') is
> necessary when the CostType object can be expanded with additional
> attributes.  Removing the significance of ':' and '.' (and either
> allowing as regular characters or forbidding entirely) would be both
> sufficient and considerably simpler.
>
> I found it quite difficult to work out what an endpoint property was.
> The explanation is a little lacking here.  I also think that the
> structure could be greatly improved.
>
> Furthermore, I find the construction of identifiers to be brittle.
> The following would simpler in my opinion:
>
> Request:
>   {
>     "properties" : [ "pid",
>                      "my-example-prop" ],
>     "endpoints"  : [ "ipv4:192.0.2.34",
>                      "ipv4:203.0.113.129" ],
>     "network-maps": [ "http://example.com/my-default-network-map" ]
>   }
>
> Response:
>     {
>     "meta" : {
>       "depends" : { "http://example.com/my-default-network-map": "xyzzy" }
>     },
>     "endpoint-properties": {
>       "ipv4:192.0.2.34"    : { "pid": {
> "http://example.com/my-default-network-map": "PID1" }
>                                "my-example-prop": "1" },
>       "ipv4:203.0.113.129" : { "pid": {
> "http://example.com/my-default-network-map": "PID3" } }
>     }
>   }
>
> I'm tempted to suggest that there be a little consistency with respect
> to network locations as well.  Sometimes type and value are in
> separate fields, other times not.  (I know that this was a point of
> long discussion in the WG though, so I'm less concerned here.)
>
> Section 15.4.1 should probably mention the tracking of clients using
> cookies or fingerprinting techniques.  (Is this where the Cookie
> prohibition in Section 8.3.7 came from?  Because if it is, then it
> should be MUST NOT send for clients as opposed to MUST NOT use for
> servers.)
>
>
> For Section 15.5.2, a server could also limit the size of M and N that
> it is happy to accept a request for.
>
> Is Appendix C normative?  It looks like it, but it's insufficiently
> specified, particularly with respect to the formatting of "field" to
> be normative.
>
> Nits:
>
> There's a bunch of lowercase "may" and "should" throughout.  I know
> that opinions differ on the use of these in combination with 2119
> lanauge, but I'll note that some of the statements appear to be
> normative.
>
> Later in p3, the SHOULD here doesn't seem particularly testable, as
> phrased, though a rewording might make it so.
>
> Section 8.2 is a little cramped.  Don't be scared of using more whitespace.
>
> In Section 8.2, why 'JSONString' and not simply 'string'?  After all,
> you use object rather than JSONObject.
>
> Section 8.3.4.2 s/should normally be/is/
>
> In Section 8.4.2 check the spelling of Info[r]ResourceDirectory.
>
> Section 9.1.4, consider quoting "accepts" in "The associated accepts
> attribute of an Information Resource [...]"
>
> Last character of Section 9.2.5.1, delete ".
>
> In Section 10.1, the definition of PID seems like an exemplar
> candidate for ABNF.
>
> In Section 11.2.1, the idea of optimizing for compactness in a
> text-based format is somewhat laughable.  Compactness is best achieved
> in these cases through the use of compression.  Readability is
> laudable, as is accessibility to software.
>
> Section 15.3.2, p2 s/need/needs/
>
> Section 15.5.1 p1, missing space(s), consider capitalizing "m" and "n".
>

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

<p dir=3D"ltr">Dear Martin,</p>
<p dir=3D"ltr">This is an Ack that the authors have received the wonderful =
comments. Thank you so much!</p>
<p dir=3D"ltr">The first major issue (regarding string) is a good suggestio=
n. We will take a pass to address it. </p>
<p dir=3D"ltr">The second major issue (uri) is more involved. There was one=
 initial proposal of using URI, and then the URI may point to any arbitrary=
 location. In light of your comments, the authors will discuss and get back=
 to you soon. Do you want to get involved in the discussions, or prefer tha=
t the authors first discuss internally to get certain conclusion and then i=
nvolve you? Please advise. We will respond to the other issues within a few=
 days as well.</p>

<p dir=3D"ltr">Thanks again!</p>
<p dir=3D"ltr">Richard</p>
<div class=3D"gmail_quote">On Jan 26, 2014 4:12 PM, &quot;Martin Thomson&qu=
ot; &lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.thomson@gmail.co=
m</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am the assigned Gen-ART reviewer for this draft. For background on<br>
Gen-ART, please see the FAQ at<br>
<br>
&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" tar=
get=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&=
gt;.<br>
<br>
Please resolve these comments along with any other Last Call comments<br>
you may receive.<br>
<br>
Document: draft-ietf-alto-protocol-25<br>
Reviewer: Martin Thomson<br>
Review Date: 2014-01-25<br>
IETF LC End Date: 2014-02-04<br>
IESG Telechat date: ?<br>
<br>
Summary: =A0This is a pretty damned good document and an impressive<br>
achievement. =A0Don&#39;t let the number of issues I raise lead you to<br>
conclude that it isn&#39;t. =A0It&#39;s huge and complex and does a decent =
job<br>
of containing that complexity, even though at times it requires a deal<br>
of back-and-forth to comprehend properly. =A0I don&#39;t think it should be=
<br>
published until at least the major issues I raise have been addressed,<br>
but those issues don&#39;t represent fundamental flaws.<br>
<br>
Major Issues:<br>
<br>
You can&#39;t use US ASCII encoding as you do; simply stating that the<br>
value is a string would be better. =A0JSON is required to be<br>
UTF-{8|16|32}, so mandating an alternative encoding could be a real<br>
problem. =A0Same for most of the string-based types. =A0In most cases you<b=
r>
can simply s/US ASCII string/string/ safely. =A0This extends to the way<br>
that specific characters are identified; this should use the U+<br>
notation, rather than the 0x notation used.<br>
<br>
Section 10.2 defines a resource ID. =A0Why do this when you could use<br>
URIs? =A0After all, that&#39;s what URIs are for. =A0I realize that this wo=
uld<br>
be something of a major change to the protocol, but I think that the<br>
question is particularly important.<br>
<br>
Use of URIs has particularly benefits too. =A0For example, the &quot;uses&q=
uot;<br>
attribute of the IRD would be made far more easily navigable if URIs<br>
were used.<br>
<br>
It&#39;s unclear to me what value VersionTag (Section 10.3) has over URI +<=
br>
ETag. =A0Section 10.3 doesn&#39;t really explain this at all, and the bulk<=
br>
of the explanation is ad hoc at best. =A0I&#39;ll note that the way of<br>
describing a dependency is quite roundabout and potentially<br>
problematic. =A0Each resource that has a dependency has a name+tag for<br>
each dependency.<br>
<br>
The name is a name from an IRD, but this creates a uniqueness problem<br>
if multiple IRDs reference the same IR. =A0This seems likely for cases<br>
where adjunct services like the endpoint cost service rely on a common<br>
network map.<br>
<br>
On the other hand, if this were changed to URI + ETag, consistent with<br>
my earlier recommendation, there would be no need for the extra<br>
indirection and HTTP headers could carry version information for each<br>
resource. =A0All that would be required is to identify dependencies<br>
correctly. =A0Even better, a link relation.<br>
<br>
I note also that vtag is used in filtered documents. =A0I think that<br>
this is problematic because two differently filtered maps will have<br>
the same ID, and - according to 11.3.1.6 - the same vtag. =A0That makes<br>
it impossible to identify a filtered map. =A0Better to instead identify<br>
each with their own URI (use Content-Location) and to separately<br>
identify the complete map from the filtered one so that it can be made<br>
clear that identifiers in each of the filtered maps is from the same<br>
namespace.<br>
<br>
Minor Issues:<br>
<br>
I think that the document needs to be clearer with respect to how the<br>
source and destination in a cost map are identified. =A0For example,<br>
Section 6.1.2 specially calls out IP addresses as the basis for costs.<br>
=A0However, the introduction to Section 6 states (though I may be<br>
inferring this) that PID is the only basis.<br>
<br>
Section 8.2 leaves quite a few questions unanswered. =A0For instance, is<br=
>
&#39;object&#39; and &#39;object-map&#39; the only reserved words? =A0How i=
s Type2<br>
actually defined as a string? =A0How might I define Type4 as an array?<br>
I&#39;m not expecting formal grammar or a rigorous definition, but the<br>
definition is a wee bit sparse.<br>
<br>
The MUST in Section 8.3.3 isn&#39;t really necessary. =A0Particularly when<=
br>
it is so immediately contradicted.<br>
<br>
Section 8.3.4.3 isn&#39;t exhaustive, obviously, but it does highlight<br>
just two of the major fallback techniques:<br>
=A0* ask another server<br>
=A0* manage without the information (since it&#39;s basically advisory in<b=
r>
most use cases anyway)<br>
The third option is to find an alternative way to obtain the desired<br>
information, since the protocol provides redundancy at more than the<br>
resource level. =A0For example, a complete cost map could be requested<br>
if the endpoint cost service fails. =A0This would be suboptimal, but<br>
probably better than managing without.<br>
<br>
Section 8.3.7 seems odd. =A0At the server, it would be easier to require<br=
>
that cookies not be set. =A0A client is likely going to use a general<br>
purpose client for making requests, so cookies set by the server are<br>
probably going to be returned as per spec. =A0In either case, forcing<br>
cookies to be ignored is potentially restrictive on the server choices<br>
(authentication springs to mind here) or requiring of special work on<br>
the client. =A0Either requires greater justification than this document<br>
provides.<br>
<br>
In Section 8.4.1, why not define ResponseMeta as an object with an<br>
optional &quot;code&quot; attribute and all of the other optional &quot;met=
a&quot;<br>
occupants you define? =A0Otherwise, this object is a non-definition of<br>
sorts.<br>
<br>
Section 10.6 and 10.8.2 define a prefixing rule for cost metric type<br>
and endpoint properties. =A0This is contradictory to the received wisdom<br=
>
of RFC 6648 and I encourage you not to define these special rules.<br>
(Note: &quot;priv:&quot; =3D~ &quot;x-&quot;, &quot;exp:&quot; =3D=3D &quot=
;x=3D&quot;)<br>
<br>
With that, I think that it would be appropriate to lower the<br>
registration requirements to &quot;Expert Review&quot;. =A0&quot;IETF Revie=
w&quot; is a high<br>
bar to set.<br>
<br>
I am not convinced that a namespace system based on a period (&#39;.&#39;) =
is<br>
necessary when the CostType object can be expanded with additional<br>
attributes. =A0Removing the significance of &#39;:&#39; and &#39;.&#39; (an=
d either<br>
allowing as regular characters or forbidding entirely) would be both<br>
sufficient and considerably simpler.<br>
<br>
I found it quite difficult to work out what an endpoint property was.<br>
The explanation is a little lacking here. =A0I also think that the<br>
structure could be greatly improved.<br>
<br>
Furthermore, I find the construction of identifiers to be brittle.<br>
The following would simpler in my opinion:<br>
<br>
Request:<br>
=A0 {<br>
=A0 =A0 &quot;properties&quot; : [ &quot;pid&quot;,<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;my-example-prop&quot; ],<b=
r>
=A0 =A0 &quot;endpoints&quot; =A0: [ &quot;ipv4:192.0.2.34&quot;,<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;ipv4:203.0.113.129&quot; ]=
,<br>
=A0 =A0 &quot;network-maps&quot;: [ &quot;<a href=3D"http://example.com/my-=
default-network-map" target=3D"_blank">http://example.com/my-default-networ=
k-map</a>&quot; ]<br>
=A0 }<br>
<br>
Response:<br>
=A0 =A0 {<br>
=A0 =A0 &quot;meta&quot; : {<br>
=A0 =A0 =A0 &quot;depends&quot; : { &quot;<a href=3D"http://example.com/my-=
default-network-map" target=3D"_blank">http://example.com/my-default-networ=
k-map</a>&quot;: &quot;xyzzy&quot; }<br>
=A0 =A0 },<br>
=A0 =A0 &quot;endpoint-properties&quot;: {<br>
=A0 =A0 =A0 &quot;ipv4:192.0.2.34&quot; =A0 =A0: { &quot;pid&quot;: {<br>
&quot;<a href=3D"http://example.com/my-default-network-map" target=3D"_blan=
k">http://example.com/my-default-network-map</a>&quot;: &quot;PID1&quot; }<=
br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;my-exa=
mple-prop&quot;: &quot;1&quot; },<br>
=A0 =A0 =A0 &quot;ipv4:203.0.113.129&quot; : { &quot;pid&quot;: {<br>
&quot;<a href=3D"http://example.com/my-default-network-map" target=3D"_blan=
k">http://example.com/my-default-network-map</a>&quot;: &quot;PID3&quot; } =
}<br>
=A0 =A0 }<br>
=A0 }<br>
<br>
I&#39;m tempted to suggest that there be a little consistency with respect<=
br>
to network locations as well. =A0Sometimes type and value are in<br>
separate fields, other times not. =A0(I know that this was a point of<br>
long discussion in the WG though, so I&#39;m less concerned here.)<br>
<br>
Section 15.4.1 should probably mention the tracking of clients using<br>
cookies or fingerprinting techniques. =A0(Is this where the Cookie<br>
prohibition in Section 8.3.7 came from? =A0Because if it is, then it<br>
should be MUST NOT send for clients as opposed to MUST NOT use for<br>
servers.)<br>
<br>
<br>
For Section 15.5.2, a server could also limit the size of M and N that<br>
it is happy to accept a request for.<br>
<br>
Is Appendix C normative? =A0It looks like it, but it&#39;s insufficiently<b=
r>
specified, particularly with respect to the formatting of &quot;field&quot;=
 to<br>
be normative.<br>
<br>
Nits:<br>
<br>
There&#39;s a bunch of lowercase &quot;may&quot; and &quot;should&quot; thr=
oughout. =A0I know<br>
that opinions differ on the use of these in combination with 2119<br>
lanauge, but I&#39;ll note that some of the statements appear to be<br>
normative.<br>
<br>
Later in p3, the SHOULD here doesn&#39;t seem particularly testable, as<br>
phrased, though a rewording might make it so.<br>
<br>
Section 8.2 is a little cramped. =A0Don&#39;t be scared of using more white=
space.<br>
<br>
In Section 8.2, why &#39;JSONString&#39; and not simply &#39;string&#39;? =
=A0After all,<br>
you use object rather than JSONObject.<br>
<br>
Section 8.3.4.2 s/should normally be/is/<br>
<br>
In Section 8.4.2 check the spelling of Info[r]ResourceDirectory.<br>
<br>
Section 9.1.4, consider quoting &quot;accepts&quot; in &quot;The associated=
 accepts<br>
attribute of an Information Resource [...]&quot;<br>
<br>
Last character of Section 9.2.5.1, delete &quot;.<br>
<br>
In Section 10.1, the definition of PID seems like an exemplar<br>
candidate for ABNF.<br>
<br>
In Section 11.2.1, the idea of optimizing for compactness in a<br>
text-based format is somewhat laughable. =A0Compactness is best achieved<br=
>
in these cases through the use of compression. =A0Readability is<br>
laudable, as is accessibility to software.<br>
<br>
Section 15.3.2, p2 s/need/needs/<br>
<br>
Section 15.5.1 p1, missing space(s), consider capitalizing &quot;m&quot; an=
d &quot;n&quot;.<br>
</blockquote></div>

--047d7bdc9ebc92016904f0e66f25--

From david.black@emc.com  Sun Jan 26 18:07:12 2014
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 806981A0177; Sun, 26 Jan 2014 18:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UYbdt8fMIrWX; Sun, 26 Jan 2014 18:07:10 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id DC25E1A017F; Sun, 26 Jan 2014 18:07:09 -0800 (PST)
Received: from maildlpprd52.lss.emc.com (maildlpprd52.lss.emc.com [10.106.48.156]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0R272eN009869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Jan 2014 21:07:04 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s0R272eN009869
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390788424; bh=NTNbS+noRA1hBvvbiBuOg2FrqTY=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=rY2IROtckpBIBAobnn1MktvIui+paBtFv70Frg6GtgN14Y+ikpSrasrkCvH8Y9/EU fME+qFSf4485+KN9dVCGs2sT+jLcTU6Kld4rv5z+nmiDsMy7h3wOX1OYTLoocBuzTU v2ylUXkxXwLIuhBCeXwq3QeeB6a6vCJ8to6Kwtjg=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s0R272eN009869
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd52.lss.emc.com (RSA Interceptor); Sun, 26 Jan 2014 21:06:56 -0500
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0R26tat031811 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 26 Jan 2014 21:06:56 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Sun, 26 Jan 2014 21:06:54 -0500
From: "Black, David" <david.black@emc.com>
To: "Alexey Melnikov (alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>,  "dcridland@arcode.com" <dcridland@arcode.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Sun, 26 Jan 2014 21:06:53 -0500
Thread-Topic: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
Thread-Index: Ac8bBHAYj1adCBYhQu2KINJ+hxA0mA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@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-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: public, Resumes
Cc: "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>, "ietf@ietf.org" <ietf@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 02:07:12 -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-qresync-rfc5162bis-09
Reviewer: David L. Black
Review Date: January 26, 2014
IETF LC End Date: January 27, 2014

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

This draft consolidates RFC 4551 (IMAP Conditional STORE) and RFC 5162
(IMAP Quick Mailbox Resynchronization) into a single document and makes
a few minor updates.  It also updates the command line length
recommendation in RFC 2683 to support the longer command lines that
can occur with these extensions.

As this is an update, I checked the diffs against RFC 4551 and RFC 5162;
they look reasonable.  I found one minor issue that should be relatively
easy to address.

Minor Issues:

The command line length change in Section 4 applies to all IMAP commands,
and hence affects old servers, including those that don't implement either
of the extensions in this draft. That raises a backwards compatibility
concern - what happens when a new client sends a > 1000 character command
line to an old server that isn't expecting more than 1000 characters?

One possibility would be to apply the larger length recommendation only
after the client determines that the server supports at least one of
these extensions.

Nits/editorial comments:

The update to RFC 2683 would be easier to find from the table of contents
if the title of Section 4 were changed to "Long Command Lines (Update to
RFC 2683)".

idnits 2.13.01 got confused by the command line examples, and flagged a
downref:

  ** Downref: Normative reference to an Informational RFC: RFC 2683

That downref appears to be ok and intended, as noted in the shepherd's
writeup.

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 mohamed.boucadair@orange.com  Mon Jan 27 00:31:15 2014
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB1061A002E; Mon, 27 Jan 2014 00:31:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.548
X-Spam-Level: 
X-Spam-Status: No, score=-0.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gNLgauZmPdZH; Mon, 27 Jan 2014 00:31:12 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) by ietfa.amsl.com (Postfix) with ESMTP id F023E1A0111; Mon, 27 Jan 2014 00:31:11 -0800 (PST)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda09.si.francetelecom.fr (ESMTP service) with ESMTP id 0CD34C04F7; Mon, 27 Jan 2014 09:31:09 +0100 (CET)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id DA2DEC804B; Mon, 27 Jan 2014 09:31:08 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Mon, 27 Jan 2014 09:31:08 +0100
From: <mohamed.boucadair@orange.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-pcp-description-option.all@tools.ietf.org" <draft-ietf-pcp-description-option.all@tools.ietf.org>
Date: Mon, 27 Jan 2014 09:31:06 +0100
Thread-Topic: Gen-ART LC review of draft-ietf-pcp-description-option-03
Thread-Index: Ac8ablfn3UbFfKwfSEyn6Pcjjhog/QAyx66A
Message-ID: <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr>
References: <02db01cf1a6e$62eb8280$28c28780$@gmail.com>
In-Reply-To: <02db01cf1a6e$62eb8280$28c28780$@gmail.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_94C682931C08B048B7A8645303FDC9F36F4736082CPUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.19.63615
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-pcp-description-option-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 08:31:16 -0000

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

Dear Roni,
Thank you for the review.
Please see inline.
Cheers,
Med
De : Roni Even [mailto:ron.even.tlv@gmail.com]
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.
Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document:  draft-ietf-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014-1-26

IETF LC End Date: 2014-2-4

IESG Telechat date:



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





Major issues:



Minor issues:



1.       I am not sure what the use of the "description" option is. I can s=
ee how to create one but as for usage the only text I can see is "Querying =
the PCP server to get the description text of an existing mapping is out of=
 scope." I think that the document should provide information about the pur=
pose of this option.

[Med] The main usage is for a user to associate a textual description with =
a mapping. This is captured by this text "   This option can be used by a u=
ser (or an application) to indicate a
   description associated with a given mapping such as "FTP server", "My
   remote access to my CP router", "Camera", "Network attached storage
   serve", etc.

"


Nits/editorial comments:

 1.  The IANA section should provide enough information to fill the registr=
y http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options
[Med] Required information as per RFC6887 is provided in http://tools.ietf.=
org/html/draft-ietf-pcp-description-option-03#section-2.


--_000_94C682931C08B048B7A8645303FDC9F36F4736082CPUEXCB1Bnante_
Content-Type: text/html; charset="iso-8859-1"
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=3Diso-8859-1"><meta name=3DGenerator content=3D"Micr=
osoft 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;}
@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:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	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:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:#1F497D;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1837839053;
	mso-list-template-ids:1556752032;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;line-height:115%;font-family:"Courier New";color:#1F497D'>D=
ear Roni,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:10.0pt;line-height:115%;font-family:"Courier New";color:#1F497D'>Thank yo=
u for the review. <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:10.0pt;line-height:115%;font-family:"Courier New";color:#1F497D'=
>Please see inline.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";color:#1F49=
7D'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:10.0pt;line-height:115%;font-family:"Courier New";color:#1F497D'>Med<o:=
p></o:p></span></p><div style=3D'border:none;border-left:solid blue 1.5pt;p=
adding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-top:solid #=
B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal style=3D'margi=
n-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><b><span lang=3DFR s=
tyle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</span=
></b><span lang=3DFR style=3D'font-size:10.0pt;font-family:"Tahoma","sans-s=
erif"'> Roni Even [mailto:ron.even.tlv@gmail.com] <br><b>Envoy=E9&nbsp;:</b=
> dimanche 26 janvier 2014 09:13<br><b>=C0&nbsp;:</b> draft-ietf-pcp-descri=
ption-option.all@tools.ietf.org<br><b>Cc&nbsp;:</b> ietf@ietf.org; gen-art@=
ietf.org<br><b>Objet&nbsp;:</b> Gen-ART LC review of draft-ietf-pcp-descrip=
tion-option-03<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DFR><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><a name=3D"OLE_L=
INK2"></a><a name=3D"OLE_LINK1"></a>I am the assigned Gen-ART reviewer for =
this draft. For background on Gen-ART, please see the FAQ at &lt;<a href=3D=
"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank"=
>http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p=
></p><p class=3DMsoNormal>Please resolve these comments along with any othe=
r 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"'>Docume=
nt:&nbsp; </span><span style=3D'font-family:"Courier New"'>draft-ietf-pcp-d=
escription-option-03<o:p></o:p></span></p><p class=3DMsoPlainText><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: Roni E=
ven<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif"'>Review Date:2014&#8211;1-26<o:p><=
/o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif"'>IETF LC End Date: 2014&#8211;2-4<o:p></o:p=
></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-fa=
mily:"Calibri","sans-serif"'>IESG Telechat date: <o:p></o:p></span></p><p c=
lass=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","=
sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: This dra=
ft is almost ready for publication as a standard track RFC.<o:p></o:p></spa=
n></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>&n=
bsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0p=
t;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 st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor issues:<o=
:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoPlainText style=3D'margin-left:36.0pt;text-indent:-18.0pt;mso-list:l0=
 level1 lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>1.<span style=
=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </sp=
an></span></span><![endif]><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif"'>I am not sure what the use of the &#8220;description&#8=
221; option is. I can see how to create one but as for usage the only text =
I can see is &#8220;Querying the PCP server to get the description text of =
an existing mapping is out of scope.&#8221; I think that the document shoul=
d provide information about the purpose of this option.<o:p></o:p></span></=
p><pre><b><i><span style=3D'color:#1F497D'>[Med] The main usage is for a us=
er to associate a textual description with a mapping. This is captured by t=
his text &#8220;</span></i></b>=A0=A0 This option can be used by a user (or=
 an application) to indicate a<o:p></o:p></pre><p class=3DMsoNormal style=
=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'>=A0=A0 description associat=
ed with a given mapping such as &quot;FTP server&quot;, &quot;My<o:p></o:p>=
</span></p><p class=3DMsoNormal style=3D'margin-bottom:0cm;margin-bottom:.0=
001pt;line-height:normal'><span style=3D'font-size:10.0pt;font-family:"Cour=
ier New"'>=A0=A0 remote access to my CP router&quot;, &quot;Camera&quot;, &=
quot;Network attached storage<o:p></o:p></span></p><p class=3DMsoNormal sty=
le=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><span sty=
le=3D'font-size:10.0pt;font-family:"Courier New"'>=A0=A0 serve&quot;, etc.<=
o:p></o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'font-size=
:10.0pt;font-family:"Courier New";color:#1F497D'>&#8221;<o:p></o:p></span><=
/i></b></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p cl=
ass=3DMsoNormal>Nits/editorial comments:<o:p></o:p></p><ol style=3D'margin-=
top:0cm' start=3D1 type=3D1><li class=3DMsoNormal style=3D'mso-list:l1 leve=
l1 lfo5'>The IANA section should provide enough information to fill the reg=
istry <a href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-paramet=
ers.xml#options">http://www.iana.org/assignments/pcp-parameters/pcp-paramet=
ers.xml#options</a> <o:p></o:p></li></ol><p class=3DMsoNormal><b><i><span s=
tyle=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";color:#=
1F497D'>[Med] Required information as per RFC6887 is provided in <a href=3D=
"http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2"=
>http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2<=
/a>. </span></i></b><span style=3D'font-size:10.0pt;line-height:115%;font-f=
amily:"Courier New";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p></div></div></body></html>=

--_000_94C682931C08B048B7A8645303FDC9F36F4736082CPUEXCB1Bnante_--

From ron.even.tlv@gmail.com  Mon Jan 27 01:35:04 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8C1A1A011C; Mon, 27 Jan 2014 01:35:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHW3abtXXyK3; Mon, 27 Jan 2014 01:35:01 -0800 (PST)
Received: from mail-ea0-x22a.google.com (mail-ea0-x22a.google.com [IPv6:2a00:1450:4013:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id ED5FD1A0117; Mon, 27 Jan 2014 01:35:00 -0800 (PST)
Received: by mail-ea0-f170.google.com with SMTP id k10so2158064eaj.15 for <multiple recipients>; Mon, 27 Jan 2014 01:34:58 -0800 (PST)
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:thread-index:content-language; bh=+S8C2s6/5BP+rxt5uSY2LO/pOQpHBE7+wBsaMf6Dvb4=; b=MGGEpDsocD/kKDZg8xNqzj+U7OndgZ5O8Oe4Y/VvNDhMouODwJ14dNECCVVzGLvjZf sc+meBMwjCAXkkC/MZsttdauerUtxplw9KCQpt+/1sNcNW8uIZ/EzO1qsgKBzkuRup28 cRDzHyxqKn81zLtiuFGf27K730pW5FvLRY9VPXO+l/ZBq5ZlgVHnF9cu8uX4nj9ZhSh8 g4PwHwSeUwssPjZQ0C1jlSOT8dWBpgVB6HXm3JwDM0lxA7ErQBt+MBns+KNlZF8TjDv1 Bb0zne/Ba/hxmlxIzEy5D++Ci/PVqprdMixognvBWpd95MBP3aGOi62F79jkGTHIxR33 jOdA==
X-Received: by 10.14.95.2 with SMTP id o2mr20122125eef.69.1390815298175; Mon, 27 Jan 2014 01:34:58 -0800 (PST)
Received: from RoniE ([109.66.49.55]) by mx.google.com with ESMTPSA id o13sm40083434eex.19.2014.01.27.01.34.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 27 Jan 2014 01:34:57 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <mohamed.boucadair@orange.com>, <draft-ietf-pcp-description-option.all@tools.ietf.org>
References: <02db01cf1a6e$62eb8280$28c28780$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr>
Date: Mon, 27 Jan 2014 11:31:08 +0200
Message-ID: <033d01cf1b42$854c10e0$8fe432a0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_033E_01CF1B53.48D64070"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF6/p6mIwEjavahOcoGuw0nlckk9wI8szcDmy6g4DA=
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-pcp-description-option-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 09:35:05 -0000

This is a multipart message in MIME format.

------=_NextPart_000_033E_01CF1B53.48D64070
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Med,=20

Inline

Roni

=20

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

Sent: 27 January, 2014 10:31 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Dear Roni,

Thank you for the review.=20

Please see inline.

Cheers,

Med

De : Roni Even [mailto:ron.even.tlv@gmail.com]=20
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

=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-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014=961-26

IETF LC End Date: 2014=962-4

IESG Telechat date:=20

=20

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

=20

=20

Major issues:

=20

Minor issues:

=20

1.       I am not sure what the use of the =93description=94 option is. =
I can
see how to create one but as for usage the only text I can see is =
=93Querying
the PCP server to get the description text of an existing mapping is out =
of
scope.=94 I think that the document should provide information about the
purpose of this option.

[Med] The main usage is for a user to associate a textual description =
with a
mapping. This is captured by this text =93   This option can be used by =
a user
(or an application) to indicate a

   description associated with a given mapping such as "FTP server", "My

   remote access to my CP router", "Camera", "Network attached storage

   serve", etc.

=94

[Roni Even] This is motivation but it is not clear why the user does it =
if
no one can see it or does anything with it. It is kept on the server but =
not
used by anyone?

=20

Nits/editorial comments:

1.	The IANA section should provide enough information to fill the
registry
http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options=
=20

[Med] Required information as per RFC6887 is provided in
http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2=
.=20

[Roni Even] So section 5 should point to the definition is section 2

=20

=20


------=_NextPart_000_033E_01CF1B53.48D64070
Content-Type: text/html;
	charset="ISO-8859-1"
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=3Diso-8859-1"><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:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	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";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	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";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:"Courier New";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle29
	{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;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 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:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 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;}
@list l2
	{mso-list-id:2105032897;
	mso-list-template-ids:-1035336528;}
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><span =
style=3D'color:#1F497D'>Hi Med, <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Inline<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com] =
<br><b>Sent:</b> 27 January, 2014 10:31 AM<br><b>To:</b> Roni Even; =
draft-ietf-pcp-description-option.all@tools.ietf.org<br><b>Cc:</b> =
ietf@ietf.org; gen-art@ietf.org<br><b>Subject:</b> RE: Gen-ART LC review =
of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Dear Roni,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Thank you for the review. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Please see inline.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Med<o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</s=
pan></b><span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni Even =
[<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Envoy=E9&nbsp;:</b> dimanche 26 janvier 2014 =
09:13<br><b>=C0&nbsp;:</b> <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc&nbsp;:</b> =
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Objet&nbsp;:<=
/b> Gen-ART LC review of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DFR><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><a name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I =
am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Document:&nbsp; <span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Courier =
New"'>draft-ietf-pcp-description-option-03<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Reviewer: Roni =
Even<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Review =
Date:2014&#8211;1-26<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>IETF LC End Date: =
2014&#8211;2-4<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>IESG Telechat date: =
<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Summary: This draft is =
almost ready for publication as a standard track RFC.<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Major =
issues:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Minor =
issues:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>I am not sure what the =
use of the &#8220;description&#8221; option is. I can see how to create =
one but as for usage the only text I can see is &#8220;Querying the PCP =
server to get the description text of an existing mapping is out of =
scope.&#8221; I think that the document should provide information about =
the purpose of this option.<o:p></o:p></p><pre><b><i><span =
style=3D'color:#1F497D'>[Med] The main usage is for a user to associate =
a textual description with a mapping. This is captured by this text =
&#8220;</span></i></b>&nbsp;&nbsp; This option can be used by a user (or =
an application) to indicate a<o:p></o:p></pre><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
description associated with a given mapping such as &quot;FTP =
server&quot;, &quot;My<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
remote access to my CP router&quot;, &quot;Camera&quot;, &quot;Network =
attached storage<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
serve&quot;, etc.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>&#8221;<o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'color:#1F497D'>[Roni Even] </span></i></b><span =
style=3D'color:#1F497D'>This is motivation but it is not clear why the =
user does it if no one can see it or does anything with it. It is kept =
on the server but not used by anyone?<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal>Nits/editorial comments:<o:p></o:p></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l1 level1 lfo5'>The IANA section should provide enough =
information to fill the registry <a =
href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml=
#options">http://www.iana.org/assignments/pcp-parameters/pcp-parameters.x=
ml#options</a> <o:p></o:p></li></ol><p class=3DMsoNormal><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>[Med] Required information as per RFC6887 is =
provided in <a =
href=3D"http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#s=
ection-2">http://tools.ietf.org/html/draft-ietf-pcp-description-option-03=
#section-2</a>. <o:p></o:p></span></i></b></p><p =
class=3DMsoNormal><b><i><span style=3D'color:#1F497D'>[Roni Even] =
</span></i></b><span style=3D'color:#1F497D'>So section 5 should point =
to the definition is section 2<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_033E_01CF1B53.48D64070--


From mohamed.boucadair@orange.com  Mon Jan 27 01:55:16 2014
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83BE71A0184; Mon, 27 Jan 2014 01:55:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.548
X-Spam-Level: 
X-Spam-Status: No, score=-1.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gskwMuUXJ2KZ; Mon, 27 Jan 2014 01:55:13 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by ietfa.amsl.com (Postfix) with ESMTP id D13381A011C; Mon, 27 Jan 2014 01:55:12 -0800 (PST)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id EF4432AC68D; Mon, 27 Jan 2014 10:55:09 +0100 (CET)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id CE590384078; Mon, 27 Jan 2014 10:55:09 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Mon, 27 Jan 2014 10:55:09 +0100
From: <mohamed.boucadair@orange.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-pcp-description-option.all@tools.ietf.org" <draft-ietf-pcp-description-option.all@tools.ietf.org>
Date: Mon, 27 Jan 2014 10:55:07 +0100
Thread-Topic: Gen-ART LC review of draft-ietf-pcp-description-option-03
Thread-Index: AQF6/p6mIwEjavahOcoGuw0nlckk9wI8szcDmy6g4DCAAAX/8A==
Message-ID: <94C682931C08B048B7A8645303FDC9F36F473608DF@PUEXCB1B.nanterre.francetelecom.fr>
References: <02db01cf1a6e$62eb8280$28c28780$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr> <033d01cf1b42$854c10e0$8fe432a0$@gmail.com>
In-Reply-To: <033d01cf1b42$854c10e0$8fe432a0$@gmail.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_94C682931C08B048B7A8645303FDC9F36F473608DFPUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.19.63615
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-pcp-description-option-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 09:55:16 -0000

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

Re-,
The description is used by the entity managing the PCP server. The document=
 does not elaborate on such usage as this is deployment-specific: e.g.,  (1=
) it can be used as  helper to clean the mapping table, (2) in some deploym=
ents that make use of a portal to instruct pcp mappings, this option can be=
 used to store a subscriber-identifier, etc. We can add some text if you th=
ink this is useful to be mentioned in the document.
For the second point, I updated Section 5 with a pointer to Section 2. Than=
ks.
Cheers,
Med
De : Roni Even [mailto:ron.even.tlv@gmail.com]
Envoy=E9 : lundi 27 janvier 2014 10:31
=C0 : BOUCADAIR Mohamed IMT/OLN; draft-ietf-pcp-description-option.all@tool=
s.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

Hi Med,
Inline
Roni

From: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> [ma=
ilto:mohamed.boucadair@orange.com]
Sent: 27 January, 2014 10:31 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org<mailto:=
draft-ietf-pcp-description-option.all@tools.ietf.org>
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@ie=
tf.org>
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

Dear Roni,
Thank you for the review.
Please see inline.
Cheers,
Med
De : Roni Even [mailto:ron.even.tlv@gmail.com]
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org<mailto:draft-iet=
f-pcp-description-option.all@tools.ietf.org>
Cc : ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@i=
etf.org>
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.
Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document:  draft-ietf-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014-1-26

IETF LC End Date: 2014-2-4

IESG Telechat date:



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





Major issues:



Minor issues:



1.       I am not sure what the use of the "description" option is. I can s=
ee how to create one but as for usage the only text I can see is "Querying =
the PCP server to get the description text of an existing mapping is out of=
 scope." I think that the document should provide information about the pur=
pose of this option.

[Med] The main usage is for a user to associate a textual description with =
a mapping. This is captured by this text "   This option can be used by a u=
ser (or an application) to indicate a
   description associated with a given mapping such as "FTP server", "My
   remote access to my CP router", "Camera", "Network attached storage
   serve", etc.

"

[Roni Even] This is motivation but it is not clear why the user does it if =
no one can see it or does anything with it. It is kept on the server but no=
t used by anyone?


Nits/editorial comments:

 1.  The IANA section should provide enough information to fill the registr=
y http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options
[Med] Required information as per RFC6887 is provided in http://tools.ietf.=
org/html/draft-ietf-pcp-description-option-03#section-2.
[Roni Even] So section 5 should point to the definition is section 2



--_000_94C682931C08B048B7A8645303FDC9F36F473608DFPUEXCB1Bnante_
Content-Type: text/html; charset="iso-8859-1"
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=3Diso-8859-1"><meta name=3DGenerator content=3D"Micr=
osoft 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;}
@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:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	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:"Texte brut Car";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:"Courier New";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle32
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:#993366;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1954749651;
	mso-list-template-ids:412145204;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;line-height:115%;font-family:"Courier New";color:#993366'>R=
e-,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0=
pt;line-height:115%;font-family:"Courier New";color:#993366'>The descriptio=
n is used by the entity managing the PCP server. The document does not elab=
orate on such usage as this is deployment-specific: e.g., =A0(1) it can be =
used as =A0helper to clean the mapping table, (2) in some deployments that =
make use of a portal to instruct pcp mappings, this option can be used to s=
tore a subscriber-identifier, etc. We can add some text if you think this i=
s useful to be mentioned in the document.<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:10.0pt;line-height:115%;font-family:"Cour=
ier New";color:#993366'>For the second point, I updated Section 5 with a po=
inter to Section 2. Thanks.<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";color=
:#993366'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'=
font-size:10.0pt;line-height:115%;font-family:"Courier New";color:#993366'>=
Med<o:p></o:p></span></p><div style=3D'border:none;border-left:solid blue 1=
.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-top:s=
olid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal style=3D=
'margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><b><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</span></b=
><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni E=
ven [mailto:ron.even.tlv@gmail.com] <br><b>Envoy=E9&nbsp;:</b> lundi 27 jan=
vier 2014 10:31<br><b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; draft-ietf-=
pcp-description-option.all@tools.ietf.org<br><b>Cc&nbsp;:</b> ietf@ietf.org=
; gen-art@ietf.org<br><b>Objet&nbsp;:</b> RE: Gen-ART LC review of draft-ie=
tf-pcp-description-option-03<o:p></o:p></span></p></div></div><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'color:#1F4=
97D'>Hi Med, <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'colo=
r:#1F497D'>Inline<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'=
color:#1F497D'>Roni<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;bo=
rder-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'bo=
rder:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p clas=
s=3DMsoNormal style=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-height:=
normal'><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif=
"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sa=
ns-serif"'> <a href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucada=
ir@orange.com</a> [<a href=3D"mailto:mohamed.boucadair@orange.com">mailto:m=
ohamed.boucadair@orange.com</a>] <br><b>Sent:</b> 27 January, 2014 10:31 AM=
<br><b>To:</b> Roni Even; <a href=3D"mailto:draft-ietf-pcp-description-opti=
on.all@tools.ietf.org">draft-ietf-pcp-description-option.all@tools.ietf.org=
</a><br><b>Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a h=
ref=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> RE:=
 Gen-ART LC review of draft-ietf-pcp-description-option-03<o:p></o:p></span=
></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNo=
rmal><span style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Dear Roni,<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";co=
lor:#1F497D'>Thank you for the review. <o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:10.0pt;line-height:115%;font-family:"Courie=
r New";color:#1F497D'>Please see inline.<o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:10.0pt;line-height:115%;font-family:"Couri=
er New";color:#1F497D'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";co=
lor:#1F497D'>Med<o:p></o:p></span></p><div style=3D'border:none;border-left=
:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none=
;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNo=
rmal style=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><=
b><span lang=3DFR style=3D'font-size:10.0pt;font-family:"Tahoma","sans-seri=
f"'>De&nbsp;:</span></b><span lang=3DFR style=3D'font-size:10.0pt;font-fami=
ly:"Tahoma","sans-serif"'> Roni Even [<a href=3D"mailto:ron.even.tlv@gmail.=
com">mailto:ron.even.tlv@gmail.com</a>] <br><b>Envoy=E9&nbsp;:</b> dimanche=
 26 janvier 2014 09:13<br><b>=C0&nbsp;:</b> <a href=3D"mailto:draft-ietf-pc=
p-description-option.all@tools.ietf.org">draft-ietf-pcp-description-option.=
all@tools.ietf.org</a><br><b>Cc&nbsp;:</b> <a href=3D"mailto:ietf@ietf.org"=
>ietf@ietf.org</a>; <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a=
><br><b>Objet&nbsp;:</b> Gen-ART LC review of draft-ietf-pcp-description-op=
tion-03<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span lang=3D=
FR><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><a name=3D"OLE_LINK2"><=
/a><a name=3D"OLE_LINK1"></a>I am the assigned Gen-ART reviewer for this dr=
aft. 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 style=
=3D'margin-bottom:0cm;margin-bottom:.0001pt'>Document:&nbsp; <span style=3D=
'font-size:10.5pt;line-height:115%;font-family:"Courier New"'>draft-ietf-pc=
p-description-option-03<o:p></o:p></span></p><p class=3DMsoPlainText style=
=3D'margin-bottom:0cm;margin-bottom:.0001pt'>Reviewer: Roni Even<o:p></o:p>=
</p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-bottom:.0001p=
t'>Review Date:2014&#8211;1-26<o:p></o:p></p><p class=3DMsoPlainText style=
=3D'margin-bottom:0cm;margin-bottom:.0001pt'>IETF LC End Date: 2014&#8211;2=
-4<o:p></o:p></p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-=
bottom:.0001pt'>IESG Telechat date: <o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p c=
lass=3DMsoPlainText style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>Summa=
ry: This draft is almost ready for publication as a standard track RFC.<o:p=
></o:p></p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-bottom=
:.0001pt'><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText style=3D'margin-bott=
om:0cm;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>Major issues:<o:p></o:p><=
/p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-bottom:.0001pt=
'><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;m=
argin-bottom:.0001pt'>Minor issues:<o:p></o:p></p><p class=3DMsoPlainText s=
tyle=3D'margin-bottom:0cm;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p cl=
ass=3DMsoPlainText style=3D'mso-margin-top-alt:0cm;margin-right:0cm;margin-=
bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt;text-indent:-18.0pt;mso=
-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>=
1.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; </span></span><![endif]>I am not sure what the use of the &#8220;d=
escription&#8221; option is. I can see how to create one but as for usage t=
he only text I can see is &#8220;Querying the PCP server to get the descrip=
tion text of an existing mapping is out of scope.&#8221; I think that the d=
ocument should provide information about the purpose of this option.<o:p></=
o:p></p><pre style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";color:=
#1F497D'>[Med] The main usage is for a user to associate a textual descript=
ion with a mapping. This is captured by this text &#8220;</span></i></b><sp=
an style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New"'>&n=
bsp;&nbsp; This option can be used by a user (or an application) to indicat=
e a<o:p></o:p></span></pre><p class=3DMsoNormal style=3D'margin-bottom:0cm;=
margin-bottom:.0001pt;line-height:normal'><span style=3D'font-size:10.0pt;f=
ont-family:"Courier New"'>&nbsp;&nbsp; description associated with a given =
mapping such as &quot;FTP server&quot;, &quot;My<o:p></o:p></span></p><p cl=
ass=3DMsoNormal style=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-heigh=
t:normal'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;=
&nbsp; remote access to my CP router&quot;, &quot;Camera&quot;, &quot;Netwo=
rk attached storage<o:p></o:p></span></p><p class=3DMsoNormal style=3D'marg=
in-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><span style=3D'font=
-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; serve&quot;, etc.<o:p>=
</o:p></span></p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-=
bottom:.0001pt'><b><i><span style=3D'font-size:10.0pt;line-height:115%;font=
-family:"Courier New";color:#1F497D'>&#8221;<o:p></o:p></span></i></b></p><=
p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><b=
><i><span style=3D'color:#1F497D'>[Roni Even] </span></i></b><span style=3D=
'color:#1F497D'>This is motivation but it is not clear why the user does it=
 if no one can see it or does anything with it. It is kept on the server bu=
t not used by anyone?<o:p></o:p></span></p><p class=3DMsoPlainText style=3D=
'margin-bottom:0cm;margin-bottom:.0001pt'><span style=3D'color:#1F497D'><o:=
p>&nbsp;</o:p></span></p><p class=3DMsoNormal>Nits/editorial comments:<o:p>=
</o:p></p><ol style=3D'margin-top:0cm' start=3D1 type=3D1><li class=3DMsoNo=
rmal style=3D'mso-list:l1 level1 lfo5'>The IANA section should provide enou=
gh information to fill the registry <a href=3D"http://www.iana.org/assignme=
nts/pcp-parameters/pcp-parameters.xml#options">http://www.iana.org/assignme=
nts/pcp-parameters/pcp-parameters.xml#options</a> <o:p></o:p></li></ol><p c=
lass=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;line-height:115%;fon=
t-family:"Courier New";color:#1F497D'>[Med] Required information as per RFC=
6887 is provided in <a href=3D"http://tools.ietf.org/html/draft-ietf-pcp-de=
scription-option-03#section-2">http://tools.ietf.org/html/draft-ietf-pcp-de=
scription-option-03#section-2</a>. <o:p></o:p></span></i></b></p><p class=
=3DMsoNormal><b><i><span style=3D'color:#1F497D'>[Roni Even] </span></i></b=
><span style=3D'color:#1F497D'>So section 5 should point to the definition =
is section 2<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color=
:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p></div></div></div></div></body></html>=

--_000_94C682931C08B048B7A8645303FDC9F36F473608DFPUEXCB1Bnante_--

From ron.even.tlv@gmail.com  Mon Jan 27 02:05:55 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFFF1A01DE; Mon, 27 Jan 2014 02:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrNmtDIo6_W8; Mon, 27 Jan 2014 02:05:52 -0800 (PST)
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 2E4AA1A01D2; Mon, 27 Jan 2014 02:05:52 -0800 (PST)
Received: by mail-ee0-f48.google.com with SMTP id t10so2127223eei.7 for <multiple recipients>; Mon, 27 Jan 2014 02:05:49 -0800 (PST)
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:thread-index:content-language; bh=dIl1Z/B8WMVRLn4+g0iy9AJ4MpetQpHGIls3eP54Tg4=; b=K+KZPoX3b4K/PgzZozsDlBrWDT4wjbz1z2QF9/3CQ/jdM4uVafwMvNPI/4GHa4+xwz HXj/0iJL6esLIALbi8kJ8z6+4JL+QH9JbfXu5XHqcIKrXUMSyWr6ZUrnBDLKqBlZKuoj DqE4zkHq5YbQYHwXDKjAzIcsctbglEltRj8vgphyW6qVWssz8JPG7mhWUuatWEh7nWXw mEsrrxCiv7yuMD+GHCFGvCmKE6mZs9YbMHUj1uDh+UjcFqdLVlQVLE21wFnCuNnzJe1O xAJCJrmQ6MjJI9uXOlzVlPmpkFlRrj5be4vbxAOOA1I7FM1E53tA8eIR+X2vThsOQvBs Q9mg==
X-Received: by 10.14.211.131 with SMTP id w3mr17084233eeo.7.1390817149571; Mon, 27 Jan 2014 02:05:49 -0800 (PST)
Received: from RoniE ([109.66.49.55]) by mx.google.com with ESMTPSA id o13sm40402995eex.19.2014.01.27.02.05.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 27 Jan 2014 02:05:49 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Reinaldo Penno \(repenno\)'" <repenno@cisco.com>, <mohamed.boucadair@orange.com>, <draft-ietf-pcp-description-option.all@tools.ietf.org>
References: <033d01cf1b42$854c10e0$8fe432a0$@gmail.com> <CF0B68F0.8395%repenno@cisco.com>
In-Reply-To: <CF0B68F0.8395%repenno@cisco.com>
Date: Mon, 27 Jan 2014 12:02:01 +0200
Message-ID: <035301cf1b46$d54ba980$7fe2fc80$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0354_01CF1B57.98D67550"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQCBFcQxKd1jXqufJNTVIZgvX5PLAp00YNqg
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-pcp-description-option-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 10:05:55 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0354_01CF1B57.98D67550
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

This should be stated and I assume that it is not for standardization =
but
not clear why the entity operating the PCP server needs it, is it =
described
in another document.

I am curious why querying the PCP server is =93out of scope=94 and not =
is =93for
further work=94.

Roni

=20

From: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]=20
Sent: 27 January, 2014 11:39 AM
To: Roni Even; mohamed.boucadair@orange.com;
draft-ietf-pcp-description-option.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: Re: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Hi,

=20

The idea is that it can be seen by the entity operating the PCP Server.=20

=20

Thanks,

=20

From: Roni Even <ron.even.tlv@gmail.com>
Date: Monday, January 27, 2014 at 1:31 AM
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>,
"draft-ietf-pcp-description-option.all@tools.ietf.org"
<draft-ietf-pcp-description-option.all@tools.ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" =
<gen-art@ietf.org>
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03
Resent-From: <draft-alias-bounces@tools.ietf.org>
Resent-To: <dthaler@microsoft.com>, <dwing@cisco.com>,
"mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Cisco
Employee <repenno@cisco.com>, <ted.lemon@nominum.com>
Resent-Date: Monday, January 27, 2014 at 1:35 AM

=20

Hi Med,=20

Inline

Roni

=20

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

Sent: 27 January, 2014 10:31 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Dear Roni,

Thank you for the review.=20

Please see inline.

Cheers,

Med

De : Roni Even [mailto:ron.even.tlv@gmail.com]=20
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

=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-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014=961-26

IETF LC End Date: 2014=962-4

IESG Telechat date:=20

=20

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

=20

=20

Major issues:

=20

Minor issues:

=20

1.       I am not sure what the use of the =93description=94 option is. =
I can
see how to create one but as for usage the only text I can see is =
=93Querying
the PCP server to get the description text of an existing mapping is out =
of
scope.=94 I think that the document should provide information about the
purpose of this option.

[Med] The main usage is for a user to associate a textual description =
with a
mapping. This is captured by this text =93   This option can be used by =
a user
(or an application) to indicate a

   description associated with a given mapping such as "FTP server", "My

   remote access to my CP router", "Camera", "Network attached storage

   serve", etc.

=94

[Roni Even] This is motivation but it is not clear why the user does it =
if
no one can see it or does anything with it. It is kept on the server but =
not
used by anyone?

=20

Nits/editorial comments:

1.	The IANA section should provide enough information to fill the
registry
http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options=
=20

[Med] Required information as per RFC6887 is provided in
http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2=
.=20

[Roni Even] So section 5 should point to the definition is section 2

=20

=20


------=_NextPart_000_0354_01CF1B57.98D67550
Content-Type: text/html;
	charset="ISO-8859-1"
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=3Diso-8859-1"><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:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	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";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:"Courier New";}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	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";}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle30
	{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;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 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:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 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;}
@list l2
	{mso-list-id:1808356015;
	mso-list-template-ids:-1385152000;}
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><span =
style=3D'color:#1F497D'>Hi,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>This should be stated =
and I assume that it is not for standardization but not clear why the =
entity operating the PCP server needs it, is it described in another =
document.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>I am curious why querying the PCP server is =
&#8220;out of scope&#8221; and not is &#8220;for further =
work&#8221;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Reinaldo Penno (repenno) [mailto:repenno@cisco.com] <br><b>Sent:</b> 27 =
January, 2014 11:39 AM<br><b>To:</b> Roni Even; =
mohamed.boucadair@orange.com; =
draft-ietf-pcp-description-option.all@tools.ietf.org<br><b>Cc:</b> =
ietf@ietf.org; gen-art@ietf.org<br><b>Subject:</b> Re: Gen-ART LC review =
of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'>Hi,<o:p></o:p></s=
pan></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'>The idea is that =
it can be seen by the entity operating the PCP =
Server.&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'>Thanks,<o:p></o:p=
></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'color:black'>From: </span></b><span style=3D'color:black'>Roni =
Even &lt;<a =
href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>&gt;<br>=
<b>Date: </b>Monday, January 27, 2014 at 1:31 AM<br><b>To: </b>&quot;<a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a>&quot; &lt;<a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a>&gt;, &quot;<a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a>&quot; &lt;<a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a>&gt;<br><b>Cc: =
</b>&quot;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&quot; =
&lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, &quot;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;<br><b>Subject: =
</b>RE: Gen-ART LC review of =
draft-ietf-pcp-description-option-03<br><b>Resent-From: </b>&lt;<a =
href=3D"mailto:draft-alias-bounces@tools.ietf.org">draft-alias-bounces@to=
ols.ietf.org</a>&gt;<br><b>Resent-To: </b>&lt;<a =
href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com</a>&gt;, =
&lt;<a href=3D"mailto:dwing@cisco.com">dwing@cisco.com</a>&gt;, &quot;<a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a>&quot; &lt;<a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a>&gt;, Cisco Employee &lt;<a =
href=3D"mailto:repenno@cisco.com">repenno@cisco.com</a>&gt;, &lt;<a =
href=3D"mailto:ted.lemon@nominum.com">ted.lemon@nominum.com</a>&gt;<br><b=
>Resent-Date: </b>Monday, January 27, 2014 at 1:35 =
AM<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div><div><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Med, </span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Inline</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
 <a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a> [<a =
href=3D"mailto:mohamed.boucadair@orange.com">mailto:mohamed.boucadair@ora=
nge.com</a>] <br><b>Sent:</b> 27 January, 2014 10:31 AM<br><b>To:</b> =
Roni Even; <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc:</b> <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
RE: Gen-ART LC review of =
draft-ietf-pcp-description-option-03</span><span =
style=3D'color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Dear Roni,</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Thank you for the review. </span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Please see inline.</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Cheers,</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Med</span><span =
style=3D'color:black'><o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
De&nbsp;:</span></b><span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
 Roni Even [<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Envoy=E9&nbsp;:</b> dimanche 26 janvier 2014 =
09:13<br><b>=C0&nbsp;:</b> <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc&nbsp;:</b> =
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Objet&nbsp;:<=
/b> Gen-ART LC review of =
draft-ietf-pcp-description-option-03</span><span =
style=3D'color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DFR =
style=3D'color:black'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a><span =
style=3D'color:black'>I am the assigned Gen-ART reviewer for this draft. =
For background on Gen-ART, please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:black'>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Document:&nbsp; </span><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Courier =
New";color:black'>draft-ietf-pcp-description-option-03</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Reviewer: Roni Even<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Review =
Date:2014&#8211;1-26<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>IETF LC End Date: =
2014&#8211;2-4<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>IESG Telechat date: <o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Summary: This draft is almost ready for =
publication as a standard track RFC.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Major issues:<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Minor issues:<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'color:black'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'color:black'>I am not sure what the use of the =
&#8220;description&#8221; option is. I can see how to create one but as =
for usage the only text I can see is &#8220;Querying the PCP server to =
get the description text of an existing mapping is out of scope.&#8221; =
I think that the document should provide information about the purpose =
of this option.<o:p></o:p></span></p><pre><b><i><span =
style=3D'color:#1F497D'>[Med] The main usage is for a user to associate =
a textual description with a mapping. This is captured by this text =
&#8220;</span></i></b><span style=3D'color:black'>&nbsp;&nbsp; This =
option can be used by a user (or an application) to indicate =
a<o:p></o:p></span></pre><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>&nbsp;&nbsp; description associated with a given =
mapping such as &quot;FTP server&quot;, &quot;My</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>&nbsp;&nbsp; remote access to my CP router&quot;, =
&quot;Camera&quot;, &quot;Network attached storage</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>&nbsp;&nbsp; serve&quot;, etc.</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>&#8221;</span></i></b><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'color:#1F497D'>[Roni Even] </span></i></b><span =
style=3D'color:#1F497D'>This is motivation but it is not clear why the =
user does it if no one can see it or does anything with it. It is kept =
on the server but not used by anyone?</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:#1F497D'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:black'>Nits/editorial comments:<o:p></o:p></span></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'color:black;mso-list:l1 level1 lfo5'>The IANA section should =
provide enough information to fill the registry <a =
href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml=
#options">http://www.iana.org/assignments/pcp-parameters/pcp-parameters.x=
ml#options</a> <o:p></o:p></li></ol><p class=3DMsoNormal><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>[Med] Required information as per RFC6887 is =
provided in <a =
href=3D"http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#s=
ection-2">http://tools.ietf.org/html/draft-ietf-pcp-description-option-03=
#section-2</a>. </span></i></b><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoNormal><b><i><span style=3D'color:#1F497D'>[Roni Even] =
</span></i></b><span style=3D'color:#1F497D'>So section 5 should point =
to the definition is section 2</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p></div></div></div></div=
></div></div></body></html>
------=_NextPart_000_0354_01CF1B57.98D67550--


From ron.even.tlv@gmail.com  Mon Jan 27 03:34:22 2014
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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 427031A01E8; Mon, 27 Jan 2014 03:34:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZC22RVCiZgjA; Mon, 27 Jan 2014 03:34:18 -0800 (PST)
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 8D5831A01E4; Mon, 27 Jan 2014 03:34:17 -0800 (PST)
Received: by mail-ee0-f51.google.com with SMTP id b57so2199343eek.38 for <multiple recipients>; Mon, 27 Jan 2014 03:34:15 -0800 (PST)
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:thread-index:content-language; bh=pHb8s3pVsDXVxNNIHuXFf9iYCvfCD+jjspbwRHMZrNE=; b=WeLp9V62jEOKqmn0gKjcMGdjcqkwopiZjyAFRWqygdcu4AKJLhDW3rWOjHro3tqOWW 9kJlD13+OoRZufKwgFfBFUkFfwIeUXPRNaDhwzix4j8vHrmZPsvl/PHi85hG93S/dMEn RUcPbGuPAvpBm4oxwVZZIIGRZ9ievC/fyryZTMfQWsGQgYPEOKs3QnwaFt4K/sUI0i9Y ygYt1KHdjV7Ji2hstgmaXFtKwWlpW6mFDSBGpRlDVZgoj56X5Sj3STbsKV09puDUHbs5 ZTBe+dl53tcJAd5HHnGZ/yWzVeF6ZxTxYbfhvx1YWw2taS8u5H2Xu4FioTokmAjq0ryl ITVQ==
X-Received: by 10.14.6.129 with SMTP id 1mr274364een.99.1390822454872; Mon, 27 Jan 2014 03:34:14 -0800 (PST)
Received: from RoniE ([109.66.49.55]) by mx.google.com with ESMTPSA id 46sm41351623ees.4.2014.01.27.03.34.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 27 Jan 2014 03:34:13 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <mohamed.boucadair@orange.com>, <draft-ietf-pcp-description-option.all@tools.ietf.org>
References: <02db01cf1a6e$62eb8280$28c28780$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr> <033d01cf1b42$854c10e0$8fe432a0$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F473608DF@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36F473608DF@PUEXCB1B.nanterre.francetelecom.fr>
Date: Mon, 27 Jan 2014 13:30:24 +0200
Message-ID: <036401cf1b53$2ec6cdd0$8c546970$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0365_01CF1B63.F2517290"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF6/p6mIwEjavahOcoGuw0nlckk9wI8szcDAx3Ucj0Btw/0U5sIHEGg
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-pcp-description-option-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 11:34:22 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0365_01CF1B63.F2517290
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Med,

I think some text will be useful

Roni

=20

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

Sent: 27 January, 2014 11:55 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Re-,

The description is used by the entity managing the PCP server. The =
document
does not elaborate on such usage as this is deployment-specific: e.g.,  =
(1)
it can be used as  helper to clean the mapping table, (2) in some
deployments that make use of a portal to instruct pcp mappings, this =
option
can be used to store a subscriber-identifier, etc. We can add some text =
if
you think this is useful to be mentioned in the document.

For the second point, I updated Section 5 with a pointer to Section 2.
Thanks.

Cheers,

Med

De : Roni Even [mailto:ron.even.tlv@gmail.com]=20
Envoy=E9 : lundi 27 janvier 2014 10:31
=C0 : BOUCADAIR Mohamed IMT/OLN;
draft-ietf-pcp-description-option.all@tools.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Hi Med,=20

Inline

Roni

=20

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

Sent: 27 January, 2014 10:31 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Dear Roni,

Thank you for the review.=20

Please see inline.

Cheers,

Med

De : Roni Even [mailto:ron.even.tlv@gmail.com]=20
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

=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-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014=961-26

IETF LC End Date: 2014=962-4

IESG Telechat date:=20

=20

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

=20

=20

Major issues:

=20

Minor issues:

=20

1.       I am not sure what the use of the =93description=94 option is. =
I can
see how to create one but as for usage the only text I can see is =
=93Querying
the PCP server to get the description text of an existing mapping is out =
of
scope.=94 I think that the document should provide information about the
purpose of this option.

[Med] The main usage is for a user to associate a textual description =
with a
mapping. This is captured by this text =93   This option can be used by =
a user
(or an application) to indicate a

   description associated with a given mapping such as "FTP server", "My

   remote access to my CP router", "Camera", "Network attached storage

   serve", etc.

=94

[Roni Even] This is motivation but it is not clear why the user does it =
if
no one can see it or does anything with it. It is kept on the server but =
not
used by anyone?

=20

Nits/editorial comments:

1.	The IANA section should provide enough information to fill the
registry
http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options=
=20

[Med] Required information as per RFC6887 is provided in
http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2=
.=20

[Roni Even] So section 5 should point to the definition is section 2

=20

=20


------=_NextPart_000_0365_01CF1B63.F2517290
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<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 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:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	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";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	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";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:"Courier New";}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	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";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
p.Textedebulles, li.Textedebulles, div.Textedebulles
	{mso-style-name:"Texte de bulles";
	mso-style-link:"Texte de bulles Car";
	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";}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#993366;}
span.EmailStyle33
	{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;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 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:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 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;}
@list l2
	{mso-list-id:1517378766;
	mso-list-template-ids:1165285046;}
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><span =
style=3D'color:#1F497D'>Hi Med,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I think some text will =
be useful<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com] =
<br><b>Sent:</b> 27 January, 2014 11:55 AM<br><b>To:</b> Roni Even; =
draft-ietf-pcp-description-option.all@tools.ietf.org<br><b>Cc:</b> =
ietf@ietf.org; gen-art@ietf.org<br><b>Subject:</b> RE: Gen-ART LC review =
of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#993366'>Re-,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#993366'>The description is used by the entity managing the =
PCP server. The document does not elaborate on such usage as this is =
deployment-specific: e.g., &nbsp;(1) it can be used as &nbsp;helper to =
clean the mapping table, (2) in some deployments that make use of a =
portal to instruct pcp mappings, this option can be used to store a =
subscriber-identifier, etc. We can add some text if you think this is =
useful to be mentioned in the document.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#993366'>For the second point, I updated Section 5 with a =
pointer to Section 2. Thanks.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#993366'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#993366'>Med<o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</s=
pan></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni Even =
[<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Envoy=E9&nbsp;:</b> lundi 27 janvier 2014 =
10:31<br><b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc&nbsp;:</b> =
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Objet&nbsp;:<=
/b> RE: Gen-ART LC review of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Med, <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Inline<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a> [<a =
href=3D"mailto:mohamed.boucadair@orange.com">mailto:mohamed.boucadair@ora=
nge.com</a>] <br><b>Sent:</b> 27 January, 2014 10:31 AM<br><b>To:</b> =
Roni Even; <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc:</b> <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
RE: Gen-ART LC review of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Dear Roni,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Thank you for the review. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Please see inline.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Med<o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</s=
pan></b><span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni Even =
[<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Envoy=E9&nbsp;:</b> dimanche 26 janvier 2014 =
09:13<br><b>=C0&nbsp;:</b> <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc&nbsp;:</b> =
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Objet&nbsp;:<=
/b> Gen-ART LC review of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DFR><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><a name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I =
am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Document:&nbsp; <span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Courier =
New"'>draft-ietf-pcp-description-option-03<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Reviewer: Roni =
Even<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Review =
Date:2014&#8211;1-26<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>IETF LC End Date: =
2014&#8211;2-4<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>IESG Telechat date: =
<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Summary: This draft is =
almost ready for publication as a standard track RFC.<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Major =
issues:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Minor =
issues:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>I am not sure what the =
use of the &#8220;description&#8221; option is. I can see how to create =
one but as for usage the only text I can see is &#8220;Querying the PCP =
server to get the description text of an existing mapping is out of =
scope.&#8221; I think that the document should provide information about =
the purpose of this option.<o:p></o:p></p><pre =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>[Med] The main usage is for a user to associate a =
textual description with a mapping. This is captured by this text =
&#8220;</span></i></b><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New"'>&nbsp;&nbsp; This option can be used by a user (or an application) =
to indicate a<o:p></o:p></span></pre><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
description associated with a given mapping such as &quot;FTP =
server&quot;, &quot;My<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
remote access to my CP router&quot;, &quot;Camera&quot;, &quot;Network =
attached storage<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
serve&quot;, etc.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>&#8221;<o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'color:#1F497D'>[Roni Even] </span></i></b><span =
style=3D'color:#1F497D'>This is motivation but it is not clear why the =
user does it if no one can see it or does anything with it. It is kept =
on the server but not used by anyone?<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal>Nits/editorial comments:<o:p></o:p></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l1 level1 lfo5'>The IANA section should provide enough =
information to fill the registry <a =
href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml=
#options">http://www.iana.org/assignments/pcp-parameters/pcp-parameters.x=
ml#options</a> <o:p></o:p></li></ol><p class=3DMsoNormal><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>[Med] Required information as per RFC6887 is =
provided in <a =
href=3D"http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#s=
ection-2">http://tools.ietf.org/html/draft-ietf-pcp-description-option-03=
#section-2</a>. <o:p></o:p></span></i></b></p><p =
class=3DMsoNormal><b><i><span style=3D'color:#1F497D'>[Roni Even] =
</span></i></b><span style=3D'color:#1F497D'>So section 5 should point =
to the definition is section 2<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div></div></bo=
dy></html>
------=_NextPart_000_0365_01CF1B63.F2517290--


From repenno@cisco.com  Mon Jan 27 01:38:51 2014
Return-Path: <repenno@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 932C91A011C; Mon, 27 Jan 2014 01:38:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.035
X-Spam-Level: 
X-Spam-Status: No, score=-10.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VV0_slMA765A; Mon, 27 Jan 2014 01:38:49 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id B64441A0117; Mon, 27 Jan 2014 01:38:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23400; q=dns/txt; s=iport; t=1390815527; x=1392025127; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=/PDkheEyah9yV21wccpxSltr10EWTKycXqUxebM/oVM=; b=ckcklDLGlDCWokqRwx/yAx9Cz1jk2eUwI532ccUbQffRA2FPThNCl8Pz Us77TfjggPL+9S1y2jx8LLyZaCtYVYboKvpxroIqRQqiiJcX0JJt6VYN8 QC48NA4P7NC9dyCEf9xPITWODoOsirFgHYn3EIwMboJL8U5asJDExqA8T w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkAHABwo5lKtJV2b/2dsb2JhbABZgkhEOFa0AIhTgQoWdIIlAQEBBC1MEgEIDgMDAQEBIQcoERQJCAEBBAENBQmHaAMRDcI8DYVWF4x3I4EqOBEGAYQ4BIVYkGOBbIEyiyuFQYMtgWlB
X-IronPort-AV: E=Sophos;i="4.95,728,1384300800"; d="scan'208,217";a="15747634"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-5.cisco.com with ESMTP; 27 Jan 2014 09:38:46 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0R9cjRb019913 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Jan 2014 09:38:46 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0123.003; Mon, 27 Jan 2014 03:38:45 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Roni Even <ron.even.tlv@gmail.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "draft-ietf-pcp-description-option.all@tools.ietf.org" <draft-ietf-pcp-description-option.all@tools.ietf.org>
Thread-Topic: Gen-ART LC review of draft-ietf-pcp-description-option-03
Thread-Index: Ac8ablfn3UbFfKwfSEyn6Pcjjhog/QAyx66AAA7VfwD//3wCgA==
Date: Mon, 27 Jan 2014 09:38:44 +0000
Message-ID: <CF0B68F0.8395%repenno@cisco.com>
In-Reply-To: <033d01cf1b42$854c10e0$8fe432a0$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.91.128]
Content-Type: multipart/alternative; boundary="_000_CF0B68F08395repennociscocom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 27 Jan 2014 04:44:19 -0800
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-pcp-description-option-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 09:38:51 -0000

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

Hi,

The idea is that it can be seen by the entity operating the PCP Server.

Thanks,

From: Roni Even <ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>>
Date: Monday, January 27, 2014 at 1:31 AM
To: "mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>" <mo=
hamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>, "draft-ie=
tf-pcp-description-option.all@tools.ietf.org<mailto:draft-ietf-pcp-descript=
ion-option.all@tools.ietf.org>" <draft-ietf-pcp-description-option.all@tool=
s.ietf.org<mailto:draft-ietf-pcp-description-option.all@tools.ietf.org>>
Cc: "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf.o=
rg>>, "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:=
gen-art@ietf.org>>
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03
Resent-From: <draft-alias-bounces@tools.ietf.org<mailto:draft-alias-bounces=
@tools.ietf.org>>
Resent-To: <dthaler@microsoft.com<mailto:dthaler@microsoft.com>>, <dwing@ci=
sco.com<mailto:dwing@cisco.com>>, "mohamed.boucadair@orange.com<mailto:moha=
med.boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.bou=
cadair@orange.com>>, Cisco Employee <repenno@cisco.com<mailto:repenno@cisco=
.com>>, <ted.lemon@nominum.com<mailto:ted.lemon@nominum.com>>
Resent-Date: Monday, January 27, 2014 at 1:35 AM

Hi Med,
Inline
Roni

From: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> [ma=
ilto:mohamed.boucadair@orange.com]
Sent: 27 January, 2014 10:31 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org<mailto:=
draft-ietf-pcp-description-option.all@tools.ietf.org>
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@ie=
tf.org>
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

Dear Roni,
Thank you for the review.
Please see inline.
Cheers,
Med
De : Roni Even [mailto:ron.even.tlv@gmail.com]
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org<mailto:draft-iet=
f-pcp-description-option.all@tools.ietf.org>
Cc : ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@i=
etf.org>
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.
Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document:  draft-ietf-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014=961-26

IETF LC End Date: 2014=962-4

IESG Telechat date:



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





Major issues:



Minor issues:



1.       I am not sure what the use of the =93description=94 option is. I c=
an see how to create one but as for usage the only text I can see is =93Que=
rying the PCP server to get the description text of an existing mapping is =
out of scope.=94 I think that the document should provide information about=
 the purpose of this option.

[Med] The main usage is for a user to associate a textual description with =
a mapping. This is captured by this text =93   This option can be used by a=
 user (or an application) to indicate a
   description associated with a given mapping such as "FTP server", "My
   remote access to my CP router", "Camera", "Network attached storage
   serve", etc.

=94

[Roni Even] This is motivation but it is not clear why the user does it if =
no one can see it or does anything with it. It is kept on the server but no=
t used by anyone?


Nits/editorial comments:

  1.  The IANA section should provide enough information to fill the regist=
ry http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#option=
s
[Med] Required information as per RFC6887 is provided in http://tools.ietf.=
org/html/draft-ietf-pcp-description-option-03#section-2.
[Roni Even] So section 5 should point to the definition is section 2



--_000_CF0B68F08395repennociscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <A71178D9E1B5CB489BEA10CF0E9BAC95@emea.cisco.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>Hi,</div>
<div><br>
</div>
<div>The idea is that it can be seen by the entity operating the PCP Server=
.&nbsp;</div>
<div><br>
</div>
<div>Thanks,</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>Roni Even &lt;<a href=3D"mail=
to:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Monday, January 27, 2014 at 1=
:31 AM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:mohamed=
.boucadair@orange.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=
=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&g=
t;, &quot;<a href=3D"mailto:draft-ietf-pcp-description-option.all@tools.iet=
f.org">draft-ietf-pcp-description-option.all@tools.ietf.org</a>&quot;
 &lt;<a href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org=
">draft-ietf-pcp-description-option.all@tools.ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:ietf@ie=
tf.org">ietf@ietf.org</a>&quot; &lt;<a href=3D"mailto:ietf@ietf.org">ietf@i=
etf.org</a>&gt;, &quot;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org=
</a>&quot; &lt;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;=
<br>
<span style=3D"font-weight:bold">Subject: </span>RE: Gen-ART LC review of d=
raft-ietf-pcp-description-option-03<br>
<span style=3D"font-weight:bold">Resent-From: </span>&lt;<a href=3D"mailto:=
draft-alias-bounces@tools.ietf.org">draft-alias-bounces@tools.ietf.org</a>&=
gt;<br>
<span style=3D"font-weight:bold">Resent-To: </span>&lt;<a href=3D"mailto:dt=
haler@microsoft.com">dthaler@microsoft.com</a>&gt;, &lt;<a href=3D"mailto:d=
wing@cisco.com">dwing@cisco.com</a>&gt;, &quot;<a href=3D"mailto:mohamed.bo=
ucadair@orange.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"m=
ailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt;,
 Cisco Employee &lt;<a href=3D"mailto:repenno@cisco.com">repenno@cisco.com<=
/a>&gt;, &lt;<a href=3D"mailto:ted.lemon@nominum.com">ted.lemon@nominum.com=
</a>&gt;<br>
<span style=3D"font-weight:bold">Resent-Date: </span>Monday, January 27, 20=
14 at 1:35 AM<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<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;}
@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-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	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";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	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";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:"Courier New";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle29
	{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;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 67698703 67698713 67698715 67698703 67698=
713 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:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 67698703 67698713 67698715 67698703 6769=
8713 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;}
@list l2
	{mso-list-id:2105032897;
	mso-list-template-ids:-1035336528;}
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]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Med, <o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Inline<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Roni<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:0in;margin-bottom:.0001pt;lin=
e-height:normal">
<b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;">From:<=
/span></b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;"=
>
<a href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.co=
m</a> [<a href=3D"mailto:mohamed.boucadair@orange.com">mailto:mohamed.bouca=
dair@orange.com</a>]
<br>
<b>Sent:</b> 27 January, 2014 10:31 AM<br>
<b>To:</b> Roni Even; <a href=3D"mailto:draft-ietf-pcp-description-option.a=
ll@tools.ietf.org">
draft-ietf-pcp-description-option.all@tools.ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a href=3D"m=
ailto:gen-art@ietf.org">
gen-art@ietf.org</a><br>
<b>Subject:</b> RE: Gen-ART LC review of draft-ietf-pcp-description-option-=
03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; line-height: 115%; f=
ont-family: 'Courier New'; color: rgb(31, 73, 125);">Dear Roni,<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; line-height: 115%; f=
ont-family: 'Courier New'; color: rgb(31, 73, 125);">Thank you for the revi=
ew.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; line-height: 115%; f=
ont-family: 'Courier New'; color: rgb(31, 73, 125);">Please see inline.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; line-height: 115%; f=
ont-family: 'Courier New'; color: rgb(31, 73, 125);">Cheers,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; line-height: 115%; f=
ont-family: 'Courier New'; color: rgb(31, 73, 125);">Med<o:p></o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:0in;margin-bottom:.0001pt;lin=
e-height:normal">
<b><span lang=3D"FR" style=3D"font-size: 10pt; font-family: Tahoma, sans-se=
rif;">De&nbsp;:</span></b><span lang=3D"FR" style=3D"font-size: 10pt; font-=
family: Tahoma, sans-serif;"> Roni Even [<a href=3D"mailto:ron.even.tlv@gma=
il.com">mailto:ron.even.tlv@gmail.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> dimanche 26 janvier 2014 09:13<br>
<b>=C0&nbsp;:</b> <a href=3D"mailto:draft-ietf-pcp-description-option.all@t=
ools.ietf.org">
draft-ietf-pcp-description-option.all@tools.ietf.org</a><br>
<b>Cc&nbsp;:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a hre=
f=3D"mailto:gen-art@ietf.org">
gen-art@ietf.org</a><br>
<b>Objet&nbsp;:</b> Gen-ART LC review of draft-ietf-pcp-description-option-=
03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><a name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>=
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq</a>&gt;.<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"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Document:&nbsp;
<span style=3D"font-size: 10.5pt; line-height: 115%; font-family: 'Courier =
New';">draft-ietf-pcp-description-option-03<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Reviewer: Roni Even<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Review Date:2014=961-26<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>IETF LC End Date: 2014=962-4<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>IESG Telechat date:
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Summary: This draft is almost ready for publication as a standard track RF=
C.<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Major issues:<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Minor issues:<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"mso-margin-top-alt:0in;margin-right:0in;=
margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<!--[if !supportLists]--><span style=3D"mso-list:Ignore">1.<span style=3D"f=
ont-style: normal; font-variant: normal; font-weight: normal; font-size: 7p=
t; line-height: normal; font-family: 'Times New Roman';">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>I am not sure what the=
 use of the =93description=94 option is. I can see how to create one but as=
 for usage the only text I can see is =93Querying the PCP server to get the=
 description text of an existing mapping
 is out of scope.=94 I think that the document should provide information a=
bout the purpose of this option.<o:p></o:p></p>
<pre><b><i><span style=3D"color:#1F497D">[Med] The main usage is for a user=
 to associate a textual description with a mapping. This is captured by thi=
s text =93</span></i></b>&nbsp;&nbsp; This option can be used by a user (or=
 an application) to indicate a<o:p></o:p></pre>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in;margin-bottom:.0001pt;lin=
e-height:normal">
<span style=3D"font-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; d=
escription associated with a given mapping such as &quot;FTP server&quot;, =
&quot;My<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in;margin-bottom:.0001pt;lin=
e-height:normal">
<span style=3D"font-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; r=
emote access to my CP router&quot;, &quot;Camera&quot;, &quot;Network attac=
hed storage<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in;margin-bottom:.0001pt;lin=
e-height:normal">
<span style=3D"font-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; s=
erve&quot;, etc.<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><b><i><span style=3D"font-size: 10pt; line-height: 115%; font-family: 'Cou=
rier New'; color: rgb(31, 73, 125);">=94<o:p></o:p></span></i></b></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><b><i><span style=3D"color:#1F497D">[Roni Even]
</span></i></b><span style=3D"color:#1F497D">This is motivation but it is n=
ot clear why the user does it if no one can see it or does anything with it=
. It is kept on the server but not used by anyone?<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<ol style=3D"margin-top:0in" start=3D"1" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo5">The IANA section =
should provide enough information to fill the registry
<a href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xm=
l#options">
http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options</=
a> <o:p>
</o:p></li></ol>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size: 10pt; line-height: 1=
15%; font-family: 'Courier New'; color: rgb(31, 73, 125);">[Med] Required i=
nformation as per RFC6887 is provided in
<a href=3D"http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#=
section-2">
http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2</=
a>. <o:p>
</o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Roni Even] </sp=
an></i></b><span style=3D"color:#1F497D">So section 5 should point to the d=
efinition is section 2<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_CF0B68F08395repennociscocom_--

From lear@cisco.com  Mon Jan 27 05:20:58 2014
Return-Path: <lear@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F15B1A020E; Mon, 27 Jan 2014 05:20:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfVPqbDkO5jQ; Mon, 27 Jan 2014 05:20:57 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 782CE1A020A; Mon, 27 Jan 2014 05:20:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3184; q=dns/txt; s=iport; t=1390828855; x=1392038455; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=z0yW11rgQCG4ugwACOvVUpM4Ma+Riefv+tmp1OKfZRo=; b=PVYiBNlNngqbMRMUmJnaSAGOVmsBFtP8p4hWO7dy9PsTj80DgG7H5gWi j8S7DD6dKfvRtKNbdTlowtqPPo3LQ61lbY9uJ0nbTQ55qAFIcTJTqMADu VGyGW/vcHA/+CP5r0USkjrHAZU4NoDEz13t/yZpV0g+nnJiUu2Q97yJTX A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8FAJdc5lKQ/khM/2dsb2JhbABZgww4g1O5WIENFnSCJQEBAQMBI1UBEAsUBAICBRYLAgIJAwIBAgErGgYBDAEHAQGHeQgNq1KcWheBKYtxgSBTB4JvgUkBA5gngTKQbIMuO4E1
X-IronPort-AV: E=Sophos;i="4.95,729,1384300800";  d="scan'208";a="3576971"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 27 Jan 2014 13:20:53 +0000
Received: from mctiny.local ([10.61.174.53]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0RDKqKK031965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 13:20:53 GMT
Message-ID: <52E65878.9030906@cisco.com>
Date: Mon, 27 Jan 2014 14:00:40 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>, "Alexey Melnikov (alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>, "dcridland@arcode.com" <dcridland@arcode.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>, "ietf@ietf.org" <ietf@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 13:20:58 -0000

Hi Dave,

First, thank you for your review.  I personally appreciate to the time
you put in to all of your reviews.

On 1/27/14, 3:06 AM, Black, David 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-qresync-rfc5162bis-09
> Reviewer: David L. Black
> Review Date: January 26, 2014
> IETF LC End Date: January 27, 2014
>
> Summary:
> This draft is basically ready for publication, but has minor issues that
> should be fixed before publication.
>
> This draft consolidates RFC 4551 (IMAP Conditional STORE) and RFC 5162
> (IMAP Quick Mailbox Resynchronization) into a single document and makes
> a few minor updates.  It also updates the command line length
> recommendation in RFC 2683 to support the longer command lines that
> can occur with these extensions.
>
> As this is an update, I checked the diffs against RFC 4551 and RFC 5162;
> they look reasonable.  I found one minor issue that should be relatively
> easy to address.
>
> Minor Issues:
>
> The command line length change in Section 4 applies to all IMAP commands,
> and hence affects old servers, including those that don't implement either
> of the extensions in this draft. That raises a backwards compatibility
> concern - what happens when a new client sends a > 1000 character command
> line to an old server that isn't expecting more than 1000 characters?

As the draft indicates, this is problematic for the two extensions in
question. We have discussed this limitation in the working group, and
nobody seems to be concerned.  That's due to two factors, I think:
first, RFC 2683 is not normative (informational).  I am unaware of any
strict line length limitation in RFC 3501, for instance.  Instead, there
is a requirement for strict syntax parsing.  If the client blows it in
any way, the server SHOULD return an error with a BAD response.

This having been said, while the working group has discussed this
matter, it would be good to hear any additional voices of concern, in
the interests of interoperability.

This takes us to your next point:

>
> One possibility would be to apply the larger length recommendation only
> after the client determines that the server supports at least one of
> these extensions.
>
> Nits/editorial comments:
>
> The update to RFC 2683 would be easier to find from the table of contents
> if the title of Section 4 were changed to "Long Command Lines (Update to
> RFC 2683)".
>
> idnits 2.13.01 got confused by the command line examples, and flagged a
> downref:
>
>   ** Downref: Normative reference to an Informational RFC: RFC 2683
>
> That downref appears to be ok and intended, as noted in the shepherd's
> writeup.

This will be addressed in a forthcoming update.  Barry has "educated" us
that really this is NOT an update to RFC2683, where the advice given in
that document is superceded by a specific option.  As such, this error
will evaporate.



From alan.b.johnston@gmail.com  Mon Jan 27 05:29:04 2014
Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B04641A0213; Mon, 27 Jan 2014 05:29:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fukego9Uc0EO; Mon, 27 Jan 2014 05:29:02 -0800 (PST)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6F21A020E; Mon, 27 Jan 2014 05:29:02 -0800 (PST)
Received: by mail-pd0-f172.google.com with SMTP id p10so5717236pdj.31 for <multiple recipients>; Mon, 27 Jan 2014 05:29:00 -0800 (PST)
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=AEqX5waXIlRUAG/JnS/qqraFYulwql7A1AFeryhnnoU=; b=gK+ZCXSKAS63gpeZsTnfVcSY70/g8aLOnmmbAHxXJ4DTuM93JWZLGOEaJ41m3NK19E ifP13O3sJX/qdiyNIm3nzAgTnIV0qHKyuIm+Gk5icDtOiv8Zah0FjJf7SF13tb2IACGJ gmb6BImzwC88UW67YrLSv8eFUCd3jD3rf27BoDvJl7ydthzEcURNWYCPNgEmj9h2ayMz 9SQLQLm6pTlaSZhrGgPUGX2N6aiiDd+Ewxzzh1OA4UHv1T+6z5QGNfO49gtuElt1frHO wEKW+nJgHr04EIA2+RZLcra6EGA6nddQ4Hz+3MP1DdfGw4M5iwg6WDxkJdAsbIPxC/Zz /qJQ==
MIME-Version: 1.0
X-Received: by 10.66.188.203 with SMTP id gc11mr29882894pac.63.1390829334072;  Mon, 27 Jan 2014 05:28:54 -0800 (PST)
Received: by 10.68.168.132 with HTTP; Mon, 27 Jan 2014 05:28:53 -0800 (PST)
In-Reply-To: <519920BA.9040308@joelhalpern.com>
References: <5195550A.3000608@nostrum.com> <519920BA.9040308@joelhalpern.com>
Date: Mon, 27 Jan 2014 07:28:53 -0600
Message-ID: <CAKhHsXHpOKaCb5M1j=H=j8z+dDsWtuKXmK_vFE9qsKSKv3mAEQ@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=047d7bf0c66466bdf204f0f3b0b0
Cc: gen-art@ietf.org, draft-ietf-cuss-sip-uui-all@tools.ietf.org, "cuss@ietf.org" <cuss@ietf.org>
Subject: Re: [Gen-art] [cuss]  review: draft-ietf-cuss-sip-uui-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 13:29:04 -0000

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

Joel,

Thanks for your review of the document.  We have made the changes you
suggested in your review in the -12 version.

     http://www.ietf.org/id/draft-ietf-cuss-sip-uui-12.txt

Let us know if there are any other issues.

- Alan -


On Sun, May 19, 2013 at 1:58 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
>
> <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-cuss-sip-uui-10
>     A Mechanism for Transporting User to User
>         Call Control Information in SIP
> Reviewer: Joel M. Halpern
> Review Date: 19-May-2013
> IETF LC End Date: 29-May-2013
> IESG Telechat date: N/A
>
> Summary: This document is nearly ready for publication as a Proposed
> Standard
>
> Major issues:
>
> Minor issues:
>     The requirements discussions for redirection and referral (second
> paragraph of section 3, in regards REQ-3) includes what appears to be
> normative requirements on redirecting devices.
> a) This would seem to belong in section 4 on Normative Definition.
> b) It would seem that there ought to be some discussion of what happens
> with redirecting devices that do not understand this new UUI. (I presume
> things work, but I don't see how.)
>
> Nits/editorial comments:
>     In section 8.2, given that this is a WG document, should the "the
> authors believe" actually be "the WG believes"?  Or even, given IETF rough
> consensus on this document, "the IETF believes"?
> _______________________________________________
> cuss mailing list
> cuss@ietf.org
> https://www.ietf.org/mailman/listinfo/cuss
>

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

<div dir=3D"ltr">Joel,<div><br></div><div>Thanks for your review of the doc=
ument. =A0We have made the changes you suggested in your review in the -12 =
version. =A0</div><div><br></div><div>=A0 =A0 =A0<a href=3D"http://www.ietf=
.org/id/draft-ietf-cuss-sip-uui-12.txt">http://www.ietf.org/id/draft-ietf-c=
uss-sip-uui-12.txt</a></div>
<div><br></div><div>Let us know if there are any other issues.</div><div><b=
r></div><div>- Alan -</div><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Sun, May 19, 2013 at 1:58 PM, Joel M. Halpern <span dir=3D=
"ltr">&lt;<a href=3D"mailto:jmh@joelhalpern.com" target=3D"_blank">jmh@joel=
halpern.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">I am the assigned Gen-ART reviewer for this draft. For bac=
kground on<br>

Gen-ART, please see the FAQ at<br>
<br>
&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" tar=
get=3D"_blank">http://wiki.tools.ietf.org/<u></u>area/gen/trac/wiki/GenArtf=
aq</a>&gt;.<br>
<br>
Please resolve these comments along with any other Last Call comments<br>
you may receive.<br>
<br>
Document: draft-ietf-cuss-sip-uui-10<br>
=A0 =A0 A Mechanism for Transporting User to User<br>
=A0 =A0 =A0 =A0 Call Control Information in SIP<br>
Reviewer: Joel M. Halpern<br>
Review Date: 19-May-2013<br>
IETF LC End Date: 29-May-2013<br>
IESG Telechat date: N/A<br>
<br>
Summary: This document is nearly ready for publication as a Proposed Standa=
rd<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
=A0 =A0 The requirements discussions for redirection and referral (second p=
aragraph of section 3, in regards REQ-3) includes what appears to be normat=
ive requirements on redirecting devices.<br>
a) This would seem to belong in section 4 on Normative Definition.<br>
b) It would seem that there ought to be some discussion of what happens wit=
h redirecting devices that do not understand this new UUI. (I presume thing=
s work, but I don&#39;t see how.)<br>
<br>
Nits/editorial comments:<br>
=A0 =A0 In section 8.2, given that this is a WG document, should the &quot;=
the authors believe&quot; actually be &quot;the WG believes&quot;? =A0Or ev=
en, given IETF rough consensus on this document, &quot;the IETF believes&qu=
ot;?<br>

______________________________<u></u>_________________<br>
cuss mailing list<br>
<a href=3D"mailto:cuss@ietf.org" target=3D"_blank">cuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/cuss" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/cuss</a><br>
</blockquote></div><br></div></div>

--047d7bf0c66466bdf204f0f3b0b0--

From david.black@emc.com  Mon Jan 27 06:21:04 2014
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1FDF1A0231; Mon, 27 Jan 2014 06:21:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4k4CV4Q1QIzT; Mon, 27 Jan 2014 06:21:02 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id D4A081A0214; Mon, 27 Jan 2014 06:21:01 -0800 (PST)
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0REKLUO005722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 09:20:24 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s0REKLUO005722
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390832424; bh=2TDDdpW2GAOoDonVpmg7CzXjIek=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=CDhHkLolIvVEg8Kcj/wWVR+cv+5cmANArOcKK6i9IszzUwSTv3Qnh+TcGKcpKM80Z uVyJzzkBzaHwzp5SQ2GsMVI9FamanA170cziXAtFXPOJc9FsldCMC4VAuu2WfXkE2D kw4nR0ylR6eUm3OXLcP2REdli60Ft8d0r27H92EI=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s0REKLUO005722
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd53.lss.emc.com (RSA Interceptor); Mon, 27 Jan 2014 09:20:13 -0500
Received: from mxhub08.corp.emc.com (mxhub08.corp.emc.com [128.222.70.205]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0REKCKA001772 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Jan 2014 09:20:12 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub08.corp.emc.com ([128.222.70.205]) with mapi; Mon, 27 Jan 2014 09:19:47 -0500
From: "Black, David" <david.black@emc.com>
To: Eliot Lear <lear@cisco.com>, "Alexey Melnikov (alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>, "dcridland@arcode.com" <dcridland@arcode.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Mon, 27 Jan 2014 09:20:10 -0500
Thread-Topic: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
Thread-Index: Ac8bYuepHQKAPJ5wQ42zaOAlQX1aAAAB1PLg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F162227@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com>
In-Reply-To: <52E65878.9030906@cisco.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
Cc: "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>, "ietf@ietf.org" <ietf@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 14:21:05 -0000

SGkgRWxpb3QsDQoNClJlZ2FyZGluZyBsaW5lIGxlbmd0aDoNCg0KPiBBcyB0aGUgZHJhZnQgaW5k
aWNhdGVzLCB0aGlzIGlzIHByb2JsZW1hdGljIGZvciB0aGUgdHdvIGV4dGVuc2lvbnMgaW4NCj4g
cXVlc3Rpb24uIFdlIGhhdmUgZGlzY3Vzc2VkIHRoaXMgbGltaXRhdGlvbiBpbiB0aGUgd29ya2lu
ZyBncm91cCwgYW5kDQo+IG5vYm9keSBzZWVtcyB0byBiZSBjb25jZXJuZWQuICBUaGF0J3MgZHVl
IHRvIHR3byBmYWN0b3JzLCBJIHRoaW5rOg0KPiBmaXJzdCwgUkZDIDI2ODMgaXMgbm90IG5vcm1h
dGl2ZSAoaW5mb3JtYXRpb25hbCkuICBJIGFtIHVuYXdhcmUgb2YgYW55DQo+IHN0cmljdCBsaW5l
IGxlbmd0aCBsaW1pdGF0aW9uIGluIFJGQyAzNTAxLCBmb3IgaW5zdGFuY2UuICBJbnN0ZWFkLCB0
aGVyZQ0KPiBpcyBhIHJlcXVpcmVtZW50IGZvciBzdHJpY3Qgc3ludGF4IHBhcnNpbmcuICBJZiB0
aGUgY2xpZW50IGJsb3dzIGl0IGluDQo+IGFueSB3YXksIHRoZSBzZXJ2ZXIgU0hPVUxEIHJldHVy
biBhbiBlcnJvciB3aXRoIGEgQkFEIHJlc3BvbnNlLg0KDQpUaGUgbGF0dGVyIHR3byBzZW50ZW5j
ZXMgd291bGQgYmUgZ29vZCB0byBhZGQgdG8gdGhlIGRyYWZ0IGluIHNvbWUgZm9ybS4NCg0KTXkg
cHJpbWFyeSBjb25jZXJuIGlzIHdoYXQgaGFwcGVucyBpZiB0aGUgY2xpZW50IHNlbmRzIGEgcmF0
aGVyIGxvbmcNCmxpbmUgdG8gYSBzZXJ2ZXIgdGhhdCBpc24ndCBwcmVwYXJlZCB0byBjb3BlLCBh
bmQgdGhlIGxhdHRlciBzZW50ZW5jZQ0Kd291bGQgYWRkcmVzcyBpdC4gIFRoYXQgY291bGQgYmUg
YWNjb21wYW5pZWQgYnkgc29tZSBzb3J0IG9mIHN0YXRlbWVudA0KdGhhdCBzZXJ2ZXJzIHRoYXQg
aW1wbGVtZW50IHRoaXMgZXh0ZW5zaW9uIG5lZWQgdG8gYmUgcHJlcGFyZWQgdG8gY29wZQ0Kd2l0
aCBsb25nZXIgbGluZXMuDQoNCkknbGwgbGVhdmUgdGhlIGRvd25yZWYgYXMgYSBwcm9jZXNzIGNv
bmNlcm4gZm9yIHlvdSAoV0cgY2hhaXIpIGFuZCBCYXJyeSAoQUQpDQp0byB3b3JrIG91dC4NCg0K
VGhhbmtzLA0KLS1EYXZpZA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206
IEVsaW90IExlYXIgW21haWx0bzpsZWFyQGNpc2NvLmNvbV0NCj4gU2VudDogTW9uZGF5LCBKYW51
YXJ5IDI3LCAyMDE0IDg6MDEgQU0NCj4gVG86IEJsYWNrLCBEYXZpZDsgQWxleGV5IE1lbG5pa292
IChhbGV4ZXkubWVsbmlrb3ZAaXNvZGUuY29tKTsNCj4gZGNyaWRsYW5kQGFyY29kZS5jb207IEdl
bmVyYWwgQXJlYSBSZXZpZXcgVGVhbSAoZ2VuLWFydEBpZXRmLm9yZykNCj4gQ2M6IEJhcnJ5IExl
aWJhIChiYXJyeWxlaWJhQGNvbXB1dGVyLm9yZyk7IGlldGZAaWV0Zi5vcmc7IGltYXBleHRAaWV0
Zi5vcmcNCj4gU3ViamVjdDogUmU6IEdlbi1BUlQgcmV2aWV3IG9mIGRyYWZ0LWlldGYtcXJlc3lu
Yy1yZmM1MTYyYmlzLTA5DQo+IA0KPiBIaSBEYXZlLA0KPiANCj4gRmlyc3QsIHRoYW5rIHlvdSBm
b3IgeW91ciByZXZpZXcuICBJIHBlcnNvbmFsbHkgYXBwcmVjaWF0ZSB0byB0aGUgdGltZQ0KPiB5
b3UgcHV0IGluIHRvIGFsbCBvZiB5b3VyIHJldmlld3MuDQo+IA0KPiBPbiAxLzI3LzE0LCAzOjA2
IEFNLCBCbGFjaywgRGF2aWQgd3JvdGU6DQo+ID4gSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCBy
ZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9yIGJhY2tncm91bmQgb24NCj4gPiBHZW4tQVJULCBw
bGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4gPg0KPiA+IDxodHRwOi8vd2lraS50b29scy5pZXRmLm9y
Zy9hcmVhL2dlbi90cmFjL3dpa2kvR2VuQXJ0ZmFxPi4NCj4gPg0KPiA+IFBsZWFzZSByZXNvbHZl
IHRoZXNlIGNvbW1lbnRzIGFsb25nIHdpdGggYW55IG90aGVyIExhc3QgQ2FsbCBjb21tZW50cw0K
PiA+IHlvdSBtYXkgcmVjZWl2ZS4NCj4gPg0KPiA+IERvY3VtZW50OiBkcmFmdC1pZXRmLXFyZXN5
bmMtcmZjNTE2MmJpcy0wOQ0KPiA+IFJldmlld2VyOiBEYXZpZCBMLiBCbGFjaw0KPiA+IFJldmll
dyBEYXRlOiBKYW51YXJ5IDI2LCAyMDE0DQo+ID4gSUVURiBMQyBFbmQgRGF0ZTogSmFudWFyeSAy
NywgMjAxNA0KPiA+DQo+ID4gU3VtbWFyeToNCj4gPiBUaGlzIGRyYWZ0IGlzIGJhc2ljYWxseSBy
ZWFkeSBmb3IgcHVibGljYXRpb24sIGJ1dCBoYXMgbWlub3IgaXNzdWVzIHRoYXQNCj4gPiBzaG91
bGQgYmUgZml4ZWQgYmVmb3JlIHB1YmxpY2F0aW9uLg0KPiA+DQo+ID4gVGhpcyBkcmFmdCBjb25z
b2xpZGF0ZXMgUkZDIDQ1NTEgKElNQVAgQ29uZGl0aW9uYWwgU1RPUkUpIGFuZCBSRkMgNTE2Mg0K
PiA+IChJTUFQIFF1aWNrIE1haWxib3ggUmVzeW5jaHJvbml6YXRpb24pIGludG8gYSBzaW5nbGUg
ZG9jdW1lbnQgYW5kIG1ha2VzDQo+ID4gYSBmZXcgbWlub3IgdXBkYXRlcy4gIEl0IGFsc28gdXBk
YXRlcyB0aGUgY29tbWFuZCBsaW5lIGxlbmd0aA0KPiA+IHJlY29tbWVuZGF0aW9uIGluIFJGQyAy
NjgzIHRvIHN1cHBvcnQgdGhlIGxvbmdlciBjb21tYW5kIGxpbmVzIHRoYXQNCj4gPiBjYW4gb2Nj
dXIgd2l0aCB0aGVzZSBleHRlbnNpb25zLg0KPiA+DQo+ID4gQXMgdGhpcyBpcyBhbiB1cGRhdGUs
IEkgY2hlY2tlZCB0aGUgZGlmZnMgYWdhaW5zdCBSRkMgNDU1MSBhbmQgUkZDIDUxNjI7DQo+ID4g
dGhleSBsb29rIHJlYXNvbmFibGUuICBJIGZvdW5kIG9uZSBtaW5vciBpc3N1ZSB0aGF0IHNob3Vs
ZCBiZSByZWxhdGl2ZWx5DQo+ID4gZWFzeSB0byBhZGRyZXNzLg0KPiA+DQo+ID4gTWlub3IgSXNz
dWVzOg0KPiA+DQo+ID4gVGhlIGNvbW1hbmQgbGluZSBsZW5ndGggY2hhbmdlIGluIFNlY3Rpb24g
NCBhcHBsaWVzIHRvIGFsbCBJTUFQIGNvbW1hbmRzLA0KPiA+IGFuZCBoZW5jZSBhZmZlY3RzIG9s
ZCBzZXJ2ZXJzLCBpbmNsdWRpbmcgdGhvc2UgdGhhdCBkb24ndCBpbXBsZW1lbnQgZWl0aGVyDQo+
ID4gb2YgdGhlIGV4dGVuc2lvbnMgaW4gdGhpcyBkcmFmdC4gVGhhdCByYWlzZXMgYSBiYWNrd2Fy
ZHMgY29tcGF0aWJpbGl0eQ0KPiA+IGNvbmNlcm4gLSB3aGF0IGhhcHBlbnMgd2hlbiBhIG5ldyBj
bGllbnQgc2VuZHMgYSA+IDEwMDAgY2hhcmFjdGVyIGNvbW1hbmQNCj4gPiBsaW5lIHRvIGFuIG9s
ZCBzZXJ2ZXIgdGhhdCBpc24ndCBleHBlY3RpbmcgbW9yZSB0aGFuIDEwMDAgY2hhcmFjdGVycz8N
Cj4gDQo+IEFzIHRoZSBkcmFmdCBpbmRpY2F0ZXMsIHRoaXMgaXMgcHJvYmxlbWF0aWMgZm9yIHRo
ZSB0d28gZXh0ZW5zaW9ucyBpbg0KPiBxdWVzdGlvbi4gV2UgaGF2ZSBkaXNjdXNzZWQgdGhpcyBs
aW1pdGF0aW9uIGluIHRoZSB3b3JraW5nIGdyb3VwLCBhbmQNCj4gbm9ib2R5IHNlZW1zIHRvIGJl
IGNvbmNlcm5lZC4gIFRoYXQncyBkdWUgdG8gdHdvIGZhY3RvcnMsIEkgdGhpbms6DQo+IGZpcnN0
LCBSRkMgMjY4MyBpcyBub3Qgbm9ybWF0aXZlIChpbmZvcm1hdGlvbmFsKS4gIEkgYW0gdW5hd2Fy
ZSBvZiBhbnkNCj4gc3RyaWN0IGxpbmUgbGVuZ3RoIGxpbWl0YXRpb24gaW4gUkZDIDM1MDEsIGZv
ciBpbnN0YW5jZS4gIEluc3RlYWQsIHRoZXJlDQo+IGlzIGEgcmVxdWlyZW1lbnQgZm9yIHN0cmlj
dCBzeW50YXggcGFyc2luZy4gIElmIHRoZSBjbGllbnQgYmxvd3MgaXQgaW4NCj4gYW55IHdheSwg
dGhlIHNlcnZlciBTSE9VTEQgcmV0dXJuIGFuIGVycm9yIHdpdGggYSBCQUQgcmVzcG9uc2UuDQo+
IA0KPiBUaGlzIGhhdmluZyBiZWVuIHNhaWQsIHdoaWxlIHRoZSB3b3JraW5nIGdyb3VwIGhhcyBk
aXNjdXNzZWQgdGhpcw0KPiBtYXR0ZXIsIGl0IHdvdWxkIGJlIGdvb2QgdG8gaGVhciBhbnkgYWRk
aXRpb25hbCB2b2ljZXMgb2YgY29uY2VybiwgaW4NCj4gdGhlIGludGVyZXN0cyBvZiBpbnRlcm9w
ZXJhYmlsaXR5Lg0KPiANCj4gVGhpcyB0YWtlcyB1cyB0byB5b3VyIG5leHQgcG9pbnQ6DQo+IA0K
PiA+DQo+ID4gT25lIHBvc3NpYmlsaXR5IHdvdWxkIGJlIHRvIGFwcGx5IHRoZSBsYXJnZXIgbGVu
Z3RoIHJlY29tbWVuZGF0aW9uIG9ubHkNCj4gPiBhZnRlciB0aGUgY2xpZW50IGRldGVybWluZXMg
dGhhdCB0aGUgc2VydmVyIHN1cHBvcnRzIGF0IGxlYXN0IG9uZSBvZg0KPiA+IHRoZXNlIGV4dGVu
c2lvbnMuDQo+ID4NCj4gPiBOaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCj4gPg0KPiA+IFRoZSB1
cGRhdGUgdG8gUkZDIDI2ODMgd291bGQgYmUgZWFzaWVyIHRvIGZpbmQgZnJvbSB0aGUgdGFibGUg
b2YgY29udGVudHMNCj4gPiBpZiB0aGUgdGl0bGUgb2YgU2VjdGlvbiA0IHdlcmUgY2hhbmdlZCB0
byAiTG9uZyBDb21tYW5kIExpbmVzIChVcGRhdGUgdG8NCj4gPiBSRkMgMjY4MykiLg0KPiA+DQo+
ID4gaWRuaXRzIDIuMTMuMDEgZ290IGNvbmZ1c2VkIGJ5IHRoZSBjb21tYW5kIGxpbmUgZXhhbXBs
ZXMsIGFuZCBmbGFnZ2VkIGENCj4gPiBkb3ducmVmOg0KPiA+DQo+ID4gICAqKiBEb3ducmVmOiBO
b3JtYXRpdmUgcmVmZXJlbmNlIHRvIGFuIEluZm9ybWF0aW9uYWwgUkZDOiBSRkMgMjY4Mw0KPiA+
DQo+ID4gVGhhdCBkb3ducmVmIGFwcGVhcnMgdG8gYmUgb2sgYW5kIGludGVuZGVkLCBhcyBub3Rl
ZCBpbiB0aGUgc2hlcGhlcmQncw0KPiA+IHdyaXRldXAuDQo+IA0KPiBUaGlzIHdpbGwgYmUgYWRk
cmVzc2VkIGluIGEgZm9ydGhjb21pbmcgdXBkYXRlLiAgQmFycnkgaGFzICJlZHVjYXRlZCIgdXMN
Cj4gdGhhdCByZWFsbHkgdGhpcyBpcyBOT1QgYW4gdXBkYXRlIHRvIFJGQzI2ODMsIHdoZXJlIHRo
ZSBhZHZpY2UgZ2l2ZW4gaW4NCj4gdGhhdCBkb2N1bWVudCBpcyBzdXBlcmNlZGVkIGJ5IGEgc3Bl
Y2lmaWMgb3B0aW9uLiAgQXMgc3VjaCwgdGhpcyBlcnJvcg0KPiB3aWxsIGV2YXBvcmF0ZS4NCj4g
DQo+IA0KDQo=

From w.roome@alcatel-lucent.com  Mon Jan 27 08:16:56 2014
Return-Path: <w.roome@alcatel-lucent.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10CF01A02E8 for <gen-art@ietfa.amsl.com>; Mon, 27 Jan 2014 08:16:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level: 
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UwuEuCCci1Ii for <gen-art@ietfa.amsl.com>; Mon, 27 Jan 2014 08:16:52 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 785991A02F0 for <gen-art@ietf.org>; Mon, 27 Jan 2014 08:16:52 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s0RGGbWU024531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 27 Jan 2014 10:16:38 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s0RGGbPA016901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Jan 2014 10:16:37 -0600
Received: from [135.222.152.83] (wdr-i7mbp2.mh.lucent.com [135.222.152.83]) by umail.lucent.com (8.13.8/TPES) with ESMTP id s0RGGX9I029992; Mon, 27 Jan 2014 10:16:34 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Mon, 27 Jan 2014 11:16:32 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: "Y. Richard Yang" <yry@cs.yale.edu>, Martin Thomson <martin.thomson@gmail.com>
Message-ID: <CF0BE8F0.C456C%w.roome@alcatel-lucent.com>
Thread-Topic: Gen-ART review of draft-ietf-alto-protocol-25
References: <CABkgnnVN=mxwwvbMKw=F-+cfgxYUrO8hzmF0r14ApfP7cXAcTQ@mail.gmail.com> <CANUuoLpVQ71VM=M8J7FmYiJK6VwdF7JvqzG36ymGWAr2Z2qXQg@mail.gmail.com>
In-Reply-To: <CANUuoLpVQ71VM=M8J7FmYiJK6VwdF7JvqzG36ymGWAr2Z2qXQg@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3473666196_2717632"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
X-Mailman-Approved-At: Mon, 27 Jan 2014 08:18:40 -0800
Cc: Sebastian Kiesel <ietf-alto@skiesel.de>, Richard Alimi <ralimi@google.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "N:" <draft-ietf-alto-protocol.all@tools.ietf.org>, "Reinaldo Penno, \(repenno\)" <repenno@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-alto-protocol-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:16:56 -0000

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

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

Here=B9s my response for =B3why resource ids instead of uris=B2:

An =B3ALTO Server=B2 is a collection of services provided by a provider. That
provider may distribute these services over several different physical
servers, and that distribution may change over time. If we used URIs to
identify those services, the IDs would have to change whenever the provider
redistributed services.

Therefore we defined =B3Resource IDs=B2 as persistent, location-independent, ID=
s
for those services. Resource IDs must be unique, but only within the contex=
t
of one provider=B9s services =8B that is, the services defined by the tree of
IRDs reachable from a root IRD. That IRD tree maps those Resource IDs to
URIs, and allows the provider to change the mapping without disrupting
clients. Thus ALTO Resource IDs are relative to the URI of the provider=B9s
IRD tree. If a provider had to use globally unique, location-dependent URIs=
,
instead of location-independent relative IDs, the provider would have an
unnecessary administrative burden.

(Yes, I know =B3URIs=B2, unlike URLs, are supposed to be =B3location independent.=
=B2
But let=B9s face reality: that only works if there=B9s some higher level mappin=
g
of URIs to locations. For all practical purposes, =B3URI=B2 means host-specific
=B3URL=B2.)

Another way to look at it is that =B3Resource IDs=B2 are like using relative
addresses within a web page. They make it easier to move a tree of related
pages from one host to another.

- Wendy Roome

From:  "Y. Richard Yang" <yry@cs.yale.edu>
Date:  Sun, January 26, 2014 at 16:40
To:  Martin Thomson <martin.thomson@gmail.com>
Cc:  "N:" <draft-ietf-alto-protocol.all@tools.ietf.org>, "gen-art@ietf.org"
<gen-art@ietf.org>, Richard Alimi <ralimi@google.com>, "Reinaldo Penno,
(repenno)" <repenno@cisco.com>, Wendy Roome <w.roome@alcatel-lucent.com>,
Sebastian Kiesel <ietf-alto@skiesel.de>
Subject:  Re: Gen-ART review of draft-ietf-alto-protocol-25


Section 10.2 defines a resource ID.  Why do this when you could use
URIs?  After all, that's what URIs are for.  I realize that this would
be something of a major change to the protocol, but I think that the
question is particularly important.


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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif;"><div>Here&#8217;s my response for =
&#8220;why resource ids instead of uris&#8221;:</div><div><br></div><div>An =
&#8220;ALTO Server&#8221; is a collection of services provided by a provider=
. That provider may distribute these services over several different physica=
l servers, and that distribution may change over time. If we used URIs to id=
entify those services, the IDs would have to change whenever the provider re=
distributed services.</div><div><br></div><div>Therefore we defined &#8220;R=
esource IDs&#8221; as persistent, location-independent, IDs for those servic=
es. Resource IDs must be unique, but only within the context of one provider=
&#8217;s services &#8212; that is, the services defined by the tree of IRDs =
reachable from a root IRD. That IRD tree maps those Resource IDs to URIs, an=
d allows the provider to change the mapping without disrupting clients. Thus=
 ALTO Resource IDs are relative to the URI of the provider&#8217;s IRD tree.=
 If a provider had to use globally unique, location-dependent URIs, instead =
of location-independent relative IDs, the provider would have an unnecessary=
 administrative burden.</div><div><br></div><div>(Yes, I know &#8220;URIs&#8=
221;, unlike URLs, are supposed to be &#8220;location independent.&#8221; Bu=
t let&#8217;s face reality: that only works if there&#8217;s some higher lev=
el mapping of URIs to locations. For all practical purposes, &#8220;URI&#822=
1; means host-specific &#8220;URL&#8221;.)</div><div><br></div><div>Another =
way to look at it is that &#8220;Resource IDs&#8221; are like using relative=
 addresses within a web page. They make it easier to move a tree of related =
pages from one host to another.</div><div><br></div><div><span class=3D"Apple-=
tab-span" style=3D"white-space:pre">	</span>- Wendy Roome</div><div><br></div>=
<span id=3D"OLK_SRC_BODY_SECTION"><div style=3D"font-family:Calibri; font-size:1=
1pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: =
medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BOR=
DER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><sp=
an style=3D"font-weight:bold">From: </span> "Y. Richard Yang" &lt;<a href=3D"mai=
lto:yry@cs.yale.edu">yry@cs.yale.edu</a>&gt;<br><span style=3D"font-weight:bol=
d">Date: </span> Sun, January 26, 2014 at 16:40<br><span style=3D"font-weight:=
bold">To: </span> Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.co=
m">martin.thomson@gmail.com</a>&gt;<br><span style=3D"font-weight:bold">Cc: </=
span> "N:" &lt;<a href=3D"mailto:draft-ietf-alto-protocol.all@tools.ietf.org">=
draft-ietf-alto-protocol.all@tools.ietf.org</a>&gt;, "<a href=3D"mailto:gen-ar=
t@ietf.org">gen-art@ietf.org</a>" &lt;<a href=3D"mailto:gen-art@ietf.org">gen-=
art@ietf.org</a>&gt;, Richard Alimi &lt;<a href=3D"mailto:ralimi@google.com">r=
alimi@google.com</a>&gt;, "Reinaldo Penno, (repenno)" &lt;<a href=3D"mailto:re=
penno@cisco.com">repenno@cisco.com</a>&gt;, Wendy Roome &lt;<a href=3D"mailto:=
w.roome@alcatel-lucent.com">w.roome@alcatel-lucent.com</a>&gt;, Sebastian Ki=
esel &lt;<a href=3D"mailto:ietf-alto@skiesel.de">ietf-alto@skiesel.de</a>&gt;<=
br><span style=3D"font-weight:bold">Subject: </span> Re: Gen-ART review of dra=
ft-ietf-alto-protocol-25<br></div><div><br></div><br style=3D"color: rgb(0, 0,=
 0); font-family: Calibri; font-size: medium; font-style: normal; font-varia=
nt: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-wi=
dth: 0px;"><span style=3D"color: rgb(0, 0, 0); font-family: Calibri; font-size=
: medium; font-style: normal; font-variant: normal; font-weight: normal; let=
ter-spacing: normal; line-height: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: auto; w=
ord-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important=
; float: none;">Section 10.2 defines a resource ID. &nbsp;Why do this when y=
ou could use</span><br style=3D"color: rgb(0, 0, 0); font-family: Calibri; fon=
t-size: medium; font-style: normal; font-variant: normal; font-weight: norma=
l; letter-spacing: normal; line-height: normal; orphans: auto; text-align: s=
tart; text-indent: 0px; text-transform: none; white-space: normal; widows: a=
uto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span style=3D"color:=
 rgb(0, 0, 0); font-family: Calibri; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; line-heig=
ht: normal; orphans: auto; text-align: start; text-indent: 0px; text-transfo=
rm: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text=
-stroke-width: 0px; display: inline !important; float: none;">URIs? &nbsp;Af=
ter all, that's what URIs are for. &nbsp;I realize that this would</span><br=
 style=3D"color: rgb(0, 0, 0); font-family: Calibri; font-size: medium; font-s=
tyle: normal; font-variant: normal; font-weight: normal; letter-spacing: nor=
mal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px=
; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px=
; -webkit-text-stroke-width: 0px;"><span style=3D"color: rgb(0, 0, 0); font-fa=
mily: Calibri; font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; orphans: a=
uto; text-align: start; text-indent: 0px; text-transform: none; white-space:=
 normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; di=
splay: inline !important; float: none;">be something of a major change to th=
e protocol, but I think that the</span><br style=3D"color: rgb(0, 0, 0); font-=
family: Calibri; font-size: medium; font-style: normal; font-variant: normal=
; font-weight: normal; letter-spacing: normal; line-height: normal; orphans:=
 auto; text-align: start; text-indent: 0px; text-transform: none; white-spac=
e: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"=
><span style=3D"color: rgb(0, 0, 0); font-family: Calibri; font-size: medium; =
font-style: normal; font-variant: normal; font-weight: normal; letter-spacin=
g: normal; line-height: normal; orphans: auto; text-align: start; text-inden=
t: 0px; text-transform: none; white-space: normal; widows: auto; word-spacin=
g: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: n=
one;">question is particularly important.</span></span></body></html>

--B_3473666196_2717632--



From alexey.melnikov@isode.com  Mon Jan 27 09:41:44 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75BFC1A0290; Mon, 27 Jan 2014 09:41:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mcNTaKPShegQ; Mon, 27 Jan 2014 09:41:41 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id C21331A0251; Mon, 27 Jan 2014 09:41:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1390844497; d=isode.com; s=selector; i=@isode.com; bh=C18uM+P5IrqBZjvicy6HsYMmV/FIf/YMEFq48laZPNU=; 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=gKHDuaWsygTzN5F1hpI/js9w5Bf4oEarrulJGwZKfYx4gyajH7B8OrhX9AQRGAQdXWPuY1 iL3aivay/zUhf/AYd6W78Aj8agaGuIoCFueBz0PtkPQoS7WFyFYkcJqWKnp048UySeQWCa +xn1rZoB2yoRy6U/Fac/FmT+bkFbOYc=;
Received: from [192.168.0.4] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <UuaaUAAIPyYq@waldorf.isode.com>; Mon, 27 Jan 2014 17:41:37 +0000
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <52E69A54.9030104@isode.com>
Date: Mon, 27 Jan 2014 17:41:40 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: Eliot Lear <lear@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com>
In-Reply-To: <52E65878.9030906@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>
Subject: Re: [Gen-art] [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:41:44 -0000

Hi Eliot,
Mostly agreeing with you, but some corrections below:

On 27/01/2014 13:00, Eliot Lear wrote:
> Hi Dave,
>
> First, thank you for your review.  I personally appreciate to the time
> you put in to all of your reviews.
>
> On 1/27/14, 3:06 AM, Black, David 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-qresync-rfc5162bis-09
>> Reviewer: David L. Black
>> Review Date: January 26, 2014
>> IETF LC End Date: January 27, 2014
>>
>> Summary:
>> This draft is basically ready for publication, but has minor issues that
>> should be fixed before publication.
>>
>> This draft consolidates RFC 4551 (IMAP Conditional STORE) and RFC 5162
>> (IMAP Quick Mailbox Resynchronization) into a single document and makes
>> a few minor updates.  It also updates the command line length
>> recommendation in RFC 2683 to support the longer command lines that
>> can occur with these extensions.
>>
>> As this is an update, I checked the diffs against RFC 4551 and RFC 5162;
>> they look reasonable.  I found one minor issue that should be relatively
>> easy to address.
>>
>> Minor Issues:
>>
>> The command line length change in Section 4 applies to all IMAP commands,
>> and hence affects old servers, including those that don't implement either
>> of the extensions in this draft. That raises a backwards compatibility
>> concern - what happens when a new client sends a > 1000 character command
>> line to an old server that isn't expecting more than 1000 characters?
> As the draft indicates, this is problematic for the two extensions in
> question. We have discussed this limitation in the working group, and
> nobody seems to be concerned.  That's due to two factors, I think:
> first, RFC 2683 is not normative (informational).
I don't think this actually matters, but the rest of your argument is 
still valid.
> I am unaware of any
> strict line length limitation in RFC 3501, for instance.  Instead, there
> is a requirement for strict syntax parsing.  If the client blows it in
> any way, the server SHOULD return an error with a BAD response.
That is very true. This is what happens now.
> This having been said, while the working group has discussed this
> matter, it would be good to hear any additional voices of concern, in
> the interests of interoperability.
Agreed.
> This takes us to your next point:
>
>> One possibility would be to apply the larger length recommendation only
>> after the client determines that the server supports at least one of
>> these extensions.
>>
>> Nits/editorial comments:
>>
>> The update to RFC 2683 would be easier to find from the table of contents
>> if the title of Section 4 were changed to "Long Command Lines (Update to
>> RFC 2683)".
>>
>> idnits 2.13.01 got confused by the command line examples, and flagged a
>> downref:
>>
>>    ** Downref: Normative reference to an Informational RFC: RFC 2683
>>
>> That downref appears to be ok and intended, as noted in the shepherd's
>> writeup.
> This will be addressed in a forthcoming update.  Barry has "educated" us
> that really this is NOT an update to RFC2683, where the advice given in
> that document is superceded by a specific option.  As such, this error
> will evaporate.
Actually, I think I convinced Barry that it is updating RFC 2683.

Best Regards,
Alexey


From jmh@joelhalpern.com  Mon Jan 27 10:16:26 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B83701A001E; Mon, 27 Jan 2014 10:16:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GM-epQnU6wHm; Mon, 27 Jan 2014 10:16:25 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 07AFD1A022F; Mon, 27 Jan 2014 10:16:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id D5E3C1004C9; Mon, 27 Jan 2014 10:16:22 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id EBCB11004C7; Mon, 27 Jan 2014 10:16:21 -0800 (PST)
Message-ID: <52E6A274.5020307@joelhalpern.com>
Date: Mon, 27 Jan 2014 13:16:20 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Alan Johnston <alan.b.johnston@gmail.com>
References: <5195550A.3000608@nostrum.com>	<519920BA.9040308@joelhalpern.com> <CAKhHsXHpOKaCb5M1j=H=j8z+dDsWtuKXmK_vFE9qsKSKv3mAEQ@mail.gmail.com>
In-Reply-To: <CAKhHsXHpOKaCb5M1j=H=j8z+dDsWtuKXmK_vFE9qsKSKv3mAEQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-cuss-sip-uui-all@tools.ietf.org, "cuss@ietf.org" <cuss@ietf.org>
Subject: Re: [Gen-art] [cuss]  review: draft-ietf-cuss-sip-uui-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 18:16:26 -0000

Thank you Alan.  Those changes fully address my comments.
Yours,
Joel

On 1/27/14 8:28 AM, Alan Johnston wrote:
> Joel,
>
> Thanks for your review of the document.  We have made the changes you
> suggested in your review in the -12 version.
>
> http://www.ietf.org/id/draft-ietf-cuss-sip-uui-12.txt
>
> Let us know if there are any other issues.
>
> - Alan -
>
>
> On Sun, May 19, 2013 at 1:58 PM, Joel M. Halpern <jmh@joelhalpern.com
> <mailto:jmh@joelhalpern.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
>     <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-cuss-sip-uui-10
>          A Mechanism for Transporting User to User
>              Call Control Information in SIP
>     Reviewer: Joel M. Halpern
>     Review Date: 19-May-2013
>     IETF LC End Date: 29-May-2013
>     IESG Telechat date: N/A
>
>     Summary: This document is nearly ready for publication as a Proposed
>     Standard
>
>     Major issues:
>
>     Minor issues:
>          The requirements discussions for redirection and referral
>     (second paragraph of section 3, in regards REQ-3) includes what
>     appears to be normative requirements on redirecting devices.
>     a) This would seem to belong in section 4 on Normative Definition.
>     b) It would seem that there ought to be some discussion of what
>     happens with redirecting devices that do not understand this new
>     UUI. (I presume things work, but I don't see how.)
>
>     Nits/editorial comments:
>          In section 8.2, given that this is a WG document, should the
>     "the authors believe" actually be "the WG believes"?  Or even, given
>     IETF rough consensus on this document, "the IETF believes"?
>     _________________________________________________
>     cuss mailing list
>     cuss@ietf.org <mailto:cuss@ietf.org>
>     https://www.ietf.org/mailman/__listinfo/cuss
>     <https://www.ietf.org/mailman/listinfo/cuss>
>
>

From barryleiba@gmail.com  Mon Jan 27 12:59:52 2014
Return-Path: <barryleiba@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA5C1A0034; Mon, 27 Jan 2014 12:59:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4U925Qkk0Oky; Mon, 27 Jan 2014 12:59:51 -0800 (PST)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 191571A00F6; Mon, 27 Jan 2014 12:59:50 -0800 (PST)
Received: by mail-qa0-f45.google.com with SMTP id ii20so8098601qab.32 for <multiple recipients>; Mon, 27 Jan 2014 12:59:48 -0800 (PST)
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=OSrFbNu2l6O1KqgTDGi2hu1gj+san85JxbwA4k43bAA=; b=R4kN6jlLnj9/n3B29XDtftV99XoQIoVkvHlXkn30YbVX9k9bvkTVFO5tZbgWXicjmT 3fm3LB5ipbXZNVS4U0Qr5KZc0Pj5xBGz6zBUW2qITlOGtbJNNVzzBh+2cCyuxv9Sc14P aNNXvPZkRRL/k57Hwl5GmkuC7kBNnm8g0rp5J90QNXkBMZjtmcSl+g0wcG0jrNfCpJkC 4xUpBBtWiBZeQqsqzCtRHvE9I/znW7MekpRRZ2cqWOXwKv1HppmaQurEKnGajcq/2fG5 VzSj3hUTdahbnIvvQnTMJ8p8eYJVIV9PfpzEg7NDbt01KjodbPsYJVJnON/5FkTcxfWL e/FA==
MIME-Version: 1.0
X-Received: by 10.229.196.197 with SMTP id eh5mr46178465qcb.3.1390856388591; Mon, 27 Jan 2014 12:59:48 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.224.26.11 with HTTP; Mon, 27 Jan 2014 12:59:48 -0800 (PST)
In-Reply-To: <52E69A54.9030104@isode.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com> <52E69A54.9030104@isode.com>
Date: Mon, 27 Jan 2014 15:59:48 -0500
X-Google-Sender-Auth: 1G53Zb6aqJxTFsRRiXicjYq710k
Message-ID: <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, Eliot Lear <lear@cisco.com>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [Gen-art] [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 20:59:52 -0000

> Actually, I think I convinced Barry that it is updating RFC 2683.

Yes: because the new line-length-limit recommendation is meant to
apply whether or not condstore or qresync are in play, this "updates"
remains (it's the others that used to be there that we scrubbed).

I think David's right that some version of what Eliot said:

> there
> is a requirement for strict syntax parsing.  If the client blows it in
> any way, the server SHOULD return an error with a BAD response.

...should be added to the section about the line-length limit.  A
sentence or two should do nicely.

Barry

From lear@cisco.com  Mon Jan 27 13:23:40 2014
Return-Path: <lear@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC9B61A0235; Mon, 27 Jan 2014 13:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6C1ijOmn1e7; Mon, 27 Jan 2014 13:23:39 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 968821A0146; Mon, 27 Jan 2014 13:23:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=878; q=dns/txt; s=iport; t=1390857817; x=1392067417; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mGexWQU6ryTrAoAhd2Rl73rE0NOxP6a31fYtzTO6uYE=; b=BkeyN9i5tWhiJQQV+4NQJhsnufLOiXJ0VlpQiJCdArNNLrrTZVGKJwLo AHZmHBqCcHV67fAUogv1U4MFGweFQ4yyvBBdAXOaeC0wn7IEdCJKpS+Yx KroUjos38zAvabk/eva/0IILAHmHO9OKwCtdiBY0Aa63SCLGokBRJjPAw U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAInN5lKQ/khM/2dsb2JhbABagwyEC7legRwWdIIlAQEBBCNVARALGAICBRYLAgIJAwIBAgErGgYBDAEHAQGIAaoBnQAXgSmNDVcHgm+BSQEDmCeSHoMtPIEt
X-IronPort-AV: E=Sophos;i="4.95,731,1384300800";  d="scan'208";a="3597002"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 27 Jan 2014 21:23:34 +0000
Received: from mctiny.local ([10.61.192.127]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0RLNX5f004819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 21:23:33 GMT
Message-ID: <52E6CE54.7020104@cisco.com>
Date: Mon, 27 Jan 2014 21:23:32 +0000
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>, Alexey Melnikov <alexey.melnikov@isode.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com>	<52E65878.9030906@cisco.com>	<52E69A54.9030104@isode.com> <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com>
In-Reply-To: <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dcridland@arcode.com" <dcridland@arcode.com>, "imapext@ietf.org" <imapext@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 21:23:40 -0000

Hi Barry, Dave, and Alexey,

On 1/27/14, 8:59 PM, Barry Leiba wrote:
>> Actually, I think I convinced Barry that it is updating RFC 2683.
> Yes: because the new line-length-limit recommendation is meant to
> apply whether or not condstore or qresync are in play, this "updates"
> remains (it's the others that used to be there that we scrubbed).
>
> I think David's right that some version of what Eliot said:
>
>> there
>> is a requirement for strict syntax parsing.  If the client blows it in
>> any way, the server SHOULD return an error with a BAD response.
> ...should be added to the section about the line-length limit.  A
> sentence or two should do nicely.
>
>

I don't see a problem, but for context I was really just borrowing from
RFC 3501, which already states that SHOULD (Section 2.2 if memory
serves).  Stating it again won't hurt.

Eliot

From dave@cridland.net  Mon Jan 27 13:26:09 2014
Return-Path: <dave@cridland.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00D221A0146 for <gen-art@ietfa.amsl.com>; Mon, 27 Jan 2014 13:26:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XSYDhhyDSBDD for <gen-art@ietfa.amsl.com>; Mon, 27 Jan 2014 13:26:07 -0800 (PST)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 8DA311A029E for <gen-art@ietf.org>; Mon, 27 Jan 2014 13:26:06 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id wp4so7083845obc.2 for <gen-art@ietf.org>; Mon, 27 Jan 2014 13:26:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=N7jwDBVDrmNguCLWnep1Rk8QFpjKRB8rdlqV1l6chMw=; b=dtzq4Na2/zm8H4s7ZbZALoPHJUiQUvSRsDBVAaPa4uFGXvxXP5InWn8bpMGlyK8jzD 2KLwh8/LIDoJv0HxbsKIOtDxOYvxgLDRRknVR8BaFmstVwHhmixW+bqPQkMa9VahpVL6 pZyq0WhluEBlHCghXFinsQQDN6Xj/EucvaGZ8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=N7jwDBVDrmNguCLWnep1Rk8QFpjKRB8rdlqV1l6chMw=; b=LRktRt6+TPZFa2J1PGGPQ2e6kWPjhGAMjXh1gRMh5zKikV5aBkBHMFPfQtcIwVWWLV ChRSSSQTggbMaacxXe01kslEGpDGAPYSbasYBmN6QucxBFUWa9/HzbtD3E5Io+KKv5JD I1QhXQZPgv+s3RWYp1jqx1VaP6TXLdmGj0DlfBgPz3afczH7gFnK9U9a/LZvKuflX/JJ vaRbIod/+jxcW/ipZ1/dpNwA7/Wl/wLv0/7jio99noOg30yw6FIfWHbQELjLdvRj9Vdh M2i/6upEvVXh6cZmJAQU1yLxMd0wdOizTYEUQorflgV9TO2IKyc7oQ/zgI9squVeJ7CW glhg==
X-Gm-Message-State: ALoCoQmWuXZcybtpMaUf70jCd3My5HE1QeLQX2JoGUChxW3I2gwqs6OxfrrRA5/O3Cyt5LLMoULp
MIME-Version: 1.0
X-Received: by 10.182.84.132 with SMTP id z4mr2378405oby.49.1390857964060; Mon, 27 Jan 2014 13:26:04 -0800 (PST)
Received: by 10.60.55.138 with HTTP; Mon, 27 Jan 2014 13:26:03 -0800 (PST)
In-Reply-To: <52E6CE54.7020104@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com> <52E69A54.9030104@isode.com> <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com> <52E6CE54.7020104@cisco.com>
Date: Mon, 27 Jan 2014 21:26:03 +0000
Message-ID: <CAKHUCzy8-YuH7sESMA_oZRnX_s38pUDqeDB78qP=0QOYbhruPg@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
To: Eliot Lear <lear@cisco.com>
Content-Type: multipart/alternative; boundary=089e0111c09ae1d54804f0fa5a09
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, Barry Leiba <barryleiba@computer.org>
Subject: Re: [Gen-art] [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 21:26:09 -0000

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

I assume you mean it should include a pointer to that SHOULD, not restate
it as such?


On Mon, Jan 27, 2014 at 9:23 PM, Eliot Lear <lear@cisco.com> wrote:

> Hi Barry, Dave, and Alexey,
>
> On 1/27/14, 8:59 PM, Barry Leiba wrote:
> >> Actually, I think I convinced Barry that it is updating RFC 2683.
> > Yes: because the new line-length-limit recommendation is meant to
> > apply whether or not condstore or qresync are in play, this "updates"
> > remains (it's the others that used to be there that we scrubbed).
> >
> > I think David's right that some version of what Eliot said:
> >
> >> there
> >> is a requirement for strict syntax parsing.  If the client blows it in
> >> any way, the server SHOULD return an error with a BAD response.
> > ...should be added to the section about the line-length limit.  A
> > sentence or two should do nicely.
> >
> >
>
> I don't see a problem, but for context I was really just borrowing from
> RFC 3501, which already states that SHOULD (Section 2.2 if memory
> serves).  Stating it again won't hurt.
>
> Eliot
>

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

<div dir=3D"ltr">I assume you mean it should include a pointer to that SHOU=
LD, not restate it as such?</div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Mon, Jan 27, 2014 at 9:23 PM, Eliot Lear <span dir=
=3D"ltr">&lt;<a href=3D"mailto:lear@cisco.com" target=3D"_blank">lear@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">Hi Barry, Dave, and Alexey,<br>
<div><div class=3D"h5"><br>
On 1/27/14, 8:59 PM, Barry Leiba wrote:<br>
&gt;&gt; Actually, I think I convinced Barry that it is updating RFC 2683.<=
br>
&gt; Yes: because the new line-length-limit recommendation is meant to<br>
&gt; apply whether or not condstore or qresync are in play, this &quot;upda=
tes&quot;<br>
&gt; remains (it&#39;s the others that used to be there that we scrubbed).<=
br>
&gt;<br>
&gt; I think David&#39;s right that some version of what Eliot said:<br>
&gt;<br>
&gt;&gt; there<br>
&gt;&gt; is a requirement for strict syntax parsing. =A0If the client blows=
 it in<br>
&gt;&gt; any way, the server SHOULD return an error with a BAD response.<br=
>
&gt; ...should be added to the section about the line-length limit. =A0A<br=
>
&gt; sentence or two should do nicely.<br>
&gt;<br>
&gt;<br>
<br>
</div></div>I don&#39;t see a problem, but for context I was really just bo=
rrowing from<br>
RFC 3501, which already states that SHOULD (Section 2.2 if memory<br>
serves). =A0Stating it again won&#39;t hurt.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Eliot<br>
</font></span></blockquote></div><br></div>

--089e0111c09ae1d54804f0fa5a09--

From david.black@emc.com  Mon Jan 27 13:43:00 2014
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CEAC1A022F; Mon, 27 Jan 2014 13:43:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cUom4Om3wqrC; Mon, 27 Jan 2014 13:42:57 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id E50401A0068; Mon, 27 Jan 2014 13:42:56 -0800 (PST)
Received: from maildlpprd01.lss.emc.com (maildlpprd01.lss.emc.com [10.253.24.33]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0RLgnYi017670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 16:42:50 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s0RLgnYi017670
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390858971; bh=12zzdRDW9QV+c/0eAaX8QEfLPao=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=rY7rrAiEtHpMhmjmUoDQE/lcEGS3l/lRujCo9sxiRRsswCJvRxuhhB/5PM5OdaKqy Ir57vKU+ImrVfJf0UGSkLX35AYZwZT13iGxxNZXPrDV/KDbrxwcJAGAjJef+Sp6eeL e9TVd++9aXXHS1Nxcko3d/TAK7+OcIvQ1MPLFR44=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s0RLgnYi017670
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd01.lss.emc.com (RSA Interceptor); Mon, 27 Jan 2014 16:42:29 -0500
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0RLgSnm028782 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Jan 2014 16:42:28 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub18.corp.emc.com ([10.254.93.47]) with mapi; Mon, 27 Jan 2014 16:42:27 -0500
From: "Black, David" <david.black@emc.com>
To: Dave Cridland <dave@cridland.net>, Eliot Lear <lear@cisco.com>
Date: Mon, 27 Jan 2014 16:42:27 -0500
Thread-Topic: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
Thread-Index: Ac8bpmqQhOX2b95ATuq5+uw+4lVz3AAAG3bw
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F1623A4@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com>	<52E69A54.9030104@isode.com> <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com> <52E6CE54.7020104@cisco.com> <CAKHUCzy8-YuH7sESMA_oZRnX_s38pUDqeDB78qP=0QOYbhruPg@mail.gmail.com>
In-Reply-To: <CAKHUCzy8-YuH7sESMA_oZRnX_s38pUDqeDB78qP=0QOYbhruPg@mail.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_8D3D17ACE214DC429325B2B98F3AE712026F1623A4MX15Acorpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: public
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, Barry Leiba <barryleiba@computer.org>
Subject: Re: [Gen-art] [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 21:43:00 -0000

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

I don't quite see the details in RFC 3501.  I think what's going on is that=
:

A server implementation that uses a shorter command line length limit than
this recommendation could clip a longer client command line at the server's
line length limit.  This SHOULD result in a syntax error (e.g., due to the
server not finding a CRLF at the end of the clipped command line) that
causes the server to return a BAD response, as specified in RFC 3501.

Thanks,
--David

From: Dave Cridland [mailto:dave@cridland.net]
Sent: Monday, January 27, 2014 4:26 PM
To: Eliot Lear
Cc: Barry Leiba; Alexey Melnikov; General Area Review Team (gen-art@ietf.or=
g); Black, David; dcridland@arcode.com; imapext@ietf.org; ietf@ietf.org
Subject: Re: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09

I assume you mean it should include a pointer to that SHOULD, not restate i=
t as such?

On Mon, Jan 27, 2014 at 9:23 PM, Eliot Lear <lear@cisco.com<mailto:lear@cis=
co.com>> wrote:
Hi Barry, Dave, and Alexey,

On 1/27/14, 8:59 PM, Barry Leiba wrote:
>> Actually, I think I convinced Barry that it is updating RFC 2683.
> Yes: because the new line-length-limit recommendation is meant to
> apply whether or not condstore or qresync are in play, this "updates"
> remains (it's the others that used to be there that we scrubbed).
>
> I think David's right that some version of what Eliot said:
>
>> there
>> is a requirement for strict syntax parsing.  If the client blows it in
>> any way, the server SHOULD return an error with a BAD response.
> ...should be added to the section about the line-length limit.  A
> sentence or two should do nicely.
>
>
I don't see a problem, but for context I was really just borrowing from
RFC 3501, which already states that SHOULD (Section 2.2 if memory
serves).  Stating it again won't hurt.

Eliot


--_000_8D3D17ACE214DC429325B2B98F3AE712026F1623A4MX15Acorpemcc_
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)"><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.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.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=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>I don&#8217;t quite =
see the details in RFC 3501.&nbsp; I think what&#8217;s going on is that:<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:black'>A server implementation that uses a shorter command line length li=
mit than<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:10.0pt;font-family:"Courier New";color:black'>this recommendation could cl=
ip a longer client command line at the server&#8217;s<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew";color:black'>line length limit.&nbsp; This SHOULD result in a syntax er=
ror (e.g., due to the<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:black'>server not find=
ing a CRLF at the end of the clipped command line) that<o:p></o:p></span></=
p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier=
 New";color:black'>causes the server to return a BAD response, as specified=
 in RFC 3501.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span=
></p><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:=
"Courier New";color:black'>Thanks,<br>--David</span><span style=3D'font-siz=
e:11.0pt;font-family:"Courier New";color:black'><o:p></o:p></span></p></div=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;bor=
der-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'bor=
der: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'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'> Dave Cridland [mailto:dave@cridland.net] <br><b>Sent:</b> =
Monday, January 27, 2014 4:26 PM<br><b>To:</b> Eliot Lear<br><b>Cc:</b> Bar=
ry Leiba; Alexey Melnikov; General Area Review Team (gen-art@ietf.org); Bla=
ck, David; dcridland@arcode.com; imapext@ietf.org; ietf@ietf.org<br><b>Subj=
ect:</b> Re: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09<o=
:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
div><p class=3DMsoNormal>I assume you mean it should include a pointer to t=
hat SHOULD, not restate it as such?<o:p></o:p></p></div><div><p class=3DMso=
Normal style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p class=3D=
MsoNormal>On Mon, Jan 27, 2014 at 9:23 PM, Eliot Lear &lt;<a href=3D"mailto=
:lear@cisco.com" target=3D"_blank">lear@cisco.com</a>&gt; wrote:<o:p></o:p>=
</p><p class=3DMsoNormal>Hi Barry, Dave, and Alexey,<o:p></o:p></p><div><di=
v><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>On 1/27/14, 8:59 =
PM, Barry Leiba wrote:<br>&gt;&gt; Actually, I think I convinced Barry that=
 it is updating RFC 2683.<br>&gt; Yes: because the new line-length-limit re=
commendation is meant to<br>&gt; apply whether or not condstore or qresync =
are in play, this &quot;updates&quot;<br>&gt; remains (it's the others that=
 used to be there that we scrubbed).<br>&gt;<br>&gt; I think David's right =
that some version of what Eliot said:<br>&gt;<br>&gt;&gt; there<br>&gt;&gt;=
 is a requirement for strict syntax parsing. &nbsp;If the client blows it i=
n<br>&gt;&gt; any way, the server SHOULD return an error with a BAD respons=
e.<br>&gt; ...should be added to the section about the line-length limit. &=
nbsp;A<br>&gt; sentence or two should do nicely.<br>&gt;<br>&gt;<o:p></o:p>=
</p></div></div><p class=3DMsoNormal>I don't see a problem, but for context=
 I was really just borrowing from<br>RFC 3501, which already states that SH=
OULD (Section 2.2 if memory<br>serves). &nbsp;Stating it again won't hurt.<=
br><span style=3D'color:#888888'><br><span class=3Dhoenzb>Eliot</span></spa=
n><o:p></o:p></p></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></di=
v></div></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE712026F1623A4MX15Acorpemcc_--

From alexey.melnikov@isode.com  Tue Jan 28 00:34:20 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2F431A019D; Tue, 28 Jan 2014 00:34:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tYwZcJ-XB8Ia; Tue, 28 Jan 2014 00:34:18 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id A1EEE1A003E; Tue, 28 Jan 2014 00:34:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1390898054; d=isode.com; s=selector; i=@isode.com; bh=lxpmDPU4z6yjKvLWu+4P5DeogEHrcYgaIXv+kitVDkQ=; 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=tJul53O7nj7jkfwO9ZwldU9iBYLe6DgI7Z3TSBVrEoVLvW6saEqqBFrjq5YIyaeH3r9n7v nITmf0AG2pYlcZlq4An73aZEHR2SBPzeIhE6F67NeQ3XAwplODskcolhB8913L/z1Yjm7M lAEsWRc9TTTxmNgRTzIGHMrKfRVep3s=;
Received: from [192.168.0.12] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <UudrhQAIPzmg@waldorf.isode.com>; Tue, 28 Jan 2014 08:34:14 +0000
X-SMTP-Protocol-Errors: PIPELINING
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (11B511)
In-Reply-To: <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com>
Date: Tue, 28 Jan 2014 08:37:07 +0000
Message-Id: <A122D59D-B356-4A92-B0C8-9E31CB938FF9@isode.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com> <52E69A54.9030104@isode.com> <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, Eliot Lear <lear@cisco.com>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [Gen-art] [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 08:34:20 -0000

On 27 Jan 2014, at 20:59, Barry Leiba <barryleiba@computer.org> wrote:

>> Actually, I think I convinced Barry that it is updating RFC 2683.
> 
> Yes: because the new line-length-limit recommendation is meant to
> apply whether or not condstore or qresync are in play, this "updates"
> remains (it's the others that used to be there that we scrubbed).
> 
> I think David's right that some version of what Eliot said:
> 
>> there
>> is a requirement for strict syntax parsing.  If the client blows it in
>> any way, the server SHOULD return an error with a BAD response.
> 
> ...should be added to the section about the line-length limit.  A
> sentence or two should do nicely.

Yes, I agree.


From elwynd@dial.pipex.com  Tue Jan 28 15:25:49 2014
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5FE31A02F0 for <gen-art@ietfa.amsl.com>; Tue, 28 Jan 2014 15:25:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQYuQIfiVy3w for <gen-art@ietfa.amsl.com>; Tue, 28 Jan 2014 15:25:46 -0800 (PST)
Received: from mk-outboundfilter-5.mail.uk.tiscali.com (mk-outboundfilter-5.mail.uk.tiscali.com [212.74.114.1]) by ietfa.amsl.com (Postfix) with ESMTP id 868851A029E for <gen-art@ietf.org>; Tue, 28 Jan 2014 15:25:45 -0800 (PST)
X-Trace: 57946078/mk-outboundfilter-5.mail.uk.tiscali.com/PIPEX/$OFF_NET_AUTH_ACCEPTED/None/81.187.254.249/None/elwynd@dial.pipex.com
X-SBRS: None
X-RemoteIP: 81.187.254.249
X-IP-MAIL-FROM: elwynd@dial.pipex.com
X-SMTP-AUTH: elwynd@dial.pipex.com
X-MUA: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap8EAN476FJRu/75/2dsb2JhbABag0S9V4Emg1hAAS8NFhgDAgECAUsNAQcBAReHbgnJfo0NgXKEPwSYKIEyhH+LboMt
X-IPAS-Result: Ap8EAN476FJRu/75/2dsb2JhbABag0S9V4Emg1hAAS8NFhgDAgECAUsNAQcBAReHbgnJfo0NgXKEPwSYKIEyhH+LboMt
X-IronPort-AV: E=Sophos;i="4.95,739,1384300800"; d="scan'208";a="57946078"
X-IP-Direction: OUT
Received: from weee-pc2.folly.org.uk (HELO [81.187.254.249]) ([81.187.254.249]) by smtp.pipex.tiscali.co.uk with ESMTP; 28 Jan 2014 23:25:42 +0000
Message-ID: <52E83C75.7030909@dial.pipex.com>
Date: Tue, 28 Jan 2014 23:25:41 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-v6ops-nat64-experience.all@tools.ietf.org
Subject: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 23:25:49 -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-nat64-experience-09.txt
Reviewer: Elwyn Davies
Review Date: 28 January 2014
IETF LC End Date: 28 January 2014
IESG Telechat date: (if known) -

Summary:
Not ready.  This document needs a serious rewrite with the assistance of 
a mother tongue English speaker.  I started doing some of this getting 
as far as s3.1.4, however I came to the conclusion that significant 
parts of the language were sufficiently unclear that I was unable to 
determine the intended meaning.  Accordingly I have abandoned the review 
and will have another go assuming a rewrite is done.  Please consider 
whether the title should be modified as noted below.

Major issues:

Minor issues:
Title:  The title is rather misleading since it the document actually 
documents two suggested ways of deploying NAT64 as well as experience of 
deploying these solutions. Maybe 'NAT64 Deployment Options and Experience'.

s1: A reference to explain what PDP context etc means in an LTE 
environment would be useful.

s3.1.3: It is stated that placing the NAT64 (middlebox) in a centralized 
location would 'reduce the diversity of  log format'.  I guess what is 
possibly being said that is that the network should preferentially use 
just one NAT64 box centrally placed rather than several (smaller) boxes 
at various edge locations.  I think this needs to be explained more 
clearly (assuming I have it right).  OTOH I would rather expect that 
most network owners would go for a single species of NAT64 box so the 
diversity of log formats is really a side issue.

s5.2: The problem here is not specifically geo-location - and since we 
normally don't have any mapping between topology and location this seems 
inappropriate - but doing host identification (which is what RFC 6967 is 
about.  Shouldn't this section just be about host identification?

s8, para 2:
> We configure ULAs as NAT64 prefixes on a NAT64-CGN.
So.. is this a mandatory requirement or just a possibility?

Nits/editorial comments:

s1, para 1: s/Internet/the Internet/

s1, para 2: s/simplify networks provisioning/simplify the provisioning 
of networks/, s/confers some benefits to/confers some benefits on/, 
s/such mobile/such a mobile/, s/if Long Term/if a Long Term/

s3.1.1: s/can be seen with better transparency features/can offer 
improved transparency to <state who or what is offered the improved 
transparency> /

s3.1.1: Expand A+P abbreviation.

s3.3.1: s/IPv4 shortage/IPv4 address shortage/

ss3.1.2, 3.1.3 and 3.1.4: These are very long paragraphs.  It would be 
good to separate the various discussion points into separate paragraphs.

s3.1.2: "..to enable access of IPv4 only applications" Presumably this 
is access to applications running on the IPv4 side from applications on 
the IPV6 side... Suggest
"to allow applications running on the IPv6 network to interact with 
applications that can only use IPv4 communications or IPv6 applications 
that need to communicate using literal IPv4 addresses."

s3.1.2: s/discover NAT64 prefix/discover the NAT64 prefix/

s3.1.2: need a reference for BIND.

s3.1.2: s/...(BIND) software supports the function./The ... (BIND) 
implementation of NAT64 supports this discovery function./

s3.1.2:s/Operators should not/Users should not/ perhaps.

s3.1.2: s/going to IPv4-only service/going to IPv4-only services/

s3.1.2: s/restrains NAT uses/restrains NAT usage/

s3.1.2: s/all traffic flows have to be traversed and translated./all 
traffic flows have to traverse the NAT44 middlebox and be translated there./

s3.1.2: s/may serve a double roles, i.e. a translator and IPv6 
forwarder./may serve a dual role acting as both translator and IPv6 
forwarder./

s3.1.2: s/Therefore, both IPv6 and IPv6

s3.1.2:
OLD:
In some sense, it encourages IPv6 transmission and restrains NAT uses 
compared to NAT44(if used), on which all traffic flows have to be 
traversed and translated. In some cases, NAT64-CGN may serve double 
roles, i.e. a translator and IPv6 forwarder. In mobile networks, NAT64 
is likely deployed as the default gateway serving for all the IPv6 
traffic. The traffic heading to a dual-stack server is only forwarded on 
the NAT64. Therefore, both IPv6 and IPv4 are suggested to be configured 
on the Internet faced interfaces of NAT64. We tested on Top100 websites 
(referring to [Alexa] statistics). 43% of websites are connected and 
forwarded on the NAT64 since those websites have both AAAA and A 
records. With expansion of IPv6 supports, the translation process on 
NAT64 will likely be faded. In addition, it should be noted the 
DNS64-DNSSEC Interaction[RFC6147] may impact the DNS64 process. For 
example, DNS64 will not work with the case, where there is a DNS query 
with the "DNSSEC OK" (DO) bit set and the "Checking Disabled" (CD) bit 
set received.
NEW:
In some sense, it encourages IPv6 transmission and restrains NAT usage 
compared to system using NAT44 (if used), on which all traffic flows 
have to traverse the NAT44 middlebox and be translated in passing. In 
some cases, NAT64-CGN may serve a dual role as both translator and IPv6 
forwarder. In mobile networks, NAT64 is likely deployed as the default 
gateway serving all the IPv6 traffic. The traffic heading to a 
dual-stack server is only forwarded via the NAT64. Therefore, it is 
suggested [or may be RECOMMENDED] that both IPv6 and IPv4 are configured 
on the Internet facing interfaces of NAT64 middleboxes.  We tested the 
configuration of the Top100 websites (as identified in the [Alexa] 
statistics).  43% of websites are [Should this be "would be"] connected 
and forwarded via NAT64 since those websites have both AAAA and A 
records. With the expansion of IPv6 support, the need for the 
translation process on NAT64 middleboxes will likely diminish. In 
addition, it should be noted that the interaction of DNS64 and DNSSEC 
[RFC6147] may impact the DNS64 process. For example, DNS64 will not work 
in the case where a DNS query is received that has the "DNSSEC OK" (DO) 
bit set and the "Checking Disabled" (CD) bit set.


s3.1.3: s/is problematic from multiple-vendor's equipment due to 
inconsistent formats of log records./obtained from equipment supplied by 
multiple vendors may be problematic due to inconsistent log formats./

s3.1.3: This gave me a bit of a laugh...  So having got over my unstable 
user experience (probably due to excessive consumption of beer..)
OLD:
    Since the topology on each
    path is different, it may cause unstable user experiences and some
    degradation of Quality of Experience (QoE) when fallback to the other
    protocol is not powerful enough.
NEW:
    Since the routes taken by the two traffic sets may be different, 
user experiences
    may be inconsistent and there may be some
    degradation of Quality of Experience (QoE) when fallback to the other
    protocol is not sufficiently rapid. [or does this mean that the 
alternative route
    doesn't have enough capacity]

Please clarify.

[I gave up on language corrections at this point as it essentially needs 
a serious rewrite.]

s4.1, last para: Specifying 91.21% of traffic seems inappropriately exact.

s6.1:  It may well be that NAT64-CGN have an FTP ALG .. given the 
general view that FTP shouldn't be used it seems peculiar that this is 
the only default implementation!
Perhaps a comment about this (and maybe even TURNING OFF the FTP ALG) 
seems like an option.





From ari.keranen@ericsson.com  Wed Jan 29 03:46:02 2014
Return-Path: <ari.keranen@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 990B61A03F5 for <gen-art@ietfa.amsl.com>; Wed, 29 Jan 2014 03:46:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.94
X-Spam-Level: 
X-Spam-Status: No, score=-0.94 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RPCOyoXC2g8W for <gen-art@ietfa.amsl.com>; Wed, 29 Jan 2014 03:46:01 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id D8A5A1A038E for <gen-art@ietf.org>; Wed, 29 Jan 2014 03:46:00 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-e5-52e8e9f42871
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 38.AA.04853.4F9E8E25; Wed, 29 Jan 2014 12:45:57 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.41) with Microsoft SMTP Server id 14.2.347.0; Wed, 29 Jan 2014 12:45:56 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 9520411025D; Wed, 29 Jan 2014 13:45:56 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 986CB5680A;	Wed, 29 Jan 2014 13:45:52 +0200 (EET)
Received: from tri60.nomadiclab.com (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 3DFA156767;	Wed, 29 Jan 2014 13:45:52 +0200 (EET)
Message-ID: <52E8E9F3.10100@ericsson.com>
Date: Wed, 29 Jan 2014 13:45:55 +0200
From: =?ISO-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>, Parthasarathi R <partha@parthasarathi.co.in>, "Francis.Dupont@fdupont.fr" <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <201311251357.rAPDvjtA037008@givry.fdupont.fr> <003101cee9f8$63890b50$2a9b21f0$@co.in> <E721D8C6A2E1544DB2DEBC313AF54DE2243BE719@xmb-rcd-x02.cisco.com>
In-Reply-To: <E721D8C6A2E1544DB2DEBC313AF54DE2243BE719@xmb-rcd-x02.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM+Jvje7Xly+CDNad4LKY+vAWm8X7C7oW j6btZLW4+uozi8WdT3NYLSZ/6mN1YPOY8nsjq8e7qX9YPZYs+cnk8WH+F3aPL5c/swWwRnHZ pKTmZJalFunbJXBlnN17mq1gHlPFiu4VzA2Mdxi7GDk5JARMJB58fMAKYYtJXLi3nq2LkYtD SOAEo8Tag4+hnA2MEp+frmOGcPYwSqz6t44FwlnLKNE1r5sVwlnOKLHs8lmwwbwCmhJXVv5m B7FZBFQlpvZuAIuzCdhL3JxwHSwuKpAs8WjbdGaIekGJkzOfgE0VEbjAKPHx1y+wBmaQqU/O s4HYwgK2Eps7l4HFhQQWM0pc3s8FYnMK+ErMv3uGDaLeVuLCnOssELa8xPa3c5ghvlOTuHpu EzNEr6rE1X+vGCcwis5CsnsWkvZZSNoXMDKvYpQsTi0uzk03MtDLTc8t0UstykwuLs7P0ytO 3cQIjLKDW34b7WA8ucf+EKM0B4uSOO911pogIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYye V0XOP9BqvDjd7tqGX1M4y55mnfDZWd1xX2zPwdeeog0bVjOmBzwNDxWdtuPe53idjvXPPszx 7zvwtzW/1G6zs4DVv6X7Jl0LFJY0E7Uw9jGda7/I9utzC93716K//OXjvHVLv8hphu8ySfVV Mam32s6JPbZetqPU9K2HyeVkzf7re+ey79JXYinOSDTUYi4qTgQAqgcHj4ACAAA=
Cc: "Flemming Andreasen \(fandreas\)" <fandreas@cisco.com>, "draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org" <draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-mmusic-sdp-g723-g729-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 11:46:02 -0000

Hi,

Regarding this change, I think we should keep the original version since 
this is a direct quote from RFC4856.


Cheers,
Ari

On 29/01/14 07:07, Muthu Arul Mozhi Perumal (mperumal) wrote:
> |- 1 page 3 (wording suggestion): implied if -> implied when
>
> Addressed.


From mperumal@cisco.com  Tue Jan 28 21:07:29 2014
Return-Path: <mperumal@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9189C1A0280 for <gen-art@ietfa.amsl.com>; Tue, 28 Jan 2014 21:07:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vqh3BVF4qH-0 for <gen-art@ietfa.amsl.com>; Tue, 28 Jan 2014 21:07:26 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id BB5861A0193 for <gen-art@ietf.org>; Tue, 28 Jan 2014 21:07:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3559; q=dns/txt; s=iport; t=1390972044; x=1392181644; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Hbh9WYg9M986x/fxwrUFqeeyyDPA7kI3qEC6QQJ+IFk=; b=QLwOGwlns0SnrLjdT6mh/6IT7iRRb4lB0FrotoZpJqf6hE03ZlhlLdns ZxlhztoCJdy2mbckiVNRXf6YD3FfXZoKOpG6tTlXxSOaRHnbI/vDxcuUA /c+vId/jDF3pG8jjGnh1ShS4agPRnIUF2hEZGqCdXAC0EMKgbiEFo2Emh M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAHuL6FKtJXHB/2dsb2JhbABagww4Vr0EgQ8WdIIlAQEBBCdSDAQCAQgQAQMBAQELHQcyFAkIAQEEAQ0FCId9DcksF40NgUExBwaDHoEUBIkRkEmQbYMtgio
X-IronPort-AV: E=Sophos;i="4.95,740,1384300800"; d="scan'208";a="16282791"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by alln-iport-7.cisco.com with ESMTP; 29 Jan 2014 05:07:23 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id s0T57NIX023043 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Jan 2014 05:07:23 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.29]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0123.003; Tue, 28 Jan 2014 23:07:23 -0600
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: Parthasarathi R <partha@parthasarathi.co.in>, "Francis.Dupont@fdupont.fr" <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: review of draft-ietf-mmusic-sdp-g723-g729-04.txt
Thread-Index: Ac7p5lgX/OVwt+Nw0E+9CmXB4mmOXQAEYCHQDK21nNA=
Date: Wed, 29 Jan 2014 05:07:22 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE2243BE719@xmb-rcd-x02.cisco.com>
References: <201311251357.rAPDvjtA037008@givry.fdupont.fr> <003101cee9f8$63890b50$2a9b21f0$@co.in>
In-Reply-To: <003101cee9f8$63890b50$2a9b21f0$@co.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [72.163.208.169]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 29 Jan 2014 05:10:35 -0800
Cc: "Flemming Andreasen \(fandreas\)" <fandreas@cisco.com>, =?iso-8859-1?Q?Ari_Ker=E4nen_=28ari=2Ekeranen=40ericsson=2Ecom=29?= <ari.keranen@ericsson.com>, "draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org" <draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-mmusic-sdp-g723-g729-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 05:07:29 -0000

Hi Francis,

We have incorporated your comments in the next revision (will be publishing=
 it shortly).=20

|- Abstract page 1: usually the Abstract should not reference an RFC
|  by its number. IMHO here it is the exception: the I-D will be
|  included into the next revision of the RFC.

We have removed the reference to RFC4856 from the Abstract.

|- I don't like the annexa/annexb name (nor my spell checker) but
|  they are the names used by the RFC...

Right, annexa/annexb name is unavoidable.

|- ToC page 2 and 7 page 7: Acknowledgement -> Acknowledgment

Addressed.

|- 1 page 3 (wording suggestion): implied if -> implied when

Addressed.

|- 1 page 3: BTW IMHO "use or preferred" should be interpreted
|  as preferred in the offer and use in the answer so the RFC is
|  correct. But as you mentioned some implementations didn't follow
|  the interpretation so I understand why a clarification new
|  document (this I-D) is needed. And of course I fully agree with
|  3.1 and 3.2.

You got it right..

|- 7 page 7: Note I checked the spelling of "Harprit S. Chhatwal
| (InnoMedia)" (uncommon for our eyes but correct).

Thank you for that..

Muthu

|-----Original Message-----
|From: Parthasarathi R [mailto:partha@parthasarathi.co.in]
|Sent: Monday, November 25, 2013 9:37 PM
|To: Francis.Dupont@fdupont.fr; gen-art@ietf.org
|Cc: draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org
|Subject: RE: review of draft-ietf-mmusic-sdp-g723-g729-04.txt
|
|Hi Francis.Dupont@fdupont.fr,
|
|Thanks a lot for the detailed review comments.
|
|I'll discuss with Muthu (Co-author) and then incorporate your comments in
|the next revision.
|
|Thanks
|Partha
|
|> -----Original Message-----
|> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
|> Sent: Monday, November 25, 2013 7:28 PM
|> To: gen-art@ietf.org
|> Cc: draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org
|> Subject: review of draft-ietf-mmusic-sdp-g723-g729-04.txt
|>
|> I am the assigned Gen-ART reviewer for this draft. For background on
|> Gen-ART, please see the FAQ at
|>
|> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
|>
|> Please resolve these comments along with any other Last Call comments
|> you may receive.
|>
|> Document: draft-ietf-mmusic-sdp-g723-g729-04.txt
|> Reviewer: Francis Dupont
|> Review Date: 20131120
|> IETF LC End Date: 20131127
|> IESG Telechat date: unknown
|>
|> Summary: Ready
|>
|> Major issues: None
|>
|> Minor issues: None
|>
|> Nits/editorial comments:
|>  - Abstract page 1: usually the Abstract should not reference an RFC
|>   by its number. IMHO here it is the exception: the I-D will be
|>   included into the next revision of the RFC.
|>
|>  - I don't like the annexa/annexb name (nor my spell checker) but
|>   they are the names used by the RFC...
|>
|>  - ToC page 2 and 7 page 7: Acknowledgement -> Acknowledgment
|>
|>  - 1 page 3 (wording suggestion): implied if -> implied when
|>
|>  - 1 page 3: BTW IMHO "use or preferred" should be interpreted
|>   as preferred in the offer and use in the answer so the RFC is
|>   correct. But as you mentioned some implementations didn't follow
|>   the interpretation so I understand why a clarification new
|>   document (this I-D) is needed. And of course I fully agree with
|>   3.1 and 3.2.
|>
|>  - 7 page 7: Note I checked the spelling of "Harprit S. Chhatwal
|>   (InnoMedia)" (uncommon for our eyes but correct).
|>
|> Regards
|>
|> Francis.Dupont@fdupont.fr


From lear@cisco.com  Wed Jan 29 08:21:46 2014
Return-Path: <lear@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A0BA1A03DF; Wed, 29 Jan 2014 08:21:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.537
X-Spam-Level: 
X-Spam-Status: No, score=-7.537 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SORTED_RECIPS=2.499, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jqYNtAmpaooi; Wed, 29 Jan 2014 08:21:45 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 113E61A03D4; Wed, 29 Jan 2014 08:21:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=823; q=dns/txt; s=iport; t=1391012502; x=1392222102; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=kEGMmm+BpBoFn2QsdBgGVKeeXmvbzN8Q3TYsTD72eqQ=; b=FizJD8zEYw7AEq7grfO6mlrSBeW9RHYmChdXJxycaLwo6ugaCT/JyPiD mc7nTURi38wQEWzez4JkQ/Z6cChpvLSnnWtjIHWULJHdNwAeWiSbEBUAr qil2CxB+xZ0JOueIIvISG/PD6tuZ+GVf9dhxB1z4WE78/Ip06QDavppMM o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AncIAIkp6VKQ/khL/2dsb2JhbABZgwyEDLoBgQcWVh6CJQEBAQMBI1UBBQsLGgIFFgsCAgkDAgECASsaBgEMAQcBAYd5CKpCnzsXgSmMfgFXB4JvgUkBA5gokh+DLjuBLAEf
X-IronPort-AV: E=Sophos;i="4.95,742,1384300800";  d="scan'208";a="4368257"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 29 Jan 2014 16:21:41 +0000
Received: from mctiny.local ([10.61.174.85]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0TGLevD012624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jan 2014 16:21:41 GMT
Message-ID: <52E92A94.9000903@cisco.com>
Date: Wed, 29 Jan 2014 17:21:40 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com> <52E69A54.9030104@isode.com> <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com> <A122D59D-B356-4A92-B0C8-9E31CB938FF9@isode.com>
In-Reply-To: <A122D59D-B356-4A92-B0C8-9E31CB938FF9@isode.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dcridland@arcode.com" <dcridland@arcode.com>, "imapext@ietf.org" <imapext@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 16:21:46 -0000

Alexey,

On 1/28/14, 9:37 AM, Alexey Melnikov wrote:

> I think David's right that some version of what Eliot said:
>>> there
>>> is a requirement for strict syntax parsing.  If the client blows it in
>>> any way, the server SHOULD return an error with a BAD response.
>> ...should be added to the section about the line-length limit.  A
>> sentence or two should do nicely.
> Yes, I agree.
>
>
>
Then my suggestion is to push out a new version with  some text along
these lines before the teleconference, please (tomorrow would be
ideal).  I will note that I believe this advice to be general in nature
and not limited to this capability, but we certainly can reinforce the
point here, and restate it if/when someone does an update to 3501
(probably when I have grandchildren, I would think).

Eliot

From mperumal@cisco.com  Wed Jan 29 09:45:52 2014
Return-Path: <mperumal@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5009C1A0352 for <gen-art@ietfa.amsl.com>; Wed, 29 Jan 2014 09:45:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.736
X-Spam-Level: 
X-Spam-Status: No, score=-14.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A0z6kZx1VXMW for <gen-art@ietfa.amsl.com>; Wed, 29 Jan 2014 09:45:51 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 11F6E1A0276 for <gen-art@ietf.org>; Wed, 29 Jan 2014 09:45:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=780; q=dns/txt; s=iport; t=1391017548; x=1392227148; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=547yVA9nKfGhi590cmqL+vgKdEegYuAPDeYgF7J0vfA=; b=lGPt32M6RvPnCzXUX80I6taUXbOuModHwKuCkGF/RcGNeqZrhhVT7OOM ruFSxd/HYBDWMKGqheKqPugi08O19oFG2+2xFuD9ewGIAh3pgdEwphnnD OUl9NA7FcOcpUIV2+f2eXKy1pvEutpiHvZu/PcKZhV5+D3iFQC9s8aM4U Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFABU+6VKtJXG9/2dsb2JhbABZgwyBDr0CgQcWdIIlAQEBBCdSDAQCAQgQAQQBAQsdBzIUCQgBAQQBDQUIh33KDxeOTjEHBoMegRQBA4kRoTaDLYIq
X-IronPort-AV: E=Sophos;i="4.95,743,1384300800"; d="scan'208";a="300504079"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-7.cisco.com with ESMTP; 29 Jan 2014 17:45:35 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0THjZ95016154 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Jan 2014 17:45:35 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.29]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Wed, 29 Jan 2014 11:45:34 -0600
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>, Parthasarathi R <partha@parthasarathi.co.in>, "Francis.Dupont@fdupont.fr" <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: review of draft-ietf-mmusic-sdp-g723-g729-04.txt
Thread-Index: Ac7p5lgX/OVwt+Nw0E+9CmXB4mmOXQAEYCHQDK21nNAAGtGngAAADQdw
Date: Wed, 29 Jan 2014 17:45:33 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE2243BF434@xmb-rcd-x02.cisco.com>
References: <201311251357.rAPDvjtA037008@givry.fdupont.fr> <003101cee9f8$63890b50$2a9b21f0$@co.in> <E721D8C6A2E1544DB2DEBC313AF54DE2243BE719@xmb-rcd-x02.cisco.com> <52E8E9F3.10100@ericsson.com>
In-Reply-To: <52E8E9F3.10100@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.54.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Flemming Andreasen \(fandreas\)" <fandreas@cisco.com>, "draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org" <draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-mmusic-sdp-g723-g729-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 17:45:52 -0000

Hi Ari,

Good catch. Will retrain the existing text for this one..

thanks,
Muthu

|-----Original Message-----
|From: Ari Ker=E4nen [mailto:ari.keranen@ericsson.com]
|Sent: Wednesday, January 29, 2014 5:16 PM
|To: Muthu Arul Mozhi Perumal (mperumal); Parthasarathi R; Francis.Dupont@f=
dupont.fr; gen-art@ietf.org
|Cc: draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org; Flemming Andreasen=
 (fandreas)
|Subject: Re: review of draft-ietf-mmusic-sdp-g723-g729-04.txt
|
|Hi,
|
|Regarding this change, I think we should keep the original version since
|this is a direct quote from RFC4856.
|
|
|Cheers,
|Ari
|
|On 29/01/14 07:07, Muthu Arul Mozhi Perumal (mperumal) wrote:
|> |- 1 page 3 (wording suggestion): implied if -> implied when
|>
|> Addressed.


From alexey.melnikov@isode.com  Thu Jan 30 10:19:20 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A3891A0295; Thu, 30 Jan 2014 10:19:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3b03o9xTxmWd; Thu, 30 Jan 2014 10:19:17 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 249EE1A0072; Thu, 30 Jan 2014 10:19:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1391105953; d=isode.com; s=selector; i=@isode.com; bh=QinOrxgtHNxOO+bEz5+TFPJ1uFCHTJqxEUBpsLGo1sw=; 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=XAkv+AH+1F4qMMBg2HdzY3laOWzkKAK9WEWseB4iEi4btkVv23CxduOywX/aBpkhGwoPRv 873akNwAMeGGF17RRIBZ40SfmM9mkQO1J5k39NRSnpISF2HqXQuxIDvy3VrS2XHzLnMnUJ UPQOpjmnehYoptL/dMjHYtofYJ+KaKs=;
Received: from [172.16.1.29] (richard.isode.com [62.3.217.249])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <UuqXnwAIP7-M@waldorf.isode.com>; Thu, 30 Jan 2014 18:19:13 +0000
Message-ID: <52EA97A5.6080006@isode.com>
Date: Thu, 30 Jan 2014 18:19:17 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
To: "Black, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com> <8D3D17ACE214DC429325B2B98F3AE712026F162227@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026F162227@MX15A.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, Eliot Lear <lear@cisco.com>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 18:19:20 -0000

Hi David,

On 27/01/2014 14:20, Black, David wrote:
> Hi Eliot,
>
> Regarding line length:
>
>> As the draft indicates, this is problematic for the two extensions in
>> question. We have discussed this limitation in the working group, and
>> nobody seems to be concerned.  That's due to two factors, I think:
>> first, RFC 2683 is not normative (informational).  I am unaware of any
>> strict line length limitation in RFC 3501, for instance.  Instead, there
>> is a requirement for strict syntax parsing.  If the client blows it in
>> any way, the server SHOULD return an error with a BAD response.
> The latter two sentences would be good to add to the draft in some form.
>
> My primary concern is what happens if the client sends a rather long
> line to a server that isn't prepared to cope, and the latter sentence
> would address it.  That could be accompanied by some sort of statement
> that servers that implement this extension need to be prepared to cope
> with longer lines.
I added some text on this issue. It will appear in -10 which I will post 
shortly.
> I'll leave the downref as a process concern for you (WG chair) and Barry (AD)
> to work out.
>
> Thanks,
> --David
>
>> -----Original Message-----
>> From: Eliot Lear [mailto:lear@cisco.com]
>> Sent: Monday, January 27, 2014 8:01 AM
>> To: Black, David; Alexey Melnikov (alexey.melnikov@isode.com);
>> dcridland@arcode.com; General Area Review Team (gen-art@ietf.org)
>> Cc: Barry Leiba (barryleiba@computer.org);ietf@ietf.org;imapext@ietf.org
>> Subject: Re: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
>>
>> Hi Dave,
>>
>> First, thank you for your review.  I personally appreciate to the time
>> you put in to all of your reviews.
>>
>> On 1/27/14, 3:06 AM, Black, David 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-qresync-rfc5162bis-09
>>> Reviewer: David L. Black
>>> Review Date: January 26, 2014
>>> IETF LC End Date: January 27, 2014
>>>
>>> Summary:
>>> This draft is basically ready for publication, but has minor issues that
>>> should be fixed before publication.
>>>
>>> This draft consolidates RFC 4551 (IMAP Conditional STORE) and RFC 5162
>>> (IMAP Quick Mailbox Resynchronization) into a single document and makes
>>> a few minor updates.  It also updates the command line length
>>> recommendation in RFC 2683 to support the longer command lines that
>>> can occur with these extensions.
>>>
>>> As this is an update, I checked the diffs against RFC 4551 and RFC 5162;
>>> they look reasonable.  I found one minor issue that should be relatively
>>> easy to address.
>>>
>>> Minor Issues:
>>>
>>> The command line length change in Section 4 applies to all IMAP commands,
>>> and hence affects old servers, including those that don't implement either
>>> of the extensions in this draft. That raises a backwards compatibility
>>> concern - what happens when a new client sends a > 1000 character command
>>> line to an old server that isn't expecting more than 1000 characters?
>> As the draft indicates, this is problematic for the two extensions in
>> question. We have discussed this limitation in the working group, and
>> nobody seems to be concerned.  That's due to two factors, I think:
>> first, RFC 2683 is not normative (informational).  I am unaware of any
>> strict line length limitation in RFC 3501, for instance.  Instead, there
>> is a requirement for strict syntax parsing.  If the client blows it in
>> any way, the server SHOULD return an error with a BAD response.
>>
>> This having been said, while the working group has discussed this
>> matter, it would be good to hear any additional voices of concern, in
>> the interests of interoperability.
>>
>> This takes us to your next point:
>>
>>> One possibility would be to apply the larger length recommendation only
>>> after the client determines that the server supports at least one of
>>> these extensions.
>>>
>>> Nits/editorial comments:
>>>
>>> The update to RFC 2683 would be easier to find from the table of contents
>>> if the title of Section 4 were changed to "Long Command Lines (Update to
>>> RFC 2683)".
>>>
>>> idnits 2.13.01 got confused by the command line examples, and flagged a
>>> downref:
>>>
>>>    ** Downref: Normative reference to an Informational RFC: RFC 2683
>>>
>>> That downref appears to be ok and intended, as noted in the shepherd's
>>> writeup.
>> This will be addressed in a forthcoming update.  Barry has "educated" us
>> that really this is NOT an update to RFC2683, where the advice given in
>> that document is superceded by a specific option.  As such, this error
>> will evaporate.
>>
>>


From david.black@emc.com  Thu Jan 30 12:24:39 2014
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06F4D1A044E; Thu, 30 Jan 2014 12:24:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YmNPA31DayuB; Thu, 30 Jan 2014 12:24:36 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4C71A03F0; Thu, 30 Jan 2014 12:24:36 -0800 (PST)
Received: from maildlpprd06.lss.emc.com (maildlpprd06.lss.emc.com [10.253.24.38]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0UKOTBt031367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Jan 2014 15:24:30 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s0UKOTBt031367
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1391113471; bh=WVx5XHAyyR0SQ7H1BQsduE8FabE=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=AzQw1ZHolXzXzlSPkEWUvyaTU1c2uC0964OET88zeBK2UnTda2ZUp5MyiFZdaZ0+y n14Ql1j768f2zLWUcuSwFb6k3G/SUSK97hzQ6oO/d+2Eb+srq30lewJiuDl2rcjO1/ lpVgCJ9cAC92brg+u+2oeEuDSMhWPvvnqQ8xFnz0=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s0UKOTBt031367
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd06.lss.emc.com (RSA Interceptor); Thu, 30 Jan 2014 12:24:15 -0800
Received: from mxhub34.corp.emc.com (mxhub34.corp.emc.com [10.254.93.82]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0UKODpT009711 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 Jan 2014 15:24:14 -0500
Received: from mx15a.corp.emc.com ([169.254.2.218]) by mxhub34.corp.emc.com ([::1]) with mapi; Thu, 30 Jan 2014 15:24:13 -0500
From: "Black, David" <david.black@emc.com>
To: "Alexey Melnikov (alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>,  "dcridland@arcode.com" <dcridland@arcode.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Thu, 30 Jan 2014 15:24:12 -0500
Thread-Topic: Gen-ART review of draft-ietf-qresync-rfc5162bis-10
Thread-Index: Ac8d+TzKew/VpFHeS7+t6IS3cG+bfg==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71202704EC4E5@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-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: public
Cc: "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>, "ietf@ietf.org" <ietf@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-qresync-rfc5162bis-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 20:24:39 -0000

The -10 version of this draft addresses all of the items noted in the
Gen-ART review of the -09 version.  It's ready for publication.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Sunday, January 26, 2014 9:07 PM
> To: Alexey Melnikov (alexey.melnikov@isode.com); dcridland@arcode.com; Ge=
neral
> Area Review Team (gen-art@ietf.org)
> Cc: Black, David; Barry Leiba (barryleiba@computer.org); imapext@ietf.org=
;
> ietf@ietf.org
> Subject: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
>=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-qresync-rfc5162bis-09
> Reviewer: David L. Black
> Review Date: January 26, 2014
> IETF LC End Date: January 27, 2014
>=20
> Summary:
> This draft is basically ready for publication, but has minor issues that
> should be fixed before publication.
>=20
> This draft consolidates RFC 4551 (IMAP Conditional STORE) and RFC 5162
> (IMAP Quick Mailbox Resynchronization) into a single document and makes
> a few minor updates.  It also updates the command line length
> recommendation in RFC 2683 to support the longer command lines that
> can occur with these extensions.
>=20
> As this is an update, I checked the diffs against RFC 4551 and RFC 5162;
> they look reasonable.  I found one minor issue that should be relatively
> easy to address.
>=20
> Minor Issues:
>=20
> The command line length change in Section 4 applies to all IMAP commands,
> and hence affects old servers, including those that don't implement eithe=
r
> of the extensions in this draft. That raises a backwards compatibility
> concern - what happens when a new client sends a > 1000 character command
> line to an old server that isn't expecting more than 1000 characters?
>=20
> One possibility would be to apply the larger length recommendation only
> after the client determines that the server supports at least one of
> these extensions.
>=20
> Nits/editorial comments:
>=20
> The update to RFC 2683 would be easier to find from the table of contents
> if the title of Section 4 were changed to "Long Command Lines (Update to
> RFC 2683)".
>=20
> idnits 2.13.01 got confused by the command line examples, and flagged a
> downref:
>=20
>   ** Downref: Normative reference to an Informational RFC: RFC 2683
>=20
> That downref appears to be ok and intended, as noted in the shepherd's
> writeup.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From ben@nostrum.com  Thu Jan 30 14:51:13 2014
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0068A1A04DD; Thu, 30 Jan 2014 14:51:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D_wL9pIoEz_W; Thu, 30 Jan 2014 14:51:09 -0800 (PST)
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 873541A0513; Thu, 30 Jan 2014 14:51:09 -0800 (PST)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0UMoxwd096662 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 30 Jan 2014 16:51:02 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <52E16808.3070308@deployingradius.com>
Date: Thu, 30 Jan 2014 16:50:58 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <807D4BB4-7C1C-4668-8F31-85CD1B080EE6@nostrum.com>
References: <C3DF6E99-2B7E-4606-A8F6-5D76C338B265@nostrum.com> <52E16808.3070308@deployingradius.com>
To: Alan DeKok <aland@deployingradius.com>
X-Mailer: Apple Mail (2.1827)
Received-SPF: pass (shaman.nostrum.com: 173.172.146.58 is authenticated by a trusted mechanism)
Cc: radext@ietf.org, draft-ietf-radext-dtls.all@tools.ietf.org, "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-Art Early Review of draft-ietf-radext-dtls-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 22:51:13 -0000

Jouni poked me to review 08. In the process of doing that, I found your =
email that I had somehow missed. Apologies for the late response. I've =
removed sections that do not seem to require further discussion or =
comment.

Thanks!

Ben.

On Jan 23, 2014, at 1:05 PM, Alan DeKok <aland@deployingradius.com> =
wrote:

> Ben Campbell wrote:
>> *** Major issues:

[...]

>> -- section 3, 2nd paragraph:  "... long-term use of RADIUS/UDP is NOT =
RECOMMENDED."=20
>>=20
>> While I agree with the sentiment, that's not an appropriate assertion =
for an experimental RFC. It would either need to go into an =
standards-track update to the RADIUS spec, or a BCP.
>=20
>  OK.

Version 08 partially addresses this by changing "NOT RECOMMENDED" to =
lower case. I don't think that's sufficient; it's not a good idea to =
rely on case alone to distinguish normative from non-normative text. I =
propose changing the sense of the statement to something along the lines =
of "The author recommends...".=20

(Unlike some reviewers, I will not go so far as to say the word "should" =
should never be used non-normatively, since the resulting text tends to =
be awkward. But I think the NOT RECOMMENDED/not recommended difference =
can be handled with more clearly non-normative text without introducing =
the same awkwardness.)

>=20
>> (Also applies to the reiteration in 10.1)
>=20
>  I'm less sure of that.  10.1 doesn't re-iterate the point above.  It
> makes a security recommendation.  i.e. allowing secure and insecure
> traffic from the same client is bad.
>=20
>  This imposes no change on existing RADIUS/UDP clients, as they will
> only be sending RADIUS/UDP.  It does impose security requirements on
> RADIUS/DTLS clients and servers, which is the intent of the section.
>=20

The text to which I refer says "It is RECOMMENDED that all RADIUS =
clients and servers implement this specification, or [RFC6614]." That =
seems to to apply a new normative statement to all RADIUS clients and =
servers, and does not in any way seem scoped to "RADIUS/DTLS clients and =
servers".


>> *** Minor issues:
>>=20
>> -- General:  It might be worth some text on why this is experimental =
rather than informational. Is there any plan to evaluate the =
implementation results? Is there an expectation that a future =
RADIUS/DTLS spec could become standards-track? Is there any plan to =
evaluate the outcome of this document?
>=20
>  It's probably easiest to reference Section 1.3 of RFC 6614.  The
> issues are the same.

I don't think that's the best approach. That discussion is specific to =
6614. Referencing it would leave the reader to infer how that discussion =
would apply to this draft. I think it would be better to include a =
similar discussion here.

>=20
>> -- Section 1, 2nd paragraph:
>>=20
>> Isn't this true for almost any use of IPSec? Is there some specific =
reason this is worse for RADIUS than for other protocols?
>=20
>  It's true for most protocols.

It's worth mentioning that.

[...]

>> The firewall rule recommendations in the 3rd sentence seems odd, =
since it seems like any protocol over DTLS would pass. Also, does this =
imply a recommendation that firewalls with DPI be used in the first =
place, since the absence of such a firewall has the same effect as =
having one that doesn't enforce the protocol? (Is there a reason a =
protocol spec should recommend firewall rules in the first place, other =
than to mention places where certain firewall rules might prevent =
interfere with operation?)
>=20
>  I'll clarify it, and move it to the Security Considerations section.

The clarification added at the end of  section 10 in version 08 mostly =
addresses this. But I assume that the point is to make sure no one sends =
non-protected RADIUS over that port, but it doesn't prevent someone from =
sending some other protocol over DTLS over the same port, correct? If =
so, I think that's worth a mention.

[...]

>> -- 2.2 and children:
>>=20
>> I find this section confusing as to where to find the authoritative =
text. Some, but not all, of the material from 6614 is repeated as =
normative text in later sections.  The description of this draft as =
applying 'semantic "patches"' to 6614 seems to imply you mean the 6114 =
text, with these patches applied, to be normative, which creates some =
potential conflicts. If, on the other hand, 2.2 (.x) is intended more as =
a informative description of the differences, please say so.
>=20
>  What conflicts occur?  The intent is show this specification as a
> revision / patch from 6614.

On a quick re-review, I have not found a specific example of conflicting =
or redundant normative text in version 08. I thought I had run into some =
around peer authentication before, but either I was mistaken or the 08 =
updates corrected it.

[...]

>=20
>> If so, it might make more sense to refer to the port by role rather =
than number when discussing port related behavior. (I note that 6614 =
only mentions the port number in the initial assignment, the IANA =
considerations, and the appendix.)
>=20
>  Maybe.  That makes the text a bit more awkward.  "UDP/2083" would get
> replaced by "that or any other port you happen to use".
>=20

It doesn't need to be that hard. One can start by saying something like =
the RADIUS/DTLS port is UDP/2083 by default, but administrators can =
assign other, non-standard values. Then all future mentions refer to =
"the RADIUS/DTLS port" rather than UDP/2023. But in any case, this is =
only a mild suggestion; with the addition of the disclaimer to section =
3.1 of version 08, the future UDP/2083 references are less troublesome.


>> -- 3.2, last paragraph:
>>=20
>> Can you elaborate on the bid down attack? Given that the use of dtls =
is configured, rather than negotiated, how would an attacker bid it =
down?
>=20
>  When secure and insecure packets are allowed from the same client, a
> malicious or broken client can choose the insecure one.  That's bad,
> when the intent is to use DTLS.

One assumes a "malicious or broken" client already has access to the =
cleartext messages. Are we talking about a MiTM "client"? Are there =
attacks where a third party can induce the client or server to send =
unprotected packets, even with no signaled negotiation? I can imagine =
one for the specific case where a node falls back to clear text if DTLS =
packets fail; an attacker could induce failures for DTLS packets. (Thus =
the next comment.)

>=20
>> -- 4, 2nd paragraph:
>>=20
>> Seems like an (or maybe even the) important point would be that a =
client should not fall back to cleartext if a server appears to not =
support it.
>=20
>  That's reasonable.
>=20
>> -4, 3rd paragraph:
>>=20
>> Is the recommendation to use a local proxy for all clients, or just =
those implemented as multiple processes?
>=20
>  Only ones with multiple processes.

The text seems to say something to the effect of " Some RADIUS clients =
have historically been implemented as multiple independent processes, =
therefore [all] RADIUS clients should use a local proxy".  I think you =
mean to say something more like "Some RADIUS clients have historically =
been implemented as multiple independent processes; clients that are =
implemented that way should use a local proxy."=20

>=20
>> -- 5.1.1, third paragraph: "In those cases, the implementation MAY =
delete the underlying session"
>>=20
>> Can you elaborate on why that's a MAY and not a SHOULD or MUST?
>=20
>  There was a long discussion about this on the RADEXT list.  In short,
> the session MUST be closed when there are security issues, or when the
> tunneled data isn't RADIUS.
>=20
>  When security is OK and the tunneled data is RADIUS, it's OK to
> silently drop the unexpected RADIUS packets.  Doing so doesn't cause =
any
> problems.

It would be helpful to add a couple of sentences to that effect.=20


>=20
>=20

>> -- 5.1.1, 4th paragraph:
>>=20
>> This paragraph rephrases 2119 normative language with more normative =
language. That creates confusion about which text is authoritative. I =
suggest either keeping the second paragraph and deleting the first, or =
make the second non-normative.
>=20
>  I'm not sure what you mean here.  The two paragraphs discuss =
different
> things, so deleting one isn't possible.

The opening sentence of the second paragraph says, "The above paragraph =
can be rephrased more generically", then appears to go on to do so. That =
makes it sound like the second paragraph asserting effectively the same =
normative requirements in more general terms. If you intend each =
paragraph to stand alone, then I suggest deleting that sentence.

>=20
>> -- 5.1.1, 6th paragraph: "The timestamp SHOULD be updated ..."
>>=20
>> Why not MUST?
>=20
>  The granularity could be 1 second, with packets being received 1000's
> of times per second.
>=20

It would be helpful to elaborate on that in the text. Your comment makes =
me thing it would be also worth having some guidance on a reasonable =
resolution for the time stamp.

If you really expect 1 second resolutions, then it might be better to =
say something like "The timestamp MUST be updated if a valid message or =
heartbeat is received during the last time interval."

[...]

>=20
>> -- 6, 1st paragraph:
>>=20
>> You mention that these are implementation guidelines, and not part of =
the protocol. But the section contains 2119 style normative =
requirements. in general, that's not appropriate unless non-compliance =
impact interoperability or create some other Bad Thing, such as insecure =
behavior, excessive bandwidth usage, congestion, etc. Implementation =
guidance for behavior that is not externally observable should use =
non-normative.
>=20
>  OK.
>=20
>> -- 6, 2nd and 3rd paragraph:
>>=20
>> The RECOMMENDation to allow administrative entry of keys and to =
derive keys from a PRNG seem contradictory.
>=20
>  The idea is that admins shouldn't be entering "0xabababab" as a key.
> Instead, they get secure keys from a secure location.  People are
> notoriously bad at creating randomness.
>=20

So paragraph 3 is a requirement on the administrator, rather than on the =
implementor? Or do you mean to say the implementation should provide =
tools for random key generation?

[...]


>> -- 9
>>=20
>> Why not choose a new port? Is there absolute certainty this won't =
conflict with the previous usage? I do note that 6414 made the same =
choice, so I guess consistency with radius/TLS has some value. But that =
draft talks about compatibility between radsec and radius/tls, which is =
not mentioned here.
>=20
>  No one is using UDP/2083 for anything.  Re-using it is OK.

Does that mean that RadSec is not used at all by anyone? or that this =
draft is compatible with it?

[...]

>> -- 10.1, 3rd paragraph:
>>=20
>> It would be helpful to have guidance on how to match a certificate to =
a client or server identity,
>=20
>  I'll add a note to see RFC 6614 Section 2.5.

I see you added that to section 10.3, 3rd paragraph. But does that =
contradict the statement in 2.2.1 that 6614 section 2.5 does not apply =
to RADIUS/DTLS?

[...]


>> -- 10.2, 2nd paragraph:
>>=20
>> This is redundant with previous normative requirements. (Also =
contradictory, since the previous text said "SHOULD", and contradictory =
guidance on what to do when the limit is exceeded.)
>=20
>  I've fixed the text to be consistent.

The paragraph is still redundant with the new text in 5.1.1 (which says =
you MUST either drop old sessions or limit creation of new ones.)


>=20
>> -- 10.3, 4th paragraph:
>>=20
>> Does this need to be as strong as SHOULD? Is this likely to conflict =
with dynamic discovery, should it ever exist?
>=20
>  RADIUS is a critical piece of infrastructure.  Exposing your RADIUS
> server to the entire IPv4 range is a bad idea.

That's true of many protocols that don't have normative requirements =
about IP filtering. This is more an operational issue than an =
implementation one, and it may not be the best choice for all (or even =
most) deployments. There may be some advantage in filtering packets =
before they get to the DTLS layer, but IP filtering is trivial to =
defeat, and it has real administrative costs. For example, any peer =
network renumbering has to be coordinated across all of your RADIUS =
nodes.

I agree it makes sense to point out that IP filtering might be helpful. =
But I think a normative SHOULD is excessive.

>=20
>  The recommendation is a SHOULD so that it does not conflict with
> dynamic discovery.
>=20

If it stays normative, It would be worth mentioning that as an example =
of why it's a SHOULD rather than a MUST.

>> -- 10.3, 5th and 6th paragraphs:
>>=20
>> Paragraph 5 says credentials should be statically configured. To me, =
"credentials" means "the certificate" in this case. That seems to =
disallow things like statically configuring a name that must match a =
certificate (perhaps signed by a CA.)
>=20
>  Credentials for the client should be statically configured.  It could
> be a PSK, or a certificate.
>=20
>  I'm not sure what "name" would match a certificate.  The document
> doesn't refer to names, and doesn't use names for anything.

The whole point of a certificate is to bind a key pair to an identity =
(often, a name.)

Example: I enter the name "trusted-peer.example.com" in a table. If a =
(perhaps dynamically discovered) peer presents certificate with a CN or =
SAN that matches "trusted-peer.example.com", and that certificate is =
issued by a CA that I trust, then I trust that peer.=20

>=20
>> Paragraph 6 seems to entirely contradict paragraph 5 by recommending =
private CAs, and accepting any peer that presents a cert signed by that =
CA. That's pretty much the opposite of statically configured =
credentials. (Paragraph 8 also seems to contradict the static =
configuration part.)
>=20
>  Both client and server still need to be configured with the private
> CA.  The alternative is to allow anyone to connect with any =
credentials,
> which seems odd.
>=20

That's static configuration of your trusted CA(s). That's not the same =
thing as static configuration of peer credentials, and it doesn't imply =
the static relationship between clients and servers mentioned in =
paragraph 5.

[...]

>=20
>> -- 10.4:
>>=20
>> The guidance in the last paragraph does not make sense. The section =
seems to say that NATs will break radius/dtls, so you should use dtls =
when behind a NAT.
>=20
>  RADIUS/UDP clients should not be behind a NAT.  I'll clarify.

Do you mean RADIUS/UDP or RADIUS/DTLS? If the former, then that brings =
back the problem of making normative statements about the base protocol. =
Also, I'm still confused by the fact the the 2nd sentence of the last =
paragraph says "If clients are located behind a NAT gateway, then a =
secure transport such as DTLS MUST be used." Given that the previous =
paragraph seems to say that RADIUS/DTLS has issues over NAT, I'm =
surprised to see it listed as mitigating NATs.

>=20
>> -- 10.6, last paragraph:
>>=20
>> Can you elaborate on this? Why would an unauthorized 3rd party be =
able to get packets past the DTLS layer? OTOH, If an authorized client =
is sending invalid radius packets, wouldn't  you want to terminate the =
session?
>=20
>  That was a *long* discussion on the RADEXT list.
>=20
>  A server may be at protocol rev X, and a client may be at protocol =
rev
> X+1.  If the client sends packets allowed by X+1, the server should
> ignore them, as it does today with RADIUS/UDP.  Closing the connection
> is not necessary.

I think your previous answer about sending packets with the same 4-tuple =
answers this as well.

>=20
>> -- 10.7
>>=20
>> Redundant normative requirements (This is at least the third time the =
separate process issue and local proxy guidance has been described.)
>=20
>  It's a security considerations section, and needs to mention this.  =
It
> refers to Section 6.1, and adds new text explaining the security
> benefits of the approach.

I agree it should be reiterated, but not _normatively_. In generally, =
you don't want to have the same normative requirement stated more than =
once. It makes sense for the security consideration section to say =
something like "Section XX recommends that clients use a local proxy"  =
But it's best to avoid any language that obscures which bit of text is =
authoritative for a given normative requirement. (There can be only =
one...)

I also notice the language here also fails to account for the fact that =
the requirement only applies to clients implemented as multiple =
independent instances. This could be fixed by something really simple =
like saying "... such clients ..." instead of "... clients... " in the =
second paragraph.

>=20
>>=20
>>=20
>> *** Nits/editorial comments:
>>=20
>> -- IDNits reports some issues; please check.
>=20
>  They're fine.
>=20
>> -- Abstract:
>> Please avoid citations in the abstract. Please consider removing the =
"scare quotes".
>=20
>  OK.
>=20
>> -- Section 1, 5th paragraph:
>>=20
>> it seems like the RADIUS problems that this does not solve are in =
generally solved by RADIUS/TLS. If so, it would probably be worth a =
mention.
>=20
>  OK.
>=20
>> -- section 2.1, 4th paragraph from end:=20
>>=20
>> Seems like there are other changes as well. For example, you don't =
include "Use DTLS" as one of the changes in RADIUS/DTLS from RADIUS/USP.
>=20
>  OK.
>=20
>> -- 2.2 and children:
>>=20
>> In my strictly personal opinion, the approach of patching 6614 =
transfers a lot of effort from the author to the reader. A reader will =
basically need to keep both docs open side by side to understand this.  =
I understand the desire to avoid duplicating normative text, but I think =
that the balance here has swung too far away from readability.  (OTOH, =
see my related comment under "minor issues).
>=20
>  I think re-doing the document is a non-starter at this point.
>=20
>  Having done this myself, the bulk of the implementation work in doing
> DTLS is the UDP layer.  Most everything else can be re-used directly
> from RADIUS/TLS.
>=20

[...]

>> -- 5.1.1, 2nd paragraph:
>>=20
>> What is an "entry" session?
>=20
>  The 4-tuple is logically a table tracking (4-tuple) -> (session =
data).
> Each one is an entry.
>=20
>  I'll try to clarify the text.
>=20

I don't see a change in version 08. In particular, I'm confused by =
"Sessions (both 4-tuple and entry) ..." That sounds like you have two =
kinds of sessions, 4-tuple sessions and entry sessions. I think you mean =
something more like "Both the 4-tuple and the session table entry for a =
session ...." right?

>=20
>> -- 7:
>>=20
>> Only the first paragraph seems to be about implementation experience.
>=20
>  OK.

No change in version 08.
>=20

[...]


From mahoney@nostrum.com  Thu Jan 30 17:46:28 2014
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBAED1A0508 for <gen-art@ietfa.amsl.com>; Thu, 30 Jan 2014 17:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-Q2jKnpYQxk for <gen-art@ietfa.amsl.com>; Thu, 30 Jan 2014 17:46:27 -0800 (PST)
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 7AED71A04F3 for <gen-art@ietf.org>; Thu, 30 Jan 2014 17:46:26 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0V1kHls003514 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 30 Jan 2014 19:46:22 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52EB0069.1060900@nostrum.com>
Date: Thu, 30 Jan 2014 19:46:17 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2014-02-06 Telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 01:46:29 -0000

Hi all,

The following reviewers have assignments:

Reviewer            LC end       Draft
------------------------------------------------------------------------------------
Brian Carpenter     2013-12-23   draft-ietf-soc-overload-control-14**

Christer Holmberg   2014-01-22   draft-ietf-ancp-mc-extensions-14

Dan Romascanu       2013-09-30   draft-ietf-p2psip-rpr-11*
Dan Romascanu       2013-12-11   draft-ietf-stox-core-09*
Dan Romascanu       2013-11-27   draft-ietf-clue-telepresence-requirements-07*

Elwyn Davies        2013-09-24   draft-ietf-insipid-session-id-reqts-09*

Francis Dupont      2013-12-09   draft-ietf-rtgwg-cl-requirement-15*
Francis Dupont      2013-09-30   draft-ietf-p2psip-drr-11*

Joel Halpern        2013-11-27   draft-ietf-xrblock-rtcp-xr-qoe-13*
Joel Halpern        2013-12-11   draft-ietf-stox-presence-07*

Martin Thomson      2014-02-04   draft-ietf-alto-protocol-25**

Robert Sparks       2014-01-31   draft-crocker-id-adoption-05**

Scott Brim          2013-12-31   draft-farrell-perpass-attack-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 christer.holmberg@ericsson.com  Fri Jan 31 03:23:39 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB9481A058A for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 03:23:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yRZoxZNCZ8hd for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 03:23:38 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 06E981A057D for <gen-art@ietf.org>; Fri, 31 Jan 2014 03:23:37 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-68-52eb87b5a407
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 34.02.04249.5B78BE25; Fri, 31 Jan 2014 12:23:33 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.02.0387.000; Fri, 31 Jan 2014 12:23:32 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-ancp-mc-extensions-14
Thread-Index: Ac8edaJ6CL5OCVGHScOmGFBRqJbbkg==
Date: Fri, 31 Jan 2014 11:23:32 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D151146@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.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrELMWRmVeSWpSXmKPExsUyM+Jvje7W9tdBBvMfG1ocavrEbHH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugStj4/c17AWPWSv2PMloYJzE0sXIySEhYCIx 5/8VRghbTOLCvfVsILaQwBFGiU0TKroYuYDsxYwSk+5+B0pwcLAJWEh0/9MGqRER0JSYu+It E4jNLJAtMf35JmYQW1jAWmLH/0lMEDUOEo87+xkhbD2JB2cPgdksAqoSHSs/sILYvAK+Eot3 LAezGYFu+H5qDdRMcYlbT+YzQdwmILFkz3lmCFtU4uXjf6wg50gIKEos75eDKNeRWLD7ExuE rS2xbOFrZojxghInZz5hmcAoMgvJ1FlIWmYhaZmFpGUBI8sqRo7i1OKk3HQjg02MwHA/uOW3 xQ7Gy39tDjFKc7AoifN+fOscJCSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoHxuJ7DzCvTOQvP PFOM+6nY9Hsn66G4P56ZUq7Lwzhe80dsz9i3z1FWzWGPg4MwC1vFT9l8xzWbt7ALz5Fcabw5 2K77I6/K47s8/8Unny459uB+54rj8ndWHpp5SPHuzHOnN37ZMo9xg9yPjOgVQn+sLV4c3pzz S377iyXrlm3dulLgkoXs7VlvY5VYijMSDbWYi4oTAWWJej9FAgAA
Cc: "draft-ietf-ancp-mc-extensions.all@tools.ietf.org" <draft-ietf-ancp-mc-extensions.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-ancp-mc-extensions-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 11:23:39 -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-ancp-mc-extensions-14.txt
Reviewer:                        Christer Holmberg
Review Date:                   31 January 2014
IETF LC End Date:            22 January 2014
IESG Telechat date:         6 February 2014=20

Summary:		I have no issues with the document. It is well written, and is re=
ady for publication.
=20
Major issues: -

Minor issues: -

Nits/editorial comments: -

Regards,

Christer

From varun@comnet.tkk.fi  Fri Jan 31 06:25:52 2014
Return-Path: <varun@comnet.tkk.fi>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B161A0276 for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 06:25:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SLFJovtegwKO for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 06:25:49 -0800 (PST)
Received: from smtp-out-02.aalto.fi (smtp-out-02.aalto.fi [130.233.228.121]) by ietfa.amsl.com (Postfix) with ESMTP id 000C51A0064 for <gen-art@ietf.org>; Fri, 31 Jan 2014 06:25:48 -0800 (PST)
Received: from smtp-out-02.aalto.fi (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id CE37C2710D7_2EBB267B; Fri, 31 Jan 2014 14:25:43 +0000 (GMT)
Received: from smtp.netlab.hut.fi (luuri.netlab.hut.fi [130.233.154.177]) by smtp-out-02.aalto.fi (Sophos Email Appliance) with ESMTP id 234C2271087_2EBB267F; Fri, 31 Jan 2014 14:25:43 +0000 (GMT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.netlab.hut.fi (Postfix) with ESMTP id 14F721E157; Fri, 31 Jan 2014 16:25:43 +0200 (EET)
X-Virus-Scanned: by amavisd-new at luuri.netlab.hut.fi
Received: from smtp.netlab.hut.fi ([127.0.0.1]) by localhost (luuri.netlab.hut.fi [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 0Er9qEom5YJy; Fri, 31 Jan 2014 16:25:37 +0200 (EET)
Received: from [10.100.37.223] (wireless-86-50-146-146.open.aalto.fi [86.50.146.146]) by smtp.netlab.hut.fi (Postfix) with ESMTPSA id BD1271E01D; Fri, 31 Jan 2014 16:25:37 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Varun Singh <varun@comnet.tkk.fi>
In-Reply-To: <52E2B7BC.5070506@bell-labs.com>
Date: Fri, 31 Jan 2014 16:25:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C6A9E5B-753F-4080-AEB5-21C2927EC689@comnet.tkk.fi>
References: <52E28081.4000102@bell-labs.com> <8C0868AA-166D-4C0E-B176-C0A88EAE97E5@comnet.tkk.fi> <52E2B7BC.5070506@bell-labs.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1827)
Cc: "xrblock-chairs@tools.ietf.org" <xrblock-chairs@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 14:25:52 -0000

Hi Vijay,

Apologies for the tardiness, comments inline.

On 24 Jan 2014, at 20:58, Vijay K. Gurbani <vkg@bell-labs.com> wrote:

> On 01/24/2014 10:44 AM, Varun Singh wrote:
>>> Nits: - S6, "In some situations, returning very detailed error
>>> information (e.g., over-range measurement or measurement
>>> unavailable) using this report block can provide an attacker with
>>> insight into the security processing." I am not sure what you mean
>>> by "security processing" here --- maybe you meant the byte discard
>>> block leaks privacy of the user?
>>>=20
>> It is not necessarily privacy of the user, but a situation when the
>> receiver reports a packet as discarded and If the packet was
>> carefully crafted by an attacker,  they infer something about the
>> security processing of the endpoint.
>=20
> Varun: It was not immediately clear to me that your threat model when
> you discuss this included the attacker mounting an active attack, but
> regardless, the larger question of what you mean by "security
> processing" remains --- who is doing the "processing" and how is the
> "security" impacted?
>=20
> If an attacker crafts a packet and sends it to the victim, who =
discards
> it, then the attacker gets a XR Bytes Discarded report block, and at
> best the attacker knows that the packet was discarded due to either
> early arrival or late arrival (the 'E' bit).  What is the "security
> processing" insight that we are worried about here?
>=20

In this particular case, we are worried about a side channel attack.=20
The attacker sends a late arriving packet (timestamp in the past)
to the receiver and if the receiver sends a discard report with the=20
same number of bytes as the payload of the injected packet, the
attacker may infer that no security processing was performed.=20
If it observes no discard report, it may infer that security procedures=20=

were performed on the packet.

> Furthermore, if the attacker is capable of mounting an attack such =
that
> it can inject arbitrary packets to the victim, then the attacker is
> either in a session with the victim (a session the victim can stop
> at any time), or the attacker has usurped the channel between the
> victim and the original participant that the victim was conversing
> with.  In both cases, I suspect that the damage done is more than the
> attacker just getting back discard report blocks.
>=20

Agree, this kind of attack can be mounted by any endpoint passively =
monitoring the session
along the path and since RTP is sent over UDP, the attacker can mount =
the above attack.=20

>> AFAIR the wording of the paragraph is adapted from other drafts
>> discussing discarded packets (RFC7097 and RFC7002) and with input
>> from sec-dir. That being said, if the wording can be made more clear,
>> I'm happy to incorporate the proposal.
>=20
> I would have had the same questions of rfc7097 or rfc7002 if I had =
been
> chosen to Gen-ART review them :-)
>=20
> I think you need to motivate your threat model in S6 to determine the
> mitigation strategies where SRTP/SAVPF will help.  You can discuss =
this

I think one of the reasons not to explicitly write about the threat =
model is because
there are several reason to use and not use SRTP/AVPF. they are covered =
in
ietf-avt-srtp-not-mandatory, and implementors should read that document
to make up their mind.

I hope the chairs can clarify on how to proceed.=20

> with your chair or your friendly sec-dir personnel and if they
> indicate that no threat model is needed, then please go ahead with the
> draft.  Gen-ART reviews are advisory in nature anyway.  However, since
> I was confused on reading the section and remain so after our brief
> email exchange, I think some text added on the motivation may be =
helpful
> to future readers (and implementers) of the extension.
>=20

Thank you again for the feedback.

Cheers,
Varun.

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


From vkg@bell-labs.com  Fri Jan 31 06:44:28 2014
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 213161A02D4 for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 06:44:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6pkEiM-Gv_Zz for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 06:44:26 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 1ABFE1A02C8 for <gen-art@ietf.org>; Fri, 31 Jan 2014 06:44:26 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id s0VEiId6015755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 31 Jan 2014 08:44:19 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s0VEiIeu025669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 31 Jan 2014 08:44:18 -0600
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 s0VEiGgP027463; Fri, 31 Jan 2014 08:44:16 -0600 (CST)
Message-ID: <52EBB6F8.8090503@bell-labs.com>
Date: Fri, 31 Jan 2014 08:45:12 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Varun Singh <varun@comnet.tkk.fi>
References: <52E28081.4000102@bell-labs.com> <8C0868AA-166D-4C0E-B176-C0A88EAE97E5@comnet.tkk.fi> <52E2B7BC.5070506@bell-labs.com> <0C6A9E5B-753F-4080-AEB5-21C2927EC689@comnet.tkk.fi>
In-Reply-To: <0C6A9E5B-753F-4080-AEB5-21C2927EC689@comnet.tkk.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: "xrblock-chairs@tools.ietf.org" <xrblock-chairs@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 14:44:28 -0000

On 01/31/2014 08:25 AM, Varun Singh wrote:
> Hi Vijay,
>
> Apologies for the tardiness, comments inline.

Varun: No worries.  More inline.

> In this particular case, we are worried about a side channel attack.
> The attacker sends a late arriving packet (timestamp in the past) to
> the receiver and if the receiver sends a discard report with the same
> number of bytes as the payload of the injected packet, the attacker
> may infer that no security processing was performed. If it observes
> no discard report, it may infer that security procedures were
> performed on the packet.

Ah, so you can trivially solve this problem by describing the attack in
the draft, much as you do above.

> I think one of the reasons not to explicitly write about the threat
> model is because there are several reason to use and not use
> SRTP/AVPF. they are covered in ietf-avt-srtp-not-mandatory, and
> implementors should read that document to make up their mind.

My reading of draft-ietf-avt-srtp-not-mandatory is that it does not
absolve RTP extension authors from talking about security, rather it
exhorts them to talk about the specific security problems exhibited
by their proposed extension and furthermore, elaborate how to address
such concerns.

> I hope the chairs can clarify on how to proceed.

Cheers,

- 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 mahoney@nostrum.com  Fri Jan 31 08:34:57 2014
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 567E31A0589 for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 08:34:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AgaS4S914pLw for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 08:34:55 -0800 (PST)
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 C52691A0576 for <gen-art@ietf.org>; Fri, 31 Jan 2014 08:34:55 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0VGYpVC046150 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Fri, 31 Jan 2014 10:34:51 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52EBD0AB.7050302@nostrum.com>
Date: Fri, 31 Jan 2014 10:34:51 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: gen-art@ietf.org
References: <52EB0069.1060900@nostrum.com>
In-Reply-To: <52EB0069.1060900@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Subject: Re: [Gen-art] Assignments for the 2014-02-06 Telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 16:34:57 -0000

And some late additions:

Joel Halpern   draft-ietf-tls-applayerprotoneg-04*

Scott Brim     draft-ietf-avtcore-clksrc-09**

Jean


On 1/30/14 7:46 PM, A. Jean Mahoney wrote:
> Hi all,
>
> The following reviewers have assignments:
>
> Reviewer            LC end       Draft
> ------------------------------------------------------------------------------------ 
>
> Brian Carpenter     2013-12-23 draft-ietf-soc-overload-control-14**
>
> Christer Holmberg   2014-01-22   draft-ietf-ancp-mc-extensions-14
>
> Dan Romascanu       2013-09-30   draft-ietf-p2psip-rpr-11*
> Dan Romascanu       2013-12-11   draft-ietf-stox-core-09*
> Dan Romascanu       2013-11-27 
> draft-ietf-clue-telepresence-requirements-07*
>
> Elwyn Davies        2013-09-24 draft-ietf-insipid-session-id-reqts-09*
>
> Francis Dupont      2013-12-09 draft-ietf-rtgwg-cl-requirement-15*
> Francis Dupont      2013-09-30   draft-ietf-p2psip-drr-11*
>
> Joel Halpern        2013-11-27 draft-ietf-xrblock-rtcp-xr-qoe-13*
> Joel Halpern        2013-12-11   draft-ietf-stox-presence-07*
>
> Martin Thomson      2014-02-04   draft-ietf-alto-protocol-25**
>
> Robert Sparks       2014-01-31   draft-crocker-id-adoption-05**
>
> Scott Brim          2013-12-31   draft-farrell-perpass-attack-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:
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From mahoney@nostrum.com  Fri Jan 31 08:38:11 2014
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70CF51A0442 for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 08:38:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0XYqZTWUKElq for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 08:38:10 -0800 (PST)
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 391EC1A0367 for <gen-art@ietf.org>; Fri, 31 Jan 2014 08:38:10 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0VGc6jc046335 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Fri, 31 Jan 2014 10:38:06 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52EBD16D.706@nostrum.com>
Date: Fri, 31 Jan 2014 10:38:05 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-01-31
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 16:38:11 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Brian Carpenter   2014-02-07   draft-ietf-manet-nhdp-olsrv2-tlv-extension-01

Christer Holmberg 2014-02-07   draft-ietf-roll-trickle-mcast-06 *

Dan Romascanu     2014-02-11   draft-ietf-pwe3-iccp-13

Francis Dupont    2014-02-12   draft-ietf-l3vpn-mldp-vrf-in-band-signaling-03

Joel Halpern      2014-02-12   draft-ietf-mpls-forwarding-06

Meral Shirazipour 2014-02-14   draft-ietf-l2vpn-vpls-mib-14

* Second LC

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

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:



From scott.brim@gmail.com  Fri Jan 31 08:56:24 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 018E01A1F48; Fri, 31 Jan 2014 08:56:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SavwqCutpbsG; Fri, 31 Jan 2014 08:56:22 -0800 (PST)
Received: from mail-oa0-x22e.google.com (mail-oa0-x22e.google.com [IPv6:2607:f8b0:4003:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E973C1A0522; Fri, 31 Jan 2014 08:56:21 -0800 (PST)
Received: by mail-oa0-f46.google.com with SMTP id n16so5414742oag.5 for <multiple recipients>; Fri, 31 Jan 2014 08:56:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=uZcH2uyBv5uVi0PGuq3jz/NpzpjG7R4y7boTuRbudNE=; b=ALGuhcIAojg3hQv4mBS+Q8W2OfvVe5pG+aiaZbKCJrEQb/x2W+2nc4C7lOi/4xrWX9 ftI9LC86G3raG7Z0Uq7SgBiLwrUl//YUYboV9yPTqS1nx4H8//L3zLpDNezFh893PT+y CSj26v3bai897OiWewJKj03Q10jsH57iRyuVIbKyI0hQAppks/cO4CElMdLrRfjy4Q1D T0394wK0jBFb0rdu28n4QMVI/G4YGg6CL5vOvwjUvwswpBZ+xdosF6Up0FCehfonwAdj bo4LXKrc1LpRB4hIdIAcXzIGCIJRynTi3ZhrkKoz8J6tkNBcUEI0rbb3ebTdrhGZpTug u3PA==
X-Received: by 10.182.142.229 with SMTP id rz5mr17533036obb.12.1391187378207;  Fri, 31 Jan 2014 08:56:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 31 Jan 2014 08:55:58 -0800 (PST)
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 31 Jan 2014 11:55:58 -0500
Message-ID: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@mail.gmail.com>
To: gen-art <gen-art@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org, IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] GEN-ART telechat review of draft-farrell-perpass-attack-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 16:56: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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-farrell-perpass-attack-05
Reviewer: Scott Brim
Review Date: 2014-02-01
IETF LC End Date: 2013-12-31
IESG Telechat date: 2014-02-06

Summary: This draft is ready for publication as a BCP.

Major issues:

Minor issues:

Nits/editorial comments:

Two comments:

First, there are good arguments for publication as Informational , but
since it incrementally adds to BCP 72, it should be incorporated
there, so BCP is slightly better.

Second, the only significant difference from -04 was the removal of
"and be prepared to justify their decisions". There was a lot of
discussion that led to this, and some concern that the statement on
architectural considerations is not strongly enough worded without it.
However, see the previous paragraph (both paragraphs are below).  I
believe that these two paragraphs, taken together, do what is desired.

   Those developing IETF specifications need to be able to describe how
   they have considered PM, and, if the attack is relevant to the work
   to be published, be able to justify related design decisions.  This
   does not mean a new "pervasive monitoring considerations" section is
   needed in IETF documentation.  It means that, if asked, there needs
   to be a good answer to the question "is pervasive monitoring relevant
   to this work and if so how has it been considered?"

   In particular, architectural decisions, including which existing
   technology is re-used, may significantly impact the vulnerability of
   a protocol to PM.  Those developing IETF specifications therefore
   need to consider mitigating PM when making these architectural
   decisions.  Getting adequate, early review of architectural decisions
   including whether appropriate mitigation of PM can be made is
   important.  Revisiting these architectural decisions late in the
   process is very costly.

Scott

From dhc@dcrocker.net  Fri Jan 31 09:22:50 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EADE61A1F62; Fri, 31 Jan 2014 09:22:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XUb-uyZnMHSW; Fri, 31 Jan 2014 09:22:45 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 62E5F1A0448; Fri, 31 Jan 2014 09:22:45 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s0VHMaT9006590 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 31 Jan 2014 09:22:40 -0800
Message-ID: <52EBDBC0.5000304@dcrocker.net>
Date: Fri, 31 Jan 2014 09:22:08 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>, gen-art <gen-art@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org, IETF discussion list <ietf@ietf.org>
References: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@mail.gmail.com>
In-Reply-To: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 31 Jan 2014 09:22:40 -0800 (PST)
Subject: Re: [Gen-art] GEN-ART telechat review of draft-farrell-perpass-attack-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 17:22:50 -0000

On 1/31/2014 8:55 AM, Scott Brim wrote:
> First, there are good arguments for publication as Informational , but
> since it incrementally adds to BCP 72, it should be incorporated
> there, so BCP is slightly better.


It does?

It does not say it does.

So that linkage is something the reviewer is creating.

At the least, a claim that it does "add to" BCP 72 invites further 
debate about the nature and implications of the update.

Again, making this a BCP confuses the nature of the document with those 
that give substantive operational guidance.

This document does exactly what it should:  It defines the topic and it 
says the IETF considers the topic important.  It calls for practices, 
but doesn't -- and shouldn't -- define them.

The job of providing substantive details about IETF practices associated 
with the topic will come later.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From hartmans@mit.edu  Fri Jan 31 09:39:05 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0B1B1A0431; Fri, 31 Jan 2014 09:39:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ws8XLzI7WUw4; Fri, 31 Jan 2014 09:39:05 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 013971A043A; Fri, 31 Jan 2014 09:39:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id A7D8520655; Fri, 31 Jan 2014 12:35:50 -0500 (EST)
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 38UyD3o8NwUb; Fri, 31 Jan 2014 12:35:50 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.106]) (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, 31 Jan 2014 12:35:50 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id BFB9680BEB; Fri, 31 Jan 2014 12:38:59 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Scott Brim <scott.brim@gmail.com>
References: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@mail.gmail.com>
Date: Fri, 31 Jan 2014 12:38:59 -0500
In-Reply-To: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@mail.gmail.com> (Scott Brim's message of "Fri, 31 Jan 2014 11:55:58 -0500")
Message-ID: <tslmwic59vw.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: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
Subject: Re: [Gen-art] GEN-ART telechat review of draft-farrell-perpass-attack-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 17:39:06 -0000

Thanks Scott.
In the interest of being clear about my position, I support publication
of 04 but do not support publication of 05.

I think all the discussion that is useful has happened and all that
remains is the consensus call from the sponsoring AD.

From elwynd@dial.pipex.com  Fri Jan 31 10:13:50 2014
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C9F51A03C3 for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 10:13:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wKNwVEGpSk5X for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 10:13:48 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 11FE31A042F for <gen-art@ietf.org>; Fri, 31 Jan 2014 10:13:48 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1W9Iat-0001QK-Tq; Fri, 31 Jan 2014 18:13:42 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Fri, 31 Jan 2014 18:13:33 +0000
Message-Id: <1391192013.24761.1839.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-insipid-session-id-reqts.all@tools.ietf.org
Subject: [Gen-art] Gen-art telechat review of draft-ietf-insipid-session-id-reqts-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 18:13:50 -0000

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

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

Document: draft-ietf-insipid-session-id-reqts-09
Reviewer: Elwyn Davies
Review Date: 31 January 2014
IETF LC End Date:
IESG Telechat date: 06 February 2014

Summary: Ready.  Thanks to the authors for addressing LC comments.

Major issues:
None

Minor issues:
None

Nits/editorial comments:
One nit escaped:
s3.1, para below Fig 1: s/and are by not exhaustive:/and are not
exhaustive:/


From jmh@joelhalpern.com  Fri Jan 31 10:30:02 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BC851A0522 for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 10:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZU9WCi-nwJ4Z for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 10:30:00 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 9A9661A046F for <gen-art@ietf.org>; Fri, 31 Jan 2014 10:30:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 431005C0490; Fri, 31 Jan 2014 10:29:57 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 9867C5C048F; Fri, 31 Jan 2014 10:29:56 -0800 (PST)
Message-ID: <52EBEBA5.9090402@joelhalpern.com>
Date: Fri, 31 Jan 2014 13:29:57 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org
References: <52EB0069.1060900@nostrum.com>
In-Reply-To: <52EB0069.1060900@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art]  Review: draft-ietf-xrblock-rtcp-xr-qoe-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 18:30:02 -0000

This revision address all of my comments and is ready for publication as 
a Proposed Standard.

Yours,
Joel

On 1/30/14, 8:46 PM, A. Jean Mahoney wrote:
> Joel Halpern        2013-11-27   draft-ietf-xrblock-rtcp-xr-qoe-13*

From jmh@joelhalpern.com  Fri Jan 31 10:34:17 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAE991A1F64 for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 10:34:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8mgUJZIGB549 for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 10:34:16 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id C6F0B1A1F71 for <gen-art@ietf.org>; Fri, 31 Jan 2014 10:34:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 6F3235C0533; Fri, 31 Jan 2014 10:34:13 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id B680B5C052E; Fri, 31 Jan 2014 10:34:10 -0800 (PST)
Message-ID: <52EBEC9D.7020902@joelhalpern.com>
Date: Fri, 31 Jan 2014 13:34:05 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org
References: <52EB0069.1060900@nostrum.com>
In-Reply-To: <52EB0069.1060900@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art]  Review: draft-ietf-stox-presence-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 18:34:18 -0000

This document is still ready for publication as a Proposed Standard.
Yours,
Joel

On 1/30/14, 8:46 PM, A. Jean Mahoney wrote:
> Joel Halpern        2013-12-11   draft-ietf-stox-presence-07*

From jmh@joelhalpern.com  Fri Jan 31 10:36:32 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 754831A1F64 for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 10:36:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fat1j9E_xxHs for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 10:36:31 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 54F841A1F5F for <gen-art@ietf.org>; Fri, 31 Jan 2014 10:36:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 005FB5C0578; Fri, 31 Jan 2014 10:36:28 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 7F2935C057A; Fri, 31 Jan 2014 10:36:24 -0800 (PST)
Message-ID: <52EBED27.8050307@joelhalpern.com>
Date: Fri, 31 Jan 2014 13:36:23 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org
References: <52EB0069.1060900@nostrum.com> <52EBD0AB.7050302@nostrum.com>
In-Reply-To: <52EBD0AB.7050302@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art]  Review: draft-ietf-tls-applayerprotoneg-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 18:36:32 -0000

This document is still ready for publication as a Proposed Standard.
Yours,
Joel

On 1/31/14, 11:34 AM, A. Jean Mahoney wrote:
> Joel Halpern   draft-ietf-tls-applayerprotoneg-04*

From paulej@packetizer.com  Fri Jan 31 11:22:09 2014
Return-Path: <paulej@packetizer.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A4541A03F5 for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 11:22:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.527
X-Spam-Level: 
X-Spam-Status: No, score=-1.527 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I98icQa0TIqz for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 11:22:07 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id BC2241A0286 for <gen-art@ietf.org>; Fri, 31 Jan 2014 11:22:07 -0800 (PST)
Received: from [192.168.1.20] (cpe-024-211-197-136.nc.res.rr.com [24.211.197.136]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id s0VJLjjV012259 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 31 Jan 2014 14:21:46 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1391196106; bh=slcyQqPbzHDdL08odukddEe7ugOsbrmVx72kPcaODj8=; h=From:To:Subject:Cc:Date:Content-Transfer-Encoding:Content-Type: In-Reply-To:Message-Id:Mime-Version:Reply-To; b=CqG+GQTmHr/FTxIWtgoe9BBAEfSBPJbvEtxVBYsyZtIP9TaVZQU2NlDsgDku7GNBE HqJv4PasYVsGNKVIpD2voj0U2t58Io9g0X+Ywt/XVXG+BL5DSHUDNqu7CVN0G7+Uc5 8/mFadqMftYwPVitsaqCvZ3gx+9Fk8j7ie4vhtlM=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Elwyn Davies" <elwynd@dial.pipex.com>, "General Area Review Team" <gen-art@ietf.org>
Date: Fri, 31 Jan 2014 19:22:14 +0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; format=flowed; charset=utf-8
In-Reply-To: <1391192013.24761.1839.camel@mightyatom>
Message-Id: <em7dcf52ea-af78-4af6-a3e1-14f70aafef9f@sydney>
Mime-Version: 1.0
User-Agent: eM_Client/6.0.19861.0
Cc: draft-ietf-insipid-session-id-reqts.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art telechat review of draft-ietf-insipid-session-id-reqts-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 19:22:09 -0000

Thanks.  I made the correction in my local copy.

------ Original Message ------
From: "Elwyn Davies" <elwynd@dial.pipex.com>
To: "General Area Review Team" <gen-art@ietf.org>
Cc: draft-ietf-insipid-session-id-reqts.all@tools.ietf.org
Sent: 1/31/2014 1:13:33 PM
Subject: Gen-art telechat review of=20
draft-ietf-insipid-session-id-reqts-09

>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-insipid-session-id-reqts-09
>Reviewer: Elwyn Davies
>Review Date: 31 January 2014
>IETF LC End Date:
>IESG Telechat date: 06 February 2014
>
>Summary: Ready. Thanks to the authors for addressing LC comments.
>
>Major issues:
>None
>
>Minor issues:
>None
>
>Nits/editorial comments:
>One nit escaped:
>s3.1, para below Fig 1: s/and are by not exhaustive:/and are not
>exhaustive:/
>


From jmh@joelhalpern.com  Fri Jan 31 11:47:17 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 730E71A0478 for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 11:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZnuUMoP_c3La for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 11:47:15 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id E3C551A0464 for <gen-art@ietf.org>; Fri, 31 Jan 2014 11:47:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 8AACD5C0DA2; Fri, 31 Jan 2014 11:47:12 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id A9F5A5C0D94; Fri, 31 Jan 2014 11:47:11 -0800 (PST)
Message-ID: <52EBFDBF.70505@joelhalpern.com>
Date: Fri, 31 Jan 2014 14:47:11 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org
References: <52EBD16D.706@nostrum.com>
In-Reply-To: <52EBD16D.706@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gen-art]  Review: draft-ietf-mpls-forwarding-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 19:47:17 -0000

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

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

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

Document: draft-ietf-mpls-forwarding-06
Reviewer: Joel M. Halpern
Review Date: 31-January-2014
IETF LC End Date: 12-Feb-2014
IESG Telechat date: N/A

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

Major issues: N/A

Minor issues: N/A

Nits/editorial comments: N/A

From kathleen.moriarty@emc.com  Fri Jan 31 12:43:24 2014
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C29941A0292; Fri, 31 Jan 2014 12:43:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vvkwKJoyxa_b; Fri, 31 Jan 2014 12:43:22 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id B47181A0448; Fri, 31 Jan 2014 12:43:22 -0800 (PST)
Received: from maildlpprd01.lss.emc.com (maildlpprd01.lss.emc.com [10.253.24.33]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0VKhGRU005554 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Jan 2014 15:43:17 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com s0VKhGRU005554
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1391200997; bh=UN/X7yK+b7Y2+3nGGEZNZQgmV/s=; h=From:To:CC:Date:Subject:Message-ID:Content-Type:MIME-Version; b=AQ8PdV9tc/GpU5bhhXN+svemxuQmmndELTfAd0zPbaIuSsxXa+52XVidon55XkJJO vk1NBQtXHPPnTC6/FMW8cxwh5gC/ms6FblcXI2lHjqDXzQX9uxnqY5vkW7rSnJ6Ce5 rV12fh8cKitcRyEoQJpS+V6pjfpcTpEIIGIY/Q7M=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com s0VKhGRU005554
Received: from mailusrhubprd03.lss.emc.com (mailusrhubprd03.lss.emc.com [10.253.24.21]) by maildlpprd01.lss.emc.com (RSA Interceptor); Fri, 31 Jan 2014 15:43:02 -0500
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailusrhubprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0VKh27H001179 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 Jan 2014 15:43:02 -0500
Received: from mx15a.corp.emc.com ([169.254.1.167]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Fri, 31 Jan 2014 15:43:01 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-yourtchenko-cisco-ies.all@tools.ietf.org" <draft-yourtchenko-cisco-ies.all@tools.ietf.org>
Date: Fri, 31 Jan 2014 15:43:00 -0500
Thread-Topic: Gen-art review of draft-yourtchenko-cisco-ies-09
Thread-Index: Ac8eqUecycNQQKRpT6GhZsmkpbn7UQ==
Message-ID: <F5063677821E3B4F81ACFB7905573F24065A5E90F1@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: multipart/alternative; boundary="_000_F5063677821E3B4F81ACFB7905573F24065A5E90F1MX15Acorpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd03.lss.emc.com
X-RSA-Classifications: public
Cc: "bclaise@cisco.com" <bclaise@cisco.com>, "ayourtch@cisco.com" <ayourtch@cisco.com>, "paitken@cisco.com" <paitken@cisco.com>, "draft-yourtchenko-cisco-ies@tools.ietf.org" <draft-yourtchenko-cisco-ies@tools.ietf.org>
Subject: [Gen-art] Gen-art review of draft-yourtchenko-cisco-ies-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 20:43:25 -0000

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

Document: draft-yourtchenko-cisco-ies-09

Reviewer: Kathleen Moriarty

Review Date: 1/31/14

IETF LC End Date:

IESG Telechat date: (if known) 2/18/14



Summary:  This draft extends RFC3954, but is specific to Cisco.  There has =
already been discussion about this being a Cisco specific draft and involve=
d consultation with the WG chair.



For Gen-art, the document has a few editorial nits that should be resolved =
and other reviewers points on the Cisco specific document should be conside=
red.  Otherwise, the document is ready for publication.



Major issues:



Minor issues:



Nits/editorial comments:

Introduction:  The third sentence is terminated with a question mark and it=
 should be a period as it is not a question in itself.  The last sentence i=
n this paragraph correctly terminates with a question mark, but the space b=
efore it should be deleted.






--_000_F5063677821E3B4F81ACFB7905573F24065A5E90F1MX15Acorpemcc_
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)"><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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	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: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=3DMsoPlainText>Document: dra=
ft-yourtchenko-cisco-ies-09<o:p></o:p></p><p class=3DMsoPlainText>Reviewer:=
 Kathleen Moriarty<o:p></o:p></p><p class=3DMsoPlainText>Review Date: 1/31/=
14<o:p></o:p></p><p class=3DMsoPlainText>IETF LC End Date:<o:p></o:p></p><p=
 class=3DMsoPlainText>IESG Telechat date: (if known) 2/18/14<o:p></o:p></p>=
<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Summar=
y:&nbsp; This draft extends <span style=3D'font-size:10.0pt;font-family:"Co=
urier New"'>RFC3954, but is specific to Cisco.&nbsp; There has already been=
 discussion about this being a Cisco specific draft and involved consultati=
on with the WG chair.<o:p></o:p></span></p><p class=3DMsoPlainText><span st=
yle=3D'font-size:10.0pt;font-family:"Courier New"'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoPlainText><span style=3D'font-size:10.0pt;font-family:"Co=
urier New"'>For Gen-art, the document has a few editorial nits that should =
be resolved and other reviewers points on the Cisco specific document shoul=
d be considered.&nbsp; Otherwise, the document is ready for publication.</s=
pan><o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3D=
MsoPlainText>Major issues:<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp=
;</o:p></p><p class=3DMsoPlainText>Minor issues:<o:p></o:p></p><p class=3DM=
soPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Nits/editorial com=
ments:<o:p></o:p></p><p class=3DMsoPlainText>Introduction:&nbsp; The third =
sentence is terminated with a question mark and it should be a period as it=
 is not a question in itself.&nbsp; The last sentence in this paragraph cor=
rectly terminates with a question mark, but the space before it should be d=
eleted.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=
=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p>=
</p></div></body></html>=

--_000_F5063677821E3B4F81ACFB7905573F24065A5E90F1MX15Acorpemcc_--

From paitken@cisco.com  Fri Jan 31 13:17:07 2014
Return-Path: <paitken@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 146FF1A0423; Fri, 31 Jan 2014 13:17:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.035
X-Spam-Level: 
X-Spam-Status: No, score=-10.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tx76ogUEsW9W; Fri, 31 Jan 2014 13:17:05 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 6BA6B1A03FE; Fri, 31 Jan 2014 13:17:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4407; q=dns/txt; s=iport; t=1391203021; x=1392412621; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=xbWoyO7zzEaQJTRt65UFPhD6YhCIKtPzHy/Qb8hno4I=; b=jgq+F+xn1XY63nSLyl1dVJ7wSj3E4fRsSxrBAiwfI/f2DWf6mPgAnGor fVY5wkPjve4Jme4XMV/RZXfHywPZUPy5yFxvXSiB1AEs0udR6nBtSz6L/ wsm5LM3RVDPoVJp4BO+O5XNlQcRq26JZQ2xSz+pgtLE9YQz50NaZJTyBs I=;
X-IronPort-AV: E=Sophos;i="4.95,759,1384300800"; d="scan'208,217";a="3827429"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-2.cisco.com with ESMTP; 31 Jan 2014 21:16:59 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0VLGwGE007667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Jan 2014 21:16:59 GMT
Received: from [10.61.105.109] (dhcp-10-61-105-109.cisco.com [10.61.105.109]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0VLGq3Z010362; Fri, 31 Jan 2014 21:16:53 GMT
Message-ID: <52EC12C4.3010503@cisco.com>
Date: Fri, 31 Jan 2014 21:16:52 +0000
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-yourtchenko-cisco-ies.all@tools.ietf.org" <draft-yourtchenko-cisco-ies.all@tools.ietf.org>
References: <F5063677821E3B4F81ACFB7905573F24065A5E90F1@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24065A5E90F1@MX15A.corp.emc.com>
Content-Type: multipart/alternative; boundary="------------060000030309060703090907"
Cc: "bclaise@cisco.com" <bclaise@cisco.com>, "ayourtch@cisco.com" <ayourtch@cisco.com>, "draft-yourtchenko-cisco-ies@tools.ietf.org" <draft-yourtchenko-cisco-ies@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-yourtchenko-cisco-ies-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 21:17:07 -0000

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

Kathleen, All,

Apologies for jumping in here, but I wasn't privvy to the earlier 
discussion to which you allude.

> Summary:  This draft extends RFC3954, but is specific to Cisco.
>

No, this draft does not extend RFC 3954.

RFC 3954 specifies the NFv9 Protocol and the associated Information 
Model. The model is extensible, and I own the netflow-police hat for 
reviewing, approving, and actioning NFv9 extensions.

The IPFIX Protocol (RFC 7011) has its own Information Model (RFC 7012, 
IANA) which is also extensible upon application to IANA, subject to 
expert review by IE-doctors (RFC 7013).

The yourtchenko-cisco-ies draft extends the IPFIX Information model. Per 
section 6 of the draft, "IANA Considerations":

    This document specifies several new IPFIX Information Elements in the
    IPFIX Information Element registry


The IPFIX Information Model was initially based upon the NFv9 
Information Model. Indeed, the two are generally considered to be 
synonymous.

The extensions which are being added to the IPFIX model seek to retain 
that synonymity by describing NFv9 elements which were not known or 
defined at the time RFC 3954 was written. These can be adopted into the 
IPFIX Information Model to retain compatibility, rather than defining 
equivalent IPFIX elements with different IDs from NFv9 and thus 
complicating life for every netflow collector.

Note that this is not a change to either the NFv9 or IPFIX protocols.


P.


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Kathleen, All,<br>
      <br>
      Apologies for jumping in here, but I wasn't privvy to the earlier
      discussion to which you allude.<o:p></o:p><br>
      <br>
    </div>
    <blockquote
      cite="mid:F5063677821E3B4F81ACFB7905573F24065A5E90F1@MX15A.corp.emc.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText">Summary:&nbsp; This draft extends <span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">RFC3954,
            but is specific to Cisco.</span></p>
      </div>
    </blockquote>
    <br>
    No, this draft does not extend RFC 3954.<br>
    <br>
    RFC 3954 specifies the NFv9 Protocol and the associated Information
    Model. The model is extensible, and I own the netflow-police hat for
    reviewing, approving, and actioning NFv9 extensions.<br>
    <br>
    The IPFIX Protocol (RFC 7011) has its own Information Model (RFC
    7012, IANA) which is also extensible upon application to IANA,
    subject to expert review by IE-doctors (RFC 7013).<br>
    <br>
    The yourtchenko-cisco-ies draft extends the IPFIX Information model.
    Per section <span class="m_h">6 of the draft, "IANA
      Considerations":<br>
    </span>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre>
   This document specifies several new IPFIX Information Elements in the
   IPFIX Information Element registry</pre>
    <br>
    The IPFIX Information Model was initially based upon the NFv9
    Information Model. Indeed, the two are generally considered to be
    synonymous.<br>
    <br>
    The extensions which are being added to the IPFIX model seek to
    retain that synonymity by describing NFv9 elements which were not
    known or defined at the time RFC 3954 was written. These can be
    adopted into the IPFIX Information Model to retain compatibility,
    rather than defining equivalent IPFIX elements with different IDs
    from NFv9 and thus complicating life for every netflow collector.<br>
    <br>
    Note that this is not a change to either the NFv9 or IPFIX
    protocols.<br>
    <br>
    <br>
    P<o:p>. <br>
    </o:p>
    <blockquote
      cite="mid:F5063677821E3B4F81ACFB7905573F24065A5E90F1@MX15A.corp.emc.com"
      type="cite">
    </blockquote>
    <br>
  </body>
</html>

--------------060000030309060703090907--

From kathleen.moriarty@emc.com  Fri Jan 31 13:34:43 2014
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C62611A0443; Fri, 31 Jan 2014 13:34:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e5_nvD-tikxG; Fri, 31 Jan 2014 13:34:41 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 4AC5C1A0426; Fri, 31 Jan 2014 13:34:41 -0800 (PST)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0VLYYfu007422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Jan 2014 16:34:35 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s0VLYYfu007422
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1391204076; bh=d3fUktOEYfPP00kQlO75Jgbno98=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=gO4dZyh+iMD9SXVwbrfvmogsRTe09tWWz6/FBzndnlOXQ+6fs1YnxeXgeh94JuiID /vbfsz01yBupWLTdYMh6MiEyVPMEfuGnq75JdZKJ6mdjIrNT7JJ6Gi/xymCt46FL9d GpUM1qTdvuQoa1RRSZZNBRWC6qvI62Kh7L55/qY4=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s0VLYYfu007422
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd04.lss.emc.com (RSA Interceptor); Fri, 31 Jan 2014 13:34:21 -0800
Received: from mxhub37.corp.emc.com (mxhub37.corp.emc.com [128.222.70.104]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0VLYLLW008302 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 Jan 2014 16:34:21 -0500
Received: from mx15a.corp.emc.com ([169.254.1.167]) by mxhub37.corp.emc.com ([128.222.70.104]) with mapi; Fri, 31 Jan 2014 16:34:21 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Paul Aitken <paitken@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-yourtchenko-cisco-ies.all@tools.ietf.org" <draft-yourtchenko-cisco-ies.all@tools.ietf.org>
Date: Fri, 31 Jan 2014 16:34:19 -0500
Thread-Topic: Gen-art review of draft-yourtchenko-cisco-ies-09
Thread-Index: Ac8eycpMD4WacNhaQf6gF4enh/p8iAAALr1A
Message-ID: <F5063677821E3B4F81ACFB7905573F24065A5E9111@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24065A5E90F1@MX15A.corp.emc.com> <52EC12C4.3010503@cisco.com>
In-Reply-To: <52EC12C4.3010503@cisco.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_F5063677821E3B4F81ACFB7905573F24065A5E9111MX15Acorpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: public
Cc: "bclaise@cisco.com" <bclaise@cisco.com>, "ayourtch@cisco.com" <ayourtch@cisco.com>, "draft-yourtchenko-cisco-ies@tools.ietf.org" <draft-yourtchenko-cisco-ies@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-yourtchenko-cisco-ies-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 21:34:44 -0000

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

Hi Paul,

In that case, please update the abstract and introduction to make the inten=
t of the document clear.  It would be helpful for the reader to understand =
the intent as they start reading the document.

The discussion referenced was posted to ietf@ietf.org<mailto:ietf@ietf.org>=
.  I think folks are addressing that discussion, so there is no need for me=
 to jump into it.  Here is a link that should pull up all the messages on t=
his draft in the last month across all mailing lists:
https://mailarchive.ietf.org/arch/search/?q=3Dyourtchenko&qdr=3Dm

Best regards,
Kathleen

From: Paul Aitken [mailto:paitken@cisco.com]
Sent: Friday, January 31, 2014 4:17 PM
To: Moriarty, Kathleen; gen-art@ietf.org; iesg@ietf.org; draft-yourtchenko-=
cisco-ies.all@tools.ietf.org
Cc: ayourtch@cisco.com; bclaise@cisco.com; draft-yourtchenko-cisco-ies@tool=
s.ietf.org
Subject: Re: Gen-art review of draft-yourtchenko-cisco-ies-09

Kathleen, All,

Apologies for jumping in here, but I wasn't privvy to the earlier discussio=
n to which you allude.

Summary:  This draft extends RFC3954, but is specific to Cisco.

No, this draft does not extend RFC 3954.

RFC 3954 specifies the NFv9 Protocol and the associated Information Model. =
The model is extensible, and I own the netflow-police hat for reviewing, ap=
proving, and actioning NFv9 extensions.

The IPFIX Protocol (RFC 7011) has its own Information Model (RFC 7012, IANA=
) which is also extensible upon application to IANA, subject to expert revi=
ew by IE-doctors (RFC 7013).

The yourtchenko-cisco-ies draft extends the IPFIX Information model. Per se=
ction 6 of the draft, "IANA Considerations":



   This document specifies several new IPFIX Information Elements in the

   IPFIX Information Element registry

The IPFIX Information Model was initially based upon the NFv9 Information M=
odel. Indeed, the two are generally considered to be synonymous.

The extensions which are being added to the IPFIX model seek to retain that=
 synonymity by describing NFv9 elements which were not known or defined at =
the time RFC 3954 was written. These can be adopted into the IPFIX Informat=
ion Model to retain compatibility, rather than defining equivalent IPFIX el=
ements with different IDs from NFv9 and thus complicating life for every ne=
tflow collector.

Note that this is not a change to either the NFv9 or IPFIX protocols.


P.



--_000_F5063677821E3B4F81ACFB7905573F24065A5E9111MX15Acorpemcc_
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)"><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";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	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";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;
	color:black;}
span.mh
	{mso-style-name:m_h;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle22
	{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 bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>Hi Paul,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fo=
nt-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'>In that case, please update t=
he abstract and introduction to make the intent of the document clear.&nbsp=
; It would be helpful for the reader to understand the intent as they start=
 reading the document.<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=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.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'>The discussion referen=
ced was posted to <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>.&nbsp;=
 I think folks are addressing that discussion, so there is no need for me t=
o jump into it. &nbsp;Here is a link that should pull up all the messages o=
n this draft in the last month across all mailing lists:<o:p></o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif";color:#1F497D'><a href=3D"https://mailarchive.ietf.org/arch=
/search/?q=3Dyourtchenko&amp;qdr=3Dm">https://mailarchive.ietf.org/arch/sea=
rch/?q=3Dyourtchenko&amp;qdr=3Dm</a><o:p></o:p></span></p><p class=3DMsoNor=
mal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";colo=
r:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'=
font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best reg=
ards,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11=
.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Kathleen<o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:=
"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div=
 style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in =
0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"T=
ahoma","sans-serif";color:windowtext'>From:</span></b><span style=3D'font-s=
ize:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Paul Aitken=
 [mailto:paitken@cisco.com] <br><b>Sent:</b> Friday, January 31, 2014 4:17 =
PM<br><b>To:</b> Moriarty, Kathleen; gen-art@ietf.org; iesg@ietf.org; draft=
-yourtchenko-cisco-ies.all@tools.ietf.org<br><b>Cc:</b> ayourtch@cisco.com;=
 bclaise@cisco.com; draft-yourtchenko-cisco-ies@tools.ietf.org<br><b>Subjec=
t:</b> Re: Gen-art review of draft-yourtchenko-cisco-ies-09<o:p></o:p></spa=
n></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=
=3DMsoNormal style=3D'margin-bottom:12.0pt'>Kathleen, All,<br><br>Apologies=
 for jumping in here, but I wasn't privvy to the earlier discussion to whic=
h you allude.<o:p></o:p></p></div><blockquote style=3D'margin-top:5.0pt;mar=
gin-bottom:5.0pt'><div><p class=3DMsoPlainText>Summary:&nbsp; This draft ex=
tends <span style=3D'font-size:10.0pt;font-family:"Courier New"'>RFC3954, b=
ut is specific to Cisco.</span><o:p></o:p></p></div></blockquote><p class=
=3DMsoNormal><br>No, this draft does not extend RFC 3954.<br><br>RFC 3954 s=
pecifies the NFv9 Protocol and the associated Information Model. The model =
is extensible, and I own the netflow-police hat for reviewing, approving, a=
nd actioning NFv9 extensions.<br><br>The IPFIX Protocol (RFC 7011) has its =
own Information Model (RFC 7012, IANA) which is also extensible upon applic=
ation to IANA, subject to expert review by IE-doctors (RFC 7013).<br><br>Th=
e yourtchenko-cisco-ies draft extends the IPFIX Information model. Per sect=
ion <span class=3Dmh>6 of the draft, &quot;IANA Considerations&quot;:</span=
><o:p></o:p></p><pre><o:p>&nbsp;</o:p></pre><pre>&nbsp;&nbsp; This document=
 specifies several new IPFIX Information Elements in the<o:p></o:p></pre><p=
re>&nbsp;&nbsp; IPFIX Information Element registry<o:p></o:p></pre><p class=
=3DMsoNormal><br>The IPFIX Information Model was initially based upon the N=
Fv9 Information Model. Indeed, the two are generally considered to be synon=
ymous.<br><br>The extensions which are being added to the IPFIX model seek =
to retain that synonymity by describing NFv9 elements which were not known =
or defined at the time RFC 3954 was written. These can be adopted into the =
IPFIX Information Model to retain compatibility, rather than defining equiv=
alent IPFIX elements with different IDs from NFv9 and thus complicating lif=
e for every netflow collector.<br><br>Note that this is not a change to eit=
her the NFv9 or IPFIX protocols.<br><br><br>P. <br><br><o:p></o:p></p><p cl=
ass=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_F5063677821E3B4F81ACFB7905573F24065A5E9111MX15Acorpemcc_--

From ben@nostrum.com  Fri Jan 31 14:57:15 2014
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD7281AC7EE for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 14:57:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8RbjkvnA4zCz for <gen-art@ietfa.amsl.com>; Fri, 31 Jan 2014 14:57:14 -0800 (PST)
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 B7C551AC4C1 for <gen-art@ietf.org>; Fri, 31 Jan 2014 14:57:14 -0800 (PST)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0VMv8bg061620 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 31 Jan 2014 16:57:10 -0600 (CST) (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, 31 Jan 2014 16:57:06 -0600
Message-Id: <8C9EE7F2-AA3D-482A-B469-4A147D143954@nostrum.com>
To: draft-ietf-radext-ieee802ext.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
X-Mailer: Apple Mail (2.1827)
Received-SPF: pass (shaman.nostrum.com: 173.172.146.58 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-radext-ieee802ext-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 31 Jan 2014 22:57:15 -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-radext-ieee802ext-10
Reviewer: Ben Campbell
Review Date: 2014-01-31
IETF LC End Date: 2014-02-04

Summary: This draft is almost ready for publication as a standards track =
RFC. I have a small number of minor comments that may be worth =
considering prior to publication.

Major issues: None

Minor issues:=20

-- 2.1, last paragraph:

Does the last sentence imply Allowed-Called-Station-Id actually should =
(or SHOULD) not be used in non-wireless scenarios? (I note that the =
Network-Id-Name section talks about how 802.1X NID-Names should not be =
included in Called-Station-Id, but rather put in Network-Id-Name. Does =
that apply here as well?

-- 2.2, last paragraph: "Since a NAS will typically only include a =
EAP-Key-Name Attribute in an Access-Request in situations where the =
Attribute is required to provision service, if an EAP-Key-Name Attribute =
is included in an Access-Request but is not present in the =
Access-Accept, the NAS SHOULD treat the Access-Accept as though it were =
an Access-Reject. "

Is there a backwards compatibility issue? What if a NAS sends the field =
to a server that doesn't implement this draft? Is there an assumption =
that a NAS that supports this draft will only work with a server that =
also supports it?=20

Or more to the point, is the "...typically only include...where =
required..." strong enough to require a normative SHOULD? Seems like =
this would discourage the inclusion of EAP-Key-Name in the non-typical =
case of it _not_ being required. Is that the intent?

Nits/editorial comments:

-- section 2.8:

It might be worth expanding "EAPoL"




From abdussalambaryun@gmail.com  Fri Jan 31 17:02:56 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4677F1ACCE8; Fri, 31 Jan 2014 17:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gpt5uh54tFlD; Fri, 31 Jan 2014 17:02:55 -0800 (PST)
Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) by ietfa.amsl.com (Postfix) with ESMTP id F3A001ACCDE; Fri, 31 Jan 2014 17:02:54 -0800 (PST)
Received: by mail-yk0-f172.google.com with SMTP id 200so3104114ykr.3 for <multiple recipients>; Fri, 31 Jan 2014 17:02:51 -0800 (PST)
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=qqPs2UxS5NFXugh/pnaXT2o0UkmIcxKPEmBp4CPEFSo=; b=qZByQkUK2Dc4/mk9wB9Xmtx0MOG24BUuzXBjXGPIksVgNP2VcWYviTbKd7ju4Wg67N L6ByksrirIkhJ1qxdtuQLGdnIICg4ZhA5NiILJEKRxu4vbk6sCEglWHCbj+64wdnnsjp SwkDoVuHsXCQ8gFFBz0m/yoJ+62FpwW3Ghq+LpsO5UFYknoxq/iS0lxEPoDKlgRtaay6 yK03PmfMY5SVxgmdK5HBYzeYNF6z91PIBszloUQZwakaxN4x56nI7uhBrkUtcYcOJd6Q O4HKDOAMVxPPb9c51pNegSCyXDZe3eUsND9NWJf2jFi8WUi/1bTlhy8Gyp9uEChj6vYv 8FMg==
MIME-Version: 1.0
X-Received: by 10.236.100.173 with SMTP id z33mr21608894yhf.9.1391216571064; Fri, 31 Jan 2014 17:02:51 -0800 (PST)
Received: by 10.170.220.213 with HTTP; Fri, 31 Jan 2014 17:02:51 -0800 (PST)
In-Reply-To: <tslmwic59vw.fsf@mit.edu>
References: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@mail.gmail.com> <tslmwic59vw.fsf@mit.edu>
Date: Sat, 1 Feb 2014 02:02:51 +0100
Message-ID: <CADnDZ89Tr-DOA100QeszaafW3ZyThAM0UX=xWN7zzYx8rERhnQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Content-Type: multipart/alternative; boundary=20cf3005e01886256f04f14dd9cc
X-Mailman-Approved-At: Fri, 31 Jan 2014 17:07:31 -0800
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-perpass-attack.all@tools.ietf.org" <draft-farrell-perpass-attack.all@tools.ietf.org>
Subject: Re: [Gen-art] GEN-ART telechat review of draft-farrell-perpass-attack-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 01 Feb 2014 01:02:56 -0000

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

On Friday, January 31, 2014, Sam Hartman wrote:

> Thanks Scott.
> In the interest of being clear about my position, I support publication
> of 04 but do not support publication of 05.


I don't know why you object 05.

>
> I think all the discussion that is useful has happened and all that
> remains is the consensus call from the sponsoring AD.
>

The AD should read all comments from the community of practical
statements and AD to follow/sponsor reasonable statements/discussions or
policies, not sponsoring best future plan as best current practice ( it may
be initial plan for BCP).

IMHO, the AD powers are not to be used against reasonable engineering
discussions/requests only if that AD has done sound reasonable
engineering replies.

AB

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

<br><br>On Friday, January 31, 2014, Sam Hartman  wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">Thanks Scott.<br>
In the interest of being clear about my position, I support publication<br>
of 04 but do not support publication of 05.</blockquote><div><br></div><div=
>I don&#39;t know why you object 05.=A0=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">

<br>
I think all the discussion that is useful has happened and all that<br>
remains is the consensus call from the sponsoring AD.<br>
</blockquote><div><br></div><div>The AD should read all comments from the c=
ommunity of practical statements=A0and AD=A0to follow/sponsor=A0reasonable =
statements/discussions=A0or policies,=A0not sponsoring best future plan as =
best current practice ( it may be initial plan for BCP).</div>
<div><br></div><div>IMHO, the AD powers are not to be used against reasonab=
le engineering discussions/requests=A0only if that AD=A0has done sound=A0re=
asonable engineering=A0replies.=A0</div><div><br></div><div>AB</div>

--20cf3005e01886256f04f14dd9cc--
