BCP 41, RFC 7141 on Byte and Packet Congestion Notification

rfc-editor@rfc-editor.org Wed, 26 February 2014 19:13 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 55EF51A0806; Wed, 26 Feb 2014 11:13:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ZpZWqV0rwBd1; Wed, 26 Feb 2014 11:13:20 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id DFFC11A07FF; Wed, 26 Feb 2014 11:13:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B326F7FC2C7; Wed, 26 Feb 2014 11:13:14 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 41, RFC 7141 on Byte and Packet Congestion Notification
From: rfc-editor@rfc-editor.org
Message-Id: <20140226191314.B326F7FC2C7@rfc-editor.org>
Date: Wed, 26 Feb 2014 11:13:14 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/zsqENqW8WOQm7apJV3_9Q-JmPjo
Cc: drafts-update-ref@iana.org, tsvwg@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: <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: Wed, 26 Feb 2014 19:13:25 -0000

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

        BCP 41        
        RFC 7141

        Title:      Byte and Packet Congestion Notification 
        Author:     B. Briscoe, J. Manner
        Status:     Best Current Practice
        Stream:     IETF
        Date:       February 2014
        Mailbox:    bob.briscoe@bt.com, 
        Pages:      48
        Characters: 123953
        Updates:    2309

        I-D Tag:    draft-ietf-tsvwg-byte-pkt-congest-12.txt

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

   This document provides recommendations of best current practice for
   dropping or marking packets using any active queue management (AQM)
   algorithm, including random early detection (RED), BLUE, pre-
   congestion notification (PCN) and newer schemes such as CoDel
   (Controlled Delay) and PIE (Proportional Integral controller
   Enhanced).  We give three strong recommendations: (1) packet size
   should be taken into account when transports detect and respond to
   congestion indications, (2) packet size should not be taken into
   account when network equipment creates congestion signals (marking,
   dropping), and therefore (3) in the specific case of RED, the byte-
   mode packet drop variant that drops fewer small packets should not be
   used.  This memo updates RFC 2309 to deprecate deliberate
   preferential treatment of small packets in AQM algorithms.

This document is a product of the Transport Area Working Group 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 http://www.rfc-editor.org/search
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