Certificate Transparency: Require SCTs for EV certificates.

tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 6394274d218e672411e5f5d4aacd9fb56747b747..37fdf79eeed733fa17bd9f6024a820e3b13275a9 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -18782,6 +18782,23 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   </summary>
 </histogram>
 
+<histogram name="Net.SSL_EVCertificateCTCompliance"
+    enum="CTRequirementCompliance">
+  <owner>eranm@chromium.org</owner>
+  <owner>rsleevi@chromium.org</owner>
+  <summary>
+    The state of compliance with Certificate Transparency presence requirements
+    for each EV certificate. An EV certificate could be non-compliant (in which
+    case it loses the EV status), comply through inclusion in the EV whitelist
+    or have the required number of Signed Certificate Timestamps. This metric
+    will gauge adoption rate of Certificate Transparency and will help identify
+    when the EV whitelist is no longer needed. Emitted during every SSL
+    connection establishment, but only if the client is checking compliance with
+    Certificate Transparency requirements (currently guarded by a Finch
+    experiment).
+  </summary>
+</histogram>
+
 <histogram name="Net.SSL_EVCertificateInWhitelist" enum="Boolean">
   <owner>eranm@chromium.org</owner>
   <owner>rsleevi@chromium.org</owner>
@@ -42766,6 +42783,12 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <int value="8" label="PlayMusic"/>
 </enum>
 
+<enum name="CTRequirementCompliance" type="int">
+  <int value="0" label="CT_NOT_COMPLIANT"/>
+  <int value="1" label="CT_IN_WHITELIST"/>
+  <int value="2" label="CT_ENOUGH_SCTS"/>
+</enum>
+
 <enum name="DailyEventIntervalType" type="int">
   <int value="0" label="First Run"/>
   <int value="1" label="Day Elapsed"/>