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

marcelo bagnulo braun <marcelo@it.uc3m.es> Thu, 06 December 2012 15:27 UTC

Return-Path: <marcelo@it.uc3m.es>
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 2D86521F8546 for <conex@ietfa.amsl.com>; Thu, 6 Dec 2012 07:27:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 pBjHaTtsaL9y for <conex@ietfa.amsl.com>; Thu, 6 Dec 2012 07:27:10 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by ietfa.amsl.com (Postfix) with ESMTP id 5301821F8545 for <conex@ietf.org>; Thu, 6 Dec 2012 07:27:10 -0800 (PST)
Received: from marcelo-bagnulos-macbook-pro.local (unknown [163.117.203.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: marcelo@smtp03.uc3m.es) by smtp03.uc3m.es (Postfix) with ESMTPSA id 8D7909D7137 for <conex@ietf.org>; Thu, 6 Dec 2012 16:27:07 +0100 (CET)
Message-ID: <50C0B949.3020007@it.uc3m.es>
Date: Thu, 06 Dec 2012 16:27:05 +0100
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: 'ConEx IETF list' <conex@ietf.org>
References: <20121206012039.ED0CE72F4EF@rfc-editor.org>
In-Reply-To: <20121206012039.ED0CE72F4EF@rfc-editor.org>
X-Forwarded-Message-Id: <20121206012039.ED0CE72F4EF@rfc-editor.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelistedACL 131 matched, not delayed by milter-greylist-4.2.7 (smtp03.uc3m.es); Thu, 06 Dec 2012 16:27:08 +0100 (CET)
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-6.8.0.1017-19426.000
X-TM-AS-Result: No--22.464-7.0-31-1
X-imss-scan-details: No--22.464-7.0-31-1
Subject: [conex] Fwd: 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 15:27:11 -0000

We have our first document out.
Thanks to the WG and specially the editors for their work.



-------- Mensaje original --------
Asunto: 	[conex] RFC 6789 on Congestion Exposure (ConEx) Concepts and 
Use Cases
Fecha: 	Wed, 5 Dec 2012 17:20:39 -0800 (PST)
De: 	rfc-editor@rfc-editor.org
Para: 	ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: 	conex@ietf.org, rfc-editor@rfc-editor.org



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


_______________________________________________
conex mailing list
conex@ietf.org
https://www.ietf.org/mailman/listinfo/conex