Convertion between SDP Session Level and Media Level Attributes
draft-petithuguenin-mmusic-attributes-level-00

Abstract

This document also normatively updates RFC 5245 by mandating all new SDP attributes to be defined at both the session and media level, and to be accompanied by a normative algorithm to convert between the two levels.

Status of this Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on June 08, 2012.

Copyright Notice

Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

This document may not be modified, and derivative works of it may not be created, except to format it for publication as an RFC or to translate it into languages other than English.

Table of Contents

• 1. Introduction
• 2. Terminology
• 3. Security Considerations
• 4. IANA Considerations
• 5. Acknowledgements
• 6. References
• 6.1. Normative References
• 6.2. Informative References
• Appendix A. Examples
• Appendix B. Release notes
• Author's Address

1. Introduction

Not all the SDP [RFC4566] attributes are defined at both session and media level. This creates problems when SDP is used with disaggregated media (see section 3 of [I-D.loreto-splices-disaggregated-media]), as each m= line can be produced or consumed by a different implementation, perhaps even on a different physical device.

2. Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

"SHOULD", "SHOULD NOT", "RECOMMENDED", and "NOT RECOMMENDED" are appropriate when valid exceptions to a general requirement are known to exist or appear to exist, and it is infeasible or impractical to enumerate all of them. However, they should not be interpreted as permitting implementors to fail to implement the general requirement when such failure would result in interoperability failure.

3. Security Considerations

4. IANA Considerations

5. Acknowledgements

This document was written with the xml2rfc tool described in [RFC2629].

6. References

6.1. Normative References

6.2. Informative References

Appendix A. Examples

Appendix B. Release notes

This section must be removed before publication as an RFC.

Author's Address