Subject: [quicwg/base-drafts] dca4b6: Enter closing after the idle timeout

From: Martin Thomson <[email-masked]>
Date: Fri, 09 Mar 2018 14:33:09 -0800

Branch: refs/heads/master
  Home:   https://github.com/quicwg/base-drafts
  Commit: dca4b6f9f1ed1e47c2836cea447bf3064c159870
      https://github.com/quicwg/base-drafts/commit/dca4b6f9f1ed1e47c2836cea447bf3064c159870
  Author: Martin Thomson <[email-masked]>
  Date:   2018-03-09 (Fri, 09 Mar 2018)

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

  Log Message:
  -----------
  Enter closing after the idle timeout

The draft was a little unclear on this point and its important.  The idle timeout ends without sending CONNECTION_CLOSE, and it can end approximately simultaneously.  If both endpoints send CONNECTION_CLOSE and then go to closing, then they might start a packet storm if neither actually looks at packets they receive before retransmitting their close packet (which is permitted).  We want idle timeout to pass without packets, so this needs to be closing.

Closes #1178

  Commit: d6d104bb2526c35724e80ba206d61646afb3516d
      https://github.com/quicwg/base-drafts/commit/d6d104bb2526c35724e80ba206d61646afb3516d
  Author: Martin Thomson <[email-masked]>
  Date:   2018-03-10 (Sat, 10 Mar 2018)

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

  Log Message:
  -----------
  Merge pull request #1179 from quicwg/idle-expiration

Enter closing after the idle timeout

Compare: https://github.com/quicwg/base-drafts/compare/486abed55eb4...d6d104bb2526