Sorry, the document still not update in “Registration Objects”, still same as Contact.
contact (optional, array of string): : An array of URIs that the server can use to contact the client for issues related to this authorization. For example, the server may wish to notify the client about server-initiated revocation. external_secret (optional, string): : An array of URIs that the server can use to contact the client for issues related to this authorization. For example, the server may wish to notify the client about server-initiated revocation. Best Regards, Andy From: Daniel McCarney [mailto:[email protected]] Sent: Friday, August 19, 2016 11:30 PM To: Andy Ligg <[email protected]> Cc: Jacob Hoffman-Andrews <[email protected]>; [email protected] Subject: Re: [Acme] Add an external secret field to registration > We checked the draft that the external_secret (optional, string) description > is same as Contact. This was fixed: https://github.com/ietf-wg-acme/acme/pull/172#discussion_r75344194 On Fri, Aug 19, 2016 at 7:26 AM, Andy Ligg <[email protected]<mailto:[email protected]>> wrote: We checked the draft that the external_secret (optional, string) description is same as Contact. Another issue we think is how to guarantee this token's security, we plan to limit this token that it will expire at the short time. Please advise, thanks. Regards, Andy > On 18 Aug 2016, at 08:58, Jacob Hoffman-Andrews > <[email protected]<mailto:[email protected]>> wrote: > > Here's one version of what it might look like to add the token Andy > proposed: > > https://github.com/ietf-wg-acme/acme/pull/172 > > Let me know what you think! _______________________________________________ Acme mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/acme
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
