Ballot SC-070: Clarify the use of DTPs for domain control validation #475
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a sentence to BRs Section 3.2.2.4 clarifying that the use of DNS recursive resolvers which are operated outside the CAs audit scope qualifies as use of a Delegated Third Party, which is forbidden for domain control validation.
These are clarifications that the CA must obtain information to be used in the Domain Validation process directly from Domain Name Registrars or IP Address Registration Authorities. CAs must not use third-party services outside their audit scope.
aarongable
changed the title
aarongable
commented
Jan 25, 2024
There was a problem hiding this comment.
Feedback from Validation subcommittee meeting 2024-01-25:
- "All DNS queries conducted in the course of..." sounds like it could include, say, DNS queries made by a validation specialist's browser while looking up the requirements they have to abide by. One suggestion is "All DNS queries required to be conducted in the course of...", but this then perhaps exempts DNS SOA lookups to get Domain Contact information because those are technically optional (could be replaced by WHOIS lookups).
- The phrasing of "from the allowed sources" doesn't make it immediately clear that those allowed sources are listed in the Section 1.6 definition of Domain Contact.
- The sentences added to 3.2.2.4 and 3.2.2.5 don't cover CAA lookups, which are described in 3.2.2.8. We need to ensure that CAA is covered, and probably end up resolving BRs: Clarify whether 3.2.2.8 can be delegated #274 at the same time.
Addressed in the latest commit by saying "in the course of satisfying the requirements of 3.2.2.4, 3.2.2.5, and 3.2.2.8".
Addressed in the latest commit by modifying the definition of Domain Contact to say what one is rather than where the info comes from, and explicitly laying out the requirements for how to obtain a Domain Contact's info in Section 3.2.2.
Addressed in the latest commit by moving the verbiage to Section 3.2.2, and explicitly calling out 3.2.2.8 as one of the covered sections. |
aarongable
changed the title
aarongable
changed the title
dzacharo
reviewed
Feb 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a paragraph to BRs Section 3.2.2 clarifying that all Domain Control Validation DNS queries must be conducted by the CA itself, without the use of third-party recursive resolvers. Similarly clarify that looking up information for Domain Contacts and IP Address Contacts must also be done without third-party services.
Require that CAA checks be performed by the CA itself, and not delegated to a third party.
Fixes #274