[cabfpub] Ballot 218: Remove validation methods #1 and #5

Ryan Sleevi sleevi at google.com
Wed Jan 3 13:24:05 MST 2018


Hi Kirk,

We had two endorsers for the discussion. As I mentioned, there's nothing
inherent in needing to direct this to VWG. As DigiCert has pointed out,
there are CAs today that are doing validations that are patently insecure.

While we can understand and appreciate that some members may wish to
introduce new validation methods that are limited in scope and
applicability (for example, Mads' example only applies to a limited subset
of ccTLDs, and cannot be done safely generically), in order to reduce that
risk, I think it's entirely appropriate to take the necessary steps to
ensure the safety of the Internet at large.

This does not prevent or inhibit the issuance of certificates that have
appropriate controls - that is, these methods could be argued as an
'optimization' - and thus we should not unduly delay progress. Regarding
passing it to the VWG, could you indicate where you saw that was suggested?
The only mention of it I saw was from you, on a separate thread, and I'm
curious if perhaps I've missed additional discussion. Certainly, our
workmode does not require sending such discussions "to committee"

On Wed, Jan 3, 2018 at 3:10 PM, Kirk Hall via Public <public at cabforum.org>
wrote:

> Tim, I thought this issue was going to be discussed first by the VWG, as
> several CAs have indicated they would like to keep (but improve) Method 1.
>
>
>
> *From:* Public [mailto:public-bounces at cabforum.org] * On Behalf Of *Tim
> Hollebeek via Public
> *Sent:* Wednesday, January 3, 2018 11:22 AM
> *To:* CA/Browser Forum Public Discussion List <public at cabforum.org>
> *Subject:* [EXTERNAL][cabfpub] Ballot 218: Remove validation methods #1
> and #5
>
>
>
>
>
> Ballot 218: Remove validation methods #1 and #5
>
>
>
> Purpose of Ballot: Section 3.2.2.4 says that it “defines the permitted
> processes and procedures for validating the Applicant’s ownership or
> control of the domain.”  Most of the validation methods actually do
> validate ownership and control, but two do not, and can be completed solely
> based on an applicant’s own assertions.
>
>
>
> Since these two validation methods do not meet the objectives of section
> 3.2.2.4, and are actively being used to avoid validating domain control or
> ownership, they should be removed, and the other methods that do validate
> domain control or ownership should be used.
>
>
>
> The following motion has been proposed by Tim Hollebeek of DigiCert and
> endorsed by Ryan Sleevi of Google and Rich Smith of Comodo.
>
>
>
> -- MOTION BEGINS –
>
>
>
> This ballot modifies the “Baseline Requirements for the Issuance and
> Management of Publicly-Trusted Certificates” as follows, based upon Version
> 1.5.4:
>
>
>
> In Section 3.2.2.4.1, add text at the end: “For certificates issued on or
> after March 1, 2018, this method SHALL NOT be used for validation, and
> completed validations using this method SHALL NOT be used for the issuance
> of certificates.”
>
>
>
> In Section 3.2.2.4.5, add text at the end: “For certificates issued on or
> after March 1, 2018, this method SHALL NOT be used for validation, and
> completed validations using this method SHALL NOT be used for the issuance
> of certificates.”
>
>
>
> In Section 4.2.1, after the paragraph that begins “After the change to any
> validation method”, add the following paragraph: “Validations completed
> using methods specified in Section 3.2.2.4.1 or Section 3.2.2.4.5 SHALL NOT
> be re-used on or after March 1, 2018.”
>
>
>
> -- MOTION ENDS –
>
>
>
> For the purposes of section 4.2.1, the new text added to 4.2.1 from this
> ballot is “specifically provided in a [this] ballot.”
>
>
>
> The procedure for approval of this ballot is as follows:
>
>
>
> Discussion (7+ days)
>
>   Start Time: 2017-01-03  19:30:00 UTC
>
>   End Time: Not Before 2017-01-10 19:30:00 UTC
>
>
>
> Vote for approval (7 days)
>
>   Start Time: TBD
>
>   End Time: TBD
>
>
>
> _______________________________________________
> Public mailing list
> Public at cabforum.org
> https://cabforum.org/mailman/listinfo/public
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/public/attachments/20180103/210c4cba/attachment.html>


More information about the Public mailing list