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

[Harald Alvestrand <[e-mail]>]

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.