RFC 7928 on Characterization Guidelines for Active Queue Management (AQM)
rfc-editor@rfc-editor.org Sat, 30 July 2016 05:17 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E363A12D5AF; Fri, 29 Jul 2016 22:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 MdsWX8eBHX0P; Fri, 29 Jul 2016 22:17:12 -0700 (PDT)
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 7954C12D61D; Fri, 29 Jul 2016 22:16:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5DA70B8032A; Fri, 29 Jul 2016 22:16:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7928 on Characterization Guidelines for Active Queue Management (AQM)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160730051659.5DA70B8032A@rfc-editor.org>
Date: Fri, 29 Jul 2016 22:16:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/n0brIsnIpJZgOsllrVh4q8Am3zU>
Cc: drafts-update-ref@iana.org, aqm@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 30 Jul 2016 05:17:19 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7928
Title: Characterization Guidelines for Active Queue
Management (AQM)
Author: N. Kuhn, Ed.,
P. Natarajan, Ed.,
N. Khademi, Ed.,
D. Ros
Status: Informational
Stream: IETF
Date: July 2016
Mailbox: nicolas.kuhn@cnes.fr,
prenatar@cisco.com,
naeemk@ifi.uio.no,
dros@simula.no
Pages: 37
Characters: 90255
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-aqm-eval-guidelines-13.txt
URL: https://www.rfc-editor.org/info/rfc7928
DOI: http://dx.doi.org/10.17487/RFC7928
Unmanaged large buffers in today's networks have given rise to a slew
of performance issues. These performance issues can be addressed by
some form of Active Queue Management (AQM) mechanism, optionally in
combination with a packet-scheduling scheme such as fair queuing.
This document describes various criteria for performing
characterizations of AQM schemes that can be used in lab testing
during development, prior to deployment.
This document is a product of the Active Queue Management and Packet Scheduling Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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