Re: [rtcweb] Separating stream manipulation from the SDP loudness (Re: Proposed Plan for Usage of SDP and RTP)

Harald Alvestrand <harald@alvestrand.no> Sun, 10 March 2013 14:35 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CBF721F8809 for <rtcweb@ietfa.amsl.com>; Sun, 10 Mar 2013 07:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.064
X-Spam-Level:
X-Spam-Status: No, score=-110.064 tagged_above=-999 required=5 tests=[AWL=0.534, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 EkARM7iY92yb for <rtcweb@ietfa.amsl.com>; Sun, 10 Mar 2013 07:35:48 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id D243D21F8804 for <rtcweb@ietf.org>; Sun, 10 Mar 2013 07:35:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 5573F39E1AD; Sun, 10 Mar 2013 15:35:45 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W15JpxHHxohm; Sun, 10 Mar 2013 15:35:43 +0100 (CET)
Received: from [192.168.255.9] (unknown [216.189.219.66]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 5332739E182; Sun, 10 Mar 2013 15:35:43 +0100 (CET)
Message-ID: <513C9A3D.8080906@alvestrand.no>
Date: Sun, 10 Mar 2013 15:35:41 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3
MIME-Version: 1.0
To: Peter Thatcher <pthatcher@google.com>
References: <CD5D3F35.B22B%robin@hookflash.com> <B9549E2E-6E68-4F34-A9C0-1F050285A70A@acmepacket.com> <CABkgnnXCio-Dw7dN5yfSjeRf3wG2oWow_M2mU-Y49TedSAPQmg@mail.gmail.com> <CAHBDyN6CFTix3W9qWgC1T0O36t4SajL3hMXaHOdkat-p5TY_xA@mail.gmail.com> <CABcZeBMLdEkFZq5rMOY0texKb4DtFQ-O86JkC17kJihxv6Dj8w@mail.gmail.com> <CAHBDyN6mM-rT315uSbeTQfKuCiVwsEDhi7Q6DEbt8pjiJ_4i6g@mail.gmail.com> <CAHp8n2nz=NZb=UaevUSS7GRSBpvn-v9_=QHz6iddnZzyx5-TSQ@mail.gmail.com> <CAJrXDUETwfY7ZvaXO_1Bq8gs8pOTgALQE8FiimrUX7sfuEpDsw@mail.gmail.com> <CAHp8n2kcEHcz11LOYYMZ3-nv2PYQKu=z6M=dsQ_H5JuR8ND7hQ@mail.gmail.com> <513B5D98.2070601@alvestrand.no> <CAJrXDUEL_5BjWVaP4Fu7sY+P7kj1GVz3q3_z=wUtgyzMUnud2w@mail.gmail.com>
In-Reply-To: <CAJrXDUEL_5BjWVaP4Fu7sY+P7kj1GVz3q3_z=wUtgyzMUnud2w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------010706040903020409070709"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Separating stream manipulation from the SDP loudness (Re: Proposed Plan for Usage of SDP and RTP)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Mar 2013 14:35:49 -0000

On 03/10/2013 06:02 AM, Peter Thatcher wrote:
>
> There's a difference between the resolution that you open the camera 
> at and the resolution you send over the network at.  Does the current 
> constraints API let you capture at one resolution and send at 
> another?  Also, does it let you change the send resolution on the fly?
>
Peter, you were in Boston, where we spent quite a bit of time on this 
very topic.

The relevant presentation is 
http://www.w3.org/wiki/images/f/fd/Constraints20130406.pdf.

Dan has promised to have the consensus of the discussion represented in 
the Media Capture and Streams spec well before the Media Capture and 
Streams meeting that we're currently scheduling for 2 weeks after the 
IETF (Doodle poll at http://doodle.com/xd7ffpidh6mgn2m8 )


> These are important controls that, as far as I know, are not currently 
> supplied to the application.  They could potentially be supplied by 
> SDP, new methods, or as you suggest, perhaps even as some kind of 
> constraint.  But I don't think they are currently provided.
>

But we DO have a W3C consensus on which approach to take in providing them.