QUIC-LB: Using Load Balancers to Generate QUIC Connection IDs
draft-duke-quic-load-balancers-00

Document Type Active Internet-Draft (individual)
Last updated 2018-02-12
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 WG                                                         M. Duke
Internet Draft                                              F5 Networks
Intended status: Standards Track                      February 12, 2018
Expires: August 12, 2018

       QUIC-LB: Using Load Balancers to Generate QUIC Connection IDs
                   draft-duke-quic-load-balancers-00.txt

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), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on August 12, 2018.

Copyright Notice

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

Duke                   Expires August 12, 2017                 [Page 1]
Internet-Draft                 QUIC-LB                    February 2018

   Section 4.e of the Trust Legal Provisions and are provided without
   warranty as described in the Simplified BSD License.

Abstract

   QUIC connection IDs allow continuation of connections across
   address/port 5-tuple changes, and can store routing information for
   stateless or low-state layer 4 load balancers.  They are also meant
   to prevent linkability of connections across deliberate address
   migration through the use of protected communications between client
   and server. This creates issues for load-balancing intermediaries.
   This specification standardizes the communication between load
   balancers and servers to overcome these issues in a protocol called
   QUIC-LB.

Table of Contents

   1. Introduction...................................................3
      1.1. Terminology...............................................3
   2. Protocol Objectives............................................4
      2.1. Simplicity................................................4
      2.2. Security..................................................4
      2.3. Robustness to Middleboxes.................................4
   3. Protocol Design................................................4
      3.1. Connection ID Generation..................................4
      3.2. Message Exchange..........................................5
      3.3. Load Balancer Trust.......................................6
      3.4. Servers with Zero Stock...................................6
   4. Message Format.................................................6
      4.1. NEW_IDS message...........................................6
      4.2. ID_STOCK message..........................................7
   5. Chained Load Balancers.........................................8
   6. Security Considerations........................................8
   7. IANA Considerations............................................8
   8. References.....................................................9
      8.1. Normative References......................................9
      8.2. Informative References....................................9
   9. Acknowledgments................................................9
   Appendix A. Alternate Approaches to server/load balancer
   coordination problems............................................10
      A.1. Terminating proxies......................................10
      A.2. Unified control of load balancer and server..............10
      A.3. Synchronized Algorithms..................................10

Duke                   Expires August 12, 2018                 [Page 2]
Internet-Draft                 QUIC-LB                    February 2018

1. Introduction

   Server-generated connection IDs create a potential need for out-of-
   band communication. QUIC packets usually contain a connection ID to
   allow endpoints to associate packets with different
   address/port/protocol 5-tuples to the same connection context. This
   feature makes connections robust in the event of NAT rebinding.
Show full document text