Re: [rtcweb] I-D Action: draft-ietf-rtcweb-use-cases-and-requirements-01.txt
Arno Bakker <arno@cs.vu.nl> Thu, 04 August 2011 07:32 UTC
Return-Path: <a.bakker@vu.nl>
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 2DA2F21F8B68 for <rtcweb@ietfa.amsl.com>; Thu, 4 Aug 2011 00:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.234
X-Spam-Level:
X-Spam-Status: No, score=-4.234 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pZI63KTVS4I5 for <rtcweb@ietfa.amsl.com>; Thu, 4 Aug 2011 00:32:08 -0700 (PDT)
Received: from mailin.vu.nl (mailin.vu.nl [130.37.164.16]) by ietfa.amsl.com (Postfix) with ESMTP id 70B6A21F8B66 for <rtcweb@ietf.org>; Thu, 4 Aug 2011 00:32:08 -0700 (PDT)
Received: from PEXHB011B.vu.local (130.37.236.65) by mailin.vu.nl (130.37.164.16) with Microsoft SMTP Server (TLS) id 14.1.218.12; Thu, 4 Aug 2011 09:32:35 +0200
Received: from [130.37.193.73] (130.37.238.20) by mails.vu.nl (130.37.236.65) with Microsoft SMTP Server (TLS) id 14.1.218.12; Thu, 4 Aug 2011 09:32:21 +0200
Message-ID: <4E3A4B06.5090007@cs.vu.nl>
Date: Thu, 04 Aug 2011 09:32:22 +0200
From: Arno Bakker <arno@cs.vu.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <20110704113719.18992.44580.idtracker@ietfa.amsl.com> <4E395997.80803@jesup.org>
In-Reply-To: <4E395997.80803@jesup.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [130.37.238.20]
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-use-cases-and-requirements-01.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: arno@cs.vu.nl
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: Thu, 04 Aug 2011 07:32:09 -0000
On 03/08/2011 16:22, Randell Jesup wrote: >> A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-rtcweb-use-cases-and-requirements-01.txt > > >> 4.2.6. Multiparty video communication >> > > Note that this covers the request from Arno for peer-to-peer distribution. > Yes. But perhaps we should rephrase requirement F11 to "The browser MUST be able to transmit streams to at least one peer" (peer could be other browser or relay server) to more properly highlight the problem of insufficient upload in larger sessions. CU, Arno
- [rtcweb] I-D Action: draft-ietf-rtcweb-use-cases-… internet-drafts
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-use-ca… Randell Jesup
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-use-ca… Arno Bakker