IETF Logo Mail Archive

Re: [TLS] OCSP must staple

"Jeremy Rowley" <jeremy.rowley@digicert.com> Wed, 28 May 2014 19:00 UTC

Return-Path: <jeremy.rowley@digicert.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 EFB441A6F51 for <tls@ietfa.amsl.com>; Wed, 28 May 2014 12:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.054
X-Spam-Level:
X-Spam-Status: No, score=-3.054 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, 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 4qg__fXl3ZAj for <tls@ietfa.amsl.com>; Wed, 28 May 2014 12:00:33 -0700 (PDT)
Received: from mail.digicert.com (mail.digicert.com [64.78.193.232]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1831A6F41 for <tls@ietf.org>; Wed, 28 May 2014 12:00:33 -0700 (PDT)
Received: from JROWLEYL2 (unknown [67.137.52.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.digicert.com (Postfix) with ESMTPSA id 5CBF37FA3D6; Wed, 28 May 2014 13:00:29 -0600 (MDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=digicert.com; s=mail; t=1401303629; bh=HBy8+3u+zPlat5j2MUB3cIv3rD8HnFmoYk/trBkIVxw=; h=From:To:References:In-Reply-To:Subject:Date; b=DtItq+rjXRglgmSwS4IrQ9AMIXaG5gqG5gTRtiFU6u4aQ4YzVByXTxhBC7WG3flRt NeqebaySvEumHkAl9U1gIEdv5sQ3ssF/wytd0JjS2Up5ikOyLLZzB2dLXQxbELfKzG rK+Z4YjinTzsR7u9P6dWbjIjJe8Z8k6sIX6BnfT0=
From: Jeremy Rowley <jeremy.rowley@digicert.com>
To: 'Kurt Roeckx' <kurt@roeckx.be>, tls@ietf.org
References: <20140528184735.GA20602@roeckx.be>
In-Reply-To: <20140528184735.GA20602@roeckx.be>
Date: Wed, 28 May 2014 13:00:28 -0600
Message-ID: <097101cf7aa7$17f960a0$47ec21e0$@digicert.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFsdq/DppDfU/GgDQi/wJFPER5LaZwcYIrA
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/MqXlbBYZ4ZDfRM0-NjcJI6n0IYM
Subject: Re: [TLS] OCSP must staple
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: <http://www.ietf.org/mail-archive/web/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: Wed, 28 May 2014 19:00:36 -0000

We do.  I believe PHB was waiting for an OID assigned by IANA for must
staple.   I'm not sure the request was ever submitted, but I'll follow up
and make sure this moves forward.

Jeremy

-----Original Message-----
From: TLS [mailto:tls-bounces@ietf.org] On Behalf Of Kurt Roeckx
Sent: Wednesday, May 28, 2014 12:48 PM
To: tls@ietf.org
Subject: [TLS] OCSP must staple

Hi,

It seems there is a draft to have OCSP must staple
(draft-hallambaker-muststaple-00).  Does anybody know what the status of
that is?  I've tried to contact the author but didn't get any reply.

Is this something we want adopt?


Kurt

_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

v2.23.0 | Report a Bug | By Email