Moved to Historic: RFC 3540 on Robust Explicit Congestion Notification (ECN) Signaling with Nonces
rfc-editor@rfc-editor.org Tue, 28 November 2017 23:14 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 9230F128CFF; Tue, 28 Nov 2017 15:14:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 EwbeuMOhCUV5; Tue, 28 Nov 2017 15:14:12 -0800 (PST)
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 066D7128BB7; Tue, 28 Nov 2017 15:14:12 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 5330FB80CFC; Tue, 28 Nov 2017 15:14:01 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: Moved to Historic: RFC 3540 on Robust Explicit Congestion Notification (ECN) Signaling with Nonces
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, tsvwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20171128231401.5330FB80CFC@rfc-editor.org>
Date: Tue, 28 Nov 2017 15:14:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/jAkRn7uBAFyALfiYMQHzFqtijZQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Tue, 28 Nov 2017 23:14:13 -0000
RFC 3540 has been reclassified as Historic.
RFC 3540
Title: Robust Explicit Congestion Notification (ECN)
Signaling with Nonces
Author: N. Spring,
D. Wetherall,
D. Ely
Status: Historic
Stream: IETF
Date: June 2003
Pages: 13
Characters: 30081
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tsvwg-tcp-nonce-04.txt
URL: https://www.rfc-editor.org/info/rfc3540
DOI: 10.17487/RFC3540
This note describes the Explicit Congestion Notification (ECN)-nonce, an optional addition to ECN that protects against accidental or malicious concealment of marked packets from the TCP sender. It improves the robustness of congestion control by preventing receivers from exploiting ECN to gain an unfair share of network bandwidth. The ECN-nonce uses the two ECN-Capable Transport (ECT)codepoints in the ECN field of the IP header, and requires a flag in the TCP header. It is computationally efficient for both routers and hosts.
This document is a product of the Transport Area Working Group Working Group of the IETF.
HISTORIC: This memo defines a Historic Document 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