Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)
draft-ietf-mmusic-mux-exclusive-12
Yes
(Alissa Cooper)
(Ben Campbell)
No Objection
(Alia Atlas)
(Alvaro Retana)
(Deborah Brungard)
(Jari Arkko)
(Kathleen Moriarty)
(Spencer Dawkins)
(Stephen Farrell)
(Suresh Krishnan)
(Terry Manderson)
Note: This ballot was opened for revision 09 and is now closed.
Alissa Cooper Former IESG member
Yes
Yes
(for -09)
Unknown
Ben Campbell Former IESG member
Yes
Yes
(for -09)
Unknown
Alexey Melnikov Former IESG member
No Objection
No Objection
(2016-08-03 for -09)
Unknown
In Section 3: The mux category [I-D.ietf-mmusic-sdp-mux-attributes] for the 'rtcp- mux-only' attribute is 'IDENTICAL', which means that the attribute, if used within a BUNDLE group [I-D.ietf-mmusic-sdp-bundle-negotiation], must be associated with all multiplexed RTP-based media descriptions within the BUNDLE group. This sounds pretty normative, so I think the following 2 references should be Normative: [I-D.ietf-mmusic-sdp-mux-attributes] Nandakumar, S., "A Framework for SDP Attributes when Multiplexing", draft-ietf-mmusic-sdp-mux-attributes-12 (work in progress), January 2016. [I-D.ietf-mmusic-sdp-bundle-negotiation] Holmberg, C., Alvestrand, H., and C. Jennings, "Negotiating Media Multiplexing Using the Session Description Protocol (SDP)", draft-ietf-mmusic-sdp-bundle- negotiation-31 (work in progress), June 2016.
Alia Atlas Former IESG member
No Objection
No Objection
(for -09)
Unknown
Alvaro Retana Former IESG member
No Objection
No Objection
(for -09)
Unknown
Deborah Brungard Former IESG member
No Objection
No Objection
(for -09)
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
(for -09)
Unknown
Joel Jaeggli Former IESG member
No Objection
No Objection
(2016-08-04 for -09)
Unknown
Tim Wicinski <tjw.ietf@gmail.com> performed the opsdir review.
Kathleen Moriarty Former IESG member
No Objection
No Objection
(for -09)
Unknown
Mirja Kühlewind Former IESG member
No Objection
No Objection
(2016-07-25 for -09)
Unknown
Quick question: My initial understanding was that newer systems usually support RTP/RTCP multiplexing, while older systems that do not support RTP/RTCP multiplexing will also not be able to understand this new attribut. So I guess that's not the use case. That means the use case if for newer system that do know about RTP/RTCP multiplexing as well as the 'rtcp-mux-only' attribute but don't support it for some reason. What are these reasons? Maybe you can provide some more background about the intended usage here! Minor: Some sentences are a little hard to pharse as they are quite long, e.g. OLD: "When an offerer sends the initial offer, if the offerer wants to indicate exclusive RTP/RTCP multiplexing for RTP-based media, the offerer MUST associate an SDP 'rtcp-mux-only' attribute with the associated SDP media description ("m=" line)." MAYBE: "If the offerer wants to indicate exclusive RTP/RTCP multiplexing for RTP-based media, the offerer MUST send the initial offer with an associated SDP 'rtcp-mux-only' attribute and the associated SDP media description ("m=" line)."
Spencer Dawkins Former IESG member
No Objection
No Objection
(for -09)
Unknown
Stephen Farrell Former IESG member
No Objection
No Objection
(for -09)
Unknown
Suresh Krishnan Former IESG member
No Objection
No Objection
(for -09)
Unknown
Terry Manderson Former IESG member
No Objection
No Objection
(for -09)
Unknown