Re: [AVTCORE] [xrblock] Fw: I-D Action: draft-ietf-avtcore-monarch-02.txt

Peter Musgrave <musgravepj@gmail.com> Wed, 15 June 2011 12:41 UTC

Return-Path: <musgravepj@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C3D721F84FB; Wed, 15 Jun 2011 05:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.045
X-Spam-Level:
X-Spam-Status: No, score=-3.045 tagged_above=-999 required=5 tests=[AWL=0.553, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 VGOG2nKkP8IH; Wed, 15 Jun 2011 05:41:24 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id DC42F21F84F8; Wed, 15 Jun 2011 05:41:23 -0700 (PDT)
Received: by fxm15 with SMTP id 15so426666fxm.31 for <multiple recipients>; Wed, 15 Jun 2011 05:41:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=f60UB0zSm6EWNFns8OFxYA/GQ4LlBxLoDGkWmy3FOYA=; b=hOevUO9nxFqB75rdDpOVaQbqH7ABQeU2P6455yYovmWmSnz9+AIqXkdaNKLpLURe1m IHzl1aASOSL56k8ArAyOkkoe2V4wO5nku8G/2B9b0h9pPjM74DgywbWgkRrnquQyTfSL QACcjx6YHJ2fjh40sLWOeW68tDnKbBfDOdi2Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Xd7R4dr+HmQwPVQxjhN2+DnaIgYCN1QhmAfJHmkcLlZbxmcUsvgCI89zrfGlf29Xjh vpP4ZSYrJY0CmVAmCwZc/B3528bmCqtoKQdrcHqU0jPtjxPpDLY9cF559zoH0jJkEk98 el6m5wn/j2mCcCw2I8dUvMw0+WNt1zHmyPabU=
MIME-Version: 1.0
Received: by 10.223.97.219 with SMTP id m27mr548751fan.81.1308141682974; Wed, 15 Jun 2011 05:41:22 -0700 (PDT)
Received: by 10.223.109.17 with HTTP; Wed, 15 Jun 2011 05:41:22 -0700 (PDT)
In-Reply-To: <AD38C157-C7DB-4E8A-8603-D87C5A411182@csperkins.org>
References: <01c501cc1c16$ebad8ea0$46298a0a@china.huawei.com> <BFEA47ED-8F65-476A-BBD4-D369493B9D22@csperkins.org> <029f01cc274c$b8fe19c0$46298a0a@china.huawei.com> <AD38C157-C7DB-4E8A-8603-D87C5A411182@csperkins.org>
Date: Wed, 15 Jun 2011 08:41:22 -0400
Message-ID: <BANLkTinQp6nszTDpnKM6M2BUaNvR_cLUWw@mail.gmail.com>
From: Peter Musgrave <musgravepj@gmail.com>
To: Colin Perkins <csp@csperkins.org>
Content-Type: multipart/alternative; boundary="0015174bdf6e545e8504a5bf787b"
Cc: avt@ietf.org, xrblock@ietf.org
Subject: Re: [AVTCORE] [xrblock] Fw: I-D Action: draft-ietf-avtcore-monarch-02.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 12:41:26 -0000

I agree with Colin

Peter Musgrave
(as individual)

On Tue, Jun 14, 2011 at 6:27 AM, Colin Perkins <csp@csperkins.org> wrote:

> On 10 Jun 2011, at 09:59, Qin Wu wrote:
> > Hi,
> >> ----- Original Message -----
> >> From: "Colin Perkins" <csp@csperkins.org>
> >> To: "Qin Wu" <sunseawq@huawei.com>
> >> Cc: <avt@ietf.org>; <xrblock@ietf.org>; <magnus.westerlund@ericsson.com
> >
> >> Sent: Thursday, June 09, 2011 9:58 PM
> >> Subject: Re: [AVTCORE] Fw: I-D Action: draft-ietf-avtcore-monarch-02.txt
> >>
> >>
> >> On 27 May 2011, at 03:36, Qin Wu wrote:
> >>> This version addresses the open issues regarding identity information
> repetition and acknowledge section.
> >>> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-02.txt
> >>>
> >>> The diff is:
> >>> http://tools.ietf.org/rfcdiff?url2=draft-ietf-avtcore-monarch-02
> >>>
> >>> Comments are welcome!
> >>
> >> This helps, but to my mind doesn't go far enough. We have the SSRC to
> identify participants. I don't see much benefit from having a separate
> identity tag in XR blocks.
> >>
> > [Qin]:  I think that we are talking about how to define future RTCP XR
> Block. It seems to me the rule we are following  to define the new RTCP XR
> BLock in the avtcore-monarch is a little different from the rule of we are
> doing to the existing RTCP XR described in RFC3611.
> >
> > As for the existing XR Block defined in RFC3611, each of the existing XR
> Block has allocated  a field for SSRC of source. However such identity
> information can be repeated several times if several metric blocks reporting
> one stream from one source  is carried in the same RTCP Packet.
> >
> > In order to reduce overhead to carry duplicated SSRC of source in each
> metric block,  in the new XR Block, we separate such SSRC of source out from
> each metric block.
> >
> > One way is to  allocate identity tag field in each metric block which can
> be used to tell which metric block report on stream from which source.
> >
> > Another way is to follow the existing rules defined in RFC3611. put back
> the SSRC of source field into each metric block which also can be used to
> tell which metric block report on stream from which source.
> > However this rule seems to contradict to the rule of reducing identity
> information repetition discussed in avtcore-monarch.
> >
> > Which way we should follow?
>
>
> I think you should follow RFC 3611.
>
> The savings from using the new identity tag don't seem worth the added
> complexity.
>
> --
> Colin Perkins
> http://csperkins.org/
>
>
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>