[aqm] RFC 8289 on Controlled Delay Active Queue Management

rfc-editor@rfc-editor.org Sat, 06 January 2018 00:02 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46B15126D0C; Fri, 5 Jan 2018 16:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 xeIBRN6SsW6y; Fri, 5 Jan 2018 16:02: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 B0167126B6E; Fri, 5 Jan 2018 16:02:11 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B2B1EB81EC5; Fri, 5 Jan 2018 16:01:54 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, aqm@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180106000154.B2B1EB81EC5@rfc-editor.org>
Date: Fri, 5 Jan 2018 16:01:54 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/aqm/GenwiNA-xv0BeQ3cSb-rjzB7O4s>
Subject: [aqm] =?utf-8?q?RFC_8289_on_Controlled_Delay_Active_Queue_Managem?= =?utf-8?q?ent?=
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Jan 2018 00:02:13 -0000

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

        
        RFC 8289

        Title:      Controlled Delay Active Queue Management 
        Author:     K. Nichols, 
                    V. Jacobson,
                    A. McGregor, Ed.,
                    J. Iyengar, Ed.
        Status:     Experimental
        Stream:     IETF
        Date:       January 2018
        Mailbox:    nichols@pollere.com, 
                    vanj@google.com, 
                    andrewmcgr@google.com,
                    jri@google.com
        Pages:      25
        Characters: 63404
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-aqm-codel-10.txt

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

        DOI:        10.17487/RFC8289

This document describes CoDel (Controlled Delay) -- a general
framework that controls bufferbloat-generated excess delay in modern
networking environments.  CoDel consists of an estimator, a setpoint,
and a control loop.  It requires no configuration in normal Internet
deployments.

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


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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