Subject: [quicwg/base-drafts] QUIC-TLS Extension and version negotiation (#99)

From: Mike Bishop <[email-masked]>
Date: Fri, 23 Dec 2016 13:05:26 -0800

Proposal on how to define the TLS extension for QUIC, and thereby fix up some of the version negotiation issues (#89, #97).

Key changes:

- TLS doc *does* define the QUIC extension, but it simply contains an opaque blob transported for whichever QUIC version is being used.
- Parameters encoding is specified, and is more "TLS-y" than the current protocol -- an enum of possible parameters, carried as numbers rather than strings where appropriate, etc.  Plenty of room to add additional parameters, but unrecognized parameters here will be fatal unless we add an explicit length.
- Server's version list is always required in TLS extension, even if no Version Negotiation packet was sent.  Client MAY open a new connection immediately if it discovers the server would have supported a newer version, and SHOULD use the newer version next time.
- Server SHOULD pick an application protocol supported by the client's proposed version; Version Negotiation only if no overlap on the current version.
You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/99

-- Commit Summary --

  * Add definition for ICSL
  * Changes to ALPN and version negotiation for #97
  * Define the QUIC TLS Extension
  * Add version negotiation verification to QUIC-TLS extension

-- File Changes --

    M draft-ietf-quic-tls.md (52)
    M draft-ietf-quic-transport.md (72)

-- Patch Links --

https://github.com/quicwg/base-drafts/pull/99.patch
https://github.com/quicwg/base-drafts/pull/99.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/99