[quicwg/base-drafts] nothing can be sent when receiving a packet just after the idle close timer expires (#2347)
Kazuho Oku <notifications@github.com> Fri, 18 January 2019 07:38 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A645131151 for <quic-issues@ietfa.amsl.com>; Thu, 17 Jan 2019 23:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.935
X-Spam-Level:
X-Spam-Status: No, score=-10.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id es1bAPPXnDgP for <quic-issues@ietfa.amsl.com>; Thu, 17 Jan 2019 23:38:53 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85F91131152 for <quic-issues@ietf.org>; Thu, 17 Jan 2019 23:38:53 -0800 (PST)
Date: Thu, 17 Jan 2019 23:38:52 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1547797132; bh=Gzmwku08e/yJNOIO7tZIvHPDsa/oQ1dMduv3bJwMjZE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=nD9fAKXxKJOqYjN15TxWwDJHWYuf8eGGI8j8C/iTH5wfj//BgA21XzjmjwZlec9jC RyrUT9xe90japcScbgfEUzt5fWBcl45Q4Q/zv2gDPZeoVvKXspdeEfFr8W7zPz8Zk+ y98LuH+AaaUdmf4kq2JXCZkcsxgprODq/QDDy8FQ=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab87b713cc8df648f4779757cdfe7d019f0912384692cf000000011859448c92a169ce17e0c497@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2347@github.com>
Subject: [quicwg/base-drafts] nothing can be sent when receiving a packet just after the idle close timer expires (#2347)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c41828ca1839_4ecf3fdabd6d45c0139732"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/8C2-AJvnRhfpBfbZ-KdkOAeNg-M>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2019 07:38:56 -0000
IIUC, the primary reason of having STATELESS_RESET is to let the client notice that the connection is dead immediately, so that it can retransmit the request using a new connection. However, when a server receives a request immediately after it's idle close timer has expired, it cannot send any packet in response, because it is in the draining period. Is this the expected behavior? IMO, we should always allow a server to respond whenever it receives a packet after the idle timeout has expired. One way of allowing that is to let an endpoint immediately discard the connection state when the idle close timer expires. -- 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/2347
- [quicwg/base-drafts] nothing can be sent when rec… Kazuho Oku
- Re: [quicwg/base-drafts] nothing can be sent when… Martin Thomson
- Re: [quicwg/base-drafts] nothing can be sent when… Christian Huitema
- Re: [quicwg/base-drafts] nothing can be sent when… Martin Thomson
- Re: [quicwg/base-drafts] nothing can be sent when… Martin Thomson
- Re: [quicwg/base-drafts] nothing can be sent when… Jana Iyengar