quicwg/version-negotiation issues and pull requests

#135 - Change a that which should be which

Pull Request - State: closed - Opened by ekr over 1 year ago

#134 - Ekr editorial auth48

Pull Request - State: closed - Opened by ekr almost 2 years ago

#133 - AUTH48 changes

Pull Request - State: closed - Opened by DavidSchinazi almost 2 years ago

#132 - Final IANA values

Pull Request - State: closed - Opened by DavidSchinazi about 2 years ago

#131 - Mandate validation of Version Information

Pull Request - State: closed - Opened by DavidSchinazi over 2 years ago - 1 comment

#130 - Attempt to clarify the examples

Pull Request - State: closed - Opened by ekr over 2 years ago

#129 - Should fail the handshake when version_info.chosen_version doesn't match long_header.version

Issue - State: closed - Opened by anrossi over 2 years ago - 9 comments

#128 - Only clients can start incompatible VN

Pull Request - State: closed - Opened by DavidSchinazi over 2 years ago

#127 - Explain what a downgrade is

Pull Request - State: closed - Opened by DavidSchinazi over 2 years ago

#126 - Specify how this document updates RFC 8999

Pull Request - State: closed - Opened by huitema over 2 years ago - 1 comment

#125 - Update discipline: tell readers what you update

Issue - State: closed - Opened by huitema over 2 years ago - 2 comments

#124 - Updates RFC 8999

Pull Request - State: closed - Opened by DavidSchinazi over 2 years ago - 4 comments

#123 - Make incompatible VN more normative

Pull Request - State: closed - Opened by DavidSchinazi over 2 years ago

#122 - Clarify validations on converted first flight

Pull Request - State: closed - Opened by DavidSchinazi over 2 years ago - 1 comment

#121 - Add reference for normative text

Pull Request - State: closed - Opened by DavidSchinazi over 2 years ago

#120 - fix original version

Pull Request - State: closed - Opened by DavidSchinazi over 2 years ago

#119 - AD review : When does the negotiation end?

Issue - State: closed - Opened by zaheduzzaman over 2 years ago - 8 comments

#118 - AD review : unclear reference to "first flight"

Issue - State: closed - Opened by zaheduzzaman over 2 years ago - 10 comments

#117 - AD review: lack of normative language

Issue - State: closed - Opened by zaheduzzaman over 2 years ago - 4 comments

#116 - AD Review : some minor editorial comments

Issue - State: closed - Opened by zaheduzzaman over 2 years ago - 3 comments

#115 - AD Review : Should this specification add a update tag?

Issue - State: closed - Opened by zaheduzzaman over 2 years ago - 10 comments

#114 - The scenario of Figure 1

Issue - State: closed - Opened by kazu-yamamoto over 2 years ago - 4 comments

#113 - nits: spellcheck

Pull Request - State: closed - Opened by LPardue over 2 years ago

#112 - INV -> INVARIANTS

Pull Request - State: closed - Opened by LPardue over 2 years ago

#111 - [INV] -> [QUIC-INVARIANTS]

Issue - State: closed - Opened by LPardue over 2 years ago
Labels: editorial

#110 - VN/v2 shepherd writeup

Pull Request - State: closed - Opened by mjoras over 2 years ago

#109 - Leave how to determine versions up to versions

Pull Request - State: closed - Opened by ekr over 2 years ago

#108 - Clarify when long header version can mismatch

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago

#107 - Refactor to create Definitions section

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago - 1 comment

#106 - Editorial clarification on advertising newer versions

Pull Request - State: closed - Opened by mirjak almost 3 years ago

#105 - Tweak diagram

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago

#104 - Clarify compatible

Pull Request - State: closed - Opened by ekr almost 3 years ago

#103 - Clarify client choice

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago

#102 - Implementaion leeway for 2 connections

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago

#101 - Clarify directionality

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago - 1 comment

#100 - Add ALPN Considerations

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago

#99 - Editorial PR for MT issue 98

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago

#98 - Not a PR because it's late

Issue - State: closed - Opened by martinthomson almost 3 years ago - 2 comments

#97 - Don't restate requirements

Issue - State: closed - Opened by martinthomson almost 3 years ago - 1 comment

#96 - Choosing the original version

Issue - State: closed - Opened by martinthomson almost 3 years ago - 1 comment
Labels: editorial

#95 - Is incompatible VN one or two connections?

Issue - State: closed - Opened by martinthomson almost 3 years ago

#94 - Original version in compatible negotiation

Issue - State: closed - Opened by martinthomson almost 3 years ago - 1 comment

#93 - Compatible Versions Section editorial

Issue - State: closed - Opened by martinthomson almost 3 years ago
Labels: editorial

#92 - Recommendations for ALPN

Issue - State: closed - Opened by martinthomson almost 3 years ago - 1 comment

#91 - Note that when you do incompatible VN you need to reset ALPN, etc.

Issue - State: closed - Opened by ekr almost 3 years ago - 1 comment

#90 - What does "compatible" VN mean

Issue - State: closed - Opened by ekr almost 3 years ago - 1 comment

#89 - Reorder sections

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago

#88 - Tweak QUICv1 compatibility requirements

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago

#87 - Clarify negotiated version

Pull Request - State: closed - Opened by DavidSchinazi almost 3 years ago

#86 - handle TP with version = 0

Pull Request - State: closed - Opened by martinduke almost 3 years ago

#85 - clarify handling of multiple ALPNs

