# "Generation Y" root program inclusion

**URL:** <https://community.letsencrypt.org/t/generation-y-root-program-inclusion/246108>\
**Category:** ISRG/Organizational\
**Created:** [March 24, 2026, 3:02pm UTC](https://community.letsencrypt.org/t/generation-y-root-program-inclusion/246108 "2026-03-24T15:02:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![AtmosphericIgnition](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/atmosphericignition/32/89826_2.png) [@AtmosphericIgnition](https://community.letsencrypt.org/u/AtmosphericIgnition)\
**Post date:** [March 24, 2026, 3:02pm UTC](https://community.letsencrypt.org/t/generation-y-root-program-inclusion/246108/1 "2026-03-24T15:02:32Z")

</div>

Hi,

I was wondering when will the ISRG apply for inclusion of the new [Generation Y](https://letsencrypt.org/2025/11/24/gen-y-hierarchy) roots to the major root programs? Are there any technical, or CAA/Browser [policy changes](https://letsencrypt.org/2025/05/14/ending-tls-client-authentication) the ISRG is waiting to come into effect before submitting the new roots?

Thank you for any answers.

---

<div class="post-metadata">

**Author:** ![mcpherrinm](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mcpherrinm/32/59604_2.png) [@mcpherrinm](https://community.letsencrypt.org/u/mcpherrinm)\
**Post date:** [March 24, 2026, 4:11pm UTC](https://community.letsencrypt.org/t/generation-y-root-program-inclusion/246108/2 "2026-03-24T16:11:51Z")

</div>

We are beginning the application process. Expect to see public discussion (eg, on the ccadb public mailing list) from the root programs in the coming weeks.

---

<div class="post-metadata">

**Author:** ![AtmosphericIgnition](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/atmosphericignition/32/89826_2.png) [@AtmosphericIgnition](https://community.letsencrypt.org/u/AtmosphericIgnition)\
**Post date:** [March 24, 2026, 11:53pm UTC](https://community.letsencrypt.org/t/generation-y-root-program-inclusion/246108/3 "2026-03-24T23:53:53Z")

</div>

Thank you for the transparency.

---

<div class="post-metadata">

**Author:** ![AtmosphericIgnition](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/atmosphericignition/32/89826_2.png) [@AtmosphericIgnition](https://community.letsencrypt.org/u/AtmosphericIgnition)\
**Post date:** [May 30, 2026, 5:03pm UTC](https://community.letsencrypt.org/t/generation-y-root-program-inclusion/246108/4 "2026-05-30T17:03:52Z")

</div>

Will last month's [incident](https://bugzilla.mozilla.org/show_bug.cgi?id=2038351) affect the timeline of submitting Generation Y certs to root stores?

---

<div class="post-metadata">

**Author:** ![mcpherrinm](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mcpherrinm/32/59604_2.png) [@mcpherrinm](https://community.letsencrypt.org/u/mcpherrinm)\
**Post date:** [May 30, 2026, 7:54pm UTC](https://community.letsencrypt.org/t/generation-y-root-program-inclusion/246108/5 "2026-05-30T19:54:24Z")

</div>

To some degree, yes, but probably only by a matter of weeks. The incident was actually found as part of the inclusion process and debugging why a linter in CCADB was failing.

---

<div class="post-metadata">

**Author:** ![AtmosphericIgnition](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/atmosphericignition/32/89826_2.png) [@AtmosphericIgnition](https://community.letsencrypt.org/u/AtmosphericIgnition)\
**Post date:** [October 3, 2026, 12:05am UTC](https://community.letsencrypt.org/t/generation-y-root-program-inclusion/246108/6 "2026-10-03T00:05:22Z")

</div>

[CAADB Entry](https://ccadb.my.salesforce-sites.com/mozilla/PrintViewForCase?CaseNumber=00003270)  
[Mozilla Root Program Submission](https://bugzilla.mozilla.org/show_bug.cgi?id=2074675)