IETF Logo Mail Archive

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

Peter Thatcher <pthatcher@google.com> Thu, 20 June 2013 17:56 UTC

Return-Path: <pthatcher@google.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 31EE321F99C9 for <rtcweb@ietfa.amsl.com>; Thu, 20 Jun 2013 10:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level:
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 LDon3SYZDFjU for <rtcweb@ietfa.amsl.com>; Thu, 20 Jun 2013 10:56:03 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id B8FE921F9CBD for <rtcweb@ietf.org>; Thu, 20 Jun 2013 10:56:00 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa11so6550895pad.33 for <rtcweb@ietf.org>; Thu, 20 Jun 2013 10:56:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=gLNmYtEJx68jl7IMLdZbPpZzUi9ZHIAqbWvCEZaHepk=; b=BUg3/1dMQoHufEJYzfrS4StqRsZKkyax3XuSVIr9rkIfmf8UoTTPsvU3EHd63hMhS/ goixG8mMM/TeaVQBUCRkeAP5ZIaaz3fMF5409F6RcGqyA3ZPEQbnfW9YjES3ozhirROo EJZInnAAiinGE9jlTXYdptQ/LS6Kzrecg3PaAOr81gXK1dbiWZo3Jlpy3R5IH7KJWtV6 /8TA+8HX3MpcFLSxfv/yxy78fcR/DX4bczPjRCSmUVdBnbiFZhdV03x9OvQ/YI4xQMdd 4MSuQLeaXKMZq36v+KAAPc8Nvbxt4jDFQn5oMTbM0wYCSdbnSZgxlHuTuk4qIa3SjqWj QX0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=gLNmYtEJx68jl7IMLdZbPpZzUi9ZHIAqbWvCEZaHepk=; b=VSuFhZB7E5auQQKKSHaQP9Ou6EByIJe10xODjdf1kBVRJM9SRjcLp9tFh/EK2se0pQ 4T5wPmz34gFnrBuh3+aqHkskltrJl7ehT4dcrqW+hZH5bmecsmAnAg5YBoJ2LBFHCtNX C2qVBV5p+GhrZfq/w+92unofBgxVWTcpoTiLpzh2tCKipLLyyoLXL1gVJvmfSCOnknJW u5g3lEOuWp4058AvlABBEWnOY7nfpD2A9fsbONxBvmx5P29lDC9j9/XIqDers7G2kWvh 8McTi1knP0R7urzQoQaNTxisgTvdZdKDlB83z7iICl/jQt2ZexHtu0cQUGwCZmv97H2H KkMQ==
X-Received: by 10.68.1.226 with SMTP id 2mr8724060pbp.150.1371750960337; Thu, 20 Jun 2013 10:56:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.88.8 with HTTP; Thu, 20 Jun 2013 10:55:20 -0700 (PDT)
In-Reply-To: <BLU169-W370B3556678DF1CCBF07FE938E0@phx.gbl>
References: <51C333E1.1030709@hookflash.com> <CAJrXDUEYyW8ATixyVaFhVH9=ri-Zy5RxaAqrJ-Ko8mJSh09L-g@mail.gmail.com> <BLU169-W370B3556678DF1CCBF07FE938E0@phx.gbl>
From: Peter Thatcher <pthatcher@google.com>
Date: Thu, 20 Jun 2013 10:55:20 -0700
Message-ID: <CAJrXDUGufkFNtOSt3a_wWmtBa6F7xFEazae=FAhSg7VoCheY0g@mail.gmail.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: multipart/alternative; boundary="bcaec5314817b62ad804df99a838"
X-Gm-Message-State: ALoCoQmObQQbEutCw4R/NeupMo+u3IXORQLbAVnl+zbuj+Xy/drLMGrQEdAGkeL2vQGpUm7/dtHyO22jDSw7ooSodKze5hGS0LJFffTFRZ8QcxNlWuXjm0j0vxg67Pfw8KhXYebkftbOjdLv93AE5MSHfH1AhuZBi2lW8meLVsz68c/y9ZAzFYxox9K9cXB6jWjyZfNpCHsS
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 17:56:04 -0000

On Thu, Jun 20, 2013 at 10:48 AM, Bernard Aboba
<bernard_aboba@hotmail.com>wrote:

> Peter Thatcher said:
>
> "How are you going to test that shim without a working implementation of
> the clean API?
>
> One thing you could do is build a shim of clean API -> SDP.  Then, you'd
> have two shims which would make a fun combination (SDP -> clean API -> SDP)
> and you're prove that SDP munging and the clean API are equivalent in power.
>
> Or you could fork Chrome or Firefox.
>
> Either way, you have a lot of work ahead of you.  Best of luck."
>
> [BA] Getting a working implementation of a clean API is not the biggest
> issue.
>

If implementing the clean API in browser is the small issue, then poor
Robin has a massive challenge ahead.



> The biggest issue is how to determine whether a shim is "successful" or
> not.   At this point, the reality is that the  implementation code
> (including undocumented behavior) represents the WebRTC 1.0 specification,
> rather than the documents produced by W3C and IETF.  This makes the bar
> (either "backward compatibility" or "equivalent in power") difficult to
> define, let alone satisfy.
>
>
>

v2.14.0 | Report a Bug | By Email