RFC 6627 on Overview of Pre-Congestion Notification Encoding

rfc-editor@rfc-editor.org Thu, 19 July 2012 00:12 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 0F03121F84D9; Wed, 18 Jul 2012 17:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.227
X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=0.373, 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 QVJaunzUrjZh; Wed, 18 Jul 2012 17:12:17 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 8478C21F84D6; Wed, 18 Jul 2012 17:12:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5426D621A1; Wed, 18 Jul 2012 17:12:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6627 on Overview of Pre-Congestion Notification Encoding
From: rfc-editor@rfc-editor.org
Message-Id: <20120719001232.5426D621A1@rfc-editor.org>
Date: Wed, 18 Jul 2012 17:12:32 -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:12:18 -0000

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

        RFC 6627

        Title:      Overview of Pre-Congestion Notification Encoding 
        Author:     G. Karagiannis, K. Chan,
                    T. Moncaster, M. Menth,
                    P. Eardley, B. Briscoe
        Status:     Informational
        Stream:     IETF
        Date:       July 2012
        Mailbox:    g.karagiannis@utwente.nl, 
        Pages:      20
        Characters: 47274
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pcn-encoding-comparison-09.txt

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

The objective of Pre-Congestion Notification (PCN) is to protect
the quality of service (QoS) of inelastic flows within a Diffserv
domain.  On every link in the PCN-domain, the overall rate of
PCN-traffic is metered, and PCN-packets are appropriately marked when
certain configured rates are exceeded.  Egress nodes provide decision 
points with information about the PCN-marks of PCN-packets that allows them
to take decisions about whether to admit or block a new flow request,
and to terminate some already admitted flows during serious pre-congestion.

The PCN working group explored a number of approaches for encoding
this pre-congestion information into the IP header.  This document provides
details of those approaches along with an explanation of the constraints 
that apply to any solution.  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