RFC 5022, "Media Server Control Markup Language (MSCML) and Protocol", September 2007Source of RFC: INDEPENDENT
Errata ID: 1233
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Rejected by: Nevil Brownlee
Date Rejected: 2011-03-28
Section 5.2 says:
Attributes of <configure_conference>: o reservedtalkers - optional (see note), no default value: The maximum number of talker legs allocated for the conference. Note: + required when establishing the Conference Control Leg but optional + in subsequent <configure_conference> requests. o reserveconfmedia - optional, default value "yes": Controls allocation of resources to enable playing or recording to or from ? the entire conference. ? ? When the reservedtalkers+1st INVITE arrives at the media server, the media server SHOULD generate a 486 Busy Here response. Failure to send a 486 response to this condition can cause the media server to oversubscribe its resources.
It should say:
< amended/clarified text should be supplied by authors >
The text spanning from page 12 to page 13 lacks of precision.
In the first bullet, it precisely specifies in which kind of leg
the attribute applies.
Similar information is missing entirely from the second bullet.
Also, it is not unambiguously clear whether "reservedtalkers+1st INVITE"
shall count the control leg or not.
Without added clarification, interoperability might suffer.
Authors response: In four years of deployment, no one has run into a real problem in the real world. No change needed.