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

Discuss greasing as an addition to an existing protocol, versus being part of it from the start #11

Open
tfpauly opened this issue Aug 4, 2021 · 2 comments
Open

Discuss greasing as an addition to an existing protocol, versus being part of it from the start #11

tfpauly opened this issue Aug 4, 2021 · 2 comments
Labels
deployability Implementations, interoperability, and experiments evolvability Protocol extensibility and greasing

Comments

@tfpauly
Copy link
Member

tfpauly commented Aug 4, 2021

We may want to consider the distinction between trying to add greasing to an existing protocol (TLS, HTTP) versus adding it from the start (QUIC).

Let's track this experiment.
@tfpauly
Copy link
Member Author

tfpauly commented Aug 4, 2021

See intarchboard/draft-use-it-or-lose-it#32

@tfpauly
Copy link
Member Author

tfpauly commented Aug 4, 2021

QUIC greasing during development found bugs before things shipped, so it's a useful example of how this can be part of the development process. Start this on early drafts, not late.

@tfpauly tfpauly added deployability Implementations, interoperability, and experiments evolvability Protocol extensibility and greasing labels Oct 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
deployability Implementations, interoperability, and experiments evolvability Protocol extensibility and greasing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tfpauly