%% You should probably cite rfc8859 instead of this I-D. @techreport{ietf-mmusic-sdp-mux-attributes-07, number = {draft-ietf-mmusic-sdp-mux-attributes-07}, 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-mux-attributes/07/}, author = {Suhas Nandakumar}, title = {{A Framework for SDP Attributes when Multiplexing}}, pagetotal = 90, year = 2015, month = jan, day = 17, 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. Typically media associated with individual media descriptions ("m=" lines) represent seperate RTP Sessions and thus carried over individual underlying transport layer flows. For scenarios where SDP is used to negotiate the usage of single 5-tuple for sending and receiving media associated with multiple media descriptions, it is required to understand the semantic implications of the SDP attributes associated with the RTP Media Streams multiplexed over a single underlying transport layer flow. The purpose of this specification is to provide a framework for analyzing the multiplexing characteristics of SDP attributes. This specification also categorizes the existing SDP attributes based on the framework described herein.}, }