RFC 7806 on On Queuing, Marking, and Dropping

rfc-editor@rfc-editor.org Thu, 14 April 2016 00:49 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 1A7B612DB6E; Wed, 13 Apr 2016 17:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.918
X-Spam-Level:
X-Spam-Status: No, score=-107.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, 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 44CbUidwsXxd; Wed, 13 Apr 2016 17:49:24 -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 0457612DB91; Wed, 13 Apr 2016 17:49:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 51D6518046C; Wed, 13 Apr 2016 17:49:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7806 on On Queuing, Marking, and Dropping
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160414004909.51D6518046C@rfc-editor.org>
Date: Wed, 13 Apr 2016 17:49:09 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/MILMfgu7G6-lpox999WcpY4yQyQ>
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: Thu, 14 Apr 2016 00:49:26 -0000

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

        
        RFC 7806

        Title:      On Queuing, Marking, and Dropping 
        Author:     F. Baker, R. Pan
        Status:     Informational
        Stream:     IETF
        Date:       April 2016
        Mailbox:    fred@cisco.com, 
                    ropan@cisco.com
        Pages:      16
        Characters: 37818
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-aqm-fq-implementation-05.txt

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

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

This note discusses queuing and marking/dropping algorithms.  While
these algorithms may be implemented in a coupled manner, this note
argues that specifications, measurements, and comparisons should
decouple the different algorithms and their contributions to system
behavior.

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