Re: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-qoe

Colin Perkins <csp@csperkins.org> Tue, 27 August 2013 22:11 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 6BC4F21E8099 for <xrblock@ietfa.amsl.com>; Tue, 27 Aug 2013 15:11:43 -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=[AWL=0.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 leIK5KhYXk0z for <xrblock@ietfa.amsl.com>; Tue, 27 Aug 2013 15:11:38 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [93.93.131.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2570311E839C for <xrblock@ietf.org>; Tue, 27 Aug 2013 15:11:38 -0700 (PDT)
Received: from [81.187.2.149] (port=46118 helo=[192.168.0.14]) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1VERU2-00010f-6i; Tue, 27 Aug 2013 23:11:30 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA43BD5D99@nkgeml501-mbs.china.huawei.com>
Date: Tue, 27 Aug 2013 23:11:30 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E282BCD2-3853-4FA3-B1DA-673F97EACF12@csperkins.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA128B4B0F@AZ-FFEXMB04.global.avaya.com> <13143CA8-0B70-4F2E-86AD-FE29CDDBB2CB@csperkins.org> <B8F9A780D330094D99AF023C5877DABA43BD5D99@nkgeml501-mbs.china.huawei.com>
To: Qin Wu <bill.wu@huawei.com>
X-Mailer: Apple Mail (2.1508)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Cc: "xrblock@ietf.org" <xrblock@ietf.org>
Subject: Re: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-qoe
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, 27 Aug 2013 22:11:43 -0000

Qin,

Thank you, most of this looks good. I just one comment:

On 27 Aug 2013, at 02:51, Qin Wu <bill.wu@huawei.com> wrote:
...
> Section 3.2.1 says "For RTP sessions where multiple payload formats can be negotiated or the payload format changes during the mid-session), the value of this field will be used to indicate what payload format was in use for the reporting interval", but doesn't the payload type indicate this whether or not multiple payload formats are used in the session?
> 
> [Qin]:Yes it indicates multiple payload format can be used in one RTP session or in RTP sessions. 
> So I propose the following change:
> OLD TEXT:
> "
> MoS Metrics reporting depends on the payload format in use.  This
> field identifies the format of the RTP payload.  For RTP session
> where multiple payload formats can be negotiated or the payload
> format changes during the mid-session), the value of this field
> will be used to indicate what payload format was in use for the
> reporting interval.
> "
> NEW TEXT:
> "
> MoS Metrics reporting depends on the payload format in use.  This
> field identifies the format of the RTP payload.  For RTP session(s)
> where multiple payload formats can be negotiated or the payload
> format changes during the mid-session), the value of this field
> will be used to indicate what payload format was in use for the
> reporting interval.
> "
> Let me know if this addresses your comment.


I don't think this is correct. A better new text might be something like:

"MoS Metrics reporting depends on the payload format in use.  This
field identifies the RTP payload type in use during the reporting interval. The binding between RTP payload types and RTP payload formats is configured via a signalling protocol, for example an SDP offer/answer exchange. If the RTP payload type used is changed during an RTP session, separate reports SHOULD be sent for each RTP payload type, with corresponding measurement information blocks indicating the time period to which they relate"

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