Browse Prior Art Database

Sending Multiple RTP Streams in a Single RTP Session (RFC8108)

IP.com Disclosure Number: IPCOM000249619D
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-08
Document File: 58 page(s) / 74K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Lennox: AUTHOR [+4]

Abstract

At the time the Real-Time Transport Protocol (RTP) [RFC3550] was originally designed, and for quite some time after, endpoints in RTP sessions typically only transmitted a single media source and, thus, used a single RTP stream and synchronization source (SSRC) per RTP session, where separate RTP sessions were typically used for each distinct media type. Recently, however, a number of scenarios have emerged in which endpoints wish to send multiple RTP streams, distinguished by distinct RTP synchronization source (SSRC) identifiers, in a single RTP session. These are outlined in Section 3. Although the initial design of RTP did consider such scenarios, the specification was not consistently written with such use cases in mind; thus, the specification is somewhat unclear in places.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Internet Engineering Task Force (IETF)                         J. Lennox Request for Comments: 8108                                         Vidyo Updates: 3550, 4585                                        M. Westerlund Category: Standards Track                                       Ericsson ISSN: 2070-1721                                                    Q. Wu                                                                   Huawei                                                               C. Perkins                                                    University of Glasgow                                                               March 2017

           Sending Multiple RTP Streams in a Single RTP Session

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.

 Lennox, et al.               Standards Track                    [Page 1]
 RFC 8108        Multiple Media Streams in an RTP Session      March 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 restri...