[xrblock] AD evaluation: draft-ietf-xrblock-rtcp-xr-video-lc-05

Alissa Cooper <alissa@cooperw.in> Fri, 20 November 2015 18:24 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F70B1B3C2F for <xrblock@ietfa.amsl.com>; Fri, 20 Nov 2015 10:24:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UKJLbyPOAA1f for <xrblock@ietfa.amsl.com>; Fri, 20 Nov 2015 10:24:21 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE8A71B3C2E for <xrblock@ietf.org>; Fri, 20 Nov 2015 10:24:21 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 1AC00205FC for <xrblock@ietf.org>; Fri, 20 Nov 2015 13:24:21 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 20 Nov 2015 13:24:21 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h= content-type:date:from:message-id:mime-version:subject:to :x-sasl-enc:x-sasl-enc; s=mesmtp; bh=blLai2J9zFZX52PZ1nEB79cjRPw =; b=ezcgKSPCdBz8SOJwCkXa1rdwMfvrTM7boT9G08AoNRV4be4L8Lbg+3VM7fk KyTg5TJrv6rSoCdMc0fnt3hcCCdjKQUjnlBGCMNPZgAiisJ6nyLCCaW7cNt6MH3S NAI1cx2rGcBupxba3x+ghH0JR/shZjwsPFxsgou8dOzPaI7Q=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=bl Lai2J9zFZX52PZ1nEB79cjRPw=; b=oP+1Enq7b3IFDnmV+iZLEXEkhBCIvLjIYO hQSZTWUkmCk3y6U+B/tOR0N//lzF4kK9HZtVthIDw2EelEtcMqlurfXF6e6XZ55S Wz4ONwfLDNo8cOOWDgBl+tsODzLmJoA3EQBCQcoO2IsEk/BBMUhAzu2f1K2Ot+6T hAzu+QvZQ=
X-Sasl-enc: 2J6HyKXx3WelEdjrROcunCF8C39BbtOwIOlh1HZ+CMWj 1448043860
Received: from dhcp-171-68-20-162.cisco.com (dhcp-171-68-20-162.cisco.com [171.68.20.162]) by mail.messagingengine.com (Postfix) with ESMTPA id 96D556800EF for <xrblock@ietf.org>; Fri, 20 Nov 2015 13:24:20 -0500 (EST)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_07B1BD6E-689C-48F0-B004-650F24902826"
Message-Id: <E2E2286B-F59F-4183-8AF5-429FBA54B76E@cooperw.in>
Date: Fri, 20 Nov 2015 10:24:19 -0800
To: xrblock@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/AZYnSp6ofdjK2QWdG2Hr5hQYKlk>
Subject: [xrblock] AD evaluation: draft-ietf-xrblock-rtcp-xr-video-lc-05
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xrblock/>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Nov 2015 18:24:23 -0000

I have reviewed this document in preparation for IETF LC. I believe the document is in good shape and is ready for LC. I’ve noted below some nits that should be fixed together with any LC comments received.

Thanks,
Alissa

== Sec 1.3 ==

"These metrics are applicable to video applications the video
   component of Audio/Video applications using RTP and applying packet
   loss concealment mechanisms which are incorporated into the receiving
   endpoint to mitigate the impact of network impairments on QoE."

There is a grammar problem with this sentence. Please fix.

s/Set Top Boxes/set top boxes/

== Sec 3 ==

s/as follow/as follows/

s/information.There/information. There/

s/methods slightly different/methods to be slightly different/

s/Thus, In this document/Thus, in this document/

== Sec 5.2 ==

s/unilateral parameter/unilateral parameters/

== Sec 6 ==

OLD
Implementers
   SHOULD consider the guidance in [RFC7202] for using appropriate
   security mechanisms, i.e., where security is a concern, the
   implementation SHOULD apply encryption and authentication to the
   report block.
   
NEW
Implementers
   should consider the guidance in [RFC7202] for using appropriate
   security mechanisms. Where security is a concern, the
   implementation SHOULD apply encryption and authentication to the
   report block.

(No need for normative directives about how to read other specs.)

== Sec 7.3 ==

OLD
RAI Area Directors

   rai-ads@tools.ietf.org

NEW
ART Area Directors

   art-ads@tools.ietf.org <mailto:art-ads@tools.ietf.org>