diff --git a/http/bk_nits/draft-ietf-quic-http.html b/http/bk_nits/draft-ietf-quic-http.html index 3f5a5aff5c..d949a5977e 100644 --- a/http/bk_nits/draft-ietf-quic-http.html +++ b/http/bk_nits/draft-ietf-quic-http.html @@ -28,7 +28,7 @@ lxml 4.5.0 pycountry 19.8.18 pyflakes 2.1.1 - PyYAML 5.3.1 + PyYAML 5.4.1 requests 2.22.0 setuptools 45.2.0 six 1.14.0 @@ -44,7 +44,23 @@ --link-color: #2a6496; --highlight-color: #f9f9f9; --line-color: #eee; + --pilcrow-weak: #ddd; + --pilcrow-strong: #bbb; --small-font-size: 14.5px; + scrollbar-color: #bbb #eee; +} +@media (prefers-color-scheme: dark) { +html { + --background-color: #121212; + --text-color: #f0f0f0; + --title-color: #fff; + --link-color: #4da4f0; + --highlight-color: #282828; + --line-color: #444; + --pilcrow-weak: #444; + --pilcrow-strong: #666; + scrollbar-color: #777 #333; +} } body { max-width: 600px; @@ -335,14 +351,14 @@ opacity: 0.2; user-select: none; } -a.pilcrow[href] { color: #ddd; } +a.pilcrow[href] { color: var(--pilcrow-weak); } a.pilcrow[href]:hover { text-decoration: none; } -@media screen { +@media not print { :hover > a.pilcrow { opacity: 1; } a.pilcrow[href]:hover { - color: #bbb; + color: var(--pilcrow-strong); background-color: transparent; } } @@ -828,7 +844,7 @@
In HTTP/2, only request and response bodies (DATA frames) are subject to flow -control. All HTTP/3 frames are sent on QUIC streams, so all frames on all -streams are flow-controlled in HTTP/3.¶
+In HTTP/2, only request and response bodies (the frame payload of DATA frames) +are subject to flow control. All HTTP/3 frames are sent on QUIC streams, so all +frames on all streams are flow-controlled in HTTP/3.¶
Due to the presence of other unidirectional stream types, HTTP/3 does not rely
exclusively on the number of concurrent unidirectional streams to control the
number of concurrent in-flight pushes. Instead, HTTP/3 clients use the
diff --git a/http/bk_nits/draft-ietf-quic-http.txt b/http/bk_nits/draft-ietf-quic-http.txt
index 1ee93d8815..9b383c7404 100644
--- a/http/bk_nits/draft-ietf-quic-http.txt
+++ b/http/bk_nits/draft-ietf-quic-http.txt
@@ -4,8 +4,8 @@
QUIC M. Bishop, Ed.
Internet-Draft Akamai
-Intended status: Standards Track 22 January 2021
-Expires: 26 July 2021
+Intended status: Standards Track 26 January 2021
+Expires: 30 July 2021
Hypertext Transfer Protocol Version 3 (HTTP/3)
@@ -51,7 +51,7 @@ Status of This Memo
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 26 July 2021.
+ This Internet-Draft will expire on 30 July 2021.
Copyright Notice
@@ -2128,8 +2128,9 @@ Table of Contents
also maintain some resources for a TCP connection beyond the closing
of the stream that carries the CONNECT request, since the outgoing
TCP connection remains in the TIME_WAIT state. Therefore, a proxy
- might delay increasing the QUIC stream limits to account for the
- resources consumed by CONNECT requests.
+ that supports CONNECT might be more conservative in the number of
+ simultaneous requests it accepts or might delay increasing the QUIC
+ stream limits after a TCP connection terminates.
10.6. Use of Compression
@@ -2555,13 +2556,13 @@ Table of Contents
[QPACK] Krasic, C., Bishop, M., and A. Frindell, Ed., "QPACK:
Header Compression for HTTP over QUIC", Work in Progress,
- Internet-Draft, draft-ietf-quic-qpack, 22 January 2021,
+ Internet-Draft, draft-ietf-quic-qpack, 26 January 2021,
@@ -838,12 +854,12 @@
Thomson
-Expires 26 July 2021
+Expires 30 July 2021
[Page]
▲
Table of Contents
-
-
+
@@ -1327,11 +1343,11 @@
@@ -841,12 +857,12 @@
Krasic, et al.
-Expires 26 July 2021
+Expires 30 July 2021
[Page]