# MDCertificateAgreement **URL:** \ **Category:** Help\ **Created:** [November 22, 2017, 1:23pm UTC](https://community.letsencrypt.org/t/mdcertificateagreement/46849 "2017-11-22T13:23:13Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![marcelof](https://avatars.discourse-cdn.com/v4/letter/m/eada6e/32.png) [@marcelof](https://community.letsencrypt.org/u/marcelof)\ **Post date:** [November 22, 2017, 1:23pm UTC](https://community.letsencrypt.org/t/mdcertificateagreement/46849/1 "2017-11-22T13:23:13Z")
Hi Dears, I have one small question about the directive MDCertificateAgreement, i implemented mod\_md in my server, but i saw sometimes the url in MDCertificateAgreement is changeded For example : old url : [https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf](https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf) new url : [https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf](https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf) Existing some place where i can see the news url? my preocupation with this in future some vhost in my conf not renew certificates with mod\_md because this url is changed. thanks for everything, Marcelo ---
**Author:** ![AfroThundr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/afrothundr/32/938_2.png) [@AfroThundr](https://community.letsencrypt.org/u/AfroThundr)\ **Post date:** [November 22, 2017, 1:31pm UTC](https://community.letsencrypt.org/t/mdcertificateagreement/46849/2 "2017-11-22T13:31:24Z")
@marcelof, the current versions of those documents are listed here: [https://letsencrypt.org/repository/](https://letsencrypt.org/repository/) ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [November 22, 2017, 1:32pm UTC](https://community.letsencrypt.org/t/mdcertificateagreement/46849/3 "2017-11-22T13:32:39Z")
> [@marcelof](#): > > Existing some place where i can see the news url? Hi @marcelof, We generally announce the terms-of-service change in the [API Announcements](https://community.letsencrypt.org/c/api-announcements) forum category. [Here is the post](https://community.letsencrypt.org/t/subscriber-agreement-update-november-15-2017/45607) about the change on Nov 15th. > [@marcelof](#): > > my preocupation with this in future some vhost in my conf not renew certificates with mod\_md because this url is changed. The subscriber agreement URL is only checked at the time of creating a registration. If you already have a certificate/registration it shouldn't affect renewals. Hope that helps! ---
**Author:** ![marcelof](https://avatars.discourse-cdn.com/v4/letter/m/eada6e/32.png) [@marcelof](https://community.letsencrypt.org/u/marcelof)\ **Post date:** [November 22, 2017, 1:38pm UTC](https://community.letsencrypt.org/t/mdcertificateagreement/46849/4 "2017-11-22T13:38:53Z")
i guess one sugestion interesting would be create one path in url, so people could be follow the url and change templates automatically, for example : [https://community.letsencrypt.org/licenses](https://community.letsencrypt.org/licenses) Thanks a lot, Marcelo ---
**Author:** ![AfroThundr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/afrothundr/32/938_2.png) [@AfroThundr](https://community.letsencrypt.org/u/AfroThundr)\ **Post date:** [November 22, 2017, 1:47pm UTC](https://community.letsencrypt.org/t/mdcertificateagreement/46849/5 "2017-11-22T13:47:09Z")
@cpu Having a set of static links to the latest versions of those would be handy for automated retrieval purposes. While we’re at it, plain text copies of all of these documents would be nice. 🙂 ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [November 22, 2017, 1:52pm UTC](https://community.letsencrypt.org/t/mdcertificateagreement/46849/6 "2017-11-22T13:52:24Z")
> [@marcelof](#): > > i guess one sugestion interesting would be create one path in url, so people could be follow the url and change templates automatically, for example : > > [https://community.letsencrypt.org/licenses](https://community.letsencrypt.org/licenses) > [@AfroThundr](#): > > @cpu Having a set of static links to the latest versions of those would be handy for automated retrieval purposes. The ACME protocol already implements two separate future-proof ways to learn the current agreement URL at runtime (from the directory meta element and as part of the new-reg flow). It's an unfortunate design decision that mod\_md chose to require users to specify the URL manually. We also maintain a URL endpoint `https://acme-v01.api.letsencrypt.org/terms` that returns a `Location` header to the current agreement URL. This is Let's Encrypt specific and the ACME protocol approaches I mention above are preferable because they will work across other ACME CAs. We don't want to have a generic "[https://community.letsencrypt.org/licenses](https://community.letsencrypt.org/licenses)" URL that works for registration because there is a legal requirement that subscribers indicate the specific subscriber agreement they have read, understood, and agreed to. ---
**Author:** ![bytecamp](https://avatars.discourse-cdn.com/v4/letter/b/54ee81/32.png) [@bytecamp](https://community.letsencrypt.org/u/bytecamp)\ **Post date:** [November 22, 2017, 1:55pm UTC](https://community.letsencrypt.org/t/mdcertificateagreement/46849/7 "2017-11-22T13:55:52Z")
> [@AfroThundr](#): > > Having a set of static links to the latest versions of those would be handy for automated retrieval purposes. For the subscriber agreement, this is already implemented in the ACME protocol: > [@API "/directory" endpoint "meta" field addition](https://community.letsencrypt.org/t/api-directory-endpoint-meta-field-addition/38526): > > T… ---
**Author:** ![AfroThundr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/afrothundr/32/938_2.png) [@AfroThundr](https://community.letsencrypt.org/u/AfroThundr)\ **Post date:** [November 22, 2017, 2:10pm UTC](https://community.letsencrypt.org/t/mdcertificateagreement/46849/8 "2017-11-22T14:10:11Z")
> [@cpu](#): > > The ACME protocol already implements two separate future-proof ways to learn the current agreement URL at runtime (from the directory meta element and as part of the new-reg flow). It's an unfortunate design decision that mod\_md chose to require users to specify the URL manually. > [@bytecamp](#): > > For the subscriber agreement, this is already implemented in the ACME protocol: Thanks for the info guys, I suppose we'd have to bug the `mod_md` devs if we want this behavior changed then. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [December 22, 2017, 2:10pm UTC](https://community.letsencrypt.org/t/mdcertificateagreement/46849/9 "2017-12-22T14:10:22Z")
Closed on December 22, 2017, 2:10pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.