[Acme] RFC 8738 on Automated Certificate Management Environment (ACME) IP Identifier Validation Extension

rfc-editor@rfc-editor.org Sat, 29 February 2020 03:42 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CBC03A0ADE; Fri, 28 Feb 2020 19:42:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lF_lVh6_YQHH; Fri, 28 Feb 2020 19:42:32 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C8EE3A0AC9; Fri, 28 Feb 2020 19:42:32 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 101EBF40740; Fri, 28 Feb 2020 19:42:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, acme@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200229034216.101EBF40740@rfc-editor.org>
Date: Fri, 28 Feb 2020 19:42:16 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/jwzu-rRFxZAdZiDY2mZ10kVya5I>
Subject: [Acme] =?utf-8?q?RFC_8738_on_Automated_Certificate_Management_En?= =?utf-8?q?vironment_=28ACME=29_IP_Identifier_Validation_Extension?=
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Feb 2020 03:42:39 -0000

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

        
        RFC 8738

        Title:      Automated Certificate Management Environment (ACME) 
                    IP Identifier Validation Extension 
        Author:     R.B. Shoemaker
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    roland@letsencrypt.org
        Pages:      5
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-acme-ip-08.txt

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

        DOI:        10.17487/RFC8738

This document specifies identifiers and challenges required to enable
the Automated Certificate Management Environment (ACME) to issue
certificates for IP addresses.

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-editor@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