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

Non-reusable number space #4287

Closed
larseggert opened this issue Oct 28, 2020 · 2 comments
Closed

Non-reusable number space #4287

larseggert opened this issue Oct 28, 2020 · 2 comments
Labels
-transport ietf-lc An issue that was raised during IETF Last Call.

Comments

@larseggert
Copy link
Member

12.3. Packet Numbers

The packet number is an integer in the range 0 to 2^62-1.

It would save a bit of wondering until later if this was described as a
non-reusable number space

@larseggert larseggert added -transport ietf-lc An issue that was raised during IETF Last Call. labels Oct 28, 2020
@larseggert larseggert added this to the transport-genart milestone Oct 28, 2020
@martinthomson
Copy link
Member

I think that this text is sufficient:

A QUIC endpoint MUST NOT reuse a packet number within the same packet number space in one connection.

It's not at the top of that section, but it isn't the most important thing to know either.

@martinthomson martinthomson added the proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. label Nov 5, 2020
@LPardue
Copy link
Member

LPardue commented Dec 8, 2020

The proposed resolution was to close to with action, which was signalled to the appropriate review channel.

Hearing no pushback, I'm closing this.

@LPardue LPardue closed this as completed Dec 8, 2020
@LPardue LPardue removed the proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. label Dec 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport ietf-lc An issue that was raised during IETF Last Call.
Projects
None yet
Development

No branches or pull requests

3 participants