Re: [Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01

[Albert ARIBAUD <[e-mail]>]

Hi again,

Le Fri, 8 Jan 2016 21:33:30 +0100
Albert ARIBAUD <[e-mail]> a écrit:

> Hi Rich,
> 
> Le Fri, 8 Jan 2016 19:52:34 +0000
> "Salz, Rich" <[e-mail]> a écrit:
> 
> > 
> > > draft-ietf-acme-acme-01 states:
> > > 
> > > 	In order to help clients configure themselves with the
> > > right URIs for each ACME operation, ACME servers provide a
> > > directory object. This should be the root URL with which clients
> > > are configured.
> > > 
> > > The question is, what exactly is the "root URL"? At first thought
> > > it would be the "/" path on the server.
> > 
> > The wording misled you, and perhaps should be fixed.  It's more like
> > the "subroot for the ACME tree" or something.
> 
> Can I offer a pull request on github with a fix?

Done : https://github.com/ietf-wg-acme/acme/pull/66

> (note: acme-v01.api.letsencrypt.org would still not match the draft)

Actually, I withdraw this statement: acme-v01.api.letsencrypt.org's
"/directory" is just as compliant as "/acme" or "/". There is no
reason to constrain the path of the directory object to a specific
value.

In fact, not constraining the directory path allows running several
ACME servers on a single HTTP host (if anyone finds a need for that),
as long as each server has a unique directory URL (and unique
resource URIs, to avoid collisions with other ACME servers).

Amicalement,
-- 
Albert.