IETF Logo Mail Archive

Re: [TLS] Mail regarding draft-ietf-tls-tls13

Tony Arcieri <bascule@gmail.com> Mon, 18 June 2018 15:36 UTC

Return-Path: <bascule@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2F39130DE1 for <tls@ietfa.amsl.com>; Mon, 18 Jun 2018 08:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5lxrm4G5UsiH for <tls@ietfa.amsl.com>; Mon, 18 Jun 2018 08:36:12 -0700 (PDT)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (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 3F34D12872C for <tls@ietf.org>; Mon, 18 Jun 2018 08:36:12 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id q135-v6so9805283vkh.1 for <tls@ietf.org>; Mon, 18 Jun 2018 08:36:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eDbQ2ceoRWFgB6o5C2Mg1q606h+WhgPq605oiogjeFg=; b=JlWW7ZsyTaRHBqblGIaRWWNFIc4S8L0JPPEhG8rbQEfS+DZsa+G2c5vXMCNRSZJ7kq LtElVtxna+0d6u9aCnm67F3/nOhIapR3IGGGFEmw/ZIqt/8ZFuoUBEdLlpk0j3J9805a feszUFpeSbuZDSch8uEkmIqFUwdBuAelCwm3WnHSluTZI6ftu4oLKEH0JzyTTeH+qVC2 etqZqqEnUpEn4nobQkztSdjG57mpMQqn3p2CT+qYZfEyeeBxMVppvbKIV7nz/20cTLK5 MIU7yV22yqVUHetGgeV7NPpZAt3xIqrfp/ZB4VyWSHtbIKawZPe7rQD3oT5e3JtN4abo kDng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eDbQ2ceoRWFgB6o5C2Mg1q606h+WhgPq605oiogjeFg=; b=gSRYbcUS8PnPhlpc1u2HhNVvam2YB+QRf8lYXWiHUJDVF568j5lIW82YZE1GDjxedD wOczdaj1iOup/dwu9DVLZj0ZdcyB470iXsfyqc/22p+hFTnhy95gMfmlU5AyTCbmNPVv 1D2HCrpcTL+moXV1vww+eMJVZGabvygHUEu1gVDeiXhskd+yToMykvshbN2KghJi6dwq FLyQxdYQc7iEeSgTWttlsH/SVv4c6Iujx/GDHsnQNFZxYktTswpIhmCdISzoEMjyOcOM dWnstNG0LcXqQ0H5AZQLpEQ1vBxPbnU39NGGv0YQMYu4s6Xa1CVDfVPVobAL/jk1sUDx +giQ==
X-Gm-Message-State: APt69E0N/3BZ+1+BLwF806buvlTAP7Xd8oqqZLcnU+7QpRLYQdAcfjj7 KjIAsOu9w+Wszim3XD3x+TDTsIzeyYKMPK3WoGM5jg==
X-Google-Smtp-Source: ADUXVKJhh7Ob+NZ9U7+ppYXceAizL0Tkyc1yJuSN3MmftupSVbISzwpQ3pVpRFiw4wcgaA1AYHV2MVWhl71/WeVXQJI=
X-Received: by 2002:a1f:2046:: with SMTP id g67-v6mr7872802vkg.43.1529336171244; Mon, 18 Jun 2018 08:36:11 -0700 (PDT)
MIME-Version: 1.0
References: <BN7PR14MB23560D791932A8CB164C592D917F0@BN7PR14MB2356.namprd14.prod.outlook.com> <897AC345-0832-4252-9D96-5A030CBEAD25@dukhovni.org> <cc5fe1d8-b065-4f30-8b76-57714aea1949@iongroup.com>
In-Reply-To: <cc5fe1d8-b065-4f30-8b76-57714aea1949@iongroup.com>
From: Tony Arcieri <bascule@gmail.com>
Date: Mon, 18 Jun 2018 08:36:00 -0700
Message-ID: <CAHOTMV+P_VWz=5uLmG=SFd5PYNgxpT=DYg3+vQffs_cqMwRXSQ@mail.gmail.com>
To: ben.personick@iongroup.com
Cc: "<tls@ietf.org>" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003ab21a056eec530f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Yj0XHKG-hsSfZzydYbAEo8eGLUw>
Subject: Re: [TLS] Mail regarding draft-ietf-tls-tls13
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2018 15:36:14 -0000

On Mon, Jun 18, 2018 at 6:30 AM Ben Personick <ben.personick@iongroup.com>
wrote:

> There is a common thread circulating, that all support for RSA
> Certificates/Ciphers are dropped in TLS 1.3.
>

RSA certificates will continue to work in TLS 1.3+.

What will not be supported in TLS 1.3+ is RSA key transport / key
encipherment (which lacks forward secrecy, among other problems). However,
this is a property of how the protocol does key exchange / key agreement
and has nothing to do with certificates.

-- 
Tony Arcieri

v2.23.0 | Report a Bug | By Email