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

Magnus Westerlund <magnus.westerlund@ericsson.com> Fri, 21 October 2011 11:21 UTC

Return-Path: <magnus.westerlund@ericsson.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 E2B1921F8AEE for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 04:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.44
X-Spam-Level:
X-Spam-Status: No, score=-106.44 tagged_above=-999 required=5 tests=[AWL=-0.068, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 K1zBw4EbeSUx for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 04:21:36 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF0921F8AEC for <rtcweb@ietf.org>; Fri, 21 Oct 2011 04:21:34 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-fd-4ea155bd504c
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 1A.D4.13753.DB551AE4; Fri, 21 Oct 2011 13:21:33 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.137.0; Fri, 21 Oct 2011 13:21:32 +0200
Message-ID: <4EA155BB.5090000@ericsson.com>
Date: Fri, 21 Oct 2011 13:21:31 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <8E91C7B0-CE22-4CDA-8AC2-707EA5DA7716@acmepacket.com>
In-Reply-To: <8E91C7B0-CE22-4CDA-8AC2-707EA5DA7716@acmepacket.com>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
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:21:37 -0000

Thanks Hadriel and your co-authors.

This documents section 5 do show a bit what level of requirements that
arise from this design. The thing I think I am still wondering of is how
to satisfy the timing constraints some of our on the wire protocol puts
on session management in the JS.

I would also have like a bit of discussion of how to arrive at
interoperability as this will be a function of the JS and the server.

But considering the tight timing I appreciate what you produced.

Cheers

Magnus

On 2011-10-21 11:39, 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. :)
> 
> 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
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------