Skip to main content

Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio Codec
draft-ietf-avt-rtp-vmr-wb-11

Yes

(Allison Mankin)

No Objection

(Alex Zinin)
(Bert Wijnen)
(Bill Fenner)
(Brian Carpenter)
(David Kessens)
(Jon Peterson)
(Russ Housley)
(Sam Hartman)
(Scott Hollenbeck)

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

Allison Mankin Former IESG member
Yes
Yes () Unknown

                            
Alex Zinin Former IESG member
No Objection
No Objection () Unknown

                            
Bert Wijnen Former IESG member
No Objection
No Objection () Unknown

                            
Bill Fenner Former IESG member
No Objection
No Objection () Unknown

                            
Brian Carpenter Former IESG member
No Objection
No Objection () Unknown

                            
David Kessens Former IESG member
No Objection
No Objection () Unknown

                            
Jon Peterson Former IESG member
No Objection
No Objection () Unknown

                            
Mark Townsley Former IESG member
No Objection
No Objection (2005-04-24) Unknown
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" ?
Russ Housley Former IESG member
(was Discuss, No Objection) No Objection
No Objection () Unknown

                            
Sam Hartman Former IESG member
No Objection
No Objection () Unknown

                            
Scott Hollenbeck Former IESG member
No Objection
No Objection () Unknown

                            
Ted Hardie Former IESG member
(was Discuss) No Objection
No Objection (2005-04-21) Unknown
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).