[Acme] I-D Action: draft-ietf-acme-authority-token-tnauthlist-02.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Automated Certificate Management Environment 
WG of the IETF.

Title   : TNAuthList profile of ACME Authority Token
Authors : Chris Wendt
  David Hancock
  Mary Barnes
  Jon Peterson
Filename: draft-ietf-acme-authority-token-tnauthlist-02.txt
Pages   : 13
Date: 2019-03-11

Abstract:
   This document defines a profile of the Automated Certificate
   Management Environment (ACME) Authority Token for the automated and
   authorized creation of certificates for VoIP Telephone Providers to
   support Secure Telephony Identity (STI) using the TNAuthList defined
   by STI certificates.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-acme-authority-token-tnauthlist/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-acme-authority-token-tnauthlist-02
https://datatracker.ietf.org/doc/html/draft-ietf-acme-authority-token-tnauthlist-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-acme-authority-token-tnauthlist-02


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

Re: [Acme] RFC 8555 on Automatic Certificate Management Environment (ACME)

[Kathleen Moriarty]

Well done, thank you all for your work on this document!

Kathleen 

Sent from my mobile device

> On Mar 11, 2019, at 6:05 PM, Daniel McCarney  wrote:
> 
> +1! Thanks everyone!
> 
>> On Mon, Mar 11, 2019 at 6:03 PM Jacob Hoffman-Andrews  wrote:
>> Yes, big thanks! This was a huge group effort over many years, and I'm 
>> very grateful to everyone who has contributed to it.
>> 
>> ___
>> Acme mailing list
>> Acme@ietf.org
>> https://www.ietf.org/mailman/listinfo/acme
> ___
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

Re: [Acme] RFC 8555 on Automatic Certificate Management Environment (ACME)

[Daniel McCarney]

+1! Thanks everyone!

On Mon, Mar 11, 2019 at 6:03 PM Jacob Hoffman-Andrews  wrote:

> Yes, big thanks! This was a huge group effort over many years, and I'm
> very grateful to everyone who has contributed to it.
>
> ___
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>
___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

Re: [Acme] RFC 8555 on Automatic Certificate Management Environment (ACME)

[Yoav Nir]

Starting work on the champagne & ticker-tape slide for the meeting.

Thanks everyone for all the work.

> On 11 Mar 2019, at 23:44, Richard Barnes  wrote:
> 
> Thanks to everyone for your work on this!  
> 
> On Mon, Mar 11, 2019 at 5:08 PM  > wrote:
> A new Request for Comments is now available in online RFC libraries.
> 
> 
> RFC 8555
> 
> Title:  Automatic Certificate Management Environment (ACME) 
> Author: R. Barnes,
> J. Hoffman-Andrews,
> D. McCarney, 
> J. Kasten
> Status: Standards Track
> Stream: IETF
> Date:   March 2019
> Mailbox:r...@ipv.sx, 
> j...@eff.org , 
> c...@letsencrypt.org ,
> jdkas...@umich.edu 
> Pages:  95
> Characters: 196903
> Updates/Obsoletes/SeeAlso:   None
> 
> I-D Tag:draft-ietf-acme-acme-18.txt
> 
> URL:https://www.rfc-editor.org/info/rfc8555 
> 
> 
> DOI:10.17487/RFC8555
> 
> Public Key Infrastructure using X.509 (PKIX) certificates are used
> for a number of purposes, the most significant of which is the
> authentication of domain names.  Thus, certification authorities
> (CAs) in the Web PKI are trusted to verify that an applicant for a
> certificate legitimately represents the domain name(s) in the
> certificate.  As of this writing, this verification is done through a
> collection of ad hoc mechanisms.  This document describes a protocol
> that a CA and an applicant can use to automate the process of
> verification and certificate issuance.  The protocol also provides
> facilities for other certificate management functions, such as
> certificate revocation.
> 
> This document is a product of the Automated Certificate Management 
> Environment Working Group of the IETF.
> 
> This is now a Proposed Standard.
> 
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards 
> ) for the 
> standardization state and status of this protocol.  Distribution of this 
> memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://www.ietf.org/mailman/listinfo/ietf-announce 
> 
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist 
> 
> 
> For searching the RFC series, see https://www.rfc-editor.org/search 
> 
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk 
> 
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-edi...@rfc-editor.org 
> .  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
> 
> ___
> Acme mailing list
> Acme@ietf.org 
> https://www.ietf.org/mailman/listinfo/acme 
> 
> ___
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme

