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

Apply GREASE to transport parameters #2550

Closed
mjoras opened this issue Mar 25, 2019 · 5 comments · Fixed by #2873
Closed

Apply GREASE to transport parameters #2550

mjoras opened this issue Mar 25, 2019 · 5 comments · Fixed by #2873
Assignees
@mjoras
Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.
Projects
Late Stage Processing

Comments

@mjoras
Copy link

mjoras commented Mar 25, 2019

We have space for private transport parameters and a process for assigning new standard transport parameters. However, since we do not apply GREASE to transport parameters, we leave ourselves open to that flexibility ossifying.

I'm happy to produce a PR to address this in the spec.
@mnot mnot added this to Triage in Late Stage Processing Mar 27, 2019
@mnot mnot added the design An issue that affects the design of the protocol; resolution requires consensus. label Apr 9, 2019
@mnot mnot moved this from Triage to Design Issues in Late Stage Processing Apr 9, 2019
@DavidSchinazi
Copy link
Contributor

During interop in London we found an implementation that failed the handshake upon seeing an unknown transport parameter. I think applying GREASE to transport parameters is a great idea.

@larseggert
Copy link
Member

Discussed in London, @mjoras to prepare a PR

@mnot
Copy link
Member

mnot commented Jun 14, 2019

@mjoras any progress here?

@loganaden
Copy link
Contributor

loganaden commented Jun 14, 2019 via email

@marten-seemann marten-seemann mentioned this issue Jul 5, 2019
Merged
@mjoras
Copy link
Author

mjoras commented Jul 9, 2019

@mnot sorry I totally dropped the ball here! I had text ages ago and was circling back today finally. Thanks @marten-seemann for seeing to it.

@mnot mnot added the proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. label Jul 9, 2019
@mnot mnot moved this from Design Issues to Consensus Emerging in Late Stage Processing Jul 9, 2019
@mnot mnot moved this from Consensus Emerging to Consensus Call issued in Late Stage Processing Aug 6, 2019
@mnot mnot moved this from Consensus Call issued to Consensus Declared in Late Stage Processing Aug 16, 2019
@mnot mnot added has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. and removed proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. labels Aug 16, 2019
Late Stage Processing automation moved this from Consensus Declared to Text Incorporated Aug 16, 2019
@juliens juliens mentioned this issue Oct 12, 2019
Closed
28 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mjoras mjoras

Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

grease transport parameters marten-seemann/base-drafts
6 participants
@martinthomson @mnot @larseggert @loganaden @DavidSchinazi @mjoras