RFC 6040 on Tunnelling of Explicit Congestion Notification

rfc-editor@rfc-editor.org Tue, 30 November 2010 06:27 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id B21E03A69D7; Mon, 29 Nov 2010 22:27:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.04
X-Spam-Status: No, score=-102.04 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 70yV1pwLRIOC; Mon, 29 Nov 2010 22:27:27 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 0C2F328C13D; Mon, 29 Nov 2010 22:26:28 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DF40AE0715; Mon, 29 Nov 2010 22:27:37 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6040 on Tunnelling of Explicit Congestion Notification
From: rfc-editor@rfc-editor.org
Message-Id: <20101130062737.DF40AE0715@rfc-editor.org>
Date: Mon, 29 Nov 2010 22:27:37 -0800
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Nov 2010 06:27:28 -0000
X-List-Received-Date: Tue, 30 Nov 2010 06:27:28 -0000

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

        RFC 6040

        Title:      Tunnelling of Explicit Congestion Notification 
        Author:     B. Briscoe
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2010
        Mailbox:    bob.briscoe@bt.com
        Pages:      35
        Characters: 89412
        Updates:    RFC3168, RFC4301, RFC4774

        I-D Tag:    draft-ietf-tsvwg-ecn-tunnel-10.txt

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

This document redefines how the explicit congestion notification
(ECN) field of the IP header should be constructed on entry to and
exit from any IP-in-IP tunnel.  On encapsulation, it updates RFC 3168
to bring all IP-in-IP tunnels (v4 or v6) into line with RFC 4301
IPsec ECN processing.  On decapsulation, it updates both RFC 3168 and
RFC 4301 to add new behaviours for previously unused combinations of
inner and outer headers.  The new rules ensure the ECN field is
correctly propagated across a tunnel whether it is used to signal one
or two severity levels of congestion; whereas before, only one
severity level was supported.  Tunnel endpoints can be updated in any
order without affecting pre-existing uses of the ECN field, thus
ensuring backward compatibility.  Nonetheless, operators wanting to
support two severity levels (e.g., for pre-congestion notification --
PCN) can require compliance with this new specification.  A thorough
analysis of the reasoning for these changes and the implications is
included.  In the unlikely event that the new rules do not meet a
specific need, RFC 4774 gives guidance on designing alternate ECN
semantics, and this document extends that to include tunnelling

This document is a product of the Transport Area Working Group Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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/rfcsearch.html.
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