Re: [rmcat] call for comments on draft-ietf-rmcat-app-interaction-00

Varun Singh <vsingh.ietf@gmail.com> Fri, 24 October 2014 15:31 UTC

Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C57771A1A4E for <rmcat@ietfa.amsl.com>; Fri, 24 Oct 2014 08:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0AtjIawIFQji for <rmcat@ietfa.amsl.com>; Fri, 24 Oct 2014 08:31:52 -0700 (PDT)
Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD8191A06E9 for <rmcat@ietf.org>; Fri, 24 Oct 2014 08:31:52 -0700 (PDT)
Received: by mail-ie0-f182.google.com with SMTP id rd18so2013110iec.41 for <rmcat@ietf.org>; Fri, 24 Oct 2014 08:31:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=eFOHbN3MP5jDYocjsH1Q07CSYSdns9pLW908fQ/VMGE=; b=i++tEUJ25qrG43iuybS7mKO2P5DxVtsVxcL+Vf27IBn/2Y+kIvBcqG7TpKXSxL10yk dpWZ1Dx99BNOl5JqFmW/BA5Jyoo0drLR96STXkpH9bWM+AzO2KIsIlnt0sxp3DEeHESC te+KPexE68bzsVU3i5fvKxTAs/eSkI2Bl4Sti/NhsaIU4KtLQFbu+tv49wZBxxBN0gB5 iUX2aMvtnPthe9czVOyznBZzPYAW0u8F7Jx/fjS9Yc0dzWXwmGoKSPoyQnL8zmDynK02 g2Q2DdsabbLIi6qgZusZ/tb7nFXdacBhRpW3CYCXI2zbZB0P24EaxlhGCrhLuQv478qH o5oA==
X-Received: by 10.50.43.167 with SMTP id x7mr4388199igl.41.1414164712111; Fri, 24 Oct 2014 08:31:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.50.114.138 with HTTP; Fri, 24 Oct 2014 08:31:31 -0700 (PDT)
In-Reply-To: <cdb98b4e0c34f901536cf9a0a6d7e9da@mail.gmail.com>
References: <cdb98b4e0c34f901536cf9a0a6d7e9da@mail.gmail.com>
From: Varun Singh <vsingh.ietf@gmail.com>
Date: Fri, 24 Oct 2014 18:31:31 +0300
Message-ID: <CAEbPqrwL2L+ehTH=6HC=FjUi21u+yZpJDzZ_4XcfbgETBM6hMA@mail.gmail.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/rmcat/ZyK359Jjo2tawEnNRrQ0G7D21uk
Cc: rmcat WG <rmcat@ietf.org>, "Eggert, Lars" <lars@netapp.com>, draft-ietf-rmcat-app-interaction@tools.ietf.org, Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
Subject: Re: [rmcat] call for comments on draft-ietf-rmcat-app-interaction-00
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 24 Oct 2014 15:31:54 -0000

Hi all,

Comments inline

On Wed, Oct 22, 2014 at 12:05 PM, Karen Elisabeth Egede Nielsen
<karen.nielsen@tieto.com> wrote:
> Hi,
>
> In order to progress the wg document on application interactions we and
> the authors of the doc would like to call for people, CC designers in
> particular, to
> read the document and provide comments with focus on the following
> aspects:
>
>   1. Scope of document: Which interfaces are we looking to have described
> in this document - especially should the document only describe the
> interface in between the RMCAT Congestion controller and the application
> or should the document provide an more extensive description of the
> various components and their interrelations - still likely with a special
> emphasis on  the RMCAT Congestion controller and the application/codec
> interface - ?
>
>  This was discussed already at IETF89 RMCAT session (see minutes) - this
> is an attempt to recap this discussion in order to establish consensus.
>

My personal thoughts on this:

I am waiting for the Constraints API for WebRTC/Media Source API
[1,2]. The API allows the web application to provide hints to the
underlying WebRTC stack on what it expects (or at least that is what I
think it does). For example through the API the application can
configure the range of expected video resolutions, video frame rate,
etc. This will be discussed and maybe finalized at next weeks W3C
meeting.

I don’t know, if we have to strictly follow the variables manipulated
by the Constraints API, but it will surely help the discussion in the
application interactions draft. Or even provide feedback to the W3C,
if there are variables that the congestion control proposal’s need.
But honestly, I am not sure I have figured out all these interfaces
yet.

Cheers,
Varun

[1]: http://w3c.github.io/mediacapture-main/#media-track-constraints
[2]: http://w3c.github.io/mediacapture-main/#constrainable-interface


>   2. What (given the scope assumed for 1.) are the top 3-4 interactions
> (e.g., allowed rate)   that matter the most and which are needed to be
> described in the document ?
>
> Thanks.
>
> BR, Karen/Chairs
>



-- 
http://www.netlab.tkk.fi/~varun/