RFC 5670 on Metering and Marking Behaviour of PCN-Nodes

rfc-editor@rfc-editor.org Tue, 24 November 2009 00:34 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 []) by core3.amsl.com (Postfix) with ESMTP id 96E4C3A6AE6; Mon, 23 Nov 2009 16:34:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.137
X-Spam-Status: No, score=-17.137 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id e27SnVbM9N0T; Mon, 23 Nov 2009 16:34:40 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id ABD243A6AE4; Mon, 23 Nov 2009 16:34:40 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id DD045372B78; Mon, 23 Nov 2009 16:29:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5670 on Metering and Marking Behaviour of PCN-Nodes
From: rfc-editor@rfc-editor.org
Message-Id: <20091124002929.DD045372B78@bosco.isi.edu>
Date: Mon, 23 Nov 2009 16:29:29 -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:34:41 -0000

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

        RFC 5670

        Title:      Metering and Marking Behaviour of 
        Author:     P. Eardley, Ed.
        Status:     Standards Track
        Date:       November 2009
        Mailbox:    philip.eardley@bt.com
        Pages:      20
        Characters: 44363
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pcn-marking-behaviour-05.txt

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

The objective of Pre-Congestion Notification (PCN) is to protect the
quality of service (QoS) of inelastic flows within a Diffserv domain
in a simple, scalable, and robust fashion.  This document defines the
two metering and marking behaviours of PCN-nodes.  Threshold-metering
and -marking marks all PCN-packets if the rate of PCN-traffic is
greater than a configured rate ("PCN-threshold-rate").  Excess-
traffic-metering and -marking marks a proportion of PCN-packets, such
that the amount marked equals the rate of PCN-traffic in excess of a
configured rate ("PCN-excess-rate").  The level of marking allows
PCN-boundary-nodes to make decisions about whether to admit or
terminate PCN-flows.  [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

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