RFC 7728: RTP Stream Pause and Resume
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7728
- Published
- February 2016
- Authors
- B. Burman; A. Akram; R. Even; M. Westerlund
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 55
- Also known as
- —
- Updates:
- RFC 5104
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6051Rapid Synchronisation of RTP FlowsCurrent
November 2010
- RFC 7825A Network Address Translator (NAT) Traversal Mechanism for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
December 2016
- RFC 7097RTP Control Protocol (RTCP) Extended Report (XR) for RLE of Discarded PacketsCurrent
January 2014
- RFC 6990RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG-2 Transport Stream (TS) Program Specific Information (PSI) Independent Decodability Statistics Metrics ReportingCurrent
August 2013
- RFC 6849An Extension to the Session Description Protocol (SDP) and Real-time Transport Protocol (RTP) for Media LoopbackCurrent
February 2013
- RFC 8845Framework for Telepresence Multi-StreamsCurrent
January 2021
- RFC 8858Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)Current
January 2021
- RFC 9991Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Failure ReportingCurrent
May 2026
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?