RFC 5696 on Baseline Encoding and Transport of Pre-Congestion Information
rfc-editor@rfc-editor.org Tue, 24 November 2009 00:35 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BD093A6B03; Mon, 23 Nov 2009 16:35:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.127
X-Spam-Level:
X-Spam-Status: No, score=-17.127 tagged_above=-999 required=5 tests=[AWL=-0.128, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hbMz0WfGc4DR; Mon, 23 Nov 2009 16:35:06 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 2A67B3A6B00; Mon, 23 Nov 2009 16:35:06 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 160FA372B7A; Mon, 23 Nov 2009 16:29:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5696 on Baseline Encoding and Transport of Pre-Congestion Information
From: rfc-editor@rfc-editor.org
Message-Id: <20091124002954.160FA372B7A@bosco.isi.edu>
Date: Mon, 23 Nov 2009 16:29:54 -0800
Cc: pcn@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 24 Nov 2009 00:35:07 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5696 Title: Baseline Encoding and Transport of Pre-Congestion Information Author: T. Moncaster, B. Briscoe, M. Menth Status: Standards Track Date: November 2009 Mailbox: toby.moncaster@bt.com, bob.briscoe@bt.com, menth@informatik.uni-wuerzburg.de Pages: 15 Characters: 33112 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pcn-baseline-encoding-07.txt URL: http://www.rfc-editor.org/rfc/rfc5696.txt The objective of the Pre-Congestion Notification (PCN) architecture is to protect the quality of service (QoS) of inelastic flows within a Diffserv domain. It achieves this by marking packets belonging to PCN-flows when the rate of traffic exceeds certain configured thresholds on links in the domain. These marks can then be evaluated to determine how close the domain is to being congested. This document specifies how such marks are encoded into the IP header by redefining the Explicit Congestion Notification (ECN) codepoints within such domains. The baseline encoding described here provides only two PCN encoding states: Not-marked and PCN-marked. Future extensions to this encoding may be needed in order to provide more than one level of marking severity. [STANDARDS TRACK] This document is a product of the Congestion and Pre-Congestion Notification 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 http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist 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 USC/Information Sciences Institute