[xrblock] Open issue- identity info repetition in draft-ietf-avtcore-monarch
Qin Wu <sunseawq@huawei.com> Mon, 09 May 2011 08:08 UTC
Return-Path: <sunseawq@huawei.com>
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 D4154E07C2; Mon, 9 May 2011 01:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.069
X-Spam-Level:
X-Spam-Status: No, score=-5.069 tagged_above=-999 required=5 tests=[AWL=1.374, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156]
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 AGOhkwECNy2a; Mon, 9 May 2011 01:08:04 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 9E974E06F4; Mon, 9 May 2011 01:08:03 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKX00B0X54PEC@szxga03-in.huawei.com>; Mon, 09 May 2011 16:05:13 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKX00IJ654P07@szxga03-in.huawei.com>; Mon, 09 May 2011 16:05:13 +0800 (CST)
Received: from w53375 ([10.138.41.70]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LKX00GTC54PSL@szxml04-in.huawei.com>; Mon, 09 May 2011 16:05:13 +0800 (CST)
Date: Mon, 09 May 2011 16:08:51 +0800
From: Qin Wu <sunseawq@huawei.com>
To: avt@ietf.org, xrblock@ietf.org
Message-id: <05e001cc0e20$5525ba60$46298a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
Content-type: multipart/alternative; boundary="Boundary_(ID_TQJUNBu71w4rw48bTcrxxg)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [xrblock] Open issue- identity info repetition in draft-ietf-avtcore-monarch
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: Mon, 09 May 2011 08:08:05 -0000
In the last IETF meeting, there was discussion on identity info repetition or dupplication. However it was not clear whether new packet type for identity block is needed. Here is some clarification and prososal from my point of view. In the example figure 2 of section 5.2 in drat-ietf-avtcore-monarch, it is assumed there is an RTCP XR packet containing four metrics blocks, reporting on streams from two source. each source is associated with two meric block. In order to reduce overhead to carry duplicated data for all the metric block contained in the same RTCP XR packet, it was proposed by draft-ietf-avtcore-monarch that measurement identity information should be separated from metric block and form independent block. However this proposal save zero octets in figure 2. So the question is whether an identity block is actually needed if identity information only contain SSRC of stream souce, or if just stacking multiple XR Blocks is acceptable. However I re-check with RTCP XR Report Block for Measurement Identity defined in draft-ietf-avt-rtcp-xr-meas-identity-02, identity information included is more than SSRC of stream source. So it should be useful to define new packet type for identity block. However the example figure 2(i.e., only contain SSRC of stream souce) is actually not consistent with report block format defined in draft-ietf-avt-rtcp-xr-meas-identity-02(i.e., contain more than SSRC of stream source). Also as we know, identity block work has just started from XRBlock WG, Therefore I suggest that the example (Figure 2, and the related discussion) is removed until the identity block is clearly defined in XRBLock. Any Comments or suggestion? Regards! -Qin
- [xrblock] Open issue- identity info repetition in… Qin Wu
- Re: [xrblock] [AVTCORE] Open issue- identity info… Qin Wu
- Re: [xrblock] [AVTCORE] Open issue- identity info… Colin Perkins
- Re: [xrblock] [AVTCORE] Open issue- identity info… Qin Wu
- Re: [xrblock] [AVTCORE] Open issue- identity info… Colin Perkins
- Re: [xrblock] [AVTCORE] Open issue- identity info… Christian Groves
- Re: [xrblock] [AVTCORE] Open issue- identity info… Colin Perkins
- Re: [xrblock] [AVTCORE] Open issue- identity info… Qin Wu