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.

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

Section 4.2 (comment 13) #537

Open
LPardue opened this issue Sep 13, 2022 · 3 comments
Open

Section 4.2 (comment 13) #537

LPardue opened this issue Sep 13, 2022 · 3 comments

Comments

@LPardue
Copy link
Member

LPardue commented Sep 13, 2022

Section 4.2: We suggest rephrasing this sentence for easier comprehension. Does the suggested text change the meaning of the original sentence?

Original:

   The recommendation is therefore that, even when lower state timeouts
   are used for other UDP traffic, a state timeout of at least two
   minutes ought to be used for QUIC traffic.

Perhaps:
Therefore, it is recommended that a state timeout of at least two
minutes be used for QUIC traffic even when lower state timeouts are
used for other UDP traffic.

@mirjak
Copy link
Contributor

mirjak commented Sep 19, 2022

I guess give this is a recommendation anyway there is no real difference in saying "recommended ... to be used" or "recommended .. ought to be used"?

@britram
Copy link
Contributor

britram commented Sep 20, 2022

NEW:

Therefore, a state timeout of at least two minutes is recommended for QUIC traffic, even when lower state timeouts are used for other UDP traffic

@mirjak
Copy link
Contributor

mirjak commented Sep 21, 2022

Even better!

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

No branches or pull requests

3 participants