Third-Party Device Attestation for ACME
draft-yusef-acme-3rd-party-device-attestation-01
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-01-16
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
ACME Working Group R. Shekh-Yusef
Internet-Draft Avaya
Intended status: Standards Track January 16, 2019
Expires: July 20, 2019
Third-Party Device Attestation for ACME
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 20, 2019.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Shekh-Yusef Expires July 20, 2019 [Page 1]
Internet-Draft 3rd-Party Device Attestation for ACME January 2019
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Entities . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Use Case . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3. Initial Trust . . . . . . . . . . . . . . . . . . . . . . 4
2.4. Protocol Flow . . . . . . . . . . . . . . . . . . . . . . 5
3. Identifier Type . . . . . . . . . . . . . . . . . . . . . . . 7
4. Applying for a Certificate . . . . . . . . . . . . . . . . . 7
5. ACME Challenge . . . . . . . . . . . . . . . . . . . . . . . 7
6. Complete Authorization . . . . . . . . . . . . . . . . . . . 8
7. Device Access Token . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
11. Normative References . . . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
ACME [I-D.ietf-acme-acme] is a mechanism for automating certificate
management on the Internet. It enables administrative entities to
prove effective control over resources like domain names, and
automates the process of generating and issuing certificates.
Proving effective control over a device requires an attestation from
a third-party who has authority over the device.
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.
Shekh-Yusef Expires July 20, 2019 [Page 2]
Internet-Draft 3rd-Party Device Attestation for ACME January 2019
Show full document text