Skip to content

Commit

Permalink
clarify that neither Reliable Size nor error code is a reliable signal (
Browse files Browse the repository at this point in the history
#34)

* clarify that neither Reliable Size nor error code is a reliable signal

* Update draft-ietf-quic-reliable-stream-reset.md

* Update draft-ietf-quic-reliable-stream-reset.md

* simplify, avoiding RFC 2219 verbs

* Update draft-ietf-quic-reliable-stream-reset.md

* Update draft-ietf-quic-reliable-stream-reset.md

Co-authored-by: Marten Seemann <[email protected]>

* Update draft-ietf-quic-reliable-stream-reset.md

Co-authored-by: Kazuho Oku <[email protected]>

* Update draft-ietf-quic-reliable-stream-reset.md

---------

Co-authored-by: Marten Seemann <[email protected]>
kazuho and marten-seemann authored Oct 17, 2023

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
1 parent 7d14034 commit a8011a7
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions draft-ietf-quic-reliable-stream-reset.md
Original file line number Diff line number Diff line change
@@ -152,8 +152,11 @@ up to that byte offset are lost, the initiator MUST retransmit this data, as
described in ({{Section 13.3 of RFC9000}}). Data sent beyond that byte offset
SHOULD NOT be retransmitted.

As described in {{Section 3.2 of RFC9000}}, it MAY deliver data beyond that
offset to the application.
As described in {{Section 3.2 of RFC9000}}, a stream reset signal might be
suppressed or withheld, and the same applies to a stream reset signal carried in
a RESET_STREAM_AT frame. Similary, the Reliable Size of the RESET_STREAM_AT
frame does not prevent a QUIC stack from delivering data beyond the
specified offset to the receiving application.

## Multiple RESET_STREAM_AT / RESET_STREAM frames {#multiple-frames}

0 comments on commit a8011a7

Please sign in to comment.