[rtcweb] Comment on draft-ietf-rtcweb-use-cases-and-requirements

David Hancock <D.Hancock@CableLabs.com> Thu, 08 August 2013 16:57 UTC

Return-Path: <D.Hancock@CableLabs.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 D978221F9FF7 for <rtcweb@ietfa.amsl.com>; Thu, 8 Aug 2013 09:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level:
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 a15fsga-IFL0 for <rtcweb@ietfa.amsl.com>; Thu, 8 Aug 2013 09:57:34 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id B532C21F9FF3 for <rtcweb@ietf.org>; Thu, 8 Aug 2013 09:57:34 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.7/8.14.7) with ESMTP id r78GvXho032343 for <rtcweb@ietf.org>; Thu, 8 Aug 2013 10:57:33 -0600
Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Thu, 08 Aug 2013 10:57:33 -0600 (MDT)
X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com)
Received: from EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee]) by EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee%11]) with mapi id 14.03.0146.000; Thu, 8 Aug 2013 10:57:33 -0600
From: David Hancock <D.Hancock@CableLabs.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Comment on draft-ietf-rtcweb-use-cases-and-requirements
Thread-Index: AQHOlFhgBvDn/5anCkio0rtFDxj6Sw==
Date: Thu, 8 Aug 2013 16:57:33 +0000
Message-ID: <CE291702.39859%d.hancock@cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.5.121010
x-originating-ip: [10.4.0.40]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <48CA966223489F45A784C0D9524C10B1@cablelabs.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
Subject: [rtcweb] Comment on draft-ietf-rtcweb-use-cases-and-requirements
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: Thu, 08 Aug 2013 16:57:40 -0000

A comment on the WebRTC use-case draft related to media sources...

Requirement F1 says local mic/cameras can be used as media sources.

    "F1      The browser must be able to use microphones and
        cameras as input devices to generate streams."

I've been told that a media source can also be an incoming media stream
from a peer, for example, where Browser-B relays media received from
Browser-A to Browser-C, like thisŠ

    +---+    +---+    +---+
    | A |--->| B |--->| C |
    +---+    +---+    +---+

Likewise with the data channel ‹ a WebRTC browser should be able to relay
data-channel data from one browser to another.

I think this is a useful capability, but I don't see it stated anywhere in
the use-case document.

I suggest we add a requirement covering this. Here's some proposed text...

    "Fx The browser must be able to relay incoming media or data streams
to a peer."



Thanks
David Hancock