
From bclaise@cisco.com  Sat Feb  1 02:34:24 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 783A01ACCEB; Sat,  1 Feb 2014 02:34:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.035
X-Spam-Level: 
X-Spam-Status: No, score=-10.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sk2saEaII7Et; Sat,  1 Feb 2014 02:34:22 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 83C0F1ACCE6; Sat,  1 Feb 2014 02:34:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12626; q=dns/txt; s=iport; t=1391250858; x=1392460458; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=jOqX9eJ/fHJF8axNAscBhA/qv9uqQaN2VoZ5DhMlQes=; b=mzojymx8facxSGMUqy07eiwb1LTZSIbMF5a2eSCtOfZqzdMmnMT9mAGT CkGq6cUHLoCezkEnFyAbr2vcgOH9nh5LFhy6GYc/wDrevL0l8uWh6LjRR /NEQhBr5pdqqXL8rYA8AYCLbE57sQPozWPvbDz6nZ5gRQgD0HrNP2JFYv M=;
X-IronPort-AV: E=Sophos;i="4.95,760,1384300800"; d="scan'208,217";a="4512225"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 01 Feb 2014 10:34:17 +0000
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s11AYGVh006641; Sat, 1 Feb 2014 10:34:16 GMT
Message-ID: <52ECCDA8.10805@cisco.com>
Date: Sat, 01 Feb 2014 11:34:16 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, Paul Aitken <paitken@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-yourtchenko-cisco-ies.all@tools.ietf.org" <draft-yourtchenko-cisco-ies.all@tools.ietf.org>
References: <F5063677821E3B4F81ACFB7905573F24065A5E90F1@MX15A.corp.emc.com> <52EC12C4.3010503@cisco.com> <F5063677821E3B4F81ACFB7905573F24065A5E9111@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24065A5E9111@MX15A.corp.emc.com>
Content-Type: multipart/alternative; boundary="------------080900050700080403000406"
Cc: "ayourtch@cisco.com" <ayourtch@cisco.com>, "draft-yourtchenko-cisco-ies@tools.ietf.org" <draft-yourtchenko-cisco-ies@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-yourtchenko-cisco-ies-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Feb 2014 10:34:24 -0000

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

Kathleen,
>
> Hi Paul,
>
> In that case, please update the abstract and introduction to make the 
> intent of the document clear.
>
That makes sense.

Regards, Benoit
>
> It would be helpful for the reader to understand the intent as they 
> start reading the document.
>
> The discussion referenced was posted to ietf@ietf.org 
> <mailto:ietf@ietf.org>. I think folks are addressing that discussion, 
> so there is no need for me to jump into it.  Here is a link that 
> should pull up all the messages on this draft in the last month across 
> all mailing lists:
>
> https://mailarchive.ietf.org/arch/search/?q=yourtchenko&qdr=m
>
> Best regards,
>
> Kathleen
>
> *From:*Paul Aitken [mailto:paitken@cisco.com]
> *Sent:* Friday, January 31, 2014 4:17 PM
> *To:* Moriarty, Kathleen; gen-art@ietf.org; iesg@ietf.org; 
> draft-yourtchenko-cisco-ies.all@tools.ietf.org
> *Cc:* ayourtch@cisco.com; bclaise@cisco.com; 
> draft-yourtchenko-cisco-ies@tools.ietf.org
> *Subject:* Re: Gen-art review of draft-yourtchenko-cisco-ies-09
>
> Kathleen, All,
>
> Apologies for jumping in here, but I wasn't privvy to the earlier 
> discussion to which you allude.
>
>     Summary:  This draft extends RFC3954, but is specific to Cisco.
>
>
> No, this draft does not extend RFC 3954.
>
> RFC 3954 specifies the NFv9 Protocol and the associated Information 
> Model. The model is extensible, and I own the netflow-police hat for 
> reviewing, approving, and actioning NFv9 extensions.
>
> The IPFIX Protocol (RFC 7011) has its own Information Model (RFC 7012, 
> IANA) which is also extensible upon application to IANA, subject to 
> expert review by IE-doctors (RFC 7013).
>
> The yourtchenko-cisco-ies draft extends the IPFIX Information model. 
> Per section 6 of the draft, "IANA Considerations":
>
>   
>     This document specifies several new IPFIX Information Elements in the
>     IPFIX Information Element registry
>
>
> The IPFIX Information Model was initially based upon the NFv9 
> Information Model. Indeed, the two are generally considered to be 
> synonymous.
>
> The extensions which are being added to the IPFIX model seek to retain 
> that synonymity by describing NFv9 elements which were not known or 
> defined at the time RFC 3954 was written. These can be adopted into 
> the IPFIX Information Model to retain compatibility, rather than 
> defining equivalent IPFIX elements with different IDs from NFv9 and 
> thus complicating life for every netflow collector.
>
> Note that this is not a change to either the NFv9 or IPFIX protocols.
>
>
> P.
>


--------------080900050700080403000406
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Kathleen,<br>
    </div>
    <blockquote
      cite="mid:F5063677821E3B4F81ACFB7905573F24065A5E9111@MX15A.corp.emc.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;
	color:black;}
span.mh
	{mso-style-name:m_h;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi
            Paul,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">In
            that case, please update the abstract and introduction to
            make the intent of the document clear.&nbsp; </span></p>
      </div>
    </blockquote>
    That makes sense.<br>
    <br>
    Regards, Benoit<br>
    <blockquote
      cite="mid:F5063677821E3B4F81ACFB7905573F24065A5E9111@MX15A.corp.emc.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">It
            would be helpful for the reader to understand the intent as
            they start reading the document.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The
            discussion referenced was posted to <a
              moz-do-not-send="true" href="mailto:ietf@ietf.org">ietf@ietf.org</a>.&nbsp;
            I think folks are addressing that discussion, so there is no
            need for me to jump into it. &nbsp;Here is a link that should
            pull up all the messages on this draft in the last month
            across all mailing lists:<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><a
              moz-do-not-send="true"
              href="https://mailarchive.ietf.org/arch/search/?q=yourtchenko&amp;qdr=m">https://mailarchive.ietf.org/arch/search/?q=yourtchenko&amp;qdr=m</a><o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best
            regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Kathleen<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">
                Paul Aitken [<a class="moz-txt-link-freetext" href="mailto:paitken@cisco.com">mailto:paitken@cisco.com</a>] <br>
                <b>Sent:</b> Friday, January 31, 2014 4:17 PM<br>
                <b>To:</b> Moriarty, Kathleen; <a class="moz-txt-link-abbreviated" href="mailto:gen-art@ietf.org">gen-art@ietf.org</a>;
                <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a>;
                <a class="moz-txt-link-abbreviated" href="mailto:draft-yourtchenko-cisco-ies.all@tools.ietf.org">draft-yourtchenko-cisco-ies.all@tools.ietf.org</a><br>
                <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:ayourtch@cisco.com">ayourtch@cisco.com</a>; <a class="moz-txt-link-abbreviated" href="mailto:bclaise@cisco.com">bclaise@cisco.com</a>;
                <a class="moz-txt-link-abbreviated" href="mailto:draft-yourtchenko-cisco-ies@tools.ietf.org">draft-yourtchenko-cisco-ies@tools.ietf.org</a><br>
                <b>Subject:</b> Re: Gen-art review of
                draft-yourtchenko-cisco-ies-09<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <div>
          <p class="MsoNormal" style="margin-bottom:12.0pt">Kathleen,
            All,<br>
            <br>
            Apologies for jumping in here, but I wasn't privvy to the
            earlier discussion to which you allude.<o:p></o:p></p>
        </div>
        <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
          <div>
            <p class="MsoPlainText">Summary:&nbsp; This draft extends <span
                style="font-size:10.0pt;font-family:&quot;Courier
                New&quot;">RFC3954, but is specific to Cisco.</span><o:p></o:p></p>
          </div>
        </blockquote>
        <p class="MsoNormal"><br>
          No, this draft does not extend RFC 3954.<br>
          <br>
          RFC 3954 specifies the NFv9 Protocol and the associated
          Information Model. The model is extensible, and I own the
          netflow-police hat for reviewing, approving, and actioning
          NFv9 extensions.<br>
          <br>
          The IPFIX Protocol (RFC 7011) has its own Information Model
          (RFC 7012, IANA) which is also extensible upon application to
          IANA, subject to expert review by IE-doctors (RFC 7013).<br>
          <br>
          The yourtchenko-cisco-ies draft extends the IPFIX Information
          model. Per section <span class="mh">6 of the draft, "IANA
            Considerations":</span><o:p></o:p></p>
        <pre><o:p>&nbsp;</o:p></pre>
        <pre>&nbsp;&nbsp; This document specifies several new IPFIX Information Elements in the<o:p></o:p></pre>
        <pre>&nbsp;&nbsp; IPFIX Information Element registry<o:p></o:p></pre>
        <p class="MsoNormal"><br>
          The IPFIX Information Model was initially based upon the NFv9
          Information Model. Indeed, the two are generally considered to
          be synonymous.<br>
          <br>
          The extensions which are being added to the IPFIX model seek
          to retain that synonymity by describing NFv9 elements which
          were not known or defined at the time RFC 3954 was written.
          These can be adopted into the IPFIX Information Model to
          retain compatibility, rather than defining equivalent IPFIX
          elements with different IDs from NFv9 and thus complicating
          life for every netflow collector.<br>
          <br>
          Note that this is not a change to either the NFv9 or IPFIX
          protocols.<br>
          <br>
          <br>
          P. <br>
          <br>
          <o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------080900050700080403000406--

From brian.e.carpenter@gmail.com  Sun Feb  2 20:18:10 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 20E951A0099 for <gen-art@ietfa.amsl.com>; Sun,  2 Feb 2014 20:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VMKhuq20-O6I for <gen-art@ietfa.amsl.com>; Sun,  2 Feb 2014 20:18:08 -0800 (PST)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 9022C1A0040 for <gen-art@ietf.org>; Sun,  2 Feb 2014 20:18:08 -0800 (PST)
Received: by mail-pd0-f178.google.com with SMTP id y13so6397461pdi.37 for <gen-art@ietf.org>; Sun, 02 Feb 2014 20:18:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=Ak6Pt7KcmnfLMXu0xH92/oXauS/5JyFZ2SZM2biJN4o=; b=RS/sWJyXrWS3XajDhpAYAlbNvIcgOq4Jl0qIyAd2hUZsscg3gP2+1ERvPlXturKhqo iluXhf15KWnbI4huQZ9h0Z/hlq3SGP6DbzZl90fy/HnjoLbgewE9aq7aib5e7nOOaZ6e /KKqiQ1AHFwm9xrkJwuP0+wlWPrQCB0bMtCfxnbdMDADdsDyufJMIBgn8TvW9P5Jp/rk KG7HbmxxagBafK7jWAFkCiSjnYH59J4uGr8Yigv7c8R36T9Nzn2Hm1AJJciS5ScAZ+S/ 6ZLOk4/meePSGNU7/Gb61rs90D7047VG5rLF9UHe3R4EUockUY0lfWi2JIJ0MRusroal rPXg==
X-Received: by 10.66.149.73 with SMTP id ty9mr34999529pab.36.1391401084172; Sun, 02 Feb 2014 20:18:04 -0800 (PST)
Received: from [192.168.178.23] (148.200.69.111.dynamic.snap.net.nz. [111.69.200.148]) by mx.google.com with ESMTPSA id ja8sm10769814pbd.3.2014.02.02.20.18.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Feb 2014 20:18:03 -0800 (PST)
Message-ID: <52EF1879.7000708@gmail.com>
Date: Mon, 03 Feb 2014 17:18:01 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-soc-overload-control.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-soc-overload-control-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: Mon, 03 Feb 2014 04:18:10 -0000

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

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

Document: draft-ietf-soc-overload-control-14.txt
Reviewer: Brian Carpenter
Review Date: 2013-12-15
IETF LC End Date: 2013-12-23
IESG Telechat date: 2014-02-06

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

Comments:
---------

Most of my LC comments were resolved, but one small change is
expected (see below). Also the IESG has to fix the nit mentioned
below.

Note: http://datatracker.ietf.org/ipr/1364/

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

"5.6.  Forwarding the overload control parameters

   Overload control is defined in a hop-by-hop manner.  Therefore,
   forwarding the contents of the overload control parameters is
   generally NOT RECOMMENDED and should only be performed if permitted
   by the configuration of SIP servers.  This means that a SIP proxy
   SHOULD strip the overload control parameters inserted by the client
   before proxying the request further downstream."

I think the reader should be reminded at this point that the proxy also
behaves as a client, so will immediately re-insert its own "oc" parameters.
(In fact it would be very odd if the proxy supported overload control
upstream but not downstream.)  Vijay suggested: I can insert the following
sentence as the last sentence of the lone paragraph in S5.6:

   "Of course, the proxy can add overload control parameters pertinent
    to itself in the Via header it inserts in the request going
    downstream."

This would be fine.

Nit:
----

I hope this is a nit: the Last Call says it's for "Internet Standard"
but surely it's intended to be "Proposed Standard"?



From dromasca@avaya.com  Mon Feb  3 06:04:44 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 3429B1A01C8 for <gen-art@ietfa.amsl.com>; Mon,  3 Feb 2014 06:04:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wK8teT9dtZl for <gen-art@ietfa.amsl.com>; Mon,  3 Feb 2014 06:04:42 -0800 (PST)
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 0643A1A017D for <gen-art@ietf.org>; Mon,  3 Feb 2014 03:03:27 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FALt271LGmAcV/2dsb2JhbABZgmshOFe+GIEFFnSCJQEBAQEDAQEBD1wXBAIBBgINBAQBAQEKHQcnCxQJCAIEARIIGodjAQyOeZEwq2cTBI5YOAaDHoEUBJ8aizGDLYIq
X-IronPort-AV: E=Sophos;i="4.95,771,1384318800"; d="scan'208";a="47832698"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 03 Feb 2014 06:03:26 -0500
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 03 Feb 2014 05:52:38 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Mon, 3 Feb 2014 12:03:24 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "A. Jean Mahoney" <mahoney@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Gen-art]  Review: draft-ietf-xrblock-rtcp-xr-qoe-13
Thread-Index: AQHPHrJ1Xf//aHWEzEqwkFm1jyPQ7JqjYXBw
Date: Mon, 3 Feb 2014 11:03:24 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E3E8D4E@AZ-FFEXMB04.global.avaya.com>
References: <52EB0069.1060900@nostrum.com> <52EBEBA5.9090402@joelhalpern.com>
In-Reply-To: <52EBEBA5.9090402@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Gen-art] Review: draft-ietf-xrblock-rtcp-xr-qoe-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 14:04:44 -0000

Thanks for the careful reviews and the useful comments, Joel.=20

Regards,

Dan
(as XRBLOCK co-chair)

> -----Original Message-----
> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Joel M.
> Halpern
> Sent: =E9=E5=ED=A0=E5 31 =E9=F0=E5=E0=F8 2014 20:30
> To: A. Jean Mahoney; gen-art@ietf.org
> Subject: [Gen-art] Review: draft-ietf-xrblock-rtcp-xr-qoe-13
>=20
> This revision address all of my comments and is ready for publication as =
a
> Proposed Standard.
>=20
> Yours,
> Joel
>=20
> On 1/30/14, 8:46 PM, A. Jean Mahoney wrote:
> > Joel Halpern        2013-11-27   draft-ietf-xrblock-rtcp-xr-qoe-13*
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

From Francis.Dupont@fdupont.fr  Mon Feb  3 06:49:01 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 470C61A00E2 for <gen-art@ietfa.amsl.com>; Mon,  3 Feb 2014 06:49:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.187
X-Spam-Level: 
X-Spam-Status: No, score=-0.187 tagged_above=-999 required=5 tests=[HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id whpcqWxe4UU4 for <gen-art@ietfa.amsl.com>; Mon,  3 Feb 2014 06:49:00 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id DC7941A0035 for <gen-art@ietf.org>; Mon,  3 Feb 2014 06:48:59 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id s13EmxIu056358; Mon, 3 Feb 2014 15:48:59 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201402031448.s13EmxIu056358@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 03 Feb 2014 15:48:59 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: draft-housley-pkix-test-oids.all@tools.ietf.org
Subject: [Gen-art] review of draft-housley-pkix-test-oids-00.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, 03 Feb 2014 14:49:01 -0000

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

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

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

Document: draft-housley-pkix-test-oids-00.txt
Reviewer: Francis Dupont
Review Date: 20140122
IETF LC End Date: 20140211
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - typo 3 page 2:
    ... The actual
   polices used for production certificates has a significant impact
        ^
BTW if the word is policies than has -> have

Regards

Francis.Dupont@fdupont.fr

From scott.brim@gmail.com  Mon Feb  3 08:59:19 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 8FBA71A015C for <gen-art@ietfa.amsl.com>; Mon,  3 Feb 2014 08:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6rOFwkJxdWg for <gen-art@ietfa.amsl.com>; Mon,  3 Feb 2014 08:59:17 -0800 (PST)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id CFEB51A0123 for <gen-art@ietf.org>; Mon,  3 Feb 2014 08:59:17 -0800 (PST)
Received: by mail-ob0-f170.google.com with SMTP id va2so8193192obc.1 for <gen-art@ietf.org>; Mon, 03 Feb 2014 08:59:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=46VDduNBuAlqBBtnRiZM6EimtMqV7XHY3Ap1faDxVVw=; b=CuElROYUzKa+dfVS+tNJ7SBFqMSjqt6v8zlCwUELll+Q1tirJGacYvAuKWvnztW1t0 ywHVyItF26ZyWK3ZTjtsxxiGdqyYpDoYX7du8GujwNQ4opoOvq86mWKTDtR6tB67axtP mqsr4F73z8bIfpdwMrB2uIqPJ7Ngbv7wVCiQYJCqr4rz/0ZJ0JAYlJPBjM8LY/dsf+wg R+5onpjcagB9TBe7ksTfLTHEOKj83ScU6IGvhVgyWu1G8JsmqC3+Eb64qhubuHfYnE0L Ar5o2Y+zQVGxwiNT+RhxmUaID5wkoWAAa9jU/jfFGR8uLp8PWbkUPiuXJZCM6TGW3yLk HykQ==
X-Received: by 10.60.165.72 with SMTP id yw8mr1167587oeb.71.1391446754188; Mon, 03 Feb 2014 08:59:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 3 Feb 2014 08:58:54 -0800 (PST)
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 3 Feb 2014 11:58:54 -0500
Message-ID: <CAPv4CP_aQKceoZ+dL0BoEaaqVMXe++bKGe=4SSrNE73rP4u1ag@mail.gmail.com>
To: gen-art <gen-art@ietf.org>,  draft-ietf-avtcore-clksrc all <draft-ietf-avtcore-clksrc.all@tools.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] gen-art telechat review of draft-ietf-avtcore-clksrc-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 16:59:19 -0000

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

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

Document: draft-ietf-avtcore-clksrc-09
Reviewer: Scott Brim
Review Date: 2014-02-03
IETF LC End Date: 2014-01-16
IESG Telechat date: 2014-02-06

Summary: Ready with a minor issue

Major issues: none

Minor issues:

This is the same version I reviewed at LC. After discussion with the
authors I have changed my question to a recommendation.

In 6.1.2 and 6.1.3 it says: "If the answerer rejects the offer because the
available reference clocks are incompatible, the rejection MUST
contain at least one timestamp reference clock specification usable by
the answerer."  I have learned that sending this reference clock
specification is not required for the protocol to function. It is for
the offerer's information, so that maybe next time the negotiation
will succeed.

- Since including the reference clock is not required for the protocol
per se to work, consider making this MUST a SHOULD.

- In any case, this needs to be justified. Even something as simple as
adding "for the offerer's information" could be sufficient, although
usually more would be expected.

Scott

From aland@deployingradius.com  Mon Feb  3 09:24:45 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 E5C171A0162; Mon,  3 Feb 2014 09:24:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R3Zx34Xt3LN9; Mon,  3 Feb 2014 09:24:41 -0800 (PST)
Received: from power.freeradius.org (power.freeradius.org [88.190.25.44]) by ietfa.amsl.com (Postfix) with ESMTP id B4A791A016B; Mon,  3 Feb 2014 09:24:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id D59A42240729; Mon,  3 Feb 2014 18:24:38 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZHFtGJAWsTD; Mon,  3 Feb 2014 18:24:38 +0100 (CET)
Received: from Thor.local (unknown [70.50.217.206]) by power.freeradius.org (Postfix) with ESMTPSA id 463E722406AE; Mon,  3 Feb 2014 18:24:37 +0100 (CET)
Message-ID: <52EFD0D4.8090507@deployingradius.com>
Date: Mon, 03 Feb 2014 12:24:36 -0500
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
References: <C3DF6E99-2B7E-4606-A8F6-5D76C338B265@nostrum.com> <52E16808.3070308@deployingradius.com> <807D4BB4-7C1C-4668-8F31-85CD1B080EE6@nostrum.com>
In-Reply-To: <807D4BB4-7C1C-4668-8F31-85CD1B080EE6@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: radext@ietf.org, draft-ietf-radext-dtls.all@tools.ietf.org, "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-Art Early Review of draft-ietf-radext-dtls-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Feb 2014 17:24:46 -0000

Ben Campbell wrote:
> Version 08 partially addresses this by changing "NOT RECOMMENDED" to lower case. I don't think that's sufficient; it's not a good idea to rely on case alone to distinguish normative from non-normative text. I propose changing the sense of the statement to something along the lines of "The author recommends...". 

  OK.  I'll word-smith it.

> The text to which I refer says "It is RECOMMENDED that all RADIUS clients and servers implement this specification, or [RFC6614]." That seems to to apply a new normative statement to all RADIUS clients and servers, and does not in any way seem scoped to "RADIUS/DTLS clients and servers".

  OK.  I'll word-smith it.

>>> -- General:  It might be worth some text on why this is experimental rather than informational. Is there any plan to evaluate the implementation results? Is there an expectation that a future RADIUS/DTLS spec could become standards-track? Is there any plan to evaluate the outcome of this document?
>>  It's probably easiest to reference Section 1.3 of RFC 6614.  The
>> issues are the same.
> 
> I don't think that's the best approach. That discussion is specific to 6614. Referencing it would leave the reader to infer how that discussion would apply to this draft. I think it would be better to include a similar discussion here.

  OK.  I'll do that.

>>> -- Section 1, 2nd paragraph:
>>>
>>> Isn't this true for almost any use of IPSec? Is there some specific reason this is worse for RADIUS than for other protocols?
>>  It's true for most protocols.
> 
> It's worth mentioning that.

  OK.

> [...]
> 
>>> The firewall rule recommendations in the 3rd sentence seems odd, since it seems like any protocol over DTLS would pass. Also, does this imply a recommendation that firewalls with DPI be used in the first place, since the absence of such a firewall has the same effect as having one that doesn't enforce the protocol? (Is there a reason a protocol spec should recommend firewall rules in the first place, other than to mention places where certain firewall rules might prevent interfere with operation?)
>>  I'll clarify it, and move it to the Security Considerations section.
> 
> The clarification added at the end of  section 10 in version 08 mostly addresses this. But I assume that the point is to make sure no one sends non-protected RADIUS over that port, but it doesn't prevent someone from sending some other protocol over DTLS over the same port, correct? If so, I think that's worth a mention.

  Well... I can connect to port 443 via TLS, and then send random data.
   I don't see why this issue needs to be called out for this protocol.
 But sure.

> The text seems to say something to the effect of " Some RADIUS clients have historically been implemented as multiple independent processes, therefore [all] RADIUS clients should use a local proxy".  I think you mean to say something more like "Some RADIUS clients have historically been implemented as multiple independent processes; clients that are implemented that way should use a local proxy." 

  Sure.  It already says that later, but I'll word-smith it.

>>  When security is OK and the tunneled data is RADIUS, it's OK to
>> silently drop the unexpected RADIUS packets.  Doing so doesn't cause any
>> problems.
> 
> It would be helpful to add a couple of sentences to that effect. 

  OK.

>>> -- 5.1.1, 4th paragraph:
>>>
>>> This paragraph rephrases 2119 normative language with more normative language. That creates confusion about which text is authoritative. I suggest either keeping the second paragraph and deleting the first, or make the second non-normative.
>>  I'm not sure what you mean here.  The two paragraphs discuss different
>> things, so deleting one isn't possible.
> 
> The opening sentence of the second paragraph says, "The above paragraph can be rephrased more generically", then appears to go on to do so. That makes it sound like the second paragraph asserting effectively the same normative requirements in more general terms. If you intend each paragraph to stand alone, then I suggest deleting that sentence.

  OK.

>>> -- 5.1.1, 6th paragraph: "The timestamp SHOULD be updated ..."
>>>
>>> Why not MUST?
>>  The granularity could be 1 second, with packets being received 1000's
>> of times per second.
>>
> 
> It would be helpful to elaborate on that in the text. Your comment makes me thing it would be also worth having some guidance on a reasonable resolution for the time stamp.
> 
> If you really expect 1 second resolutions, then it might be better to say something like "The timestamp MUST be updated if a valid message or heartbeat is received during the last time interval."

  OK.

>>> The RECOMMENDation to allow administrative entry of keys and to derive keys from a PRNG seem contradictory.
>>  The idea is that admins shouldn't be entering "0xabababab" as a key.
>> Instead, they get secure keys from a secure location.  People are
>> notoriously bad at creating randomness.
>>
> 
> So paragraph 3 is a requirement on the administrator, rather than on the implementor? Or do you mean to say the implementation should provide tools for random key generation?

  It's a requirement that implementors allow administrators to enter
strong keys.

> [...]
> 
> 
>>> -- 9
>>>
>>> Why not choose a new port? Is there absolute certainty this won't conflict with the previous usage? I do note that 6414 made the same choice, so I guess consistency with radius/TLS has some value. But that draft talks about compatibility between radsec and radius/tls, which is not mentioned here.
>>  No one is using UDP/2083 for anything.  Re-using it is OK.
> 
> Does that mean that RadSec is not used at all by anyone? or that this draft is compatible with it?

  RadSec is RADIUS over TLS on TCP port 2083.  No one uses UDP port 2083
for anything.

>>> It would be helpful to have guidance on how to match a certificate to a client or server identity,
>>  I'll add a note to see RFC 6614 Section 2.5.
> 
> I see you added that to section 10.3, 3rd paragraph. But does that contradict the statement in 2.2.1 that 6614 section 2.5 does not apply to RADIUS/DTLS?

  It's a typo.  The reference should be to 6614 Section 2.4.

>>> This is redundant with previous normative requirements. (Also contradictory, since the previous text said "SHOULD", and contradictory guidance on what to do when the limit is exceeded.)
>>  I've fixed the text to be consistent.
> 
> The paragraph is still redundant with the new text in 5.1.1 (which says you MUST either drop old sessions or limit creation of new ones.)

  I'm OK with that.  The Security Considerations section can re-iterate
security issues.

> [ re: source IP filtering ]
>
> I agree it makes sense to point out that IP filtering might be helpful. But I think a normative SHOULD is excessive.

  I disagree.

>>  The recommendation is a SHOULD so that it does not conflict with
>> dynamic discovery.
>> 
> If it stays normative, It would be worth mentioning that as an example of why it's a SHOULD rather than a MUST.

  Which it says.

> The whole point of a certificate is to bind a key pair to an identity (often, a name.)
> 
> Example: I enter the name "trusted-peer.example.com" in a table. If a (perhaps dynamically discovered) peer presents certificate with a CN or SAN that matches "trusted-peer.example.com", and that certificate is issued by a CA that I trust, then I trust that peer. 

  This document doesn't do dynamic discovery for peers.  So it's OK to
suggest that statically configuring relationships is a good idea.

>>> Paragraph 6 seems to entirely contradict paragraph 5 by recommending private CAs, and accepting any peer that presents a cert signed by that CA. That's pretty much the opposite of statically configured credentials. (Paragraph 8 also seems to contradict the static configuration part.)
>>  Both client and server still need to be configured with the private
>> CA.  The alternative is to allow anyone to connect with any credentials,
>> which seems odd.
>>
> 
> That's static configuration of your trusted CA(s). That's not the same thing as static configuration of peer credentials, and it doesn't imply the static relationship between clients and servers mentioned in paragraph 5.

  We're getting into the weeds here.  I view dynamic discovery of
servers as an issue for the dynamic discovery document.  Therefore,
credentials should be statically configured.

  However, a *server* can allow clients who present the correct
credentials.  This is not dynamic discovery of clients.

> [...]
> 
>>> -- 10.4:
>>>
>>> The guidance in the last paragraph does not make sense. The section seems to say that NATs will break radius/dtls, so you should use dtls when behind a NAT.
>>  RADIUS/UDP clients should not be behind a NAT.  I'll clarify.
> 
> Do you mean RADIUS/UDP or RADIUS/DTLS? If the former, then that brings back the problem of making normative statements about the base protocol.

  I mean RADIUS/UDP.  It's not really changing RADIUS/UDP.  RADIUS/UDP
was designed before NATs were in wide-spread use, and with the intention
of using it in a flat / open network.  So it's silent on the issue of
NATs, and many other topics.

> Also, I'm still confused by the fact the the 2nd sentence of the last paragraph says "If clients are located behind a NAT gateway, then a secure transport such as DTLS MUST be used." Given that the previous paragraph seems to say that RADIUS/DTLS has issues over NAT, I'm surprised to see it listed as mitigating NATs.

  Yes.  DTLS helps avoid some problems of NATs, but not all.  This is
the nature of a NAT: they screw with the traffic and make life harder
for the application behind a NAT.

>>> Redundant normative requirements (This is at least the third time the separate process issue and local proxy guidance has been described.)
>>  It's a security considerations section, and needs to mention this.  It
>> refers to Section 6.1, and adds new text explaining the security
>> benefits of the approach.
> 
> I agree it should be reiterated, but not _normatively_. In generally, you don't want to have the same normative requirement stated more than once. It makes sense for the security consideration section to say something like "Section XX recommends that clients use a local proxy"  But it's best to avoid any language that obscures which bit of text is authoritative for a given normative requirement. (There can be only one...)

  I'll take a look at word-smithing it.

> I also notice the language here also fails to account for the fact that the requirement only applies to clients implemented as multiple independent instances. This could be fixed by something really simple like saying "... such clients ..." instead of "... clients... " in the second paragraph.

  I'll update it.

  Alan DeKok.

From rjsparks@nostrum.com  Mon Feb  3 15:06:30 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 5B0261A027B; Mon,  3 Feb 2014 15:06:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBEVV-F5TbfS; Mon,  3 Feb 2014 15:06:29 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6253F1A0267; Mon,  3 Feb 2014 15:06:29 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s13N6Tco047547 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Mon, 3 Feb 2014 17:06:29 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52F020FE.6090904@nostrum.com>
Date: Mon, 03 Feb 2014 17:06:38 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, pcp@ietf.org, draft-ietf-pcp-nat64-prefix64@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] Gen-art LC review: draft-ietf-pcp-nat64-prefix64-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, 03 Feb 2014 23:06:30 -0000

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

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

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

Document: draft-ietf-pcp-nat64-prefix64-04
Reviewer: Robert Sparks
Review Date: 3-Jan-2014
IETF LC End Date: 4-Jan-2014
IESG Telechat date: Unknown

Summary: Ready with Nits

Nits/editorial comments:

There are several references to expired drafts (some very expired).
If those are not going to progress, the details you wanted to call out 
would be better moved here.

It's not clear which of the results in nat64-experiments you are 
pointing to for support for this document.
Is the reference necessary? If so, can it be made more specific.

In section 4.1, you restate the allowed values for length from RFC6052. 
Consider making the statement
even clearer that these values are a consequence of RFC6052 and aren't 
being defined by this document.
Something like "The allowed values are specified in RFC6052 (currently 
4,5,6,7,8,12).
(I almost didn't include this since that set's not likely to change, but 
somebody might copy the style...)

RjS




From brian.e.carpenter@gmail.com  Mon Feb  3 16:31:07 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 DFDF21A026A for <gen-art@ietfa.amsl.com>; Mon,  3 Feb 2014 16:31:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GcRzxUZrXPQH for <gen-art@ietfa.amsl.com>; Mon,  3 Feb 2014 16:31:06 -0800 (PST)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 375ED1A0264 for <gen-art@ietf.org>; Mon,  3 Feb 2014 16:31:06 -0800 (PST)
Received: by mail-pa0-f50.google.com with SMTP id kp14so7770580pab.37 for <gen-art@ietf.org>; Mon, 03 Feb 2014 16:31:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=DgE6U4cvydxxGemBcNcLNa2wX/fsRDmruHCs3ovTIX8=; b=gb+xS/vKPoACFGC5TKe6u21LDJzJOWKnwvZTAFqf0myQPJ9v0+AsjoWqWaf6kbOlDx hOXufCBXk+7pOgkGfgwKcEHVnYL3fSfvXTP7YYb5JQm9bSAFXk9mfH3Hz/zLUOtCidqw ItxgMz49ecDf+1xev08bEKcVMOj/Vl/NABMOm7QJIkWmrcvofGFqek6kr5iC35N7yKfC wy5O+/Ehd0Xdzn/HYxpXW/96HYUWj9mmJJwQqEexw3YVouLdET33lQg/8f+jTGl9xiJN aKYzI3awaKZFybEsKsn6ZPTy+DRJxkqpWFXN8ExykRUbz2kxz5lC3JHKK2jnvOwtwmQo 8xIA==
X-Received: by 10.66.137.109 with SMTP id qh13mr10673219pab.140.1391473866188;  Mon, 03 Feb 2014 16:31:06 -0800 (PST)
Received: from [130.216.38.108] (sc-cs-567-laptop.cs.auckland.ac.nz. [130.216.38.108]) by mx.google.com with ESMTPSA id tu3sm60115033pbc.40.2014.02.03.16.31.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Feb 2014 16:31:05 -0800 (PST)
Message-ID: <52F034C9.60802@gmail.com>
Date: Tue, 04 Feb 2014 13:31:05 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-manet-nhdp-olsrv2-tlv-extension.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-ART LC review of draft-ietf-manet-nhdp-olsrv2-tlv-extension-01.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, 04 Feb 2014 00:31:08 -0000

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

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

Document: draft-ietf-manet-nhdp-olsrv2-tlv-extension-01.txt
Reviewer: Brian Carpenter
Review Date: 2014-02-04
IETF LC End Date: 2014-02-07
IESG Telechat date:

Summary:  Ready
--------

Comments:
---------

This draft is well-written and clear.

It retro-fits extensibility to two existing specifications.
As an author of RFC 6709 I find this an interesting exercise. Do
the hints in http://tools.ietf.org/html/rfc6709#section-4 help,
especially bullet 2?

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

It is highly unusual for a draft to formally update another draft
(draft-ietf-manet-olsrv2), even though the latter is approved and
in the RFC queue. If we were a rational organisation, that draft
would be updated before publication.

(The writeup actually says "The Optimized Link State Routing Protocol
version 2 (OLSRv2) has been published as Standards Track." but that is
inaccurate.)


From yang.r.yang@gmail.com  Mon Feb  3 20:57:11 2014
Return-Path: <yang.r.yang@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E43F1A034D for <gen-art@ietfa.amsl.com>; Mon,  3 Feb 2014 20:57:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QGcBFEE3ZALD for <gen-art@ietfa.amsl.com>; Mon,  3 Feb 2014 20:57:09 -0800 (PST)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 7030C1A02D2 for <gen-art@ietf.org>; Mon,  3 Feb 2014 20:57:09 -0800 (PST)
Received: by mail-pa0-f53.google.com with SMTP id lj1so7969756pab.40 for <gen-art@ietf.org>; Mon, 03 Feb 2014 20:57:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=LpXpBcAt/yT7k9cseNvWwPw1j8wq6MmnApPRfgXEU3E=; b=T2p6bD82gpj9F1cRb+YcccvF3ZMt/6JVzqABAfvIKmAzVbuH/K7U0fa9skSdWeGBbX p5PqJ3T60FQ1/ZC85EgniRJ/5WR/c20XXXMTNb2Sn8DdZO+JayUQ8G3HY6u8tj9mYo6a w/yK+97FvJd1UeHVKznV3yCAwlGt3o4QLU/Zl7b9/RPvGTgN3Y+4tFOSL76/++xtJIxc xohKkGg8y7V7eyX3a52XwxMZ85dWftatcZ0Vy1dhBid0Im0ONnfnd6JMwE5epkXh4Fgc I585vXXv5PJshKLGIrRDat4KGIG8LKVrlqoYsaTSwq3/Jr47jtxXWKY6YLUekJk8USDp deKA==
MIME-Version: 1.0
X-Received: by 10.68.0.99 with SMTP id 3mr11642541pbd.68.1391489829334; Mon, 03 Feb 2014 20:57:09 -0800 (PST)
Sender: yang.r.yang@gmail.com
Received: by 10.68.144.168 with HTTP; Mon, 3 Feb 2014 20:57:09 -0800 (PST)
Received: by 10.68.144.168 with HTTP; Mon, 3 Feb 2014 20:57:09 -0800 (PST)
In-Reply-To: <CF0BE8F0.C456C%w.roome@alcatel-lucent.com>
References: <CABkgnnVN=mxwwvbMKw=F-+cfgxYUrO8hzmF0r14ApfP7cXAcTQ@mail.gmail.com> <CANUuoLpVQ71VM=M8J7FmYiJK6VwdF7JvqzG36ymGWAr2Z2qXQg@mail.gmail.com> <CF0BE8F0.C456C%w.roome@alcatel-lucent.com>
Date: Mon, 3 Feb 2014 23:57:09 -0500
X-Google-Sender-Auth: NTW2NwMg996edYH2Yq95Nqi7lFM
Message-ID: <CANUuoLrf=iF9Swrn6CAoNSTEr=qVvq-PVNEyrPjGsqKWKY3oTQ@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Wendy Roome <w.roome@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=bcaec5215553fc77ef04f18d780b
Cc: gen-art@ietf.org, "N:" <draft-ietf-alto-protocol.all@tools.ietf.org>, Sebastian Kiesel <ietf-alto@skiesel.de>, Richard Alimi <ralimi@google.com>, "Reinaldo Penno, \(repenno\)" <repenno@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-alto-protocol-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 04:57:11 -0000

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

Hi Martin,

Wendy gave a good summary on the reasoning of not using URIs. We are
wondering if you may have some additional comments so that we can address.
Thank you so much!

Richard
On Jan 27, 2014 11:16 AM, "Wendy Roome" <w.roome@alcatel-lucent.com> wrote:

> Here's my response for "why resource ids instead of uris":
>
> An "ALTO Server" is a collection of services provided by a provider. That
> provider may distribute these services over several different physical
> servers, and that distribution may change over time. If we used URIs to
> identify those services, the IDs would have to change whenever the provider
> redistributed services.
>
> Therefore we defined "Resource IDs" as persistent, location-independent,
> IDs for those services. Resource IDs must be unique, but only within the
> context of one provider's services -- that is, the services defined by the
> tree of IRDs reachable from a root IRD. That IRD tree maps those Resource
> IDs to URIs, and allows the provider to change the mapping without
> disrupting clients. Thus ALTO Resource IDs are relative to the URI of the
> provider's IRD tree. If a provider had to use globally unique,
> location-dependent URIs, instead of location-independent relative IDs, the
> provider would have an unnecessary administrative burden.
>
> (Yes, I know "URIs", unlike URLs, are supposed to be "location
> independent." But let's face reality: that only works if there's some
> higher level mapping of URIs to locations. For all practical purposes,
> "URI" means host-specific "URL".)
>
> Another way to look at it is that "Resource IDs" are like using relative
> addresses within a web page. They make it easier to move a tree of related
> pages from one host to another.
>
> - Wendy Roome
>
> From: "Y. Richard Yang" <yry@cs.yale.edu>
> Date: Sun, January 26, 2014 at 16:40
> To: Martin Thomson <martin.thomson@gmail.com>
> Cc: "N:" <draft-ietf-alto-protocol.all@tools.ietf.org>, "gen-art@ietf.org"
> <gen-art@ietf.org>, Richard Alimi <ralimi@google.com>, "Reinaldo Penno,
> (repenno)" <repenno@cisco.com>, Wendy Roome <w.roome@alcatel-lucent.com>,
> Sebastian Kiesel <ietf-alto@skiesel.de>
> Subject: Re: Gen-ART review of draft-ietf-alto-protocol-25
>
>
> Section 10.2 defines a resource ID.  Why do this when you could use
> URIs?  After all, that's what URIs are for.  I realize that this would
> be something of a major change to the protocol, but I think that the
> question is particularly important.
>

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

<p dir=3D"ltr">Hi Martin,</p>
<p dir=3D"ltr">Wendy gave a good summary on the reasoning of not using URIs=
. We are wondering if you may have some additional comments so that we can =
address. Thank you so much!</p>
<p dir=3D"ltr">Richard</p>
<div class=3D"gmail_quote">On Jan 27, 2014 11:16 AM, &quot;Wendy Roome&quot=
; &lt;<a href=3D"mailto:w.roome@alcatel-lucent.com">w.roome@alcatel-lucent.=
com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style=3D"font-size:14px;font-family:Calibri,sans-serif;word-wrap:break=
-word"><div>Here&rsquo;s my response for &ldquo;why resource ids instead of=
 uris&rdquo;:</div><div><br></div><div>An &ldquo;ALTO Server&rdquo; is a co=
llection of services provided by a provider. That provider may distribute t=
hese services over several different physical servers, and that distributio=
n may change over time. If we used URIs to identify those services, the IDs=
 would have to change whenever the provider redistributed services.</div>
<div><br></div><div>Therefore we defined &ldquo;Resource IDs&rdquo; as pers=
istent, location-independent, IDs for those services. Resource IDs must be =
unique, but only within the context of one provider&rsquo;s services &mdash=
; that is, the services defined by the tree of IRDs reachable from a root I=
RD. That IRD tree maps those Resource IDs to URIs, and allows the provider =
to change the mapping without disrupting clients. Thus ALTO Resource IDs ar=
e relative to the URI of the provider&rsquo;s IRD tree. If a provider had t=
o use globally unique, location-dependent URIs, instead of location-indepen=
dent relative IDs, the provider would have an unnecessary administrative bu=
rden.</div>
<div><br></div><div>(Yes, I know &ldquo;URIs&rdquo;, unlike URLs, are suppo=
sed to be &ldquo;location independent.&rdquo; But let&rsquo;s face reality:=
 that only works if there&rsquo;s some higher level mapping of URIs to loca=
tions. For all practical purposes, &ldquo;URI&rdquo; means host-specific &l=
dquo;URL&rdquo;.)</div>
<div><br></div><div>Another way to look at it is that &ldquo;Resource IDs&r=
dquo; are like using relative addresses within a web page. They make it eas=
ier to move a tree of related pages from one host to another.</div><div><br=
></div><div>
<span style=3D"white-space:pre-wrap">	</span>- Wendy Roome</div><div><br></=
div><span><div style=3D"border-right:medium none;padding-right:0in;padding-=
left:0in;padding-top:3pt;text-align:left;font-size:11pt;border-bottom:mediu=
m none;font-family:Calibri;border-top:#b5c4df 1pt solid;padding-bottom:0in;=
border-left:medium none">
<span style=3D"font-weight:bold">From: </span> &quot;Y. Richard Yang&quot; =
&lt;<a href=3D"mailto:yry@cs.yale.edu" target=3D"_blank">yry@cs.yale.edu</a=
>&gt;<br><span style=3D"font-weight:bold">Date: </span> Sun, January 26, 20=
14 at 16:40<br>
<span style=3D"font-weight:bold">To: </span> Martin Thomson &lt;<a href=3D"=
mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.com=
</a>&gt;<br><span style=3D"font-weight:bold">Cc: </span> &quot;N:&quot; &lt=
;<a href=3D"mailto:draft-ietf-alto-protocol.all@tools.ietf.org" target=3D"_=
blank">draft-ietf-alto-protocol.all@tools.ietf.org</a>&gt;, &quot;<a href=
=3D"mailto:gen-art@ietf.org" target=3D"_blank">gen-art@ietf.org</a>&quot; &=
lt;<a href=3D"mailto:gen-art@ietf.org" target=3D"_blank">gen-art@ietf.org</=
a>&gt;, Richard Alimi &lt;<a href=3D"mailto:ralimi@google.com" target=3D"_b=
lank">ralimi@google.com</a>&gt;, &quot;Reinaldo Penno, (repenno)&quot; &lt;=
<a href=3D"mailto:repenno@cisco.com" target=3D"_blank">repenno@cisco.com</a=
>&gt;, Wendy Roome &lt;<a href=3D"mailto:w.roome@alcatel-lucent.com" target=
=3D"_blank">w.roome@alcatel-lucent.com</a>&gt;, Sebastian Kiesel &lt;<a hre=
f=3D"mailto:ietf-alto@skiesel.de" target=3D"_blank">ietf-alto@skiesel.de</a=
>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span> Re: Gen-ART review of dra=
ft-ietf-alto-protocol-25<br></div><div><br></div><br style=3D"text-indent:0=
px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:no=
rmal;font-weight:normal;line-height:normal;text-transform:none;font-size:me=
dium;white-space:normal;font-family:Calibri;word-spacing:0px">
<span style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;te=
xt-align:start;font-style:normal;display:inline!important;font-weight:norma=
l;float:none;line-height:normal;text-transform:none;font-size:medium;white-=
space:normal;font-family:Calibri;word-spacing:0px">Section 10.2 defines a r=
esource ID. &nbsp;Why do this when you could use</span><br style=3D"text-in=
dent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-st=
yle:normal;font-weight:normal;line-height:normal;text-transform:none;font-s=
ize:medium;white-space:normal;font-family:Calibri;word-spacing:0px">
<span style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;te=
xt-align:start;font-style:normal;display:inline!important;font-weight:norma=
l;float:none;line-height:normal;text-transform:none;font-size:medium;white-=
space:normal;font-family:Calibri;word-spacing:0px">URIs? &nbsp;After all, t=
hat&#39;s what URIs are for. &nbsp;I realize that this would</span><br styl=
e=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:s=
tart;font-style:normal;font-weight:normal;line-height:normal;text-transform=
:none;font-size:medium;white-space:normal;font-family:Calibri;word-spacing:=
0px">
<span style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;te=
xt-align:start;font-style:normal;display:inline!important;font-weight:norma=
l;float:none;line-height:normal;text-transform:none;font-size:medium;white-=
space:normal;font-family:Calibri;word-spacing:0px">be something of a major =
change to the protocol, but I think that the</span><br style=3D"text-indent=
:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:=
normal;font-weight:normal;line-height:normal;text-transform:none;font-size:=
medium;white-space:normal;font-family:Calibri;word-spacing:0px">
<span style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;te=
xt-align:start;font-style:normal;display:inline!important;font-weight:norma=
l;float:none;line-height:normal;text-transform:none;font-size:medium;white-=
space:normal;font-family:Calibri;word-spacing:0px">question is particularly=
 important.</span></span></div>

</blockquote></div>

--bcaec5215553fc77ef04f18d780b--

From Chris.Dearlove@baesystems.com  Tue Feb  4 02:30:27 2014
Return-Path: <Chris.Dearlove@baesystems.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 4E5971A03EB for <gen-art@ietfa.amsl.com>; Tue,  4 Feb 2014 02:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.435
X-Spam-Level: 
X-Spam-Status: No, score=-7.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2pgmq3BZhdW5 for <gen-art@ietfa.amsl.com>; Tue,  4 Feb 2014 02:30:25 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 814A11A03EA for <gen-art@ietf.org>; Tue,  4 Feb 2014 02:30:24 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,778,1384300800"; d="scan'208";a="346441948"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 04 Feb 2014 10:30:23 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
X-IronPort-AV: E=Sophos;i="4.95,778,1384300800"; d="scan'208";a="44883521"
Received: from glkxh0003v.greenlnk.net ([10.109.2.34]) by baemasodc005.greenlnk.net with ESMTP; 04 Feb 2014 10:30:23 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.106]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.03.0174.001; Tue, 4 Feb 2014 10:30:23 +0000
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "draft-ietf-manet-nhdp-olsrv2-tlv-extension.all@tools.ietf.org" <draft-ietf-manet-nhdp-olsrv2-tlv-extension.all@tools.ietf.org>, "General Area Review Team" <gen-art@ietf.org>
Thread-Topic: Gen-ART LC review of draft-ietf-manet-nhdp-olsrv2-tlv-extension-01.txt
Thread-Index: AQHPIUBxOT5Y+MAr2kaLGnYrShfTy5qk37dA
Date: Tue, 4 Feb 2014 10:30:23 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D4024C752@GLKXM0002V.GREENLNK.net>
References: <52F034C9.60802@gmail.com>
In-Reply-To: <52F034C9.60802@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-manet-nhdp-olsrv2-tlv-extension-01.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, 04 Feb 2014 10:30:27 -0000

VGhhbmtzIGZvciB0aGF0IHJldmlldy4NCg0KVG8gYmUgY2xlYXIsIHRoZSBmb2xsb3dpbmcgY29t
bWVudHMgYXJlIG1pbmUsIG5vdCBhZ3JlZWQgd2l0aCB0aGUgb3RoZXIgYXV0aG9ycyAodGhvdWdo
IEkgaGF2ZSBubyByZWFzb24gdG8gYmVsaWV2ZSB0aGV5IHdvdWxkIGRpc2FncmVlIHdpdGggdGhl
bSkuDQoNCkkgdGFrZSB5b3VyIGNvbW1lbnQgb24gdGhlIHJhdGlvbmFsIG9yZ2FuaXNhdGlvbi4g
QnV0IHRoYXQgZG9jdW1lbnQgaXMgYWxyZWFkeSBiYWRseSBkZWxheWVkLCBhbmQgZGVsYXlpbmcg
aXQgZnVydGhlciBmb3Igc29tZXRoaW5nIG5lZWRlZCBvbmx5IGJ5IGV4dGVuc2lvbnMgKHdlIGhh
dmUgb25lIHBsYW5uZWQgZXhwZXJpbWVudGFsIGV4dGVuc2lvbiAsbm90IHlldCBhY2NlcHRlZCBi
eSB0aGUgV0cgdGhvdWdoIGluIHRoYXQgcHJvY2VzcywgdGhhdCBuZWVkcyB0aGlzKSB3b3VsZCBJ
IHRoaW5rIGhhdmUgYmVlbiBhIGZpbmFsIHN0cmF3IHRvIGJyZWFrIHNvbWUgY2FtZWwncyBiYWNr
LiBBbmQgd2Ugd291bGQgc3RpbGwgbmVlZGVkIHRvIGhhdmUgdXBkYXRlZCBOSERQLCB3aGljaCBz
ZWVtZWQgY2xlYW5lciBmcm9tIGEgc2VwYXJhdGUgZG9jdW1lbnQgcmF0aGVyIHRoYW4gYnVyaWVk
IGluIE9MU1J2Mi4gV2hpbGUgbm90IGZvcm1hbGx5IGltcG9zaW5nIG9uIG90aGVyIHByb3RvY29s
cyB1c2luZyBSRkMgNTQ0NCwgd2UnZCBsaWtlIHRvIHRoaW5rIHRoaXMgaXMgZ29vZCBhZHZpY2Ug
Zm9yIHRoZW0uDQoNClRoZSBhdXRob3JzIGF0dGVtcHRlZCB0byBmb2xsb3cgZ3VpZGVsaW5lcyBz
aW1pbGFyIHRvIHRob3NlIGluIFJGQyA2NzA5LCBidXQgbW9zdCBvZiBvdXIgd29yayBwcmVkYXRl
ZCBpdCAoSSBkaWQgc2F5IGJhZGx5IGRlbGF5ZWQpIHNvIHdlIGRpZG4ndCB1c2UgaXQgc3BlY2lm
aWNhbGx5LiBJdCdzIGEgZ29vZCBsaXN0IGFuZCB3ZSdkIHVzZSBpdCBpbiB0aGUgZnV0dXJlLiBX
ZSBnb3Qgc29tZSB0aGluZ3MgcmlnaHQgdGhlcmUuIChNb3N0IGltcG9ydGFudGx5LCB3ZSBlbnN1
cmVkIHRoYXQgdG8gY29udmV5IGluZm9ybWF0aW9uLCBtZXJlIHByZXNlbmNlIG9mIGFuIGFkZHJl
c3Mgd2FzIG5vdCBlbm91Z2gsIHRoYXQgd291bGQgaGF2ZSBiZWVuIHZlcnkgbGltaXRpbmcuKSBX
ZSBtaXNzZWQgc29tZSB0aGluZ3MsIHRoaXMgd291bGQgYmUgb25lLiBTZWN1cml0eSBkZWxheWVk
IHVzLiBXZSBsZWFybmVkIHNvbWUgdGhpbmdzLg0KDQpUaGUgd3JpdGV1cCB3aWxsIGJlIHRydWUg
c29vbiA7KSBXZSBhcmUgZW5nYWdlZCBpbiBwcmUtQVVUSDQ4IHF1ZXN0aW9ucyBhbmQgZWRpdHMg
d2l0aCB0aGUgUkZDIEVkaXRvciBvbiB0aGUgZG9jdW1lbnQgKE9MU1J2MikuIFlvdSB3aWxsIGJl
IHBsZWFzZWQgdG8ga25vdyB0aGF0IHdoZXJlIHdlIGhhdmUgaWRlbnRpZmllZCBhIGZldyB0aGlu
Z3MgdGhhdCB3b3VsZCBoYXZlIHJlc3VsdGVkIGluIGltbWVkaWF0ZSBlcnJhdGEsIHdlIGhhdmUg
aW5zdGVhZCBwdXQgdGhlbSBpbnRvIHRoZSBlZGl0IChhbmQgYXMgdGVjaG5pY2FsLCB0aGUgUkZD
IEVkaXRvciBoYXMgcmVmZXJyZWQgYmFjayB0byB0aGUgc3BvbnNvcmluZyBBRCB0byBPSykuDQoN
Ci0tIA0KQ2hyaXN0b3BoZXIgRGVhcmxvdmUNClNlbmlvciBQcmluY2lwYWwgRW5naW5lZXIsIENv
bW11bmljYXRpb25zIEdyb3VwDQpDb21tdW5pY2F0aW9ucywgTmV0d29ya3MgYW5kIEltYWdlIEFu
YWx5c2lzIENhcGFiaWxpdHkNCkJBRSBTeXN0ZW1zIEFkdmFuY2VkIFRlY2hub2xvZ3kgQ2VudHJl
DQpXZXN0IEhhbm5pbmdmaWVsZCBSb2FkLCBHcmVhdCBCYWRkb3csIENoZWxtc2ZvcmQsIENNMiA4
SE4sIFVLDQpUZWw6ICs0NCAxMjQ1IDI0MjE5NMKgfCAgRmF4OiArNDQgMTI0NSAyNDIxMjQNCmNo
cmlzLmRlYXJsb3ZlQGJhZXN5c3RlbXMuY29tIHwgaHR0cDovL3d3dy5iYWVzeXN0ZW1zLmNvbQ0K
DQpCQUUgU3lzdGVtcyAoT3BlcmF0aW9ucykgTGltaXRlZA0KUmVnaXN0ZXJlZCBPZmZpY2U6IFdh
cndpY2sgSG91c2UsIFBPIEJveCA4NywgRmFybmJvcm91Z2ggQWVyb3NwYWNlIENlbnRyZSwgRmFy
bmJvcm91Z2gsIEhhbnRzLCBHVTE0IDZZVSwgVUsNClJlZ2lzdGVyZWQgaW4gRW5nbGFuZCAmIFdh
bGVzIE5vOiAxOTk2Njg3DQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBCcmlh
biBFIENhcnBlbnRlciBbbWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbV0gDQpTZW50
OiAwNCBGZWJydWFyeSAyMDE0IDAwOjMxDQpUbzogZHJhZnQtaWV0Zi1tYW5ldC1uaGRwLW9sc3J2
Mi10bHYtZXh0ZW5zaW9uLmFsbEB0b29scy5pZXRmLm9yZzsgR2VuZXJhbCBBcmVhIFJldmlldyBU
ZWFtDQpTdWJqZWN0OiBHZW4tQVJUIExDIHJldmlldyBvZiBkcmFmdC1pZXRmLW1hbmV0LW5oZHAt
b2xzcnYyLXRsdi1leHRlbnNpb24tMDEudHh0DQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0hIFdB
Uk5JTkcgISAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tIFRoaXMgbWVzc2FnZSBvcmlnaW5hdGVzIGZy
b20gb3V0c2lkZSBvdXIgb3JnYW5pc2F0aW9uLCBlaXRoZXIgZnJvbSBhbiBleHRlcm5hbCBwYXJ0
bmVyIG9yIGZyb20gdGhlIGludGVybmV0Lg0KQ29uc2lkZXIgY2FyZWZ1bGx5IHdoZXRoZXIgeW91
IHNob3VsZCBjbGljayBvbiBhbnkgbGlua3MsIG9wZW4gYW55IGF0dGFjaG1lbnRzIG9yIHJlcGx5
Lg0KRm9sbG93IHRoZSAnUmVwb3J0IFN1c3BpY2lvdXMgRW1haWxzJyBsaW5rIG9uIElUIG1hdHRl
cnMgZm9yIGluc3RydWN0aW9ucyBvbiByZXBvcnRpbmcgc3VzcGljaW91cyBlbWFpbCBtZXNzYWdl
cy4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tDQoNCkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQu
IEZvciBiYWNrZ3JvdW5kIG9uIEdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdCA8aHR0cDov
L3dpa2kudG9vbHMuaWV0Zi5vcmcvYXJlYS9nZW4vdHJhYy93aWtpL0dlbkFydGZhcT4uDQoNClBs
ZWFzZSByZXNvbHZlIHRoZXNlIGNvbW1lbnRzIGFsb25nIHdpdGggYW55IG90aGVyIExhc3QgQ2Fs
bCBjb21tZW50cyB5b3UgbWF5IHJlY2VpdmUuDQoNCkRvY3VtZW50OiBkcmFmdC1pZXRmLW1hbmV0
LW5oZHAtb2xzcnYyLXRsdi1leHRlbnNpb24tMDEudHh0DQpSZXZpZXdlcjogQnJpYW4gQ2FycGVu
dGVyDQpSZXZpZXcgRGF0ZTogMjAxNC0wMi0wNA0KSUVURiBMQyBFbmQgRGF0ZTogMjAxNC0wMi0w
Nw0KSUVTRyBUZWxlY2hhdCBkYXRlOg0KDQpTdW1tYXJ5OiAgUmVhZHkNCi0tLS0tLS0tDQoNCkNv
bW1lbnRzOg0KLS0tLS0tLS0tDQoNClRoaXMgZHJhZnQgaXMgd2VsbC13cml0dGVuIGFuZCBjbGVh
ci4NCg0KSXQgcmV0cm8tZml0cyBleHRlbnNpYmlsaXR5IHRvIHR3byBleGlzdGluZyBzcGVjaWZp
Y2F0aW9ucy4NCkFzIGFuIGF1dGhvciBvZiBSRkMgNjcwOSBJIGZpbmQgdGhpcyBhbiBpbnRlcmVz
dGluZyBleGVyY2lzZS4gRG8gdGhlIGhpbnRzIGluIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1s
L3JmYzY3MDkjc2VjdGlvbi00IGhlbHAsIGVzcGVjaWFsbHkgYnVsbGV0IDI/DQoNCk1pbm9yIElz
c3VlczoNCi0tLS0tLS0tLS0tLQ0KDQpJdCBpcyBoaWdobHkgdW51c3VhbCBmb3IgYSBkcmFmdCB0
byBmb3JtYWxseSB1cGRhdGUgYW5vdGhlciBkcmFmdCAoZHJhZnQtaWV0Zi1tYW5ldC1vbHNydjIp
LCBldmVuIHRob3VnaCB0aGUgbGF0dGVyIGlzIGFwcHJvdmVkIGFuZCBpbiB0aGUgUkZDIHF1ZXVl
LiBJZiB3ZSB3ZXJlIGEgcmF0aW9uYWwgb3JnYW5pc2F0aW9uLCB0aGF0IGRyYWZ0IHdvdWxkIGJl
IHVwZGF0ZWQgYmVmb3JlIHB1YmxpY2F0aW9uLg0KDQooVGhlIHdyaXRldXAgYWN0dWFsbHkgc2F5
cyAiVGhlIE9wdGltaXplZCBMaW5rIFN0YXRlIFJvdXRpbmcgUHJvdG9jb2wgdmVyc2lvbiAyIChP
TFNSdjIpIGhhcyBiZWVuIHB1Ymxpc2hlZCBhcyBTdGFuZGFyZHMgVHJhY2suIiBidXQgdGhhdCBp
cw0KaW5hY2N1cmF0ZS4pDQoNCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqClRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2ht
ZW50cyBhcmUgY29uZmlkZW50aWFsIHRvIHRoZSBpbnRlbmRlZApyZWNpcGllbnQgYW5kIG1heSBh
bHNvIGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZApyZWNpcGllbnQg
cGxlYXNlIGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtIGFuZCBub3RpZnkgdGhlIHNlbmRlci4K
WW91IHNob3VsZCBub3QgY29weSBpdCBvciB1c2UgaXQgZm9yIGFueSBwdXJwb3NlIG5vciBkaXNj
bG9zZSBvcgpkaXN0cmlidXRlIGl0cyBjb250ZW50cyB0byBhbnkgb3RoZXIgcGVyc29uLgoqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKgo=


From meral.shirazipour@ericsson.com  Tue Feb  4 02:31:50 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 760CB1A03E7 for <gen-art@ietfa.amsl.com>; Tue,  4 Feb 2014 02:31:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YjhC4UlG9wN7 for <gen-art@ietfa.amsl.com>; Tue,  4 Feb 2014 02:31:48 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 500941A03D9 for <gen-art@ietf.org>; Tue,  4 Feb 2014 02:31:48 -0800 (PST)
X-AuditID: c6180641-b7f2f8e000002cdc-be-52f0c194ec7c
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id DC.E2.11484.491C0F25; Tue,  4 Feb 2014 11:31:48 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0387.000; Tue, 4 Feb 2014 05:31:47 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-xrblock-rtcp-xr-synchronization.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-synchronization.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call draft-ietf-xrblock-rtcp-xr-synchronization-07
Thread-Index: Ac8hlCDu13JJMQR2QFirFof+iT/45Q==
Date: Tue, 4 Feb 2014 10:31:46 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A32D38FEB@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.10]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D38FEBeusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsUyuXRPuO6Ugx+CDI5e0rFY92kNm8XVV59Z HJg8liz5yeTx5fJntgCmKC6blNSczLLUIn27BK6MeSffsBXs0qnY0XCMsYFxpnoXIyeHhICJ xNEjz9kgbDGJC/fWA9lcHEICRxgldh79wgrhLGOU+PV5NztIFZuAhcT238/BEiIC6xgljl19 DNYuLOAhsfffSjBbRMBX4trZNUwQtp7Etb0dzCA2i4CKxKU1n1lAbF6gmgM7z4MNZQRa/f0U RD2zgLjErSfzmSBOEpBYsuc8M4QtKvHy8T9WCFtJYtLSc6wQ9fkSrx/eZIWYKShxcuYTlgmM QrOQjJqFpGwWkjKIuI7Egt2f2CBsbYllC18zw9hnDjxmQhZfwMi+ipGjtDi1LDfdyHATIzAi jkmwOe5gXPDJ8hCjNAeLkjjvl7fOQUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoY9z96H+uf X3f2f62q6y83qXlxeevLNyXkHux/E754Au8ByRkvN1n8aNhaG6r5Nfpc7c3TnoV/tHd8PnpY pFGZU+q68QzeyZ4fFy6zeadfa/1u5uYU3ncW/I5Tam3OlZw25fNVF31096hJRcmLsq3/3n2p 2WOuyTY1Ofm19dRfCnp2jxKMOvfXKbEUZyQaajEXFScCAI7JuxdWAgAA
Subject: [Gen-art] Gen-ART Last Call draft-ietf-xrblock-rtcp-xr-synchronization-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, 04 Feb 2014 10:31:50 -0000

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

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

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

Document: draft-ietf-xrblock-rtcp-xr-synchronization-07
Reviewer: Meral Shirazipour
Review Date: 2014-02-04
IETF LC End Date:  2014-02-04
IESG Telechat date: NA


Summary:
This draft is ready to be published as Standards Track RFC but I have some =
minor comments.

Major issues:
N/A
Minor issues:
N/A

Nits/editorial comments:
-[Page 4], Section 1.4,
"used by network manager"---->"used by the network manager"


-[Page 8], Section 4.2,
"In this document, the value I=3D00 is the reserved value and MUST NOT be u=
sed."
It would be good to add if it should be ignored by receiver if used, or dis=
card the whole Synchronization Offset Report ...

-General: would be good to add caption to Figures p.5 and p.7

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

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-xrblock-rtcp-xr-synchronization=
-07<o:p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2014-02-04<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date:&nbsp; 2014-02-04<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: NA<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is ready to be published as Standards Tra=
ck RFC but I have some minor comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major issues:<o:p></o:p></p>
<p class=3D"MsoNormal">N/A<o:p></o:p></p>
<p class=3D"MsoNormal">Minor issues:<o:p></o:p></p>
<p class=3D"MsoNormal">N/A<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], Section 1.4,<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;used by network manager&quot;----&gt;&quot;use=
d by the network manager&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 8], Section 4.2, <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;In this document, the value I=3D00 is the rese=
rved value and MUST NOT be used.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">It would be good to add if it should be ignored by r=
eceiver if used, or discard the whole Synchronization Offset Report ...<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-General: would be good to add caption to Figures p.=
5 and p.7<o:p></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_ABCAA4EF18F17B4FB619EA93DEF7939A32D38FEBeusaamb107erics_--

From martin.thomson@gmail.com  Tue Feb  4 10:14:33 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 7B1A61A0100 for <gen-art@ietfa.amsl.com>; Tue,  4 Feb 2014 10:14:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tm1xRU1pq4YM for <gen-art@ietfa.amsl.com>; Tue,  4 Feb 2014 10:14:31 -0800 (PST)
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 2BD371A013B for <gen-art@ietf.org>; Tue,  4 Feb 2014 10:14:30 -0800 (PST)
Received: by mail-wg0-f48.google.com with SMTP id x13so13017267wgg.3 for <gen-art@ietf.org>; Tue, 04 Feb 2014 10:14:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=tpCqf99TLjni0vCkR5/v4lCX+3rkbCdoADnfatn6JMc=; b=HGX23uaeFFmXTDCABn/9mu90eTriMRxsVAlCNjDporlAvdlHQGsHCPp25zJJSBhTtf /xw0YbF5KgeB0UFL2nByL9rQs9IwhybuLqiwVa2sfq80Km3ws2aBLsi/VmrqPaIjiJUi JAjf7gALZwR/vr0EXMbAtbcwp9sSWoVDdpVszNuMmyS2W3TLF8KwQUVOL56yc5zMibBs OOrjn+xhF6x8YTeDYKfIRanI+56v7YWnEM2d8dVWz9CcZBeZ6WMLRPVQLFWfPXIX78J/ eU1VLPMxqPJeld2lRNfQa6Itj9bAmkken6pRfn6rGYQqoM+jQTIEn4WTQ4KYJsLIiU8R qg8Q==
MIME-Version: 1.0
X-Received: by 10.180.74.200 with SMTP id w8mr13713175wiv.58.1391537669173; Tue, 04 Feb 2014 10:14:29 -0800 (PST)
Received: by 10.227.10.196 with HTTP; Tue, 4 Feb 2014 10:14:29 -0800 (PST)
In-Reply-To: <CF0BE8F0.C456C%w.roome@alcatel-lucent.com>
References: <CABkgnnVN=mxwwvbMKw=F-+cfgxYUrO8hzmF0r14ApfP7cXAcTQ@mail.gmail.com> <CANUuoLpVQ71VM=M8J7FmYiJK6VwdF7JvqzG36ymGWAr2Z2qXQg@mail.gmail.com> <CF0BE8F0.C456C%w.roome@alcatel-lucent.com>
Date: Tue, 4 Feb 2014 10:14:29 -0800
Message-ID: <CABkgnnWTjb8_tJEa3c10iFsqeszsx-KZJOZOf6dkHPJ0vPQ99Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Wendy Roome <w.roome@alcatel-lucent.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "N:" <draft-ietf-alto-protocol.all@tools.ietf.org>, "Y. Richard Yang" <yry@cs.yale.edu>, Sebastian Kiesel <ietf-alto@skiesel.de>, Richard Alimi <ralimi@google.com>, "Reinaldo Penno, \(repenno\)" <repenno@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-alto-protocol-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 18:14:33 -0000

On 27 January 2014 08:16, Wendy Roome <w.roome@alcatel-lucent.com> wrote:
> An =E2=80=9CALTO Server=E2=80=9D is a collection of services provided by =
a provider. That
> provider may distribute these services over several different physical
> servers, and that distribution may change over time. If we used URIs to
> identify those services, the IDs would have to change whenever the provid=
er
> redistributed services.

That might be considered a feature.  Let me try to explain.

What you are suggesting is a very common reaction to REST.  Stuff does
need to move, and it frequently does in practice.  But that doesn't
necessarily change the way that things are identified.

If it is more convenient for a provider to use a form of internal
identification, using a URI does not prevent this.  That happens all
the time.  The unique ID column in your SQL database frequently gets
mapped to some portion of a URI.

Moving can still happen, but it doesn't work quite how you are
thinking (I think).  You don't really move data, you make new data.
And the IRD helps your clients discover the new data.  For example, a
network map at https://a.example.com/map/12 is moved to a new location
at https://b.example.com/maps/primary/12.  The data might be the same,
but it is a different thing (caches will have to download a copy, even
if the content is the same).  Clients using cost maps will see a new
location upon which the cost map depends.

The key point here is that this doesn't require the use of mechanisms
that are duplicative of these existing functions.

From suresh.krishnan@ericsson.com  Tue Feb  4 21:10:51 2014
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 047821A002D for <gen-art@ietfa.amsl.com>; Tue,  4 Feb 2014 21:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aQtX3uxfMYc2 for <gen-art@ietfa.amsl.com>; Tue,  4 Feb 2014 21:10:49 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 5D4531A0029 for <gen-art@ietf.org>; Tue,  4 Feb 2014 21:10:49 -0800 (PST)
X-AuditID: c6180641-b7f2f8e000002cdc-0e-52f1c7d96c3e
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id E8.EC.11484.9D7C1F25; Wed,  5 Feb 2014 06:10:49 +0100 (CET)
Received: from [164.48.125.18] (147.117.188.8) by smtps-am.internal.ericsson.com (147.117.188.87) with Microsoft SMTP Server (TLS) id 14.2.347.0; Wed, 5 Feb 2014 00:10:47 -0500
Message-ID: <52F1C7D3.8080609@ericsson.com>
Date: Wed, 5 Feb 2014 00:10:43 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, <draft-ietf-avtext-rtp-duplication.all@tools.ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [147.117.188.8]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHJMWRmVeSWpSXmKPExsUyuXRPuO7N4x+DDJraVS2WNf9ksbj66jOL A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJXRt2Yha8EO9orNE1ezNDD+Yu1i5OSQEDCR mDJrCwuELSZx4d56ti5GLg4hgSOMEi8W3oJytjBKNB2/yAhSxSugLXFy60YmEJtFQEXiz/l7 YN1sQJM27PwMFhcVCJNovzCTGaJeUOLkzCdgNSICmRJNj/rAaoQFfCR+3VoNFmcWsJW4MOc6 lC0vsf3tHLBeIQFNia1rvkNdqijx4vhPpgmM/LOQjJ2FpH0WkvYFjMyrGDlKi1PLctONDDcx AsPsmASb4w7GBZ8sDzFKc7AoifN+eescJCSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoFR7h0T Y+mTJktn6Svh/SveWqUYu1yPFS3g18pJ+z7zs8ep5nB2/sj2mZ4nzPY9fnRo2vKfen9O5K2Z reO1hmXdn7YnCcHbTOdVf1C86uDs2SXAsEd5rYuHZlZN+PtTYW6Hds4MYGWb9D+cQfHBQuWQ 40bzZY1nz93+2j9PvvFbTdKlRcUailOVWIozEg21mIuKEwEJslu8AQIAAA==
Subject: [Gen-art] Gen-ART Last Call review ofdraft-ietf-avtext-rtp-duplication-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 05:10:51 -0000

I am the assigned Gen-ART reviewer for draft-ietf-avtext-rtp-duplication-04

For background on Gen-ART, please see the FAQ at 
<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.

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

Summary: This draft is almost ready for publication as a Proposed 
Standard but I have one issue that probably needs further clarification 
in the draft.

* Section 7

I am not sure how the following MUST NOT is testable.

"First of all, RTP duplication MUST NOT be used
  in cases where the primary cause of packet loss is congestion since
  duplication can make congestion only worse."

I my understanding (correct me if I am wrong) neither the source of the 
duplication nor the destination will know whether the packet loss was 
due to congestion or something else. Can you please clarify how this 
"MUST NOT" would be followed?

Thanks
Suresh


From dromasca@avaya.com  Wed Feb  5 01:25:50 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 ACB411A00B4 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 01:25:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level: 
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ecK2d8bAMP-E for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 01:25:49 -0800 (PST)
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 D7FFB1A00B1 for <gen-art@ietf.org>; Wed,  5 Feb 2014 01:25:48 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmsMAIkC8lLGmAcV/2dsb2JhbABZgkgjIThXqDoDjTKIVoEIFnSCJwEBAxIbXgEVBw5WJgEEARoah2MBDKJprBKNA4FBIIJHD2aBFASZXYU+izGDLYIq
X-IronPort-AV: E=Sophos;i="4.95,785,1384318800"; d="scan'208,217";a="48196685"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 05 Feb 2014 04:25:47 -0500
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 05 Feb 2014 04:14:51 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Wed, 5 Feb 2014 04:25:45 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-clue-telepresence-requirements.all@tools.ietf.org" <draft-ietf-clue-telepresence-requirements.all@tools.ietf.org>
Thread-Topic: Gen-ART telechat review for draft-ietf-clue-telepresence-requirements
Thread-Index: Ac8iVD7DopGLVodrSuqSjcVUtNpS+g==
Date: Wed, 5 Feb 2014 09:25:44 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E3EC704@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_9904FB1B0159DA42B0B887B7FA8119CA2E3EC704AZFFEXMB04globa_"
MIME-Version: 1.0
Subject: [Gen-art] Gen-ART telechat review for draft-ietf-clue-telepresence-requirements
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 05 Feb 2014 09:25:50 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3EC704AZFFEXMB04globa_
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:  draft-ietf-clue-telepresence-requirements-07.txt

Reviewer: Dan Romascanu

Review Date: 2/5/2014

IETF LC End Date: 11/27/2013

IESG Telechat date: 2/6/2014



Summary:

Ready - all issues raised in my LC review were addressed. Thanks.



Major issues:



Minor issues:



Nits/editorial comments:




--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3EC704AZFFEXMB04globa_
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 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on Gen-ART, please see the FAQ at<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"MsoNormal" style=3D"line-height:14.4pt">Document:&nbsp; draft-i=
etf-clue-telepresence-requirements-07.txt<span style=3D"font-size:10.0pt;fo=
nt-family:&quot;Courier New&quot;"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 2/5/2014<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 11/27/2013<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: 2/6/2014<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 &#8211; all issues raised in my LC review w=
ere addressed. Thanks.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major issues:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor issues:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3EC704AZFFEXMB04globa_--

From dromasca@avaya.com  Wed Feb  5 01:39:38 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 C37781A00B7 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 01:39:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.134
X-Spam-Level: 
X-Spam-Status: No, score=-3.134 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZpyJ5fjP0CB for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 01:39:37 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 0F0721A00B3 for <gen-art@ietf.org>; Wed,  5 Feb 2014 01:39:36 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am4TAM8F8lKHCzI1/2dsb2JhbABZgkgjIThXqDoIjS2IVoEIFnSCJwEBAxIbXgEVBw5WJgEEARoah2MBDKJfrBGNA4FBIIM8gRQEmV2FPosxgy2CKg
X-IronPort-AV: E=Sophos;i="4.95,785,1384318800"; d="scan'208,217";a="41737622"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 05 Feb 2014 04:39:34 -0500
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; 05 Feb 2014 04:26:55 -0500
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, 5 Feb 2014 10:39:32 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-stox-core.all@tools.ietf.org" <draft-ietf-stox-core.all@tools.ietf.org>
Thread-Topic: Gen-ART telechat review for draft-ietf-stox-core-09
Thread-Index: Ac8iViobqQC/sQKQR/qAb2M2HMt5pA==
Date: Wed, 5 Feb 2014 09:39:31 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E3EC739@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_9904FB1B0159DA42B0B887B7FA8119CA2E3EC739AZFFEXMB04globa_"
MIME-Version: 1.0
Subject: [Gen-art] Gen-ART telechat review for draft-ietf-stox-core-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 09:39:38 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3EC739AZFFEXMB04globa_
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: draft-ietf-stox-core

Reviewer: Dan Romascanu

Review Date: 2/5/2014

IETF LC End Date: 12/11/2013

IESG Telechat date: 2/6/2014



Summary:



Ready.



Major issues:



Minor issues:



Nits/editorial comments:




--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3EC739AZFFEXMB04globa_
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 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on Gen-ART, please see the FAQ at<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-stox-core<o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 2/5/2014<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 12/11/2013<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: 2/6/2014<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">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_9904FB1B0159DA42B0B887B7FA8119CA2E3EC739AZFFEXMB04globa_--

From dromasca@avaya.com  Wed Feb  5 01:52:30 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 CE0681A00BB for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 01:52:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level: 
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RhbTXHxI8Ypf for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 01:52:27 -0800 (PST)
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 571611A00B5 for <gen-art@ietf.org>; Wed,  5 Feb 2014 01:52:27 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Am4TAGQI8lKHCzI1/2dsb2JhbABZgkgjIThXqDoIjS2IVoEIFnSCJwEBAxIbXgEVBw5WJgEEARoah2MBDKJirBKNA4FBIIM8gRQEmV2FPosxgy2CKg
X-IronPort-AV: E=Sophos;i="4.95,785,1384318800"; d="scan'208,217";a="48199124"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 05 Feb 2014 04:52:26 -0500
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 05 Feb 2014 04:39:30 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Wed, 5 Feb 2014 10:52:06 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-p2psip-rpr.all@tools.ietf.org" <draft-ietf-p2psip-rpr.all@tools.ietf.org>
Thread-Topic: Gen-ART telechat review of draft-ietf-p2psip-rpr-11
Thread-Index: Ac8iV+0gGXQcKR00QaG6ng5XMXn+5Q==
Date: Wed, 5 Feb 2014 09:52:05 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E3EC765@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_9904FB1B0159DA42B0B887B7FA8119CA2E3EC765AZFFEXMB04globa_"
MIME-Version: 1.0
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-p2psip-rpr-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, 05 Feb 2014 09:52:31 -0000

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


Document: draft-ietf-p2psip-rpr-11

Reviewer: Dan Romascanu

Review Date: 2/5/2014

IETF LC End Date: 2013/09/30

IESG Telechat date: 2/6/2014



Summary:



Ready. All issues raised in the LC review were addressed. Thanks.



Major issues:



Minor issues:



Nits/editorial comments:




--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3EC765AZFFEXMB04globa_
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 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on Gen-ART, please see the FAQ at<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"MsoNormal" style=3D"margin-bottom:6.0pt">Document: draft-ietf-p=
2psip-rpr-11<b><span style=3D"font-size:16.5pt;font-family:&quot;Arial&quot=
;,&quot;sans-serif&quot;"><o:p></o:p></span></b></p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 2/5/2014<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 2013/09/30<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: 2/6/2014<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. All issues raised in the LC review were ad=
dressed. Thanks.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major issues:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor issues:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3EC765AZFFEXMB04globa_--

From abegen@cisco.com  Wed Feb  5 04:03:09 2014
Return-Path: <abegen@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 80C5A1A00F2 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 04:03:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wSj4VR19lZNN for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 04:03:07 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id BDF9F1A00F1 for <gen-art@ietf.org>; Wed,  5 Feb 2014 04:03:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1856; q=dns/txt; s=iport; t=1391601787; x=1392811387; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=XX4LxET6eWWT+chaSGLC/kZ3ELhvmwaNWrOcS1A3qfo=; b=IUbx2LDzd8hKgkcBYcyibPlpz8i3u24ikM+YYCXRciH3l6zTGKlsO5Gy 7NAaCaBLVzpbB9Mq0/9tm7sEldoEY95W7KixXsXZedTF/5eslorkPvFJd 9x10AumFnB+SZ5aYfJUtlJspWB+V+z5f1L+MvtXmEs2Fzb73biJPMV++a A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAPcn8lKtJV2Y/2dsb2JhbABZgmshOFe+Q4EOFnSCJQEBAQQ6TwIBCBEEAQELFBAyHQgCBAESCBOHagEMzxIXjkQzBYMkgRQEqkyDLYIq
X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="18112564"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-1.cisco.com with ESMTP; 05 Feb 2014 12:03:06 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s15C36HG005743 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Feb 2014 12:03:06 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Wed, 5 Feb 2014 06:03:06 -0600
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-avtext-rtp-duplication.all@tools.ietf.org" <draft-ietf-avtext-rtp-duplication.all@tools.ietf.org>
Thread-Topic: Gen-ART Last Call review ofdraft-ietf-avtext-rtp-duplication-04.txt
Thread-Index: AQHPIjC0e7xZuU/Zl0KNy+komQZIBZqmjz+R
Date: Wed, 5 Feb 2014 12:03:06 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE9940E923896@xmb-aln-x01.cisco.com>
References: <52F1C7D3.8080609@ericsson.com>
In-Reply-To: <52F1C7D3.8080609@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.222.167]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Gen-art] Gen-ART Last Call review ofdraft-ietf-avtext-rtp-duplication-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 12:03:09 -0000

Hi Suresh,=0A=
=0A=
The text in section 7 says why this method is good for managed networks and=
 is not for unmanaged networks. In managed environments, you have a pretty =
good idea of what is happening. By design, there should not be any congesti=
on problems in such networks anyway (for the managed traffic). So, a provid=
er who will deploy this will know whether dupping is a good solution for th=
em or not.=0A=
=0A=
Thanks.=0A=
-acbegen=0A=
________________________________________=0A=
From: Suresh Krishnan [suresh.krishnan@ericsson.com]=0A=
Sent: Wednesday, February 05, 2014 12:10 AM=0A=
To: General Area Review Team; draft-ietf-avtext-rtp-duplication.all@tools.i=
etf.org=0A=
Subject: Gen-ART Last Call review ofdraft-ietf-avtext-rtp-duplication-04.tx=
t=0A=
=0A=
I am the assigned Gen-ART reviewer for draft-ietf-avtext-rtp-duplication-04=
=0A=
=0A=
For background on Gen-ART, please see the FAQ at=0A=
<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>.=0A=
=0A=
Please resolve these comments along with any other Last Call comments=0A=
you may receive.=0A=
=0A=
Summary: This draft is almost ready for publication as a Proposed=0A=
Standard but I have one issue that probably needs further clarification=0A=
in the draft.=0A=
=0A=
* Section 7=0A=
=0A=
I am not sure how the following MUST NOT is testable.=0A=
=0A=
"First of all, RTP duplication MUST NOT be used=0A=
  in cases where the primary cause of packet loss is congestion since=0A=
  duplication can make congestion only worse."=0A=
=0A=
I my understanding (correct me if I am wrong) neither the source of the=0A=
duplication nor the destination will know whether the packet loss was=0A=
due to congestion or something else. Can you please clarify how this=0A=
"MUST NOT" would be followed?=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=

From elwynd@dial.pipex.com  Wed Feb  5 05:02:15 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 45A1D1A00FE for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 05:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TjU-LCYNmwjs for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 05:02:11 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 39C2B1A0110 for <gen-art@ietf.org>; Wed,  5 Feb 2014 05:02:11 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1WB277-0007Nf-9x; Wed, 05 Feb 2014 13:02:03 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Martin Thomson <martin.thomson@gmail.com>
In-Reply-To: <CABkgnnWTjb8_tJEa3c10iFsqeszsx-KZJOZOf6dkHPJ0vPQ99Q@mail.gmail.com>
References: <CABkgnnVN=mxwwvbMKw=F-+cfgxYUrO8hzmF0r14ApfP7cXAcTQ@mail.gmail.com> <CANUuoLpVQ71VM=M8J7FmYiJK6VwdF7JvqzG36ymGWAr2Z2qXQg@mail.gmail.com> <CF0BE8F0.C456C%w.roome@alcatel-lucent.com> <CABkgnnWTjb8_tJEa3c10iFsqeszsx-KZJOZOf6dkHPJ0vPQ99Q@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-13"
Date: Wed, 05 Feb 2014 13:01:59 +0000
Message-Id: <1391605319.24761.4633.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: quoted-printable
Cc: Wendy Roome <w.roome@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "N:" <draft-ietf-alto-protocol.all@tools.ietf.org>, "Y. Richard Yang" <yry@cs.yale.edu>, Sebastian Kiesel <ietf-alto@skiesel.de>, Richard Alimi <ralimi@google.com>, "Reinaldo Penno, \(repenno\)" <repenno@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-alto-protocol-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 13:02:15 -0000

This is not really anything to do with me but I would point out that the
Information Centric Networking folks would probably disagree with the
view on "new data" that Martin expresses below - ICN would prefer that
if the data is the same then it has a single way of naming it and any
copy is as good as any other (and the recipient can check it).

As regards locations and URIs, the ni naming scheme (RFC 6920) for data
objects is a URI scheme that specifically avoids incorporating locations
in the components that uniquely identify the data whilst allowing a
location to be added as a hint.

I am not familiar with the details of the ALTO story, so I don't know
whether it is sensible to expect all the resources to be effectively
just data items - perhaps there is a distinction to be made?

Regards,
Elwyn
 =20

On Tue, 2014-02-04 at 10:14 -0800, Martin Thomson wrote:
> On 27 January 2014 08:16, Wendy Roome <w.roome@alcatel-lucent.com> wrote:
> > An =B4ALTO Server=A1 is a collection of services provided by a provider=
. That
> > provider may distribute these services over several different physical
> > servers, and that distribution may change over time. If we used URIs to
> > identify those services, the IDs would have to change whenever the prov=
ider
> > redistributed services.
>=20
> That might be considered a feature.  Let me try to explain.
>=20
> What you are suggesting is a very common reaction to REST.  Stuff does
> need to move, and it frequently does in practice.  But that doesn't
> necessarily change the way that things are identified.
>=20
> If it is more convenient for a provider to use a form of internal
> identification, using a URI does not prevent this.  That happens all
> the time.  The unique ID column in your SQL database frequently gets
> mapped to some portion of a URI.
>=20
> Moving can still happen, but it doesn't work quite how you are
> thinking (I think).  You don't really move data, you make new data.
> And the IRD helps your clients discover the new data.  For example, a
> network map at https://a.example.com/map/12 is moved to a new location
> at https://b.example.com/maps/primary/12.  The data might be the same,
> but it is a different thing (caches will have to download a copy, even
> if the content is the same).  Clients using cost maps will see a new
> location upon which the cost map depends.
>=20
> The key point here is that this doesn't require the use of mechanisms
> that are duplicative of these existing functions.
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From martin.thomson@gmail.com  Wed Feb  5 09:53:28 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 9C0171A011B for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 09:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xgXePLmZ_h2u for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 09:53:27 -0800 (PST)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by ietfa.amsl.com (Postfix) with ESMTP id CB2201A010D for <gen-art@ietf.org>; Wed,  5 Feb 2014 09:53:26 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id cc10so814603wib.11 for <gen-art@ietf.org>; Wed, 05 Feb 2014 09:53:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=n/eCMfzMeS7Efzqvif/d4m7W2dHGRH+beB/GIAqHWTA=; b=ZBObae0Nfy1HhBfARDsiuCAqI8pJY2keo2+5sGxd6KCdXbG9g1McOeHhqpsz/ILRo+ oTO0jENrccpx5FOvbKcOZ5hLvz5tjZ88gyZRI8rVuBJgYx41zeVOFibQxgTHiB+6fEoV cCRlkUK4HY2TVpFNdRfMCsbpBl7nLwc5SCwxgYS9+tGL/2fgg9/H0F11kr50ird0KKpC tCKFrx+KWiaT8Foqa0SVGUONmFZDC2RKJ6glx+3VQOnqkU7wmSNmA5LKvb7134C48JZF rH54N36YR5Z0+RccMuUe20Wk9f7SFEQ5Ynr09uXH6826QR+GBjdmWcjsTqk4m0OzPYY1 aQIw==
MIME-Version: 1.0
X-Received: by 10.194.236.9 with SMTP id uq9mr2330849wjc.31.1391622805624; Wed, 05 Feb 2014 09:53:25 -0800 (PST)
Received: by 10.227.10.196 with HTTP; Wed, 5 Feb 2014 09:53:25 -0800 (PST)
In-Reply-To: <1391605319.24761.4633.camel@mightyatom>
References: <CABkgnnVN=mxwwvbMKw=F-+cfgxYUrO8hzmF0r14ApfP7cXAcTQ@mail.gmail.com> <CANUuoLpVQ71VM=M8J7FmYiJK6VwdF7JvqzG36ymGWAr2Z2qXQg@mail.gmail.com> <CF0BE8F0.C456C%w.roome@alcatel-lucent.com> <CABkgnnWTjb8_tJEa3c10iFsqeszsx-KZJOZOf6dkHPJ0vPQ99Q@mail.gmail.com> <1391605319.24761.4633.camel@mightyatom>
Date: Wed, 5 Feb 2014 09:53:25 -0800
Message-ID: <CABkgnnWJPK6jDqxZFNAqucCu8cVBR3sMhkg=e1fJbxQy96jmwg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
Content-Type: text/plain; charset=UTF-8
Cc: Wendy Roome <w.roome@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "N:" <draft-ietf-alto-protocol.all@tools.ietf.org>, "Y. Richard Yang" <yry@cs.yale.edu>, Sebastian Kiesel <ietf-alto@skiesel.de>, Richard Alimi <ralimi@google.com>, "Reinaldo Penno, \(repenno\)" <repenno@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-alto-protocol-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 17:53:28 -0000

On 5 February 2014 05:01, Elwyn Davies <elwynd@dial.pipex.com> wrote:
> This is not really anything to do with me but I would point out that the
> Information Centric Networking folks would probably disagree with the
> view on "new data" that Martin expresses below - ICN would prefer that
> if the data is the same then it has a single way of naming it and any
> copy is as good as any other (and the recipient can check it).

It's always nice to conceptualize the next highest layer of
abstraction, but I find that when enacting anything, the lowest
abstraction layer that works is often best.

There's nothing wrong with the concept you describe.  But I haven't
found that the abstraction is as useful in practice as it is in
theory.

> As regards locations and URIs, the ni naming scheme (RFC 6920) for data
> objects is a URI scheme that specifically avoids incorporating locations
> in the components that uniquely identify the data whilst allowing a
> location to be added as a hint.

I didn't suggest ni, for two reasons: ni isn't widely used; and the
document already has an additional layer of indirection, my concern
was that the additional indirection was unnecessary, not that a
different form would be more appropriate.

From jari.arkko@piuha.net  Wed Feb  5 10:03:34 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 0642B1A0122 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:03:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UD0B-F9xEtqu for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:03:31 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8681A0150 for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:03:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 033B92CC5F; Wed,  5 Feb 2014 20:03:30 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wh72bCIjGVSN; Wed,  5 Feb 2014 20:03:29 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 080A02CC48; Wed,  5 Feb 2014 20:03:16 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CANUuoLrf=iF9Swrn6CAoNSTEr=qVvq-PVNEyrPjGsqKWKY3oTQ@mail.gmail.com>
Date: Wed, 5 Feb 2014 13:03:13 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6597E0A-B8D4-44CF-9458-B4C910B0B6CC@piuha.net>
References: <CABkgnnVN=mxwwvbMKw=F-+cfgxYUrO8hzmF0r14ApfP7cXAcTQ@mail.gmail.com> <CANUuoLpVQ71VM=M8J7FmYiJK6VwdF7JvqzG36ymGWAr2Z2qXQg@mail.gmail.com> <CF0BE8F0.C456C%w.roome@alcatel-lucent.com> <CANUuoLrf=iF9Swrn6CAoNSTEr=qVvq-PVNEyrPjGsqKWKY3oTQ@mail.gmail.com>
To: "Y. Richard Yang" <yry@cs.yale.edu>, Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: Wendy Roome <w.roome@alcatel-lucent.com>, gen-art@ietf.org, "N:" <draft-ietf-alto-protocol.all@tools.ietf.org>, Sebastian Kiesel <ietf-alto@skiesel.de>, Richard Alimi <ralimi@google.com>, "Reinaldo Penno, \(repenno\)" <repenno@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-alto-protocol-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 18:03:34 -0000

Thank you very much Martin for your review, and Richard for the quick =
responses and your interest in correcting issues.

I expect a new version of the draft is needed for the string issue.=20

Jari

On Feb 3, 2014, at 11:57 PM, Y. Richard Yang <yry@cs.yale.edu> wrote:

> Hi Martin,
>=20
> Wendy gave a good summary on the reasoning of not using URIs. We are =
wondering if you may have some additional comments so that we can =
address. Thank you so much!
>=20
> Richard
>=20
> On Jan 27, 2014 11:16 AM, "Wendy Roome" <w.roome@alcatel-lucent.com> =
wrote:
> Here=92s my response for =93why resource ids instead of uris=94:
>=20
> An =93ALTO Server=94 is a collection of services provided by a =
provider. That provider may distribute these services over several =
different physical servers, and that distribution may change over time. =
If we used URIs to identify those services, the IDs would have to change =
whenever the provider redistributed services.
>=20
> Therefore we defined =93Resource IDs=94 as persistent, =
location-independent, IDs for those services. Resource IDs must be =
unique, but only within the context of one provider=92s services =97 =
that is, the services defined by the tree of IRDs reachable from a root =
IRD. That IRD tree maps those Resource IDs to URIs, and allows the =
provider to change the mapping without disrupting clients. Thus ALTO =
Resource IDs are relative to the URI of the provider=92s IRD tree. If a =
provider had to use globally unique, location-dependent URIs, instead of =
location-independent relative IDs, the provider would have an =
unnecessary administrative burden.
>=20
> (Yes, I know =93URIs=94, unlike URLs, are supposed to be =93location =
independent.=94 But let=92s face reality: that only works if there=92s =
some higher level mapping of URIs to locations. For all practical =
purposes, =93URI=94 means host-specific =93URL=94.)
>=20
> Another way to look at it is that =93Resource IDs=94 are like using =
relative addresses within a web page. They make it easier to move a tree =
of related pages from one host to another.
>=20
> 	- Wendy Roome
>=20
> From: "Y. Richard Yang" <yry@cs.yale.edu>
> Date: Sun, January 26, 2014 at 16:40
> To: Martin Thomson <martin.thomson@gmail.com>
> Cc: "N:" <draft-ietf-alto-protocol.all@tools.ietf.org>, =
"gen-art@ietf.org" <gen-art@ietf.org>, Richard Alimi =
<ralimi@google.com>, "Reinaldo Penno, (repenno)" <repenno@cisco.com>, =
Wendy Roome <w.roome@alcatel-lucent.com>, Sebastian Kiesel =
<ietf-alto@skiesel.de>
> Subject: Re: Gen-ART review of draft-ietf-alto-protocol-25
>=20
>=20
> Section 10.2 defines a resource ID.  Why do this when you could use
> URIs?  After all, that's what URIs are for.  I realize that this would
> be something of a major change to the protocol, but I think that the
> question is particularly important.
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Feb  5 10:06:05 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 B7F321A0154 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:06:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uaq-uieIfVHQ for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:06:01 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 30BB41A0159 for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:06:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1EE642CC95; Wed,  5 Feb 2014 20:06:00 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4s6J6kJC2XH6; Wed,  5 Feb 2014 20:05:59 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 58C3D2CC6B; Wed,  5 Feb 2014 20:05:54 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E3EC765@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 5 Feb 2014 13:05:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <946584FC-EFF4-4328-A8B6-0299B5DDC6A8@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA2E3EC765@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-p2psip-rpr.all@tools.ietf.org" <draft-ietf-p2psip-rpr.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-p2psip-rpr-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, 05 Feb 2014 18:06:06 -0000

Thank you for your review and re-review, Dan! And thank you authors for =
the revisions!

I have balloted no-obj.

jari

On Feb 5, 2014, at 4:52 AM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at
> =20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> =20
> Document: draft-ietf-p2psip-rpr-11
>=20
> Reviewer: Dan Romascanu
> Review Date: 2/5/2014
> IETF LC End Date: 2013/09/30
> IESG Telechat date: 2/6/2014
> =20
> Summary:
> =20
> Ready. All issues raised in the LC review were addressed. Thanks.
> =20
> 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 jari.arkko@piuha.net  Wed Feb  5 10:09:00 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3809C1A0120 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:09:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gRoOir2EdvQs for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:08:58 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D9C551A010D for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:08:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C95572CC5F; Wed,  5 Feb 2014 20:08:56 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XNTalj0Aj9ad; Wed,  5 Feb 2014 20:08:53 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7F17C2CC48; Wed,  5 Feb 2014 20:08:44 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52946268.9090502@ericsson.com>
Date: Wed, 5 Feb 2014 13:08:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B191799-A8FC-42B9-95A3-451856422AD1@piuha.net>
References: <201310021114.r92BEsDt086478@givry.fdupont.fr> <B0D29E0424F2DE47A0B36779EC66677925854B88@nkgeml501-mbs.china.huawei.com> <52946268.9090502@ericsson.com>
To: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
X-Mailer: Apple Mail (2.1510)
Cc: 'yunfei zhang' <hishigh@gmail.com>, jiangxingfeng 00215458 <jiangxingfeng@huawei.com>, gen-art@ietf.org, Zongning <zongning@huawei.com>
Subject: Re: [Gen-art] review of draft-ietf-p2psip-drr-10.txt (resent)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 05 Feb 2014 18:09:00 -0000

Thank you Francis for the review and Ning for the update. I have =
balloted no-obj.

Jari

On Nov 26, 2013, at 3:57 AM, Gonzalo Camarillo =
<gonzalo.camarillo@ericsson.com> wrote:

> Hi,
>=20
> this was a gen-art review. So, I am cc:ing gen-art@ietf.org
>=20
> Cheers,
>=20
> Gonzalo
>=20
> On 26/11/2013 9:54 AM, Zongning wrote:
>> Hi, Francis,
>>=20
>> Just want to confirm if you are happy with this new revision, which =
we believe addressed your comments on editorial issues.
>>=20
>> Thanks.
>>=20
>> -Ning
>>=20
>>> -----Original Message-----
>>> From: Zongning
>>> Sent: Monday, October 21, 2013 3:47 PM
>>> To: 'Francis.Dupont@fdupont.fr'
>>> Cc: 'Roni Even'; 'yunfei zhang'; jiangxingfeng 00215458
>>> Subject: RE: review of draft-ietf-p2psip-drr-10.txt (resent)
>>>=20
>>> Hi, Francis,
>>>=20
>>> Could you please review the updated version to confirm if your
>>> comments/suggestions have been appropriately resolved?
>>>=20
>>> URL:
>>> http://www.ietf.org/internet-drafts/draft-ietf-p2psip-drr-11.txt
>>> Status:          =
http://datatracker.ietf.org/doc/draft-ietf-p2psip-drr
>>> Htmlized:        http://tools.ietf.org/html/draft-ietf-p2psip-drr-11
>>> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-p2psip-drr-11
>>>=20
>>> Thanks,
>>>=20
>>> -Ning
>>>=20
>>>> -----Original Message-----
>>>> From: Francis.Dupont@fdupont.fr [mailto:Francis.Dupont@fdupont.fr]
>>>> Sent: Wednesday, October 02, 2013 7:15 PM
>>>> To: gen-art@ietf.org
>>>> Cc: draft-ietf-p2psip-drr.all@tools.ietf.org
>>>> Subject: review of draft-ietf-p2psip-drr-10.txt (resent)
>>>>=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-p2psip-drr-10.txt
>>>> Reviewer: Francis Dupont
>>>> Review Date: 20130927
>>>> IETF LC End Date: 20130930
>>>> IESG Telechat date: unknown
>>>>=20
>>>> Summary: Almost Ready
>>>>=20
>>>> Major issues: None
>>>>=20
>>>> Minor issues: the title and the abstract must get an explicit =
expansion
>>>> of the RELOAD acronym, e.g., the title shoud be:
>>>>   An extension to REsource LOcation And Discovery (RELOAD) protocol
>>>>   to support Direct Response Routing
>>>>=20
>>>> Nits/editorial comments:
>>>> - proposed changes to the title and to the abstract (both page 1)
>>>>=20
>>>> - ToC page 2 and 10 page 13: Acknowledgements -> Acknowledgments
>>>>=20
>>>> - IMHO Authors' Addresses should be in the body so before the =
Appendix
>>>>=20
>>>> - 2 page 3 in Publicly Reachable: closed system -> closed network
>>>>=20
>>>> - 3.1.2 page 6 (in fact more for the RFC Editor): Figure 2 label
>>>>  should be in the same page than the figure itself (or with other
>>>>  words please avoid silly page breaks).
>>>>=20
>>>> - 3.2.1 page 6: the responding peer receives a response...
>>>>  if I am not fully lost it should be a request, not a response?
>>>>=20
>>>> - 5.1 page 8 (4 times): e.g. -> e.g.,
>>>>=20
>>>> - 5.2 page 9: I trust you (and the WG) for the delays...
>>>>=20
>>>> - 8 page 13: drat -> draft (and IMHO document is far more =
appropriate
>>>>  as it will be published as an RFC before this draft :-).
>>>>=20
>>>> - 11.2 page 14: add a reference to RFC 6887 (and see below).
>>>>=20
>>>> - A.1 page 16: endpoint- independent -> endpoint-independent
>>>>=20
>>>> - A.1 page 16: even it doesn't provide a direct way of getting
>>>>  the external assigned address (but read 11.6) PCP [RFC 6887]
>>>>  must be added to UPnP-IGD and NAT-PMP. If you need some words,
>>>>  one can consider PCP as a far more complete version of NAT-PMP.
>>>>  BTW the "test address" comment applies too to PCP.
>>>>=20
>>>> Regards
>>>>=20
>>>> Francis.Dupont@fdupont.fr
>>>>=20
>>>> PS: my checker complains about standalone (-> stand-alone), inline
>>>> (?, please ignore), publically (-> publicly?, this should be =
addressed,
>>>> even by the RFC Editor, as it occurs many times), etc.
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Feb  5 10:31: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 4681E1A0156 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:31:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQIUhBHluG37 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:31:54 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9982E1A0132 for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:31:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8E7E62CC5F; Wed,  5 Feb 2014 20:31:52 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CjzNyW8qtZXP; Wed,  5 Feb 2014 20:31:51 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B59722CC48; Wed,  5 Feb 2014 20:31:44 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52EBEBA5.9090402@joelhalpern.com>
Date: Wed, 5 Feb 2014 13:31:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A1C6590-3C2D-4554-9F04-47EA808039B8@piuha.net>
References: <52EB0069.1060900@nostrum.com> <52EBEBA5.9090402@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, draft-ietf-xrblock-rtcp-xr-qoe.all@tools.ietf.org
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org Team" <gen-art@ietf.org>
Subject: Re: [Gen-art] Review: draft-ietf-xrblock-rtcp-xr-qoe-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 18:31:55 -0000

Joel: Many thanks again for your review and re-review, and to the =
authors for the revisions. I have balloted no-obj.

By the way, as an example of the usefulness of the Gen-ART system, take =
this week. I'm writing this onboard a day-long flight that I use to set =
my IESG positions. On the remainder of the week I've burned two =
extra-long days on meetings and the one remaining day will go into =
determining the outcome on a 600-mail last call. I could not have done =
this without your support in the review team.

Thank you, Gen-ART.

Jari

On Jan 31, 2014, at 1:29 PM, Joel M. Halpern <jmh@joelhalpern.com> =
wrote:

> This revision address all of my comments and is ready for publication =
as a Proposed Standard.
>=20
> Yours,
> Joel
>=20
> On 1/30/14, 8:46 PM, A. Jean Mahoney wrote:
>> Joel Halpern        2013-11-27   draft-ietf-xrblock-rtcp-xr-qoe-13*
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Feb  5 10:35:48 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 6D4F61A0189 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:35:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W-eWeYSzxfHg for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:35:47 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 276861A016B for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:35:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 19BCB2CC5F; Wed,  5 Feb 2014 20:35:46 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17dqtJ0-Iw54; Wed,  5 Feb 2014 20:35:43 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 02D792CC48; Wed,  5 Feb 2014 20:35:35 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52EBED27.8050307@joelhalpern.com>
Date: Wed, 5 Feb 2014 13:35:33 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <B0C97AA7-76B9-44AB-88D3-88FFBDE985B9@piuha.net>
References: <52EB0069.1060900@nostrum.com> <52EBD0AB.7050302@nostrum.com> <52EBED27.8050307@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, draft-ietf-tls-applayerprotoneg@tools.ietf.org
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org Team" <gen-art@ietf.org>
Subject: Re: [Gen-art] Review: draft-ietf-tls-applayerprotoneg-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 18:35:48 -0000

Thanks for your review, Joel!

On Jan 31, 2014, at 1:36 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:

> This document is still ready for publication as a Proposed Standard.
> Yours,
> Joel
> 
> On 1/31/14, 11:34 AM, A. Jean Mahoney wrote:
>> Joel Halpern   draft-ietf-tls-applayerprotoneg-04*
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Feb  5 10:36:27 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 26C821A01C0 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:36:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PeJag3qOaRyj for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:36:23 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 507971A01BB for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:36:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3DB542CC6B; Wed,  5 Feb 2014 20:36:22 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-mv2_YA_-DG; Wed,  5 Feb 2014 20:36:21 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B9AA72CC48; Wed,  5 Feb 2014 20:36:17 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D151146@ESESSMB209.ericsson.se>
Date: Wed, 5 Feb 2014 13:36:16 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A89A5096-2B13-4549-B150-5F230762C281@piuha.net>
References: <7594FB04B1934943A5C02806D1A2204B1D151146@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1510)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-ancp-mc-extensions.all@tools.ietf.org" <draft-ietf-ancp-mc-extensions.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ancp-mc-extensions-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 18:36:27 -0000

Thank you for your review, Christer!

Jari

On Jan 31, 2014, at 6:23 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:

>=20
> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at < =
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd or AD before =
posting a new version of the draft.
>=20
> Document:                       draft-ietf-ancp-mc-extensions-14.txt
> Reviewer:                        Christer Holmberg
> Review Date:                   31 January 2014
> IETF LC End Date:            22 January 2014
> IESG Telechat date:         6 February 2014=20
>=20
> Summary:		I have no issues with the document. It is well =
written, and is ready for publication.
>=20
> Major issues: -
>=20
> Minor issues: -
>=20
> Nits/editorial comments: -
>=20
> Regards,
>=20
> Christer
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Feb  5 10:37: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 671871A01C1 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:37:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NpwAgjpQoXA for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:37:21 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C4D5A1A0140 for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:37:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id B67AA2CC5F; Wed,  5 Feb 2014 20:37:19 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jr_HJ845hDzn; Wed,  5 Feb 2014 20:37:18 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 368862CC48; Wed,  5 Feb 2014 20:37:12 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E3EC739@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 5 Feb 2014 13:37:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC9DB012-145F-4EC1-9E0E-CBD23C1FB0FA@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA2E3EC739@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1510)
Cc: "draft-ietf-stox-core.all@tools.ietf.org" <draft-ietf-stox-core.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART telechat review for draft-ietf-stox-core-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 18:37:22 -0000

Thanks for your review, Dan!

Jari

On Feb 5, 2014, at 4:39 AM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at
> =20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> =20
> Please resolve these comments along with any other Last Call comments =
you may receive.
> =20
> Document: draft-ietf-stox-core
> Reviewer: Dan Romascanu
> Review Date: 2/5/2014
> IETF LC End Date: 12/11/2013
> IESG Telechat date: 2/6/2014
> =20
> Summary:
> =20
> Ready.
> =20
> 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 jari.arkko@piuha.net  Wed Feb  5 10:38:04 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 B14FD1A0138 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:38:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Os8SGNJ9COUC for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:38:03 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 578D51A016B for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:38:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4B9F82CC48; Wed,  5 Feb 2014 20:38:02 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xHCTfsjV21-f; Wed,  5 Feb 2014 20:38:01 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 302D22CC5F; Wed,  5 Feb 2014 20:37:55 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52EBEC9D.7020902@joelhalpern.com>
Date: Wed, 5 Feb 2014 13:37:54 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <1B01A614-B183-4F8B-A882-FEBD2C3C9940@piuha.net>
References: <52EB0069.1060900@nostrum.com> <52EBEC9D.7020902@joelhalpern.com>
To: Joel M. Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1510)
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] Review: draft-ietf-stox-presence-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 18:38:04 -0000

Thanks for your review, Joel

Jari

On Jan 31, 2014, at 1:34 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:

> This document is still ready for publication as a Proposed Standard.
> Yours,
> Joel
> 
> On 1/30/14, 8:46 PM, A. Jean Mahoney wrote:
>> Joel Halpern        2013-12-11   draft-ietf-stox-presence-07*
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Feb  5 10:39:52 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0818F1A01BB for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:39:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id agJejM5qyKhI for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:39:50 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5A6C91A0192 for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:39:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4BA1E2CC6B; Wed,  5 Feb 2014 20:39:49 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wILbpajcGJXm; Wed,  5 Feb 2014 20:39:48 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 58FC92CC48; Wed,  5 Feb 2014 20:39:39 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAPv4CP_aQKceoZ+dL0BoEaaqVMXe++bKGe=4SSrNE73rP4u1ag@mail.gmail.com>
Date: Wed, 5 Feb 2014 13:39:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B477470-E7AF-4916-8430-81BA5368F309@piuha.net>
References: <CAPv4CP_aQKceoZ+dL0BoEaaqVMXe++bKGe=4SSrNE73rP4u1ag@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: gen-art <gen-art@ietf.org>, draft-ietf-avtcore-clksrc all <draft-ietf-avtcore-clksrc.all@tools.ietf.org>
Subject: Re: [Gen-art] gen-art telechat review of draft-ietf-avtcore-clksrc-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 18:39:52 -0000

Authors: I agree with Scott's recommendation. Are you willing to =
consider the change?

(But I have balloted no-obj.)

Jari

On Feb 3, 2014, at 11:58 AM, 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>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-avtcore-clksrc-09
> Reviewer: Scott Brim
> Review Date: 2014-02-03
> IETF LC End Date: 2014-01-16
> IESG Telechat date: 2014-02-06
>=20
> Summary: Ready with a minor issue
>=20
> Major issues: none
>=20
> Minor issues:
>=20
> This is the same version I reviewed at LC. After discussion with the
> authors I have changed my question to a recommendation.
>=20
> In 6.1.2 and 6.1.3 it says: "If the answerer rejects the offer because =
the
> available reference clocks are incompatible, the rejection MUST
> contain at least one timestamp reference clock specification usable by
> the answerer."  I have learned that sending this reference clock
> specification is not required for the protocol to function. It is for
> the offerer's information, so that maybe next time the negotiation
> will succeed.
>=20
> - Since including the reference clock is not required for the protocol
> per se to work, consider making this MUST a SHOULD.
>=20
> - In any case, this needs to be justified. Even something as simple as
> adding "for the offerer's information" could be sufficient, although
> usually more would be expected.
>=20
> Scott
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Feb  5 10:51:05 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 BC8831A0174 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:51:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GqV9OQ5gClW7 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:51:03 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 581411A0159 for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:51:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 178B12CC5F; Wed,  5 Feb 2014 20:51:02 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VebrMcmWNs1c; Wed,  5 Feb 2014 20:51:00 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 678162CC48; Wed,  5 Feb 2014 20:50:37 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201306271615.r5RGFcqn049951@givry.fdupont.fr>
Date: Wed, 5 Feb 2014 13:50:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2692DE93-0689-484F-B603-D8EF89762B1E@piuha.net>
References: <201306271615.r5RGFcqn049951@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1510)
Cc: gen-art@ietf.org, draft-ietf-rtgwg-cl-requirement.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-rtgwg-cl-requirement-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 18:51:05 -0000

Thanks for your (old) review of this document. Given the significant =
textual changes, I also re-read the document now. Looked OK to me=85 and =
at least some of the editorial comments have been taken into account.

jari

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

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-rtgwg-cl-requirement-10.txt
> Reviewer: Francis Dupont
> Review Date: 20130617
> IETF LC End Date: 20130619
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
> - ToC page 3 and 7 page 12: Acknowledgements -> Acknowledgments
>=20
> - 2 page 4: double include words in:
>=20
>   The services supported include pseudowire based services (RFC 3985
>   [RFC3985]), including VPN services,
>=20
> I suggest something like:
>=20
>   The supported services are, but not limited to, pseudowire based
>   services (RFC 3985 [RFC3985]), including VPN services,
>=20
> - 3 page 5 (component link): the term NPO is used before being defined
>=20
> - 3 page 5 (component link): expand the WDM abbrev -- not well known
>  according tothe RFC Editor list:
>  http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
>=20
> - 3 page 5 (flow identification): same for the PW abbrev
>=20
> - 4.1 page 6: CAN -> MAY
>=20
> - 6 page 12 (MR#10) -> interpretted -> interpreted
>=20
> - 9 page 13: Encrption -> Encryption
>=20
> - Authors' Addresses: add the country (USA) in postal addresses
>=20
> Regards
>=20
> Francis.Dupont@fdupont.fr
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Feb  5 10:52:49 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 9814A1A0140 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:52:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EC05mginnbIC for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:52:47 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7ECE91A014E for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:52:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 71EC42CC6B; Wed,  5 Feb 2014 20:52:46 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VBHHKodLaH1Z; Wed,  5 Feb 2014 20:52:42 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id ADAF52CC5F; Wed,  5 Feb 2014 20:52:39 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <em7dcf52ea-af78-4af6-a3e1-14f70aafef9f@sydney>
Date: Wed, 5 Feb 2014 13:52:36 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <8BA4E28F-B97B-4E2F-B601-1DF012AB0122@piuha.net>
References: <em7dcf52ea-af78-4af6-a3e1-14f70aafef9f@sydney>
To: "Paul E. Jones" <paulej@packetizer.com>
X-Mailer: Apple Mail (2.1510)
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-insipid-session-id-reqts.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art telechat review of draft-ietf-insipid-session-id-reqts-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 05 Feb 2014 18:52:49 -0000

Thanks, all. 

Jari

On Jan 31, 2014, at 2:22 PM, Paul E. Jones <paulej@packetizer.com> wrote:

> Thanks.  I made the correction in my local copy.
> 
> ------ Original Message ------
> From: "Elwyn Davies" <elwynd@dial.pipex.com>
> To: "General Area Review Team" <gen-art@ietf.org>
> Cc: draft-ietf-insipid-session-id-reqts.all@tools.ietf.org
> Sent: 1/31/2014 1:13:33 PM
> Subject: Gen-art telechat review of draft-ietf-insipid-session-id-reqts-09
> 
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>> 
>> Please wait for direction from your document shepherd
>> or AD before posting a new version of the draft.
>> 
>> Document: draft-ietf-insipid-session-id-reqts-09
>> Reviewer: Elwyn Davies
>> Review Date: 31 January 2014
>> IETF LC End Date:
>> IESG Telechat date: 06 February 2014
>> 
>> Summary: Ready. Thanks to the authors for addressing LC comments.
>> 
>> Major issues:
>> None
>> 
>> Minor issues:
>> None
>> 
>> Nits/editorial comments:
>> One nit escaped:
>> s3.1, para below Fig 1: s/and are by not exhaustive:/and are not
>> exhaustive:/
>> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From jari.arkko@piuha.net  Wed Feb  5 10:53:53 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDC11A0159 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:53:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mb-biD071II3 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 10:53:52 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 28E551A0138 for <gen-art@ietf.org>; Wed,  5 Feb 2014 10:53:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1845C2CC5F; Wed,  5 Feb 2014 20:53:33 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5uEgz5hDb3_N; Wed,  5 Feb 2014 20:53:30 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B89AE2CC48; Wed,  5 Feb 2014 20:53:27 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E3EC704@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 5 Feb 2014 13:53:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <21B57F40-B5F1-4A92-A3AE-32F755AD623F@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA2E3EC704@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1510)
Cc: "draft-ietf-clue-telepresence-requirements.all@tools.ietf.org" <draft-ietf-clue-telepresence-requirements.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART telechat review for draft-ietf-clue-telepresence-requirements
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 05 Feb 2014 18:53:53 -0000

Thank you for the review & edits!

Jari

On Feb 5, 2014, at 4:25 AM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at
> =20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> =20
> Please resolve these comments along with any other Last Call comments =
you may receive.
> =20
> Document:  draft-ietf-clue-telepresence-requirements-07.txt
> Reviewer: Dan Romascanu
> Review Date: 2/5/2014
> IETF LC End Date: 11/27/2013
> IESG Telechat date: 2/6/2014
> =20
> Summary:
> Ready =96 all issues raised in my LC review were addressed. Thanks.
> =20
> 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 jari.arkko@piuha.net  Wed Feb  5 11:03:20 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94A691A0117 for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 11:03:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qloy4cgG4wLv for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 11:03:17 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7A6E31A001A for <gen-art@ietf.org>; Wed,  5 Feb 2014 11:03:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 67C772CC5F; Wed,  5 Feb 2014 21:03:16 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ozPgZV_kllEU; Wed,  5 Feb 2014 21:03:14 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 14F5D2CC48; Wed,  5 Feb 2014 21:03:10 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52D82EA9.1000202@nostrum.com>
Date: Wed, 5 Feb 2014 14:03:07 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <81392D7F-14B3-488D-A3E1-37F65E933475@piuha.net>
References: <52D82EA9.1000202@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>, draft-crocker-id-adoption@tools.ietf.org
X-Mailer: Apple Mail (2.1510)
Cc: General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-art LC review of draft-crocker-id-adoption-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 19:03:20 -0000

Thank you for the review.

I have also reviewed the document myself and found an excellent, thank =
you for writing it!

I have balloted Yes for this document.

Jari

On Jan 16, 2014, at 2:10 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-crocker-id-adoption-05
> Reviewer: Robert Sparks
> Review Date: 16-Jan-2014
> IETF LC End Date: 31-Jan-2014
> IESG Telechat date: 6-Feb-2014
>=20
> Summary: This document is ready for publication as an Informational =
RFC
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From aidan.williams@audinate.com  Wed Feb  5 23:37:07 2014
Return-Path: <aidan.williams@audinate.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89DD41A038F for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 23:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.223
X-Spam-Level: 
X-Spam-Status: No, score=0.223 tagged_above=-999 required=5 tests=[BASE64_LENGTH_79_INF=1.502, BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=1.157, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EDHSZpwNkk5A for <gen-art@ietfa.amsl.com>; Wed,  5 Feb 2014 23:37:05 -0800 (PST)
Received: from zimbra8.audinate.com (sydney.audinate.com [150.101.200.21]) by ietfa.amsl.com (Postfix) with ESMTP id 509701A004C for <gen-art@ietf.org>; Wed,  5 Feb 2014 23:37:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by zimbra8.audinate.com (Postfix) with ESMTP id 2FAA9332CDB; Thu,  6 Feb 2014 18:37:01 +1100 (EST)
Received: from zimbra8.audinate.com ([127.0.0.1]) by localhost (zimbra8.audinate.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id zDGsFvDtR403; Thu,  6 Feb 2014 18:36:57 +1100 (EST)
Received: from localhost (localhost [127.0.0.1]) by zimbra8.audinate.com (Postfix) with ESMTP id 72100332CD0; Thu,  6 Feb 2014 18:36:57 +1100 (EST)
X-Virus-Scanned: amavisd-new at audinate.com
Received: from zimbra8.audinate.com ([127.0.0.1]) by localhost (zimbra8.audinate.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id wB5qjQ6CAMMB; Thu,  6 Feb 2014 18:36:57 +1100 (EST)
Received: from zimbra8.audinate.com (zimbra8.audinate.com [10.12.0.4]) by zimbra8.audinate.com (Postfix) with ESMTP id 3DE3B332CC6; Thu,  6 Feb 2014 18:36:57 +1100 (EST)
Message-ID: <CBCD0466-38F6-4998-80EE-6A7621F98777@audinate.com>
To: "=?utf-8?B?SmFyaSBBcmtrbw==?=" <jari.arkko@piuha.net>, "=?utf-8?B?U2NvdHQgQnJpbQ==?=" <scott.brim@gmail.com>
Importance: Normal
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_573002_2089785274.1391672217156"
X-Mailer: Zimbra 8.0.6_GA_5922 (MobileSync - Apache-HttpClient/UNAVAILABLE (java 1.4))
From: Aidan Williams <aidan.williams@audinate.com>
Date: Thu, 6 Feb 2014 18:36:57 +1100 (EST)
In-Reply-To: <7B477470-E7AF-4916-8430-81BA5368F309@piuha.net>
References: <CAPv4CP_aQKceoZ+dL0BoEaaqVMXe++bKGe=4SSrNE73rP4u1ag@mail.gmail.com> <7B477470-E7AF-4916-8430-81BA5368F309@piuha.net>
Thread-Topic: gen-art telechat review of draft-ietf-avtcore-clksrc-09
Thread-Index: w1CgbdkO+gTfIZ/f5wngpF/q6tdJcA==
Cc: =?utf-8?B?Z2VuLWFydA==?= <gen-art@ietf.org>, =?utf-8?B?ZHJhZnQtaWV0Zi1hdnRjb3JlLWNsa3NyYyBhbGw=?= <draft-ietf-avtcore-clksrc.all@tools.ietf.org>
Subject: Re: [Gen-art] =?utf-8?q?gen-art_telechat_review_of_draft-ietf-avtcore?= =?utf-8?q?-clksrc-09?=
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2014 07:37:07 -0000

------=_Part_573002_2089785274.1391672217156
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit


Hi Jari,

Yes, we are happy to make changes to address these comments.

- aidan

Sent from my HTC

----- Reply message -----
From: "Jari Arkko" <jari.arkko@piuha.net>
To: "Scott Brim" <scott.brim@gmail.com>
Cc: "gen-art" <gen-art@ietf.org>, "draft-ietf-avtcore-clksrc all" <draft-ietf-avtcore-clksrc.all@tools.ietf.org>
Subject: [Gen-art] gen-art telechat review of draft-ietf-avtcore-clksrc-09
Date: Wed, Feb 5, 2014 7:40 PM


Authors: I agree with Scott's recommendation. Are you willing to consider the change?

(But I have balloted no-obj.)

Jari

On Feb 3, 2014, at 11:58 AM, 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 wait for direction from your document shepherd
> or AD before posting a new version of the draft.
> 
> Document: draft-ietf-avtcore-clksrc-09
> Reviewer: Scott Brim
> Review Date: 2014-02-03
> IETF LC End Date: 2014-01-16
> IESG Telechat date: 2014-02-06
> 
> Summary: Ready with a minor issue
> 
> Major issues: none
> 
> Minor issues:
> 
> This is the same version I reviewed at LC. After discussion with the
> authors I have changed my question to a recommendation.
> 
> In 6.1.2 and 6.1.3 it says: "If the answerer rejects the offer because the
> available reference clocks are incompatible, the rejection MUST
> contain at least one timestamp reference clock specification usable by
> the answerer."  I have learned that sending this reference clock
> specification is not required for the protocol to function. It is for
> the offerer's information, so that maybe next time the negotiation
> will succeed.
> 
> - Since including the reference clock is not required for the protocol
> per se to work, consider making this MUST a SHOULD.
> 
> - In any case, this needs to be justified. Even something as simple as
> adding "for the offerer's information" could be sufficient, although
> usually more would be expected.
> 
> Scott
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


------=_Part_573002_2089785274.1391672217156
Content-Type: multipart/related; 
	boundary="----=_Part_573003_926053433.1391672217157"

------=_Part_573003_926053433.1391672217157
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html><body><div><div style=3D"font-size: 12pt; font-family: Calibri,sans-s=
erif;"><div>Hi Jari,</div><div><br></div><div>Yes, we are happy to make cha=
nges to address these comments.</div><div><br></div><div>- aidan</div><div>=
<br></div><div>Sent from my HTC</div><br><div id=3D"htc_header">----- Reply=
 message -----<br>From: &quot;Jari Arkko&quot; &lt;jari.arkko@piuha.net&gt;=
<br>To: &quot;Scott Brim&quot; &lt;scott.brim@gmail.com&gt;<br>Cc: &quot;ge=
n-art&quot; &lt;gen-art@ietf.org&gt;, &quot;draft-ietf-avtcore-clksrc all&q=
uot; &lt;draft-ietf-avtcore-clksrc.all@tools.ietf.org&gt;<br>Subject: [Gen-=
art] gen-art telechat review of draft-ietf-avtcore-clksrc-09<br>Date: Wed, =
Feb 5, 2014 7:40 PM</div></div><br>
</div><br><div>Authors: I agree with Scott's recommendation. Are you willin=
g to consider the change?
<br>
<br>(But I have balloted no-obj.)
<br>
<br>Jari
<br>
<br>On Feb 3, 2014, at 11:58 AM, Scott Brim &lt;scott.brim@gmail.com&gt; wr=
ote:
<br>
<br>&gt; I am the assigned Gen-ART reviewer for this draft. For background =
on
<br>&gt; Gen-ART, please see the FAQ at
<br>&gt; &lt; <a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenA=
rtfaq&gt">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt</a>;.
<br>&gt;=20
<br>&gt; Please wait for direction from your document shepherd
<br>&gt; or AD before posting a new version of the draft.
<br>&gt;=20
<br>&gt; Document: draft-ietf-avtcore-clksrc-09
<br>&gt; Reviewer: Scott Brim
<br>&gt; Review Date: 2014-02-03
<br>&gt; IETF LC End Date: 2014-01-16
<br>&gt; IESG Telechat date: 2014-02-06
<br>&gt;=20
<br>&gt; Summary: Ready with a minor issue
<br>&gt;=20
<br>&gt; Major issues: none
<br>&gt;=20
<br>&gt; Minor issues:
<br>&gt;=20
<br>&gt; This is the same version I reviewed at LC. After discussion with t=
he
<br>&gt; authors I have changed my question to a recommendation.
<br>&gt;=20
<br>&gt; In 6.1.2 and 6.1.3 it says: &quot;If the answerer rejects the offe=
r because the
<br>&gt; available reference clocks are incompatible, the rejection MUST
<br>&gt; contain at least one timestamp reference clock specification usabl=
e by
<br>&gt; the answerer.&quot; &nbsp;I have learned that sending this referen=
ce clock
<br>&gt; specification is not required for the protocol to function. It is =
for
<br>&gt; the offerer's information, so that maybe next time the negotiation
<br>&gt; will succeed.
<br>&gt;=20
<br>&gt; - Since including the reference clock is not required for the prot=
ocol
<br>&gt; per se to work, consider making this MUST a SHOULD.
<br>&gt;=20
<br>&gt; - In any case, this needs to be justified. Even something as simpl=
e as
<br>&gt; adding &quot;for the offerer's information&quot; could be sufficie=
nt, although
<br>&gt; usually more would be expected.
<br>&gt;=20
<br>&gt; Scott
<br>&gt; _______________________________________________
<br>&gt; Gen-art mailing list
<br>&gt; Gen-art@ietf.org
<br>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/gen-art">https://=
www.ietf.org/mailman/listinfo/gen-art</a>
<br>
<br></div></body></html>
------=_Part_573003_926053433.1391672217157
Content-Type: text/plain;
	charset= utf-8
Content-Transfer-Encoding: base64
Content-Disposition: inline

DQpIaSBKYXJpLAoKWWVzLCB3ZSBhcmUgaGFwcHkgdG8gbWFrZSBjaGFuZ2VzIHRvIGFkZHJlc3MgdGhlc2UgY29tbWVudHMuCgotIGFpZGFuCgpTZW50IGZyb20gbXkgSFRDCgotLS0tLSBSZXBseSBtZXNzYWdlIC0tLS0tCkZyb206ICJKYXJpIEFya2tvIiA8amFyaS5hcmtrb0BwaXVoYS5uZXQ+ClRvOiAiU2NvdHQgQnJpbSIgPHNjb3R0LmJyaW1AZ21haWwuY29tPgpDYzogImdlbi1hcnQiIDxnZW4tYXJ0QGlldGYub3JnPiwgImRyYWZ0LWlldGYtYXZ0Y29yZS1jbGtzcmMgYWxsIiA8ZHJhZnQtaWV0Zi1hdnRjb3JlLWNsa3NyYy5hbGxAdG9vbHMuaWV0Zi5vcmc+ClN1YmplY3Q6IFtHZW4tYXJ0XSBnZW4tYXJ0IHRlbGVjaGF0IHJldmlldyBvZiBkcmFmdC1pZXRmLWF2dGNvcmUtY2xrc3JjLTA5CkRhdGU6IFdlZCwgRmViIDUsIDIwMTQgNzo0MCBQTQoKDQo=
------=_Part_573003_926053433.1391672217157
Content-Type: text/html;
	charset= utf-8
Content-Transfer-Encoding: base64
Content-Disposition: inline

DQo8IURPQ1RZUEUgSFRNTCBQVUJMSUMgIi0vL1czQy8vRFREIEhUTUwgNC4wMS8vRU4iICJodHRwOi8vd3d3LnczLm9yZy9UUi9odG1sNC9zdHJpY3QuZHRkIj4KPGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZTogMTJwdDsgZm9udC1mYW1pbHk6IENhbGlicmksc2Fucy1zZXJpZjsiPjxkaXY+SGkgSmFyaSw8L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Plllcywgd2UgYXJlIGhhcHB5IHRvIG1ha2UgY2hhbmdlcyB0byBhZGRyZXNzIHRoZXNlIGNvbW1lbnRzLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+LSBhaWRhbjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+U2VudCBmcm9tIG15IEhUQzwvZGl2Pjxicj48ZGl2IGlkPSJodGNfaGVhZGVyIj4tLS0tLSBSZXBseSBtZXNzYWdlIC0tLS0tPGJyPkZyb206ICZxdW90O0phcmkgQXJra28mcXVvdDsgJmx0O2phcmkuYXJra29AcGl1aGEubmV0Jmd0Ozxicj5UbzogJnF1b3Q7U2NvdHQgQnJpbSZxdW90OyAmbHQ7c2NvdHQuYnJpbUBnbWFpbC5jb20mZ3Q7PGJyPkNjOiAmcXVvdDtnZW4tYXJ0JnF1b3Q7ICZsdDtnZW4tYXJ0QGlldGYub3JnJmd0OywgJnF1b3Q7ZHJhZnQtaWV0Zi1hdnRjb3JlLWNsa3NyYyBhbGwmcXVvdDsgJmx0O2RyYWZ0LWlldGYtYXZ0Y29yZS1jbGtzcmMuYWxsQHRvb2xzLmlldGYub3JnJmd0Ozxicj5TdWJqZWN0OiBbR2VuLWFydF0gZ2VuLWFydCB0ZWxlY2hhdCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1hdnRjb3JlLW
 Nsa3NyYy0wOTxicj5EYXRlOiBXZWQsIEZlYiA1LCAyMDE0IDc6NDAgUE08L2Rpdj48L2Rpdj48YnI+DQo=
------=_Part_573003_926053433.1391672217157--

------=_Part_573002_2089785274.1391672217156--

From w.roome@alcatel-lucent.com  Thu Feb  6 07:23:24 2014
Return-Path: <w.roome@alcatel-lucent.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9437F1A0143 for <gen-art@ietfa.amsl.com>; Thu,  6 Feb 2014 07:23:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HshITRFWT8sF for <gen-art@ietfa.amsl.com>; Thu,  6 Feb 2014 07:23:21 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id B69A21A03D5 for <gen-art@ietf.org>; Thu,  6 Feb 2014 07:23:20 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id s16FMtAn028525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 6 Feb 2014 09:22:55 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s16FMsxp000424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 6 Feb 2014 09:22:54 -0600
Received: from [135.222.152.71] (wdr-i7mbp2.mh.lucent.com [135.222.152.71]) by umail.lucent.com (8.13.8/TPES) with ESMTP id s16FMkS8011618; Thu, 6 Feb 2014 09:22:48 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Thu, 06 Feb 2014 10:22:47 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: Martin Thomson <martin.thomson@gmail.com>, Elwyn Davies <elwynd@dial.pipex.com>
Message-ID: <CF191011.CCC97%w.roome@alcatel-lucent.com>
Thread-Topic: [Gen-art] Gen-ART review of draft-ietf-alto-protocol-25
References: <CABkgnnVN=mxwwvbMKw=F-+cfgxYUrO8hzmF0r14ApfP7cXAcTQ@mail.gmail.com> <CANUuoLpVQ71VM=M8J7FmYiJK6VwdF7JvqzG36ymGWAr2Z2qXQg@mail.gmail.com> <CF0BE8F0.C456C%w.roome@alcatel-lucent.com> <CABkgnnWTjb8_tJEa3c10iFsqeszsx-KZJOZOf6dkHPJ0vPQ99Q@mail.gmail.com> <1391605319.24761.4633.camel@mightyatom> <CABkgnnWJPK6jDqxZFNAqucCu8cVBR3sMhkg=e1fJbxQy96jmwg@mail.gmail.com>
In-Reply-To: <CABkgnnWJPK6jDqxZFNAqucCu8cVBR3sMhkg=e1fJbxQy96jmwg@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "N:" <draft-ietf-alto-protocol.all@tools.ietf.org>, "Y. Richard Yang" <yry@cs.yale.edu>, Sebastian Kiesel <ietf-alto@skiesel.de>, Richard Alimi <ralimi@google.com>, "Reinaldo Penno, \(repenno\)" <repenno@cisco.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-alto-protocol-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2014 15:23:24 -0000

Here=B9s another take on using URIs for resource ids:

Suppose we define the uri of an ALTO resource as

   [uri-of-alto-ird] # [resource-id]

Eg, the uri of the default network map in the {9.2.3} example would be:

   http://alto.example.com/directory#my-default-network-map

In the IRD, we use the resource-id as the key for simplicity, because all
ids have the same prefix.

BTW, this makes it easier to configure a client to use a specific resource
(e.g., a specific non-default network map) =8B just give the client the uri
of that format.

Also, the resource id can be in any IRD reachable from the IRD in the
resource uri. e.g., the uri of the filtered cost service in {9.2.4} would
be

   http://alto.example.com/directory#filtered-cost-map


What do y=B9all think of that interpretation?

	- Wendy Roome


On 02/05/2014, 12:53, "Martin Thomson" <martin.thomson@gmail.com> wrote:

>On 5 February 2014 05:01, Elwyn Davies <elwynd@dial.pipex.com> wrote:
>> This is not really anything to do with me but I would point out that the
>> Information Centric Networking folks would probably disagree with the
>> view on "new data" that Martin expresses below - ICN would prefer that
>> if the data is the same then it has a single way of naming it and any
>> copy is as good as any other (and the recipient can check it).
>
>It's always nice to conceptualize the next highest layer of
>abstraction, but I find that when enacting anything, the lowest
>abstraction layer that works is often best.
>
>There's nothing wrong with the concept you describe.  But I haven't
>found that the abstraction is as useful in practice as it is in
>theory.
>
>> As regards locations and URIs, the ni naming scheme (RFC 6920) for data
>> objects is a URI scheme that specifically avoids incorporating locations
>> in the components that uniquely identify the data whilst allowing a
>> location to be added as a hint.
>
>I didn't suggest ni, for two reasons: ni isn't widely used; and the
>document already has an additional layer of indirection, my concern
>was that the additional indirection was unnecessary, not that a
>different form would be more appropriate.



From sajassi@cisco.com  Thu Feb  6 17:53:25 2014
Return-Path: <sajassi@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 B44FC1A058F; Thu,  6 Feb 2014 17:53:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7CZigPpO-26T; Thu,  6 Feb 2014 17:53:23 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id C56EE1A0587; Thu,  6 Feb 2014 17:53:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2768; q=dns/txt; s=iport; t=1391738001; x=1392947601; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=BZFF3iiPoICh29ERqgWoUAazjJsRciGf/dPmm9I2heg=; b=fXqoNBgPXsXocybym4W/EeopAtM2Y4emqY0ifqYBgLf2X1qp6HPkvWPE C0SHQYPEVwJvkndtSatfh0r116T1jVin4Q7zdMKKIuBIBOTbfwTbQSKpK tRro0H432cNPIK10wP1ilIaFseyKKucJdEQRPrJCW9/cpU5F6O9Q1OSaY g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoAFAKc79FKtJV2a/2dsb2JhbABZgmshOFEGvneBDxZ0giUBAQEEOj8SAQgUBB5CJQIEAQ0FG4dqAQcFzRIXjQeBEQsGAVAHhDgElEKDaYEyiy8BhT+DLXEBAXYIFyI
X-IronPort-AV: E=Sophos;i="4.95,797,1384300800"; d="scan'208";a="18630478"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-7.cisco.com with ESMTP; 07 Feb 2014 01:53:21 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s171rLKt007263 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 7 Feb 2014 01:53:21 GMT
Received: from xmb-aln-x13.cisco.com ([fe80::5404:b599:9f57:834b]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Thu, 6 Feb 2014 19:53:20 -0600
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>, "Vijay K. Gurbani" <vkg@bell-labs.com>
Thread-Topic: Gen-ART review of draft-ietf-l2vpn-evpn-req-06
Thread-Index: AQHPFsfC/0MfMrqH5kyG31zYqBDMOJqQJL6AgBja6QA=
Date: Fri, 7 Feb 2014 01:53:20 +0000
Message-ID: <CF197BB4.BD65E%sajassi@cisco.com>
In-Reply-To: <73A43A96-248E-47FD-8589-D79BC316B9C2@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [10.21.94.250]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <97F2FF5F2D30B148A952DBB1DCC7B92A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-l2vpn-evpn-req@tools.ietf.org" <draft-ietf-l2vpn-evpn-req@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, IESG IESG <iesg@ietf.org>, "l2vpn-chairs@tools.ietf.org" <l2vpn-chairs@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-l2vpn-evpn-req-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 01:53:26 -0000

Vijay, Jari:

Thanks for your comments. (R13) and (R14) are security related
requirements and to clarify this point, I have expanded on these
requirements:

(R13) A solution MUST be capable of detecting and properly handling a
situation where the same MAC address appears behind two different Ethernet
Segment (whether inadvertently or maliciously).

(R14) A solution MUST be capable of associating a MAC address to a
specific Ethernet Segment (sticky MAC) in order to help limit malicious
traffic into a network for that MAC address. This capability can limit the
appearance of spoofed MAC address on a network. When this feature is
enabled, the MAC mobility for such sticky MAC addresses are disallowed and
the traffic for such MAC addresses from any other Ethernet Segment MUST be
discarded. =20



Regards,
Ali

On 1/21/14 2:19 PM, "Jari Arkko" <jari.arkko@piuha.net> wrote:

>Thanks for your review and re-review, Vijay. And thanks for the authors
>for the changes that occurred between the two reviews.
>
>I do agree with Vijay's point about R13 and R14.
>
>Jari
>
>On Jan 21, 2014, at 6:32 PM, Vijay K. Gurbani <vkg@bell-labs.com> wrote:
>
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document: draft-ietf-l2vpn-evpn-req-06
>> Reviewer: Vijay K. Gurbani
>> Review Date: Jan-21-2014
>> IETF LC End Date: Unknown
>> IESG Telechat date: Jan-23-2014
>>=20
>> Major: 0
>> Minor: 0
>> Nits: 2
>>=20
>> This document is ready for publication as an Informational.
>>=20
>> The document is ready, most of the nits in the nit-list I had have
>> been addressed by the IESG during balloting.  That said, the remaining
>> nits on my list are:
>>=20
>> - The requirements in the Security Considerations section (R13 and R14)
>> are better put in Section 6 (Ease of Provisioning Requirements), no?
>> Is there something intrinsic to do with security on R13 and R14 that
>> they are put in the Security Considerations section?  If there is, it
>> is not apparent to me.
>>=20
>> - Grammar/language: Section 7, Requirement 9:
>> s/This gives rise to two/This results in two/
>> (Reason: "gives rise to" is probably best left to works of
>> fiction :-) )
>>=20
>> Thanks,
>>=20
>> - vijay
>> --=20
>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
>> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
>> Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq
>


From mahoney@nostrum.com  Fri Feb  7 08:23:30 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 806181A03C9 for <gen-art@ietfa.amsl.com>; Fri,  7 Feb 2014 08:23:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iTvKu2HEuB5u for <gen-art@ietfa.amsl.com>; Fri,  7 Feb 2014 08:23:29 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 310141A0177 for <gen-art@ietf.org>; Fri,  7 Feb 2014 08:23:29 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s17GNPZE015456 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Fri, 7 Feb 2014 10:23:28 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52F5087D.9090604@nostrum.com>
Date: Fri, 07 Feb 2014 10:23:25 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-02-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 16:23:30 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Ben Campbell      2014-02-21   draft-ietf-v6ops-64share-09

Brian Carpenter   2014-02-20   draft-ietf-stir-problem-statement-03

Peter Yee         2014-02-28   draft-fairhurst-ipdvb-ule-iana-05

Roni Even         2014-02-28   draft-housley-pkix-oids-00

Robert Sparks     2014-03-24   draft-mahalingam-dutt-dcops-vxlan-08

Russ Housley      2014-02-17   draft-ietf-dmm-requirements-13

Scott Brim        2014-02-18   draft-ietf-tcpm-1323bis-19

Suresh Krishnan   2014-02-18   draft-ietf-dhc-dhcpv6-unknown-msg-05

Vijay Gurbani     2014-03-05   draft-melnikov-smime-msa-to-mda-02

Wassim Haddad     2014-02-19   draft-ietf-storm-rdmap-ext-08



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 bill.wu@huawei.com  Fri Feb  7 19:55:32 2014
Return-Path: <bill.wu@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED7B1A0342 for <gen-art@ietfa.amsl.com>; Fri,  7 Feb 2014 19:55:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ro9VtQV-UGyz for <gen-art@ietfa.amsl.com>; Fri,  7 Feb 2014 19:55:29 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3E3A61A0349 for <gen-art@ietf.org>; Fri,  7 Feb 2014 19:55:29 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDJ23580; Sat, 08 Feb 2014 03:55:27 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 8 Feb 2014 03:54:37 +0000
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 8 Feb 2014 03:55:23 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.56]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Sat, 8 Feb 2014 11:55:17 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>, "draft-ietf-xrblock-rtcp-xr-synchronization.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-synchronization.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call draft-ietf-xrblock-rtcp-xr-synchronization-07
Thread-Index: Ac8hlCDu13JJMQR2QFirFof+iT/45QC7UqDg
Date: Sat, 8 Feb 2014 03:55:16 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43C7B339@nkgeml501-mbs.china.huawei.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32D38FEB@eusaamb107.ericsson.se>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A32D38FEB@eusaamb107.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.149]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA43C7B339nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Gen-art] Gen-ART Last Call draft-ietf-xrblock-rtcp-xr-synchronization-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: Sat, 08 Feb 2014 03:55:32 -0000

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

Hi, Meral:
Thanks for your comments and proposed changes.
All these changes make sense to me.
Thank you very much.

Regards!
-Qin
From: Meral Shirazipour [mailto:meral.shirazipour@ericsson.com]
Sent: Tuesday, February 04, 2014 6:32 PM
To: draft-ietf-xrblock-rtcp-xr-synchronization.all@tools.ietf.org; gen-art@=
ietf.org
Subject: Gen-ART Last Call draft-ietf-xrblock-rtcp-xr-synchronization-07

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

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

Document: draft-ietf-xrblock-rtcp-xr-synchronization-07
Reviewer: Meral Shirazipour
Review Date: 2014-02-04
IETF LC End Date:  2014-02-04
IESG Telechat date: NA


Summary:
This draft is ready to be published as Standards Track RFC but I have some =
minor comments.

Major issues:
N/A
Minor issues:
N/A

Nits/editorial comments:
-[Page 4], Section 1.4,
"used by network manager"---->"used by the network manager"


-[Page 8], Section 4.2,
"In this document, the value I=3D00 is the reserved value and MUST NOT be u=
sed."
It would be good to add if it should be ignored by receiver if used, or dis=
card the whole Synchronization Offset Report ...

-General: would be good to add caption to Figures p.5 and p.7

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

--_000_B8F9A780D330094D99AF023C5877DABA43C7B339nkgeml501mbschi_
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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size: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"color:#1F497D">Hi, Meral:<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for your commen=
ts and proposed changes.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">All these changes make=
 sense to me.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thank you very much.<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">-Qin<o:p></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;"> Meral Sh=
irazipour [mailto:meral.shirazipour@ericsson.com]
<br>
<b>Sent:</b> Tuesday, February 04, 2014 6:32 PM<br>
<b>To:</b> draft-ietf-xrblock-rtcp-xr-synchronization.all@tools.ietf.org; g=
en-art@ietf.org<br>
<b>Subject:</b> Gen-ART Last Call draft-ietf-xrblock-rtcp-xr-synchronizatio=
n-07<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-xrblock-rtcp-xr-synchronization=
-07<o:p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2014-02-04<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date:&nbsp; 2014-02-04<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: NA<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is ready to be published as Standards Tra=
ck RFC but I have some minor comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major issues:<o:p></o:p></p>
<p class=3D"MsoNormal">N/A<o:p></o:p></p>
<p class=3D"MsoNormal">Minor issues:<o:p></o:p></p>
<p class=3D"MsoNormal">N/A<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-[Page 4], Section 1.4,<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;used by network manager&quot;----&gt;&quot;use=
d by the network manager&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[Page 8], Section 4.2, <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;In this document, the value I=3D00 is the rese=
rved value and MUST NOT be used.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">It would be good to add if it should be ignored by r=
eceiver if used, or discard the whole Synchronization Offset Report ...<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-General: would be good to add caption to Figures p.=
5 and p.7<o:p></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_B8F9A780D330094D99AF023C5877DABA43C7B339nkgeml501mbschi_--

From dromasca@avaya.com  Mon Feb 10 08:25:31 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 194451A017E for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 08:25:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.147
X-Spam-Level: 
X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] 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 OtCRQdHBWrBa for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 08:25:27 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 44C4D1A0622 for <gen-art@ietf.org>; Mon, 10 Feb 2014 08:25:27 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApYOAET8+FLGmAcV/2dsb2JhbABZgkgjIThXqF8DBY4DiFSBEhZ0gicBAQMSG14BFQcOViYBBAEJERqHYwEMnkKrIBeNCYFDIIJHD2aBFASZXYU+izGDLYIq
X-IronPort-AV: E=Sophos;i="4.95,818,1384318800"; d="scan'208,217";a="48810169"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Feb 2014 11:25:26 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 10 Feb 2014 11:14:11 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Mon, 10 Feb 2014 17:25:24 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pwe3-iccp.all@tools.ietf.org" <draft-ietf-pwe3-iccp.all@tools.ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-pwe3-iccp-13.txt
Thread-Index: Ac8mfK1YD6d/W/BiTLW9KxB/AQ+PnA==
Date: Mon, 10 Feb 2014 16:25:23 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E3F6B5D@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_9904FB1B0159DA42B0B887B7FA8119CA2E3F6B5DAZFFEXMB04globa_"
MIME-Version: 1.0
Subject: [Gen-art] Gen-ART review of draft-ietf-pwe3-iccp-13.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, 10 Feb 2014 16:25:31 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3F6B5DAZFFEXMB04globa_
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: draft-ietf-pwe3-iccp-13.txt

Reviewer: Dan Romascanu

Review Date: 2/10/14

IETF LC End Date: 2/11/14

IESG Telechat date:



Summary:



Ready with issues.



This is a complex but well written document. It is ready, a number of minor=
 issues need clarification and possibly editing. Some nits also may be cons=
idered to fix



Major issues:



None



Minor issues:



1.       The document (and the name of the protocol defined here) uses the =
notion of 'chassis'. However there is no definition or reference to a defin=
ition that would clarify what a 'chassis' is.

2.       In section 7.2.2.1 - I am not a fan of transferring information in=
 text format like in the Disconnect Cause String - no interoperability resu=
lts if there no agreement on a finite set of causes. Anyway - should this n=
ot be UTF-8 format?

3.       Similar question in Section 7.2.4 - why is Aggregator Name a text?=
 Why not using AggregatorID as per IEEE 802.1AX?

4.       In Section 7.2.5 - if Port Speed corresponds to the ifHighSpeed ob=
ject in the IF-MIB, should not also Port (interface) name correspond to ifN=
ame truncated to 20 characters whenever possible?





Nits/editorial comments:



1.       Some acronyms need expansion at the first occurrence - e.g. POP, C=
O

2.       In section 3.3/i: PE nodes MAY be collocated or remote - this MAY =
needs not be capitalized.

3.       The first two lines in the diagram in page 16 are mis-aligned

4.       The diagrams in 7.1.1., 7.1.5   end at 16-bit boundary with the la=
st field defined for optional sub-TLVs. Is this intentional? Do they sugges=
t that the number of octets is always 4*n + 2? What happens else?

5.       In section 7.3.1:' -ii. PW ID TLV or generalized PW ID TLV' I thin=
k what is meant is actually ' -ii. One of PW ID TLV or generalized PW ID TL=
V'


--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3F6B5DAZFFEXMB04globa_
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 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1301615959;
	mso-list-type:hybrid;
	mso-list-template-ids:516582904 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:2069835166;
	mso-list-type:hybrid;
	mso-list-template-ids:-1020377848 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
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-pwe3-iccp-13.txt<o:p></o:p><=
/p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 2/10/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 2/11/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:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Ready with issues. <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This is a complex but well written document. It i=
s ready, a number of minor issues need clarification and possibly editing. =
Some nits also may be considered to fix<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" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 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>The document (and the name=
 of the protocol defined here) uses the notion of &#8216;chassis&#8217;. Ho=
wever there is no definition or reference to a definition that would clarif=
y what a &#8216;chassis&#8217; is.
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>In section 7.2.2.1 &#8211;=
 I am not a fan of transferring information in text format like in the Disc=
onnect Cause String &#8211; no interoperability results if there no agreeme=
nt on a finite set of causes. Anyway &#8211; should
 this not be UTF-8 format? <o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">3.<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>Similar question in Sectio=
n 7.2.4 &#8211; why is Aggregator Name a text? Why not using AggregatorID a=
s per IEEE 802.1AX?<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">4.<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 7.2.5 &#8211; i=
f Port Speed corresponds to the ifHighSpeed object in the IF-MIB, should no=
t also Port (interface) name correspond to ifName truncated to 20 character=
s whenever possible?
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt"><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" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![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>Some acronyms need expansi=
on at the first occurrence &#8211; e.g. POP, CO<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![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>In section 3.3/i: PE nodes=
 MAY be collocated or remote &#8211; this MAY needs not be capitalized.
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">3.<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>The first two lines in the=
 diagram in page 16 are mis-aligned<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">4.<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>The diagrams in 7.1.1., 7.=
1.5&nbsp;&nbsp; end at 16-bit boundary with the last field defined for opti=
onal sub-TLVs. Is this intentional? Do they suggest that the number of octe=
ts is always 4*n &#43; 2? What happens else?
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">5.<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 7.3.1:&#8217; -=
ii. PW ID TLV or generalized PW ID TLV&#8217; I think what is meant is actu=
ally &#8217; -ii. One of PW ID TLV or generalized PW ID TLV&#8217;<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E3F6B5DAZFFEXMB04globa_--

From scott.brim@gmail.com  Mon Feb 10 08:50:23 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 DA5911A0565 for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 08:50:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4bopQzIPI8-R for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 08:50:22 -0800 (PST)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 2843D1A06F9 for <gen-art@ietf.org>; Mon, 10 Feb 2014 08:50:17 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id wn1so7573467obc.9 for <gen-art@ietf.org>; Mon, 10 Feb 2014 08:50:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=lSv2ResTKLoe4j++3GPw66KNET4WRo0naoiq3qij7l8=; b=UruUj0WIUUVfx4WlOfYqnbTFEJ/AmFL+RLBDISp9LNIYZVdBSH42bVSC2aW2RwWGbn DseIfJIPU8pIrnDyOLISTOV8TUTJHNV7cC5ZcxTmhlqUVf6U1YRioiHeXhk99oT539Bb HsIP2MijQp+mmnhS80iPoppvtHHs3RiPEKFjAq0FWYI+RFLu7zDrIud6XPhyiSHkRADV OThIXNJzLT00ga4t2Fwj03Wzv/hc+iwpcPsdhaSZXzRTvukJ4Mg0k1eUSVTAqEFn/kf2 9nPCVY6diaJI8fHEajkYDh2d8hbhrxU/KhU4f4t7ludD1k60Axu79SSMnJOeVBKmEjBL RLiA==
X-Received: by 10.183.24.161 with SMTP id ij1mr15489741obd.33.1392051016796; Mon, 10 Feb 2014 08:50:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 10 Feb 2014 08:49:56 -0800 (PST)
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 10 Feb 2014 11:49:56 -0500
Message-ID: <CAPv4CP_fSxXK5iQCDvryEWvpu1j6-9heRQYnRyUTz=ht9zTsVg@mail.gmail.com>
To: gen-art <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] gen-art LC review of draft-ietf-tcpm-1323bis-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2014 16:50: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-tcpm-1323bis-19
Reviewer: Scott Brim
Review Date: 2014-02-10
IETF LC End Date: 2014-02-18
IESG Telechat date: not yet

Summary: Ready with a minor issue

Major issues: none

Minor issues:

> For brevity, the full discussions of the merits and history behind
> the TCP options defined within this document have been omitted.
> [RFC1323] should be consulted for reference.

  The reader is referred to RFC 1323 for background information
  (basically an informative reference) ... but if this draft obsoletes
  RFC 1323, can it refer the reader to it?

Nits/editorial comments: none


Thanks ... Scott

From scott.brim@gmail.com  Mon Feb 10 10:18:16 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 DF3621A0407 for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 10:18:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6coQ9wiy2z7U for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 10:18:14 -0800 (PST)
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 125F31A01E8 for <gen-art@ietf.org>; Mon, 10 Feb 2014 10:18:14 -0800 (PST)
Received: by mail-oa0-f52.google.com with SMTP id i4so7991019oah.11 for <gen-art@ietf.org>; Mon, 10 Feb 2014 10:18:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=Hy0WncPVsR34bnex92peafmjKEBJXz0l3xrUr30L+90=; b=AAVsMdgsKP5NA/ztZ2eCWxcJaHbTJWoSFHvuz974KsDujKUDXMxHwVYVxEwFo25vaw upU8VfxOMKhA4znfAuJ5C8umEAjXCd6EVHQfTi8KmsuSmnyHCyjkpS+ZjLfTbnMlV7HL RDspFchsIZSXhwEjONHhysRqOj0Acfqdbhu8m1896duVaO8idHRcxEGgWxX4snwcV0D7 qLBCSdBDeNNp5nFY/k7qeYcPuW8BjjAoZLQLfK0mtCxLGc8HaPbvpX9MKJXbDQ3LN4pL VtNGkhkr+RwvxBUmTT9L2yWW8LGhuCtEp8v8tjMIOo5V26YHTPTobbfdLbkQvuxIj3Tj 2/QQ==
X-Received: by 10.60.174.167 with SMTP id bt7mr2714441oec.54.1392056293369; Mon, 10 Feb 2014 10:18:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 10 Feb 2014 10:17:53 -0800 (PST)
In-Reply-To: <CAPv4CP_fSxXK5iQCDvryEWvpu1j6-9heRQYnRyUTz=ht9zTsVg@mail.gmail.com>
References: <CAPv4CP_fSxXK5iQCDvryEWvpu1j6-9heRQYnRyUTz=ht9zTsVg@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 10 Feb 2014 13:17:53 -0500
Message-ID: <CAPv4CP_QU1KoG6cEdYZM4XSEt_73J8X2WF5W2xXJ30sfYzwytQ@mail.gmail.com>
To: gen-art <gen-art@ietf.org>, draft-ietf-tcpm-1323bis.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Gen-art] Fwd: gen-art LC review of draft-ietf-tcpm-1323bis-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2014 18:18:17 -0000

---------- Forwarded message ----------
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, Feb 10, 2014 at 11:49 AM
Subject: gen-art LC review of draft-ietf-tcpm-1323bis-19
To: gen-art <gen-art@ietf.org>


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

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

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

Document: draft-ietf-tcpm-1323bis-19
Reviewer: Scott Brim
Review Date: 2014-02-10
IETF LC End Date: 2014-02-18
IESG Telechat date: not yet

Summary: Ready with a minor issue

Major issues: none

Minor issues:

> For brevity, the full discussions of the merits and history behind
> the TCP options defined within this document have been omitted.
> [RFC1323] should be consulted for reference.

  The reader is referred to RFC 1323 for background information
  (basically an informative reference) ... but if this draft obsoletes
  RFC 1323, can it refer the reader to it?

Nits/editorial comments: none


Thanks ... Scott

From rs@netapp.com  Mon Feb 10 11:08:52 2014
Return-Path: <rs@netapp.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 A9D701A0827 for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 11:08:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548, 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 EXkGFG2k85Os for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 11:08:50 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id A00011A07F8 for <gen-art@ietf.org>; Mon, 10 Feb 2014 11:08:50 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,819,1384329600"; d="scan'208";a="101213635"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx11-out.netapp.com with ESMTP; 10 Feb 2014 11:08:50 -0800
Received: from SACEXCMBX02-PRD.hq.netapp.com ([169.254.1.77]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Mon, 10 Feb 2014 11:08:50 -0800
From: "Scheffenegger, Richard" <rs@netapp.com>
To: Scott Brim <scott.brim@gmail.com>, gen-art <gen-art@ietf.org>, "draft-ietf-tcpm-1323bis.all@tools.ietf.org" <draft-ietf-tcpm-1323bis.all@tools.ietf.org>
Thread-Topic: gen-art LC review of draft-ietf-tcpm-1323bis-19
Thread-Index: AQHPJoyXo1uSN3BYH0qUFM/8FWUorpqu1+YQ
Date: Mon, 10 Feb 2014 19:08:49 +0000
Message-ID: <012C3117EDDB3C4781FD802A8C27DD4F26043972@SACEXCMBX02-PRD.hq.netapp.com>
References: <CAPv4CP_fSxXK5iQCDvryEWvpu1j6-9heRQYnRyUTz=ht9zTsVg@mail.gmail.com> <CAPv4CP_QU1KoG6cEdYZM4XSEt_73J8X2WF5W2xXJ30sfYzwytQ@mail.gmail.com>
In-Reply-To: <CAPv4CP_QU1KoG6cEdYZM4XSEt_73J8X2WF5W2xXJ30sfYzwytQ@mail.gmail.com>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.114]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 10 Feb 2014 11:21:07 -0800
Subject: Re: [Gen-art] gen-art LC review of draft-ietf-tcpm-1323bis-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2014 19:08:52 -0000

Hi Scott,

Thanks for your review!


It was our understanding that obsoleted and historic rfcs can still be refe=
renced...

During the discussion in the WG, much of the discussion, and historic conje=
cture was decided to have to go, to be replaced with "lessons learned". But=
 for someone not familiar, the old text describing some of the thoughts tha=
t went into the design of the options, might still be useful to know..


It's unclear to me how to address your comment.

Do you propose to remove the 2nd sentence?=20

Or is the question you actually ask in your comment something to be answere=
d by IESG, and either requires no change, or potentially the removal of all=
 1323 references throughout the document...


Richard Scheffenegger


> -----Original Message-----
> From: Scott Brim [mailto:scott.brim@gmail.com]
> Sent: Montag, 10. Februar 2014 19:18
> To: gen-art; draft-ietf-tcpm-1323bis.all@tools.ietf.org
> Subject: Fwd: gen-art LC review of draft-ietf-tcpm-1323bis-19
>=20
> ---------- Forwarded message ----------
> From: Scott Brim <scott.brim@gmail.com>
> Date: Mon, Feb 10, 2014 at 11:49 AM
> Subject: gen-art LC review of draft-ietf-tcpm-1323bis-19
> To: gen-art <gen-art@ietf.org>
>=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-tcpm-1323bis-19
> Reviewer: Scott Brim
> Review Date: 2014-02-10
> IETF LC End Date: 2014-02-18
> IESG Telechat date: not yet
>=20
> Summary: Ready with a minor issue
>=20
> Major issues: none
>=20
> Minor issues:
>=20
> > For brevity, the full discussions of the merits and history behind the
> > TCP options defined within this document have been omitted.
> > [RFC1323] should be consulted for reference.
>=20
>   The reader is referred to RFC 1323 for background information
>   (basically an informative reference) ... but if this draft obsoletes
>   RFC 1323, can it refer the reader to it?
>=20
> Nits/editorial comments: none
>=20
>=20
> Thanks ... Scott

From housley@vigilsec.com  Mon Feb 10 11:52:32 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6E741A047B; Mon, 10 Feb 2014 11:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jcg9erZ1F8L3; Mon, 10 Feb 2014 11:52:31 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id DBB591A0549; Mon, 10 Feb 2014 11:52:30 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id D06D9F2409B; Mon, 10 Feb 2014 14:52:20 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id QxULSL9I3Yrv; Mon, 10 Feb 2014 14:51:59 -0500 (EST)
Received: from [192.168.2.110] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id E120BF240A1; Mon, 10 Feb 2014 14:51:59 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 10 Feb 2014 14:51:48 -0500
Message-Id: <53AC26FD-54C8-481E-8B3B-F529C26C0C20@vigilsec.com>
To: draft-ietf-dmm-requirements.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IETF Gen-ART <gen-art@ietf.org>, IESG <iesg@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-dmm-requirements-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2014 19:52: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-dmm-requirements-14
Reviewer: Russ Housley
Review Date: 2014-02-10
IETF LC End Date: 2014-02-17
IESG Telechat date: Unknown

Summary:  Ready for publication.


Major Concerns:  None.


Minor Concerns:  None.


Other Comments:

I think that the Abstract could be more polished.  Some mention of the
anchor point seems desirable.

Spell out acronyms the first time they are used. EPC is an example that
needs to be expanded.


From scott.brim@gmail.com  Mon Feb 10 11:58:57 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B91561A0473 for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 11:58:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VMQQXrKlIz6g for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 11:58:56 -0800 (PST)
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 13E1D1A046A for <gen-art@ietf.org>; Mon, 10 Feb 2014 11:58:56 -0800 (PST)
Received: by mail-oa0-f43.google.com with SMTP id h16so8119318oag.30 for <gen-art@ietf.org>; Mon, 10 Feb 2014 11:58:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=cGPkGROfPw8X3eIn0EKoSOndqM+zE5iu++s4m8vV9MI=; b=kOoHsRLTMMaTgiyBKmSISi07LQ4LK2xWKtdO6YwpP9zPQXTg0y7cd1+p4kKUIMsKTA jZv+X0bXgFzng+EtwJba2VDsQWqTicDpJI76nq1xc5ZNsZ5k+zqROo3100u7yd5a2KVK 5EF2sMLQJUpCVXCu691o9Nyp6sRg+A/dzkstdgBH7hhPxUZLtDklNTAoinCnQ03N4LMn HeKZmYrgRBzAj9x0ASGiR4ja120Q5Zx+A1q/GIbSLlG2Zm1lf0P5ayP8PH7sLrc5+HBN jJpgAenTmPoOCGn9OR9l8pvmiHX6TRMky5ASlrW5RaNLXnOWo1V7tQzjgBAsqrWBtnXR Bafw==
X-Received: by 10.182.47.195 with SMTP id f3mr3239077obn.49.1392062335423; Mon, 10 Feb 2014 11:58:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 10 Feb 2014 11:58:35 -0800 (PST)
In-Reply-To: <5A0BDBA1-B4EA-4329-BAA3-A57599205B85@quantum.com>
References: <CAPv4CP_fSxXK5iQCDvryEWvpu1j6-9heRQYnRyUTz=ht9zTsVg@mail.gmail.com> <CAPv4CP_QU1KoG6cEdYZM4XSEt_73J8X2WF5W2xXJ30sfYzwytQ@mail.gmail.com> <5A0BDBA1-B4EA-4329-BAA3-A57599205B85@quantum.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 10 Feb 2014 14:58:35 -0500
Message-ID: <CAPv4CP94wrO-t7-ARybQx_v_XgwO=miZS3YwjcOMUxM1taC9JQ@mail.gmail.com>
To: David Borman <David.Borman@quantum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: gen-art <gen-art@ietf.org>, "draft-ietf-tcpm-1323bis.all@tools.ietf.org" <draft-ietf-tcpm-1323bis.all@tools.ietf.org>
Subject: Re: [Gen-art] gen-art LC review of draft-ietf-tcpm-1323bis-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2014 19:58:57 -0000

On Mon, Feb 10, 2014 at 2:45 PM, David Borman <David.Borman@quantum.com> wr=
ote:
> Scott,
>
> This is an informative reference, not a normative reference.  I'd only se=
e this as an issue if it was the latter, which it isn't.  The protocol spec=
ification in 1323bis stands on its own, which is why it obsoletes 1323.  Th=
is is just an informative reference so the reader knows that the original b=
ackground material in 1323 was omitted in 1323bis, and they should look at =
1323 if they want that additional history.  We decided there wasn't much va=
lue in rewriting the background material to reflect current terminology and=
 situations, and instead just refer the reader to 1323, which can be read w=
ithin the 20+ year old context in which it was originally written.
>
>                         -David

It's a "structure of our documents" question. I don't know the answer
because I've never seen this done before. Obsoleted RFCs are included
in informational references all the time, but explicitly saying "if
you want a more in-depth understanding, go look at the RFC that we are
replacing with this one" made me wonder, and I didn't find an answer
in a quick search.

If you've investigated and this is normal, then great. Otherwise I'm
sure one of my gen-art colleagues will have an answer for us very
soon. If not, the IESG will.

... Scott


From prvs=21185e6cb9=david.borman@quantum.com  Mon Feb 10 11:45:43 2014
Return-Path: <prvs=21185e6cb9=david.borman@quantum.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 ED7501A03C9 for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 11:45:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.267
X-Spam-Level: 
X-Spam-Status: No, score=-2.267 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, 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 EqJVFpkVqPBC for <gen-art@ietfa.amsl.com>; Mon, 10 Feb 2014 11:45:41 -0800 (PST)
Received: from mx0a-000ceb01.pphosted.com (mx0a-000ceb01.pphosted.com [67.231.144.126]) by ietfa.amsl.com (Postfix) with ESMTP id DEAD21A01A8 for <gen-art@ietf.org>; Mon, 10 Feb 2014 11:45:41 -0800 (PST)
Received: from pps.filterd (m0030277 [127.0.0.1]) by mx0a-000ceb01.pphosted.com (8.14.5/8.14.5) with SMTP id s1AJgkOX031141; Mon, 10 Feb 2014 11:45:38 -0800
Received: from ppoxedge2.quantum.com ([146.174.252.28]) by mx0a-000ceb01.pphosted.com with ESMTP id 1hxmfa1tad-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 10 Feb 2014 11:45:38 -0800
Received: from PPOMSG2.QUANTUM.com (10.50.35.27) by PPOXEDGE2.quantum.com (146.174.252.28) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 10 Feb 2014 12:44:58 -0700
Received: from PPOMSG1.QUANTUM.com ([10.50.35.26]) by ppomsg2 ([10.50.35.27]) with mapi id 14.03.0158.001; Mon, 10 Feb 2014 12:45:37 -0700
From: David Borman <David.Borman@quantum.com>
To: Scott Brim <scott.brim@gmail.com>
Thread-Topic: gen-art LC review of draft-ietf-tcpm-1323bis-19
Thread-Index: AQHPJoyF0E9hgg/or0WF9ynq8TSpiJqvWZSA
Date: Mon, 10 Feb 2014 19:45:36 +0000
Message-ID: <5A0BDBA1-B4EA-4329-BAA3-A57599205B85@quantum.com>
References: <CAPv4CP_fSxXK5iQCDvryEWvpu1j6-9heRQYnRyUTz=ht9zTsVg@mail.gmail.com> <CAPv4CP_QU1KoG6cEdYZM4XSEt_73J8X2WF5W2xXJ30sfYzwytQ@mail.gmail.com>
In-Reply-To: <CAPv4CP_QU1KoG6cEdYZM4XSEt_73J8X2WF5W2xXJ30sfYzwytQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.110.1]
Content-ID: <4004A0989780C54A853353770BFFF64A@QUANTUM.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2014-02-10_04:2014-02-10,2014-02-09,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1402100115
Content-Type: text/plain; charset="Windows-1252"
X-Mailman-Approved-At: Tue, 11 Feb 2014 05:18:53 -0800
Cc: gen-art <gen-art@ietf.org>, "draft-ietf-tcpm-1323bis.all@tools.ietf.org" <draft-ietf-tcpm-1323bis.all@tools.ietf.org>
Subject: Re: [Gen-art] gen-art LC review of draft-ietf-tcpm-1323bis-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2014 19:45:44 -0000

Scott,

This is an informative reference, not a normative reference.  I=92d only se=
e this as an issue if it was the latter, which it isn=92t.  The protocol sp=
ecification in 1323bis stands on its own, which is why it obsoletes 1323.  =
This is just an informative reference so the reader knows that the original=
 background material in 1323 was omitted in 1323bis, and they should look a=
t 1323 if they want that additional history.  We decided there wasn=92t muc=
h value in rewriting the background material to reflect current terminology=
 and situations, and instead just refer the reader to 1323, which can be re=
ad within the 20+ year old context in which it was originally written.

			-David


On Feb 10, 2014, at 12:17 PM, Scott Brim <scott.brim@gmail.com> wrote:

> ---------- Forwarded message ----------
> From: Scott Brim <scott.brim@gmail.com>
> Date: Mon, Feb 10, 2014 at 11:49 AM
> Subject: gen-art LC review of draft-ietf-tcpm-1323bis-19
> To: gen-art <gen-art@ietf.org>
>=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-tcpm-1323bis-19
> Reviewer: Scott Brim
> Review Date: 2014-02-10
> IETF LC End Date: 2014-02-18
> IESG Telechat date: not yet
>=20
> Summary: Ready with a minor issue
>=20
> Major issues: none
>=20
> Minor issues:
>=20
>> For brevity, the full discussions of the merits and history behind
>> the TCP options defined within this document have been omitted.
>> [RFC1323] should be consulted for reference.
>=20
>  The reader is referred to RFC 1323 for background information
>  (basically an informative reference) ... but if this draft obsoletes
>  RFC 1323, can it refer the reader to it?
>=20
> Nits/editorial comments: none
>=20
>=20
> Thanks ... Scott

----------------------------------------------------------------------
The information contained in this transmission may be confidential. Any dis=
closure, copying, or further distribution of confidential information is no=
t permitted unless such privilege is explicitly granted in writing by Quant=
um. Quantum reserves the right to have electronic communications, including=
 email and attachments, sent across its networks filtered through anti viru=
s and spam software programs and retain such messages in order to comply wi=
th applicable data security and retention requirements. Quantum is not resp=
onsible for the proper and complete transmission of the substance of this c=
ommunication or for any delay in its receipt.

From nobody Thu Feb 13 12:13:34 2014
Return-Path: <ayourtch@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 988BB1A0446; Thu, 13 Feb 2014 12:09:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.049
X-Spam-Level: 
X-Spam-Status: No, score=-10.049 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.548, 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 yCYSh_PMKbZe; Thu, 13 Feb 2014 12:08:54 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id E236D1A0441; Thu, 13 Feb 2014 12:08:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3146; q=dns/txt; s=iport; t=1392322133; x=1393531733; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=imEUXKmVTw0UYp3X86+l+BueIQ6oRiBzPf7Y4MNAh0M=; b=Tg9hNOrUKYAs6GqTLW7qMo354l13NuZd9ubYamnlWlx25krSgeaPt/Q9 RO0NhF6TbeTSOt7Jmf7deOMYC5KQoUAd8NSPFrfS7ojhB9yHjSA30UmV/ XK+YGT0HrK2M2jYmftFkfyh22+5ZFnNwRfcG5aG/HKV75VVuOsPEdMhse s=;
X-IronPort-AV: E=Sophos;i="4.95,840,1384300800"; d="scan'208";a="20288418"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-8.cisco.com with ESMTP; 13 Feb 2014 20:08:52 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s1DK8q42021506 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 13 Feb 2014 20:08:52 GMT
Received: from [10.61.163.205] (10.61.163.205) by xhc-rcd-x13.cisco.com (173.37.183.87) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 13 Feb 2014 14:08:51 -0600
Date: Thu, 13 Feb 2014 21:08:31 +0100
From: Andrew Yourtchenko <ayourtch@cisco.com>
X-X-Sender: ayourtch@ayourtch-mac
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24065A5E9111@MX15A.corp.emc.com>
Message-ID: <alpine.OSX.2.00.1402132106180.73875@ayourtch-mac>
References: <F5063677821E3B4F81ACFB7905573F24065A5E90F1@MX15A.corp.emc.com> <52EC12C4.3010503@cisco.com> <F5063677821E3B4F81ACFB7905573F24065A5E9111@MX15A.corp.emc.com>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1143318632-1392322131=:73875"
X-Originating-IP: [10.61.163.205]
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/dpvfByr-lmWYw2kP9fPxlJuU1k8
X-Mailman-Approved-At: Thu, 13 Feb 2014 12:13:31 -0800
Cc: Paul Aitken <paitken@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-yourtchenko-cisco-ies.all@tools.ietf.org" <draft-yourtchenko-cisco-ies.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "bclaise@cisco.com" <bclaise@cisco.com>, "draft-yourtchenko-cisco-ies@tools.ietf.org" <draft-yourtchenko-cisco-ies@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art review of draft-yourtchenko-cisco-ies-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 20:09:00 -0000

--0-1143318632-1392322131=:73875
Content-Type: text/plain; charset="ISO-8859-15"; format=flowed
Content-Transfer-Encoding: 8BIT

Hello Kathleen,

Today we've uploaded the new revision 
http://tools.ietf.org/html/draft-yourtchenko-cisco-ies-10

This document takes into the account the review comments (minus one 
technical issue that is outside of the authors' control).

Please let us know whether the new changes adequately addresses the 
review comments.

Many thanks!

--a


On Fri, 31 Jan 2014, Moriarty, Kathleen wrote:

> 
> Hi Paul,
>
> 
> 
> In that case, please update the abstract and introduction to make the intent of the document clear.  It would be helpful
> for the reader to understand the intent as they start reading the document.
>
> 
> 
> The discussion referenced was posted to ietf@ietf.org.  I think folks are addressing that discussion, so there is no need
> for me to jump into it.  Here is a link that should pull up all the messages on this draft in the last month across all
> mailing lists:
> 
> https://mailarchive.ietf.org/arch/search/?q=yourtchenko&qdr=m
>
> 
> 
> Best regards,
> 
> Kathleen
>
> 
> 
> From: Paul Aitken [mailto:paitken@cisco.com]
> Sent: Friday, January 31, 2014 4:17 PM
> To: Moriarty, Kathleen; gen-art@ietf.org; iesg@ietf.org; draft-yourtchenko-cisco-ies.all@tools.ietf.org
> Cc: ayourtch@cisco.com; bclaise@cisco.com; draft-yourtchenko-cisco-ies@tools.ietf.org
> Subject: Re: Gen-art review of draft-yourtchenko-cisco-ies-09
>
> 
> 
> Kathleen, All,
> 
> Apologies for jumping in here, but I wasn't privvy to the earlier discussion to which you allude.
>
>       Summary:  This draft extends RFC3954, but is specific to Cisco.
> 
> 
> No, this draft does not extend RFC 3954.
> 
> RFC 3954 specifies the NFv9 Protocol and the associated Information Model. The model is extensible, and I own the
> netflow-police hat for reviewing, approving, and actioning NFv9 extensions.
> 
> The IPFIX Protocol (RFC 7011) has its own Information Model (RFC 7012, IANA) which is also extensible upon application to
> IANA, subject to expert review by IE-doctors (RFC 7013).
> 
> The yourtchenko-cisco-ies draft extends the IPFIX Information model. Per section 6 of the draft, "IANA Considerations":
>
> 
>
>    This document specifies several new IPFIX Information Elements in the
>
>    IPFIX Information Element registry
> 
> 
> The IPFIX Information Model was initially based upon the NFv9 Information Model. Indeed, the two are generally considered
> to be synonymous.
> 
> The extensions which are being added to the IPFIX model seek to retain that synonymity by describing NFv9 elements which
> were not known or defined at the time RFC 3954 was written. These can be adopted into the IPFIX Information Model to
> retain compatibility, rather than defining equivalent IPFIX elements with different IDs from NFv9 and thus complicating
> life for every netflow collector.
> 
> Note that this is not a change to either the NFv9 or IPFIX protocols.
> 
> 
> P.
>
> 
> 
> 
>
--0-1143318632-1392322131=:73875--


From nobody Thu Feb 13 13:10:26 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 2F8231A0407 for <gen-art@ietfa.amsl.com>; Thu, 13 Feb 2014 13:10:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id scpGqKNDY38R for <gen-art@ietfa.amsl.com>; Thu, 13 Feb 2014 13:10:23 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 42CC31A04B4 for <gen-art@ietf.org>; Thu, 13 Feb 2014 13:10:22 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([137.254.4.55]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s1DLAKF8088071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Thu, 13 Feb 2014 15:10:21 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52FD34B7.8030704@nostrum.com>
Date: Thu, 13 Feb 2014 15:10:15 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 137.254.4.55 is authenticated by a trusted mechanism)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/h2HtBntyVLjsIG2B5se-4Dt7mX4
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-02-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, 13 Feb 2014 21:10:25 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Christer Holmberg 2014-02-24   draft-ietf-eman-framework-15

Dan Romascanu     2014-02-24   draft-ietf-mpls-ldp-applicability-label-adv-02

David Black       2014-02-24   draft-ietf-multimob-pmipv6-source-07

Elwyn Davies      2014-02-24   draft-ietf-mpls-tp-psc-itu-02

Francis Dupont    2014-02-25   draft-ietf-sidr-policy-qualifiers-01

Joel Halpern      2014-02-27   draft-ietf-ippm-testplan-rfc2680-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 Thu Feb 13 13:17:44 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 CBD711A04B8 for <gen-art@ietfa.amsl.com>; Thu, 13 Feb 2014 13:17:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktaEm32j9GHk for <gen-art@ietfa.amsl.com>; Thu, 13 Feb 2014 13:17:40 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 254B91A047C for <gen-art@ietf.org>; Thu, 13 Feb 2014 13:17:40 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([137.254.4.55]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s1DLHcFJ088374 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Thu, 13 Feb 2014 15:17:38 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <52FD366D.2080700@nostrum.com>
Date: Thu, 13 Feb 2014 15:17:33 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 137.254.4.55 is authenticated by a trusted mechanism)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Y7qJNFjyC3RjNuHJ-8xWCIB856k
Subject: [Gen-art] Assignments for the 2014-02-20 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, 13 Feb 2014 21:17:42 -0000

Hi all,

The following reviewers have assignments:

Reviewer            LC end       Draft
------------------------------------------------------------------------------------
Alexey Melnikov     2013-12-23   draft-montemurro-gsma-imei-urn-19 *

David Black         2014-01-27   draft-ietf-qresync-rfc5162bis-10 **

Dan Romascanu       2014-02-11   draft-ietf-pwe3-iccp-13 **
Dan Romascanu       2014-01-23 draft-ietf-dane-registry-acronyms-03 **

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

Francis Dupont      2014-02-11   draft-housley-pkix-test-oids-00 **
Francis Dupont      2013-11-27 draft-ietf-mmusic-sdp-g723-g729-05 *

Joel Halpern        2014-02-04 
draft-ietf-manet-olsrv2-rmpr-optimization-00 **
Joel Halpern        2014-02-12   draft-ietf-mpls-forwarding-08 *

Meral Shirazipour   2014-02-14   draft-ietf-l2vpn-vpls-mib-14
Meral Shirazipour   2014-02-04 
draft-ietf-xrblock-rtcp-xr-synchronization-08 *

Martin Thomson      2014-02-04   draft-ietf-alto-protocol-25 **

Roni Even           2013-12-23 
draft-allen-dispatch-imei-urn-as-instanceid-12 **
Roni Even           2014-02-04 draft-ietf-pcp-description-option-04 *

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

Robert Sparks       2014-02-04   draft-ietf-pcp-nat64-prefix64-05 *

Suresh Krishnan     2014-02-04 draft-ietf-avtext-rtp-duplication-05 *

Vijay Gurbani       2014-02-04 
draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01 *


* 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 Feb 13 13:51:28 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 40C941A0055 for <gen-art@ietfa.amsl.com>; Thu, 13 Feb 2014 13:51:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ck1ueluEncHF for <gen-art@ietfa.amsl.com>; Thu, 13 Feb 2014 13:51:25 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 8878F1A0047 for <gen-art@ietf.org>; Thu, 13 Feb 2014 13:51:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 9B3944610E2; Thu, 13 Feb 2014 13:51:24 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-222.clppva.east.verizon.net [70.106.135.222]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 124534610E0; Thu, 13 Feb 2014 13:51:23 -0800 (PST)
Message-ID: <52FD3E67.3000404@joelhalpern.com>
Date: Thu, 13 Feb 2014 16:51:35 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org
References: <52EBD16D.706@nostrum.com> <52EBFDBF.70505@joelhalpern.com>
In-Reply-To: <52EBFDBF.70505@joelhalpern.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/uvpH_G3EwQrzbxCpCyUcxwyG0Sc
Subject: Re: [Gen-art] Review: draft-ietf-mpls-forwarding-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 13 Feb 2014 21:51:27 -0000

This document is still ready for publication as an Informational RFC.
Yours,
Joel

On 1/31/14, 2:47 PM, Joel M. Halpern 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-forwarding-06
> Reviewer: Joel M. Halpern
> Review Date: 31-January-2014
> IETF LC End Date: 12-Feb-2014
> IESG Telechat date: N/A
>
> Summary: This document is ready for publication as an Informational RFC.
>
> Major issues: N/A
>
> Minor issues: N/A
>
> Nits/editorial comments: N/A
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
>


From nobody Thu Feb 13 14:51:52 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 83A661A02B7 for <gen-art@ietfa.amsl.com>; Thu, 13 Feb 2014 14:51:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2oRyPQFZ4V5A for <gen-art@ietfa.amsl.com>; Thu, 13 Feb 2014 14:51:44 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 9047F1A02CA for <gen-art@ietf.org>; Thu, 13 Feb 2014 14:51:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 9E305461751; Thu, 13 Feb 2014 14:51:36 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-222.clppva.east.verizon.net [70.106.135.222]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 0C46546173C; Thu, 13 Feb 2014 14:51:35 -0800 (PST)
Message-ID: <52FD4C85.9020302@joelhalpern.com>
Date: Thu, 13 Feb 2014 17:51:49 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org
References: <52FD34B7.8030704@nostrum.com>
In-Reply-To: <52FD34B7.8030704@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/zV0cGSJ5r5_eNyH4qO3_rGKTmOg
Subject: [Gen-art]  Review: draft-ietf-ippm-testplan-rfc2680-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, 13 Feb 2014 22:51:46 -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-ippm-testplan-rfc2680-04
     Test Plan and Results for Advancing RFC 2680 on the Standards Track
Reviewer: Joel M. Halpern
Review Date: 13-February-2014
IETF LC End Date: 27-February-2014
IESG Telechat date: N/A

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

Major issues: N/A

Minor issues: N/A

Nits/editorial comments: N/A

PS: While this reader did not follow all of the details of the 
statistical analysis, covering all of that seems to me to be out of 
scope for this document, and therefore it is ready.


From nobody Fri Feb 14 00:30:53 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 E51011A013F for <gen-art@ietfa.amsl.com>; Fri, 14 Feb 2014 00:30:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id deSsQFLOznwv for <gen-art@ietfa.amsl.com>; Fri, 14 Feb 2014 00:30:49 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8071A015B for <gen-art@ietf.org>; Fri, 14 Feb 2014 00:30:49 -0800 (PST)
X-AuditID: c6180641-b7f2f8e000002cdc-0d-52fdd432b92c
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id B1.B7.11484.234DDF25; Fri, 14 Feb 2014 09:30:42 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0387.000; Fri, 14 Feb 2014 03:30:40 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org" <draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-l2vpn-vpls-mib-14
Thread-Index: Ac8pXrfGcnMMtKEMSg6wS//ZbtRHVA==
Date: Fri, 14 Feb 2014 08:30:40 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A32D51903@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D51903eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUyuXSPn67Rlb9BBm+uK1qc2N/EZHH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugStj0dzjrAVtahXbuqexNjBeVexi5OSQEDCR 2Pn8KiOELSZx4d56ti5GLg4hgSOMEouO/WeEcJYzSiw5/4cVpIpNwEJi++/nrCAJEYEeRolV //pZQBLCAo4S/ec+gBWJCLhJHFpxhRHC1pOY9LsfaCwHB4uAqsTNtbEgYV4BX4nGi8vAShiB Nn8/tYYJxGYWEJe49WQ+E8RFAhJL9pxnhrBFJV4+/scKYStJfPw9nx2iPl9ixdMudoiZghIn Zz5hmcAoNAvJqFlIymYhKYOI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGDlKi1PLctON DDcxAuPhmASb4w7GBZ8sDzFKc7AoifN+eescJCSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoGx v0v04kUVxccesmZTnlVWijdf/ZS0h/XR3Nrk+DWbg9P/+YuszfzRe8ubrf/4Mc8gr93BYZpq 01bkrJY48e2YaWvU6ovKBx/W5oeqW545kffj+3+ryzybVFNN/gqonDe3l3i+b43pfOFXh3Nu Ns1q/VZ95YniTieVbRdCLqdv0jY6mrPxGc96JZbijERDLeai4kQAQEBHiFUCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/s91kRXTO2arbNaDc0t_qP6KwPbw
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-l2vpn-vpls-mib-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 08:30:52 -0000

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

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

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

Document: draft-ietf-l2vpn-vpls-mib-14
Reviewer: Meral Shirazipour
Review Date: 2013-02-14
IETF LC End Date:  2014-02-14
IESG Telechat date: 2014-02-20


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


Nits/editorial comments:
Suggestion: I noticed that Unsigned32 is used with 16 bit encoding. It coul=
d be good to mention it in the descriptions like other MIB documents do.
Look for "Unsigned32 (1..65535)" in the draft.


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

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CA">Document: draft-ietf-l2vpn-vpls=
-mib-14<o:p></o:p></span></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-02-14<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date:&nbsp; 2014-02-14<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2014-02-20<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is ready to be published as Standards Tra=
ck RFC but I have some editorial comments .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">Suggestion: I noticed that Unsigned32 is used with 1=
6 bit encoding. It could be good to mention it in the descriptions like oth=
er MIB documents do.<o:p></o:p></p>
<p class=3D"MsoNormal">Look for &quot;Unsigned32 (1..65535)&quot; in the dr=
aft. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D51903eusaamb107erics_--


From nobody Fri Feb 14 09:06:43 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 148AC1A02C3; Fri, 14 Feb 2014 09:06:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2C48RCu2aaT4; Fri, 14 Feb 2014 09:06:38 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 0DBB61A028B; Fri, 14 Feb 2014 09:06:38 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 781889A4307; Fri, 14 Feb 2014 12:06:27 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id 6e8fZaSbQEYD; Fri, 14 Feb 2014 12:06:25 -0500 (EST)
Received: from [192.168.2.110] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id B487A9A4304; Fri, 14 Feb 2014 12:06:26 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Feb 2014 12:06:14 -0500
Message-Id: <E0403989-8A34-4E3D-8F53-2F4338967A36@vigilsec.com>
To: draft-ietf-opsec-vpn-leakages.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/d4gs5NL5ZKuM3MbL4JDo_N3Pfjc
Cc: Fernando Gont <fgont@si6networks.com>, IETF Gen-ART <gen-art@ietf.org>, IESG <iesg@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-opsec-vpn-leakages-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 17:06:40 -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-vpn-leakages-03
Reviewer: Russ Housley
Review Date: 2014-02-14
IETF LC End Date: 2013-12-16
IESG Telechat date: 2014-02-20

Summary:  The document is almost ready for publication as a
informational RFC.  I raise minor concerns that should be resolved
before IESG evaluation.

Major Concern:

In my review of -02, I said:
>
> This document is about encrypted tunnels, and I am asking for this to
> be stated very early in the document.  Sadly, the IETF uses VPN to mean
> two very different things, please tell the reader which one is being
> discussed in the abstract and the introduction of the document.  IPsec
> and L3VPN demonstrate the two very different meanings for VPN, and
> "VPN leakage" has meaning in both of them.

I think it could be much more clear from the very beginning.
To this end I propose some alternate Abstract text:

   The subtle way in which the IPv6 and IPv4 protocols co-exist in
   typical networks, together with the lack of proper IPv6 support in
   popular Virtual Private Network (VPN) products, may inadvertently
   result in VPN traffic leaks.  That is, traffic meant to be
   transferred over an encrypted and integrity protected VPN connection
   may instead be transferred in the clear.  This document discusses
   some scenarios in which such VPN leakages may occur, either as a
   side effect of enabling IPv6 on a local network, or as a result of a
   deliberate act by a local attacker.  Additionally, this document
   offers possible mitigations for this issue.

Personal Observation:

I do not find this document very helpful.  It can be summarized as:

   If IPv6 is not supported in your VPN software, then disable IPv6
   support in all network interfaces before you try to use it.

I do not know why the OPSEC WG thinks that this message is worthy of
an RFC.


From nobody Fri Feb 14 11:09:57 2014
Return-Path: <fgont@si6networks.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 9D1041A02D0; Fri, 14 Feb 2014 11:09:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 80qWvOlGljgU; Fri, 14 Feb 2014 11:09:49 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id D9ADF1A0068; Fri, 14 Feb 2014 11:09:48 -0800 (PST)
Received: from [2001:5c0:1400:a::dfb] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.82) (envelope-from <fgont@si6networks.com>) id 1WEO8n-0000be-7S; Fri, 14 Feb 2014 20:09:37 +0100
Message-ID: <52FE6010.5000107@si6networks.com>
Date: Fri, 14 Feb 2014 15:27:28 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>,  draft-ietf-opsec-vpn-leakages.all@tools.ietf.org
References: <E0403989-8A34-4E3D-8F53-2F4338967A36@vigilsec.com>
In-Reply-To: <E0403989-8A34-4E3D-8F53-2F4338967A36@vigilsec.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/VbDC4phZxu3EKyOdTOZUXSwQkaE
Cc: IETF Gen-ART <gen-art@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-opsec-vpn-leakages-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 19:09:53 -0000

Hi, Russ,

Thanks so much for your feedback! Please find my comments in-line...

On 02/14/2014 02:06 PM, Russ Housley wrote:
> 
> Summary:  The document is almost ready for publication as a
> informational RFC.  I raise minor concerns that should be resolved
> before IESG evaluation.
> 
> Major Concern:
> 
> In my review of -02, I said:
>>
>> This document is about encrypted tunnels, and I am asking for this to
>> be stated very early in the document.  Sadly, the IETF uses VPN to mean
>> two very different things, please tell the reader which one is being
>> discussed in the abstract and the introduction of the document.  IPsec
>> and L3VPN demonstrate the two very different meanings for VPN, and
>> "VPN leakage" has meaning in both of them.
> 
> I think it could be much more clear from the very beginning.
> To this end I propose some alternate Abstract text:
> 
>    The subtle way in which the IPv6 and IPv4 protocols co-exist in
>    typical networks, together with the lack of proper IPv6 support in
>    popular Virtual Private Network (VPN) products, may inadvertently
>    result in VPN traffic leaks.  That is, traffic meant to be
>    transferred over an encrypted and integrity protected VPN connection
>    may instead be transferred in the clear.  This document discusses
>    some scenarios in which such VPN leakages may occur, either as a
>    side effect of enabling IPv6 on a local network, or as a result of a
>    deliberate act by a local attacker.  Additionally, this document
>    offers possible mitigations for this issue.

Will do. Thanks!



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

While I cannot speak for the opsec wg myself, my understanding is that
this document serves at these goals:

* Raising awareness among VPN users

* Suggesting workarounds to VPN users

* Raising awareness among vendors -- some of them have implemented
patches in response to this document.

* Briefly describing some tricky issues that might bite implementations.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sun Feb 16 16:20:31 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 92D2C1A02F0 for <gen-art@ietfa.amsl.com>; Sun, 16 Feb 2014 16:20:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IyAy9cfM4Zdl for <gen-art@ietfa.amsl.com>; Sun, 16 Feb 2014 16:20:26 -0800 (PST)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id B75261A02D0 for <gen-art@ietf.org>; Sun, 16 Feb 2014 16:20:26 -0800 (PST)
Received: by mail-pd0-f182.google.com with SMTP id v10so14280013pde.27 for <gen-art@ietf.org>; Sun, 16 Feb 2014 16:20:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=Lr2xZdUdLg8fDfuL2oxC55A07gcM/wke2jA0J/jdsis=; b=MJIRefjkv1Y+Ol2qEO2rbKljXbzkb9XJLVO0BuVH+sLoTx92p4aIc/SSkReJrip8pD U/1kx4Sim5MtAUdQRQbCsg64GjMPI5FxIs16iqwlWajukJhR66nIhXkMNIRiVdM41tYl BRGWly3W3pW5oYbs46u2G2Uxz6nutG5KhZ+/Gk9rchMaxLpzuJg47WrTLtNns9JvRigb x42wGa3cNrj3wWi80SOIb0EY8+LAPHTfWZy29sZE97DTxNBGBZOc385xp86cXFpn956K wz8UyvNG4WkrdBwpUYLNTsh1nj1V2NHEHNQ8YF9hrSW8AJwEUCt/Sp3tjY7ykHOxeN4P qw2w==
X-Received: by 10.68.0.99 with SMTP id 3mr23007180pbd.68.1392596424525; Sun, 16 Feb 2014 16:20:24 -0800 (PST)
Received: from [192.168.178.23] (22.200.69.111.dynamic.snap.net.nz. [111.69.200.22]) by mx.google.com with ESMTPSA id ns7sm39611565pbc.32.2014.02.16.16.20.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 16 Feb 2014 16:20:23 -0800 (PST)
Message-ID: <530155C7.2090206@gmail.com>
Date: Mon, 17 Feb 2014 13:20:23 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-ietf-stir-problem-statement.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/Ws0K5BO8v9h-U8Ppn0qRbllEDBA
Subject: [Gen-art] Gen-ART LC review of draft-ietf-stir-problem-statement-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, 17 Feb 2014 00:20:28 -0000

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

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

Document: draft-ietf-stir-problem-statement-03.txt
Reviewer: Brian Carpenter
Review Date: 2014-02-17
IETF LC End Date: 2014-02-20
IESG Telechat date: 2014-02-20

Summary: Ready
--------

Comments:
---------

Well written, clear, very scary.


From nobody Sun Feb 16 19:23:09 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 C8B481A0252; Sun, 16 Feb 2014 19:23:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 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.548, 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 skrX1SWhA8Yw; Sun, 16 Feb 2014 19:23:04 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id CFF261A0129; Sun, 16 Feb 2014 19:23:03 -0800 (PST)
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 s1H3Mucq029109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 Feb 2014 22:22:57 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s1H3Mucq029109
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1392607378; bh=8LXXScS+P6JA9k2uaKBfapUwxGU=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=VKKoqTOlQsXv6b2Naw2nlA287eSxs3SSPn7mytBEihojrrVsK6GiHknINmPtP5Lmk nxZrYHJVp8V8wKgCWqEuFYoLFMyPlmTnUY8Qx7u4jmc/BcUsw4aYvcUCXToMEXLmUl eQ+rAMU9q5Gxl4Fyc+/2ph3/B967JScKNVH96960=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s1H3Mucq029109
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd06.lss.emc.com (RSA Interceptor); Sun, 16 Feb 2014 19:22:46 -0800
Received: from mxhub06.corp.emc.com (mxhub06.corp.emc.com [128.222.70.203]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s1H3MicB000374 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 16 Feb 2014 22:22:45 -0500
Received: from mx15a.corp.emc.com ([169.254.1.167]) by mxhub06.corp.emc.com ([128.222.70.203]) with mapi; Sun, 16 Feb 2014 22:22:45 -0500
From: "Black, David" <david.black@emc.com>
To: "schmidt@informatik.haw-hamburg.de" <schmidt@informatik.haw-hamburg.de>, "shgao@bjtu.edu.cn" <shgao@bjtu.edu.cn>, "hkzhang@bjtu.edu.cn" <hkzhang@bjtu.edu.cn>, "mw@link-lab.net" <mw@link-lab.net>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Sun, 16 Feb 2014 22:22:43 -0500
Thread-Topic: Gen-ART review of draft-ietf-multimob-pmipv6-source-07
Thread-Index: Ac8rj4MZQa2HyqMUS1m6n+2pSS4Syw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712027281E4CC@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: mailusrhubprd02.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/0t3yRjDI8jTD2rWSLaBZQ-BLfpc
Cc: "multimob@ietf.org" <multimob@ietf.org>, "Brian Haberman \(brian@innovationslab.net\)" <brian@innovationslab.net>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-multimob-pmipv6-source-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 03:23: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-multimob-pmipv6-source-07
Reviewer: David L. Black
Review Date: Feb 16, 2014
IETF LC End Date: Feb 24, 2014

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

This draft describes multicast support for proxy mobile IPv6.  It assumes
significant understanding of multicast and specifically the PIM-SM protocol=
.

Nits/editorial comments:

-- Introduction, 3rd paragraph

Remove the word business from the following text, please:

             Such approaches (partially) follow
   the business model of providing multicast data services in parallel
   to PMIPv6 unicast routing [I-D.ietf-multimob-handover-optimization].

-- 4.3.1

The fact that PIM-SM has three phases could be made somewhat clearer here.=
=20
Suggestion:

OLD
   The granularity of mobility-related routing
   locators required in PIM depends on the complexity (phases) of its
   deployment.

   The following information is needed for all three phases of PIM as
   defined in [RFC4601].
NEW
   The granularity of mobility-related routing
   locators required in PIM depends on the complexity (specific phase)
   of its deployment.

   For all three phases of PIM deployment (see [RFC4601]), the following
   information is needed.

Also, is "deployment" the right word to describe the phases?  It implies
that not all of the phases need to be present in an implementation or
used, even if applicable.

-- 4.3.2 - 4.3.4

I would also suggest including the names of the phases from RFC 4601 in
these section titles, e.g.:

4.3.2.  Operations of PIM in Phase One (RP Tree)

-- idnits

idnits 2.13.01 found an unused reference and a couple of drafts that
have been updated:

  =3D=3D Unused Reference: 'RFC2236' is defined on line 1047, but no explic=
it
     reference was found in the text

  =3D=3D Outdated reference: A later version (-02) exists of
     draft-ietf-multimob-fmipv6-pfmipv6-multicast-01

  =3D=3D Outdated reference: A later version (-07) exists of
     draft-ietf-multimob-handover-optimization-06

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 Mon Feb 17 06:47:01 2014
Return-Path: <prvs=118abc007=schmidt@informatik.haw-hamburg.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 1DE2C1A047F; Mon, 17 Feb 2014 02:41:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.548] 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 MuszvDscQ6bd; Mon, 17 Feb 2014 02:41:16 -0800 (PST)
Received: from mx3.haw-public.haw-hamburg.de (mx3.haw-public.haw-hamburg.de [141.22.6.2]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD501A01CA; Mon, 17 Feb 2014 02:41:15 -0800 (PST)
Received: from mailgate.informatik.haw-hamburg.de ([141.22.30.74]) by mail3.is.haw-hamburg.de with ESMTP/TLS/ADH-AES256-SHA; 17 Feb 2014 11:41:12 +0100
Received: from localhost (localhost [127.0.0.1]) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id 423B210679D7; Mon, 17 Feb 2014 11:41:12 +0100 (CET)
Received: from mailgate.informatik.haw-hamburg.de ([127.0.0.1]) by localhost (mailgate.informatik.haw-hamburg.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 13124-09; Mon, 17 Feb 2014 11:41:11 +0100 (CET)
Received: from [172.27.31.57] (unknown [195.37.142.72]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTPSA id 7014310679CF;  Mon, 17 Feb 2014 11:41:11 +0100 (CET)
Message-ID: <5301E745.6020109@informatik.haw-hamburg.de>
Date: Mon, 17 Feb 2014 11:41:09 +0100
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>,  "shgao@bjtu.edu.cn" <shgao@bjtu.edu.cn>, "hkzhang@bjtu.edu.cn" <hkzhang@bjtu.edu.cn>,  "mw@link-lab.net" <mw@link-lab.net>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
References: <8D3D17ACE214DC429325B2B98F3AE712027281E4CC@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712027281E4CC@MX15A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-new at informatik.haw-hamburg.de
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/upM4lFsYYRAo43LnZ-YxIA5oX0o
X-Mailman-Approved-At: Mon, 17 Feb 2014 06:46:59 -0800
Cc: "Brian Haberman \(brian@innovationslab.net\)" <brian@innovationslab.net>, "multimob@ietf.org" <multimob@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-multimob-pmipv6-source-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 10:41:20 -0000

Hi David,

many thanks for the review and the feedback.

Please see responses inline.

On 17.02.2014 04:22, Black, David wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-multimob-pmipv6-source-07
> Reviewer: David L. Black
> Review Date: Feb 16, 2014
> IETF LC End Date: Feb 24, 2014
>
> Summary: This draft is basically ready for publication, but has nits that
> should be fixed before publication.
>
> This draft describes multicast support for proxy mobile IPv6.  It assumes
> significant understanding of multicast and specifically the PIM-SM protocol.
>
> Nits/editorial comments:
>
> -- Introduction, 3rd paragraph
>
> Remove the word business from the following text, please:
>
>               Such approaches (partially) follow
>     the business model of providing multicast data services in parallel
>     to PMIPv6 unicast routing [I-D.ietf-multimob-handover-optimization].
>

O.K., done.

> -- 4.3.1
>
> The fact that PIM-SM has three phases could be made somewhat clearer here.
> Suggestion:
>
> OLD
>     The granularity of mobility-related routing
>     locators required in PIM depends on the complexity (phases) of its
>     deployment.
>
>     The following information is needed for all three phases of PIM as
>     defined in [RFC4601].
> NEW
>     The granularity of mobility-related routing
>     locators required in PIM depends on the complexity (specific phase)
>     of its deployment.
>
>     For all three phases of PIM deployment (see [RFC4601]), the following
>     information is needed.
>

O.K., done

> Also, is "deployment" the right word to describe the phases?  It implies
> that not all of the phases need to be present in an implementation or
> used, even if applicable.
>

You're right. We have reworded

     For all three phases in the operation of PIM (see [RFC4601]), the 
following information is needed.


> -- 4.3.2 - 4.3.4
>
> I would also suggest including the names of the phases from RFC 4601 in
> these section titles, e.g.:
>
> 4.3.2.  Operations of PIM in Phase One (RP Tree)
>

Thanks, done.

> -- idnits
>
> idnits 2.13.01 found an unused reference and a couple of drafts that
> have been updated:
>
>    == Unused Reference: 'RFC2236' is defined on line 1047, but no explicit
>       reference was found in the text
>

Oh, a lapse - RFC2236 is listed mainly for historic/compatibility 
reasons. It is referenced now.

>    == Outdated reference: A later version (-02) exists of
>       draft-ietf-multimob-fmipv6-pfmipv6-multicast-01
>
>    == Outdated reference: A later version (-07) exists of
>       draft-ietf-multimob-handover-optimization-06
>

This is due to an update problem of the online tool (ID database), which 
seems fixed now.

Thanks again!

We will update the document as soon as the submission re-opens.

Best regards,

Thomas
-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °


From nobody Mon Feb 17 07:12:26 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 448791A024C for <gen-art@ietfa.amsl.com>; Mon, 17 Feb 2014 07:12:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.548, 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 v15TOi77q_nq for <gen-art@ietfa.amsl.com>; Mon, 17 Feb 2014 07:12:21 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 864FD1A04C3 for <gen-art@ietf.org>; Mon, 17 Feb 2014 07:12:20 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id s1HFCGsc027226; Mon, 17 Feb 2014 16:12:16 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201402171512.s1HFCGsc027226@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Mon, 17 Feb 2014 16:12:16 +0100
Sender: Francis.Dupont@fdupont.fr
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/o9fIr0nnfkiLLDa-1CQ7Y_Im3-Y
Cc: draft-ietf-l3vpn-mldp-vrf-in-band-signaling.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-l3vpn-mldp-vrf-in-band-signaling-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, 17 Feb 2014 15:12:23 -0000

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

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

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

Document: draft-ietf-l3vpn-mldp-vrf-in-band-signaling-03.txt
Reviewer: Francis Dupont
Review Date: 20140211
IETF LC End Date: 20140212
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - the number of authors is greater than the (soft) limit

 - 1 page 5: too many 'o' in 'co-oordination'

 - 1.2 pages 5 & 6: IMHO you should describe more terms in the Terminology
  section, e.g., UMH, RPA and even RD (as VRF is already in it)

Regards 

Francis.Dupont@fdupont.fr


From nobody Tue Feb 18 01:14:44 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 58B371A03FA; Tue, 18 Feb 2014 01:14:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zae4h1hICibf; Tue, 18 Feb 2014 01:14:35 -0800 (PST)
Received: from mail-ea0-x230.google.com (mail-ea0-x230.google.com [IPv6:2a00:1450:4013:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id C5BF11A0448; Tue, 18 Feb 2014 01:14:34 -0800 (PST)
Received: by mail-ea0-f176.google.com with SMTP id b10so3650920eae.7 for <multiple recipients>; Tue, 18 Feb 2014 01:14:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=uFtPujwSzkovtYSWYwjHwql12IUUONqTr7wcMcP4jtw=; b=d1tlm/35nic53BIIsSiUc7vUw9+PLG4FoiPypZFXfLZZFrq2YU17DQ5QzsVHLnU1KY YayiRywHqJpQdPHVMf9PWpZsng7WzFysY5opJgF5phSCMaVWPo3z6TsVbJBVFltHNu5M sfYtWgvoxnvY0032sC6ZJLyjkVhBSDLkJpBJ3Wf4IpynyQGPTkh7J4feGKGTER7C+pTw dMkXLuOnM9zXH6Xsv/2HZLCjI6Whu3iTRSsTcYTbAGvSCy0f4mDvt1hTUtSBUUpyc6uT Zpuy4g/HWmKh99GYbA/9Vqr2mK3dIxXEPfld0ndcTYz50KcnEuVWHBW2kfoVw1QL9dZ/ 3xwg==
X-Received: by 10.14.202.8 with SMTP id c8mr2340923eeo.88.1392714871414; Tue, 18 Feb 2014 01:14:31 -0800 (PST)
Received: from RoniE (bzq-109-67-98-212.red.bezeqint.net. [109.67.98.212]) by mx.google.com with ESMTPSA id u6sm67743636eep.11.2014.02.18.01.14.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 18 Feb 2014 01:14:30 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-housley-pkix-oids.all@tools.ietf.org>
Date: Tue, 18 Feb 2014 11:14:27 +0200
Message-ID: <031401cf2c89$d4a7c460$7df74d20$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0315_01CF2C9A.983157B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8sidKRf87DCw65R4apOy5PlRZ42Q==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/KGgfeC9KobR9rBYc2rNU1PqKY1Q
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [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: Tue, 18 Feb 2014 09:14:40 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0315_01CF2C9A.983157B0
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-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)

 


------=_NextPart_000_0315_01CF2C9A.983157B0
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'color:black'>draft-housley-pkix-oids-00<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;2-18<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2014&#8211;2-28<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=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 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)<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0315_01CF2C9A.983157B0--


From nobody Tue Feb 18 02:58:57 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 A65281A032F; Tue, 18 Feb 2014 02:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, 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 00KW-Nd6mWTg; Tue, 18 Feb 2014 02:58:51 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA421A00DD; Tue, 18 Feb 2014 02:58:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18552; q=dns/txt; s=iport; t=1392721128; x=1393930728; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=xwyTrbfesVS7BObpU9JxFRX7ghNcOe2hA0Qj2Ykt6S8=; b=atnW2yfGD+fewoGu0YbXqb3CnKlZrpGYRg/JMLzaymCy7nCcZxwewUJK f9u0xa0iP/AMqn8edTDyQBA8SR4/6UHZSoZWEMvrM10uzoSiEtiJ4g+D5 vkVObNtg1enT0ioIvjnY6WsI8OPvmPR44BHuAhqNylzACrTUeT2aUMBT1 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwFAIg8A1OQ/khM/2dsb2JhbABZgwY4iTa2cYEWFnSCJQEBAQMBeAEFCwsUDRYPCQMCAQIBRQYBDAEHAQEQh2kIDcsuF40KgSBGEQeEOASYLIEyhRWLXIMuO4Et
X-IronPort-AV: E=Sophos;i="4.97,501,1389744000"; d="scan'208,217";a="4717563"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 18 Feb 2014 10:58:46 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s1IAwjNg000648; Tue, 18 Feb 2014 10:58:45 GMT
Message-ID: <53033CE5.2000309@cisco.com>
Date: Tue, 18 Feb 2014 11:58:45 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Elwyn Davies <elwynd@dial.pipex.com>, General Area Review Team <gen-art@ietf.org>, Tal Mizrahi <talmi@marvell.com>
References: <1358863845.28723.19076.camel@mightyatom>
In-Reply-To: <1358863845.28723.19076.camel@mightyatom>
Content-Type: multipart/alternative; boundary="------------080008020208000101050801"
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/rO86XLaPAtDzqWjcZRlRhcPoDik
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-opsawg-oam-overview.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-opsawg-oam-overview-08.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, 18 Feb 2014 10:58:55 -0000

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

Elwyn,

Thanks for your review.
I don't plan to reply for the authors (btw, not sure I've seen a reply 
to this), and but a few clarification questions in line, to engage the 
discussion.

> I am the assigned Gen-ART 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-oam-overview-08.txt
> Reviewer: Elwyn Davies
> Review Date: 22 Jan 2013
> IETF LC End Date:25 Jan 2013
> IESG Telechat date: (if known) -
>
> Summary: In my opinion, this draft has serious issues as described
> below.
>
> Major issues:
> General 1: Title vs Abstract vs Section 1 vs actual content:
>
> Here in the UK a well-known brand of varnishes and wood preservative
> paints uses the slogan 'Does what it says on the tin!'.  If my
> understanding and the write-up in RFC 6491, OAM covers a whole lot more
> than the coverage of the specific mechanisms discussed in this
> document .. and there are various other mechanisms such as SNMP and
> Netconf that support the OAM constellation.
Can you provide an example of what you mean here?
Do you mean that SNMP (and NETCONF) can be used to monitor the OAM results?

> I would take the view that
> this document certainly does not 'do what it says on the tin'.
> Accordingly I take issue with the title as it doesn't provide a total
> overview of OAM mechanisms; the abstract closes down the scope of OAM as
> compared with RFC 6491 and s1 restricts it even more - and certainly
> does not summarize all the OAM tools and mechanisms defined in the IETF.
> The last para of s1 claims that 'management aspects are outside the
> scope of this document' - if this is really saying that this 'overview'
> of OAM skips the whole M aspect of OAM then I'm afraid the document is
> badly misnamed.  And it significantly reduces the value of the work.
Ok, the document title could be improved.
>
> General (2): The intended purpose of this document: Back in 2011 Stewart
> Bryant summarized a review of a previous version of this document from
> the routing directorate
> (https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/ entry dated 2011-08-10 referring to version 05 of the document).  IMO the initial section of that review regarding the audience of this document was well targeted and *has not been fixed*.  If this is intended as an introductory overview for people wishing to see what OAM is about in the IETF then it needs further introductory text and some background.  It should also state what its target audience actually is.
This sentence was added:

       The target audience of this document includes network equipment
        vendors, network operators and standard development organizations,
        and can be used as an index to some of the main OAM tools defined in
        the IETF.

And section 1.2


      1.2
      <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-13#section-1.2>.
      Target Audience



    The target audience of this document includes:

    o Standard development organizations - both IETF working groups and
       non-IETF organizations can benefit from this document when
       designing new OAM protocols, or when looking to reuse existing OAM
       tools for new technologies.

    o Network equipment vendors and network operators - can use this
       document as an index to some of the common IETF OAM tools.

    It should be noted that this document is not necessarily suitable for
    beginners without any background in OAM.


Please let the authors know what you would like to see.

I let the authors/doc. shepherd answer the following points.

Regards, Benoit
>
> General (3): I don't know if Scott Bradner has actually produced a proto
> shpeherd write up, but I would be intrigued to know the level of
> concensus behind this document.  In particular the tool classification
> in s1.1 and terminology in s2 (particularly s2.2.2) is that used
> exclusively in the MPLS-TP work in the IETF which is derived from the
> 802.1ag terminology.  The terminology is presented as if it is common to
> OAM work across the IETF. Does the IETF management community at large
> concur with this expansion of the applicability of the terminology set
> based on 'Management Domains' etc?
>
> General (4): As an overview, I think it would be advisable to point out
> that one reason for the multiplicity of tools is that they support at
> least four different data plane technologies (native IP, vanilla MPLS,
> MPLS-TP and PWE) and note that in several cases the data plane
> technologies rely on distinct (IP-based) management channels to allow
> the information gleaned by the operations in the the data plane to be
> reported back to the application that originated the operation.
>
>
> Minor (or at least less major) issues:
>
> s1, para1: For consistency with  the abstract, s1.1 .. and because I'd
> expect OAM to handle it as well ... OAM deals with performance
> monitoring and statistics gathering as well as dealing with degradation.
>
> s1.1: The section is entitled building blocks but actually only mentions
> one block, i.e., the OAM protocol.  Presumably this section really ought
> to say something about the applications and device drivers that have to
> instantiated in the MPs.  In particular as introduction to the text in
> the following section it should say something about classifying
> applications into continuously running or proactive monitoring and
> on-demand applications (since the latter are introduced without any
> definition in the next section.)
>
>
> s2.2.2/3: I am not familiar with 802.1 management issues and I was
> rather confused by the logical status of MIPs .  The text here seems to
> indicate that they are intermediate and generally don't terminate
> messages but then says in s2.2.3 that messages are 'destined to' MIPs.
> Looking for some additional understanding, I fetched up at Wikipedia
> (now there's a surprise) http://en.wikipedia.org/wiki/IEEE_802.1ag.
> This page mentions the concept of maintenance domains and the
> explanation of MIPs as internal points in the domain that generally
> forward messages within the domain whereas end points (MEPs) are
> effectively on the domain boundary. This makes a whole lot more sense
> and seemed to be a rather better set of term definitions than we have in
> this draft.
> I noticed eventually that the term Management Domain (MD) had appeared
> in the first line of s1.1 but does not appear in s2 at all. If we are
> going to accept the Management Domain terminology set, then MD certainly
> ought to be defined and discussed here.
>
>
> s2.2.3, para1, sentence 1:
>>    either initiates or reacts to OAM messages.
> The following sentences contradict this.  Should be 'initiates and/or
> reacts to OAM messages'.  See comment above.
>
> s3, general: The level of detail regarding the various toolsets is not
> very even.  In particular, the MPLS-TP toolset gets significantly more
> attention than others and the detail in OWAMP/TWAMP may be more than is
> desirable for an overview.
>
> s3.1: A few words about the likely suppression of pings and traceroute
> messages due to ICMP filtering is probably desirable as these limit
> their usefulness in the wider Internet.
>
> s3.3: What about RFC6374 (MPLS packet loss measurement)? It appears in
> the list in s1.4 but is not mentioned here.
>
> s3.4.1: Talking about what the MPLS working group 'is currently doing'
> will not be helpful for an archival document.
>
> s3.4.3.1: The OnDemand-CV reference is for non-TP MPLS... do you mean
> RFC 6426 which appears to be the TP variant?
>
> Nits/editorial comments:
> General: For a reader who wants to go on and look at the RFCs that
> define the various tools, it would probably be helpful to use reference
> tags that  either are or include the RFC number.
> s1.3, para 2: s/in several fronts/covering several different approaches/
>
> s2.2.2, last para: Need to expand 'p2mp'.
>
> s3.4.3.8: Should this section reference RFC6375?
>
> s3.5.1: It appears that the basic AC acronym (associated channel) is not
> defined.
>
>


--------------080008020208000101050801
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Elwyn,<br>
      <br>
      Thanks for your review.<br>
      I don't plan to reply for the authors (btw, not sure I've seen a
      reply to this), and but a few clarification questions in line, to
      engage the discussion.<br>
      <br>
    </div>
    <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
      type="cite">
      <pre wrap="">I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<a class="moz-txt-link-rfc2396E" href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>.

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

Document: draft-ietf-opsawg-oam-overview-08.txt
Reviewer: Elwyn Davies
Review Date: 22 Jan 2013
IETF LC End Date:25 Jan 2013
IESG Telechat date: (if known) -

Summary: In my opinion, this draft has serious issues as described
below.

Major issues:
General 1: Title vs Abstract vs Section 1 vs actual content:

Here in the UK a well-known brand of varnishes and wood preservative
paints uses the slogan 'Does what it says on the tin!'.  If my
understanding and the write-up in RFC 6491, OAM covers a whole lot more
than the coverage of the specific mechanisms discussed in this
document .. and there are various other mechanisms such as SNMP and
Netconf that support the OAM constellation.  </pre>
    </blockquote>
    Can you provide an example of what you mean here?<br>
    Do you mean that SNMP (and NETCONF) can be used to monitor the OAM
    results?<br>
    <br>
    <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
      type="cite">
      <pre wrap="">I would take the view that
this document certainly does not 'do what it says on the tin'.
Accordingly I take issue with the title as it doesn't provide a total
overview of OAM mechanisms; the abstract closes down the scope of OAM as
compared with RFC 6491 and s1 restricts it even more - and certainly
does not summarize all the OAM tools and mechanisms defined in the IETF.</pre>
    </blockquote>
    <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
      type="cite">
      <pre wrap="">
The last para of s1 claims that 'management aspects are outside the
scope of this document' - if this is really saying that this 'overview'
of OAM skips the whole M aspect of OAM then I'm afraid the document is
badly misnamed.  And it significantly reduces the value of the work.</pre>
    </blockquote>
    Ok, the document title could be improved.<br>
    <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
      type="cite">
      <pre wrap="">

General (2): The intended purpose of this document: Back in 2011 Stewart
Bryant summarized a review of a previous version of this document from
the routing directorate
(<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/">https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/</a> entry dated 2011-08-10 referring to version 05 of the document).  IMO the initial section of that review regarding the audience of this document was well targeted and *has not been fixed*.  If this is intended as an introductory overview for people wishing to see what OAM is about in the IETF then it needs further introductory text and some background.  It should also state what its target audience actually is.</pre>
    </blockquote>
    This sentence was added:<br>
    <blockquote>
      <pre>  The target audience of this document includes network equipment
   vendors, network operators and standard development organizations,
   and can be used as an index to some of the main OAM tools defined in
   the IETF.

</pre>
    </blockquote>
    And section 1.2<br>
    <pre class="newpage"><span class="h3"><h3><a class="selflink" name="section-1.2" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-13#section-1.2">1.2</a>. Target Audience</h3></span>

   The target audience of this document includes:

   o Standard development organizations - both IETF working groups and
      non-IETF organizations can benefit from this document when
      designing new OAM protocols, or when looking to reuse existing OAM
      tools for new technologies.

   o Network equipment vendors and network operators - can use this
      document as an index to some of the common IETF OAM tools.

   It should be noted that this document is not necessarily suitable for
   beginners without any background in OAM.</pre>
    <br>
    Please let the authors know what you would like to see.<br>
    <br>
    I let the authors/doc. shepherd answer the following points.<br>
    <br>
    Regards, Benoit <br>
    <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
      type="cite">
      <pre wrap="">

General (3): I don't know if Scott Bradner has actually produced a proto
shpeherd write up, but I would be intrigued to know the level of
concensus behind this document.  In particular the tool classification
in s1.1 and terminology in s2 (particularly s2.2.2) is that used
exclusively in the MPLS-TP work in the IETF which is derived from the
802.1ag terminology.  The terminology is presented as if it is common to
OAM work across the IETF. Does the IETF management community at large
concur with this expansion of the applicability of the terminology set
based on 'Management Domains' etc?

General (4): As an overview, I think it would be advisable to point out
that one reason for the multiplicity of tools is that they support at
least four different data plane technologies (native IP, vanilla MPLS,
MPLS-TP and PWE) and note that in several cases the data plane
technologies rely on distinct (IP-based) management channels to allow
the information gleaned by the operations in the the data plane to be
reported back to the application that originated the operation. 


Minor (or at least less major) issues:

s1, para1: For consistency with  the abstract, s1.1 .. and because I'd 
expect OAM to handle it as well ... OAM deals with performance 
monitoring and statistics gathering as well as dealing with degradation.

s1.1: The section is entitled building blocks but actually only mentions 
one block, i.e., the OAM protocol.  Presumably this section really ought 
to say something about the applications and device drivers that have to 
instantiated in the MPs.  In particular as introduction to the text in 
the following section it should say something about classifying 
applications into continuously running or proactive monitoring and 
on-demand applications (since the latter are introduced without any 
definition in the next section.)


s2.2.2/3: I am not familiar with 802.1 management issues and I was 
rather confused by the logical status of MIPs .  The text here seems to 
indicate that they are intermediate and generally don't terminate 
messages but then says in s2.2.3 that messages are 'destined to' MIPs.  
Looking for some additional understanding, I fetched up at Wikipedia 
(now there's a surprise) <a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/IEEE_802.1ag">http://en.wikipedia.org/wiki/IEEE_802.1ag</a>.  
This page mentions the concept of maintenance domains and the 
explanation of MIPs as internal points in the domain that generally 
forward messages within the domain whereas end points (MEPs) are 
effectively on the domain boundary. This makes a whole lot more sense
and seemed to be a rather better set of term definitions than we have in
this draft.  
I noticed eventually that the term Management Domain (MD) had appeared
in the first line of s1.1 but does not appear in s2 at all. If we are
going to accept the Management Domain terminology set, then MD certainly
ought to be defined and discussed here.   


s2.2.3, para1, sentence 1:
</pre>
      <blockquote type="cite">
        <pre wrap="">  either initiates or reacts to OAM messages.
</pre>
      </blockquote>
      <pre wrap="">The following sentences contradict this.  Should be 'initiates and/or 
reacts to OAM messages'.  See comment above.

s3, general: The level of detail regarding the various toolsets is not
very even.  In particular, the MPLS-TP toolset gets significantly more
attention than others and the detail in OWAMP/TWAMP may be more than is
desirable for an overview.

s3.1: A few words about the likely suppression of pings and traceroute 
messages due to ICMP filtering is probably desirable as these limit
their usefulness in the wider Internet.

s3.3: What about RFC6374 (MPLS packet loss measurement)? It appears in
the list in s1.4 but is not mentioned here.

s3.4.1: Talking about what the MPLS working group 'is currently doing' 
will not be helpful for an archival document.

s3.4.3.1: The OnDemand-CV reference is for non-TP MPLS... do you mean 
RFC 6426 which appears to be the TP variant?

Nits/editorial comments:
General: For a reader who wants to go on and look at the RFCs that 
define the various tools, it would probably be helpful to use reference 
tags that  either are or include the RFC number.
s1.3, para 2: s/in several fronts/covering several different approaches/

s2.2.2, last para: Need to expand 'p2mp'.

s3.4.3.8: Should this section reference RFC6375?

s3.5.1: It appears that the basic AC acronym (associated channel) is not 
defined.


</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------080008020208000101050801--


From nobody Tue Feb 18 03:09:23 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 B78C41A0453; Tue, 18 Feb 2014 03:09:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, 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 Z2nIa9fyMbCR; Tue, 18 Feb 2014 03:09:19 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id B6C611A03D0; Tue, 18 Feb 2014 03:09:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19630; q=dns/txt; s=iport; t=1392721755; x=1393931355; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=yxNVQbN/w0Wv35HuMiPOmBIDEc7oVTmi6uBjO778dzE=; b=I6zfaym0ubhqfVWUi3eqSzM6OW63nDj9I6o4hAps5AmRSzEYArO+XT8u K1v0JaYLoWCLmLiQCKO0OHC5Uz5CqmJDZWvQyB8FK1yWhURCTaVYwqRLT LnTo8BDKy64atCAU1Trl1VDD/kpiBlKG15L/fps0lV6oeUeGYK63qsCKE s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmsFANE+A1OQ/khR/2dsb2JhbABZgwY4iTa2cYEWFnSCJgEBBHgBEAsUDRYPCQMCAQIBRQYBDAEHAQEQh3ENyzMXjQqBFQsGAT8RB4Q4BJgsgTKFFYtcgy47gS0IFw
X-IronPort-AV: E=Sophos;i="4.97,501,1389744000"; d="scan'208,217";a="4718286"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 18 Feb 2014 11:09:13 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s1IB9D0o004703; Tue, 18 Feb 2014 11:09:13 GMT
Message-ID: <53033F59.9010000@cisco.com>
Date: Tue, 18 Feb 2014 12:09:13 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Elwyn Davies <elwynd@dial.pipex.com>, General Area Review Team <gen-art@ietf.org>, Tal Mizrahi <talmi@marvell.com>
References: <1358863845.28723.19076.camel@mightyatom> <53033CE5.2000309@cisco.com>
In-Reply-To: <53033CE5.2000309@cisco.com>
Content-Type: multipart/alternative; boundary="------------080003090707070005040706"
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/905iNSTARPtDsHHYRmIGiXcvfjg
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-opsawg-oam-overview.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-opsawg-oam-overview-08.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, 18 Feb 2014 11:09:21 -0000

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

Elwyn,

Please disregard this email. I wrongly read the date: 22/01/2014 instead 
of 22/01/2013.
My understanding is that the points have been addressed in the version 13.

Regards, Benoit
> Elwyn,
>
> Thanks for your review.
> I don't plan to reply for the authors (btw, not sure I've seen a reply 
> to this), and but a few clarification questions in line, to engage the 
> discussion.
>
>> I am the assigned Gen-ART 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-oam-overview-08.txt
>> Reviewer: Elwyn Davies
>> Review Date: 22 Jan 2013
>> IETF LC End Date:25 Jan 2013
>> IESG Telechat date: (if known) -
>>
>> Summary: In my opinion, this draft has serious issues as described
>> below.
>>
>> Major issues:
>> General 1: Title vs Abstract vs Section 1 vs actual content:
>>
>> Here in the UK a well-known brand of varnishes and wood preservative
>> paints uses the slogan 'Does what it says on the tin!'.  If my
>> understanding and the write-up in RFC 6491, OAM covers a whole lot more
>> than the coverage of the specific mechanisms discussed in this
>> document .. and there are various other mechanisms such as SNMP and
>> Netconf that support the OAM constellation.
> Can you provide an example of what you mean here?
> Do you mean that SNMP (and NETCONF) can be used to monitor the OAM 
> results?
>
>> I would take the view that
>> this document certainly does not 'do what it says on the tin'.
>> Accordingly I take issue with the title as it doesn't provide a total
>> overview of OAM mechanisms; the abstract closes down the scope of OAM as
>> compared with RFC 6491 and s1 restricts it even more - and certainly
>> does not summarize all the OAM tools and mechanisms defined in the IETF.
>> The last para of s1 claims that 'management aspects are outside the
>> scope of this document' - if this is really saying that this 'overview'
>> of OAM skips the whole M aspect of OAM then I'm afraid the document is
>> badly misnamed.  And it significantly reduces the value of the work.
> Ok, the document title could be improved.
>> General (2): The intended purpose of this document: Back in 2011 Stewart
>> Bryant summarized a review of a previous version of this document from
>> the routing directorate
>> (https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/  entry dated 2011-08-10 referring to version 05 of the document).  IMO the initial section of that review regarding the audience of this document was well targeted and *has not been fixed*.  If this is intended as an introductory overview for people wishing to see what OAM is about in the IETF then it needs further introductory text and some background.  It should also state what its target audience actually is.
> This sentence was added:
>
>        The target audience of this document includes network equipment
>         vendors, network operators and standard development organizations,
>         and can be used as an index to some of the main OAM tools defined in
>         the IETF.
>
> And section 1.2
>
>
>       1.2
>       <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-13#section-1.2>.
>       Target Audience
>
>
>
>     The target audience of this document includes:
>
>     o Standard development organizations - both IETF working groups and
>        non-IETF organizations can benefit from this document when
>        designing new OAM protocols, or when looking to reuse existing OAM
>        tools for new technologies.
>
>     o Network equipment vendors and network operators - can use this
>        document as an index to some of the common IETF OAM tools.
>
>     It should be noted that this document is not necessarily suitable for
>     beginners without any background in OAM.
>
> Please let the authors know what you would like to see.
>
> I let the authors/doc. shepherd answer the following points.
>
> Regards, Benoit
>> General (3): I don't know if Scott Bradner has actually produced a proto
>> shpeherd write up, but I would be intrigued to know the level of
>> concensus behind this document.  In particular the tool classification
>> in s1.1 and terminology in s2 (particularly s2.2.2) is that used
>> exclusively in the MPLS-TP work in the IETF which is derived from the
>> 802.1ag terminology.  The terminology is presented as if it is common to
>> OAM work across the IETF. Does the IETF management community at large
>> concur with this expansion of the applicability of the terminology set
>> based on 'Management Domains' etc?
>>
>> General (4): As an overview, I think it would be advisable to point out
>> that one reason for the multiplicity of tools is that they support at
>> least four different data plane technologies (native IP, vanilla MPLS,
>> MPLS-TP and PWE) and note that in several cases the data plane
>> technologies rely on distinct (IP-based) management channels to allow
>> the information gleaned by the operations in the the data plane to be
>> reported back to the application that originated the operation.
>>
>>
>> Minor (or at least less major) issues:
>>
>> s1, para1: For consistency with  the abstract, s1.1 .. and because I'd
>> expect OAM to handle it as well ... OAM deals with performance
>> monitoring and statistics gathering as well as dealing with degradation.
>>
>> s1.1: The section is entitled building blocks but actually only mentions
>> one block, i.e., the OAM protocol.  Presumably this section really ought
>> to say something about the applications and device drivers that have to
>> instantiated in the MPs.  In particular as introduction to the text in
>> the following section it should say something about classifying
>> applications into continuously running or proactive monitoring and
>> on-demand applications (since the latter are introduced without any
>> definition in the next section.)
>>
>>
>> s2.2.2/3: I am not familiar with 802.1 management issues and I was
>> rather confused by the logical status of MIPs .  The text here seems to
>> indicate that they are intermediate and generally don't terminate
>> messages but then says in s2.2.3 that messages are 'destined to' MIPs.
>> Looking for some additional understanding, I fetched up at Wikipedia
>> (now there's a surprise)http://en.wikipedia.org/wiki/IEEE_802.1ag.
>> This page mentions the concept of maintenance domains and the
>> explanation of MIPs as internal points in the domain that generally
>> forward messages within the domain whereas end points (MEPs) are
>> effectively on the domain boundary. This makes a whole lot more sense
>> and seemed to be a rather better set of term definitions than we have in
>> this draft.
>> I noticed eventually that the term Management Domain (MD) had appeared
>> in the first line of s1.1 but does not appear in s2 at all. If we are
>> going to accept the Management Domain terminology set, then MD certainly
>> ought to be defined and discussed here.
>>
>>
>> s2.2.3, para1, sentence 1:
>>>    either initiates or reacts to OAM messages.
>> The following sentences contradict this.  Should be 'initiates and/or
>> reacts to OAM messages'.  See comment above.
>>
>> s3, general: The level of detail regarding the various toolsets is not
>> very even.  In particular, the MPLS-TP toolset gets significantly more
>> attention than others and the detail in OWAMP/TWAMP may be more than is
>> desirable for an overview.
>>
>> s3.1: A few words about the likely suppression of pings and traceroute
>> messages due to ICMP filtering is probably desirable as these limit
>> their usefulness in the wider Internet.
>>
>> s3.3: What about RFC6374 (MPLS packet loss measurement)? It appears in
>> the list in s1.4 but is not mentioned here.
>>
>> s3.4.1: Talking about what the MPLS working group 'is currently doing'
>> will not be helpful for an archival document.
>>
>> s3.4.3.1: The OnDemand-CV reference is for non-TP MPLS... do you mean
>> RFC 6426 which appears to be the TP variant?
>>
>> Nits/editorial comments:
>> General: For a reader who wants to go on and look at the RFCs that
>> define the various tools, it would probably be helpful to use reference
>> tags that  either are or include the RFC number.
>> s1.3, para 2: s/in several fronts/covering several different approaches/
>>
>> s2.2.2, last para: Need to expand 'p2mp'.
>>
>> s3.4.3.8: Should this section reference RFC6375?
>>
>> s3.5.1: It appears that the basic AC acronym (associated channel) is not
>> defined.
>>
>>
>


--------------080003090707070005040706
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Elwyn,<br>
      <br>
      Please disregard this email. I wrongly read the date: 22/01/2014
      instead of 22/01/2013.<br>
      My understanding is that the points have been addressed in the
      version 13.<br>
      <br>
      Regards, Benoit<br>
    </div>
    <blockquote cite="mid:53033CE5.2000309@cisco.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div class="moz-cite-prefix">Elwyn,<br>
        <br>
        Thanks for your review.<br>
        I don't plan to reply for the authors (btw, not sure I've seen a
        reply to this), and but a few clarification questions in line,
        to engage the discussion.<br>
        <br>
      </div>
      <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
        type="cite">
        <pre wrap="">I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>.

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

Document: draft-ietf-opsawg-oam-overview-08.txt
Reviewer: Elwyn Davies
Review Date: 22 Jan 2013
IETF LC End Date:25 Jan 2013
IESG Telechat date: (if known) -

Summary: In my opinion, this draft has serious issues as described
below.

Major issues:
General 1: Title vs Abstract vs Section 1 vs actual content:

Here in the UK a well-known brand of varnishes and wood preservative
paints uses the slogan 'Does what it says on the tin!'.  If my
understanding and the write-up in RFC 6491, OAM covers a whole lot more
than the coverage of the specific mechanisms discussed in this
document .. and there are various other mechanisms such as SNMP and
Netconf that support the OAM constellation.  </pre>
      </blockquote>
      Can you provide an example of what you mean here?<br>
      Do you mean that SNMP (and NETCONF) can be used to monitor the OAM
      results?<br>
      <br>
      <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
        type="cite">
        <pre wrap="">I would take the view that
this document certainly does not 'do what it says on the tin'.
Accordingly I take issue with the title as it doesn't provide a total
overview of OAM mechanisms; the abstract closes down the scope of OAM as
compared with RFC 6491 and s1 restricts it even more - and certainly
does not summarize all the OAM tools and mechanisms defined in the IETF.</pre>
      </blockquote>
      <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
        type="cite">
        <pre wrap="">The last para of s1 claims that 'management aspects are outside the
scope of this document' - if this is really saying that this 'overview'
of OAM skips the whole M aspect of OAM then I'm afraid the document is
badly misnamed.  And it significantly reduces the value of the work.</pre>
      </blockquote>
      Ok, the document title could be improved.<br>
      <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
        type="cite">
        <pre wrap="">
General (2): The intended purpose of this document: Back in 2011 Stewart
Bryant summarized a review of a previous version of this document from
the routing directorate
(<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/">https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/</a> entry dated 2011-08-10 referring to version 05 of the document).  IMO the initial section of that review regarding the audience of this document was well targeted and *has not been fixed*.  If this is intended as an introductory overview for people wishing to see what OAM is about in the IETF then it needs further introductory text and some background.  It should also state what its target audience actually is.</pre>
      </blockquote>
      This sentence was added:<br>
      <blockquote>
        <pre>  The target audience of this document includes network equipment
   vendors, network operators and standard development organizations,
   and can be used as an index to some of the main OAM tools defined in
   the IETF.

</pre>
      </blockquote>
      And section 1.2<br>
      <pre class="newpage"><span class="h3"><h3><a moz-do-not-send="true" class="selflink" name="section-1.2" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-13#section-1.2">1.2</a>. Target Audience</h3></span>

   The target audience of this document includes:

   o Standard development organizations - both IETF working groups and
      non-IETF organizations can benefit from this document when
      designing new OAM protocols, or when looking to reuse existing OAM
      tools for new technologies.

   o Network equipment vendors and network operators - can use this
      document as an index to some of the common IETF OAM tools.

   It should be noted that this document is not necessarily suitable for
   beginners without any background in OAM.</pre>
      <br>
      Please let the authors know what you would like to see.<br>
      <br>
      I let the authors/doc. shepherd answer the following points.<br>
      <br>
      Regards, Benoit <br>
      <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
        type="cite">
        <pre wrap="">
General (3): I don't know if Scott Bradner has actually produced a proto
shpeherd write up, but I would be intrigued to know the level of
concensus behind this document.  In particular the tool classification
in s1.1 and terminology in s2 (particularly s2.2.2) is that used
exclusively in the MPLS-TP work in the IETF which is derived from the
802.1ag terminology.  The terminology is presented as if it is common to
OAM work across the IETF. Does the IETF management community at large
concur with this expansion of the applicability of the terminology set
based on 'Management Domains' etc?

General (4): As an overview, I think it would be advisable to point out
that one reason for the multiplicity of tools is that they support at
least four different data plane technologies (native IP, vanilla MPLS,
MPLS-TP and PWE) and note that in several cases the data plane
technologies rely on distinct (IP-based) management channels to allow
the information gleaned by the operations in the the data plane to be
reported back to the application that originated the operation. 


Minor (or at least less major) issues:

s1, para1: For consistency with  the abstract, s1.1 .. and because I'd 
expect OAM to handle it as well ... OAM deals with performance 
monitoring and statistics gathering as well as dealing with degradation.

s1.1: The section is entitled building blocks but actually only mentions 
one block, i.e., the OAM protocol.  Presumably this section really ought 
to say something about the applications and device drivers that have to 
instantiated in the MPs.  In particular as introduction to the text in 
the following section it should say something about classifying 
applications into continuously running or proactive monitoring and 
on-demand applications (since the latter are introduced without any 
definition in the next section.)


s2.2.2/3: I am not familiar with 802.1 management issues and I was 
rather confused by the logical status of MIPs .  The text here seems to 
indicate that they are intermediate and generally don't terminate 
messages but then says in s2.2.3 that messages are 'destined to' MIPs.  
Looking for some additional understanding, I fetched up at Wikipedia 
(now there's a surprise) <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/IEEE_802.1ag">http://en.wikipedia.org/wiki/IEEE_802.1ag</a>.  
This page mentions the concept of maintenance domains and the 
explanation of MIPs as internal points in the domain that generally 
forward messages within the domain whereas end points (MEPs) are 
effectively on the domain boundary. This makes a whole lot more sense
and seemed to be a rather better set of term definitions than we have in
this draft.  
I noticed eventually that the term Management Domain (MD) had appeared
in the first line of s1.1 but does not appear in s2 at all. If we are
going to accept the Management Domain terminology set, then MD certainly
ought to be defined and discussed here.   


s2.2.3, para1, sentence 1:
</pre>
        <blockquote type="cite">
          <pre wrap="">  either initiates or reacts to OAM messages.
</pre>
        </blockquote>
        <pre wrap="">The following sentences contradict this.  Should be 'initiates and/or 
reacts to OAM messages'.  See comment above.

s3, general: The level of detail regarding the various toolsets is not
very even.  In particular, the MPLS-TP toolset gets significantly more
attention than others and the detail in OWAMP/TWAMP may be more than is
desirable for an overview.

s3.1: A few words about the likely suppression of pings and traceroute 
messages due to ICMP filtering is probably desirable as these limit
their usefulness in the wider Internet.

s3.3: What about RFC6374 (MPLS packet loss measurement)? It appears in
the list in s1.4 but is not mentioned here.

s3.4.1: Talking about what the MPLS working group 'is currently doing' 
will not be helpful for an archival document.

s3.4.3.1: The OnDemand-CV reference is for non-TP MPLS... do you mean 
RFC 6426 which appears to be the TP variant?

Nits/editorial comments:
General: For a reader who wants to go on and look at the RFCs that 
define the various tools, it would probably be helpful to use reference 
tags that  either are or include the RFC number.
s1.3, para 2: s/in several fronts/covering several different approaches/

s2.2.2, last para: Need to expand 'p2mp'.

s3.4.3.8: Should this section reference RFC6375?

s3.5.1: It appears that the basic AC acronym (associated channel) is not 
defined.


</pre>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------080003090707070005040706--


From nobody Tue Feb 18 12:11:48 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 DAA091A0221 for <gen-art@ietfa.amsl.com>; Tue, 18 Feb 2014 12:11:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W1WXBR-5l82N for <gen-art@ietfa.amsl.com>; Tue, 18 Feb 2014 12:11:44 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF251A04FB for <gen-art@ietf.org>; Tue, 18 Feb 2014 12:11:44 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id s1IKBeUE025422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <gen-art@ietf.org>; Tue, 18 Feb 2014 14:11:41 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s1IKBe9t020495 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <gen-art@ietf.org>; Tue, 18 Feb 2014 14:11:40 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id s1IKBe8e008830 for <gen-art@ietf.org>; Tue, 18 Feb 2014 14:11:40 -0600 (CST)
Message-ID: <5303BEC0.2050000@bell-labs.com>
Date: Tue, 18 Feb 2014 14:12:48 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: gen-art@ietf.org
References: <52EF1879.7000708@gmail.com>
In-Reply-To: <52EF1879.7000708@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/ZvY3CQyVALn1b4HSbt1oaezDQl4
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-soc-overload-control-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, 18 Feb 2014 20:11:47 -0000

On 02/02/2014 10:18 PM, Brian E Carpenter wrote:
> Summary:  Almost ready
> --------
>
> Comments:
> ---------
> Minor Issue:
> -----------
>
> "5.6.  Forwarding the overload control parameters
>
>     Overload control is defined in a hop-by-hop manner.  Therefore,
>     forwarding the contents of the overload control parameters is
>     generally NOT RECOMMENDED and should only be performed if permitted
>     by the configuration of SIP servers.  This means that a SIP proxy
>     SHOULD strip the overload control parameters inserted by the client
>     before proxying the request further downstream."
>
> I think the reader should be reminded at this point that the proxy also
> behaves as a client, so will immediately re-insert its own "oc" parameters.
> (In fact it would be very odd if the proxy supported overload control
> upstream but not downstream.)  Vijay suggested: I can insert the following
> sentence as the last sentence of the lone paragraph in S5.6:
>
>     "Of course, the proxy can add overload control parameters pertinent
>      to itself in the Via header it inserts in the request going
>      downstream."
>
> This would be fine.

Brian: Thank you for the review.  I have added the above sentence.

I will close the loop and ping you when I release -15 after the
quarantine period.

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 Wed Feb 19 00:12:33 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 552EB1A0080 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 00:12:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548] 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 n4WG5zc9NKNf for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 00:12:29 -0800 (PST)
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 E2B7A1A02B8 for <gen-art@ietf.org>; Wed, 19 Feb 2014 00:12:28 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkANACFnBFOHCzIm/2dsb2JhbABZgkIjIThXp2kIjyyIVoEYFnSCJwEBAxIbTBIBFQcOViYBBA4NGodjAQygf6w/jHKBQSARgyuBFASZYoU9izWDLYIq
X-IronPort-AV: E=Sophos; i="4.97,504,1389762000"; d="scan'208,217"; a="50112629"
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; 19 Feb 2014 03:12:25 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 19 Feb 2014 02:59:29 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Wed, 19 Feb 2014 09:12:24 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat review of draft-ietf-dane-registry-acronyms-03
Thread-Index: Ac8tSlDUA8N1+TbcRbuptBuvgFv9vA==
Date: Wed, 19 Feb 2014 08:12:22 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E42AA10@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_9904FB1B0159DA42B0B887B7FA8119CA2E42AA10AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/vrpqnSKbn48soS7zatdflQMy5JA
Cc: "draft-ietf-dane-registry-acronyms.all@tools.ietf.org" <draft-ietf-dane-registry-acronyms.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART Telechat review of draft-ietf-dane-registry-acronyms-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 08:12:31 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E42AA10AZFFEXMB04globa_
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-dane-registry-acronyms-03

Reviewer: Dan Romascanu

Review Date: 2/19/14

IETF LC End Date:

IESG Telechat date: 2/19/14



Summary:



Ready. All issues mentioned in the IETFLC Gen-ART review were addressed. Th=
ank you.



Major issues:



Minor issues:



Nits/editorial comments:


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 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: draft-ietf-dane-registry-acronyms-03<o:=
p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 2/19/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: <o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: 2/19/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"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Ready. All issues mentioned in the IETFLC Gen-ART=
 review were addressed. Thank you.
<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_9904FB1B0159DA42B0B887B7FA8119CA2E42AA10AZFFEXMB04globa_--


From nobody Wed Feb 19 00:23:12 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 1E9B61A0080 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 00:23:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.147
X-Spam-Level: 
X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] 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 LLsbFdmnXNOL for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 00:23:08 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 855E11A0074 for <gen-art@ietf.org>; Wed, 19 Feb 2014 00:23:07 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnUPAP1oBFPGmAcV/2dsb2JhbABZgkIjIThXp2kDBY8siFaBGBZ0gicBAQMSG0wSARUHDlYmAQQKBA0ah2MBDKEArCoXjHKBQSARgjYPZoEUBJlihT2LNYMtgio
X-IronPort-AV: E=Sophos; i="4.97,504,1389762000"; d="scan'208,217"; a="43467594"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 19 Feb 2014 03:23:02 -0500
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 19 Feb 2014 03:11:17 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Wed, 19 Feb 2014 09:23:00 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART telechat review of draft-ietf-pwe3-iccp-13.txt
Thread-Index: Ac8tS8kjrB7FJfNFRI2tMAreZtQXjg==
Date: Wed, 19 Feb 2014 08:23:00 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E42AA33@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_9904FB1B0159DA42B0B887B7FA8119CA2E42AA33AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/YRMymyn1bcfdWksfQDJBkUlh8Jo
Cc: "draft-ietf-pwe3-iccp.all@tools.ietf.org" <draft-ietf-pwe3-iccp.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART telechat review of draft-ietf-pwe3-iccp-13.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, 19 Feb 2014 08:23:11 -0000

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

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



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



Document: draft-ietf-pwe3-iccp-13.txt

Reviewer: Dan Romascanu

Review Date: 2/19/14

IETF LC End Date: 2/11/14

IESG Telechat date: 2/20/14



Summary:



Ready with issues. I did not see any answer from the editors or shepherd to=
 the issues raised in the IETFLC Gen-ART review and there was no revision o=
f the document since then. Although none of the issues raised seems to be b=
locking, I believed that they should be considered and answered as part of =
the IETF Last Call Comments.



This is a complex but well written document. It is ready, a number of minor=
 issues need clarification and possibly editing. Some nits also may be cons=
idered to fix



Major issues:



None



Minor issues:



1.       The document (and the name of the protocol defined here) uses the =
notion of 'chassis'. However there is no definition or reference to a defin=
ition that would clarify what a 'chassis' is.

2.       In section 7.2.2.1 - I am not a fan of transferring information in=
 text format like in the Disconnect Cause String - no interoperability resu=
lts if there no agreement on a finite set of causes. Anyway - should this n=
ot be UTF-8 format?

3.       Similar question in Section 7.2.4 - why is Aggregator Name a text?=
 Why not using AggregatorID as per IEEE 802.1AX?

4.       In Section 7.2.5 - if Port Speed corresponds to the ifHighSpeed ob=
ject in the IF-MIB, should not also Port (interface) name correspond to ifN=
ame truncated to 20 characters whenever possible?





Nits/editorial comments:



1.       Some acronyms need expansion at the first occurrence - e.g. POP, C=
O

2.       In section 3.3/i: PE nodes MAY be collocated or remote - this MAY =
needs not be capitalized.

3.       The first two lines in the diagram in page 16 are mis-aligned

4.       The diagrams in 7.1.1., 7.1.5   end at 16-bit boundary with the la=
st field defined for optional sub-TLVs. Is this intentional? Do they sugges=
t that the number of octets is always 4*n + 2? What happens else?

5.       In section 7.3.1:' -ii. PW ID TLV or generalized PW ID TLV' I thin=
k what is meant is actually ' -ii. One of PW ID TLV or generalized PW ID TL=
V'



--_000_9904FB1B0159DA42B0B887B7FA8119CA2E42AA33AZFFEXMB04globa_
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;}
/* List Definitions */
@list l0
	{mso-list-id:1301615959;
	mso-list-type:hybrid;
	mso-list-template-ids:516582904 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:2069835166;
	mso-list-type:hybrid;
	mso-list-template-ids:-1020377848 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
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 &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"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document: draft-ietf-pwe3-iccp-13.txt<o:p></o:p><=
/p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 2/19/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 2/11/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: 2/20/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"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Ready with issues. I did not see any answer from =
the editors or shepherd to the issues raised in the IETFLC Gen-ART review a=
nd there was no revision of the document since then. Although none of the i=
ssues raised seems to be blocking,
 I believed that they should be considered and answered as part of the IETF=
 Last Call Comments.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This is a complex but well written document. It i=
s ready, a number of minor issues need clarification and possibly editing. =
Some nits also may be considered to fix<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" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 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>The document (and the name=
 of the protocol defined here) uses the notion of &#8216;chassis&#8217;. Ho=
wever there is no definition or reference to a definition that would clarif=
y what a &#8216;chassis&#8217; is.
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>In section 7.2.2.1 &#8211;=
 I am not a fan of transferring information in text format like in the Disc=
onnect Cause String &#8211; no interoperability results if there no agreeme=
nt on a finite set of causes. Anyway &#8211; should
 this not be UTF-8 format? <o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">3.<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>Similar question in Sectio=
n 7.2.4 &#8211; why is Aggregator Name a text? Why not using AggregatorID a=
s per IEEE 802.1AX?<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">4.<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 7.2.5 &#8211; i=
f Port Speed corresponds to the ifHighSpeed object in the IF-MIB, should no=
t also Port (interface) name correspond to ifName truncated to 20 character=
s whenever possible?
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt"><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" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![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>Some acronyms need expansi=
on at the first occurrence &#8211; e.g. POP, CO<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![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>In section 3.3/i: PE nodes=
 MAY be collocated or remote &#8211; this MAY needs not be capitalized.
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">3.<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>The first two lines in the=
 diagram in page 16 are mis-aligned<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">4.<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>The diagrams in 7.1.1., 7.=
1.5&nbsp;&nbsp; end at 16-bit boundary with the last field defined for opti=
onal sub-TLVs. Is this intentional? Do they suggest that the number of octe=
ts is always 4*n &#43; 2? What happens else?
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">5.<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 7.3.1:&#8217; -=
ii. PW ID TLV or generalized PW ID TLV&#8217; I think what is meant is actu=
ally &#8217; -ii. One of PW ID TLV or generalized PW ID TLV&#8217;<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>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E42AA33AZFFEXMB04globa_--


From nobody Wed Feb 19 06:31:34 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E65821A04C0 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 06:31:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9dQqpfnm3eqv for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 06:31:29 -0800 (PST)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 797571A0491 for <gen-art@ietf.org>; Wed, 19 Feb 2014 06:31:29 -0800 (PST)
Received: by mail-we0-f173.google.com with SMTP id x48so394808wes.32 for <gen-art@ietf.org>; Wed, 19 Feb 2014 06:31:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Gk93F98kd55QRiJVR22FYWexp6f0E916Yw0vhXAze8I=; b=lbYLwe0BXYmoFb017VK7kCqaXq5CSANPS7mWBCH64ut8ouEU2ZxfDUwsLO/hP0LaRa NS1nh7q8Py9SqwAYMl4/557hYabgbgCiL4isNz2vo3EvR//DDUe/6AJL/zz01467ZgZf GpASMhbpGIpmgUb9kflmlVyhGkY9xCPuGHUr1dFqd89q60r2lJMouykkeFRypoadCFyI KD9gaVjWlT8YCkPTEPlBYy5OI3aajgKju3DrVZNfna8c+rN+I9m7gJRTxLf5W0wS1Fcy E0FQI9xwTfqYdcG4zqX5f04srizLTVI6DCgF5pMM1qHNNapAosXqPDkuSvbLdIJEBaGX iw2Q==
X-Received: by 10.180.102.97 with SMTP id fn1mr1804129wib.15.1392820285625; Wed, 19 Feb 2014 06:31:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.103.68 with HTTP; Wed, 19 Feb 2014 06:31:05 -0800 (PST)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E42AA33@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA2E42AA33@AZ-FFEXMB04.global.avaya.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 19 Feb 2014 09:31:05 -0500
Message-ID: <CAA=duU3a66VKUcx3=jwimwRzNZJ4+EZCpKbS-dfUspJ+c+N8+Q@mail.gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/oeg7nlTq8921xStLxr1cCZDAH5Q
Cc: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pwe3-iccp.all@tools.ietf.org" <draft-ietf-pwe3-iccp.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-pwe3-iccp-13.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, 19 Feb 2014 14:31:32 -0000

Dan,

Thanks for the review (twice!).

Authors,

Could you please respond to Dan's review and comments?

Thanks,
Andy


On Wed, Feb 19, 2014 at 3:23 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>.
>
>
>
> Please wait for direction from your document shepherd or AD before posting a
> new version of the draft.
>
>
>
>
>
> Document: draft-ietf-pwe3-iccp-13.txt
>
> Reviewer: Dan Romascanu
>
> Review Date: 2/19/14
>
> IETF LC End Date: 2/11/14
>
> IESG Telechat date: 2/20/14
>
>
>
> Summary:
>
>
>
> Ready with issues. I did not see any answer from the editors or shepherd to
> the issues raised in the IETFLC Gen-ART review and there was no revision of
> the document since then. Although none of the issues raised seems to be
> blocking, I believed that they should be considered and answered as part of
> the IETF Last Call Comments.
>
>
>
> This is a complex but well written document. It is ready, a number of minor
> issues need clarification and possibly editing. Some nits also may be
> considered to fix
>
>
>
> Major issues:
>
>
>
> None
>
>
>
> Minor issues:
>
>
>
> 1.       The document (and the name of the protocol defined here) uses the
> notion of 'chassis'. However there is no definition or reference to a
> definition that would clarify what a 'chassis' is.
>
> 2.       In section 7.2.2.1 - I am not a fan of transferring information in
> text format like in the Disconnect Cause String - no interoperability
> results if there no agreement on a finite set of causes. Anyway - should
> this not be UTF-8 format?
>
> 3.       Similar question in Section 7.2.4 - why is Aggregator Name a text?
> Why not using AggregatorID as per IEEE 802.1AX?
>
> 4.       In Section 7.2.5 - if Port Speed corresponds to the ifHighSpeed
> object in the IF-MIB, should not also Port (interface) name correspond to
> ifName truncated to 20 characters whenever possible?
>
>
>
>
>
> Nits/editorial comments:
>
>
>
> 1.       Some acronyms need expansion at the first occurrence - e.g. POP, CO
>
> 2.       In section 3.3/i: PE nodes MAY be collocated or remote - this MAY
> needs not be capitalized.
>
> 3.       The first two lines in the diagram in page 16 are mis-aligned
>
> 4.       The diagrams in 7.1.1., 7.1.5   end at 16-bit boundary with the
> last field defined for optional sub-TLVs. Is this intentional? Do they
> suggest that the number of octets is always 4*n + 2? What happens else?
>
> 5.       In section 7.3.1:' -ii. PW ID TLV or generalized PW ID TLV' I think
> what is meant is actually ' -ii. One of PW ID TLV or generalized PW ID TLV'
>
>
>
>


From nobody Wed Feb 19 10:36:15 2014
Return-Path: <ssalam@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 BBB6D1A0512 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 10:30:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.049
X-Spam-Level: 
X-Spam-Status: No, score=-10.049 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.548, 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 HuRkhqLfXTId for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 10:30:28 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id D08781A0500 for <gen-art@ietf.org>; Wed, 19 Feb 2014 10:30:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3810; q=dns/txt; s=iport; t=1392834625; x=1394044225; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=thnOUmUn2TdKqlntG/JfbRYYQf3AS3JWksTECdB+Wps=; b=eWEbL1B62dN9rSKYjfaOpBHJmsDkcMil0X/c7O4esVrXcgR3HCLE5hjY 5V7UFM/3lOy/5RuFXQv8lZh3A6ZD0c/oM6f0Qo9W/eLaRE/1USnV4o3nk KWRqWMEF7Gx7Lku4rDdgAIFBSWmx9BuCFjtJ9/UvhiANb/ytM+UdR/lZ5 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAIP3BFOtJXG9/2dsb2JhbABZgmUhOFe/fIEbFnSCJQEBAQR5EgEIFARPESUBAQQKBAWHcQMRAQzGEA2HcBeMTyOBcgeEOASWRIFsgTKLLIVGgy2CKg
X-IronPort-AV: E=Sophos;i="4.97,507,1389744000"; d="scan'208";a="21653377"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by alln-iport-8.cisco.com with ESMTP; 19 Feb 2014 18:30:24 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id s1JIUO0Q019894 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Feb 2014 18:30:24 GMT
Received: from xmb-aln-x13.cisco.com ([fe80::5404:b599:9f57:834b]) by xhc-rcd-x04.cisco.com ([::1]) with mapi id 14.03.0123.003; Wed, 19 Feb 2014 12:30:24 -0600
From: "Samer Salam (ssalam)" <ssalam@cisco.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Thread-Topic: Gen-ART telechat review of draft-ietf-pwe3-iccp-13.txt
Thread-Index: Ac8tS8kjrB7FJfNFRI2tMAreZtQXjgAZboGA//+8vYA=
Date: Wed, 19 Feb 2014 18:30:22 +0000
Message-ID: <CF2A34E3.22FD2%ssalam@cisco.com>
In-Reply-To: <CAA=duU3a66VKUcx3=jwimwRzNZJ4+EZCpKbS-dfUspJ+c+N8+Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [10.21.90.94]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <46D1908AC67D1E43A29FBCC88724E161@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/dn7USVkcYuKPrq25-K_zxdZ9_r0
X-Mailman-Approved-At: Wed, 19 Feb 2014 10:36:12 -0800
Cc: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pwe3-iccp.all@tools.ietf.org" <draft-ietf-pwe3-iccp.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-pwe3-iccp-13.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, 19 Feb 2014 18:30:30 -0000

Hi Dan,=20

Thank you for your review. Please find responses inline=8A

Hi Andy,

Please let us know when we can go ahead an update the draft to address the
review comments.


Regards,
Samer

On 2014-02-19 6:31 AM, "Andrew G. Malis" <agmalis@gmail.com> wrote:

>Dan,
>
>Thanks for the review (twice!).
>
>Authors,
>
>Could you please respond to Dan's review and comments?
>
>Thanks,
>Andy
>
>
>On Wed, Feb 19, 2014 at 3:23 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>.
>>
>>
>>
>> Please wait for direction from your document shepherd or AD before
>>posting a
>> new version of the draft.
>>
>>
>>
>>
>>
>> Document: draft-ietf-pwe3-iccp-13.txt
>>
>> Reviewer: Dan Romascanu
>>
>> Review Date: 2/19/14
>>
>> IETF LC End Date: 2/11/14
>>
>> IESG Telechat date: 2/20/14
>>
>>
>>
>> Summary:
>>
>>
>>
>> Ready with issues. I did not see any answer from the editors or
>>shepherd to
>> the issues raised in the IETFLC Gen-ART review and there was no
>>revision of
>> the document since then. Although none of the issues raised seems to be
>> blocking, I believed that they should be considered and answered as
>>part of
>> the IETF Last Call Comments.
>>
>>
>>
>> This is a complex but well written document. It is ready, a number of
>>minor
>> issues need clarification and possibly editing. Some nits also may be
>> considered to fix
>>
>>
>>
>> Major issues:
>>
>>
>>
>> None
>>
>>
>>
>> Minor issues:
>>
>>
>>
>> 1.       The document (and the name of the protocol defined here) uses
>>the
>> notion of 'chassis'. However there is no definition or reference to a
>> definition that would clarify what a 'chassis' is.

Good point, will add a definition to that effect.

>>
>> 2.       In section 7.2.2.1 - I am not a fan of transferring
>>information in
>> text format like in the Disconnect Cause String - no interoperability
>> results if there no agreement on a finite set of causes. Anyway - should
>> this not be UTF-8 format?

This is meant to relay information to a human user, and not intended to be
used to take any automated actions. Will clarify that it is UTF-8.

>>
>> 3.       Similar question in Section 7.2.4 - why is Aggregator Name a
>>text?
>> Why not using AggregatorID as per IEEE 802.1AX?

The AggregatorID is already part of the TLV. The name is to enhance human
usability, same reason as above.

>>
>> 4.       In Section 7.2.5 - if Port Speed corresponds to the ifHighSpeed
>> object in the IF-MIB, should not also Port (interface) name correspond
>>to
>> ifName truncated to 20 characters whenever possible?
>>

Agreed, will update accordingly.

>>
>>
>>
>>
>> Nits/editorial comments:
>>
>>
>>
>> 1.       Some acronyms need expansion at the first occurrence - e.g.
>>POP, CO

Will update the draft accordingly.

>>
>> 2.       In section 3.3/i: PE nodes MAY be collocated or remote - this
>>MAY
>> needs not be capitalized.

Will fix.

>>
>> 3.       The first two lines in the diagram in page 16 are mis-aligned

Will fix.

>>
>> 4.       The diagrams in 7.1.1., 7.1.5   end at 16-bit boundary with the
>> last field defined for optional sub-TLVs. Is this intentional? Do they
>> suggest that the number of octets is always 4*n + 2? What happens else?

No that was not intentional. Will add text to clarify that there are no
such assumptions.

>>
>> 5.       In section 7.3.1:' -ii. PW ID TLV or generalized PW ID TLV' I
>>think
>> what is meant is actually ' -ii. One of PW ID TLV or generalized PW ID
>>TLV'

Will update.

>>
>>
>>
>>


From nobody Wed Feb 19 13:34:25 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 111FF1A0418 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 13:34:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6i9_K3vClC7G for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 13:34:18 -0800 (PST)
Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 14A231A0244 for <gen-art@ietf.org>; Wed, 19 Feb 2014 13:34:17 -0800 (PST)
Received: by mail-qa0-f44.google.com with SMTP id w5so1569767qac.17 for <gen-art@ietf.org>; Wed, 19 Feb 2014 13:34:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=KWdxb7MBU4hdVf3XVCVXQ66Vb5+uST/n7Y+ceD2CbZ0=; b=QIzYsMEz3KCzKDZhIya+alQwfrD4DNLemjtDEqWirzT8nT4kAegeLiqJruDynL7nWa vz3uWf2Y7Ame6LS+juQpM07zr3BmhxEyes4hkRtd4KA6geNoDPS/BmNYXDQja7nSYLCe nzdp0XnzEXyrAGzz/FIEslsKRvcZTVRtF4lsTcm9+bSaNF7lUOBzpIzWxHYu9S42JpVO asWYPR5AWcX0A6nZh/9dCZb0aevAUlyqTT1UNWMTzTyF7WOFKJcgxt9dOpgenws/P5wX w5vwcpnl5rbsFxGhnYzt6ZFE7FNdxpvEnmX27pn3mQtt4rN6gC9mIugzS9d9pQxNAioh 4qKw==
X-Received: by 10.140.94.74 with SMTP id f68mr51010099qge.64.1392845654550; Wed, 19 Feb 2014 13:34:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.92.136 with HTTP; Wed, 19 Feb 2014 13:33:54 -0800 (PST)
In-Reply-To: <CF2A34E3.22FD2%ssalam@cisco.com>
References: <CAA=duU3a66VKUcx3=jwimwRzNZJ4+EZCpKbS-dfUspJ+c+N8+Q@mail.gmail.com> <CF2A34E3.22FD2%ssalam@cisco.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 19 Feb 2014 16:33:54 -0500
Message-ID: <CAA=duU0ixoxsE14ssL+OZUpZB=LjhW=SWi9XLBEvbcO3n+vnFg@mail.gmail.com>
To: "Samer Salam (ssalam)" <ssalam@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/QpQ94PSN9PegJOosAJUtOGHRjc8
Cc: Stewart Bryant <stbryant@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pwe3-iccp.all@tools.ietf.org" <draft-ietf-pwe3-iccp.all@tools.ietf.org>, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-pwe3-iccp-13.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, 19 Feb 2014 21:34:21 -0000

Samer,

Thanks for responding to Dan.

The timing for a new revision is up to Stewart - don't take any action
until you hear from him.

Cheers,
Andy

On Wed, Feb 19, 2014 at 1:30 PM, Samer Salam (ssalam) <ssalam@cisco.com> wr=
ote:
> Hi Dan,
>
> Thank you for your review. Please find responses inline=C5=A0
>
> Hi Andy,
>
> Please let us know when we can go ahead an update the draft to address th=
e
> review comments.
>
>
> Regards,
> Samer
>
> On 2014-02-19 6:31 AM, "Andrew G. Malis" <agmalis@gmail.com> wrote:
>
>>Dan,
>>
>>Thanks for the review (twice!).
>>
>>Authors,
>>
>>Could you please respond to Dan's review and comments?
>>
>>Thanks,
>>Andy
>>
>>
>>On Wed, Feb 19, 2014 at 3:23 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>.
>>>
>>>
>>>
>>> Please wait for direction from your document shepherd or AD before
>>>posting a
>>> new version of the draft.
>>>
>>>
>>>
>>>
>>>
>>> Document: draft-ietf-pwe3-iccp-13.txt
>>>
>>> Reviewer: Dan Romascanu
>>>
>>> Review Date: 2/19/14
>>>
>>> IETF LC End Date: 2/11/14
>>>
>>> IESG Telechat date: 2/20/14
>>>
>>>
>>>
>>> Summary:
>>>
>>>
>>>
>>> Ready with issues. I did not see any answer from the editors or
>>>shepherd to
>>> the issues raised in the IETFLC Gen-ART review and there was no
>>>revision of
>>> the document since then. Although none of the issues raised seems to be
>>> blocking, I believed that they should be considered and answered as
>>>part of
>>> the IETF Last Call Comments.
>>>
>>>
>>>
>>> This is a complex but well written document. It is ready, a number of
>>>minor
>>> issues need clarification and possibly editing. Some nits also may be
>>> considered to fix
>>>
>>>
>>>
>>> Major issues:
>>>
>>>
>>>
>>> None
>>>
>>>
>>>
>>> Minor issues:
>>>
>>>
>>>
>>> 1.       The document (and the name of the protocol defined here) uses
>>>the
>>> notion of 'chassis'. However there is no definition or reference to a
>>> definition that would clarify what a 'chassis' is.
>
> Good point, will add a definition to that effect.
>
>>>
>>> 2.       In section 7.2.2.1 - I am not a fan of transferring
>>>information in
>>> text format like in the Disconnect Cause String - no interoperability
>>> results if there no agreement on a finite set of causes. Anyway - shoul=
d
>>> this not be UTF-8 format?
>
> This is meant to relay information to a human user, and not intended to b=
e
> used to take any automated actions. Will clarify that it is UTF-8.
>
>>>
>>> 3.       Similar question in Section 7.2.4 - why is Aggregator Name a
>>>text?
>>> Why not using AggregatorID as per IEEE 802.1AX?
>
> The AggregatorID is already part of the TLV. The name is to enhance human
> usability, same reason as above.
>
>>>
>>> 4.       In Section 7.2.5 - if Port Speed corresponds to the ifHighSpee=
d
>>> object in the IF-MIB, should not also Port (interface) name correspond
>>>to
>>> ifName truncated to 20 characters whenever possible?
>>>
>
> Agreed, will update accordingly.
>
>>>
>>>
>>>
>>>
>>> Nits/editorial comments:
>>>
>>>
>>>
>>> 1.       Some acronyms need expansion at the first occurrence - e.g.
>>>POP, CO
>
> Will update the draft accordingly.
>
>>>
>>> 2.       In section 3.3/i: PE nodes MAY be collocated or remote - this
>>>MAY
>>> needs not be capitalized.
>
> Will fix.
>
>>>
>>> 3.       The first two lines in the diagram in page 16 are mis-aligned
>
> Will fix.
>
>>>
>>> 4.       The diagrams in 7.1.1., 7.1.5   end at 16-bit boundary with th=
e
>>> last field defined for optional sub-TLVs. Is this intentional? Do they
>>> suggest that the number of octets is always 4*n + 2? What happens else?
>
> No that was not intentional. Will add text to clarify that there are no
> such assumptions.
>
>>>
>>> 5.       In section 7.3.1:' -ii. PW ID TLV or generalized PW ID TLV' I
>>>think
>>> what is meant is actually ' -ii. One of PW ID TLV or generalized PW ID
>>>TLV'
>
> Will update.
>
>>>
>>>
>>>
>>>
>


From nobody Wed Feb 19 14:02:20 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07E181A0226 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 14:02:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 49a3Fb_FXqYm for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 14:02:16 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id BF8E21A0214 for <gen-art@ietf.org>; Wed, 19 Feb 2014 14:02:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6D49D2CEAE; Thu, 20 Feb 2014 00:02:11 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3QJ6rlzyktww; Thu, 20 Feb 2014 00:02:09 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 9DC9B2CC5D; Thu, 20 Feb 2014 00:02:09 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52F020FE.6090904@nostrum.com>
Date: Wed, 19 Feb 2014 23:02:09 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A80D8C8F-6D7F-4468-9EE8-488A2B70D347@piuha.net>
References: <52F020FE.6090904@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/6z--rOgNJ0n0t2MmXcFM7sHWwNs
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-pcp-nat64-prefix64@tools.ietf.org
Subject: Re: [Gen-art] [pcp] Gen-art LC review: draft-ietf-pcp-nat64-prefix64-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, 19 Feb 2014 22:02:19 -0000

Thanks for your review, Robert. Mohamed, others, I see that you've taken =
the comments into account. Thanks!

Jari

On Feb 4, 2014, at 12:06 AM, Robert Sparks <rjsparks@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-pcp-nat64-prefix64-04
> Reviewer: Robert Sparks
> Review Date: 3-Jan-2014
> IETF LC End Date: 4-Jan-2014
> IESG Telechat date: Unknown
>=20
> Summary: Ready with Nits
>=20
> Nits/editorial comments:
>=20
> There are several references to expired drafts (some very expired).
> If those are not going to progress, the details you wanted to call out =
would be better moved here.
>=20
> It's not clear which of the results in nat64-experiments you are =
pointing to for support for this document.
> Is the reference necessary? If so, can it be made more specific.
>=20
> In section 4.1, you restate the allowed values for length from =
RFC6052. Consider making the statement
> even clearer that these values are a consequence of RFC6052 and aren't =
being defined by this document.
> Something like "The allowed values are specified in RFC6052 (currently =
4,5,6,7,8,12).
> (I almost didn't include this since that set's not likely to change, =
but somebody might copy the style...)
>=20
> RjS
>=20
>=20
>=20
> _______________________________________________
> pcp mailing list
> pcp@ietf.org
> https://www.ietf.org/mailman/listinfo/pcp


From nobody Wed Feb 19 14:04:14 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 958F31A0529 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 14:04:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 Pe45YSa4G626 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 14:04:10 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB891A0272 for <gen-art@ietf.org>; Wed, 19 Feb 2014 14:04:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id BCCE82CEAE; Thu, 20 Feb 2014 00:04:06 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fRpXPR0S371F; Thu, 20 Feb 2014 00:04:06 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D34002CC5D; Thu, 20 Feb 2014 00:04:05 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <E721D8C6A2E1544DB2DEBC313AF54DE2243BF434@xmb-rcd-x02.cisco.com>
Date: Wed, 19 Feb 2014 23:04:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5EEC1C8-652F-4188-BE82-64528711024B@piuha.net>
References: <201311251357.rAPDvjtA037008@givry.fdupont.fr> <003101cee9f8$63890b50$2a9b21f0$@co.in> <E721D8C6A2E1544DB2DEBC313AF54DE2243BE719@xmb-rcd-x02.cisco.com> <52E8E9F3.10100@ericsson.com> <E721D8C6A2E1544DB2DEBC313AF54DE2243BF434@xmb-rcd-x02.cisco.com>
To: Muthu Arul Mozhi Perumal (mperumal) <mperumal@cisco.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/6qopbmswLjxE8_UmOkwj7r-EpxY
Cc: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "Flemming Andreasen \(fandreas\)" <fandreas@cisco.com>, "draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org" <draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org>, Parthasarathi R <partha@parthasarathi.co.in>
Subject: Re: [Gen-art] review of draft-ietf-mmusic-sdp-g723-g729-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 22:04:12 -0000

Thanks guys for the edits (and for catching the one that shouldn't be =
done!). And thank you again Francis for your in-depth review. All =
appreciated. I have balloted no-obj.

Jari

On Jan 29, 2014, at 6:45 PM, Muthu Arul Mozhi Perumal (mperumal) =
<mperumal@cisco.com> wrote:

> Hi Ari,
>=20
> Good catch. Will retrain the existing text for this one..
>=20
> thanks,
> Muthu
>=20
> |-----Original Message-----
> |From: Ari Ker=E4nen [mailto:ari.keranen@ericsson.com]
> |Sent: Wednesday, January 29, 2014 5:16 PM
> |To: Muthu Arul Mozhi Perumal (mperumal); Parthasarathi R; =
Francis.Dupont@fdupont.fr; gen-art@ietf.org
> |Cc: draft-ietf-mmusic-sdp-g723-g729.all@tools.ietf.org; Flemming =
Andreasen (fandreas)
> |Subject: Re: review of draft-ietf-mmusic-sdp-g723-g729-04.txt
> |
> |Hi,
> |
> |Regarding this change, I think we should keep the original version =
since
> |this is a direct quote from RFC4856.
> |
> |
> |Cheers,
> |Ari
> |
> |On 29/01/14 07:07, Muthu Arul Mozhi Perumal (mperumal) wrote:
> |> |- 1 page 3 (wording suggestion): implied if -> implied when
> |>
> |> Addressed.
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Feb 19 14:09:50 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B168B1A0276; Wed, 19 Feb 2014 14:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 pUi57moZDwEk; Wed, 19 Feb 2014 14:09:48 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4251A0226; Wed, 19 Feb 2014 14:09:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7F2362CEAE; Thu, 20 Feb 2014 00:09:44 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k7-3FIEw0GgI; Thu, 20 Feb 2014 00:09:44 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 0E0962CC5D; Thu, 20 Feb 2014 00:09:44 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <036401cf1b53$2ec6cdd0$8c546970$@gmail.com>
Date: Wed, 19 Feb 2014 23:09:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <04EE3A4E-6895-43B3-93E6-DA9F155F579C@piuha.net>
References: <02db01cf1a6e$62eb8280$28c28780$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr> <033d01cf1b42$854c10e0$8fe432a0$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F473608DF@PUEXCB1B.nanterre.francetelecom.fr> <036401cf1b53$2ec6cdd0$8c546970$@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/oUjWGiolRye2fAHSrEH9GV2t130
Cc: gen-art@ietf.org, mohamed.boucadair@orange.com, ietf@ietf.org, draft-ietf-pcp-description-option.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-pcp-description-option-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 22:09:49 -0000

I am going through the documents for the upcoming IESG telechat. Roni - =
thank you very much for the review. Mohamed & others - I see that you =
have addressed the comments in -04, thank you for that!

Jari


From nobody Wed Feb 19 14:57:10 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 F12D31A02BE for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 14:57:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 HURreihkowOE for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 14:57:06 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D5AB01A02A1 for <gen-art@ietf.org>; Wed, 19 Feb 2014 14:57:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 32CE62CEAE; Thu, 20 Feb 2014 00:57:02 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPKNFaKuM8nY; Thu, 20 Feb 2014 00:57:01 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id C6A8F2CC5D; Thu, 20 Feb 2014 00:57:00 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAA=duU0ixoxsE14ssL+OZUpZB=LjhW=SWi9XLBEvbcO3n+vnFg@mail.gmail.com>
Date: Wed, 19 Feb 2014 23:57:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <798794E7-45CF-4F10-89FF-D2F5215C2883@piuha.net>
References: <CAA=duU3a66VKUcx3=jwimwRzNZJ4+EZCpKbS-dfUspJ+c+N8+Q@mail.gmail.com> <CF2A34E3.22FD2%ssalam@cisco.com> <CAA=duU0ixoxsE14ssL+OZUpZB=LjhW=SWi9XLBEvbcO3n+vnFg@mail.gmail.com>
To: Andrew G. Malis <agmalis@gmail.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Wu59iVZXfT1MyP02J4Zn7RKWdsE
Cc: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "Samer Salam \(ssalam\)" <ssalam@cisco.com>, "draft-ietf-pwe3-iccp.all@tools.ietf.org" <draft-ietf-pwe3-iccp.all@tools.ietf.org>, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-pwe3-iccp-13.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, 19 Feb 2014 22:57:09 -0000

Thanks your review, Dan. Thank you authors for addressing the concerns =
(in a new version, once it appears :-)

Jari

On Feb 19, 2014, at 10:33 PM, Andrew G. Malis <agmalis@gmail.com> wrote:

> Samer,
>=20
> Thanks for responding to Dan.
>=20
> The timing for a new revision is up to Stewart - don't take any action
> until you hear from him.
>=20
> Cheers,
> Andy
>=20
> On Wed, Feb 19, 2014 at 1:30 PM, Samer Salam (ssalam) =
<ssalam@cisco.com> wrote:
>> Hi Dan,
>>=20
>> Thank you for your review. Please find responses inline=8A
>>=20
>> Hi Andy,
>>=20
>> Please let us know when we can go ahead an update the draft to =
address the
>> review comments.
>>=20
>>=20
>> Regards,
>> Samer
>>=20
>> On 2014-02-19 6:31 AM, "Andrew G. Malis" <agmalis@gmail.com> wrote:
>>=20
>>> Dan,
>>>=20
>>> Thanks for the review (twice!).
>>>=20
>>> Authors,
>>>=20
>>> Could you please respond to Dan's review and comments?
>>>=20
>>> Thanks,
>>> Andy
>>>=20
>>>=20
>>> On Wed, Feb 19, 2014 at 3:23 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
>>>>=20
>>>>=20
>>>> Please wait for direction from your document shepherd or AD before
>>>> posting a
>>>> new version of the draft.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> Document: draft-ietf-pwe3-iccp-13.txt
>>>>=20
>>>> Reviewer: Dan Romascanu
>>>>=20
>>>> Review Date: 2/19/14
>>>>=20
>>>> IETF LC End Date: 2/11/14
>>>>=20
>>>> IESG Telechat date: 2/20/14
>>>>=20
>>>>=20
>>>>=20
>>>> Summary:
>>>>=20
>>>>=20
>>>>=20
>>>> Ready with issues. I did not see any answer from the editors or
>>>> shepherd to
>>>> the issues raised in the IETFLC Gen-ART review and there was no
>>>> revision of
>>>> the document since then. Although none of the issues raised seems =
to be
>>>> blocking, I believed that they should be considered and answered as
>>>> part of
>>>> the IETF Last Call Comments.
>>>>=20
>>>>=20
>>>>=20
>>>> This is a complex but well written document. It is ready, a number =
of
>>>> minor
>>>> issues need clarification and possibly editing. Some nits also may =
be
>>>> considered to fix
>>>>=20
>>>>=20
>>>>=20
>>>> Major issues:
>>>>=20
>>>>=20
>>>>=20
>>>> None
>>>>=20
>>>>=20
>>>>=20
>>>> Minor issues:
>>>>=20
>>>>=20
>>>>=20
>>>> 1.       The document (and the name of the protocol defined here) =
uses
>>>> the
>>>> notion of 'chassis'. However there is no definition or reference to =
a
>>>> definition that would clarify what a 'chassis' is.
>>=20
>> Good point, will add a definition to that effect.
>>=20
>>>>=20
>>>> 2.       In section 7.2.2.1 - I am not a fan of transferring
>>>> information in
>>>> text format like in the Disconnect Cause String - no =
interoperability
>>>> results if there no agreement on a finite set of causes. Anyway - =
should
>>>> this not be UTF-8 format?
>>=20
>> This is meant to relay information to a human user, and not intended =
to be
>> used to take any automated actions. Will clarify that it is UTF-8.
>>=20
>>>>=20
>>>> 3.       Similar question in Section 7.2.4 - why is Aggregator Name =
a
>>>> text?
>>>> Why not using AggregatorID as per IEEE 802.1AX?
>>=20
>> The AggregatorID is already part of the TLV. The name is to enhance =
human
>> usability, same reason as above.
>>=20
>>>>=20
>>>> 4.       In Section 7.2.5 - if Port Speed corresponds to the =
ifHighSpeed
>>>> object in the IF-MIB, should not also Port (interface) name =
correspond
>>>> to
>>>> ifName truncated to 20 characters whenever possible?
>>>>=20
>>=20
>> Agreed, will update accordingly.
>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> Nits/editorial comments:
>>>>=20
>>>>=20
>>>>=20
>>>> 1.       Some acronyms need expansion at the first occurrence - =
e.g.
>>>> POP, CO
>>=20
>> Will update the draft accordingly.
>>=20
>>>>=20
>>>> 2.       In section 3.3/i: PE nodes MAY be collocated or remote - =
this
>>>> MAY
>>>> needs not be capitalized.
>>=20
>> Will fix.
>>=20
>>>>=20
>>>> 3.       The first two lines in the diagram in page 16 are =
mis-aligned
>>=20
>> Will fix.
>>=20
>>>>=20
>>>> 4.       The diagrams in 7.1.1., 7.1.5   end at 16-bit boundary =
with the
>>>> last field defined for optional sub-TLVs. Is this intentional? Do =
they
>>>> suggest that the number of octets is always 4*n + 2? What happens =
else?
>>=20
>> No that was not intentional. Will add text to clarify that there are =
no
>> such assumptions.
>>=20
>>>>=20
>>>> 5.       In section 7.3.1:' -ii. PW ID TLV or generalized PW ID =
TLV' I
>>>> think
>>>> what is meant is actually ' -ii. One of PW ID TLV or generalized PW =
ID
>>>> TLV'
>>=20
>> Will update.
>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Feb 19 14:58:25 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 C5E641A0504 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 14:58:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 DX8vFlX1esqt for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 14:58:22 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C88461A04C1 for <gen-art@ietf.org>; Wed, 19 Feb 2014 14:58:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 286642CEAE; Thu, 20 Feb 2014 00:58:18 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aI8X-y99qwYX; Thu, 20 Feb 2014 00:58:16 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 98BC92CC5D; Thu, 20 Feb 2014 00:58:16 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA2E42AA10@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 19 Feb 2014 23:58:16 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2498177E-1F38-46EB-93F1-CEF02837C449@piuha.net>
References: <9904FB1B0159DA42B0B887B7FA8119CA2E42AA10@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/l7I2ucHqVP1H6kN--KeKTd3g-w4
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dane-registry-acronyms.all@tools.ietf.org" <draft-ietf-dane-registry-acronyms.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-dane-registry-acronyms-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 22:58:24 -0000

Thank you, all.

Jari

On Feb 19, 2014, at 9:12 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: draft-ietf-dane-registry-acronyms-03
> Reviewer: Dan Romascanu
> Review Date: 2/19/14
> IETF LC End Date:
> IESG Telechat date: 2/19/14
> =20
> Summary:
> =20
> Ready. All issues mentioned in the IETFLC Gen-ART review were =
addressed. Thank you.
> =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 Feb 19 15:00:59 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 0EE001A02A1 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:00:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 R33PAv91dNrY for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:00:55 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 83C9A1A02BE for <gen-art@ietf.org>; Wed, 19 Feb 2014 15:00:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D71A32CEAE; Thu, 20 Feb 2014 01:00:50 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 73h0Os6XsZEW; Thu, 20 Feb 2014 01:00:49 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 114172CC5D; Thu, 20 Feb 2014 01:00:49 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71202704EC4E5@MX15A.corp.emc.com>
Date: Thu, 20 Feb 2014 00:00:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <561D6A26-CD69-4C4B-B70B-8A58E9C5F545@piuha.net>
References: <8D3D17ACE214DC429325B2B98F3AE71202704EC4E5@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/QyqJiRUHcZ0cULYG_jYBzQAN5UY
Cc: dcridland@arcode.com, "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-qresync-rfc5162bis-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 23:00:57 -0000

David, thank you for the review. Alexey et al, thank you for the =
revisions.

Jari

On Jan 30, 2014, at 9:24 PM, "Black, David" <david.black@emc.com> wrote:

> The -10 version of this draft addresses all of the items noted in the
> Gen-ART review of the -09 version.  It's ready for publication.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Black, David
>> Sent: Sunday, January 26, 2014 9:07 PM
>> To: Alexey Melnikov (alexey.melnikov@isode.com); =
dcridland@arcode.com; General
>> Area Review Team (gen-art@ietf.org)
>> Cc: Black, David; Barry Leiba (barryleiba@computer.org); =
imapext@ietf.org;
>> ietf@ietf.org
>> Subject: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
>>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>=20
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document: draft-ietf-qresync-rfc5162bis-09
>> Reviewer: David L. Black
>> Review Date: January 26, 2014
>> IETF LC End Date: January 27, 2014
>>=20
>> Summary:
>> This draft is basically ready for publication, but has minor issues =
that
>> should be fixed before publication.
>>=20
>> This draft consolidates RFC 4551 (IMAP Conditional STORE) and RFC =
5162
>> (IMAP Quick Mailbox Resynchronization) into a single document and =
makes
>> a few minor updates.  It also updates the command line length
>> recommendation in RFC 2683 to support the longer command lines that
>> can occur with these extensions.
>>=20
>> As this is an update, I checked the diffs against RFC 4551 and RFC =
5162;
>> they look reasonable.  I found one minor issue that should be =
relatively
>> easy to address.
>>=20
>> Minor Issues:
>>=20
>> The command line length change in Section 4 applies to all IMAP =
commands,
>> and hence affects old servers, including those that don't implement =
either
>> of the extensions in this draft. That raises a backwards =
compatibility
>> concern - what happens when a new client sends a > 1000 character =
command
>> line to an old server that isn't expecting more than 1000 characters?
>>=20
>> One possibility would be to apply the larger length recommendation =
only
>> after the client determines that the server supports at least one of
>> these extensions.
>>=20
>> Nits/editorial comments:
>>=20
>> The update to RFC 2683 would be easier to find from the table of =
contents
>> if the title of Section 4 were changed to "Long Command Lines (Update =
to
>> RFC 2683)".
>>=20
>> idnits 2.13.01 got confused by the command line examples, and flagged =
a
>> downref:
>>=20
>>  ** Downref: Normative reference to an Informational RFC: RFC 2683
>>=20
>> That downref appears to be ok and intended, as noted in the =
shepherd's
>> writeup.
>>=20
>> Thanks,
>> --David
>> ----------------------------------------------------
>> David L. Black, Distinguished Engineer
>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> david.black@emc.com        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>=20


From nobody Wed Feb 19 15:03:18 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 46DBD1A02A1 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:03:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 FDXS5iZH3YWS for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:03:03 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 258761A0516 for <gen-art@ietf.org>; Wed, 19 Feb 2014 15:03:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id B92F52CEAE; Thu, 20 Feb 2014 01:02:56 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MuI1rDgb9IMT; Thu, 20 Feb 2014 01:02:55 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 537CA2CC5D; Thu, 20 Feb 2014 01:02:55 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A32D51903@eusaamb107.ericsson.se>
Date: Thu, 20 Feb 2014 00:02:55 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A05E54D-8985-4BB6-9335-D0D84F6F80B4@piuha.net>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32D51903@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/tu6vQa3SpjKjEy7ocYVT9QnoBFA
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org" <draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-l2vpn-vpls-mib-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 23:03:10 -0000

Thanks for your review, Meral. Authors, have you taken a look at the =
comment on Unsigned32?

Jari

On Feb 14, 2014, at 9:30 AM, Meral Shirazipour =
<meral.shirazipour@ericsson.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq.
> =20
> Please resolve these comments along with any other Last Call comments =
you may receive.
> =20
> Document: draft-ietf-l2vpn-vpls-mib-14
> Reviewer: Meral Shirazipour
> Review Date: 2013-02-14
> IETF LC End Date:  2014-02-14
> IESG Telechat date: 2014-02-20
> =20
> =20
> Summary:
> This draft is ready to be published as Standards Track RFC but I have =
some editorial comments .
> =20
> =20
> Nits/editorial comments:
> Suggestion: I noticed that Unsigned32 is used with 16 bit encoding. It =
could be good to mention it in the descriptions like other MIB documents =
do.
> Look for "Unsigned32 (1..65535)" in the draft.
> =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 Wed Feb 19 15:05:10 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 8BAD61A0529 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:05:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJ7Sm70WZjaV for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:05:00 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6003E1A0524 for <gen-art@ietf.org>; Wed, 19 Feb 2014 15:05:00 -0800 (PST)
X-AuditID: c618062d-b7f858e0000031c7-1d-5305389536f4
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 55.BF.12743.59835035; Thu, 20 Feb 2014 00:04:53 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0387.000; Wed, 19 Feb 2014 18:04:56 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-xrblock-rtcp-xr-synchronization.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-synchronization.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-synchronization-08
Thread-Index: Ac8txtugukUdyuEKTIWlyBu/446yNQ==
Date: Wed, 19 Feb 2014 23:04:55 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A32D6CEAD@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_ABCAA4EF18F17B4FB619EA93DEF7939A32D6CEADeusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUyuXRPrO5UC9Zgg2srVS3WfVrDZnH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSvj0NpJLAVLFCqeHPzL0sB4X6aLkZNDQsBE 4sDDlWwQtpjEhXvrgWwuDiGBI4wSC9s+sUI4yxklvi2ZzwhSxSZgIbH993OwhIjAOkaJY1cf A7VwcAgLREgc3Z8MUiMiECvRsWgFC4StJ3G18wUTiM0ioCoxYfUkdhCbV8BX4vLU2WA1jECb v59aA1bDLCAucevJfCaIiwQkluw5zwxhi0q8fPyPFcJWlNjXP50doj5f4vPqCVAzBSVOznzC MoFRaBaSUbOQlM1CUgYR15FYsPsTG4StLbFs4WtmGPvMgcdMyOILGNlXMXKUFqeW5aYbGWxi BMbDMQk23R2Me15aHmKU5mBREuf98tY5SEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAMj7+LL kZL920vf/Pl7w/j37SYtRdl9tvI75v/fkZRh8+eDumHL2nNPQtV3Mi5aN1/h98s/1sW3GP6n LPladlbe+OyE8/1rxBdHvFjKvL7x7x11QVWtO/8TXrD99135tIVz2o+kSV3dx1T3XdHiMpuY xCHO6ePw85zG57orru09YfM6LRyzQ7zOKLEUZyQaajEXFScCAAVwFb5VAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/BC0ePQao-LwnIFR1GUkkStL8fLk
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-xrblock-rtcp-xr-synchronization-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 19 Feb 2014 23:05:07 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D6CEADeusaamb107erics_
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-synchronization-08
Reviewer: Meral Shirazipour
Review Date: 2014-02-19
IETF LC End Date:  2014-02-04
IESG Telechat date: 2014-02-20

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



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

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

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

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D6CEADeusaamb107erics_--


From nobody Wed Feb 19 15:06:55 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 368D71A0535 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:06:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZUlMkXZh3swC for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:06:52 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id E69E71A02B9 for <gen-art@ietf.org>; Wed, 19 Feb 2014 15:06:51 -0800 (PST)
X-AuditID: c618062d-b7f858e0000031c7-76-530539043edb
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id B8.CF.12743.40935035; Thu, 20 Feb 2014 00:06:45 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0387.000; Wed, 19 Feb 2014 18:06:46 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org" <draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-l2vpn-vpls-mib-14
Thread-Index: Ac8txyM7coV6Lff1RBi+nYVvj33J1g==
Date: Wed, 19 Feb 2014 23:06:45 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A32D6CED4@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_ABCAA4EF18F17B4FB619EA93DEF7939A32D6CED4eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyuXRPoC6rJWuwweVWAYsT+5uYLK6++szi wOSxZMlPJo8vlz+zBTBFcdmkpOZklqUW6dslcGWs+7KUteCvRsWxp/wNjF0qXYycHBICJhIz V3QwQdhiEhfurWfrYuTiEBI4wiixaN0PdghnOaPE+i0bWUGq2AQsJLb/fs4KkhAR6GGUWPWv n6WLkYNDWMBV4tUyGZAaEQEviUl/bzJB2HoSj/+cYASxWQRUJaaebweL8wr4Sjz6948ZxGYE 2vz91BqwOLOAuMStJ/OhLhKQWLLnPDOELSrx8vE/VghbUWJf/3R2iPp8iStn7rJDzBSUODnz CcsERqFZSEbNQlI2C0kZRFxHYsHuT2wQtrbEsoWvmWHsMwceMyGLL2BkX8XIUVqcWpabbmSw iREYDcck2HR3MO55aXmIUZqDRUmc98tb5yAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjCFv pmqu27wyqbXDLF85WazpD1d0zJs1bOurKoTnyclEvJlVrqC6JefApHo3y9X/5uXsvb506vWS 7CXLfyndD1G6LGbYn1S9V7XUMWWarEryjuDXf37aXJpe7LQz2bjhwom7p4QY959a9VPpXMaH lSVbuZfP27R670qG2ZUhD6NbHTcdvnwwuUuJpTgj0VCLuag4EQBQAuwaVAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/vbaQlrm3QLFx-72XMdKc49s73EE
Subject: [Gen-art] Gen-ART Telechat Call review of draft-ietf-l2vpn-vpls-mib-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 23:06:54 -0000

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D6CED4eusaamb107erics_
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-l2vpn-vpls-mib-14
Reviewer: Meral Shirazipour
Review Date: 2013-02-14
IETF LC End Date:  2014-02-14
IESG Telechat date: 2014-02-20

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


Nits/editorial comments:
It was noticed that Unsigned32 is used with 16 bit encoding. It would good =
to mention it in the descriptions like other MIB documents do.
Look for "Unsigned32 (1..65535) in the draft :
-Offline discussion with one of the authors, a suggestion could be "the num=
ber of VPLS Edge devices(VEid) is limited to 65535 in any implementation"



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

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at &lt;
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt; .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please wait for direction from your document shepher=
d or AD before posting a new version of the draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FR-CA">Document: draft-ietf-l2vpn-vpls=
-mib-14<o:p></o:p></span></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-02-14<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date:&nbsp; 2014-02-14<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: 2014-02-20<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is ready to be published as Standards Tra=
ck RFC but I have some editorial comments .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">It was noticed that Unsigned32 is used with 16 bit e=
ncoding. It would good to mention it in the descriptions like other MIB doc=
uments do.<o:p></o:p></p>
<p class=3D"MsoNormal">Look for &quot;Unsigned32 (1..65535) in the draft :<=
o:p></o:p></p>
<p class=3D"MsoNormal">-Offline discussion with one of the authors, a sugge=
stion could be &quot;the number of VPLS Edge devices(VEid) is limited to 65=
535 in any implementation&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D6CED4eusaamb107erics_--


From nobody Wed Feb 19 15:09:20 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 680971A0524 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:09:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 QiGtQsGe5n2Y for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:09:16 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C76DA1A04D2 for <gen-art@ietf.org>; Wed, 19 Feb 2014 15:09:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 241A62CEB2; Thu, 20 Feb 2014 01:09:12 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hySFNbqUEJsj; Thu, 20 Feb 2014 01:09:09 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id ABA972CC5D; Thu, 20 Feb 2014 01:09:09 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201402171512.s1HFCGsc027226@givry.fdupont.fr>
Date: Thu, 20 Feb 2014 00:09:09 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <42DF65AD-76DE-4AE2-974D-A7A022951A5E@piuha.net>
References: <201402171512.s1HFCGsc027226@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/hK32LfcSEMkFl6ALl-vLiAFT5po
Cc: gen-art@ietf.org, draft-ietf-l3vpn-mldp-vrf-in-band-signaling.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-l3vpn-mldp-vrf-in-band-signaling-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: Wed, 19 Feb 2014 23:09:18 -0000

Thanks for your review, Francis.

Jari

On Feb 17, 2014, at 4:12 PM, Francis Dupont <Francis.Dupont@fdupont.fr> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-l3vpn-mldp-vrf-in-band-signaling-03.txt
> Reviewer: Francis Dupont
> Review Date: 20140211
> IETF LC End Date: 20140212
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
> - the number of authors is greater than the (soft) limit
>=20
> - 1 page 5: too many 'o' in 'co-oordination'
>=20
> - 1.2 pages 5 & 6: IMHO you should describe more terms in the =
Terminology
>  section, e.g., UMH, RPA and even RD (as VRF is already in it)
>=20
> Regards=20
>=20
> Francis.Dupont@fdupont.fr
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Feb 19 15:16:14 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B0C31A0296; Wed, 19 Feb 2014 15:16:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 fT20pNH1DnbC; Wed, 19 Feb 2014 15:16:06 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9692F1A0289; Wed, 19 Feb 2014 15:16:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id EA28C2CEB2; Thu, 20 Feb 2014 01:16:01 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fSE1oym6jsJF; Thu, 20 Feb 2014 01:16:00 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 4BDD92CC5D; Thu, 20 Feb 2014 01:16:00 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52FE6010.5000107@si6networks.com>
Date: Thu, 20 Feb 2014 00:16:00 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <0AEED795-7A58-482B-A06C-EF6560523B4B@piuha.net>
References: <E0403989-8A34-4E3D-8F53-2F4338967A36@vigilsec.com> <52FE6010.5000107@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/RYRD3NIPX2PlAjqG4JdbdOR5EtA
Cc: draft-ietf-opsec-vpn-leakages.all@tools.ietf.org, IETF Gen-ART <gen-art@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-opsec-vpn-leakages-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 23:16:08 -0000

Thanks for your review, Russ. Is there a new version coming up?

Jari

On Feb 14, 2014, at 7:27 PM, Fernando Gont <fgont@si6networks.com> wrote:

> Hi, Russ,
> 
> Thanks so much for your feedback! Please find my comments in-line...
> 
> On 02/14/2014 02:06 PM, Russ Housley wrote:
>> 
>> Summary:  The document is almost ready for publication as a
>> informational RFC.  I raise minor concerns that should be resolved
>> before IESG evaluation.
>> 
>> Major Concern:
>> 
>> In my review of -02, I said:
>>> 
>>> This document is about encrypted tunnels, and I am asking for this to
>>> be stated very early in the document.  Sadly, the IETF uses VPN to mean
>>> two very different things, please tell the reader which one is being
>>> discussed in the abstract and the introduction of the document.  IPsec
>>> and L3VPN demonstrate the two very different meanings for VPN, and
>>> "VPN leakage" has meaning in both of them.
>> 
>> I think it could be much more clear from the very beginning.
>> To this end I propose some alternate Abstract text:
>> 
>>   The subtle way in which the IPv6 and IPv4 protocols co-exist in
>>   typical networks, together with the lack of proper IPv6 support in
>>   popular Virtual Private Network (VPN) products, may inadvertently
>>   result in VPN traffic leaks.  That is, traffic meant to be
>>   transferred over an encrypted and integrity protected VPN connection
>>   may instead be transferred in the clear.  This document discusses
>>   some scenarios in which such VPN leakages may occur, either as a
>>   side effect of enabling IPv6 on a local network, or as a result of a
>>   deliberate act by a local attacker.  Additionally, this document
>>   offers possible mitigations for this issue.
> 
> Will do. Thanks!
> 
> 
> 
>> Personal Observation:
>> 
>> I do not find this document very helpful.  It can be summarized as:
>> 
>>   If IPv6 is not supported in your VPN software, then disable IPv6
>>   support in all network interfaces before you try to use it.
>> 
>> I do not know why the OPSEC WG thinks that this message is worthy of
>> an RFC.
> 
> While I cannot speak for the opsec wg myself, my understanding is that
> this document serves at these goals:
> 
> * Raising awareness among VPN users
> 
> * Suggesting workarounds to VPN users
> 
> * Raising awareness among vendors -- some of them have implemented
> patches in response to this document.
> 
> * Briefly describing some tricky issues that might bite implementations.
> 
> Thanks!
> 
> Best regards,
> -- 
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> 
> 
> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Feb 19 15:19:20 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 509891A02E5 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 HwyFTNxpJdD3 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:19:16 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id BEEAD1A0289 for <gen-art@ietf.org>; Wed, 19 Feb 2014 15:19:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1CA882CEB2; Thu, 20 Feb 2014 01:19:12 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vGCEtOGTY1Yl; Thu, 20 Feb 2014 01:19:11 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 388F32CC5D; Thu, 20 Feb 2014 01:19:11 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <029301cef404$506bed60$f143c820$@gmail.com>
Date: Thu, 20 Feb 2014 00:19:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <88FA7F37-C3F3-4F7B-9430-AD9B76A2EA11@piuha.net>
References: <029301cef404$506bed60$f143c820$@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/HD1fojS7qrkn5YoD-hB8j4S4_Ek
Cc: gen-art@ietf.org, draft-allen-dispatch-imei-urn-as-instanceid.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-allen-dispatch-imei-urn-as-instanceid-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: Wed, 19 Feb 2014 23:19:18 -0000

Thanks for your review, Roni.

Jari

On Dec 8, 2013, at 11:57 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-allen-dispatch-imei-urn-as-instanceid-12
> Reviewer: Roni Even
> Review Date:2013=9612-8
> IETF LC End Date: 2013-12=9623
> 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
> =20
>=20
> =20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Feb 19 15:22:00 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE38D1A04F0 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:21:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 jpexEK7vYiCL for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:21:56 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 637391A0409 for <gen-art@ietf.org>; Wed, 19 Feb 2014 15:21:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id B6F822CEB2; Thu, 20 Feb 2014 01:21:52 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9AoBc-PiybM; Thu, 20 Feb 2014 01:21:50 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7FD3D2CC5D; Thu, 20 Feb 2014 01:21:50 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52FD3E67.3000404@joelhalpern.com>
Date: Thu, 20 Feb 2014 00:21:50 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <4E60E509-65A7-4CD3-915C-ABBD92430B19@piuha.net>
References: <52EBD16D.706@nostrum.com> <52EBFDBF.70505@joelhalpern.com> <52FD3E67.3000404@joelhalpern.com>
To: Joel M. Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/lgKyU_nB88Dc9QrPeqb2HkEG2KY
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] Review: draft-ietf-mpls-forwarding-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 19 Feb 2014 23:21:58 -0000

Thanks for your review, Joel :-)

On Feb 13, 2014, at 10:51 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:

> This document is still ready for publication as an Informational RFC.
> Yours,
> Joel
> 
> On 1/31/14, 2:47 PM, Joel M. Halpern 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-forwarding-06
>> Reviewer: Joel M. Halpern
>> Review Date: 31-January-2014
>> IETF LC End Date: 12-Feb-2014
>> IESG Telechat date: N/A
>> 
>> Summary: This document is ready for publication as an Informational RFC.
>> 
>> Major issues: N/A
>> 
>> Minor issues: N/A
>> 
>> Nits/editorial comments: N/A
>> _______________________________________________
>> 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 Wed Feb 19 15:26:12 2014
Return-Path: <fgont@si6networks.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 61A8A1A040A; Wed, 19 Feb 2014 15:26:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 yeUVLIa15EYd; Wed, 19 Feb 2014 15:26:03 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 1449F1A02BE; Wed, 19 Feb 2014 15:26:03 -0800 (PST)
Received: from 75-138-17-190.fibertel.com.ar ([190.17.138.75] helo=[192.168.3.103]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.82) (envelope-from <fgont@si6networks.com>) id 1WGGWR-00085v-Ov; Thu, 20 Feb 2014 00:25:48 +0100
Message-ID: <53053D73.7070600@si6networks.com>
Date: Wed, 19 Feb 2014 20:25:39 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <E0403989-8A34-4E3D-8F53-2F4338967A36@vigilsec.com> <52FE6010.5000107@si6networks.com> <0AEED795-7A58-482B-A06C-EF6560523B4B@piuha.net>
In-Reply-To: <0AEED795-7A58-482B-A06C-EF6560523B4B@piuha.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/xKdDU75PzkepHGVw76tOiGjR6FE
Cc: draft-ietf-opsec-vpn-leakages.all@tools.ietf.org, IETF Gen-ART <gen-art@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-opsec-vpn-leakages-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 23:26:06 -0000

On 02/19/2014 08:16 PM, Jari Arkko wrote:
> Thanks for your review, Russ. Is there a new version coming up?

Yes. I'll be posting it tomorrow as the latest.

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Feb 19 15:35:33 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 9FC511A0535 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:35:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zbMBbf0SRXWi for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:35:28 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id F30101A052E for <gen-art@ietf.org>; Wed, 19 Feb 2014 15:35:09 -0800 (PST)
X-AuditID: c618062d-b7f858e0000031c7-b4-53053fa68471
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id D7.C0.12743.6AF35035; Thu, 20 Feb 2014 00:35:02 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0387.000; Wed, 19 Feb 2014 18:35:05 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: Agrahara Kiran Koushik <kkoushik@cisco.com>
Thread-Topic: Gen-ART Telechat Call review of draft-ietf-l2vpn-vpls-mib-14
Thread-Index: Ac8txyM7coV6Lff1RBi+nYVvj33J1gALdECAAAp1OsA=
Date: Wed, 19 Feb 2014 23:35:04 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A32D6D0A2@eusaamb107.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32D6CED4@eusaamb107.ericsson.se> <0F834B8C-89A9-41B7-8B8D-4B0B728281B9@cisco.com>
In-Reply-To: <0F834B8C-89A9-41B7-8B8D-4B0B728281B9@cisco.com>
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_ABCAA4EF18F17B4FB619EA93DEF7939A32D6D0A2eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrILMWRmVeSWpSXmKPExsUyuXRPgu4ye9Zgg6mXJC1O7G9isrj66jOL Rcv0mYwOzB5Tfm9k9Viy5CeTx5fLn9kCmKO4bFJSczLLUov07RK4MhZfamcp2Jxe8fvwRrYG xs6YLkZODgkBE4kjN+YxQthiEhfurWfrYuTiEBI4wijRc76FFcJZzihxo+sUWBWbgIXE9t/P WUFsEQF9idtTZoDZzAI9jBKtKwVAbGEBT4kvFyexQdR4SUz6e5MJwraSmDT7FjOIzSKgKtF9 9g87iM0r4Cuxr+sv1OYGRolX736wgCQ4BWwlVn47D7aAEei876fWMEEsE5e49WQ+E8TZAhJL 9pxnhrBFJV4+/scKYStK7Oufzg5Rny8xbecbqGWCEidnPmGZwCg6C8moWUjKZiEpg4jrSCzY /YkNwtaWWLbwNTOMfebAYyZk8QWM7KsYOUqLU8ty040MNjECo+2YBJvuDsY9Ly0PMUpzsCiJ 83556xwkJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgZFNtWThtZytzRe0KsXXrft0wmzng7c3 Uy89d02TNugNCzw0/e6sH1fuWykdOznpBx+HTtDs4r5vct3/vXduVZqwO/PbrSj+emFRESaL TReuP7u5nvHtjyfFziF1PLvvzpnL90LlQpRm6ksWnbm7uY15OpbLBtQc2nbF9tAT/bNSj/az N+qz8tkqsRRnJBpqMRcVJwIAbyyFi4QCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/VJcYWBaWeKrZtGR6LWdWzZA6qLk
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org" <draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Call review of draft-ietf-l2vpn-vpls-mib-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 23:35:31 -0000

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

Hi,
  Thank you again Kiran, it works for me.

Best,
Meral

From: Agrahara Kiran Koushik [mailto:kkoushik@cisco.com]
Sent: Wednesday, February 19, 2014 3:34 PM
To: Meral Shirazipour
Cc: draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org; gen-art@ietf.org
Subject: Re: Gen-ART Telechat Call review of draft-ietf-l2vpn-vpls-mib-14

Hi
Here is the text we are planning to add in the DESCRIPTION clause for objec=
ts
which refer to VE ID and have a upper limit of 65535.

"
                The VE ID takes 2 octets in VPLS BGP NLRI according
                 to RFC 4761. Hence we have limited the the range of
                 this object to 65535.
"

Let me know if this is acceptable?

Thanks
Kiran

On Feb 19, 2014, at 5:06 PM, Meral Shirazipour <meral.shirazipour@ericsson.=
com<mailto:meral.shirazipour@ericsson.com>> wrote:


I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ 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-l2vpn-vpls-mib-14
Reviewer: Meral Shirazipour
Review Date: 2013-02-14
IETF LC End Date:  2014-02-14
IESG Telechat date: 2014-02-20

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


Nits/editorial comments:
It was noticed that Unsigned32 is used with 16 bit encoding. It would good =
to mention it in the descriptions like other MIB documents do.
Look for "Unsigned32 (1..65535) in the draft :
-Offline discussion with one of the authors, a suggestion could be "the num=
ber of VPLS Edge devices(VEid) is limited to 65535 in any implementation"



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


--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D6D0A2eusaamb107erics_
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)">
<base href=3D"x-msg://3141/"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp; Thank you again Ki=
ran, it works for me.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best,<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Meral<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Agrahara=
 Kiran Koushik [mailto:kkoushik@cisco.com]
<br>
<b>Sent:</b> Wednesday, February 19, 2014 3:34 PM<br>
<b>To:</b> Meral Shirazipour<br>
<b>Cc:</b> draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org; gen-art@ietf.org<b=
r>
<b>Subject:</b> Re: Gen-ART Telechat Call review of draft-ietf-l2vpn-vpls-m=
ib-14<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Hi<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Here is the text we are planning to add in the DESCR=
IPTION clause for objects<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">which refer to VE ID and have a upper limit of 65535=
.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp;The VE ID takes 2 octets in VPLS BGP NLRI according<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp;to RFC 4761. Hence we have limited the the range of<o:p></o:p></p=
>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp;this object to 65535.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Let me know if this is acceptable?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Kiran<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">On Feb 19, 2014, at 5:06 PM, Meral Shirazipour &lt;<=
a href=3D"mailto:meral.shirazipour@ericsson.com">meral.shirazipour@ericsson=
.com</a>&gt; wrote:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">I am the assigned Gen-ART reviewer for =
this draft. For background on Gen-ART, please see the FAQ at &lt;<span clas=
s=3D"apple-converted-space">&nbsp;</span><a href=3D"http://wiki.tools.ietf.=
org/area/gen/trac/wiki/GenArtfaq"><span style=3D"color:purple">http://wiki.=
tools.ietf.org/area/gen/trac/wiki/GenArtfaq</span></a>&gt;
 .<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Please wait for direction from your doc=
ument shepherd or AD before posting a new version of the draft.<o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"FR-CA" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Document: draft-ietf-l2v=
pn-vpls-mib-14</span><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Reviewer: Meral Shirazipour<o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Review Date: 2013-02-14<o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">IETF LC End Date:&nbsp; 2014-02-14<o:p>=
</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">IESG Telechat date: 2014-02-20<o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Summary:<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">This draft is ready to be published as =
Standards Track RFC but I have some editorial comments .<o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Nits/editorial comments:<o:p></o:p></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">It was noticed that Unsigned32 is used =
with 16 bit encoding. It would good to mention it in the descriptions like =
other MIB documents do.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Look for &quot;Unsigned32 (1..65535) in=
 the draft :<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">-Offline discussion with one of the aut=
hors, a suggestion could be &quot;the number of VPLS Edge devices(VEid) is =
limited to 65535 in any implementation&quot;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Best Regards,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Meral<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">---<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Meral Shirazipour<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Ericsson<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Research<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><a href=3D"http://www.ericsson.com"><sp=
an style=3D"color:purple">www.ericsson.com</span></a><o:p></o:p></span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D6D0A2eusaamb107erics_--


From nobody Wed Feb 19 15:43:16 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 182931A0538; Wed, 19 Feb 2014 15:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 Rs3Km9HxIYA0; Wed, 19 Feb 2014 15:43:12 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4F74F1A0529; Wed, 19 Feb 2014 15:43:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A45092CEB2; Thu, 20 Feb 2014 01:43:08 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7iBZZBbFT3Bu; Thu, 20 Feb 2014 01:43:08 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 01DB42CC5D; Thu, 20 Feb 2014 01:43:07 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <53053D73.7070600@si6networks.com>
Date: Thu, 20 Feb 2014 00:43:07 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <6D55190B-7EFA-417D-9A19-A99E6887F4BA@piuha.net>
References: <E0403989-8A34-4E3D-8F53-2F4338967A36@vigilsec.com> <52FE6010.5000107@si6networks.com> <0AEED795-7A58-482B-A06C-EF6560523B4B@piuha.net> <53053D73.7070600@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/rtTRz2ffC9xwMcISotodYUodyEA
Cc: draft-ietf-opsec-vpn-leakages.all@tools.ietf.org, IETF Gen-ART <gen-art@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-opsec-vpn-leakages-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 23:43:14 -0000

Thank you, Fernando.

Jari

On Feb 20, 2014, at 12:25 AM, Fernando Gont <fgont@si6networks.com> wrote:

> On 02/19/2014 08:16 PM, Jari Arkko wrote:
>> Thanks for your review, Russ. Is there a new version coming up?
> 
> Yes. I'll be posting it tomorrow as the latest.
> 
> Thanks!
> 
> Cheers,
> -- 
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> 
> 
> 
> 


From nobody Wed Feb 19 16:20:28 2014
Return-Path: <kkoushik@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 444AD1A0535 for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:34:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.048
X-Spam-Level: 
X-Spam-Status: No, score=-15.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, 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 3dtiOUpMilZM for <gen-art@ietfa.amsl.com>; Wed, 19 Feb 2014 15:34:07 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id ED7521A0545 for <gen-art@ietf.org>; Wed, 19 Feb 2014 15:33:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8235; q=dns/txt; s=iport; t=1392852832; x=1394062432; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=7yLxJci5YGw+VTWmnaQ7tsyu99ytdFDJrMe+xtZn7uM=; b=d1ZA6BFniau0vRvvN2Svvn8eVJjCHSmry7cN0qDKsHs2LhPrxsbAngua qA/hnycio+G3qRDJWTUk6TOUI7nU+8G56sUNePzFAqEq3sY2dCDeI8qIZ aBuXRTEVl9HiwBiY7L5eA8WX4kb88HmuLYxC0bCWQLeyOZTaKnGdFbVec 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AssFAK8+BVOtJV2Z/2dsb2JhbABYgkJEOLgIiFaBFxZ0giUBAQEDAUkwBQsLFDJXBhOHfQgNzkAXjHKBGgFGEQeDJIEUBIlIjmiBMoUVi12DTB2BLAEf
X-IronPort-AV: E=Sophos;i="4.97,508,1389744000";  d="scan'208,217";a="305184698"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 19 Feb 2014 23:33:51 +0000
Received: from [10.152.13.159] ([10.152.13.159]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s1JNXpGk010629 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 19 Feb 2014 23:33:51 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_6275AA08-1495-4F1D-8B06-4B4E194FA23E"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Agrahara Kiran Koushik <kkoushik@cisco.com>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A32D6CED4@eusaamb107.ericsson.se>
Date: Wed, 19 Feb 2014 17:33:51 -0600
Message-Id: <0F834B8C-89A9-41B7-8B8D-4B0B728281B9@cisco.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32D6CED4@eusaamb107.ericsson.se>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/bfyr3RHlVa51eVADNgT5sT9CY-Y
X-Mailman-Approved-At: Wed, 19 Feb 2014 16:20:26 -0800
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org" <draft-ietf-l2vpn-vpls-mib.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Call review of draft-ietf-l2vpn-vpls-mib-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 23:34:10 -0000

--Apple-Mail=_6275AA08-1495-4F1D-8B06-4B4E194FA23E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi
Here is the text we are planning to add in the DESCRIPTION clause for =
objects
which refer to VE ID and have a upper limit of 65535.

"=20
                The VE ID takes 2 octets in VPLS BGP NLRI according
                 to RFC 4761. Hence we have limited the the range of
                 this object to 65535.
"

Let me know if this is acceptable?

Thanks
Kiran

On Feb 19, 2014, at 5:06 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-l2vpn-vpls-mib-14
> Reviewer: Meral Shirazipour
> Review Date: 2013-02-14
> IETF LC End Date:  2014-02-14
> IESG Telechat date: 2014-02-20
> =20
> Summary:
> This draft is ready to be published as Standards Track RFC but I have =
some editorial comments .
> =20
> =20
> Nits/editorial comments:
> It was noticed that Unsigned32 is used with 16 bit encoding. It would =
good to mention it in the descriptions like other MIB documents do.
> Look for "Unsigned32 (1..65535) in the draft :
> -Offline discussion with one of the authors, a suggestion could be =
"the number of VPLS Edge devices(VEid) is limited to 65535 in any =
implementation"
> =20
> =20
> =20
> Best Regards,
> Meral
> ---
> Meral Shirazipour
> Ericsson
> Research
> www.ericsson.com


--Apple-Mail=_6275AA08-1495-4F1D-8B06-4B4E194FA23E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><base href=3D"x-msg://3141/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>Hi</div><div>Here is the =
text we are planning to add in the DESCRIPTION clause for =
objects</div><div>which refer to VE ID and have a upper limit of =
65535.</div><div><br></div><div>"&nbsp;</div><div>&nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;The VE ID takes 2 octets in =
VPLS BGP NLRI according</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;to RFC 4761. Hence we have limited the the =
range of</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;this object to =
65535.</div><div>"</div><div><br></div><div>Let me know if this is =
acceptable?</div><div><br></div><div>Thanks</div><div>Kiran</div><div><br>=
</div><div><div>On Feb 19, 2014, at 5:06 PM, Meral Shirazipour &lt;<a =
href=3D"mailto:meral.shirazipour@ericsson.com">meral.shirazipour@ericsson.=
com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"font-family: =
Helvetica; font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div =
class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">I am the assigned Gen-ART reviewer for this =
draft. For background on Gen-ART, please see the FAQ at &lt;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
style=3D"color: purple; text-decoration: underline; =
">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt; =
.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">Please wait for direction from your document =
shepherd or AD before posting a new version of the =
draft.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"FR-CA">Document: =
draft-ietf-l2vpn-vpls-mib-14<o:p></o:p></span></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
">Reviewer: Meral Shirazipour<o:p></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
">Review Date: 2013-02-14<o:p></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">IETF LC =
End Date:&nbsp; 2014-02-14<o:p></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">IESG =
Telechat date: 2014-02-20<o:p></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
">Summary:<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">This draft is ready =
to be published as Standards Track RFC but I have some editorial =
comments .<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">Nits/editorial =
comments:<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">It was noticed that =
Unsigned32 is used with 16 bit encoding. It would good to mention it in =
the descriptions like other MIB documents do.<o:p></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">Look for "Unsigned32 (1..65535) in the draft =
:<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; ">-Offline discussion with one =
of the authors, a suggestion could be "the number of VPLS Edge =
devices(VEid) is limited to 65535 in any =
implementation"<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">Best =
Regards,<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
">Meral<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
">---<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; ">Meral =
Shirazipour<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
">Ericsson<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
">Research<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><a =
href=3D"http://www.ericsson.com" style=3D"color: purple; =
text-decoration: underline; =
">www.ericsson.com</a><o:p></o:p></div></div></div></blockquote></div><br>=
</body></html>=

--Apple-Mail=_6275AA08-1495-4F1D-8B06-4B4E194FA23E--


From nobody Thu Feb 20 01:57:23 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 BAFFA1A0086 for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 01:57:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] 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 CmqVUUZAcRiE for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 01:57:17 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id BB79E1A0063 for <gen-art@ietf.org>; Thu, 20 Feb 2014 01:57:17 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiYIAATRBVOHCzIm/2dsb2JhbABZgmUhOFenfpgKgQ8WdIIlAQEBAQMSZwwEAgEIDQQDAQEBAQodByERFAkIAgQBCQQFCBMHh08DEQEMokykAw2HcBeMTyOBQTEHBoMegRQElkMBgx6FPYVvhUaDLYIq
X-IronPort-AV: E=Sophos;i="4.97,511,1389762000"; d="scan'208";a="50179506"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 20 Feb 2014 04:57:13 -0500
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; 20 Feb 2014 04:44:14 -0500
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; Thu, 20 Feb 2014 10:57:11 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Samer Salam (ssalam)" <ssalam@cisco.com>, "Andrew G. Malis" <agmalis@gmail.com>
Thread-Topic: Gen-ART telechat review of draft-ietf-pwe3-iccp-13.txt
Thread-Index: AQHPLX9Is0UuULJl+k+6bducB5ycz5q9Oh8AgACuj1A=
Date: Thu, 20 Feb 2014 09:57:11 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E42B6E1@AZ-FFEXMB04.global.avaya.com>
References: <CAA=duU3a66VKUcx3=jwimwRzNZJ4+EZCpKbS-dfUspJ+c+N8+Q@mail.gmail.com> <CF2A34E3.22FD2%ssalam@cisco.com>
In-Reply-To: <CF2A34E3.22FD2%ssalam@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/tjRAwYjtfSMtJnyY4vTNB-w2QXk
Cc: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pwe3-iccp.all@tools.ietf.org" <draft-ietf-pwe3-iccp.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART telechat review of draft-ietf-pwe3-iccp-13.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, 20 Feb 2014 09:57:21 -0000

Hi Samer,

Thank you for your response and for addressing my comments. I am fine with =
the proposed solutions. At this point in the process the change control of =
the document is with the shepherding AD, so please wait for his instruction=
s about when to update the document.=20

Regards,

Dan


> -----Original Message-----
> From: Samer Salam (ssalam) [mailto:ssalam@cisco.com]
> Sent: Wednesday, February 19, 2014 8:30 PM
> To: Andrew G. Malis; Romascanu, Dan (Dan)
> Cc: gen-art@ietf.org; draft-ietf-pwe3-iccp.all@tools.ietf.org; BOCCI Matt=
hew
> Subject: Re: Gen-ART telechat review of draft-ietf-pwe3-iccp-13.txt
>=20
> Hi Dan,
>=20
> Thank you for your review. Please find responses inline=A9
>=20
> Hi Andy,
>=20
> Please let us know when we can go ahead an update the draft to address th=
e
> review comments.
>=20
>=20
> Regards,
> Samer
>=20
> On 2014-02-19 6:31 AM, "Andrew G. Malis" <agmalis@gmail.com> wrote:
>=20
> >Dan,
> >
> >Thanks for the review (twice!).
> >
> >Authors,
> >
> >Could you please respond to Dan's review and comments?
> >
> >Thanks,
> >Andy
> >
> >
> >On Wed, Feb 19, 2014 at 3:23 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>.
> >>
> >>
> >>
> >> Please wait for direction from your document shepherd or AD before
> >>posting a  new version of the draft.
> >>
> >>
> >>
> >>
> >>
> >> Document: draft-ietf-pwe3-iccp-13.txt
> >>
> >> Reviewer: Dan Romascanu
> >>
> >> Review Date: 2/19/14
> >>
> >> IETF LC End Date: 2/11/14
> >>
> >> IESG Telechat date: 2/20/14
> >>
> >>
> >>
> >> Summary:
> >>
> >>
> >>
> >> Ready with issues. I did not see any answer from the editors or
> >>shepherd to  the issues raised in the IETFLC Gen-ART review and there
> >>was no revision of  the document since then. Although none of the
> >>issues raised seems to be  blocking, I believed that they should be
> >>considered and answered as part of  the IETF Last Call Comments.
> >>
> >>
> >>
> >> This is a complex but well written document. It is ready, a number of
> >>minor  issues need clarification and possibly editing. Some nits also
> >>may be  considered to fix
> >>
> >>
> >>
> >> Major issues:
> >>
> >>
> >>
> >> None
> >>
> >>
> >>
> >> Minor issues:
> >>
> >>
> >>
> >> 1.       The document (and the name of the protocol defined here) uses
> >>the
> >> notion of 'chassis'. However there is no definition or reference to a
> >>definition that would clarify what a 'chassis' is.
>=20
> Good point, will add a definition to that effect.
>=20
> >>
> >> 2.       In section 7.2.2.1 - I am not a fan of transferring
> >>information in
> >> text format like in the Disconnect Cause String - no interoperability
> >>results if there no agreement on a finite set of causes. Anyway -
> >>should  this not be UTF-8 format?
>=20
> This is meant to relay information to a human user, and not intended to b=
e
> used to take any automated actions. Will clarify that it is UTF-8.
>=20
> >>
> >> 3.       Similar question in Section 7.2.4 - why is Aggregator Name a
> >>text?
> >> Why not using AggregatorID as per IEEE 802.1AX?
>=20
> The AggregatorID is already part of the TLV. The name is to enhance human
> usability, same reason as above.
>=20
> >>
> >> 4.       In Section 7.2.5 - if Port Speed corresponds to the ifHighSpe=
ed
> >> object in the IF-MIB, should not also Port (interface) name
> >>correspond to  ifName truncated to 20 characters whenever possible?
> >>
>=20
> Agreed, will update accordingly.
>=20
> >>
> >>
> >>
> >>
> >> Nits/editorial comments:
> >>
> >>
> >>
> >> 1.       Some acronyms need expansion at the first occurrence - e.g.
> >>POP, CO
>=20
> Will update the draft accordingly.
>=20
> >>
> >> 2.       In section 3.3/i: PE nodes MAY be collocated or remote - this
> >>MAY
> >> needs not be capitalized.
>=20
> Will fix.
>=20
> >>
> >> 3.       The first two lines in the diagram in page 16 are mis-aligned
>=20
> Will fix.
>=20
> >>
> >> 4.       The diagrams in 7.1.1., 7.1.5   end at 16-bit boundary with t=
he
> >> last field defined for optional sub-TLVs. Is this intentional? Do they
> >> suggest that the number of octets is always 4*n + 2? What happens else=
?
>=20
> No that was not intentional. Will add text to clarify that there are no
> such assumptions.
>=20
> >>
> >> 5.       In section 7.3.1:' -ii. PW ID TLV or generalized PW ID TLV' I
> >>think
> >> what is meant is actually ' -ii. One of PW ID TLV or generalized PW ID
> >>TLV'
>=20
> Will update.
>=20
> >>
> >>
> >>
> >>


From nobody Thu Feb 20 05:23: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 3598C1A0155 for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 05:23:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 R6pajpOpMQSG for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 05:23:10 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4B7AC1A0056 for <gen-art@ietf.org>; Thu, 20 Feb 2014 05:23:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6F40C2CCC1; Thu, 20 Feb 2014 15:22:48 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NB0DsyrDGXqd; Thu, 20 Feb 2014 15:22:47 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 11ED42CC5D; Thu, 20 Feb 2014 15:22:47 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A32D6CEAD@eusaamb107.ericsson.se>
Date: Thu, 20 Feb 2014 14:22:46 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E0F6F7C-B0A3-4EC3-8EF6-77AA7F5ACD4B@piuha.net>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A32D6CEAD@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/Q5XWEB5oe6HOow974mfdiRbF0-M
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-xrblock-rtcp-xr-synchronization.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-synchronization.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART Telechat Call review of draft-ietf-xrblock-rtcp-xr-synchronization-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 20 Feb 2014 13:23:12 -0000

Thanks for your review!

On Feb 20, 2014, at 12:04 AM, Meral Shirazipour =
<meral.shirazipour@ericsson.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at < =
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> .
> =20
> Please wait for direction from your document shepherd or AD before =
posting a new version of the draft.
> =20
> Document: draft-ietf-xrblock-rtcp-xr-synchronization-08
> Reviewer: Meral Shirazipour
> Review Date: 2014-02-19
> IETF LC End Date:  2014-02-04
> IESG Telechat date: 2014-02-20
> =20
> Summary: This draft is ready for publication as an 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 Thu Feb 20 05:29:20 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F24981A0162 for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 05:29:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 bPXi912Bm8yR for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 05:29:16 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id B63931A0161 for <gen-art@ietf.org>; Thu, 20 Feb 2014 05:29:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D9B242CCD0; Thu, 20 Feb 2014 15:29:11 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5JWiN-4OpeyB; Thu, 20 Feb 2014 15:29:10 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B47A22CCC1; Thu, 20 Feb 2014 15:29:09 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52EBB6F8.8090503@bell-labs.com>
Date: Thu, 20 Feb 2014 14:29:09 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AF4E591-2495-4E7C-9460-0CBD9502D8A1@piuha.net>
References: <52E28081.4000102@bell-labs.com> <8C0868AA-166D-4C0E-B176-C0A88EAE97E5@comnet.tkk.fi> <52E2B7BC.5070506@bell-labs.com> <0C6A9E5B-753F-4080-AEB5-21C2927EC689@comnet.tkk.fi> <52EBB6F8.8090503@bell-labs.com>
To: Vijay K. Gurbani <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/gZuALGbn2RBu9LWUo4066i08Nio
Cc: "xrblock-chairs@tools.ietf.org" <xrblock-chairs@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, Varun Singh <varun@comnet.tkk.fi>, "draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-bytes-discarded-metric-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 13:29:18 -0000

Thanks for the review, Vijay! For what it is worth, I agree with you on =
it being desirable to document the reason for that sentence, and agree =
that other documents are not necessarily sufficient to explain the =
situation.

Jari

On Jan 31, 2014, at 3:45 PM, Vijay K. Gurbani <vkg@bell-labs.com> wrote:

> On 01/31/2014 08:25 AM, Varun Singh wrote:
>> Hi Vijay,
>>=20
>> Apologies for the tardiness, comments inline.
>=20
> Varun: No worries.  More inline.
>=20
>> In this particular case, we are worried about a side channel attack.
>> The attacker sends a late arriving packet (timestamp in the past) to
>> the receiver and if the receiver sends a discard report with the same
>> number of bytes as the payload of the injected packet, the attacker
>> may infer that no security processing was performed. If it observes
>> no discard report, it may infer that security procedures were
>> performed on the packet.
>=20
> Ah, so you can trivially solve this problem by describing the attack =
in
> the draft, much as you do above.
>=20
>> I think one of the reasons not to explicitly write about the threat
>> model is because there are several reason to use and not use
>> SRTP/AVPF. they are covered in ietf-avt-srtp-not-mandatory, and
>> implementors should read that document to make up their mind.
>=20
> My reading of draft-ietf-avt-srtp-not-mandatory is that it does not
> absolve RTP extension authors from talking about security, rather it
> exhorts them to talk about the specific security problems exhibited
> by their proposed extension and furthermore, elaborate how to address
> such concerns.
>=20
>> I hope the chairs can clarify on how to proceed.
>=20
> Cheers,
>=20
> - vijay
> --=20
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web: http://ect.bell-labs.com/who/vkg/  | Calendar: =
http://goo.gl/x3Ogq
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Thu Feb 20 06:03:14 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1461A0174 for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 06:03:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 HUfFBTurHjfP for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 06:03:06 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 002B11A0162 for <gen-art@ietf.org>; Thu, 20 Feb 2014 06:03:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1F58C2CD39; Thu, 20 Feb 2014 16:03:02 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G_QCbe4AaAVd; Thu, 20 Feb 2014 16:03:00 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 627222CCE4; Thu, 20 Feb 2014 16:03:00 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <530155C7.2090206@gmail.com>
Date: Thu, 20 Feb 2014 15:03:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD3AFA4C-4A50-49C4-B2D8-1A4F1C3067F8@piuha.net>
References: <530155C7.2090206@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/2VGXd4t_4BcI0yt65MFcG5poUi4
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-stir-problem-statement.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-stir-problem-statement-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, 20 Feb 2014 14:03:12 -0000

Thanks for your review ;-)

On Feb 17, 2014, at 1:20 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-stir-problem-statement-03.txt
> Reviewer: Brian Carpenter
> Review Date: 2014-02-17
> IETF LC End Date: 2014-02-20
> IESG Telechat date: 2014-02-20
>=20
> Summary: Ready
> --------
>=20
> Comments:
> ---------
>=20
> Well written, clear, very scary.
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Thu Feb 20 06:04:54 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 4376D1A0061 for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 06:04:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 pFRrgfs8bJN3 for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 06:04:51 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 125341A016D for <gen-art@ietf.org>; Thu, 20 Feb 2014 06:04:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 31E922CD39; Thu, 20 Feb 2014 16:04:47 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FeUFScvcbQ4q; Thu, 20 Feb 2014 16:04:46 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 25F182CCE4; Thu, 20 Feb 2014 16:04:46 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201402031448.s13EmxIu056358@givry.fdupont.fr>
Date: Thu, 20 Feb 2014 15:04:45 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <6A4069EF-802D-42CD-A083-21840327678A@piuha.net>
References: <201402031448.s13EmxIu056358@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/5YpN34Y3tb0UrbVdYqjqr6EWyKg
Cc: gen-art@ietf.org, draft-housley-pkix-test-oids.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-housley-pkix-test-oids-00.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, 20 Feb 2014 14:04:53 -0000

Thanks for the review again, Francis! Russ, did you noise the typo?

Jari

On Feb 3, 2014, at 3:48 PM, Francis Dupont <Francis.Dupont@fdupont.fr> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> 
> <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-test-oids-00.txt
> Reviewer: Francis Dupont
> Review Date: 20140122
> IETF LC End Date: 20140211
> IESG Telechat date: unknown
> 
> Summary: Ready
> 
> Major issues: None
> 
> Minor issues: None
> 
> Nits/editorial comments:
> - typo 3 page 2:
>    ... The actual
>   polices used for production certificates has a significant impact
>        ^
> BTW if the word is policies than has -> have
> 
> Regards
> 
> Francis.Dupont@fdupont.fr
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Thu Feb 20 06:08:29 2014
Return-Path: <ice@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 E4C2F1A018D for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 06:08:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.704
X-Spam-Level: 
X-Spam-Status: No, score=-6.704 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vVYekvLEyyQm for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 06:08:24 -0800 (PST)
Received: from aer-iport-4.cisco.com (unknown [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id 524011A018C for <gen-art@ietf.org>; Thu, 20 Feb 2014 06:08:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1183; q=dns/txt; s=iport; t=1392905301; x=1394114901; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=txMK4vrh9WRNBmace77vP6h+pkJTCiStynNYb2N+Kus=; b=R+Fie/WEnpSFCWJR0QwASBPV8isez4235MfuTvFrRwUqV/BL5jtQ3KaV GSIq4xYHR+7BwXZzZ8clCyHfCoR1WOALChoAI8JPzUpwLa1XO37FqzAoQ aPu+myMQNqpMcRXy3uCfSHRW7z50j94cMy3ifvmhHMZ2VxH/swm0t04M9 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAIACQLBlOQ/khR/2dsb2JhbABZgwY4qFeYCoENFnSCJQEBAQMBOj8FCwsQBDJXBhOHfQgNzjkXjHKBGyQzB4MkgRQEmDCBMpBygy47gS0
X-IronPort-AV: E=Sophos;i="4.97,512,1389744000";  d="scan'208";a="826862"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-4.cisco.com with ESMTP; 20 Feb 2014 14:08:20 +0000
Received: from ams-iwijnand-87112.cisco.com (ams-iwijnand-87112.cisco.com [10.55.191.157]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s1KE8JBj019139 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Feb 2014 14:08:20 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <201402171512.s1HFCGsc027226@givry.fdupont.fr>
Date: Thu, 20 Feb 2014 15:08:19 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EB8AFD32-213B-4919-A061-703A6AB03F33@cisco.com>
References: <201402171512.s1HFCGsc027226@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/F-Uw2ALBraomV7FOrhCVw7uBDdg
Cc: gen-art@ietf.org, draft-ietf-l3vpn-mldp-vrf-in-band-signaling.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-l3vpn-mldp-vrf-in-band-signaling-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, 20 Feb 2014 14:08:27 -0000

Hi Francis,

I'll resolve the editorial nits.

Regarding the co-author list, you say (soft) limit, what does (soft) =
mean here?

Does one co-author need to drop of, or will it pass?

Thx,

Ice.

On 17 Feb 2014, at 16:12, Francis Dupont <Francis.Dupont@fdupont.fr> =
wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-l3vpn-mldp-vrf-in-band-signaling-03.txt
> Reviewer: Francis Dupont
> Review Date: 20140211
> IETF LC End Date: 20140212
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
> - the number of authors is greater than the (soft) limit
>=20
> - 1 page 5: too many 'o' in 'co-oordination'
>=20
> - 1.2 pages 5 & 6: IMHO you should describe more terms in the =
Terminology
>  section, e.g., UMH, RPA and even RD (as VRF is already in it)
>=20
> Regards=20
>=20
> Francis.Dupont@fdupont.fr


From nobody Thu Feb 20 06:12:23 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 A5E321A01B4; Thu, 20 Feb 2014 06:12:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 LQEHjEk4g9FW; Thu, 20 Feb 2014 06:12:14 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id BE5601A01B2; Thu, 20 Feb 2014 06:12:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DD2F02CCE4; Thu, 20 Feb 2014 16:12:05 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U1i6dvKP2JXF; Thu, 20 Feb 2014 16:12:04 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 2C3EB2CCD0; Thu, 20 Feb 2014 16:12:04 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52E83C75.7030909@dial.pipex.com>
Date: Thu, 20 Feb 2014 15:12:03 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D2A7761-2C8D-41C7-8BC7-B4F175187F95@piuha.net>
References: <52E83C75.7030909@dial.pipex.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/dm9sHsDIhSrHSQ2-FetdNtlMpEs
Cc: General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-v6ops-nat64-experience.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 14:12:19 -0000

Thanks for the review, Elwyn. Joel, Fred, authors, any comments on this?

Jari

On Jan 29, 2014, at 12:25 AM, Elwyn Davies <elwynd@dial.pipex.com> =
wrote:

>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-v6ops-nat64-experience-09.txt
> Reviewer: Elwyn Davies
> Review Date: 28 January 2014
> IETF LC End Date: 28 January 2014
> IESG Telechat date: (if known) -
>=20
> Summary:
> Not ready.  This document needs a serious rewrite with the assistance =
of a mother tongue English speaker.  I started doing some of this =
getting as far as s3.1.4, however I came to the conclusion that =
significant parts of the language were sufficiently unclear that I was =
unable to determine the intended meaning.  Accordingly I have abandoned =
the review and will have another go assuming a rewrite is done.  Please =
consider whether the title should be modified as noted below.
>=20
> Major issues:
>=20
> Minor issues:
> Title:  The title is rather misleading since it the document actually =
documents two suggested ways of deploying NAT64 as well as experience of =
deploying these solutions. Maybe 'NAT64 Deployment Options and =
Experience'.
>=20
> s1: A reference to explain what PDP context etc means in an LTE =
environment would be useful.
>=20
> s3.1.3: It is stated that placing the NAT64 (middlebox) in a =
centralized location would 'reduce the diversity of  log format'.  I =
guess what is possibly being said that is that the network should =
preferentially use just one NAT64 box centrally placed rather than =
several (smaller) boxes at various edge locations.  I think this needs =
to be explained more clearly (assuming I have it right).  OTOH I would =
rather expect that most network owners would go for a single species of =
NAT64 box so the diversity of log formats is really a side issue.
>=20
> s5.2: The problem here is not specifically geo-location - and since we =
normally don't have any mapping between topology and location this seems =
inappropriate - but doing host identification (which is what RFC 6967 is =
about.  Shouldn't this section just be about host identification?
>=20
> s8, para 2:
>> We configure ULAs as NAT64 prefixes on a NAT64-CGN.
> So.. is this a mandatory requirement or just a possibility?
>=20
> Nits/editorial comments:
>=20
> s1, para 1: s/Internet/the Internet/
>=20
> s1, para 2: s/simplify networks provisioning/simplify the provisioning =
of networks/, s/confers some benefits to/confers some benefits on/, =
s/such mobile/such a mobile/, s/if Long Term/if a Long Term/
>=20
> s3.1.1: s/can be seen with better transparency features/can offer =
improved transparency to <state who or what is offered the improved =
transparency> /
>=20
> s3.1.1: Expand A+P abbreviation.
>=20
> s3.3.1: s/IPv4 shortage/IPv4 address shortage/
>=20
> ss3.1.2, 3.1.3 and 3.1.4: These are very long paragraphs.  It would be =
good to separate the various discussion points into separate paragraphs.
>=20
> s3.1.2: "..to enable access of IPv4 only applications" Presumably this =
is access to applications running on the IPv4 side from applications on =
the IPV6 side... Suggest
> "to allow applications running on the IPv6 network to interact with =
applications that can only use IPv4 communications or IPv6 applications =
that need to communicate using literal IPv4 addresses."
>=20
> s3.1.2: s/discover NAT64 prefix/discover the NAT64 prefix/
>=20
> s3.1.2: need a reference for BIND.
>=20
> s3.1.2: s/...(BIND) software supports the function./The ... (BIND) =
implementation of NAT64 supports this discovery function./
>=20
> s3.1.2:s/Operators should not/Users should not/ perhaps.
>=20
> s3.1.2: s/going to IPv4-only service/going to IPv4-only services/
>=20
> s3.1.2: s/restrains NAT uses/restrains NAT usage/
>=20
> s3.1.2: s/all traffic flows have to be traversed and translated./all =
traffic flows have to traverse the NAT44 middlebox and be translated =
there./
>=20
> s3.1.2: s/may serve a double roles, i.e. a translator and IPv6 =
forwarder./may serve a dual role acting as both translator and IPv6 =
forwarder./
>=20
> s3.1.2: s/Therefore, both IPv6 and IPv6
>=20
> s3.1.2:
> OLD:
> In some sense, it encourages IPv6 transmission and restrains NAT uses =
compared to NAT44(if used), on which all traffic flows have to be =
traversed and translated. In some cases, NAT64-CGN may serve double =
roles, i.e. a translator and IPv6 forwarder. In mobile networks, NAT64 =
is likely deployed as the default gateway serving for all the IPv6 =
traffic. The traffic heading to a dual-stack server is only forwarded on =
the NAT64. Therefore, both IPv6 and IPv4 are suggested to be configured =
on the Internet faced interfaces of NAT64. We tested on Top100 websites =
(referring to [Alexa] statistics). 43% of websites are connected and =
forwarded on the NAT64 since those websites have both AAAA and A =
records. With expansion of IPv6 supports, the translation process on =
NAT64 will likely be faded. In addition, it should be noted the =
DNS64-DNSSEC Interaction[RFC6147] may impact the DNS64 process. For =
example, DNS64 will not work with the case, where there is a DNS query =
with the "DNSSEC OK" (DO) bit set and the "Checking Disabled" (CD) bit =
set received.
> NEW:
> In some sense, it encourages IPv6 transmission and restrains NAT usage =
compared to system using NAT44 (if used), on which all traffic flows =
have to traverse the NAT44 middlebox and be translated in passing. In =
some cases, NAT64-CGN may serve a dual role as both translator and IPv6 =
forwarder. In mobile networks, NAT64 is likely deployed as the default =
gateway serving all the IPv6 traffic. The traffic heading to a =
dual-stack server is only forwarded via the NAT64. Therefore, it is =
suggested [or may be RECOMMENDED] that both IPv6 and IPv4 are configured =
on the Internet facing interfaces of NAT64 middleboxes.  We tested the =
configuration of the Top100 websites (as identified in the [Alexa] =
statistics).  43% of websites are [Should this be "would be"] connected =
and forwarded via NAT64 since those websites have both AAAA and A =
records. With the expansion of IPv6 support, the need for the =
translation process on NAT64 middleboxes will likely diminish. In =
addition, it should be noted that the interaction of DNS64 and DNSSEC =
[RFC6147] may impact the DNS64 process. For example, DNS64 will not work =
in the case where a DNS query is received that has the "DNSSEC OK" (DO) =
bit set and the "Checking Disabled" (CD) bit set.
>=20
>=20
> s3.1.3: s/is problematic from multiple-vendor's equipment due to =
inconsistent formats of log records./obtained from equipment supplied by =
multiple vendors may be problematic due to inconsistent log formats./
>=20
> s3.1.3: This gave me a bit of a laugh...  So having got over my =
unstable user experience (probably due to excessive consumption of =
beer..)
> OLD:
>   Since the topology on each
>   path is different, it may cause unstable user experiences and some
>   degradation of Quality of Experience (QoE) when fallback to the =
other
>   protocol is not powerful enough.
> NEW:
>   Since the routes taken by the two traffic sets may be different, =
user experiences
>   may be inconsistent and there may be some
>   degradation of Quality of Experience (QoE) when fallback to the =
other
>   protocol is not sufficiently rapid. [or does this mean that the =
alternative route
>   doesn't have enough capacity]
>=20
> Please clarify.
>=20
> [I gave up on language corrections at this point as it essentially =
needs a serious rewrite.]
>=20
> s4.1, last para: Specifying 91.21% of traffic seems inappropriately =
exact.
>=20
> s6.1:  It may well be that NAT64-CGN have an FTP ALG .. given the =
general view that FTP shouldn't be used it seems peculiar that this is =
the only default implementation!
> Perhaps a comment about this (and maybe even TURNING OFF the FTP ALG) =
seems like an option.
>=20
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Thu Feb 20 06:47:45 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 1CB581A019B for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 06:47:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1x9s5Xt9AwpK for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 06:47:40 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 1DBFC1A0195 for <gen-art@ietf.org>; Thu, 20 Feb 2014 06:47:40 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id A1D179A4325; Thu, 20 Feb 2014 09:47:26 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id e+NcUZ8pYtNF; Thu, 20 Feb 2014 09:47:05 -0500 (EST)
Received: from v150.vpn.iad.rg.net (v150.vpn.iad.rg.net [198.180.150.150]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id BBD719A4317; Thu, 20 Feb 2014 09:47:05 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <52E83C75.7030909@dial.pipex.com>
Date: Thu, 20 Feb 2014 09:46:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E87A560B-EC79-432C-9D7F-E25079D4EE2A@vigilsec.com>
References: <52E83C75.7030909@dial.pipex.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/apVN21DIIPTx--P9xopEWM8p3Ko
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-v6ops-nat64-experience.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 14:47:43 -0000

Elwyn:

Nice review.  I'm sure the document will be improved because of your =
efforts.  I'd like to make two comments.

> s3.1.3: It is stated that placing the NAT64 (middlebox) in a =
centralized location would 'reduce the diversity of  log format'.  I =
guess what is possibly being said that is that the network should =
preferentially use just one NAT64 box centrally placed rather than =
several (smaller) boxes at various edge locations.  I think this needs =
to be explained more clearly (assuming I have it right).  OTOH I would =
rather expect that most network owners would go for a single species of =
NAT64 box so the diversity of log formats is really a side issue.

In the beginning, yes.  Subsequent procurements cal lead to changing =
vendor.  Mergers also lead to multiple venders.

> s5.2: The problem here is not specifically geo-location - and since we =
normally don't have any mapping between topology and location this seems =
inappropriate - but doing host identification (which is what RFC 6967 is =
about.  Shouldn't this section just be about host identification?

If a law enforcement agency shows up with a subpoena, they really do =
want to know what door to knock down.

Thanks for listening,
  Russ


From nobody Thu Feb 20 07:37: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 126F91A0170 for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 07:37:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JU0iW48BrVAK for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 07:37:38 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id B44341A01CB for <gen-art@ietf.org>; Thu, 20 Feb 2014 07:37:38 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id s1KFbOXj020533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 20 Feb 2014 09:37:25 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s1KFbOSh029919 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 20 Feb 2014 09:37:24 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id s1KFbNCY014679; Thu, 20 Feb 2014 09:37:23 -0600 (CST)
Message-ID: <53062177.9050407@bell-labs.com>
Date: Thu, 20 Feb 2014 09:38:31 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: draft-ietf-abfab-arch@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/ttQngNIIoLM0_3heH4NxGREdWwk
Cc: General Area Review Team <gen-art@ietf.org>, abfab-chairs@tools.ietf.org, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: [Gen-art] Gen-ART review of draft-ietf-abfab-arch-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 15:37:41 -0000

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

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

Document: draft-ietf-abfab-arch-12
Reviewer: Vijay K. Gurbani
Review Date: Feb-20-2014
IETF LC End Date: Unknown
IESG Telechat date: Feb-20-2014

Major: 0
Minor: 0
Nits:  0

This document is ready as an Informational.

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 Feb 20 07:50:43 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 5052F1A01E4 for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 07:50:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 UYAy3feia7_r for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 07:50:38 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A9D511A01FD for <gen-art@ietf.org>; Thu, 20 Feb 2014 07:50:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E99182CEAE; Thu, 20 Feb 2014 17:50:31 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P783JuiVV5l2; Thu, 20 Feb 2014 17:50:29 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 617CF2CCD0; Thu, 20 Feb 2014 17:50:29 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <53062177.9050407@bell-labs.com>
Date: Thu, 20 Feb 2014 16:50:29 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <73C9734D-C56F-4747-B7DE-21EB161BA3D5@piuha.net>
References: <53062177.9050407@bell-labs.com>
To: Vijay K. Gurbani <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/32-mXl7xrCpj6ae8lczXAE__ab0
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-abfab-arch@tools.ietf.org, abfab-chairs@tools.ietf.org, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-abfab-arch-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 15:50:41 -0000

Thanks for your review, Vijay!

Jari

On Feb 20, 2014, at 4:38 PM, Vijay K. Gurbani <vkg@bell-labs.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Please resolve these comments along with any other Last Call comments
> you may receive.
> 
> Document: draft-ietf-abfab-arch-12
> Reviewer: Vijay K. Gurbani
> Review Date: Feb-20-2014
> IETF LC End Date: Unknown
> IESG Telechat date: Feb-20-2014
> 
> Major: 0
> Minor: 0
> Nits:  0
> 
> This document is ready as an Informational.
> 
> 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
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Thu Feb 20 08:05:17 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 BE69F1A01DA for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 08:05:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 DUpYkZAK2gLy for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 08:05:14 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CE05E1A01E3 for <gen-art@ietf.org>; Thu, 20 Feb 2014 08:05:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E8F5E2CEAE; Thu, 20 Feb 2014 18:05:09 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mEpOaEFc06Sg; Thu, 20 Feb 2014 18:05:09 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id BE6412CCD0; Thu, 20 Feb 2014 18:05:08 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52E1DA89.40707@joelhalpern.com>
Date: Thu, 20 Feb 2014 17:05:08 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <BCB401D6-A8CA-4CF5-AA05-9C2082B5EE3F@piuha.net>
References: <52E1989D.4020804@nostrum.com> <52E1DA89.40707@joelhalpern.com>
To: Joel M. Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Sh4b2cz9HTZvWJCfHqN0dG9RqPU
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] review: draft-ietf-manet-olsrv2-rmpr-optimization-00
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 16:05:15 -0000

Thank you for your review, Joel.

jari

On Jan 24, 2014, at 4:14 AM, 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-manet-olsrv2-rmpr-optimization-00
>    Routing MPR Optimization for the Optimized Link State
>             Routing Protocol version 2 (OLSRv2)
> Reviewer: Joel M. Halpern
> Review Date: 21-January-2014
> IETF LC End Date: 4-February-2014
> IESG Telechat date: N/A
> 
> Summary: This document is ready for publication as a Proposed Standard.
> 
> Major issues: N/A
> 
> Minor issues: N/A
> 
> Nits/editorial comments: N/A
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Thu Feb 20 08:06:57 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 57A791A01EA for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 08:06:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 Nxfj1-gFcJAt for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 08:06:54 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4279F1A01F7 for <gen-art@ietf.org>; Thu, 20 Feb 2014 08:06:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 583042CEB1; Thu, 20 Feb 2014 18:06:50 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IDhagAtPetV8; Thu, 20 Feb 2014 18:06:49 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 607652CEAE; Thu, 20 Feb 2014 18:06:49 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52F034C9.60802@gmail.com>
Date: Thu, 20 Feb 2014 17:06:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D78829C0-005A-45AE-9EE9-B8F84D05F09C@piuha.net>
References: <52F034C9.60802@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/0LHcQnY8YZWtNHxMOgooMD1bjRo
Cc: draft-ietf-manet-nhdp-olsrv2-tlv-extension.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-manet-nhdp-olsrv2-tlv-extension-01.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, 20 Feb 2014 16:06:56 -0000

Thanks for your review, Brian.

Jari

On Feb 4, 2014, at 1:31 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-manet-nhdp-olsrv2-tlv-extension-01.txt
> Reviewer: Brian Carpenter
> Review Date: 2014-02-04
> IETF LC End Date: 2014-02-07
> IESG Telechat date:
>=20
> Summary:  Ready
> --------
>=20
> Comments:
> ---------
>=20
> This draft is well-written and clear.
>=20
> It retro-fits extensibility to two existing specifications.
> As an author of RFC 6709 I find this an interesting exercise. Do
> the hints in http://tools.ietf.org/html/rfc6709#section-4 help,
> especially bullet 2?
>=20
> Minor Issues:
> ------------
>=20
> It is highly unusual for a draft to formally update another draft
> (draft-ietf-manet-olsrv2), even though the latter is approved and
> in the RFC queue. If we were a rational organisation, that draft
> would be updated before publication.
>=20
> (The writeup actually says "The Optimized Link State Routing Protocol
> version 2 (OLSRv2) has been published as Standards Track." but that is
> inaccurate.)
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Thu Feb 20 08:56:56 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD0821A0217; Thu, 20 Feb 2014 08:56:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 aceD2vCJ6KOb; Thu, 20 Feb 2014 08:56:48 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 019F51A01EE; Thu, 20 Feb 2014 08:56:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 855FF2CEB2; Thu, 20 Feb 2014 18:56:43 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6URdb7Yzef1; Thu, 20 Feb 2014 18:56:42 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 174A92CEB1; Thu, 20 Feb 2014 18:56:42 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <0D2A7761-2C8D-41C7-8BC7-B4F175187F95@piuha.net>
Date: Thu, 20 Feb 2014 17:56:41 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0D801AD-CD5A-4259-8BF5-85A105207217@piuha.net>
References: <52E83C75.7030909@dial.pipex.com> <0D2A7761-2C8D-41C7-8BC7-B4F175187F95@piuha.net>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/EIcT9SDFU8Ou3LTuJYi5VRUoJUc
Cc: General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-v6ops-nat64-experience.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 16:56:53 -0000

FWIW, I have now done my own review. I think there are language issues, =
but they do not prevent going forward. Language itself will be fixed by =
the RFC Editor. I'm more interested in cases where there might be an =
semantics unclarity issue.=20

I think it would be beneficial to go through each of the comments before =
final approval of the document.

With that in mind, going through some of my own and Elwyn's comments:

>    o  Operators who adopt NAT64-FE may leverage the application layer
>       proxies, e.g. X-Forwarded-For (XFF)
>       [
> I-D.ietf-appsawg-http-forwarded
> ], to convey the IPv6 source
>       address in HTTP headers. =20

I'd say =85 may leverage application layer proxies, and those may use =
additional attributes such as X-Forwarded-For ...

> Those messages would be passed on to
>       web-servers.  The log parsing tools are required to be able to
>       support IPv6 and may lookup Radius servers for the target
>       subscribers based on IPv6 addresses included in XFF HTTP =
headers.
>       XFF is the de facto standard which has been integrated in most
>       Load Balancers.  Therefore, it may be superior to use in a =
NAT-FE
>       environment.  In the downsides, XFF is specific to HTTP.  It
>       restricts the usages so that the solution can't be applied to
>       requests made over HTTPs.  This makes geo-location problematic =
for
>       HTTPs based services.
>=20

Not sure we should call something a de facto standard while pointing to =
a draft. I'd just say "=85 has been implemented in many =85"

> The experiences of some
>    applications are still align with [
> RFC6586].=20


Not sure what this means.


> |  SIP-VoIP      |Fail, due to the lack of NAT64 traversal            =
|
>=20

Did you mean ALG? Not sure what this would mean otherwise.

>> Minor issues:
>> Title:  The title is rather misleading since it the document actually =
documents two suggested ways of deploying NAT64 as well as experience of =
deploying these solutions. Maybe 'NAT64 Deployment Options and =
Experience'.

I think that is a reasonable suggestion.

>>=20
>> s1: A reference to explain what PDP context etc means in an LTE =
environment would be useful.
>>=20
>> s3.1.3: It is stated that placing the NAT64 (middlebox) in a =
centralized location would 'reduce the diversity of  log format'.  I =
guess what is possibly being said that is that the network should =
preferentially use just one NAT64 box centrally placed rather than =
several (smaller) boxes at various edge locations.  I think this needs =
to be explained more clearly (assuming I have it right).  OTOH I would =
rather expect that most network owners would go for a single species of =
NAT64 box so the diversity of log formats is really a side issue.
>>=20
>> s5.2: The problem here is not specifically geo-location - and since =
we normally don't have any mapping between topology and location this =
seems inappropriate - but doing host identification (which is what RFC =
6967 is about.  Shouldn't this section just be about host =
identification?
>>=20
>> s8, para 2:
>>> We configure ULAs as NAT64 prefixes on a NAT64-CGN.
>> So.. is this a mandatory requirement or just a possibility?
>>=20
>> Nits/editorial comments:
>>=20
>> s1, para 1: s/Internet/the Internet/
>>=20
>> s1, para 2: s/simplify networks provisioning/simplify the =
provisioning of networks/, s/confers some benefits to/confers some =
benefits on/, s/such mobile/such a mobile/, s/if Long Term/if a Long =
Term/
>>=20
>> s3.1.1: s/can be seen with better transparency features/can offer =
improved transparency to <state who or what is offered the improved =
transparency> /
>>=20
>> s3.1.1: Expand A+P abbreviation.
>>=20
>> s3.3.1: s/IPv4 shortage/IPv4 address shortage/
>>=20
>> ss3.1.2, 3.1.3 and 3.1.4: These are very long paragraphs.  It would =
be good to separate the various discussion points into separate =
paragraphs.
>>=20
>> s3.1.2: "..to enable access of IPv4 only applications" Presumably =
this is access to applications running on the IPv4 side from =
applications on the IPV6 side... Suggest
>> "to allow applications running on the IPv6 network to interact with =
applications that can only use IPv4 communications or IPv6 applications =
that need to communicate using literal IPv4 addresses."
>>=20
>> s3.1.2: s/discover NAT64 prefix/discover the NAT64 prefix/
>>=20
>> s3.1.2: need a reference for BIND.
>>=20
>> s3.1.2: s/...(BIND) software supports the function./The ... (BIND) =
implementation of NAT64 supports this discovery function./
>>=20
>> s3.1.2:s/Operators should not/Users should not/ perhaps.
>>=20
>> s3.1.2: s/going to IPv4-only service/going to IPv4-only services/
>>=20
>> s3.1.2: s/restrains NAT uses/restrains NAT usage/
>>=20
>> s3.1.2: s/all traffic flows have to be traversed and translated./all =
traffic flows have to traverse the NAT44 middlebox and be translated =
there./
>>=20
>> s3.1.2: s/may serve a double roles, i.e. a translator and IPv6 =
forwarder./may serve a dual role acting as both translator and IPv6 =
forwarder./
>>=20
>> s3.1.2: s/Therefore, both IPv6 and IPv6
>>=20
>> s3.1.2:
>> OLD:
>> In some sense, it encourages IPv6 transmission and restrains NAT uses =
compared to NAT44(if used), on which all traffic flows have to be =
traversed and translated. In some cases, NAT64-CGN may serve double =
roles, i.e. a translator and IPv6 forwarder. In mobile networks, NAT64 =
is likely deployed as the default gateway serving for all the IPv6 =
traffic. The traffic heading to a dual-stack server is only forwarded on =
the NAT64. Therefore, both IPv6 and IPv4 are suggested to be configured =
on the Internet faced interfaces of NAT64. We tested on Top100 websites =
(referring to [Alexa] statistics). 43% of websites are connected and =
forwarded on the NAT64 since those websites have both AAAA and A =
records. With expansion of IPv6 supports, the translation process on =
NAT64 will likely be faded. In addition, it should be noted the =
DNS64-DNSSEC Interaction[RFC6147] may impact the DNS64 process. For =
example, DNS64 will not work with the case, where there is a DNS query =
with the "DNSSEC OK" (DO) bit set and the "Checking Disabled" (CD) bit =
set received.
>> NEW:
>> In some sense, it encourages IPv6 transmission and restrains NAT =
usage compared to system using NAT44 (if used), on which all traffic =
flows have to traverse the NAT44 middlebox and be translated in passing. =
In some cases, NAT64-CGN may serve a dual role as both translator and =
IPv6 forwarder. In mobile networks, NAT64 is likely deployed as the =
default gateway serving all the IPv6 traffic. The traffic heading to a =
dual-stack server is only forwarded via the NAT64. Therefore, it is =
suggested [or may be RECOMMENDED] that both IPv6 and IPv4 are configured =
on the Internet facing interfaces of NAT64 middleboxes.  We tested the =
configuration of the Top100 websites (as identified in the [Alexa] =
statistics).  43% of websites are [Should this be "would be"] connected =
and forwarded via NAT64 since those websites have both AAAA and A =
records. With the expansion of IPv6 support, the need for the =
translation process on NAT64 middleboxes will likely diminish. In =
addition, it should be noted that the interaction of DNS64 and DNSSEC =
[RFC6147] may impact the DNS64 process. For example, DNS64 will not work =
in the case where a DNS query is received that has the "DNSSEC OK" (DO) =
bit set and the "Checking Disabled" (CD) bit set.
>>=20
>>=20
>> s3.1.3: s/is problematic from multiple-vendor's equipment due to =
inconsistent formats of log records./obtained from equipment supplied by =
multiple vendors may be problematic due to inconsistent log formats./
>>=20
>> s3.1.3: This gave me a bit of a laugh...  So having got over my =
unstable user experience (probably due to excessive consumption of =
beer..)
>> OLD:
>>  Since the topology on each
>>  path is different, it may cause unstable user experiences and some
>>  degradation of Quality of Experience (QoE) when fallback to the =
other
>>  protocol is not powerful enough.
>> NEW:
>>  Since the routes taken by the two traffic sets may be different, =
user experiences
>>  may be inconsistent and there may be some
>>  degradation of Quality of Experience (QoE) when fallback to the =
other
>>  protocol is not sufficiently rapid. [or does this mean that the =
alternative route
>>  doesn't have enough capacity]

Yes, that would be better.

>>=20
>> Please clarify.
>>=20
>> [I gave up on language corrections at this point as it essentially =
needs a serious rewrite.]
>>=20
>> s4.1, last para: Specifying 91.21% of traffic seems inappropriately =
exact.
>>=20
>> s6.1:  It may well be that NAT64-CGN have an FTP ALG .. given the =
general view that FTP shouldn't be used it seems peculiar that this is =
the only default implementation!
>> Perhaps a comment about this (and maybe even TURNING OFF the FTP ALG) =
seems like an option.


Jari


From nobody Thu Feb 20 10:55:04 2014
Return-Path: <fred@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 E90C51A021B; Thu, 20 Feb 2014 10:55:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.049
X-Spam-Level: 
X-Spam-Status: No, score=-115.049 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.548, 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 azWqTxxb73eV; Thu, 20 Feb 2014 10:54:58 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id D84011A00EC; Thu, 20 Feb 2014 10:54:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9620; q=dns/txt; s=iport; t=1392922494; x=1394132094; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=mIuPuggCSA+lIBVum/xIZR7TSSdjKsjD+7i6sbRFLug=; b=a1u55h8TWzt1/N/FREPR/lB0SAh2auf2PiYE9lUY/QBtkzJjULxHGhya 80CDEM9Qt1H1OkGZFWWBBWQOeyCxZo7oIZgRa8MoeqVVC9Cf5E/iOySVp kfBG0R8yabdBbGfvmr+J94NpxtvOEbK1uvyEvHeDoXNaYiIDL/4Y2a4vd I=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAMROBlOtJXG8/2dsb2JhbABTBoMGOFfADoEQFnSCJQEBAQMBAQEBawsFCwIBCBQELicLJQIEDgUODYdiCA3OKBeMcoEvMhEHgySBFASQQYEzhjyBMpBygy2CKg
X-IronPort-AV: E=Sophos;i="4.97,513,1389744000";  d="asc'?scan'208";a="305422717"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-5.cisco.com with ESMTP; 20 Feb 2014 18:54:53 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id s1KIsqWJ025341 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 20 Feb 2014 18:54:52 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.247]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Thu, 20 Feb 2014 12:54:52 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>
Thread-Topic: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
Thread-Index: AQHPHIBOEbCch1t4W0Wxbfxn26ov75q+twmAgABPAAA=
Date: Thu, 20 Feb 2014 18:54:52 +0000
Message-ID: <A3508B43-77DD-4113-A0E4-C8A188410608@cisco.com>
References: <52E83C75.7030909@dial.pipex.com> <0D2A7761-2C8D-41C7-8BC7-B4F175187F95@piuha.net>
In-Reply-To: <0D2A7761-2C8D-41C7-8BC7-B4F175187F95@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.246.218]
Content-Type: multipart/signed; boundary="Apple-Mail=_650FD774-AA6B-4143-B7A5-F336781D6A23"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Vj4PekcaAY_XgZUnPE4JCVDXuNo
Cc: General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>, "<draft-ietf-v6ops-nat64-experience.all@tools.ietf.org>" <draft-ietf-v6ops-nat64-experience.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 18:55:01 -0000

--Apple-Mail=_650FD774-AA6B-4143-B7A5-F336781D6A23
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I appreciate the review. I disagree that it needs a complete rewrite, =
but I agree that language work would be beneficial. I do believe that =
the RFC Editor will have an unusual level of changes, due to language =
issues.

On Feb 21, 2014, at 3:12 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> Thanks for the review, Elwyn. Joel, Fred, authors, any comments on =
this?
>=20
> Jari
>=20
> On Jan 29, 2014, at 12:25 AM, Elwyn Davies <elwynd@dial.pipex.com> =
wrote:
>=20
>>=20
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>=20
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document: draft-ietf-v6ops-nat64-experience-09.txt
>> Reviewer: Elwyn Davies
>> Review Date: 28 January 2014
>> IETF LC End Date: 28 January 2014
>> IESG Telechat date: (if known) -
>>=20
>> Summary:
>> Not ready.  This document needs a serious rewrite with the assistance =
of a mother tongue English speaker.  I started doing some of this =
getting as far as s3.1.4, however I came to the conclusion that =
significant parts of the language were sufficiently unclear that I was =
unable to determine the intended meaning.  Accordingly I have abandoned =
the review and will have another go assuming a rewrite is done.  Please =
consider whether the title should be modified as noted below.
>>=20
>> Major issues:
>>=20
>> Minor issues:
>> Title:  The title is rather misleading since it the document actually =
documents two suggested ways of deploying NAT64 as well as experience of =
deploying these solutions. Maybe 'NAT64 Deployment Options and =
Experience'.
>>=20
>> s1: A reference to explain what PDP context etc means in an LTE =
environment would be useful.
>>=20
>> s3.1.3: It is stated that placing the NAT64 (middlebox) in a =
centralized location would 'reduce the diversity of  log format'.  I =
guess what is possibly being said that is that the network should =
preferentially use just one NAT64 box centrally placed rather than =
several (smaller) boxes at various edge locations.  I think this needs =
to be explained more clearly (assuming I have it right).  OTOH I would =
rather expect that most network owners would go for a single species of =
NAT64 box so the diversity of log formats is really a side issue.
>>=20
>> s5.2: The problem here is not specifically geo-location - and since =
we normally don't have any mapping between topology and location this =
seems inappropriate - but doing host identification (which is what RFC =
6967 is about.  Shouldn't this section just be about host =
identification?
>>=20
>> s8, para 2:
>>> We configure ULAs as NAT64 prefixes on a NAT64-CGN.
>> So.. is this a mandatory requirement or just a possibility?
>>=20
>> Nits/editorial comments:
>>=20
>> s1, para 1: s/Internet/the Internet/
>>=20
>> s1, para 2: s/simplify networks provisioning/simplify the =
provisioning of networks/, s/confers some benefits to/confers some =
benefits on/, s/such mobile/such a mobile/, s/if Long Term/if a Long =
Term/
>>=20
>> s3.1.1: s/can be seen with better transparency features/can offer =
improved transparency to <state who or what is offered the improved =
transparency> /
>>=20
>> s3.1.1: Expand A+P abbreviation.
>>=20
>> s3.3.1: s/IPv4 shortage/IPv4 address shortage/
>>=20
>> ss3.1.2, 3.1.3 and 3.1.4: These are very long paragraphs.  It would =
be good to separate the various discussion points into separate =
paragraphs.
>>=20
>> s3.1.2: "..to enable access of IPv4 only applications" Presumably =
this is access to applications running on the IPv4 side from =
applications on the IPV6 side... Suggest
>> "to allow applications running on the IPv6 network to interact with =
applications that can only use IPv4 communications or IPv6 applications =
that need to communicate using literal IPv4 addresses."
>>=20
>> s3.1.2: s/discover NAT64 prefix/discover the NAT64 prefix/
>>=20
>> s3.1.2: need a reference for BIND.
>>=20
>> s3.1.2: s/...(BIND) software supports the function./The ... (BIND) =
implementation of NAT64 supports this discovery function./
>>=20
>> s3.1.2:s/Operators should not/Users should not/ perhaps.
>>=20
>> s3.1.2: s/going to IPv4-only service/going to IPv4-only services/
>>=20
>> s3.1.2: s/restrains NAT uses/restrains NAT usage/
>>=20
>> s3.1.2: s/all traffic flows have to be traversed and translated./all =
traffic flows have to traverse the NAT44 middlebox and be translated =
there./
>>=20
>> s3.1.2: s/may serve a double roles, i.e. a translator and IPv6 =
forwarder./may serve a dual role acting as both translator and IPv6 =
forwarder./
>>=20
>> s3.1.2: s/Therefore, both IPv6 and IPv6
>>=20
>> s3.1.2:
>> OLD:
>> In some sense, it encourages IPv6 transmission and restrains NAT uses =
compared to NAT44(if used), on which all traffic flows have to be =
traversed and translated. In some cases, NAT64-CGN may serve double =
roles, i.e. a translator and IPv6 forwarder. In mobile networks, NAT64 =
is likely deployed as the default gateway serving for all the IPv6 =
traffic. The traffic heading to a dual-stack server is only forwarded on =
the NAT64. Therefore, both IPv6 and IPv4 are suggested to be configured =
on the Internet faced interfaces of NAT64. We tested on Top100 websites =
(referring to [Alexa] statistics). 43% of websites are connected and =
forwarded on the NAT64 since those websites have both AAAA and A =
records. With expansion of IPv6 supports, the translation process on =
NAT64 will likely be faded. In addition, it should be noted the =
DNS64-DNSSEC Interaction[RFC6147] may impact the DNS64 process. For =
example, DNS64 will not work with the case, where there is a DNS query =
with the "DNSSEC OK" (DO) bit set and the "Checking Disabled" (CD) bit =
set received.
>> NEW:
>> In some sense, it encourages IPv6 transmission and restrains NAT =
usage compared to system using NAT44 (if used), on which all traffic =
flows have to traverse the NAT44 middlebox and be translated in passing. =
In some cases, NAT64-CGN may serve a dual role as both translator and =
IPv6 forwarder. In mobile networks, NAT64 is likely deployed as the =
default gateway serving all the IPv6 traffic. The traffic heading to a =
dual-stack server is only forwarded via the NAT64. Therefore, it is =
suggested [or may be RECOMMENDED] that both IPv6 and IPv4 are configured =
on the Internet facing interfaces of NAT64 middleboxes.  We tested the =
configuration of the Top100 websites (as identified in the [Alexa] =
statistics).  43% of websites are [Should this be "would be"] connected =
and forwarded via NAT64 since those websites have both AAAA and A =
records. With the expansion of IPv6 support, the need for the =
translation process on NAT64 middleboxes will likely diminish. In =
addition, it should be noted that the interaction of DNS64 and DNSSEC =
[RFC6147] may impact the DNS64 process. For example, DNS64 will not work =
in the case where a DNS query is received that has the "DNSSEC OK" (DO) =
bit set and the "Checking Disabled" (CD) bit set.
>>=20
>>=20
>> s3.1.3: s/is problematic from multiple-vendor's equipment due to =
inconsistent formats of log records./obtained from equipment supplied by =
multiple vendors may be problematic due to inconsistent log formats./
>>=20
>> s3.1.3: This gave me a bit of a laugh...  So having got over my =
unstable user experience (probably due to excessive consumption of =
beer..)
>> OLD:
>>  Since the topology on each
>>  path is different, it may cause unstable user experiences and some
>>  degradation of Quality of Experience (QoE) when fallback to the =
other
>>  protocol is not powerful enough.
>> NEW:
>>  Since the routes taken by the two traffic sets may be different, =
user experiences
>>  may be inconsistent and there may be some
>>  degradation of Quality of Experience (QoE) when fallback to the =
other
>>  protocol is not sufficiently rapid. [or does this mean that the =
alternative route
>>  doesn't have enough capacity]
>>=20
>> Please clarify.
>>=20
>> [I gave up on language corrections at this point as it essentially =
needs a serious rewrite.]
>>=20
>> s4.1, last para: Specifying 91.21% of traffic seems inappropriately =
exact.
>>=20
>> s6.1:  It may well be that NAT64-CGN have an FTP ALG .. given the =
general view that FTP shouldn't be used it seems peculiar that this is =
the only default implementation!
>> Perhaps a comment about this (and maybe even TURNING OFF the FTP ALG) =
seems like an option.
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20


--Apple-Mail=_650FD774-AA6B-4143-B7A5-F336781D6A23
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 - http://gpgtools.org

iD8DBQFTBk94bjEdbHIsm0MRAmVeAKCaFRCUNpwSnzQdeTcRTIC/XA/t0ACfR0UT
0uS+nQV/DTVlLQzoRqrABBc=
=Vl3O
-----END PGP SIGNATURE-----

--Apple-Mail=_650FD774-AA6B-4143-B7A5-F336781D6A23--


From nobody Thu Feb 20 11:42:54 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 927841A024F; Thu, 20 Feb 2014 11:42:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nqkaMUPoeHSl; Thu, 20 Feb 2014 11:42:45 -0800 (PST)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 8A42D1A0252; Thu, 20 Feb 2014 11:42:45 -0800 (PST)
Received: by mail-pa0-f47.google.com with SMTP id kp14so2344575pab.20 for <multiple recipients>; Thu, 20 Feb 2014 11:42:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ClDMNxEKC/aM7Pzsu9g9Fi5ZUk6lkxCb4iKxeLBT7GY=; b=fQ5fuGCRxOqeZinBgR4oYc6+J4/jBJuIWywi4Zb/9xNkp52oN20sJKZzmcBfnG6d4z wPstGX6cHAwXhFSZdVLn/jinRFvvQiat2u7l2Hlz7Wna2vyQAx/qInufusAFribW+8bm 7KIe+yWem/oDwczpDiHYtgPcYLSnd0RpBsz/tdW1LJfA+2orFriA2cnrymT0qZGZM5xq EE+nP/bDUOogeGEghiMAX+gjf6psUcYCj0hNqjTj7oi9Qbf2SyOaV1Kd8b4Si8+kngTm 6cimUQWyKuzirsgY0r85nhvwCozTmA+USsc8Vp5fSBAhb4zn7QBcxtDCOVii2Rg9XF5J iYAA==
X-Received: by 10.68.130.169 with SMTP id of9mr4128887pbb.79.1392925361925; Thu, 20 Feb 2014 11:42:41 -0800 (PST)
Received: from [192.168.178.23] (189.201.69.111.dynamic.snap.net.nz. [111.69.201.189]) by mx.google.com with ESMTPSA id y9sm32134948pas.10.2014.02.20.11.42.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Feb 2014 11:42:41 -0800 (PST)
Message-ID: <53065AB9.8070400@gmail.com>
Date: Fri, 21 Feb 2014 08:42:49 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <52E83C75.7030909@dial.pipex.com> <0D2A7761-2C8D-41C7-8BC7-B4F175187F95@piuha.net> <A0D801AD-CD5A-4259-8BF5-85A105207217@piuha.net>
In-Reply-To: <A0D801AD-CD5A-4259-8BF5-85A105207217@piuha.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/8ZutlLLwpYAYnc9xoXlzkEHr2Js
Cc: General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-v6ops-nat64-experience.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 19:42:47 -0000

On 21/02/2014 05:56, Jari Arkko wrote:
...
>> The experiences of some
>>    applications are still align with [
>> RFC6586]. 
> 
> 
> Not sure what this means.

I assume it's a polite way of saying "As expected, a bunch
of applications don't work properly." Actually I don't think
it's a service to the community to say this indirectly -
anybody proposing to put users behind NAT64 needs to be well
informed about the FAILs.

     Brian


From nobody Thu Feb 20 14:19:01 2014
Return-Path: <daniel@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 7B2131A01DB for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 14:04:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xDdKZLkD4t9e for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 14:04:56 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 2848C1A0150 for <gen-art@ietf.org>; Thu, 20 Feb 2014 14:04:56 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1KM4oA1027328; Thu, 20 Feb 2014 22:04:50 GMT
Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1KM4npx027318 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Feb 2014 22:04:50 GMT
From: "Daniel King" <daniel@olddog.co.uk>
To: "'Joel M. Halpern'" <jmh@joelhalpern.com>
References: <526056C6.7060007@nostrum.com> <5260FFC8.7090602@joelhalpern.com>
In-Reply-To: <5260FFC8.7090602@joelhalpern.com>
Date: Thu, 20 Feb 2014 22:04:50 -0000
Message-ID: <02d801cf2e87$c6f373a0$54da5ae0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQFlbOx/bobLUaa+PgxYuF+lGMJ5EwHVWnW8m4OBN+A=
Content-Language: en-ca
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/_UduR_6z7sX_HjD79h51GCdXDiE
X-Mailman-Approved-At: Thu, 20 Feb 2014 14:18:59 -0800
Cc: adrian@olddog.co.uk, mpls-chairs@tools.ietf.org, gen-art@ietf.org, draft-ietf-mpls-ldp-multi-topology@tools.ietf.org
Subject: Re: [Gen-art] [mpls] Review: draft-ietf-mpls-ldp-multi-topology-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 22:04:58 -0000

Dear Joel, 

Thank you for your comments. 

We have updated the MPLS LDP MT draft and have clarified the Multi-Topology
Identifiers, figure 10 shows the initial MT-ID registry values:

http://tools.ietf.org/html/draft-ietf-mpls-ldp-multi-topology-11#section-9

We have also defined (and documented in the draft) that a new Internet-Draft
will be created to document the policy and process for allocating future
MT-IDs values from the LDP MT Name Space.

Re: Network byte order

The implementers chose the sequence format so that MT-ID was added
intentionally after IP Prefix to emphasise it as an extension to existing IP
Prefix. 

Br, Dan. 

-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Joel
M. Halpern
Sent: October 18, 2013 10:31 AM
To: A. Jean Mahoney
Cc: mpls@ietf.org; gen-art@ietf.org; IETF discussion list
Subject: [mpls] [Gen-art] Review: draft-ietf-mpls-ldp-multi-topology-09.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-mpls-ldp-multi-topology-09.txt
     LDP Extensions for Multi Topology Routing
Reviewer: Joel M. Halpern
Review Date: 18-October-2013
IETF LC End Date: 6-November-2013
IESG Telechat date: N/A

Summary: This document is nearly ready for publication as a Proposed
Standard RFC.  I believe there is one major issue that is easily addressed.

Major issues:
     I may have simply missed this reviewing the document, but as far as I
can tell there is no specification of the relationship between the MT-IDs in
this document and the MT-IDs used elsewhere.  Yes, I can take a guess at the
intent.  But is it stated somewhere that these are the same IDs negotiated
in the relevant IGP?  Or is there some other intent?

Minor issues:

Nits/editorial comments:
     I find it odd that the MT-ID follows the IP prefix in the various
formats.  Yes, the computer can parse both.  But since we tend to think in
Network byte order, I expect more significant information (MT-ID) to occur
before less significant information (IP prefix within topology.)
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls


From nobody Thu Feb 20 15:11:21 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 63A911A033B for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 15:11:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Sjx4hzXhQqR for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 15:11:16 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5368F1A0336 for <gen-art@ietf.org>; Thu, 20 Feb 2014 15:11:16 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s1KNB8w9009953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Thu, 20 Feb 2014 17:11:12 -0600 (CST) (envelope-from mahoney@nostrum.com)
Message-ID: <53068B8C.90901@nostrum.com>
Date: Thu, 20 Feb 2014 17:11:08 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/OGLKA4IhXEyJBsmkKfv1t8h3Chc
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-02-20
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Feb 2014 23:11:20 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Martin Thomson    2014-03-14   draft-drage-sipping-rfc3455bis-13

Meral Shirazipour 2014-02-28   draft-ietf-ecrit-trustworthy-location-08

Roni Even         2014-03-03   draft-ietf-mpls-special-purpose-labels-05

Robert Sparks     2014-03-12   draft-ietf-jcardcal-jcal-09

Scott Brim        2014-03-14   draft-vanelburg-dispatch-private-network-ind-05


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

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:



From nobody Thu Feb 20 17:12:38 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 215831A039B for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 17:12:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ICZvrMB-jb9V for <gen-art@ietfa.amsl.com>; Thu, 20 Feb 2014 17:12:34 -0800 (PST)
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 5E6551A0396 for <gen-art@ietf.org>; Thu, 20 Feb 2014 17:12:34 -0800 (PST)
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 1WGefD-0006ns-3U; Fri, 21 Feb 2014 01:12:27 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Russ Housley <housley@vigilsec.com>
In-Reply-To: <E87A560B-EC79-432C-9D7F-E25079D4EE2A@vigilsec.com>
References: <52E83C75.7030909@dial.pipex.com> <E87A560B-EC79-432C-9D7F-E25079D4EE2A@vigilsec.com>
Content-Type: text/plain
Date: Fri, 21 Feb 2014 01:12:25 +0000
Message-Id: <1392945145.8036.158.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/N_a-x6_XpjNzvd7GTGGuGSqB864
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-v6ops-nat64-experience.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 01:12:37 -0000

On Thu, 2014-02-20 at 09:46 -0500, Russ Housley wrote:
> Elwyn:
> 
> Nice review.  I'm sure the document will be improved because of your
> efforts. 
:-)

 I'd like to make two comments.
> 
> > s3.1.3: It is stated that placing the NAT64 (middlebox) in a
> centralized location would 'reduce the diversity of  log format'.  I
> guess what is possibly being said that is that the network should
> preferentially use just one NAT64 box centrally placed rather than
> several (smaller) boxes at various edge locations.  I think this needs
> to be explained more clearly (assuming I have it right).  OTOH I would
> rather expect that most network owners would go for a single species
> of NAT64 box so the diversity of log formats is really a side issue.
> 
> In the beginning, yes.  Subsequent procurements cal lead to changing
> vendor.  Mergers also lead to multiple venders.
For sure! And of course you then have to decide whether to modify the 
merged network to conform to the centralized location story.  A little
clarification is, I believe, needed to cover all the bases.
> 
> > s5.2: The problem here is not specifically geo-location - and since
> we normally don't have any mapping between topology and location this
> seems inappropriate - but doing host identification (which is what RFC
> 6967 is about.  Shouldn't this section just be about host
> identification?
> 
> If a law enforcement agency shows up with a subpoena, they really do
> want to know what door to knock down.
Maybe I'd prefer my operator not to know which door - with wi-fi
involved there is no guarantee which door the host is behind in any
case.  It's an interesting point that I had not thought about: Does my
ISP in the UK actually get to know whether the phone number I am paying
for service on is at the same address as on the bills?  Since I provide
my own modem and the ISP has, to the best of my knowledge, never been
near either my house or the exchange where my ADSL line terminates it
depends on whether BT checks the linkage and tells the ISP it is right.
It's so long since I signed up I have no idea what would have happened
if the addresses didn't match. Another PRIVACY issue!

/Elwyn 
> 
> Thanks for listening,
>   Russ
> 


From nobody Fri Feb 21 04:33:04 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 B02CF1A0039; Fri, 21 Feb 2014 04:32:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 2Ih4rBB1W6Mv; Fri, 21 Feb 2014 04:32:46 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CE2B41A002B; Fri, 21 Feb 2014 04:32:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 543402CEB5; Fri, 21 Feb 2014 14:32:40 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPYYpcMRJT_p; Fri, 21 Feb 2014 14:32:39 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3D6A82CC5D; Fri, 21 Feb 2014 14:32:39 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAM+vMEQh_Mgjhp3u07CxFAOyR3wkTf+8hepx14ubWOf+bjEqgA@mail.gmail.com>
Date: Fri, 21 Feb 2014 13:32:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <67462D7E-6E00-45E8-A246-7A7447908116@piuha.net>
References: <52E83C75.7030909@dial.pipex.com> <0D2A7761-2C8D-41C7-8BC7-B4F175187F95@piuha.net> <A0D801AD-CD5A-4259-8BF5-85A105207217@piuha.net> <CAM+vMEQh_Mgjhp3u07CxFAOyR3wkTf+8hepx14ubWOf+bjEqgA@mail.gmail.com>
To: GangChen <phdgang@gmail.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/pfzOBzwY_sF9fBYRTBAmKkzT99s
Cc: General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-v6ops-nat64-experience.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 12:32:58 -0000

Hi,

First: I cleared my discuss, so this document's progress is now up to =
you guys and Joel. Some further discussion inline:

> 4-02-21 0:56 GMT+08:00, Jari Arkko <jari.arkko@piuha.net>:
>> FWIW, I have now done my own review. I think there are language =
issues, but
>> they do not prevent going forward. Language itself will be fixed by =
the RFC
>> Editor. I'm more interested in cases where there might be an =
semantics
>> unclarity issue.
>>=20
>> I think it would be beneficial to go through each of the comments =
before
>> final approval of the document.
>>=20
>> With that in mind, going through some of my own and Elwyn's comments:
>>=20
>>>   o  Operators who adopt NAT64-FE may leverage the application layer
>>>      proxies, e.g. X-Forwarded-For (XFF)
>>>      [
>>> I-D.ietf-appsawg-http-forwarded
>>> ], to convey the IPv6 source
>>>      address in HTTP headers.
>>=20
>> I'd say ... may leverage application layer proxies, and those may use
>> additional attributes such as X-Forwarded-For ...
>=20
>>=20
>>> Those messages would be passed on to
>>>      web-servers.  The log parsing tools are required to be able to
>>>      support IPv6 and may lookup Radius servers for the target
>>>      subscribers based on IPv6 addresses included in XFF HTTP =
headers.
>>>      XFF is the de facto standard which has been integrated in most
>>>      Load Balancers.  Therefore, it may be superior to use in a =
NAT-FE
>>>      environment.  In the downsides, XFF is specific to HTTP.  It
>>>      restricts the usages so that the solution can't be applied to
>>>      requests made over HTTPs.  This makes geo-location problematic =
for
>>>      HTTPs based services.
>>>=20
>>=20
>> Not sure we should call something a de facto standard while pointing =
to a
>> draft. I'd just say "... has been implemented in many ..."
>=20
> thank you for the suggestion. We will make following changes:
>=20
> =3D=3DNEW
>=20
>   o  Operators who adopt NAT64-FE may leverage the application layer
>      proxies. Those may use additional attributes such as =
X-Forwarded-For (XFF)
>      [I-D.ietf-appsawg-http-forwarded] to convey the IPv6 source
>      address in HTTP headers.  Those messages would be passed on to
>      web-servers.  The log parsing tools are required to be able to
>      support IPv6 and may lookup Radius servers for the target
>      subscribers based on IPv6 addresses included in XFF HTTP headers.
>      XFF has been implemented in most Load Balancers.  Therefore,
>      it may be superior to use in a NAT-FE
>      environment.  In the downsides, XFF is specific to HTTP.  It
>      restricts the usages so that the solution can't be applied to
>      requests made over HTTPs.  This makes geo-location problematic =
for
>      HTTPs based services.

OK

>=20
>=20
>=20
>>> The experiences of some
>>>   applications are still align with [
>>> RFC6586].
>>=20
>>=20
>> Not sure what this means.
>=20
> Several applications don't work properly as described in the RFC6585.

If you use that text, then it would be fine.

>=20
>>=20
>>=20
>>> |  SIP-VoIP      |Fail, due to the lack of NAT64 traversal           =
 |
>>>=20
>>=20
>> Did you mean ALG? Not sure what this would mean otherwise.
>=20
> I mean ICE is recommended to be supported in order to avoid SIP-ALG.
> After the discussion with Dan Wing, resorting to SIP-ALG for
> supporting IPv4-IPv6 inter-working is not preferred.

Ok. Please elaborate, because the text was unclear to the reader.

Also, I think you should go through Elwyn's comments and see if you make =
improvements.

Jari


From nobody Fri Feb 21 05:39:20 2014
Return-Path: <phdgang@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 607491A04F7 for <gen-art@ietfa.amsl.com>; Fri, 21 Feb 2014 01:14:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d3-TrAjcaqtu for <gen-art@ietfa.amsl.com>; Fri, 21 Feb 2014 01:14:29 -0800 (PST)
Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id DB4271A0041 for <gen-art@ietf.org>; Fri, 21 Feb 2014 01:14:28 -0800 (PST)
Received: by mail-qc0-f180.google.com with SMTP id i17so5384103qcy.25 for <gen-art@ietf.org>; Fri, 21 Feb 2014 01:14:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wwndgNU0oFPZ4u3yiBUTmo74WCYN0I7tUipwYByK/YA=; b=uAr9WGiHcuZopeSRcqFj6hqGvu+TKDn6zvh5AlVvZ6mXaMzcLDaCdqO3Kl3pjCZnSG idXui14SPV5v5NGtH1JEkLWWnyUo0F4QeZ+yK9uKk05MCSRTsBk3xr/CqootQUgbAaP9 JOlvGD1OpJn5IWmNHFSYzE2bunuToKHek4JUU70n+G2DCH9/mkHV1DdlJwp2z0ok0H2V IyfzD8AZfq2TDUfN0zZbDgf3EXxzEwuguWoKeIHsdJTqP8QG998KXHBbpaWkm9vvzGHs F595ZwEiXt5XJVWWDju86GGKMF2B9BeOGemVOTBhfRl8Uk8hhggfxrvhWQvknlJjylKr ZUVg==
MIME-Version: 1.0
X-Received: by 10.224.115.78 with SMTP id h14mr8169994qaq.94.1392974064753; Fri, 21 Feb 2014 01:14:24 -0800 (PST)
Received: by 10.224.51.137 with HTTP; Fri, 21 Feb 2014 01:14:24 -0800 (PST)
In-Reply-To: <52E83C75.7030909@dial.pipex.com>
References: <52E83C75.7030909@dial.pipex.com>
Date: Fri, 21 Feb 2014 17:14:24 +0800
Message-ID: <CAM+vMETtsxOoJyWPgYKzOgZWxKULh7NGJctf+xA=qFQ2ZHerAw@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/KLhWTLfBJl0JSEcKDZU7Aj7iG4k
X-Mailman-Approved-At: Fri, 21 Feb 2014 05:39:18 -0800
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-v6ops-nat64-experience.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 09:14:32 -0000

Hi Elwyn,

Thank you for the comments.
I apologize for the late reply due to some personal reasons.
Please see my reply inline.

2014-01-29 7:25 GMT+08:00, Elwyn Davies <elwynd@dial.pipex.com>:
>
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-v6ops-nat64-experience-09.txt
> Reviewer: Elwyn Davies
> Review Date: 28 January 2014
> IETF LC End Date: 28 January 2014
> IESG Telechat date: (if known) -
>
> Summary:
> Not ready.  This document needs a serious rewrite with the assistance of
> a mother tongue English speaker.  I started doing some of this getting
> as far as s3.1.4, however I came to the conclusion that significant
> parts of the language were sufficiently unclear that I was unable to
> determine the intended meaning.  Accordingly I have abandoned the review
> and will have another go assuming a rewrite is done.  Please consider
> whether the title should be modified as noted below.

I'm an ESL person. I have incorporated editorial suggestions from the
kind working group. We could improve the writing quality with your
comments.


> Major issues:
>
> Minor issues:
> Title:  The title is rather misleading since it the document actually
> documents two suggested ways of deploying NAT64 as well as experience of
> deploying these solutions. Maybe 'NAT64 Deployment Options and Experience'.

I agree with your comments that the title is more accurate as "NAT64
Deployment Options and Experience".

> s1: A reference to explain what PDP context etc means in an LTE
> environment would be useful.

 As stated in RFC6459,
 "A Packet Data Protocol (PDP) context is the equivalent of a
 virtual connection between the User Equipment (UE) and a PDN using
 a specific gateway."

We could add the reference of RFC6459 when the PDP is first shown in the draft.

> s3.1.3: It is stated that placing the NAT64 (middlebox) in a centralized
> location would 'reduce the diversity of  log format'.  I guess what is
> possibly being said that is that the network should preferentially use
> just one NAT64 box centrally placed rather than several (smaller) boxes
> at various edge locations.  I think this needs to be explained more
> clearly (assuming I have it right).  OTOH I would rather expect that
> most network owners would go for a single species of NAT64 box so the
> diversity of log formats is really a side issue.

Your understanding is correct. One single species is desirable.
A centralized NAT64 box is easier for operators to just use a single species.

we will make following changes:

===OLD

   It has been observed that the
   process of correlating log information is problematic from multiple-
   vendor's equipment due to inconsistent formats of log records.
   Placing NAT64 in a centralized location may reduce diversity of log
   format and simplify the network provisioning.

===NEW

   It has been observed that the
   process of correlating log information is problematic from multiple-
   vendor's equipment due to inconsistent formats of log records.
   Placing NAT64 in a centralized location may be beneficial
   to operators to use a single species of NAT64 that reduces diversity of log
   format and simplify the provisioning of networks.


> s5.2: The problem here is not specifically geo-location - and since we
> normally don't have any mapping between topology and location this seems
> inappropriate - but doing host identification (which is what RFC 6967 is
> about.  Shouldn't this section just be about host identification?

There are some use cases to determine user's location depending on
IPv6 address, for example lawful interception and navigation services.
In my experience, the information of network topology and relevant
locations is required to be provided to lawful agency. Map apps can
also get user's location information in order to provide navigation
service. IPv6 is good for such usages, since it has global meaning.

> s8, para 2:
>> We configure ULAs as NAT64 prefixes on a NAT64-CGN.
> So.. is this a mandatory requirement or just a possibility?

It's just a possibility. It actually just describes a test which
evaluates the impact of using ULA.


> Nits/editorial comments:
>
> s1, para 1: s/Internet/the Internet/
>
> s1, para 2: s/simplify networks provisioning/simplify the provisioning
> of networks/, s/confers some benefits to/confers some benefits on/,
> s/such mobile/such a mobile/, s/if Long Term/if a Long Term/
>
> s3.1.1: s/can be seen with better transparency features/can offer
> improved transparency to <state who or what is offered the improved
> transparency> /
>
> s3.1.1: Expand A+P abbreviation.
>
> s3.3.1: s/IPv4 shortage/IPv4 address shortage/
>
> ss3.1.2, 3.1.3 and 3.1.4: These are very long paragraphs.  It would be
> good to separate the various discussion points into separate paragraphs.
>
> s3.1.2: "..to enable access of IPv4 only applications" Presumably this
> is access to applications running on the IPv4 side from applications on
> the IPV6 side... Suggest
> "to allow applications running on the IPv6 network to interact with
> applications that can only use IPv4 communications or IPv6 applications
> that need to communicate using literal IPv4 addresses."
>
> s3.1.2: s/discover NAT64 prefix/discover the NAT64 prefix/
>
> s3.1.2: need a reference for BIND.
>
> s3.1.2: s/...(BIND) software supports the function./The ... (BIND)
> implementation of NAT64 supports this discovery function./
>
> s3.1.2:s/Operators should not/Users should not/ perhaps.
>
> s3.1.2: s/going to IPv4-only service/going to IPv4-only services/
>
> s3.1.2: s/restrains NAT uses/restrains NAT usage/
>
> s3.1.2: s/all traffic flows have to be traversed and translated./all
> traffic flows have to traverse the NAT44 middlebox and be translated
> there./
>
> s3.1.2: s/may serve a double roles, i.e. a translator and IPv6
> forwarder./may serve a dual role acting as both translator and IPv6
> forwarder./
>
> s3.1.2: s/Therefore, both IPv6 and IPv6
>
> s3.1.2:
> OLD:
> In some sense, it encourages IPv6 transmission and restrains NAT uses
> compared to NAT44(if used), on which all traffic flows have to be
> traversed and translated. In some cases, NAT64-CGN may serve double
> roles, i.e. a translator and IPv6 forwarder. In mobile networks, NAT64
> is likely deployed as the default gateway serving for all the IPv6
> traffic. The traffic heading to a dual-stack server is only forwarded on
> the NAT64. Therefore, both IPv6 and IPv4 are suggested to be configured
> on the Internet faced interfaces of NAT64. We tested on Top100 websites
> (referring to [Alexa] statistics). 43% of websites are connected and
> forwarded on the NAT64 since those websites have both AAAA and A
> records. With expansion of IPv6 supports, the translation process on
> NAT64 will likely be faded. In addition, it should be noted the
> DNS64-DNSSEC Interaction[RFC6147] may impact the DNS64 process. For
> example, DNS64 will not work with the case, where there is a DNS query
> with the "DNSSEC OK" (DO) bit set and the "Checking Disabled" (CD) bit
> set received.
> NEW:
> In some sense, it encourages IPv6 transmission and restrains NAT usage
> compared to system using NAT44 (if used), on which all traffic flows
> have to traverse the NAT44 middlebox and be translated in passing. In
> some cases, NAT64-CGN may serve a dual role as both translator and IPv6
> forwarder. In mobile networks, NAT64 is likely deployed as the default
> gateway serving all the IPv6 traffic. The traffic heading to a
> dual-stack server is only forwarded via the NAT64. Therefore, it is
> suggested [or may be RECOMMENDED] that both IPv6 and IPv4 are configured
> on the Internet facing interfaces of NAT64 middleboxes.  We tested the
> configuration of the Top100 websites (as identified in the [Alexa]
> statistics).  43% of websites are [Should this be "would be"] connected
> and forwarded via NAT64 since those websites have both AAAA and A
> records. With the expansion of IPv6 support, the need for the
> translation process on NAT64 middleboxes will likely diminish. In
> addition, it should be noted that the interaction of DNS64 and DNSSEC
> [RFC6147] may impact the DNS64 process. For example, DNS64 will not work
> in the case where a DNS query is received that has the "DNSSEC OK" (DO)
> bit set and the "Checking Disabled" (CD) bit set.
>
>
> s3.1.3: s/is problematic from multiple-vendor's equipment due to
> inconsistent formats of log records./obtained from equipment supplied by
> multiple vendors may be problematic due to inconsistent log formats./

Thank you for the detailed suggestion. I have already updated my local
copy with your suggestion. It will be updated along with new editorial
improvement.

> s3.1.3: This gave me a bit of a laugh...  So having got over my unstable
> user experience (probably due to excessive consumption of beer..)
> OLD:
>     Since the topology on each
>     path is different, it may cause unstable user experiences and some
>     degradation of Quality of Experience (QoE) when fallback to the other
>     protocol is not powerful enough.
> NEW:
>     Since the routes taken by the two traffic sets may be different,
> user experiences
>     may be inconsistent and there may be some
>     degradation of Quality of Experience (QoE) when fallback to the other
>     protocol is not sufficiently rapid. [or does this mean that the
> alternative route
>     doesn't have enough capacity]
>
> Please clarify.

It means the alternative route may have less capacity or lower speed.


> [I gave up on language corrections at this point as it essentially needs
> a serious rewrite.]
>
> s4.1, last para: Specifying 91.21% of traffic seems inappropriately exact.

The discussion in the wg encourage us to share the concrete data for
the statement.
The statistic is also verified by several mobile operators.


> s6.1:  It may well be that NAT64-CGN have an FTP ALG .. given the
> general view that FTP shouldn't be used it seems peculiar that this is
> the only default implementation!
> Perhaps a comment about this (and maybe even TURNING OFF the FTP ALG)
> seems like an option.

The recommendation of avoidance of FTP-ALG use align with RFC6384.

Best Regards

Gang
>
>
>
>


From nobody Fri Feb 21 05:39:22 2014
Return-Path: <phdgang@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 745091A050A for <gen-art@ietfa.amsl.com>; Fri, 21 Feb 2014 01:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yNd5Dof48yxM for <gen-art@ietfa.amsl.com>; Fri, 21 Feb 2014 01:27:12 -0800 (PST)
Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) by ietfa.amsl.com (Postfix) with ESMTP id AD6CB1A04F8 for <gen-art@ietf.org>; Fri, 21 Feb 2014 01:27:12 -0800 (PST)
Received: by mail-qg0-f47.google.com with SMTP id 63so6973674qgz.6 for <gen-art@ietf.org>; Fri, 21 Feb 2014 01:27:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sBYfvQrIzQ/RHXmiT/C2VysUpMeqnjcybJz6goWzRxk=; b=d2EBEXvYwhKkzlMAocBFoJ4/GrKiqy0BsaQweuP66T6Ht4vXYJNdGS7vDl1AiodMxy cG1LCzcWgI2WQHZgSfKAw1SOJIbYJS12iSma6TLz02RoSzZWPzwC9n/pstTb9DwfXWrj M1//hOfoSkV8TFzwDXw+7Zf2GkNcuZwPSYDk3xAtfGljz3+uasRgRbBPgyf24YTOGEdA nhWmdtoSTJqs+TgFBqnXbdE8W2sJxJDVBA4enNG7akQ0k8+1bejAXDK+AeD9lFa4zaLV Qo1nozXr/u/gUnea+zyA0SM43fkbfOWWLLu5pDU2K1TA8QwaMXO7svJY85Z26zt5xALc gVKQ==
MIME-Version: 1.0
X-Received: by 10.140.49.9 with SMTP id p9mr7657654qga.75.1392974828744; Fri, 21 Feb 2014 01:27:08 -0800 (PST)
Received: by 10.224.51.137 with HTTP; Fri, 21 Feb 2014 01:27:08 -0800 (PST)
In-Reply-To: <E87A560B-EC79-432C-9D7F-E25079D4EE2A@vigilsec.com>
References: <52E83C75.7030909@dial.pipex.com> <E87A560B-EC79-432C-9D7F-E25079D4EE2A@vigilsec.com>
Date: Fri, 21 Feb 2014 17:27:08 +0800
Message-ID: <CAM+vMESJY0ERRVJq-wDiwxTFy1jXLFy0CHwiU1FcXv2QdyfHxQ@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/tbbMKri7O8XLgZy1sOB-orQQVlc
X-Mailman-Approved-At: Fri, 21 Feb 2014 05:39:18 -0800
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-v6ops-nat64-experience.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 09:27:14 -0000

2014-02-20 22:46 GMT+08:00, Russ Housley <housley@vigilsec.com>:
> Elwyn:
>
> Nice review.  I'm sure the document will be improved because of your
> efforts.  I'd like to make two comments.
>
>> s3.1.3: It is stated that placing the NAT64 (middlebox) in a centralized
>> location would 'reduce the diversity of  log format'.  I guess what is
>> possibly being said that is that the network should preferentially use
>> just one NAT64 box centrally placed rather than several (smaller) boxes at
>> various edge locations.  I think this needs to be explained more clearly
>> (assuming I have it right).  OTOH I would rather expect that most network
>> owners would go for a single species of NAT64 box so the diversity of log
>> formats is really a side issue.
>
> In the beginning, yes.  Subsequent procurements cal lead to changing vendor.
>  Mergers also lead to multiple venders.

The procurement for more capacity of equipment(e.g. add board card)
still could avoid multi-vendor coordination. The procurement for new
equipment leads multiple vendor. However, it earns the time to improve
implementation.

BRs

Gang

>
>> s5.2: The problem here is not specifically geo-location - and since we
>> normally don't have any mapping between topology and location this seems
>> inappropriate - but doing host identification (which is what RFC 6967 is
>> about.  Shouldn't this section just be about host identification?
>
> If a law enforcement agency shows up with a subpoena, they really do want to
> know what door to knock down.
>
> Thanks for listening,
>   Russ
>
>


From nobody Fri Feb 21 05:39:24 2014
Return-Path: <phdgang@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 92A5C1A043D; Fri, 21 Feb 2014 01:59:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZC-pSc6MMMKw; Fri, 21 Feb 2014 01:59:19 -0800 (PST)
Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF8C1A0436; Fri, 21 Feb 2014 01:59:19 -0800 (PST)
Received: by mail-qg0-f46.google.com with SMTP id e89so7052469qgf.5 for <multiple recipients>; Fri, 21 Feb 2014 01:59:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LDoOuW78Kk98ovZDh1TU3WH6kdmuroCQPFttSGejBXs=; b=UJ+jhiVPc4pmzNp7jyeMC9dmpV3K66lhubWWlrR5AEy4In+kBWZ1GgmOfLpdqTx3Xa 6MDiLHTJZSTTincXGp6cNdPwGcnFDoEFq0ZS+v5a3FB+cXW5fkmPDRk0FhY6VFAail8M Z7U4IYh1euPh9wuysM9mbvtS5ucf5qRSU8Mu8kFrAApa4I7IvVPss4PW4NGKf8dYpoau HPY6A2RLXjI5FDQbKF6qa8Km9AJkY9821arv9DpM919I+9A+Pkris214wPtPcz6m66rC l/nnRSIFvRadKRKUgAnmI+kSwY/VhYkpaNWXwlgTiqOEO5ZC5XZuddFDGeXhu2olaiV4 6ZIA==
MIME-Version: 1.0
X-Received: by 10.229.172.4 with SMTP id j4mr8445548qcz.6.1392976755281; Fri, 21 Feb 2014 01:59:15 -0800 (PST)
Received: by 10.224.51.137 with HTTP; Fri, 21 Feb 2014 01:59:15 -0800 (PST)
In-Reply-To: <A0D801AD-CD5A-4259-8BF5-85A105207217@piuha.net>
References: <52E83C75.7030909@dial.pipex.com> <0D2A7761-2C8D-41C7-8BC7-B4F175187F95@piuha.net> <A0D801AD-CD5A-4259-8BF5-85A105207217@piuha.net>
Date: Fri, 21 Feb 2014 17:59:15 +0800
Message-ID: <CAM+vMEQh_Mgjhp3u07CxFAOyR3wkTf+8hepx14ubWOf+bjEqgA@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/ANpkLezh1_rVjX3FkfQ-6k6wPGM
X-Mailman-Approved-At: Fri, 21 Feb 2014 05:39:18 -0800
Cc: General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-v6ops-nat64-experience.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 09:59:22 -0000

Hello Jari,

Thank you for the comments. Please see my reply inline.


2014-02-21 0:56 GMT+08:00, Jari Arkko <jari.arkko@piuha.net>:
> FWIW, I have now done my own review. I think there are language issues, but
> they do not prevent going forward. Language itself will be fixed by the RFC
> Editor. I'm more interested in cases where there might be an semantics
> unclarity issue.
>
> I think it would be beneficial to go through each of the comments before
> final approval of the document.
>
> With that in mind, going through some of my own and Elwyn's comments:
>
>>    o  Operators who adopt NAT64-FE may leverage the application layer
>>       proxies, e.g. X-Forwarded-For (XFF)
>>       [
>> I-D.ietf-appsawg-http-forwarded
>> ], to convey the IPv6 source
>>       address in HTTP headers.
>
> I'd say ... may leverage application layer proxies, and those may use
> additional attributes such as X-Forwarded-For ...

>
>> Those messages would be passed on to
>>       web-servers.  The log parsing tools are required to be able to
>>       support IPv6 and may lookup Radius servers for the target
>>       subscribers based on IPv6 addresses included in XFF HTTP headers.
>>       XFF is the de facto standard which has been integrated in most
>>       Load Balancers.  Therefore, it may be superior to use in a NAT-FE
>>       environment.  In the downsides, XFF is specific to HTTP.  It
>>       restricts the usages so that the solution can't be applied to
>>       requests made over HTTPs.  This makes geo-location problematic for
>>       HTTPs based services.
>>
>
> Not sure we should call something a de facto standard while pointing to a
> draft. I'd just say "... has been implemented in many ..."

thank you for the suggestion. We will make following changes:

==NEW

   o  Operators who adopt NAT64-FE may leverage the application layer
      proxies. Those may use additional attributes such as X-Forwarded-For (XFF)
      [I-D.ietf-appsawg-http-forwarded] to convey the IPv6 source
      address in HTTP headers.  Those messages would be passed on to
      web-servers.  The log parsing tools are required to be able to
      support IPv6 and may lookup Radius servers for the target
      subscribers based on IPv6 addresses included in XFF HTTP headers.
      XFF has been implemented in most Load Balancers.  Therefore,
      it may be superior to use in a NAT-FE
      environment.  In the downsides, XFF is specific to HTTP.  It
      restricts the usages so that the solution can't be applied to
      requests made over HTTPs.  This makes geo-location problematic for
      HTTPs based services.



>> The experiences of some
>>    applications are still align with [
>> RFC6586].
>
>
> Not sure what this means.

Several applications don't work properly as described in the RFC6585.

>
>
>> |  SIP-VoIP      |Fail, due to the lack of NAT64 traversal            |
>>
>
> Did you mean ALG? Not sure what this would mean otherwise.

I mean ICE is recommended to be supported in order to avoid SIP-ALG.
After the discussion with Dan Wing, resorting to SIP-ALG for
supporting IPv4-IPv6 inter-working is not preferred.

BRs

Gang

>
>>> Minor issues:
>>> Title:  The title is rather misleading since it the document actually
>>> documents two suggested ways of deploying NAT64 as well as experience of
>>> deploying these solutions. Maybe 'NAT64 Deployment Options and
>>> Experience'.
>
> I think that is a reasonable suggestion.
>
>>>
>>> s1: A reference to explain what PDP context etc means in an LTE
>>> environment would be useful.
>>>
>>> s3.1.3: It is stated that placing the NAT64 (middlebox) in a centralized
>>> location would 'reduce the diversity of  log format'.  I guess what is
>>> possibly being said that is that the network should preferentially use
>>> just one NAT64 box centrally placed rather than several (smaller) boxes
>>> at various edge locations.  I think this needs to be explained more
>>> clearly (assuming I have it right).  OTOH I would rather expect that most
>>> network owners would go for a single species of NAT64 box so the
>>> diversity of log formats is really a side issue.
>>>
>>> s5.2: The problem here is not specifically geo-location - and since we
>>> normally don't have any mapping between topology and location this seems
>>> inappropriate - but doing host identification (which is what RFC 6967 is
>>> about.  Shouldn't this section just be about host identification?
>>>
>>> s8, para 2:
>>>> We configure ULAs as NAT64 prefixes on a NAT64-CGN.
>>> So.. is this a mandatory requirement or just a possibility?
>>>
>>> Nits/editorial comments:
>>>
>>> s1, para 1: s/Internet/the Internet/
>>>
>>> s1, para 2: s/simplify networks provisioning/simplify the provisioning of
>>> networks/, s/confers some benefits to/confers some benefits on/, s/such
>>> mobile/such a mobile/, s/if Long Term/if a Long Term/
>>>
>>> s3.1.1: s/can be seen with better transparency features/can offer
>>> improved transparency to <state who or what is offered the improved
>>> transparency> /
>>>
>>> s3.1.1: Expand A+P abbreviation.
>>>
>>> s3.3.1: s/IPv4 shortage/IPv4 address shortage/
>>>
>>> ss3.1.2, 3.1.3 and 3.1.4: These are very long paragraphs.  It would be
>>> good to separate the various discussion points into separate paragraphs.
>>>
>>> s3.1.2: "..to enable access of IPv4 only applications" Presumably this is
>>> access to applications running on the IPv4 side from applications on the
>>> IPV6 side... Suggest
>>> "to allow applications running on the IPv6 network to interact with
>>> applications that can only use IPv4 communications or IPv6 applications
>>> that need to communicate using literal IPv4 addresses."
>>>
>>> s3.1.2: s/discover NAT64 prefix/discover the NAT64 prefix/
>>>
>>> s3.1.2: need a reference for BIND.
>>>
>>> s3.1.2: s/...(BIND) software supports the function./The ... (BIND)
>>> implementation of NAT64 supports this discovery function./
>>>
>>> s3.1.2:s/Operators should not/Users should not/ perhaps.
>>>
>>> s3.1.2: s/going to IPv4-only service/going to IPv4-only services/
>>>
>>> s3.1.2: s/restrains NAT uses/restrains NAT usage/
>>>
>>> s3.1.2: s/all traffic flows have to be traversed and translated./all
>>> traffic flows have to traverse the NAT44 middlebox and be translated
>>> there./
>>>
>>> s3.1.2: s/may serve a double roles, i.e. a translator and IPv6
>>> forwarder./may serve a dual role acting as both translator and IPv6
>>> forwarder./
>>>
>>> s3.1.2: s/Therefore, both IPv6 and IPv6
>>>
>>> s3.1.2:
>>> OLD:
>>> In some sense, it encourages IPv6 transmission and restrains NAT uses
>>> compared to NAT44(if used), on which all traffic flows have to be
>>> traversed and translated. In some cases, NAT64-CGN may serve double
>>> roles, i.e. a translator and IPv6 forwarder. In mobile networks, NAT64 is
>>> likely deployed as the default gateway serving for all the IPv6 traffic.
>>> The traffic heading to a dual-stack server is only forwarded on the
>>> NAT64. Therefore, both IPv6 and IPv4 are suggested to be configured on
>>> the Internet faced interfaces of NAT64. We tested on Top100 websites
>>> (referring to [Alexa] statistics). 43% of websites are connected and
>>> forwarded on the NAT64 since those websites have both AAAA and A records.
>>> With expansion of IPv6 supports, the translation process on NAT64 will
>>> likely be faded. In addition, it should be noted the DNS64-DNSSEC
>>> Interaction[RFC6147] may impact the DNS64 process. For example, DNS64
>>> will not work with the case, where there is a DNS query with the "DNSSEC
>>> OK" (DO) bit set and the "Checking Disabled" (CD) bit set received.
>>> NEW:
>>> In some sense, it encourages IPv6 transmission and restrains NAT usage
>>> compared to system using NAT44 (if used), on which all traffic flows have
>>> to traverse the NAT44 middlebox and be translated in passing. In some
>>> cases, NAT64-CGN may serve a dual role as both translator and IPv6
>>> forwarder. In mobile networks, NAT64 is likely deployed as the default
>>> gateway serving all the IPv6 traffic. The traffic heading to a dual-stack
>>> server is only forwarded via the NAT64. Therefore, it is suggested [or
>>> may be RECOMMENDED] that both IPv6 and IPv4 are configured on the
>>> Internet facing interfaces of NAT64 middleboxes.  We tested the
>>> configuration of the Top100 websites (as identified in the [Alexa]
>>> statistics).  43% of websites are [Should this be "would be"] connected
>>> and forwarded via NAT64 since those websites have both AAAA and A
>>> records. With the expansion of IPv6 support, the need for the translation
>>> process on NAT64 middleboxes will likely diminish. In addition, it should
>>> be noted that the interaction of DNS64 and DNSSEC [RFC6147] may impact
>>> the DNS64 process. For example, DNS64 will not work in the case where a
>>> DNS query is received that has the "DNSSEC OK" (DO) bit set and the
>>> "Checking Disabled" (CD) bit set.
>>>
>>>
>>> s3.1.3: s/is problematic from multiple-vendor's equipment due to
>>> inconsistent formats of log records./obtained from equipment supplied by
>>> multiple vendors may be problematic due to inconsistent log formats./
>>>
>>> s3.1.3: This gave me a bit of a laugh...  So having got over my unstable
>>> user experience (probably due to excessive consumption of beer..)
>>> OLD:
>>>  Since the topology on each
>>>  path is different, it may cause unstable user experiences and some
>>>  degradation of Quality of Experience (QoE) when fallback to the other
>>>  protocol is not powerful enough.
>>> NEW:
>>>  Since the routes taken by the two traffic sets may be different, user
>>> experiences
>>>  may be inconsistent and there may be some
>>>  degradation of Quality of Experience (QoE) when fallback to the other
>>>  protocol is not sufficiently rapid. [or does this mean that the
>>> alternative route
>>>  doesn't have enough capacity]
>
> Yes, that would be better.
>
>>>
>>> Please clarify.
>>>
>>> [I gave up on language corrections at this point as it essentially needs
>>> a serious rewrite.]
>>>
>>> s4.1, last para: Specifying 91.21% of traffic seems inappropriately
>>> exact.
>>>
>>> s6.1:  It may well be that NAT64-CGN have an FTP ALG .. given the general
>>> view that FTP shouldn't be used it seems peculiar that this is the only
>>> default implementation!
>>> Perhaps a comment about this (and maybe even TURNING OFF the FTP ALG)
>>> seems like an option.
>
>
> Jari
>
>


From nobody Fri Feb 21 07:15:05 2014
Return-Path: <joelja@bogus.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 A1A461A01AB; Fri, 21 Feb 2014 07:15:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 aqu-8emLz3VC; Fri, 21 Feb 2014 07:14:59 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD1E1A0279; Fri, 21 Feb 2014 07:14:59 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s1LFEeK2015724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 21 Feb 2014 15:14:41 GMT (envelope-from joelja@bogus.com)
Message-ID: <53076D5B.7020004@bogus.com>
Date: Fri, 21 Feb 2014 07:14:35 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, GangChen <phdgang@gmail.com>
References: <52E83C75.7030909@dial.pipex.com> <0D2A7761-2C8D-41C7-8BC7-B4F175187F95@piuha.net> <A0D801AD-CD5A-4259-8BF5-85A105207217@piuha.net> <CAM+vMEQh_Mgjhp3u07CxFAOyR3wkTf+8hepx14ubWOf+bjEqgA@mail.gmail.com> <67462D7E-6E00-45E8-A246-7A7447908116@piuha.net>
In-Reply-To: <67462D7E-6E00-45E8-A246-7A7447908116@piuha.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wriT84j9ETPMviRj0uh2WIXgmgHptnS5W"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Fri, 21 Feb 2014 15:14:42 +0000 (UTC)
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/EqHG16M0lABBuWr4R7uBvOuc2eE
Cc: General Area Review Team <gen-art@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-v6ops-nat64-experience.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-v6ops-nat64-experience-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 15:15:01 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--wriT84j9ETPMviRj0uh2WIXgmgHptnS5W
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2/21/14, 4:32 AM, Jari Arkko wrote:
> Hi,
>=20
> First: I cleared my discuss, so this document's progress is now up to y=
ou guys and Joel. Some further discussion inline:

related to this, I'd like one more pass through the source document
before we send it to the rfc editor. if you can drop me a copy after you
cleared the genart comments but before we post it that would be appreciat=
ed.

>> 4-02-21 0:56 GMT+08:00, Jari Arkko <jari.arkko@piuha.net>:
>>> FWIW, I have now done my own review. I think there are language issue=
s, but
>>> they do not prevent going forward. Language itself will be fixed by t=
he RFC
>>> Editor. I'm more interested in cases where there might be an semantic=
s
>>> unclarity issue.
>>>
>>> I think it would be beneficial to go through each of the comments bef=
ore
>>> final approval of the document.
>>>
>>> With that in mind, going through some of my own and Elwyn's comments:=

>>>
>>>>   o  Operators who adopt NAT64-FE may leverage the application layer=

>>>>      proxies, e.g. X-Forwarded-For (XFF)
>>>>      [
>>>> I-D.ietf-appsawg-http-forwarded
>>>> ], to convey the IPv6 source
>>>>      address in HTTP headers.
>>>
>>> I'd say ... may leverage application layer proxies, and those may use=

>>> additional attributes such as X-Forwarded-For ...
>>
>>>
>>>> Those messages would be passed on to
>>>>      web-servers.  The log parsing tools are required to be able to
>>>>      support IPv6 and may lookup Radius servers for the target
>>>>      subscribers based on IPv6 addresses included in XFF HTTP header=
s.
>>>>      XFF is the de facto standard which has been integrated in most
>>>>      Load Balancers.  Therefore, it may be superior to use in a NAT-=
FE
>>>>      environment.  In the downsides, XFF is specific to HTTP.  It
>>>>      restricts the usages so that the solution can't be applied to
>>>>      requests made over HTTPs.  This makes geo-location problematic =
for
>>>>      HTTPs based services.
>>>>
>>>
>>> Not sure we should call something a de facto standard while pointing =
to a
>>> draft. I'd just say "... has been implemented in many ..."
>>
>> thank you for the suggestion. We will make following changes:
>>
>> =3D=3DNEW
>>
>>   o  Operators who adopt NAT64-FE may leverage the application layer
>>      proxies. Those may use additional attributes such as X-Forwarded-=
For (XFF)
>>      [I-D.ietf-appsawg-http-forwarded] to convey the IPv6 source
>>      address in HTTP headers.  Those messages would be passed on to
>>      web-servers.  The log parsing tools are required to be able to
>>      support IPv6 and may lookup Radius servers for the target
>>      subscribers based on IPv6 addresses included in XFF HTTP headers.=

>>      XFF has been implemented in most Load Balancers.  Therefore,
>>      it may be superior to use in a NAT-FE
>>      environment.  In the downsides, XFF is specific to HTTP.  It
>>      restricts the usages so that the solution can't be applied to
>>      requests made over HTTPs.  This makes geo-location problematic fo=
r
>>      HTTPs based services.
>=20
> OK
>=20
>>
>>
>>
>>>> The experiences of some
>>>>   applications are still align with [
>>>> RFC6586].
>>>
>>>
>>> Not sure what this means.
>>
>> Several applications don't work properly as described in the RFC6585.
>=20
> If you use that text, then it would be fine.
>=20
>>
>>>
>>>
>>>> |  SIP-VoIP      |Fail, due to the lack of NAT64 traversal          =
  |
>>>>
>>>
>>> Did you mean ALG? Not sure what this would mean otherwise.
>>
>> I mean ICE is recommended to be supported in order to avoid SIP-ALG.
>> After the discussion with Dan Wing, resorting to SIP-ALG for
>> supporting IPv4-IPv6 inter-working is not preferred.
>=20
> Ok. Please elaborate, because the text was unclear to the reader.
>=20
> Also, I think you should go through Elwyn's comments and see if you mak=
e improvements.
>=20
> Jari
>=20
>=20



--wriT84j9ETPMviRj0uh2WIXgmgHptnS5W
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMHbVsACgkQ8AA1q7Z/VrIDsgCePsg73T7B78iT263LCysGK0vZ
rD0AnRcRqXrOeUEVfzUQ16PhWxz1ob47
=tHC2
-----END PGP SIGNATURE-----

--wriT84j9ETPMviRj0uh2WIXgmgHptnS5W--


From nobody Mon Feb 24 00:03:33 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 12ADC1A082E for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 00:03:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level: 
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 qWrVv0OcapMm for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 00:03:29 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 359B31A082A for <gen-art@ietf.org>; Mon, 24 Feb 2014 00:03:28 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-0c-530afcced17e
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id CD.EC.10875.ECCFA035; Mon, 24 Feb 2014 09:03:26 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.02.0387.000; Mon, 24 Feb 2014 09:03:26 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-eman-framework-15
Thread-Index: Ac8xNt9qcN91At2hSB+wgtdMVCjCog==
Date: Mon, 24 Feb 2014 08:03:25 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1B2557@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1B2557ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+Jvje65P1zBBt3fzSy+bbKyuPrqM4sD k8eSJT+ZPL5c/swWwBTFZZOSmpNZllqkb5fAlfH7Qw9LwZ6Yik23XzI1MF4N6GLk5JAQMJE4 8uUcE4QtJnHh3nq2LkYuDiGBQ4wSL7/1MUI4Sxgl5k8/zNLFyMHBJmAh0f1PG6RBREBTYu6K t0wgYWaBZIkFv1xAwsIC5hJP1v1lhiixkXgx4y6UrSexe81WFhCbRUBVYu7l+awgrbwCvhKd B5VBwoxAJ3w/tQbsHGYBcYkPB68zQ5wmILFkz3koW1Ti5eN/rBC2ksTaw9tZIOrzJbb8P88O YvMKCEqcnPmEZQKj8Cwko2YhKZuFpAwiriOxYPcnNghbW2LZwtfMMPaZA4+ZkMUXMLKvYmTP TczMSS833MQIjI6DW37r7mA8dU7kEKM0B4uSOO+Ht85BQgLpiSWp2ampBalF8UWlOanFhxiZ ODilGhjVuKx+GsSsKS+UevqgW3DOp92n7pV92l/0fvVG/frnez4K3L3FxM3ko9D9V3D7joZd L1R+fbLuLvt8/sz3mVPdV/Mp/Jff9ei40eRs3pPMV8+zmzWbnVwZl3299NqyGUlN6tZfar9u Uv1xLnQVh2jb1r21p+2C9vw33zTzw4lHL3SdfBU8V/5zVmIpzkg01GIuKk4EAAKlnelcAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/6gu3SM8-sfJa66odHCXb2VD_UaU
Cc: "draft-ietf-eman-framework.all@tools.ietf.org" <draft-ietf-eman-framework.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-eman-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, 24 Feb 2014 08:03:32 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1B2557ESESSMB209erics_
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-eman-framework-15.tx=
t

Reviewer:                                     Christer Holmberg

Review Date:                               24 February 2014

IETF LC End Date:                       24 February 2014

IESG Telechat date:                   N/A



Summary:                                     I have no major issues with th=
e document, but I have a few editorial comments that I ask the authors to c=
onsider addressing.

Major issues: -



Minor issues: -



Nits/editorial comments:







Section 4:

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



Q4_1:                 The 3rd picture (Single Power Supply with Multiple De=
vices) is split between two pages. Would it be possible to make sure the wh=
ole picture is on a single page?



Q4_2:                 In the 4th picture (Multiple Power Supplies with Sing=
le Devices), there are two "######" lines between 'power source 1' and 'dev=
ice'? Is there a  reason for that?





Section 5:

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



Q5_1:                 I think it would be useful to have a few general word=
s about what is not covered also in the Abstract and Introduction.





Section 6.2:

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



Q6_2_1:            Within section 6.2, and the subclasses, do you need to i=
ndicate '(Class)'? The section name already indicates '(Class)'?



Q6_2_2:            Shall 'Component (Component)' be 'Component (Class)'?





Section 6.3:

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



Q6_3_1:            For section 6.3.2, I suggest to change the section title=
 from 'Context in General' to 'Context: General', to be aligned with the ot=
her Context related attributes.





Regards,



Christer


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Vain tekstin\00E4 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.Shkpostityyli17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.VaintekstinChar
	{mso-style-name:"Vain tekstin\00E4 Char";
	mso-style-priority:99;
	mso-style-link:"Vain tekstin\00E4";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 2.0cm 70.85pt 2.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FI" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">I am the assigned Gen-ART re=
viewer for this draft. For background on Gen-ART, please see the FAQ at &lt=
;
</span><a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">=
<span lang=3D"EN-US">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfa=
q</span></a><span lang=3D"EN-US">&gt;.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Please wait for direction fr=
om your document shepherd or AD before posting a new version of the draft.<=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Document:&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-eman-framework-15.txt<o:p></o:p><=
/span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Reviewer:&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Christer Holmberg<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Review Date:&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; 24 February 2014<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">IETF LC End Date:&nbsp;&nbsp=
;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24 February 2014<o:p></o:p></span=
></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">IESG Telechat date:&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; N/A<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Summary:&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I have no major issues with =
the document, but I have a few editorial comments that I ask the authors to=
 consider addressing.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Major issues: -<o:p></o:p></=
span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Minor issues: -<o:p></o:p></=
span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Nits/editorial comments: <o:=
p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Section 4:<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">------------<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Q4_1:&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; T=
he 3<sup>rd</sup> picture (Single Power Supply with Multiple Devices) is sp=
lit between two pages. Would it be possible to make sure the whole picture =
is on a single page?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Q4_2:&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I=
n the 4<sup>th</sup> picture (Multiple Power Supplies with Single Devices),=
 there are two &#8220;######&#8221; lines between &#8216;power source 1&#82=
17; and &#8216;device&#8217;? Is there a&nbsp; reason for that?<o:p></o:p><=
/span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Section 5:<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">------------<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Q5_1:&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I=
 think it would be useful to have a few general words about what is not cov=
ered also in the Abstract and Introduction.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Section 6.2:<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">--------------<o:p></o:p></s=
pan></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Q6_2_1:&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Within section 6.2, and the s=
ubclasses, do you need to indicate &#8216;(Class)&#8217;? The section name =
already indicates &#8216;(Class)&#8217;?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Q6_2_2:&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Shall &#8216;Component (Compo=
nent)&#8217; be &#8216;Component (Class)&#8217;?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Section 6.3:<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">--------------<o:p></o:p></s=
pan></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Q6_3_1:&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For section 6.3.2, I suggest =
to change the section title from &#8216;Context in General&#8217; to &#8216=
;Context: General&#8217;, to be aligned with the other Context related attr=
ibutes.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Regards,<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Christer<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1B2557ESESSMB209erics_--


From nobody Mon Feb 24 00:24:22 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 E501A1A00EB for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 00:24:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level: 
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 d0aT8ihp0gRp for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 00:24:16 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 429B31A041E for <gen-art@ietf.org>; Mon, 24 Feb 2014 00:24:11 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-ab-530b01aa1880
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 41.40.10875.AA10B035; Mon, 24 Feb 2014 09:24:11 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.02.0387.000; Mon, 24 Feb 2014 09:24:10 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-roll-trickle-mcast-07
Thread-Index: Ac8xODbxNRCAJgNcQoCBBtm2EqQIfg==
Date: Mon, 24 Feb 2014 08:24:09 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1B26CB@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1B26CBESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFLMWRmVeSWpSXmKPExsUyM+Jvje5qRu5gg1/tLBYTv7QzWlx99ZnF gcljyZKfTB5fLn9mC2CK4rJJSc3JLEst0rdL4Mq4tz+54FEbY8XFKbtYGhjvVXcxcnJICJhI PPj/gBnCFpO4cG89WxcjF4eQwCFGiYfbFrKDJIQEljBKdO1Q7GLk4GATsJDo/qcNEhYR0JSY u+ItE4jNLJAtcWvPVyaQEmEBa4mJy+shShwkfsy5xAhh60mc37iEBcRmEVCVePnmGFicV8BX 4vSLJWA2I9AJ30+tgRopLvHh4HWo0wQkluw5D2WLSrx8/I8VwlaSWHt4OwtEfb7E/O83mCFm CkqcnPmEZQKj8Cwko2YhKZuFpAwiriOxYPcnNghbW2LZwtfMMPaZA4+ZkMUXMLKvYmTPTczM SS833MQIjI+DW37r7mA8dU7kEKM0B4uSOO+Ht85BQgLpiSWp2ampBalF8UWlOanFhxiZODil GhjTf/au0i2ImJZ9NWOV/qvfc+//UAjP0NgdpOdlJTE7rPTm9V4JAQexJCVO9ajrefkic/N8 Ttvv7o+8+vtxvbXSy5T7DOyLin6zdDxxX1g/mafL3N6xkKHhcXjU01D/xTpZAbwr1eK3dDjE TpZXl4lfeHl+3QHDd1Vn09iWK/6WtVZ+3HkhSomlOCPRUIu5qDgRAJfZH4FdAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/EWkqHojvb6-4ABDoORPd53otfTA
Cc: "draft-ietf-roll-trickle-mcast.all@tools.ietf.org" <draft-ietf-roll-trickle-mcast.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-roll-trickle-mcast-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 08:24:19 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1B26CBESESSMB209erics_
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-roll-trickle-mcast-07

Reviewer:                           Christer Holmberg

Review Date:                     24 February 2014

IETF LC End Date:             7 February 2014

IETF Telechat Date:         N/A

Summary:        I provided comments on a previous version (-05) of this doc=
ument. Unfortunately I can't find the reply to my comments from the authors=
, so some of my comments may not have been valid, or the authors may have d=
isagreed with my change suggestions.

However, when I check the -07 version of the document I see that some of my=
 comments have not been addressed, so I'll re-submit them again - just in c=
ase.


Major Issues: None

Minor Issues: None

Editorial nits:

Section 1:
------------

Q_1_1:

I assume "LLN" stands for "Low power and Lossy Networks", but there is no e=
xtension anywhere. Please insert "Low power and Lossy Networks (LLN)" on fi=
rst occurance.


Section 3:
------------

Q_3_1:

In a few places the text says "this protocol". I would suggest to replace t=
hat with "MPL".


Section 4:
-----------

Q_4_2:

I would suggest to add something in front of "Overview" in the subject of s=
ection 4.3. Overview of what? :)




Regards,

Christer




--_000_7594FB04B1934943A5C02806D1A2204B1D1B26CBESESSMB209erics_
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.Shkpostityyli17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 2.0cm 70.85pt 2.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FI" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">I am the ass=
igned Gen-ART reviewer for this draft. For background on Gen-ART, please se=
e the FAQ at &lt;</span><span style=3D"font-size:10.0pt;font-family:&quot;T=
ahoma&quot;,&quot;sans-serif&quot;;color:black"><a href=3D"https://rvi.se.e=
ricsson.net/owa/,DanaInfo=3Dmail.internal.ericsson.com,SSL&#43;redir.aspx?C=
=3DvCr1L8PWQUqCZeSAn6cKI_Abm6K8vNAI1hJJwcnXe8VAikdG2PcMrstLszaJeAo7bR8W3uA2=
uu0.&amp;URL=3Dhttps%3a%2f%2frvi.se.ericsson.net%2fowa%2f%2cDanaInfo%3dmail=
.internal.ericsson.com%2cSSL%2bredir.aspx%3fC%3dvCr1L8PWQUqCZeSAn6cKI_Abm6K=
8vNAI1hJJwcnXe8VAikdG2PcMrstLszaJeAo7bR8W3uA2uu0.%26URL%3dhttp%253a%252f%25=
2fwiki.tools.ietf.org%252farea%252fgen%252ftrac%252fwiki%252fGenArtfaq" tar=
get=3D"_blank"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;">http://wiki.tools.ietf.org/area/=
gen/trac/wiki/GenArtfaq</span></a></span><span lang=3D"EN-US" style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:b=
lack">&gt;</span><span lang=3D"EN-US" 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 lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Document:&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ie=
tf-roll-trickle-mcast-07</span><span lang=3D"EN-US" style=3D"font-size:10.0=
pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Reviewer:&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Christer Holmberg</span><span lang=3D"EN-US" 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 lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Review Date:=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;24 February 2014</span><=
span lang=3D"EN-US" 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 lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">IETF LC End =
Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;7 February 2014</span><span lang=3D"EN-US" style=3D"font-size:10.0p=
t;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"><o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">IETF Telecha=
t Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; N/A</span><span lan=
g=3D"EN-US" 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 lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Summary:&nbs=
p; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I provided comments on a previous version=
 (-05) of this document. Unfortunately I can&#8217;t find the reply to my c=
omments from the authors,
 so some of my comments may not have been valid, or the authors may have di=
sagreed with my change suggestions.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;<=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">However, whe=
n I check the -07 version of the document I see that some of my comments ha=
ve not been addressed, so I&#8217;ll re-submit them again - just
 in case.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;<=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Major Issues=
: None</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&qu=
ot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Minor Issues=
: None</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&qu=
ot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Editorial ni=
ts:</span><span lang=3D"EN-US" 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 lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">Section 1:<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" 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 lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">Q_1_1:<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">I assume &quo=
t;LLN&quot; stands for &quot;Low power and Lossy Networks&quot;, but there =
is no extension anywhere. Please insert &quot;Low power and Lossy Networks =
(LLN)&quot; on
 first occurance.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">Section 3:<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" 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 lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">Q_3_1:<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">In a few plac=
es the text says &quot;this protocol&quot;. I would suggest to replace that=
 with &quot;MPL&quot;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">Section 4:<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" 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 lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;&nbsp;<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">Q_4_2:<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">I would sugge=
st to&nbsp;add something in front of &quot;Overview&quot; in the subject of=
 section 4.3. Overview of what? :)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">&nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size: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">&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">Christer<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">&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;"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1B26CBESESSMB209erics_--


From nobody Mon Feb 24 03:41:55 2014
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 907E91A07D7; Mon, 24 Feb 2014 03:41:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 fw5hhsPooT6t; Mon, 24 Feb 2014 03:41:49 -0800 (PST)
Received: from mail-ea0-x233.google.com (mail-ea0-x233.google.com [IPv6:2a00:1450:4013:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id BBA671A0740; Mon, 24 Feb 2014 03:41:48 -0800 (PST)
Received: by mail-ea0-f179.google.com with SMTP id q10so3053408ead.24 for <multiple recipients>; Mon, 24 Feb 2014 03:41:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=ryJCeBzFaezvH2/jzOyv3gwnXw8fdsqfGXGa29wCdnQ=; b=UVeMIjdgBDghPoGc0Zmir6iJRgoN6EmZQGP9Asj8zIetMfdnbPB9SzvjAyz7d3t1Yu FFZ48sYJqCcg0rT+nBUI6aTebWd9kR/72L+LCbMDxg9wNuk7IykafPP+igJXsr9X+7eB 0TI5Fz2RGHTTr/gL/bpUR2fJH2ytykQxcTa+491k66Q6otuXPB1SkgoGuGGMFcGJVbfu d6Rr80//PYG9N+482GsQyhZMMLEYH16/Xp46Q1PG63+hSoRtmoq13K61JO4lXSDspHsT 0+TLCOJrmWgNYXkbzpFGOKZlVfXymFZIcGrig2x1tlHFtNQu2Z3KtzMk0sQaPV3WhDAl 4BLw==
X-Received: by 10.14.221.201 with SMTP id r49mr24237976eep.104.1393242107768;  Mon, 24 Feb 2014 03:41:47 -0800 (PST)
Received: from RoniE ([109.67.98.212]) by mx.google.com with ESMTPSA id 46sm62776928ees.4.2014.02.24.03.41.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 24 Feb 2014 03:41:46 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-mpls-special-purpose-labels.all@tools.ietf.org>
Date: Mon, 24 Feb 2014 13:41:41 +0200
Message-ID: <07cd01cf3155$64d69780$2e83c680$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_07CE_01CF3166.28602AD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8xVWLYNV4LALsIQoymtX+xVkQDqw==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/V45D0GFf7nrAzAaMzc3AtXTtYLY
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-mpls-special-purpose-labels-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 11:41:51 -0000

This is a multipart message in MIME format.

------=_NextPart_000_07CE_01CF3166.28602AD0
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-special-purpose-labels-05

Reviewer: Roni Even

Review Date:2014-2-24

IETF LC End Date: 2014-3-3

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

1.  In section 3.2 (a):  I noticed that the policy to update the registry
according  to section 5 is standard action so it should be the same here
since this is an update to the registry.

 

 

Nits/editorial comments:

1.	In section 3 last sentence "This answer to this" should be "The .."
2.	In section 3.2 item c you have "for for"

 


------=_NextPart_000_07CE_01CF3166.28602AD0
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;}
/* List Definitions */
@list l0
	{mso-list-id:1161195496;
	mso-list-type:hybrid;
	mso-list-template-ids:-1103323742 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1462651820;
	mso-list-type:hybrid;
	mso-list-template-ids:-1754494482 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><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-special-purpose-labels-05</spa=
n><span 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;2-24<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2014&#8211;3-3<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as 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 =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.2 (a):&nbsp; I noticed that </span>the policy to update the registry =
according&nbsp; to section 5 is standard action so it should be the same =
here since this is an update to the registry.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo2'>In =
section 3 last sentence &#8220;This answer to this&#8221; should be =
&#8220;The ..&#8221;<o:p></o:p></li><li class=3DMsoNormal =
style=3D'mso-list:l0 level1 lfo2'>In section 3.2 item c you have =
&#8220;for for&#8221;<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_07CE_01CF3166.28602AD0--


From nobody Mon Feb 24 03:55:02 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 1086F1A0091; Mon, 24 Feb 2014 03:54:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.917
X-Spam-Level: **
X-Spam-Status: No, score=2.917 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] 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 DhPCwfbtiJ9y; Mon, 24 Feb 2014 03:54:56 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 7F23B1A0348; Mon, 24 Feb 2014 03:54:56 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1OBsroC024140; Mon, 24 Feb 2014 11:54:53 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1OBsoUa024118 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 24 Feb 2014 11:54:52 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Roni Even'" <ron.even.tlv@gmail.com>, <draft-ietf-mpls-special-purpose-labels.all@tools.ietf.org>
References: <07cd01cf3155$64d69780$2e83c680$@gmail.com>
In-Reply-To: <07cd01cf3155$64d69780$2e83c680$@gmail.com>
Date: Mon, 24 Feb 2014 11:54:51 -0000
Message-ID: <074c01cf3157$3b8b3b90$b2a1b2b0$@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: AQI/FAznYkcQkSVfLg/s3RCyC/ms/Jnkg8nQ
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/PhJwISDAhjy3EJpFcZVZ-u-At3Y
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-special-purpose-labels-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 11:54:58 -0000

Hi Roni,

Thanks for taking the time.

> Minor issues:
> 1. In section 3.2 (a):=A0 I noticed that the policy to update the =
registry
according
>=A0 to section 5 is standard action so it should be the same here since =
this is
an
> update to the registry.

Hmmm, but I don't think so.
Section 5 (and the existing registry) define the procedures to be used =
for
assigning new values from a namespace per 5226. Procedures for
retiring/deprecating values are rarely, if ever, documented and do not =
need to
follow the same rules as are used for assignments.

That said, I think I can see some value in symmetry. but it seems a bit =
OTT to
have a Standards Track RFC saying "this code point is not used". What is =
certain
(and we appear to agree on this) is that IETF consensus is needed =
(presumably as
tested by IETF last call on the relevant I-D).

Since we disagree, but my disagreement is not too strong, I will be =
guided by
the IESG (and specifically our sponsoring AD) as to whether to change:
OLD
       An RFC with at
       least Informational status is required.
NEW
      A Standards=20
      Track RFC is required.
END

> Nits/editorial comments:
> 1. In section 3 last sentence =93This answer to this=94 should be =
=93The ..=94

Ack

> 2. In section 3.2 item c you have =93for for=94

Ack

Cheers,
Adrian


From nobody Mon Feb 24 04:46:32 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 708C21A0072 for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 04:46:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.247
X-Spam-Level: 
X-Spam-Status: No, score=-1.247 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547] 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 wO0plltSuR8p for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 04:46:29 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 5F7591A0457 for <gen-art@ietf.org>; Mon, 24 Feb 2014 04:46:29 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvcLAI0+C1OHCzIm/2dsb2JhbABZgkIjITtXqCoIj2GIWIEWFnSCJwEBAxIbTBIBFQcOViYBBA4NGodjAQyaWKsVF4xygUEgEYMrgRQEmWaFPos3gy2CKg
X-IronPort-AV: E=Sophos; i="4.97,534,1389762000"; d="scan'208,217"; a="50643263"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 24 Feb 2014 07:46:28 -0500
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; 24 Feb 2014 07:33:21 -0500
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, 24 Feb 2014 13:46:26 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review for draft-ietf-mpls-ldp-applicability-label-adv-02
Thread-Index: Ac8xXmwAmM7V+KZLRYuRAri+JMQFqw==
Date: Mon, 24 Feb 2014 12:46:26 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E435527@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA2E435527AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/RaWBAd887p6OVvPvtAbLbidEUwI
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 review for draft-ietf-mpls-ldp-applicability-label-adv-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 12:46:31 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E435527AZFFEXMB04globa_
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: draft-ietf-mpls-ldp-applicability-label-adv-02

Reviewer: Dan Romascanu

Review Date: 2/24/14

IETF LC End Date: 2/24/14

IESG Telechat date:



Summary: ready with minor issues



Major issues:



Minor issues:



In the table in 2.2 - the RFC column points to RFC 5036 for the first two e=
ntries. Actually RFC 5036 defines only the range for LDP FEC types, but say=
s nothing about the values. The right information seems to be 'xxxx (this R=
FC)' or '5036 and xxxx (this RFC)'



Nits/editorial comments:


Some acronyms are not expanded at first occurrence - FEC, LSR


Regards,

Dan


--_000_9904FB1B0159DA42B0B887B7FA8119CA2E435527AZFFEXMB04globa_
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;}
@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<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-mpls-ldp-applicability-label=
-adv-02<o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 2/24/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: <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary: ready with minor issues<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major issues:<o:p></o:p></p>
<p class=3D"MsoPlainText"><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">In the table in 2.2 &#8211; the RFC column points=
 to RFC 5036 for the first two entries. Actually RFC 5036 defines only the =
range for LDP FEC types, but says nothing about the values. The right infor=
mation seems to be &#8216;xxxx (this RFC)&#8217; or
 &#8216;5036 and xxxx (this RFC)&#8217;<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">Some acronyms are not expanded at first occurrence &=
#8211; FEC, LSR
<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">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dan<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA2E435527AZFFEXMB04globa_--


From nobody Mon Feb 24 05:37:08 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 B6C231A040E; Mon, 24 Feb 2014 05:37:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level: 
X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  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 23BWA3RQr3hz; Mon, 24 Feb 2014 05:36:58 -0800 (PST)
Received: from mail-ee0-x231.google.com (mail-ee0-x231.google.com [IPv6:2a00:1450:4013:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 54C7E1A085C; Mon, 24 Feb 2014 05:36:58 -0800 (PST)
Received: by mail-ee0-f49.google.com with SMTP id d17so3135753eek.8 for <multiple recipients>; Mon, 24 Feb 2014 05:36:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=9ipil7DZOamQD4kGkOHJ4vrCL3WkxivF+T8B4KO+qe8=; b=OX3KoQQjvX/NizU0iMpR/7BuN0tskJKFF7t3le5gARgY5X/S7QR3zYB9zanwRmDsND PF9P6+SGVAb/ME+TFNXDxeqnzSu74m6g8iJyXTt3i/Jr++e472S42AnrusQIu1STrHQk TVLdtC8DyaoqhzN9L/XjTiZp5kL7D3q/WP/Mkxtz3d1FVD+vDHAyPT6QI8EK/zNaSLfx 59gsF8c3LJruzteMsVeKYWgHHecPfVLlROgc8NFaSKj8U8W99Xh83gRxGTiyhGaQGEOz a4NHcOoVZAXxzQdr1igsriaG7K8HiWqlcnEWWiAvZy+KrcQhrEjUGT251IDBX8vSVU6K sB9A==
X-Received: by 10.15.56.130 with SMTP id y2mr24723407eew.17.1393249017215; Mon, 24 Feb 2014 05:36:57 -0800 (PST)
Received: from RoniE ([109.67.98.212]) by mx.google.com with ESMTPSA id x2sm63872874eeo.8.2014.02.24.05.36.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 24 Feb 2014 05:36:55 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <adrian@olddog.co.uk>, <draft-ietf-mpls-special-purpose-labels.all@tools.ietf.org>
References: <07cd01cf3155$64d69780$2e83c680$@gmail.com> <074c01cf3157$3b8b3b90$b2a1b2b0$@olddog.co.uk>
In-Reply-To: <074c01cf3157$3b8b3b90$b2a1b2b0$@olddog.co.uk>
Date: Mon, 24 Feb 2014 15:36:40 +0200
Message-ID: <080e01cf3165$7adb15f0$709141d0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI/FAznYkcQkSVfLg/s3RCyC/ms/AEVqdCjmdv0qrA=
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/8ZNCBLE95qCc_F3CgL1mM7PgBjQ
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-special-purpose-labels-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 13:37:03 -0000

Hi Adrian,
I do not have a strong position on this topic ( I can agree that =
deprecating
a code point is a rare case) , I was wondering why the difference and I =
can
agree with any direction that you will choose about the maturity level
needed
Roni

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: 24 February, 2014 1:55 PM
> To: 'Roni Even'; =
draft-ietf-mpls-special-purpose-labels.all@tools.ietf.org
> Cc: ietf@ietf.org; gen-art@ietf.org
> Subject: RE: Gen-ART LC review of
draft-ietf-mpls-special-purpose-labels-05
>=20
> Hi Roni,
>=20
> Thanks for taking the time.
>=20
> > Minor issues:
> > 1. In section 3.2 (a):=A0 I noticed that the policy to update the
> > registry
> according
> >=A0 to section 5 is standard action so it should be the same here =
since
> >this is
> an
> > update to the registry.
>=20
> Hmmm, but I don't think so.
> Section 5 (and the existing registry) define the procedures to be used =
for
> assigning new values from a namespace per 5226. Procedures for
> retiring/deprecating values are rarely, if ever, documented and do not
need to
> follow the same rules as are used for assignments.
>=20
> That said, I think I can see some value in symmetry. but it seems a =
bit
OTT to
> have a Standards Track RFC saying "this code point is not used". What =
is
certain
> (and we appear to agree on this) is that IETF consensus is needed
(presumably
> as tested by IETF last call on the relevant I-D).
>=20
> Since we disagree, but my disagreement is not too strong, I will be =
guided
by
> the IESG (and specifically our sponsoring AD) as to whether to change:
> OLD
>        An RFC with at
>        least Informational status is required.
> NEW
>       A Standards
>       Track RFC is required.
> END
>=20
> > Nits/editorial comments:
> > 1. In section 3 last sentence =93This answer to this=94 should be =
=93The ..=94
>=20
> Ack
>=20
> > 2. In section 3.2 item c you have =93for for=94
>=20
> Ack
>=20
> Cheers,
> Adrian


From nobody Mon Feb 24 10:11:45 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 6FFE21A00ED for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 10:11:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.2
X-Spam-Level: 
X-Spam-Status: No, score=-99.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 7FIFmkAHNQ_p for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 10:11:40 -0800 (PST)
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 703EF1A00B1 for <gen-art@ietf.org>; Mon, 24 Feb 2014 10:11:40 -0800 (PST)
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 1WI008-00065n-6h; Mon, 24 Feb 2014 18:11:36 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Mon, 24 Feb 2014 18:11:33 +0000
Message-Id: <1393265494.8036.426.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/pVtNWuS4gdp9V_CPcnaYBkP9nnY
Cc: draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org
Subject: [Gen-art] Gen-art LC review of draft-ietf-mpls-tp-psc-itu-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 18:11:43 -0000

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

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

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

Document: draft-ietf-mpls-tp-psc-itu-02.txt
Reviewer: Elwyn Davies
Review Date: 24 Feb 2014
IETF LC End Date: 24 Feb 2014
IESG Telechat date: (if known) -

Summary:
Almost Ready for IESG.  There is a statement in s1 that could indicate
that the consequences of turning on a subset of the new capabilities has
not been fully thought through.  I am also not clear whether EXER
fulfils the intentions of R84 in RFC 5654 as stated.  The repeated
transmission of the advertised capabilities adds to the scope for random
bit errors to halt protection operation.  A few minor nits noted below.

Major issues:
None

Minor issues:
s1, next to last para:

>    This document describes the behavior of the PSC protocol including
>    the priority logic and the state machine when all the capabilities
>    associated with the APS mode are enabled.  The PSC protocol behavior
>    for the PSC mode is as defined in RFC 6378.

APS mode involves five capabilities which can, apparently, be
implemented and advertised indpendently, so presumably there might be
reasons for either implementing or turning on just a subset.  Are there
any implications for the PSC protocol if only some subset of the the
capabilities are available in a given node?  (This may be a dumb
question and I haven't tried to work out what might go wrong if you did
have any of the available subsets.) 

s9.1.1/s9.2: Following on from the previous point, s9.1.1 implies that
the system can operate happily with some subset of the five capabilities
turned on provided that both ends concur.  However there is no mode name
that would cover such a subset.  Does this actually mean that turning on
a subset doesn't really work? And if it doesn't work why bother with
five flag bits?  Also the phraseology used here could lead to future
problems if more capabilities are defined:  suppose some future new mode
(FOO) adds <n> more capabilities but the two 'modes' can be turned on
independently - as currently expressed you would have to define three
mode names for APS only, FOO only and APS + FOO.. and so on with more
capability sets.  Unintended consequence? Oh, and what if a capability
is used in more than one mode?

s8: EXER appears to test the PSC channel but nothing else.  I am not
clear that this fully satisfies R84 in RFC 5654.. It may be that I don't
know what information would go back in the RR response, but should the
response say anything about the state in the remote node (like the
remote end of the working path is not working in some way and/or what is
the PSC state - RFC 6378 s3.6)?

s13: The addition of the Capabilities TLV and the requirement that it is
carried accurately and repeatedly in every PSC message introduces a new
aspect to the DoS/random corruption problem mentioned in s6 of RFC 6378.
A single bit corruption in a PSC message will lead to disablement of
protection switching and requirement of operator intervention.  I am not
sure if this is a serious issue, but it probably merits a comment in s13
and verification that it does match with the words in RFC 6378 as
regards 'converging on a stable state'.

Nits/editorial comments:
s4.4, title: s/Capability 1/Priority Modifications/ (Ok, its accurate
but bald)

s7.3 et seq: The term "selector bridge" is introduced without
definition.  I suspect it is a piece of jargon I am supposed to know but
I think a reference would help.

s7.4, para 1: 

> the rules to resolve the equal priority requests are
>    required.
Should this be s/the rules/some rules/?

s8, definition of Exercise (EXER): Describing EXER as 'replacing' one of
NR, RR or DNR seems a bit odd.  Mentioning RR is particularly
problematic since it makes the definitions sort of circular as RR is the
response to EXER.  I guess what is probably appropriate is to say that
it is built in the same way as an NR message would be built. 

s9.1: RFC 6378 doesn't define the encoding of the TLV type and TLV
length fields, so it needs to be done here (Unsigned integers). (It also
doesn't define encoding of the (unnecessary) overall TLV length field in
the PSC header.

s9.1: What happens if the receiver gets a TLV with some a flags length
that isn't a multiple of 4 (or indeed a TLV it deosn't recognize?)  It
might be cleaner to define the length in terms of units of 32 bits.

s10.3, para 2: s/they SHALL be disappeared./they SHALL be discarded./





From nobody Mon Feb 24 13:51:13 2014
Return-Path: <huub.van.helvoort@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21B911A030A for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 13:51:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.418
X-Spam-Level: 
X-Spam-Status: No, score=0.418 tagged_above=-999 required=5 tests=[BAYES_50=0.8, CN_BODY_457=0.011, CN_BODY_832=0.004, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, 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 sx_gE1uVg1FH for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 13:51:08 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9F8E91A02FF for <gen-art@ietf.org>; Mon, 24 Feb 2014 13:51:07 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBL81877; Mon, 24 Feb 2014 21:50:44 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 24 Feb 2014 21:50:36 +0000
Received: from LHREML511-MBS.china.huawei.com ([10.201.4.130]) by lhreml406-hub.china.huawei.com ([10.201.5.243]) with mapi id 14.03.0158.001; Mon, 24 Feb 2014 21:50:41 +0000
From: Huub Van Helvoort <huub.van.helvoort@huawei.com>
To: Elwyn Davies <elwynd@dial.pipex.com>, General Area Review Team <gen-art@ietf.org>
Thread-Topic: Gen-art LC review of draft-ietf-mpls-tp-psc-itu-02.txt
Thread-Index: AQHPMYvrdiAImCxNeE+GYoW8Xv9JPprE2huk
Date: Mon, 24 Feb 2014 21:50:39 +0000
Message-ID: <74118A81AEACB94EB8AB398AF85AF7820C556F@lhreml511-mbs>
References: <1393265494.8036.426.camel@mightyatom>
In-Reply-To: <1393265494.8036.426.camel@mightyatom>
Accept-Language: en-GB, nl-NL, zh-CN, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.73.93]
Content-Type: multipart/alternative; boundary="_000_74118A81AEACB94EB8AB398AF85AF7820C556Flhreml511mbs_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/fC8czShQRtQGL7WKzmDb4DBR15c
Cc: "draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org" <draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-mpls-tp-psc-itu-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 21:51:12 -0000

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

SGVsbG8gRWx3eW4sDQoNCg0KDQpUaGFuayB5b3UgZm9yIHlvdXIgcmV2aWV3Lg0KDQoNCg0KU2Vl
IG15IHJlc3BvbnNlIGluLWxpbmUgW0h1dWJdDQoNCkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQg
cmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZvciBiYWNrZ3JvdW5kIG9uDQpHZW4tQVJULCBwbGVh
c2Ugc2VlIHRoZSBGQVEgYXQNCg0KPGh0dHA6Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2Vu
L3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0KDQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBh
bG9uZyB3aXRoIGFueSBvdGhlciBMYXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4N
Cg0KRG9jdW1lbnQ6IGRyYWZ0LWlldGYtbXBscy10cC1wc2MtaXR1LTAyLnR4dA0KUmV2aWV3ZXI6
IEVsd3luIERhdmllcw0KUmV2aWV3IERhdGU6IDI0IEZlYiAyMDE0DQpJRVRGIExDIEVuZCBEYXRl
OiAyNCBGZWIgMjAxNA0KSUVTRyBUZWxlY2hhdCBkYXRlOiAoaWYga25vd24pIC0NCg0KU3VtbWFy
eToNCkFsbW9zdCBSZWFkeSBmb3IgSUVTRy4gIFRoZXJlIGlzIGEgc3RhdGVtZW50IGluIHMxIHRo
YXQgY291bGQgaW5kaWNhdGUNCnRoYXQgdGhlIGNvbnNlcXVlbmNlcyBvZiB0dXJuaW5nIG9uIGEg
c3Vic2V0IG9mIHRoZSBuZXcgY2FwYWJpbGl0aWVzIGhhcw0Kbm90IGJlZW4gZnVsbHkgdGhvdWdo
dCB0aHJvdWdoLiAgSSBhbSBhbHNvIG5vdCBjbGVhciB3aGV0aGVyIEVYRVINCmZ1bGZpbHMgdGhl
IGludGVudGlvbnMgb2YgUjg0IGluIFJGQyA1NjU0IGFzIHN0YXRlZC4gIFRoZSByZXBlYXRlZA0K
dHJhbnNtaXNzaW9uIG9mIHRoZSBhZHZlcnRpc2VkIGNhcGFiaWxpdGllcyBhZGRzIHRvIHRoZSBz
Y29wZSBmb3IgcmFuZG9tDQpiaXQgZXJyb3JzIHRvIGhhbHQgcHJvdGVjdGlvbiBvcGVyYXRpb24u
ICBBIGZldyBtaW5vciBuaXRzIG5vdGVkIGJlbG93Lg0KDQpbSHV1Yl0gSSBoYXZlIGFkZHJlc3Nl
ZCB0aGVzZSBiZWxvdy4NCg0KTWFqb3IgaXNzdWVzOg0KTm9uZQ0KDQpNaW5vciBpc3N1ZXM6DQpz
MSwgbmV4dCB0byBsYXN0IHBhcmE6DQoNCj4gICAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgdGhl
IGJlaGF2aW9yIG9mIHRoZSBQU0MgcHJvdG9jb2wgaW5jbHVkaW5nDQo+ICAgIHRoZSBwcmlvcml0
eSBsb2dpYyBhbmQgdGhlIHN0YXRlIG1hY2hpbmUgd2hlbiBhbGwgdGhlIGNhcGFiaWxpdGllcw0K
PiAgICBhc3NvY2lhdGVkIHdpdGggdGhlIEFQUyBtb2RlIGFyZSBlbmFibGVkLiAgVGhlIFBTQyBw
cm90b2NvbCBiZWhhdmlvcg0KPiAgICBmb3IgdGhlIFBTQyBtb2RlIGlzIGFzIGRlZmluZWQgaW4g
UkZDIDYzNzguDQoNCkFQUyBtb2RlIGludm9sdmVzIGZpdmUgY2FwYWJpbGl0aWVzIHdoaWNoIGNh
biwgYXBwYXJlbnRseSwgYmUNCmltcGxlbWVudGVkIGFuZCBhZHZlcnRpc2VkIGluZHBlbmRlbnRs
eSwgc28gcHJlc3VtYWJseSB0aGVyZSBtaWdodCBiZQ0KcmVhc29ucyBmb3IgZWl0aGVyIGltcGxl
bWVudGluZyBvciB0dXJuaW5nIG9uIGp1c3QgYSBzdWJzZXQuDQoNCg0KDQpbSHV1Yl0gVGhlcmUg
d2VyZSBvcmlnaW5hbGx5IHNlcGFyYXRlIGRyYWZ0cyBmb3IgZWFjaCBvZiB0aGUgY2FwYWJpbGl0
aWVzLg0KDQpIb3dldmVyLCBpdCB3YXMgdmVyeSBjb21wbGV4IHRvIGRlZmluZSB0aGUgZWZmZWN0
IG9uIHRoZSBzdGF0ZQ0KDQp0cmFuc2l0aW9uIHRhYmxlcyBmb3IgZWFjaCBjYXBhYmlsaXR5IG9y
IGNvbWJpbmF0aW9uIG9mIGNhcGFiaWxpdGllcy4NCg0KDQoNCltIdXViXSB0byByZXNvbHZlIHRo
aXMgaXNzdWUgaXQgd2FzIGRlY2VpZGVkIHRoYXQgZm9yIGFueSBwZXJtaXRhdGlvbg0KDQpvZiB0
aGUgcG9zc2libGUgY29tYmluYXRpb25zIG9mIGNhcGFiaWxpdGllcyBhIHNlcGFyYXRlIGRyYWZ0
IHNob3VsZCBiZQ0KDQpkZXZlbG9wZWQuIFJGQzYzNzggaXMgdGhlIG9uZSB3aGVyZSBub25lIG9m
IHRoZSBjYXBhYmlsaXRpZXMgaXMNCg0KdXNlZCwgYW5kIHRoaXMgZHJhZnQgaXMgdGhlIG9uZSB3
aGVyZSBhbGwgY2FwYWJpbGlpZXMgYXJlIHVzZWQuIFNvIGZhcg0KDQpub25lIG9mIHRoZSBvdGhl
ciBwb3NzaWJsZSBkcmFmdHMgaXMgd3JpdHRlbi4NCg0KDQoNCltIdXViXSBUaGlzIGRyYWZ0IHBy
b3ZpZGVzIHRoZSBiZWhhdmlvciBzaW1pbGFyIHRvIEFQUyB1c2VkIGluIElUVS1UDQoNCmZvciBv
dGhlciB0ZWNobm9sb2dpZXMuDQoNCg0KDQpBcmUgdGhlcmUNCg0KYW55IGltcGxpY2F0aW9ucyBm
b3IgdGhlIFBTQyBwcm90b2NvbCBpZiBvbmx5IHNvbWUgc3Vic2V0IG9mIHRoZSB0aGUNCmNhcGFi
aWxpdGllcyBhcmUgYXZhaWxhYmxlIGluIGEgZ2l2ZW4gbm9kZT8gIChUaGlzIG1heSBiZSBhIGR1
bWINCnF1ZXN0aW9uIGFuZCBJIGhhdmVuJ3QgdHJpZWQgdG8gd29yayBvdXQgd2hhdCBtaWdodCBn
byB3cm9uZyBpZiB5b3UgZGlkDQpoYXZlIGFueSBvZiB0aGUgYXZhaWxhYmxlIHN1YnNldHMuKQ0K
DQoNCg0KW0h1dWJdIGJvdGggbm9kZXMgTVVTVCBzdXBwb3J0IHRoZSBzYW1lIHN1YnNldCwgaWYg
dGhleSBkb24ndCB0aGUNCg0KcmVzdWx0IHdpbGwgYmUgdW5wcmVkaWN0YWJsZSBiZWNhdXNlIHRo
ZSBzdGF0ZSBtYWNoaW5lcyBhcmUgZGlmZmVyZW50Lg0KDQpzOS4xLjEvczkuMjogRm9sbG93aW5n
IG9uIGZyb20gdGhlIHByZXZpb3VzIHBvaW50LCBzOS4xLjEgaW1wbGllcyB0aGF0DQp0aGUgc3lz
dGVtIGNhbiBvcGVyYXRlIGhhcHBpbHkgd2l0aCBzb21lIHN1YnNldCBvZiB0aGUgZml2ZSBjYXBh
YmlsaXRpZXMNCnR1cm5lZCBvbiBwcm92aWRlZCB0aGF0IGJvdGggZW5kcyBjb25jdXIuICBIb3dl
dmVyIHRoZXJlIGlzIG5vIG1vZGUgbmFtZQ0KdGhhdCB3b3VsZCBjb3ZlciBzdWNoIGEgc3Vic2V0
Lg0KDQoNCg0KW0h1dWJdIGFzIGluZGljYXRlZCBhYm92ZSwgdGhlIG1vZGUgbmFtZSBkb2VzIG5v
dCBleGlzdCBiZWNhdXNlIHRoZQ0KDQpkcmFmdCB0aGF0IGRlc2NyaWJlcyB0aGF0IG1vZGUgZG9l
cyBub3QgKHlldCkgZXhpc3QuDQoNCg0KDQpEb2VzIHRoaXMgYWN0dWFsbHkgbWVhbiB0aGF0IHR1
cm5pbmcgb24NCmEgc3Vic2V0IGRvZXNuJ3QgcmVhbGx5IHdvcms/DQoNCg0KDQpbSHV1Yl0gaW5k
ZWVkLCBub3QgdW50aWwgdGhlcmUgaXMgYSBkcmFmdCB0aGF0IGRlc2NyaWJlcyBpdC4NCg0KDQoN
CkFuZCBpZiBpdCBkb2Vzbid0IHdvcmsgd2h5IGJvdGhlciB3aXRoDQpmaXZlIGZsYWcgYml0cz8N
Cg0KDQoNCltIdXViXSB0byBnaXZlIG90aGVycyB0aGUgb3Bwb3J0dW5pdHkgdG8gd3JpdGUgdGhl
IG1pc3NpbmcgZHJhZnQocyksIHRoaXMNCg0Kd2FzIHRoZSBhZ3JlZWQgYnkgdGhlIFdHIGNoYWly
cy4NCg0KDQoNCkFsc28gdGhlIHBocmFzZW9sb2d5IHVzZWQgaGVyZSBjb3VsZCBsZWFkIHRvIGZ1
dHVyZQ0KcHJvYmxlbXMgaWYgbW9yZSBjYXBhYmlsaXRpZXMgYXJlIGRlZmluZWQ6ICBzdXBwb3Nl
IHNvbWUgZnV0dXJlIG5ldyBtb2RlDQooRk9PKSBhZGRzIDxuPiBtb3JlIGNhcGFiaWxpdGllcyBi
dXQgdGhlIHR3byAnbW9kZXMnIGNhbiBiZSB0dXJuZWQgb24NCmluZGVwZW5kZW50bHkgLSBhcyBj
dXJyZW50bHkgZXhwcmVzc2VkIHlvdSB3b3VsZCBoYXZlIHRvIGRlZmluZSB0aHJlZQ0KbW9kZSBu
YW1lcyBmb3IgQVBTIG9ubHksIEZPTyBvbmx5IGFuZCBBUFMgKyBGT08uLiBhbmQgc28gb24gd2l0
aCBtb3JlDQpjYXBhYmlsaXR5IHNldHMuICBVbmludGVuZGVkIGNvbnNlcXVlbmNlPyBPaCwgYW5k
IHdoYXQgaWYgYSBjYXBhYmlsaXR5DQppcyB1c2VkIGluIG1vcmUgdGhhbiBvbmUgbW9kZT8NCg0K
DQoNCltIdXViXSBpdCBpcyB1cCB0byB0aGUgYXV0aG9ycyBvZiBhZGRpdGlvbmFsIGRyYWZ0cyB0
byBjb21lIHVwIHdpdGggYSBuYW1lDQoNCmZvciB0aGUgbW9kZSBkZXNjcmliZWQgaW4gdGhlaXIg
ZHJhZnQuDQoNCnM4OiBFWEVSIGFwcGVhcnMgdG8gdGVzdCB0aGUgUFNDIGNoYW5uZWwgYnV0IG5v
dGhpbmcgZWxzZS4gIEkgYW0gbm90DQpjbGVhciB0aGF0IHRoaXMgZnVsbHkgc2F0aXNmaWVzIFI4
NCBpbiBSRkMgNTY1NC4NCg0KDQoNCltIdXViXSBFWEVSIHZlcmlmaWVzIHRoYXQgdGhlIFBTQyBl
bmdpbmUgYXQgdGhlIGZhciBlbmQgaXMgc3RpbGwgcnVubmluZw0KDQpwcm9wZXJseSBhbmQgbm90
IHN0dWNrIGF0IHNlbmRpbmcgdGhlIHNhbWUgUFNDIG1lc3NhZ2UgY29udGludW91c2x5Lg0KDQpU
aGUgUFNDIGNoYW5uZWwgaXMgdGVzdGVkIGJ5IHNlbmRpbmcgUFNDIG1lc3NhZ2VzIHJlZ3VsYXJs
eS4NCg0KKHNlZSBSRkM2Mzc4IHM0LjEpDQoNCg0KDQpJdCBtYXkgYmUgdGhhdCBJIGRvbid0DQpr
bm93IHdoYXQgaW5mb3JtYXRpb24gd291bGQgZ28gYmFjayBpbiB0aGUgUlIgcmVzcG9uc2UsIGJ1
dCBzaG91bGQgdGhlDQpyZXNwb25zZSBzYXkgYW55dGhpbmcgYWJvdXQgdGhlIHN0YXRlIGluIHRo
ZSByZW1vdGUgbm9kZSAobGlrZSB0aGUNCnJlbW90ZSBlbmQgb2YgdGhlIHdvcmtpbmcgcGF0aCBp
cyBub3Qgd29ya2luZyBpbiBzb21lIHdheSBhbmQvb3Igd2hhdCBpcw0KdGhlIFBTQyBzdGF0ZSAt
IFJGQyA2Mzc4IHMzLjYpPw0KDQoNCg0KW0h1dWJdIHRoZSBmYWN0IHRoYXQgUlIgaXMgcmVjZWl2
ZWQgYWZ0ZXIgc2VuZGluZyBFWEVSIGlzIHByb29mIHRoYXQgdGhlDQoNClBTQyBlbmdpbmUgaXMg
aGVhbHRoeS4gSWYgaXQgd2FzIG5vdCBoZWFsdHkgaXQgd291bGQgbm90IGhhdmUgc2VudCB0aGUg
UlIuDQoNCkJlY2F1c2UgRVhFUiBoYXMgdGhlIGxvd2VzdCBwcmlvcml0eSBpcyBjYW4gb25seSBi
ZSB1c2VkIGluIHRoZSBJRExFDQoNCnN0YXRlLCBzbyB0aGUgZmFyIGVuZCBjb3VsZCBvbmx5IHNl
bmQgb25lIHN0YXRlLg0KDQpzMTM6IFRoZSBhZGRpdGlvbiBvZiB0aGUgQ2FwYWJpbGl0aWVzIFRM
ViBhbmQgdGhlIHJlcXVpcmVtZW50IHRoYXQgaXQgaXMNCmNhcnJpZWQgYWNjdXJhdGVseSBhbmQg
cmVwZWF0ZWRseSBpbiBldmVyeSBQU0MgbWVzc2FnZSBpbnRyb2R1Y2VzIGEgbmV3DQphc3BlY3Qg
dG8gdGhlIERvUy9yYW5kb20gY29ycnVwdGlvbiBwcm9ibGVtIG1lbnRpb25lZCBpbiBzNiBvZiBS
RkMgNjM3OC4NCkEgc2luZ2xlIGJpdCBjb3JydXB0aW9uIGluIGEgUFNDIG1lc3NhZ2Ugd2lsbCBs
ZWFkIHRvIGRpc2FibGVtZW50IG9mDQpwcm90ZWN0aW9uIHN3aXRjaGluZyBhbmQgcmVxdWlyZW1l
bnQgb2Ygb3BlcmF0b3IgaW50ZXJ2ZW50aW9uLiAgSSBhbSBub3QNCnN1cmUgaWYgdGhpcyBpcyBh
IHNlcmlvdXMgaXNzdWUsIGJ1dCBpdCBwcm9iYWJseSBtZXJpdHMgYSBjb21tZW50IGluIHMxMw0K
YW5kIHZlcmlmaWNhdGlvbiB0aGF0IGl0IGRvZXMgbWF0Y2ggd2l0aCB0aGUgd29yZHMgaW4gUkZD
IDYzNzggYXMNCnJlZ2FyZHMgJ2NvbnZlcmdpbmcgb24gYSBzdGFibGUgc3RhdGUnLg0KDQoNCg0K
W0h1dWJdIGEgYml0IGVycm9yIHdpbGwgb2NjdXIgaW4gb25lIG1lc3NhZ2UsIFJGQzYzNzggczQu
MSBhZGRyZXNzZXMNCg0KdGhhdCBpc3N1ZS4NCg0KTml0cy9lZGl0b3JpYWwgY29tbWVudHM6DQpz
NC40LCB0aXRsZTogcy9DYXBhYmlsaXR5IDEvUHJpb3JpdHkgTW9kaWZpY2F0aW9ucy8gKE9rLCBp
dHMgYWNjdXJhdGUNCmJ1dCBiYWxkKQ0KDQoNCg0KW0h1dWJdIE9LLg0KDQpzNy4zIGV0IHNlcTog
VGhlIHRlcm0gInNlbGVjdG9yIGJyaWRnZSIgaXMgaW50cm9kdWNlZCB3aXRob3V0DQpkZWZpbml0
aW9uLiAgSSBzdXNwZWN0IGl0IGlzIGEgcGllY2Ugb2YgamFyZ29uIEkgYW0gc3VwcG9zZWQgdG8g
a25vdyBidXQNCkkgdGhpbmsgYSByZWZlcmVuY2Ugd291bGQgaGVscC4NCg0KDQoNCltIdXViXSBS
RkM2Mzc4IHVzZXMgInNlbGVjdG9yIiwgInNlbGVjdG9yIGJyaWRnZSIgaXMgdGhlIGVxdWl2YWxl
bnQgSVRVIHRlcm0uDQoNCnM3LjQsIHBhcmEgMToNCg0KPiB0aGUgcnVsZXMgdG8gcmVzb2x2ZSB0
aGUgZXF1YWwgcHJpb3JpdHkgcmVxdWVzdHMgYXJlDQo+ICAgIHJlcXVpcmVkLg0KU2hvdWxkIHRo
aXMgYmUgcy90aGUgcnVsZXMvc29tZSBydWxlcy8/DQoNCg0KDQpbSHV1Yl0gb3Igcy90aGUgcnVs
ZXMvcnVsZXMvDQoNCnM4LCBkZWZpbml0aW9uIG9mIEV4ZXJjaXNlIChFWEVSKTogRGVzY3JpYmlu
ZyBFWEVSIGFzICdyZXBsYWNpbmcnIG9uZSBvZg0KTlIsIFJSIG9yIEROUiBzZWVtcyBhIGJpdCBv
ZGQuICBNZW50aW9uaW5nIFJSIGlzIHBhcnRpY3VsYXJseQ0KcHJvYmxlbWF0aWMgc2luY2UgaXQg
bWFrZXMgdGhlIGRlZmluaXRpb25zIHNvcnQgb2YgY2lyY3VsYXIgYXMgUlIgaXMgdGhlDQpyZXNw
b25zZSB0byBFWEVSLiAgSSBndWVzcyB3aGF0IGlzIHByb2JhYmx5IGFwcHJvcHJpYXRlIGlzIHRv
IHNheSB0aGF0DQppdCBpcyBidWlsdCBpbiB0aGUgc2FtZSB3YXkgYXMgYW4gTlIgbWVzc2FnZSB3
b3VsZCBiZSBidWlsdC4NCg0KW0h1dWJdIHRoZSAicmVwbGFjaW5nIiBtZWFucyB0aGF0IGluIGNh
c2UgYW4gb3BlcmF0b3Igd2FudHMgdG8gdmVyaWZ5DQoNCnRoZSBvcGVyYXRpb24gb2YgUFNDLCB0
aGUgZXhjZXJzaXNlIGNvbW1lbmQgaXMgaXNzdWVkIGFuZCB0aGUNCg0KdHJhbnNtaXNzaW9uIG9m
IFJSIChvciBOUiwgb3IgRE5SKSBpcyBzdG9wcGVkIGFuZCBFWEVSIGlzIHNlbnQgaW5zdGVhZC4N
Cg0KDQoNCnM5LjE6IFJGQyA2Mzc4IGRvZXNuJ3QgZGVmaW5lIHRoZSBlbmNvZGluZyBvZiB0aGUg
VExWIHR5cGUgYW5kIFRMVg0KbGVuZ3RoIGZpZWxkcywgc28gaXQgbmVlZHMgdG8gYmUgZG9uZSBo
ZXJlIChVbnNpZ25lZCBpbnRlZ2VycykuIChJdCBhbHNvDQpkb2Vzbid0IGRlZmluZSBlbmNvZGlu
ZyBvZiB0aGUgKHVubmVjZXNzYXJ5KSBvdmVyYWxsIFRMViBsZW5ndGggZmllbGQgaW4NCnRoZSBQ
U0MgaGVhZGVyLg0KDQoNCg0KW0h1dWJdIElBTkEgYXNpZ25lZCB0aGUgVExWIHR5cGUgdmFsdWUu
IEJ5IG5vdCBnaXZpbmcgZXhhY3QgdmFsdWVzDQoNCndlIGxlYXZlIHRoZSBwb3NzaWJpbGl0eSBv
cGVuIHRoYXQgdGhlcmUgYXJlIG1vcmUgdGhhbiAzMiBmbGFncy4NCg0KczkuMTogV2hhdCBoYXBw
ZW5zIGlmIHRoZSByZWNlaXZlciBnZXRzIGEgVExWIHdpdGggc29tZSBhIGZsYWdzIGxlbmd0aA0K
dGhhdCBpc24ndCBhIG11bHRpcGxlIG9mIDQgKG9yIGluZGVlZCBhIFRMViBpdCBkZW9zbid0IHJl
Y29nbml6ZT8pICBJdA0KbWlnaHQgYmUgY2xlYW5lciB0byBkZWZpbmUgdGhlIGxlbmd0aCBpbiB0
ZXJtcyBvZiB1bml0cyBvZiAzMiBiaXRzLg0KDQoNCg0KW0h1dWJdIHRoaXMgY2FuIGJlIHRyZWF0
ZWQgdGhlIHNhbWUgYXMgYSBiaXQgZXJyb3IgaW4gYSBQU0MgbWVzc2FnZS4NCg0KczEwLjMsIHBh
cmEgMjogcy90aGV5IFNIQUxMIGJlIGRpc2FwcGVhcmVkLi90aGV5IFNIQUxMIGJlIGRpc2NhcmRl
ZC4vDQoNCg0KDQpbSHV1Yl0gT0suDQoNCg0KDQpDaGVlcnMsIEh1dWIuDQoNCg0KDQotLQ0KSHV1
YiB2YW4gSGVsdm9vcnQsILqjuN/D9w0KU2VuaW9yIENvbnN1bHRhbnQsILjfvLa5y87KDQpIdWF3
ZWkgVGVjaG5vbG9naWVzIEx0ZCwgu6rOqry8yvXT0M/euavLviAtIEV1cm9wZWFuIFJlc2VhcmNo
IENlbnRlciwgxbfW3tHQvr/L+Q0KS2Fyc3BlbGRyZWVmIDQsIDExMDFDSiBBbXN0ZXJkYW0sIFRo
ZSBOZXRoZXJsYW5kcw0KVGVsOiArMzEgMjAgNDMwMCA5MzYgICBNb2I6ICszMSA2IDQ5MjQ4OTM2
DQo=

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

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<style id=3D"owaParaStyle">P {
	MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px
}
</style>
</head>
<body fPStyle=3D"1" ocsi=3D"0">
<div style=3D"direction: ltr;font-family: Arial;color: #000000;font-size: 1=
0pt;">
<p>Hello Elwyn,</p>
<p>&nbsp;</p>
<p>Thank you for your review.</p>
<p>&nbsp;</p>
<p>See my response in-line [<font style=3D"BACKGROUND-COLOR: #ffff00">Huub<=
/font>]<br>
<br>
I am the assigned Gen-ART reviewer for this draft. For background on<br>
Gen-ART, please see the FAQ at<br>
<br>
&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.<br>
<br>
Please resolve these comments along with any other Last Call comments<br>
you may receive.<br>
<br>
Document: draft-ietf-mpls-tp-psc-itu-02.txt<br>
Reviewer: Elwyn Davies<br>
Review Date: 24 Feb 2014<br>
IETF LC End Date: 24 Feb 2014<br>
IESG Telechat date: (if known) -<br>
<br>
Summary:<br>
Almost Ready for IESG.&nbsp; There is a statement in s1 that could indicate=
<br>
that the consequences of turning on a subset of the new capabilities has<br=
>
not been fully thought through.&nbsp; I am also not clear whether EXER<br>
fulfils the intentions of R84 in RFC 5654 as stated.&nbsp; The repeated<br>
transmission of the advertised capabilities adds to the scope for random<br=
>
bit errors to halt protection operation.&nbsp; A few minor nits noted below=
.<br>
</p>
<p>[<font style=3D""><font style=3D"BACKGROUND-COLOR: #ffff99"><font style=
=3D"">Huub</font>] I have addressed these below.</font></font></p>
<p><br>
Major issues:<br>
None<br>
<br>
Minor issues:<br>
s1, next to last para:<br>
<br>
&gt;&nbsp;&nbsp;&nbsp; This document describes the behavior of the PSC prot=
ocol including<br>
&gt;&nbsp;&nbsp;&nbsp; the priority logic and the state machine when all th=
e capabilities<br>
&gt;&nbsp;&nbsp;&nbsp; associated with the APS mode are enabled.&nbsp; The =
PSC protocol behavior<br>
&gt;&nbsp;&nbsp;&nbsp; for the PSC mode is as defined in RFC 6378.<br>
<br>
APS mode involves five capabilities which can, apparently, be<br>
implemented and advertised indpendently, so presumably there might be<br>
reasons for either implementing or turning on just a subset.&nbsp;</p>
<p>&nbsp;</p>
<p>[<font style=3D""><font style=3D"BACKGROUND-COLOR: #ffff99"><font style=
=3D"">Huub</font>] There were originally separate drafts for each of the ca=
pabilities.</font></font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99" size=3D"3" face=3D"Times New R=
oman">However, it was very complex to define the effect on the state</font>=
</p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99" size=3D"3" face=3D"Times New R=
oman">transition tables for each capability or combination of capabilities.=
</font></p>
<p><font size=3D"3" face=3D"Times New Roman"></font>&nbsp;</p>
<p><font size=3D"3" face=3D"Times New Roman">[<font style=3D"BACKGROUND-COL=
OR: #ffff99">Huub] to resolve this issue it was deceided that for any permi=
tation</font></font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99" size=3D"3" face=3D"Times New R=
oman">of the possible combinations of capabilities a separate draft should =
be</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99" size=3D"3" face=3D"Times New R=
oman">developed. RFC6378 is the one where none of the capabilities is</font=
></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99" size=3D"3" face=3D"Times New R=
oman">used, and this draft is the one where all capabiliies are used. So fa=
r</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99" size=3D"3" face=3D"Times New R=
oman">none of the other possible drafts is written.</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99" size=3D"3" face=3D"Times New R=
oman"></font>&nbsp;</p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99" size=3D"3" face=3D"Times New R=
oman">[Huub] This draft provides the behavior similar to APS used in ITU-T<=
/font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99" size=3D"3" face=3D"Times New R=
oman">for other technologies.</font></p>
<p><font size=3D"3" face=3D"Times New Roman"></font>&nbsp;</p>
<p>Are there</p>
<p>any implications for the PSC protocol if only some subset of the the<br>
capabilities are available in a given node?&nbsp; (This may be a dumb<br>
question and I haven't tried to work out what might go wrong if you did<br>
have any of the available subsets.)</p>
<p>&nbsp;</p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">[Huub] both nodes MUST support=
 the same subset, if they don't the</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">result will be unpredictable b=
ecause the state machines are different.</font><br>
<br>
s9.1.1/s9.2: Following on from the previous point, s9.1.1 implies that<br>
the system can operate happily with some subset of the five capabilities<br=
>
turned on provided that both ends concur.&nbsp; However there is no mode na=
me<br>
that would cover such a subset.</p>
<p>&nbsp;</p>
<p>[<font style=3D"BACKGROUND-COLOR: #ffff99">Huub] as indicated above, the=
 mode name does not exist because the</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">draft that describes that mode=
 does not (yet) exist.</font></p>
<p>&nbsp;</p>
<p>Does this actually mean that turning on<br>
a subset doesn't really work?</p>
<p>&nbsp;</p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">[Huub] indeed, not until there=
 is a draft that describes it.</font></p>
<p>&nbsp;</p>
<p>And if it doesn't work why bother with<br>
five flag bits?</p>
<p>&nbsp;</p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">[Huub] to give others the oppo=
rtunity&nbsp;to write the&nbsp;missing draft(s), this</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">was the agreed by the WG chair=
s.</font></p>
<p>&nbsp;</p>
<p>Also the phraseology used here could lead to future<br>
problems if more capabilities are defined:&nbsp; suppose some future new mo=
de<br>
(FOO) adds &lt;n&gt; more capabilities but the two 'modes' can be turned on=
<br>
independently - as currently expressed you would have to define three<br>
mode names for APS only, FOO only and APS &#43; FOO.. and so on with more<b=
r>
capability sets.&nbsp; Unintended consequence? Oh, and what if a capability=
<br>
is used in more than one mode?</p>
<p>&nbsp;</p>
<p>[<font style=3D"BACKGROUND-COLOR: #ffff99">Huub] it is up to the authors=
 of additional drafts to come up with a name</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">for the mode described in thei=
r draft.</font><br>
<br>
s8: EXER appears to test the PSC channel but nothing else.&nbsp; I am not<b=
r>
clear that this fully satisfies R84 in RFC 5654.</p>
<p>&nbsp;</p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">[Huub]&nbsp;EXER verifies that=
 the PSC engine at the far end is still running</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">properly and not stuck at send=
ing the same PSC message continuously.</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">The PSC channel is tested by s=
ending PSC messages regularly.</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">(see RFC6378 s4.1)</font></p>
<p>&nbsp;</p>
<p>It may be that I don't<br>
know what information would go back in the RR response, but should the<br>
response say anything about the state in the remote node (like the<br>
remote end of the working path is not working in some way and/or what is<br=
>
the PSC state - RFC 6378 s3.6)?</p>
<p>&nbsp;</p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">[Huub] the fact that RR is rec=
eived after sending EXER is proof that the</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">PSC engine is healthy. If it w=
as not healty it would not have sent the RR.</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">Because EXER has the lowest pr=
iority is can only be used in the IDLE</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">state, so the far end could on=
ly send one state.</font></p>
<p><br>
s13: The addition of the Capabilities TLV and the requirement that it is<br=
>
carried accurately and repeatedly in every PSC message introduces a new<br>
aspect to the DoS/random corruption problem mentioned in s6 of RFC 6378.<br=
>
A single bit corruption in a PSC message will lead to disablement of<br>
protection switching and requirement of operator intervention.&nbsp; I am n=
ot<br>
sure if this is a serious issue, but it probably merits a comment in s13<br=
>
and verification that it does match with the words in RFC 6378 as<br>
regards 'converging on a stable state'.</p>
<p>&nbsp;</p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">[Huub] a bit error will occur =
in one message, RFC6378 s4.1 addresses</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">that issue.</font><br>
<br>
Nits/editorial comments:<br>
s4.4, title: s/Capability 1/Priority Modifications/ (Ok, its accurate<br>
but bald)</p>
<p>&nbsp;</p>
<p>[<font style=3D"BACKGROUND-COLOR: #ffff99">Huub] OK.<br>
</font><br>
s7.3 et seq: The term &quot;selector bridge&quot; is introduced without<br>
definition.&nbsp; I suspect it is a piece of jargon I am supposed to know b=
ut<br>
I think a reference would help.</p>
<p>&nbsp;</p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">[Huub] RFC6378 uses &quot;sele=
ctor&quot;, &quot;selector bridge&quot; is the equivalent ITU term.</font><=
br>
<br>
s7.4, para 1:<br>
<br>
&gt; the rules to resolve the equal priority requests are<br>
&gt;&nbsp;&nbsp;&nbsp; required.<br>
Should this be s/the rules/some rules/?</p>
<p>&nbsp;</p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">[Huub] or s/the rules/rules/</=
font></p>
<p><br>
s8, definition of Exercise (EXER): Describing EXER as 'replacing' one of<br=
>
NR, RR or DNR seems a bit odd.&nbsp; Mentioning RR is particularly<br>
problematic since it makes the definitions sort of circular as RR is the<br=
>
response to EXER.&nbsp; I guess what is probably appropriate is to say that=
<br>
it is built in the same way as an NR message would be built.<br>
</p>
<p>[<font style=3D"BACKGROUND-COLOR: #ffff99">Huub] the &quot;replacing&quo=
t; means that in case an operator wants to verify</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">the operation of PSC, the exce=
rsise commend is issued and the
</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">transmission of RR (or NR, or =
DNR) is stopped and&nbsp;EXER is sent instead.</font></p>
<p>&nbsp;</p>
<p>s9.1: RFC 6378 doesn't define the encoding of the TLV type and TLV<br>
length fields, so it needs to be done here (Unsigned integers). (It also<br=
>
doesn't define encoding of the (unnecessary) overall TLV length field in<br=
>
the PSC header.</p>
<p>&nbsp;</p>
<p>[<font style=3D"BACKGROUND-COLOR: #ffff99">Huub] IANA asigned the TLV ty=
pe value. By not giving exact values</font></p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">we leave the possibility open =
that there are more than 32 flags.<br>
</font><br>
s9.1: What happens if the receiver gets a TLV with some a flags length<br>
that isn't a multiple of 4 (or indeed a TLV it deosn't recognize?)&nbsp; It=
<br>
might be cleaner to define the length in terms of units of 32 bits.</p>
<p>&nbsp;</p>
<p><font style=3D"BACKGROUND-COLOR: #ffff99">[Huub] this can be treated the=
 same as a bit error in a PSC message.&nbsp;</font><br>
<br>
s10.3, para 2: s/they SHALL be disappeared./they SHALL be discarded./</p>
<p>&nbsp;</p>
<p>[<font style=3D"BACKGROUND-COLOR: #ffff99">Huub] OK</font>.</p>
<p>&nbsp;</p>
<p>Cheers, Huub.</p>
<p>&nbsp;</p>
<p>--<br>
Huub van Helvoort, =BA=A3=B8=DF=C3=F7<br>
Senior Consultant, =B8=DF=BC=B6=B9=CB=CE=CA<br>
Huawei Technologies Ltd, =BB=AA=CE=AA=BC=BC=CA=F5=D3=D0=CF=DE=B9=AB=CB=BE -=
 European Research Center, =C5=B7=D6=DE=D1=D0=BE=BF=CB=F9<br>
Karspeldreef 4, 1101CJ Amsterdam, The Netherlands<br>
Tel: &#43;31 20 4300 936&nbsp;&nbsp; Mob: &#43;31 6 49248936</p>
</div>
</body>
</html>

--_000_74118A81AEACB94EB8AB398AF85AF7820C556Flhreml511mbs_--


From nobody Mon Feb 24 13:54:39 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 060C41A02FA for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 13:54:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Da586BfRabHy for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 13:54:36 -0800 (PST)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 631A61A02B5 for <gen-art@ietf.org>; Mon, 24 Feb 2014 13:54:36 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id uy5so7985862obc.33 for <gen-art@ietf.org>; Mon, 24 Feb 2014 13:54:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:content-type; bh=cstd+UD4eN0vkiqn8gym2lbMfmjz4S6Iu3FQeyNAquU=; b=0Vttn4FC8d62TjkaIHTysAfYF14zZUpvYI6wNBcTNnTQg6xzqfnyshbVR72f0Z+YrV scTc+9GNWqUfajBq8WBCGUOwxtaRxbx3k0vW4MZ4C3GdLR6FAvbQoS6S9wMaax+zK2pb 0V88O2D9Iyo+bXz7Swb8n82Py/oQbkM7+aT0mFyKZBb0I0MdkpoqlHbINNbIB+hD9Ieh tFpqiNE0wEIWfeXUoP9HOSkxBoxwyg9MqVy4QPhRgCuvUyJkmAZT8d8n09uedpibjiTF vYIaWTVCVOhuGKeRH6+wF1rYkWbwFJk4MinDQrDGbsCUxJ6NL/0S7iU1HD1p7suKJZIR 7wjQ==
X-Received: by 10.60.44.8 with SMTP id a8mr23775942oem.19.1393278875663; Mon, 24 Feb 2014 13:54:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 24 Feb 2014 13:54:15 -0800 (PST)
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 24 Feb 2014 16:54:15 -0500
Message-ID: <CAPv4CP9EyObfbq77NeD2cSdyyCQ7Z7OY1ZuMciopr-MjQvRT4Q@mail.gmail.com>
To: draft-vanelburg-dispatch-private-network-ind-05.all@tools.ietf.org,  gen-art <gen-art@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/WYxfey6rxwsvcKi6bHD2Bgsm4cY
Subject: [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: Mon, 24 Feb 2014 21:54:38 -0000

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

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

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

Document: draft-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:


From nobody Mon Feb 24 13:57:41 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 00CB11A02B5 for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 13:57:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oliIEPQtLhvO for <gen-art@ietfa.amsl.com>; Mon, 24 Feb 2014 13:57:39 -0800 (PST)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id D82EC1A0185 for <gen-art@ietf.org>; Mon, 24 Feb 2014 13:57:38 -0800 (PST)
Received: by mail-ob0-f177.google.com with SMTP id wp18so7790585obc.36 for <gen-art@ietf.org>; Mon, 24 Feb 2014 13:57:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:content-type; bh=cstd+UD4eN0vkiqn8gym2lbMfmjz4S6Iu3FQeyNAquU=; b=DfNpjSWJm1sTOJwK4lQAkwW6/kJBgh66VO5Y0s/IUBsz5FhVu4VZlNEasC8FzsQlAY 0gIfgesY/5GjNr7X6zanNn07c2V3cYPD5df6frLmypumACTp0WwSiUNJV+ceFVhuhTRm 3ElHpcuM1eY7g8l8cDgDPr0zTvzzgjSClBPsYrm3vexQUP4nl6/X/vndlUnYLphXhlJG /0g4zLiGLP/Hk6kPl/DNI8ZSeh+kEMZ9gIOQvpPUXlmLw5e7K03xohO7gZFucxHD6zBQ KvcUETvTDkr7Asv1PiN47Kk0H0vOQiz0HEUkSKXFSI/OxVhT4qpt+PjgL5pCRVhTXDw/ oQaw==
X-Received: by 10.183.24.161 with SMTP id ij1mr19469374obd.33.1393279058207; Mon, 24 Feb 2014 13:57:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 24 Feb 2014 13:57:18 -0800 (PST)
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 24 Feb 2014 16:57:18 -0500
Message-ID: <CAPv4CP-r9xDefNDxkF7v3DbET9hM9jiYiAX2Pc2HgHdD1RjwNA@mail.gmail.com>
To: gen-art <gen-art@ietf.org>,  draft-vanelburg-dispatch-private-network-ind.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/8BRiLmfiA1wEBxRn1XtSx7ABIXM
Subject: [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: Mon, 24 Feb 2014 21:57:40 -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-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:


From nobody Mon Feb 24 15:38:17 2014
Return-Path: <h.anthony.chan@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 42AA01A0223; Mon, 24 Feb 2014 14:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 mLBGKoaZvzzF; Mon, 24 Feb 2014 14:49:26 -0800 (PST)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 951B41A02EE; Mon, 24 Feb 2014 14:49:26 -0800 (PST)
Received: by mail-ig0-f171.google.com with SMTP id l13so816018iga.4 for <multiple recipients>; Mon, 24 Feb 2014 14:49:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:reply-to:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:importance; bh=WS/Sjd6xmHUujIHY+L/QhViJWBZ79wxfH9uiCnxsXLs=; b=ou7TWmFy/x9njI2rs10DkQkMpllWVxoXhfxligcGFswb/0LjdbbeeClkD96WEV5IQe 6sKet/eUI7rDOe+qTzVLuoD7PAP6Y9o1gmGtDKNriV3+0ajEgqPVXvfligGodaTx/y0t LDFlTVO3X1mbSxj3Lhd+kwzdhMw3QLKdxKztB2FG8JkFCLeJEHATGn0+ejEPnfQLQA3l iJBUHx2Mf9TFL1fWUjPrdY0M4slHHnT5cdI2tEemAFIzJYG5qUTpkdbLyoQ6UjA4ONU1 HwPUsPQHeQlzTw4UG4x2F424riNwwz+TAKirWF2IjBr9b/FZdr8p8gL/zE+cxYlCcYUN 4nMg==
X-Received: by 10.42.231.5 with SMTP id jo5mr16928309icb.23.1393282165723; Mon, 24 Feb 2014 14:49:25 -0800 (PST)
Received: from C73782TX02 ([50.58.7.243]) by mx.google.com with ESMTPSA id ro10sm30979825igb.6.2014.02.24.14.49.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 24 Feb 2014 14:49:25 -0800 (PST)
Message-ID: <4EDD3C94D45547DBBEE9AE54BD54FD44@china.huawei.com>
From: "H Anthony Chan" <h.anthony.chan@gmail.com>
To: "Russ Housley" <housley@vigilsec.com>, <draft-ietf-dmm-requirements.all@tools.ietf.org>
References: <53AC26FD-54C8-481E-8B3B-F529C26C0C20@vigilsec.com>
In-Reply-To: <53AC26FD-54C8-481E-8B3B-F529C26C0C20@vigilsec.com>
Date: Mon, 24 Feb 2014 16:49:23 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001E_01CF3180.5F24B5D0"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8117.416
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/GOqmr9_worsYYwtdGATUGbDuryA
X-Mailman-Approved-At: Mon, 24 Feb 2014 15:38:16 -0800
Cc: IETF Gen-ART <gen-art@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dmm-requirements-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: H Anthony Chan <h.a.chan@ieee.org>
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 22:49:29 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_001E_01CF3180.5F24B5D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks.

Regarding the first comment, the abstract can be elaborated a little =
more as follows:

   This document defines the requirements for Distributed Mobility
   Management (DMM) at the network layer.  The hierarchical structure in
   traditional wireless networks has led primarily to centrally deployed
   mobility anchors.  As some wireless networks are evolving away from
   the hierarchical structure, it can be useful have a distributed model
   for mobility management in which traffic does not need to traverse
   centrally deployed mobility anchors far from the optimal route.

Regarding the second comments on defining the acronyms:
It appears there are 3 such instances: EPC, 3GPP, WLAN. All other =
acronyms have been properly defined.=20

EPC needs to be spelled out before the acronym appears.
3GPP was spelled out in Section 3.1 but was also used in Section 1. It =
needs to move to Section 1.=20
WLAN is also spelled out.=20

H Anthony Chan

From: Russ Housley=20
Sent: Monday, February 10, 2014 1:51 PM
To: draft-ietf-dmm-requirements.all@tools.ietf.org=20
Cc: IESG ; IETF Gen-ART=20
Subject: Gen-ART review of draft-ietf-dmm-requirements-14


I am the assigned Gen-ART 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-dmm-requirements-14
Reviewer: Russ Housley
Review Date: 2014-02-10
IETF LC End Date: 2014-02-17
IESG Telechat date: Unknown

Summary:  Ready for publication.


Major Concerns:  None.


Minor Concerns:  None.


Other Comments:

I think that the Abstract could be more polished.  Some mention of the
anchor point seems desirable.

Spell out acronyms the first time they are used. EPC is an example that
needs to be expanded.
------=_NextPart_000_001E_01CF3180.5F24B5D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dunicode" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 10.00.9200.16736"></HEAD>
<BODY id=3DMailContainerBody=20
style=3D"PADDING-TOP: 15px; PADDING-LEFT: 10px; PADDING-RIGHT: 10px" =
leftMargin=3D0=20
topMargin=3D0 CanvasTabStop=3D"true" name=3D"Compose message area">
<DIV>Thanks.</DIV>
<DIV><BR>Regarding the first comment, the abstract can be elaborated a =
little=20
more as follows:<BR><BR>&nbsp;&nbsp; This document defines the =
requirements for=20
Distributed Mobility<BR>&nbsp;&nbsp; Management (DMM) at the network=20
layer.&nbsp; The hierarchical structure in<BR>&nbsp;&nbsp; traditional =
wireless=20
networks has led primarily to centrally deployed<BR>&nbsp;&nbsp; =
mobility=20
anchors.&nbsp; As some wireless networks are evolving away =
from<BR>&nbsp;&nbsp;=20
the hierarchical structure, it can be useful have a distributed=20
model<BR>&nbsp;&nbsp; for mobility management in which traffic does not =
need to=20
traverse<BR>&nbsp;&nbsp; centrally deployed mobility anchors far from =
the=20
optimal route.<BR><BR><FONT face=3DCalibri>Regarding the second comments =
on=20
defining the acronyms:</FONT></DIV>
<DIV><FONT face=3DCalibri>It appears there are 3 such instances: EPC, =
3GPP, WLAN.=20
All other acronyms have been properly defined. </FONT></DIV>
<DIV><FONT face=3DCalibri></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>EPC needs to be spelled out before the acronym =

appears.</FONT></DIV>
<DIV><FONT face=3DCalibri>3GPP was&nbsp;spelled out&nbsp;in Section 3.1 =
but was=20
also used in Section 1. It needs to move to Section 1. </FONT></DIV>
<DIV><FONT face=3DCalibri>WLAN is also spelled out. </FONT></DIV>
<DIV><FONT face=3DCalibri></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>H Anthony Chan</FONT><BR><BR>From: Russ =
Housley=20
<BR>Sent: Monday, February 10, 2014 1:51 PM<BR>To:=20
draft-ietf-dmm-requirements.all@tools.ietf.org <BR>Cc: IESG ; IETF =
Gen-ART=20
<BR>Subject: Gen-ART review of =
draft-ietf-dmm-requirements-14<BR><BR><BR>I am=20
the assigned Gen-ART reviewer for this draft. For background =
on<BR>Gen-ART,=20
please see the FAQ=20
at<BR>&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.<BR=
><BR>Please=20
resolve these comments along with any other Last Call comments<BR>you =
may=20
receive.<BR><BR>Document: draft-ietf-dmm-requirements-14<BR>Reviewer: =
Russ=20
Housley<BR>Review Date: 2014-02-10<BR>IETF LC End Date: =
2014-02-17<BR>IESG=20
Telechat date: Unknown<BR><BR>Summary:&nbsp; Ready for=20
publication.<BR><BR><BR>Major Concerns:&nbsp; None.<BR><BR><BR>Minor=20
Concerns:&nbsp; None.<BR><BR><BR>Other Comments:<BR><BR>I think that the =

Abstract could be more polished.&nbsp; Some mention of the<BR>anchor =
point seems=20
desirable.<BR><BR>Spell out acronyms the first time they are used. EPC =
is an=20
example that<BR>needs to be expanded.</DIV></BODY></HTML>

------=_NextPart_000_001E_01CF3180.5F24B5D0--


From nobody Tue Feb 25 03:19:15 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 8FA471A043A for <gen-art@ietfa.amsl.com>; Tue, 25 Feb 2014 03:19:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.035
X-Spam-Level: 
X-Spam-Status: No, score=-98.035 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, CN_BODY_457=0.011, CN_BODY_832=0.004, MIME_CHARSET_FARAWAY=2.45, 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 KDTld6jJZpP0 for <gen-art@ietfa.amsl.com>; Tue, 25 Feb 2014 03:19:09 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 5D8731A0316 for <gen-art@ietf.org>; Tue, 25 Feb 2014 03:19:09 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1WIG2P-0000SX-Nv; Tue, 25 Feb 2014 11:19:05 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Huub Van Helvoort <huub.van.helvoort@huawei.com>
In-Reply-To: <74118A81AEACB94EB8AB398AF85AF7820C556F@lhreml511-mbs>
References: <1393265494.8036.426.camel@mightyatom> <74118A81AEACB94EB8AB398AF85AF7820C556F@lhreml511-mbs>
Content-Type: text/plain; charset="gb2312"
Date: Tue, 25 Feb 2014 11:18:59 +0000
Message-Id: <1393327139.8036.458.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/VeIcAMLe8bZS8WSp9mXP11cv3Mw
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org" <draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-mpls-tp-psc-itu-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 11:19:14 -0000

On Mon, 2014-02-24 at 21:50 +0000, Huub Van Helvoort wrote:
> Hello Elwyn,
>=20
> =20
>=20
> Thank you for your review.
>=20
> =20
>=20
> See my response in-line [Huub]
>=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-mpls-tp-psc-itu-02.txt
> Reviewer: Elwyn Davies
> Review Date: 24 Feb 2014
> IETF LC End Date: 24 Feb 2014
> IESG Telechat date: (if known) -
>=20
> Summary:
> Almost Ready for IESG.  There is a statement in s1 that could indicate
> that the consequences of turning on a subset of the new capabilities
> has
> not been fully thought through.  I am also not clear whether EXER
> fulfils the intentions of R84 in RFC 5654 as stated.  The repeated
> transmission of the advertised capabilities adds to the scope for
> random
> bit errors to halt protection operation.  A few minor nits noted
> below.
>=20
>=20
> [Huub] I have addressed these below.
>=20
>=20
> Major issues:
> None
>=20
> Minor issues:
> s1, next to last para:
>=20
> >    This document describes the behavior of the PSC protocol
> including
> >    the priority logic and the state machine when all the
> capabilities
> >    associated with the APS mode are enabled.  The PSC protocol
> behavior
> >    for the PSC mode is as defined in RFC 6378.
>=20
> APS mode involves five capabilities which can, apparently, be
> implemented and advertised indpendently, so presumably there might be
> reasons for either implementing or turning on just a subset.=20
>=20
> =20
>=20
> [Huub] There were originally separate drafts for each of the
> capabilities.
>=20
> However, it was very complex to define the effect on the state
>=20
> transition tables for each capability or combination of capabilities.
>=20
> =20
>=20
> [Huub] to resolve this issue it was deceided that for any permitation
>=20
> of the possible combinations of capabilities a separate draft should
> be
>=20
> developed. RFC6378 is the one where none of the capabilities is
>=20
> used, and this draft is the one where all capabiliies are used. So far
>=20
> none of the other possible drafts is written.
>=20
> =20
>=20
> [Huub] This draft provides the behavior similar to APS used in ITU-T
>=20
> for other technologies.
>=20
> =20
>=20
> Are there
>=20
> any implications for the PSC protocol if only some subset of the the
> capabilities are available in a given node?  (This may be a dumb
> question and I haven't tried to work out what might go wrong if you
> did
> have any of the available subsets.)
>=20
> =20
>=20
> [Huub] both nodes MUST support the same subset, if they don't the
>=20
> result will be unpredictable because the state machines are different.
>=20
> s9.1.1/s9.2: Following on from the previous point, s9.1.1 implies that
> the system can operate happily with some subset of the five
> capabilities
> turned on provided that both ends concur.  However there is no mode
> name
> that would cover such a subset.
>=20
> =20
>=20
> [Huub] as indicated above, the mode name does not exist because the
>=20
> draft that describes that mode does not (yet) exist.
>=20
> =20
>=20
> Does this actually mean that turning on
> a subset doesn't really work?
>=20
> =20
>=20
> [Huub] indeed, not until there is a draft that describes it.
>=20
> =20
>=20
> And if it doesn't work why bother with
> five flag bits?
>=20
> =20
>=20
> [Huub] to give others the opportunity to write the missing draft(s),
> this
>=20
> was the agreed by the WG chairs.
>=20
> =20
>=20
> Also the phraseology used here could lead to future
> problems if more capabilities are defined:  suppose some future new
> mode
> (FOO) adds <n> more capabilities but the two 'modes' can be turned on
> independently - as currently expressed you would have to define three
> mode names for APS only, FOO only and APS + FOO.. and so on with more
> capability sets.  Unintended consequence? Oh, and what if a capability
> is used in more than one mode?
>=20
> =20
>=20
> [Huub] it is up to the authors of additional drafts to come up with a
> name
>=20
> for the mode described in their draft.

To be absolutely honest, my initial reaction to the above (i.e., right
back to the beginning of Minor Issues) went something like=20
"******** ARRRGGGGHHH! Choke!! Splutter!!!".

Be that as it may, if that is what is agreed then please could there be
some explanation in the document. Please!

>=20
> s8: EXER appears to test the PSC channel but nothing else.  I am not
> clear that this fully satisfies R84 in RFC 5654.
>=20
> =20
>=20
> [Huub] EXER verifies that the PSC engine at the far end is still
> running
>=20
> properly and not stuck at sending the same PSC message continuously.
>=20
> The PSC channel is tested by sending PSC messages regularly.
>=20
> (see RFC6378 s4.1)
>=20
> =20
>=20
> It may be that I don't
> know what information would go back in the RR response, but should the
> response say anything about the state in the remote node (like the
> remote end of the working path is not working in some way and/or what
> is
> the PSC state - RFC 6378 s3.6)?
>=20
> =20
>=20
> [Huub] the fact that RR is received after sending EXER is proof that
> the
>=20
> PSC engine is healthy. If it was not healty it would not have sent the
> RR.
Agreed.
>=20
> Because EXER has the lowest priority is can only be used in the IDLE
>=20
> state, so the far end could only send one state.
OK.. I rather thought that the requirement was looking for a bit more
information to be returned.

>=20
>=20
> s13: The addition of the Capabilities TLV and the requirement that it
> is
> carried accurately and repeatedly in every PSC message introduces a
> new
> aspect to the DoS/random corruption problem mentioned in s6 of RFC
> 6378.
> A single bit corruption in a PSC message will lead to disablement of
> protection switching and requirement of operator intervention.  I am
> not
> sure if this is a serious issue, but it probably merits a comment in
> s13
> and verification that it does match with the words in RFC 6378 as
> regards 'converging on a stable state'.
>=20
> =20
>=20
> [Huub] a bit error will occur in one message, RFC6378 s4.1 addresses
>=20
> that issue.

I don't think this covers the problem:
The last para of s6 of RFC 6378 says:

>    However, a new concern for this document is the accidental corruption
>    of messages (through faulty implementations or random corruption).
>    The main concern is around the Request, FPath, and Path fields as a
>    change to these fields would change the behavior of the peer end
>    point.  Although this document does not define a way to avoid a
>    change in network behavior upon receipt of a message indicating a
>    change in protection status, the transition between states will
>    converge on a known and stable behavior in the face of messages that
>    do not match reality.

This appears to imply that random bit errors can percolate up to the=20
protocol engine.  If the bit error affects the capability flag bits in the=20
Capability TLV then the behaviour specified in s9.1.1 would come into play:

>    When a node receives a Capabilities TLV it MUST compare it to its
>    most recent transmitted Capabilities TLV.  If the two are equal, the
>    protected domain is said to be running in the mode indicated by that
>    set of capabilities (see Section 9.2).  If the sent and received
>    Capabilities TLVs are not equal, this indicates a capabilities
>    mismatch.  When this happens, the node MUST alert the operator and
>    MUST NOT perform any protection switching until the operator resolves
>    the mismatch in the Capabilities TLV.

The result of such a corrupted bit would a.s. be a mismatch that should
be followed by a turn off of protection switching and operator alerting.

>=20
> Nits/editorial comments:
> s4.4, title: s/Capability 1/Priority Modifications/ (Ok, its accurate
> but bald)
>=20
> =20
>=20
> [Huub] OK.
>=20
> s7.3 et seq: The term "selector bridge" is introduced without
> definition.  I suspect it is a piece of jargon I am supposed to know
> but
> I think a reference would help.
>=20
> =20
>=20
> [Huub] RFC6378 uses "selector", "selector bridge" is the equivalent
> ITU term.
Can we tie them together then please?

>=20
> s7.4, para 1:
>=20
> > the rules to resolve the equal priority requests are
> >    required.
> Should this be s/the rules/some rules/?
>=20
> =20
>=20
> [Huub] or s/the rules/rules/
Either would help.

>=20
>=20
> s8, definition of Exercise (EXER): Describing EXER as 'replacing' one
> of
> NR, RR or DNR seems a bit odd.  Mentioning RR is particularly
> problematic since it makes the definitions sort of circular as RR is
> the
> response to EXER. =20

Any thoughts here?...

> I guess what is probably appropriate is to say that
> it is built in the same way as an NR message would be built.


>=20
>=20
> [Huub] the "replacing" means that in case an operator wants to verify
>=20
> the operation of PSC, the excersise commend is issued and the
>=20
> transmission of RR (or NR, or DNR) is stopped and EXER is sent
> instead.
>=20
I think I see what is going on noew=20
Perhaps adding something like the phrase "that would normally be sent
periodically in the IDLE state"=20
> =20
>=20
> s9.1: RFC 6378 doesn't define the encoding of the TLV type and TLV
> length fields, so it needs to be done here (Unsigned integers). (It
> also
> doesn't define encoding of the (unnecessary) overall TLV length field
> in
> the PSC header.
>=20
> =20
>=20
> [Huub] IANA asigned the TLV type value. By not giving exact values
>=20
> we leave the possibility open that there are more than 32 flags.
That's not the issue.  The problem is that the protocol does not specify
how the type and length numbers should be represented on the wire.  The
standard answer is unsigned integer in network bit order.
>=20
> s9.1: What happens if the receiver gets a TLV with some a flags length
> that isn't a multiple of 4 (or indeed a TLV it deosn't recognize?)  It
> might be cleaner to define the length in terms of units of 32 bits.
>=20
> =20
>=20
> [Huub] this can be treated the same as a bit error in a PSC message.
This should be stated.
> =20
>=20
> s10.3, para 2: s/they SHALL be disappeared./they SHALL be discarded./
>=20
> =20
>=20
> [Huub] OK.
>=20
> =20
>=20
> Cheers, Huub.
>=20
> =20
>=20
> --
> Huub van Helvoort, =BA=A3=B8=DF=C3=F7
> Senior Consultant, =B8=DF=BC=B6=B9=CB=CE=CA
> Huawei Technologies Ltd, =BB=AA=CE=AA=BC=BC=CA=F5=D3=D0=CF=DE=B9=AB=CB=BE=
 - European Research Center,
> =C5=B7=D6=DE=D1=D0=BE=BF=CB=F9
> Karspeldreef 4, 1101CJ Amsterdam, The Netherlands
> Tel: +31 20 4300 936   Mob: +31 6 49248936
>=20
>=20


From nobody Tue Feb 25 07:56:49 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 465261A00DF for <gen-art@ietfa.amsl.com>; Tue, 25 Feb 2014 07:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 H_XaSowlct9R for <gen-art@ietfa.amsl.com>; Tue, 25 Feb 2014 07:56:44 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id E98031A00A5 for <gen-art@ietf.org>; Tue, 25 Feb 2014 07:56:43 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id s1PFuYMj026640 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 25 Feb 2014 09:56:35 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s1PFuYtn002932 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 25 Feb 2014 09:56:34 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id s1PFuSib026785; Tue, 25 Feb 2014 09:56:30 -0600 (CST)
Message-ID: <530CBD74.1010201@bell-labs.com>
Date: Tue, 25 Feb 2014 09:57:40 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: draft-melnikov-smime-msa-to-mda@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/fnWFnzJI8weoLqbOpvLIkmBsfF4
Cc: General Area Review Team <gen-art@ietf.org>, Sean Turner <turners@ieca.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: [Gen-art] Gen-ART review of draft-melnikov-smime-msa-to-mda-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 15:56:46 -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-melnikov-smime-msa-to-mda-03
Reviewer: Vijay K. Gurbani
Review Date: Feb-25-2014
IETF LC End Date: Mar-05-2014
IESG Telechat date: Unknown

I must say that this draft was written with implementors in mind.
This is very refreshing.

Major: 0
Minor: 0
Nits:  4

This document is ready as a Proposed Standard.  Some minor nits follow:

Nits:

- S2.2, "Organizational policy and good security practice often
  require that messages be reviewed before they are released to
  external recipients."  Here, I suspect that organizational policy may
  require such a vetting but I would think that "good security practice"
  would not.  After all, unless a party is forced to do so (the
  "organizational policy" part), why would one party willingly subject
  its private communications to a third party before sending it
  to the recipient?  I would not consider that a third party reading
  my messages a "good security practice".  Therefore, I would take
  the "good security practice" phrase out, unless of course, there is
  some context to that phrase that I am not privy to.

- S3.3, first sentence: "A 'domain signature' is a signature generated
  on behalf of a set of users in the domain the users are a member of."
  This sentence appears rather, for the lack of a better word, clunky.
  How about rewriting this as: "A 'domain signature' is a signature
  generated on behalf of a set of users who belong to the specific
  domain."

- S5, steps 3-A and 3-B: s/found then/found, then/
  There are some more occurences of this, if you feel like it, you may
  want to change these to have a comma as well.

- S7, first paragraph: s/permits masquerade./permits masquerading./
   or, s/permits masquerade attacks./

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 Tue Feb 25 09:24:01 2014
Return-Path: <h.anthony.chan@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 1CC2A1A00A9; Tue, 25 Feb 2014 09:23:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.144
X-Spam-Level: **
X-Spam-Status: No, score=2.144 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_ASCII_ART_SPACINGc=0.833, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_28=0.6, SPF_PASS=-0.001, T_FREEMAIL_DOC_PDF=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 7MHRRRLImyf5; Tue, 25 Feb 2014 09:23:45 -0800 (PST)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5A81F1A0118; Tue, 25 Feb 2014 09:23:44 -0800 (PST)
Received: by mail-ig0-f170.google.com with SMTP id uq10so51540igb.1 for <multiple recipients>; Tue, 25 Feb 2014 09:23:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:reply-to:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:importance; bh=1Jsrexq1lR4F0xLAfMxr4HNDCnYserOlwhZeRwnyfks=; b=Fu1GrBfVmxlsDgyYucT1K8pB92LdOCwqt851G6Mj8lweIzrvezwJu3a18SnpR4B4OO SNZIya65f5n3Aa01idj74MPTnduz9aFTBjnoJXGl1vEUKNatYfWoWHsmgweJBweeKGbG t68gxeiPOjNaairM5dWObENuq18wSa/DGfkzbgXdd489QS6TPXd3osCHJ71ySs1SeKNw q22AdUinCxKv5saesge/X2hcFEsOSILl9nIe73BPgWk8YB8uMmDdu2YL41ac/jydOra/ mGn/R7Z8JBJq8DwoWTr2g1qa7MKxsEfAuuI1SdjL7Qhe0zXRqIZs5BTYvcos7nzN1EOj Gkng==
X-Received: by 10.50.66.180 with SMTP id g20mr21063319igt.44.1393349023302; Tue, 25 Feb 2014 09:23:43 -0800 (PST)
Received: from C73782TX02 ([50.58.7.243]) by mx.google.com with ESMTPSA id hs6sm39389553igb.2.2014.02.25.09.23.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 25 Feb 2014 09:23:41 -0800 (PST)
Message-ID: <C960CA0E66F94F768EEBEA6E80C32991@china.huawei.com>
From: "H Anthony Chan" <h.anthony.chan@gmail.com>
To: "Russ Housley" <housley@vigilsec.com>, <draft-ietf-dmm-requirements.all@tools.ietf.org>
References: <53AC26FD-54C8-481E-8B3B-F529C26C0C20@vigilsec.com> <4EDD3C94D45547DBBEE9AE54BD54FD44@china.huawei.com>
In-Reply-To: <4EDD3C94D45547DBBEE9AE54BD54FD44@china.huawei.com>
Date: Tue, 25 Feb 2014 11:23:39 -0600
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_00C1_01CF321C.084D7200"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8117.416
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/i7mWqB3kqQnUK-a1j-h2Vs2buCE
Cc: IETF Gen-ART <gen-art@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dmm-requirements-14
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: H Anthony Chan <h.a.chan@ieee.org>
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 17:23:54 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00C1_01CF321C.084D7200
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_00C2_01CF321C.084D7200"


------=_NextPart_001_00C2_01CF321C.084D7200
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Russ,
Thanks for the comments, and the changes are incorporated into the =
attached file.
It they are okay, I will upload on coming Monday.=20
H Anthony Chan


From: H Anthony Chan=20
Sent: Monday, February 24, 2014 4:49 PM
To: Russ Housley ; draft-ietf-dmm-requirements.all@tools.ietf.org=20
Cc: IESG ; IETF Gen-ART=20
Subject: Re: Gen-ART review of draft-ietf-dmm-requirements-14


Thanks.

Regarding the first comment, the abstract can be elaborated a little =
more as follows:

   This document defines the requirements for Distributed Mobility
   Management (DMM) at the network layer.  The hierarchical structure in
   traditional wireless networks has led primarily to centrally deployed
   mobility anchors.  As some wireless networks are evolving away from
   the hierarchical structure, it can be useful have a distributed model
   for mobility management in which traffic does not need to traverse
   centrally deployed mobility anchors far from the optimal route.

Regarding the second comments on defining the acronyms:
It appears there are 3 such instances: EPC, 3GPP, WLAN. All other =
acronyms have been properly defined.=20

EPC needs to be spelled out before the acronym appears.
3GPP was spelled out in Section 3.1 but was also used in Section 1. It =
needs to move to Section 1.=20
WLAN is also spelled out.=20

H Anthony Chan

From: Russ Housley=20
Sent: Monday, February 10, 2014 1:51 PM
To: draft-ietf-dmm-requirements.all@tools.ietf.org=20
Cc: IESG ; IETF Gen-ART=20
Subject: Gen-ART review of draft-ietf-dmm-requirements-14


I am the assigned Gen-ART 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-dmm-requirements-14
Reviewer: Russ Housley
Review Date: 2014-02-10
IETF LC End Date: 2014-02-17
IESG Telechat date: Unknown

Summary:  Ready for publication.


Major Concerns:  None.


Minor Concerns:  None.


Other Comments:

I think that the Abstract could be more polished.  Some mention of the
anchor point seems desirable.

Spell out acronyms the first time they are used. EPC is an example that
needs to be expanded.
------=_NextPart_001_00C2_01CF321C.084D7200
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 10.00.9200.16736"></HEAD>
<BODY id=3DMailContainerBody=20
style=3D"PADDING-TOP: 15px; PADDING-LEFT: 10px; PADDING-RIGHT: 10px" =
leftMargin=3D0=20
topMargin=3D0 CanvasTabStop=3D"true" name=3D"Compose message area">
<DIV><FONT face=3DCalibri>Russ,</FONT></DIV>
<DIV><FONT face=3DCalibri>Thanks for the comments, and t</FONT><FONT=20
face=3DCalibri>he changes are incorporated into the attached =
file.</FONT></DIV>
<DIV><FONT face=3DCalibri>It they are okay, I will upload on coming =
Monday.=20
</FONT></DIV>
<DIV><FONT face=3DCalibri>H Anthony Chan</FONT></DIV>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV><FONT size=3D3 face=3DCalibri></FONT><BR></DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A =
title=3Dh.anthony.chan@gmail.com=20
href=3D"mailto:h.anthony.chan@gmail.com">H Anthony Chan</A> </DIV>
<DIV><B>Sent:</B> Monday, February 24, 2014 4:49 PM</DIV>
<DIV><B>To:</B> <A title=3Dhousley@vigilsec.com=20
href=3D"mailto:housley@vigilsec.com">Russ Housley</A> ; <A=20
title=3D"mailto:draft-ietf-dmm-requirements.all@tools.ietf.org&#10;CTRL =
+ Click to follow link"=20
href=3D"mailto:draft-ietf-dmm-requirements.all@tools.ietf.org">draft-ietf=
-dmm-requirements.all@tools.ietf.org</A>=20
</DIV>
<DIV><B>Cc:</B> <A title=3Diesg@ietf.org =
href=3D"mailto:iesg@ietf.org">IESG</A> ; <A=20
title=3Dgen-art@ietf.org href=3D"mailto:gen-art@ietf.org">IETF =
Gen-ART</A> </DIV>
<DIV><B>Subject:</B> Re: Gen-ART review of=20
draft-ietf-dmm-requirements-14</DIV></DIV></DIV>
<DIV><BR></DIV>
<DIV>Thanks.</DIV>
<DIV><BR>Regarding the first comment, the abstract can be elaborated a =
little=20
more as follows:<BR><BR>&nbsp;&nbsp; This document defines the =
requirements for=20
Distributed Mobility<BR>&nbsp;&nbsp; Management (DMM) at the network=20
layer.&nbsp; The hierarchical structure in<BR>&nbsp;&nbsp; traditional =
wireless=20
networks has led primarily to centrally deployed<BR>&nbsp;&nbsp; =
mobility=20
anchors.&nbsp; As some wireless networks are evolving away =
from<BR>&nbsp;&nbsp;=20
the hierarchical structure, it can be useful have a distributed=20
model<BR>&nbsp;&nbsp; for mobility management in which traffic does not =
need to=20
traverse<BR>&nbsp;&nbsp; centrally deployed mobility anchors far from =
the=20
optimal route.<BR><BR><FONT face=3DCalibri>Regarding the second comments =
on=20
defining the acronyms:</FONT></DIV>
<DIV><FONT face=3DCalibri>It appears there are 3 such instances: EPC, =
3GPP, WLAN.=20
All other acronyms have been properly defined. </FONT></DIV>
<DIV><FONT face=3DCalibri></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>EPC needs to be spelled out before the acronym =

appears.</FONT></DIV>
<DIV><FONT face=3DCalibri>3GPP was&nbsp;spelled out&nbsp;in Section 3.1 =
but was=20
also used in Section 1. It needs to move to Section 1. </FONT></DIV>
<DIV><FONT face=3DCalibri>WLAN is also spelled out. </FONT></DIV>
<DIV><FONT face=3DCalibri></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>H Anthony Chan</FONT><BR><BR>From: Russ =
Housley=20
<BR>Sent: Monday, February 10, 2014 1:51 PM<BR>To:=20
draft-ietf-dmm-requirements.all@tools.ietf.org <BR>Cc: IESG ; IETF =
Gen-ART=20
<BR>Subject: Gen-ART review of =
draft-ietf-dmm-requirements-14<BR><BR><BR>I am=20
the assigned Gen-ART reviewer for this draft. For background =
on<BR>Gen-ART,=20
please see the FAQ=20
at<BR>&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.<BR=
><BR>Please=20
resolve these comments along with any other Last Call comments<BR>you =
may=20
receive.<BR><BR>Document: draft-ietf-dmm-requirements-14<BR>Reviewer: =
Russ=20
Housley<BR>Review Date: 2014-02-10<BR>IETF LC End Date: =
2014-02-17<BR>IESG=20
Telechat date: Unknown<BR><BR>Summary:&nbsp; Ready for=20
publication.<BR><BR><BR>Major Concerns:&nbsp; None.<BR><BR><BR>Minor=20
Concerns:&nbsp; None.<BR><BR><BR>Other Comments:<BR><BR>I think that the =

Abstract could be more polished.&nbsp; Some mention of the<BR>anchor =
point seems=20
desirable.<BR><BR>Spell out acronyms the first time they are used. EPC =
is an=20
example that<BR>needs to be expanded.</DIV></BODY></HTML>

------=_NextPart_001_00C2_01CF321C.084D7200--

------=_NextPart_000_00C1_01CF321C.084D7200
Content-Type: application/pdf;
	name="draft-ietf-dmm-requirements-15.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="draft-ietf-dmm-requirements-15.pdf"

JVBERi0xLjQKJcfsj6IKNSAwIG9iago8PC9MZW5ndGggNiAwIFIvRmlsdGVyIC9GbGF0ZURlY29k
ZT4+CnN0cmVhbQp4nK1WXXPaOBR951fc4WWTmcQEsmmavhEgDVs+0sSZnU7TB2HLtja25EgyhH/f
I2EINO2U2QYmsQDp3KNzz73SE50EbTpx7/oZFY3W7TmlpnFCH/GXNp4abT+B6kdU0GWISe+p3aEw
aazWtalzSudn+KZoHEy4XSj9SP/in5ApfdSqKmmv13VAvYxJejgYxMHD4WH4X6N9SuGocTCUlmvJ
7XFfs8Tuh0bXFVtwQSGPMqlylQpuDv9aYcmYx2Qss5X5QEOZKF0wK5Rk+T7A/YBGonJYg+dSaA6M
bpVWxlLn4og6J+2/90HpZUIyGquZyLnD2nNXv3zdBHTHhX0TLKKpZjJ9Cywk9Yt6VJa9Ba9P/f6Q
Rmz2x1j/BPRJ6UxJLv8X1qVWLI5UQT1VFJUUkbeP+QNeV3ymK6aX1DlbeQhYpxfe/dvTbvlTBcsV
XFpD8C31hbFazCoLR3szCbukMZMs9ZOAUtfQT6PGrp6OBbfJcVwUx3oL/bh9hsWdd35xd4YoLLL1
BsNMGIpVVLmZFPNESG7IZpz0Pvx2SL1wReH3x+OHQ2LWY8m6leRsyXXgonLKBNdMRxkUz1HBuops
pTmJdRrBMhZ1KS9AJOfGrIEMZcxQDiKlFgXTIl+SVRQhtGY5PsS8zNWSxzVWsZaTyShT2oBC15BR
Bf8JNAMLPlf53DU9tmBLSrQq1qx+yfyIhKUITW/GqTI8qXKQnHNiFG8JV6iY5zWWE3XDrHgRT0ha
ADxzEiSJiJAf5EQqC46AwEbxw5xrs67q1/t+tWNKmPb78DtQpYVsOaGjWx68mGPHkyP0jYptWofL
2SNfEkSKDTXH93dh82j1pMnUj28Hn++Ht4O+G99dd0ejzWA1Y8ct+GF6P6rnutELSm86Hg8m/RXQ
uPsFDyZjak5vwuF00h01nUQWzq2pbfzrUgd5Zs5GOGdKzZ3msErMTYQU4ANW3l71qNNuX2wGNcxX
fHYfv20pcuePFlKJj0djXqjtyvnhOMM3ppoVwtpVJJggp0itjiUZObfZzGVgR4lSq7kwruu4OJe9
Gzp/7zfshxdbbDB5N+LKrYv6hF7rUPPlm8k0kCkKm2vM2gkdMvNIV0qD2sPBcBBePRyiNibKQscM
xauAoil1J7+BRWGn3KgtQ9davCbAftTG1GWfY62jF1Vau5RtZtVQ9bagJMJn1pYfWq2YIQtoWo9o
Hq7DBUqnLd/wTKvGaf1eJb9gi+Kc5SL2RciwtWdRVIUjZsQzqkfazOwo5fLhBHDVXYIQj4/QIsuc
RW4EEDUzKvd+my1r3bbkgDflct1DRMGhxtD7BVeHEgZAH2PWmxe94zV9g1gJx0ajteS45iCdqGGE
dq1P+JTxog5t3fULy5q+78KKiJHigmOCJgDenfltbd/Rjgg2YXlQHyf1feh316GvN2gQ1P4GzEHY
+Iz3dzxj4KdlbmRzdHJlYW0KZW5kb2JqCjYgMCBvYmoKMTA4MAplbmRvYmoKMTIgMCBvYmoKPDwv
TGVuZ3RoIDEzIDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnicbVNNc9owEL37V+wt
MEMMNkwgvYWPdDJDOhR8Kz0Ie20rY0tGWkP5910Z0wApHvwh7b597+1qDwM/gIG72mdcev31GDLr
DeA7/zNv7wVNALSPuIRpxEETCEKIUu+cF0A4hPF4AlHpdd4UoVFIj3MjUoIvv/n7++Ma9/brDrzi
ztTCnCAcBKNu9OENnyFaeh3einJp4Q76KIsC8E8lDYJW8FJntSUIn3tNvt998MKnJn+mq5ORWU7w
Q5OMkXcc5ufythNvu00WvC2iV4iMQxIqAcoRKjRWKwsyQUUylZiAsG6HcYLhhWGi47rkABA15dpY
H+CF+TUFLBi0aA6YXLG6qPqXyO+23n1gTEAaprMVsKUXEp+8HiwsMRPFTfWV0QdppaO5xkKQVJkD
abLmbQHb6t52cqLqW79PDg7Rl0ipr03WL9gcZfFRqlSzIVIBpqnjw/Y6Eokgtjptcap6xwlci3d1
ygFXYlj9qkBhkZUfJB5dOn8kd1RiYTCti+LUay09QYI2NnKHcNK1udjnXGALyciYGpFHSblbqZhd
i8Vy7ynMdIJ8KyutXFEeFjIiJm5ganR5Gw4lm9FCSRUXNaduZFkV545PN3NYnu0BYhzH90I1cU5t
sKEGI//KImfaeZiall23yUli9VC5pYQxnCRd81gLY4SiE1doUW7qOMj/83KzNXqanEc+F4obvUj8
bbcHyHQLvz1li+bE2Pvzcn8Yf61EhhD+ZtBF5P3k6y/0D0YyZW5kc3RyZWFtCmVuZG9iagoxMyAw
IG9iago1NjMKZW5kb2JqCjE3IDAgb2JqCjw8L0xlbmd0aCAxOCAwIFIvRmlsdGVyIC9GbGF0ZURl
Y29kZT4+CnN0cmVhbQp4nJ2UXW+bMBSG7/0rzl0TqWUxkBAusyarKq1V13LX7sIBQzxhvPgjWvbr
d3DI2qwVXcFCtmyf57zHvHgLk4DCpG1dn0vy6T6BypAJXOFbkS2hfgN0XS7hc4ab5kBDyEpyiKMQ
RpAkc8gkGV03luuG24ulZqWFV8/y5ubinm/N6xX4wtfaMb2HcELjcfaDRClkX8koY+uagyrhUiG8
sWZ8RsKZX8IoGgBgUq0Kl1uhGgg+3CBGIo2OxBBnMNUOUyHPgDO8ANGA3QgDhcqdxBXoJ06ROPJV
hUGrMONaikbVqtr3R/awolYXptasFr9R0o5r41CRMFaLtbM4JdVa1MLuQbKGVdwLPWHN/uqKvK6X
vLeC+3QlL1jtmS3fEdLHmnesGMd3WuEHl/BgmX038g1W2rGmOEarOaE9xQxwBqUda4asB5473daE
5jCi4Jod/PG/rLhjJa1jF7eLgZwT1vzg1cO5Kz2oxiMr9edVcs2bnA8hIevZX6n3163SEsvb8Y+T
T1ih/8vLoTR69OrC2Q0e0xksikJzYwbUSVt/xdOpvy4uN6yBp9GqCJ7G58AtsDrorrPVr5/oPIMp
K2cshOm5v9j+vfUe7/D/gOg7QlcZ+YbtD4ldPHhlbmRzdHJlYW0KZW5kb2JqCjE4IDAgb2JqCjQ3
MQplbmRvYmoKMjIgMCBvYmoKPDwvTGVuZ3RoIDIzIDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4K
c3RyZWFtCnichVZdb9s4EHz3r1j05RzA8fkjbZrHNGmLAGnrawwUhyYPtERZbChSISm7ul9/sxTl
yMkB5yCIYpHD2dnZXT7RbDqnGf+kv1k1+vP7OW39aEaf8bsdPY3mcQGlP1lFH9ZY9J7mC1oXo27f
nBZLOj9/T+tqNL4xQTojw+m1E0WgV5/rL19Ov8sn//oNfZIb1wjX0mI2PztZ/xotL2h9OxrPp0SA
dTZvsqCsOfljtHgX3xC/oFBKqoUPlMtM5JIEFUI5Mk21kY5sQaCzt+7xVIsWX1R2o7QKLdXOBptZ
7QE4X/aApdhJ2khpyAdhcuFy9Y/M6ef3T1fvFudvH+LT24uzs/S0fD/rnt4tZ/MHQDFIfLOYLx9A
/VKH0jbbsuPZn0m5KgqwUeAvXeWZZ9GYGKAnHJyQhPc2UyKAQiW9F1tJhXWVCH7CgC0JrUlWtbZ4
fI5NmKy0joLtYbS2+36BJGOhU7DkZCXAwEmRlWKDF8gZkwqQwWPxDsdimUgoHWdpQi8pwlsjqnRa
bZUJExKVNVuyYAcCwj+CqTS+cdInmMwaIxHpjpluWg5ozzpjVy2yRxmgjvRBmXj6hADt+dDC2SpG
nXAGwbBFAikoRxmWOsTbAoRlYeVeyKI60wDU91ihFCF+edgkXFaqAJ7MHDxy0XbmEOQrVv3ZYNh3
AOqOiCmMeOBSFCrjZZXSOqaXn5+5e+YjDNlaOhGsS0BJYvAASFurLMZUCQMP5CxbDEFUvfzTo7q4
Vj44tWnCMPxuc8Va3o9RifcnUTKcrrlqBVISbcHIYoPsH1VGEjaWQ6cSIyULbJC4rbMNot7IUqXg
FXcDpJL1Qz01eZuCw+ExsNqpSjiFwFJOCstOhRWOw7kfz0GWvnSqNV6ywk5OEBvLUyIGuZNuwt7y
TcVW6jsRfxVA9CiW+FEm0020Xcw+sqItVKarbgNdSw1B0JC+dqnwoHF1/dWDyb5UWZliiZ9S5Egm
LCQe0ToOioPoTmVRCJRRlkGgAIHgeLbsXXMM0ntFVbX18IWRe9TmU6NcTBqMY3rjZBy36XkVB9fE
Ty6COIDlKQpOlIXg0Akc5O9MyhQ7kr0TSscGwLhDqN6FmUBpIqLJISS0sp3KORFGdm0CtHXnLhAf
gsCK6GBbhZA8QkZTA4qOLUDSzWp3NqiSQltIeT+W0+10MgSJPfZidvEwgeGUy+mzNFwwqChaCRfw
jy9VTStnfwEaEMvPqxXnCvyHQChq9NvbmOqbFV1mGRorlt/erC6xnAv3LrJDVHi/TtS+ddSGSPfj
u5vV+hs2/VzfTRfL6RlGAP4LpYsdf1hWojvmkLIkxBDuB/KseVHH7RJtubcejvpxe/mVT1oJ9InT
4b6uKqbXyPo0sURiH+LYJJHnijVCX6YtsrAXbS9+HKUHlEpiBhjlq+hhH33BhcaJ/q0qdvORi/cq
lKloP66uhkgfd1bz5FjFZo5yglXvx1jUC3WxnMXR+LcMXe98PtzTXr5wIKqqbpxvgKgG0z52CbYd
drotP3PmNtxj8fyqQFMdkbe66YbsRrY29alXdwKQQxfw2AM76/bIiBjJamvigQdF02CJc5XHFF7t
lFdsob6C1JHazorYpTy6KhqgjQMXsioNplk8tLuF5NbIGBm3S815iMU2xNpZrsdUl9wkdHvcPePn
AybyyzrrVUNXG6YACdbcx40sVDd2XzfPblbupLZ1LPnnmXY8ONkmVEhklTQv5+l3LATSARqlQjFj
Z3RZvOvFfKdpFDtaLQCVBl+fsSMHP48333pUeZxNmHABdxYWjW8ZqDx7yrMU8G8KLQ53Gf9miNUV
6Qazi5srbj6Oe0pmq6oxGMXpmhZvOrXkJtjfKTCQhzhbabdO1CWPb06hmP7/bObrADg3+ii6yPU/
JAZVzlZ/4xtcOTJtuX47CYdQ8aLGGRMh4ObX56+veDYPX+eR7SuerKjdfHp/gmtcQEub9lX+u1ac
4Mtm20ClxcUkXtzpxQf9CnfWM74Zf1yP/sLPv0Wn+OVlbmRzdHJlYW0KZW5kb2JqCjIzIDAgb2Jq
CjE1MDcKZW5kb2JqCjI3IDAgb2JqCjw8L0xlbmd0aCAyOCAwIFIvRmlsdGVyIC9GbGF0ZURlY29k
ZT4+CnN0cmVhbQp4nIVWwXLbNhC96ytwiz1jqpYU20l7SuOk9UyccR31FOsAESsJDQjQAChZ+fq+
BUiJVNqJNB7JIrB4+/btWzyLy/FEXPK7/Syr0S+PN2IdRpfiD/ytR8+jSVog2o+yEr/PseiNmEzF
fDXK+yZiOhM3N2/EvBqd3dlI3lIsbr1cRfHD6/b+vnik5/DjE/GRlr6Rfi+ml5PX5/N/RrO3Yv5p
dIZHT2fTp3Mh5k7J/asgKrfUhgSO2Tn/LYjaUyAbRSC/1SXhf7fVinwQOx03WLc7fzWazLpo6VVu
pDFk1xTGQtxzQB33opaR8QehrdKljCTiRsbDgU5REG4VySLgIZSnSmorsFWWG1IiOuwiEWQFKE4D
mFu1TyuGuXJelM4GhiiXhvqxavLaKT5ERI39Xx8kfio+OYDRdj3+GzkugPhLTaVe6VLcPWR0QN+P
U0kr15SOC01dOx+FDkggAu1zoz1gMgxZ14bz1ICTUzWyseWmH0paBbhVbSjRQdqD6BDSlt2GeeFs
exTxScjPUhlJ9SP9hBik9afb0Zb8hSgb7/GT2V8gw0FiXal6aaEqem27lMxO7kPhrHBgLqV2MWQG
B+MPbGKtQck98ERWC5MOfMAe6SXXiYCtza0fJDTLUHq9JJ/PDMI4jsck0l5IT0cGurRbuY77ceYb
5kpaVCU0BslARmInA5gGGPzoGl9Cc1yDhuOBeG6R0oUY+oEYReL2pAXA6Z1dcc1ZCqk6BwZL16Co
KjXJoOBHUQBQJGP0miyChmaNfom9nugXAuGMEsuhnDMMBVwGZOgtGd4ATiX3mPh6V9yOlxukJ70u
1KYsSiNDKJYykCqGkWilXxaJibTrm/MbZ8kW19B6kR/jg4seNYXFBWA2ARyqpkStBzoEUbJyTRZg
V+5OGEALZCcVm1537gEHw9K9UDpEKKCJPf0zHRLt43zoYigZZVEbabHM7aRHb8uBG1UOYlkZMNoe
l/lJHP9nYBZX7YLm+hz6qzQOpe+k1uD7bwLEQ+DooGMI1DGGQ6XwxRh2lqEIOMJK+xCLjauFd0iR
dfRRlhwlrV7uc3IdBywVUHniRC3iC6FjomyZgAe9ZM9wA00AsYCE2aD460kglDU6gD1oTVFNcGi0
HA7ebQhgfOat73ZELL0ctmu7u5j67agNOpFD4AxRPXRUlXsgy72B8A/iHmplC/G6JvzAc+snw3E1
7jAc2UbTb51WuXS9LkevYT7okMcG80sYW1aHKjB/QMiC6uJg4PJAWHlXgXnhTHIeyePvVERDRScT
Uq5s0jFs9ZBY6AlcHff35kqrmKOSS/zqpdHf/2cDmPrCBQelszEfm2wKYqja2XMkBUqRSgFFaKWZ
2o6VH5qqAt3fM/NdvNdtvIqdJDrfCacddlUqByxnBzNrXRrjgbdKM1zERtpWqjByT76N9DM2GNsa
WrZ9WFfcNtqmLmzjBMJoy+7b3gDy8OX9OKNsUsq9GNenxTqwlqWaT7eqa3ywiPGcPXLvvjnYj6qq
IqA6LNNFy/KxbOB6BfGnQ9vrxu0x2XF3Nxo/0lbTbsFw2pvZFOm9dxZJ5xya0HlnT1BH9NPxhMtE
vtLWGbfuivQONWHwaBrQYQ70Fp5Mchv4TxW6HHH9kKV3dl8dDhykMzg80YouWFKaZB5jggNKvjOs
+lZ/n3v07mF73UkQNIrQXrOyEXx9/Pj+enpzhdnSbnvw7mXfNThvHu5oQ/G+q+lkhn0y83y4cD62
KfZYSctnN1ezRRZ16Ewn06BtaRqVXWvF/r2DDf46uH89nd1/fjrHJcrhEhVqZ1U3/BHpapqYeg8j
wcIPaswrCUyZcTseP7zUmg3gXbNm05u+vUhXcnHyglbWJK4WiPlhPvoL738BQfoGKWVuZHN0cmVh
bQplbmRvYmoKMjggMCBvYmoKMTQwNgplbmRvYmoKMzIgMCBvYmoKPDwvTGVuZ3RoIDMzIDAgUi9G
aWx0ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnicjVZNc+I4EL3zK/q2SRWwATZhpvbE5mM2VcNW
NsVtkoOwZayNLTmSDMP8+n0tZLCBqYwpyl+t7tevX7f8TlfDEV3xL56Tsvf785RWrndFX/Bf9d57
o2BA8ZSU9NcCRp9oNKZF1tutG9F4QtPpJ1qUvYtH7aXV0g/urMg8nRx38/ngWb670zf0IJe2FnZL
46vRH5eL/3qTz7T42rvAq5eL239eLvskdEq5KSWJldQej/+evVyScFRJS9+eH25vxtPr1z+pMIko
qDRLVSi/xbIkN/byt95ocvD4dR7WwmOwg88kkc7RSni5EVtYzGdfut6vx6PJ6w5FYpDodw+f7K1l
M5leT16HeD6+aWI9ahJpqrwyuk8+V47SQI7S3pq0RlQ8lZSZojAbpVcECks3jL5vkakVRbGlVFaF
2cr0ODEXLXFYmQGHN8Hh3qwUGoSVTNnOB186xKdNrpKcjS3yt7JDEY61RDkyuTmJGDjgGICWZSoh
k1GpigIpunAdKD3g0iaVIaDQZECV8MYSZLIx9o0DR4gpLbfBrRNc5BCry2VkQ/1o03DI7xCxFG+I
WDvJcJKPOWzovlPOW7Ws/UcBUEZtfOM6AHLMu/B7UlIjd0Za4i1XxQpQ6k54/gV8lAlLmTVl4MdU
XpWQuDUA2mXooQCCKOnI8AF0DqVyPQu5lkWoFHtgzeUKVbFJvj3IMuXLnZRS4QVVwufHyGO9zknN
bZ2XZRfcvLHr9s+OTnaUoAlkwq3C4JTOjC1FuLXyvVZ2x2NlzVqlh7DHqNoo6qoy1qO7LAlaqbXU
e3YgSoYX58xk2JUXV6pGr34oiDPptQCwTlB+1rZMBAuS83x84plgeeAgT9GG1EmmxCRKcqFXkocM
r2QTmK+lG54PmNU6EOjC4mXThaqsimAAJFBIqjKMCrYvxBaZMgx2D2q9QRXIeZG8IcTMR8DRz8tF
VBVmY1jaP1v9BJ2+RD0LhbvBUjiEPfT8IDoLz7sSmWnEGgTPZx3vAbJitpVKQt/EAJqxdgisrNKJ
QuqcINcSYq+Vy1nzS4CR0IMgh0KwyCAq7VWGXggTTkSYTZM0JQu7hkB34B+e466q2i7DbNyYYZj+
8/Y0fHzq7+qINuyqYN9IscjYI3iYNzXn3uW6oy2bic/vjrD1MdNR1ygWY9VKaQyKVqSlRC/ISFTQ
WCtmEBbosHyKTk7JQVoLvOBtlpXW+DkUibdX6KPdvyjXm6w8TwzhnEmUCLBbKTSbacS5UT7/efwn
qFNiE4vWcb6GnK7Hofi3aBsAuU+H/OkgPYliGD817r9XGCWOZvWqdp7Gn/vho+P4i+TbE/Khm1f4
vF/0/sXvf9lC7+plbmRzdHJlYW0KZW5kb2JqCjMzIDAgb2JqCjEwMDkKZW5kb2JqCjM3IDAgb2Jq
Cjw8L0xlbmd0aCAzOCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nIVVTXPiOBC9
+1f0baEK2AA7YebIEsKmakh5gao9DDkIuwFtZMmRZILn10/rw8TMULshKRx399PT69fSG9wNhnDn
PvE7K5LfVxM4mOQOFvR3SN6SoU+A+JUV8OeGkj7DcASbfRLqhjAaw2TyGTZF0nmSFrVE23/QbG/h
l5+H5bK/wjfzawQecacrpmsY3Q3/6G7+TcZfYPM16VDIoDFcSeA5Ssv3HDW8cyFgz7WxoFVlEawC
e0RQmh+4ZAKIxLvSr/B+5NkRNPa7vyXDcYOYc42ZNa6kgMpwefDVDso9szzXtKYDzVHwEy0Y8SOV
AaE5nBX2A5SrKln2ih6UG3hnNWRM0sqmEha4BKEox5M1A4CpBDxz4wojliotL/h3Zt1WQ17kKer/
4Kj2/vVRGduLSEzmYCraNvFgPtLfMYP0UonKRvqj+0aMDZVLPFsgxahuZ9x+lDREsBSMmGcku2aC
fycIh50Tb813xDCHQu244La+krdgkh2woDLYVzKiEZD1K/nGtCiMB0MSZNZapAFtAcWtPV2zuZHY
86sIlQUhudwrXTTPQPYszBVX0o9ReVk6UXdEDlG2W912ndv8jR5EbqT2K5YWGP2C65fAD4JMZkel
ex6iMUqOrv+0jWCuCHNrXR3WpNQTZ8FgAXDgJVFUTTOhdG56vvMR6oY8YGpjsTAesy0libMjHL+/
TNF7JYDaL7FlKhfLmWUhANuOX4B6qnKEpxQIbL/n2bZ7bbAlk/XF7TdJ5VgKVbtHQ69fkfyOrjMt
gtcGu5bVwRJ/8jqpxXRGM986AvwLS6auNFIDDJijepdN0yQ88gNFwJlwfmZFKTCoE8aqQCCWxHHb
+Wu67XodnLtE2/pBIEeF0r4uXZ5BffIe8adMjBogN/r/28ptO8vngByhliE4zTI34Qtm0R0nlDZd
UB5RjglP6ekevq0eZ/ejyacXT42CqVbn+hrpkvhpNBy/uEOpdEN+QlH70ROiEkw3iplwegTmEWi8
SFNYoCR9BaTewLBiOVew9oYidot0tSZ6FxBHx5fNT0qcsNlcLL6UzdOrKiycFf5vyiOWVSpMgJM0
UCQSDVg4Chr5fGRdlaXSFp6D7ovFmpRvzs11bNmtzLXP9HsK236O7pqFWRHoWr96nm27EY2GiAxv
3eX0YczanzfBCz8xJx2uiF/L9eDGrlnzwxFpf/FPpHVhfwmuffAGHRkOjJuk3OROwqDNjnSBUYPy
AWkERIKJQbyt5+eSriYD0+pQ0R08+tLz9/bPl/q3lPoFkxcCnW+Sv+nzA7Rot5dlbmRzdHJlYW0K
ZW5kb2JqCjM4IDAgb2JqCjk2OQplbmRvYmoKNDIgMCBvYmoKPDwvTGVuZ3RoIDQzIDAgUi9GaWx0
ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnicrVZNc9owEL37V+ytMMSYj7ZJjjQQykzMUMJMDiEH
YQSo2JIjySV0+PFdGzv+TCCdiMGStau3T+u3sp+h1WxDK/zFveMZ1vQS1spowRD/a+PZaEcOEHeO
Bz9m6HQF7Q7MVsZxXRs6Xbi8vIKZZ9RGXFPJqTb7kqw0lFrfts0pfVZlC9zShQyI3EOn1f5an/02
utcwuzNqib07nExgOJneFxdGhsGkNG+PJtYEL/UvRrubg4KGGbVGccmpeYRKQQ4wHN6PsSu0A0zM
4UPF/M+edWf3DjmQT2GCzZrPi66nDQUQC6Da+X1DHsUKL1Xepww5GOvYld1PG7I4VjIo+p9jyABZ
qUN+wXmGFMnK+mRXnGs4QuXVkd59bP6IdYD7jIzTOxxlZJzeHeyxZfeGyXx89/m8oKTdjGKtUpJe
bQWdZdTVSIMWutB6mI5vwu2Vu5NrO9+T4+WWrQNJod0EuKFcS+Kyv3QJnlgwl+k9eISTNfXQ1AxR
u80OevaZ0pItAl3tGe/LLltgFXBHM8EVTu6BuErAgsIyg6cFeIGrme/S3DmIZ/ROyK0CokBtxI4D
4wn7zgUgkN4QDeRIiAIXSxq6EL4HsUIjVTQm9goVcsDwiso/GHmBhNBGJA4SnrBjegPE96XwJSM6
gUh2bUkRaMbX2T3Oa1N7XgeH+OToFGau8G7Itip1lUcVL4VMwyc/teFYBW+PimfwhxlUrn6jvRmt
sjU+HuIA9vh/o5QK4AxZN9/Rdawkn0jNiOui5CRqKBxktJ17hI8js9/ci63QxFx6nqkcyolk4gmJ
jHioV1gJ6VGJQlIUBEescHJJNAHfJRzVrWJGmRgXwDzfZQ7T6E+UCrxQnYoiMxIJGmshgiB8CY7A
ihdujBKBRvW1pMpBPEwDFlBEdEe2bEt2xMTaoS/a9D3mm45vBr6ZYj8lGbot7rwqnUeiGDCq24XA
Okv2lyUUEQ0NMdlkVuaODUzawyYs+yRQUqdpOIfwwlmDuUIWCo8KjXXvUKXCrznMOiAZKhHiWyd6
XDcbXDuvDZbNef0CKJ4ybjNW1ODFZxI30QvWgdLQub6IPgeLwnucIA24ekLMwcz4hb9/EpZxLWVu
ZHN0cmVhbQplbmRvYmoKNDMgMCBvYmoKODI4CmVuZG9iago0NyAwIG9iago8PC9MZW5ndGggNDgg
MCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJyNVk1z2zYQvetX7K32jKRachInubmS
k3omcl1bt9gHiFyJaEiAAUDJyq/vWxD6oKNmSo2GEgE8PLx9u8vvdDEc0YV80j2rer8/XNHK9y7o
M76r3vfeKE6gdMsq+mOOSe9pNKb5steuG9H4kq6u3tO86p3dmsDOcBhMnVoG+umazmaDB/7ufx6h
T7xwjXJbGl+M3pzP/+ldfqD5l94ZhpaNyYK2xpNvsoKU3Bc+c7qWp1Qpo1ZcsQn97kCuglooz31S
Jj//rTe63CGC4sa6b6SyjL0n1YQCy3Wm4rpgacHkdaVL5cot5doHpxdN4HwImPG7Hcz18RBVdqFL
HbZHhMhnBX7Q0jpStCxVaGfxnoFddoglQsbm7El7qp2trQe4NvT1XtXsBtMjNtOtUZXOhrO09bPw
E5zb4HEGw0uNH3bNjjLQcarUP/6DaaHWjCVsyBd2YxJOKJxtVoWI0ZSqDcIJHpMD+M9cZtaxUOgD
jenpzPHTeeNZgkL8Eth4Ed0u8QeQ2qzk1MFmtvRybCxKQNBEr+LMhQ0FbFF2g3PyXIntjoteOSV7
DP+0FQ+vV5jin08daXeM4eP1zXPkWisXtMKeOzr/b+eToPez2/vnhPOreTLtKDSOa+tCa4eDLpjJ
OFXjeEg0L9gx/AbXL+I9ySa6Gt6cYppgDqonuzYC2TmmclmBzTIZ6JMOYlHHma0Ak2M82IS11M4H
ymAXncN8m4JB1x0ifEqvw/6ZMiCfoKJF8jb1Uk14g3PeO7souaLHoMLuFIfMhAqCJzM8lELetZik
8twhw8B1o+EhFCQcCsneVJVyMTn20h6ycmnL0m7A+2Nnk/vH0UeiO2sGFgWnUiUhWQL7RLy9HvBI
TrzWCpoeZ6EyWQGh7TLEyPqmDNHw5gDYYdFe7RYxlxwvtliQOVZetpD0glSDYAe4Ie6l2g47WnSY
IXZQXy/ZI7T9GHR+UVVdIrQImEnFSJAVrKMcdvPspJhY10Fqn3rJTEUTiyaAcE651Hi6pbtU6p7O
JtO7p/M+Vrf4cA7rNfA7YKXNJMlIrRXqL1jT7T2h+kh5hqew2ON0wqrzvFbZNw5+2MF6OrvZOS7q
RlFX/aOt8xDAGtmJCuvDQFpFTt6WjYxCuL9MB0zktdHGBcpBvyUaI+lSjKOlJLXX7+jrw6fJu6uL
t88djJ399jtLURHdwiFIIg4sGWucPJ7dxfJzyPf2yqwDVG2RG1BbOoYoDIGjoVUICr1HUjKCeIU2
NLv+HHthm7kdNGMDqbouIaZIHuMj6yZ3lFv2cXzBsRKV+psUb/AaPp2/SogxEmIqYUdhzdD3nK2S
ZrxOwkqPDw4hbM3emuOE0Y9rzaHz76tR6hlZclue3NZt0O0167Rc39ZTEETRFKPFyir01jGJ7EY5
cGvb9QleCQb+mPy6pUoWabDW/lVKH7CiYdKLwf6dpFNj9+L7ppbaj6C8itxe2OGrWFwiFl+QFSKT
h1VVYiiqHTEPjTFcHhfi129L7bU/YZT8BW8ySov2KGN8QvRHDjEnmjrt4PcvE/syuCuBYsmIhm9b
Dt6OI9oEmSZJnA+lbjColcOEf/NSazHGdbNqkP7jD/345kivLjTXFdMHycKbee9vfP4FIN2DnmVu
ZHN0cmVhbQplbmRvYmoKNDggMCBvYmoKMTIxOQplbmRvYmoKNTIgMCBvYmoKPDwvTGVuZ3RoIDUz
IDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnicfVbbbhs3EH3XV8xbbUBWbSWxk/Yp
sZMgQB24iYqiiPNAkSOJDXe55kWy+vU9w13Ju7JaG4JsaTiXcxnuA51PLuhcfrt3XY1+/nJFyzg6
p494LUcPo4sSQN2brujdDEGv6WJKs8WoPXdB0xd0dfWaZtXo5FOdONSczm6CWiR69nNze3v2hR/i
82/oA89DVmFL0/OLl6ezv0cv3tDst9HJPqDyc+ts2pL2qPKYaOEDsdIruv1MOWbl3JYCP2QbOCI6
sERqrlNQic3pT6OLF8OMiPM5aETbmhS1oc7+w4YMR7usx5RWOSLOZG3rJUWtnGq7mCDfU6YbG1Ow
85wkKq2YUq5rdlQpi15rhTZokWudrEel2pSY3UCDTLvhjp+sPPIbu1hwQLMEpDc+/CD8bZPlOMi0
sWlFTfANB5JhMBkO44PktXfdhKQV0q69NcBAB1axm+CwqT2OPdRKBZzvnaxzNUc9vwApUTCaXu4w
v/v68heir4hyTI3HeBK2UNZlUCWgqJSU/jGofN3jBFisfJAqbe8gWW1pzi3X6+xqDmqO5MlTLGWO
cF4Kx17l2CsdMbngAYg7PlE2bmPiakI0O0DFVo3SZQhFMWsgEhfZdalI6OrOtkD15DVIs9d1pWq1
5EqIFVYw2EIFWgJamIoU8GbnDjF9BUz/gNakurhnny3mpvEhCRjaWZahMVwi46n2Ih2MZtOgk093
z4/buPcWpLO2BseQEh8Uhon+YgRJ3BGwpZByG7WNO2OacYFbvuA1o99GBVVxajXzv45AJ12uHNmg
8gfx/6OqGsdjir6CiJrGWa3EK6A4DNLUHqoZTA96UtEL5lbGQAr4PheBKYIOjEeHGHbIlvgSL4oI
F09Ke7bOshKgbnSRbMVxXBwuvgyDtga5dilCRrublRXp4hTWmfHoVRrV6GPZfryzzCBFEdtKNIPq
72ALI7ULGF12/MuT5WRMXz/dnc1VFEXvvhniDM3J1O5pMyF9Kd0bgJzaihpB4oplObWIDqEWdI+I
6ddWKJKyptwTLQTViQvHjptjp0dZ+jDbaj/EoSEuYYjb/an93hMuV6xMtxaZw1nyZ/IOBqsq18cI
+lPFstF7K09ar56nvz9pQe6v7ULVoSWeLocx/WBuoGm75qdMYCvpyf2p4CQCSBn3qUGuhYw+6O6/
hzjE5AqY3HDj/LZslwJBlV2yTZ/s6F0u1hlUwdYTCcvLYRWZsqe2tFbBKlkqogTYk+vYug6bX/zU
bqsjADwvJyrzwCW02pKl0msWCWveHF8NvY35lK3bnXCOc1wvC6bSpOF5Xsq/gxRymVoNLMYtt+hD
njDO+BFXQItUr9EOAVPaO9jjthymhWVnDgl4LQTk1kTcQq+hLcKFIOWfbeF9wP4iEuuVfaSCXtnE
OpW7K5dbt+e1I4g/9b9T6bcvH64vp9OX36EzuUOdGEMuCl+jxJL36u3htOve9LqLeR51sE2bPfmN
CqbYG1thU6NzVtUgS/dYVJ5Xtvt2bt9+FPTuIJz15f0p+L/28kiR2G1bWoasH61fNoOtjcUawX3V
AsLd2oeZtMcEhbJX04LPtVz19yfvDdwmrgO7k67C+8emPES+zcuMMtM34/JUSsOfb3cQHx6OvyPn
+9nod/z+C6DZj6dlbmRzdHJlYW0KZW5kb2JqCjUzIDAgb2JqCjEyMzEKZW5kb2JqCjU3IDAgb2Jq
Cjw8L0xlbmd0aCA1OCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nI1WTXPbNhC9
61fsrfaMrFpyEif2KYnd1jN1RrHVU90DBC5JtCRBA6Bk9df3LUh9kFI7lUaSTQJvd9++feArXU6m
dCnv7leXox+frinzo0v6GZ9s9DqaxgXU/eiSviyw6CNNZ7RIR+2+Kc2u6Pr6Iy3K0dlDFdhVHC7u
nEoDHb3uHh8vnvjVH9+hn3jpGuU2NLucvjtf/Dm6+kSLX0dnuwVrE3Iq7dIUJmwoNFXFhaeXM55k
kzHNHx/mqw/d5ZfzMSVNXRitAp//MJpe9aHKpgi45wP5Zum1M3Uwtno58y/nZDzVzlZMwdKSybFm
s+KEQu5sk+VA2+MkJk3ZcRWoqX1wrEqqVcj9hGiRt0DLgksq1YZU4S3xm0FQ64DcAyqtY/K8AhiZ
ihSQgWeWTUDkXc1crQxSKxFwgu0dQe8RDZw2xrHc8bgz+7Ct93OKhpC2Za2cqbLTuKWqVBY3k8qU
qZCixj9OFeZvTnr8JVwXdhOXIs9n1kIcXZGqEtwTKpcSJuS8Ld4fLnw37soOQo/vrpoEeCY17OPG
1BaFXQuMOyjrplfX0/336Q30dFAO4mn2Hvt61NLDfFfpmKDNtXV/kdKyNqaNtgYJ5m3RSDqxbSvk
lNByc0I8ImJ6/O15gX4oVNjjdJ8EynCnKO4nB02EXAUC2WlqNGmF7q+sSeQK5BCR5AtxdmCq0rl1
faBUOUqdLSODFnouVRFL40mPuO71aINZKSn3ppXqAdUyAmV7P3JAunFR5FB4lUg/T7GyZZZXHY83
mE0lAxUBtfXhouWbvW2c5gvG8EAAKxm1fjFaaVShLdwEnR/HbVKXXBdCtkP/9e4bAnh2whQp1x+q
XmO2RDMgqMGWOGfVhgqrIw+Regy8Lqw/zkgMwaYxiS7cLbJYInq8ZLIK+gVCKICoXAb8qimX+LFp
Hyl2kamyGJdYWAqxgx9VFFEyphT5Sca4pNqOSyz9cj6QTquK2hpwJMmlyhQNDETJRzQEkCMz8Rsf
uLztQ72cJbESOBigBh6Aitqpx+5WeehIy39uywHlELm4CMoSXouhZscxudIEk0VxSXr/0bOYa1+/
R2JVSQJF+c47dqYzf57iUHieyddVq6D587uBl0W/atPYOdRk6DMz+MyXTa28j9Pe6fyiUBs+GHDf
1LV1g+kWp9jbyqFn/AsK6pZ5kZWnZmwp7Ya7CAKOp8oGkTJ2TGSi+5nI0FXMEMFYdNVPjN9UWRc8
pnXOopBOlDmGFH+vOmWKF9XtKdoNCCIOJtXW3J7MinSuqiyeX9IJ2G7XmtPJDXQjp2Ob7iCn6GGu
A4f5QKB7aFJyZThgkn+wGSMNt00uloaixtv8auznSsexxiQJ2sBRTYHAuDUeEtEhREgjfoh1rqkh
WZT6i13LOX5i6A/rF8vPhzKQjqGlqlirzbZ5t8MBOfCPaFkWJ3w0Lh9idniEauV+FBOrT5C+5P15
h6xsJC3mI417iBUG6cg+tT5KxXLiyZMbJFnCOoKKroN8RKcHzYK7gfXUvP2PI4m3R5AQHp33+JBC
vHacAPd+FuG+Qiaws/tkIs+ALBlPOvz7txp7PX1usgaNm30ax0dN6r9+n8PCaDr9A5j3i9F3vP8B
hf51HGVuZHN0cmVhbQplbmRvYmoKNTggMCBvYmoKMTIxMQplbmRvYmoKNjIgMCBvYmoKPDwvTGVu
Z3RoIDYzIDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnichVbLcts4ELzrK+a2dpWk
WH4muXljJeuqOHFs5rTZA0QOKSQkQAOgHvn69ICUZEreslQqWSbY6OnuGfCJTsYTOpF3951WgzcP
V1T4wQl9wqcYPA0mcQF1X2lFfydY9JYmp5Tkg/a+CZ2e0dXVW0qqwdGtCewMh9GNU3mgg9fN3d3o
gZ/84RX6yDPXKLem05PJ+XHyc3D2jpLPg6Pdiso6Js5znWo2gZxtgjYFKZPtX2o8k80JRJbW/Tr+
azA528Ny7G3jUvY0W5PnktMOi27vSWUZrnuyjmrHuV6RSlPrMlkRLOCeAS3nHObswGCmSx0A1tS1
dYG0x/6ccRYJYhdjA1VKm4APkPowqYVyq0AqEOB2aMqkc9DALkYuoErBtdglnUf8MXBOLzfVJXNc
dvzUaMeVKNGVgjoFtnZ2VnLl6f7xItK6f7ykjH3q9AxEtelJ9SiiWEPn/T0ept/O3hN0Wsi9dWnX
slO/HPhM3paN3O/p8Z+v3z/fUFCu4NDeqDaEdCWe93AOzGKz0M6atiCw7vC+fE1oxoDVJezPyNec
akRAleUaPm2c6DPD7udDVEq1ckGnTamc/PI6NKplu4wyg9lCBY7rdyr2scDlDcz5cp14UrgHsdvz
o3vd2SBogH9/aBGsz62DKaAsmhRs2KnyJSGsk3hHIMn37TT5SJLwcav4TkVJCUDZM3KD8iqdjfrc
sVlpTTFCv1aEiOnf1gzbnEWDAMArCBogLNZC51y52Gf7wa0qK9lE6wSbqfVrgVxYnbXmN8YwOtAr
p2EYgOqSVxJ68cOWi9huc+4JsU0w1mzzKaV2xi7nGo2x1GUZ+w20FdZLBTITvK1kMHQVCAepdbQJ
DuWsQgPVDgJ/jsBPV9rHIbFtTpAJNrXlXiyue/Gnu++PCeXa+Wi11xmmhePGb2YX2p5NnC3i5+gl
333AQoUB9BtubHdFdeJxl/u1IBhe7q6/GsUH7gYlb0rbJkr83xuqoPASt1ImJTtn3Qg7G37N/xC4
qkNMe8xCtEEmWTuxlz1Vd7tlvODS1tsZEIdhLB9/aQxqCxWDVuUuIsCbcQyRrngTf7Ggqbba/x9v
eH4Bzz/YKA2blBGqMO9aDGS7s8VHmLn1YS8ECarqxaBS640Q6DzreQhexTzIKYOBjnOBCxeNeUll
XLY7mw4TuKUh5xfikv4a9/k8cIEARbOgi2j+bEeYCHWH8d+H2Z3ttfymo9JWnFaYLbdOmGfDyA8x
wV8USUjLMc5OJoIKUSToIV/SvlpGQrT8oPQ+0C7zeJBonIRD0jsk1a+nOzkiQZU66/cIZTrPkSts
uPF3iGR5r2eYULbGXJZ5iMPLM84P/NirJ0OyQFRUXTBlVs57341VHEt2yfFRQHQOroF2jsv22Jnr
uo81AwFuT/1KvLy8iJH4IIP2x9E0G/84hq5ohnLc3TFd1QiXp+umEOjTd8P4LEX917/3qmA8wf0H
zGky+Ib3H5nvFXtlbmRzdHJlYW0KZW5kb2JqCjYzIDAgb2JqCjExMTEKZW5kb2JqCjY3IDAgb2Jq
Cjw8L0xlbmd0aCA2OCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nIVWXXPbNhB8
16+4t9ozkmLZaZzkzU2c1jNxvqz0pe4DBBwp1CAgA6Qd9dd3DyQlUdI01nhkWeDeYXdvgUc6m87o
TF7du65GL75dUplGZ/Q7fsvR42iWF1D3piv6bY5Fr2l2TvNi1D43o/MLurx8TfNqdHLja46e68n7
qIqaDn7e395OvvFjOvyGPvAiNiqu6fxs9vJ0/s/o4g3NP45OtituQ22fVG2Df0v3J+r+lOpAq8iJ
4xPTQumHZxVNIh2qFZYtrLP1mlKgeqnq019Gs4s9QP5hU219Sej4OcSHRMobWoZU46/I5ENNqihY
12zyVzp4rG8YhYG3g1Q0XktjpBI1qVFunNffnyzQJXu1cExWuJmYUCnrKaw45q2QLYZQhpONbKb4
7/mrvuH50iaK/Njgq4o92jIGG0+csDkGCQEVKvpydynP62gX6Bhl7rht6+W0K/Lt+uurtyT/b6Kw
gx0la7pe0rCTK5EL/LkmY9x+v5vTp89z2UgMptEgiJ8p9VDRpoc0phCPUa2qlbPFekv5/mOiEWnl
hfMFU2VrWyrhfbEednWIULFeKm9TlVBcuKiDDi4NGTzioT9VtKGB1HUN7yRKjV6KgLaCOCn4vGwM
Qr1VjkJxbF/iPat5TJXyE+snUGNSWWOgdwfbOgEuFKxKrWV3TsEvSzbDnUEvlSk3vHJhLTpPMRfY
k/WpVl7KKBjGOS5BTwV6YFHDgjpEQmmuVrXMh9IaPgFw53Hh58kaIRClgH8FxpccwatoBJvuuSAL
o1DDWZ3pyiWhFBUhlizITbUAQCgo2dJjHbArFFUlH2A1YmMDF+usYY2YKKymIoaKLMZuZ2uY4eV0
+Pw7eBRDAGLcepydn1asrSDkrjAkjYeb0dRGtV6iA4YgzpiesXWG5i0HApLIhDz56JEtggXf2Nh3
utfQldYhCpnSzxFDvti4cYf3VpIhkCRLDIgNSYlSUKB1g9IIHN0ZUT6HaP9tPx48X2COsVq5/DDX
eppVgt2ahDnKWRlqEJ+JE5/J8trui6RypqxzAioHdsz6AEGVSjx5mKB7UHD+ZkkVukTecmK4sL5N
qpvr+YefZB6i/gnvqZuSTTC15ulCCZUGc4pBa6l1OYS7pExijBX2kglza5kwUY+3XWKgYWAp3O1p
2/bz0iIpKvXAO6MKiAJOslJlwVqBMlo5VWNKqp4WUQkfs/NDn9wdaKa7znEok0VG1YpcSO2hhBnj
iOnrgFq7GuVLJJWYRrsmewt8IijE+UsVq74Keol7eYiD4BIHwW3jxGCQ8v9OAqH77o/P3z++7w+z
avNcL0OSYgth5IkdjrfsF/UUrDmWm30aQX4ZK8teiwg7uH00GHaYwrj+aZxfb4y2wdhRZ6nkjsDs
t8fX0cZwbQGzcoVw3EbUkvOZXHrxjHyKXCA0EMcbswzZ6jXFWQgwj0xTppP86LazvsFPhihhJTno
CKrnPsQTUv2AIWT4DWYRRdqxWIbGmYN0yNruPMwqus3laA94KykCZIi04LrlpwPc2QbOSxkgiHi0
zf1bTqsqrkj9sWsaXBG0JP9OJ81CbjOr3mD5grd/pkCf8AwGEFVwfOM9u0203Z9OJUmO7m6I0/Im
cL61LXQGptUbF2wTQZyA2KCbL0OMQ/fKDOBYxAHB+WIJIAhaLvMJZfJ2Ratfz7MN3+HYACPXZnp/
KhGOItMO+vrHCjmY6KopG8CcvxnnizINf/76gg5pdvE3MK/no694/Qe4h8QvZW5kc3RyZWFtCmVu
ZG9iago2OCAwIG9iagoxMzA5CmVuZG9iago3MiAwIG9iago8PC9MZW5ndGggNzMgMCBSL0ZpbHRl
ciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJx9VE1z2zYQvfNX7K32jMSasmIpOcmxVVuN7agye2nd
wwpcUrBAgMZHXPXXd0FJ48CZiTgaDInd997uW+AFzvICzuJzWEWb/bqaQOOyM7jhf5O9ZEUfAIdF
tPC55KApFCMo62yfV8DoHCaTKZRtdrLQnqwmP7y2WHv44Xd9fz9c0Yv7cQd+o7UNaHcwOivGp+Vz
dv4Ryrvs5C3i6cQHrUk9nYKMPDUKAqOhDcpLgc4PBXa4VgQoBDkH1gQOc/npL9no4ghWbiTv0EuQ
llrSHrCqLEeTA78h6KxhhNbB8rEA1BWvU6jICSvXVDExgxXnR7BHEl6yhHHkOAi+yPvvwUq/gyuj
nazIYgxziZClInTEUmqy4E3PXkkngnMRMmhOewP6XrHUR+JEzIf84jsZE5axuHy4/JmEB6PpLWPK
GRzsudLgjXU/bZuDyoiwl+MA4dmwJ0B1bSy3tDW6Ac3bbIFLRHZo2SzZYYR4NXYrOZILQvCEbdSs
oyOyb+uhKxj8hvUMgFBswNQMGKHiVm2UMq8RY4MOWqwIvhEPkZONljVPRTSYXZRtx8LimzhWeOhG
jxR55F7Pp6Tsqw1axaMxz2FJUWxazW3AV5JQkthoo0wj6Qg5b1GqTyBivqRuJkzbxWnMjW0ShntS
EhmBhw6FSdAvlUBPangXROzzZ1IK7nD9jsIfUvM2Is0aY5r4QaqcOROquSKNcM2bVmLCFOk5GhYe
Vb8VP35jXTc5rEjyWVqZ1ig5gNFkPIDy62rx8HXAF0Mxng76rF0qiiJVXu2pZn4PL3v0XPpE1e88
K8PbnQlbuCNKjxfqpt0FdvdPLdlXxydhAF+MJUzpnhljEyFmrg05inxrE44vxnmejyW3UW55JGVq
43xxVcJNu75NUbd595YwIyk8V5SeCiuFkPCY+vZXOX9nkTOz/zwFhwdPPoz6WJ4uzdfavMqfTnm6
eVRVfrjs5v92fNIcXIYmOA+jj4P+Ynx3af69xIagGP/DmPMy+4Of/wHLF7KzZW5kc3RyZWFtCmVu
ZG9iago3MyAwIG9iago3NjIKZW5kb2JqCjc3IDAgb2JqCjw8L0xlbmd0aCA3OCAwIFIvRmlsdGVy
IC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nHVU21LbMBB991fsW2Fq1NgpEPpkcAIkxAwNbplS+qDI
G0eJLQVdQunXV86FqZJij8ce7zlnz0q7eoYWiaDV3Js3q4NPo1ModdCCK/eUwXMQrQCwebEaLnIH
6kAUQz4J1rwI4jacnnYgr4ODvjCoBJqjrqITA3tXN8uORvis9yNwiWNlqXqFuBV9PsxnQfsM8mFw
4EIpVZXUMCBw4dSpKqQ+/BBE7W38m+BLVJoXtNhi+/0+FAgZLRQvHLiBnS+Jhw2h3QphiCUVqMMN
FuLOWRSFcL+gXGyIvZry6guw2Zgl3BDL2jXBxkJ8srVwh65wyFhKhfC8XVv6ghxyZFMhK1nyFfEf
1RWTrJnJdIUmTNae+j3KOQykhBs59dRvXq0oF9JFb6nhUtDqrUDzGjq4Quqn07O5nCZzYQllZK68
NA8oYGill+Ex720EbiU56YTwyGdcOJ8w6oY/rPswlEOXa6M4M6HzIVy8DGHAqSi1hThqtaI4hHTK
xY6XykrygiL5Y7ApmTDhV604XFlR0CVWFfdcpVwzuRHT5RqTsObn3tpdW2cPRenzGzOQyTGv0PdU
OOjU8oQ1iHoF2JPMqGIShhzHmvn7cdtLYUjHUlEjldtq6FklFzspqjUxEcgqOiZoPfGmgeGBu4pp
7bd5lt6PGvWdBmKO8JLUTKsjJ6eJVOVO8/AKBij9vuwLbbixRjZjkmOFrkgrOKNMNsNwvkSu5E7r
OKGZ00nokrgxWJidNKrkEi55aR0VC/neiGKT8b/6kzfuOykML+E7Ckr9hdnyXThZrsJ7Wza0XEPW
6FeQSmEUKup+WOUW2nfarMVENisB/Y/dnZ2rWZ0YXqyn/zhecdIpFfB00CvI02EIaIBWZHOm9X4v
XDkazm1ptYH4LFydbjsn3887WiJEx7+cZi8Pvrr7L4j1jvxlbmRzdHJlYW0KZW5kb2JqCjc4IDAg
b2JqCjY5NgplbmRvYmoKODIgMCBvYmoKPDwvTGVuZ3RoIDgzIDAgUi9GaWx0ZXIgL0ZsYXRlRGVj
b2RlPj4Kc3RyZWFtCnicdZTbTttAEIbv/RQjbgpSso0DIqRXDkmAAmlpcFW1wMVgT5wFezfsAcjb
d3xA4KS1ZVn2/PPNYWf3CXoihF55N++kCD7PB5DZoAen/GTBUxBWAmheSQHHMYuOIOxDvAhqvxD6
+zAYHEFcBLtflSOjyHUnBhcOtq7JbNad05PdtsAJ3RuPZg39XniwFz8E+0OIL4NdNp17VDBGk2sL
f7ySGe59CsL9N3MVdCIz6TBnQ/lrWqDMv1SOtZ+o/aKPWpHogvX9wzfQKKdXVKnxcEXOkE18K04D
xTeVWDWqKCstW7hT0iaTnPMFGswkKiVtC/hTyWcyVro16AXEL8TJtQvIxOO7b+RdJREqb8U597kk
BZeYoZJkWiHOuexV9e8D9aFyEJLc4j+p/0JrZQEzmSwphzNMU0zbvTAysVarNrh2E7U+okazRZ9I
8wjPWsGZz3QLOyHvLMeEmHJ61AUXda8NOm0k2XasEiIY0i0hkav1IqX2ii4LTGHml9zA9tCMXtCk
cK1z76RWG2y0Re0SrXGp9VYBx2vtVdY913AhizY2jsucN3gFJvbeZxFPC6FJlgKd24KecfN4zke5
7FZpt7jfDapsYziWlYPAXGKpj3Sl+cdU8wDAb8qkaiGvsbBcxUblpVisS3G0QuMUf9la2ICbbTkU
AHNakCGVVEvTBByKkC3ftCnQ8XS3NWWgm/nJuB+Gwztuo8GUA3TgWnRg54LW8KJNamGhDXhLIBWw
2ILTvMdTmWC1Pd4r+HDxoeKloYL3B1zSM+V2pwPH4ysIDzolBMqQHZiV3YdwOBwIJpWHFpPGvNRw
uztNxe1eB8hxE0SDnb6umGph5DNvHfQZUR5PG0fXzRVmBOHhHTOncfCD779zgICEZW5kc3RyZWFt
CmVuZG9iago4MyAwIG9iago2NjIKZW5kb2JqCjg3IDAgb2JqCjw8L0xlbmd0aCA4OCAwIFIvRmls
dGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nL2WTXPiRhCG7/yKLi6xqzSKgKw/crMR9rJrNgSU
ciVxDoNo0CzSDJ4ZGbO/Pj1CYFiJxYdUoCgh1N3zzqO3WzxD4LcgcO/yGGeNn0eXMDeNAO7pM288
N1pFAJSHOIPbiIKuoNWGaNbY5LWg3YHLyyuIssZZX1rUEi0LNZ9ZqLzCwYCN8NlUr8AdTnTO9Rra
QeuX8+hro3MN0UPj7Npv+wB9OVM641a8IIxwhhpljOb8p0b7ooiiAn/3WehPEi6nXAs2TWIWp9wY
NuEGp2ypcSZe/6GMVmebsfe6LfM8GPsefOTpihvBPbins/ucLr1gmpZXQ5RzivE9KvZdmSgROOG5
9eCBAj8rnSiJ0oNPdEYLQN+HO641ag+a4cfu8OUCCpHVSoVq2KhuejB1PNmJ3bHgQ7XQ09lK6QUI
ScXUXKMxT+ckKE8L0h2/ynBRymYXGZfb0pS8RG0FmqMMD7c7pJuVenBbA3CMwiJFlFBCv6r6QeSE
qO8ADQsBdNgKaNaA3/A5oZwF7Tcc1Rrv5bPiC7HgK87I6Phq2TITSxYvWb5kBpdc08aVPErpscz2
YFRQ+pasuZS53pw7HmN/n1hVZ3O8WwXUDLpKWq3SIvUPgxqGKZcI1C+O2esaBmoiUqzWcXR31nrX
plgQ/BcGW6uFspxNs4yZGCUZWh3F9WcRW7Tbvm9CzCiNfu+V0P7yocsVeYYQQExNURW6XcsUbEJh
rBaT3FKbFYSEJVRc8jlmKO1xk9WoJy71GKo1foutmtBNIjTBd2iGnHzK9nT5XRKieSq+0fetxuMj
zJlcbvDcKvlVOU+NSzyf2MB3v0oX0bzZ331VI9HZW3lHh7ziHBUjToWcG+e9+1RNeFqt0FVZlksR
F64xzqLlyHZ2cUlIEc4mIcaYbXgE1yd5hGvJMxH/nyzKJessAuM4oS+0ByPmkkA5W92l3FJnVQvd
6Dgh+8Y2126EVVB2ND0eisdnAa2e6g4jtf4XXEGEcSJVquY03bw3jcUUwTjXdFLXsF+iwdjRJ+hX
J6Fvq/qD/vAo8C49mTZN2jzRWLASNvnBTKpB0+/1eodsDg32Q1JPZ/1u9+kcHqk7TaKWDl2EKcYH
Fv0VZlpl1UIjNMjpzoFVMLbF03dq3HSjCUst3H4/veE78e3PbMKxwVXHtMZiMk6UrjPXtuXeKDgM
Y+RZinX/Ph6FRndlt9hBp24m14d2sREnnSD3pr5zFFrgqV9W6b0uqY6Bm3yeGwvta6/4c3e4lIM2
R2hdOji9qPE7vf8Fs2Hz2WVuZHN0cmVhbQplbmRvYmoKODggMCBvYmoKOTU5CmVuZG9iago5MiAw
IG9iago8PC9MZW5ndGggOTMgMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJyNll1T
4kgUhu/5Fae4Wa0KWcKXOjdbGEBRoixkx7FWL9qkIT0k3bE7geHf7+kOEZSwNVCSmHTOefs5X3mH
pu1AU393xyCp/Tm7gKWqNeEG/5a195pjFsDuECRw7eOiS3Ba4C9qxXMOtNpwcXEJflI7G/OMSk6z
xkCSRQZHn4HnNWb0XR3fgRF9kzmRW2g1nc65/7PWvgJ/UjvDW/9OSUplY8BUJtlbntHQ9sQbi1m2
tWd0zejm9fyPmtMu1x983IhwC25tC57FSmSkOP/BqAV3eDKnLMPTKZ4SHsLAhgnLLTT2xUz9wHex
cstJwgIodYBHOFnShPIMGC8u02M7JZ9v4OZS6sX9NJWCBBFVxu5YqZyqugVwJ3LJSQxicWzGFUmS
cxaQjAmuLFiL2IaeBVzY4FiQpjZ0Gk7X+gTVsdFQq/c7UOf94UmiI6YiKi3wkFmfh1QqgYRH+N+9
SBWN8aoGG0RkoZfd7NB69vE2cFGM0HBVvQ+HhMfTPdgSECyEhPYNoLZ6RYRgKkVAacj4UiEzyCIK
zlUW7ZAbUkhzvk1SoViegODHRqZmNwT3MOahQH9GuYklzEjIxBfy8HI2HXsz9+W8QlGr2bysRD4R
+nG+tP9RVJ7kfM/k27bgVy+fMLvST+kE+STlVKrt9m0hi6tupRqPLWUh51Yk1O4vMSvVSVVPZMVW
ZIN1NENh30lMQh3+Msp3Nni5JAw1f9gFbfdYX+EIfLEhMlQfldFQAUHaH+Ef0DQWW11X6nfD3nc9
aKEYVzwMf/h44JiJlAcUMOgwyrNcVuh5oNlGyJUW7NMg4iIWS0axuAY0oMkblTqgvWqEJkPsAcmI
/bhYxIJoPScZTii2nHskZk50G3pGYM94nEX6yngHc25j+xJ8qWGe6CfaJexdfkPWG4wAVotLODyx
EUP5MVtT+ZdOmfn4xn30vKpcdZqW+f2ywdnIbV9026+gGxzXpYohLuoZ6/2nKLXpUM1oTHT1+lQm
zPDbmpBVQkDDoC2jwZxTzbZz7LrbcrTrm5yHZE3jGDHNDbdcU9EIB3RNJEmJufcdLyCxTRjlcmvu
n/Kud3BtwxQTFGujjkn0a1sW+ni67iEsLVD7x36WL3OVVdWzlti+bKLEuYhZUo4al6gM1eZBwLBQ
XLwyjD0Sr1ihWTuf2KekXet9mp54iwcigwhLPD4Uh13n1tMnL+cfdXIc0v1AKjeDSi14DDKxS+aq
3Vx1Oq+mD2IhqEJ7/bAbz/M0FTIzzRgldNA0DmBFw/+PtLZrwYNYl5VUlWi9Vks7x6mQsDCzwEfn
T4RGMVNBVAycXVncSxxCXOOuXxNFT3ne9w6j18vjDFliKCc4ayhm88d2cGQf5kBFNy24T0vuA5EQ
JLRDq5VjnqSSxVWT1uztovsV7J2IuBmeg3337MvV6lNR7RSe2iIKP8hX7UUXVLwf+L2ueUq/B6H+
YWjjrAKaAcE3huIz/JUyia8fZZpfmUbQ+exHt7olTtRL3dWGfu1v/P4HdlS3rmVuZHN0cmVhbQpl
bmRvYmoKOTMgMCBvYmoKMTEzNQplbmRvYmoKOTcgMCBvYmoKPDwvTGVuZ3RoIDk4IDAgUi9GaWx0
ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnichZXbUuM4EIbv8xRd3AxUOV4fCJDdG0xODATIJKaW
ZdgLYXdsEVsKshTIPP22HFOzniy1dlKOLbn7+9V/K6/guT549myuSdn5bX4KWdXxYELfrPPa8esJ
0FySEi5imnQGfgDxsrN7z4cghNPTM4jLzuFXoVEJ1N2hYksNe8fw5qY7x9dqfwTG+KwMU1sIPP/4
KH7phH2Ip51DGvo+Hw9OQs//G+AxNw48ug78yVZ8xd6YA3O6YyKFqUujTGQOHESwMGqDW5BLuJHP
vOB6e/Sl44cfEf91LMx6LZUGLkDnCB8KDijweAA2rQNXpqi5fJeiBCctrlOvR1zXile5YMKBBeFc
S5kWfIc2lUYhV9KBmcUm/G8NcOR+xjQ0WpOyg6lMWMF/YApzaTQXGSylgpmS79udLuKdbU4OHAr0
S4gantgICNcay2dUVkHwHwr6Xp8UTIxI2QYLy201POaSWB9qNSqXAknbFd2NkWfowKQRMf9UxMci
HBDiMcRkiCVP4G65LCRLiarARJOau7XmUvwUti+lpXQnjJAdiNaKF1ZU+IuoeOEGoXtMhvmMLZzM
ZkQ2QYGKFTBjyQo1zFnKJZGpDU8Qng4ns/ni6QhQkK0SLFHoap/Ogo82sthQle4F36CqKGKMSmGl
Faffu7BRkmBVwS3qN6lW+3GeDkfd+3ge3VJGVs8lsZYT4jns5FAjuvTxHLhhKsk/k94PvfD/lA9l
ycjxt6xEWGwrMohd/QRTMmv1Byw0yxDChmAfdodEeYB6IrBE+y5r+jcyOpeq+gJRmlLsCqsW8SVE
giaILQxolWkVMOVki6ejloBLw96Q06omuZCFzDh+VKIXHnswxYwlWxgqFy4ML1LbKSE1XMEE9V38
AKc9Lzh24H4RNa+NSH7xO+QucxPKe84R0ZUq+8lt25CtkSJNuWnBDHIuWOPKJhwVXgcOBGfwYJh4
M+SVdw7Rhhpl9wCG3Loh0Q5cIH+xgL7neT2irMO1sQpu0jr3eWIHyzqVm8iyhTfjZDKerGjtucYW
4p2ijfADjoQrg5AaGBSyggFtSBoLAplB3w+CE0KgukjRXeCGZ4Lq3uv5pGasrO3bZOsmp1vZnOey
zrNHdslT1LLKOfwlV1KzFtv1cPgVpuy5CRx0/a7fg7ucKdryxuaFl9xWbcG4ZiU9Cnsn3TOqH1yx
NRNtnG0d/nyVprxgz5X7sqbxvl+navw0St2nIweovVnhNvYdva85eREik5lKQ0Cbif3XaXscvs9s
E/h920ujuPONzn8AXkPlnGVuZHN0cmVhbQplbmRvYmoKOTggMCBvYmoKOTYwCmVuZG9iagoxMDIg
MCBvYmoKPDwvTGVuZ3RoIDEwMyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nGWP
UU/CMBSF3/srzpuQwGzHIuCTAkNRMUj2Jj7UUUbZ2kLbJfrv7XC+SG+am9zz3XtyTqARA22q7bki
1+shCkcoHsIvyImwM4C25QqTLEAjsBjZjvzuMcQDDIcjZIp0FtoLq4XvzyzfeVy82XLZX4uTu1Qw
F5+25vYbMWVJNzuQwRjZC+kE6cnUWuLZ2L3RQnevCBv8SRNr+DY3ClOjVKBy7qXRLjCNujK2LHnF
dcl9jTjpYb547VPKRhSPonJSlzLMpA7Itt1JFZfVLQ6NZ6SNO3J1VzSzKNgE5iZOzubTPdfYdNJt
tOn2IDx4FbVR0q+jtMLhvi5q5xGPe+dQ/wK/r3ghgvARjqYZeQv1A67OZi5lbmRzdHJlYW0KZW5k
b2JqCjEwMyAwIG9iagoyNzYKZW5kb2JqCjQgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFsw
IDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsv
UERGIC9UZXh0XQovRXh0R1N0YXRlIDkgMCBSCi9Gb250IDEwIDAgUgo+PgovQ29udGVudHMgNSAw
IFIKPj4KZW5kb2JqCjExIDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJd
Ci9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0K
L0V4dEdTdGF0ZSAxNCAwIFIKL0ZvbnQgMTUgMCBSCj4+Ci9Db250ZW50cyAxMiAwIFIKPj4KZW5k
b2JqCjE2IDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUg
MC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0
ZSAxOSAwIFIKL0ZvbnQgMjAgMCBSCj4+Ci9Db250ZW50cyAxNyAwIFIKPj4KZW5kb2JqCjIxIDAg
b2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQg
MyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSAyNCAwIFIK
L0ZvbnQgMjUgMCBSCj4+Ci9Db250ZW50cyAyMiAwIFIKPj4KZW5kb2JqCjI2IDAgb2JqCjw8L1R5
cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jl
c291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSAyOSAwIFIKL0ZvbnQgMzAg
MCBSCj4+Ci9Db250ZW50cyAyNyAwIFIKPj4KZW5kb2JqCjMxIDAgb2JqCjw8L1R5cGUvUGFnZS9N
ZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8
L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSAzNCAwIFIKL0ZvbnQgMzUgMCBSCj4+Ci9D
b250ZW50cyAzMiAwIFIKPj4KZW5kb2JqCjM2IDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBb
MCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRb
L1BERiAvVGV4dF0KL0V4dEdTdGF0ZSAzOSAwIFIKL0ZvbnQgNDAgMCBSCj4+Ci9Db250ZW50cyAz
NyAwIFIKPj4KZW5kb2JqCjQxIDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4
NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4
dF0KL0V4dEdTdGF0ZSA0NCAwIFIKL0ZvbnQgNDUgMCBSCj4+Ci9Db250ZW50cyA0MiAwIFIKPj4K
ZW5kb2JqCjQ2IDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3Rh
dGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdT
dGF0ZSA0OSAwIFIKL0ZvbnQgNTAgMCBSCj4+Ci9Db250ZW50cyA0NyAwIFIKPj4KZW5kb2JqCjUx
IDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJl
bnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSA1NCAw
IFIKL0ZvbnQgNTUgMCBSCj4+Ci9Db250ZW50cyA1MiAwIFIKPj4KZW5kb2JqCjU2IDAgb2JqCjw8
L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIK
L1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSA1OSAwIFIKL0ZvbnQg
NjAgMCBSCj4+Ci9Db250ZW50cyA1NyAwIFIKPj4KZW5kb2JqCjYxIDAgb2JqCjw8L1R5cGUvUGFn
ZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNl
czw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSA2NCAwIFIKL0ZvbnQgNjUgMCBSCj4+
Ci9Db250ZW50cyA2MiAwIFIKPj4KZW5kb2JqCjY2IDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJv
eCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NT
ZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSA2OSAwIFIKL0ZvbnQgNzAgMCBSCj4+Ci9Db250ZW50
cyA2NyAwIFIKPj4KZW5kb2JqCjcxIDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5
NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAv
VGV4dF0KL0V4dEdTdGF0ZSA3NCAwIFIKL0ZvbnQgNzUgMCBSCj4+Ci9Db250ZW50cyA3MiAwIFIK
Pj4KZW5kb2JqCjc2IDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9S
b3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4
dEdTdGF0ZSA3OSAwIFIKL0ZvbnQgODAgMCBSCj4+Ci9Db250ZW50cyA3NyAwIFIKPj4KZW5kb2Jq
CjgxIDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9Q
YXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSA4
NCAwIFIKL0ZvbnQgODUgMCBSCj4+Ci9Db250ZW50cyA4MiAwIFIKPj4KZW5kb2JqCjg2IDAgb2Jq
Cjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAw
IFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSA4OSAwIFIKL0Zv
bnQgOTAgMCBSCj4+Ci9Db250ZW50cyA4NyAwIFIKPj4KZW5kb2JqCjkxIDAgb2JqCjw8L1R5cGUv
UGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291
cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSA5NCAwIFIKL0ZvbnQgOTUgMCBS
Cj4+Ci9Db250ZW50cyA5MiAwIFIKPj4KZW5kb2JqCjk2IDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRp
YUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1By
b2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSA5OSAwIFIKL0ZvbnQgMTAwIDAgUgo+PgovQ29u
dGVudHMgOTcgMCBSCj4+CmVuZG9iagoxMDEgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFsw
IDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsv
UERGIC9UZXh0XQovRXh0R1N0YXRlIDEwNCAwIFIKL0ZvbnQgMTA1IDAgUgo+PgovQ29udGVudHMg
MTAyIDAgUgo+PgplbmRvYmoKMyAwIG9iago8PCAvVHlwZSAvUGFnZXMgL0tpZHMgWwo0IDAgUgox
MSAwIFIKMTYgMCBSCjIxIDAgUgoyNiAwIFIKMzEgMCBSCjM2IDAgUgo0MSAwIFIKNDYgMCBSCjUx
IDAgUgo1NiAwIFIKNjEgMCBSCjY2IDAgUgo3MSAwIFIKNzYgMCBSCjgxIDAgUgo4NiAwIFIKOTEg
MCBSCjk2IDAgUgoxMDEgMCBSCl0gL0NvdW50IDIwCj4+CmVuZG9iagoxIDAgb2JqCjw8L1R5cGUg
L0NhdGFsb2cgL1BhZ2VzIDMgMCBSCi9NZXRhZGF0YSAxMDYgMCBSCj4+CmVuZG9iago3IDAgb2Jq
Cjw8L1R5cGUvRXh0R1N0YXRlCi9PUE0gMT4+ZW5kb2JqCjkgMCBvYmoKPDwvUjcKNyAwIFI+Pgpl
bmRvYmoKMTAgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKMTQgMCBvYmoKPDwvUjcKNyAwIFI+
PgplbmRvYmoKMTUgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKMTkgMCBvYmoKPDwvUjcKNyAw
IFI+PgplbmRvYmoKMjAgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKMjQgMCBvYmoKPDwvUjcK
NyAwIFI+PgplbmRvYmoKMjUgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKMjkgMCBvYmoKPDwv
UjcKNyAwIFI+PgplbmRvYmoKMzAgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKMzQgMCBvYmoK
PDwvUjcKNyAwIFI+PgplbmRvYmoKMzUgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKMzkgMCBv
YmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKNDAgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKNDQg
MCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKNDUgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoK
NDkgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKNTAgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRv
YmoKNTQgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKNTUgMCBvYmoKPDwvUjgKOCAwIFI+Pgpl
bmRvYmoKNTkgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKNjAgMCBvYmoKPDwvUjgKOCAwIFI+
PgplbmRvYmoKNjQgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKNjUgMCBvYmoKPDwvUjgKOCAw
IFI+PgplbmRvYmoKNjkgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKNzAgMCBvYmoKPDwvUjgK
OCAwIFI+PgplbmRvYmoKNzQgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKNzUgMCBvYmoKPDwv
UjgKOCAwIFI+PgplbmRvYmoKNzkgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKODAgMCBvYmoK
PDwvUjgKOCAwIFI+PgplbmRvYmoKODQgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKODUgMCBv
YmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKODkgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKOTAg
MCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKOTQgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoK
OTUgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKOTkgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRv
YmoKMTAwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjEwNCAwIG9iago8PC9SNwo3IDAgUj4+
CmVuZG9iagoxMDUgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKOCAwIG9iago8PC9CYXNlRm9u
dC9Db3VyaWVyL1R5cGUvRm9udAovU3VidHlwZS9UeXBlMT4+CmVuZG9iagoxMDYgMCBvYmoKPDwv
VHlwZS9NZXRhZGF0YQovU3VidHlwZS9YTUwvTGVuZ3RoIDEzMjk+PnN0cmVhbQo8P3hwYWNrZXQg
YmVnaW49J++7vycgaWQ9J1c1TTBNcENlaGlIenJlU3pOVGN6a2M5ZCc/Pgo8P2Fkb2JlLXhhcC1m
aWx0ZXJzIGVzYz0iQ1JMRiI/Pgo8eDp4bXBtZXRhIHhtbG5zOng9J2Fkb2JlOm5zOm1ldGEvJyB4
OnhtcHRrPSdYTVAgdG9vbGtpdCAyLjkuMS0xMywgZnJhbWV3b3JrIDEuNic+CjxyZGY6UkRGIHht
bG5zOnJkZj0naHR0cDovL3d3dy53My5vcmcvMTk5OS8wMi8yMi1yZGYtc3ludGF4LW5zIycgeG1s
bnM6aVg9J2h0dHA6Ly9ucy5hZG9iZS5jb20vaVgvMS4wLyc+CjxyZGY6RGVzY3JpcHRpb24gcmRm
OmFib3V0PSc4NjllZWQ5ZS1kNWM0LTExZWUtMDAwMC00MWE1M2IwNTFmODcnIHhtbG5zOnBkZj0n
aHR0cDovL25zLmFkb2JlLmNvbS9wZGYvMS4zLycgcGRmOlByb2R1Y2VyPSdHUEwgR2hvc3RzY3Jp
cHQgOS4wMicvPgo8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0nODY5ZWVkOWUtZDVjNC0xMWVl
LTAwMDAtNDFhNTNiMDUxZjg3JyB4bWxuczp4bXA9J2h0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEu
MC8nPjx4bXA6TW9kaWZ5RGF0ZT4yMDE0LTAyLTI1VDAwOjA0OjEzKzAxOjAwPC94bXA6TW9kaWZ5
RGF0ZT4KPHhtcDpDcmVhdGVEYXRlPjIwMTQtMDItMjVUMDA6MDQ6MTMrMDE6MDA8L3htcDpDcmVh
dGVEYXRlPgo8eG1wOkNyZWF0b3JUb29sPkdOVSBFbnNjcmlwdCAxLjYuNS45MDwveG1wOkNyZWF0
b3JUb29sPjwvcmRmOkRlc2NyaXB0aW9uPgo8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0nODY5
ZWVkOWUtZDVjNC0xMWVlLTAwMDAtNDFhNTNiMDUxZjg3JyB4bWxuczp4YXBNTT0naHR0cDovL25z
LmFkb2JlLmNvbS94YXAvMS4wL21tLycgeGFwTU06RG9jdW1lbnRJRD0nODY5ZWVkOWUtZDVjNC0x
MWVlLTAwMDAtNDFhNTNiMDUxZjg3Jy8+CjxyZGY6RGVzY3JpcHRpb24gcmRmOmFib3V0PSc4Njll
ZWQ5ZS1kNWM0LTExZWUtMDAwMC00MWE1M2IwNTFmODcnIHhtbG5zOmRjPSdodHRwOi8vcHVybC5v
cmcvZGMvZWxlbWVudHMvMS4xLycgZGM6Zm9ybWF0PSdhcHBsaWNhdGlvbi9wZGYnPjxkYzp0aXRs
ZT48cmRmOkFsdD48cmRmOmxpIHhtbDpsYW5nPSd4LWRlZmF1bHQnPkVuc2NyaXB0IE91dHB1dDwv
cmRmOmxpPjwvcmRmOkFsdD48L2RjOnRpdGxlPjwvcmRmOkRlc2NyaXB0aW9uPgo8L3JkZjpSREY+
CjwveDp4bXBtZXRhPgogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCjw/eHBhY2tldCBl
bmQ9J3cnPz4KZW5kc3RyZWFtCmVuZG9iagoyIDAgb2JqCjw8L1Byb2R1Y2VyKEdQTCBHaG9zdHNj
cmlwdCA5LjAyKQovQ3JlYXRpb25EYXRlKEQ6MjAxNDAyMjUwMDA0MTMrMDEnMDAnKQovTW9kRGF0
ZShEOjIwMTQwMjI1MDAwNDEzKzAxJzAwJykKL1RpdGxlKEVuc2NyaXB0IE91dHB1dCkKL0NyZWF0
b3IoR05VIEVuc2NyaXB0IDEuNi41LjkwKT4+ZW5kb2JqCnhyZWYKMCAxMDcKMDAwMDAwMDAwMCA2
NTUzNSBmIAowMDAwMDI0NjY1IDAwMDAwIG4gCjAwMDAwMjc0NDMgMDAwMDAgbiAKMDAwMDAyNDQ3
MSAwMDAwMCBuIAowMDAwMDIxMjI5IDAwMDAwIG4gCjAwMDAwMDAwMTUgMDAwMDAgbiAKMDAwMDAw
MTE2NSAwMDAwMCBuIAowMDAwMDI0NzMxIDAwMDAwIG4gCjAwMDAwMjU5NzQgMDAwMDAgbiAKMDAw
MDAyNDc3MiAwMDAwMCBuIAowMDAwMDI0ODAxIDAwMDAwIG4gCjAwMDAwMjEzODggMDAwMDAgbiAK
MDAwMDAwMTE4NSAwMDAwMCBuIAowMDAwMDAxODIwIDAwMDAwIG4gCjAwMDAwMjQ4MzEgMDAwMDAg
biAKMDAwMDAyNDg2MSAwMDAwMCBuIAowMDAwMDIxNTUwIDAwMDAwIG4gCjAwMDAwMDE4NDAgMDAw
MDAgbiAKMDAwMDAwMjM4MyAwMDAwMCBuIAowMDAwMDI0ODkxIDAwMDAwIG4gCjAwMDAwMjQ5MjEg
MDAwMDAgbiAKMDAwMDAyMTcxMiAwMDAwMCBuIAowMDAwMDAyNDAzIDAwMDAwIG4gCjAwMDAwMDM5
ODIgMDAwMDAgbiAKMDAwMDAyNDk1MSAwMDAwMCBuIAowMDAwMDI0OTgxIDAwMDAwIG4gCjAwMDAw
MjE4NzQgMDAwMDAgbiAKMDAwMDAwNDAwMyAwMDAwMCBuIAowMDAwMDA1NDgxIDAwMDAwIG4gCjAw
MDAwMjUwMTEgMDAwMDAgbiAKMDAwMDAyNTA0MSAwMDAwMCBuIAowMDAwMDIyMDM2IDAwMDAwIG4g
CjAwMDAwMDU1MDIgMDAwMDAgbiAKMDAwMDAwNjU4MyAwMDAwMCBuIAowMDAwMDI1MDcxIDAwMDAw
IG4gCjAwMDAwMjUxMDEgMDAwMDAgbiAKMDAwMDAyMjE5OCAwMDAwMCBuIAowMDAwMDA2NjA0IDAw
MDAwIG4gCjAwMDAwMDc2NDUgMDAwMDAgbiAKMDAwMDAyNTEzMSAwMDAwMCBuIAowMDAwMDI1MTYx
IDAwMDAwIG4gCjAwMDAwMjIzNjAgMDAwMDAgbiAKMDAwMDAwNzY2NSAwMDAwMCBuIAowMDAwMDA4
NTY1IDAwMDAwIG4gCjAwMDAwMjUxOTEgMDAwMDAgbiAKMDAwMDAyNTIyMSAwMDAwMCBuIAowMDAw
MDIyNTIyIDAwMDAwIG4gCjAwMDAwMDg1ODUgMDAwMDAgbiAKMDAwMDAwOTg3NiAwMDAwMCBuIAow
MDAwMDI1MjUxIDAwMDAwIG4gCjAwMDAwMjUyODEgMDAwMDAgbiAKMDAwMDAyMjY4NCAwMDAwMCBu
IAowMDAwMDA5ODk3IDAwMDAwIG4gCjAwMDAwMTEyMDAgMDAwMDAgbiAKMDAwMDAyNTMxMSAwMDAw
MCBuIAowMDAwMDI1MzQxIDAwMDAwIG4gCjAwMDAwMjI4NDYgMDAwMDAgbiAKMDAwMDAxMTIyMSAw
MDAwMCBuIAowMDAwMDEyNTA0IDAwMDAwIG4gCjAwMDAwMjUzNzEgMDAwMDAgbiAKMDAwMDAyNTQw
MSAwMDAwMCBuIAowMDAwMDIzMDA4IDAwMDAwIG4gCjAwMDAwMTI1MjUgMDAwMDAgbiAKMDAwMDAx
MzcwOCAwMDAwMCBuIAowMDAwMDI1NDMxIDAwMDAwIG4gCjAwMDAwMjU0NjEgMDAwMDAgbiAKMDAw
MDAyMzE3MCAwMDAwMCBuIAowMDAwMDEzNzI5IDAwMDAwIG4gCjAwMDAwMTUxMTAgMDAwMDAgbiAK
MDAwMDAyNTQ5MSAwMDAwMCBuIAowMDAwMDI1NTIxIDAwMDAwIG4gCjAwMDAwMjMzMzIgMDAwMDAg
biAKMDAwMDAxNTEzMSAwMDAwMCBuIAowMDAwMDE1OTY1IDAwMDAwIG4gCjAwMDAwMjU1NTEgMDAw
MDAgbiAKMDAwMDAyNTU4MSAwMDAwMCBuIAowMDAwMDIzNDk0IDAwMDAwIG4gCjAwMDAwMTU5ODUg
MDAwMDAgbiAKMDAwMDAxNjc1MyAwMDAwMCBuIAowMDAwMDI1NjExIDAwMDAwIG4gCjAwMDAwMjU2
NDEgMDAwMDAgbiAKMDAwMDAyMzY1NiAwMDAwMCBuIAowMDAwMDE2NzczIDAwMDAwIG4gCjAwMDAw
MTc1MDcgMDAwMDAgbiAKMDAwMDAyNTY3MSAwMDAwMCBuIAowMDAwMDI1NzAxIDAwMDAwIG4gCjAw
MDAwMjM4MTggMDAwMDAgbiAKMDAwMDAxNzUyNyAwMDAwMCBuIAowMDAwMDE4NTU4IDAwMDAwIG4g
CjAwMDAwMjU3MzEgMDAwMDAgbiAKMDAwMDAyNTc2MSAwMDAwMCBuIAowMDAwMDIzOTgwIDAwMDAw
IG4gCjAwMDAwMTg1NzggMDAwMDAgbiAKMDAwMDAxOTc4NSAwMDAwMCBuIAowMDAwMDI1NzkxIDAw
MDAwIG4gCjAwMDAwMjU4MjEgMDAwMDAgbiAKMDAwMDAyNDE0MiAwMDAwMCBuIAowMDAwMDE5ODA2
IDAwMDAwIG4gCjAwMDAwMjA4MzggMDAwMDAgbiAKMDAwMDAyNTg1MSAwMDAwMCBuIAowMDAwMDI1
ODgxIDAwMDAwIG4gCjAwMDAwMjQzMDUgMDAwMDAgbiAKMDAwMDAyMDg1OCAwMDAwMCBuIAowMDAw
MDIxMjA4IDAwMDAwIG4gCjAwMDAwMjU5MTIgMDAwMDAgbiAKMDAwMDAyNTk0MyAwMDAwMCBuIAow
MDAwMDI2MDM2IDAwMDAwIG4gCnRyYWlsZXIKPDwgL1NpemUgMTA3IC9Sb290IDEgMCBSIC9JbmZv
IDIgMCBSCi9JRCBbPDY1QzAxMkUwMDZFRDQ5QTgyRUJFMkIwRDc1Njg2QkFFPjw2NUMwMTJFMDA2
RUQ0OUE4MkVCRTJCMEQ3NTY4NkJBRT5dCj4+CnN0YXJ0eHJlZgoyNzYyMgolJUVPRgo=

------=_NextPart_000_00C1_01CF321C.084D7200
Content-Type: text/plain;
	name="draft-ietf-dmm-requirements-15.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="draft-ietf-dmm-requirements-15.txt"

=0A=
=0A=
=0A=
Network Working Group                                      H. Chan (Ed.)=0A=
Internet-Draft                                       Huawei Technologies=0A=
Intended status: Informational                                    D. Liu=0A=
Expires: August 29, 2014                                    China Mobile=0A=
                                                                P. Seite=0A=
                                                                  Orange=0A=
                                                               H. Yokota=0A=
                                                                KDDI Lab=0A=
                                                             J. Korhonen=0A=
                                                 Broadcom Communications=0A=
                                                       February 25, 2014=0A=
=0A=
=0A=
            Requirements for Distributed Mobility Management=0A=
                     draft-ietf-dmm-requirements-15=0A=
=0A=
Abstract=0A=
=0A=
   This document defines the requirements for Distributed Mobility=0A=
   Management (DMM) at the network layer.  The hierarchical structure in=0A=
   traditional wireless networks has led primarily to centrally deployed=0A=
   mobility anchors.  As some wireless networks are evolving away from=0A=
   the hierarchical structure, it can be useful have a distributed model=0A=
   for mobility management in which traffic does not need to traverse=0A=
   centrally deployed mobility anchors far from the optimal route.=0A=
=0A=
Requirements Language=0A=
=0A=
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",=0A=
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this=0A=
   document are to be interpreted as described in RFC 2119 RFC 2119=0A=
   [RFC2119].=0A=
=0A=
Status of this Memo=0A=
=0A=
   This Internet-Draft is submitted in full conformance with the=0A=
   provisions of BCP 78 and BCP 79.=0A=
=0A=
   Internet-Drafts are working documents of the Internet Engineering=0A=
   Task Force (IETF).  Note that other groups may also distribute=0A=
   working documents as Internet-Drafts.  The list of current Internet-=0A=
   Drafts is at http://datatracker.ietf.org/drafts/current/.=0A=
=0A=
   Internet-Drafts are draft documents valid for a maximum of six months=0A=
   and may be updated, replaced, or obsoleted by other documents at any=0A=
   time.  It is inappropriate to use Internet-Drafts as reference=0A=
   material or to cite them other than as "work in progress."=0A=
=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014                [Page 1]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
   This Internet-Draft will expire on August 29, 2014.=0A=
=0A=
Copyright Notice=0A=
=0A=
   Copyright (c) 2014 IETF Trust and the persons identified as the=0A=
   document authors.  All rights reserved.=0A=
=0A=
   This document is subject to BCP 78 and the IETF Trust's Legal=0A=
   Provisions Relating to IETF Documents=0A=
   (http://trustee.ietf.org/license-info) in effect on the date of=0A=
   publication of this document.  Please review these documents=0A=
   carefully, as they describe your rights and restrictions with respect=0A=
   to this document.  Code Components extracted from this document must=0A=
   include Simplified BSD License text as described in Section 4.e of=0A=
   the Trust Legal Provisions and are provided without warranty as=0A=
   described in the Simplified BSD License.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014                [Page 2]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
Table of Contents=0A=
=0A=
   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4=0A=
   2.  Conventions used in this document  . . . . . . . . . . . . . .  5=0A=
     2.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  5=0A=
   3.  Centralized versus distributed mobility management . . . . . .  6=0A=
     3.1.  Centralized mobility management  . . . . . . . . . . . . .  7=0A=
     3.2.  Distributed mobility management  . . . . . . . . . . . . .  8=0A=
   4.  Problem Statement  . . . . . . . . . . . . . . . . . . . . . .  9=0A=
   5.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 11=0A=
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 14=0A=
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14=0A=
   8.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 14=0A=
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 16=0A=
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 16=0A=
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 17=0A=
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014                [Page 3]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
1.  Introduction=0A=
=0A=
   In the past decade a fair number of network-layer mobility protocols=0A=
   have been standardized [RFC6275] [RFC5944] [RFC5380] [RFC6301]=0A=
   [RFC5213].  Although the protocols differ in terms of functions and=0A=
   associated message formats, they all employ a mobility anchor to=0A=
   allow a mobile node to remain reachable after it has moved to a=0A=
   different network.  The anchor point, among other tasks, ensures=0A=
   connectivity by forwarding packets destined to, or sent from, the=0A=
   mobile node.  It is a centrally deployed mobility anchor in the sense=0A=
   that the deployed architectures today have a small number of these=0A=
   anchors and the traffic of millions of mobile nodes in an operator=0A=
   network are typically managed by the same anchor.=0A=
=0A=
   Distributed mobility management (DMM) is an alternative to the above=0A=
   centralized deployment.  The background behind the interests to study=0A=
   DMM are primarily in the following.=0A=
=0A=
   (1)  Mobile users are, more than ever, consuming Internet content=0A=
        including that of local Content Delivery Networks (CDNs) which=0A=
        had not taken mobility service into account before.  Such=0A=
        traffic imposes new requirements on mobile core networks for=0A=
        data traffic delivery.  To prevent exceeding the available core=0A=
        network capacity, service providers need to implement new=0A=
        strategies such as selective IPv4 traffic offload (e.g.,=0A=
        [RFC6909], Third Generation Partnership Project (3GPP) work=0A=
        items Local IP Access (LIPA) and Selected IP Traffic Offload=0A=
        (SIPTO) [TS.23.401]) through alternative access networks such as=0A=
        Wireless Local Area Network (WLAN) [Paper-=0A=
        Mobile.Data.Offloading].  In addition, a gateway selection=0A=
        mechanism takes the user proximity into account within the EPC=0A=
        Evolved Packet Core (EPC) [TS.29303].  Yet these mechanisms were=0A=
        not pursued in the past owing to charging and billing which=0A=
        require solutions beyond the mobility protocol.  Consequently,=0A=
        assigning a gateway anchor node from a visited network in=0A=
        roaming scenario has until recently been done and are limited to=0A=
        voice services only.=0A=
=0A=
        Both traffic offloading and CDN mechanisms could benefit from=0A=
        the development of mobile architectures with fewer levels of=0A=
        routing hierarchy introduced into the data path by the mobility=0A=
        management system.  This trend towards so-called "flat networks"=0A=
        works best for direct communications among peers in the same=0A=
        geographical area.  Distributed mobility management in a truly=0A=
        flat mobile architecture would anchor the traffic closer to the=0A=
        point of attachment of the user.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014                [Page 4]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
   (2)  Today's mobile networks present service providers with new=0A=
        challenges.  Mobility patterns indicate that mobile nodes often=0A=
        remain attached to the same point of attachment for considerable=0A=
        periods of time [Paper-Locating.User].  Specific IP mobility=0A=
        management support is not required for applications that launch=0A=
        and complete their sessions while the mobile node is connected=0A=
        to the same point of attachment.  However, currently, IP=0A=
        mobility support is designed for always-on operation,=0A=
        maintaining all parameters of the context for each mobile=0A=
        subscriber for as long as they are connected to the network.=0A=
        This can result in a waste of resources and unnecessary costs=0A=
        for the service provider.  Infrequent node mobility coupled with=0A=
        application intelligence suggest that mobility support could be=0A=
        provided selectively such as in [I-D.bhandari-dhc-class-based-=0A=
        prefix] and [I-D.korhonen-6man-prefix-properties], thus reducing=0A=
        the amount of context maintained in the network.=0A=
=0A=
   DMM may distribute the mobility anchors in the data-plane towards a=0A=
   more flat network such that the mobility anchors are positioned=0A=
   closer to the user; ideally, mobility agents could be collocated with=0A=
   the first-hop router.  Facilitated by the distribution of mobility=0A=
   anchors, it may be possible to selectively use or not use mobility=0A=
   protocol support depending on whether such support is needed or not.=0A=
   It can thus reduce the amount of state information that must be=0A=
   maintained in various mobility agents of the mobile network.  It can=0A=
   then avoid the unnecessary establishment of mechanisms to forward=0A=
   traffic from an old to a new mobility anchor.=0A=
=0A=
   This document compares distributed mobility management with=0A=
   centralized mobility management in Section 3.  The problems that can=0A=
   be addressed with DMM are summarized in Section 4.  The mandatory=0A=
   requirements as well as the optional requirements for network-layer=0A=
   distributed mobility management are given in Section 5.  Finally,=0A=
   security considerations are discussed in Section 6.=0A=
=0A=
   The problem statement and the use cases [I-D.yokota-dmm-scenario] can=0A=
   be found in [Paper-Distributed.Mobility.Review].=0A=
=0A=
=0A=
2.  Conventions used in this document=0A=
=0A=
2.1.  Terminology=0A=
=0A=
   All the general mobility-related terms and their acronyms used in=0A=
   this document are to be interpreted as defined in the Mobile IPv6=0A=
   base specification [RFC6275], in the Proxy mobile IPv6 specification=0A=
   [RFC5213], and in Mobility Related Terminology [RFC3753].  These=0A=
   terms include the following: mobile node (MN), correspondent node=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014                [Page 5]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
   (CN), and home agent (HA) as per [RFC6275]; local mobility anchor=0A=
   (LMA) and mobile access gateway (MAG) as per [RFC5213], and context=0A=
   as per [RFC3753].=0A=
=0A=
   In addition, this draft introduces the following terms.=0A=
=0A=
   Centrally deployed mobility anchors=0A=
=0A=
      refer to the mobility management deployments in which there are=0A=
      very few mobility anchors and the traffic of millions of mobile=0A=
      nodes in an operator network are managed by the same anchor.=0A=
=0A=
   Centralized mobility management=0A=
=0A=
      makes use of centrally deployed mobility anchors.=0A=
=0A=
   Distributed mobility management=0A=
=0A=
      is not centralized so that traffic does not need to traverse=0A=
      centrally deployed mobility anchors far from the optimal route.=0A=
=0A=
   Flat mobile network=0A=
=0A=
      has few levels of routing hierarchy introduced into the data path=0A=
      by the mobility management system.=0A=
=0A=
   Mobility context=0A=
=0A=
      is the collection of information required to provide mobility=0A=
      management support for a given mobile node.=0A=
=0A=
=0A=
3.  Centralized versus distributed mobility management=0A=
=0A=
   Mobility management is needed because the IP address of a mobile node=0A=
   may change as the node moves.  Mobility management functions may be=0A=
   implemented at different layers of the protocol stack.  At the IP=0A=
   (network) layer, mobility management can be client-based or network-=0A=
   based.=0A=
=0A=
   An IP-layer mobility management protocol is typically based on the=0A=
   principle of distinguishing between a session identifier and a=0A=
   routing address and maintaining a mapping between the two.  In Mobile=0A=
   IP, the new IP address of the mobile node after the node has moved is=0A=
   the routing address, whereas the original IP address before the=0A=
   mobile node moves serves as the session identifier.  The location=0A=
   management (LM) information is kept by associating the routing=0A=
   address with the session identifier.  Packets addressed to the=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014                [Page 6]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
   session identifier will first route to the original network which re-=0A=
   directs them using the routing address to deliver to the session.=0A=
   Re-directing packets this way can result in long routes.  An existing=0A=
   optimization routes directly using the routing address of the host,=0A=
   and such is a host-based solution.=0A=
=0A=
   The next two subsections explain centralized and distributed mobility=0A=
   management functions in the network.=0A=
=0A=
3.1.  Centralized mobility management=0A=
=0A=
   In centralized mobility management, the location information in terms=0A=
   of a mapping between the session identifier and the routing address=0A=
   is kept at a single mobility anchor, and packets destined to the=0A=
   session identifier are routed via this anchor.  In other words, such=0A=
   mobility management systems are centralized in both the control plane=0A=
   and the data plane (mobile node IP traffic).=0A=
=0A=
   Many existing mobility management deployments make use of centralized=0A=
   mobility anchoring in a hierarchical network architecture, as shown=0A=
   in Figure 1.  Examples are the home agent (HA) and local mobility=0A=
   anchor (LMA) serving as the anchors for the mobile node (MN) and=0A=
   Mobile Access Gateway (MAG) in Mobile IPv6 [RFC6275] and in Proxy=0A=
   Mobile IPv6 [RFC5213] respectively.  Cellular networks such as the=0A=
   3GPP General Packet Radio System (GPRS) networks and 3GPP Evolved=0A=
   Packet System (EPS) networks employ centralized mobility management=0A=
   too.  In the 3GPP GPRS network, the Gateway GPRS Support Node (GGSN),=0A=
   Serving GPRS Support Node (SGSN) and Radio Network Controller (RNC)=0A=
   constitute a hierarchy of anchors.  In the 3GPP EPS network, the=0A=
   Packet Data Network Gateway (P-GW) and Serving Gateway (S-GW)=0A=
   constitute another hierarchy of anchors.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014                [Page 7]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
        3GPP GPRS                3GPP EPS                MIP/PMIP=0A=
         +------+                +------+                +------+=0A=
         | GGSN |                | P-GW |                |HA/LMA|=0A=
         +------+                +------+                +------+=0A=
            /\                      /\                      /\=0A=
           /  \                    /  \                    /  \=0A=
          /    \                  /    \                  /    \=0A=
         /      \                /      \                /      \=0A=
        /        \              /        \              /        \=0A=
       /          \            /          \            /          \=0A=
      /            \          /            \          /            \=0A=
  +------+      +------+  +------+      +------+  +------+      +------+=0A=
  | SGSN |      | SGSN |  | S-GW |      | S-GW |  |MN/MAG|      |MN/MAG|=0A=
  +------+      +------+  +------+      +------+  +------+      +------+=0A=
     /\            /\=0A=
    /  \          /  \=0A=
   /    \        /    \=0A=
+---+  +---+  +---+  +---+=0A=
|RNC|  |RNC|  |RNC|  |RNC|=0A=
+---+  +---+  +---+  +---+=0A=
=0A=
   Figure 1.  Centralized mobility management.=0A=
=0A=
3.2.  Distributed mobility management=0A=
=0A=
   Mobility management functions may also be distributed to multiple=0A=
   networks as shown in Figure 2, so that a mobile node in any of these=0A=
   networks may be served by a nearby function with appropriate=0A=
   mobility/routing management (RM) capability.=0A=
=0A=
=0A=
                    +------+  +------+  +------+  +------+=0A=
                    |  RM  |  |  RM  |  |  RM  |  |  RM  |=0A=
                    +------+  +------+  +------+  +------+=0A=
                                           |=0A=
                                         +----+=0A=
                                         | MN |=0A=
                                         +----+=0A=
=0A=
   Figure 2.  Distributed mobility management.=0A=
=0A=
   Mobility management may be partially or fully distributed=0A=
   [I-D.yokota-dmm-scenario].  In the former case only the data plane is=0A=
   distributed, implicitly assuming separation of data and control=0A=
   planes as described in [I-D.wakikawa-netext-pmip-cp-up-separation].=0A=
   Fully distributed mobility management implies that both the data=0A=
   plane and the control plane are distributed.  While mobility=0A=
   management can be distributed, it is not necessary for other=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014                [Page 8]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
   functions such as subscription management, subscription database, and=0A=
   network access authentication to be similarly distributed.=0A=
=0A=
   A distributed mobility management scheme for a flat mobile network of=0A=
   access nodes is proposed in [Paper-Distributed.Dynamic.Mobility].=0A=
   Its benefits over centralized mobility management have been shown=0A=
   through simulations [Paper-Distributed.Centralized.Mobility].=0A=
   Moreover, the (re)use and extension of existing protocols in the=0A=
   design of both fully distributed mobility management [Paper-=0A=
   Migrating.Home.Agents] [Paper-Distributed.Mobility.SAE] and partially=0A=
   distributed mobility management [Paper-Distributed.Mobility.PMIP]=0A=
   [Paper-Distributed.Mobility.MIP] have been reported in the=0A=
   literature.  Therefore, before designing new mobility management=0A=
   protocols for a future distributed architecture, it is recommended to=0A=
   first consider whether existing mobility management protocols can be=0A=
   extended.=0A=
=0A=
=0A=
4.  Problem Statement=0A=
=0A=
   The problems that can be addressed with DMM are summarized in the=0A=
   following:=0A=
=0A=
   PS1:  Non-optimal routes=0A=
=0A=
         Routing via a centralized anchor often results in non-optimal=0A=
         routes, thereby increasing the end-to-end delay.  The problem=0A=
         is manifested, for example, when accessing a nearby server or=0A=
         servers of a Content Delivery Network (CDN), or when receiving=0A=
         locally available IP multicast or sending IP multicast packets.=0A=
         (Existing route optimization is only a host-based solution.  On=0A=
         the other hand, localized routing with PMIPv6 [RFC6705]=0A=
         addresses only a part of the problem where both the MN and the=0A=
         correspondent node (CN) are attached to the same MAG, and it is=0A=
         not applicable when the CN does not behave like an MN.)=0A=
=0A=
   PS2:  Divergence from other evolutionary trends in network=0A=
         architectures such as distribution of content delivery.=0A=
=0A=
         Mobile networks have generally been evolving towards a flat=0A=
         network.  Centralized mobility management, which is non-optimal=0A=
         with a flat network architecture, does not support this=0A=
         evolution.=0A=
=0A=
   PS3:  Lack of scalability of centralized tunnel management and=0A=
         mobility context maintenance=0A=
=0A=
         Setting up tunnels through a central anchor and maintaining=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014                [Page 9]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
         mobility context for each MN usually requires more concentrated=0A=
         resources in a centralized design, thus reducing scalability.=0A=
         Distributing the tunnel maintenance function and the mobility=0A=
         context maintenance function among different network entities=0A=
         with proper signaling protocol design can avoid increasing the=0A=
         concentrated resources with an increasing number of MNs.=0A=
=0A=
   PS4:  Single point of failure and attack=0A=
=0A=
         Centralized anchoring designs may be more vulnerable to single=0A=
         points of failures and attacks than a distributed system.  The=0A=
         impact of a successful attack on a system with centralized=0A=
         mobility management can be far greater as well.=0A=
=0A=
   PS5:  Unnecessary mobility support to clients that do not need it=0A=
=0A=
         IP mobility support is usually provided to all MNs.  Yet it is=0A=
         not always required, and not every parameter of mobility=0A=
         context is always used.  For example, some applications or=0A=
         nodes do not need a stable IP address during a handover to=0A=
         maintain session continuity.  Sometimes, the entire application=0A=
         session runs while the MN does not change the point of=0A=
         attachment.  Besides, some sessions, e.g., SIP-based sessions,=0A=
         can handle mobility at the application layer and hence do not=0A=
         need IP mobility support; it is then unnecessary to provide IP=0A=
         mobility support for such sessions.=0A=
=0A=
   PS6:  Mobility signaling overhead with peer-to-peer communication=0A=
=0A=
         Wasting resources when mobility signaling (e.g., maintenance of=0A=
         the tunnel, keep alive signaling, etc.) is not turned off for=0A=
         peer-to-peer communication.=0A=
=0A=
   PS7:  Deployment with multiple mobility solutions=0A=
=0A=
         There are already many variants and extensions of MIP as well=0A=
         mobility solutions at other layers.  Deployment of new mobility=0A=
         management solutions can be challenging, and debugging=0A=
         difficult, when they co-exist with solutions already deployed=0A=
         in the field.=0A=
=0A=
   PS8:  Duplicate multicast traffic=0A=
=0A=
         IP multicast distribution over architectures using IP mobility=0A=
         solutions (e.g., [RFC6224]) may lead to convergence of=0A=
         duplicated multicast subscriptions towards the downstream=0A=
         tunnel entity (e.g., MAG in PMIPv6).  Concretely, when=0A=
         multicast subscription for individual mobile nodes is coupled=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014               [Page 10]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
         with mobility tunnels (e.g., PMIPv6 tunnel), duplicate=0A=
         multicast subscription(s) is prone to be received through=0A=
         different upstream paths.  This problem may also exist or be=0A=
         more severe in a distributed mobility environment.=0A=
=0A=
=0A=
5.  Requirements=0A=
=0A=
   After comparing distributed mobility management against centralized=0A=
   deployment in Section 3 and describing the problems in Section 4,=0A=
   this section identifies the following requirements:=0A=
=0A=
   REQ1:  Distributed processing=0A=
=0A=
          IP mobility, network access and routing solutions provided by=0A=
          DMM MUST enable distributed processing for mobility management=0A=
          so that traffic can avoid traversing single mobility anchor=0A=
          far from the optimal route.=0A=
=0A=
          Motivation: This requirement is motivated by current trends in=0A=
          network evolution: (a) it is cost- and resource-effective to=0A=
          cache contents, and the caching (e.g., CDN) servers are=0A=
          distributed so that each user in any location can be close to=0A=
          one of the servers; (b) the significantly larger number of=0A=
          mobile nodes and flows call for improved scalability; (c)=0A=
          single points of failure are avoided in a distributed system;=0A=
          (d) threats against centrally deployed anchors, e.g., home=0A=
          agent and local mobility anchor, are mitigated in a=0A=
          distributed system.=0A=
=0A=
   This requirement addresses the problems PS1, PS2, PS3, and PS4=0A=
   described in Section 4.=0A=
=0A=
   REQ2:  Bypassable network-layer mobility support=0A=
=0A=
          DMM solutions MUST enable network-layer mobility but it MUST=0A=
          be possible to not use it.  Mobility support is needed, for=0A=
          example, when a mobile host moves and an application cannot=0A=
          cope with a change in the IP address.  Mobility support is=0A=
          also needed when a mobile router changes its IP address as it=0A=
          moves together with a host and, in the presence of ingress=0A=
          filtering, an application in the host is interrupted.  However=0A=
          mobility support at the network-layer is not always needed; a=0A=
          mobile node can often be stationary, and mobility support can=0A=
          also be provided at other layers.  It is then not always=0A=
          necessary to maintain a stable IP address or prefix.=0A=
=0A=
          Motivation: The motivation of this requirement is to enable=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014               [Page 11]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
          more efficient routing and more efficient use of network=0A=
          resources by selecting an IP address or prefix according to=0A=
          whether mobility support is needed and by not maintaining=0A=
          context at the mobility anchor when there is no such need.=0A=
=0A=
   This requirement addresses the problems PS5 and PS6 described in=0A=
   Section 4.=0A=
=0A=
   REQ3:  IPv6 deployment=0A=
=0A=
          DMM solutions SHOULD target IPv6 as the primary deployment=0A=
          environment and SHOULD NOT be tailored specifically to support=0A=
          IPv4, in particular in situations where private IPv4 addresses=0A=
          and/or NATs are used.=0A=
=0A=
          Motivation: This requirement conforms to the general=0A=
          orientation of IETF work.  DMM deployment is foreseen in mid-=0A=
          to long-term horizon, when IPv6 is expected to be far more=0A=
          common than today.=0A=
=0A=
   This requirement avoids the unnecessarily complexity in solving the=0A=
   problems in Section 4 for IPv4, which will not be able to use some of=0A=
   the IPv6-specific features.=0A=
=0A=
   REQ4:  Existing mobility protocols=0A=
=0A=
          A DMM solution MUST first consider reusing and extending IETF-=0A=
          standardized protocols before specifying new protocols.=0A=
=0A=
          Motivation: Reuse of existing IETF work is more efficient and=0A=
          less error-prone.=0A=
=0A=
   This requirement attempts to avoid the need of new protocols=0A=
   development and therefore their potential problems of being time-=0A=
   consuming and error-prone.=0A=
=0A=
   REQ5:  Coexistence with deployed networks and hosts=0A=
=0A=
          The DMM solution may require loose, tight or no integration=0A=
          into existing mobility protocols and host IP stack.=0A=
          Regardless of the integration level, the DMM solution MUST be=0A=
          able to coexist with existing network deployments, end hosts=0A=
          and routers that may or may not implement existing mobility=0A=
          protocols.  Furthermore, a DMM solution SHOULD work across=0A=
          different networks, possibly operated as separate=0A=
          administrative domains, when allowed by the trust relationship=0A=
          between them.=0A=
=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014               [Page 12]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
          Motivation: (a) to preserve backwards compatibility so that=0A=
          existing networks and hosts are not affected and continue to=0A=
          function as usual, and (b) enable inter-domain operation if=0A=
          desired.=0A=
=0A=
   This requirement addresses the problem PS7 described in Section 4.=0A=
=0A=
   REQ6:  Security considerations=0A=
=0A=
          A DMM solution MUST NOT introduce new security risks, or=0A=
          amplify existing security risks, that cannot be mitigated by=0A=
          existing security mechanisms or protocols.=0A=
=0A=
          Motivation: Various attacks such as impersonation, denial of=0A=
          service, man-in-the-middle attacks, and so on, may be launched=0A=
          in a DMM deployment.  For instance, an illegitimate node may=0A=
          attempt to access a network providing DMM.  Another example is=0A=
          that a malicious node can forge a number of signaling messages=0A=
          thus redirecting traffic from its legitimate path.=0A=
          Consequently, the specific node is under a denial of service=0A=
          attack, whereas other nodes do not receive their traffic.=0A=
          Accordingly, security mechanisms/protocols providing access=0A=
          control, integrity, authentication, authorization,=0A=
          confidentiality, etc. can be used to protect the DMM entities=0A=
          as they are already used to protect against existing networks=0A=
          and existing mobility protocols defined in IETF.=0A=
=0A=
   This requirement prevents a DMM solution from introducing=0A=
   uncontrollable problems of potentially insecure mobility management=0A=
   protocols which make deployment infeasible because platforms=0A=
   conforming to the protocols are at risk for data loss and numerous=0A=
   other dangers, including financial harm to the users.=0A=
=0A=
   REQ7:  Multicast considerations=0A=
=0A=
          DMM SHOULD enable multicast solutions to be developed to avoid=0A=
          network inefficiency in multicast traffic delivery.=0A=
=0A=
          Motivation: Existing multicast deployment have been introduced=0A=
          after completing the design of the reference mobility=0A=
          protocol, often leading to network inefficiency and non-=0A=
          optimal routing for the multicast traffic.  Instead DMM should=0A=
          consider multicast early so that the multicast solutions can=0A=
          better consider efficiency nature in the multicast traffic=0A=
          delivery (such as duplicate multicast subscriptions towards=0A=
          the downstream tunnel entities).  The multicast solutions=0A=
          should then avoid restricting the management of all IP=0A=
          multicast traffic to a single host through a dedicated=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014               [Page 13]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
          (tunnel) interface on multicast-capable access routers.=0A=
=0A=
   This requirement addresses the problems PS1 and PS8 described in=0A=
   Section 4.=0A=
=0A=
=0A=
6.  Security Considerations=0A=
=0A=
   Please refer to the discussion under Security requirement in Section=0A=
   5.6.=0A=
=0A=
=0A=
7.  IANA Considerations=0A=
=0A=
   None=0A=
=0A=
=0A=
8.  Contributors=0A=
=0A=
   This requirements document is a joint effort among numerous=0A=
   participants working in a team.  In addition to the authors, each of=0A=
   the following has made very significant and important contributions=0A=
   to this work:=0A=
=0A=
   Charles E. Perkins=0A=
   Huawei Technologies=0A=
   Email: charliep@computer.org=0A=
=0A=
   Melia Telemaco=0A=
   Alcatel-Lucent Bell Labs=0A=
   Email: telemaco.melia@googlemail.com=0A=
=0A=
   Elena Demaria=0A=
   Telecom Italia=0A=
   via G. Reiss Romoli, 274, TORINO, 10148, Italy=0A=
   Email: elena.demaria@telecomitalia.it=0A=
=0A=
   Jong-Hyouk Lee=0A=
   Sangmyung University, Korea=0A=
   Email: jonghyouk@smu.ac.kr=0A=
=0A=
   Kostas Pentikousis=0A=
   EICT GmbH=0A=
   Email: k.pentikousis@eict.de=0A=
=0A=
   Tricci So=0A=
   ZTE=0A=
   Email: tso@zteusa.com=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014               [Page 14]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
   Carlos J. Bernardos=0A=
   Universidad Carlos III de Madrid=0A=
   Av.  Universidad, 30, Leganes, Madrid 28911, Spain=0A=
   Email: cjbc@it.uc3m.es=0A=
=0A=
   Peter McCann=0A=
   Huawei Technologies=0A=
   Email: Peter.McCann@huawei.com=0A=
=0A=
   Seok Joo Koh=0A=
   Kyungpook National University, Korea=0A=
   Email: sjkoh@knu.ac.kr=0A=
=0A=
   Wen Luo=0A=
   ZTE=0A=
   No.68, Zijinhua RD,Yuhuatai District, Nanjing, Jiangsu 210012, China=0A=
   Email: luo.wen@zte.com.cn=0A=
=0A=
   Sri Gundavelli=0A=
   Cisco=0A=
   sgundave@cisco.com=0A=
=0A=
   Hui Deng=0A=
   China Mobile=0A=
   Email: denghui@chinamobile.com=0A=
=0A=
   Marco Liebsch=0A=
   NEC Laboratories Europe=0A=
   Email: liebsch@neclab.eu=0A=
=0A=
   Carl Williams=0A=
   MCSR Labs=0A=
   Email: carlw@mcsr-labs.org=0A=
=0A=
   Seil Jeon=0A=
   Instituto de Telecomunicacoes, Aveiro=0A=
   Email: seiljeon@av.it.pt=0A=
=0A=
   Sergio Figueiredo=0A=
   Universidade de Aveiro=0A=
   Email: sfigueiredo@av.it.pt=0A=
=0A=
   Stig Venaas=0A=
   Email: stig@venaas.com=0A=
=0A=
   Luis Miguel Contreras Murillo=0A=
   Telefonica I+D=0A=
   Email: lmcm@tid.es=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014               [Page 15]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
   Juan Carlos Zuniga=0A=
   InterDigital=0A=
   Email: JuanCarlos.Zuniga@InterDigital.com=0A=
=0A=
   Alexandru Petrescu=0A=
   Email: alexandru.petrescu@gmail.com=0A=
=0A=
   Georgios Karagiannis=0A=
   University of Twente=0A=
   Email: g.karagiannis@utwente.nl=0A=
=0A=
   Julien Laganier=0A=
   Juniper=0A=
   Email: julien.ietf@gmail.com=0A=
=0A=
   Wassim Michel Haddad=0A=
   Ericsson=0A=
   Email: Wassim.Haddad@ericsson.com=0A=
=0A=
   Dirk von Hugo=0A=
   Deutsche Telekom Laboratories=0A=
   Email: Dirk.von-Hugo@telekom.de=0A=
=0A=
   Ahmad Muhanna=0A=
   Award Solutions=0A=
   Email: asmuhanna@yahoo.com=0A=
=0A=
   Byoung-Jo Kim=0A=
   ATT Labs=0A=
   Email: macsbug@research.att.com=0A=
=0A=
   Hassan Ali-Ahmad=0A=
   Orange=0A=
   Email: hassan.aliahmad@orange.com=0A=
=0A=
   Alper Yegin=0A=
   Samsung=0A=
   Email: alper.yegin@partner.samsung.com=0A=
=0A=
=0A=
9.  References=0A=
=0A=
9.1.  Normative References=0A=
=0A=
   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate=0A=
              Requirement Levels", BCP 14, RFC 2119, March 1997.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014               [Page 16]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
9.2.  Informative References=0A=
=0A=
   [I-D.bhandari-dhc-class-based-prefix]=0A=
              Bhandari, S., Halwasia, G., Gundavelli, S., Deng, H.,=0A=
              Thiebaut, L., Korhonen, J., and I. Farrer, "DHCPv6 class=0A=
              based prefix", draft-bhandari-dhc-class-based-prefix-05=0A=
              (work in progress), July 2013.=0A=
=0A=
   [I-D.korhonen-6man-prefix-properties]=0A=
              Korhonen, J., Patil, B., Gundavelli, S., Seite, P., and D.=0A=
              Liu, "IPv6 Prefix Properties",=0A=
              draft-korhonen-6man-prefix-properties-02 (work in=0A=
              progress), July 2013.=0A=
=0A=
   [I-D.wakikawa-netext-pmip-cp-up-separation]=0A=
              Wakikawa, R., Pazhyannur, R., and S. Gundavelli,=0A=
              "Separation of Control and User Plane for Proxy Mobile=0A=
              IPv6", draft-wakikawa-netext-pmip-cp-up-separation-00=0A=
              (work in progress), July 2013.=0A=
=0A=
   [I-D.yokota-dmm-scenario]=0A=
              Yokota, H., Seite, P., Demaria, E., and Z. Cao, "Use case=0A=
              scenarios for Distributed Mobility Management",=0A=
              draft-yokota-dmm-scenario-00 (work in progress),=0A=
              October 2010.=0A=
=0A=
   [Paper-Distributed.Centralized.Mobility]=0A=
              Bertin, P., Bonjour, S., and J-M. Bonnin, "A Distributed=0A=
              or Centralized Mobility",  Proceedings of Global=0A=
              Communications Conference  (GlobeCom), December 2009.=0A=
=0A=
   [Paper-Distributed.Dynamic.Mobility]=0A=
              Bertin, P., Bonjour, S., and J-M. Bonnin, "A Distributed=0A=
              Dynamic Mobility Management Scheme Designed for Flat IP=0A=
              Architectures",  Proceedings of 3rd International=0A=
              Conference on New Technologies, Mobility and Security=0A=
              (NTMS), 2008.=0A=
=0A=
   [Paper-Distributed.Mobility.MIP]=0A=
              Chan, H., "Distributed Mobility Management with Mobile=0A=
              IP",  Proceedings of IEEE International Communication=0A=
              Conference (ICC) Workshop on Telecommunications: from=0A=
              Research to Standards, June 2012.=0A=
=0A=
   [Paper-Distributed.Mobility.PMIP]=0A=
              Chan, H., "Proxy Mobile IP with Distributed Mobility=0A=
              Anchors",  Proceedings of GlobeCom Workshop  on Seamless=0A=
              Wireless Mobility, December 2010.=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014               [Page 17]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
   [Paper-Distributed.Mobility.Review]=0A=
              Chan, H., Yokota, H., Xie, J., Seite, P., and D. Liu,=0A=
              "Distributed and Dynamic Mobility Management in Mobile=0A=
              Internet: Current Approaches and Issues",  Journal of=0A=
              Communications, vol. 6, no. 1, pp. 4-15, February 2011.=0A=
=0A=
   [Paper-Distributed.Mobility.SAE]=0A=
              Fisher, M., Anderson, F., Kopsel, A., Schafer, G., and M.=0A=
              Schlager, "A Distributed IP Mobility Approach for 3G SAE",=0A=
               Proceedings of the 19th International Symposium on=0A=
              Personal, Indoor and Mobile Radio Communications (PIMRC),=0A=
              2008.=0A=
=0A=
   [Paper-Locating.User]=0A=
              Kirby, G., "Locating the User",  Communication=0A=
              International, 1995.=0A=
=0A=
   [Paper-Migrating.Home.Agents]=0A=
              Wakikawa, R., Valadon, G., and J. Murai, "Migrating Home=0A=
              Agents Towards Internet-scale Mobility Deployments",=0A=
               Proceedings of the ACM 2nd CoNEXT Conference  on Future=0A=
              Networking Technologies, December 2006.=0A=
=0A=
   [Paper-Mobile.Data.Offloading]=0A=
              Lee, K., Lee, J., Yi, Y., Rhee, I., and S. Chong, "Mobile=0A=
              Data Offloading: How Much Can WiFi Deliver?",  SIGCOMM=0A=
              2010, 2010.=0A=
=0A=
   [RFC3753]  Manner, J. and M. Kojo, "Mobility Related Terminology",=0A=
              RFC 3753, June 2004.=0A=
=0A=
   [RFC5213]  Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,=0A=
              and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.=0A=
=0A=
   [RFC5380]  Soliman, H., Castelluccia, C., ElMalki, K., and L.=0A=
              Bellier, "Hierarchical Mobile IPv6 (HMIPv6) Mobility=0A=
              Management", RFC 5380, October 2008.=0A=
=0A=
   [RFC5944]  Perkins, C., "IP Mobility Support for IPv4, Revised",=0A=
              RFC 5944, November 2010.=0A=
=0A=
   [RFC6224]  Schmidt, T., Waehlisch, M., and S. Krishnan, "Base=0A=
              Deployment for Multicast Listener Support in Proxy Mobile=0A=
              IPv6 (PMIPv6) Domains", RFC 6224, April 2011.=0A=
=0A=
   [RFC6275]  Perkins, C., Johnson, D., and J. Arkko, "Mobility Support=0A=
              in IPv6", RFC 6275, July 2011.=0A=
=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014               [Page 18]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
   [RFC6301]  Zhu, Z., Wakikawa, R., and L. Zhang, "A Survey of Mobility=0A=
              Support in the Internet", RFC 6301, July 2011.=0A=
=0A=
   [RFC6705]  Krishnan, S., Koodli, R., Loureiro, P., Wu, Q., and A.=0A=
              Dutta, "Localized Routing for Proxy Mobile IPv6",=0A=
              RFC 6705, September 2012.=0A=
=0A=
   [RFC6909]  Gundavelli, S., Zhou, X., Korhonen, J., Feige, G., and R.=0A=
              Koodli, "IPv4 Traffic Offload Selector Option for Proxy=0A=
              Mobile IPv6", RFC 6909, April 2013.=0A=
=0A=
   [TS.23.401]=0A=
              3GPP, "General Packet Radio Service (GPRS) enhancements=0A=
              for Evolved Universal Terrestrial Radio Access Network=0A=
              (E-UTRAN) access", 3GPP TR 23.401 10.10.0, March 2013.=0A=
=0A=
   [TS.29303]=0A=
              3GPP, "Domain Name System Procedures; Stage 3", 3GPP=0A=
              TR 23.303 11.2.0, September 2012.=0A=
=0A=
=0A=
Authors' Addresses=0A=
=0A=
   H Anthony Chan (editor)=0A=
   Huawei Technologies=0A=
   5340 Legacy Dr. Building 3, Plano, TX 75024, USA=0A=
   Email: h.a.chan@ieee.org=0A=
=0A=
=0A=
   Dapeng Liu=0A=
   China Mobile=0A=
   Unit2, 28 Xuanwumenxi Ave, Xuanwu District, Beijing 100053, China=0A=
   Email: liudapeng@chinamobile.com=0A=
=0A=
=0A=
   Pierrick Seite=0A=
   Orange=0A=
   4, rue du Clos Courtel, BP 91226, Cesson-Sevigne 35512, France=0A=
   Email: pierrick.seite@orange.com=0A=
=0A=
=0A=
   Hidetoshi Yokota=0A=
   KDDI Lab=0A=
   2-1-15 Ohara, Fujimino, Saitama, 356-8502 Japan=0A=
   Email: yokota@kddilabs.jp=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014               [Page 19]=0A=
=0C=0A=
Internet-Draft                  DMM-Reqs                   February 2014=0A=
=0A=
=0A=
   Jouni Korhonen=0A=
   Broadcom Communications=0A=
   Porkkalankatu 24, FIN-00180 Helsinki, Finland=0A=
   Email: jouni.nospam@gmail.com=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Chan (Ed.), et al.       Expires August 29, 2014               [Page 20]=0A=
=0C=0A=

------=_NextPart_000_00C1_01CF321C.084D7200
Content-Type: text/xml;
	name="draft-ietf-dmm-requirements-15.xml"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="draft-ietf-dmm-requirements-15.xml"

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC ''=20
  'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
]>

<?xml-stylesheet type=3D'text/xsl' href=3D'rfc2629.xslt'?>

<?rfc toc=3D"yes"?>
<?rfc symrefs=3D"yes"?>
<?rfc sortrefs=3D"yes"?>
<?rfc iprnotified=3D"no"?>
<?rfc strict=3D"yes"?>
<?rfc compact=3D"yes"?>=20
<?rfc subcompact=3D"no"?>


<rfc category=3D"info" ipr=3D"trust200902"=20
docName=3D"draft-ietf-dmm-requirements-15">

<front>
<title abbrev=3D"DMM-Reqs">
Requirements for Distributed Mobility Management
</title>

<author initials=3D"H" surname=3D"Chan (Ed.)"=20
fullname=3D"H Anthony Chan (editor)">
<organization>Huawei Technologies</organization>
<address>
<postal>
<street>5340 Legacy Dr. Building 3, Plano, TX 75024, USA</street>
<street>Email: h.a.chan@ieee.org</street>
</postal>
</address>
</author>

<author initials=3D"D" surname=3D"Liu"=20
fullname=3D"Dapeng Liu">
<organization>China Mobile</organization>
<address>
<postal>
<street>Unit2, 28 Xuanwumenxi Ave, Xuanwu District,
Beijing 100053, China</street>
<street>Email: liudapeng@chinamobile.com</street>
</postal>
</address>
</author>

<author initials=3D"P" surname=3D"Seite"=20
fullname=3D"Pierrick Seite">
<organization>Orange</organization>
<address>
<postal>
<street>4, rue du Clos Courtel, BP 91226,
Cesson-Sevigne 35512, France</street>
<street>Email: pierrick.seite@orange.com</street>
</postal>
</address>
</author>

<author initials=3D"H" surname=3D"Yokota"=20
fullname=3D"Hidetoshi Yokota">
<organization>KDDI Lab</organization>
<address>
<postal>
<street>2-1-15 Ohara, Fujimino, Saitama, 356-8502 Japan</street>
<street>Email: yokota@kddilabs.jp</street>
</postal>
</address>
</author>

<author initials=3D"J" surname=3D"Korhonen"=20
fullname=3D"Jouni Korhonen">
<organization>Broadcom Communications</organization>
<address>
<postal>
<street>Porkkalankatu 24, FIN-00180 Helsinki, Finland</street>
<street>Email: jouni.nospam@gmail.com</street>


</postal>
</address>
</author>

<date month=3D"February" year=3D"2014"></date>
<area></area>
<workgroup></workgroup>

<abstract>
<t>
This document defines the requirements=20
for Distributed Mobility Management (DMM)
at the network layer.
The hierarchical structure=20
in traditional wireless networks=20
has led primarily to centrally deployed mobility anchors.=20
As some wireless networks are evolving away from the hierarchical =
structure,
it can be useful have a distributed model for mobility management=20
in which traffic does not need to traverse
centrally deployed mobility anchors far from the optimal route.=20
</t>
</abstract>

<note title=3D"Requirements Language">
<t>The key words &quot;MUST&quot;, &quot;MUST NOT&quot;,
&quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,
&quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;,
&quot;MAY&quot;, and &quot;OPTIONAL&quot; in this document are to be
interpreted as described in RFC 2119 <xref target=3D"RFC2119">RFC =
2119</xref>.
</t>
</note>

</front>

<middle>

<section anchor=3D"intro" title=3D"Introduction">

<t>
In the past decade a fair number of=20
network-layer mobility protocols=20
have been standardized
 <xref target=3D"RFC6275"/>
 <xref target=3D"RFC5944"/>
 <xref target=3D"RFC5380"/>
 <xref target=3D"RFC6301"/>
 <xref target=3D"RFC5213"/>.
Although the protocols differ=20
in terms of functions and associated message formats,=20
they all employ a mobility anchor
to allow a mobile node to remain reachable=20
after it has moved to a different network.=20
The anchor point, among other tasks,=20
ensures connectivity=20
by forwarding packets=20
destined to, or sent from, the mobile node.=20
It is a centrally deployed mobility anchor
in the sense that the deployed architectures today=20
have a small number of these anchors=20
and the traffic of millions of mobile nodes=20
in an operator network are typically managed=20
by the same anchor.
</t>

<t>
Distributed mobility management (DMM) is an alternative
to the above centralized deployment.
The background behind the interests to study DMM=20
are primarily in the following.=20
</t>

<t>
<list style=3D'format (%d)'>

<t>
Mobile users are, more than ever,=20
consuming Internet content=20
including that of local Content Delivery Networks (CDNs)
which had not taken mobility service into account before.=20
Such traffic imposes new requirements=20
on mobile core networks for data traffic delivery.=20
To prevent exceeding the available core network capacity,=20
service providers need to implement new strategies=20
such as selective IPv4 traffic offload=20
(e.g.,=20
 <xref target=3D"RFC6909"/>,
Third Generation Partnership Project (3GPP)
work items Local IP Access (LIPA)=20
and Selected IP Traffic Offload
(SIPTO)=20
[TS.23.401])
through alternative access networks
such as Wireless Local Area Network (WLAN)
[Paper-Mobile.Data.Offloading].=20
In addition, a gateway selection mechanism
takes the user proximity into account
within the EPC Evolved Packet Core (EPC) [TS.29303].=20
Yet these mechanisms were not pursued in the past
owing to charging and billing=20
which require solutions beyond the mobility protocol.
Consequently, assigning a gateway anchor node
from a visited network in roaming scenario
has until recently been done and are limited
to voice services only.=20

<vspace blankLines=3D"1" />

Both traffic offloading and CDN mechanisms=20
could benefit from the development of mobile architectures=20
with fewer levels of routing hierarchy=20
introduced into the data path=20
by the mobility management system.=20
This trend towards so-called "flat networks"=20
works best for direct communications among peers=20
in the same geographical area.=20
Distributed mobility management=20
in a truly flat mobile architecture
would anchor the traffic=20
closer to the point of attachment of the user.
</t>

<t>
Today's mobile networks present=20
service providers with new challenges.=20
Mobility patterns indicate that=20
mobile nodes often
remain attached to the same point of attachment
for considerable periods of time
[Paper-Locating.User].
Specific IP mobility management support=20
is not required for applications=20
that launch and complete their sessions=20
while the mobile node is connected=20
to the same point of attachment.=20
However, currently,
IP mobility support is designed for always-on operation,
maintaining all parameters of the context=20
for each mobile subscriber=20
for as long as they are connected to the network.=20
This can result in a waste of resources=20
and unnecessary costs for the service provider.=20
Infrequent node mobility=20
coupled with application intelligence
suggest that mobility support could be provided selectively
such as in=20
[I-D.bhandari-dhc-class-based-prefix]
and=20
[I-D.korhonen-6man-prefix-properties],=20
thus reducing the amount of context maintained=20
in the network.
</t>

</list>
</t>


<t>
DMM may distribute the mobility anchors=20
in the data-plane
towards a more flat network
such that the mobility anchors are positioned=20
closer to the user;=20
ideally,=20
mobility agents could be collocated=20
with the first-hop router.

Facilitated by the distribution of mobility anchors,
it may be possible to selectively use or not use
mobility protocol support
depending on whether such support
is needed or not.
It can thus reduce the amount of state information=20
that must be maintained=20
in various mobility agents of the mobile network.=20
It can then avoid the unnecessary establishment of mechanisms
to forward traffic from an old to a new mobility anchor.
</t>

<t>
This document compares distributed mobility management=20
with centralized mobility management in Section 3.=20
The problems that can be addressed with DMM=20
are summarized in Section 4.=20
The mandatory requirements as well as the optional requirements=20
for network-layer distributed mobility management
are given in Section 5.=20
Finally, security considerations are discussed in Section 6.
</t>
<t>
The problem statement and the use cases
[I-D.yokota-dmm-scenario]
can be found in=20
[Paper-Distributed.Mobility.Review].
</t>

</section>

<section title=3D"Conventions used in this document">

<section title=3D"Terminology">
<t>All the general mobility-related terms and their acronyms used in =
this document are to be interpreted=20
as defined in the Mobile IPv6 base specification
 <xref target=3D"RFC6275"/>,=20
in the Proxy mobile IPv6 specification=20
 <xref target=3D"RFC5213"/>,
and in Mobility Related Terminology=20
 <xref target=3D"RFC3753"/>.=20
These terms include the following:
mobile node (MN), correspondent node (CN),=20
and home agent (HA) as per=20
 <xref target=3D"RFC6275"/>;=20
local mobility anchor (LMA)=20
and mobile access gateway (MAG) as per=20
 <xref target=3D"RFC5213"/>,
and context as per
 <xref target=3D"RFC3753"/>.
</t>

<t>
In addition, this draft introduces the following terms.=20
</t>

<t>
<list style=3D'hanging'>

<t hangText=3D'Centrally deployed mobility anchors'>
<vspace blankLines=3D"1" />
refer to the mobility management deployments
in which there are very few mobility anchors
and the traffic of millions of mobile nodes
in an operator network
are managed by the same anchor.
</t>

<t hangText=3D'Centralized mobility management'>
<vspace blankLines=3D"1" />
makes use of centrally deployed mobility anchors.
</t>

<t hangText=3D'Distributed mobility management'>
<vspace blankLines=3D"1" />
is not centralized so that
traffic does not need to traverse=20
centrally deployed mobility anchors
far from the optimal route.
</t>

<t hangText=3D'Flat mobile network'>
<vspace blankLines=3D"1" />
has few levels of routing hierarchy
introduced into the data path
by the mobility management system.
</t>

<t hangText=3D'Mobility context'>
<vspace blankLines=3D"1" />
is the collection of information=20
required to provide mobility management support=20
for a given mobile node.
</t>

</list>
</t>

</section>

</section>


<section=20
title=3D"Centralized versus distributed mobility management">
<t>
Mobility management is needed because
the IP address of a mobile node
may change as the node moves.=20
Mobility management functions=20
may be implemented at different layers=20
of the protocol stack.=20
At the IP (network) layer,=20
mobility management can be client-based or network-based.=20
</t>

<t>
An IP-layer mobility management protocol
is typically based on the principle=20
of distinguishing between a session identifier and a routing address
and maintaining a mapping between the two.=20
In Mobile IP,=20
the new IP address of the mobile node=20
after the node has moved=20
is the routing address,
whereas the original IP address=20
before the mobile node moves
serves as the session identifier.
The location management (LM) information
is kept by associating the routing address=20
with the session identifier.=20
Packets addressed to the session identifier
will first route to the original network
which re-directs them using the routing address
to deliver to the session.=20
Re-directing packets this way can result in long routes.
An existing optimization routes directly
using the routing address of the host,
and such is a host-based solution.=20
</t>

<t>
The next two subsections explain centralized and distributed
mobility management functions in the network.
</t>

<section title=3D"Centralized mobility management">
<t>
In centralized mobility management,=20
the location information in terms of a mapping
between the session identifier=20
and the routing address=20
is kept at a single mobility anchor,=20
and packets destined to the session identifier=20
are routed via this anchor.=20
In other words,=20
such mobility management systems are centralized=20
in both the control plane and the data plane
(mobile node IP traffic).
</t>

<t>
Many existing mobility management deployments=20
make use of centralized mobility anchoring=20
in a hierarchical network architecture,=20
as shown in Figure 1.=20
Examples are the home agent (HA)=20
and local mobility anchor (LMA)=20
serving as the anchors for the mobile node (MN)
and Mobile Access Gateway (MAG)
in Mobile IPv6=20
<xref target=3D"RFC6275"/>=20
and=20
in Proxy Mobile IPv6=20
<xref target=3D"RFC5213"/>
respectively.=20
Cellular networks=20
such as the 3GPP=20
General Packet Radio System (GPRS) networks =20
and 3GPP Evolved Packet System (EPS) networks=20
employ centralized mobility management too.=20
In the 3GPP GPRS network,=20
the Gateway GPRS Support Node (GGSN),=20
Serving GPRS Support Node (SGSN)=20
and Radio Network Controller (RNC)
constitute a hierarchy of anchors.
In the 3GPP EPS network,=20
the Packet Data Network Gateway (P-GW)=20
and Serving Gateway (S-GW)=20
constitute another hierarchy of anchors.
</t>

      <figure>
        <preamble></preamble>
        <artwork><![CDATA[
        3GPP GPRS                3GPP EPS                MIP/PMIP
         +------+                +------+                +------+     =20
         | GGSN |                | P-GW |                |HA/LMA|     =20
         +------+                +------+                +------+     =20
            /\                      /\                      /\
           /  \                    /  \                    /  \
          /    \                  /    \                  /    \=20
         /      \                /      \                /      \
        /        \              /        \              /        \
       /          \            /          \            /          \
      /            \          /            \          /            \
  +------+      +------+  +------+      +------+  +------+      +------+
  | SGSN |      | SGSN |  | S-GW |      | S-GW |  |MN/MAG|      |MN/MAG|
  +------+      +------+  +------+      +------+  +------+      +------+
     /\            /\
    /  \          /  \
   /    \        /    \
+---+  +---+  +---+  +---+
|RNC|  |RNC|  |RNC|  |RNC|
+---+  +---+  +---+  +---+
      	]]></artwork>
        <postamble></postamble>
      </figure>

<t>Figure 1. Centralized mobility management.
</t>
</section>

<section title=3D"Distributed mobility management">
<t>Mobility management functions may also be distributed=20
to multiple networks
as shown in Figure 2,=20
so that a mobile node in any of these networks
may be served by a nearby function=20
with appropriate mobility/routing management (RM) capability.=20
</t>

      <figure>
        <preamble></preamble>
        <artwork><![CDATA[
                 +------+  +------+  +------+  +------+   =20
                 |  RM  |  |  RM  |  |  RM  |  |  RM  |   =20
                 +------+  +------+  +------+  +------+   =20
                                        |         =20
                                      +----+         =20
                                      | MN |         =20
                                      +----+         =20
      	]]></artwork>
        <postamble></postamble>
      </figure>

<t>Figure 2. Distributed mobility management.
</t>
<t>
Mobility management may be partially or fully distributed
[I-D.yokota-dmm-scenario].
In the former case only the data plane is distributed,
implicitly assuming separation of data and control planes
as described in=20
[I-D.wakikawa-netext-pmip-cp-up-separation].
Fully distributed mobility management implies that
both the data plane and the control plane are distributed.
While mobility management can be distributed,
it is not necessary=20
for other functions
such as subscription management,=20
subscription database, and network access authentication to be similarly =
distributed.
</t>

<t>
A distributed mobility management scheme=20
for a flat mobile network
of access nodes is proposed in=20
[Paper-Distributed.Dynamic.Mobility].=20
Its benefits=20
over centralized mobility management=20
have been shown through simulations =20
[Paper-Distributed.Centralized.Mobility].
Moreover,
the (re)use and extension of existing protocols=20
in the design of both fully distributed mobility management
[Paper-Migrating.Home.Agents]=20
[Paper-Distributed.Mobility.SAE]
and partially distributed mobility management
[Paper-Distributed.Mobility.PMIP]
[Paper-Distributed.Mobility.MIP]
have been reported in the literature.=20
Therefore,
before designing new mobility management protocols=20
for a future distributed architecture,=20
it is recommended to first consider=20
whether existing mobility management protocols=20
can be extended.=20

</t>

</section>

</section>


<section=20
title=3D"Problem Statement">
<t>
The problems that can be addressed with DMM are summarized in the =
following:
</t>

<t>
<list style=3D'format PS%d:' counter=3D"PS_count">

<!-- PS1 -->
<t>
Non-optimal routes
<vspace blankLines=3D"1" />
Routing via a centralized anchor=20
often results in non-optimal routes,
thereby increasing the end-to-end delay.
The problem is manifested, for example,
when accessing a nearby server or servers=20
of a Content Delivery Network (CDN),
or when receiving locally available IP multicast=20
or sending IP multicast packets.
(Existing route optimization=20
is only a host-based solution.=20
On the other hand,=20
localized routing with PMIPv6=20
 <xref target=3D"RFC6705"/>
addresses only a part of the problem=20
where both the MN and the correspondent node (CN)=20
are attached to the same MAG,=20
and it is not applicable=20
when the CN does not behave like an MN.)
</t>

<!-- PS2 -->
<t>
Divergence from other evolutionary trends in network architectures
such as distribution of content delivery.
<vspace blankLines=3D"1" />
Mobile networks have generally been evolving towards a flat network.=20
Centralized mobility management,
which is non-optimal with a flat network architecture,
does not support this evolution.
</t>

<!-- PS3 -->
<t>
Lack of scalability of centralized tunnel management=20
and mobility context maintenance
<vspace blankLines=3D"1" />
Setting up tunnels through a central anchor
and maintaining mobility context=20
for each MN=20
usually requires more concentrated resources
in a centralized design,
thus reducing scalability.=20
Distributing the tunnel maintenance function=20
and the mobility context maintenance function=20
among different network entities=20
with proper signaling protocol design
can avoid increasing the concentrated resources
with an increasing number of MNs.
</t>

<!-- PS4 -->
<t>
Single point of failure and attack
<vspace blankLines=3D"1" />
Centralized anchoring designs=20
may be more vulnerable=20
to single points of failures and attacks
than a distributed system.=20
The impact of a successful attack=20
on a system with centralized mobility management=20
can be far greater as well.
</t>

<!-- PS5 -->
<t>
Unnecessary mobility support=20
to clients that do not need it
<vspace blankLines=3D"1" />
IP mobility support is usually provided to all MNs.
Yet it is not always required,
and not every parameter of mobility context is always used.=20
For example,=20
some applications or nodes do not need a stable IP address=20
during a handover to maintain session continuity.=20
Sometimes, the entire application session runs=20
while the MN does not change the point of attachment.=20
Besides, some sessions, e.g., SIP-based sessions,=20
can handle mobility at the application layer=20
and hence do not need IP mobility support;=20
it is then unnecessary
to provide IP mobility support for such sessions.
</t>

<!-- PS6 -->
<t>
Mobility signaling overhead=20
with peer-to-peer communication
<vspace blankLines=3D"1" />
Wasting resources when mobility signaling=20
(e.g., maintenance of the tunnel, keep alive signaling, etc.)=20
is not turned off for peer-to-peer communication.=20
</t>

<!-- PS7 -->
<t>
Deployment with multiple mobility solutions
<vspace blankLines=3D"1" />
There are already many variants and extensions of MIP
as well mobility solutions at other layers.=20
Deployment of new mobility management solutions can be challenging,=20
and debugging difficult,=20
when they co-exist with solutions already deployed in the field.
</t>

<!-- PS8 -->
<t>
Duplicate multicast traffic
<vspace blankLines=3D"1" />
IP multicast distribution over architectures=20
using IP mobility solutions=20
(e.g., <xref target=3D"RFC6224"/>)=20
may lead to convergence=20
of duplicated multicast subscriptions=20
towards the downstream tunnel entity=20
(e.g., MAG in PMIPv6).
Concretely,=20
when multicast subscription=20
for individual mobile nodes=20
is coupled with mobility tunnels
(e.g., PMIPv6 tunnel),=20
duplicate multicast subscription(s)=20
is prone to be received=20
through different upstream paths.=20
This problem may also exist=20
or be more severe=20
in a distributed mobility environment.=20
</t>
</list>
</t>

</section>


<section title=3D"Requirements">
<t>
After comparing distributed mobility management
against centralized deployment in Section 3
and describing the problems in Section 4,
this section identifies=20
the following requirements:
</t>

<!-- REQ1 -->
<t>
<list style=3D'format REQ%d:' counter=3D"R_count">
<t>
Distributed processing
<vspace blankLines=3D"1" />
IP mobility, network access and routing solutions
provided by DMM=20
MUST enable distributed processing=20
for mobility management=20
so that traffic=20
can avoid traversing single mobility anchor=20
far from the optimal route.
<vspace blankLines=3D"1" />
Motivation:=20
This requirement is motivated by=20
current trends in network evolution:
(a) it is cost- and resource-effective=20
to cache contents,=20
and the caching (e.g., CDN) servers are distributed
so that each user in any location
can be close to one of the servers;=20
(b) the significantly larger number of mobile nodes
and flows
call for improved scalability;=20
(c) single points of failure are avoided
in a distributed system;=20
(d) threats against centrally deployed anchors,
e.g., home agent and local mobility anchor,
are mitigated in a distributed system.=20
</t>
</list>
</t>

<t>
This requirement addresses the problems=20
PS1, PS2, PS3, and PS4 described in Section 4.
</t>

<!-- REQ2 -->
<t>
<list style=3D'format REQ%d:' counter=3D"R_count">
<t>
Bypassable network-layer mobility support
<vspace blankLines=3D"1" />
DMM solutions MUST enable network-layer mobility=20
but it MUST be possible to not use it.=20

Mobility support is needed, for example,=20
when a mobile host moves and an application=20
cannot cope with a change in the IP address.

Mobility support is also needed=20
when a mobile router changes its IP address
as it moves together with a host
and, in the presence of ingress filtering,
an application in the host is interrupted.

However mobility support at the network-layer=20
is not always needed;
a mobile node can often be stationary,
and mobility support can also be provided=20
at other layers.
It is then not always necessary to maintain a
stable IP address or prefix.
<vspace blankLines=3D"1" />
Motivation:
The motivation of this requirement is to
enable more efficient routing=20
and more efficient use of network resources=20
by selecting an IP address or prefix
according to
whether mobility support is needed
and by not maintaining context=20
at the mobility anchor=20
when there is no such need.
</t>
</list>
</t>

<t>
This requirement addresses the problems=20
PS5 and PS6 described in Section 4.
</t>

<!-- REQ3 -->
<t>
<list style=3D'format REQ%d:' counter=3D"R_count">
<t>
IPv6 deployment
<vspace blankLines=3D"1" />
DMM solutions SHOULD target IPv6=20
as the primary deployment environment
and SHOULD NOT be tailored specifically to support IPv4,=20
in particular in situations=20
where private IPv4 addresses and/or NATs are used.
<vspace blankLines=3D"1" />
Motivation:
This requirement conforms
to the general orientation of IETF work.=20
DMM deployment is foreseen=20
in mid- to long-term horizon,
when IPv6 is expected=20
to be far more common than today.
</t>
</list>
</t>

<t>
This requirement avoids the unnecessarily complexity=20
in solving the problems in Section 4 for IPv4,=20
which will not be able to use=20
some of the IPv6-specific features.
</t>


<!-- REQ4 -->
<t>
<list style=3D'format REQ%d:' counter=3D"R_count">
<t>
Existing mobility protocols
<vspace blankLines=3D"1" />
A DMM solution MUST=20
first consider reusing and extending=20
IETF-standardized protocols=20
before specifying new protocols.
<vspace blankLines=3D"1" />
Motivation:
Reuse of existing IETF work
is more efficient and less error-prone.
</t>
</list>

</t>

<t>
This requirement attempts to avoid the need of
new protocols development
and therefore their potential problems=20
of being time-consuming and error-prone.
</t>


<!-- REQ5 -->
<t>
<list style=3D'format REQ%d:' counter=3D"R_count">
<t>
Coexistence with deployed networks and hosts
<vspace blankLines=3D"1" />
The DMM solution may require loose, tight
or no integration into existing mobility protocols
and host IP stack.
Regardless of the integration level,
the DMM solution MUST
be able to coexist=20
with existing network deployments,
end hosts and routers
that may or may not=20
implement existing mobility protocols.
Furthermore,
a DMM solution SHOULD work across different networks,
possibly operated as separate administrative domains,=20
when allowed by the trust relationship
between them.=20
<vspace blankLines=3D"1" />
Motivation:=20
(a) to preserve backwards compatibility=20
so that existing networks and hosts=20
are not affected=20
and continue to function as usual,
and=20
(b) enable inter-domain operation if desired.
</t>
</list>
</t>

<t>
This requirement addresses=20
the problem PS7 described in Section 4.
</t>


<!-- REQ6 -->
<t>
<list style=3D'format REQ%d:' counter=3D"R_count">
<t>
Security considerations
<vspace blankLines=3D"1" />
A DMM solution MUST NOT introduce new security risks,=20
or amplify existing security risks,
that cannot be mitigated by=20
existing security mechanisms or protocols.=20
<vspace blankLines=3D"1" />
Motivation:
Various attacks such as impersonation, denial of service,=20
man-in-the-middle attacks, and so on,=20
may be launched in a DMM deployment.=20
For instance,=20
an illegitimate node=20
may attempt to access a network providing DMM.=20
Another example is that=20
a malicious node can forge a number of signaling messages=20
thus redirecting traffic from its legitimate path.
Consequently,=20
the specific node is under a denial of service attack,=20
whereas other nodes do not receive their traffic.=20
Accordingly,=20
security mechanisms/protocols providing access control,=20
integrity, authentication, authorization,=20
confidentiality, etc.=20
can be used to protect the DMM entities=20
as they are already used to protect=20
against existing networks=20
and existing mobility protocols defined in IETF.=20
</t>
</list>
</t>

<t>
This requirement prevents a DMM solution=20
from introducing uncontrollable problems=20
of potentially insecure mobility management protocols=20
which make deployment infeasible=20
because platforms conforming to the protocols=20
are at risk for data loss and numerous other dangers,=20
including financial harm to the users.=20
</t>


<!-- REQ7 -->
<t>
<list style=3D'format REQ%d:' counter=3D"R_count">
<t>
Multicast considerations
<vspace blankLines=3D"1" />
DMM SHOULD enable multicast solutions
to be developed to avoid network inefficiency
in multicast traffic delivery.
<vspace blankLines=3D"1" />
Motivation:
Existing multicast deployment have been introduced=20
after completing the design of the reference mobility protocol,=20
often leading to network inefficiency and non-optimal routing
for the multicast traffic.
Instead DMM should consider multicast early
so that the multicast solutions
can better consider efficiency nature
in the multicast traffic delivery
(such as duplicate multicast subscriptions
towards the downstream tunnel entities).=20
The multicast solutions should then=20
avoid restricting the management of all IP multicast traffic=20
to a single host through a dedicated (tunnel) interface=20
on multicast-capable access routers.=20
</t>
</list>
</t>

<t>
This requirement addresses the problems=20
PS1 and PS8 described in Section 4.
</t>


</section>


<section anchor=3D"security" title=3D"Security Considerations">
<t>
Please refer to the discussion=20
under Security requirement in Section 5.6.=20
</t>
</section>


<section title=3D"IANA Considerations">
<t>None</t>
</section>


<section title=3D"Contributors">
<t>This requirements document is a joint effort=20
among numerous participants working in a team.
In addition to the authors,
each of the following=20
has made very significant and important contributions to this work:
</t>

<t>
Charles E. Perkins
<vspace blankLines=3D"0" />
Huawei Technologies
<vspace blankLines=3D"0" />
Email: charliep@computer.org</t>

<t>Melia Telemaco
<vspace blankLines=3D"0" />
Alcatel-Lucent Bell Labs
<vspace blankLines=3D"0" />
Email: telemaco.melia@googlemail.com</t>

<t>Elena Demaria
<vspace blankLines=3D"0" />
Telecom Italia
<vspace blankLines=3D"0" />
via G. Reiss Romoli, 274, TORINO, 10148, Italy
<vspace blankLines=3D"0" />
Email: elena.demaria@telecomitalia.it</t>

<t>Jong-Hyouk Lee
<vspace blankLines=3D"0" />
Sangmyung University, Korea
<vspace blankLines=3D"0" />
Email: jonghyouk@smu.ac.kr</t>

<t>Kostas Pentikousis
<vspace blankLines=3D"0" />
EICT GmbH
<vspace blankLines=3D"0" />
Email: k.pentikousis@eict.de</t>

<t>Tricci So
<vspace blankLines=3D"0" />
ZTE
<vspace blankLines=3D"0" />
Email: tso@zteusa.com</t>

<t>Carlos J. Bernardos
<vspace blankLines=3D"0" />
Universidad Carlos III de Madrid
<vspace blankLines=3D"0" />
Av. Universidad, 30, Leganes, Madrid 28911, Spain
<vspace blankLines=3D"0" />
Email: cjbc@it.uc3m.es</t>

<t>Peter McCann
<vspace blankLines=3D"0" />
Huawei Technologies
<vspace blankLines=3D"0" />
Email: Peter.McCann@huawei.com</t>

<t>Seok Joo Koh
<vspace blankLines=3D"0" />
Kyungpook National University, Korea
<vspace blankLines=3D"0" />
Email: sjkoh@knu.ac.kr</t>

<t>Wen Luo
<vspace blankLines=3D"0" />
ZTE
<vspace blankLines=3D"0" />
No.68, Zijinhua RD,Yuhuatai District, Nanjing, Jiangsu 210012, China
<vspace blankLines=3D"0" />
Email: luo.wen@zte.com.cn</t>

<t>Sri Gundavelli
<vspace blankLines=3D"0" />
Cisco
<vspace blankLines=3D"0" />
sgundave@cisco.com</t>

<t>Hui Deng
<vspace blankLines=3D"0" />
China Mobile
<vspace blankLines=3D"0" />
Email: denghui@chinamobile.com</t>

<t>Marco Liebsch
<vspace blankLines=3D"0" />
NEC Laboratories Europe
<vspace blankLines=3D"0" />
Email: liebsch@neclab.eu</t>

<t>Carl Williams
<vspace blankLines=3D"0" />
MCSR Labs
<vspace blankLines=3D"0" />
Email: carlw@mcsr-labs.org</t>

<t>Seil Jeon
<vspace blankLines=3D"0" />
Instituto de Telecomunicacoes, Aveiro
<vspace blankLines=3D"0" />
Email: seiljeon@av.it.pt</t>

<t>S=E9rgio Figueiredo
<vspace blankLines=3D"0" />
Universidade de Aveiro
<vspace blankLines=3D"0" />
Email: sfigueiredo@av.it.pt</t>

<t>Stig Venaas
<vspace blankLines=3D"0" />
Email: stig@venaas.com</t>

<t>Luis Miguel Contreras Murillo
<vspace blankLines=3D"0" />
Telefonica I+D
<vspace blankLines=3D"0" />
Email: lmcm@tid.es</t>

<t>Juan Carlos Zuniga
<vspace blankLines=3D"0" />
InterDigital
<vspace blankLines=3D"0" />
Email: JuanCarlos.Zuniga@InterDigital.com</t>

<t>Alexandru Petrescu
<vspace blankLines=3D"0" />
Email: alexandru.petrescu@gmail.com</t>

<t>Georgios Karagiannis
<vspace blankLines=3D"0" />
University of Twente
<vspace blankLines=3D"0" />
Email: g.karagiannis@utwente.nl</t>

<t>Julien Laganier
<vspace blankLines=3D"0" />
Juniper
<vspace blankLines=3D"0" />
Email: julien.ietf@gmail.com</t>

<t>Wassim Michel Haddad
<vspace blankLines=3D"0" />
Ericsson
<vspace blankLines=3D"0" />
Email: Wassim.Haddad@ericsson.com</t>

<t>Dirk von Hugo
<vspace blankLines=3D"0" />
Deutsche Telekom Laboratories
<vspace blankLines=3D"0" />
Email: Dirk.von-Hugo@telekom.de</t>

<t>Ahmad Muhanna
<vspace blankLines=3D"0" />
Award Solutions
<vspace blankLines=3D"0" />
Email: asmuhanna@yahoo.com</t>

<t>Byoung-Jo Kim
<vspace blankLines=3D"0" />
ATT Labs
<vspace blankLines=3D"0" />
Email: macsbug@research.att.com</t>

<t>Hassan Ali-Ahmad
<vspace blankLines=3D"0" />
Orange
<vspace blankLines=3D"0" />
Email: hassan.aliahmad@orange.com</t>

<t>Alper Yegin
<vspace blankLines=3D"0" />
Samsung
<vspace blankLines=3D"0" />
Email: alper.yegin@partner.samsung.com</t>

</section>

</middle>


<back>

<references title=3D"Normative References">
  &rfc2119;
</references>

<references title=3D"Informative References">
<?rfc include=3D"reference.RFC.6275" ?>
<?rfc include=3D"reference.RFC.5213" ?>
<?rfc include=3D"reference.RFC.5380" ?>
<?rfc include=3D"reference.RFC.5944" ?>
<?rfc include=3D"reference.RFC.6301" ?>
<?rfc include=3D"reference.RFC.3753" ?>
<?rfc include=3D"reference.RFC.6909" ?>
<?rfc include=3D"reference.RFC.6705" ?>
<?rfc include=3D"reference.RFC.6224" ?>

<reference anchor=3D"I-D.yokota-dmm-scenario">
<front>
<title>Use case scenarios for Distributed Mobility Management</title>=20
<author initials=3D"H" surname=3D"Yokota"=20
fullname=3D"Hidetoshi Yokota">
  <organization />=20
</author>
<author initials=3D"P" surname=3D"Seite"=20
fullname=3D"Pierrick Seite">
  <organization />=20
</author>
<author initials=3D"E" surname=3D"Demaria"=20
fullname=3D"Elena Demaria">
  <organization />=20
</author>
<author initials=3D"Z" surname=3D"Cao" fullname=3D"Zhen Cao">
  <organization />=20
</author>
<date day=3D"18" month=3D"October" year=3D"2010" />=20
</front>
<seriesInfo name=3D"Internet-Draft"=20
 value=3D"draft-yokota-dmm-scenario-00" />=20
<format type=3D"TXT" target=3D
 =
"http://www.ietf.org/internet-drafts/draft-yokota-dmm-scenario-00.txt"/> =

</reference>

<reference anchor=3D"I-D.wakikawa-netext-pmip-cp-up-separation">
<front>
<title>Separation of Control and User Plane for Proxy Mobile =
IPv6</title>=20
<author fullname=3D"Ryuji Wakikawa" surname=3D"Wakikawa" initials=3D"R">
  <organization/>
</author>
<author fullname=3D"Rajesh Pazhyannur" surname=3D"Pazhyannur" =
initials=3D"R">
  <organization/>
</author>
<author fullname=3D"Sri Gundavelli" surname=3D"Gundavelli" =
initials=3D"S">
  <organization/>
</author>
<date year=3D"2013" day=3D"15" month=3D"July"/>
</front>
<seriesInfo value=3D"draft-wakikawa-netext-pmip-cp-up-separation-00" =
name=3D"Internet-Draft"/>
<format =
target=3D"http://www.ietf.org/internet-drafts/draft-wakikawa-netext-pmip-=
cp-up-separation-00.txt" type=3D"TXT"/>
</reference>

<reference anchor=3D"I-D.korhonen-6man-prefix-properties">
<front>
<title>IPv6 Prefix Properties</title>
<author fullname=3D"Jouni Korhonen" surname=3D"Korhonen" initials=3D"J">
  <organization/>
</author>
<author fullname=3D"Basavaraj Patil" surname=3D"Patil" initials=3D"B">
  <organization/>
</author>
<author fullname=3D"Sri Gundavelli" surname=3D"Gundavelli" =
initials=3D"S">
  <organization/>
</author>
<author fullname=3D"Pierrick Seite" surname=3D"Seite" initials=3D"P">
  <organization/>
</author>
<author fullname=3D"Dapeng Liu" surname=3D"Liu" initials=3D"D">
  <organization/>
</author>
<date year=3D"2013" day=3D"9" month=3D"July"/>
</front>
<seriesInfo value=3D"draft-korhonen-6man-prefix-properties-02" =
name=3D"Internet-Draft"/><format =
target=3D"http://www.ietf.org/internet-drafts/draft-korhonen-6man-prefix-=
properties-02.txt" type=3D"TXT"/>
</reference>

<reference anchor=3D"I-D.bhandari-dhc-class-based-prefix">
<front>
<title>DHCPv6 class based prefix</title>
<author fullname=3D"Shwetha Bhandari" surname=3D"Bhandari" =
initials=3D"S">
  <organization/>
</author>
<author fullname=3D"Gaurav Halwasia" surname=3D"Halwasia" =
initials=3D"G">
  <organization/>
</author>
<author fullname=3D"Sri Gundavelli" surname=3D"Gundavelli" =
initials=3D"S">
  <organization/>
</author>
<author fullname=3D"Hui Deng" surname=3D"Deng" initials=3D"H">
  <organization/>
</author>
<author fullname=3D"Laurent Thiebaut" surname=3D"Thiebaut" =
initials=3D"L">
  <organization/>
</author>
<author fullname=3D"Jouni Korhonen" surname=3D"Korhonen" initials=3D"J">
  <organization/>
</author>
<author fullname=3D"Ian Farrer" surname=3D"Farrer" initials=3D"I">
  <organization/>
</author>
<date year=3D"2013" day=3D"15" month=3D"July"/>
</front>
<seriesInfo value=3D"draft-bhandari-dhc-class-based-prefix-05" =
name=3D"Internet-Draft"/>
<format =
target=3D"http://www.ietf.org/internet-drafts/draft-bhandari-dhc-class-ba=
sed-prefix-05.txt" type=3D"TXT"/>
</reference>

<reference anchor=3D"TS.23.401">=20
<front>=20
<title>General Packet Radio Service (GPRS) enhancements for Evolved =
Universal Terrestrial Radio Access Network (E-UTRAN) access</title>
<author><organization>3GPP</organization></author>=20
<date year=3D"2013" month=3D"March" day=3D"07"/>=20
</front>=20
<seriesInfo value=3D"23.401 10.10.0" name=3D"3GPP TR"/>=20
<format target=3D"http://www.3gpp.org/ftp/Specs/html-info/23401.htm" =
type=3D"HTML"/> </reference>

<reference anchor=3D"TS.29303">=20
<front>=20
<title>Domain Name System Procedures; Stage 3</title>
<author><organization>3GPP</organization></author>=20
<date year=3D"2012" month=3D"September" day=3D"28"/>=20
</front>=20
<seriesInfo value=3D"23.303 11.2.0" name=3D"3GPP TR"/>=20
<format target=3D"http://www.3gpp.org/ftp/Specs/html-info/29303.htm" =
type=3D"HTML"/> </reference>

<reference anchor=3D"Paper-Locating.User">
<front>
<title>Locating the User</title>
<author initials=3D"G" surname=3D"Kirby">
  <organization />
</author>
<date year=3D"1995" />
</front>
<seriesInfo name=3D"" value=3D"Communication International" />
</reference>

<reference anchor=3D"Paper-Mobile.Data.Offloading">
<front>
<title>Mobile Data Offloading: How Much Can WiFi Deliver?</title>
<author initials=3D"K" surname=3D"Lee">
  <organization />
</author>
<author initials=3D"J" surname=3D"Lee">
  <organization />
</author>
<author initials=3D"Y" surname=3D"Yi">
  <organization />
</author>
<author initials=3D"I" surname=3D"Rhee">
  <organization />
</author>
<author initials=3D"S" surname=3D"Chong">
  <organization />
</author>
<date year=3D"2010" />
</front>
<seriesInfo name=3D"" value=3D"SIGCOMM 2010" />
</reference>

<reference anchor=3D"Paper-Distributed.Dynamic.Mobility">
<front>
<title>A Distributed Dynamic Mobility Management Scheme Designed for =
Flat IP Architectures</title>
<author initials=3D"P" surname=3D"Bertin">
  <organization />
</author>
<author initials=3D"S" surname=3D"Bonjour">
  <organization />
</author>
<author initials=3D"J-M" surname=3D"Bonnin">
  <organization />
</author>
<date year=3D"2008" />
</front>
<seriesInfo name=3D""=20
value=3D"Proceedings of 3rd International Conference on New =
Technologies, Mobility and Security (NTMS)" />
</reference>

<reference anchor=3D"Paper-Distributed.Centralized.Mobility">
<front>
<title>A Distributed or Centralized Mobility</title>
<author initials=3D"P" surname=3D"Bertin">
  <organization />
</author>
<author initials=3D"S" surname=3D"Bonjour">
  <organization />
</author>
<author initials=3D"J-M" surname=3D"Bonnin">
  <organization />
</author>
<date month=3D"December" year=3D"2009" />
</front>
<seriesInfo name=3D""=20
value=3D"Proceedings of Global Communications Conference=20
(GlobeCom)" />
</reference>

<reference anchor=3D"Paper-Migrating.Home.Agents">
<front>
<title>Migrating Home Agents Towards Internet-scale Mobility =
Deployments</title>
<author initials=3D"R" surname=3D"Wakikawa">
  <organization />
</author>
<author initials=3D"G" surname=3D"Valadon">
  <organization />
</author>
<author initials=3D"J" surname=3D"Murai">
  <organization />
</author>
<date month=3D"December" year=3D"2006" />
</front>
<seriesInfo name=3D""=20
value=3D"Proceedings of the ACM 2nd CoNEXT Conference=20
on Future Networking Technologies" />
</reference>

<reference anchor=3D"Paper-Distributed.Mobility.SAE">
<front>
<title>A Distributed IP Mobility Approach for 3G SAE</title>
<author initials=3D"M" surname=3D"Fisher">
  <organization />
</author>
<author initials=3D"F.U" surname=3D"Anderson">
  <organization />
</author>
<author initials=3D"A" surname=3D"Kopsel">
  <organization />
</author>
<author initials=3D"G" surname=3D"Schafer">
  <organization />
</author>
<author initials=3D"M" surname=3D"Schlager">
  <organization />
</author>
<date year=3D"2008" />
</front>
<seriesInfo name=3D""=20
value=3D"Proceedings of the 19th International Symposium on Personal, =
Indoor and Mobile Radio Communications (PIMRC)"/>
</reference>

<reference anchor=3D"Paper-Distributed.Mobility.Review">
<front>
<title>Distributed and Dynamic Mobility Management in Mobile Internet: =
Current Approaches and Issues</title>
<author initials=3D"H" surname=3D"Chan">
  <organization />
</author>
<author initials=3D"H" surname=3D"Yokota">
  <organization />
</author>
<author initials=3D"J" surname=3D"Xie">
  <organization />
</author>
<author initials=3D"P" surname=3D"Seite">
  <organization />
</author>
<author initials=3D"D" surname=3D"Liu">
  <organization />
</author>
<date month=3D"February" year=3D"2011" />
</front>
<seriesInfo name=3D""=20
value=3D"Journal of Communications, vol. 6, no. 1, pp. 4-15" />
</reference>

<reference anchor=3D"Paper-Distributed.Mobility.PMIP">
<front>
<title>Proxy Mobile IP with Distributed Mobility Anchors</title>
<author initials=3D"H" surname=3D"Chan">
  <organization />
</author>
<date month=3D"December" year=3D"2010" />
</front>
<seriesInfo name=3D""=20
value=3D"Proceedings of GlobeCom Workshop=20
on Seamless Wireless Mobility" />
</reference>

<reference anchor=3D"Paper-Distributed.Mobility.MIP">
<front>
<title>Distributed Mobility Management with Mobile IP</title>
<author initials=3D"H" surname=3D"Chan">
  <organization />
</author>
<date month=3D"June" year=3D"2012" />
</front>
<seriesInfo name=3D""=20
value=3D"Proceedings of IEEE International Communication Conference =
(ICC) Workshop on Telecommunications: from Research to Standards" />
</reference>

</references>

</back>
</rfc>

------=_NextPart_000_00C1_01CF321C.084D7200--


From nobody Tue Feb 25 10:40:33 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 011991A0289 for <gen-art@ietfa.amsl.com>; Tue, 25 Feb 2014 10:40:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.148
X-Spam-Level: 
X-Spam-Status: No, score=-1.148 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, 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 DhVX8Kb-gY_l for <gen-art@ietfa.amsl.com>; Tue, 25 Feb 2014 10:40:22 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id CA7541A01A8 for <gen-art@ietf.org>; Tue, 25 Feb 2014 10:40:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1393353620; d=isode.com; s=selector; i=@isode.com; bh=t8kFeX6Sznl4PIwQXw/Suk3mcSHUvfbeZhoLSP8uw7Q=; 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=im1bWBzp3vky/n6LeUYPWGXUw/+1fe04jMOaWxBnJUzNi4WNa3giDCkp+aMeXLKJBDcUXL ji3Glxdk/8otLtGn+6oaASi79eOF2ByNUarzx9ezxcTfKu/AeMQYM1kEseH4dqV7Qy55zm n/iYdtlHeoLt80oxwHwjIkjFTJpARTY=;
Received: from [192.168.0.4] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <UwzjkgBvgb7D@statler.isode.com>; Tue, 25 Feb 2014 18:40:19 +0000
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <530CE392.5060906@isode.com>
Date: Tue, 25 Feb 2014 18:40:18 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
References: <530CBD74.1010201@bell-labs.com>
In-Reply-To: <530CBD74.1010201@bell-labs.com>
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/so_VLjsqOF6Szob04B9Vhv2EPEE
Cc: General Area Review Team <gen-art@ietf.org>, draft-melnikov-smime-msa-to-mda@tools.ietf.org, Sean Turner <turners@ieca.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Gen-art] Gen-ART review of draft-melnikov-smime-msa-to-mda-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 18:40:26 -0000

On 25/02/2014 15:57, Vijay K. Gurbani 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-melnikov-smime-msa-to-mda-03
> Reviewer: Vijay K. Gurbani
> Review Date: Feb-25-2014
> IETF LC End Date: Mar-05-2014
> IESG Telechat date: Unknown
>
> I must say that this draft was written with implementors in mind.
> This is very refreshing.
>
> Major: 0
> Minor: 0
> Nits:  4
>
> This document is ready as a Proposed Standard.  Some minor nits follow:
Hi Vijay,
Thank you for your review.

> Nits:
>
> - S2.2, "Organizational policy and good security practice often
>  require that messages be reviewed before they are released to
>  external recipients."  Here, I suspect that organizational policy may
>  require such a vetting but I would think that "good security practice"
>  would not.  After all, unless a party is forced to do so (the
>  "organizational policy" part), why would one party willingly subject
>  its private communications to a third party before sending it
>  to the recipient?  I would not consider that a third party reading
>  my messages a "good security practice".  Therefore, I would take
>  the "good security practice" phrase out, unless of course, there is
>  some context to that phrase that I am not privy to.
I think this is a rather subjective topic: what one party (an 
enterprise/organization) considers "good" practice might indeed not be 
considered "good" by the sender. I am happy to remove "good" from the 
sentence.

> - S3.3, first sentence: "A 'domain signature' is a signature generated
>  on behalf of a set of users in the domain the users are a member of."
>  This sentence appears rather, for the lack of a better word, clunky.
>  How about rewriting this as: "A 'domain signature' is a signature
>  generated on behalf of a set of users who belong to the specific
>  domain."
Yes, your version is better. Changed.

> - S5, steps 3-A and 3-B: s/found then/found, then/
>  There are some more occurences of this, if you feel like it, you may
>  want to change these to have a comma as well.
Changed.
> - S7, first paragraph: s/permits masquerade./permits masquerading./
>   or, s/permits masquerade attacks./
Changed.

Best Regards,
Alexey


From nobody Tue Feb 25 11:03:18 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 C82A51A01A9 for <gen-art@ietfa.amsl.com>; Tue, 25 Feb 2014 11:03:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rndt2FbJLLr7 for <gen-art@ietfa.amsl.com>; Tue, 25 Feb 2014 11:03:06 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id E427E1A0199 for <gen-art@ietf.org>; Tue, 25 Feb 2014 11:03:05 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s1PJ2w0o005844 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 25 Feb 2014 13:02:59 -0600 (CST)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id s1PJ2vsq019782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 25 Feb 2014 13:02:58 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id s1PJ2tOQ027594; Tue, 25 Feb 2014 13:02:57 -0600 (CST)
Message-ID: <530CE927.60102@bell-labs.com>
Date: Tue, 25 Feb 2014 13:04:07 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <530CBD74.1010201@bell-labs.com> <530CE392.5060906@isode.com>
In-Reply-To: <530CE392.5060906@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; 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/sVJ8Cw-Sb6qkVIeLMGZZEq2qE88
Cc: General Area Review Team <gen-art@ietf.org>, draft-melnikov-smime-msa-to-mda@tools.ietf.org, Sean Turner <turners@ieca.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Gen-art] Gen-ART review of draft-melnikov-smime-msa-to-mda-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 19:03:13 -0000

On 02/25/2014 12:40 PM, Alexey Melnikov wrote:
> Hi Vijay,
> Thank you for your review.

Alexey: No worries.

> I think this is a rather subjective topic: what one party (an
> enterprise/organization) considers "good" practice might indeed not be
> considered "good" by the sender. I am happy to remove "good" from the
> sentence.

Perfect; that works for me.

Thanks for incorporating the remaining changes.

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 Wed Feb 26 08:42:10 2014
Return-Path: <huub.van.helvoort@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C50B91A02DC for <gen-art@ietfa.amsl.com>; Wed, 26 Feb 2014 08:41:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.048
X-Spam-Level: 
X-Spam-Status: No, score=-2.048 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, 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 YFhw9n55MAEt for <gen-art@ietfa.amsl.com>; Wed, 26 Feb 2014 08:41:53 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 327D61A019B for <gen-art@ietf.org>; Wed, 26 Feb 2014 08:41:37 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDZ94012; Wed, 26 Feb 2014 16:40:43 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 26 Feb 2014 16:38:53 +0000
Received: from LHREML511-MBS.china.huawei.com ([10.201.4.130]) by lhreml404-hub.china.huawei.com ([::1]) with mapi id 14.03.0158.001; Wed, 26 Feb 2014 16:39:01 +0000
From: Huub Van Helvoort <huub.van.helvoort@huawei.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
Thread-Topic: Gen-art LC review of draft-ietf-mpls-tp-psc-itu-02.txt
Thread-Index: AQHPMYvrdiAImCxNeE+GYoW8Xv9JPprE2hukgAD5j4CAAeB53A==
Date: Wed, 26 Feb 2014 16:39:01 +0000
Message-ID: <74118A81AEACB94EB8AB398AF85AF7820C6BEF@lhreml511-mbs>
References: <1393265494.8036.426.camel@mightyatom> <74118A81AEACB94EB8AB398AF85AF7820C556F@lhreml511-mbs>, <1393327139.8036.458.camel@mightyatom>
In-Reply-To: <1393327139.8036.458.camel@mightyatom>
Accept-Language: en-GB, nl-NL, zh-CN, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.71.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/Gc0ZUtYd6l4fyiNVkfUQdwePy1k
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org" <draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-mpls-tp-psc-itu-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 16:41:59 -0000

Hello Elwyn,

Please find my response in-line [Huub2]

To avoid any confusion I have snipped the parts that do not need
further expanation.

> Minor issues:
> s1, next to last para:
>
> >    This document describes the behavior of the PSC protocol
> including
> >    the priority logic and the state machine when all the
> capabilities
> >    associated with the APS mode are enabled.  The PSC protocol
> behavior
> >    for the PSC mode is as defined in RFC 6378.
>
> APS mode involves five capabilities which can, apparently, be
> implemented and advertised indpendently, so presumably there might be
> reasons for either implementing or turning on just a subset.
>
> [Huub] There were originally separate drafts for each of the
> capabilities.
> However, it was very complex to define the effect on the state
> transition tables for each capability or combination of capabilities.
>
> [Huub] to resolve this issue it was decided that for any permitation
> of the possible combinations of capabilities a separate draft should
> be
> developed. RFC6378 is the one where none of the capabilities is
> used, and this draft is the one where all capabiliies are used. So far
> none of the other possible drafts is written.
>
> [Huub] This draft provides the behavior similar to APS used in ITU-T
> for other technologies.
>
> Are there
> any implications for the PSC protocol if only some subset of the the
> capabilities are available in a given node?  (This may be a dumb
> question and I haven't tried to work out what might go wrong if you
> did have any of the available subsets.)
>
> [Huub] both nodes MUST support the same subset, if they don't the
> result will be unpredictable because the state machines are different.
>
> s9.1.1/s9.2: Following on from the previous point, s9.1.1 implies that
> the system can operate happily with some subset of the five
> capabilities
> turned on provided that both ends concur.  However there is no mode
> name that would cover such a subset.
>
> [Huub] as indicated above, the mode name does not exist because the
> draft that describes that mode does not (yet) exist.
>
> Does this actually mean that turning on
> a subset doesn't really work?
>
> [Huub] indeed, not until there is a draft that describes it.
>
> And if it doesn't work why bother with
> five flag bits?
>
> [Huub] to give others the opportunity to write the missing draft(s),
> this was the agreed by the WG chairs.
>
> Also the phraseology used here could lead to future
> problems if more capabilities are defined:  suppose some future new
> mode
> (FOO) adds <n> more capabilities but the two 'modes' can be turned on
> independently - as currently expressed you would have to define three
> mode names for APS only, FOO only and APS + FOO.. and so on with more
> capability sets.  Unintended consequence? Oh, and what if a capability
> is used in more than one mode?
>
> [Huub] it is up to the authors of additional drafts to come up with a
> name for the mode described in their draft.

To be absolutely honest, my initial reaction to the above (i.e., right
back to the beginning of Minor Issues) went something like
"******** ARRRGGGGHHH! Choke!! Splutter!!!".

Be that as it may, if that is what is agreed then please could there be
some explanation in the document. Please!

[Huub2] the probability that there may be several "solutions" is IMHO
very small.
Personally I do not expect any other solution because RFC6378 is
what IETF wants, and this draft is what ITU-T wants and will=20
document in recommendation G.8131.
Any other "solution" would be non-standard.=20
Adding an explanation to this draft will give the impression that
other solutions will be acceptable. Something neither IETF nor
ITU-t would admit to.

> s13: The addition of the Capabilities TLV and the requirement that it
> is
> carried accurately and repeatedly in every PSC message introduces a
> new
> aspect to the DoS/random corruption problem mentioned in s6 of RFC
> 6378.
> A single bit corruption in a PSC message will lead to disablement of
> protection switching and requirement of operator intervention.  I am
> not
> sure if this is a serious issue, but it probably merits a comment in
> s13
> and verification that it does match with the words in RFC 6378 as
> regards 'converging on a stable state'.
>
> [Huub] a bit error will occur in one message, RFC6378 s4.1 addresses
> that issue.

I don't think this covers the problem:
The last para of s6 of RFC 6378 says:

>    However, a new concern for this document is the accidental corruption
>    of messages (through faulty implementations or random corruption).
>    The main concern is around the Request, FPath, and Path fields as a
>    change to these fields would change the behavior of the peer end
>    point.  Although this document does not define a way to avoid a
>    change in network behavior upon receipt of a message indicating a
>    change in protection status, the transition between states will
>    converge on a known and stable behavior in the face of messages that
>    do not match reality.

This appears to imply that random bit errors can percolate up to the
protocol engine.  If the bit error affects the capability flag bits in the
Capability TLV then the behaviour specified in s9.1.1 would come into play:

>    When a node receives a Capabilities TLV it MUST compare it to its
>    most recent transmitted Capabilities TLV.  If the two are equal, the
>    protected domain is said to be running in the mode indicated by that
>    set of capabilities (see Section 9.2).  If the sent and received
>    Capabilities TLVs are not equal, this indicates a capabilities
>    mismatch.  When this happens, the node MUST alert the operator and
>    MUST NOT perform any protection switching until the operator resolves
>    the mismatch in the Capabilities TLV.

The result of such a corrupted bit would a.s. be a mismatch that should
be followed by a turn off of protection switching and operator alerting.

[Huub2]
A received PSC message with a bit error is a not valid PSC message.

If a received PSC message is unexpected (due to a bit error, or a corrupt
far end protocol engone) in a particular state it is considered a not valid=
=20
message and is ignored

The capability of a protected link is provisioned at initiation and cannot
be changed during operation, so a PSC message with a capability bit
changed (e.g. due to a bit error)  is considered not valid PSC message
and is ignored.

I think this is covered by the last paragraph in s4.1 of RFC6378.
=3D=3D=3D=3D
    If no valid PSC message is received, over a period of several
    continual messages intervals, the last valid received message remains
    applicable.
 =3D=3D=3D

> Nits/editorial comments:
> s4.4, title: s/Capability 1/Priority Modifications/ (Ok, its accurate
> but bald)
>
> [Huub] OK.

[Huub2] will be changed as you propose.

> s7.3 et seq: The term "selector bridge" is introduced without
> definition.  I suspect it is a piece of jargon I am supposed to know
> but
> I think a reference would help.
>
> [Huub] RFC6378 uses "selector", "selector bridge" is the equivalent
> ITU term.

Can we tie them together then please?

[Huub2] for consistency I propose to use "selector" in the whole
document. Selector (without bridge) is already used in a few places.

> s7.4, para 1:
> > the rules to resolve the equal priority requests are
> >    required. Should this be s/the rules/some rules/?
>
> [Huub] or s/the rules/rules/

Either would help.

[Huub2] OK.

> s8, definition of Exercise (EXER): Describing EXER as 'replacing' one
> of
> NR, RR or DNR seems a bit odd.  Mentioning RR is particularly
> problematic since it makes the definitions sort of circular as RR is
> the response to EXER.

Any thoughts here?...

[Huub2] see below.

> I guess what is probably appropriate is to say that
> it is built in the same way as an NR message would be built.
>
> [Huub] the "replacing" means that in case an operator wants to verify
> the operation of PSC, the excersise commend is issued and the
> transmission of RR (or NR, or DNR) is stopped and EXER is sent
> instead.

I think I see what is going on noew
Perhaps adding something like the phrase "that would normally be sent
periodically in the IDLE state"

[Huub2] if it helps readability we will do as suggested.

> s9.1: RFC 6378 doesn't define the encoding of the TLV type and TLV
> length fields, so it needs to be done here (Unsigned integers). (It
> also
> doesn't define encoding of the (unnecessary) overall TLV length field
> in the PSC header.
>
> [Huub] IANA asigned the TLV type value. By not giving exact values
> we leave the possibility open that there are more than 32 flags.

That's not the issue.  The problem is that the protocol does not specify
how the type and length numbers should be represented on the wire.  The
standard answer is unsigned integer in network bit order.

[Huub2] OK, I now understand your point. This can be addressed.

> s9.1: What happens if the receiver gets a TLV with some a flags length
> that isn't a multiple of 4 (or indeed a TLV it deosn't recognize?)  It
> might be cleaner to define the length in terms of units of 32 bits.
>
> [Huub] this can be treated the same as a bit error in a PSC message.

This should be stated.

[Huub2] OK, we will address this.

Best regards, Huub.=


From nobody Wed Feb 26 10:23:58 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 0D0B11A07C3 for <gen-art@ietfa.amsl.com>; Wed, 26 Feb 2014 10:23:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fuGWuQ-KJsyK for <gen-art@ietfa.amsl.com>; Wed, 26 Feb 2014 10:23:46 -0800 (PST)
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 2A17D1A07D3 for <gen-art@ietf.org>; Wed, 26 Feb 2014 10:23:46 -0800 (PST)
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 1WIj8t-0005z1-JJ; Wed, 26 Feb 2014 18:23:39 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Huub Van Helvoort <huub.van.helvoort@huawei.com>
In-Reply-To: <74118A81AEACB94EB8AB398AF85AF7820C6BEF@lhreml511-mbs>
References: <1393265494.8036.426.camel@mightyatom> <74118A81AEACB94EB8AB398AF85AF7820C556F@lhreml511-mbs> ,<1393327139.8036.458.camel@mightyatom> <74118A81AEACB94EB8AB398AF85AF7820C6BEF@lhreml511-mbs>
Content-Type: text/plain
Date: Wed, 26 Feb 2014 18:23:35 +0000
Message-Id: <1393439015.8036.563.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/Q3olgAzZKSFnm2gBJBLdQHmvyok
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org" <draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-mpls-tp-psc-itu-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 18:23:54 -0000

Hi, Huub.

Thanks for the responses: Agreed bits snipped again.


On Wed, 2014-02-26 at 16:39 +0000, Huub Van Helvoort wrote:
> Hello Elwyn,
> 
> Please find my response in-line [Huub2]
> 
> To avoid any confusion I have snipped the parts that do not need
> further expanation.
> 
> > Minor issues:
> > s1, next to last para:
> >
> > >    This document describes the behavior of the PSC protocol
> > including
> > >    the priority logic and the state machine when all the
> > capabilities
> > >    associated with the APS mode are enabled.  The PSC protocol
> > behavior
> > >    for the PSC mode is as defined in RFC 6378.
> >
> > APS mode involves five capabilities which can, apparently, be
> > implemented and advertised indpendently, so presumably there might be
> > reasons for either implementing or turning on just a subset.
> >
> > [Huub] There were originally separate drafts for each of the
> > capabilities.
> > However, it was very complex to define the effect on the state
> > transition tables for each capability or combination of capabilities.
> >
> > [Huub] to resolve this issue it was decided that for any permitation
> > of the possible combinations of capabilities a separate draft should
> > be
> > developed. RFC6378 is the one where none of the capabilities is
> > used, and this draft is the one where all capabiliies are used. So far
> > none of the other possible drafts is written.
> >
> > [Huub] This draft provides the behavior similar to APS used in ITU-T
> > for other technologies.
> >
> > Are there
> > any implications for the PSC protocol if only some subset of the the
> > capabilities are available in a given node?  (This may be a dumb
> > question and I haven't tried to work out what might go wrong if you
> > did have any of the available subsets.)
> >
> > [Huub] both nodes MUST support the same subset, if they don't the
> > result will be unpredictable because the state machines are different.
> >
> > s9.1.1/s9.2: Following on from the previous point, s9.1.1 implies that
> > the system can operate happily with some subset of the five
> > capabilities
> > turned on provided that both ends concur.  However there is no mode
> > name that would cover such a subset.
> >
> > [Huub] as indicated above, the mode name does not exist because the
> > draft that describes that mode does not (yet) exist.
> >
> > Does this actually mean that turning on
> > a subset doesn't really work?
> >
> > [Huub] indeed, not until there is a draft that describes it.
> >
> > And if it doesn't work why bother with
> > five flag bits?
> >
> > [Huub] to give others the opportunity to write the missing draft(s),
> > this was the agreed by the WG chairs.
> >
> > Also the phraseology used here could lead to future
> > problems if more capabilities are defined:  suppose some future new
> > mode
> > (FOO) adds <n> more capabilities but the two 'modes' can be turned on
> > independently - as currently expressed you would have to define three
> > mode names for APS only, FOO only and APS + FOO.. and so on with more
> > capability sets.  Unintended consequence? Oh, and what if a capability
> > is used in more than one mode?
> >
> > [Huub] it is up to the authors of additional drafts to come up with a
> > name for the mode described in their draft.
> 
> To be absolutely honest, my initial reaction to the above (i.e., right
> back to the beginning of Minor Issues) went something like
> "******** ARRRGGGGHHH! Choke!! Splutter!!!".
> 
> Be that as it may, if that is what is agreed then please could there be
> some explanation in the document. Please!
> 
> [Huub2] the probability that there may be several "solutions" is IMHO
> very small.
> Personally I do not expect any other solution because RFC6378 is
> what IETF wants, and this draft is what ITU-T wants and will 
> document in recommendation G.8131.
> Any other "solution" would be non-standard. 
> Adding an explanation to this draft will give the impression that
> other solutions will be acceptable. Something neither IETF nor
> ITU-t would admit to.

Politics! OK - How about we add to either s9.1.1 or s9.2 something like:

   Only combinations of capabilities specified by a mode are allowed.   
   Capability TLVs with other combinations will be treated as invalid 
   PSC messages. 
> 
> > s13: The addition of the Capabilities TLV and the requirement that it
> > is
> > carried accurately and repeatedly in every PSC message introduces a
> > new
> > aspect to the DoS/random corruption problem mentioned in s6 of RFC
> > 6378.
> > A single bit corruption in a PSC message will lead to disablement of
> > protection switching and requirement of operator intervention.  I am
> > not
> > sure if this is a serious issue, but it probably merits a comment in
> > s13
> > and verification that it does match with the words in RFC 6378 as
> > regards 'converging on a stable state'.
> >
> > [Huub] a bit error will occur in one message, RFC6378 s4.1 addresses
> > that issue.
> 
> I don't think this covers the problem:
> The last para of s6 of RFC 6378 says:
> 
> >    However, a new concern for this document is the accidental corruption
> >    of messages (through faulty implementations or random corruption).
> >    The main concern is around the Request, FPath, and Path fields as a
> >    change to these fields would change the behavior of the peer end
> >    point.  Although this document does not define a way to avoid a
> >    change in network behavior upon receipt of a message indicating a
> >    change in protection status, the transition between states will
> >    converge on a known and stable behavior in the face of messages that
> >    do not match reality.
> 
> This appears to imply that random bit errors can percolate up to the
> protocol engine.  If the bit error affects the capability flag bits in the
> Capability TLV then the behaviour specified in s9.1.1 would come into play:
> 
> >    When a node receives a Capabilities TLV it MUST compare it to its
> >    most recent transmitted Capabilities TLV.  If the two are equal, the
> >    protected domain is said to be running in the mode indicated by that
> >    set of capabilities (see Section 9.2).  If the sent and received
> >    Capabilities TLVs are not equal, this indicates a capabilities
> >    mismatch.  When this happens, the node MUST alert the operator and
> >    MUST NOT perform any protection switching until the operator resolves
> >    the mismatch in the Capabilities TLV.
> 
> The result of such a corrupted bit would a.s. be a mismatch that should
> be followed by a turn off of protection switching and operator alerting.
> 
> [Huub2]
> A received PSC message with a bit error is a not valid PSC message.
> 
> If a received PSC message is unexpected (due to a bit error, or a corrupt
> far end protocol engone) in a particular state it is considered a not valid 
> message and is ignored
> 
> The capability of a protected link is provisioned at initiation and cannot
> be changed during operation, so a PSC message with a capability bit
> changed (e.g. due to a bit error)  is considered not valid PSC message
> and is ignored.
> 
> I think this is covered by the last paragraph in s4.1 of RFC6378.
> ====
>     If no valid PSC message is received, over a period of several
>     continual messages intervals, the last valid received message remains
>     applicable.
>  ===

Sorry to harp on about this... I think we are trying to distinguish
between invalid messages and protocol errors.  If a PSC message with the
wrong set of Capability bits set is (always?) considered not a valid PSC
message then you need to change the wording of the piece of s9.1.1
quoted above.  The text in [Huub2} implies:
either:
   that there is a distinction between the first PSC message and   
   subsequent ones, in which case the comparison is against the 
   internally configured value of the capability bits, since nothing 
   has been sent or received yet, and that means that the 
   specified action only happens on the first PSC message - it 
   isn't clear to me that the specified action makes sense in that case.
or:
   that *any* PSC message with the wrong set of capability bits set 
   (again tested against the internally configured value) is 
   flagged up as invalid and discarded *without any action being 
   taken*. In this case the text in s9.1.1 is never actioned.

For my peace of mind.. Can you confirm whether my interprestation of RFC
6378 s6 is correct, i.e., bit errors in transmission are *not* detected
by the layers below the PSC protocol and corrupted PSC messages will be
passed to the PSC state machine.    



From nobody Wed Feb 26 11:11:23 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 492FA1A0118 for <gen-art@ietfa.amsl.com>; Wed, 26 Feb 2014 11:11:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.617
X-Spam-Level: *
X-Spam-Status: No, score=1.617 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] 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 yAf3kI2q1tu5 for <gen-art@ietfa.amsl.com>; Wed, 26 Feb 2014 11:11:16 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 674451A0867 for <gen-art@ietf.org>; Wed, 26 Feb 2014 11:10:30 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1QJAQ3r003400; Wed, 26 Feb 2014 19:10:27 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1QJAPjU003388 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 26 Feb 2014 19:10:26 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <elwynd@folly.org.uk>, <huubatwork@gmail.com>
References: <1393265494.8036.426.camel@mightyatom>	 <74118A81AEACB94EB8AB398AF85AF7820C556F@lhreml511-mbs>	 , <1393327139.8036.458.camel@mightyatom>	 <74118A81AEACB94EB8AB398AF85AF7820C6BEF@lhreml511-mbs>, <1393439015.8036.563.camel@mightyatom> <dc49e44e59a448b1ba5522c5ee893fd4@BLUPR05MB151.namprd05.prod.outlook.com>
In-Reply-To: <dc49e44e59a448b1ba5522c5ee893fd4@BLUPR05MB151.namprd05.prod.outlook.com>
Date: Wed, 26 Feb 2014 19:10:25 -0000
Message-ID: <0f3601cf3326$688c6940$39a53bc0$@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: AQGd5+ySYb5smzoWRp6z/6OWLkbnXgD+ZPcDArZD8EgCLHQ1zQGrHDI6An3H9RSa2ikWQA==
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/FsIf3A11miFQ_zGQRNehRC7UcjI
Cc: gen-art@ietf.org, draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-mpls-tp-psc-itu-02.txt
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, 26 Feb 2014 19:11:21 -0000

Sut mae, Elwyn-gwas,

[snip]

> Politics! OK - How about we add to either s9.1.1 or s9.2 something like:

I don't think it is politics at all, and I don't really like that Huub
referenced this as IETF and ITU-T since both documents are IETF standards track
work.

There are some people who want to deploy one set of options (the empty set) and
they have an RFC.
There is another set of people who want to deploy a different set of options
(all 5 of them) and they will have this RFC.

>    Only combinations of capabilities specified by a mode are allowed.
>    Capability TLVs with other combinations will be treated as invalid
>    PSC messages.

But this is not true.

What we have is:
A node knows which options it supports, and those options are expressed as
bundles (modes).
A node that tries to communicate with you must offer a set of options (a mode).
Either you support the mode or you don't.
If you support it, off you go.
If you don't support it, you reject the message saying "unsupported" as
described in this document.

The message that offers a different set of options (i.e. a different mode) is
not invalid, it is just that you don't understand it. You can't accept it
because you don't know how to behave in that mode.

OTOH, when someone writes the new RFC describing that mode, you might enhance
your implementation to support it as well.

(Hint: it really helps to think in modes. A mode is expressed as a bit-flag with
plenty-bits of which five currently have meaning.)

I agree with you that there is some distinction to be made between "invalid
message" and "protocol error".
But "no valid message" does not mean "protocol error" or "invalid message" was
received. It is a composite of possibilities that reflects the negation of
receiving a message that was small and perfectly formed.

Ciao,
Adrian


From nobody Wed Feb 26 11:58:16 2014
Return-Path: <huub.van.helvoort@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EBC71A0700 for <gen-art@ietfa.amsl.com>; Wed, 26 Feb 2014 11:58:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level: 
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, 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 g3-T0oJxrLXC for <gen-art@ietfa.amsl.com>; Wed, 26 Feb 2014 11:58:02 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD0C1A0118 for <gen-art@ietf.org>; Wed, 26 Feb 2014 11:58:02 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBO00970; Wed, 26 Feb 2014 19:57:49 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 26 Feb 2014 19:57:37 +0000
Received: from LHREML511-MBS.china.huawei.com ([10.201.4.130]) by lhreml404-hub.china.huawei.com ([::1]) with mapi id 14.03.0158.001; Wed, 26 Feb 2014 19:57:43 +0000
From: Huub Van Helvoort <huub.van.helvoort@huawei.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
Thread-Topic: Gen-art LC review of draft-ietf-mpls-tp-psc-itu-02.txt
Thread-Index: AQHPMYvrdiAImCxNeE+GYoW8Xv9JPprE2hukgAD5j4CAAeB53IAAKH2AgAAD1pk=
Date: Wed, 26 Feb 2014 19:57:43 +0000
Message-ID: <74118A81AEACB94EB8AB398AF85AF7820C70B8@lhreml511-mbs>
References: <1393265494.8036.426.camel@mightyatom> <74118A81AEACB94EB8AB398AF85AF7820C556F@lhreml511-mbs> ,<1393327139.8036.458.camel@mightyatom> <74118A81AEACB94EB8AB398AF85AF7820C6BEF@lhreml511-mbs>, <1393439015.8036.563.camel@mightyatom>
In-Reply-To: <1393439015.8036.563.camel@mightyatom>
Accept-Language: en-GB, nl-NL, zh-CN, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.69.245]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/_fhh4cZ3yrAQvF_S9e3rgmuR4Ys
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org" <draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-mpls-tp-psc-itu-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 19:58:08 -0000

Hello Elwyn,

Thanks for your reply.
See my responses in-line [Huub3].

=3D=3D=3D=3D=3D
On Wed, 2014-02-26 at 16:39 +0000, Huub Van Helvoort wrote:
> Hello Elwyn,
>
> Please find my response in-line [Huub2]
>
> To avoid any confusion I have snipped the parts that do not need
> further expanation.
>
> > Minor issues:
> > s1, next to last para:
> >
> > >    This document describes the behavior of the PSC protocol
> > including
> > >    the priority logic and the state machine when all the
> > capabilities
> > >    associated with the APS mode are enabled.  The PSC protocol
> > behavior
> > >    for the PSC mode is as defined in RFC 6378.
> >
> > APS mode involves five capabilities which can, apparently, be
> > implemented and advertised indpendently, so presumably there might be
> > reasons for either implementing or turning on just a subset.
> >
> > [Huub] There were originally separate drafts for each of the
> > capabilities.
> > However, it was very complex to define the effect on the state
> > transition tables for each capability or combination of capabilities.
> >
> > [Huub] to resolve this issue it was decided that for any permitation
> > of the possible combinations of capabilities a separate draft should
> > be
> > developed. RFC6378 is the one where none of the capabilities is
> > used, and this draft is the one where all capabiliies are used. So far
> > none of the other possible drafts is written.
> >
> > [Huub] This draft provides the behavior similar to APS used in ITU-T
> > for other technologies.
> >
> > Are there
> > any implications for the PSC protocol if only some subset of the the
> > capabilities are available in a given node?  (This may be a dumb
> > question and I haven't tried to work out what might go wrong if you
> > did have any of the available subsets.)
> >
> > [Huub] both nodes MUST support the same subset, if they don't the
> > result will be unpredictable because the state machines are different.
> >
> > s9.1.1/s9.2: Following on from the previous point, s9.1.1 implies that
> > the system can operate happily with some subset of the five
> > capabilities
> > turned on provided that both ends concur.  However there is no mode
> > name that would cover such a subset.
> >
> > [Huub] as indicated above, the mode name does not exist because the
> > draft that describes that mode does not (yet) exist.
> >
> > Does this actually mean that turning on
> > a subset doesn't really work?
> >
> > [Huub] indeed, not until there is a draft that describes it.
> >
> > And if it doesn't work why bother with
> > five flag bits?
> >
> > [Huub] to give others the opportunity to write the missing draft(s),
> > this was the agreed by the WG chairs.
> >
> > Also the phraseology used here could lead to future
> > problems if more capabilities are defined:  suppose some future new
> > mode
> > (FOO) adds <n> more capabilities but the two 'modes' can be turned on
> > independently - as currently expressed you would have to define three
> > mode names for APS only, FOO only and APS + FOO.. and so on with more
> > capability sets.  Unintended consequence? Oh, and what if a capability
> > is used in more than one mode?
> >
> > [Huub] it is up to the authors of additional drafts to come up with a
> > name for the mode described in their draft.
>
> To be absolutely honest, my initial reaction to the above (i.e., right
> back to the beginning of Minor Issues) went something like
> "******** ARRRGGGGHHH! Choke!! Splutter!!!".
>
> Be that as it may, if that is what is agreed then please could there be
> some explanation in the document. Please!
>
> [Huub2] the probability that there may be several "solutions" is IMHO
> very small.
> Personally I do not expect any other solution because RFC6378 is
> what IETF wants, and this draft is what ITU-T wants and will
> document in recommendation G.8131.
> Any other "solution" would be non-standard.
> Adding an explanation to this draft will give the impression that
> other solutions will be acceptable. Something neither IETF nor
> ITU-t would admit to.

Politics! OK - How about we add to either s9.1.1 or s9.2 something like:

   Only combinations of capabilities specified by a mode are allowed.
   Capability TLVs with other combinations will be treated as invalid
   PSC messages.

[Huub3] that works for me. Eric, Jeong-dong can you address this?

> > s13: The addition of the Capabilities TLV and the requirement that it
> > is
> > carried accurately and repeatedly in every PSC message introduces a
> > new
> > aspect to the DoS/random corruption problem mentioned in s6 of RFC
> > 6378.
> > A single bit corruption in a PSC message will lead to disablement of
> > protection switching and requirement of operator intervention.  I am
> > not
> > sure if this is a serious issue, but it probably merits a comment in
> > s13
> > and verification that it does match with the words in RFC 6378 as
> > regards 'converging on a stable state'.
> >
> > [Huub] a bit error will occur in one message, RFC6378 s4.1 addresses
> > that issue.
>
> I don't think this covers the problem:
> The last para of s6 of RFC 6378 says:
>
> >    However, a new concern for this document is the accidental corruptio=
n
> >    of messages (through faulty implementations or random corruption).
> >    The main concern is around the Request, FPath, and Path fields as a
> >    change to these fields would change the behavior of the peer end
> >    point.  Although this document does not define a way to avoid a
> >    change in network behavior upon receipt of a message indicating a
> >    change in protection status, the transition between states will
> >    converge on a known and stable behavior in the face of messages that
> >    do not match reality.
>
> This appears to imply that random bit errors can percolate up to the
> protocol engine.  If the bit error affects the capability flag bits in th=
e
> Capability TLV then the behaviour specified in s9.1.1 would come into pla=
y:
>
> >    When a node receives a Capabilities TLV it MUST compare it to its
> >    most recent transmitted Capabilities TLV.  If the two are equal, the
> >    protected domain is said to be running in the mode indicated by that
> >    set of capabilities (see Section 9.2).  If the sent and received
> >    Capabilities TLVs are not equal, this indicates a capabilities
> >    mismatch.  When this happens, the node MUST alert the operator and
> >    MUST NOT perform any protection switching until the operator resolve=
s
> >    the mismatch in the Capabilities TLV.
>
> The result of such a corrupted bit would a.s. be a mismatch that should
> be followed by a turn off of protection switching and operator alerting.
>
> [Huub2]
> A received PSC message with a bit error is a not valid PSC message.
>
> If a received PSC message is unexpected (due to a bit error, or a corrupt
> far end protocol engone) in a particular state it is considered a not val=
id
> message and is ignored
>
> The capability of a protected link is provisioned at initiation and canno=
t
> be changed during operation, so a PSC message with a capability bit
> changed (e.g. due to a bit error)  is considered not valid PSC message
> and is ignored.
>
> I think this is covered by the last paragraph in s4.1 of RFC6378.
> =3D=3D=3D=3D
>     If no valid PSC message is received, over a period of several
>     continual messages intervals, the last valid received message remains
>     applicable.
>  =3D=3D=3D

Sorry to harp on about this...

[Huub3] no problem, clarity is key

I think we are trying to distinguish
between invalid messages and protocol errors.  If a PSC message with the
wrong set of Capability bits set is (always?) considered not a valid PSC
message then you need to change the wording of the piece of s9.1.1
quoted above.=20

[Huub3] I agree, I will check with the other authors if they agree too.
If they disagree I will inform you.

The text in [Huub2} implies:
either:
   that there is a distinction between the first PSC message and
   subsequent ones, in which case the comparison is against the
   internally configured value of the capability bits, since nothing
   has been sent or received yet, and that means that the
   specified action only happens on the first PSC message - it
   isn't clear to me that the specified action makes sense in that case.

[Huub3] it is a bit different. When a new/changed PSC message
is sent, it is sent three times very fast. A majority decision is taken
to determine the correct value, so it is possible that the first is
discarded because it is not the same as the second and third.
The capability bits are always compared to the provisioned mode.

or:
   that *any* PSC message with the wrong set of capability bits set
   (again tested against the internally configured value) is
   flagged up as invalid and discarded *without any action being
   taken*. In this case the text in s9.1.1 is never actioned.

[Huub3] according to s9.1.1 the capability TLV MUST be added
always to every PSC message sent. The capability bits are set to
the provisioned mode. There is one exception: the original PSC as=20
described in RFC6378, because that does not use capability TLV.

For my peace of mind.. Can you confirm whether my interprestation of RFC
6378 s6 is correct, i.e., bit errors in transmission are *not* detected
by the layers below the PSC protocol and corrupted PSC messages will be
passed to the PSC state machine.

[Huub3] If the (lower) server layer is Ethernet, the Ethernet frame can
use the FCS to detect bit errors and discard the Ethernet/MPLS frame.
If FCS is not used bit errors are undetected.
If the (lower) server layer is SDH/SONET/OTN the FEC (forward
error correction) will correct bit errors that occur in the physical layer.
If FEC is not used bit errors are counted, if the error rate is excessive
AIS will be inserted, in a packet (higher) client layer this will result in
discarding all frames.

Cheers, Huub.=


From nobody Wed Feb 26 12:22:03 2014
Return-Path: <huubatwork@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 53F751A08A6 for <gen-art@ietfa.amsl.com>; Wed, 26 Feb 2014 12:21:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gk-QzO1aW2vZ for <gen-art@ietfa.amsl.com>; Wed, 26 Feb 2014 12:21:53 -0800 (PST)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id 2A70B1A0880 for <gen-art@ietf.org>; Wed, 26 Feb 2014 12:21:52 -0800 (PST)
Received: by mail-wi0-f182.google.com with SMTP id f8so2635511wiw.3 for <gen-art@ietf.org>; Wed, 26 Feb 2014 12:21:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:disposition-notification-to:date:from:reply-to :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=CaaGH1HnLDxswlu9+CRCQQnmKI/ezB+3Jx0Uqm2siO4=; b=wZ5Pu57ZxGG/ATJOgOST6YHJWEycsBtpHnl1EfHUefb0HQE/lQH7P3AhKQKUWsp6cK e2Im/RCTLrXU8mIVeN0nLW1idyrpqr2j9KnNeggXzdoRE7prDr9vf7/lN0JEhvHr2QTq JynVPZnm+nVK0XI9sPPwaXezqUaODZFE3GbF+NES8nKdld0UrhIrLawUIeJ1ZCGgl3id Un/jW+MRMycf6nhjRXambx05gM8TI/zqUGVRVa9oE9/7lfO6wNdcs7jqDGLWJZWmrac7 J9J82wPX5u5NMLLnuGlwdUxlZRgCngDMP/gSIc12L1qZA0FGqMM3FWZp+hzwEJErx3Or YICg==
X-Received: by 10.180.221.68 with SMTP id qc4mr9350705wic.30.1393446111451; Wed, 26 Feb 2014 12:21:51 -0800 (PST)
Received: from McAsterix.local (g215085.upc-g.chello.nl. [80.57.215.85]) by mx.google.com with ESMTPSA id hy8sm5245112wjb.2.2014.02.26.12.21.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Feb 2014 12:21:50 -0800 (PST)
Message-ID: <530E4CDD.7080506@gmail.com>
Date: Wed, 26 Feb 2014 21:21:49 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, elwynd@folly.org.uk
References: <1393265494.8036.426.camel@mightyatom>	 <74118A81AEACB94EB8AB398AF85AF7820C556F@lhreml511-mbs>	 , <1393327139.8036.458.camel@mightyatom>	 <74118A81AEACB94EB8AB398AF85AF7820C6BEF@lhreml511-mbs>, <1393439015.8036.563.camel@mightyatom> <dc49e44e59a448b1ba5522c5ee893fd4@BLUPR05MB151.namprd05.prod.outlook.com> <0f3601cf3326$688c6940$39a53bc0$@olddog.co.uk>
In-Reply-To: <0f3601cf3326$688c6940$39a53bc0$@olddog.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/QDfBYJpLlSFLoxV8CXNkVLw2cBQ
Cc: gen-art@ietf.org, draft-ietf-mpls-tp-psc-itu.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art LC review of draft-ietf-mpls-tp-psc-itu-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: huubatwork@gmail.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: Wed, 26 Feb 2014 20:21:58 -0000

Shwmae Adrian,

You wrote:

> [snip]
>
>> Politics! OK - How about we add to either s9.1.1 or s9.2 something like:
>
> I don't think it is politics at all, and I don't really like that Huub
> referenced this as IETF and ITU-T since both documents are IETF standards track
> work.

Please excuse me for giving the impression that this draft is an ITU-T
document. You are absolutely right that both are IETF documents.
I should have used "PSC in ITU-T mode" to refer to this draft.

> There are some people who want to deploy one set of options (the empty set) and
> they have an RFC.
> There is another set of people who want to deploy a different set of options
> (all 5 of them) and they will have this RFC.

Indeed.

>>     Only combinations of capabilities specified by a mode are allowed.
>>     Capability TLVs with other combinations will be treated as invalid
>>     PSC messages.
>
> But this is not true.
>
> What we have is:
> A node knows which options it supports, and those options are expressed as
> bundles (modes).
> A node that tries to communicate with you must offer a set of options (a mode).
> Either you support the mode or you don't.
> If you support it, off you go.
> If you don't support it, you reject the message saying "unsupported" as
> described in this document.

Again: correct. I tried to simplify too much and used the wrong word
(invalid, instead of unsupported).

> The message that offers a different set of options (i.e. a different mode) is
> not invalid, it is just that you don't understand it. You can't accept it
> because you don't know how to behave in that mode.

Indeed (not supported).

> OTOH, when someone writes the new RFC describing that mode, you might enhance
> your implementation to support it as well.

Yes, and initially advertise your own capabilities, compare to the
capabilities received from the far-end and attempt to converge.

> (Hint: it really helps to think in modes. A mode is expressed as a bit-flag with
> plenty-bits of which five currently have meaning.)
>
> I agree with you that there is some distinction to be made between "invalid
> message" and "protocol error".
> But "no valid message" does not mean "protocol error" or "invalid message" was
> received. It is a composite of possibilities that reflects the negation of
> receiving a message that was small and perfectly formed.

OK.

Cheers, Huub.




-- 
*****************************************************************
               è¯·è®°ä½�ï¼Œä½ æ˜¯ç‹¬ä¸€æ— äºŒçš„ï¼Œå°±åƒ�å…¶ä»–æ¯�ä¸€ä¸ªäººä¸€æ ·


From nobody Thu Feb 27 08:03:10 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 692EA1A038C for <gen-art@ietfa.amsl.com>; Thu, 27 Feb 2014 08:03:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 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.547, 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 78snEhXdMrJx for <gen-art@ietfa.amsl.com>; Thu, 27 Feb 2014 08:02:56 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2A7921A0382 for <gen-art@ietf.org>; Thu, 27 Feb 2014 08:02:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2014; q=dns/txt; s=iport; t=1393516973; x=1394726573; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Ja4IZIyqBnErKK/DvDxlTP/VEzret3JWIm9DuXnHJzM=; b=LqP/JtVAKCAFc9i7RnDr9oWC1FFWU9hoFGXiiKiG9NF00Zhs+TvhE1N+ FlJnM91qmU+RoxgQU+hTJGsd4ktB4oozmcMETgzj177H1nzWNfFBLlZOU 65wrB3RY2rwOMXlQpYXNQonknvahh6xohjrOmz2UeKdP4srA/q6Ws4HNJ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjoFANNgD1OQ/khN/2dsb2JhbABagwY7wWKBGxZ0giYBAQQ4QAEQCxQNFg8JAwIBAgFFBgEMAQcBAYd1DcpxF4xkgXEHhDcBA5g4gTKFGItggy08
X-IronPort-AV: E=Sophos;i="4.97,555,1389744000";  d="scan'208";a="5666228"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-2.cisco.com with ESMTP; 27 Feb 2014 16:02:51 +0000
Received: from [10.61.205.235] ([10.61.205.235]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s1RG2pNr021437; Thu, 27 Feb 2014 16:02:51 GMT
Message-ID: <530F38BE.3030508@cisco.com>
Date: Thu, 27 Feb 2014 13:08:14 +0000
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>, draft-ietf-radext-ieee802ext.all@tools.ietf.org
References: <8C9EE7F2-AA3D-482A-B469-4A147D143954@nostrum.com>
In-Reply-To: <8C9EE7F2-AA3D-482A-B469-4A147D143954@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/JJehG786udmMm1xXIoRQ4ehtFlk
Cc: "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-ieee802ext-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 16:03:02 -0000

Dear authors,

Can you please follow up on that one.

Regards, Benoit
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-radext-ieee802ext-10
> Reviewer: Ben Campbell
> Review Date: 2014-01-31
> IETF LC End Date: 2014-02-04
>
> Summary: This draft is almost ready for publication as a standards track RFC. I have a small number of minor comments that may be worth considering prior to publication.
>
> Major issues: None
>
> Minor issues:
>
> -- 2.1, last paragraph:
>
> Does the last sentence imply Allowed-Called-Station-Id actually should (or SHOULD) not be used in non-wireless scenarios? (I note that the Network-Id-Name section talks about how 802.1X NID-Names should not be included in Called-Station-Id, but rather put in Network-Id-Name. Does that apply here as well?
>
> -- 2.2, last paragraph: "Since a NAS will typically only include a EAP-Key-Name Attribute in an Access-Request in situations where the Attribute is required to provision service, if an EAP-Key-Name Attribute is included in an Access-Request but is not present in the Access-Accept, the NAS SHOULD treat the Access-Accept as though it were an Access-Reject. "
>
> Is there a backwards compatibility issue? What if a NAS sends the field to a server that doesn't implement this draft? Is there an assumption that a NAS that supports this draft will only work with a server that also supports it?
>
> Or more to the point, is the "...typically only include...where required..." strong enough to require a normative SHOULD? Seems like this would discourage the inclusion of EAP-Key-Name in the non-typical case of it _not_ being required. Is that the intent?
>
> Nits/editorial comments:
>
> -- section 2.8:
>
> It might be worth expanding "EAPoL"
>
>
>
> .
>


From nobody Thu Feb 27 14:56:33 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 010621A02A6 for <gen-art@ietfa.amsl.com>; Thu, 27 Feb 2014 14:56:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] 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 RfJT3FyPj5rg for <gen-art@ietfa.amsl.com>; Thu, 27 Feb 2014 14:56:30 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 786581A0257 for <gen-art@ietf.org>; Thu, 27 Feb 2014 14:56:30 -0800 (PST)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s1RMuSYE047615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <gen-art@ietf.org>; Thu, 27 Feb 2014 16:56:28 -0600 (CST) (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: <530FC29B.6010103@nostrum.com>
Date: Thu, 27 Feb 2014 16:56:27 -0600
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.3.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/Pl9bdq8Zb6uJ2QDC361hbFopCn0
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2014-02-27
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?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, 27 Feb 2014 22:56:32 -0000

Hi all,

The following reviewers have assignments:

Reviewer          LC end       Draft
---------------------------------------------------------------------
Suresh Krishnan   2014-03-12   draft-ietf-ipsecme-ikev2-fragmentation-05


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

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:



From nobody Thu Feb 27 16:43:30 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 CC3B31A0186 for <gen-art@ietfa.amsl.com>; Thu, 27 Feb 2014 16:43:28 -0800 (PST)
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 GBEmEj2wi5OM for <gen-art@ietfa.amsl.com>; Thu, 27 Feb 2014 16:43:26 -0800 (PST)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 920031A022C for <gen-art@ietf.org>; Thu, 27 Feb 2014 16:43:26 -0800 (PST)
Received: by mail-we0-f174.google.com with SMTP id t60so7361wes.5 for <gen-art@ietf.org>; Thu, 27 Feb 2014 16:43:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=qliqqURKydUFEPqkZLa/pp9lOdPfeqQYRze8NQX1xUE=; b=edMT4XP8DaPTNGkTwjcWaz2wiFUFOmMTYTabwF29c26B1IcLz8SFXTm8i+ivc9BVO9 YlTFSkiVa+9tpwvCzlmXlGCbTuwUrlF03fIui7vKjHgxAuq4XXuPCy7vStMD15dxJlBE lwLNsTJyqgMAdGuTy9AM9JrlDhGdmFuRrwpSZh1zpEpPo+HJhJQKc2szTtY1Q2vobsqv hnhI3xxn7MwhH32de5/8pCVkSNK1JFGuByiodEnF5d6zeKVnLIaXEf2F++kY6aGOv9Vs D1zOqXwpokNEMEfbTz/07LI5xPklMbPbLkESoLFOLM23eUPtUOm0+vdnkziv6wJ4Zl2i PINw==
MIME-Version: 1.0
X-Received: by 10.194.110.41 with SMTP id hx9mr16480wjb.28.1393548204478; Thu, 27 Feb 2014 16:43:24 -0800 (PST)
Received: by 10.227.10.196 with HTTP; Thu, 27 Feb 2014 16:43:24 -0800 (PST)
Date: Thu, 27 Feb 2014 16:43:24 -0800
Message-ID: <CABkgnnVVQCAz=ixeR04rc75Vc-rL2JFQcjT0-hX_UCL-c=FGjQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, draft-drage-sipping-rfc3455bis.all@tools.ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/OUbbpVn13uQ8a5JhfqbJnmkg1JM
Subject: [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, 28 Feb 2014 00:43:29 -0000

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

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

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

Document: draft-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.

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.

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

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.

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.

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.

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.

Nits/editorial comments:

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

S1, S3 It looks like a few characters are missing from these sections:
"trust.These", "environment The", "[RFC3455]   This"

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)

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?


From nobody Fri Feb 28 22:05:39 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 10C541A0642 for <gen-art@ietfa.amsl.com>; Fri, 28 Feb 2014 22:05:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rq6O8IK4u07s for <gen-art@ietfa.amsl.com>; Fri, 28 Feb 2014 22:05:33 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 753011A042E for <gen-art@ietf.org>; Fri, 28 Feb 2014 22:05:32 -0800 (PST)
X-AuditID: c6180641-b7f2f8e000002cdc-96-531178aadef9
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id B0.E6.11484.AA871135; Sat,  1 Mar 2014 07:05:30 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0387.000; Sat, 1 Mar 2014 01:05:29 -0500
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-ecrit-trustworthy-location.all@tools.ietf.org" <draft-ietf-ecrit-trustworthy-location.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call draft-ietf-ecrit-trustworthy-location-08
Thread-Index: Ac81E9VNoIUSDSUdRiWQlrxlIFVyrw==
Date: Sat, 1 Mar 2014 06:05:27 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A32D7F18E@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.12]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A32D7F18Eeusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyuXRPlO6qCsFggz+7rS1WTjzEZnH11WcW ByaPJUt+Mnl8ufyZLYApissmJTUnsyy1SN8ugSujby9LwUubis7OdSwNjHNNuxg5OSQETCQO XHrFCmGLSVy4t56ti5GLQ0jgCKPEhb8zoZxljBI73sxnBqliE7CQ2P77OStIQkRgCaPE0jsP gBwODmEBZ4l5L7VAakQEPCT+v9rMBGHrSaz68x5sA4uAisSqL90sIDavgK9E//13YHFGoM3f T60Bq2cWEJe49WQ+E8RFAhJL9pxnhrBFJV4+/gd1qZLEnNfXmCHq8yVOHN3FCjFTUOLkzCcs ExiFZiEZNQtJ2SwkZRBxHYkFuz+xQdjaEssWvmaGsc8ceMyELL6AkX0VI0dpcWpZbrqR4SZG YDQck2Bz3MG44JPlIUZpDhYlcd4vb52DhATSE0tSs1NTC1KL4otKc1KLDzEycXBKNTDyR8mL VfGvDjuX3r3ssrb5emMJBtsly/jeHVi8PsklOfNr743M9yx7eRWOzvM+U758v/PkNe/THsz4 63FLxP8Yy4bfqpZKbPfNPQIXvepMvXx/I5O5+t7ZLbGS110+8/IJhu94KxNmW3n9tK/1zzns jR0bDhZsFYg+uU984hHD3mDutWtOl1gqsRRnJBpqMRcVJwIA48Vf2FQCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/dSPDDW_dM_23t4csC8-TQzvO86k
Subject: [Gen-art] Gen-ART Last Call draft-ietf-ecrit-trustworthy-location-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Mar 2014 06:05:37 -0000

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

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

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

Document: draft-ietf-ecrit-trustworthy-location-08
Reviewer: Meral Shirazipour
Review Date: 2013-02-28
IETF LC End Date:  2014-02-28
IESG Telechat date: NA


Summary:
This draft is ready to be published as Informational RFC but I have a few c=
omments.


Nits/editorial comments:
-[page 3] "an prank emergency"--a-->"a prank emergency"
-[page 3] "PSAP"---->"Public-safety answering point (PSAP)" (then remove Pu=
blic safety answering point from next occurrence of PSAP in text) on the sa=
me page.
General comment:
AIP, PIDF, VSP, VESA, VPC and ERDB  please spell out at 'first use'
-[page 5] "one-off basis" ---->"on-off basis" ?
-[page 14] "attacker continue o learn"--typo-->"attacker continue to learn"
-[page 16] "on the Internet"-->"in the Internet"
-[page 19]
" In some countries, regulators may not
   require the authenticated identity of the emergency caller, as is
   true for PSTN-based emergency calls placed from pay phones or SIM-
   less cell phones today.
"
I am not an expert but I doubt today only SIM-less cards can be tracked.

-[page 19]
"Location theft requires the attacker to be in proximity to the location to=
 spoofed,.."
--->"...being spoofed"?

-Reference [TASMANIA] is no longer a valid link

-Although emergency prank calls are probably the most valid use case, can t=
his method be applied to other use cases where location information needs t=
o be
validated? If so it would be good to mention this in the draft, at least br=
iefly.

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

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or background on Gen-ART, please see the FAQ at
<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a> .<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-ecrit-trustworthy-location-08<o=
:p></o:p></p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2013-02-28<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date:&nbsp; 2014-02-28<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: NA<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary:<o:p></o:p></p>
<p class=3D"MsoNormal">This draft is ready to be published as Informational=
 RFC but I have a few comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal">-[page 3] &quot;an prank emergency&quot;--a--&gt;&qu=
ot;a prank emergency&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[page 3] &quot;PSAP&quot;----&gt;&quot;Public-safet=
y answering point (PSAP)&quot; (then remove Public safety answering point f=
rom next occurrence of PSAP in text) on the same page.<o:p></o:p></p>
<p class=3D"MsoNormal">General comment:<o:p></o:p></p>
<p class=3D"MsoNormal">AIP, PIDF, VSP, VESA, VPC and ERDB&nbsp; please spel=
l out at 'first use'<o:p></o:p></p>
<p class=3D"MsoNormal">-[page 5] &quot;one-off basis&quot; ----&gt;&quot;on=
-off basis&quot; ?<o:p></o:p></p>
<p class=3D"MsoNormal">-[page 14] &quot;attacker continue o learn&quot;--ty=
po--&gt;&quot;attacker continue to learn&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[page 16] &quot;on the Internet&quot;--&gt;&quot;in=
 the Internet&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">-[page 19] <o:p></o:p></p>
<p class=3D"MsoNormal">&quot; In some countries, regulators may not<o:p></o=
:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; require the authenticated identity of t=
he emergency caller, as is<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; true for PSTN-based emergency calls pla=
ced from pay phones or SIM-<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; less cell phones today.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">I am not an expert but I doubt today only SIM-less c=
ards can be tracked.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-[page 19]<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;Location theft requires the attacker to be in =
proximity to the location to spoofed,..&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">---&gt;&quot;...being spoofed&quot;?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-Reference [TASMANIA] is no longer a valid link<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">-Although emergency prank calls are probably the mos=
t valid use case, can this method be applied to other use cases where locat=
ion information needs to be<o:p></o:p></p>
<p class=3D"MsoNormal">validated? If so it would be good to mention this in=
 the draft, at least briefly.<o:p></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_ABCAA4EF18F17B4FB619EA93DEF7939A32D7F18Eeusaamb107erics_--


From nobody Fri Feb 28 23:38:10 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 D972C1A064A; Fri, 28 Feb 2014 23:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.4
X-Spam-Level: 
X-Spam-Status: No, score=0.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_LIST=2.3, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZGaLgYuI1Ao8; Fri, 28 Feb 2014 23:38:06 -0800 (PST)
Received: from p3plsmtpa08-09.prod.phx3.secureserver.net (p3plsmtpa08-09.prod.phx3.secureserver.net [173.201.193.110]) by ietfa.amsl.com (Postfix) with ESMTP id 7A1361A0642; Fri, 28 Feb 2014 23:38:06 -0800 (PST)
Received: from spectre ([173.8.184.78]) by p3plsmtpa08-09.prod.phx3.secureserver.net with  id Y7e21n00C1huGat017e2iJ; Sat, 01 Mar 2014 00:38:04 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-fairhurst-ipdvb-ule-iana.all@tools.ietf.org>
Date: Fri, 28 Feb 2014 23:38:09 -0800
Message-ID: <094c01cf3521$3246d710$96d48530$@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: Ac81HgXbbOG0QnGwTUW8b/mclBzGGg==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/gen-art/sKFnuyMRUaT_2Eiw08Vj5fljIBg
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-fairhurst-ipdvb-ule-iana-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Mar 2014 07:38:08 -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-fairhurst-ipdvb-ule-iana-05
Reviewer: Peter Yee
Review Date: February-27-2014
IETF LC End Date: February-28-2014
IESG Telechat date: TBD

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

This document updates the IANA rules for maintenance of the ULE Next-Header
registry, as originally specified in RFC 4326.


Nits:

General nits:

Throughout the document, make all references to the registry in question
read "Next-Header registry" for consistency with RFC 4326, except in titles
or section headers where each word would be capitalized.


Specific nits:

Page 1, Title: consider inserting "Next-Header" between "ULE" and "Registry"
since that's the registry in question.

Page 1, Abstract, 2nd sentence: change "codepoints" to "code points" to
align with RFC 4259 and ATSC usage.

Page 3, Section 2.1, 1st sentence of the 1st and second paragraphs: you
refer to Mandatory Extension Headers and Optional Extension Headers
registries.  From RFC 4326, these are really subdivisions of the single
Next-Header registry.  You might want to rephrase those sentences to reflect
that you are not defining two registries.

Page 3, Section 2.1, 1st paragraph, 3rd sentence: Should that be "or the
specified protocol" or "of the specified protocol"?  I wasn't certain from
the context in RFC 4326 how the type values are used.

Page 3, Section 3, 1st paragraph, 2nd sentence: replace "these" with "them".

Page 5, 1st partial paragraph, last sentence: change "can not" to "cannot";
change "guarenteed" to "guaranteed".

Page 5, 1st full paragraph, last sentence: insert "is" between "that" and
"to".  

Page 5, Section 4, 1st paragraph: insert "an" between "record" and
"additional"

Section 8: as this section will be removed, no corrections are noted.

		-Peter Yee



