[quicwg/base-drafts] Encrypting token in Retry packet (#3477)
Quoc-Viet Nguyen <notifications@github.com> Sat, 22 February 2020 23:12 UTC
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 4DDB83A0A45 for <quic-issues@ietfa.amsl.com>; Sat, 22 Feb 2020 15:12:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.1
X-Spam-Level:
X-Spam-Status: No, score=-3.1 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, 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 qiFabMNPMGPV for <quic-issues@ietfa.amsl.com>; Sat, 22 Feb 2020 15:12:24 -0800 (PST)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D52383A0A44 for <quic-issues@ietf.org>; Sat, 22 Feb 2020 15:12:23 -0800 (PST)
Date: Sat, 22 Feb 2020 15:12:23 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1582413143; bh=zp06QEinBzkHNd7fB+vUc/zvZ87cpZwHHcAr4bKQuOQ=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ZG+a35NO3UUxN8mXpcZkneqAfNIpjnS0uGRqbsE+CJin+Sdi9HaedfCRjzge6SN2o 1uZvmqxViAuxpr9kGGQfU3taUMTcJJLX5vOQ0TToM8Io0PuQ1v80MrbO/RPCYxz9hQ csablh+5dWhRZumR1DsRzoA7JOb6Y5oWT4Zpjpts=
From: Quoc-Viet Nguyen <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZZPYGRIJY7INYLTMV4L3T5PEVBNHHCD4DU3Q@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3477@github.com>
Subject: [quicwg/base-drafts] Encrypting token in Retry packet (#3477)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e51b5571d6f9_4f9a3fd60becd9684465b9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nqv
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/noNABtjq5uj6iki4GbZVGB36wKE>
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: Sat, 22 Feb 2020 23:12:25 -0000
I have read through https://github.com/quicwg/base-drafts/pull/3120 and related issues (https://github.com/quicwg/base-drafts/issues/3274 https://github.com/quicwg/base-drafts/issues/3014) and wonder if we can have it similar to Initial Packet encryption instead. I understand we already have consensus but wonder if we can make the protocol simpler. In initial packet, the initial AEAD is calculated from Destination CID. So I propose we remove pseudo-packet concept and build AEAD from Original Destination CID to encrypt the retry token just like Initial packet encrypting its token, packet number and payload. I see the benefits are: - Consistent packet encryption mechanism, more code resuse (please) - No additional buffer to build pseudo-packet - Easier to have custom protocol (or next version) to use chosen AEAD, i.e. CHACHA20_POLY1305 - Can apply to other packets in future (e.g Version Negotiation) -- 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/3477
- [quicwg/base-drafts] Encrypting token in Retry pa… Quoc-Viet Nguyen
- Re: [quicwg/base-drafts] Encrypting token in Retr… Martin Thomson
- Re: [quicwg/base-drafts] Encrypting token in Retr… Quoc-Viet Nguyen
- Re: [quicwg/base-drafts] Encrypting token in Retr… Martin Thomson
- Re: [quicwg/base-drafts] Encrypting token in Retr… ianswett
- Re: [quicwg/base-drafts] Encrypting token in Retr… Lars Eggert