Re: [rtcweb] Additional requirement - audio-only communication

Bernard Aboba <bernard_aboba@hotmail.com> Sat, 27 August 2011 17:45 UTC

Return-Path: <bernard_aboba@hotmail.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 4E88A21F85C6 for <rtcweb@ietfa.amsl.com>; Sat, 27 Aug 2011 10:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.38
X-Spam-Level:
X-Spam-Status: No, score=-102.38 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 FIfT6xi5WZ+M for <rtcweb@ietfa.amsl.com>; Sat, 27 Aug 2011 10:45:53 -0700 (PDT)
Received: from blu0-omc4-s36.blu0.hotmail.com (blu0-omc4-s36.blu0.hotmail.com [65.55.111.175]) by ietfa.amsl.com (Postfix) with ESMTP id 90A8D21F8564 for <rtcweb@ietf.org>; Sat, 27 Aug 2011 10:45:53 -0700 (PDT)
Received: from BLU152-W45 ([65.55.111.137]) by blu0-omc4-s36.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 27 Aug 2011 10:47:12 -0700
Message-ID: <BLU152-W45F92B13E693A3BB138B6093120@phx.gbl>
Content-Type: multipart/alternative; boundary="_eb913a86-aa96-44b2-9637-85db1f139037_"
X-Originating-IP: [98.203.198.61]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <stewe@stewe.org>, <rtcweb@ietf.org>
Date: Sat, 27 Aug 2011 10:47:12 -0700
Importance: Normal
In-Reply-To: <CA7E6671.3035D%stewe@stewe.org>
References: <BLU152-W2519098D92E87F138A4B1293120@phx.gbl>, <CA7E6671.3035D%stewe@stewe.org>
MIME-Version: 1.0
X-OriginalArrivalTime: 27 Aug 2011 17:47:12.0707 (UTC) FILETIME=[59FCF130:01CC64E1]
Subject: Re: [rtcweb] Additional requirement - audio-only communication
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: Sat, 27 Aug 2011 17:45:54 -0000

The W3C WEBRTC wiki (which includes links to archives, tracker, editor's draft, etc.) is available here: http://www.w3.org/2011/04/webrtc/wiki/Main_Page

Currently a link points to a W3C editor's draft dated 23 August 2011: http://dev.w3.org/2011/webrtc/editor/webrtc.html
Date: Sat, 27 Aug 2011 09:19:09 -0400
From: stewe@stewe.org
To: rtcweb@ietf.org
Subject: Re: [rtcweb] Additional requirement - audio-only communication



Or perhaps pointers on this list to the newest version every now and then (whenever a major update has happened)?Specifically, is Harald's draft from March 24 still the one to look at?(The companion lists have quite a bit of traffic, and there are only so many cycles per day to monitor those, especially if API design is not in your core interest or competency).Thanks,Stephan

From:  Bernard Aboba <bernard_aboba@hotmail.com>;
Date:  Sat, 27 Aug 2011 08:55:06 -0700
To:  <stefan.lk.hakansson@ericsson.com>;, <rtcweb@ietf.org>;
Subject:  Re: [rtcweb] Additional requirement - audio-only communication


[BA] Agreed that there seems to be some misconceptions about what the current API proposal can do. 

To clear this up, would it make sense to have a (brief) presentation on the API at the interim?

 		 	   		  _______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb


_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb