Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio Codec
RFC 4348

Note: This ballot was opened for revision 11 and is now closed.

(Allison Mankin) Yes

(Brian Carpenter) No Objection

(Bill Fenner) No Objection

(Ted Hardie) (was Discuss) No Objection

Comment (2005-04-21 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
The document says:

6.4. Implementation Considerations

   An application implementing this payload format MUST
   understand all the payload parameters in the out-of-band
   signaling used. For example, if an application uses SDP, all 
   the SDP and MIME parameters in this document MUST be
   understood. This requirement ensures that an implementation
   always can decide if it is capable or not of communicating.

Can the document author or chairs explain what
the phrase "in the out-of-band-signaling used" is intended to mean
here?  That is, do the authors always mean the union of 
(the set of MIME parameters associated with this type) and
the (the set of mechanisms inherent in their chosen signaling
protocol), or do they mean that there will may be a limited subset
of parameters valid for a specific signaling protocol?  (After reading
the example, I came to the "union" conclusion, but then became
concerned that it might be different in non-SDP cases).

(Sam Hartman) No Objection

(Scott Hollenbeck) No Objection

(Russ Housley) (was Discuss, No Objection) No Objection

(David Kessens) No Objection

(Jon Peterson) No Objection

(Mark Townsley) No Objection

Comment (2005-04-24 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Just a minor oddity I noticed: "Variable-Rate Multimode Wideband" is referred to as "VMR-WB" vs. "VRM-WB"

I suspect this is so in order to align with AMR-WB (Adaptive Multi-Rate Wideband)

Perhaps VMR-WB should accordingly be named "Variable Multi-Rate" ?

(Bert Wijnen) No Objection

(Alex Zinin) No Objection