On 08/17/2016 11:57 AM, Eric Rescorla wrote:
> On Wed, Aug 17, 2016 at 11:27 AM, Jacob Hoffman-Andrews <[email protected]
> <mailto:[email protected]>> wrote:
>
> On 08/17/2016 10:47 AM, Eric Rescorla wrote:
> > I don't think the current text is very clear, so I think if
> we're going
> > to not change
> > that we should keep the text as-is while we discuss what it
> ought to say.
>
> In other words, don't change the protocol part until we have the
> legal /
> UI part nailed down?
>
>
> No, I'm talking solely about this sentence.
Alright, I looked at the diff again and tried another pass of making it
a protocol-only change. How's this?
https://github.com/ietf-wg-acme/acme/pull/167
diff --git a/draft-ietf-acme-acme.md b/draft-ietf-acme-acme.md
index fa0850a..558df73 100644
--- a/draft-ietf-acme-acme.md
+++ b/draft-ietf-acme-acme.md
@@ -173,8 +173,7 @@ The first phase of ACME is for the client to
register with the ACME server. The
client generates an asymmetric key pair and associates this key pair
with a set
of contact information by signing the contact information. The server
acknowledges the registration by replying with a registration object
echoing the
-client's input. The server can also provide terms of service at this
stage,
-which the client can present to a human user.
+client's input.
~~~~~~~~~~
Client Server
@@ -183,7 +182,6 @@ which the client can present to a human user.
Signature ------->
<------- Registration
- Terms of Service
~~~~~~~~~~
@@ -894,6 +892,7 @@ Content-Type: application/jose+json
"url": "https://example.com/acme/new-reg";
})
"payload": base64url({
+ "terms-of-service": "agreed",
"contact": [
"mailto:[email protected]";,
"tel:+12025551212"
@@ -924,16 +923,13 @@ registration URI.
If the server wishes to present the client with terms under which the ACME
service is to be used, it MUST indicate the URI where such terms can be
accessed
in a Link header with link relation "terms-of-service". As noted
above, the
-client may indicate its agreement with these terms by updating its
registration
-to include the "agreement" field, with the terms URI as its value.
When these
-terms change in a way that requires an agreement update, the server MUST
-use a different URI in the Link header.
+client may indicate its agreement when creating registraion by
including the
+"terms-of-service": "agreed" field.
~~~~~~~~~~
HTTP/1.1 201 Created
Content-Type: application/json
Location: https://example.com/acme/reg/asdf
-Link: <https://example.com/acme/terms>;rel="terms-of-service"
Link: <https://example.com/acme/some-directory>;rel="directory"
{
_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme
