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 06AF9131213
 for <quic-issues@ietfa.amsl.com>; Thu, 14 Feb 2019 14:35:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Level: 
X-Spam-Status: No, score=-8.001 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_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 rUcbuYScqCKI for <quic-issues@ietfa.amsl.com>;
 Thu, 14 Feb 2019 14:35:41 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 398F013120E
 for <quic-issues@ietf.org>; Thu, 14 Feb 2019 14:35:41 -0800 (PST)
Date: Thu, 14 Feb 2019 14:35:40 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1550183740;
 bh=Cxglg3ufqZp5IlL1atBBOG4v+V7wdZ4lER8vUay3W2Y=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=Iy5a1f82ZmNZQKvfXpC3P1ZEmm3HZSdJMmHyrMunDoRwngtVS7N21e/aRndOqp0It
 VVKQYtVEnKiKnGXsAH7WwzuRlv8XAtTHIxradq2Za7cT3pYfSiHoosXYqTdx3tKyPt
 rAPy4/CIwWS0jvwQ6WJKlelur7q9YsLeHJGqHW1c=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abfb92e81331ec910d606eda9a47e7880cc40dc3ed92cf00000001187daf3c92a169ce1877f890@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2466/c463830354@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2466@github.com>
References: <quicwg/base-drafts/pull/2466@github.com>
Subject: Re: [quicwg/base-drafts] Bound 0-to-1-RTT Transition (#2466)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c65ed3c35c36_4cff3f99b7ed45b4990b3";
 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/D5wVHNNGX39iPP5_r6wsqAkN3SI>
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: Thu, 14 Feb 2019 22:35:43 -0000


----==_mimepart_5c65ed3c35c36_4cff3f99b7ed45b4990b3
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I'm not clear what you mean by "a requirement to demonstrate that they don't apply before they can be forgotten/changed"?  Do you just mean the stronger statement of checking that 0-RTT data doesn't exceed the limits?  I agree that #2461 is a stronger statement, but it's also more complex to verify -- you basically have to tag the processing of every data packet that arrives in 0-RTT and apply special logic to it.

It's entirely possible that we spec #2461 and people implement #2466 as a good-enough way of achieving the requirement.  :-)

-- 
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/pull/2466#issuecomment-463830354
----==_mimepart_5c65ed3c35c36_4cff3f99b7ed45b4990b3
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>I'm not clear what you mean by "a requirement to demonstrate that they=
 don't apply before they can be forgotten/changed"?  Do you just mean the=
 stronger statement of checking that 0-RTT data doesn't exceed the limits=
?  I agree that <a class=3D"issue-link js-issue-link" data-error-text=3D"=
Failed to load issue title" data-id=3D"409599624" data-permission-text=3D=
"Issue title is private" data-url=3D"https://github.com/quicwg/base-draft=
s/issues/2461" data-hovercard-type=3D"pull_request" data-hovercard-url=3D=
"/quicwg/base-drafts/pull/2461/hovercard" href=3D"https://github.com/quic=
wg/base-drafts/pull/2461">#2461</a> is a stronger statement, but it's als=
o more complex to verify -- you basically have to tag the processing of e=
very data packet that arrives in 0-RTT and apply special logic to it.</p>=

<p>It's entirely possible that we spec <a class=3D"issue-link js-issue-li=
nk" data-error-text=3D"Failed to load issue title" data-id=3D"409599624" =
data-permission-text=3D"Issue title is private" data-url=3D"https://githu=
b.com/quicwg/base-drafts/issues/2461" data-hovercard-type=3D"pull_request=
" data-hovercard-url=3D"/quicwg/base-drafts/pull/2461/hovercard" href=3D"=
https://github.com/quicwg/base-drafts/pull/2461">#2461</a> and people imp=
lement <a class=3D"issue-link js-issue-link" data-error-text=3D"Failed to=
 load issue title" data-id=3D"410515600" data-permission-text=3D"Issue ti=
tle is private" data-url=3D"https://github.com/quicwg/base-drafts/issues/=
2466" data-hovercard-type=3D"pull_request" data-hovercard-url=3D"/quicwg/=
base-drafts/pull/2466/hovercard" href=3D"https://github.com/quicwg/base-d=
rafts/pull/2466">#2466</a> as a good-enough way of achieving the requirem=
ent.  :-)</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/pull/2466#issuecomment-463830354">view it on GitHub</a>, o=
r <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq5uMwR=
uk_zYlIZsmTV7oKTTnFwIeks5vNeS8gaJpZM4a8iof">mute the thread</a>.<img src=3D=
"https://github.com/notifications/beacon/AWbkq6gn59bcTmaelsiN6jATbOY9_ePZ=
ks5vNeS8gaJpZM4a8iof.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://github.githubassets.com/images/email/message_cards/header.png","avata=
r_image_url":"https://github.githubassets.com/images/email/message_cards/=
avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/q=
uicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@=
MikeBishop in #2466: I'm not clear what you mean by \"a requirement to de=
monstrate that they don't apply before they can be forgotten/changed\"?  =
Do you just mean the stronger statement of checking that 0-RTT data doesn=
't exceed the limits?  I agree that #2461 is a stronger statement, but it=
's also more complex to verify -- you basically have to tag the processin=
g of every data packet that arrives in 0-RTT and apply special logic to i=
t.\r\n\r\nIt's entirely possible that we spec #2461 and people implement =
#2466 as a good-enough way of achieving the requirement.  :-)"}],"action"=
:{"name":"View Pull Request","url":"https://github.com/quicwg/base-drafts=
/pull/2466#issuecomment-463830354"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/pull/2466#issuecomment-4=
63830354",
"url": "https://github.com/quicwg/base-drafts/pull/2466#issuecomment-4638=
30354",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c65ed3c35c36_4cff3f99b7ed45b4990b3--

