Skip to main content

RFC 8108 - Sending Multiple RTP Streams in a Single RTP Session

  • Status: Proposed Standard
  • Published: March 2017
  • Stream: IETF
  • Updates: RFC 3550, RFC 4585
  • Errata: No Errata

Document Information​

  • RFC Number: 8108
  • Title: Sending Multiple RTP Streams in a Single RTP Session
  • Authors: J. Lennox (Vidyo), M. Westerlund (Ericsson), Q. Wu (Huawei), C. Perkins (University of Glasgow)
  • Date: March 2017
  • Category: Standards Track
  • Updates: RFC 3550, RFC 4585
  • ISSN: 2070-1721

Abstract​

This memo expands and clarifies the behavior of Real-time Transport Protocol (RTP) endpoints that use multiple synchronization sources (SSRCs). This occurs, for example, when an endpoint sends multiple RTP streams in a single RTP session. This memo updates RFC 3550 with regard to handling multiple SSRCs per endpoint in RTP sessions, with a particular focus on RTP Control Protocol (RTCP) behavior. It also updates RFC 4585 to change and clarify the calculation of the timeout of SSRCs and the inclusion of feedback messages.

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 7841.

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/rfc8108.

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.

Table of Contents​