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 D45831200C5
 for <quic-issues@ietfa.amsl.com>; Mon, 28 Oct 2019 01:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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_HELO_NONE=0.001, 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 vHJr9wQ4-d6c for <quic-issues@ietfa.amsl.com>;
 Mon, 28 Oct 2019 01:00:12 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 56EBB120041
 for <quic-issues@ietf.org>; Mon, 28 Oct 2019 01:00:12 -0700 (PDT)
Date: Mon, 28 Oct 2019 01:00:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1572249611;
 bh=M0+TU1eehGUA3MiMLcrDwkO2Lr+maecYtWwn38QAR48=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=VxdBg0DyPFHus7HlVlaon1Uavl5YcQQUELnqxsaG4S6JAAAniWQ13vBCneVJGo3NG
 gwnnjHGdt8ybxpSvofB1UD5HucUO4hnmaQzHEpCyjFzaTTEugAT9VMnAZ8KLjoI3mK
 cbGHwmv5Sur2DdAqCqMQELAUS8tqyufwaJF6bOD8=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKZKGVZ6EHCUEG6RD253YPJIXEVBNHHB4QEEV4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3095/546833078@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3095@github.com>
References: <quicwg/base-drafts/issues/3095@github.com>
Subject: Re: [quicwg/base-drafts] Backoff of CONNECTION_CLOSE needs to be a
 MUST (#3095)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5db6a00b9027b_48693faa576cd9642326a5";
 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/BIej5JDz-48kDGctqHxeRwDh6ro>
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: Mon, 28 Oct 2019 08:00:15 -0000


----==_mimepart_5db6a00b9027b_48693faa576cd9642326a5
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

In #3157, I've gone with
* SHOULD limit when you retain packet protection keys (as you can stop sending packets once you receive CONNECTION_CLOSE)
* MUST limit when you drop packet protection keys (as you do not know when to stop)

Re https://github.com/quicwg/base-drafts/issues/3095#issuecomment-542920940, while we can define a rule based on how endpoints use CIDs, I think I prefer having a rule based on how a stack is implemented (i.e. when you drop packet protection keys) rather than how a stack is configured (i.e. the way CIDs are used). IMO, the latter is harder to test and therefore fragile.

-- 
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/3095#issuecomment-546833078
----==_mimepart_5db6a00b9027b_48693faa576cd9642326a5
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>In <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="513144065" data-permission-text="Issue title is private" data-url="https://github.com/quicwg/base-drafts/issues/3157" data-hovercard-type="pull_request" data-hovercard-url="/quicwg/base-drafts/pull/3157/hovercard" href="https://github.com/quicwg/base-drafts/pull/3157">#3157</a>, I've gone with</p>
<ul>
<li>SHOULD limit when you retain packet protection keys (as you can stop sending packets once you receive CONNECTION_CLOSE)</li>
<li>MUST limit when you drop packet protection keys (as you do not know when to stop)</li>
</ul>
<p>Re <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="507544751" data-permission-text="Issue title is private" data-url="https://github.com/quicwg/base-drafts/issues/3095" data-hovercard-type="issue" data-hovercard-url="/quicwg/base-drafts/issues/3095/hovercard?comment_id=542920940&amp;comment_type=issue_comment" href="https://github.com/quicwg/base-drafts/issues/3095#issuecomment-542920940">#3095 (comment)</a>, while we can define a rule based on how endpoints use CIDs, I think I prefer having a rule based on how a stack is implemented (i.e. when you drop packet protection keys) rather than how a stack is configured (i.e. the way CIDs are used). IMO, the latter is harder to test and therefore fragile.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3095?email_source=notifications&amp;email_token=AFTOJK4BD6MLAW6TDLBWHM3QQ2LYXA5CNFSM4JBEQ6Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECMAFNQ#issuecomment-546833078">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK52LEMFQS23PM5IYITQQ2LYXANCNFSM4JBEQ6QQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK642AG6YH4VESD57ALQQ2LYXA5CNFSM4JBEQ6Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECMAFNQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3095?email_source=notifications\u0026email_token=AFTOJK4BD6MLAW6TDLBWHM3QQ2LYXA5CNFSM4JBEQ6Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECMAFNQ#issuecomment-546833078",
"url": "https://github.com/quicwg/base-drafts/issues/3095?email_source=notifications\u0026email_token=AFTOJK4BD6MLAW6TDLBWHM3QQ2LYXA5CNFSM4JBEQ6Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECMAFNQ#issuecomment-546833078",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5db6a00b9027b_48693faa576cd9642326a5--

