IETF Logo Mail Archive

Re: [quicwg/base-drafts] Don't allow use of AEAD_AES_128_CCM_8 (#2029)

Martin Thomson <notifications@github.com> Wed, 21 November 2018 06:31 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 01E7C1293FB for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 22:31:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 f0XDmMPZ1-ZJ for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 22:31:40 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B85C128766 for <quic-issues@ietf.org>; Tue, 20 Nov 2018 22:31:39 -0800 (PST)
Date: Tue, 20 Nov 2018 22:31:39 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542781899; bh=g3+UJRYhTumdmrhvZEU8KSS9xlD75fKRqSnCe6xSf6E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F33kNDWtJL6JwpQ7Va4HDR4TnISsNSU679/PTC9Gq5fzWs0VYuS5kHoBqO1R4JX5Z tdLaolsCUozeUYI/BRhaBWBhtmXtjWTomPp/5HL7HxmsM1sayYtWlmqtv1044lNX3K r+RGlvHNCAf05R+ixhNGAUtZFvKKZ2nTIONr//Qo=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab13a7d1b87afb04eb91dbdea4e77cc5fc4dea9fa992cf00000001180cbdcb92a169ce16d3575c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2029/c440552150@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2029@github.com>
References: <quicwg/base-drafts/pull/2029@github.com>
Subject: Re: [quicwg/base-drafts] Don't allow use of AEAD_AES_128_CCM_8 (#2029)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bf4fbcb241dd_6c683fb7a90d45bc5163fa"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/4CqaexJ-Xmzax2u9Xt-hod7aFSA>
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: Wed, 21 Nov 2018 06:31:42 -0000

> Do we need to say anything about cipher suites that might get defined for TLS 1.3 after we ship QUIC?

We do elsewhere; for them to be used, they need a corresponding header protection algorithm.  That's all, but that's enough to prevents the CCM suite from being used.


-- 
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/pull/2029#issuecomment-440552150

v2.23.0 | Report a Bug | By Email