RTP Stream Pause and Resume
RFC 7728
| Document | Type |
RFC - Proposed Standard
(February 2016; Errata)
Updates RFC 5104
|
|
|---|---|---|---|
| Authors | Bo Burman , Azam Akram , Roni Even , Magnus Westerlund | ||
| Last updated | 2020-01-21 | ||
| Replaces | draft-westerlund-avtext-rtp-stream-pause | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized with errata bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Jonathan Lennox | ||
| Shepherd write-up | Show (last changed 2015-06-08) | ||
| IESG | IESG state | RFC 7728 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Ben Campbell | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) B. Burman
Request for Comments: 7728 A. Akram
Updates: 5104 Ericsson
Category: Standards Track R. Even
ISSN: 2070-1721 Huawei Technologies
M. Westerlund
Ericsson
February 2016
RTP Stream Pause and Resume
Abstract
With the increased popularity of real-time multimedia applications,
it is desirable to provide good control of resource usage, and users
also demand more control over communication sessions. This document
describes how a receiver in a multimedia conversation can pause and
resume incoming data from a sender by sending real-time feedback
messages when using the Real-time Transport Protocol (RTP) for real-
time data transport. This document extends the Codec Control Message
(CCM) RTP Control Protocol (RTCP) feedback package by explicitly
allowing and describing specific use of existing CCMs and adding a
group of new real-time feedback messages used to pause and resume RTP
data streams. This document updates RFC 5104.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7728.
Burman, et al. Standards Track [Page 1]
RFC 7728 RTP Stream Pause February 2016
Copyright Notice
Copyright (c) 2016 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.
Burman, et al. Standards Track [Page 2]
RFC 7728 RTP Stream Pause February 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6
2.3. Requirements Language . . . . . . . . . . . . . . . . . . 7
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1. Point to Point . . . . . . . . . . . . . . . . . . . . . 8
3.2. RTP Mixer to Media Sender . . . . . . . . . . . . . . . . 9
3.3. RTP Mixer to Media Sender in Point to Multipoint . . . . 10
3.4. Media Receiver to RTP Mixer . . . . . . . . . . . . . . . 11
3.5. Media Receiver to Media Sender across RTP Mixer . . . . . 11
4. Design Considerations . . . . . . . . . . . . . . . . . . . . 12
4.1. Real-Time Nature . . . . . . . . . . . . . . . . . . . . 12
4.2. Message Direction . . . . . . . . . . . . . . . . . . . . 12
4.3. Apply to Individual Sources . . . . . . . . . . . . . . . 12
4.4. Consensus . . . . . . . . . . . . . . . . . . . . . . . . 13
4.5. Message Acknowledgments . . . . . . . . . . . . . . . . . 13
Show full document text