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

Harald Alvestrand <harald@alvestrand.no> Fri, 21 October 2011 11:40 UTC

Return-Path: <harald@alvestrand.no>
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 9E33821F8B59 for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 04:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.486
X-Spam-Level:
X-Spam-Status: No, score=-110.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 7UFMIXfDXrfH for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 04:40:32 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id EA09221F84A4 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 04:40:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3ACC839E08B; Fri, 21 Oct 2011 13:40:31 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q44zMLbH80W8; Fri, 21 Oct 2011 13:40:30 +0200 (CEST)
Received: from [192.168.1.58] (162.80-203-220.nextgentel.com [80.203.220.162]) by eikenes.alvestrand.no (Postfix) with ESMTPS id A8B6439E088; Fri, 21 Oct 2011 13:40:30 +0200 (CEST)
Message-ID: <4EA15A31.50902@alvestrand.no>
Date: Fri, 21 Oct 2011 13:40:33 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <8E91C7B0-CE22-4CDA-8AC2-707EA5DA7716@acmepacket.com>
In-Reply-To: <8E91C7B0-CE22-4CDA-8AC2-707EA5DA7716@acmepacket.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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:40:32 -0000

On 10/21/2011 11:39 AM, Hadriel Kaplan wrote:
> Howdy,
> we've posted an initial strawman for "API requirements" for "no signaling" as our chairs have asked for for the con call.
> I'm still not sure why we need to provide this in an I-D, but given only a few days notice and having other day jobs, we've tried our best in the short timeframe.
>
> Note: given the announced conf call for Friday (today?), I've submitted this version without getting final proof-reading from the other authors.  So some new bits I wrote they may not agree with... in fact some bits I wrote *I* may not agree with, given how late it is at night for me (well I guess early in the morning technically).  Caveat emptor. :)
Thank you, this document was most informative to me, and illustrated the 
position taken well (although I disagree with its conclusions).

It also served very nicely to illustrate the breadth of functionality 
that a "low level API" needs to expose.

One note (speaking as a W3C WG chair): While it's very nice to imagine 
that one can toss a task like "design an API" over to another 
organization and having it performed, in practice, the W3C functions 
much like the IETF; it's not a place where you throw work in order to 
get work done, it's a place where people who need the work done go to 
work on the problem.

But we all knew that, I think....

> Link details below.
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
> 	Title           : API Requirements for RTCWEB-enabled Browsers
> 	Author(s)       : Hadriel Kaplan
>                           Dan Burnett
>                           Neil Stratford
>                           Tim Panton
> 	Filename        : draft-kaplan-rtcweb-api-reqs-00.txt
> 	Pages           : 13
> 	Date            : 2011-10-21
>
>    This document discusses the advantages and disadvantages of several
>    proposed approaches to what type of API and architectural model
>    RTCWeb Browsers should expose and use.  The document then defines
>    the requirements for an API that treats the Browser as a library and
>    interface as opposed to a self-contained application agent.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-kaplan-rtcweb-api-reqs-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-kaplan-rtcweb-api-reqs-00.txt
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>