* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Acme Status Pages

Automated Certificate Management Environment (Active WG)
Sec Area: Stephen Farrell, Kathleen Moriarty | 2015-Jun-26 —  
Chairs
 
 


2015-06-26 charter

Automated Certificate Management Environment (acme)
---------------------------------------------------

 Charter

 Current Status: Active

 Chairs:
     Rich Salz <rsalz@akamai.com>
     Ted Hardie <ted.ietf@gmail.com>

 Security Area Directors:
     Stephen Farrell <stephen.farrell@cs.tcd.ie>
     Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>

 Security Area Advisor:
     Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>

 Mailing Lists:
     General Discussion: acme@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/acme
     Archive:            https://mailarchive.ietf.org/arch/browse/acme/

Description of Working Group:

  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.

Goals and Milestones:
  Aug 2015 - Initial working group draft
  Mar 2016 - Submit working group draft to IESG as Proposed Standard


All charter page changes, including changes to draft-list, rfc-list and milestones:



Generated from PyHt script /wg/acme/charters.pyht Latest update: 24 Oct 2012 16:51 GMT -