BCP 197, RFC 7567 on IETF Recommendations Regarding Active Queue Management

rfc-editor@rfc-editor.org Thu, 09 July 2015 22:39 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 (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 097571A1A54; Thu, 9 Jul 2015 15:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id DXhSZrclhm8D; Thu, 9 Jul 2015 15:39:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) by ietfa.amsl.com (Postfix) with ESMTP id 6EA041A1B3F; Thu, 9 Jul 2015 15:39:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D6D2318046F; Thu, 9 Jul 2015 15:36:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 197, RFC 7567 on IETF Recommendations Regarding Active Queue Management
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150709223618.D6D2318046F@rfc-editor.org>
Date: Thu, 9 Jul 2015 15:36:18 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/TVH__TreamEFwMEqKOZA-NaEFA8>
Cc: aqm@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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, 09 Jul 2015 22:39:58 -0000

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

        BCP 197        
        RFC 7567

        Title:      IETF Recommendations Regarding Active Queue 
        Author:     F. Baker, Ed.,
                    G. Fairhurst, Ed.
        Status:     Best Current Practice
        Stream:     IETF
        Date:       July 2015
        Mailbox:    fred@cisco.com, 
        Pages:      31
        Characters: 76832
        Obsoletes:  RFC 2309
        See Also:   BCP 197

        I-D Tag:    draft-ietf-aqm-recommendation-11.txt

        URL:        https://www.rfc-editor.org/info/rfc7567

        DOI:        http://dx.doi.org/10.17487/RFC7567

This memo presents recommendations to the Internet community
concerning measures to improve and preserve Internet performance.  It
presents a strong recommendation for testing, standardization, and
widespread deployment of active queue management (AQM) in network
devices to improve the performance of today's Internet.  It also
urges a concerted effort of research, measurement, and ultimate
deployment of AQM mechanisms to protect the Internet from flows that
are not sufficiently responsive to congestion notification.

Based on 15 years of experience and new research, this document
replaces the recommendations of RFC 2309.

This document is a product of the Active Queue Management and Packet Scheduling Working Group of the IETF.

BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. 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 https://www.rfc-editor.org/search
For downloading RFCs, see https://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