IETF Logo Mail Archive

Re: [TLS] TLS 1.3 and OCSP stapling

Rob Stradling <rob.stradling@comodo.com> Mon, 14 December 2015 12:29 UTC

Return-Path: <rob.stradling@comodo.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3A21ACDE5 for <tls@ietfa.amsl.com>; Mon, 14 Dec 2015 04:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.38
X-Spam-Level:
X-Spam-Status: No, score=-1.38 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 glflqsTOoAWv for <tls@ietfa.amsl.com>; Mon, 14 Dec 2015 04:29:29 -0800 (PST)
Received: from mmextmx2.mcr.colo.comodoca.net (mail1.comodoca.com [91.209.196.72]) (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 02A0D1ACDDC for <tls@ietf.org>; Mon, 14 Dec 2015 04:29:28 -0800 (PST)
Received: (qmail 28351 invoked by uid 1004); 14 Dec 2015 12:29:26 -0000
Received: from ian.brad.office.comodo.net (HELO ian.brad.office.comodo.net) (192.168.0.202) by mmextmx2.mcr.colo.comodoca.net (qpsmtpd/0.84) with ESMTP; Mon, 14 Dec 2015 12:29:26 +0000
Received: (qmail 11239 invoked by uid 1000); 14 Dec 2015 12:29:26 -0000
Received: from and0004.comodo.net (HELO [192.168.0.58]) (192.168.0.58) (smtp-auth username rob, mechanism plain) by ian.brad.office.comodo.net (qpsmtpd/0.40) with (AES128-SHA encrypted) ESMTPSA; Mon, 14 Dec 2015 12:29:26 +0000
To: "Salz, Rich" <rsalz@akamai.com>, Martin Thomson <martin.thomson@gmail.com>, Ilari Liusvaara <ilariliusvaara@welho.com>
References: <20151211185258.GA5451@LK-Perkele-V2.elisa-laajakaista.fi> <CABkgnnU5orJz4YRan1WT-0bMEd0WZ1d1Jow=XMG1Ru2m9H9dCQ@mail.gmail.com> <2cef9d92f1e344f09053fc4efbe2c381@usma1ex-dag1mb1.msg.corp.akamai.com>
From: Rob Stradling <rob.stradling@comodo.com>
Message-ID: <566EB625.7060402@comodo.com>
Date: Mon, 14 Dec 2015 12:29:25 +0000
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <2cef9d92f1e344f09053fc4efbe2c381@usma1ex-dag1mb1.msg.corp.akamai.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/ek-943gjki6Yv_wLF7Ufm6jgRRM>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] TLS 1.3 and OCSP stapling
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
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, 14 Dec 2015 12:29:32 -0000

On 12/12/15 15:02, Salz, Rich wrote:
>> I think that the best way to deal with the status_request_v2 extension is to
>> make it a proper part of the TLS 1.3 messages, probably Certificate or
>> CertificateVerify.  This is a fairly heavily important extension.
>
> I'd be in favor of this.

Wouldn't switching OCSP stapling from "extension" to "proper part of the 
TLS 1.3 messages" mess things up for the TLS Feature certificate 
extension [1], which can be used to tell a TLS client that it should 
expect to receive TLS extension 5 (status_request) and/or TLS extension 
17 (status_request_v2) from the TLS server?

[1] https://tools.ietf.org/html/rfc7633

-- 
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online

v2.23.0 | Report a Bug | By Email