Skip to content

feat(transport): implement RESET_STREAM_AT frame#3102

Draft
mxinden wants to merge 1 commit intomozilla:mainfrom
mxinden:reset-stream-at
Draft

feat(transport): implement RESET_STREAM_AT frame#3102
mxinden wants to merge 1 commit intomozilla:mainfrom
mxinden:reset-stream-at

Conversation

@mxinden
Copy link
Member

@mxinden mxinden commented Nov 3, 2025

@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2025

Failed Interop Tests

None ❓

All results

Succeeded Interop Tests

None ❓

Unsupported Interop Tests

None ❓

Copy link
Member

@martinthomson martinthomson left a comment

Choose a reason for hiding this comment

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

Following a link, I find this. No substance here yet, but a reasonable start.

Comment on lines +9 to +12
// TODO: When using 0-RTT, both endpoints MUST remember the value of this
// transport parameter. This allows use of this extension in 0-RTT packets. When
// the server accepts 0-RTT data, the server MUST NOT disable this extension on
// the resumed connection.
Copy link
Member

Choose a reason for hiding this comment

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

This is already handled. By "default", our check in ok_for_0rtt() checks if the new connection includes the transport parameter when the old connection did.

GreaseQuicBit = 0x2ab2,
MinAckDelay = 0xff02_de1a,
MaxDatagramFrameSize = 0x0020,
ResetStreamAt = 0x17f7586d2cb571,
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
ResetStreamAt = 0x17f7586d2cb571,
ResetStreamAt = 0x24,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants