[conex] RFC 6789 on Congestion Exposure (ConEx) Concepts and Use Cases

rfc-editor@rfc-editor.org Thu, 06 December 2012 01:28 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: conex@ietfa.amsl.com
Delivered-To: conex@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E8E921F89CB; Wed, 5 Dec 2012 17:28:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.85
X-Spam-Level:
X-Spam-Status: No, score=-101.85 tagged_above=-999 required=5 tests=[AWL=0.750, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 89PhU24MkA-6; Wed, 5 Dec 2012 17:28:56 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id D5D8821F8997; Wed, 5 Dec 2012 17:28:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id ED0CE72F4EF; Wed, 5 Dec 2012 17:20:39 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121206012039.ED0CE72F4EF@rfc-editor.org>
Date: Wed, 05 Dec 2012 17:20:39 -0800
Cc: conex@ietf.org, rfc-editor@rfc-editor.org
Subject: [conex] RFC 6789 on Congestion Exposure (ConEx) Concepts and Use Cases
X-BeenThere: conex@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Congestion Exposure working group discussion list <conex.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/conex>, <mailto:conex-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/conex>
List-Post: <mailto:conex@ietf.org>
List-Help: <mailto:conex-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/conex>, <mailto:conex-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Dec 2012 01:28:57 -0000

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

        
        RFC 6789

        Title:      Congestion Exposure (ConEx) Concepts and 
                    Use Cases 
        Author:     B. Briscoe, Ed.,
                    R. Woundy, Ed.,
                    A. Cooper, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       December 2012
        Mailbox:    bob.briscoe@bt.com, 
                    richard_woundy@cable.comcast.com, 
                    acooper@cdt.org
        Pages:      17
        Characters: 41078
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-conex-concepts-uses-05.txt

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

This document provides the entry point to the set of documentation
about the Congestion Exposure (ConEx) protocol.  It explains the
motivation for including a ConEx marking at the IP layer: to expose
information about congestion to network nodes.  Although such
information may have a number of uses, this document focuses on how
the information communicated by the ConEx marking can serve as the
basis for significantly more efficient and effective traffic
management than what exists on the Internet today.  This document 
is not an Internet Standards Track specification; it is
published for informational purposes.

This document is a product of the Congestion Exposure 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
  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