Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BRs: Clarify what "an appropriate way" means for wildcards and gTLDs #229

Open
sleevi opened this issue Nov 18, 2020 · 3 comments
Open

BRs: Clarify what "an appropriate way" means for wildcards and gTLDs #229

sleevi opened this issue Nov 18, 2020 · 3 comments
Assignees
Labels
baseline-requirements Server Certificate CWG - Baseline Requirements enhancement

Comments

@sleevi
Copy link
Contributor

sleevi commented Nov 18, 2020

BRs 3.2.2.6 includes the following language:

CAs MUST refuse issuance unless the applicant proves its rightful control of the entire Domain Namespace.

A CA is not prohibited from issuing a Wildcard Certificate to the Registrant of an entire gTLD, provided that control of the entire namespace is demonstrated in an appropriate way.

This language should be clarified, with reference to specific validation procedures, how to determine "rightful control" and "in an appropriate way". Practically speaking, this means a validation of domain control using a method that modifies DNS at the FQDN level (that is, where the ADN == FQDN == Public Suffix). An e-mail based demonstration of control using WHOIS data, a direct modification of a record on the 'bare' FQDN (and not any underscore prefix), etc.

@sleevi sleevi added enhancement baseline-requirements Server Certificate CWG - Baseline Requirements labels Nov 18, 2020
@barrini
Copy link
Contributor

barrini commented Oct 4, 2023

@dzacharo Dimitris, as per F2F 60, I assigned this issue to you.

@dzacharo
Copy link
Contributor

dzacharo commented Oct 4, 2023

Following up on the discussion at F2F#60, the question raised was what’s considered "an appropriate way"?

Since this issue was opened, the SCWG has defined which Domain Validation Methods from section 3.2.2.4 are applicable to Wildcard Domain Name validation. These are namely:

  • 3.2.2.4.2
  • 3.2.2.4.4
  • 3.2.2.4.7
  • 3.2.2.4.12
  • 3.2.2.4.13
  • 3.2.2.4.14
  • 3.2.2.4.15
  • 3.2.2.4.16
  • 3.2.2.4.17

If there are no objections, we could prepare a ballot to clarify that only methods allowed to validate Wildcard Domain Names are considered appropriate for section 3.2.2.6.

@barrini barrini closed this as completed Apr 25, 2024
@barrini barrini reopened this Apr 25, 2024
@dzacharo
Copy link
Contributor

During the SCWG teleconference of 2024-04-25 it was discussed that the "appropriate way" in 3.2.2.6 could be as easy as replacing with the methods in 3.2.2.4 allowed for wildcard. @timfromdigicert will check if these methods can actually be used for gTLDs to prove control of the Domain Namespace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
baseline-requirements Server Certificate CWG - Baseline Requirements enhancement
Projects
None yet
Development

No branches or pull requests

3 participants