From 98b93d088b1509cb5ba21cf8f872327a83a1eb2d Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Wed, 24 Jun 2020 14:45:13 +1000 Subject: [PATCH] Add a Scope section to invariants I'm not committed to this. I think that the document would be fine without it, but it brings less of the manageability concerns into scope than the proposed alternative. Closes #3773. Closes #3774. --- draft-ietf-quic-invariants.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/draft-ietf-quic-invariants.md b/draft-ietf-quic-invariants.md index 794a1b70d9..3bd8cff284 100644 --- a/draft-ietf-quic-invariants.md +++ b/draft-ietf-quic-invariants.md @@ -112,6 +112,23 @@ endpoints use QUIC packets to establish a QUIC connection, which is shared protocol state between those endpoints. +# Scope + +To the extent that other entities are able to participate in communication +between QUIC endpoints, a goal of the QUIC design is to provide technical +measures that prevent interaction with a QUIC connection by entities other than +QUIC endpoints. However, these technical measures are limited in what they can +protect and could vary between versions. + +This document defines what parts of the QUIC protocol are not permitted to vary +between versions. As a consequence, this also guarantees a minimal amount of +information that is made available to entities other than QUIC endpoints. + +Limited interaction with QUIC connections is permitted by entities other than +endpoints, such as load balancers or measurement devices, where interactions are +expressly enabled by endpoints. + + # Notational Conventions Packet diagrams in this document use a format defined in {{QUIC-TRANSPORT}} to