draft-ietf-mmusic-rfc3388bis-01.txt   draft-ietf-mmusic-rfc3388bis-02.txt 
MMUSIC Working Group G. Camarillo MMUSIC Working Group G. Camarillo
Internet-Draft Ericsson Internet-Draft Ericsson
Obsoletes: 3388 (if approved) July 7, 2008 Obsoletes: 3388 (if approved) January 13, 2009
Intended status: Standards Track Intended status: Standards Track
Expires: January 8, 2009 Expires: July 17, 2009
The SDP (Session Description Protocol) Grouping Framework The SDP (Session Description Protocol) Grouping Framework
draft-ietf-mmusic-rfc3388bis-01.txt draft-ietf-mmusic-rfc3388bis-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 8, 2009. This Internet-Draft will expire on July 17, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 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.
Abstract Abstract
In this specification, we define a framework to group "m" lines in In this specification, we define a framework to group "m" lines in
SDP (Session Description Protocol) for different purposes. This SDP (Session Description Protocol) for different purposes. This
framework uses the "group" and "mid" SDP attributes, both of which framework uses the "group" and "mid" SDP attributes, both of which
are defined in this specification. Additionally, we specify how to are defined in this specification. Additionally, we specify how to
use the framework for two different purposes: for lip synchronization use the framework for two different purposes: for lip synchronization
and for receiving a media flow consisting of several media streams on and for receiving a media flow consisting of several media streams on
different transport addresses. different transport addresses.
skipping to change at page 2, line 42 skipping to change at page 3, line 4
9.4. Backward Compatibility . . . . . . . . . . . . . . . . . . 17 9.4. Backward Compatibility . . . . . . . . . . . . . . . . . . 17
9.4.1. Offerer does not Support "group" . . . . . . . . . . . 17 9.4.1. Offerer does not Support "group" . . . . . . . . . . . 17
9.4.2. Answerer does not Support "group" . . . . . . . . . . 17 9.4.2. Answerer does not Support "group" . . . . . . . . . . 17
10. Changes from RFC 3388 . . . . . . . . . . . . . . . . . . . . 18 10. Changes from RFC 3388 . . . . . . . . . . . . . . . . . . . . 18
11. Security Considerations . . . . . . . . . . . . . . . . . . . 18 11. Security Considerations . . . . . . . . . . . . . . . . . . . 18
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
13.1. Normative References . . . . . . . . . . . . . . . . . . . 19 13.1. Normative References . . . . . . . . . . . . . . . . . . . 19
13.2. Informational References . . . . . . . . . . . . . . . . . 19 13.2. Informational References . . . . . . . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19
Intellectual Property and Copyright Statements . . . . . . . . . . 21
1. Introduction 1. Introduction
An SDP [RFC4566] session description typically contains one or more An SDP [RFC4566] session description typically contains one or more
media lines, which are commonly known as "m" lines. When a session media lines, which are commonly known as "m" lines. When a session
description contains more than one "m" line, SDP does not provide any description contains more than one "m" line, SDP does not provide any
means to express a particular relationship between two or more of means to express a particular relationship between two or more of
them. When an application receives an SDP session description with them. When an application receives an SDP session description with
more than one "m" line, it is up to the application what to do with more than one "m" line, it is up to the application what to do with
them. SDP does not carry any information about grouping media them. SDP does not carry any information about grouping media
skipping to change at page 21, line 4 skipping to change at line 863
Author's Address Author's Address
Gonzalo Camarillo Gonzalo Camarillo
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
Jorvas 02420 Jorvas 02420
Finland Finland
Email: Gonzalo.Camarillo@ericsson.com Email: Gonzalo.Camarillo@ericsson.com
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 8 change blocks. 
10 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/