Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface

Cullen Jennings <fluffy@iii.ca> Fri, 19 July 2013 14:04 UTC

Return-Path: <fluffy@iii.ca>
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 F186D21E80D0 for <rtcweb@ietfa.amsl.com>; Fri, 19 Jul 2013 07:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.416
X-Spam-Level:
X-Spam-Status: No, score=0.416 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_18=0.6, J_CHICKENPOX_19=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_SORBS_WEB=0.619]
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 9m3fdtodMdZq for <rtcweb@ietfa.amsl.com>; Fri, 19 Jul 2013 07:04:07 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF1721E80B8 for <rtcweb@ietf.org>; Fri, 19 Jul 2013 07:04:07 -0700 (PDT)
Received: from [10.171.47.8] (unknown [209.121.225.136]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1B485509B6; Fri, 19 Jul 2013 10:04:00 -0400 (EDT)
References: <CAJrXDUGMohpBdi-ft-o_uE7ewFkw7wRY9x7gYEncjov7qi-Bew@mail.gmail.com> <CABcZeBPa4wBS8pYq=0wesMOfL6TkeC7QGAZ8pWwOcnkhkJqWfA@mail.gmail.com> <CAJrXDUFxo8P8wxh8jX3019yPQOuwQ0eVdsFmRXsbWdWinnc5oA@mail.gmail.com> <CABcZeBOTKpmFC34waqZ4kA-P8t+E6yY9gX1JFCHhsBH0+CF-Qw@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30BC0F@ESESSMB209.ericsson.se> <CAD5OKxtKLMf_d=8GSMrqfNhDHPe9MFP2ZTKzZHFn9CyMr-gSVQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30C833@ESESSMB209.ericsson.se> <CAD5OKxvGfkgRp6tXwbOu_kVteHiBBqsyR5ixH18FMKjCNGO8VQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30CD1E@ESESSMB209.ericsson.se> <BLU401-EAS386F88B3FE140492B39B59693610@phx.gbl> <AE1A6B5FD507DC4FB3C5166F3A05A484213E41E7@TK5EX14MBXC265.redmond.corp.microsoft.com>
In-Reply-To: <AE1A6B5FD507DC4FB3C5166F3A05A484213E41E7@TK5EX14MBXC265.redmond.corp.microsoft.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <C50FDAD5-492C-4A83-AD6D-464242FB4A05@iii.ca>
X-Mailer: iPad Mail (10B329)
From: Cullen Jennings <fluffy@iii.ca>
Date: Fri, 19 Jul 2013 07:04:01 -0700
To: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
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, 19 Jul 2013 14:04:12 -0000

Folks wanted to sort out how mindless works fist before getting to theses smaller details but in general I think progress is being made on all of these

On Jul 17, 2013, at 2:58 PM, "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>; wrote:

> Bernard Aboba:
>> 
>> The problem was that we never defined what mangling browsers had to
>> support. Given all the SDP specs that is actually a huge work item.
> 
> 
> This is exactly what my slides that weren't presented last November started to touch upon. It only takes a few minutes with RFC3264 and its references to start documenting cases that are clearly "valid SDP offer/answer" and yet for which I cannot for the life of me figure out what a browser should do if they're presented.
> 
> Just off the top of my head:
> 
> Can I...
> - Change the t= line to be something other than t=0 0?
> - Change the rtpmap associations before calling setLocal?
> - Change a=sendrecv to a=recvonly before calling setLocal?
> - What do you do when you see a=content:sl ?
> - What if someone adds an r= or p= or e=?
> - What is the RFC that describes a=group:BUNDLE (as seen in some browser implementations)?
> - Can I remove a=group:BUNDLE (or add it) before calling setLocal?
> - How about removing a=rtcp-mux?
> - Should I do something special at my end if you set a=ice-options:google-ice ?
> - If you put a=ssrc lines in there, can I change the ssrc before passing it back to setLocal?
> - Can I delete the a=ssrc lines?
> - Is a=rtcp:1 IN IP4 0.0.0.0 valid or not?
> - What about 0.0.0.0 in the o= line?
> - If I get a bunch of a=candidate lines, can I swap them around to change the priority before calling setLocal?
> - What if someone claims SAVP instead of SAVPF but gives me rtcp info?
>    
> At the *very least* for each and every line that comes from createOffer and createAnswer you must be able to answer the following:
> - Can I delete it?
> - Duplicate it?
> - Change it?
> - If not, how are violation handled? (Both when passed to another browser at the far end and when these modifications happen before calling setLocal)
> - And can I add additional valid SDP to what came from createOffer or createAnswer and pass it back to setLocal or not?
> 
> We appear to be nowhere near a document which explains the answers to these questions, certainly not in the W3C WG, and not in any IETF RFC or draft I can locate.
> 
> Matthew Kaufman
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb