Browse Prior Art Database

Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements (RFC7713)

IP.com Disclosure Number: IPCOM000245068D
Original Publication Date: 2015-Dec-01
Included in the Prior Art Database: 2016-Feb-07
Document File: 60 page(s) / 77K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Mathis: AUTHOR [+2]

Abstract

This document describes an abstract mechanism by which, to a first approximation, senders inform the network about the congestion encountered by packets earlier in the same flow. It is not a complete protocol specification because it is known that designing an encoding (e.g., packet formats, codepoint allocations, etc.) is likely to entail compromises that preclude some uses of the protocol. The goal of this document is to provide a framework for developing and testing algorithms to evaluate the benefits of the ConEx protocol and to evaluate the consequences of the compromises in various different encoding designs. This document lays out requirements for concrete protocol specifications.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Internet Engineering Task Force (IETF)                         M. Mathis Request for Comments: 7713                                  Google, Inc. Category: Informational                                       B. Briscoe ISSN: 2070-1721                                                       BT                                                            December 2015

        Congestion Exposure (ConEx) Concepts, Abstract Mechanism,                             and Requirements

Abstract

   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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7713.

 Mathis & Briscoe              Informational                     [Page 1]
 RFC 7713          ConEx Concepts and Abstract Mechanism    December 2015

 Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    public...