All, I have just submitted new updated version to address the issues raised by Ilari and Ryan. I would appreciate any more reviews and comments.
Regards, Rifaat ---------- Forwarded message --------- From: <[email protected]> Date: Wed, Jan 16, 2019 at 3:28 PM Subject: New Version Notification for draft-yusef-acme-3rd-party-device-attestation-01.txt To: Rifaat Shekh-Yusef <[email protected]> A new version of I-D, draft-yusef-acme-3rd-party-device-attestation-01.txt has been successfully submitted by Rifaat Shekh-Yusef and posted to the IETF repository. Name: draft-yusef-acme-3rd-party-device-attestation Revision: 01 Title: Third-Party Device Attestation for ACME Document date: 2019-01-16 Group: Individual Submission Pages: 9 URL: https://www.ietf.org/internet-drafts/draft-yusef-acme-3rd-party-device-attestation-01.txt Status: https://datatracker.ietf.org/doc/draft-yusef-acme-3rd-party-device-attestation/ Htmlized: https://tools.ietf.org/html/draft-yusef-acme-3rd-party-device-attestation-01 Htmlized: https://datatracker.ietf.org/doc/html/draft-yusef-acme-3rd-party-device-attestation Diff: https://www.ietf.org/rfcdiff?url2=draft-yusef-acme-3rd-party-device-attestation-01 Abstract: This document defines a Third-Party Device Attestation for ACME mechanism to allow the ACME CA to delegate some of its authentication and authorization functions to a separate trusted entity, to automate the issuance of certificates to devices. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
