Re: [rtcweb] Proposed text - remote recording use case

Iñaki Baz Castillo <ibc@aliax.net> Fri, 16 September 2011 15:22 UTC

Return-Path: <ibc@aliax.net>
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 0243C21F8C5C for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 08:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level:
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 6WQ6K91+gaNi for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 08:22:29 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 4620D21F8C57 for <rtcweb@ietf.org>; Fri, 16 Sep 2011 08:22:29 -0700 (PDT)
Received: by qyk33 with SMTP id 33so4017978qyk.10 for <rtcweb@ietf.org>; Fri, 16 Sep 2011 08:24:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.204.73 with SMTP id fl9mr2073774qab.328.1316186683688; Fri, 16 Sep 2011 08:24:43 -0700 (PDT)
Received: by 10.229.79.207 with HTTP; Fri, 16 Sep 2011 08:24:43 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CA0BC110FA00@MCHP058A.global-ad.net>
References: <A444A0F8084434499206E78C106220CA0B04921B16@MCHP058A.global-ad.net> <2E239D6FCD033C4BAF15F386A979BF510F09ED@sonusinmail02.sonusnet.com> <8357A942-21EA-4209-82DB-ADFCEB5F32EF@acmepacket.com> <A444A0F8084434499206E78C106220CA0BC0F38C34@MCHP058A.global-ad.net> <2E239D6FCD033C4BAF15F386A979BF510F0B4E@sonusinmail02.sonusnet.com> <A444A0F8084434499206E78C106220CA0BC110F5F0@MCHP058A.global-ad.net> <2E239D6FCD033C4BAF15F386A979BF510F0C8A@sonusinmail02.sonusnet.com> <A444A0F8084434499206E78C106220CA0BC110FA00@MCHP058A.global-ad.net>
Date: Fri, 16 Sep 2011 17:24:43 +0200
Message-ID: <CALiegfk45RUifXh3YG30qNV2UgA-0BBYqE0CiBT4gO+hx=YYtQ@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Proposed text - remote recording use case
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, 16 Sep 2011 15:22:30 -0000

2011/9/16 Elwell, John <john.elwell@siemens-enterprise.com>om>:
> RTC-Web is specifying:

> - the browser API (W3C); and

> - protocols that the browser uses for browser-to-browser communication (IETF).

AFAIK those protocols just cover the media plane, but not the signaling plane.


> Any use of WebSockets for communication between JS and elsewhere is not within scope, as far as I understand.

I agree.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>