RFC 6663 on Requirements for Signaling of Pre-Congestion Information in a Diffserv Domain

rfc-editor@rfc-editor.org Thu, 19 July 2012 00:13 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 9852711E80E2; Wed, 18 Jul 2012 17:13:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.237
X-Spam-Status: No, score=-102.237 tagged_above=-999 required=5 tests=[AWL=0.363, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id tdupZ4VAKKAA; Wed, 18 Jul 2012 17:13:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id CF9A411E81D9; Wed, 18 Jul 2012 17:13:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4D6F872E093; Wed, 18 Jul 2012 17:13:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6663 on Requirements for Signaling of Pre-Congestion Information in a Diffserv Domain
From: rfc-editor@rfc-editor.org
Message-Id: <20120719001356.4D6F872E093@rfc-editor.org>
Date: Wed, 18 Jul 2012 17:13:56 -0700
Cc: pcn@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Thu, 19 Jul 2012 00:13:44 -0000

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

        RFC 6663

        Title:      Requirements for Signaling of Pre-Congestion 
                    Information in a Diffserv Domain 
        Author:     G. Karagiannis, T. Taylor,
                    K. Chan, M. Menth,
                    P. Eardley
        Status:     Informational
        Stream:     IETF
        Date:       July 2012
        Mailbox:    g.karagiannis@utwente.nl, 
        Pages:      7
        Characters: 15316
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pcn-signaling-requirements-08.txt

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

Pre-Congestion Notification (PCN) is a means for protecting quality of
service for inelastic traffic admitted to a Diffserv domain.  The
overall PCN architecture is described in RFC 5559.  This memo
describes the requirements for the signaling applied within the PCN-domain:
(1) PCN-feedback-information is carried from the PCN-egress-node to
the Decision Point; (2) the Decision Point may ask the PCN-ingress-node to
measure, and report back, the rate of sent PCN-traffic between that
PCN-ingress-node and PCN-egress-node.  The Decision Point may be either
collocated with the PCN-ingress-node or a centralized node (in the first 
case, (2) is not required).  The signaling requirements pertain in 
particular to two edge behaviors, Controlled Load (CL) and Single Marking 
(SM).  This document is not an Internet Standards Track specification; it 
is published for informational purposes.

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

INFORMATIONAL: This memo provides information 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

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