[quicwg/base-drafts] fa9f2a: Reorder TLS interface summary

Martin Thomson <noreply@github.com> Mon, 06 July 2020 02:06 UTC

Date: Sun, 05 Jul 2020 19:06:36 -0700
From: Martin Thomson <noreply@github.com>
To: quic-issues@ietf.org
Message-ID: <quicwg/base-drafts/push/refs/heads/interface-summary-order/000000-fa9f2a@github.com>
Subject: [quicwg/base-drafts] fa9f2a: Reorder TLS interface summary
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/rF8QF2e7gH2FxMiqaGFBgqRaHrM>
Precedence: list

  Branch: refs/heads/interface-summary-order
  Home:   https://github.com/quicwg/base-drafts
  Commit: fa9f2afff3dca923287bc8429e6066bd93980890
      https://github.com/quicwg/base-drafts/commit/fa9f2afff3dca923287bc8429e6066bd93980890
  Author: Martin Thomson <mt@lowentropy.net>
  Date:   2020-07-06 (Mon, 06 Jul 2020)

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

  Log Message:
  -----------
  Reorder TLS interface summary

I came back to this today and found that the ordering was inconsistent
and not sufficiently clear.

Changing this so that all the actions for a single endpoint were grouped
seemed to be the best arrangement.  All events and actions are as close
as possible in the ordering to the preceding event that caused or
enabled it.

The application data packets are displayed with a different marking,
which helps distinguish those that carry CRYPTO frames.

The final implied exchange for Get Handshake was removed.  This was, I
think, intended to imply something about session tickets.  Without
explanation, it is confusing.

This doesn't show HANDSHAKE_DONE, nor do I think that it should, because
that is something that the transport does once it gets the Handshake
Complete signal.

[quicwg/base-drafts] fa9f2a: Reorder TLS interfac… Martin Thomson