ECN support in QUIC
draft-johansson-quic-ecn-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2017-01-18
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       I. Johansson
Internet-Draft                                               Ericsson AB
Intended status: Informational                          January 18, 2017
Expires: July 22, 2017

                          ECN support in QUIC
                      draft-johansson-quic-ecn-00

Abstract

   This memo outlines the ECN support in QUIC.  The intention is that
   most of the material ends up updating other new or existing QUIC
   protocol specifications, thus it may be possible that this draft does
   not warrant a working group status.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 July 22, 2017.

Copyright Notice

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

Johansson                 Expires July 22, 2017                 [Page 1]
Internet-Draft             ECN support in QUIC              January 2017

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Elements of ECN support . . . . . . . . . . . . . . . . . . .   2
     2.1.  ECN negotialtion  . . . . . . . . . . . . . . . . . . . .   3
     2.2.  ECN bits in the IP header, semantics  . . . . . . . . . .   3
     2.3.  ECN echo  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.4.  Fallback in case of ECN fault . . . . . . . . . . . . . .   6
     2.5.  OS socket specifics, access to the ECN bits . . . . . . .   6
     2.6.  Monitoring  . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   4.  Open questions  . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   ECN support in transport protocols is a fundamental feature that
   should be included in the QUIC specification as a mandatory element.
   The benefits of ECN is described in [I-D.ietf-aqm-ecn-benefits].  The
   ECN support should be implemented to support both present and future
   ECN, the latter is outlined in [I-D.ietf-tsvwg-ecn-experimentation],
   of particular interest is the ability to discriminate between classic
   ECN and L4S ECN by means of an ability to differentiate between the
   use of the ECT(0) and ECT(1) code points.  This draft does however
   not delve into the details of the congestion control implementation.

2.  Elements of ECN support

   This draft covers the following aspects of ECN support:

   o  ECN negotiation

   o  ECN echo

   o  ECN bits in the IP header, semantics

   o  Fallback in case of ECN fault

Johansson                 Expires July 22, 2017                 [Page 2]
Internet-Draft             ECN support in QUIC              January 2017

   o  OS socket specifics, access to the ECN bits

   o  Monitoring

2.1.  ECN negotialtion

   In TCP, ECN was added as a later feature than the original TCP
   specification, this necessitated negotiation as there was (and still
   are?)  TCP stacks that do not support ECN.

   With QUIC, the situation is more straightforward.  The suggested way
   forward is here to just add ECN support from a given version of QUIC,
Show full document text