Re: [quicwg/base-drafts] Added normative text to invariants (#3774)

[Mike Bishop <[e-mail]>]

@MikeBishop approved this pull request.



> +# Requirements for Intermediaries
+
+An intermediary MAY observe the QUIC version in certain packets, statefully note
+the version associated with the connection IDs (see {{connection-id}}) in the
+packet, and if it understands that version, parse and process packets with one
+of those connection IDs without regard for the invariants in this document.
+
+Intermediaries MUST implement a mode that, if they cannot associate a version
+with a packet's connection ID or do not understand the associated QUIC version,
+uses only the invariant fields described in this document to execute its
+function(s). This might mean that the intermediary cannot accomplish its
+function(s) at all, or that it implements a default behavior.
+
+Intermediaries MUST NOT implement a default behavior of dropping packets of QUIC
+versions they do not understand, or packets that have a connection ID they
+cannot associate with a QUIC version.

Perhaps "MUST NOT drop packets on the basis of..." would be avoid the wiggles of "default"?

> +packet, and if it understands that version, parse and process packets with one
+of those connection IDs without regard for the invariants in this document.
+
+Intermediaries MUST implement a mode that, if they cannot associate a version
+with a packet's connection ID or do not understand the associated QUIC version,
+uses only the invariant fields described in this document to execute its
+function(s). This might mean that the intermediary cannot accomplish its
+function(s) at all, or that it implements a default behavior.
+
+Intermediaries MUST NOT implement a default behavior of dropping packets of QUIC
+versions they do not understand, or packets that have a connection ID they
+cannot associate with a QUIC version.
+
+Specifications for intermediaries SHOULD document any implicit assumptions they
+are making about endpoint behavior beyond the invariants in this document, and
+the impact if future versions of QUIC violate those assumptions.

```suggestion
the impact if future versions of QUIC do not conform to those assumptions.
```
"Violate" has a negative connotation, and behavior changes aren't something we want to discourage.

> @@ -234,7 +281,7 @@ and is not constrained by this specification.
 The remainder of the packet has version-specific semantics.
 
 
-## Connection ID
+## Connection ID {#connection-id}

Nothing wrong with doing this, but it's pointless since this would be the default anchor generated for this section title anyway.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3774#pullrequestreview-435175866