section 5 of the requirements document

Looking through section 5 ("Design Considerations and Remarks"), it
seems to me that most of the content has been captured elsewhere in the
requirements, or is sufficiently handled by current proposals that we
could remove it from the scenarios document.  There are two things that
I think we should capture elsewhere though:

 

1)       Sections 5.5 and 5.6 on pre- and post-processing discuss
features like automatic gain control and image scaling.  The specific
techniques for performing these operations are probably outside our
scope, but we should make sure that our API makes it easy to slot them
in once they are defined.  Maybe we can do this as part of the recording
work.  (I'm thinking of something along the lines of a class that takes
a MediaStream as input and produces a modified stream as output.)  In
any case, there hasn't been much discussion of how to enable media
processing, and we should take it as an action item to do so.

2)      In section 5.8 there is mention of one participant in a video
conference sending a request over a PeerConnection to ask another
participant to mute.  This issue of modification/control of a remote
device has come up a couple of times, but without much follow-up.  We
should take an action item to decide if it is in scope, and, if so, how
to enable it.  (I know that PeerConnection belongs to WebRTC, but our
scenarios document covers their work as well.)

 

Finally, it should be stated clearly somewhere whether the "trapezoid"
use case is in scope or not (again, that's a WebRTC issue, but there's
only one scenarios document.)

 

I'll wait a week for comments and suggestions before starting to remove
section 5.  

 

-          Jim