Making each host role have it's own distinct name would definitely be a
gain from a clarity perspective but making those distinctions based
solely on the TLD that is being used seems like it'd actually make
things somewhat more confusing.
Instead why not use subdomains below example.com that explicitly
indicate what their role is, e.g. {server,client,validation}.exmaple.com?
On 02/19/2017 02:23 PM, Josh Soref wrote:
> rfc 2606 provides multiple example TLDs.
>
> The acme spec at present uses example.org 3 times,
> example.net 2 times
> example.com 92 times
>
> It's somewhat hard to tell when a URL in an example refers to an ACME
> server and when it refers to the user running the ACME client.
>
> It would be helpful if the sample ACME server domain was example.net,
> the sample domain requested by ACME clients was within example.com,
> and the sample domain for ACME client users (and anything which isn't
> the above two categories) was within example.org.
>
> _______________________________________________
> Acme mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/acme
>
_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme
