Adding Explicit Congestion Notification (ECN) to TCP control packets and TCP retransmissions
draft-bagnulo-tcpm-generalized-ecn-00

Document Type Active Internet-Draft (individual)
Last updated 2016-12-09 (latest revision 2016-09-29)
Replaces draft-bagnulo-tsvwg-generalized-ecn
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         M. Bagnulo
Internet-Draft                                                      UC3M
Intended status: Informational                                B. Briscoe
Expires: April 2, 2017                               Simula Research Lab
                                                      September 29, 2016

Adding Explicit Congestion Notification (ECN) to TCP control packets and
                          TCP retransmissions
                 draft-bagnulo-tcpm-generalized-ecn-00

Abstract

   This document describes an experimental modification to ECN to allow
   the use of ECN to the following TCP packets: SYNs, Pure ACKs, Window
   probes, FINs, RSTs and retransmissions.

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 April 2, 2017.

Copyright Notice

   Copyright (c) 2016 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.

Bagnulo & Briscoe         Expires April 2, 2017                 [Page 1]
Internet-Draft         ECN and TCP control packets        September 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Experiment goals  . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Document structure  . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Specification . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Network behaviour . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Endpoint behaviour  . . . . . . . . . . . . . . . . . . .   6
       3.2.1.  SYN . . . . . . . . . . . . . . . . . . . . . . . . .   6
       3.2.2.  Pure ACK  . . . . . . . . . . . . . . . . . . . . . .   8
       3.2.3.  Window Probe  . . . . . . . . . . . . . . . . . . . .   9
       3.2.4.  FIN . . . . . . . . . . . . . . . . . . . . . . . . .  10
       3.2.5.  RST . . . . . . . . . . . . . . . . . . . . . . . . .  10
       3.2.6.  Retransmissions . . . . . . . . . . . . . . . . . . .  11
   4.  Discussion about the arguments in RFC3168 . . . . . . . . . .  12
     4.1.  The reliability argument  . . . . . . . . . . . . . . . .  12
     4.2.  TCP SYNs  . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.3.  Pure ACKs.  . . . . . . . . . . . . . . . . . . . . . . .  16
     4.4.  Retransmitted packets.  . . . . . . . . . . . . . . . . .  18
     4.5.  Window probe packets  . . . . . . . . . . . . . . . . . .  20
   5.  Security considerations . . . . . . . . . . . . . . . . . . .  21
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  21
   8.  Informative References  . . . . . . . . . . . . . . . . . . .  21
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Introduction

   RFC3168 [RFC3168] specifies the support of Explicit Congestion
   Notification (ECN) to IP.  By using the ECN capability, switches
   performing Active Queue Management (AQM) can use ECN marks instead of
   packets drops to signal congestion to the endpoints of a
   communication.  This results in lower packet loss and increased
   performance.  However, RFC3168 specifies the support of ECN in TCP
   data packets, but precludes the use of ECN in TCP control packets
   (TCP SYN, TCP SYN/ACK, pure ACKs, Window probes) and in retransmitted
   packets.  RFC3168 is silent about the use of ECN in RST and FIN
   packets.  RFC 5562 [RFC5562] is an experimental extension to ECN that
Show full document text