Re: [rtcweb] SDP testing

Matthew Kaufman <matthew@matthew.at> Mon, 22 October 2012 03:59 UTC

Return-Path: <matthew@matthew.at>
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 750C721F8A41 for <rtcweb@ietfa.amsl.com>; Sun, 21 Oct 2012 20:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.206
X-Spam-Level:
X-Spam-Status: No, score=-1.206 tagged_above=-999 required=5 tests=[AWL=0.224, BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 gbIy6U09AL7j for <rtcweb@ietfa.amsl.com>; Sun, 21 Oct 2012 20:59:06 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1E321F8955 for <rtcweb@ietf.org>; Sun, 21 Oct 2012 20:59:06 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by where.matthew.at (Postfix) with ESMTP id 0581D148093 for <rtcweb@ietf.org>; Sun, 21 Oct 2012 20:59:06 -0700 (PDT)
Message-ID: <5084C489.2050306@matthew.at>
Date: Sun, 21 Oct 2012 20:59:05 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <5082DDAF.7080102@matthew.at>, <508325F9.8010107@alvestrand.no> <BLU002-W136BDAECA1A38C4DA5FB5E593740@phx.gbl>, <50839B63.5090607@alvestrand.no> <BLU002-W1256A732EEB7A146894B228937B0@phx.gbl> <88E820A7-103D-420D-AB7E-836EED12B548@iii.ca>
In-Reply-To: <88E820A7-103D-420D-AB7E-836EED12B548@iii.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] SDP testing
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: Mon, 22 Oct 2012 03:59:06 -0000

On 10/21/2012 4:41 PM, Cullen Jennings wrote:
>
> The issue of what can be changed that Mathew raised has been discussed as an open issue and we know that we need to nail that down in the specification. It seemed like one of the things that could be left till a bit later in the process when we had more information about what the use cases were and what to put. The one use case that has been raised very clearly is people want to be able to remove a particular codec for various reasons. I suspect that lots of people will argue to make sure that type of change of SDP is supported. I'm not sure what use case drive the rest but 100% agree this is a topic we need to put some time into.  Right now, it does not seem to be holding up implications which are still trying to nail down all the basic stuff along with ICE, DTLS, etc.
>

The API surface exposed in the browser must be *completely* specified. 
While I am glad that you "100% agree this is a topic we need to put some 
time into," I also know that in the years since SDP O/A was first 
proposed a concrete set of interoperability specifications has yet to 
materialize, and so it seems unlikely that this WG or the W3C WG will 
manage to fully document what changes to the SDP emitted by createOffer 
and the SDP accepted by setLocalDescription and setRemoteDescription are 
permitted without a *significant* effort.

I will note that the JSEP draft says that calling createOffer is 
optional, and so it must be possible to, with only access to the 
specification and the referenced specifications, generate a blob of SDP 
which is accepted by setLocalDescription in *every* browser 
implementation. We are nowhere near that point.

All of this is of course easily avoided by choosing an API surface which 
is not an underspecified blob of SDP.

Matthew Kaufman