[quicwg/base-drafts] Acknowledging *_CLOSE (#733)
Mike Bishop <notifications@github.com> Tue, 15 August 2017 20:24 UTC
Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 EA94E1323BE for <quic-issues@ietfa.amsl.com>; Tue, 15 Aug 2017 13:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.595
X-Spam-Level:
X-Spam-Status: No, score=-0.595 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 6hx8ZdM5nibv for <quic-issues@ietfa.amsl.com>; Tue, 15 Aug 2017 13:24:56 -0700 (PDT)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C82C132043 for <quic-issues@ietf.org>; Tue, 15 Aug 2017 13:24:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=jPqrnKcGtFV3YocCAimvxUUWKVw=; b=GGbgeRBma4V8UIoT ta50NYVTfSJs/aYsswrLA5U34Rdjuk6PhagGLxbo57Atw2gZ4SX7HLERmw62kiQ8 7dEIu9Opd1RPHkpNs1qeMr6YCYf+IAXsdhsvEu91wZII5yz2ctJn94PgxblRzCr2 QZGdhcpZHcCK4gOt+X5MaRbu21I=
Received: by filter1071p1mdw1.sendgrid.net with SMTP id filter1071p1mdw1-17044-59935896-27 2017-08-15 20:24:54.962042899 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id xMmTbI0VQNaAKuv3E45wKw for <quic-issues@ietf.org>; Tue, 15 Aug 2017 20:24:54.974 +0000 (UTC)
Date: Tue, 15 Aug 2017 20:24:55 +0000
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab32b8713bdc75436fe7063a63b1107e268149dc3592cf0000000115ab1a9692a169ce0eed37cd@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/733@github.com>
Subject: [quicwg/base-drafts] Acknowledging *_CLOSE (#733)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59935896cb997_54a33fb3fedc5c341299be"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0VNyiUXe40BbbkcnbkkoU6nPToHVjAz0fqd4 Yq0f60O1GN1IL6OUzSGb6jm9v0s+2n0RMJ2mXBGmuM70r33WYeMVwaXeubPx9qBcU8oYkRpdfxXBzb IbVkvCoIScZaxjXWVnONnNxHLwdGYUmFPbtdvb+C4Jipk5XMCG9sXJYDe6gKwnw/rEo/SFMBwzaGoe k=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/tnAiYjkxRJYpz3W3Yt3-h__e6Jk>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 15 Aug 2017 20:24:58 -0000
The current text suggests that the sender of CONNECTION_CLOSE keep sending the final packet in response to subsequent incoming packets with a backoff, until you wait long enough that you figure the other side probably figured it out and stopped sending. @nibanks points out that if you have a QUIC object that represents the connection, this means that the object and its data can't actually go away until the timeout is done. Is there value in having a short-circuit by which the sender of *_CLOSE can be sure it was received and go away early? The obvious solution is to suggest responding to a *_CLOSE with a matching *_CLOSE, but that just moves the timeout to the other side. Given that servers are likely to have a persistent connection management layer, that might be acceptable, but isn't so perfect for peer-to-peer applications. -- 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/733
- [quicwg/base-drafts] Acknowledging *_CLOSE (#733) Mike Bishop
- Re: [quicwg/base-drafts] Acknowledging *_CLOSE (#… Marten Seemann
- Re: [quicwg/base-drafts] Acknowledging *_CLOSE (#… Nick Banks
- Re: [quicwg/base-drafts] Acknowledging *_CLOSE (#… MikkelFJ
- Re: [quicwg/base-drafts] Acknowledging *_CLOSE (#… Christian Huitema
- Re: [quicwg/base-drafts] Acknowledging *_CLOSE (#… MikkelFJ
- Re: [quicwg/base-drafts] Acknowledging *_CLOSE (#… Martin Thomson