[rtcweb] Requesting a new use case / requirement for draft-ietf-rtcweb-use-cases-and-requirements

Iñaki Baz Castillo <ibc@aliax.net> Tue, 30 July 2013 13:11 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0DF3B21F8436 for <rtcweb@ietfa.amsl.com>; Tue, 30 Jul 2013 06:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 0SZRRLzJhfzU for <rtcweb@ietfa.amsl.com>; Tue, 30 Jul 2013 06:11:38 -0700 (PDT)
Received: from mail-qe0-f47.google.com (mail-qe0-f47.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id DAF7521E80C0 for <rtcweb@ietf.org>; Tue, 30 Jul 2013 06:11:37 -0700 (PDT)
Received: by mail-qe0-f47.google.com with SMTP id b10so1606764qen.34 for <rtcweb@ietf.org>; Tue, 30 Jul 2013 06:11:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding:x-gm-message-state; bh=EMdfIkHxCduGvw/2aAkBUiI9u1GCfKc1irlfWR6uCQ0=; b=V11A6fNfeoIg8yqCqkmYILURJwUpkroMBXe5DwLjXsJmwfnjpRm7eItGiwLl9uNETw oqtWeEG1aYAyf5E0zrQKDqmGpocRSLFqL5QJ0+KJXUPafYOGI5RRHnLkGuhzBpQp1ZWx 6xSkfW1hGDGvSMwxaE8SUB8riCv0jEoLy1ZXsakwqwPwQDUu2fq0RtE5Y2DceAhNzBU0 F397udfn5XU3yD/0N1p7aGvPThP0nzvbxIfbqF5jhJPfQlnGjeaXtCPNkZTkEfcSfokG j41n0+5SQbpsQA2HrTHqKa7MSzUDPGdGwr1F86P54t0CQFFtcp7qdWLlzhleIZmMcTOu LANw==
X-Received: by with SMTP id fs2mr7215024qcb.68.1375189896090; Tue, 30 Jul 2013 06:11:36 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Tue, 30 Jul 2013 06:11:16 -0700 (PDT)
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Tue, 30 Jul 2013 15:11:16 +0200
Message-ID: <CALiegf=uFvE7-H_6a3fwApenUVdp8HAhOhh1f7YWbT0BQFt9Ug@mail.gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, draft-ietf-rtcweb-use-cases-and-requirements@tools.ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQl8FYchDASa0WjXKQ+FOzo65zT1XR6TACP1nPxFQdKg+XLY8bd6NpZP0FO9H1q6zbMfjYgK
Subject: [rtcweb] Requesting a new use case / requirement for 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: Tue, 30 Jul 2013 13:11:43 -0000

Hi, I would like to request a new use case / requirement for WebRTC to
be included in draft-ietf-rtcweb-use-cases-and-requirements:

Contacting a conference server

The browser must be able to generate a media offer to be sent to a
conference server, by providing its audio and video information (media
tracks to be sent by the browser), and the conference server must be
able to reply a single response accepting the offer and indicating the
browser all the media tracks from other participants it will send to
it. This must be possible without requiring a new media negotiation
round trip, and without requiring that the browser knows the number of
participants in the conference before contacting it.

Note that in this scenario the browser is the session initiator and
thus the media description offerer, while the conference server
provides the media description answer.

Thanks a lot.

Iñaki Baz Castillo