Re: [rtcweb] More Comments on draft-ietf-rtcweb-use-cases-and-requirements-07

Ted Hardie <ted.ietf@gmail.com> Sun, 10 June 2012 16:48 UTC

Return-Path: <ted.ietf@gmail.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 3B79821F85A0 for <rtcweb@ietfa.amsl.com>; Sun, 10 Jun 2012 09:48:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 TQ2IyizwZhw3 for <rtcweb@ietfa.amsl.com>; Sun, 10 Jun 2012 09:48:21 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 42EA921F8597 for <rtcweb@ietf.org>; Sun, 10 Jun 2012 09:48:21 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so2091460vcq.31 for <rtcweb@ietf.org>; Sun, 10 Jun 2012 09:48:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=lzggdgYfRz+CmhrwZaznr/nT6kZTmxIp2bP7AGRRSR0=; b=CkM4wk1GiRYZL6QjM1uyQ4RzFmO7jcQVL5ta11/7/R8uieV3gBpFy8L3T1AxyKEH/G VQgCq30jGkpKPP32/MDXo/L2yev6dK2DzMfi0qK6l+ZV5BFyEFUVkw9+1dTMwkraec8l pGaz999pMkbZX5ky6NkD3lmfBBgq3+ThVeGHb9g3kU1XPkyx5JWg4hj3uI8USQtH24cW o4SxKX+QlcQhJdNYQpp2r40AGD9FWgnagem7bNvMeAsnA7aiJeh1goH+X19+XhNG2uGu zYb1IOtnd5EKQJHdJVgVAPC3EOWZY13QSCFMo5N0Wd9VNUNsKiiPgmeb8K4BFPLBPIRo qsgQ==
MIME-Version: 1.0
Received: by 10.52.21.99 with SMTP id u3mr9417371vde.56.1339346900272; Sun, 10 Jun 2012 09:48:20 -0700 (PDT)
Received: by 10.52.37.51 with HTTP; Sun, 10 Jun 2012 09:48:20 -0700 (PDT)
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF021B53@MCHP04MSX.global-ad.net>
References: <5A2F246E-9D77-4B72-B3F1-681B00FA99FD@cisco.com> <F3D4ABD6AB47084B84337CF4F3446A464B2F11B52E@ESESSCMS0362.eemea.ericsson.se> <AAB6A6B6-BEC7-436C-B1EB-2C117596C7C6@cisco.com> <F3D4ABD6AB47084B84337CF4F3446A464B2F2631AC@ESESSCMS0362.eemea.ericsson.se> <9F33F40F6F2CD847824537F3C4E37DDF021B53@MCHP04MSX.global-ad.net>
Date: Sun, 10 Jun 2012 18:48:20 +0200
Message-ID: <CA+9kkMCL1k3x2hYi632nDU2g6CtOq3O7risDi38+7FTeWkxcGA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] More Comments on draft-ietf-rtcweb-use-cases-and-requirements-07
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: Sun, 10 Jun 2012 16:48:22 -0000

On Sun, Jun 10, 2012 at 5:33 PM, Hutton, Andrew
<andrew.hutton@siemens-enterprise.com> wrote:
> Hi,
>

> Section 4.1.1.1 (Simple Video Communication Service) contains the statement "Each user can also pause sending of media (audio, video, or both) and mute incoming media".  I think this and the associated requirements need some clarification for example whether the requirement is to control the direction of the media and therefore requires the generation of a new SDP offer with for example a direction of "recvonly/inactive".

Howdy,

As a clarifying question, are you thinking that it is not clear
because non-signaling methods could achieve some of these?  That is
"muting" incoming media could also be accomplished entirely receive
side, by simply not rendering it?

regards,

Ted

 The only associated requirement seems to be A8 but this does not help
clarify what is meant by "pause" in the use case. It needs to be
clarified whether the pause/resume/mute are actions within the browser
or are actions which result in notifications to the remote user.
>
> Maybe we could add a use case which involves controlling the direction of multiple streams to emulate switching between different users in a multiparty call scenario.
>
>
> The statement "It is essential that the communication cannot be eavesdropped" appears in all use cases so could be moved to section 4.1 but I think it needs to be reworded in terms of the media always being encrypted as I don't like the term "eavesdropped" which is not defined.
>
> Regards
> Andy
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb