Re: [rmcat] comments on draft-alvestrand-rmcat-remb-02

"Alfred E. Heggestad" <aeh@db.org> Tue, 08 October 2013 18:41 UTC

Return-Path: <aeh@db.org>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46DB621E81EE for <rmcat@ietfa.amsl.com>; Tue, 8 Oct 2013 11:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level:
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[AWL=-2.500, BAYES_00=-2.599, GB_SUMOF=5]
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 2IAyx2oV919O for <rmcat@ietfa.amsl.com>; Tue, 8 Oct 2013 11:41:15 -0700 (PDT)
Received: from mailstore06.sysedata.no (b.mail.tornado.no [195.159.29.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8B921E8113 for <rmcat@ietf.org>; Tue, 8 Oct 2013 11:41:03 -0700 (PDT)
Received: from [46.15.202.74] (helo=alfred-heggestads-macbook-pro.local) by mailstore06.sysedata.no with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from <aeh@db.org>) id 1VTcDN-0004xd-7L; Tue, 08 Oct 2013 20:41:01 +0200
Message-ID: <525451BC.5030703@db.org>
Date: Tue, 08 Oct 2013 20:41:00 +0200
From: "Alfred E. Heggestad" <aeh@db.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Varun Singh <vsingh.ietf@gmail.com>
References: <5251549C.3080500@db.org> <CAEbPqryhXwbtyq0du38c5q0G6XceAZZWJN=5Vh0Wdq0HBAux8w@mail.gmail.com>
In-Reply-To: <CAEbPqryhXwbtyq0du38c5q0G6XceAZZWJN=5Vh0Wdq0HBAux8w@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: rmcat WG <rmcat@ietf.org>
Subject: Re: [rmcat] comments on draft-alvestrand-rmcat-remb-02
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmcat>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2013 18:41:20 -0000

Hi Varun,

okay, thanks for the info!


/alfred

On 10/6/13 6:45 PM, Varun Singh wrote:
> Hi Alfred,
>
> Some comment inline.
>
> -Varun
>
> On Sun, Oct 6, 2013 at 3:16 PM, Alfred E. Heggestad <aeh@db.org> wrote:
>> Hi,
>>
>> I have some comments/questions about draft-alvestrand-rmcat-remb-02
>>
>>
>> - is the new RTCP AFB message valid for all kinds of streams ?
>>    audio, video etc ?
>>
>
> It depends on how many and which SSRCs are reported in the feedback message.
> As per the draft, it is up to the implementation (or the congestion
> control algorithm)
> to choose which SSRCs, i.e., it could report just the SSRCs of audio
> or video or a combination.
>
>> - the maximum bitrate, is it defined as the maximum bitrate for
>>    a particular stream, or the maximum bitrate for the whole "Session" ?
>>
>
> One method of calculating the receiver's maximum estimate is defined by
> Google's congestion control (GCC) in
> http://tools.ietf.org/html/draft-alvestrand-rtcweb-congestion
>
> As per GCC, REMB can be used for reporting the sum of the receiver
> estimate across all media streams that share the same end-to-end path.
> I supposed the SSRCs of the multiple media streams that make up the
> aggregate estimate
> are reported in the block.
>
>> - the message is using a unique identifier "REMB" to de-multiplex incoming
>>    AFB messages, is this method defined in a spec somewhere, and is there
>
> The demultiplexing is defined in Section 6.4 of RFC4585,
> https://tools.ietf.org/html/rfc4585#section-6.4
>
>>    a central registry of other types of AFB messages?
>>
>> - section 2.3 OPEN ISSUE, I dont think explicit signaling is needed.
>>
>>
>>
>>
>> /alfred
>
>
>