Re: [quicwg/base-drafts] Receiver's behavior on key update (#2791)

MikkelFJ <> Wed, 19 June 2019 08:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A66A9120391 for <>; Wed, 19 Jun 2019 01:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Status: No, score=-6.463 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gyX39mTj6Pa4 for <>; Wed, 19 Jun 2019 01:33:32 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CEA6712002F for <>; Wed, 19 Jun 2019 01:33:31 -0700 (PDT)
Date: Wed, 19 Jun 2019 01:33:30 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560933210; bh=J5Vy1xACfAqat5mKdZy913gsUQrK1mrR9nIQaZebRtU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LW6MICnrM/DN6beRsOgMkFja++cYoegH/6EAw7O0k4FgW1klciyjkgCah50WAlKwH Wl5OR/zQb18iwgHXaCwtOV3VtXcHGM1HnVdnQPoOdokJ8g7XtmJPLJzEKvb/TXPo7L F64Q/GTja15SRyBhVrlkRA+U4AnXYfP0LwsliZaY=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2791/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Receiver's behavior on key update (#2791)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d09f35a91c98_47323ff1acccd96c2488ae"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 19 Jun 2019 08:33:34 -0000

Clarification on violation:
a new key in an old packet: should never be violation, unless it is too old in which case it can optionally trigger a close.

If it is too old, it is not an attack vector because client mixed up keys without discussion. Only, it is hard to specify exactly when old is too old without complex text.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: