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 BF41E130EA5
 for <quic-issues@ietfa.amsl.com>; Mon, 18 Jun 2018 05:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level: 
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01]
 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 zxoVbDbaiUaP for <quic-issues@ietfa.amsl.com>;
 Mon, 18 Jun 2018 05:03:37 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 57352130E96
 for <quic-issues@ietf.org>; Mon, 18 Jun 2018 05:03:37 -0700 (PDT)
Date: Mon, 18 Jun 2018 05:03:36 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1529323416;
 bh=cZ0IFuYhvnRqpIR8brewObnmOuGPB2Mbb9Cit6nFjRw=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=PiFTk87DpHlol4dFpVpADk1c/twkL+3aFdkZn4ClQ5zsgJALGWAJdlzUBCSE6bmVT
 BmpkiDnf21PHJvEMLwf9P2J8i9MDDVO7A/mgQ/tFTWhqmwDUP5gbeAv81XPRn8nozU
 zsn4sucSiGOYfkMRJ+UVh+zq0VQdWvVpNB3AqXzQ=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab8ce0976e00231b058f502ec1234a7633417fb55792cf00000001173f619892a169ce138d6870@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1405/398031584@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1405@github.com>
References: <quicwg/base-drafts/issues/1405@github.com>
Subject: Re: [quicwg/base-drafts] Handling of duplicate packets (#1405)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5b279f988bf77_73d73ff644322f88332182";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/waZPSAKvcqCXnoBnZ7v8mORg6_k>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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, 18 Jun 2018 12:03:39 -0000


----==_mimepart_5b279f988bf77_73d73ff644322f88332182
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

But I think you are right that QUIC should much more prominently document such a rekeying requirement. For example that a key update MUST happen no later than after 2^32 packet exhanges or earlier if specific AEAD mode requires this (but such modes probably shouldn't be permitted).

While some crypto modes could surve much more than 2^32 other modes would eventually fail badly (AES-GCM). By forcing an update no later than 2^32 it is easy to avoid implementation mistakes and for the peer to do a hard disconnect if keys are not updated. Silent crypto errors are really bad.

-- 
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/1405#issuecomment-398031584
----==_mimepart_5b279f988bf77_73d73ff644322f88332182
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>But I think you are right that QUIC should much more prominently docum=
ent such a rekeying requirement. For example that a key update MUST happe=
n no later than after 2^32 packet exhanges or earlier if specific AEAD mo=
de requires this (but such modes probably shouldn't be permitted).</p>
<p>While some crypto modes could surve much more than 2^32 other modes wo=
uld eventually fail badly (AES-GCM). By forcing an update no later than 2=
^32 it is easy to avoid implementation mistakes and for the peer to do a =
hard disconnect if keys are not updated. Silent crypto errors are really =
bad.</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/issues/1405#issuecomment-398031584">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq91V=
CFZ9u7vxbas-mGSwed2lOWgyks5t95cYgaJpZM4UUmEV">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq6kEt2aJHbCPwDTUDedV1BeJ=
I6Eaks5t95cYgaJpZM4UUmEV.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/ld+json">{"@context":"http://schema.org","@ty=
pe":"EmailMessage","potentialAction":{"@type":"ViewAction","target":"http=
s://github.com/quicwg/base-drafts/issues/1405#issuecomment-398031584","ur=
l":"https://github.com/quicwg/base-drafts/issues/1405#issuecomment-398031=
584","name":"View Issue"},"description":"View this Issue on GitHub","publ=
isher":{"@type":"Organization","name":"GitHub","url":"https://github.com"=
}}</script>
<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://assets-cdn.github.com/images/email/message_cards/header.png","avatar_=
image_url":"https://assets-cdn.github.com/images/email/message_cards/avat=
ar.png","action":{"name":"Open in GitHub","url":"https://github.com/quicw=
g/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@mikk=
elfj in #1405: But I think you are right that QUIC should much more promi=
nently document such a rekeying requirement. For example that a key updat=
e MUST happen no later than after 2^32 packet exhanges or earlier if spec=
ific AEAD mode requires this (but such modes probably shouldn't be permit=
ted).\r\n\r\nWhile some crypto modes could surve much more than 2^32 othe=
r modes would eventually fail badly (AES-GCM). By forcing an update no la=
ter than 2^32 it is easy to avoid implementation mistakes and for the pee=
r to do a hard disconnect if keys are not updated. Silent crypto errors a=
re really bad."}],"action":{"name":"View Issue","url":"https://github.com=
/quicwg/base-drafts/issues/1405#issuecomment-398031584"}}}</script>
<script type=3D"application/ld+json">{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [quicwg/base-drafts] Handling of duplicate packets (#1405)"=
,
"sections": [
{
"text": "",
"activityTitle": "**MikkelFJ**",
"activityImage": "https://assets-cdn.github.com/images/email/message_card=
s/avatar.png",
"activitySubtitle": "@mikkelfj",
"facts": [

]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \=
"quicwg/base-drafts\",\n\"issueId\": 1405,\n\"IssueComment\": \"{{IssueCo=
mment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"q=
uicwg/base-drafts\",\n\"issueId\": 1405\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/quicwg/base-drafts/issues/1405#issuecomment-39=
8031584"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 3409431=
25\n}"
}
],
"themeColor": "26292E"
}</script>=

----==_mimepart_5b279f988bf77_73d73ff644322f88332182--

