[rfc-dist] Correction: BCP 41, RFC 7141 on Byte and Packet Congestion Notification

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Wed Feb 26 11:33:13 PST 2014

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 at bt.com, 
                   jukka.manner at aalto.fi
       Pages:      41
       Characters: 103344
       Updates:    RFC 2309, RFC 2914
       See Also:   BCP 41

       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 at 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

More information about the rfc-dist mailing list