
From mahoney@nostrum.com  Tue May  1 15:40:10 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A694221E8055 for <gen-art@ietfa.amsl.com>; Tue,  1 May 2012 15:40:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yy5+YAAJAQrJ for <gen-art@ietfa.amsl.com>; Tue,  1 May 2012 15:40:10 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9D84D21E8050 for <gen-art@ietf.org>; Tue,  1 May 2012 15:40:09 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-244-61-199.dllstx.fios.verizon.net [71.244.61.199]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q41Me5ex004088 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Tue, 1 May 2012 17:40:06 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FA06645.2070906@nostrum.com>
Date: Tue, 01 May 2012 17:40:05 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 71.244.61.199 is authenticated by a trusted mechanism)
Subject: [Gen-art] A new batch of IETF LC reviews - 2012-05-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 22:40:10 -0000

Hi all,

The following reviewers have assignments:

Reviewer               LC end       Draft

Allyn Romanow        2012-05-28     draft-polk-ipr-disclosure-03

Ben Campbell         2012-05-14     draft-ietf-ccamp-assoc-info-03

David Black          2012-05-10     draft-ietf-codec-opus-12


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

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From mahoney@nostrum.com  Thu May  3 16:52:59 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C56321F8740 for <gen-art@ietfa.amsl.com>; Thu,  3 May 2012 16:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GHaXLBYrKbZZ for <gen-art@ietfa.amsl.com>; Thu,  3 May 2012 16:52:59 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 01AE621F873E for <gen-art@ietf.org>; Thu,  3 May 2012 16:52:58 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-244-61-199.dllstx.fios.verizon.net [71.244.61.199]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q43Nqo8l064649 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 3 May 2012 18:52:51 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FA31A52.3070004@nostrum.com>
Date: Thu, 03 May 2012 18:52:50 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 71.244.61.199 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-05-10 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 May 2012 23:52:59 -0000

Hi all,

The following reviewers have assignments:

Reviewer:              LC end:      Draft:

Brian Carpenter        2011-11-03   
draft-sprecher-mpls-tp-oam-considerations-03

Christer Holmberg      2012-03-21   draft-betts-itu-oam-ach-code-point-04

Miguel Garcia          2012-04-06   
draft-ietf-roll-minrank-hysteresis-of-10

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

Vijay Gurbani          2012-04-11   draft-ietf-ippm-reporting-metrics-08
Vijay Gurbani          2012-05-07   
draft-ietf-appsawg-mime-default-charset-03
Vijay Gurbani          2012-04-03   draft-ietf-avtext-rams-scenarios-04 *

Wassim Haddad          2012-03-23   draft-ietf-mpls-tp-oam-analysis-09
Wassim Haddad          2012-04-03   draft-ietf-avtext-splicing-for-rtp-07
Wassim Haddad          2012-03-23   draft-ietf-mpls-tp-oam-analysis-09

* Draft already reviewed


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

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

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

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

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From brian.e.carpenter@gmail.com  Fri May  4 00:47:22 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 586E021F8686 for <gen-art@ietfa.amsl.com>; Fri,  4 May 2012 00:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.551
X-Spam-Level: 
X-Spam-Status: No, score=-101.551 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id thfEHDDKajVx for <gen-art@ietfa.amsl.com>; Fri,  4 May 2012 00:47:20 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 38E3521F8630 for <gen-art@ietf.org>; Fri,  4 May 2012 00:47:20 -0700 (PDT)
Received: by eabd1 with SMTP id d1so310622eab.31 for <gen-art@ietf.org>; Fri, 04 May 2012 00:47:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=/Bk4emxt2g3VYZwCPSCUXWqC8riRDwYj9XXkpnQL+Dg=; b=Kn7g/+9m5VpOGrc9pWOljF3K9U0osIxplF0J60A4Bvof9wbbSv2hYNMQOFIif3Oouc Jl2BluX2U3YI72eTXzLLk+zCkMa1wzmgSK+6LxUCtTXpauHUDDB6nyGe0a9XKq7j8O9Q rXuV+kAsB5OkB/V1Y9G6DYDXQZjE2tOXchENHuojdu276oTzWDFxAjj73qPJAQIBvFPN z7ULAV7Pf7iC7P8dJy0Gmwq3qiqnz1o1Vyykw2WaFGEWHYUTCVE1Kz9B/HeQXyTc++/H d00YoZ/9qGONr3AL6zSOWbfY3KuNDWu7Yz1cPBYVkJo23NtEJ/ePpoVoY5eYiVgffZJD UwRw==
Received: by 10.14.47.207 with SMTP id t55mr965319eeb.70.1336117639177; Fri, 04 May 2012 00:47:19 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-144.as13285.net. [2.102.217.144]) by mx.google.com with ESMTPS id e56sm37364683eea.11.2012.05.04.00.47.17 (version=SSLv3 cipher=OTHER); Fri, 04 May 2012 00:47:18 -0700 (PDT)
Message-ID: <4FA38981.9080000@gmail.com>
Date: Fri, 04 May 2012 08:47:13 +0100
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-sprecher-mpls-tp-oam-considerations.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------060806080503080509020209"
Subject: [Gen-art] Gen-ART telechat review of draft-sprecher-mpls-tp-oam-considerations-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2012 07:47:22 -0000

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

Please see attached review.

--------------060806080503080509020209
Content-Type: text/plain;
 name="draft-sprecher-mpls-tp-oam-considerations-03-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename*0="draft-sprecher-mpls-tp-oam-considerations-03-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9uIGZyb20geW91ciBkb2N1bWVudCBzaGVwaGVy
ZA0Kb3IgQUQgYmVmb3JlIHBvc3RpbmcgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQuIA0K
DQpEb2N1bWVudDogZHJhZnQtc3ByZWNoZXItbXBscy10cC1vYW0tY29uc2lkZXJhdGlvbnMt
MDMudHh0DQpSZXZpZXdlcjogQnJpYW4gQ2FycGVudGVyDQpSZXZpZXcgRGF0ZTogMjAxMi0w
NS0wNA0KSUVURiBMQyBFbmQgRGF0ZTogMjAxMS0xMC0yNA0KSUVTRyBUZWxlY2hhdCBkYXRl
OiAyMDEyLTA1LTEwDQoNClN1bW1hcnk6ICBSZWFkeQ0KLS0tLS0tLS0NCg0KQ29tbWVudHM6
DQotLS0tLS0tLS0NCg0KTXkgTGFzdCBDYWxsIGNvbW1lbnRzIGhhdmUgYmVlbiBhZGRyZXNz
ZWQsIGFuZCB0aGUgZG9jdW1lbnQgbm93IHJlYWRzDQptb3JlIGxvZ2ljYWxseSwgZHVlIHRv
IG1hdGVyaWFsIGJlaW5nIG1vdmVkIHRvIHRoZSBhcHBlbmRpY2VzLg0KDQpOaXQ6DQotLS0t
DQoNClRoZXJlIGlzIGR1cGxpY2F0ZWQgdGV4dCBpbiBzZWN0aW9uIDEuMjoNCg0KICAgYmUg
bWFuYWdlZCB1c2luZyB0b29scyB3aXRoIHNpbWlsYXIgbG9vayBhbmQgZmVlbC4gIFRoZSBy
ZXF1aXJlbWVudHMNCiAgIHNwZWNpZmljYXRpb25zIFtSRkM1NjU0XSBhbmQgW1JGQzU4NjBd
IHNwZWNpZmljYXRpb25zIFtSRkM1NjU0XSBhbmQNCiAgIFtSRkM1ODYwXSBjYXB0dXJlIHRo
ZSBlc3NlbnRpYWwgaXNzdWVzIHRoYXQgbXVzdCBiZSByZXNvbHZlZCB0byBhbGxvdw0KDQoN
Cg0K
--------------060806080503080509020209--

From alexey.melnikov@isode.com  Sat May  5 10:59:01 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDBFF21F84DC; Sat,  5 May 2012 10:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.22
X-Spam-Level: 
X-Spam-Status: No, score=-101.22 tagged_above=-999 required=5 tests=[AWL=-0.018, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UAho01lU9z8U; Sat,  5 May 2012 10:59:01 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id D5A5621F85E1; Sat,  5 May 2012 10:59:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1336240739; d=isode.com; s=selector; i=@isode.com; bh=z0FQpR/wyCzitOypN2B4QaTPk+OJW9jO4VXIVPzCu2g=; 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=DUTtmrOzBl2xHG9dpWUz/DbmbOQbwCp922yj7YkXbNdM+ow3S7apkdsdrI4hP5dLWfsDac 73PEmLH8KYFi2WPNvVAAL46/cpx27o2OLeHCGqUInE521HO/4LLYeZM1VRUiI+CU2GMFp3 LLDLHOsQYNPH3ACAF/Yns8iTT/L6UOE=;
Received: from [188.28.202.123] (188.28.202.123.threembb.co.uk [188.28.202.123])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T6VqYgB=g4tZ@rufus.isode.com>; Sat, 5 May 2012 18:58:59 +0100
References: <CADhm99oKj8Trcx5o37kg=xZ85ut1iT4xcog+mBO_GP1T4Xnxqg@mail.gmail.com> <01b401cd13d3$322bc950$96835bf0$@isode.com> <3B677B5C-CC21-4252-B343-C6C4A57BBE5B@isode.com> <021901cd1447$39b550f0$ad1ff2d0$@isode.com> <24541053-C0B1-47B3-B866-19E0909BB176@isode.com> <021f01cd1491$13104820$3930d860$@isode.com>
In-Reply-To: <021f01cd1491$13104820$3930d860$@isode.com>
Message-Id: <E30B4753-60B8-470B-A1DF-E2ABD31D62E0@isode.com>
X-Mailer: iPad Mail (9B176)
From: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Sat, 5 May 2012 18:58:51 +0100
To: "Gen-art@ietf.org" <Gen-art@ietf.org>, "draft-ietf-netext-access-network-option.all@tools.ietf.org" <draft-ietf-netext-access-network-option.all@tools.ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=Apple-Mail-0EA4160C-1829-4002-953A-92DA5766DA08
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org" <iesg@ietf.org>
Subject: [Gen-art] Gen-Art review of draft-ietf-netext-access-network-option-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 May 2012 17:59:02 -0000

--Apple-Mail-0EA4160C-1829-4002-953A-92DA5766DA08
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

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

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

Document: draft-ietf-netext-access-network-option-10.txt
Reviewer: Alexey Melnikov
Review Date: 5 May 2012
IETF LC End Date: 9 May 2012
IESG Telechat date: Unknown

Summary: This draft is ready as a Proposed Standard

Major issues: none

Minor issues:

Minor: [ANI] and [TS23003] seem to be Normative (as per their use in 3.1.1)

Nits/editorials:

1.  Introduction

   This document defines a new mobility option, the Access Network
   Identifier (ANI) option and its sub-options for Proxy Mobile IPv6,
   that can be used by the mobile access gateway to signal the access
   network information to the local mobility anchor.  The specific
   details on how the local mobility anchor uses this information are
   out-of-scope for this document.  These mobility options are optional
   and are not mandatory for the Proxy Mobile IPv6 protocol.

Nit: Last sentence: "optional" and "not mandatory" are the same thing on my b=
ook.

Strictly speaking PEN numbers are not limited to 4 bytes. However you have a=
 registry for types of identifiers, so a new value can be allocated for bigg=
er-than-4-bytes PENs.=

--Apple-Mail-0EA4160C-1829-4002-953A-92DA5766DA08
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body bgcolor=3D"#FFFFFF"><div><div></div>I am the assign=
ed Gen-ART reviewer for this draft. For background on<br><span>Gen-ART, plea=
se see the FAQ at</span><br><span>&lt;<a href=3D"http://wiki.tools.ietf.org/=
area/gen/trac/wiki/GenArtfaq" x-apple-data-detectors=3D"true" x-apple-data-d=
etectors-result=3D"0">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfa=
q</a>&gt;.</span><br><span></span><br><span>Please resolve these comments al=
ong with any other Last Call comments</span><br><span>you may receive.</span=
></div><div><span style=3D"font-family: Noteworthy; font-size: large; line-h=
eight: 24px; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webki=
t-composition-fill-color: rgba(130, 98, 83, 0.0898438); -webkit-composition-=
frame-color: rgba(191, 107, 82, 0.496094); "><font class=3D"Apple-style-span=
" face=3D"Helvetica"><span class=3D"Apple-style-span" style=3D"font-size: 17=
px; line-height: normal; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.300=
781); -webkit-composition-fill-color: rgba(175, 192, 227, 0.234375); -webkit=
-composition-frame-color: rgba(77, 128, 180, 0.234375);"><br></span></font><=
/span><span>Document:&nbsp;</span><span class=3D"Apple-style-span" style=3D"=
font-family: Noteworthy; font-size: 18px; font-weight: bold; line-height: 24=
px; -webkit-composition-fill-color: rgba(130, 98, 83, 0.0898438); -webkit-co=
mposition-frame-color: rgba(191, 107, 82, 0.496094); -webkit-tap-highlight-c=
olor: rgba(26, 26, 26, 0.292969); ">draft-ietf-netext-access-network-option-=
10.txt</span><br><span>Reviewer: Alexey Melnikov</span><br><span>Review Date=
: 5 May 2012</span><br><span>IETF LC End Date: 9 May 2012</span><br><span>IE=
SG Telechat date:&nbsp;Unknown</span><br><span></span><br><span>Summary: Thi=
s draft is ready as a Proposed Standard</span><br><span></span><br><span>Maj=
or issues: none</span></div><div><br><span>Minor issues:</span><div><br></di=
v><span class=3D"Apple-style-span" style=3D"font-family: Noteworthy; font-si=
ze: 18px; font-weight: bold; line-height: 24px; -webkit-tap-highlight-color:=
 rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(130, 98, 8=
3, 0.0898438); -webkit-composition-frame-color: rgba(191, 107, 82, 0.496094)=
; "><div>Minor:&nbsp;<span class=3D"Apple-style-span" style=3D"-webkit-compo=
sition-fill-color: rgba(130, 98, 83, 0.0898438); -webkit-tap-highlight-color=
: rgba(26, 26, 26, 0.292969); ">[ANI] and [TS23003] seem to be Normative (as=
 per their use in 3.1.1)</span></div></span><div><span></span><br><span>Nits=
/editorials:</span><br><span></span><br></div><span class=3D"Apple-style-spa=
n" style=3D"font-family: Noteworthy; font-size: 18px; font-weight: bold; lin=
e-height: 24px; -webkit-composition-fill-color: rgba(130, 98, 83, 0.09375); -=
webkit-composition-frame-color: rgba(191, 107, 82, 0.496094); -webkit-tap-hi=
ghlight-color: rgba(26, 26, 26, 0.296875); "><div>1. &nbsp;Introduction</div=
><div><br></div><div>&nbsp; &nbsp;This document defines a new mobility optio=
n, the Access Network</div><div>&nbsp; &nbsp;Identifier (ANI) option and its=
 sub-options for Proxy Mobile IPv6,</div><div>&nbsp; &nbsp;that can be used b=
y the mobile access gateway to signal the access</div><div>&nbsp; &nbsp;netw=
ork information to the local mobility anchor. &nbsp;The specific</div><div>&=
nbsp; &nbsp;details on how the local mobility anchor uses this information a=
re</div><div>&nbsp; &nbsp;out-of-scope for this document. &nbsp;These mobili=
ty options are optional</div><div>&nbsp; &nbsp;and are not mandatory for the=
 Proxy Mobile IPv6 protocol.</div><div><br></div><div>Nit: Last sentence: "o=
ptional" and "not mandatory" are the same thing on my book.</div><div><br></=
div><div>Strictly speaking PEN numbers are not limited to 4 bytes. However y=
ou have a registry for types of identifiers, so a new value can be allocated=
 for bigger-than-4-bytes PENs.</div></span></div></body></html>=

--Apple-Mail-0EA4160C-1829-4002-953A-92DA5766DA08--

From rgcole01@comcast.net  Sun May  6 07:41:16 2012
Return-Path: <rgcole01@comcast.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 898A621F8491 for <gen-art@ietfa.amsl.com>; Sun,  6 May 2012 07:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yqf0wzBz8OGp for <gen-art@ietfa.amsl.com>; Sun,  6 May 2012 07:41:14 -0700 (PDT)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6489721F846F for <gen-art@ietf.org>; Sun,  6 May 2012 07:41:14 -0700 (PDT)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta10.westchester.pa.mail.comcast.net with comcast id 6ePk1j0010EZKEL5AehEYa; Sun, 06 May 2012 14:41:14 +0000
Received: from [10.0.1.195] ([68.55.94.27]) by omta01.westchester.pa.mail.comcast.net with comcast id 6ehE1j0080bRkG43MehExu; Sun, 06 May 2012 14:41:14 +0000
From: Robert G Cole <rgcole01@comcast.net>
To: jmh@joelhalpern.com
In-Reply-To: <CAK=bVC-oB-7uwGw4TWJYO0YD4xbV-RjGSq90G2EU=agbMBLQXg@mail.gmail.com>
References: <4F7E279C.3030707@nostrum.com> <4F7F12CA.9010009@joelhalpern.com> <CAK=bVC-oB-7uwGw4TWJYO0YD4xbV-RjGSq90G2EU=agbMBLQXg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Sun, 06 May 2012 10:41:11 -0400
Message-ID: <1336315271.2040.6.camel@chapman>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sun, 06 May 2012 08:33:00 -0700
Cc: robert.g.cole@us.army.mil, gen-art@ietf.org, manet@ietf.org, Ulrich Herberg <ulrich@herberg.name>, sratliff@cisco.com
Subject: Re: [Gen-art] Fwd: [manet]  review: draft-ietf-manet-nhdp-mib-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 May 2012 14:41:16 -0000

Joel,

Ulrich and I have updated the NHDP-MIB module to address your questions
and suggestions.  We hope these changes are satisfactory?

Thanks,

Bob and Ulrich

----- Original Message -----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
Sent: Sunday, May 06, 2012 02:29 PM
To: manet-chairs@tools.ietf.org <manet-chairs@tools.ietf.org>;
draft-ietf-manet-nhdp-mib@tools.ietf.org <draft-ietf-manet-nhdp-mib@tools.ietf.org>; adrian@olddog.co.uk <adrian@olddog.co.uk>
Subject: New Version Notification - draft-ietf-manet-nhdp-mib-13.txt

New version (-13) has been submitted for
draft-ietf-manet-nhdp-mib-13.txt:
http://www.ietf.org/internet-drafts/draft-ietf-manet-nhdp-mib-13.txt

Sub state has been changed to AD Followup from Revised ID Needed


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-mib/

Diff from previous version:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-manet-nhdp-mib-13

IETF Secretariat.


On Mon, 2012-04-23 at 11:14 -0700, Ulrich Herberg wrote:



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



From jouni.nospam@gmail.com  Sun May  6 12:58:59 2012
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54EB421F8549; Sun,  6 May 2012 12:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyYtqiaC1HuI; Sun,  6 May 2012 12:58:58 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 62C2A21F84DF; Sun,  6 May 2012 12:58:58 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so3017735wgb.13 for <multiple recipients>; Sun, 06 May 2012 12:58:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=n5/9AYJo7nobC146FVKsqZdRH0862yyQbSeEnTbjgK0=; b=FlhSvRbpCJzN6ATFOElGhTCGoQR54ky8gk6nSn7rQrvdHzUa+OMrmzr37QJ6prJWBH n+08vwcBrpo+2D4WnbYcs0Hl5lrCdUlC6DNemYG/YL4b3y14wJTfgagMVZq1VhVJ8m83 Z2zVGoTrUqi3njXW2BqQopkJUEsE1i1tG1e+8pwNMWC/y8OYlx9GK+Xenzx4JCwIng2r Q6Fl1/sfsar01YEPHb1IDgJw9ns032DUGXtDuAiHAGbtOgLMw0pEVqBfNlOZI1zsvcdJ oXc5g4l+tRmS4PTrlBlSBP132GhiLc/hx9nENix4t4sUXm8OUOhLScIToIxCqQzXZfUh zhPA==
Received: by 10.180.77.4 with SMTP id o4mr29482396wiw.17.1336334337517; Sun, 06 May 2012 12:58:57 -0700 (PDT)
Received: from [188.117.15.106] ([188.117.15.106]) by mx.google.com with ESMTPS id k6sm16524411wiy.7.2012.05.06.12.58.53 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 06 May 2012 12:58:55 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <E30B4753-60B8-470B-A1DF-E2ABD31D62E0@isode.com>
Date: Sun, 6 May 2012 22:58:52 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <47440497-5003-4067-97D5-5426099AFECC@gmail.com>
References: <CADhm99oKj8Trcx5o37kg=xZ85ut1iT4xcog+mBO_GP1T4Xnxqg@mail.gmail.com> <01b401cd13d3$322bc950$96835bf0$@isode.com> <3B677B5C-CC21-4252-B343-C6C4A57BBE5B@isode.com> <021901cd1447$39b550f0$ad1ff2d0$@isode.com> <24541053-C0B1-47B3-B866-19E0909BB176@isode.com> <021f01cd1491$13104820$3930d860$@isode.com> <E30B4753-60B8-470B-A1DF-E2ABD31D62E0@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1084)
Cc: "Gen-art@ietf.org" <Gen-art@ietf.org>, "draft-ietf-netext-access-network-option.all@tools.ietf.org" <draft-ietf-netext-access-network-option.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-netext-access-network-option-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 May 2012 19:58:59 -0000

Alexey,

Thanks for the review. See some initial comments inline.


On May 5, 2012, at 8:58 PM, Alexey Melnikov wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-netext-access-network-option-10.txt
> Reviewer: Alexey Melnikov
> Review Date: 5 May 2012
> IETF LC End Date: 9 May 2012
> IESG Telechat date: Unknown
>=20
> Summary: This draft is ready as a Proposed Standard
>=20
> Major issues: none
>=20
> Minor issues:
>=20
> Minor: [ANI] and [TS23003] seem to be Normative (as per their use in =
3.1.1)

If it is OK from the RFC process point of view, we can put these
non-IETF references into the normative section.

>=20
> Nits/editorials:
>=20
> 1.  Introduction
>=20
>    This document defines a new mobility option, the Access Network
>    Identifier (ANI) option and its sub-options for Proxy Mobile IPv6,
>    that can be used by the mobile access gateway to signal the access
>    network information to the local mobility anchor.  The specific
>    details on how the local mobility anchor uses this information are
>    out-of-scope for this document.  These mobility options are =
optional
>    and are not mandatory for the Proxy Mobile IPv6 protocol.
>=20
> Nit: Last sentence: "optional" and "not mandatory" are the same thing =
on my book.

Proposal for new text:

   "These mobility options are optional for the Proxy Mobile IPv6 =
protocol."

>=20
> Strictly speaking PEN numbers are not limited to 4 bytes. However you =
have a registry for types of identifiers, so a new value can be =
allocated for bigger-than-4-bytes PENs.

Right. So we could just remove the 4 octet length requirement and use a=20=

"natural" length indicated octet coding for the PENs. For example

ANI Length =3D 1 -> PENs 0-255
ANI Length =3D 2 -> PENs 0-65535
ANI Length =3D 3 -> PENs 0-16777216
...

That would be ok?


- Jouni



From alexey.melnikov@isode.com  Mon May  7 02:40:30 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B67E821F858F; Mon,  7 May 2012 02:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level: 
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fUdQcMUqNjAh; Mon,  7 May 2012 02:40:30 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id A26E621F8570; Mon,  7 May 2012 02:40:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1336383627; d=isode.com; s=selector; i=@isode.com; bh=l1m2rqWpBNHgcq24BpyCgKcQsNS3lN0wf4KQhqAVrDM=; 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=Z9IkZh79e4aeY+x644u3TDnmBhWnSJpOj/169ew6GgdwS0pMH52fmhXizKkAeoz/kL3lk8 xyeJbqd4B1yE7ILVxqEMvm6nlrvx5YMfop25Np/ioYzhtWaLSuwHaPm846VfaFSrGnYkdY 2LPiklih54i9sHHD22b3HdDn1B2AMqY=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T6eYigB=g4me@rufus.isode.com>; Mon, 7 May 2012 10:40:27 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4FA798B8.7070702@isode.com>
Date: Mon, 07 May 2012 10:41:12 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: jouni korhonen <jouni.nospam@gmail.com>
References: <CADhm99oKj8Trcx5o37kg=xZ85ut1iT4xcog+mBO_GP1T4Xnxqg@mail.gmail.com> <01b401cd13d3$322bc950$96835bf0$@isode.com> <3B677B5C-CC21-4252-B343-C6C4A57BBE5B@isode.com> <021901cd1447$39b550f0$ad1ff2d0$@isode.com> <24541053-C0B1-47B3-B866-19E0909BB176@isode.com> <021f01cd1491$13104820$3930d860$@isode.com> <E30B4753-60B8-470B-A1DF-E2ABD31D62E0@isode.com> <47440497-5003-4067-97D5-5426099AFECC@gmail.com>
In-Reply-To: <47440497-5003-4067-97D5-5426099AFECC@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Gen-art@ietf.org" <Gen-art@ietf.org>, "draft-ietf-netext-access-network-option.all@tools.ietf.org" <draft-ietf-netext-access-network-option.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-Art review of draft-ietf-netext-access-network-option-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 09:40:30 -0000

On 06/05/2012 20:58, jouni korhonen wrote:
> Alexey,
Hi Jouni,
> Thanks for the review. See some initial comments inline.
>
>
> On May 5, 2012, at 8:58 PM, Alexey Melnikov wrote:
>
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-netext-access-network-option-10.txt
>> Reviewer: Alexey Melnikov
>> Review Date: 5 May 2012
>> IETF LC End Date: 9 May 2012
>> IESG Telechat date: Unknown
>>
>> Summary: This draft is ready as a Proposed Standard
>>
>> Major issues: none
>>
>> Minor issues:
>>
>> Minor: [ANI] and [TS23003] seem to be Normative (as per their use in 3.1.1)
> If it is OK from the RFC process point of view, we can put these
> non-IETF references into the normative section.
I think that is fine in general. You should double check with the 
responsible AD whether the references are stable (as otherwise they 
might not be suitable for referencing normatively).
>> Nits/editorials:
>>
>> 1.  Introduction
>>
>>     This document defines a new mobility option, the Access Network
>>     Identifier (ANI) option and its sub-options for Proxy Mobile IPv6,
>>     that can be used by the mobile access gateway to signal the access
>>     network information to the local mobility anchor.  The specific
>>     details on how the local mobility anchor uses this information are
>>     out-of-scope for this document.  These mobility options are optional
>>     and are not mandatory for the Proxy Mobile IPv6 protocol.
>>
>> Nit: Last sentence: "optional" and "not mandatory" are the same thing on my book.
> Proposal for new text:
>
>     "These mobility options are optional for the Proxy Mobile IPv6 protocol."
Perfect :-).
>> Strictly speaking PEN numbers are not limited to 4 bytes. However you have a registry for types of identifiers, so a new value can be allocated for bigger-than-4-bytes PENs.
> Right. So we could just remove the 4 octet length requirement and use a
> "natural" length indicated octet coding for the PENs. For example
>
> ANI Length = 1 ->  PENs 0-255
> ANI Length = 2 ->  PENs 0-65535
> ANI Length = 3 ->  PENs 0-16777216
> ...
>
> That would be ok?
That would work, as long as the extra complexity (which is marginal in 
this case) is Ok with the WG.


From christer.holmberg@ericsson.com  Mon May  7 03:25:34 2012
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF15821F85A3 for <gen-art@ietfa.amsl.com>; Mon,  7 May 2012 03:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51lK539Ma5Zr for <gen-art@ietfa.amsl.com>; Mon,  7 May 2012 03:25:33 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id C82F221F858E for <gen-art@ietf.org>; Mon,  7 May 2012 03:25:32 -0700 (PDT)
X-AuditID: c1b4fb2d-b7b76ae0000063d8-3b-4fa7a31bc3c9
Authentication-Results: mailgw1.ericsson.se x-tls.subject="/CN=esessmw0247"; auth=fail (cipher=AES128-SHA)
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client CN "esessmw0247", Issuer "esessmw0247" (not verified)) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 37.AB.25560.B13A7AF4; Mon,  7 May 2012 12:25:31 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.64]) by esessmw0247.eemea.ericsson.se ([153.88.115.93]) with mapi; Mon, 7 May 2012 12:25:24 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Date: Mon, 7 May 2012 12:25:22 +0200
Thread-Topic: Gen-ART review of draft-betts-itu-oam-ach-code-point-04
Thread-Index: Ac0sOT0zWKIZyXd2SLuWg9ACQeaLng==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C4435E382@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F2072F1E0DE894DA4B517B93C6A05852C4435E382ESESSCMS0356e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "'draft-betts-itu-oam-ach-code-point.all@tools.ietf.org'" <draft-betts-itu-oam-ach-code-point.all@tools.ietf.org>
Subject: [Gen-art] Gen-ART review of draft-betts-itu-oam-ach-code-point-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 10:25:34 -0000

--_000_7F2072F1E0DE894DA4B517B93C6A05852C4435E382ESESSCMS0356e_
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-betts-itu-oam-ach-code-point-04
Reviewer: Christer Holmberg
Review Date: 7 May 2012
IETF LC End Date: 21 March 2012
IESG Telechat date: 10 May 2012
Summary: The draft is ready for publication, with a couple of editorial nit=
s.
Major issues: -
Minor issues: -
Nits/editorial comments:

(The comments also applied to the -03 version, and I apologize for not brin=
ging them up when I reviewed that version.)
- General: G-ACh is mentioned throughout the document, but only in section =
4 is there a reference to RFC 5586. I suggest to add a reference on first o=
ccurrence at least to section 1. It would probably be good also in section =
3.

- Section 1: What is the purpose of the last paragraph, talking about IETF =
Experts not agreeing? For someone who has not followed the work, it seems a=
s little strange.
- Section 3: The text says "The G-ACh Type assigned by this document". I gu=
ess it would be better to say e.g. "based on this document".
Regards,
Christer


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:55050477;
	mso-list-type:hybrid;
	mso-list-template-ids:475815826 -624681240 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:3;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:768430861;
	mso-list-type:hybrid;
	mso-list-template-ids:313398348 -456090258 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:3;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the assigne=
d Gen-ART reviewer for this draft. For background on Gen-ART, please see th=
e FAQ at &lt; http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;.<=
o:p></o:p></p><p class=3DMsoNormal> <o:p></o:p></p><p class=3DMsoNormal>Ple=
ase wait for direction from your document shepherd or AD before posting a n=
ew version of the draft.<o:p></o:p></p><p class=3DMsoNormal> <o:p></o:p></p=
><p class=3DMsoNormal>Document: draft-betts-itu-oam-ach-code-point-04<o:p><=
/o:p></p><p class=3DMsoNormal>Reviewer: Christer Holmberg<o:p></o:p></p><p =
class=3DMsoNormal>Review Date: 7 May 2012<o:p></o:p></p><p class=3DMsoNorma=
l>IETF LC End Date: 21 March 2012<o:p></o:p></p><p class=3DMsoNormal>IESG T=
elechat date: 10 May 2012<o:p></o:p></p><p class=3DMsoNormal> <o:p></o:p></=
p><p class=3DMsoNormal>Summary: The draft is ready for publication, with a =
couple of editorial nits.<o:p></o:p></p><p class=3DMsoNormal> <o:p></o:p></=
p><p class=3DMsoNormal>Major issues: -<o:p></o:p></p><p class=3DMsoNormal> =
<o:p></o:p></p><p class=3DMsoNormal>Minor issues: -<o:p></o:p></p><p class=
=3DMsoNormal> <o:p></o:p></p><p class=3DMsoNormal>Nits/editorial comments:<=
o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorma=
l>(The comments also applied to the -03 version, and I apologize for not br=
inging them up when I reviewed that version.)<o:p></o:p></p><p class=3DMsoN=
ormal> <o:p></o:p></p><p class=3DMsoNormal>- General: G-ACh is mentioned th=
roughout the document, but only in section 4 is there a reference to RFC 55=
86. I suggest to add a reference on first occurrence at least to section 1.=
 It would probably be good also in section 3.<o:p></o:p></p><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>- Section 1: What is the pu=
rpose of the last paragraph, talking about IETF Experts not agreeing? For s=
omeone who has not followed the work, it seems as little strange.<o:p></o:p=
></p><p class=3DMsoNormal> <o:p></o:p></p><p class=3DMsoNormal>- Section 3:=
 The text says &#8220;The G-ACh Type assigned by this document&#8221;. I gu=
ess it would be better to say e.g. &#8220;based on this document&#8221;.<o:=
p></o:p></p><p class=3DMsoNormal> <o:p></o:p></p><p class=3DMsoNormal>Regar=
ds,<o:p></o:p></p><p class=3DMsoNormal> <o:p></o:p></p><p class=3DMsoNormal=
>Christer<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></b=
ody></html>=

--_000_7F2072F1E0DE894DA4B517B93C6A05852C4435E382ESESSCMS0356e_--

From adrian@olddog.co.uk  Mon May  7 06:49:16 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A8F921F8637; Mon,  7 May 2012 06:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lMYM1HLaSzVW; Mon,  7 May 2012 06:49:15 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 4094B21F8630; Mon,  7 May 2012 06:49:14 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q47DnCcp012234;  Mon, 7 May 2012 14:49:12 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q47DnAow012225 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 May 2012 14:49:11 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Christer Holmberg'" <christer.holmberg@ericsson.com>, <gen-art@ietf.org>
References: <7F2072F1E0DE894DA4B517B93C6A05852C4435E382@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852C4435E382@ESESSCMS0356.eemea.ericsson.se>
Date: Mon, 7 May 2012 14:49:10 +0100
Message-ID: <006601cd2c58$2f326b30$8d974190$@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: AQIMbPmvAujJQq4KsAzDKDfxoFlAaJY/0X7Q
Content-Language: en-gb
Cc: draft-betts-itu-oam-ach-code-point.all@tools.ietf.org, iesg@ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-betts-itu-oam-ach-code-point-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 13:49:16 -0000

All (copying the IESG),

I do sincerely welcome all reviews of all I-Ds that I sponsor or where I am the
responsible AD. I even mainly welcome them when I am an author.

However, when Directorate or Review Team reviews come in so long after the end
of IETF Last Call, and especially when they arrive after the I-D has been
updated to address last call comments, I do grind my teeth a bit.

Additionally, when Directorate or Review Team reviews are repeated and bring up
new issues (even minor ones) that were in the document at the time of the first
review but didn't warrant a comment at that time, I feel like I am being asked
for a rock.

Anyway, thanks Chris for caring enough to read the document for a second time,
and see in line for answers.

> Summary: The draft is ready for publication, with a couple of editorial nits.
>
> Major issues: -
>
> Minor issues: -
> 
> Nits/editorial comments:
>
> (The comments also applied to the -03 version, and I apologize for
> not bringing them up when I reviewed that version.)
>
> - General: G-ACh is mentioned throughout the document, but only in 
> section 4 is there a reference to RFC 5586. I suggest to add a reference
> on first occurrence at least to section 1. It would probably be good also
> in section 3.

Added RFC Editor note

Section1 para 2

s/Generic Associated Channel (G-ACh) Type/Generic Associated Channel (G-ACh)
Type [RFC5586]

> - Section 1: What is the purpose of the last paragraph, talking about IETF
>  Experts not agreeing? For someone who has not followed the work, it
>  seems as little strange.

I am not sure how to answer you without giving a long and detailed history of
this work covering the last four years. Such a history is without doubt
contentious.

You might read the referenced I-D for an alternate viewpoint. Or you might speak
privately with any number of people involved with this work.

In summary, this text is necessary to obtain consensus on the publication of
this document, and is agreed by the document author.

> - Section 3: The text says "The G-ACh Type assigned by this document". I guess
> it would be better to say e.g. "based on this document".

Well, of course, "based on" is also not right :-)

One might say, "...assigned by the IANA as a result of the request contained in
this document."
To me that is over-baked. What is more, during late-stage IANA processing, the
"request" text in I-Ds is replaced with "action" text that describes what action
IANA has taken.

Common usage is that a document that is approved for publication and that makes
an IANA request is the document that made the assignment or created the
registry.

So we won't make any change for that.

Cheers,
Adrian


From christer.holmberg@ericsson.com  Mon May  7 10:51:51 2012
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C16E221F861F; Mon,  7 May 2012 10:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.15
X-Spam-Level: 
X-Spam-Status: No, score=-6.15 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qO+8mvMU3V0M; Mon,  7 May 2012 10:51:50 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id A64FF21F861E; Mon,  7 May 2012 10:51:47 -0700 (PDT)
X-AuditID: c1b4fb30-b7c78ae000006de5-46-4fa80bb2a84b
Authentication-Results: mailgw7.ericsson.se x-tls.subject="/CN=esessmw0197"; auth=fail (cipher=AES128-SHA)
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client CN "esessmw0197", Issuer "esessmw0197" (not verified)) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 1B.54.28133.2BB08AF4; Mon,  7 May 2012 19:51:47 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.64]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Mon, 7 May 2012 19:51:45 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Mon, 7 May 2012 19:51:44 +0200
Thread-Topic: Gen-ART review of draft-betts-itu-oam-ach-code-point-04
Thread-Index: AQIMbPmvAujJQq4KsAzDKDfxoFlAaJY/0X7QgABHP8E=
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C44001345@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A05852C4435E382@ESESSCMS0356.eemea.ericsson.se>, <006601cd2c58$2f326b30$8d974190$@olddog.co.uk>
In-Reply-To: <006601cd2c58$2f326b30$8d974190$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-betts-itu-oam-ach-code-point.all@tools.ietf.org" <draft-betts-itu-oam-ach-code-point.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-betts-itu-oam-ach-code-point-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 17:51:52 -0000

Hi Adrian,

I will not go more into the comment regarding IETF Experts not agreeing. If=
 the paragraph was needed in order to move the work forward, I don't want t=
o mess that up :)

I am happy if the 5586 reference is fixed, which you have requested the RFC=
 editor to do.

Once again, I appologize for not giving these comments earlier.

Regards,

Christer

________________________________________
From: Adrian Farrel [adrian@olddog.co.uk]
Sent: Monday, May 07, 2012 4:49 PM
To: Christer Holmberg; gen-art@ietf.org
Cc: draft-betts-itu-oam-ach-code-point.all@tools.ietf.org; iesg@ietf.org
Subject: RE: Gen-ART review of draft-betts-itu-oam-ach-code-point-04

All (copying the IESG),

I do sincerely welcome all reviews of all I-Ds that I sponsor or where I am=
 the
responsible AD. I even mainly welcome them when I am an author.

However, when Directorate or Review Team reviews come in so long after the =
end
of IETF Last Call, and especially when they arrive after the I-D has been
updated to address last call comments, I do grind my teeth a bit.

Additionally, when Directorate or Review Team reviews are repeated and brin=
g up
new issues (even minor ones) that were in the document at the time of the f=
irst
review but didn't warrant a comment at that time, I feel like I am being as=
ked
for a rock.

Anyway, thanks Chris for caring enough to read the document for a second ti=
me,
and see in line for answers.

> Summary: The draft is ready for publication, with a couple of editorial n=
its.
>
> Major issues: -
>
> Minor issues: -
>
> Nits/editorial comments:
>
> (The comments also applied to the -03 version, and I apologize for
> not bringing them up when I reviewed that version.)
>
> - General: G-ACh is mentioned throughout the document, but only in
> section 4 is there a reference to RFC 5586. I suggest to add a reference
> on first occurrence at least to section 1. It would probably be good also
> in section 3.

Added RFC Editor note

Section1 para 2

s/Generic Associated Channel (G-ACh) Type/Generic Associated Channel (G-ACh=
)
Type [RFC5586]

> - Section 1: What is the purpose of the last paragraph, talking about IET=
F
>  Experts not agreeing? For someone who has not followed the work, it
>  seems as little strange.

I am not sure how to answer you without giving a long and detailed history =
of
this work covering the last four years. Such a history is without doubt
contentious.

You might read the referenced I-D for an alternate viewpoint. Or you might =
speak
privately with any number of people involved with this work.

In summary, this text is necessary to obtain consensus on the publication o=
f
this document, and is agreed by the document author.

> - Section 3: The text says "The G-ACh Type assigned by this document". I =
guess
> it would be better to say e.g. "based on this document".

Well, of course, "based on" is also not right :-)

One might say, "...assigned by the IANA as a result of the request containe=
d in
this document."
To me that is over-baked. What is more, during late-stage IANA processing, =
the
"request" text in I-Ds is replaced with "action" text that describes what a=
ction
IANA has taken.

Common usage is that a document that is approved for publication and that m=
akes
an IANA request is the document that made the assignment or created the
registry.

So we won't make any change for that.

Cheers,
Adrian=

From miguel.a.garcia@ericsson.com  Tue May  8 00:28:54 2012
Return-Path: <miguel.a.garcia@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 090D721F84B8 for <gen-art@ietfa.amsl.com>; Tue,  8 May 2012 00:28:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.214
X-Spam-Level: 
X-Spam-Status: No, score=-6.214 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9zr8eDMIhXtm for <gen-art@ietfa.amsl.com>; Tue,  8 May 2012 00:28:53 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3387021F8484 for <gen-art@ietf.org>; Tue,  8 May 2012 00:28:52 -0700 (PDT)
X-AuditID: c1b4fb30-b7c78ae000006de5-51-4fa8cb33c2b6
Authentication-Results: mailgw7.ericsson.se x-tls.subject="/CN=esessmw0237"; auth=fail (cipher=AES128-SHA)
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client CN "esessmw0237", Issuer "esessmw0237" (not verified)) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 7D.F1.28133.33BC8AF4; Tue,  8 May 2012 09:28:52 +0200 (CEST)
Received: from [159.107.24.244] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.213.0; Tue, 8 May 2012 09:28:51 +0200
Message-ID: <4FA8CB32.8080709@ericsson.com>
Date: Tue, 8 May 2012 09:28:50 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gnawali@cs.uh.edu, pal@cs.stanford.edu, jpv@cisco.com,  Adrian Farrel <adrian@olddog.co.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-roll-minrank-hysteresis-of-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 07:28:54 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft. For background on Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

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

Document: draft-ietf-roll-minrank-hysteresis-of-10.txt
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 2012-05-08
IESG Telechat date: 2012-05-10

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

Major issues: none

Minor issues: none

Nits/editorial comments:

I reviewed version -07 of this document. At that time, I had a few 
editorial comments, and all of them but one have been addressed in 
version -10. The comment that has not been address is included here again 
for your consideration:

- Section 3.1. Towards the end of the section, the sentence reads:

    The path cost corresponding to a neighbor SHOULD be re-computed each
    time:

and then there are 3 conditions numbered from 1 to 3. It is not clear if 
the path cost should be recomputed when all of the 3 conditions are met, 
or when any of the 3 conditions are met. In other words, it is not clear 
if the 3 bullet points are an "AND" or an "OR" operation among then. 
Presumably they are an "OR". If this is the case, perhaps the sentence 
should be rephrased as:

    The path cost corresponding to a neighbor SHOULD be re-computed each
    time any of the following conditions are met:



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

From vkg@bell-labs.com  Tue May  8 07:20:17 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84FD321F845C for <gen-art@ietfa.amsl.com>; Tue,  8 May 2012 07:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.69
X-Spam-Level: 
X-Spam-Status: No, score=-109.69 tagged_above=-999 required=5 tests=[AWL=0.909, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dWXLTdSWHsPx for <gen-art@ietfa.amsl.com>; Tue,  8 May 2012 07:20:16 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 7703621F845A for <gen-art@ietf.org>; Tue,  8 May 2012 07:20:12 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id q48EJT4g027392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 8 May 2012 09:19:31 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q48EJTbo026092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 May 2012 09:19:29 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q48EJOxH025958; Tue, 8 May 2012 09:19:24 -0500 (CDT)
Message-ID: <4FA92CA5.7020903@bell-labs.com>
Date: Tue, 08 May 2012 09:24:37 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: draft-ietf-ippm-reporting-metrics@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: henk@uijterwaal.nl, Wesley Eddy <wes@mti-systems.com>, General Area Review Team <gen-art@ietf.org>, matt@internet2.edu
Subject: [Gen-art] Gen-ART review of draft-ietf-ippm-reporting-metrics-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 14:20:17 -0000

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

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

Document: draft-ietf-ippm-reporting-metrics-08
Reviewer: Vijay K. Gurbani
Review Date: May-08-2012
IETF LC End Date: April-11-2012
IESG Telechat date: May-10-2012

Summary: This draft is ready as an Informational but has some minor
issues and nits that should be fixed before publication.

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

Minor issues:
- S3.1: I suspect that the metrics like packet loss and packet delay
  discussed in S3.1 are for hosts on the (I)nternet and not in a
  laboratory setting, yes?  If so, it may be good to state this.

- S4.1: I would mention at the end of the paragraph that you intend
  to fill the gap in RFC2680 by providing a reasonable value for the
  waiting time.

- S4.1.1: In Figure 1, t_0 is probably the delay in the initial
  link before you get to the first router.  If so, please make this
  explicit.

- S4.1.1: Just curious --- you provide a rationale for the choice
  of link delay of 100ms and queue length of 100ms.  But n=5 and L=4
  seem to be magic numbers.  I suspect that the choice of these is
  sound, but a couple of words on why the values of these variables
  are set to the ones shown would be good.

- S5.1.1: In the two bullet items here, you posit that processes
  are spawned when an unexpected condition occurs.  Why should this
  be a process?  Why not a thread?  Or a light-weight process?  Or
  an event loop?  My point is to stay away from well known and
  contextual words that dictate a specific architecture; i.e., the
  receiver spawns processes to handle an event.  Better to be generic,
  something like the following (please modify as you see fit):

  OLD:
   o  Packets that arrive within expected tolerance are handled by
       processes that remove headers, restore smooth delivery timing (as
       in a de-jitter buffer), restore sending order, check for errors in
       payloads, and many other operations.

    o  Packets that do not arrive when expected spawn other processes
       that attempt recovery from the apparent loss, such as
       retransmission requests, loss concealment, or forward error
       correction to replace the missing packet.
   NEW:
   o  Packets that arrive within expected tolerance are handled by
       removing headers, restoring smooth delivery timing (as
       in a de-jitter buffer), restoring sending order, checking for
       errors in payloads, and many other operations.

    o  Packets that do not arrive when expected lead to an attempted
       recovery from the apparent loss, such as retransmission
       requests, loss concealment, or forward error correction to
       replace the missing packet

- S5.1.2: Figure 3 --- if I understand the surrounding text for Figure
  3 correctly, then to show a "small fraction of packets are lost",
  the CDF curve should be asymptotic to the Y-axis and then become
  stable at the Y=1 value (i.e., be asymptotic to it).  We want to
  denote that almost 100% of the packets exhibit a loss close to 0.

Nits:

- S1: While characterizing the main audience, I am not sure what
  "consumer" means --- is it synonymous with "user"?  And if so, I
  think that replacing consumer with user may be better.  If these
  terms are not synonymous, then please provide a definition (even a
  loose one) of what a consumer is.

- S3.1, seems like a grammatical error in the sentence:
  "We have calculated a waiting time above that should be sufficient
  to differentiate between packets that are truly lost or have long
  finite delays under general measurement circumstances, 51 seconds."
  Probably better to rephrase as:
  "We have calculated that under general measurement circumstances,
  51 seconds is an appropriate length of time to differentiate between
  packets that are truly lost from packets that are experiencing
  long finite delays."

- S4.1.1: Right before Figure 1, you define D.  My suggestion would
  be to replace the text:
    "The normal path delay across n hops without encountering a
    loop, D, is"
  with
    "The normal path delay, D, across n hops without encountering a
    loop is"
  Here, "D" is qualifying the delay, not the loop.  So it is best
  close to the word "delay".

- S5.1.2: In Figure 3, I would suggest using "+Inf" instead of
  "+o0" to denote infinity.  It took me a while to figure out that
  the latter is an ASCII approximation to infinity.

- S6.6: In the section heading, I would advise spelling out
  "Avail." completely.  Truncating it as such serves no purpose that
  I could see and simply acts as a detraction.

Thanks!	

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From acmorton@att.com  Tue May  8 08:12:54 2012
Return-Path: <acmorton@att.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFE1711E807F for <gen-art@ietfa.amsl.com>; Tue,  8 May 2012 08:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.693
X-Spam-Level: 
X-Spam-Status: No, score=-103.693 tagged_above=-999 required=5 tests=[AWL=0.645, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F90HzVBIeWiF for <gen-art@ietfa.amsl.com>; Tue,  8 May 2012 08:12:53 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id 8D39B21F84E6 for <gen-art@ietf.org>; Tue,  8 May 2012 08:12:53 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id 5f739af4.0.496717.00-438.1362821.nbfkord-smmo05.seg.att.com (envelope-from <acmorton@att.com>);  Tue, 08 May 2012 15:12:53 +0000 (UTC)
X-MXL-Hash: 4fa937f541ab0ff8-85d97ab7abb825e47cdd893ee259976d3ec7bf0c
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q48FCqVx025016 for <gen-art@ietf.org>; Tue, 8 May 2012 11:12:53 -0400
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q48FCmL3024966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Tue, 8 May 2012 11:12:48 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor) for <gen-art@ietf.org>; Tue, 8 May 2012 11:12:26 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q48FCQhp010404 for <gen-art@ietf.org>; Tue, 8 May 2012 11:12:26 -0400
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q48FCLX8009679 for <gen-art@ietf.org>; Tue, 8 May 2012 11:12:22 -0400
Message-Id: <201205081512.q48FCLX8009679@alpd052.aldc.att.com>
Received: from acmt.att.com (dn135-16-251-71.dhcpn.ugn.att.com[135.16.251.71](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120508150858gw10060lqoe>; Tue, 8 May 2012 15:08:59 +0000
X-Originating-IP: [135.16.251.71]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 08 May 2012 11:13:31 -0400
To: "Vijay K. Gurbani" <vkg@bell-labs.com>, draft-ietf-ippm-reporting-metrics@tools.ietf.org
From: Al Morton <acmorton@att.com>
In-Reply-To: <4FA92CA5.7020903@bell-labs.com>
References: <4FA92CA5.7020903@bell-labs.com>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=dit6Jc5sqrAA:10 a=5BdZ5gd732QA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=azEeBXcERCOERiMjQvkA:9 a=RSA_syLTnGnTQ8z8b]
X-AnalysisOut: [wYA:7 a=CjuIK1q_8ugA:10 a=_W_S_7VecoQA:10 a=q4htw2QqTbiheL]
X-AnalysisOut: [az:21 a=X_4z4ktRHvr-via4:21]
Cc: henk@uijterwaal.nl, Wesley Eddy <wes@mti-systems.com>, General Area Review Team <gen-art@ietf.org>, matt@internet2.edu
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ippm-reporting-metrics-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 15:12:54 -0000

<html>
<body>
Hi Vijay,<br><br>
Thanks for your review, please see replies below.<br><br>
Al<br><br>
At 10:24 AM 5/8/2012, Vijay K. Gurbani wrote:<br>
<blockquote type=cite class=cite cite="">...<br><br>
<dl>
<dd>Document: draft-ietf-ippm-reporting-metrics-08
<dd>Reviewer: Vijay K. Gurbani
<dd>Review Date: May-08-2012
<dd>IETF LC End Date: April-11-2012
<dd>IESG Telechat date: May-10-2012<br>

<dd>Summary: This draft is ready as an Informational but has some minor
<dd>issues and nits that should be fixed before publication.<br>

<dd>Major issues: 0
<dd>Minor issues: 6
<dd>Nits/editorial comments: 5<br>

<dd>Minor issues:
<dd>- S3.1: I suspect that the metrics like packet loss and packet delay
<dd>&nbsp;discussed in S3.1 are for hosts on the (I)nternet and not in a
<dd>&nbsp;laboratory setting, yes?&nbsp; If so, it may be good to state
this.</blockquote>
</dl><br>
IPPM's metrics are able to be used in either the cap-I Internet<br>
or the isolated test lab, and several BMWG RFCs reference IPPM<br>
metric definitions. When the RFC 2330 considerations are followed,<br>
these metrics are safe to use in any setting.<br><br>
<br><br><blockquote type=cite class=cite cite="">
<dl>
<dd>- S4.1: I would mention at the end of the paragraph that you intend
<dd>&nbsp;to fill the gap in RFC2680 by providing a reasonable value for
the
<dd>&nbsp;waiting time.</blockquote>
</dl><br>
I'll add:&nbsp; &quot;We estimate a practical bound on waiting time
below.&quot;<br><br>
<blockquote type=cite class=cite cite="">
<dl>
<dd>- S4.1.1: In Figure 1, t_0 is probably the delay in the initial
<dd>&nbsp;link before you get to the first router.&nbsp; If so, please
make this
<dd>&nbsp;explicit.</blockquote>
</dl><br>
To address Adrian Farrell's Comment, we've added path models for<br>
the normal and loop cases, above each equation.<br><br>
<blockquote type=cite class=cite cite="">
<dl>
<dd>- S4.1.1: Just curious --- you provide a rationale for the choice
<dd>&nbsp;of link delay of 100ms and queue length of 100ms.&nbsp; But n=5
and L=4
<dd>&nbsp;seem to be magic numbers.&nbsp; I suspect that the choice of
these is
<dd>&nbsp;sound, but a couple of words on why the values of these
variables
<dd>&nbsp;are set to the ones shown would be good.</blockquote>
</dl><br>
there's nothing special about n=5 and L=4. <br>
Together n, L and TTL determine C_max, which I will note that <br>
we use in the calculation, just to be clear.<br><br>
<blockquote type=cite class=cite cite="">
<dl>
<dd>- S5.1.1: In the two bullet items here, you posit that processes
<dd>&nbsp;are spawned when an unexpected condition occurs.&nbsp; Why
should this
<dd>&nbsp;be a process?&nbsp; Why not a thread?&nbsp; Or a light-weight
process?&nbsp; Or
<dd>&nbsp;an event loop?&nbsp; My point is to stay away from well known
and
<dd>&nbsp;contextual words that dictate a specific architecture; i.e.,
the
<dd>&nbsp;receiver spawns processes to handle an event.&nbsp; Better to
be generic,
<dd>&nbsp;something like the following (please modify as you see
fit):</blockquote>
</dl><br>
I thought process *was* generic, but will try your suggested text.<br>
Is &quot;operations&quot; sufficiently generic?<br><br>
<blockquote type=cite class=cite cite="">
<dl>
<dd>&nbsp;OLD:
<dd>&nbsp; o&nbsp; Packets that arrive within expected tolerance are
handled by
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; processes that remove headers, restore
smooth delivery timing (as
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in a de-jitter buffer), restore
sending order, check for errors in
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; payloads, and many other
operations.<br>

<dd>&nbsp;&nbsp; o&nbsp; Packets that do not arrive when expected spawn
other processes
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that attempt recovery from the
apparent loss, such as
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; retransmission requests, loss
concealment, or forward error
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; correction to replace the missing
packet.
<dd>&nbsp; NEW:
<dd>&nbsp; o&nbsp; Packets that arrive within expected tolerance are
handled by
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; removing headers, restoring smooth
delivery timing (as
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in a de-jitter buffer), restoring
sending order, checking for
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; errors in payloads, and many other
operations.<br>

<dd>&nbsp;&nbsp; o&nbsp; Packets that do not arrive when expected lead to
an attempted
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recovery from the apparent loss, such
as retransmission
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; requests, loss concealment, or forward
error correction to
<dd>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; replace the missing packet<br>

<dd>- S5.1.2: Figure 3 --- if I understand the surrounding text for
Figure
<dd>&nbsp;3 correctly, then to show a &quot;small fraction of packets are
lost&quot;,
<dd>&nbsp;the CDF curve should be asymptotic to the Y-axis and then
become
<dd>&nbsp;stable at the Y=1 value (i.e., be asymptotic to it).&nbsp; We
want to
<dd>&nbsp;denote that almost 100% of the packets exhibit a loss close to
0.</blockquote>
</dl><br>
I think that might be the Loss CDF, but this is the Delay CDF when<br>
Lost Packets are assigned delay = +infinity.<br><br>
The text says:
<dl>
<dd>&quot;As further evidence of overlap, consider the Cumulative
Distribution Function (CDF) of Delay when the value &quot;positive
infinity&quot; is assigned to all lost packets.&quot; 
</dl>I think you've helped make our case, it's confusing to mix Loss and
Delay<br>
on the same dimension...<br><br>
<blockquote type=cite class=cite cite="">
<dl>
<dd>Nits:<br>

<dd>- S1: While characterizing the main audience, I am not sure what
<dd>&nbsp;&quot;consumer&quot; means --- is it synonymous with
&quot;user&quot;?&nbsp; And if so, I
<dd>&nbsp;think that replacing consumer with user may be better.&nbsp; If
these
<dd>&nbsp;terms are not synonymous, then please provide a definition
(even a
<dd>&nbsp;loose one) of what a consumer is.</blockquote>
</dl><br>
&quot;user&quot; is too vague and also has a strong precedent in the
computer<br>
networking context - we can add an adjective:<br>
s/consumer/report consumer/<br><br>
<blockquote type=cite class=cite cite="">
<dl>
<dd>- S3.1, seems like a grammatical error in the sentence:
<dd>&nbsp;&quot;We have calculated a waiting time above that should be
sufficient
<dd>&nbsp;to differentiate between packets that are truly lost or have
long
<dd>&nbsp;finite delays under general measurement circumstances, 51
seconds.&quot;
<dd>&nbsp;Probably better to rephrase as:
<dd>&nbsp;&quot;We have calculated that under general measurement
circumstances,
<dd>&nbsp;51 seconds is an appropriate length of time to differentiate
between
<dd>&nbsp;packets that are truly lost from packets that are experiencing
<dd>&nbsp;long finite delays.&quot;</blockquote>
</dl><br>
My grammar-checker accepted a slightly revised version,<br>
with s/above/in section 4.1.1/<br><br>
<blockquote type=cite class=cite cite="">
<dl>
<dd>- S4.1.1: Right before Figure 1, you define D.&nbsp; My suggestion
would
<dd>&nbsp;be to replace the text:
<dd>&nbsp;&nbsp; &quot;The normal path delay across n hops without
encountering a
<dd>&nbsp;&nbsp; loop, D, is&quot;
<dd>&nbsp;with
<dd>&nbsp;&nbsp; &quot;The normal path delay, D, across n hops without
encountering a
<dd>&nbsp;&nbsp; loop is&quot;
<dd>&nbsp;Here, &quot;D&quot; is qualifying the delay, not the
loop.&nbsp; So it is best
<dd>&nbsp;close to the word &quot;delay&quot;.</blockquote>
</dl><br>
OK<br><br>
<blockquote type=cite class=cite cite="">
<dl>
<dd>- S5.1.2: In Figure 3, I would suggest using &quot;+Inf&quot; instead
of
<dd>&nbsp;&quot;+o0&quot; to denote infinity.&nbsp; It took me a while to
figure out that
<dd>&nbsp;the latter is an ASCII approximation to infinity.</blockquote>
</dl><br>
So far, everybody else got it...<br><br>
<blockquote type=cite class=cite cite="">
<dl>
<dd>- S6.6: In the section heading, I would advise spelling out
<dd>&nbsp;&quot;Avail.&quot; completely.&nbsp; Truncating it as such
serves no purpose that
<dd>&nbsp;I could see and simply acts as a detraction.<br>
</blockquote>
</dl>OK<br>
</body>
</html>


From vkg@bell-labs.com  Tue May  8 08:37:51 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77FCD11E80A0 for <gen-art@ietfa.amsl.com>; Tue,  8 May 2012 08:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.729
X-Spam-Level: 
X-Spam-Status: No, score=-107.729 tagged_above=-999 required=5 tests=[AWL=-1.130, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ylOzZXZ1Anic for <gen-art@ietfa.amsl.com>; Tue,  8 May 2012 08:37:50 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF7511E809A for <gen-art@ietf.org>; Tue,  8 May 2012 08:37:48 -0700 (PDT)
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 q48FbjcV002345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 8 May 2012 10:37:46 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q48Fbi3G009449 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 May 2012 10:37:45 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q48FbifO003819; Tue, 8 May 2012 10:37:44 -0500 (CDT)
Message-ID: <4FA93F01.2030208@bell-labs.com>
Date: Tue, 08 May 2012 10:42:57 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: Al Morton <acmorton@att.com>
References: <4FA92CA5.7020903@bell-labs.com> <201205081512.q48FCLX3009677@alpd052.aldc.att.com>
In-Reply-To: <201205081512.q48FCLX3009677@alpd052.aldc.att.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
Cc: henk@uijterwaal.nl, Wesley Eddy <wes@mti-systems.com>, General Area Review Team <gen-art@ietf.org>, draft-ietf-ippm-reporting-metrics@tools.ietf.org, matt@internet2.edu
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ippm-reporting-metrics-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 15:37:51 -0000

On 05/08/2012 10:13 AM, Al Morton wrote:
> Hi Vijay,
>
> Thanks for your review, please see replies below.

Al: Thanks for indulging me.  Points worth spending one more iteration
on are below.

> I thought process *was* generic, but will try your suggested text.

Thanks.

> Is "operations" sufficiently generic?

I think so; the term "operations" existed in your original writeup
and I simply reused it.

> I think that might be the Loss CDF,

Ah, right.

> but this is the Delay CDF when Lost Packets are assigned delay = +infinity.

OK.

>>     Nits:
>>     - S1: While characterizing the main audience, I am not sure what
>>     "consumer" means --- is it synonymous with "user"? And if so, I
>>     think that replacing consumer with user may be better. If these
>>     terms are not synonymous, then please provide a definition (even a
>>     loose one) of what a consumer is.
>
> "user" is too vague and also has a strong precedent in the computer
> networking context - we can add an adjective:
> s/consumer/report consumer/

I tried to re-read the sentences with s/consumer/report consumer/, but
I must admit that I am none the wiser.  Maybe s/consumer/audience/?

>>     - S3.1, seems like a grammatical error in the sentence:
>>     "We have calculated a waiting time above that should be sufficient
>>     to differentiate between packets that are truly lost or have long
>>     finite delays under general measurement circumstances, 51 seconds."
>>     Probably better to rephrase as:
>>     "We have calculated that under general measurement circumstances,
>>     51 seconds is an appropriate length of time to differentiate between
>>     packets that are truly lost from packets that are experiencing
>>     long finite delays."
>
> My grammar-checker accepted a slightly revised version,
> with s/above/in section 4.1.1/

The original sentence seems odd --- the object of the calculated waiting
time (51 seconds) appears at the end of the sentence.  By the time the
reader gets to the ", 51 seconds", he or she may have lost the context
of why 51 seconds is important.

>>     - S5.1.2: In Figure 3, I would suggest using "+Inf" instead of
>>     "+o0" to denote infinity. It took me a while to figure out that
>>     the latter is an ASCII approximation to infinity.
>
> So far, everybody else got it...

OK, no problem.  Please do retain the original text.

Thank you for your time, Al!

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From mahoney@nostrum.com  Thu May 10 14:36:58 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0C2721F85E7 for <gen-art@ietfa.amsl.com>; Thu, 10 May 2012 14:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MvFGENhFeaIU for <gen-art@ietfa.amsl.com>; Thu, 10 May 2012 14:36:58 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 126CB21F85B5 for <gen-art@ietf.org>; Thu, 10 May 2012 14:36:57 -0700 (PDT)
Received: from dn3-30.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q4ALatoJ010113 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 10 May 2012 16:36:57 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FAC34F6.20700@nostrum.com>
Date: Thu, 10 May 2012 16:36:54 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-05-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 21:36:58 -0000

Hi all,

The following reviewers have assignments:


Reviewer                  LC end       Draft

Brian Carpenter          2012-05-31  draft-levine-application-gzip-02

Christer Holmberg      T 2012-05-21  
draft-ietf-pkix-cmp-transport-protocols-18

David Black              2012-06-04  draft-kucherawy-marf-source-ports-03

Francis Dupont           2012-05-21  draft-ietf-appsawg-media-type-regs-07

Joel Halpern             2012-06-04  draft-farrresnickel-ipr-sanctions-05

T means the draft is on the upcoming telechat (5/24).



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

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From brian.e.carpenter@gmail.com  Sat May 12 00:15:52 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC569E8007 for <gen-art@ietfa.amsl.com>; Sat, 12 May 2012 00:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.588
X-Spam-Level: 
X-Spam-Status: No, score=-101.588 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DE4teh+hfxfg for <gen-art@ietfa.amsl.com>; Sat, 12 May 2012 00:15:51 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8BB889E8005 for <gen-art@ietf.org>; Sat, 12 May 2012 00:15:51 -0700 (PDT)
Received: by wibhj8 with SMTP id hj8so124061wib.13 for <gen-art@ietf.org>; Sat, 12 May 2012 00:15:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type; bh=wQ6mLDTGP6TF/CoV4gBCOJGSDzveWL4ro4Yhh4vUPkA=; b=lcu05LQbNqkzpE3K6aR59U5zQpPIJUKJTg8Dqq9Avyb/X6HxJG2TD0ZsmRWyOeESKw vgIJdguXtU917QcC8klO0amQoXdHIDOVOS8z+PGTNuBBnqm8R4sTG43w5GYBWK8bzACM gCusysrHS7roowkA9p1GUM8ORwIeSB3DuyD6RiwL0FAziGtPGTWGxj52qqFLHd/wJYnF 4DlF2dcqhAYTALcNXFmIQYjbk+4MJRFw2/1y2IGq7T/lProKI0sneJKzhqVz/sLhw9x2 XOwOr9/9HlwQfzuHP/VclDMM8L7rDD19TgqeaK65YZdMN9EY8f8g/ZBdm45Y5KTyvK9a 5UlQ==
Received: by 10.180.90.233 with SMTP id bz9mr2213889wib.21.1336806950756; Sat, 12 May 2012 00:15:50 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-118.as13285.net. [2.102.216.118]) by mx.google.com with ESMTPS id du4sm26309442wib.10.2012.05.12.00.15.48 (version=SSLv3 cipher=OTHER); Sat, 12 May 2012 00:15:50 -0700 (PDT)
Message-ID: <4FAE0E22.3080501@gmail.com>
Date: Sat, 12 May 2012 08:15:46 +0100
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-levine-application-gzip.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>
Content-Type: multipart/mixed; boundary="------------020709030303080001060100"
Subject: [Gen-art] Gen-ART LC review of draft-levine-application-gzip-02.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 May 2012 07:15:52 -0000

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

Please see attached review.


--------------020709030303080001060100
Content-Type: text/plain;
 name="draft-levine-application-gzip-02-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-levine-application-gzip-02-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBM
YXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4NCg0KRG9jdW1lbnQ6IGRyYWZ0
LWxldmluZS1hcHBsaWNhdGlvbi1nemlwLTAyLnR4dA0KUmV2aWV3ZXI6IEJyaWFuIENhcnBl
bnRlcg0KUmV2aWV3IERhdGU6IDIwMTItMDUtMTINCklFVEYgTEMgRW5kIERhdGU6IDIwMTIt
MDUtMzENCklFU0cgVGVsZWNoYXQgZGF0ZTogDQoNClN1bW1hcnk6ICBSZWFkeQ0KLS0tLS0t
LS0NCg0K
--------------020709030303080001060100--

From jmh@joelhalpern.com  Sat May 12 16:51:10 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0841921F8688 for <gen-art@ietfa.amsl.com>; Sat, 12 May 2012 16:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.331
X-Spam-Level: 
X-Spam-Status: No, score=-102.331 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJSk8MmWX+OW for <gen-art@ietfa.amsl.com>; Sat, 12 May 2012 16:51:09 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id AB12321F8418 for <gen-art@ietf.org>; Sat, 12 May 2012 16:51:09 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 8636D558008 for <gen-art@ietf.org>; Sat, 12 May 2012 16:51:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 272911BC8F4A; Sat, 12 May 2012 16:51:09 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.100] (pool-71-161-52-31.clppva.btas.verizon.net [71.161.52.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 959EE1BC8F48; Sat, 12 May 2012 16:51:08 -0700 (PDT)
Message-ID: <4FAEF784.6060501@joelhalpern.com>
Date: Sat, 12 May 2012 19:51:32 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4FAC34F6.20700@nostrum.com>
In-Reply-To: <4FAC34F6.20700@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org
Subject: [Gen-art]  review: draft-farrresnickel-ipr-sanctions-05.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 May 2012 23:51: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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-farrresnickel-ipr-sanctions-05.txt
     Sanctions Available for Application to Violators of IETF IPR Policy
Reviewer: Joel M. Halpern
Review Date: 12-May-2012
IETF LC End Date: 04-June-2012
IESG Telechat date: N/A

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

Issues: None

From christer.holmberg@ericsson.com  Mon May 14 00:34:41 2012
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 782AE21F85C4 for <gen-art@ietfa.amsl.com>; Mon, 14 May 2012 00:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.154
X-Spam-Level: 
X-Spam-Status: No, score=-6.154 tagged_above=-999 required=5 tests=[AWL=0.094,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U6YBN25fKty9 for <gen-art@ietfa.amsl.com>; Mon, 14 May 2012 00:34:39 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF6F21F85A8 for <gen-art@ietf.org>; Mon, 14 May 2012 00:34:39 -0700 (PDT)
X-AuditID: c1b4fb2d-b7bc5ae00000796a-7c-4fb0b58ef7b1
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 5A.7E.31082.E85B0BF4; Mon, 14 May 2012 09:34:38 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.64]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Mon, 14 May 2012 09:34:37 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org" <draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org>
Date: Mon, 14 May 2012 09:34:36 +0200
Thread-Topic: Genart review of draft-ietf-pkix-cmp-transport-protocols-18
Thread-Index: Ac0xoqdXoxjsfzuuSE+UhyHHLVaitg==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C4442A39D@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F2072F1E0DE894DA4B517B93C6A05852C4442A39DESESSCMS0356e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [Gen-art] Genart review of draft-ietf-pkix-cmp-transport-protocols-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 07:34:41 -0000

--_000_7F2072F1E0DE894DA4B517B93C6A05852C4442A39DESESSCMS0356e_
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-pkix-cmp-transport-protocols-18.txt
Reviewer: Christer Holmberg
Review Date: 14 May 2012
IETF LC End Date: 21 May 2012
IESG Telechat date: 24 May 2012

Summary: The draft is ready for publication, but with a number of editorial=
 nits.

Major issues: -

Minor issues: -

Nits/editorial comments:


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

Q1-1: In my opinion the following statement (1st paragraph) can be removed:

   "This document defines the transport mechanism which was removed from th=
e main CMP specification
   with the second release and referred to be in a separate document."



Because, the following paragraphs describes very well the background, and j=
ustification of the new transport. There is no need to say whether the new =
transport was originally supposed to be part of the main spec or not.



Q1-2: In the 2nd paragraph, please add reference to HTTP on first occurrenc=
e.





Q1-3: The following statement is a little confusing:



   "During the long time it existed as draft, this RFC was undergoing drast=
ic changes."



There hasn't been any changes to the RFC, but to the draft. So, I would say=
 something like:



            "Before this document was published as an RFC, the draft versio=
n underwent drastic changes during the work process."





Section 2:

-----------



Q2-1: The section only contains the RFC 2119 terminology, but that is norma=
lly in a "Conventions" section.



Q2-2: As there are no requirements listed, I suggest to remove the section.







Section 3.2:

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



Q3_2-1: The text says:



"However, neither HTTP nor this protocol are designed to correlate messages=
 on the same

            connection in any meaningful way;"



It is a little unclear what "this protocol" refers to.







Section 4:

-----------



Q4-1: It is a little unclear what is meant by "legacy implementations". Do =
you consider implementations based on earlier versions of the draft as "leg=
acy"? In my opinion a "legacy" implementation is based on a previously publ=
ished standard/RFC.



So, if the section is supposed to cover issues with earlier versions of thi=
s draft, I think it should be called something else.





Regards,



Christer

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:"Tahoma","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif";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; http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&g=
t;.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0=
pt;font-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";color:black'>Please wait for direction from your document sh=
epherd or AD before posting a new version of the draft.<o:p></o:p></span></=
p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma"=
,"sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:bl=
ack'>Document: draft-ietf-pkix-cmp-transport-protocols-18.txt<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"T=
ahoma","sans-serif";color:black'>Reviewer: Christer Holmberg<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif";color:black'>Review Date: 14 May 2012<o:p></o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";color:black'>IETF LC End Date: 21 May 2012<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif";color:black'>IESG Telechat date: 24 May 2012<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";col=
or:black'>Summary: The draft is ready for publication, but with a number of=
 editorial nits.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-f=
amily:"Tahoma","sans-serif";color:black'>Major issues: -<o:p></o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:b=
lack'>Minor issues: -<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p>&n=
bsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;f=
ont-family:"Tahoma","sans-serif";color:black'>Nits/editorial comments:<o:p>=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-=
family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><div>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif";color:black'>&nbsp;<o:p></o:p></span></p></div><div><p class=3D=
MsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"=
;color:black'>Section 1:<o:p></o:p></span></p></div><div><p class=3DMsoNorm=
al><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:=
black'>-----------&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p=
>&nbsp;</o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Q1-1: In my opi=
nion the following statement (1st paragraph)&nbsp;can be removed:<o:p></o:p=
></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt=
;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p=
></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-famil=
y:"Tahoma","sans-serif";color:black'>&nbsp;&nbsp; &quot;This document defin=
es the transport mechanism which was removed from the main CMP specificatio=
n<br>&nbsp;&nbsp; with the second release and referred to be in a separate =
document.&quot;<o:p></o:p></span></p></div><p><span style=3D'font-size:10.0=
pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span><=
/p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";col=
or:black'>Because, the following paragraphs describes very well the backgro=
und, and justification of the new transport. There is no need to say whethe=
r&nbsp;the new transport&nbsp;was originally supposed to be part of the mai=
n spec or not.<o:p></o:p></span></p><div><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p>&n=
bsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;f=
ont-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><=
/div><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";c=
olor:black'>Q1-2: In the 2nd paragraph, please add reference to HTTP on fir=
st occurrence.<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font=
-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><=
span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:blac=
k'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-fami=
ly:"Tahoma","sans-serif";color:black'>Q1-3: The following statement is a li=
ttle confusing:<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;fon=
t-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p>=
<span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:bla=
ck'>&nbsp;&nbsp;&nbsp;&quot;During the long time it existed as draft, this =
RFC was undergoing drastic changes.&quot;<o:p></o:p></span></p><p><span sty=
le=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp=
;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Taho=
ma","sans-serif";color:black'>There hasn&#8217;t been any changes to the RF=
C, but to the draft. So, I would say something like:<o:p></o:p></span></p><=
p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:b=
lack'><o:p>&nbsp;</o:p></span></p><p><span style=3D'font-size:10.0pt;font-f=
amily:"Tahoma","sans-serif";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Before this document was published =
as an RFC, the draft version underwent drastic changes during the work proc=
ess.&#8221;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-fa=
mily:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><spa=
n style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:=
"Tahoma","sans-serif";color:black'>Section 2:<o:p></o:p></span></p><p><span=
 style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>-=
----------<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-fam=
ily:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p><p><span=
 style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Q=
2-1: The section only contains the RFC 2119 terminology, but that is normal=
ly in a &#8220;Conventions&#8221; section.<o:p></o:p></span></p><p><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p=
>&nbsp;</o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tah=
oma","sans-serif";color:black'>Q2-2: As there are no requirements listed, I=
 suggest to remove the section.<o:p></o:p></span></p><p><span style=3D'font=
-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>&nbsp;<o:p></o:=
p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-=
serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span style=3D'font-size=
:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></s=
pan></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif=
";color:black'>Section 3.2:<o:p></o:p></span></p><p><span style=3D'font-siz=
e:10.0pt;font-family:"Tahoma","sans-serif";color:black'>-------------<o:p><=
/o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sa=
ns-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span style=3D'font-s=
ize:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Q3_2-1:&nbsp;The =
text says:<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-fam=
ily:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p style=
=3D'text-indent:36.0pt'><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";color:black'>&#8220;However, neither HTTP nor this protocol =
are designed to correlate messages on the same<o:p></o:p></span></p><p><spa=
n style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; connection in=
 any meaningful way;&#8221;<o:p></o:p></span></p><p><span style=3D'font-siz=
e:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></=
span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-seri=
f";color:black'>It is a little unclear what &#8220;this protocol&#8221; ref=
ers to.<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family=
:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p=
>&nbsp;</o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tah=
oma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Section=
 4:<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif";color:black'>-----------<o:p></o:p></span></p><p><span s=
tyle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:=
p>&nbsp;</o:p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif";color:black'>Q4-1: It is a little unclear what is meant =
by &#8220;legacy implementations&#8221;. Do you consider implementations ba=
sed on earlier versions of the draft as &#8220;legacy&#8221;? In my opinion=
 a &#8220;legacy&#8221; implementation is based on a previously published s=
tandard/RFC.<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-f=
amily:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><sp=
an style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'=
>So, if the section is supposed to cover issues with earlier versions of th=
is draft, I think it should be called something else.<o:p></o:p></span></p>=
<p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:=
black'>&nbsp;<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-=
family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><s=
pan style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black=
'>Regards,<o:p></o:p></span></p><p><span style=3D'font-size:10.0pt;font-fam=
ily:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p><span=
 style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>C=
hrister<o:p></o:p></span></p></div></body></html>=

--_000_7F2072F1E0DE894DA4B517B93C6A05852C4442A39DESESSCMS0356e_--

From elwynd@dial.pipex.com  Mon May 14 08:47:58 2012
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2D9421F87E1 for <gen-art@ietfa.amsl.com>; Mon, 14 May 2012 08:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.482
X-Spam-Level: 
X-Spam-Status: No, score=-100.482 tagged_above=-999 required=5 tests=[AWL=-1.083, BAYES_50=0.001, J_CHICKENPOX_21=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-GmddZB8v1Z for <gen-art@ietfa.amsl.com>; Mon, 14 May 2012 08:47:54 -0700 (PDT)
Received: from b.c.painless.aa.net.uk (c.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e35]) by ietfa.amsl.com (Postfix) with ESMTP id 1BE0B21F87D3 for <gen-art@ietf.org>; Mon, 14 May 2012 08:47:54 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by c.painless.aaisp.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1STxV3-0004z6-Ms for gen-art@ietf.org; Mon, 14 May 2012 16:47:53 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Mon, 14 May 2012 16:47:51 +0100
Message-Id: <1337010471.23527.1663.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-art test - please ignore
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 15:47:58 -0000

PLEASE IGNORE THIS MESSAGE - TESTING SP*M FILTER PROBLEM
I am the assigned Gen-ART reviewer 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-codec-opus-12.txt
Reviewer:  Elwyn Davies
Review Date:  14 May 2012 (completed)
IETF LC End Date: 10 May 2012
IESG Telechat date: (if known) -

Summary: 
Before offering some views on the document, let me say that this piece
of work seems to be a tour de force on behalf of its developers.  It is
certainly one of the (if not the) most technically complex pieces of
work that has been presented to the IETF, and is far more mathematically
complex and rigorous than our usual run of standards.  It is also
perhaps a vindication of the rough concensus and running code
philosophy. So congratulations to the authors and the companies that
have supported this work.  But back to the review....

I came to this review with a very outdated view of what goes on inside
codecs, so it was rather a shock to the system.  Taking that into
account, I think that some additional high level, up front description
of the two parts (SILK and CELT) and the range encoding system would
make it easier for future (naive) readers and potential implementers to
understand what is going on.  For example, after struggling with the
description of CELT in the decoder (s4.3) I found that going off and
reading the slides on CELT presented at IETF 79 helped considerably.
Such additions might also help future dissemination of the technique by
giving potential users a quick overview.  It would also make it easier
to justify the decision to postpone the high level (and highly
mathematical/technical) view to section 5 after the detailed description
of the decoder.

I also found that the descriptions of the SILK and CELT decoders
appeared to be written with a different perspective (see detailed
comments) doubtless by different authors.  This is not ideal and,
despite the expected further increase in page count, some additional
text in s4.3 seems desirable.

By far the most difficult to parse section is 4.3.3 talking about bit
allocation in CELT.  Despite considerable study, I didn't feel I had
really got to grips with how this worked.  An example might help.

Finally, the most contentious aspect of this document is the requirement
to treat the code as normative.  There are just over 30,000 physical
lines of code and I haven't checked them hardly at all.  Slocount
reckons this represents 7.14 man years of effort.  As with the document,
there is a discrepancy between CELT and SILK with the latter code being
more heavily commented, especially as regards routine parameters.  A
proper validation of the claim that the code implements the description
would take several weeks of time: I guess that we have to take the
document shepherd's assurances on this.  One issue is that both code and
document are pretty much saturated with what we used to call 'magic
numbers'.  Although these are explained in the document, it does not
appear that this is always the case in the code.  I would also be
happier if the code contained Doxygen (or similar) dcoumentation
statements for all routines (rather than just the API).

So overall, the work is something that ought to be standardized but the
document needs further work - not quite ready for the IESG. 

Major issues: 
Can we accept the code as normative?  If not how do we proceed?

Minor issues:
Contrast between decoder descriptions of LP part and CELT part:  The
SILK descriptions go into gory detail on the values used in lots of
tables, etc., whereas the CELT part has a very limited treatment of the
numeric values used (assuming reliance on finding the values in the
reference implementation, either explictly or implicitly).  There are
things to be said for both techniques.  I was wondering (while reading
the SILK description) if the authors have any means of automatically
generating the tables from the code in the SILK part (or vice versa) to
avoid double maintenance. On the other hand, there are pieces of the
CELT decoder description (especially in s4.3.3 where knowing numbers of
bands, etc.) where some actual numbers would help comprehension.

s2 (and more generally):  The splitting of the signal in the frequency
domain into signal (components?) below and above 8kHz in the hybrid case
presumably requires that the output of the CELT encoder is windowed so
that only one of encoders gnerates output below 8kHZ.  I think something
is needed in s2 to explain how this is managed (presumably to do with
energy bands?).  I didn't find anything in s5 about what has to be done
for the encoder when running in hybrid mode which surprised me somewhat.

s4.1: Despite having found a copy of the range coding paper and tried to
read it, I found the description of range coding opaque (there are some
more words later in s5 but this is a bit late for understanding the
decoder).  Given that this is (I think) fairly novel, some additional
less opaque description could be very helpful to people trying to
understand what is going on. In particular knowledge of how entropy
coding works is pretty much a prerequisite. 

s4.2.5, para 3:
>    When switching from 20 ms to 10 ms, the 10 ms
>    20 ms Opus frame, potentially leaving a hole that needs to be
>    concealed from even a single packet loss.
How?

s4.2.5, para 4: 
> In order to properly produce LBRR frames under all conditions, an
>    encoder might need to buffer up to 60 ms of audio and re-encode it
>    during these transitions.  However, the reference implementation
opts
>    to disable LBRR frames at the transition point for simplicity.
> 
Should this be phrased in RFC 2119 requiremenmts language?  The first
part sounds like a SHOULD with the second part being the get out , but
its not entirely clear what the consequences are other then simplicity.


======================================================================
            MINOR ISSUES ABOVE submitted as part 1 of review
======================================================================
general/s11.2:  Several references [Hadamard], [Viterbi}, etc., are to
Wikipaedia pages.  Whilst these are convenient (and only illustrative)
they are not guaranteed to be very stable.  Better (i.e., more stable)
references are desirable.

s1, para 2:
>    The decoder contains a great deal of integer and fixed-point
>    arithmetic which must be performed exactly, including all rounding
>    considerations,...
Is this a MUST?  There are instances in the text which might contradict
this (e.g., para 1 of s4.2.7.5 which has (capitalized) SHOULDs).

s4.3:
As a complete newcomer to CELT, I would have appreciated a more high
level understanding of what CELT is doing at this point.  I  tried
reading s4.3 without any additional input and found it very hard going.
Eventually I gave up and went looking for some additional input.  This
presentation seems to have a useful view 
http://www.ietf.org/proceedings/79/slides/codec-2.pdf

I think that it would be extremely helpful to have a description similar
to this at this point in the document, even though there is some
material in section 5.3 which could also be forward referenced.  Still
the material in s5.3 does not start from the basic principles that CELT
is using, and since these are essentially novel, it would be very good
to give prospective implementers/users an understanding of what is going
on.  Incidentally, I found the above IETF presentation more useful than
http://www.celt-codec.org/presentations/misc/lca-celt.pdf
Note that the SILK part seems rather less opaque.  It would also be
useful to indicate numerically how many bands are involved and what the
number of MDCT bins are in the various bands. 

s4.3, last para: Can the 'out of range error' occur in the LP decoder?
(if not why not?)

======================================================================

Nits/editorial comments: 

global: bytes -> octets
global: The form/terminology Q<n> (e.g., Q13, Q15, Q16) ought to be
explained.

s1: Expand CELP

s1.1.6: Need to define floor().

s2: ? Expand SILK

s2: Reference for Vorbis.

s2.1.8: Expand AAC (and MP3).

s3: References for Ogg, Matroska, maybe RTP.

s3: Fig 1, Table 2 and intervening text:  Presumably SILK only (Table 2)
etc correspond to MODES 1-3 in Figure 1. This needs to be consistent.

s3.2.1: Make it clear which of the octets is len[0]/len[1].  To be
precise it might be better to say len0/len1 are the values of the two
length octets (in whichever order you intend). The form len[0] could be
misinterpreted as a function 'length of 0'.

s3.2.5: better s/figure below/Figure 5/

s3.2.5:
> In the CBR case, the compressed length of each frame in bytes is
>    equal to the number of remaining bytes in the packet after
>    subtracting the (optional) padding, (N-2-P), divided by M. This
>    number MUST be a non-negative integer multiple of M.
'This number' is not the  compressed length of each frame that is the
subject of the first sentence, but the number of remaining octets - this
needs rewording.

s3.2.5:
> The number of header bytes (TOC byte, frame
>    count byte, padding length bytes, and frame length bytes), plus the
>    length of the first M-1 frames themselves, plus the length of the
>    padding MUST be no larger than N, the total size of the packet.
Surely this is a non sequitur? This might be better phrased as 'The
total size of a well formed packet MUST be at least...' 

s3.3: The example diagrams ought to have figure numbers.

s3.4: I am not keen on duplicating normative requirements in this way
(double maintenance issue).  It would be better to put explicit numbered
requirements in the sections above an reference the resulting numbers
here. 

s4.1:
> The decoder initializes rng to 128 and initializes val to
>    127 minus the top 7 bits of the first input octet. 
How are the 'top seven bits' to be interpreted here? e.g. as the bottom
seven bits of a 8 bit integer field? an 8 bit integer with the lowest
bit zeroed out?


s4.1.1:  This is really a global point.  This section refers to
entdec.c.  Presumably (since we haven't reached the code yet) and it is
still compressed, there is some file structure.  I don't think this has
been said above.  It would be good to provide a list of the file
components (i.e., sectional structure of the code) at the start, maybe
even  giving line number positions within the decompressed code.


s4.1.1.1:
> Then it reads the next octet of the
>    payload and combines it with the left-over bit buffered from the
>    previous octet to form the 8-bit value sym.  It takes the left-over
>    bit as the high bit (bit 7) of sym, and the top 7 bits of the octet
>    it just read as the other 7 bits of sym.
This is not well phrased.  Better
     Then it reads the next octet of the payload [packet? payload hasn't
really been used before] and combines the left  over bit from the
previous octet (see Section 4.1 for starting this process) as the high
bit (bit 7)| of 'sym' and the top 7 bits of the octet as the other 7
bits of sym, leaving the remaining bit for the next iteration.  

s4.1.5.2:
Should r_Q15 = rng >> (l-16) be r_Q15 = rng >> (lg-16)?  There doesn't
seem to be an 'l' defined.

s4.2.1: Expand LTP earlier. It would also be useful to expand LPC again.
 
s4.2.2: acronym VAD is not expanded until the beginning of s4.2.3.

s4.2.7: acronym LSF needs to be expanded on first use.

s4.2.7.1: Explain briefly why Table 7 has values for indices 0 to 15
when wi0/1 are in range 0 to 14.

s4.2.7.4, para below Table 12:
> These 6 bits are combined to form a gain index between 0 and 63.

s/gain index/gain_index/ as this variable is used subsequently.

s4.2.7.4: The use of log_gain seems slightly confusing when combined
with gain_index.  One at least is presumably log scaled.  Maybe a bit
more explanation is needed.

======================================================================
            COMMENTS ABOVE submitted as part 1 of review
======================================================================
General: Define L1 and L2 (as in L1-norm, etc).

s4.2.7.2, last para:
> In that case, if this
>    flag is zero (indicating that there should be a side channel), then
>    Packet Loss Concealment (PLC, see Section 4.4) SHOULD be invoked to
>    recover a side channel signal.
What are the consequences (or what actions need to be taken) if it is
not invoked?

s4.2.7.5, para 1:
> These represent the interleaved zeros on the
>    unit circle between 0 and pi (hence "normalized") in the standard
>    decomposition of the LPC filter into a symmetric part and an anti-
>    symmetric part (P and Q in Section 4.2.7.5.6).
'on the unit circle between 0 and pi' might be clearer as 'on the upper
half of the unit circle' or 'on the half of the unit circle in the
positive imaginary area of the complex plane'.
'standard decomposition'?  Needs a reference.

s4.2.7.5, para 1: A reference for the use of LSF in LPC would be useful.

s4.2.7.5.x: There is inconsistent use of stage 1/stage 2 vs
stage-1/stage-2.  Please be consistent.

s4.2.7.5, para 1:
>    Because of non-linear
>    effects in the decoding process, an implementation SHOULD match the
>    fixed-point arithmetic described in this section exactly.  An
encoder
>    SHOULD also use the same process.
- Does this contradict the 'must' in s1, para 2?
- What are the consequences of ignoring the SHOULD?  How bad would they
get?  Might it become unstable and how would one know?

s4.2.7.5.1, para 1: s/This indexes an element in a coarse codebook,
   selects the PDFs for the second stage of the VQ/This indexes an 
   element in a coarse codebook that selects the PDFs for the second
stage 
   of the VQ/

s4.2.7.5.3, last para: 
> However, nothing in
>    either the reconstruction process or the quantization process in
the
>    encoder thus far guarantees that the coefficients are monotonically
>    increasing and separated well enough to ensure a stable filter.
A reference that indicates why this requirement is needed would be
desirable.
(and also for s4.2.5.7.8).

s4.2.7.5.4 and Table 25: Are the values in Table 25 NDeltaMin or
NDelatMin_Q15?
The equations after Table 25 use both NDeltaMin and NDeltaMin_Q15.  Is
this correct?
In particular the first two equations deliver _Q15 values but use raw
NDeltaMin.

s4.1.1/s4.2.7.1 and other places:  The term 'exact integer division' is
used in various places.  My understanding was that this phrase implied
that it was known that the dividend was an exact multiple of the divisor
by some out-of-band means.  This doesn't seem to be the case generally
in Opus (e.g,, where both n/5 and n%5  are needed - clearly this doesn't
anticipate n%5 == 0 every time!)  So what does 'exact integer division'
imply?  A definition may be needed. 

s4.3, last para: s/described in the figure above./described in Table 55
above./

s4.3.1: 
> The "transient" flag encoded in the bitstream has a probability of
1/8. 
This statement appears out of the blue apparently.  Some more
explanation of what the transient flag actually implies and why we
should be so sure about its PDF would help.

s4.3.2.1: Arguably a reference is needed for the z-transform.

s4.3.2.1: Avoid the equation picture splitting across page boundaries.
in the current version it is unclear what the denominator is. (use
needLines processing direcrive in xml2rfc).  Same applies to the
equation below Table 57 in s4.3.4.3.

4.3.2.1, after the equations:
> The
>    prediction is clamped internally so that fixed point
implementations
>    with limited dynamic range do not suffer desynchronization.
As a person with limited skills in the srt, I have no idea what
desynchronization implies here. 

4.3.2.1, ibid:
> We
>    approximate the ideal probability distribution of the prediction
>    error using a Laplace distribution with separate parameters for
each
>    frame size in intra- and inter-frame modes.
I suspect this sentence belongs before the equation described the
z-transform.
Where are the values of the parameters for the inter-frame mode defined
(the intra-frame ones are in the text)?

s4.3.2.3: Paragraph on decoding band boosts:  Might be improved by using
equations rather than the wordy descriptions used at present.

(global)s4.3.2.3, para above table 56: s/iff/if and only if/

s4.3.2.3: LOG2_FRAC_TABLE is missing.

s4.3.3: It would be helpful to explain either here, or at the outset of
s4.3 overall, how the concept of energy bands and MDCT bins applies to
the CELT part of the codec, and just how many bands and bins are used.
Some of this is contained in s5.3.2, but the magic number 17 appears
later in 4.3.3 which is presumably something to do with the point in the
frequency domain that CELT takes over from LP in the hybrid mode.  It
would make the very complex section 4.3.3 rather easier to understand
with this extra information - I have to say I struggled!  On reflection,
I think an example of what bits are allocated to a band and how thay rae
subsequently used would be quite helpful - Without going to delve into
the code I am really not clear that I understand just what bits are
allocated and what they then encode and I have read the text quite a few
times now.

s4.3.3: Be consistent between 'tone to noise' and 'tone-to-noise'.

s4.3.3:
>    The band-energy normalized structure of Opus MDCT mode ensures that
a
>    constant bit allocation for the shape content of a band will result
>    in a roughly constant tone to noise ratio, which provides for
fairly
>    consistent perceptual performance.  The effectiveness of this
>    approach is the result of two factors: that the band energy, which
is
>    understood to be perceptually important on its own, is always
>    preserved regardless of the shape precision, and because the
constant
>    tone-to-noise ratio implies a constant intra-band noise to masking
>    ratio.  Intra-band masking is the strongest of the perceptual
masking
>    effects.  This structure means that the ideal allocation is more
>    consistent from frame to frame than it is for other codecs without
an
>    equivalent structure.
This paragraph contains a number of interesting assertions:  Is there a
reference where one could see them justified (it may be that this is the
result of original research in the Opus team).
 
s4.3.3, paragraphs after the bullet points:  The concepts of 'shape' and
'shape encoding' is introcuced here without explicit definition.  Are we
talking about the shape windowing used in FFT/MDCT here? This should be
made clear.

s4.3.3, 5th para after bullet points: s/In the reference the maximums/In
the reference implementation the maximums/

s4.3.3, 6th para after the bullet points:  A table of bands per mode and
number of MDCT bins  covered would be helpful here in order to  get a
feeling for the scale of the problem.  Also the cache_caps50 table in
the code contains the magic number 168.  Where does this come from?

s4.3.3, 6th para after the bullet points:
> set LM to the shift value for the frame size (e.g. 0 for 120, 1 for
>    240, 3 for 480),  
Where do these frame sizes get specified? And what is the total set of
frame sizes? The text says 'e.g.' (which incidentally should be 'e.g.,')
implying that this is not the complete set.

s4.3.3, 6th para after the bullet points: Need to define 'truncating
integer division' to go with 'exact integer division'.

s4.3.3, 7th para after the bullet points: 
> The band boosts are represented by a series of binary symbols which
>    are coded with very low probability.
How many, at least, and what values?  Are these range encoded? I don't
see them in the table above or with a PDF specified.

s4.3.3, 7th para after the bullet points:
>    and every time
>    a band is boosted the initial cost is reduced (down to a minimum of
>    two).
Would that be a value of two or two bits? 
  
s4.3.3: Paragraph on decoding band boosts:  Might be improved by using
equations rather than the wordy descriptions used at present.

(global)s4.3.3, para above table 56: s/iff/if and only if/

s4.3.3, 2nd para after Table 56: 
> For stereo frames, bits are reserved for intensity stereo and for
>    dual stereo.  Intensity stereo requires ilog2(end-start) bits.
The terms 'intenmsity stereo' and 'dual stereo' don't appear to have
been defined.

s4.3.3: LOG2_FRAC_TABLE is missing.

4.3.4.3, last para:
>    If the decoded vector represents more than one time block, then the
>    following process is applied separately on each time block. 
Should this sentence come before the previous paragraph?  There  isn't
really a 'following process' in this section and I don't think it menas
the process in s4.3.4.4?


s4.3.4.3, last sentence: 
> This extra rotation is applied in an interleaved manner with a stride
>    equal to round(sqrt(N/nb_blocks))
I think this needs some more explanation for the uninitiated.

s4.3.4.4:
> Multiple levels of splitting may be
>    applied up to a frame size dependent limit. 
What this limit is does not appear to be defined.

s4.3.5: The 'collapse' phenomenon is not fully defined, and it would be
useful to mention why it happens.  Also s/min/minimum/.

s4.3.6: s/Just like/Just as/

s4.3.7, last para: I think 'power complementarity' requires further
explanation or a reference.

s4.5, para 3: s/To avoid or reduces glitches during these/To avoid or
reduce glitches during these/

s4.5.1.1, para 1: s/For for SILK-only/For SILK-only/

s4.5.1.4, para 2: s/redundant frame is as-is,/redundant frame as-is,/

s5, figure 16: The Optional High-pass Filter box has two spurious '+'
symbols on the vertical sides. 

s5, last para:  A reference for the Auto Regressive Moving Average
(ARMA) filter would be useful.

s5.2.3.4.2.1, title: s/Burgs method/Burg's Method/

s5.2.3.5, para 2: Expand 'R/D performance' (or probably specify it as
abbreviation for rate-distortion in para 1).

s5.3.5, para 1 below equation: Is E an abbreviation for 'extra'?

s5.3.6: The abbreviation RD for rate-distortion is defined here (see
comment on s5.2.3.5).

s6.1: This section is perhaps a little 'triumphalist' for the reference
implementation (this may of course be justified!.  The quality metric is
a 'relative quality metric' and presumably if someone does a *really*
good job of coding, it is entirely possible that the new algorithms
might get better than 100 on the quality score (i.e., provide a better
answer than the reference implementation).

s6.2: Just wondering, but is non-standard frame size the only option
offered by Opus Custom?  If not, probably more text is needed here.  Are
there any major changes to the algorithms implied by the use of Opus
Custom?

s7.  Referencing SECGUIDE (RFC 3552) seems inappropriate since it occurs
in such a security considerations section. Just omit it.

s11.2: A number of references are to Wikipaedia pages.  While these were
useful to me in refreshing or initializing my knowledge, they are not
usually considered adequately stable for use in RFCs.  I fear you may
have to provide more stable references.

Appendix A: I checked that the code extracted as inicated and was able
to be compiled under Ubuntu 10.04 LTS.









  





From ben@nostrum.com  Mon May 14 12:11:56 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC3D421F88D0; Mon, 14 May 2012 12:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.45
X-Spam-Level: 
X-Spam-Status: No, score=-101.45 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3, SPF_PASS=-0.001,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KkKuTJch2xw7; Mon, 14 May 2012 12:11:56 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB7721F88C9; Mon, 14 May 2012 12:11:55 -0700 (PDT)
Received: from dn3-123.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q4EJBs4E074214 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 14 May 2012 14:11:55 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 May 2012 14:12:10 -0500
Message-Id: <6D18CD1E-FBB8-43F7-8D82-46667AA2075B@nostrum.com>
To: draft-ietf-ccamp-assoc-info.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC Review of draft-ietf-ccamp-assoc-info-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 19:11:57 -0000

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

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

Document: draft-ietf-ccamp-assoc-info-03
Reviewer: Ben Campbell
Review Date: 2012-06-14
IETF LC End Date: 2012-06-14

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

Major issues:

None

Minor issues:

None

Nits/editorial comments:

-- 2.1, 1st paragraph:

Please expand RSVP-TE on first mention.

-- 2.1, 2nd paragraph: "...can take place independent from..."

s/independent/independently

-- 2.2, paragraph 5: "... definition of the Association ID, which is =
(quoting [RFC4872]):"

The quoted text this refers to is more of a description of use than a =
definition.=

From adrian@olddog.co.uk  Mon May 14 12:44:24 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD0221F8767 for <gen-art@ietfa.amsl.com>; Mon, 14 May 2012 12:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.52
X-Spam-Level: 
X-Spam-Status: No, score=-2.52 tagged_above=-999 required=5 tests=[AWL=0.079,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oef4b8Gku1yP for <gen-art@ietfa.amsl.com>; Mon, 14 May 2012 12:44:23 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id F209A21F866E for <gen-art@ietf.org>; Mon, 14 May 2012 12:44:22 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q4EJiL9c016076;  Mon, 14 May 2012 20:44:21 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q4EJiJrE016060 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 14 May 2012 20:44:20 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Ben Campbell'" <ben@nostrum.com>, <draft-ietf-ccamp-assoc-info.all@tools.ietf.org>
References: <6D18CD1E-FBB8-43F7-8D82-46667AA2075B@nostrum.com>
In-Reply-To: <6D18CD1E-FBB8-43F7-8D82-46667AA2075B@nostrum.com>
Date: Mon, 14 May 2012 20:44:19 +0100
Message-ID: <02d501cd3209$f4e1ddf0$dea599d0$@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: AQKPYG+EoWR2PH09lv7vuPvRHMMBhZVFUdNQ
Content-Language: en-gb
Cc: gen-art@ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-ccamp-assoc-info-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 19:44:24 -0000

Thanks Ben.

All entered as RFC Editor notes except the last one...


> -- 2.2, paragraph 5: "... definition of the Association ID, which is (quoting
> [RFC4872]):"
> 
> The quoted text this refers to is more of a description of use than a
definition.

I agree, but don't think any change is needed. The full text here is...

   They
   also share the same definition of the Association ID, which is
   (quoting [RFC4872]):

      "The Association ID MUST be set to the LSP ID of the LSP being
      protected by this LSP or the LSP protecting this LSP.  If unknown,
      this value is set to its own signaled LSP ID value (default).
      Also, the value of the Association ID MAY change during the
      lifetime of the LSP."

Thus "which is" means "and here is a description".

If you feel really strongly we can probably work something out. 

A


From ben@nostrum.com  Mon May 14 12:52:08 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 954D321F88D0 for <gen-art@ietfa.amsl.com>; Mon, 14 May 2012 12:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.313
X-Spam-Level: 
X-Spam-Status: No, score=-102.313 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W5XGNiROVG0T for <gen-art@ietfa.amsl.com>; Mon, 14 May 2012 12:52:08 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 12A6B21F85D1 for <gen-art@ietf.org>; Mon, 14 May 2012 12:52:07 -0700 (PDT)
Received: from dn3-123.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q4EJq6VS080330 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 14 May 2012 14:52:07 -0500 (CDT) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <02d501cd3209$f4e1ddf0$dea599d0$@olddog.co.uk>
Date: Mon, 14 May 2012 14:52:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <38397590-FB4B-43B6-A6AF-08F0D97B0181@nostrum.com>
References: <6D18CD1E-FBB8-43F7-8D82-46667AA2075B@nostrum.com> <02d501cd3209$f4e1ddf0$dea599d0$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1278)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: gen-art@ietf.org, draft-ietf-ccamp-assoc-info.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-ccamp-assoc-info-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 19:52:08 -0000

On May 14, 2012, at 2:44 PM, Adrian Farrel wrote:

> Thanks Ben.
>=20
> All entered as RFC Editor notes except the last one...
>=20
>=20
>> -- 2.2, paragraph 5: "... definition of the Association ID, which is =
(quoting
>> [RFC4872]):"
>>=20
>> The quoted text this refers to is more of a description of use than a
> definition.
>=20
> I agree, but don't think any change is needed. The full text here =
is...
>=20
>   They
>   also share the same definition of the Association ID, which is
>   (quoting [RFC4872]):
>=20
>      "The Association ID MUST be set to the LSP ID of the LSP being
>      protected by this LSP or the LSP protecting this LSP.  If =
unknown,
>      this value is set to its own signaled LSP ID value (default).
>      Also, the value of the Association ID MAY change during the
>      lifetime of the LSP."
>=20
> Thus "which is" means "and here is a description".
>=20
> If you feel really strongly we can probably work something out.=20

No problem at all. It was pedantic enough that I almost didn't include =
it :-)


From martin.peylo@nsn.com  Tue May 15 09:13:07 2012
Return-Path: <martin.peylo@nsn.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAF3321F8740 for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 09:13:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PcnWTpWAF-yS for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 09:12:59 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 7BE8721F878B for <gen-art@ietf.org>; Tue, 15 May 2012 09:12:58 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q4FGCrjG016268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 May 2012 18:12:53 +0200
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q4FGCoAt031008; Tue, 15 May 2012 18:12:50 +0200
Received: from FIESEXC006.nsn-intra.net ([10.159.0.14]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 May 2012 18:12:14 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CD32B5.7BD9515E"
Date: Tue, 15 May 2012 19:12:10 +0300
Message-ID: <3BF363C82C184B46930A905352C2013F021E39F1@FIESEXC006.nsn-intra.net>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852C4442A39D@ESESSCMS0356.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Genart review of draft-ietf-pkix-cmp-transport-protocols-18
Thread-Index: Ac0xoqdXoxjsfzuuSE+UhyHHLVaitgBDSLxQ
References: <7F2072F1E0DE894DA4B517B93C6A05852C4442A39D@ESESSCMS0356.eemea.ericsson.se>
From: "Peylo, Martin (NSN - FI/Espoo)" <martin.peylo@nsn.com>
To: "ext Christer Holmberg" <christer.holmberg@ericsson.com>, <gen-art@ietf.org>, <draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org>
X-OriginalArrivalTime: 15 May 2012 16:12:14.0550 (UTC) FILETIME=[7DD9AF60:01CD32B5]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 55911
X-purgate-ID: 151667::1337098376-00005945-90CFDA49/0-0/0-0
X-Mailman-Approved-At: Tue, 15 May 2012 09:24:48 -0700
Subject: Re: [Gen-art] Genart review of draft-ietf-pkix-cmp-transport-protocols-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2012 16:13:07 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CD32B5.7BD9515E
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01CD32B5.7BD9515E"


------_=_NextPart_002_01CD32B5.7BD9515E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Christer,

=20

thank you for your review and valuable nits. Please find my comments
inline, prefixed with an "MP".

=20

Attached, the so far unpublished (pre-)19 version of the draft
implementing the changes described below.

=20

Kind regards,

Martin

=20

From: ext Christer Holmberg [mailto:christer.holmberg@ericsson.com]=20
Sent: Monday, May 14, 2012 10:35 AM
To: gen-art@ietf.org;
draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org
Subject: Genart review of draft-ietf-pkix-cmp-transport-protocols-18

=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 wait for direction from your document shepherd or AD before
posting a new version of the draft.

=20

Document: draft-ietf-pkix-cmp-transport-protocols-18.txt

Reviewer: Christer Holmberg

Review Date: 14 May 2012

IETF LC End Date: 21 May 2012

IESG Telechat date: 24 May 2012

=20

Summary: The draft is ready for publication, but with a number of
editorial nits.

=20

Major issues: -

=20

Minor issues: -

=20

Nits/editorial comments:

=20

=20

Section 1:

-----------=20

=20

Q1-1: In my opinion the following statement (1st paragraph) can be
removed:

=20

   "This document defines the transport mechanism which was removed from
the main CMP specification
   with the second release and referred to be in a separate document."

=20

Because, the following paragraphs describes very well the background,
and justification of the new transport. There is no need to say whether
the new transport was originally supposed to be part of the main spec or
not.

=20

MP: Removed.

=20

=20

Q1-2: In the 2nd paragraph, please add reference to HTTP on first
occurrence.

=20

MP: although it's the first occurrence in 2nd paragraph, I would prefer
to add the references to RFC 1945 and RFC2616 to the 4th paragraph.
Reason is that 2nd paragraph contains only an historic reference - and
there (in RFC2510) it was not referenced what HTTP is either. See below
how the 4th paragraph will then look like when also fixing Q1-3.

=20

Q1-3: The following statement is a little confusing:

=20

   "During the long time it existed as draft, this RFC was undergoing
drastic changes."

=20

There hasn't been any changes to the RFC, but to the draft. So, I would
say something like:

=20

            "Before this document was published as an RFC, the draft
version underwent drastic changes during the work process."

=20

MP: Changed, I inserted "long-lasting" to highlight the long time it
took from draft-1 (June 22, 2000) to now. So the paragraph is now:

=20

   Before this document was published as an RFC, the draft version

   underwent drastic changes during the long-lasting work process.  The=20

   "TCP-Based Management Protocol" was enhanced and a TCP-Messages-over-

   HTTP transport specification appeared.  As both proved to be needless

   and cumbersome, implementers preferred to use plain HTTP transport

   following [RFC1945] or [RFC2616].  This document now reflects that by

   exclusively describing HTTP as transport protocol for CMP.

=20

Section 2:

-----------

=20

Q2-1: The section only contains the RFC 2119 terminology, but that is
normally in a "Conventions" section.

=20

Q2-2: As there are no requirements listed, I suggest to remove the
section.

=20

MP: This was totally missed so far. I will change this section to
"Conventions Used in This Document" as of course the RFC 2119
terminology is used throughout the document.

=20

Section 3.2:

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

=20

Q3_2-1: The text says:

=20

"However, neither HTTP nor this protocol are designed to correlate
messages on the same

            connection in any meaningful way;"

=20

It is a little unclear what "this protocol" refers to.

=20

MP: changed to "... neither HTTP nor the protocol specified in this
document are designed..."

=20

Section 4:

-----------

=20

Q4-1: It is a little unclear what is meant by "legacy implementations".
Do you consider implementations based on earlier versions of the draft
as "legacy"? In my opinion a "legacy" implementation is based on a
previously published standard/RFC.

=20

So, if the section is supposed to cover issues with earlier versions of
this draft, I think it should be called something else.

=20

MP: I'm following a proposal from Sean Turner here and take his
excellent suggestion to replace the complete section.

=20

> 4.  Implementation Considerations

>=20

>     Implementors should be aware that implementations might exist that

>     use a different approach for HTTP transport because this document

>     has been under development for more than a decade.  Further,

>     implementations based on earlier drafts of this

>     document might use an unregistered "application/pkixcmp-poll" MIME

>     type.

>=20

=20

=20

=20

Regards,

=20

Christer


------_=_NextPart_002_01CD32B5.7BD9515E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Mangal;
	panose-1:0 0 4 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
h2
	{mso-style-priority:9;
	mso-style-link:"Heading 2 Char";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:18.0pt;
	font-family:"Times New Roman","serif";
	font-weight:bold;}
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:12.0pt;
	font-family:Consolas;}
p
	{mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Arial","sans-serif";
	color:#1F497D;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.Heading2Char
	{mso-style-name:"Heading 2 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 2";
	font-weight:bold;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText>Hi =
Christer,<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>thank you for your review and valuable nits. Please =
find my comments inline, prefixed with an =
&#8220;MP&#8221;.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Attached, the so far unpublished (pre-)19 version =
of the draft implementing the changes described below.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Kind =
regards,<o:p></o:p></p><p class=3DMsoPlainText>Martin<o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ext Christer Holmberg [mailto:christer.holmberg@ericsson.com] =
<br><b>Sent:</b> Monday, May 14, 2012 10:35 AM<br><b>To:</b> =
gen-art@ietf.org; =
draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org<br><b>Subject:=
</b> Genart review of =
draft-ietf-pkix-cmp-transport-protocols-18<o:p></o:p></span></p></div></d=
iv><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at &lt; <a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://w=
iki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></span=
></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Please wait for direction from your document shepherd or AD before =
posting a new version of the draft.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Document: =
draft-ietf-pkix-cmp-transport-protocols-18.txt<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Reviewer: Christer Holmberg<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Review Date: 14 May 2012<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
IETF LC End Date: 21 May 2012<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
IESG Telechat date: 24 May 2012<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Summary: The draft is ready for publication, but with a number of =
editorial nits.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Major issues: -<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Minor issues: -<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Nits/editorial comments:<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Section 1:<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
-----------&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Q1-1: In my opinion the following statement (1st paragraph)&nbsp;can be =
removed:<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;&nbsp; &quot;This document defines the transport mechanism which =
was removed from the main CMP specification<br>&nbsp;&nbsp; with the =
second release and referred to be in a separate =
document.&quot;<o:p></o:p></span></p></div><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Because, the following paragraphs describes very well the background, =
and justification of the new transport. There is no need to say =
whether&nbsp;the new transport&nbsp;was originally supposed to be part =
of the main spec or not.<o:p></o:p></span></p><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D=
'>MP: Removed.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p></div><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Q1-2: In the 2nd paragraph, please add reference to HTTP on first =
occurrence.<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D=
'><o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>MP: although it&#8217;s the first occurrence in 2<sup>nd</sup> =
paragraph, I would prefer to add the references to RFC 1945 and RFC2616 =
to the 4<sup>th</sup> paragraph. Reason is that 2<sup>nd</sup> paragraph =
contains only an historic reference - and there (in RFC2510) it was not =
referenced what HTTP is either. See below how the 4<sup>th</sup> =
paragraph will then look like when also fixing =
Q1-3.<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Q1-3: The following statement is a little =
confusing:<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;&nbsp;&nbsp;&quot;During the long time it existed as draft, this =
RFC was undergoing drastic changes.&quot;<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
There hasn&#8217;t been any changes to the RFC, but to the draft. So, I =
would say something like:<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&#8220;Before this document was published as an RFC, the draft version =
underwent drastic changes during the work =
process.&#8221;<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D=
'><o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>MP: Changed, I inserted &#8220;long-lasting&#8221; to highlight the =
long time it took from draft-1 (June 22, 2000) to now. So the paragraph =
is now:<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>&nbsp;&nbsp; Before this document was published as an RFC, the draft =
version<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>&nbsp;&nbsp; underwent drastic changes during the long-lasting work =
process.&nbsp; The <o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>&nbsp;&nbsp;&nbsp;&quot;TCP-Based Management Protocol&quot; was =
enhanced and a TCP-Messages-over-<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>&nbsp;&nbsp; HTTP transport specification appeared.&nbsp; As both =
proved to be needless<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>&nbsp;&nbsp; and cumbersome, implementers preferred to use plain HTTP =
transport<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>&nbsp;&nbsp; following [RFC1945] or [RFC2616].&nbsp; This document now =
reflects that by<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>&nbsp;&nbsp; exclusively describing HTTP as transport protocol for =
CMP.<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Section 2:<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
-----------<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Q2-1: The section only contains the RFC 2119 terminology, but that is =
normally in a &#8220;Conventions&#8221; =
section.<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Q2-2: As there are no requirements listed, I suggest to remove the =
section.<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D=
'>MP: This was totally missed so far. I will change this section to =
&#8220;Conventions Used in This Document&#8221; as of course the RFC =
2119 terminology is used throughout the =
document.<b><o:p></o:p></b></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Section 3.2:<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
-------------<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Q3_2-1:&nbsp;The text says:<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p style=3D'text-indent:36.0pt'><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&#8220;However, neither HTTP nor this protocol are designed to correlate =
messages on the same<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; connection =
in any meaningful way;&#8221;<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
It is a little unclear what &#8220;this protocol&#8221; refers =
to.<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D=
'>MP: changed to &#8220;&#8230; neither HTTP nor the protocol specified =
in this document are =
designed&#8230;&#8221;<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Section 4:<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
-----------<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Q4-1: It is a little unclear what is meant by &#8220;legacy =
implementations&#8221;. Do you consider implementations based on earlier =
versions of the draft as &#8220;legacy&#8221;? In my opinion a =
&#8220;legacy&#8221; implementation is based on a previously published =
standard/RFC.<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
So, if the section is supposed to cover issues with earlier versions of =
this draft, I think it should be called something =
else.<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
&nbsp;<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
>MP: I&#8217;m following a proposal from Sean Turner here and take his =
excellent suggestion to replace the complete =
section.<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText>&gt; 4.&nbsp; =
Implementation Considerations<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;Implementors should be aware that =
implementations might exist that<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &nbsp;&nbsp;&nbsp;&nbsp;use a different =
approach for HTTP transport because this document<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &nbsp;&nbsp;&nbsp;&nbsp;has been under =
development for more than a decade.&nbsp; Further,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &nbsp;&nbsp;&nbsp;&nbsp;implementations based =
on earlier drafts of this<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;document might use an unregistered =
&quot;application/pkixcmp-poll&quot; MIME<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &nbsp;&nbsp;&nbsp;&nbsp;type.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <o:p></o:p></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Regards,<o:p></o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<o:p>&nbsp;</o:p></span></p><p><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
Christer<o:p></o:p></span></p></div></body></html>
------_=_NextPart_002_01CD32B5.7BD9515E--

------_=_NextPart_001_01CD32B5.7BD9515E
Content-Type: text/plain;
	name="draft-ietf-pkix-cmp-transport-protocols-pre19.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-pkix-cmp-transport-protocols-pre19.txt
Content-Disposition: attachment;
	filename="draft-ietf-pkix-cmp-transport-protocols-pre19.txt"

CgoKTmV0d29yayBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIFQuIEthdXNlCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIFRlY3RpYQpVcGRhdGVzOiA0MjEwIChpZiBhcHBy
b3ZlZCkgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgTS4gUGV5bG8KSW50ZW5k
ZWQgc3RhdHVzOiBTdGFuZGFyZHMgVHJhY2sgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgTlNOCkV4cGlyZXM6IE5vdmVtYmVyIDE2LCAyMDEyICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIE1heSAxNSwgMjAxMgoKCiAgIEludGVybmV0IFguNTA5IFB1YmxpYyBLZXkg
SW5mcmFzdHJ1Y3R1cmUgLS0gSFRUUCBUcmFuc3BvcnQgZm9yIENNUAogICAgICAgICAgICAgZHJh
ZnQtaWV0Zi1wa2l4LWNtcC10cmFuc3BvcnQtcHJvdG9jb2xzLTE5LnR4dAoKQWJzdHJhY3QKCiAg
IFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGhvdyB0byBsYXllciB0aGUgQ2VydGlmaWNhdGUgTWFu
YWdlbWVudAogICBQcm90b2NvbCBvdmVyIEhUVFAuICBJdCBpcyB0aGUgIkNNUHRyYW5zIiBkb2N1
bWVudCByZWZlcmVuY2VkIGluIFJGQwogICA0MjEwIGFuZCB0aGVyZWZvcmUgdXBkYXRlcyB0aGUg
cmVmZXJlbmNlIGdpdmVuIHRoZXJlaW4uCgpTdGF0dXMgb2YgdGhpcyBNZW1vCgogICBUaGlzIElu
dGVybmV0LURyYWZ0IGlzIHN1Ym1pdHRlZCBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGggdGhlCiAg
IHByb3Zpc2lvbnMgb2YgQkNQIDc4IGFuZCBCQ1AgNzkuCgogICBJbnRlcm5ldC1EcmFmdHMgYXJl
IHdvcmtpbmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZwogICBUYXNrIEZv
cmNlIChJRVRGKS4gIE5vdGUgdGhhdCBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZQog
ICB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuICBUaGUgbGlzdCBvZiBjdXJy
ZW50IEludGVybmV0LQogICBEcmFmdHMgaXMgYXQgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RyYWZ0cy9jdXJyZW50Ly4KCiAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRz
IHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRocwogICBhbmQgbWF5IGJlIHVwZGF0ZWQs
IHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueQogICB0aW1l
LiAgSXQgaXMgaW5hcHByb3ByaWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5j
ZQogICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9n
cmVzcy4iCgogICBUaGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIE5vdmVtYmVyIDE2
LCAyMDEyLgoKQ29weXJpZ2h0IE5vdGljZQoKICAgQ29weXJpZ2h0IChjKSAyMDEyIElFVEYgVHJ1
c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZpZWQgYXMgdGhlCiAgIGRvY3VtZW50IGF1dGhvcnMu
ICBBbGwgcmlnaHRzIHJlc2VydmVkLgoKICAgVGhpcyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIEJD
UCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdhbAogICBQcm92aXNpb25zIFJlbGF0aW5nIHRv
IElFVEYgRG9jdW1lbnRzCiAgIChodHRwOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNlbnNlLWluZm8p
IGluIGVmZmVjdCBvbiB0aGUgZGF0ZSBvZgogICBwdWJsaWNhdGlvbiBvZiB0aGlzIGRvY3VtZW50
LiAgUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHMKICAgY2FyZWZ1bGx5LCBhcyB0aGV5IGRl
c2NyaWJlIHlvdXIgcmlnaHRzIGFuZCByZXN0cmljdGlvbnMgd2l0aCByZXNwZWN0CiAgIHRvIHRo
aXMgZG9jdW1lbnQuICBDb2RlIENvbXBvbmVudHMgZXh0cmFjdGVkIGZyb20gdGhpcyBkb2N1bWVu
dCBtdXN0CiAgIGluY2x1ZGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZSB0ZXh0IGFzIGRlc2NyaWJl
ZCBpbiBTZWN0aW9uIDQuZSBvZgogICB0aGUgVHJ1c3QgTGVnYWwgUHJvdmlzaW9ucyBhbmQgYXJl
IHByb3ZpZGVkIHdpdGhvdXQgd2FycmFudHkgYXMKICAgZGVzY3JpYmVkIGluIHRoZSBTaW1wbGlm
aWVkIEJTRCBMaWNlbnNlLgoKCgoKS2F1c2UgJiBQZXlsbyAgICAgICAgICAgRXhwaXJlcyBOb3Zl
bWJlciAxNiwgMjAxMiAgICAgICAgICAgICAgIFtQYWdlIDFdCgwKSW50ZXJuZXQtRHJhZnQgICAg
ICAgICAgICAgICAgICBDTVB0cmFucyAgICAgICAgICAgICAgICAgICAgICAgIE1heSAyMDEyCgoK
ICAgVGhpcyBkb2N1bWVudCBtYXkgY29udGFpbiBtYXRlcmlhbCBmcm9tIElFVEYgRG9jdW1lbnRz
IG9yIElFVEYKICAgQ29udHJpYnV0aW9ucyBwdWJsaXNoZWQgb3IgbWFkZSBwdWJsaWNseSBhdmFp
bGFibGUgYmVmb3JlIE5vdmVtYmVyCiAgIDEwLCAyMDA4LiAgVGhlIHBlcnNvbihzKSBjb250cm9s
bGluZyB0aGUgY29weXJpZ2h0IGluIHNvbWUgb2YgdGhpcwogICBtYXRlcmlhbCBtYXkgbm90IGhh
dmUgZ3JhbnRlZCB0aGUgSUVURiBUcnVzdCB0aGUgcmlnaHQgdG8gYWxsb3cKICAgbW9kaWZpY2F0
aW9ucyBvZiBzdWNoIG1hdGVyaWFsIG91dHNpZGUgdGhlIElFVEYgU3RhbmRhcmRzIFByb2Nlc3Mu
CiAgIFdpdGhvdXQgb2J0YWluaW5nIGFuIGFkZXF1YXRlIGxpY2Vuc2UgZnJvbSB0aGUgcGVyc29u
KHMpIGNvbnRyb2xsaW5nCiAgIHRoZSBjb3B5cmlnaHQgaW4gc3VjaCBtYXRlcmlhbHMsIHRoaXMg
ZG9jdW1lbnQgbWF5IG5vdCBiZSBtb2RpZmllZAogICBvdXRzaWRlIHRoZSBJRVRGIFN0YW5kYXJk
cyBQcm9jZXNzLCBhbmQgZGVyaXZhdGl2ZSB3b3JrcyBvZiBpdCBtYXkKICAgbm90IGJlIGNyZWF0
ZWQgb3V0c2lkZSB0aGUgSUVURiBTdGFuZGFyZHMgUHJvY2VzcywgZXhjZXB0IHRvIGZvcm1hdAog
ICBpdCBmb3IgcHVibGljYXRpb24gYXMgYW4gUkZDIG9yIHRvIHRyYW5zbGF0ZSBpdCBpbnRvIGxh
bmd1YWdlcyBvdGhlcgogICB0aGFuIEVuZ2xpc2guCgoKVGFibGUgb2YgQ29udGVudHMKCiAgIDEu
ICBJbnRyb2R1Y3Rpb24gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgMwogICAyLiAgQ29udmVudGlvbnMgVXNlZCBpbiBUaGlzIERvY3VtZW50ICAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDQKICAgMy4gIEhUVFAtQmFzZWQgUHJvdG9jb2wgIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA1CiAgICAgMy4xLiAgSFRU
UCBWZXJzaW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
NQogICAgIDMuMi4gIFBlcnNpc3RlbnQgQ29ubmVjdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gIDUKICAgICAzLjMuICBHZW5lcmFsIEZvcm0gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA1CiAgICAgMy40LiAgTWVkaWEgVHlwZSAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNgogICAgIDMu
NS4gIENvbW11bmljYXRpb24gV29ya2Zsb3cgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gIDYKICAgICAzLjYuICBIVFRQIFJlcXVlc3QtVVJJIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICA2CiAgICAgMy43LiAgUHVzaGluZyBvZiBBbm5vdW5jZW1l
bnRzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNgogICAgIDMuOC4gIEhUVFAg
Q29uc2lkZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDcK
ICAgNC4gIEltcGxlbWVudGF0aW9uIENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICA5CiAgIDUuICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMAogICA2LiAgSUFOQSBDb25zaWRlcmF0aW9u
cyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTEKICAgNy4gIEFj
a25vd2xlZGdtZW50cyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIDEyCiAgIDguICBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAxMwogICAgIDguMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTMKICAgICA4LjIuICBJbmZvcm1h
dGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEzCiAg
IEF1dGhvcnMnIEFkZHJlc3NlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAxNAoKCgoKCgoKCgoKCgoKCgoKCkthdXNlICYgUGV5bG8gICAgICAgICAgIEV4
cGlyZXMgTm92ZW1iZXIgMTYsIDIwMTIgICAgICAgICAgICAgICBbUGFnZSAyXQoMCkludGVybmV0
LURyYWZ0ICAgICAgICAgICAgICAgICAgQ01QdHJhbnMgICAgICAgICAgICAgICAgICAgICAgICBN
YXkgMjAxMgoKCjEuICBJbnRyb2R1Y3Rpb24KCiAgIFRoZSBDZXJ0aWZpY2F0ZSBNYW5hZ2VtZW50
IFByb3RvY29sIChDTVApIFtSRkM0MjEwXSByZXF1aXJlcyBhIHdlbGwKICAgZGVmaW5lZCB0cmFu
c3BvcnQgbWVjaGFuaXNtIHRvIGVuYWJsZSBFbmQgRW50aXRpZXMgKEVFcyksCiAgIFJlZ2lzdHJh
dGlvbiBBdXRob3JpdGllcyAoUkFzKSBhbmQgQ2VydGlmaWNhdGlvbiBBdXRob3JpdGllcyAoQ0Fz
KSB0bwogICBwYXNzIFBLSU1lc3NhZ2Ugc2VxdWVuY2VzIGJldHdlZW4gdGhlbS4KCiAgIFRoZSBm
aXJzdCB2ZXJzaW9uIG9mIHRoZSBDTVAgc3BlY2lmaWNhdGlvbiBbUkZDMjUxMF0gaW5jbHVkZWQg
YSBicmllZgogICBkZXNjcmlwdGlvbiBvZiBhIHNpbXBsZSB0cmFuc3BvcnQgcHJvdG9jb2wgbGF5
ZXIgb24gdG9wIG9mIFRDUC4gIEl0cwogICBmZWF0dXJlcyB3YXMgc2ltcGxlIHRyYW5zcG9ydCBs
ZXZlbCBlcnJvci1oYW5kbGluZyBhbmQgYSBtZWNoYW5pc20gdG8KICAgcG9sbCBmb3Igb3V0c3Rh
bmRpbmcgUEtJIG1lc3NhZ2VzLiAgQWRkaXRpb25hbGx5IGl0IHdhcyBtZW50aW9uZWQKICAgdGhh
dCBQS0kgbWVzc2FnZXMgY291bGQgYWxzbyBiZSBjb252ZXllZCB1c2luZyBmaWxlLSwgRS1tYWls
LSBhbmQKICAgSFRUUC1iYXNlZCB0cmFuc3BvcnQsIGJ1dCB0aG9zZSB3ZXJlIG5vdCBzcGVjaWZp
ZWQgaW4gZGV0YWlsLgoKICAgVGhlIGN1cnJlbnQgdmVyc2lvbiBvZiB0aGUgQ01QIHNwZWNpZmlj
YXRpb24gW1JGQzQyMTBdIGluY29ycG9yYXRlZAogICBpdHMgb3duIHBvbGxpbmcgbWVjaGFuaXNt
IGFuZCB0aHVzIHRoZSBuZWVkIGZvciBhIHRyYW5zcG9ydCBwcm90b2NvbAogICBwcm92aWRpbmcg
dGhpcyBmdW5jdGlvbmFsaXR5IHZhbmlzaGVkLiAgVGhlIHJlbWFpbmluZyBmZWF0dXJlcyBDTVAK
ICAgcmVxdWlyZXMgZnJvbSBpdHMgdHJhbnNwb3J0IHByb3RvY29scyBhcmUgY29ubmVjdGlvbiBh
bmQgZXJyb3IKICAgaGFuZGxpbmcuCgogICBCZWZvcmUgdGhpcyBkb2N1bWVudCB3YXMgcHVibGlz
aGVkIGFzIGFuIFJGQywgdGhlIGRyYWZ0IHZlcnNpb24KICAgdW5kZXJ3ZW50IGRyYXN0aWMgY2hh
bmdlcyBkdXJpbmcgdGhlIGxvbmctbGFzdGluZyB3b3JrIHByb2Nlc3MuICBUaGUKICAgIlRDUC1C
YXNlZCBNYW5hZ2VtZW50IFByb3RvY29sIiB3YXMgZW5oYW5jZWQgYW5kIGEgVENQLU1lc3NhZ2Vz
LW92ZXItCiAgIEhUVFAgdHJhbnNwb3J0IHNwZWNpZmljYXRpb24gYXBwZWFyZWQuICBBcyBib3Ro
IHByb3ZlZCB0byBiZSBuZWVkbGVzcwogICBhbmQgY3VtYmVyc29tZSwgaW1wbGVtZW50ZXJzIHBy
ZWZlcnJlZCB0byB1c2UgcGxhaW4gSFRUUCB0cmFuc3BvcnQKICAgZm9sbG93aW5nIFtSRkMxOTQ1
XSBvciBbUkZDMjYxNl0uICBUaGlzIGRvY3VtZW50IG5vdyByZWZsZWN0cyB0aGF0IGJ5CiAgIGV4
Y2x1c2l2ZWx5IGRlc2NyaWJpbmcgSFRUUCBhcyB0cmFuc3BvcnQgcHJvdG9jb2wgZm9yIENNUC4K
CiAgIFRoZSB1c2FnZSBvZiBIVFRQIGZvciB0cmFuc3BvcnRpbmcgQ01QIG1lc3NhZ2VzIGV4Y2x1
c2l2ZWx5IHVzZXMgUE9TVAogICBtZXRob2QgZm9yIHJlcXVlc3RzLCBlZmZlY3RpdmVseSB0dW5u
ZWxpbmcgQ01QIG92ZXIgSFRUUC4gIFdoaWxlIHRoaXMKICAgaXMgZ2VuZXJhbGx5IGNvbnNpZGVy
ZWQgYXMgYmFkIHByYWN0aWNlIGFuZCBzaG91bGQgbm90IGJlIGVtdWxhdGVkLAogICB0aGVyZSBh
cmUgZ29vZCByZWFzb25zIHRvIGRvIHNvIGZvciB0cmFuc3BvcnRpbmcgQ01QLiAgSFRUUCBpcyB1
c2VkCiAgIGFzIGl0IGlzIGdlbmVyYWxseSBlYXN5IHRvIGltcGxlbWVudCBhbmQgYWJsZSB0byB0
cmF2ZXJzZSBuZXR3b3JrCiAgIGJvcmRlcnMgdXRpbGl6aW5nIHViaXF1aXRvdXMgcHJveGllcy4g
IE1vc3QgaW1wb3J0YW50bHksIEhUVFAgaXMKICAgYWxyZWFkeSBjb21tb25seSB1c2VkIGluIGV4
aXN0aW5nIENNUCBpbXBsZW1lbnRhdGlvbnMuICBPdGhlciBIVFRQCiAgIHJlcXVlc3QgbWV0aG9k
cyBzdWNoIGFzIEdFVCBhcmUgbm90IHVzZWQgYXMgUEtJIG1hbmFnZW1lbnQgb3BlcmF0aW9ucwog
ICBjYW4gb25seSBiZSB0cmlnZ2VyZWQgdXNpbmcgQ01QJ3MgUEtJIG1lc3NhZ2VzIHdoaWNoIG5l
ZWQgdG8gYmUKICAgdHJhbnNwb3J0ZWQgd2l0aGluIGEgUE9TVCByZXF1ZXN0LgoKICAgV2l0aCBp
dHMgc3RhdHVzIGNvZGVzIEhUVFAgcHJvdmlkZXMgbmVlZGVkIGVycm9yIHJlcG9ydGluZwogICBj
YXBhYmlsaXRpZXMuICBHZW5lcmFsIHByb2JsZW1zIG9uIHRoZSBzZXJ2ZXIgc2lkZSBhcyB3ZWxs
IGFzIHRob3NlCiAgIGRpcmVjdGx5IGNhdXNlZCBieSB0aGUgcmVzcGVjdGl2ZSByZXF1ZXN0IGNh
biBiZSByZXBvcnRlZCB0byB0aGUKICAgY2xpZW50LgoKICAgQXMgQ01QIGltcGxlbWVudHMgYSB0
cmFuc2FjdGlvbiBJRCwgaWRlbnRpZnlpbmcgdHJhbnNhY3Rpb25zIHNwYW5uaW5nCiAgIG92ZXIg
bW9yZSB0aGFuIGp1c3QgYSBzaW5nbGUgcmVxdWVzdC9yZXNwb25zZSBwYWlyLCB0aGUgc3RhdGVs
ZXNzbmVzcwogICBvZiBIVFRQIGlzIG5vdCBibG9ja2luZyBpdHMgdXNhZ2UgYXMgdHJhbnNwb3J0
IHByb3RvY29sIGZvciBDTVAKICAgbWVzc2FnZXMuCgoKCkthdXNlICYgUGV5bG8gICAgICAgICAg
IEV4cGlyZXMgTm92ZW1iZXIgMTYsIDIwMTIgICAgICAgICAgICAgICBbUGFnZSAzXQoMCkludGVy
bmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgQ01QdHJhbnMgICAgICAgICAgICAgICAgICAgICAg
ICBNYXkgMjAxMgoKCjIuICBDb252ZW50aW9ucyBVc2VkIGluIFRoaXMgRG9jdW1lbnQKCiAgIFRo
ZSBrZXkgd29yZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hB
TEwgTk9UIiwKICAgIlNIT1VMRCIsICJTSE9VTEQgTk9UIiwgIlJFQ09NTUVOREVEIiwgIk1BWSIs
IGFuZCAiT1BUSU9OQUwiIGluIHRoaXMKICAgZG9jdW1lbnQgYXJlIHRvIGJlIGludGVycHJldGVk
IGFzIGRlc2NyaWJlZCBpbiBbUkZDMjExOV0uCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoK
CgoKCgoKCgoKCgoKCgoKCgpLYXVzZSAmIFBleWxvICAgICAgICAgICBFeHBpcmVzIE5vdmVtYmVy
IDE2LCAyMDEyICAgICAgICAgICAgICAgW1BhZ2UgNF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAg
ICAgICAgICAgIENNUHRyYW5zICAgICAgICAgICAgICAgICAgICAgICAgTWF5IDIwMTIKCgozLiAg
SFRUUC1CYXNlZCBQcm90b2NvbAoKICAgRm9yIGRpcmVjdCBpbnRlcmFjdGlvbiBiZXR3ZWVuIHR3
byBlbnRpdGllcywgd2hlcmUgYSByZWxpYWJsZQogICB0cmFuc3BvcnQgcHJvdG9jb2wgbGlrZSBU
Q1AgaXMgYXZhaWxhYmxlLCBIVFRQIFNIT1VMRCBiZSB1dGlsaXplZCBmb3IKICAgY29udmV5aW5n
IENNUCBtZXNzYWdlcy4KCjMuMS4gIEhUVFAgVmVyc2lvbnMKCiAgIEltcGxlbWVudGF0aW9ucyBN
VVNUIHN1cHBvcnQgSFRUUC8xLjAgW1JGQzE5NDVdLCBhbmQgU0hPVUxEIHN1cHBvcnQKICAgSFRU
UC8xLjEgW1JGQzI2MTZdLgoKMy4yLiAgUGVyc2lzdGVudCBDb25uZWN0aW9ucwoKICAgSFRUUCBw
ZXJzaXN0ZW50IGNvbm5lY3Rpb25zIFtSRkMyNjE2XSBhbGxvdyBtdWx0aXBsZSBpbnRlcmFjdGlv
bnMgdG8KICAgdGFrZSBwbGFjZSBvbiB0aGUgc2FtZSBIVFRQIGNvbm5lY3Rpb24uICBIb3dldmVy
LCBuZWl0aGVyIEhUVFAgbm9yCiAgIHRoZSBwcm90b2NvbCBzcGVjaWZpZWQgaW4gdGhpcyBkb2N1
bWVudCBhcmUgZGVzaWduZWQgdG8gY29ycmVsYXRlCiAgIG1lc3NhZ2VzIG9uIHRoZSBzYW1lIGNv
bm5lY3Rpb24gaW4gYW55IG1lYW5pbmdmdWwgd2F5OyBwZXJzaXN0ZW50CiAgIGNvbm5lY3Rpb25z
IGFyZSBvbmx5IGEgcGVyZm9ybWFuY2Ugb3B0aW1pemF0aW9uLiAgSW4gcGFydGljdWxhciwKICAg
aW50ZXJtZWRpYXJpZXMgY2FuIGRvIHRoaW5ncyBsaWtlIG1peCBjb25uZWN0aW9ucyBmcm9tIGRp
ZmZlcmVudAogICBjbGllbnRzIGludG8gb25lICJ1cHN0cmVhbSIgY29ubmVjdGlvbnMsIHRlcm1p
bmF0ZSBwZXJzaXN0ZW50CiAgIGNvbm5lY3Rpb25zIGFuZCBmb3J3YXJkIHJlcXVlc3RzIGFzIG5v
bi1wZXJzaXN0ZW50IHJlcXVlc3RzLCBldGMuICBBcwogICBzdWNoLCBpbXBsZW1lbnRhdGlvbnMg
TVVTVCBOT1QgaW5mZXIgdGhhdCByZXF1ZXN0cyBvbiB0aGUgc2FtZQogICBjb25uZWN0aW9uIGNv
bWUgZnJvbSB0aGUgc2FtZSBjbGllbnQgKGUuZy4sIGZvciBjb3JyZWxhdGluZyBQS0kKICAgbWVz
c2FnZXMgd2l0aCBvbmdvaW5nIHRyYW5zYWN0aW9ucyk7IGV2ZXJ5IG1lc3NhZ2UgaXMgdG8gYmUg
ZXZhbHVhdGVkCiAgIGluIGlzb2xhdGlvbi4KCjMuMy4gIEdlbmVyYWwgRm9ybQoKICAgQSBERVIt
ZW5jb2RlZCBQS0lNZXNzYWdlIGlzIHNlbnQgYXMgdGhlIGVudGl0eS1ib2R5IG9mIGFuIEhUVFAg
UE9TVAogICByZXF1ZXN0LiAgSWYgdGhpcyBIVFRQIHJlcXVlc3QgaXMgc3VjY2Vzc2Z1bCwgdGhl
IHNlcnZlciByZXR1cm5zIHRoZQogICBDTVAgcmVzcG9uc2UgaW4gdGhlIGJvZHkgb2YgdGhlIEhU
VFAgcmVzcG9uc2UuICBUaGUgSFRUUCByZXNwb25zZQogICBzdGF0dXMgY29kZSBpbiB0aGlzIGNh
c2UgTVVTVCBiZSAyMDA7IG90aGVyICJTdWNjZXNzZnVsIDJ4eCIgY29kZXMKICAgTVVTVCBOT1Qg
YmUgdXNlZCBmb3IgdGhpcyBwdXJwb3NlLiAgSFRUUCByZXNwb25zZXMgdG8gcHVzaGVkIENNUAog
ICBBbm5vdW5jZW1lbnQgbWVzc2FnZXMgKGkuZS4sIENBIENlcnRpZmljYXRlIEFubm91bmNlbWVu
dCwgQ2VydGlmaWNhdGUKICAgQW5ub3VuY2VtZW50LCBSZXZvY2F0aW9uIEFubm91bmNlbWVudCwg
YW5kIENSTCBBbm5vdW5jZW1lbnQpIHV0aWxpemUKICAgdGhlIHN0YXR1cyBjb2RlcyAyMDEgYW5k
IDIwMiB0byBpZGVudGlmeSB3aGV0aGVyIHRoZSByZWNlaXZlZAogICBpbmZvcm1hdGlvbiB3YXMg
cHJvY2Vzc2VkLgoKICAgV2hpbGUgIlJlZGlyZWN0aW9uIDN4eCIgc3RhdHVzIGNvZGVzIE1BWSBi
ZSBzdXBwb3J0ZWQgYnkKICAgaW1wbGVtZW50YXRpb25zLCBjbGllbnRzIHNob3VsZCBvbmx5IGJl
IGVuYWJsZWQgdG8gYXV0b21hdGljYWxseQogICBmb2xsb3cgdGhlbSBhZnRlciBjYXJlZnVsIGNv
bnNpZGVyYXRpb24gb2YgcG9zc2libGUgc2VjdXJpdHkKICAgaW1wbGljYXRpb25zLgoKICAgQWxs
IGFwcGxpY2FibGUgIkNsaWVudCBFcnJvciA0eHgiIG9yICJTZXJ2ZXIgRXJyb3IgNXh4IiBzdGF0
dXMgY29kZXMKICAgbWF5IGJlIHVzZWQgdG8gaW5mb3JtIHRoZSBjbGllbnQgYWJvdXQgZXJyb3Jz
LgoKCgoKCgpLYXVzZSAmIFBleWxvICAgICAgICAgICBFeHBpcmVzIE5vdmVtYmVyIDE2LCAyMDEy
ICAgICAgICAgICAgICAgW1BhZ2UgNV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAg
IENNUHRyYW5zICAgICAgICAgICAgICAgICAgICAgICAgTWF5IDIwMTIKCgozLjQuICBNZWRpYSBU
eXBlCgogICBUaGUgSW50ZXJuZXQgTWVkaWEgVHlwZSAiYXBwbGljYXRpb24vcGtpeGNtcCIgTVVT
VCBiZSBzZXQgaW4gdGhlIEhUVFAKICAgaGVhZGVyIHdoZW4gY29udmV5aW5nIGEgUEtJTWVzc2Fn
ZS4KCjMuNS4gIENvbW11bmljYXRpb24gV29ya2Zsb3cKCiAgIEluIENNUCBtb3N0IGNvbW11bmlj
YXRpb24gaXMgaW5pdGlhdGVkIGJ5IHRoZSBlbmQgZW50aXRpZXMgd2hlcmUKICAgZXZlcnkgQ01Q
IHJlcXVlc3QgdHJpZ2dlcnMgYSBDTVAgcmVzcG9uc2UgbWVzc2FnZSBmcm9tIHRoZSBDQSBvciBS
QS4KCiAgIFRoZSBDTVAgQW5ub3VuY2VtZW50IG1lc3NhZ2VzIGRlc2NyaWJlZCBpbiBTZWN0aW9u
IDMuNyBhcmUgYW4KICAgZXhjZXB0aW9uLiAgVGhlaXIgY3JlYXRpb24gbWF5IGJlIHRyaWdnZXJl
ZCBieSBjZXJ0YWluIGV2ZW50cyBvciBkb25lCiAgIG9uIGEgcmVndWxhciBiYXNpcyBieSBhIENB
LiAgVGhlIHJlY2lwaWVudCBvZiB0aGUgQW5ub3VuY2VtZW50IG9ubHkKICAgcmVwbGllcyB3aXRo
IGFuIEhUVFAgc3RhdHVzIGNvZGUgYWNrbm93bGVkZ2luZyB0aGUgcmVjZWlwdCBvcgogICBpbmRp
Y2F0aW5nIGFuIGVycm9yIGJ1dCBub3Qgd2l0aCBhIENNUCByZXNwb25zZS4KCiAgIElmIHRoZSBy
ZWNlaXB0IG9mIGFuIEhUVFAgcmVxdWVzdCBpcyBub3QgY29uZmlybWVkIGJ5IHJlY2VpdmluZyBh
bgogICBIVFRQIHJlc3BvbnNlLCBpdCBNVVNUIGJlIGFzc3VtZWQgdGhhdCB0aGUgdHJhbnNwb3J0
ZWQgQ01QIG1lc3NhZ2UKICAgd2FzIG5vdCBzdWNjZXNzZnVsbHkgZGVsaXZlcmVkIHRvIGl0cyBk
ZXN0aW5hdGlvbi4KCjMuNi4gIEhUVFAgUmVxdWVzdC1VUkkKCiAgIFRoZSBSZXF1ZXN0LVVSSSBp
cyBmb3JtZWQgYXMgc3BlY2lmaWVkIGluIFtSRkMzOTg2XS4KCiAgIEEgc2VydmVyIGltcGxlbWVu
dGF0aW9uIE1VU1QgaGFuZGxlIFJlcXVlc3QtVVJJIHBhdGhzIHdpdGggb3Igd2l0aG91dAogICBh
IHRyYWlsaW5nIHNsYXNoIGFzIGlkZW50aWNhbC4KCiAgIEFuIGV4YW1wbGUgb2YgYSBSZXF1ZXN0
LUxpbmUgYW5kIGEgSG9zdCBoZWFkZXIgZmllbGQgaW4gYW4gSFRUUC8xLjEKICAgaGVhZGVyLCBz
ZW5kaW5nIGEgQ01QIHJlcXVlc3QgdG8gYSBzZXJ2ZXIsIGxvY2F0ZWQgaW4gdGhlICIvY21wIiBw
YXRoCiAgIG9mIHRoZSBob3N0ICJleGFtcGxlLmNvbSIsIHdvdWxkIGJlCgogICAgICBQT1NUIC9j
bXAgSFRUUC8xLjEKICAgICAgSG9zdDogZXhhbXBsZS5jb20KCiAgIG9yIGluIHRoZSBhYnNvbHV0
ZVVSSSBmb3JtCgogICAgICBQT1NUIGh0dHA6Ly9leGFtcGxlLmNvbS9jbXAvIEhUVFAvMS4xCiAg
ICAgIEhvc3Q6IGV4YW1wbGUuY29tCgozLjcuICBQdXNoaW5nIG9mIEFubm91bmNlbWVudHMKCiAg
IEEgQ01QIHNlcnZlciBtYXkgY3JlYXRlIGV2ZW50LXRyaWdnZXJlZCBhbm5vdW5jZW1lbnRzIG9y
IGdlbmVyYXRlCiAgIHRoZW0gb24gYSByZWd1bGFyIGJhc2lzLiAgSXQgTUFZIHV0aWxpemUgSFRU
UCB0cmFuc3BvcnQgdG8gY29udmV5CiAgIHRoZW0gdG8gYSBzdWl0YWJsZSByZWNpcGllbnQuICBB
cyBubyByZXF1ZXN0IG1lc3NhZ2VzIGFyZSBzcGVjaWZpZWQKICAgZm9yIHRob3NlIGFubm91bmNl
bWVudHMgdGhleSBjYW4gb25seSBiZSBwdXNoZWQgdG8gdGhlIHJlY2lwaWVudC4KCiAgIElmIGFu
IEVFIHdhbnRzIHRvIHBvbGwgZm9yIGEgcG90ZW50aWFsIENBIEtleSBVcGRhdGUgQW5ub3VuY2Vt
ZW50IG9yCiAgIHRoZSBjdXJyZW50IENSTCwgYSBQS0kgSW5mb3JtYXRpb24gUmVxdWVzdCB1c2lu
ZyBhIEdlbmVyYWwgTWVzc2FnZSBhcwoKCgpLYXVzZSAmIFBleWxvICAgICAgICAgICBFeHBpcmVz
IE5vdmVtYmVyIDE2LCAyMDEyICAgICAgICAgICAgICAgW1BhZ2UgNl0KDApJbnRlcm5ldC1EcmFm
dCAgICAgICAgICAgICAgICAgIENNUHRyYW5zICAgICAgICAgICAgICAgICAgICAgICAgTWF5IDIw
MTIKCgogICBkZXNjcmliZWQgaW4gRS41IG9mIFtSRkM0MjEwXSBjYW4gYmUgdXNlZC4KCiAgIFdo
ZW4gcHVzaGluZyBBbm5vdW5jZW1lbnQgbWVzc2FnZXMsIFBLSU1lc3NhZ2Ugc3RydWN0dXJlcyBh
cmUgc2VudCBhcwogICB0aGUgZW50aXR5LWJvZHkgb2YgYW4gSFRUUCBQT1NUIHJlcXVlc3QuCgog
ICBTdWl0YWJsZSByZWNpcGllbnRzIGZvciBDTVAgYW5ub3VuY2VtZW50cyBtaWdodCBlLmcuIGJl
IHJlcG9zaXRvcmllcwogICBzdG9yaW5nIHRoZSBhbm5vdW5jZWQgaW5mb3JtYXRpb24gc3VjaCBh
cyBkaXJlY3Rvcnkgc2VydmljZXMuICBUaG9zZQogICBsaXN0ZW4gZm9yIGluY29taW5nIG1lc3Nh
Z2VzLCB1dGlsaXppbmcgdGhlIHNhbWUgSFRUUCBSZXF1ZXN0LVVSSQogICBzY2hlbWUgYXMgZGVm
aW5lZCBpbiBTZWN0aW9uIDMuNi4KCiAgIFRoZSBmb2xsb3dpbmcgUEtJTWVzc2FnZXMgYXJlIGFu
bm91bmNlbWVudHMgdGhhdCBtYXkgYmUgcHVzaGVkIGJ5IGEKICAgQ0EuICBUaGUgcHJlZml4ZWQg
bnVtYmVycyByZWZsZWN0IEFTTi4xIG51bWJlcmluZyBvZiB0aGUgcmVzcGVjdGl2ZQogICBlbGVt
ZW50LgoKICAgICAgWzE1XSBDQSBLZXkgVXBkYXRlIEFubm91bmNlbWVudAogICAgICBbMTZdIENl
cnRpZmljYXRlIEFubm91bmNlbWVudAogICAgICBbMTddIFJldm9jYXRpb24gQW5ub3VuY2VtZW50
CiAgICAgIFsxOF0gQ1JMIEFubm91bmNlbWVudAoKICAgQ01QIEFubm91bmNlbWVudCBtZXNzYWdl
cyBkbyBub3QgcmVxdWlyZSBhbnkgQ01QIHJlc3BvbnNlLiAgSG93ZXZlciwKICAgdGhlIHJlY2lw
aWVudCBNVVNUIGFja25vd2xlZGdlIHJlY2VpcHQgd2l0aCBhIEhUVFAgcmVzcG9uc2UgaGF2aW5n
IGFuCiAgIGFwcHJvcHJpYXRlIHN0YXR1cyBjb2RlIGFuZCBhbiBlbXB0eSBib2R5LiAgV2hlbiBu
b3QgcmVjZWl2aW5nIHN1Y2gKICAgcmVzcG9uc2UgaXQgTVVTVCBiZSBhc3N1bWVkIHRoYXQgdGhl
IGRlbGl2ZXJ5IHdhcyBub3Qgc3VjY2Vzc2Z1bCBhbmQKICAgaWYgYXBwbGljYWJsZSB0aGUgc2Vu
ZGluZyBzaWRlIG1heSByZXRyeSBzZW5kaW5nIHRoZSBBbm5vdW5jZW1lbnQKICAgYWZ0ZXIgd2Fp
dGluZyBmb3IgYW4gYXBwcm9wcmlhdGUgdGltZSBzcGFuLgoKICAgSWYgdGhlIGFubm91bmNlZCBp
c3N1ZSB3YXMgc3VjY2Vzc2Z1bGx5IHN0b3JlZCBpbiBhIGRhdGFiYXNlIG9yIHdhcwogICBhbHJl
YWR5IHByZXNlbnQsIHRoZSBhbnN3ZXIgTVVTVCBiZSBhbiBIVFRQIHJlc3BvbnNlIHdpdGggYSAi
MjAxCiAgIENyZWF0ZWQiIHN0YXR1cyBjb2RlIGFuZCBlbXB0eSBtZXNzYWdlIGJvZHkuCgogICBJ
biBjYXNlIHRoZSBhbm5vdW5jZWQgaW5mb3JtYXRpb24gd2FzIG9ubHkgYWNjZXB0ZWQgZm9yIGZ1
cnRoZXIKICAgcHJvY2Vzc2luZywgdGhlIHN0YXR1cyBjb2RlIG9mIHRoZSByZXR1cm5lZCBIVFRQ
IHJlc3BvbnNlIE1BWSBhbHNvIGJlCiAgICIyMDIgQWNjZXB0ZWQiLiAgQWZ0ZXIgYW4gYXBwcm9w
cmlhdGUgZGVsYXksIHRoZSBzZW5kZXIgbWF5IHRoZW4gdHJ5CiAgIHRvIHNlbmQgdGhlIEFubm91
bmNlbWVudCBhZ2FpbiBhbmQgbWF5IHJlcGVhdCB0aGlzIHVudGlsIGl0IHJlY2VpdmVzCiAgIGEg
Y29uZmlybWF0aW9uIHRoYXQgaXQgaGFkIGJlZW4gc3VjY2Vzc2Z1bGx5IHByb2Nlc3NlZC4gIFRo
ZQogICBhcHByb3ByaWF0ZSBkdXJhdGlvbiBvZiB0aGUgZGVsYXkgYW5kIHRoZSBvcHRpb24gdG8g
aW5jcmVhc2UgaXQKICAgYmV0d2VlbiBjb25zZWN1dGl2ZSBhdHRlbXB0cyBzaG91bGQgYmUgY2Fy
ZWZ1bGx5IGNvbnNpZGVyZWQuCgogICBBIHJlY2VpdmVyIE1VU1QgYW5zd2VyIHdpdGggYSBzdWl0
YWJsZSA0eHggb3IgNXh4IEhUVFAgZXJyb3IgY29kZQogICB3aGVuIGEgcHJvYmxlbSBvY2N1cnMu
CgozLjguICBIVFRQIENvbnNpZGVyYXRpb25zCgogICBXaGlsZSBpbXBsZW1lbnRhdGlvbnMgTUFZ
IG1ha2UgdXNlIG9mIGFsbCBkZWZpbmVkIGZlYXR1cmVzIG9mIHRoZQogICBIVFRQIHByb3RvY29s
LCB0aGV5IFNIT1VMRCBrZWVwIHRoZSBwcm90b2NvbCB1dGlsaXphdGlvbiBhcyBzaW1wbGUgYXMK
ICAgcG9zc2libGUuICBFLmcuIHRoZXJlIGlzIG5vIGJlbmVmaXQgaW4gdXNpbmcgY2h1bmtlZCBU
cmFuc2Zlci0KICAgRW5jb2RpbmcgYXMgdGhlIGxlbmd0aCBvZiBhbiBBU04uMSBzZXF1ZW5jZSBp
cyBrbm93IHdoZW4gc3RhcnRpbmcgdG8KICAgc2VuZCBpdC4KCgoKS2F1c2UgJiBQZXlsbyAgICAg
ICAgICAgRXhwaXJlcyBOb3ZlbWJlciAxNiwgMjAxMiAgICAgICAgICAgICAgIFtQYWdlIDddCgwK
SW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICBDTVB0cmFucyAgICAgICAgICAgICAgICAg
ICAgICAgIE1heSAyMDEyCgoKICAgVGhlcmUgaXMgbm8gbmVlZCBmb3IgdGhlIGNsaWVudHMgdG8g
c2VuZCBhbiAiRXhwZWN0IiByZXF1ZXN0LWhlYWRlcgogICBmaWVsZCB3aXRoIHRoZSAiMTAwLWNv
bnRpbnVlIiBleHBlY3RhdGlvbiBhbmQgd2FpdCBmb3IgYSAiMTAwCiAgIENvbnRpbnVlIiBzdGF0
dXMgYXMgZGVzY3JpYmVkIGluIGNoYXB0ZXIgOC4yLjMgb2YgW1JGQzI2MTZdLiAgVGhlIENNUAog
ICBwYXlsb2FkIHNlbnQgYnkgYSBjbGllbnQgaXMgcmVsYXRpdmVseSBzbWFsbCwgc28gaGF2aW5n
IGV4dHJhCiAgIG1lc3NhZ2VzIGV4Y2hhbmdlZCBpcyBtb3JlIGluZWZmaWNpZW50IGFzIHRoZSBz
ZXJ2ZXIgd2lsbCBhbnl3YXkgb25seQogICBzZWxkb20gcmVqZWN0IGEgbWVzc2FnZSB3aXRob3V0
IGV2YWx1YXRpbmcgdGhlIGJvZHkuCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoK
CgoKCgoKCgoKCkthdXNlICYgUGV5bG8gICAgICAgICAgIEV4cGlyZXMgTm92ZW1iZXIgMTYsIDIw
MTIgICAgICAgICAgICAgICBbUGFnZSA4XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAg
ICAgQ01QdHJhbnMgICAgICAgICAgICAgICAgICAgICAgICBNYXkgMjAxMgoKCjQuICBJbXBsZW1l
bnRhdGlvbiBDb25zaWRlcmF0aW9ucwoKICAgSW1wbGVtZW50b3JzIHNob3VsZCBiZSBhd2FyZSB0
aGF0IGltcGxlbWVudGF0aW9ucyBtaWdodCBleGlzdCB0aGF0CiAgIHVzZSBhIGRpZmZlcmVudCBh
cHByb2FjaCBmb3IgSFRUUCB0cmFuc3BvcnQgYmVjYXVzZSB0aGlzIGRvY3VtZW50IGhhcwogICBi
ZWVuIHVuZGVyIGRldmVsb3BtZW50IGZvciBtb3JlIHRoYW4gYSBkZWNhZGUuICBGdXJ0aGVyLAog
ICBpbXBsZW1lbnRhdGlvbnMgYmFzZWQgb24gZWFybGllciBkcmFmdHMgb2YgdGhpcyBkb2N1bWVu
dCBtaWdodCB1c2UgYW4KICAgdW5yZWdpc3RlcmVkICJhcHBsaWNhdGlvbi9wa2l4Y21wLXBvbGwi
IE1JTUUgdHlwZS4KCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgpL
YXVzZSAmIFBleWxvICAgICAgICAgICBFeHBpcmVzIE5vdmVtYmVyIDE2LCAyMDEyICAgICAgICAg
ICAgICAgW1BhZ2UgOV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgIENNUHRyYW5z
ICAgICAgICAgICAgICAgICAgICAgICAgTWF5IDIwMTIKCgo1LiAgU2VjdXJpdHkgQ29uc2lkZXJh
dGlvbnMKCiAgIFRoZSBmb2xsb3dpbmcgYXNwZWN0cyBuZWVkIHRvIGJlIGNvbnNpZGVyZWQgYnkg
aW1wbGVtZW50ZXJzIGFuZAogICB1c2VyczoKCiAgIDEuICBUaGVyZSBpcyB0aGUgcmlzayBmb3Ig
ZGVuaWFsIG9mIHNlcnZpY2UgYXR0YWNrcyB0aHJvdWdoIHJlc291cmNlCiAgICAgICBjb25zdW1w
dGlvbiBieSBvcGVuaW5nIG1hbnkgY29ubmVjdGlvbnMgdG8gYW4gSFRUUCBzZXJ2ZXIuCiAgICAg
ICBUaGVyZWZvcmUgaWRsZSBjb25uZWN0aW9ucyBzaG91bGQgYmUgdGVybWluYXRlZCBhZnRlciBh
bgogICAgICAgYXBwcm9wcmlhdGUgdGltZW91dCwgbWF5YmUgYWxzbyBkZXBlbmRpbmcgb24gdGhl
IGF2YWlsYWJsZSBmcmVlCiAgICAgICByZXNvdXJjZXMuICBBZnRlciBzZW5kaW5nIGEgQ01QIEVy
cm9yIE1lc3NhZ2UsIHRoZSBzZXJ2ZXIgc2hvdWxkCiAgICAgICBjbG9zZSB0aGUgY29ubmVjdGlv
biBldmVuIGlmIHRoZSBDTVAgdHJhbnNhY3Rpb24gaXMgbm90IHlldCBmdWxseQogICAgICAgY29t
cGxldGVkLgoKICAgMi4gIFdpdGhvdXQgYmVpbmcgZW5jYXBzdWxhdGVkIGluIGVmZmVjdGl2ZSBz
ZWN1cml0eSBwcm90b2NvbHMgc3VjaAogICAgICAgYXMgVExTIFtSRkM1MjQ2XSB0aGVyZSBpcyBu
byBpbnRlZ3JpdHkgcHJvdGVjdGlvbiBhdCB0aGUgSFRUUAogICAgICAgcHJvdG9jb2wgbGV2ZWwu
ICBUaGVyZWZvcmUgaW5mb3JtYXRpb24gZnJvbSB0aGUgSFRUUCBwcm90b2NvbAogICAgICAgc2hv
dWxkIG5vdCBiZSB1c2VkIHRvIGNoYW5nZSBzdGF0ZSBvZiB0aGUgdHJhbnNhY3Rpb24uCgogICAz
LiAgQ2xpZW50IHVzZXJzIHNob3VsZCBiZSBhd2FyZSB0aGF0IHN0b3JpbmcgdGhlIHRhcmdldCBs
b2NhdGlvbiBvZgogICAgICAgYSBIVFRQIHJlc3BvbnNlIHdpdGggdGhlICIzMDEgTW92ZWQgUGVy
bWFuZW50bHkiIHN0YXR1cyBjb2RlCiAgICAgICBjb3VsZCBiZSBleHBsb2l0ZWQgYnkgYSBtYW4t
aW4tdGhlLW1pZGRsZSBhdHRhY2tlciB0byBibG9jayB0aGVtCiAgICAgICBwZXJtYW5lbnRseSBm
cm9tIGNvbnRhY3RpbmcgdGhlIGNvcnJlY3Qgc2VydmVyLgoKICAgNC4gIElmIG5vIG1lYXN1cmVz
IHRvIGF1dGhlbnRpY2F0ZSBhbmQgcHJvdGVjdCB0aGUgSFRUUCByZXNwb25zZXMgdG8KICAgICAg
IHB1c2hlZCBBbm5vdW5jZW1lbnQgbWVzc2FnZXMgYXJlIGluIHBsYWNlIHRoZWlyIGluZm9ybWF0
aW9uCiAgICAgICByZWdhcmRpbmcgdGhlIEFubm91bmNlbWVudCdzIHByb2Nlc3Npbmcgc3RhdGUg
bWF5IG5vdCBiZSB0cnVzdGVkLgogICAgICAgSW4gdGhhdCBjYXNlIHRoZSBvdmVyYWxsIGRlc2ln
biBvZiB0aGUgUEtJIHN5c3RlbSBtdXN0IG5vdCBkZXBlbmQKICAgICAgIG9uIHRoZSBBbm5vdW5j
ZW1lbnRzIGJlaW5nIHJlbGlhYmx5IHJlY2VpdmVkIGFuZCBwcm9jZXNzZWQgYnkKICAgICAgIHRo
ZWlyIGRlc3RpbmF0aW9uLgoKICAgNS4gIENNUCBwcm92aWRlcyBpbmJ1aWx0IGludGVncml0eSBw
cm90ZWN0aW9uIGFuZCBhdXRoZW50aWNhdGlvbi4KICAgICAgIFRoZSBpbmZvcm1hdGlvbiBjb21t
dW5pY2F0ZWQgdW5lbmNyeXB0ZWQgaW4gQ01QIG1lc3NhZ2VzIGRvZXMgbm90CiAgICAgICBjb250
YWluIHNlbnNpdGl2ZSBpbmZvcm1hdGlvbiBlbmRhbmdlcmluZyB0aGUgc2VjdXJpdHkgb2YgdGhl
IFBLSQogICAgICAgd2hlbiBpbnRlcmNlcHRlZC4gIEhvd2V2ZXIsIGl0IG1pZ2h0IGJlIHBvc3Np
YmxlIGZvciBhbgogICAgICAgZWF2ZXNkcm9wcGVyIHRvIHV0aWxpemUgdGhlIGF2YWlsYWJsZSBp
bmZvcm1hdGlvbiB0byBnYXRoZXIKICAgICAgIGNvbmZpZGVudGlhbCB0ZWNobmljYWwgb3IgYnVz
aW5lc3MgY3JpdGljYWwgaW5mb3JtYXRpb24uCiAgICAgICBUaGVyZWZvcmUgdXNlcnMgb2YgdGhl
IEhUVFAgdHJhbnNwb3J0IGZvciBDTVAgbWlnaHQgd2FudCB0bwogICAgICAgY29uc2lkZXIgdXNp
bmcgSFRUUCBvdmVyIFRMUyBhY2NvcmRpbmcgdG8gW1JGQzI4MThdIG9yIHZpcnR1YWwKICAgICAg
IHByaXZhdGUgbmV0d29ya3MgY3JlYXRlZCBlLmcuIGJ5IHV0aWxpemluZyBJbnRlcm5ldCBQcm90
b2NvbAogICAgICAgU2VjdXJpdHkgYWNjb3JkaW5nIHRvIFtSRkM0MzAxXS4KCgoKCgoKCgoKCgpL
YXVzZSAmIFBleWxvICAgICAgICAgICBFeHBpcmVzIE5vdmVtYmVyIDE2LCAyMDEyICAgICAgICAg
ICAgICBbUGFnZSAxMF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgIENNUHRyYW5z
ICAgICAgICAgICAgICAgICAgICAgICAgTWF5IDIwMTIKCgo2LiAgSUFOQSBDb25zaWRlcmF0aW9u
cwoKICAgVGhlIElBTkEgaGFzIGFscmVhZHkgcmVnaXN0ZXJlZCB0aGUgTUlNRSBtZWRpYSB0eXBl
ICJhcHBsaWNhdGlvbi8KICAgcGtpeGNtcCIgZm9yIGlkZW50aWZ5aW5nIENNUCBzZXF1ZW5jZXMg
ZHVlIHRvIGFuIHJlcXVlc3QgbWFkZSBpbgogICBjb25uZWN0aW9uIHdpdGggW1JGQzI1MTBdLgoK
ICAgTm8gZnVydGhlciBhY3Rpb24gYnkgdGhlIElBTkEgaXMgbmVjZXNzYXJ5IGZvciB0aGlzIGRv
Y3VtZW50IG9yIGFueQogICBhbnRpY2lwYXRlZCB1cGRhdGVzLgoKCgoKCgoKCgoKCgoKCgoKCgoK
CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKS2F1c2UgJiBQZXlsbyAgICAgICAgICAgRXhwaXJlcyBO
b3ZlbWJlciAxNiwgMjAxMiAgICAgICAgICAgICAgW1BhZ2UgMTFdCgwKSW50ZXJuZXQtRHJhZnQg
ICAgICAgICAgICAgICAgICBDTVB0cmFucyAgICAgICAgICAgICAgICAgICAgICAgIE1heSAyMDEy
CgoKNy4gIEFja25vd2xlZGdtZW50cwoKICAgVW50aWwgdGhlIGZpZnRoIGRyYWZ0IHZlcnNpb24g
b2YgdGhpcyBkb2N1bWVudCwgcmVsZWFzZWQgb24gTm92ZW1iZXIKICAgMjR0aCAyMDAwLCB0aGUg
c29sZSBhdXRob3JzIHdlcmUgQW1pdCBLYXBvb3IgYW5kIFJvbmFsZCBUc2NobGFlciBmcm9tCiAg
IENlcnRpY29tLiAgVXAgdG8gdGhpcyBwb2ludCB0aGUgbm93IHJlbW92ZWQgVENQLUJhc2VkIHRy
YW5zcG9ydCB3YXMKICAgZGVzY3JpYmVkIGluIGRldGFpbC4gIFRoZXkgYXJlIG5vdCBhdmFpbGFi
bGUgZm9yIHRoaXMgd29ya2luZyBvbiB0aGlzCiAgIGRvY3VtZW50IGFueW1vcmUgYXQgdGhlIHRp
bWUgaXQgaXMgZW50ZXJpbmcgdGhlICJBdXRob3JzIEZpbmFsIFJldmlldwogICBzdGF0ZSBBVVRI
NDgiLiAgQXMgdGhleSB0aGVyZWZvcmUgY2Fubm90IGFwcHJvdmUgdGhpcyBkb2N1bWVudCBhcyBp
dAogICB3b3VsZCBiZSBuZWNlc3NhcnksIHRoZWlyIG5hbWVzIHdlcmUgbW92ZWQgdG8gdGhpcyBz
ZWN0aW9uLiAgVGhlaXIKICAgY29udGFjdCBkYXRhIGFzIG9yaWdpbmFsbHkgc3RhdGVkIGJ5IHRo
ZW0gaXMgYXMgZm9sbG93czoKCiAgICAgIEFtaXQgS2Fwb29yCiAgICAgIENlcnRpY29tCiAgICAg
IDI1ODAxIEluZHVzdHJpYWwgQmx2ZAogICAgICBIYXl3YXJkLCBDQQogICAgICBVUwogICAgICBF
bWFpbDogYW1pdEB0cnVzdHBvaW50LmNvbQoKICAgICAgUm9uYWxkIFRzY2hhbGFlcgogICAgICBD
ZXJ0aWNvbQogICAgICAyNTgwMSBJbmR1c3RyaWFsIEJsdmQKICAgICAgSGF5d2FyZCwgQ0EKICAg
ICAgVVMKICAgICAgRW1haWw6IHJvbmFsZEB0cnVzdHBvaW50LmNvbQoKICAgVGhlIGF1dGhvcnMg
Z3JhdGVmdWxseSBhY2tub3dsZWRnZSB0aGUgY29udHJpYnV0aW9ucyBvZiB2YXJpb3VzCiAgIG1l
bWJlcnMgb2YgdGhlIElFVEYgUEtJWCBXb3JraW5nIEdyb3VwIGFuZCB0aGUgSUNTQSBDQS10YWxr
IG1haWxpbmcKICAgbGlzdCAoYSBsaXN0IHNvbGVseSBkZXZvdGVkIHRvIGRpc2N1c3NpbmcgQ01Q
IGludGVyb3BlcmFiaWxpdHkKICAgZWZmb3J0cykuCgogICBCeSBwcm92aWRpbmcgaWRlYXMsIGdp
dmluZyBoaW50cyBhbmQgZG9pbmcgaW52YWx1YWJsZSByZXZpZXcgd29yaywKICAgdGhlIGZvbGxv
d2luZyBhbHBoYWJldGljYWxseSBsaXN0ZWQgaW5kaXZpZHVhbHMgaGF2ZSBzaWduaWZpY2FudGx5
CiAgIGNvbnRyaWJ1dGVkIHRvIHRoaXMgZG9jdW1lbnQ6CgogICAgICBUb21hcyBHdXN0YXZzc29u
LCBQcmltZWtleQogICAgICBQZXRlciBHdXRtYW5uLCBVbml2ZXJzaXR5IG9mIEF1Y2tsYW5kCiAg
ICAgIFdvbGYtRGlldHJpY2ggTW9lbGxlciwgTm9raWEgU2llbWVucyBOZXR3b3JrcwoKCgoKCgoK
CgoKCgoKCkthdXNlICYgUGV5bG8gICAgICAgICAgIEV4cGlyZXMgTm92ZW1iZXIgMTYsIDIwMTIg
ICAgICAgICAgICAgIFtQYWdlIDEyXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAg
Q01QdHJhbnMgICAgICAgICAgICAgICAgICAgICAgICBNYXkgMjAxMgoKCjguICBSZWZlcmVuY2Vz
Cgo4LjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlcwoKICAgW1JGQzIxMTldICBCcmFkbmVyLCBTLiwg
IktleSB3b3JkcyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5kaWNhdGUKICAgICAgICAgICAgICBSZXF1
aXJlbWVudCBMZXZlbHMiLCBCQ1AgMTQsIFJGQyAyMTE5LCBNYXJjaCAxOTk3LgoKICAgW1JGQzI1
MTBdICBBZGFtcywgQy4gYW5kIFMuIEZhcnJlbGwsICJJbnRlcm5ldCBYLjUwOSBQdWJsaWMgS2V5
CiAgICAgICAgICAgICAgSW5mcmFzdHJ1Y3R1cmUgQ2VydGlmaWNhdGUgTWFuYWdlbWVudCBQcm90
b2NvbHMiLAogICAgICAgICAgICAgIFJGQyAyNTEwLCBNYXJjaCAxOTk5LgoKICAgW1JGQzI2MTZd
ICBGaWVsZGluZywgUi4sIEdldHR5cywgSi4sIE1vZ3VsLCBKLiwgRnJ5c3R5aywgSC4sCiAgICAg
ICAgICAgICAgTWFzaW50ZXIsIEwuLCBMZWFjaCwgUC4sIGFuZCBULiBCZXJuZXJzLUxlZSwgIkh5
cGVydGV4dAogICAgICAgICAgICAgIFRyYW5zZmVyIFByb3RvY29sIC0tIEhUVFAvMS4xIiwgUkZD
IDI2MTYsIEp1bmUgMTk5OS4KCiAgIFtSRkMzOTg2XSAgQmVybmVycy1MZWUsIFQuLCBGaWVsZGlu
ZywgUi4sIGFuZCBMLiBNYXNpbnRlciwgIlVuaWZvcm0KICAgICAgICAgICAgICBSZXNvdXJjZSBJ
ZGVudGlmaWVyIChVUkkpOiBHZW5lcmljIFN5bnRheCIsIFNURCA2NiwKICAgICAgICAgICAgICBS
RkMgMzk4NiwgSmFudWFyeSAyMDA1LgoKICAgW1JGQzQyMTBdICBBZGFtcywgQy4sIEZhcnJlbGws
IFMuLCBLYXVzZSwgVC4sIGFuZCBULiBNb25vbmVuLAogICAgICAgICAgICAgICJJbnRlcm5ldCBY
LjUwOSBQdWJsaWMgS2V5IEluZnJhc3RydWN0dXJlIENlcnRpZmljYXRlCiAgICAgICAgICAgICAg
TWFuYWdlbWVudCBQcm90b2NvbCAoQ01QKSIsIFJGQyA0MjEwLCBTZXB0ZW1iZXIgMjAwNS4KCjgu
Mi4gIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMKCiAgIFtSRkMxOTQ1XSAgQmVybmVycy1MZWUsIFQu
LCBGaWVsZGluZywgUi4sIGFuZCBILiBOaWVsc2VuLCAiSHlwZXJ0ZXh0CiAgICAgICAgICAgICAg
VHJhbnNmZXIgUHJvdG9jb2wgLS0gSFRUUC8xLjAiLCBSRkMgMTk0NSwgTWF5IDE5OTYuCgogICBb
UkZDMjgxOF0gIFJlc2NvcmxhLCBFLiwgIkhUVFAgT3ZlciBUTFMiLCBSRkMgMjgxOCwgTWF5IDIw
MDAuCgogICBbUkZDNDMwMV0gIEtlbnQsIFMuIGFuZCBLLiBTZW8sICJTZWN1cml0eSBBcmNoaXRl
Y3R1cmUgZm9yIHRoZQogICAgICAgICAgICAgIEludGVybmV0IFByb3RvY29sIiwgUkZDIDQzMDEs
IERlY2VtYmVyIDIwMDUuCgogICBbUkZDNTI0Nl0gIERpZXJrcywgVC4gYW5kIEUuIFJlc2Nvcmxh
LCAiVGhlIFRyYW5zcG9ydCBMYXllciBTZWN1cml0eQogICAgICAgICAgICAgIChUTFMpIFByb3Rv
Y29sIFZlcnNpb24gMS4yIiwgUkZDIDUyNDYsIEF1Z3VzdCAyMDA4LgoKCgoKCgoKCgoKCgoKCgoK
S2F1c2UgJiBQZXlsbyAgICAgICAgICAgRXhwaXJlcyBOb3ZlbWJlciAxNiwgMjAxMiAgICAgICAg
ICAgICAgW1BhZ2UgMTNdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICBDTVB0cmFu
cyAgICAgICAgICAgICAgICAgICAgICAgIE1heSAyMDEyCgoKQXV0aG9ycycgQWRkcmVzc2VzCgog
ICBUb21pIEthdXNlCiAgIFRlY3RpYSBDb3Jwb3JhdGlvbgogICBLdW1wdWxhbnRpZSAzCiAgIEhl
bHNpbmtpICAwMDUyMAogICBGaW5sYW5kCgogICBFbWFpbDogdG9rYUB0ZWN0aWEuY29tCgoKICAg
TWFydGluIFBleWxvCiAgIE5va2lhIFNpZW1lbnMgTmV0d29ya3MKICAgTGlubm9pdHVzdGllIDYK
ICAgRXNwb28gIDAyNjAwCiAgIEZpbmxhbmQKCiAgIEVtYWlsOiBtYXJ0aW4ucGV5bG9AbnNuLmNv
bQoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgpLYXVzZSAmIFBleWxvICAgICAgICAg
ICBFeHBpcmVzIE5vdmVtYmVyIDE2LCAyMDEyICAgICAgICAgICAgICBbUGFnZSAxNF0KDAo=

------_=_NextPart_001_01CD32B5.7BD9515E--

From david.black@emc.com  Tue May 15 11:12:00 2012
Return-Path: <david.black@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3033721F8759 for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 11:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.477
X-Spam-Level: 
X-Spam-Status: No, score=-110.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5eyt8OAxJM7C for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 11:11:59 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD8521F8757 for <gen-art@ietf.org>; Tue, 15 May 2012 11:11:59 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q4FIBiQc002192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 May 2012 14:11:45 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 15 May 2012 14:11:37 -0400
Received: from mxhub22.corp.emc.com (mxhub22.corp.emc.com [128.222.70.134]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q4FIBaE4005708; Tue, 15 May 2012 14:11:36 -0400
Received: from mx15a.corp.emc.com ([169.254.1.236]) by mxhub22.corp.emc.com ([128.222.70.134]) with mapi; Tue, 15 May 2012 14:11:36 -0400
From: <david.black@emc.com>
To: <richard.clayton@cl.cam.ac.uk>, <msk@cloudmark.com>, <gen-art@ietf.org>
Date: Tue, 15 May 2012 14:11:35 -0400
Thread-Topic: Gen-ART review of draft-kucherawy-marf-source-ports-03
Thread-Index: Ac0yxioEDxACVAT4RWGXKh8wSGTOFw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712057151FA@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: johnl@iecc.com, barryleiba@computer.org
Subject: [Gen-art] Gen-ART review of draft-kucherawy-marf-source-ports-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2012 18:12:00 -0000

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

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

Document: draft-kucherawy-marf-source-ports-03
Reviewer: David L. Black
Review Date: May 15, 2012
IETF LC End Date: June 4, 2012

This is a short draft that adds source ports to the Abuse Reporting Format =
for mail abuse reporting.

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

Major issues: None.

Minor issues: None.

Nits/editorial comments:

  In section 3, please summarize what the "CFWS" ABNF element represents (c=
omments and folding white space).

  Typo in last paragraph of section 3: "RECOMMENED" -> "RECOMMENDED"

  idnits 2.12.13 didn't find anything that requires attention.

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


From msk@cloudmark.com  Tue May 15 11:15:48 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEF8621F87EE for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 11:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qkeHWICaG7Db for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 11:15:47 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id 1690721F87ED for <gen-art@ietf.org>; Tue, 15 May 2012 11:15:41 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.26]) by mail.cloudmark.com with bizsmtp id AJFX1j0010as01C01JFXxz; Tue, 15 May 2012 11:15:40 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=eMmRfQV1 c=1 sm=1 a=QMZKka45TBd+hNGtXG2bIg==:17 a=LvckAehuu68A:10 a=t-S1CdA-bjIA:10 a=zutiEJmiVI4A:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=G0_B3m8xAAAA:8 a=B6GvL0XKAAAA:8 a=48vgC7mUAAAA:8 a=3DW5ysfuAAAA:8 a=8qSefF8wAAAA:8 a=M3ye38umb6-IZjpXCI4A:9 a=z6sI0IIig7CTUWiyJG0A:7 a=CjuIK1q_8ugA:10 a=lW_bInUQU2sA:10 a=lZB815dzVvQA:10 a=2SAumGWBsQEA:10 a=mHZC5r8sFEQA:10 a=QMZKka45TBd+hNGtXG2bIg==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::54de:dc60:5f3e:334%10]) with mapi id 14.01.0355.002; Tue, 15 May 2012 11:15:31 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "david.black@emc.com" <david.black@emc.com>, "richard.clayton@cl.cam.ac.uk" <richard.clayton@cl.cam.ac.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-kucherawy-marf-source-ports-03
Thread-Index: Ac0yxioEDxACVAT4RWGXKh8wSGTOFwAACSTg
Date: Tue, 15 May 2012 18:15:30 +0000
Message-ID: <9452079D1A51524AA5749AD23E0039281229BF@exch-mbx901.corp.cloudmark.com>
References: <8D3D17ACE214DC429325B2B98F3AE712057151FA@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712057151FA@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1337105740; bh=bU5a9fXONf+BjyZWh8vUhfC7zJXwciyHtD15PppKeIg=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=kHfCijesT8kz7B1oI2HFMPQ0/NvspHAMf1jgGx3ISRfZ8Pt+c7eiqRzw2elYbPdSs 35QVGtNuyV1Wl3XEwrl56LkrKov31qNX+5HY2djsLzFAg1a/fbIE5T4/ZkiT63SIS9 bJcjYfX3Y3MXCRy0Jd+tCSimUOLINs4F7V0HGHhk=
Cc: "johnl@iecc.com" <johnl@iecc.com>, "barryleiba@computer.org" <barryleiba@computer.org>
Subject: Re: [Gen-art] Gen-ART review of draft-kucherawy-marf-source-ports-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2012 18:15:48 -0000

> -----Original Message-----
> From: david.black@emc.com [mailto:david.black@emc.com]
> Sent: Tuesday, May 15, 2012 11:12 AM
> To: richard.clayton@cl.cam.ac.uk; Murray S. Kucherawy; gen-art@ietf.org
> Cc: david.black@emc.com; johnl@iecc.com; barryleiba@computer.org
> Subject: Gen-ART review of draft-kucherawy-marf-source-ports-03
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Ah, David.  We meet again.  :-)

> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-kucherawy-marf-source-ports-03
> Reviewer: David L. Black
> Review Date: May 15, 2012
> IETF LC End Date: June 4, 2012
>=20
> This is a short draft that adds source ports to the Abuse Reporting
> Format for mail abuse reporting.
>=20
> Summary:
> This draft is basically ready for publication, but has nits that should
> be fixed before publication.
>=20
> Major issues: None.
>=20
> Minor issues: None.
>=20
> Nits/editorial comments:
>=20
>   In section 3, please summarize what the "CFWS" ABNF element
> represents (comments and folding white space).
>=20
>   Typo in last paragraph of section 3: "RECOMMENED" -> "RECOMMENDED"

Sounds reasonable to me.  I'll include both of those in -04 after LC closes=
.

Thanks for the review!

Cheers,
-MSK

From christer.holmberg@ericsson.com  Tue May 15 11:50:31 2012
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 186C821F881A for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 11:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.164
X-Spam-Level: 
X-Spam-Status: No, score=-6.164 tagged_above=-999 required=5 tests=[AWL=0.085,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dsee-irQS6kk for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 11:50:30 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 776E021F8779 for <gen-art@ietf.org>; Tue, 15 May 2012 11:50:29 -0700 (PDT)
X-AuditID: c1b4fb30-b7be1ae0000059fc-56-4fb2a5744077
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id A7.DB.23036.475A2BF4; Tue, 15 May 2012 20:50:28 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.64]) by esessmw0256.eemea.ericsson.se ([153.88.115.96]) with mapi; Tue, 15 May 2012 20:50:28 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Peylo, Martin (NSN - FI/Espoo)" <martin.peylo@nsn.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org" <draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org>
Date: Tue, 15 May 2012 20:48:47 +0200
Thread-Topic: Genart review of draft-ietf-pkix-cmp-transport-protocols-18
Thread-Index: Ac0xoqdXoxjsfzuuSE+UhyHHLVaitgBDSLxQAAbkgBs=
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C44001372@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A05852C4442A39D@ESESSCMS0356.eemea.ericsson.se>, <3BF363C82C184B46930A905352C2013F021E39F1@FIESEXC006.nsn-intra.net>
In-Reply-To: <3BF363C82C184B46930A905352C2013F021E39F1@FIESEXC006.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Gen-art] Genart review of draft-ietf-pkix-cmp-transport-protocols-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2012 18:50:31 -0000

Hi Martin,

Your suggested changes look good.

Regarding Q2-2, however, I belive the section is normally called just "Conv=
entions".

Regards,

Christer

________________________________
From: Peylo, Martin (NSN - FI/Espoo) [martin.peylo@nsn.com]
Sent: Tuesday, May 15, 2012 7:12 PM
To: Christer Holmberg; gen-art@ietf.org; draft-ietf-pkix-cmp-transport-prot=
ocols.all@tools.ietf.org
Subject: RE: Genart review of draft-ietf-pkix-cmp-transport-protocols-18


Hi Christer,



thank you for your review and valuable nits. Please find my comments inline=
, prefixed with an =93MP=94.



Attached, the so far unpublished (pre-)19 version of the draft implementing=
 the changes described below.



Kind regards,

Martin

From: ext Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: Monday, May 14, 2012 10:35 AM
To: gen-art@ietf.org; draft-ietf-pkix-cmp-transport-protocols.all@tools.iet=
f.org
Subject: Genart review of draft-ietf-pkix-cmp-transport-protocols-18

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-pkix-cmp-transport-protocols-18.txt
Reviewer: Christer Holmberg
Review Date: 14 May 2012
IETF LC End Date: 21 May 2012
IESG Telechat date: 24 May 2012

Summary: The draft is ready for publication, but with a number of editorial=
 nits.

Major issues: -

Minor issues: -

Nits/editorial comments:


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

Q1-1: In my opinion the following statement (1st paragraph) can be removed:

   "This document defines the transport mechanism which was removed from th=
e main CMP specification
   with the second release and referred to be in a separate document."



Because, the following paragraphs describes very well the background, and j=
ustification of the new transport. There is no need to say whether the new =
transport was originally supposed to be part of the main spec or not.

MP: Removed.



Q1-2: In the 2nd paragraph, please add reference to HTTP on first occurrenc=
e.



MP: although it=92s the first occurrence in 2nd paragraph, I would prefer t=
o add the references to RFC 1945 and RFC2616 to the 4th paragraph. Reason i=
s that 2nd paragraph contains only an historic reference - and there (in RF=
C2510) it was not referenced what HTTP is either. See below how the 4th par=
agraph will then look like when also fixing Q1-3.



Q1-3: The following statement is a little confusing:



   "During the long time it existed as draft, this RFC was undergoing drast=
ic changes."



There hasn=92t been any changes to the RFC, but to the draft. So, I would s=
ay something like:



            =93Before this document was published as an RFC, the draft vers=
ion underwent drastic changes during the work process.=94



MP: Changed, I inserted =93long-lasting=94 to highlight the long time it to=
ok from draft-1 (June 22, 2000) to now. So the paragraph is now:



   Before this document was published as an RFC, the draft version

   underwent drastic changes during the long-lasting work process.  The

   "TCP-Based Management Protocol" was enhanced and a TCP-Messages-over-

   HTTP transport specification appeared.  As both proved to be needless

   and cumbersome, implementers preferred to use plain HTTP transport

   following [RFC1945] or [RFC2616].  This document now reflects that by

   exclusively describing HTTP as transport protocol for CMP.



Section 2:

-----------



Q2-1: The section only contains the RFC 2119 terminology, but that is norma=
lly in a =93Conventions=94 section.



Q2-2: As there are no requirements listed, I suggest to remove the section.



MP: This was totally missed so far. I will change this section to =93Conven=
tions Used in This Document=94 as of course the RFC 2119 terminology is use=
d throughout the document.



Section 3.2:

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



Q3_2-1: The text says:



=93However, neither HTTP nor this protocol are designed to correlate messag=
es on the same

            connection in any meaningful way;=94



It is a little unclear what =93this protocol=94 refers to.



MP: changed to =93=85 neither HTTP nor the protocol specified in this docum=
ent are designed=85=94



Section 4:

-----------



Q4-1: It is a little unclear what is meant by =93legacy implementations=94.=
 Do you consider implementations based on earlier versions of the draft as =
=93legacy=94? In my opinion a =93legacy=94 implementation is based on a pre=
viously published standard/RFC.



So, if the section is supposed to cover issues with earlier versions of thi=
s draft, I think it should be called something else.



MP: I=92m following a proposal from Sean Turner here and take his excellent=
 suggestion to replace the complete section.



> 4.  Implementation Considerations

>

>     Implementors should be aware that implementations might exist that

>     use a different approach for HTTP transport because this document

>     has been under development for more than a decade.  Further,

>     implementations based on earlier drafts of this

>     document might use an unregistered "application/pkixcmp-poll" MIME

>     type.

>







Regards,



Christer

From martin.peylo@nsn.com  Tue May 15 11:58:44 2012
Return-Path: <martin.peylo@nsn.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7047921F86D8 for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 11:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfFjrVQVYwzp for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 11:58:43 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 2F5E921F86C7 for <gen-art@ietf.org>; Tue, 15 May 2012 11:58:42 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q4FIwYft021911 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 May 2012 20:58:34 +0200
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q4FIwSjv011702; Tue, 15 May 2012 20:58:31 +0200
Received: from FIESEXC006.nsn-intra.net ([10.159.0.14]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 May 2012 20:58:30 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 15 May 2012 21:58:25 +0300
Message-ID: <3BF363C82C184B46930A905352C2013F021E3A49@FIESEXC006.nsn-intra.net>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852C44001372@ESESSCMS0356.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Genart review of draft-ietf-pkix-cmp-transport-protocols-18
Thread-Index: Ac0xoqdXoxjsfzuuSE+UhyHHLVaitgBDSLxQAAbkgBsAABThMA==
References: <7F2072F1E0DE894DA4B517B93C6A05852C4442A39D@ESESSCMS0356.eemea.ericsson.se>, <3BF363C82C184B46930A905352C2013F021E39F1@FIESEXC006.nsn-intra.net> <7F2072F1E0DE894DA4B517B93C6A05852C44001372@ESESSCMS0356.eemea.ericsson.se>
From: "Peylo, Martin (NSN - FI/Espoo)" <martin.peylo@nsn.com>
To: "ext Christer Holmberg" <christer.holmberg@ericsson.com>, <gen-art@ietf.org>, <draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org>
X-OriginalArrivalTime: 15 May 2012 18:58:30.0459 (UTC) FILETIME=[B7F498B0:01CD32CC]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 6226
X-purgate-ID: 151667::1337108319-00005945-4F0DD4F0/0-0/0-0
Subject: Re: [Gen-art] Genart review of draft-ietf-pkix-cmp-transport-protocols-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2012 18:58:44 -0000

Hi Christer,

about Q2-2 I also had thought so - but I did some spot tests in some
RFCs and there I found always "Conventions Used in This Document".  E.g.
(wildly random RFCs).

http://tools.ietf.org/html/rfc6001
http://tools.ietf.org/html/rfc6005
http://tools.ietf.org/html/rfc6188#section-1.1

I saw one with "Conventions and Terminology" (didn't note down the
number) but there was really some more terminology.

Kind regards,
Martin




-----Original Message-----
From: ext Christer Holmberg [mailto:christer.holmberg@ericsson.com]=20
Sent: Tuesday, May 15, 2012 9:49 PM
To: Peylo, Martin (NSN - FI/Espoo); gen-art@ietf.org;
draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org
Subject: RE: Genart review of draft-ietf-pkix-cmp-transport-protocols-18

Hi Martin,

Your suggested changes look good.

Regarding Q2-2, however, I belive the section is normally called just
"Conventions".

Regards,

Christer

________________________________
From: Peylo, Martin (NSN - FI/Espoo) [martin.peylo@nsn.com]
Sent: Tuesday, May 15, 2012 7:12 PM
To: Christer Holmberg; gen-art@ietf.org;
draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org
Subject: RE: Genart review of draft-ietf-pkix-cmp-transport-protocols-18


Hi Christer,



thank you for your review and valuable nits. Please find my comments
inline, prefixed with an "MP".



Attached, the so far unpublished (pre-)19 version of the draft
implementing the changes described below.



Kind regards,

Martin

From: ext Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: Monday, May 14, 2012 10:35 AM
To: gen-art@ietf.org;
draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org
Subject: Genart review of draft-ietf-pkix-cmp-transport-protocols-18

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

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

Document: draft-ietf-pkix-cmp-transport-protocols-18.txt
Reviewer: Christer Holmberg
Review Date: 14 May 2012
IETF LC End Date: 21 May 2012
IESG Telechat date: 24 May 2012

Summary: The draft is ready for publication, but with a number of
editorial nits.

Major issues: -

Minor issues: -

Nits/editorial comments:


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

Q1-1: In my opinion the following statement (1st paragraph) can be
removed:

   "This document defines the transport mechanism which was removed from
the main CMP specification
   with the second release and referred to be in a separate document."



Because, the following paragraphs describes very well the background,
and justification of the new transport. There is no need to say whether
the new transport was originally supposed to be part of the main spec or
not.

MP: Removed.



Q1-2: In the 2nd paragraph, please add reference to HTTP on first
occurrence.



MP: although it's the first occurrence in 2nd paragraph, I would prefer
to add the references to RFC 1945 and RFC2616 to the 4th paragraph.
Reason is that 2nd paragraph contains only an historic reference - and
there (in RFC2510) it was not referenced what HTTP is either. See below
how the 4th paragraph will then look like when also fixing Q1-3.



Q1-3: The following statement is a little confusing:



   "During the long time it existed as draft, this RFC was undergoing
drastic changes."



There hasn't been any changes to the RFC, but to the draft. So, I would
say something like:



            "Before this document was published as an RFC, the draft
version underwent drastic changes during the work process."



MP: Changed, I inserted "long-lasting" to highlight the long time it
took from draft-1 (June 22, 2000) to now. So the paragraph is now:



   Before this document was published as an RFC, the draft version

   underwent drastic changes during the long-lasting work process.  The

   "TCP-Based Management Protocol" was enhanced and a TCP-Messages-over-

   HTTP transport specification appeared.  As both proved to be needless

   and cumbersome, implementers preferred to use plain HTTP transport

   following [RFC1945] or [RFC2616].  This document now reflects that by

   exclusively describing HTTP as transport protocol for CMP.



Section 2:

-----------



Q2-1: The section only contains the RFC 2119 terminology, but that is
normally in a "Conventions" section.



Q2-2: As there are no requirements listed, I suggest to remove the
section.



MP: This was totally missed so far. I will change this section to
"Conventions Used in This Document" as of course the RFC 2119
terminology is used throughout the document.



Section 3.2:

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



Q3_2-1: The text says:



"However, neither HTTP nor this protocol are designed to correlate
messages on the same

            connection in any meaningful way;"



It is a little unclear what "this protocol" refers to.



MP: changed to "... neither HTTP nor the protocol specified in this
document are designed..."



Section 4:

-----------



Q4-1: It is a little unclear what is meant by "legacy implementations".
Do you consider implementations based on earlier versions of the draft
as "legacy"? In my opinion a "legacy" implementation is based on a
previously published standard/RFC.



So, if the section is supposed to cover issues with earlier versions of
this draft, I think it should be called something else.



MP: I'm following a proposal from Sean Turner here and take his
excellent suggestion to replace the complete section.



> 4.  Implementation Considerations

>

>     Implementors should be aware that implementations might exist that

>     use a different approach for HTTP transport because this document

>     has been under development for more than a decade.  Further,

>     implementations based on earlier drafts of this

>     document might use an unregistered "application/pkixcmp-poll" MIME

>     type.

>







Regards,



Christer

From christer.holmberg@ericsson.com  Tue May 15 12:02:22 2012
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8959221F86EB for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 12:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.165
X-Spam-Level: 
X-Spam-Status: No, score=-6.165 tagged_above=-999 required=5 tests=[AWL=0.084,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V4HWBu5xJfL6 for <gen-art@ietfa.amsl.com>; Tue, 15 May 2012 12:02:21 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE8021F86E1 for <gen-art@ietf.org>; Tue, 15 May 2012 12:02:20 -0700 (PDT)
X-AuditID: c1b4fb2d-b7bbfae000005e4b-42-4fb2a83b4091
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id BF.E6.24139.B38A2BF4; Tue, 15 May 2012 21:02:19 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.64]) by esessmw0256.eemea.ericsson.se ([153.88.115.96]) with mapi; Tue, 15 May 2012 21:02:19 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Peylo, Martin (NSN - FI/Espoo)" <martin.peylo@nsn.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org" <draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org>
Date: Tue, 15 May 2012 21:01:35 +0200
Thread-Topic: Genart review of draft-ietf-pkix-cmp-transport-protocols-18
Thread-Index: Ac0xoqdXoxjsfzuuSE+UhyHHLVaitgBDSLxQAAbkgBsAABThMAAAXZPM
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C44001373@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A05852C4442A39D@ESESSCMS0356.eemea.ericsson.se>, <3BF363C82C184B46930A905352C2013F021E39F1@FIESEXC006.nsn-intra.net> <7F2072F1E0DE894DA4B517B93C6A05852C44001372@ESESSCMS0356.eemea.ericsson.se>, <3BF363C82C184B46930A905352C2013F021E3A49@FIESEXC006.nsn-intra.net>
In-Reply-To: <3BF363C82C184B46930A905352C2013F021E3A49@FIESEXC006.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Gen-art] Genart review of draft-ietf-pkix-cmp-transport-protocols-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2012 19:02:22 -0000

Hi,

Ok, if it's used elsewhere, I'm fine with it :)

Regards,

Christer

________________________________________
From: Peylo, Martin (NSN - FI/Espoo) [martin.peylo@nsn.com]
Sent: Tuesday, May 15, 2012 9:58 PM
To: Christer Holmberg; gen-art@ietf.org; draft-ietf-pkix-cmp-transport-prot=
ocols.all@tools.ietf.org
Subject: RE: Genart review of draft-ietf-pkix-cmp-transport-protocols-18

Hi Christer,

about Q2-2 I also had thought so - but I did some spot tests in some
RFCs and there I found always "Conventions Used in This Document".  E.g.
(wildly random RFCs).

http://tools.ietf.org/html/rfc6001
http://tools.ietf.org/html/rfc6005
http://tools.ietf.org/html/rfc6188#section-1.1

I saw one with "Conventions and Terminology" (didn't note down the
number) but there was really some more terminology.

Kind regards,
Martin




-----Original Message-----
From: ext Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: Tuesday, May 15, 2012 9:49 PM
To: Peylo, Martin (NSN - FI/Espoo); gen-art@ietf.org;
draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org
Subject: RE: Genart review of draft-ietf-pkix-cmp-transport-protocols-18

Hi Martin,

Your suggested changes look good.

Regarding Q2-2, however, I belive the section is normally called just
"Conventions".

Regards,

Christer

________________________________
From: Peylo, Martin (NSN - FI/Espoo) [martin.peylo@nsn.com]
Sent: Tuesday, May 15, 2012 7:12 PM
To: Christer Holmberg; gen-art@ietf.org;
draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org
Subject: RE: Genart review of draft-ietf-pkix-cmp-transport-protocols-18


Hi Christer,



thank you for your review and valuable nits. Please find my comments
inline, prefixed with an "MP".



Attached, the so far unpublished (pre-)19 version of the draft
implementing the changes described below.



Kind regards,

Martin

From: ext Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: Monday, May 14, 2012 10:35 AM
To: gen-art@ietf.org;
draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org
Subject: Genart review of draft-ietf-pkix-cmp-transport-protocols-18

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

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

Document: draft-ietf-pkix-cmp-transport-protocols-18.txt
Reviewer: Christer Holmberg
Review Date: 14 May 2012
IETF LC End Date: 21 May 2012
IESG Telechat date: 24 May 2012

Summary: The draft is ready for publication, but with a number of
editorial nits.

Major issues: -

Minor issues: -

Nits/editorial comments:


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

Q1-1: In my opinion the following statement (1st paragraph) can be
removed:

   "This document defines the transport mechanism which was removed from
the main CMP specification
   with the second release and referred to be in a separate document."



Because, the following paragraphs describes very well the background,
and justification of the new transport. There is no need to say whether
the new transport was originally supposed to be part of the main spec or
not.

MP: Removed.



Q1-2: In the 2nd paragraph, please add reference to HTTP on first
occurrence.



MP: although it's the first occurrence in 2nd paragraph, I would prefer
to add the references to RFC 1945 and RFC2616 to the 4th paragraph.
Reason is that 2nd paragraph contains only an historic reference - and
there (in RFC2510) it was not referenced what HTTP is either. See below
how the 4th paragraph will then look like when also fixing Q1-3.



Q1-3: The following statement is a little confusing:



   "During the long time it existed as draft, this RFC was undergoing
drastic changes."



There hasn't been any changes to the RFC, but to the draft. So, I would
say something like:



            "Before this document was published as an RFC, the draft
version underwent drastic changes during the work process."



MP: Changed, I inserted "long-lasting" to highlight the long time it
took from draft-1 (June 22, 2000) to now. So the paragraph is now:



   Before this document was published as an RFC, the draft version

   underwent drastic changes during the long-lasting work process.  The

   "TCP-Based Management Protocol" was enhanced and a TCP-Messages-over-

   HTTP transport specification appeared.  As both proved to be needless

   and cumbersome, implementers preferred to use plain HTTP transport

   following [RFC1945] or [RFC2616].  This document now reflects that by

   exclusively describing HTTP as transport protocol for CMP.



Section 2:

-----------



Q2-1: The section only contains the RFC 2119 terminology, but that is
normally in a "Conventions" section.



Q2-2: As there are no requirements listed, I suggest to remove the
section.



MP: This was totally missed so far. I will change this section to
"Conventions Used in This Document" as of course the RFC 2119
terminology is used throughout the document.



Section 3.2:

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



Q3_2-1: The text says:



"However, neither HTTP nor this protocol are designed to correlate
messages on the same

            connection in any meaningful way;"



It is a little unclear what "this protocol" refers to.



MP: changed to "... neither HTTP nor the protocol specified in this
document are designed..."



Section 4:

-----------



Q4-1: It is a little unclear what is meant by "legacy implementations".
Do you consider implementations based on earlier versions of the draft
as "legacy"? In my opinion a "legacy" implementation is based on a
previously published standard/RFC.



So, if the section is supposed to cover issues with earlier versions of
this draft, I think it should be called something else.



MP: I'm following a proposal from Sean Turner here and take his
excellent suggestion to replace the complete section.



> 4.  Implementation Considerations

>

>     Implementors should be aware that implementations might exist that

>     use a different approach for HTTP transport because this document

>     has been under development for more than a decade.  Further,

>     implementations based on earlier drafts of this

>     document might use an unregistered "application/pkixcmp-poll" MIME

>     type.

>







Regards,



Christer=

From jmvalin@jmvalin.ca  Tue May 15 17:33:30 2012
Return-Path: <jmvalin@jmvalin.ca>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D18321F85F2; Tue, 15 May 2012 17:33:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQNhI0S0FQaq; Tue, 15 May 2012 17:33:26 -0700 (PDT)
Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by ietfa.amsl.com (Postfix) with ESMTP id 07FB921F85F1; Tue, 15 May 2012 17:33:26 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_+C3bRGW2uyqqCN0LMd/yZQ)"
Received: from [192.168.1.14] ([96.21.20.94]) by VL-VM-MR006.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0M4300KGTAVO2L70@VL-VM-MR006.ip.videotron.ca>; Tue, 15 May 2012 20:33:25 -0400 (EDT)
Message-id: <4FB2F5D0.7070701@jmvalin.ca>
Date: Tue, 15 May 2012 20:33:20 -0400
From: Jean-Marc Valin <jmvalin@jmvalin.ca>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
To: Elwyn Davies <elwynd@folly.org.uk>
References: <1337001184.23527.1544.camel@mightyatom.folly.org.uk>
In-reply-to: <1337001184.23527.1544.camel@mightyatom.folly.org.uk>
X-Enigmail-Version: 1.4.1
X-Mailman-Approved-At: Tue, 15 May 2012 23:33:06 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "codec@ietf.org" <codec@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-codec-opus.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-codec-opus-12.txt (completed)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 00:33:30 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_+C3bRGW2uyqqCN0LMd/yZQ)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Hi Elwyn,

Thanks for the very thorough review. We've addressed your issues and
submitted draft version -13. See our response to each of the issues you
raised (aggregated from all the authors) in the attached document.

Cheers,

	Jean-Marc

On 12-05-14 09:13 AM, Elwyn Davies 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-codec-opus-12.txt
> Reviewer:  Elwyn Davies
> Review Date:  14 May 2012 (completed)
> IETF LC End Date: 10 May 2012
> IESG Telechat date: (if known) -
> 

--Boundary_(ID_+C3bRGW2uyqqCN0LMd/yZQ)
Content-type: text/plain; CHARSET=US-ASCII; name=Gen-art.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=Gen-art.txt

Elwyn Davies wrote:
> Major issues: 
> Can we accept the code as normative?  If not how do we proceed?

The issue with code being normative was specifically addressed in 
the guidelines document for this WG (RFC 6569).

> Minor issues:
> Contrast between decoder descriptions of LP part and CELT part:  The
> SILK descriptions go into gory detail on the values used in lots of
> tables, etc., whereas the CELT part has a very limited treatment of the
> numeric values used (assuming reliance on finding the values in the
> reference implementation, either explictly or implicitly).  There are
> things to be said for both techniques.  I was wondering (while reading
> the SILK description) if the authors have any means of automatically
> generating the tables from the code in the SILK part (or vice versa) to
> avoid double maintenance. On the other hand, there are pieces of the
> CELT decoder description (especially in s4.3.3 where knowing numbers of
> bands, etc.) where some actual numbers would help comprehension.
> 

We have made many changes to section 4.3 (and 4.3.3 specifically) to address
the specific issues below. As for the tables, they are not generated
automatically.


> s2 (and more generally):  The splitting of the signal in the frequency
> domain into signal (components?) below and above 8kHz presumably
> requires that the signal is subjected to a Discrete Fourier Transform to
> allow the signal to be split.  I think sometging is needed in s2 to
> explain how this is managed (or if I don't understand, to explain why it
> isn't necessary).

No DFT is used. The lower band is obtained through resampling (which is already described) and the higher band is obtained by not coding the lower band with CELT (the text says that CELT starts at band 17 in hybrid mode). The explanation was reworded to make this as clear as possible at this point in the text.

> s4.1: Despite having found a copy of the range coding paper and tried to
> read it, I found the whole business of range coding opaque.  Given that
> this is (I think) fairly novel, some additional less opaque description
> could be very helpful to people trying to understand what is going on.
> In particular knowledge of how entropy coding works is pretty much a
> prerequisite.

Added a link to the Wikipedia article on range coding.

> s4.2.5, para 3:
>>     When switching from 20 ms to 10 ms, the 10 ms
>>     20 ms Opus frame, potentially leaving a hole that needs to be
>>     concealed from even a single packet loss.
> How?

As explained in the LBRR text, a 10 ms frame will only contain 10 ms LBRR data even if the previous frame was 20 ms, so there's 10 ms "missing".

> s4.2.5, para 4:
>> In order to properly produce LBRR frames under all conditions, an
>>     encoder might need to buffer up to 60 ms of audio and re-encode it
>>     during these transitions.  However, the reference implementation opts
>>     to disable LBRR frames at the transition point for simplicity.
>>
> Should this be phrased in RFC 2119 requiremenmts language?  The first
> part sounds like a SHOULD with the second part being the get out , but
> its not entirely clear what the consequences are other then simplicity.

There really is no SHOULD there. We're just describing possible strategies for encoding. In general, we have avoided 2119 language as much as possible for the encoder. However, the sentence, "Since transitions are relatively infrequent in normal usage, this does not have a significant impact on packet loss robustness," was added to alleviate any concerns about the consequences of this decision.

> ======================================================================
>              MINOR ISSUES ABOVE submitted as part 1 of review
> ======================================================================
> general/s11.2:  Several references [Hadamard], [Viterbi}, etc., are to
> Wikipaedia pages.  Whilst these are convenient (and only illustrative)
> they are not guaranteed to be very stable.  Better (i.e., more stable)
> references are desirable.

We believe that the links themselves should be quite stable. We could 
also link specific revisions in Wikipedia, but the quality of the content
is more likely to get better than worse. Considering
that these references are informational, we believe that Wikipedia is a
good source.

> s1, para 2:
>>     The decoder contains a great deal of integer and fixed-point
>>     arithmetic which must be performed exactly, including all rounding
>>     considerations,...
> Is this a MUST?  There are instances in the text which might contradict
> this (e.g., para 1 of s4.2.7.5 which has (capitalized) SHOULDs).

This sentence did not mean to imply that _all_ such arithmetic must be performed exactly, only that there exists a good deal of arithmetic for which this is true (for example, to achieve the final range check MUST from Section 6). Since it isn't clear at this point exactly which arithmetic is being referred to, we can't use RFC 2119 strength here. Replaced "must be" with "needs to be" to avoid the impression of an RFC 2119 requirement.

> s4.3:
> As a complete newcomer to CELT, I would have appreciated a more high
> level understanding of what CELT is doing at this point.  I  tried
> reading s4.3 without any additional input and found it very hard going.
> Eventually I gave up and went looking for some additional input.  This
> presentation seems to have a useful view 
> http://www.ietf.org/proceedings/79/slides/codec-2.pdf
> I think that it would be extremely helpful to have a description similar
> to this at this point in the document, even though there is some
> material in section 5.3 which could also be forward referenced.  Still
> the material in s5.3 does not start from the basic principles that CELT
> is using, and since these are essentially novel, it would be very good
> to give prospective implementers/users an understanding of what is going
> on.  Incidentally, I found the above IETF presentation more useful than
> http://www.celt-codec.org/presentations/misc/lca-celt.pdf
> Note that the SILK part seems rather less opaque.  It would also be
> useful to indicate numerically how many bands are involved and what the
> number of MDCT bins are in the various bands. 

The intro of section 4.3 has been expanded with general information about CELT
similar to what the codec-2.pdf slides from 79 included. 

> s4.3, last para: Can the 'out of range error' occur in the LP decoder? (if not why not?)

Added the following text:
"Such out of range errors cannot occur in the SILK layer."


> ======================================================================
> 
> Nits/editorial comments:
> 
> global: bytes ->  octets

We believe that in the field of audio codecs, the mention of "byte" without
further context is well understood to mean 8 bits.

> global: The form/terminology Q<n>  (e.g., Q13, Q15, Q16) ought to be
> explained.

This was already defined in the section on notation:
   The notation "Q<n>", where n
   is an integer, denotes the number of binary digits to the right of
   the decimal point in a fixed-point number. 

> s1: Expand CELP

Done.
 
> s1.1.6: Need to define floor().

Done. Also defined abs(), ceil(), and round().

> s2: ? Expand SILK

SILK is not an acronym.

> s2: Reference for Vorbis.

Linked to http://xiph.org/vorbis/

> s2.1.8: Expand AAC (and MP3).

Expanded
MP3: MPEG 1, Layer 3
AAC: Advanced Audio Coding

> s3: References for Ogg, Matroska, maybe RTP.

Done.

> s3: Fig 1, Table 2 and intervening text:  Presumably SILK only (Table 2)
> etc correspond to MODES 1-3 in Figure 1. This needs to be consistent.

Changed LP to SILK and MDCT to CELT.

> s3.2.1: Make it clear which of the octets is len[0]/len[1].  To be
> precise it might be better to say len0/len1 are the values of the two
> length octets (in whichever order you intend). The form len[0] could be
> misinterpreted as a function 'length of 0'.

Replaced len[0] and len[1] with first_byte and second_byte, respectively.

> s3.2.5: better s/figure below/Figure 5/

Fixed for all cases of "figure below".

> s3.2.5:
>> In the CBR case, the compressed length of each frame in bytes is
>>     equal to the number of remaining bytes in the packet after
>>     subtracting the (optional) padding, (N-2-P), divided by M. This
>>     number MUST be a non-negative integer multiple of M.
> 'This number' is not the  compressed length of each frame that is the
> subject of the first sentence, but the number of remaining octets - this
> needs rewording.

Fixed by defining R=N-2-P, e.g.,
   In the CBR case, let R=N-2-P be the number of bytes remaining in the
   packet after subtracting the (optional) padding.  Then the compressed
   length of each frame in bytes is equal to R/M. The value R MUST be a
   non-negative integer multiple of M. The compressed data for all M
   frames follows, each of size R/M bytes, as illustrated in Figure 6.
 
> s3.2.5:
>> The number of header bytes (TOC byte, frame
>>     count byte, padding length bytes, and frame length bytes), plus the
>>     length of the first M-1 frames themselves, plus the length of the
>>     padding MUST be no larger than N, the total size of the packet.
> Surely this is a non sequitur? This might be better phrased as 'The
> total size of a well formed packet MUST be at least...'

Note that the text mentions the "length of the first M-1 frames", so the calculation does not include the size of the last frame. That being said, we also clarified by using "signaled length" instead of "length".

> s3.3: The example diagrams ought to have figure numbers.

Fixed.

> s3.4: I am not keen on duplicating normative requirements in this way
> (double maintenance issue).  It would be better to put explicit numbered
> requirements in the sections above an reference the resulting numbers
> here.

A checklist style summary is quite useful for implementors, and worth the maintenance burden for a document that is (hopefully) going to be published once and read many times. The list intentionally does not include any RFC 2119 keywords, to avoid any conflict should there (accidentally) be room to interpret the re-statement any differently from the original statement. Numbering the requirements and referencing the numbers is still a good idea, but it should be possible to read the list without flipping back and forth to the previous sections.

> s4.1:
>> The decoder initializes rng to 128 and initializes val to
>>     127 minus the top 7 bits of the first input octet.
> How are the 'top seven bits' to be interpreted here? e.g. as the bottom
> seven bits of a 8 bit integer field? an 8 bit integer with the lowest
> bit zeroed out?

Tried for something more explicit:
   Let b0 be the first input octet (or zero if there are no octets in
   this Opus frame).  The decoder initializes rng to 128 and initializes
   val to (127 - (b0>>1)), where (b0>>1) is the top 7 bits of the first
   input octet.  It saves the remaining bit, (b0&1), for use in the
   renormalization procedure described in ...

> s4.1.1:  This is really a global point.  This section refers to
> entdec.c.  Presumably (since we haven't reached the code yet) and it is
> still compressed, there is some file structure.  I don't think this has
> been said above.  It would be good to provide a list of the file
> components (i.e., sectional structure of the code) at the start, maybe
> even  giving line number positions within the decompressed code.

In cases where it was deemed necessary (e.g. large functions), there are
indeed line numbers in references to the code. As for a list of files
we did not think it was useful because one already needs to decompress
the code to see the references.

> s4.1.1.1:
>> Then it reads the next octet of the
>>     payload and combines it with the left-over bit buffered from the
>>     previous octet to form the 8-bit value sym.  It takes the left-over
>>     bit as the high bit (bit 7) of sym, and the top 7 bits of the octet
>>     it just read as the other 7 bits of sym.
> This is not well phrased.  Better
>       Then it reads the next octet of the payload [packet? payload hasn't
> really been used before] and combines the left  over bit from the

"Packet" is inaccurate, as the next byte in the packet may come from a different Opus frame. Replaced with "Opus frame" instead.

> previous octet (see Section 4.1 for starting this process) as the high
> bit (bit 7)| of 'sym' and the top 7 bits of the octet as the other 7
> bits of sym, leaving the remaining bit for the next iteration.

This may be trying to do too much in a single sentence. Perhaps:
  Then it reads the next octet of the Opus frame and forms an 8-bit
  value sym, using the left-over bit buffered from the previous octet
  as the high bit and the top 7 bits of the octet just read as the
  other 7 bits of sym.  The remaining bit in the octet just read is
  buffered for use in the next iteration.  If no more input octets
  remain, it uses zero bits instead.  See
  <xref target="range-decoder-init"/> for the initialization used to
  process the first octet.

Also broke out range-decoder-init into its own section to make it easier to reference.

> s4.1.5.2:
> Should r_Q15 = rng>>  (l-16) be r_Q15 = rng>>  (lg-16)?  There doesn't
> seem to be an 'l' defined.

Fixed. Sorry; this is a leftover from changing "l" to "lg" in response to one of the AD's review comments.

> s4.2.1: Expand LTP earlier. It would also be useful to expand LPC again.

Done (both).

> s4.2.2: acronym VAD is not expanded until the beginning of s4.2.3.

Fixed.

> s4.2.7: acronym LSF needs to be expanded on first use.

Fixed.

> s4.2.7.1: Explain briefly why Table 7 has values for indices 0 to 15
> when wi0/1 are in range 0 to 14.

Added:
   Although wi0 and wi1 only have 15 possible values, Table 7 contains
   16 entries to allow interpolation between entry wi0 and (wi0 + 1)
   (and likewise for wi1).

> s4.2.7.4, para below Table 12:
>> These 6 bits are combined to form a gain index between 0 and 63.
> s/gain index/gain_index/ as this variable is used subsequently.

Used:
  These 6 bits are combined to form a value, gain_index, between 0 and
  63.
Also updated the "delta gain index" for subframes without an independent gain, below.

> s4.2.7.4: The use of log_gain seems slightly confusing when combined
> with gain_index.  One at least is presumably log scaled.  Maybe a bit
> more explanation is needed.

The gain_index happens to map directly to log_gain for subframes with an independent gain (with the exception of the clamping), but this is not true for subframes where the gain is coded relative to the previous subframe. We are open to suggestions that would make the need for this distinction clearer.

Also replaced "previous gain index" with "previous_log_gain", as it is the latter that actually matters.

> ======================================================================
>              COMMENTS ABOVE submitted as part 1 of review
> ======================================================================
> s4.2.7.2, last para:
>> In that case, if this
>>     flag is zero (indicating that there should be a side channel), then
>>     Packet Loss Concealment (PLC, see Section 4.4) SHOULD be invoked to
>>     recover a side channel signal.
> What are the consequences (or what actions need to be taken) if it is
> not invoked?

Added:
  Otherwise, the stereo image will collapse.

> s4.2.7.5, para 1:
>> These represent the interleaved zeros on the
>>     unit circle between 0 and pi (hence "normalized") in the standard
>>     decomposition of the LPC filter into a symmetric part and an anti-
>>     symmetric part (P and Q in Section 4.2.7.5.6).
> 'on the unit circle between 0 and pi' might be clearer as 'on the upper
> half of the unit circle' or 'on the half of the unit circle in the
> positive imaginary area of the complex plane'.
> 'standard decomposition'?  Needs a reference.

Reworded as:
   These represent the interleaved zeros on the upper half of the unit
   circle (between 0 and pi, hence "normalized") in the standard
   decomposition [line-spectral-pairs] of the LPC filter into a
   symmetric part and an anti-symmetric part (P and Q in Section
   4.2.7.5.6).

Added the reference [line-spectral-pairs] pointing to http://en.wikipedia.org/wiki/Line_spectral_pairs

> s4.2.7.5, para 1: A reference for the use of LSF in LPC would be useful.

The above reference serves this function as well.

> s4.2.7.5.x: There is inconsistent use of stage 1/stage 2 vs
> stage-1/stage-2.  Please be consusistent

"Stage 1" is correct when referring to the noun by itself, or as an object of a verb ("stage 1 decoding"). "Stage-1" is correct when modifying another noun ("stage-1 index"). However, we changed the titles of some of the tables around to allow them to use the modifier form more consistently.

> s4.2.7.5, para 1:
>>     Because of non-linear
>>     effects in the decoding process, an implementation SHOULD match the
>>     fixed-point arithmetic described in this section exactly.  An encoder
>>     SHOULD also use the same process.
> - Does this contradict the 'must' in s1, para 2?

No, for the reasons described above.

> - What are the consequences of ignoring the SHOULD?  How bad would they
> get?  Might it become unstable and how would one know?

They would not become unstable. However, changing the exact arithmetic may
lead to a decoder output that is not close enough to that of the 
reference decoder to pass the conformance test.

> s4.2.7.5.1, para 1: s/This indexes an element in a coarse codebook,
>     selects the PDFs for the second stage of the VQ/This indexes an
>     element in a coarse codebook that selects the PDFs for the second stage
>     of the VQ/

The text as written is correct. The index I1 is what selects the PDFs for the second stage, not the vector from the coarse codebook in Tables 23 and 24. I.e., it's saying, "This does A, B, and C."

> s4.2.7.5.3, last para: 
>> However, nothing in
>>    either the reconstruction process or the quantization process in the
>>    encoder thus far guarantees that the coefficients are monotonically
>>    increasing and separated well enough to ensure a stable filter.
> A reference that indicates why this requirement is needed would be desirable.
> (and also for s4.2.5.7.8).

Added a reference to:
P. Kabal and R. P. Ramachandran, "The Computation of Line Spectral Frequencies 
Using Chebyshev Polynomials", IEEE Trans. Acoustics, Speech, Signal Processing,
vol. 34, no. 6, pp. 1419-1426, Dec. 1986.

> s4.2.7.5.4 and Table 25: Are the values in Table 25 NDeltaMin or NDelatMin_Q15?
> The equations after Table 25 use both NDeltaMin and NDeltaMin_Q15.  Is this correct?
> In particular the first two equations deliver _Q15 values but use raw NDeltaMin.

Good catch. All uses of NDeltaMin should have been NDeltaMin_Q15.

> s4.1.1/s4.2.7.1 and other places:  The term 'exact integer division' is
> used in various places.  My understanding was that this phrase implied
> that it was known that the dividend was an exact multiple of the divisor
> by some out-of-band means.  This doesn't seem to be the case generally
> in Opus (e.g,, where both n/5 and n%5  are needed - clearly this doesn't
> anticipate n%5 == 0 every time!)  So what does 'exact integer division'
> imply?  A definition may be needed. 

The "exact" here was merely 
meant in contrast to inexact floating-point division. Removed "exact", leaving only 
"integer division" (which, like all other operators, uses C conventions, as stated in 
Notation and Conventions). Hopefully this should avoid people trying to read too much into 
the phrase.

> s4.3, last para: s/described in the figure above./described in Table 55 above./

Fixed.

> s4.3.1: 
>> The "transient" flag encoded in the bitstream has a probability of 1/8. 
> This statement appears out of the blue apparently.  Some more
> explanation of what the transient flag actually implies and why we
> should be so sure about its PDF would help.

Added a bit of context and moved the probability 1/8 to later in the text.

> s4.3.2.1: Arguably a reference is needed for the z-transform.

Reference added.

> s4.3.2.1: Avoid the equation picture splitting across page boundaries.
> in the current version it is unclear what the denominator is. (use
> needLines processing direcrive in xml2rfc).  Same applies to the
> equation below Table 57 in s4.3.4.3.

It's not quite clear how to use needLines without undesirable side-effects.
Hopefully this is something the RFC editor should be able to handle.

> 4.3.2.1, after the equations:
>> The
>>    prediction is clamped internally so that fixed point implementations
>>    with limited dynamic range do not suffer desynchronization.
> As a person with limited skills in the srt, I have no idea what
> desynchronization implies here. 

Clarified to "always remain in the same state as floating point implementations".

> 4.3.2.1, ibid:
>> We
>>    approximate the ideal probability distribution of the prediction
>>    error using a Laplace distribution with separate parameters for each
>>    frame size in intra- and inter-frame modes.
> I suspect this sentence belongs before the equation described the z-transform.
> Where are the values of the parameters for the inter-frame mode defined
> (the intra-frame ones are in the text)?

The probability model is for the difference between the energy and its
prediction. Added a reference to the table where the pdf parameters are
located in the code.

> s4.3.2.3: Paragraph on decoding band boosts:  Might be improved by using
> equations rather than the wordy descriptions used at present.
> 
> (global)s4.3.2.3, para above table 56: s/iff/if and only if/

Fixed.

> s4.3.2.3: LOG2_FRAC_TABLE is missing.

Text now says that the table is in rate.c

> s4.3.3: It would be helpful to explain either here, or at the outset of
> s4.3 overall, how the concept of energy bands and MDCT bins applies to
> the CELT part of the codec, and just how many bands and bins are used.
> Some of this is contained in s5.3.2, but the magic number 17 appears
> later in 4.3.3 which is presumably something to do with the point in the
> frequency domain that CELT takes over from LP in the hybrid mode.  It
> would make the very complex section 4.3.3 rather easier to understand
> with this extra information - I have to say I struggled!  On reflection,
> I think an example of what bits are allocated to a band and how thay rae
> subsequently used would be quite helpful - Without going to delve into
> the code I am really not clear that I understand just what bits are
> allocated and what they then encode and I have read the text quite a few
> times now.

Added an explanation of band 17 at the beginning of 4.3. There is also
some text about the number of bins per band.

> s4.3.3: Be consistent between 'tone to noise' and 'tone-to-noise'.

The text was rephrased in terms of signal-to-noise.

> s4.3.3:
>>    The band-energy normalized structure of Opus MDCT mode ensures that a
>>    constant bit allocation for the shape content of a band will result
>>    in a roughly constant tone to noise ratio, which provides for fairly
>>    consistent perceptual performance.  The effectiveness of this
>>    approach is the result of two factors: that the band energy, which is
>>    understood to be perceptually important on its own, is always
>>    preserved regardless of the shape precision, and because the constant
>>    tone-to-noise ratio implies a constant intra-band noise to masking
>>    ratio.  Intra-band masking is the strongest of the perceptual masking
>>    effects.  This structure means that the ideal allocation is more
>>    consistent from frame to frame than it is for other codecs without an
>>    equivalent structure.
> This paragraph contains a number of interesting assertions:  Is there a
> reference where one could see them justified (it may be that this is the
> result of original research in the Opus team).

The particular importance of energy preservation was substantively a discovery
of the Vorbis team during the later tuning of that codec. Vorbis encoders 
include a separate step called 'noise normalization' which attempts to restore
lost energy. In CELT this energy preservation was made implicit in the design of the
codec. 

The text here is intended to explain the motivation behind the particular
band-energy normalized structure of this part of the codec in the hopes
that a higher-level understanding would help make the component steps make
a little more sense. This is "original research", but there is now a link
to an older paper describing this research:
   [Valin2010]
              Valin, JM., Terriberry, T., Montgomery, C., and G.
              Maxwell, "A High-Quality Speech and Audio Codec With Less
              Than 10 ms delay", IEEE Trans. on Audio, Speech and
              Language Processing, Vol. 18, No. 1, pp. 58-67 2010.


> s4.3.3, paragraphs after the bullet points:  The concepts of 'shape' and
> 'shape encoding' is introcuced here without explicit definition.  Are we
> talking about the shape windowing used in FFT/MDCT here? This should be
> made clear.

The concept of shape is now discussed at the beginning of s4.3.

> s4.3.3, 5th para after bullet points: s/In the reference the maximums/In
> the reference implementation the maximums/

Fixed.

> s4.3.3, 6th para after the bullet points:  A table of bands per mode and
> number of MDCT bins  covered would be helpful here in order to  get a
> feeling for the scale of the problem.  Also the cache_caps50 table in
> the code contains the magic number 168.  Where does this come from?

The layout of the band is now included at the beginning of 4.3. Also, section
4.3.3 now includes an explanation for the size of cache_caps50 
(21 bands, 4 values of LM, mono+stereo). 

> s4.3.3, 6th para after the bullet points:
>> set LM to the shift value for the frame size (e.g. 0 for 120, 1 for
>>    240, 3 for 480),  
> Where do these frame sizes get specified? And what is the total set of
> frame sizes? The text says 'e.g.' (which incidentally should be 'e.g.,')
> implying that this is not the complete set.

The calculation of LM is now given earlier in section 4.3.3


> s4.3.3, 6th para after the bullet points: Need to define 'truncating
> integer division' to go with 'exact integer division'.

Replaced with "integer division"

> s4.3.3, 7th para after the bullet points: 
>> The band boosts are represented by a series of binary symbols which
>>    are coded with very low probability.
> How many, at least, and what values?  Are these range encoded? I don't
> see them in the table above or with a PDF specified.

The text has been clarified to say that this is entropy coded. Also, the
probabilities that correspond to 6 bit and 2 bits (1/64 and 1/4, respectively)
are given to emphasize the fact that the number of bits is directly related to
the probabilities.

> s4.3.3, 7th para after the bullet points:
>>    and every time
>>    a band is boosted the initial cost is reduced (down to a minimum of
>>    two).
> Would that be a value of two or two bits? 

Two bits (fixed in the draft).

> s4.3.3: Paragraph on decoding band boosts:  Might be improved by using
> equations rather than the wordy descriptions used at present.
> 
> (global)s4.3.3, para above table 56: s/iff/if and only if/

Fixed.

> s4.3.3, 2nd para after Table 56: 
>> For stereo frames, bits are reserved for intensity stereo and for
>>    dual stereo.  Intensity stereo requires ilog2(end-start) bits.
> The terms 'intenmsity stereo' and 'dual stereo' don't appear to have
> been defined.

Added a definition of intensity, dual, and mid-side stereo to the beginning
of section 4.3. 

> s4.3.3: LOG2_FRAC_TABLE is missing.

Text now says that the table is in rate.c

> 4.3.4.3, last para:
>>    If the decoded vector represents more than one time block, then the
>>    following process is applied separately on each time block. 
> Should this sentence come before the previous paragraph?  There  isn't
> really a 'following process' in this section and I don't think it menas
> the process in s4.3.4.4?


Indeed. Replaced "the following process" with "this spreading process".

> s4.3.4.3, last sentence: 
>> This extra rotation is applied in an interleaved manner with a stride
>>    equal to round(sqrt(N/nb_blocks))
> I think this needs some more explanation for the uninitiated.

Although "stride" is a relatively common term, we added this to the sentence:
"i.e. it is applied independently for each set of sample S_k = {stride*n + k},
n=0..N/stride-1."

> s4.3.4.4:
>> Multiple levels of splitting may be
>>    applied up to a frame size dependent limit. 
> What this limit is does not appear to be defined.

Added the limit of LM+1 splits.

> s4.3.5: The 'collapse' phenomenon is not fully defined, and it would be
> useful to mention why it happens.  Also s/min/minimum/.

Added a short description of the anti-collapse feature and fixed the
s/min/minimum/

> s4.3.6: s/Just like/Just as/

Fixed.

> s4.3.7, last para: I think 'power complementarity' requires further
> explanation or a reference.

Added reference to:
John P. Princen and Alan B. Bradley, "Analysis/synthesis filter bank design based on time domain aliasing cancellation," IEEE Trans. Acoust. Speech Sig. Proc. ASSP-34 (5), 1153-1161 (1986)

> s4.5, para 3: s/To avoid or reduces glitches during these/To avoid or
> reduce glitches during these/

Fixed.

> s4.5.1.1, para 1: s/For for SILK-only/For SILK-only/

Fixed.

> s4.5.1.4, para 2: s/redundant frame is as-is,/redundant frame as-is,/

Fixed.

> s5, figure 16: The Optional High-pass Filter box has two spurious '+'
> symbols on the vertical sides. 

Fixed.

> s5, last para:  A reference for the Auto Regressive Moving Average
> (ARMA) filter would be useful.

This is a simple issue and a reference to the entire theory would have made 
the issue more complicated. The parenthesis now states "i.e. with poles and 
zeros" to clarify this.

> s5.2.3.4.2.1, title: s/Burgs method/Burg's Method/

Fixed.

> s5.2.3.5, para 2: Expand 'R/D performance' (or probably specify it as
> abbreviation for rate-distortion in para 1).

Done.

> s5.3.5, para 1 below equation: Is E an abbreviation for 'extra'?

Oops. s/extra/E/ in the text below.

> s5.3.6: The abbreviation RD for rate-distortion is defined here (see
> comment on s5.2.3.5).

Fixed.

> s6.1: This section is perhaps a little 'triumphalist' for the reference
> implementation (this may of course be justified!.  The quality metric is
> a 'relative quality metric' and presumably if someone does a *really*
> good job of coding, it is entirely possible that the new algorithms
> might get better than 100 on the quality score (i.e., provide a better
> answer than the reference implementation).

Conformance with the specification is defined by a faithful reproduction of
the specified decoder behavior (see RFC 6569 s4.3). By specifying the
decoder, future encoders have the freedom to have improved quality with the
confidence that they know what output a conforming decoder will produce.

The tests in s6.1 are measuring the quality of the decoded signal against the 
reference decoded signal, not against the original audio, so greater than 100%
wouldn't be possible or meaningful. The test signals have been specially
prepared to thoroughly test a decoder implementation, and they sacrifice encoded
quality in order to rapidly exercise the corner cases.

> s6.2: Just wondering, but is non-standard frame size the only option
> offered by Opus Custom?  If not, probably more text is needed here.  Are
> there any major changes to the algorithms implied by the use of Opus
> Custom?

Opus-custom permits more flexibility for frame-sizes at a cost of limiting
the mode switching, requiring more dynamic memory, etc. The algorithm itself
remains exactly the same, though some things like the band count/layout change
to accommodate the different frame sizes while still approximating the same Bark
structure.

> s7.  Referencing SECGUIDE (RFC 3552) seems inappropriate since it occurs
> in such a security considerations section. Just omit it.

Done.

> s11.2: A number of references are to Wikipaedia pages.  While these were
> useful to me in refreshing or initializing my knowledge, they are not
> usually considered adequately stable for use in RFCs.  I fear you may
> have to provide more stable references.

In the cases where we use Wikipedia citations, they are intended as informative 
general references for introductory subject matter, and we are not relying on any
specific details or wording that would be affected by further revisions. While 
the alternatives are often dense academic papers that may not be well suited
to  a general codec implementing audience.


--Boundary_(ID_+C3bRGW2uyqqCN0LMd/yZQ)--

From elwynd@folly.org.uk  Wed May 16 14:26:50 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 149B821F87CD; Wed, 16 May 2012 14:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.873
X-Spam-Level: 
X-Spam-Status: No, score=0.873 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_EQ_IP_ADDR=1.119, J_CHICKENPOX_13=0.6,  RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2W0cFGKDAa6V; Wed, 16 May 2012 14:26:45 -0700 (PDT)
Received: from b.c.painless.aa.net.uk (c.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e35]) by ietfa.amsl.com (Postfix) with ESMTP id D109721F8799; Wed, 16 May 2012 14:26:44 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[81.187.254.250]) by c.painless.aaisp.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1SUlk2-0005BY-54; Wed, 16 May 2012 22:26:42 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: Jean-Marc Valin <jmvalin@jmvalin.ca>
In-Reply-To: <4FB2F5D0.7070701@jmvalin.ca>
References: <1337001184.23527.1544.camel@mightyatom.folly.org.uk> <4FB2F5D0.7070701@jmvalin.ca>
Content-Type: text/plain
Organization: Folly Consulting
Date: Wed, 16 May 2012 22:26:40 +0100
Message-Id: <1337203600.31554.2213.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, "codec@ietf.org" <codec@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-codec-opus.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-codec-opus-12.txt (completed)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 21:26:50 -0000

Hi, Jean-Marc.

... and thanks for the super-quick response!  You have been quite busy.

I have had a look through the new draft and I think the additions help
considerably with comprehension for the naive (and to give new
implementers a way in.)

I'll leave you to negotiate with the RFC Editor over the Wikipaedia
references.  To quote the RFC Style guide
http://www.rfc-editor.org/rfc-style-guide/rfc-style
Section 4.8, item (x) References, last section:
> URLs and DNS names in RFCs
> 
>       The use of URLs in RFCs is discouraged, because many URLs are not
>       stable references.  Exceptions may be made for normative
>       references in those cases where the URL is demonstrably the most
>       stable reference available.  References to long-lived files on
>       ietf.org and rfc-editor.org are generally acceptable.
They are certainly convenient *as long as they remain in place and
aren't corrupted*.

I found a couple of trivial editorial nits in the changes:
s4.3.3 (in the added text):
> The CELT layer, however, can adapt over a very wide range of rates,
> and thus has a large number of codebooks sizes
s/codebooks/codebook/

s4.3.3, para after Table 57: s?the maximums in bit/sample are
precomputed?the maximums in bits/sample are precomputed?

Also suggest:
s4.3: Add reference for Bark scale: Zwicker, E. (1961), "Subdivision of
the audible frequency range into critical bands," The Journal of the
Acoustical Society of America, 33, Feb., 1961.

A few responses in line below (agreed pieces elided): 

Regards,
Elwyn  Davies
====================================================================================

On Tue, 2012-05-15 at 20:33 -0400, Jean-Marc Valin wrote:
> Hi Elwyn,
> 
> Thanks for the very thorough review. We've addressed your issues and
> submitted draft version -13. See our response to each of the issues you
> raised (aggregated from all the authors) in the attached document.

Thanks very much to all the authors.
> 
> Cheers,
> 
> 	Jean-Marc
> 


> Elwyn Davies wrote:
> > Major issues: 
> > Can we accept the code as normative?  If not how do we proceed?
> 
> The issue with code being normative was specifically addressed in 
> the guidelines document for this WG (RFC 6569).
> 
Yes.  I failed to read this although Robert Sparks did point out to me
that the code was normative - but he didn't think he said this was
agreed in advance (or maybe I didn't understand what he was saying).

To be honest I would like to have had the time to tie the text to the
code but realistically that is several weeks or even months work to do
it properly - without that I feel that I have only done half a job. I
may decide that it interests me enough to have a superficial go next
week but no promises!

> 
> > Minor issues:
> > Contrast between decoder descriptions of LP part and CELT part:  The
> > SILK descriptions go into gory detail on the values used in lots of
> > tables, etc., whereas the CELT part has a very limited treatment of
> the
> > numeric values used (assuming reliance on finding the values in the
> > reference implementation, either explictly or implicitly).  There
> are
> > things to be said for both techniques.  I was wondering (while
> reading
> > the SILK description) if the authors have any means of automatically
> > generating the tables from the code in the SILK part (or vice versa)
> to
> > avoid double maintenance. On the other hand, there are pieces of the
> > CELT decoder description (especially in s4.3.3 where knowing numbers
> of
> > bands, etc.) where some actual numbers would help comprehension.
> > 
> 
> We have made many changes to section 4.3 (and 4.3.3 specifically) to
> address
> the specific issues below. As for the tables, they are not generated
> automatically.

I think this is addressed satisfactorily now.  There is still some
difference but it is much reduced and not so glaring now. The addition
of the band tables really helps.

> 
> 
> > s2 (and more generally):  The splitting of the signal in the
> frequency
> > domain into signal (components?) below and above 8kHz presumably
> > requires that the signal is subjected to a Discrete Fourier
> Transform to
> > allow the signal to be split.  I think sometging is needed in s2 to
> > explain how this is managed (or if I don't understand, to explain
> why it
> > isn't necessary).
> 
> No DFT is used. The lower band is obtained through resampling (which
> is already described) and the higher band is obtained by not coding
> the lower band with CELT (the text says that CELT starts at band 17 in
> hybrid mode). The explanation was reworded to make this as clear as
> possible at this point in the text.

[I thought I had reworded this comment in the 2nd version to talk about
MDCT but no matter]. 
Yes, para 5 of s2 does say that the bands are discarded.  I think it
would useful to have a concrete statement in the new text added to s4.3
that bands 0 to 16 are discarded in hybrid mode (thereby making the 17
in the band boost section more obvious) [There is a comment below that
you have added some text about band 17 in section 4.3 but I can't see
it].


> 
> > s4.2.5, para 3:
> >>     When switching from 20 ms to 10 ms, the 10 ms
> >>     20 ms Opus frame, potentially leaving a hole that needs to be
> >>     concealed from even a single packet loss.
> > How?
> 
> As explained in the LBRR text, a 10 ms frame will only contain 10 ms
> LBRR data even if the previous frame was 20 ms, so there's 10 ms
> "missing".
Indeed - that there would be a hole was clear.  The 'How' referred to
how would it be concealed.  Having read further by now this may be down
to Packet Loss Concealment - so maybe all it needs is a foward ref to
s4.4. 
> 
> > s4.3:
> > As a complete newcomer to CELT, I would have appreciated a more high
> > level understanding of what CELT is doing at this point.  I  tried
> > reading s4.3 without any additional input and found it very hard
> going.
> > Eventually I gave up and went looking for some additional input.
> This
> > presentation seems to have a useful view 
> > http://www.ietf.org/proceedings/79/slides/codec-2.pdf
> > I think that it would be extremely helpful to have a description
> similar
> > to this at this point in the document, even though there is some
> > material in section 5.3 which could also be forward referenced.
> Still
> > the material in s5.3 does not start from the basic principles that
> CELT
> > is using, and since these are essentially novel, it would be very
> good
> > to give prospective implementers/users an understanding of what is
> going
> > on.  Incidentally, I found the above IETF presentation more useful
> than
> > http://www.celt-codec.org/presentations/misc/lca-celt.pdf
> > Note that the SILK part seems rather less opaque.  It would also be
> > useful to indicate numerically how many bands are involved and what
> the
> > number of MDCT bins are in the various bands. 
> 
> The intro of section 4.3 has been expanded with general information
> about CELT
> similar to what the codec-2.pdf slides from 79 included. 
> 
I think this is an excellent improvement.
> 
> > Nits/editorial comments:
> > 
> > global: bytes ->  octets
> 
> We believe that in the field of audio codecs, the mention of "byte"
> without
> further context is well understood to mean 8 bits.

True. But this is a matter of IETF style.  The style is to use octets
where we mean 8 bit bytes. I think you now have a mixture!

> 
> > global: The form/terminology Q<n>  (e.g., Q13, Q15, Q16) ought to be
> > explained.
> 
> This was already defined in the section on notation:
>    The notation "Q<n>", where n
>    is an integer, denotes the number of binary digits to the right of
>    the decimal point in a fixed-point number.
Sorry - I missed that.
> 
> > s3.4: I am not keen on duplicating normative requirements in this
> way
> > (double maintenance issue).  It would be better to put explicit
> numbered
> > requirements in the sections above an reference the resulting
> numbers
> > here.
> 
> A checklist style summary is quite useful for implementors, and worth
> the maintenance burden for a document that is (hopefully) going to be
> published once and read many times. The list intentionally does not
> include any RFC 2119 keywords, to avoid any conflict should there
> (accidentally) be room to interpret the re-statement any differently
> from the original statement. Numbering the requirements and
> referencing the numbers is still a good idea, but it should be
> possible to read the list without flipping back and forth to the
> previous sections.

Good solution!

> 
> > s4.1.1:  This is really a global point.  This section refers to
> > entdec.c.  Presumably (since we haven't reached the code yet) and it
> is
> > still compressed, there is some file structure.  I don't think this
> has
> > been said above.  It would be good to provide a list of the file
> > components (i.e., sectional structure of the code) at the start,
> maybe
> > even  giving line number positions within the decompressed code.
> 
> In cases where it was deemed necessary (e.g. large functions), there
> are
> indeed line numbers in references to the code. As for a list of files
> we did not think it was useful because one already needs to decompress
> the code to see the references.

OK. We'll have to live with this situation.

Having looked at the code, I think it is a considerable pity that it
isn't Doxygen commented (or some such) throughout so that the whole
system can be viewed as a Doxygen tree. I can smell roasted programmer
from here... :-)
> 
> > s4.2.7.5.1, para 1: s/This indexes an element in a coarse codebook,
> >     selects the PDFs for the second stage of the VQ/This indexes an
> >     element in a coarse codebook that selects the PDFs for the
> second stage
> >     of the VQ/
> 
> The text as written is correct. The index I1 is what selects the PDFs
> for the second stage, not the vector from the coarse codebook in
> Tables 23 and 24. I.e., it's saying, "This does A, B, and C."

OK.  I think it might be clearer if the three things were separated out
as a list.  Now you point it out I can read it correctly but it
triggered minor confusion - worth turning the three things into bullet
points.

NEW:  s4.3: Add reference for Bark scale: Zwicker, E. (1961),
"Subdivision of the audible frequency range into critical bands," The
Journal of the Acoustical Society of America, 33, Feb., 1961.

Generally the new intro to s4.3 helps *a lot*.
> > s4.3.2.1: Avoid the equation picture splitting across page
> boundaries.
> > in the current version it is unclear what the denominator is. (use
> > needLines processing direcrive in xml2rfc).  Same applies to the
> > equation below Table 57 in s4.3.4.3.
> 
> It's not quite clear how to use needLines without undesirable
> side-effects.
> Hopefully this is something the RFC editor should be able to handle.
Indeed.. but I don't know what undesirable side effects there are?
AFAIK (and in my own usage) it just ensures there are n lines available
on the current page at some point in the text and forces a page throw if
not.
> 
> 
> > s4.3.3: (was specified as s 4.3.2.3 whcj was wrong) Paragraph on
> decoding band boosts:  Might be improved by using
> > equations rather than the wordy descriptions used at present.

Any thoughts on this one
> > 
> > (global)s4.3.2.3, para above table 56: s/iff/if and only if/
> 
> Fixed.
> 
> 
> > s4.3.3: <<snip>>.
> 
> Added an explanation of band 17 

I don't think this happened.

> 
> 
> > s6.1: This section is perhaps a little 'triumphalist' for the
> reference
> > implementation (this may of course be justified!.  The quality
> metric is
> > a 'relative quality metric' and presumably if someone does a
> *really*
> > good job of coding, it is entirely possible that the new algorithms
> > might get better than 100 on the quality score (i.e., provide a
> better
> > answer than the reference implementation).
> 
> Conformance with the specification is defined by a faithful
> reproduction of
> the specified decoder behavior (see RFC 6569 s4.3). By specifying the
> decoder, future encoders have the freedom to have improved quality
> with the
> confidence that they know what output a conforming decoder will
> produce.
> 
> The tests in s6.1 are measuring the quality of the decoded signal
> against the 
> reference decoded signal, not against the original audio, so greater
> than 100%
> wouldn't be possible or meaningful. The test signals have been
> specially
> prepared to thoroughly test a decoder implementation, and they
> sacrifice encoded
> quality in order to rapidly exercise the corner cases.
> 
You might want to add this comment to the text.

As regards the 100 limit, I was sort of assuming that the quality figure
was derived from improving on the 48dB SNR figure.  Probably a
misreading.  AS a matter of interest, would one be able to tell from the
tests that a putative new implementation really was 'better' in some
sense? Or is this now almost a subjective matter that can only be
determined by extensive listening tests?  I got the impression we may be
converging on the diminishing returns point.

/Elwyn

> 



From jmvalin@jmvalin.ca  Thu May 17 09:49:14 2012
Return-Path: <jmvalin@jmvalin.ca>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C31921F86A6; Thu, 17 May 2012 09:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uM1zOyNLW1da; Thu, 17 May 2012 09:49:13 -0700 (PDT)
Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by ietfa.amsl.com (Postfix) with ESMTP id 3181621F866B; Thu, 17 May 2012 09:49:13 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_9fGhe3E5xtAslVrakW0puQ)"
Received: from [192.168.1.14] ([96.21.20.94]) by VL-VM-MR003.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0M4600ALWEQ0NZA0@VL-VM-MR003.ip.videotron.ca>; Thu, 17 May 2012 12:49:12 -0400 (EDT)
Message-id: <4FB52BFE.4070606@jmvalin.ca>
Date: Thu, 17 May 2012 12:49:02 -0400
From: Jean-Marc Valin <jmvalin@jmvalin.ca>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
To: Elwyn Davies <elwynd@folly.org.uk>
References: <1337001184.23527.1544.camel@mightyatom.folly.org.uk> <4FB2F5D0.7070701@jmvalin.ca> <1337203600.31554.2213.camel@mightyatom.folly.org.uk>
In-reply-to: <1337203600.31554.2213.camel@mightyatom.folly.org.uk>
X-Enigmail-Version: 1.4.1
Cc: General Area Review Team <gen-art@ietf.org>, "codec@ietf.org" <codec@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-codec-opus.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-codec-opus-12.txt (completed)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 16:49:14 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_9fGhe3E5xtAslVrakW0puQ)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Hi Elwyn,

We're submitted a -14 draft to address your comments. Again, see the
response to each of these issues in the attached document.

Thanks again,

	Jean-Marc


On 12-05-16 05:26 PM, Elwyn Davies wrote:
> Hi, Jean-Marc.
> 
> ... and thanks for the super-quick response!  You have been quite busy.
> 
> I have had a look through the new draft and I think the additions help
> considerably with comprehension for the naive (and to give new
> implementers a way in.)


--Boundary_(ID_9fGhe3E5xtAslVrakW0puQ)
Content-type: text/plain; CHARSET=US-ASCII; name=genart2.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=genart2.txt

On 12-05-16 05:26 PM, Elwyn Davies wrote:
>> The CELT layer, however, can adapt over a very wide range of rates,
>> and thus has a large number of codebooks sizes
> s/codebooks/codebook/

Fixed.

> s4.3.3, para after Table 57: s?the maximums in bit/sample are
> precomputed?the maximums in bits/sample are precomputed?

Fixed.

> Also suggest:
> s4.3: Add reference for Bark scale: Zwicker, E. (1961), "Subdivision of
> the audible frequency range into critical bands," The Journal of the
> Acoustical Society of America, 33, Feb., 1961.

Done.

>> No DFT is used. The lower band is obtained through resampling (which
>> is already described) and the higher band is obtained by not coding
>> the lower band with CELT (the text says that CELT starts at band 17 in
>> hybrid mode). The explanation was reworded to make this as clear as
>> possible at this point in the text.
> 
> [I thought I had reworded this comment in the 2nd version to talk about
> MDCT but no matter]. 
> Yes, para 5 of s2 does say that the bands are discarded.  I think it
> would useful to have a concrete statement in the new text added to s4.3
> that bands 0 to 16 are discarded in hybrid mode (thereby making the 17
> in the band boost section more obvious) [There is a comment below that
> you have added some text about band 17 in section 4.3 but I can't see
> it].

Sorry, we started working on the revision as soon as you sent the first part
of the review, and then we just copied the new parts (didn't notice some of
the review changed).

Also, the reason you didn't see the new explanations about band 17 in s4.3 is that we moved them to s2 para 5, to help make the explanation of the signal splitting clearer, but forgot to update the response to indicate that (sorry about that). However, it probably does make sense to explain it in both places, so the sentence,
  "In hybrid mode, the first 17 bands (up to 8 kHz) are not coded."
has been added to s4.3 as well.

>> As explained in the LBRR text, a 10 ms frame will only contain 10 ms
>> LBRR data even if the previous frame was 20 ms, so there's 10 ms
>> "missing".
> Indeed - that there would be a hole was clear.  The 'How' referred to
> how would it be concealed.  Having read further by now this may be down
> to Packet Loss Concealment - so maybe all it needs is a foward ref to
> s4.4. 

Reference added.

>> We believe that in the field of audio codecs, the mention of "byte"
>> without
>> further context is well understood to mean 8 bits.
> 
> True. But this is a matter of IETF style.  The style is to use octets
> where we mean 8 bit bytes. I think you now have a mixture!
> 
>>

Indeed, there's a bit of inconsistency here. Considering Cullen's email,
the document now uses "byte" consistently.

>>> s4.2.7.5.1, para 1: s/This indexes an element in a coarse codebook,
>>>     selects the PDFs for the second stage of the VQ/This indexes an
>>>     element in a coarse codebook that selects the PDFs for the
>> second stage
>>>     of the VQ/
>>
>> The text as written is correct. The index I1 is what selects the PDFs
>> for the second stage, not the vector from the coarse codebook in
>> Tables 23 and 24. I.e., it's saying, "This does A, B, and C."
> 
> OK.  I think it might be clearer if the three things were separated out
> as a list.  Now you point it out I can read it correctly but it
> triggered minor confusion - worth turning the three things into bullet
> points.

This is not a bad idea. I agree it helps make things clearer. Done.

> NEW:  s4.3: Add reference for Bark scale: Zwicker, E. (1961),
> "Subdivision of the audible frequency range into critical bands," The
> Journal of the Acoustical Society of America, 33, Feb., 1961.

Done (as stated above).

>>> s4.3.3: (was specified as s 4.3.2.3 whcj was wrong) Paragraph on
>> decoding band boosts:  Might be improved by using
>>> equations rather than the wordy descriptions used at present.
> 
> Any thoughts on this one

Oops, that one slipped through. While most of the text is actually
describing an algorithm rather than an equation, it was possible to simplify
the part about the quanta with an equation. The text now reads:
"For each band from the coding start (0 normally, but 17 in Hybrid mode)
to the coding end (which changes depending on the signaled bandwidth), the boost quanta
in units of 1/8 bit is calculated as: quanta = min(8*N, max(48, N))."

>>> s4.3.3: <<snip>>.
>>
>> Added an explanation of band 17 
> 
> I don't think this happened.

See above -- operator error. It's fixed now.

>> The tests in s6.1 are measuring the quality of the decoded signal
>> against the 
>> reference decoded signal, not against the original audio, so greater
>> than 100%
>> wouldn't be possible or meaningful. The test signals have been
>> specially
>> prepared to thoroughly test a decoder implementation, and they
>> sacrifice encoded
>> quality in order to rapidly exercise the corner cases.
>>
> You might want to add this comment to the text.

Added the comment about 100 being the max. As for the other part, the test
vector section already states that:
"These test vectors were created specifically to exercise all aspects of the
decoder and therefore the audio quality of the decoded output is
significantly lower than what Opus can achieve in normal operation."

> As regards the 100 limit, I was sort of assuming that the quality figure
> was derived from improving on the 48dB SNR figure.  Probably a
> misreading.  AS a matter of interest, would one be able to tell from the
> tests that a putative new implementation really was 'better' in some
> sense? Or is this now almost a subjective matter that can only be
> determined by extensive listening tests?  I got the impression we may be
> converging on the diminishing returns point.

You can't have a "better" decoder because the reference implementation is
*by definition* the best decoder possible. From there, the encoder can
be improved to optimize the quality of a bitstream to be decoded by that
reference decoder. The encoder included with the reference is mature enough
that improvements usually need to be validated with human listening tests;
objective quality measurements aren't quite reliable enough alone to distinguish
'different' from 'better', unless the change is very significant.



--Boundary_(ID_9fGhe3E5xtAslVrakW0puQ)--

From elwynd@folly.org.uk  Thu May 17 11:56:16 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E05D21F8749; Thu, 17 May 2012 11:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.423
X-Spam-Level: 
X-Spam-Status: No, score=0.423 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,  HELO_EQ_IP_ADDR=1.119, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SZOnUTjBiws8; Thu, 17 May 2012 11:56:15 -0700 (PDT)
Received: from b.c.painless.aa.net.uk (c.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e35]) by ietfa.amsl.com (Postfix) with ESMTP id 984BD21F86A6; Thu, 17 May 2012 11:56:15 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[81.187.254.250]) by c.painless.aaisp.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1SV5rz-0004j9-L1; Thu, 17 May 2012 19:56:15 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: Jean-Marc Valin <jmvalin@jmvalin.ca>
In-Reply-To: <4FB52BFE.4070606@jmvalin.ca>
References: <1337001184.23527.1544.camel@mightyatom.folly.org.uk> <4FB2F5D0.7070701@jmvalin.ca> <1337203600.31554.2213.camel@mightyatom.folly.org.uk> <4FB52BFE.4070606@jmvalin.ca>
Content-Type: text/plain
Organization: Folly Consulting
Date: Thu, 17 May 2012 19:56:13 +0100
Message-Id: <1337280973.31554.4834.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, "codec@ietf.org" <codec@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-codec-opus.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-codec-opus-12.txt (completed)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 18:56:16 -0000

Hi, Jean-Marc and co-authors

On Thu, 2012-05-17 at 12:49 -0400, Jean-Marc Valin wrote:
> Hi Elwyn,
> 
> We're submitted a -14 draft to address your comments. Again, see the
> response to each of these issues in the attached document.

I think we are done.  Thanks once again for the rapid response.

Regards,
Elwyn

PS
I still prefer octets.

/E
> 
> Thanks again,
> 
> 	Jean-Marc
> 
> 
> On 12-05-16 05:26 PM, Elwyn Davies wrote:
> > Hi, Jean-Marc.
> > 
> > ... and thanks for the super-quick response!  You have been quite busy.
> > 
> > I have had a look through the new draft and I think the additions help
> > considerably with comprehension for the naive (and to give new
> > implementers a way in.)
> 


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

Hi all,

The following reviewers have assignments:

Reviewer                 LC end     Draft

Kathleen Moriarty      T 2012-05-25 draft-ietf-dccp-udpencap-10

Mary Barnes              2012-05-29 draft-ietf-mpls-ldp-gtsm-06

Martin Thomson           2012-05-30 draft-ietf-tcpm-tcpmss-04

Miguel Garcia           R2012-05-31 draft-ietf-dane-protocol-21

Peter McCann             2012-06-11 
draft-camarillo-rai-media-policy-dataset-01

Peter Yee              T 2012-05-30 draft-ietf-mile-template-04

Richard Barnes           2012-05-31 draft-ietf-dnsext-dnssec-bis-updates-18

Roni Even               R2012-05-28 draft-melnikov-smtp-priority-13

Suresh Krishnan        T 2012-05-30 draft-ietf-mile-iodef-xmlreg-01


T - on an upcoming Telechat (June 6)
R - returning (that is, a second last call)


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

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From mahoney@nostrum.com  Thu May 17 15:46:24 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81AC221F87A8 for <gen-art@ietfa.amsl.com>; Thu, 17 May 2012 15:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xYgU6ALW9Bb4 for <gen-art@ietfa.amsl.com>; Thu, 17 May 2012 15:46:24 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id CCE5D21F8772 for <gen-art@ietf.org>; Thu, 17 May 2012 15:46:23 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-71-170-40-250.dllstx.fios.verizon.net [71.170.40.250]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q4HMkNYD083862 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 17 May 2012 17:46:23 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FB57FBF.5050006@nostrum.com>
Date: Thu, 17 May 2012 17:46:23 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 71.170.40.250 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-05-24 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 22:46:24 -0000

Hi all,

The following reviewers have assignments:

Reviewer                 LC end     Draft

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

Ben Campbell           2012-05-14  draft-ietf-ccamp-assoc-info-03 **

Christer Holmberg      2012-05-21  
draft-ietf-pkix-cmp-transport-protocols-19 *

Joel Halpern           2012-04-16  draft-ietf-manet-nhdp-mib-13 *

Miguel Garcia          2012-03-21  draft-ietf-pwe3-redundancy-bit-07 *

Martin Thomson         2012-03-21  draft-ietf-pwe3-redundancy-08 *

Roni Even              2012-04-17  
draft-claise-export-application-info-in-ipfix-07 *

Vijay Gurbani          2012-04-03  draft-snell-atompub-tombstones-15 *

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

* Earlier draft reviewed
** Already reviewed


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

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

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

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

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From elwynd@folly.org.uk  Thu May 17 16:09:51 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3C8121F87CB for <gen-art@ietfa.amsl.com>; Thu, 17 May 2012 16:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.373
X-Spam-Level: 
X-Spam-Status: No, score=0.373 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,  HELO_EQ_IP_ADDR=1.119, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y7dtTY19PlLH for <gen-art@ietfa.amsl.com>; Thu, 17 May 2012 16:09:45 -0700 (PDT)
Received: from b.c.painless.aa.net.uk (c.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e35]) by ietfa.amsl.com (Postfix) with ESMTP id 4660B21F87A8 for <gen-art@ietf.org>; Thu, 17 May 2012 16:09:45 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[81.187.254.250]) by c.painless.aaisp.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1SV9pI-0005sL-GE for gen-art@ietf.org; Fri, 18 May 2012 00:09:44 +0100
From: Elwyn Davies <elwynd@folly.org.uk>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Organization: Folly Consulting
Date: Fri, 18 May 2012 00:09:42 +0100
Message-Id: <1337296182.31554.5362.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Subject: [Gen-art] Gen-art last call review of draft-ietf-codec-opus-12.txt (completed)
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 23:09:51 -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-codec-opus-12.txt
Reviewer:  Elwyn Davies
Review Date:  14 May 2012 (completed)
IETF LC End Date: 10 May 2012
IESG Telechat date: (if known) -

Summary: 
Before offering some views on the document, let me say that this piece
of work seems to be a tour de force on behalf of its developers.  It is
certainly one of the (if not the) most technically complex pieces of
work that has been presented to the IETF, and is far more mathematically
complex and rigorous than our usual run of standards.  It is also
perhaps a vindication of the rough concensus and running code
philosophy. So congratulations to the authors and the companies that
have supported this work.  But back to the review....

I came to this review with a very outdated view of what goes on inside
codecs, so it was rather a shock to the system.  Taking that into
account, I think that some additional high level, up front description
of the two parts (SILK and CELT) and the range encoding system would
make it easier for future (naive) readers and potential implementers to
understand what is going on.  For example, after struggling with the
description of CELT in the decoder (s4.3) I found that going off and
reading the slides on CELT presented at IETF 79 helped considerably.
Such additions might also help future dissemination of the technique by
giving potential users a quick overview.  It would also make it easier
to justify the decision to postpone the high level (and highly
mathematical/technical) view to section 5 after the detailed description
of the decoder.

I also found that the descriptions of the SILK and CELT decoders
appeared to be written with a different perspective (see detailed
comments) doubtless by different authors.  This is not ideal and,
despite the expected further increase in page count, some additional
text in s4.3 seems desirable.

By far the most difficult to parse section is 4.3.3 talking about bit
allocation in CELT.  Despite considerable study, I didn't feel I had
really got to grips with how this worked.  An example might help.

Finally, the most contentious aspect of this document is the requirement
to treat the code as normative.  There are just over 30,000 physical
lines of code and I haven't checked them hardly at all.  Slocount
reckons this represents 7.14 man years of effort.  As with the document,
there is a discrepancy between CELT and SILK with the latter code being
more heavily commented, especially as regards routine parameters.  A
proper validation of the claim that the code implements the description
would take several weeks of time: I guess that we have to take the
document shepherd's assurances on this.  One issue is that both code and
document are pretty much saturated with what we used to call 'magic
numbers'.  Although these are explained in the document, it does not
appear that this is always the case in the code.  I would also be
happier if the code contained Doxygen (or similar) dcoumentation
statements for all routines (rather than just the API).

So overall, the work is something that ought to be standardized but the
document needs further work - not quite ready for the IESG. 

Major issues: 
Can we accept the code as normative?  If not how do we proceed?

Minor issues:
Contrast between decoder descriptions of LP part and CELT part:  The
SILK descriptions go into gory detail on the values used in lots of
tables, etc., whereas the CELT part has a very limited treatment of the
numeric values used (assuming reliance on finding the values in the
reference implementation, either explictly or implicitly).  There are
things to be said for both techniques.  I was wondering (while reading
the SILK description) if the authors have any means of automatically
generating the tables from the code in the SILK part (or vice versa) to
avoid double maintenance. On the other hand, there are pieces of the
CELT decoder description (especially in s4.3.3 where knowing numbers of
bands, etc.) where some actual numbers would help comprehension.

s2 (and more generally):  The splitting of the signal in the frequency
domain into signal (components?) below and above 8kHz in the hybrid case
presumably requires that the output of the CELT encoder is windowed so
that only one of encoders gnerates output below 8kHZ.  I think something
is needed in s2 to explain how this is managed (presumably to do with
energy bands?).  I didn't find anything in s5 about what has to be done
for the encoder when running in hybrid mode which surprised me somewhat.

s4.1: Despite having found a copy of the range coding paper and tried to
read it, I found the description of range coding opaque (there are some
more words later in s5 but this is a bit late for understanding the
decoder).  Given that this is (I think) fairly novel, some additional
less opaque description could be very helpful to people trying to
understand what is going on. In particular knowledge of how entropy
coding works is pretty much a prerequisite. 

s4.2.5, para 3:
>    When switching from 20 ms to 10 ms, the 10 ms
>    20 ms Opus frame, potentially leaving a hole that needs to be
>    concealed from even a single packet loss.
How?

s4.2.5, para 4: 
> In order to properly produce LBRR frames under all conditions, an
>    encoder might need to buffer up to 60 ms of audio and re-encode it
>    during these transitions.  However, the reference implementation opts
>    to disable LBRR frames at the transition point for simplicity.
> 
Should this be phrased in RFC 2119 requiremenmts language?  The first
part sounds like a SHOULD with the second part being the get out , but
its not entirely clear what the consequences are other then simplicity.


======================================================================
            MINOR ISSUES ABOVE submitted as part 1 of review
======================================================================
general/s11.2:  Several references [Hadamard], [Viterbi}, etc., are to
Wikipaedia pages.  Whilst these are convenient (and only illustrative)
they are not guaranteed to be very stable.  Better (i.e., more stable)
references are desirable.

s1, para 2:
>    The decoder contains a great deal of integer and fixed-point
>    arithmetic which must be performed exactly, including all rounding
>    considerations,...
Is this a MUST?  There are instances in the text which might contradict
this (e.g., para 1 of s4.2.7.5 which has (capitalized) SHOULDs).

s4.3:
As a complete newcomer to CELT, I would have appreciated a more high
level understanding of what CELT is doing at this point.  I  tried
reading s4.3 without any additional input and found it very hard going.
Eventually I gave up and went looking for some additional input.  This
presentation seems to have a useful view 
http://www.ietf.org/proceedings/79/slides/codec-2.pdf

I think that it would be extremely helpful to have a description similar
to this at this point in the document, even though there is some
material in section 5.3 which could also be forward referenced.  Still
the material in s5.3 does not start from the basic principles that CELT
is using, and since these are essentially novel, it would be very good
to give prospective implementers/users an understanding of what is going
on.  Incidentally, I found the above IETF presentation more useful than
http://www.celt-codec.org/presentations/misc/lca-celt.pdf
Note that the SILK part seems rather less opaque.  It would also be
useful to indicate numerically how many bands are involved and what the
number of MDCT bins are in the various bands. 

s4.3, last para: Can the 'out of range error' occur in the LP decoder? (if not why not?)

======================================================================

Nits/editorial comments: 

global: bytes -> octets
global: The form/terminology Q<n> (e.g., Q13, Q15, Q16) ought to be
explained.

s1: Expand CELP

s1.1.6: Need to define floor().

s2: ? Expand SILK

s2: Reference for Vorbis.

s2.1.8: Expand AAC (and MP3).

s3: References for Ogg, Matroska, maybe RTP.

s3: Fig 1, Table 2 and intervening text:  Presumably SILK only (Table 2)
etc correspond to MODES 1-3 in Figure 1. This needs to be consistent.

s3.2.1: Make it clear which of the octets is len[0]/len[1].  To be
precise it might be better to say len0/len1 are the values of the two
length octets (in whichever order you intend). The form len[0] could be
misinterpreted as a function 'length of 0'.

s3.2.5: better s/figure below/Figure 5/

s3.2.5:
> In the CBR case, the compressed length of each frame in bytes is
>    equal to the number of remaining bytes in the packet after
>    subtracting the (optional) padding, (N-2-P), divided by M. This
>    number MUST be a non-negative integer multiple of M.
'This number' is not the  compressed length of each frame that is the
subject of the first sentence, but the number of remaining octets - this
needs rewording.

s3.2.5:
> The number of header bytes (TOC byte, frame
>    count byte, padding length bytes, and frame length bytes), plus the
>    length of the first M-1 frames themselves, plus the length of the
>    padding MUST be no larger than N, the total size of the packet.
Surely this is a non sequitur? This might be better phrased as 'The
total size of a well formed packet MUST be at least...' 

s3.3: The example diagrams ought to have figure numbers.

s3.4: I am not keen on duplicating normative requirements in this way
(double maintenance issue).  It would be better to put explicit numbered
requirements in the sections above an reference the resulting numbers
here. 

s4.1:
> The decoder initializes rng to 128 and initializes val to
>    127 minus the top 7 bits of the first input octet. 
How are the 'top seven bits' to be interpreted here? e.g. as the bottom
seven bits of a 8 bit integer field? an 8 bit integer with the lowest
bit zeroed out?


s4.1.1:  This is really a global point.  This section refers to
entdec.c.  Presumably (since we haven't reached the code yet) and it is
still compressed, there is some file structure.  I don't think this has
been said above.  It would be good to provide a list of the file
components (i.e., sectional structure of the code) at the start, maybe
even  giving line number positions within the decompressed code.


s4.1.1.1:
> Then it reads the next octet of the
>    payload and combines it with the left-over bit buffered from the
>    previous octet to form the 8-bit value sym.  It takes the left-over
>    bit as the high bit (bit 7) of sym, and the top 7 bits of the octet
>    it just read as the other 7 bits of sym.
This is not well phrased.  Better
     Then it reads the next octet of the payload [packet? payload hasn't
really been used before] and combines the left  over bit from the
previous octet (see Section 4.1 for starting this process) as the high
bit (bit 7)| of 'sym' and the top 7 bits of the octet as the other 7
bits of sym, leaving the remaining bit for the next iteration.  

s4.1.5.2:
Should r_Q15 = rng >> (l-16) be r_Q15 = rng >> (lg-16)?  There doesn't
seem to be an 'l' defined.

s4.2.1: Expand LTP earlier. It would also be useful to expand LPC again.
 
s4.2.2: acronym VAD is not expanded until the beginning of s4.2.3.

s4.2.7: acronym LSF needs to be expanded on first use.

s4.2.7.1: Explain briefly why Table 7 has values for indices 0 to 15
when wi0/1 are in range 0 to 14.

s4.2.7.4, para below Table 12:
> These 6 bits are combined to form a gain index between 0 and 63.

s/gain index/gain_index/ as this variable is used subsequently.

s4.2.7.4: The use of log_gain seems slightly confusing when combined
with gain_index.  One at least is presumably log scaled.  Maybe a bit
more explanation is needed.

======================================================================
            COMMENTS ABOVE submitted as part 1 of review
======================================================================
General: Define L1 and L2 (as in L1-norm, etc).

s4.2.7.2, last para:
> In that case, if this
>    flag is zero (indicating that there should be a side channel), then
>    Packet Loss Concealment (PLC, see Section 4.4) SHOULD be invoked to
>    recover a side channel signal.
What are the consequences (or what actions need to be taken) if it is
not invoked?

s4.2.7.5, para 1:
> These represent the interleaved zeros on the
>    unit circle between 0 and pi (hence "normalized") in the standard
>    decomposition of the LPC filter into a symmetric part and an anti-
>    symmetric part (P and Q in Section 4.2.7.5.6).
'on the unit circle between 0 and pi' might be clearer as 'on the upper
half of the unit circle' or 'on the half of the unit circle in the
positive imaginary area of the complex plane'.
'standard decomposition'?  Needs a reference.

s4.2.7.5, para 1: A reference for the use of LSF in LPC would be useful.

s4.2.7.5.x: There is inconsistent use of stage 1/stage 2 vs
stage-1/stage-2.  Please be consistent.

s4.2.7.5, para 1:
>    Because of non-linear
>    effects in the decoding process, an implementation SHOULD match the
>    fixed-point arithmetic described in this section exactly.  An encoder
>    SHOULD also use the same process.
- Does this contradict the 'must' in s1, para 2?
- What are the consequences of ignoring the SHOULD?  How bad would they
get?  Might it become unstable and how would one know?

s4.2.7.5.1, para 1: s/This indexes an element in a coarse codebook,
   selects the PDFs for the second stage of the VQ/This indexes an 
   element in a coarse codebook that selects the PDFs for the second stage 
   of the VQ/

s4.2.7.5.3, last para: 
> However, nothing in
>    either the reconstruction process or the quantization process in the
>    encoder thus far guarantees that the coefficients are monotonically
>    increasing and separated well enough to ensure a stable filter.
A reference that indicates why this requirement is needed would be desirable.
(and also for s4.2.5.7.8).

s4.2.7.5.4 and Table 25: Are the values in Table 25 NDeltaMin or NDelatMin_Q15?
The equations after Table 25 use both NDeltaMin and NDeltaMin_Q15.  Is this correct?
In particular the first two equations deliver _Q15 values but use raw NDeltaMin.

s4.1.1/s4.2.7.1 and other places:  The term 'exact integer division' is
used in various places.  My understanding was that this phrase implied
that it was known that the dividend was an exact multiple of the divisor
by some out-of-band means.  This doesn't seem to be the case generally
in Opus (e.g,, where both n/5 and n%5  are needed - clearly this doesn't
anticipate n%5 == 0 every time!)  So what does 'exact integer division'
imply?  A definition may be needed. 

s4.3, last para: s/described in the figure above./described in Table 55 above./

s4.3.1: 
> The "transient" flag encoded in the bitstream has a probability of 1/8. 
This statement appears out of the blue apparently.  Some more
explanation of what the transient flag actually implies and why we
should be so sure about its PDF would help.

s4.3.2.1: Arguably a reference is needed for the z-transform.

s4.3.2.1: Avoid the equation picture splitting across page boundaries.
in the current version it is unclear what the denominator is. (use
needLines processing direcrive in xml2rfc).  Same applies to the
equation below Table 57 in s4.3.4.3.

4.3.2.1, after the equations:
> The
>    prediction is clamped internally so that fixed point implementations
>    with limited dynamic range do not suffer desynchronization.
As a person with limited skills in the srt, I have no idea what
desynchronization implies here. 

4.3.2.1, ibid:
> We
>    approximate the ideal probability distribution of the prediction
>    error using a Laplace distribution with separate parameters for each
>    frame size in intra- and inter-frame modes.
I suspect this sentence belongs before the equation described the z-transform.
Where are the values of the parameters for the inter-frame mode defined
(the intra-frame ones are in the text)?

s4.3.2.3: Paragraph on decoding band boosts:  Might be improved by using
equations rather than the wordy descriptions used at present.

(global)s4.3.2.3, para above table 56: s/iff/if and only if/

s4.3.2.3: LOG2_FRAC_TABLE is missing.

s4.3.3: It would be helpful to explain either here, or at the outset of
s4.3 overall, how the concept of energy bands and MDCT bins applies to
the CELT part of the codec, and just how many bands and bins are used.
Some of this is contained in s5.3.2, but the magic number 17 appears
later in 4.3.3 which is presumably something to do with the point in the
frequency domain that CELT takes over from LP in the hybrid mode.  It
would make the very complex section 4.3.3 rather easier to understand
with this extra information - I have to say I struggled!  On reflection,
I think an example of what bits are allocated to a band and how thay rae
subsequently used would be quite helpful - Without going to delve into
the code I am really not clear that I understand just what bits are
allocated and what they then encode and I have read the text quite a few
times now.

s4.3.3: Be consistent between 'tone to noise' and 'tone-to-noise'.

s4.3.3:
>    The band-energy normalized structure of Opus MDCT mode ensures that a
>    constant bit allocation for the shape content of a band will result
>    in a roughly constant tone to noise ratio, which provides for fairly
>    consistent perceptual performance.  The effectiveness of this
>    approach is the result of two factors: that the band energy, which is
>    understood to be perceptually important on its own, is always
>    preserved regardless of the shape precision, and because the constant
>    tone-to-noise ratio implies a constant intra-band noise to masking
>    ratio.  Intra-band masking is the strongest of the perceptual masking
>    effects.  This structure means that the ideal allocation is more
>    consistent from frame to frame than it is for other codecs without an
>    equivalent structure.
This paragraph contains a number of interesting assertions:  Is there a
reference where one could see them justified (it may be that this is the
result of original research in the Opus team).
 
s4.3.3, paragraphs after the bullet points:  The concepts of 'shape' and
'shape encoding' is introcuced here without explicit definition.  Are we
talking about the shape windowing used in FFT/MDCT here? This should be
made clear.

s4.3.3, 5th para after bullet points: s/In the reference the maximums/In
the reference implementation the maximums/

s4.3.3, 6th para after the bullet points:  A table of bands per mode and
number of MDCT bins  covered would be helpful here in order to  get a
feeling for the scale of the problem.  Also the cache_caps50 table in
the code contains the magic number 168.  Where does this come from?

s4.3.3, 6th para after the bullet points:
> set LM to the shift value for the frame size (e.g. 0 for 120, 1 for
>    240, 3 for 480),  
Where do these frame sizes get specified? And what is the total set of
frame sizes? The text says 'e.g.' (which incidentally should be 'e.g.,')
implying that this is not the complete set.

s4.3.3, 6th para after the bullet points: Need to define 'truncating
integer division' to go with 'exact integer division'.

s4.3.3, 7th para after the bullet points: 
> The band boosts are represented by a series of binary symbols which
>    are coded with very low probability.
How many, at least, and what values?  Are these range encoded? I don't
see them in the table above or with a PDF specified.

s4.3.3, 7th para after the bullet points:
>    and every time
>    a band is boosted the initial cost is reduced (down to a minimum of
>    two).
Would that be a value of two or two bits? 
  
s4.3.3: Paragraph on decoding band boosts:  Might be improved by using
equations rather than the wordy descriptions used at present.

(global)s4.3.3, para above table 56: s/iff/if and only if/

s4.3.3, 2nd para after Table 56: 
> For stereo frames, bits are reserved for intensity stereo and for
>    dual stereo.  Intensity stereo requires ilog2(end-start) bits.
The terms 'intenmsity stereo' and 'dual stereo' don't appear to have
been defined.

s4.3.3: LOG2_FRAC_TABLE is missing.

4.3.4.3, last para:
>    If the decoded vector represents more than one time block, then the
>    following process is applied separately on each time block. 
Should this sentence come before the previous paragraph?  There  isn't
really a 'following process' in this section and I don't think it menas
the process in s4.3.4.4?


s4.3.4.3, last sentence: 
> This extra rotation is applied in an interleaved manner with a stride
>    equal to round(sqrt(N/nb_blocks))
I think this needs some more explanation for the uninitiated.

s4.3.4.4:
> Multiple levels of splitting may be
>    applied up to a frame size dependent limit. 
What this limit is does not appear to be defined.

s4.3.5: The 'collapse' phenomenon is not fully defined, and it would be
useful to mention why it happens.  Also s/min/minimum/.

s4.3.6: s/Just like/Just as/

s4.3.7, last para: I think 'power complementarity' requires further
explanation or a reference.

s4.5, para 3: s/To avoid or reduces glitches during these/To avoid or
reduce glitches during these/

s4.5.1.1, para 1: s/For for SILK-only/For SILK-only/

s4.5.1.4, para 2: s/redundant frame is as-is,/redundant frame as-is,/

s5, figure 16: The Optional High-pass Filter box has two spurious '+'
symbols on the vertical sides. 

s5, last para:  A reference for the Auto Regressive Moving Average
(ARMA) filter would be useful.

s5.2.3.4.2.1, title: s/Burgs method/Burg's Method/

s5.2.3.5, para 2: Expand 'R/D performance' (or probably specify it as
abbreviation for rate-distortion in para 1).

s5.3.5, para 1 below equation: Is E an abbreviation for 'extra'?

s5.3.6: The abbreviation RD for rate-distortion is defined here (see
comment on s5.2.3.5).

s6.1: This section is perhaps a little 'triumphalist' for the reference
implementation (this may of course be justified!.  The quality metric is
a 'relative quality metric' and presumably if someone does a *really*
good job of coding, it is entirely possible that the new algorithms
might get better than 100 on the quality score (i.e., provide a better
answer than the reference implementation).

s6.2: Just wondering, but is non-standard frame size the only option
offered by Opus Custom?  If not, probably more text is needed here.  Are
there any major changes to the algorithms implied by the use of Opus
Custom?

s7.  Referencing SECGUIDE (RFC 3552) seems inappropriate since it occurs
in such a security considerations section. Just omit it.

s11.2: A number of references are to Wikipaedia pages.  While these were
useful to me in refreshing or initializing my knowledge, they are not
usually considered adequately stable for use in RFCs.  I fear you may
have to provide more stable references.

Appendix A: I checked that the code extracted as inicated and was able
to be compiled under Ubuntu 10.04 LTS.









  




From jmh@joelhalpern.com  Thu May 17 16:22:58 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C532B21F8771 for <gen-art@ietfa.amsl.com>; Thu, 17 May 2012 16:22:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.322
X-Spam-Level: 
X-Spam-Status: No, score=-102.322 tagged_above=-999 required=5 tests=[AWL=-0.057, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ui2ItFo5SlFL for <gen-art@ietfa.amsl.com>; Thu, 17 May 2012 16:22:55 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 33BC921F86EB for <gen-art@ietf.org>; Thu, 17 May 2012 16:22:55 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 279DF5581CC for <gen-art@ietf.org>; Thu, 17 May 2012 16:22:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id DFD3F1C04AA; Thu, 17 May 2012 16:22:54 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.110] (pool-71-161-50-234.clppva.btas.verizon.net [71.161.50.234]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id B80BA1C04A9; Thu, 17 May 2012 16:22:46 -0700 (PDT)
Message-ID: <4FB5882D.5020106@joelhalpern.com>
Date: Thu, 17 May 2012 19:22:21 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
References: <4F7E279C.3030707@nostrum.com>
In-Reply-To: <4F7E279C.3030707@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Adrian Farrel <adrian@olddog.co.uk>, sratliff@cisco.com
Subject: [Gen-art]   review:  draft-ietf-manet-nhdp-mib-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 23:22:58 -0000

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

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

Document: draft-ietf-manet-nhdp-mib-13
     Definition of Managed Objects for the
         Neighborhood Discovery Protocol
Reviewer: Joel M. Halpern
Review Date: 17-May-2012
IETF LC End Date: N/A
IESG Telechat date: 24-May-2012

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

The authors have done a thorough job of addressing my concerns.  Thank you.

PS: The datatracker still thinks the document is in WG Last Call in the 
manet WG.

From christer.holmberg@ericsson.com  Thu May 17 22:45:59 2012
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E99921F86F5 for <gen-art@ietfa.amsl.com>; Thu, 17 May 2012 22:45:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.166
X-Spam-Level: 
X-Spam-Status: No, score=-6.166 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0k74E0MHfPp for <gen-art@ietfa.amsl.com>; Thu, 17 May 2012 22:45:58 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 9C57121F86F0 for <gen-art@ietf.org>; Thu, 17 May 2012 22:45:57 -0700 (PDT)
X-AuditID: c1b4fb2d-b7bbfae000005e4b-22-4fb5e2131bda
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 0B.FA.24139.312E5BF4; Fri, 18 May 2012 07:45:55 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.64]) by esessmw0256.eemea.ericsson.se ([153.88.115.96]) with mapi; Fri, 18 May 2012 07:45:55 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org" <draft-ietf-pkix-cmp-transport-protocols.all@tools.ietf.org>
Date: Fri, 18 May 2012 07:45:54 +0200
Thread-Topic: [Gen-art] Genart review of draft-ietf-pkix-cmp-transport-protocols-19
Thread-Index: Ac00uO9SChkVZPK3SqabtOiREkEnNA==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C444FE409@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F2072F1E0DE894DA4B517B93C6A05852C444FE409ESESSCMS0356e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [Gen-art] Genart review of draft-ietf-pkix-cmp-transport-protocols-19
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2012 05:45:59 -0000

--_000_7F2072F1E0DE894DA4B517B93C6A05852C444FE409ESESSCMS0356e_
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-pkix-cmp-transport-protocols-19.txt
Reviewer: Christer Holmberg
Review Date: 14 May 2012
IETF LC End Date: 21 May 2012
IESG Telechat date: 24 May 2012

Summary: The draft is ready for publication. My previous comments (version =
-18) have been addressed.

Major issues: -

Minor issues: -

Nits/editorial comments: -


Regards,



Christer

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif";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; <a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/=
GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;=
font-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif";color:black'>Please wait for direction from your document sheph=
erd or AD before posting a new version of the draft.<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","s=
ans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black=
'>Document: draft-ietf-pkix-cmp-transport-protocols-19.txt<o:p></o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Taho=
ma","sans-serif";color:black'>Reviewer: Christer Holmberg<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif";color:black'>Review Date: 14 May 2012<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif";color:black'>IETF LC End Date: 21 May 2012<o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma",=
"sans-serif";color:black'>IESG Telechat date: 24 May 2012<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorm=
al><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:=
black'>Summary: The draft is ready for publication. My previous comments (v=
ersion -18) have been addressed.<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:bla=
ck'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-si=
ze:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Major issues: -<o:=
p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Tahoma","san=
s-serif";color:black'>Minor issues: -<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";colo=
r:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Nits/editoria=
l comments: -<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:=
p></span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-=
serif";color:black'>Regards,<o:p></o:p></span></p><p><span style=3D'font-si=
ze:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p>&nbsp;</o:p><=
/span></p><p><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-ser=
if";color:black'>Christer<o:p></o:p></span></p></div></body></html>=

--_000_7F2072F1E0DE894DA4B517B93C6A05852C444FE409ESESSCMS0356e_--

From vkg@bell-labs.com  Fri May 18 06:20:04 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BD4621F8576 for <gen-art@ietfa.amsl.com>; Fri, 18 May 2012 06:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.682
X-Spam-Level: 
X-Spam-Status: No, score=-107.682 tagged_above=-999 required=5 tests=[AWL=-1.083, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PtwJn6AeVHpD for <gen-art@ietfa.amsl.com>; Fri, 18 May 2012 06:20:03 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id BA79B21F8575 for <gen-art@ietf.org>; Fri, 18 May 2012 06:20:03 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id q4IDK0jm010645 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 18 May 2012 08:20:01 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q4IDJx8u028541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 18 May 2012 08:20:00 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q4IDJt4x015944; Fri, 18 May 2012 08:19:59 -0500 (CDT)
Message-ID: <4FB64DBB.7000206@bell-labs.com>
Date: Fri, 18 May 2012 08:25:15 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: draft-snell-atompub-tombstones@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: General Area Review Team <gen-art@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: [Gen-art] Gen-ART review of draft-snell-atompub-tombstones-15
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2012 13:20:04 -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-snell-atompub-tombstones-15
Reviewer: Vijay K. Gurbani
Review Date: May-18-2012
IETF LC End Date: Feb-21-2012
IESG Telechat date: May-24-2012

Summary: This draft is ready as a Proposed Standard

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

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From ron.even.tlv@gmail.com  Sat May 19 23:50:33 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5037D21F85A0; Sat, 19 May 2012 23:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level: 
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=-0.628, BAYES_20=-0.74, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AGoQSIC09+Ve; Sat, 19 May 2012 23:50:32 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5B421F8599; Sat, 19 May 2012 23:50:26 -0700 (PDT)
Received: by wibhj8 with SMTP id hj8so1109658wib.13 for <multiple recipients>; Sat, 19 May 2012 23:50:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=Kr/BjTgAlXXRfz34R3lHws69uWnBSH+D1pf2vJev9SA=; b=rLU2A6zlMO/uZFd56bV4+oFGAKLn3Yt786sw0pj1Fb5TBULLo+VsZhIJmRA0h3OWgp FCPPQ+3OOkjtnc4mKJ4hhcjSl4xag2pE//l7sFhf6Twx+Fl/47ur59jgqNTcMQuqzzng /1xe1ty5cKU9OgZjSRxk0Qvjpt9aqWd/SZbee+QUq5EbqWKjguebiqsmfKEAIX4Wl9C1 T2oQlIUK1fkVgRcp1PtLPJLrt3cTK77I0ytJQq2YkOxUR6T9peR0BrP5sA/9Xkms34xE DykiMFbK5VBx1S/7rqiW0PB6p8Nrxg6V1Otxd14T1zjG+7uu+33MoOXxF3ahcALVdjnh VZrA==
Received: by 10.180.79.166 with SMTP id k6mr14743884wix.8.1337496626274; Sat, 19 May 2012 23:50:26 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-177-198-116.red.bezeqint.net. [79.177.198.116]) by mx.google.com with ESMTPS id j3sm24030073wiw.1.2012.05.19.23.50.23 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 19 May 2012 23:50:25 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-melnikov-smtp-priority.all@tools.ietf.org>
Date: Sun, 20 May 2012 09:47:52 +0300
Message-ID: <4fb89431.634cb40a.0fe6.ffffbced@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01CD366D.A19A94D0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac02VHodmFEqqIDRT6GfHoZ8rqHIpg==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC review of draft-melnikov-smtp-priority-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2012 06:50:33 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0028_01CD366D.A19A94D0
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-melnikov-smtp-priority-13

Reviewer: Roni Even

Review Date:2012-5-20

IETF LC End Date: 2012-5-28

IESG Telechat date:

 

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

 

Major issues:

 

Minor issues:

 

 

 

Nits/editorial comments:

 

1.       MUA is used but not expanded.

 

 

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1208569498;
	mso-list-type:hybrid;
	mso-list-template-ids:1331728552 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-melni=
kov-smtp-priority-13<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;5&#8211;20<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;5&#8211;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 a standard track </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC</span><=
span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>MUA is =
used but not expanded.<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><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0028_01CD366D.A19A94D0--


From Rajiv.Papneja@huawei.com  Tue May 22 11:30:32 2012
Return-Path: <Rajiv.Papneja@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F408121F85DF; Tue, 22 May 2012 11:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.509
X-Spam-Level: 
X-Spam-Status: No, score=-4.509 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GsTtTbQ9+Vtq; Tue, 22 May 2012 11:30:26 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 02E2121F85D4; Tue, 22 May 2012 11:30:25 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGD85816; Tue, 22 May 2012 14:30:25 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 22 May 2012 11:28:06 -0700
Received: from dfweml511-mbs.china.huawei.com ([169.254.15.75]) by dfweml408-hub.china.huawei.com ([10.193.5.134]) with mapi id 14.01.0323.003; Tue, 22 May 2012 11:28:01 -0700
From: Rajiv Papneja <Rajiv.Papneja@huawei.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Review: draft-ietf-bmwg-protection-meth-09.txt
Thread-Index: AQHM/j0YcQICZ4zzmkasgx8iN2o5AZbWR6dw
Date: Tue, 22 May 2012 18:28:00 +0000
Message-ID: <52B0D42F4BADB144B850705C4549F6EA017F1B97@dfweml511-mbs.china.huawei.com>
References: <4F5973CE.309@nostrum.com> <4F5A784D.4020401@joelhalpern.com>
In-Reply-To: <4F5A784D.4020401@joelhalpern.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.132.180]
Content-Type: multipart/alternative; boundary="_000_52B0D42F4BADB144B850705C4549F6EA017F1B97dfweml511mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Tue, 22 May 2012 11:32:10 -0700
Cc: "draft-ietf-bmwg-protection-meth.all@tools.ietf.org" <draft-ietf-bmwg-protection-meth.all@tools.ietf.org>, "bmwg@ietf.org" <bmwg@ietf.org>
Subject: Re: [Gen-art] Review: draft-ietf-bmwg-protection-meth-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2012 18:30:32 -0000

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

Hello Joel,



Thank you so much for your review and comments. Please see our responses in=
line. We will posting the updated draft soon.



Regards,

-Rajiv



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

From: Joel M. Halpern [mailto:jmh@joelhalpern.com]

Sent: Friday, March 09, 2012 4:38 PM

To: gen-art@ietf.org

Cc: bmwg@ietf.org; draft-ietf-bmwg-protection-meth.all@tools.ietf.org

Subject: [Gen-art] Review: draft-ietf-bmwg-protection-meth-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-bmwg-protection-meth-09.txt

     Methodology for benchmarking MPLS protection mechanisms

Reviewer: Joel M. Halpern

Review Date: 9-March-2012

IETF LC End Date: 20-March-2012

IESG Telechat date: N/A



Summary: This document is almost ready for publication as an

Informational RFC.



Major issues:

     I find a definitions section (Section 3)that says

"This document also uses existing terminology defined in other BMWG work."

and follows this with examples, but neither a complete list of terms nor

a complete list of documents, to be an unclear approach.  If the reader

finds terms they do not know, they have no good indication as to what

document(s) they should read to repair the gap.



response> Addressed this by removing the examples, and adding the reference=
s as following:

The last line in the section 3 now read as -



"This document also uses existing terminology defined in other BMWG

   Work [Br91], [Ma98], [Po06]"

****************



    The description of the General Reference Topology (section 4) seems

unclear to me.  The text starts out discussing, and the diagram

explicitly shows, a Traffic Generator and a Traffic Analyzer.  In the

diagram these are two disparate devices, connected to routers R1 and R5

respectively.  So far, so good.  However, the text then talks about

"the Tester" as being made up of the Traffic generator and the Traffic

Analyzer", and describes "the Tester" as being directly connected to the

Device Under Test.  It is exceedingly unclear whether this is supposed

to mean that the full collection of routers R1-R6 are the device under

test, or whether R1, R5, or some other specific router is the device

under test.



Response>

Current : A Tester is directly connected to the DUT.



New text:  A Tester is connected to the test network and depending upon the=
 test case, the DUT may vary.

***************



     Could an effort be made to reword section 5.7?  First it says "one

or more traffic streams".  Then it says "16 flows".  Then it talks about

traffic spreading across some set of prefixes.  And the description of

the reason for not doing round-robin across the prefixes leaves me even

more confused about what one actually should set up.





Response>

Current: At least 16 flows should be used, and more if possible.

New text: For better accuracy, one may even consider provisioning 16 flows,=
 or

      more if possible.



Current: It is suggested that there be one or more traffic streams as long =
as

   there is a steady and constant rate of flow for all the streams.



New text: It is suggested that there be three or more traffic streams as lo=
ng as

   there is a steady and constant rate of flow for all the streams.



***********

     Section 5.8 describing the capabilities of "the Tester" seems to

contradict section 4, where "the Tester is comprised of" the Traffic

generator and the Traffic Analyzer.  The capabilities listed in section

5.8 go well beyond that.





Response>



Current: The Tester is comprised of a Traffic Generator (TG) & Test Analyze=
r (TA)



New : The Tester is comprised of a Traffic Generator (TG), Test Analyzer (T=
A) and an Emulator

***********



     The 8 scenarios shown in section 6 all have Mid-Point PLRs as far

as I can tell.  Section 7 says that the test it describes can be applied

to all the 8 cases from section 6.  But then it carefully describes

cases of Headend, Mid-Point, and Egress PLR.  But no examples of the

first or third have been shown.  Thus, I do not see, for example, as

described in section 7.1. one can select a scenario from section 6, and

then establish a headend PLR.



Response>

Added the following in section 6

  UR - Upstream router, MID PLR, HE PLR



Updated the topologies accordingly - for R1 added UR in all setups, for R2 =
modified the current description to MID PLR, HE PLR



************



    This reviewer would like to verify that the test procedures

described produce a meaningful value for items like Failover Packet Loss

and Failover Time.  Is there a specific reference for these, since the

actual calculations are not described here?



     Finding the definition of the Failover Time calculation methods

hidden in the reporting format (section 8) was quite surprising.  Given

that these are important definitions for the meaning fo the tests, they

should occur before the test descriptions, not in the reporting format.





Response> We agree to move the failover time measurements sections from the=
 reporting section to section 5.9 -



Text remains the same.



********************



Minor issues:

     As noted by id-nits, section 3 references TERM-ID as a document

defining terminology, but there is no such ID in the list of references.

  And why do the section headers for 5.1, 5.2, and 5.6 also have

"[TERM-ID]"?  Note that even if those section headers are defined terms,

it is stylistically unusual to put the reference into the section header.

(It almost looks like "TERM-ID" was a marker for things which still

needed a proper reference.)





Response> s/[Term-ID]/RFC6414



*********************



     In section 5.1 a set of example failure events is listed.  It is

unclear whether this list is the ones to be tested for, or just "some"

events.  In addition, it is unclear why there is inconsistency in the

coverage of the descriptions of the failures. The three different

monitoring methods are mentioned explicitly with the Interface Shutdown

failures, but are not even mentioned for the other failures.  And then

while most of the failures list local or remote side, the last two

failures do not indicate a side.  Why?



Response> Clarified the significance of mentioning of failover events. Adde=
d remote and local side applicability on Sub-interface failure and Parent i=
nterface failure.



*************************************





     Some of the abbreviations in section 6 are unclear.  For example,

since there is no real provider it is not clear which router(s) are

meant by PE as distinct from P routers.  Also, while I familiar with

Layer3 VPN, I am not familiar with the usage"Layer2 VC".  Further given

taht VPNs have different label usages, I suspect that both "Layer3 VPN"

and "Layer2 VC" are insufficiently specific to match to a specific size

label stack.





     As an example of the above confusion, in the figure in section

6.1.2, the number of labels  in the Layer3VPN from the PE to the P

router is described as going from 2 to 3 upon failure.  The PE->P link

in the diagram is R1->R2, which is upstream of the failure.  So the

number of labels on that link won't change.  The number of labels on the

R6->R3 P->PE link (assuming I have properly guessed what PE is) does go

from 2 to 3.  But the lines refer simply to PE-P.



Response> Following changes have been made



1.    Added a relationship between the general reference topology and indiv=
idual test setups. Suggested that the individual test setups are sub-set of=
 a large topology

2.    Removed TA/TG

3.    Added notes for purposes clarifying the roles of the routers wrt to P=
/PE -



Following template used for all the figures-

               +-------+  +--------+    +--------+

               |  R1   |  |   R2   | PRI|   R3   |

               |  UR/HE|--|  HE/MID|----| MP/TE  |

               |       |  |  PLR   |----|        |

               +-------+  +--------+ BKP+--------+



                             Figure 2.



          Traffic            Num of Labels   Num of labels

                             before failure  after failure

          IP TRAFFIC (P-P)         0             0

          Layer3 VPN (PE-PE)       1             1

          Layer3 VPN (PE-P)        2             2

          Layer2 VC (PE-PE)        1             1

          Layer2 VC (PE-P)         2             2

    Mid-point LSPs           0             0





Note: Please note the following:

For P-P case, R2 and R3 acts as P routers.

For PE-PE case, R2 acts as PE and R3 is acts as a remote PE

   For PE-P case, R2 acts as a PE router, R3 acts as a P router and R5 acts=
 as

remote PE router (Please refer figure 1 for complete setup)

For Mid-point case, R1, R2 and R3 acts as shown in figure - HE, Midpoint/PL=
R

and TE respectively.





***********************************



     Similarly, while I suspect that the numbers are accurate, it is

very hard to map the pre-failure label counts to the diagrams in a way

that explains the difference between the numbers in section 6.1.1/6.1.2

and  6.1.3 and onward.  Assuming PE-PE traffic is HE-TE traffic, then

the internal topology should not affect the label count on that.  So you

probably mean something else.  But I don't know what.



     It is unclear what section 7 means by "Select an overlay technology

(e.g. IGP, VPN, or VC)."  Please clarify.



Response> Clarified Section 7.1.1, step B



New text - Select or enable IP, Layer 3 VPN or Layer 2 VPN services with th=
e DUT as the headend PLR



Updated this as necessary



For section 7.1.2 - test setup, "B" is not applicable - removed.



**********



     Why is section 7.1.3 (determining tailend performance) included in

the document, when no test cases include tailend failure?



Response> Removed 7.1.3



************



     Is it an issue that the timestamp based  method for determining the

failover time will, on average, overestimate the failure time by on

inter-packet interval?  (Based on assuming that on average the failure

and recovery are each uniformly distributed across the inter-packet

interval.)



RESPONSE> We suggest other two measurement methods, so it is up the user to=
 have a preference.



***********





Nits/editorial comments:

     Section 7.1.2 item A refers to 9 scenarios from section 6. There

are only 8.



RESPONSE>  Fixed



*********

     Section 7.4 decides to leave out the nubmer of scenarios from

section 6, leading to a surprising, but otherwise probably meaningless,

difference in wording.



RESPONSE>  Fixed

**************

--_000_52B0D42F4BADB144B850705C4549F6EA017F1B97dfweml511mbschi_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<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:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@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"MsoPlainText">Hello Joel,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thank you so much for your review and comments. P=
lease see our responses inline. We will posting the updated draft soon.<o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Regards,<o:p></o:p></p>
<p class=3D"MsoPlainText">-Rajiv<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<o:p></o:p></p>
<p class=3D"MsoPlainText">From: Joel M. Halpern [mailto:jmh@joelhalpern.com=
] <o:p></o:p></p>
<p class=3D"MsoPlainText">Sent: Friday, March 09, 2012 4:38 PM<o:p></o:p></=
p>
<p class=3D"MsoPlainText">To: gen-art@ietf.org<o:p></o:p></p>
<p class=3D"MsoPlainText">Cc: bmwg@ietf.org; draft-ietf-bmwg-protection-met=
h.all@tools.ietf.org<o:p></o:p></p>
<p class=3D"MsoPlainText">Subject: [Gen-art] Review: draft-ietf-bmwg-protec=
tion-meth-09.txt<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on
<o:p></o:p></p>
<p class=3D"MsoPlainText">Gen-ART, please see the FAQ at <o:p></o:p></p>
<p class=3D"MsoPlainText">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki=
/GenArtfaq&gt;.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please resolve these comments along with any othe=
r Last Call comments
<o:p></o:p></p>
<p class=3D"MsoPlainText">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-bmwg-protection-meth-09.txt<=
o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Methodology for benchmar=
king MPLS protection mechanisms<o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: Joel M. Halpern<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 9-March-2012<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 20-March-2012<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: N/A<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary: This document is almost ready for public=
ation as an
<o:p></o:p></p>
<p class=3D"MsoPlainText">Informational RFC.<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">&nbsp;&nbsp;&nbsp;&nbsp; I find a definitions sec=
tion (Section 3)that says<o:p></o:p></p>
<p class=3D"MsoPlainText">&quot;This document also uses existing terminolog=
y defined in other BMWG work.&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText">and follows this with examples, but neither a com=
plete list of terms nor
<o:p></o:p></p>
<p class=3D"MsoPlainText">a complete list of documents, to be an unclear ap=
proach.&nbsp; If the reader
<o:p></o:p></p>
<p class=3D"MsoPlainText">finds terms they do not know, they have no good i=
ndication as to what
<o:p></o:p></p>
<p class=3D"MsoPlainText">document(s) they should read to repair the gap.<o=
:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">response&gt; Addressed this by removing the examp=
les, and adding the references as following:<o:p></o:p></p>
<p class=3D"MsoPlainText">The last line in the section 3 now read as - <o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&quot;This document also uses existing terminolog=
y defined in other BMWG<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; Work [Br91], [Ma98], [Po06]&quot;<o:=
p></o:p></p>
<p class=3D"MsoPlainText">****************<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp; The description of the General=
 Reference Topology (section 4) seems
<o:p></o:p></p>
<p class=3D"MsoPlainText">unclear to me.&nbsp; The text starts out discussi=
ng, and the diagram
<o:p></o:p></p>
<p class=3D"MsoPlainText">explicitly shows, a Traffic Generator and a Traff=
ic Analyzer.&nbsp; In the
<o:p></o:p></p>
<p class=3D"MsoPlainText">diagram these are two disparate devices, connecte=
d to routers R1 and R5
<o:p></o:p></p>
<p class=3D"MsoPlainText">respectively.&nbsp; So far, so good.&nbsp; Howeve=
r, the text then talks about
<o:p></o:p></p>
<p class=3D"MsoPlainText">&quot;the Tester&quot; as being made up of the Tr=
affic generator and the Traffic
<o:p></o:p></p>
<p class=3D"MsoPlainText">Analyzer&quot;, and describes &quot;the Tester&qu=
ot; as being directly connected to the
<o:p></o:p></p>
<p class=3D"MsoPlainText">Device Under Test.&nbsp; It is exceedingly unclea=
r whether this is supposed
<o:p></o:p></p>
<p class=3D"MsoPlainText">to mean that the full collection of routers R1-R6=
 are the device under
<o:p></o:p></p>
<p class=3D"MsoPlainText">test, or whether R1, R5, or some other specific r=
outer is the device
<o:p></o:p></p>
<p class=3D"MsoPlainText">under test.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">Current : A Tester is directly connected to the D=
UT.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">New text:&nbsp; A Tester is connected to the test=
 network and depending upon the test case, the DUT may vary.<o:p></o:p></p>
<p class=3D"MsoPlainText">***************<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Could an effort be made =
to reword section 5.7?&nbsp; First it says &quot;one
<o:p></o:p></p>
<p class=3D"MsoPlainText">or more traffic streams&quot;.&nbsp; Then it says=
 &quot;16 flows&quot;.&nbsp; Then it talks about
<o:p></o:p></p>
<p class=3D"MsoPlainText">traffic spreading across some set of prefixes.&nb=
sp; And the description of
<o:p></o:p></p>
<p class=3D"MsoPlainText">the reason for not doing round-robin across the p=
refixes leaves me even
<o:p></o:p></p>
<p class=3D"MsoPlainText">more confused about what one actually should set =
up.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">Current: At least 16 flows should be used, and mo=
re if possible.<o:p></o:p></p>
<p class=3D"MsoPlainText">New text: For better accuracy, one may even consi=
der provisioning 16 flows, or
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; more if possible.<=
o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Current: It is suggested that there be one or mor=
e traffic streams as long as<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; there is a steady and constant rate =
of flow for all the streams.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">New text: It is suggested that there be three or =
more traffic streams as long as<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; there is a steady and constant rate =
of flow for all the streams.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">***********<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Section 5.8 describing t=
he capabilities of &quot;the Tester&quot; seems to
<o:p></o:p></p>
<p class=3D"MsoPlainText">contradict section 4, where &quot;the Tester is c=
omprised of&quot; the Traffic
<o:p></o:p></p>
<p class=3D"MsoPlainText">generator and the Traffic Analyzer.&nbsp; The cap=
abilities listed in section
<o:p></o:p></p>
<p class=3D"MsoPlainText">5.8 go well beyond that.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Current: The Tester is comprised of a Traffic Gen=
erator (TG) &amp; Test Analyzer (TA)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">New : The Tester is comprised of a Traffic Genera=
tor (TG), Test Analyzer (TA) and an Emulator<o:p></o:p></p>
<p class=3D"MsoPlainText">***********<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; The 8 scenarios shown in=
 section 6 all have Mid-Point PLRs as far
<o:p></o:p></p>
<p class=3D"MsoPlainText">as I can tell.&nbsp; Section 7 says that the test=
 it describes can be applied
<o:p></o:p></p>
<p class=3D"MsoPlainText">to all the 8 cases from section 6.&nbsp; But then=
 it carefully describes
<o:p></o:p></p>
<p class=3D"MsoPlainText">cases of Headend, Mid-Point, and Egress PLR.&nbsp=
; But no examples of the
<o:p></o:p></p>
<p class=3D"MsoPlainText">first or third have been shown.&nbsp; Thus, I do =
not see, for example, as
<o:p></o:p></p>
<p class=3D"MsoPlainText">described in section 7.1. one can select a scenar=
io from section 6, and
<o:p></o:p></p>
<p class=3D"MsoPlainText">then establish a headend PLR.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">Added the following in section 6<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp; UR - Upstream router, MID PLR, HE PLR <o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Updated the topologies accordingly - for R1 added=
 UR in all setups, for R2 modified the current description to MID PLR, HE P=
LR<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">************<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp; This reviewer would like to ve=
rify that the test procedures
<o:p></o:p></p>
<p class=3D"MsoPlainText">described produce a meaningful value for items li=
ke Failover Packet Loss
<o:p></o:p></p>
<p class=3D"MsoPlainText">and Failover Time.&nbsp; Is there a specific refe=
rence for these, since the
<o:p></o:p></p>
<p class=3D"MsoPlainText">actual calculations are not described here?<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Finding the definition o=
f the Failover Time calculation methods
<o:p></o:p></p>
<p class=3D"MsoPlainText">hidden in the reporting format (section 8) was qu=
ite surprising.&nbsp; Given
<o:p></o:p></p>
<p class=3D"MsoPlainText">that these are important definitions for the mean=
ing fo the tests, they
<o:p></o:p></p>
<p class=3D"MsoPlainText">should occur before the test descriptions, not in=
 the reporting format.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; We agree to move the failover time m=
easurements sections from the reporting section to section 5.9 &#8211;
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Text remains the same.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">********************<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">&nbsp;&nbsp;&nbsp;&nbsp; As noted by id-nits, sec=
tion 3 references TERM-ID as a document
<o:p></o:p></p>
<p class=3D"MsoPlainText">defining terminology, but there is no such ID in =
the list of references.
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;And why do the section headers for 5.=
1, 5.2, and 5.6 also have
<o:p></o:p></p>
<p class=3D"MsoPlainText">&quot;[TERM-ID]&quot;?&nbsp; Note that even if th=
ose section headers are defined terms,
<o:p></o:p></p>
<p class=3D"MsoPlainText">it is stylistically unusual to put the reference =
into the section header.<o:p></o:p></p>
<p class=3D"MsoPlainText">(It almost looks like &quot;TERM-ID&quot; was a m=
arker for things which still
<o:p></o:p></p>
<p class=3D"MsoPlainText">needed a proper reference.)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; s/[Term-ID]/RFC6414<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">*********************<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; In section 5.1 a set of =
example failure events is listed.&nbsp; It is
<o:p></o:p></p>
<p class=3D"MsoPlainText">unclear whether this list is the ones to be teste=
d for, or just &quot;some&quot;
<o:p></o:p></p>
<p class=3D"MsoPlainText">events.&nbsp; In addition, it is unclear why ther=
e is inconsistency in the
<o:p></o:p></p>
<p class=3D"MsoPlainText">coverage of the descriptions of the failures. The=
 three different
<o:p></o:p></p>
<p class=3D"MsoPlainText">monitoring methods are mentioned explicitly with =
the Interface Shutdown
<o:p></o:p></p>
<p class=3D"MsoPlainText">failures, but are not even mentioned for the othe=
r failures.&nbsp; And then
<o:p></o:p></p>
<p class=3D"MsoPlainText">while most of the failures list local or remote s=
ide, the last two
<o:p></o:p></p>
<p class=3D"MsoPlainText">failures do not indicate a side.&nbsp; Why?<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; Clarified the significance of mentio=
ning of failover events. Added remote and local side applicability on Sub-i=
nterface failure and Parent interface failure.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">*************************************<o:p></o:p><=
/p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Some of the abbreviation=
s in section 6 are unclear.&nbsp; For example,
<o:p></o:p></p>
<p class=3D"MsoPlainText">since there is no real provider it is not clear w=
hich router(s) are
<o:p></o:p></p>
<p class=3D"MsoPlainText">meant by PE as distinct from P routers.&nbsp; Als=
o, while I familiar with
<o:p></o:p></p>
<p class=3D"MsoPlainText">Layer3 VPN, I am not familiar with the usage&quot=
;Layer2 VC&quot;.&nbsp; Further given
<o:p></o:p></p>
<p class=3D"MsoPlainText">taht VPNs have different label usages, I suspect =
that both &quot;Layer3 VPN&quot;
<o:p></o:p></p>
<p class=3D"MsoPlainText">and &quot;Layer2 VC&quot; are insufficiently spec=
ific to match to a specific size
<o:p></o:p></p>
<p class=3D"MsoPlainText">label stack.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; As an example of the abo=
ve confusion, in the figure in section
<o:p></o:p></p>
<p class=3D"MsoPlainText">6.1.2, the number of labels&nbsp; in the Layer3VP=
N from the PE to the P
<o:p></o:p></p>
<p class=3D"MsoPlainText">router is described as going from 2 to 3 upon fai=
lure.&nbsp; The PE-&gt;P link
<o:p></o:p></p>
<p class=3D"MsoPlainText">in the diagram is R1-&gt;R2, which is upstream of=
 the failure.&nbsp; So the
<o:p></o:p></p>
<p class=3D"MsoPlainText">number of labels on that link won't change.&nbsp;=
 The number of labels on the
<o:p></o:p></p>
<p class=3D"MsoPlainText">R6-&gt;R3 P-&gt;PE link (assuming I have properly=
 guessed what PE is) does go
<o:p></o:p></p>
<p class=3D"MsoPlainText">from 2 to 3.&nbsp; But the lines refer simply to =
PE-P.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; Following changes have been made <o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">1.&nbsp;&nbsp;&nbsp; Added a relationship between=
 the general reference topology and individual test setups. Suggested that =
the individual test setups are sub-set of a large topology
<o:p></o:p></p>
<p class=3D"MsoPlainText">2.&nbsp;&nbsp;&nbsp; Removed TA/TG <o:p></o:p></p=
>
<p class=3D"MsoPlainText">3.&nbsp;&nbsp;&nbsp; Added notes for purposes cla=
rifying the roles of the routers wrt to P/PE &#8211;
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Following template used for all the figures- <o:p=
></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;-------&#43;&nbsp; &#43;-----=
---&#43;&nbsp;&nbsp;&nbsp; &#43;--------&#43;<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; R1&nbsp;&nbsp; |&nbsp; |&nbsp;&=
nbsp; R2&nbsp;&nbsp; | PRI|&nbsp;&nbsp; R3&nbsp;&nbsp; |<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; UR/HE|--|&nbsp; HE/MID|----| MP=
/TE&nbsp; |<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |=
&nbsp; |&nbsp; PLR&nbsp;&nbsp; |----|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; |<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-------&#43;&nbsp; &#43;--------&#=
43; BKP&#43;--------&#43;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Figure 2.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Traffic&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Num of Labels&nbsp;&nbsp; Num of labels<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; before failure&nbsp; after fai=
lure<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; IP TRAFFIC (P-P)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<o:p=
></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Layer3 VPN (PE-PE)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<o:p></o:p></p=
>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Layer3 VPN (PE-P)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2<o:p></o:=
p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Layer2 VC (PE-PE)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1<o:p></o:=
p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Layer2 VC (PE-P)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2<o:p=
></o:p></p>
<p class=3D"MsoPlainText" style=3D"text-indent:.5in">&nbsp;&nbsp; &nbsp;Mid=
-point LSPs&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Note: Please note the following:<o:p></o:p></p>
<p class=3D"MsoPlainText">For P-P case, R2 and R3 acts as P routers.<o:p></=
o:p></p>
<p class=3D"MsoPlainText">For PE-PE case, R2 acts as PE and R3 is acts as a=
 remote PE
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;For PE-P case, R2 acts as a PE =
router, R3 acts as a P router and R5 acts as
<o:p></o:p></p>
<p class=3D"MsoPlainText">remote PE router (Please refer figure 1 for compl=
ete setup)<o:p></o:p></p>
<p class=3D"MsoPlainText">For Mid-point case, R1, R2 and R3 acts as shown i=
n figure &#8211; HE, Midpoint/PLR
<o:p></o:p></p>
<p class=3D"MsoPlainText">and TE respectively. <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">***********************************<o:p></o:p></p=
>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Similarly, while I suspe=
ct that the numbers are accurate, it is
<o:p></o:p></p>
<p class=3D"MsoPlainText">very hard to map the pre-failure label counts to =
the diagrams in a way
<o:p></o:p></p>
<p class=3D"MsoPlainText">that explains the difference between the numbers =
in section 6.1.1/6.1.2
<o:p></o:p></p>
<p class=3D"MsoPlainText">and&nbsp; 6.1.3 and onward.&nbsp; Assuming PE-PE =
traffic is HE-TE traffic, then
<o:p></o:p></p>
<p class=3D"MsoPlainText">the internal topology should not affect the label=
 count on that.&nbsp; So you
<o:p></o:p></p>
<p class=3D"MsoPlainText">probably mean something else.&nbsp; But I don't k=
now what.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; It is unclear what secti=
on 7 means by &quot;Select an overlay technology
<o:p></o:p></p>
<p class=3D"MsoPlainText">(e.g. IGP, VPN, or VC).&quot;&nbsp; Please clarif=
y.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; Clarified Section 7.1.1, step B <o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">New text - Select or enable IP, Layer 3 VPN or La=
yer 2 VPN services with the DUT as the headend PLR<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Updated this as necessary<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">For section 7.1.2 &#8211; test setup, &#8220;B&#8=
221; is not applicable &#8211; removed.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">**********<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Why is section 7.1.3 (de=
termining tailend performance) included in
<o:p></o:p></p>
<p class=3D"MsoPlainText">the document, when no test cases include tailend =
failure?<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; Removed 7.1.3<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">************<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Is it an issue that the =
timestamp based&nbsp; method for determining the
<o:p></o:p></p>
<p class=3D"MsoPlainText">failover time will, on average, overestimate the =
failure time by on
<o:p></o:p></p>
<p class=3D"MsoPlainText">inter-packet interval?&nbsp; (Based on assuming t=
hat on average the failure
<o:p></o:p></p>
<p class=3D"MsoPlainText">and recovery are each uniformly distributed acros=
s the inter-packet
<o:p></o:p></p>
<p class=3D"MsoPlainText">interval.)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">RESPONSE&gt; We suggest other two measurement met=
hods, so it is up the user to have a preference.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">***********<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Section 7.1.2 item A ref=
ers to 9 scenarios from section 6. There
<o:p></o:p></p>
<p class=3D"MsoPlainText">are only 8.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">RESPONSE&gt;&nbsp; Fixed <o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">*********<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Section 7.4 decides to l=
eave out the nubmer of scenarios from
<o:p></o:p></p>
<p class=3D"MsoPlainText">section 6, leading to a surprising, but otherwise=
 probably meaningless,
<o:p></o:p></p>
<p class=3D"MsoPlainText">difference in wording.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">RESPONSE&gt;&nbsp; Fixed&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">**************<o:p></o:p></p>
</div>
</body>
</html>

--_000_52B0D42F4BADB144B850705C4549F6EA017F1B97dfweml511mbschi_--

From bclaise@cisco.com  Tue May 22 16:44:12 2012
Return-Path: <bclaise@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BA5221F86B0; Tue, 22 May 2012 16:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.543
X-Spam-Level: 
X-Spam-Status: No, score=-10.543 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dBix-febMl-A; Tue, 22 May 2012 16:44:09 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5D221F86AD; Tue, 22 May 2012 16:44:09 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4MNUfbX020073; Wed, 23 May 2012 01:30:41 +0200 (CEST)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4MNUbKH000323; Wed, 23 May 2012 01:30:37 +0200 (CEST)
Message-ID: <4FBC219D.8070000@cisco.com>
Date: Wed, 23 May 2012 01:30:37 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
References: <4f800f2f.634cb40a.13a1.ffff8003@mx.google.com>
In-Reply-To: <4f800f2f.634cb40a.13a1.ffff8003@mx.google.com>
Content-Type: multipart/alternative; boundary="------------080106040303000401020104"
Cc: me <bclaise@cisco.com>, gen-art@ietf.org, 'IETF' <ietf@ietf.org>, draft-claise-export-application-info-in-ipfix.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-claise-export-application-info-in-ipfix-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2012 23:44:12 -0000

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

Hi Roni,

Thanks for your review.
See in-line.
>
> I am the assigned Gen-ART reviewer for this draft. For background on 
> Gen-ART, please see the FAQ at 
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments 
> you may receive.
>
> Document: draft-claise-export-application-info-in-ipfix-05
>
> Reviewer: Roni Even
>
> Review Date:2012--4--7
>
> IETF LC End Date: 2012--4--17
>
> IESG Telechat date:
>
> Summary: This draft is almost ready for publication as an 
> Informational RFC.
>
> Major issues:
>
> Minor issues:
>
> 1.In sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to information 
> in Cisco web page. I could not locate and information that is 
> referenced. The link is to the main Cisco web page. For example in 
> section 6.5 it lists the selectorID as 10000, where is this value located?
>
The exact URsL are 
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html
and 
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html
As you can see from the URLs, there is a chance that those might change.
Stephen Farrell had the same comment.
>
> 2.For the definition of Classification engine IDs in section 4.1 for 
> the non standard values like PANA-L3, PANA-L4, PANA-L7, PANA-L2, is 
> there a requirement that the selector IDs will be publically available?
>
Yes. Also, they would be exported with an IPFIX Options Template Record.
An example of PANA-L3 was the IPFIX port, 4739, which was pre-reserved 
by IANA, 3 years before RFC5101 was published.

> 3.In section 4.2 "However, an IANA L3 protocol encoding may encoded 
> with 3 bytes." When is it encoded in 3 bytes, also figure 2 is not 
> reflecting this example, I expected to see a 32 bit value according to 
> the text and not a general figure. (small nit in the above sentence 
> "may be" instead of "may".
>
Will be corrected.
>
> 4.In section 7 I noticed that "p2pTechnology, tunnelTechnology, and 
> encryptedTechnology" are already assigned in the IANA IPFIX 
> Information elements so why assign them again as new?
>
from RFC5102:

    The value of these identifiers is in the range of 1-32767.  Within
    this range, Information Element identifier values in the sub-range of
    1-127 are compatible with field types used by NetFlow version 9
    [RFC3954  <http://tools.ietf.org/html/rfc3954>].


So basically, if Cisco has assigned those numbers already, they can 
reused in IANA.
>
> 5.In section 7 I noticed that you request that the  
> applicationDescription, applicationId, applicationName, 
> classificationEngineId will receive elementid values from the range 
> 0-127. My reading from section 4.2 is this is not required, maybe add 
> text that will explain this request.
>
See my previous remark.
>
> 6.In the security section arethere additional considerations when the 
> applicationid information is coming from a proprietary classification 
> engine about authentication of the information source?
>
Not as far as I know.
Maybe I'm missing something. Can you please elaborate.
>
> Nits/editorial comments:
>
> 1.In section 4.1 last sentence what is the meaning of "by theses 
> specifications" , I did not understand the context.
>
> 2.In section 6.6 "to determine whether or the default HTTP port" 
> delete the "or"
>
> 3.In section 6.6 "The Classification Engine ID is 2" should be "3".
>

will be corrected.

Thanks again.

Regards, Benoit.
>


--------------080106040303000401020104
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">
    Hi Roni,<br>
    <br>
    Thanks for your review.<br>
    See in-line.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1032532832;
	mso-list-type:hybrid;
	mso-list-template-ids:-209704826 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1347488741;
	mso-list-type:hybrid;
	mso-list-template-ids:-636856504 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="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">I am the assigned Gen-ART reviewer for this
          draft. For background on Gen-ART, please see the FAQ at &lt;<a
            moz-do-not-send="true"
            href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
            target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Please resolve these comments along with
          any other Last Call comments you may receive.<o:p></o:p></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Document:
          </span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">draft-claise-export-application-info-in-ipfix-05<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Reviewer:
            Roni Even<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Review
            Date:2012&#8211;4&#8211;7<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IETF
            LC End Date: 2012&#8211;4&#8211;17<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IESG
            Telechat date:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary:
            This draft is almost ready for publication as an
            Informational </span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">RFC</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Major
            issues:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Minor
            issues:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">1.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;;">In sections 2,
            4.1 (PANA-L7), 5, 6.5 the draft points to information in
            Cisco web page. I could not locate and information that is
            referenced. The link is to the main Cisco web page. For
            example in section 6.5 it lists the selectorID as 10000,
            where is this value located?</span></p>
      </div>
    </blockquote>
    The exact URsL are
    <a class="moz-txt-link-freetext"
href="http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html">http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html</a><br>
    and
    <a class="moz-txt-link-freetext"
href="http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html">http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html</a><br>
    As you can see from the URLs, there is a chance that those might
    change.<br>
    Stephen Farrell had the same comment. <br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">2.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">For
            the definition of Classification engine IDs in section 4.1
            for the non standard values like PANA-L3, PANA-L4, PANA-L7,
            PANA-L2, is there a requirement that the selector IDs will
            be publically available?</span></p>
      </div>
    </blockquote>
    Yes. Also, they would be exported with an IPFIX Options Template
    Record.<br>
    An example of PANA-L3 was the IPFIX port, 4739, which was
    pre-reserved by IANA, 3 years before RFC5101 was published.<br>
    <br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">3.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            section 4.2 &#8220;However, an IANA L3 protocol encoding may
            encoded with 3 bytes.&#8221; When is it encoded in 3 bytes, also
            figure 2 is not reflecting this example, I expected to see a
            32 bit value according to the text and not a general figure.
            (small nit in the above sentence &#8220;may be&#8221; instead of &#8220;may&#8221;.</span></p>
      </div>
    </blockquote>
    Will be corrected.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">4.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            section 7 I noticed that &#8221;p2pTechnology, tunnelTechnology,
            and encryptedTechnology&#8221; are already assigned in the IANA
            IPFIX Information elements so why assign them again as new?</span></p>
      </div>
    </blockquote>
    from RFC5102:<br>
    <pre class="newpage">   The value of these identifiers is in the range of 1-32767.  Within
   this range, Information Element identifier values in the sub-range of
   1-127 are compatible with field types used by NetFlow version 9
   [<a href="http://tools.ietf.org/html/rfc3954" title="&quot;Cisco Systems NetFlow Services Export Version 9&quot;">RFC3954</a>].

</pre>
    So basically, if Cisco has assigned those numbers already, they can
    reused in IANA.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">5.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            section 7 I noticed that you request that the&nbsp;
            applicationDescription, applicationId, applicationName,
            classificationEngineId will receive elementid values from
            the range 0-127. My reading from section 4.2 is this is not
            required, maybe add text that will explain this request.</span></p>
      </div>
    </blockquote>
    See my previous remark.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">6.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            the security section are</span><span style="font-size: 11pt;
            font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">
            there additional considerations when the applicationid
            information is coming from a proprietary classification
            engine about authentication of the information source?</span></p>
      </div>
    </blockquote>
    Not as far as I know.<br>
    Maybe I'm missing something. Can you please elaborate.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Nits/editorial
            comments:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
          lfo2"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">1.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            section 4.1 last sentence what is the meaning of &#8220;by theses
            specifications&#8221; , I did not understand the context.<o:p></o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
          lfo2"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">2.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            section 6.6 &#8220;</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">to
            determine whether or the default HTTP port&#8221; delete the &#8220;or&#8221;<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">3.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;;">In section 6.6
            &#8220;The Classification Engine ID is 2&#8221; should be &#8220;3&#8221;.</span></p>
      </div>
    </blockquote>
    <br>
    will be corrected.<br>
    <br>
    Thanks again.<br>
    <br>
    Regards, Benoit.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
          lfo2"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------080106040303000401020104--

From ron.even.tlv@gmail.com  Wed May 23 00:14:08 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F61C21F8587; Wed, 23 May 2012 00:14:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.293
X-Spam-Level: 
X-Spam-Status: No, score=-3.293 tagged_above=-999 required=5 tests=[AWL=0.305,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vl8N91RWfaUn; Wed, 23 May 2012 00:14:05 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id C29B121F8596; Wed, 23 May 2012 00:14:04 -0700 (PDT)
Received: by werb13 with SMTP id b13so3849212wer.31 for <multiple recipients>; Wed, 23 May 2012 00:14:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=i0uIYONZ23Pp3We4GBrw/scoeu3XMXvXaS1hp9fbhcE=; b=kcgTJf35t25E4XeWZUU9/yGmCzAK1EEpUwHaKDP6j3lcSNnGJsMEeJewbmgkJ56xGH RAmlm3V3gYGzfMRAQT7iEayub1nRN+kzxUhlXLEhqhV3/ONLLchsIa17vNRJVgHsapG4 5uTH0Q6+4xXMdcKMJ1Ecu/VBFfKuaku55c/ZlmMLYibRaKtRRxtrvE128i6jdjiOgPQe BXJiHBeTmFtFvYZPr6oExKD2xKnm1JW/2BbPPw2bPm7nYIAQtp+Aiv/6Ai1RvekyaqDW kCE4zu8ZYmQRIVD/on2Tx2BTaTL5+sZ6ooFQtzyaF/dY/wZNIK0dbDIyGm3MxQwZd3U6 pNig==
Received: by 10.180.98.201 with SMTP id ek9mr43318051wib.7.1337757243756; Wed, 23 May 2012 00:14:03 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-177-198-116.red.bezeqint.net. [79.177.198.116]) by mx.google.com with ESMTPS id gb9sm38468117wib.8.2012.05.23.00.14.01 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 May 2012 00:14:03 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Benoit Claise'" <bclaise@cisco.com>
References: <4f800f2f.634cb40a.13a1.ffff8003@mx.google.com> <4FBC219D.8070000@cisco.com>
In-Reply-To: <4FBC219D.8070000@cisco.com>
Date: Wed, 23 May 2012 10:11:50 +0300
Message-ID: <4fbc8e3b.2968b40a.5c9a.4414@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002E_01CD38CC.7A29B550"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac04cuj+nPaJQ4f7Ra6W4Tdvse+fBgAPFb+g
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>, draft-claise-export-application-info-in-ipfix.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-claise-export-application-info-in-ipfix-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2012 07:14:08 -0000

This is a multi-part message in MIME format.

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

Hi Benoit,

Thanks, see in-line

Roni

 

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

 

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

 

Document: draft-claise-export-application-info-in-ipfix-05

Reviewer: Roni Even

Review Date:2012-4-7

IETF LC End Date: 2012-4-17

IESG Telechat date:

 

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

 

Major issues:

 

Minor issues:

 

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

The exact URsL are
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/pre
sentation_c96-629396.html
and
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/pro
duct_bulletin_c25-627831.html
As you can see from the URLs, there is a chance that those might change.
Stephen Farrell had the same comment. 

 

RE: My concern was that going to Cisco web page I tried to search for the
information using the search window and could not find it so I think that
this link is not helpful for finding the information.





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

Yes. Also, they would be exported with an IPFIX Options Template Record.
An example of PANA-L3 was the IPFIX port, 4739, which was pre-reserved by
IANA, 3 years before RFC5101 was published.

 

RE: OK






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

Will be corrected.

 

RE:OK





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

from RFC5102:

   The value of these identifiers is in the range of 1-32767.  Within
   this range, Information Element identifier values in the sub-range of
   1-127 are compatible with field types used by NetFlow version 9
   [RFC3954 <http://tools.ietf.org/html/rfc3954> ].
 

So basically, if Cisco has assigned those numbers already, they can reused
in IANA.

 

RE: The question is if you want the existing assignment to be used without
change than why have this information in the IANA consideration in the first
place. 

 





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

See my previous remark. 

 

RE:  OK, even though it should be clear that this applies to these specific
selectors since you want them to be compatible with NetFlow version 9 and it
is not a general request for using specific sub range for all selectors.





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

Not as far as I know.
Maybe I'm missing something. Can you please elaborate.

RE: No, this is OK for me.





 

Nits/editorial comments:

 

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

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

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


will be corrected.

Thanks again.

Regards, Benoit.



 

 


------=_NextPart_000_002E_01CD38CC.7A29B550
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	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";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;
	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;}
span.EmailStyle19
	{mso-style-type:personal;
	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: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.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1032532832;
	mso-list-type:hybrid;
	mso-list-template-ids:-209704826 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1347488741;
	mso-list-type:hybrid;
	mso-list-template-ids:-636856504 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite =
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Hi =
Benoit,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks, see in-line<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><p class=3DMsoNormal>I am the assigned Gen-ART reviewer for this =
draft. For background on Gen-ART, please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
draft-claise-export-application-info-in-ipfix-05</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;4&#8211;7</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;4&#8211;17</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as an Informational =
RFC.</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In =
sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to information in =
Cisco web page. I could not locate and information that is referenced. =
The link is to the main Cisco web page. For example in section 6.5 it =
lists the selectorID as 10000, where is this value =
located?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>The =
exact URsL are <a =
href=3D"http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555=
/ps6601/presentation_c96-629396.html">http://www.cisco.com/en/US/prod/col=
lateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html</a><br=
>and <a =
href=3D"http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558=
/ps6616/product_bulletin_c25-627831.html">http://www.cisco.com/en/US/prod=
/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.htm=
l</a><br>As you can see from the URLs, there is a chance that those =
might change.<br>Stephen Farrell had the same comment. </span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: My concern was that going to Cisco web =
page I tried to search for the information using the search window and =
could not find it so I think that this link is not helpful for finding =
the information.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>For the =
definition of Classification engine IDs in section 4.1 for the non =
standard values like PANA-L3, PANA-L4, PANA-L7, PANA-L2, is there a =
requirement that the selector IDs will be publically =
available?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>Yes. =
Also, they would be exported with an IPFIX Options Template =
Record.<br>An example of PANA-L3 was the IPFIX port, 4739, which was =
pre-reserved by IANA, 3 years before RFC5101 was published.</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: OK<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><br><o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
4.2 &#8220;However, an IANA L3 protocol encoding may encoded with 3 =
bytes.&#8221; When is it encoded in 3 bytes, also figure 2 is not =
reflecting this example, I expected to see a 32 bit value according to =
the text and not a general figure. (small nit in the above sentence =
&#8220;may be&#8221; instead of =
&#8220;may&#8221;.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>Will =
be corrected.</span><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif";color:#1F497D'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE:OK<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
7 I noticed that &#8221;p2pTechnology, tunnelTechnology, and =
encryptedTechnology&#8221; are already assigned in the IANA IPFIX =
Information elements so why assign them again as =
new?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>from =
RFC5102:<o:p></o:p></span></p><pre>&nbsp;&nbsp; The value of these =
identifiers is in the range of 1-32767.&nbsp; =
Within<o:p></o:p></pre><pre>&nbsp;&nbsp; this range, Information Element =
identifier values in the sub-range of<o:p></o:p></pre><pre>&nbsp;&nbsp; =
1-127 are compatible with field types used by NetFlow version =
9<o:p></o:p></pre><pre>&nbsp;&nbsp; [<a =
href=3D"http://tools.ietf.org/html/rfc3954" title=3D"&quot;Cisco Systems =
NetFlow Services Export Version =
9&quot;">RFC3954</a>].<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>So =
basically, if Cisco has assigned those numbers already, they can reused =
in IANA.</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: The question is if you want the existing =
assignment to be used without change than why have this information in =
the IANA consideration in the first place. <o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
7 I noticed that you request that the&nbsp; applicationDescription, =
applicationId, applicationName, classificationEngineId will receive =
elementid values from the range 0-127. My reading from section 4.2 is =
this is not required, maybe add text that will explain this =
request.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>See =
my previous remark.</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'> <o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: &nbsp;OK, even though it should be clear =
that this applies to these specific selectors since you want them to be =
compatible with NetFlow version 9 and it is not a general request for =
using specific sub range for all selectors.<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In the =
security section are there additional considerations when the =
applicationid information is coming from a proprietary classification =
engine about authentication of the information =
source?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>Not =
as far as I know.<br>Maybe I'm missing something. Can you please =
elaborate.</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: No, this is OK for =
me.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![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 =
4.1 last sentence what is the meaning of &#8220;by theses =
specifications&#8221; , I did not understand the =
context.</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><span style=3D'mso-list:Ignore'>2.<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 =
6.6 &#8220;to determine whether or the default HTTP port&#8221; delete =
the &#8220;or&#8221;</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
6.6 &#8220;The Classification Engine ID is 2&#8221; should be =
&#8220;3&#8221;.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br>will be corrected.<br><br>Thanks =
again.<br><br>Regards, Benoit.<br><br><o:p></o:p></span></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_002E_01CD38CC.7A29B550--


From miguel.a.garcia@ericsson.com  Wed May 23 00:22:21 2012
Return-Path: <miguel.a.garcia@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA4821F855B for <gen-art@ietfa.amsl.com>; Wed, 23 May 2012 00:22:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.649
X-Spam-Level: 
X-Spam-Status: No, score=-6.649 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CYZ88J9UXlCQ for <gen-art@ietfa.amsl.com>; Wed, 23 May 2012 00:22:20 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 0A56D21F855A for <gen-art@ietf.org>; Wed, 23 May 2012 00:22:19 -0700 (PDT)
X-AuditID: c1b4fb30-b7b55ae000002887-cb-4fbc902a9207
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 5C.22.10375.A209CBF4; Wed, 23 May 2012 09:22:18 +0200 (CEST)
Received: from [159.107.24.192] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.3.213.0; Wed, 23 May 2012 09:22:17 +0200
Message-ID: <4FBC9029.1000305@ericsson.com>
Date: Wed, 23 May 2012 09:22:17 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: draft-ietf-pwe3-redundancy-bit.authors@tools.ietf.org,  Andy Malis <amalis@gmail.com>, pwe3-chairs@tools.ietf.org, Stewart Bryant <stbryant@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: General Area Review Team <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-pwe3-redundancy-bit-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2012 07:22:21 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft. For background on Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

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

Document: draft-ietf-pwe3-redundancy-bit-07.txt
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 23-May-2012
IESG Telechat date: 24-May-2012

Summary: The document is almost ready for publication as a standards 
track RFC, but has some minor issues that should be fixed.

I reviewed version -06 of this document. At that time I had a few 
comments. Most of them have been successfully addressed. In this review I 
am addressing the leftovers and new issues.

Major issues: none

Minor issues:

- In my previous review, I highlighted that many lowercase 2119-reserved 
words (like "must", "may", etc.) should actually be written in uppercase 
to be really normative. Rather than analyzing each case on a one by one 
basis, the authors have systematically written in uppercase all 
2119-reserved words. The problem is that now some uppercase 2119-reserved 
words don't make sense, and should be reverted to lowercase. Allow me 
some examples:

   * Sections 1 (Introduction) and 2 (Motivation and Scope). Since these 
are descriptive sections in nature, normative text should not be written 
here. If there is a need to write normative text, it should be written 
later in any of the procedures sections.

   * Section 5.2, 1st paragraph, the "MUST" does not really have a 
normative intention as it is currently written:

    One endpoint node of the redundant set of PWs is designated the
    Master and is responsible for selecting which PW both endpoints MUST
    use to forward user traffic.

   * Section 15.2. I understand that this section describes scenarios or 
examples of architectures. Therefore, it does not make sense to write 
normative statements in here. If you need one, it should be written in 
any of the procedures sections. There is a "SHOULD" on the 4th paragraph 
of Section 15.2. The same applies to the last paragraph in Section 15.4 
and last paragraph in Section 15.6.




Nits/editorial comments:

- The abstract has added a new sentence at the end. Unfortunately there 
is a new reference "in RFC 5542 [9]". Abstracts shouldn't include 
references. Just write "... in RFC 5542".

- There is an extra dot at the end of the second paragraph in Section 
6.1. The same happen in the last paragraph of Section 15.3. And yet the 
same in the third paragraph of Section 15.4, and the second paragraph in 
15.6.

- Section 15.4, second paragraph, the term "Figure" is repeated.

- Section 15.5, the last paragraph starts with some strange indentation.

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

From wassim.haddad@ericsson.com  Wed May 23 22:48:46 2012
Return-Path: <wassim.haddad@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A39221F850C for <gen-art@ietfa.amsl.com>; Wed, 23 May 2012 22:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6uBeUearZPcM for <gen-art@ietfa.amsl.com>; Wed, 23 May 2012 22:48:45 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7C45C21F850B for <gen-art@ietf.org>; Wed, 23 May 2012 22:48:45 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q4O5mfYZ016124; Thu, 24 May 2012 00:48:44 -0500
Received: from [164.48.125.36] (147.117.20.214) by eusaamw0711.eamcs.ericsson.se (147.117.20.179) with Microsoft SMTP Server id 8.3.213.0; Thu, 24 May 2012 01:48:43 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 23 May 2012 22:48:38 -0700
Message-ID: <7C1F64FA-2589-47DD-9AB3-71B850D20AA9@ericsson.com>
To: Gen-art <gen-art@ietf.org>
MIME-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Cc: draft-ietf-ledbat-congestion.all@tools.ietf.org
Subject: [Gen-art]  Gen-ART review of draft-ietf-ledbat-congestion-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2012 05:48:46 -0000

I have been selected as the General Area Review Team reviewer for this =
draft.=20
For background on Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

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

Document: draft-ietf-ledbat-congestion-09
Reviewer: Wassim Haddad
Review Date: 23-May-2012
IESG Telechat date: 24-May-2012

Summary: The document is ready for publication as an experimental RFC.=20=


Major Issues: None
Minor Issues: None


Regards,

Wassim H.






From alexey.melnikov@isode.com  Thu May 24 01:33:32 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C445821F8603; Thu, 24 May 2012 01:33:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iYxz4q+yffKr; Thu, 24 May 2012 01:33:31 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5F621F85FD; Thu, 24 May 2012 01:33:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1337848410; d=isode.com; s=selector; i=@isode.com; bh=1+fS+vrIYw5fHFLlvwVeRV5Y0fi4KKv0f/QjpxlRHRs=; 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=lJN0BmbZEzgw+63q0CMBoaiMpDiW6XssutUOenxaj3Bkq0r2bIhSXwSRyzyiSAfYhaBAnN Ha2rW5+ntLTk5yD1Vlh4J2WSlAcV9fzyQeVLSy/CmEm/T9RFHZKXKTM9ifmaqXMSpkSb8I UsRGUOv8sD/VlH4VZE0L6CFgSAuilAY=;
Received: from [192.168.1.144] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T73yWgAE4yDB@rufus.isode.com>; Thu, 24 May 2012 09:33:30 +0100
X-SMTP-Protocol-Errors: NORDNS PIPELINING
Message-ID: <4FBDF270.10606@isode.com>
Date: Thu, 24 May 2012 09:33:52 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Roni Even <ron.even.tlv@gmail.com>
References: <4fb89431.634cb40a.0fe6.ffffbced@mx.google.com>
In-Reply-To: <4fb89431.634cb40a.0fe6.ffffbced@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------050109010604060202050908"
Cc: gen-art@ietf.org, draft-melnikov-smtp-priority.all@tools.ietf.org, 'IETF' <ietf@ietf.org>
Subject: Re: [Gen-art] Gen-ART LC review of draft-melnikov-smtp-priority-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2012 08:33:32 -0000

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

Hi Roni,

On 20/05/2012 07:47, Roni Even wrote:
>
> I am the assigned Gen-ART reviewer for this draft. For background on 
> Gen-ART, please see the FAQ at 
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments 
> you may receive.
>
> Document: draft-melnikov-smtp-priority-13
>
> Reviewer: Roni Even
>
> Review Date:2012--5--20
>
> IETF LC End Date: 2012--5--28
>
> IESG Telechat date:
>
> Summary: This draft is ready for publication as a standard track RFC.
>
> Major issues:
>
> Minor issues:
>
> Nits/editorial comments:
>
> 1.MUA is used but not expanded.
>

Expanded the first reference in my copy, thanks.


--------------050109010604060202050908
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">
    Hi Roni,<br>
    <br>
    On 20/05/2012 07:47, Roni Even wrote:
    <blockquote cite="mid:4fb89431.634cb40a.0fe6.ffffbced@mx.google.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1208569498;
	mso-list-type:hybrid;
	mso-list-template-ids:1331728552 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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">I am the assigned Gen-ART reviewer for this
          draft. For background on Gen-ART, please see the FAQ at &lt;<a
            moz-do-not-send="true"
            href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
            target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Please resolve these comments along with
          any other Last Call comments you may receive.<o:p></o:p></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Document:
          </span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">draft-melnikov-smtp-priority-13<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Reviewer:
            Roni Even<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Review
            Date:2012&#8211;5&#8211;20<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IETF
            LC End Date: 2012&#8211;5&#8211;28<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IESG
            Telechat date:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary:
            This draft is ready for publication as a standard track </span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">RFC</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Major
            issues:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Minor
            issues:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Nits/editorial
            comments:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">1.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;;">MUA is used but
            not expanded.</span></p>
      </div>
    </blockquote>
    <br>
    Expanded the first reference in my copy, thanks.<br>
    <br>
  </body>
</html>

--------------050109010604060202050908--

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

Hi all,

The following reviewers have assignments:

Reviewer                 LC end     Draft

Alexey Melnikov        T 2012-06-06 draft-ietf-trill-rbridge-bfd-05

Ben Campbell           T 2012-06-06 draft-ietf-trill-rbridge-extension-04

Vijay Gurbani            2012-06-06 
draft-ietf-nfsv4-pnfs-block-disk-protection-02

Wassim Haddad            2012-06-06 draft-ietf-cdni-problem-statement-06

T - on an upcoming Telechat (June 6)


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

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From vkg@bell-labs.com  Thu May 24 13:54:44 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 000E111E80D5 for <gen-art@ietfa.amsl.com>; Thu, 24 May 2012 13:54:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.599
X-Spam-Level: 
X-Spam-Status: No, score=-108.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vbl4kb1O6qvn for <gen-art@ietfa.amsl.com>; Thu, 24 May 2012 13:54:43 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 5220611E8081 for <gen-art@ietf.org>; Thu, 24 May 2012 13:54:43 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q4OKseL8004201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 24 May 2012 15:54:40 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q4OKsdM1007791 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 May 2012 15:54:40 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q4OKsbtx007387; Thu, 24 May 2012 15:54:39 -0500 (CDT)
Message-ID: <4FBEA152.1080305@bell-labs.com>
Date: Thu, 24 May 2012 16:00:02 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: draft-ietf-nfsv4-pnfs-block-disk-protection@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.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: General Area Review Team <gen-art@ietf.org>, beepy@netapp.com, spencer.shepler@gmail.com, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [Gen-art] Gen-ART review of draft-ietf-nfsv4-pnfs-block-disk-protection-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2012 20:54:44 -0000

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

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

Document: draft-ietf-nfsv4-pnfs-block-disk-protection-02
Reviewer: Vijay K. Gurbani
Review Date: May-24-2012
IETF LC End Date: June-06-2012
IESG Telechat date: Not known

Summary: This draft is ready as a Proposed Standard

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

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/


From martin.thomson@gmail.com  Thu May 24 15:49:08 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5260121F8533 for <gen-art@ietfa.amsl.com>; Thu, 24 May 2012 15:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=0.294,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4bXsYPbDgkYW for <gen-art@ietfa.amsl.com>; Thu, 24 May 2012 15:49:07 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7414C21F8532 for <gen-art@ietf.org>; Thu, 24 May 2012 15:49:07 -0700 (PDT)
Received: by bkty8 with SMTP id y8so295548bkt.31 for <gen-art@ietf.org>; Thu, 24 May 2012 15:49:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=9ShSwPjBfcWeh9x2AFrefXgf3IoyJ4c9qQkPeCGxwKw=; b=wuO2vqtHsUnkmlNn6v8rOlDwjum4bAVJtgJSQJMwKLfOA44kh6gdvTDHBo+mzpWDEA sakq6WX+bAxpDOsdw+tg9lJ+hv9gRJiLEwTB2wBNgj0u/TpLfpOqXxy3dT57KcZbFvVY NX4j2sT2VsqVTAojgx1Y3x+GeFQyYpEG4Znb5OGewdjnoGdWhC81eRJks0V8v+ikQZ19 GxYxfwcZR42gFRTUi7jcdt872NrCvxnOL+gvDnrRxsOAfPNj2jmJ1Iiv7+c1aNg1LDMz AsKX4wrzWrWHuRFBnTYUFvaYpCa7nVJ/BedyAm4kcpzwUnFCaSgF8/H8s1b+HN/WrbYQ z1cg==
MIME-Version: 1.0
Received: by 10.204.150.84 with SMTP id x20mr500224bkv.26.1337899746471; Thu, 24 May 2012 15:49:06 -0700 (PDT)
Received: by 10.204.66.4 with HTTP; Thu, 24 May 2012 15:49:06 -0700 (PDT)
In-Reply-To: <CABkgnnXOM28=vT_PWhBwDE3T=KNoYhRJEnqv455YGC2eXF0AfQ@mail.gmail.com>
References: <CABkgnnXOM28=vT_PWhBwDE3T=KNoYhRJEnqv455YGC2eXF0AfQ@mail.gmail.com>
Date: Thu, 24 May 2012 15:49:06 -0700
Message-ID: <CABkgnnUWX2v1WyUSRFsWTC3we_FnUmVR0HwPTEqzrVYAqDyFOA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: gen-art@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: [Gen-art] Fwd: Gen-ART review of draft-ietf-tcpm-tcpmss-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2012 22:49:08 -0000

Feature request for the tool: a place to put reviews so that I don't
keep forgetting to CC the gen-art list.

---------- Forwarded message ----------
From: Martin Thomson <martin.thomson@gmail.com>
Date: 20 May 2012 19:34
Subject: Gen-ART review of draft-ietf-tcpm-tcpmss-04
To: draft-ietf-tcpm-tcpmss.all@tools.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-tcpmss-04
Reviewer: Martin Thomson
Review Date: 2012-05-20
IETF LC End Date:
IESG Telechat date: (if known)

Summary: This draft clarifies a point of potential confusion around
the use of the TCP MSS. =C2=A0The draft is ready for publication as an
informational RFC, with a couple of nits.

Major issues: none

Minor issues: none

Nits/editorial comments:

Opinion... The draft seems a little long. =C2=A0Section 4 contains the only
truly crucial point: namely the one made after the matrix. =C2=A0That
alone, plus the short description in Section 2, seems sufficient. The
appendix is excessive.

Section 6 does not contain security considerations. =C2=A0It need not
contain anything.

Sections 3 and 5 have extra indentation for their subsections.

The table in Section 4 has a wayward period.

From kathleen.moriarty@emc.com  Fri May 25 09:50:28 2012
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0C7421F8743; Fri, 25 May 2012 09:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2mJtkgR8dAFp; Fri, 25 May 2012 09:50:27 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 3009321F873E; Fri, 25 May 2012 09:50:26 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q4PGoGRu008804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 May 2012 12:50:18 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 25 May 2012 12:50:07 -0400
Received: from mxhub30.corp.emc.com (mxhub30.corp.emc.com [128.222.70.170]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q4PGo5w9021493; Fri, 25 May 2012 12:50:05 -0400
Received: from mx15a.corp.emc.com ([169.254.1.101]) by mxhub30.corp.emc.com ([128.222.70.170]) with mapi; Fri, 25 May 2012 12:50:05 -0400
From: <kathleen.moriarty@emc.com>
To: <gen-art@ietf.org>, <iesg@ietf.org>, <draft-ietf-dccp-udpencap.all@tools.ietf.org>
Date: Fri, 25 May 2012 12:50:04 -0400
Thread-Topic: Gen-art review of draft-ietf-dccp-udpencap
Thread-Index: Ac06lm7XJrUTB2x+Q0i/7unKvG9rkg==
Message-ID: <F5063677821E3B4F81ACFB7905573F24018A6373@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: gorry@erg.abdn.ac.uk, tphelan@sonusnet.com
Subject: [Gen-art] Gen-art review of draft-ietf-dccp-udpencap
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2012 16:50: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-dccp-udpencap
Reviewer: Kathleen Moriarty
Review Date: 5/25/12
IETF LC End Date: 5/25/12
IESG Telechat date: (if known)

Summary:  The document is ready with the exception of fixing some reference=
s noted below.

This document specifies an alternative encapsulation of the Datagram
   Congestion Control Protocol (DCCP), referred to as DCCP-UDP.  This
   encapsulation allows DCCP to be carried through the current
   generation of Network Address Translation (NAT) middleboxes without
   modification of those middleboxes.  This document also updates the
   SDP information for DCCP defined in RFC 5762.

Sorry for the late review, I just saw this today!

Major issues:

Minor issues:

Nits/editorial comments:  The document reads well, but there are some refer=
ences that need to be addressed, some removed and one should use the newer =
reference:

Confirmed this one does not appear in text:
=3D=3D Unused Reference: 'RFC5234' is defined on line 758, but no explicit
     reference was found in the text


The following one is OK, I am not sure why the checker doesn't see the refe=
rence in the text.
  =3D=3D Unused Reference: 'RFC4585' is defined on line 786, but no explici=
t
     reference was found in the text

Confirmed this one does not appear in text:
  =3D=3D Unused Reference: 'RFC4762' is defined on line 791, but no explici=
t
     reference was found in the text

Update the obsolete reference:
  ** Obsolete normative reference: RFC 4234 (Obsoleted by RFC 5234)

_______________________________________________


From rbarnes@bbn.com  Fri May 25 15:03:58 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC2BA21F859B for <gen-art@ietfa.amsl.com>; Fri, 25 May 2012 15:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7QvNn9LRD0TJ for <gen-art@ietfa.amsl.com>; Fri, 25 May 2012 15:03:53 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id B131621F85C9 for <gen-art@ietf.org>; Fri, 25 May 2012 15:03:53 -0700 (PDT)
Received: from ros-dhcp192-1-51-6.bbn.com ([192.1.51.6]:56794) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1SY2bS-000601-5P for gen-art@ietf.org; Fri, 25 May 2012 18:03:22 -0400
From: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 May 2012 18:03:52 -0400
References: <EBFB2D2E-78FF-46D6-B4FF-1F57FB8D769B@bbn.com>
To: gen-art@ietf.org
Message-Id: <B5AA25FB-945D-4888-AB7B-90F9142A65F2@bbn.com>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Subject: [Gen-art] Fwd: Gen-ART review of draft-ietf-dnsext-dnssec-bis-updates-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2012 22:03:58 -0000

Forgot to copy gen-art.

Begin forwarded message:

> From: "Richard L. Barnes" <rbarnes@bbn.com>
> Subject: Gen-ART review of draft-ietf-dnsext-dnssec-bis-updates-18
> Date: May 25, 2012 5:02:28 PM EDT
> To: IESG <iesg@ietf.org>, ietf@ietf.org
> Cc: draft-ietf-dnsext-dnssec-bis-updates@tools.ietf.org
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-dnsext-dnssec-bis-updates-18
> Reviewer: Richard Barnes
> Review Date: May-25-2012
> IETF LC End Date: Not known
> IESG Telechat date: Jan-05-2012
>=20
> Summary: Almost ready, couple of questions
>=20
> MAJOR:
>=20
> 4.1.
> It's not clear what the threat model is that this section is designed =
to address.  If the zone operator is malicious, then it can simulate the =
necessary zone cut and still prove the non-existence of records in the =
child zone. =20
>=20
> 5.10.
> I find the recommendation of the "Accept Any Success" policy =
troubling.  It deals very poorly with compromise (and other roll-over =
scenarios): Suppose there are two trust anchors, one for example.com and =
one for child.example.com.  If the private key corresponding to the TA =
for child.example.com is compromised, but the validator continues to =
trust it, this negates the benefit provided by the parent (example.com) =
facilitating a rollover.  Suggest an alternative policy, "Highest =
Signer": Out of the set of keys configured as TAs, the validator only =
uses a key as a TA (for purposes of validation) if there does not exist =
a DNSSEC path from it to any other TA.  This policy seems like more work =
to enforce (because you have to do more backward chaining), but ISTM =
that the validator should have the necessary DNSSEC records anyway, so =
it's just a matter a couple of quick checks.
>=20
>=20
>=20


From peter@akayla.com  Sat May 26 23:59:52 2012
Return-Path: <peter@akayla.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D4E921F84A0 for <gen-art@ietfa.amsl.com>; Sat, 26 May 2012 23:59:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LE9+SbGJPTxH for <gen-art@ietfa.amsl.com>; Sat, 26 May 2012 23:59:50 -0700 (PDT)
Received: from smtpauth23.prod.mesa1.secureserver.net (smtpauth23.prod.mesa1.secureserver.net [64.202.165.47]) by ietfa.amsl.com (Postfix) with SMTP id 6734421F848F for <gen-art@ietf.org>; Sat, 26 May 2012 23:59:50 -0700 (PDT)
Received: (qmail 17455 invoked from network); 27 May 2012 06:59:49 -0000
Received: from unknown (70.77.224.29) by smtpauth23.prod.mesa1.secureserver.net (64.202.165.47) with ESMTP; 27 May 2012 06:59:47 -0000
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-mile-template.all@tools.ietf.org>
Date: Sat, 26 May 2012 23:59:46 -0700
Message-ID: <01df01cd3bd6$4e62a460$eb27ed20$@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: Ac07f1lxlPP7F3TrS72lPztocaSCDg==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-mile-template-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 May 2012 06:59:52 -0000

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

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

Document: draft-ietf-mile-template-04
Reviewer: Peter Yee
Review Date: 26-May-2012
IETF LC End Date: 28-May-2012
IESG Telechat date: 07-June-2012

Summary: This draft gives guidance on creating extensions to IODEF (RFC 5070).
The document is ready for publication as an informational RFC. 

Major Issues: None

Minor Issues: None

Nits/editorial comments:
	1) There are two occurrences of the statement "Note that this list is
present as of publication time".  It might be clearer to use the word "current"
in place of "present".
	2) Section A.3, insert "section" after "This" in the third sentence.
	3) Section A.8, drop "section" in the second sentence.
	4) Regarding the example in Appendix B, RFC 6116 uses the e164.arpa
domain, not e164.int.  You'll probably want to switch to the former.



From stephen.farrell@cs.tcd.ie  Tue May 29 03:09:14 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47DAB21F87B3 for <gen-art@ietfa.amsl.com>; Tue, 29 May 2012 03:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.649
X-Spam-Level: 
X-Spam-Status: No, score=-100.649 tagged_above=-999 required=5 tests=[AWL=-0.350, BAYES_00=-2.599, MANGLED_FROM=2.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C+PP8thP9ghB for <gen-art@ietfa.amsl.com>; Tue, 29 May 2012 03:09:13 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 833D021F87A7 for <gen-art@ietf.org>; Tue, 29 May 2012 03:09:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 472DB153958; Tue, 29 May 2012 11:09:11 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1338286149; bh=MLw3bRkuBJEaiK Mkr9Kq0ynUc0xFb/SRzOn1rfNoeFk=; b=Ake1grOCPfD9sx+1cKik6yE9btK21u aj0TPDL86wxaVHETw28wwkm/THgkFrYyL39AMUgrcMDYJZIPZI+OzmoOQDbKhb7x kWeYxbAeRNl+LN3ByY3v/zlFglC/uqMu0l1i6ieNY63dMRESJZ9aOlydbenVjUi2 IlFB69Xb9v+Jcj1v3LLiwSM0v/nZlfRIPIgLDfBBKK/omA8MbVgJsuXUwk13ILlb CZ21NFmK0ouW+OYgZkHrU1SQvBstxZVD9lVifkRP6X6zuPY5pyKd4u7RdOMAMgEB eOTYvEd3AeA1UTxRZ93WXxS7Rvy0TOEUPlRXMbd0YfeDcOf80ztyc+rg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id ucEn9BBKgJ0J; Tue, 29 May 2012 11:09:09 +0100 (IST)
Received: from [IPv6:2001:770:10:203:746a:67db:b7ac:1c60] (unknown [IPv6:2001:770:10:203:746a:67db:b7ac:1c60]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id EBD0B153947; Tue, 29 May 2012 11:09:01 +0100 (IST)
Message-ID: <4FC4A03E.4000700@cs.tcd.ie>
Date: Tue, 29 May 2012 11:09:02 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: ssakane <ssakane@cisco.com>
References: <CBEA16C5.624A%ssakane@cisco.com>
In-Reply-To: <CBEA16C5.624A%ssakane@cisco.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, Jeffrey Hutzelman <jhutz@cmu.edu>, Masahiro Ishiyama <masahiro@isl.rdc.toshiba.co.jp>
Subject: Re: [Gen-art] Gen-art review of draft-sakane-dhc-dhcpv6-kdc-option-14.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2012 10:09:14 -0000

Hi,

On 05/28/2012 10:01 PM, ssakane wrote:
> All,
> 
> I have corresponded all you suggested, and made a new version of the draft.
> But, I haven't submitted it yet.
> 
> Corresponding to Alexey's review, I have merged both client operation
> and server operation into a single section: client and server operation
> in order for readers to understand the operations easily.
> And, I have improved the description of how a client gets information
> and what kind of information a server has to reply.
> 
> However, I am worry that this improvement will probably take this draft
> to the WG review phase again.
> I would like to ask from you whether my improvement was good way or not.

I'd say post the new revision and send a mail to the WG
list summarising the changes. There's no need to note
changes that are just to the layout of the text but if
there are changes to the protocol (e.g. addition of a
new MUST or something) then that's what the WG should
see. And if nobody yells, then we can go ahead.


> 
> And, I also need an input from you about 4.1. KDC discovery for a client
> because this behavior should be left to local matter.  I am thinking to
> just remove this diagram and its description.  See my response corresponding
> to Alexey's comment below.

Removing it seems fine to me, but maybe you want to
be more precise about what the administrator of the
realm MUST do here - just saying "define the method
for the client" isn't really clear, maybe say that
the administrator for the realm MUST pick one as
the preferred method for clients to use. (If that's
what you want to say.)

Jeff - if any of that is not what you prefer, please
say so, but posting the revision and moving this along
seems right to me.

Cheers,
S.

> 
> Anyway, for your help, I put the output of rfcdiff in
> 
> http://www.tanu.org/~sakane/limited/draft-sakane-dhc-dhcpv6-kdc-option-15-fr
> om-4.diff.html
> 
> Shoichi
> 
> 
> On 5/12/12 11:03 AM, "ssakane" <ssakane@cisco.com> wrote:
> 
>> Alexey,
>>
>> Thank you for your review and comments.
>>
>> Firstly, I really apologize that my response has been delayed.
>> I had some other deadlines last months.
>>
>> We totally agreed that the section 4 and 5 should be improved
>> to explain strictly the operations of both client and server.
>> Please wait for submitting new version in few weeks.
>>
>> Other responses are in-line.
>>
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>
>>> Please resolve these comments along with any other Last Call comments
>>> you may receive.
>>>
>>> Document: draft-sakane-dhc-dhcpv6-kdc-option-14.txt
>>> Reviewer: Alexey Melnikov
>>> Review Date: 23 March 2012
>>> IETF LC End Date: 23 March 2012
>>> IESG Telechat date: (if known)  -
>>>
>>> Summary: I think this document needs another revision before being ready
>>> for IESG review, although I don't think that changes are difficult.
>>>
>>>
>>> 1.  Introduction
>>>
>>>     To provide a set of IP addresses of the KDC, the Kerberos V5
>>>     specification [RFC4120] defines KDC discovery by utilizing DNS SRV
>>>     records [RFC2782].  However, systems that do not employ the DNS, but
>>>     do use DHCP, do exist, for example industrial systems.  Some
>>>     industrial systems don't use DNS because they have already had their
>>>     own name spaces and their own name resolution systems, including pre-
>>>     configured mapping tables for devices, rather than using FQDNs and
>>>     DNS.  And these systems would prefer not to employ DNS only for name
>>>     resolution because adding a new server may bring a decrease in the
>>>     reliability of the system, and increase the management cost of the
>>>     system.
>>>
>>> Minor: I am a bit doubtful about this claim, but maybe this is just me.
>>> Many systems already depend on DNS. However, I think you might be
>>> missing out on showing another reason of why your extension might be
>>> useful: it might eliminate some DNS lookups and thus can speed-up
>>> acquisition of Kerberos credentials.
>>
>> You are correct on traditional IP-based systems such as networks of
>> university, business office, and a backbone of a building.
>> There are two reasons why we proposed these options.  Firstly, these
>> options are useful for bootstrapping of the clients of the kerberos
>> system.  This is written in the 5th paragraph of section 1.
>>
>> Secondly, there are domains not designed to use thorough IP functions.
>> Those systems have own name space and own name resolution mechanism,
>> but not DNS.  The systems are typically operated in the industry,
>> or building control systems.  Some of those systems were not integrated
>> communication security, and require it as a new function.  We are thinking
>> to integrate the kerberos system into those systems as long as not
>> breaking their original specification.  There is a more information
>> in the appendix A.
>>
>>> 3.3.  Kerberos Default Realm Name Option
>>>
>>>     This option provides a default realm name of the Kerberos system.
>>>     Unlike the Kerberos Realm Name Option, it is intended for a DHCPv6
>>>     server to use, and specifies the default realm name to both clients
>>>     and Kerberos application servers in the Kerberos system.
>>>
>>> Major: Can you give me an example of when this option might be different
>>> from the Kerberos Realm Name Option (section 3.2)?
>>
>> When a client does not know the realm name that the client should belong to,
>> the Default Realm Name Option is useful to tell the name to the client.
>> The DHCP sever provides it when the client didn't specify any option.
>> The server may select a specific realm name for the client by the principal
>> name in the Principal Name option which is given by the client.
>> This option was come up with by the discussion in the WG.
>> We described it in the 1st paragraph of section 3.3:
>>
>>    This option provides a default realm name of the Kerberos system.
>>    Unlike the Kerberos Realm Name Option, it is intended for a DHCPv6
>>    server to use, and specifies the default realm name to both clients
>>    and Kerberos application servers in the Kerberos system.
>>
>> In case when a client needs to know the Kerberos information in the specific
>> realm, the client use the Kerberos Realm Name Option to tell the realm name
>> to the DHCP server.
>>
>> We are going to add more detail in section 4 and 5.
>>
>>> 3.4.  Kerberos KDC Option
>>>
>>>     This option provides a set of configuration information about a KDC.
>>>
>>>     The format of the Kerberos KDC Option is:
>>>
>>>        0                   1                   2                   3
>>>        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>        |         OPTION_KRB_KDC        |          option-len           |
>>>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>        |           Priority            |            Weight             |
>>>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>        | Transport Type|          Port Number          |               |
>>>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               |
>>>        |                                                               |
>>>        |                                                               |
>>>        |                       KDC IPv6 address        +---------------+
>>>        |                                               |               |
>>>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               :
>>>        :                                                               :
>>>        :                          realm-name                           :
>>>        :                       (variable length)                       :
>>>        :                                                               :
>>>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>
>>> Major: realm-name is not described later in this section. I think it
>>> should be removed considering that you have 2 other options for Kerberos
>>> realms already.
>>
>> The description about realm-name itself is added in section 3.4.
>> Realm Option variants are all needed.  We are going to write them
>> about the operation of each server and client into section 4 and 5
>> respectively.
>>
>>> 4.  Client Operation
>>>
>>>     When the client requires configuration parameters for a Kerberos
>>>     system while bootstrapping, the client SHOULD put the client
>>>     principal name itself into the Kerberos Principal Name Option.
>>>
>>> Minor: So this option is only ever sent from a DHCP client to a DHCP
>>> server? Section 3.1 is not clear on that.
>>
>> Yes, it is.  
>>
>>>     When the client requires specific information for a certain realm,
>>>     the client SHOULD specify the realm name in the Kerberos Realm Name
>>>     Option.
>>>
>>> Minor: This might be answering one of my questions above, but I think
>>> you should make this clear in Section 3.2.
>>
>> A DHCP client sends this option to get a set of kerberos parameters.
>> We agree with you.  We will add more detail in both section 4 and 5.
>>
>>>     When the client requires specific information related to a
>>>     certain Kerberos application server of the Kerberos system, the
>>>     client SHOULD put the principal name of the server into the Kerberos
>>>     Principal Name Option.
>>>
>>> Major: Is such dual-purpose use a good idea?
>>
>> Yes, there is no reason to separate this option.
>> From the viewpoint of the DHCP server, the server just provides a certain
>> information related to the principal name a client sent.
>> From the viewpoint of a client, the client just put a principal name
>> of which the client want to know the information related to a Kerberos
>> application server or a Kerberos application client (i.e. the client itself).
>>
>>> 4.1.  KDC discovery for a client
>>>
>>>     1) Initially, the client asks both DNS and Kerberos information to
>>>        the DHCP server.
>>>
>>> Nit: s/to/from
>>>     6) If, as the result of (1), if the client gets both DNS and Kerberos
>>>        information from the DHCP server, then the client asks Kerberos
>>>        information to the DNS server.
>>>
>>> Nit: s/to/from
>>
>> Thanks for the corrections.
>>
>>> Minor: But this (or the diagram) looks confusing to me: if the client
>>> already got both Kerberos and other information from DHCP, why should it
>>> query DNS at all? I think either your diagram is confusing, or the
>>> description below, or both.
>>
>> In the early stage of writing this document, we think the DNS method should
>> be preferred because the method was standardized already.  We wanted to avoid
>> conflict as much as possible.
>>
>> However, we have already described that it must be defined by the
>> administrator in the draft.  And, from your comments, we are shifting to
>> different mind that such behavior should be left to the administrator of
>> the system.  So, we are thinking that the diagram and its description is
>> not needed anymore.
>>
>> If you think that it is better to remove this description from
>> "When there are no criteria in the environment, and the client ..."
>> to the end of this seciton, we can remove it.  Could you suggest me ?
>>
>>> 5.  Server Operation
>>>
>>>     After the DHCPv6 server receives a message which is contained an
>>>     Option Request Option, the information the server will provide
>>>     depends on local policy.  If there are no criteria on the server, the
>>>     following operation is RECOMMENDED.
>>>
>>> Nit: It is not entirely clear to me what you mean by "no criteria" above.
>>
>> I meant it should be policy of the server's behavior.
>> We replace the word like the following.
>>
>>    After the DHCPv6 server receives a message which is contained an
>>    Option Request Option, the information the server will provide
>>    depends on local policy.  If there is no local policy on the server, the
>>    following operation is RECOMMENDED.
>>
>>> idnits reports a DownRef to RFC 6251, but this was called out during
>>> IETF LC, so no problems here.
>>
>> Again, I apologize for my response.
>>
>> Best regards,
>> Shoichi
> 

From jhutz@cmu.edu  Tue May 29 06:22:54 2012
Return-Path: <jhutz@cmu.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC6FB21F85C6 for <gen-art@ietfa.amsl.com>; Tue, 29 May 2012 06:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Z1QXQBldkKL for <gen-art@ietfa.amsl.com>; Tue, 29 May 2012 06:22:54 -0700 (PDT)
Received: from smtp03.srv.cs.cmu.edu (SMTP03.SRV.CS.CMU.EDU [128.2.217.198]) by ietfa.amsl.com (Postfix) with ESMTP id 326D221F85C3 for <gen-art@ietf.org>; Tue, 29 May 2012 06:22:54 -0700 (PDT)
Received: from [192.168.1.108] (cpe-174-100-242-113.neo.res.rr.com [174.100.242.113]) (authenticated bits=0) by smtp03.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id q4TDMh3t002245 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 29 May 2012 09:22:48 -0400 (EDT)
References: <CBEA16C5.624A%ssakane@cisco.com> <4FC4A03E.4000700@cs.tcd.ie>
User-Agent: K-9 Mail for Android
In-Reply-To: <4FC4A03E.4000700@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
From: Jeffrey Hutzelman <jhutz@cmu.edu>
Date: Tue, 29 May 2012 09:22:38 -0400
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, ssakane <ssakane@cisco.com>
Message-ID: <42af0731-e5c2-4143-a72f-6497ac5912ca@email.android.com>
X-Scanned-By: mimedefang-cmuscs on 128.2.217.198
Cc: General Area Review Team <gen-art@ietf.org>, Masahiro Ishiyama <masahiro@isl.rdc.toshiba.co.jp>
Subject: Re: [Gen-art] Gen-art review of draft-sakane-dhc-dhcpv6-kdc-option-14.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2012 13:22:54 -0000

Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:

>
>Hi,
>
>On 05/28/2012 10:01 PM, ssakane wrote:
>> All,
>> 
>> I have corresponded all you suggested, and made a new version of the
>draft.
>> But, I haven't submitted it yet.
>> 
>> Corresponding to Alexey's review, I have merged both client operation
>> and server operation into a single section: client and server
>operation
>> in order for readers to understand the operations easily.
>> And, I have improved the description of how a client gets information
>> and what kind of information a server has to reply.
>> 
>> However, I am worry that this improvement will probably take this
>draft
>> to the WG review phase again.
>> I would like to ask from you whether my improvement was good way or
>not.
>
>I'd say post the new revision and send a mail to the WG
>list summarising the changes. There's no need to note
>changes that are just to the layout of the text but if
>there are changes to the protocol (e.g. addition of a
>new MUST or something) then that's what the WG should
>see. And if nobody yells, then we can go ahead.
>
>
>> 
>> And, I also need an input from you about 4.1. KDC discovery for a
>client
>> because this behavior should be left to local matter.  I am thinking
>to
>> just remove this diagram and its description.  See my response
>corresponding
>> to Alexey's comment below.
>
>Removing it seems fine to me, but maybe you want to
>be more precise about what the administrator of the
>realm MUST do here - just saying "define the method
>for the client" isn't really clear, maybe say that
>the administrator for the realm MUST pick one as
>the preferred method for clients to use. (If that's
>what you want to say.)
>
>Jeff - if any of that is not what you prefer, please
>say so, but posting the revision and moving this along
>seems right to me.

As long as there are no changes to the protocol (bits or semantics), that seems fine.


From mahoney@nostrum.com  Tue May 29 08:39:05 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B29D221F86C5 for <gen-art@ietfa.amsl.com>; Tue, 29 May 2012 08:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IfZTDn3-YE6W for <gen-art@ietfa.amsl.com>; Tue, 29 May 2012 08:39:05 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2A18921F86B1 for <gen-art@ietf.org>; Tue, 29 May 2012 08:39:04 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([4.30.77.1]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q4TFd0r3019033 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Tue, 29 May 2012 10:39:01 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FC4ED93.9010206@nostrum.com>
Date: Tue, 29 May 2012 10:38:59 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
References: <4FBE997D.2020101@nostrum.com>
In-Reply-To: <4FBE997D.2020101@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Subject: Re: [Gen-art] A *new* batch of IETF LC reviews - 2012-05-24
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2012 15:39:05 -0000

Hi all,

The next telechat date is June 7. The date below is a typo.
https://datatracker.ietf.org/iesg/agenda/

Jean

On 5/24/12 3:26 PM, A. Jean Mahoney wrote:
> Hi all,
>
> The following reviewers have assignments:
>
> Reviewer                 LC end     Draft
>
> Alexey Melnikov        T 2012-06-06 draft-ietf-trill-rbridge-bfd-05
>
> Ben Campbell           T 2012-06-06 draft-ietf-trill-rbridge-extension-04
>
> Vijay Gurbani            2012-06-06 
> draft-ietf-nfsv4-pnfs-block-disk-protection-02
>
> Wassim Haddad            2012-06-06 draft-ietf-cdni-problem-statement-06
>
> T - on an upcoming Telechat (June 6)
>
>
> The assignments are captured in the spreadsheets:
> http://wiki.tools.ietf.org/dav/genart/gen-art.html
> http://wiki.tools.ietf.org/dav/genart/gen-art-by-reviewer.html
>
> And I have made the assignments in the review tool:
> http://art.tools.ietf.org/tools/art/genart/
>
>
> The standard template is included below.
>
> Thanks,
>
> Jean
>
> -------------------------------------------------------------------
>
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document:
> Reviewer:
> Review Date:
> IETF LC End Date:
> IESG Telechat date: (if known)
>
> Summary:
>
> Major issues:
>
> Minor issues:
>
> Nits/editorial comments:
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From bclaise@cisco.com  Tue May 29 16:14:28 2012
Return-Path: <bclaise@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3593B11E817B; Tue, 29 May 2012 16:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.499
X-Spam-Level: 
X-Spam-Status: No, score=-10.499 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CbDCCuNcQM6V; Tue, 29 May 2012 16:14:25 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 8D65911E8173; Tue, 29 May 2012 16:14:24 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4TNAkXF001703; Wed, 30 May 2012 01:10:46 +0200 (CEST)
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4TNAhH7023219; Wed, 30 May 2012 01:10:43 +0200 (CEST)
Message-ID: <4FC55773.3000803@cisco.com>
Date: Wed, 30 May 2012 01:10:43 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
References: <4f800f2f.634cb40a.13a1.ffff8003@mx.google.com> <4FBC219D.8070000@cisco.com> <4fbc8e3b.2968b40a.5c9a.4414@mx.google.com>
In-Reply-To: <4fbc8e3b.2968b40a.5c9a.4414@mx.google.com>
Content-Type: multipart/alternative; boundary="------------060607070404000601010907"
Cc: me <bclaise@cisco.com>, gen-art@ietf.org, 'IETF' <ietf@ietf.org>, draft-claise-export-application-info-in-ipfix.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-claise-export-application-info-in-ipfix-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2012 23:14:28 -0000

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

Hi Roni,

[keeping only the open discussions]
>
> Hi Benoit,
>
> Thanks, see in-line
>
> Roni
>
> I am the assigned Gen-ART reviewer for this draft. For background on 
> Gen-ART, please see the FAQ at 
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments 
> you may receive.
>
> Document: draft-claise-export-application-info-in-ipfix-05
>
> Reviewer: Roni Even
>
> Review Date:2012--4--7
>
> IETF LC End Date: 2012--4--17
>
> IESG Telechat date:
>
> Summary: This draft is almost ready for publication as an 
> Informational RFC.
>
> Major issues:
>
> Minor issues:
>
> In sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to information 
> in Cisco web page. I could not locate and information that is 
> referenced. The link is to the main Cisco web page. For example in 
> section 6.5 it lists the selectorID as 10000, where is this value located?
>
> The exact URsL are 
> http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html
> and 
> http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html
> As you can see from the URLs, there is a chance that those might change.
> Stephen Farrell had the same comment.
>
> RE: My concern was that going to Cisco web page I tried to search for 
> the information using the search window and could not find it so I 
> think that this link is not helpful for finding the information.
>
Understood. We propose
1. to remove all references to [CISCO] in the draft, except in the appendix
2. to add the following text

             Appendix X (non normative)

       A reference to the Cisco Systems assigned numbers for the Application Id and
       the different attribute assignments can be found at [CISCO  <http://tools.ietf.org/html/draft-claise-export-application-info-in-ipfix-07#ref-CISCO>].

       [CISCO-APPLICATION-REGISTRY] http://www.cisco.com/go/application-registry
  

3. However, it will take a couple of days to set up this new URL. So we 
propose to add

             RFC-EDITOR NOTE: at the time of publication, if the 
[CISCO-APPLICATION-REGISTRY] is not available,
             this appendix must be removed

Does it work for you?

>
>
> In section 7 I noticed that "p2pTechnology, tunnelTechnology, and 
> encryptedTechnology" are already assigned in the IANA IPFIX 
> Information elements so why assign them again as new?
>
> from RFC5102:
>
>     The value of these identifiers is in the range of 1-32767.  Within
>     this range, Information Element identifier values in the sub-range of
>     1-127 are compatible with field types used by NetFlow version 9
>     [RFC3954  <http://tools.ietf.org/html/rfc3954>].
>   
>
> So basically, if Cisco has assigned those numbers already, they can 
> reused in IANA.
>
> RE: The question is if you want the existing assignment to be used 
> without change than why have this information in the IANA 
> consideration in the first place.
>
Because the IANA registry currently contain "reserved for the 
corresponding IEs
See "100-127 Reserved" at http://www.iana.org/assignments/ipfix/ipfix.xml
>
>
>
> In section 7 I noticed that you request that the  
> applicationDescription, applicationId, applicationName, 
> classificationEngineId will receive elementid values from the range 
> 0-127. My reading from section 4.2 is this is not required, maybe add 
> text that will explain this request.
>
> See my previous remark.
>
> RE:  OK, even though it should be clear that this applies to these 
> specific selectors since you want them to be compatible with NetFlow 
> version 9 and it is not a general request for using specific sub range 
> for all selectors.
>
>
>
> Nits/editorial comments:
>
> 1.In section 4.1 last sentence what is the meaning of "by theses 
> specifications" , I did not understand the context.
>
> 2.In section 6.6 "to determine whether or the default HTTP port" 
> delete the "or"
>
> In section 6.6 "The Classification Engine ID is 2" should be "3".
>
All corrected in to-be-posted-version.

Regards, Benoit.
>
>
> will be corrected.
>
> Thanks again.
>
> Regards, Benoit.
>


--------------060607070404000601010907
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">
    Hi Roni,<br>
    <br>
    [keeping only the open discussions]<br>
    <blockquote cite="mid:4fbc8e3b.2968b40a.5c9a.4414@mx.google.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	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";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;
	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;}
span.EmailStyle19
	{mso-style-type:personal;
	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: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.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1032532832;
	mso-list-type:hybrid;
	mso-list-template-ids:-209704826 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1347488741;
	mso-list-type:hybrid;
	mso-list-template-ids:-636856504 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="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="color:#1F497D">Hi Benoit,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Thanks, see
            in-line<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Roni<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div style="border-width: medium medium medium 1.5pt;
          border-style: none none none solid; border-color:
          -moz-use-text-color -moz-use-text-color -moz-use-text-color
          blue; -moz-border-top-colors: none; -moz-border-right-colors:
          none; -moz-border-bottom-colors: none;
          -moz-border-left-colors: none; -moz-border-image: none;
          padding: 0in 0in 0in 4pt;">
          <p class="MsoNormal">I am the assigned Gen-ART reviewer for
            this draft. For background on Gen-ART, please see the FAQ at
            &lt;<a moz-do-not-send="true"
              href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
              target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
          <p class="MsoNormal">&nbsp;<o:p></o:p></p>
          <p class="MsoNormal">Please resolve these comments along with
            any other Last Call comments you may receive.<o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Document:
              draft-claise-export-application-info-in-ipfix-05</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Reviewer:
              Roni Even</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Review
              Date:2012&#8211;4&#8211;7</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IETF
              LC End Date: 2012&#8211;4&#8211;17</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IESG
              Telechat date:</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary:
              This draft is almost ready for publication as an
              Informational RFC.</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Major
              issues:</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Minor
              issues:</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to
              information in Cisco web page. I could not locate and
              information that is referenced. The link is to the main
              Cisco web page. For example in section 6.5 it lists the
              selectorID as 10000, where is this value located?</span><o:p></o:p></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;">The exact URsL are <a
                moz-do-not-send="true"
href="http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html">http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html</a><br>
              and <a moz-do-not-send="true"
href="http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html">http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html</a><br>
              As you can see from the URLs, there is a chance that those
              might change.<br>
              Stephen Farrell had the same comment. </span><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal" style="margin-bottom: 0.0001pt;
            line-height: normal;"><span style="color: rgb(31, 73, 125);">RE:
              My concern was that going to Cisco web page I tried to
              search for the information using the search window and
              could not find it so I think that this link is not helpful
              for finding the information.</span></p>
        </div>
      </div>
    </blockquote>
    Understood. We propose <br>
    1. to remove all references to [CISCO] in the draft, except in the
    appendix<br>
    2. to add the following text<br>
    &nbsp;&nbsp;&nbsp; <br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Appendix X (non normative)<br>
    <br>
    <pre class="newpage">      A reference to the Cisco Systems assigned numbers for the Application Id and
      the different attribute assignments can be found at [<a href="http://tools.ietf.org/html/draft-claise-export-application-info-in-ipfix-07#ref-CISCO">CISCO</a>].

      [CISCO-APPLICATION-REGISTRY] <a class="moz-txt-link-freetext" href="http://www.cisco.com/go/application-registry">http://www.cisco.com/go/application-registry</a>
&nbsp;</pre>
    3. However, it will take a couple of days to set up this new URL. So
    we propose to add<br>
    <br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; RFC-EDITOR NOTE: at the time of publication, if the
    [CISCO-APPLICATION-REGISTRY] is not available, <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this appendix must be removed<br>
    <br>
    Does it work for you?<br>
    <br>
    <blockquote cite="mid:4fbc8e3b.2968b40a.5c9a.4414@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <div style="border-width: medium medium medium 1.5pt;
          border-style: none none none solid; border-color:
          -moz-use-text-color -moz-use-text-color -moz-use-text-color
          blue; -moz-border-top-colors: none; -moz-border-right-colors:
          none; -moz-border-bottom-colors: none;
          -moz-border-left-colors: none; -moz-border-image: none;
          padding: 0in 0in 0in 4pt;">
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              section 7 I noticed that &#8221;p2pTechnology, tunnelTechnology,
              and encryptedTechnology&#8221; are already assigned in the IANA
              IPFIX Information elements so why assign them again as
              new?</span><o:p></o:p></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;">from RFC5102:<o:p></o:p></span></p>
          <pre>&nbsp;&nbsp; The value of these identifiers is in the range of 1-32767.&nbsp; Within<o:p></o:p></pre>
          <pre>&nbsp;&nbsp; this range, Information Element identifier values in the sub-range of<o:p></o:p></pre>
          <pre>&nbsp;&nbsp; 1-127 are compatible with field types used by NetFlow version 9<o:p></o:p></pre>
          <pre>&nbsp;&nbsp; [<a moz-do-not-send="true" href="http://tools.ietf.org/html/rfc3954" title="&quot;Cisco Systems NetFlow Services Export Version 9&quot;">RFC3954</a>].<o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;">So basically, if Cisco has
              assigned those numbers already, they can reused in IANA.</span><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal" style="margin-bottom: 0.0001pt;
            line-height: normal;"><span style="color: rgb(31, 73, 125);">RE:
              The question is if you want the existing assignment to be
              used without change than why have this information in the
              IANA consideration in the first place. </span></p>
        </div>
      </div>
    </blockquote>
    Because the IANA registry currently contain "reserved for the
    corresponding IEs<br>
    See "100-127 Reserved" at
    <a class="moz-txt-link-freetext" href="http://www.iana.org/assignments/ipfix/ipfix.xml">http://www.iana.org/assignments/ipfix/ipfix.xml</a>
    <blockquote cite="mid:4fbc8e3b.2968b40a.5c9a.4414@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <div style="border-width: medium medium medium 1.5pt;
          border-style: none none none solid; border-color:
          -moz-use-text-color -moz-use-text-color -moz-use-text-color
          blue; -moz-border-top-colors: none; -moz-border-right-colors:
          none; -moz-border-bottom-colors: none;
          -moz-border-left-colors: none; -moz-border-image: none;
          padding: 0in 0in 0in 4pt;">
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D">&nbsp;<o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              section 7 I noticed that you request that the&nbsp;
              applicationDescription, applicationId, applicationName,
              classificationEngineId will receive elementid values from
              the range 0-127. My reading from section 4.2 is this is
              not required, maybe add text that will explain this
              request.</span><o:p></o:p></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;">See my previous remark.</span><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;color:#1F497D"> <o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D">RE: &nbsp;OK, even though it should be
              clear that this applies to these specific selectors since
              you want them to be compatible with NetFlow version 9 and
              it is not a general request for using specific sub range
              for all selectors.<o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              <br>
              <o:p></o:p></span></p>
          <span style="color:#1F497D"><o:p></o:p></span>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Nits/editorial
              comments:</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in;mso-list:l0
            level1 lfo4"><!--[if !supportLists]--><span
              style="mso-list:Ignore">1.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp; </span></span><!--[endif]--><span
              dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              section 4.1 last sentence what is the meaning of &#8220;by
              theses specifications&#8221; , I did not understand the context.</span><o:p></o:p></p>
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in;mso-list:l0
            level1 lfo4"><!--[if !supportLists]--><span
              style="mso-list:Ignore">2.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp; </span></span><!--[endif]--><span
              dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              section 6.6 &#8220;to determine whether or the default HTTP
              port&#8221; delete the &#8220;or&#8221;</span><o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left: 0.5in;
            text-indent: -0.25in;"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              section 6.6 &#8220;The Classification Engine ID is 2&#8221; should be
              &#8220;3&#8221;.</span></p>
        </div>
      </div>
    </blockquote>
    All corrected in to-be-posted-version.<br>
    <br>
    Regards, Benoit.<br>
    <blockquote cite="mid:4fbc8e3b.2968b40a.5c9a.4414@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in"><o:p></o:p></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              will be corrected.<br>
              <br>
              Thanks again.<br>
              <br>
              Regards, Benoit.<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal">&nbsp;<o:p></o:p></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------060607070404000601010907--

From ron.even.tlv@gmail.com  Tue May 29 21:36:55 2012
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FECB21F8673; Tue, 29 May 2012 21:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.444
X-Spam-Level: 
X-Spam-Status: No, score=-3.444 tagged_above=-999 required=5 tests=[AWL=0.154,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aZQfe3VFadkg; Tue, 29 May 2012 21:36:46 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id E968C11E80C7; Tue, 29 May 2012 21:36:44 -0700 (PDT)
Received: by wibhn6 with SMTP id hn6so2737826wib.13 for <multiple recipients>; Tue, 29 May 2012 21:36:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=5br74H5zE59Y29A6PxRb5bPP8qXRxrPaG/ImXFvabfo=; b=akrhoAgJPq+XMzr+t15JUDuJdo5eI4WPecwqzzM/CRziR7ALORu6Idxs98d71KIB2z L93NpugzHaDzHLeyTaWAwwuEPaASHgNO7JvXGPdMrYZ2pc2f2QK5ev6XgqlYDmvNNYzX EfwgGHLX6IzlT8nVlLzVsVSyINGMbU4oBoyd3t7yrOtyBviPaZWu9u5G0p6T4PHqu6CX gvWIn+K+RuvrWM/Go4xChoD8YUClB6EeYTGIkYVLshDcUSLyc7iqvcjbrsH+dPcvRERV BJYVA7icCq5z1y5OjfTwmeDEvZklYEVAFUNA/9uH3Wd3LnxgpLFUhL2w+DTOcbWnOPuY sVTw==
Received: by 10.216.143.148 with SMTP id l20mr9909939wej.115.1338352603969; Tue, 29 May 2012 21:36:43 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-177-198-116.red.bezeqint.net. [79.177.198.116]) by mx.google.com with ESMTPS id f19sm52415571wiw.11.2012.05.29.21.36.40 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 May 2012 21:36:41 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Benoit Claise'" <bclaise@cisco.com>
References: <4f800f2f.634cb40a.13a1.ffff8003@mx.google.com> <4FBC219D.8070000@cisco.com> <4fbc8e3b.2968b40a.5c9a.4414@mx.google.com> <4FC55773.3000803@cisco.com>
In-Reply-To: <4FC55773.3000803@cisco.com>
Date: Wed, 30 May 2012 07:34:27 +0300
Message-ID: <4fc5a3d9.f34bb40a.71e1.4c87@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0034_01CD3E36.A698F2D0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac098EkDfcSzloutTp2WdvYu0WEgvAALR5bw
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>, draft-claise-export-application-info-in-ipfix.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART LC review of draft-claise-export-application-info-in-ipfix-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2012 04:36:55 -0000

This is a multi-part message in MIME format.

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

Hi Benoit,

Your proposals are OK with me

Roni

 

From: Benoit Claise [mailto:bclaise@cisco.com] 
Sent: Wednesday, May 30, 2012 2:11 AM
To: Roni Even
Cc: draft-claise-export-application-info-in-ipfix.all@tools.ietf.org;
gen-art@ietf.org; 'IETF'; me
Subject: Re: Gen-ART LC review of
draft-claise-export-application-info-in-ipfix-05

 

Hi Roni,

[keeping only the open discussions]



Hi Benoit,

Thanks, see in-line

Roni

 

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

 

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

 

Document: draft-claise-export-application-info-in-ipfix-05

Reviewer: Roni Even

Review Date:2012-4-7

IETF LC End Date: 2012-4-17

IESG Telechat date:

 

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

 

Major issues:

 

Minor issues:

 

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

The exact URsL are
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/pre
sentation_c96-629396.html
and
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/pro
duct_bulletin_c25-627831.html
As you can see from the URLs, there is a chance that those might change.
Stephen Farrell had the same comment. 

 

RE: My concern was that going to Cisco web page I tried to search for the
information using the search window and could not find it so I think that
this link is not helpful for finding the information.

Understood. We propose 
1. to remove all references to [CISCO] in the draft, except in the appendix
2. to add the following text
    
            Appendix X (non normative)

      A reference to the Cisco Systems assigned numbers for the Application
Id and
      the different attribute assignments can be found at [CISCO
<http://tools.ietf.org/html/draft-claise-export-application-info-in-ipfix-07
#ref-CISCO> ].
 
      [CISCO-APPLICATION-REGISTRY]
http://www.cisco.com/go/application-registry
 

3. However, it will take a couple of days to set up this new URL. So we
propose to add

            RFC-EDITOR NOTE: at the time of publication, if the
[CISCO-APPLICATION-REGISTRY] is not available, 
            this appendix must be removed

Does it work for you?









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

from RFC5102:

   The value of these identifiers is in the range of 1-32767.  Within
   this range, Information Element identifier values in the sub-range of
   1-127 are compatible with field types used by NetFlow version 9
   [RFC3954 <http://tools.ietf.org/html/rfc3954> ].
 

So basically, if Cisco has assigned those numbers already, they can reused
in IANA.

 

RE: The question is if you want the existing assignment to be used without
change than why have this information in the IANA consideration in the first
place. 

Because the IANA registry currently contain "reserved for the corresponding
IEs
See "100-127 Reserved" at http://www.iana.org/assignments/ipfix/ipfix.xml 

 






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

See my previous remark. 

 

RE:  OK, even though it should be clear that this applies to these specific
selectors since you want them to be compatible with NetFlow version 9 and it
is not a general request for using specific sub range for all selectors.






 

Nits/editorial comments:

 

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

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

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

All corrected in to-be-posted-version.

Regards, Benoit.




will be corrected.

Thanks again.

Regards, Benoit.




 

 

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Times New Roman \, serif";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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";
	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";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;
	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.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1032532832;
	mso-list-type:hybrid;
	mso-list-template-ids:-209704826 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
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 bgcolor=3Dwhite =
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Hi =
Benoit,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Your proposals are OK with =
me<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'> Benoit Claise [mailto:bclaise@cisco.com] <br><b>Sent:</b> =
Wednesday, May 30, 2012 2:11 AM<br><b>To:</b> Roni Even<br><b>Cc:</b> =
draft-claise-export-application-info-in-ipfix.all@tools.ietf.org; =
gen-art@ietf.org; 'IETF'; me<br><b>Subject:</b> Re: Gen-ART LC review of =
draft-claise-export-application-info-in-ipfix-05<o:p></o:p></span></p></d=
iv></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Hi Roni,<br><br>[keeping only the open =
discussions]<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Benoit,</span><o:p></o:p></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Thanks, see =
in-line</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div =
style=3D'border:none;border-left:solid windowtext 1.5pt;padding:0in 0in =
0in 4.0pt;border-color:-moz-use-text-color -moz-use-text-color =
-moz-use-text-color&#13;&#10;          blue;-moz-border-top-colors: =
none;-moz-border-right-colors:
          none;-moz-border-bottom-colors: none;-moz-border-left-colors: =
none;-moz-border-image: none'><p class=3DMsoNormal>I am the assigned =
Gen-ART reviewer for this draft. For background on Gen-ART, please see =
the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
draft-claise-export-application-info-in-ipfix-05</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;4&#8211;7</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;4&#8211;17</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as an Informational =
RFC.</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In =
sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to information in =
Cisco web page. I could not locate and information that is referenced. =
The link is to the main Cisco web page. For example in section 6.5 it =
lists the selectorID as 10000, where is this value =
located?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'>The exact URsL are <a =
href=3D"http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555=
/ps6601/presentation_c96-629396.html">http://www.cisco.com/en/US/prod/col=
lateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html</a><br=
>and <a =
href=3D"http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558=
/ps6616/product_bulletin_c25-627831.html">http://www.cisco.com/en/US/prod=
/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.htm=
l</a><br>As you can see from the URLs, there is a chance that those =
might change.<br>Stephen Farrell had the same comment. =
</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: My concern was that going to Cisco web =
page I tried to search for the information using the search window and =
could not find it so I think that this link is not helpful for finding =
the information.</span><o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt;line-height:normal'><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Understood. We propose <br>1. to remove all references =
to [CISCO] in the draft, except in the appendix<br>2. to add the =
following text<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Appendix X (non =
normative)<o:p></o:p></span></p><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A =
reference to the Cisco Systems assigned numbers for the Application Id =
and<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the different =
attribute assignments can be found at [<a =
href=3D"http://tools.ietf.org/html/draft-claise-export-application-info-i=
n-ipfix-07#ref-CISCO">CISCO</a>].<o:p></o:p></pre><pre><o:p>&nbsp;</o:p><=
/pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [CISCO-APPLICATION-REGISTRY] <a =
href=3D"http://www.cisco.com/go/application-registry">http://www.cisco.co=
m/go/application-registry</a><o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre=
><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>3. =
However, it will take a couple of days to set up this new URL. So we =
propose to add<br><br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; RFC-EDITOR NOTE: at the time of publication, if the =
[CISCO-APPLICATION-REGISTRY] is not available, =
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
this appendix must be removed<br><br>Does it work for =
you?<br><br><br><o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid windowtext 1.5pt;padding:0in 0in =
0in 4.0pt'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'><br><br><br></span><o:p></o:p></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
7 I noticed that &#8221;p2pTechnology, tunnelTechnology, and =
encryptedTechnology&#8221; are already assigned in the IANA IPFIX =
Information elements so why assign them again as =
new?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'>from RFC5102:</span><o:p></o:p></p><pre>&nbsp;&nbsp; The =
value of these identifiers is in the range of 1-32767.&nbsp; =
Within<o:p></o:p></pre><pre>&nbsp;&nbsp; this range, Information Element =
identifier values in the sub-range of<o:p></o:p></pre><pre>&nbsp;&nbsp; =
1-127 are compatible with field types used by NetFlow version =
9<o:p></o:p></pre><pre>&nbsp;&nbsp; [<a =
href=3D"http://tools.ietf.org/html/rfc3954" title=3D"&quot;Cisco Systems =
NetFlow Services Export Version =
9&quot;">RFC3954</a>].<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'>So basically, if Cisco has assigned those numbers =
already, they can reused in IANA.</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: The question is if you want the existing =
assignment to be used without change than why have this information in =
the IANA consideration in the first place. =
</span><o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Because the IANA registry currently contain =
&quot;reserved for the corresponding IEs<br>See &quot;100-127 =
Reserved&quot; at <a =
href=3D"http://www.iana.org/assignments/ipfix/ipfix.xml">http://www.iana.=
org/assignments/ipfix/ipfix.xml</a> <o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid windowtext 1.5pt;padding:0in 0in =
0in 4.0pt;border-color:-moz-use-text-color -moz-use-text-color =
-moz-use-text-color&#13;&#10;          blue;-moz-border-top-colors: =
none;-moz-border-right-colors:
          none;-moz-border-bottom-colors: none;-moz-border-left-colors: =
none;-moz-border-image: none'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'><br><br><br></span><o:p></o:p></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
7 I noticed that you request that the&nbsp; applicationDescription, =
applicationId, applicationName, classificationEngineId will receive =
elementid values from the range 0-127. My reading from section 4.2 is =
this is not required, maybe add text that will explain this =
request.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'>See my previous remark.</span><span =
style=3D'font-size:12.0pt'> </span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: &nbsp;OK, even though it should be clear =
that this applies to these specific selectors since you want them to be =
compatible with NetFlow version 9 and it is not a general request for =
using specific sub range for all selectors.</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'><br><br><br></span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
4.1 last sentence what is the meaning of &#8220;by theses =
specifications&#8221; , I did not understand the =
context.</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>2.<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 =
6.6 &#8220;to determine whether or the default HTTP port&#8221; delete =
the &#8220;or&#8221;</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
6.6 &#8220;The Classification Engine ID is 2&#8221; should be =
&#8220;3&#8221;.</span><o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>All =
corrected in to-be-posted-version.<br><br>Regards, =
Benoit.<br><br><o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'><br>will be corrected.<br><br>Thanks =
again.<br><br>Regards, Benoit.<br><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'>&nbsp;</span><o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_0034_01CD3E36.A698F2D0--


From janardhan.iyengar@fandm.edu  Tue May 29 19:12:33 2012
Return-Path: <janardhan.iyengar@fandm.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1C8B11E8136 for <gen-art@ietfa.amsl.com>; Tue, 29 May 2012 19:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hj9S5cgO5j6K for <gen-art@ietfa.amsl.com>; Tue, 29 May 2012 19:12:33 -0700 (PDT)
Received: from spammy3.fandm.edu (spammy3.fandm.edu [155.68.1.26]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF9A11E811D for <gen-art@ietf.org>; Tue, 29 May 2012 19:12:33 -0700 (PDT)
X-ASG-Debug-ID: 1338343133-0313f20a6fc8d830001-nPVVhF
Received: from zimfe2.fandm.edu (smtp.fandm.edu [155.68.130.30]) by spammy3.fandm.edu with ESMTP id XGit0gCsN3qmvWPc; Tue, 29 May 2012 21:58:53 -0400 (EDT)
X-Barracuda-Envelope-From: janardhan.iyengar@fandm.edu
X-Barracuda-Apparent-Source-IP: 155.68.130.30
Received: from 247-212-246-103.static.youbroadband.in (unknown [103.246.212.247]) by zimfe2.fandm.edu (Postfix) with ESMTPSA id 81F8F116A55C; Tue, 29 May 2012 21:58:51 -0400 (EDT)
Message-ID: <4FC4A4CF.3080404@fandm.edu>
Date: Tue, 29 May 2012 06:28:31 -0400
From: Jana Iyengar <janardhan.iyengar@fandm.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Wassim Haddad <wassim.haddad@ericsson.com>
References: <7C1F64FA-2589-47DD-9AB3-71B850D20AA9@ericsson.com>
X-ASG-Orig-Subj: Re: [Gen-art] Gen-ART review of draft-ietf-ledbat-congestion-09
In-Reply-To: <7C1F64FA-2589-47DD-9AB3-71B850D20AA9@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Barracuda-Connect: smtp.fandm.edu[155.68.130.30]
X-Barracuda-Start-Time: 1338343133
X-Barracuda-URL: http://155.68.1.26:80/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at fandm.edu
X-Barracuda-Spam-Score: 0.81
X-Barracuda-Spam-Status: No, SCORE=0.81 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=6.0 KILL_LEVEL=7.1 tests=DATE_IN_PAST_12_24, DATE_IN_PAST_12_24_2
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.98393 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.01 DATE_IN_PAST_12_24 Date: is 12 to 24 hours before Received: date 0.80 DATE_IN_PAST_12_24_2   DATE_IN_PAST_12_24_2
X-Mailman-Approved-At: Wed, 30 May 2012 00:05:03 -0700
Cc: draft-ietf-ledbat-congestion.all@tools.ietf.org, Gen-art <gen-art@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ledbat-congestion-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2012 02:12:33 -0000

Hi Wassim,

On 5/24/12 1:48 AM, Wassim Haddad wrote:
> Summary: The document is ready for publication as an experimental RFC.
>
> Major Issues: None
> Minor Issues: None

Thank you!

- jana

From miguel.a.garcia@ericsson.com  Wed May 30 01:19:47 2012
Return-Path: <miguel.a.garcia@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EAEA21F86F7 for <gen-art@ietfa.amsl.com>; Wed, 30 May 2012 01:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level: 
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1wSbSSEE-2Sq for <gen-art@ietfa.amsl.com>; Wed, 30 May 2012 01:19:46 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id DE84721F86FC for <gen-art@ietf.org>; Wed, 30 May 2012 01:19:45 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fc66d000006fdc-75-4fc5d8208e9a
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 2D.CA.28636.028D5CF4; Wed, 30 May 2012 10:19:44 +0200 (CEST)
Received: from [159.107.24.205] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.264.0; Wed, 30 May 2012 10:19:44 +0200
Message-ID: <4FC5D81E.6000409@ericsson.com>
Date: Wed, 30 May 2012 10:19:42 +0200
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>, jakob@kirei.se
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrALMWRmVeSWpSXmKPExsUyM+Jvra7CjaP+BteXylhcffWZxeLS/H4W i5blLha31n9htZi+9xq7xeFjl5kc2DzWdl9l81iy5CeTx6Nrz9g9bt/4w+6x6fIdRo/Ps68y B7BFcdmkpOZklqUW6dslcGXsmPGdvWA3W8W1RvMGxpWsXYycHBICJhLXDzezQNhiEhfurWfr YuTiEBI4xShx+tdcdghnDaNE95JNjCBVvALaEm9PNLOB2CwCqhKfVn0A62YTMJdo3biRHcQW FQiWmNd9kwWiXlDi5MwnYLaIgIXEva1tLCBDmQWWMUpMbd8GNlRYwEriSuM6sJOYBWwlLsy5 zgJhy0tsfzuHGcQWEtCUmHxzKfMERv5ZSObOQtIyC0nLAkbmVYzCuYmZOenlhnqpRZnJxcX5 eXrFqZsYgaF8cMtv3R2Mp86JHGKU5mBREuflStrvLySQnliSmp2aWpBaFF9UmpNafIiRiYNT qoFRMfLVr7mp/31XHgwsaJ1p+PqLft0K326e/s27l92PvWrEFff+f9SDggpL9iMh/5U6IxZk 6lqfVdshfkgsWMLCY3rsiWttHvfadVVfrfl5Ouj5lXKNIxl/Hd6nBajnrzocdU5r+bIHwRph Eic3N10ujDlvrvDs4YLGZ0cF1WTDE/5vSD3M1flBiaU4I9FQi7moOBEAZs/VWDMCAAA=
Cc: Ondrej Sury <ondrej.sury@nic.cz>, Warren Kumari <warren@kumari.net>, General Area Review Team <gen-art@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: [Gen-art] Gen-ART review of draft-ietf-dane-protocol-21.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2012 08:19:47 -0000

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft. For background on Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

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

Document: draft-ietf-dane-protocol-21.txt
Reviewer: Miguel Garcia <Miguel.A.Garcia@ericsson.com>
Review Date: 20121-05-30
IETF LC End Date: 2012-05-31
IESG Telechat date: 2012-06-07

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

Major issues: none

Minor issues: none

Nits/editorial comments:

I previously reviewed version -19. I have now verified the changes from 
-19 to -21, and the document is correct. I have no further comments.

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

From Francis.Dupont@fdupont.fr  Wed May 30 05:59:28 2012
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6408D21F863D for <gen-art@ietfa.amsl.com>; Wed, 30 May 2012 05:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0LlT1FY1iZj for <gen-art@ietfa.amsl.com>; Wed, 30 May 2012 05:59:28 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id A6A2921F8573 for <gen-art@ietf.org>; Wed, 30 May 2012 05:59:27 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id q4UCxPNL040225; Wed, 30 May 2012 14:59:25 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201205301259.q4UCxPNL040225@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: gen-art@ietf.org
Date: Wed, 30 May 2012 14:59:25 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: draft-ietf-appsawg-media-type-regs.all@tools.ietf.org
Subject: [Gen-art] review of draft-ietf-appsawg-media-type-regs-10.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2012 12:59: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-appsawg-media-type-regs-10.txt
Reviewer: Francis Dupont
Review Date: 20120523
IETF LC End Date: 20120521
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:
 - ToC page 3: Acknowledgements -> Acknowledgments

 - 4.2.5 page 12: missing "." in:
  understood by implementors The
                            ^

 - 4.6 page 17: servies -> services

 - 7 page 26: suffx -> suffix

 - 8 page 27: Registions -> Registrations
  and mutiple -> multiple

 - 9 page 27: Acknowledgements -> Acknowledgments
 
Regards

Francis.Dupont@fdupont.fr

PS: I want to signal the high quality of this document, for instance I got the idea to check
where the types are case-insensitive and I found it in 10 seconds from the printed version
(i.e., no grep :-)!

From mahoney@nostrum.com  Thu May 31 12:50:54 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0185F21F859E for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 12:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dxrIUdIJdHla for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 12:50:52 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC9121F850F for <gen-art@ietf.org>; Thu, 31 May 2012 12:50:50 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local ([4.30.77.1]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q4VJonIS097048 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 31 May 2012 14:50:50 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FC7CB99.50701@nostrum.com>
Date: Thu, 31 May 2012 14:50:49 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Subject: [Gen-art] A *new* batch of IETF LC reviews - 2012-05-31
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 19:50:54 -0000

Hi all,

The following reviewers have assignments:

Reviewer              LC end      Draft

Brian Carpenter       2012-06-09  draft-ietf-spfbis-experiment-09

Christer Holmberg   T 2012-06-08  draft-ietf-mif-dns-server-selection-09

Francis Dupont        2012-06-12  
draft-ietf-v6ops-ra-guard-implementation-04

Joel Halpern          2012-06-12  draft-ietf-krb-wg-kdc-model-12

Meral Shirazipour     2012-06-12  draft-ietf-grow-simple-va-08

Miguel Garcia         2012-06-12  draft-ietf-pim-ecmp-03

Peter McCann          2012-06-12  draft-ietf-pim-pop-count-06

Roni Even             2012-06-13  draft-ietf-nea-pt-tls-05

Suresh Krishnan       2012-06-27  draft-hoffman-tao4677bis-15

Vijay Gurbani         2012-06-14  
draft-ietf-xrblock-rtcp-xr-meas-identity-06

Wassim Haddad         2012-06-14  draft-ietf-intarea-ipv4-id-update-05


T - on an upcoming Telechat (June 21)


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

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


The standard template is included below.

Thanks,

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From vkg@bell-labs.com  Thu May 31 13:16:19 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1009421F844E for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 13:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.599
X-Spam-Level: 
X-Spam-Status: No, score=-107.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIZh55K+gAUn for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 13:16:18 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 6229921F8570 for <gen-art@ietf.org>; Thu, 31 May 2012 13:16:18 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q4VKG9F4017686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 31 May 2012 15:16:10 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q4VKG8gf026602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 31 May 2012 15:16:08 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q4VKG7Om011073; Thu, 31 May 2012 15:16:07 -0500 (CDT)
Message-ID: <4FC7D2D2.9060008@bell-labs.com>
Date: Thu, 31 May 2012 15:21:38 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: draft-ietf-xrblock-rtcp-xr-meas-identity@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.10
Cc: Shida Schubert <shida@ntt-at.com>, General Area Review Team <gen-art@ietf.org>, eckelcu@cisco.com, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 20:16: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 resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-xrblock-rtcp-xr-meas-identity-06
Reviewer: Vijay K. Gurbani
Review Date: May-31-2012
IETF LC End Date: June-14-2012
IESG Telechat date: Not known

Summary: This draft is ready as a Proposed Standard; it has one minor
comment that should be fixed before publication.

Major: 0
Minor: 1
Nits: 0

Minor:

- In S6, the text says that "... the use of security mechanisms with
  RTP, as documented in Section 9 of [RFC3550] SHOULD apply."

  I am puzzled by the normative language here.  Won't it be more proper
  to simply say that "... the use of security mechanisms with RTP, as
  documented in Section 9 of [RFC3550] apply."

  The use of SHOULD seem to indicate that there are certain cases
  during measurement reporting where the security considerations do not
  apply.  Surely you do not mean that, do you?

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From eckelcu@cisco.com  Thu May 31 13:51:53 2012
Return-Path: <eckelcu@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A1CB11E8074 for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 13:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.513
X-Spam-Level: 
X-Spam-Status: No, score=-10.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PcjN2JjmPndX for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 13:51:53 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 16A9111E8072 for <gen-art@ietf.org>; Thu, 31 May 2012 13:51:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=2128; q=dns/txt; s=iport; t=1338497513; x=1339707113; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=M2NdYdQyKl8a8tUcUNpZNz4THwzjax5GZeHElf6ztVA=; b=IyTArcjTKFRu/l3h7eRaIm5pKGSLbuX5rnsZz0eBvjSYPrNhksX3/32d Rtj4DTZe1L+66AGm+x+CfCuRIvEXDhkO5R+k8gwvNVlk3RQidE9fWlYlx Cwh+JOZDuiMsJEOV8i7duQCaRGrlmZ5LsrhetGwULC5yUFM9JdIEjdkL0 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHbZx0+rRDoH/2dsb2JhbAA7CbQVgQeCGAEBAQQSAR0KPwwEAgEIEQMBAQELBhcBBgFFCQgBAQQBEggBGYdoAQuZAZ9TixERCYRMYAOIQI1njH6BZoMAgT8
X-IronPort-AV: E=Sophos;i="4.75,693,1330905600"; d="scan'208";a="44602507"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 31 May 2012 20:51:53 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q4VKpqYH010350; Thu, 31 May 2012 20:51:52 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 31 May 2012 13:51:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 31 May 2012 13:51:51 -0700
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C07386A45@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <4FC7D2D2.9060008@bell-labs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
Thread-Index: Ac0/ajpu7gQIXgg0Q5SXaGSE6vtsLgABJjHw
References: <4FC7D2D2.9060008@bell-labs.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>, <draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org>
X-OriginalArrivalTime: 31 May 2012 20:51:52.0585 (UTC) FILETIME=[34F2A790:01CD3F6F]
X-Mailman-Approved-At: Thu, 31 May 2012 13:52:59 -0700
Cc: Shida Schubert <shida@ntt-at.com>, General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 20:51:53 -0000

Hi Vijay,

Thank you for your review. I agree with your comment. It was actually
one of the WGLC comments:
http://www.ietf.org/mail-archive/web/xrblock/current/msg00395.html

This comment in particular seems to have fallen through the cracks.
Thanks for catching it.

Cheers,
Charles

> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@bell-labs.com]
> Sent: Thursday, May 31, 2012 1:22 PM
> To: draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org
> Cc: General Area Review Team; Charles Eckel (eckelcu); Shida Schubert;
> Gonzalo Camarillo
> Subject: Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-xrblock-rtcp-xr-meas-identity-06
> Reviewer: Vijay K. Gurbani
> Review Date: May-31-2012
> IETF LC End Date: June-14-2012
> IESG Telechat date: Not known
>=20
> Summary: This draft is ready as a Proposed Standard; it has one minor
> comment that should be fixed before publication.
>=20
> Major: 0
> Minor: 1
> Nits: 0
>=20
> Minor:
>=20
> - In S6, the text says that "... the use of security mechanisms with
>   RTP, as documented in Section 9 of [RFC3550] SHOULD apply."
>=20
>   I am puzzled by the normative language here.  Won't it be more
proper
>   to simply say that "... the use of security mechanisms with RTP, as
>   documented in Section 9 of [RFC3550] apply."
>=20
>   The use of SHOULD seem to indicate that there are certain cases
>   during measurement reporting where the security considerations do
not
>   apply.  Surely you do not mean that, do you?
>=20
> Thanks,
>=20
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web:   http://ect.bell-labs.com/who/vkg/

From jmh@joelhalpern.com  Thu May 31 14:10:52 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE97321F855B for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 14:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.252
X-Spam-Level: 
X-Spam-Status: No, score=-102.252 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2l1ZcLnuvx7T for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 14:10:52 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 5B89C21F8559 for <gen-art@ietf.org>; Thu, 31 May 2012 14:10:52 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 409E255827D for <gen-art@ietf.org>; Thu, 31 May 2012 14:10:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 0D99B1BD163A; Thu, 31 May 2012 14:10:52 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.110] (pool-71-161-51-118.clppva.btas.verizon.net [71.161.51.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 4C1641BD1661; Thu, 31 May 2012 14:10:51 -0700 (PDT)
Message-ID: <4FC7DE46.3070505@joelhalpern.com>
Date: Thu, 31 May 2012 17:10:30 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
References: <4FC7CB99.50701@nostrum.com>
In-Reply-To: <4FC7CB99.50701@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: [Gen-art]  Review: draft-ietf-krb-wg-kdc-model-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 21:10:53 -0000

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

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

Document: draft-ietf-krb-wg-kdc-model-12
     An information model for Kerberos version 5
Reviewer: Joel M. Halpern
Review Date: 31-May-2012
IETF LC End Date: 12-June-2012
IESG Telechat date: (if known)

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

Major issues: None.

Minor issues:
     ID-Nits reports the uage of "MUST not" isntead of "MUST NOT", and 
it claims this is wrong.

Nits/editorial comments:

From mahoney@nostrum.com  Thu May 31 14:33:01 2012
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 488EB21F8644 for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 14:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ixnqyaLDLXn6 for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 14:33:00 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6B2BD21F863D for <gen-art@ietf.org>; Thu, 31 May 2012 14:33:00 -0700 (PDT)
Received: from A-Jean-Mahoneys-MacBook-Pro.local (pool-173-74-105-72.dllstx.fios.verizon.net [173.74.105.72]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q4VLWuYG002418 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <gen-art@ietf.org>; Thu, 31 May 2012 16:32:56 -0500 (CDT) (envelope-from mahoney@nostrum.com)
Message-ID: <4FC7E387.5090605@nostrum.com>
Date: Thu, 31 May 2012 16:32:55 -0500
From: "A. Jean Mahoney" <mahoney@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: gen-art@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.74.105.72 is authenticated by a trusted mechanism)
Subject: [Gen-art] Assignments for the 2012-06-07 telechat
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 21:33:01 -0000

Hi all,

The following reviewers have assignments:

Reviewer                 LC end     Draft

Alexey Melnikov         2012-06-06  draft-ietf-trill-rbridge-bfd-05

Ben Campbell            2012-06-06  draft-ietf-trill-rbridge-extension-04

Elwyn Davies            2012-05-10  draft-ietf-codec-opus-14 *

Joel Halpern            2012-04-16  draft-ietf-manet-nhdp-mib-13 **

Kathleen Moriarty       2012-05-25  draft-ietf-dccp-udpencap-10 **

Martin Thomson          2012-05-30  draft-ietf-tcpm-tcpmss-04 **

Mary Barnes             2012-05-29  draft-ietf-mpls-ldp-gtsm-07

Miguel Garcia           2012-05-31  draft-ietf-dane-protocol-21 **

Peter Yee               2012-05-30  draft-ietf-mile-template-04 **

Richard Barnes          2012-05-02  draft-ietf-appsawg-about-uri-scheme-05
Richard Barnes          2012-05-31  
draft-ietf-dnsext-dnssec-bis-updates-18 **

Suresh Krishnan         2012-05-30  draft-ietf-mile-iodef-xmlreg-01


* Earlier draft reviewed
** Already reviewed


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

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

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

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

Jean

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

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

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

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

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

From ben@nostrum.com  Thu May 31 15:08:17 2012
Return-Path: <ben@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 717CE21F866B; Thu, 31 May 2012 15:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.45
X-Spam-Level: 
X-Spam-Status: No, score=-101.45 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3, SPF_PASS=-0.001,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1tq+XpNl1WUY; Thu, 31 May 2012 15:08:16 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id A0F9B21F8665; Thu, 31 May 2012 15:08:16 -0700 (PDT)
Received: from [10.0.1.33] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q4VM8FgH004192 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 31 May 2012 17:08:15 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 31 May 2012 17:08:14 -0500
Message-Id: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com>
To: draft-ietf-trill-rbridge-extension.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
Subject: [Gen-art] Gen-ART LC/Telechat review of draft-ietf-trill-rbridge-extension-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 22:08:17 -0000

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

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

Document: draft-ietf-trill-rbridge-extension-04
Reviewer: Ben Campbell
Review Date: 2012-05-31
IETF LC End Date: 2012-06-07
IESG Telechat date: 2012-06-07

Note: Since this draft is on the agenda of the IESG Telechat on the same =
day that the IETF last call expires, this review is intended for both =
purposes.

Summary:=20

This draft is almost ready for publication as a proposed standard, but I =
have some clarification questions and comments that should be considered =
prior to publication.

Major issues:

None

Minor issues:

-- section 2, general:

Do the authors assume that all TRILL extensions will follow this spec? =
Since RFC6325 already specifies an extension mechanism, what stops an =
extension from ignoring this spec and doing something different? Does it =
hurt if they do?

-- section 2, 3rd paragraph from end: "Non-critical extensions can be =
safely ignored."

Is that intended to be normative? (Seems like it should be, since =
behavior for critical extensions is normative).

-- section 2.1, 1st paragraph, last sentence:

Redundant with normative language in previous section.


-- section 2.3, first paragraph:=20

Is the first sentence intended as normative?

-- section 6, last paragraph:

No security implications of this are mentioned. Is it really a security =
consideration?

Also, is this more likely to be set incorrectly than all the other =
things that some implementation might screw up, so that it warrants =
special treatment?


Nits/editorial comments:

-- section 1:=20

Please expand TRILL on first mention in the body of the document (i.e. =
not just in the Abstract.)

-- section 2:

Please expand RBridge and IS-IS on first mention.

-- section 2, bullet list, 2nd bullet: " ... which would only =
necessarily affect the RBridge(s) where a TRILL frame is decapsulated"

Does that mean it always affects the decapsulating RBridge but might =
effect transit RBridges as well?=20

-- section 2, first paragraph after bullet list: "critical hop-by-hop =
extension"

I assume this means an extension with the critical flag set? If so, it =
would be more precise to say that.

-- sectio 2.1, 1st paragraph:

I'm a little confused by a citation for "future documents". Do you mean =
the cited document as an example of something that might do this (in =
which case a "for example" would help), or do you mean to say that =
document will do this?

-- section 2.2, 1st paragraph:

Please expand PDU on first mention.

-- section 2.3, first paragraph:=20

s/modifictions/modifications

-- section 5:

Since section 3 is entirely composed of the referenced table, and seems =
to exist mostly if not entirely for the purpose of this reference, why =
not just move the table to the IANA considerations section.



From bill.wu@huawei.com  Thu May 31 18:33:52 2012
Return-Path: <bill.wu@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A618D11E80CE for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 18:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.52
X-Spam-Level: 
X-Spam-Status: No, score=-4.52 tagged_above=-999 required=5 tests=[AWL=0.326,  BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hdBJuhV8Rlwf for <gen-art@ietfa.amsl.com>; Thu, 31 May 2012 18:33:51 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id AD2EB11E8080 for <gen-art@ietf.org>; Thu, 31 May 2012 18:33:51 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGT17080; Thu, 31 May 2012 21:33:51 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 31 May 2012 18:29:32 -0700
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 31 May 2012 18:29:38 -0700
Received: from w53375 (10.138.41.149) by szxeml410-hub.china.huawei.com (10.82.67.137) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 1 Jun 2012 09:27:35 +0800
Message-ID: <A0778DDE5E0445E0AEAA5A21A523D53A@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Vijay K. Gurbani" <vkg@bell-labs.com>, <draft-ietf-xrblock-rtcp-xr-meas-identity@tools.ietf.org>
References: <4FC7D2D2.9060008@bell-labs.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C07386A45@xmb-sjc-234.amer.cisco.com>
Date: Fri, 1 Jun 2012 09:27:32 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
Cc: Shida Schubert <shida@ntt-at.com>, General Area Review Team <gen-art@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-xrblock-rtcp-xr-meas-identity-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 01:33:52 -0000

QWdyZWUsIFRoYW5rcyENCg0KUmVnYXJkcyENCi1RaW4NCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2Ug
LS0tLS0gDQpGcm9tOiAiQ2hhcmxlcyBFY2tlbCAoZWNrZWxjdSkiIDxlY2tlbGN1QGNpc2NvLmNv
bT4NClRvOiAiVmlqYXkgSy4gR3VyYmFuaSIgPHZrZ0BiZWxsLWxhYnMuY29tPjsgPGRyYWZ0LWll
dGYteHJibG9jay1ydGNwLXhyLW1lYXMtaWRlbnRpdHlAdG9vbHMuaWV0Zi5vcmc+DQpDYzogIkdl
bmVyYWwgQXJlYSBSZXZpZXcgVGVhbSIgPGdlbi1hcnRAaWV0Zi5vcmc+OyAiU2hpZGEgU2NodWJl
cnQiIDxzaGlkYUBudHQtYXQuY29tPjsgIkdvbnphbG8gQ2FtYXJpbGxvIiA8Z29uemFsby5jYW1h
cmlsbG9AZXJpY3Nzb24uY29tPg0KU2VudDogRnJpZGF5LCBKdW5lIDAxLCAyMDEyIDQ6NTEgQU0N
ClN1YmplY3Q6IFJFOiBHZW4tQVJUIHJldmlldyBvZiBkcmFmdC1pZXRmLXhyYmxvY2stcnRjcC14
ci1tZWFzLWlkZW50aXR5LTA2DQoNCg0KSGkgVmlqYXksDQoNClRoYW5rIHlvdSBmb3IgeW91ciBy
ZXZpZXcuIEkgYWdyZWUgd2l0aCB5b3VyIGNvbW1lbnQuIEl0IHdhcyBhY3R1YWxseQ0Kb25lIG9m
IHRoZSBXR0xDIGNvbW1lbnRzOg0KaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2Vi
L3hyYmxvY2svY3VycmVudC9tc2cwMDM5NS5odG1sDQoNClRoaXMgY29tbWVudCBpbiBwYXJ0aWN1
bGFyIHNlZW1zIHRvIGhhdmUgZmFsbGVuIHRocm91Z2ggdGhlIGNyYWNrcy4NClRoYW5rcyBmb3Ig
Y2F0Y2hpbmcgaXQuDQoNCkNoZWVycywNCkNoYXJsZXMNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPiBGcm9tOiBWaWpheSBLLiBHdXJiYW5pIFttYWlsdG86dmtnQGJlbGwtbGFicy5j
b21dDQo+IFNlbnQ6IFRodXJzZGF5LCBNYXkgMzEsIDIwMTIgMToyMiBQTQ0KPiBUbzogZHJhZnQt
aWV0Zi14cmJsb2NrLXJ0Y3AteHItbWVhcy1pZGVudGl0eUB0b29scy5pZXRmLm9yZw0KPiBDYzog
R2VuZXJhbCBBcmVhIFJldmlldyBUZWFtOyBDaGFybGVzIEVja2VsIChlY2tlbGN1KTsgU2hpZGEg
U2NodWJlcnQ7DQo+IEdvbnphbG8gQ2FtYXJpbGxvDQo+IFN1YmplY3Q6IEdlbi1BUlQgcmV2aWV3
IG9mIGRyYWZ0LWlldGYteHJibG9jay1ydGNwLXhyLW1lYXMtaWRlbnRpdHktMDYNCj4gDQo+IEkg
YW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZvciBiYWNr
Z3JvdW5kIG9uDQo+IEdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPiA8aHR0cDovL3dp
a2kudG9vbHMuaWV0Zi5vcmcvYXJlYS9nZW4vdHJhYy93aWtpL0dlbkFydGZhcT4uDQo+IA0KPiBQ
bGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBMYXN0IENh
bGwgY29tbWVudHMNCj4geW91IG1heSByZWNlaXZlLg0KPiANCj4gRG9jdW1lbnQ6IGRyYWZ0LWll
dGYteHJibG9jay1ydGNwLXhyLW1lYXMtaWRlbnRpdHktMDYNCj4gUmV2aWV3ZXI6IFZpamF5IEsu
IEd1cmJhbmkNCj4gUmV2aWV3IERhdGU6IE1heS0zMS0yMDEyDQo+IElFVEYgTEMgRW5kIERhdGU6
IEp1bmUtMTQtMjAxMg0KPiBJRVNHIFRlbGVjaGF0IGRhdGU6IE5vdCBrbm93bg0KPiANCj4gU3Vt
bWFyeTogVGhpcyBkcmFmdCBpcyByZWFkeSBhcyBhIFByb3Bvc2VkIFN0YW5kYXJkOyBpdCBoYXMg
b25lIG1pbm9yDQo+IGNvbW1lbnQgdGhhdCBzaG91bGQgYmUgZml4ZWQgYmVmb3JlIHB1YmxpY2F0
aW9uLg0KPiANCj4gTWFqb3I6IDANCj4gTWlub3I6IDENCj4gTml0czogMA0KPiANCj4gTWlub3I6
DQo+IA0KPiAtIEluIFM2LCB0aGUgdGV4dCBzYXlzIHRoYXQgIi4uLiB0aGUgdXNlIG9mIHNlY3Vy
aXR5IG1lY2hhbmlzbXMgd2l0aA0KPiAgIFJUUCwgYXMgZG9jdW1lbnRlZCBpbiBTZWN0aW9uIDkg
b2YgW1JGQzM1NTBdIFNIT1VMRCBhcHBseS4iDQo+IA0KPiAgIEkgYW0gcHV6emxlZCBieSB0aGUg
bm9ybWF0aXZlIGxhbmd1YWdlIGhlcmUuICBXb24ndCBpdCBiZSBtb3JlDQpwcm9wZXINCj4gICB0
byBzaW1wbHkgc2F5IHRoYXQgIi4uLiB0aGUgdXNlIG9mIHNlY3VyaXR5IG1lY2hhbmlzbXMgd2l0
aCBSVFAsIGFzDQo+ICAgZG9jdW1lbnRlZCBpbiBTZWN0aW9uIDkgb2YgW1JGQzM1NTBdIGFwcGx5
LiINCj4gDQo+ICAgVGhlIHVzZSBvZiBTSE9VTEQgc2VlbSB0byBpbmRpY2F0ZSB0aGF0IHRoZXJl
IGFyZSBjZXJ0YWluIGNhc2VzDQo+ICAgZHVyaW5nIG1lYXN1cmVtZW50IHJlcG9ydGluZyB3aGVy
ZSB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgZG8NCm5vdA0KPiAgIGFwcGx5LiAgU3VyZWx5
IHlvdSBkbyBub3QgbWVhbiB0aGF0LCBkbyB5b3U/DQo+IA0KPiBUaGFua3MsDQo+IA0KPiAtIHZp
amF5DQo+IC0tDQo+IFZpamF5IEsuIEd1cmJhbmksIEJlbGwgTGFib3JhdG9yaWVzLCBBbGNhdGVs
LUx1Y2VudA0KPiAxOTYwIEx1Y2VudCBMYW5lLCBSbS4gOUMtNTMzLCBOYXBlcnZpbGxlLCBJbGxp
bm9pcyA2MDU2MyAoVVNBKQ0KPiBFbWFpbDogdmtnQHtiZWxsLWxhYnMuY29tLGFjbS5vcmd9IC8g
dmlqYXkuZ3VyYmFuaUBhbGNhdGVsLWx1Y2VudC5jb20NCj4gV2ViOiAgIGh0dHA6Ly9lY3QuYmVs
bC1sYWJzLmNvbS93aG8vdmtnLw==

