Re: [quicwg/base-drafts] Bring back AEAD_AES_128_CCM_8 now that we pad the plaintext (#2581)

David Schinazi <notifications@github.com> Tue, 28 May 2019 10:12 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 BE34A120145 for <quic-issues@ietfa.amsl.com>; Tue, 28 May 2019 03:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.391
X-Spam-Level:
X-Spam-Status: No, score=-1.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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=no 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 dvrujysLHFkT for <quic-issues@ietfa.amsl.com>; Tue, 28 May 2019 03:12:57 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C5FD12008A for <quic-issues@ietf.org>; Tue, 28 May 2019 03:12:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=XyCR7+KEkK9AAm2aGxH6vzNhv2w=; b=frYQqaPxvcTDHf6m HbMF++eGUqFQnop9BDGOkL+AsS9orYBIaBUU6lzINbppXp9tAsTQAL4vS/TI0bmX u4RHVOAK/KqLcBdPOuj3P9FeG4fH5jVqRCzTtewq23WyEDpIxRpxO1XQ0/UszT2u T39l5o9XLQl4dQRU4Y2iESagQ+M=
Received: by filter0476p1iad2.sendgrid.net with SMTP id filter0476p1iad2-8937-5CED09A8-10 2019-05-28 10:12:56.467186065 +0000 UTC m=+398838.642294566
Received: from github-lowworker-e711880.cp1-iad.github.net (unknown [140.82.115.67]) by ismtpd0045p1mdw1.sendgrid.net (SG) with ESMTP id Z4ihFadiR_qaAUZYTrfsYQ for <quic-issues@ietf.org>; Tue, 28 May 2019 10:12:56.353 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e711880.cp1-iad.github.net (Postfix) with ESMTP id 0D2294400BA for <quic-issues@ietf.org>; Tue, 28 May 2019 03:12:56 -0700 (PDT)
Date: Tue, 28 May 2019 10:12:56 +0000
From: David Schinazi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK37REGATHQNSQL42FN27I6CREVBNHHBTAQI4Y@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2581/496454668@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2581@github.com>
References: <quicwg/base-drafts/issues/2581@github.com>
Subject: Re: [quicwg/base-drafts] Bring back AEAD_AES_128_CCM_8 now that we pad the plaintext (#2581)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ced09a8b46f_611d3f9662acd9644939a1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak27vDYHEIEN1/gmQ44T0ekywjWdMjQiuyv3KU aCjk5+D5Qzjhs0imdSEbIVy9wkrivMnj4GIy1Nq9TvEGPuH5b7iwU0gLBWhkCRhHEeQuYsgzmEw+Qa Nv5eG1EXHflT2ACT/FJ/zbGmJJCo4FzvoykIh61JFMXYTwtyompiEkKsSUHhRvPlU3vWZHz7Ug3uJ1 k=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/05-O8IxAeRUi4x0kUKAIR29JK98>
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: Tue, 28 May 2019 10:12:59 -0000

I would personally have preferred to include AES_128_CCM_8 in the QUIC spec to have parity with TLS 1.3, but I can live with the text from #2743 because that allows someone to write a one-page spec on how to use AES_128_CCM_8 in QUIC without risking interoperability issues. I'm OK with closing this issue with no further action at this point.

-- 
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/2581#issuecomment-496454668