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

Document Type Active Internet-Draft (individual)
Last updated 2017-04-05
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                             April 4, 2017
Expires: October 6, 2017

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

Abstract

   This memo outlines the ECN (Explicit Congestion Notification) support
   in QUIC.  The draft specifies the ECN negotiation and the ECN echo
   and in addition, different aspects of fallback in case of ECN failure
   as well as OS specific issues with ECN and monitoring for ECN
   capability.  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 October 6, 2017.

Copyright Notice

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

Johansson                Expires October 6, 2017                [Page 1]
Internet-Draft             ECN support in QUIC                April 2017

   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.

Table of Contents

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

1.  Introduction

   ECN support in transport protocols is a fundamental feature that
   should be included in the QUIC specification as a mandatory element.
   ECN has the key benefit that it allows for non-destructive congestion
   notification by network node, i.e packets are marked instead
   discarded.  This is particularly beneficial for realtime applications
   with requirements on latency, ECN also has the benefit that it
   provides with a congestion signal that is unambiguous.  The benefits
   with ECN is described in more detail 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
Show full document text