The list of reserved names is here: https://tools.ietf.org/html/rfc2606
I can understand how something more evocative might be helpful, but at this point, I'm inclined to let it be. --Richard On Thu, Sep 20, 2018 at 8:04 AM Felipe Gasper <fel...@felipegasper.com> wrote: > Are “acmeserver.com” or “caserver.com” reserved domains? > > > What about: > > acme-client.example.com > > acme-server.example.com > > ? > > > -FG > > > On Sep 20, 2018, at 8:58 AM, Kas <kas=40lightc....@dmarc.ietf.org> > wrote: > > > > From section 2 : > > "The CA verifies that the client controls the requested domain name(s) > by having the ACME client perform some action(s) that can only be done with > control of the domain name(s). For example, the CA might require a client > requesting example.com to provision DNS record under example.com or an > HTTP resource under http://example.com."; > > > > I suggest to use "example.com" only for the client mentioned in section > 2, while adding another identifier like "acmeserver.com" or "caserver.com" > will enhance the readability of all these examples. > > > > _______________________________________________ > > Acme mailing list > > Acme@ietf.org > > https://www.ietf.org/mailman/listinfo/acme > > _______________________________________________ > Acme mailing list > Acme@ietf.org > https://www.ietf.org/mailman/listinfo/acme >
_______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
