IETF Logo Mail Archive

Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)

"Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net> Thu, 27 June 2013 05:27 UTC

Return-Path: <matthew.kaufman@skype.net>
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 68FD521F9BD5 for <rtcweb@ietfa.amsl.com>; Wed, 26 Jun 2013 22:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.598
X-Spam-Level:
X-Spam-Status: No, score=-5.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, 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 p9l9fHuPODlQ for <rtcweb@ietfa.amsl.com>; Wed, 26 Jun 2013 22:27:49 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0238.outbound.protection.outlook.com [207.46.163.238]) by ietfa.amsl.com (Postfix) with ESMTP id 3565C21F8F87 for <rtcweb@ietf.org>; Wed, 26 Jun 2013 22:27:48 -0700 (PDT)
Received: from BL2FFO11FD021.protection.gbl (10.173.161.202) by BL2FFO11HUB052.protection.gbl (10.173.161.128) with Microsoft SMTP Server (TLS) id 15.0.717.3; Thu, 27 Jun 2013 05:27:48 +0000
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD021.mail.protection.outlook.com (10.173.161.100) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 27 Jun 2013 05:27:47 +0000
Received: from TK5EX14MBXC273.redmond.corp.microsoft.com ([169.254.1.171]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.03.0136.001; Thu, 27 Jun 2013 05:26:38 +0000
From: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
To: Robin Raymond <robin@hookflash.com>, Bernard Aboba <bernard_aboba@hotmail.com>
Thread-Topic: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)
Thread-Index: AQHOa1pL3f2CtN2bTEydXd59L0Jyj5k6p8cAgAKBMYCAAAxEgIALzZYAgAAPjYCAAAHm4A==
Date: Thu, 27 Jun 2013 05:26:37 +0000
Message-ID: <AE1A6B5FD507DC4FB3C5166F3A05A4841A2E9DE2@TK5EX14MBXC273.redmond.corp.microsoft.com>
References: <CAJrXDUHdoxLTsofiwLBdwBNnCCkCBgjSdbmLaXrNEPODMrsSVA@mail.gmail.com>, <CAHp8n2m4VwkpbdGE+q73qqij5RDCB4Vb-Ui1LmGSx1zmv8TX2g@mail.gmail.com>, <CAJrXDUEfdsZJBgkcb=MJnxRmk9ZMTHw39DE=YWa+ngXxvfsQ0A@mail.gmail.com>, <51C1D55D.6040905@hookflash.com> <BLU169-W225763F0847397377AA5AE93750@phx.gbl> <51CBC919.1070805@hookflash.com>
In-Reply-To: <51CBC919.1070805@hookflash.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.32]
Content-Type: multipart/alternative; boundary="_000_AE1A6B5FD507DC4FB3C5166F3A05A4841A2E9DE2TK5EX14MBXC273r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454003)(189002)(199002)(69226001)(81542001)(16406001)(71186001)(79102001)(81342001)(74502001)(74706001)(77982001)(31966008)(47446002)(55846006)(74662001)(76482001)(74366001)(51856001)(54356001)(46102001)(44976004)(74876001)(77096001)(59766001)(19300405004)(76786001)(76796001)(54316002)(15202345003)(56816003)(53806001)(56776001)(6806003)(47976001)(20776003)(47736001)(4396001)(512954002)(63696002)(50986001)(33656001)(49866001)(80022001)(66066001)(561944002)(16236675002)(65816001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB052; H:TK5EX14HUBC101.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08902E536D
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in 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: Thu, 27 Jun 2013 05:27:54 -0000

If the current API course is followed, it is mandatory that it be possible to produce a 1-for-1 compatible shim without reference to anything but the W3C documentation and its normative references. Otherwise it cannot be a W3C specification.

Matthew Kaufman

From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Robin Raymond
Sent: Wednesday, June 26, 2013 10:10 PM
To: Bernard Aboba
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)


You are absolutely correct, that it is an unobtainable goal to produce a shim 1-for-1 compatible without reverse engineering.

In the draft:
http://tools.ietf.org/id/draft-raymond-rtcweb-webrtc-js-obj-api-rationale-00.txt

We declare in section 5.4.8 "SIP/SDP and current WebRTC API shim compatibility statement" that it would not be the goal of this shim to do that. I think we have to work towards producing a shim that follows the spirit of the current WebRTC API rather than emulating the exact letter of every feature (and bug), especially since the feature definitions are vague. As any JS shim could be forked and modified, if a particular "feature/bug" needed to be emulated by someone it could be done by the developer needing the specialized behavior. Every JavaScript developer will have full control over the shim's code or which shim(s) to use.

-Robin

v2.23.0 | Report a Bug | By Email