Re: [rtcweb] Comments to use-cases/reqs document

Harald Alvestrand <harald@alvestrand.no> Mon, 11 July 2011 14:17 UTC

Return-Path: <harald@alvestrand.no>
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 69BFD21F8570 for <rtcweb@ietfa.amsl.com>; Mon, 11 Jul 2011 07:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.485
X-Spam-Level:
X-Spam-Status: No, score=-102.485 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 xLHdhmpgjTbn for <rtcweb@ietfa.amsl.com>; Mon, 11 Jul 2011 07:17:38 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id CBC2D21F8C1A for <rtcweb@ietf.org>; Mon, 11 Jul 2011 07:17:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 9925939E179 for <rtcweb@ietf.org>; Mon, 11 Jul 2011 16:16:25 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R4NEIDVT98VV for <rtcweb@ietf.org>; Mon, 11 Jul 2011 16:16:25 +0200 (CEST)
Received: from [192.168.1.53] (162.80-203-220.nextgentel.com [80.203.220.162]) by eikenes.alvestrand.no (Postfix) with ESMTPS id E622439E087 for <rtcweb@ietf.org>; Mon, 11 Jul 2011 16:16:24 +0200 (CEST)
Message-ID: <4E1B0607.6080202@alvestrand.no>
Date: Mon, 11 Jul 2011 16:17:43 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <4E0B0373.3040509@ericsson.com>
In-Reply-To: <4E0B0373.3040509@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [rtcweb] Comments to use-cases/reqs document
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: Mon, 11 Jul 2011 14:17:38 -0000

Just one comment-on-comment:

On 06/29/11 12:50, Stefan Håkansson LK wrote:
> All,
>
> some comments to
> <http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/?include_text=1> 
>
>
>
> 3. The "Video Size Change" use case derives F22; but that is already
> derived in "Simple Video Communication Service". I propose to remove 
> the "Video Size Change" use case.

I disagree with this proposal.
While the "resizing" requirement is in "simple video communication 
service" as
"The users can change the display sizes during the session", I believe 
the basic use case does not derive the requirement that the change in 
video size be communicated to the other party.

I would propose the following changes:
- Reinstate the text below:

4.2.4.  Video Size Change

4.2.4.1.  Description

    Alice and Bob are in a video call in their browsers and have
    negotiate a high resolution video.  Bob decides to change the size of
    the windows his browser is displaying video to a small size.

    Bob's browser regenerates the video codec paramters with Alice's
    browser to change the resolution of the video Alice sends to match
    the smaller size.

4.2.4.2.  Derived Requirements

    F22 ( It SHOULD be possible to modify video codec parameters during a
    session.)

- Change the text of F22 to be:

   It SHOULD be possible for one party to request a change in video 
codec parameters, such as size,
   during a session, and for the other party to react to this request.