Skip to content
Open
Changes from all commits
Commits
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: 13 additions & 5 deletions draft-ietf-httpbis-incremental.md
Original file line number Diff line number Diff line change
Expand Up @@ -217,8 +217,14 @@ accompanied by a connection_limit_reached Proxy-Status response header field
For performance and efficiency reasons, a small amount of buffering might be
used by intermediaries, even for incremental messages. Immediate forwarding
might be exploited to cause an intermediary to waste effort on many small
packets. Enabling incremental delivery might instead set limits on the number
bytes that are buffered or the time that buffers are held before forwarding.
packets.

Enabling incremental delivery might set limits on the number
bytes that are buffered before forwarding.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
bytes that are buffered before forwarding.
of bytes that are buffered before forwarding.

Error in the existing text, but as long as you're touching the line....

Any intermediary that buffers incoming data
MUST limit the time that buffers are held before forwarding;
an intermediary cannot rely on receiving more bytes to drive progress.

Any buffering could adversely affect application latency, even if it improves
efficiency. In all cases, intermediaries cannot hold data in buffers
indefinitely, so data needs to be forwarded when either the time limit or the
Expand All @@ -228,7 +234,8 @@ byte limit is reached.
# IANA Considerations

An HTTP field named Incremental is registered
in the Hypertext Transfer Protocol (HTTP) Field Name Registry,
in the [Hypertext Transfer Protocol (HTTP) Field Name
Registry](https://www.iana.org/assignments/http-fields/http-fields.xhtml),
following the procedures in {{Section 18.4 of !HTTP=RFC9110}}.
The following values are registered:

Expand All @@ -248,8 +255,9 @@ Comments:
: None
{:compact}

An HTTP Proxy Error Type is registered in the HTTP Proxy Error Types registry as
shown below:
An HTTP Proxy Error Type is registered in the [HTTP Proxy Error Types
Registry](https://www.iana.org/assignments/http-proxy-status/http-proxy-status.xhtml#http-proxy-error-types)
as shown below:

Name:
: incremental_refused
Expand Down