Re: [TLS] Status of X.509v3 TLS Feature Extension?

Stephen Checkoway <s@pahtak.org> Mon, 28 April 2014 19:35 UTC

Return-Path: <s@pahtak.org>
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 5CAA71A6FA1 for <tls@ietfa.amsl.com>; Mon, 28 Apr 2014 12:35:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 iaCX5WN0WKij for <tls@ietfa.amsl.com>; Mon, 28 Apr 2014 12:35:29 -0700 (PDT)
Received: from mail-qc0-f173.google.com (mail-qc0-f173.google.com [209.85.216.173]) by ietfa.amsl.com (Postfix) with ESMTP id 6AED21A6F0A for <tls@ietf.org>; Mon, 28 Apr 2014 12:35:29 -0700 (PDT)
Received: by mail-qc0-f173.google.com with SMTP id r5so7414142qcx.18 for <tls@ietf.org>; Mon, 28 Apr 2014 12:35:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=lIUniBsi5hKSRplGy3pjhiRWRaMqGCrWECNL5NdXVmA=; b=VCjWcqYJgpg1d+0FqiJ7gYQpRa8u5/UyCqqnpheLrxTMvGhcF8NYjBSOi+ZY7QUrfL HUB0ZU0Hx8eb4hsTX1wJ49gdTPW64AVtxjNlMUKjq5pLQSWMfmrV3Lm1/4cLGE9f6Idi IYPCVc+MwTsOTc0ENYFfKlcbRF7tHAAtM/u88Jk27a5ljoYsQ5WalyIWmZCxTfVT8VVR kvkDo8T3VdFMKGqUZEULA76SLKF6EmzRmGzByKyDYvqje51ZEyXWzfEzYrUoYvCSHlzM 2yoq1s5SbddnNGXZ74G4omPTvj67iXyZGE6lX43M5rU+nOo6CPlUcbV6izn7U7p6e+GM tTAQ==
X-Gm-Message-State: ALoCoQkzwWCoDXB62l61ol9E0ZIsB04bGpjdjesVaMMUJM+MyFauT7m4vU2m97AG26ysi3+IImgs
X-Received: by 10.140.21.231 with SMTP id 94mr34550227qgl.31.1398713728288; Mon, 28 Apr 2014 12:35:28 -0700 (PDT)
Received: from zbox.pahtak.org (c-68-48-196-126.hsd1.md.comcast.net. [68.48.196.126]) by mx.google.com with ESMTPSA id c16sm34890813qaw.4.2014.04.28.12.35.27 for <tls@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Apr 2014 12:35:27 -0700 (PDT)
Received: from polaris.isi.jhu.edu (polaris.isi.jhu.edu [128.220.247.217]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by zbox.pahtak.org (Postfix) with ESMTPSA id D1205AC287F for <tls@ietf.org>; Mon, 28 Apr 2014 15:35:26 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Stephen Checkoway <s@pahtak.org>
In-Reply-To: <9A043F3CF02CD34C8E74AC1594475C738AC09A2C@uxcn10-tdc06.UoA.auckland.ac.nz>
Date: Mon, 28 Apr 2014 15:35:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4ACA9D88-4A16-415D-AFC9-2CC5F8D874D1@pahtak.org>
References: <9A043F3CF02CD34C8E74AC1594475C738AC09A2C@uxcn10-tdc06.UoA.auckland.ac.nz>
To: "<tls@ietf.org>" <tls@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/c81gH-c26IzOcUaib5nBjuicy-s
Subject: Re: [TLS] Status of X.509v3 TLS Feature Extension?
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: Mon, 28 Apr 2014 19:35:31 -0000

On Apr 28, 2014, at 3:32 PM, Peter Gutmann <pgut001@cs.auckland.ac.nz> wrote:

> Stephen Checkoway <s@pahtak.org> writes:
>> On Apr 28, 2014, at 1:42 PM, Martin Rex <mrex@sap.com> wrote:
>> 
>>> EV certs seem to be able to provide a benefit without "fail-hard".
>> 
>> That's the first time I've ever heard that claim. What benefit do they
>> provide users?
> 
> Well now that's a completely different question.  The original statement was
> that they provide a benefit, no-one said the benefit was to users.

Indeed. Your book has a very nice discussion of them.

-- 
Stephen Checkoway