IETF Logo Mail Archive

Re: [rtcweb] Proposed Plan for Usage of SDP and RTP - Lower level API minus SDP

Silvia Pfeiffer <silviapfeiffer1@gmail.com> Fri, 08 March 2013 02:56 UTC

Return-Path: <silviapfeiffer1@gmail.com>
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 BB48A21F862B for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2013 18:56:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[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 V5UByzt-ZlIB for <rtcweb@ietfa.amsl.com>; Thu, 7 Mar 2013 18:56:38 -0800 (PST)
Received: from mail-lb0-f179.google.com (mail-lb0-f179.google.com [209.85.217.179]) by ietfa.amsl.com (Postfix) with ESMTP id C72D221F862A for <rtcweb@ietf.org>; Thu, 7 Mar 2013 18:56:37 -0800 (PST)
Received: by mail-lb0-f179.google.com with SMTP id j14so973969lbo.24 for <rtcweb@ietf.org>; Thu, 07 Mar 2013 18:56:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=Qt+g2U7SJ7aBltH/cVL0GlKz/pA5xK+YMMlsFs2/omw=; b=MCAS4yE/JlDfdV+Qrm8VVPEvObPPBjZg68TCzNQPUJh1azUEIHrEAZjk1dGqWNEY5b WzmMbaMIvdPl7zl8Jx9uWJOlR/Gp+OWObhbXjlKDubFK9hdyNQnXqxy3yTm4TsHMl5Mn OVHg7QTJLfQm1lqMC67hjMJkA8cWi6ww2e+VN2VZNV6x/jfvda3VTXdw//+pgxypJfbN 5lGx7pydG+cv5Jv+tyTLKasLqwH8m5U++NFUyAAfOcVaV0L4HofT8GmgQRHKT+sQU8lm rGkXfZuieBqWwvzc9caYozPy5ezM3ep/Ornjx1qDlG2Tgr2YBPQMBa6CaB7Lr8WRfKW+ Ab9Q==
X-Received: by 10.152.109.112 with SMTP id hr16mr502738lab.38.1362711396473; Thu, 07 Mar 2013 18:56:36 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.51.229 with HTTP; Thu, 7 Mar 2013 18:56:16 -0800 (PST)
In-Reply-To: <513930C8.6050900@mozilla.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> <513930C8.6050900@mozilla.com>
From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Fri, 08 Mar 2013 13:56:16 +1100
Message-ID: <CAHp8n2kWgpthrMB4tR3Mvz7szPk7JskZJBsWZS9KZt6VES_1kw@mail.gmail.com>
To: "Timothy B. Terriberry" <tterriberry@mozilla.com>
Content-Type: multipart/alternative; boundary="bcaec54eea70b7e56904d760f8ce"
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Proposed Plan for Usage of SDP and RTP - Lower level API minus SDP
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: Fri, 08 Mar 2013 02:56:38 -0000

On Fri, Mar 8, 2013 at 11:28 AM, Timothy B. Terriberry <
tterriberry@mozilla.com> wrote:

> Silvia Pfeiffer wrote:
>
>> For example: the programmer wants to say - I want to get this video
>> resolution, this audio bitrate & channels, I want to use this camera and
>> this microphone for this call. Having to manipulate SDP directly for
>> this is a programmer's nightmare.
>>
>
> I would like to point out that the currently proposed W3C APIs do not
> require (or even allow) SDP manipulation for _any_ of this, with the
> possible exception of audio bitrate (which, as we've long discussed, should
> actually be adapted in real-time based on available bandwidth as determined
> by congestion control, with some app-provided way to set priorities that
> will _not_ be based on SDP... the number in SDP merely defines the limits
> of what's possible).


Is there any way for the Web developer to influence the negotiation of,
say, the video resolution? For example, if the video is displayed in a
160x120 video element, then it makes no sense to receive anything larger
than that resolution. I was under the impression that this would have to be
done through manipulating SDP?

Silvia.

v2.23.0 | Report a Bug | By Email