[quicwg/base-drafts] Why would late-arriving packets create state? (#2148)

ekr <notifications@github.com> Thu, 13 December 2018 19:29 UTC

Date: Thu, 13 Dec 2018 11:29:51 -0800
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5ecd3c1424d43535e2bc0924ce8178b062bd033d92cf00000001182a752f92a169ce174b868c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2148@github.com>
Subject: [quicwg/base-drafts] Why would late-arriving packets create state? (#2148)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12b32f8abcb_58283f7e066d45c0649ae"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/sjjD3ZBRgV6m0UTM4EhobsOuRME>

```
Disposing of connection state prior to the end of the closing or draining period
could cause delayed or reordered packets to be handled poorly.  Endpoints that
have some alternative means to ensure that late-arriving packets on the
connection do not create QUIC state, such as those that are able to close the
UDP socket, MAY use an abbreviated draining period which can allow for faster
resource recovery.  Servers that retain an open socket for accepting new
connections SHOULD NOT exit the closing or draining period early.
```

I'm not following why in general this *would* create state. If the
handshake has occurred > MSL ago, and you just refuse to create state
on short packets with unknown CIDs s, why isn't that enough?



-- 
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/issues/2148

[quicwg/base-drafts] Why would late-arriving pack… ekr
Re: [quicwg/base-drafts] Why would late-arriving … Martin Thomson
Re: [quicwg/base-drafts] Why would late-arriving … Martin Thomson