[AVTCORE] RFC 8108 on Sending Multiple RTP Streams in a Single RTP Session
rfc-editor@rfc-editor.org Tue, 07 March 2017 22:19 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6821129655; Tue, 7 Mar 2017 14:19:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BWbcgD6HZ0hA; Tue, 7 Mar 2017 14:19:20 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B7A512961C; Tue, 7 Mar 2017 14:18:52 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1D8FFB819B9; Tue, 7 Mar 2017 14:18:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170307221851.1D8FFB819B9@rfc-editor.org>
Date: Tue, 07 Mar 2017 14:18:51 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/afC3TAtgWEO7R3d8l62UNb9E_8A>
Cc: drafts-update-ref@iana.org, avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVTCORE] RFC 8108 on Sending Multiple RTP Streams in a Single RTP Session
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Mar 2017 22:19:22 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8108
Title: Sending Multiple RTP Streams in
a Single RTP Session
Author: J. Lennox, M. Westerlund,
Q. Wu, C. Perkins
Status: Standards Track
Stream: IETF
Date: March 2017
Mailbox: jonathan@vidyo.com,
magnus.westerlund@ericsson.com,
bill.wu@huawei.com,
csp@csperkins.org
Pages: 29
Characters: 74580
Updates: RFC 3550, RFC 4585
I-D Tag: draft-ietf-avtcore-rtp-multi-stream-11.txt
URL: https://www.rfc-editor.org/info/rfc8108
DOI: 10.17487/RFC8108
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.
This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC