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.

Sign up for GitHub

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

Jump to bottom

Remove extraneous "for either" in 3.2.2.4.7 #502

Open
clintwilson opened this issue Apr 18, 2024 · 0 comments
Open

Remove extraneous "for either" in 3.2.2.4.7 #502

clintwilson opened this issue Apr 18, 2024 · 0 comments
Labels
baseline-requirements Server Certificate CWG - Baseline Requirements clean-up Items for future clean-up ballot

Comments

@clintwilson
Copy link
Member

The first paragraph of 3.2.2.4.7 of the TBRs reads (emphasis mine):

Confirming the Applicant's control over the FQDN by confirming the presence of a Random Value or Request Token for either in a DNS CNAME, TXT or CAA record for either 1) an Authorization Domain Name; or 2) an Authorization Domain Name that is prefixed with a Domain Label that begins with an underscore character.

This first instance of for either occurring in this paragraph appears to be extraneous to me.
@clintwilson clintwilson added baseline-requirements Server Certificate CWG - Baseline Requirements clean-up Items for future clean-up ballot labels Apr 18, 2024
XolphinMartijn added a commit to XolphinMartijn/servercert that referenced this issue Oct 22, 2024
@XolphinMartijn
fix: cabforum#502 Remove extraneous "for either"
92dffe5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
baseline-requirements Server Certificate CWG - Baseline Requirements clean-up Items for future clean-up ballot
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@clintwilson