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

Roman Shpount <roman@telurix.com> Wed, 12 October 2011 17:03 UTC

Return-Path: <roman@telurix.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 009CF21F8C93 for <rtcweb@ietfa.amsl.com>; Wed, 12 Oct 2011 10:03:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.826
X-Spam-Level:
X-Spam-Status: No, score=-2.826 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 3dj4-zRH6VDY for <rtcweb@ietfa.amsl.com>; Wed, 12 Oct 2011 10:03:49 -0700 (PDT)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id 8953D21F8C67 for <rtcweb@ietf.org>; Wed, 12 Oct 2011 10:03:49 -0700 (PDT)
Received: by pzk37 with SMTP id 37so490472pzk.9 for <rtcweb@ietf.org>; Wed, 12 Oct 2011 10:03:49 -0700 (PDT)
Received: by 10.68.26.168 with SMTP id m8mr2500788pbg.29.1318439029315; Wed, 12 Oct 2011 10:03:49 -0700 (PDT)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by mx.google.com with ESMTPS id ki1sm1680942pbb.3.2011.10.12.10.03.47 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 12 Oct 2011 10:03:47 -0700 (PDT)
Received: by pzk37 with SMTP id 37so490391pzk.9 for <rtcweb@ietf.org>; Wed, 12 Oct 2011 10:03:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.74.4 with SMTP id p4mr2454091pbv.47.1318439026770; Wed, 12 Oct 2011 10:03:46 -0700 (PDT)
Received: by 10.68.47.40 with HTTP; Wed, 12 Oct 2011 10:03:46 -0700 (PDT)
In-Reply-To: <CALiegfkwYYSjeSD2PHmOxv16uxQ66kBffraAzXEmaO1UicBFUQ@mail.gmail.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> <CA+9kkMCibnPLrEq1234bUMXpiKBK0+22mqwYOM__CpcO2nOayg@mail.gmail.com> <CALiegfms2bt-WPtMeosFQz3-aSf2L6mfX+i68tw45sSgix561Q@mail.gmail.com> <4E8D6507.8000707@ericsson.com> <CALiegf=VyViX2arp0gr0dK4WN_jv=bjwP0LUAxRf=quTxrYrUQ@mail.gmail.com> <CALiegfn15szv-2yXeWptWjsQC2CwVODg_X90gD4odZkCR0LzvA@mail.gmail.com> <4E955775.10206@alvestrand.no> <CABRok6n6UA_nFfLzQ4K+H0+idspEsymW29OZH0J5q1ewF3PpRw@mail.gmail.com> <4E956526.2090604@alvestrand.no> <380E325E-A7EF-489A-AA24-0270224FC87A@phonefromhere.com> <4E957C55.9020706@alvestrand.no> <13C2526B-E7B1-408C-BD1D-EC5E8C8F6472@phonefromhere.com> <4E95871F.9010605@alvestrand.no> <E21755ED-205F-4D80-BB97-CF32E989EB3F@phonefromhere.com> <4E959D48.3090401@mozilla.com> <9E790044-DE19-46DD-89D8-C4F2973F8D65@phonefromhere.com> <CAD5OKxvORBxJk=5oAeWjUdMgq9pr7eePOnKana4VtwVEHFNGNg@mail.gmail.com> <CALiegfkwYYSjeSD2PHmOxv16uxQ66kBffraAzXEmaO1UicBFUQ@mail.gmail.com>
Date: Wed, 12 Oct 2011 13:03:46 -0400
Message-ID: <CAD5OKxusmjt=Sn=p876GPi4EDK_mUBhAQqN4Wv0Fsiy-P3zxKw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Content-Type: multipart/alternative; boundary=f46d0413911dd943e904af1d0185
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, 12 Oct 2011 17:03:50 -0000

On Wed, Oct 12, 2011 at 12:56 PM, Iñaki Baz Castillo <ibc@aliax.net>; wrote:

> 2011/10/12 Roman Shpount <roman@telurix.com>;:
> > P.S. I do find the current API proposal a bit deficient due to its
> inability
> > to support forking, asymmetric codec selection, and delegating codec
> > negotiation to the RTC implementation.
>
> Perhaps I miss something but... which "current API" do you mean?
>
>
I've meant "Architecture and API for RTCWeb" from Neil Stratford:
https://docs.google.com/document/pub?id=1MfrFHKx6O6yWtIv_jqwyH-RAbm8AgRtXQ7dJTZz5J2g&pli=1and
draft-jennings-rtcweb-api-00. There might be something that I've
missed
while reading those documents but I could not figure out how to implement
any of the features that I've listed.

_____________
Roman Shpount