IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Fri, 21 October 2011 11:24 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 5C84A21F8B56 for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 04:24:35 -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 WV1R2FLgoOqq for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 04:24:35 -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 CB5CE21F8B0C for <rtcweb@ietf.org>; Fri, 21 Oct 2011 04:24:34 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so3872345vcb.31 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 04:24:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.117.81 with SMTP id p17mr1012843vcq.41.1319196274344; Fri, 21 Oct 2011 04:24:34 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Fri, 21 Oct 2011 04:24:34 -0700 (PDT)
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852234235CE0@ESESSCMS0356.eemea.ericsson.se>
References: <8E91C7B0-CE22-4CDA-8AC2-707EA5DA7716@acmepacket.com> <CALiegfkqt-5nGFOVn=UtpQp+o9o_Bm99g=mH=C97paDUUykvUA@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852234235CE0@ESESSCMS0356.eemea.ericsson.se>
Date: Fri, 21 Oct 2011 13:24:34 +0200
Message-ID: <CALiegfmjRq2qkn2pyPuxDS4=1BYxKNiZU3zJTY7OeKjoLSD07g@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Christer Holmberg <christer.holmberg@ericsson.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 11:24:35 -0000

2011/10/21 Christer Holmberg <christer.holmberg@ericsson.com>:
> We need to specify what is to be used by the JS library developers. If they then design libraries that allow people to set up calls using 20 lines of code, fine, but how can WE enforce that to happen?
>
> I don't think we can say that the API WE specify shall allow setting up a call using 20 lines. We can only hope (and, of course, do whatever we can do in order to allow that to happen) that the API WE specify allows someone ELSE to produce a library which then allows users to set up calls using 20 lines :)

That's exactly what I meant :)

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

v2.23.0 | Report a Bug | By Email