Re: [rtcweb] API draft: draft-kaplan-rtcweb-api-reqs-00

Iñaki Baz Castillo <ibc@aliax.net> Fri, 21 October 2011 12:30 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 E852321F8C6A for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 05:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.52
X-Spam-Level:
X-Spam-Status: No, score=-2.52 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 vddUg3aIkl4c for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 05:30:38 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED1E21F8C65 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 05:30:37 -0700 (PDT)
Received: by vws5 with SMTP id 5so3436586vws.31 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 05:30:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.35.34 with SMTP id e2mr13983746vdj.52.1319200237364; Fri, 21 Oct 2011 05:30:37 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Fri, 21 Oct 2011 05:30:37 -0700 (PDT)
In-Reply-To: <0AA9DA1C-40F4-469E-9ECD-3EDA090F477F@voxeo.com>
References: <8E91C7B0-CE22-4CDA-8AC2-707EA5DA7716@acmepacket.com> <4EA15A31.50902@alvestrand.no> <0AA9DA1C-40F4-469E-9ECD-3EDA090F477F@voxeo.com>
Date: Fri, 21 Oct 2011 14:30:37 +0200
Message-ID: <CALiegf=AXq9X_kOTRzhdYn4zoHWE=iU9uGCRCLnGQcxXw1LRTA@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Dan Burnett <dburnett@voxeo.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] API draft: draft-kaplan-rtcweb-api-reqs-00
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: Fri, 21 Oct 2011 12:30:39 -0000

2011/10/21 Dan Burnett <dburnett@voxeo.com>;:
> And speaking as an editor in the W3C group to which you are referring, the point here is that protocol discussions are leading API discussions, and both are happening in the RTCWeb group, when the API discussions should all be happening in the W3C WebRTC group.  But, since JS API discussions are happening here, we now have a "no-signaling" draft in the IETF that lists requirements on the WebRTC API, *because the chairs asked for it*.

Hi Dan, I understand your point but please consider that this WG has
been involved in a discussion about the scope of such WebRTC API. It's
still unclear/undefined whether such API must only deal with media
aspects of the RTCweb stack in the browser, or whether it must also
deal with external signaling (in-the-wire).

Honestly I think that current works and proposals are helping a lot
for us to understand the whole picture. However I don't think that
this WG is attempting to define such API (which is a task of W3C) but
just to define its scope.

Regards.


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