# CAs MUST process the accounturi and validationmethods parameters as specified in RFC 8657. — TLS certificate and CA requirement effective dates (CA/Browser Forum, Chrome, Mozilla)

For CAs MUST process the accounturi and validationmethods parameters as specified in RFC 8657., requirement is CAs MUST process the accounturi and validationmethods parameters as specified in RFC 8657; effective date is 2027-03-15; baseline requirements section is 4.2.2.1.2; authority is CA/Browser Forum TLS Baseline Requirements; scope is all publicly-trusted CAs issuing TLS server certificates, recorded from its source on 2026-08-05.

- **Requirement:** CAs MUST process the accounturi and validationmethods parameters as specified in RFC 8657. _(verified: appears in the quote below)_
- **Effective date:** 2027-03-15
- **Baseline Requirements section:** 4.2.2.1.2
- **Authority:** CA/Browser Forum TLS Baseline Requirements _(our reading, not quoted from the source)_
- **Scope:** all publicly-trusted CAs issuing TLS server certificates _(our reading, not quoted from the source)_

## What the source says

> CAs MUST process the accounturi and validationmethods parameters as specified in <https://datatracker.ietf.org/doc/html/rfc8657> RFC 8657

## Source

- https://cabforum.org/working-groups/server/baseline-requirements/requirements/

Last verified: 2026-08-05. Review by: 2026-11-03.
Part of [TLS certificate and CA requirement effective dates (CA/Browser Forum, Chrome, Mozilla)](https://referencesource.org/tls-certificate-requirement-effective-dates/).