Re: [MLS] Substitute AES-128-GCM with AES-256-GCM for TreeKEM
"Salz, Rich" <rsalz@akamai.com> Thu, 20 September 2018 11:55 UTC
Return-Path: <rsalz@akamai.com>
X-Original-To: mls@ietfa.amsl.com
Delivered-To: mls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 140B7130E92 for <mls@ietfa.amsl.com>; Thu, 20 Sep 2018 04:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 PkWwUf5Zv3jA for <mls@ietfa.amsl.com>; Thu, 20 Sep 2018 04:55:41 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 302C1130E85 for <mls@ietf.org>; Thu, 20 Sep 2018 04:55:41 -0700 (PDT)
Received: from pps.filterd (m0122330.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w8KBppUM007217; Thu, 20 Sep 2018 12:55:40 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=bbCDdhrzUsTPPox/S9LzwBqI/equg/WI94y0s05vBM8=; b=BOe+5bUNPYU92ohBEQf44BCe+RMD+dQRD3aBEKyYWle3C+94N5z2GhhwW4KGvuvZ19YI +gutRLtoNTWPK6/h4VtNDN5aaFIYt3JWjBME5h6FHVClcdeu5LEM5g8pwPaqh9XjW8vD ShxiYVLUuGr3azDr0+eATfFPkJy+ZrgB1cETxmIr2u7fbaVkuNYkewpa9tq2LAHQZxqG SMMhDo0Xra1olqyo1/IvtF3QbKeTnY6f+fRGRdKu6O8q3MJU/ae09Wixnm1gIMfXgFC0 lHmDGWtobpwGPDJnMzJgGoPjWabfbKCdKh0Zmy4NjMsenf+b9ZTTcR1iSIl52PlFTeai Ow==
Received: from prod-mail-ppoint3 (a96-6-114-86.deploy.static.akamaitechnologies.com [96.6.114.86] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 2mkxn71pqr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 20 Sep 2018 12:55:40 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w8KBnu4E009267; Thu, 20 Sep 2018 07:55:39 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.31]) by prod-mail-ppoint3.akamai.com with ESMTP id 2mgwdwh77e-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 20 Sep 2018 07:55:39 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 20 Sep 2018 07:55:37 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1365.000; Thu, 20 Sep 2018 07:55:37 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Raphael Robert <raphael@wire.com>, "mls@ietf.org" <mls@ietf.org>
Thread-Topic: [MLS] Substitute AES-128-GCM with AES-256-GCM for TreeKEM
Thread-Index: AQHUUDygXlE2RNBLW0SuJXugYVQdcqT4K+EAgAEXsAD//82kAA==
Date: Thu, 20 Sep 2018 11:55:37 +0000
Message-ID: <E91763CB-C647-4E83-BC01-0ECD22254F46@akamai.com>
References: <7397E576-521F-4198-9232-C59530877E19@wire.com> <CAL02cgQb0BnPKQ015Uh5VOAsvSD6iXK4AE==Vyw9WXac0Th_kg@mail.gmail.com> <911130F4-8B46-45C9-A4A6-8359A950DD48@wire.com>
In-Reply-To: <911130F4-8B46-45C9-A4A6-8359A950DD48@wire.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.11.0.180909
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.40.146]
Content-Type: multipart/alternative; boundary="_000_E91763CBC6474E83BC010ECD22254F46akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-20_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809200121
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-20_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809200122
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/Iumw5s4ZtlAIPM31PHgnuwv2gL8>
Subject: Re: [MLS] Substitute AES-128-GCM with AES-256-GCM for TreeKEM
X-BeenThere: mls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Messaging Layer Security <mls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mls>, <mailto:mls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mls/>
List-Post: <mailto:mls@ietf.org>
List-Help: <mailto:mls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mls>, <mailto:mls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2018 11:55:43 -0000
Is there a good rationale, perhaps a link, explaining why all parts of a cipher-suite need to be at the same strength? I tend to call those things “crypto numerology” but perhaps (not being a cryptographer) I’m just biased. Yes, I understand that it might be no better than the weakest link.
- [MLS] Substitute AES-128-GCM with AES-256-GCM for… Raphael Robert
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Salz, Rich
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Richard Barnes
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Dennis Jackson
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Richard Barnes
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Dennis Jackson
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Raphael Robert
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Richard Barnes
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Salz, Rich
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Salz, Rich
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Joel Alwen
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Salz, Rich
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Joel Alwen
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Dennis Jackson
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Richard Barnes
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Salz, Rich
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Raphael Robert
- Re: [MLS] Substitute AES-128-GCM with AES-256-GCM… Joel Alwen