[conex] RFC 7713 on Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements

rfc-editor@rfc-editor.org Tue, 29 December 2015 05:28 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: conex@ietfa.amsl.com
Delivered-To: conex@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2F4A1A1A6A; Mon, 28 Dec 2015 21:28:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o0FLlLRNlJ8K; Mon, 28 Dec 2015 21:28:51 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 6EE461A1A68; Mon, 28 Dec 2015 21:28:51 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 46E62180016; Mon, 28 Dec 2015 21:28:21 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151229052821.46E62180016@rfc-editor.org>
Date: Mon, 28 Dec 2015 21:28:21 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/conex/Yn0TsYdZksjPejc0zQnb5A-iy7Q>
Cc: conex@ietf.org, rfc-editor@rfc-editor.org
Subject: [conex] RFC 7713 on Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements
X-BeenThere: conex@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 29 Dec 2015 05:28:53 -0000

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

        
        RFC 7713

        Title:      Congestion Exposure (ConEx) Concepts, Abstract 
                    Mechanism, and Requirements 
        Author:     M. Mathis, B. Briscoe
        Status:     Informational
        Stream:     IETF
        Date:       December 2015
        Mailbox:    mattmathis@google.com, 
                    ietf@bobbriscoe.net
        Pages:      30
        Characters: 76797
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-conex-abstract-mech-13.txt

        URL:        https://www.rfc-editor.org/info/rfc7713

        DOI:        http://dx.doi.org/10.17487/RFC7713

This document describes an abstract mechanism by which senders inform
the network about the congestion recently encountered by packets in
the same flow.  Today, network elements at any layer may signal
congestion to the receiver by dropping packets or by Explicit
Congestion Notification (ECN) markings, and the receiver passes this
information back to the sender in transport-layer feedback.  The
mechanism described here enables the sender to also relay this
congestion information back into the network in-band at the IP layer,
such that the total amount of congestion from all elements on the
path is revealed to all IP elements along the path, where it could,
for example, be used to provide input to traffic management.  This
mechanism is called Congestion Exposure, or ConEx.  The companion
document, "Congestion Exposure (ConEx) Concepts and Use Cases"
(RFC 6789), provides the entry point to the set of ConEx documentation.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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