Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.txt

Colin Perkins <csp@csperkins.org> Tue, 11 December 2012 22:26 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5086121F862B for <xrblock@ietfa.amsl.com>; Tue, 11 Dec 2012 14:26:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.974
X-Spam-Level:
X-Spam-Status: No, score=-105.974 tagged_above=-999 required=5 tests=[AWL=0.625, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KmEO-yoLQWGy for <xrblock@ietfa.amsl.com>; Tue, 11 Dec 2012 14:26:57 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [93.93.130.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8703721F8625 for <xrblock@ietf.org>; Tue, 11 Dec 2012 14:26:57 -0800 (PST)
Received: from [217.108.124.185] (helo=[10.5.0.232]) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1TiYHv-0008Pk-HD; Tue, 11 Dec 2012 22:26:56 +0000
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA024844@AZ-FFEXMB04.global.avaya.com>
Date: Tue, 11 Dec 2012 23:26:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6DC0D5A8-E781-4584-BA7A-38EC6F9134AA@csperkins.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA024844@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1283)
X-BlackCat-Spam-Score: -20
X-Mythic-Debug: Threshold = On =
Cc: "xrblock@ietf.org" <xrblock@ietf.org>
Subject: Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 11 Dec 2012 22:26:58 -0000

On 29 Nov 2012, at 13:51, Romascanu, Dan (Dan) wrote:
> This is a Working Group Last Call for http://www.ietf.org/id/draft-ietf-xrblock-rtcp-xr-jb-02.txt.  
> 
> Please read and review this document, and send your comments, questions and concerns to the WG list before December 13, 2012. If you have no comments and you believe that the document is ready for submission to the IESG as a Standards Track document please send a short message as well to help us in determining the level of review and consensus. 


This looks to be in good shape. One minor comment: why is SHOULD used for the value to report if over-range or unknown values are received, rather than MUST?

Also, one question: there are many reserved values for the jb cfg. Do we need to define how new values are to be registered in an IANA Registry, or is the assumption that this draft is revised if new values are needed?

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