[cabfpub] Hopefully Final Version of Google's EV/CT plan

kirk_hall at trendmicro.com kirk_hall at trendmicro.com
Tue Mar 25 01:33:27 UTC 2014

Trend Micro agrees with both parts of Rick's message below.  

If something is worth doing, it's worth doing well.  Let's get all the specifics nailed down and tested.

Our limited discussion with enterprise clients indicates very strong support for the PRIVATE option, so that will probably be our default option.


-----Original Message-----
From: public-bounces at cabforum.org [mailto:public-bounces at cabforum.org] On Behalf Of Rick Andrews
Sent: Monday, March 24, 2014 3:04 PM
To: Ben Laurie
Subject: Re: [cabfpub] Hopefully Final Version of Google's EV/CT plan


One of Symantec's concerns is that we're currently building to an Experimental RFC. It looks like the Trans Working Group's expectation is to send 6962-bis to the IESG in December 2014. If the document undergoes significant changes close to that deadline, it will be difficult for everyone to comply.

Symantec intends to log certificates using the PRIVATE option proposed by Rob Stradling, so we need that issue to be finalized very soon, to give us time to build and test it.


-----Original Message-----
From: Trans [mailto:trans-bounces at ietf.org] On Behalf Of Ben Laurie
Sent: Wednesday, March 19, 2014 4:47 AM
To: CABFPub; therightkey at ietf.org; trans at ietf.org; certificate-transparency at googlegroups.com
Subject: [Trans] Hopefully Final Version of Google's EV/CT plan

We've updated the EV/CT plan to finalise all TBDs and to clarify some points from the previous version.

The current (and hopefully final) version of the plan can be found at https://sites.google.com/site/certificatetransparency/ev-ct-plan.

Ideally questions should be directed to the appropriate list(s), but feel free also to contact me directly.

Trans mailing list
Trans at ietf.org
Public mailing list
Public at cabforum.org
<table class="TM_EMAIL_NOTICE"><tr><td><pre>
The information contained in this email and any attachments is confidential 
and may be subject to copyright or other intellectual property protection. 
If you are not the intended recipient, you are not authorized to use or 
disclose this information, and we request that you notify us by reply mail or
telephone and delete the original message from your mail system.

More information about the Public mailing list