[PCN] RFC 6661 on Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Controlled Load (CL) Mode of Operation

rfc-editor@rfc-editor.org Thu, 19 July 2012 00:13 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pcn@ietfa.amsl.com
Delivered-To: pcn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 113E221F85EA; Wed, 18 Jul 2012 17:13:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.231
X-Spam-Level:
X-Spam-Status: No, score=-102.231 tagged_above=-999 required=5 tests=[AWL=0.369, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GlcuBAm9CF6A; Wed, 18 Jul 2012 17:13:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 7517C21F85E4; Wed, 18 Jul 2012 17:13:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EAC1872E034; Wed, 18 Jul 2012 17:13:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120719001333.EAC1872E034@rfc-editor.org>
Date: Wed, 18 Jul 2012 17:13:33 -0700 (PDT)
Cc: pcn@ietf.org, rfc-editor@rfc-editor.org
Subject: [PCN] RFC 6661 on Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Controlled Load (CL) Mode of Operation
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 00:13:19 -0000

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

        
        RFC 6661

        Title:      Pre-Congestion Notification (PCN) Boundary-Node
                    Behavior for the Controlled Load (CL) Mode 
                    of Operation 
        Author:     A. Charny, F. Huang,
                    G. Karagiannis, M. Menth,
                    T. Taylor, Ed.
        Status:     Experimental
        Stream:     IETF
        Date:       July 2012
        Mailbox:    anna@mwsm.com, 
                    huangfuqing@huawei.com, 
                    g.karagiannis@utwente.nl,
                    menth@uni-tuebingen.de, 
                    tom.taylor.stds@gmail.com
        Pages:      33
        Characters: 72258
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pcn-cl-edge-behaviour-14.txt

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

Pre-Congestion Notification (PCN) is a means for protecting the
quality of service for inelastic traffic admitted to a Diffserv
domain.  The overall PCN architecture is described in RFC 5559.  This
memo is one of a series describing possible boundary-node behaviors
for a PCN-domain.  The behavior described here is that for a form of
measurement-based load control using three PCN marking states: not-
marked, threshold-marked, and excess-traffic-marked.  This behavior
is known informally as the Controlled Load (CL) PCN-boundary-node
behavior.  This document defines an Experimental Protocol for the 
Internet community.

This document is a product of the Congestion and Pre-Congestion Notification Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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
Association Management Solutions, LLC