Skip to content

address compliance issues - #690

Closed
sleepybishop wants to merge 1 commit into
h2o:masterfrom
sleepybishop:rfc-compliance
Closed

address compliance issues#690
sleepybishop wants to merge 1 commit into
h2o:masterfrom
sleepybishop:rfc-compliance

Conversation

@sleepybishop

Copy link
Copy Markdown
Contributor

This pr addresses the findings from h2o/h2o#3607.

The picotls related items are deferred until h2o/picotls#617 is merged.

@kazuho

kazuho commented Sep 8, 2026

Copy link
Copy Markdown
Member

Thank you very much for the PR! I'll take a look and merge this.

@kazuho

kazuho commented Sep 8, 2026

Copy link
Copy Markdown
Member

Excuse me, based on my understanding that this PR only to change the two points listed below, I would close without doing anything:

Persistent congestion: it is not required by QUIC. RFC 9002 is merely "exemplary" (Abstract of RFC 9000), and CUBIC relies on QUIC PTO to handle the same case. Therefore, there is little need, if any, to implement it.

Use of unified loss detection rather than per-epoch states. This also is not a conformance issue, since loss detection is specified by RFC 9002. This is an intentional design choice and I do not see a compelling reason to adopt a more complex design.

I will post the same message to the original issue once I finish going through all of them.

@kazuho kazuho closed this Sep 8, 2026
@sleepybishop

Copy link
Copy Markdown
Contributor Author

Fair, thanks for taking a look.

@kazuho

kazuho commented Sep 9, 2026

Copy link
Copy Markdown
Member

Thank you so much for all your contributions. I highly appreciate them.

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