An ECN Extension to CONNECT-UDP
draft-schinazi-masque-connect-udp-ecn-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author David Schinazi 
Last updated 2020-12-12
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized 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                                        D. Schinazi
Internet-Draft                                                Google LLC
Intended status: Standards Track                        12 December 2020
Expires: 15 June 2021

                    An ECN Extension to CONNECT-UDP
                draft-schinazi-masque-connect-udp-ecn-00

Abstract

   The CONNECT-UDP method allows proxying UDP packets over HTTP.  This
   document describes an extension to CONNECT-UDP that allows conveying
   ECN information on proxied UDP packets.

   Discussion of this work is encouraged to happen on the MASQUE IETF
   mailing list (masque@ietf.org (mailto:masque@ietf.org)) or on the
   GitHub repository which contains the draft:
   https://github.com/DavidSchinazi/draft-connect-udp-ecn.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Source for this draft and an issue tracker can be found at
   https://github.com/DavidSchinazi/draft-connect-udp-ecn.

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 https://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 15 June 2021.

Copyright Notice

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

Schinazi                  Expires 15 June 2021                  [Page 1]
Internet-Draft          CONNECT-UDP ECN Extension          December 2020

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://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
     1.1.  Conventions and Definitions . . . . . . . . . . . . . . .   2
   2.  ECN Header Definition . . . . . . . . . . . . . . . . . . . .   2
   3.  Datagram Encoding of Proxied UDP Packets  . . . . . . . . . .   3
   4.  Stream Encoding of Proxied UDP Packets  . . . . . . . . . . .   3
   5.  HTTP Intermediaries . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  HTTP Header . . . . . . . . . . . . . . . . . . . . . . .   4
     7.2.  Stream Chunk Type Registration  . . . . . . . . . . . . .   5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The CONNECT-UDP [CONNECT-UDP] method allows proxying UDP packets over
   HTTP.  This document describes an extension to CONNECT-UDP that
   allows conveying ECN [ECN] information on proxied UDP packets.

   Discussion of this work is encouraged to happen on the MASQUE IETF
   mailing list (masque@ietf.org (mailto:masque@ietf.org)) or on the
   GitHub repository which contains the draft:
   https://github.com/DavidSchinazi/draft-connect-udp-ecn.

1.1.  Conventions and Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  ECN Header Definition

   "ECN" is a Item Structured Header [STRUCT-HDR].  Its value MUST be a
   Boolean.  Its ABNF is:

Schinazi                  Expires 15 June 2021                  [Page 2]
Internet-Draft          CONNECT-UDP ECN Extension          December 2020

     ECN = sf-boolean

   The "ECN" header indicates whether the sender supports this
   extension.  A value of 1 indicates support whereas a value of 0 (or
   the absence of the header) indicates lack of support.

   Clients MUST NOT indicate support for this extension unless they know
   that the protocol running over UDP that is being proxied supports
   ECN, and will react appropriately to Congestion Experienced (CE)
Show full document text