Re: [rtcweb] Requesting "SDP or not SDP" debate to be re-opened

Christer Holmberg <> Wed, 19 June 2013 08:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3446121F9FB9 for <>; Wed, 19 Jun 2013 01:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.629
X-Spam-Status: No, score=-5.629 tagged_above=-999 required=5 tests=[AWL=0.320, BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ksmUU+I0RqcC for <>; Wed, 19 Jun 2013 01:42:05 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id B07D921F9E88 for <>; Wed, 19 Jun 2013 01:42:04 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d6d000003d54-58-51c16edbaffc
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id D9.BE.15700.BDE61C15; Wed, 19 Jun 2013 10:42:03 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.02.0328.009; Wed, 19 Jun 2013 10:42:03 +0200
From: Christer Holmberg <>
To: Iñaki Baz Castillo <>
Thread-Topic: [rtcweb] Requesting "SDP or not SDP" debate to be re-opened
Date: Wed, 19 Jun 2013 08:42:02 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsUyM+Jvre7tvIOBBjP2SFlM32djsfZfO7sD k8e5hvfsHkuW/GQKYIritklKLCkLzkzP07dL4M64cmUPU8EkqYpdb5exNjDukexi5OSQEDCR aNy1kxnCFpO4cG89WxcjF4eQwGFGiT9tuxghnEWMEqfnT2XqYuTgYBOwkOj+pw3SICJgI/Hv wgV2EJtZQFXi/KFzjCC2sICHxO1ne1lAykUEPCWWn62CKE+SaLt9F6yEBaj86envYHt5BXwl fkyczwJiCwnMYJHYcNMKxOYUCJS4dO8eWD0j0G3fT61hglglLnHryXwmiJsFJJbsOQ91v6jE y8f/WEHWSggoSizvlwMxmQU0Jdbv0ofoVJSY0v2QHWKroMTJmU9YJjCKzUIydBZCxywkHbOQ dCxgZFnFyJ6bmJmTXm64iREYGwe3/NbdwXjqnMghRmkOFiVx3g+ndgUKCaQnlqRmp6YWpBbF F5XmpBYfYmTi4AQRXFINjEkqOQ3Xz23SEolcsc7sZrxhLt+12zV3KnZlNFsu+OSr7dTjurvP NUzh+ISrnyMKm+L8w26+4V11bOFEv/q7b/ierWtdfGsrz8ed4iWy66ZXxz/wD5GbMmHblK1P Q9kmrpv/Tvr8xUfd/9mPhF/4nLb/eP8sN4t/cbnrl/tXhX/I4ov2Sf29VVqJpTgj0VCLuag4 EQCWsNJuYAIAAA==
Cc: "" <>
Subject: Re: [rtcweb] Requesting "SDP or not SDP" debate to be re-opened
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 19 Jun 2013 08:42:10 -0000


You are the one who requested the debate to be re-opened. Are you saying that I need to go through previous discussions to figure out what you want to debate - or to figure out what you THINK you want to debate? :)



-----Original Message-----
From: Iñaki Baz Castillo [] 
Sent: 19. kesäkuuta 2013 11:39
To: Christer Holmberg
Subject: Re: [rtcweb] Requesting "SDP or not SDP" debate to be re-opened

2013/6/19 Christer Holmberg <>:
> We need to be very clear what we talk about, or some people are always 
> going to be confused :)
> So, AFAIK, the discussion is about SDP O/A usage in the API, only in 
> the API, and nowhere but the API.
> Whatever people us on the wire is outside the scope.

Hi Christer,

I do not dare to summarize what we request in a single response, and I don't want to say something that "I didn't want to say" ;)

IMHO this thread clearly describes what we request, i.e. in these exact mails:


My "non-normative" summary:

I don't think that the discussion is just about "SDP O/A usage in the API". We don't want a replacement for SDP, nor a new representation of SDP, nor to deal with blob strings between the JS layer and the WebRTC layer. In short we want something like a JS wrapper of the native WebRTC API, to directly manage media/transport parameters and media streams without having to pass a monolithic and unmanageable SDP blob between the JS and the WebRTC layer. And once the JS makes all the API calls to get the required media parameters, the JS can send them to the remote peer in the way it prefers (which may be via a SDP created by the JS app, or via an AJAX request for sending codecs/media-types info followed by a WebSocket connection for sending ICE candidates one by one, or serialized in JSON via a previously open DataChannel session... or whatever mechanism available in the Web and browsers).

For sure, other participants in this thread can improve/fix my "summary".

Please. re-read the 3 links above, IMHO they should clearly describe what we are requesting for :)

Best regards.

Iñaki Baz Castillo