quicwg/quic-v2

Issues

• How does the client learn the negotiated version?

  #78 opened 2 years ago by DavidSchinazi
  4

• How should endpoints react to differences between long header version and chosen version

  #76 opened 2 years ago by DavidSchinazi
  5

• AD review : Interaction with 0-RTT packets

  #73 opened 2 years ago by zaheduzzaman
  5

• AD reveiw : Minor editorial comments

  #72 opened 2 years ago by zaheduzzaman
  1

• Is the version number going to stay?

  #62 opened 3 years ago by DavidSchinazi
  1

• Duplicate text

  #65 opened 3 years ago by DavidSchinazi
  2

• Editorial: cleanup references

  #66 opened 3 years ago by DavidSchinazi
  2

• Why is the original version not authenticated?

  #64 opened 3 years ago by DavidSchinazi
  3

• Will abstract notes be kept or removed after publication?

  #59 opened 3 years ago by DavidSchinazi
  1

• Editorial: I-D.ietf-dprive-dnsoquic is now RFC9250

  #67 opened 3 years ago by rmarx
  1

• Consistency between "QUIC version N" and "QUICvN"

  #53 opened 3 years ago by LPardue
  1

• Use [QUIC-INVARIANTS] instead of [RFC-8999]

  #54 opened 3 years ago by LPardue
  1

• Section 6

  #52 opened 3 years ago by LPardue
  1

• Do you need to mention version aliasing explicitly in the intro?

  #49 opened 3 years ago by LPardue
  0

• Changes vs diferences

  #50 opened 3 years ago by LPardue
  0

• Section 3.2 packet type differences grokkability

  #51 opened 3 years ago by LPardue
  0

• "keys derived from a universally known salt"

  #48 opened 3 years ago by LPardue
  0

• NEW-TOKEN tokens?

  #39 opened 3 years ago by martinduke
  1

• Require use of version-info TP

  #42 opened 3 years ago by martinduke
  0

• DoQ

  #44 opened 3 years ago by martinduke
  0

• Consider adding an optional field in QUIC-v2 header?

  #40 opened 3 years ago by Neo-ZK
  1

• QUICv2 should not allow TLS resumption with QUICv1 tickets

  #31 opened 3 years ago by DavidSchinazi
  8

• Encourage Compatible VN

  #35 opened 3 years ago by martinduke
  0

• Test vectors

  #17 opened 3 years ago by martinthomson
  2

• HTTP/3 over QUICv2

  #30 opened 3 years ago by DavidSchinazi
  8

• Retry and compatible upgrade

  #23 opened 3 years ago by martinthomson
  3

• MUST fully support VN is too strong

  #25 opened 3 years ago by DavidSchinazi
  6

• Grease the packet type?

  #7 opened 3 years ago by martinduke
  1

• Request provisional version number allocation

  #20 opened 3 years ago by martinduke
  2

• Don't Change Labels

  #9 opened 3 years ago by nibanks
  6

• Packet injection during Compatible VN

  #21 opened 3 years ago by martinduke
  2

• Need to specify the update process

  #15 opened 3 years ago by huitema
  7

• Clarify about cross version 0-RTT via Compatible Version Negotiation

  #14 opened 3 years ago by flano-yuki
  2

• Applicability of extensions

  #10 opened 3 years ago by martinduke
  0

• ALPN

  #5 opened 4 years ago by martinduke
  7

• Different version number

  #4 opened 4 years ago by martinduke
  2

• Update Labels

  #3 opened 4 years ago by martinduke
  1

• Retry protection key

  #2 opened 4 years ago by huitema
  0

• Add a provisional version

  #1 opened 4 years ago by martinduke
  1