[Servercert-wg] [DIscussion Period Begins] SC-070: Clarify the use of DTPs for domain control validation

Aaron Gable aaron at letsencrypt.org
Wed Feb 7 18:48:10 UTC 2024


Hi Eva,

I think the requirement is clear: the contact information must be obtained
directly by the CA. If a validation specialist is using a browser to access
WHOIS information that has already been gathered by the CA, then as long as
that information was "obtained directly by the CA", the requirement has
been satisfied. The requirement is on how the CA acquires the information,
now on how individuals within the CA's staff act on that information.

Aaron

On Wed, Feb 7, 2024 at 4:46 AM Eva Van Steenberge <
eva.vansteenberge at globalsign.com> wrote:

> Hello Aaron (and all!)
>
>
>
> Thank you very much for this – excellent work! We only have a question
> with regards to line 665:
>
> > All contact information for Domain Contacts MUST come from the WHOIS
> record, a DNS SOA record, or direct contact with the Domain Name Registrar
> of the Base Domain Name, and MUST be obtained *directly* by the CA, *i.e.
> without the use of third-party services operated outside the CA's audit
> scope*.
>
>
>
> Would this section benefit from a definition for third-party services to
> further remove any risk of ambiguity?
>
>
>
> I feel like we intuitively all have an understanding what is meant, but
> could (to give an extreme example) this text be interpreted as both
> allowing and prohibiting the use of a browser to facilitate representing
> WHOIS information that is otherwise gathered from appropriate sources,
> using an internal service completely developed and controlled by the CA?
>
>
>
> Kind regards,
>
>
>
> Eva
>
>
>
> *From:* Servercert-wg <servercert-wg-bounces at cabforum.org> *On Behalf Of *Aaron
> Gable via Servercert-wg
> *Sent:* 02 February 2024 22:20
> *To:* CA/B Forum Server Certificate WG Public Discussion List <
> servercert-wg at cabforum.org>
> *Subject:* [Servercert-wg] [DIscussion Period Begins] SC-070: Clarify the
> use of DTPs for domain control validation
>
>
>
> This ballot aims to clarify the existing language around the use of
> delegated third-parties during domain and IP address control validation. It
> leaves the existing language in place, and adds specifics for the cases of
> DNS queries, WHOIS lookups, and contact with the Domain Name Registrat or
> IP Address Registration Authority.
>
>
>
> Additionally, it places these same restrictions on CAA checking, with an
> effective date of 2024-05-15.
>
>
>
> This ballot is proposed by Aaron Gable (ISRG / Let's Encrypt) and endorsed
> by Mads Henriksveen (Buypass) and Dimitris Zacharopoulos (HARICA). You can
> view and comment on the github pull request representing this ballot here:
> https://github.com/cabforum/servercert/pull/475
>
>
>
> --- Motion Begins ---
>
>
>
> This ballot modifies the "Baseline Requirements for the Issuance and
> Management of Publicly-Trusted Certificates" ("Baseline Requirements")
> based on Version 2.0.2
>
>
>
> MODIFY the Baseline Requirements as specified in the following redline:
> https://github.com/cabforum/servercert/compare/41f01640748fa612386f8b1a3031cd1bff3d4f35...00ea6e24c474fd0ab6eecc25cb8eb733fffc60c3
>
>
>
> --- Motion Ends ---
>
>
>
> Discussion (at least 7 days):
>
> - Start: 2024-02-02 22:30 UTC
>
> - End no earlier than 2024-02-09 22:30 UTC
>
>
>
> Vote for approval (7 days):
>
> - Start: TBD
>
> - End: TBD
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/servercert-wg/attachments/20240207/ec085306/attachment.html>


More information about the Servercert-wg mailing list