From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: acme WG <acme@ietf.org>
Subject: WG Review: Automated Certificate Management Environment (acme)
A new IETF working group has been proposed in the Security Area. The IESG
has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send
your comments to the IESG mailing list (iesg at ietf.org) by 2015-06-22.
Automated Certificate Management Environment (acme)
------------------------------------------------
Current Status: Proposed WG
Chairs:
Rich Salz <rsalz@akamai.com>
Ted Hardie <ted.ietf@gmail.com>
Assigned Area Director:
Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Mailing list
Address: acme@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/acme
Archive: http://www.ietf.org/mail-archive/web/acme/
Charter:
Historically, issuance of certificates for Internet applications
(e.g., web servers) has involved many manual identity validation steps
by the certification authority (CA). The ACME WG will specify
conventions for automated X.509 certificate management, including
validation of control over an identifier, certificate issuance,
certificate renewal, and certificate revocation. The initial focus of
the ACME WG will be on domain name certificates (as used by web
servers), but other uses of certificates can be considered as work
progresses.
ACME certificate management must allow the CA to verify, in an
automated manner, that the party requesting a certificate has authority
over the requested identifiers, including the subject and subject
alternative names. The processing must also confirm that the requesting
party has access to the private key that corresponds to the public key
that will appear in the certificate. All of the processing must be done
in a manner that is compatible with common service deployment
environments, such as hosting environments.
ACME certificate management must, in an automated manner, allow an
authorized party to request revocation of a certificate.
The ACME working group is specifying ways to automate certificate
issuance, validation, revocation and renewal. The ACME working
group is not reviewing or producing certificate policies or
practices.
The starting point for ACME WG discussions shall be draft-barnes-acme.
Milestones:
Aug 2015 - Initial working group draft
Mar 2016 - Submit working group draft to IESG as Proposed Standard
WG action announcement
WG Action Announcement
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: acme WG <acme@ietf.org>
Subject: WG Action: Formed Automated Certificate Management Environment (acme)
A new IETF working group has been formed in the Security Area. For
additional information please contact the Area Directors or the WG
Chairs.
Automated Certificate Management Environment (acme)
------------------------------------------------
Current Status: Proposed WG
Chairs:
Rich Salz <rsalz@akamai.com>
Ted Hardie <ted.ietf@gmail.com>
Assigned Area Director:
Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Mailing list
Address: acme@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/acme
Archive: https://mailarchive.ietf.org/arch/browse/acme/
Charter:
Historically, issuance of certificates for Internet applications
(e.g., web servers) has involved many manual identity validation steps
by the certification authority (CA). The ACME WG will specify
conventions for automated X.509 certificate management, including
validation of control over an identifier, certificate issuance,
certificate renewal, and certificate revocation. The initial focus of
the ACME WG will be on domain name certificates (as used by web
servers), but other uses of certificates can be considered as work
progresses.
ACME certificate management must allow the CA to verify, in an
automated manner, that the party requesting a certificate has authority
over the requested identifiers, including the subject and subject
alternative names. The processing must also confirm that the requesting
party has access to the private key that corresponds to the public key
that will appear in the certificate. All of the processing must be done
in a manner that is compatible with common service deployment
environments, such as hosting environments.
ACME certificate management must, in an automated manner, allow an
authorized party to request revocation of a certificate.
The ACME working group is specifying ways to automate certificate
issuance, validation, revocation and renewal. The ACME working
group is not reviewing or producing certificate policies or
practices.
The starting point for ACME WG discussions shall be draft-barnes-acme.
Milestones:
Aug 2015 - Initial working group draft
Mar 2016 - Submit working group draft to IESG as Proposed Standard