
From nobody Tue Apr  1 05:30:55 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 E8A6F1A06B7 for <gen-art@ietfa.amsl.com>; Tue,  1 Apr 2014 05:30:52 -0700 (PDT)
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 u8b6eGBLEa2r for <gen-art@ietfa.amsl.com>; Tue,  1 Apr 2014 05:30:50 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by ietfa.amsl.com (Postfix) with ESMTP id 191DC1A06B6 for <gen-art@ietf.org>; Tue,  1 Apr 2014 05:30:49 -0700 (PDT)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda10.si.francetelecom.fr (ESMTP service) with ESMTP id 92767374490; Tue,  1 Apr 2014 14:30:45 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 2050BC8101; Tue,  1 Apr 2014 14:30:45 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.11]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Tue, 1 Apr 2014 14:30:28 +0200
From: <mohamed.boucadair@orange.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Tue, 1 Apr 2014 14:30:18 +0200
Thread-Topic: Gen-ART review of draft-ietf-pcp-dhcp-09
Thread-Index: Ac9Fpwf/9xTcRrHXRFa3srTdvkpCagBh4qPQADXLCnAAA8O1kAABVDUwAWL3N0A=
Message-ID: <94C682931C08B048B7A8645303FDC9F36F54484A22@PUEXCB1B.nanterre.francetelecom.fr>
References: <7594FB04B1934943A5C02806D1A2204B1D25AC4A@ESESSMB209.ericsson.se> <94C682931C08B048B7A8645303FDC9F36F528DE334@PUEXCB1B.nanterre.francetelecom.fr> <7594FB04B1934943A5C02806D1A2204B1D25FC1D@ESESSMB209.ericsson.se> <94C682931C08B048B7A8645303FDC9F36F528DE78F@PUEXCB1B.nanterre.francetelecom.fr> <7594FB04B1934943A5C02806D1A2204B1D25FFB5@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D25FFB5@ESESSMB209.ericsson.se>
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_94C682931C08B048B7A8645303FDC9F36F54484A22PUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.4.1.90014
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/7AmegyLZY2rzAzASZ6HGaD-KorM
Cc: "draft-ietf-pcp-dhcp.all@tools.ietf.org" <draft-ietf-pcp-dhcp.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pcp-dhcp-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, 01 Apr 2014 12:30:53 -0000

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

Dear Christer,

FYI, a new version is now available online. The new version integrates your=
 comments. You may double check at this url:

http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&url2=3Ddraft-ietf-pcp-dhc=
p-10.txt

Cheers,
Med

De : Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Envoy=E9 : mardi 25 mars 2014 12:06
=C0 : BOUCADAIR Mohamed IMT/OLN; gen-art@ietf.org
Cc : draft-ietf-pcp-dhcp.all@tools.ietf.org
Objet : RE: Gen-ART review of draft-ietf-pcp-dhcp-09

Thanks! :)

That addresses all my issues.

Regards,

Christer

From: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> [ma=
ilto:mohamed.boucadair@orange.com]
Sent: 25. maaliskuuta 2014 12:29
To: Christer Holmberg; gen-art@ietf.org<mailto:gen-art@ietf.org>
Cc: draft-ietf-pcp-dhcp.all@tools.ietf.org<mailto:draft-ietf-pcp-dhcp.all@t=
ools.ietf.org>
Subject: RE: Gen-ART review of draft-ietf-pcp-dhcp-09

Dear Christer,

Your proposed text reflects exactly the intent. I updated my local copy of =
the draft accordingly.

Thank you for the review.

Cheers,
Med


De : Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Envoy=E9 : mardi 25 mars 2014 09:50
=C0 : BOUCADAIR Mohamed IMT/OLN; gen-art@ietf.org<mailto:gen-art@ietf.org>
Cc : draft-ietf-pcp-dhcp.all@tools.ietf.org<mailto:draft-ietf-pcp-dhcp.all@=
tools.ietf.org>
Objet : RE: Gen-ART review of draft-ietf-pcp-dhcp-09

Hi Med,

I am ok with most of your replies, but I still have an issue with the deplo=
yment scenario statement.

Q1_A:

The Abstract (and, later, also the Introduction) says: "The use of DHCPv4 o=
r DHCPv6 depends on the PCP deployment scenario."

I think this is a little unclear. Would it be possible to add some extra te=
xt, describing in what type of scenarios the mechanism is applicable?

[Med] The decision to use DHCPv4 or DHCPv6 is deployment-specific. The text=
 calls out one particular deployment case where dhcpv6 is used to configure=
 an IPv4 PCP server (see section 5). It is out of scope of the document to =
list in which cases dhcpv4, dhcpv6, or both will be used to configure pcp s=
ervers. I suggest to maintain that sentence as it is.

[Christer] RFC 6887 lists different scenarios, and when reading the sentenc=
e above I get a picture that usage of DHCPv4/DHCPv6 applies specifically to=
 some of those scenarios, but not to others.

So, if the applicable scenarios are out of the scope of the document, then =
you should say that. Perhaps something like:

"The use of DHCPv4 or DHCPv6 depends on the PCP deployment scenario. The se=
t of deployment scenarios to which use of DHCPv4 or DHCPv6 apply are outsid=
e the scope of this document."

Regards,

Christer

--_000_94C682931C08B048B7A8645303FDC9F36F54484A22PUEXCB1Bnante_
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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	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: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: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.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	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:"Times New Roman","serif";
	mso-fareast-language:EN-GB;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	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.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#993366;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle30
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:#003300;}
.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=3DEN-US link=3D"#0563C1=
" vlink=3D"#954F72"><div class=3DWordSection1><p class=3DMsoNormal><span st=
yle=3D'font-size:10.0pt;font-family:"Courier New";color:#003300'>Dear Chris=
ter,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:"Courier New";color:#003300'><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New=
";color:#003300'>FYI, a new version is now available online. The new versio=
n integrates your comments. You may double check at this url:<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"C=
ourier New";color:#003300'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:10.0pt;font-family:"Courier New";color:#003300'><=
a href=3D"http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&amp;url2=3Ddraf=
t-ietf-pcp-dhcp-10.txt">http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&a=
mp;url2=3Ddraft-ietf-pcp-dhcp-10.txt</a> <o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:#0=
03300'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:"Courier New";color:#003300'>Cheers,<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"C=
ourier New";color:#003300'>Med<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Courier New";color:#003300'><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:so=
lid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DFR style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&n=
bsp;:</span></b><span lang=3DFR style=3D'font-size:10.0pt;font-family:"Taho=
ma","sans-serif"'> Christer Holmberg [mailto:christer.holmberg@ericsson.com=
] <br><b>Envoy=E9&nbsp;:</b> mardi 25 mars 2014 12:06<br><b>=C0&nbsp;:</b> =
BOUCADAIR Mohamed IMT/OLN; gen-art@ietf.org<br><b>Cc&nbsp;:</b> draft-ietf-=
pcp-dhcp.all@tools.ietf.org<br><b>Objet&nbsp;:</b> RE: Gen-ART review of dr=
aft-ietf-pcp-dhcp-09<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'>Tha=
nks! </span><span style=3D'font-family:Wingdings;color:#1F497D'>J</span><o:=
p></o:p></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>&nbsp;</span=
><o:p></o:p></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>That add=
resses all my issues.</span><o:p></o:p></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span s=
tyle=3D'color:#1F497D'>Regards,</span><o:p></o:p></p><p class=3DMsoNormal><=
span style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNorm=
al><span style=3D'color:#1F497D'>Christer</span><o:p></o:p></p><p class=3DM=
soNormal><span style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div><di=
v style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm=
 0cm'><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"'> <a href=3D"mailto:mohamed.boucadair@orange.c=
om">mohamed.boucadair@orange.com</a> [<a href=3D"mailto:mohamed.boucadair@o=
range.com">mailto:mohamed.boucadair@orange.com</a>] <br><b>Sent:</b> 25. ma=
aliskuuta 2014 12:29<br><b>To:</b> Christer Holmberg; <a href=3D"mailto:gen=
-art@ietf.org">gen-art@ietf.org</a><br><b>Cc:</b> <a href=3D"mailto:draft-i=
etf-pcp-dhcp.all@tools.ietf.org">draft-ietf-pcp-dhcp.all@tools.ietf.org</a>=
<br><b>Subject:</b> RE: Gen-ART review of draft-ietf-pcp-dhcp-09</span><o:p=
></o:p></p></div></div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:#993366'>Dear Christer,</span><o:p></o:p></p><p class=3DMsoNormal><span s=
tyle=3D'font-size:10.0pt;font-family:"Courier New";color:#993366'>&nbsp;</s=
pan><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Courier New";color:#993366'>Your proposed text reflects exactly t=
he intent. I updated my local copy of the draft accordingly.</span><o:p></o=
:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Co=
urier New";color:#993366'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal>=
<span style=3D'font-size:10.0pt;font-family:"Courier New";color:#993366'>Th=
ank you for the review.</span><o:p></o:p></p><p class=3DMsoNormal><span sty=
le=3D'font-size:10.0pt;font-family:"Courier New";color:#993366'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-=
family:"Courier New";color:#993366'>Cheers,</span><o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:#993366'>Med</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'fon=
t-size:10.0pt;font-family:"Courier New";color:#993366'>&nbsp;</span><o:p></=
o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"C=
ourier New";color:#993366'>&nbsp;</span><o:p></o:p></p><div style=3D'border=
:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div sty=
le=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'=
><p class=3DMsoNormal><b><span lang=3DFR style=3D'font-size:10.0pt;font-fam=
ily:"Tahoma","sans-serif"'>De&nbsp;:</span></b><span lang=3DFR style=3D'fon=
t-size:10.0pt;font-family:"Tahoma","sans-serif"'> Christer Holmberg [<a hre=
f=3D"mailto:christer.holmberg@ericsson.com">mailto:christer.holmberg@ericss=
on.com</a>] <br><b>Envoy=E9&nbsp;:</b> mardi 25 mars 2014 09:50<br><b>=C0&n=
bsp;:</b> BOUCADAIR Mohamed IMT/OLN; <a href=3D"mailto:gen-art@ietf.org">ge=
n-art@ietf.org</a><br><b>Cc&nbsp;:</b> <a href=3D"mailto:draft-ietf-pcp-dhc=
p.all@tools.ietf.org">draft-ietf-pcp-dhcp.all@tools.ietf.org</a><br><b>Obje=
t&nbsp;:</b> RE: Gen-ART review of draft-ietf-pcp-dhcp-09</span><o:p></o:p>=
</p></div></div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNor=
mal><span style=3D'color:#1F497D'>Hi Med,</span><o:p></o:p></p><p class=3DM=
soNormal><span style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'color:#1F497D'>I am ok with most of your replie=
s, but I still have an issue with the deployment scenario statement.</span>=
<o:p></o:p></p><div style=3D'border:none;border-left:solid blue 1.5pt;paddi=
ng:0cm 0cm 0cm 4.0pt'><p class=3DMsoPlainText style=3D'mso-margin-top-alt:a=
uto;mso-margin-bottom-alt:auto'><b><span style=3D'font-size:12.0pt;font-fam=
ily:"Times New Roman","serif"'>Q1_A</span></b><span style=3D'font-size:12.0=
pt;font-family:"Times New Roman","serif"'>:</span><o:p></o:p></p><p class=
=3DMsoPlainText style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto=
'><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>Th=
e Abstract (and, later, also the Introduction) says: &#8220;The use of DHCP=
v4 or DHCPv6 depends on the PCP deployment scenario.&#8221;</span><o:p></o:=
p></p><p class=3DMsoPlainText style=3D'mso-margin-top-alt:auto;mso-margin-b=
ottom-alt:auto'><span style=3D'font-size:12.0pt;font-family:"Times New Roma=
n","serif"'>I think this is a little unclear. Would it be possible to add s=
ome extra text, describing in what type of scenarios the mechanism is appli=
cable?</span><o:p></o:p></p><p class=3DMsoPlainText style=3D'mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto'><b><i><span style=3D'font-size:10.0pt=
;font-family:"Courier New";color:#1F497D'>[Med] The decision to use DHCPv4 =
or DHCPv6 is deployment-specific. The text calls out one particular deploym=
ent case where dhcpv6 is used to configure an IPv4 PCP server (see section =
5). It is out of scope of the document to list in which cases dhcpv4, dhcpv=
6, or both will be used to configure pcp servers. I suggest to maintain tha=
t sentence as it is.</span></i></b><o:p></o:p></p><p class=3DMsoPlainText s=
tyle=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=3DEN=
-GB style=3D'color:red'>[Christer] RFC 6887 lists different scenarios, and =
when reading the sentence above I get a picture that usage of DHCPv4/DHCPv6=
 applies specifically to some of those scenarios, but not to others.</span>=
<o:p></o:p></p><p class=3DMsoPlainText style=3D'mso-margin-top-alt:auto;mso=
-margin-bottom-alt:auto'><span lang=3DEN-GB style=3D'color:red'>So, if the =
applicable scenarios are out of the scope of the document, then you should =
say that. Perhaps something like:</span><o:p></o:p></p><p class=3DMsoPlainT=
ext style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=
=3DEN-GB style=3D'color:red'>&#8220;The use of DHCPv4 or DHCPv6 depends on =
the PCP deployment scenario. The set of deployment scenarios to which use o=
f DHCPv4 or DHCPv6 apply are outside the scope of this document.&#8221;</sp=
an><o:p></o:p></p><p class=3DMsoPlainText style=3D'mso-margin-top-alt:auto;=
mso-margin-bottom-alt:auto'><span lang=3DEN-GB style=3D'color:red'>Regards,=
</span><o:p></o:p></p><p class=3DMsoPlainText style=3D'mso-margin-top-alt:a=
uto;mso-margin-bottom-alt:auto'><span lang=3DEN-GB style=3D'color:red'>Chri=
ster</span><o:p></o:p></p></div></div></div></div></body></html>=

--_000_94C682931C08B048B7A8645303FDC9F36F54484A22PUEXCB1Bnante_--


From nobody Tue Apr  1 05:36:03 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 622411A06B7 for <gen-art@ietfa.amsl.com>; Tue,  1 Apr 2014 05:35:59 -0700 (PDT)
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 vBvcngCRDEqP for <gen-art@ietfa.amsl.com>; Tue,  1 Apr 2014 05:35:55 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id E1B7D1A06A1 for <gen-art@ietf.org>; Tue,  1 Apr 2014 05:35:54 -0700 (PDT)
X-AuditID: c1b4fb38-b7f518e000000889-e1-533ab2a65afe
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 73.A6.02185.6A2BA335; Tue,  1 Apr 2014 14:35:50 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0174.001; Tue, 1 Apr 2014 14:35:50 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-pcp-dhcp-09
Thread-Index: Ac9Fpwf/9xTcRrHXRFa3srTdvkpCagBh4qPQADXLCnAAA8O1kAABVDUwAWL3N0AAADkVoA==
Date: Tue, 1 Apr 2014 12:35:49 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D271658@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D25AC4A@ESESSMB209.ericsson.se> <94C682931C08B048B7A8645303FDC9F36F528DE334@PUEXCB1B.nanterre.francetelecom.fr> <7594FB04B1934943A5C02806D1A2204B1D25FC1D@ESESSMB209.ericsson.se> <94C682931C08B048B7A8645303FDC9F36F528DE78F@PUEXCB1B.nanterre.francetelecom.fr> <7594FB04B1934943A5C02806D1A2204B1D25FFB5@ESESSMB209.ericsson.se> <94C682931C08B048B7A8645303FDC9F36F54484A22@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36F54484A22@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D271658ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrALMWRmVeSWpSXmKPExsUyM+Jvje6yTVbBBnOPqVvM+v6K1eLqq88s FoffPmV3YPZYsuQnk0fLs5NsHl8uf2YLYI7isklJzcksSy3St0vgyrjx9ihbwYQpjBVLTqxn bmDc3MLYxcjJISFgInGi6RwrhC0mceHeerYuRi4OIYGjjBJnfs9hhnAWM0qcW9QOlOHgYBOw kOj+pw3SICKQJbFrzx9mEJtZIFxizqPPTCC2sICpxI3NB1khaswkZk3eyQhhh0kcu9YIFmcR UJHoP3AeLM4r4CuxaO5Bdohdp5kl9r38xw6S4BSIkbj1/g6YzQh03fdTa5gglolL3Hoynwni agGJJXvOM0PYohIvH/+D+kZR4uOrfYwgNzML5EtcfJgCsUtQ4uTMJywTGEVnIZk0C6FqFpIq iBI9iRtTp7BB2NoSyxa+ZoawdSVm/DvEgiy+gJF9FSNHcWpxUm66kcEmRmCsHdzy22IH4+W/ NocYpTlYlMR5P751DhISSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAuMb8s5i7g/jdld1s9bvW yr3Xu9qisU2z3q19vW2NjGTwXxn1ozc1DCYuOuJp9nBB+RVV6fJn6mulJm/n+bQyMcOL3/1z 0rIL+SnLdn4NNLs1cb/qu6WBbkqX9ur2XGGapxrusCxhisS692Ear9+eFdZcdqJedIbrztTo K6ubnDJ9DhfK1iiVKLEUZyQaajEXFScCAPwtqDSDAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/nfJz9CgSbJ7bGXUDvGF5NomtfQM
Cc: "draft-ietf-pcp-dhcp.all@tools.ietf.org" <draft-ietf-pcp-dhcp.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pcp-dhcp-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, 01 Apr 2014 12:35:59 -0000

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

Hi Med,

Everything looks good from my perspective :)

Regards,

Christer

From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
Sent: 1. huhtikuuta 2014 15:30
To: Christer Holmberg; gen-art@ietf.org
Cc: draft-ietf-pcp-dhcp.all@tools.ietf.org
Subject: RE: Gen-ART review of draft-ietf-pcp-dhcp-09

Dear Christer,

FYI, a new version is now available online. The new version integrates your=
 comments. You may double check at this url:

http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&url2=3Ddraft-ietf-pcp-dhc=
p-10.txt

Cheers,
Med

De : Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Envoy=E9 : mardi 25 mars 2014 12:06
=C0 : BOUCADAIR Mohamed IMT/OLN; gen-art@ietf.org<mailto:gen-art@ietf.org>
Cc : draft-ietf-pcp-dhcp.all@tools.ietf.org<mailto:draft-ietf-pcp-dhcp.all@=
tools.ietf.org>
Objet : RE: Gen-ART review of draft-ietf-pcp-dhcp-09

Thanks! :)

That addresses all my issues.

Regards,

Christer

From: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> [ma=
ilto:mohamed.boucadair@orange.com]
Sent: 25. maaliskuuta 2014 12:29
To: Christer Holmberg; gen-art@ietf.org<mailto:gen-art@ietf.org>
Cc: draft-ietf-pcp-dhcp.all@tools.ietf.org<mailto:draft-ietf-pcp-dhcp.all@t=
ools.ietf.org>
Subject: RE: Gen-ART review of draft-ietf-pcp-dhcp-09

Dear Christer,

Your proposed text reflects exactly the intent. I updated my local copy of =
the draft accordingly.

Thank you for the review.

Cheers,
Med


De : Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Envoy=E9 : mardi 25 mars 2014 09:50
=C0 : BOUCADAIR Mohamed IMT/OLN; gen-art@ietf.org<mailto:gen-art@ietf.org>
Cc : draft-ietf-pcp-dhcp.all@tools.ietf.org<mailto:draft-ietf-pcp-dhcp.all@=
tools.ietf.org>
Objet : RE: Gen-ART review of draft-ietf-pcp-dhcp-09

Hi Med,

I am ok with most of your replies, but I still have an issue with the deplo=
yment scenario statement.

Q1_A:

The Abstract (and, later, also the Introduction) says: "The use of DHCPv4 o=
r DHCPv6 depends on the PCP deployment scenario."

I think this is a little unclear. Would it be possible to add some extra te=
xt, describing in what type of scenarios the mechanism is applicable?

[Med] The decision to use DHCPv4 or DHCPv6 is deployment-specific. The text=
 calls out one particular deployment case where dhcpv6 is used to configure=
 an IPv4 PCP server (see section 5). It is out of scope of the document to =
list in which cases dhcpv4, dhcpv6, or both will be used to configure pcp s=
ervers. I suggest to maintain that sentence as it is.

[Christer] RFC 6887 lists different scenarios, and when reading the sentenc=
e above I get a picture that usage of DHCPv4/DHCPv6 applies specifically to=
 some of those scenarios, but not to others.

So, if the applicable scenarios are out of the scope of the document, then =
you should say that. Perhaps something like:

"The use of DHCPv4 or DHCPv6 depends on the PCP deployment scenario. The se=
t of deployment scenarios to which use of DHCPv4 or DHCPv6 apply are outsid=
e the scope of this document."

Regards,

Christer

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	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:"Times New Roman","serif";
	mso-fareast-language:EN-GB;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	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:0cm;
	margin-bottom:.0001pt;
	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.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#993366;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#003300;}
span.EmailStyle31
	{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"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Med,<o:p></o:p></sp=
an></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">Everything looks good =
from my perspective
</span><span style=3D"font-family:Wingdings;color:#1F497D">J</span><span st=
yle=3D"color:#1F497D"><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">Regards,<o:p></o:p></s=
pan></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">Christer<o:p></o:p></s=
pan></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 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;"> mohamed.=
boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
<br>
<b>Sent:</b> 1. huhtikuuta 2014 15:30<br>
<b>To:</b> Christer Holmberg; gen-art@ietf.org<br>
<b>Cc:</b> draft-ietf-pcp-dhcp.all@tools.ietf.org<br>
<b>Subject:</b> RE: Gen-ART review of draft-ietf-pcp-dhcp-09<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#003300">Dear Christer,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#003300"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#003300">FYI, a new version is now available online. =
The new version integrates your comments. You may double check at this url:=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#003300"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#003300"><a href=3D"http://tools.ietf.org/rfcdiff?dif=
ftype=3D--hwdiff&amp;url2=3Ddraft-ietf-pcp-dhcp-10.txt">http://tools.ietf.o=
rg/rfcdiff?difftype=3D--hwdiff&amp;url2=3Ddraft-ietf-pcp-dhcp-10.txt</a>
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#003300"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#003300">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#003300">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#003300"><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 lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span=
 lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;"> Christer Holmberg [<a href=3D"mailto:christer.holmberg@=
ericsson.com">mailto:christer.holmberg@ericsson.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> mardi 25 mars 2014 12:06<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; <a href=3D"mailto:gen-art@ietf=
.org">gen-art@ietf.org</a><br>
<b>Cc&nbsp;:</b> <a href=3D"mailto:draft-ietf-pcp-dhcp.all@tools.ietf.org">=
draft-ietf-pcp-dhcp.all@tools.ietf.org</a><br>
<b>Objet&nbsp;:</b> RE: Gen-ART review of draft-ietf-pcp-dhcp-09<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">Thanks! </span><span s=
tyle=3D"font-family:Wingdings;color:#1F497D">J</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">That addresses all my =
issues.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=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;">
<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> 25. maaliskuuta 2014 12:29<br>
<b>To:</b> Christer Holmberg; <a href=3D"mailto:gen-art@ietf.org">gen-art@i=
etf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:draft-ietf-pcp-dhcp.all@tools.ietf.org">draft-=
ietf-pcp-dhcp.all@tools.ietf.org</a><br>
<b>Subject:</b> RE: Gen-ART review of draft-ietf-pcp-dhcp-09</span><o:p></o=
:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#993366">Dear Christer,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#993366">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#993366">Your proposed text reflects exactly the inte=
nt. I updated my local copy of the draft accordingly.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#993366">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#993366">Thank you for the review.</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#993366">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#993366">Cheers,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#993366">Med</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#993366">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#993366">&nbsp;</span><o:p></o:p></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 lang=3D"FR" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">De&nbsp;:</span></b><span=
 lang=3D"FR" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;"> Christer Holmberg [<a href=3D"mailto:christer.holmberg@=
ericsson.com">mailto:christer.holmberg@ericsson.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> mardi 25 mars 2014 09:50<br>
<b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; <a href=3D"mailto:gen-art@ietf=
.org">gen-art@ietf.org</a><br>
<b>Cc&nbsp;:</b> <a href=3D"mailto:draft-ietf-pcp-dhcp.all@tools.ietf.org">=
draft-ietf-pcp-dhcp.all@tools.ietf.org</a><br>
<b>Objet&nbsp;:</b> RE: Gen-ART review of draft-ietf-pcp-dhcp-09</span><o:p=
></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Med,</span><o:p></o=
:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I am ok with most of y=
our replies, but I still have an issue with the deployment scenario stateme=
nt.</span><o:p></o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<p class=3D"MsoPlainText" style=3D"mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto">
<b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,=
&quot;serif&quot;">Q1_A</span></b><span style=3D"font-size:12.0pt;font-fami=
ly:&quot;Times New Roman&quot;,&quot;serif&quot;">:</span><o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto">
<span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&qu=
ot;serif&quot;">The Abstract (and, later, also the Introduction) says: &#82=
20;The use of DHCPv4 or DHCPv6 depends on the PCP deployment scenario.&#822=
1;</span><o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto">
<span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&qu=
ot;serif&quot;">I think this is a little unclear. Would it be possible to a=
dd some extra text, describing in what type of scenarios the mechanism is a=
pplicable?</span><o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto">
<b><i><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;c=
olor:#1F497D">[Med] The decision to use DHCPv4 or DHCPv6 is deployment-spec=
ific. The text calls out one particular deployment case where dhcpv6 is use=
d to configure an IPv4 PCP server (see section
 5). It is out of scope of the document to list in which cases dhcpv4, dhcp=
v6, or both will be used to configure pcp servers. I suggest to maintain th=
at sentence as it is.</span></i></b><o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto">
<span lang=3D"EN-GB" style=3D"color:red">[Christer] RFC 6887 lists differen=
t scenarios, and when reading the sentence above I get a picture that usage=
 of DHCPv4/DHCPv6 applies specifically to some of those scenarios, but not =
to others.</span><o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto">
<span lang=3D"EN-GB" style=3D"color:red">So, if the applicable scenarios ar=
e out of the scope of the document, then you should say that. Perhaps somet=
hing like:</span><o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto">
<span lang=3D"EN-GB" style=3D"color:red">&#8220;The use of DHCPv4 or DHCPv6=
 depends on the PCP deployment scenario. The set of deployment scenarios to=
 which use of DHCPv4 or DHCPv6 apply are outside the scope of this document=
.&#8221;</span><o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto">
<span lang=3D"EN-GB" style=3D"color:red">Regards,</span><o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto">
<span lang=3D"EN-GB" style=3D"color:red">Christer</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D271658ESESSMB209erics_--


From nobody Tue Apr  1 05:44:40 2014
Return-Path: <Frederic.Jounay@orange.ch>
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 71DA81A06BE for <gen-art@ietfa.amsl.com>; Tue,  1 Apr 2014 05:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.819
X-Spam-Level: 
X-Spam-Status: No, score=-0.819 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779, 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 uY_1aQuQFWMN for <gen-art@ietfa.amsl.com>; Tue,  1 Apr 2014 05:44:37 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.138]) by ietfa.amsl.com (Postfix) with ESMTP id 494271A06C5 for <gen-art@ietf.org>; Tue,  1 Apr 2014 05:44:36 -0700 (PDT)
Received: from [85.158.136.83:34581] by server-2.bemta-5.messagelabs.com id 0F/7B-12074-FA4BA335; Tue, 01 Apr 2014 12:44:31 +0000
X-Env-Sender: Frederic.Jounay@orange.ch
X-Msg-Ref: server-8.tower-36.messagelabs.com!1396356270!2323958!2
X-Originating-IP: [213.55.206.7]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10876 invoked from network); 1 Apr 2014 12:44:31 -0000
Received: from unknown (HELO chcrochs054.orange.ch) (213.55.206.7) by server-8.tower-36.messagelabs.com with RC4-SHA encrypted SMTP; 1 Apr 2014 12:44:31 -0000
Received: from CHCROCHC051.orange.ch ([fe80:0000:0000:0000:704b:3a68:12.14.247.83]) by chcrochs054.orange.ch ([172.19.166.54]) with mapi; Tue, 1 Apr 2014 14:44:27 +0200
From: =?utf-8?B?Sm91bmF5IEZyw6lkw6lyaWM=?= <Frederic.Jounay@orange.ch>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "draft-ietf-pwe3-p2mp-pw-requirements.all@tools.ietf.org" <draft-ietf-pwe3-p2mp-pw-requirements.all@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>
Date: Tue, 1 Apr 2014 14:44:26 +0200
Thread-Topic: Gen-ART LC review of draft-ietf-pwe3-p2mp-pw-requirements-07.txt
Thread-Index: Ac9CvcK5VacwHaDIR7yBAAEUtuHKggCIKC2QAjBCONA=
Message-ID: <78046FD1C8FE0345AFBC11640A8DF6E201864A00816E@CHCROCHC051.orange.ch>
References: <53286465.4040802@gmail.com> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/TLeKWMs7WcCYo4RTGDyLr6iArl4
Cc: "Adrian Farrel \(adrian@olddog.co.uk\)" <adrian@olddog.co.uk>, "Andrew G. Malis \(agmalis@gmail.com\)" <agmalis@gmail.com>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-pwe3-p2mp-pw-requirements-07.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, 01 Apr 2014 12:44:39 -0000

SGkgQnJpYW4sIA0KDQpXZSB3aWxsIHVwZGF0ZSB0aGUgZHJhZnQgdG8gY29ycmVjdCB0aGUgc2Vu
dGVuY2UgbWVhbmluZyANCg0KPiAzLjQuNy4gIFNjYWxhYmlsaXR5DQo+DQo+ICAgVGhlIHNvbHV0
aW9uIFNIT1VMRCBzY2FsZSBhdCB3b3JzdCBsaW5lYXJseSB3aXRoIHRoZSBudW1iZXIgb2YgTGVh
Zg0KPiAgIFBFcy4NCg0KDQpJIGRvbid0IHJlYWxseSBzZWUgaG93IHRvIGFkZHJlc3MgdGhlIHNl
Y29uZCBjb21tZW50DQoiVGhlIGRvY3VtZW50IGlzIHNjb3BlZCBmb3IgTVBMUyBzdWJzdHJhdGVz
LCBidXQgSSBzZWUgdmVyeSBsaXR0bGUgaW4gaXQgdGhhdCByZXF1aXJlcyBNUExTLiBBcmNoaXRl
Y3R1cmFsbHksIGl0IGlzIHF1aXRlIGdlbmVyYWwuIFdhcyB0aGVyZSBhbnkgY29uc2lkZXJhdGlv
biBvZiBtYWtpbmcgaXQgYXBwbGljYWJsZSB0byBhIG5vbi1NUExTIHN1YnN0cmF0ZT8iDQpUaGUg
ZHJhZnQgYWltcyBhdCBkZWZpbmluZyBQMk1QIFBzZXVkb3dpcmUsIHdoaWNoIGlzIGEgVlBOIGVu
YWJsZXIgYmFzZWQgb24gTVBMUyB0ZWNobm8gKFBXKSwgYnV0IGluIHRoZSB0ZXh0IHdlIG9wZW4g
dGhlIHVuZGVybHlpbmcgbGF5ZXIgdG8gUFNOIHR1bm5lbHMNCg0KQlIsDQpGcmVkIA0KDQoNCi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBKb3VuYXkgRnLDqWTDqXJpYyANClNlbnQ6
IEZyaWRheSwgMjEgTWFyY2ggMjAxNCAwOToyMQ0KVG86ICdCcmlhbiBFIENhcnBlbnRlcic7IGRy
YWZ0LWlldGYtcHdlMy1wMm1wLXB3LXJlcXVpcmVtZW50cy5hbGxAdG9vbHMuaWV0Zi5vcmc7IEdl
bmVyYWwgQXJlYSBSZXZpZXcgVGVhbQ0KU3ViamVjdDogUkU6IEdlbi1BUlQgTEMgcmV2aWV3IG9m
IGRyYWZ0LWlldGYtcHdlMy1wMm1wLXB3LXJlcXVpcmVtZW50cy0wNy50eHQNCg0KSGkgQnJpYW4s
DQoNClRoYW5rIHlvdSBmb3IgeW91ciBjb21tZW50LCBpbmRlZWQgdGhpcyBpcyBhbiBFbmdsaXNo
IGluYWNjdXJhY3kgOikNCg0KQlIsDQpGcmVkDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQpGcm9tOiBCcmlhbiBFIENhcnBlbnRlciBbbWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWls
LmNvbV0gDQpTZW50OiBUdWVzZGF5LCAxOCBNYXJjaCAyMDE0IDE2OjIxDQpUbzogZHJhZnQtaWV0
Zi1wd2UzLXAybXAtcHctcmVxdWlyZW1lbnRzLmFsbEB0b29scy5pZXRmLm9yZzsgR2VuZXJhbCBB
cmVhIFJldmlldyBUZWFtDQpTdWJqZWN0OiBHZW4tQVJUIExDIHJldmlldyBvZiBkcmFmdC1pZXRm
LXB3ZTMtcDJtcC1wdy1yZXF1aXJlbWVudHMtMDcudHh0DQoNCkkgYW0gdGhlIGFzc2lnbmVkIEdl
bi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZvciBiYWNrZ3JvdW5kIG9uIEdlbi1BUlQs
IHBsZWFzZSBzZWUgdGhlIEZBUSBhdCA8aHR0cDovL3dpa2kudG9vbHMuaWV0Zi5vcmcvYXJlYS9n
ZW4vdHJhYy93aWtpL0dlbkFydGZhcT4uDQoNClBsZWFzZSByZXNvbHZlIHRoZXNlIGNvbW1lbnRz
IGFsb25nIHdpdGggYW55IG90aGVyIExhc3QgQ2FsbCBjb21tZW50cyB5b3UgbWF5IHJlY2VpdmUu
DQoNCkRvY3VtZW50OiBkcmFmdC1pZXRmLXB3ZTMtcDJtcC1wdy1yZXF1aXJlbWVudHMtMDcudHh0
DQpSZXZpZXdlcjogQnJpYW4gQ2FycGVudGVyDQpSZXZpZXcgRGF0ZTogMjAxNC0wMy0xOA0KSUVU
RiBMQyBFbmQgRGF0ZTogMjAxNC0wMy0yNw0KSUVTRyBUZWxlY2hhdCBkYXRlOg0KDQpTdW1tYXJ5
OiBSZWFkeQ0KLS0tLS0tLS0NCg0KTWlub3IgaXNzdWVzOg0KLS0tLS0tLS0tLS0tLQ0KDQpUaGUg
ZG9jdW1lbnQgaXMgc2NvcGVkIGZvciBNUExTIHN1YnN0cmF0ZXMsIGJ1dCBJIHNlZSB2ZXJ5IGxp
dHRsZSBpbiBpdCB0aGF0IHJlcXVpcmVzIE1QTFMuIEFyY2h0ZWN0dXJhbGx5LCBpdCBpcyBxdWl0
ZSBnZW5lcmFsLiBXYXMgdGhlcmUgYW55IGNvbnNpZGVyYXRpb24gb2YgbWFraW5nIGl0IGFwcGxp
Y2FibGUgdG8gYSBub24tTVBMUyBzdWJzdHJhdGU/DQoNCj4gMy40LjcuICBTY2FsYWJpbGl0eQ0K
Pg0KPiAgIFRoZSBzb2x1dGlvbiBTSE9VTEQgc2NhbGUgYXQgbGVhc3QgbGluZWFybHkgd2l0aCB0
aGUgbnVtYmVyIG9mIExlYWYNCj4gICBQRXMuDQoNCkkgdGhpbmsgdGhpcyBzaG91bGQgYmUgImF0
IHdvcnN0IGxpbmVhcmx5Ii4NCg0KDQo=


From nobody Tue Apr  1 16:14:42 2014
Return-Path: <ales.vizdal@t-mobile.cz>
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 92CBD1A000F for <gen-art@ietfa.amsl.com>; Tue,  1 Apr 2014 16:14:40 -0700 (PDT)
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_50=0.8, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 TOzJd3O8x0Ra for <gen-art@ietfa.amsl.com>; Tue,  1 Apr 2014 16:14:37 -0700 (PDT)
Received: from ctxmailhub.t-mobile.cz (ctxmailhub.t-mobile.cz [93.153.104.87]) by ietfa.amsl.com (Postfix) with ESMTP id 5E99E1A000E for <gen-art@ietf.org>; Tue,  1 Apr 2014 16:14:37 -0700 (PDT)
From: =?iso-8859-2?Q?V=EDzdal_Ale=B9?= <ales.vizdal@t-mobile.cz>
To: Ben Campbell <ben@nostrum.com>, "draft-ietf-v6ops-64share.all@tools.ietf.org" <draft-ietf-v6ops-64share.all@tools.ietf.org>
Date: Wed, 2 Apr 2014 01:14:31 +0200
Thread-Topic: Gen-ART LC/Telechat Review of draft-ietf-v6ops-64share-09
Thread-Index: Ac9FO0171p16arsaQDabkhVipxouHgIvC3YQ
Message-ID: <1808340F7EC362469DDFFB112B37E2FCDA33129A66@SRVHKE02.rdm.cz>
References: <F415DB78-4352-4307-93CB-C26C09D7A98C@nostrum.com>
In-Reply-To: <F415DB78-4352-4307-93CB-C26C09D7A98C@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-loop: 2
Content-Type: multipart/alternative; boundary="_000_1808340F7EC362469DDFFB112B37E2FCDA33129A66SRVHKE02rdmcz_"
MIME-Version: 1.0
X-CFilter-Loop: Forwarded
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Axp4unwnRGtz6y5vBI1L4UoI87M
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC/Telechat Review of draft-ietf-v6ops-64share-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, 01 Apr 2014 23:14:40 -0000

--_000_1808340F7EC362469DDFFB112B37E2FCDA33129A66SRVHKE02rdmcz_
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

Dear Ben, all,



Many thanks for your review. An updated I-D has been submitted.



Please see inline.



> -----Original Message-----

> From: Ben Campbell [mailto:ben@nostrum.com]

> Sent: Friday, March 21, 2014 8:25 PM

> To: draft-ietf-v6ops-64share.all@tools.ietf.org

> Cc: gen-art@ietf.org Team (gen-art@ietf.org)

> Subject: Gen-ART LC/Telechat Review of draft-ietf-v6ops-

> 64share-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-v6ops-64share-09

> Reviewer: Ben Campbell

> Review Date: 2014-03-21

> IETF LC End Date: long time ago

> IESG Telechat date: 2014-03-27

>

> Note: I somehow missed this assignment at last call time.

> Therefore this review serves as both a last call and an IESG

> telechat review.

>

> Summary: This draft is mostly ready for publication as an

> informational RFC. I have a few editorial comments that might

> be worth considering prior to publication.

>

> Major issues: None

>

> Minor issues: None

>

> Nits/editorial comments:

>

> -- Section 1, paragraph 1:

>

> Can you elaborate on what it means to "extend" The prefix to

> a LAN link? Are we talking about routing IPv6 traffic from

> other local devices (on the LAN) across the 3gpp link, for

> example, like one might do when tethering devices to a phone

> or mobile hotspot?



Yes, this is the case.



> Can you offer a reference for "the 3GPP specification"?

>

> Can you offer a reference for "the 3GPP specification"?



Done.



> -- paragraph 2: "This can be achieved by receiving the Router

> Advertisement (RA) [RFC4861] announced globally unique /64

> IPv6 prefix from the 3GPP radio interface and then

> advertising"

>

> What does these things. The UE?



Yes, the UE. Ref to the UE has been added.



> Please expand RA on first mention.



Done.



>

> -- section 3, R-1:

>

> Please expand SLAAC on first use.



Done.



> -- section 4.2, 1st paragraph: "The 3GPP RA /64 prefix

> information is used to configure NDP on the LAN and assigns

> itself an address on the LAN link."

>

> The prefix information assigns itself an address? I don't

> think that's what you mean to say.



Fixed, please review.



> -- section 4.2, step 7:

>

> Please expand DAD on first use.



Done.



Cheers,

Ales

________________________________
Z=E1sady komunikace, kter=E9 spole=E8nost T-Mobile Czech Republic a.s. u=BE=
=EDv=E1 p=F8i sjedn=E1v=E1n=ED smluv, jsou uvedeny zde http://www.t-mobile.=
cz/zasady. Nen=ED-li v z=E1sad=E1ch uvedeno jinak, nep=F8edstavuje tato zpr=
=E1va kone=E8n=FD n=E1vrh na uzav=F8en=ED =E8i zm=ECnu smlouvy ani p=F8ijet=
=ED takov=E9ho n=E1vrhu. The communication principles which T-Mobile Czech =
Republic a.s. applies when negotiating contracts are defined here http://ww=
w.t-mobile.cz/principles. Unless otherwise stated in the principles, this m=
essage does not constitute the final offer to contract or an amendment of a=
 contract or acceptance of such offer.

--_000_1808340F7EC362469DDFFB112B37E2FCDA33129A66SRVHKE02rdmcz_
Content-Type: text/html; charset="iso-8859-2"
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=3Diso-8859-=
2">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Fixedsys;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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:10.0pt;
	font-family:"Fixedsys","serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Fixedsys","serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 121.0pt 70.85pt 121.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Dear Ben, all,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Many thanks for your review. An updated I-D has b=
een submitted.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please see inline.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt; <span lang=3D"EN-US">-----Original Message--=
---</span></p>
<p class=3D"MsoPlainText">&gt; <span lang=3D"EN-US">From: Ben Campbell [mai=
lto:ben@nostrum.com]</span></p>
<p class=3D"MsoPlainText">&gt; <span lang=3D"EN-US">Sent: Friday, March 21,=
 2014 8:25 PM</span></p>
<p class=3D"MsoPlainText">&gt; <span lang=3D"EN-US">To: draft-ietf-v6ops-64=
share.all@tools.ietf.org</span></p>
<p class=3D"MsoPlainText">&gt; <span lang=3D"EN-US">Cc: gen-art@ietf.org Te=
am (gen-art@ietf.org)</span></p>
<p class=3D"MsoPlainText">&gt; <span lang=3D"EN-US">Subject: Gen-ART LC/Tel=
echat Review of draft-ietf-v6ops-</span></p>
<p class=3D"MsoPlainText">&gt; <span lang=3D"EN-US">64share-09</span></p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; I am the assigned Gen-ART reviewer for this =
draft. For</p>
<p class=3D"MsoPlainText">&gt; background on Gen-ART, please see the FAQ at=
 &lt;</p>
<p class=3D"MsoPlainText">&gt; <a href=3D"http://wiki.tools.ietf.org/area/g=
en/trac/wiki/GenArtfaq">
<span style=3D"color:windowtext;text-decoration:none">http://wiki.tools.iet=
f.org/area/gen/trac/wiki/GenArtfaq</span></a>&gt;.</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; Please wait for direction from your document=
 shepherd or AD</p>
<p class=3D"MsoPlainText">&gt; before posting a new version of the draft.</=
p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; Document: draft-ietf-v6ops-64share-09</p>
<p class=3D"MsoPlainText">&gt; Reviewer: Ben Campbell</p>
<p class=3D"MsoPlainText">&gt; Review Date: 2014-03-21</p>
<p class=3D"MsoPlainText">&gt; IETF LC End Date: long time ago</p>
<p class=3D"MsoPlainText">&gt; IESG Telechat date: 2014-03-27</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; Note: I somehow missed this assignment at la=
st call time.</p>
<p class=3D"MsoPlainText">&gt; Therefore this review serves as both a last =
call and an IESG</p>
<p class=3D"MsoPlainText">&gt; telechat review.</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; Summary: This draft is mostly ready for publ=
ication as an</p>
<p class=3D"MsoPlainText">&gt; informational RFC. I have a few editorial co=
mments that might</p>
<p class=3D"MsoPlainText">&gt; be worth considering prior to publication.</=
p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; Major issues: None</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; Minor issues: None</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; Nits/editorial comments:</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; -- Section 1, paragraph 1:</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; Can you elaborate on what it means to &quot;=
extend&quot; The prefix to</p>
<p class=3D"MsoPlainText">&gt; a LAN link? Are we talking about routing IPv=
6 traffic from</p>
<p class=3D"MsoPlainText">&gt; other local devices (on the LAN) across the =
3gpp link, for</p>
<p class=3D"MsoPlainText">&gt; example, like one might do when tethering de=
vices to a phone</p>
<p class=3D"MsoPlainText">&gt; or mobile hotspot?</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Yes, this is the case.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt; Can you offer a reference for &quot;the 3GPP=
 specification&quot;?</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; Can you offer a reference for &quot;the 3GPP=
 specification&quot;?</p>
<p class=3D"MsoPlainText"><span style=3D"color:black"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Done.<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span style=3D"color:black"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText">&gt; -- paragraph 2: &quot;This can be achieved b=
y receiving the Router</p>
<p class=3D"MsoPlainText">&gt; Advertisement (RA) [RFC4861] announced globa=
lly unique /64</p>
<p class=3D"MsoPlainText">&gt; IPv6 prefix from the 3GPP radio interface an=
d then</p>
<p class=3D"MsoPlainText">&gt; advertising&quot;</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; What does these things. The UE?</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Yes, the UE. Ref to t=
he UE has been added.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText">&gt; Please expand RA on first mention.<s><o:p></=
o:p></s></p>
<p class=3D"MsoPlainText"><s><span style=3D"color:black"><o:p><span style=
=3D"text-decoration:none">&nbsp;</span></o:p></span></s></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Done.<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><s><span style=3D"color:black"><o:p><span style=
=3D"text-decoration:none">&nbsp;</span></o:p></span></s></p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; -- section 3, R-1:</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; Please expand SLAAC on first use.</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Done.<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span style=3D"color:black"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText">&gt; -- section 4.2, 1st paragraph: &quot;The 3GP=
P RA /64 prefix</p>
<p class=3D"MsoPlainText">&gt; information is used to configure NDP on the =
LAN and assigns</p>
<p class=3D"MsoPlainText">&gt; itself an address on the LAN link.&quot;</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; The prefix information assigns itself an add=
ress? I don't</p>
<p class=3D"MsoPlainText">&gt; think that's what you mean to say.</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Fixed, please review.=
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText">&gt; -- section 4.2, step 7:</p>
<p class=3D"MsoPlainText">&gt; </p>
<p class=3D"MsoPlainText">&gt; Please expand DAD on first use.</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Done.<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Cheers,<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Ales<o:p></o:p></span=
></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">Z=E1sady komunikace, kter=E9=
 spole=E8nost T-Mobile Czech Republic a.s. u=BE=EDv=E1 p=F8i sjedn=E1v=E1n=
=ED smluv, jsou uvedeny zde http://www.t-mobile.cz/zasady. Nen=ED-li v z=E1=
sad=E1ch uvedeno jinak, nep=F8edstavuje tato zpr=E1va kone=E8n=FD n=E1vrh n=
a
 uzav=F8en=ED =E8i zm=ECnu smlouvy ani p=F8ijet=ED takov=E9ho n=E1vrhu. The=
 communication principles which T-Mobile Czech Republic a.s. applies when n=
egotiating contracts are defined here http://www.t-mobile.cz/principles. Un=
less otherwise stated in the principles, this message
 does not constitute the final offer to contract or an amendment of a contr=
act or acceptance of such offer.<br>
</font>
</body>
</html>

--_000_1808340F7EC362469DDFFB112B37E2FCDA33129A66SRVHKE02rdmcz_--


From nobody Wed Apr  2 07:41:24 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 AD3181A0249 for <gen-art@ietfa.amsl.com>; Wed,  2 Apr 2014 07:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 5k9VzhZy0oGI for <gen-art@ietfa.amsl.com>; Wed,  2 Apr 2014 07:41:17 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id B34A81A0237 for <gen-art@ietf.org>; Wed,  2 Apr 2014 07:41:16 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: At8LANcgPFPGmAcV/2dsb2JhbABZgkIjITtXqkIMkCWBIR6HNYEeFnSCJwEBAxIbXgEVBw5WJgEEGxqHVwEMnU6EVqx3F4x8gUMggkYPZ4EUBIkei0yFH4VEi0KDMIIr
X-IronPort-AV: E=Sophos; i="4.97,780,1389762000"; d="scan'208,217"; a="48973098"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 02 Apr 2014 10:41:11 -0400
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; 02 Apr 2014 10:26:55 -0400
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.0174.001; Wed, 2 Apr 2014 16:41:09 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review for draft-ietf-idr-aigp-16
Thread-Index: Ac9OgZWPsNihasKtQmyyDhH0ojlp8g==
Date: Wed, 2 Apr 2014 14:41:08 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E46F20F@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_9904FB1B0159DA42B0B887B7FA8119CA2E46F20FAZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/btr3cS9uxSYOQKN8Nxibi7XK75c
Subject: [Gen-art] Gen-ART review for draft-ietf-idr-aigp-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: Wed, 02 Apr 2014 14:41:22 -0000

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

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



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



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



Document: draft-ietf-idr-aigp-16

Reviewer: Dan Romascanu

Review Date: 4/2/14

IETF LC End Date: 4/8/14

IESG Telechat date: (if known)



Summary:



Ready



Major issues:



None



Minor issues:



None



Nits/editorial comments:



In Section 3.4.1 in page 8:



=D8  The AIGP attribute may be added only to routes that satisfy one of the=
 following conditions:



It seems to me that in order to be consistent with similar statements in th=
e same section the 'may' here needs to be a capitalized RFC 2119 MAY


--_000_9904FB1B0159DA42B0B887B7FA8119CA2E46F20FAZFFEXMB04globa_
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=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:237252371;
	mso-list-type:hybrid;
	mso-list-template-ids:-255669840 -72564498 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
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: draft-ietf-idr-aigp-16<o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 4/2/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 4/8/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: (if known)<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"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Ready<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">None<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">None<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">In Section 3.4.1 in page 8: <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</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"font-family:Wingdings"><span style=3D"m=
so-list:Ignore">=D8<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span>The AIGP attribute =
may be added only to routes that satisfy one of the following conditions:
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">It seems to me that in order to be consistent wit=
h similar statements in the same section the &#8216;may&#8217; here needs t=
o be a capitalized RFC 2119 MAY
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E46F20FAZFFEXMB04globa_--


From nobody Thu Apr  3 03:48:41 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 821481A0221; Thu,  3 Apr 2014 03:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level: 
X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 WqO9BC2H-6pk; Thu,  3 Apr 2014 03:48:35 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB061A0232; Thu,  3 Apr 2014 03:48:29 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id l18so1657832wgh.7 for <multiple recipients>; Thu, 03 Apr 2014 03:48:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=yRyXLy+JPtECGEufnKiq9TViy2IaUAgS9WbWZPkaDQ4=; b=KFx8wz9wOrn3f1G9Jg33NOT809kEoPd5mUpauKdNODk6srHBObjjqAq7/aUS2urfks 6uhJE8v1mIMTvkNszPM4E9zeYOQxDi89OLThPUuhCi8DA+RNUoJAWlkIdhydwg0mhfFV 8uhWRlT5DGiMw6EzkITlehT0sTwni3PCnLT3+aRtKcOmTMRgdxVaEr1UTIR6pf2o2KWG SoLjdo+I3GgSRpG0+jg7w3ulQq7U0/w2Agoa+f0T9OLfoqWvA1pPqiZoVOEPDOdo9CI/ EGpbSiDLuCfFgdub2Qg/tRanLk33RTVvMchQW/2zd/abWIuOLjkszZbhnLM2CBHr896o SS3Q==
X-Received: by 10.180.7.198 with SMTP id l6mr628908wia.52.1396522105287; Thu, 03 Apr 2014 03:48:25 -0700 (PDT)
Received: from RoniE (bzq-79-183-174-212.red.bezeqint.net. [79.183.174.212]) by mx.google.com with ESMTPSA id s46sm11190997ees.3.2014.04.03.03.48.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 03 Apr 2014 03:48:23 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-mpls-lsp-ping-ttl-tlv.all@tools.ietf.org>
Date: Thu, 3 Apr 2014 13:48:18 +0300
Message-ID: <0a7d01cf4f2a$3b3cba10$b1b62e30$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0A7E_01CF4F43.608A8E50"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac9PKjjoTsJKpdiERKaL9DKHmOz8KQ==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/gFJv2qb3t8A8SGr9O8RutaQjtTU
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-mpls-lsp-ping-ttl-tlv-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, 03 Apr 2014 10:48:39 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0A7E_01CF4F43.608A8E50
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-lsp-ping-ttl-tlv-07

Reviewer: Roni Even

Review Date:2014-4-3

IETF LC End Date: 2014-4-7

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

In section 1 first paragraph "request packet to any another node" 

 


------=_NextPart_000_0A7E_01CF4F43.608A8E50
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><pre><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document:&n=
bsp; </span><span =
style=3D'font-size:10.5pt'>draft-ietf-mpls-lsp-ping-ttl-tlv-07</span><spa=
n style=3D'color:black'><o:p></o:p></span></pre><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;4-3<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;4-7<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as 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=3DMsoNormal>In section 1 first =
paragraph &#8220;request packet to any another node&#8221; =
<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0A7E_01CF4F43.608A8E50--


From nobody Thu Apr  3 08:14:16 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 883B71A0214 for <gen-art@ietfa.amsl.com>; Thu,  3 Apr 2014 08:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Level: 
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 ryt1WTPlhqM7 for <gen-art@ietfa.amsl.com>; Thu,  3 Apr 2014 08:14:04 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id DAD631A01EF for <gen-art@ietf.org>; Thu,  3 Apr 2014 08:14:03 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s33FDwsR027659; Thu, 3 Apr 2014 16:13:58 +0100
Received: from 950129200 (16.17.90.92.rev.sfr.net [92.90.17.16]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s33FDseS027644 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Apr 2014 16:13:55 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Roni Even'" <ron.even.tlv@gmail.com>, <draft-ietf-mpls-lsp-ping-ttl-tlv.all@tools.ietf.org>
References: <0a7d01cf4f2a$3b3cba10$b1b62e30$@gmail.com>
In-Reply-To: <0a7d01cf4f2a$3b3cba10$b1b62e30$@gmail.com>
Date: Thu, 3 Apr 2014 16:13:54 +0100
Message-ID: <07c101cf4f4f$55a26330$00e72990$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_07C2_01CF4F57.B7693C30"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLBk9M1z7VFQnUtsq7WEuWr8AVLk5kbdf7g
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20606.007
X-TM-AS-Result: No--24.257-10.0-31-10
X-imss-scan-details: No--24.257-10.0-31-10
X-TMASE-MatchedRID: vrenrrvn/xdDZFBd1jLr/uYAh37ZsBDC1kqyrcMalqX8bD+4PAZXi/b8 7PAFFIpFe1pE2Xvb5l9z3Lx1JAXQea/V8/cgjzjS+L2GsArAgtpA8JZETQujwrrfxlRjqBJ3OsK CHECCak3azok4GbDV8kSi4vfRCvHts9KysQDKV8FUXvI6K7iraRSRa9qpSosf1oQ9rh6i+Ubv/7 2zC4hJFZ3woJ2UeuYF6HMoliKXreiqDvek35mqXJ3bt4XlQMWj4L7b7oFFzFe13HaVceMXUiL8H aC6OsQfMHoR0KY0MZVVsQM/S7OiNfJMF6pylZNWXTK4OtPUfQSjuF41aTJRXZ/paSZmLhGje5ba sibx4KfyTo1GsSlyqhkigyII1PZ5MuPfXQm0MvCKC6Im4I1RF9Vj2MQh1a6nYB83633RxLcTSns KccEd+AI2jcyWmkkvVFcyUv+neW54gIWnbcyVjZhyXgGCpXKTuacNrbMY+LQ93acSBBsAmjApi0 hTr2bdDu0z6gr6YMqsL00KbDwQC4sxYRAg7qHw+KUzuemidPyQF91MxEBdRrXvDHySC+eUlSBIv H74wfJrar1QOTCmjzl5+IQAcYVk8lEDYmoBkrPbH8WaUL9qjB2CTNIhL2HPmCNknSXswf8SkGdm Qt+XWVIDtuOc/FONbnM/8VJDhM2jbvDx57hYL5cJk+S0k5+D/wlhIU/V2FXp50NNm9drSORqQAx bWD9+4vM1YF6AJbbqChA6lSRJvrQ/aqQZTRfK0C1sQRfQzEEj80Za3RRg8NPbhdvkrYl+zuAR4I VK1bxXFpGY1r5Epz9HnkKX+SdhPJuGM8tMGsU=
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/7JqLWliv7lbGz0LI-yPzurRRRHQ
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-lsp-ping-ttl-tlv-07
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: Thu, 03 Apr 2014 15:14:09 -0000

This is a multipart message in MIME format.

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

Thanks for your time, Roni.
 
Adrian
 
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Roni Even
Sent: 03 April 2014 11:48
To: draft-ietf-mpls-lsp-ping-ttl-tlv.all@tools.ietf.org
Cc: gen-art@ietf.org; ietf@ietf.org
Subject: Gen-ART LC review of draft-ietf-mpls-lsp-ping-ttl-tlv-07
 
I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART,
please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Please resolve these comments along with any other Last Call comments you may
receive.
Document:  draft-ietf-mpls-lsp-ping-ttl-tlv-07
Reviewer: Roni Even
Review Date:2014-4-3
IETF LC End Date: 2014-4-7
IESG Telechat date: 
 
Summary: This draft is ready for publication as Standard track RFC.
 
 
Major issues:
 
Minor issues:
 
 
Nits/editorial comments:
In section 1 first paragraph "request packet to any another node" 
 

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CF4F57.42B2B1F0"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-520092929 1073806591 9 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.5pt;
	font-family:Consolas;
	mso-fareast-font-family:Calibri;}
pre
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Calibri;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:Consolas;}
span.EmailStyle21
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New Roman";color:#1F497D'>Thanks for your time, =
Roni.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New =
Roman";color:#1F497D'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'mso-ascii-font-family:Calibri;mso-hansi-font-family:Calibri;mso-=
bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><b><=
span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> ietf =
[mailto:ietf-bounces@ietf.org] <b>On Behalf Of </b>Roni =
Even<br><b>Sent:</b> 03 April 2014 11:48<br><b>To:</b> =
draft-ietf-mpls-lsp-ping-ttl-tlv.all@tools.ietf.org<br><b>Cc:</b> =
gen-art@ietf.org; ietf@ietf.org<br><b>Subject:</b> Gen-ART LC review of =
draft-ietf-mpls-lsp-ping-ttl-tlv-07<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a><span =
style=3D'mso-bookmark:OLE_LINK2'><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>I am the assigned Gen-ART reviewer for =
this draft. For background on Gen-ART, please see the FAQ at =
&lt;</span></span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Please resolve these comments along =
with any other Last Call comments you may =
receive.<o:p></o:p></span></p><pre><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Document:&nbsp; </span><span lang=3DEN-US =
style=3D'font-size:10.5pt;mso-ansi-language:EN-US'>draft-ietf-mpls-lsp-pi=
ng-ttl-tlv-07</span><span lang=3DEN-US =
style=3D'color:black;mso-ansi-language:EN-US'><o:p></o:p></span></pre><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Reviewer: Roni Even<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Review Date:2014&#8211;4-3<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>IETF LC End Date: 2014&#8211;4-7<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>IESG Telechat date: <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Summary: This draft is ready for publication as Standard =
track RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Major issues:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'>Minor issues:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-ansi-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>Nits/editorial =
comments:<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>In section 1 first paragraph =
&#8220;request packet to any another node&#8221; =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p></div></div=
></body></html>
------=_NextPart_000_07C2_01CF4F57.B7693C30--


From nobody Thu Apr  3 14:44:14 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 49E871A02F9 for <gen-art@ietfa.amsl.com>; Thu,  3 Apr 2014 14:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 2gSDFmS2vY1r for <gen-art@ietfa.amsl.com>; Thu,  3 Apr 2014 14:44:06 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 260A51A01FD for <gen-art@ietf.org>; Thu,  3 Apr 2014 14:44:05 -0700 (PDT)
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 nostrum.com (8.14.8/8.14.7) with ESMTP id s33Li1IZ014997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Thu, 3 Apr 2014 16:44:01 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88] claimed to be A-Jean-Mahoneys-MacBook-Pro.local
Message-ID: <533DD620.20309@nostrum.com>
Date: Thu, 03 Apr 2014 16:44:00 -0500
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.4.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/zXb_1NQBTQHQxhQiBZ0OHavgyfg
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-04-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, 03 Apr 2014 21:44:12 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------

Scott Brim        2014-04-15   draft-ietf-ccamp-rsvp-te-eth-oam-ext-11



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 nobody Thu Apr  3 15:01:47 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 E2BB41A016C for <gen-art@ietfa.amsl.com>; Thu,  3 Apr 2014 15:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 t9FuL4VpMsZz for <gen-art@ietfa.amsl.com>; Thu,  3 Apr 2014 15:01:41 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F9F81A00D1 for <gen-art@ietf.org>; Thu,  3 Apr 2014 15:01:41 -0700 (PDT)
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 nostrum.com (8.14.8/8.14.7) with ESMTP id s33M1a8u016445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Thu, 3 Apr 2014 17:01:37 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88] claimed to be A-Jean-Mahoneys-MacBook-Pro.local
Message-ID: <533DDA40.6090909@nostrum.com>
Date: Thu, 03 Apr 2014 17:01:36 -0500
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.4.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/7u7okk2h_d7KuG8sHccrnUgutZo
Subject: [Gen-art] Assignments for the 2014-04-10 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, 03 Apr 2014 22:01:46 -0000

Hi all,

The following reviewers have assignments:

Reviewer            LC end       Draft
------------------------------------------------------------------------------------
Alexey Melnikov     2014-03-24   draft-ietf-cdni-framework-10 **

Christer Holmberg   2014-04-01   draft-ietf-pcp-dhcp-11 *

Meral Shirazipour   2014-03-28 draft-ietf-xrblock-rtcp-xr-loss-conceal-11 *

Russ Housley        2013-12-16   draft-ietf-opsec-vpn-leakages-04 *

* 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 nobody Thu Apr  3 15:48:07 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 939F11A0328 for <gen-art@ietfa.amsl.com>; Thu,  3 Apr 2014 15:48:06 -0700 (PDT)
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 Gqd9BNV4n2_3 for <gen-art@ietfa.amsl.com>; Thu,  3 Apr 2014 15:48:02 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 33AEF1A0335 for <gen-art@ietf.org>; Thu,  3 Apr 2014 15:48:02 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 29249F2C073; Thu,  3 Apr 2014 18:47:48 -0400 (EDT)
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 5B4EmBmVkbh8; Thu,  3 Apr 2014 18:47:26 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-241-160-129.washdc.fios.verizon.net [96.241.160.129]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 5FFC2F2C072; Thu,  3 Apr 2014 18:47:27 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <533DDA40.6090909@nostrum.com>
Date: Thu, 3 Apr 2014 18:47:15 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <18F45B50-1FDB-4E57-A1B6-2F7B9AF8DAD5@vigilsec.com>
References: <533DDA40.6090909@nostrum.com>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Z24mX0P2WbCDy0i7eZQYjwHK_0o
Cc: IETF Gen-ART <gen-art@ietf.org>
Subject: [Gen-art] draft-ietf-opsec-vpn-leakages
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, 03 Apr 2014 22:48:06 -0000

On Apr 3, 2014, at 6:01 PM, A. Jean Mahoney wrote:

> Russ Housley        2013-12-16   draft-ietf-opsec-vpn-leakages-04 *


I have reviewed two previous versions of this document.  I have included =
this note on both...

> Personal Observation:
>=20
> I do not find this document very helpful.  It can be summarized as:
>=20
>    If IPv6 is not supported in your VPN software, then disable IPv6
>    support in all network interfaces before you try to use it.
>=20
> I do not know why the OPSEC WG thinks that this message is worthy of
> an RFC.


I am not going to put any more time into this document.

Russ


From nobody Thu Apr  3 16:05:14 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 057991A035A for <gen-art@ietfa.amsl.com>; Thu,  3 Apr 2014 16:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, T_RP_MATCHES_RCVD=-0.01] 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 2my0N2B3xHno for <gen-art@ietfa.amsl.com>; Thu,  3 Apr 2014 16:05:07 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9254B1A0351 for <gen-art@ietf.org>; Thu,  3 Apr 2014 16:05:06 -0700 (PDT)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s33N50Sr021447 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Apr 2014 18:05:01 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-173-172-146-58.tx.res.rr.com [173.172.146.58] claimed to be [10.0.1.29]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ben Campbell <ben@nostrum.com>
Date: Thu, 3 Apr 2014 18:05:00 -0500
X-Mao-Original-Outgoing-Id: 418259100.541384-2c7f4bea6fc6f58fb565e9fa26312732
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F266BF4-52CD-4A28-8AF7-745956E6EBA1@nostrum.com>
To: draft-hoffman-xml2rfc.all@tools.ietf.org
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Wimr5NmEPMZ-GSStjyhKA_b1pTI
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART Early Review of draft-hoffman-xml2rfc-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, 03 Apr 2014 23:05: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 comments
you may receive.

Document: draft-hoffman-xml2rfc-04
Reviewer: Ben Campbell
Review Date:  2014-04-03
IETF LC End Date: Not in last call

Note: This is an early review, rather than the usual Gen-ART review at =
IETF last call. The Gen-ART processes do not precisely apply.

Summary: This draft is on the right track. I have a few comments and =
questions that may or may not be worth consideration.

*** Major Issues: ***

None

*** Minor issues: ***

-- General:

There are a few "to do" items left in the draft.  (Not surprising for an =
early review.)

-- Section 1, paragraph 2:

I find it confusing that we have two drafts in parallel, one for V2 that =
is obsoleted by this draft, and this draft for V3. With this draft =
copying much of V2 forward, which is authoritative?

-- 1.1, entry for <tident>

THANK YOU!!!! I think faking indented text using the <list> work around =
was one of the most annoying things about previous versions.

--2.2:

Can I have more than one of any given address sub-element? If so, how =
should it render?

-- 2.5.3:

If "height" ought to be avoided, should it be deprecated?

Also, what's the unit for height?

(Same questions apply to "width")

-- 2.5.5:

An example of how to use inlined graphics files might be helpful.

-- 2.5.6:

A generic "code" value might be useful. Otherwise, how do you expect =
these to be used? Syntax highlighting? I assume the processor should =
never actually try to interpret code based on the "type" attribute. (Are =
there security considerations there?)

-- 2.7:

It seems like <b> (and also <i>)  is just as much format dependent as =
things like <width>. Wouldn't something like <em> be more useful for =
this purpose, where you have an abstract concept of emphasis that can be =
rendered differently for different formats? This seems like a place =
where our use cases are different than those for HTML, where markup is =
usually rendered by browsers that have similar font display =
capabilities.

In particular, what happens to <b>text<.b> when rendered into ASCII =
text?

-- 2.9:

Why does the "cite" attribute have different requirements than, say, =
xref? In particular, why wouldn't I want to cite a reference in the =
current doc, rather than a URL?

-- 2.9.1:

How would one reference an auto generated anchor identifier? If it =
doesn't exist until processing time...?

-- 2.15.2

What is the format for Month? Must you write it out? Abbreviate? =
Number?)

-- 2.26

An example might be helpful

--2.33.2

Is it possible to continue numbering from a previous list?

-- 2.43.5

The text says that "iprExtract" is used to reference a specific =
section.... Can you elaborate on how? E.g. do you reference an anchor? =
Are you allowed to have more than one "as-is" section?

-- 2.44.2:

Why are numberless subsections disallowed? It's pretty common to see =
documents that have non-numbered sub-heads inside numbered sections.

-- 2.44.5:

The default for the TOC attribute is "default"? Does that mean the =
actual meaning of "default" is controlled elsewhere?

Also, is there a way to limit the depth for ToCs?

-- 2.45 (and subsections)

Should the seriesInfo "name" values match the table from 2.40?

-- 2.54:

Is it possible to select the symbol to be used for an unordered list?

-- 5, security considerations

I wonder if the possibility of executable content existing in an RFC or =
draft is worth mention here? For an extreme example, see RFC6716, =
Appendix A. But more realistically, 2.5.5 mentions the possibility of =
in-lined binary content, and 2.5.6 allows the identification of code in =
a way that a naive processor implementation might take as an invitation =
to interpret said code.

Also, does the need for a processor to potentially render binary content =
in general (in-lined or otherwise) expand the attack surface over that =
for previous versions of XML2RFC?


*** Nits/editorial comments: ***

-- 1, paragraph 3:

I find the paragraph a little confusing. Saying certain elements will =
not be used in text generation may be a bit overstated, in that the =
generation of metadata may well become part of the process of generating =
the final text. It might be more correct to say "may not affect the =
rendering of the final text".  (And in the case of the example of index =
generation, I see that the text of this draft has an imbedded index--so =
I assume the related elements _were_ used in generating the text.

-- 1.1:

Is the section on changes from V2 intended to remain in the final RFC? =
Often such sections are removed, but there is info in here (esp 1.1.1) =
that may be useful in the long run.

-- 1.1, bulleted list of changes:

I find the past tense a bit confusing. I assume that the list represents =
incremental differences from V2, but the past tense made me wonder if it =
was meant as ways that V2 is different than V3.  (I suspect the author =
thought in terms of "changes that were made as we wrote this text", but =
I think the reader will think in terms of "changes this text makes to =
V2".

-- List entry for "postalline"

I had to stare at "postalline" for a while before I realized it meant =
"postal line" and not some sort of material, perhaps made from recycled =
mail (poh- stah-LEEN ). The point being that I find combined words like =
this very hard to read without some sort of separator or mixed case. =
Please consider that when creating new elements with compound word =
names. (e.g. <postal-line> or <postalLine> are much easier to read, for =
me at least.)

-- 1.1, 2nd paragraph, "less importantly"

I suggest dropping the value judgement. (I would personally find the =
lack of offline operation more of an issue than a need to change my =
anchor names, but that's just me.)

-- 2.5.8:

Please expand CJK on first use.

-- 2.40, series value table:

The value for 3GPP is "TBD". Is there an expectation that the RFC will =
have something real there?

-- 2.48, Content Model:

It might be worth marking deprecated elements. Otherwise a reader may =
not follow the xref to discover a legal child element is deprecated.

-- 2.58:

It might be helpful to mention what happens if an <xref> is _not_ empty.


From nobody Fri Apr  4 00:43:29 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 D1A831A03AC for <gen-art@ietfa.amsl.com>; Fri,  4 Apr 2014 00:43:27 -0700 (PDT)
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 pgAeiA0SgMIR for <gen-art@ietfa.amsl.com>; Fri,  4 Apr 2014 00:43:23 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2721A0047 for <gen-art@ietf.org>; Fri,  4 Apr 2014 00:43:22 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f328e0000012ab-c2-533e6295af56
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 6D.56.04779.5926E335; Fri,  4 Apr 2014 09:43:17 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0174.001; Fri, 4 Apr 2014 09:43:17 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-pcp-dhcp-11
Thread-Index: Ac9P2XEBGaD96qoeRtipi1hdNJfDsw==
Date: Fri, 4 Apr 2014 07:43:16 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D2772AF@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.19]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D2772AFESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNLMWRmVeSWpSXmKPExsUyM+Jvje7UJLtgg75uM4tZ31+xWlx99ZnF gcljyZKfTB5fLn9mC2CK4rJJSc3JLEst0rdL4Mr4tGQxa8EevYpjrbvZGxhPanQxcnJICJhI vNtzhRXCFpO4cG89WxcjF4eQwGFGifauDewQzmJGiVmvnwJVcXCwCVhIdP/TBmkQEdCUmLvi LROIzSwQLjHn0WcwW1jAUOL+mQOsEDVmElP7T0PZehLXXvYyg9gsAioSv77/YAEZySvgK7F5 uTlImBHohu+n1kCNFJe49WQ+E8RtAhJL9pxnhrBFJV4+/gd1s6JE+9MGRoj6fIl5k7vAbF4B QYmTM5+wTGAUnoVk1CwkZbOQlEHEdSQW7P7EBmFrSyxb+JoZxj5z4DETsvgCRvZVjOy5iZk5 6eWGmxiBEXJwy2/dHYynzokcYpTmYFES5/3w1jlISCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dU A2PvtvIdCRMTDr2KUjmZeGenyipx2T+urX6mvitWyQa471Kb/2ZFnLKdxOG3/lfn/G1+vUs9 5fYprkknw/pWleYpvPpr4Lrvst/JBJaA/iNnpbctj01/seDmpyLmOcz3ni1fpB7VuzcwxzPU mPmcuDLPBJmJ9x+p10eZfix04TCziTgT3/XMd5USS3FGoqEWc1FxIgBJ4OoMXgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/6f26D7wOljdhKwNy2P8Tx4EbrvU
Cc: "draft-ietf-pcp-dhcp.all@tools.ietf.org" <draft-ietf-pcp-dhcp.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-pcp-dhcp-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, 04 Apr 2014 07:43:28 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D2772AFESESSMB209erics_
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-pcp-dhcp-11.txt

Reviewer:                               Christer Holmberg

Review Date:                          4 April 2014

IETF LC End Date:                1 April 2014

IESG Telechat date:               10 April 2014



Summary:                               My review comments on a previous ver=
sion (-09) of the document have been addressed, and the document is now rea=
dy for publication.

Major issues: -

Minor issues: -

Nits/editorial comments: -



Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D2772AFESESSMB209erics_
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:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	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:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Times New Roman","serif";
	mso-fareast-language:EN-GB;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<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;
<span lang=3D"EN-GB"><a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wi=
ki/GenArtfaq"><span lang=3D"EN-US">http://wiki.tools.ietf.org/area/gen/trac=
/wiki/GenArtfaq</span></a></span>&gt;.<span lang=3D"EN-GB"><o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText">Please wait for direction from your document shep=
herd or AD before posting a new version of the draft.<span lang=3D"EN-GB"><=
o:p></o:p></span></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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-pcp-dhcp-=
11.txt<span lang=3D"EN-GB"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">Reviewer:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Christer Holmb=
erg<span lang=3D"EN-GB"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">Review Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4 April 2014<span lang=3D"EN-GB"><o:=
p></o:p></span></p>
<p class=3D"MsoPlainText">IETF LC End Date:&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 April 2014<span lan=
g=3D"EN-GB"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">IESG Telechat date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10 April 2014<span l=
ang=3D"EN-GB"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">&nbsp;<span lang=3D"EN-GB"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">Summary:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; My review comme=
nts on a previous version (-09) of the document have been addressed, and th=
e document is now ready for publication.<o:p></o:p></p>
<p class=3D"MsoPlainText">Major issues: -<span lang=3D"EN-GB"><o:p></o:p></=
span></p>
<p class=3D"MsoPlainText">Minor issues: -<o:p></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">Christer&nbsp;<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D2772AFESESSMB209erics_--


From nobody Fri Apr  4 10:44:14 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 990111A0372 for <gen-art@ietfa.amsl.com>; Fri,  4 Apr 2014 10:44:13 -0700 (PDT)
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 nwmFgeDGt_Rb for <gen-art@ietfa.amsl.com>; Fri,  4 Apr 2014 10:44:09 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 20A841A02A6 for <gen-art@ietf.org>; Fri,  4 Apr 2014 10:43:47 -0700 (PDT)
X-AuditID: c6180641-b7f768e000001855-64-533eec66931a
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id C4.66.06229.66CEE335; Fri,  4 Apr 2014 19:31:19 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0174.001; Fri, 4 Apr 2014 13:43:42 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-xrblock-rtcp-xr-loss-conceal.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-loss-conceal.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-xrblock-rtcp-xr-loss-conceal-11
Thread-Index: Ac9QLVdGuhOT5y+ITlONceJOKltGPA==
Date: Fri, 4 Apr 2014 17:43:40 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A32DDA29A@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.9]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A32DDA29Aeusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUyuXRPiG76G7tgg/7NAhY77q9mtbj66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJVx8eZN9oJ58hVH/r1nbWB8KN3FyMkhIWAi cW7bIyYIW0ziwr31bF2MXBxCAkcZJdb3P2CHcJYxSvy8tZQVpIpNwEJi++/nYLaIwApGiWlT KkFsYYFQidn/29gg4lESRw79Y4Kw9SS+nOxhB7FZBFQkVu/ZBhbnFfCV2HjnKTOIzQi0+fup NWBxZgFxiVtP5kNdJCCxZM95ZghbVOLl43+sELaixL7+6ewQ9fkSB459hZopKHFy5hOWCYxC s5CMmoWkbBaSMoi4jsSC3Z/YIGxtiWULXzPD2GcOPGZCFl/AyL6KkaO0OLUsN93IcBMjMB6O SbA57mBc8MnyEKM0B4uSOO+Xt85BQgLpiSWp2ampBalF8UWlOanFhxiZODilGhjnOU+ZyLJa YVa+VLPB82s/F60sFMt5qvzLui1yVUN+e2R9PUtmcOpnvq6OhqfPO9pErrUv1r9R8/fbx7Av hZKHI6Q+HAibzSd3e1Wubt0Dq9vNvcILVl1NerJt+rkQW8PjbKnLp0zO0M+S7zhuN/X0/fNb N9R17vfZVOl3jPXVVzcR7kUnLtUrsRRnJBpqMRcVJwIAVDqPLlUCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/1rzUlbn5UWndCNwdKTbEiV17Y4c
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-xrblock-rtcp-xr-loss-conceal-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, 04 Apr 2014 17:44:13 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32DDA29Aeusaamb107erics_
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-xrblock-rtcp-xr-loss-conceal-11
Reviewer: Meral Shirazipour
Review Date: 2014-04-04
IETF LC End Date: 2013-03-28
IESG Telechat date: 2014-04-10

Summary: This draft is ready to be published as Standards Track RFC.



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

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32DDA29Aeusaamb107erics_
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; http://wiki.tools.ietf=
.org/area/gen/trac/wiki/GenArtfaq&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-xrblock-rtcp-xr-loss-conceal-11=
<o:p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2014-04-04<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2013-03-28<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2014-04-10<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready to be published as Stan=
dards 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_ABCAA4EF18F17B4FB619EA93DEF7939A32DDA29Aeusaamb107erics_--


From nobody Fri Apr  4 11:12:44 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 B7A051A0545 for <gen-art@ietfa.amsl.com>; Fri,  4 Apr 2014 11:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.9
X-Spam-Level: 
X-Spam-Status: No, score=-100.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_SUMOF=1, USER_IN_WHITELIST=-100] 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 hXGC5vhNtCDD for <gen-art@ietfa.amsl.com>; Fri,  4 Apr 2014 11:12:37 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 36BEB1A0443 for <gen-art@ietf.org>; Fri,  4 Apr 2014 11:12:03 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1WW8ao-0003sC-Ls; Fri, 04 Apr 2014 19:11:54 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Fri, 04 Apr 2014 19:11:48 +0100
Message-Id: <1396635108.15324.14192.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/7TBqtvkZqLKMCrF8mtPd1It9d9E
Cc: draft-ietf-mpls-psc-updates.all@tools.ietf.org
Subject: [Gen-art] Gen-art telechat review of draft-ietf-mpls-psc-updates-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: Fri, 04 Apr 2014 18:12: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-ietf-mpls-psc-updates-03.txt
Reviewer: Elwyn Davies
Review Date: 4 April 2014
IETF LC End Date: 2014-04-09
IESG Telechat date: (if known) -

Summary:
Almost ready.  

Major Issues:

Minor Issues:
General: 
As discussed during 
Last Call/IETF review of draft-ietf-mpls-tp-psc-itu, RFC 6378 is missing
some details regarding 
- the on-the-wire format of messages
- detection of and behaviour in the event of reception of malformed
messages 
- behaviour in the event of receiving unknown TLV items
- behaviour in the event or receiving unexpected TLV items in a
particular mode.

Specifics:
On-the-wire format: 
- The encoding of the TLV Length field is not specified (unsigned binary
integer in network bit order).
- The encoding of the individual TLV length and Type fields in s2 should
also be specified (unsigned binary integer in network bit order). 
- The value of TLV Length should be more precisely specified.  Suggest:
  The TLV Length is the sum of the lengths of all TLVs in the message, 
  where the length of a TLV is the sum of the lengths of the three
  TLV fields, i.e., the the length of the value field + 4.

Malformed messages check:
- Check values of fields prior to TLV Length are consistent with s4.2 of
RFC 6378.
- Check overall length of message matches value in TLV Length + 12.
- Check Sum of lengths of TLVs matches value in TLV Length. 
- Check all TLV types received are recognized.

Behaviour in the event of receiving a malformed message:
- There has been discussion of appropriate behaviour on the MPLS mailing
list.

Behaviour in the event of receiving a well-formed but inappropriate TLV
in a message:
- This needs to be specified. (might be mode specific)

Nits/Editorial Comments:
General: s/i.e. /i.e., /g, s/e.g. /e.g., /g

Abstract/s1: Make the count of changes consistent (four/five currently).
Might be better just to say 'a number of changes' and leave the reader
to count.

s1: Since the number of items has grown to five and maybe six (depending
on how the above changes are inserted), it would helpful to link the
categorization to the actual section numbers.)

s2: It would be good to have the conventional picture here - just grab
the one from draft-mpls-tp-psc-itu.

s2, Value field: Better to say that this has the number of octets
specified in the length field rather than talking about multiples of 4
again.  The discussion of padding seems superfluous.

s4, next to last para: Should 'A remote No Request message SHALL be ignored' be
'A remote NR message SHALL be ignored' for consistency?

s5,para 8: s/In both cases the request which was driving/In both cases the request that was driving/

s6: It might be worth pointing out that extensions of PSC (like tp-psc-itu) may 
introcuce additional capabilities and state that it is up to these sepcifications to 
say how capability mismatch in this areas is/are handled.

  




From nobody Fri Apr  4 11:58:25 2014
Return-Path: <elwynd@folly.org.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 CEDE51A045A for <gen-art@ietfa.amsl.com>; Fri,  4 Apr 2014 11:58:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.9
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_SUMOF=1] 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 2mWiD0CLIQ62 for <gen-art@ietfa.amsl.com>; Fri,  4 Apr 2014 11:58:19 -0700 (PDT)
Received: from a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id A09671A01FC for <gen-art@ietf.org>; Fri,  4 Apr 2014 11:58:19 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtp (Exim 4.77) (envelope-from <elwynd@folly.org.uk>) id 1WW9JV-0005DT-Ic; Fri, 04 Apr 2014 19:58:08 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Organization: Folly Consulting
Date: Fri, 04 Apr 2014 19:58:04 +0100
Message-Id: <1396637884.15324.14300.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/DYWIhFfs1DtLfZqN049c43kYL1U
Cc: draft-ietf-mpls-psc-updates.all@tools.ietf.org
Subject: [Gen-art] Gen-art last call review of draft-ietf-mpls-psc-updates-03.txt (review type corrected).
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, 04 Apr 2014 18:58:24 -0000

(Sorry...  got the wrong review type in the subject line).

I am the assigned Gen-ART 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-psc-updates-03.txt
Reviewer: Elwyn Davies
Review Date: 4 April 2014
IETF LC End Date: 2014-04-09
IESG Telechat date: (if known) -

Summary:
Almost ready.  

Major Issues:

Minor Issues:
General: 
As discussed during 
Last Call/IETF review of draft-ietf-mpls-tp-psc-itu, RFC 6378 is missing
some details regarding 
- the on-the-wire format of messages
- detection of and behaviour in the event of reception of malformed
messages 
- behaviour in the event of receiving unknown TLV items
- behaviour in the event or receiving unexpected TLV items in a
particular mode.

Specifics:
On-the-wire format: 
- The encoding of the TLV Length field is not specified (unsigned binary
integer in network bit order).
- The encoding of the individual TLV length and Type fields in s2 should
also be specified (unsigned binary integer in network bit order). 
- The value of TLV Length should be more precisely specified.  Suggest:
  The TLV Length is the sum of the lengths of all TLVs in the message, 
  where the length of a TLV is the sum of the lengths of the three
  TLV fields, i.e., the the length of the value field + 4.

Malformed messages check:
- Check values of fields prior to TLV Length are consistent with s4.2 of
RFC 6378.
- Check overall length of message matches value in TLV Length + 12.
- Check Sum of lengths of TLVs matches value in TLV Length. 
- Check all TLV types received are recognized.

Behaviour in the event of receiving a malformed message:
- There has been discussion of appropriate behaviour on the MPLS mailing
list.

Behaviour in the event of receiving a well-formed but inappropriate TLV
in a message:
- This needs to be specified. (might be mode specific)

Nits/Editorial Comments:
General: s/i.e. /i.e., /g, s/e.g. /e.g., /g

Abstract/s1: Make the count of changes consistent (four/five currently).
Might be better just to say 'a number of changes' and leave the reader
to count.

s1: Since the number of items has grown to five and maybe six (depending
on how the above changes are inserted), it would helpful to link the
categorization to the actual section numbers.)

s2: It would be good to have the conventional picture here - just grab
the one from draft-mpls-tp-psc-itu.

s2, Value field: Better to say that this has the number of octets
specified in the length field rather than talking about multiples of 4
again.  The discussion of padding seems superfluous.

s4, next to last para: Should 'A remote No Request message SHALL be ignored' be
'A remote NR message SHALL be ignored' for consistency?

s5,para 8: s/In both cases the request which was driving/In both cases the request that was driving/

s6: It might be worth pointing out that extensions of PSC (like tp-psc-itu) may 
introcuce additional capabilities and state that it is up to these sepcifications to 
say how capability mismatch in this areas is/are handled.

  



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


From nobody Sat Apr  5 08:23:16 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 4DC5E1A01A5; Sat,  5 Apr 2014 08:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.95
X-Spam-Level: 
X-Spam-Status: No, score=0.95 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 L2-GRALffltp; Sat,  5 Apr 2014 08:23:10 -0700 (PDT)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 4F1121A018C; Sat,  5 Apr 2014 08:23:10 -0700 (PDT)
Received: by mail-oa0-f43.google.com with SMTP id eb12so4895464oac.30 for <multiple recipients>; Sat, 05 Apr 2014 08:23:05 -0700 (PDT)
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=dGXDd8s7r2BciJ/PKBcXMBZKHvmrP6VKqil5pkwRzpU=; b=KNlB8+RyS7nB3djXTTq8duOFR+3EqLebQBpuPzTB+R/MUlRX8OckelW91z8/pVDRJW CCdylmxPEN2kAbbgzwKmfwS29Dr9RYfik38fk9dTj+M4k7TzK/aMhHdty2AXKPrKkEhG 6zOxXwDNsTYZxTZE8hPqbVKrneIxdAvsI+GxjKrNP3JWPavzPHQN+KSUJKJzLogrZuC/ Y71cZ9fbsQRzLfcu6gyqIgWwvt0QXK5KjsxG/F+1d5xYfcYfvCYiNdxr35azSud+L+cs azQlE2gcStWr3OCWNxXsEumz1UEwZ2twFxeF4LyOIDKoZnjkdYwYW/tTAncrjF4jFM79 tEUw==
X-Received: by 10.182.44.232 with SMTP id h8mr64072obm.73.1396711385266; Sat, 05 Apr 2014 08:23:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.25.41 with HTTP; Sat, 5 Apr 2014 08:22:45 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C0ADDF7@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C0ADDF7@MX15A.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sat, 5 Apr 2014 11:22:45 -0400
Message-ID: <CAF4+nEEL1LUxBEaGyUxEHNWb=fMgu2zVAuHqiSf64d0ZW=w3ng@mail.gmail.com>
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/h3FFjxvB6PMR8oZVKJl46kEC_HQ
Cc: "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ostokes@extremenetworks.com" <ostokes@extremenetworks.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-esadi-06.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, 05 Apr 2014 15:23:14 -0000

Hi David,

Thanks for this very thorough review. See my responses below:

On Sat, Mar 29, 2014 at 10:23 PM, Black, David <david.black@emc.com> wrote:
>
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-trill-esadi-06.txt
> Reviewer: David L. Black
> Review Date: March 29, 2014
> IETF LC End Date: April 1, 2014
>
> Summary: This draft is on the right track, but has open issues
> described in the review.
>
> This draft revises the ESADI specification for TRILL from its
> original form in RFC 6325.
>
> Major issues:
>
> The draft changes ESADI in a non-backwards-compatible fashion from
> its original specification in RFC 6325, but does not explain why this
> is ok.  That explanation needs to be provided, and if implementations
> of ESADI as originally specified in RFC 6325 exist, that explanation
> needs to encompass coexistence and interoperability (or lack thereof)
> with such implementations.  That explanation probably belongs in
> Section 1.1, and could be expanded upon in Appendix A.

This was a considered decision of the TRILL WG. At least since the -02
version in February 2013, the ESADI WG draft has had ESADI-LSP
provisions that were incompatible with RFC 6325 ESADI for the purpose
of accomodating orders of magnitude more LSP fragments. This text in
the draft, which originally used a somewhat ad hoc change from IS-IS
LSPs to accomodate additional fragments, was posted to the list
without objection before being incorporated. Since a standard IS-IS
way of doing this was later in process in the ISIS WG, the ESADI draft
was changed to follow this more standard way of providing for more LSP
fragments and a new WG Last Call done in the TRILL WG specifically on
this issue. See

http://www.ietf.org/mail-archive/web/trill/current/msg06037.html
http://www.ietf.org/mail-archive/web/trill/current/msg06009.html

In Appendix A (Changes to [RFC6325]), how about replacing items 2 and
3 in the list as follows (includes fixing a typo in item 3):

OLD
   2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
      is changed from the base IS-IS format to the Extended Level 1
      Circuit Scoped format in [FS-LSP].
NEW
   2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
      is changed from the base IS-IS format to the Extended Level 1
      Circuit Scoped format (E-L1CS) specified in [FS-LSP]. This
      change is not backwards compatible with [RFC6325]. It is made in
      light of (a) the very limited, if any, deployment of [RFC6325]
      ESADI, and (b) the 256 times greater information carrying
      capacity of the E-L1CS format compared with the base IS-IS
      format. It is anticipated that this greater carrying capacity
      will be needed, under some circumstances, to carry end station
      addressing information or other information that is added to
      ESADI in the future.
OLD
   3. Unicasting of ESADI PDUs is supported including replacing Section
      4.6.2.2 of [RFC6325] with the next text give in Section 4.1 of
      this document.
NEW
   3. Unicasting of ESADI PDUs is optionally supported including
      replacing Section 4.6.2.2 of [RFC6325] with the new text give in
      Section 4.1 of this document. This unicast support is backwards
      compatible because it is only used when the recipient RBridge
      signals its support.

See possible replacement below for the first paragraph of Section 1.1
that includes a condensed version of this additional material
concerning backwards non-compatibility.

> Overall, this draft is not self-contained - to a significant extent,
> it is written as if it were effectively a long collection of errata
> to the ESADI specification in RFC 6325. That makes it difficult to
> understand - it would be better if this draft completely obsoleted
> and replaced the ESADI specification in RFC 6325, describing its
> changes, instead of providing specific text changes to portions of
> the RFC 6325 text.

All of the changes to ESADI are described in Appendix A.

If the ESADI related material in RFC 6325 was entirely contained in
one contiguous area of RFC 6325, it would have been easy to write this
draft as simply obsoleting and replacing that area of RFC 6325.  The
largest such monolithic block on ESADI in RFC 6325 is Section 4.2.5
(The TRILL ESADI Protocol), including its two subsections ("4.2.5.1
TRILL ESADI Participation" and "4.2.5.2 TRILL ESADI Information"). All
of that is obsoleted and replaced by this draft.  However, there are
other non-contiguous parts of RFC 6325 necessarily affected. For
example, Section 4.6 of RFC 6325 describes how to handle every
possible type of frame that might be received; since an ESADI PDU is
one such type of frame, it is necessary to change Section 4.6.2.2
("TRILL ESADI Frames") of RFC 6325.

There is really no substitute for having a general familiarity with
RFC 6325 in understanding this document. Although I have seen IESG
members criticize statements such as "Familiarity with X is assumed."
when X is a normative reference, on the grounds that familiarity with
all normative references is automatically assumed, perhaps some such
statement is warranted in this case.

In addressing both of your issues here, the first paragraph of Section
1.1 could be changed as follows:

OLD
   This document updates [RFC6325], the TRILL base specification,
   replacing the description of the ESADI protocol in Section 4.2.5 of
   [RFC6325], providing more detail, and prevailing over [RFC6325] where
   they conflict. The changes are summarized in Appendix A. These
   changes are not backwards compatible because, among other things,
   they change the format of ESADI-LSPs.
NEW
   This document updates [RFC6325], the TRILL base protocol
   specification, obsoleting and replacing the description of the
   ESADI protocol (Section 4.2.5 of [RFC6325] including all
   subsections), providing more detail on ESADI, updating other ESADI
   related sections of [RFC6325], and prevailing over [RFC6325] in any
   case where they conflict. For this reason, familiarity with
   [RFC6325] is particularly assumed.  These changes are not backwards
   compatible because they change the format of ESADI-LSPs to
   substantially increase the amount of information that can be
   carried. These changes are further discussed in Appendix A.


> Minor issues:
>
> I don't understand the discussion in section 2 of it being "an
> implementation decision how independent the multiple ESADI instances
> at an RBridge are" in light of the clear statement that "the ESADI
> update process operates separately for each ESADI instance."  The
> example given involves database structure considerations that are
> specific to the node implementation and do not affect the independent
> updates for each ESADI instance.  There may not be an actual
> technical problem here, but at least the first chunk of text quoted
> in this paragraph of the review needs to be rewritten.

Two things motivated the text you cite in Section 2: (1) ESADI uses
multiple instances of the flooding process for the purpose of limiting
the flooding to the TRILL switches that have expressed interest in a
particular Data Label. RFC 6822 specifies a different type of IS-IS
"instance" and there is some implication in 6822 of fault and
performance isolation between RFC 6822 instances. Although this
document says its instances are not the same as RFC 6822 instances,
someone might still have the impression that ESADI instances are
necessarily to be implemented inside a TRILL switch is a highly
isolated manner. This text is to emphasize that the extent to which
the execution of different ESADI instances are isolated within a TRILL
switch is an implementation decision. (2) Perhaps a symptom of item 1:
in early discussions of ESADI, there were multiple complaints that
maintaining 'so many different link state databases' in a TRILL switch
would be an undue burden. So the text here specifically mentions that
the databases for all ESADI instances at a TRILL switch can be merged
(with an appropriate marker in each record saying which instance it
belongs to).

While the IETF generally standardizes bits on the wire and not
internal implementation details, the above concerns lead to these few
sentences to dispel any false impression.  I do not really see how
there can be much confusion since the draft also says, as your point
out, "But the ESADI update process operates separately for each ESADI
instance and independently from the TRILL IS-IS update process.". I
suggest the following change:

OLD
   It is an implementation decision how independent the multiple ESADI
   instances at an RBridge are.
NEW
   This specification does not constrain how coupled or independent
   the multiple ESADI instances are in their implementation internal
   to an RBridge.


> Also in Section 2:
>
>    ESADI does no routing so there is no reason for pseudo-nodes in ESADI
>    and none are created.
>
> Need to explain what a pseudo-node is before this sentence.

I do not think this document is the right place for a detailed
explanation of pseudo-nodes. How about changing to the following:

   ESADI does no routing calculations so there is no reason for
   pseudo-nodes in ESADI and none are created (Pseudo-nodes [IS-IS]
   are a construct for optimizing routing calculations.)


> p.9, Figure 2 - explain how the receiver determines whether the inner
> Ethernet header contains a VLAN tag or FGL.  This also applies to Figure
> 3 on p.10.

I'm not sure this draft is the place for a detailed explanation but I
have no problem adding the already existing reference "[RFCfgl]" to
both figures right after where they say "VLAN or FGL Data Label (4 or
8 bytes)". That referenced document [RFCfgl], which is in the RFC
Editor's queue, explains this.


> p.10, Section 2.1:
>
>    All transit RBridges forward ESADI packets as if they were ordinary
>    TRILL Data packets.
>
> Need to explain what a "transit" RBridge is.  Between this and the
> above pseudo-node comment, I suggest adding an overview of the
> TRILL protocol to the start of Section 2.

How about just eliminating the word "transit", which I don't think is
necessary, and changing the sentence in question to

     All RBridges forward ESADI packets as if they were ordinary TRILL
     Data packets [RFC6325].


> p.11, Section 2.1:
>
>    No "routing" computation or routing decisions ever have to be
>    performed by ESADI.
>
> What is a ' "routing" computation' ??  This should be rephrased to
> contrast to what the non-ESADI TRILL usage of IS-IS does.

How about the following change:

OLD
   No "routing" computation or routing decisions ever have to be
   performed by ESADI.
NEW
   No "routing" calculation (least cost path or distribution tree
   construction) ever has to be performed by ESADI.


> p.12, Section 2.2:
>
>    If a VLAN or FGL ID
>    field within an ESADI-LSP PDU does include a value, that field's
>    contents is ignored.
>
> This looks like it's an important requirement, so:
>          "is ignored" -> "MUST be ignored"

OK.


> p.13, Section 3
>
>   "SNPA/MAC address"
>    is not considered in this tie breaking and there is no "Port ID".
>
> This is contrasting ESADI tie-breaking to a tie-breaking procedure
> that I'd guess is specified in another document; that needs to be
> explained, along with a reference to that document, preferably with
> the section number where the other tie-breaking procedure is
> specified.

The other document is [rfc6327bis] which is referenced.  However, this
reference can be made clearer. How about

OLD
   Generally speaking, the DRB election on the ESADI virtual link (see
   Section 2.1) operates similarly to a TRILL IS-IS broadcast link
   [rfc6327bis] with the following exceptions:
NEW
   Generally speaking, the DRB election on the ESADI virtual link (see
   Section 2.1) operates similarly to the DRB election on a TRILL
   IS-IS broadcast link, as described in Section 4.2.1 ("DRB Election
   Details") of [rfc6327bis], with the following exceptions:


> Section 6 - explain where the 1470 byte number in the third
> paragraph comes from.

How about adding the following at the end of the relevant paragraph,
just before the Section 6.1 header:

   (As stated in Section 4.3.1 of [RFC6325], 1470 bytes was chosen to
   make it extremely unlikely that a TRILL control packet, even with
   reasonable additional headers, tags, and/or encapsulation, would
   encounter MTU problems on an inter-RBridge link.)


> Section 8 - more should be said on whether/when the Authentication
> TLV should be used when ESADI conveys information from an
> authenticated registration. In particular, if this recommendation
> for usage of the Authentication TLV with information from an
> authenticated registration usage is not a "SHOULD" or "MUST", an
> explanation is in order.

Consider the following: we have a network with secure trunk links
between trusted TRILL switches but in some cases those switches are
connected to end stations via 802.11 Wi-Fi links. It seems entirely
reasonable to use 802.11 authentication in allowing end stations to
connect due to the inherent accessiblity of radio links, but might not
be necessary to use authentication on ESADI PDUs between TRILL
switches.

In any case, if there is a concern about forged packets, the IS-IS
LSPs in the TRILL campus should be authenticated and, in that case,
the ESADI PDUs will be authenticated by default as provided in Section
6.3 of this draft.

How about adding a new paragraph to Section 8, between the current
first and second paragraphs, incorporating the above, such as:

   However, there may be cases where it is not necessary to
   authenticate ESADI PDUs despite using authenticated registration
   for end stations.  For example a TRILL campus with secure RBridges
   and inter-RBridge links configured as trunks but some end stations
   connected via 802.11 wireless access links might use 802.11
   authentication for the connection of such end staions but not
   necessarily authenticate ESDAI PDUs. Note that if the IS-IS LSPs in
   a TRILL campus are authenticated, perhaps due to a concern about
   forged packets, the ESADI PDUs will be authenticated by default as
   provided in Section 6.3.


> Nits/editorial comments:
>
> There are lots of acronyms that are not expanded on first use,
> defined in the terminology section, or otherwise explained, e.g.,
> DRB, Sz, CSNP, PSNP. It may be ok to point to terminology/acronym
> definitions in RFC 6325.

I believe these are all defined/expanded in RFC 6325 but it would
still be a good idea to expand them on first use in this document.


> Last sentence on p.8:
>
> OLD
>    The outer VLAN tag will not be present if it was stripped by
>    an Ethernet port out of which the packet was sent.
> NEW
>    The outer VLAN tag will not be present for a packet on an
>    an Ethernet link that does not use VLAN tags.

Well, whether or not any particular Ethernet frame carrying a TRILL
Data packet is VLAN tagged or not depends on whether the port sending
that frame is configured to send it tagged or untagged. There is no
requirement or enforcement mechanism that all the ports on that
Ethernet link be identically configured in this regard. So I do not
consider it to be a property of the link.


Also, Appendix A item 1: replces -> replaces

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

> idnits 2.13.01 got confused by the Section 4.6.2.2 reference to
> RFC 6325 in Section 4.1, and thought 4.6.2.2 was an IPv4 address -
> this is not a problem.
>
> idnits also warned about possible pre-RFC5378 (2008) content.  This
> is probably not a problem, but please check with your AD.
>
> 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
> ----------------------------------------------------


From nobody Sat Apr  5 18:10:35 2014
Return-Path: <paul.hoffman@vpnc.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 74D911A027B for <gen-art@ietfa.amsl.com>; Sat,  5 Apr 2014 18:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.647
X-Spam-Level: 
X-Spam-Status: No, score=-0.647 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_INVITATION=-2, HELO_MISMATCH_COM=0.553] 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 vDuD61P8YAEN for <gen-art@ietfa.amsl.com>; Sat,  5 Apr 2014 18:10:28 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1BEF61A024B for <gen-art@ietf.org>; Sat,  5 Apr 2014 18:10:28 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-175.dsl.dynamic.sonic.net [50.1.98.175]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s361AJ9l056007 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 5 Apr 2014 18:10:21 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-175.dsl.dynamic.sonic.net [50.1.98.175] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <7F266BF4-52CD-4A28-8AF7-745956E6EBA1@nostrum.com>
Date: Sat, 5 Apr 2014 18:10:16 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CEB04259-BFD4-41D6-85D4-45C5EAFD7E6B@vpnc.org>
References: <7F266BF4-52CD-4A28-8AF7-745956E6EBA1@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/DAsDJ4Uz5C1sKC2M1cGiFa1M4Mg
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, draft-hoffman-xml2rfc.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Early Review of draft-hoffman-xml2rfc-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, 06 Apr 2014 01:10:33 -0000

Thanks for the review!

--Paul Hoffman

On Apr 3, 2014, at 4:05 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
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other comments
> you may receive.
>=20
> Document: draft-hoffman-xml2rfc-04
> Reviewer: Ben Campbell
> Review Date:  2014-04-03
> IETF LC End Date: Not in last call
>=20
> Note: This is an early review, rather than the usual Gen-ART review at =
IETF last call. The Gen-ART processes do not precisely apply.
>=20
> Summary: This draft is on the right track. I have a few comments and =
questions that may or may not be worth consideration.
>=20
> *** Major Issues: ***
>=20
> None

Yay!

> *** Minor issues: ***
>=20
> -- General:
>=20
> There are a few "to do" items left in the draft.  (Not surprising for =
an early review.)

Whacking away at them, yes.

> -- Section 1, paragraph 2:
>=20
> I find it confusing that we have two drafts in parallel, one for V2 =
that is obsoleted by this draft, and this draft for V3. With this draft =
copying much of V2 forward, which is authoritative?

Both. the v2 draft is authoritative for that version of the format =
(which is still in use); this draft will be definitive for v3 when v3 is =
implemented. Unlike a regular protocol, this format is not going to be =
immediately implemented when the draft goes to the RFC Editor.

> -- 1.1, entry for <tident>
>=20
> THANK YOU!!!! I think faking indented text using the <list> work =
around was one of the most annoying things about previous versions.

Hrm; I'm not used to seeing that in GenArt reviews. :-)

And, to be fair, lots of the new features have been suggested by many =
people on the RFC Editor's design team and in the bigger community.

> --2.2:
>=20
> Can I have more than one of any given address sub-element? If so, how =
should it render?

Yep; unclear. There are a lot of things in this draft (and the in the v2 =
draft) where the rendering is undefined. We may or may not clarify those =
in the doc before we are finished; if not, it will be up to the =
programmers.

> -- 2.5.3:
>=20
> If "height" ought to be avoided, should it be deprecated?

Yes; fixed.

> Also, what's the unit for height?

Deprecated. :-)

> (Same questions apply to "width")

Same answer. Also fixed.

> -- 2.5.5:
>=20
> An example of how to use inlined graphics files might be helpful.

Will do, once we have a more stable definition of what SVG will be =
allowed. (You just added another open "to do" item.)

> -- 2.5.6:
>=20
> A generic "code" value might be useful.

This would fall under "ascii-art".

> Otherwise, how do you expect these to be used? Syntax highlighting?

Probably not for the non-canonical versions, but some people will want =
to post-process the canonical XML to add syntax highlight, validation, =
and so on. The text above it says "A processor might add type-specific =
formatting to artwork with the preferred values in the non-canonical =
output formats."

> I assume the processor should never actually try to interpret code =
based on the "type" attribute. (Are there security considerations =
there?)

Correct, and yes. Added a security consideration about this.

> -- 2.7:
>=20
> It seems like <b> (and also <i>)  is just as much format dependent as =
things like <width>. Wouldn't something like <em> be more useful for =
this purpose, where you have an abstract concept of emphasis that can be =
rendered differently for different formats?

In some senses, yes, but given that we know the main expected types of =
non-canonical output (HTML, PDF, EPUB), they all handle bold and italic =
and fixed-width fonts just fine. There are plenty of people who would =
think that "emphasis" means bold, and plenty who would think it means =
"italic".

> This seems like a place where our use cases are different than those =
for HTML, where markup is usually rendered by browsers that have similar =
font display capabilities.

No, our use cases very much align with HTML here: that's a design =
choice.

> In particular, what happens to <b>text<.b> when rendered into ASCII =
text?

Nothing. Just like today, there is a lot of formatting that is lost in =
the text output.

> -- 2.9:
>=20
> Why does the "cite" attribute have different requirements than, say, =
xref? In particular, why wouldn't I want to cite a reference in the =
current doc, rather than a URL?

It can do both: the URL can be a fragment that points to a reference in =
the current doc.

> -- 2.9.1:
>=20
> How would one reference an auto generated anchor identifier? If it =
doesn't exist until processing time...?

Correct, so you can't. You can only use "target" attributes to named =
anchors.

> -- 2.15.2
>=20
> What is the format for Month? Must you write it out? Abbreviate? =
Number?)

Whoops, that one was unclear. Fixed. (Will require the English =
spelling.)

> -- 2.26
>=20
> An example might be helpful

Good call; fixed.

> --2.33.2
>=20
> Is it possible to continue numbering from a previous list?

Not directly.

> -- 2.43.5
>=20
> The text says that "iprExtract" is used to reference a specific =
section.... Can you elaborate on how? E.g. do you reference an anchor? =
Are you allowed to have more than one "as-is" section?

Good question, and one I don't know the answer to right now. Another =
to-do listed.

> -- 2.44.2:
>=20
> Why are numberless subsections disallowed?

If it was a sub-section, the heading could easily be mistaken for free =
text.

> It's pretty common to see documents that have non-numbered sub-heads =
inside numbered sections.

Those are probably "notes" and such, not real sections. Do you see a =
need for these? It's certainly possible to have them, but they seem more =
confusing than necessary to me.

> -- 2.44.5:
>=20
> The default for the TOC attribute is "default"? Does that mean the =
actual meaning of "default" is controlled elsewhere?
>=20
> Also, is there a way to limit the depth for ToCs?

Yes to both: they were added to <rfc> in the -05.

> -- 2.45 (and subsections)
>=20
> Should the seriesInfo "name" values match the table from 2.40?

That's a good question, and is in play right now.

> -- 2.54:
>=20
> Is it possible to select the symbol to be used for an unordered list?

Nope. That's a conscious design choice: the lists will look similar =
across RFCs.

> -- 5, security considerations
>=20
> I wonder if the possibility of executable content existing in an RFC =
or draft is worth mention here? For an extreme example, see RFC6716, =
Appendix A. But more realistically, 2.5.5 mentions the possibility of =
in-lined binary content, and 2.5.6 allows the identification of code in =
a way that a naive processor implementation might take as an invitation =
to interpret said code.

Yup, and (as above) I added a paragraph about this.

> Also, does the need for a processor to potentially render binary =
content in general (in-lined or otherwise) expand the attack surface =
over that for previous versions of XML2RFC?

Not in any way I can think of.

> *** Nits/editorial comments: ***
>=20
> -- 1, paragraph 3:
>=20
> I find the paragraph a little confusing. Saying certain elements will =
not be used in text generation may be a bit overstated, in that the =
generation of metadata may well become part of the process of generating =
the final text. It might be more correct to say "may not affect the =
rendering of the final text".  (And in the case of the example of index =
generation, I see that the text of this draft has an imbedded index--so =
I assume the related elements _were_ used in generating the text.

Fixed.

> -- 1.1:
>=20
> Is the section on changes from V2 intended to remain in the final RFC? =
Often such sections are removed, but there is info in here (esp 1.1.1) =
that may be useful in the long run.

Yes, it is intended to stay. It might move to an appendix, but it is =
important to list.

> -- 1.1, bulleted list of changes:
>=20
> I find the past tense a bit confusing. I assume that the list =
represents incremental differences from V2, but the past tense made me =
wonder if it was meant as ways that V2 is different than V3.  (I suspect =
the author thought in terms of "changes that were made as we wrote this =
text", but I think the reader will think in terms of "changes this text =
makes to V2".

Good call. Fixed.

> -- List entry for "postalline"
>=20
> I had to stare at "postalline" for a while before I realized it meant =
"postal line" and not some sort of material, perhaps made from recycled =
mail (poh- stah-LEEN ). The point being that I find combined words like =
this very hard to read without some sort of separator or mixed case. =
Please consider that when creating new elements with compound word =
names. (e.g. <postal-line> or <postalLine> are much easier to read, for =
me at least.)

The latter. Fixed.

> -- 1.1, 2nd paragraph, "less importantly"
>=20
> I suggest dropping the value judgement. (I would personally find the =
lack of offline operation more of an issue than a need to change my =
anchor names, but that's just me.)

Fixed.

> -- 2.5.8:
>=20
> Please expand CJK on first use.

Eeeps. Of course.

> -- 2.40, series value table:
>=20
> The value for 3GPP is "TBD". Is there an expectation that the RFC will =
have something real there?

Yes. More research is obviously needed.

> -- 2.48, Content Model:
>=20
> It might be worth marking deprecated elements. Otherwise a reader may =
not follow the xref to discover a legal child element is deprecated.

These are automatically generated, and marking the deprecated ones is =
probably really really hard. We thought of this and punted.

> -- 2.58:
>=20
> It might be helpful to mention what happens if an <xref> is _not_ =
empty.

Marked as another to-do.

Again: thanks! The things above marked as fixed or to-do will appear in =
the next draft.


From nobody Mon Apr  7 05:49:38 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 60E6C1A06FB for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 05:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.138
X-Spam-Level: *
X-Spam-Status: No, score=1.138 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 z6t6e5dA79nI for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 05:49:32 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 9C12F1A06EC for <gen-art@ietf.org>; Mon,  7 Apr 2014 05:49:32 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id s37CnPHK033272; Mon, 7 Apr 2014 14:49:25 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201404071249.s37CnPHK033272@givry.fdupont.fr>
From: Francis Dupont <dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 07 Apr 2014 14:49:25 +0200
Sender: Francis.Dupont@fdupont.fr
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/ZjSIiG1dHn0GL9xSISQddtsMyWE
Cc: draft-ietf-idr-last-as-reservation.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-idr-last-as-reservation-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: Mon, 07 Apr 2014 12:49:37 -0000

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

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

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

Document: draft-ietf-idr-last-as-reservation-04.txt
Reviewer: Francis Dupont
Review Date: 20140401
IETF LC End Date: 20130403
IESG Telechat date: unknown

Summary: Not Ready

Major issues: there is a typo in the IANA considerations, i.e., the
heart of the document. It seems to be a trivial typo but there is no
proof of this...

Minor issues: None

Nits/editorial comments:
 Appendix A page 4: Acknowledgements -> Acknowledgements

Regards

Francis.Dupont@fdupont.fr

PS: the typo looks like a bad cut & paste between versions 03 and 04.
If (/when?) this is confirmed by authors I'll change summary to Ready
and the typo from major issue to editorial.


From nobody Mon Apr  7 06:08:16 2014
Return-Path: <Jon.Mitchell@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 2F0CE1A0702 for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 06:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 XgsfaeE1h88H for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 06:07:53 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0209.outbound.protection.outlook.com [207.46.163.209]) by ietfa.amsl.com (Postfix) with ESMTP id 17E351A0715 for <gen-art@ietf.org>; Mon,  7 Apr 2014 06:07:53 -0700 (PDT)
Received: from BLUPR03MB166.namprd03.prod.outlook.com (10.255.212.142) by BLUPR03MB165.namprd03.prod.outlook.com (10.255.212.139) with Microsoft SMTP Server (TLS) id 15.0.908.10; Mon, 7 Apr 2014 13:07:46 +0000
Received: from BLUPR03MB166.namprd03.prod.outlook.com ([169.254.3.183]) by BLUPR03MB166.namprd03.prod.outlook.com ([169.254.3.183]) with mapi id 15.00.0913.002; Mon, 7 Apr 2014 13:07:46 +0000
From: "Jon Mitchell (GNS)" <Jon.Mitchell@microsoft.com>
To: Francis Dupont <dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: review of draft-ietf-idr-last-as-reservation-04.txt
Thread-Index: AQHPUl/shpjyKy18A0SP4XmuOxDRzpsGGz8w
Date: Mon, 7 Apr 2014 13:07:46 +0000
Message-ID: <5e18a7416c194ca3a6469252c34e1918@BLUPR03MB166.namprd03.prod.outlook.com>
References: <201404071249.s37CnPHK033272@givry.fdupont.fr>
In-Reply-To: <201404071249.s37CnPHK033272@givry.fdupont.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [206.165.221.10]
x-forefront-prvs: 0174BD4BDA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(428001)(164054003)(189002)(199002)(377454003)(13464003)(87936001)(76786001)(85306002)(76576001)(33646001)(76796001)(19580395003)(2656002)(74876001)(31966008)(94946001)(69226001)(79102001)(77096001)(19580405001)(87266001)(93136001)(53806001)(92566001)(74502001)(81686001)(81542001)(74662001)(56816005)(83072002)(4396001)(80022001)(80976001)(20776003)(98676001)(93516002)(77982001)(74706001)(50986001)(59766001)(47736001)(54316002)(56776001)(85852003)(65816001)(47446002)(76482001)(95666003)(46102001)(47976001)(74316001)(97186001)(97336001)(99396002)(90146001)(83322001)(66066001)(86362001)(74366001)(94316002)(63696002)(81816001)(54356001)(95416001)(49866001)(81342001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR03MB165; H:BLUPR03MB166.namprd03.prod.outlook.com; FPR:BCC0C01A.8EF20FC6.71C1374B.88D2CF5D.20291; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (: microsoft.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/LbAbpTuD98zBaqTnr1Q6CDECir8
Cc: "draft-ietf-idr-last-as-reservation.all@tools.ietf.org" <draft-ietf-idr-last-as-reservation.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-idr-last-as-reservation-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: Mon, 07 Apr 2014 13:08:04 -0000

Yes, this duplicate paragraph in IANA considerations is a typo introduced i=
n -04, can be removed via editing process to allow IESG review w/o update i=
f AD OK's that approach or draft updated to remove if that is preferred.  A=
lia?

I'm also willing to change to Acknowledgments (no e after g) which I think =
is the suggestion being made?

Thanks,

Jon


-----Original Message-----
From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr] On Behal=
f Of Francis Dupont
Sent: Monday, April 7, 2014 8:49 AM
To: gen-art@ietf.org
Cc: draft-ietf-idr-last-as-reservation.all@tools.ietf.org
Subject: review of draft-ietf-idr-last-as-reservation-04.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-ietf-idr-last-as-reservation-04.txt
Reviewer: Francis Dupont
Review Date: 20140401
IETF LC End Date: 20130403
IESG Telechat date: unknown

Summary: Not Ready

Major issues: there is a typo in the IANA considerations, i.e., the heart o=
f the document. It seems to be a trivial typo but there is no proof of this=
...

Minor issues: None

Nits/editorial comments:
 Appendix A page 4: Acknowledgements -> Acknowledgements

Regards

Francis.Dupont@fdupont.fr

PS: the typo looks like a bad cut & paste between versions 03 and 04.
If (/when?) this is confirmed by authors I'll change summary to Ready and t=
he typo from major issue to editorial.


From nobody Mon Apr  7 06:44:36 2014
Return-Path: <akatlas@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 D3A681A0418 for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 06:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[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 ZqMLqVYu12we for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 06:43:08 -0700 (PDT)
Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 4C8D91A0159 for <gen-art@ietf.org>; Mon,  7 Apr 2014 06:43:08 -0700 (PDT)
Received: by mail-yk0-f171.google.com with SMTP id q9so5494784ykb.16 for <gen-art@ietf.org>; Mon, 07 Apr 2014 06:43:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TQslHjwKLv9Qo8xBtq5AeMP63jMnkQxA6RK68WTVHcw=; b=V2N5YI8+7juxTGS8uyF9g4KbtYTMHXuF4kEhyypZwLEE4EYbvJ9Tsj7Er5NWS5XelP XLPtvlcpSxz+RYEIuzISWK0QzvJlJpWAGnm3a6wGQHRn1R5vIxLlnIG66EaBFcrNeaWy Nov9NJEViufwJx7fv28zBczLrq9f+akT6cqIEuoP365QL1UJt/cruCT0UiXiSlNHlF7p F2faZIooZMK1+mPz8HXTQzKuhrpBfrwj9ccfAevrYlBHIU8SAqglXmJE8+YlXp/OEpFV e/2UWbLVzTTiyCX2sAs1cOG9wgoUlsCTkrmQFverXtuUDTS6HWtcUMrDC9am/otL5DTO hTYQ==
MIME-Version: 1.0
X-Received: by 10.236.138.73 with SMTP id z49mr2276382yhi.152.1396878182644; Mon, 07 Apr 2014 06:43:02 -0700 (PDT)
Received: by 10.170.194.69 with HTTP; Mon, 7 Apr 2014 06:43:02 -0700 (PDT)
In-Reply-To: <5e18a7416c194ca3a6469252c34e1918@BLUPR03MB166.namprd03.prod.outlook.com>
References: <201404071249.s37CnPHK033272@givry.fdupont.fr> <5e18a7416c194ca3a6469252c34e1918@BLUPR03MB166.namprd03.prod.outlook.com>
Date: Mon, 7 Apr 2014 09:43:02 -0400
Message-ID: <CAG4d1rdzXD1jiZ3=GYjvhoOaUFcwBtN_5-3xxKybHRO3RHP5ng@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: "Jon Mitchell (GNS)" <Jon.Mitchell@microsoft.com>
Content-Type: multipart/alternative; boundary=20cf303ea634df01e204f6740ba4
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/B0kmJUUBQMiolyQ3H8EHCgqDcBQ
X-Mailman-Approved-At: Mon, 07 Apr 2014 06:44:33 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, Francis Dupont <dupont@fdupont.fr>, "draft-ietf-idr-last-as-reservation.all@tools.ietf.org" <draft-ietf-idr-last-as-reservation.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-idr-last-as-reservation-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: Mon, 07 Apr 2014 13:43:14 -0000

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

On Mon, Apr 7, 2014 at 9:07 AM, Jon Mitchell (GNS) <
Jon.Mitchell@microsoft.com> wrote:

>
> Yes, this duplicate paragraph in IANA considerations is a typo introduced
> in -04, can be removed via editing process to allow IESG review w/o update
> if AD OK's that approach or draft updated to remove if that is preferred.
>  Alia?
>

If it's not a big deal, I'd prefer a quick respin without the typo for the
IESG.  It'll just save time/comments later on.  The draft is probably for
the telechat on April 24, so there's a bit of time.

Alia

>
> I'm also willing to change to Acknowledgments (no e after g) which I think
> is the suggestion being made?
>
> Thanks,
>
> Jon
>
>
> -----Original Message-----
> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr] On
> Behalf Of Francis Dupont
> Sent: Monday, April 7, 2014 8:49 AM
> To: gen-art@ietf.org
> Cc: draft-ietf-idr-last-as-reservation.all@tools.ietf.org
> Subject: review of draft-ietf-idr-last-as-reservation-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-idr-last-as-reservation-04.txt
> Reviewer: Francis Dupont
> Review Date: 20140401
> IETF LC End Date: 20130403
> IESG Telechat date: unknown
>
> Summary: Not Ready
>
> Major issues: there is a typo in the IANA considerations, i.e., the heart
> of the document. It seems to be a trivial typo but there is no proof of
> this...
>
> Minor issues: None
>
> Nits/editorial comments:
>  Appendix A page 4: Acknowledgements -> Acknowledgements
>
> Regards
>
> Francis.Dupont@fdupont.fr
>
> PS: the typo looks like a bad cut & paste between versions 03 and 04.
> If (/when?) this is confirmed by authors I'll change summary to Ready and
> the typo from major issue to editorial.
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Apr 7, 2014 at 9:07 AM, Jon Mitchell (GNS) <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:Jon.Mitchell@microsoft.com" target=3D"_blank">Jon.Mitchell@micr=
osoft.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"><br>
Yes, this duplicate paragraph in IANA considerations is a typo introduced i=
n -04, can be removed via editing process to allow IESG review w/o update i=
f AD OK&#39;s that approach or draft updated to remove if that is preferred=
. =A0Alia?<br>
</blockquote><div><br></div><div>If it&#39;s not a big deal, I&#39;d prefer=
 a quick respin without the typo for the IESG. =A0It&#39;ll just save time/=
comments later on. =A0The draft is probably for the telechat on April 24, s=
o there&#39;s a bit of time.</div>
<div><br></div><div>Alia=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 also willing to change to Acknowledgments (no e after g) which I th=
ink is the suggestion being made?<br>
<br>
Thanks,<br>
<br>
Jon<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:Francis.Dupont@fdupont.fr">Francis.Dupont@fdupont.f=
r</a> [mailto:<a href=3D"mailto:Francis.Dupont@fdupont.fr">Francis.Dupont@f=
dupont.fr</a>] On Behalf Of Francis Dupont<br>
Sent: Monday, April 7, 2014 8:49 AM<br>
To: <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br>
Cc: <a href=3D"mailto:draft-ietf-idr-last-as-reservation.all@tools.ietf.org=
">draft-ietf-idr-last-as-reservation.all@tools.ietf.org</a><br>
Subject: review of draft-ietf-idr-last-as-reservation-04.txt<br>
<br>
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, 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 you m=
ay receive.<br>
<br>
Document: draft-ietf-idr-last-as-reservation-04.txt<br>
Reviewer: Francis Dupont<br>
Review Date: 20140401<br>
IETF LC End Date: 20130403<br>
IESG Telechat date: unknown<br>
<br>
Summary: Not Ready<br>
<br>
Major issues: there is a typo in the IANA considerations, i.e., the heart o=
f the document. It seems to be a trivial typo but there is no proof of this=
...<br>
<br>
Minor issues: None<br>
<br>
Nits/editorial comments:<br>
=A0Appendix A page 4: Acknowledgements -&gt; Acknowledgements<br>
<br>
Regards<br>
<br>
<a href=3D"mailto:Francis.Dupont@fdupont.fr">Francis.Dupont@fdupont.fr</a><=
br>
<br>
PS: the typo looks like a bad cut &amp; paste between versions 03 and 04.<b=
r>
If (/when?) this is confirmed by authors I&#39;ll change summary to Ready a=
nd the typo from major issue to editorial.<br>
</div></div></blockquote></div><br></div></div>

--20cf303ea634df01e204f6740ba4--


From nobody Mon Apr  7 07:28:07 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 F23091A045A for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 07:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.162
X-Spam-Level: 
X-Spam-Status: No, score=-0.162 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 0bmKCeTAFoCw for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 07:27:58 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 678171A072C for <gen-art@ietf.org>; Mon,  7 Apr 2014 07:27:58 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id s37ERqZj039500; Mon, 7 Apr 2014 16:27:52 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201404071427.s37ERqZj039500@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Jon Mitchell (GNS)" <Jon.Mitchell@microsoft.com>
In-reply-to: Your message of Mon, 07 Apr 2014 13:07:46 -0000. <5e18a7416c194ca3a6469252c34e1918@BLUPR03MB166.namprd03.prod.outlook.com> 
Date: Mon, 07 Apr 2014 16:27:52 +0200
Sender: Francis.Dupont@fdupont.fr
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/uhMlc3C7wnRcvL3sCXaZLI5WGwk
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, Francis Dupont <dupont@fdupont.fr>, "draft-ietf-idr-last-as-reservation.all@tools.ietf.org" <draft-ietf-idr-last-as-reservation.all@tools.ietf.org>
Subject: Re: [Gen-art] review of draft-ietf-idr-last-as-reservation-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: Mon, 07 Apr 2014 14:28:04 -0000

 In your previous mail you wrote:

>  Yes, this duplicate paragraph in IANA considerations is a typo introduced

=> fine (the problem with a typo is authors' intent is not clear / hard
to infer).

>  I'm also willing to change to Acknowledgments (no e after g) which I think
>  is the suggestion being made?

=> yes, it is US English so without the 'e'.

Thanks

Francis.Dupont@fdupont.fr

PS: I'll move to Ready so the I-D should go further (e.g., IANA review).


From nobody Mon Apr  7 11:37:42 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 9C6421A0846 for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 11:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, GB_I_INVITATION=-2, T_RP_MATCHES_RCVD=-0.01] 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 zR6nm5NCH_wl for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 11:37:31 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id A1A091A084B for <gen-art@ietf.org>; Mon,  7 Apr 2014 11:37:12 -0700 (PDT)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s37Ib3nt067790 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Apr 2014 13:37:05 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-173-172-146-58.tx.res.rr.com [173.172.146.58] claimed to be [10.0.1.29]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <CEB04259-BFD4-41D6-85D4-45C5EAFD7E6B@vpnc.org>
Date: Mon, 7 Apr 2014 13:37:03 -0500
X-Mao-Original-Outgoing-Id: 418588623.644463-4a32c0f3e700dda81f97ca669c02882f
Content-Transfer-Encoding: quoted-printable
Message-Id: <4368F77F-B2DD-4990-AE97-F24BBE5FEB64@nostrum.com>
References: <7F266BF4-52CD-4A28-8AF7-745956E6EBA1@nostrum.com> <CEB04259-BFD4-41D6-85D4-45C5EAFD7E6B@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/yxWQu9b-bzCamI00icnxHxJLtTw
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, draft-hoffman-xml2rfc.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Early Review of draft-hoffman-xml2rfc-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, 07 Apr 2014 18:37:38 -0000

Hi, thanks for the quick response. Comments inline; sections that do not =
seem to need further comment are deleted, and marked with "[...]"

Thanks!

Ben.

On Apr 5, 2014, at 8:10 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

[...]

>=20
>> -- Section 1, paragraph 2:
>>=20
>> I find it confusing that we have two drafts in parallel, one for V2 =
that is obsoleted by this draft, and this draft for V3. With this draft =
copying much of V2 forward, which is authoritative?
>=20
> Both. the v2 draft is authoritative for that version of the format =
(which is still in use); this draft will be definitive for v3 when v3 is =
implemented. Unlike a regular protocol, this format is not going to be =
immediately implemented when the draft goes to the RFC Editor.

It's not clear to me that updates to "regular protocols" always get =
immediately implemented, at least not to the point of immediately =
replacing older version.  Especially we we are talking about formally =
incrementing version numbers.

I think my real question is whether V3 really obsoletes V2 in the usual =
sense. Do we allow further updates (e.g. an "updates" draft with bug =
fixes) to V2 once it becomes an RFC? If so, do those updates, assuming =
they impact "common" parts, affect V3? Would that be automatic, or would =
V3 require a parallel update? Do we intend to allow V2 to evolve =
independently of V3?

>=20
>> -- 1.1, entry for <tident>
>>=20
>> THANK YOU!!!! I think faking indented text using the <list> work =
around was one of the most annoying things about previous versions.
>=20
> Hrm; I'm not used to seeing that in GenArt reviews. :-)
>=20
> And, to be fair, lots of the new features have been suggested by many =
people on the RFC Editor's design team and in the bigger community.

Okay, change that to THANK Y'ALL!!!!

>=20
>> --2.2:
>>=20
>> Can I have more than one of any given address sub-element? If so, how =
should it render?
>=20
> Yep; unclear. There are a lot of things in this draft (and the in the =
v2 draft) where the rendering is undefined. We may or may not clarify =
those in the doc before we are finished; if not, it will be up to the =
programmers.

I accept that different rendering decisions might be okay. But would you =
also leave whether a specific sub-element can be repeated to the =
implementors? Seem like that could lead to xml2rfc "code" that is =
correct for one processor but incorrect for another.

[...]

>=20
>> -- 2.7:
>>=20
>> It seems like <b> (and also <i>)  is just as much format dependent as =
things like <width>. Wouldn't something like <em> be more useful for =
this purpose, where you have an abstract concept of emphasis that can be =
rendered differently for different formats?
>=20
> In some senses, yes, but given that we know the main expected types of =
non-canonical output (HTML, PDF, EPUB), they all handle bold and italic =
and fixed-width fonts just fine. There are plenty of people who would =
think that "emphasis" means bold, and plenty who would think it means =
"italic".
>=20
>> This seems like a place where our use cases are different than those =
for HTML, where markup is usually rendered by browsers that have similar =
font display capabilities.
>=20
> No, our use cases very much align with HTML here: that's a design =
choice.

Well, HTML _does_ have <em>. I realize it's not very useful in HTML, =
since you rarely render HTML to a format that can't do bold or italics. =
But to test the assertion, do you consider typesetting a common use case =
for HTML? Is it not one for xml2rfc?

>=20
>> In particular, what happens to <b>text<.b> when rendered into ASCII =
text?
>=20
> Nothing. Just like today, there is a lot of formatting that is lost in =
the text output.

There are some common conventions here; they just seemed to have fallen =
by the wayside. For example, a title of a long-format work gets =
italicized when that's supported, but underlined on an old fashioned =
typewriter. There are more modern simulations like _this_ and *this*. =20=


OTOH, I guess an ascii rendering processor could make those same choices =
for <i> and <b> as well as for <em>, so maybe I just countered my own =
argument. But from a typesetting perspective, abstractions like <em> =
allow one to separate the intent of the author ("I want this to be =
emphasized") from the intent of the editor/publisher.("This is how our =
'style' renders emphasis.")

>=20
>> -- 2.9:
>>=20
>> Why does the "cite" attribute have different requirements than, say, =
xref? In particular, why wouldn't I want to cite a reference in the =
current doc, rather than a URL?
>=20
> It can do both: the URL can be a fragment that points to a reference =
in the current doc.

How would you do that? Is there a way to construct a URL that points to =
an xml2rfc anchor?

>=20
>> -- 2.9.1:
>>=20
>> How would one reference an auto generated anchor identifier? If it =
doesn't exist until processing time...?
>=20
> Correct, so you can't. You can only use "target" attributes to named =
anchors.

If you can't reference an auto-generated anchor, why do you have them? =
What else do you do with anchors?

>=20
>> --2.33.2
>>=20
>> Is it possible to continue numbering from a previous list?
>=20
> Not directly.

I may be misreading it, but doesn't V2 support number continuation with =
the "counter" attribute of <list>? If so, is the intent to remove that =
capability?

[...]

>> -- 2.44.2:
>>=20
>> Why are numberless subsections disallowed?
>=20
> If it was a sub-section, the heading could easily be mistaken for free =
text.
>=20
>> It's pretty common to see documents that have non-numbered sub-heads =
inside numbered sections.
>=20
> Those are probably "notes" and such, not real sections. Do you see a =
need for these? It's certainly possible to have them, but they seem more =
confusing than necessary to me.

I've seen docs (not necessarily RFCs), that did something like this:

1. Heading
1.1 Subhead
1.1.1 Minor Subhead
(no number) Really Minor Subhead

I think the idea is to label deep sub-topics without the clutter of =
1.1.1.1. Is it _necessary_? Probably not. But that's the use case I =
immediately envisioned when I thought about the ability to suppress =
numbering.=20

[...]

>=20
>> -- 5, security considerations
>>=20
>> I wonder if the possibility of executable content existing in an RFC =
or draft is worth mention here? For an extreme example, see RFC6716, =
Appendix A. But more realistically, 2.5.5 mentions the possibility of =
in-lined binary content, and 2.5.6 allows the identification of code in =
a way that a naive processor implementation might take as an invitation =
to interpret said code.
>=20
> Yup, and (as above) I added a paragraph about this.
>=20
>> Also, does the need for a processor to potentially render binary =
content in general (in-lined or otherwise) expand the attack surface =
over that for previous versions of XML2RFC?
>=20
> Not in any way I can think of.

For example (just thinking "out loud"), if a processor could insert JPEG =
artwork, does it need to worry about buffer overflow attacks on the JPEG =
format, as well as attacks on the xml itself? If so, does it matter if =
the artwork was in-lined vs referenced?=20

[...]

>=20
>> -- 2.48, Content Model:
>>=20
>> It might be worth marking deprecated elements. Otherwise a reader may =
not follow the xref to discover a legal child element is deprecated.
>=20
> These are automatically generated, and marking the deprecated ones is =
probably really really hard. We thought of this and punted.
>=20

Okay.



From nobody Mon Apr  7 12:41:17 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 1E5591A07F5; Mon,  7 Apr 2014 12:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 0lbUX2xwYsT3; Mon,  7 Apr 2014 12:41:10 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A54E1A0705; Mon,  7 Apr 2014 12:41:10 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-50-89.dllstx.fios.verizon.net [173.71.50.89]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s37Jf3c1073059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Mon, 7 Apr 2014 14:41:04 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-71-50-89.dllstx.fios.verizon.net [173.71.50.89] claimed to be unnumerable.local
Message-ID: <5342FF4F.4040906@nostrum.com>
Date: Mon, 07 Apr 2014 14:41:03 -0500
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.4.0
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, draft-ietf-l2vpn-vpls-ldp-mac-opt@tools.ietf.org, l2vpn@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/zB9Cekao_dqfGo1qWho5nakzgj8
Subject: [Gen-art] Gen-art LC review: draft-ietf-l2vpn-vpls-ldp-mac-opt-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: Mon, 07 Apr 2014 19:41: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-l2vpn-vpls-ldp-mac-opt-11
Reviewer: Robert Sparks
Review Date: 7Apr2014
IETF LC End Date: 8Apr2014
IESG Telechat date: not yet scheduled

Summary: This draft is almost ready for publication as a Proposed 
Standard, but has minor issues (primarily editorial) that should be 
addressed.

I found this document very difficult to read. It asks the reader to hop 
between sections in unusual ways (for instance, it sends the reader to 
the problem statement section for details on normative behavior). I 
strongly encourage an editorial pass focusing on document structure.

There are many instances of SHOULD in the document where the text should 
just be using prose instead. It's not always clear when an 
implementation would choose to ignore the SHOULD, and what the 
consequences of that choice would be.

The document is inconsistent about the level of support needed in the 
network before trying to use this extension.
Section 5.1.2 says the assumption is everything understands it before 
it's turned on. Section 6 points back to figure 2 and says
to use the extension over the pw where you administratively know the 
peer supports the extension, and fall back to 4762 for
everything else. Which of those did you intend?

Specific comments in document order:

Section 3.2 paragraph 1: This paragraph would benefit from being broken 
into several. It's hard to find its point. The SHOULD in this paragraph 
is probably not a 2119 SHOULD (this section isn't defining the 
protocol). It would be useful in this overview to explicitly say _why_ 
"This cannot be achieved with ... 4762]" at this point in the document.

Section 3.2 paragraph 2: This SHOULD _is_ defining protocol - shouldn't 
it be in section 5?

Section 4.1.1 paragraph 3: It took me some time to find Z on the figure. 
It might help to introduce it similar to how you introduce X.

Section 4.1.2: paragraph 1: I think you meant to reference 4.1.1

Section 5: The first sentence talks about requirements in section 4. 
Section 4 describes a problem using some examples but doesn't explicitly 
call out requirements. Doing so would help the document.

Last sentence in 5.1.1 (and several other places in the document): 
Please add an article before "MAC Flush message".  (I apologize for such 
a small nit, but each of these instances made making sure I was reading 
what the sentence intended significantly more difficult).

Section 5.1.2 first paragraph: This section is defining behavior - why 
are you sending the reader back into the problem statement for detail on 
the behavior?

5.1.2 paragraph 2: You meant section 6, not 5.

5.1.2 paragraph 3: I can't follow this paragraph's structure. I think 
you're trying to say "An MTU-s or PE2-rs SHOULD send MAC withdraw 
messages as defined in [RFC4762] in cases where the network is being 
upgraded and devices are not capable of understanding the optimized MAC 
flush." (But if so, the next sentence is redundant.) Why is this SHOULD?

5.1.3 paragraph 1: Why is this a SHOULD and not a MUST? (Similar 
question for the SHOULD in paragraph 2). It's not clear if you're trying 
to avoid "Some things won't implement this spec" or "Don't do this if 
you haven't administratively ensured every element understands this 
extension first" or something else?

5.1.3 paragraph 3: You say "unless specified otherwise". Do you ever 
specify otherwise? Why is this disclaimer here?

5.1.3 last paragraph: You meant section 6 not 5.






From nobody Mon Apr  7 12:43:26 2014
Return-Path: <paul.hoffman@vpnc.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 E215F1A0257 for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 12:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.347
X-Spam-Level: 
X-Spam-Status: No, score=-3.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, HELO_MISMATCH_COM=0.553] 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 mx1QoEnRHoyU for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 12:43:17 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5D28E1A047A for <gen-art@ietf.org>; Mon,  7 Apr 2014 12:43:05 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-175.dsl.dynamic.sonic.net [50.1.98.175]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s37Jguj4033730 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Apr 2014 12:42:58 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-175.dsl.dynamic.sonic.net [50.1.98.175] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4368F77F-B2DD-4990-AE97-F24BBE5FEB64@nostrum.com>
Date: Mon, 7 Apr 2014 12:42:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA2734FB-81B2-44DA-AA13-94357F5997E7@vpnc.org>
References: <7F266BF4-52CD-4A28-8AF7-745956E6EBA1@nostrum.com> <CEB04259-BFD4-41D6-85D4-45C5EAFD7E6B@vpnc.org> <4368F77F-B2DD-4990-AE97-F24BBE5FEB64@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/pXOCMmJsWMp35bsdF4lzDgS7_sc
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, draft-hoffman-xml2rfc.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Early Review of draft-hoffman-xml2rfc-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, 07 Apr 2014 19:43:24 -0000

Comment-on-comments below. I now have one new action item.

--Paul Hoffman

On Apr 7, 2014, at 11:37 AM, Ben Campbell <ben@nostrum.com> wrote:

> Hi, thanks for the quick response. Comments inline; sections that do =
not seem to need further comment are deleted, and marked with "[...]"
>=20
> Thanks!
>=20
> Ben.
>=20
> On Apr 5, 2014, at 8:10 PM, Paul Hoffman <paul.hoffman@vpnc.org> =
wrote:
>=20
> [...]
>=20
>>=20
>>> -- Section 1, paragraph 2:
>>>=20
>>> I find it confusing that we have two drafts in parallel, one for V2 =
that is obsoleted by this draft, and this draft for V3. With this draft =
copying much of V2 forward, which is authoritative?
>>=20
>> Both. the v2 draft is authoritative for that version of the format =
(which is still in use); this draft will be definitive for v3 when v3 is =
implemented. Unlike a regular protocol, this format is not going to be =
immediately implemented when the draft goes to the RFC Editor.
>=20
> It's not clear to me that updates to "regular protocols" always get =
immediately implemented, at least not to the point of immediately =
replacing older version.  Especially we we are talking about formally =
incrementing version numbers.
>=20
> I think my real question is whether V3 really obsoletes V2 in the =
usual sense. Do we allow further updates (e.g. an "updates" draft with =
bug fixes) to V2 once it becomes an RFC? If so, do those updates, =
assuming they impact "common" parts, affect V3? Would that be automatic, =
or would V3 require a parallel update? Do we intend to allow V2 to =
evolve independently of V3?

All good questions. I'll open a thread on rfc-interest with the =
question, but I strongly suspect it will end up having a non-answer.

>=20
>>=20
>>> -- 1.1, entry for <tident>
>>>=20
>>> THANK YOU!!!! I think faking indented text using the <list> work =
around was one of the most annoying things about previous versions.
>>=20
>> Hrm; I'm not used to seeing that in GenArt reviews. :-)
>>=20
>> And, to be fair, lots of the new features have been suggested by many =
people on the RFC Editor's design team and in the bigger community.
>=20
> Okay, change that to THANK Y'ALL!!!!
>=20
>>=20
>>> --2.2:
>>>=20
>>> Can I have more than one of any given address sub-element? If so, =
how should it render?
>>=20
>> Yep; unclear. There are a lot of things in this draft (and the in the =
v2 draft) where the rendering is undefined. We may or may not clarify =
those in the doc before we are finished; if not, it will be up to the =
programmers.
>=20
> I accept that different rendering decisions might be okay. But would =
you also leave whether a specific sub-element can be repeated to the =
implementors? Seem like that could lead to xml2rfc "code" that is =
correct for one processor but incorrect for another.

Nope. The format is the format: it allows multiple sub-elements, and it =
would be wrong for a processor to reject an input based on that. It is =
probably fine for a processor to not render them all, although it would =
be better if it issued a warning. It would be best if we had rules for =
how processors should render each entity, but we haven't gone to that =
level of detail yet.

>=20
> [...]
>=20
>>=20
>>> -- 2.7:
>>>=20
>>> It seems like <b> (and also <i>)  is just as much format dependent =
as things like <width>. Wouldn't something like <em> be more useful for =
this purpose, where you have an abstract concept of emphasis that can be =
rendered differently for different formats?
>>=20
>> In some senses, yes, but given that we know the main expected types =
of non-canonical output (HTML, PDF, EPUB), they all handle bold and =
italic and fixed-width fonts just fine. There are plenty of people who =
would think that "emphasis" means bold, and plenty who would think it =
means "italic".
>>=20
>>> This seems like a place where our use cases are different than those =
for HTML, where markup is usually rendered by browsers that have similar =
font display capabilities.
>>=20
>> No, our use cases very much align with HTML here: that's a design =
choice.
>=20
> Well, HTML _does_ have <em>. I realize it's not very useful in HTML, =
since you rarely render HTML to a format that can't do bold or italics. =
But to test the assertion, do you consider typesetting a common use case =
for HTML? Is it not one for xml2rfc?

No to both.

>=20
>>=20
>>> In particular, what happens to <b>text<.b> when rendered into ASCII =
text?
>>=20
>> Nothing. Just like today, there is a lot of formatting that is lost =
in the text output.
>=20
> There are some common conventions here; they just seemed to have =
fallen by the wayside. For example, a title of a long-format work gets =
italicized when that's supported, but underlined on an old fashioned =
typewriter. There are more modern simulations like _this_ and *this*. =20=

>=20
> OTOH, I guess an ascii rendering processor could make those same =
choices for <i> and <b> as well as for <em>, so maybe I just countered =
my own argument.

That was my first reaction. :-)

> But from a typesetting perspective, abstractions like <em> allow one =
to separate the intent of the author ("I want this to be emphasized") =
from the intent of the editor/publisher.("This is how our 'style' =
renders emphasis.")

In an ideal world where authors understood typesetting, yes. That's the =
world I began work in 35 years ago. (Cue the DEC formatting language =
theme music...) But that's not what is typical among IETF authors who =
are, not surprisingly, often literal-minded and goal-oriented.

>=20
>>=20
>>> -- 2.9:
>>>=20
>>> Why does the "cite" attribute have different requirements than, say, =
xref? In particular, why wouldn't I want to cite a reference in the =
current doc, rather than a URL?
>>=20
>> It can do both: the URL can be a fragment that points to a reference =
in the current doc.
>=20
> How would you do that? Is there a way to construct a URL that points =
to an xml2rfc anchor?

<blockquote cite=3D"#anchorname">, I believe.

>=20
>>=20
>>> -- 2.9.1:
>>>=20
>>> How would one reference an auto generated anchor identifier? If it =
doesn't exist until processing time...?
>>=20
>> Correct, so you can't. You can only use "target" attributes to named =
anchors.
>=20
> If you can't reference an auto-generated anchor, why do you have them? =
What else do you do with anchors?

After the RFC is published, other documents can reference the anchor. =
Currently, the document only specifies this for <blockquote> and <cref>, =
but it has been mentioned for other elements as well.

>=20
>>=20
>>> --2.33.2
>>>=20
>>> Is it possible to continue numbering from a previous list?
>>=20
>> Not directly.
>=20
> I may be misreading it, but doesn't V2 support number continuation =
with the "counter" attribute of <list>? If so, is the intent to remove =
that capability?

Yes and yes. Each list is free-standing. The need for continued =
numbering between lists in v2 is mostly obviated by allowing <t> in =
lists in v3. The semantics of "here is a second list whose numbers don't =
start at 1" are unclear, and we're trying to make v3 more semantically =
clearer.=20

>=20
> [...]
>=20
>>> -- 2.44.2:
>>>=20
>>> Why are numberless subsections disallowed?
>>=20
>> If it was a sub-section, the heading could easily be mistaken for =
free text.
>>=20
>>> It's pretty common to see documents that have non-numbered sub-heads =
inside numbered sections.
>>=20
>> Those are probably "notes" and such, not real sections. Do you see a =
need for these? It's certainly possible to have them, but they seem more =
confusing than necessary to me.
>=20
> I've seen docs (not necessarily RFCs), that did something like this:
>=20
> 1. Heading
> 1.1 Subhead
> 1.1.1 Minor Subhead
> (no number) Really Minor Subhead
>=20
> I think the idea is to label deep sub-topics without the clutter of =
1.1.1.1. Is it _necessary_? Probably not. But that's the use case I =
immediately envisioned when I thought about the ability to suppress =
numbering.=20

Noted. I'd prefer to make all levels headings numbered if that's the =
overall style.

>=20
> [...]
>=20
>>=20
>>> -- 5, security considerations
>>>=20
>>> I wonder if the possibility of executable content existing in an RFC =
or draft is worth mention here? For an extreme example, see RFC6716, =
Appendix A. But more realistically, 2.5.5 mentions the possibility of =
in-lined binary content, and 2.5.6 allows the identification of code in =
a way that a naive processor implementation might take as an invitation =
to interpret said code.
>>=20
>> Yup, and (as above) I added a paragraph about this.
>>=20
>>> Also, does the need for a processor to potentially render binary =
content in general (in-lined or otherwise) expand the attack surface =
over that for previous versions of XML2RFC?
>>=20
>> Not in any way I can think of.
>=20
> For example (just thinking "out loud"), if a processor could insert =
JPEG artwork, does it need to worry about buffer overflow attacks on the =
JPEG format, as well as attacks on the xml itself? If so, does it matter =
if the artwork was in-lined vs referenced?=20

Um, maybe. I'm not at all sure how to word a security consideration =
about that that would be more useful than "a processor should not be =
stupid when doing includes".

>=20
> [...]
>=20
>>=20
>>> -- 2.48, Content Model:
>>>=20
>>> It might be worth marking deprecated elements. Otherwise a reader =
may not follow the xref to discover a legal child element is deprecated.
>>=20
>> These are automatically generated, and marking the deprecated ones is =
probably really really hard. We thought of this and punted.
>>=20
>=20
> Okay.


From nobody Mon Apr  7 13:40:02 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 09D961A0847 for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 13:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, T_RP_MATCHES_RCVD=-0.01] 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 mT9Ri1WGGIq5 for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 13:39:53 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BFDE1A04B1 for <gen-art@ietf.org>; Mon,  7 Apr 2014 13:39:53 -0700 (PDT)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s37Kdjd7077741 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Apr 2014 15:39:46 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-173-172-146-58.tx.res.rr.com [173.172.146.58] claimed to be [10.0.1.29]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <FA2734FB-81B2-44DA-AA13-94357F5997E7@vpnc.org>
Date: Mon, 7 Apr 2014 15:39:46 -0500
X-Mao-Original-Outgoing-Id: 418595986.060336-071a105964e4e75d2b655a6e036f4a5a
Content-Transfer-Encoding: quoted-printable
Message-Id: <6578DB9B-72E7-4CF5-81B7-F44A574A100D@nostrum.com>
References: <7F266BF4-52CD-4A28-8AF7-745956E6EBA1@nostrum.com> <CEB04259-BFD4-41D6-85D4-45C5EAFD7E6B@vpnc.org> <4368F77F-B2DD-4990-AE97-F24BBE5FEB64@nostrum.com> <FA2734FB-81B2-44DA-AA13-94357F5997E7@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/YkIRX78JAGDjE4NhOD9WKfiDE50
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, draft-hoffman-xml2rfc.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Early Review of draft-hoffman-xml2rfc-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, 07 Apr 2014 20:39:59 -0000

On Apr 7, 2014, at 2:42 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> Comment-on-comments below. I now have one new action item.
>=20
> --Paul Hoffman
>=20
> On Apr 7, 2014, at 11:37 AM, Ben Campbell <ben@nostrum.com> wrote:
>=20
>=20

[...]

>>>=20
>>>> --2.2:
>>>>=20
>>>> Can I have more than one of any given address sub-element? If so, =
how should it render?
>>>=20
>>> Yep; unclear. There are a lot of things in this draft (and the in =
the v2 draft) where the rendering is undefined. We may or may not =
clarify those in the doc before we are finished; if not, it will be up =
to the programmers.
>>=20
>> I accept that different rendering decisions might be okay. But would =
you also leave whether a specific sub-element can be repeated to the =
implementors? Seem like that could lead to xml2rfc "code" that is =
correct for one processor but incorrect for another.
>=20
> Nope. The format is the format: it allows multiple sub-elements, and =
it would be wrong for a processor to reject an input based on that. It =
is probably fine for a processor to not render them all, although it =
would be better if it issued a warning. It would be best if we had rules =
for how processors should render each entity, but we haven't gone to =
that level of detail yet.
>=20

Well, that was the original question--are multiple of the same =
sub-element allowed :-)

I guess a better followup question than "how do you render it" would be =
"are there cases where multiples of the same sub-type clearly does or =
does not make sense according to RFC style.


>>=20
>> [...]
>>=20
>>>=20
>>>> -- 2.7:
>>>>=20
>>>> It seems like <b> (and also <i>)  is just as much format dependent =
as things like <width>. Wouldn't something like <em> be more useful for =
this purpose, where you have an abstract concept of emphasis that can be =
rendered differently for different formats?
>>>=20
>>> In some senses, yes, but given that we know the main expected types =
of non-canonical output (HTML, PDF, EPUB), they all handle bold and =
italic and fixed-width fonts just fine. There are plenty of people who =
would think that "emphasis" means bold, and plenty who would think it =
means "italic".
>>>=20
>>>> This seems like a place where our use cases are different than =
those for HTML, where markup is usually rendered by browsers that have =
similar font display capabilities.
>>>=20
>>> No, our use cases very much align with HTML here: that's a design =
choice.
>>=20
>> Well, HTML _does_ have <em>. I realize it's not very useful in HTML, =
since you rarely render HTML to a format that can't do bold or italics. =
But to test the assertion, do you consider typesetting a common use case =
for HTML? Is it not one for xml2rfc?
>=20
> No to both.
>=20
>>=20
>>>=20
>>>> In particular, what happens to <b>text<.b> when rendered into ASCII =
text?
>>>=20
>>> Nothing. Just like today, there is a lot of formatting that is lost =
in the text output.
>>=20
>> There are some common conventions here; they just seemed to have =
fallen by the wayside. For example, a title of a long-format work gets =
italicized when that's supported, but underlined on an old fashioned =
typewriter. There are more modern simulations like _this_ and *this*. =20=

>>=20
>> OTOH, I guess an ascii rendering processor could make those same =
choices for <i> and <b> as well as for <em>, so maybe I just countered =
my own argument.
>=20
> That was my first reaction. :-)
>=20
>> But from a typesetting perspective, abstractions like <em> allow one =
to separate the intent of the author ("I want this to be emphasized") =
from the intent of the editor/publisher.("This is how our 'style' =
renders emphasis.")
>=20
> In an ideal world where authors understood typesetting, yes. That's =
the world I began work in 35 years ago. (Cue the DEC formatting language =
theme music...) But that's not what is typical among IETF authors who =
are, not surprisingly, often literal-minded and goal-oriented.

Okay, I give in on this one.

>=20
>>=20
>>>=20
>>>> -- 2.9:
>>>>=20
>>>> Why does the "cite" attribute have different requirements than, =
say, xref? In particular, why wouldn't I want to cite a reference in the =
current doc, rather than a URL?
>>>=20
>>> It can do both: the URL can be a fragment that points to a reference =
in the current doc.
>>=20
>> How would you do that? Is there a way to construct a URL that points =
to an xml2rfc anchor?
>=20
> <blockquote cite=3D"#anchorname">, I believe.
>=20
>>=20
>>>=20
>>>> -- 2.9.1:
>>>>=20
>>>> How would one reference an auto generated anchor identifier? If it =
doesn't exist until processing time...?
>>>=20
>>> Correct, so you can't. You can only use "target" attributes to named =
anchors.
>>=20
>> If you can't reference an auto-generated anchor, why do you have =
them? What else do you do with anchors?
>=20
> After the RFC is published, other documents can reference the anchor. =
Currently, the document only specifies this for <blockquote> and <cref>, =
but it has been mentioned for other elements as well.

I think this means that, at least for blockquote, even if you leave out =
anchor attribute in the xml, you will get whatever sort of identifier =
makes sense in the rendered output (e.g. an id attribute in HTML)? I =
read it to mean that the processor would auto generate a (perhaps =
ephemeral) anchor in the XML itself, which is not quite the same thing.

>=20
>>=20
>>>=20
>>>> --2.33.2
>>>>=20
>>>> Is it possible to continue numbering from a previous list?
>>>=20
>>> Not directly.
>>=20
>> I may be misreading it, but doesn't V2 support number continuation =
with the "counter" attribute of <list>? If so, is the intent to remove =
that capability?
>=20
> Yes and yes. Each list is free-standing. The need for continued =
numbering between lists in v2 is mostly obviated by allowing <t> in =
lists in v3. The semantics of "here is a second list whose numbers don't =
start at 1" are unclear, and we're trying to make v3 more semantically =
clearer.=20

Okay

>=20
>>=20
>> [...]
>>=20
>>>> -- 2.44.2:
>>>>=20
>>>> Why are numberless subsections disallowed?
>>>=20
>>> If it was a sub-section, the heading could easily be mistaken for =
free text.
>>>=20
>>>> It's pretty common to see documents that have non-numbered =
sub-heads inside numbered sections.
>>>=20
>>> Those are probably "notes" and such, not real sections. Do you see a =
need for these? It's certainly possible to have them, but they seem more =
confusing than necessary to me.
>>=20
>> I've seen docs (not necessarily RFCs), that did something like this:
>>=20
>> 1. Heading
>> 1.1 Subhead
>> 1.1.1 Minor Subhead
>> (no number) Really Minor Subhead
>>=20
>> I think the idea is to label deep sub-topics without the clutter of =
1.1.1.1. Is it _necessary_? Probably not. But that's the use case I =
immediately envisioned when I thought about the ability to suppress =
numbering.=20
>=20
> Noted. I'd prefer to make all levels headings numbered if that's the =
overall style.

Okay

>=20
>>=20
>> [...]
>>=20
>>>=20
>>>> -- 5, security considerations
>>>>=20
>>>> I wonder if the possibility of executable content existing in an =
RFC or draft is worth mention here? For an extreme example, see RFC6716, =
Appendix A. But more realistically, 2.5.5 mentions the possibility of =
in-lined binary content, and 2.5.6 allows the identification of code in =
a way that a naive processor implementation might take as an invitation =
to interpret said code.
>>>=20
>>> Yup, and (as above) I added a paragraph about this.
>>>=20
>>>> Also, does the need for a processor to potentially render binary =
content in general (in-lined or otherwise) expand the attack surface =
over that for previous versions of XML2RFC?
>>>=20
>>> Not in any way I can think of.
>>=20
>> For example (just thinking "out loud"), if a processor could insert =
JPEG artwork, does it need to worry about buffer overflow attacks on the =
JPEG format, as well as attacks on the xml itself? If so, does it matter =
if the artwork was in-lined vs referenced?=20
>=20
> Um, maybe. I'm not at all sure how to word a security consideration =
about that that would be more useful than "a processor should not be =
stupid when doing includes".

Just as a strawman example:

Unlike previous versions, XML2RFC V3 allows the inclusion of potentially =
binary content via the "src" attribute of the <artwork> element. =
Processor implementors should bear in mind that such content may have =
vulnerabilities of its own. For example, certain JPEG renderers have =
been vulnerable to buffer-overflow attacks. An xml2rfc processor that =
allows the inclusion of artwork in JPEG format might be subject to =
buffer overrun attacks on both its XML parser and in its JPEG rendering =
code.

[...]=


From nobody Mon Apr  7 14:35:00 2014
Return-Path: <paul.hoffman@vpnc.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 DAADE1A026F for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 14:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.347
X-Spam-Level: 
X-Spam-Status: No, score=-3.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, HELO_MISMATCH_COM=0.553] 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 5QKqOqG_NhxC for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 14:34:48 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 299F81A0298 for <gen-art@ietf.org>; Mon,  7 Apr 2014 14:34:48 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-175.dsl.dynamic.sonic.net [50.1.98.175]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s37LYcs3040867 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Apr 2014 14:34:40 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-175.dsl.dynamic.sonic.net [50.1.98.175] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <6578DB9B-72E7-4CF5-81B7-F44A574A100D@nostrum.com>
Date: Mon, 7 Apr 2014 14:34:35 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6EACCA4-31ED-4213-A6F1-3598A05EB3C0@vpnc.org>
References: <7F266BF4-52CD-4A28-8AF7-745956E6EBA1@nostrum.com> <CEB04259-BFD4-41D6-85D4-45C5EAFD7E6B@vpnc.org> <4368F77F-B2DD-4990-AE97-F24BBE5FEB64@nostrum.com> <FA2734FB-81B2-44DA-AA13-94357F5997E7@vpnc.org> <6578DB9B-72E7-4CF5-81B7-F44A574A100D@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/k3NQcFsjgSbfOcrKmx7W3ieV-XM
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, draft-hoffman-xml2rfc.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Early Review of draft-hoffman-xml2rfc-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, 07 Apr 2014 21:34:55 -0000

On Apr 7, 2014, at 1:39 PM, Ben Campbell <ben@nostrum.com> wrote:

> On Apr 7, 2014, at 2:42 PM, Paul Hoffman <paul.hoffman@vpnc.org> =
wrote:
>=20
>> Comment-on-comments below. I now have one new action item.
>>=20
>> --Paul Hoffman
>>=20
>>>>=20
>>>>> --2.2:
>>>>>=20
>>>>> Can I have more than one of any given address sub-element? If so, =
how should it render?
>>>>=20
>>>> Yep; unclear. There are a lot of things in this draft (and the in =
the v2 draft) where the rendering is undefined. We may or may not =
clarify those in the doc before we are finished; if not, it will be up =
to the programmers.
>>>=20
>>> I accept that different rendering decisions might be okay. But would =
you also leave whether a specific sub-element can be repeated to the =
implementors? Seem like that could lead to xml2rfc "code" that is =
correct for one processor but incorrect for another.
>>=20
>> Nope. The format is the format: it allows multiple sub-elements, and =
it would be wrong for a processor to reject an input based on that. It =
is probably fine for a processor to not render them all, although it =
would be better if it issued a warning. It would be best if we had rules =
for how processors should render each entity, but we haven't gone to =
that level of detail yet.
>>=20
>=20
> Well, that was the original question--are multiple of the same =
sub-element allowed :-)
>=20
> I guess a better followup question than "how do you render it" would =
be "are there cases where multiples of the same sub-type clearly does or =
does not make sense according to RFC style.

I think they all probably make sense for some postal address format used =
somewhere in the world. The real question is whether we can guess how to =
sensibly render something with, say, two <city> elements. My guess is =
"no", and we'll end up telling the author to instead use a bunch of =
<postalLine> elements instead.

>>>>> -- 2.9.1:
>>>>>=20
>>>>> How would one reference an auto generated anchor identifier? If it =
doesn't exist until processing time...?
>>>>=20
>>>> Correct, so you can't. You can only use "target" attributes to =
named anchors.
>>>=20
>>> If you can't reference an auto-generated anchor, why do you have =
them? What else do you do with anchors?
>>=20
>> After the RFC is published, other documents can reference the anchor. =
Currently, the document only specifies this for <blockquote> and <cref>, =
but it has been mentioned for other elements as well.
>=20
> I think this means that, at least for blockquote, even if you leave =
out anchor attribute in the xml, you will get whatever sort of =
identifier makes sense in the rendered output (e.g. an id attribute in =
HTML)? I read it to mean that the processor would auto generate a =
(perhaps ephemeral) anchor in the XML itself, which is not quite the =
same thing.

Correct, and this has convinced me to remove the auto-generation of =
anchors from <blockquote> and <cref>. (And, since writing last, I have =
discovered that even anchors to <cref> doesn't even render in the =
current xml2rfc, so that is of questionable value as well.

>>>>> -- 5, security considerations
>>>>>=20
>>>>> I wonder if the possibility of executable content existing in an =
RFC or draft is worth mention here? For an extreme example, see RFC6716, =
Appendix A. But more realistically, 2.5.5 mentions the possibility of =
in-lined binary content, and 2.5.6 allows the identification of code in =
a way that a naive processor implementation might take as an invitation =
to interpret said code.
>>>>=20
>>>> Yup, and (as above) I added a paragraph about this.
>>>>=20
>>>>> Also, does the need for a processor to potentially render binary =
content in general (in-lined or otherwise) expand the attack surface =
over that for previous versions of XML2RFC?
>>>>=20
>>>> Not in any way I can think of.
>>>=20
>>> For example (just thinking "out loud"), if a processor could insert =
JPEG artwork, does it need to worry about buffer overflow attacks on the =
JPEG format, as well as attacks on the xml itself? If so, does it matter =
if the artwork was in-lined vs referenced?=20
>>=20
>> Um, maybe. I'm not at all sure how to word a security consideration =
about that that would be more useful than "a processor should not be =
stupid when doing includes".
>=20
> Just as a strawman example:
>=20
> Unlike previous versions, XML2RFC V3 allows the inclusion of =
potentially binary content via the "src" attribute of the <artwork> =
element. Processor implementors should bear in mind that such content =
may have vulnerabilities of its own. For example, certain JPEG renderers =
have been vulnerable to buffer-overflow attacks. An xml2rfc processor =
that allows the inclusion of artwork in JPEG format might be subject to =
buffer overrun attacks on both its XML parser and in its JPEG rendering =
code.

It really depends on what you mean by "binary". The v2 format supports =
inclusion of files in a few places already; a malicious submitter could =
make those files "binary". Further, a processor doesn't render anything: =
it puts out files. So, at best, the advice is "don't have a buffer =
overrun when including a file that you might output", which seems dumb. =
I'm still open to adding a security consideration, but I guess I feel it =
has to at least be marginally useful.

--Paul Hoffman=


From nobody Mon Apr  7 15:03:12 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 3C2101A0298 for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 15:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level: 
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, T_RP_MATCHES_RCVD=-0.01] 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 q5CTTH0T_e1I for <gen-art@ietfa.amsl.com>; Mon,  7 Apr 2014 15:03:05 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD6D1A02D1 for <gen-art@ietf.org>; Mon,  7 Apr 2014 15:02:59 -0700 (PDT)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s37M2oOR085383 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Apr 2014 17:02:51 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-173-172-146-58.tx.res.rr.com [173.172.146.58] claimed to be [10.0.1.29]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <C6EACCA4-31ED-4213-A6F1-3598A05EB3C0@vpnc.org>
Date: Mon, 7 Apr 2014 17:02:51 -0500
X-Mao-Original-Outgoing-Id: 418600971.756083-ec49417cf634171c0ab9a2a2fbdef0b3
Content-Transfer-Encoding: quoted-printable
Message-Id: <9663A7F0-9FBC-4C7F-8539-3E13CC73B10F@nostrum.com>
References: <7F266BF4-52CD-4A28-8AF7-745956E6EBA1@nostrum.com> <CEB04259-BFD4-41D6-85D4-45C5EAFD7E6B@vpnc.org> <4368F77F-B2DD-4990-AE97-F24BBE5FEB64@nostrum.com> <FA2734FB-81B2-44DA-AA13-94357F5997E7@vpnc.org> <6578DB9B-72E7-4CF5-81B7-F44A574A100D@nostrum.com> <C6EACCA4-31ED-4213-A6F1-3598A05EB3C0@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/uObg2kM_Ds0o7dL1TRMM8UP0HJ4
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, draft-hoffman-xml2rfc.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Early Review of draft-hoffman-xml2rfc-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, 07 Apr 2014 22:03:10 -0000

"Okay" on all topics save the one below.

Thanks!

Ben.

On Apr 7, 2014, at 4:34 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

[...]

>>>>>>=20
>>>>>> -- 5, security considerations
>>>>>>=20
>>>>>> I wonder if the possibility of executable content existing in an =
RFC or draft is worth mention here? For an extreme example, see RFC6716, =
Appendix A. But more realistically, 2.5.5 mentions the possibility of =
in-lined binary content, and 2.5.6 allows the identification of code in =
a way that a naive processor implementation might take as an invitation =
to interpret said code.
>>>>>=20
>>>>> Yup, and (as above) I added a paragraph about this.
>>>>>=20
>>>>>> Also, does the need for a processor to potentially render binary =
content in general (in-lined or otherwise) expand the attack surface =
over that for previous versions of XML2RFC?
>>>>>=20
>>>>> Not in any way I can think of.
>>>>=20
>>>> For example (just thinking "out loud"), if a processor could insert =
JPEG artwork, does it need to worry about buffer overflow attacks on the =
JPEG format, as well as attacks on the xml itself? If so, does it matter =
if the artwork was in-lined vs referenced?=20
>>>=20
>>> Um, maybe. I'm not at all sure how to word a security consideration =
about that that would be more useful than "a processor should not be =
stupid when doing includes".
>>=20
>> Just as a strawman example:
>>=20
>> Unlike previous versions, XML2RFC V3 allows the inclusion of =
potentially binary content via the "src" attribute of the <artwork> =
element. Processor implementors should bear in mind that such content =
may have vulnerabilities of its own. For example, certain JPEG renderers =
have been vulnerable to buffer-overflow attacks. An xml2rfc processor =
that allows the inclusion of artwork in JPEG format might be subject to =
buffer overrun attacks on both its XML parser and in its JPEG rendering =
code.
>=20
> It really depends on what you mean by "binary". The v2 format supports =
inclusion of files in a few places already; a malicious submitter could =
make those files "binary".

Were those files likely to be binary in normal usage?=20

(I also note that the v2 security considerations are almost identical to =
the V3 ones, except for a disclaimer that they are probably incomplete =
:-)  )

> Further, a processor doesn't render anything: it puts out files.

That's an interesting point that I hadn't considered. I think it's =
probably true most of the time, but not all the time. On minimal =
thinking, I can imagine a processor that converts artwork to some =
preferred format. Or maybe some sort of just in time render that =
combines xml processing with direct display or printing.

> So, at best, the advice is "don't have a buffer overrun when including =
a file that you might output", which seems dumb. I'm still open to =
adding a security consideration, but I guess I feel it has to at least =
be marginally useful.

I still think it might be useful to say something to the effect of =
"While most of these security considerations apply to the interpreting =
of XML and rendering into various output formats, implementors may find =
that they are interpreting things other than XML, and should remember =
that those things may have additional security considerations".

The situation that seems most worthy of mention is that, if someone =
writes a processor that pulls in other (perhaps downloadable) libraries, =
plug-ins, OS functions, etc to process input beyond the XML itself,  =
they may inherit any security issues of those things. I realize that's a =
true statement about computing in general--but it seems more relevant =
for V3 processors than for previous versions. The fact that people keep =
finding vulnerabilities in such architectures suggests that the horse is =
not quite dead.

Obviously, this is all personal opinion, and carries no more weight than =
those of any other commenter (and probably less than those who have =
actually been working on updating xml2rfc).




From nobody Mon Apr  7 23:58:40 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 63BFD1A014B; Mon,  7 Apr 2014 23:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-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 NJBHjiHz1Adf; Mon,  7 Apr 2014 23:58:35 -0700 (PDT)
Received: from p3plsmtpa09-08.prod.phx3.secureserver.net (p3plsmtpa09-08.prod.phx3.secureserver.net [173.201.193.237]) by ietfa.amsl.com (Postfix) with ESMTP id 265961A0146; Mon,  7 Apr 2014 23:58:29 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-08.prod.phx3.secureserver.net with  id nJyH1n0061huGat01JyHvd; Mon, 07 Apr 2014 23:58:24 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-opsec-lla-only.all@tools.ietf.org>
Date: Mon, 7 Apr 2014 23:58:18 -0700
Message-ID: <012001cf52f7$f0361670$d0a24350$@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: Ac9S8v0hRSibx5myQkiFkifq7Hdr0g==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/7K7fywQF5cRP9U-iuofzcv241O4
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-opsec-lla-only-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, 08 Apr 2014 06:58:39 -0000

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

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

Document: draft-ietf-opsec-lla-only-07
Reviewer: Peter Yee
Review Date: April-7-2014
IETF LC End Date: April-7-2014
IESG Telechat date: TBD

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

This document discusses the (controversial) use of IPv6 link-local addresses
on router infrastructure links.  I don't find all of the arguments for use
of link-local addresses to be terribly compelling, but I'm not utterly
averse to the document's publication as a summary of some of the pros and
cons for those who desire to configure their routers in the manner
prescribed.  There may be other reasons that should be taken into
consideration, but I lack a network operator's experience to discuss them.

Minor:

Page 4, 4th paragraph: I don't buy this argument.  DNS can be simplified for
non-link-local addresses by simply not registering those addresses in DNS.
Use of link-local addresses isn't a requirement to simplify DNS.

Page 4, 5th paragraph, 2nd sentence: SSH brute force password attacks aren't
really reduced unless the reduction is simply not being able to attack a
single router over multiple interfaces in parallel.  A better scheme for
reducing SSH brute force password attacks might be to limit the rate of
responses to SSH login attempts in the face of repeated failures.
Considering dropping this marginal example.

Page 4, 6th paragraph, 1st sentence: I'm not sure what is meant by "the same
result".  Is this in reference to all 5 paragraphs that precede the 6th?  If
so, you might wish to elaborate with "the same results as the above" .
However, if the same results can be obtained without going to link-local
addressing as this paragraph indicates, why is the use of link-local
addressing being suggested?  The paragraph might do well to explain why one
scheme is preferable over the other.

Page 6, 1st partial paragraph: the argument is made that "more work" is
required to discover all of an IXPs loopback interface addresses before a
generic attack can be mounted.  This wouldn't seem to be a lot of upfront
work and once it has been done, the advantage is negated.  I don't find the
argument particularly persuasive.  

Nits:

Page 2, Section 2 title: change "Address" to "Addressing".

Page 3, second paragraph: change "non link-local" to "non-link-local".

Page 4, 1st paragraph, 3rd sentence: change "accellerated" to "
accelerated".

Page 4, 5th paragraph, 2nd sentence: delete the comma after "[RFC4987])" and
change the "or" to "and".

Page 6, 1st full paragraph, 1st sentence: change "allow" to "allows" and
insert "an" before "MPLS LSP".


		-Peter Yee




From nobody Tue Apr  8 02:33:07 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 51CC41A01FA for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 02:33:05 -0700 (PDT)
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 cC4CHreYZYBQ for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 02:33:01 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) by ietfa.amsl.com (Postfix) with ESMTP id 202061A01EE for <gen-art@ietf.org>; Tue,  8 Apr 2014 02:33:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 6597A240A31; Tue,  8 Apr 2014 02:32:55 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (60-250-43-148.HINET-IP.hinet.net [60.250.43.148]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 489492406E4; Tue,  8 Apr 2014 02:32:54 -0700 (PDT)
Message-ID: <5343C243.2040805@joelhalpern.com>
Date: Tue, 08 Apr 2014 05:32:51 -0400
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.4.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org,  Paul Hoffman <paul.hoffman@vpnc.org>, ISE <rfc-ise@rfc-editor.org>,  "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
References: <532B70EE.9090704@nostrum.com>
In-Reply-To: <532B70EE.9090704@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/NSpUc7zFEGAbTicGWD4zFlR0-Lk
Subject: [Gen-art]  review: draft-hoffman-xml2rfc-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, 08 Apr 2014 09:33:05 -0000

I am one of the requested Gen-ART 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-hoffman-xml2rfc-04
     The 'XML2RFC' version 3 Vocabulary
Reviewer: Joel M. Halpern

Summary: This review focuses on readability rather than on XML details.
     In that light, this document could use some improvement.

Major issues:
     The explanation in section 1.1 seems to bounce from topic to topic 
losing the reader repeatedly.  The explanation of the intended 
compatibility before the list of changes is confusing.  Either there are 
v2 features that don't work, or all v2 works, with some deprecated.
     It seems that discussion of the RFC Editor handling of v2 documents 
and this grammar belongs somewhere other than the definition of the 
grammar.  I was surprised to find discussion of canonical RFCs here. 
That set of text was probably the most confusing aspect of section 1.1.

     In section 2.5.6 on the 'type' attribute of the <artwork> element, 
it talks about the processor.  Since that appears to be a reference to 
the internal RFC Editor processor, rather than to the tools readers or 
writers will use, I would think that confusing text should be removed. 
(The processor will throw errors in certain cases, but consumers should 
not throw errors in any text cases?)


Minor issues:
     The question of how the grammar is generated is not a substantive 
difference between v2 and v3, and tells the reader nothing about what 
will follow.  If it should be mentioned at all, it would seem better in 
some other section of the document than 1.1

     Does <artwork> section 2.5 still need to be enclosed in the cdata 
construct to actually have the formatting preserved?  If so, should 
section 2.5 say that?  (Or am I just confused and issuing useless 
incantations in my current docs?)

     In section 2.5, and probably elsewhere, some of the attributes are 
"ought to be avoided", and one is "Deprecated".  The author apparently 
means something specific by "ought to be avoided", but this reader is 
confused.

     In section 2.22.6 on the suppress-title attribute for the <figure> 
element, the text is either confusing or incorrect.  THe text talks 
about figures that have anchor attributes getting autogenerated titles. 
  And that if one wants to suppress that, one should set this to 
"false".  It seems pretty odd that setting suppress to false (which is 
the default) would suppress the autogenerated title.  If it will, the 
attribute name is just wrong.  More likely, you suppress the 
auto-generated title by setting this attribute to "true".
     This also seems to occur in 2.49.4 in the suppress-title for <table>.

     Since <format> is defined (in section 2.23) it ought to be lsited 
as part of the valid content model for <reference> in section 2.40.

    In section 2.40 on <reference>, it might be useful to explain what 
will happen with the short form references.  It seems that how they get 
rendered will depend upon whether the processing engine has the ability 
to find additional data to use?  Or maybe not?

     Also, since <reference> allows <front>, <innerRefContent>, ... it 
seems that <reference> has a content model.  So I presume it is an error 
for it to say that it does not have a content model?

    I would have expected the values of the 'series' attribute of the 
<reference> element to be described in the attribute section (2.40.3) 
rather than in the base element section (2.40).


Nits/editorial comments:
     It would be nice if the deprecated elements were marked as 
deprecated both in their definition and in the places where they can 
appear.  (for example, marking <facsimile> as deprecated in the content 
model listing for <address>).  On the other hand, that may be a pain to 
get right.

     In the description of <date> in section 2.15, the text correctly 
notes that it can appear either as a document date or as a reference 
date.  And then correctly notes that the only legal parent for this is 
<front>.  Is there any way to remind the reader that <front> is used in 
long form references?


From nobody Tue Apr  8 03:15:50 2014
Return-Path: <julian.reschke@gmx.de>
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 988581A0220 for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 03:15:46 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 nrUkjDfvZqNM for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 03:15:41 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 98A701A0289 for <gen-art@ietf.org>; Tue,  8 Apr 2014 03:15:41 -0700 (PDT)
Received: from [192.168.2.117] ([93.217.69.239]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MI5Ve-1WaCtC334Y-003xvh; Tue, 08 Apr 2014 12:15:29 +0200
Message-ID: <5343CC30.5080203@gmx.de>
Date: Tue, 08 Apr 2014 12:15:12 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>,  "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>,  ISE <rfc-ise@rfc-editor.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
References: <532B70EE.9090704@nostrum.com> <5343C243.2040805@joelhalpern.com>
In-Reply-To: <5343C243.2040805@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:ODLhCRKDdbE1WQ0CXctW4e28g3/Yx4N7MKr83PJaNAAnhsmNJiD ORNEIPMI0V8L5Le2E+I+l2C+sEFTdCyKRndsbkIrX71AO79hbaXkLtbmn+HegAse2p2OC+q 1O0yvLvxFTnKVvR9ePjJri50fXVW2BzJlfUK0su7FHU+2Vl25nM/zHw5rpKwCbWaXl7Rk6P j2G75oDVlxkYEMaFjU3Gw==
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/0_IEEKx8-wCnedUVJhenXFOMW7s
Subject: Re: [Gen-art] [rfc-i]  review: draft-hoffman-xml2rfc-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, 08 Apr 2014 10:15:46 -0000

On 2014-04-08 11:32, Joel M. Halpern wrote:
> ...
>      Does <artwork> section 2.5 still need to be enclosed in the cdata
> construct to actually have the formatting preserved?  If so, should
> section 2.5 say that?  (Or am I just confused and issuing useless
> incantations in my current docs?)

There is no need (and never was) to use CDATA unless you want to avoid 
escaping "<" and "&".

>      Since <format> is defined (in section 2.23) it ought to be lsited
> as part of the valid content model for <reference> in section 2.40.

It currently states "Content model: this element does not have any 
contents." which indicates a bigger problem :-)

> ...


Best regards, Julian


From nobody Tue Apr  8 08:30:56 2014
Return-Path: <paul.hoffman@vpnc.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 701551A0433 for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 08:30:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.353
X-Spam-Level: *
X-Spam-Status: No, score=1.353 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553] 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 gDdNOA4Gj7Hf for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 08:30:48 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 884561A0454 for <gen-art@ietf.org>; Tue,  8 Apr 2014 08:30:48 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-175.dsl.dynamic.sonic.net [50.1.98.175]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s38FUjIJ000398 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 8 Apr 2014 08:30:46 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-175.dsl.dynamic.sonic.net [50.1.98.175] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <5343C243.2040805@joelhalpern.com>
Date: Tue, 8 Apr 2014 08:30:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D3448424-6B53-445B-B681-6E3E3F8CB249@vpnc.org>
References: <532B70EE.9090704@nostrum.com> <5343C243.2040805@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Gz7gdLtFmoAKGIivPjJX31pqwqo
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: Re: [Gen-art] [rfc-i]  review: draft-hoffman-xml2rfc-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, 08 Apr 2014 15:30:52 -0000

On Apr 8, 2014, at 2:32 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:

> I am one of the requested Gen-ART 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.

Neither of those exist today, but that topic is under discussion.

> Document: draft-hoffman-xml2rfc-04
>    The 'XML2RFC' version 3 Vocabulary
> Reviewer: Joel M. Halpern
>=20
> Summary: This review focuses on readability rather than on XML =
details.
>    In that light, this document could use some improvement.
>=20
> Major issues:
>    The explanation in section 1.1 seems to bounce from topic to topic =
losing the reader repeatedly. =20

I figured doing the list in alphabetical order by element would allow =
comparison more easily. It sounds like you would prefer the list grouped =
by type of change?

> The explanation of the intended compatibility before the list of =
changes is confusing.  Either there are v2 features that don't work, or =
all v2 works, with some deprecated.

Both are true. Some v2 features are described in the v2 document as not =
working; in addition, some v2 features are deprecated in v3 because they =
are replaced by something better.

>    It seems that discussion of the RFC Editor handling of v2 documents =
and this grammar belongs somewhere other than the definition of the =
grammar.  I was surprised to find discussion of canonical RFCs here. =
That set of text was probably the most confusing aspect of section 1.1.

Some felt that it was important to list the design criteria to explain =
the changes. Those design criteria are the ones that you are calling =
confusing. Are you proposing that they not be listed? Or listed =
elsewhere?

>    In section 2.5.6 on the 'type' attribute of the <artwork> element, =
it talks about the processor.  Since that appears to be a reference to =
the internal RFC Editor processor,

Arrgh, no. Good catch. It is about private processors. I'll make that =
explicit.

> rather than to the tools readers or writers will use, I would think =
that confusing text should be removed. (The processor will throw errors =
in certain cases, but consumers should not throw errors in any text =
cases?)

Got it; I'll clarify that as well.

> Minor issues:
>    The question of how the grammar is generated is not a substantive =
difference between v2 and v3, and tells the reader nothing about what =
will follow.  If it should be mentioned at all, it would seem better in =
some other section of the document than 1.1

Done.

>    Does <artwork> section 2.5 still need to be enclosed in the cdata =
construct to actually have the formatting preserved?  If so, should =
section 2.5 say that?  (Or am I just confused and issuing useless =
incantations in my current docs?)

The latter, and I say that as someone who was doing that much longer =
than I needed to. As Julian said, you only need that incantation if =
there are "<" and "&" characters. Of course, if you have those =
characters and you don't do CDATA, the error message you get seems =
unrelated to the problem at hand...

>    In section 2.5, and probably elsewhere, some of the attributes are =
"ought to be avoided", and one is "Deprecated".  The author apparently =
means something specific by "ought to be avoided", but this reader is =
confused.

Fixed.

>    In section 2.22.6 on the suppress-title attribute for the <figure> =
element, the text is either confusing or incorrect.  THe text talks =
about figures that have anchor attributes getting autogenerated titles.  =
And that if one wants to suppress that, one should set this to "false".  =
It seems pretty odd that setting suppress to false (which is the =
default) would suppress the autogenerated title.  If it will, the =
attribute name is just wrong.  More likely, you suppress the =
auto-generated title by setting this attribute to "true".

Correct. Fixed.

>    This also seems to occur in 2.49.4 in the suppress-title for =
<table>.

Ditto and ditto.

>    Since <format> is defined (in section 2.23) it ought to be lsited =
as part of the valid content model for <reference> in section 2.40.

As Julian said, we have a bigger problem with this section. As you =
probably noticed the sub-sections are automatically generated. The =
tooling for that (and deep bows to Julian for doing that tooling) is =
having a problem with my proposed format right now. This will be =
resolved.

>   In section 2.40 on <reference>, it might be useful to explain what =
will happen with the short form references.  It seems that how they get =
rendered will depend upon whether the processing engine has the ability =
to find additional data to use?  Or maybe not?

Good point, yes.

>    Also, since <reference> allows <front>, <innerRefContent>, ... it =
seems that <reference> has a content model.  So I presume it is an error =
for it to say that it does not have a content model?

Exactly.

>   I would have expected the values of the 'series' attribute of the =
<reference> element to be described in the attribute section (2.40.3) =
rather than in the base element section (2.40).

We might move them there, depending on whether we keep these as =
attributes. This is still under discussion.

> Nits/editorial comments:
>    It would be nice if the deprecated elements were marked as =
deprecated both in their definition and in the places where they can =
appear.  (for example, marking <facsimile> as deprecated in the content =
model listing for <address>).  On the other hand, that may be a pain to =
get right.

This has been suggested many times. We'll see if we can add this to the =
tooling, but it might be very difficult to do reliably.

>    In the description of <date> in section 2.15, the text correctly =
notes that it can appear either as a document date or as a reference =
date.  And then correctly notes that the only legal parent for this is =
<front>.  Is there any way to remind the reader that <front> is used in =
long form references?

Done.

Thanks!

--Paul Hoffman=


From nobody Tue Apr  8 08:42:20 2014
Return-Path: <julian.reschke@gmx.de>
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 3BAB91A0461 for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 08:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 msxdTtkRu6C6 for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 08:42:14 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 606991A040F for <gen-art@ietf.org>; Tue,  8 Apr 2014 08:42:14 -0700 (PDT)
Received: from [192.168.2.117] ([93.217.69.239]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0LlESk-1X6LDL1MoQ-00b2qy; Tue, 08 Apr 2014 17:42:01 +0200
Message-ID: <534418C2.1090200@gmx.de>
Date: Tue, 08 Apr 2014 17:41:54 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>,  "Joel M. Halpern" <jmh@joelhalpern.com>
References: <532B70EE.9090704@nostrum.com> <5343C243.2040805@joelhalpern.com> <D3448424-6B53-445B-B681-6E3E3F8CB249@vpnc.org>
In-Reply-To: <D3448424-6B53-445B-B681-6E3E3F8CB249@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:wiJRf+vfgvWLt82uyZRwWjGgw7jK5Ja+nBZAXPUhL8Sbw1vpkJI qyqUlJt1//DzpA2+ofnlRA/TjrtCRAb0umLJyjnuPlxiunXIzLzyIZhYVM5pC1IJC2p1CAk mBv7TzQDcvmJeBuDPDIcbYmp79g6yIKJsnKVlUP1Lrdzoizy6eRhyeHIn67MqSjU1YvCsqw ikP+RFqAvFfIx0m6w4t2Q==
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/1gYV-ToIPOFPIMbEikCf38RDtns
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: [Gen-art] CDATA, was: [rfc-i]  review: draft-hoffman-xml2rfc-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, 08 Apr 2014 15:42:18 -0000

On 2014-04-08 17:30, Paul Hoffman wrote:
> ...
>>     Does <artwork> section 2.5 still need to be enclosed in the cdata construct to actually have the formatting preserved?  If so, should section 2.5 say that?  (Or am I just confused and issuing useless incantations in my current docs?)
>
> The latter, and I say that as someone who was doing that much longer than I needed to. As Julian said, you only need that incantation if there are "<" and "&" characters. Of course, if you have those characters and you don't do CDATA, the error message you get seems unrelated to the problem at hand...
> ...

You *never* "need" CDATA. CDATA is just a syntactic construct that can 
make it easier to escape things.

Basically, you trade the need to replace "<" by "&lt;" and "&" by 
"&amp;" by the need not to have certain character sequences inside the 
CDATA section.

Best regards, Julian


From nobody Tue Apr  8 12:21: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 C75431A0709 for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 12:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 8c0ZtFQ21duL for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 12:21:17 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4DBDF1A06F0 for <gen-art@ietf.org>; Tue,  8 Apr 2014 12:21:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E595D2CED6; Tue,  8 Apr 2014 22:21:15 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u66JznWLKJtD; Tue,  8 Apr 2014 22:21:14 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7E6012CC48; Tue,  8 Apr 2014 22:21:14 +0300 (EEST)
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: <53305C3B.4030009@isode.com>
Date: Tue, 8 Apr 2014 22:21:14 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <5499BF74-8101-46B6-B007-BEC7879A69ED@piuha.net>
References: <53305C3B.4030009@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/P9VRXVMRJAR0ByOQp84q80yq5gE
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-cdni-framework.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-cdni-framework-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, 08 Apr 2014 19:21:23 -0000

Alexey: thank you for your review.

Jari

On Mar 24, 2014, at 6:24 PM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:

> I am the assigned Gen-ART reviewer for draft-ietf-cdni-framework-10.
>=20
> For background on Gen-ART, please see the FAQ at =
<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
>=20
> Summary: This draft is ready for publication as an Informational RFC.
>=20
> Major issues: none
> Minor issues: none
> Nits: none
>=20
> Best Regards,
> Alexey
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Apr  8 12:26:33 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 B41431A0425 for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 12:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 SgYQzwT8L_rX for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 12:26:27 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 1ACFD1A01BA for <gen-art@ietf.org>; Tue,  8 Apr 2014 12:26:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5DB392CED6; Tue,  8 Apr 2014 22:26:26 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eEF5mUsGxcrd; Tue,  8 Apr 2014 22:26:25 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 335062CC48; Tue,  8 Apr 2014 22:26:25 +0300 (EEST)
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: <CAPv4CP-r9xDefNDxkF7v3DbET9hM9jiYiAX2Pc2HgHdD1RjwNA@mail.gmail.com>
Date: Tue, 8 Apr 2014 22:26:25 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <67F5EE00-ED9B-4D64-8C7E-69CBFF67B076@piuha.net>
References: <CAPv4CP-r9xDefNDxkF7v3DbET9hM9jiYiAX2Pc2HgHdD1RjwNA@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/qhSOxeP9Mk-k23xY5Ulvb4j1itQ
Cc: gen-art <gen-art@ietf.org>, draft-vanelburg-dispatch-private-network-ind.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-vanelburg-dispatch-private-network-ind-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, 08 Apr 2014 19:26:29 -0000

Thanks for your review, Scott.

Jari

On Feb 24, 2014, at 11:57 PM, Scott Brim <scott.brim@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-vanelburg-dispatch-private-network-ind-05
> Reviewer: Scott Brim
> Review Date: 2014-02-24
> IETF LC End Date: 2014-03-14
> IESG Telechat date:
> 
> Summary: This draft is ready for publication as an informational RFC.
> 
> Major issues:
> 
> Minor issues:
> 
> Nits/editorial comments:
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Apr  8 12:27: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 063591A04B8 for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 12:27:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 7MnY8it00BJh for <gen-art@ietfa.amsl.com>; Tue,  8 Apr 2014 12:27:35 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 249A61A01BA for <gen-art@ietf.org>; Tue,  8 Apr 2014 12:27:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 671212CED6; Tue,  8 Apr 2014 22:27:16 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LFZU6d0E33nA; Tue,  8 Apr 2014 22:27:15 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id BA9292CC48; Tue,  8 Apr 2014 22:27:15 +0300 (EEST)
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: <ABCAA4EF18F17B4FB619EA93DEF7939A32DDA29A@eusaamb107.ericsson.se>
Date: Tue, 8 Apr 2014 22:27:15 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AFD9B22-A803-48D1-8916-6766F6BA7895@piuha.net>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32DDA29A@eusaamb107.ericsson.se>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/j5zhqkB5vRHFCxv0sCToAcy_n3I
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-xrblock-rtcp-xr-loss-conceal.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-loss-conceal.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Call review of draft-ietf-xrblock-rtcp-xr-loss-conceal-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, 08 Apr 2014 19:27:37 -0000

Thank you for your review, Meral.

Jari

On Apr 4, 2014, at 8:43 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>.
> =20
> Please wait for direction from your document shepherd or AD before =
posting a new version of the draft.
> =20
> Document: draft-ietf-xrblock-rtcp-xr-loss-conceal-11
> Reviewer: Meral Shirazipour
> Review Date: 2014-04-04
> IETF LC End Date: 2013-03-28
> IESG Telechat date: 2014-04-10
> =20
> Summary: This draft is ready to be published as 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 nobody Tue Apr  8 13:59:21 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 659AF1A040D; Tue,  8 Apr 2014 13:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.427
X-Spam-Level: 
X-Spam-Status: No, score=0.427 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, 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 p8ndqZgaA8Kj; Tue,  8 Apr 2014 13:59:07 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id A29C51A026E; Tue,  8 Apr 2014 13:59:06 -0700 (PDT)
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s38KwumY001289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Apr 2014 16:58:57 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s38KwumY001289
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1396990740; bh=h0bIKzzWEU1n2jM90gYTQeYA8/E=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=WlBrDPXh2HRboR1yXuwIz8ntmEf7ScWQlVe9lvALNRQwHk5fugR7I2xfKeQgdpzkB f9RfJBqYnlPgq2VGgq6IztahDRSeu/YWcr1I/IMBRu+UK9q6U/vJcEt+fA+5ROB2SK W+JkXcDGKzpA+c67HjY3RLkG/hJE7jB9LH1ak51o=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s38KwumY001289
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd53.lss.emc.com (RSA Interceptor); Tue, 8 Apr 2014 16:58:39 -0400
Received: from mxhub08.corp.emc.com (mxhub08.corp.emc.com [128.222.70.205]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s38Kwbbd021670 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 8 Apr 2014 16:58:38 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub08.corp.emc.com ([128.222.70.205]) with mapi; Tue, 8 Apr 2014 16:58:37 -0400
From: "Black, David" <david.black@emc.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 8 Apr 2014 16:58:36 -0400
Thread-Topic: Gen-ART review of draft-ietf-trill-esadi-06.txt
Thread-Index: Ac9Q4vX57WukMZzRQMC+3VZdMgWnAwCdvEuQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C1D15CD@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C0ADDF7@MX15A.corp.emc.com> <CAF4+nEEL1LUxBEaGyUxEHNWb=fMgu2zVAuHqiSf64d0ZW=w3ng@mail.gmail.com>
In-Reply-To: <CAF4+nEEL1LUxBEaGyUxEHNWb=fMgu2zVAuHqiSf64d0ZW=w3ng@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/4UbgR73ZHkrDfmXYZQZIFrmUekg
Cc: "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ostokes@extremenetworks.com" <ostokes@extremenetworks.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-esadi-06.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, 08 Apr 2014 20:59:12 -0000

Donald,

Thank you for the extensive comments on the review.  I'll summarize here
rather than add more text inline.  I'm fine with the proposed course of
action for anything not mentioned here:

[1] Absence of backwards compatibility:
        - The Appendix A changes look good.
        - The "limited deployment" (and presumably also "limited
                implementation") rationale for no backwards compatibility
                should be included in Section 1.1.  This merits additional
                text in Section 1.1

[2] Structure of draft wrt RFC 6325:
        I think the rest of the proposed changes to Section 1.1 are reasona=
ble:

        - Appendix A does explain what's changed.  I would have liked to se=
e
                more formality/precision in Section 1.1, but that's a matte=
r of
                editorial taste that I'll leave to the authors.  The propos=
ed
                addition of a forward reference to Appendix A will definite=
ly
                help.
        - The proposed addition of an explicit statement about expecting
                familiarity with RFC 6325 in Section 1.1 will also help.

[3] Independence of ESADI instances: What bothered me was the absence of
a strong mention of implementation structure - I have some new text to
suggest to strengthen that point:

OLD
   It is an implementation decision how independent the multiple ESADI
   instances at an RBridge are.
NEW
   Multiple ESADI instances may share implementation components within
   an RBridge as long as that sharing preserves the independent operation
   of each instance of the ESADI protocol.

Then the link state database example that follows makes more sense,
at least to me.

[4] Section 8  Authentication TLV usage discussion.

> How about adding a new paragraph to Section 8, between the current
> first and second paragraphs, incorporating the above, such as:
>
>    However, there may be cases where it is not necessary to
>    authenticate ESADI PDUs despite using authenticated registration
>    for end stations.  For example a TRILL campus with secure RBridges
>    and inter-RBridge links configured as trunks but some end stations
>    connected via 802.11 wireless access links might use 802.11
>    authentication for the connection of such end stations but not
>    necessarily authenticate ESADI PDUs. Note that if the IS-IS LSPs in
>    a TRILL campus are authenticated, perhaps due to a concern about
>    forged packets, the ESADI PDUs will be authenticated by default as
>    provided in Section 6.3.

These seems a bit descriptive, with most of the text describing a
specific example.  I'm looking for some more prescriptive guidance
about what SHOULD (or perhaps should?) be the case when the Authentication
TLV is not used with authenticated registration.

[5] VLAN tag presence (nit)

> > Last sentence on p.8:
> >
> > OLD
> >    The outer VLAN tag will not be present if it was stripped by
> >    an Ethernet port out of which the packet was sent.
> > NEW
> >    The outer VLAN tag will not be present for a packet on an
> >    an Ethernet link that does not use VLAN tags.

I don't think the word "stripped" is right, as it would not apply if
the tag wasn't present in the first place, although I also agree with
your comment that my suggested use of "link" isn't right, either.

Here's another suggestion:

    The outer VLAN tag will not be present if it was not included
    by the Ethernet port that sent the packet.

Thanks,
--David

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Saturday, April 05, 2014 11:23 AM
> To: Black, David
> Cc: zhai.hongjun@zte.com.cn; hu.fangwei@zte.com.cn; Radia@alum.mit.edu;
> ostokes@extremenetworks.com; General Area Review Team (gen-art@ietf.org);
> trill@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART review of draft-ietf-trill-esadi-06.txt
>
> Hi David,
>
> Thanks for this very thorough review. See my responses below:
>
> On Sat, Mar 29, 2014 at 10:23 PM, Black, David <david.black@emc.com> wrot=
e:
> >
> > I am the assigned Gen-ART 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-trill-esadi-06.txt
> > Reviewer: David L. Black
> > Review Date: March 29, 2014
> > IETF LC End Date: April 1, 2014
> >
> > Summary: This draft is on the right track, but has open issues
> > described in the review.
> >
> > This draft revises the ESADI specification for TRILL from its
> > original form in RFC 6325.
> >
> > Major issues:
> >
> > The draft changes ESADI in a non-backwards-compatible fashion from
> > its original specification in RFC 6325, but does not explain why this
> > is ok.  That explanation needs to be provided, and if implementations
> > of ESADI as originally specified in RFC 6325 exist, that explanation
> > needs to encompass coexistence and interoperability (or lack thereof)
> > with such implementations.  That explanation probably belongs in
> > Section 1.1, and could be expanded upon in Appendix A.
>
> This was a considered decision of the TRILL WG. At least since the -02
> version in February 2013, the ESADI WG draft has had ESADI-LSP
> provisions that were incompatible with RFC 6325 ESADI for the purpose
> of accomodating orders of magnitude more LSP fragments. This text in
> the draft, which originally used a somewhat ad hoc change from IS-IS
> LSPs to accomodate additional fragments, was posted to the list
> without objection before being incorporated. Since a standard IS-IS
> way of doing this was later in process in the ISIS WG, the ESADI draft
> was changed to follow this more standard way of providing for more LSP
> fragments and a new WG Last Call done in the TRILL WG specifically on
> this issue. See
>
> http://www.ietf.org/mail-archive/web/trill/current/msg06037.html
> http://www.ietf.org/mail-archive/web/trill/current/msg06009.html
>
> In Appendix A (Changes to [RFC6325]), how about replacing items 2 and
> 3 in the list as follows (includes fixing a typo in item 3):
>
> OLD
>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
>       is changed from the base IS-IS format to the Extended Level 1
>       Circuit Scoped format in [FS-LSP].
> NEW
>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
>       is changed from the base IS-IS format to the Extended Level 1
>       Circuit Scoped format (E-L1CS) specified in [FS-LSP]. This
>       change is not backwards compatible with [RFC6325]. It is made in
>       light of (a) the very limited, if any, deployment of [RFC6325]
>       ESADI, and (b) the 256 times greater information carrying
>       capacity of the E-L1CS format compared with the base IS-IS
>       format. It is anticipated that this greater carrying capacity
>       will be needed, under some circumstances, to carry end station
>       addressing information or other information that is added to
>       ESADI in the future.
> OLD
>    3. Unicasting of ESADI PDUs is supported including replacing Section
>       4.6.2.2 of [RFC6325] with the next text give in Section 4.1 of
>       this document.
> NEW
>    3. Unicasting of ESADI PDUs is optionally supported including
>       replacing Section 4.6.2.2 of [RFC6325] with the new text give in
>       Section 4.1 of this document. This unicast support is backwards
>       compatible because it is only used when the recipient RBridge
>       signals its support.
>
> See possible replacement below for the first paragraph of Section 1.1
> that includes a condensed version of this additional material
> concerning backwards non-compatibility.
>
> > Overall, this draft is not self-contained - to a significant extent,
> > it is written as if it were effectively a long collection of errata
> > to the ESADI specification in RFC 6325. That makes it difficult to
> > understand - it would be better if this draft completely obsoleted
> > and replaced the ESADI specification in RFC 6325, describing its
> > changes, instead of providing specific text changes to portions of
> > the RFC 6325 text.
>
> All of the changes to ESADI are described in Appendix A.
>
> If the ESADI related material in RFC 6325 was entirely contained in
> one contiguous area of RFC 6325, it would have been easy to write this
> draft as simply obsoleting and replacing that area of RFC 6325.  The
> largest such monolithic block on ESADI in RFC 6325 is Section 4.2.5
> (The TRILL ESADI Protocol), including its two subsections ("4.2.5.1
> TRILL ESADI Participation" and "4.2.5.2 TRILL ESADI Information"). All
> of that is obsoleted and replaced by this draft.  However, there are
> other non-contiguous parts of RFC 6325 necessarily affected. For
> example, Section 4.6 of RFC 6325 describes how to handle every
> possible type of frame that might be received; since an ESADI PDU is
> one such type of frame, it is necessary to change Section 4.6.2.2
> ("TRILL ESADI Frames") of RFC 6325.
>
> There is really no substitute for having a general familiarity with
> RFC 6325 in understanding this document. Although I have seen IESG
> members criticize statements such as "Familiarity with X is assumed."
> when X is a normative reference, on the grounds that familiarity with
> all normative references is automatically assumed, perhaps some such
> statement is warranted in this case.
>
> In addressing both of your issues here, the first paragraph of Section
> 1.1 could be changed as follows:
>
> OLD
>    This document updates [RFC6325], the TRILL base specification,
>    replacing the description of the ESADI protocol in Section 4.2.5 of
>    [RFC6325], providing more detail, and prevailing over [RFC6325] where
>    they conflict. The changes are summarized in Appendix A. These
>    changes are not backwards compatible because, among other things,
>    they change the format of ESADI-LSPs.
> NEW
>    This document updates [RFC6325], the TRILL base protocol
>    specification, obsoleting and replacing the description of the
>    ESADI protocol (Section 4.2.5 of [RFC6325] including all
>    subsections), providing more detail on ESADI, updating other ESADI
>    related sections of [RFC6325], and prevailing over [RFC6325] in any
>    case where they conflict. For this reason, familiarity with
>    [RFC6325] is particularly assumed.  These changes are not backwards
>    compatible because they change the format of ESADI-LSPs to
>    substantially increase the amount of information that can be
>    carried. These changes are further discussed in Appendix A.
>
>
> > Minor issues:
> >
> > I don't understand the discussion in section 2 of it being "an
> > implementation decision how independent the multiple ESADI instances
> > at an RBridge are" in light of the clear statement that "the ESADI
> > update process operates separately for each ESADI instance."  The
> > example given involves database structure considerations that are
> > specific to the node implementation and do not affect the independent
> > updates for each ESADI instance.  There may not be an actual
> > technical problem here, but at least the first chunk of text quoted
> > in this paragraph of the review needs to be rewritten.
>
> Two things motivated the text you cite in Section 2: (1) ESADI uses
> multiple instances of the flooding process for the purpose of limiting
> the flooding to the TRILL switches that have expressed interest in a
> particular Data Label. RFC 6822 specifies a different type of IS-IS
> "instance" and there is some implication in 6822 of fault and
> performance isolation between RFC 6822 instances. Although this
> document says its instances are not the same as RFC 6822 instances,
> someone might still have the impression that ESADI instances are
> necessarily to be implemented inside a TRILL switch is a highly
> isolated manner. This text is to emphasize that the extent to which
> the execution of different ESADI instances are isolated within a TRILL
> switch is an implementation decision. (2) Perhaps a symptom of item 1:
> in early discussions of ESADI, there were multiple complaints that
> maintaining 'so many different link state databases' in a TRILL switch
> would be an undue burden. So the text here specifically mentions that
> the databases for all ESADI instances at a TRILL switch can be merged
> (with an appropriate marker in each record saying which instance it
> belongs to).
>
> While the IETF generally standardizes bits on the wire and not
> internal implementation details, the above concerns lead to these few
> sentences to dispel any false impression.  I do not really see how
> there can be much confusion since the draft also says, as your point
> out, "But the ESADI update process operates separately for each ESADI
> instance and independently from the TRILL IS-IS update process.". I
> suggest the following change:
>
> OLD
>    It is an implementation decision how independent the multiple ESADI
>    instances at an RBridge are.
> NEW
>    This specification does not constrain how coupled or independent
>    the multiple ESADI instances are in their implementation internal
>    to an RBridge.
>
>
> > Also in Section 2:
> >
> >    ESADI does no routing so there is no reason for pseudo-nodes in ESAD=
I
> >    and none are created.
> >
> > Need to explain what a pseudo-node is before this sentence.
>
> I do not think this document is the right place for a detailed
> explanation of pseudo-nodes. How about changing to the following:
>
>    ESADI does no routing calculations so there is no reason for
>    pseudo-nodes in ESADI and none are created (Pseudo-nodes [IS-IS]
>    are a construct for optimizing routing calculations.)
>
>
> > p.9, Figure 2 - explain how the receiver determines whether the inner
> > Ethernet header contains a VLAN tag or FGL.  This also applies to Figur=
e
> > 3 on p.10.
>
> I'm not sure this draft is the place for a detailed explanation but I
> have no problem adding the already existing reference "[RFCfgl]" to
> both figures right after where they say "VLAN or FGL Data Label (4 or
> 8 bytes)". That referenced document [RFCfgl], which is in the RFC
> Editor's queue, explains this.
>
>
> > p.10, Section 2.1:
> >
> >    All transit RBridges forward ESADI packets as if they were ordinary
> >    TRILL Data packets.
> >
> > Need to explain what a "transit" RBridge is.  Between this and the
> > above pseudo-node comment, I suggest adding an overview of the
> > TRILL protocol to the start of Section 2.
>
> How about just eliminating the word "transit", which I don't think is
> necessary, and changing the sentence in question to
>
>      All RBridges forward ESADI packets as if they were ordinary TRILL
>      Data packets [RFC6325].
>
>
> > p.11, Section 2.1:
> >
> >    No "routing" computation or routing decisions ever have to be
> >    performed by ESADI.
> >
> > What is a ' "routing" computation' ??  This should be rephrased to
> > contrast to what the non-ESADI TRILL usage of IS-IS does.
>
> How about the following change:
>
> OLD
>    No "routing" computation or routing decisions ever have to be
>    performed by ESADI.
> NEW
>    No "routing" calculation (least cost path or distribution tree
>    construction) ever has to be performed by ESADI.
>
>
> > p.12, Section 2.2:
> >
> >    If a VLAN or FGL ID
> >    field within an ESADI-LSP PDU does include a value, that field's
> >    contents is ignored.
> >
> > This looks like it's an important requirement, so:
> >          "is ignored" -> "MUST be ignored"
>
> OK.
>
>
> > p.13, Section 3
> >
> >   "SNPA/MAC address"
> >    is not considered in this tie breaking and there is no "Port ID".
> >
> > This is contrasting ESADI tie-breaking to a tie-breaking procedure
> > that I'd guess is specified in another document; that needs to be
> > explained, along with a reference to that document, preferably with
> > the section number where the other tie-breaking procedure is
> > specified.
>
> The other document is [rfc6327bis] which is referenced.  However, this
> reference can be made clearer. How about
>
> OLD
>    Generally speaking, the DRB election on the ESADI virtual link (see
>    Section 2.1) operates similarly to a TRILL IS-IS broadcast link
>    [rfc6327bis] with the following exceptions:
> NEW
>    Generally speaking, the DRB election on the ESADI virtual link (see
>    Section 2.1) operates similarly to the DRB election on a TRILL
>    IS-IS broadcast link, as described in Section 4.2.1 ("DRB Election
>    Details") of [rfc6327bis], with the following exceptions:
>
>
> > Section 6 - explain where the 1470 byte number in the third
> > paragraph comes from.
>
> How about adding the following at the end of the relevant paragraph,
> just before the Section 6.1 header:
>
>    (As stated in Section 4.3.1 of [RFC6325], 1470 bytes was chosen to
>    make it extremely unlikely that a TRILL control packet, even with
>    reasonable additional headers, tags, and/or encapsulation, would
>    encounter MTU problems on an inter-RBridge link.)
>
>
> > Section 8 - more should be said on whether/when the Authentication
> > TLV should be used when ESADI conveys information from an
> > authenticated registration. In particular, if this recommendation
> > for usage of the Authentication TLV with information from an
> > authenticated registration usage is not a "SHOULD" or "MUST", an
> > explanation is in order.
>
> Consider the following: we have a network with secure trunk links
> between trusted TRILL switches but in some cases those switches are
> connected to end stations via 802.11 Wi-Fi links. It seems entirely
> reasonable to use 802.11 authentication in allowing end stations to
> connect due to the inherent accessiblity of radio links, but might not
> be necessary to use authentication on ESADI PDUs between TRILL
> switches.
>
> In any case, if there is a concern about forged packets, the IS-IS
> LSPs in the TRILL campus should be authenticated and, in that case,
> the ESADI PDUs will be authenticated by default as provided in Section
> 6.3 of this draft.
>
> How about adding a new paragraph to Section 8, between the current
> first and second paragraphs, incorporating the above, such as:
>
>    However, there may be cases where it is not necessary to
>    authenticate ESADI PDUs despite using authenticated registration
>    for end stations.  For example a TRILL campus with secure RBridges
>    and inter-RBridge links configured as trunks but some end stations
>    connected via 802.11 wireless access links might use 802.11
>    authentication for the connection of such end staions but not
>    necessarily authenticate ESDAI PDUs. Note that if the IS-IS LSPs in
>    a TRILL campus are authenticated, perhaps due to a concern about
>    forged packets, the ESADI PDUs will be authenticated by default as
>    provided in Section 6.3.
>
>
> > Nits/editorial comments:
> >
> > There are lots of acronyms that are not expanded on first use,
> > defined in the terminology section, or otherwise explained, e.g.,
> > DRB, Sz, CSNP, PSNP. It may be ok to point to terminology/acronym
> > definitions in RFC 6325.
>
> I believe these are all defined/expanded in RFC 6325 but it would
> still be a good idea to expand them on first use in this document.
>
>
> > Last sentence on p.8:
> >
> > OLD
> >    The outer VLAN tag will not be present if it was stripped by
> >    an Ethernet port out of which the packet was sent.
> > NEW
> >    The outer VLAN tag will not be present for a packet on an
> >    an Ethernet link that does not use VLAN tags.
>
> Well, whether or not any particular Ethernet frame carrying a TRILL
> Data packet is VLAN tagged or not depends on whether the port sending
> that frame is configured to send it tagged or untagged. There is no
> requirement or enforcement mechanism that all the ports on that
> Ethernet link be identically configured in this regard. So I do not
> consider it to be a property of the link.
>
>
> Also, Appendix A item 1: replces -> replaces
>
> 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
>
> > idnits 2.13.01 got confused by the Section 4.6.2.2 reference to
> > RFC 6325 in Section 4.1, and thought 4.6.2.2 was an IPv4 address -
> > this is not a problem.
> >
> > idnits also warned about possible pre-RFC5378 (2008) content.  This
> > is probably not a problem, but please check with your AD.
> >
> > 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
> > ----------------------------------------------------


From nobody Wed Apr  9 05:41:13 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 827EE1A019E; Wed,  9 Apr 2014 05:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.772
X-Spam-Level: 
X-Spam-Status: No, score=-0.772 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.272] 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 CsNBC1rT8S4t; Wed,  9 Apr 2014 05:41:07 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A8F401A0136; Wed,  9 Apr 2014 05:41:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5160E2CC48; Wed,  9 Apr 2014 15:41:05 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WghUjvQBw7Oh; Wed,  9 Apr 2014 15:41:04 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3BA752CCBE; Wed,  9 Apr 2014 15:41:04 +0300 (EEST)
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: <CABkgnnVVQCAz=ixeR04rc75Vc-rL2JFQcjT0-hX_UCL-c=FGjQ@mail.gmail.com>
Date: Wed, 9 Apr 2014 14:41:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F92FD08-1636-48C0-9634-8806E9F577FF@piuha.net>
References: <CABkgnnVVQCAz=ixeR04rc75Vc-rL2JFQcjT0-hX_UCL-c=FGjQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/8LBeOsqEgukGdgb_ASttoD5jEK4
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IESG IESG <iesg@ietf.org>, draft-drage-sipping-rfc3455bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-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: Wed, 09 Apr 2014 12:41:10 -0000

Thanks for the review, Martin. Have there been any responses or changes =
based on your comments? I do not see the document version having =
changed...

Jari

On Feb 28, 2014, at 1:43 AM, Martin Thomson <martin.thomson@gmail.com> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-drage-sipping-rfc3455bis-13
> Reviewer: Martin Thomson
> Review Date: 2014-02-27
> IETF LC End Date: 2014-03-14
> IESG Telechat date: (if known)
>=20
> Summary: I find it strange that this 3GPP document is being published
> on the standards track.  But since it's a -bis there is clearly
> precedent, and it is otherwise sound.
>=20
> Major issues:
>=20
> This document doesn't include enough information for me to some of the
> headers.  For example, there isn't enough information in the document
> to allow me to interpret the contents of cgi-3gpp:
>          cgi-3gpp     =3D "cgi-3gpp" EQUAL (token / quoted-string)
> (I pick on P-Access-Network-Info, because I'm somewhat familiar with =
it.)
>=20
> This can probably be addressed by the inclusion of appropriate
> normative references.  I seem to recall there being a 3GPP TS that
> covered at least some of these.
>=20
> Minor issues:
>=20
> RFC 4244 is now obsolete, see 7044.  (related nit: Change log entry #2
> seems quite defensive, unnecessarily so.  This document only needs to
> define P-Called-Party-ID, and reference History-Info as an alternative
> mechanism.)
>=20
> Change log entry #5, mentions a shortcoming of 3455 (no registry for
> access network types), but the draft does nothing about it.  It seems
> to be propagating the mistake it notes.
>=20
> A lot has happened since RFC 3455 was published.  The privacy
> considerations around the use of P-Access-Network-Info are unchanged
> from their pre-Geopriv form.  In particular, I find the UA knowledge
> part to be problematic; Geopriv definitions can probably help here.
>=20
> S6.1 P-Associated-URI is a powerful linkability vector, which could be
> a far more serious privacy leak than the text implies.  The following
> seems like good advice, but is not sufficient:
>=20
>   An eavesdropper could possibly collect the list of identities a user
>   is registered.  This can have privacy implications.  To mitigate =
this
>   problem, this extension SHOULD only be used in a secured =
environment,
>   where encryption of SIP messages is provided either end-to-end or
>   hop-by-hop.
>=20
> You also have to trust the other end of the hop with the information.
> I think that's implicit, but probably needs to be stated.
>=20
> S6.4  This claim sounds false to me:
>=20
>   However, there
>   are no security problems resulting from a UA inserting incorrect
>   information.  Networks providing services based on the information
>   carried in the P-Access-Network-Info header field will therefore =
need
>   to trust the UA sending the information.  A rogue UA sending false
>   access network information will do no more harm than to restrict the
>   user from using certain services.
>=20
> Any parameter whereby changing it can cause loss of service is likely
> to be true in the inverse.  The draft makes no claims that would make
> me believe otherwise.
>=20
> Nits/editorial comments:
>=20
> S1 Having the disclaimer as the first section is a little strange.  I
> don't know what it is disclaiming yet.
>=20
> S1, S3 It looks like a few characters are missing from these sections:
> "trust.These", "environment The", "[RFC3455]   This"
>=20
> The change log contains a lot of normative language.  I expected to
> see pointers to changes, and maybe some justification, but items
> include normative-sounding text and no pointers(7), other contain
> pointers and duplicate text (3&4)
>=20
> Change log #6 notes the removal of a field; given that this is
> extensible, why not just mark the CDMA 2000 item deprecated instead of
> removing it?
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr  9 06:56:33 2014
Return-Path: <eric@notcom.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 F24D51A02FC for <gen-art@ietfa.amsl.com>; Wed,  9 Apr 2014 06:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.722
X-Spam-Level: *
X-Spam-Status: No, score=1.722 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, GB_SUMOF=1, RCVD_IN_DNSWL_LOW=-0.7] 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 xfdAutjNaSTL for <gen-art@ietfa.amsl.com>; Wed,  9 Apr 2014 06:52:03 -0700 (PDT)
Received: from mail-yk0-f170.google.com (mail-yk0-f170.google.com [209.85.160.170]) by ietfa.amsl.com (Postfix) with ESMTP id 349E71A02C6 for <gen-art@ietf.org>; Wed,  9 Apr 2014 06:52:03 -0700 (PDT)
Received: by mail-yk0-f170.google.com with SMTP id 9so2189223ykp.29 for <gen-art@ietf.org>; Wed, 09 Apr 2014 06:52:02 -0700 (PDT)
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=Nghw9m9iCUAW9xdpyS/eF1/MuY1rNXHhC0GAulJRuTw=; b=MIA3AHo+70OUc387QJ8hnnTUyJTtUWBODfPDICodJwaM1q6LInnJa9Mh/7SQJCA2ss GlS90ISAMfyoenmasLEqRSyu78YTMJIo/aGF9IbttRVjWCfp2MOxgp29rNYPjTMler5g 0KMxXpxTfweLiRr14wrexWFiQuM9X5THmxhjuSl3DYEl0Zrtll3wxkYaTyxQsbrcwtnr dhvZm0baTU2MxdBdyIkSuLCgerQ6mjfBNNaSR82LC7W5aHuLFomYR9h1gpY5YBnUNWlk VT+OAQ9ZDCiND35JNg0m+X/o8Umo+ylND60+NhFPTnG4HdHtsAZAc8Lp3b4jz9zKoXGT /DcA==
X-Gm-Message-State: ALoCoQkOrs9BIMSh+Q4R/HfKbn+Y72sK8cEsa1s/gNsqw7m3Qgsb0PCtVjRsPE5A0ULbDv04a1il
MIME-Version: 1.0
X-Received: by 10.236.116.99 with SMTP id f63mr14097976yhh.10.1397051522490; Wed, 09 Apr 2014 06:52:02 -0700 (PDT)
Received: by 10.170.60.5 with HTTP; Wed, 9 Apr 2014 06:52:02 -0700 (PDT)
In-Reply-To: <1396637884.15324.14300.camel@mightyatom>
References: <1396637884.15324.14300.camel@mightyatom>
Date: Wed, 9 Apr 2014 09:52:02 -0400
Message-ID: <CA+97oKMXCeu9BcWKuUbKU2OvdZ+0s9bn1oTxZ-K8ac6hDMZXfQ@mail.gmail.com>
From: Eric Osborne <eric@notcom.com>
To: Elwyn Davies <elwynd@folly.org.uk>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/cRIMFlVyQBiwBT7xSVMUNFRW7dk
X-Mailman-Approved-At: Wed, 09 Apr 2014 06:56:31 -0700
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-mpls-psc-updates.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-mpls-psc-updates-03.txt (review type corrected).
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, 09 Apr 2014 13:52:07 -0000

Hi Elwyn-

  Thanks for the comments.  I'll make sure they're addressed before
publication.  I also have other comments but they're along the same
lines as yours, and those will be integrated too.



eric


On Fri, Apr 4, 2014 at 2:58 PM, Elwyn Davies <elwynd@folly.org.uk> wrote:
> (Sorry...  got the wrong review type in the subject line).
>
> I am the assigned Gen-ART 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-psc-updates-03.txt
> Reviewer: Elwyn Davies
> Review Date: 4 April 2014
> IETF LC End Date: 2014-04-09
> IESG Telechat date: (if known) -
>
> Summary:
> Almost ready.
>
> Major Issues:
>
> Minor Issues:
> General:
> As discussed during
> Last Call/IETF review of draft-ietf-mpls-tp-psc-itu, RFC 6378 is missing
> some details regarding
> - the on-the-wire format of messages
> - detection of and behaviour in the event of reception of malformed
> messages
> - behaviour in the event of receiving unknown TLV items
> - behaviour in the event or receiving unexpected TLV items in a
> particular mode.
>
> Specifics:
> On-the-wire format:
> - The encoding of the TLV Length field is not specified (unsigned binary
> integer in network bit order).
> - The encoding of the individual TLV length and Type fields in s2 should
> also be specified (unsigned binary integer in network bit order).
> - The value of TLV Length should be more precisely specified.  Suggest:
>   The TLV Length is the sum of the lengths of all TLVs in the message,
>   where the length of a TLV is the sum of the lengths of the three
>   TLV fields, i.e., the the length of the value field + 4.
>
> Malformed messages check:
> - Check values of fields prior to TLV Length are consistent with s4.2 of
> RFC 6378.
> - Check overall length of message matches value in TLV Length + 12.
> - Check Sum of lengths of TLVs matches value in TLV Length.
> - Check all TLV types received are recognized.
>
> Behaviour in the event of receiving a malformed message:
> - There has been discussion of appropriate behaviour on the MPLS mailing
> list.
>
> Behaviour in the event of receiving a well-formed but inappropriate TLV
> in a message:
> - This needs to be specified. (might be mode specific)
>
> Nits/Editorial Comments:
> General: s/i.e. /i.e., /g, s/e.g. /e.g., /g
>
> Abstract/s1: Make the count of changes consistent (four/five currently).
> Might be better just to say 'a number of changes' and leave the reader
> to count.
>
> s1: Since the number of items has grown to five and maybe six (depending
> on how the above changes are inserted), it would helpful to link the
> categorization to the actual section numbers.)
>
> s2: It would be good to have the conventional picture here - just grab
> the one from draft-mpls-tp-psc-itu.
>
> s2, Value field: Better to say that this has the number of octets
> specified in the length field rather than talking about multiples of 4
> again.  The discussion of padding seems superfluous.
>
> s4, next to last para: Should 'A remote No Request message SHALL be ignored' be
> 'A remote NR message SHALL be ignored' for consistency?
>
> s5,para 8: s/In both cases the request which was driving/In both cases the request that was driving/
>
> s6: It might be worth pointing out that extensions of PSC (like tp-psc-itu) may
> introcuce additional capabilities and state that it is up to these sepcifications to
> say how capability mismatch in this areas is/are handled.
>
>
>
>
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
>


From nobody Wed Apr  9 07:12:26 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 AAAE81A031B; Wed,  9 Apr 2014 07:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 vhbMOTHYZzDD; Wed,  9 Apr 2014 07:12:16 -0700 (PDT)
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 8C7521A030F; Wed,  9 Apr 2014 07:12:16 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id j17so2786963oag.28 for <multiple recipients>; Wed, 09 Apr 2014 07:12:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=/NIGo8WZTEy/5SnGfqjh8vN6IGks3+JRMpkOo2m6gmA=; b=k7EZ205U5NvuomikPMsQ0+ZoMZCWleQKLuwCQUcrBj8CD9HRPntQSBRdHgbKnN905Y taCP/Os9jLHAJwg61QEOgHtIOkZamfMG2owlm21uWN0RL0tWPjf1KAVPX2z4A4PDNdDX Hnez7ThQaX3mIRHPkcxxRWF+15NE9+g0YpQkgdzeitxFtmnQJHSlxleHgwX8llhW8frW QAyHYFp1jvjBQRIY4ZkZZ5zWGCtMAUHzqFNcgl5Dap18TMUNPL+dgxHmXv97Tt5wG8m9 XVGdEn6sfUkTVxKf12ufxi4/qCnvj/5XM5MXGMSshDKS9TWBM8hT44+MltngYgqOPQQg pjBQ==
X-Received: by 10.182.38.199 with SMTP id i7mr1145673obk.68.1397052735937; Wed, 09 Apr 2014 07:12:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.25.41 with HTTP; Wed, 9 Apr 2014 07:11:55 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C1D15CD@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C0ADDF7@MX15A.corp.emc.com> <CAF4+nEEL1LUxBEaGyUxEHNWb=fMgu2zVAuHqiSf64d0ZW=w3ng@mail.gmail.com> <8D3D17ACE214DC429325B2B98F3AE712076C1D15CD@MX15A.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 9 Apr 2014 10:11:55 -0400
Message-ID: <CAF4+nEGDK+=sdmQqs=Qx=2jZb8KAS5h6XvAQJAtmMBF_WC8z1w@mail.gmail.com>
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/xo-0SsYkZhiRPTCLZ7ltXSSNEGU
Cc: "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ostokes@extremenetworks.com" <ostokes@extremenetworks.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-esadi-06.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, 09 Apr 2014 14:12:20 -0000

Hi David,

On Tue, Apr 8, 2014 at 4:58 PM, Black, David <david.black@emc.com> wrote:
> Donald,
>
> Thank you for the extensive comments on the review.  I'll summarize here
> rather than add more text inline.  I'm fine with the proposed course of
> action for anything not mentioned here:

OK. It is good sign when the amount of text being written with each
exchange starts to shrink rather than grow :-)

> [1] Absence of backwards compatibility:
>         - The Appendix A changes look good.
>         - The "limited deployment" (and presumably also "limited
>                 implementation") rationale for no backwards compatibility
>                 should be included in Section 1.1.  This merits additional
>                 text in Section 1.1

OK. We could add a few more words to the proposed new version of the
first paragraph in Section 1.1 as follows:

NEWER
   This document updates [RFC6325], the TRILL base protocol
   specification, obsoleting and replacing the description of the
   ESADI protocol (Section 4.2.5 of [RFC6325] including all
   subsections), providing more detail on ESADI, updating other ESADI
   related sections of [RFC6325], and prevailing over [RFC6325] in any
   case where they conflict. For this reason, familiarity with
   [RFC6325] is particularly assumed.  These changes include a change
   to the format of ESADI-LSPs that is not backwards compatible; this
   change is justified by the substantially increased amount of
   information that can be carried in light of the very limited, if
   any, deployment of [RFC6325] ESADI. These changes are further
   discussed in Appendix A.

> [2] Structure of draft wrt RFC 6325:
>         I think the rest of the proposed changes to Section 1.1 are reasonable:
>
>         - Appendix A does explain what's changed.  I would have liked to see
>                 more formality/precision in Section 1.1, but that's a matter of
>                 editorial taste that I'll leave to the authors.  The proposed
>                 addition of a forward reference to Appendix A will definitely
>                 help.
>         - The proposed addition of an explicit statement about expecting
>                 familiarity with RFC 6325 in Section 1.1 will also help.
>
> [3] Independence of ESADI instances: What bothered me was the absence of
> a strong mention of implementation structure - I have some new text to
> suggest to strengthen that point:
>
> OLD
>    It is an implementation decision how independent the multiple ESADI
>    instances at an RBridge are.
> NEW
>    Multiple ESADI instances may share implementation components within
>    an RBridge as long as that sharing preserves the independent operation
>    of each instance of the ESADI protocol.
>
> Then the link state database example that follows makes more sense,
> at least to me.

I'm OK with the wording you suggest.

> [4] Section 8  Authentication TLV usage discussion.
>
>> How about adding a new paragraph to Section 8, between the current
>> first and second paragraphs, incorporating the above, such as:
>>
>>    However, there may be cases where it is not necessary to
>>    authenticate ESADI PDUs despite using authenticated registration
>>    for end stations.  For example a TRILL campus with secure RBridges
>>    and inter-RBridge links configured as trunks but some end stations
>>    connected via 802.11 wireless access links might use 802.11
>>    authentication for the connection of such end stations but not
>>    necessarily authenticate ESADI PDUs. Note that if the IS-IS LSPs in
>>    a TRILL campus are authenticated, perhaps due to a concern about
>>    forged packets, the ESADI PDUs will be authenticated by default as
>>    provided in Section 6.3.
>
> These seems a bit descriptive, with most of the text describing a
> specific example.  I'm looking for some more prescriptive guidance
> about what SHOULD (or perhaps should?) be the case when the Authentication
> TLV is not used with authenticated registration.

Well, a more general statement of the criteria for such cases could be
added such as below:

   However, there may be cases where it is not necessary to
   authenticate ESADI PDUs despite using authenticated registration
   for end stations because of a significant threat of forged packets
   on end station links when that threat is not present for
   inter-RBridge trunks.  For example a TRILL campus with secure
   RBridges and inter-RBridge links configured as trunks but some end
   stations connected via 802.11 wireless access links might use
   802.11 authentication for the connection of such end stations but
   not necessarily authenticate ESADI PDUs. Note that if the IS-IS
   LSPs in a TRILL campus are authenticated, perhaps due to a concern
   about forged packets, the ESADI PDUs will be authenticated by
   default as provided in Section 6.3.

> [5] VLAN tag presence (nit)
>
>> > Last sentence on p.8:
>> >
>> > OLD
>> >    The outer VLAN tag will not be present if it was stripped by
>> >    an Ethernet port out of which the packet was sent.
>> > NEW
>> >    The outer VLAN tag will not be present for a packet on an
>> >    an Ethernet link that does not use VLAN tags.
>
> I don't think the word "stripped" is right, as it would not apply if
> the tag wasn't present in the first place, although I also agree with
> your comment that my suggested use of "link" isn't right, either.
>
> Here's another suggestion:
>
>     The outer VLAN tag will not be present if it was not included
>     by the Ethernet port that sent the packet.

I agree that "stripped" is not a very good word to use. I'm OK with
your suggested wording.

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

> Thanks,
> --David
>
>> -----Original Message-----
>> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
>> Sent: Saturday, April 05, 2014 11:23 AM
>> To: Black, David
>> Cc: zhai.hongjun@zte.com.cn; hu.fangwei@zte.com.cn; Radia@alum.mit.edu;
>> ostokes@extremenetworks.com; General Area Review Team (gen-art@ietf.org);
>> trill@ietf.org; ietf@ietf.org
>> Subject: Re: Gen-ART review of draft-ietf-trill-esadi-06.txt
>>
>> Hi David,
>>
>> Thanks for this very thorough review. See my responses below:
>>
>> On Sat, Mar 29, 2014 at 10:23 PM, Black, David <david.black@emc.com> wrote:
>> >
>> > I am the assigned Gen-ART reviewer for this draft. For background on
>> > Gen-ART, please see the FAQ at
>> >
>> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>> >
>> > Please resolve these comments along with any other Last Call comments
>> > you may receive.
>> >
>> > Document: draft-ietf-trill-esadi-06.txt
>> > Reviewer: David L. Black
>> > Review Date: March 29, 2014
>> > IETF LC End Date: April 1, 2014
>> >
>> > Summary: This draft is on the right track, but has open issues
>> > described in the review.
>> >
>> > This draft revises the ESADI specification for TRILL from its
>> > original form in RFC 6325.
>> >
>> > Major issues:
>> >
>> > The draft changes ESADI in a non-backwards-compatible fashion from
>> > its original specification in RFC 6325, but does not explain why this
>> > is ok.  That explanation needs to be provided, and if implementations
>> > of ESADI as originally specified in RFC 6325 exist, that explanation
>> > needs to encompass coexistence and interoperability (or lack thereof)
>> > with such implementations.  That explanation probably belongs in
>> > Section 1.1, and could be expanded upon in Appendix A.
>>
>> This was a considered decision of the TRILL WG. At least since the -02
>> version in February 2013, the ESADI WG draft has had ESADI-LSP
>> provisions that were incompatible with RFC 6325 ESADI for the purpose
>> of accomodating orders of magnitude more LSP fragments. This text in
>> the draft, which originally used a somewhat ad hoc change from IS-IS
>> LSPs to accomodate additional fragments, was posted to the list
>> without objection before being incorporated. Since a standard IS-IS
>> way of doing this was later in process in the ISIS WG, the ESADI draft
>> was changed to follow this more standard way of providing for more LSP
>> fragments and a new WG Last Call done in the TRILL WG specifically on
>> this issue. See
>>
>> http://www.ietf.org/mail-archive/web/trill/current/msg06037.html
>> http://www.ietf.org/mail-archive/web/trill/current/msg06009.html
>>
>> In Appendix A (Changes to [RFC6325]), how about replacing items 2 and
>> 3 in the list as follows (includes fixing a typo in item 3):
>>
>> OLD
>>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
>>       is changed from the base IS-IS format to the Extended Level 1
>>       Circuit Scoped format in [FS-LSP].
>> NEW
>>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
>>       is changed from the base IS-IS format to the Extended Level 1
>>       Circuit Scoped format (E-L1CS) specified in [FS-LSP]. This
>>       change is not backwards compatible with [RFC6325]. It is made in
>>       light of (a) the very limited, if any, deployment of [RFC6325]
>>       ESADI, and (b) the 256 times greater information carrying
>>       capacity of the E-L1CS format compared with the base IS-IS
>>       format. It is anticipated that this greater carrying capacity
>>       will be needed, under some circumstances, to carry end station
>>       addressing information or other information that is added to
>>       ESADI in the future.
>> OLD
>>    3. Unicasting of ESADI PDUs is supported including replacing Section
>>       4.6.2.2 of [RFC6325] with the next text give in Section 4.1 of
>>       this document.
>> NEW
>>    3. Unicasting of ESADI PDUs is optionally supported including
>>       replacing Section 4.6.2.2 of [RFC6325] with the new text give in
>>       Section 4.1 of this document. This unicast support is backwards
>>       compatible because it is only used when the recipient RBridge
>>       signals its support.
>>
>> See possible replacement below for the first paragraph of Section 1.1
>> that includes a condensed version of this additional material
>> concerning backwards non-compatibility.
>>
>> > Overall, this draft is not self-contained - to a significant extent,
>> > it is written as if it were effectively a long collection of errata
>> > to the ESADI specification in RFC 6325. That makes it difficult to
>> > understand - it would be better if this draft completely obsoleted
>> > and replaced the ESADI specification in RFC 6325, describing its
>> > changes, instead of providing specific text changes to portions of
>> > the RFC 6325 text.
>>
>> All of the changes to ESADI are described in Appendix A.
>>
>> If the ESADI related material in RFC 6325 was entirely contained in
>> one contiguous area of RFC 6325, it would have been easy to write this
>> draft as simply obsoleting and replacing that area of RFC 6325.  The
>> largest such monolithic block on ESADI in RFC 6325 is Section 4.2.5
>> (The TRILL ESADI Protocol), including its two subsections ("4.2.5.1
>> TRILL ESADI Participation" and "4.2.5.2 TRILL ESADI Information"). All
>> of that is obsoleted and replaced by this draft.  However, there are
>> other non-contiguous parts of RFC 6325 necessarily affected. For
>> example, Section 4.6 of RFC 6325 describes how to handle every
>> possible type of frame that might be received; since an ESADI PDU is
>> one such type of frame, it is necessary to change Section 4.6.2.2
>> ("TRILL ESADI Frames") of RFC 6325.
>>
>> There is really no substitute for having a general familiarity with
>> RFC 6325 in understanding this document. Although I have seen IESG
>> members criticize statements such as "Familiarity with X is assumed."
>> when X is a normative reference, on the grounds that familiarity with
>> all normative references is automatically assumed, perhaps some such
>> statement is warranted in this case.
>>
>> In addressing both of your issues here, the first paragraph of Section
>> 1.1 could be changed as follows:
>>
>> OLD
>>    This document updates [RFC6325], the TRILL base specification,
>>    replacing the description of the ESADI protocol in Section 4.2.5 of
>>    [RFC6325], providing more detail, and prevailing over [RFC6325] where
>>    they conflict. The changes are summarized in Appendix A. These
>>    changes are not backwards compatible because, among other things,
>>    they change the format of ESADI-LSPs.
>> NEW
>>    This document updates [RFC6325], the TRILL base protocol
>>    specification, obsoleting and replacing the description of the
>>    ESADI protocol (Section 4.2.5 of [RFC6325] including all
>>    subsections), providing more detail on ESADI, updating other ESADI
>>    related sections of [RFC6325], and prevailing over [RFC6325] in any
>>    case where they conflict. For this reason, familiarity with
>>    [RFC6325] is particularly assumed.  These changes are not backwards
>>    compatible because they change the format of ESADI-LSPs to
>>    substantially increase the amount of information that can be
>>    carried. These changes are further discussed in Appendix A.
>>
>>
>> > Minor issues:
>> >
>> > I don't understand the discussion in section 2 of it being "an
>> > implementation decision how independent the multiple ESADI instances
>> > at an RBridge are" in light of the clear statement that "the ESADI
>> > update process operates separately for each ESADI instance."  The
>> > example given involves database structure considerations that are
>> > specific to the node implementation and do not affect the independent
>> > updates for each ESADI instance.  There may not be an actual
>> > technical problem here, but at least the first chunk of text quoted
>> > in this paragraph of the review needs to be rewritten.
>>
>> Two things motivated the text you cite in Section 2: (1) ESADI uses
>> multiple instances of the flooding process for the purpose of limiting
>> the flooding to the TRILL switches that have expressed interest in a
>> particular Data Label. RFC 6822 specifies a different type of IS-IS
>> "instance" and there is some implication in 6822 of fault and
>> performance isolation between RFC 6822 instances. Although this
>> document says its instances are not the same as RFC 6822 instances,
>> someone might still have the impression that ESADI instances are
>> necessarily to be implemented inside a TRILL switch is a highly
>> isolated manner. This text is to emphasize that the extent to which
>> the execution of different ESADI instances are isolated within a TRILL
>> switch is an implementation decision. (2) Perhaps a symptom of item 1:
>> in early discussions of ESADI, there were multiple complaints that
>> maintaining 'so many different link state databases' in a TRILL switch
>> would be an undue burden. So the text here specifically mentions that
>> the databases for all ESADI instances at a TRILL switch can be merged
>> (with an appropriate marker in each record saying which instance it
>> belongs to).
>>
>> While the IETF generally standardizes bits on the wire and not
>> internal implementation details, the above concerns lead to these few
>> sentences to dispel any false impression.  I do not really see how
>> there can be much confusion since the draft also says, as your point
>> out, "But the ESADI update process operates separately for each ESADI
>> instance and independently from the TRILL IS-IS update process.". I
>> suggest the following change:
>>
>> OLD
>>    It is an implementation decision how independent the multiple ESADI
>>    instances at an RBridge are.
>> NEW
>>    This specification does not constrain how coupled or independent
>>    the multiple ESADI instances are in their implementation internal
>>    to an RBridge.
>>
>>
>> > Also in Section 2:
>> >
>> >    ESADI does no routing so there is no reason for pseudo-nodes in ESADI
>> >    and none are created.
>> >
>> > Need to explain what a pseudo-node is before this sentence.
>>
>> I do not think this document is the right place for a detailed
>> explanation of pseudo-nodes. How about changing to the following:
>>
>>    ESADI does no routing calculations so there is no reason for
>>    pseudo-nodes in ESADI and none are created (Pseudo-nodes [IS-IS]
>>    are a construct for optimizing routing calculations.)
>>
>>
>> > p.9, Figure 2 - explain how the receiver determines whether the inner
>> > Ethernet header contains a VLAN tag or FGL.  This also applies to Figure
>> > 3 on p.10.
>>
>> I'm not sure this draft is the place for a detailed explanation but I
>> have no problem adding the already existing reference "[RFCfgl]" to
>> both figures right after where they say "VLAN or FGL Data Label (4 or
>> 8 bytes)". That referenced document [RFCfgl], which is in the RFC
>> Editor's queue, explains this.
>>
>>
>> > p.10, Section 2.1:
>> >
>> >    All transit RBridges forward ESADI packets as if they were ordinary
>> >    TRILL Data packets.
>> >
>> > Need to explain what a "transit" RBridge is.  Between this and the
>> > above pseudo-node comment, I suggest adding an overview of the
>> > TRILL protocol to the start of Section 2.
>>
>> How about just eliminating the word "transit", which I don't think is
>> necessary, and changing the sentence in question to
>>
>>      All RBridges forward ESADI packets as if they were ordinary TRILL
>>      Data packets [RFC6325].
>>
>>
>> > p.11, Section 2.1:
>> >
>> >    No "routing" computation or routing decisions ever have to be
>> >    performed by ESADI.
>> >
>> > What is a ' "routing" computation' ??  This should be rephrased to
>> > contrast to what the non-ESADI TRILL usage of IS-IS does.
>>
>> How about the following change:
>>
>> OLD
>>    No "routing" computation or routing decisions ever have to be
>>    performed by ESADI.
>> NEW
>>    No "routing" calculation (least cost path or distribution tree
>>    construction) ever has to be performed by ESADI.
>>
>>
>> > p.12, Section 2.2:
>> >
>> >    If a VLAN or FGL ID
>> >    field within an ESADI-LSP PDU does include a value, that field's
>> >    contents is ignored.
>> >
>> > This looks like it's an important requirement, so:
>> >          "is ignored" -> "MUST be ignored"
>>
>> OK.
>>
>>
>> > p.13, Section 3
>> >
>> >   "SNPA/MAC address"
>> >    is not considered in this tie breaking and there is no "Port ID".
>> >
>> > This is contrasting ESADI tie-breaking to a tie-breaking procedure
>> > that I'd guess is specified in another document; that needs to be
>> > explained, along with a reference to that document, preferably with
>> > the section number where the other tie-breaking procedure is
>> > specified.
>>
>> The other document is [rfc6327bis] which is referenced.  However, this
>> reference can be made clearer. How about
>>
>> OLD
>>    Generally speaking, the DRB election on the ESADI virtual link (see
>>    Section 2.1) operates similarly to a TRILL IS-IS broadcast link
>>    [rfc6327bis] with the following exceptions:
>> NEW
>>    Generally speaking, the DRB election on the ESADI virtual link (see
>>    Section 2.1) operates similarly to the DRB election on a TRILL
>>    IS-IS broadcast link, as described in Section 4.2.1 ("DRB Election
>>    Details") of [rfc6327bis], with the following exceptions:
>>
>>
>> > Section 6 - explain where the 1470 byte number in the third
>> > paragraph comes from.
>>
>> How about adding the following at the end of the relevant paragraph,
>> just before the Section 6.1 header:
>>
>>    (As stated in Section 4.3.1 of [RFC6325], 1470 bytes was chosen to
>>    make it extremely unlikely that a TRILL control packet, even with
>>    reasonable additional headers, tags, and/or encapsulation, would
>>    encounter MTU problems on an inter-RBridge link.)
>>
>>
>> > Section 8 - more should be said on whether/when the Authentication
>> > TLV should be used when ESADI conveys information from an
>> > authenticated registration. In particular, if this recommendation
>> > for usage of the Authentication TLV with information from an
>> > authenticated registration usage is not a "SHOULD" or "MUST", an
>> > explanation is in order.
>>
>> Consider the following: we have a network with secure trunk links
>> between trusted TRILL switches but in some cases those switches are
>> connected to end stations via 802.11 Wi-Fi links. It seems entirely
>> reasonable to use 802.11 authentication in allowing end stations to
>> connect due to the inherent accessiblity of radio links, but might not
>> be necessary to use authentication on ESADI PDUs between TRILL
>> switches.
>>
>> In any case, if there is a concern about forged packets, the IS-IS
>> LSPs in the TRILL campus should be authenticated and, in that case,
>> the ESADI PDUs will be authenticated by default as provided in Section
>> 6.3 of this draft.
>>
>> How about adding a new paragraph to Section 8, between the current
>> first and second paragraphs, incorporating the above, such as:
>>
>>    However, there may be cases where it is not necessary to
>>    authenticate ESADI PDUs despite using authenticated registration
>>    for end stations.  For example a TRILL campus with secure RBridges
>>    and inter-RBridge links configured as trunks but some end stations
>>    connected via 802.11 wireless access links might use 802.11
>>    authentication for the connection of such end staions but not
>>    necessarily authenticate ESDAI PDUs. Note that if the IS-IS LSPs in
>>    a TRILL campus are authenticated, perhaps due to a concern about
>>    forged packets, the ESADI PDUs will be authenticated by default as
>>    provided in Section 6.3.
>>
>>
>> > Nits/editorial comments:
>> >
>> > There are lots of acronyms that are not expanded on first use,
>> > defined in the terminology section, or otherwise explained, e.g.,
>> > DRB, Sz, CSNP, PSNP. It may be ok to point to terminology/acronym
>> > definitions in RFC 6325.
>>
>> I believe these are all defined/expanded in RFC 6325 but it would
>> still be a good idea to expand them on first use in this document.
>>
>>
>> > Last sentence on p.8:
>> >
>> > OLD
>> >    The outer VLAN tag will not be present if it was stripped by
>> >    an Ethernet port out of which the packet was sent.
>> > NEW
>> >    The outer VLAN tag will not be present for a packet on an
>> >    an Ethernet link that does not use VLAN tags.
>>
>> Well, whether or not any particular Ethernet frame carrying a TRILL
>> Data packet is VLAN tagged or not depends on whether the port sending
>> that frame is configured to send it tagged or untagged. There is no
>> requirement or enforcement mechanism that all the ports on that
>> Ethernet link be identically configured in this regard. So I do not
>> consider it to be a property of the link.
>>
>>
>> Also, Appendix A item 1: replces -> replaces
>>
>> Thanks,
>> Donald
>> =============================
>>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>  155 Beaver Street, Milford, MA 01757 USA
>>  d3e3e3@gmail.com
>>
>> > idnits 2.13.01 got confused by the Section 4.6.2.2 reference to
>> > RFC 6325 in Section 4.1, and thought 4.6.2.2 was an IPv4 address -
>> > this is not a problem.
>> >
>> > idnits also warned about possible pre-RFC5378 (2008) content.  This
>> > is probably not a problem, but please check with your AD.
>> >
>> > 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
>> > ----------------------------------------------------
>


From nobody Wed Apr  9 07:49:58 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 189751A0381; Wed,  9 Apr 2014 07:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 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.272, 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 h4AEyxcnSWVG; Wed,  9 Apr 2014 07:49:08 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 819751A035C; Wed,  9 Apr 2014 07:49:04 -0700 (PDT)
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 s39Emuv0014241 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Apr 2014 10:48:56 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s39Emuv0014241
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1397054937; bh=Zd/PWnSobXXG+1rB6Sv7YqTLvvI=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=qm7xeSsqkmOp0Lpu588vlTX22tWwcSaNltBoWU+cwaAViO6gWk+y/Q2Zsb+ms4j/p j6Ou7+v4RVWRnNJJ2s5zT3WgN2T3zls28WHeLynLRLHHXgFsy74Bs+pMBL1aDUd9wf m4EdcjbrueorOteC5cfEOCSeaA6c1ymGItMKz+EU=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s39Emuv0014241
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd04.lss.emc.com (RSA Interceptor); Wed, 9 Apr 2014 07:48:33 -0700
Received: from mxhub34.corp.emc.com (mxhub34.corp.emc.com [10.254.93.82]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s39EmWx0005663 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 9 Apr 2014 10:48:32 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub34.corp.emc.com ([::1]) with mapi; Wed, 9 Apr 2014 10:48:31 -0400
From: "Black, David" <david.black@emc.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 9 Apr 2014 10:48:31 -0400
Thread-Topic: Gen-ART review of draft-ietf-trill-esadi-06.txt
Thread-Index: Ac9T/bw5MYNmhqmoQ322fGIxvjgcIgABHitQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C1D16FC@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C0ADDF7@MX15A.corp.emc.com> <CAF4+nEEL1LUxBEaGyUxEHNWb=fMgu2zVAuHqiSf64d0ZW=w3ng@mail.gmail.com> <8D3D17ACE214DC429325B2B98F3AE712076C1D15CD@MX15A.corp.emc.com> <CAF4+nEGDK+=sdmQqs=Qx=2jZb8KAS5h6XvAQJAtmMBF_WC8z1w@mail.gmail.com>
In-Reply-To: <CAF4+nEGDK+=sdmQqs=Qx=2jZb8KAS5h6XvAQJAtmMBF_WC8z1w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/P0Hk1W-JOjdYJ2N7-dGMeCFHEPE
Cc: "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ostokes@extremenetworks.com" <ostokes@extremenetworks.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-esadi-06.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, 09 Apr 2014 14:49:24 -0000

Hi Donald,

I think we're basically done here.

For [4], I would like to see stronger requirements in the security text, bu=
t
I can accept what's proposed below as an improvement.  Please ensure that a
good security reviewer (e.g., a sec-dir reviewer) takes a look at that new
text as well as the rest of the security considerations.

Everything else below is fine with me.

Thanks,
--David

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Wednesday, April 09, 2014 10:12 AM
> To: Black, David
> Cc: zhai.hongjun@zte.com.cn; hu.fangwei@zte.com.cn; Radia@alum.mit.edu;
> ostokes@extremenetworks.com; General Area Review Team (gen-art@ietf.org);
> trill@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART review of draft-ietf-trill-esadi-06.txt
>
> Hi David,
>
> On Tue, Apr 8, 2014 at 4:58 PM, Black, David <david.black@emc.com> wrote:
> > Donald,
> >
> > Thank you for the extensive comments on the review.  I'll summarize her=
e
> > rather than add more text inline.  I'm fine with the proposed course of
> > action for anything not mentioned here:
>
> OK. It is good sign when the amount of text being written with each
> exchange starts to shrink rather than grow :-)
>
> > [1] Absence of backwards compatibility:
> >         - The Appendix A changes look good.
> >         - The "limited deployment" (and presumably also "limited
> >                 implementation") rationale for no backwards compatibili=
ty
> >                 should be included in Section 1.1.  This merits additio=
nal
> >                 text in Section 1.1
>
> OK. We could add a few more words to the proposed new version of the
> first paragraph in Section 1.1 as follows:
>
> NEWER
>    This document updates [RFC6325], the TRILL base protocol
>    specification, obsoleting and replacing the description of the
>    ESADI protocol (Section 4.2.5 of [RFC6325] including all
>    subsections), providing more detail on ESADI, updating other ESADI
>    related sections of [RFC6325], and prevailing over [RFC6325] in any
>    case where they conflict. For this reason, familiarity with
>    [RFC6325] is particularly assumed.  These changes include a change
>    to the format of ESADI-LSPs that is not backwards compatible; this
>    change is justified by the substantially increased amount of
>    information that can be carried in light of the very limited, if
>    any, deployment of [RFC6325] ESADI. These changes are further
>    discussed in Appendix A.
>
> > [2] Structure of draft wrt RFC 6325:
> >         I think the rest of the proposed changes to Section 1.1 are
> reasonable:
> >
> >         - Appendix A does explain what's changed.  I would have liked t=
o see
> >                 more formality/precision in Section 1.1, but that's a m=
atter
> of
> >                 editorial taste that I'll leave to the authors.  The
> proposed
> >                 addition of a forward reference to Appendix A will
> definitely
> >                 help.
> >         - The proposed addition of an explicit statement about expectin=
g
> >                 familiarity with RFC 6325 in Section 1.1 will also help=
.
> >
> > [3] Independence of ESADI instances: What bothered me was the absence o=
f
> > a strong mention of implementation structure - I have some new text to
> > suggest to strengthen that point:
> >
> > OLD
> >    It is an implementation decision how independent the multiple ESADI
> >    instances at an RBridge are.
> > NEW
> >    Multiple ESADI instances may share implementation components within
> >    an RBridge as long as that sharing preserves the independent operati=
on
> >    of each instance of the ESADI protocol.
> >
> > Then the link state database example that follows makes more sense,
> > at least to me.
>
> I'm OK with the wording you suggest.
>
> > [4] Section 8  Authentication TLV usage discussion.
> >
> >> How about adding a new paragraph to Section 8, between the current
> >> first and second paragraphs, incorporating the above, such as:
> >>
> >>    However, there may be cases where it is not necessary to
> >>    authenticate ESADI PDUs despite using authenticated registration
> >>    for end stations.  For example a TRILL campus with secure RBridges
> >>    and inter-RBridge links configured as trunks but some end stations
> >>    connected via 802.11 wireless access links might use 802.11
> >>    authentication for the connection of such end stations but not
> >>    necessarily authenticate ESADI PDUs. Note that if the IS-IS LSPs in
> >>    a TRILL campus are authenticated, perhaps due to a concern about
> >>    forged packets, the ESADI PDUs will be authenticated by default as
> >>    provided in Section 6.3.
> >
> > These seems a bit descriptive, with most of the text describing a
> > specific example.  I'm looking for some more prescriptive guidance
> > about what SHOULD (or perhaps should?) be the case when the Authenticat=
ion
> > TLV is not used with authenticated registration.
>
> Well, a more general statement of the criteria for such cases could be
> added such as below:
>
>    However, there may be cases where it is not necessary to
>    authenticate ESADI PDUs despite using authenticated registration
>    for end stations because of a significant threat of forged packets
>    on end station links when that threat is not present for
>    inter-RBridge trunks.  For example a TRILL campus with secure
>    RBridges and inter-RBridge links configured as trunks but some end
>    stations connected via 802.11 wireless access links might use
>    802.11 authentication for the connection of such end stations but
>    not necessarily authenticate ESADI PDUs. Note that if the IS-IS
>    LSPs in a TRILL campus are authenticated, perhaps due to a concern
>    about forged packets, the ESADI PDUs will be authenticated by
>    default as provided in Section 6.3.
>
> > [5] VLAN tag presence (nit)
> >
> >> > Last sentence on p.8:
> >> >
> >> > OLD
> >> >    The outer VLAN tag will not be present if it was stripped by
> >> >    an Ethernet port out of which the packet was sent.
> >> > NEW
> >> >    The outer VLAN tag will not be present for a packet on an
> >> >    an Ethernet link that does not use VLAN tags.
> >
> > I don't think the word "stripped" is right, as it would not apply if
> > the tag wasn't present in the first place, although I also agree with
> > your comment that my suggested use of "link" isn't right, either.
> >
> > Here's another suggestion:
> >
> >     The outer VLAN tag will not be present if it was not included
> >     by the Ethernet port that sent the packet.
>
> I agree that "stripped" is not a very good word to use. I'm OK with
> your suggested wording.
>
> 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
>
> > Thanks,
> > --David
> >
> >> -----Original Message-----
> >> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> >> Sent: Saturday, April 05, 2014 11:23 AM
> >> To: Black, David
> >> Cc: zhai.hongjun@zte.com.cn; hu.fangwei@zte.com.cn; Radia@alum.mit.edu=
;
> >> ostokes@extremenetworks.com; General Area Review Team (gen-art@ietf.or=
g);
> >> trill@ietf.org; ietf@ietf.org
> >> Subject: Re: Gen-ART review of draft-ietf-trill-esadi-06.txt
> >>
> >> Hi David,
> >>
> >> Thanks for this very thorough review. See my responses below:
> >>
> >> On Sat, Mar 29, 2014 at 10:23 PM, Black, David <david.black@emc.com> w=
rote:
> >> >
> >> > I am the assigned Gen-ART 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 comment=
s
> >> > you may receive.
> >> >
> >> > Document: draft-ietf-trill-esadi-06.txt
> >> > Reviewer: David L. Black
> >> > Review Date: March 29, 2014
> >> > IETF LC End Date: April 1, 2014
> >> >
> >> > Summary: This draft is on the right track, but has open issues
> >> > described in the review.
> >> >
> >> > This draft revises the ESADI specification for TRILL from its
> >> > original form in RFC 6325.
> >> >
> >> > Major issues:
> >> >
> >> > The draft changes ESADI in a non-backwards-compatible fashion from
> >> > its original specification in RFC 6325, but does not explain why thi=
s
> >> > is ok.  That explanation needs to be provided, and if implementation=
s
> >> > of ESADI as originally specified in RFC 6325 exist, that explanation
> >> > needs to encompass coexistence and interoperability (or lack thereof=
)
> >> > with such implementations.  That explanation probably belongs in
> >> > Section 1.1, and could be expanded upon in Appendix A.
> >>
> >> This was a considered decision of the TRILL WG. At least since the -02
> >> version in February 2013, the ESADI WG draft has had ESADI-LSP
> >> provisions that were incompatible with RFC 6325 ESADI for the purpose
> >> of accomodating orders of magnitude more LSP fragments. This text in
> >> the draft, which originally used a somewhat ad hoc change from IS-IS
> >> LSPs to accomodate additional fragments, was posted to the list
> >> without objection before being incorporated. Since a standard IS-IS
> >> way of doing this was later in process in the ISIS WG, the ESADI draft
> >> was changed to follow this more standard way of providing for more LSP
> >> fragments and a new WG Last Call done in the TRILL WG specifically on
> >> this issue. See
> >>
> >> http://www.ietf.org/mail-archive/web/trill/current/msg06037.html
> >> http://www.ietf.org/mail-archive/web/trill/current/msg06009.html
> >>
> >> In Appendix A (Changes to [RFC6325]), how about replacing items 2 and
> >> 3 in the list as follows (includes fixing a typo in item 3):
> >>
> >> OLD
> >>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
> >>       is changed from the base IS-IS format to the Extended Level 1
> >>       Circuit Scoped format in [FS-LSP].
> >> NEW
> >>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
> >>       is changed from the base IS-IS format to the Extended Level 1
> >>       Circuit Scoped format (E-L1CS) specified in [FS-LSP]. This
> >>       change is not backwards compatible with [RFC6325]. It is made in
> >>       light of (a) the very limited, if any, deployment of [RFC6325]
> >>       ESADI, and (b) the 256 times greater information carrying
> >>       capacity of the E-L1CS format compared with the base IS-IS
> >>       format. It is anticipated that this greater carrying capacity
> >>       will be needed, under some circumstances, to carry end station
> >>       addressing information or other information that is added to
> >>       ESADI in the future.
> >> OLD
> >>    3. Unicasting of ESADI PDUs is supported including replacing Sectio=
n
> >>       4.6.2.2 of [RFC6325] with the next text give in Section 4.1 of
> >>       this document.
> >> NEW
> >>    3. Unicasting of ESADI PDUs is optionally supported including
> >>       replacing Section 4.6.2.2 of [RFC6325] with the new text give in
> >>       Section 4.1 of this document. This unicast support is backwards
> >>       compatible because it is only used when the recipient RBridge
> >>       signals its support.
> >>
> >> See possible replacement below for the first paragraph of Section 1.1
> >> that includes a condensed version of this additional material
> >> concerning backwards non-compatibility.
> >>
> >> > Overall, this draft is not self-contained - to a significant extent,
> >> > it is written as if it were effectively a long collection of errata
> >> > to the ESADI specification in RFC 6325. That makes it difficult to
> >> > understand - it would be better if this draft completely obsoleted
> >> > and replaced the ESADI specification in RFC 6325, describing its
> >> > changes, instead of providing specific text changes to portions of
> >> > the RFC 6325 text.
> >>
> >> All of the changes to ESADI are described in Appendix A.
> >>
> >> If the ESADI related material in RFC 6325 was entirely contained in
> >> one contiguous area of RFC 6325, it would have been easy to write this
> >> draft as simply obsoleting and replacing that area of RFC 6325.  The
> >> largest such monolithic block on ESADI in RFC 6325 is Section 4.2.5
> >> (The TRILL ESADI Protocol), including its two subsections ("4.2.5.1
> >> TRILL ESADI Participation" and "4.2.5.2 TRILL ESADI Information"). All
> >> of that is obsoleted and replaced by this draft.  However, there are
> >> other non-contiguous parts of RFC 6325 necessarily affected. For
> >> example, Section 4.6 of RFC 6325 describes how to handle every
> >> possible type of frame that might be received; since an ESADI PDU is
> >> one such type of frame, it is necessary to change Section 4.6.2.2
> >> ("TRILL ESADI Frames") of RFC 6325.
> >>
> >> There is really no substitute for having a general familiarity with
> >> RFC 6325 in understanding this document. Although I have seen IESG
> >> members criticize statements such as "Familiarity with X is assumed."
> >> when X is a normative reference, on the grounds that familiarity with
> >> all normative references is automatically assumed, perhaps some such
> >> statement is warranted in this case.
> >>
> >> In addressing both of your issues here, the first paragraph of Section
> >> 1.1 could be changed as follows:
> >>
> >> OLD
> >>    This document updates [RFC6325], the TRILL base specification,
> >>    replacing the description of the ESADI protocol in Section 4.2.5 of
> >>    [RFC6325], providing more detail, and prevailing over [RFC6325] whe=
re
> >>    they conflict. The changes are summarized in Appendix A. These
> >>    changes are not backwards compatible because, among other things,
> >>    they change the format of ESADI-LSPs.
> >> NEW
> >>    This document updates [RFC6325], the TRILL base protocol
> >>    specification, obsoleting and replacing the description of the
> >>    ESADI protocol (Section 4.2.5 of [RFC6325] including all
> >>    subsections), providing more detail on ESADI, updating other ESADI
> >>    related sections of [RFC6325], and prevailing over [RFC6325] in any
> >>    case where they conflict. For this reason, familiarity with
> >>    [RFC6325] is particularly assumed.  These changes are not backwards
> >>    compatible because they change the format of ESADI-LSPs to
> >>    substantially increase the amount of information that can be
> >>    carried. These changes are further discussed in Appendix A.
> >>
> >>
> >> > Minor issues:
> >> >
> >> > I don't understand the discussion in section 2 of it being "an
> >> > implementation decision how independent the multiple ESADI instances
> >> > at an RBridge are" in light of the clear statement that "the ESADI
> >> > update process operates separately for each ESADI instance."  The
> >> > example given involves database structure considerations that are
> >> > specific to the node implementation and do not affect the independen=
t
> >> > updates for each ESADI instance.  There may not be an actual
> >> > technical problem here, but at least the first chunk of text quoted
> >> > in this paragraph of the review needs to be rewritten.
> >>
> >> Two things motivated the text you cite in Section 2: (1) ESADI uses
> >> multiple instances of the flooding process for the purpose of limiting
> >> the flooding to the TRILL switches that have expressed interest in a
> >> particular Data Label. RFC 6822 specifies a different type of IS-IS
> >> "instance" and there is some implication in 6822 of fault and
> >> performance isolation between RFC 6822 instances. Although this
> >> document says its instances are not the same as RFC 6822 instances,
> >> someone might still have the impression that ESADI instances are
> >> necessarily to be implemented inside a TRILL switch is a highly
> >> isolated manner. This text is to emphasize that the extent to which
> >> the execution of different ESADI instances are isolated within a TRILL
> >> switch is an implementation decision. (2) Perhaps a symptom of item 1:
> >> in early discussions of ESADI, there were multiple complaints that
> >> maintaining 'so many different link state databases' in a TRILL switch
> >> would be an undue burden. So the text here specifically mentions that
> >> the databases for all ESADI instances at a TRILL switch can be merged
> >> (with an appropriate marker in each record saying which instance it
> >> belongs to).
> >>
> >> While the IETF generally standardizes bits on the wire and not
> >> internal implementation details, the above concerns lead to these few
> >> sentences to dispel any false impression.  I do not really see how
> >> there can be much confusion since the draft also says, as your point
> >> out, "But the ESADI update process operates separately for each ESADI
> >> instance and independently from the TRILL IS-IS update process.". I
> >> suggest the following change:
> >>
> >> OLD
> >>    It is an implementation decision how independent the multiple ESADI
> >>    instances at an RBridge are.
> >> NEW
> >>    This specification does not constrain how coupled or independent
> >>    the multiple ESADI instances are in their implementation internal
> >>    to an RBridge.
> >>
> >>
> >> > Also in Section 2:
> >> >
> >> >    ESADI does no routing so there is no reason for pseudo-nodes in E=
SADI
> >> >    and none are created.
> >> >
> >> > Need to explain what a pseudo-node is before this sentence.
> >>
> >> I do not think this document is the right place for a detailed
> >> explanation of pseudo-nodes. How about changing to the following:
> >>
> >>    ESADI does no routing calculations so there is no reason for
> >>    pseudo-nodes in ESADI and none are created (Pseudo-nodes [IS-IS]
> >>    are a construct for optimizing routing calculations.)
> >>
> >>
> >> > p.9, Figure 2 - explain how the receiver determines whether the inne=
r
> >> > Ethernet header contains a VLAN tag or FGL.  This also applies to Fi=
gure
> >> > 3 on p.10.
> >>
> >> I'm not sure this draft is the place for a detailed explanation but I
> >> have no problem adding the already existing reference "[RFCfgl]" to
> >> both figures right after where they say "VLAN or FGL Data Label (4 or
> >> 8 bytes)". That referenced document [RFCfgl], which is in the RFC
> >> Editor's queue, explains this.
> >>
> >>
> >> > p.10, Section 2.1:
> >> >
> >> >    All transit RBridges forward ESADI packets as if they were ordina=
ry
> >> >    TRILL Data packets.
> >> >
> >> > Need to explain what a "transit" RBridge is.  Between this and the
> >> > above pseudo-node comment, I suggest adding an overview of the
> >> > TRILL protocol to the start of Section 2.
> >>
> >> How about just eliminating the word "transit", which I don't think is
> >> necessary, and changing the sentence in question to
> >>
> >>      All RBridges forward ESADI packets as if they were ordinary TRILL
> >>      Data packets [RFC6325].
> >>
> >>
> >> > p.11, Section 2.1:
> >> >
> >> >    No "routing" computation or routing decisions ever have to be
> >> >    performed by ESADI.
> >> >
> >> > What is a ' "routing" computation' ??  This should be rephrased to
> >> > contrast to what the non-ESADI TRILL usage of IS-IS does.
> >>
> >> How about the following change:
> >>
> >> OLD
> >>    No "routing" computation or routing decisions ever have to be
> >>    performed by ESADI.
> >> NEW
> >>    No "routing" calculation (least cost path or distribution tree
> >>    construction) ever has to be performed by ESADI.
> >>
> >>
> >> > p.12, Section 2.2:
> >> >
> >> >    If a VLAN or FGL ID
> >> >    field within an ESADI-LSP PDU does include a value, that field's
> >> >    contents is ignored.
> >> >
> >> > This looks like it's an important requirement, so:
> >> >          "is ignored" -> "MUST be ignored"
> >>
> >> OK.
> >>
> >>
> >> > p.13, Section 3
> >> >
> >> >   "SNPA/MAC address"
> >> >    is not considered in this tie breaking and there is no "Port ID".
> >> >
> >> > This is contrasting ESADI tie-breaking to a tie-breaking procedure
> >> > that I'd guess is specified in another document; that needs to be
> >> > explained, along with a reference to that document, preferably with
> >> > the section number where the other tie-breaking procedure is
> >> > specified.
> >>
> >> The other document is [rfc6327bis] which is referenced.  However, this
> >> reference can be made clearer. How about
> >>
> >> OLD
> >>    Generally speaking, the DRB election on the ESADI virtual link (see
> >>    Section 2.1) operates similarly to a TRILL IS-IS broadcast link
> >>    [rfc6327bis] with the following exceptions:
> >> NEW
> >>    Generally speaking, the DRB election on the ESADI virtual link (see
> >>    Section 2.1) operates similarly to the DRB election on a TRILL
> >>    IS-IS broadcast link, as described in Section 4.2.1 ("DRB Election
> >>    Details") of [rfc6327bis], with the following exceptions:
> >>
> >>
> >> > Section 6 - explain where the 1470 byte number in the third
> >> > paragraph comes from.
> >>
> >> How about adding the following at the end of the relevant paragraph,
> >> just before the Section 6.1 header:
> >>
> >>    (As stated in Section 4.3.1 of [RFC6325], 1470 bytes was chosen to
> >>    make it extremely unlikely that a TRILL control packet, even with
> >>    reasonable additional headers, tags, and/or encapsulation, would
> >>    encounter MTU problems on an inter-RBridge link.)
> >>
> >>
> >> > Section 8 - more should be said on whether/when the Authentication
> >> > TLV should be used when ESADI conveys information from an
> >> > authenticated registration. In particular, if this recommendation
> >> > for usage of the Authentication TLV with information from an
> >> > authenticated registration usage is not a "SHOULD" or "MUST", an
> >> > explanation is in order.
> >>
> >> Consider the following: we have a network with secure trunk links
> >> between trusted TRILL switches but in some cases those switches are
> >> connected to end stations via 802.11 Wi-Fi links. It seems entirely
> >> reasonable to use 802.11 authentication in allowing end stations to
> >> connect due to the inherent accessiblity of radio links, but might not
> >> be necessary to use authentication on ESADI PDUs between TRILL
> >> switches.
> >>
> >> In any case, if there is a concern about forged packets, the IS-IS
> >> LSPs in the TRILL campus should be authenticated and, in that case,
> >> the ESADI PDUs will be authenticated by default as provided in Section
> >> 6.3 of this draft.
> >>
> >> How about adding a new paragraph to Section 8, between the current
> >> first and second paragraphs, incorporating the above, such as:
> >>
> >>    However, there may be cases where it is not necessary to
> >>    authenticate ESADI PDUs despite using authenticated registration
> >>    for end stations.  For example a TRILL campus with secure RBridges
> >>    and inter-RBridge links configured as trunks but some end stations
> >>    connected via 802.11 wireless access links might use 802.11
> >>    authentication for the connection of such end staions but not
> >>    necessarily authenticate ESDAI PDUs. Note that if the IS-IS LSPs in
> >>    a TRILL campus are authenticated, perhaps due to a concern about
> >>    forged packets, the ESADI PDUs will be authenticated by default as
> >>    provided in Section 6.3.
> >>
> >>
> >> > Nits/editorial comments:
> >> >
> >> > There are lots of acronyms that are not expanded on first use,
> >> > defined in the terminology section, or otherwise explained, e.g.,
> >> > DRB, Sz, CSNP, PSNP. It may be ok to point to terminology/acronym
> >> > definitions in RFC 6325.
> >>
> >> I believe these are all defined/expanded in RFC 6325 but it would
> >> still be a good idea to expand them on first use in this document.
> >>
> >>
> >> > Last sentence on p.8:
> >> >
> >> > OLD
> >> >    The outer VLAN tag will not be present if it was stripped by
> >> >    an Ethernet port out of which the packet was sent.
> >> > NEW
> >> >    The outer VLAN tag will not be present for a packet on an
> >> >    an Ethernet link that does not use VLAN tags.
> >>
> >> Well, whether or not any particular Ethernet frame carrying a TRILL
> >> Data packet is VLAN tagged or not depends on whether the port sending
> >> that frame is configured to send it tagged or untagged. There is no
> >> requirement or enforcement mechanism that all the ports on that
> >> Ethernet link be identically configured in this regard. So I do not
> >> consider it to be a property of the link.
> >>
> >>
> >> Also, Appendix A item 1: replces -> replaces
> >>
> >> 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
> >>
> >> > idnits 2.13.01 got confused by the Section 4.6.2.2 reference to
> >> > RFC 6325 in Section 4.1, and thought 4.6.2.2 was an IPv4 address -
> >> > this is not a problem.
> >> >
> >> > idnits also warned about possible pre-RFC5378 (2008) content.  This
> >> > is probably not a problem, but please check with your AD.
> >> >
> >> > 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
> >> > ----------------------------------------------------
> >


From nobody Wed Apr  9 09:40:09 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 F2F101A03D4; Wed,  9 Apr 2014 09:40:05 -0700 (PDT)
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 Z0MSBwTpwjPj; Wed,  9 Apr 2014 09:40:01 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id D5D7D1A0380; Wed,  9 Apr 2014 09:40:00 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id x48so2716540wes.38 for <multiple recipients>; Wed, 09 Apr 2014 09:39:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Wy/6QV5J6tEpUKh9QZQavuEAX2n4wMjnDLEomPxwCPc=; b=GcAKMMlXgm0qTNPYeGV28Ngb9G6Pcpju4HSv+S9aPcTZtJAFK09Hb4DwY/eilRxbWi FUyYywQ7yxVKbqX2i5vF7sqyxcoWs6LwjMyiYuZu+Bariq+7TH94ThZakx4ouWs9iNKe xYuO2nCRyYlfn0Ly4RdQ37ox6q2v6BCGIoVITbDKbxBBkjqmdhDbmRJGTxEtkq1xx/7N CUfl/LvYPnj71S6ciPVt+kXsBzpDkEFBZlYmbxgmzECXxl2RrY4BBcvyr2TYi5ypg8pt M2B2fDrh+qlXU0HLYtECnUaZ7/+As6Yyc+WcakUbKSJkVUB9TE+IBNfw3JwFYVL2i3l8 P0Lw==
MIME-Version: 1.0
X-Received: by 10.180.77.129 with SMTP id s1mr10931755wiw.56.1397061599873; Wed, 09 Apr 2014 09:39:59 -0700 (PDT)
Received: by 10.227.144.132 with HTTP; Wed, 9 Apr 2014 09:39:59 -0700 (PDT)
In-Reply-To: <5F92FD08-1636-48C0-9634-8806E9F577FF@piuha.net>
References: <CABkgnnVVQCAz=ixeR04rc75Vc-rL2JFQcjT0-hX_UCL-c=FGjQ@mail.gmail.com> <5F92FD08-1636-48C0-9634-8806E9F577FF@piuha.net>
Date: Wed, 9 Apr 2014 09:39:59 -0700
Message-ID: <CABkgnnUdkHYxGnFOkaHf-Xc+v=UYiASBS7KBJeC75aEV1SyKMA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/S3aVMLeCd-U0mEQbk_eEWpSLmvg
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IESG IESG <iesg@ietf.org>, draft-drage-sipping-rfc3455bis.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-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: Wed, 09 Apr 2014 16:40:06 -0000

On 9 April 2014 05:41, Jari Arkko <jari.arkko@piuha.net> wrote:
> Have there been any responses or changes based on your comments? I do not see the document version having changed...

I have seen no response or revision.


From nobody Wed Apr  9 14:44:35 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 BBCFE1A02B3 for <gen-art@ietfa.amsl.com>; Wed,  9 Apr 2014 14:44:32 -0700 (PDT)
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 6YICk9v67MRO for <gen-art@ietfa.amsl.com>; Wed,  9 Apr 2014 14:44:31 -0700 (PDT)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id D8B221A0290 for <gen-art@ietf.org>; Wed,  9 Apr 2014 14:44:30 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id l6so3460141oag.39 for <gen-art@ietf.org>; Wed, 09 Apr 2014 14:44:30 -0700 (PDT)
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=uvp45db05rSXrsOFRr0kNUi+UIfUrxutzfQloPd378M=; b=vrYsDI0o+7RkRvO9SRWI5ICQ+2g+hxPA9AGSC5kSacqFVs1/G5Ch9zK9U/MnHYAN+H wAF1OCzKe/EnQBabyKQDzqiC6Is0r7uBzxnVCopZyQOnebRUar3jAp00aL+xaI040LE0 IXSSkBjvJT6xMu+iRWfAQIGglv8h9MlsZIBLNdfvYe5qi/L7w/Y4C3m83njQmNnhkFsf HasLWrpJjoIWmmcj61Zm6PTJek1qcA64nUYuZNLGV5T8LK+oQjb7Q+O0cBGmeumjbRCg xdJSBAT9qBR4flCvyJvT+s70Tu+Rynii0O3NhtU3mdDTRO9SNiIg4+uI63hnbNBRBNdZ 0/yg==
X-Received: by 10.60.141.70 with SMTP id rm6mr10710957oeb.27.1397079870270; Wed, 09 Apr 2014 14:44:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.153.6 with HTTP; Wed, 9 Apr 2014 14:44:09 -0700 (PDT)
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 9 Apr 2014 17:44:09 -0400
Message-ID: <CAPv4CP9itHJExWNNP8HZyc2Wa7PeLHe0QbD3gOpciRR_2-6JHg@mail.gmail.com>
To: draft-ietf-ccamp-rsvp-te-eth-oam-ext.all@tools.ietf.org,  gen-art <gen-art@ietf.org>, Adrian Ferrell <adrian@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/FAAUbDACiF5dOp7OCRGhO4F8aAU
Subject: [Gen-art] GEN-ART last call review of draft-ietf-ccamp-rsvp-te-eth-oam-ext
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, 09 Apr 2014 21: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-ccamp-rsvp-te-eth-oam-ext-11
Reviewer: Scott Brim
Review Date: 2014-04-09
IETF LC End Date: 2014-04-15
IESG Telechat date: none yet

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

Major issues: None

Minor issues: None

Nits/editorial comments:

  Nice  job.

  Obsessive copyeditor nit: The sections on sub-TLVs in 3.3 all begin
  with "The ___ Sub-TLV is depicted below, this sub-TLV ...". You should
  end a sentence after "below" and begin a new one with "This".

Scott


From nobody Thu Apr 10 01:39:24 2014
Return-Path: <R.Jesske@telekom.de>
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 C75201A00A3 for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 01:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level: 
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] 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 YR0PK7KfBl5n for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 01:07:25 -0700 (PDT)
Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) by ietfa.amsl.com (Postfix) with ESMTP id BBA1B1A0023 for <gen-art@ietf.org>; Thu, 10 Apr 2014 01:07:23 -0700 (PDT)
Received: from he113676.emea1.cds.t-internal.com ([10.134.99.29]) by tcmail41.telekom.de with ESMTP/TLS/AES128-SHA; 10 Apr 2014 10:07:17 +0200
Received: from HE113667.emea1.cds.t-internal.com ([fe80::c943:1394:e86e:fce3]) by HE113676.emea1.cds.t-internal.com ([::1]) with mapi; Thu, 10 Apr 2014 10:07:15 +0200
From: <R.Jesske@telekom.de>
To: <mary.ietf.barnes@gmail.com>, <draft-drage-sipping-rfc3455bis@tools.ietf.org>, <gen-art@ietf.org>, <jari.arkko@piuha.net>, <martin.thomson@gmail.com>
Date: Thu, 10 Apr 2014 10:07:13 +0200
Thread-Topic: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-13
Thread-Index: Ac9USKMg8FdDoNCWSBqBu+RDaPdx0AANRLog
Message-ID: <058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6F@HE113667.emea1.cds.t-internal.com>
References: <CABkgnnVVQCAz=ixeR04rc75Vc-rL2JFQcjT0-hX_UCL-c=FGjQ@mail.gmail.com> <5F92FD08-1636-48C0-9634-8806E9F577FF@piuha.net> <CABkgnnUdkHYxGnFOkaHf-Xc+v=UYiASBS7KBJeC75aEV1SyKMA@mail.gmail.com> <CAHBDyN5a+S-1QUzD0eWpkxMdT0tBZ9_DZELM1FKuutmXNk8a0g@mail.gmail.com>
In-Reply-To: <CAHBDyN5a+S-1QUzD0eWpkxMdT0tBZ9_DZELM1FKuutmXNk8a0g@mail.gmail.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: multipart/alternative; boundary="_000_058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6FHE113667eme_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/vByAsllAvXj0wuDJuIQsrMfDBGA
X-Mailman-Approved-At: Thu, 10 Apr 2014 01:39:23 -0700
Cc: atle.monrad@ericsson.com, rlb@ipv.sx, gonzalo.camarillo@ericsson.com
Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-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: Thu, 10 Apr 2014 08:07:31 -0000

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

Hi Marry,
I'm really sorry, this mail slipped through my hands. And I didn't see anyt=
hing in the data tracker history. Since I'm the main Editor, it is my fault=
 that this was not answered.
It is true we cannot claim any speed if we do nothing. Again I'm Sorry.

So here are my answers. For the Gen-review.
So I have created a Version -14 which I can upload now. Please indicate if =
I should do this or if I should wait for further comments?


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-drage-sipping-rfc3455bis-13

Reviewer: Martin Thomson

Review Date: 2014-02-27

IETF LC End Date: 2014-03-14

IESG Telechat date: (if known)



Summary: I find it strange that this 3GPP document is being published on th=
e standards track.  But since it's a -bis there is clearly precedent, and i=
t is otherwise sound.



[RJ] Yes it is informal as RFC3455 is I'll change that.



Major issues:



This document doesn't include enough information for me to some of the head=
ers.  For example, there isn't enough information in the document to allow =
me to interpret the contents of cgi-3gpp:

          cgi-3gpp     =3D "cgi-3gpp" EQUAL (token / quoted-string)

(I pick on P-Access-Network-Info, because I'm somewhat familiar with it.)



This can probably be addressed by the inclusion of appropriate normative re=
ferences.  I seem to recall there being a 3GPP TS that covered at least som=
e of these.


[RJ] Below that section we have the text:
The access-info MAY contain additional information relating to the access n=
etwork. The values for "cgi-3gpp", "utran-cell-id-3gpp",
       "i-wlan-node-id", "dsl-location" and "ci-3gpp2", "ci-3gpp2-femto" an=
d  "gstn-location" are defined in 3GPP TS 24.229

Do we need more?



Minor issues:



RFC 4244 is now obsolete, see 7044.  (related nit: Change log entry #2 seem=
s quite defensive, unnecessarily so.  This document only needs to define P-=
Called-Party-ID, and reference History-Info as an alternative

mechanism.)



[RJ] Replaced

[RJ] Due to your comment I have removed the whole text as follows:
Additionally the P-Called-Party-ID
       header field has been defined within 3GPP systems since release
       5, and therefore it is realistic to expect implementations to be
       already released to the field.  It is therefore considered that
       replacement of the P-Called-Party-ID header field within 3GPP
       systems causes more issues that it solves, and therefore the
       update of RFC3455 <xref
         target=3D"RFC3455"></xref> to remove the P-Called-Party-ID header =
field
       will not be addressed.  However it is recommended that any new
       usage of this type of functionality should use the History-Info

       header field defined in RFC 7044 <xref target=3D"RFC7044"></xref>rat=
her than the P-Called-Party-ID header field





Change log entry #5, mentions a shortcoming of 3455 (no registry for access=
 network types), but the draft does nothing about it.  It seems to be propa=
gating the mistake it notes.



[RJ] Yes I can agree this. so this seems a action for future.



A lot has happened since RFC 3455 was published.  The privacy consideration=
s around the use of P-Access-Network-Info are unchanged from their pre-Geop=
riv form.  In particular, I find the UA knowledge part to be problematic; G=
eopriv definitions can probably help here.



[RJ] sorry cannot do





S6.1 P-Associated-URI is a powerful linkability vector, which could be a fa=
r more serious privacy leak than the text implies.  The following seems lik=
e good advice, but is not sufficient:



   An eavesdropper could possibly collect the list of identities a user

   is registered.  This can have privacy implications.  To mitigate this

   problem, this extension SHOULD only be used in a secured environment,

   where encryption of SIP messages is provided either end-to-end or

   hop-by-hop.



You also have to trust the other end of the hop with the information.

I think that's implicit, but probably needs to be stated.



[RJ] I have addedthe following:

And where a trustrelationship equivalent with that defined in RFC 3325 <xre=
f target=3D"RFC3325">between entities exist





S6.4  This claim sounds false to me:



   However, there

   are no security problems resulting from a UA inserting incorrect

   information.  Networks providing services based on the information

   carried in the P-Access-Network-Info header field will therefore need

   to trust the UA sending the information.  A rogue UA sending false

   access network information will do no more harm than to restrict the

   user from using certain services.



Any parameter whereby changing it can cause loss of service is likely to be=
 true in the inverse.  The draft makes no claims that would make me believe=
 otherwise.



[RJ] Since we have the P-Access-Network-Info as header that is also set up =
by the IMS entity P-CSCF with adding the network provided element there is =
a difference in interpreting the header by Applications. Of course the netw=
ork provided information is trustful and can be used for sensitive services=
 since the user provided information should only be used by services which =
are not sensitive.



[RJ] Is this sufficient?





Nits/editorial comments:



S1 Having the disclaimer as the first section is a little strange.  I don't=
 know what it is disclaiming yet.



[RJ] That is a copy from RFC3455. RFC3455 fullfills the requirements docume=
nted in RFC4083. Would this be sufficient to write as a one sentence statem=
ent?





S1, S3 It looks like a few characters are missing from these sections:

"trust.These", "environment The", "[RFC3455]   This"



[RJ] Done



The change log contains a lot of normative language.  I expected to see poi=
nters to changes, and maybe some justification, but items include normative=
-sounding text and no pointers(7), other contain pointers and duplicate tex=
t (3&4)



[RJ] tried to solve this. deleted normative text and made some corrections =
to your points.



Change log #6 notes the removal of a field; given that this is extensible, =
why not just mark the CDMA 2000 item deprecated instead of removing it?

[RJ] As far as I know is that 3GPP does not want to use it anymore. Is it n=
ot sufficent to not the deletion?


Best Regards

Roland

Von: Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
Gesendet: Donnerstag, 10. April 2014 01:08
An: draft-drage-sipping-rfc3455bis@tools.ietf.org
Cc: Atle Monrad; Gonzalo Camarillo; Richard Barnes
Betreff: Fwd: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-13

Can you guys please respond to Martin's review?  This document is on the IE=
SG telechat agenda for tomorrow.  Honestly, you guys cannot complain that I=
ETF is not doing work in a timely manner if authors cannot respond to revie=
ws like this, especially at this stage of the game.

I will note that I haven't seen all the messages around these reviews becau=
se people don't usually add the shepherd and I don't seem to be being picke=
d up by any aliases.

Regards,
Mary.
---------- Forwarded message ----------
From: Martin Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.=
com>>
Date: Wed, Apr 9, 2014 at 11:39 AM
Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-13
To: Jari Arkko <jari.arkko@piuha.net<mailto:jari.arkko@piuha.net>>
Cc: "gen-art@ietf.org<mailto:gen-art@ietf.org> Review Team" <gen-art@ietf.o=
rg<mailto:gen-art@ietf.org>>, IESG IESG <iesg@ietf.org<mailto:iesg@ietf.org=
>>, draft-drage-sipping-rfc3455bis.all@tools.ietf.org<mailto:draft-drage-si=
pping-rfc3455bis.all@tools.ietf.org>

On 9 April 2014 05:41, Jari Arkko <jari.arkko@piuha.net<mailto:jari.arkko@p=
iuha.net>> wrote:
> Have there been any responses or changes based on your comments? I do not=
 see the document version having changed...
I have seen no response or revision.


--_000_058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6FHE113667eme_
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 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin: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:"Nur Text Zchn";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Sprechblasentext Zchn";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.SprechblasentextZchn
	{mso-style-name:"Sprechblasentext Zchn";
	mso-style-priority:99;
	mso-style-link:Sprechblasentext;
	font-family:"Tahoma","sans-serif";}
span.E-MailFormatvorlage19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.NurTextZchn
	{mso-style-name:"Nur Text Zchn";
	mso-style-priority:99;
	mso-style-link:"Nur Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
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=3DDE link=3Dblue vlink=
=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>Hi Marry,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I=
&#8217;m really sorry, this mail slipped through my hands. And I didn&#8217=
;t see anything in the data tracker history. Since I&#8217;m the main Edito=
r, it is my fault that this was not answered.<o:p></o:p></span></p><p class=
=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'>It is true we cannot claim any speed if we=
 do nothing. Again I&#8217;m Sorry.<o:p></o:p></span></p><p class=3DMsoNorm=
al><span lang=3DEN-US style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><sp=
an lang=3DEN-US style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif=
";color:#1F497D'>So here are my answers. For the Gen-review.<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'>So I have created a Version=
 -14 which I can upload now. Please indicate if I should do this or if I sh=
ould wait for further comments?<o:p></o:p></span></p><p class=3DMsoNormal><=
span lang=3DEN-US style=3D'font-size:11.0pt;font-family:"Calibri","sans-ser=
if";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><spa=
n lang=3DEN-US>I am the assigned Gen-ART reviewer for this draft. For backg=
round on Gen-ART, please see the FAQ at<o:p></o:p></span></p><p class=3DMso=
PlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlai=
nText><span lang=3DEN-US>&lt;</span><a href=3D"http://wiki.tools.ietf.org/a=
rea/gen/trac/wiki/GenArtfaq"><span lang=3DEN-US>http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq</span></a><span lang=3DEN-US>&gt;.<o:p></o:p><=
/span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoPlainText><span lang=3DEN-US>Please resolve these comme=
nts along with any other Last Call comments you may receive.<o:p></o:p></sp=
an></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoPlainText><span lang=3DEN-US>Document: draft-drage-sipping=
-rfc3455bis-13<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN=
-US>Reviewer: Martin Thomson<o:p></o:p></span></p><p class=3DMsoPlainText><=
span lang=3DEN-US>Review Date: 2014-02-27<o:p></o:p></span></p><p class=3DM=
soPlainText><span lang=3DEN-US>IETF LC End Date: 2014-03-14<o:p></o:p></spa=
n></p><p class=3DMsoPlainText><span lang=3DEN-US>IESG Telechat date: (if kn=
own)<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&=
nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>Summary: I=
 find it strange that this 3GPP document is being published on the standard=
s track.&nbsp; But since it's a -bis there is clearly precedent, and it is =
otherwise sound.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3D=
EN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-U=
S>[RJ] Yes it is informal as RFC3455 is I&#8217;ll change that.<o:p></o:p><=
/span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoPlainText><span lang=3DEN-US>Major issues:<o:p></o:p></=
span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span=
></p><p class=3DMsoPlainText><span lang=3DEN-US>This document doesn't inclu=
de enough information for me to some of the headers.&nbsp; For example, the=
re isn't enough information in the document to allow me to interpret the co=
ntents of cgi-3gpp:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=
=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; cgi-3gpp&nb=
sp;&nbsp;&nbsp;&nbsp; =3D &quot;cgi-3gpp&quot; EQUAL (token / quoted-string=
)<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>(I pick o=
n P-Access-Network-Info, because I'm somewhat familiar with it.)<o:p></o:p>=
</span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></sp=
an></p><p class=3DMsoPlainText><span lang=3DEN-US>This can probably be addr=
essed by the inclusion of appropriate normative references.&nbsp; I seem to=
 recall there being a 3GPP TS that covered at least some of these.<o:p></o:=
p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></=
span></p><p class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN=
-US>[RJ] Below that section we have the text: <o:p></o:p></span></p><p clas=
s=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-US style=3D'col=
or:black;background:white;mso-highlight:white'>The access-info MAY contain =
additional information relating to the access network. The values for &quot=
;cgi-3gpp&quot;, &quot;utran-cell-id-3gpp&quot;,<o:p></o:p></span></p><p cl=
ass=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-US style=3D'c=
olor:black;background:white;mso-highlight:white'>&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; &quot;i-wlan-node-id&quot;, &quot;dsl-location&quot; and &quot;c=
i-3gpp2&quot;, &quot;ci-3gpp2-femto&quot; and&nbsp; &quot;gstn-location&quo=
t; are defined in 3GPP TS 24.229</span><span lang=3DEN-US style=3D'color:bl=
ack'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'text-autospace:non=
e'><span lang=3DEN-US style=3D'color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-US style=3D=
'color:black'>Do we need more?</span><span lang=3DEN-US><o:p></o:p></span><=
/p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><=
p class=3DMsoPlainText><span lang=3DEN-US>Minor issues:<o:p></o:p></span></=
p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoPlainText><span lang=3DEN-US>RFC 4244 is now obsolete, see 7044=
.&nbsp; (related nit: Change log entry #2 seems quite defensive, unnecessar=
ily so.&nbsp; This document only needs to define P-Called-Party-ID, and ref=
erence History-Info as an alternative<o:p></o:p></span></p><p class=3DMsoPl=
ainText><span lang=3DEN-US>mechanism.)<o:p></o:p></span></p><p class=3DMsoP=
lainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlain=
Text><span lang=3DEN-US>[RJ] Replaced<o:p></o:p></span></p><p class=3DMsoPl=
ainText><span lang=3DEN-US>[RJ] Due to your comment I have removed the whol=
e text as follows:<o:p></o:p></span></p><p class=3DMsoNormal style=3D'text-=
autospace:none'><span lang=3DEN-US style=3D'color:black;background:white;ms=
o-highlight:white'>Additionally the P-Called-Party-ID<o:p></o:p></span></p>=
<p class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-US style=
=3D'color:black;background:white;mso-highlight:white'>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; header field has been defined within 3GPP systems since rel=
ease<o:p></o:p></span></p><p class=3DMsoNormal style=3D'text-autospace:none=
'><span lang=3DEN-US style=3D'color:black;background:white;mso-highlight:wh=
ite'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5, and therefore it is realistic =
to expect implementations to be<o:p></o:p></span></p><p class=3DMsoNormal s=
tyle=3D'text-autospace:none'><span lang=3DEN-US style=3D'color:black;backgr=
ound:white;mso-highlight:white'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; alread=
y released to the field.&nbsp; It is therefore considered that<o:p></o:p></=
span></p><p class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN=
-US style=3D'color:black;background:white;mso-highlight:white'>&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; replacement of the P-Called-Party-ID header field =
within 3GPP<o:p></o:p></span></p><p class=3DMsoNormal style=3D'text-autospa=
ce:none'><span lang=3DEN-US style=3D'color:black;background:white;mso-highl=
ight:white'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; systems causes more issues=
 that it solves, and therefore the<o:p></o:p></span></p><p class=3DMsoNorma=
l style=3D'text-autospace:none'><span lang=3DEN-US style=3D'color:black;bac=
kground:white;mso-highlight:white'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; upd=
ate of RFC3455 </span><span lang=3DEN-US style=3D'color:blue;background:whi=
te;mso-highlight:white'>&lt;</span><span lang=3DEN-US style=3D'color:maroon=
;background:white;mso-highlight:white'>xref</span><span lang=3DEN-US style=
=3D'color:red;background:white;mso-highlight:white'><o:p></o:p></span></p><=
p class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-US style=
=3D'color:red;background:white;mso-highlight:white'>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; target</span><span lang=3DEN-US style=3D'color:bl=
ue;background:white;mso-highlight:white'>=3D&quot;</span><span lang=3DEN-US=
 style=3D'color:black;background:white;mso-highlight:white'>RFC3455</span><=
span lang=3DEN-US style=3D'color:blue;background:white;mso-highlight:white'=
>&quot;&gt;&lt;/</span><span lang=3DEN-US style=3D'color:maroon;background:=
white;mso-highlight:white'>xref</span><span lang=3DEN-US style=3D'color:blu=
e;background:white;mso-highlight:white'>&gt;</span><span lang=3DEN-US style=
=3D'color:black;background:white;mso-highlight:white'> to remove the P-Call=
ed-Party-ID header field<o:p></o:p></span></p><p class=3DMsoNormal style=3D=
'text-autospace:none'><span lang=3DEN-US style=3D'color:black;background:wh=
ite;mso-highlight:white'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; will not be a=
ddressed.&nbsp; However it is recommended that any new<o:p></o:p></span></p=
><p class=3DMsoNormal style=3D'text-autospace:none'><span lang=3DEN-US styl=
e=3D'color:black;background:white;mso-highlight:white'>&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; usage of this type of functionality should use the History=
-Info<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US style=
=3D'color:black;background:white;mso-highlight:white'>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; header field defined in RFC 7044 </span><span lang=3DEN-US =
style=3D'color:blue;background:white;mso-highlight:white'>&lt;</span><span =
lang=3DEN-US style=3D'color:maroon;background:white;mso-highlight:white'>xr=
ef</span><span lang=3DEN-US style=3D'color:red;background:white;mso-highlig=
ht:white'> target</span><span lang=3DEN-US style=3D'color:blue;background:w=
hite;mso-highlight:white'>=3D&quot;</span><span lang=3DEN-US style=3D'color=
:black;background:white;mso-highlight:white'>RFC7044</span><span lang=3DEN-=
US style=3D'color:blue;background:white;mso-highlight:white'>&quot;&gt;&lt;=
/</span><span lang=3DEN-US style=3D'color:maroon;background:white;mso-highl=
ight:white'>xref</span><span lang=3DEN-US style=3D'color:blue;background:wh=
ite;mso-highlight:white'>&gt;</span><span lang=3DEN-US style=3D'color:black=
;background:white;mso-highlight:white'>rather than the P-Called-Party-ID he=
ader field</span><span lang=3DEN-US style=3D'color:black'><o:p></o:p></span=
></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Change log entry #5, mentions a sho=
rtcoming of 3455 (no registry for access network types), but the draft does=
 nothing about it.&nbsp; It seems to be propagating the mistake it notes.<o=
:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>[RJ] Yes I can a=
gree this. so this seems a action for future.<o:p></o:p></span></p><p class=
=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DM=
soPlainText><span lang=3DEN-US>A lot has happened since RFC 3455 was publis=
hed.&nbsp; The privacy considerations around the use of P-Access-Network-In=
fo are unchanged from their pre-Geopriv form.&nbsp; In particular, I find t=
he UA knowledge part to be problematic; Geopriv definitions can probably he=
lp here.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>[RJ] s=
orry cannot do <o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DE=
N-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>S6.=
1 P-Associated-URI is a powerful linkability vector, which could be a far m=
ore serious privacy leak than the text implies.&nbsp; The following seems l=
ike good advice, but is not sufficient:<o:p></o:p></span></p><p class=3DMso=
PlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlai=
nText><span lang=3DEN-US>&nbsp;&nbsp; An eavesdropper could possibly collec=
t the list of identities a user<o:p></o:p></span></p><p class=3DMsoPlainTex=
t><span lang=3DEN-US>&nbsp;&nbsp; is registered.&nbsp; This can have privac=
y implications.&nbsp; To mitigate this<o:p></o:p></span></p><p class=3DMsoP=
lainText><span lang=3DEN-US>&nbsp;&nbsp; problem, this extension SHOULD onl=
y be used in a secured environment,<o:p></o:p></span></p><p class=3DMsoPlai=
nText><span lang=3DEN-US>&nbsp;&nbsp; where encryption of SIP messages is p=
rovided either end-to-end or<o:p></o:p></span></p><p class=3DMsoPlainText><=
span lang=3DEN-US>&nbsp;&nbsp; hop-by-hop.<o:p></o:p></span></p><p class=3D=
MsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoP=
lainText><span lang=3DEN-US>You also have to trust the other end of the hop=
 with the information.<o:p></o:p></span></p><p class=3DMsoPlainText><span l=
ang=3DEN-US>I think that's implicit, but probably needs to be stated.<o:p><=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p=
></span></p><p class=3DMsoPlainText><span lang=3DEN-US>[RJ] I have addedthe=
 following:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US=
 style=3D'color:black;background:white;mso-highlight:white'>And where a tru=
strelationship equivalent with that defined in RFC 3325 </span><span lang=
=3DEN-US style=3D'color:blue;background:white;mso-highlight:white'>&lt;</sp=
an><span lang=3DEN-US style=3D'color:maroon;background:white;mso-highlight:=
white'>xref</span><span lang=3DEN-US style=3D'color:red;background:white;ms=
o-highlight:white'> target</span><span lang=3DEN-US style=3D'color:blue;bac=
kground:white;mso-highlight:white'>=3D&quot;</span><span lang=3DEN-US style=
=3D'color:black;background:white;mso-highlight:white'>RFC3325</span><span l=
ang=3DEN-US style=3D'color:blue;background:white;mso-highlight:white'>&quot=
;&gt;</span><span lang=3DEN-US style=3D'color:black;background:white;mso-hi=
ghlight:white'>between entities exist</span><span lang=3DEN-US style=3D'col=
or:black'><o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>S6.4&nbs=
p; This claim sounds false to me:<o:p></o:p></span></p><p class=3DMsoPlainT=
ext><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText>=
<span lang=3DEN-US>&nbsp;&nbsp; However, there<o:p></o:p></span></p><p clas=
s=3DMsoPlainText><span lang=3DEN-US>&nbsp;&nbsp; are no security problems r=
esulting from a UA inserting incorrect<o:p></o:p></span></p><p class=3DMsoP=
lainText><span lang=3DEN-US>&nbsp;&nbsp; information.&nbsp; Networks provid=
ing services based on the information<o:p></o:p></span></p><p class=3DMsoPl=
ainText><span lang=3DEN-US>&nbsp;&nbsp; carried in the P-Access-Network-Inf=
o header field will therefore need<o:p></o:p></span></p><p class=3DMsoPlain=
Text><span lang=3DEN-US>&nbsp;&nbsp; to trust the UA sending the informatio=
n.&nbsp; A rogue UA sending false<o:p></o:p></span></p><p class=3DMsoPlainT=
ext><span lang=3DEN-US>&nbsp;&nbsp; access network information will do no m=
ore harm than to restrict the<o:p></o:p></span></p><p class=3DMsoPlainText>=
<span lang=3DEN-US>&nbsp;&nbsp; user from using certain services.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></s=
pan></p><p class=3DMsoPlainText><span lang=3DEN-US>Any parameter whereby ch=
anging it can cause loss of service is likely to be true in the inverse.&nb=
sp; The draft makes no claims that would make me believe otherwise.<o:p></o=
:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p><=
/span></p><p class=3DMsoPlainText><span lang=3DEN-US>[RJ] Since we have the=
 P-Access-Network-Info as header that is also set up by the IMS entity P-CS=
CF with adding the network provided element there is a difference in interp=
reting the header by Applications. Of course the network provided informati=
on is trustful and can be used for sensitive services since the user provid=
ed information should only be used by services which are not sensitive.<o:p=
></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o=
:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>[RJ] Is this suffi=
cient?<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>Nits/editori=
al comments:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-U=
S><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>S1=
 Having the disclaimer as the first section is a little strange.&nbsp; I do=
n't know what it is disclaiming yet.<o:p></o:p></span></p><p class=3DMsoPla=
inText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainTe=
xt><span lang=3DEN-US>[RJ] That is a copy from RFC3455. RFC3455 fullfills t=
he requirements documented in RFC4083. Would this be sufficient to write as=
 a one sentence statement?<o:p></o:p></span></p><p class=3DMsoPlainText><sp=
an lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span l=
ang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=
=3DEN-US>S1, S3 It looks like a few characters are missing from these secti=
ons:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>&quot;=
trust.These&quot;, &quot;environment The&quot;, &quot;[RFC3455]&nbsp;&nbsp;=
 This&quot;<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>[RJ=
] Done<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>The chan=
ge log contains a lot of normative language.&nbsp; I expected to see pointe=
rs to changes, and maybe some justification, but items include normative-so=
unding text and no pointers(7), other contain pointers and duplicate text (=
3&amp;4)<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>[RJ] t=
ried to solve this. deleted normative text and made some corrections to you=
r points.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US><=
o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>Chang=
e log #6 notes the removal of a field; given that this is extensible, why n=
ot just mark the CDMA 2000 item deprecated instead of removing it?<o:p></o:=
p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>[RJ] As far as I kn=
ow is that 3GPP does not want to use it anymore. Is it not sufficent to not=
 the deletion?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best Regar=
ds<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US 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 lang=3DEN-US style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Roland<o:p></o:p=
></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></spa=
n></p><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0p=
t 0cm 0cm 0cm'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font=
-family:"Tahoma","sans-serif"'>Von:</span></b><span style=3D'font-size:10.0=
pt;font-family:"Tahoma","sans-serif"'> Mary Barnes [mailto:mary.ietf.barnes=
@gmail.com] <br><b>Gesendet:</b> Donnerstag, 10. April 2014 01:08<br><b>An:=
</b> draft-drage-sipping-rfc3455bis@tools.ietf.org<br><b>Cc:</b> Atle Monra=
d; Gonzalo Camarillo; Richard Barnes<br><b>Betreff:</b> Fwd: [Gen-art] Gen-=
ART review of draft-drage-sipping-rfc3455bis-13<o:p></o:p></span></p></div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Can you=
 guys please respond to Martin's review? &nbsp;This document is on the IESG=
 telechat agenda for tomorrow. &nbsp;Honestly, you guys cannot complain tha=
t IETF is not doing work in a timely manner if authors cannot respond to re=
views like this, especially at this stage of the game.&nbsp;<o:p></o:p></p>=
<div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNor=
mal>I will note that I haven't seen all the messages around these reviews b=
ecause people don't usually add the shepherd and I don't seem to be being p=
icked up by any aliases.&nbsp;<o:p></o:p></p><div><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Regards,<o:p></o:p></p></d=
iv><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Mary.&nbsp;<o:p=
></o:p></p><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>-------=
--- Forwarded message ----------<br>From: <b>Martin Thomson</b> &lt;<a href=
=3D"mailto:martin.thomson@gmail.com">martin.thomson@gmail.com</a>&gt;<br>Da=
te: Wed, Apr 9, 2014 at 11:39 AM<br>Subject: Re: [Gen-art] Gen-ART review o=
f draft-drage-sipping-rfc3455bis-13<br>To: Jari Arkko &lt;<a href=3D"mailto=
:jari.arkko@piuha.net">jari.arkko@piuha.net</a>&gt;<br>Cc: &quot;<a href=3D=
"mailto:gen-art@ietf.org">gen-art@ietf.org</a> Review Team&quot; &lt;<a hre=
f=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;, IESG IESG &lt;<a hr=
ef=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;, <a href=3D"mailto:draft-=
drage-sipping-rfc3455bis.all@tools.ietf.org">draft-drage-sipping-rfc3455bis=
.all@tools.ietf.org</a><br><br><o:p></o:p></p><div><p class=3DMsoNormal sty=
le=3D'margin-bottom:12.0pt'>On 9 April 2014 05:41, Jari Arkko &lt;<a href=
=3D"mailto:jari.arkko@piuha.net">jari.arkko@piuha.net</a>&gt; wrote:<br>&gt=
; Have there been any responses or changes based on your comments? I do not=
 see the document version having changed...<o:p></o:p></p></div><p class=3D=
MsoNormal style=3D'margin-bottom:12.0pt'>I have seen no response or revisio=
n.<o:p></o:p></p></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></di=
v></div></div></body></html>=

--_000_058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6FHE113667eme_--


From nobody Thu Apr 10 03:33:52 2014
Return-Path: <atle.monrad@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 0FCAC1A01B4 for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 02:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.239
X-Spam-Level: 
X-Spam-Status: No, score=-1.239 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, 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 gRgM3sLoFIGi for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 02:43:59 -0700 (PDT)
Received: from sesbmg21.mgmt.ericsson.se (sesbmg21.ericsson.net [193.180.251.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0036A1A0194 for <gen-art@ietf.org>; Thu, 10 Apr 2014 02:43:57 -0700 (PDT)
X-AuditID: c1b4fb31-b7f688e000003e64-d4-534667dbbfe7
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 81.DE.15972.BD766435; Thu, 10 Apr 2014 11:43:56 +0200 (CEST)
Received: from ESESSMB203.ericsson.se ([169.254.3.11]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0174.001; Thu, 10 Apr 2014 11:43:55 +0200
From: Atle Monrad <atle.monrad@ericsson.com>
To: "R.Jesske@telekom.de" <R.Jesske@telekom.de>, "mary.ietf.barnes@gmail.com" <mary.ietf.barnes@gmail.com>, "draft-drage-sipping-rfc3455bis@tools.ietf.org" <draft-drage-sipping-rfc3455bis@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "jari.arkko@piuha.net" <jari.arkko@piuha.net>, "martin.thomson@gmail.com" <martin.thomson@gmail.com>
Thread-Topic: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-13
Thread-Index: AQHPVEiLlLht95WsuUSY8HWMu0FUAZsKXamAgAA8PWA=
Date: Thu, 10 Apr 2014 09:43:54 +0000
Message-ID: <7D2F7D7ADBA812449F25F4A69922881C167FCCE5@ESESSMB203.ericsson.se>
References: <CABkgnnVVQCAz=ixeR04rc75Vc-rL2JFQcjT0-hX_UCL-c=FGjQ@mail.gmail.com> <5F92FD08-1636-48C0-9634-8806E9F577FF@piuha.net> <CABkgnnUdkHYxGnFOkaHf-Xc+v=UYiASBS7KBJeC75aEV1SyKMA@mail.gmail.com> <CAHBDyN5a+S-1QUzD0eWpkxMdT0tBZ9_DZELM1FKuutmXNk8a0g@mail.gmail.com> <058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6F@HE113667.emea1.cds.t-internal.com>
In-Reply-To: <058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6F@HE113667.emea1.cds.t-internal.com>
Accept-Language: nb-NO, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7D2F7D7ADBA812449F25F4A69922881C167FCCE5ESESSMB203erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKIsWRmVeSWpSXmKPExsUyM+Jvje6ddLdgg2OfmSwaTvewW1x99ZnF Ysa+FWwW1878Y7T4vH8/s0XTnS42i6l9tg7sHjtn3WX3WLLkJ5PH5I2zWDy2LpnO5tH2UsHj y+XPbAFsUVw2Kak5mWWpRfp2CVwZS59cZy+4sICp4uSWh8wNjM//MHYxcnJICJhI7H+5lQ3C FpO4cG89kM3FISRwklFi46NuFghnMaPEtGW72UGq2AR0JM79vMMKkhAReMAk8XtCL1iCWSBY 4vfbr0wgtrCAl8SadX/B4iIC3hKTv71mhrCtJLbvbgBbzSKgKnFj2S4wm1fAV6Kp+xITxLYn TBI/mnvAmjkFYiXWfpgJdBMHB6OArMTcJl6IXeISt57MZ4I4W0BiyZ7zzBC2qMTLx/9YIWwl icYlT1gh6vMl+p88Y4bYJShxcuYTlgmMorOQjJqFpGwWkjKIuI7Egt2f2CBsbYllC18zw9hn DjxmQhZfwMi+ilGyOLU4KTfdyFAvNz23RC+1KDO5uDg/T684dRMjMKoPbvltuINx4jX7Q4zS HCxK4rwM0zuDhATSE0tSs1NTC1KL4otKc1KLDzEycXBKNTCKPp7q3664f/+Swn3Ltl1SK1Eq ffUtf//t8pCAtfUr3x2cW87g7VdjLsz/Wal51n411Zt/Ol/oPCs6NefgsrPzbPLllffay9lp Ht3RukniNKuezaLevu+ztt6qOHp40hVXr2VZfg3/FmzMlHnem6B2yNJqj9OMxCMslpdsbIQj i/99XOvttXGrEktxRqKhFnNRcSIA0itggbgCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/q6ctmjJe61m_ALt5clLhw7vSGeM
X-Mailman-Approved-At: Thu, 10 Apr 2014 03:33:50 -0700
Cc: "rlb@ipv.sx" <rlb@ipv.sx>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-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: Thu, 10 Apr 2014 09:44:03 -0000

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

Thanks Roland

Mary, is the draft back on track ??

:)

/atle

________________________________


Atle Monrad
3GPP CT Chairman

Group Function Technology - Standardization and Technical Regulation
Ericsson


From: R.Jesske@telekom.de [mailto:R.Jesske@telekom.de]
Sent: 10. april 2014 10:07
To: mary.ietf.barnes@gmail.com; draft-drage-sipping-rfc3455bis@tools.ietf.o=
rg; gen-art@ietf.org; jari.arkko@piuha.net; martin.thomson@gmail.com
Cc: Atle Monrad; Gonzalo Camarillo; rlb@ipv.sx
Subject: AW: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-13

Hi Marry,
I'm really sorry, this mail slipped through my hands. And I didn't see anyt=
hing in the data tracker history. Since I'm the main Editor, it is my fault=
 that this was not answered.
It is true we cannot claim any speed if we do nothing. Again I'm Sorry.

So here are my answers. For the Gen-review.
So I have created a Version -14 which I can upload now. Please indicate if =
I should do this or if I should wait for further comments?


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-drage-sipping-rfc3455bis-13

Reviewer: Martin Thomson

Review Date: 2014-02-27

IETF LC End Date: 2014-03-14

IESG Telechat date: (if known)



Summary: I find it strange that this 3GPP document is being published on th=
e standards track.  But since it's a -bis there is clearly precedent, and i=
t is otherwise sound.



[RJ] Yes it is informal as RFC3455 is I'll change that.



Major issues:



This document doesn't include enough information for me to some of the head=
ers.  For example, there isn't enough information in the document to allow =
me to interpret the contents of cgi-3gpp:

          cgi-3gpp     =3D "cgi-3gpp" EQUAL (token / quoted-string)

(I pick on P-Access-Network-Info, because I'm somewhat familiar with it.)



This can probably be addressed by the inclusion of appropriate normative re=
ferences.  I seem to recall there being a 3GPP TS that covered at least som=
e of these.


[RJ] Below that section we have the text:
The access-info MAY contain additional information relating to the access n=
etwork. The values for "cgi-3gpp", "utran-cell-id-3gpp",
       "i-wlan-node-id", "dsl-location" and "ci-3gpp2", "ci-3gpp2-femto" an=
d  "gstn-location" are defined in 3GPP TS 24.229

Do we need more?



Minor issues:



RFC 4244 is now obsolete, see 7044.  (related nit: Change log entry #2 seem=
s quite defensive, unnecessarily so.  This document only needs to define P-=
Called-Party-ID, and reference History-Info as an alternative

mechanism.)



[RJ] Replaced

[RJ] Due to your comment I have removed the whole text as follows:
Additionally the P-Called-Party-ID
       header field has been defined within 3GPP systems since release
       5, and therefore it is realistic to expect implementations to be
       already released to the field.  It is therefore considered that
       replacement of the P-Called-Party-ID header field within 3GPP
       systems causes more issues that it solves, and therefore the
       update of RFC3455 <xref
         target=3D"RFC3455"></xref> to remove the P-Called-Party-ID header =
field
       will not be addressed.  However it is recommended that any new
       usage of this type of functionality should use the History-Info

       header field defined in RFC 7044 <xref target=3D"RFC7044"></xref>rat=
her than the P-Called-Party-ID header field





Change log entry #5, mentions a shortcoming of 3455 (no registry for access=
 network types), but the draft does nothing about it.  It seems to be propa=
gating the mistake it notes.



[RJ] Yes I can agree this. so this seems a action for future.



A lot has happened since RFC 3455 was published.  The privacy consideration=
s around the use of P-Access-Network-Info are unchanged from their pre-Geop=
riv form.  In particular, I find the UA knowledge part to be problematic; G=
eopriv definitions can probably help here.



[RJ] sorry cannot do





S6.1 P-Associated-URI is a powerful linkability vector, which could be a fa=
r more serious privacy leak than the text implies.  The following seems lik=
e good advice, but is not sufficient:



   An eavesdropper could possibly collect the list of identities a user

   is registered.  This can have privacy implications.  To mitigate this

   problem, this extension SHOULD only be used in a secured environment,

   where encryption of SIP messages is provided either end-to-end or

   hop-by-hop.



You also have to trust the other end of the hop with the information.

I think that's implicit, but probably needs to be stated.



[RJ] I have addedthe following:

And where a trustrelationship equivalent with that defined in RFC 3325 <xre=
f target=3D"RFC3325">between entities exist





S6.4  This claim sounds false to me:



   However, there

   are no security problems resulting from a UA inserting incorrect

   information.  Networks providing services based on the information

   carried in the P-Access-Network-Info header field will therefore need

   to trust the UA sending the information.  A rogue UA sending false

   access network information will do no more harm than to restrict the

   user from using certain services.



Any parameter whereby changing it can cause loss of service is likely to be=
 true in the inverse.  The draft makes no claims that would make me believe=
 otherwise.



[RJ] Since we have the P-Access-Network-Info as header that is also set up =
by the IMS entity P-CSCF with adding the network provided element there is =
a difference in interpreting the header by Applications. Of course the netw=
ork provided information is trustful and can be used for sensitive services=
 since the user provided information should only be used by services which =
are not sensitive.



[RJ] Is this sufficient?





Nits/editorial comments:



S1 Having the disclaimer as the first section is a little strange.  I don't=
 know what it is disclaiming yet.



[RJ] That is a copy from RFC3455. RFC3455 fullfills the requirements docume=
nted in RFC4083. Would this be sufficient to write as a one sentence statem=
ent?





S1, S3 It looks like a few characters are missing from these sections:

"trust.These", "environment The", "[RFC3455]   This"



[RJ] Done



The change log contains a lot of normative language.  I expected to see poi=
nters to changes, and maybe some justification, but items include normative=
-sounding text and no pointers(7), other contain pointers and duplicate tex=
t (3&4)



[RJ] tried to solve this. deleted normative text and made some corrections =
to your points.



Change log #6 notes the removal of a field; given that this is extensible, =
why not just mark the CDMA 2000 item deprecated instead of removing it?

[RJ] As far as I know is that 3GPP does not want to use it anymore. Is it n=
ot sufficent to not the deletion?


Best Regards

Roland

Von: Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
Gesendet: Donnerstag, 10. April 2014 01:08
An: draft-drage-sipping-rfc3455bis@tools.ietf.org<mailto:draft-drage-sippin=
g-rfc3455bis@tools.ietf.org>
Cc: Atle Monrad; Gonzalo Camarillo; Richard Barnes
Betreff: Fwd: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-13

Can you guys please respond to Martin's review?  This document is on the IE=
SG telechat agenda for tomorrow.  Honestly, you guys cannot complain that I=
ETF is not doing work in a timely manner if authors cannot respond to revie=
ws like this, especially at this stage of the game.

I will note that I haven't seen all the messages around these reviews becau=
se people don't usually add the shepherd and I don't seem to be being picke=
d up by any aliases.

Regards,
Mary.
---------- Forwarded message ----------
From: Martin Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.=
com>>
Date: Wed, Apr 9, 2014 at 11:39 AM
Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-13
To: Jari Arkko <jari.arkko@piuha.net<mailto:jari.arkko@piuha.net>>
Cc: "gen-art@ietf.org<mailto:gen-art@ietf.org> Review Team" <gen-art@ietf.o=
rg<mailto:gen-art@ietf.org>>, IESG IESG <iesg@ietf.org<mailto:iesg@ietf.org=
>>, draft-drage-sipping-rfc3455bis.all@tools.ietf.org<mailto:draft-drage-si=
pping-rfc3455bis.all@tools.ietf.org>
On 9 April 2014 05:41, Jari Arkko <jari.arkko@piuha.net<mailto:jari.arkko@p=
iuha.net>> wrote:
> Have there been any responses or changes based on your comments? I do not=
 see the document version having changed...
I have seen no response or revision.


--_000_7D2F7D7ADBA812449F25F4A69922881C167FCCE5ESESSMB203erics_
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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.Sprechblasentext, li.Sprechblasentext, div.Sprechblasentext
	{mso-style-name:Sprechblasentext;
	mso-style-link:"Sprechblasentext Zchn";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.SprechblasentextZchn
	{mso-style-name:"Sprechblasentext Zchn";
	mso-style-priority:99;
	mso-style-link:Sprechblasentext;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
p.NurText, li.NurText, div.NurText
	{mso-style-name:"Nur Text";
	mso-style-link:"Nur Text Zchn";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.NurTextZchn
	{mso-style-name:"Nur Text Zchn";
	mso-style-priority:99;
	mso-style-link:"Nur Text";
	font-family:Consolas;}
span.EmailStyle26
	{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:70.85pt 70.85pt 2.0cm 70.85pt;}
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">Thanks Roland<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">Mary, is the draft back o=
n track ??<br>
<br>
</span><span style=3D"font-size:11.0pt;font-family:Wingdings;color:#1F497D"=
>J</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D"><br>
<br>
/atle<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><b><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F=
497D">________________________________</span></b><span style=3D"font-size:1=
0.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D">
<br>
<br>
<br>
<b>Atle Monrad</b><br>
3GPP CT Chairman<br>
<br>
Group Function Technology &#8211; Standardization and Technical Regulation<=
/span><span style=3D"font-size:10.0pt;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:#1F497D"><br>
Ericsson</span><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-seri=
f&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-fa=
mily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o=
:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span 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;"> R.Jesske=
@telekom.de [mailto:R.Jesske@telekom.de]
<br>
<b>Sent:</b> 10. april 2014 10:07<br>
<b>To:</b> mary.ietf.barnes@gmail.com; draft-drage-sipping-rfc3455bis@tools=
.ietf.org; gen-art@ietf.org; jari.arkko@piuha.net; martin.thomson@gmail.com=
<br>
<b>Cc:</b> Atle Monrad; Gonzalo Camarillo; rlb@ipv.sx<br>
<b>Subject:</b> AW: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455=
bis-13<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:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Marry,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I&#8217;m really sorry, t=
his mail slipped through my hands. And I didn&#8217;t see anything in the d=
ata tracker history. Since I&#8217;m the main Editor, it is my fault that
 this was not answered.<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">It is true we cannot clai=
m any speed if we do nothing. Again I&#8217;m Sorry.<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">So here are my answers. F=
or the Gen-review.<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">So I have created a Versi=
on -14 which I can upload now. Please indicate if I should do this or if I =
should wait for further 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"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;<span lang=3D"DE"><a href=3D"http://wiki.tool=
s.ietf.org/area/gen/trac/wiki/GenArtfaq"><span lang=3D"EN-US">http://wiki.t=
ools.ietf.org/area/gen/trac/wiki/GenArtfaq</span></a></span>&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: draft-drage-sipping-rfc3455bis-13<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">Reviewer: Martin Thomson<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 2014-02-27<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 2014-03-14<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: (if known)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary: I find it strange that this 3GPP documen=
t is being published on the standards track.&nbsp; But since it's a -bis th=
ere is clearly precedent, and it is otherwise sound.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[RJ] Yes it is informal as RFC3455 is I&#8217;ll =
change that.<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">This document doesn't include enough information =
for me to some of the headers.&nbsp; For example, there isn't enough inform=
ation in the document to allow me to interpret the contents of cgi-3gpp:<o:=
p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; cgi-3gpp&nbsp;&nbsp;&nbsp;&nbsp; =3D &quot;cgi-3gpp&quot; EQUAL (toke=
n / quoted-string)<o:p></o:p></p>
<p class=3D"MsoPlainText">(I pick on P-Access-Network-Info, because I'm som=
ewhat familiar with it.)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This can probably be addressed by the inclusion o=
f appropriate normative references.&nbsp; I seem to recall there being a 3G=
PP TS that covered at least some of these.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">[RJ] Below that sectio=
n we have the text:
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack;background:white;mso-highlight:white">The access-info MAY contain addi=
tional information relating to the access network. The values for &quot;cgi=
-3gpp&quot;, &quot;utran-cell-id-3gpp&quot;,<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack;background:white;mso-highlight:white">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; &quot;i-wlan-node-id&quot;, &quot;dsl-location&quot; and &quot;ci-3gpp=
2&quot;, &quot;ci-3gpp2-femto&quot; and&nbsp; &quot;gstn-location&quot; are=
 defined in 3GPP TS 24.229</span><span style=3D"color:black"><o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack">Do we need more?</span><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">RFC 4244 is now obsolete, see 7044.&nbsp; (relate=
d nit: Change log entry #2 seems quite defensive, unnecessarily so.&nbsp; T=
his document only needs to define P-Called-Party-ID, and reference History-=
Info as an alternative<o:p></o:p></p>
<p class=3D"MsoPlainText">mechanism.)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[RJ] Replaced<o:p></o:p></p>
<p class=3D"MsoPlainText">[RJ] Due to your comment I have removed the whole=
 text as follows:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack;background:white;mso-highlight:white">Additionally the P-Called-Party-=
ID<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack;background:white;mso-highlight:white">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; header field has been defined within 3GPP systems since release<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack;background:white;mso-highlight:white">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; 5, and therefore it is realistic to expect implementations to be<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack;background:white;mso-highlight:white">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; already released to the field.&nbsp; It is therefore considered that<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack;background:white;mso-highlight:white">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; replacement of the P-Called-Party-ID header field within 3GPP<o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack;background:white;mso-highlight:white">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; systems causes more issues that it solves, and therefore the<o:p></o:p=
></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack;background:white;mso-highlight:white">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; update of RFC3455
</span><span style=3D"color:blue;background:white;mso-highlight:white">&lt;=
</span><span style=3D"color:maroon;background:white;mso-highlight:white">xr=
ef</span><span style=3D"color:red;background:white;mso-highlight:white"><o:=
p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:r=
ed;background:white;mso-highlight:white">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; target</span><span style=3D"color:blue;background:white;mso-=
highlight:white">=3D&quot;</span><span style=3D"color:black;background:whit=
e;mso-highlight:white">RFC3455</span><span style=3D"color:blue;background:w=
hite;mso-highlight:white">&quot;&gt;&lt;/</span><span style=3D"color:maroon=
;background:white;mso-highlight:white">xref</span><span style=3D"color:blue=
;background:white;mso-highlight:white">&gt;</span><span style=3D"color:blac=
k;background:white;mso-highlight:white">
 to remove the P-Called-Party-ID header field<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack;background:white;mso-highlight:white">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; will not be addressed.&nbsp; However it is recommended that any new<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"color:b=
lack;background:white;mso-highlight:white">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; usage of this type of functionality should use the History-Info<o:p></=
o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black;background:white;mso-h=
ighlight:white">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; header field defined i=
n RFC 7044
</span><span style=3D"color:blue;background:white;mso-highlight:white">&lt;=
</span><span style=3D"color:maroon;background:white;mso-highlight:white">xr=
ef</span><span style=3D"color:red;background:white;mso-highlight:white"> ta=
rget</span><span style=3D"color:blue;background:white;mso-highlight:white">=
=3D&quot;</span><span style=3D"color:black;background:white;mso-highlight:w=
hite">RFC7044</span><span style=3D"color:blue;background:white;mso-highligh=
t:white">&quot;&gt;&lt;/</span><span style=3D"color:maroon;background:white=
;mso-highlight:white">xref</span><span style=3D"color:blue;background:white=
;mso-highlight:white">&gt;</span><span style=3D"color:black;background:whit=
e;mso-highlight:white">rather
 than the P-Called-Party-ID header field</span><span style=3D"color:black">=
<o:p></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">Change log entry #5, mentions a shortcoming of 34=
55 (no registry for access network types), but the draft does nothing about=
 it.&nbsp; It seems to be propagating the mistake it notes.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[RJ] Yes I can agree this. so this seems a action=
 for future.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">A lot has happened since RFC 3455 was published.&=
nbsp; The privacy considerations around the use of P-Access-Network-Info ar=
e unchanged from their pre-Geopriv form.&nbsp; In particular, I find the UA=
 knowledge part to be problematic; Geopriv definitions
 can probably help here.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[RJ] sorry cannot do <o:p></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"MsoPlainText">S6.1 P-Associated-URI is a powerful linkability v=
ector, which could be a far more serious privacy leak than the text implies=
.&nbsp; The following seems like good advice, but is not sufficient:<o:p></=
o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; An eavesdropper could possibly colle=
ct the list of identities a user<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; is registered.&nbsp; This can have p=
rivacy implications.&nbsp; To mitigate this<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; problem, this extension SHOULD only =
be used in a secured environment,<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; where encryption of SIP messages is =
provided either end-to-end or<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; hop-by-hop.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">You also have to trust the other end of the hop w=
ith the information.<o:p></o:p></p>
<p class=3D"MsoPlainText">I think that's implicit, but probably needs to be=
 stated.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[RJ] I have addedthe following:<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:black;background:white;mso-h=
ighlight:white">And where a trustrelationship equivalent with that defined =
in RFC 3325
</span><span style=3D"color:blue;background:white;mso-highlight:white">&lt;=
</span><span style=3D"color:maroon;background:white;mso-highlight:white">xr=
ef</span><span style=3D"color:red;background:white;mso-highlight:white"> ta=
rget</span><span style=3D"color:blue;background:white;mso-highlight:white">=
=3D&quot;</span><span style=3D"color:black;background:white;mso-highlight:w=
hite">RFC3325</span><span style=3D"color:blue;background:white;mso-highligh=
t:white">&quot;&gt;</span><span style=3D"color:black;background:white;mso-h=
ighlight:white">between
 entities exist</span><span style=3D"color:black"><o:p></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">S6.4&nbsp; This claim sounds false to me:<o:p></o=
:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; However, there<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; are no security problems resulting f=
rom a UA inserting incorrect<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; information.&nbsp; Networks providin=
g services based on the information<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; carried in the P-Access-Network-Info=
 header field will therefore need<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; to trust the UA sending the informat=
ion.&nbsp; A rogue UA sending false<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; access network information will do n=
o more harm than to restrict the<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; user from using certain services.<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Any parameter whereby changing it can cause loss =
of service is likely to be true in the inverse.&nbsp; The draft makes no cl=
aims that would make me believe otherwise.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[RJ] Since we have the P-Access-Network-Info as h=
eader that is also set up by the IMS entity P-CSCF with adding the network =
provided element there is a difference in interpreting the header by Applic=
ations. Of course the network provided
 information is trustful and can be used for sensitive services since the u=
ser provided information should only be used by services which are not sens=
itive.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[RJ] Is this sufficient?<o:p></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"MsoPlainText">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">S1 Having the disclaimer as the first section is =
a little strange.&nbsp; I don't know what it is disclaiming yet.<o:p></o:p>=
</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[RJ] That is a copy from RFC3455. RFC3455 fullfil=
ls the requirements documented in RFC4083. Would this be sufficient to writ=
e as a one sentence statement?<o:p></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"MsoPlainText">S1, S3 It looks like a few characters are missing=
 from these sections:<o:p></o:p></p>
<p class=3D"MsoPlainText">&quot;trust.These&quot;, &quot;environment The&qu=
ot;, &quot;[RFC3455]&nbsp;&nbsp; This&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[RJ] Done<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The change log contains a lot of normative langua=
ge.&nbsp; I expected to see pointers to changes, and maybe some justificati=
on, but items include normative-sounding text and no pointers(7), other con=
tain pointers and duplicate text (3&amp;4)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[RJ] tried to solve this. deleted normative text =
and made some corrections to your points.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Change log #6 notes the removal of a field; given=
 that this is extensible, why not just mark the CDMA 2000 item deprecated i=
nstead of removing it?<o:p></o:p></p>
<p class=3D"MsoPlainText">[RJ] As far as I know is that 3GPP does not want =
to use it anymore. Is it not sufficent to not the deletion?<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>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best Regards<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><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">Roland<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"DE" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">Von:</span></b><span lang=
=3D"DE" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans=
-serif&quot;"> Mary Barnes [<a href=3D"mailto:mary.ietf.barnes@gmail.com">m=
ailto:mary.ietf.barnes@gmail.com</a>]
<br>
<b>Gesendet:</b> Donnerstag, 10. April 2014 01:08<br>
<b>An:</b> <a href=3D"mailto:draft-drage-sipping-rfc3455bis@tools.ietf.org"=
>draft-drage-sipping-rfc3455bis@tools.ietf.org</a><br>
<b>Cc:</b> Atle Monrad; Gonzalo Camarillo; Richard Barnes<br>
<b>Betreff:</b> Fwd: [Gen-art] Gen-ART review of draft-drage-sipping-rfc345=
5bis-13<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"DE"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"DE">Can you guys please respond to Mar=
tin's review? &nbsp;This document is on the IESG telechat agenda for tomorr=
ow. &nbsp;Honestly, you guys cannot complain that IETF is not doing work in=
 a timely manner if authors cannot respond to
 reviews like this, especially at this stage of the game.&nbsp;<o:p></o:p><=
/span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"DE"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"DE">I will note that I haven't seen al=
l the messages around these reviews because people don't usually add the sh=
epherd and I don't seem to be being picked up by any aliases.&nbsp;<o:p></o=
:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"DE"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"DE">Regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"DE">Mar=
y.&nbsp;<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"DE">---=
------- Forwarded message ----------<br>
From: <b>Martin Thomson</b> &lt;<a href=3D"mailto:martin.thomson@gmail.com"=
>martin.thomson@gmail.com</a>&gt;<br>
Date: Wed, Apr 9, 2014 at 11:39 AM<br>
Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-13<=
br>
To: Jari Arkko &lt;<a href=3D"mailto:jari.arkko@piuha.net">jari.arkko@piuha=
.net</a>&gt;<br>
Cc: &quot;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a> Review T=
eam&quot; &lt;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;,=
 IESG IESG &lt;<a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;,
<a href=3D"mailto:draft-drage-sipping-rfc3455bis.all@tools.ietf.org">draft-=
drage-sipping-rfc3455bis.all@tools.ietf.org</a><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"DE">On =
9 April 2014 05:41, Jari Arkko &lt;<a href=3D"mailto:jari.arkko@piuha.net">=
jari.arkko@piuha.net</a>&gt; wrote:<br>
&gt; Have there been any responses or changes based on your comments? I do =
not see the document version having changed...<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"DE">I h=
ave seen no response or revision.<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"DE"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_7D2F7D7ADBA812449F25F4A69922881C167FCCE5ESESSMB203erics_--


From nobody Thu Apr 10 03:56:41 2014
Return-Path: <gonzalo.camarillo@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 204371A0687 for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 03:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.24
X-Spam-Level: 
X-Spam-Status: No, score=-101.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, USER_IN_WHITELIST=-100] 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 BHIQWsxNubXX for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 03:56:35 -0700 (PDT)
Received: from sesbmg21.mgmt.ericsson.se (sesbmg21.ericsson.net [193.180.251.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5E8001A01C5 for <gen-art@ietf.org>; Thu, 10 Apr 2014 03:56:33 -0700 (PDT)
X-AuditID: c1b4fb31-b7f688e000003e64-5c-534678e0bb9e
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id C5.76.15972.0E876435; Thu, 10 Apr 2014 12:56:32 +0200 (CEST)
Received: from [131.160.36.126] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.32) with Microsoft SMTP Server id 14.3.174.1; Thu, 10 Apr 2014 12:56:32 +0200
Message-ID: <534678DF.60603@ericsson.com>
Date: Thu, 10 Apr 2014 13:56:31 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: <R.Jesske@telekom.de>, <mary.ietf.barnes@gmail.com>, <draft-drage-sipping-rfc3455bis@tools.ietf.org>, <gen-art@ietf.org>, <jari.arkko@piuha.net>, <martin.thomson@gmail.com>
References: <CABkgnnVVQCAz=ixeR04rc75Vc-rL2JFQcjT0-hX_UCL-c=FGjQ@mail.gmail.com>	<5F92FD08-1636-48C0-9634-8806E9F577FF@piuha.net>	<CABkgnnUdkHYxGnFOkaHf-Xc+v=UYiASBS7KBJeC75aEV1SyKMA@mail.gmail.com> <CAHBDyN5a+S-1QUzD0eWpkxMdT0tBZ9_DZELM1FKuutmXNk8a0g@mail.gmail.com> <058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6F@HE113667.emea1.cds.t-internal.com>
In-Reply-To: <058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6F@HE113667.emea1.cds.t-internal.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrPLMWRmVeSWpSXmKPExsUyM+Jvje6DCrdggwcLjSwaTvewW1x99ZnF Ysa+FWwW1878Y7T4vH8/s0XTnS42i6l9tg7sHjtn3WX3WLLkJ5PH5I2zWDy2LpnO5tH2UsHj y+XPbAFsUVw2Kak5mWWpRfp2CVwZd34/Zi2Y61Hx8+M59gbGC2ZdjJwcEgImEi0Pd7NA2GIS F+6tZ+ti5OIQEjjJKLH2xkxWCGcNo8S7o9cYQap4BTQltnfPZgaxWQRUJR6t6wCLswlYSGy5 dR9skqhAlET3pEfsEPWCEidnPmEBGSQisIVR4vrM+WAJZgEdiQUHOsAGCQv4SWxa/RZq9R0m iXe/poEVcQrESqz9MBMowQF0n7hET2MQRK+BxJFFc1ghbHmJ5q0QBwkJaEssf9bCMoFRaBaS 3bOQtMxC0rKAkXkVo2RxanFSbrqRoV5uem6JXmpRZnJxcX6eXnHqJkZgpBzc8ttwB+PEa/aH GKU5WJTEeRmmdwYJCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYPTpyHiQrBWttqW4fkNL7kOO vgeMN6fuuHNhy9O9R7hZeOIWM6QZrtT6OvPDX+t7dqc/3qp7Oi17v9LdzwdM3/FOjd9haVZS MPFGXva/WY+D9eTOdf/brtLxuOJrqZjw/LNnVf7euV9xtIrf/BT3otJK3zMPWG88PrTYrLTm 77lzXu8LhJxzdhYrsRRnJBpqMRcVJwIAYYhS5WICAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/ofqd2YN5F-Oz1FPBX91BUMPfpQs
Cc: atle.monrad@ericsson.com, rlb@ipv.sx
Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-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: Thu, 10 Apr 2014 10:56:39 -0000

Hi Roland,

do not update the draft until the AD tells you so.

Cheers,

Gonzalo

On 10/04/2014 11:07 AM, R.Jesske@telekom.de wrote:
> Hi Marry,
> 
> I’m really sorry, this mail slipped through my hands. And I didn’t see
> anything in the data tracker history. Since I’m the main Editor, it is
> my fault that this was not answered.
> 
> It is true we cannot claim any speed if we do nothing. Again I’m Sorry.
> 
>  
> 
> So here are my answers. For the Gen-review.
> 
> So I have created a Version -14 which I can upload now. Please indicate
> if I should do this or if I should wait for further comments?
> 
>  
> 
> I am the assigned Gen-ART 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-drage-sipping-rfc3455bis-13
> 
> Reviewer: Martin Thomson
> 
> Review Date: 2014-02-27
> 
> IETF LC End Date: 2014-03-14
> 
> IESG Telechat date: (if known)
> 
>  
> 
> Summary: I find it strange that this 3GPP document is being published on
> the standards track.  But since it's a -bis there is clearly precedent,
> and it is otherwise sound.
> 
>  
> 
> [RJ] Yes it is informal as RFC3455 is I’ll change that.
> 
>  
> 
> Major issues:
> 
>  
> 
> This document doesn't include enough information for me to some of the
> headers.  For example, there isn't enough information in the document to
> allow me to interpret the contents of cgi-3gpp:
> 
>           cgi-3gpp     = "cgi-3gpp" EQUAL (token / quoted-string)
> 
> (I pick on P-Access-Network-Info, because I'm somewhat familiar with it.)
> 
>  
> 
> This can probably be addressed by the inclusion of appropriate normative
> references.  I seem to recall there being a 3GPP TS that covered at
> least some of these.
> 
>  
> 
> [RJ] Below that section we have the text:
> 
> The access-info MAY contain additional information relating to the
> access network. The values for "cgi-3gpp", "utran-cell-id-3gpp",
> 
>        "i-wlan-node-id", "dsl-location" and "ci-3gpp2", "ci-3gpp2-femto"
> and  "gstn-location" are defined in 3GPP TS 24.229
> 
>  
> 
> Do we need more?
> 
>  
> 
> Minor issues:
> 
>  
> 
> RFC 4244 is now obsolete, see 7044.  (related nit: Change log entry #2
> seems quite defensive, unnecessarily so.  This document only needs to
> define P-Called-Party-ID, and reference History-Info as an alternative
> 
> mechanism.)
> 
>  
> 
> [RJ] Replaced
> 
> [RJ] Due to your comment I have removed the whole text as follows:
> 
> Additionally the P-Called-Party-ID
> 
>        header field has been defined within 3GPP systems since release
> 
>        5, and therefore it is realistic to expect implementations to be
> 
>        already released to the field.  It is therefore considered that
> 
>        replacement of the P-Called-Party-ID header field within 3GPP
> 
>        systems causes more issues that it solves, and therefore the
> 
>        update of RFC3455 <xref
> 
>          target="RFC3455"></xref>to remove the P-Called-Party-ID header
> field
> 
>        will not be addressed.  However it is recommended that any new
> 
>        usage of this type of functionality should use the History-Info
> 
>        header field defined in RFC 7044
> <xreftarget="RFC7044"></xref>rather than the P-Called-Party-ID header field
> 
>  
> 
>  
> 
> Change log entry #5, mentions a shortcoming of 3455 (no registry for
> access network types), but the draft does nothing about it.  It seems to
> be propagating the mistake it notes.
> 
>  
> 
> [RJ] Yes I can agree this. so this seems a action for future.
> 
>  
> 
> A lot has happened since RFC 3455 was published.  The privacy
> considerations around the use of P-Access-Network-Info are unchanged
> from their pre-Geopriv form.  In particular, I find the UA knowledge
> part to be problematic; Geopriv definitions can probably help here.
> 
>  
> 
> [RJ] sorry cannot do
> 
>  
> 
>  
> 
> S6.1 P-Associated-URI is a powerful linkability vector, which could be a
> far more serious privacy leak than the text implies.  The following
> seems like good advice, but is not sufficient:
> 
>  
> 
>    An eavesdropper could possibly collect the list of identities a user
> 
>    is registered.  This can have privacy implications.  To mitigate this
> 
>    problem, this extension SHOULD only be used in a secured environment,
> 
>    where encryption of SIP messages is provided either end-to-end or
> 
>    hop-by-hop.
> 
>  
> 
> You also have to trust the other end of the hop with the information.
> 
> I think that's implicit, but probably needs to be stated.
> 
>  
> 
> [RJ] I have addedthe following:
> 
> And where a trustrelationship equivalent with that defined in RFC 3325
> <xreftarget="RFC3325">between entities exist
> 
>  
> 
>  
> 
> S6.4  This claim sounds false to me:
> 
>  
> 
>    However, there
> 
>    are no security problems resulting from a UA inserting incorrect
> 
>    information.  Networks providing services based on the information
> 
>    carried in the P-Access-Network-Info header field will therefore need
> 
>    to trust the UA sending the information.  A rogue UA sending false
> 
>    access network information will do no more harm than to restrict the
> 
>    user from using certain services.
> 
>  
> 
> Any parameter whereby changing it can cause loss of service is likely to
> be true in the inverse.  The draft makes no claims that would make me
> believe otherwise.
> 
>  
> 
> [RJ] Since we have the P-Access-Network-Info as header that is also set
> up by the IMS entity P-CSCF with adding the network provided element
> there is a difference in interpreting the header by Applications. Of
> course the network provided information is trustful and can be used for
> sensitive services since the user provided information should only be
> used by services which are not sensitive.
> 
>  
> 
> [RJ] Is this sufficient?
> 
>  
> 
>  
> 
> Nits/editorial comments:
> 
>  
> 
> S1 Having the disclaimer as the first section is a little strange.  I
> don't know what it is disclaiming yet.
> 
>  
> 
> [RJ] That is a copy from RFC3455. RFC3455 fullfills the requirements
> documented in RFC4083. Would this be sufficient to write as a one
> sentence statement?
> 
>  
> 
>  
> 
> S1, S3 It looks like a few characters are missing from these sections:
> 
> "trust.These", "environment The", "[RFC3455]   This"
> 
>  
> 
> [RJ] Done
> 
>  
> 
> The change log contains a lot of normative language.  I expected to see
> pointers to changes, and maybe some justification, but items include
> normative-sounding text and no pointers(7), other contain pointers and
> duplicate text (3&4)
> 
>  
> 
> [RJ] tried to solve this. deleted normative text and made some
> corrections to your points.
> 
>  
> 
> Change log #6 notes the removal of a field; given that this is
> extensible, why not just mark the CDMA 2000 item deprecated instead of
> removing it?
> 
> [RJ] As far as I know is that 3GPP does not want to use it anymore. Is
> it not sufficent to not the deletion?
> 
>  
> 
>  
> 
> Best Regards
> 
>  
> 
> Roland
> 
>  
> 
> *Von:*Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
> *Gesendet:* Donnerstag, 10. April 2014 01:08
> *An:* draft-drage-sipping-rfc3455bis@tools.ietf.org
> *Cc:* Atle Monrad; Gonzalo Camarillo; Richard Barnes
> *Betreff:* Fwd: [Gen-art] Gen-ART review of
> draft-drage-sipping-rfc3455bis-13
> 
>  
> 
> Can you guys please respond to Martin's review?  This document is on the
> IESG telechat agenda for tomorrow.  Honestly, you guys cannot complain
> that IETF is not doing work in a timely manner if authors cannot respond
> to reviews like this, especially at this stage of the game. 
> 
>  
> 
> I will note that I haven't seen all the messages around these reviews
> because people don't usually add the shepherd and I don't seem to be
> being picked up by any aliases. 
> 
>  
> 
> Regards,
> 
> Mary. 
> 
> ---------- Forwarded message ----------
> From: *Martin Thomson* <martin.thomson@gmail.com
> <mailto:martin.thomson@gmail.com>>
> Date: Wed, Apr 9, 2014 at 11:39 AM
> Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-13
> To: Jari Arkko <jari.arkko@piuha.net <mailto:jari.arkko@piuha.net>>
> Cc: "gen-art@ietf.org <mailto:gen-art@ietf.org> Review Team"
> <gen-art@ietf.org <mailto:gen-art@ietf.org>>, IESG IESG <iesg@ietf.org
> <mailto:iesg@ietf.org>>,
> draft-drage-sipping-rfc3455bis.all@tools.ietf.org
> <mailto:draft-drage-sipping-rfc3455bis.all@tools.ietf.org>
> 
> On 9 April 2014 05:41, Jari Arkko <jari.arkko@piuha.net
> <mailto:jari.arkko@piuha.net>> wrote:
>> Have there been any responses or changes based on your comments? I do
> not see the document version having changed...
> 
> I have seen no response or revision.
> 
>  
> 


From nobody Thu Apr 10 07:15:30 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 113C51A02A3 for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 07:15:24 -0700 (PDT)
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, 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 XjGebdZHM5SA for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 07:15:19 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id DDD731A029F for <gen-art@ietf.org>; Thu, 10 Apr 2014 07:15:18 -0700 (PDT)
X-AuditID: c1b4fb25-b7f3b8e0000006f1-8d-5346a774b10e
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 37.23.01777.477A6435; Thu, 10 Apr 2014 16:15:17 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.3.174.1; Thu, 10 Apr 2014 16:15:16 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 81DEE1101FF; Thu, 10 Apr 2014 17:15:16 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 83CAF5723D;	Thu, 10 Apr 2014 17:15:15 +0300 (EEST)
Received: from [IPv6:::1] (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id ED7ED50679;	Thu, 10 Apr 2014 17:15:14 +0300 (EEST)
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: <058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6F@HE113667.emea1.cds.t-internal.com>
Date: Thu, 10 Apr 2014 17:15:15 +0300
Content-Transfer-Encoding: quoted-printable
Message-ID: <74C1B909-BE20-434E-85FD-B866FC855D8A@piuha.net>
References: <CABkgnnVVQCAz=ixeR04rc75Vc-rL2JFQcjT0-hX_UCL-c=FGjQ@mail.gmail.com> <5F92FD08-1636-48C0-9634-8806E9F577FF@piuha.net> <CABkgnnUdkHYxGnFOkaHf-Xc+v=UYiASBS7KBJeC75aEV1SyKMA@mail.gmail.com> <CAHBDyN5a+S-1QUzD0eWpkxMdT0tBZ9_DZELM1FKuutmXNk8a0g@mail.gmail.com> <058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6F@HE113667.emea1.cds.t-internal.com>
To: <R.Jesske@telekom.de>
X-Mailer: Apple Mail (2.1510)
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyM+JvjW7pcrdgg42PeCwaTvewW1x99ZnF 4tqZf4wWn/fvZ7ZoutPFZjG1z9aBzWPnrLvsHkuW/GTymLxxFotH20sFjy+XP7MFsEZx2aSk 5mSWpRbp2yVwZdy/MZepYL9ZxfQnV9kaGDu0uxg5OSQETCS2fm5khbDFJC7cW88GYgsJHGaU WNeq3MXIBWRvYJQ4eWITG4Szl1Fi2cdFLBBV6xgl5n2whkjMY5RYMKMNbBSzgIHEkUVzwGxe AT2J54+/gjUIC3hJ3Dl/jB3EZhNQl/hw8xKYzSkQK7H2w0yw1SwCqhKbTlxnhJhzmVFiyptg CFtbYtnC18wQM20kzvy7xQpxxB0miesbOEBsEQFJiSs3uqHekZU4fe45C4StJnH13CZmiHpF iYn3t7NNYBSdheTUWUhOnYVk3QJG5lWM7LmJmTnp5UabGIGRc3DLb9UdjHfOiRxilOZgURLn /fDWOUhIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDY3dAyxG5/khdzv6d91+cYbl6lWXFjzkq zjMTSkNfNnnMn9uQv+n82vkvb+vOl8zd8fBr+RaDEP/jLDzBLrU/Gv56nk/uVTioXrdVRu/v M5U9Rn8nb/ix9C7jGr7VDqX/J8Y3sx1ifaPCHSGolXRiyrGHKW1cGm2MZ0/X73Dj+cWheTNX u1VFQYmlOCPRUIu5qDgRALU+SKNqAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/FrSz46ofkjC9vZd11dX1l0tW_rg
Cc: rlb@ipv.sx, gen-art@ietf.org, gonzalo.camarillo@ericsson.com, draft-drage-sipping-rfc3455bis@tools.ietf.org, atle.monrad@ericsson.com, mary.ietf.barnes@gmail.com
Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-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: Thu, 10 Apr 2014 14:15:24 -0000

Roland,

Thanks for your responses. I think these are generally to the right =
direction, I have commented below where I think some further discussion =
is needed.

On Apr 10, 2014, at 11:07 AM, R.Jesske@telekom.de wrote:

> Hi Marry,
> I=92m really sorry, this mail slipped through my hands. And I didn=92t =
see anything in the data tracker history. Since I=92m the main Editor, =
it is my fault that this was not answered.
> It is true we cannot claim any speed if we do nothing. Again I=92m =
Sorry.
>=20
> So here are my answers. For the Gen-review.
> So I have created a Version -14 which I can upload now. Please =
indicate if I should do this or if I should wait for further comments?
>=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-drage-sipping-rfc3455bis-13
> Reviewer: Martin Thomson
> Review Date: 2014-02-27
> IETF LC End Date: 2014-03-14
> IESG Telechat date: (if known)
>=20
> Summary: I find it strange that this 3GPP document is being published =
on the standards track.  But since it's a -bis there is clearly =
precedent, and it is otherwise sound.
>=20
> [RJ] Yes it is informal as RFC3455 is I=92ll change that.

It is published for informational according to the last call =
announcement, and I can't find any statement from the draft that this =
would be on the standards track.

> Major issues:
>=20
> This document doesn't include enough information for me to some of the =
headers.  For example, there isn't enough information in the document to =
allow me to interpret the contents of cgi-3gpp:
>          cgi-3gpp     =3D "cgi-3gpp" EQUAL (token / quoted-string)
> (I pick on P-Access-Network-Info, because I'm somewhat familiar with =
it.)
>=20
> This can probably be addressed by the inclusion of appropriate =
normative references.  I seem to recall there being a 3GPP TS that =
covered at least some of these.
>=20
> [RJ] Below that section we have the text:
> The access-info MAY contain additional information relating to the =
access network. The values for "cgi-3gpp", "utran-cell-id-3gpp",
>       "i-wlan-node-id", "dsl-location" and "ci-3gpp2", =
"ci-3gpp2-femto" and  "gstn-location" are defined in 3GPP TS 24.229
>=20
> Do we need more?

I think this is fine.

But would anyone mind if 24.229 was a normative reference? In my mind I =
need to read it to understand what to put into these attributes.

> Minor issues:
>=20
> RFC 4244 is now obsolete, see 7044.  (related nit: Change log entry #2 =
seems quite defensive, unnecessarily so.  This document only needs to =
define P-Called-Party-ID, and reference History-Info as an alternative
> mechanism.)
>=20
> [RJ] Replaced
> [RJ] Due to your comment I have removed the whole text as follows:
> Additionally the P-Called-Party-ID
>       header field has been defined within 3GPP systems since release
>       5, and therefore it is realistic to expect implementations to be
>       already released to the field.  It is therefore considered that
>       replacement of the P-Called-Party-ID header field within 3GPP
>       systems causes more issues that it solves, and therefore the
>       update of RFC3455 <xref
>         target=3D"RFC3455"></xref> to remove the P-Called-Party-ID =
header field
>       will not be addressed.  However it is recommended that any new
>       usage of this type of functionality should use the History-Info
>       header field defined in RFC 7044 <xref =
target=3D"RFC7044"></xref>rather than the P-Called-Party-ID header field

OK for me.

> Change log entry #5, mentions a shortcoming of 3455 (no registry for =
access network types), but the draft does nothing about it.  It seems to =
be propagating the mistake it notes.
>=20
> [RJ] Yes I can agree this. so this seems a action for future.

Yes.

>=20
> A lot has happened since RFC 3455 was published.  The privacy =
considerations around the use of P-Access-Network-Info are unchanged =
from their pre-Geopriv form.  In particular, I find the UA knowledge =
part to be problematic; Geopriv definitions can probably help here.
>=20
> [RJ] sorry cannot do=20

I think a better approach would be to describe the issues, rather than =
try to change what the implementations do, if that is what you meant by =
using Geopriv definitions.

> S6.1 P-Associated-URI is a powerful linkability vector, which could be =
a far more serious privacy leak than the text implies.  The following =
seems like good advice, but is not sufficient:
>=20
>   An eavesdropper could possibly collect the list of identities a user
>   is registered.  This can have privacy implications.  To mitigate =
this
>   problem, this extension SHOULD only be used in a secured =
environment,
>   where encryption of SIP messages is provided either end-to-end or
>   hop-by-hop.
>=20
> You also have to trust the other end of the hop with the information.
> I think that's implicit, but probably needs to be stated.
>=20
> [RJ] I have addedthe following:
> And where a trustrelationship equivalent with that defined in RFC 3325 =
<xref target=3D"RFC3325">between entities exist

This is good, but I'd be even more explicit. Maybe add "That is, the =
privacy of the user relies on the other entities in the session not =
disclosing information that they have learned about the user.

>=20
> S6.4  This claim sounds false to me:
>=20
>   However, there
>   are no security problems resulting from a UA inserting incorrect
>   information.  Networks providing services based on the information
>   carried in the P-Access-Network-Info header field will therefore =
need
>   to trust the UA sending the information.  A rogue UA sending false
>   access network information will do no more harm than to restrict the
>   user from using certain services.
>=20
> Any parameter whereby changing it can cause loss of service is likely =
to be true in the inverse.  The draft makes no claims that would make me =
believe otherwise.
>=20
> [RJ] Since we have the P-Access-Network-Info as header that is also =
set up by the IMS entity P-CSCF with adding the network provided element =
there is a difference in interpreting the header by Applications. Of =
course the network provided information is trustful and can be used for =
sensitive services since the user provided information should only be =
used by services which are not sensitive.
>=20
> [RJ] Is this sufficient?

I feel that this may need more explanation. If you point was that the =
P-CSCF adds information that is trustworthy and leads to discovery of =
false information planted by the rogue UA, then maybe we should be =
explicit about this.

Jari


From nobody Thu Apr 10 07:43:22 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 31E061A0224 for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 07:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 hrk7zgMMcKHS for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 07:43:17 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CDF431A01AD for <gen-art@ietf.org>; Thu, 10 Apr 2014 07:43:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DBF052CC64; Thu, 10 Apr 2014 17:43:14 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4D2rG-R2-IbN; Thu, 10 Apr 2014 17:43:12 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 9E9FE2CC61; Thu, 10 Apr 2014 17:43:12 +0300 (EEST)
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: <7594FB04B1934943A5C02806D1A2204B1D2772AF@ESESSMB209.ericsson.se>
Date: Thu, 10 Apr 2014 17:43:12 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD8F4BC4-BC80-4B31-A6C9-4A0561751CAE@piuha.net>
References: <7594FB04B1934943A5C02806D1A2204B1D2772AF@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/z7aOFz7isgCfNI6zGPBxcJPpWGU
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pcp-dhcp.all@tools.ietf.org" <draft-ietf-pcp-dhcp.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-pcp-dhcp-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, 10 Apr 2014 14:43:21 -0000

Christer et al: thank you for the review and the changes!

Jari

On Apr 4, 2014, at 10:43 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-pcp-dhcp-11.txt
>=20
> Reviewer:                               Christer Holmberg
>=20
> Review Date:                          4 April 2014
>=20
> IETF LC End Date:                1 April 2014
>=20
> IESG Telechat date:               10 April 2014
>=20
> =20
>=20
> Summary:                               My review comments on a =
previous version (-09) of the document have been addressed, and the =
document is now ready for publication.
>=20
> Major issues: -
>=20
> Minor issues: -
>=20
> Nits/editorial comments: -
>=20
> =20
>=20
> Regards,
>=20
> Christer=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Thu Apr 10 09:12:59 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 121651A0289; Thu, 10 Apr 2014 09:12:56 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 hdXmW-Dz-JZW; Thu, 10 Apr 2014 09:12:54 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 1ABE31A01FF; Thu, 10 Apr 2014 09:12:53 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3AGCpBa028824; Thu, 10 Apr 2014 17:12:52 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3AGCova028807 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 10 Apr 2014 17:12:51 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Robert Sparks'" <rjsparks@nostrum.com>, "'General Area Review Team'" <gen-art@ietf.org>, <draft-ietf-l2vpn-vpls-ldp-mac-opt@tools.ietf.org>, <l2vpn@ietf.org>
References: <5342FF4F.4040906@nostrum.com>
In-Reply-To: <5342FF4F.4040906@nostrum.com>
Date: Thu, 10 Apr 2014 17:12:51 +0100
Message-ID: <031f01cf54d7$b9432180$2bc96480$@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: AQJXXrgC05DloNvZAOm6v9OnzzYQ25n68DpQ
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20624.000
X-TM-AS-Result: No--20.850-10.0-31-10
X-imss-scan-details: No--20.850-10.0-31-10
X-TMASE-MatchedRID: cxtZ8fwm3r+nykMun0J1wvAjkTMkRNNUkclKpZaEedradW4iYSMjUeO7 Q9MS0NLni4zi2tMdmf5/129x0+dDBxME5sXUqWznbMGKOuLn5FU7Uh8Mo43jSVMnnsDzMI/0AMN ZJLKWqgY8ivFkadaiTVJ0nehpZ2rrXV8zTKunnsn7/v/5alNYetRmti/O6j0CRJWmeOMHa+SlQa x3ye0WRV0+aUSxlEKolCdkhztc19MmH3w4SvLIydjko+KiQPUGVo4lwLFUdisxCa3oFeZrRXLOA PNCmmpA8MaosETR+4LwIQ8TEKBvAHZ4WhytKCEOiUPZPmKZOQmWesyrtKuK7fgnJH5vm2+g33pz MsMDyh+4iy5ozcFtGbi4+LWAODipFDysHLls3CSGwT67eecJ8PDYQQsX+kfDN/M32cK+fkhpRez oWC5XLY7b6FbuI0+YDmIE4Tvg5l9bmMYrRJDeAk+4wmL9kCTxy1y/jIuoZZ4nFcnAoAp5r9V2ks C4+totJRrVLqjmxpfxeKURfJizjF/wr9J3woyTbD4iYfbCo2ND3kXYiJVSRKJpFCjCjSYrF5ZRT dcETVTi8zVgXoAltlwtzewu2M63VkVZa47CjvDdB/CxWTRRuyUIayx+Skid
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/QT3yBFPU_m_RHECDqtK9N6WLl4A
Subject: Re: [Gen-art] Gen-art LC review: draft-ietf-l2vpn-vpls-ldp-mac-opt-11
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: Thu, 10 Apr 2014 16:12:56 -0000

Thanks Robert,

Will be interested to hear author/shepherd responses to this.

Adrian

> -----Original Message-----
> From: L2vpn [mailto:l2vpn-bounces@ietf.org] On Behalf Of Robert Sparks
> Sent: 07 April 2014 20:41
> To: General Area Review Team;
draft-ietf-l2vpn-vpls-ldp-mac-opt@tools.ietf.org;
> l2vpn@ietf.org
> Subject: Gen-art LC review: draft-ietf-l2vpn-vpls-ldp-mac-opt-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-l2vpn-vpls-ldp-mac-opt-11
> Reviewer: Robert Sparks
> Review Date: 7Apr2014
> IETF LC End Date: 8Apr2014
> IESG Telechat date: not yet scheduled
> 
> Summary: This draft is almost ready for publication as a Proposed
> Standard, but has minor issues (primarily editorial) that should be
> addressed.
> 
> I found this document very difficult to read. It asks the reader to hop
> between sections in unusual ways (for instance, it sends the reader to
> the problem statement section for details on normative behavior). I
> strongly encourage an editorial pass focusing on document structure.
> 
> There are many instances of SHOULD in the document where the text should
> just be using prose instead. It's not always clear when an
> implementation would choose to ignore the SHOULD, and what the
> consequences of that choice would be.
> 
> The document is inconsistent about the level of support needed in the
> network before trying to use this extension.
> Section 5.1.2 says the assumption is everything understands it before
> it's turned on. Section 6 points back to figure 2 and says
> to use the extension over the pw where you administratively know the
> peer supports the extension, and fall back to 4762 for
> everything else. Which of those did you intend?
> 
> Specific comments in document order:
> 
> Section 3.2 paragraph 1: This paragraph would benefit from being broken
> into several. It's hard to find its point. The SHOULD in this paragraph
> is probably not a 2119 SHOULD (this section isn't defining the
> protocol). It would be useful in this overview to explicitly say _why_
> "This cannot be achieved with ... 4762]" at this point in the document.
> 
> Section 3.2 paragraph 2: This SHOULD _is_ defining protocol - shouldn't
> it be in section 5?
> 
> Section 4.1.1 paragraph 3: It took me some time to find Z on the figure.
> It might help to introduce it similar to how you introduce X.
> 
> Section 4.1.2: paragraph 1: I think you meant to reference 4.1.1
> 
> Section 5: The first sentence talks about requirements in section 4.
> Section 4 describes a problem using some examples but doesn't explicitly
> call out requirements. Doing so would help the document.
> 
> Last sentence in 5.1.1 (and several other places in the document):
> Please add an article before "MAC Flush message".  (I apologize for such
> a small nit, but each of these instances made making sure I was reading
> what the sentence intended significantly more difficult).
> 
> Section 5.1.2 first paragraph: This section is defining behavior - why
> are you sending the reader back into the problem statement for detail on
> the behavior?
> 
> 5.1.2 paragraph 2: You meant section 6, not 5.
> 
> 5.1.2 paragraph 3: I can't follow this paragraph's structure. I think
> you're trying to say "An MTU-s or PE2-rs SHOULD send MAC withdraw
> messages as defined in [RFC4762] in cases where the network is being
> upgraded and devices are not capable of understanding the optimized MAC
> flush." (But if so, the next sentence is redundant.) Why is this SHOULD?
> 
> 5.1.3 paragraph 1: Why is this a SHOULD and not a MUST? (Similar
> question for the SHOULD in paragraph 2). It's not clear if you're trying
> to avoid "Some things won't implement this spec" or "Don't do this if
> you haven't administratively ensured every element understands this
> extension first" or something else?
> 
> 5.1.3 paragraph 3: You say "unless specified otherwise". Do you ever
> specify otherwise? Why is this disclaimer here?
> 
> 5.1.3 last paragraph: You meant section 6 not 5.
> 
> 
> 



From nobody Thu Apr 10 10:11:07 2014
Return-Path: <don.fedyk@hp.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 4DFBC1A02FD; Thu, 10 Apr 2014 09:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 zHdvB6RT0iao; Thu, 10 Apr 2014 09:27:04 -0700 (PDT)
Received: from g6t1524.atlanta.hp.com (g6t1524.atlanta.hp.com [15.193.200.67]) by ietfa.amsl.com (Postfix) with ESMTP id B0B481A023A; Thu, 10 Apr 2014 09:27:04 -0700 (PDT)
Received: from G6W4001.americas.hpqcorp.net (g6w4001.atlanta.hp.com [16.205.80.210]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g6t1524.atlanta.hp.com (Postfix) with ESMTPS id 88CB4294; Thu, 10 Apr 2014 16:27:03 +0000 (UTC)
Received: from G6W3997.americas.hpqcorp.net (16.205.80.212) by G6W4001.americas.hpqcorp.net (16.205.80.210) with Microsoft SMTP Server (TLS) id 14.3.169.1; Thu, 10 Apr 2014 16:25:10 +0000
Received: from G6W2492.americas.hpqcorp.net ([169.254.8.28]) by G6W3997.americas.hpqcorp.net ([16.205.80.212]) with mapi id 14.03.0169.001; Thu, 10 Apr 2014 16:25:10 +0000
From: "Fedyk, Don" <don.fedyk@hp.com>
To: Robert Sparks <rjsparks@nostrum.com>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-l2vpn-vpls-ldp-mac-opt@tools.ietf.org" <draft-ietf-l2vpn-vpls-ldp-mac-opt@tools.ietf.org>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Thread-Topic: Gen-art LC review: draft-ietf-l2vpn-vpls-ldp-mac-opt-11
Thread-Index: AQHPUpla/vBEaWxwvkyaZc2uEqclVJsIK+Vw
Date: Thu, 10 Apr 2014 16:25:10 +0000
Message-ID: <A46D9C092EA46F489F135060986AD9FFD13A45@G6W2492.americas.hpqcorp.net>
References: <5342FF4F.4040906@nostrum.com>
In-Reply-To: <5342FF4F.4040906@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [15.193.49.29]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/TUNfrUqUXuE0-um9P11LUhklOUI
X-Mailman-Approved-At: Thu, 10 Apr 2014 10:11:05 -0700
Subject: Re: [Gen-art] Gen-art LC review: draft-ietf-l2vpn-vpls-ldp-mac-opt-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, 10 Apr 2014 16:27:06 -0000

Hi Robert

Thanks for your comments.

Inline [Don]

I've incorporated your feedback in the latest draft which I will distribute=
 and check with authors and ADs and Chairs shortly.=20

Don.

-----Original Message-----
From: L2vpn [mailto:l2vpn-bounces@ietf.org] On Behalf Of Robert Sparks
Sent: Monday, April 07, 2014 3:41 PM
To: General Area Review Team; draft-ietf-l2vpn-vpls-ldp-mac-opt@tools.ietf.=
org; l2vpn@ietf.org
Subject: Gen-art LC review: draft-ietf-l2vpn-vpls-ldp-mac-opt-11

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

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

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

Document: draft-ietf-l2vpn-vpls-ldp-mac-opt-11
Reviewer: Robert Sparks
Review Date: 7Apr2014
IETF LC End Date: 8Apr2014
IESG Telechat date: not yet scheduled

Summary: This draft is almost ready for publication as a Proposed Standard,=
 but has minor issues (primarily editorial) that should be addressed.

I found this document very difficult to read. It asks the reader to hop bet=
ween sections in unusual ways (for instance, it sends the reader to the pro=
blem statement section for details on normative behavior). I strongly encou=
rage an editorial pass focusing on document structure.
[Don] Will work with AD to see what can be done here. =20
There are many instances of SHOULD in the document where the text should ju=
st be using prose instead. It's not always clear when an implementation wou=
ld choose to ignore the SHOULD, and what the consequences of that choice wo=
uld be.
[Don] I'll check this.=20

The document is inconsistent about the level of support needed in the netwo=
rk before trying to use this extension.
Section 5.1.2 says the assumption is everything understands it before it's =
turned on. Section 6 points back to figure 2 and says to use the extension =
over the pw where you administratively know the peer supports the extension=
, and fall back to 4762 for everything else. Which of those did you intend?
[Don] I will clarify.  =20
Specific comments in document order:

Section 3.2 paragraph 1: This paragraph would benefit from being broken int=
o several. It's hard to find its point. The SHOULD in this paragraph is pro=
bably not a 2119 SHOULD (this section isn't defining the protocol). It woul=
d be useful in this overview to explicitly say _why_ "This cannot be achiev=
ed with ... 4762]" at this point in the document.
[Don] Will address this .

Section 3.2 paragraph 2: This SHOULD _is_ defining protocol - shouldn't it =
be in section 5?
[Don] Agree.=20

Section 4.1.1 paragraph 3: It took me some time to find Z on the figure.=20
It might help to introduce it similar to how you introduce X.
[Don] OK

Section 4.1.2: paragraph 1: I think you meant to reference 4.1.1
[Don] Done.

Section 5: The first sentence talks about requirements in section 4.=20
Section 4 describes a problem using some examples but doesn't explicitly ca=
ll out requirements. Doing so would help the document.
[[Don]] Renamed Problem Space as recommended by Ben.=20

Last sentence in 5.1.1 (and several other places in the document):=20
Please add an article before "MAC Flush message".  (I apologize for such a =
small nit, but each of these instances made making sure I was reading what =
the sentence intended significantly more difficult).
[Don] OK.=20

Section 5.1.2 first paragraph: This section is defining behavior - why are =
you sending the reader back into the problem statement for detail on the be=
havior?
[Don] s/4.2/5.2/

5.1.2 paragraph 2: You meant section 6, not 5.
[Don] Done.

5.1.2 paragraph 3: I can't follow this paragraph's structure. I think you'r=
e trying to say "An MTU-s or PE2-rs SHOULD send MAC withdraw messages as de=
fined in [RFC4762] in cases where the network is being upgraded and devices=
 are not capable of understanding the optimized MAC flush." (But if so, the=
 next sentence is redundant.) Why is this SHOULD?
[Don] Updated.=20

5.1.3 paragraph 1: Why is this a SHOULD and not a MUST? (Similar question f=
or the SHOULD in paragraph 2). It's not clear if you're trying to avoid "So=
me things won't implement this spec" or "Don't do this if you haven't admin=
istratively ensured every element understands this extension first" or some=
thing else?
[Don] Changed to MUST for optimized MAC Flush.=20

5.1.3 paragraph 3: You say "unless specified otherwise". Do you ever specif=
y otherwise? Why is this disclaimer here?
[Don] Removed.

5.1.3 last paragraph: You meant section 6 not 5.
[Don] Done.=20






From nobody Thu Apr 10 14:26:13 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 E96191A02C1 for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 14:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 0nFn8ODTT63X for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 14:26:09 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 890531A024F for <gen-art@ietf.org>; Thu, 10 Apr 2014 14:26:09 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-50-89.dllstx.fios.verizon.net [173.71.50.89]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3ALQ31J013045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Thu, 10 Apr 2014 16:26:08 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-71-50-89.dllstx.fios.verizon.net [173.71.50.89] claimed to be A-Jean-Mahoneys-MacBook-Pro.local
Message-ID: <53470C6B.6020409@nostrum.com>
Date: Thu, 10 Apr 2014 16:26:03 -0500
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.4.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/AqgNBX7ODpN38kr6m8ms3iLWyi4
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-04-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, 10 Apr 2014 21:26:11 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Suresh Krishnan   2014-04-18   draft-kivinen-ipsecme-ikev2-rfc5996bis-02

Tom Taylor        2014-04-23*  draft-ietf-precis-framework-15

* Since the draft is on the 4/24 telechat, review is actually due 4/22


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

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:




From nobody Thu Apr 10 15:23:17 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 6952A1A02B3 for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 15:23:14 -0700 (PDT)
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 bnx4-ULfA1ox for <gen-art@ietfa.amsl.com>; Thu, 10 Apr 2014 15:23:09 -0700 (PDT)
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 D8D6C1A0259 for <gen-art@ietf.org>; Thu, 10 Apr 2014 15:23:08 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id d1so98716wiv.15 for <gen-art@ietf.org>; Thu, 10 Apr 2014 15:23:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=+jMB/x97zy11qy0Gs3E51ONdz4cKjpvjg+FAv9BCjm0=; b=kKQIBrHmK5fcAt1HcnszMYVF6MbcVlZ1xIu2dSeHq7+fH0UPYkbb9U9ailr06d/ioU 1eZ1y5b02AS8TmMF1BQsf+UV0BfrrAOnQP4rF5OfYcYN/UEqbaO2drQqh7Q3MY0JsRYr OhiLFFmj0AaY6bwCeY/zV9dTOK8UTtJl47eKjOIhmrCVhNMukUOnbHx6XxPIV43HbKaP jVhqal8qegsvmT748WrPtwDglJZi+r/i7vRcsHfxbJEVu+xBMePmtHo8z2Sku3FElAVZ GuHnj9M8r5rQSSYim2+h6CV0UuBGCKe0SjXNBTsnXYPTISudj5AGu0BdTPMnYWWIcKOk PiKQ==
MIME-Version: 1.0
X-Received: by 10.180.13.180 with SMTP id i20mr58219wic.56.1397168587248; Thu, 10 Apr 2014 15:23:07 -0700 (PDT)
Received: by 10.227.144.132 with HTTP; Thu, 10 Apr 2014 15:23:07 -0700 (PDT)
In-Reply-To: <74C1B909-BE20-434E-85FD-B866FC855D8A@piuha.net>
References: <CABkgnnVVQCAz=ixeR04rc75Vc-rL2JFQcjT0-hX_UCL-c=FGjQ@mail.gmail.com> <5F92FD08-1636-48C0-9634-8806E9F577FF@piuha.net> <CABkgnnUdkHYxGnFOkaHf-Xc+v=UYiASBS7KBJeC75aEV1SyKMA@mail.gmail.com> <CAHBDyN5a+S-1QUzD0eWpkxMdT0tBZ9_DZELM1FKuutmXNk8a0g@mail.gmail.com> <058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6F@HE113667.emea1.cds.t-internal.com> <74C1B909-BE20-434E-85FD-B866FC855D8A@piuha.net>
Date: Thu, 10 Apr 2014 15:23:07 -0700
Message-ID: <CABkgnnX-vvkScXnNcTKN+42pF2e=jD4b0nSRjV1OYqAQO8isQQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/DQiO1-x6OzI9N-HjHBKb3kXaxVo
Cc: Richard Barnes <rlb@ipv.sx>, "gen-art@ietf.org" <gen-art@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, R.Jesske@telekom.de, draft-drage-sipping-rfc3455bis@tools.ietf.org, atle.monrad@ericsson.com, Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-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: Thu, 10 Apr 2014 22:23:14 -0000

On 10 April 2014 07:15, Jari Arkko <jari.arkko@piuha.net> wrote:
>>
>> A lot has happened since RFC 3455 was published.  The privacy considerat=
ions around the use of P-Access-Network-Info are unchanged from their pre-G=
eopriv form.  In particular, I find the UA knowledge part to be problematic=
; Geopriv definitions can probably help here.
>>
>> [RJ] sorry cannot do
>
> I think a better approach would be to describe the issues, rather than tr=
y to change what the implementations do, if that is what you meant by using=
 Geopriv definitions.

Yes, a description of the issues would be appropriate.  I don't expect
to change anything here, but this is a very poorly understood
architecture with privacy properties that are challenging.  Making
those properties clearer is - I believe - entirely appropriate.
Geopriv [RFC6280] has tools that you can use - a framework of terms
and concepts - that should make this relatively easy to achieve.  It
shouldn't require more than a couple of paragraphs.


From nobody Fri Apr 11 13:08:05 2014
Return-Path: <eric@notcom.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 4027F1A0414 for <gen-art@ietfa.amsl.com>; Fri, 11 Apr 2014 13:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.722
X-Spam-Level: *
X-Spam-Status: No, score=1.722 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, GB_SUMOF=1, RCVD_IN_DNSWL_LOW=-0.7] 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 DkO_flAB3_vl for <gen-art@ietfa.amsl.com>; Fri, 11 Apr 2014 13:08:01 -0700 (PDT)
Received: from mail-yh0-f45.google.com (mail-yh0-f45.google.com [209.85.213.45]) by ietfa.amsl.com (Postfix) with ESMTP id A06A31A022E for <gen-art@ietf.org>; Fri, 11 Apr 2014 13:08:01 -0700 (PDT)
Received: by mail-yh0-f45.google.com with SMTP id a41so5844292yho.18 for <gen-art@ietf.org>; Fri, 11 Apr 2014 13:08:00 -0700 (PDT)
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=K/h4zGNVX00Nj715dvJ8VA++nQ0bMDsx/HFx4J/kZsA=; b=hbOYZrhcDT6dfOy+iuJt3D8sttPfV89ISgGULgDlDQwCcjYMQa2+Ykqz7OiO9bX1Bo BJXFrfKpVdeRhGO2mpi/OFS+XQvk/EOO+7gJag8afFJvBf0j5fJ2vS+XaXDvB4nc6LHq a7KdMxxynUnKrkdE3HLvZxu/E8hg8MOE375wRqBb8iUVktcmP+eGArLIVqGXzZsR0nmX 6j7Pwdg7MhWf4C3tR/O4XL7XSmk3wJt6jp6VyGauqN9RAWvMTuaMNtGRy8QtCWBsRVEp kjd50zyRpiZroAewBZ+az6wXJRxHMu2/xqPWk23H4YL33teeLsOOyPVlfB/rvW1mUQm2 3PRQ==
X-Gm-Message-State: ALoCoQmEE8pqYl+bJ+KwGpC1XuzA00U/9NFZipJt6DD4m2SgnAZ4wPnzFnHy01E33r/f2Ycg6cCV
MIME-Version: 1.0
X-Received: by 10.236.139.70 with SMTP id b46mr35018771yhj.63.1397246879936; Fri, 11 Apr 2014 13:07:59 -0700 (PDT)
Received: by 10.170.60.5 with HTTP; Fri, 11 Apr 2014 13:07:59 -0700 (PDT)
In-Reply-To: <1396637884.15324.14300.camel@mightyatom>
References: <1396637884.15324.14300.camel@mightyatom>
Date: Fri, 11 Apr 2014 16:07:59 -0400
Message-ID: <CA+97oKOnyw5D69EMgEORQJyJ0Wk7p=_KQk5=+dHww1JVv_y8pw@mail.gmail.com>
From: Eric Osborne <eric@notcom.com>
To: Elwyn Davies <elwynd@folly.org.uk>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/e4vCLSi8aAwOA76HwPQHqH2doUo
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-mpls-psc-updates.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-mpls-psc-updates-03.txt (review type corrected).
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, 11 Apr 2014 20:08:03 -0000

Hi Elwyn-

  A few questions and comments inline with EO#.


> Specifics:
> On-the-wire format:
> - The encoding of the TLV Length field is not specified (unsigned binary
> integer in network bit order).
> - The encoding of the individual TLV length and Type fields in s2 should
> also be specified (unsigned binary integer in network bit order).
> - The value of TLV Length should be more precisely specified.  Suggest:
>   The TLV Length is the sum of the lengths of all TLVs in the message,
>   where the length of a TLV is the sum of the lengths of the three
>   TLV fields, i.e., the the length of the value field + 4.


EO#
Your comments are around the on-wire format for PSC TLVs.  It seems
weird to specify the encoding *only* for TLVs and not for the rest of
PSC.  So the first thing I thought of was adding a section that says
"all of PSC is network byte order".  This seems like overkill, though,
as no other MPLS-TP RFCs discuss byte order.  Would any reasonable
implementer get everything else right in all other protocols and then
get it wrong in PSC TLVs?

>
> Malformed messages check:
> - Check values of fields prior to TLV Length are consistent with s4.2 of
> RFC 6378.
> - Check overall length of message matches value in TLV Length + 12.
> - Check Sum of lengths of TLVs matches value in TLV Length.
> - Check all TLV types received are recognized.
>

EO#  Same kind of question - is this necessary?  It seems like an
implementation issue.  I'd hate to see an implementation that lets
other errors pass by uncaught because psc-updates didn't tell the
implementer what other sorts of errors to look for.

For both of these questions I looked at a few big RFCs as examples -
2328, 5340, 2460, 6427, 4271 - and got very little out of them.

4271 just says "All multi-octet fields are in network byte order."
None of the rest say anything about network bit/byte ordering or the
error checking an implementation must have in order to be compliant.

And of course rfc6378 itself doesn't cover this much either, for any
of its own fixed fields.

It took me longer to go do that research than it would have to just
write the section you want, so I'm not really wedded to leaving that
sort of stuff out.  It just seems like overkill to put it only in PSC
TLVs when it's nowhere else.

Is this level of detail really necessary?



> Behaviour in the event of receiving a malformed message:
> - There has been discussion of appropriate behaviour on the MPLS mailing
> list.
>
> Behaviour in the event of receiving a well-formed but inappropriate TLV
> in a message:
> - This needs to be specified. (might be mode specific)

EO#  ACK - these two need to be specified as per discussion on the list.

>
> Nits/Editorial Comments:
> General: s/i.e. /i.e., /g, s/e.g. /e.g., /g
>
> Abstract/s1: Make the count of changes consistent (four/five currently).
> Might be better just to say 'a number of changes' and leave the reader
> to count.
>
> s1: Since the number of items has grown to five and maybe six (depending
> on how the above changes are inserted), it would helpful to link the
> categorization to the actual section numbers.)
>
> s2: It would be good to have the conventional picture here - just grab
> the one from draft-mpls-tp-psc-itu.
>
> s2, Value field: Better to say that this has the number of octets
> specified in the length field rather than talking about multiples of 4
> again.  The discussion of padding seems superfluous.
>


EO#  It seems odd that you want me to take our four words around
padding while adding a section on implementation-level error
checking...







eric

> s4, next to last para: Should 'A remote No Request message SHALL be ignored' be
> 'A remote NR message SHALL be ignored' for consistency?
>
> s5,para 8: s/In both cases the request which was driving/In both cases the request that was driving/
>
> s6: It might be worth pointing out that extensions of PSC (like tp-psc-itu) may
> introcuce additional capabilities and state that it is up to these sepcifications to
> say how capability mismatch in this areas is/are handled.
>
>
>
>
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
>


From nobody Sun Apr 13 14:00:30 2014
Return-Path: <tom.taylor.stds@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 CD3B31A0229 for <gen-art@ietfa.amsl.com>; Sun, 13 Apr 2014 14:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 WTAE4XCNhFbF for <gen-art@ietfa.amsl.com>; Sun, 13 Apr 2014 14:00:25 -0700 (PDT)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 460721A0231 for <gen-art@ietf.org>; Sun, 13 Apr 2014 14:00:25 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id to1so7414694ieb.34 for <gen-art@ietf.org>; Sun, 13 Apr 2014 14:00:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=KEcghaOwWXoBWqrArOnLepcwP/Q36eid5KmIyAaNqUg=; b=kusPgJFdG1h8EVGY4GKBqAcoWn9uo2QrtDRrAsauhQ4FWu3j6zI90ILjoa/ph2NkOM p0fyxD5CHalc3SJbMZqijqv9Grp1DHo1eqpIPKVWISDvfAlXGWpgHJNKTv4BBn/5Zcnn fUWn5FZd4yQyqC6ZWVn+YYx0KIzCv1l+jTBIHyTRURfavqyBN00lCOlTg1JABWW6pIMJ 5Z8XrN/azOGDMQdFCU+j55d8RFF+e9C+Sz0kMpSJM1kmC0WszGoRxQmyK1xtOwYjfNb4 TBUkem1tIULv8hMuDKiMN0kxJXQZSgC/X6l19ZdAVY086Jf1I5WXchJMTcJ04ixwpZa1 ha2g==
X-Received: by 10.43.141.81 with SMTP id jd17mr29348355icc.39.1397422823056; Sun, 13 Apr 2014 14:00:23 -0700 (PDT)
Received: from [192.168.97.184] ([67.210.160.130]) by mx.google.com with ESMTPSA id ix1sm24165983igc.15.2014.04.13.14.00.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Apr 2014 14:00:22 -0700 (PDT)
Message-ID: <534AFAE4.4040102@gmail.com>
Date: Sun, 13 Apr 2014 17:00:20 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Gen Art <gen-art@ietf.org>, precis-chairs@tools.ietf.org,  draft-ietf-precis-framework@tools.ietf.org,  Pete Resnick <presnick@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/hm895iWcxrBHuYlhEy700wyKeuw
Subject: [Gen-art] Gen-ART LC review of draft-ietf-precis-framework-15
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, 13 Apr 2014 21:00:28 -0000

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

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

This document is beautifully written and is ready to go. As a person 
unfamiliar with the basic concepts I had to read into the document a bit 
to get traction, then re-read from the beginning, but the additional 
effort was minimal and rewarding.

Document:           draft-ietf-precis-framework-15
Reviewer:           Tom Taylor
Review Date:        13/04/2014
IETF LC End Date:   23/04/2014
IESG Telechat date: 24/04/2014

Summary: This document provides:
-- the historical background leading up to the approach used for
    its technical content
-- definitions of two string classes suitable as bases for two
    general classes of application
-- instructions for creating profiles of the string classes
    (particularly the FreeformClass) for specific applications
-- a satisfying set of security considerations.

This document obsoletes Stringprep (RFC 3454). It establishes new IANA 
registries for derived properties of Unicode code points for Unicode 
versions subsequent to 6.2, for base string classes, and for profiles.

Major issues:

Minor issues:

Nits/editorial comments:


From nobody Sun Apr 13 18:48:42 2014
Return-Path: <stpeter@stpeter.im>
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 1A1BA1A02E5 for <gen-art@ietfa.amsl.com>; Sun, 13 Apr 2014 18:48:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, 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 rO0QPY0Ke12f for <gen-art@ietfa.amsl.com>; Sun, 13 Apr 2014 18:48:39 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id BA8651A02E3 for <gen-art@ietf.org>; Sun, 13 Apr 2014 18:48:39 -0700 (PDT)
Received: from aither.local (unknown [24.8.184.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 2257240352; Sun, 13 Apr 2014 19:48:32 -0600 (MDT)
Message-ID: <534B3E6F.3010709@stpeter.im>
Date: Sun, 13 Apr 2014 19:48:31 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Tom Taylor <tom.taylor.stds@gmail.com>, Gen Art <gen-art@ietf.org>,  precis-chairs@tools.ietf.org, draft-ietf-precis-framework@tools.ietf.org,  Pete Resnick <presnick@qualcomm.com>
References: <534AFAE4.4040102@gmail.com>
In-Reply-To: <534AFAE4.4040102@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/jXaYsN9DHkiM7kUklXEqH8iZiok
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-precis-framework-15
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, 14 Apr 2014 01:48:41 -0000

Hi Tom, thanks for the review and for the kind words about the document.

Peter

On 4/13/14, 3:00 PM, Tom Taylor 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>.
>
> This document is beautifully written and is ready to go. As a person
> unfamiliar with the basic concepts I had to read into the document a bit
> to get traction, then re-read from the beginning, but the additional
> effort was minimal and rewarding.
>
> Document:           draft-ietf-precis-framework-15
> Reviewer:           Tom Taylor
> Review Date:        13/04/2014
> IETF LC End Date:   23/04/2014
> IESG Telechat date: 24/04/2014
>
> Summary: This document provides:
> -- the historical background leading up to the approach used for
>     its technical content
> -- definitions of two string classes suitable as bases for two
>     general classes of application
> -- instructions for creating profiles of the string classes
>     (particularly the FreeformClass) for specific applications
> -- a satisfying set of security considerations.
>
> This document obsoletes Stringprep (RFC 3454). It establishes new IANA
> registries for derived properties of Unicode code points for Unicode
> versions subsequent to 6.2, for base string classes, and for profiles.
>
> Major issues:
>
> Minor issues:
>
> Nits/editorial comments:
>


From nobody Mon Apr 14 06:20:17 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 0B81D1A0484; Mon, 14 Apr 2014 06:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.873
X-Spam-Level: 
X-Spam-Status: No, score=-0.873 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.272, 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 VLY__cycL83n; Mon, 14 Apr 2014 06:20:08 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id CD73C1A0494; Mon, 14 Apr 2014 06:20:04 -0700 (PDT)
Received: from maildlpprd02.lss.emc.com (maildlpprd02.lss.emc.com [10.253.24.34]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3EDJsfJ025680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Apr 2014 09:19:56 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s3EDJsfJ025680
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1397481596; bh=TzurfSxhx1crxzjb21l9IQpecwM=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=YGhiPNkFhliIcOzmMgEwi89Jgdc7ceAIEjmbbQvbEtL4u2Q00PCU6kKUzo9u+WYC7 gFPZARJ2kKSqvyQ4OHTmdOoFNzIo7bRsuORFcMm0rOgv6ZK/R8xZRc+gC9PbGWoVuP DPMWgj+7Fgde9fiUYrBpayvwKI6zXrLx1Oerg9Pw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s3EDJsfJ025680
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd02.lss.emc.com (RSA Interceptor); Mon, 14 Apr 2014 09:19:36 -0400
Received: from mxhub28.corp.emc.com (mxhub28.corp.emc.com [10.254.110.184]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3EDJZxt020247 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 14 Apr 2014 09:19:35 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub28.corp.emc.com ([10.254.110.184]) with mapi; Mon, 14 Apr 2014 09:19:34 -0400
From: "Black, David" <david.black@emc.com>
To: "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "Donald Eastlake (d3e3e3@gmail.com)" <d3e3e3@gmail.com>, "ostokes@extremenetworks.com" <ostokes@extremenetworks.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Mon, 14 Apr 2014 09:19:34 -0400
Thread-Topic: Gen-ART review of draft-ietf-trill-esadi-07.txt
Thread-Index: Ac9X5C1IRV0XGBZDQo+hNsgFemwTCQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C1D1C22@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
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/yOOhtFYvdBv2ERV0UTdIMN6b8rk
Cc: "ietf@ietf.org" <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-trill-esadi-07.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, 14 Apr 2014 13:20:13 -0000

The -07 version of this draft addresses all of the concerns raised by the G=
en-ART
review of the -06 version.  I would have preferred to see stronger Security
Considerations text on usage (and non-usage of the Authentication TLV.  Tha=
t said,
the text in the -07 version is an improvement, and I will leave any further
follow-up to the IESG.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Saturday, March 29, 2014 10:24 PM
> To: zhai.hongjun@zte.com.cn; hu.fangwei@zte.com.cn; Radia@alum.mit.edu; D=
onald
> Eastlake (d3e3e3@gmail.com); ostokes@extremenetworks.com; General Area Re=
view
> Team (gen-art@ietf.org)
> Cc: trill@ietf.org; ietf@ietf.org; Black, David
> Subject: Gen-ART review of draft-ietf-trill-esadi-06.txt
>=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-trill-esadi-06.txt
> Reviewer: David L. Black
> Review Date: March 29, 2014
> IETF LC End Date: April 1, 2014
>=20
> Summary: This draft is on the right track, but has open issues
> described in the review.
>=20
> This draft revises the ESADI specification for TRILL from its
> original form in RFC 6325.
>=20
> Major issues:
>=20
> The draft changes ESADI in a non-backwards-compatible fashion from
> its original specification in RFC 6325, but does not explain why this
> is ok.  That explanation needs to be provided, and if implementations
> of ESADI as originally specified in RF 6325 exist, that explanation
> needs to encompass coexistence and interoperability (or lack thereof)
> with such implementations.  That explanation probably belongs in
> Section 1.1, and could be expanded upon in Appendix A.
>=20
> Overall, this draft is not self-contained - to a significant extent,
> it is written as if it were effectively a long collection of errata
> to the ESADI specification in RFC 6325.  That makes it difficult to
> understand - it would be better if this draft completely obsoleted
> and replaced the ESADI specification in RFC 6325, describing its
> changes, instead of providing specific text changes to portions
> of the RFC 6325 text.
>=20
> Minor issues:
>=20
> I don't understand the discussion in section 2 of it being "an
> implementation decision how independent the multiple ESADI instances
> at an RBridge are" in light of the clear statement that "the ESADI
> update process operates separately for each ESADI instance."  The
> example given involves database structure considerations that are
> specific to the node implementation and do not affect the independent
> updates for each ESADI instance.  There may not be an actual
> technical problem here, but at least the first chunk of text quoted
> in this paragraph of the review needs to be rewritten.
>=20
> Also in Section 2:
>=20
>    ESADI does no routing so there is no reason for pseudo-nodes in ESADI
>    and none are created.
>=20
> Need to explain what a pseudo-node is before this sentence.
>=20
> p.9, Figure 2 - explain how the receiver determines whether the inner
> Ethernet header contains a VLAN tag or FGL.  This also applies to Figure
> 3 on p.10.
>=20
> p.10, Section 2.1:
>=20
>    All transit RBridges forward ESADI packets as if they were ordinary
>    TRILL Data packets.
>=20
> Need to explain what a "transit" RBridge is.  Between this and the
> above pseudo-node comment, I suggest adding an overview of the
> TRILL protocol to the start of Section 2.
>=20
> p.11, Section 2.1:
>=20
>    No "routing" computation or routing decisions ever have to be performe=
d
>    by ESADI.
>=20
> What is a ' "routing" computation' ??  This should be rephrased to
> contrast to what the non-ESADI TRILL usage of IS-IS does.
>=20
> p.12, Section 2.2:
>=20
>    If a VLAN or FGL ID
>    field within an ESADI-LSP PDU does include a value, that field's
>    contents is ignored.
>=20
> This looks like it's an important requirement, so:
> 	 "is ignored" -> "MUST be ignored"
>=20
> p.13, Section 3
>=20
>   "SNPA/MAC address"
>    is not considered in this tie breaking and there is no "Port ID".
>=20
> This is contrasting ESDI tie-breaking to a tie-breaking
> procedure that I'd guess is specified in another document; that needs to
> be explained, along with a reference to that document, preferably with
> the section number where the other tie-breaking procedure is specified.
>=20
> Section 6 - explain where the 1470 byte number in the third paragraph
> comes from.
>=20
> Section 8 - more should be said on whether/when the Authentication TLV
> should be used when ESADI conveys information from an authenticated
> registration.  In particular, if this recommendation for usage of the
> Authentication TLV with information from an authenticated
> registration usage is not a "SHOULD" or "MUST", an explanation is in
> order.
>=20
> Nits/editorial comments:
>=20
> There are lots of acronyms that are not expanded on first use, defined
> in the terminology section, or otherwise explained, e.g., DRB, Sz, CSNP,
> PSNP.  It may be ok to point to terminology/acronym definitions in RFC
> 6325.
>=20
> Last sentence on p.8:
>=20
> OLD
>    The outer VLAN tag will not be present if it was stripped by
>    an Ethernet port out of which the packet was sent.
> NEW
>    The outer VLAN tag will not be present for a packet on an
>    an Ethernet link that does not use VLAN tags.
>=20
> idnits 2.13.01 got confused by the Section 4.6.2.2 reference to
> RFC 6325 in Section 4.1, and thought 4.6.2.2 was an IPv4 address -
> this is not a problem.
>=20
> idnits also warned about possible pre-RFC5378 (2008) content.  This
> is probably not a problem, but please check with your AD.
>=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 nobody Mon Apr 14 08:58:25 2014
Return-Path: <elwynd@folly.org.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 E3D741A04A7 for <gen-art@ietfa.amsl.com>; Mon, 14 Apr 2014 08:58:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.8
X-Spam-Level: *
X-Spam-Status: No, score=1.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  GB_SUMOF=1] 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 XNUzJskgmqLB for <gen-art@ietfa.amsl.com>; Mon, 14 Apr 2014 08:58:21 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id EF5661A01D2 for <gen-art@ietf.org>; Mon, 14 Apr 2014 08:58:20 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1WZjGq-0004Wt-GJ; Mon, 14 Apr 2014 16:58:11 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: Eric Osborne <eric@notcom.com>
In-Reply-To: <CA+97oKOnyw5D69EMgEORQJyJ0Wk7p=_KQk5=+dHww1JVv_y8pw@mail.gmail.com>
References: <1396637884.15324.14300.camel@mightyatom> <CA+97oKOnyw5D69EMgEORQJyJ0Wk7p=_KQk5=+dHww1JVv_y8pw@mail.gmail.com>
Content-Type: text/plain
Organization: Folly Consulting
Date: Mon, 14 Apr 2014 16:58:07 +0100
Message-Id: <1397491087.15324.22621.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/EVSTacQSZeek9tXuzyc4FNYLpw8
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-mpls-psc-updates.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-mpls-psc-updates-03.txt (review type corrected).
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, 14 Apr 2014 15:58:24 -0000

Hi, Eric.
On Fri, 2014-04-11 at 16:07 -0400, Eric Osborne wrote:
> Hi Elwyn-
> 
>   A few questions and comments inline with EO#.
> 
> 
> > Specifics:
> > On-the-wire format:
> > - The encoding of the TLV Length field is not specified (unsigned binary
> > integer in network bit order).
> > - The encoding of the individual TLV length and Type fields in s2 should
> > also be specified (unsigned binary integer in network bit order).
> > - The value of TLV Length should be more precisely specified.  Suggest:
> >   The TLV Length is the sum of the lengths of all TLVs in the message,
> >   where the length of a TLV is the sum of the lengths of the three
> >   TLV fields, i.e., the the length of the value field + 4.
> 
> 
> EO#
> Your comments are around the on-wire format for PSC TLVs.  It seems
> weird to specify the encoding *only* for TLVs and not for the rest of
> PSC.  So the first thing I thought of was adding a section that says
> "all of PSC is network byte order".  This seems like overkill, though,
> as no other MPLS-TP RFCs discuss byte order.  Would any reasonable
> implementer get everything else right in all other protocols and then
> get it wrong in PSC TLVs?

The other parts of the PSC don't involve integers and so aren't
affected.

The usual solution is to add a single statement to the effect that all
integer fields are encoded as unsigned integers in network bit order.

Assuming things is always dangerous in standards.

> 
> >
> > Malformed messages check:
> > - Check values of fields prior to TLV Length are consistent with s4.2 of
> > RFC 6378.
> > - Check overall length of message matches value in TLV Length + 12.
> > - Check Sum of lengths of TLVs matches value in TLV Length.
> > - Check all TLV types received are recognized.
> >
> 
> EO#  Same kind of question - is this necessary?  It seems like an
> implementation issue.  I'd hate to see an implementation that lets
> other errors pass by uncaught because psc-updates didn't tell the
> implementer what other sorts of errors to look for.
> 
> For both of these questions I looked at a few big RFCs as examples -
> 2328, 5340, 2460, 6427, 4271 - and got very little out of them.
> 
> 4271 just says "All multi-octet fields are in network byte order."
> None of the rest say anything about network bit/byte ordering or the
> error checking an implementation must have in order to be compliant.
> 
> And of course rfc6378 itself doesn't cover this much either, for any
> of its own fixed fields.
> 
> It took me longer to go do that research than it would have to just
> write the section you want, so I'm not really wedded to leaving that
> sort of stuff out.  It just seems like overkill to put it only in PSC
> TLVs when it's nowhere else.
> 
> Is this level of detail really necessary?

Doubtless that is a matter of opinion, but in my experience of code
inspection and functional specifications/standards, providing a
checklist while we are thinking about it can help to avoid the sort of
security doom that OpenSSL is coping with at the moment.

> 
> 
> 
> > Behaviour in the event of receiving a malformed message:
> > - There has been discussion of appropriate behaviour on the MPLS mailing
> > list.
> >
> > Behaviour in the event of receiving a well-formed but inappropriate TLV
> > in a message:
> > - This needs to be specified. (might be mode specific)
> 
> EO#  ACK - these two need to be specified as per discussion on the list.
> 
> >
> > Nits/Editorial Comments:
> > General: s/i.e. /i.e., /g, s/e.g. /e.g., /g
> >
> > Abstract/s1: Make the count of changes consistent (four/five currently).
> > Might be better just to say 'a number of changes' and leave the reader
> > to count.
> >
> > s1: Since the number of items has grown to five and maybe six (depending
> > on how the above changes are inserted), it would helpful to link the
> > categorization to the actual section numbers.)
> >
> > s2: It would be good to have the conventional picture here - just grab
> > the one from draft-mpls-tp-psc-itu.
> >
> > s2, Value field: Better to say that this has the number of octets
> > specified in the length field rather than talking about multiples of 4
> > again.  The discussion of padding seems superfluous.
> >
> 
> 
> EO#  It seems odd that you want me to take our four words around
> padding while adding a section on implementation-level error
> checking...

You are not obliged to follow the comment. Anything here is designed to
make it easier for people to follow what is going on after memories have
faded... and we all have our views of how this is best achieved.

Regards
Elwyn
> 
> 
> 
> 
> 
> 
> 
> eric
> 
> > s4, next to last para: Should 'A remote No Request message SHALL be ignored' be
> > 'A remote NR message SHALL be ignored' for consistency?
> >
> > s5,para 8: s/In both cases the request which was driving/In both cases the request that was driving/
> >
> > s6: It might be worth pointing out that extensions of PSC (like tp-psc-itu) may
> > introcuce additional capabilities and state that it is up to these sepcifications to
> > say how capability mismatch in this areas is/are handled.
> >
> >
> >
> >
> >
> > _______________________________________________
> > Gen-art mailing list
> > Gen-art@ietf.org
> > https://www.ietf.org/mailman/listinfo/gen-art
> >
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Apr 15 12:28:56 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 B9A9E1A06A1 for <gen-art@ietfa.amsl.com>; Tue, 15 Apr 2014 12:28:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.828
X-Spam-Level: 
X-Spam-Status: No, score=0.828 tagged_above=-999 required=5 tests=[BAYES_50=0.8, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.272] 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 gt3Hwj1UeNZI for <gen-art@ietfa.amsl.com>; Tue, 15 Apr 2014 12:28:50 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E9361A0488 for <gen-art@ietf.org>; Tue, 15 Apr 2014 12:28:50 -0700 (PDT)
Received: from [172.20.10.7] (mobile-166-147-071-138.mycingular.net [166.147.71.138]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3FJShI0061471 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 15 Apr 2014 14:28:45 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host mobile-166-147-071-138.mycingular.net [166.147.71.138] claimed to be [172.20.10.7]
Content-Type: text/plain; charset=iso-8859-2
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <1808340F7EC362469DDFFB112B37E2FCDA33129A66@SRVHKE02.rdm.cz>
Date: Tue, 15 Apr 2014 14:28:36 -0500
X-Mao-Original-Outgoing-Id: 419282916.536916-f02479540ab606aa43d554fd43c38c11
Content-Transfer-Encoding: quoted-printable
Message-Id: <1619F656-EBAA-4CAC-B477-6859AF4003EF@nostrum.com>
References: <F415DB78-4352-4307-93CB-C26C09D7A98C@nostrum.com> <1808340F7EC362469DDFFB112B37E2FCDA33129A66@SRVHKE02.rdm.cz>
To: =?iso-8859-2?Q?V=EDzdal_Ale=B9?= <ales.vizdal@t-mobile.cz>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/fpE-ZyxQt1HOUvbG379Xhu4u0ug
Cc: "draft-ietf-v6ops-64share.all@tools.ietf.org" <draft-ietf-v6ops-64share.all@tools.ietf.org>, "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC/Telechat Review of draft-ietf-v6ops-64share-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, 15 Apr 2014 19:28:54 -0000

Hi,

Version 10 addresses all of my comments on version 09.

Thanks!

Ben.

On Apr 1, 2014, at 6:14 PM, V=EDzdal Ale=B9 <ales.vizdal@t-mobile.cz> =
wrote:

> Dear Ben, all,
> =20
> Many thanks for your review. An updated I-D has been submitted.
> =20
> Please see inline.
> =20
> > -----Original Message-----
> > From: Ben Campbell [mailto:ben@nostrum.com]
> > Sent: Friday, March 21, 2014 8:25 PM
> > To: draft-ietf-v6ops-64share.all@tools.ietf.org
> > Cc: gen-art@ietf.org Team (gen-art@ietf.org)
> > Subject: Gen-ART LC/Telechat Review of draft-ietf-v6ops-
> > 64share-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-v6ops-64share-09
> > Reviewer: Ben Campbell
> > Review Date: 2014-03-21
> > IETF LC End Date: long time ago
> > IESG Telechat date: 2014-03-27
> >
> > Note: I somehow missed this assignment at last call time.
> > Therefore this review serves as both a last call and an IESG
> > telechat review.
> >
> > Summary: This draft is mostly ready for publication as an
> > informational RFC. I have a few editorial comments that might
> > be worth considering prior to publication.
> >
> > Major issues: None
> >
> > Minor issues: None
> >
> > Nits/editorial comments:
> >
> > -- Section 1, paragraph 1:
> >
> > Can you elaborate on what it means to "extend" The prefix to
> > a LAN link? Are we talking about routing IPv6 traffic from
> > other local devices (on the LAN) across the 3gpp link, for
> > example, like one might do when tethering devices to a phone
> > or mobile hotspot?
> =20
> Yes, this is the case.
> =20
> > Can you offer a reference for "the 3GPP specification"?
> >
> > Can you offer a reference for "the 3GPP specification"?
> =20
> Done.
> =20
> > -- paragraph 2: "This can be achieved by receiving the Router
> > Advertisement (RA) [RFC4861] announced globally unique /64
> > IPv6 prefix from the 3GPP radio interface and then
> > advertising"
> >
> > What does these things. The UE?
> =20
> Yes, the UE. Ref to the UE has been added.
> =20
> > Please expand RA on first mention.
> =20
> Done.
> =20
> >
> > -- section 3, R-1:
> >
> > Please expand SLAAC on first use.
> =20
> Done.
> =20
> > -- section 4.2, 1st paragraph: "The 3GPP RA /64 prefix
> > information is used to configure NDP on the LAN and assigns
> > itself an address on the LAN link."
> >
> > The prefix information assigns itself an address? I don't
> > think that's what you mean to say.
> =20
> Fixed, please review.
> =20
> > -- section 4.2, step 7:
> >
> > Please expand DAD on first use.
> =20
> Done.
> =20
> Cheers,
> Ales
>=20
> Z=E1sady komunikace, kter=E9 spole=E8nost T-Mobile Czech Republic a.s. =
u=BE=EDv=E1 p=F8i sjedn=E1v=E1n=ED smluv, jsou uvedeny zde =
http://www.t-mobile.cz/zasady. Nen=ED-li v z=E1sad=E1ch uvedeno jinak, =
nep=F8edstavuje tato zpr=E1va kone=E8n=FD n=E1vrh na uzav=F8en=ED =E8i =
zm=ECnu smlouvy ani p=F8ijet=ED takov=E9ho n=E1vrhu. The communication =
principles which T-Mobile Czech Republic a.s. applies when negotiating =
contracts are defined here http://www.t-mobile.cz/principles. Unless =
otherwise stated in the principles, this message does not constitute the =
final offer to contract or an amendment of a contract or acceptance of =
such offer.


From nobody Wed Apr 16 08:08:00 2014
Return-Path: <eric@notcom.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 53D671A01AE for <gen-art@ietfa.amsl.com>; Wed, 16 Apr 2014 08:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, 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 1u8nKDzcn8kr for <gen-art@ietfa.amsl.com>; Wed, 16 Apr 2014 08:07:57 -0700 (PDT)
Received: from mail-yk0-f173.google.com (mail-yk0-f173.google.com [209.85.160.173]) by ietfa.amsl.com (Postfix) with ESMTP id 050431A00FB for <gen-art@ietf.org>; Wed, 16 Apr 2014 08:07:56 -0700 (PDT)
Received: by mail-yk0-f173.google.com with SMTP id 10so10249533ykt.32 for <gen-art@ietf.org>; Wed, 16 Apr 2014 08:07:53 -0700 (PDT)
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=hBcWF8MaNGz0DIMUv+m1QWdmLENZs5wEOgGBLbV6H00=; b=F9WEDWlUCtEYUZ5A5UNqqBtiqnzuPlXjx8N6k/rjJkSVQzBoGhyz6PEeiKPR1mHdqk MrPzNiNePSCtoCL7oK+ny4F/6Hu7uXDftxefFFpKCjhNGin8bToRPoXZ0/TBHYiM6DD6 2g8sWK5y6E1Ns6NOPo4HJvHuyeBt7VVmEioBdZzl7BtgAELIn1yvoa7qLQ82pC3YAwtC KOCK1PMxe2Hw3KAOMTqBiH6MCrmG4le1hiTJRcm2Dal7hjEe/NX1e9trxI/ZoHR/EyLs CbAlloA4hOf1N+1mgRWNSKe2iEVOh21yanZMIjNP1GfG5oZ6qhNDOxn7boVCCgG6B+jY GqoA==
X-Gm-Message-State: ALoCoQmjsVrz1kKhiJlAQrgP+K8iJqB9r96V6VCbDLQTgaRQO9ItqXIj3DCFL+tVgNfCZZ/eCQS7
MIME-Version: 1.0
X-Received: by 10.236.20.194 with SMTP id p42mr13625405yhp.56.1397660873622; Wed, 16 Apr 2014 08:07:53 -0700 (PDT)
Received: by 10.170.60.5 with HTTP; Wed, 16 Apr 2014 08:07:53 -0700 (PDT)
In-Reply-To: <1397491087.15324.22621.camel@mightyatom>
References: <1396637884.15324.14300.camel@mightyatom> <CA+97oKOnyw5D69EMgEORQJyJ0Wk7p=_KQk5=+dHww1JVv_y8pw@mail.gmail.com> <1397491087.15324.22621.camel@mightyatom>
Date: Wed, 16 Apr 2014 11:07:53 -0400
Message-ID: <CA+97oKM9HcXL1JSD6Zp3ZHYjKJyz88eSGimiq0=9BUdyqjSs=w@mail.gmail.com>
From: Eric Osborne <eric@notcom.com>
To: Elwyn Davies <elwynd@folly.org.uk>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/9KI2l2-7Mj_lhP2nsZel6yXiQTs
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-mpls-psc-updates.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-mpls-psc-updates-03.txt (review type corrected).
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, 16 Apr 2014 15:07:58 -0000

Hi Elwyn-

  Inline and trimmed a bit.

...

>> > Specifics:
>> > On-the-wire format:
...
>>
>> EO#
>> Your comments are around the on-wire format for PSC TLVs.  It seems
>> weird to specify the encoding *only* for TLVs and not for the rest of
>> PSC
.....
> The other parts of the PSC don't involve integers and so aren't
> affected.
>
> The usual solution is to add a single statement to the effect that all
> integer fields are encoded as unsigned integers in network bit order.
>
> Assuming things is always dangerous in standards.

All true.  OK, I'll add a such a statement.

...

>> > Malformed messages check:
>> > - Check values of fields prior to TLV Length are consistent with s4.2 of
>> > RFC 6378.
>> > - Check overall length of message matches value in TLV Length + 12.
>> > - Check Sum of lengths of TLVs matches value in TLV Length.
>> > - Check all TLV types received are recognized.
>> >
...
>>
>> Is this level of detail really necessary?
>
> Doubtless that is a matter of opinion, but in my experience of code
> inspection and functional specifications/standards, providing a
> checklist while we are thinking about it can help to avoid the sort of
> security doom that OpenSSL is coping with at the moment.
>

EO#  OK.  I'll add these cases and make clear that they are not the
only ones.  I don't want to make it too heavy as I'm wary of crossing
that line between protocol spec and implementation spec.

I will put something together today or tomorrow and get it out to this
list for review.

thanks!



eric


From nobody Wed Apr 16 14:27: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 A57F91A035A for <gen-art@ietfa.amsl.com>; Wed, 16 Apr 2014 14:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 ysOVcsjOuCR1 for <gen-art@ietfa.amsl.com>; Wed, 16 Apr 2014 14:27:07 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5731A01C1 for <gen-art@ietf.org>; Wed, 16 Apr 2014 14:27:07 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([137.254.4.59]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3GLR32C093055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Wed, 16 Apr 2014 16:27:03 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [137.254.4.59] claimed to be A-Jean-Mahoneys-MacBook-Pro.local
Message-ID: <534EF5A1.5080008@nostrum.com>
Date: Wed, 16 Apr 2014 16:26:57 -0500
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.4.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/WM1oeeCqKfS0xdIv98rILjqTbM0
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-04-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: Wed, 16 Apr 2014 21:27:11 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Alexey Melnikov   2014-04-25   draft-ietf-salud-alert-info-urns-12

Ben Campbell      2014-04-30   draft-ietf-radext-dtls-10

Brian Carpenter   2014-04-25   draft-ietf-rtcweb-use-cases-and-requirements-14

Christer Holmberg 2014-04-28   draft-ietf-bfd-tc-mib-05

Dan Romascanu     2014-04-29   draft-ietf-dhc-dhcpv4-over-dhcpv6-07

David Black       2014-04-28   draft-ietf-bfd-mib-17

Vijay Gurbani     2014-04-24   draft-ietf-l2vpn-vpls-inter-domain-redundancy-05

Wassim Haddad     2014-04-25   draft-ietf-straw-b2bua-loop-detection-04

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 nobody Wed Apr 16 15:03:20 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 98BC51A03C1 for <gen-art@ietfa.amsl.com>; Wed, 16 Apr 2014 15:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 lyaYzOwHJCMR for <gen-art@ietfa.amsl.com>; Wed, 16 Apr 2014 15:03:16 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 392E21A03C0 for <gen-art@ietf.org>; Wed, 16 Apr 2014 15:03:14 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([137.254.4.59]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3GM3A14096018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Wed, 16 Apr 2014 17:03:10 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [137.254.4.59] claimed to be A-Jean-Mahoneys-MacBook-Pro.local
Message-ID: <534EFE18.1070103@nostrum.com>
Date: Wed, 16 Apr 2014 17:03:04 -0500
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.4.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/7cEJuJs4eclysFpzxHFQmFFMwr8
Subject: [Gen-art] Assignments for the 2014-04-24 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: Wed, 16 Apr 2014 22:03:17 -0000

Hi all,

The following reviewers have assignments:

Reviewer            LC end       Draft
------------------------------------------------------------------------------------
Dan Romascanu          TR2014-02-24 
draft-ietf-mpls-ldp-applicability-label-adv-03 *

Dan Romascanu          TR2014-04-08 draft-ietf-idr-aigp-17 *

Roni Even              TR2014-02-28 draft-housley-pkix-oids-02 *

Russ Housley           TR2013-12-16 draft-ietf-opsec-vpn-leakages-04 **

Tom Taylor             TR2014-04-23 draft-ietf-precis-framework-15 **

* 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 nobody Wed Apr 16 16:31:19 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 D97341A0410; Wed, 16 Apr 2014 16:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 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.272, 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 DzgEx2SxbtlP; Wed, 16 Apr 2014 16:31:13 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 27E6A1A040F; Wed, 16 Apr 2014 16:31:12 -0700 (PDT)
Received: from maildlpprd06.lss.emc.com (maildlpprd06.lss.emc.com [10.253.24.38]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3GNV7C1003223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Apr 2014 19:31:08 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s3GNV7C1003223
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1397691068; bh=v3EwX5/iElkqecTL8cKXJGphWVY=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=pfeRnmVgmn7BlgDHfYP1Npst+unTEj122jtCF8Fu/TMZeLbg+uoUKnuTYia3agmwO EWzfwTZYp0cTEjSeXczyOxPNC6JEEw486ONQylWX15QvyIh3dsbzYuaBnZnb/gKDhQ P1TPDMXa0ezF81zdRhwGggv8nbUK4y6OVaqhkjmM=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s3GNV7C1003223
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd06.lss.emc.com (RSA Interceptor); Wed, 16 Apr 2014 16:30:59 -0700
Received: from mxhub33.corp.emc.com (mxhub33.corp.emc.com [10.254.93.81]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3GNUv2n006543 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 16 Apr 2014 19:30:58 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub33.corp.emc.com ([::1]) with mapi; Wed, 16 Apr 2014 19:30:57 -0400
From: "Black, David" <david.black@emc.com>
To: "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "zali@cisco.com" <zali@cisco.com>, "nobo@cisco.com" <nobo@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Wed, 16 Apr 2014 19:30:56 -0400
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@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
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/cQ-DXXarUgk67itJ4Z-bf2U1w5Y
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 16 Apr 2014 23:31:18 -0000

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

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

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

Document: draft-ietf-bfd-mib-17
Reviewer: David L. Black
Review Date: April 16, 2014
IETF LC End Date: April 28, 2014

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

This draft is a MIB module for the BFD protocol, which is an important low-
level routing protocol.  The draft is reasonable for a MIB draft; one needs
to go read the protocol documents to understand how the protocol works, and
significant portions of the text are derived from the usual MIB "boilerplat=
e"
as one would expect.  The "Brief Description of MIB Objects" is indeed
brief, but reasonable.  The shepherd writeup indicates that there are
multiple implementations.

Major issues:

This MIB contains many writable objects, so the authors should
take note of the IESG statement on writable MIB modules:

	http://www.ietf.org/iesg/statement/writable-mib-module.html

I did not see this mentioned in the shepherd writeup.  If the OPS Area
has not been consulted, I strongly suggest doing so during IETF Last
Call, e.g., starting with Benoit Claise (AD).

Minor issues:

The security considerations section includes considerations for
unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus,
but omits the corresponding considerations for bfdAdminStatus and
bfdSessNotificationsEnable.  Both of the latter objects are global,
so significant damage can be inflicted via these objects with a
small number of unauthorized modifications, so they need to be
included in the first list of sensitive objects.

I suggest that the authors recheck the entire MIB to ensure that
every object or table that should be included in the security
considerations section is appropriately included.

Also, as a General Variable, would bfdSessNotificationsEnable be better
named bfdNotificationsEnable, as it's not in the BFD Session Table?

I did not see a compliance requirement for a system that only
implements BFD protocol version 0.  That absence should at least be
mentioned somewhere.  For example, if this reflects a considered and
deliberate decision by the WG, that should be mentioned in the
introduction.

Nits/editorial comments:

In the security considerations for authentication-related objects:

OLD
   In order for these sensitive information
   from being improperly accessed, implementers MAY wish to disallow
   access to these objects.
NEW
   In order to prevent this sensitive information
   from being improperly accessed, implementers MAY disallow
   access to these objects.

idnits 2.13.01 found a truly minor nit that should be corrected when
the draft is next revised:

  =3D=3D Outdated reference: A later version (-05) exists of
     draft-ietf-bfd-tc-mib-04

it also generated a warning that probably does not reflect an actual proble=
m:

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
     have content which was first submitted before 10 November 2008.  If yo=
u
     have contacted all the original authors and they are all willing to gr=
ant
     the BCP78 rights to the IETF Trust, then this is fine, and you can ign=
ore
     this comment.  If not, you may need to add the pre-RFC5378 disclaimer.=
=20
     (See the Legal Provisions document at
     http://trustee.ietf.org/license-info for more information.)

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 nobody Thu Apr 17 08:32:50 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 55A6E1A01BB for <gen-art@ietfa.amsl.com>; Thu, 17 Apr 2014 08:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.5
X-Spam-Level: 
X-Spam-Status: No, score=-5.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 j2zTa7R1r0qe for <gen-art@ietfa.amsl.com>; Thu, 17 Apr 2014 08:32:42 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id ACF3F1A0219 for <gen-art@ietf.org>; Thu, 17 Apr 2014 08:32:40 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id s3HFWZAe024918 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 17 Apr 2014 10:32:36 -0500 (CDT)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s3HFWYX8031459 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 17 Apr 2014 10:32:35 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id s3HFWYaU029731; Thu, 17 Apr 2014 10:32:34 -0500 (CDT)
Message-ID: <534FF47C.6020504@bell-labs.com>
Date: Thu, 17 Apr 2014 10:34:20 -0500
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.4.0
MIME-Version: 1.0
To: draft-ietf-l2vpn-vpls-inter-domain-redundancy@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/dw_zbn-8rsF3H-OhIxf9aUueB9w
Cc: l2vpn-chairs@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
Subject: [Gen-art] Gen-ART review of draft-ietf-l2vpn-vpls-inter-domain-redundancy-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, 17 Apr 2014 15:32:47 -0000

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

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

Document: draft-ietf-l2vpn-vpls-inter-domain-redundancy-05
Reviewer: Vijay K. Gurbani
Review Date: Apr-17-2014
IETF LC End Date: Apr-24-2014
IESG Telechat date: Not known.

This document is ready as a Proposed Standard but has some nits and a
minor issue that should be looked at.

Major: 0
Minor: 1
Nits:  7

Minor:

- Section 7, paragraph 2: Okay to use MD5?  Or something stronger...?

Nits:

- Section 1, paragraph 1:
   s/is to provide/provides/

- Section 1, paragraph 2:
   s/options introduced./options are introduced./

- Section 3: What is an "ASBR"?  If it is a well-known term in the
  domain, I suspect you don't need to expand it ...

- Section 3: s/agreements(SLAs)./agreements (SLAs).

- Section 7, first paragraph: s/will have/has/

- Section 7, second paragraph:
  s/ICCP is now/If ICCP is/

- Section 7: You use "pseudowire" here whereas in most of the
  remaining document you used "PW".  You may want to be consistent.

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 nobody Thu Apr 17 09:13:19 2014
Return-Path: <lizho.jin@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 56DEC1A014E for <gen-art@ietfa.amsl.com>; Thu, 17 Apr 2014 09:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[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 cQ_WkfS781rI for <gen-art@ietfa.amsl.com>; Thu, 17 Apr 2014 09:13:09 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB591A0101 for <gen-art@ietf.org>; Thu, 17 Apr 2014 09:13:09 -0700 (PDT)
Received: by mail-ig0-f172.google.com with SMTP id hn18so2449379igb.11 for <gen-art@ietf.org>; Thu, 17 Apr 2014 09:13:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HFw09wABAexk8K+6hd4meWtjL/VkcRbmByNp6IgGQbc=; b=D/7zGtD9MGtykS9+Jjtd5xU+oyF7Hma7DoaJUQlaoXQLfZ3JcEcWWYW0ur3j8FUryc CBZYl17ocBlvZJTS0ctNsAJsqd9pnng887kr1rLmrqtXrLRGyXHc2krCdWn30xX7u+gD Hv+9nEaLersHegN2Y1TUs4hg04/PVJolpi09K9MDfrE9gIoH1c3J99BV5QmBR8TKzlxw SkjIFbcCmMhaQe68u0zWHSYhYzym56G/M+lfWgVJ5Eg9utnHRsBMw7CSHZ/IhhhFILRt VUJfv+noEOvJm+M0D1451yXU5pKqjievFltl01J3figisR9tvLdEYtAxb2KNTRrk2fQ0 cNbw==
MIME-Version: 1.0
X-Received: by 10.43.59.82 with SMTP id wn18mr10260608icb.6.1397751185411; Thu, 17 Apr 2014 09:13:05 -0700 (PDT)
Received: by 10.42.95.208 with HTTP; Thu, 17 Apr 2014 09:13:05 -0700 (PDT)
In-Reply-To: <534FF47C.6020504@bell-labs.com>
References: <534FF47C.6020504@bell-labs.com>
Date: Fri, 18 Apr 2014 00:13:05 +0800
Message-ID: <CAH==cJyw6HANd1bdSYyYMD2QeMhdn3KeSq8iZvODVfaFAMs4Zw@mail.gmail.com>
From: Lizhong Jin <lizho.jin@gmail.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Content-Type: multipart/alternative; boundary=bcaec51961f1e412d004f73f4e25
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/4KlNOGcKI2xDZBQlcUe4bfsK-J4
Cc: "draft-ietf-l2vpn-vpls-inter-domain-redundancy@tools.ietf.org" <draft-ietf-l2vpn-vpls-inter-domain-redundancy@tools.ietf.org>, "l2vpn-chairs@tools.ietf.org" <l2vpn-chairs@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-l2vpn-vpls-inter-domain-redundancy-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, 17 Apr 2014 16:13:14 -0000

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

Hi Vijay,
Thank you for the review. See my reply inline below.

Regards
Lizhong

On Thursday, April 17, 2014, 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>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-l2vpn-vpls-inter-domain-redundancy-05
> Reviewer: Vijay K. Gurbani
> Review Date: Apr-17-2014
> IETF LC End Date: Apr-24-2014
> IESG Telechat date: Not known.
>
> This document is ready as a Proposed Standard but has some nits and a
> minor issue that should be looked at.
>
> Major: 0
> Minor: 1
> Nits:  7
>
> Minor:
>
> - Section 7, paragraph 2: Okay to use MD5?  Or something stronger...?
>
[Lizhong] the MD5 will follow the security consideration in
[I-D.ietf-pwe3-iccp] where "SHOULD" is used. And the security section has
been proposed by SEC-Dir to change as below:
   Besides the security properties of [I-D.ietf-pwe3-iccp] for ICCP
   control plane, [RFC4762] and [RFC6870] for PW control plane, this
   document has additional security consideration for ICCP control
   plane.

   In this document, ICCP protocol is deployed between two PEs or ASBRs.
   The two PEs or ASBRs should only be connected by a well managed and
   highly monitored network.  This should be ensured by the operator.

   The state flapping on the inter-domain and intra-domain PW may cause
   security threats or be exploited to create denial of service attacks.
   For example, excessive PW state flapping (e.g., by malicious peer
   PE's implementation) may lead to excessive ICCP exchanges.
   Implementations SHOULD provide mechanisms to perform control-plane
   policing and mitigate such types of attacks.


>
> Nits:
>
> - Section 1, paragraph 1:
>   s/is to provide/provides/
>
[Lizhong] accepted

>
> - Section 1, paragraph 2:
>   s/options introduced./options are introduced./
>
[Lizhong] accepted

>
> - Section 3: What is an "ASBR"?  If it is a well-known term in the
>  domain, I suspect you don't need to expand it ...
>
[Lizhong] should be expanded. Thanks.

>
> - Section 3: s/agreements(SLAs)./agreements (SLAs).
>
[Lizhong] accepted

>
> - Section 7, first paragraph: s/will have/has/
>
[Lizhong] accepted

>
> - Section 7, second paragraph:
>  s/ICCP is now/If ICCP is/
>
[Lizhong] accepted

>
> - Section 7: You use "pseudowire" here whereas in most of the
>  remaining document you used "PW".  You may want to be consistent.
>
[Lizhong] accepted

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

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

Hi Vijay,<div>Thank you for the review. See my reply inline below.</div><di=
v><br></div><div>Regards</div><div>Lizhong<br><br>On Thursday, April 17, 20=
14, Vijay K. Gurbani &lt;<a href=3D"mailto:vkg@bell-labs.com">vkg@bell-labs=
.com</a>&gt; 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>
&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-l2vpn-vpls-inter-<u></u>domain-redundancy-05<br>
Reviewer: Vijay K. Gurbani<br>
Review Date: Apr-17-2014<br>
IETF LC End Date: Apr-24-2014<br>
IESG Telechat date: Not known.<br>
<br>
This document is ready as a Proposed Standard but has some nits and a<br>
minor issue that should be looked at.<br>
<br>
Major: 0<br>
Minor: 1<br>
Nits: =C2=A07<br>
<br>
Minor:<br>
<br>
- Section 7, paragraph 2: Okay to use MD5? =C2=A0Or something stronger...?<=
br></blockquote><div>[Lizhong] the MD5 will follow the security considerati=
on in [I-D.ietf-pwe3-iccp] where &quot;SHOULD&quot; is used. And the securi=
ty section has been proposed by SEC-Dir to change as below:</div>
<div><div>=C2=A0 =C2=A0Besides the security properties of [I-D.ietf-pwe3-ic=
cp] for ICCP</div><div>=C2=A0 =C2=A0control plane, [RFC4762] and [RFC6870] =
for PW control plane, this</div><div>=C2=A0 =C2=A0document has additional s=
ecurity consideration for ICCP control</div>
<div>=C2=A0 =C2=A0plane.</div><div><br></div><div>=C2=A0 =C2=A0In this docu=
ment, ICCP protocol is deployed between two PEs or ASBRs.</div><div>=C2=A0 =
=C2=A0The two PEs or ASBRs should only be connected by a well managed and</=
div><div>=C2=A0 =C2=A0highly monitored network. =C2=A0This should be ensure=
d by the operator.</div>
<div><br></div><div>=C2=A0 =C2=A0The state flapping on the inter-domain and=
 intra-domain PW may cause</div><div>=C2=A0 =C2=A0security threats or be ex=
ploited to create denial of service attacks.</div><div>=C2=A0 =C2=A0For exa=
mple, excessive PW state flapping (e.g., by malicious peer</div>
<div>=C2=A0 =C2=A0PE&#39;s implementation) may lead to excessive ICCP excha=
nges.</div><div>=C2=A0 =C2=A0Implementations SHOULD provide mechanisms to p=
erform control-plane</div><div>=C2=A0 =C2=A0policing and mitigate such type=
s of attacks.</div></div><div>
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
<br>
Nits:<br>
<br>
- Section 1, paragraph 1:<br>
=C2=A0 s/is to provide/provides/<br></blockquote><div>[Lizhong] accepted=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<br>
- Section 1, paragraph 2:<br>
=C2=A0 s/options introduced./options are introduced./<br></blockquote><div>=
[Lizhong] accepted=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- Section 3: What is an &quot;ASBR&quot;? =C2=A0If it is a well-known term =
in the<br>
=C2=A0domain, I suspect you don&#39;t need to expand it ...<br></blockquote=
><div>[Lizhong] should be expanded. Thanks.=C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">

<br>
- Section 3: s/agreements(SLAs)./agreements (SLAs).<br></blockquote><div>[L=
izhong] accepted=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- Section 7, first paragraph: s/will have/has/<br></blockquote><div>[Lizhon=
g] accepted</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- Section 7, second paragraph:<br>
=C2=A0s/ICCP is now/If ICCP is/<br></blockquote><div>[Lizhong] accepted=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<br>
- Section 7: You use &quot;pseudowire&quot; here whereas in most of the<br>
=C2=A0remaining document you used &quot;PW&quot;. =C2=A0You may want to be =
consistent.<br></blockquote><div>[Lizhong] accepted=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">

<br>
Thanks,<br>
<br>
- vijay<br>
-- <br>
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent<br>
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)<br>
Email: vkg@{<a href=3D"http://bell-labs.com" target=3D"_blank">bell-labs.co=
m</a>,<a href=3D"http://acm.org" target=3D"_blank">acm.org</a>} / <a>vijay.=
gurbani@alcatel-lucent.com</a><br>
Web: <a href=3D"http://ect.bell-labs.com/who/vkg/" target=3D"_blank">http:/=
/ect.bell-labs.com/who/<u></u>vkg/</a> =C2=A0| Calendar: <a href=3D"http://=
goo.gl/x3Ogq" target=3D"_blank">http://goo.gl/x3Ogq</a><br>
</blockquote></div>

--bcaec51961f1e412d004f73f4e25--


From nobody Thu Apr 17 09:18: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 F2B441A00E6 for <gen-art@ietfa.amsl.com>; Thu, 17 Apr 2014 09:18:39 -0700 (PDT)
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 CGkPc0FJyK_f for <gen-art@ietfa.amsl.com>; Thu, 17 Apr 2014 09:18:35 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 537DC1A00A3 for <gen-art@ietf.org>; Thu, 17 Apr 2014 09:18:34 -0700 (PDT)
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 s3HGITX3010623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 17 Apr 2014 11:18:30 -0500 (CDT)
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 s3HGIT0m031316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 17 Apr 2014 11:18:29 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id s3HGIT6K027495; Thu, 17 Apr 2014 11:18:29 -0500 (CDT)
Message-ID: <534FFF3F.6070108@bell-labs.com>
Date: Thu, 17 Apr 2014 11:20:15 -0500
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.4.0
MIME-Version: 1.0
To: Lizhong Jin <lizho.jin@gmail.com>
References: <534FF47C.6020504@bell-labs.com> <CAH==cJyw6HANd1bdSYyYMD2QeMhdn3KeSq8iZvODVfaFAMs4Zw@mail.gmail.com>
In-Reply-To: <CAH==cJyw6HANd1bdSYyYMD2QeMhdn3KeSq8iZvODVfaFAMs4Zw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/WPmTJ7j8IDf4hrgbQjnKzsiIGSQ
Cc: "draft-ietf-l2vpn-vpls-inter-domain-redundancy@tools.ietf.org" <draft-ietf-l2vpn-vpls-inter-domain-redundancy@tools.ietf.org>, "l2vpn-chairs@tools.ietf.org" <l2vpn-chairs@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-l2vpn-vpls-inter-domain-redundancy-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, 17 Apr 2014 16:18:40 -0000

On 04/17/2014 11:13 AM, Lizhong Jin wrote:
>     - Section 7, paragraph 2: Okay to use MD5?  Or something stronger...?
>
> [Lizhong] the MD5 will follow the security consideration in
> [I-D.ietf-pwe3-iccp] where "SHOULD" is used. And the security section
> has been proposed by SEC-Dir to change as below: [...]

Lizhong: No worries; I just wanted to make sure that enough eyeballs had
paid attention to MD5, and it appears that is the case.

Thanks for accepting the rest of the nits.

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 nobody Thu Apr 17 14:31:57 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 5D0441A0167; Thu, 17 Apr 2014 14:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 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.272, 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 YQaQqrcGVipN; Thu, 17 Apr 2014 14:31:49 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 26B9F1A0133; Thu, 17 Apr 2014 14:31:48 -0700 (PDT)
Received: from maildlpprd54.lss.emc.com (maildlpprd54.lss.emc.com [10.106.48.158]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3HLVfcP030891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Apr 2014 17:31:41 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s3HLVfcP030891
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1397770302; bh=g4RSLBFR0A8YAd4iJhfH78ibJFY=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=VSrAbX62azadSl/bgkEfACJ7xVeub5vI5M3Ugi92nd2h0sePVXA1gcelbhYer755Y kGc+z2mIUaO89oz5n3fqp6XiiX3FVyfT+efO8QP61R4dQMYSTccSSTLINc3pZHDJCE 2TSVbGebcEpHqbGjy7lr6NENVl/WPQ/WEKGzM75U=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s3HLVfcP030891
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd54.lss.emc.com (RSA Interceptor); Thu, 17 Apr 2014 17:31:25 -0400
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3HLVPUI006105 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 17 Apr 2014 17:31:25 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub18.corp.emc.com ([10.254.93.47]) with mapi; Thu, 17 Apr 2014 17:31:25 -0400
From: "Black, David" <david.black@emc.com>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "Zafar Ali (zali)" <zali@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Thu, 17 Apr 2014 17:31:23 -0400
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpAAiJosQAAum6hA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C2EC413@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.cisco.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/URgFzqKqhqPCBe5dHqxsyLYHusE
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 17 Apr 2014 21:31:53 -0000

Hi Nobo,

> > This MIB contains many writable objects, so the authors should take not=
e of
> > the IESG statement on writable MIB modules:
> >
> > 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> >
> > I did not see this mentioned in the shepherd writeup.  If the OPS Area =
has
> > not been consulted, I strongly suggest doing so during IETF Last Call, =
e.g.,
> > starting with Benoit Claise (AD).
>=20
> I remember seeing the statement from IESG, which I agree is a good direct=
ion
> for new charter items. [This] BFD MIB, on the other hand, is almost 10 ye=
ars
> old, with several implementations already around. I highly suspect the WG=
 will
> not want to see *change of direction* at this point. With that said, let =
me
> take this up with the AD and the Shepherd.

I have no problem with "running code" as a good reason to continue with
writable objects in this MIB; taking this topic up with your AD and Shepher=
d
should suffice.

> > I suggest that the authors recheck the entire MIB to ensure that every =
object
> > or table that should be included in the security considerations section=
 is
> > appropriately included.
>=20
> I've gone through them. There are set of objects which really should not =
be
> modified once a session is functioning. I've added this in the security
> considerations section.

Good - thank you for doing that.

Everything else is fine with me, and I appreciate the prompt response.

Thanks,
--David

> -----Original Message-----
> From: Nobo Akiya (nobo) [mailto:nobo@cisco.com]
> Sent: Thursday, April 17, 2014 5:18 PM
> To: Black, David; tnadeau@lucidvision.com; Zafar Ali (zali); General Area
> Review Team (gen-art@ietf.org)
> Cc: rtg-bfd@ietf.org; ietf@ietf.org
> Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
>=20
> Hi David,
>=20
> Thank you for thorough review of this document.
> Please see replies in-line.
>=20
> > -----Original Message-----
> > From: Black, David [mailto:david.black@emc.com]
> > Sent: Wednesday, April 16, 2014 7:31 PM
> > To: tnadeau@lucidvision.com; Zafar Ali (zali); Nobo Akiya (nobo); Gener=
al
> > Area Review Team (gen-art@ietf.org)
> > Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> > Subject: Gen-ART review of draft-ietf-bfd-mib-17
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on Ge=
n-
> > ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-bfd-mib-17
> > Reviewer: David L. Black
> > Review Date: April 16, 2014
> > IETF LC End Date: April 28, 2014
> >
> > Summary: This draft is on the right track, but has open issues
> > 		described in the review.
> >
> > This draft is a MIB module for the BFD protocol, which is an important =
low-
> > level routing protocol.  The draft is reasonable for a MIB draft; one n=
eeds
> to
> > go read the protocol documents to understand how the protocol works, an=
d
> > significant portions of the text are derived from the usual MIB
> "boilerplate"
> > as one would expect.  The "Brief Description of MIB Objects" is indeed
> brief,
> > but reasonable.  The shepherd writeup indicates that there are multiple
> > implementations.
> >
> > Major issues:
> >
> > This MIB contains many writable objects, so the authors should take not=
e of
> > the IESG statement on writable MIB modules:
> >
> > 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> >
> > I did not see this mentioned in the shepherd writeup.  If the OPS Area =
has
> > not been consulted, I strongly suggest doing so during IETF Last Call, =
e.g.,
> > starting with Benoit Claise (AD).
>=20
> I remember seeing the statement from IESG, which I agree is a good direct=
ion
> for new charter items. [This] BFD MIB, on the other hand, is almost 10 ye=
ars
> old, with several implementations already around. I highly suspect the WG=
 will
> not want to see *change of direction* at this point. With that said, let =
me
> take this up with the AD and the Shepherd.
>=20
> >
> > Minor issues:
> >
> > The security considerations section includes considerations for
> > unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus,
> > but omits the corresponding considerations for bfdAdminStatus and
> > bfdSessNotificationsEnable.  Both of the latter objects are global, so
> > significant damage can be inflicted via these objects with a small numb=
er of
> > unauthorized modifications, so they need to be included in the first li=
st of
> > sensitive objects.
>=20
> Good point. I will add bfdAdminStatus and bfdOperStatus in the security
> considerations section.
>=20
> >
> > I suggest that the authors recheck the entire MIB to ensure that every
> object
> > or table that should be included in the security considerations section=
 is
> > appropriately included.
>=20
> I've gone through them. There are set of objects which really should not =
be
> modified once a session is functioning. I've added this in the security
> considerations section.
>=20
>    o  Some management objects define the BFD session whilst other
>       management objects define the parameter of the BFD session.  It is
>       particularly important to control the support for SET access to
>       those management objects that define the BFD session, as changes
>       to them can be disruptive.  Implementation SHOULD NOT allow
>       changes to following management objects when bfdSessState is
>       up(4):
>=20
>       *  bfdSessVersionNumber
>       *  bfdSessType
>       *  bfdSessDestinationUdpPort
>       *  bfdSessMultipointFlag
>       *  bfdSessInterface
>       *  bfdSessSrcAddrType
>       *  bfdSessSrcAddr
>       *  bfdSessDstAddrType
>       *  bfdSessDstAddr
>=20
> >
> > Also, as a General Variable, would bfdSessNotificationsEnable be better
> > named bfdNotificationsEnable, as it's not in the BFD Session Table?
>=20
> That's true. Renamed as suggested.
>=20
> >
> > I did not see a compliance requirement for a system that only implement=
s
> > BFD protocol version 0.  That absence should at least be mentioned
> > somewhere.  For example, if this reflects a considered and deliberate
> > decision by the WG, that should be mentioned in the introduction.
>=20
> Good point. If I remember correctly, BFD version 0 had a problem in the s=
tate
> machine that can cause the two ends to fall into a deadlock. It would be,
> therefore, very bad for anybody to have BFD version 0 deployed out there,=
 and
> asking for any MIB compliance requirement for such. Consensus on absence =
of
> compliance requirement for BFD version 0 was never polled in the WG, but =
I can
> say that there shouldn't be any desire for that.
>=20
> I will add a short statement on lack of BFD version 0 compliance requirem=
ent
> in the introduction section, as you suggested.
>=20
> >
> > Nits/editorial comments:
> >
> > In the security considerations for authentication-related objects:
> >
> > OLD
> >    In order for these sensitive information
> >    from being improperly accessed, implementers MAY wish to disallow
> >    access to these objects.
> > NEW
> >    In order to prevent this sensitive information
> >    from being improperly accessed, implementers MAY disallow
> >    access to these objects.
>=20
> Thanks for the text. Updated in local copy.
>=20
> >
> > idnits 2.13.01 found a truly minor nit that should be corrected when th=
e
> > draft is next revised:
> >
> >   =3D=3D Outdated reference: A later version (-05) exists of
> >      draft-ietf-bfd-tc-mib-04
>=20
> Agree, non-issue.
>=20
> >
> > it also generated a warning that probably does not reflect an actual
> > problem:
> >
> >   -- The document seems to lack a disclaimer for pre-RFC5378 work, but =
may
> >      have content which was first submitted before 10 November 2008.  I=
f you
> >      have contacted all the original authors and they are all willing t=
o
> grant
> >      the BCP78 rights to the IETF Trust, then this is fine, and you can
> ignore
> >      this comment.  If not, you may need to add the pre-RFC5378 disclai=
mer.
> >      (See the Legal Provisions document at
> >      http://trustee.ietf.org/license-info for more information.)
>=20
> Agree, non-issue.
>=20
> Thanks again!
>=20
> -Nobo
>=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=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
>=20


From nobody Thu Apr 17 14:55:36 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 86D601A01D6; Thu, 17 Apr 2014 14:55:32 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 cESKme936dPR; Thu, 17 Apr 2014 14:55:30 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 4B72C1A01CE; Thu, 17 Apr 2014 14:55:30 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3HLtKmr011886; Thu, 17 Apr 2014 22:55:20 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3HLtJQ1011877 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 17 Apr 2014 22:55:19 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Black, David'" <david.black@emc.com>, <tnadeau@lucidvision.com>, <zali@cisco.com>, <nobo@cisco.com>, "'General Area Review Team'" <gen-art@ietf.org>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com>
Date: Thu, 17 Apr 2014 22:55:18 +0100
Message-ID: <051b01cf5a87$b92a84d0$2b7f8e70$@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: AQHXstybkl3Rj5QCVQi0ErrtVmSSApsFo67A
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.0.0.1014-20640.002
X-TM-AS-Result: No--7.041-10.0-31-10
X-imss-scan-details: No--7.041-10.0-31-10
X-TMASE-MatchedRID: QfHZjzml1E+nykMun0J1wpmug812qIbzC/ExpXrHizxXopZjyO6CZaem Jq66qqv9A72lF8jbwSm+h2+kRiP1Xo4a2rhHAtuZoMfp2vHck9WHxi2fvkKUM8izgKND8Lm5VZ8 xQvqztISd5Vi9MggDmL1DgIPIkgsZSWKSZniod93ThGbP9qB93B9fNWA7SFWqWltirZ/iPP4Duw Qv5f82WF/nw1MAso95JvN5sPGL1gQqCxvBy34zX2gws6g0ewz2moKXVHfiMM8gcyGevtftJ6PFj JEFr+olqYB+kyCYtxRcLc3sLtjOt+TCMddcL/gjOwBXM346/+zID5XcD4FtapcOFu+rNPoeDEFa KkIPel+133QqrH6lMVsi4ALUpd8T
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/5BCo8m3KscpVmUfLZZk5zbRBkl0
Cc: rtg-bfd@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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: Thu, 17 Apr 2014 21:55:32 -0000

Hi David,

Thanks for the review.

To pick out one of your points:

> This MIB contains many writable objects, so the authors should
> take note of the IESG statement on writable MIB modules:
> 
> 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> 
> I did not see this mentioned in the shepherd writeup.  If the OPS Area
> has not been consulted, I strongly suggest doing so during IETF Last
> Call, e.g., starting with Benoit Claise (AD).

The OPS Directorate and the MIB Doctors will have been alerted to this document
by the last call and we can expect their comments.

But this question was discussed between the AD and the authors, and the AD was
unlikely to agree to sponsor the document if he felt it went against the IESG
statement. Our discussion resulted in some reduction of writeable objects.

I think there are several points to consider:
1. This document had already been completed and publication requested (i.e.
shepherd write-up written) at the time of the IESG statement. It would be
unreasonable to make the statement retrospective.
2. There are already various implementations in equipment (not just management
stations) of proprietary modules approximating to this document and these
support write-access.
3. This is a low-level component protocol of the sort that is used on dumber
devices and that is an area where write-access is more common.

Cheers,
Adrian



From nobody Thu Apr 17 15:06:49 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 A974F1A01AD; Thu, 17 Apr 2014 15:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 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.272, 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 qlcU0EXzAanW; Thu, 17 Apr 2014 15:06:42 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1BF1A01A5; Thu, 17 Apr 2014 15:06:41 -0700 (PDT)
Received: from maildlpprd01.lss.emc.com (maildlpprd01.lss.emc.com [10.253.24.33]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3HM6WCl028810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Apr 2014 18:06:33 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s3HM6WCl028810
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1397772394; bh=x5lPp3hwEyXiFe09SBaiImx5+CQ=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=DUr7XRUrSxNEVBasvsv0aoBRzweKYySNTspmpf2P6t97h4d+7kpT2fEAkcCjzMQK8 PJ8AsSk6sI5BsAZjUKZCkLDdt8jnKwFEZOwpNGxu2SFMVcURN4U6BpxTP3mg+mJHYl LdAG7S8UalWA7VJlISkl+eOQR5EaP0h/CmTS/5bI=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s3HM6WCl028810
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd01.lss.emc.com (RSA Interceptor); Thu, 17 Apr 2014 18:06:22 -0400
Received: from mxhub28.corp.emc.com (mxhub28.corp.emc.com [10.254.110.184]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3HM6Lqn009455 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 17 Apr 2014 18:06:21 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub28.corp.emc.com ([10.254.110.184]) with mapi; Thu, 17 Apr 2014 18:06:21 -0400
From: "Black, David" <david.black@emc.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "zali@cisco.com" <zali@cisco.com>, "nobo@cisco.com" <nobo@cisco.com>, "'General Area Review Team'" <gen-art@ietf.org>
Date: Thu, 17 Apr 2014 18:06:20 -0400
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: AQHXstybkl3Rj5QCVQi0ErrtVmSSApsFo67AgAAGUSA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C2EC421@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
In-Reply-To: <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
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: mailusrhubprd54.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/mreQsu7Pct3A5C00sTcX0bbedOA
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 17 Apr 2014 22:06:44 -0000

Hi Adrian,

As clarified in my response to Nobo, I raised the concern about writable
MIB modules primarily as a process check (I was expecting to find something
on this topic in the shepherd writeup, and didn't).  In particular, this
concern was not intended as a strong reason not to publish, and I have no
disagreements with any of the points in your message below.

With you on top of this and the OPS folks sure to notice, I have no doubt
that this will get suitably addressed, although it might be simpler to
ensure that the OPS Area is ok now rather than waiting for IESG Evaluation.

Thanks,
--David (in part, wearing his OPS Directorate member "hat").

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Thursday, April 17, 2014 5:55 PM
> To: Black, David; tnadeau@lucidvision.com; zali@cisco.com; nobo@cisco.com=
;
> 'General Area Review Team'
> Cc: rtg-bfd@ietf.org; ietf@ietf.org
> Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
>=20
> Hi David,
>=20
> Thanks for the review.
>=20
> To pick out one of your points:
>=20
> > This MIB contains many writable objects, so the authors should
> > take note of the IESG statement on writable MIB modules:
> >
> > 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> >
> > I did not see this mentioned in the shepherd writeup.  If the OPS Area
> > has not been consulted, I strongly suggest doing so during IETF Last
> > Call, e.g., starting with Benoit Claise (AD).
>=20
> The OPS Directorate and the MIB Doctors will have been alerted to this
> document
> by the last call and we can expect their comments.
>=20
> But this question was discussed between the AD and the authors, and the A=
D was
> unlikely to agree to sponsor the document if he felt it went against the =
IESG
> statement. Our discussion resulted in some reduction of writeable objects=
.
>=20
> I think there are several points to consider:
> 1. This document had already been completed and publication requested (i.=
e.
> shepherd write-up written) at the time of the IESG statement. It would be
> unreasonable to make the statement retrospective.
> 2. There are already various implementations in equipment (not just manag=
ement
> stations) of proprietary modules approximating to this document and these
> support write-access.
> 3. This is a low-level component protocol of the sort that is used on dum=
ber
> devices and that is an area where write-access is more common.
>=20
> Cheers,
> Adrian
>=20
>=20


From nobody Thu Apr 17 15:10:58 2014
Return-Path: <nobo@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 E519A1A0168; Thu, 17 Apr 2014 14:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.773
X-Spam-Level: 
X-Spam-Status: No, score=-114.773 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.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, 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 w6XFA6VeeC2l; Thu, 17 Apr 2014 14:18:34 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 135CD1A0054; Thu, 17 Apr 2014 14:18:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6800; q=dns/txt; s=iport; t=1397769510; x=1398979110; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hLKYK5Tid4Oymx7mWHA3JWXrFKs8DPKGdfamuUTiTOw=; b=ONWRRAQZXfZt/cLeHmsVHE371nt7WfIarDx/E8judYe+J8CvEXPeaSaQ M/UEDFThlYNkKA+k2V0PcXFLBos4irsS/R4YWyhmQxZqkIN4SRKCtdTA+ c7ROZAx4hwCEYcvDX6gAYGLbe6lZlop1N0n6XDWi6i0lJu+NHON9uhUVg 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAGNEUFOtJA2K/2dsb2JhbABWA4JlITtXw2eBJxZ0giUBAQEDAXkMBAIBCBEDAQEBCx0HMhQJCAEBBAENBQgBh2sIAQzMHBeMb4FCIRACBQYLgxOBFASIdDaLVoUlkRaDMYIr
X-IronPort-AV: E=Sophos;i="4.97,881,1389744000"; d="scan'208";a="318644398"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-4.cisco.com with ESMTP; 17 Apr 2014 21:18:30 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s3HLITFG025344 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 17 Apr 2014 21:18:29 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Thu, 17 Apr 2014 16:18:29 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Black, David" <david.black@emc.com>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "Zafar Ali (zali)" <zali@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpAAiJosQ
Date: Thu, 17 Apr 2014 21:18:28 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.212.138]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Cg6NRAQso6NAvxGO41OuIOOIWpo
X-Mailman-Approved-At: Thu, 17 Apr 2014 15:10:55 -0700
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 17 Apr 2014 21:18:41 -0000

Hi David,

Thank you for thorough review of this document.
Please see replies in-line.

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Wednesday, April 16, 2014 7:31 PM
> To: tnadeau@lucidvision.com; Zafar Ali (zali); Nobo Akiya (nobo); General
> Area Review Team (gen-art@ietf.org)
> Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> Subject: Gen-ART review of draft-ietf-bfd-mib-17
>=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-bfd-mib-17
> Reviewer: David L. Black
> Review Date: April 16, 2014
> IETF LC End Date: April 28, 2014
>=20
> Summary: This draft is on the right track, but has open issues
> 		described in the review.
>=20
> This draft is a MIB module for the BFD protocol, which is an important lo=
w-
> level routing protocol.  The draft is reasonable for a MIB draft; one nee=
ds to
> go read the protocol documents to understand how the protocol works, and
> significant portions of the text are derived from the usual MIB "boilerpl=
ate"
> as one would expect.  The "Brief Description of MIB Objects" is indeed br=
ief,
> but reasonable.  The shepherd writeup indicates that there are multiple
> implementations.
>=20
> Major issues:
>=20
> This MIB contains many writable objects, so the authors should take note =
of
> the IESG statement on writable MIB modules:
>=20
> 	http://www.ietf.org/iesg/statement/writable-mib-module.html
>=20
> I did not see this mentioned in the shepherd writeup.  If the OPS Area ha=
s
> not been consulted, I strongly suggest doing so during IETF Last Call, e.=
g.,
> starting with Benoit Claise (AD).

I remember seeing the statement from IESG, which I agree is a good directio=
n for new charter items. [This] BFD MIB, on the other hand, is almost 10 ye=
ars old, with several implementations already around. I highly suspect the =
WG will not want to see *change of direction* at this point. With that said=
, let me take this up with the AD and the Shepherd.

>=20
> Minor issues:
>=20
> The security considerations section includes considerations for
> unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus,
> but omits the corresponding considerations for bfdAdminStatus and
> bfdSessNotificationsEnable.  Both of the latter objects are global, so
> significant damage can be inflicted via these objects with a small number=
 of
> unauthorized modifications, so they need to be included in the first list=
 of
> sensitive objects.

Good point. I will add bfdAdminStatus and bfdOperStatus in the security con=
siderations section.

>=20
> I suggest that the authors recheck the entire MIB to ensure that every ob=
ject
> or table that should be included in the security considerations section i=
s
> appropriately included.

I've gone through them. There are set of objects which really should not be=
 modified once a session is functioning. I've added this in the security co=
nsiderations section.

   o  Some management objects define the BFD session whilst other
      management objects define the parameter of the BFD session.  It is
      particularly important to control the support for SET access to
      those management objects that define the BFD session, as changes
      to them can be disruptive.  Implementation SHOULD NOT allow
      changes to following management objects when bfdSessState is
      up(4):

      *  bfdSessVersionNumber
      *  bfdSessType
      *  bfdSessDestinationUdpPort
      *  bfdSessMultipointFlag
      *  bfdSessInterface
      *  bfdSessSrcAddrType
      *  bfdSessSrcAddr
      *  bfdSessDstAddrType
      *  bfdSessDstAddr

>=20
> Also, as a General Variable, would bfdSessNotificationsEnable be better
> named bfdNotificationsEnable, as it's not in the BFD Session Table?

That's true. Renamed as suggested.

>=20
> I did not see a compliance requirement for a system that only implements
> BFD protocol version 0.  That absence should at least be mentioned
> somewhere.  For example, if this reflects a considered and deliberate
> decision by the WG, that should be mentioned in the introduction.

Good point. If I remember correctly, BFD version 0 had a problem in the sta=
te machine that can cause the two ends to fall into a deadlock. It would be=
, therefore, very bad for anybody to have BFD version 0 deployed out there,=
 and asking for any MIB compliance requirement for such. Consensus on absen=
ce of compliance requirement for BFD version 0 was never polled in the WG, =
but I can say that there shouldn't be any desire for that.

I will add a short statement on lack of BFD version 0 compliance requiremen=
t in the introduction section, as you suggested.

>=20
> Nits/editorial comments:
>=20
> In the security considerations for authentication-related objects:
>=20
> OLD
>    In order for these sensitive information
>    from being improperly accessed, implementers MAY wish to disallow
>    access to these objects.
> NEW
>    In order to prevent this sensitive information
>    from being improperly accessed, implementers MAY disallow
>    access to these objects.

Thanks for the text. Updated in local copy.

>=20
> idnits 2.13.01 found a truly minor nit that should be corrected when the
> draft is next revised:
>=20
>   =3D=3D Outdated reference: A later version (-05) exists of
>      draft-ietf-bfd-tc-mib-04

Agree, non-issue.

>=20
> it also generated a warning that probably does not reflect an actual
> problem:
>=20
>   -- The document seems to lack a disclaimer for pre-RFC5378 work, but ma=
y
>      have content which was first submitted before 10 November 2008.  If =
you
>      have contacted all the original authors and they are all willing to =
grant
>      the BCP78 rights to the IETF Trust, then this is fine, and you can i=
gnore
>      this comment.  If not, you may need to add the pre-RFC5378 disclaime=
r.
>      (See the Legal Provisions document at
>      http://trustee.ietf.org/license-info for more information.)

Agree, non-issue.

Thanks again!

-Nobo

>=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 nobody Thu Apr 17 15:11:35 2014
Return-Path: <aldrin.ietf@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 45E821A0100; Thu, 17 Apr 2014 15:11:32 -0700 (PDT)
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 u9_pYKbvpYtm; Thu, 17 Apr 2014 15:11:22 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id D3D081A00FE; Thu, 17 Apr 2014 15:11:21 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id rr13so817177pbb.25 for <multiple recipients>; Thu, 17 Apr 2014 15:11:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LFXLyYpahXiiwnMu44Nc1E4R1kYqRN49rDIcE/QeGfo=; b=hEaJUEsbwsaPkVvXJvmykvB/SjKfpBJPXbck3oieXVwQndHu9UX3k/h3KV7TjJLNw0 yC9HyPHV/BlJ1J32NbDXcd8P4Mlv/essuIDn30UsHqGNa7Hi69ApxJECNkGfFX2QTowQ p3DTjEbzG2xlrzryaJ04J4lYqgBF5viHgYpztCIf9r0B+QooxMum2JuJjqN7Pu9SIjgR QAbRvEtB7+d9fnkVPlNIYPFT1EVh8sbmwjhb9mpl0vOaioZ2o/dj5KJWEO/l5g1vFRiR CZOuUBR3c0QtSh0oau/iwFrAisF6vbG96ABDHYfWdno2+bJSo3V3Kn7LlGyUGwevVIHn 9GLg==
X-Received: by 10.68.254.103 with SMTP id ah7mr18009827pbd.159.1397772678265;  Thu, 17 Apr 2014 15:11:18 -0700 (PDT)
Received: from [192.168.1.7] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id pl10sm55697899pbb.56.2014.04.17.15.11.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 15:11:17 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
In-Reply-To: <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
Date: Thu, 17 Apr 2014 15:11:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/qg28cNdbSx0qv8AkOuXoXSAjkxs
Cc: tnadeau@lucidvision.com, ietf@ietf.org, nobo@cisco.com, rtg-bfd@ietf.org, zali@cisco.com, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 17 Apr 2014 22:11:32 -0000

Hi Adrian,

One comment inline.

On Apr 17, 2014, at 2:55 PM, Adrian Farrel wrote:

> Hi David,
>=20
> Thanks for the review.
>=20
> To pick out one of your points:
>=20
>> This MIB contains many writable objects, so the authors should
>> take note of the IESG statement on writable MIB modules:
>>=20
>> 	http://www.ietf.org/iesg/statement/writable-mib-module.html
>>=20
>> I did not see this mentioned in the shepherd writeup.  If the OPS =
Area
>> has not been consulted, I strongly suggest doing so during IETF Last
>> Call, e.g., starting with Benoit Claise (AD).
>=20
> The OPS Directorate and the MIB Doctors will have been alerted to this =
document
> by the last call and we can expect their comments.
>=20
> But this question was discussed between the AD and the authors, and =
the AD was
> unlikely to agree to sponsor the document if he felt it went against =
the IESG
> statement. Our discussion resulted in some reduction of writeable =
objects.
>=20
> I think there are several points to consider:
> 1. This document had already been completed and publication requested =
(i.e.
> shepherd write-up written) at the time of the IESG statement. It would =
be
> unreasonable to make the statement retrospective.
> 2. There are already various implementations in equipment (not just =
management
> stations) of proprietary modules approximating to this document and =
these
> support write-access.

%sam - If this MIB allows write access, do you/WG anticipate, any =
extension to the MIB should also provide write-access as well? For =
example: http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ =
augments this base MIB to support MPLS. It adds more confusion than =
solving the issue as base MIB supports write-access, but augmented/ MIB =
extension doesn't.=20

As the BFD MIB authors were not supportive of write-access objects in =
the MIBs, why to have them in the first place?=20

cheers
-sam
> 3. This is a low-level component protocol of the sort that is used on =
dumber
> devices and that is an area where write-access is more common.
>=20
> Cheers,
> Adrian
>=20
>=20


From nobody Thu Apr 17 15:40:26 2014
Return-Path: <aldrin.ietf@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 EE9291A0188; Thu, 17 Apr 2014 15:40:24 -0700 (PDT)
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 eR_prD7fdVy2; Thu, 17 Apr 2014 15:40:23 -0700 (PDT)
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 521771A0176; Thu, 17 Apr 2014 15:40:23 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id p10so819849pdj.31 for <multiple recipients>; Thu, 17 Apr 2014 15:40:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gvbubcSt5auUHsa6TpP/bsQ7HxWk9Ll6lcrsfEFtZM4=; b=Wa90Z3SjJ5EUcQ0Zhw5maeny+KUACTiXLvadWHgr64xSZRd+xJMfswJPBdOk8qse/U las9lpQ1UcnZkWWahW9X/DQJONUwOO8kVFws5P1dyk88AiOhHRE+J7dKuya8m01gags3 pam2RY55WXalW+8GyKNmRYVJN/sM3dsOhhgYGmQ5V2A8aRffe8PRXmmjseKjvkIju3of M06loibhYLTEsmdbx11A+d8dWQB8+w9YRGw3srC6bgMiqrCUS9qdpoTfQcvOZvEDV0ZY kbFfkLE1LjwFYx6zZ3hvXL6x2NBZ3WzvzOy70NYpDMuzDzasVvC/CexWuqqYKnH4YdZJ S7qA==
X-Received: by 10.66.253.33 with SMTP id zx1mr18534581pac.28.1397774419692; Thu, 17 Apr 2014 15:40:19 -0700 (PDT)
Received: from [192.168.1.7] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id q10sm55812565pbl.29.2014.04.17.15.40.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 15:40:17 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
In-Reply-To: <20140417221850.GD29430@pfrc>
Date: Thu, 17 Apr 2014 15:40:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc>
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/VwzIwVZ-vmzS-JIeUSaLkMFkXbE
Cc: ietf@ietf.org, adrian@olddog.co.uk, rtg-bfd@ietf.org, zali@cisco.com, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 17 Apr 2014 22:40:25 -0000

Hi Jeff,

Comments inline.

On Apr 17, 2014, at 3:18 PM, Jeffrey Haas wrote:

> Sam,
>=20
> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>> %sam - If this MIB allows write access, do you/WG anticipate, any =
extension to the MIB should also provide write-access as well? For =
example: http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ =
augments this base MIB to support MPLS. It adds more confusion than =
solving the issue as base MIB supports write-access, but augmented/ MIB =
extension doesn't.=20
>>=20
>> As the BFD MIB authors were not supportive of write-access objects in =
the MIBs, why to have them in the first place?=20
>=20
> As noted in earlier mailing list chatter, there is some support for =
write
> access in existing implementations.  Given the lack of significant =
detail
> when pressed for the name of such an implementation, I'm suspecting =
smaller
> vendor or internal implementation.  That's still sufficient to leave =
write
> available.
>=20
> Given that one of the original contexts of asking if we could remove =
write
> was whether IETF was being asked to provide such a thing for MPLS-TP =
with
> related impact on your extension MIB and the answer was "no", that =
shouldn't
> be the main criteria. =20
No. The context of my question is not related to MPLS-TP as such, but =
write-access support in general.=20
I should have added 'clarification' in my earlier email.
>=20
> My suspicion is that if we were to ship the base MIB with writeable =
objects,
> we may be forced to consider similar things for the extension MIB(s).
Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE =
and BFD-MIB respectively,  with write-access. Had to do write-access =
because of the reason you've mentioned above, which is base MIB. It =
would be painful to publish/support write-access MIB's when there is no =
clear interest. Hence my clarification question.=20

-sam

>=20
> -- Jeff


From nobody Thu Apr 17 18:05:03 2014
Return-Path: <nobo@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 313A91A01E6; Thu, 17 Apr 2014 18:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.773
X-Spam-Level: 
X-Spam-Status: No, score=-114.773 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.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, 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 ZeXP7-RUyS0X; Thu, 17 Apr 2014 18:04:53 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 64AF41A0134; Thu, 17 Apr 2014 18:04:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2616; q=dns/txt; s=iport; t=1397783090; x=1398992690; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=9hS/2W9x/fYLzWcVQQBs8PLMW9/qgJipIGCwZA11CS4=; b=Gbbr6rbJEMvUI99IFDb0d2WuHYwwTQbxY+49cHnHU5ALla0fTaM4xOOd IswlHGRFWT8aX/am45/2A/xJkK39KedYO0AJulmagwTWSb9YLwlllCz2Q ILtINXXtQiczeUHqMXU26uJIccTUOsiEWNLILzTO6KHX8v/xjXLpPFQrg E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAJd5UFOtJV2Z/2dsb2JhbABZgmUhO1fDaIEjFnSCJQEBAQMBOjQLEAIBCBgKFBAyJQEBBAENDQELh2AIAQzMFBeOABACAR4xAgWDJIEUBJolkRaDMYIr
X-IronPort-AV: E=Sophos;i="4.97,882,1389744000"; d="scan'208";a="318620035"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 18 Apr 2014 01:04:49 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s3I14nIr011776 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Apr 2014 01:04:49 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0123.003; Thu, 17 Apr 2014 20:04:48 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Sam K. Aldrin" <aldrin.ietf@gmail.com>, Jeffrey Haas <jhaas@pfrc.org>
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpAA5br4AAACOm4AAAEPMAAAAv3uAAAaLVxA=
Date: Fri, 18 Apr 2014 01:04:47 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com>
In-Reply-To: <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.242.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/AhvhxelaDov5nSNJQscexcNzUQA
Cc: "ietf@ietf.org" <ietf@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 01:04:58 -0000

Hi Sam,

> > On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
> >> %sam - If this MIB allows write access, do you/WG anticipate, any
> extension to the MIB should also provide write-access as well? For exampl=
e:
> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments this
> base MIB to support MPLS. It adds more confusion than solving the issue a=
s
> base MIB supports write-access, but augmented/ MIB extension doesn't.
> >>
> >> As the BFD MIB authors were not supportive of write-access objects in
> the MIBs, why to have them in the first place?
> >
> > As noted in earlier mailing list chatter, there is some support for
> > write access in existing implementations.  Given the lack of
> > significant detail when pressed for the name of such an
> > implementation, I'm suspecting smaller vendor or internal
> > implementation.  That's still sufficient to leave write available.
> >
> > Given that one of the original contexts of asking if we could remove
> > write was whether IETF was being asked to provide such a thing for
> > MPLS-TP with related impact on your extension MIB and the answer was
> > "no", that shouldn't be the main criteria.
> No. The context of my question is not related to MPLS-TP as such, but wri=
te-
> access support in general.
> I should have added 'clarification' in my earlier email.
> >
> > My suspicion is that if we were to ship the base MIB with writeable
> > objects, we may be forced to consider similar things for the extension
> MIB(s).
> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE and
> BFD-MIB respectively,  with write-access. Had to do write-access because =
of
> the reason you've mentioned above, which is base MIB. It would be painful
> to publish/support write-access MIB's when there is no clear interest. He=
nce
> my clarification question.

This mentions three vendors wanting to implement MIB as writable.

http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html

And one more vendor voicing for writable.

http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html

I agree that defining & wording writable MIB is much more painful than all =
read-only MIB. But above thread indicates the desire by multiple vendors to=
 implement writable BFD MIB. Therefore it does seem that there are interest=
s, and going forward with write-access will benefit the community. And with=
 *ReadOnlyCompliance defined, BFD MIB can also accommodate those implementi=
ng them as just read-only.

-Nobo

>=20
> -sam
>=20
> >
> > -- Jeff


From nobody Thu Apr 17 18:24:37 2014
Return-Path: <aldrin.ietf@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 8B6CD1A018F; Thu, 17 Apr 2014 18:24:30 -0700 (PDT)
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 NdC8r-4JTAZc; Thu, 17 Apr 2014 18:24:28 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 7B96F1A0057; Thu, 17 Apr 2014 18:24:28 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id kq14so958280pab.38 for <multiple recipients>; Thu, 17 Apr 2014 18:24:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=35aHL2qacWZN28WEqFB9sF9D1eRAX7ZaqHAhqbfSSZ8=; b=LmBGZd1Ai2g4tjRlc47UHbYKa5zPK4ykWzA+m/68o1aeQEBgmxPhejTD1FxPy451b+ nuFWtJUtwVbRE959WgzC0wghGxfi4cqFSTUVD839yocc31w1S6Ejkmwadz0pxmmMBzw/ b/xrwLyS7B2M9/7JWFk9i5jN/HbC6F6Qdsf5XKFlcW3XwZC4ewHtckiRuXjpztrvYJkq LEmJyG0YxHVh4pvEFEG3gwtgey9cg74VmNoaoffPoe4QCiQS46MeiX0wxNjYtWDr9Jqg P0vCk0QQB6uI8BTDEvH9tAV1aBROO3m6yVZAI+u/5Xa6KbgGX6I1TTOsdv0kriYqYSJU YIFw==
X-Received: by 10.68.139.71 with SMTP id qw7mr19092420pbb.68.1397784264847; Thu, 17 Apr 2014 18:24:24 -0700 (PDT)
Received: from [192.168.1.7] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id pv4sm56277102pbb.55.2014.04.17.18.24.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 18:24:24 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com>
Date: Thu, 17 Apr 2014 18:24:22 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/LYBRGQ4vlLGrZy-hZ7V5gUgaXJE
Cc: "ietf@ietf.org" <ietf@ietf.org>, Jeffrey Haas <jhaas@pfrc.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 01:24:30 -0000

Hi Nobo,
[sorry for the top post]

Yes, this is an old MIB and was in existence for a long time.=20
My only concern is with the new extension MIB's. If the base MIB (this =
MIB) has write access, future extension MIB's may be forced to support =
write-access. And that is the painful part, where community at large has =
not shown interest in developing write-access MIB's at IETF, lest =
implementation.=20

I want to re-iterate again, I am not objecting or proposing an =
alternative option. Just wanted to get clarification, so that, we don't =
have to burn cycles and do the exercise again, when we have to review =
these new extension MIB's.

-sam

On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:

> Hi Sam,
>=20
>>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>>>> %sam - If this MIB allows write access, do you/WG anticipate, any
>> extension to the MIB should also provide write-access as well? For =
example:
>> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments =
this
>> base MIB to support MPLS. It adds more confusion than solving the =
issue as
>> base MIB supports write-access, but augmented/ MIB extension doesn't.
>>>>=20
>>>> As the BFD MIB authors were not supportive of write-access objects =
in
>> the MIBs, why to have them in the first place?
>>>=20
>>> As noted in earlier mailing list chatter, there is some support for
>>> write access in existing implementations.  Given the lack of
>>> significant detail when pressed for the name of such an
>>> implementation, I'm suspecting smaller vendor or internal
>>> implementation.  That's still sufficient to leave write available.
>>>=20
>>> Given that one of the original contexts of asking if we could remove
>>> write was whether IETF was being asked to provide such a thing for
>>> MPLS-TP with related impact on your extension MIB and the answer was
>>> "no", that shouldn't be the main criteria.
>> No. The context of my question is not related to MPLS-TP as such, but =
write-
>> access support in general.
>> I should have added 'clarification' in my earlier email.
>>>=20
>>> My suspicion is that if we were to ship the base MIB with writeable
>>> objects, we may be forced to consider similar things for the =
extension
>> MIB(s).
>> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE =
and
>> BFD-MIB respectively,  with write-access. Had to do write-access =
because of
>> the reason you've mentioned above, which is base MIB. It would be =
painful
>> to publish/support write-access MIB's when there is no clear =
interest. Hence
>> my clarification question.
>=20
> This mentions three vendors wanting to implement MIB as writable.
>=20
> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
>=20
> And one more vendor voicing for writable.
>=20
> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
>=20
> I agree that defining & wording writable MIB is much more painful than =
all read-only MIB. But above thread indicates the desire by multiple =
vendors to implement writable BFD MIB. Therefore it does seem that there =
are interests, and going forward with write-access will benefit the =
community. And with *ReadOnlyCompliance defined, BFD MIB can also =
accommodate those implementing them as just read-only.
>=20
> -Nobo
>=20
>>=20
>> -sam
>>=20
>>>=20
>>> -- Jeff
>=20


From nobody Thu Apr 17 18:41:54 2014
Return-Path: <nobo@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 22E931A0247; Thu, 17 Apr 2014 18:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.773
X-Spam-Level: 
X-Spam-Status: No, score=-109.773 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.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, 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 X-EJv6ivQlcP; Thu, 17 Apr 2014 18:41:45 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 50A341A0242; Thu, 17 Apr 2014 18:41:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2257; q=dns/txt; s=iport; t=1397785302; x=1398994902; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=b6TQy5UOH1kB4k7F1+x4znplvvUu1wHmVZ+W4zYEsxw=; b=M8na4kgIknpOEp3py/dhLy0NcS3l1vNngH03Atc3rd55Iv16wtgmYHz3 Ud0a/RQCmoBIDwIBRu0d4r1kYtDor0SUJRTUIN7Hq7j4TEu2JoZOlxgi0 HGup9gX6YQLHIAeoX0yalPSHJcdkXRUFsoW9DeEOh9EHWS52M9KfOZRL0 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAASCUFOtJA2M/2dsb2JhbABZgmUhgRLDaIEjFnSCJQEBAQMBOj8MBAIBCA4DBAEBAQoUCQcyFAkIAQEEDgUIh2wIAcwjF44xMQcGgx6BFAEDqzuDMYIr
X-IronPort-AV: E=Sophos;i="4.97,882,1389744000"; d="scan'208";a="36817188"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-4.cisco.com with ESMTP; 18 Apr 2014 01:41:41 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s3I1ffI5020901 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Apr 2014 01:41:41 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Thu, 17 Apr 2014 20:41:40 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpAAiJosQABf5+IAAA1d10A==
Date: Fri, 18 Apr 2014 01:41:40 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E10BDEA@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.cisco.com> <20140417221511.GC29430@pfrc>
In-Reply-To: <20140417221511.GC29430@pfrc>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.242.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/gYtC7ujdJSmJypi606S5V1JoXFc
Cc: "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "ietf@ietf.org" <ietf@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 01:41:49 -0000

Hi Jeff,

> -----Original Message-----
> From: Jeffrey Haas [mailto:jhaas@pfrc.org]
> Sent: Thursday, April 17, 2014 6:15 PM
> To: Nobo Akiya (nobo)
> Cc: Black, David; tnadeau@lucidvision.com; Zafar Ali (zali); General Area
> Review Team (gen-art@ietf.org); rtg-bfd@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>=20
> On Thu, Apr 17, 2014 at 09:18:28PM +0000, Nobo Akiya (nobo) wrote:
> > > I did not see a compliance requirement for a system that only
> > > implements BFD protocol version 0.  That absence should at least be
> > > mentioned somewhere.  For example, if this reflects a considered and
> > > deliberate decision by the WG, that should be mentioned in the
> introduction.
> >
> > Good point. If I remember correctly, BFD version 0 had a problem in the
> state machine that can cause the two ends to fall into a deadlock. It wou=
ld
> be, therefore, very bad for anybody to have BFD version 0 deployed out
> there, and asking for any MIB compliance requirement for such. Consensus
> on absence of compliance requirement for BFD version 0 was never polled
> in the WG, but I can say that there shouldn't be any desire for that.
>=20
> With respect to v0 vs. v1 from a MIB perspective, the only user-visible d=
etail
> was the additional state in the state machine.  That means that the MIB i=
n its
> current form should be able to accommodate bfd v0.
>=20
> This does suggest, however, that the TC mib could use a comment in the
> DESCRIPTION toward the point that failing(5) is only valid for BFD v0.

Agree, and it's already there :)

[snip]
    IANAbfdSessStateTC ::=3D TEXTUAL-CONVENTION
    STATUS         current
    DESCRIPTION
        "BFD session state. State failing(5) is only applicable if
         corresponding session is running in BFD version 0."
[snip]

-Nobo

>=20
> A conformance clause indicating that those so foolish as to deploy BFD v0
> would better be served by the determinism of a five-year-old child flippi=
ng
> a coin is probably out of scope for the draft.  But if someone has suffic=
iently
> proscriptive text to add to say "don't do bfd v0" that is acceptable to t=
he
> reviewers, I'm fine with that.
>=20
> -- Jeff


From nobody Thu Apr 17 19:17:42 2014
Return-Path: <nobo@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 E5FB91A00B4; Thu, 17 Apr 2014 19:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.773
X-Spam-Level: 
X-Spam-Status: No, score=-114.773 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.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, 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 g-aiWU41Ab9d; Thu, 17 Apr 2014 19:17:34 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id B08EA1A001B; Thu, 17 Apr 2014 19:17:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4382; q=dns/txt; s=iport; t=1397787450; x=1398997050; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=b6+yzgHZCagbonRihcCu34WjcP/VyaXKFjyYVKTH4qk=; b=PlJgFkx2jkRNiSNuYtVvORSxqOLgie8yzRJ/A2jcMGEMml/OGPbedR8R lazdMe1RuH0TwhfTX9aJrXdEhOg+JeuLvWaSGdb0ijbpMC54A4D2rKJby YfaOTKrqStDqhyjD7MjPQ4WA6/EfSM3aS6XuTatJr/CbjsjBjrwBCFkkC Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAK6JUFOtJV2b/2dsb2JhbABZgmUhO1fDaIEjFnSCJQEBAQQ6NAsMBAIBCBEEAQEBChQJByERFAkIAgQOBQgBC4dUAxEBDMUiDYZrF4xJgTcQAgEeMQIFBoMegRQElwCDJYtGhVCDMYIr
X-IronPort-AV: E=Sophos;i="4.97,882,1389744000"; d="scan'208";a="318435662"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-1.cisco.com with ESMTP; 18 Apr 2014 02:17:29 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3I2HT3j007371 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Apr 2014 02:17:29 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Thu, 17 Apr 2014 21:17:29 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpAA5br4AAACOm4AAAEPMAAAAv3uAAAaLVxD///l/AIAATS4g
Date: Fri, 18 Apr 2014 02:17:28 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com> <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com>
In-Reply-To: <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.242.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/VMMikZ7zLqqc9emN27pxXOnhYlw
Cc: "ietf@ietf.org" <ietf@ietf.org>, Jeffrey Haas <jhaas@pfrc.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 02:17:38 -0000

Hi Sam,

> -----Original Message-----
> From: Sam K. Aldrin [mailto:aldrin.ietf@gmail.com]
> Sent: Thursday, April 17, 2014 9:24 PM
> To: Nobo Akiya (nobo)
> Cc: Jeffrey Haas; ietf@ietf.org; 'Black, David'; adrian@olddog.co.uk; rtg=
-
> bfd@ietf.org; Zafar Ali (zali); 'General Area Review Team'
> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>=20
> Hi Nobo,
> [sorry for the top post]
>=20
> Yes, this is an old MIB and was in existence for a long time.
> My only concern is with the new extension MIB's. If the base MIB (this MI=
B)
> has write access, future extension MIB's may be forced to support write-
> access. And that is the painful part, where community at large has not
> shown interest in developing write-access MIB's at IETF, lest
> implementation.
>=20
> I want to re-iterate again, I am not objecting or proposing an alternativ=
e
> option. Just wanted to get clarification, so that, we don't have to burn =
cycles
> and do the exercise again, when we have to review these new extension
> MIB's.

That's a good point, it would be good to have this clarified for future wor=
k.

IMO:

For new charters, IESG encourages NETCONF/YANG. This means S-BFD (if gets i=
ncluded in the charter) should look into NETCONF/YANG (i.e. not extension t=
o the BFD base MIB).

For currently chartered BFD tasks, the BFD WG should continue with writable=
 MIB. Large part of that is the BFD base & MPLS MIBs which [painful] writab=
le effort is mostly done already.

-Nobo

>=20
> -sam
>=20
> On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:
>=20
> > Hi Sam,
> >
> >>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
> >>>> %sam - If this MIB allows write access, do you/WG anticipate, any
> >> extension to the MIB should also provide write-access as well? For
> example:
> >> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments
> >> this base MIB to support MPLS. It adds more confusion than solving
> >> the issue as base MIB supports write-access, but augmented/ MIB
> extension doesn't.
> >>>>
> >>>> As the BFD MIB authors were not supportive of write-access objects
> >>>> in
> >> the MIBs, why to have them in the first place?
> >>>
> >>> As noted in earlier mailing list chatter, there is some support for
> >>> write access in existing implementations.  Given the lack of
> >>> significant detail when pressed for the name of such an
> >>> implementation, I'm suspecting smaller vendor or internal
> >>> implementation.  That's still sufficient to leave write available.
> >>>
> >>> Given that one of the original contexts of asking if we could remove
> >>> write was whether IETF was being asked to provide such a thing for
> >>> MPLS-TP with related impact on your extension MIB and the answer was
> >>> "no", that shouldn't be the main criteria.
> >> No. The context of my question is not related to MPLS-TP as such, but
> >> write- access support in general.
> >> I should have added 'clarification' in my earlier email.
> >>>
> >>> My suspicion is that if we were to ship the base MIB with writeable
> >>> objects, we may be forced to consider similar things for the
> >>> extension
> >> MIB(s).
> >> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE
> >> and BFD-MIB respectively,  with write-access. Had to do write-access
> >> because of the reason you've mentioned above, which is base MIB. It
> >> would be painful to publish/support write-access MIB's when there is
> >> no clear interest. Hence my clarification question.
> >
> > This mentions three vendors wanting to implement MIB as writable.
> >
> > http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
> >
> > And one more vendor voicing for writable.
> >
> > http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
> >
> > I agree that defining & wording writable MIB is much more painful than =
all
> read-only MIB. But above thread indicates the desire by multiple vendors =
to
> implement writable BFD MIB. Therefore it does seem that there are
> interests, and going forward with write-access will benefit the community=
.
> And with *ReadOnlyCompliance defined, BFD MIB can also accommodate
> those implementing them as just read-only.
> >
> > -Nobo
> >
> >>
> >> -sam
> >>
> >>>
> >>> -- Jeff
> >


From nobody Thu Apr 17 19:19:10 2014
Return-Path: <aldrin.ietf@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 AC17B1A00B4; Thu, 17 Apr 2014 19:19:08 -0700 (PDT)
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 sZ4x4Yn91-kt; Thu, 17 Apr 2014 19:19:06 -0700 (PDT)
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 A93BC1A001B; Thu, 17 Apr 2014 19:19:06 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id md12so994256pbc.21 for <multiple recipients>; Thu, 17 Apr 2014 19:19:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kIw2nM3r6y6FniSxk3XSE9wIBRMAQ+U6ypzHYqbDpU0=; b=rg8tuoOHlgTXMMoFIjrTCDqvEPOIcJEqCgsf8FqmnqKlkR66kiZyxGuZ7/8zc8qUMt 6w3rp2bUZJG2FyGUSIGGK3/xjHwoxiWuOeYsr2u6B+0BY9pgfQFAQG0R3jC6ms5Mknxp u5S1tYAqAV4A9203h/Ui44kZJItnf4yb6DOFyq2hSXU+YOq/zTxg574nh4B/f9macORV Jd9ypy1GSj9Bnn+k3+bILaJB/7Va7hRXhCwfpjGd7gam8aYfx2N+kSwrB74d7Ea13m8o NG51RED13+PFoiiNGTZOHGAnYVtnOkL8xPEjku97v9g938IQsOJjZcLC/RRTd5H+XcMA aYmQ==
X-Received: by 10.66.197.135 with SMTP id iu7mr18967003pac.149.1397787543040;  Thu, 17 Apr 2014 19:19:03 -0700 (PDT)
Received: from [192.168.1.5] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id xo9sm133063879pab.18.2014.04.17.19.19.01 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 19:19:02 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Sam Aldrin <aldrin.ietf@gmail.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com>
Date: Thu, 17 Apr 2014 19:19:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D48D4ED0-BA1B-49E6-9E6F-4052C59B83FE@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com> <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/tSEKNY1tKUfcnizRqaxIwvbCfkI
Cc: "ietf@ietf.org" <ietf@ietf.org>, Jeffrey Haas <jhaas@pfrc.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 02:19:08 -0000

Thanks, Nobo. Much appreciated.

-sam
On Apr 17, 2014, at 7:17 PM, Nobo Akiya (nobo) <nobo@cisco.com> wrote:

> Hi Sam,
>=20
>> -----Original Message-----
>> From: Sam K. Aldrin [mailto:aldrin.ietf@gmail.com]
>> Sent: Thursday, April 17, 2014 9:24 PM
>> To: Nobo Akiya (nobo)
>> Cc: Jeffrey Haas; ietf@ietf.org; 'Black, David'; adrian@olddog.co.uk; =
rtg-
>> bfd@ietf.org; Zafar Ali (zali); 'General Area Review Team'
>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>>=20
>> Hi Nobo,
>> [sorry for the top post]
>>=20
>> Yes, this is an old MIB and was in existence for a long time.
>> My only concern is with the new extension MIB's. If the base MIB =
(this MIB)
>> has write access, future extension MIB's may be forced to support =
write-
>> access. And that is the painful part, where community at large has =
not
>> shown interest in developing write-access MIB's at IETF, lest
>> implementation.
>>=20
>> I want to re-iterate again, I am not objecting or proposing an =
alternative
>> option. Just wanted to get clarification, so that, we don't have to =
burn cycles
>> and do the exercise again, when we have to review these new extension
>> MIB's.
>=20
> That's a good point, it would be good to have this clarified for =
future work.
>=20
> IMO:
>=20
> For new charters, IESG encourages NETCONF/YANG. This means S-BFD (if =
gets included in the charter) should look into NETCONF/YANG (i.e. not =
extension to the BFD base MIB).
>=20
> For currently chartered BFD tasks, the BFD WG should continue with =
writable MIB. Large part of that is the BFD base & MPLS MIBs which =
[painful] writable effort is mostly done already.
>=20
> -Nobo
>=20
>>=20
>> -sam
>>=20
>> On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:
>>=20
>>> Hi Sam,
>>>=20
>>>>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>>>>>> %sam - If this MIB allows write access, do you/WG anticipate, any
>>>> extension to the MIB should also provide write-access as well? For
>> example:
>>>> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments
>>>> this base MIB to support MPLS. It adds more confusion than solving
>>>> the issue as base MIB supports write-access, but augmented/ MIB
>> extension doesn't.
>>>>>>=20
>>>>>> As the BFD MIB authors were not supportive of write-access =
objects
>>>>>> in
>>>> the MIBs, why to have them in the first place?
>>>>>=20
>>>>> As noted in earlier mailing list chatter, there is some support =
for
>>>>> write access in existing implementations.  Given the lack of
>>>>> significant detail when pressed for the name of such an
>>>>> implementation, I'm suspecting smaller vendor or internal
>>>>> implementation.  That's still sufficient to leave write available.
>>>>>=20
>>>>> Given that one of the original contexts of asking if we could =
remove
>>>>> write was whether IETF was being asked to provide such a thing for
>>>>> MPLS-TP with related impact on your extension MIB and the answer =
was
>>>>> "no", that shouldn't be the main criteria.
>>>> No. The context of my question is not related to MPLS-TP as such, =
but
>>>> write- access support in general.
>>>> I should have added 'clarification' in my earlier email.
>>>>>=20
>>>>> My suspicion is that if we were to ship the base MIB with =
writeable
>>>>> objects, we may be forced to consider similar things for the
>>>>> extension
>>>> MIB(s).
>>>> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, =
MPLS-TE
>>>> and BFD-MIB respectively,  with write-access. Had to do =
write-access
>>>> because of the reason you've mentioned above, which is base MIB. It
>>>> would be painful to publish/support write-access MIB's when there =
is
>>>> no clear interest. Hence my clarification question.
>>>=20
>>> This mentions three vendors wanting to implement MIB as writable.
>>>=20
>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
>>>=20
>>> And one more vendor voicing for writable.
>>>=20
>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
>>>=20
>>> I agree that defining & wording writable MIB is much more painful =
than all
>> read-only MIB. But above thread indicates the desire by multiple =
vendors to
>> implement writable BFD MIB. Therefore it does seem that there are
>> interests, and going forward with write-access will benefit the =
community.
>> And with *ReadOnlyCompliance defined, BFD MIB can also accommodate
>> those implementing them as just read-only.
>>>=20
>>> -Nobo
>>>=20
>>>>=20
>>>> -sam
>>>>=20
>>>>>=20
>>>>> -- Jeff
>>>=20
>=20


From nobody Thu Apr 17 19:48:14 2014
Return-Path: <randy_presuhn@mindspring.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 7A7A31A0194; Thu, 17 Apr 2014 19:48:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 SXJNWw-pUZP6; Thu, 17 Apr 2014 19:48:09 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id ABBAE1A001E; Thu, 17 Apr 2014 19:48:06 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=jk6KUMFGWhs0UB7t4U3v6bBAIYZ23zc1Fsy516gl3MSoVGCn9U/AHLlwE5XG0hMM; h=Message-ID:Date:From:Reply-To:To:Subject:Cc:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.39] (helo=elwamui-little.atl.sa.earthlink.net) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1WayqJ-0007yr-En; Thu, 17 Apr 2014 22:47:55 -0400
Received: from 99.23.160.116 by webmail.earthlink.net with HTTP; Thu, 17 Apr 2014 22:47:55 -0400
Message-ID: <25276146.1397789275400.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
Date: Thu, 17 Apr 2014 19:47:55 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: "Sam K. Aldrin" <aldrin.ietf@gmail.com>,  "Nobo Akiya (nobo)" <nobo@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbc8c1f0f3881847dfdf761c2c2f8dbc85f350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.39
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Bh2WGQ6pu5VZ6gxmJonU61K_6Nw
Cc: "ietf@ietf.org" <ietf@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.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, 18 Apr 2014 02:48:10 -0000

Hi -

>From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
>Sent: Apr 17, 2014 6:24 PM
...
>Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
...
>My only concern is with the new extension MIB's.
>If the base MIB (this MIB) has write access,
>future extension MIB's may be forced to support
>write-access.

And how, exactly, does the fact that a base MIB module
permits write access force extension MIB modules to
require (or even permit) write access?

It's perfectly reasonable SMI to define an AUGMENTS
table consisting entirely of read-only objects.

Randy


From nobody Thu Apr 17 20:53:33 2014
Return-Path: <aldrin.ietf@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 B60861A0147; Thu, 17 Apr 2014 20:53:31 -0700 (PDT)
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 Rp9kF1SqukfW; Thu, 17 Apr 2014 20:53:30 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 339291A00C0; Thu, 17 Apr 2014 20:53:30 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id rd3so1066974pab.39 for <multiple recipients>; Thu, 17 Apr 2014 20:53:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IPL7jibdZfBm/MKJUWytg45glowdrHwo43dKe8MCkCw=; b=KdIt143+7azLk0RP+nlVOLdWO0Pm2VVRrmwI2EFJuF551H5RcHLnGJybuhjv5wpiHJ tR7/xzCNU11kCd+KPrCZtyxevuYRuRJ4OGVp2qHSijjeinouqXuzqvFcPCz48h8Yecwm MHBHe6BsbDCaMb3oWBm7KAV6OtHIYz2YBbKc+ucEChFBZ1KWEsFv0EbqwO+zu9f2nb6R MSeP33Xfidoj+6Ij9aLUztdYlnx6I+LVr/5KOVj0t1AHmqsChFn+4iZ94xEBPtkYs6j1 eNCa3qkzQkpeWnmkA7JUkU3Jd0rJKRe5Ux9Pr+mBZ4W2opLGvRpwfidx4bDppnBEIkNA GJ0g==
X-Received: by 10.68.178.66 with SMTP id cw2mr19692869pbc.89.1397793206554; Thu, 17 Apr 2014 20:53:26 -0700 (PDT)
Received: from [192.168.1.7] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id ha2sm56880842pbb.8.2014.04.17.20.53.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 20:53:25 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
In-Reply-To: <25276146.1397789275400.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
Date: Thu, 17 Apr 2014 20:53:22 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B03C974-91FE-48CC-AF82-A82517E106C0@gmail.com>
References: <25276146.1397789275400.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
To: Randy Presuhn <randy_presuhn@mindspring.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/qTaVr-wPtXTE5P2vzhDK-gd_Qk0
Cc: "ietf@ietf.org" <ietf@ietf.org>, "Nobo Akiya \(nobo\)" <nobo@cisco.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 03:53:31 -0000

Hi Randy,

Inline for my comments.
On Apr 17, 2014, at 7:47 PM, Randy Presuhn wrote:

> Hi -
>=20
>> From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
>> Sent: Apr 17, 2014 6:24 PM
> ...
>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
> ...
>> My only concern is with the new extension MIB's.
>> If the base MIB (this MIB) has write access,
>> future extension MIB's may be forced to support
>> write-access.
>=20
> And how, exactly, does the fact that a base MIB module
> permits write access force extension MIB modules to
> require (or even permit) write access?
>=20
> It's perfectly reasonable SMI to define an AUGMENTS
> table consisting entirely of read-only objects.

True, you could add only read-only objects.=20
But the point is, not with syntax or what could be added or augmented.
In order to support new functionality, we are extending/augmenting =
existing base MIB and in addition some write-access objects as well. If =
we make those new ones read-only objects, then only some objects or =
tables could be used with write-access and these new objects (read-only) =
have to be configured differently. In other words, full functionality =
cannot be provided. This got nothing to do with SMI.

The point we are extending or re-using the base MIB is not to re-define =
new objects altogether and also to re-use the applications. Atleast that =
is what we have done in this case.

Hope this clarifies.

cheers
-sam
>=20
> Randy


From nobody Thu Apr 17 21:38:03 2014
Return-Path: <randy_presuhn@mindspring.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 B5D4D1A0101; Thu, 17 Apr 2014 21:37:58 -0700 (PDT)
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, 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 ZEgl1aKCfVJI; Thu, 17 Apr 2014 21:37:57 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 29C2F1A0088; Thu, 17 Apr 2014 21:37:56 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=TgJQePhp8ZEIoouz1h65UWPyEZqrEqCSR+hDr1FY+UMXONUTjvyPVsyCjSjNwJHk; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.23.160.116] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Wb0Yh-0004Eg-GT; Fri, 18 Apr 2014 00:37:51 -0400
Message-ID: <007101cf5ab8$77cf7280$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
References: <25276146.1397789275400.JavaMail.root@elwamui-little.atl.sa.earthlink.net> <4B03C974-91FE-48CC-AF82-A82517E106C0@gmail.com>
Date: Thu, 17 Apr 2014 21:43:46 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbcc293d221268b88ce71ccdfb8fd2a570a350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.160.116
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/74pzJ5KElu437iHIzSImTGlEJ6Y
Cc: ietf@ietf.org, "Nobo Akiya \(nobo\)" <nobo@cisco.com>, adrian@olddog.co.uk, rtg-bfd@ietf.org, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 04:37:58 -0000

Hi -

> From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
...
> Sent: Thursday, April 17, 2014 9:53 PM
> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
...
> In order to support new functionality, we are extending/augmenting existing base
> MIB and in addition some write-access objects as well. If we make those new
> ones read-only objects, then only some objects or tables could be used with
> write-access and these new objects (read-only) have to be configured differently.
> In other words, full functionality cannot be provided. This got nothing to do with SMI.

Then what's the problem?  If the WG has consensus to add functionality, and
that functionality logically requires a read-write MIB module of extension,
the IESG policy already allows for such cases.

Randy


From nobody Thu Apr 17 21:50:53 2014
Return-Path: <aldrin.ietf@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 6B93B1A0140; Thu, 17 Apr 2014 21:50:42 -0700 (PDT)
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 3cn9wfGe_k4M; Thu, 17 Apr 2014 21:50:40 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id EBF7C1A0130; Thu, 17 Apr 2014 21:50:39 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id kl14so1103677pab.32 for <multiple recipients>; Thu, 17 Apr 2014 21:50:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=l2MfswrE2Co/PzLnz2IWz81pjYeDLiPL72wg2NcwRfo=; b=szJHJG1zo6gUy7R/UnnmbDbuYZUvlCxfrws3Rzdk3dPWqjAevjtUQ7lB1RXheJp6As C8iJgGPxX1IJuK4nXB+n1G6iAjJOFG8p1XjIVBHdaOFdfvnETF7jCkpEIFF/VoVFyS73 NJ12GYVZpDrNFMdDLgc3tQKwh3G/J7ua3XlL0s2M0eUAQY5lMfDfr3AiwINj/YBE2uw/ NQB6kFS6Zz/eAksoe4Q3DzfBjAqlfd6Gp1ECFNsGbik+sZMe6onOgalpXLqJ2ZuxftD3 GA+vSJE/CvIBaGjn7sJXc8gjsFpnoHKJdfa1L1TzK4DF8nGsnbqI/dJpjJhBgAxO82wj uXXw==
X-Received: by 10.66.150.169 with SMTP id uj9mr19900037pab.148.1397796635882;  Thu, 17 Apr 2014 21:50:35 -0700 (PDT)
Received: from [192.168.1.5] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id vd8sm135850111pac.12.2014.04.17.21.50.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 21:50:35 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Content-Type: text/plain; charset=iso-8859-1
From: Sam Aldrin <aldrin.ietf@gmail.com>
X-Priority: 3
In-Reply-To: <007101cf5ab8$77cf7280$6b01a8c0@oemcomputer>
Date: Thu, 17 Apr 2014 21:50:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A35F863-6CBB-447B-9232-B353141E4D9A@gmail.com>
References: <25276146.1397789275400.JavaMail.root@elwamui-little.atl.sa.earthlink.net> <4B03C974-91FE-48CC-AF82-A82517E106C0@gmail.com> <007101cf5ab8$77cf7280$6b01a8c0@oemcomputer>
To: Randy Presuhn <randy_presuhn@mindspring.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/aKuHZ3-lNVl0qkDW_eA5INcQvdM
Cc: ietf@ietf.org, "Nobo Akiya \(nobo\)" <nobo@cisco.com>, adrian@olddog.co.uk, rtg-bfd@ietf.org, "Zafar Ali \(zali\)" <zali@cisco.com>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 04:50:42 -0000

Hi Randy,

On Apr 17, 2014, at 8:43 PM, Randy Presuhn =
<randy_presuhn@mindspring.com> wrote:

> Hi -
>=20
>> From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
> ...
>> Sent: Thursday, April 17, 2014 9:53 PM
>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
> ...
>> In order to support new functionality, we are extending/augmenting =
existing base
>> MIB and in addition some write-access objects as well. If we make =
those new
>> ones read-only objects, then only some objects or tables could be =
used with
>> write-access and these new objects (read-only) have to be configured =
differently.
>> In other words, full functionality cannot be provided. This got =
nothing to do with SMI.
>=20
> Then what's the problem?  If the WG has consensus to add =
functionality, and
> that functionality logically requires a read-write MIB module of =
extension,
> the IESG policy already allows for such cases.

Yes, that is what I wanted to clarify, when I sent my email, to find if =
there is WG consensus to go with write-access objects, as this base MIB =
will have implication on the other MIB in the pipeline?

We had quite a big thread on MPLS list on this very subject and wanted =
to avoid the repeat.
http://www.ietf.org/mail-archive/web/mpls/current/msg11598.html

cheers
-sam
>=20
> Randy
>=20


From nobody Fri Apr 18 02:38:26 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 A08971A02D5; Fri, 18 Apr 2014 02:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level: 
X-Spam-Status: No, score=-9.773 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.272, 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 1qmc2Iv3_E6j; Fri, 18 Apr 2014 02:38:16 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 1F0D61A0095; Fri, 18 Apr 2014 02:38:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1625; q=dns/txt; s=iport; t=1397813892; x=1399023492; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ykFJxg01yjpmcg96OyitluycaXNWhMs2sfg+HnqdycU=; b=ZgtY1TgtgcIVl+CuO9JdKix2RVaE/5ubTiD+pBfF9vu0ydyX0Pgf2o5G dWMRCp6z4awe6W+NSer+LiWPGYzQUfRrtaD0I09CfBbQCworLNcwqOlL/ W3fSzUnqR5OHb0dzgjStu3dSQhGFIrS7o7ssx7Lnr0vS2iq9b6R8gmuT2 E=;
X-IronPort-AV: E=Sophos;i="4.97,883,1389744000"; d="scan'208";a="18997933"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 18 Apr 2014 09:38:11 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3I9cB6J004547; Fri, 18 Apr 2014 09:38:11 GMT
Message-ID: <5350F283.1070907@cisco.com>
Date: Fri, 18 Apr 2014 11:38:11 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, "'Black, David'" <david.black@emc.com>, tnadeau@lucidvision.com, zali@cisco.com, nobo@cisco.com, "'General Area Review Team'" <gen-art@ietf.org>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
In-Reply-To: <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/IY9W_igg48UqmqaSktGBVUKRWkU
Cc: rtg-bfd@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 09:38:20 -0000

Hi Adrian,
> Hi David,
>
> Thanks for the review.
>
> To pick out one of your points:
>
>> This MIB contains many writable objects, so the authors should
>> take note of the IESG statement on writable MIB modules:
>>
>> 	http://www.ietf.org/iesg/statement/writable-mib-module.html
>>
>> I did not see this mentioned in the shepherd writeup.  If the OPS Area
>> has not been consulted, I strongly suggest doing so during IETF Last
>> Call, e.g., starting with Benoit Claise (AD).
> The OPS Directorate and the MIB Doctors will have been alerted to this document
> by the last call and we can expect their comments.
>
> But this question was discussed between the AD and the authors, and the AD was
> unlikely to agree to sponsor the document if he felt it went against the IESG
> statement. Our discussion resulted in some reduction of writeable objects.
>
> I think there are several points to consider:
> 1. This document had already been completed and publication requested (i.e.
> shepherd write-up written) at the time of the IESG statement. It would be
> unreasonable to make the statement retrospective.
> 2. There are already various implementations in equipment (not just management
> stations) of proprietary modules approximating to this document and these
> support write-access.
> 3. This is a low-level component protocol of the sort that is used on dumber
> devices and that is an area where write-access is more common.
Thanks for the explanation. That makes sense to me.
This would be a useful addition to the writeup.

Regards, Benoit
>
> Cheers,
> Adrian
>
>
> .
>


From nobody Fri Apr 18 02:41:18 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 152DE1A02ED; Fri, 18 Apr 2014 02:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level: 
X-Spam-Status: No, score=-9.773 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.272, 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 l0KikSbirRsL; Fri, 18 Apr 2014 02:41:15 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB151A02E6; Fri, 18 Apr 2014 02:41:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4493; q=dns/txt; s=iport; t=1397814071; x=1399023671; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=bjzfSWuLPBsKnl2k8kCmV3tXHQglzz7edw/goZL3YpI=; b=i3LqvAO0Jye998umRel+XO8l4895jWEp6XTwgfqR3ut9MibP8viqED2I 4SlRWtpPuJ6tIujeNW6Yq/DThuKTNwQ1SAiVevdq6nU65aSR2blC4e80Q xHpG/MrzwkX/1wR10KS/KBUxoBD+2zxQ9T/qgk4V5m3PRjYao2aiBdmke c=;
X-IronPort-AV: E=Sophos;i="4.97,883,1389744000"; d="scan'208";a="18999086"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 18 Apr 2014 09:41:10 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3I9f9m5007414; Fri, 18 Apr 2014 09:41:09 GMT
Message-ID: <5350F335.8020309@cisco.com>
Date: Fri, 18 Apr 2014 11:41:09 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Nobo Akiya (nobo)" <nobo@cisco.com>, "Sam K. Aldrin" <aldrin.ietf@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com> <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Ni7JZ-S63tNtiqGB3y_42633BpM
Cc: "ietf@ietf.org" <ietf@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 09:41:17 -0000

On 18/04/2014 04:17, Nobo Akiya (nobo) wrote:
> Hi Sam,
>
>> -----Original Message-----
>> From: Sam K. Aldrin [mailto:aldrin.ietf@gmail.com]
>> Sent: Thursday, April 17, 2014 9:24 PM
>> To: Nobo Akiya (nobo)
>> Cc: Jeffrey Haas; ietf@ietf.org; 'Black, David'; adrian@olddog.co.uk; rtg-
>> bfd@ietf.org; Zafar Ali (zali); 'General Area Review Team'
>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>>
>> Hi Nobo,
>> [sorry for the top post]
>>
>> Yes, this is an old MIB and was in existence for a long time.
>> My only concern is with the new extension MIB's. If the base MIB (this MIB)
>> has write access, future extension MIB's may be forced to support write-
>> access. And that is the painful part, where community at large has not
>> shown interest in developing write-access MIB's at IETF, lest
>> implementation.
>>
>> I want to re-iterate again, I am not objecting or proposing an alternative
>> option. Just wanted to get clarification, so that, we don't have to burn cycles
>> and do the exercise again, when we have to review these new extension
>> MIB's.
> That's a good point, it would be good to have this clarified for future work.
>
> IMO:
>
> For new charters, IESG encourages NETCONF/YANG. This means S-BFD (if gets included in the charter) should look into NETCONF/YANG (i.e. not extension to the BFD base MIB).
>
> For currently chartered BFD tasks, the BFD WG should continue with writable MIB. Large part of that is the BFD base & MPLS MIBs which [painful] writable effort is mostly done already.
This is in essence what 
https://www.ietf.org/iesg/statement/writable-mib-module.html says.

Regards, Benoit.
>
> -Nobo
>
>> -sam
>>
>> On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:
>>
>>> Hi Sam,
>>>
>>>>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>>>>>> %sam - If this MIB allows write access, do you/WG anticipate, any
>>>> extension to the MIB should also provide write-access as well? For
>> example:
>>>> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments
>>>> this base MIB to support MPLS. It adds more confusion than solving
>>>> the issue as base MIB supports write-access, but augmented/ MIB
>> extension doesn't.
>>>>>> As the BFD MIB authors were not supportive of write-access objects
>>>>>> in
>>>> the MIBs, why to have them in the first place?
>>>>> As noted in earlier mailing list chatter, there is some support for
>>>>> write access in existing implementations.  Given the lack of
>>>>> significant detail when pressed for the name of such an
>>>>> implementation, I'm suspecting smaller vendor or internal
>>>>> implementation.  That's still sufficient to leave write available.
>>>>>
>>>>> Given that one of the original contexts of asking if we could remove
>>>>> write was whether IETF was being asked to provide such a thing for
>>>>> MPLS-TP with related impact on your extension MIB and the answer was
>>>>> "no", that shouldn't be the main criteria.
>>>> No. The context of my question is not related to MPLS-TP as such, but
>>>> write- access support in general.
>>>> I should have added 'clarification' in my earlier email.
>>>>> My suspicion is that if we were to ship the base MIB with writeable
>>>>> objects, we may be forced to consider similar things for the
>>>>> extension
>>>> MIB(s).
>>>> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE
>>>> and BFD-MIB respectively,  with write-access. Had to do write-access
>>>> because of the reason you've mentioned above, which is base MIB. It
>>>> would be painful to publish/support write-access MIB's when there is
>>>> no clear interest. Hence my clarification question.
>>> This mentions three vendors wanting to implement MIB as writable.
>>>
>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
>>>
>>> And one more vendor voicing for writable.
>>>
>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
>>>
>>> I agree that defining & wording writable MIB is much more painful than all
>> read-only MIB. But above thread indicates the desire by multiple vendors to
>> implement writable BFD MIB. Therefore it does seem that there are
>> interests, and going forward with write-access will benefit the community.
>> And with *ReadOnlyCompliance defined, BFD MIB can also accommodate
>> those implementing them as just read-only.
>>> -Nobo
>>>
>>>> -sam
>>>>
>>>>> -- Jeff
> .
>


From nobody Fri Apr 18 05:07:01 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 C05931A01F6; Fri, 18 Apr 2014 05:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level: 
X-Spam-Status: No, score=-9.773 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.272, 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 bZXkzubpP6WY; Fri, 18 Apr 2014 05:06:50 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6B91A0208; Fri, 18 Apr 2014 05:06:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5179; q=dns/txt; s=iport; t=1397822806; x=1399032406; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=WMcgKt5iEVVOziy2T0Qu/vnY+NvLYvE0yk6xHct/scg=; b=DvcK+m+JKy2TbUZducgPC4glzQRmHCKUUID1pFs0yI7Vth6DUiRgvQaV D1YhdSRFveJARXZP7R5nd/sRxIOE3R9Dlxydz2qsozi7sGMPdBwyvVFZC grN2V16vzmQHTTDgjCDLRxWj9/YKIQCZ9qd31wU+eF1S7/GLtnjM3fTCv 0=;
X-IronPort-AV: E=Sophos;i="4.97,884,1389744000"; d="scan'208";a="14946174"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 18 Apr 2014 12:06:45 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3IC6i88025687; Fri, 18 Apr 2014 12:06:44 GMT
Message-ID: <53511554.2000402@cisco.com>
Date: Fri, 18 Apr 2014 14:06:44 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Thomas Nadeau <tnadeau@lucidvision.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com> <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com> <5350F335.8020309@cisco.com> <33B44E73-320B-4FC9-8438-E471F605F318@lucidvision.com>
In-Reply-To: <33B44E73-320B-4FC9-8438-E471F605F318@lucidvision.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/6KG5acq-M_oGJxKDRcCcjeBxg_w
Cc: "ietf@ietf.org" <ietf@ietf.org>, "Sam K. Aldrin" <aldrin.ietf@gmail.com>, "Nobo Akiya \(nobo\)" <nobo@cisco.com>, Farrel Adrian <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 12:06:55 -0000

On 18/04/2014 13:51, Thomas Nadeau wrote:
> On Apr 18, 2014:5:41 AM, at 5:41 AM, Benoit Claise <bclaise@cisco.com> wrote:
>
>> On 18/04/2014 04:17, Nobo Akiya (nobo) wrote:
>>> Hi Sam,
>>>
>>>> -----Original Message-----
>>>> From: Sam K. Aldrin [mailto:aldrin.ietf@gmail.com]
>>>> Sent: Thursday, April 17, 2014 9:24 PM
>>>> To: Nobo Akiya (nobo)
>>>> Cc: Jeffrey Haas; ietf@ietf.org; 'Black, David'; adrian@olddog.co.uk; rtg-
>>>> bfd@ietf.org; Zafar Ali (zali); 'General Area Review Team'
>>>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>>>>
>>>> Hi Nobo,
>>>> [sorry for the top post]
>>>>
>>>> Yes, this is an old MIB and was in existence for a long time.
>>>> My only concern is with the new extension MIB's. If the base MIB (this MIB)
>>>> has write access, future extension MIB's may be forced to support write-
>>>> access. And that is the painful part, where community at large has not
>>>> shown interest in developing write-access MIB's at IETF, lest
>>>> implementation.
>>>>
>>>> I want to re-iterate again, I am not objecting or proposing an alternative
>>>> option. Just wanted to get clarification, so that, we don't have to burn cycles
>>>> and do the exercise again, when we have to review these new extension
>>>> MIB's.
>>> That's a good point, it would be good to have this clarified for future work.
>>>
>>> IMO:
>>>
>>> For new charters, IESG encourages NETCONF/YANG. This means S-BFD (if gets included in the charter) should look into NETCONF/YANG (i.e. not extension to the BFD base MIB).
>>>
>>> For currently chartered BFD tasks, the BFD WG should continue with writable MIB. Large part of that is the BFD base & MPLS MIBs which [painful] writable effort is mostly done already.
>> This is in essence what https://www.ietf.org/iesg/statement/writable-mib-module.html says.
>>
>> Regards, Benoit.
> 	Yes, this is why we left the writable stuff in - and why I recently spent about 4 hours doing Adrian's edits around support of such things.  Lets please put the discussion around read-write to bed for these two modules as they clearly were well under way and complete by the time the statement came out.
No disagreement.

Regards, B.
>
> 	--Tom
>
>
>
>>> -Nobo
>>>
>>>> -sam
>>>>
>>>> On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:
>>>>
>>>>> Hi Sam,
>>>>>
>>>>>>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>>>>>>>> %sam - If this MIB allows write access, do you/WG anticipate, any
>>>>>> extension to the MIB should also provide write-access as well? For
>>>> example:
>>>>>> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments
>>>>>> this base MIB to support MPLS. It adds more confusion than solving
>>>>>> the issue as base MIB supports write-access, but augmented/ MIB
>>>> extension doesn't.
>>>>>>>> As the BFD MIB authors were not supportive of write-access objects
>>>>>>>> in
>>>>>> the MIBs, why to have them in the first place?
>>>>>>> As noted in earlier mailing list chatter, there is some support for
>>>>>>> write access in existing implementations.  Given the lack of
>>>>>>> significant detail when pressed for the name of such an
>>>>>>> implementation, I'm suspecting smaller vendor or internal
>>>>>>> implementation.  That's still sufficient to leave write available.
>>>>>>>
>>>>>>> Given that one of the original contexts of asking if we could remove
>>>>>>> write was whether IETF was being asked to provide such a thing for
>>>>>>> MPLS-TP with related impact on your extension MIB and the answer was
>>>>>>> "no", that shouldn't be the main criteria.
>>>>>> No. The context of my question is not related to MPLS-TP as such, but
>>>>>> write- access support in general.
>>>>>> I should have added 'clarification' in my earlier email.
>>>>>>> My suspicion is that if we were to ship the base MIB with writeable
>>>>>>> objects, we may be forced to consider similar things for the
>>>>>>> extension
>>>>>> MIB(s).
>>>>>> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE
>>>>>> and BFD-MIB respectively,  with write-access. Had to do write-access
>>>>>> because of the reason you've mentioned above, which is base MIB. It
>>>>>> would be painful to publish/support write-access MIB's when there is
>>>>>> no clear interest. Hence my clarification question.
>>>>> This mentions three vendors wanting to implement MIB as writable.
>>>>>
>>>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
>>>>>
>>>>> And one more vendor voicing for writable.
>>>>>
>>>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
>>>>>
>>>>> I agree that defining & wording writable MIB is much more painful than all
>>>> read-only MIB. But above thread indicates the desire by multiple vendors to
>>>> implement writable BFD MIB. Therefore it does seem that there are
>>>> interests, and going forward with write-access will benefit the community.
>>>> And with *ReadOnlyCompliance defined, BFD MIB can also accommodate
>>>> those implementing them as just read-only.
>>>>> -Nobo
>>>>>
>>>>>> -sam
>>>>>>
>>>>>>> -- Jeff
>>> .
>>>
>>


From nobody Fri Apr 18 13:20:39 2014
Return-Path: <jhaas@slice.pfrc.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 0945D1A0100; Thu, 17 Apr 2014 15:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.84
X-Spam-Level: 
X-Spam-Status: No, score=-1.84 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.272, 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 C1saCmvMvMKx; Thu, 17 Apr 2014 15:15:14 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id CF17F1A011D; Thu, 17 Apr 2014 15:15:14 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 37915C2A3; Thu, 17 Apr 2014 18:15:11 -0400 (EDT)
Date: Thu, 17 Apr 2014 18:15:11 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>
Message-ID: <20140417221511.GC29430@pfrc>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/cTg7X9Yde7tKMlFgG5B8SeNr6jE
X-Mailman-Approved-At: Fri, 18 Apr 2014 13:20:35 -0700
Cc: "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "ietf@ietf.org" <ietf@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 17 Apr 2014 22:15:16 -0000

On Thu, Apr 17, 2014 at 09:18:28PM +0000, Nobo Akiya (nobo) wrote:
> > I did not see a compliance requirement for a system that only implements
> > BFD protocol version 0.  That absence should at least be mentioned
> > somewhere.  For example, if this reflects a considered and deliberate
> > decision by the WG, that should be mentioned in the introduction.
> 
> Good point. If I remember correctly, BFD version 0 had a problem in the state machine that can cause the two ends to fall into a deadlock. It would be, therefore, very bad for anybody to have BFD version 0 deployed out there, and asking for any MIB compliance requirement for such. Consensus on absence of compliance requirement for BFD version 0 was never polled in the WG, but I can say that there shouldn't be any desire for that.

With respect to v0 vs. v1 from a MIB perspective, the only user-visible
detail was the additional state in the state machine.  That means that the
MIB in its current form should be able to accommodate bfd v0.

This does suggest, however, that the TC mib could use a comment in the
DESCRIPTION toward the point that failing(5) is only valid for BFD v0.

A conformance clause indicating that those so foolish as to deploy BFD v0
would better be served by the determinism of a five-year-old child flipping
a coin is probably out of scope for the draft.  But if someone has
sufficiently proscriptive text to add to say "don't do bfd v0" that is
acceptable to the reviewers, I'm fine with that.

-- Jeff


From nobody Fri Apr 18 13:20:41 2014
Return-Path: <jhaas@slice.pfrc.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 A4F6F1A00D1; Thu, 17 Apr 2014 15:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.84
X-Spam-Level: 
X-Spam-Status: No, score=-1.84 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.272, 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 uxxf6ice03wp; Thu, 17 Apr 2014 15:18:54 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 6449C1A0173; Thu, 17 Apr 2014 15:18:54 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id CB696C2A3; Thu, 17 Apr 2014 18:18:50 -0400 (EDT)
Date: Thu, 17 Apr 2014 18:18:50 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
Message-ID: <20140417221850.GD29430@pfrc>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/aLHS9d30XcV3wugkRSYIU7Cvso8
X-Mailman-Approved-At: Fri, 18 Apr 2014 13:20:35 -0700
Cc: ietf@ietf.org, adrian@olddog.co.uk, rtg-bfd@ietf.org, zali@cisco.com, 'General Area Review Team' <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 17 Apr 2014 22:18:55 -0000

Sam,

On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
> %sam - If this MIB allows write access, do you/WG anticipate, any extension to the MIB should also provide write-access as well? For example: http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments this base MIB to support MPLS. It adds more confusion than solving the issue as base MIB supports write-access, but augmented/ MIB extension doesn't. 
> 
> As the BFD MIB authors were not supportive of write-access objects in the MIBs, why to have them in the first place? 

As noted in earlier mailing list chatter, there is some support for write
access in existing implementations.  Given the lack of significant detail
when pressed for the name of such an implementation, I'm suspecting smaller
vendor or internal implementation.  That's still sufficient to leave write
available.

Given that one of the original contexts of asking if we could remove write
was whether IETF was being asked to provide such a thing for MPLS-TP with
related impact on your extension MIB and the answer was "no", that shouldn't
be the main criteria.  

My suspicion is that if we were to ship the base MIB with writeable objects,
we may be forced to consider similar things for the extension MIB(s).

-- Jeff


From nobody Fri Apr 18 13:20:43 2014
Return-Path: <tnadeau@lucidvision.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 180EC1A01D9; Fri, 18 Apr 2014 04:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, 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 ticfNNMf88AU; Fri, 18 Apr 2014 04:51:17 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 747EA1A01BB; Fri, 18 Apr 2014 04:51:17 -0700 (PDT)
Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id ED2B9276E09A; Fri, 18 Apr 2014 07:51:12 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_CA1BA98C-0029-484D-835E-D8BB0151E3E9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <5350F335.8020309@cisco.com>
Date: Fri, 18 Apr 2014 07:51:11 -0400
Message-Id: <33B44E73-320B-4FC9-8438-E471F605F318@lucidvision.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com> <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com> <5350F335.8020309@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/n9IQBSO95OEWIItwc7-xPK3wTZ0
X-Mailman-Approved-At: Fri, 18 Apr 2014 13:20:36 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "Sam K. Aldrin" <aldrin.ietf@gmail.com>, "Nobo Akiya \(nobo\)" <nobo@cisco.com>, Farrel Adrian <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-17
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, 18 Apr 2014 11:51:22 -0000

--Apple-Mail=_CA1BA98C-0029-484D-835E-D8BB0151E3E9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Apr 18, 2014:5:41 AM, at 5:41 AM, Benoit Claise <bclaise@cisco.com> =
wrote:

> On 18/04/2014 04:17, Nobo Akiya (nobo) wrote:
>> Hi Sam,
>>=20
>>> -----Original Message-----
>>> From: Sam K. Aldrin [mailto:aldrin.ietf@gmail.com]
>>> Sent: Thursday, April 17, 2014 9:24 PM
>>> To: Nobo Akiya (nobo)
>>> Cc: Jeffrey Haas; ietf@ietf.org; 'Black, David'; =
adrian@olddog.co.uk; rtg-
>>> bfd@ietf.org; Zafar Ali (zali); 'General Area Review Team'
>>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>>>=20
>>> Hi Nobo,
>>> [sorry for the top post]
>>>=20
>>> Yes, this is an old MIB and was in existence for a long time.
>>> My only concern is with the new extension MIB's. If the base MIB =
(this MIB)
>>> has write access, future extension MIB's may be forced to support =
write-
>>> access. And that is the painful part, where community at large has =
not
>>> shown interest in developing write-access MIB's at IETF, lest
>>> implementation.
>>>=20
>>> I want to re-iterate again, I am not objecting or proposing an =
alternative
>>> option. Just wanted to get clarification, so that, we don't have to =
burn cycles
>>> and do the exercise again, when we have to review these new =
extension
>>> MIB's.
>> That's a good point, it would be good to have this clarified for =
future work.
>>=20
>> IMO:
>>=20
>> For new charters, IESG encourages NETCONF/YANG. This means S-BFD (if =
gets included in the charter) should look into NETCONF/YANG (i.e. not =
extension to the BFD base MIB).
>>=20
>> For currently chartered BFD tasks, the BFD WG should continue with =
writable MIB. Large part of that is the BFD base & MPLS MIBs which =
[painful] writable effort is mostly done already.
> This is in essence what =
https://www.ietf.org/iesg/statement/writable-mib-module.html says.
>=20
> Regards, Benoit.

	Yes, this is why we left the writable stuff in - and why I =
recently spent about 4 hours doing Adrian's edits around support of such =
things.  Lets please put the discussion around read-write to bed for =
these two modules as they clearly were well under way and complete by =
the time the statement came out.

	--Tom



>>=20
>> -Nobo
>>=20
>>> -sam
>>>=20
>>> On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:
>>>=20
>>>> Hi Sam,
>>>>=20
>>>>>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>>>>>>> %sam - If this MIB allows write access, do you/WG anticipate, =
any
>>>>> extension to the MIB should also provide write-access as well? For
>>> example:
>>>>> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments
>>>>> this base MIB to support MPLS. It adds more confusion than solving
>>>>> the issue as base MIB supports write-access, but augmented/ MIB
>>> extension doesn't.
>>>>>>> As the BFD MIB authors were not supportive of write-access =
objects
>>>>>>> in
>>>>> the MIBs, why to have them in the first place?
>>>>>> As noted in earlier mailing list chatter, there is some support =
for
>>>>>> write access in existing implementations.  Given the lack of
>>>>>> significant detail when pressed for the name of such an
>>>>>> implementation, I'm suspecting smaller vendor or internal
>>>>>> implementation.  That's still sufficient to leave write =
available.
>>>>>>=20
>>>>>> Given that one of the original contexts of asking if we could =
remove
>>>>>> write was whether IETF was being asked to provide such a thing =
for
>>>>>> MPLS-TP with related impact on your extension MIB and the answer =
was
>>>>>> "no", that shouldn't be the main criteria.
>>>>> No. The context of my question is not related to MPLS-TP as such, =
but
>>>>> write- access support in general.
>>>>> I should have added 'clarification' in my earlier email.
>>>>>> My suspicion is that if we were to ship the base MIB with =
writeable
>>>>>> objects, we may be forced to consider similar things for the
>>>>>> extension
>>>>> MIB(s).
>>>>> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, =
MPLS-TE
>>>>> and BFD-MIB respectively,  with write-access. Had to do =
write-access
>>>>> because of the reason you've mentioned above, which is base MIB. =
It
>>>>> would be painful to publish/support write-access MIB's when there =
is
>>>>> no clear interest. Hence my clarification question.
>>>> This mentions three vendors wanting to implement MIB as writable.
>>>>=20
>>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
>>>>=20
>>>> And one more vendor voicing for writable.
>>>>=20
>>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
>>>>=20
>>>> I agree that defining & wording writable MIB is much more painful =
than all
>>> read-only MIB. But above thread indicates the desire by multiple =
vendors to
>>> implement writable BFD MIB. Therefore it does seem that there are
>>> interests, and going forward with write-access will benefit the =
community.
>>> And with *ReadOnlyCompliance defined, BFD MIB can also accommodate
>>> those implementing them as just read-only.
>>>> -Nobo
>>>>=20
>>>>> -sam
>>>>>=20
>>>>>> -- Jeff
>> .
>>=20
>=20
>=20


--Apple-Mail=_CA1BA98C-0029-484D-835E-D8BB0151E3E9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTURGvAAoJEPcO+I7eiUJZZdUP/2hj6JdK+vrnJ453vcz5vMtQ
hUDqYKBE+thw5IfQ8M8dzqEm0cCEn885BVskoq/VPSfbmeWFTDUhcuQKjY5Oaf2E
tAQZkr1erB3MxhI4iUr6on2pzHaNXfvJ3Q7pb16wK/mq+e7MILbNPYX3CdfpdKR5
LiJIAi40qA+1l2noIArF1kFc58HRqlZqj2tx51CVk0f4G/8TL+fT3kBcEa67QWdv
HTirCYJU+zyEBEZkA5YXWYQJZW98eXa+2ta8rdR4hJ8C2o9sRAwgxmPjrfldUPVg
DZkj99welxc4tAV1j7D3LrIuVYBrlM5SXXaeP90qVhWbLWlRI+B7oUB8L+QsT31e
KaLb10AY8W7y/OkwOEjkqMt41Udx7GhkCr8VAdOHVV+Nq0Zwl3tA7373odf48Xxl
DWkTyLdaZUJ1sj0oIEaWtYbmTowcpNW3ZRSob9GdLCgv9QYm4JQSPii1/2gCutMm
wiqN3Uwfn/Hi4BAy/IT3IUajQ9YCPzB18GrnEWTAiFlrAfqlzjKo+/8JX6d5BVxc
bVX0bWPVC/g61+ScskzqluSVXGgE+4dOr52/dHQ3/AJdrTdUT6kRHMGowW8KPP85
HvF+/+I4bjKrDrkAA2U9LIFmQedcf7KZ4EhMTSGY1wUWPXNkjDVwmRI8k8F1Ba2a
Vm3F1kdHtkHwB2M3H6sm
=AeIB
-----END PGP SIGNATURE-----

--Apple-Mail=_CA1BA98C-0029-484D-835E-D8BB0151E3E9--


From nobody Fri Apr 18 16:34:35 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 262CF1A0503 for <gen-art@ietfa.amsl.com>; Fri, 18 Apr 2014 16:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.2
X-Spam-Level: 
X-Spam-Status: No, score=-101.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_LETTER=-2, 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 jUWGJ88KR4bY for <gen-art@ietfa.amsl.com>; Fri, 18 Apr 2014 16:34:25 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 318841A04FA for <gen-art@ietf.org>; Fri, 18 Apr 2014 16:34:25 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1WbIIR-0007fk-Kr; Sat, 19 Apr 2014 00:34:19 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Sat, 19 Apr 2014 00:34:09 +0100
Message-Id: <1397864049.15324.27546.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/uAHGp0OoQrdKUsfMb93e-lGmLBs
Cc: RFC Interest <rfc-interest@rfc-editor.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>
Subject: [Gen-art] Gen-art early review of draft-hoffman-xml2rfc-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: Fri, 18 Apr 2014 23:34:30 -0000

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

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

This is an "early review" requested by Heather Flanagan as part of the 
development of xml2rfc version 3.
 
Document: draft-hoffman-xml2rfc-04.txt
Reviewer: Elwyn Davies
Review Date: 19 April 2014
IETF LC End Date: N/A
IESG Telechat date: (if known) N/A

Summary:

Major issues:

Minor issues:
s1.1/s1.1.1:
I think it would good to split up the text in s1.1 into two parts.  The
text from para 2 ("The design criteria of the changes..") up to and
including the para starting "The canonical RFCs will not have..." is
about the design rationale and probably deserves a separate section.
s1.1.1 should be a sub-section of this new section.  The remainder of
s1.1 is then *really* the change list.  

ss2.11, 2.37, 2.42, 2.47: <city> and other components of <postal>:
Should these elements be allowed to be any unicode characters with an
@ascii attribute as per fullname?

ss2.16, 2.17, 2.18 <dl> and components:  I think the definition list
needs a bit more work.
- <dd> doesn't seem to have a way of getting blank lines into a
definition.  I think it needs the same alternative 'sequence of one or
more <t>'s as allowed for <ol> and <ul>.
- <dd> should allow subsidiary <dl>'s as content.
- Is there any reason why a <dd> shouldn't include <texttable> (and
indeed any other type of list entry)?  Currently <texttable> only occurs
as a child of <section>. 
- Should the author be allowed any control over the amount of indent for
the definition part?  I realize that we are trying to avoid controlling
the formatting explicitly, but there may be aesthetic/readbility reasons
why the author may want the indent to be a controllable.  One reason is
where there are two or more logically related definition lists, maybe
in different sections or just separated by other text.  The author may
wish to have the same amount of indent in these lists so that the reader
is not distracted by the different amount of indent.  My suggestion
would be to allow the author to specify a text string whose length is
used to determine the indent - this avoids any need to specify units or
worry about line length.  Presumably the default would be 'a bit longer
than the longest definition term in the list' although I am not sure
what happens if you have a very long label/term and the definition start
on the same line.
- This brings me on to another issue.  A convention often used in
definition or dictionary lists is that if the label/term is longer than
the hanging indent, the label is allowed to run over the top of the
definition but the definition starts on the same line as the term.  I am
not clear if this can be achieved with the specification as is.  I would
like to be able to achieve this (see next point).
- The 'hanging' attribute is used to specify that the term is or is not
on a separate line.  If hanging is false is the intention that the
definition will be indented?  Or is this left up to the whim of the
formatter?  Currently all list entries are indented (although you could
perhaps use a zero indent - I have never tried!) so it would probably
worth being explicit about what is intended.  If the intention is not to
indent, then it might be useful to have an additional value for spacing
that also adds space between the label line and the definition.

s2.22.7 figure/@title attr:  There is currently no way to incorporate
font characteristic changes in the title (bold etc).  In v2 this has
never been an issue, but it might be desirable to be able to allow font
changes in future.  Maybe this could be done by allowing a <title>
element instead of the attribute and modify the title to allow font
changes - that would also allow the document title to include font
changes as well.  This would probably apply to <texttable> as well.

s2.33 <ol>: The <ol> element does not cater for the cases like 
<list style="format R(%d)" counter="req"> 
that allows ordered lists to be numbered across multiple
instances/sections without having to manually keep track of the counter
start value in each separate <ol>.  An example can be found in 
RFC 5772, s3.6.1 et seq.  This would need the counter attribute to
reappear on this element.  The discussion of the possibility of
specifying a hangIndent as per the comments on <dl> above is also
relevant because the length of the label is dependent on the number and
it is better to use the same indent for all related lists.  Having a
counter="variable-name" attribute would also alter the effect of start -
counter variable should be left unchanged if specified and start is not
specified.  'Default' counter (known as .COUNTER in v2) is reset to 1 if
neither counter nor start is specified. 

Nits/editorial comments:
========================
s1.1, 2nd set of bullets, 1st bullet: Expand RNG

ss1.1, 2.36, 2.37, App B: s/postalline/postalLine/ (this has been
discussed on the mailing list and does make it more comprehensible.

s1.1:  I think it would be worth giving an overview of what is being
done to list handling here, probably as a new subsection to go with with
the rebranded s1.1.1.  It is IMO the other really major change that
users will have to get their heads round.

s2.2 <author>:  Probably worth  mentioning that it is not used when
<author> is used in <reference>.  Maybe also worth flagging that
<facsimile> is deprecated.

s2.4 <area>: s/this document applies to/to which this document relates/
Should probably mention that the areas/names might change over time.
(Are there any historical areas that need to be considered?  I don't
think so but I can't be sure.)

s2.5 <artwork>: Could be useful to mention use of CDATA here.  I would
be inclined to add 'accessed via a URI' to the discussion of the src
attribute.

s2.5.5 src attr: Are there any restrictions on the URI to be used?  In
particular is file: allowed? 

s2.5.5 src attr: Does this need an associated 'scale' attribute so that
the graphic can be displayed as intended?

s2.5.6 type attr, last para: s/mainatin/maintain/

s2.5.6 type attr: I think 'xml' would be an essential extra.  Also
probably 'message-flow' and maybe 'protocol-format' or some such as a
variant on ascii-art specifically identifying one of the many wire
format descriptions. 

s2.6.3 initials attr: An example would help ... say 'e.g., for J. Edgar
Hoover initials="J. E."'

ss2.7, 2.25, 2.52 <b>, <i>, <tt>:  I presume the intention is that the
effects of these font characteristic specifiers should be cumulative
(i.e., <i> just italic text <b> bold italic text </b> italic text</i>)
etc.  Whatever is intended should be explained (maybe a common section
back at the beginning?) I assume that  <i><b><i></i></b></i> would be
legal but that the inner <i> would have no additional effect in each
case.  Maybe processors could issue a warning.

s2.8 <back>: Worth noting that <sections> are appendices here.

s2.9 <blockquote>/s2.9.2 cite attr: I am not keen on requiring the cite
value to be a URL.  Wouldn't it be more natural for it to be a reference
anchor with an optional attribute specifying the location within the
reference, thus:
   <blockquote anchor="bq1" cite="RFC1918" location="Section 2.5 -or-
page 3">Some quoted text........</blockquote>

[I am not sure about the attribute name 'location' but nothing better
springs to mind just now.]

Would this then come out (in ASCII) as:

... previous text with quoted lines indented after it:
   Some quoted text.......
           ([RFC1918], Section 2.5)
Followed by text after the @blockquote.  The reference should probably
be right justified.

How would the anchor be referenced?  Maybe "[RFC1918], Section 2.5"

s2.10 <c>: I have suggested further on that @ttcol should have an align
attribute.  If this is agreed, my idea would be that the alignment
applies to all the cells in the column headed by the relevant @ttcol.

s2.13 <country>:  Once upon a time I thought that we were supposed to be
using two letter country codes from ISO 3166. As per RFC 2629, s2.2.2.

s2.15 <date>: Where do we put 'vague date' strings? Must say I have
never tried a vague date in a reference.  

s2.15.1 day attr:  Note that it is the day *number*. 

s2.15 <date>/s2.15.2 month attr: Is there any reason why we can't allow 
month numbers here as an official alternative?  I think we can still do
the calculation! Better check the style guide to see how dates are
printed out: Presumably the intention is we stick with 16 April 2014
etc.

s2.16 <dd>: I think this should be able to have 

s2.18 <dt>, para 1:  Cut and paste error, I think. Replace with 
'The term being defined by an entry in a definition list.' 

s2.15.3 year attr: Should probably reinforce that it is a 4 digit year
number (or explicitly that it can be 2 digit?)

s2.20 <eref>: Might be worth mentioning that the content and the @target
attr would be combined if the output format can represent hyperlinks.

s2.22 <figure>, para 1: s/postamable/postamble/

s2.22.6 suppress-title attr:  Reversing the meaning of the true/false
values would make more sense (as discussed elsewhere).  Comment also
applies to s2.49.4.

s2.22.7 title attr:  The autogenerated title is combined with the
contents of the attribute  in v2 - I think this could be clarified (I
misread it): Try s/the title gets an/the title is combined with an/.
Also applies to s2.49.5.

s2.23 <format>:  I like 'depredated'!  Unfortunately I guess we have to
s/Depredated/Deprecated/.

s2.29 <li>:  Should one or more <texttable>'s be allowed in the content?

s2.33.3 style attr: It would be useful to specify  what happens after
z/Z in the letter cases (I *think* v2 does aa, ab, ac etc.).  Somewhere
there is an RFC that exercises this.  I believe that if you go back far
enough in the xml2rfc mailing list (say about 2005) there is some
discussion of this.

s2.33.3 style attr: It would probably be very occasionally useful to be
able to specify the field width of the % formats.

s2.37 <postalline>: As suggested on the mailing list it would be more
readable if this were <postalLine>.  As suggested previously this might
need an ascii equivalent.

ss2.38/2.39 <postamble>/<preamble>: Is there ever a need for multiple
paras in a pre-/postamble?  I think I have seen <vspace> in some cases.
Should multiple <t>'s be allowed?

s2.40 <reference>: This is, I believe, still under discussion.  One
point is that the id case may want to specify the version of the id
explicitly (defaulting to the most recent).  The content model is not
right: It is either empty or one <front> plus optional <seriesInfo>,
<format>, <innerRefContent>, <annotation>'s.  <innerRefContent> is
defined but hasn't made it into <reference yet>.
In para 6: s/refernence/reference/

ss2.40.2/2.40.3 series/document attrs:  These are specified as mandatory
but this doesn't work if the <front> specification option is used.

ss2.43.7/2.43.10 obsoletes/updates attrs: Probably ought to specify
whether or not white space is allowed.

s2.44 <section>: Might be worth saying explicitly that it can be empty.

s2.48 <t>: Should <texttable> be allowed within <t>?  As mentionaed
above there are some other places where <t> might be a child (<dd> and
maybe <note>).

s2.49 <texttable>: See previous discussion as to whether <texttable>
should be used elsewhere.  See also comments on s2.22.6 and s2.22.7.

s2.50 <tindent>: Could <tindent>'s appear inside list elements?

s2.51 <title>: Could this be allowed <b>, <i> and <tt>in the content?

s2.53 <ttcol>:  The content model should probably allow for <b>, <i> and
<tt>.

Appendix B looks to match OK except for <reference>.





From nobody Sun Apr 20 15:45:26 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 644E41A007D for <gen-art@ietfa.amsl.com>; Sun, 20 Apr 2014 15:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 3YcF30uWWd_R for <gen-art@ietfa.amsl.com>; Sun, 20 Apr 2014 15:45:21 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCDB1A006F for <gen-art@ietf.org>; Sun, 20 Apr 2014 15:45:21 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id fp1so3069537pdb.14 for <gen-art@ietf.org>; Sun, 20 Apr 2014 15:45:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=YbbA+u65EL16Ng6kpS5bio49rSlo/SeOzOKKsvi0org=; b=EXK//4NhDcDRktVayp4nQKGeO+aG5ubzTy230Sn1SV2aox+tV0Euf5Am1QHnlzkqRE BA/t+vJWEo3qyKHxkTNlvp+24hKR5CMcQjeqCDE6BwLVqFBDU0F9k7T1WzWoinX1EKEn tq1SQpGe2dDhdhKY6c+MeCMb3ameANCK9vnimWak5/F0WcZ8qu8QERm02U4oYiumUeHX 4PXWCn3Rr4Ov3q4e+Znuz89JElyJftpGNlB9OFnKZ1e/syPkhwkzHJCXGjxjC33Oxp9f OC7pgYnkK0/a1YZAzPH99VKV1fjORWYoupDRAFmMlbj++ZXMC0hvBEkLgAe/rmj3jPi2 5tow==
X-Received: by 10.68.136.133 with SMTP id qa5mr34472765pbb.63.1398033916985; Sun, 20 Apr 2014 15:45:16 -0700 (PDT)
Received: from [192.168.178.20] (136.197.69.111.dynamic.snap.net.nz. [111.69.197.136]) by mx.google.com with ESMTPSA id qh2sm176787391pab.13.2014.04.20.15.45.14 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Apr 2014 15:45:16 -0700 (PDT)
Message-ID: <53544DF8.2010301@gmail.com>
Date: Mon, 21 Apr 2014 10:45:12 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-rtcweb-use-cases-and-requirements.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/HIpGI-cgqGtvVZJM0SA2psOc3KA
Subject: [Gen-art] Gen-ART LC review of draft-ietf-rtcweb-use-cases-and-requirements-14.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, 20 Apr 2014 22:45:24 -0000

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

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

Document: draft-ietf-rtcweb-use-cases-and-requirements-14.txt
Reviewer: Brian Carpenter
Review Date: 2014-04-21
IETF LC End Date: 2014-04-25
IESG Telechat date:

Summary:  In good shape but still needs work.
--------

Comment:
--------

In case there are W3C people reading this review, let me clarify that Gen-ART reviews
are by generalists who are often encountering a topic for the first time. I haven't
classified the issues into "major" and "minor" but some of them really do need
attention before the document advances. There are also some nits noted at the end.

Issues:
-------

>   The following considerations are applicable to all use cases:
>
>   o  Clients can be on IPv4-only
>
>   o  Clients can be on IPv6-only
>
>   o  Clients can be on dual-stack

It isn't clear whether this is intended to include the case where an
IPv4-only client communicates with an IPv6-only node (or vice versa).

It also isn't clear about cases in which a mobile client's connectivity
changes dynamically during a session (e.g. from IPv4 to IPv6). This is
partly clarified later by F17, but only partly.

>   o  Clients can be on networks with a NAT using any type of Mapping
>      and Filtering behaviors (as described in RFC4787).

That document is scoped for UDP only. Is that sufficient? As I understand the
RTCWEB transport drafts, it is aiming at connection-oriented transport.
(How many NATs support SCTP, for example?)

> 3.2.  Common requirements
>
>   The requirements retrived from the Simple Video Communication Service
>   use-case (Section 3.3.1) by default apply to all other use-cases, and
>   are considred common.  For each individual use-case, only the
>   additional requirements are listed.

In fact you duplicate the additional requirements in each use case where they
occur. That seems like overkill. Also there's at least one mix-up as a result,
noted below.

> 3.3.1.2.  Common Requirements
...
>  F3      Transmitted streams and data must be rate
>          controlled (meaning that the browser must, regardless
>          of application behavior, reduce send rate when
>          there is congestion).

I think that needs to be broken into two more atomic requirements.
Something like

   F3.1    There must be a mechanism by which the transport layer
           can signal the occurrence of congestion to the browser.

   F3.2    Transmitted streams and data must be rate
           controlled (meaning that the browser must, regardless
           of application behavior, reduce send rate while
           there is congestion).

The change from "when" to "while" is intentional, since the browser
should allow the rate to increase when there is no congestion.

>   F11     It must be possible to protect streams and data
>           from wiretapping [RFC2804].

I don't see the relevance of the reference (of which I am a co-author),
which mainly states that the IETF won't consider requirements *for* wiretapping.
I'm sure you can find a reference that says encryption is a Good Thing.

>   F14     The browser must make it possible to set up a
>           call between two parties without one party
>           learning the other party's host IP address.

It is not clear how to interpret that. I assume it's supposed to be a
restatement of the earlier comment:

>   The application gives the users the opportunity to stop it from
>   exposing the host IP address to the application of the other user.

But -- assuming the implementation model is peer-to-peer communication
between the two hosts, rather than client1-server-client2 communication --
I'm afraid I don't see how F14 can be guaranteed, since the peers must be
aware of each others' IP address. Even if the browser and app hide the
remote address, a little Wiresharking will reveal it immediately.
There's not much point stating a requirement that cannot be met.

I realised at this point in the document that you need to be very
explicit about whether communication is indeed intended to be peer-to-peer
or via the server. And assuming it is meant to be peer-to-peer, what
is the model for the rendez-vous between the peers? What requirements do
you need to solve the resulting referral problem?
(http://tools.ietf.org/html/draft-carpenter-referral-ps-02)

This topic belongs in the Common Requirements.

> 3.3.7.1.  Description
...
>   The user in the previous use case that starts a trip is behind a
>   common residential router that supports prioritization of traffic.

Please talk about differentiated services (RFC 2474 etc.). IP doesn't
have simple priority. That's exactly why the DART WG was just formed.

> 3.3.7.2.  Additional Requirements
>
>   ----------------------------------------------------------------
>   REQ-ID      DESCRIPTION
>   ----------------------------------------------------------------
>   F17     The communication session must survive across a
>           change of the network interface used by the
>           session
>   ----------------------------------------------------------------
>   F22     The browser must be able to receive streams and
>           data from multiple peers concurrently.
>   ----------------------------------------------------------------

This seems completely messed up. The reader expects requirements for
QoS at this point. Isn't this "F22" really F24?

> 3.3.10.2.  Additional Requirements
>
>   ----------------------------------------------------------------
>   REQ-ID      DESCRIPTION
>   ----------------------------------------------------------------
>   F22     The browser should be able to take advantage
>           of available capabilities (supplied by network
>           nodes) to prioritize voice, video and data
>           appropriately.

Again, please cite differentiated services rather than prioritization.
Also, you now have two different F22s. This one seems to fit 3.3.7.2 better.

Below, you also have two F25s. And other duplicates. Wasn't the idea
just to add *new* requirements when they arose? As F22 shows, the
duplication is error-prone.

> 6.  Security Considerations

I am really surprised that there isn't a sub-section on Privacy
Considerations. RFC 6973 describes the various types of threat and they
seem specially relevant here.

Nits:
-----

> 2.  Conventions
>
>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>   document are to be interpreted as described in BCP 14, RFC 2119
>   [RFC2119].

The change log says you removed this. Also there is no change log
since version 10.

RFC 4787 is mentioned but not listed as an Informative Reference.

>    A17, A23
>    A13, A14, A15, A16

What are these lines that occur in a few places?

RFC 2804 and RFC 5479 are Informational documents so cannot reasonably be
Normative References.


From nobody Mon Apr 21 13:21:01 2014
Return-Path: <eric@notcom.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 0BA711A0281 for <gen-art@ietfa.amsl.com>; Mon, 21 Apr 2014 13:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, 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 6-oyyPRlGTkc for <gen-art@ietfa.amsl.com>; Mon, 21 Apr 2014 13:20:54 -0700 (PDT)
Received: from mail-yh0-f52.google.com (mail-yh0-f52.google.com [209.85.213.52]) by ietfa.amsl.com (Postfix) with ESMTP id CDC951A02AF for <gen-art@ietf.org>; Mon, 21 Apr 2014 13:20:53 -0700 (PDT)
Received: by mail-yh0-f52.google.com with SMTP id 29so2045665yhl.11 for <gen-art@ietf.org>; Mon, 21 Apr 2014 13:20:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=VOTEPQjZiFiaj+A92QM5sKYZ9gLyayNdY9aPm5OXlv4=; b=RpuQY7aak6a1a1CaC2ieDu5WsBwZdN2hcHufs8qPI4JfbhgNnji5GctcRMRytdCbcT xBkgkDibguXGvrxHVVt1OlKSADQANQ84/M881blbhFP7z/wEaVnGGITfiOscSnml8XyL ysveZUpp15n/nhDj6hzQA1xMEzQ3y7oqQ9aSGSzB9lTw2xy/uQbOSBjFKbtHdafRaUks hqICsXh5w6B/D75k2NsIBl85yIZhANGI5JnLkdlJ4F/M768OO7KOupOXjcLw8+vVkmYx lzupa9ZFEUhHViq4Ca3zLgm7/44f6cc1jNcuBRl1BGyGN52RYy/TnYKCssHPDQd/gQAw eJXQ==
X-Gm-Message-State: ALoCoQkUawT7bQhFGxhUq02Ja+O/ooKSUYXv+axJVG3c/LrutG9DI87cjsGtll0nmRexOy03Zo3n
MIME-Version: 1.0
X-Received: by 10.236.102.70 with SMTP id c46mr56255379yhg.40.1398111648525; Mon, 21 Apr 2014 13:20:48 -0700 (PDT)
Received: by 10.170.60.5 with HTTP; Mon, 21 Apr 2014 13:20:48 -0700 (PDT)
Date: Mon, 21 Apr 2014 16:20:48 -0400
Message-ID: <CA+97oKMKPCwc5X-EL=dS2X1dK3zWoMkieeu2DN78P9P=mxZdpg@mail.gmail.com>
From: Eric Osborne <eric@notcom.com>
To: General Area Review Team <gen-art@ietf.org>, draft-ietf-mpls-psc-updates.all@tools.ietf.org,  "mpls@ietf.org" <mpls@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/EBzua-REHIKn5eRdPiDrJQTdlLE
Subject: [Gen-art] Addressing comments on draft-ietf-mpls-psc-updates-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, 21 Apr 2014 20:20:58 -0000

Folks-

  I have posted draft-ietf-mpls-psc-updates-04.  It addresses the
gen-art comments as well as other feeback received on this list from
the v-03 last call.  I also shuffled things around so that the section
order made more sense.

  This draft elicited a comment and a warning from idnits.  I believe
they are both OK to disregard:

1)

  -- The draft header indicates that this document updates RFC6378, but the
     abstract doesn't seem to directly say this.  It does mention RFC6378
     though, so this could be OK.


It's pretty clear that the document updates rfc6378.


2)

  == Missing Reference: 'RFC-ietf-mpls-psc-updates-04' is mentioned on line
     412, but not defined


This is a self-reference which needs to be updated with the RFC number
for this draft.



  I expect this to be good to go, but given the amount of reshuffling
and new text I'd like to give folks one more shot at tweaking the
language.

The meat of the work is in section 2.2.  Adrian, Elwyn - this contains
the majority of the changes based on gen-art feedback and other
discussions on the list.  Please give this the once-over at your
convenience.




eric


From nobody Tue Apr 22 08:40:36 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 48AE01A0682; Tue, 22 Apr 2014 08:40:35 -0700 (PDT)
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 9df5IJXvxz2P; Tue, 22 Apr 2014 08:40:29 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id DB7E31A068B; Tue, 22 Apr 2014 08:40:18 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1Wccnh-0005W1-PC; Tue, 22 Apr 2014 16:40:01 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Eric Osborne <eric@notcom.com>
In-Reply-To: <CA+97oKMKPCwc5X-EL=dS2X1dK3zWoMkieeu2DN78P9P=mxZdpg@mail.gmail.com>
References: <CA+97oKMKPCwc5X-EL=dS2X1dK3zWoMkieeu2DN78P9P=mxZdpg@mail.gmail.com>
Content-Type: text/plain
Date: Tue, 22 Apr 2014 16:39:59 +0100
Message-Id: <1398181199.15324.27769.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/unStQUg0QiItWlN40nhh8fSOLhI
Cc: "mpls@ietf.org" <mpls@ietf.org>, General Area Review Team <gen-art@ietf.org>, draft-ietf-mpls-psc-updates.all@tools.ietf.org
Subject: Re: [Gen-art] Addressing comments on draft-ietf-mpls-psc-updates-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, 22 Apr 2014 15:40:35 -0000

Hi, Eric.

I checked over the new version and it addresses my previous comments
just fine.  Thanks.

One trivial nit:
s2.3.2: s/processesed/processed/

I noted Adrian's point about draft-ietf-mpls-tp-psc-itu in the tracker
and I guess the suggested change is reasonable.

If you are updating the text you could also fix:
- The style is supposed to be 'RFC 6378' rather than RFC6378 outside of
reference anchors.
- Sort out the punctuations of 'i.e.,' : Currently there is one with no
comma (5, para 1), two with one comma and one with two commas (s6, para
10 - the quote from RFC 6378 where it has one comma); and of 'e.g.,' :
Currently one with no comma (s4.3, para 2).

I'll send an official telechat review when the review is scheduled.

Cheers,
Elwyn



On Mon, 2014-04-21 at 16:20 -0400, Eric Osborne wrote:
> Folks-
> 
>   I have posted draft-ietf-mpls-psc-updates-04.  It addresses the
> gen-art comments as well as other feeback received on this list from
> the v-03 last call.  I also shuffled things around so that the section
> order made more sense.
> 
>   This draft elicited a comment and a warning from idnits.  I believe
> they are both OK to disregard:
> 
> 1)
> 
>   -- The draft header indicates that this document updates RFC6378, but the
>      abstract doesn't seem to directly say this.  It does mention RFC6378
>      though, so this could be OK.
> 
> 
> It's pretty clear that the document updates rfc6378.
> 
> 
> 2)
> 
>   == Missing Reference: 'RFC-ietf-mpls-psc-updates-04' is mentioned on line
>      412, but not defined
> 
> 
> This is a self-reference which needs to be updated with the RFC number
> for this draft.
> 
> 
> 
>   I expect this to be good to go, but given the amount of reshuffling
> and new text I'd like to give folks one more shot at tweaking the
> language.
> 
> The meat of the work is in section 2.2.  Adrian, Elwyn - this contains
> the majority of the changes based on gen-art feedback and other
> discussions on the list.  Please give this the once-over at your
> convenience.
> 
> 
> 
> 
> eric
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 23 05:56:04 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 AC8241A038D for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 05:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.871
X-Spam-Level: 
X-Spam-Status: No, score=-2.871 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] 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 nFaYFss11Rk6 for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 05:55:59 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 2EDBB1A0260 for <gen-art@ietf.org>; Wed, 23 Apr 2014 05:55:58 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsIJANC2V1PGmAcV/2dsb2JhbABZgkIjIU9XqkEGBJBuiHqBGRZ0gicBAQMSG0wSARUHDlYmAQQODRqIHwEMoTWtaheMZoFBIBGDK4EVBJoshUuLU4Mxgis
X-IronPort-AV: E=Sophos; i="4.97,911,1389762000"; d="scan'208,217"; a="51645291"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 Apr 2014 08:55:52 -0400
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; 23 Apr 2014 08:40:18 -0400
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.0174.001; Wed, 23 Apr 2014 14:55:21 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat Review for draft-ietf-idr-aigp-17
Thread-Index: Ac9e80hXmKR5r4YoQ7i2AMeqTGJ6zw==
Date: Wed, 23 Apr 2014 12:55:20 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C7C5387@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_9904FB1B0159DA42B0B887B7FA8119CA5C7C5387AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/3BIwlK47TZokXCkp625CTDf0WyA
Cc: "draft-ietf-idr-aigp.all@tools.ietf.org" <draft-ietf-idr-aigp.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART Telechat Review for draft-ietf-idr-aigp-17
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, 23 Apr 2014 12:56:02 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C7C5387AZFFEXMB04globa_
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: https://datatracker.ietf.org/doc/draft-ietf-idr-aigp/

Reviewer: Dan Romascanu

Review Date: 4/23/14

IETF LC End Date: 4/8/14

IESG Telechat date: 4/24/14



Summary: Ready



Major issues:



Minor issues:



Nits/editorial comments:


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on Gen-ART, please see the FAQ at &lt;
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please wait for direction from your document shep=
herd or AD before posting a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document: https://datatracker.ietf.org/doc/draft-=
ietf-idr-aigp/<o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 4/23/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 4/8/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: 4/24/14<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary: Ready<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"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C7C5387AZFFEXMB04globa_--


From nobody Wed Apr 23 06:07:05 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 0296F1A0394 for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 06:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.171
X-Spam-Level: 
X-Spam-Status: No, score=-2.171 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272] 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 HA1QNKEsFgBC for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 06:07:00 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 396511A0392 for <gen-art@ietf.org>; Wed, 23 Apr 2014 06:07:00 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkJAIe6V1OHCzIm/2dsb2JhbABZgkIjIU9XqkeQcoh6gRkWdIInAQEDEhtMEgEVBw5WJgEEDg0aiB8BDKE4rWsXjGaBQSARgyuBFQSaLIVLi1ODMYIr
X-IronPort-AV: E=Sophos; i="4.97,912,1389762000"; d="scan'208,217"; a="59334925"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 23 Apr 2014 09:06:35 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 23 Apr 2014 09:05:41 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0174.001; Wed, 23 Apr 2014 15:06:33 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat review for draft-ietf-mpls-ldp-applicability-label-adv
Thread-Index: Ac9e9NipjsWJDIq1QCWKdMWzFaA8AQ==
Date: Wed, 23 Apr 2014 13:06:33 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C7C53AF@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_9904FB1B0159DA42B0B887B7FA8119CA5C7C53AFAZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/JiX55NlBpALB2SkpSxyaxDT_4dU
Cc: "draft-ietf-mpls-ldp-applicability-label-adv.all@tools.ietf.org" <draft-ietf-mpls-ldp-applicability-label-adv.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART Telechat review for draft-ietf-mpls-ldp-applicability-label-adv
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, 23 Apr 2014 13:07:02 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C7C53AFAZFFEXMB04globa_
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: https://datatracker.ietf.org/doc/draft-ietf-mpls-ldp-applicabilit=
y-label-adv/

Reviewer: Dan Romascanu

Review Date: 4/23/14

IETF LC End Date: 2/24/14

IESG Telechat date: 4/24/14



Summary:

Ready

Major issues:



Minor issues:



Nits/editorial comments:




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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on Gen-ART, please see the FAQ at &lt;
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please wait for direction from your document shep=
herd or AD before posting a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document: https://datatracker.ietf.org/doc/draft-=
ietf-mpls-ldp-applicability-label-adv/<o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 4/23/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 2/24/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: 4/24/14<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<o:p></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"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C7C53AFAZFFEXMB04globa_--


From nobody Wed Apr 23 08:44:11 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 56A731A026A for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 08:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.955
X-Spam-Level: 
X-Spam-Status: No, score=0.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.793] 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 txWnkA1q22H6 for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 08:44:06 -0700 (PDT)
Received: from p130.piuha.net (unknown [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 60D911A00CB for <gen-art@ietf.org>; Wed, 23 Apr 2014 08:44:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 558CB2CD0E; Wed, 23 Apr 2014 18:44:00 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9m2bbWNpaWmE; Wed, 23 Apr 2014 18:43:58 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 0DB632CC48; Wed, 23 Apr 2014 18:43:56 +0300 (EEST)
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: <534B3E6F.3010709@stpeter.im>
Date: Wed, 23 Apr 2014 12:43:57 -0300
Content-Transfer-Encoding: 7bit
Message-Id: <2F079AC7-D0E5-49F3-8697-DDEAB13848F0@piuha.net>
References: <534AFAE4.4040102@gmail.com> <534B3E6F.3010709@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/9LUm_u2sRn5v0tjoc8Utlqfw7eA
Cc: Pete Resnick <presnick@qualcomm.com>, draft-ietf-precis-framework@tools.ietf.org, Gen Art <gen-art@ietf.org>, precis-chairs@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-precis-framework-15
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, 23 Apr 2014 15:44:08 -0000

Tom: Thank you for the review.

Jari

On Apr 13, 2014, at 10:48 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:

> Hi Tom, thanks for the review and for the kind words about the document.
> 
> Peter
> 
> On 4/13/14, 3:00 PM, Tom Taylor 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>.
>> 
>> This document is beautifully written and is ready to go. As a person
>> unfamiliar with the basic concepts I had to read into the document a bit
>> to get traction, then re-read from the beginning, but the additional
>> effort was minimal and rewarding.
>> 
>> Document:           draft-ietf-precis-framework-15
>> Reviewer:           Tom Taylor
>> Review Date:        13/04/2014
>> IETF LC End Date:   23/04/2014
>> IESG Telechat date: 24/04/2014
>> 
>> Summary: This document provides:
>> -- the historical background leading up to the approach used for
>>    its technical content
>> -- definitions of two string classes suitable as bases for two
>>    general classes of application
>> -- instructions for creating profiles of the string classes
>>    (particularly the FreeformClass) for specific applications
>> -- a satisfying set of security considerations.
>> 
>> This document obsoletes Stringprep (RFC 3454). It establishes new IANA
>> registries for derived properties of Unicode code points for Unicode
>> versions subsequent to 6.2, for base string classes, and for profiles.
>> 
>> Major issues:
>> 
>> Minor issues:
>> 
>> Nits/editorial comments:
>> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 23 08: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 0C2561A00CB for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 08:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.955
X-Spam-Level: 
X-Spam-Status: No, score=0.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.793] 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 1LSLG07UDBcK for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 08:50:52 -0700 (PDT)
Received: from p130.piuha.net (unknown [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id A42161A0016 for <gen-art@ietf.org>; Wed, 23 Apr 2014 08:50:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9B8A52CD39; Wed, 23 Apr 2014 18:50:45 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TNb-8qEzKJEo; Wed, 23 Apr 2014 18:50:44 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 93EAD2CC48; Wed, 23 Apr 2014 18:50:43 +0300 (EEST)
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: <9904FB1B0159DA42B0B887B7FA8119CA5C7C53AF@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 23 Apr 2014 12:50:43 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <D234DC8E-FB6F-4FB4-BD37-2C6815CB679B@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C7C53AF@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/YyqMSPxMUP50uLakXeMsBocwOso
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-mpls-ldp-applicability-label-adv.all@tools.ietf.org" <draft-ietf-mpls-ldp-applicability-label-adv.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review for draft-ietf-mpls-ldp-applicability-label-adv
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, 23 Apr 2014 15:50:53 -0000

Dan: Thank you very much for your review. And Kamran et al: thank you =
for making the changes earlier requested.

I have placed a no-obj position for this document on tomorrow's =
telechat.

Jari

On Apr 23, 2014, at 10:06 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 < =
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: =
https://datatracker.ietf.org/doc/draft-ietf-mpls-ldp-applicability-label-a=
dv/
> Reviewer: Dan Romascanu
> Review Date: 4/23/14
> IETF LC End Date: 2/24/14
> IESG Telechat date: 4/24/14
> =20
> Summary:
> Ready
> Major issues:
> =20
> Minor issues:
> =20
> Nits/editorial comments:
> =20
> =20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 23 08:54:39 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 5A5F71A02C6 for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 08:54:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.172
X-Spam-Level: 
X-Spam-Status: No, score=-1.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_SUMOF=1, RP_MATCHES_RCVD=-0.272] 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 3mziEmM8O84I for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 08:54:33 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 878BD1A0365 for <gen-art@ietf.org>; Wed, 23 Apr 2014 08:54:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 13D262CD0E; Wed, 23 Apr 2014 18:54:25 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ixDSP-GUc67V; Wed, 23 Apr 2014 18:54:23 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id EBB122CC48; Wed, 23 Apr 2014 18:54:21 +0300 (EEST)
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: <532235BA.3030006@ericsson.com>
Date: Wed, 23 Apr 2014 12:54:22 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D51D4B3-07A2-41C4-8A13-67D10921499C@piuha.net>
References: <E87B771635882B4BA20096B589152EF62862687F@eusaamb107.ericsson.se> <C10F3E57F0DA43CFA8B3A95FC0A780A1@buildpc> <532235BA.3030006@ericsson.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/oWn5IlzutKtei9GZGHp-ajhEkDE
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-ipsecme-ikev2-fragmentation.all@tools.ietf.org, Valery Smyslov <svan@elvis.ru>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-ipsecme-ikev2-fragmentation-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, 23 Apr 2014 15:54:34 -0000

Suresh: Thank you very much for the review, and Valery for making the =
changes. I have placed the no-objection position for this document in =
tomorrow's IESG telechat.

Jari

On Mar 13, 2014, at 7:48 PM, Suresh Krishnan =
<suresh.krishnan@ericsson.com> wrote:

> Hi Valery,
>  Thanks a lot for quickly addressing my comments. Your proposed =
resolutions sound good to me.
>=20
> Cheers
> Suresh
>=20
> On 03/13/2014 02:03 AM, Valery Smyslov wrote:
>> Hi Suresh,
>> thank you for the review. Please find my answers below.
>>=20
>>    ----- Original Message -----
>>    *From:* Suresh Krishnan <mailto:suresh.krishnan@ericsson.com>
>>    *To:* draft-ietf-ipsecme-ikev2-fragmentation.all@tools.ietf.org
>>    <mailto:draft-ietf-ipsecme-ikev2-fragmentation.all@tools.ietf.org> =
;
>>    General Area Review Team <mailto:gen-art@ietf.org>
>>    *Sent:* Thursday, March 13, 2014 4:50 AM
>>    *Subject:* Gen-ART Last Call review of
>>    draft-ietf-ipsecme-ikev2-fragmentation-05
>>=20
>>    I am the assigned Gen-ART reviewer for
>>    draft-ietf-ipsecme-ikev2-fragmentation-05
>>=20
>>    For background on Gen-ART, please see the FAQ at
>>    <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.
>>=20
>>    Please resolve these comments along with any other Last Call
>>    comments you may receive.
>>=20
>>    Summary: This draft is almost ready for publication as a Proposed
>>    Standard but I have some suggestions that the authors may like to
>>    consider.
>>=20
>>    * Retransmission and duplication
>>=20
>>    It is unclear how the receiver of the message deals with lost
>>    fragments that are retransmitted. If I understand correctly, the
>>    sender only knows that all the fragments did not get to the
>>    receiver, and has no knowledge about which fragments were not
>>    received. So it ends up retransmitting all the fragments.
>>=20
>> Right.
>>=20
>>    This means that the receiver needs to do some form of
>>    de-duplication. Are the duplicate fragments discarded on the
>>    receiver (without verification) or are they blindly written into a
>>    reassembly buffer (after verification)? The difference is pretty
>>    significant because there is a authentication step involved for =
each
>>    fragment.
>>=20
>> Duplicated fragments are discarded without verification. It is =
described
>> in Section 2.6, second bullet:
>>=20
>>    o  Check, that this IKE Fragment Message is new for the receiver =
and
>>       not a replay.  If IKE Fragment message with the same Message =
ID,
>>       same Fragment Number and same Total Fragments fields was =
already
>>       received and successfully processed, this message is considered =
a
>>       replay and MUST be silently discarded.
>>=20
>> Note, that this check takes place before verifying fragment =
authenticity
>> (next bullet).
>>=20
>> If you think this text is unclear, could you please suggest how to
>> improve it?
>>=20
>>    * IPv6 payload length
>>=20
>>    I find this text to be a bit handwavy
>>=20
>>    =93   For IPv6 this estimation is difficult as there may be =
varying IPv6
>>=20
>>        Extension headers included.=94
>>=20
>>    I think it would be preferable to at least estimate for the case
>>    where there are no extension headers. Suggest adding some text =
like
>>    this (Feel free to modify/ignore)
>>=20
>>    NEW:
>>=20
>>        For IPv6 Encrypted Payload content size is less than IP =
Datagram
>>    size
>>=20
>>        by the sum of the following values in the case where there are =
no
>>=20
>>        extension :
>>=20
>>        o  IPv6 header size (40 bytes)
>>=20
>>        o  UDP header size (8 bytes)
>>=20
>>        o  non-ESP marker size (4 bytes if present)
>>=20
>>        o  IKE Header size (28 bytes)
>>=20
>>        o  Encrypted Payload header size (4 bytes)
>>=20
>>        o  IV size (varying)
>>=20
>>        o  padding and its size (at least 1 byte)
>>=20
>>        o  ICV size (varying)
>>=20
>>        The sum may be estimated as 81..85 bytes + IV + ICV + padding.
>>=20
>>        If extension headers are present, the payload content size is
>>    further
>>=20
>>        reduced by the sum of the size of the extension headers. The
>>    length of
>>=20
>>        each extension header can be calculated as 8 * (Hdr Ext Len) =
bytes
>>=20
>>        except for the fragment header which is always 8 bytes in =
length.
>>=20
>> Thank you, I'll use it.
>>=20
>>    * Editorial
>>=20
>>    Appendix A:
>>=20
>>    s/forgeg/forged/
>>=20
>>    s/ reassempling/reassembly/
>>=20
>> Thanks,
>>=20
>> Valery.
>>=20
>>    Thanks
>>=20
>>    Suresh
>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 23 08:55:39 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 6D5891A00CB for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 08:55:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.955
X-Spam-Level: 
X-Spam-Status: No, score=0.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.793] 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 1Rtmwq_NRaPk for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 08:55:35 -0700 (PDT)
Received: from p130.piuha.net (unknown [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA8D1A0016 for <gen-art@ietf.org>; Wed, 23 Apr 2014 08:55:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 62CCA2CD0E; Wed, 23 Apr 2014 18:55:29 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eJ_afMjAVDVZ; Wed, 23 Apr 2014 18:55:28 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 73ACF2CC48; Wed, 23 Apr 2014 18:55:27 +0300 (EEST)
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: <9904FB1B0159DA42B0B887B7FA8119CA5C7C5387@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 23 Apr 2014 12:55:27 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <94F6377C-A31B-4CCE-B312-68040050D859@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C7C5387@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/xs4tJYwaQ62-kc78GIxB4vm0CHY
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-idr-aigp.all@tools.ietf.org" <draft-ietf-idr-aigp.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Review for draft-ietf-idr-aigp-17
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, 23 Apr 2014 15:55:36 -0000

Thanks for your review, Dan.

Jari

On Apr 23, 2014, at 9:55 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 < =
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: https://datatracker.ietf.org/doc/draft-ietf-idr-aigp/
> Reviewer: Dan Romascanu
> Review Date: 4/23/14
> IETF LC End Date: 4/8/14
> IESG Telechat date: 4/24/14
> =20
> Summary: Ready
> =20
> Major issues:
> =20
> Minor issues:
> =20
> Nits/editorial comments:
> =20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 23 08:58: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 E5A271A02A2; Wed, 23 Apr 2014 08:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.955
X-Spam-Level: 
X-Spam-Status: No, score=0.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.793] 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 FLydAnP902NI; Wed, 23 Apr 2014 08:58:38 -0700 (PDT)
Received: from p130.piuha.net (unknown [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 205B71A00CB; Wed, 23 Apr 2014 08:58:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 135FE2CD0E; Wed, 23 Apr 2014 18:58:32 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pm3JWH4-5bqe; Wed, 23 Apr 2014 18:58:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 9BEB32CC48; Wed, 23 Apr 2014 18:58:29 +0300 (EEST)
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: <031401cf2c89$d4a7c460$7df74d20$@gmail.com>
Date: Wed, 23 Apr 2014 12:58:29 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <17346734-D965-45A8-BD0F-75B952A564CC@piuha.net>
References: <031401cf2c89$d4a7c460$7df74d20$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/OBvW5iRxxLmt8yCC0saLLwVPNBc
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IESG <iesg@ietf.org>, draft-housley-pkix-oids.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-housley-pkix-oids-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: Wed, 23 Apr 2014 15:58:40 -0000

Thanks for your review, Roni. But, there was no e-mail response. Russ =
happens to be sitting next to me and he's checking whether he has dealt =
with this.

Jari

On Feb 18, 2014, at 6:14 AM, Roni Even <ron.even.tlv@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document:  draft-housley-pkix-oids-00
> Reviewer: Roni Even
> Review Date:2014=962-18
> IETF LC End Date: 2014=962-28
> IESG Telechat date:
> =20
> Summary: This draft is ready for publication as an Informational RFC.
> =20
> =20
> Major issues:
> =20
> Minor issues:
> =20
> =20
> Nits/editorial comments:
>=20
> In section 3.26 first entry I noticed when comparing to RFC5055 =
section 3.2.4.2.4 that the description in RFC5055 is =
id-nvae-name-mismatch. It caused me a problem when trying to find it in =
RFC5055, the values are correct so may not be important (maybe to ASN.1 =
compiler?) I did not check all the descriptions but I looked at RFC 5055 =
to understand the registration. (BTW: all the names in this table are =
not the same)
>=20
> =20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 23 09:18:34 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 73CF81A02A2; Wed, 23 Apr 2014 09:18:31 -0700 (PDT)
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 Q7J_2Lmy4dSn; Wed, 23 Apr 2014 09:18:28 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id D34181A03CF; Wed, 23 Apr 2014 09:18:27 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 2E869F2C079; Wed, 23 Apr 2014 12:18:12 -0400 (EDT)
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 ZT49-xtYIdcR; Wed, 23 Apr 2014 12:17:51 -0400 (EDT)
Received: from 156-193.netmundial.org (unknown [199.91.193.156]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3EDFFF2C07B; Wed, 23 Apr 2014 12:17:50 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=windows-1252
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <17346734-D965-45A8-BD0F-75B952A564CC@piuha.net>
Date: Wed, 23 Apr 2014 12:17:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F1A536EB-B522-4CFB-A2A2-8A32F496C8A1@vigilsec.com>
References: <031401cf2c89$d4a7c460$7df74d20$@gmail.com> <17346734-D965-45A8-BD0F-75B952A564CC@piuha.net>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/JcbfoJJ7aYv8y_h5bnN3vt_2jI0
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IESG <iesg@ietf.org>, draft-housley-pkix-oids.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-housley-pkix-oids-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: Wed, 23 Apr 2014 16:18:31 -0000

Roni:

Thanks for catching this error.  I will post -03 to correct it.  I will =
also take this opportunity to add a sentence to the security =
considerations.

Russ


On Apr 23, 2014, at 11:58 AM, Jari Arkko wrote:

> Thanks for your review, Roni. But, there was no e-mail response. Russ =
happens to be sitting next to me and he's checking whether he has dealt =
with this.
>=20
> Jari
>=20
> On Feb 18, 2014, at 6:14 AM, Roni Even <ron.even.tlv@gmail.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-housley-pkix-oids-00
>> Reviewer: Roni Even
>> Review Date:2014=962-18
>> IETF LC End Date: 2014=962-28
>> IESG Telechat date:
>>=20
>> Summary: This draft is ready for publication as an Informational RFC.
>>=20
>>=20
>> Major issues:
>>=20
>> Minor issues:
>>=20
>>=20
>> Nits/editorial comments:
>>=20
>> In section 3.26 first entry I noticed when comparing to RFC5055 =
section 3.2.4.2.4 that the description in RFC5055 is =
id-nvae-name-mismatch. It caused me a problem when trying to find it in =
RFC5055, the values are correct so may not be important (maybe to ASN.1 =
compiler?) I did not check all the descriptions but I looked at RFC 5055 =
to understand the registration. (BTW: all the names in this table are =
not the same)


From nobody Wed Apr 23 09:46: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 724A31A0221; Wed, 23 Apr 2014 09:45:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 FX3JzsKbFhcg; Wed, 23 Apr 2014 09:45:57 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A4BBA1A01E6; Wed, 23 Apr 2014 09:45:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 82EE62CEC5; Wed, 23 Apr 2014 19:45:50 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G33CVZLimfEg; Wed, 23 Apr 2014 19:45:49 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E00C62CC48; Wed, 23 Apr 2014 19:45:47 +0300 (EEST)
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: <F1A536EB-B522-4CFB-A2A2-8A32F496C8A1@vigilsec.com>
Date: Wed, 23 Apr 2014 13:45:48 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA53ECA5-F662-43DE-AF01-FAA17A39FBF4@piuha.net>
References: <031401cf2c89$d4a7c460$7df74d20$@gmail.com> <17346734-D965-45A8-BD0F-75B952A564CC@piuha.net> <F1A536EB-B522-4CFB-A2A2-8A32F496C8A1@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/o9hT5_qh4L6kkZ7tDQlBlominog
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IESG <iesg@ietf.org>, draft-housley-pkix-oids.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-housley-pkix-oids-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: Wed, 23 Apr 2014 16:45:59 -0000

Thanks, Russ. That also clears the question i had on the tracker about =
whether some further discussion is needed.

Jari

On Apr 23, 2014, at 1:17 PM, Russ Housley <housley@vigilsec.com> wrote:

> Roni:
>=20
> Thanks for catching this error.  I will post -03 to correct it.  I =
will also take this opportunity to add a sentence to the security =
considerations.
>=20
> Russ
>=20
>=20
> On Apr 23, 2014, at 11:58 AM, Jari Arkko wrote:
>=20
>> Thanks for your review, Roni. But, there was no e-mail response. Russ =
happens to be sitting next to me and he's checking whether he has dealt =
with this.
>>=20
>> Jari
>>=20
>> On Feb 18, 2014, at 6:14 AM, Roni Even <ron.even.tlv@gmail.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-housley-pkix-oids-00
>>> Reviewer: Roni Even
>>> Review Date:2014=962-18
>>> IETF LC End Date: 2014=962-28
>>> IESG Telechat date:
>>>=20
>>> Summary: This draft is ready for publication as an Informational =
RFC.
>>>=20
>>>=20
>>> Major issues:
>>>=20
>>> Minor issues:
>>>=20
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> In section 3.26 first entry I noticed when comparing to RFC5055 =
section 3.2.4.2.4 that the description in RFC5055 is =
id-nvae-name-mismatch. It caused me a problem when trying to find it in =
RFC5055, the values are correct so may not be important (maybe to ASN.1 =
compiler?) I did not check all the descriptions but I looked at RFC 5055 =
to understand the registration. (BTW: all the names in this table are =
not the same)
>=20


From nobody Wed Apr 23 10:17:06 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 CDB6C1A03D1; Wed, 23 Apr 2014 10:17:00 -0700 (PDT)
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 1Alo5Ukpa-7I; Wed, 23 Apr 2014 10:16:59 -0700 (PDT)
Received: from mail-ee0-x232.google.com (mail-ee0-x232.google.com [IPv6:2a00:1450:4013:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id D224F1A0389; Wed, 23 Apr 2014 10:16:58 -0700 (PDT)
Received: by mail-ee0-f50.google.com with SMTP id c13so1014865eek.23 for <multiple recipients>; Wed, 23 Apr 2014 10:16:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=HB/+jIUxoi9KRTWAgQLpk8QK4Q5FHIwqDfmXbnTpdfk=; b=iAAzP+uzyq1TLW+Eo0LrqIfmaD7jhOJkokTMebFw+FMZGp7ScBUc8bg2TCcoTLAahV H9qZFtRqbrscq1oeGWTm7/HQ5KlssPZA4mml6X7XkqWDDcWdQwPlLMQLXT58eiCRyeiF K0uBEaecOfx6F27OW8DKtdVizW1ogI7WiJ6/Mvpi9/g+UtyQ2zHC3KQjqD53Di/Z8vVR Ss6l2TKw0JVE7mDT4et5WwkPrllqJIDc8im/2JzNobJbHNF0vdP63fEOQzV0JoMlEZ+q O9VTe/gFTEFij0rXMse2FtxMZRLm83kg/r9TrPfGSWEC1hKwROZBsWjOV8eGEpFwcIoA vQJg==
X-Received: by 10.15.31.70 with SMTP id x46mr64068862eeu.26.1398273412595; Wed, 23 Apr 2014 10:16:52 -0700 (PDT)
Received: from RoniE ([109.67.104.144]) by mx.google.com with ESMTPSA id y7sm7983819eev.5.2014.04.23.10.16.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 23 Apr 2014 10:16:51 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Russ Housley'" <housley@vigilsec.com>
References: <031401cf2c89$d4a7c460$7df74d20$@gmail.com> <17346734-D965-45A8-BD0F-75B952A564CC@piuha.net> <F1A536EB-B522-4CFB-A2A2-8A32F496C8A1@vigilsec.com>
In-Reply-To: <F1A536EB-B522-4CFB-A2A2-8A32F496C8A1@vigilsec.com>
Date: Wed, 23 Apr 2014 20:16:46 +0300
Message-ID: <007101cf5f17$cfde69a0$6f9b3ce0$@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: AQKOUdJGn0XkSivssDPEaeXoTFjzVQJT4I5XAbjTqQGZgSZHUA==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/eBDg1xCm0x_v6SjhZIUflQDgh7M
Cc: gen-art@ietf.org, 'The IESG' <iesg@ietf.org>, draft-housley-pkix-oids.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-housley-pkix-oids-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: Wed, 23 Apr 2014 17:17:01 -0000

OK

> -----Original Message-----
> From: Russ Housley [mailto:housley@vigilsec.com]
> Sent: 23 April, 2014 7:17 PM
> To: Roni Even
> Cc: gen-art@ietf.org Review Team; The IESG; draft-housley-pkix-
> oids.all@tools.ietf.org
> Subject: Re: [Gen-art] Gen-ART LC review of draft-housley-pkix-oids-00
> 
> Roni:
> 
> Thanks for catching this error.  I will post -03 to correct it.  I will
also take this
> opportunity to add a sentence to the security considerations.
> 
> Russ
> 
> 
> On Apr 23, 2014, at 11:58 AM, Jari Arkko wrote:
> 
> > Thanks for your review, Roni. But, there was no e-mail response. Russ
> happens to be sitting next to me and he's checking whether he has dealt
with
> this.
> >
> > Jari
> >
> > On Feb 18, 2014, at 6:14 AM, Roni Even <ron.even.tlv@gmail.com> wrote:
> >
> >> I am the assigned Gen-ART reviewer for this draft. For background on
Gen-
> ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >>
> >> Please resolve these comments along with any other Last Call comments
> you may receive.
> >>
> >> Document:  draft-housley-pkix-oids-00
> >> Reviewer: Roni Even
> >> Review Date:2014-2-18
> >> IETF LC End Date: 2014-2-28
> >> IESG Telechat date:
> >>
> >> Summary: This draft is ready for publication as an Informational RFC.
> >>
> >>
> >> Major issues:
> >>
> >> Minor issues:
> >>
> >>
> >> Nits/editorial comments:
> >>
> >> In section 3.26 first entry I noticed when comparing to RFC5055 section
> 3.2.4.2.4 that the description in RFC5055 is id-nvae-name-mismatch. It
caused
> me a problem when trying to find it in RFC5055, the values are correct so
may
> not be important (maybe to ASN.1 compiler?) I did not check all the
> descriptions but I looked at RFC 5055 to understand the registration.
(BTW: all
> the names in this table are not the same)


From nobody Wed Apr 23 10:31:17 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 3EDDD1A03D6 for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 10:31:15 -0700 (PDT)
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 UcrIALm2aGP5 for <gen-art@ietfa.amsl.com>; Wed, 23 Apr 2014 10:31:10 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 69CE51A0389 for <gen-art@ietf.org>; Wed, 23 Apr 2014 10:31:10 -0700 (PDT)
X-AuditID: c618062d-f79f66d000001393-ca-5357aa610e24
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 0C.04.05011.16AA7535; Wed, 23 Apr 2014 13:56:18 +0200 (CEST)
Received: from eusjgala119.dyn.sj.us.am.ericsson.se (147.117.188.8) by smtp-am.internal.ericsson.com (147.117.188.86) with Microsoft SMTP Server id 14.3.174.1; Wed, 23 Apr 2014 13:30:59 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_21F1CB79-DD58-4FEC-B968-9988484D4EF2"
Date: Wed, 23 Apr 2014 10:31:21 -0700
Message-ID: <D62FB93E-40B6-488E-B7F9-B0B5BE6C857E@ericsson.com>
To: General Area Review <gen-art@ietf.org>
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
X-Mailer: Apple Mail (2.1874)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJLMWRmVeSWpSXmKPExsUyuXRPiG7SqvBggxNTOSw2zr/AanH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvj5OpOloKzghUdJ/+wNDA+4u9i5OSQEDCR OLn6CiuELSZx4d56ti5GLg4hgaOMEt8ebmWFcA4zSjTt/coIUsUmYCDxdflZsA5mgSSJMwva weLCAr4SmxpXMIHYLAKqEuueH2ABsXkF7CVW/Z/HCFGfI/F0yws2EFtEQEuiefVHNogaPYme 71uZIK6QlXj0oQmsV0hAXWLKrQksExj5ZiFZNwtJC0RcW2LZwtfMELaOxILdn9ggbHmJ7W/n MMPUnDnwmGkBI9sqRo7S4tSy3HQjg02MwLA8JsGmu4Nxz0vLQ4wCHIxKPLxTrvsGC7EmlhVX 5h5ilOZgURLn/fLWOUhIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QD4zT72XMeaU5Mu2ciy9Ce +03y/EmFtO2LfNM8Zv27uP/9CW3Za/1PD6+xLjNQPKB9VO3qslcbP69NtAj0/M0fc868JPgR 2785G39z2keXXKtfn5Ch4b6TO3rDwnB3X455fVWOd55nf13CYtIQ4X7r9VXlEPHfVh6Pwl86 KJ+49kiWI+ba7WM2ZUosxRmJhlrMRcWJAM1Lb6ssAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/r8AnqfWiknW_8Wb31Vmeszec3Mo
Cc: draft-ietf-straw-b2bua-loop-detection.all@tools.ietf.org
Subject: [Gen-art] Gen-ART Review of draft-ietf-straw-b2bua-loop-detection-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, 23 Apr 2014 17:31:15 -0000

--Apple-Mail=_21F1CB79-DD58-4FEC-B968-9988484D4EF2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"

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

Document: draft-ietf-straw-b2bua-loop-detection-04
Reviewer: Wassim Haddad
Review Date: 23 Apr 2014
IETF LC End Date: 25 Apr 2014
IETF Telechat Date: 24 Apr 2014

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

Major Issues: None

Minor Issues: none


Regards,

Wassim H.




--Apple-Mail=_21F1CB79-DD58-4FEC-B968-9988484D4EF2
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset="us-ascii"

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><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-ietf-straw-b2bua-loop-detection-04<br>Reviewer: Wassim Haddad<br>Review Date: 23 Apr 2014<br>IETF LC End Date: 25 Apr 2014<br>IETF Telechat Date: 24 Apr 2014<br><br>Summary: This draft is ready to be published as proposed 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><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Helvetica;  font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div></div><br class="Apple-interchange-newline">
</div>
<br></body></html>
--Apple-Mail=_21F1CB79-DD58-4FEC-B968-9988484D4EF2--


From nobody Thu Apr 24 05:35:11 2014
Return-Path: <eric@notcom.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 970211A01D1 for <gen-art@ietfa.amsl.com>; Thu, 24 Apr 2014 05:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, 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 MnK6K51UGNP4 for <gen-art@ietfa.amsl.com>; Thu, 24 Apr 2014 05:35:06 -0700 (PDT)
Received: from mail-yh0-f51.google.com (mail-yh0-f51.google.com [209.85.213.51]) by ietfa.amsl.com (Postfix) with ESMTP id 957361A01C1 for <gen-art@ietf.org>; Thu, 24 Apr 2014 05:35:06 -0700 (PDT)
Received: by mail-yh0-f51.google.com with SMTP id f10so2140346yha.10 for <gen-art@ietf.org>; Thu, 24 Apr 2014 05:35:00 -0700 (PDT)
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=d235aReLnZQOGjuPSqjq5TqGV8Y9WjLnNSl0GKtjh7A=; b=X+RzAe9wTFt1FHnRKXdzMihbw+6ioJhr1zHU0IunrsUP23DFOoyGcvF61C1o6TikSs nEHbziBVB9ZWC2AIjGXC45jZxTSz3/w8WQ7No6NKEoRwfxfmZrZ0HU9GDf0Ab2ZCMNL2 mWK35kZrhfB/hJAAzeBWt3q3Jrxjqp01fGkI3pRCkw3kF58MyIBl5iQ5X64lZZk9FbPj I0rsIkML2yzNg4ZGFDFKQAvH3Tb+nB3A0e07jAD71fz5IaRPI7+llz8BQL+rZYrum1DN 9eC7H4QwMGdEL+ljTVZOORAZMedZGnpncfTZwY7n2JiR8NLcjaNfW06v9WEIRWzDGyHn wnfg==
X-Gm-Message-State: ALoCoQln0HhaabNUP2P8Mz6Ar27Ycb0XYbxPsCbXdfh4/aFgbfP4zMs4dYHnSIXhKbWMQYwTTT3n
MIME-Version: 1.0
X-Received: by 10.236.20.194 with SMTP id p42mr2078668yhp.56.1398342900447; Thu, 24 Apr 2014 05:35:00 -0700 (PDT)
Received: by 10.170.60.5 with HTTP; Thu, 24 Apr 2014 05:35:00 -0700 (PDT)
In-Reply-To: <1398181199.15324.27769.camel@mightyatom>
References: <CA+97oKMKPCwc5X-EL=dS2X1dK3zWoMkieeu2DN78P9P=mxZdpg@mail.gmail.com> <1398181199.15324.27769.camel@mightyatom>
Date: Thu, 24 Apr 2014 08:35:00 -0400
Message-ID: <CA+97oKPbug_Wo5bHOt8rAxYQ2hr+ZK1YuE+ou29ziTb22zBxWQ@mail.gmail.com>
From: Eric Osborne <eric@notcom.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/XyzD7XhtM2hTBRrCubUFgiQOIoQ
Cc: "mpls@ietf.org" <mpls@ietf.org>, General Area Review Team <gen-art@ietf.org>, draft-ietf-mpls-psc-updates.all@tools.ietf.org
Subject: Re: [Gen-art] Addressing comments on draft-ietf-mpls-psc-updates-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, 24 Apr 2014 12:35:08 -0000

Hi Elwyn-

  Inline.

On Tue, Apr 22, 2014 at 11:39 AM, Elwyn Davies <elwynd@dial.pipex.com> wrote:
> Hi, Eric.
>
> I checked over the new version and it addresses my previous comments
> just fine.  Thanks.
>

Cool!

> One trivial nit:
> s2.3.2: s/processesed/processed/
>

OK.

> I noted Adrian's point about draft-ietf-mpls-tp-psc-itu in the tracker
> and I guess the suggested change is reasonable.
>

I agree.

> If you are updating the text you could also fix:
> - The style is supposed to be 'RFC 6378' rather than RFC6378 outside of
> reference anchors.

OK

> - Sort out the punctuations of 'i.e.,' : Currently there is one with no
> comma (5, para 1), two with one comma and one with two commas (s6, para
> 10 - the quote from RFC 6378 where it has one comma); and of 'e.g.,' :
> Currently one with no comma (s4.3, para 2).

Sorry, I thought I caught all of those.

>
> I'll send an official telechat review when the review is scheduled.
>

OK.
thanks!




eric


> Cheers,
> Elwyn
>
>
>
> On Mon, 2014-04-21 at 16:20 -0400, Eric Osborne wrote:
>> Folks-
>>
>>   I have posted draft-ietf-mpls-psc-updates-04.  It addresses the
>> gen-art comments as well as other feeback received on this list from
>> the v-03 last call.  I also shuffled things around so that the section
>> order made more sense.
>>
>>   This draft elicited a comment and a warning from idnits.  I believe
>> they are both OK to disregard:
>>
>> 1)
>>
>>   -- The draft header indicates that this document updates RFC6378, but the
>>      abstract doesn't seem to directly say this.  It does mention RFC6378
>>      though, so this could be OK.
>>
>>
>> It's pretty clear that the document updates rfc6378.
>>
>>
>> 2)
>>
>>   == Missing Reference: 'RFC-ietf-mpls-psc-updates-04' is mentioned on line
>>      412, but not defined
>>
>>
>> This is a self-reference which needs to be updated with the RFC number
>> for this draft.
>>
>>
>>
>>   I expect this to be good to go, but given the amount of reshuffling
>> and new text I'd like to give folks one more shot at tweaking the
>> language.
>>
>> The meat of the work is in section 2.2.  Adrian, Elwyn - this contains
>> the majority of the changes based on gen-art feedback and other
>> discussions on the list.  Please give this the once-over at your
>> convenience.
>>
>>
>>
>>
>> eric
>>
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>


From nobody Thu Apr 24 13:44: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 DDDE01A0389 for <gen-art@ietfa.amsl.com>; Thu, 24 Apr 2014 13:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 7RMEC1Kyzj7S for <gen-art@ietfa.amsl.com>; Thu, 24 Apr 2014 13:44:07 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id A9C341A0165 for <gen-art@ietf.org>; Thu, 24 Apr 2014 13:44:07 -0700 (PDT)
Received: from ncltghk6cs1.tekelec.com ([198.89.36.10]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3OKhZnB017972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Thu, 24 Apr 2014 15:43:59 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [198.89.36.10] claimed to be ncltghk6cs1.tekelec.com
Message-ID: <53597772.6000401@nostrum.com>
Date: Thu, 24 Apr 2014 15:43:30 -0500
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.4.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/FjcWea_w2KS_Ivz81OCdxRof-U0
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-04-24
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, 24 Apr 2014 20:44:09 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Elwyn Davies      2014-05-16   draft-pal-eidr-urn-01

Francis Dupont    2014-05-02   draft-ietf-ipsecme-esp-ah-reqts-07

Joel Halpern      2014-05-06   draft-ietf-mpls-extended-admin-group-05

Martin Thomson    2014-05-06   draft-ietf-opsawg-large-flow-load-balancing-11

Meral Shirazipour 2014-05-07   draft-ietf-appsawg-uri-get-off-my-lawn-04

Peter Yee         2014-05-21   draft-eastlake-iana-cfm-considerations-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 nobody Thu Apr 24 14:51:21 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 B52281A03F8 for <gen-art@ietfa.amsl.com>; Thu, 24 Apr 2014 14:51:17 -0700 (PDT)
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 jOPQT00x7CtX for <gen-art@ietfa.amsl.com>; Thu, 24 Apr 2014 14:51:15 -0700 (PDT)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by ietfa.amsl.com (Postfix) with ESMTP id 4CB641A03F7 for <gen-art@ietf.org>; Thu, 24 Apr 2014 14:51:15 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id cc10so1788537wib.10 for <gen-art@ietf.org>; Thu, 24 Apr 2014 14:51:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=976aMduacSgI35IteaTCEw2PDbK7eIBifCsyWzO40mU=; b=QVUP0dkHH+VrUQ8JXApz3gPOz5Uj2WFrQknZhLV66GVEDLa41taLqpukmfXtnzWITQ gSqr778Bey9/zeCPceoawh7YqdDvQwxKckM4sYrRbu6bIp/lvd4qP1dTob/ac9N36FQv 5NDTT/xzrImi4xMptpnGECl6kFvWaEQJcUqJNYNIYC7dQASrxTW+sO6V/nSPWWSw5kpK tvjIzg2FCvN023Qx95q+5sm4R0ZWiMl3tRrPrDh4W201eamwgKQgr4CnPXlYvz/r2n+y L7KpgSiWF84PFvckaWBC40v7nH+b/0tjQYzbRGvrhk1pJ4sFECLD/ndY6Jx0pwv9jhRT Jj/w==
MIME-Version: 1.0
X-Received: by 10.194.60.4 with SMTP id d4mr3672358wjr.28.1398376268707; Thu, 24 Apr 2014 14:51:08 -0700 (PDT)
Received: by 10.227.144.132 with HTTP; Thu, 24 Apr 2014 14:51:08 -0700 (PDT)
Date: Thu, 24 Apr 2014 14:51:08 -0700
Message-ID: <CABkgnnW8TLAaWu=M+cn8Fs5uqwuHBjSqOsS0iNmL69qhz4R52Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: draft-ietf-opsawg-large-flow-load-balancing.all@tools.ietf.org,  "gen-art@ietf.org" <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/vOQMoNPeRV9BiNk-Rv0hPtWhYe0
Subject: [Gen-art] Gen-ART review of draft-ietf-opsawg-large-flow-load-balancing-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, 24 Apr 2014 21:51: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-opsawg-large-flow-load-balancing-11
Reviewer: Martin Thomson
Review Date: 2014-04-24
IETF LC End Date: 2014-05-06
IESG Telechat date: (if known)

Summary: Basically ready.  Looks like a pretty straightforward, even
commonsense, coverage of the ways that flow distribution might be
achieved and a need for it identified.

Major issues: None

Minor issues: Or questions, really.

There's not a lot of discussion about the costs of maintaining an
exception list for rebalanced flows.  A hash-based distribution is
going to cost essentially zero state because the outbound path can be
determined on a per-packet basis, but as soon as you start
redistributing, there is an added state cost (and potential increase
in lookup times).  That probably needs some discussion.

This plays into the security considerations, which I think need to
highlight this as a potential DoS vector.  Implementing automatic
redistribution on top of a hash-based stateless distribution is
vulnerable to attack if the hash function used is predictable.

In Section 5.1 the recommended formula for determining imbalance puts
the average utilization on the divisor, which leads to large
variations in output when the overall utilization is low.  In that
state, it's probably best to avoid redistribution entirely, since no
single link is likely to be close to capacity.  I'd recommend a
simpler formula of max_i(|U_i - U_ave|).  (Note: You are missing an
ellipsis in the calculation of U_ave in the divisor part.)

Nits/editorial comments:

You don't rely on the definition of COTS, which I think is good.  It
can probably go.  There may be others.  I don't tend to check these
things.

Some diagrams have some alignment issues, see Figure 2.

I've never encountered a Fat-Tree before.  So the use of the name
actually hindered comprehension.  It's harmless, but probably
unnecessary.

Section 5.3 essentially includes a copy of Section 4.3.1.

The formulae in Section 5.6.1 are incomprehensible.  I assume that
there is a missing solidus '/' character on each.


From nobody Thu Apr 24 14:55:47 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 64E4A1A0407; Thu, 24 Apr 2014 14:55:45 -0700 (PDT)
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 STJv4lV94laG; Thu, 24 Apr 2014 14:55:44 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id F038D1A03FD; Thu, 24 Apr 2014 14:55:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 111A11C0A6C; Thu, 24 Apr 2014 14:55:38 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (74-84-92-146.client.mchsi.com [74.84.92.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4C7711C0518; Thu, 24 Apr 2014 14:55:37 -0700 (PDT)
Message-ID: <53598854.2010201@joelhalpern.com>
Date: Thu, 24 Apr 2014 17:55:32 -0400
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.4.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org,  "mpls@ietf.org" <mpls@ietf.org>
References: <53597772.6000401@nostrum.com>
In-Reply-To: <53597772.6000401@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/rc5E1gQdkW9upuk9mAsgXWYkEBQ
Subject: [Gen-art]  review: draft-ietf-mpls-extended-admin-group-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, 24 Apr 2014 21:55:45 -0000

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

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

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

Document: draft-ietf-mpls-extended-admin-group-05
     Extended Administrative Groups in MPLS-TE
Reviewer: Joel M. Halpern
Review Date: 24-April-2014
IETF LC End Date: 06-May-2014
IESG Telechat date: N/A

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

Major issues: N/A

Minor issues:
     I believe that the description of when to use this EAG is slightly 
misleading.  The text says that EAG is to be used "when a node wishes to 
advertise more than 32 colors for a link."  I believe it is more 
accurate to say that it is to be used "when a node wishes to advertise 
colors for a link which are not represented in the first 32 bits of the 
color mask."  The node may only wish to advertise colors 7 and 60, but 
that will require the EAG.

Nits/editorial comments: N/A


From nobody Thu Apr 24 22:30:30 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 B286D1A030B; Thu, 24 Apr 2014 22:30:28 -0700 (PDT)
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 DN7jsYcV5HsT; Thu, 24 Apr 2014 22:30:26 -0700 (PDT)
Received: from p3plsmtpa06-04.prod.phx3.secureserver.net (p3plsmtpa06-04.prod.phx3.secureserver.net [173.201.192.105]) by ietfa.amsl.com (Postfix) with ESMTP id AD8071A02F9; Thu, 24 Apr 2014 22:30:26 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa06-04.prod.phx3.secureserver.net with  id u5WG1n00F1huGat015WHe1; Thu, 24 Apr 2014 22:30:19 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-eastlake-iana-cfm-considerations.all@tools.ietf.org>
Date: Thu, 24 Apr 2014 22:30:22 -0700
Message-ID: <009d01cf6047$760de3c0$6229ab40$@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: Ac9gNrW6VZ0N8bbSRQGXqYGcN4aAIQ==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/YnMl-cTaIOFfIrUOryaSw7IrFvQ
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-eastlake-iana-cfm-considerations-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, 25 Apr 2014 05:30:28 -0000

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

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

Document: draft-eastlake-iana-cfm-considerations-01
Reviewer: Peter Yee
Review Date: April-24-2014
IETF LC End Date: May-21-2014
IESG Telechat date: TBD

Summary: This draft is basically ready for publication as a Best Current
Practice, but has some nits that should be fixed before publication. [Ready
with nits.]

This document provides the IANA Considerations for two registries covering
the IEEE Std 802.1Q-2011 CFM OpCode and TLV Type blocks assigned to the
IETF.

Nits:

Most comments that follow are for alignment with the terminology and usage
found in IEEE Std 802.1Q-2011.

General: globally replace "Continuity" with "Connectivity".

General: globally replace "Codepoints" with "Code Points".

General: globally replace "Op-Code" with "OpCode".

Page 3, 2nd paragraph, 2nd sentence: change "IANA Consideration" to "IANA
Considerations".

Page 5, 1st paragraph: end the reference with a period.

Page 5, 2nd paragraph: replace "Mansfield, S." with "and S. Mansfield" to
match http://www.rfc-editor.org/in-notes/rfc-ref.txt.  Hey, I'm running out
of nits to pick here. :-)

		-Peter Yee



From nobody Fri Apr 25 00:44:34 2014
Return-Path: <R.Jesske@telekom.de>
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 4B06B1A0336 for <gen-art@ietfa.amsl.com>; Fri, 25 Apr 2014 00:44:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level: 
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] 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 8gQovx6Q-yyQ for <gen-art@ietfa.amsl.com>; Fri, 25 Apr 2014 00:44:27 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id 42EDA1A0311 for <gen-art@ietf.org>; Fri, 25 Apr 2014 00:44:26 -0700 (PDT)
Received: from he113656.emea1.cds.t-internal.com ([10.134.99.16]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 25 Apr 2014 09:44:18 +0200
Received: from HE113667.emea1.cds.t-internal.com ([fe80::c943:1394:e86e:fce3]) by HE113656.emea1.cds.t-internal.com ([10.134.99.16]) with mapi; Fri, 25 Apr 2014 09:44:17 +0200
From: <R.Jesske@telekom.de>
To: <jari.arkko@piuha.net>
Date: Fri, 25 Apr 2014 09:44:16 +0200
Thread-Topic: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-13
Thread-Index: Ac9Ux2EreeKJU44GQ3Sj8lNIfhmgJgLjAuAQ
Message-ID: <058CE00BD4D6B94FAD033A2439EA1E4B01E1D8A5DADC@HE113667.emea1.cds.t-internal.com>
References: <CABkgnnVVQCAz=ixeR04rc75Vc-rL2JFQcjT0-hX_UCL-c=FGjQ@mail.gmail.com> <5F92FD08-1636-48C0-9634-8806E9F577FF@piuha.net> <CABkgnnUdkHYxGnFOkaHf-Xc+v=UYiASBS7KBJeC75aEV1SyKMA@mail.gmail.com> <CAHBDyN5a+S-1QUzD0eWpkxMdT0tBZ9_DZELM1FKuutmXNk8a0g@mail.gmail.com> <058CE00BD4D6B94FAD033A2439EA1E4B01E0CE66CA6F@HE113667.emea1.cds.t-internal.com> <74C1B909-BE20-434E-85FD-B866FC855D8A@piuha.net>
In-Reply-To: <74C1B909-BE20-434E-85FD-B866FC855D8A@piuha.net>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/8m4EPh9XRQDZlJ8zV61C1FxH73k
Cc: rlb@ipv.sx, gen-art@ietf.org, gonzalo.camarillo@ericsson.com, draft-drage-sipping-rfc3455bis@tools.ietf.org, atle.monrad@ericsson.com, mary.ietf.barnes@gmail.com
Subject: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-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, 25 Apr 2014 07:44:30 -0000

Hi Jari,

1. I have put the document status to informal
2. I have shifted TS 24.229 to normative and updated the references to the =
latest 3GPP Release
3. Added Text to 6.1: That is, the privacy of the user relies on the other =
entities in the session not disclosing information that they have learned a=
bout the user.
4. For the P-Access-Network Info header I was looking to our use cases. The=
 main use case is the emergency call where a possibility is: the UE include=
s a P-Access-Network-Info header field, which contains a cell identifier or=
 location identifier, which is subsequently mapped, potentially by the reci=
pient, into a real location.=20

So we have the statement in 4.4.2:
  Additionally, the first outbound proxy, if in possession of
   appropriate information, can also add a P-Access-Network-Info header
   field with its own information.

So I have added a sentence in Section 4.4 saying:

A proxy providing services based on the P-Access-Network header field must =
consider the trust relationship to the UA or outbound proxy including the P=
-Access-Network header field.

I hope that solves the issues. A version -14 will coming soon.

Best Regards

Roland



-----Urspr=FCngliche Nachricht-----
Von: Jari Arkko [mailto:jari.arkko@piuha.net]=20
Gesendet: Donnerstag, 10. April 2014 16:15
An: Jesske, Roland
Cc: mary.ietf.barnes@gmail.com; draft-drage-sipping-rfc3455bis@tools.ietf.o=
rg; gen-art@ietf.org; martin.thomson@gmail.com; atle.monrad@ericsson.com; g=
onzalo.camarillo@ericsson.com; rlb@ipv.sx
Betreff: Re: [Gen-art] Gen-ART review of draft-drage-sipping-rfc3455bis-13

Roland,

Thanks for your responses. I think these are generally to the right directi=
on, I have commented below where I think some further discussion is needed.

On Apr 10, 2014, at 11:07 AM, R.Jesske@telekom.de wrote:

> Hi Marry,
> I'm really sorry, this mail slipped through my hands. And I didn't see an=
ything in the data tracker history. Since I'm the main Editor, it is my fau=
lt that this was not answered.
> It is true we cannot claim any speed if we do nothing. Again I'm Sorry.
>=20
> So here are my answers. For the Gen-review.
> So I have created a Version -14 which I can upload now. Please indicate i=
f I should do this or if I should wait for further comments?
>=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-drage-sipping-rfc3455bis-13
> Reviewer: Martin Thomson
> Review Date: 2014-02-27
> IETF LC End Date: 2014-03-14
> IESG Telechat date: (if known)
>=20
> Summary: I find it strange that this 3GPP document is being published on =
the standards track.  But since it's a -bis there is clearly precedent, and=
 it is otherwise sound.
>=20
> [RJ] Yes it is informal as RFC3455 is I'll change that.

It is published for informational according to the last call announcement, =
and I can't find any statement from the draft that this would be on the sta=
ndards track.

> Major issues:
>=20
> This document doesn't include enough information for me to some of the he=
aders.  For example, there isn't enough information in the document to allo=
w me to interpret the contents of cgi-3gpp:
>          cgi-3gpp     =3D "cgi-3gpp" EQUAL (token / quoted-string)
> (I pick on P-Access-Network-Info, because I'm somewhat familiar with it.)
>=20
> This can probably be addressed by the inclusion of appropriate normative =
references.  I seem to recall there being a 3GPP TS that covered at least s=
ome of these.
>=20
> [RJ] Below that section we have the text:
> The access-info MAY contain additional information relating to the access=
 network. The values for "cgi-3gpp", "utran-cell-id-3gpp",
>       "i-wlan-node-id", "dsl-location" and "ci-3gpp2", "ci-3gpp2-femto" a=
nd  "gstn-location" are defined in 3GPP TS 24.229
>=20
> Do we need more?

I think this is fine.

But would anyone mind if 24.229 was a normative reference? In my mind I nee=
d to read it to understand what to put into these attributes.

> Minor issues:
>=20
> RFC 4244 is now obsolete, see 7044.  (related nit: Change log entry #2 se=
ems quite defensive, unnecessarily so.  This document only needs to define =
P-Called-Party-ID, and reference History-Info as an alternative
> mechanism.)
>=20
> [RJ] Replaced
> [RJ] Due to your comment I have removed the whole text as follows:
> Additionally the P-Called-Party-ID
>       header field has been defined within 3GPP systems since release
>       5, and therefore it is realistic to expect implementations to be
>       already released to the field.  It is therefore considered that
>       replacement of the P-Called-Party-ID header field within 3GPP
>       systems causes more issues that it solves, and therefore the
>       update of RFC3455 <xref
>         target=3D"RFC3455"></xref> to remove the P-Called-Party-ID header=
 field
>       will not be addressed.  However it is recommended that any new
>       usage of this type of functionality should use the History-Info
>       header field defined in RFC 7044 <xref target=3D"RFC7044"></xref>ra=
ther than the P-Called-Party-ID header field

OK for me.

> Change log entry #5, mentions a shortcoming of 3455 (no registry for acce=
ss network types), but the draft does nothing about it.  It seems to be pro=
pagating the mistake it notes.
>=20
> [RJ] Yes I can agree this. so this seems a action for future.

Yes.

>=20
> A lot has happened since RFC 3455 was published.  The privacy considerati=
ons around the use of P-Access-Network-Info are unchanged from their pre-Ge=
opriv form.  In particular, I find the UA knowledge part to be problematic;=
 Geopriv definitions can probably help here.
>=20
> [RJ] sorry cannot do=20

I think a better approach would be to describe the issues, rather than try =
to change what the implementations do, if that is what you meant by using G=
eopriv definitions.

> S6.1 P-Associated-URI is a powerful linkability vector, which could be a =
far more serious privacy leak than the text implies.  The following seems l=
ike good advice, but is not sufficient:
>=20
>   An eavesdropper could possibly collect the list of identities a user
>   is registered.  This can have privacy implications.  To mitigate this
>   problem, this extension SHOULD only be used in a secured environment,
>   where encryption of SIP messages is provided either end-to-end or
>   hop-by-hop.
>=20
> You also have to trust the other end of the hop with the information.
> I think that's implicit, but probably needs to be stated.
>=20
> [RJ] I have addedthe following:
> And where a trustrelationship equivalent with that defined in RFC 3325 <x=
ref target=3D"RFC3325">between entities exist

This is good, but I'd be even more explicit. Maybe add "That is, the privac=
y of the user relies on the other entities in the session not disclosing in=
formation that they have learned about the user.

>=20
> S6.4  This claim sounds false to me:
>=20
>   However, there
>   are no security problems resulting from a UA inserting incorrect
>   information.  Networks providing services based on the information
>   carried in the P-Access-Network-Info header field will therefore need
>   to trust the UA sending the information.  A rogue UA sending false
>   access network information will do no more harm than to restrict the
>   user from using certain services.
>=20
> Any parameter whereby changing it can cause loss of service is likely to =
be true in the inverse.  The draft makes no claims that would make me belie=
ve otherwise.
>=20
> [RJ] Since we have the P-Access-Network-Info as header that is also set u=
p by the IMS entity P-CSCF with adding the network provided element there i=
s a difference in interpreting the header by Applications. Of course the ne=
twork provided information is trustful and can be used for sensitive servic=
es since the user provided information should only be used by services whic=
h are not sensitive.
>=20
> [RJ] Is this sufficient?

I feel that this may need more explanation. If you point was that the P-CSC=
F adds information that is trustworthy and leads to discovery of false info=
rmation planted by the rogue UA, then maybe we should be explicit about thi=
s.

Jari


From nobody Fri Apr 25 07:07:08 2014
Return-Path: <eric@notcom.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 E8A291A050E for <gen-art@ietfa.amsl.com>; Fri, 25 Apr 2014 07:07:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, 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 AIueZF6ADvuI for <gen-art@ietfa.amsl.com>; Fri, 25 Apr 2014 07:07:03 -0700 (PDT)
Received: from mail-yh0-f52.google.com (mail-yh0-f52.google.com [209.85.213.52]) by ietfa.amsl.com (Postfix) with ESMTP id E44711A04F8 for <gen-art@ietf.org>; Fri, 25 Apr 2014 07:07:02 -0700 (PDT)
Received: by mail-yh0-f52.google.com with SMTP id 29so3595813yhl.11 for <gen-art@ietf.org>; Fri, 25 Apr 2014 07:06:56 -0700 (PDT)
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=C6UuSJmF37b36gipDz5dbOmpcAsyfjFXoDSCAyuY34I=; b=aN2EQELCx19CZFUUtDGiOdAVJqSX0BgFHmUURVB8vN3S8UfJy9HrSF/i1YXytk0+FL ugz4ztSGB4zm0r8uEHEeFCQ0EL06znAb1o47Hr4K8HeN5n5hvzUd2nKJjU25mwFbPFmZ xgWkLTYpHRJFeEPzDeNKHjx0/Ca9fhdIuw5/4Z/ojWQPPMdISVw4aJ9R5GJfaZy1on1Z Kp2GoCRTxRmK8Nv4zAHEeSvyhxqAEbzym70lEITPFcx12arIIVYO1lvswx7LwipZQLLO E/KO+dGLA8eWZj3VNScJqt00Pp2n3nd523em1WfntWfdUP7mbtxGP7lCCjg6FHIBNtza Tuyg==
X-Gm-Message-State: ALoCoQkN32Yj+RZOfsVQAv0h+/H/weSKKPNl3BVH0N/NOSDEPdb+itDJKu2cCWseDNKaRam2Kq2Y
MIME-Version: 1.0
X-Received: by 10.236.126.43 with SMTP id a31mr2649504yhi.154.1398434816205; Fri, 25 Apr 2014 07:06:56 -0700 (PDT)
Received: by 10.170.60.5 with HTTP; Fri, 25 Apr 2014 07:06:56 -0700 (PDT)
In-Reply-To: <53598854.2010201@joelhalpern.com>
References: <53597772.6000401@nostrum.com> <53598854.2010201@joelhalpern.com>
Date: Fri, 25 Apr 2014 10:06:56 -0400
Message-ID: <CA+97oKPxMJC2zngqUwfRGCNXtP61rqsoRdCbhLAj+_30dZTVeg@mail.gmail.com>
From: Eric Osborne <eric@notcom.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/MdVtgjDK0QJHhSM3DKD5qOdz4ig
Cc: "mpls@ietf.org" <mpls@ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] [mpls] review: draft-ietf-mpls-extended-admin-group-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, 25 Apr 2014 14:07:06 -0000

Hi Joel-

  Thanks for the review.  On your minor issue:
---
 I believe it is more accurate to say that it is to be used "when a
node wishes to advertise colors for a link which are not represented
in the first 32 bits of the color mask."  The node may only wish to
advertise colors 7 and 60, but that will require the EAG.
---

I see your point, but I'm having trouble coming up with obvious text.
Deciding which colors are represented in a color mask is up to the
operator, which means it would have to say something like

"when a node wishes to advertise colors for a link which the operator
has defined to be outside the first 32 bits of the color mask".

but this would be the only use of 'color mask' in the document, and
it's not one I've seen used in any other docs around link coloring.

The whole sentence you refer to is:

" The EAG sub-TLV is used in addition to the Administrative Groups
when a node wishes to advertise more than 32 colors for a link."

If I rephrased it as

" The EAG sub-TLV is used in addition to the Administrative Groups
when an operator wants to make more than 32 colors available for
advertisement on a link"

would that do it?
s/wishes/wants/ while I'm here.



eric


On Thu, Apr 24, 2014 at 5:55 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-mpls-extended-admin-group-05
>     Extended Administrative Groups in MPLS-TE
> Reviewer: Joel M. Halpern
> Review Date: 24-April-2014
> IETF LC End Date: 06-May-2014
> IESG Telechat date: N/A
>
> Summary: This document is ready for publication as a Proposed Standards RFC
>
> Major issues: N/A
>
> Minor issues:
>     I believe that the description of when to use this EAG is slightly
> misleading.  The text says that EAG is to be used "when a node wishes to
> advertise more than 32 colors for a link."  I believe it is more accurate to
> say that it is to be used "when a node wishes to advertise colors for a link
> which are not represented in the first 32 bits of the color mask."  The node
> may only wish to advertise colors 7 and 60, but that will require the EAG.
>
> Nits/editorial comments: N/A
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From nobody Fri Apr 25 08:28:35 2014
Return-Path: <eric@notcom.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 8A7691A0639 for <gen-art@ietfa.amsl.com>; Fri, 25 Apr 2014 08:28:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, 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 8jmAGcmnWi_O for <gen-art@ietfa.amsl.com>; Fri, 25 Apr 2014 08:28:29 -0700 (PDT)
Received: from mail-yh0-f51.google.com (mail-yh0-f51.google.com [209.85.213.51]) by ietfa.amsl.com (Postfix) with ESMTP id E3DD71A0572 for <gen-art@ietf.org>; Fri, 25 Apr 2014 08:28:28 -0700 (PDT)
Received: by mail-yh0-f51.google.com with SMTP id f10so3699996yha.24 for <gen-art@ietf.org>; Fri, 25 Apr 2014 08:28:22 -0700 (PDT)
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=4/WSSr0/h/jO/uR3jN02snLwL6jRSw65AxfpYheld0Y=; b=U2p9GWWs2hH0bmoqbAHELhjsvXfc1YFDQYr2oedfGd4/GzoabyhWtsyd0jpUtA5CK4 ccci7ltJPSOIW8MpZeRZt1CcyZVeyp9OEFn6LdjPiMwTIRs8XNzTQ63drkYTBWri3laC FESH77pKTVXmL/1Ew1RlC5im8hGB1oK+UuiR616j7YP/dPOmPIjtoYEPQs4fKXXXuc3a bsZ3JNHroPt2w4j6Wk++YfyUlSAgsk1/NRTw1wxWcQZyzivoqfaip4C+BiQeCa24FHnk menEpiUghUMuJg6EerVJW40/bnr9PqodoPfUnwMcsuv1lDdmbtd97g4+eXmmHUEXYFbs jzsg==
X-Gm-Message-State: ALoCoQm+R5F4k+LklJV0Ehp735aUs5xIIyE3V6YcBykYFsyyd2RJDscHIQffME1aTFvYjGtkc2r3
MIME-Version: 1.0
X-Received: by 10.236.20.194 with SMTP id p42mr12617329yhp.56.1398439702388; Fri, 25 Apr 2014 08:28:22 -0700 (PDT)
Received: by 10.170.60.5 with HTTP; Fri, 25 Apr 2014 08:28:22 -0700 (PDT)
In-Reply-To: <535A7903.2070704@joelhalpern.com>
References: <53597772.6000401@nostrum.com> <53598854.2010201@joelhalpern.com> <CA+97oKPxMJC2zngqUwfRGCNXtP61rqsoRdCbhLAj+_30dZTVeg@mail.gmail.com> <535A7903.2070704@joelhalpern.com>
Date: Fri, 25 Apr 2014 11:28:22 -0400
Message-ID: <CA+97oKPbtmSz8DLP8v6Xt3wwVNQdC7Qib0duj2orgyXwstGaXw@mail.gmail.com>
From: Eric Osborne <eric@notcom.com>
To: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/xaT9boqoScTnhjs8ya-kGN9ApLE
Cc: "mpls@ietf.org" <mpls@ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] [mpls] review: draft-ietf-mpls-extended-admin-group-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, 25 Apr 2014 15:28:31 -0000

Works for me.
So

" The EAG sub-TLV is used in addition to the Administrative Groups
when an operator wants to make more than 32 colors available for
advertisement in a network"

I had gone back and forth with Adrian on language to scope this to a
single LSDB, so as to avoid the discussion of signaling EAG desire in
RSVP or PCEP.  I don't want to add that sort of disclaimer here too,
as it makes the sentence clunky and unweildy.



eric


On Fri, Apr 25, 2014 at 11:02 AM, Joel Halpern Direct
<jmh.direct@joelhalpern.com> wrote:
> What if instead of "on the link" it is simoply "in the network".  This
> recommend the use of EAG whenever the operators is using more than 32 colors
> across the link.  It thus actually better aligns with avoiding the
> under-claiming issue by suggesting that operators should use the EAG if they
> have more than 32 candidate colors.
>
> Yours,
> Joel
>
> PS: substituting wants for wishes is probably reasonable.  If we talk about
> network-wide you might even be able to us "intends".
>
>
> On 4/25/14, 10:06 AM, Eric Osborne wrote:
>>
>> Hi Joel-
>>
>>    Thanks for the review.  On your minor issue:
>> ---
>>   I believe it is more accurate to say that it is to be used "when a
>> node wishes to advertise colors for a link which are not represented
>> in the first 32 bits of the color mask."  The node may only wish to
>> advertise colors 7 and 60, but that will require the EAG.
>> ---
>>
>> I see your point, but I'm having trouble coming up with obvious text.
>> Deciding which colors are represented in a color mask is up to the
>> operator, which means it would have to say something like
>>
>> "when a node wishes to advertise colors for a link which the operator
>> has defined to be outside the first 32 bits of the color mask".
>>
>> but this would be the only use of 'color mask' in the document, and
>> it's not one I've seen used in any other docs around link coloring.
>>
>> The whole sentence you refer to is:
>>
>> " The EAG sub-TLV is used in addition to the Administrative Groups
>> when a node wishes to advertise more than 32 colors for a link."
>>
>> If I rephrased it as
>>
>> " The EAG sub-TLV is used in addition to the Administrative Groups
>> when an operator wants to make more than 32 colors available for
>> advertisement on a link"
>>
>> would that do it?
>> s/wishes/wants/ while I'm here.
>>
>>
>>
>> eric
>>
>>
>> On Thu, Apr 24, 2014 at 5:55 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-mpls-extended-admin-group-05
>>>      Extended Administrative Groups in MPLS-TE
>>> Reviewer: Joel M. Halpern
>>> Review Date: 24-April-2014
>>> IETF LC End Date: 06-May-2014
>>> IESG Telechat date: N/A
>>>
>>> Summary: This document is ready for publication as a Proposed Standards
>>> RFC
>>>
>>> Major issues: N/A
>>>
>>> Minor issues:
>>>      I believe that the description of when to use this EAG is slightly
>>> misleading.  The text says that EAG is to be used "when a node wishes to
>>> advertise more than 32 colors for a link."  I believe it is more accurate
>>> to
>>> say that it is to be used "when a node wishes to advertise colors for a
>>> link
>>> which are not represented in the first 32 bits of the color mask."  The
>>> node
>>> may only wish to advertise colors 7 and 60, but that will require the
>>> EAG.
>>>
>>> Nits/editorial comments: N/A
>>>
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls


From nobody Fri Apr 25 08:39:46 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 725E51A0342; Fri, 25 Apr 2014 08:39:44 -0700 (PDT)
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 QmpUyYCYrI25; Fri, 25 Apr 2014 08:39:42 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 180FD1A0312; Fri, 25 Apr 2014 08:39:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id ED21D1C0A7D; Fri, 25 Apr 2014 08:39:35 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (74-84-92-146.client.mchsi.com [74.84.92.146]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 5D9921C0878; Fri, 25 Apr 2014 08:39:35 -0700 (PDT)
Message-ID: <535A81AF.3030500@joelhalpern.com>
Date: Fri, 25 Apr 2014 11:39:27 -0400
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.4.0
MIME-Version: 1.0
To: Eric Osborne <eric@notcom.com>
References: <53597772.6000401@nostrum.com>	<53598854.2010201@joelhalpern.com>	<CA+97oKPxMJC2zngqUwfRGCNXtP61rqsoRdCbhLAj+_30dZTVeg@mail.gmail.com>	<535A7903.2070704@joelhalpern.com> <CA+97oKPbtmSz8DLP8v6Xt3wwVNQdC7Qib0duj2orgyXwstGaXw@mail.gmail.com>
In-Reply-To: <CA+97oKPbtmSz8DLP8v6Xt3wwVNQdC7Qib0duj2orgyXwstGaXw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/0IJRD8d5DDY0HX9bCVCvGHpnegM
Cc: "mpls@ietf.org" <mpls@ietf.org>, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] [mpls] review: draft-ietf-mpls-extended-admin-group-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, 25 Apr 2014 15:39:44 -0000

That works for me.
Thank you Eric.
Yours,
Joel

On 4/25/14, 11:28 AM, Eric Osborne wrote:
> Works for me.
> So
>
> " The EAG sub-TLV is used in addition to the Administrative Groups
> when an operator wants to make more than 32 colors available for
> advertisement in a network"
>
> I had gone back and forth with Adrian on language to scope this to a
> single LSDB, so as to avoid the discussion of signaling EAG desire in
> RSVP or PCEP.  I don't want to add that sort of disclaimer here too,
> as it makes the sentence clunky and unweildy.
>
>
>
> eric
>
>
> On Fri, Apr 25, 2014 at 11:02 AM, Joel Halpern Direct
> <jmh.direct@joelhalpern.com> wrote:
>> What if instead of "on the link" it is simoply "in the network".  This
>> recommend the use of EAG whenever the operators is using more than 32 colors
>> across the link.  It thus actually better aligns with avoiding the
>> under-claiming issue by suggesting that operators should use the EAG if they
>> have more than 32 candidate colors.
>>
>> Yours,
>> Joel
>>
>> PS: substituting wants for wishes is probably reasonable.  If we talk about
>> network-wide you might even be able to us "intends".
>>
>>
>> On 4/25/14, 10:06 AM, Eric Osborne wrote:
>>>
>>> Hi Joel-
>>>
>>>     Thanks for the review.  On your minor issue:
>>> ---
>>>    I believe it is more accurate to say that it is to be used "when a
>>> node wishes to advertise colors for a link which are not represented
>>> in the first 32 bits of the color mask."  The node may only wish to
>>> advertise colors 7 and 60, but that will require the EAG.
>>> ---
>>>
>>> I see your point, but I'm having trouble coming up with obvious text.
>>> Deciding which colors are represented in a color mask is up to the
>>> operator, which means it would have to say something like
>>>
>>> "when a node wishes to advertise colors for a link which the operator
>>> has defined to be outside the first 32 bits of the color mask".
>>>
>>> but this would be the only use of 'color mask' in the document, and
>>> it's not one I've seen used in any other docs around link coloring.
>>>
>>> The whole sentence you refer to is:
>>>
>>> " The EAG sub-TLV is used in addition to the Administrative Groups
>>> when a node wishes to advertise more than 32 colors for a link."
>>>
>>> If I rephrased it as
>>>
>>> " The EAG sub-TLV is used in addition to the Administrative Groups
>>> when an operator wants to make more than 32 colors available for
>>> advertisement on a link"
>>>
>>> would that do it?
>>> s/wishes/wants/ while I'm here.
>>>
>>>
>>>
>>> eric
>>>
>>>
>>> On Thu, Apr 24, 2014 at 5:55 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-mpls-extended-admin-group-05
>>>>       Extended Administrative Groups in MPLS-TE
>>>> Reviewer: Joel M. Halpern
>>>> Review Date: 24-April-2014
>>>> IETF LC End Date: 06-May-2014
>>>> IESG Telechat date: N/A
>>>>
>>>> Summary: This document is ready for publication as a Proposed Standards
>>>> RFC
>>>>
>>>> Major issues: N/A
>>>>
>>>> Minor issues:
>>>>       I believe that the description of when to use this EAG is slightly
>>>> misleading.  The text says that EAG is to be used "when a node wishes to
>>>> advertise more than 32 colors for a link."  I believe it is more accurate
>>>> to
>>>> say that it is to be used "when a node wishes to advertise colors for a
>>>> link
>>>> which are not represented in the first 32 bits of the color mask."  The
>>>> node
>>>> may only wish to advertise colors 7 and 60, but that will require the
>>>> EAG.
>>>>
>>>> Nits/editorial comments: N/A
>>>>
>>>> _______________________________________________
>>>> mpls mailing list
>>>> mpls@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mpls


From nobody Fri Apr 25 09:53:48 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 935B51A0268 for <gen-art@ietfa.amsl.com>; Fri, 25 Apr 2014 09:53:44 -0700 (PDT)
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 87iR1a7qZuVT for <gen-art@ietfa.amsl.com>; Fri, 25 Apr 2014 09:53:41 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 665EE1A055D for <gen-art@ietf.org>; Fri, 25 Apr 2014 09:53:41 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1WdjNO-0003oQ-VV; Fri, 25 Apr 2014 17:53:29 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Fri, 25 Apr 2014 17:53:22 +0100
Message-Id: <1398444802.15324.27829.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/HPgpJoRdkIgToGMFaRGQC9gxESA
Cc: draft-pal-eidr-urn.all@tools.ietf.org
Subject: [Gen-art] Gen-art LC review of draft-pal-eidr-urn-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, 25 Apr 2014 16:53:44 -0000

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

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

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

Document: draft-pal-eidr-urn-01.txt
Reviewer: Elwyn Davies
Review Date: 25 April 2014
IETF LC End Date: 16 May 2014
IESG Telechat date: (if known) -

Summary: Ready with very minor nits.

Query/Suggestion:  I don't know if creating IANA registries for
EIDR-PREFIXes and corresponding EIDR-SUFFIX types has been considered.
If additional prefixes are likely to have the same suffix format (i.e.,
just fulfilling a need for more space), then considerable future effort
could be avoided by using expert review by someone from EIRA or SMPTE to
add new prefixes.  Of course it may be that new prefixes are not likely
to be needed too often and anyway would need a new suffix format, in
which case this is irrelevant.  Just a thought!

Major issues:
None

Minor issues:
None

Nits/editorial comments:
Header: Shouuld spcify the intended status (which is Informational
according to the tracker).

Abstact: s/global/globally/

s1, para 2: s/time of registration/the time of registration/

s2 title and para 1: It would be more appropriate to title this section 
   'Completed URN Namespace Definition Template'
and make para 1 something like:
   The namespece definition according to the template in [RFC3406] is as
follows:

s2, example:
The example http://doi.org/10.5240/68DD-341E-03EE-4BB8-1761-Q is a
working EIDR DOI for the movie "Superman Returns".  Whilst this
illustrates the namespace very well, it is normally good to use a dummy
example to avoid any downstream issues (I don't see that the owners of
the film would complain, but other might look on it as favouritism). 
Would it be possible to create a dummy working EIDR that could be used
in the RFC?




From nobody Mon Apr 28 03:05:51 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 A9E671A0966 for <gen-art@ietfa.amsl.com>; Mon, 28 Apr 2014 03:05:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.25
X-Spam-Level: 
X-Spam-Status: No, score=-3.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] 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 GO7jw_cVGV4u for <gen-art@ietfa.amsl.com>; Mon, 28 Apr 2014 03:05:46 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id D83BF1A0977 for <gen-art@ietf.org>; Mon, 28 Apr 2014 03:05:45 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsAFABknXlPGmAcV/2dsb2JhbABZgkIjIU9XqlwKAQEBAQEEAZB7gSUdAYc4gQ4WdIInAQEDEhtMEgEVBw5WJgEEDg0BGYgfAQybZ64dF4Vahw2BQSARgjUPZ4EVBJpGhUuLWYMxgis
X-IronPort-AV: E=Sophos; i="4.97,943,1389762000"; d="scan'208,217"; a="59879129"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 28 Apr 2014 06:05:44 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 28 Apr 2014 05:49:57 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0174.001; Mon, 28 Apr 2014 12:05:43 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: GenART review of draft-ietf-dhc-dhcpv4-over-dhcpv6
Thread-Index: Ac9iyWgu2uThFl0JTuWHJ0qB7blhmg==
Date: Mon, 28 Apr 2014 10:05:43 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C7C8BA4@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_9904FB1B0159DA42B0B887B7FA8119CA5C7C8BA4AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/1G4vA30JS4VLWoTyGBCLkN6dJDs
Cc: "draft-ietf-dhc-dhcpv4-over-dhcpv6.all@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6.all@tools.ietf.org>
Subject: [Gen-art] GenART review of draft-ietf-dhc-dhcpv4-over-dhcpv6
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, 28 Apr 2014 10:05:48 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C7C8BA4AZFFEXMB04globa_
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-dhc-dhcpv4-over-dhcpv6-07.txt

Reviewer: Dan Romascanu

Review Date: 4/28/14

IETF LC End Date: 4/29/14

IESG Telechat date:



Summary: Ready, with a few small issues



Major issues: None



Minor issues:



1.       In section 10:


   When the server receives a DHCPv4-query message from a client, it
   searches for the DHCPv4 Message option.  The server discards the
   packet without this option.  The server MAY notify an administrator
   about the receipt of a malformed packet.  The mechanism for this
   notification is out of scope for this document.

It would be good to clarify the behavior of the server beyond possibly noti=
fying an administrator at the receipt of a malformed packet. Is the packet =
discarded?


2.       I believe that [RFC3527] should rather be a Normative Reference. E=
ven if the use of a Link Selection sub-option is under a 'may' - it cannot =
be implemented unless RFC3527 is read.





Nits/editorial comments:



In the introduction there is reference to the 'DHCP leasequery'. Actually i=
n RFC 4388 one can find Leasequery either capitalized (in the title) or ALL=
-CAPS in the text.






--_000_9904FB1B0159DA42B0B887B7FA8119CA5C7C8BA4AZFFEXMB04globa_
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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size: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";}
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 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1787842950;
	mso-list-type:hybrid;
	mso-list-template-ids:2142000282 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-dhc-d=
hcpv4-over-dhcpv6-07.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 4/28/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 4/29/14<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: Ready, with a few small issues<o:p></o:p=
></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major issues: None<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor issues:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</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 10: <o:p></o:p>=
</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; When the server receives a DHCPv4-query=
 message from a client, it<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; searches for the DHCPv4 Message option.=
&nbsp; The server discards the<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; packet without this option.&nbsp; The s=
erver MAY notify an administrator<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; about the receipt of a malformed packet=
.&nbsp; The mechanism for this<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; notification is out of scope for this d=
ocument.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">It would be good to clarify the behavior of the serv=
er beyond possibly notifying an administrator at the receipt of a malformed=
 packet. Is the packet discarded?
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 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>I believe that [RFC3527] s=
hould rather be a Normative Reference. Even if the use of a Link Selection =
sub-option is under a &#8216;may&#8217; &#8211; it cannot be implemented un=
less RFC3527 is read.
<o:p></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"MsoPlainText">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">In the introduction there is reference to the &#8=
216;DHCP leasequery&#8217;. Actually in RFC 4388 one can find Leasequery ei=
ther capitalized (in the title) or ALL-CAPS in the text.
<o:p></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_9904FB1B0159DA42B0B887B7FA8119CA5C7C8BA4AZFFEXMB04globa_--


From nobody Mon Apr 28 05:59:14 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 16A481A078F for <gen-art@ietfa.amsl.com>; Mon, 28 Apr 2014 05:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 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.651] 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 Y4-3sWcdn974 for <gen-art@ietfa.amsl.com>; Mon, 28 Apr 2014 05:59:11 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 7F1D51A047C for <gen-art@ietf.org>; Mon, 28 Apr 2014 05:59:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1398689950; d=isode.com; s=selector; i=@isode.com; bh=ONOVXf+oc9aNtxo+QmuMYQoADN770+gKoK+ZIBlBjDk=; 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=fnC435RwHs8XEk9hC0GQsN+Rx44tDQIdSaiw/YTHk96E1QiH3n6efJI/ZnGXNrhPP5Nuk6 tiZXqdGLOgzI9extolw5vzQNH1WLYTaVnzMSsjNEvXGqTjJyKyiE6JucZz+zkGOM38UTf2 QGTQM+ikM3S3mNhuVV1Lk/n2fZy9bFs=;
Received: from [172.16.1.29] (richard.isode.com [62.3.217.249])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <U15QnQBYHouL@waldorf.isode.com>; Mon, 28 Apr 2014 13:59:09 +0100
Message-ID: <535E50C1.2060100@isode.com>
Date: Mon, 28 Apr 2014 13:59:45 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
To: General Area Review Team <gen-art@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/DolLAym0eJdFxFM8ygq1pZ_GR4g
Cc: draft-ietf-salud-alert-info-urns.all@tools.ietf.org
Subject: [Gen-art] Gen-art LC review of draft-ietf-salud-alert-info-urns-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: Mon, 28 Apr 2014 12:59: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-salud-alert-info-urns-12.txt
Reviewer: Alexey Melnikov
Review Date: 27 April 2014
IETF LC End Date: 25 April 2014
IESG Telechat date: (if known) N/A

Summary: Ready with nits/questions.


Major issues:
None

Minor issues:

13.  User Agent Behaviour

    The User Agent (UA) MUST produce a reasonable rendering regardless of
    the combination of URIs (of any schemes) in the Alert-Info header
    field.

This MUST is not well defined to be implementable. How can conformance 
or violation of this requirement can be tested? I suggest you avoid 
using RFC 2119 language here.


Has this been submitted to the urn-nid@apps.ietf.org mailing list for 2 
weeks review? (as per RFC 3406)


Nits/editorial comments:

  "REQ-4: has been deleted.  To avoid confusion, the number will not be 
reused".

  I find this to be rather unusual. Are these requirements used in RFPs?


In Section 7:

date              = [CC] YY [ "-" MM ["-" DD] ]


  Is there a need for having 2 octet years? Are you trying to save some 
bytes here at the expense of extra (albeit minor) complexity?


From nobody Mon Apr 28 07:20:59 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 DE88D1A0A18; Mon, 28 Apr 2014 07:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.952
X-Spam-Level: 
X-Spam-Status: No, score=-4.952 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_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 JPjx954n08Zr; Mon, 28 Apr 2014 07:20:40 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id DD51B1A047E; Mon, 28 Apr 2014 07:20:39 -0700 (PDT)
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com [10.106.48.159]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3SEKZxV016338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Apr 2014 10:20:37 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s3SEKZxV016338
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1398694837; bh=ifxQuMJFdVKke3no56uo8mXGgoI=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=db0MLgTiIUMLR66yqA5EFBQEm9S+RSrDcLf5EzY9oX3hQ/+xcLBCBTv+9tAs+Vot3 p2Y9MP/Sevioz1sT04Vz8G8ZN59T/waqhDC2pD4mpuI8pmM8Me2eXogG5vyFr3mntF 2YcTMaE69Q3mfkAyJWCKb2OG5PVyWyRs9c/f1Suo=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s3SEKZxV016338
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd55.lss.emc.com (RSA Interceptor); Mon, 28 Apr 2014 10:20:26 -0400
Received: from mxhub35.corp.emc.com (mxhub35.corp.emc.com [10.254.93.83]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3SEKPDB001656 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 28 Apr 2014 10:20:26 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub35.corp.emc.com ([::1]) with mapi; Mon, 28 Apr 2014 10:20:25 -0400
From: "Black, David" <david.black@emc.com>
To: "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "zali@cisco.com" <zali@cisco.com>, "nobo@cisco.com" <nobo@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Mon, 28 Apr 2014 10:20:23 -0400
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Index: Ac9i7PyERuk5jZsyQOKSHRHy2Ij/Lw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@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: mailusrhubprd52.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/-WtS-Zz9MdmvMl4J94jhriDCiRo
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-18
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, 28 Apr 2014 14:20:46 -0000

The -18 version of this draft responds to all of the comments in the
Gen-ART review of -17, including the request for coordination w/the
OPS area, although I wasn't exactly expecting that to occur on the
main IETF list.

The -18 version is ready with one small nit - The following text has
been added to the introduction:

   This memo does not define a compliance requirement for a system that=09
   only implements BFD version 0. This is a reflection of a considered=09
   and deliberate decision by the BFD WG.

An explanation of the rationale for that decision would help - I suggest
adding the following text and a suitable reference to the end of the text
above:
 =20
   because the BFD version 0 protocol may deadlock and hence SHOULD NOT
   be used, as explained further in [RFCxxxx].

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Wednesday, April 16, 2014 7:31 PM
> To: tnadeau@lucidvision.com; zali@cisco.com; nobo@cisco.com; General Area
> Review Team (gen-art@ietf.org)
> Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> Subject: Gen-ART review of draft-ietf-bfd-mib-17
>=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-bfd-mib-17
> Reviewer: David L. Black
> Review Date: April 16, 2014
> IETF LC End Date: April 28, 2014
>=20
> Summary: This draft is on the right track, but has open issues
> 		described in the review.
>=20
> This draft is a MIB module for the BFD protocol, which is an important lo=
w-
> level routing protocol.  The draft is reasonable for a MIB draft; one nee=
ds
> to go read the protocol documents to understand how the protocol works, a=
nd
> significant portions of the text are derived from the usual MIB "boilerpl=
ate"
> as one would expect.  The "Brief Description of MIB Objects" is indeed
> brief, but reasonable.  The shepherd writeup indicates that there are
> multiple implementations.
>=20
> Major issues:
>=20
> This MIB contains many writable objects, so the authors should
> take note of the IESG statement on writable MIB modules:
>=20
> 	http://www.ietf.org/iesg/statement/writable-mib-module.html
>=20
> I did not see this mentioned in the shepherd writeup.  If the OPS Area
> has not been consulted, I strongly suggest doing so during IETF Last
> Call, e.g., starting with Benoit Claise (AD).
>=20
> Minor issues:
>=20
> The security considerations section includes considerations for
> unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus,
> but omits the corresponding considerations for bfdAdminStatus and
> bfdSessNotificationsEnable.  Both of the latter objects are global,
> so significant damage can be inflicted via these objects with a
> small number of unauthorized modifications, so they need to be
> included in the first list of sensitive objects.
>=20
> I suggest that the authors recheck the entire MIB to ensure that
> every object or table that should be included in the security
> considerations section is appropriately included.
>=20
> Also, as a General Variable, would bfdSessNotificationsEnable be better
> named bfdNotificationsEnable, as it's not in the BFD Session Table?
>=20
> I did not see a compliance requirement for a system that only
> implements BFD protocol version 0.  That absence should at least be
> mentioned somewhere.  For example, if this reflects a considered and
> deliberate decision by the WG, that should be mentioned in the
> introduction.
>=20
> Nits/editorial comments:
>=20
> In the security considerations for authentication-related objects:
>=20
> OLD
>    In order for these sensitive information
>    from being improperly accessed, implementers MAY wish to disallow
>    access to these objects.
> NEW
>    In order to prevent this sensitive information
>    from being improperly accessed, implementers MAY disallow
>    access to these objects.
>=20
> idnits 2.13.01 found a truly minor nit that should be corrected when
> the draft is next revised:
>=20
>   =3D=3D Outdated reference: A later version (-05) exists of
>      draft-ietf-bfd-tc-mib-04
>=20
> it also generated a warning that probably does not reflect an actual prob=
lem:
>=20
>   -- The document seems to lack a disclaimer for pre-RFC5378 work, but ma=
y
>      have content which was first submitted before 10 November 2008.  If =
you
>      have contacted all the original authors and they are all willing to =
grant
>      the BCP78 rights to the IETF Trust, then this is fine, and you can i=
gnore
>      this comment.  If not, you may need to add the pre-RFC5378 disclaime=
r.
>      (See the Legal Provisions document at
>      http://trustee.ietf.org/license-info for more information.)
>=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 nobody Mon Apr 28 07:32:38 2014
Return-Path: <worley@ariadne.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 160391A6F05 for <gen-art@ietfa.amsl.com>; Mon, 28 Apr 2014 07:32:35 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 9V5eDiR3FroA for <gen-art@ietfa.amsl.com>; Mon, 28 Apr 2014 07:32:31 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 7A7361A6F07 for <gen-art@ietf.org>; Mon, 28 Apr 2014 07:32:31 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta12.westchester.pa.mail.comcast.net with comcast id vQU51n0081vXlb85CSYWvU; Mon, 28 Apr 2014 14:32:30 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta17.westchester.pa.mail.comcast.net with comcast id vSYW1n0061KKtkw3dSYWwN; Mon, 28 Apr 2014 14:32:30 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s3SEWThx000677; Mon, 28 Apr 2014 10:32:29 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s3SEWTur000676; Mon, 28 Apr 2014 10:32:29 -0400
Date: Mon, 28 Apr 2014 10:32:29 -0400
Message-Id: <201404281432.s3SEWTur000676@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-reply-to: <535E50C1.2060100@isode.com> (alexey.melnikov@isode.com)
References: <535E50C1.2060100@isode.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1398695550; bh=F2scQd4ytnlgwvvycTOXn9fm5lL54/wCV/PKn760NYU=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=My/6BA6w8HkskJvY4w5gKfod4Z6csiCaGkuvmnjqabEcASKNN1pxnOvMv0xz1cH9F tfMRRHInvQmU15rAdtqdQdH3wOisFcTSQW33lM51k1OyDSqGUANziO2+AgirHNoHZF C7+hlN2CI327lYYerz6nOtklIVQPC4gcp4yRpPUA3TUC2RqTymYRWeiONnKYMjvZV3 DsrlSBRZ9eAj4Ux+Px17/rkydGRTCHExGzriqjr0UMPM4GI2LlCKNf13HTQjYJl6IW thh0oB5Cm1Xa/sWl3j8mFbt/b2q9GH6mALHFINg1N14Y+QRz6ROAxSJ0ELCwUM7vYv DrI1mGmFKdU6A==
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/yrJl5dcD5lKBcbm2hgqy_ice5KQ
Cc: draft-ietf-salud-alert-info-urns.all@tools.ietf.org, gen-art@ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-salud-alert-info-urns-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: Mon, 28 Apr 2014 14:32:35 -0000

This item:

> Has this been submitted to the urn-nid@apps.ietf.org mailing list for 2 
> weeks review? (as per RFC 3406)

has been taken care of.  The urn-nid review started 3 Oct 2013:
http://www.ietf.org/mail-archive/web/urn-nid/current/msg01218.html

Dale


From nobody Mon Apr 28 10:46:38 2014
Return-Path: <nobo@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 042971A6F46; Mon, 28 Apr 2014 10:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.152
X-Spam-Level: 
X-Spam-Status: No, score=-110.152 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.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, 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 p7-YSXwmlJCl; Mon, 28 Apr 2014 10:46:31 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id E62E71A6F54; Mon, 28 Apr 2014 10:46:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6446; q=dns/txt; s=iport; t=1398707190; x=1399916790; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=JyCIPF2EoPy9QGYyxwF75PYSuSCAvEUjofgznu3yey0=; b=aXuU9KPUVVM1bf4PfNkZTps9C5+lI7gec250ERi64ySPEhWfgza9BuyP 33/j5tLRGh+am9hokuD4MmSM6bZ0FuWLIEx2f6xaM2hpKlbpwF6vK8dX2 EFQ9A5sqaPCRHuIq9ooWx6IrXHcdXUqBnVapSXGfRQ9LJl/7tbTDvmu6i o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAHqTXlOtJV2b/2dsb2JhbABWA4JlIU9XxGmBGRZ0giUBAQEDAXkMBAIBCBEDAQEBCx0HMhQJCAEBBAENBQgBiDAIAQzIMheMZ4FBIRACBQYLgxOBFQSIfziLY4UskSSDMYIr
X-IronPort-AV: E=Sophos;i="4.97,945,1389744000"; d="scan'208";a="39406939"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP; 28 Apr 2014 17:46:28 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3SHkS6e015443 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 28 Apr 2014 17:46:28 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Mon, 28 Apr 2014 12:46:28 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Black, David" <david.black@emc.com>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "Zafar Ali (zali)" <zali@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Index: Ac9i7PyERuk5jZsyQOKSHRHy2Ij/LwAG2CxA
Date: Mon, 28 Apr 2014 17:46:28 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.212.215]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/_EREGvLmANystzuB4my66JgZFeA
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-18
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, 28 Apr 2014 17:46:33 -0000

Hi David,

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Monday, April 28, 2014 10:20 AM
> To: tnadeau@lucidvision.com; Zafar Ali (zali); Nobo Akiya (nobo); General
> Area Review Team (gen-art@ietf.org)
> Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
>=20
> The -18 version of this draft responds to all of the comments in the Gen-=
ART
> review of -17, including the request for coordination w/the OPS area,
> although I wasn't exactly expecting that to occur on the main IETF list.

Thanks, they were very good comments.

>=20
> The -18 version is ready with one small nit - The following text has been
> added to the introduction:
>=20
>    This memo does not define a compliance requirement for a system that
>=20
>    only implements BFD version 0. This is a reflection of a considered
>    and deliberate decision by the BFD WG.
>=20
> An explanation of the rationale for that decision would help - I suggest
> adding the following text and a suitable reference to the end of the text
> above:
>=20
>    because the BFD version 0 protocol may deadlock and hence SHOULD NOT
>    be used, as explained further in [RFCxxxx].

Unfortunately the problem with BFD version 0 is not documented in any RFCs,=
 and MIB is probably not the right place to start this documentation either=
. If this should be documented in a RFC, possibly a new info document or ra=
ise errata on RFC5880 ... I'm not sure what would be a reasonable/recommend=
ed path here. In any case, my vote for the MIB document(s) is to keep the c=
urrent text to proceed. Would that be ok with you?

-Nobo

>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Wednesday, April 16, 2014 7:31 PM
> > To: tnadeau@lucidvision.com; zali@cisco.com; nobo@cisco.com; General
> > Area Review Team (gen-art@ietf.org)
> > Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> > Subject: Gen-ART review of draft-ietf-bfd-mib-17
> >
> > I am the assigned Gen-ART 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-bfd-mib-17
> > Reviewer: David L. Black
> > Review Date: April 16, 2014
> > IETF LC End Date: April 28, 2014
> >
> > Summary: This draft is on the right track, but has open issues
> > 		described in the review.
> >
> > This draft is a MIB module for the BFD protocol, which is an important
> > low- level routing protocol.  The draft is reasonable for a MIB draft;
> > one needs to go read the protocol documents to understand how the
> > protocol works, and significant portions of the text are derived from t=
he
> usual MIB "boilerplate"
> > as one would expect.  The "Brief Description of MIB Objects" is indeed
> > brief, but reasonable.  The shepherd writeup indicates that there are
> > multiple implementations.
> >
> > Major issues:
> >
> > This MIB contains many writable objects, so the authors should take
> > note of the IESG statement on writable MIB modules:
> >
> > 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> >
> > I did not see this mentioned in the shepherd writeup.  If the OPS Area
> > has not been consulted, I strongly suggest doing so during IETF Last
> > Call, e.g., starting with Benoit Claise (AD).
> >
> > Minor issues:
> >
> > The security considerations section includes considerations for
> > unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus,
> > but omits the corresponding considerations for bfdAdminStatus and
> > bfdSessNotificationsEnable.  Both of the latter objects are global, so
> > significant damage can be inflicted via these objects with a small
> > number of unauthorized modifications, so they need to be included in
> > the first list of sensitive objects.
> >
> > I suggest that the authors recheck the entire MIB to ensure that every
> > object or table that should be included in the security considerations
> > section is appropriately included.
> >
> > Also, as a General Variable, would bfdSessNotificationsEnable be
> > better named bfdNotificationsEnable, as it's not in the BFD Session Tab=
le?
> >
> > I did not see a compliance requirement for a system that only
> > implements BFD protocol version 0.  That absence should at least be
> > mentioned somewhere.  For example, if this reflects a considered and
> > deliberate decision by the WG, that should be mentioned in the
> > introduction.
> >
> > Nits/editorial comments:
> >
> > In the security considerations for authentication-related objects:
> >
> > OLD
> >    In order for these sensitive information
> >    from being improperly accessed, implementers MAY wish to disallow
> >    access to these objects.
> > NEW
> >    In order to prevent this sensitive information
> >    from being improperly accessed, implementers MAY disallow
> >    access to these objects.
> >
> > idnits 2.13.01 found a truly minor nit that should be corrected when
> > the draft is next revised:
> >
> >   =3D=3D Outdated reference: A later version (-05) exists of
> >      draft-ietf-bfd-tc-mib-04
> >
> > it also generated a warning that probably does not reflect an actual
> problem:
> >
> >   -- The document seems to lack a disclaimer for pre-RFC5378 work, but
> may
> >      have content which was first submitted before 10 November 2008.  I=
f
> you
> >      have contacted all the original authors and they are all willing t=
o grant
> >      the BCP78 rights to the IETF Trust, then this is fine, and you can=
 ignore
> >      this comment.  If not, you may need to add the pre-RFC5378 disclai=
mer.
> >      (See the Legal Provisions document at
> >      http://trustee.ietf.org/license-info for more information.)
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer EMC Corporation, 176 South St.,
> > Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From nobody Mon Apr 28 23:00:40 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 4CEEA1A8876; Mon, 28 Apr 2014 23:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.352
X-Spam-Level: 
X-Spam-Status: No, score=-3.352 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_LOW=-0.7, RP_MATCHES_RCVD=-0.651, 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 TGSTr96EXk8U; Mon, 28 Apr 2014 23:00:31 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 269D91A883C; Mon, 28 Apr 2014 23:00:30 -0700 (PDT)
Received: from maildlpprd05.lss.emc.com (maildlpprd05.lss.emc.com [10.253.24.37]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3T60QPg008071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Apr 2014 02:00:28 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com s3T60QPg008071
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1398751228; bh=cAqupTYVpHhHWClD9b5xnOOQOIg=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=W7VZGD6Y738hFaqZHi2lCPSt5KAMLiXZbmpNiC3fCpDcHq3Z/ZNbOwzPQSLeYq7Hb i8XXPQKDVZdiaaP7MAa/vZIifhaYbOoyPoDq9Ge6XzNZMnx9UWEXWjql1YImBSMn0H V7wncUiOuUCSKdGO6fxYDcEuegqm7BI7WQ9av73E=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com s3T60QPg008071
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd05.lss.emc.com (RSA Interceptor); Tue, 29 Apr 2014 02:00:14 -0400
Received: from mxhub15.corp.emc.com (mxhub15.corp.emc.com [128.222.70.236]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3T60C17030349 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 29 Apr 2014 02:00:13 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub15.corp.emc.com ([128.222.70.236]) with mapi; Tue, 29 Apr 2014 02:00:12 -0400
From: "Black, David" <david.black@emc.com>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "Zafar Ali (zali)" <zali@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Tue, 29 Apr 2014 02:00:05 -0400
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Index: Ac9i7PyERuk5jZsyQOKSHRHy2Ij/LwAG2CxAABnaMYA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C437EA9@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/YoeVj5YSdpftfC0nC36b4ksbB7o
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-18
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, 29 Apr 2014 06:00:38 -0000

Hi Nobo,

With respect to the MIB, this concern is a nit, so I'm ok with going ahead =
without
making this change ...

... However ...

Your WG chairs and AD should be concerned that this significant flaw in
BFD version 0 (justifying a "SHOULD NOT use" recommendation) is undocumente=
d.

Thanks,
--David

> -----Original Message-----
> From: Nobo Akiya (nobo) [mailto:nobo@cisco.com]
> Sent: Monday, April 28, 2014 1:46 PM
> To: Black, David; tnadeau@lucidvision.com; Zafar Ali (zali); General Area
> Review Team (gen-art@ietf.org)
> Cc: rtg-bfd@ietf.org; ietf@ietf.org
> Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
>=20
> Hi David,
>=20
> > -----Original Message-----
> > From: Black, David [mailto:david.black@emc.com]
> > Sent: Monday, April 28, 2014 10:20 AM
> > To: tnadeau@lucidvision.com; Zafar Ali (zali); Nobo Akiya (nobo); Gener=
al
> > Area Review Team (gen-art@ietf.org)
> > Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> > Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
> >
> > The -18 version of this draft responds to all of the comments in the Ge=
n-ART
> > review of -17, including the request for coordination w/the OPS area,
> > although I wasn't exactly expecting that to occur on the main IETF list=
.
>=20
> Thanks, they were very good comments.
>=20
> >
> > The -18 version is ready with one small nit - The following text has be=
en
> > added to the introduction:
> >
> >    This memo does not define a compliance requirement for a system that
> >
> >    only implements BFD version 0. This is a reflection of a considered
> >    and deliberate decision by the BFD WG.
> >
> > An explanation of the rationale for that decision would help - I sugges=
t
> > adding the following text and a suitable reference to the end of the te=
xt
> > above:
> >
> >    because the BFD version 0 protocol may deadlock and hence SHOULD NOT
> >    be used, as explained further in [RFCxxxx].
>=20
> Unfortunately the problem with BFD version 0 is not documented in any RFC=
s,
> and MIB is probably not the right place to start this documentation eithe=
r. If
> this should be documented in a RFC, possibly a new info document or raise
> errata on RFC5880 ... I'm not sure what would be a reasonable/recommended=
 path
> here. In any case, my vote for the MIB document(s) is to keep the current=
 text
> to proceed. Would that be ok with you?
>=20
> -Nobo
>=20
> >
> > Thanks,
> > --David
> >
> > > -----Original Message-----
> > > From: Black, David
> > > Sent: Wednesday, April 16, 2014 7:31 PM
> > > To: tnadeau@lucidvision.com; zali@cisco.com; nobo@cisco.com; General
> > > Area Review Team (gen-art@ietf.org)
> > > Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> > > Subject: Gen-ART review of draft-ietf-bfd-mib-17
> > >
> > > I am the assigned Gen-ART 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-bfd-mib-17
> > > Reviewer: David L. Black
> > > Review Date: April 16, 2014
> > > IETF LC End Date: April 28, 2014
> > >
> > > Summary: This draft is on the right track, but has open issues
> > > 		described in the review.
> > >
> > > This draft is a MIB module for the BFD protocol, which is an importan=
t
> > > low- level routing protocol.  The draft is reasonable for a MIB draft=
;
> > > one needs to go read the protocol documents to understand how the
> > > protocol works, and significant portions of the text are derived from=
 the
> > usual MIB "boilerplate"
> > > as one would expect.  The "Brief Description of MIB Objects" is indee=
d
> > > brief, but reasonable.  The shepherd writeup indicates that there are
> > > multiple implementations.
> > >
> > > Major issues:
> > >
> > > This MIB contains many writable objects, so the authors should take
> > > note of the IESG statement on writable MIB modules:
> > >
> > > 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> > >
> > > I did not see this mentioned in the shepherd writeup.  If the OPS Are=
a
> > > has not been consulted, I strongly suggest doing so during IETF Last
> > > Call, e.g., starting with Benoit Claise (AD).
> > >
> > > Minor issues:
> > >
> > > The security considerations section includes considerations for
> > > unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus=
,
> > > but omits the corresponding considerations for bfdAdminStatus and
> > > bfdSessNotificationsEnable.  Both of the latter objects are global, s=
o
> > > significant damage can be inflicted via these objects with a small
> > > number of unauthorized modifications, so they need to be included in
> > > the first list of sensitive objects.
> > >
> > > I suggest that the authors recheck the entire MIB to ensure that ever=
y
> > > object or table that should be included in the security consideration=
s
> > > section is appropriately included.
> > >
> > > Also, as a General Variable, would bfdSessNotificationsEnable be
> > > better named bfdNotificationsEnable, as it's not in the BFD Session T=
able?
> > >
> > > I did not see a compliance requirement for a system that only
> > > implements BFD protocol version 0.  That absence should at least be
> > > mentioned somewhere.  For example, if this reflects a considered and
> > > deliberate decision by the WG, that should be mentioned in the
> > > introduction.
> > >
> > > Nits/editorial comments:
> > >
> > > In the security considerations for authentication-related objects:
> > >
> > > OLD
> > >    In order for these sensitive information
> > >    from being improperly accessed, implementers MAY wish to disallow
> > >    access to these objects.
> > > NEW
> > >    In order to prevent this sensitive information
> > >    from being improperly accessed, implementers MAY disallow
> > >    access to these objects.
> > >
> > > idnits 2.13.01 found a truly minor nit that should be corrected when
> > > the draft is next revised:
> > >
> > >   =3D=3D Outdated reference: A later version (-05) exists of
> > >      draft-ietf-bfd-tc-mib-04
> > >
> > > it also generated a warning that probably does not reflect an actual
> > problem:
> > >
> > >   -- The document seems to lack a disclaimer for pre-RFC5378 work, bu=
t
> > may
> > >      have content which was first submitted before 10 November 2008. =
 If
> > you
> > >      have contacted all the original authors and they are all willing=
 to
> grant
> > >      the BCP78 rights to the IETF Trust, then this is fine, and you c=
an
> ignore
> > >      this comment.  If not, you may need to add the pre-RFC5378
> disclaimer.
> > >      (See the Legal Provisions document at
> > >      http://trustee.ietf.org/license-info for more information.)
> > >
> > > 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) 2=
93-7786
> > > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > > ----------------------------------------------------
>=20


From nobody Tue Apr 29 04:21:28 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 DA1C81A0840 for <gen-art@ietfa.amsl.com>; Tue, 29 Apr 2014 04:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Or5Bog-ysjka for <gen-art@ietfa.amsl.com>; Tue, 29 Apr 2014 04:21:24 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 031E51A083B for <gen-art@ietf.org>; Tue, 29 Apr 2014 04:21:23 -0700 (PDT)
X-AuditID: c1b4fb2d-f79036d00000126a-f7-535f8b32c825
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 80.C5.04714.23B8F535; Tue, 29 Apr 2014 13:21:22 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.191]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0174.001; Tue, 29 Apr 2014 13:21:21 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "draft-ietf-rtcweb-use-cases-and-requirements.all@tools.ietf.org" <draft-ietf-rtcweb-use-cases-and-requirements.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Gen-ART LC review of draft-ietf-rtcweb-use-cases-and-requirements-14.txt
Thread-Index: AQHPXOo38K7t40wgw0yOyZFPjpPV/5sogD1A
Date: Tue, 29 Apr 2014 11:21:21 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D2E3D66@ESESSMB209.ericsson.se>
References: <53544DF8.2010301@gmail.com>
In-Reply-To: <53544DF8.2010301@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJLMWRmVeSWpSXmKPExsUyM+Jvja5Rd3ywwZ710hZtF/cxWSy6PZ3Z 4uqrzywOzB47Z91l91iy5CeTx5fLn9kCmKO4bFJSczLLUov07RK4Mr7tPMNecN+u4tnRTsYG xpWGXYycHBICJhLt504xQ9hiEhfurWfrYuTiEBI4yihxYssjJpCEkMASRomO36pdjBwcbAIW Et3/tEHCIgJvGSXmHDYAsYUFEiV2Hn7MBhFPkpi9YSIjhG0kMefSSlYQm0VAVeJt/zOwOK+A r0Tb9y42iPEaEg3fnoDVcApoStxrPg92DyPQPd9PrQE7gVlAXOLWk/lMEHcKSCzZcx7qZlGJ l4//sYKcJiGgJDFtaxpEuY7Egt2f2CBsbYllC18zQ6wVlDg58wnLBEbRWUimzkLSMgtJyywk LQsYWVYxihanFhfnphsZ66UWZSYXF+fn6eWllmxiBMbNwS2/dXcwrn7teIhRgINRiYe3+Etk sBBrYllxZe4hRmkOFiVx3ra73sFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGF1cJOcphp2c 8PjfefkZtt1e1k8idYrv7EienOCcXb/CSiklskkm5sGnwG/+htzVxZ6CPfuSmx5v2qOe1HfL fnqy0SHh4J83VFVW8R2Wyv5kUrmR6cbkKzYvz62NlTC88NnnaK92i/SbEM43QvUJ2be96hsj Zq457bHKnvfmicXrH89+fWrhPiWW4oxEQy3mouJEAM+cvOR8AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/QX-p5a3njT3HMLyaUAlwdsdc8qY
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-rtcweb-use-cases-and-requirements-14.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, 29 Apr 2014 11:21:27 -0000

Hi Brian,

Thanks for your comments!

As we've had Easter vacation, and 1st May vacation is coming up, we won't b=
e able to address your comments until next week.

Just to let you know :)

Regards,

Christer



-----Original Message-----
From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Brian E Carpen=
ter
Sent: 21. huhtikuuta 2014 1:45
To: draft-ietf-rtcweb-use-cases-and-requirements.all@tools.ietf.org; Genera=
l Area Review Team
Subject: [Gen-art] Gen-ART LC review of draft-ietf-rtcweb-use-cases-and-req=
uirements-14.txt

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

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

Document: draft-ietf-rtcweb-use-cases-and-requirements-14.txt
Reviewer: Brian Carpenter
Review Date: 2014-04-21
IETF LC End Date: 2014-04-25
IESG Telechat date:

Summary:  In good shape but still needs work.
--------

Comment:
--------

In case there are W3C people reading this review, let me clarify that Gen-A=
RT reviews are by generalists who are often encountering a topic for the fi=
rst time. I haven't classified the issues into "major" and "minor" but some=
 of them really do need attention before the document advances. There are a=
lso some nits noted at the end.

Issues:
-------

>   The following considerations are applicable to all use cases:
>
>   o  Clients can be on IPv4-only
>
>   o  Clients can be on IPv6-only
>
>   o  Clients can be on dual-stack

It isn't clear whether this is intended to include the case where an IPv4-o=
nly client communicates with an IPv6-only node (or vice versa).

It also isn't clear about cases in which a mobile client's connectivity cha=
nges dynamically during a session (e.g. from IPv4 to IPv6). This is partly =
clarified later by F17, but only partly.

>   o  Clients can be on networks with a NAT using any type of Mapping
>      and Filtering behaviors (as described in RFC4787).

That document is scoped for UDP only. Is that sufficient? As I understand t=
he RTCWEB transport drafts, it is aiming at connection-oriented transport.
(How many NATs support SCTP, for example?)

> 3.2.  Common requirements
>
>   The requirements retrived from the Simple Video Communication Service
>   use-case (Section 3.3.1) by default apply to all other use-cases, and
>   are considred common.  For each individual use-case, only the
>   additional requirements are listed.

In fact you duplicate the additional requirements in each use case where th=
ey occur. That seems like overkill. Also there's at least one mix-up as a r=
esult, noted below.

> 3.3.1.2.  Common Requirements
...
>  F3      Transmitted streams and data must be rate
>          controlled (meaning that the browser must, regardless
>          of application behavior, reduce send rate when
>          there is congestion).

I think that needs to be broken into two more atomic requirements.
Something like

   F3.1    There must be a mechanism by which the transport layer
           can signal the occurrence of congestion to the browser.

   F3.2    Transmitted streams and data must be rate
           controlled (meaning that the browser must, regardless
           of application behavior, reduce send rate while
           there is congestion).

The change from "when" to "while" is intentional, since the browser should =
allow the rate to increase when there is no congestion.

>   F11     It must be possible to protect streams and data
>           from wiretapping [RFC2804].

I don't see the relevance of the reference (of which I am a co-author), whi=
ch mainly states that the IETF won't consider requirements *for* wiretappin=
g.
I'm sure you can find a reference that says encryption is a Good Thing.

>   F14     The browser must make it possible to set up a
>           call between two parties without one party
>           learning the other party's host IP address.

It is not clear how to interpret that. I assume it's supposed to be a resta=
tement of the earlier comment:

>   The application gives the users the opportunity to stop it from
>   exposing the host IP address to the application of the other user.

But -- assuming the implementation model is peer-to-peer communication betw=
een the two hosts, rather than client1-server-client2 communication -- I'm =
afraid I don't see how F14 can be guaranteed, since the peers must be aware=
 of each others' IP address. Even if the browser and app hide the remote ad=
dress, a little Wiresharking will reveal it immediately.
There's not much point stating a requirement that cannot be met.

I realised at this point in the document that you need to be very explicit =
about whether communication is indeed intended to be peer-to-peer or via th=
e server. And assuming it is meant to be peer-to-peer, what is the model fo=
r the rendez-vous between the peers? What requirements do you need to solve=
 the resulting referral problem?
(http://tools.ietf.org/html/draft-carpenter-referral-ps-02)

This topic belongs in the Common Requirements.

> 3.3.7.1.  Description
...
>   The user in the previous use case that starts a trip is behind a
>   common residential router that supports prioritization of traffic.

Please talk about differentiated services (RFC 2474 etc.). IP doesn't have =
simple priority. That's exactly why the DART WG was just formed.

> 3.3.7.2.  Additional Requirements
>
>   ----------------------------------------------------------------
>   REQ-ID      DESCRIPTION
>   ----------------------------------------------------------------
>   F17     The communication session must survive across a
>           change of the network interface used by the
>           session
>   ----------------------------------------------------------------
>   F22     The browser must be able to receive streams and
>           data from multiple peers concurrently.
>   ----------------------------------------------------------------

This seems completely messed up. The reader expects requirements for QoS at=
 this point. Isn't this "F22" really F24?

> 3.3.10.2.  Additional Requirements
>
>   ----------------------------------------------------------------
>   REQ-ID      DESCRIPTION
>   ----------------------------------------------------------------
>   F22     The browser should be able to take advantage
>           of available capabilities (supplied by network
>           nodes) to prioritize voice, video and data
>           appropriately.

Again, please cite differentiated services rather than prioritization.
Also, you now have two different F22s. This one seems to fit 3.3.7.2 better=
.

Below, you also have two F25s. And other duplicates. Wasn't the idea just t=
o add *new* requirements when they arose? As F22 shows, the duplication is =
error-prone.

> 6.  Security Considerations

I am really surprised that there isn't a sub-section on Privacy Considerati=
ons. RFC 6973 describes the various types of threat and they seem specially=
 relevant here.

Nits:
-----

> 2.  Conventions
>
>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>   document are to be interpreted as described in BCP 14, RFC 2119
>   [RFC2119].

The change log says you removed this. Also there is no change log since ver=
sion 10.

RFC 4787 is mentioned but not listed as an Informative Reference.

>    A17, A23
>    A13, A14, A15, A16

What are these lines that occur in a few places?

RFC 2804 and RFC 5479 are Informational documents so cannot reasonably be N=
ormative References.

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


From nobody Tue Apr 29 05:47:35 2014
Return-Path: <eric@notcom.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 7F8931A08C3 for <gen-art@ietfa.amsl.com>; Tue, 29 Apr 2014 05:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] 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 kgT66IYfkk4E for <gen-art@ietfa.amsl.com>; Tue, 29 Apr 2014 05:47:28 -0700 (PDT)
Received: from mail-yk0-f179.google.com (mail-yk0-f179.google.com [209.85.160.179]) by ietfa.amsl.com (Postfix) with ESMTP id 49BCD1A08C6 for <gen-art@ietf.org>; Tue, 29 Apr 2014 05:47:28 -0700 (PDT)
Received: by mail-yk0-f179.google.com with SMTP id 9so116517ykp.10 for <gen-art@ietf.org>; Tue, 29 Apr 2014 05:47:27 -0700 (PDT)
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=qBxoju/bNqOAad9cRoi2KC5kJQK7PE2HPAWPijmFBAY=; b=N90772yOhhrgAaSC44tUZcESgM5D7gda3+GfLm03d8qPuSpt/aCBqJjn21qWjhKrWW I1b107CSEmb00rbQINnDsiFXXQx+NMfXxOAueqNhUFOdi7Oxq+8RkFuNjLWVYAVS4+jV 3hrkIOqtyHjd7p+R1rCaD8sjbAQJdPOVNFeu3w2KU+qfEpHyl8MdPbFdnIoa62n6DEgo 13PufAR2CRShZVaSE5U83f4TN20PaqHxcPcLaYP4BRdoYNsk0oo0rAFfXzw3qKYf+BQ1 qqbqlaJ5DbVeXbetEryb4ke7t/RR/N1mmnrnjUEIJTxDTua7pwLJgP7ft0kea+yWw1YT zIUg==
X-Gm-Message-State: ALoCoQm0HgoOpijpTqlWpzNXAFdQLhsToTGGhOFm0srB2hN/IjTIDxHWjWtuGnI5PvuHr/q9AoCA
MIME-Version: 1.0
X-Received: by 10.236.53.69 with SMTP id f45mr27028734yhc.53.1398775647019; Tue, 29 Apr 2014 05:47:27 -0700 (PDT)
Received: by 10.170.60.5 with HTTP; Tue, 29 Apr 2014 05:47:26 -0700 (PDT)
In-Reply-To: <535A81AF.3030500@joelhalpern.com>
References: <53597772.6000401@nostrum.com> <53598854.2010201@joelhalpern.com> <CA+97oKPxMJC2zngqUwfRGCNXtP61rqsoRdCbhLAj+_30dZTVeg@mail.gmail.com> <535A7903.2070704@joelhalpern.com> <CA+97oKPbtmSz8DLP8v6Xt3wwVNQdC7Qib0duj2orgyXwstGaXw@mail.gmail.com> <535A81AF.3030500@joelhalpern.com>
Date: Tue, 29 Apr 2014 08:47:26 -0400
Message-ID: <CA+97oKMcpFDCOBSEzVLibPNu7rTKeXio0ku0BV4qeZ4Qk7CnFg@mail.gmail.com>
From: Eric Osborne <eric@notcom.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Y18CwnP7ykJKArOIaUs01qk62pY
Cc: "mpls@ietf.org" <mpls@ietf.org>, General Area Review Team <gen-art@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>
Subject: Re: [Gen-art] [mpls] review: draft-ietf-mpls-extended-admin-group-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, 29 Apr 2014 12:47:30 -0000

Done and posted as -06.

Chairs: This latest posting has all of the reviews, nits and other
changes that have been requested.  It is ready for publication.



eric

On Fri, Apr 25, 2014 at 11:39 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> That works for me.
> Thank you Eric.
> Yours,
> Joel
>
>
> On 4/25/14, 11:28 AM, Eric Osborne wrote:
>>
>> Works for me.
>> So
>>
>> " The EAG sub-TLV is used in addition to the Administrative Groups
>> when an operator wants to make more than 32 colors available for
>> advertisement in a network"
>>
>> I had gone back and forth with Adrian on language to scope this to a
>> single LSDB, so as to avoid the discussion of signaling EAG desire in
>> RSVP or PCEP.  I don't want to add that sort of disclaimer here too,
>> as it makes the sentence clunky and unweildy.
>>
>>
>>
>> eric
>>
>>
>> On Fri, Apr 25, 2014 at 11:02 AM, Joel Halpern Direct
>> <jmh.direct@joelhalpern.com> wrote:
>>>
>>> What if instead of "on the link" it is simoply "in the network".  This
>>> recommend the use of EAG whenever the operators is using more than 32
>>> colors
>>> across the link.  It thus actually better aligns with avoiding the
>>> under-claiming issue by suggesting that operators should use the EAG if
>>> they
>>> have more than 32 candidate colors.
>>>
>>> Yours,
>>> Joel
>>>
>>> PS: substituting wants for wishes is probably reasonable.  If we talk
>>> about
>>> network-wide you might even be able to us "intends".
>>>
>>>
>>> On 4/25/14, 10:06 AM, Eric Osborne wrote:
>>>>
>>>>
>>>> Hi Joel-
>>>>
>>>>     Thanks for the review.  On your minor issue:
>>>> ---
>>>>    I believe it is more accurate to say that it is to be used "when a
>>>> node wishes to advertise colors for a link which are not represented
>>>> in the first 32 bits of the color mask."  The node may only wish to
>>>> advertise colors 7 and 60, but that will require the EAG.
>>>> ---
>>>>
>>>> I see your point, but I'm having trouble coming up with obvious text.
>>>> Deciding which colors are represented in a color mask is up to the
>>>> operator, which means it would have to say something like
>>>>
>>>> "when a node wishes to advertise colors for a link which the operator
>>>> has defined to be outside the first 32 bits of the color mask".
>>>>
>>>> but this would be the only use of 'color mask' in the document, and
>>>> it's not one I've seen used in any other docs around link coloring.
>>>>
>>>> The whole sentence you refer to is:
>>>>
>>>> " The EAG sub-TLV is used in addition to the Administrative Groups
>>>> when a node wishes to advertise more than 32 colors for a link."
>>>>
>>>> If I rephrased it as
>>>>
>>>> " The EAG sub-TLV is used in addition to the Administrative Groups
>>>> when an operator wants to make more than 32 colors available for
>>>> advertisement on a link"
>>>>
>>>> would that do it?
>>>> s/wishes/wants/ while I'm here.
>>>>
>>>>
>>>>
>>>> eric
>>>>
>>>>
>>>> On Thu, Apr 24, 2014 at 5:55 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-mpls-extended-admin-group-05
>>>>>       Extended Administrative Groups in MPLS-TE
>>>>> Reviewer: Joel M. Halpern
>>>>> Review Date: 24-April-2014
>>>>> IETF LC End Date: 06-May-2014
>>>>> IESG Telechat date: N/A
>>>>>
>>>>> Summary: This document is ready for publication as a Proposed Standards
>>>>> RFC
>>>>>
>>>>> Major issues: N/A
>>>>>
>>>>> Minor issues:
>>>>>       I believe that the description of when to use this EAG is
>>>>> slightly
>>>>> misleading.  The text says that EAG is to be used "when a node wishes
>>>>> to
>>>>> advertise more than 32 colors for a link."  I believe it is more
>>>>> accurate
>>>>> to
>>>>> say that it is to be used "when a node wishes to advertise colors for a
>>>>> link
>>>>> which are not represented in the first 32 bits of the color mask."  The
>>>>> node
>>>>> may only wish to advertise colors 7 and 60, but that will require the
>>>>> EAG.
>>>>>
>>>>> Nits/editorial comments: N/A
>>>>>
>>>>> _______________________________________________
>>>>> mpls mailing list
>>>>> mpls@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mpls


From nobody Tue Apr 29 07:58:37 2014
Return-Path: <jhaas@slice.pfrc.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 F27DC1A0928; Tue, 29 Apr 2014 07:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.219
X-Spam-Level: 
X-Spam-Status: No, score=-2.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.651, 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 x2WRFYNd8foT; Tue, 29 Apr 2014 07:58:25 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id A5A6F1A0925; Tue, 29 Apr 2014 07:58:25 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 870EBC220; Tue, 29 Apr 2014 10:58:24 -0400 (EDT)
Date: Tue, 29 Apr 2014 10:58:24 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Black, David" <david.black@emc.com>
Message-ID: <20140429145824.GR1256@pfrc>
References: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712076C437EA9@MX15A.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C437EA9@MX15A.corp.emc.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/OnGHPZi4WezX0mncWC50dFT24AM
Cc: "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Nobo Akiya \(nobo\)" <nobo@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-18
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, 29 Apr 2014 14:58:30 -0000

On Tue, Apr 29, 2014 at 02:00:05AM -0400, Black, David wrote:
> With respect to the MIB, this concern is a nit, so I'm ok with going ahead without
> making this change ...
> 
> ... However ...
> 
> Your WG chairs and AD should be concerned that this significant flaw in
> BFD version 0 (justifying a "SHOULD NOT use" recommendation) is undocumented.

And also un-RFCed.

It was a "work in progress" that never fully saw the light of full
deployment.  Vendors very quickly moved to version 1 which fixed a critical
issue in the state machine.  If any version 0 survives, it's historical and
likely to be a source of operational agony rather than a useful feature.

-- Jeff


From nobody Tue Apr 29 08:28:27 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 997311A0913; Tue, 29 Apr 2014 08:28:25 -0700 (PDT)
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 odRdtdvjG1vp; Tue, 29 Apr 2014 08:28:23 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 631FA1A092A; Tue, 29 Apr 2014 08:28:21 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id wp4so416521obc.35 for <multiple recipients>; Tue, 29 Apr 2014 08:28:20 -0700 (PDT)
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=5/CuRQhyHM3HLgIv75WtmRMsElLM2d17fnrNFr9r9PY=; b=NS2wWR/vxmw7EVgPAejDRxYgyHO53Im4aLHxzMa+/uBSN8X0uJUkDsdP2wUqdG7Iw+ vawhbugBGKNppLbxOWQeQthQ9ZUCJA7ZQHdS2hGmNdycNzAK0wewkrPfDkvg6P1q3WMK UB29XwsMm+aVPcfJD+lDyqJy9Sf0ZbqsAlmGRKwwrGClJEoFjmJS/zeEsMNAnPY2xy1d pBYE+6x10wEKW4lmze/o+PoFqsJEBNwi1R20w6+mpfPHitGhX286jWq0IxPGg+Vx+L+H I6MihVyBbS1ciYHliWyLYCYcXj5j9M5AIApOZ3t4dwAadtBKvbw5f1Exrs6AVEEv/uAy TnCA==
X-Received: by 10.60.57.164 with SMTP id j4mr112918oeq.24.1398785300242; Tue, 29 Apr 2014 08:28:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.25.41 with HTTP; Tue, 29 Apr 2014 08:28:00 -0700 (PDT)
In-Reply-To: <009d01cf6047$760de3c0$6229ab40$@akayla.com>
References: <009d01cf6047$760de3c0$6229ab40$@akayla.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 29 Apr 2014 11:28:00 -0400
Message-ID: <CAF4+nEEq2LmPm37i-TWTTwGQYgNTRf-JJjo+_34K4Mrd_nCxtQ@mail.gmail.com>
To: Peter Yee <peter@akayla.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/SJ9xcbdUd9B-TxGxK5g73phZHKk
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-eastlake-iana-cfm-considerations.all@tools.ietf.org, IETF Discussion <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-eastlake-iana-cfm-considerations-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, 29 Apr 2014 15:28:25 -0000

Hi Peter,

I'm fine with all of your suggestion. Thanks for the review.

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

On Fri, Apr 25, 2014 at 1:30 AM, Peter Yee <peter@akayla.com> wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>
> Please resolve these comments along with any other Last Call comments you
> may receive.
>
> Document: draft-eastlake-iana-cfm-considerations-01
> Reviewer: Peter Yee
> Review Date: April-24-2014
> IETF LC End Date: May-21-2014
> IESG Telechat date: TBD
>
> Summary: This draft is basically ready for publication as a Best Current
> Practice, but has some nits that should be fixed before publication. [Ready
> with nits.]
>
> This document provides the IANA Considerations for two registries covering
> the IEEE Std 802.1Q-2011 CFM OpCode and TLV Type blocks assigned to the
> IETF.
>
> Nits:
>
> Most comments that follow are for alignment with the terminology and usage
> found in IEEE Std 802.1Q-2011.
>
> General: globally replace "Continuity" with "Connectivity".
>
> General: globally replace "Codepoints" with "Code Points".
>
> General: globally replace "Op-Code" with "OpCode".
>
> Page 3, 2nd paragraph, 2nd sentence: change "IANA Consideration" to "IANA
> Considerations".
>
> Page 5, 1st paragraph: end the reference with a period.
>
> Page 5, 2nd paragraph: replace "Mansfield, S." with "and S. Mansfield" to
> match http://www.rfc-editor.org/in-notes/rfc-ref.txt.  Hey, I'm running out
> of nits to pick here. :-)
>
>                 -Peter Yee
>
>


From nobody Tue Apr 29 08:37:58 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 24D721A091D; Tue, 29 Apr 2014 08:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.952
X-Spam-Level: 
X-Spam-Status: No, score=-4.952 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_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 o92jOI376Ijw; Tue, 29 Apr 2014 08:37:53 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 2D78C1A01DF; Tue, 29 Apr 2014 08:37:52 -0700 (PDT)
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3TFbmDT024855 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Apr 2014 11:37:49 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com s3TFbmDT024855
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1398785870; bh=XDdtEZPUnWQK32BO3jrDItmfWrQ=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=JDw7ZcIrygsEoH1M/ed5ImfNsp+5Pu9Ul7yGhRsCMIiVRrvOjJyJRjJziGBJmnXJw YdNG3UG+ECbWnE5SU2hHGUU9A6+FNbv9MN6e8UEVQKc3Vi+h2bN0Q9CcwGkAXQhB40 PgvX4stbA2K7mhh6L8ZRTq5IWUhqzAAUAmsHwzPc=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com s3TFbmDT024855
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd53.lss.emc.com (RSA Interceptor); Tue, 29 Apr 2014 11:37:42 -0400
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3TFbfU1015605 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 29 Apr 2014 11:37:41 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub01.corp.emc.com ([10.254.141.103]) with mapi; Tue, 29 Apr 2014 11:37:40 -0400
From: "Black, David" <david.black@emc.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Date: Tue, 29 Apr 2014 11:37:39 -0400
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Index: Ac9ju3y+7+r2M3cwRuClVDsxPJjgywAAKutg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C437F73@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712076C437EA9@MX15A.corp.emc.com> <20140429145824.GR1256@pfrc>
In-Reply-To: <20140429145824.GR1256@pfrc>
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
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/17fQH0O33NkhF7DoAQ-_Hg3Y3gk
Cc: "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Nobo Akiya \(nobo\)" <nobo@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-18
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, 29 Apr 2014 15:37:55 -0000

Jeff - could you work w/Nobo to get the word "historical" included in
the MIB draft as a characterization of BFD version 0 ?  For example,
the following text could be added to the introduction:

   because the BFD version 0 protocol is primarily of historical interest
   by comparison to the widespread deployment of the BFD version 1 protocol=
.

Thanks,
--David


> -----Original Message-----
> From: Jeffrey Haas [mailto:jhaas@pfrc.org]
> Sent: Tuesday, April 29, 2014 10:58 AM
> To: Black, David
> Cc: Nobo Akiya (nobo); tnadeau@lucidvision.com; Zafar Ali (zali); General=
 Area
> Review Team (gen-art@ietf.org); rtg-bfd@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-18
>=20
> On Tue, Apr 29, 2014 at 02:00:05AM -0400, Black, David wrote:
> > With respect to the MIB, this concern is a nit, so I'm ok with going ah=
ead
> without
> > making this change ...
> >
> > ... However ...
> >
> > Your WG chairs and AD should be concerned that this significant flaw in
> > BFD version 0 (justifying a "SHOULD NOT use" recommendation) is
> undocumented.
>=20
> And also un-RFCed.
>=20
> It was a "work in progress" that never fully saw the light of full
> deployment.  Vendors very quickly moved to version 1 which fixed a critic=
al
> issue in the state machine.  If any version 0 survives, it's historical a=
nd
> likely to be a source of operational agony rather than a useful feature.
>=20
> -- Jeff


From nobody Tue Apr 29 12:06:56 2014
Return-Path: <nobo@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 DCCAC1A097F; Tue, 29 Apr 2014 12:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.152
X-Spam-Level: 
X-Spam-Status: No, score=-110.152 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.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, 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 0md08NaBolkX; Tue, 29 Apr 2014 12:06:49 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 17CE41A0792; Tue, 29 Apr 2014 12:06:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2317; q=dns/txt; s=iport; t=1398798408; x=1400008008; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=JAJOJ90lUsDTAnSqJwPDqTxu8hZxx9IW/Tk7n3KX5EQ=; b=iAyNGn3Splg/6W1CjJUmWX+XA4CuHDDyf1kUBFL+OE+eUpqmqGhuVTa9 liuwxMygUc3LzG0IeXWksZ5r1bVy+VLjkiIR5E9g9n5e9nWVIQlyCR5Yy EB5PA45xKigZSyjjSR65yzrbeZk+CFOm023YfvnGefnsDbg7lh8/3GWqS g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwHAC/3X1OtJV2b/2dsb2JhbABZgmUhT1EGxQ+BJhZ0giUBAQEEOj8MBAIBCBEEAQEBChQJBzIUCQgBAQQBDQUIAYg4AQcFyTMXjh4xBwaDHoEVBJpMkSaDMYIr
X-IronPort-AV: E=Sophos;i="4.97,952,1389744000"; d="scan'208";a="39747614"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP; 29 Apr 2014 19:06:47 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3TJ6ljS015380 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 29 Apr 2014 19:06:47 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Tue, 29 Apr 2014 14:06:47 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Black, David" <david.black@emc.com>, Jeffrey Haas <jhaas@pfrc.org>
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Index: Ac9i7PyERuk5jZsyQOKSHRHy2Ij/LwAG2CxAABnaMYAAHWa2AAABXuyAAAM2hqA=
Date: Tue, 29 Apr 2014 19:06:46 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E11775C@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712076C437EA9@MX15A.corp.emc.com> <20140429145824.GR1256@pfrc> <8D3D17ACE214DC429325B2B98F3AE712076C437F73@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C437F73@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.244.77]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/rzOXeDgEfgqVbx13oGI5tsepMMM
Cc: "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-mib-18
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, 29 Apr 2014 19:06:51 -0000

Hi David,

BFD-MIB-19 with suggested text has just been published.

URL:            http://www.ietf.org/internet-drafts/draft-ietf-bfd-mib-19.t=
xt
Status:         https://datatracker.ietf.org/doc/draft-ietf-bfd-mib/
Htmlized:       http://tools.ietf.org/html/draft-ietf-bfd-mib-19
Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-bfd-mib-19

Thanks again!

-Nobo

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Tuesday, April 29, 2014 11:38 AM
> To: Jeffrey Haas
> Cc: Nobo Akiya (nobo); tnadeau@lucidvision.com; Zafar Ali (zali); General
> Area Review Team (gen-art@ietf.org); rtg-bfd@ietf.org; ietf@ietf.org; Bla=
ck,
> David
> Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
>=20
> Jeff - could you work w/Nobo to get the word "historical" included in the
> MIB draft as a characterization of BFD version 0 ?  For example, the foll=
owing
> text could be added to the introduction:
>=20
>    because the BFD version 0 protocol is primarily of historical interest
>    by comparison to the widespread deployment of the BFD version 1
> protocol.
>=20
> Thanks,
> --David
>=20
>=20
> > -----Original Message-----
> > From: Jeffrey Haas [mailto:jhaas@pfrc.org]
> > Sent: Tuesday, April 29, 2014 10:58 AM
> > To: Black, David
> > Cc: Nobo Akiya (nobo); tnadeau@lucidvision.com; Zafar Ali (zali);
> > General Area Review Team (gen-art@ietf.org); rtg-bfd@ietf.org;
> > ietf@ietf.org
> > Subject: Re: Gen-ART review of draft-ietf-bfd-mib-18
> >
> > On Tue, Apr 29, 2014 at 02:00:05AM -0400, Black, David wrote:
> > > With respect to the MIB, this concern is a nit, so I'm ok with going
> > > ahead
> > without
> > > making this change ...
> > >
> > > ... However ...
> > >
> > > Your WG chairs and AD should be concerned that this significant flaw
> > > in BFD version 0 (justifying a "SHOULD NOT use" recommendation) is
> > undocumented.
> >
> > And also un-RFCed.
> >
> > It was a "work in progress" that never fully saw the light of full
> > deployment.  Vendors very quickly moved to version 1 which fixed a
> > critical issue in the state machine.  If any version 0 survives, it's
> > historical and likely to be a source of operational agony rather than a
> useful feature.
> >
> > -- Jeff


From nobody Wed Apr 30 03:27:04 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 0B5C71A6F38 for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 03:26:51 -0700 (PDT)
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, 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 AIYlXbC8XKmt for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 03:26:43 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0F2831A0118 for <gen-art@ietf.org>; Wed, 30 Apr 2014 03:26:41 -0700 (PDT)
X-AuditID: c1b4fb25-f798c6d000001521-89-5360cfdff2c7
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id CC.6F.05409.FDFC0635; Wed, 30 Apr 2014 12:26:39 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.191]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0174.001; Wed, 30 Apr 2014 12:26:39 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-bfd-tc-mib-06
Thread-Index: Ac9kXmZkqLpMSYwHT0aMT2C9XEwyyQ==
Date: Wed, 30 Apr 2014 10:26:39 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D2E5726@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.147]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D2E5726ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFLMWRmVeSWpSXmKPExsUyM+Jvje798wnBBj+/G1ts+fWV0eLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfGqpsv2QtWFFZ8ereVtYHxV0YXIyeHhICJ xJnL21ghbDGJC/fWs3UxcnEICRxllPi8/hY7hLOEUeLFjD9ADgcHm4CFRPc/bZAGEQFNibkr 3jKBhJkFoiW+tqWBmMICxhLnDqVCVFhInD/8kBnC1pPoPzkDzGYRUJWY8+4GO4jNK+ArMWnj SUYQmxHohO+n1jCB2MwC4hK3nsxngjhNQGLJnvPMELaoxMvH/1hBVkkIKElM25oGUZ4v8Xrz FBaIkYISJ2c+YZnAKDwLyaRZSMpmISmDiOtILNj9iQ3C1pZYtvA1M4x95sBjJmTxBYzsqxhF i1OLk3LTjYz1Uosyk4uL8/P08lJLNjECI+fglt+qOxgvv3E8xCjAwajEw1v8JTJYiDWxrLgy 9xCjNAeLkjjvl1s+wUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYS08Il6V/Fjhe7SWm0hYs /vtuY0FFJEfsGweZI3Ou7D+vsf1UUzKrtDKf54vVTl3u1ktOb/dY0Wwq1MO08Kah4umrRy+q T+5eoX/kUmhiZFS79u4XVUnCJZff/L9cuDbmnMHPfc/n72eQ5TDbInTio93avRNuXNvjf+j4 rWPfZAxyuV/e3BnzVImlOCPRUIu5qDgRAHC0sh99AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/6dap86iFOfNMr5JSDGTI-p7xFgE
Cc: "draft-ietf-bfd-tc-mib.all@tools.ietf.org" <draft-ietf-bfd-tc-mib.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-bfd-tc-mib-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: Wed, 30 Apr 2014 10:26:51 -0000

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

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq<https://rvi.se.ericsson.net/owa/,DanaInfo=3Dmail.internal.ericsson.c=
om,SSL+redir.aspx?C=3DvCr1L8PWQUqCZeSAn6cKI_Abm6K8vNAI1hJJwcnXe8VAikdG2PcMr=
stLszaJeAo7bR8W3uA2uu0.&URL=3Dhttps%3a%2f%2frvi.se.ericsson.net%2fowa%2f%2c=
DanaInfo%3dmail.internal.ericsson.com%2cSSL%2bredir.aspx%3fC%3dvCr1L8PWQUqC=
ZeSAn6cKI_Abm6K8vNAI1hJJwcnXe8VAikdG2PcMrstLszaJeAo7bR8W3uA2uu0.%26URL%3dht=
tp%253a%252f%252fwiki.tools.ietf.org%252farea%252fgen%252ftrac%252fwiki%252=
fGenArtfaq>>

Document:                         draft-ietf-bfd-tc-mib-06

Reviewer:                           Christer Holmberg

Review Date:                     30 April 2014

IETF LC End Date:             28 April 2014

IETF Telechat Date:         15 May 2014

Summary:        The document is almost ready for publication, with a couple=
 of minor nits that the authors may want to address.

Major Issues: None

Minor Issues: None

Editorial nits:

Section 1 (Introduction):
---------------------------------

Q_1:


s/"two MIB modules"/"two Management Information Base (MIB) modules"



Section 4 (Security Considerations):
------------------------------------------------

Q_4:

The last sentence says:

"Therefore, this document has no impact on the security of the Internet."

That sounds a little funny :) Wouldn't it be better to simply say:

"Therefore, this document does not introduce any additional security consid=
erations."


Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D2E5726ESESSMB209erics_
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: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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">I am the assigned Gen-ART r=
eviewer for this draft. For background on Gen-ART, please see the FAQ at &l=
t;</span><span lang=3D"FI" style=3D"font-size:10.0pt;font-family:&quot;Taho=
ma&quot;,&quot;sans-serif&quot;;color:black"><a href=3D"https://rvi.se.eric=
sson.net/owa/,DanaInfo=3Dmail.internal.ericsson.com,SSL&#43;redir.aspx?C=3D=
vCr1L8PWQUqCZeSAn6cKI_Abm6K8vNAI1hJJwcnXe8VAikdG2PcMrstLszaJeAo7bR8W3uA2uu0=
.&amp;URL=3Dhttps%3a%2f%2frvi.se.ericsson.net%2fowa%2f%2cDanaInfo%3dmail.in=
ternal.ericsson.com%2cSSL%2bredir.aspx%3fC%3dvCr1L8PWQUqCZeSAn6cKI_Abm6K8vN=
AI1hJJwcnXe8VAikdG2PcMrstLszaJeAo7bR8W3uA2uu0.%26URL%3dhttp%253a%252f%252fw=
iki.tools.ietf.org%252farea%252fgen%252ftrac%252fwiki%252fGenArtfaq" target=
=3D"_blank"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;">http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq</span></a></span><span style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">&gt;</span><=
span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-se=
rif&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<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:black">Document:&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-bfd-tc-mib-0=
6</span><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quo=
t;sans-serif&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<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:black">Reviewer:&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Christer Ho=
lmberg</span><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;=
,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<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:black">Review Date:&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30 April 2014</span><span style=3D"font-size=
:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<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:black">IETF LC End Date:&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 28 April 201=
4</span><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quo=
t;sans-serif&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<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:black">IETF Telechat Date:&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 15 May 2014</span><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color=
:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<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:black">Summary:&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; The document is almost ready for publication, with a cou=
ple of minor nits that the authors may want to address.<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<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:black">Major Issues: None</span><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-ser=
if&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<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:black">Minor Issues: None</span><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-ser=
if&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<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:black">Editorial nits:</span><span=
 style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">Section 1 (Introduction):<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">----------------------------=
-----<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">Q_1:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">s/&#8221;two MIB modules&#82=
21;/&#8221;two Management Information Base (MIB) modules&#8221;<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">Section 4 (Security Consider=
ations):<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">----------------------------=
--------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">Q_4:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">The last sentence says:<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
>&#8220;Therefore, this document has no impact on the security of the Inter=
net.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">That sounds a little funny :=
) Wouldn&#8217;t it be better to simply say:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
>&#8220;Therefore, this document does not introduce any additional security=
 considerations.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">Regards,<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;;color:black">Christer<o:p></o:p></span></=
p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D2E5726ESESSMB209erics_--


From nobody Wed Apr 30 07:01:44 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 C0F0F1A08D4 for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 07:01:43 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 6xu2NB7RnDHv for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 07:01:42 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id E98C71A08D0 for <gen-art@ietf.org>; Wed, 30 Apr 2014 07:01:41 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3UE1bRv013193; Wed, 30 Apr 2014 15:01:37 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3UE1aYu013181 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Apr 2014 15:01:37 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1D2E5726@ESESSMB209.ericsson.se> <f9e2fcab904e4a368ec04a5f694b48b0@BLUPR05MB151.namprd05.prod.outlook.com>
In-Reply-To: <f9e2fcab904e4a368ec04a5f694b48b0@BLUPR05MB151.namprd05.prod.outlook.com>
Date: Wed, 30 Apr 2014 15:01:33 +0100
Message-ID: <084501cf647c$b1e9b700$15bd2500$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJSHc86u6Xjr9lHZ9xaDK1t6gXuwAFpj2wVmhlwdTA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20664.007
X-TM-AS-Result: No--1.367-10.0-31-10
X-imss-scan-details: No--1.367-10.0-31-10
X-TMASE-MatchedRID: fgYTp5XatxanykMun0J1wpmug812qIbzC/ExpXrHizyKYlxVoGRyYYMD vFclzIUY0e+MIg7zZb4gCQdFOX/GPb+gVyuD/4tWvHKClHGjjr0hotH7bEpEMiBzIZ6+1+0no8W MkQWv6iWUlyXyo7IG7uTCMddcL/gjro1URZJFbJuJBlGoshqHNqs1OW+hCilDhr6IMozUulT8wt HNB+I1GLVnkzm2f/FHHqtCHpE8TP+3hM1RueMs5gby7BE6DRcEclCd0Ao/PhCwn+PGVed3d2n3E e4z0B9SIp5Rs422B5N7VnB1kjR3X4ZYKEHoCBPn
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/8XpmkfQ1NSjCeTW4THpwevIsxe0
Cc: 'General Area Review Team' <gen-art@ietf.org>, draft-ietf-bfd-tc-mib.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-tc-mib-06
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: Wed, 30 Apr 2014 14:01:43 -0000

Hi Christer,

Thanks for your efforts.

> Editorial nits:
>=A0
> Section 1 (Introduction):
>---------------------------------
>=A0
> Q_1:
>
> s/=94two MIB modules=94/=94two Management Information Base (MIB) =
modules=94

Note that "MIB" is found as "well known" at
http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
=A0
Authors, please do not make this change.
=A0
Cheers,
Adrian


From nobody Wed Apr 30 07:19:16 2014
Return-Path: <tnadeau@lucidvision.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 6E3851A08DF for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 07:19:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, 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 uItOxv9_xJyo for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 07:19:14 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 279051A078F for <gen-art@ietf.org>; Wed, 30 Apr 2014 07:19:14 -0700 (PDT)
Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 62AF82789491; Wed, 30 Apr 2014 10:19:12 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_27E9154F-AD15-4E4D-847E-75C5915581E3"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <084501cf647c$b1e9b700$15bd2500$@olddog.co.uk>
Date: Wed, 30 Apr 2014 10:19:08 -0400
Message-Id: <019935C0-A625-4E68-AC32-2614BED7E1F8@lucidvision.com>
References: <7594FB04B1934943A5C02806D1A2204B1D2E5726@ESESSMB209.ericsson.se> <f9e2fcab904e4a368ec04a5f694b48b0@BLUPR05MB151.namprd05.prod.outlook.com> <084501cf647c$b1e9b700$15bd2500$@olddog.co.uk>
To: Farrel Adrian <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/-hsPDBD52yJD7q833OSQ3h-6MTw
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-bfd-tc-mib.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-tc-mib-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: Wed, 30 Apr 2014 14:19:15 -0000

--Apple-Mail=_27E9154F-AD15-4E4D-847E-75C5915581E3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

ACK

On Apr 30, 2014:10:01 AM, at 10:01 AM, Adrian Farrel =
<adrian@olddog.co.uk> wrote:

> Hi Christer,
>=20
> Thanks for your efforts.
>=20
>> Editorial nits:
>> =20
>> Section 1 (Introduction):
>> ---------------------------------
>> =20
>> Q_1:
>>=20
>> s/=94two MIB modules=94/=94two Management Information Base (MIB) =
modules=94
>=20
> Note that "MIB" is found as "well known" at
> http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
> =20
> Authors, please do not make this change.
> =20
> Cheers,
> Adrian
>=20
>=20


--Apple-Mail=_27E9154F-AD15-4E4D-847E-75C5915581E3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTYQZdAAoJEPcO+I7eiUJZSq8P/0bob5kUKCfBufiHdKTVRCMr
yQixxdhnXdVVfc+AlFxD5ycpZsafw3XfFQbnQTX0H2lLfM9U1xBICUEMKs8cLNbg
m5/n06hSLBARgjOJcYHEnqtkM82KxvCWxzbWtGNZSHAtdTsXPaPEcSnCytMNCyyN
2HNv6W94kvHHQx9RIjqdQcoSAg0paQroplW7PunmVwemo9BDaMPuRigJy7bdvhhO
9eN94HfCMK/gLDBuyGCqITD+U87UHNMkogxnsNdCPCx2dJfPOWcB3PcserjBRLaK
Na/uiNeOjBBmimu6jzxzD8epNArjvUfIrEGon3JRCg+YTgu+KlA3SRfjGG/oZEuB
G6dGsff7rs3RG03sG3guWWmQ9pitCSBgEnwReYPrydg7xBOZDPAPyhPHxSbMTOzz
U+scn+eTJxXPjVK28n74hqAdaoC2VrWDzdnY653QimCUPjJBmS3OgvquRbw2ipOw
K4nHokldrpaYq3qnBX3O9aAMkR/b+5M9mocBwoSpGZQIIl8L2LvR2KUtTp8Nj7ng
vdAd7eOlKAjBFmF6CHNVW1fvH9d/zx1WEoKgjQk9bM8iblC7jV9UfUudHOjbiURq
dFq38lHyzxjPjOgEqF55UMjD1YWMtYzts4GHzjpsFniMPvFJkLWWHaUZvi4Uzxt0
O10gm1HUpd8alMhZdmsn
=YMoa
-----END PGP SIGNATURE-----

--Apple-Mail=_27E9154F-AD15-4E4D-847E-75C5915581E3--


From nobody Wed Apr 30 07:24:44 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 D7C651A6FB3 for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 07:24:42 -0700 (PDT)
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 3IWjCp6zelK3 for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 07:24:41 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) by ietfa.amsl.com (Postfix) with ESMTP id 6638A1A6F92 for <gen-art@ietf.org>; Wed, 30 Apr 2014 07:24:41 -0700 (PDT)
X-AuditID: c1b4fb3a-f79106d0000013ca-5c-536107a7cbef
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 94.5C.05066.7A701635; Wed, 30 Apr 2014 16:24:39 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.191]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0174.001; Wed, 30 Apr 2014 16:24:38 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Thread-Topic: Gen-ART review of draft-ietf-bfd-tc-mib-06
Thread-Index: Ac9kXmZkqLpMSYwHT0aMT2C9XEwyyQFpj2wVmhlwdTDl24YX3Q==
Date: Wed, 30 Apr 2014 14:24:37 +0000
Message-ID: <gfjmp10isq90fl30al44p0hq.1398867874137@email.android.com>
References: <7594FB04B1934943A5C02806D1A2204B1D2E5726@ESESSMB209.ericsson.se> <f9e2fcab904e4a368ec04a5f694b48b0@BLUPR05MB151.namprd05.prod.outlook.com>, <084501cf647c$b1e9b700$15bd2500$@olddog.co.uk>
In-Reply-To: <084501cf647c$b1e9b700$15bd2500$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJLMWRmVeSWpSXmKPExsUyM+Jvje5y9sRggy+rRC1+9Nxgttjy6yuj xdVXn1kcmD2WLPnJ5LFi80pGjy+XP7MFMEdx2aSk5mSWpRbp2yVwZbyfeIm1YAdrxcLbvg2M q1i6GDk5JARMJA587GKGsMUkLtxbz9bFyMUhJHCUUeL/sy1QzhJGiZ6ZfUBVHBxsAhYS3f+0 QRpEBPQlus9NYwepYRboYZS4vPQ5G0iNsIC5xI33URA1FhLnDz9khrCdJJ792coGYrMIqErM /9zIClLOK+Amse6QGsSqE4wSi3t3soPEOQWsJbqWFoOUMwLd9v3UGiYQm1lAXOLWk/lMEDcL SCzZcx7qflGJl4//sULUGEi8PzefGcLWlli28DWYzSsgKHFy5hOWCYyis5CMmoWkZRaSlllI WhYwsqxiFC1OLS7OTTcy0kstykwuLs7P08tLLdnECIybg1t+W+1gPPjc8RCjAAejEg9v8ZfI YCHWxLLiytxDjNIcLErivJMWuQcLCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYOz1iZDx447k cJL8uoevzGPWnO1fpvfdrF784adNRNEN/pCOLewXjijevpk9rcTinPEsobhXf/Kv7XN8Mvf5 if/ZK+aH8N9m+TnD0cuWZ7tbg8FiPaX82YWRn04ffTThRnTSZMNfNp3r3fbdqapeYFqYcK/X aVvW17nXbAytlv+8M/nyAyWV1k9KLMUZiYZazEXFiQCbCMTjfAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/1V7nkzzf_9nU4k7yCH5PXLogYpw
Cc: 'General Area Review Team' <gen-art@ietf.org>, "draft-ietf-bfd-tc-mib.all@tools.ietf.org" <draft-ietf-bfd-tc-mib.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-tc-mib-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: Wed, 30 Apr 2014 14:24:43 -0000

Hi,

The reason I suggested to expand MIB in the Introduction is because it is e=
xpanded in the Abstract. Should the expansion then be removed from the Abst=
ract?

Regards,

Christer

Sent from my Sony Ericsson Xperia arc S

Adrian Farrel <adrian@olddog.co.uk> wrote:


Hi Christer,

Thanks for your efforts.

> Editorial nits:
>=A0
> Section 1 (Introduction):
>---------------------------------
>=A0
> Q_1:
>
> s/=94two MIB modules=94/=94two Management Information Base (MIB) modules=
=94

Note that "MIB" is found as "well known" at
http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt

Authors, please do not make this change.

Cheers,
Adrian


From nobody Wed Apr 30 12:42:19 2014
Return-Path: <nobo@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 0F0671A099C for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 12:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.152
X-Spam-Level: 
X-Spam-Status: No, score=-115.152 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.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, 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 qy-0GxllHoA6 for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 12:42:07 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 044021A04AF for <gen-art@ietf.org>; Wed, 30 Apr 2014 12:42:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1066; q=dns/txt; s=iport; t=1398886925; x=1400096525; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=QLqtsT/wTmhZmt1+89SBjsqNK0ViFjZDfVaHGTdGB5U=; b=lcw6na1tKeQt1zivHgYRV2ESuFdeA4Mn2epKqWz3wxrJRJN6nLzA7sy0 CYHM3Nd2i1r7/251fjXRsO5dIFSWKgp2toACyHJ6QBjjlXdmH/+pHHaYT GHJrPiJMqtLEdwsSGjaOA7TRBJvinaiotota7LzdFUCl/84pgVW2eFRhk 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAJ5RYVOtJV2Y/2dsb2JhbABZgmUhT1fESoEhFnSCJQEBAQMBOj8FCwIBCCIUEDIlAQEEAQ0NiDEIAQzJKRMEjiAxB4MkgRUErBKDMYIr
X-IronPort-AV: E=Sophos;i="4.97,960,1389744000"; d="scan'208";a="321548265"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP; 30 Apr 2014 19:42:05 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3UJg5fR020068 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 30 Apr 2014 19:42:05 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Wed, 30 Apr 2014 14:42:05 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Thread-Topic: Gen-ART review of draft-ietf-bfd-tc-mib-06
Thread-Index: Ac9kXmZkqLpMSYwHT0aMT2C9XEwyyQFpj2wVmhlwdTDl24YX3f//qIHg
Date: Wed, 30 Apr 2014 19:42:04 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E118B02@xmb-aln-x01.cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B1D2E5726@ESESSMB209.ericsson.se> <f9e2fcab904e4a368ec04a5f694b48b0@BLUPR05MB151.namprd05.prod.outlook.com>, <084501cf647c$b1e9b700$15bd2500$@olddog.co.uk> <gfjmp10isq90fl30al44p0hq.1398867874137@email.android.com>
In-Reply-To: <gfjmp10isq90fl30al44p0hq.1398867874137@email.android.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.212.75]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/TeWga2oNjjC_1dsZf0J6ONnwsb0
Cc: 'General Area Review Team' <gen-art@ietf.org>, "draft-ietf-bfd-tc-mib.all@tools.ietf.org" <draft-ietf-bfd-tc-mib.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-bfd-tc-mib-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: Wed, 30 Apr 2014 19:42:10 -0000

Hi Christer,

Many thanks for reviewing this document!

We have published -07, reflecting your comment.

https://datatracker.ietf.org/doc/draft-ietf-bfd-tc-mib/

Please see inline for response to each.

> Section 1 (Introduction):
> ---------------------------------
>=20
> Q_1:
>=20
>=20
> s/"two MIB modules"/"two Management Information Base (MIB) modules"

Authors had an offline discussion about this one, and concluded that the te=
rm is sufficiently well known and modification is not required.

> Section 4 (Security Considerations):
> ------------------------------------------------
>=20
> Q_4:
>=20
> The last sentence says:
>=20
>        "Therefore, this document has no impact on the security of the Int=
ernet."
>=20
> That sounds a little funny :) Wouldn't it be better to simply say:
>=20
>        "Therefore, this document does not introduce any additional securi=
ty
> considerations."

Good catch, it does sound a bit funny. We have replaced the text with what =
you have suggested.

Thanks again!

-Nobo


From nobody Wed Apr 30 13:40: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 52B461A093B for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 13:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 fuZ3PWCO1-9G for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 13:39:53 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id CE7581A0792 for <gen-art@ietf.org>; Wed, 30 Apr 2014 13:39:53 -0700 (PDT)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3UKdowG060500 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Apr 2014 15:39:51 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-173-172-146-58.tx.res.rr.com [173.172.146.58] claimed to be [10.0.1.29]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ben Campbell <ben@nostrum.com>
Date: Wed, 30 Apr 2014 15:39:50 -0500
X-Mao-Original-Outgoing-Id: 420583190.734361-c79b34c74dcf33eed9b94023e219fc8c
Content-Transfer-Encoding: quoted-printable
Message-Id: <6CC52ADD-76B8-4BA3-BC6C-ADAE24819D6D@nostrum.com>
To: draft-ietf-radext-dtls.all@tools.ietf.org
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/zmVyFYL7HBdanaRwz-HXrwwIqqc
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-dtls-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: Wed, 30 Apr 2014 20:39:58 -0000

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

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

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

Document: draft-ietf-radext-dtls-11
Reviewer: Ben Campbell
Review Date: 2014-04-30
IETF LC End Date: 2014-04-30

Summary: This draft is almost ready for publication as an experimental =
RFC. There are a few minor issues that should be considered prior to =
publication.

Note: I as assigned version 10, but 11 came out as I was working on the =
review. This review is for version 11.

Note: This review is incremental to an early (pre-submission) review I =
did for versions 7 and 8. Any comments from that review not repeated =
here have been addressed either in the text or in correspondence.

Major Issues:

None.

Minor Issues:

-- 3.2, last paragraph:

I'm still confused about how this is a bid down attack.=20

[The author replied that, 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.]

While I agree that's bad, I don't see how it qualifies as a bid-down =
attack. One assumes a malicious client already has access to the =
cleartext messages. Are we talking about an 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, but =
that is covered elsewhere.
Comment not addressed.

-- 6, 2nd and 3rd paragraph:

The RECOMMENDation to allow administrative entry of keys and to derive =
keys from a PRNG seem contradictory.


[The author responded that it's a requirement that implementors allow =
administrators to enter
strong keys. but I don't get that from the text, which both RECOMMENDS =
that the interface allow people to enter human readable hex strings, and =
that keys should be derived from a PRNG instead of letting =
administrators make up keys. How can it be both?

I don't see how an interface could prevent administrators from entering =
better keys. Perhaps the intent is to offer or interface with tools for =
random generation, or to scan entered keys for things with insufficient =
entropy?]
=20
-- 10.3, 2nd paragraph:

This is redundant and inconsistent with previous normative requirements =
in 5.1.1.=20

[Author replied that it's worth reiterating security issues, and that =
the sections were now consistent. But there's still conflicting =
normative statements here. 5.1.1 says implementations SHOULD monitor =
number of sessions. This section says MUST.

And I still assert that, even if the security issue is worth =
reiterating, it should not be reiterated _normatively_.  Doing so =
creates confusion about which text is authoritative, especially when =
they conflict. Even if they don't conflict now, it's easy for future =
updates to accidentally create conflicts.]

-- 10.4 5th and 6th paragraphs:

Paragraph 5 says credentials should be manually configured, and strongly =
tied to a host name. It is not clear to me from the text whether using a =
certificate (perhaps issued by a trusted CA) to bind the credentials to =
the hostname is permissible. The use of "manual" would seem to disallow =
that. But paragraph 6 talks about configuring trusted CAs.

[The author commented that dynamic discovery was out of scope--but I =
don't think anything about this implies dynamic discovery. (e.g. =
configuring a client to talk to foo.example.com, then using using a CA =
to validate that a server certificate to ensure that that server really =
is foo.example.com is not the same as dynamic discovery.]

-- 10.5, last paragraph:

This seems to be making normative statements about RADIUS/UDP. It's not =
appropriate to make those statements here unless this draft normatively =
updates RADIUS/UDP. (Which and experimental rfc shouldn't do.)

Nits and Editorial Comments:


-- idnits reports: The document seems to use 'NOT RECOMMENDED' as an RFC =
2119 keyword, but
     does not include the phrase in its RFC 2119 key words list.



-- 6.1, first paragraph: "subsystem does not need to multiple
   multiple sessions on one socket"

I think one instance of "multiple" was intended as a different word?




From nobody Wed Apr 30 15:22:48 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 7CFAD1A09BC for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 15:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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-xqvBkJmjGr for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 15:22:38 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 083A41A09AC for <gen-art@ietf.org>; Wed, 30 Apr 2014 15:22:37 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-57-107-66.dllstx.fios.verizon.net [173.57.107.66]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3UMMae8069085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Wed, 30 Apr 2014 17:22:36 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-57-107-66.dllstx.fios.verizon.net [173.57.107.66] claimed to be A-Jean-Mahoneys-MacBook-Pro.local
Message-ID: <536177AB.3060809@nostrum.com>
Date: Wed, 30 Apr 2014 17:22:35 -0500
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.4.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/YjDa-ad7-7-u4ykBUQNVf8BqhAc
Subject: [Gen-art] A *new* batch of IETF LC reviews  - 2014-04-30
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, 30 Apr 2014 22:22:41 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Brian Carpenter   2014-005-13  draft-ietf-netmod-system-mgmt-15 *

Roni Even         2014-05-12   draft-ietf-mpls-ldp-ip-pw-capability-07

Robert Sparks     2014-05-12   draft-ietf-ippm-2330-update-04

Scott Brim        2014-05-14   draft-ietf-cuss-sip-uui-isdn-08

* 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 nobody Wed Apr 30 18:39:35 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 85ABA1A09B2 for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 18:39:34 -0700 (PDT)
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 sSL_tNnL5KkA for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 18:39:32 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [88.190.25.44]) by ietfa.amsl.com (Postfix) with ESMTP id 255C71A09A9 for <gen-art@ietf.org>; Wed, 30 Apr 2014 18:39:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id ED4242240167; Thu,  1 May 2014 03:38:58 +0200 (CEST)
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 g8J4GihW4EdM; Thu,  1 May 2014 03:38:55 +0200 (CEST)
Received: from Thor.local (unknown [67.71.146.163]) by power.freeradius.org (Postfix) with ESMTPSA id 78AE32240093; Thu,  1 May 2014 03:38:54 +0200 (CEST)
Message-ID: <5361A5AD.4050608@deployingradius.com>
Date: Wed, 30 Apr 2014 21:38:53 -0400
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: <6CC52ADD-76B8-4BA3-BC6C-ADAE24819D6D@nostrum.com>
In-Reply-To: <6CC52ADD-76B8-4BA3-BC6C-ADAE24819D6D@nostrum.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/U3b_z8_AT3Og3lO2czK-DI2hRrc
Cc: 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 LC Review of draft-ietf-radext-dtls-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, 01 May 2014 01:39:34 -0000

Ben Campbell wrote:
> -- 3.2, last paragraph:
> 
> I'm still confused about how this is a bid down attack. 
> 
> [The author replied that, 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.]
> 
> While I agree that's bad, I don't see how it qualifies as a bid-down attack. One assumes a malicious client already has access to the cleartext messages. Are we talking about an 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, but that is covered elsewhere.
> Comment not addressed.

  The point of DTLS isn't just to protect from malicious clients.  It's
to protect clients and servers from malicious third parties.  Those
parties can read all RADIUS/UDP traffic now.  They will not be able to
read RADIUS/DTLS traffic.

  These third parties could actively cause DTLS to fail, and force the
client and server to use an insecure transport.  This sounds like a
downbidding attack to me.

  Do you have another definition for downbidding which you are using?
Or would another term be acceptable here?

> -- 6, 2nd and 3rd paragraph:
> 
> The RECOMMENDation to allow administrative entry of keys and to derive keys from a PRNG seem contradictory.
> 
> 
> [The author responded that it's a requirement that implementors allow administrators to enter
> strong keys. but I don't get that from the text, which both RECOMMENDS that the interface allow people to enter human readable hex strings, and that keys should be derived from a PRNG instead of letting administrators make up keys. How can it be both?

  Because the administrators have to enter the same key on both the
client and server.  If one machine auto-generated a secure pseudo-random
number, it would still have to be transported to the other, and entered
in an administration UI... via the method suggested in the document.

> I don't see how an interface could prevent administrators from entering better keys. Perhaps the intent is to offer or interface with tools for random generation, or to scan entered keys for things with insufficient entropy?]

  Have you ever entered a password in a poorly designed on-line form?
"special characters like !, %, &, $, etc. are not allowed".  Vendors do
this today with RADIUS systems, for the shared secret.  Such idiocy
should be discouraged.

> -- 10.3, 2nd paragraph:
> 
> This is redundant and inconsistent with previous normative requirements in 5.1.1. 
> 
> [Author replied that it's worth reiterating security issues, and that the sections were now consistent. But there's still conflicting normative statements here. 5.1.1 says implementations SHOULD monitor number of sessions. This section says MUST.
> 
> And I still assert that, even if the security issue is worth reiterating, it should not be reiterated _normatively_.  Doing so creates confusion about which text is authoritative, especially when they conflict. Even if they don't conflict now, it's easy for future updates to accidentally create conflicts.]

  I'll address that.

> -- 10.4 5th and 6th paragraphs:
> 
> Paragraph 5 says credentials should be manually configured, and strongly tied to a host name. It is not clear to me from the text whether using a certificate (perhaps issued by a trusted CA) to bind the credentials to the hostname is permissible. The use of "manual" would seem to disallow that. But paragraph 6 talks about configuring trusted CAs.
> 
> [The author commented that dynamic discovery was out of scope--but I don't think anything about this implies dynamic discovery. (e.g. configuring a client to talk to foo.example.com, then using using a CA to validate that a server certificate to ensure that that server really is foo.example.com is not the same as dynamic discovery.]

  I'm not sure what the objection here is.

  The point is that when a client connects to a server, the server uses
the source IP to determine which set of credentials to use.  There is no
"binding" of a certificate to a hostname.  The system is configured to
verify that "when you see packets from IP X, they must be using
certificate C".

  This configuration is independent of the certificate contents.

> -- 10.5, last paragraph:
> 
> This seems to be making normative statements about RADIUS/UDP. It's not appropriate to make those statements here unless this draft normatively updates RADIUS/UDP. (Which and experimental rfc shouldn't do.)

  The consensus of the WG was that the text belonged.

> Nits and Editorial Comments:
> 
> 
> -- idnits reports: The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but
>      does not include the phrase in its RFC 2119 key words list.

  OK.  I'll fix that.

> 
> -- 6.1, first paragraph: "subsystem does not need to multiple
>    multiple sessions on one socket"
> 
> I think one instance of "multiple" was intended as a different word?

  "manage multiple sessions on one socket"


From nobody Wed Apr 30 19:57:38 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 AA3271A09DD for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 19:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 eJU6OrMN6Vp2 for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 19:57:16 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id E08841A092F for <gen-art@ietf.org>; Wed, 30 Apr 2014 19:57:15 -0700 (PDT)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s412v7lg091081 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Apr 2014 21:57:09 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-173-172-146-58.tx.res.rr.com [173.172.146.58] claimed to be [10.0.1.29]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <5361A5AD.4050608@deployingradius.com>
Date: Wed, 30 Apr 2014 21:57:07 -0500
X-Mao-Original-Outgoing-Id: 420605827.283837-a52ecd1a60062d4a53ea0736b2290ebe
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA06E979-2FAC-4D2C-A6D0-F261F1AE3A51@nostrum.com>
References: <6CC52ADD-76B8-4BA3-BC6C-ADAE24819D6D@nostrum.com> <5361A5AD.4050608@deployingradius.com>
To: Alan DeKok <aland@deployingradius.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/sVmUFHtAYOeti9VDUIaIswOYeZk
Cc: 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 LC Review of draft-ietf-radext-dtls-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, 01 May 2014 02:57:22 -0000

Thanks for the quick response. Comments inline, with sections that do =
not appear to need further content removed.


On Apr 30, 2014, at 8:38 PM, Alan DeKok <aland@deployingradius.com> =
wrote:

> Ben Campbell wrote:
>> -- 3.2, last paragraph:
>>=20
>> I'm still confused about how this is a bid down attack.=20
>>=20
>> [The author replied that, 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
>> While I agree that's bad, I don't see how it qualifies as a bid-down =
attack. One assumes a malicious client already has access to the =
cleartext messages. Are we talking about an 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, but =
that is covered elsewhere.
>> Comment not addressed.
>=20
>  The point of DTLS isn't just to protect from malicious clients.  It's
> to protect clients and servers from malicious third parties.  Those
> parties can read all RADIUS/UDP traffic now.  They will not be able to
> read RADIUS/DTLS traffic.
>=20
>  These third parties could actively cause DTLS to fail, and force the
> client and server to use an insecure transport.  This sounds like a
> downbidding attack to me.
>=20
>  Do you have another definition for downbidding which you are using?
> Or would another term be acceptable here?

I tend to think of a bid-down attack as one in which security parameters =
are negotiated, and an attacker removes a more secure security mechanism =
to force endpoints to fall back to a less secure. But an outright =
failure of the DTLS handshake is more likely something less subtle--an =
outright impersonation attack, or a MiTM modification of content.

>=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
>>=20
>> [The author responded that it's a requirement that implementors allow =
administrators to enter
>> strong keys. but I don't get that from the text, which both =
RECOMMENDS that the interface allow people to enter human readable hex =
strings, and that keys should be derived from a PRNG instead of letting =
administrators make up keys. How can it be both?
>=20
>  Because the administrators have to enter the same key on both the
> client and server.  If one machine auto-generated a secure =
pseudo-random
> number, it would still have to be transported to the other, and =
entered
> in an administration UI... via the method suggested in the document.

I think it's reasonable to say that good administration practices =
involve random key generation, and that the interface should not prevent =
the entry of arbitrary hex strings. But the text says things like=20

"When creating keys, it is RECOMMENDED that keys be derived from a =
cryptographically secure pseudo-random number generator (CSPRNG) instead =
of allowing administrators to invent "secure" keys on theur  [sic--add =
that as an editorial comment] own." =20

That part seems to say explicitly that the implementation shouldn't let =
admins enter their own keys. (Which makes the bit about entering the key =
on the peer seem difficult.)

>=20
>> I don't see how an interface could prevent administrators from =
entering better keys. Perhaps the intent is to offer or interface with =
tools for random generation, or to scan entered keys for things with =
insufficient entropy?]
>=20
>  Have you ever entered a password in a poorly designed on-line form?
> "special characters like !, %, &, $, etc. are not allowed".  Vendors =
do
> this today with RADIUS systems, for the shared secret.  Such idiocy
> should be discouraged.

I accept that, and my real concern is not about allowing the admin to =
enter arbitrary hex strings. My concern is that it also says the admin =
should not be able to enter their own keys (see above.) How do you =
expect the interface to prevent the use of "invented on their own" keys, =
while allowing arbitrary hex strings?

[...]

>> -- 10.4 5th and 6th paragraphs:
>>=20
>> Paragraph 5 says credentials should be manually configured, and =
strongly tied to a host name. It is not clear to me from the text =
whether using a certificate (perhaps issued by a trusted CA) to bind the =
credentials to the hostname is permissible. The use of "manual" would =
seem to disallow that. But paragraph 6 talks about configuring trusted =
CAs.
>>=20
>> [The author commented that dynamic discovery was out of scope--but I =
don't think anything about this implies dynamic discovery. (e.g. =
configuring a client to talk to foo.example.com, then using using a CA =
to validate that a server certificate to ensure that that server really =
is foo.example.com is not the same as dynamic discovery.]
>=20
>  I'm not sure what the objection here is.
>=20
>  The point is that when a client connects to a server, the server uses
> the source IP to determine which set of credentials to use.  There is =
no
> "binding" of a certificate to a hostname.  The system is configured to
> verify that "when you see packets from IP X, they must be using
> certificate C".

Are you explicitly recommending against doing client authentication in =
the DTLS handshake? That seems inconsistent with the 3rd paragraph, that =
says "Any authentication credentials for that client are then determined =
solely from the client identity, and not from an IP address."

But, my concern was not just about servers authenticating clients. =
Paragraph 5 says:=20

"authentication credentials for that relationship should also be =
statically configured.  That is, a client connecting to a DTLS server =
SHOULD be pre-configured with the servers credentials (e.g. PSK or =
certificate)."

That seems to exclude the possibility of the client being pre-configured =
with a host name for the server, then the server presents a certificate =
issued from a trusted CA that includes that host name. This is a common =
TLS/DTLS use case.  Now, maybe you consider that to still be static =
configuration of credentials, since the host name and the trust anchor =
need to be statically configured. But your statement that there is no =
(as in never?) binding of a certificate to a host name makes me think =
otherwise. (Or at least confused me.) I assume you expect to do =
something with trusted CAs, since paragraph 6 talks about their =
configuration.

>=20
>  This configuration is independent of the certificate contents.
>=20
>> -- 10.5, last paragraph:
>>=20
>> This seems to be making normative statements about RADIUS/UDP. It's =
not appropriate to make those statements here unless this draft =
normatively updates RADIUS/UDP. (Which and experimental rfc shouldn't =
do.)
>=20
>  The consensus of the WG was that the text belonged.

I think we must be talking past each other. I read this to say that you =
expect people who are implementing/deploying RADIUS/UDP, who may not =
have seen any reason to read this experimental spec in the first place, =
to honor normative statements in this draft?=20

In general, it does not make sense for a given protocol to make =
normative statements about implementations that don't implement that =
protocol. If the working group wants to make this sort of statement, =
there are avenues to do so. But I don't think an experimental RFC is the =
right place.

[...]


From nobody Wed Apr 30 19:58:16 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 D4F221A09E6 for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 19:58:06 -0700 (PDT)
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 is1Ol4cbSj2Q for <gen-art@ietfa.amsl.com>; Wed, 30 Apr 2014 19:57:59 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id ED0311A09DC for <gen-art@ietf.org>; Wed, 30 Apr 2014 19:57:58 -0700 (PDT)
Received: by mail-ig0-f174.google.com with SMTP id h18so23731igc.7 for <gen-art@ietf.org>; Wed, 30 Apr 2014 19:57:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=XYPrw0mV3LJc0K9G05020EAORGso5gkVm1KwOnIj0M4=; b=OnfQ4S+egA4dvFjmzXDO+JtOM2EKh+ziZnGPaixjL+aKJjRmO/qHTqhireRlwjpQjV cygaUuxZUJ1+ctDCIOIdqe8Snj5C3dki1kT4B9j4YwMAnRKUzuse4cd9iKOJm7FstFbx 2OHPdjAi/iRMra4frIdt74qkTDTdq7zinHo8LndMOs0PfF1NSWi4tNxKFpcPJJ4bnQLu To8X4WjekHBYTug/oHvIXNj157ZhkXb+10lF4VYVvLuVaW/tqHDeK/1fSjfuleoIo4fY u8Dq0XmLWC4Rw2azwdL/UKu0bPkLdH1y6HxA10bUCmHDIKPFdyFVqFg2tpm95baO0LVA VmOA==
X-Received: by 10.50.49.44 with SMTP id r12mr132932ign.41.1398913077296; Wed, 30 Apr 2014 19:57:57 -0700 (PDT)
Received: from [192.168.178.20] (87.200.69.111.dynamic.snap.net.nz. [111.69.200.87]) by mx.google.com with ESMTPSA id sc2sm3996340igb.5.2014.04.30.19.57.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 30 Apr 2014 19:57:56 -0700 (PDT)
Message-ID: <5361B83A.3070404@gmail.com>
Date: Thu, 01 May 2014 14:58:02 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-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
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/e4vuTEPCeJ3PHzht1ayzHaBPw5U
Subject: [Gen-art] Gen-ART LC review of draft-ietf-netmod-system-mgmt-15.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, 01 May 2014 02:58:07 -0000

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

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

Document: draft-ietf-netmod-system-mgmt-15.txt
Reviewer: Brian Carpenter
Review Date: 2014-05-01
IETF LC End Date: 2014-05-13
IESG Telechat date:

Summary:  Ready
--------

Comments:
---------

This is a re-review during the 2nd Last Call. Thanks for responding to my eariler
comments. The latest changes all appear to be improvements.

