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

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 18 June 2013 16:24 UTC

Return-Path: <prvs=78816e9fb4=christer.holmberg@ericsson.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 B4D6221F9B08 for <rtcweb@ietfa.amsl.com>; Tue, 18 Jun 2013 09:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.58
X-Spam-Level:
X-Spam-Status: No, score=-5.58 tagged_above=-999 required=5 tests=[AWL=0.368, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 p9HFXcZerPjM for <rtcweb@ietfa.amsl.com>; Tue, 18 Jun 2013 09:24:42 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 52ED521E808E for <rtcweb@ietf.org>; Tue, 18 Jun 2013 09:24:34 -0700 (PDT)
X-AuditID: c1b4fb25-b7f4c6d000004656-a9-51c089bb0c61
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id E3.E8.18006.BB980C15; Tue, 18 Jun 2013 18:24:28 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.6]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.02.0328.009; Tue, 18 Jun 2013 18:24:27 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>, =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)
Thread-Index: AQHOa1pIuB/+178/L06DgV0q3oZHV5k6IN0AgAAH7oCAACn2AIAAffyAgAAzWgCAAA4dgIAAUBqAgAALU4CAAA83AIAALG4w
Date: Tue, 18 Jun 2013 16:24:27 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C3ABABC@ESESSMB209.ericsson.se>
References: <CAJrXDUHdoxLTsofiwLBdwBNnCCkCBgjSdbmLaXrNEPODMrsSVA@mail.gmail.com> <CABkgnnUmRpanfpwryyiCUsOdMLzrd74n-4LXaj_AK3aLe0yQ8Q@mail.gmail.com> <CAJrXDUGnEwtsGZwUUqQgH0vDnMPy=XxqwQB9fpNcW9yQDhFt4w@mail.gmail.com> <CABkgnnVghXLu0ZdNkBkvLkqr=xgx6irWnyebU6rv+D45M+iaUg@mail.gmail.com> <CAJrXDUFkdfE2gfkRx6im3qNwjd3ObNv0tGO8O0vht146+A1kfQ@mail.gmail.com> <CALiegfmMWiEZDL4eCc6VSEsH1z8F6K5Xzz_-Z6hiKiD9yAap0Q@mail.gmail.com> <51C0269B.5070200@telecomitalia.it> <51C069CD.6000804@hookflash.com>, <CALiegf=uENdToGPr1eRRgCOHY6kvoEy8-Aja8mhGWSp0Q=4D8w@mail.gmail.com> <AE1A6B5FD507DC4FB3C5166F3A05A4841A2C6D46@TK5EX14MBXC273.redmond.corp.microsoft.com>
In-Reply-To: <AE1A6B5FD507DC4FB3C5166F3A05A4841A2C6D46@TK5EX14MBXC273.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C3ABABCESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrGLMWRmVeSWpSXmKPExsUyM+Jvre6ezgOBBgfWMllM32djMePWWRaL tf/a2R2YPc41vGf3WLLkJ5PHrQeT2AKYo7htkhJLyoIz0/P07RK4M3oO/2Mr2FRTcfb5FvYG xk85XYycHBICJhJ35y9khbDFJC7cW8/WxcjFISRwmFGi6fwkdpCEkMAiRolFdyy7GDk42AQs JLr/aYPUiAjMZJTY/rqJCaRGWCBf4n77E2aQGhGBAolDOxkhzDyJ1xc1QCpYBFQlZr46CLaK V8BX4vrVP0wQq2ayShx8uYcZJMEpkCgx78A0FhCbEeie76fWgI1nFhCX+HDwOjPEnQISS/ac h7JFJV4+/gd1v5LEjw2XWCDq8yV+HT7LDLFMUOLkzCcsExhFZiEZNQtJ2SwkZRBxPYkbU6ew QdjaEssWvoaq15WY8e8QC7L4Akb2VYzsuYmZOenlRpsYgdF0cMtv1R2Md86JHGKU5mBREuf9 eGpXoJBAemJJanZqakFqUXxRaU5q8SFGJg5OEMEl1cBYMSs93Pm9esnhV/rGLVMfP5UMijuW e0RG/7PhGa3bZ+5XMCz6JyVi3Le7eIbG2z1736VOe3/9/dVI1+23X8zdN2uOb83nuduaG8NT LJ97BHpmzf7XWX7n686w+uv6yiG3rUv72LPY9GebFPHoOLa33knivmu7aovKfOtcJcWos4qr 1v7+JnNIiaU4I9FQi7moOBEAWcUuvHkCAAA=
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: Tue, 18 Jun 2013 16:24:48 -0000

Hi,

The fact that you may not need ICE, or DTLS-SRTP, for your use-case is not related to SDP O/A, is it? SDP O/A itself doesn't mandate you to do ICE or DTLS-SRTP :)

Regards,

Christer

Lähettäjä: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] Puolesta Matthew Kaufman (SKYPE)
Lähetetty: 18. kesäkuuta 2013 18:43
Vastaanottaja: Iñaki Baz Castillo; rtcweb@ietf.org
Aihe: Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)

It isn't SDP that's the problem. It is the offer/answer semantics.

Here's a real simple example of the problem: If I have a web browser that can do RTP A/V, I should be able to send a form post or XHR to ask my security camera to start streaming me RTP video to a specific address and port. The browser doesn't need to do ICE connectivity tests, because it is only going to receive video.

I should be able to use a few lines of JavaScript to initialize the UDP/RTP receive port and wire it to a video window, set up the codec mapping, and ask it for its local address and port so I can tell the camera where to send things. But that isn't how it works at all. Instead I need to run, in JavaScript, the entire offer/answer exchange from the security camera's point of view, extract the relevant information from the SDP blob, and then send it off. (Never mind that I also need to have DTLS-SRTP added to my camera, even though I'm sending unencrypted RTP from it all over the rest of my LAN to other receivers that aren't browsers)

Same thing if I have a two-way radio system that can talk RTP and ICE and which has its own proprietary way of setting up connections... again, need to write a whole SDP parser *and* state machine to run the "fake" offer/answer exchange.

Pain. In. The. Ass.

Matthew Kaufman

________________________________
From: rtcweb-bounces@ietf.org<mailto:rtcweb-bounces@ietf.org> [rtcweb-bounces@ietf.org] on behalf of Iñaki Baz Castillo [ibc@aliax.net]
Sent: Tuesday, June 18, 2013 7:48 AM
To: rtcweb@ietf.org<mailto:rtcweb@ietf.org>
Subject: Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)
2013/6/18 Robin Raymond <robin@hookflash.com<mailto:robin@hookflash.com>>
SDP is clearly the WRONG technical choice. It was wrong from the start but I think there was a great misunderstanding that it was required or SIP wouldn't be compatible with WebRTC. Since the strong majority at the table were SIP guys because they are the "established" industry it became the 'way to do it' despite how horrible it is for the future. So here we are today...


Dear WG Chairs,

With all due respect, IMHO there is enough material to reopen the "SDP or not SDP" debate so I would like to request it to the WG.

I would also appreciate that those in favour of mandating SDP as the core communication for WebRTC explain their rationale again (given the number of arguments against SDP and the frustration SDP is causing), and also that they give arguments and responses to all the SDP related issues exposed in this thread, that are nicely summarized in this mail:

  http://www.ietf.org/mail-archive/web/rtcweb/current/msg07873.html


Really thanks a lot.


--
Iñaki Baz Castillo
<ibc@aliax.net<mailto:ibc@aliax.net>>