Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RFC Editor Copyedits #4956

Merged
merged 7 commits into from
Feb 16, 2022
Merged

RFC Editor Copyedits #4956

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
a2a90a8
Most of the RFC Editor edits
MikeBishop Feb 15, 2022
ebcd587
Missed a few
MikeBishop Feb 15, 2022
65f2b27
HTTP/3 is RFC9114
MikeBishop Feb 15, 2022
8309388
Follow RFC 7301; revert change at line 305
MikeBishop Feb 15, 2022
b7f8355
Between/between => of
MikeBishop Feb 16, 2022
4f43349
Combined internal references; fixes #4955
MikeBishop Feb 16, 2022
0efcdce
Use << for section name references
MikeBishop Feb 16, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions rfc9114.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -942,10 +942,10 @@ processed.
The information in the GOAWAY frame enables a client and server to agree on
which requests or pushes were accepted prior to the shutdown of the HTTP/3
connection. Upon sending a GOAWAY frame, the endpoint SHOULD explicitly cancel
(see {{request-cancellation}} and {{frame-cancel-push}}) any requests or pushes
that have identifiers greater than or equal to the one indicated, in order to
clean up transport state for the affected streams. The endpoint SHOULD continue
to do so as more requests or pushes arrive.
(see Sections {{<request-cancellation}} and {{<frame-cancel-push}}) any requests
or pushes that have identifiers greater than or equal to the one indicated, in
order to clean up transport state for the affected streams. The endpoint SHOULD
continue to do so as more requests or pushes arrive.

Endpoints MUST NOT initiate new requests or promise new pushes on the connection
after receipt of a GOAWAY frame from the peer. Clients MAY establish a new
Expand Down Expand Up @@ -1954,11 +1954,11 @@ content includes both attacker-controlled plaintext and secret data (e.g.,
Where HTTP/2 employs PADDING frames and Padding fields in other frames to make a
connection more resistant to traffic analysis, HTTP/3 can either rely on
transport-layer padding or employ the reserved frame and stream types discussed
in {{frame-reserved}} and {{stream-grease}}. These methods of padding produce
different results in terms of the granularity of padding, how padding is
arranged in relation to the information that is being protected, whether padding
is applied in the case of packet loss, and how an implementation might control
padding.
in Sections {{<frame-reserved}} and {{<stream-grease}}. These methods of
padding produce different results in terms of the granularity of padding, how
padding is arranged in relation to the information that is being protected,
whether padding is applied in the case of packet loss, and how an implementation
might control padding.

Reserved stream types can be used to give the appearance of sending traffic even
when the connection is idle. Because HTTP traffic often occurs in bursts,
Expand Down