Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
draft-ietf-mmusic-sdp-bundle-negotiation-38
|
| Document |
Type |
|
Active Internet-Draft (mmusic WG)
|
|
Last updated |
|
2017-04-12
|
|
Replaces |
|
draft-holmberg-mmusic-sdp-bundle-negotiation
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Consensus: Waiting for Write-Up
(wg milestone:
Feb 2017 - Submit SDP extension...
)
Revised I-D Needed - Issue raised by WG
|
|
Document shepherd |
|
Flemming Andreasen
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
MMUSIC Working Group C. Holmberg
Internet-Draft Ericsson
Updates: 3264 (if approved) H. Alvestrand
Intended status: Standards Track Google
Expires: October 14, 2017 C. Jennings
Cisco
April 12, 2017
Negotiating Media Multiplexing Using the Session Description Protocol
(SDP)
draft-ietf-mmusic-sdp-bundle-negotiation-38.txt
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 address:port combination (BUNDLE address) for receiving media,
referred to as bundled media, specified by multiple SDP media
descriptions ("m=" lines).
To assist endpoints in negotiating the use of bundle this
specification defines a new SDP attribute, 'bundle-only', which can
be used to request that specific media is only used if bundled. The
specification also updates RFC 3264, to allow usage of zero port
values without meaning that media is rejected.
There are multiple ways to correlate the bundled RTP packets with the
appropriate media descriptions. This specification defines a new
Real-time Transport Protocol (RTP) source description (SDES) item and
a new RTP header extension that provides an additional way to do this
correlation by using them to carry a value that associates the RTP/
RTCP packets with a specific media description.
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
Holmberg, et al. Expires October 14, 2017 [Page 1]
Internet-Draft Bundled media April 2017
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 October 14, 2017.
Copyright Notice
Copyright (c) 2017 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 contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. Applicability Statement . . . . . . . . . . . . . . . . . . . 7
5. SDP Grouping Framework BUNDLE Extension . . . . . . . . . . . 7
6. SDP 'bundle-only' Attribute . . . . . . . . . . . . . . . . . 8
7. SDP Information Considerations . . . . . . . . . . . . . . . 9
7.1. Connection Data (c=) . . . . . . . . . . . . . . . . . . 9
7.2. Bandwidth (b=) . . . . . . . . . . . . . . . . . . . . . 9
8. SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . . 9
Show full document text