IETF Logo Mail Archive

Re: [quicwg/base-drafts] Connections SHOULD Respond to Connection Close Frames (#1029)

Nick Banks <notifications@github.com> Tue, 09 January 2018 14:55 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 C815F128961 for <quic-issues@ietfa.amsl.com>; Tue, 9 Jan 2018 06:55:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.381
X-Spam-Level:
X-Spam-Status: No, score=-5.381 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_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 7TkPfJdsP5S6 for <quic-issues@ietfa.amsl.com>; Tue, 9 Jan 2018 06:55:53 -0800 (PST)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62538126C0F for <quic-issues@ietf.org>; Tue, 9 Jan 2018 06:55:53 -0800 (PST)
Date: Tue, 09 Jan 2018 06:55:52 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1515509752; bh=bToDr2w5Fy2OGzPq3QnCGngy7FTdFj2rKsgMe7gK9mw=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uKUHf/J+wavDL6NYKK2vt04gf1MoB/8mwT06qk8nolHA5vkE7uDZaSk7AqYfVJ4fM CV7X4HLGkX9BNyWecCtAQBSPT5YskRCQfzmmOGqNxfPI5kjFz2TAs0Ds9lBgnsBuLP vquPfIZqZssA/QTRkTvHjuX+RQ3D7RhYNwBRdrKE=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc0e2745f40fece2e01bce02bbc76a864b785162492cf00000001166c99f892a169ce10e7bb4d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1029/356306987@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1029@github.com>
References: <quicwg/base-drafts/issues/1029@github.com>
Subject: Re: [quicwg/base-drafts] Connections SHOULD Respond to Connection Close Frames (#1029)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a54d7f8b92d4_7a9c2ae416f12ec443429"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/7w4R-cTbT7G3DJ1kCchmIH60dBI>
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, 09 Jan 2018 14:55:55 -0000

If not, then implementations that wish to respect the spec will always have to wait the full draining period. What is the harm in recommending the CONNECTION_CLOSE should be sent? It is a very useful signal to the endpoint that initially closed the connection.

-- 
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/1029#issuecomment-356306987

v2.30.2 | Report a Bug | By Email | System Status