___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

Re: [Acme] RFC 8555 on Automatic Certificate Management Environment (ACME)

[Jacob Hoffman-Andrews]

Yes, big thanks! This was a huge group effort over many years, and I'm 
very grateful to everyone who has contributed to it.


___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

Re: [Acme] RFC 8555 on Automatic Certificate Management Environment (ACME)

[Richard Barnes]

Thanks to everyone for your work on this!

On Mon, Mar 11, 2019 at 5:08 PM  wrote:

> A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 8555
>
> Title:  Automatic Certificate Management Environment (ACME)
> Author: R. Barnes,
> J. Hoffman-Andrews,
> D. McCarney,
> J. Kasten
> Status: Standards Track
> Stream: IETF
> Date:   March 2019
> Mailbox:r...@ipv.sx,
> j...@eff.org,
> c...@letsencrypt.org,
> jdkas...@umich.edu
> Pages:  95
> Characters: 196903
> Updates/Obsoletes/SeeAlso:   None
>
> I-D Tag:draft-ietf-acme-acme-18.txt
>
> URL:https://www.rfc-editor.org/info/rfc8555
>
> DOI:10.17487/RFC8555
>
> Public Key Infrastructure using X.509 (PKIX) certificates are used
> for a number of purposes, the most significant of which is the
> authentication of domain names.  Thus, certification authorities
> (CAs) in the Web PKI are trusted to verify that an applicant for a
> certificate legitimately represents the domain name(s) in the
> certificate.  As of this writing, this verification is done through a
> collection of ad hoc mechanisms.  This document describes a protocol
> that a CA and an applicant can use to automate the process of
> verification and certificate issuance.  The protocol also provides
> facilities for other certificate management functions, such as
> certificate revocation.
>
> This document is a product of the Automated Certificate Management
> Environment Working Group of the IETF.
>
> This is now a Proposed Standard.
>
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and
> suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for
> the
> standardization state and status of this protocol.  Distribution of this
> memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://www.ietf.org/mailman/listinfo/ietf-announce
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
> ___
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>
___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

[Acme] RFC 8555 on Automatic Certificate Management Environment (ACME)

[rfc-editor]

A new Request for Comments is now available in online RFC libraries.


RFC 8555

Title:  Automatic Certificate Management Environment (ACME) 
Author: R. Barnes,
J. Hoffman-Andrews,
D. McCarney, 
J. Kasten
Status: Standards Track
Stream: IETF
Date:   March 2019
Mailbox:r...@ipv.sx, 
j...@eff.org, 
c...@letsencrypt.org,
jdkas...@umich.edu
Pages:  95
Characters: 196903
Updates/Obsoletes/SeeAlso:   None

I-D Tag:draft-ietf-acme-acme-18.txt

URL:https://www.rfc-editor.org/info/rfc8555

DOI:10.17487/RFC8555

Public Key Infrastructure using X.509 (PKIX) certificates are used
for a number of purposes, the most significant of which is the
authentication of domain names.  Thus, certification authorities
(CAs) in the Web PKI are trusted to verify that an applicant for a
certificate legitimately represents the domain name(s) in the
certificate.  As of this writing, this verification is done through a
collection of ad hoc mechanisms.  This document describes a protocol
that a CA and an applicant can use to automate the process of
verification and certificate issuance.  The protocol also provides
facilities for other certificate management functions, such as
certificate revocation.

This document is a product of the Automated Certificate Management Environment 
Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme

[Acme] I-D Action: draft-ietf-acme-authority-token-02.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Automated Certificate Management Environment 
WG of the IETF.

Title   : ACME Challenges Using an Authority Token
Authors : Jon Peterson
  Mary Barnes
  David Hancock
  Chris Wendt
Filename: draft-ietf-acme-authority-token-02.txt
Pages   : 12
Date: 2019-03-11

Abstract:
   Some proposed extensions to the Automated Certificate Management
   Environment (ACME) rely on proving eligibility for certificates
   through consulting an external authority that issues a token
   according to a particular policy.  This document specifies a generic
   Authority Token challenge for ACME which supports subtype claims for
   different identifiers or namespaces that can be defined separately
   for specific applications.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-acme-authority-token/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-acme-authority-token-02
https://datatracker.ietf.org/doc/html/draft-ietf-acme-authority-token-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-acme-authority-token-02


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
Acme mailing list
Acme@ietf.org
https://www.ietf.org/mailman/listinfo/acme