IETF Logo Mail Archive

Re: [quicwg/base-drafts] Where can you send CONNECTION_CLOSE (#2151)

ekr <notifications@github.com> Fri, 14 December 2018 00:30 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 8EADC1286E7 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 16:30:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.459
X-Spam-Level:
X-Spam-Status: No, score=-9.459 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 ltkfJb9wSqOV for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 16:30:28 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B158512E036 for <quic-issues@ietf.org>; Thu, 13 Dec 2018 16:30:28 -0800 (PST)
Date: Thu, 13 Dec 2018 16:30:27 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544747427; bh=5SCEmZhZQ3do1QjoUIcW4go2uAg9aqZy/0C2LNTIPhU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xEPSf7DN0/6PskA0HFUJkcGRBymUhZCzF0TBDU7XQaJvVk1RoaKV/6Op30ByGHfox WXSwiH+JripL+g9SoptscNVx/jJn+CPcZ0n6cClWSh1xLCQRCBxvs666GB/zxGb2Db 9O6LPZzmoBP18TadMGyOlDnfW3UEngKoNSNJXS3w=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf6ced647401682348647fb2dd902f70eff2f794792cf00000001182abba392a169ce174b9201@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2151/447170985@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2151@github.com>
References: <quicwg/base-drafts/issues/2151@github.com>
Subject: Re: [quicwg/base-drafts] Where can you send CONNECTION_CLOSE (#2151)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12f9a3c5755_78553fcdf5ed45c4139736"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/BnOJaS-upb9yyfJvMq5qzhmXGWU>
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, 14 Dec 2018 00:30:30 -0000

I'm not sure. It seems like there are two policies:

- Always use level N until you are sure that the other side has level N+1
- Always use the highest level.

I take you to be proposing the first of these, which, I believe, means "use the highest level where you have received packets from the peer in (or zero)". This text may say that, but all this stuff about certain is kind of hard to parse. Rather than making people reason it out, I think we should provide them with a clear rule (for instance the one above).





-- 
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/2151#issuecomment-447170985

v2.23.0 | Report a Bug | By Email