QUIC-LB: Using Load Balancers to Generate QUIC Connection IDs
draft-duke-quic-load-balancers-01
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Martin Duke
|
|
Last updated |
|
2018-05-22
|
|
Replaced by |
|
draft-ietf-quic-load-balancers
|
|
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)
|
QUIC M. Duke
Internet-Draft F5 Networks, Inc.
Intended status: Standards Track May 22, 2018
Expires: November 23, 2018
QUIC-LB: Using Load Balancers to Generate QUIC Connection IDs
draft-duke-quic-load-balancers-01
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.
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 November 23, 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
(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
Duke Expires November 23, 2018 [Page 1]
Internet-Draft QUIC-LB May 2018
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. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Protocol Objectives . . . . . . . . . . . . . . . . . . . . . 3
2.1. Simplicity . . . . . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . . . 5
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 . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 9
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 9
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 9
B.1. Since draft-duke-quic-load-balancers-00 . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
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.
QUIC allows servers (or load balancers) to designate an initial
connection ID to encode useful routing information for load
balancers. It also encourages servers, in packets protected by
cryptography, to provide additional connection IDs to the client.
Show full document text