Address-bound Token for QUIC
draft-kazuho-quic-address-bound-token-00

Document Type Active Internet-Draft (individual)
Last updated 2019-04-03
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)
QUIC                                                              K. Oku
Internet-Draft                                                    Fastly
Intended status: Standards Track                          April 04, 2019
Expires: October 6, 2019

                      Address-bound Token for QUIC
                draft-kazuho-quic-address-bound-token-00

Abstract

   This document describes a QUIC extension for an address-bound token.
   This token can be used for sharing address validation and congestion
   controller state between the same two endpoints across multiple
   connections and origins.

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, 2019.

Copyright Notice

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

Oku                      Expires October 6, 2019                [Page 1]
Internet-Draft        Address-bound Token for QUIC            April 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   2
   2.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The address_bound_token Transport Parameter . . . . . . . . .   3
   4.  Sharing the Congestion Controller . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
     5.1.  Reflection Attack . . . . . . . . . . . . . . . . . . . .   4
     5.2.  Plaintext Tokens  . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Design Variations  . . . . . . . . . . . . . . . . .   5
     A.1.  Using Alt-Svc Name as the Key . . . . . . . . . . . . . .   5
     A.2.  Cross-connection Prioritization . . . . . . . . . . . . .   5
   Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Some, if not all of the application protocols that are built on top
   of QUIC [QUIC-TRANSPORT], including HTTP/3 [QUIC-HTTP], require or
   would require clients to establish different connections for each
   server name, even when those server names are hosted by the same
   server.  This restriction introduces several drawbacks:

   o  Address validation is required for each connection establishment
      specifying a different server name, thereby restricting the amount
      of data that a server can initially send.

   o  Distribution of network bandwidth among these connections is
      governed by the startup phase and congestion control dynamics,
      which can lead to unfair distribution for short-lived connections.

   o  It is hard if not impossible to prioritize the transmission of
      some connections among others.

   To resolve these issues, this document defines a QUIC transport
   parameter that expands the scope of the token from the server name to
   a union of the server name and the server's address tuple.

1.1.  Notational Conventions

   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 [RFC2119].

Oku                      Expires October 6, 2019                [Page 2]
Internet-Draft        Address-bound Token for QUIC            April 2019

2.  Overview

   When accepting a new connection, a server sends the
   "address_bound_token" transport parameter indicating to the client
Show full document text