IETF Logo Mail Archive

Re: [therightkey] [cabfpub] Updated Certificate Transparency + Extended Validation plan

"Jeremy Rowley" <jeremy.rowley@digicert.com> Wed, 05 February 2014 02:38 UTC

Return-Path: <jeremy.rowley@digicert.com>
X-Original-To: therightkey@ietfa.amsl.com
Delivered-To: therightkey@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC7D41A0170 for <therightkey@ietfa.amsl.com>; Tue, 4 Feb 2014 18:38:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.836
X-Spam-Level:
X-Spam-Status: No, score=-4.836 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_MED=-2.3, RP_MATCHES_RCVD=-0.535, 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 E74-BAujQ1_E for <therightkey@ietfa.amsl.com>; Tue, 4 Feb 2014 18:38:02 -0800 (PST)
Received: from mail.digicert.com (mail.digicert.com [64.78.193.232]) by ietfa.amsl.com (Postfix) with ESMTP id 689CE1A0190 for <therightkey@ietf.org>; Tue, 4 Feb 2014 18:38:02 -0800 (PST)
Received: from JROWLEYL1 (c-67-166-110-179.hsd1.ut.comcast.net [67.166.110.179]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.digicert.com (Postfix) with ESMTPSA id 8F13F2E0A7; Tue, 4 Feb 2014 19:38:01 -0700 (MST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=digicert.com; s=mail; t=1391567881; bh=A1Ob75Nbirfz3utoBcYWf72Yl/YJZQNhyZsJPVgaAtA=; h=From:To:Cc:References:In-Reply-To:Subject:Date; b=MtDrA0EdSzco86cL5IumvS57f181JhaSWetDXZUHwM8rFy9qLW82xn1uk2ebin8EL fXe8aHyxCdPZpn7HJXWv5/QVozVo9b7+Oar6HdBpTeXhnOuOzeO9Ij1TGfWtsjiu+6 udK6BXn9gl1cLFqXI90BbomNrqw85mpVozB9BGbc=
From: Jeremy Rowley <jeremy.rowley@digicert.com>
To: 'Wayne Thayer' <wthayer@godaddy.com>, 'Ryan Sleevi' <sleevi@google.com>
References: <CABrd9STwBDxwB1vtmS9Ozb5e_7D=zfOqkOBeAaT2HG7X-cw5gw@mail.gmail.com> <647dad549e3047e4a94c721a616f1dee@CO1PR02MB064.namprd02.prod.outlook.com> <CACvaWvYb-anrri8rzxNDee_UW4AKM7uNC7j7UwHqPRnK4oQiFw@mail.gmail.com> <CF16EFDA.678DA%wthayer@godaddy.com>
In-Reply-To: <CF16EFDA.678DA%wthayer@godaddy.com>
Date: Tue, 04 Feb 2014 19:38:05 -0700
Message-ID: <08b001cf221b$4cd7b4a0$e6871de0$@digicert.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_08B1_01CF21E0.A07B2690"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGGS/IGH2GP3iOZeF9RA+GsPjuqQQIVdKDBAjguOYYBXOgcbJsKSiSg
Content-Language: en-us
Cc: therightkey@ietf.org, 'Ben Laurie' <benl@google.com>, certificate-transparency@googlegroups.com, 'CABFPub' <public@cabforum.org>
Subject: Re: [therightkey] [cabfpub] Updated Certificate Transparency + Extended Validation plan
X-BeenThere: therightkey@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <therightkey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/therightkey>, <mailto:therightkey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/therightkey/>
List-Post: <mailto:therightkey@ietf.org>
List-Help: <mailto:therightkey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/therightkey>, <mailto:therightkey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Feb 2014 02:38:04 -0000

I'm confused as well.  Does that mean Android will start showing an EV
indicator?

 

From: therightkey [mailto:therightkey-bounces@ietf.org] On Behalf Of Wayne
Thayer
Sent: Tuesday, February 04, 2014 7:33 PM
To: Ryan Sleevi
Cc: therightkey@ietf.org; Ben Laurie;
certificate-transparency@googlegroups.com; CABFPub
Subject: Re: [therightkey] [cabfpub] Updated Certificate Transparency +
Extended Validation plan

 

 

Hi Wayne,

 

Considering we already do not indicate EV on Android, nor have we ever, I
don't think this perceived loss of functionality is as significant as you
may believe.

 

Further, considering the very real and distinct performance characteristics
of mobile (radio warmups, RTTs, initcwnds), the idea of fetching OCSP, or,
worse, CRLs - especially when some CAs have CRLs that are quite large (20+
MB) - in order to assure the EV display is... non-ideal. So again, the EV
indicator on mobile is not as strong or as present as it may be on desktop
platforms.

 

In that case, what does this statement mean?

 

Chrome for mobile platforms will cease to show EV indicators for
certificates that are not CT qualified according to the criteria below.

 

 

 

-----Original Message-----
From: therightkey [mailto:therightkey-bounces@ietf.org] On Behalf Of Ben
Laurie
Sent: Tuesday, February 04, 2014 10:08 AM
To: CABFPub; certificate-transparency@googlegroups.com;
therightkey@ietf.org

Subject: [therightkey] Updated Certificate Transparency + Extended
Validation plan

Enclosed, our revised plan.

Comments welcome.

_______________________________________________
Public mailing list
Public@cabforum.org
https://cabforum.org/mailman/listinfo/public

v2.23.0 | Report a Bug | By Email