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

Decouple QUIC version and ALPN #12

Closed
martinthomson opened this issue Nov 23, 2016 · 2 comments
Closed

Decouple QUIC version and ALPN #12

martinthomson opened this issue Nov 23, 2016 · 2 comments
Labels
-tls 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.

Comments

@martinthomson
Copy link
Member

As per discussion at the meeting. This will allow QUIC to evolve ahead of any updates to its higher layers.
@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. -tls labels Nov 23, 2016
@MikeBishop MikeBishop added the proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. label Jan 12, 2017
@MikeBishop
Copy link
Contributor

This is decoupled per the changes in #122 (which are mired in a separate discussion). Whether #122 gets merged before -01 snaps or not, let's confirm that this issue is resolved acceptably at the interim.

In -00, the text was this:

The ALPN identifier for the protocol MUST be specific to the QUIC version that it operates over.

The text in #122 currently says:

The application-layer protocol MAY restrict the QUIC versions that it can operate over. Servers MUST select an application protocol compatible with the QUIC version that the client has selected.

@mnot
Copy link
Member

mnot commented Jan 25, 2017

Discussed in Tokyo; same as #97, now a dup.

@mnot mnot closed this as completed Jan 25, 2017
@mnot mnot removed the proposal-ready An issue which has a proposal that is believed to be ready for a consensus call. label Jan 25, 2017
@mnot mnot added the has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. label Apr 19, 2017
siyengar pushed a commit to siyengar/base-drafts that referenced this issue May 17, 2018
@ekr
Merge pull request quicwg#12 from ekr/crypto_hs_frame
39d3951 
Rename CRYPTO to CRYPTO_HS
martinthomson pushed a commit that referenced this issue Jul 8, 2019
@huitema
Merge pull request #12 from quicwg/master
3a11ef0 
Align with master 2019/06/04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-tls 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
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@martinthomson @mnot @MikeBishop