[straw] RFC 8079 on Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs)
rfc-editor@rfc-editor.org Thu, 23 February 2017 00:26 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: straw@ietfa.amsl.com
Delivered-To: straw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7729C129CF4; Wed, 22 Feb 2017 16:26:18 -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 lIEC41eFa9ey; Wed, 22 Feb 2017 16:26:11 -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 A8015129CFF; Wed, 22 Feb 2017 16:26:02 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 94F09B8192E; Wed, 22 Feb 2017 16:26:02 -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: <20170223002602.94F09B8192E@rfc-editor.org>
Date: Wed, 22 Feb 2017 16:26:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/straw/jOR_q17FXrpjQ-dGrLklkThE0rc>
Cc: drafts-update-ref@iana.org, straw@ietf.org, rfc-editor@rfc-editor.org
Subject: [straw] RFC 8079 on Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs)
X-BeenThere: straw@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Sip Traversal Required for Applications to Work \(STRAW\) working group discussion list" <straw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/straw>, <mailto:straw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/straw/>
List-Post: <mailto:straw@ietf.org>
List-Help: <mailto:straw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/straw>, <mailto:straw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 00:26:18 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8079
Title: Guidelines for End-to-End Support of
the RTP Control Protocol (RTCP) in
Back-to-Back User Agents (B2BUAs)
Author: L. Miniero, S. Garcia Murillo, V. Pascual
Status: Standards Track
Stream: IETF
Date: February 2017
Mailbox: lorenzo@meetecho.com,
sergio.garcia.murillo@gmail.com,
victor.pascual.avila@oracle.com
Pages: 16
Characters: 41687
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-straw-b2bua-rtcp-17.txt
URL: https://www.rfc-editor.org/info/rfc8079
DOI: 10.17487/RFC8079
SIP Back-to-Back User Agents (B2BUAs) are often designed to also be
on the media path, rather than just to intercept signalling. This
means that B2BUAs often implement an RTP or RTP Control Protocol
(RTCP) stack as well, thus leading to separate multimedia sessions
that the B2BUA correlates and bridges together. If not disciplined,
this behaviour can severely impact the communication experience,
especially when statistics and feedback information contained in RTCP
messages get lost because of mismatches in the reported data.
This document defines the proper behaviour B2BUAs should follow when
acting on both the signalling plane and media plane in order to
preserve the end-to-end functionality of RTCP.
This document is a product of the Sip Traversal Required for Applications to Work 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