Last Call: <draft-ietf-straw-b2bua-rtcp-13.txt> (Guidelines to support RTCP end-to-end in Back-to-Back User Agents (B2BUAs)) to Proposed Standard

The IESG <> Mon, 26 September 2016 15:24 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 402AB12B125; Mon, 26 Sep 2016 08:24:57 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-straw-b2bua-rtcp-13.txt> (Guidelines to support RTCP end-to-end in Back-to-Back User Agents (B2BUAs)) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 26 Sep 2016 08:24:57 -0700
Archived-At: <>
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 26 Sep 2016 15:24:57 -0000

The IESG has received a request from the Sip Traversal Required for
Applications to Work WG (straw) to consider the following document:
- 'Guidelines to support RTCP end-to-end in Back-to-Back User Agents
  <draft-ietf-straw-b2bua-rtcp-13.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2016-10-10. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   SIP Back-to-Back User Agents (B2BUAs) are often envisaged to also be
   on the media path, rather than just intercepting signalling.  This
   means that B2BUAs often implement an RTP/RTCP stack as well, thus
   leading to separate multimedia sessions that the B2BUA correlates and
   bridges together.  If not disciplined, though, 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
   also acting on the signalling/media plane in order to preserve the
   end-to-end functionality of RTCP.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc7656: A Taxonomy of Semantics and Mechanisms for Real-Time Transport Protocol (RTP) Sources (Informational - IETF stream)
Note that some of these references may already be listed in the acceptable Downref Registry.