[MEDIACTRL] (no subject)

["MUNSON, GARY A, ATTLABS" <[e-mail]>]

Hi Lorenzo, Chris,

My colleague Bob Epley has flagged a few more corrections (we believe)
for the mrb interface spec

1)	P20, active-mix, line 4:  elements -> element  

2)	P37, 5.2.4.1.2.2, supported-format - should be 'required-format'
here.  "supported" is correct in the Publish interface (Section
5.1.4.10) but it should be "required" in the consumer interface, as it
is in 5.2.4.1.3.2 (under mixerInfo).  This paragraph also leaves out the
sentence "A valid value is a MIME media type which, depending on its
definition, can include additional parameters (e.g., [RFC4281])"  that
appears in the similar sections on -supported- under the Publish
interface. We think that belongs here as well. 

3)	P42, 5.2.4.1.3.1,  mix, line 4:  <codec> -> <rtp-codec>
Likewise in Section 8, near the bottom of p104. 

4)	P46, last sentence in encryption section:  Should say "The
<encryption> element has no child elements.">


We have a couple questions as well.

a)	Section 5.1.4.17  For vxml-support / vxml-mode, RFC 5552 and the
IVR Package are cited as examples. Would RFC 4220 be another appropriate
example (that just didn't happen to get mentioned)?
		
b)	Audio and video mixing modes are left unspecified (i.e., there's
no enumeration, there's no reference to another spec). I believe that's
to allow for whatever modes vendors provide, some of which may
proprietary. So there is no good 'standard' list of mixing modes to
cite/reference. Is our understanding correct?
		
BR,

Gary