%% You should probably cite draft-ietf-mmusic-sdp-mux-attributes instead of this I-D.
@techreport{nandakumar-mmusic-sdp-mux-attributes-05,
    number =    {draft-nandakumar-mmusic-sdp-mux-attributes-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-nandakumar-mmusic-sdp-mux-attributes/05/},
    author =    {Suhas Nandakumar},
    title =     {{A Framework for SDP Attributes when Multiplexing}},
    pagetotal = 57,
    year =      2013,
    month =     oct,
    day =       20,
    abstract =  {The Session Description Protocol (SDP) provides mechanisms to describe attributes of multimedia sessions and of individual media streams (e.g., Real-time Transport Protocol (RTP) sessions) within a multimedia session. In the RTCWeb WG, there is a need to use a single 5-tuple for sending and receiving media associated with multiple media descriptions ("m=" lines). Such a requirement has raised concerns over the semantic implications of the SDP attributes associated with the RTP Sessions multiplexed over a single transport layer flow. The scope of this specification is to provide a framework for analyzing the multiplexing characteristics of SDP attributes. The specification also categorizes existing attributes based on the framework described herein.},
}