Pull Request - State: closed - Opened by martinduke almost 3 years ago - 1 comment

#84 - Consider 0RTT in definition of compatible.

Pull Request - State: closed - Opened by martinduke almost 3 years ago - 2 comments

#84 - Consider 0RTT in definition of compatible.

Pull Request - State: closed - Opened by martinduke almost 3 years ago - 2 comments

#83 - min support, but much much shorter

Pull Request - State: closed - Opened by martinduke almost 3 years ago

#83 - min support, but much much shorter

Pull Request - State: closed - Opened by martinduke almost 3 years ago

#82 - Clarify minimum levels of compliance

Pull Request - State: closed - Opened by martinduke almost 3 years ago - 2 comments

#81 - Don't assume a single protocol

Issue - State: closed - Opened by MikeBishop almost 3 years ago - 1 comment

#80 - Differing levels of support for the standard

Issue - State: closed - Opened by martinduke about 3 years ago

#79 - What is the negotiated version during the handshake?

Issue - State: closed - Opened by DavidSchinazi about 3 years ago - 3 comments

#78 - Refactor Retry and 0-RTT sections into a new "Considerations for compatibility with QUICv1" section

Issue - State: closed - Opened by DavidSchinazi about 3 years ago

#77 - Fix definition of "compatible"

Issue - State: closed - Opened by ghost about 3 years ago - 3 comments

#76 - A value of 0 in the transport parameter

Issue - State: closed - Opened by martinthomson about 3 years ago - 7 comments

#75 - Clarify that VN validation fails if server other versions are empty

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#74 - Current version in version info breaks transport parameters design patterns

Issue - State: closed - Opened by huitema about 3 years ago - 8 comments

#73 - Validation on incompatible negotiation

Issue - State: closed - Opened by kazu-yamamoto about 3 years ago - 12 comments

#72 - validating Version Information on compatible negotiation

Issue - State: closed - Opened by kazu-yamamoto about 3 years ago - 7 comments

#71 - Clarify other versions empty

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#70 - Security issue when upgrading based on received version in header

Issue - State: closed - Opened by huitema about 3 years ago - 10 comments

#69 - How can the server chosen version field be empty?

Issue - State: closed - Opened by huitema about 3 years ago - 3 comments

#68 - Specify impact on 0-RTT, session resume tickets, etc.

Issue - State: closed - Opened by huitema about 3 years ago - 20 comments

#67 - Specify impact on encryption keys

Issue - State: closed - Opened by huitema about 3 years ago - 7 comments

#67 - Specify impact on encryption keys

Issue - State: closed - Opened by huitema about 3 years ago - 7 comments

#66 - Special case QUIC version 1

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago - 28 comments

#65 - adding example scenarios

Pull Request - State: closed - Opened by kazu-yamamoto about 3 years ago - 1 comment

#64 - Soften requirement on address stability

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#63 - Clarify that Version Information is invariant but its encoding is not

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#62 - Remove outdated text about self-describing frames

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#61 - Clarify that clients only list useful compatible versions

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#60 - Conversion cannot fail

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#59 - Error signaling is a requirement on all QUIC versions

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#58 - Version Negotiation terminates a connection attempt

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#57 - No anthropomorphism

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#56 - Remove backticks

Pull Request - State: closed - Opened by DavidSchinazi about 3 years ago

#55 - Backward compatibility with the version negotiation of RFC 9000

Issue - State: closed - Opened by kazu-yamamoto about 3 years ago - 15 comments

#54 - Clarify that we will switch to permanent smaller codepoints

Pull Request - State: closed - Opened by DavidSchinazi over 3 years ago

#53 - Small transport parameter codepoint

Issue - State: closed - Opened by martinthomson over 3 years ago - 1 comment

#52 - Edits to Retry text

Pull Request - State: closed - Opened by martinthomson over 3 years ago

#51 - Don't choose the oldest

Pull Request - State: closed - Opened by martinthomson over 3 years ago

#50 - Tweak the intro

Pull Request - State: closed - Opened by martinthomson over 3 years ago

#49 - Client validation

Pull Request - State: closed - Opened by martinthomson over 3 years ago

#48 - Remove redundant attribute

Pull Request - State: closed - Opened by martinthomson over 3 years ago

#47 - Consider reordering sections

Issue - State: closed - Opened by martinthomson over 3 years ago
Labels: editorial

#46 - Allow interop with non-supporting endpoints

Pull Request - State: closed - Opened by DavidSchinazi over 3 years ago

#45 - Anthropomorphism

Issue - State: closed - Opened by MikeBishop almost 4 years ago - 2 comments
Labels: editorial

#44 - Remove backticks for fields

Issue - State: closed - Opened by DavidSchinazi almost 4 years ago
Labels: editorial

#43 - Should the client communicate version preference ordering?

Issue - State: closed - Opened by DavidSchinazi almost 4 years ago - 5 comments

#42 - Incorporate MT's design

Pull Request - State: closed - Opened by DavidSchinazi almost 4 years ago

#41 - Do applications define compatible versions?

Issue - State: closed - Opened by martinduke almost 4 years ago - 6 comments
Labels: has-pr

#40 - Incompatible VN and unaware server

Issue - State: closed - Opened by huitema almost 4 years ago

#39 - Packet loss during version negotiation

Issue - State: closed - Opened by huitema almost 4 years ago - 3 comments

GitHub / quicwg/version-negotiation issues and pull requests