Re: [quicwg/base-drafts] Encrypting Retry token (#3274)

Christian Huitema <> Fri, 06 December 2019 20:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9F4B6120091 for <>; Fri, 6 Dec 2019 12:43:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_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] 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 0n2vReCFAtmx for <>; Fri, 6 Dec 2019 12:43:53 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C60D112006B for <>; Fri, 6 Dec 2019 12:43:52 -0800 (PST)
Date: Fri, 06 Dec 2019 12:43:51 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1575665031; bh=Q4/+rgrv7OtZRI0+5R36Rcj0Fncrdt4lj94rrczeLaQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TwLzGEE94hRiX6l0D5LP/98B7mndG2BvHhVeoTnxi1s+ITphUr2jB7oqtYuZVak37 xb5wZ9NyRuUnkj5iXAvJzKVP7ZoI8CbxY/Jrg14VXLsNv2vtuwLvW9wuw9eC01GlXb LUYZRS9NQl630wxVvanSivgZWjRInXj84gerfhKc=
From: Christian Huitema <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3274/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Encrypting Retry token (#3274)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5deabd87db686_6913fbe8fecd960103266"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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: Fri, 06 Dec 2019 20:43:55 -0000

I think I agree with Nick's reasoning. We started this issue by looking only at corruption during transmission. If we focus on that, a simple checksum would be sufficient. We can now start spin-bitting the checksum: crc64, fnv1a, 0-keyed aesgcm, md5... In fact, for curiosity, what is the spec of ghash?

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