Sorry for the lag on getting this out. Given the discussions at IETF 101 and on 
the list the main change in this version is the removal of the reverse-dns 
challenge type. While I still think there is some value in at least having a 
technical definition of the method there is enough opposition that it’s 
inclusion in this draft would’ve stopped any forward progress in its tracks. 
Otherwise there are a few minor editorial changes but not much else.

> On May 18, 2018, at 12:49 PM, [email protected] wrote:
> 
> 
> 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 IP Identifier Validation Extension
>        Author          : Roland Bracewell Shoemaker
>       Filename        : draft-ietf-acme-ip-02.txt
>       Pages           : 4
>       Date            : 2018-05-18
> 
> Abstract:
>   This document specifies identifiers and challenges required to enable
>   the Automated Certificate Management Environment (ACME) to issue
>   certificates for IP addresses.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-acme-ip/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-acme-ip-02
> https://datatracker.ietf.org/doc/html/draft-ietf-acme-ip-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-acme-ip-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
> [email protected]
> https://www.ietf.org/mailman/listinfo/acme

_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme

Reply via email to