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

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

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 88BF312002F for <>; Wed, 19 Jun 2019 01:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.391
X-Spam-Status: No, score=-6.391 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_24=1.618, 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 U2GdUmka_zbI for <>; Wed, 19 Jun 2019 01:41:42 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B82AA120128 for <>; Wed, 19 Jun 2019 01:41:41 -0700 (PDT)
Date: Wed, 19 Jun 2019 01:41:40 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560933700; bh=IKdMu+pksgyXaOH6Y6dAslnBlRenQo1m9y0Sjr/vL58=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JlaxrMfKadRRclsqyx9zcnEPwMVgrefSklmeLqrmr/8AggvqA5HvbNebOhFmjsa1a 7jk4kmeUWH2VfXoSzxYFvEJOkEXccJxAXJFXh0cH+0R3xQanmxvsB6HHjP7ZGpISGc Y5hpXK2dXlCcsUDQOgHRmtQKbjBq5oFiq5xFy2yU=
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_5d09f5443b499_11ac3fbf992cd95c29861e"; 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:41:44 -0000

My previous comment landed without me reading your latest comment.

>I think we can clarify that and the mechanism could be simple, because we already suggest that an endpoint might track the lowest, successfully unprotected packet number of the current key phase.

This is the hard part because that goal post keeps moving down as delayed packets arrive.
The problem is exactly if this goal post moves past a packet number observed with a more recent key.

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