Re: [rtcweb] WebRTC JS object API with SDP shim option

Bernard Aboba <bernard_aboba@hotmail.com> Thu, 20 June 2013 18:02 UTC

Return-Path: <bernard_aboba@hotmail.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 E1D0921F9FF5 for <rtcweb@ietfa.amsl.com>; Thu, 20 Jun 2013 11:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.544
X-Spam-Level:
X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 TzxwCF2GLoWC for <rtcweb@ietfa.amsl.com>; Thu, 20 Jun 2013 11:02:04 -0700 (PDT)
Received: from blu0-omc2-s21.blu0.hotmail.com (blu0-omc2-s21.blu0.hotmail.com [65.55.111.96]) by ietfa.amsl.com (Postfix) with ESMTP id 5D8BB21F9FE1 for <rtcweb@ietf.org>; Thu, 20 Jun 2013 11:02:00 -0700 (PDT)
Received: from BLU169-W87 ([65.55.111.73]) by blu0-omc2-s21.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 20 Jun 2013 11:02:00 -0700
X-TMN: [Hf+ZhDkC39nvTcYt1sL2Q6F06c9N0kPr]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU169-W87C022E5537B0C41C5841C938E0@phx.gbl>
Content-Type: multipart/alternative; boundary="_849cbe1a-8152-4245-bfb1-d70d3516ee38_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Robin Raymond <robin@hookflash.com>
Date: Thu, 20 Jun 2013 11:01:59 -0700
Importance: Normal
In-Reply-To: <51C34166.2080901@hookflash.com>
References: <51C333E1.1030709@hookflash.com>, <CAJrXDUEYyW8ATixyVaFhVH9=ri-Zy5RxaAqrJ-Ko8mJSh09L-g@mail.gmail.com> <BLU169-W370B3556678DF1CCBF07FE938E0@phx.gbl>, <51C34166.2080901@hookflash.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Jun 2013 18:02:00.0393 (UTC) FILETIME=[42F75390:01CE6DE0]
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] WebRTC JS object API with SDP shim option
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: Thu, 20 Jun 2013 18:02:10 -0000

Robin said: 



"Would someone produce unit tests against the produced SDP and offered 
SDP that is the "defined webrtc spec" so the bar could be set?"
[BA] If there actually was a "defined webrtc spec" that covered the SDP blob in detail, that would be possible.   But at the moment, that doesn't exist (and seems unlikely to be produced).  
Robin also said: 
"Hitting a
 moving target will be challenging. Seems to me a lot of what is SDP is 
not extremely well defined at this point so the only thing I can do is 
produce "good" SDP since the exact definition of what is webRTC SDP 
seems a bit lacking."
[BA] I would suggest that the SDP subset relating to Audio probably can be well defined enough to produce unit tests.  Given the state of the "Plan A" vs. "Plan B" debate, and the other video-related uncertainties, trying to develop test cases for video would probably be a fool's errand.