Subject: [quicwg/base-drafts] 6de5e8: Force the server and client to remember transport ...

From: Martin Thomson <[email-masked]>
Date: Sun, 21 May 2017 17:19:05 -0700

Branch: refs/heads/master
  Home:   https://github.com/quicwg/base-drafts
  Commit: 6de5e8cda18bb448e880a5d48b3772ae07a671de
      https://github.com/quicwg/base-drafts/commit/6de5e8cda18bb448e880a5d48b3772ae07a671de
  Author: Martin Thomson <[email-masked]>
  Date:   2017-05-09 (Tue, 09 May 2017)

  Changed paths:
    M draft-ietf-quic-tls.md
    M draft-ietf-quic-transport.md

  Log Message:
  -----------
  Force the server and client to remember transport parameters for 0-RTT

This includes Victor's recommendation to avoid the client violating server
constraints on operation.  This means that the server that accepts 0-RTT is
required to provide new transport parameters that are compatible with its
previously advertised value, or reject 0-RTT.

I made this easier on servers, by allowing them to advertise different
transport parameters that only apply to 0-RTT.  They include these values in
the TLS NewSessionTicket message, alongside the ticket that is used to resume.

  Commit: 2eeef08c4261bf69da7dee9200288187cdc3576d
      https://github.com/quicwg/base-drafts/commit/2eeef08c4261bf69da7dee9200288187cdc3576d
  Author: Martin Thomson <[email-masked]>
  Date:   2017-05-21 (Sun, 21 May 2017)

  Changed paths:
    M draft-ietf-quic-tls.md
    M draft-ietf-quic-transport.md

  Log Message:
  -----------
  Merge pull request #512 from quicwg/0rtt_parameters

Force the server and client to remember transport parameters for 0-RTT

Compare: https://github.com/quicwg/base-drafts/compare/93467b4e45a4...2eeef08c4261