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

Early Data isn't explained #2856

Closed
MikeBishop opened this issue Jun 27, 2019 · 0 comments · Fixed by #3225
Closed

Early Data isn't explained #2856

MikeBishop opened this issue Jun 27, 2019 · 0 comments · Fixed by #3225
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing

Comments

@MikeBishop
Copy link
Contributor

There's a lot of text in the transport draft that assumes you know what 0-RTT / early data are. The term "early data" occurs only once, and doesn't even appear until describing the 0-RTT packet type. The introductory sections should probably contain some high-level description of Early Data, then point off to TLS for more detailed considerations.

Purely editorial -- nothing new needs to be specified, but an uninitiated reader will need some context. This could possibly be part of #2843.
@MikeBishop MikeBishop added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels Jun 27, 2019
@mnot mnot added this to Editorial Issues in Late Stage Processing Jul 1, 2019
martinthomson added a commit that referenced this issue Nov 12, 2019
@martinthomson
A day in the life
7a1bfb7 
...and now we know how many holes it takes to fill the Albert Hall.

This section has existed for a long time as "TBD".  No longer.  It also
takes the opportunity to explain a little bit about what 0-RTT is for.

Closes #2856.
Closes #2843.
@martinthomson martinthomson mentioned this issue Nov 12, 2019
Merged
Late Stage Processing automation moved this from Editorial Issues to Text Incorporated Dec 3, 2019
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.
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

A day in the life quicwg/base-drafts
1 participant
@MikeBishop