QUIC-LB: Generating Routable QUIC Connection IDs
draft-duke-quic-load-balancers-02

Document Type Active Internet-Draft (individual)
Last updated 2018-09-17
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                                                             M. Duke
Internet-Draft                                         F5 Networks, Inc.
Intended status: Standards Track                      September 17, 2018
Expires: March 21, 2019

            QUIC-LB: Generating Routable QUIC Connection IDs
                    draft-duke-quic-load-balancers-02

Abstract

   QUIC connection IDs allow continuation of connections across address/
   port 4-tuple changes, and can store routing information for stateless
   or low-state load balancers.  They also can 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 methods for encoding routing information and proposes an
   optional protocol called QUIC_LB to exchange the parameters of that
   encoding.

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

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
   (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

Duke                     Expires March 21, 2019                 [Page 1]
Internet-Draft                   QUIC-LB                  September 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Protocol Objectives . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Simplicity  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Security  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Robustness to Middleboxes . . . . . . . . . . . . . . . .   5
     2.4.  Load Balancer Chains  . . . . . . . . . . . . . . . . . .   5
   3.  Routing Algorithms  . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Plaintext CID Algorithm . . . . . . . . . . . . . . . . .   6
       3.1.1.  Load Balancer Actions . . . . . . . . . . . . . . . .   6
       3.1.2.  Server Actions  . . . . . . . . . . . . . . . . . . .   6
     3.2.  Encrypted CID Algorithm . . . . . . . . . . . . . . . . .   7
       3.2.1.  Load Balancer Actions . . . . . . . . . . . . . . . .   7
       3.2.2.  Server Actions  . . . . . . . . . . . . . . . . . . .   8
   4.  Protocol Description  . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Out of band sharing . . . . . . . . . . . . . . . . . . .   8
     4.2.  QUIC-LB Message Exchange  . . . . . . . . . . . . . . . .   8
       4.2.1.  Packet Header Format  . . . . . . . . . . . . . . . .   9
       4.2.2.  Ack Payload . . . . . . . . . . . . . . . . . . . . .   9
       4.2.3.  Fail Payload  . . . . . . . . . . . . . . . . . . . .  10
       4.2.4.  Routing Info Payload  . . . . . . . . . . . . . . . .  11
       4.2.5.  Encrypted CID Payload . . . . . . . . . . . . . . . .  11
       4.2.6.  Server ID Payload . . . . . . . . . . . . . . . . . .  12
       4.2.7.  Modulus Payload . . . . . . . . . . . . . . . . . . .  13
   5.  Configuration Requirements  . . . . . . . . . . . . . . . . .  13
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     6.1.  Outside attackers . . . . . . . . . . . . . . . . . . . .  14
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  15
   Appendix B.  Change Log . . . . . . . . . . . . . . . . . . . . .  15
     B.1.  Since draft-duke-quic-load-balancers-00 . . . . . . . . .  15
Show full document text