RFC 6679 on Explicit Congestion Notification (ECN) for RTP over UDP

rfc-editor@rfc-editor.org Thu, 02 August 2012 19:01 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id C860811E827E; Thu, 2 Aug 2012 12:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.989
X-Spam-Status: No, score=-101.989 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id kHEuz49Fpabk; Thu, 2 Aug 2012 12:01:20 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF6111E8181; Thu, 2 Aug 2012 12:01:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CD585621A0; Thu, 2 Aug 2012 12:00:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6679 on Explicit Congestion Notification (ECN) for RTP over UDP
From: rfc-editor@rfc-editor.org
Message-Id: <20120802190032.CD585621A0@rfc-editor.org>
Date: Thu, 02 Aug 2012 12:00:28 -0700
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 19:01:20 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6679

        Title:      Explicit Congestion Notification (ECN) for 
                    RTP over UDP 
        Author:     M. Westerlund, I. Johansson,
                    C. Perkins, P. O'Hanlon,
                    K. Carlberg
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2012
        Mailbox:    magnus.westerlund@ericsson.com, 
        Pages:      58
        Characters: 148560
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avtcore-ecn-for-rtp-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6679.txt

This memo specifies how Explicit Congestion Notification (ECN) can be
used with the Real-time Transport Protocol (RTP) running over UDP,
using the RTP Control Protocol (RTCP) as a feedback mechanism.  It
defines a new RTCP Extended Report (XR) block for periodic ECN
feedback, a new RTCP transport feedback message for timely reporting
of congestion events, and a Session Traversal Utilities for NAT
(STUN) extension used in the optional initialisation method using
Interactive Connectivity Establishment (ICE).  Signalling and
procedures for negotiation of capabilities and initialisation methods
are also defined.  [STANDARDS-TRACK]

This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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