Re: [xrblock] Tags and SSRC's in XR Blocks
Varun Singh <vsingh.ietf@gmail.com> Fri, 18 November 2011 10:24 UTC
Return-Path: <vsingh.ietf@gmail.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 BBE6F21F8888 for <xrblock@ietfa.amsl.com>; Fri, 18 Nov 2011 02:24:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.687
X-Spam-Level:
X-Spam-Status: No, score=-2.687 tagged_above=-999 required=5 tests=[AWL=0.911, 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 HRXAU7uj+9lI for <xrblock@ietfa.amsl.com>; Fri, 18 Nov 2011 02:24:30 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 77DDB21F869E for <xrblock@ietf.org>; Fri, 18 Nov 2011 02:24:30 -0800 (PST)
Received: by faap16 with SMTP id p16so6234947faa.31 for <xrblock@ietf.org>; Fri, 18 Nov 2011 02:24:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=bSTJxFW3ZLlvZjlu89yZOMCuDUIWR9amvewlmUUmFNU=; b=W6QRdc3mFztuvkyzPQ7wekRLzwYG2nLomgRIYW6XyJJlcCtlIysuOylOkhzAye4i5c BL3PV2UuMoJann+UUbRDa97CnUBmVATilCEzOnDREw/1bRnH+SdMFmoNVslyAxU/SctE kQ9jkAC1ih83Dbf5pg1XMSG7MDcii8zrkL5e8=
Received: by 10.205.133.4 with SMTP id hw4mr2644386bkc.91.1321611868204; Fri, 18 Nov 2011 02:24:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.62.17 with HTTP; Fri, 18 Nov 2011 02:24:07 -0800 (PST)
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05CC2F8C@xmb-sjc-234.amer.cisco.com>
References: <CAE897BC.3DAAF%alan.d.clark@telchemy.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05CC2F8C@xmb-sjc-234.amer.cisco.com>
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Fri, 18 Nov 2011 18:24:07 +0800
Message-ID: <CAEbPqrx_HGC3ZxQ4tnJZHdF7N7MLC4hRnh4ZOqpqP0SVY1c7Zg@mail.gmail.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Content-Type: multipart/alternative; boundary="000e0cdfcd04ef6ed804b1ffbd95"
Cc: xrblock@ietf.org
Subject: Re: [xrblock] Tags and SSRC's in XR Blocks
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: Fri, 18 Nov 2011 10:24:34 -0000
Hi Alan, draft-clark-xrblock-rtcp-xr-qoe-00 has a 6-bit tag while the Measurement ID block defines it as a 3-bit identifier. In draft-ietf-avt-rtcp-xr-meas-identity-02#section-2: there is a 0 bit, is this done so that the Tag field aligns across blocks? if so then there should be 2 zero bits to cover for the new I field. Also in the measurement identity draft: Bits shown as '0' in the figure SHOULD be set to zero. SHOULD be MUST? Cheers, Varun On Fri, Nov 18, 2011 at 12:57, Charles Eckel (eckelcu) <eckelcu@cisco.com>wrote: > Hi Alan, > > As this issue concerns the monarch draft as well as the measurement > identification block draft, it was discussed on both the avtcore and > xrblock lists: > > http://proxy2974.my-addr.net/myaddrproxy.php/http/www.ietf.org/mail-arch > ive/web/avt/current/msg14582.html > and > http://proxy2974.my-addr.net/myaddrproxy.php/http/www.ietf.org/mail-arch > ive/web/avt/current/msg14658.html > > The decision at that time was to remove the tag and rely on the SSRC. > The thread speaks to point (i) you raised. It does not speak to point > (ii). > Point (ii) was raised during the xrblock working group session with > week, and one of the action items for the measurement identification > draft was to clarify the intended usage of the measurement identity > block in such cases. > > Cheers, > Charles > > > -----Original Message----- > > From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On > Behalf Of Alan Clark > > Sent: Wednesday, November 16, 2011 11:27 AM > > To: xrblock@ietf.org > > Subject: [xrblock] Tags and SSRC's in XR Blocks > > > > > > The original concept for the XR blocks used the idea of a Tag to > relate the metrics blocks to a > > measurement identification block. This approach was used for a number > of reasons: > > > > (i) It is more efficient as the Source SSRC, which is already in the > measurement identification block, > > does not have to be repeated for every metrics block. As some of the > metrics blocks are only 3-4 > > words in size, the redundant SSRC increases the message size by > 25-30%. > > > > (ii) It provides more flexibility in the organization of metrics > blocks into RTCP packets - allowing > > either one RTCP packet to contain several sets of measurement data or > allowing one set of measurement > > data to be carried over several RTCP packets. > > > > I'm not sure why the Tag was removed - was there some good technical > reason for this? > > > > Alan > > _______________________________________________ > xrblock mailing list > xrblock@ietf.org > https://www.ietf.org/mailman/listinfo/xrblock > -- http://www.netlab.tkk.fi/~varun/
- [xrblock] Tags and SSRC's in XR Blocks Alan Clark
- Re: [xrblock] Tags and SSRC's in XR Blocks Charles Eckel (eckelcu)
- Re: [xrblock] Tags and SSRC's in XR Blocks Varun Singh
- Re: [xrblock] Tags and SSRC's in XR Blocks Varun Singh
- Re: [xrblock] Tags and SSRC's in XR Blocks Qin Wu