%% You should probably cite rfc8843 instead of this I-D.
@techreport{ietf-mmusic-sdp-bundle-negotiation-50,
    number =    {draft-ietf-mmusic-sdp-bundle-negotiation-50},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-bundle-negotiation/50/},
    author =    {Christer Holmberg and Harald T. Alvestrand and Cullen Fluffy Jennings},
    title =     {{Negotiating Media Multiplexing Using the Session Description Protocol (SDP)}},
    pagetotal = 68,
    year =      2018,
    month =     apr,
    day =       24,
    abstract =  {This specification defines a new Session Description Protocol (SDP) Grouping Framework extension, 'BUNDLE'. The extension can be used with the SDP Offer/Answer mechanism to negotiate the usage of a single transport (5-tuple) for sending and receiving media described by multiple SDP media descriptions ("m=" sections). Such transport is referred to as a BUNDLE transport, and the media is referred to as bundled media. The "m=" sections that use the BUNDLE transport form a BUNDLE group. This specification updates RFC 3264, to allow assigning a zero port value to a "m=" section also in cases where the media described by the "m=" section is not disabled or rejected. This specification defines a new RTP Control Protocol (RTCP) source description (SDES) item and a new RTP header extension that can be used to correlate bundled RTP/RTCP packets with their appropriate "m=" section. This specification updates RFC 7941, by adding an exception, for the MID RTP header extension, to the requirement regarding protection of an SDES RTP header extension carrying an SDES item for the MID RTP header extension.},
}