Re: [httpslocal/usecases] An example of the STAR solution in local network (#16) from Tatsuya Igarashi on 2017-11-02 (public-httpslocal@w3.org from November 2017)

From: Tatsuya Igarashi <notifications@github.com>
Date: Thu, 02 Nov 2017 01:59:22 +0000 (UTC)
To: httpslocal/usecases <usecases@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <httpslocal/usecases/pull/16/c341295741@github.com>

>Many thanks for your proposal! I merged it but I'm concerned about:
>'NDO' should be 'DNO' ?

Thanks, it is a typo. I will change to 'DNO'.

>Isn't it necessary for NDC to achieve an ACME challenge in the refresh step? If it is true, I think NDC cannot refresh the certificate in STAR-compliant way because NDC cannot control the DNS entry directly and cannot choose a HTTP-based ACME challenge.

The draft of STAR does not clearly state an ACME challenge at the refresh step. [2.2 Refresh in STAR](https://tools.ietf.org/html/draft-ietf-acme-star-00#section-2.2). I guess that the refresh will be automatically by ACME Server and STAR Server(NDO), so NDC communicates only with ACME server to refresh the cert. I need to study this furthermore.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpslocal/usecases/pull/16#issuecomment-341295741

Received on Thursday, 2 November 2017 01:59:52 UTC