Re: [rtcweb] Making progress on the signaling discussion (NB: Action items enclosed!)

Iñaki Baz Castillo <ibc@aliax.net> Wed, 05 October 2011 10:37 UTC

Return-Path: <ibc@aliax.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 DD22B21F8A7B for <rtcweb@ietfa.amsl.com>; Wed, 5 Oct 2011 03:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.034
X-Spam-Level:
X-Spam-Status: No, score=-2.034 tagged_above=-999 required=5 tests=[AWL=-0.557, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_24=0.6, J_CHICKENPOX_63=0.6, MIME_8BIT_HEADER=0.3, 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 U1NCD3IuZ8DG for <rtcweb@ietfa.amsl.com>; Wed, 5 Oct 2011 03:37:08 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 06E0321F8726 for <rtcweb@ietf.org>; Wed, 5 Oct 2011 03:37:07 -0700 (PDT)
Received: by vcbfo11 with SMTP id fo11so1458204vcb.31 for <rtcweb@ietf.org>; Wed, 05 Oct 2011 03:40:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.179.202 with SMTP id br10mr650809vcb.41.1317811215330; Wed, 05 Oct 2011 03:40:15 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Wed, 5 Oct 2011 03:40:15 -0700 (PDT)
In-Reply-To: <0EF30DF7-91D2-48A5-90BD-B7E7CA3C61E4@phonefromhere.com>
References: <CA+9kkMBi9BzDu=WOq3RG-o5nbfnUTftDg3LRBU3DFh=Kc4W5ZQ@mail.gmail.com> <CALiegfmYgQ+yb=pDp1J2_PVa1SkxTOuaUCM02Vt6-iGabwif1g@mail.gmail.com> <CA+9kkMCUTiPO3eASjn0mbRA9YCF6TMmGGOjQ4NkVkvzVMN39Gg@mail.gmail.com> <CALiegfnx=qoS_pqyC45WVEYEFqj-3eP9g_kyhAUaOO6He_UEfw@mail.gmail.com> <91623260-6A12-4737-8BA9-4D6B60FCD389@phonefromhere.com> <CALiegfk_6pviBMBmYUvj69JA73Uy0rnXaMvThPuGT2R5NOWycQ@mail.gmail.com> <0EF30DF7-91D2-48A5-90BD-B7E7CA3C61E4@phonefromhere.com>
Date: Wed, 5 Oct 2011 12:40:15 +0200
Message-ID: <CALiegf=GpVUQb7cPMQH+4DpO_fvYPP7LjyyZ8uO5r13hDQORyQ@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Tim Panton <tim@phonefromhere.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Making progress on the signaling discussion (NB: Action items enclosed!)
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: Wed, 05 Oct 2011 10:37:09 -0000

2011/10/5 Tim Panton <tim@phonefromhere.com>;:
>> Your points are perfectly valid and should indeed be covered. But I
>> didn't want to be so explicit in my immature API suggestion. It was
>> just an overview.


> I guess what I was getting at was the fact that the SDP seemed
> central to the API - I'd like something more generic and javascript
> friendly as the central concept.


Hi Tim. At the end you web application will receive (via the custom
signaling) something "like" and SDP containing the media information
offered/answered by the peer (when receiving or initiating a media
session).

This is: your web browser needs to know the remote IP:port, the media
streams, supported codecs by the peer... At the end that looks like a
SDP. And such "SDP" should be retrieved by your web application via
some signaling protocol (on top of HTTP or WebSocket), and you will
receive it as a JSON object, or XML, or whatever format.

Then you will always need to parse such "like-SDP", obtain something
like a WebRTC.SDP object, and use it for starting/answering a session.

You can propose a different name, something like...
"WebRTC.SessionDescription"? :)
but the underlying concept is the same (IMHO).

Regards.


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