datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

TCP modifications for Congestion Exposure
draft-ietf-conex-tcp-modifications-05

Document type: Active Internet-Draft (conex WG)
Document stream: IETF
Last updated: 2014-02-14
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Congestion Exposure (ConEx)                           M. Kuehlewind, Ed.
Internet-Draft                                   University of Stuttgart
Intended status: Experimental                           R. Scheffenegger
Expires: August 18, 2014                                    NetApp, Inc.
                                                       February 14, 2014

               TCP modifications for Congestion Exposure
                 draft-ietf-conex-tcp-modifications-05

Abstract

   Congestion Exposure (ConEx) is a mechanism by which senders inform
   the network about the congestion encountered by previous packets on
   the same flow.  This document describes the necessary modifications
   to use ConEx with the Transmission Control Protocol (TCP).

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 18, 2014.

Copyright Notice

   Copyright (c) 2014 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
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Kuehlewind & ScheffeneggeExpires August 18, 2014                [Page 1]
Internet-Draft  TCP modifications for Congestion Exposure  February 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Sender-side Modifications . . . . . . . . . . . . . . . . . .   3
   3.  Accounting congestion . . . . . . . . . . . . . . . . . . . .   4
     3.1.  ECN . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
       3.1.1.  Accurate ECN feedback . . . . . . . . . . . . . . . .   6
       3.1.2.  Classic ECN support . . . . . . . . . . . . . . . . .   6
     3.2.  Loss Detection  . . . . . . . . . . . . . . . . . . . . .   7
       3.2.1.  Without SACK Support  . . . . . . . . . . . . . . . .   7
   4.  Setting the ConEx Bits  . . . . . . . . . . . . . . . . . . .   8
     4.1.  Setting the E and the L Bit . . . . . . . . . . . . . . .   8
     4.2.  Credit Bits . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Loss of ConEx information . . . . . . . . . . . . . . . . . .  10
   6.  Timeliness of the ConEx Signals . . . . . . . . . . . . . . .  10
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     10.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Appendix A.  Revision history . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   Congestion Exposure (ConEx) is a mechanism by which senders inform
   the network about the congestion encountered by previous packets on
   the same flow.  ConEx concepts and use cases are further explained in
   [RFC6789].  The abstract ConEx mechanism is explained in
   [draft-ietf-conex-abstract-mech].  This document describes the
   necessary modifications to use ConEx with the Transmission Control
   Protocol (TCP).

   The ConEx signal is based on loss or Explicit Congestion Notification
   (ECN) marks [RFC3168] as a congestion indication.  This congestion
   information is retrieved by the sender based on existing feedback
   mechanisms from the receiver to the sender in TCP.

   This document describes mechanisms for both TCP with and without the
   Selective Acknowledgment (SACK) extension [RFC2018].  However, ConEx

[include full document text]