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.

Sign up for GitHub

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

Jump to bottom

transport: error handling if the number of frames is zero #4361

Closed
kazu-yamamoto opened this issue Nov 17, 2020 · 0 comments · Fixed by #4391
Closed

transport: error handling if the number of frames is zero #4361

kazu-yamamoto opened this issue Nov 17, 2020 · 0 comments · Fixed by #4391
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus. ietf-lc An issue that was raised during IETF Last Call.
Projects
Late Stage Processing

Comments

@kazu-yamamoto
Copy link
Contributor

Sec 12.4 says:

The payload of a packet that contains frames MUST contain at least one frame, and MAY contain multiple frames and multiple frame types.

There is no specification of error handling in the case of zero frame. I would like to know what kind of error MUST be sent.

Also, the packet formats contains the following field:

Packet Payload (..)

Should we change this to the following?

Packet Payload (8..)
@larseggert larseggert added -transport ietf-lc An issue that was raised during IETF Last Call. labels Nov 17, 2020
@larseggert larseggert added this to Triage in Late Stage Processing via automation Nov 17, 2020
@martinthomson martinthomson added the editorial An issue that does not affect the design of the protocol; does not require consensus. label Nov 18, 2020
@project-bot project-bot bot moved this from Triage to Editorial Issues in Late Stage Processing Nov 18, 2020
martinthomson added a commit that referenced this issue Nov 18, 2020
@martinthomson
Packets can't be zero-length
6e3a65e 
Closes #4361.
@martinthomson martinthomson mentioned this issue Nov 18, 2020
Merged
Late Stage Processing automation moved this from Editorial Issues to Issue Handled Nov 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus. ietf-lc An issue that was raised during IETF Last Call.
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Packets can't be zero-length quicwg/base-drafts
3 participants
@martinthomson @kazu-yamamoto @larseggert