draft-ietf-quic-load-balancers-03.txt   draft-ietf-quic-load-balancers-04.txt 
QUIC M. Duke QUIC M. Duke
Internet-Draft F5 Networks, Inc. Internet-Draft F5 Networks, Inc.
Intended status: Standards Track N. Banks Intended status: Standards Track N. Banks
Expires: 11 January 2021 Microsoft Expires: 15 February 2021 Microsoft
10 July 2020 14 August 2020
QUIC-LB: Generating Routable QUIC Connection IDs QUIC-LB: Generating Routable QUIC Connection IDs
draft-ietf-quic-load-balancers-03 draft-ietf-quic-load-balancers-04
Abstract Abstract
QUIC connection IDs allow continuation of connections across address/ QUIC connection IDs allow continuation of connections across address/
port 4-tuple changes, and can store routing information for stateless port 4-tuple changes, and can store routing information for stateless
or low-state load balancers. They also can prevent linkability of or low-state load balancers. They also can prevent linkability of
connections across deliberate address migration through the use of connections across deliberate address migration through the use of
protected communications between client and server. This creates protected communications between client and server. This creates
issues for load-balancing intermediaries. This specification issues for load-balancing intermediaries. This specification
standardizes methods for encoding routing information given a small standardizes methods for encoding routing information given a small
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 11 January 2021. This Internet-Draft will expire on 15 February 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
skipping to change at page 2, line 22 skipping to change at page 2, line 22
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. Protocol Objectives . . . . . . . . . . . . . . . . . . . . . 5 2. Protocol Objectives . . . . . . . . . . . . . . . . . . . . . 5
2.1. Simplicity . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Simplicity . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Security . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. Security . . . . . . . . . . . . . . . . . . . . . . . . 5
3. First CID octet . . . . . . . . . . . . . . . . . . . . . . . 6 3. First CID octet . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Config Rotation . . . . . . . . . . . . . . . . . . . . . 6 3.1. Config Rotation . . . . . . . . . . . . . . . . . . . . . 6
3.2. Configuration Failover . . . . . . . . . . . . . . . . . 7 3.2. Configuration Failover . . . . . . . . . . . . . . . . . 7
3.3. Length Self-Description . . . . . . . . . . . . . . . . . 7 3.3. Length Self-Description . . . . . . . . . . . . . . . . . 7
4. Routing Algorithms . . . . . . . . . . . . . . . . . . . . . 7 3.4. Format . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. Routing Algorithms . . . . . . . . . . . . . . . . . . . . . 8
4.1. Plaintext CID Algorithm . . . . . . . . . . . . . . . . . 9 4.1. Plaintext CID Algorithm . . . . . . . . . . . . . . . . . 9
4.1.1. Configuration Agent Actions . . . . . . . . . . . . . 9 4.1.1. Configuration Agent Actions . . . . . . . . . . . . . 9
4.1.2. Load Balancer Actions . . . . . . . . . . . . . . . . 9 4.1.2. Load Balancer Actions . . . . . . . . . . . . . . . . 9
4.1.3. Server Actions . . . . . . . . . . . . . . . . . . . 9 4.1.3. Server Actions . . . . . . . . . . . . . . . . . . . 10
4.2. Obfuscated CID Algorithm . . . . . . . . . . . . . . . . 10 4.2. Stream Cipher CID Algorithm . . . . . . . . . . . . . . . 10
4.2.1. Configuration Agent Actions . . . . . . . . . . . . . 10 4.2.1. Configuration Agent Actions . . . . . . . . . . . . . 10
4.2.2. Load Balancer Actions . . . . . . . . . . . . . . . . 10 4.2.2. Load Balancer Actions . . . . . . . . . . . . . . . . 10
4.2.3. Server Actions . . . . . . . . . . . . . . . . . . . 11 4.2.3. Server Actions . . . . . . . . . . . . . . . . . . . 12
4.3. Stream Cipher CID Algorithm . . . . . . . . . . . . . . . 11 4.3. Block Cipher CID Algorithm . . . . . . . . . . . . . . . 12
4.3.1. Configuration Agent Actions . . . . . . . . . . . . . 12 4.3.1. Configuration Agent Actions . . . . . . . . . . . . . 12
4.3.2. Load Balancer Actions . . . . . . . . . . . . . . . . 12 4.3.2. Load Balancer Actions . . . . . . . . . . . . . . . . 13
4.3.3. Server Actions . . . . . . . . . . . . . . . . . . . 13 4.3.3. Server Actions . . . . . . . . . . . . . . . . . . . 13
4.4. Block Cipher CID Algorithm . . . . . . . . . . . . . . . 13 5. ICMP Processing . . . . . . . . . . . . . . . . . . . . . . . 13
4.4.1. Configuration Agent Actions . . . . . . . . . . . . . 14 6. Retry Service . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.2. Load Balancer Actions . . . . . . . . . . . . . . . . 14 6.1. Common Requirements . . . . . . . . . . . . . . . . . . . 14
4.4.3. Server Actions . . . . . . . . . . . . . . . . . . . 15 6.2. No-Shared-State Retry Service . . . . . . . . . . . . . . 15
5. ICMP Processing . . . . . . . . . . . . . . . . . . . . . . . 15 6.2.1. Configuration Agent Actions . . . . . . . . . . . . . 15
6. Retry Service . . . . . . . . . . . . . . . . . . . . . . . . 15 6.2.2. Service Requirements . . . . . . . . . . . . . . . . 15
6.1. Common Requirements . . . . . . . . . . . . . . . . . . . 16 6.2.3. Server Requirements . . . . . . . . . . . . . . . . . 17
6.2. No-Shared-State Retry Service . . . . . . . . . . . . . . 16 6.3. Shared-State Retry Service . . . . . . . . . . . . . . . 17
6.2.1. Configuration Agent Actions . . . . . . . . . . . . . 17 6.3.1. Configuration Agent Actions . . . . . . . . . . . . . 19
6.2.2. Service Requirements . . . . . . . . . . . . . . . . 17 6.3.2. Service Requirements . . . . . . . . . . . . . . . . 19
6.2.3. Server Requirements . . . . . . . . . . . . . . . . . 18 6.3.3. Server Requirements . . . . . . . . . . . . . . . . . 19
6.3. Shared-State Retry Service . . . . . . . . . . . . . . . 19 7. Configuration Requirements . . . . . . . . . . . . . . . . . 20
6.3.1. Configuration Agent Actions . . . . . . . . . . . . . 21 8. Additional Use Cases . . . . . . . . . . . . . . . . . . . . 21
6.3.2. Service Requirements . . . . . . . . . . . . . . . . 21 8.1. Load balancer chains . . . . . . . . . . . . . . . . . . 21
6.3.3. Server Requirements . . . . . . . . . . . . . . . . . 21 8.2. Moving connections between servers . . . . . . . . . . . 22
7. Configuration Requirements . . . . . . . . . . . . . . . . . 22 9. Version Invariance of QUIC-LB . . . . . . . . . . . . . . . . 22
8. Additional Use Cases . . . . . . . . . . . . . . . . . . . . 23 10. Security Considerations . . . . . . . . . . . . . . . . . . . 23
8.1. Load balancer chains . . . . . . . . . . . . . . . . . . 23 10.1. Attackers not between the load balancer and server . . . 23
8.2. Moving connections between servers . . . . . . . . . . . 24 10.2. Attackers between the load balancer and server . . . . . 24
9. Version Invariance of QUIC-LB . . . . . . . . . . . . . . . . 24 10.3. Multiple Configuration IDs . . . . . . . . . . . . . . . 24
10. Security Considerations . . . . . . . . . . . . . . . . . . . 25 10.4. Limited configuration scope . . . . . . . . . . . . . . 24
10.1. Attackers not between the load balancer and server . . . 25 10.5. Stateless Reset Oracle . . . . . . . . . . . . . . . . . 25
10.2. Attackers between the load balancer and server . . . . . 26 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
10.3. Limited configuration scope . . . . . . . . . . . . . . 26 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
10.4. Stateless Reset Oracle . . . . . . . . . . . . . . . . . 26 12.1. Normative References . . . . . . . . . . . . . . . . . . 25
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 12.2. Informative References . . . . . . . . . . . . . . . . . 25
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 Appendix A. Load Balancer Test Vectors . . . . . . . . . . . . . 26
12.1. Normative References . . . . . . . . . . . . . . . . . . 27 A.1. Plaintext Connection ID Algorithm . . . . . . . . . . . . 26
12.2. Informative References . . . . . . . . . . . . . . . . . 27 A.2. Stream Cipher Connection ID Algorithm . . . . . . . . . . 26
Appendix A. Load Balancer Test Vectors . . . . . . . . . . . . . 27 A.3. Block Cipher Connection ID Algorithm . . . . . . . . . . 27
A.1. Obfuscated Connection ID Algorithm . . . . . . . . . . . 27 Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . 28
A.2. Stream Cipher Connection ID Algorithm . . . . . . . . . . 28 Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 28
A.3. Block Cipher Connection ID Algorithm . . . . . . . . . . 29 C.1. since-draft-ietf-quic-load-balancers-03 . . . . . . . . . 28
Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . 30 C.2. since-draft-ietf-quic-load-balancers-02 . . . . . . . . . 28
Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 30 C.3. since-draft-ietf-quic-load-balancers-01 . . . . . . . . . 28
C.1. since-draft-ietf-quic-load-balancers-02 . . . . . . . . . 30 C.4. since-draft-ietf-quic-load-balancers-00 . . . . . . . . . 29
C.2. since-draft-ietf-quic-load-balancers-01 . . . . . . . . . 30 C.5. Since draft-duke-quic-load-balancers-06 . . . . . . . . . 29
C.3. since-draft-ietf-quic-load-balancers-00 . . . . . . . . . 30 C.6. Since draft-duke-quic-load-balancers-05 . . . . . . . . . 29
C.4. Since draft-duke-quic-load-balancers-06 . . . . . . . . . 30 C.7. Since draft-duke-quic-load-balancers-04 . . . . . . . . . 29
C.5. Since draft-duke-quic-load-balancers-05 . . . . . . . . . 31 C.8. Since draft-duke-quic-load-balancers-03 . . . . . . . . . 29
C.6. Since draft-duke-quic-load-balancers-04 . . . . . . . . . 31 C.9. Since draft-duke-quic-load-balancers-02 . . . . . . . . . 29
C.7. Since draft-duke-quic-load-balancers-03 . . . . . . . . . 31 C.10. Since draft-duke-quic-load-balancers-01 . . . . . . . . . 30
C.8. Since draft-duke-quic-load-balancers-02 . . . . . . . . . 31 C.11. Since draft-duke-quic-load-balancers-00 . . . . . . . . . 30
C.9. Since draft-duke-quic-load-balancers-01 . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
C.10. Since draft-duke-quic-load-balancers-00 . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
1. Introduction 1. Introduction
QUIC packets [QUIC-TRANSPORT] usually contain a connection ID to QUIC packets [QUIC-TRANSPORT] usually contain a connection ID to
allow endpoints to associate packets with different address/port allow endpoints to associate packets with different address/port
4-tuples to the same connection context. This feature makes 4-tuples to the same connection context. This feature makes
connections robust in the event of NAT rebinding. QUIC endpoints connections robust in the event of NAT rebinding. QUIC endpoints
usually designate the connection ID which peers use to address usually designate the connection ID which peers use to address
packets. Server-generated connection IDs create a potential need for packets. Server-generated connection IDs create a potential need for
out-of-band communication to support QUIC. out-of-band communication to support QUIC.
skipping to change at page 6, line 20 skipping to change at page 6, line 20
The first octet of a Connection ID is reserved for two special The first octet of a Connection ID is reserved for two special
purposes, one mandatory (config rotation) and one optional (length purposes, one mandatory (config rotation) and one optional (length
self-description). self-description).
Subsequent sections of this document refer to the contents of this Subsequent sections of this document refer to the contents of this
octet as the "first octet." octet as the "first octet."
3.1. Config Rotation 3.1. Config Rotation
The first two bits of any connection-ID MUST encode the configuration The first two bits of any connection ID MUST encode an identifier for
phase of that ID. QUIC-LB messages indicate the phase of the the configuration that the connection ID uses. This enables
algorithm and parameters that they encode. incremental deployment of new QUIC-LB settings (e.g., keys).
A new configuration may change one or more parameters of the old
configuration, or change the algorithm used.
It is possible for servers to have mutually exclusive sets of
supported algorithms, or for a transition from one algorithm to
another to result in Fail Payloads. The four states encoded in these
two bits allow two mutually exclusive server pools to coexist, and
for each of them to transition to a new set of parameters.
When new configuration is distributed to servers, there will be a When new configuration is distributed to servers, there will be a
transition period when connection IDs reflecting old and new transition period when connection IDs reflecting old and new
configuration coexist in the network. The rotation bits allow load configuration coexist in the network. The rotation bits allow load
balancers to apply the correct routing algorithm and parameters to balancers to apply the correct routing algorithm and parameters to
incoming packets. incoming packets.
Configuration Agents SHOULD make an effort to deliver new Configuration Agents SHOULD deliver new configurations to load
configurations to load balancers before doing so to servers, so that balancers before doing so to servers, so that load balancers are
load balancers are ready to process CIDs using the new parameters ready to process CIDs using the new parameters when they arrive.
when they arrive.
A Configuration Agent SHOULD NOT use a codepoint to represent a new A Configuration Agent SHOULD NOT use a codepoint to represent a new
configuration until it takes precautions to make sure that all configuration until it takes precautions to make sure that all
connections using CIDs with an old configuration at that codepoint connections using CIDs with an old configuration at that codepoint
have closed or transitioned. have closed or transitioned.
Servers MUST NOT generate new connection IDs using an old Servers MUST NOT generate new connection IDs using an old
configuration after receiving a new one from the configuration agent. configuration after receiving a new one from the configuration agent.
Servers MUST send NEW_CONNECTION_ID frames that provide CIDS using Servers MUST send NEW_CONNECTION_ID frames that provide CIDs using
the new configuration, and retire CIDs using the old configuration the new configuration, and retire CIDs using the old configuration
using the "Retire Prior To" field of that frame. using the "Retire Prior To" field of that frame.
It also possible to use these bits for more long-lived distinction of
different configurations, but this has privacy implications (see
Section 10.3).
3.2. Configuration Failover 3.2. Configuration Failover
If a server has not received a valid QUIC-LB configuration, and If a server has not received a valid QUIC-LB configuration, and
believes that low-state, Connection-ID aware load balancers are in believes that low-state, Connection-ID aware load balancers are in
the path, it SHOULD generate connection IDs with the config rotation the path, it SHOULD generate connection IDs with the config rotation
bits set to '11' and SHOULD use the "disable_migration" transport bits set to '11' and SHOULD use the "disable_active_migration"
parameter in all new QUIC connections. It SHOULD NOT send transport parameter in all new QUIC connections. It SHOULD NOT send
NEW_CONNECTION_ID frames with new values. NEW_CONNECTION_ID frames with new values.
A load balancer that sees a connection ID with config rotation bits A load balancer that sees a connection ID with config rotation bits
set to '11' MUST revert to 5-tuple routing. set to '11' MUST revert to 5-tuple routing.
3.3. Length Self-Description 3.3. Length Self-Description
Local hardware cryptographic offload devices may accelerate QUIC Local hardware cryptographic offload devices may accelerate QUIC
servers by receiving keys from the QUIC implementation indexed to the servers by receiving keys from the QUIC implementation indexed to the
connection ID. However, on physical devices operating multiple QUIC connection ID. However, on physical devices operating multiple QUIC
skipping to change at page 7, line 40 skipping to change at page 7, line 34
Note that this is a function of particular server devices and is Note that this is a function of particular server devices and is
irrelevant to load balancers. As such, load balancers MAY omit this irrelevant to load balancers. As such, load balancers MAY omit this
from their configuration. However, the remaining 6 bits in the first from their configuration. However, the remaining 6 bits in the first
octet of the Connection ID are reserved to express the length of the octet of the Connection ID are reserved to express the length of the
following connection ID, not including the first octet. following connection ID, not including the first octet.
A server not using this functionality SHOULD make the six bits appear A server not using this functionality SHOULD make the six bits appear
to be random. to be random.
3.4. Format
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|C R| CID Len |
+-+-+-+-+-+-+-+-+
Figure 1: First Octet Format
The first octet has the following fields:
CR: Config Rotation bits.
CID Len: Length Self-Description (if applicable). Encodes the length
of the Connection ID following the First Octet.
4. Routing Algorithms 4. Routing Algorithms
In QUIC-LB, load balancers do not generate individual connection IDs In QUIC-LB, load balancers do not generate individual connection IDs
to servers. Instead, they communicate the parameters of an algorithm to servers. Instead, they communicate the parameters of an algorithm
to generate routable connection IDs. to generate routable connection IDs.
The algorithms differ in the complexity of configuration at both load The algorithms differ in the complexity of configuration at both load
balancer and server. Increasing complexity improves obfuscation of balancer and server. Increasing complexity improves obfuscation of
the server mapping. the server mapping.
As clients sometimes generate the DCIDs in long headers, these might As clients sometimes generate the DCIDs in long headers, these might
not conform to the expectations of the routing algorithm. These are not conform to the expectations of the routing algorithm. These are
called "non-compliant DCIDs": called "non-compliant DCIDs":
* The DCID might not be long enough for the routing algorithm to * The DCID might not be long enough for the routing algorithm to
process. process.
* The extracted server mapping might not correspond to an active * The extracted server mapping might not correspond to an active
server. server.
* A field that should be all zeroes after decryption may not be so.
Load balancers MUST forward packets with long headers with non- Load balancers MUST forward packets with long headers with non-
compliant DCIDs to an active server using an algorithm of its own compliant DCIDs to an active server using an algorithm of its own
choosing. It need not coordinate this algorithm with the servers. choosing. It need not coordinate this algorithm with the servers.
The algorithm SHOULD be deterministic over short time scales so that The algorithm SHOULD be deterministic over short time scales so that
related packets go to the same server. The design of this algorithm related packets go to the same server. The design of this algorithm
SHOULD consider the version-invariant properties of QUIC described in SHOULD consider the version-invariant properties of QUIC described in
[QUIC-INVARIANTS] to maximize its robustness to future versions of [QUIC-INVARIANTS] to maximize its robustness to future versions of
QUIC. For example, a non-compliant DCID might be converted to an QUIC. For example, a non-compliant DCID might be converted to an
integer and divided by the number of servers, with the modulus used integer and divided by the number of servers, with the modulus used
to forward the packet. The number of servers is usually consistent to forward the packet. The number of servers is usually consistent
skipping to change at page 9, line 27 skipping to change at page 9, line 36
format is depicted in the figure below. format is depicted in the figure below.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| First octet | Server ID (X=8..152) | | First octet | Server ID (X=8..152) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Any (0..152-X) | | Any (0..152-X) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Plaintext CID Format Figure 2: Plaintext CID Format
4.1.1. Configuration Agent Actions 4.1.1. Configuration Agent Actions
The configuration agent selects a number of bytes of the server The configuration agent selects a number of bytes of the server
connection ID to encode individual server IDs, called the "routing connection ID to encode individual server IDs, called the "routing
bytes". The number of bytes MUST have enough entropy to have a bytes". The number of bytes MUST have enough entropy to have a
different code point for each server. different code point for each server.
It also assigns a server ID to each server. It also assigns a server ID to each server.
skipping to change at page 10, line 5 skipping to change at page 10, line 15
4.1.3. Server Actions 4.1.3. Server Actions
The server chooses a connection ID length. This MUST be at least one The server chooses a connection ID length. This MUST be at least one
byte longer than the routing bytes. byte longer than the routing bytes.
When a server needs a new connection ID, it encodes its assigned When a server needs a new connection ID, it encodes its assigned
server ID in consecutive octets beginning with the second. All other server ID in consecutive octets beginning with the second. All other
bits in the connection ID, except for the first octet, MAY be set to bits in the connection ID, except for the first octet, MAY be set to
any other value. These other bits SHOULD appear random to observers. any other value. These other bits SHOULD appear random to observers.
4.2. Obfuscated CID Algorithm 4.2. Stream Cipher CID Algorithm
The Obfuscated CID Algorithm makes an attempt to obscure the mapping The Stream Cipher CID algorithm provides cryptographic protection at
of connections to servers to reduce linkability, while not requiring the cost of additional per-packet processing at the load balancer to
true encryption and decryption. The format is depicted in the figure decrypt every incoming connection ID. The CID format is depicted
below. below.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| First octet | Mixed routing and non-routing bits (64..152) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Obfuscated CID Format
4.2.1. Configuration Agent Actions
The configuration agent selects an arbitrary set of bits of the
server connection ID that it will use to route to a given server,
called the "routing bits". The number of bits MUST have enough
entropy to have a different code point for each server, and SHOULD
have enough entropy so that there are many codepoints for each
server.
The configuration agent MUST NOT select a routing mask with more than
136 routing bits set to 1, which allows for the first octet and up to
2 octets for server purposes in a maximum-length connection ID.
The configuration agent selects a divisor that MUST be larger than
the number of servers. It SHOULD be large enough to accommodate
reasonable increases in the number of servers. The divisor MUST be
an odd integer so certain addition operations do not always produce
an even number.
The configuration agent also assigns each server a "modulus", an
integer between 0 and the divisor minus 1. These MUST be unique for
each server, and SHOULD be distributed across the entire number space
between zero and the divisor.
4.2.2. Load Balancer Actions
Upon receipt of a QUIC packet, the load balancer extracts the
selected bits of the Server CID and expresses them as an unsigned
integer of that length. The load balancer then divides the result by
the chosen divisor. The modulus of this operation maps to the
modulus for the destination server.
Note that any Server CID that contains a server's modulus, plus an
arbitrary integer multiple of the divisor, in the routing bits is
routable to that server regardless of the contents of the non-routing
bits. Outside observers that do not know the divisor or the routing
bits will therefore have difficulty identifying that two Server CIDs
route to the same server.
Note also that not all Connection IDs are necessarily routable, as
the computed modulus may not match one assigned to any server. These
DCIDs are non-compliant as described above.
4.2.3. Server Actions
The server chooses a connection ID length. This MUST contain all of
the routing bits and MUST be at least 9 octets to provide adequate
entropy.
When a server needs a new connection ID, it adds an arbitrary
nonnegative integer multiple of the divisor to its modulus, without
exceeding the maximum integer value implied by the number of routing
bits. The choice of multiple should appear random within these
constraints.
The server encodes the result in the routing bits. It MAY put any
other value into bits that used neither for routing nor config
rotation. These bits SHOULD appear random to observers.
4.3. Stream Cipher CID Algorithm
The Stream Cipher CID algorithm provides true cryptographic
protection, rather than mere obfuscation, at the cost of additional
per-packet processing at the load balancer to decrypt every incoming
connection ID. The CID format is depicted below.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| First Octet | Nonce (X=64..128) | | First Octet | Nonce (X=64..128) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Encrypted Server ID (Y=8..152-X) | | Encrypted Server ID (Y=8..152-X) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| For server use (0..152-X-Y) | | For server use (0..152-X-Y) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Stream Cipher CID Format Figure 3: Stream Cipher CID Format
4.3.1. Configuration Agent Actions 4.2.1. Configuration Agent Actions
The configuration agent assigns a server ID to every server in its The configuration agent assigns a server ID to every server in its
pool, and determines a server ID length (in octets) sufficiently pool, and determines a server ID length (in octets) sufficiently
large to encode all server IDs, including potential future servers. large to encode all server IDs, including potential future servers.
The configuration agent also selects a nonce length and an 16-octet The configuration agent also selects a nonce length and an 16-octet
AES-ECB key to use for connection ID decryption. The nonce length AES-ECB key to use for connection ID decryption. The nonce length
MUST be at least 8 octets and no more than 16 octets. The nonce MUST be at least 8 octets and no more than 16 octets. The nonce
length and server ID length MUST sum to 19 or fewer octets. length and server ID length MUST sum to 19 or fewer octets.
4.3.2. Load Balancer Actions 4.2.2. Load Balancer Actions
Upon receipt of a QUIC packet, the load balancer extracts as many of Upon receipt of a QUIC packet, the load balancer extracts as many of
the earliest octets from the destination connection ID as necessary the earliest octets from the destination connection ID as necessary
to match the nonce length. The server ID immediately follows. to match the nonce length. The server ID immediately follows.
The load balancer decrypts the nonce and the server ID using the The load balancer decrypts the nonce and the server ID using the
following three pass algorithm: following three pass algorithm:
* Pass 1: The load balancer decrypts the server ID using 128-bit AES * Pass 1: The load balancer decrypts the server ID using 128-bit AES
Electronic Codebook (ECB) mode, much like QUIC header protection. Electronic Codebook (ECB) mode, much like QUIC header protection.
skipping to change at page 13, line 24 skipping to change at page 12, line 5
This three-pass algorithm is a simplified version of the FFX This three-pass algorithm is a simplified version of the FFX
algorithm, with the property that each encrypted nonce value depends algorithm, with the property that each encrypted nonce value depends
on all server ID bits, and each encrypted server ID bit depends on on all server ID bits, and each encrypted server ID bit depends on
all nonce bits and all server ID bits. This mitigates attacks all nonce bits and all server ID bits. This mitigates attacks
against stream ciphers in which attackers simply flip encrypted against stream ciphers in which attackers simply flip encrypted
server-ID bits. server-ID bits.
The output of the decryption is the server ID that the load balancer The output of the decryption is the server ID that the load balancer
uses for routing. uses for routing.
4.3.3. Server Actions 4.2.3. Server Actions
When generating a routable connection ID, the server writes arbitrary When generating a routable connection ID, the server writes arbitrary
bits into its nonce octets, and its provided server ID into the bits into its nonce octets, and its provided server ID into the
server ID octets. Servers MAY opt to have a longer connection ID server ID octets. Servers MAY opt to have a longer connection ID
beyond the nonce and server ID. The additional bits MAY encode beyond the nonce and server ID. The additional bits MAY encode
additional information, but SHOULD appear essentially random to additional information, but SHOULD appear essentially random to
observers. observers.
If the decrypted nonce bits increase monotonically, that guarantees If the decrypted nonce bits increase monotonically, that guarantees
that nonces are not reused between connection IDs from the same that nonces are not reused between connection IDs from the same
server. server.
The server encrypts the server ID using exactly the algorithm as The server encrypts the server ID using exactly the algorithm as
described in Section 4.3.2, performing the three passes in reverse described in Section 4.2.2, performing the three passes in reverse
order. order.
4.4. Block Cipher CID Algorithm 4.3. Block Cipher CID Algorithm
The Block Cipher CID Algorithm, by using a full 16 octets of The Block Cipher CID Algorithm, by using a full 16 octets of
plaintext and a 128-bit cipher, provides higher cryptographic plaintext and a 128-bit cipher, provides higher cryptographic
protection and detection of non-compliant connection IDs. However, protection and detection of non-compliant connection IDs. However,
it also requires connection IDs of at least 17 octets, increasing it also requires connection IDs of at least 17 octets, increasing
overhead of client-to-server packets. overhead of client-to-server packets.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| First octet | Encrypted server ID (X=8..128) | | First octet | Encrypted server ID (X=8..128) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Encrypted Zero Padding (Y=0..128-X) | | Encrypted bits for server use (128-X) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Encrypted bits for server use (128-X-Y) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Unencrypted bits for server use (0..24) | | Unencrypted bits for server use (0..24) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Block Cipher CID Format Figure 4: Block Cipher CID Format
4.4.1. Configuration Agent Actions 4.3.1. Configuration Agent Actions
The configuration agent assigns a server ID to every server in its The configuration agent assigns a server ID to every server in its
pool, and determines a server ID length (in octets) sufficiently pool, and determines a server ID length (in octets) sufficiently
large to encode all server IDs, including potential future servers. large to encode all server IDs, including potential future servers.
The server ID will start in the second octet of the decrypted The server ID will start in the second octet of the decrypted
connection ID and occupy continuous octets beyond that. connection ID and occupy continuous octets beyond that.
The configuration agent selects a zero-padding length. This SHOULD They server ID length MUST be no more than 16 octets and SHOULD sum
be at least four octets to allow detection of non-compliant DCIDs. to no more than 12 octets, to provide servers adequate space to
The server ID and zero- padding length MUST sum to no more than 16 encode their own opaque data.
octets. They SHOULD sum to no more than 12 octets, to provide
servers adequate space to encode their own opaque data.
The configuration agent also selects an 16-octet AES-ECB key to use The configuration agent also selects an 16-octet AES-ECB key to use
for connection ID decryption. for connection ID decryption.
4.4.2. Load Balancer Actions 4.3.2. Load Balancer Actions
Upon receipt of a QUIC packet, the load balancer reads the first Upon receipt of a QUIC packet, the load balancer reads the first
octet to obtain the config rotation bits. It then decrypts the octet to obtain the config rotation bits. It then decrypts the
subsequent 16 octets using AES-ECB decryption and the chosen key. subsequent 16 octets using AES-ECB decryption and the chosen key.
The decrypted plaintext contains the server id, zero padding, and The decrypted plaintext contains the server id and opaque server data
opaque server data in that order. The load balancer uses the server in that order. The load balancer uses the server ID octets for
ID octets for routing. routing.
4.4.3. Server Actions 4.3.3. Server Actions
When generating a routable connection ID, the server MUST choose a When generating a routable connection ID, the server MUST choose a
connection ID length between 17 and 20 octets. The server writes its connection ID length between 17 and 20 octets. The server writes its
provided server ID into the server ID octets, zeroes into the zero- provided server ID into the server ID octets and arbitrary bits into
padding octets, and arbitrary bits into the remaining bits. These the remaining bits. These arbitrary bits MAY encode additional
arbitrary bits MAY encode additional information. Bits in the first, information. Bits in the eighteenth, nineteenth, and twentieth
eighteenth, nineteenth, and twentieth octets SHOULD appear octets SHOULD appear essentially random to observers. The first
essentially random to observers. The first octet is reserved as octet is reserved as described in Section 3.
described in Section 3.
The server then encrypts the second through seventeenth octets using The server then encrypts the second through seventeenth octets using
the 128-bit AES-ECB cipher. the 128-bit AES-ECB cipher.
5. ICMP Processing 5. ICMP Processing
For protocols where 4-tuple load balancing is sufficient, it is For protocols where 4-tuple load balancing is sufficient, it is
straightforward to deliver ICMP packets from the network to the straightforward to deliver ICMP packets from the network to the
correct server, by reading the IP and transport-layer headers to correct server, by reading the IP and transport-layer headers to
obtain the 4-tuple. When routing is based on connection ID, further obtain the 4-tuple. When routing is based on connection ID, further
skipping to change at page 22, line 26 skipping to change at page 20, line 26
QUIC-LB requires common configuration to synchronize understanding of QUIC-LB requires common configuration to synchronize understanding of
encodings and guarantee explicit consent of the server. encodings and guarantee explicit consent of the server.
The load balancer and server MUST agree on a routing algorithm and The load balancer and server MUST agree on a routing algorithm and
the relevant parameters for that algorithm. the relevant parameters for that algorithm.
For Plaintext CID Routing, this consists of the Server ID and the For Plaintext CID Routing, this consists of the Server ID and the
routing bytes. The Server ID is unique to each server, and the routing bytes. The Server ID is unique to each server, and the
routing bytes are global. routing bytes are global.
For Obfuscated CID Routing, this consists of the Routing Bits,
Divisor, and Modulus. The Modulus is unique to each server, but the
others MUST be global.
For Stream Cipher CID Routing, this consists of the Server ID, Server For Stream Cipher CID Routing, this consists of the Server ID, Server
ID Length, Key, and Nonce Length. The Server ID is unique to each ID Length, Key, and Nonce Length. The Server ID is unique to each
server, but the others MUST be global. The authentication token MUST server, but the others MUST be global. The authentication token MUST
be distributed out of band for this algorithm to operate. be distributed out of band for this algorithm to operate.
For Block Cipher CID Routing, this consists of the Server ID, Server For Block Cipher CID Routing, this consists of the Server ID, Server
ID Length, Key, and Zero-Padding Length. The Server ID is unique to ID Length, Key, and Zero-Padding Length. The Server ID is unique to
each server, but the others MUST be global. each server, but the others MUST be global.
A full QUIC-LB configuration MUST also specify the information A full QUIC-LB configuration MUST also specify the information
content of the first CID octet and the presence and mode of any Retry content of the first CID octet and the presence and mode of any Retry
Service. Service.
The following pseudocode describes the data items necessary to store The following pseudocode describes the data items necessary to store
a full QUIC-LB configuration at the server. It is meant to describe a full QUIC-LB configuration at the server. It is meant to describe
the conceptual range and not specify the presentation of such the conceptual range and not specify the presentation of such
configuration in an internet packet. The comments signify the range configuration in an internet packet. The comments signify the range
of acceptable values where applicable. of acceptable values where applicable.
uint2 config_rotation_bits; uint2 config_rotation_bits;
boolean first_octet_encodes_cid_length; boolean first_octet_encodes_cid_length;
enum { none, non_shared_state, shared_state } retry_service; enum { none, non_shared_state, shared_state } retry_service;
select (retry_service) { select (retry_service) {
case none: null; case none: null;
case non_shared_state: uint32 list_of_quic_versions[]; case non_shared_state: uint32 list_of_quic_versions[];
case shared_state: uint8 key[16]; case shared_state: uint8 key[16];
} retry_service_config; } retry_service_config;
enum { none, plaintext, obfuscated, stream_cipher, block_cipher } enum { none, plaintext, stream_cipher, block_cipher }
routing_algorithm; routing_algorithm;
select (routing_algorithm) { select (routing_algorithm) {
case none: null; case none: null;
case plaintext: struct { case plaintext: struct {
uint8 server_id_length; /* 1..19 */ uint8 server_id_length; /* 1..19 */
uint8 server_id[server_id_length]; uint8 server_id[server_id_length];
} plaintext_config; } plaintext_config;
case obfuscated: struct { case stream_cipher: struct {
uint8 routing_bit_mask[19]; uint8 nonce_length; /* 8..16 */
uint16 divisor; /* Must be odd */ uint8 server_id_length; /* 1..(19 - nonce_length) */
uint16 modulus; /* 0..(divisor - 1) */ uint8 server_id[server_id_length];
} obfuscated_config; uint8 key[16];
case stream_cipher: struct { } stream_cipher_config;
uint8 nonce_length; /* 8..16 */ case block_cipher: struct {
uint8 server_id_length; /* 1..(19 - nonce_length) */ uint8 server_id_length;
uint8 server_id[server_id_length]; uint8 server_id[server_id_length];
uint8 key[16]; uint8 key[16];
} stream_cipher_config; } block_cipher_config;
case block_cipher: struct { } routing_algorithm_config;
uint8 server_id_length;
uint8 zero_padding_length; /* 0..(16 - server_id_length) */
uint8 server_id[server_id_length];
uint8 key[16];
} block_cipher_config;
} routing_algorithm_config;
8. Additional Use Cases 8. Additional Use Cases
This section discusses considerations for some deployment scenarios This section discusses considerations for some deployment scenarios
not implied by the specification above. not implied by the specification above.
8.1. Load balancer chains 8.1. Load balancer chains
Some network architectures may have multiple tiers of low-state load Some network architectures may have multiple tiers of low-state load
balancers, where a first tier of devices makes a routing decision to balancers, where a first tier of devices makes a routing decision to
skipping to change at page 25, line 47 skipping to change at page 23, line 47
patterns, and therefore efforts to frustrate any analysis of server patterns, and therefore efforts to frustrate any analysis of server
ID encoding have diminishing returns. ID encoding have diminishing returns.
10.1. Attackers not between the load balancer and server 10.1. Attackers not between the load balancer and server
Any attacker might open a connection to the server infrastructure and Any attacker might open a connection to the server infrastructure and
aggressively simulate migration to obtain a large sample of IDs that aggressively simulate migration to obtain a large sample of IDs that
map to the same server. It could then apply analytical techniques to map to the same server. It could then apply analytical techniques to
try to obtain the server encoding. try to obtain the server encoding.
The Stream and Block Cipher CID algorithms provide robust entropy to The Stream and Block Cipher CID algorithms provide robust protection
making any sort of linkage. The Obfuscated CID obscures the mapping against any sort of linkage. The Plaintext CID algorithm makes no
and prevents trivial brute-force attacks to determine the routing attempt to protect this encoding.
parameters, but does not provide robust protection against
sophisticated attacks.
Were this analysis to obtain the server encoding, then on-path Were this analysis to obtain the server encoding, then on-path
observers might apply this analysis to correlating different client observers might apply this analysis to correlating different client
IP addresses. IP addresses.
10.2. Attackers between the load balancer and server 10.2. Attackers between the load balancer and server
Attackers in this privileged position are intrinsically able to map Attackers in this privileged position are intrinsically able to map
two connection IDs to the same server. The QUIC-LB algorithms do two connection IDs to the same server. The QUIC-LB algorithms do
prevent the linkage of two connection IDs to the same individual prevent the linkage of two connection IDs to the same individual
connection if servers make reasonable selections when generating new connection if servers make reasonable selections when generating new
IDs for that connection. IDs for that connection.
10.3. Limited configuration scope 10.3. Multiple Configuration IDs
During the period in which there are multiple deployed configuration
IDs (see Section 3.1), there is a slight increase in linkability.
The server space is effectively divided into segments with CIDs that
have different config rotation bits. Entities that manage servers
SHOULD strive to minimize these periods by quickly deploying new
configurations across the server pool.
10.4. Limited configuration scope
A simple deployment of QUIC-LB in a cloud provider might use the same A simple deployment of QUIC-LB in a cloud provider might use the same
global QUIC-LB configuration across all its load balancers that route global QUIC-LB configuration across all its load balancers that route
to customer servers. An attacker could then simply become a to customer servers. An attacker could then simply become a
customer, obtain the configuration, and then extract server IDs of customer, obtain the configuration, and then extract server IDs of
other customers' connections at will. other customers' connections at will.
To avoid this, the configuration agent SHOULD issue QUIC-LB To avoid this, the configuration agent SHOULD issue QUIC-LB
configurations to mutually distrustful servers that have different configurations to mutually distrustful servers that have different
keys (for the block cipher or stream cipher algorithms) or routing keys for encryption algorithms. The load balancers can distinguish
masks and divisors (for the obfuscated algorithm). The load these configurations by external IP address, or by assigning
balancers can distinguish these configurations by external IP different values to the config rotation bits (Section 3.1). Note
address, or by assigning different values to the config rotation bits that either solution has a privacy impact; see Section 10.3.
(Section 3.1). Note that either of these techniques exposes
information to outside observers, as traffic destined for each server
set can be easily distinguished.
These techniques are not necessary for the plaintext algorithm, as it These techniques are not necessary for the plaintext algorithm, as it
does not attempt to conceal the server ID. does not attempt to conceal the server ID.
10.4. Stateless Reset Oracle 10.5. Stateless Reset Oracle
Section 21.9 of [QUIC-TRANSPORT] discusses the Stateless Reset Oracle Section 21.9 of [QUIC-TRANSPORT] discusses the Stateless Reset Oracle
attack. For a server deployment to be vulnerable, an attacking attack. For a server deployment to be vulnerable, an attacking
client must be able to cause two packets with the same Destination client must be able to cause two packets with the same Destination
CID to arrive at two different servers that share the same CID to arrive at two different servers that share the same
cryptographic context for Stateless Reset tokens. As QUIC-LB cryptographic context for Stateless Reset tokens. As QUIC-LB
requires deterministic routing of DCIDs over the life of a requires deterministic routing of DCIDs over the life of a
connection, it is a sufficient means of avoiding an Oracle without connection, it is a sufficient means of avoiding an Oracle without
additional measures. additional measures.
skipping to change at page 27, line 41 skipping to change at page 26, line 14
Appendix A. Load Balancer Test Vectors Appendix A. Load Balancer Test Vectors
Because any connection ID encoding in this specification includes Because any connection ID encoding in this specification includes
many bits for server use without affecting extraction of the server many bits for server use without affecting extraction of the server
ID, there are many possible connection IDs for any given set of ID, there are many possible connection IDs for any given set of
parameters. However, every connection ID should result in a unique parameters. However, every connection ID should result in a unique
server ID. The following connection IDs can be used to verify that a server ID. The following connection IDs can be used to verify that a
load balancer implementation extracts the correct server ID. load balancer implementation extracts the correct server ID.
A.1. Obfuscated Connection ID Algorithm A.1. Plaintext Connection ID Algorithm
The following section lists a set of OCID load balancer
configuration, followed by five CIDs from which the load balancer can
extract the server ID.
cr_bits 0x0 length_self_encoding: y bitmask ddc2f17788d77e3239b4ea TBD
divisor 345
cid 0b72715d4745ce26cca8c750 sid b
cid 0b63a1785b6c0b0857225e96 sid 3f
cid 0b66474fa11329e6bb947818 sid 147
cid 0b34bd7c0882deb0252e2a58 sid ca
cid 0b0506ee792163bf9330dc0a sid 14d
cr_bits 0x1 length_self_encoding: n bitmask A.2. Stream Cipher Connection ID Algorithm
4855d35f5b88ddada153af61b6707ee646 divisor 301
cid 542dc4c09e2d548e508dc825bbbca991c131 sid 8 cr_bits 0x0 length_self_encoding: y nonce_len 10 sid_len 1 key
cid 47988071f9f03a25c322cc6fb1d57151d26f sid 93 9c46142f1597511357cf437841721d4b
cid 6a13e05071f74cdb7d0dc24d72687b21e1d1 sid c0
cid 4323c129650c7ee66f37266044ef52e74ffa sid 60
cid 5e95f77e7e66891b57c224c5781c8c5dd8ba sid 8f
cr_bits 0x0 length_self_encoding: y bitmask 9f98bd3df66338c2d2c6 cid 0b05be7bf896ed26cb4cc59a sid ab cid 0b43909398577dd7df1597d4 sid
divisor 459 37 cid 0bf85fa27034785803747464 sid 0e cid 0bc630c588fdecbfbdb62e61
sid 44 cid 0b8788901684f5d4e4dc6aeb sid 83
cid 0ad52216e7798c28340fd6 sid 125 cr_bits 0x0 length_self_encoding: n nonce_len 9 sid_len 2 key
cid 0a78f8ecbd087083639f94 sid 4b 434ae6fbf36aca0773a6a75f10e3f747
cid 0ac7e70a5fe6b353b824aa sid 12
cid 0af9612ae5ccba3ef98b81 sid d1
cid 0a94ab209ea1d2e1e23751 sid 5d
cr_bits 0x2 length_self_encoding: n bitmask dfba93c4f98f57103f5ae331 cid 08644a29067622f363d4c83e sid 846a cid 234b2899f9b213a70abfe193
divisor 461 sid 4417 cid 3ff4ef53bbaad327c1e18fa5 sid 7554 cid
08a0eaf4cc08f184e6cf7743 sid b78a cid 3fb2f5cf1b3e08bf97709c42 sid
ed7e
cid 8b70b8c69e40ef2f3f8937e817 sid d3 cr_bits 0x0 length_self_encoding: y nonce_len 12 sid_len 3 key
cid b1828830ea1789dab13a043795 sid 44 02e895bf84f6a80c3c7156da88a96755
cid 90604a580baa3eb0a47812e490 sid 137
cid a5b4bc309337ff73e143ff6deb sid 9f
cid fce75c0a984a79d3b4af40d155 sid 127
cr_bits 0x0 length_self_encoding: y bitmask 8320fefc5309f7aa670476 cid 0f7405813570b8f9a6a10564d7b92834 sid 49023c cid
divisor 379 0f3bb656319c6af210239dcaef77d3b9 sid b0a8ce cid
0f3ae6d54ee97fc6907b5e2d60436caf sid 21f035 cid
0f4774918a6576c88f85829306f6450f sid 9e46ea cid
0f7467db6ca1eb4c185e642b0c9f8f44 sid c33db0
cid 0bb110af53dca7295e7d4b7e sid 101 cr_bits 0x0 length_self_encoding: n nonce_len 11 sid_len 4 key
cid 0b0d284cdff364a634a4b93b sid e3 ccb612da03f5dc205faf9b0b1d5429cb
cid 0b82ff1555c4a95f9b198090 sid 14e
cid 0b7a427d3e508ad71e98b797 sid 14e
cid 0b71d1d4e3e3cd54d435b3fd sid eb
A.2. Stream Cipher Connection ID Algorithm cid 0c4b23e27639aef72f861ad2dce39d96 sid 125fdba1 cid
063ed9a173d22be11818b77a3bd5ec37 sid 0f3f82bc cid
1a14e39b0f6ca6a3a48f6fdd2083fa09 sid 05950af2 cid
36cb4df5a7776edb21ec87c35c24e988 sid 3cb80d59 cid
05749809112a91327fef4b3152335298 sid 4746cb79
cr_bits 0x0 length_self_encoding: y nonce_len 8 sid_len 5 key
625696d413ea1a352401afce6eec2432
TBD cid 0d2a7b43eeaac8b36fce2c14ac96 sid 4b00da143a cid
0ddd6cdb6685e75b91f4a1bb0dde sid f9aa795663 cid
0d870ea4d173d29484e41ea4a189 sid e430dcfb3f cid
0df12abe175241b5ab035d23910f sid 8bc66a2596 cid
0d390df5de76903ca94b2e9daa49 sid 7637d0c172
A.3. Block Cipher Connection ID Algorithm A.3. Block Cipher Connection ID Algorithm
Like the previous section, the text below lists a set of load Like the previous section, the text below lists a set of load
balancer configuration and 5 CIDs generated with that configuration. balancer configuration and 5 CIDs generated with that configuration.
cr_bits 0x0 length_self_encoding: y sid_len 1 zp_len 11 key cr_bits 0x0 length_self_encoding: y sid_len 1 zp_len 11 key
8c24cb9b9c3289b4ee63c3f3d7f93a9a 8c24cb9b9c3289b4ee63c3f3d7f93a9a
cid: 1378e44f874642624fa69e7b4aec15a2a678b8b5 sid: 48 cid: 1378e44f874642624fa69e7b4aec15a2a678b8b5 sid: 48
skipping to change at page 30, line 17 skipping to change at page 28, line 26
cid: 93744f4bedf95e04dd6607592ecf775825403093 sid: e264d714d2 cid: 93744f4bedf95e04dd6607592ecf775825403093 sid: e264d714d2
cid: 93256308e3d349f8839dec840b0a90c7e7a1fc20 sid: 618b07791f cid: 93256308e3d349f8839dec840b0a90c7e7a1fc20 sid: 618b07791f
Appendix B. Acknowledgments Appendix B. Acknowledgments
Appendix C. Change Log Appendix C. Change Log
*RFC Editor's Note:* Please remove this section prior to *RFC Editor's Note:* Please remove this section prior to
publication of a final version of this document. publication of a final version of this document.
C.1. since-draft-ietf-quic-load-balancers-02 C.1. since-draft-ietf-quic-load-balancers-03
* Improved Config Rotation text
* Added stream cipher test vectors
* Deleted the Obfuscated CID algorithm
C.2. since-draft-ietf-quic-load-balancers-02
* Replaced stream cipher algorithm with three-pass version * Replaced stream cipher algorithm with three-pass version
* Updated Retry format to encode info for required TPs * Updated Retry format to encode info for required TPs
* Added discussion of version invariance * Added discussion of version invariance
* Cleaned up text about config rotation * Cleaned up text about config rotation
* Added Reset Oracle and limited configuration considerations * Added Reset Oracle and limited configuration considerations
* Allow dropped long-header packets for known QUIC versions * Allow dropped long-header packets for known QUIC versions
C.2. since-draft-ietf-quic-load-balancers-01 C.3. since-draft-ietf-quic-load-balancers-01
* Test vectors for load balancer decoding * Test vectors for load balancer decoding
* Deleted remnants of in-band protocol * Deleted remnants of in-band protocol
* Light edit of Retry Services section * Light edit of Retry Services section
* Discussed load balancer chains * Discussed load balancer chains
C.3. since-draft-ietf-quic-load-balancers-00 C.4. since-draft-ietf-quic-load-balancers-00
* Removed in-band protocol from the document * Removed in-band protocol from the document
C.4. Since draft-duke-quic-load-balancers-06 C.5. Since draft-duke-quic-load-balancers-06
* Switch to IETF WG draft. * Switch to IETF WG draft.
C.5. Since draft-duke-quic-load-balancers-05 C.6. Since draft-duke-quic-load-balancers-05
* Editorial changes * Editorial changes
* Made load balancer behavior independent of QUIC version * Made load balancer behavior independent of QUIC version
* Got rid of token in stream cipher encoding, because server might * Got rid of token in stream cipher encoding, because server might
not have it not have it
* Defined "non-compliant DCID" and specified rules for handling * Defined "non-compliant DCID" and specified rules for handling
them. them.
* Added psuedocode for config schema * Added psuedocode for config schema
C.6. Since draft-duke-quic-load-balancers-04 C.7. Since draft-duke-quic-load-balancers-04
* Added standard for retry services * Added standard for retry services
C.7. Since draft-duke-quic-load-balancers-03 C.8. Since draft-duke-quic-load-balancers-03
* Renamed Plaintext CID algorithm as Obfuscated CID * Renamed Plaintext CID algorithm as Obfuscated CID
* Added new Plaintext CID algorithm * Added new Plaintext CID algorithm
* Updated to allow 20B CIDs * Updated to allow 20B CIDs
* Added self-encoding of CID length * Added self-encoding of CID length
C.8. Since draft-duke-quic-load-balancers-02 C.9. Since draft-duke-quic-load-balancers-02
* Added Config Rotation * Added Config Rotation
* Added failover mode * Added failover mode
* Tweaks to existing CID algorithms * Tweaks to existing CID algorithms
* Added Block Cipher CID algorithm * Added Block Cipher CID algorithm
* Reformatted QUIC-LB packets * Reformatted QUIC-LB packets
C.9. Since draft-duke-quic-load-balancers-01 C.10. Since draft-duke-quic-load-balancers-01
* Complete rewrite * Complete rewrite
* Supports multiple security levels * Supports multiple security levels
* Lightweight messages * Lightweight messages
C.10. Since draft-duke-quic-load-balancers-00 C.11. Since draft-duke-quic-load-balancers-00
* Converted to markdown * Converted to markdown
* Added variable length connection IDs * Added variable length connection IDs
Authors' Addresses Authors' Addresses
Martin Duke Martin Duke
F5 Networks, Inc. F5 Networks, Inc.
 End of changes. 61 change blocks. 
287 lines changed or deleted 209 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/