Re: [quicwg/base-drafts] Tolerate unknown stream types, add greasing (#1525)

[Mike Bishop <[e-mail]>]

MikeBishop commented on this pull request.



>  unknown. Implementations SHOULD NOT send stream types the peer is not already
-known to support, since a stream error can be promoted to a connection error at
-the peer's discretion (see {{errors}}).
+known to support. Recipients of unknown stream types MAY trigger a QUIC
+STOP_SENDING frame with an error code of HTTP_UNKNOWN_STREAM_TYPE, but MUST NOT
+consider such streams to be an error of any kind.
+
+### Reserved Stream Types {#stream-grease}
+
+Stream types of the format `0x1f * N` are reserved to exercise the requirement
+that unknown types be ignored. These streams have no semantic meaning, and can
+be sent when application-layer padding is desired.  They MAY also be sent on

Perhaps.  HTTP/2 allowed padding on the HEADERS and DATA frames, to make analysis of the traffic more difficult.  QUIC can pad individual packets to different / uniform sizes, but I'm assuming that most stacks won't generate traffic where none exists.  An application layer can make analysis more difficult by sending traffic even when no requests are happening.

-- 
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/1525#discussion_r200708927