Re: Draft new version: draft-ietf-mmusic-mux-exclusive-11
Eric Rescorla <[email protected]>
| Newsgroups | gmane.ietf.mmusic |
|---|---|
| Message-ID | <CABcZeBMNRG9oyKNoTZj6meHiuVKvescjRB1KV_N6sGF20f9hUg@mail.gmail.com> |
On Fri, Feb 17, 2017 at 9:04 AM, Paul Kyzivat <[email protected]> wrote: > On 2/17/17 3:46 AM, Christer Holmberg wrote: > >> Hi, >> >> Based on the comments from Ekr, I've submitted a new version of >> draft-mux-exclusive. >> >> The SDP 'rtcp-mux-only' attribute is now only allowed in SDP offers. >> > > With the new text the offerer never knows if the answerer supports > rtcp-mux-only. He only knows that the answerer supports rtcp-mux. > Yes. I don't think this matters for that O/A, but it might matter for subsequent > O/As. > Why? -Ekjr > At the least, I think section 4.5 is now confusing. For m-lines previously > negotiated with rtcp-mux-only, must the side that is sending a new offer > include the attribute again, while the side that is answering must *not* > include it? (Note the implications when the new offer is in the opposite > direction from the original one.) I think this will be somewhat of a pain - > perhaps more pain than simply always including it in all offers and answers. > > Thanks, > Paul > > > Regards, >> >> Christer >> >> >> -----Original Message----- >> From: mmusic [mailto:[email protected]] On Behalf Of >> [email protected] >> Sent: 17 February 2017 10:44 >> To: [email protected] >> Cc: [email protected] >> Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-mux-exclusive-11.txt >> >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This draft is a work item of the Multiparty Multimedia Session Control of >> the IETF. >> >> Title : Indicating Exclusive Support of RTP/RTCP >> Multiplexing using SDP >> Author : Christer Holmberg >> Filename : draft-ietf-mmusic-mux-exclusive-11.txt >> Pages : 12 >> Date : 2017-02-17 >> >> Abstract: >> This document defines a new SDP media-level attribute, 'rtcp-mux- >> only', that can be used by an endpoint to indicate exclusive support >> of RTP/RTCP multiplexing. The document also updates RFC 5761, by >> clarifying that an offerer can use a mechanism to indicate that it is >> not able to send and receive RTCP on separate ports. >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-mmusic-mux-exclusive/ >> >> There's also a htmlized version available at: >> https://tools.ietf.org/html/draft-ietf-mmusic-mux-exclusive-11 >> >> A diff from the previous version is available at: >> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-mux-exclusive-11 >> >> >> Please note that it may take a couple of minutes from the time of >> submission until the htmlized version and diff are available at >> tools.ietf.org. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> mmusic mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/mmusic >> >> _______________________________________________ >> mmusic mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/mmusic >> >> > _______________________________________________ > mmusic mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/mmusic > _______________________________________________ mmusic mailing list [email protected] https://www.ietf.org/mailman/listinfo/mmusic